From: Ethan Benson <erbenson@alaska.net>
To: johnathan spectre <jspectre@lords.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ybin, nvsetenv and MacOS X
Date: Mon, 25 Sep 2000 21:22:55 -0800 [thread overview]
Message-ID: <20000925212255.O1928@plato.local.lan> (raw)
In-Reply-To: <B5F51108.2280%jspectre@lords.com>; from jspectre@lords.com on Mon, Sep 25, 2000 at 02:26:17PM -0400
[-- Attachment #1: Type: text/plain, Size: 2429 bytes --]
On Mon, Sep 25, 2000 at 02:26:17PM -0400, johnathan spectre wrote:
>
> After an install of ybin (I've reinstalled it a few times) selecting "x"
> will result in some disk activity the first time I press "x". Then return me
> to ybin's boot menu.
this means that the command to boot MacOSX failed, when something in
my menu fails OpenFirmware simply reloads it silently. (not terribly
intuitive i know, im not sure what i can really do about it..)
> Pressing "x" every time after boots me into my MacOS 9 partition as if I
> pressed "m" or let the system boot to default (it doesn't cycle after that
> first time).
eventually i think mac-boot (the default OF boot command) will tire of
reloading my script and just look for some other partition to boot.
thats probably whats happening here.
> I'm wondering if ybin hasn't been updated to MacOS X Beta yet or is
> something wrong? OS X is installed on partition 16 on my system and boots
> fine if I use Apple's boot disk app to set it as the boot volume.
well since i don't have access to OSX i am just guessing as to how to
boot it. i am making the assumption that it boots the same way as OS9
(which from what people have told me is true) i execute the command:
boot XX:Y,\\:tbxi where XX is the OpenFirmware path to whatever device
you specified, and Y is the partition you specify. ie: hd:16,\\:tbxi
this SHOULD work assuming apple has a blessed directory on the
partition you specify and a file with type tbxi located there. this
is what is done in HFS+ setups as i understand and what you have on
the OSX bootstrap partition for UFS setups. keep in mind that for a
UFS setup you need to specify the OSX bootstrap partiiton and not the
OSX root partition. for HFS+ setups i asume the OSX root partition is
correct.
> Additionally, I tried "boot hd:16,\\:tbxi" which is what I thought the boot
> menu was trying to do. I get an error message and nothing happens (I might
> be wrong though, I'm still learning what these scripts do).
this is the command my menu is executing yes. can you tell me more
about your OSX install? is it HFS+ or UFS? also a mac-fdisk -l
/dev/hda would be helpful.
another possiblity is you booted OS9 and it mounted your OSX partition
and deblessed it since its not real MacOS.... (this is worse then
win95's installer....)
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
prev parent reply other threads:[~2000-09-26 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-25 18:26 ybin, nvsetenv and MacOS X johnathan spectre
2000-09-26 5:22 ` Ethan Benson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000925212255.O1928@plato.local.lan \
--to=erbenson@alaska.net \
--cc=jspectre@lords.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).