Operating Systems > macOS
Linux on PPC?
ravuya:
The iBook is a great machine. Fast, small, and generally durable. However, it is a laptop and quite small. I find that I can't really use it without a full-size keyboard plugged into it. ;)
I recommend that before you get any ideas about buying the thing, that you run out to the shop and see if they'll let you test-drive it.
Yeah, Yaboot is what took out my firmware. It's a real bitch of a bootloader.
I haven't heard much about the internal softmodems on most Apple hardware, but from what I understand, YDL has support for them. You might want to email them and back that point up.
[ October 24, 2002: Message edited by: Ravuya ]
Zombie9920:
quote:Originally posted by Ravuya:
The iBook is a great machine. Fast, small, and generally durable. However, it is a laptop and quite small. I find that I can't really use it without a full-size keyboard plugged into it. ;)
I recommend that before you get any ideas about buying the thing, that you run out to the shop and see if they'll let you test-drive it.
Yeah, Yaboot is what took out my firmware. It's a real bitch of a bootloader.
I haven't heard much about the internal softmodems on most Apple hardware, but from what I understand, YDL has support for them. You might want to email them and back that point up.
[ October 24, 2002: Message edited by: Ravuya ]
--- End quote ---
So, Linux boot loaders don't only fuck with Windows...they also fuck with MacOS, ehhh(just like I said to lazy g in another thread..it was Lilo's fault that his Windows boot record got taken out)? Isn't there some way for you to clean your Master Boot Record on a Mac? With Windows you would just boot to DOS and run fdisk /mbr(this doesn't take out Windows since Windows does write it's boot info in the MBR..it uses system files on the regular partation to boot) then poof the Linux boot loader is gone....I couldn't imagine Apple not giving MacOS users a way of cleaning thier mbr without taking out the whole partation.
[ October 24, 2002: Message edited by: Zombie9920 ]
voidmain:
FDISK /MBR does not remove the boot loader, it just puts the backup copy of the MBR over the primary copy. The MBR is just the first sector of the disk consisting of 512 bytes and is really nothing more than a pointer to somewhere else on disk where the actual boot loader code resides. Having said that, Windows only has the capability of booting other Microsoft operating systems so the need for an alternate boot loader is necessary (such as LILO, GRUB, System Commander, etc). Apparently MacOS is the same, but I do not have experience with MacOS so I can't speak for it.
If you understand the boot loader, and the boot process of each operating system in question you should have no trouble with it. And I have *never* had a case where I had to dump a partition because of boot loader problems as boot loaders only really mess with boot sectors on the partition. And I have multi booted many OSs in my time from just about every version of Microsoft OSs to many different Linux distros, to OS/2 Warp, to Solaris x86, to BE, to etc..
You do have to know what you are doing though in many circumstances. For instance, if you know what you are doing you would also know that there are other ways other than "FDISK /MBR" to replace the master boot record. For instance you can use "dd" rather than "FDISK /MBR", or just install another boot loader which will place it's own pointer code in that first 512 bytes of the disk.
The easiest way is to set up the boot loader of each OS to load said OS from the "partition" boot record (first 512 bytes of the partition that the OS resides on). Then you use a master boot loader (such as LILO, GRUB, System Commander, etc) to load each of those partitions and be the loader called from the MBR.
psyjax:
The way to manuly edit the boot record on a Mac is to boot into the firmware and change it there. I did this, but it never seemed to work.
I could boot OSX, but not classic. I'm almost certain it was yaboot's fault and to clean up the problem I would have needed a magnet.
None the less, I got stuff workin hunky dory naw adays so who's counting
ravuya:
I fixed it by removing the battery for 15 minutes, walking around, watching TV. When I came back and reinserted the battery and plugged the machine back in, the firmware was fine. The drive was still dead, however. I really miss that drive.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version