| 1 |
On Fri, Dec 02, 2005 at 12:45:00PM +0900, Georgi Georgiev wrote: |
| 2 |
> maillog: 02/12/2005-02:47:55(+0000): Stephen Bennett types |
| 3 |
> > On Fri, 02 Dec 2005 03:35:23 +0100 |
| 4 |
> > Matthias Langer <mlangc@×××.at> wrote: |
| 5 |
> > |
| 6 |
> > > revealed that there are in fact hundrets of premade device nodes in |
| 7 |
> > > the /dev directory. And this is not only true for the box where i |
| 8 |
> > > discovered this, which was brought up from a 2004.x cd, but also true |
| 9 |
> > > for the box where i just installed gentoo from 2005.1-r1. |
| 10 |
> > > |
| 11 |
> > > Is there any reason for this ? |
| 12 |
> > |
| 13 |
> > Not all systems use udev or devfs. Plus, it's nice to be able to boot |
| 14 |
> > the system when your dynamic /dev management fails for whatever reason. |
| 15 |
> |
| 16 |
> I don't need a fully populated /dev to get a working shell with |
| 17 |
> init=/bin/bash on the kernel cmdline. And at that point it is easy to |
| 18 |
> run /dev/MAKEDEV and get whatever devices are needed for |
| 19 |
> troubleshooting. |
| 20 |
> |
| 21 |
> I of course assume that if the dynamic /dev management fails, then we |
| 22 |
> need to *recover* instead of trying to get the system up as usual. And I |
| 23 |
> also assume that the init scripts will anyway tell me "fatal error: give |
| 24 |
> root password for maintenance or Ctrl-D to continue" if I have something |
| 25 |
> vital missing from /dev. |
| 26 |
|
| 27 |
If udev fails, and you have a completly empty /dev, you will not get any |
| 28 |
console output at all for this type of message to be shown :( |
| 29 |
|
| 30 |
So it's better to be safe than sorry. |
| 31 |
|
| 32 |
That being said, my boxes have an empty /dev... |
| 33 |
|
| 34 |
thanks, |
| 35 |
|
| 36 |
greg k-h |
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives