I have encountered a very annoying behaviour of the editor ed (I HATE vi!).
It appears to function flawlessly while I am changing rc.conf and ttys. I
finally "w" the file (it reports the correct number of bytes written); then
I "q". A "ls -l" gives the correct number of bytes.

Then I reboot, to take advantage of the changes. On coming up again, either
in the minishell of the Installer or the regular system, the changed files
are empty! And I mean EMPTY - not just the changes lost, but the whole
d&*&* file! I finally got around it by editing these files outside of
netbsd and "cpin"ing them back in. I haven't had a chance to try ed since.

Is this unique to ed, or is it a system problem? Is it restricted to
nascent systems or is it a continuing problem? Anybody else so archaic as
to use ed?

Dan Killoran

______________________________________________________________________________
Got a device you would like to have run on the Mac? Call:
                 Daniel-the-Driver-Maker
      Fast service - accurate work - responsive support

         (Offer void wherever taxed or prohibited!)