MAKEDEV does not make hard disk devices in Unix Cross Install

Asked by jerryrw

I am using the install documentation in appendix D.4 of the install guide on the 7.04 Beta DVD. After running debootstrap to install the base system from the DVD, there are very few devices in /dev. Specifically there are no hard disk devices hdX, sdX so the fstab/mount procedure that follows fails.

Changing to the dev directory prior to the chroot and running MAKEDEV generic fixes the issue.

I do not know if this is a documentation error or a debootstrap config error.

Since I have broken this install three times "tweaking" it, I took very detailed notes on the procedure to cross install from another active Linux distro. I have re-writen the doc to show the work arround but do not know where to post it to.

As I dont know how to link this to another bug report yet, I am also posting a separate bug on the "default" english locale not being installed by debootstrap either.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu installation-guide Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

Documentation bug, I think. Something like 'mount --bind /dev /PATH/TO/TARGET/SYSTEM/dev' is usually best.

Revision history for this message
Phillip Susi (psusi) said :
#2

Yea, MAKEDEV is now obsolete and /dev should be basically empty. At boot time /dev is mounted as a tmpfs and populated with dev nods by udev for the hardware actually installed as it is detected. If you want to chroot into a hard disk from the livecd to manipulate it, you want to bind mount the /dev on the hard disk to your real /dev as Colin said... docs should be updated.

Revision history for this message
Guery Eve (eveguery) said :
#3

Comment installer les paquets manquants pour MP3, Podcaster, et lire DVD

Revision history for this message
Colin Watson (cjwatson) said :
#4

This bug should not have been converted into a question. Guery, please ask your question *separately*, rather than by taking over somebody else's unrelated bug report.

Can you help with this problem?

Provide an answer of your own, or ask jerryrw for more information if necessary.

To post a message you must log in.