NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/sys/amiga/misc/20637

Internet Message Format | 1993-01-28 | 1.6 KB

Path: sparky!uunet!europa.eng.gtefsd.com!emory!sol.ctr.columbia.edu!ira.uka.de!fauern!rz.uni-passau.de!forwiss.uni-passau.de!ramsch
From: [e-mail] (Martin Ramsch)
Newsgroups: comp.sys.amiga.misc
Subject: Re: MakeLink
Followup-To: comp.sys.amiga.misc
Date: 26 Jan 1993 10:20:23 GMT
Organization: University of Passau, Germany
Lines: 34
Distribution: world
Message-ID: <[e-mail]>
References: <[e-mail]>
NNTP-Posting-Host: aragorn.forwiss.uni-passau.de

In article <[e-mail]>, [e-mail] (Ross Smith) writes:
|> [...]
|> When I do a dir, both files appear, and when I type them, Bravo now has the
|> same text as Alpha. Looks OK so far.
|>
|> *But*, when I use an editor to change the text in Alpha, Bravo remains
|> unchanged! As far as I can see, the "MakeLink" command isn't doing what it's
|> advertised to do, it's just doing a simple copy. You get two completely
|> separate files, with no link between them at all.
|>
|> What's going on?

Hi,

I guess, the MakeLink command works right. I myselfuse (hard-)links
extensivly without problems :-)

But your editor might be the malefactor. Some editors do not save
over the old file (this would overwrite the common content of the
original file and all its links), but rename the old file as backup
copy and produce a entirely new file with the given file name.
So the links point to the OLD renamed file, that may have been moved
to t:, or become real files, if their 'parent' file gets deleted.

--
Froehlich gruessend

 _ // Martin Ramsch
 \X/  [e-mail]