Date: Thu, 23 Jun 2005 05:20:48 +0700 From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-advocacy@freebsd.org Subject: Re[2]: FreeBSD entry on Wikipedia Message-ID: <553024286.20050623052048@mail.ru> In-Reply-To: <1BE4083B-4E39-446C-AAB8-8787DA10D136@glbx.net> References: <6F2F8FD3FBCF7A489CB18912A4807EBA0E0851@mvwcim1a.acuson.com> <42B76191.1040402@buckhorn.net> <4E4F19D4-F10F-4F15-AF9D-B1FCCEB6FFF9@glbx.net> <1148288725.20050623031110@mail.ru> <1BE4083B-4E39-446C-AAB8-8787DA10D136@glbx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Andy, Thursday, June 23, 2005, 4:24:36 AM, you 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? AG> Linux used to wrap at 497 days, but there were a few changes in 2.5.x to AG> change the counters to 64-bit. -- In theory 2.6.x should be fine. AG> I'm not 100% sure when or if this was backported to a 2.4 kernel AG> release, AG> but the patches have been around since early 2002. (around 2.4.19) AG> -- http://lwn.net/2002/0307/a/uptime.php3 AG> As for why Netcraft is reporting it... I guess it's probably safe enough AG> to say that "most" linux machines will wrap at 497 days, as not everyone AG> patches or upgrades their kernel. I've not understood. AFAIR, Netcraft says that it was broken somewhere in 2.5, and it began to wrap again. Moreover, it would be great if you could tell method how Netcraft is determining uptime remotely - they changed counters to 64bit, and what?.. Where it is in TCP/IP stack? And where that stuff in FreeBSD ? AG> On a more personal note, I don't believe having a long uptime is always AG> a good thing... Certainly, not always, but mostly. Although it's main function - to make impression. Top 50 is very impressive about BSD, isn't it? :) AG> If there are indeed Linux machines with uptimes of over AG> 1000 days, they are no doubt full of security holes, but this applies AG> equally to any OS. Not equally. Are the BSD machines in Top 50 really vulnerable to remote code execution attacks?.. AG> And yes, nearly all my machines are FreeBSD, before anyone asks ;) :) -- Best regards, Vadim Goncharov ICQ UIN 166852181 mailto:vadim_nuclight@mail.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553024286.20050623052048>