udev.conf - Issue 6879062: Add boot-services milestone marker for boot; fixed udev-addon init time.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: udev.conf

Issue 6879062: Add boot-services milestone marker for boot; fixed udev-addon init time. (Closed) Base URL: ssh://gitrw.chromium.org:9222/init.git@master

Patch Set: Address jrbarnette review feedback. Created 9 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
1 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.	1 # Copyright (c) 2011 The Chromium OS Authors. All rights reserved.

2 # Use of this source code is governed by a BSD-style license that can be	2 # Use of this source code is governed by a BSD-style license that can be

3 # found in the LICENSE file.	3 # found in the LICENSE file.

4	4

5 description "Start the udev daemon"	5 description "Start the udev daemon"

6 author "chromium-os-dev@chromium.org"	6 author "chromium-os-dev@chromium.org"

7	7

8 # Start udev early so flimflam can be notified of "wlan0". The	8 # Start udev early so flimflam can be notified of "wlan0". The

9 # general "trigger" for remaining devices is now in the udev-addon	9 # general "trigger" for remaining devices is now in the udev-addon

10 # job	10 # job

11 start on runlevel 2	11 start on starting boot-services

	12 stop on stopping boot-services
	diandersAtChromium 2011/04/20 16:36:44 NOTE: I'm not convinced this is right. It certain NOTE: I'm not convinced this is right. It certainly changes behavior. I am getting errors spewed when I do a 'shutdown -r now' from the command line. I will check whether this was the cause.
12	13

13 respawn	14 respawn

14 expect fork	15 expect fork

15	16

16 pre-start script	17 pre-start script

17 # udev uses inotify to monitor the dynamic rules directory	18 # udev uses inotify to monitor the dynamic rules directory

18 # /dev/.udev/rules.d; however, this directory must exist before	19 # /dev/.udev/rules.d; however, this directory must exist before

19 # udevd runs, or the inotify won't find the directory even if it	20 # udevd runs, or the inotify won't find the directory even if it

20 # is created later. This is an issue with udev-146. Udev	21 # is created later. This is an issue with udev-146. Udev

21 # versions 156 and later do not exhibit this problem, and for	22 # versions 156 and later do not exhibit this problem, and for

(...skipping 17 matching lines...) Expand all Loading...
39 # one.	40 # one.

40 mv $drvfile $drvfile.bad	41 mv $drvfile $drvfile.bad

41 MESSAGE="udev pre-start: modprobe $drv failed."	42 MESSAGE="udev pre-start: modprobe $drv failed."

42 MESSAGE="$MESSAGE Renamed $drvfile with .bad suffix."	43 MESSAGE="$MESSAGE Renamed $drvfile with .bad suffix."

43 logger "$MESSAGE"	44 logger "$MESSAGE"

44 fi	45 fi

45 fi	46 fi

46 end script	47 end script

47	48

48 exec udevd --daemon	49 exec udevd --daemon

OLD	NEW

« dbus.conf ('K') | « system-services.conf ('k') | no next file » | no next file with comments »