Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!gatech!destroyer!caen!umeecs!dip.eecs.umich.edu!dmuntz From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz) Subject: Re: 386bsd-0.1 Message-ID: <1992Jul27.165321.13424@zip.eecs.umich.edu> Keywords: 386bsd Sender: news@zip.eecs.umich.edu (Mr. News) Organization: University of Michigan EECS Dept., Ann Arbor References: <cproto.712235554@marsh> Date: Mon, 27 Jul 1992 16:53:21 GMT Lines: 29 In article <cproto.712235554@marsh> cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes: >Hi there, > >after running 386bsd-0.0 since march, 0.1 has not much to offer. Here >is a list of problems, the first is really a showstopper: > >2 - if fsck fails at the second partition, init continues rather then >reboot You only need to reboot if fsck fails on the root partition. > >3 - the com driver looses characters (0.0 hasn't) Get the new com.c (I believe it is at agate, but check past postings). > >5 - pccons.c driver delays entered characters until the next char is >typed (sometimes) (0.0 hasn't) I haven't seen this and I've been using 0.1 quite a bit. > >6 - cp is stupid in single user mode ???? (0.0 wasn't) 0.0 was also (along with mv and possibly rm) -Dan