Date: Sat, 1 Jan 2000 18:38:04 +0200 (EET) From: mika ruohotie <bsdisp@shadows.aeon.net> To: freebsd-isp@freebsd.org Cc: freebsd-advocacy@freebsd.org Subject: Re: uptimes, Woo Hoo Message-ID: <200001011638.SAA60402@shadows.aeon.net> In-Reply-To: <386D0764.29C12FD4@pipeline.ch> from Andre Oppermann at "Dec 31, 1999 08:43:32 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> $ uname -a > FreeBSD xxx.pipeline.ch 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE > $ uptime > 8:29PM up 492 days, 15:31, 1 user, load averages: 0.00, 0.00, 0.00 thought i'd add my contribution too... fire% uname -a FreeBSD fire 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Dec 16 21:37:18 EET 1997 root@fire:/usr/src/sys/compile/FIRE i386 fire% uptime 2:15AM up 745 days, 22:23, 1 user, load averages: 0.05, 0.01, 0.00 fire% it's weekend, machine's not doing much. and i _was_ slightly unaware what would happen. since i tested y2k with its sistermachine, i'm sure the bios will not blow up if i have to reboot. oh, and i thought people say "dont use current on production". :> the machine was physically installed that particular day, dec 16th. and i've seen loads as high as 2-3 in times... whoops, the clock has drifted slightly, it thinks it's already jan 2nd. happy new year and patience in waiting still another year until the hype millennium comes... =) mickey -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001011638.SAA60402>