*BSD News Article 54889


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!info.ucla.edu!agate!news.mindlink.net!uniserve!usenet
From: tom@uniserve.com (Tom Samplonius)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Linux vs FreeBSD
Date: 17 Nov 1995 06:57:41 GMT
Organization: UNIServe Online
Lines: 24
Distribution: world
Message-ID: <48hbp5$i3@atlas.uniserve.com>
References: <489kuu$rbo@pelican.cs.ucla.edu> <48aoee$j59@post.gsfc.nasa.gov> <30A9C704.5D0C6A5@FreeBSD.org> <DI37qp.Jyo@ritz.mordor.com>
NNTP-Posting-Host: pc.sdf.com
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
X-Newsreader: WinVN 0.99.6

In article <DI37qp.Jyo@ritz.mordor.com>, ritz@ritz.mordor.com says...
>
>
>Note, my experience has been that a noticeable portion of the ports
>are broken.  The pine/pico and tcsh ports come to mind.

  pine/pico broken?  That's surprising.  I just pkg_add'ed that one yesterday, 
and it works fine.

>This isn't really a complaint, just a point of information.  Turns
>out there were binaries available in the packages area.  I just
>prefer to build my own (when it's possible).

  pico/pine builds fine too.  I've done this many times.

>p.s.  For future reference, where does one send a port?  :)

  This could be the problem.... you don't know about the freebsd-ports list 
yet.  Use majordomo@freebsd.org and on it.

Tom

PS.  Chopped Newsgroups: down to appropiate groups.