Date: Sat, 30 Apr 2011 19:39:09 +0200 From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Subject: Re: Look of boot2, on HDD Message-ID: <20110430.173909.578.1@DEV> In-Reply-To: <4DBC3D63.6020508@FreeBSD.org> References: <20110429.160309.656.1@DEV> <mailpost.1304116761.7079263.67267.mailing.freebsd.hackers@FreeBSD.cs.nctu.edu.tw> <4DBC3D63.6020508@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----=0D=0AFrom: Alexander Motin =
<mav@FreeBSD.org>=0D=0ATo: freebsd-hackers@freebsd.org=0D=0ADate: Sat, 30 =
Apr 2011 19:48:35 +0300=0D=0ASubject: Re: Look of boot2, on =
HDD=0D=0A=0D=0A> Garrett Cooper wrote:=0D=0A> > 2011/4/29 =
<rank1seeker@gmail.com>:=0D=0A> >> /boot/boot2 STAGE 2 bootstrap =
file=0D=0A> >> Understands the FreeBSD file system enough, to find files =
on it, and can provide a simple interface to choose the kernel or loader =
to run.=0D=0A> >>=0D=0A> >> Once sys is fully booted, HDD is =
'ada0'.=0D=0A> >> However, STAGE 2, sees it, as a 'ad4', at boot process, =
which is same seen, by booted sys, when I turn off AHCI.=0D=0A> >>=0D=0A> =
>> So, here is the riddle ...=0D=0A> >> On fully booted sys, how do I =
query STAGE 2, to tell me, how it'll see, my 'ada0' HDD?=0D=0A> > =0D=0A> =
> This is a very interesting catch:=0D=0A> > =0D=0A> > =
/usr/src/sys/boot/pc98/boot2/boot2.c:static const char *const=0D=0A> > =
dev_nm[NDEV] =3D {"ad", "da", "fd"};=0D=0A> > =
/usr/src/sys/boot/i386/boot2/boot2.c:static const char *const=0D=0A> > =
dev_nm[NDEV] =3D {"ad", "da", "fd"};=0D=0A> > =0D=0A> > It probably =
will be a no-op soon because of some of the=0D=0A> > compatibility =
changes Alex made, but still a potential point of=0D=0A> > confusion =
nonetheless.=0D=0A> =0D=0A> Pardon my ignorance, but could somebody shed =
some light for me on this=0D=0A> list of names? Why much more =
sophisticated loader(8) operates disks as=0D=0A> diak0/1/..., while boot2 =
tries to mimic something he has no any idea=0D=0A> about, using very =
limited information from random sources? Does this=0D=0A> names important =
for anything?=0D=0A> =0D=0A> Even with old ATA names didn't match on my =
laptop: boot2 reports ad0,=0D=0A> while system - ad4. Also we have a lot =
of drivers who's disk names don't=0D=0A> fit into this set of ad, da and =
fd.=0D=0A> =0D=0A> -- =0D=0A> Alexander Motin=0D=0A=0D=0AWell ..., ATM, I =
say lets NOT touch/edit boot2 nor loader.=0D=0ALet them continue to see =
devices, the way they "like" ...=0D=0A=0D=0ANOW, all I would like, is to =
find a way of ASKING them, how will they see "$target" device, at theirs =
boot step/time.=0D=0A"Asking" is done, on a fully booted sys and I am =
interested in asking STAGE 2 (boot2).=0D=0A=0D=0A=0D=0ADomagoj =
Smol=E8i=E6=0D=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110430.173909.578.1>