Under -current /etc/host/hostname.* has been replaced by
	/etc/ifconfig.* - you probably want to rename hostname.ae0 :)
	(The format of ifconfig.* is different, but should ok unless
	you have any strange options)


		David/abs

  -- "Its hard to say it... I hate to say it... but its probably me..." --

On Wed, 20 Aug 1997, Edward Seth Miller wrote:

> 
> 
> On Wed, 20 Aug 1997, Colin Wood wrote:
> 
> > Edward Seth Miller wrote:
> > > 
> > > On Wed, 20 Aug 1997, Bill Studenmund wrote:
> > > 
> > > > > The problem is that it needs the dev that needs to be fsck-ed to be 
> > > > > specified; it doesn't just assume one like it used to.  The fstab appears 
> > > > > to be in good shape... it looks like:
> > > > 
> > > > [/etc/fstab]
> > > > 
> > > > > I'm assuming that the way it runs fsck at startup is essentially just 
> > > > > invoking fsck -f.  At least, the way it fails is about the same...  (It 
> > > > > says, "fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem ..." 
> > > > > instead of running.)
> > > > 
> > > > Actually it's fsck -p, when it should be fsck -p /
> > > 
> > > Okay...  Where can I find that, so that I can change it?  (This is 
> > > starting to annoy me...
> > 
> > It should be near the top of /etc/rc, but like Scott said, you should
> > probably upgrade your /etc directory to -current.  If you're going to do
> > this, be sure to untar it in some place non-destructive like /tmp.  Then
> > you can merge in any changes you've made before moving the files into the
> > /etc directory.
> 
> Great.  Found it.  Thanks, all.  Now, does anybody have any idea why my 
> ethernet has stopped working?
> 	I copied hosts, hostname.ae0, myname, mygate, resolv.conf, and 
> defaultdomain, but for whatever reason, my tcp/ip can't see anything 
> else.  My machine doesn't even respond to pings.  Under MacOS, OTOH, it 
> works fine.  I'm a bit confused...
> 
> 	-Seth Miller
>