> On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote:
> > You're not using the loader, so nothing gets to read /etc/fstab and set
> > vfs.root.mountfrom. Thus the kernel can't use it to find the root
> > filesystem. I should probably emit a diagnostic to the effect that it
> > wasn't set, since in many cases to come that will be fatal for the boot
> > process.
>
> I just rebuild/reinstall -current /kernel and /sys/boot and update
> bootblocks via disklabel, as result diagnostic
> in question gone, but I _not_ see vfs.root.mountfrom variable in my
> sysctl -a output.
I had hoped I made it clear earlier; vfs.root.mountfrom is a kernel
environment variable, not a sysctl variable. You can read the kernel
environment from the kern.environment sysctl in a slightly non-obvious
fashion: get the oid for kern.environment (two values), then add one
more value to the oid and iterate it from 0 until you receive ENOENT.
Each read will return one string from the kernel environment.
You're probably right in that it should be exposed in the sysctl space,
yes.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message