Date: Fri, 27 Jun 2014 12:54:58 -0700 From: paul beard <paulbeard@gmail.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>, Polytropon <freebsd@edvax.de> Cc: questions@freebsd.org Subject: Re: what should uname -v be telling me here? Message-ID: <CAMtcK2rZzJPaWBnuZ6s2iZyg4_XjE62JBFTo=iUd%2BT_r4_zoew@mail.gmail.com> In-Reply-To: <44lhsi5ugm.fsf@be-well.ilk.org> References: <CAMtcK2rBDWwu1=4DbKGB_4kDdi5Fz9Mq3%2Bzf_Ph9jTmrCLZpSg@mail.gmail.com> <44lhsi5ugm.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, after some headscratching and physical inspection, it looks like this machine is booting and running from the same physical disk. It appears I never understood that you could boot from a different device than the one that was mounted and holding all your data *without realizing it* or being able to find out (ideally sysctl would reveal the device that the running kernel was pulled from: if it does, I can't make it out). It seems there should be some way to specify a boot device without futzing around in the BIOS or learn what device has been defined. dmesg doesn't even reveal that, as far as I can tell. It looks like boot.config might do some or all of what I expect. I also don't see how I can remove or rewrite just the MBR/bootsector on disk other than the active disk. If I could do that I could be reasonably sure I was booting and running from the disk I think I am. It may be time to stop pretending I know how any of this stuff actually works. On Fri, Jun 27, 2014 at 6:54 AM, Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > paul beard <paulbeard@gmail.com> writes: > >> I noticed that uname -a isn't returning what I expect so I deleted and >> re-pulled a source tree from svn, removed obj, and after a few >> iterations of rebuilding kernels and removing anything I can think of >> to resolve this, I'm at a loss. > > You're clearly not booting from the same kernel that shows up as > /boot/kernel/kernel, so it sounds as though you're booting from > a different partition than whatever is showing up as /boot/kernel > once the system is up. > > Look at your disk partitioning. Also, make sure that you aren't > mounting something on top of /boot in your /etc/fstab. -- Paul Beard / www.paulbeard.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2rZzJPaWBnuZ6s2iZyg4_XjE62JBFTo=iUd%2BT_r4_zoew>