Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!mcsun!unido!ira.uka.de!rusmv1!wega!allrutz
From: allrutz@wega.tat.physik.uni-tuebingen.de (Ralf Allrutz)
Newsgroups: comp.os.minix
Subject: Minix-ST: problems with mg (microGnuEmacs)
Message-ID: <allrutz.677263910@wega>
Date: 18 Jun 91 16:51:50 GMT
Sender: news@rusmv1.rus.uni-stuttgart.de (USENET News System)
Organization: Comp.Center (RUS) U of Stuttgart, FRG
Lines: 27

Dear MINIXers,

I just found some strange behaviour in 'mg' (microGnuEmacs), but I don't
know yet, if it's a MINIX- or a mg-problem. The facts: 'mg world.c'
yields '(New file)', typing some characters, then ^X^C yields 'Cannot open
file for writing'. ... Just curious, I tried 'mined' which does exactly
what it is designed to do. Looking at the buffer window in 'mg' I find
a very strange pathname for world.c: /src/world.c instead of /usr/src/world.c.
Now here is my mount table:
/dev/hd2 is mounted on /usr
/dev/hd5 is mounted on /usr/src
/dev/ram is root device
When /dev/hd5 is mounted on /user, 'mg' works fine, but if the mount point
is in another mounted filesystem, 'mg' seems to track the pathnames only
up to the mount point, assuming it to be the root directory. The problem
vanishes if I use the absolute pathname of the file (mg /usr/src/world.c).

Any ideas ?

Ralf Allrutz

========================================================================
Lehrstuhl fuer theoretische Astrophysik
Universitaet Tuebingen
Auf der Mogenstelle 10
D-7400 Tuebingen
========================================================================