... I also love how characters have evolved, with Marge loosening up some and showing her cruel side.. Fox should thank its lucky stars that the show has stayed as good as it has for as long as it has..
Not bad character development for a show whose players haven't aged a year..
Anyone have any pointers to work on checking Linux and GNU/*GPL code for Y2k problems? I've done some work in this area for an investment bank but I quit that gig some months ago and I'm interested in contributing..
I manage a handful of Solaris and Linux servers and seem to always have time for other projects as well.
Yah, I have about 12-15 SPARCs and a few of my Linux 'toys', and I end up doing the Maytag repariman thing, but at least it leaves me plenty of time to read/. and fiddle with code!
I did inherit a lot of junky crap, but at least I can do everything remotely and mostly without reboot so it could be a whole lot worse..
... but make sure to get a BIOS version which will update the 32h location! Many BIOSes before 1997 will _not_ update that memory location, and almost no RTCs will update it. Newer Dallas clocks will, but barely anyone has 'em, and many sysboards have the RTC soldered onto the MB (and use Lithium batteries), though my MB has the RTC 'chunk' and a compliant BIOS.
Very few applications require a compliant RTC, but all PCs should have a compliant BIOS. check out www.rightime.com for test2000, a free PC tool which will show you all kinds of diag info (actually the viewcmos util included in the package) on your BIOS and RTC..
Seriously, though, even if the OS is compliant (like Unix), sloppy programming can still result in Y2k problems! Assuming much of Mac code is in C (or derives from a C API), you should check the manpages for various C time/date functions.. particularly tm_year. Yes, the manpages are pretty explicit about tm_year = year-1900, but who's to say that the programmer read those pages, or understood that part of the API? People fuck up. They're lazy and/or ignorant. Shit like this has been known to happen.
Yes, maybe that's the fault of a sloppy programmer, but the code remains even if the programmer doesn't. You can't pass the buck to someone who's quit, been fired, or dead..
Check your code. Check your predecessor's code. That's the only way to be sure.
backing up 100GB? Easy.. Just snag a 20-tape 2+ drive DLT robot.. Or even one of those fun IBM 349x mega-libraries which store hundreds of terabytes in cabinets 10-meters long..
I said easy, not cheap..;)
Besides, anyone interested in these drives is probably interested in running them in RAID configurations, and I can see a nice 12-drive setup with mirrored 5-disk RAID5 and a hot spare for each mirrorset.. 400GB and if you put them in separate cabinets you're close to fault tolerant..
Sweet!
(If you haven't already guessed, one of the main differences between Sun fans and IBM fans is Sun fans like high-speed and price performance, while uptime and high-availability give IBMers chills..)
Most drives today are built to be 'interface agnostic': you can pretty much bolt an identity onto the drive hardware.
Though I bet Ultra2-LVD and FCAL are definite, and when IBM's storage division catches up, I bet you'll see an SSA flavor.
Are there any limitations in EIDE for this size? I'm only familiar with SCSI, and I use IDE because it's necessary in some applications (laptops, mostly)..
Slashdot Mirror
Gibson would never use it, dude.. He writes all his work on a typewriter!
Neal Stephenson on the other hand.. (and IMO Snow Crash was a better read than Neuromancer, but I tend to prefer my fiction with a sense of humor..)
Cheers,
... I also love how characters have evolved, with Marge loosening up some and showing her cruel side.. Fox should thank its lucky stars that the show has stayed as good as it has for as long as it has..
Not bad character development for a show whose players haven't aged a year..
Hi,
Where do I download the new code? All I see released is the v0.2, and that's some revs behind I would imagine....
Thanks,
Hi,
Anyone have any pointers to work on checking Linux and GNU/*GPL code for Y2k problems? I've done some work in this area for an investment bank but I quit that gig some months ago and I'm interested in contributing..
Cheers,
I manage a handful of Solaris and Linux servers and seem to always have time for other projects as well.
/. and fiddle with code!
Yah, I have about 12-15 SPARCs and a few of my Linux 'toys', and I end up doing the Maytag repariman thing, but at least it leaves me plenty of time to read
I did inherit a lot of junky crap, but at least I can do everything remotely and mostly without reboot so it could be a whole lot worse..
... but make sure to get a BIOS version which will update the 32h location! Many BIOSes before 1997 will _not_ update that memory location, and almost no RTCs will update it. Newer Dallas clocks will, but barely anyone has 'em, and many sysboards have the RTC soldered onto the MB (and use Lithium batteries), though my MB has the RTC 'chunk' and a compliant BIOS.
Very few applications require a compliant RTC, but all PCs should have a compliant BIOS. check out www.rightime.com for test2000, a free PC tool which will show you all kinds of diag info (actually the viewcmos util included in the package) on your BIOS and RTC..
Have a compliant day,
Haaah Haaah!
Seriously, though, even if the OS is compliant (like Unix), sloppy programming can still result in Y2k problems! Assuming much of Mac code is in C (or derives from a C API), you should check the manpages for various C time/date functions.. particularly tm_year. Yes, the manpages are pretty explicit about tm_year = year-1900, but who's to say that the programmer read those pages, or understood that part of the API? People fuck up. They're lazy and/or ignorant. Shit like this has been known to happen.
Yes, maybe that's the fault of a sloppy programmer, but the code remains even if the programmer doesn't. You can't pass the buck to someone who's quit, been fired, or dead..
Check your code. Check your predecessor's code. That's the only way to be sure.
backing up 100GB? Easy.. Just snag a 20-tape 2+ drive DLT robot.. Or even one of those fun IBM 349x mega-libraries which store hundreds of terabytes in cabinets 10-meters long..
;)
I said easy, not cheap..
Besides, anyone interested in these drives is probably interested in running them in RAID configurations, and I can see a nice 12-drive setup with mirrored 5-disk RAID5 and a hot spare for each mirrorset.. 400GB and if you put them in separate cabinets you're close to fault tolerant..
Sweet!
(If you haven't already guessed, one of the main differences between Sun fans and IBM fans is Sun fans like high-speed and price performance, while uptime and high-availability give IBMers chills..)
Most drives today are built to be 'interface agnostic': you can pretty much bolt an identity onto the drive hardware.
Though I bet Ultra2-LVD and FCAL are definite, and when IBM's storage division catches up, I bet you'll see an SSA flavor.
Are there any limitations in EIDE for this size? I'm only familiar with SCSI, and I use IDE because it's necessary in some applications (laptops, mostly)..