Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!mandrill!hal!ncoast!allbery
From: allbery@ncoast.UUCP
Newsgroups: comp.os.minix
Subject: Mount problem solved, and incompatibility with V7
Message-ID: <4275@ncoast.UUCP>
Date: Wed, 26-Aug-87 20:48:58 EDT
Article-I.D.: ncoast.4275
Posted: Wed Aug 26 20:48:58 1987
Date-Received: Sat, 29-Aug-87 15:35:17 EDT
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 23

Well, my mount problem has been solved.  Since this is an incompatibility
with V7 Un*x, I am considering it a bug.  To wit:

if the inode to be mounted on is in use, the mount fails.

As it turns out, /etc/update is opening "often-used" inodes in order to keep
them in memory for fast lookup.  The list of opened inodes includes /tmp.
While I understand this, I don't understand why it would preclude my using
/tmp as a mount point.  (It is also redundant if I mount something else on
/tmp, since that should load the root inode into memory anyway.)

Plexus Sys3 used a program /etc/openup to do this; this also allowed a
list of directories/files/devices to be changed without recompiling
/etc/update.  (Yes, devices. "/etc/openup -rw /dev/tty3; stty 9600 < /dev/tty3"
is a handy way to insure that your serial printer always works as expected.)
May I suggest something similar in Minix to replace /etc/update doing this?
-- 
	    Brandon S. Allbery, moderator of comp.sources.misc
  {{harvard,mit-eddie}!necntc,well!hoptoad,sun!mandrill!hal}!ncoast!allbery
ARPA: necntc!ncoast!allbery@harvard.harvard.edu  Fido: 157/502  MCI: BALLBERY
   <<ncoast Public Access UNIX: +1 216 781 6201 24hrs. 300/1200/2400 baud>>
** Site "cwruecmp" has changed its name to "mandrill".  Please re-address **
*** all mail to ncoast to pass through "mandrill" instead of "cwruecmp". ***