Date: Fri, 27 Jun 2014 13:57:06 -0700 From: paul beard <paulbeard@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: "questions@freebsd.org" <questions@freebsd.org>, Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Subject: Re: what should uname -v be telling me here? Message-ID: <CAMtcK2rh3tSF6brU_JxA1%2Btzzuv8SsEoHf_oxAhcW95NRRpKjQ@mail.gmail.com> In-Reply-To: <20140627223650.25210a53.freebsd@edvax.de> References: <CAMtcK2rBDWwu1=4DbKGB_4kDdi5Fz9Mq3%2Bzf_Ph9jTmrCLZpSg@mail.gmail.com> <44lhsi5ugm.fsf@be-well.ilk.org> <CAMtcK2rZzJPaWBnuZ6s2iZyg4_XjE62JBFTo=iUd%2BT_r4_zoew@mail.gmail.com> <20140627223650.25210a53.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 27, 2014 at 1:36 PM, Polytropon <freebsd@edvax.de> wrote: > You need to find out where /boot resides (in my case, > it's on ad4s1a, which is mounted at /) to identify the boot > device (or to be precise, the device the kernel has been read > from). I keep thinking this should be something you ought to be able to discover without being on console. I realize the BIOS can't be interrogated but if I knew that the active kernel was ad3:/boot/kernel or ad2:/boot/kernel, it would be useful. Kind of surprised that doesn't appear anywhere in dmesg or that it can't be read out of somewhere. -- Paul Beard / www.paulbeard.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2rh3tSF6brU_JxA1%2Btzzuv8SsEoHf_oxAhcW95NRRpKjQ>