If you tell me that the Earth is going to change for the worse, and there's nothing we can do to stop it, then my response is we shouldn't try. We should instead work on how to survive the change. No reason to waste resources trying to stop something that can't be, spend them on dealing with it instead.

Likewise if you tell me Earth is doomed, and there's nothing we can do to stop it, then my response is that we should just not worry about the future at all, and enjoy what time we have left because there isn't anything else to do.

However if you tell me that we are creating a problem, but we can fix that problem by changing what we are doing, then I'm interested in hearing what you propose we do, what it would cost, how it would mitigate the problem, etc, etc.

If a problem is solvable then it makes sense to talk about what it would take to solve it. If a problem is just something we can't do anything about then we shouldn't worry about trying.

There should be particular guide lines for police discretion.
Broken lights, improper passing... Stuff in general where the person isn't really trying to do something criminal.
Besides, do you really expect to increase your staff 100% to watch what everyone else is doing all the time. The recordings should be reserved for legal proceedings, not job evaluations.

All of witch can allow for alterations, intimating the witnesses, creating false confessions, etc...

Red Hat use to have a distribution for everyone. It was one of the most popular Linux distributions. Then it moved to Red Hat Enterprise, and that really caused many of the Linux users to find something else and switch. Fedora is nice and all, but it felt like Red Hat throwing a bone.

Ubuntu came up and took its place as the distribution for everyone. Red Hat got stuck in the stuffy enterprise market.

As most people who know, Enterprise software means over priced software, that barely works, but somehow it makes executives feel good about using it, probably because they need a full IT Staff just to keep it running.

So companies who want to follow the buzzards of agile and nimble, have swapped to non-Red Hat based systems.
Nothing technical, just bad PR from Red Hat, that made them loose their fan base.

But he is innocent until proven guilty. So while his actions may be under suspicion, he isn't guilty of his misconduct due to lack of evidence.

Thank goodness I still live in a world of telephones, car batteries, handguns, and many other things made of zync!

While for the standard home user, 4:30-7:30 outage, means you have to forgo your morning entertainment. However there are a lot of small/mid sized businesses dependent on TWC for their operations.

I just wish they would send me an email about the outage so I know not to try to reboot my wireless router then my cable modem. Then plug my PC to the cable modem to see where the connectivity down.

(BTW I was kidding about the email notification)

I agree that most of what people have can be re-downloaded. However, separating that out is a chore, and what if you miss something? Might as well back up the entire drive just to make sure. But that would be a great product -- a search engine service that you can upload a list of file hashes and have it return a url for each file that is available online.

I haven't used rdiff-backup, but I used to use rsnapshot (actually a homebrew equivalent to it) -- was backing up several hosts to a central one. But I really missed having all the backup metadata in a database, where I could do simple SQL queries to find out file patterns were taking up the most space (this helps you tune your include/exclude list). Also, trying to replicate a rsnapshot volume that had a bunch of hard links (each day's backup's common files were hard linked to the previous days' files) -- this made for some very slow copying, unless I did a raw image copy (30 systems, with 10 daily, 6 weekly, and 12 monthly backup each made for a lot of file inode entries). That's why I wrote Snebu, so for each file that doesn't change between backups, only one gets stored. And references between backup sets are handled in the DB (sqlite3 based) instead of via hard links in the filesystem. Oh, and files are also compressed (lzop compatible format), which is something that rsnapshot didn't give me.

My favorite feature, that I'm testing out now (should be in the next version once it is stable and I hammer out the UI issues) is the ability to have a shadow copy of the backup DB that you stick on a thumb drive. This allows you to make incremental backups of your laptop to the shadow copy and sync it back to the main backup later on. Other features coming include external plugin modules to support moving / copying older backup sets to independent volumes, and potentially tape changers and cloud storage too (however these will all be secondary storage locations, the primary will be local storage).

Rotational Vibration (RV) is the vibration the drive experiences from the platters rotating at high speed. When you put a bunch of drives in a cage, some interesting harmonics build up which can shorten the life span of the drives further. Enterprise grade hard drives are built to better withstand these vibrations, lessening the chance of failure. (At least that is what their literature says -- personally I'd mount the drives using grommets or something like what Rackspace uses [rubber bands I think?]).

I remember when tape drives stored a few times more data than hard drives, and were priced about the same. I know I can back up to external USB drives (which I do using Snebu, but I which tape drives were more affordable.

The main question is how many channels are allocated for DOCSIS. Each channel gets you about 38mbps of bandwidth, though more can be had on newer standards with 4096QAM (if the SNR is good enough to support it). So if there's 4 downstream channels then a max of about 152mbps total down (upstream is separate).

How many channels can they add? Not sure with current DOCSIS specs, but the wire limits are either 600mhz for old systems, or 1ghz for most new ones. So you cold probably get in the range of 166 total channels or 6gbps or so. Of course in reality, some of those channels have to go to TV and so on.

Now DOCSIS 3.1 is adding new methods for operation and supposedly will pull 10gbps down. Not sure how much of that is tested and how much of that is pipe dream but it is what the spec claims.

I agree, having a manual break should be required as a bare minimum.
Even if the software is perfect, if there is an unexpected power outage, you will need a manual break to stop the car that just may be aimlessly costing.

GNU/Linux is the term for the standard Linux OS Distribution.
As opposed to Android and many of the other imbedded OS's that use the Linux Kernel.

If you are using an OS that is very Unix Like and is based on the Linux Kernel then it is probably GNU Linux, unless it is not using most of the GNU licensed tools.
cat, ls, mv, cp...