Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!pasteur!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bbn!rochester!ritcv!cci632!ccicpg!felix!zemon
From: fuat@cunixc.columbia.edu (Fuat C. Baran)
Newsgroups: comp.unix.ultrix
Subject: /etc/init -> /bin/init
Message-ID: <27815@felix.UUCP>
Date: 5 Apr 88 22:12:00 GMT
Sender: zemon@felix.UUCP
Reply-To: fuat@cunixc.columbia.edu (Fuat C. Baran)
Organization: Columbia University Center for Computing Activities
Lines: 27
Approved: zemon@felix.UUCP
Reply-Path:




Does anyone know why DEC decided to move /etc/init to /bin/init in
Ultrix 2.2?  I didn't run across this in the release notes or anywhere
else.  We tried booting a 2.2 /vmunix on a 2.0 filesystem, and it hung
after the autosizer output.  We were wondering what might be causing
that and decided to cmp init, and that's when we noticed the init had
moved... Linking /etc/init to /bin/init solved that problem.  Of
course /etc/mount, /etc/umount, etc. don't work right since the getmnt
system call seems to have been changed.  (This wasn't in the release
notes either...)

Seems like DEC thinks that when you upgrade from one release to
another you should just totally blank out all your disks.  They don't
even bother to completely document what the changes are, so its trial
and error trying to put your system back to the way it was...


					--Fuat Baran
					  Academic Systems Group


-- 
ARPANET: fuat@columbia.edu           U.S. MAIL: Columbia University
BITNET:  fuat@cunixc.columbia.edu               Center for Computing Activities
USENET:  ...!rutgers!columbia!cunixc!fuat       712 Watson Labs, 612 W115th St.
PHONE:   (212) 280-5128                         New York, NY 10025