Date: Sun, 6 Apr 1997 13:02:25 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 2.2.1-RELEASE still changing??? Message-ID: <199704061702.NAA00373@lakes.water.net>
next in thread | raw e-mail | index | archive | help
I've just ftp'd to ftp.freebsd.org to see if the XFree86 stuff has been rebuilt for 2.2.1-RELEASE (I don't believe there's been any "official" status on the utmp issues there.) However; I discovered that the compat21 and floppies as well as some other files have changed. This can be quite frustrating; as it takes me about two weeks to down-load all of 2.2.1 [that's 2.2.1-RELEASE, the packages, and XFree86...] Frequently things fail because of network problems (I believe at my end)... and have to be restarted. Or, the machine doing the download crashes... Then, of course, when things change I either have to determine exactly what changes (re: my frequent calls for CHECKSUM.MD5 files) and try to patch things together, or restart everything... Can we treat the "released" version as 'frozen' (albeit with potential bugs) and adopt a different approach to fixes. Something like: 2.2.1-RELEASE and then maybe 2.2.1-postRELEASE (or something else appropriate). That would give me, at least, a better shot at actually getting something... Another approach would be to announce these changes ahead of time; I could halt my down-loads then instead of discovering it after-the-fact. [Maybe they are announced, and I'm just on the wrong mailing list?] Of course, if I'm the only one affected; then forget about this... Finally, a sufficient answer could be "why don't you just wait for your CD-ROM in the mail?" (only problem here is the absence of DES.) - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704061702.NAA00373>