Bug#620881: Acknowledgement (installation-guide: MAKEDEV script absence)
Christian PERRIER, le Tue 03 May 2011 06:53:53 +0200, a écrit :
> Quoting Samuel Thibault (email@example.com):
> > What should be done instead? FTR, what's in IG is currently
> > “D.3.4.1. Create device files
> > At this point /dev/ only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using udev) or static device files for the new system.
> > A few of the available options are:
> > * create a default set of static device files using
> > # cd /dev
> > # MAKEDEV generic
> > * manually create only specific device files using MAKEDEV
> > * bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care”
> > The /dev/sda* or /dev/hda* entries are for instance needed to get the
> > next steps working. Is bind mounting some other Linux system's /dev
> > really the now-recommended way?
> Hmmm. I'd vote for keeping the first paragraph only.
Well, it's not very good for a documentation to mention that there are
"different ways", and not mention them. Since this paragraph is about
installing from Linux, it can be suggested to use the host's MAKEDEV
script, if there is any.
> Maybe add something saying roughly that, by default, a system with
> udev installed is good enough for most uses.
Err, this part of the documentation is not about choosing between
enabling udev or not. It's about setting up some /dev entries for e.g.
bootloader setup, since udev on /dev is not running at that stage.