help installing too
Bill McBrine
Simon Cox <si...@rooster.sci.port.ac.uk> wrote:
>I get as far as mount /usr under /dev
>I put in the USR disk and specified /dev/fd0 to mount usr under, but it says
>unknown file system. Does the disc need to be a minix disc?
>Any help would be appreciated.
>
>Simon
Simon... you need to type fd0c if you have merged disks? This is for
1.44 disks that have pairs of USR's on them. Otherwise I guess fd0
alone should work...?
I also have a couple problems I hope someone could help me with in email.
I'm trying to install Minix 1.7.0/386 binaries. Not the VM version.
It's going onto a 65 Meg RLL drive, and the instdist script does seem
to break when it tries to make the fs on the disk after partitioning it.
I might be part'ing it wrong, but I've tried the 'm' key options that it
cycles through and it still doesn't work. I've tried using three partitions
that it cycles through (two small part's, then the remainder of the disk),
and also one large partition. I write it to the disk just fine, hit return
after that when "everything looks right" and boom it dies.
"please finish the name of the primary partition: /dev/" (I enter "hd0")
I then hit return since everything 'looks' fine.
Here, I'll enter what it says when it dies...
"Migrating to disk...
Usage: mkfs [-...] [-b ..] [-i..] special [proto]
Scanning /dev/hd0c for bad blocks...
/dev/hd0c is not readable
mount: No such file or directory
# "
And it breaks there. The script called "mkfs /dev/$usr" which translates
to /dev/hd0c, but mkfs doesn't like that, and if I manaully type
"mkfs /dev/hd0" I get ...
Unrecoverable write error on device 3/0 block 66559
Unrecoverable disk error on device 3/0 block 66559
mkfs: File system is too big for minor device
Now I know there are some bad blocks on the disk, but isn't it supposed to
get past these and what about the fs error it complained about?
I can't get past this part of the installation process.. Is the script
really broken or am I (more likely!) doing something wrong? The RLL
HD's architecture is 1024x5x26, so it shouldn't be the problem...
Thanks to anyone that can fix the problem! Also, any ftpable FAQ or FAQ-like
document (not just a features listing or other lite material) that would
help me learn more about Minix would be appreciated. I'm wanting to use
Minix on my private site for things such as a bbs with email and news and
some of my own development. I like it for its compactness and memory use
(or lack of memory use :-).
I have a 6 meg machine (with Not a ton of disk space) which I want to run
a *nix on, but I've had little success with Linux on this machine. I'd
like to try out Minix but not if I can't even install the thing. I'm also
curious about FreeBSD (or other *BSD), but I've heard that that is harder
on memory than even Linux... so any advice is also welcome. I'm probably
going to go and try out Linux again, and maybe FreeBSD if I hear better
things about it...
Thanks for your comments!!
l8r...
--
* Bill McBrine *** EMail: rag...@hakatac.almanac.bc.ca (other address pending)
Interests: Atari8bit. Tandy 6000 (i have 3.1) * bmcbrine@{this doesn't work!?}
Robotics. Amiga News & Devl's. Networking. Userfriendly Datamanagement Systems.
Disclaimer: I cannot be held accountable for my action or inaction...Can I?
Will Rose
: In article <4amsii$8...@hawk.ee.port.ac.uk>,
: "Migrating to disk...
The disk partitions are hd0 (the whole disk), hd1, hd2, hd3 and hd4
for the first disk, and hd5 (6, 7, 8, 9) for the second.
The subpartitions are hd1a, hd1b, hd1c, hd1d, etc.
hd0c won't exist - hd1c may exist, depending on whether subpartitions
have been installed on hd1. Minix expects by default to boot from
hd3 or (I think) subpartition c, but this is easily changed in the
boot monitor.
The other problem you may be running into is the RLL drive; you
could try using bios_wini if the driver seems off, but if you can
successfully partition the drive that's unlikely to be the case.