Re: G3 Beige Tower install help
2008/9/7, Stephen Allen <email@example.com>:
> OK kept the MacOS partition(s). There are 7 of em put there by the MacOS 9
> disk utility (6 small ones).
In Apple's partitioning, the 1st partition contains the partition map,
then there are typically 5 driver partitions used by Mac OS, and then
the actual Mac OS partition. You said in the beginning that you
created the Linux partitions as well with Apple's Disk Utility? Did
you change that part during Debian installation process? Or was it
usable for Debian as such?
> I have one disk and it was labeled hdb when partioning. So that would be
> 'mount -t hfs (It's hfs)/dev/hdb7 (MacOS was installed on the 7th
I'm surprised that it is not hda. Perhaps it is jumpered as slave? It
would more natural to jumper it as master. I remember that some older
G3s had problems with slave drives, at least together with a master.
> There are a bunch of small Apple/MacOS partitions before this. But I assume
> since you mentioned system folder that it's has to go on the larger MacOS
> partition where the Mac system folder is; correct ?
> There didn't appear to be an 'initrd.gz' but there was an 'initrd'. Same
> thing right ? On /mnt I didn't have a directory 'System Folder', however
> mount didn't through any complaints when mounting hdb7, so I assume that
> was OK.
> Unfortunately it didn't boot. I'm getting close though. Any ideas ?
There may be an empty directory called initrd on the root level of
target. The initrd.gz (and vmlinux) should be in boot subdirectory.
You did go through installing the kernel package? This may be a
separate step in the installer.
If you didn't see the 'System Folder' then the mounting was not OK.
The explanation can be that Mac OS has put an HFS wrapper around the
HFS+ file system. So try with 'mount -t hfsplus ...' instead.