Subject: Re: Panic shutting down
To: Chris G Demetriou <Chris_G_Demetriou@BALVENIE.PDL.CS.CMU.EDU>
From: David Brownlee <D.K.Brownlee@city.ac.uk>
List: current-users
Date: 09/14/1995 10:28:19
If MAKEDEV hasn't changed (or the nodes it creates) .. I dont run it -
I've found this a fair comprimise :)
David/abs
D.K.Brownlee@city.ac.uk (MIME) +44 171 477 8186 {post,host}master (abs)
Network Analyst, UCS, City University, Northampton Square, London EC1V 0HB.
<<< Monochrome - Largest UK Internet BBS - telnet mono.org >>>
>=- Microsoft: Abort and Retry Cancel -or- NetBSD: http://www.netbsd.org -=<
On Wed, 13 Sep 1995, Chris G Demetriou wrote:
> > > moving 'init' doesn't fix the bug, it just makes it harder to trigger.
> > >
> > But if I trigger it every time I update my -current, doesn't it make
> > sense to put a fix into the init install & append a note to a pr that
> > the fix will go away when the real problem is fixed.
> > (Sorry, I just dont like corrupting my disk :)
>
> or, better yet, #ifdef out the unmounting/clean-marking, so that the
> code is always 'safe,' and note that the #ifdef will be removed when
> the code is fixed.
>
> if you update your -current system _completely_, wouldn't you also make
> new device nodes (which will trigger the problem, too)?
>
>
>
>
> chris
>