n 2008/02/17 07:38 (GMT-0800) rafe apparently typed:
A real SCSI disk, an SATA disk, or a PATA disk (which by default the
installer will pretend is SCSI)? If the latter, you can regain access to all
partitions by installing with a special parameter explained by the official
You should use advanced partitioning only for dealing with the pre-existing
partitions you created in advance prior to starting the SUSE YaST installer.
Using more than one partitioning tool on the same HD usually means
unnecessary trouble. I do all my partitioning in advance with DFSee, then use
the SUSE partitioner merely for designating what partitions to use for what
You should have a separate partition of type 82 for Linux swap, roughly
double your RAM size as a minimum - if your total RAM is conservative. Double
a large amount of RAM is essentially a pointless waste of disk space - unless
you use swap to suspend to disk.
I recommend you spend some time figuring out a way to do some partition
consolidation. Lots of partitions when you use only OS/2 is not a terribly
big deal, but in a multiboot environment, that complexity gets out of hand.
My OS/2 boot is always F:, making it easier to redo things updisk.
The simple page doesn't provide some options you need. Don't try to use it.
Linux pretends it can't tell the difference between HPFS and NTFS. It seems
to like to try to mount all 07 partitions as NTFS. One way to work around
that is to change them all to hidden HPFS. If you manually set the mount
points, then it should accept what you select. Right now I should be asleep,
and can't remember its preference. I sometimes set my HPFS mount points
during install, sometimes manually after installation is done.
Trying to add one with LVM or FDISK is convoluted. I never use either of
them. I do all disk partitioning with DFSee, which can be executed regardless
what is booted. Adding a partition to BM in DFSee is very simple.
If you want BM to be your master boot loader, SUSE's boot loader belongs on a
partition, not the MBR. If you have a separate /boot, that's where it goes.
Otherwise, it goes on /. Within the boot loader step of installation there
are checkboxes for what to do with it. If you have a disk 1 primary on which
SUSE's / or /boot go, it will default there. Otherwise, it thinks, as most
distros think, that it needs to go on the MBR, which you need to correct. BM
can't start Linux directly. What it does is what Linux calls "chainloading",
transferring boot control to a partition on which a Linux bootloader lives.
You can set that up prior to Linux installation if you do the partitioning in
advance. If you try to test that you've done it right before the boot loader
is actually installed, you'll get a "partition is not formatted" message,
even if it is actually formatted for Linux.
Its kernels include HPFS support, but it will not properly configure
/etc/fstab to use them. You'll need to do that manually. Here's a line from
one of mine:
/dev/hda1 /hpfs/C hpfs noexec,case=asis,umask=0,ro,noauto
Note that if you set HPFS or MSDOS or VFAT to rw, Linux will do to them as it
does to its native partitions, and change the directory timestamp each time
any file within a directory is written. I keep only one OS/2 compatible
partition set to rw status to avoid unwanted directory timestamp changes.
"For God so loved the world that he gave