From owner-freebsd-current@FreeBSD.ORG Thu Dec 22 09:08:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17E9416A41F for ; Thu, 22 Dec 2005 09:08:08 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C6B143D5E for ; Thu, 22 Dec 2005 09:08:05 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: by nproxy.gmail.com with SMTP id l24so123399nfc for ; Thu, 22 Dec 2005 01:08:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E3Ei0Q4L2/OeEHyuLIVsm3uFX6h5ybT1VYD1MX1Iqo+bXUIdWHeZw0pnmNIcs8IcDiNGdiyCrumWBPB9/wXVrwROLSN4BiEm9xLhnHYpIAw/JzcGqmN1FLGvs8RY4n9AHlAYcFoHAJc7+R9f3P9c5HCoRk/sheYEKFSpULeAAwc= Received: by 10.48.250.8 with SMTP id x8mr77928nfh; Thu, 22 Dec 2005 01:08:04 -0800 (PST) Received: by 10.48.215.13 with HTTP; Thu, 22 Dec 2005 01:08:04 -0800 (PST) Message-ID: <5fbf03c20512220108o72912108g6b7d011530bc9f88@mail.gmail.com> Date: Thu, 22 Dec 2005 10:08:04 +0100 From: Spil Oss To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= In-Reply-To: <43A492B6.6050305@t-hosting.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> Cc: Wilko Bulte , current , freebsd-stable@freebsd.org, Joe Rhett Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 09:08:08 -0000 As a FreeBSD-n00b with some 'friends' that know FreeBSD better/well I can only say Please add this kind of information to the Handbook Any addition to the handbook on tracking down problems and smarter ways to fix things would be greatly appreciated. I found myself recompiling my kernel to test changes to a device's driver, but now you tell me I could have done that a lot smarter! Whenever I get my 'knickers-in-a-twist' when using FreeBSD my first point of reference is 'The Handbook'. Any additional information in there would greatly be appreciated. Learning-curve is very, very steep when you're used to lslpp and windowsupdate to patch your system. I _do_ appreciate that most developers and users are very experienced in using FreeBSD, but that makes it increasingly difficult for the not-so-fortunate to come up to speed with the use of FreeBSD. Spil. On 12/17/05, K=F6vesd=E1n G=E1bor wrote: > Wilko Bulte wrote: > > >On Sat, Dec 17, 2005 at 01:54:34PM -0800, Joe Rhett wrote.. > > > > > >>On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > >> > >> > >>>There will be three FreeBSD 6 releases in 2006. > >>> > >>> > >>While this is nice, may I suggest that it is time to put aside/delay on= e > >>release cycle and come up with a binary update mechanism supported well= by > >>the OS? Increasing the speed of releases is good. Increasing the numb= er > >>of deployed systems out of date because there are no easy binary upgrad= e > >>mechanisms is bad. > >> > >>It has been bad, it's getting worse. > >> > >> > > > >So, when will you fix it? Or hire someone to fix it? FreeBSD after > >all is mostly a volunteer operation. > > > > > > > I agree. And after all, tracking a security branch isn't too difficult, > but the most people think that they have to do a complete "make > buildworld" after a security advisory, but this isn't true. For example > there was that cvsbug issue in September: > ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:20.cvsbug= .asc > One can read here: > > b) Execute the following commands as root: > > # cd /usr/src > # patch < /path/to/patch > # cd /usr/src/gnu/usr.bin/cvs/cvsbug > # make obj && make depend && make && make install > # cd /usr/src/gnu/usr.bin/send-pr > # make obj && make depend && make && make install > > Is that difficult? I don't think so. No reboot required and it doesn't > take more than 5 minutes even on a slower machine. Only the > vulnerabilities in the kernel are problematic for servers, since they > require a reboot. I think I'll submit a PR with a patch to clarify this > in Handbook. Do you consider this useful? > > Regards, > > Gabor Kovesdan > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >