...puts us in the new age of environmental consciousness. Not only you can reuse the same parts of code on different platforms, but the Mozilla mailer is the first one to have separate folders for trash and junk.
From: Richard Stallman To: Subject: Bitkeeper Cc: Date: Fri, 18 Jul 2003 15:51:36 -0400 View all headers/Unparsed body/ Forward this mail to
> If you are trying to copy BK, give it up. We'll simply follow in the
> footsteps of every other company faced with this sort of thing and change
> the protocol every 6 months. Since you would be chasing us you can never
> catch up. If you managed to stay close then we'd put digital signatures
> into the protocol to prevent your clone from interoperating with BK.
I think it would be appropriate at this point to write a free client that talks with Bitkeeper, and for Linux developers to start switching to that from Bitkeeper. At that point, McVoy will face a hard choice: if he carries out these threats, he risks alienating the community that he hopes will market Bitkeeper for him. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Yup. So you can't release your program in PHP without providing the customer with its source code. But if you provide the source code, you may release it under whatever license you desire as section 6 says. But since the program you're going to sell IS its own source. The customer would receive the php source anyway.
Doh. Data layout on Amiga was very "dynamic" i.e. file header could've been located anywhere on the disk, even quite far from the file, and the "register" of them was in the middle of the floppy (and not at the end like FAT) so head movement to anywhere on the disk was at worst half a disk away. Anyway, you could have optimised the layout (there were programs for that) for file read speed - header next to the file, so you just read the header and immediately follow to the file, or for directory read speed, where all the headers were stored just by the index, so the drive could read them all at once to display - but need to move from each header to a file and back while copying files etc. Besides, if two programs at once attempted to read the same file, they started fighting over the drive head and the result was terribly slow and noisy operation.
One thing more I remember: You could hear the "knocking" of the drive while reading Amiga files twice as often as while reading PC. Reason: Two times higher speed. With PC files the track was changed every 4 floppy disk rotations, with Amiga - every 2 (1 per side). - so the reason was better filesystem performance, not worse file layout. The same amount of data readed in half the time so twice as much head movement needed.
Ah. And AFFS floppy was some 860K while PeeCee just 720:)
First off, AmigaDOS wasn't a filesystem but an OS layer. Amiga used Amiga Fast File System (and older Amigas used what was later called "Old File System".) AFFS was one of the best filesystems available at that time. Directory caching, long filenames with arbitrary characters, good speed, very good failure recovery tools, consistent "volumes" system (so you could "assign sys: ram: and continue using system as if it was booted from RamDisk), consistent device names (df0:, hd0:, ram:, com: etc), locking mechanisms (semaphores etc - obviously not necessary in single-tasking filesystem like M$-DOS, while pretty useful in multi-tasking Amiga), pretty advanced scripting language, and 8 different "permission bits". For that times, it was a dream of a filesystem for a multitasking single-user system. The 8.3 all-caps CR-LF 4-protection-bit single-tasking FAT was one of many reasons Amiga users laughed off PCs.
Doh! You miss the purpose! Everyone knew it's illegal and that was what was giving the thrill! Besides, using Amiga floppies this way seemed to be quite "elytist" since nobody in the post office ever caught anyone for sending floppies - Nobody in the PC'ised/deadtree post service could read the return address from the floppy! (and person who received the disk could be questioned about the originator but all they had to say was "I have no idea who does it come from" (which was true, until they read the floppy content too;) and they could do nothing about them:) Plus only FAILED faked stamp attempts were detected and these were a tiny margin, otherwise the method would be pretty useless (obviously, a detected fake wasn't delivered!). Much, much more floppies were getting lost in the mail service standard procedures, simply stolen by dishonest mail service workers, damaged in transport or simply never delivered. (did I mention I'm talking about Poland here?)
Besides - do you believe all that was on the floppies was legal?:)
...when the modems were scarce and phone bills high. Every more or less respectable demoscene group had a member whose function was listed as "swapper".
Swappers would get in contact with swappers from other groups, and exchange floppies full of newest stuff, productions, news, and everything of any interest (plus some exotic stuff other than floppies - a chicken bone, The Party membership ID, misprinted train tickets, and whatever interesting that caught the eye and filled the envelope up to (but not above) another price-weight treshold.)
One of the most specific swapper activities was "faking stamps". With 80 and more contacts, at least one letter a month exchanged with each of them, you had to cut on stamp prices, so you smeared the stamp with water-washable glue and wrote in the letter "stamps back", so your contact ripped your stamps off the envelope and sent you in his reply letter together with floppies. Then some washing and stamps could be reused - one set of stamps could go the same way 5-6 times before they needed to be replaced because they started looking suspect. And if it was found - you never put return address on the envelope and nobody in the post office could ever read an Amiga floppy:)
Another practice was making the floppies sent pretty. You almost never sent back the same floppies - they were in constant flow. Adding a marker signature was the default. Often some sticker or a drawing was common. But there were true masterpieces: A floppy painted gold, with the metal part (and under it) painted silver, the metal part without the spring but removable and attached with a thin chain to the write-protect hole, so you removed it before inserting and it was hanging from your floppy drive while the floppy was inside.
And finally all the "disk hunt" methods. Famous swappers were rarely replying to newbies who were asking for contact - you had to gain some fame on the scene with your group's productions - or get a recommendation from another swapper. So - the unanswered letters were a good supply of floppies. Sometimes they would even put an ad in some zine (spread by swapp of course;) which said a girl wants to swap, everyone welcome etc. This was bringing a good deal of free floppies, often with some quite funny stuff on them.
Well, Internet was what put end to it. Plus average data size - sending 6-8 floppies in one letter wasn't cheap or easy anymore, and with A1200 getting more common, high-level languages, multi-disk demos and mpeg movies, it became necessity...
Nowadays still throwing a CD across a computer lab is way faster than transferring the data over the net:)
...I'll send you a wonder inaudible dialtone that repels mosquitos, bears and Jehovah Witnesses, attracts women and money, makes people on crowded motorway drive off your way, reduces your body fat and makes you forever young. Additionally it's not only inaudible - its presence won't be shown on your phone in any way so no woman will find out you used this to attract it, and no mosquito will be attracted to shining display. Call now! 1-900-...
Q&D worked for the most successful company in the world, Microsoft, so apparently it's a good idea. Just make sure about your license agreement: "You can't hurt us, we can hurt you" and "All your money are belong to us", that's about all Microsoft has there and it seems sufficient.
The ADV: header isn't really useful, since the spam will be deleted only after the delivery, at the target machine. And let me cite after CAUCE:
Some junk emailers say, "Just hit the Delete key!" Unfortunately, the problem is much bigger than the time and effort of one person deleting a couple of emails. There are many different places along the process of transmitting and delivering email where costs are incurred. In the Internet world, "time" equals many different things besides the hourly rate that many people are still charged.
For example, for an Internet Service Provider, "time" includes the load on the processor in their mail servers; "CPU time" is a precious commodity and processor performance is a critical issue for ISPs. When their CPUs are tied up processing spam, it creates a drag on all of the mail in that queue -- wanted and unwanted alike. This is also a problem with "filtering" schemes; filtering email consumes vast amounts of CPU time and is the primary reason most ISPs cannot implement it as a strategy for eliminating junk email.
The problem is also compounded by the fact that ISPs purchase bandwidth -- their connection to the rest of the Internet -- based on their projected usage by their prospective user base. For most small to mid-sized ISPs, bandwidth costs are among one of the greatest portions of their budget and contributes to the reason why many ISPs have a tiny profit margin. Without junk email, greater consumption of bandwidth would normally track with increased numbers of customers. However, when an outside entity (e.g., the junk emailer) begins to consume an ISP's bandwidth, the ISP has few choices: 1) let the paying customers cope with slower internet access, 2) eat the costs of increasing bandwidth, or 3) raise rates. In short, the recipients are still forced to bear costs that the advertiser has avoided.
"Time" also makes for some other interesting problems, especially coupled with volume. Recent public comments by AOL are a useful point of reference: of the estimated 30 million email messages each day, about 30% on average was unsolicited commercial email. With volumes such as that, it's a tremendous burden shifted to the ISP to process and store that amount of data. Volumes like that may undoubtedly contribute to many of the access, speed, and reliability problems we've seen with lots of ISPs. Indeed, many large ISPs have suffered major system outages as the result of massive junk email campaigns. If huge outfits like Netcom and AOL can barely cope with the flood, it is no wonder that smaller ISPs are dying under the crush of spam.
Slashdot Mirror
...puts us in the new age of environmental consciousness.
Not only you can reuse the same parts of code on different platforms, but the Mozilla mailer is the first one to have separate folders for trash and junk.
Seduced, shaggy Samson snored.
She scissored short. Sorely shorn,
Soon shackled slave, Samson sighed,
Silently scheming,
Sightlessly seeking
Some savage, spectacular suicide.
-- Stanislaw Lem, "Cyberiad"
it was already slashdotted when I got there, luckily I "squeezed through" and got the text after hitting "reload" a few times, you moron.
you'd be surprised: It wasn't me (SF) who posted that comment. One of basic karma whore rules is "be quick". Doesn't give time to preview.
By the way, I appreciate a good troll and post some from time to time.
[i]That sounds waaaaaaaaay too much like Microsoft for me[/i]
Naah. Microsoft would never SAY such thing. (they do this secretly)
Err, sorry :) Replace all "developers.slashdot.org with lkml.org :)
... Mike Fedyk Scott Robert Ladd "J.A. Magallon" Alan Cox James Simmons "David S. Miller" (Eric W. Biederman) Jeff Garzik Mark Mielke Loup
Possible replies by: Rik van Riel "Trever L. Adams" Michael Buesch Shawn Shawn Larry McVoy Shawn Larry McVoy Jrn Engel Alan Cox "Trever L. Adams" Svein Ove Aas "Trever L. Adams" Alan Cox Valdis.Kletnieks@vt
Possible replies by: Rik van Riel Trever L. Adams Michael Buesch Shawn Shawn Larry McVoy Shawn Larry McVoy Jrn Engel Alan Cox Trever L. Adams Svein Ove Aas Trever L. Adams Alan Cox Valdis.Kletnieks@vt ... Mike Fedyk Scott Robert Ladd J.A. Magallon Alan Cox James Simmons David S. Miller (Eric W. Biederman) Jeff Garzik Mark Mielke From: Richard Stallman <rms@gnu ...>
From: Richard Stallman
e read the FAQ at http://www.tux.org/lkml/
To:
Subject: Bitkeeper
Cc:
Date: Fri, 18 Jul 2003 15:51:36 -0400
View all headers/Unparsed body/
Forward this mail to
> If you are trying to copy BK, give it up. We'll simply follow in the
> footsteps of every other company faced with this sort of thing and change
> the protocol every 6 months. Since you would be chasing us you can never
> catch up. If you managed to stay close then we'd put digital signatures
> into the protocol to prevent your clone from interoperating with BK.
I think it would be appropriate at this point to write a free client
that talks with Bitkeeper, and for Linux developers to start switching
to that from Bitkeeper. At that point, McVoy will face a hard choice:
if he carries out these threats, he risks alienating the community
that he hopes will market Bitkeeper for him.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at http://vger.kernel.org/majordomo-info.html
Pleas
go.to/phaser This non-military device easy to build at home will provide you with a lot of pleasure! Literally!
Yup. So you can't release your program in PHP without providing the customer with its source code. But if you provide the source code, you may release it under whatever license you desire as section 6 says.
But since the program you're going to sell IS its own source. The customer would receive the php source anyway.
So where's your problem?
Want 12Mbits for $21/sec? Move to Poland. (...) .For 12Mbit a month...
(it's not SO bad. But it's bad.)
You say putting program code in contents of jpeg (despite the fact it could work quite elsewhere just as well) is just a common practice?
See IOCCC for true masters of making the code unreadable!
It's Pizzaware!
(see point 1.8 for details)
Doh. Data layout on Amiga was very "dynamic" i.e. file header could've been located anywhere on the disk, even quite far from the file, and the "register" of them was in the middle of the floppy (and not at the end like FAT) so head movement to anywhere on the disk was at worst half a disk away. Anyway, you could have optimised the layout (there were programs for that) for file read speed - header next to the file, so you just read the header and immediately follow to the file, or for directory read speed, where all the headers were stored just by the index, so the drive could read them all at once to display - but need to move from each header to a file and back while copying files etc. Besides, if two programs at once attempted to read the same file, they started fighting over the drive head and the result was terribly slow and noisy operation.
:)
One thing more I remember: You could hear the "knocking" of the drive while reading Amiga files twice as often as while reading PC. Reason: Two times higher speed. With PC files the track was changed every 4 floppy disk rotations, with Amiga - every 2 (1 per side). - so the reason was better filesystem performance, not worse file layout. The same amount of data readed in half the time so twice as much head movement needed.
Ah. And AFFS floppy was some 860K while PeeCee just 720
First off, AmigaDOS wasn't a filesystem but an OS layer. Amiga used Amiga Fast File System (and older Amigas used what was later called "Old File System".) AFFS was one of the best filesystems available at that time. Directory caching, long filenames with arbitrary characters, good speed, very good failure recovery tools, consistent "volumes" system (so you could "assign sys: ram: and continue using system as if it was booted from RamDisk), consistent device names (df0:, hd0:, ram:, com: etc), locking mechanisms (semaphores etc - obviously not necessary in single-tasking filesystem like M$-DOS, while pretty useful in multi-tasking Amiga), pretty advanced scripting language, and 8 different "permission bits".
For that times, it was a dream of a filesystem for a multitasking single-user system. The 8.3 all-caps CR-LF 4-protection-bit single-tasking FAT was one of many reasons Amiga users laughed off PCs.
Most of our labs work on 10mbit and don't reach even that reliably. Mostly because of amateurish wiring ;)
Doh! You miss the purpose! Everyone knew it's illegal and that was what was giving the thrill! Besides, using Amiga floppies this way seemed to be quite "elytist" since nobody in the post office ever caught anyone for sending floppies - Nobody in the PC'ised/deadtree post service could read the return address from the floppy! (and person who received the disk could be questioned about the originator but all they had to say was "I have no idea who does it come from" (which was true, until they read the floppy content too ;) and they could do nothing about them :) Plus only FAILED faked stamp attempts were detected and these were a tiny margin, otherwise the method would be pretty useless (obviously, a detected fake wasn't delivered!). Much, much more floppies were getting lost in the mail service standard procedures, simply stolen by dishonest mail service workers, damaged in transport or simply never delivered. (did I mention I'm talking about Poland here?)
:)
Besides - do you believe all that was on the floppies was legal?
You may find RFC 1149 useful:
"A Standard for the Transmission of IP Datagrams on Avian Carriers}
Note this would have the same times:
PING privaria.org (64.33.49.48) 10000000000000 (10000000000028) bytes of data.
Breaking the IP specs about MTU size though.
...when the modems were scarce and phone bills high. Every more or less respectable demoscene group had a member whose function was listed as "swapper".
:)
;) which said a girl wants to swap, everyone welcome etc. This was bringing a good deal of free floppies, often with some quite funny stuff on them.
:)
Swappers would get in contact with swappers from other groups, and exchange floppies full of newest stuff, productions, news, and everything of any interest (plus some exotic stuff other than floppies - a chicken bone, The Party membership ID, misprinted train tickets, and whatever interesting that caught the eye and filled the envelope up to (but not above) another price-weight treshold.)
One of the most specific swapper activities was "faking stamps". With 80 and more contacts, at least one letter a month exchanged with each of them, you had to cut on stamp prices, so you smeared the stamp with water-washable glue and wrote in the letter "stamps back", so your contact ripped your stamps off the envelope and sent you in his reply letter together with floppies. Then some washing and stamps could be reused - one set of stamps could go the same way 5-6 times before they needed to be replaced because they started looking suspect. And if it was found - you never put return address on the envelope and nobody in the post office could ever read an Amiga floppy
Another practice was making the floppies sent pretty. You almost never sent back the same floppies - they were in constant flow. Adding a marker signature was the default. Often some sticker or a drawing was common. But there were true masterpieces: A floppy painted gold, with the metal part (and under it) painted silver, the metal part without the spring but removable and attached with a thin chain to the write-protect hole, so you removed it before inserting and it was hanging from your floppy drive while the floppy was inside.
And finally all the "disk hunt" methods. Famous swappers were rarely replying to newbies who were asking for contact - you had to gain some fame on the scene with your group's productions - or get a recommendation from another swapper. So - the unanswered letters were a good supply of floppies. Sometimes they would even put an ad in some zine (spread by swapp of course
Well, Internet was what put end to it. Plus average data size - sending 6-8 floppies in one letter wasn't cheap or easy anymore, and with A1200 getting more common, high-level languages, multi-disk demos and mpeg movies, it became necessity...
Nowadays still throwing a CD across a computer lab is way faster than transferring the data over the net
...I'll send you a wonder inaudible dialtone that repels mosquitos, bears and Jehovah Witnesses, attracts women and money, makes people on crowded motorway drive off your way, reduces your body fat and makes you forever young. Additionally it's not only inaudible - its presence won't be shown on your phone in any way so no woman will find out you used this to attract it, and no mosquito will be attracted to shining display. Call now! 1-900-...
Q&D worked for the most successful company in the world, Microsoft, so apparently it's a good idea. Just make sure about your license agreement: "You can't hurt us, we can hurt you" and "All your money are belong to us", that's about all Microsoft has there and it seems sufficient.
Now imagine any "false positive" blocked at ISP's server. Would get people rather angry, wouldn't it?
The ADV: header isn't really useful, since the spam will be deleted only after the delivery, at the target machine. And let me cite after CAUCE:
Some junk emailers say, "Just hit the Delete key!" Unfortunately, the problem is much bigger than the time and effort of one person deleting a couple of emails. There are many different places along the process of transmitting and delivering email where costs are incurred. In the Internet world, "time" equals many different things besides the hourly rate that many people are still charged.
For example, for an Internet Service Provider, "time" includes the load on the processor in their mail servers; "CPU time" is a precious commodity and processor performance is a critical issue for ISPs. When their CPUs are tied up processing spam, it creates a drag on all of the mail in that queue -- wanted and unwanted alike. This is also a problem with "filtering" schemes; filtering email consumes vast amounts of CPU time and is the primary reason most ISPs cannot implement it as a strategy for eliminating junk email.
The problem is also compounded by the fact that ISPs purchase bandwidth -- their connection to the rest of the Internet -- based on their projected usage by their prospective user base. For most small to mid-sized ISPs, bandwidth costs are among one of the greatest portions of their budget and contributes to the reason why many ISPs have a tiny profit margin. Without junk email, greater consumption of bandwidth would normally track with increased numbers of customers. However, when an outside entity (e.g., the junk emailer) begins to consume an ISP's bandwidth, the ISP has few choices: 1) let the paying customers cope with slower internet access, 2) eat the costs of increasing bandwidth, or 3) raise rates. In short, the recipients are still forced to bear costs that the advertiser has avoided.
"Time" also makes for some other interesting problems, especially coupled with volume. Recent public comments by AOL are a useful point of reference: of the estimated 30 million email messages each day, about 30% on average was unsolicited commercial email. With volumes such as that, it's a tremendous burden shifted to the ISP to process and store that amount of data. Volumes like that may undoubtedly contribute to many of the access, speed, and reliability problems we've seen with lots of ISPs. Indeed, many large ISPs have suffered major system outages as the result of massive junk email campaigns. If huge outfits like Netcom and AOL can barely cope with the flood, it is no wonder that smaller ISPs are dying under the crush of spam.