Date: Tue, 25 Mar 2003 18:14:19 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Daniela <dgw@liwest.at> Cc: hackers@FreeBSD.ORG Subject: Re: Lots of kernel core dumps Message-ID: <20030325071418.GA16046@cirb503493.alcatel.com.au> In-Reply-To: <200303242018.43648.dgw@liwest.at> References: <200303212037.46322.dgw@liwest.at> <200303230010.38736.dgw@liwest.at> <200303231120.15652.wes@softweyr.com> <200303242018.43648.dgw@liwest.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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 security 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. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030325071418.GA16046>