From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 26 10:38:25 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B777537B404 for ; Wed, 26 Mar 2003 10:38:25 -0800 (PST) Received: from lilzcluster.liwest.at (lilzclust02.liwest.at [212.33.55.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2939A43FB1 for ; Wed, 26 Mar 2003 10:38:24 -0800 (PST) (envelope-from dgw@liwest.at) Received: from CM58-27.liwest.at by lilzcluster.liwest.at (8.10.2/1.1.2.11/08Jun01-1123AM) id h2QIc3m0001124636; Wed, 26 Mar 2003 19:38:11 +0100 (MET) Content-Type: text/plain; charset="iso-8859-1" From: Daniela To: Peter Jeremy Date: Wed, 26 Mar 2003 19:36:13 +0100 User-Agent: KMail/1.4.3 References: <200303212037.46322.dgw@liwest.at> <200303242018.43648.dgw@liwest.at> <20030325071418.GA16046@cirb503493.alcatel.com.au> In-Reply-To: <20030325071418.GA16046@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303261936.13694.dgw@liwest.at> X-Spam-Status: No, hits=-31.9 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: hackers@FreeBSD.ORG Subject: Re: Lots of kernel core dumps X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 18:38:29 -0000 On Tuesday 25 March 2003 08:14, Peter Jeremy wrote: > On Mon, Mar 24, 2003 at 08:18:43PM +0100, Daniela wrote: > >Well, it's just a home server. I don't mind a few crashes, but securit= y is > >important for me. What do you think, should I go back to -stable? > > If you're willing to put up with a few crashes _and_ assist with > debugging the crashes (eg trying patches) then running -CURRENT would > help the Project. One option you could try is to stick with -CURRENT > for a month or two and see how it pans out - if you feel it's too > painful, downgrade to -STABLE. (I ran -CURRENT on my main workstation > for about 3 years - I dropped back to -STABLE midway through last year > because -CURRENT happened to strike an extended period of instability > and it was causing me too much angst). > > On the topic of security, you should be aware that -CURRENT is not > officially supported and therefore isn't mentioned in security > advisories - in general -CURRENT will have security patches applied > before -STABLE but you will need to do some detective work if you > want to identify the exact time/revision affected. There have also > been a couple of instances where security problems only affected > -CURRENT. In short, if I keep my eyes open, security isn't bad, right? I'll give -current a try, thanks for your advice. Daniela