Date: Sun, 21 Nov 1999 12:01:15 -0800 From: Mike Smith <mike@smith.net.au> To: "Andrey A. Chernov" <ache@freebsd.org> Cc: Mike Smith <mike@smith.net.au>, sthaug@nethelp.no, current@freebsd.org Subject: Re: Root mount failed:22 ??? Message-ID: <199911212001.MAA03373@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 21 Nov 1999 11:05:19 PST." <19991121110519.A38340@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911212001.MAA03373>