/dev/null under devfs (was Re: perl problem)

Craig M. Reece craigthulu at earthlink.net
Sun Jan 14 15:32:16 PST 2001


Sorry, these are only problems in the chroot environment where there is 
nothing in the /dev directory even with a devfs kernel.

On Sunday, January 14, 2001 06:26 pm, scott thomason spoke thusly:
> It's funny that you had trouble with /dev/null. The devfs doc states
> explicitly that /dev/null (and zero, etc.) is provided. I guess I'll find
> out later tonight... ---scott
>
> On Sun, 14 Jan 2001 18:05:28 -0500, Craig M. Reece said:
> > I ended up switching back to creating my own /dev entries (MAKEDEV was
> > too old to cover everything) since I couldn't get vmware to play nice
> > with devfs. I have since then found some more documentation and will give
> > devfs another whirl with my next LFS install (which will also use kernel
> > 2.4, glibc 2.2.1, etc.)
> >
> >  You may also want to include a few other handy /dev entries depending on
> > what else you intend to install before rebooting, for example,
> > /dev/random and /dev/urandom before doing openssh, gpg, etc. I am sure
> > there are others but I can't remember them all now... Basically /dev/null
> > was the only one that, if it was missing, would cause confusing error
> > messages, the other missing ones generated very clear error messages from
> > the package at hand.
> >
> >  Another hint... you can attach the /proc filesystem to more than one
> > place in the tree (with kernel 2.4, I think you can bind any part of the
> > file tree multiple times). This is really needed in the chroot
> > environment for something or other that I installed... (not in the book).
> >
> >
> >  Hrm... time to stop rambling fo a bit ;)
> >
> >  On Sunday, January 14, 2001 01:29 pm, scott thomason spoke thusly:
> >  > Thanks! I'm just building devfs right now, I'm sure it would have bit
> >  > me. ---scott
> >  >
> >  > On Sun, 14 Jan 2001 10:09:26 -0500, Craig M. Reece said:
> >  > > It was one of my early problems when I switched to using devfs.
> >  > > Since I was no longer using MAKEDEV, the /dev/null didn't exist when
> >  > > I was building perl. Popping back out of chroot and mknod 'ing it
> >  > > did the job.
> >  > >
> >  > >  On Sunday, January 14, 2001 07:32 am, scott thomason spoke thusly:
> >  > >  > I don't think that's it, but I'd sure like to hear if it works
> >  > >  > for you. ---scott
> >  > >  >
> >  > >  > On Sun, 14 Jan 2001 00:20:24 -0500, Craig M. Reece said:
> >  > >  > > Make sure you have a /dev/null available.
> >
> >  --
> >  Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
> >  and put unsubscribe in the subject header of the message

-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the lfs-dev mailing list