I still use RCS because it has the in-line markup to keep track of the revision you have. And
is so simple to set-up and use that a 1 page cheat-sheet is usually enough for most people that
can type without looking at their fingers.
Put it on a ZFS filesystem and take hourly snapshots. Don't worry about network access, since
that is how you are going to loose your repo. People can login to a server to edit and rsync to make
remote copies. Easy and safe (using ssh for example).
I always display the $Id$ string in the version output for each module under -V or --version:
that means you can know for sure that you have the latest version before you test/release.
If you don't like ransom notes (which perl programs may become over time) use this trick: get
perl to reformat the code with a this command:
$ perl -MO=Deparse ransom.pl >better.pl
Most of the time that removes the crazy from the script. I just got a large legacy code-base and
that little trick made my life much better. If the perl code works, then you are just looking for
work to do. Newer is not always better.
At the library I want to see a list of all the titles in print from my favorite authors, I just use the local WiFi to get the data. For larger downloads I ask on the WiFi, but get the data over the visible light network. So I can see the text of all those books, DRM allowing. Or watch a lecture on the Great Bustard.
At airports, my PDA/phone gets all the flight updates on an endless loop, via the visible light network. At Home Depot I'm offered product information and How To videos. I'd love to see the view from the cockpit in real-time while I was flying. If we build really high capacity broadcast networks (like the over-the-air TV used to be), then we'll find uses for them we've never thought about at all. This may even make a computer useful in a class room.
I don't believe most of this requires encryption. Mostly an asymmetric network gets us video and large data requests over a cheap, local, and very limited range network. If you want encryption for small slices of data, us the WiFi to do a key exchange.
Slashdot Mirror
I still use RCS because it has the in-line markup to keep track of the revision you have. And is so simple to set-up and use that a 1 page cheat-sheet is usually enough for most people that can type without looking at their fingers. Put it on a ZFS filesystem and take hourly snapshots. Don't worry about network access, since that is how you are going to loose your repo. People can login to a server to edit and rsync to make remote copies. Easy and safe (using ssh for example). I always display the $Id$ string in the version output for each module under -V or --version: that means you can know for sure that you have the latest version before you test/release.
Most of the time that removes the crazy from the script. I just got a large legacy code-base and that little trick made my life much better. If the perl code works, then you are just looking for work to do. Newer is not always better.
At the library I want to see a list of all the titles in print from my favorite authors, I just use the local WiFi to get the data. For larger downloads I ask on the WiFi, but get the data over the visible light network. So I can see the text of all those books, DRM allowing. Or watch a lecture on the Great Bustard. At airports, my PDA/phone gets all the flight updates on an endless loop, via the visible light network. At Home Depot I'm offered product information and How To videos. I'd love to see the view from the cockpit in real-time while I was flying. If we build really high capacity broadcast networks (like the over-the-air TV used to be), then we'll find uses for them we've never thought about at all. This may even make a computer useful in a class room. I don't believe most of this requires encryption. Mostly an asymmetric network gets us video and large data requests over a cheap, local, and very limited range network. If you want encryption for small slices of data, us the WiFi to do a key exchange.