No, Stallman is pushing this thing because its modular and relies on the Mach microkernel and the Flux OSKit library, in stark contrast to Linux's monolithic kernel design. Not to say monolithic kernels are bad, but microkernels do have their advantages, and both GNU/Hurd and GNU/Linux will each have their respective pros and cons.
Anyone have any luck compressing SAML-encoded security assertions, or any use of XML for that matter? Maybe I'm old-fashioned, but to me having a plethora of XML tags without abbreviations of any kind is an inadequate use of the ASCII encoding character space. Which is clearer?
D. E. Knuth,
The art of computer programming. Vol. 2, Seminumerical algorithms, third ed., Addison-Wesley Series in Computer Science and Information Processing. Addison-Wesley, Reading, MA, 1997.
or:
<citation>
<author><sirname>Knuth</sirname><givenname>Donald</givenname><middlename>Ervin</middlename>
<entitled>Art of Computer Programming, The</entitled>
<volume>2<volume>
<subtitle>Seminumerical Algorithms</subtitle>
<edition><ordinal>3</ordinal></edition> ;
<excerpt>Addison-Wesley Series in Computer Science and Information Processing</excerpt>
<publisher>Addison-Wesley</publisher>
<publishers_house>Reading, MA</publishers_house>
<year>1997</year>
I'm not knocking XML--but you have to admit it is extremely verbose compared to terse standard syntaxen available today. If one can combine the flexibility of XML with the tersity of unstructured documents, we'll in for a datum revolution.
I agree yEnc was a quick hack, but it does work, and people are downloading yEncoded DivX movies off Usenet right now.
Not all newsreaders or browsers support yEnc yet, but Forte Agent does, and your newsreader should too. There is even a plug-in for Outlook Express. If worst comes to worse, one can always manually yDecode the file using YDEC.EXE.
Audiogalaxy History Lesson: Push Technology=Good++
on
E-Mail Size Limits?
·
· Score: 2
Just to show you there's no hard feelings, I have e-mailed you a copy of this great new game I have called Grand Theft Auto 3.
Warez-by-mail, I love it already! Seriously I believe this an excellent idea. Anyone old enough to remember when Audiogalaxy was running at full capacity? You could join groups. That was sweet. Not only could you chat with other's either publically or privately about music interests, you could join sending groups! Anyone could send a MP3s to the whole group. Dedicated groups where created and you joined them if you wanted a specific album, among other things. Imagine the possibilities.
This eventually lead to spammers sending viruses--and several groups, Owners Protection, Anti-Spam, etc. where created to blacklist spammers those users. A guy I worked with registered a new Audiogalaxy account every couple months in order to map user ID numbers (which where numerically sequential) into a ballpark figure of the date in which the user registered, and you had to be an Audiogalaxy member for a few months to get into certain groups. This was all to prevent spammers sending unsoliciated music to the entire group, but all-in-all the "group" philosophy of Audiogalaxy was one-of-a-kind. It was wonderful.
(Michael--the owner of AG--was working on limiting which members could send files to the groups, but he never got around to it before the demise from the RIAA. Of course, AG group's analogy in this case--mailing lists--,which I'm sure you are aware, can have sending restricted to certain users, thus avoiding spam. Spam is now irrelevant, I only mention it as a footnote in Audiogalaxy history.)
Not only could you join groups to have the owners share their favorite albums (often, sometimes compilations) with you, you could join so-called "free-send" groups where anyone could send anyone any file. That was kinda neat, if you had a nice song you could send it to the group and see what others thunk, especially if you're the one that recorded it. I learned about plenty of independent musicians this way.
And the perhaps most important thing that came out of Audiogalaxy's groups is: you got 0-day. Before The Eminem Show came out, I vividly remember hundreds, even thousands of fellow fans joining, eagarly waiting for the album to come out. When it dropped, members of our sending group got it first. I left my satellite on 24/7, and it starting downloaded immediately within hours of its release. I was amazed. Audiogalaxy has beaten IRC. No other P2P technology has shined so well in this regard, in fact, P2P is often now looked upon as a place to get old stuff, not 0-day.
That's not to say there is no room for improvements. On the contrary, there are plenty of improvements which could be made on the old SMTP protocol. Audiogalaxy, being peer-to-peer, was smart enough to download from other peers once they picked up the file, alleviating uploading from the original sender. This meant someone with connections but a 56K modem could leak The Eminem Show to an AG group, and it would be sent to a couple people. Those people would then be sharing it for others. Eventually, the entire group had it! And this is what was intended; if you didn't want the CD you didn't join that group. (Joining and leaving groups was easy).
Didn't mean to write a book there, but I hope I proved my point. Push technology is kick-ass. Forget your silly pull FTP and HTTP! Its good, but I want to subscribe to a warez mailing list, and get warez when it comes out. I have a fast enough connection, I laugh at all those sysadmins who say their servers can't handle >5MB attachments. Mine can, and the warez community will be able to, without a trace of a doubt.
As aside, the NNTP protocol behind Usenet seems to be similar to Audiogalaxy groups, but not similar enough. The peers are not individual users but individual dedicated servers. Usenet is also way too uncontrolled, even with moderators. I'd prefer SMTP mailing lists. Now we just need to find a way to make SMTP attachments be distributed over willing users...hey look! Bit Torrent!.
Warez by mail. You heard it here first. (Note that although warez has a negative connotation, especially legally, it is a big sucker of bandwidth. And once warez pioneers the P2P email, the world of legal uses will follow!)
Re:"Email cannot serve as ... file transfer"
on
E-Mail Size Limits?
·
· Score: 2
I don't know of any sysadmin who's setup can be brought down by a large email attachment
Read the rest of the comments to this article. You will see plenty of cases of sysadmins discussing problems with servers going down due to large file attachments.
Maybe you should read the rest of gruntvald's comment, eric. Like he said, maybe its your sysadmin that needs training?
What, your network can't handle N bits at once? Your 100MHz PII is the problem, not SMTP. Since when does an Internet protocol technology have arbitrary limits?
many serial connections used characters 0-31 for signaling (with XON and XOFF being only the best-known) -- sending a file containing these characters might hang or abort your connection.
So encode only those characters which hang or abort your connection! Not all 0-31. No one uses serious serial lines anymore. IP is 8-bit clean. This amateur hack-job is the best solution proposed yet. Don't like it? Propose something better.
SMTP was never designed to handle binary files at all, which is why binary files are encoded into text, which increases their size by 30%.
I'm still waiting for yEnc to be officially incorporated into Outlook and other e-mail clients and recognized automatically. XXE/UUE/Base64 adds 30-40% overhead, while yEnc offers 1-2%. All communication channels on the Internet today are nearly 8-bit clean, but certain characters cannot pass through unmolested - yEnc only encodes such characters.
yEnc has shown widespread acceptance in Usenet, I'd like to see it used as the de-facto format for SMTP mail. Electronic mail's "push" nature makes it extremely useful where FTP/HTTP is not (although IRC DCC is) and I'd enjoy having the pleasure of subscribing to mailing lists which send out multimedia or other forms of large content and having it delivered, just like postal mail, right to my desktop or a nearby ISP mail server. Who is with me?
Internet Relay Chat. There are currently two major Ogg Vorbis-only releasing groups and several minor (one-person) "groups" which often have their own IRC channels with iroffer XDCC's and private FTP's. I'm not going to mention their channels and IRC network which they reside on for security reasons, but here's a hint: Team Inaniation Network and Ogg Ripping Network. I'll leave you to find their location.
My apologies for replying twice, but I tried conv=noerror,sync on my BSD box and dd was able to read the entire disk image! I've been trying to recover this disk for months now; it held several important files and source code I programmed when I was 11. Thank you very much kind sir.
Funny thing is, the only hard errors where in at fsbn 113664 and 113840. The rest of the disk was flawless, but since the FAT media descriptor was damaged I can't view the disk with DOS or mount_msdos. And even more comical:
microuptime() went backwards (439.452644 -> 439.-694925999)
microuptime() went backwards (495.644229 -> 495.-694728800) ....
calcru: negative time of -695354479 usec for pid 7777 (ls)
That's kinda weird, its supposedly fixed in 5.0, I'm running the 4.7 branch with up-to-the-second CVS.
"A Word of Warning From A Caught Uncapper"
by Kris Olsen
Bored during my summer, I thought I would take this project on. I began my research on June 26, before 2600 published the article on uncapping. Through various methods (mainly IRC), I talked to several people and finally figured out how to uncap my modem. Well, it wasn't as easy as it seems.
I went to a lot of trouble that in the end left me without cable and nearly in jail.
My ISP, like many, uses a system called QoS, or Quality of Service. This means a few things.
1) You can't connect without a config that the ISP doesn't already have (i.e., you can't create a config file with a 10mbit/10mbit line if the cable company only offers 400/200 800/400 and 1.5/512). This means in order to uncap, you can only uncap to a better service plan (i.e., going from 400/200 to 1.5/512).
2) In order to uncap to a better service plan you must get the config for that service plan, as making one with those caps often will not work. Take note, this config file has a different name than the one sent to your modem, and since the TFTP protocol doesn't allow directory listing, you must either have once used the faster service and seen the config file, or you have to know someone who has it who can help you out. Should you manage to get this config file, your problems are still not over.
3) The QoS checks your modem's MAC address every 10-15 minutes (depending on the size of your node) to make sure that the parameters set in your modem are the ones that you pay for. Note: the MAC cannot be changed because you have to register your MAC with the ISP, s they inevitably know who you are. To get around the QoS resetting your modem, one may think "Well hay, let's just change the SNMP ports so they can't send the reboot command to me!" Hah! That pisses them off like nothing else, and yes, they can track that. All it takes is about a day to find your port. The default SNMP ports are 161 and 162. I changed minme to 9999999941 and 9999999942. In two days they were once again resetting via SNMP.
4) So you figure, "Well, that means I have one or two days of uncapped modem, right?" Wrong. There is another way they can reset you that you can do nothing about. In order for your modem to stay connected to the server it must "ping" the server and get responses back. I say "ping" in quotations since it is not your normal 52 byte packet ping. It is a special CMTS type ping. What the ISP can do, should they notice that you are indeed using a faster config, is "suspend" the "pings," meaning that they are lost, and none come back to the modem. This will force an "HFC: Async Error Range Failed" error on your modem's long, which will be followed by "HFC: Shutting Upstream Down," and then "BOOTING: (firmware version)."
So now, this doesn't seem that bad. You may be thinking, "Why is this guy even writing this stuff - if there is a will there is a way." That is true, but my purpose is to show you that if your ISP does use QoS (examples of some that do are: Blueyonder, ATTBI, Cableone, Charter, Comcast, and NTL) then if you ever attempt ot uncap, they will notice and they will call you.
I received my first call the morning after I requested tech support to come out and fix the signal strength of my line (it was way out of spec and kept resetting my modem). Well, as protocol they watch your line to see what they can diagnose before the tech arrived at your house. Well that morning (the 10th of July), I uncapped and within ten minutes I had a call from the headquarters of my ISP, some 600 miles away. This was a "tap on the wrist" type conversation. They said basically, we see that you are uncapping, and that violates our Terms of Service agreement. Don't do it again. So I didn't for a while.
A couple of weeks went by and I used Ethereal, I common network "sniffer", to determine whether or not my ISP was watching my MAC address. Later I learned they were on the entire time and when they saw me "Sniffing" for info, they simply hid themselves behind the IP address 255.255.255.254. Not knowing that information, I decided it was safe to uncap again. And so I did and continued to be reset with HFC errors. I tried various methods to get around it, installed hacked firmware, sent various SNMP commands, even attempted to fake a CMTP server so that the CM would send the "pings" to a computer on my LAN, all to no avail. So when my modem would go back to normal, I would send it a new config, and the process went on and on like that for two weeks or so.
I left early on a Friday morning for a little weekend getaway. While I was out of town, I didn't even think about the status of my cable. No, I did not leave it uncapped when I left the house, but the damage had already been done. My ISP had all the evidence they needed to shut my cable off, and press misdemeaner charges, mainly based on cyber theft.
I returned to find a message on my answering machine from an "Internet Engineer" at the ISP's headquarters. He was not very pleased. The message was over 15 minutes long and contained a great deal of threats and comments obviously designed to scare an uncapped. It worked. I was terrified. After hearing the message, I went out to check the mail. In there was an envelope from my ISP containing a "Declaration of Termination of Service." In this letter were several items, including possible criminal charges to be pressed, two pages dealing every time I uncapped from July 10 to the present, and a long, long list of how I violated the Terms of Service with my ISP. Sure enough, when I went to contact the Internet Engineer by email, (the only contact information that was listed), my Internet service did not work. As a routing check, I looked at my modem's long file only to find this disturbing messsage: 7-Information D509.0 Retreived TFTP Config TRMNT.cm SUCCESS.
I twas clear. My service had been terminated. But my problems were not over yet.
The following day (August 5) I received another call from him, telling me that the ISP wanted to press charges. As soon as I was off the phone I immediately called my lawyer and told him the entire situation. My lawyer spent the rest of the day on the phone with my ISP and came to an agreement that for the two months that I uncapped, I would have to pay for the better service.
In the end, uncapping got me these final results:
Pros:
200+ KBps downloads (needing to be reconfigured every 35 minutes)
100+ KBps uploads (needing to be reconfigured every 35 minutes).
Cons:
No more cable Internet.
Almost got charges pressed.
Ended up wasting about 150 hours of my life to no avail.
Had to deal with really pissed off nerds with power.
The choice is up to you. This was just my experience.
----
Reprinted from 2600: The Hacker Quarterly, Volume 19, Number 3, Fall 2002 without permission. Even though Olsen's account obviously has some glaring mistakes (52-byte ping? Since when is the payload fixed? He probably means an ICMP ping.), I believe it provides an interesting account into what can happen if you're uncapped. Maybe not as drastic as the visit from the FBI in this Slashdot article, but certainly uncapping is still not worth it. Especially when your cable provider is a monopoly!
First and foremost, I would like to thank you for your response. I had not expected an authoritive reply from the author himself.:)
But if you look at the dd stats I provided above, you'll see only 29 or so blocks where output. I have a fairly small disk, but it was very disheartening to know that only 27MB could be recovered off my 6GB disk. I realize G4U isn't a...hey wait, I just read my other post and someone said dd will ignore the errors if passed conv=noerror,sync. I would suggest you implement such an option in G4U, it would give folks like me who have bad hard disks they want to mirror laying around a lot less headaches:).
Cheers, and congrats with the nice utility,
Istealmymusic
wd0: (uncorrectable data error)
wd0: transfer error, downgrading to PIO mode 4
wd0(pciide0:0:1): using PIO mode 4
wd0d: error reading fsbn 56960 of 56960-57087 (wd0 bn 569760; cn 60 tn 4 sn 8); retrying ...
dd:/dev/rwd0d: Input/output error
27+0 records in
27+0 records out
28311552 bytes transferred in 41.015 secs (690273 bytes/sec)
226 Transfer complete.
8087791 bytes sent in 00:37 (211.08 KB/s)
221 Goodbye.
rm: not found
#
Any help?
Thank you. What's coming to Slashdot these days? Confuse Netrek with Nethack and become lambasted en masse and typecast troll. Netrek was indeed what I was referring to, I apologize for anyone which was mislead by my comment, and commend you for having set me straight.
How is the 4th Annual NetHack Tournament committe planning on handling the scourage of the gaming field that is cheaters, flooders, packeteers, and other undesirables? Denial-of-Service is unavoidable, but preventing gamers from modifying the client executable (given the fact that the source is freely available) to achieve higher scores, go through walls (similar to Doom II's IDCLIP walk-through-walls code), or acquire inventory out of thin air? Often, the NetHack executable is signed with a cryptographic hash which is used to verify authentic, genuine, non-modified executables to the server, how reliable is this--and what will the NetHack Tournament ringleaders be using?
Slashdot Mirror
You better hope the rechargable battery is solid-state. Otherwise, overload the power source and you'll have acid eating away at your bits.
system.ini: /L:R /S:64M
device=vdrive.sys
...anti-hate laws.
No, Stallman is pushing this thing because its modular and relies on the Mach microkernel and the Flux OSKit library, in stark contrast to Linux's monolithic kernel design. Not to say monolithic kernels are bad, but microkernels do have their advantages, and both GNU/Hurd and GNU/Linux will each have their respective pros and cons.
Voice Over ICMP. Ingenius. ICMP can be used as a covent data channel, there is a nice article in Phrack, highly recommended.
Not all newsreaders or browsers support yEnc yet, but Forte Agent does, and your newsreader should too. There is even a plug-in for Outlook Express. If worst comes to worse, one can always manually yDecode the file using YDEC.EXE.
This eventually lead to spammers sending viruses--and several groups, Owners Protection, Anti-Spam, etc. where created to blacklist spammers those users. A guy I worked with registered a new Audiogalaxy account every couple months in order to map user ID numbers (which where numerically sequential) into a ballpark figure of the date in which the user registered, and you had to be an Audiogalaxy member for a few months to get into certain groups. This was all to prevent spammers sending unsoliciated music to the entire group, but all-in-all the "group" philosophy of Audiogalaxy was one-of-a-kind. It was wonderful.
(Michael--the owner of AG--was working on limiting which members could send files to the groups, but he never got around to it before the demise from the RIAA. Of course, AG group's analogy in this case--mailing lists--,which I'm sure you are aware, can have sending restricted to certain users, thus avoiding spam. Spam is now irrelevant, I only mention it as a footnote in Audiogalaxy history.)
Not only could you join groups to have the owners share their favorite albums (often, sometimes compilations) with you, you could join so-called "free-send" groups where anyone could send anyone any file. That was kinda neat, if you had a nice song you could send it to the group and see what others thunk, especially if you're the one that recorded it. I learned about plenty of independent musicians this way.
And the perhaps most important thing that came out of Audiogalaxy's groups is: you got 0-day. Before The Eminem Show came out, I vividly remember hundreds, even thousands of fellow fans joining, eagarly waiting for the album to come out. When it dropped, members of our sending group got it first. I left my satellite on 24/7, and it starting downloaded immediately within hours of its release. I was amazed. Audiogalaxy has beaten IRC. No other P2P technology has shined so well in this regard, in fact, P2P is often now looked upon as a place to get old stuff, not 0-day.
That's not to say there is no room for improvements. On the contrary, there are plenty of improvements which could be made on the old SMTP protocol. Audiogalaxy, being peer-to-peer, was smart enough to download from other peers once they picked up the file, alleviating uploading from the original sender. This meant someone with connections but a 56K modem could leak The Eminem Show to an AG group, and it would be sent to a couple people. Those people would then be sharing it for others. Eventually, the entire group had it! And this is what was intended; if you didn't want the CD you didn't join that group. (Joining and leaving groups was easy).
Didn't mean to write a book there, but I hope I proved my point. Push technology is kick-ass. Forget your silly pull FTP and HTTP! Its good, but I want to subscribe to a warez mailing list, and get warez when it comes out. I have a fast enough connection, I laugh at all those sysadmins who say their servers can't handle >5MB attachments. Mine can, and the warez community will be able to, without a trace of a doubt.
As aside, the NNTP protocol behind Usenet seems to be similar to Audiogalaxy groups, but not similar enough. The peers are not individual users but individual dedicated servers. Usenet is also way too uncontrolled, even with moderators. I'd prefer SMTP mailing lists. Now we just need to find a way to make SMTP attachments be distributed over willing users...hey look! Bit Torrent!.
Warez by mail. You heard it here first. (Note that although warez has a negative connotation, especially legally, it is a big sucker of bandwidth. And once warez pioneers the P2P email, the world of legal uses will follow!)
What, your network can't handle N bits at once? Your 100MHz PII is the problem, not SMTP. Since when does an Internet protocol technology have arbitrary limits?
I have never stumbled across this term before, does it refer to an xbox game or something? I'd like more information.
yEnc has shown widespread acceptance in Usenet, I'd like to see it used as the de-facto format for SMTP mail. Electronic mail's "push" nature makes it extremely useful where FTP/HTTP is not (although IRC DCC is) and I'd enjoy having the pleasure of subscribing to mailing lists which send out multimedia or other forms of large content and having it delivered, just like postal mail, right to my desktop or a nearby ISP mail server. Who is with me?
Internet Relay Chat. There are currently two major Ogg Vorbis-only releasing groups and several minor (one-person) "groups" which often have their own IRC channels with iroffer XDCC's and private FTP's. I'm not going to mention their channels and IRC network which they reside on for security reasons, but here's a hint: Team Inaniation Network and Ogg Ripping Network. I'll leave you to find their location.
Funny thing is, the only hard errors where in at fsbn 113664 and 113840. The rest of the disk was flawless, but since the FAT media descriptor was damaged I can't view the disk with DOS or mount_msdos. And even more comical:
microuptime() went backwards (439.452644 -> 439.-694925999)
....
microuptime() went backwards (495.644229 -> 495.-694728800)
calcru: negative time of -695354479 usec for pid 7777 (ls)
That's kinda weird, its supposedly fixed in 5.0, I'm running the 4.7 branch with up-to-the-second CVS.
Can someone explain why this filter would be useful to me?
by Kris Olsen
Bored during my summer, I thought I would take this project on. I began my research on June 26, before 2600 published the article on uncapping. Through various methods (mainly IRC), I talked to several people and finally figured out how to uncap my modem. Well, it wasn't as easy as it seems.
I went to a lot of trouble that in the end left me without cable and nearly in jail.
My ISP, like many, uses a system called QoS, or Quality of Service. This means a few things.
1) You can't connect without a config that the ISP doesn't already have (i.e., you can't create a config file with a 10mbit/10mbit line if the cable company only offers 400/200 800/400 and 1.5/512). This means in order to uncap, you can only uncap to a better service plan (i.e., going from 400/200 to 1.5/512).
2) In order to uncap to a better service plan you must get the config for that service plan, as making one with those caps often will not work. Take note, this config file has a different name than the one sent to your modem, and since the TFTP protocol doesn't allow directory listing, you must either have once used the faster service and seen the config file, or you have to know someone who has it who can help you out. Should you manage to get this config file, your problems are still not over.
3) The QoS checks your modem's MAC address every 10-15 minutes (depending on the size of your node) to make sure that the parameters set in your modem are the ones that you pay for. Note: the MAC cannot be changed because you have to register your MAC with the ISP, s they inevitably know who you are. To get around the QoS resetting your modem, one may think "Well hay, let's just change the SNMP ports so they can't send the reboot command to me!" Hah! That pisses them off like nothing else, and yes, they can track that. All it takes is about a day to find your port. The default SNMP ports are 161 and 162. I changed minme to 9999999941 and 9999999942. In two days they were once again resetting via SNMP.
4) So you figure, "Well, that means I have one or two days of uncapped modem, right?" Wrong. There is another way they can reset you that you can do nothing about. In order for your modem to stay connected to the server it must "ping" the server and get responses back. I say "ping" in quotations since it is not your normal 52 byte packet ping. It is a special CMTS type ping. What the ISP can do, should they notice that you are indeed using a faster config, is "suspend" the "pings," meaning that they are lost, and none come back to the modem. This will force an "HFC: Async Error Range Failed" error on your modem's long, which will be followed by "HFC: Shutting Upstream Down," and then "BOOTING: (firmware version)."
So now, this doesn't seem that bad. You may be thinking, "Why is this guy even writing this stuff - if there is a will there is a way." That is true, but my purpose is to show you that if your ISP does use QoS (examples of some that do are: Blueyonder, ATTBI, Cableone, Charter, Comcast, and NTL) then if you ever attempt ot uncap, they will notice and they will call you.
I received my first call the morning after I requested tech support to come out and fix the signal strength of my line (it was way out of spec and kept resetting my modem). Well, as protocol they watch your line to see what they can diagnose before the tech arrived at your house. Well that morning (the 10th of July), I uncapped and within ten minutes I had a call from the headquarters of my ISP, some 600 miles away. This was a "tap on the wrist" type conversation. They said basically, we see that you are uncapping, and that violates our Terms of Service agreement. Don't do it again. So I didn't for a while.
A couple of weeks went by and I used Ethereal, I common network "sniffer", to determine whether or not my ISP was watching my MAC address. Later I learned they were on the entire time and when they saw me "Sniffing" for info, they simply hid themselves behind the IP address 255.255.255.254. Not knowing that information, I decided it was safe to uncap again. And so I did and continued to be reset with HFC errors. I tried various methods to get around it, installed hacked firmware, sent various SNMP commands, even attempted to fake a CMTP server so that the CM would send the "pings" to a computer on my LAN, all to no avail. So when my modem would go back to normal, I would send it a new config, and the process went on and on like that for two weeks or so.
I left early on a Friday morning for a little weekend getaway. While I was out of town, I didn't even think about the status of my cable. No, I did not leave it uncapped when I left the house, but the damage had already been done. My ISP had all the evidence they needed to shut my cable off, and press misdemeaner charges, mainly based on cyber theft.
I returned to find a message on my answering machine from an "Internet Engineer" at the ISP's headquarters. He was not very pleased. The message was over 15 minutes long and contained a great deal of threats and comments obviously designed to scare an uncapped. It worked. I was terrified. After hearing the message, I went out to check the mail. In there was an envelope from my ISP containing a "Declaration of Termination of Service." In this letter were several items, including possible criminal charges to be pressed, two pages dealing every time I uncapped from July 10 to the present, and a long, long list of how I violated the Terms of Service with my ISP. Sure enough, when I went to contact the Internet Engineer by email, (the only contact information that was listed), my Internet service did not work. As a routing check, I looked at my modem's long file only to find this disturbing messsage: 7-Information D509.0 Retreived TFTP Config TRMNT.cm SUCCESS.
I twas clear. My service had been terminated. But my problems were not over yet.
The following day (August 5) I received another call from him, telling me that the ISP wanted to press charges. As soon as I was off the phone I immediately called my lawyer and told him the entire situation. My lawyer spent the rest of the day on the phone with my ISP and came to an agreement that for the two months that I uncapped, I would have to pay for the better service.
In the end, uncapping got me these final results:
Pros:
Cons:
The choice is up to you. This was just my experience.
----
Reprinted from 2600: The Hacker Quarterly, Volume 19, Number 3, Fall 2002 without permission. Even though Olsen's account obviously has some glaring mistakes (52-byte ping? Since when is the payload fixed? He probably means an ICMP ping.), I believe it provides an interesting account into what can happen if you're uncapped. Maybe not as drastic as the visit from the FBI in this Slashdot article, but certainly uncapping is still not worth it. Especially when your cable provider is a monopoly!
dd: conv option disabled
?Invalid command.
No dice. I'm gonna have to try those flags on my BSD box; I hadn't realized they exist but may be exactly what I'm looking for. Thanks!
But if you look at the dd stats I provided above, you'll see only 29 or so blocks where output. I have a fairly small disk, but it was very disheartening to know that only 27MB could be recovered off my 6GB disk. I realize G4U isn't a ...hey wait, I just read my other post and someone said dd will ignore the errors if passed conv=noerror,sync. I would suggest you implement such an option in G4U, it would give folks like me who have bad hard disks they want to mirror laying around a lot less headaches :).
Cheers, and congrats with the nice utility,
Istealmymusic
wd0: (uncorrectable data error)
... /dev/rwd0d: Input/output error
wd0: transfer error, downgrading to PIO mode 4
wd0(pciide0:0:1): using PIO mode 4
wd0d: error reading fsbn 56960 of 56960-57087 (wd0 bn 569760; cn 60 tn 4 sn 8); retrying
dd:
27+0 records in
27+0 records out
28311552 bytes transferred in 41.015 secs (690273 bytes/sec)
226 Transfer complete.
8087791 bytes sent in 00:37 (211.08 KB/s)
221 Goodbye.
rm: not found
#
Any help?
...moderate this post down! Thank you.
Kernel panics with "failed to read sector ######" when mirroring a broken hard disk. Any workarounds?
Cheers,
Istealmymusic
How is the 4th Annual NetHack Tournament committe planning on handling the scourage of the gaming field that is cheaters, flooders, packeteers, and other undesirables? Denial-of-Service is unavoidable, but preventing gamers from modifying the client executable (given the fact that the source is freely available) to achieve higher scores, go through walls (similar to Doom II's IDCLIP walk-through-walls code), or acquire inventory out of thin air? Often, the NetHack executable is signed with a cryptographic hash which is used to verify authentic, genuine, non-modified executables to the server, how reliable is this--and what will the NetHack Tournament ringleaders be using?
I watch Friends but not Ally, what would that make me?