Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:11272 comp.os.386bsd.bugs:2293
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!library.ucla.edu!ihnp4.ucsd.edu!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!usenet.pa.dec.com!jkh
From: jkh@nx.ilo.dec.com (Jordan Hubbard)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs
Subject: Situation update on 1.1.5R [Was Re: FreeBSD 1.15R (Re: Suggestion for addition to FAQs)]
Date: 01 Jul 1994 14:41:39 GMT
Organization: Digital Equipment Corporation, Galway Ireland
Lines: 92
Message-ID: <JKH.94Jul1154139@nx.ilo.dec.com>
References: <16FE595EDS85.98022249@wsuvm1.csc.wsu.edu> <2v0cnq$k45@masala.cc.uh.edu>
NNTP-Posting-Host: nx.ilo.dec.com
In-reply-to: wjin@.uh.edu's message of 1 Jul 1994 06:22:50 GMT
In article <2v0cnq$k45@masala.cc.uh.edu> wjin@.uh.edu (Woody Jin) writes:
As someone said here, FreeBSD 1.1R must be the god of any free unices
around (maybe that it why they named it FreeBSD 8-) 8-) ).
Installation was a breeze from the beginning to the end
Gee, now that's the kind of feedback I live for! :-)
I really want to donate some money (just a small amount (since I am only
a poor grad student who has a wife and two kids) to express that I thank
the FreeBSD core team.
Could someone tell me how to do it ?
It's very kind of you to offer, but if you really are keen to make
such a donation I, for one, would be much happier to see it go to the
Free Software Foundation, or someone like the League for Programming
Freedom (who truly have ALL of our long-term interests at heart).
The FreeBSD group is, unfortunately, not well set up to deal with
donations, and receiving such things would only add additional
headache and misery in trying to figure out who best deserved it and,
once given, who'd get to be next in line for any subsequent donations
(which might never arrive). I think, for now, it's best that we stay
with our current all-volunteer-none-of-us-are-paid-for-this model.
Should we ever actually be set up with a larger and more official
organizational structure, I'll see what we can do about dealing with
donations. The offer is certainly appreciated!
BTW, some questions about the 1.15R
1) Why does sys part of the source distribution contain *.o files,
which increases the size almost twice ?
Because I'm a bonehead (sound of head smacking table). I had the
src tree cleaned, but this did not include the things in sys/compile.
Whoops! I'll fix it!
2) Where is the source for the secrdist ?
Good question! !?! Geeze.. Phoo! Somehow that got missed in
copying over the secrdist! It's sitting here in my build area, but it
didn't get over to freebsd.cdrom.com.. And now freebsd.cdrom.com is
down.. :-(
Ok, I've copied it onto the ~ftp/pub/BSD/FreeBSD/FreeBSD-1.1.5-RELEASE
tree on gatekeeper.dec.com. When freebsd.cdrom.com comes back up,
I'll copy this into the archive copy as well. Sorry about that, and
thanks to Woody for reporting it!
I'm sorry for these boners folks, 1.1.5R is my first run through the
release process and I'm just now seeing where some of the pitfalls lie
(e.g. it's not all as automated as I'd thought we had it! :-( ).
I'm now in the process of rolling a 1.1.5.1 release that corrects ALL
the problems reported so far. This will be purely a "convenience"
release since I'll also show the 2 or 3 (small) things that need to be
done to bring 1.1.5R up to the same point. 1.1.5 users will NOT have
to grab 1.1.5.1R, I'll simply be providing it for the benefit of those
people who have NOT grabbed 1.1.5R yet!
Just to run through the current "bug list" for the benefit of those
here, here's what's been found in 1.1.5R so far that I intend to
correct with the updated release:
1. Things were build with a dependency on libcrypt by default.
This will be fixed in 1.1.5.1R. 1.1.5R users can fix this
by simply installing the secrdist (non-US users should see the
FAQ entry on where to get their own non-US copy).
2. The filesystem floppy didn't have device entries for wd1, making
installations onto the second drive fail for IDE drives (it works
for SCSI drives, which were my test case :-( ). 1.1.5R users
wishing to install under these circumstances have no easy
work-around, except to patch the filesystem floppy! :(
3. The /sys/compile/GENERIC* kernel files got left in the srcdist
sys.* files. This has been eliminated.
4. A potentially destabilizing change to the Wangtek driver has been
backed out. This should affect few people, if any, but while I'm
being conservative.. 1.1.5R users will find a patch file in the
new release for this change and the changes I had to make to
etc/Makefile to fix problems 1-3.
As you can see, none of these problems are very severe, and will
probably not even effect most people, but I feel it important to
be thorough!
Regards,
Jordan