Dan Nicholson wrote:
> On 2/18/06, Matthew Burgess <[EMAIL PROTECTED]> wrote:
>> Alternatively, what purpose does populating /dev do at this stage?  Does
>> something we build later on actually require devices in there that we
>> haven't yet got available to us?
> 
> Hi Matt,
> 
> Glad to hear some news on the udev branch.  Anyway, I don't think
> populating /dev after udev has any real benefits.  When I was doing
> the ICA builds, I was never running the udevstart command, and I never
> had any issues.  The only place I could see them being needed is
> potentially for running the grub shell in Ch. 8.4.
> 
> The first time grub is run it scans your system for potential drives
> and creates /boot/grub/device.map.  I'm not sure about this, but it
> might need to have the corresponding device nodes in /dev to find,
> e.g, hda.  I'd have to test that, though.  Maybe someone else knows.

However, some people build, for instance X11, in the chroot (very
tempted to let my spellchecker change this to cheroot :) environment,
and they might need some of the device nodes.  Joe's way might be best,
however.

R.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to