On Tue, Dec 20, larrystotler@netscape.net wrote:
I added the MacOS patition, /dev/hda6, under YaST. However, when I checked the directory, which I labeled /macos, I found the text file about "Where did all the files go?". So, I looked at /etc/fstab, and the filesystem type was "hfs". I changed it to "hfs+", and was given an error when I tried to remount it. I changed the filesystem type to "hfsplus" and when I remounted it this time it worked fine. I went back into YaST's partitioner and checked to see if there was an option for the Apple HFS+ filesystem, and it only listed 1 Apple filesystem type.
YaST only knows about hfs, not hfsplus.
Do I need to use the ramdisk image to boot the system with an updated kernel? When I uncheck the ramdisk option, and input sda3 as my root device, I get a kernel panic because it can't find the root device. I am assuming that it is not loading the Adaptec SCSI module for some reason. Checking the "Force SCSI" option does not work as well. I have found that since I used YOU to update the kernel that the installation system no longer comes up when I boot using the newer ramdisk, so I don't know if it is a big deal about using the ramsdisk or not. I have 384MB, and I have a good deal of free RAM available.
When the kernel is updated, /boot/vmlinux and /boot/initrd must be copied to the hfs boot partition.
One thing I have noticed is that the USB drivers seem to be loaded before the SCSI drivers using the installation system. It seems that the USB drive gets labeled /dev/sda and the SCSI drive gets bumped to /dev/sdb. After updating my kernel with YOU, It properly loads the adaptec driver and sees /dev/sda3 properly. Perhaps a warning should be given during installation when USB and SCSI drives are detected. I realize that the majority of systems out there use IDE, but there are still many of us that prefer the dependability and speed of SCSI. I realize that a lot of devices are made to look like SCSI in Linux as well as WinDoZe, but it seems there would be a more intelligent way to set this up....
Yes, thats a known problem. For some reason, we like to stick with the kernel names like 'sda' instead of using mount per UUID or persistant device names. Maybe one day it gets changed.
Also, I think I had brought this up once before. Why is it that when I am running under KDE, I have to use "control open-apple Fx" to get to a text terminal, but when I am on a text terminal, I use the standard "control alt Fx" key combination. I know that KDE has an option to edit the key combos, but can this one be modified? It would be nice to have the regular combo all the time.
This is a bug in the kbd package, it needs an update to match what X does. -- short story of a lazy sysadmin: alias appserv=wotan