Groovy hepcat jjge was jivin' in alt.os.linux.slackware on Thu, 16 Aug
2018 3:50 pm. It's a cool scene! Dig it.
Post by jjge
Post by Peter "Shaggy" Haywood
There's no such thing as "Linux 7". Do you mean Slackware 7?
I stand corrected. Yes. I use it occasionally to run the last
available WordPerfect, under a now-defunct libc version.
Post by Peter "Shaggy" Haywood Post by jjge
format the HD, and I made an MSDOS files system and a swap file.
Why use that filesystem? You could use umsdos, of course, but I never
saw the point. It should be ext2, IMHO.
Having now tried out this distro on a machine with 2 hard drives but
without any free space for a new partition on either of them, I now see
the point of UMSDOS. :) Yuck, though!
Post by jjge
Well, I tried almost all possibilities, including ext2.
That's odd. I've had no problem using ext2.
Post by jjge Post by Peter "Shaggy" Haywood
Of course, you should remember that the early version of ext2 in
kernel 1.0.9 doesn't support all the options that ext2 in the 2.6
series (as in Slackware 7) supports; and I don't just mean
journaling. Sou you should look up the mkfs.ext2 man page, especially
the -O (that's a capital o) option. I don't know what options are not
supported by 1.0.9, but you could probably google it, I suppose.
Post by jjge
However, mount /dev/hda1 /mnt is refused with the message "wrong fs
type, /dev/hda1 already mounted, /mnt busy or other error."
Elsewhere in this thread you mentioned you were trying to mount it
with msdos instead of umsdos, but even when you changed that it still
didn't work. Sorry! I can't help with that. I've never used umsdos.
Is it possible that the version of mount you're using doesn't support
(u)msdos? No, of course the umsds144.img should do it. It was just a
Post by jjge
So, the thing seems to work at least basically, but is not very
useful yet. And at this stage, it seems that I am stuck. Does anyone
have an idea to proceed?
The Linux version is 1.0.9
So, the Slackware version would be, according to Wikipedia, 2.0,
right? I'm downloading it now to try it out. I'll try it with qemu
and let you know how it goes in a few days.
I've now tried out Slackware 2.0.0 on a qemu virtual system as well as
on an old 486 (which has several other Linux distros, including a
couple of other versions of Slackware, as well as DOS). I've
encountered several problems in both cases. On both systems I've had
trouble getting the CD-ROM drive recognised. I've worked around this in
qemu, after trying many other things, by setting up the CD-ROM image as
a hard drive and, in the guest OS, mounting the whole disk (not a
partition). But on the 486 Slack 2 still can't get to grips with the
IDE CD drive. Part of the problem may be that it doesn't recognise the
second IDE controller. I'll try temporarily removing the second hard
drive and putting the CD-ROM on the first IDE controller. But I still
doubt that it will work. :(
On the 486, networking worked straight out of the box. The 3com509 ISA
NIC was recognised and functioned fine. Pinging other computers worked
perfectly. I still haven't tried other networking functions (like
accessing NFS shares, transfering files, ssh, etc.), but I'll have a
look at that stuff later.
On the qemu virtual machine, however, networking has so far been a
bust! The few network cards virtualised by this qemu installation don't
seem to be supported by Linux 1.0.9 or 1.1.18. I may have to do what
I've done in the past for various reasons: compile qemu myself,
enabling more network drivers.
As I stated above, I've used UMSDOS to install Slack 2 on the 486. I
could have set up a new partition for it by resizing and shuffling
around some other partitions. But I didn't relish that, actually. I
could've installed a third hard drive; but the ancient kernel seems to
have trouble recognising more than 2 IDE drives, and in fact it
couldn't even see the second hard drive on this machine! Oy! :) Perhaps
all it needs is a couple of "hd=" kernel options. I'll try that later.
I might see if I can find space for a new partition on my 386. For
networking it has a 3com503, which should work. And using ext2 instead
of UMSDOS might not grate so much. There's just something
not-quite-right about UMSDOS.
Compiling the kernel, even the 1.1.18 version, was quick, relatively
painless (except when I enabled certain drivers which wouldn't compile
for some reason) and straight-forward. The compiled kernel works fine.
Installing lilo on the virtual machine failed. I still don't know why.
It just wouldn't boot. I don't like lilo anyhow. I installed grub 0.95
instead. Actually, grub didn't work on Slack 2, possibly because it's
an ELF binary and unsupported by the old kernel. What I had to do was
boot another Linux virtual machine with the Slack 2 disk image as
second drive, and use that to install grub. That worked, and now the
system is bootable.
On the 486 I didn't want to screw up the existing boot loader (also
grub 0.95), so opted not to install lilo at all. I
updated /boot/grub/menu.lst to include an entry for the new system, and
bing - bang - boom, it worked perfectly!
Anyhow, these have been my experiences so far with Slackware 2.0.0.
More experimentation is to come.
Anyhow, as to your original problem, that of not finding the fdisk
binary; on both systems on which I've tried Slackware 2.0.0 the install
disks both had fdisk. No problem there!
But with UMSDOS do you really need to use fdisk? Since you're
installing into a DOS directory on an existing partition, you don't
really need to create a new partition, do you? Or do you for some
----- Dig the NEW and IMPROVED news sig!! -----
-------------- Shaggy was here! ---------------
Ain't I'm a dawg!!