I've used some pretty big Teradata databases (though not as huge as the ones on this list) and I have to admit the performance was pretty good. Most notable was how well performance scaled - that is, compared to Oracle or Sybase IQ you could keep throwing more and more data at Teradata for minimal loss in performance.
I would like to suggest that, once this case is finally settled, Slashdot begin using the caldera systems icon for "Laugh, it's Funny" instead of the Monty Python foot. I know I already associate that blue and red C with a good humourous story.
I was saying the same thing when Darth Maul was slaughtered at the end of Ep1: So, are we just going to randomly pluck a new Dark Lord of the Sith out of nowhere so that he can be killed by Annakin?
The first 3 films has the Emperor invisible behind the scenes, and Darth Vader as a consistent villlain through all 3. The latest 3 seem to have the Emperor mostly invisible behind the scenes, and a random selection of revolving door bad guys.
Givent he recent attacks against Savannah, Debian, and Gentoo, I wonder if it is at all possible that WindowsUpdate got hacked - not badly, possibly just enough for someone to touch the patch causing it to be reissued.
It's not like we'll hear about it if that is the case, so any guesses?
That's good to know. I only have the second edition, and it tends to refer to bash as something new and different, and doesn't spend as much time with it as would be useful for someone not working on Solaris or AIX.
I think it sounds quite poor really. Random villain rotation, and a serious lack of real motivation for a lot of actions taken by characters. I'm now firmly in the camp that Lucas had no great plan, and he's just making this up as he goes along.
And no, I won't go and see it. I _might_ watch it on video, or if it ever makes it to the $2.50 cinema down the road, but I sure as hell won't pay full price for it. DVDs? I doubt I'll own ANY Star Wars DVDs given that they will only be available as Lucas' hand butchered special editions.
Lucas seems to havea real problem managing his villians. He establishes a powerful villiain in Ep1, capable of killing senior Jedi, only to finish the film by cutting him in half. So in Ep2 we have to get introduced to Dooku, who happily kicks Annakin and Obi Wan around, only to be summarily killed at the very beginning of Ep3, so we get a new all powerful villain General Grevious (where the hell does he get these names, just looking through the dictionary?!) who has apparently killed many jedi. So um, exactly how good are these Jedi. There are apparently not that many of them, but there seems to be a large supply of villains who can kick them around.
Lucas really needed to do better than "no, I don't like him anymore, lets' make another villain" approach to things.
It's a shame that the book is perhaps a little basic - when I heard the title I was hoping for something along the lines of UNIX Power Tools specialised to Linux. UNIX Power Toolsreally is one of the best books out there on using UNIX. No matter how experienced a user you are you're likely to find some little gem of information buried in it - and that's all it really is, simply a collection of little gems of information about everything UNIX. It would be nice to see a book along those lines that covered Linux more specifically.
I've read an awful lot of "see this is why open source is good" and "hah! Windows 98 had free support for 5 years", so let's just boil this down a little.
No one (except maybe a few deluded individuals) are claiming that Redhats EOL after only a year is a particularly nice thing to have happen. I'm not that happy about it, but I can push on with Fedora which actually works quite nicely, and all will be well. But the short answer is: EOL after a year is a bad thing no matter who does it. Equally, I think Microsoft supporting Windows 98 for 5 years is not a bad effort all things considered (and there will be fewer who will agree with me on that, but hey).
I think the point being made here is NOT that Redhat EOLing after a year is good, or terribly acceptable. The point is that, under this system, in the worst case if the company you are with ups stakes and moves to a different market and leaves you in the cold, you have some recourse.
I think it is great that Microsoft has provided 5 years of support for Windows 98. The catch is, if they were to decide t EOL Server 2003 tomorrow, there's not a whole lot anyone could do about it (especially given the healthy degree of lockin Microsoft has gained). I don't think that Microsoft will do that, but then we don't know. I do recall there was some fuss recently about whether the latest OS X patches were going to available for Jaguar. Had they not been, what would Apple users been left with? Or, to look at it another way, BeOS got seriously EOLd a while ago. There are some fine efforts with OpenBeOS to reconstruct it, but that's no small task, and until they manage something BeOS is effectively dead (well, okay, there's Zeta, but that was a lucky save). This is a demonstration that, in the worst case for a Linux Distro, it's not the end.
So, to reapeat: EOL - bad. Continuing Support - good.
Jedidiah.
Re:Stick with Windows and if you do...
on
PC Annoyances
·
· Score: 1
I agree that it would meet his needs - but I think he was not looking to buy a completely new set of hardware.
As other people have pointed out, this is an unstable development release, not a polished final product. I suspect the varied labelling is due to people coding up different components and putting temporary placeholder strings in for now (if the "Component" isn't a give away placeholder string I don't know what is) while they get the features working. I think you'll find a lot of that will be cleaned up for Evolution 2.0
with nothing more than a respectable corporate name on the outside of the box.
Maybe it's because that corporation provides services like an on-site support contract?
To be fair though, there have been several Linux companies (Redhat and SUSE most prominent) that have offered support contracts. When Sun offers pretty much the same thing people take notice - it's amazing what a anme can do. Especially when you not that Sun is in decline (not irreversible, but let's face it, they haven't been doing quite so well the last few quarters) while Redhat and SUSE are both pushing ahead.
It will be interesting to see if uptake of Sun's Linux distro will see Redhat and SUSE's fortunes improve further - they are big names in the linux business, so if linux gets to be a name of note, all of a sudden they could start making some big contracts.
If OO competes too well with M$word, then Micro$oft is likely to make their next version incompatible with OO or incompitable enough that people will be reluctant to switch.
It begins to get double edged though. Do you upgrade to the new MS office which saves in file formats that your older MS Office intalls (and other people using older MS Office suites) can't read - or do you cross grade to OpenOffice where you can get free upgrades and (due to the open nature of file formats)no more file format issues on upgrading? Hmmm.
As long as the next Office with the major file format changes arrives before OpenOffice gets too much of a toehold, it will work. On the other hand, if it arrives too late it could blow up in MS's face.
If your browser knows how to take the hints to save it's current state, yes, it will. Certainly galeon works that way, and expect others will too (especially the integrated browsers like Konqueror and Epiphany).
I'm the "guy who gets in your way" because my responsibility is to the system, not to you.
I suspect this is one of the sticking points. As far as many are concerned the job of the sysadmin is to make sure the system, and applications on it are available to them. If a developer can't do what he/she wants, then you're (in his mind) failing in your job to provide systems to him/her. Of course, often it's a greater good scenario - you make one persons access to the system a little bit harder to make sure everyone's access remains constant and stable. The pissed off developer tends to have a rather shorter term view than that though.
I think it is easier to see this in comparison to debian. Redhat used to be a bleeding edge distro, but as they got more business uptake, they had to slow back a bit. This left them in a quandry. They couldn't test the bleeding edge stuff and still have a solid stable server for business. Basically, they had everything as Debian testing, bto keep roughly in line with Enterprise Linux which was essentially equivalent to debian stable. Fedora represents a chance for Redhat to make a proper unstable distribution again - in the debian sense of unstable: rapid updates for new packages, but still fairly solid in most respects.
Debian had a fine setup from the start (though these days even unstable is running a little behind, hence the beginnings of UserLinux), but Redhat didn't have that differentiation. This split is effectively formalising that differentiation between stable and unstable products. The difference to debian is that Redhat stable comes with big support contract as well.
What do all those Gentoo fanboys who were saying "this would never happen with Gentoo" when Debian had problems have to say now? What can you do about zealots?
And sorry to all the many, many, perfectly sensible Gentoo users out there. An unfortunate incident, but, as with the Debian incident, it looks as if it is being well handled. I'll be interested to see the details on how the compromise occurred.
SELinux and it's ilk, while not invulnerable to buffer overflows, are a LOT less vulnerable. You can happily get your buffer overflow in such systems, but that generally won't get you root access - rather the program you just overflowed will get terminated and restarted and you'll be back where you started. It's a good system (and integrated into Linux 2.6) so check it out.
Jedidiah.
Re:I use good passwords, and here's how
on
Real Security?
·
· Score: 1
Not entirely. A cracker will have a list of techniques to try. First on that list is an obvious dictionary attack. After that they'll likely go for a modified dictionary attack (leet speaked words, words with digits prepended or appended etc.), and then you'll be on to putting together characters. At that point they'll probably be looping over common letter strings first. They can then try leet speacked versions of those. That's about where they'd get a hit. That's a long way down the tree, so, as I say, it's probably sufficient for general use, but it is not as good (in theory) as something that is purely random characters.
It's also worth noting that the Shinkansen lines in Japan have never had _any_ passenger deaths. The odd inattentive railway worker, or suicide jumping on the tracks, but _no_ train accidents.
They've been running since 1964. I would say almost 40 years of constant use with no accidents is a pretty damn fine record. JR are very good at safety.
Slashdot Mirror
I've used some pretty big Teradata databases (though not as huge as the ones on this list) and I have to admit the performance was pretty good. Most notable was how well performance scaled - that is, compared to Oracle or Sybase IQ you could keep throwing more and more data at Teradata for minimal loss in performance.
Jedidiah
Neither uvsc.edu, nor iomega was down for me, yet www.sco.com is still unrepsonsive, and now ftp.sco.com doesn't worj either (it was previously).
Jedidiah
I would like to suggest that, once this case is finally settled, Slashdot begin using the caldera systems icon for "Laugh, it's Funny" instead of the Monty Python foot. I know I already associate that blue and red C with a good humourous story.
Jedidiah.
I was saying the same thing when Darth Maul was slaughtered at the end of Ep1: So, are we just going to randomly pluck a new Dark Lord of the Sith out of nowhere so that he can be killed by Annakin?
The first 3 films has the Emperor invisible behind the scenes, and Darth Vader as a consistent villlain through all 3. The latest 3 seem to have the Emperor mostly invisible behind the scenes, and a random selection of revolving door bad guys.
"Villain of the week" does not instill much fear.
Jedidiah.
Givent he recent attacks against Savannah, Debian, and Gentoo, I wonder if it is at all possible that WindowsUpdate got hacked - not badly, possibly just enough for someone to touch the patch causing it to be reissued.
It's not like we'll hear about it if that is the case, so any guesses?
Jedidiah.
That's good to know. I only have the second edition, and it tends to refer to bash as something new and different, and doesn't spend as much time with it as would be useful for someone not working on Solaris or AIX.
Jedidiah
I think it sounds quite poor really. Random villain rotation, and a serious lack of real motivation for a lot of actions taken by characters. I'm now firmly in the camp that Lucas had no great plan, and he's just making this up as he goes along.
And no, I won't go and see it. I _might_ watch it on video, or if it ever makes it to the $2.50 cinema down the road, but I sure as hell won't pay full price for it. DVDs? I doubt I'll own ANY Star Wars DVDs given that they will only be available as Lucas' hand butchered special editions.
Jedidiah.
Lucas seems to havea real problem managing his villians. He establishes a powerful villiain in Ep1, capable of killing senior Jedi, only to finish the film by cutting him in half. So in Ep2 we have to get introduced to Dooku, who happily kicks Annakin and Obi Wan around, only to be summarily killed at the very beginning of Ep3, so we get a new all powerful villain General Grevious (where the hell does he get these names, just looking through the dictionary?!) who has apparently killed many jedi. So um, exactly how good are these Jedi. There are apparently not that many of them, but there seems to be a large supply of villains who can kick them around.
Lucas really needed to do better than "no, I don't like him anymore, lets' make another villain" approach to things.
Jedidiah
It's a shame that the book is perhaps a little basic - when I heard the title I was hoping for something along the lines of UNIX Power Tools specialised to Linux. UNIX Power Toolsreally is one of the best books out there on using UNIX. No matter how experienced a user you are you're likely to find some little gem of information buried in it - and that's all it really is, simply a collection of little gems of information about everything UNIX. It would be nice to see a book along those lines that covered Linux more specifically.
Jedidiah
I've read an awful lot of "see this is why open source is good" and "hah! Windows 98 had free support for 5 years", so let's just boil this down a little.
No one (except maybe a few deluded individuals) are claiming that Redhats EOL after only a year is a particularly nice thing to have happen. I'm not that happy about it, but I can push on with Fedora which actually works quite nicely, and all will be well. But the short answer is: EOL after a year is a bad thing no matter who does it. Equally, I think Microsoft supporting Windows 98 for 5 years is not a bad effort all things considered (and there will be fewer who will agree with me on that, but hey).
I think the point being made here is NOT that Redhat EOLing after a year is good, or terribly acceptable. The point is that, under this system, in the worst case if the company you are with ups stakes and moves to a different market and leaves you in the cold, you have some recourse.
I think it is great that Microsoft has provided 5 years of support for Windows 98. The catch is, if they were to decide t EOL Server 2003 tomorrow, there's not a whole lot anyone could do about it (especially given the healthy degree of lockin Microsoft has gained). I don't think that Microsoft will do that, but then we don't know. I do recall there was some fuss recently about whether the latest OS X patches were going to available for Jaguar. Had they not been, what would Apple users been left with? Or, to look at it another way, BeOS got seriously EOLd a while ago. There are some fine efforts with OpenBeOS to reconstruct it, but that's no small task, and until they manage something BeOS is effectively dead (well, okay, there's Zeta, but that was a lucky save). This is a demonstration that, in the worst case for a Linux Distro, it's not the end.
So, to reapeat: EOL - bad. Continuing Support - good.
Jedidiah.
I agree that it would meet his needs - but I think he was not looking to buy a completely new set of hardware.
Jedidiah
As other people have pointed out, this is an unstable development release, not a polished final product. I suspect the varied labelling is due to people coding up different components and putting temporary placeholder strings in for now (if the "Component" isn't a give away placeholder string I don't know what is) while they get the features working. I think you'll find a lot of that will be cleaned up for Evolution 2.0
Jedidiah
with nothing more than a respectable corporate name on the outside of the box.
Maybe it's because that corporation provides services like an on-site support contract?
To be fair though, there have been several Linux companies (Redhat and SUSE most prominent) that have offered support contracts. When Sun offers pretty much the same thing people take notice - it's amazing what a anme can do. Especially when you not that Sun is in decline (not irreversible, but let's face it, they haven't been doing quite so well the last few quarters) while Redhat and SUSE are both pushing ahead.
It will be interesting to see if uptake of Sun's Linux distro will see Redhat and SUSE's fortunes improve further - they are big names in the linux business, so if linux gets to be a name of note, all of a sudden they could start making some big contracts.
Jedidiah
If OO competes too well with M$word, then Micro$oft is likely to make their next version incompatible with OO or incompitable enough that people will be reluctant to switch.
It begins to get double edged though. Do you upgrade to the new MS office which saves in file formats that your older MS Office intalls (and other people using older MS Office suites) can't read - or do you cross grade to OpenOffice where you can get free upgrades and (due to the open nature of file formats)no more file format issues on upgrading? Hmmm.
As long as the next Office with the major file format changes arrives before OpenOffice gets too much of a toehold, it will work. On the other hand, if it arrives too late it could blow up in MS's face.
Jedidiah
If your browser knows how to take the hints to save it's current state, yes, it will. Certainly galeon works that way, and expect others will too (especially the integrated browsers like Konqueror and Epiphany).
Jedidiah
I'm the "guy who gets in your way" because my responsibility is to the system, not to you.
I suspect this is one of the sticking points. As far as many are concerned the job of the sysadmin is to make sure the system, and applications on it are available to them. If a developer can't do what he/she wants, then you're (in his mind) failing in your job to provide systems to him/her. Of course, often it's a greater good scenario - you make one persons access to the system a little bit harder to make sure everyone's access remains constant and stable. The pissed off developer tends to have a rather shorter term view than that though.
Jedidiah.
I think it is easier to see this in comparison to debian. Redhat used to be a bleeding edge distro, but as they got more business uptake, they had to slow back a bit. This left them in a quandry. They couldn't test the bleeding edge stuff and still have a solid stable server for business. Basically, they had everything as Debian testing, bto keep roughly in line with Enterprise Linux which was essentially equivalent to debian stable. Fedora represents a chance for Redhat to make a proper unstable distribution again - in the debian sense of unstable: rapid updates for new packages, but still fairly solid in most respects.
Debian had a fine setup from the start (though these days even unstable is running a little behind, hence the beginnings of UserLinux), but Redhat didn't have that differentiation. This split is effectively formalising that differentiation between stable and unstable products. The difference to debian is that Redhat stable comes with big support contract as well.
Jedidiah
Similarly bad.
Q: What's the integral of 1 over "cabin"?
A: A house boat.
Think about it.
Jedidiah.
Warning, this is quite pathetic (more along the lines of demonstrating exactly how lacking in humour mathematicians are)
Q: What's an anagram of "Banach-Tarski"
A: "Banach-Tarski Banach-Tarski"
I did warn you it sucked...
Jedidiah
You are aware that several countries maintain permanent Antarctic bases?
Jedidiah
What do all those Gentoo fanboys who were saying "this would never happen with Gentoo" when Debian had problems have to say now? What can you do about zealots?
And sorry to all the many, many, perfectly sensible Gentoo users out there. An unfortunate incident, but, as with the Debian incident, it looks as if it is being well handled. I'll be interested to see the details on how the compromise occurred.
Jedidiah
SELinux and it's ilk, while not invulnerable to buffer overflows, are a LOT less vulnerable. You can happily get your buffer overflow in such systems, but that generally won't get you root access - rather the program you just overflowed will get terminated and restarted and you'll be back where you started. It's a good system (and integrated into Linux 2.6) so check it out.
Jedidiah.
Not entirely. A cracker will have a list of techniques to try. First on that list is an obvious dictionary attack. After that they'll likely go for a modified dictionary attack (leet speaked words, words with digits prepended or appended etc.), and then you'll be on to putting together characters. At that point they'll probably be looping over common letter strings first. They can then try leet speacked versions of those. That's about where they'd get a hit. That's a long way down the tree, so, as I say, it's probably sufficient for general use, but it is not as good (in theory) as something that is purely random characters.
Jedidiah
I never said there weren't plenty of other jobs ripe for outsourcing...
Jedidiah
It's also worth noting that the Shinkansen lines in Japan have never had _any_ passenger deaths. The odd inattentive railway worker, or suicide jumping on the tracks, but _no_ train accidents.
They've been running since 1964. I would say almost 40 years of constant use with no accidents is a pretty damn fine record. JR are very good at safety.
Jedidiah