Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!mcsun!sun4nl!fwi.uva.nl!vdlinden From: vdlinden@fwi.uva.nl (Frank van der Linden) Newsgroups: comp.os.386bsd.misc Subject: Re: Status on discussed merge between NetBSD and FreeBSD Date: 15 Nov 1993 01:38:52 GMT Organization: FWI, University of Amsterdam Lines: 61 Distribution: world Message-ID: <2c6mjc$6bl@mail.fwi.uva.nl> References: <JKH.93Nov13222001.2@whisker.lotus.ie> <crt.753292942@tiamat.umd.umich.edu> <CGD.93Nov14085627@eden.CS.Berkeley.EDU> <CGIA2G.7qx@aib.com> NNTP-Posting-Host: carol.fwi.uva.nl dwex@aib.com (David E. Wexelblat) writes: >Now, normally, I try to stay out of this BSD-du-jour crap, but... So do I, but I'd like to react to this one. >NetBSD shared libraries for XFree86 do NOT work. At least, they don't >work for anything built with libXt, which is, oh, about 90% of the >applications. There have been at least 3 different attempts to get >shared libraries working right, but it's not there yet. Actually, I have been running shared libs with XFree 2.0 on NetBSD-current for some days now, works like a charm. Yep, there were problems with libXt in the beginning, but an update by Paul Kranenburg (great work!) to ld & ld.so has fixed this. It really works, no separate shared data libs too.. I've checked all clients that come with the stock XFree, they all work (am typing this right now in X, while the machine has been up for a day (simply because I switch it off every night :)), and compiling heavily in X the last hours). >and the alternate insanity of BSD-du-jour, I'll just stick to my >old-fashioned, expensive, but QUIET commercial operating system. Hmm, still, I'd rather pay nothing and have a bit of noise, than pay $2000 for silence 8-) But anyway: yeah, this is all getting to be a teeny weeny bit out of hand, isn't it. RFD: comp.os.386bsd.flame ? I wonder if this is a problem in free software: you want your code to be free, but somehow you don't like other people taking it just like that and making it part of their own stuff, without getting 'proper credit' (where 'proper credit' seems to be a hotly debated issue). Actually, I already wondered how long this 'access to eachothers source-trees' thing between Free/NetBSD was going to last, but it seems this has been answered now. Seems like *BSD has always suffered from disagreements from the start; it started off with Bill Jolitz leaving the original BSDI group because of differences with regards to commercialness. As far as I can remember, at least, it's all getting a bit fuzzy now. Now, where were the days when there was just a mailing list of people trying to make Net/2 work on a 386, even before 386bsd 0.0 was out.. I'm a happy NetBSD-current user at the moment, and I'll probably stick to that for a while, since it is the most interesting thing for me to work with, and interaction through the mailing lists on sun-lamp and the daily updates works really well. I'll ignore all the FlameBSD/EgoBSD stuff. Sure, I have my opinions on this, but I think there's a hole in my asbestos suit, so I don't really dare say much.. Though it makes some interesting reading on a rainy, stormy sunday night *grin* Peace and love (or anything that comes close to it), - Frank -- +----------------------------------------------------------------------------+ | I am not sure what a .signature is for, but my mom told me to make one. | | Frank van der Linden, vdlinden@fwi.uva.nl | +----------------------------------------------------------------------------+