trying to add openSuse 10.3 to this OS/2 box

trying to add openSuse 10.3 to this OS/2 box

Post by rafe » Tue, 19 Feb 2008 00:38:59

thanks for the previous guidance getting the CD distro on
alt.os.linux.suse -- please note this is being posted to OS/2 and Suse

been trying to install openSuse 10.3 on my main box without my success
the last few days.

the first attempt pretty much ended when the install routine found too
many partitions on my HD -- 18 -- and told me it couldn't deal with
more than 15, apparently because I'm using a SCSI disk.

so, I eliminated three partitions and started anew. unfortunately, I
was somewhat inebriated last night, only the first of several bad

basically I ran into trouble trying to choose advanced partitioning
for the installation.

to begin with, while I think I understand the Linux syntax for
designating partitions, whenever I actually encounter it I become
confused -- which is one reason when I thought I was choosing the last
1.5 GB partition for swap, I had actually picked my C: partition.

I just spent an hour this morning returning my HD to something like
its former state -- here is the output of FDISK (this morning I
combined last the two partitions I'd created for Suse)

Name Status Access FS Type MBytes
Startable : Primary BOOT MANAGER 7
None C: Logical HPFS 1506
4 Maint Bootable D: Logical HPFS 800
3 Maint Bootable E: Logical HPFS 706
None F: Logical HPFS 1506
None G: Logical FAT 203
None H: Logical HPFS 902
None I: Logical HPFS 1506
None J: Logical FAT 102
Warp4 Bootable K: Logical HPFS 800
None L: Logical HPFS 3004
None M: Logical HPFS 6314
None : Logical Type 83 17877

note there are no primary partitions, don't ask me why -- it hasn't
really been a problem, except it does seem to irritate FDISK, which
never fails to complain whenever I exit.

also -- when the installation sent me into the advanced partitioning
page, I noticed a few odd things: for one, all my HPFS and FAT
partitions were not so designated -- instead I think they were called
"Linux compatability" or something. on the other hand, I think in the
"Simple" page, it identified FAT as such and HPFS as hpfs/ntfs. I'm
mostly concerned about the Suse installation 1) keeping its hands to
itself and 2) giving me HPFS support out of the box.

finally, I can't seem to find a way to add the partition where I wish
to install Suse into OS/2's Boot Manager -- can anyone explain why?
my preference would be to use BM to start Suse, I'm not sure I have
that option. if that's the case, where should I put Suse's boot
loader, and how can I be sure that it's going to invoke Boot Manager,
and not blow it away as it seems to like to do as a rule?

trying to add openSuse 10.3 to this OS/2 box

Post by » Tue, 19 Feb 2008 00:53:28

On Sun, 17 Feb 2008 15:38:59 UTC, rafe < XXXX@XXXXX.COM >

Cutting everything. I just managed to add my OpenSUSE install, here's
how I did it.

First of all I used LVM from eCS 2 RC3 install program to create my
partition structure (circa 9 partitions/volumes), which includes one
volume for Windows XP (still don't have it, but just in case), two for
eCS (Italian and English versions), one for Solaris 10 (thanks Sun)
and another for a Linux flavor: choose OpenSuse, but seems it's not a
really itty-bitty good idea (seems to lack GCC: I tried to launch
"make" and received an error! Boh?)

After installing eCS I installed also Suse: YaST2 broke my Boot

Seems there's some conflict between eCS's BM and Grub from SUSE's
standard install, so after installing eCS and BM *and* Suse *and*
recreating BM (alas!), it's just a matter of restarting SUSE's desktop
from the install CD and reinstall Grub, this time making it load from
the SUSE volume. It works nice and clean now.



trying to add openSuse 10.3 to this OS/2 box

Post by rafe » Tue, 19 Feb 2008 01:02:51

no LVM here. what confuses me also is that OS/2's and Linux's LVM are
not the same -- in any case unless it's really necessary, I'd just as
soon not start up with it.

just one question: does Suse recognize your HPFS partitions out of the


trying to add openSuse 10.3 to this OS/2 box

Post by William L. » Tue, 19 Feb 2008 02:26:52


It, Suse 10.3, recognized only those volumes that were single partition
below some magic limit, 1024 cylinders? Since I had only one HPFS
partition that met that qualification, that was the only one available
to be mounted (it recognized the partitions of multipartition volumes,
but of course, not as volumes, which made them unreadable.). So, yes, I
did nothing to get HPFS recognized. BTW, it will install if there are
more than 15 partition existing. It offers to ignore the excess. You
can chose to install the development package and get Gcc.
Thanks a Million!

trying to add openSuse 10.3 to this OS/2 box

Post by Dave Ye » Tue, 19 Feb 2008 02:42:17


Never done Suse but the usual recommended way is to create the
partitions with the OS/2 fdisk, perhaps as FAT. Add the partition that
will be the Linux boot partition (/ or /boot depending on disk size) to
BM then using the advanced install only use the Linux fdisk to change
the partition type to 82 or 83 depending on whether ext2 or swap.
Then install the file system under Linux and install. Make sure grub or
LILO is installed to the Linux boot partition, not the MBR.
ps Mixing fdisks when partitioning is never a good idea due to different
bugs in them.

trying to add openSuse 10.3 to this OS/2 box

Post by Stan Goodm » Tue, 19 Feb 2008 04:09:39

afe wrote:

I installed openSuSE on the same drive as OS/2. It was not difficult. Of
course I was sober at the time.

DO NOT PARTITION WITH LINUX. Use either OS/2-LVM (compatibility partitions
only) or DFSee. You can use DFSee for setting partition types if you like.

Perhaps you forgot that your OS/2 Boot Manager (which IS a primary
partition, despite what you have said below) counts as a partition?

There is no reason why there MUST be as primary partition. But, as noted,
Boot Manager is occupying one.

HPFS is recognized out of the box. You can't get at them without first
mounting them.

Have the SuSE boot loader at /boot. Be carful, because left to its own
advices, the installation witll try to put it in the MBS. Use OS/2-LVM (or
DFSee) for making an entry for SuSE in Boot Manager.

If you stay sober, you can do it. Otherwise, unless you have a designated
operator, ....?

Stan Goodman
Qiryat Tiv'on

trying to add openSuse 10.3 to this OS/2 box

Post by » Thu, 21 Feb 2008 06:45:13

On Sun, 17 Feb 2008 16:02:51 UTC, rafe < XXXX@XXXXX.COM >

Yes, there are differences between the two LVM (damn IBM, will they
ever make something right other than OS/2?). I suggest you to go the
LVM way, it's way better than using the old fdisk.

Yes it does. And oh, btw I found why I lack GCC: my Suse distro comes
from a Linux fan magazine, it's a desktop distro only. Bad news,
though: what use is a Un*ix without development tools? :-(


trying to add openSuse 10.3 to this OS/2 box

Post by Felix Miat » Fri, 22 Feb 2008 16:29:25

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
release notes.

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
mount points.

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

trying to add openSuse 10.3 to this OS/2 box

Post by Richard Bu » Thu, 06 Mar 2008 05:22:55

How does SUSE or for that matter, any other 'UX do with rather large JFS volumes
made under OS/2? I set them up as the 4096 block size that's recommended, just
haven't had the time to try any LINUX distro's yet.

trying to add openSuse 10.3 to this OS/2 box

Post by Dave Ye » Thu, 06 Mar 2008 09:10:31


With Ubuntu I had to set permissions (using chmod) on the JFS volume
before I could access it as a normal user.

trying to add openSuse 10.3 to this OS/2 box

Post by William L. » Thu, 06 Mar 2008 10:54:16


As long as the volume is a single partition, it is as Dave says. Suse
seems to not understand LVM version 1 multi-partition volumes (or I
failed to do something that's required).
Thanks a Million!

trying to add openSuse 10.3 to this OS/2 box

Post by Richard Bu » Sat, 08 Mar 2008 03:19:14

Sounds like I'm all set then as both are single partitions on 1 big drive. Now
to just get the time to play...