I was trying to clarify what I think was a factual error in Autocracy's observations of the write/read/delete data. Specifically, I think he interpreted the ext2 read as.something instead of.oh-something.
How does "yeah, but dirty restarts are faster" relate? I don't think that they do. I think that you are looking for a "my fs rulz, your fs sux" pissing contest, and you have mistaken me for some sort of ext2 zealot. So you've thrown out this non-sequiter to try to get a nice flame war going.
The problem is that you are doomed to look like a fool in any flame war, because you can't even follow the conversation.
WRT the US legal system I meant "as" in the sense that they share a problem, not as=like. So both could benifit from loser pays.
I think you have missed some of the implications of loser pays. It attracts lawyers to/winning/ cases, instead of clients with deep pockets.
The flip side of the Maggio (?) situation is that/he/ could get some studs and not worry aobut having to pay them since his case was a lock. Ah, then Nestle wouldn't have brought it in the first place, because they knew they had a loser and were just gambling (at no risk, that's my point) that he would roll over.
So, the result of loser pays is 1) the big guys ability to steamroller the little guy is greatly reduced and 2) nusance settlements go away, so little guys stop suing big guys as a form of lotto.
You might get a little more luck if you put the drive in the freezer for a while first (not sure what the IBM problem is). If it is heat related this will buy you a bit of useful time.
If you have some access to the drive but the filesystem is trashed, you can get a lot of data with dd. (This months sysadmin has an article on/file/ recovery, and some of the techniques would be applicable here.)
Finally, drives are made of parts, and you might be able to replace the bad part. This is pretty easy if it is the drive logic. (a few screws and maybe a little solder)
If it is anything except the platters themselves you can swap the platters with a good drive. (Replacing the heads, which are the most likely culprit.) The big downside here is that you have to trash a good drive (of the EXACT same type) to do this. The resulting drive is NOT to be trusted, or you will find yourself in the same position again very soon (hours or days), since you probably don't have a clean room handy to do the swap. (I suddenly think of "The Manhattan Project" when that HS kid is handling the weapons-grade plutonium with a fish tank and some rubber gloves.)
SMTP - plain text email
POP3 - plain text email AND usually user/pass pairs
telnet - more of the same
r-tools - 'nuff said (and one of the top 10)
old versions of sendmail - 'nuff said (and one of the top 10)
bind - 'nuff said
RPC - big fat holes (and one of the top 10)
Now, I perfectly understand that much of the above is because the internet "used to be such a nice neighborhood." I'm just suggesting that we not pretend away the past.
Your sig presumes that 65 is substantially safer than 75. Do you have any evidence of this (other than your "gut" or that it is "obvious" that this is true?
Your time would be better spent trying to convince people to follow at a safe distance.
Why? If they can tamper with the releases, they can tamper with the MD5s.
For mirrors. You get the MD5 (AFAIR, 128bits, conceiveably double that when including the filename;-) from the "official" site and use it to verify that the bins on the mirror haven't been altered.
They really don't need your help, even in the event that you haven't tampered with the software at hand. Mozilla's dedicated 45mbps line will hold up just fine.
Really? Did you know that bugzilla was screwed up for HOURS when slashdot ran the story about the manager or whoever being laid off?
Oh, and I can only wish I was so cool that I could "tamper" with the software within, what, and hour of the release. I'm working on it, but I'm not there yet.
You are right in theory though. The mozilla folks really ought to put up MD5s with the release.
You're almost as dumb as the people shouting that they have a kernel mirror up after a new release (they already got a 100mbps line, people).
Well, a Linux kernel source tarball is about, what, 20M? And there are about, what, a bazillion ftp.us.kernel.org mirrors? And another bazillion world wide? I think that this is a bit different.
Oh, by the way, get a FUCKING LOGIN if you're going to talk shit. Oh, wait, you probably have one, but don't want to waste your precious karma.
1. Write a library to make the code that is invalid in whatever Pascal compiler you want to use valid. (i.e. emulate missing built-in funcions)
2. Automate translating code from one version to another. For instance, maybe the Sun Pascal has OO extensions, and you could automate translating the Sun object declarations to Objective Pascal (that's a language, right?) style declarations.
3. There is surely a Free (or at least open) Pascal compiler that you could modify to compile the Sun style code.
I'd bet that the best bet is a bit of all three.
It also seems that Pascal and C should translate almost exactly 1-1. There is a Pascal to C conversion script out there, you might be able to write a Sun Pascal to C conversion script faster than any of the other suggestions.
Slashdot Mirror
How is this even remotely a reply to what I said?
.something instead of .oh-something.
I was trying to clarify what I think was a factual error in Autocracy's observations of the write/read/delete data. Specifically, I think he interpreted the ext2 read as
How does "yeah, but dirty restarts are faster" relate? I don't think that they do. I think that you are looking for a "my fs rulz, your fs sux" pissing contest, and you have mistaken me for some sort of ext2 zealot. So you've thrown out this non-sequiter to try to get a nice flame war going.
The problem is that you are doomed to look like a fool in any flame war, because you can't even follow the conversation.
Sorry, pal.
-Peter
Uh, did you miss the zero in the tenths place on ext2? It has the lowest write AND read time.
So, to answer your question directly, yes, I see a trend, ext2 is fastest in all three areas.
-Peter
Yeah, just like the cube.
Oh, wait . . .
-Peter
Yeah, that's a great idea.
But it doesn't answer the fucking question, does it?
-Peter
PS: Get a fucking login, twit.
-P
By managemnet I meant managing the project (doing releases, managing the mailing list, etc.)
So the design/management (almost made the same typo twice!) meant "techical/non-techical project stuff that isn't coding."
Make better sense?
-Peter
Code Free Software in your spare time!
And don't let yourself get sucked into project design/managemnet, which would defeat the purpose.
-Peter
WRT the US legal system I meant "as" in the sense that they share a problem, not as=like. So both could benifit from loser pays.
/winning/ cases, instead of clients with deep pockets.
/he/ could get some studs and not worry aobut having to pay them since his case was a lock. Ah, then Nestle wouldn't have brought it in the first place, because they knew they had a loser and were just gambling (at no risk, that's my point) that he would roll over.
I think you have missed some of the implications of loser pays. It attracts lawyers to
The flip side of the Maggio (?) situation is that
So, the result of loser pays is 1) the big guys ability to steamroller the little guy is greatly reduced and 2) nusance settlements go away, so little guys stop suing big guys as a form of lotto.
-Peter
Yeah, the board decided that these guys (Nestle and Apsen Grove software) were abusing the system.
What isn't mentioned is what the repercussions will be.
If it is just a matter of pissing away the money on lawyers, that isn't enough.
Sounds like this system is in bad a need of loser pays as the US court system.
-Peter
Even better, you are only responsible for the $50 if the fraud is with your card.
If you dispute a charge and the merchant can't prove he earned the $$ you pay nothing.
-Peter
Let's crawl before we walk and get warp working first!
-Peter
Consider using dd, grep, etc. on a Tom's Root/Boot disk.
-Peter
There is no really cheap way to go, but . . .
/file/ recovery, and some of the techniques would be applicable here.)
You might get a little more luck if you put the drive in the freezer for a while first (not sure what the IBM problem is). If it is heat related this will buy you a bit of useful time.
If you have some access to the drive but the filesystem is trashed, you can get a lot of data with dd. (This months sysadmin has an article on
Finally, drives are made of parts, and you might be able to replace the bad part. This is pretty easy if it is the drive logic. (a few screws and maybe a little solder)
If it is anything except the platters themselves you can swap the platters with a good drive. (Replacing the heads, which are the most likely culprit.) The big downside here is that you have to trash a good drive (of the EXACT same type) to do this. The resulting drive is NOT to be trusted, or you will find yourself in the same position again very soon (hours or days), since you probably don't have a clean room handy to do the swap. (I suddenly think of "The Manhattan Project" when that HS kid is handling the weapons-grade plutonium with a fish tank and some rubber gloves.)
Good luck (you're gonna need it).
-Peter
I'm a bit biased, but . . .
Siege is a great way to stress test a webserver.
GPL, C (with an optional bash wrapper for automated "progressive" testing)
I want to "port" the script to straight sh, but I can't find it for testing. If anyone knows where I can get it, let me know.
-Peter
I assume MO here means magneto-optical.
Who the hell has an MO hard drive? MO WORM drives used to be pretty popular . . .
Hm.
-Peter
Yeah, it is illegal here (USA) as well. That was my point. It is illegal in both places, but Germans actually care.
See how this supports my orginal statment?
-Peter
Our (USA) government is pretty clueless when it comes to legislating technology.
The advantage we have is that when we find a law stupid, we feel free to violate it.
Is there even a word for jaywalking in German?
-Peter
Yeah, Gary and Dave, the old blokes brought us:
SMTP - plain text email
POP3 - plain text email AND usually user/pass pairs
telnet - more of the same
r-tools - 'nuff said (and one of the top 10)
old versions of sendmail - 'nuff said (and one of the top 10)
bind - 'nuff said
RPC - big fat holes (and one of the top 10)
Now, I perfectly understand that much of the above is because the internet "used to be such a nice neighborhood." I'm just suggesting that we not pretend away the past.
-Peter
Your sig presumes that 65 is substantially safer than 75. Do you have any evidence of this (other than your "gut" or that it is "obvious" that this is true?
Your time would be better spent trying to convince people to follow at a safe distance.
-Peter
The article says that there is an 80% chance that there WON'T be a total re-write by year end 2002.
-Peter
In *nix environments, reboots are not required as often (except for kernel changes[...])
I've never used it, but AFAIK you can even get around this with the HURD.
-Peter
That's true if by PC you mean "beige box."
But not if you mean "Intel (or compatible) based system."
You can get a "PC" with redundant power, "lights out" mangemnet, hot-plug PCI, hot-plug RAID disks, etc.
-Peter
Why? If they can tamper with the releases, they can tamper with the MD5s.
;-) from the "official" site and use it to verify that the bins on the mirror haven't been altered.
For mirrors. You get the MD5 (AFAIR, 128bits, conceiveably double that when including the filename
-Peter
I know I shouldn't feed the trolls, but . . .
They really don't need your help, even in the event that you haven't tampered with the software at hand. Mozilla's dedicated 45mbps line will hold up just fine.
Really? Did you know that bugzilla was screwed up for HOURS when slashdot ran the story about the manager or whoever being laid off?
Oh, and I can only wish I was so cool that I could "tamper" with the software within, what, and hour of the release. I'm working on it, but I'm not there yet.
You are right in theory though. The mozilla folks really ought to put up MD5s with the release.
You're almost as dumb as the people shouting that they have a kernel mirror up after a new release (they already got a 100mbps line, people).
Well, a Linux kernel source tarball is about, what, 20M? And there are about, what, a bazillion ftp.us.kernel.org mirrors? And another bazillion world wide? I think that this is a bit different.
Oh, by the way, get a FUCKING LOGIN if you're going to talk shit. Oh, wait, you probably have one, but don't want to waste your precious karma.
I've got the new release mirrored at ftp://nerf-herder.net/pub/mozilla
-Peter
A couple things you could do:
1. Write a library to make the code that is invalid in whatever Pascal compiler you want to use valid. (i.e. emulate missing built-in funcions)
2. Automate translating code from one version to another. For instance, maybe the Sun Pascal has OO extensions, and you could automate translating the Sun object declarations to Objective Pascal (that's a language, right?) style declarations.
3. There is surely a Free (or at least open) Pascal compiler that you could modify to compile the Sun style code.
I'd bet that the best bet is a bit of all three.
It also seems that Pascal and C should translate almost exactly 1-1. There is a Pascal to C conversion script out there, you might be able to write a Sun Pascal to C conversion script faster than any of the other suggestions.
Good luck!
-Peter