From: kjb=731...@cs.vu.nl (Kees J Bot)
Subject: Re: make fdboot problem ??????
Date: 1999/05/08
Message-ID: <pqr0h7.7bp.ln@mega.am.cs.vu.nl>#1/1
X-Deja-AN: 475466441
References: <37326F69.290A4539@charlie.cns.iit.edu> <6l6ug7.cvo.ln@mega.am.cs.vu.nl> <3733B702.747B6070@charlie.cns.iit.edu>
Organization: One Minix-vmd system, it works!
Newsgroups: comp.os.minix

In article <3733B702.747B6...@charlie.cns.iit.edu>,
Dmitry Koshkin  <kosh...@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.)
-- 
Kees J. Bot, Systems Programmer, Sciences dept., Vrije Universiteit Amsterdam