Either print the barcode directly on the disc with an inkjet or use the Avery labels for CDs. They even make printable labels that go on the little portion of the CD in the center (not the hole).
I went the no-tech and lazy way. I bought a bunch of the tyvek sleeves. I don't write on the sleeves, but I write directly on the disc with a marker. I throw the CD in any available sleeve, and put it in some reasonable order. I can usually find something quickly, but sometimes it takes a while.
Unless you're some sort of clean-o-maniac who lives for everything to have a place, realize it's a crappy media for storing in bulk and do something that gets you most of what you want. If you take 40 hours over a span of time to organize this stuff are you ever going to recoup that time? I don't know how often I've gone overboard for this stuff.
With Linux ported to so many other processors and hardware arrangements you're not thinking in a proper way. Instead of asking how to make an X86 box without components that are essential to it's longevity, you should be looking at your goal and work backwards from there. Hell, you may even find out Linux is not your answer. (gasp!)
I think Rebel.com has done an excellent job with the Netwinder. It's a small computer using a SA1100 StrongARM processor. It's the same processor used in the Empeg car audio player and can do what you want and much more. It not only runs Linux, but it was designed specifically for Linux. I had a chance to talk with them at Linux World and I can tell you they're a small shop full of good people.
You may also look at the LART project being done in TuDelft, Netherlands. I don't think they're selling anything (yet?) but it's nice to see Linux on a small processor capable of some real power. I don't have a link handy, oops.
Or, you could use a uCsimm. It's a port of Linux to the Dragonball microcontroller with integrated Ethernet. It all fits on a 30 pin simm complete with Flash. I consider that to be really cool. There are many more choices out there than plain ol' Linux on x86. Don't limit yourself.
As an administrator of a couple mid sized ISP's I think your approach is not only detrimental to the entire Internet but plain childish.
Most often the souce of the packets is spoofed and therefore very hard to block while still allowing normal traffic to come through. ISPs don't mind getting involved in helping to find the source of the problem but you must realize that they aren't the problem. This is akin to getting mad at Greyhound for the derelicts they keep dropping off in your neighborhood.
Your ISP is affected by this just as much as you are. ISPs do not, and cannot, buy enough bandwidth to support everyone at full speed. If an ISP sells 10 T-1's to customers chances are the ISP will only have the equivilant of 7 or 8 T-1's of bandwidth to the Internet. It's economically impossible to not oversell bandwidth. Because of this an attack to your connection that goes across the network of your ISP is using precious bandwidth.
You need to get in contact with hte ISP and give them as much data as you can. Simply calling and saying "it don't work" or something along those lines will not get to a solution as fast as getting some details and passing them along. You also need to realize that the ISP is probably just going to figure which incoming Internet connection this is coming from and call his upstream provider giving them the same information you gave. At this point the ISP can no longer do much about it except follow-up. And if you've ever dealt with a Telco or a bigger NSP you'll know how slow and incompetent these guys can be.
Your approach of just IP forwarding the packets to the ISP is not unlike finding unwanted garbage in your lawn and just tossing it to the neighbors lawn.
I got a copy of Code Fusion for Linux at LinuxWorld in San Jose about a month ago. Since I hardly ever write C code I never even broke the shrinkwrap. If anyone would like to buy my shrinkwrapped, unused copy please Email me at terry@dcomm.net
Slashdot Mirror
Either print the barcode directly on the disc with an inkjet or use the Avery labels for CDs. They even make printable labels that go on the little portion of the CD in the center (not the hole).
I went the no-tech and lazy way. I bought a bunch of the tyvek sleeves. I don't write on the sleeves, but I write directly on the disc with a marker. I throw the CD in any available sleeve, and put it in some reasonable order. I can usually find something quickly, but sometimes it takes a while.
Unless you're some sort of clean-o-maniac who lives for everything to have a place, realize it's a crappy media for storing in bulk and do something that gets you most of what you want. If you take 40 hours over a span of time to organize this stuff are you ever going to recoup that time? I don't know how often I've gone overboard for this stuff.
I think Rebel.com has done an excellent job with the Netwinder. It's a small computer using a SA1100 StrongARM processor. It's the same processor used in the Empeg car audio player and can do what you want and much more. It not only runs Linux, but it was designed specifically for Linux. I had a chance to talk with them at Linux World and I can tell you they're a small shop full of good people.
You may also look at the LART project being done in TuDelft, Netherlands. I don't think they're selling anything (yet?) but it's nice to see Linux on a small processor capable of some real power. I don't have a link handy, oops.
Or, you could use a uCsimm. It's a port of Linux to the Dragonball microcontroller with integrated Ethernet. It all fits on a 30 pin simm complete with Flash. I consider that to be really cool. There are many more choices out there than plain ol' Linux on x86. Don't limit yourself.
What is the newest gadget you bought and couldn't wait to play with?
As an administrator of a couple mid sized ISP's I think your approach is not only detrimental to the entire Internet but plain childish.
Most often the souce of the packets is spoofed and therefore very hard to block while still allowing normal traffic to come through. ISPs don't mind getting involved in helping to find the source of the problem but you must realize that they aren't the problem. This is akin to getting mad at Greyhound for the derelicts they keep dropping off in your neighborhood.
Your ISP is affected by this just as much as you are. ISPs do not, and cannot, buy enough bandwidth to support everyone at full speed. If an ISP sells 10 T-1's to customers chances are the ISP will only have the equivilant of 7 or 8 T-1's of bandwidth to the Internet. It's economically impossible to not oversell bandwidth. Because of this an attack to your connection that goes across the network of your ISP is using precious bandwidth.
You need to get in contact with hte ISP and give them as much data as you can. Simply calling and saying "it don't work" or something along those lines will not get to a solution as fast as getting some details and passing them along. You also need to realize that the ISP is probably just going to figure which incoming Internet connection this is coming from and call his upstream provider giving them the same information you gave. At this point the ISP can no longer do much about it except follow-up. And if you've ever dealt with a Telco or a bigger NSP you'll know how slow and incompetent these guys can be.
Your approach of just IP forwarding the packets to the ISP is not unlike finding unwanted garbage in your lawn and just tossing it to the neighbors lawn.
I got a copy of Code Fusion for Linux at LinuxWorld in San Jose about a month ago. Since I hardly ever write C code I never even broke the shrinkwrap. If anyone would like to buy my shrinkwrapped, unused copy please Email me at terry@dcomm.net