Date: Fri, 10 Jan 1997 21:08:40 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: curt@zxcv-pc.jumpnet.com (Curt Finch) Cc: bugs@freebsd.org, questions@freebsd.org Subject: Re: python problems on freebsd (fwd) Message-ID: <Mutt.19970110210840.j@uriah.heep.sax.de> In-Reply-To: <Pine.BSD.3.95.970110064805.13685B-100000@zxcv-pc.jumpnet.com>; from Curt Finch on Jan 10, 1997 06:48:56 -0600 References: <Pine.BSD.3.95.970110064805.13685B-100000@zxcv-pc.jumpnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Curt Finch wrote: > ---------- Forwarded message ---------- > From: Stephen Robert Norris <srn@flibble.cs.su.oz.au> > Curt Finch wrote: > > > > it's just the sed distributed w/ freebsd, i'm sure it's fine > > i'll work on it and send out the real answer when i find it > > > > thanx for your input > > It isn't. Use GNU sed. I had exactly the same problem on a clients > FreeBSD box, and using GNU sed fixed it completely. > > I wonder why FreeBSD has a broken sed? Because nobody reported a problem with it yet? Not really. Please, either report your problem for verification, or check the most recent version. Several bugs have been fixed between 2.1.5 and 2.1.6, and later on. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970110210840.j>