*BSD News Article 80376


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!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!howland.erols.net!newsfeed.internetmci.com!in1.uu.net!news2.new-york.net!main.put.com!not-for-mail
From: le@put.com (Louis Epstein)
Subject: FBSD Future...
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
X-Nntp-Posting-User: le
Lines: 20
Organization: Putnam Internet Services
Message-ID: <Dz37x9.7vC@news2.new-york.net>
X-Trace: 844997084/8391
X-Nntp-Posting-Host: main.put.com
Date: Fri, 11 Oct 1996 01:24:45 GMT

Well,I see that the expected release of 2.2 has been pushed back from
late summer '96 to first quarter '97,quite a jump,and I wonder what
more there is to it past Walnut Creek's desire to keep the CDROMs
semi-annual.

I gather that 2.1.6 will be released on the net only,not on CDROM,so
how would one handle an upgrade from 2.1?(No point in going to
2.1.5 first if 2.1.6 is coming).How long would I have to take my
ISP down to go to 2.1.6,and get it in shape to honor the 9-12 character
IDs enabled by a kernel recompile for my 2.1??And what would I actually
gain by so doing?

Which SNAPs of 2.2 will be on the CDROM for SNAP subscribers?
501 was,626 wasn't,were 801 and 1006?

For a got-to-stay-up business like an ISP,it might be better to wait
for a 2.2.x after 2.2R gets its bug reports dealt with...I guess
the first such release is at least 9 months off.

(64-bit 3.x is presumably years away still).