"DB" == David Brown <[EMAIL PROTECTED]> "TR" == Tom R. <[EMAIL PROTECTED]>
TR> Although mounting your MacOS disks automatically eases TR> moving your kernels, mounted MacOS disks are read-only disks TR> if you run MOL. If your primary disk is read-only, upon MOL TR> startup the app will hang. MOL needs a read-write TR> partition. Took me a while to figure out why I had problems TR> with MOL on my DebianLombard. DB> Hmm. MOL, and MacOS should work just fine with a read-only DB> partition. It is actually a good idea to do first, to DB> prevent screwing up a partition. You won't be able to do DB> much with the MacOS booted read-only, but it should work. I actually use my mounted HFS disks for more than just moving kernels back and forth (I edit graphics in MacOS and need to move them to Linux, have information (PDFs & HTML) stored on those disks I occasionally need to look at, and so on). It's true that you can't use those disks read-write in MOL if you have them mounted in Linux (annoying, too). I haven't actually gotten MOL to run in a useful way, although I admit that we haven't spent much time on it. MOL generally fails to load if there are any extensions loading, and one possibility that occurred to us is that one or more of the extensions needs to write to one of the non-writable disks. I may give it another try, though -- it would be nice to not have to reboot to use some of my Mac apps. CMC +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Behind the counter a boy with a shaven head stared vacantly into space, a dozen spikes of microsoft protruding from the socket behind his ear. +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ C.M. Connelly [EMAIL PROTECTED] SHC, DS +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
