From: Greg KH <greg@kroah.com>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 23:45:54 -0700 [thread overview]
Message-ID: <20050621064554.GC15239@kroah.com> (raw)
In-Reply-To: <200506191639.27970.nick@linicks.net>
On Sun, Jun 19, 2005 at 04:39:27PM +0100, Nick Warne wrote:
> Andrew Haninger wrote:
>
> > 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)
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?
> 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
next prev parent reply other threads:[~2005-06-21 8:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 15:39 2.6.12 udev hangs at boot Nick Warne
2005-06-19 21:23 ` Andrew Haninger
2005-06-21 6:45 ` Greg KH [this message]
2005-06-21 17:06 ` Nick Warne
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 15:32 Nick Warne
2005-06-21 6:40 ` Greg KH
2005-06-18 12:32 Nick Warne
2005-06-18 13:03 ` Alistair John Strachan
2005-06-18 13:44 ` Nick Warne
2005-06-18 14:58 ` Andrew Walrond
2005-06-18 16:53 ` Jeff Garzik
2005-06-18 17:06 ` Nick Warne
2005-06-19 15:04 ` Andrew Haninger
2005-06-20 10:04 ` Denis Vlasenko
2005-06-20 10:17 ` Stefan Smietanowski
2005-06-20 11:13 ` Denis Vlasenko
2005-06-20 16:25 ` Stefan Smietanowski
2005-06-20 16:39 ` Bill Davidsen
2005-06-20 16:48 ` Greg KH
2005-06-20 17:24 ` Jeff Garzik
2005-06-20 17:34 ` Greg KH
2005-06-20 19:00 ` Nick Warne
2005-06-20 19:21 ` Greg KH
2005-06-20 19:32 ` Nick Warne
2005-06-20 19:42 ` David Lang
2005-06-21 6:28 ` Greg KH
2005-06-21 6:31 ` David Lang
2005-06-21 6:47 ` Greg KH
2005-06-20 19:46 ` Jesper Juhl
2005-06-20 19:34 ` Andrew Haninger
2005-06-20 19:49 ` Josh Boyer
2005-06-21 6:42 ` Greg KH
2005-06-20 19:24 ` Olaf Hering
2005-06-20 21:26 ` Daniel Barkalow
2005-06-20 22:14 ` Jesper Juhl
2005-06-20 22:26 ` Tomasz Torcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050621064554.GC15239@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox