Gary Greene <[EMAIL PROTECTED]> writes:
> > > First I was to mount /proc because mkinitrd _does not check_
> > > that /proc is available and thus we end in a loop at the step it
> > > scans for /proc/mounts FS.
> >
> > I don't consider that to be a bug. Many (all?) of our system
> > tools rely very much on /proc being available. I'm not even sure
> > the system will boot without a /proc filesystem mounted.
>
> Oh, it WILL boot, but not kindly...
>
> Can I suggest that all Mandrake apps (since this test would be
> almost trivial) with the need to access /proc at least please have a
> check and warning message included so the n00b that gets his new
> linux system almost running and the theoretical chance that the
> mkinitrd util is as broken as it was then won't be pulling their
> hair out in frustration?
so many apps rely on /proc being mounted (which may even be required
by fsstnd, fhs or/and lsb) that if we've to choose between altering
1000 tools or mounting /proc by default, i would choose the later.
which is what we choose to do.
my 2 cents.
there's quite some stuff that one can expect to have. it's good to
test for stuff in configure and the like places, but testing many
features[1] availlability in all programs is more bug prone and
hackward than relying on having these features as defined per
standards.
[1] eg: /proc/ mounted, dynamic loader, ipc, unix domain sockets,
... and whatever you can imagine 99.999% people use and that you
do not check about.
