From owner-freebsd-advocacy@FreeBSD.ORG Wed Jun 22 21:24:40 2005 Return-Path: X-Original-To: freebsd-advocacy@freebsd.org Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A3516A41C for ; Wed, 22 Jun 2005 21:24:40 +0000 (GMT) (envelope-from andy@glbx.net) Received: from mx1.out.mail.glbx.net (mx1.out.mail.glbx.net [80.76.201.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B46E43D1F for ; Wed, 22 Jun 2005 21:24:39 +0000 (GMT) (envelope-from andy@glbx.net) Received: from hydrogen.glbx.net ([80.76.194.12] helo=[172.16.0.12]) by mx1.mail.glbx.net with esmtpsa (Exim 4.51; TLSv1:RC4-SHA:128) id 1DlCi6-0001Xr-5Z for freebsd-advocacy@freebsd.org; Wed, 22 Jun 2005 22:24:38 +0100 In-Reply-To: <1148288725.20050623031110@mail.ru> References: <6F2F8FD3FBCF7A489CB18912A4807EBA0E0851@mvwcim1a.acuson.com> <42B76191.1040402@buckhorn.net> <4E4F19D4-F10F-4F15-AF9D-B1FCCEB6FFF9@glbx.net> <1148288725.20050623031110@mail.ru> Mime-Version: 1.0 (Apple Message framework v730) X-Priority: 3 (Normal) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1BE4083B-4E39-446C-AAB8-8787DA10D136@glbx.net> Content-Transfer-Encoding: 7bit From: Andy Gilligan Date: Wed, 22 Jun 2005 22:24:36 +0100 To: freebsd-advocacy@freebsd.org X-Mailer: Apple Mail (2.730) Subject: Re: FreeBSD entry on Wikipedia X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2005 21:24:40 -0000 On 22 Jun 2005, at 21:11, Vadim Goncharov wrote: > AG> On 21 Jun 2005, at 01:38, Bob Martin wrote: >>> IMHO, if they can roll out a patch to a major security flaw in a >>> day, they should have been able to fix the uptime clock at some >>> point in the last decade. Odd that MS can do something that Linux >>> can't. >>> > AG> This was fixed about 3 years ago. > > Sure? So why Netcraft states about it aven nowadays? Even more, it > says > that some versions of FreeBSD (newer, as I understood) also wrap that > uptime counter? Linux used to wrap at 497 days, but there were a few changes in 2.5.x to change the counters to 64-bit. -- In theory 2.6.x should be fine. I'm not 100% sure when or if this was backported to a 2.4 kernel release, but the patches have been around since early 2002. (around 2.4.19) -- http://lwn.net/2002/0307/a/uptime.php3 As for why Netcraft is reporting it... I guess it's probably safe enough to say that "most" linux machines will wrap at 497 days, as not everyone patches or upgrades their kernel. On a more personal note, I don't believe having a long uptime is always a good thing... If there are indeed Linux machines with uptimes of over 1000 days, they are no doubt full of security holes, but this applies equally to any OS. And yes, nearly all my machines are FreeBSD, before anyone asks ;) Best regards, -Andy