Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!noc.netcom.net!ix.netcom.com!howland.reston.ans.net!swrinde!cs.utexas.edu!uwm.edu!spool.mu.edu!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Two 2.0.5 questions Date: 1 Jun 1995 08:40:16 GMT Organization: University of California, Berkeley Lines: 26 Message-ID: <3qjudg$oab@agate.berkeley.edu> References: <3qj2eo$5ln@newshost.loc3.tandem.com> NNTP-Posting-Host: violet.berkeley.edu In article <3qj2eo$5ln@newshost.loc3.tandem.com>, mueller_scott <scott@tandem.com> wrote: >1 - I'm running 2.0R. I understand 2.0.5 has the "slice" code; does this >mean I can't use my current 2.0R partitions/fstab entries? Backing up to >300 floppies does not appeal to me... On the other arm, I'm planning to buy You can still use your current 2.0R stuff, though I recommend that you use a new root filesystem for 2.0.5R so that your /dev entries are properly created for the slice code. Basically, I would start fresh with a new / and /usr from 2.0.5 and use the (M)ount command to mount your old partitions. >2 - I encountered one each of libc and kernel bugs under 2.0R and sent pointers >in to bugs@freebsd.org. Is there a Changes file or similar that I can ftp >to see if fixes made it into 2.0.5, so I don't have to pull the full release >down and read the source? You can query our bugs database, though I'm not sure how to do this via mail at the moment - talk to Paul Richards: paul@freebsd.org. Or use the easier to use search engine at http://www.freebsd.org. We're working on improving the whole bugs tracking system substantially over the next few months, so if you totally draw a blank, don't hesitate to ask! Jordan