Date: Wed, 22 Mar 2006 22:19:46 +0100 From: =?UTF-8?B?RXJpayBOw7hyZ2FhcmQ=?= <norgaard@locolomo.org> To: Kris Kennaway <kris@obsecurity.org> Cc: "Marc G. Fournier" <scrappy@hub.org>, rakhesh@rakhesh.com, freebsd-questions@freebsd.org Subject: Re: 6.1-BETA 4 stable for normal use? Message-ID: <4421BF72.50407@locolomo.org> In-Reply-To: <20060322210010.GA26879@xor.obsecurity.org> References: <20060322050432.7801.qmail@web54512.mail.yahoo.com> <4421119C.1050002@locolomo.org> <20060322160052.E1178@ganymede.hub.org> <4421B9C6.10401@locolomo.org> <20060322210010.GA26879@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Wed, Mar 22, 2006 at 09:55:34PM +0100, Erik N?rgaard wrote: >> Marc G. Fournier wrote: >>>> I am using 6.1-PRERELEASE which has actually been upgraded from >>>> 6.1-BETA3. The system as such is stable, but there are some nuisances. >>>> These are not fatal in any way but may cause confusion. So in >>>> particular if you're new to FreeBSD, better stay with 6.0. >>> Like ... ? >> Well, I have another machine at work which for some yet unknown reason >> requires me to reload the pf rule set in order to fetch - I posted on >> that last week. >> >> And I have minor errors like when I run "man pf.conf" and exit the >> man-page then I get this error: >> >> col: write error >> grotty:<standard input> (<standard input>):31713:fatal error: output error > > Did you file PRs? If not, and you only posted to this list, your > emails did not reach any of the relevant people. No, I need to investigate more and ensure me that it has not been a passing error. For example, the mentioned problem with pf, I first thougt it was a misconfiguration problem that fetch didn't use passive ftp, in which case this was the right forum. Then by accident I discovered that reloading the ruleset solved the problem. Rebooting, I would have the problem again until a new reload of the ruleset. I then tried at home to repeat on a different machine which had been updated almost at the same time but without luck. So, I there may be some error in updating or that very snap I got. In any case I need to investigate that more. And the other error, I have now tried and found that it appears only in Eterm, not in xterm or on the console. It may have been introduced as the ports version is now 0.9.3_4. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4421BF72.50407>