*BSD News Article 91047


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!vbcnet-west!knews.uk0.vbc.net!vbcnet-gb!azure.xara.net!xara.net!dispatch.news.demon.net!demon!netcom.net.uk!ix.netcom.com!worldnet.att.net!cpk-news-hub1.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!news-xfer.netaxs.com!hammer.uoregon.edu!zephyr.texoma.net!uunet!in2.uu.net!165.254.2.53!nonexistent.com!not-for-mail
From: le@put.com (Louis Epstein)
Subject: Re: Upgrading 2.1.0 to 2.1.7 - how to?
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
X-Nntp-Posting-User: le
Organization: Putnam Internet Services
Message-ID: <E71JD9.LyH@nonexistent.com>
References: <5elbnc$l89@shellx.best.com> <5fbkre$9mf@uriah.heep.sax.de>
X-Trace: 858355532/22435
X-Nntp-Posting-Host: main.put.com
Date: Fri, 14 Mar 1997 16:05:33 GMT
Lines: 30
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37034

J Wunsch (j@uriah.heep.sax.de) wrote:
: le@put.com (Louis Epstein) wrote:
: 
: > : You gotta replace all of them.  It's probably the simplest way to just
: > : use the upgrade option of sysinstall -- but make sure you've got
: > : proper backups in place, in particular of your /etc directory.
: > 
: > Where would I put the backups?
: 
: On the tape drive where you put your nightly backups, too. ;-)

Hmm,a set of filees elsewhere on the HD would get wiped?
 
: If you're only concerned about /etc, that'll fit onto a floppy disk.
: 
: > My 2.1 kernel was recompiled for long user IDs,can the affected files
: > be patched back in to 2.1.7 or must the process be repeated?
: 
: I'm not sure what the affected files are.  I would probably repeat the
: process.  The good news: FreeBSD 3.0 will finally allow for longer
: usernames by default.

But it may be a year before there's a bugfixed stable 3.x...

: > (What improvements can be expected as a result of this upgrade?)
: 
: Security and other bug fixes mostly.

2.1.0 and 2.1.5 have the same security holes,at least,that 2.1.6
did,right?