Patents, by nature, are anti-free-market. They always have been. They grant an exclusive monopoly on some type of business for a limited amount of time.
I don't see how you can bash people that support the free market, when patents are a prime example of the free market being tampered with. Anyone who is truely supporting a free market would support either a very narrow range of things that could be patented, or the elimination of patents altogether.
. Now admittedly a bullet has efficient balistic characteristics
Sometimes. It depends on the bullet. Obviously something like a wadcutter or a shotgun slug has terrible aerodynamics, those things often tumble through the air. Of course they also have muzzle velocities below 1000fps normally.
Hollowpoints also trade a little resistance for greater expansion on impact.
Correct, locally we run rsync with 30 minute cycles over 100bt. The script simply does a killall rsync at the beginning in case of a sudden data influx that causes an older script to run too long. Your sugesstions are good, the killall rsync was a quick and dirty way to buy a little insurance.
Sounds like you're initiating nightly, so you can lose twenty-four hours of data.
Offsites are a third level backup, we have local rsync incrementals, and also mirroring. In total, we always have from 2 to 4 copies of any given file in the archive. The archive is interacted with only through wrapper shell scripts from a user's point of view at least, which allow me to present a level of abstraction.
This system is pretty tailored to the type of thing we do, sticking large files into an archive. The shell scripts also allow logging and do basic locking when a file is out for changes. SSH plays a big role in all this, rsync is over SSH, the abstraction shell scripts use scp and ssh.
However, reduce it too much and you've created a new dependency on that T1
Yep. There is a possibility of a snowball effect, especially with slow lines like the 512K. Since the 512K is also used for many other things during business hours, I had to throttle the rsync down to 30 kilobytes a second. We decided to just go to nightly only and run it unthrottled, that has worked a lot better for us.
Time to recovery: It's fast to rsync a single file back to the original copy;... Mitigation of these factors is going to cost; spool on this side of the circuit? get a bigger circuit?
Well this is an easy one for us. Since we also have redundant local backups, the offsite backup is generally for severe disaster recovery only. In that case, we would do one of two things:
a) Just use the offsite server as the active archive. It would slow us down some, but it would work. The nature of our archive is that there aren't small incremental updates to files, files get checked in and out for changes, or copied for read-only access. We could operate at reduced capacity from it remotely. We also have a full T1 to the Internet (from a different ISP) in addition to the 512K WAN link, it could be used to transfer files in an emergency.
b) This is the primary plan in case of severe storage disaster. We just get them to ship us the server or RAIDset. Insert witty comment about 747s full of disks.:)
Our system isn't perfect, but for the shoestring budget we built it with, I think it's pretty robust.
Sharing the files to everyone is not the same as letting one person get the files.
Also, you can't ever upload via kpf.
Giving them a login only takes two simple commands and then they can upload/download, login, whatever you want them to do. The only port that needs to be open is ssh.
To turn Michael's argument on it's ear, "a computer is a lot less useful if it isn't on the network".
So I want to let my friend download some files from me over the network or the Internet. If my machine doesn't support more than one user, I have to give him my password and give him access to my whole system!
In a modern operating system, I can just give him an account, and then drop the files I want him to get into his home directory. Very simple, and doesn't expose any more of my system to tampering than needs to be exposed.
I probably sound like a broken record, but a plan like this one closes the door on lots of legitimate uses of email.
Thousands of email lists such as those hosted on Sourceforge would be shut down by a plan like this one, as well as killing lists like the Linux Kernel Mailing List, which sends millions of messages a year.
Also gone would be the days of the open mailing list, where people can send a message to the list without being subscribed, as is common in the open source world.
In short, this proposal guarantees that the only people able to use legitimate email lists will be large companies with the budget to spam. I got an unsolicited email from Wachovia this morning, apparently since I had a First Union account, they turned on all the marketing "spam me" options in my profile when the two merged.
I don't see how this tax will deter these semi-legitimate corporate spammers.
Re:"Stacks" in Longhorn like "Piles" in Panther?
on
Looking at Longhorn
·
· Score: 1
Talk about obvious. What's the difference between "files in a directory" and "documents in piles"? Not much it sounds like. It seems the only new thing is automatically filing the documents based on content, which seems also pretty trivial.
Carmageddon II for the PC had the best I have ever seen. Maybe not "realistic" in the sense that you could drive off after smashing the car pretty hard, but still a very cool damage model.
If you hit a solid object offset going 150-200, you could actually manage to shear the car in half every now and then. Since the game was really about hitting pedestrians and crashing the car doing crazy stunts, I guess they put a lot of effort into the damage part.
That is a valid argument for securing the transmission, but I don't think it's all that compelling for visible cameras.
If you can see the camera, then you can pretty much tell what it can and can't see. It may have a wide angle lens, but it's still pretty much limited to what it is pointed at. Visible cameras are more for deterrent value anyway.
I think your argument mostly applies to hidden cameras. Discovering the location of the hidden cameras would defeat the purpose of hiding them.
Well, as I understand it, the "quad pumped" intel is done by actually doubling the number of lines, and both sets run with data on the rise and fall of the clock. This is the part I think is most misleading, and the biggest abuse of the word.
The intrinsic value of Citizen Kane is not degraded or removed by infinite copies. You have argued this.
Since infinite copies do not degrade or remove the intrinsic value, your earlier argument regarding copyright law existing to protect intrinsic value is meaningless.
I really wish you would register so I could see who I am talking to.
That's not what I meant. I meant out of something like a rifle. I'm just not very impressed that they just shot this sled into a wall, it seems kinda pointless.
Speaking of which: I read something years ago about some scientists who were launching artillery shells out of a device, the rounds were slightly smaller than the barrel and had a sort of sabot. The barrel was filled with hydrogen and oxygen IIRC. Their trick was to fire the round, and then have the explosive mix in the barrel explode exactly behind the round, causing the round to "surf" on the shock wave of the exploding gasses.
Don't remember any specific numbers on muzzle velocities, but apparently it was pretty powerful.
rdiff-backup and rsync with rotating incrementals are both able to do the first two very well, with the advantage of never needing a "full" backup after you do the first one, something tape will never be able to do. This makes things like offsite backups over slow and cheap links possible that would not be otherwise.
We back up about 1TB of total data to a offsite backup over a 512kbit fractional T1, with daily rsync incremental snapshots that we keep for 30 days. Our data velocity is about 3-6GB per day of data that changes or is added. The backup easily finishes between 5pm and 8am.
For #3, long term archival of small amount of data, hard disks probably aren't a good choice.
I resent it when people say "the only real backup solution is tape".
Then really, how is this different from just firing a bullet and saying that it is just as fast? I know some standard rifles shoot around mach2-3, so it wouldn't be too hard to make one souped up for extra speed.
Well, I guess if it actually worked 100% of the time I wouldn't complain, but of the two ISPs I have been on that have had it, I've had problems with both.
One time one dial-in ISP I was on turned on content filtering somehow on the transparent proxy, and accidentally blocked every web site. It stayed that way for at least 6 hours. This ISP also had trouble with caching old content, doing web development on a remote host was a nightmare, because their proxy would not refresh changes until a few minutes later.
As far as the T1 equipment goes, it can be as simple as a single Linux box with Sangoma Wanpipe PCI card, the driver is well supported, in the main kernel, and rock solid. It acts as the CSU/DSU and the router.
Get a Class C, assign addresses via DHCP with long leases, and don't fuck around with anything else. Don't packet filter, or traffic shape, or anything else, that's just asking for trouble.
If people start hogging it, and other people complain about the slowness, then just start posting a list on the bulletin board showing a nice traffic graph by unit.:)
Let your T1 ISP do your DNS for you, or set up that single machine as the primary DNS, and let your ISP run secondary for you (be careful with the glue!).
As far as the political issues go, I'd include a small remuneration for yourself in the monthly fee.
Slashdot Mirror
I have a friend that cannot get his knee insured because he had a soccer accident in university.
The alternative is coercing an insurance company to take a risk that they believe will cost them more money than it brings in.
It's akin to my breaking my arm accidentally, then coming to your house with a gun and demanding you pay my medical bills.
Patents, by nature, are anti-free-market. They always have been. They grant an exclusive monopoly on some type of business for a limited amount of time.
I don't see how you can bash people that support the free market, when patents are a prime example of the free market being tampered with. Anyone who is truely supporting a free market would support either a very narrow range of things that could be patented, or the elimination of patents altogether.
. Now admittedly a bullet has efficient balistic characteristics
Sometimes. It depends on the bullet. Obviously something like a wadcutter or a shotgun slug has terrible aerodynamics, those things often tumble through the air. Of course they also have muzzle velocities below 1000fps normally.
Hollowpoints also trade a little resistance for greater expansion on impact.
. Rsync would support reducing that (
... Mitigation of these factors is going to cost; spool on this side of the circuit? get a bigger circuit?
:)
Correct, locally we run rsync with 30 minute cycles over 100bt. The script simply does a killall rsync at the beginning in case of a sudden data influx that causes an older script to run too long. Your sugesstions are good, the killall rsync was a quick and dirty way to buy a little insurance.
Sounds like you're initiating nightly, so you can lose twenty-four hours of data.
Offsites are a third level backup, we have local rsync incrementals, and also mirroring. In total, we always have from 2 to 4 copies of any given file in the archive. The archive is interacted with only through wrapper shell scripts from a user's point of view at least, which allow me to present a level of abstraction.
This system is pretty tailored to the type of thing we do, sticking large files into an archive. The shell scripts also allow logging and do basic locking when a file is out for changes. SSH plays a big role in all this, rsync is over SSH, the abstraction shell scripts use scp and ssh.
However, reduce it too much and you've created a new dependency on that T1
Yep. There is a possibility of a snowball effect, especially with slow lines like the 512K. Since the 512K is also used for many other things during business hours, I had to throttle the rsync down to 30 kilobytes a second. We decided to just go to nightly only and run it unthrottled, that has worked a lot better for us.
Time to recovery: It's fast to rsync a single file back to the original copy;
Well this is an easy one for us. Since we also have redundant local backups, the offsite backup is generally for severe disaster recovery only. In that case, we would do one of two things:
a) Just use the offsite server as the active archive. It would slow us down some, but it would work. The nature of our archive is that there aren't small incremental updates to files, files get checked in and out for changes, or copied for read-only access. We could operate at reduced capacity from it remotely. We also have a full T1 to the Internet (from a different ISP) in addition to the 512K WAN link, it could be used to transfer files in an emergency.
b) This is the primary plan in case of severe storage disaster. We just get them to ship us the server or RAIDset. Insert witty comment about 747s full of disks.
Our system isn't perfect, but for the shoestring budget we built it with, I think it's pretty robust.
Sharing the files to everyone is not the same as letting one person get the files.
Also, you can't ever upload via kpf.
Giving them a login only takes two simple commands and then they can upload/download, login, whatever you want them to do. The only port that needs to be open is ssh.
Today, a machine is rarely single user.
To turn Michael's argument on it's ear, "a computer is a lot less useful if it isn't on the network".
So I want to let my friend download some files from me over the network or the Internet. If my machine doesn't support more than one user, I have to give him my password and give him access to my whole system!
In a modern operating system, I can just give him an account, and then drop the files I want him to get into his home directory. Very simple, and doesn't expose any more of my system to tampering than needs to be exposed.
I probably sound like a broken record, but a plan like this one closes the door on lots of legitimate uses of email.
Thousands of email lists such as those hosted on Sourceforge would be shut down by a plan like this one, as well as killing lists like the Linux Kernel Mailing List, which sends millions of messages a year.
Also gone would be the days of the open mailing list, where people can send a message to the list without being subscribed, as is common in the open source world.
In short, this proposal guarantees that the only people able to use legitimate email lists will be large companies with the budget to spam. I got an unsolicited email from Wachovia this morning, apparently since I had a First Union account, they turned on all the marketing "spam me" options in my profile when the two merged.
I don't see how this tax will deter these semi-legitimate corporate spammers.
Talk about obvious. What's the difference between "files in a directory" and "documents in piles"? Not much it sounds like. It seems the only new thing is automatically filing the documents based on content, which seems also pretty trivial.
I wish you would really put your advertisements in your sig, it's pretty obnoxious to attach them on to the end of your message like that.
Carmageddon II for the PC had the best I have ever seen. Maybe not "realistic" in the sense that you could drive off after smashing the car pretty hard, but still a very cool damage model.
If you hit a solid object offset going 150-200, you could actually manage to shear the car in half every now and then. Since the game was really about hitting pedestrians and crashing the car doing crazy stunts, I guess they put a lot of effort into the damage part.
That is a valid argument for securing the transmission, but I don't think it's all that compelling for visible cameras.
If you can see the camera, then you can pretty much tell what it can and can't see. It may have a wide angle lens, but it's still pretty much limited to what it is pointed at. Visible cameras are more for deterrent value anyway.
I think your argument mostly applies to hidden cameras. Discovering the location of the hidden cameras would defeat the purpose of hiding them.
Well, as I understand it, the "quad pumped" intel is done by actually doubling the number of lines, and both sets run with data on the rise and fall of the clock. This is the part I think is most misleading, and the biggest abuse of the word.
And tomorrow it's free jewlery day! Just show up at your local jewelery store with a gun! :)
SCO's Darl McBride:
"There's a certain point here where you stand up for what's right and let
the chips fall where they will."
Indeed Darl, indeed.
The intrinsic value of Citizen Kane is not degraded or removed by infinite copies. You have argued this.
Since infinite copies do not degrade or remove the intrinsic value, your earlier argument regarding copyright law existing to protect intrinsic value is meaningless.
I really wish you would register so I could see who I am talking to.
That's not what I meant. I meant out of something like a rifle. I'm just not very impressed that they just shot this sled into a wall, it seems kinda pointless.
Speaking of which:
I read something years ago about some scientists who were launching artillery shells out of a device, the rounds were slightly smaller than the barrel and had a sort of sabot. The barrel was filled with hydrogen and oxygen IIRC. Their trick was to fire the round, and then have the explosive mix in the barrel explode exactly behind the round, causing the round to "surf" on the shock wave of the exploding gasses.
Don't remember any specific numbers on muzzle velocities, but apparently it was pretty powerful.
rdiff-backup and rsync with rotating incrementals are both able to do the first two very well, with the advantage of never needing a "full" backup after you do the first one, something tape will never be able to do. This makes things like offsite backups over slow and cheap links possible that would not be otherwise.
We back up about 1TB of total data to a offsite backup over a 512kbit fractional T1, with daily rsync incremental snapshots that we keep for 30 days. Our data velocity is about 3-6GB per day of data that changes or is added. The backup easily finishes between 5pm and 8am.
For #3, long term archival of small amount of data, hard disks probably aren't a good choice.
I resent it when people say "the only real backup solution is tape".
Copyright law is based on extending legal protection to the intrinsic value of a work.
The value of something that can be infinitely duplicated is zero.
The only thing giving it value is the artificial scarcity created by copyright laws.
There is no need to confuse the issue with semantics.
Rdiff backup, does incremental snapshot.
http://rdiff-backup.stanford.edu/
Hah, yeah, that is pretty hilarious.
Then really, how is this different from just firing a bullet and saying that it is just as fast? I know some standard rifles shoot around mach2-3, so it wouldn't be too hard to make one souped up for extra speed.
Well, I guess if it actually worked 100% of the time I wouldn't complain, but of the two ISPs I have been on that have had it, I've had problems with both.
One time one dial-in ISP I was on turned on content filtering somehow on the transparent proxy, and accidentally blocked every web site. It stayed that way for at least 6 hours. This ISP also had trouble with caching old content, doing web development on a remote host was a nightmare, because their proxy would not refresh changes until a few minutes later.
The catch is that you have to really pay attention to what's said in the end to enjoy it.
That sounds suspiciously like Jerry Springer.
"The RIAA paid $18,000 for the chairman of the House Judiciary Committee to travel to Taiwan and Thailand
Why is this buried in a Slashback? Come on! This is huge news.
I agree regarding the cabling.
:)
As far as the T1 equipment goes, it can be as simple as a single Linux box with Sangoma Wanpipe PCI card, the driver is well supported, in the main kernel, and rock solid. It acts as the CSU/DSU and the router.
Get a Class C, assign addresses via DHCP with long leases, and don't fuck around with anything else. Don't packet filter, or traffic shape, or anything else, that's just asking for trouble.
If people start hogging it, and other people complain about the slowness, then just start posting a list on the bulletin board showing a nice traffic graph by unit.
Let your T1 ISP do your DNS for you, or set up that single machine as the primary DNS, and let your ISP run secondary for you (be careful with the glue!).
As far as the political issues go, I'd include a small remuneration for yourself in the monthly fee.