At Thu, 5 Apr 2001 12:06:10 -0500,
Nathan Scott wrote:
> hi Ed,
> [CC'd to linux-xfs in case others are bitten by this]
> On Apr 4, 9:45pm, Ed McKenzie wrote:
> > Subject: Re: XFS volume labels
> > On Thu, Apr 05, 2001 at 11:26:49AM -0500, Nathan Scott wrote:
> > > another thing to look into will be that /proc/partitions and
> > > /dev are in a sane state - /proc/partitions should be fine
> > > using an xfs kernel with procfs on, but if you've got /dev
> > > mounted elsewhere (using devfs?) to /dev, then this code will
> > > fail to find the devices.
> > >
> > > you may end up having to build mount with -g and stepping thru
> > > it with gdb... I can't seem to reproduce the problem at all.
> > *gods smack Ed*
> > I was booting with devfs=nomount, because it broke a bunch of
> > userspace stuff. I'll have to live with it for now, but mount-by-label
> > does work. Sorry for the spurious bug report.
> No worries - good to see the problem resolved.
> > Any chance SGI might disable devfs in future prerelease RPMS? RedHat's
> I'd say thats unlikely, but its not really my area.
devfs fixes several evilness-es in the way linux handles devices:
As the number of attached devices increases so does the management
of said devices.
We would like to know now devfs is working now before things get to
out of hand.
Other than the "/dev/mouse doesn't exist" or "/dev/cdrom doesn't
exist" what other problems have you experienced?
So yes devfs will remain turned on unless significant problems are
> > official statement is that the distro is devfs-ready, but it's an
> > unsupported configuration -- and I'm quickly learning how unsupported
> > it is. :)
> I guess your best bet is to let the individual authors or
> Red Hat know about those packages which are not working
> with devfs (I've found bugzilla.redhat.com pretty easy to
> use in the past).