What transpired in the next few minutes was that /dev, /etc and /lib had also gone in their entirety; fortunately Neil had interrupted rm while it was somewhere down below /news, and /tmp, /usr and /users were all untouched.
Answers on a postage stamp to: Mario Wolczko, dept.
By yet another miracle of good fortune, the terminal from which the damage had been casino night hairstyles done was still su'd to root (su is in /bin, remember?Mark Forums Read, view Forum Leaders.So now we had a /etc, writable by all.Apart from the fact that nobody could login bin/login?How about recovery across Ethernet of any of this from another VAX?Or maybe make skeletal entries for /etc/passwd, /etc/hosts and so on, so that /usr/bin/ftp would work.Of Computer Science arpa: The University usenet: mcvax!And at the top of the screen I spied the following lines: # cd # rm -rf oh, shit, I thought.A strange error message of the form (I forget the exact details) "cannot access /foo/bar for userid 147" had been issued by msg.
If you followed a valid link, please notify the administrator, all times are GMT -8.
Alternatively, we could get the boot tape out and rebuild the root filesystem, but neither James nor Neil had done that before, and we weren't sure that the first thing to happen would be that the whole disk would be re-formatted, losing all our user.
Rational thought saved us from this one.
Not only had we lost /etc/restore, but all of the device entries for the tape deck had vanished.
I owe a debt of thanks to David Korn for making echo a built-in of his shell; needless to say, /bin, together with /bin/echo, had been deleted.Instantly, I guessed that something was amiss.(We take dumps of the user files every Thursday; by Murphy's Law this had to happen on a Wednesday).Of course /bin/mkdir had gone, and so had /bin/mv, so we couldn't rename /tmp to /etc.Off we set on our merry way, and within only an hour we had managed to concoct the dozen or so lines of assembler to create /etc.I can't remember what happened in the succeeding minutes; my memory is just a blur.He has some helpful hints for those who are not familiar with the process, noting that refrigerated fruit absorbs the gas more quickly than warm, and that considering the water content of the fruit is important when selecting what to carbonate.A few seconds thought (which as usual, lasted a couple of minutes) suggested that we write the binary on top of an already existing binary, owned by oblem solved.Who's userid 147?; the sender of the message, the destination, or what?Of course, some things can't stand life without say /etc/termcap, or /dev/kmem, or /etc/utmp, but by and large it all hangs together.