make fdboot problem ??????
Dmitry Koshkin
First: general information
I have successfully running Minix system on a computer with special
small HD for it.
I can do needed work with compiling kernel and making fdboot.
BUT:
I tryied to install Minix on the THREE computers and it worked but
during
make fdboot
I got:
#make fdboot /dev/fd0
/dev/fd0 is read-write mounted on /mnt
/dev/fdo unmounted from /mnt
/usr/mdec/bootblock and 2 addresses to boot patched into /dev/fd0
dd: cannot open unknown ???????????
make: Error code 256 ???????????
What is common for all computers:
1) I could compile library and kernel
2) All of them have WinNT 4.0
3) All HD are 4-6 GBt, and Minix is located upper then 1 GBt,
4) All computer have RAM 128 kBt.
5) I tryed to assign a different HD space for Minix: from 30 MBt to 500
Mbt
with the same result.
6) Two of the computer are the same Desktop, One is Laptop.
If anyone can give me advice, explanation, possible resolving this
problem,
or just opinion It will be greatly appreciated.
I am wayting an advice.
Thanks
Dmitry.
Kees J Bot
Dmitry Koshkin <kos...@charlie.cns.iit.edu> wrote:
>
>/dev/fdo unmounted from /mnt
>/usr/mdec/bootblock and 2 addresses to boot patched into /dev/fd0
>dd: cannot open unknown ???????????
>make: Error code 256 ???????????
It looks like /etc/fstab is not correct on that machine. One look at
the fstabs of your other Minix installations should tell you how to
change it.
--
Kees J. Bot, Systems Programmer, Sciences dept., Vrije Universiteit Amsterdam
Minix: http://www.cs.vu.nl/pub/minix/ ftp://ftp.cs.vu.nl/pub/minix/
Minix-vmd: http://www.Minix-vmd.org/ ftp://ftp.Minix-vmd.org/
Dmitry Koshkin
all
old and wrong setting appears again.
What part of the program rewrite all values back?
Dmitry
Kees J Bot
Dmitry Koshkin <kos...@charlie.cns.iit.edu> wrote:
>Thanks, It really helped. But after changing this file after rebooting
>all
>old and wrong setting appears again.
You must using a RAM disk for the root partition.
>What part of the program rewrite all values back?
One does that by hand, I'am afraid. This would do it:
-- First fix /etc/fstab
M root -- See 'man M'
cp /etc/fstab /root/etc/fstab
U root
The best thing to do is to use the hard disk partition directly instead
of the RAM disk. Boot your system, get to the boot monitor prompt (ESC)
and change 'rootdev' to be the same as 'ramimagedev'.
If I remember correctly you are running Minix on a 286, so it is nice to
use the RAM disk as a disk cache. Set 'ramsize=512' to enable this.
Don't forget to type 'save'. (On a 386 one would set the disk buffer
cache to 1024 and not use the RAM disk at all.)
With these changes the system should run better than it does now, and
you don't have the volatile root file system problem anymore.
(You may not know the word "volatile", and I found out that I really
didn't know it either. <URL:http://www.m-w.com/netdict.htm> showed
several meanings that are new to me (2, 3, and 4). That's what you
get when you learn English from technical geeks.)
Will Rose
[...]
: With these changes the system should run better than it does now, and
: you don't have the volatile root file system problem anymore.
This is not always a problem. Every so often, generally during maintenance,
I find it quite useful to be able to add miscellaneous files to my /bin
directory and get the original back on reboot.
Dmitry
Dmitry.
Kees J Bot
>Kees J Bot <kjb=731...@cs.vu.nl> wrote:
>[...]
>: With these changes the system should run better than it does now, and
>: you don't have the volatile root file system problem anymore.
>
>This is not always a problem. Every so often, generally during maintenance,
>I find it quite useful to be able to add miscellaneous files to my /bin
>directory and get the original back on reboot.
That's true. Just this morning I copied a Minix system from one disk to
another while running from the RAM disk with /usr mounted read-only.
That way you can copy a partition raw (cp /dev/xxx /dev/yyy) as I did in
this case, or you can copy the root partition more easily because you
can mount it on /root, the new root on /mnt and 'cpdir /root /mnt' to
copy one to the other.
Alexander Klietz
pqr0h7...@mega.am.cs.vu.nl...
> If I remember correctly you are running Minix on a 286, so it is nice to
> use the RAM disk as a disk cache. Set 'ramsize=512' to enable this.
> Don't forget to type 'save'. (On a 386 one would set the disk buffer
> cache to 1024 and not use the RAM disk at all.)
>
> you don't have the volatile root file system problem anymore.
Is it recommended in general for a 286 system to set 'ramsize=512'? Mine has
only 1MB of RAM. And: I'm just taking my first steps.
I have done a new install (second one) of Minix 2.0.0 (16bit) and have set
rootdev to the same value as ramimagedev (=bootdev). So I was able to do
installation without using tinyroot and tinyusr (well, it's all in the
usage(8) pages, I just haven't noticed it properly when installing first
time). When prompted, I set memory size to 1024 KBytes.
Now, when booting from harddisk, the settings are:
rootdev = hd2a
ramimagedev = hd2a
ramsize = (0)
memsize = (640)
emssize = (384)
According to the monitor(8) page it should be different by default. Is is
better to change the RAM disk value? I thought I have to be sparing with my
memory.
If have not read all of the man pages by now, I know I should :-) So if it
is mentioned somewhere, please give me a tip.
Regards
Alexander Klietz
"In order to confuse and obfuscate the public, we utilize substantial
technical jargon"
The SETI@home Sky Survey
Kees J Bot
Alexander Klietz <alex....@t-online.de> wrote:
>
>Is it recommended in general for a 286 system to set 'ramsize=512'? Mine has
>only 1MB of RAM. And: I'm just taking my first steps.
Only 'ramsize=512' is enough to hold all the compiler passes for a
'cc -c'. Less memory will help a bit in other cases, but you can't
spare any memory on a 1M machine, so don't even bother.
>When prompted, I set memory size to 1024 KBytes.
The reason the setup asks that question is to compute 'ramsize'. See
the horrible shell code at the end of commands/scripts/setup.sh. The
Minix kernel knows how much memory there is, but there is no way yet to
query this in user space, so that's why the question is asked.
>Now, when booting from harddisk, the settings are:
>
>ramsize = (0)
>
>According to the monitor(8) page it should be different by default. Is is
>better to change the RAM disk value? I thought I have to be sparing with my
>memory.
The settings are fine, no need to tinker with them. The description of
ramsize is a bit confusing thanks to it dual nature. Ramsize either
tells FS to stretch the "root in RAM" file system to that size, or it
tells the size of the RAM disk if root is not in the RAM disk. FS uses
an unused RAM disk as a cache until a user program touches it (mkfs).
>If have not read all of the man pages by now, I know I should :-) So if it
>is mentioned somewhere, please give me a tip.
It is mentioned in the "Lots of memory on a 286" section in the usage
manual. The advise is a bit open ended, a "try it and see if you like
it" kind of advise. If you run 2.0.2 then config(8) also says something
on this under the ENABLE_CACHE2 explanation. Config(8) is 90% useful
for 2.0.0 as well, so read
<URL:http://www.cs.vu.nl/pub/minix/2.0.2/wwwman/man8/config.8.html>
if you have 2.0.0.