It's only a drag when operating in x86 Legacy Mode on an AMD64-based core. When you're operating in x86-64 Compatibility Mode or x86-64 Long Mode, you get access to sixteen 64-bit registers. Here's a graphic which explains it quite nicely: http://www.devx.com/assets/amd/5929.gif
The rest of the article explains the concepts of the AMD64 architecture. Link: http://www.devx.com/amd/Article/16018
Like I said elsewhere, I use the Dag-Apt Firebird RPMS, which are available for RH7.3, RH8 and RH9. Linkage: http://dag.wieers.com/packages/mozilla-firebird/
Unfortunately they only have 0.6.1 packages at the moment, but I'm sure they'll update to 0.7. I checked the apt repository at FreshRPMS as well and they haven't updated yet either.
They aren't stopping development, they're just changing the way they develop Mozilla and all the applications that are related to it. A good link that explains the entire modus operandi of the Mozilla development team is: http://www.mozilla.org/roadmap.html
It explains quite clearly how the Mozilla team are moving away from big, hard-to-maintain monolithic applciaitons suites and towards a modular system of components, like Firebird and Thunderbird, which can be worked on much more easily. It's a very good read, actually.
Freenet has problems; the authors of Freenet have stated that Freenet is subject to breakage at any time because it is NOT production software; it's actually a research project that should not be trusted to carry important data. Naturally this upset quite a lot of people. I think Slashdot even had a story about it as well.
Can cell phones even be registered on the DNC list? I thought only landlines and similar phone systems could be registered, not cell phones. If they can, though, then by all means let's register our cell phones and show that the telemarketers are not going to get us that way either!
That makes a lot of sense. Why should we avoid literature that portrays the OSS community in a bad light? "Gasp, horror, someone wrote nasty things about us!"
Reading this stuff, while distasteful to some people, is very important; I'm reading it right now. Learning about ourselves from a different perspective will allow us to remove the myths and misconceptions and tell people the truth about ourselves. Avoiding this type of stuff only guarantees that we'll continue acting in a way that the corporate world doesn't like, which is not a Good Thing.
Although I must take exception to the title of the article, "Linux Hit Men."
You probably heard correctly. Except in those days, tape drives were king of long-term backups because it was relatively easy to create a tape big enough to hold a gig of data. Nowadays you would need an enormous amount of tape(s) to fully back up 300GB of data. I know the tape storage companies are scaling tapes up (IIRC there are 80GB tapes floating around), but ATM a 300GB disk is really just too big to easily back up, IMO.
A drive that big is hardly useful by itself; it's better off in a RAID 1 or RAID 1+0 configuration. Having 300GB of data on a single hard disk only guarantees that when the disk crashes and FUBARs all of your non-backed-up data, you'll wish you'd gotten 2 of the monsters. Drives this big are just too vulnerable when used singly without RAID or a sound backup plan.
I'm all for innovation, but seriously, who needs a 300GB hard disks except for pr0n c0lLeCt0R5, warez d00ds and RAID junkies?
Most of the spam I get is on my webmail accounts; right now it's all W32.Swen. I don't operate a local mail server, so I haven't had to deal with the crazy life of a spam-battling mailadmin;-)
That does sound like a good idea, yet no one has implemented it yet. Why not? Is it actually nontrivial to monitor port 25 connections without drastically slowing down traffic? Or is it just that no one has quite figured out how to do it yet?
Does anyone know when the Googlecache will appear?
As for the music site itself, I suspect it will last until pressure from U.S. companies forces it to either start raising prices or using DRM. I would be surprised if it managed to take off like iTunes.
You are most definitely correct, sir. Just because we think we have the moral high ground in this case doesn't mean that SCO doesn't have something to go on.
To those of you fighting this case, KEEP FIGHTING!
It's not the exact same thing, but I have no doubts that the code which finds bugs in other code and the code which monitors itself probably share a few common traits. IHNKOE, but either way both toolsets are extremely useful for large projects like the Linux kernel.
The people who run the Stanford bug checker project run their code on the Linux kernels all the time and post the results. From my POV, about 85% of the stuff it finds are legit bugs, like heap usage bugs.
This sort of thing is a godsend for huge interconnected projects because it makes it so much easier to find bugs without exhaustively searching the entire code.
My father has two DVSam 17" LCDs connected to a Matrox Millennium G450. He absolutely loves this setup because it makes it much easier to work on larger tasks like copying files using Explorer or viewing multiple Web pages or viewing a Web page while typing an e-mail.
I wish I could have a dual-monitor setup.
There are real-time variants of the Linux kernel, and at best all they had to do was write a kernel module which would talk to the transmission devices. They may have even used the V4L API to do it. And the presence of a software GSM library here (http://kbs.cs.tu-berlin.de/~jutta/toast.html) would have made writing the software much easier as well.
That's precisely the sort of thing that people were upset about. By removing the NXDOMAIN response from the.com and.net domains, VeriSign managed to break things in very mysterious and diffcult-to-detect ways. DNS problems and spam were only part of the problem, as your example showed.
Let's just hope that VeriSign is prevented from ever breaking DNS like this again.
Most major ISPs and institutions successfully blocked a "service" which only resulted in widespread disruption in the way the Internet works. It didn't necessarily stay blocked, as in the case of Adelphia, but it was blocked rather quickly. I like the graphs showing SiteFinder traffic; they're very easy to read and they show the drops quite clearly.
Looking through the study, I found something interesting: most of the blockages of SiteFinder were outside the U.S. Interesting.....
Slashdot Mirror
I've read some of Edgar Rice Burrough's Barsoom series from Project Gutenberg.
It's only a drag when operating in x86 Legacy Mode on an AMD64-based core. When you're operating in x86-64 Compatibility Mode or x86-64 Long Mode, you get access to sixteen 64-bit registers. Here's a graphic which explains it quite nicely: http://www.devx.com/assets/amd/5929.gif
The rest of the article explains the concepts of the AMD64 architecture. Link: http://www.devx.com/amd/Article/16018
Like I said elsewhere, I use the Dag-Apt Firebird RPMS, which are available for RH7.3, RH8 and RH9. Linkage: http://dag.wieers.com/packages/mozilla-firebird/
Unfortunately they only have 0.6.1 packages at the moment, but I'm sure they'll update to 0.7. I checked the apt repository at FreshRPMS as well and they haven't updated yet either.
Much better! Thanks for mirroring this. Here's to slashdotting your site! ;-)
Does anyone know when RPMs will surface? I use the Dag-Apt RPMs for 0.6.1, and would like to know if anyone intends to make 0.7 RPMs.
They aren't stopping development, they're just changing the way they develop Mozilla and all the applications that are related to it. A good link that explains the entire modus operandi of the Mozilla development team is: http://www.mozilla.org/roadmap.html
It explains quite clearly how the Mozilla team are moving away from big, hard-to-maintain monolithic applciaitons suites and towards a modular system of components, like Firebird and Thunderbird, which can be worked on much more easily. It's a very good read, actually.
Since when is Netscape a proprietary application? Sources have been available since 1998!
These days, probably pretty damn fast. Check your search function.
Freenet has problems; the authors of Freenet have stated that Freenet is subject to breakage at any time because it is NOT production software; it's actually a research project that should not be trusted to carry important data. Naturally this upset quite a lot of people. I think Slashdot even had a story about it as well.
Can cell phones even be registered on the DNC list? I thought only landlines and similar phone systems could be registered, not cell phones. If they can, though, then by all means let's register our cell phones and show that the telemarketers are not going to get us that way either!
Because there will always be low-IQ morons who really think that they can get that new vacuum cleaner for only three easy payments of $19.95.
Ugh.
You're right. Like I said somewhere else, ignoring this stuff is only going to hurt us in the long run.
That makes a lot of sense. Why should we avoid literature that portrays the OSS community in a bad light? "Gasp, horror, someone wrote nasty things about us!"
Reading this stuff, while distasteful to some people, is very important; I'm reading it right now. Learning about ourselves from a different perspective will allow us to remove the myths and misconceptions and tell people the truth about ourselves. Avoiding this type of stuff only guarantees that we'll continue acting in a way that the corporate world doesn't like, which is not a Good Thing.
Although I must take exception to the title of the article, "Linux Hit Men."
You probably heard correctly. Except in those days, tape drives were king of long-term backups because it was relatively easy to create a tape big enough to hold a gig of data. Nowadays you would need an enormous amount of tape(s) to fully back up 300GB of data. I know the tape storage companies are scaling tapes up (IIRC there are 80GB tapes floating around), but ATM a 300GB disk is really just too big to easily back up, IMO.
A drive that big is hardly useful by itself; it's better off in a RAID 1 or RAID 1+0 configuration. Having 300GB of data on a single hard disk only guarantees that when the disk crashes and FUBARs all of your non-backed-up data, you'll wish you'd gotten 2 of the monsters. Drives this big are just too vulnerable when used singly without RAID or a sound backup plan.
I'm all for innovation, but seriously, who needs a 300GB hard disks except for pr0n c0lLeCt0R5, warez d00ds and RAID junkies?
Most of the spam I get is on my webmail accounts; right now it's all W32.Swen. I don't operate a local mail server, so I haven't had to deal with the crazy life of a spam-battling mailadmin ;-)
That does sound like a good idea, yet no one has implemented it yet. Why not? Is it actually nontrivial to monitor port 25 connections without drastically slowing down traffic? Or is it just that no one has quite figured out how to do it yet?
Does anyone know when the Googlecache will appear?
As for the music site itself, I suspect it will last until pressure from U.S. companies forces it to either start raising prices or using DRM. I would be surprised if it managed to take off like iTunes.
You are most definitely correct, sir. Just because we think we have the moral high ground in this case doesn't mean that SCO doesn't have something to go on.
To those of you fighting this case, KEEP FIGHTING!
It's not the exact same thing, but I have no doubts that the code which finds bugs in other code and the code which monitors itself probably share a few common traits. IHNKOE, but either way both toolsets are extremely useful for large projects like the Linux kernel.
The people who run the Stanford bug checker project run their code on the Linux kernels all the time and post the results. From my POV, about 85% of the stuff it finds are legit bugs, like heap usage bugs.
This sort of thing is a godsend for huge interconnected projects because it makes it so much easier to find bugs without exhaustively searching the entire code.
My father has two DVSam 17" LCDs connected to a Matrox Millennium G450. He absolutely loves this setup because it makes it much easier to work on larger tasks like copying files using Explorer or viewing multiple Web pages or viewing a Web page while typing an e-mail.
I wish I could have a dual-monitor setup.
There are real-time variants of the Linux kernel, and at best all they had to do was write a kernel module which would talk to the transmission devices. They may have even used the V4L API to do it. And the presence of a software GSM library here (http://kbs.cs.tu-berlin.de/~jutta/toast.html) would have made writing the software much easier as well.
That's precisely the sort of thing that people were upset about. By removing the NXDOMAIN response from the .com and .net domains, VeriSign managed to break things in very mysterious and diffcult-to-detect ways. DNS problems and spam were only part of the problem, as your example showed.
Let's just hope that VeriSign is prevented from ever breaking DNS like this again.
Most major ISPs and institutions successfully blocked a "service" which only resulted in widespread disruption in the way the Internet works. It didn't necessarily stay blocked, as in the case of Adelphia, but it was blocked rather quickly. I like the graphs showing SiteFinder traffic; they're very easy to read and they show the drops quite clearly.
Looking through the study, I found something interesting: most of the blockages of SiteFinder were outside the U.S. Interesting.....