Re: Example miboot on new world rom problem

On Fri, Nov 10, 2000 at 04:53:32PM -0600, jcarr@mail.linuxppc.org wrote:

quoted

setup a 800K Apple_Bootstrap partition where the newworld bootstrap is
installed, that will solve your problem.  if you put it first you
don't need to do anything to OpenFirmwares configuration, just reset
it to defaults.  

Ok. That sounds workable. Is that what OSX does also? If so, will it
conflict?

when OSX is installed on an OldWorld or with UFS filesystems it
creates two bootstrap partitions, the first being Apple_Boot the
second being Apple_Secondary or something close to that.  since i have
been using Apple_Bootstrap OSX appears to ignore ours.  (the installer
does sometimes reorder all the partitions around to put its own first,
which is annoying since it hoses /etc/fstab among other things.  its
fixable with mac-fdisk though i added explanation on how to my
mac-fdisk doc)

quoted

miboot needs alot of things...  simplest way to deal with this is
don't install miboot on a newworld!  we don't install lilo on sparcs
or silo on x86 boxes afterall.  

Well, I think that the macos will not like the system folder unless it has
a system file. But whatever we put in the system folder as the system

the MacOS does not like fake system folders of any kind, even these
fake ones you create are being deblessed and thus made unbootable by
MacOS very regularly.  i have a large mailbox of users asking me what
to do about this, i always tell them to change the partition type of
thier bootstrap partition to Apple_Bootstrap so MacOS can't see it
anymore.  that is the only solution that works 100%  

file, we will still have the problem we were having:

Anyone that has a partition visable to the macos and trys to boot off of
it will still get miboot. And, I think, It will be hard to get people not
to expect that to work.
Jeff

thats why you don't install miboot on a newworld ;-)

-- 
Ethan Benson
http://www.alaska.net/~erbenson/