Date: Tue, 31 May 2011 19:50:11 -0700 From: perryh@pluto.rain.com To: dieterbsd@engineer.com Cc: hackers@freebsd.org Subject: Re: Active slice, only for a next boot Message-ID: <4de5a8e3.kcNH3s3BI3v0Bcca%perryh@pluto.rain.com> In-Reply-To: <20110531234514.95200@gmx.com> References: <20110531234514.95200@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Dieter BSD" <dieterbsd@engineer.com> wrote: > If you neglected to specify RS-232 console in the requirements, > there is this thing. ??I haven't tried it. > http://www.realweasel.com/ Heard of it, aka the PC Weasel. I've never actually seen one. They have been around for a while; the original -- which they apparently still make -- was ISA. > Somebody probably sells a KVM-over-IP box. Raritan, at least. Probably others also. > > Unfortunately it doesn't have a better way to do this as the > > only input it gets from boot0 or any other MBR boot loader is > > the BIOS drive number in %dl. I'm not sure how else you would > > detect that a non-active slice was booted from when that is > > your only input. > > The NetBSD boot code manages to do it. Dunno how NetBSD does it, but one approach that comes to mind would be for whatever installs boot1 to set one of its bytes to the slice number in which it is installed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4de5a8e3.kcNH3s3BI3v0Bcca%perryh>