[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#620881: Acknowledgement (installation-guide: MAKEDEV script absence)

Christian PERRIER, le Tue 05 Apr 2011 18:14:06 +0200, a écrit :
> Quoting João Carneiro (baptista.carneiro@gmail.com):
> > i actually found later that the makedev package was missing, so this bug
> > should be reassigned to debootstrap.
> Not really. debootstrap installs the base system and makedev is not
> part of it (since the last release of the package, which indeed hasn't
> been updated since then...mostly because it is considered useless on
> modern Linux systems).
> That bug really belong to the IG, to have it avoid suggesting outdated
> actions.

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?


Reply to: