2.6.12 udev hangs at boot
Quoted 2 lines · Andrew Haninger
Anyway, just a heads-up to anyone else experiencing a breaking of 'less' and missing /dev files.
Yep... I had 'less' break too (you will find 'man' is broke also, rolling on from that).
It turns out to be a problem (typo?) in /etc/udev/rules.d/udev.rules
Try changing:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
to:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
(change is in second line tty -> pty)
As to the missing /dev/ entries - remember you are using udev now - they appear 'on the fly' as and when you plug something in - ensure you have set 'hotplug' to start.
Nick
Signature · 2 lines
"When you're chewing on life's gristle, Don't grumble, Give a whistle..."
Quoted 3 lines · Nick Warne
As to the missing
/dev/entries - remember you are using udev now - they appear 'on the fly' as and when you plug something in - ensure you have set 'hotplug' to start.
I have set hotplug to start on Slackware 10 (chmod a+x /etc/rc.d/rc.hotplug) and it seems to start fine. When running the default udev (v0.26) it loads all that I need for my external hard disk except for sd_mod. If I manually modprobed sd_mod, /dev/sda and /dev/sda1 would be automatically created, which was nice. With the latest version of udev (v0.58) it loads sd_mod when I plug in the drive, but /dev/sd** are not created dynamically (they are there all the time). Having them created dynamically is nifty, but not necessary for me. It would be nice if it was a little more brainless (e.g. /dev entries are created on the fly by default) since I don't know how to turn on/off dynamic creation of /dev entries.
Also, starting hotplug on boot gives a (slight) delay on my system. This might be normal, but I'm not sure.
I'm probably not understanding something correctly, but this is what I'm seeing.
Thanks.
Quoted 16 lines · Nick Warne
Quoted 2 lines · Andrew Haninger
Anyway, just a heads-up to anyone else experiencing a breaking of 'less' and missing /dev files.
Yep... I had 'less' break too (you will find 'man' is broke also, rolling on from that).
It turns out to be a problem (typo?) in
/etc/udev/rules.d/udev.rulesTry changing:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
Quoted 7 lines
to:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"(change is in second line tty -> pty)
Hm, that's what already ships with the udev tarball in the gentoo rule set (which is usually the most up-to-date rule set in the tarball.)
Which one are you looking at?
Quoted 3 lines
As to the missing
/dev/entries - remember you are using udev now - they appear 'on the fly' as and when you plug something in - ensure you have set 'hotplug' to start.
Not necessarily, people are getting udev working and full hotplug support by setting /sbin/hotplug to NULL. Ah, the magic of netlink...
thanks,
greg k-h
Quoted 14 lines · you
Quoted 14 lines
It turns out to be a problem (typo?) in
/etc/udev/rules.d/udev.rulesTry changing:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"to:
# pty devices KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k" KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
Quoted 6 lines
Quoted 1 line
(change is in second line tty -> pty)
Hm, that's what already ships with the udev tarball in the gentoo rule set (which is usually the most up-to-date rule set in the tarball.)
Which one are you looking at?
This wasn't my 'solution' - I googled:
http://kerneltrap.org/node/4474
I don't understand why 'less' broke at all...
Nick
Signature · 2 lines
"When you're chewing on life's gristle, Don't grumble, Give a whistle..."