Date: Thu, 20 Feb 2003 08:15:31 -0600 (GMT) From: Sean Welch <welchsm@earthlink.net> To: Andrew Gallatin <gallatin@cs.duke.edu>, Peter Grehan <grehan@FreeBSD.ORG> Cc: freebsd-ppc@FreeBSD.ORG Subject: Re: Re: Also interested in testing Message-ID: <7241722.1045757734299.JavaMail.nobody@waldorf.psp.pas.earthlink.net>
next in thread | raw e-mail | index | archive | help
Thanks (both of you) for the clarification. It sounds as though
the "safest" method would be to run the loader on HFS+ with
everything else on the UFS slice.
The OS X loader mod is an interesting possibility; they already
have some sort of support for their own funky mod of UFS. (Don't
try to run OS X on UFS -- it is really flakey) I saw some work
being done over in the OpenBSD camp to support that version of
UFS and it looked to me as though the addressing was
non-standard. Maybe standard UFS support wouldn't be that hard
to add, but I'd hate to have to rely on their code to boot
FreeBSD.
Has anyone taken a look at "ofwboot" from Net/OpenBSD? (At
first glance it appears both are using the same code...) Also,
is there any support for the airport wireless yet? When I was
reading through support for the platform offered by the other
BSDs, I believe I saw that the modem is attached internally to
the USB bus; any chance that since 5.0 supports USB modems it
is just recognized as one of those? OpenBSD (I think it was)
could see the modem but had no driver for it.
Sean
-------Original Message-------
From: Andrew Gallatin <gallatin@cs.duke.edu>
Sent: 02/20/03 07:44 AM
To: Peter Grehan <grehan@FreeBSD.ORG>
Subject: Re: Also interested in testing
>
>
Peter Grehan writes:
> > In fact, when I was playing with this, the loader couldn't really
pass
> > the root device to the kernel either, since you need to specify the
> > root device in OFW syntax (<30 chars or so of hex and device names>),
> > not FreeBSD syntax (ad0s10). So in either case, the kernel would
> > stop and ask for its root.
>
> This has to be fixed, but in the meantime, at the loader prompt you
can issue
> something like:
>
> > set vfs.root.mountfrom=ufs:ad0s11
>
> and then boot.
Yes, of course. But its shorter to type ufs:ad0s11 at the mountroot
prompt ;)
What's the prognosis for the loader learning enough about HFS or HFS+
to be able to pull its configuration from files?
Alternatively, I wonder if we could teach the OS-X boot loader about
FFS so that it could load the loader from a FFS partition, and the
loader could remain blissfully ignorant about HFS.
Drew
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ppc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7241722.1045757734299.JavaMail.nobody>