| Summary: | sys-fs/udev-147: warns the user to add udev-postmount to default runlevel even if it has been added | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | peng shao <shallpion> |
| Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | aklhfex, base-system, cancellettopugno, leho, oeffentlicheszeug, padangustasana, roy, teidakankan |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | /etc/init.d/udev | ||
|
Description
peng shao
2009-11-22 20:46:59 UTC
Very strange. Please attach your /etc/init.d/udev file. If your file contains this in _start():
if [ ! -e /etc/runlevels/${RC_DEFAULTLEVEL:-default}/udev-postmount ]; then
ewarn "You should add udev-postmount service to your default runlevel."
fi
then add this in the line before "if":
echo default runlevel: ${RC_DEFAULTLEVEL}
Created attachment 210984 [details]
/etc/init.d/udev
(In reply to comment #1) > Very strange. Please attach your /etc/init.d/udev file. If your file contains > this in _start(): > if [ ! -e /etc/runlevels/${RC_DEFAULTLEVEL:-default}/udev-postmount ]; > then > ewarn "You should add udev-postmount service to your default > runlevel." > fi > then add this in the line before "if": > echo default runlevel: ${RC_DEFAULTLEVEL} > Dear Matthias, I looked into /etc/init.d/udev and add that line to the position suggested then did a restart, but the strange message remains there. I posted my /etc/init.d/udev file in the attachment(without that line added). If my memory serves me I haven't touch it at all, just leave it as default since I have no need to modify it... Thanks. Sorry that file actually includes the line---I forgot to remove it before uploading. Sorry for that. By the way, I tried several versions of udev before 147, and none of them produced the second message about the existence of /dev/mapper/control, is this warning-like message a new feature of 147, or something wrong? Thanks. (In reply to comment #1) > Very strange. Please attach your /etc/init.d/udev file. If your file contains > this in _start(): > if [ ! -e /etc/runlevels/${RC_DEFAULTLEVEL:-default}/udev-postmount ]; > then > ewarn "You should add udev-postmount service to your default > runlevel." > fi > then add this in the line before "if": > echo default runlevel: ${RC_DEFAULTLEVEL} > Sorry, I did a restart again and fount the first time I missed the important output of echo. I bet you won't believe it :) It is default runlevel: shutdown I did touch /etc/runlevels/shutdown/udev-postmount, and found this worked for the warning message "You should ...." It looks like some variables are messed up on my machine.... (In reply to comment #5) > (In reply to comment #1) > > then add this in the line before "if": > > echo default runlevel: ${RC_DEFAULTLEVEL} > > > > Sorry, I did a restart again and fount the first time I missed the important > output of echo. I bet you won't believe it :) It is > > default runlevel: shutdown > Looks strange. @Roy: Please have a look. > I did touch /etc/runlevels/shutdown/udev-postmount, and found this worked for > the warning message "You should ...." > > It looks like some variables are messed up on my machine.... > I did a simple test: during the boot process, I press "I" to call the interactive boot, and before I start any service I exit to shell at first, then run "echo $RC_DEFAULTLEVEL" to test what the value of this variable is. I list my result in the following. Here the format of the result is "service:shutdown/default", which means BEFORE I start the service, the value of $RC_DEFAULTLEVEL is shutdown/default. sysfs:shutdown udev-mount:shutdown dmesg:shutdown udev:shutdown devfs:shutdown hwclock:default .... It looks like after devfs was started the variable was set to the expected default Thanks Any solution for this issue...? (In reply to comment #8) > Any solution for this issue...? > No solution yet.. :( I opened a thread in the forum, looks like someone has more weird phenomenon on this issue :( i am also running into this warning, except for me RC_DEFAULTLEVEL has value "backup", a custom runlevel i've created. why it gets assigned to that variable, i have no idea. softlevel kernel parameter related perhaps? i cannot recall if i had that set when debugged this. This is no longer problem since postmount is gone in current stable =sys-fs/udev-197-r3. *** Bug 368041 has been marked as a duplicate of this bug. *** |
