1) fix the PAGEFILE. Go inot the settings and change ti to fixed size - 2x-3x size of ram - both of minimum and maximum size. Do not let WInodws manage it! [ ... ]

Better still, move PAGEFILE.SYS off of C: entirely, preferably on to its own spindle if you can. That way the swapper isn't having a fight with every other application in the system for accessing system files; and PAGEFILE.SYS itself won't become fragmented.

Consider moving %TEMP% and %TMP% off of C: as well.

4) Dump the System Restore from time to time. This is just junk removal. [ ... ]

Sadly, this appears to be an all-or-nothing affair -- on XP, you can either delete all restore points or none of them. It would be nice to delete those that are, say, more than a year old.

I last tried a Debian install around the time of Dayton Hamvention, so a few months ago. I don't have a bug #, I tried to debug GDM for a while but didn't have enough time. I can try another install sometime soon.

Well, a Core i5 tablet with two parallel screen digitizers is an odd enough bird that you can't expect it to run on the somewhat aged Debian stable. And indeed the older GNOME there handles the touchscreen incorrectly.

Because it has a touchscreen and a separate pen digitizer on the same screen. And now with the keyboard, it also has a Cirque touchpad, for a total of three digitizers.

The Toughpad has a touchscreen and a pen (with a separate digitizer!) and the touchscreen doesn't work properly in the older GNOME in stable.

There is a video of someone throwing around my model, without the keyboard, here.

After something like 20 years I finally found a system that won't run Debian unstable right now. My Panasonic Toughpad FZ-G1 magnesium tablet + iKey Jumpseat magnesium keyboard. Systemd and GDM break. Bought (for less than full price) because I am a frequent traveler and speaker and really do need something you can drop from 6 feet and pour coffee over have it keep working.

But because of this bug I have ubuntu at the moment, and am not having fun and am eager to return to Debian.

We are in a War on Faith, because Faith justifies anything and ISIS takes it to extremes. But in the end they are just a bigger version of Christian-dominated school boards that mess with the teaching of Evolution, or Mormon sponsors of anti-gay-marriage measures, or my Hebrew school teacher, an adult who slapped me as a 12-year-old for some unremembered offense against his faith.

Hm. The covenant of Noah is about two paragraphs before this part (King James Version) which is used for various justifications of slavery and discrimination against all sorts of people because they are said to bear the Curse of Ham. If folks wanted to use the Bible to justify anything ISIS says is justified by God's words in the Koran, they could easily do so.

18 And the sons of Noah, that went forth of the ark, were Shem, and Ham, and Japheth: and Ham is the father of Canaan.
19 These are the three sons of Noah: and of them was the whole earth overspread.
20 And Noah began to be an husbandman, and he planted a vineyard:
21 And he drank of the wine, and was drunken; and he was uncovered within his tent.
22 And Ham, the father of Canaan, saw the nakedness of his father, and told his two brethren without.
23 And Shem and Japheth took a garment, and laid it upon both their shoulders, and went backward, and covered the nakedness of their father; and their faces were backward, and they saw not their father's nakedness.
24 And Noah awoke from his wine, and knew what his younger son had done unto him.
25 And he said, Cursed be Canaan; a servant of servants shall he be unto his brethren.
26 And he said, Blessed be the Lord God of Shem; and Canaan shall be his servant.
27 God shall enlarge Japheth, and he shall dwell in the tents of Shem; and Canaan shall be his servant.

As far as I'm aware, you don't need 'dump' with ZFS. You create a snapshot, then 'zfs send' that snapshot off to your backup storage. Can be done on a live filesystem. Delete the local snapshot when you're done copying it off. ( http://docs.oracle.com/cd/E187... )

I dunno about ZFS for Linux, but FreeNAS's ZFS has NFSv4 ACLs. Are these not sufficient?

...federal officials forced American tech companies to participate in the NSA's controversial PRISM program.

You misspelled "illegal." HTH. HAND.

Yes. Alas, this is a consequence of ZFS's COW (copy on write) design.

In a filesystem like EXT3, if you open a file, seek to some offset, and write new data, EXT3 will write the new data to the existing disk block in place. ZFS, however, will allocate a new block for that offset (copy on write), write the modified data to it, and update the block chain. The result is that it's apparently very easy to badly fragment a ZFS file (do a Google search for "ZFS fragmentation" to see various stories and tests people have written).

You can apparently mitigate the problem by occasionally copying the entire affected file -- Oracle's own whitepaper on the subject apparently reads, "Periodically copying data files reorganizes the file location on disk and gives better full scan response time."

Bottom line: ZFS is not a panacea, nor is it simple. There are myriad options, and trade-offs to all of them.

Get rid of your dictator and adopt a representative democracy and it will be over. Indeed, nobody could have thought it would go on this long.

First, a gratuitous plug for my Let's Play/Drown Out video series, currently focusing on 3DO console titles: http://www.youtube.com/playlis...

Why is that link relevant? Because they were all made using Kdenlive.

When I first started mucking around with digital video, I tried a bunch of free/libre packages, and formed the following opinions of each:

Windows Movie Maker
Yes, $(GOD) help me, I gave it a serious try. To my utter surprise, it mostly worked and did what I wanted without crashing. However, the UI was rather inflexible, and I needed more than the handful of features it offered, so I kept looking.

Cinelerra
Every Google search for free video editing software always turns this up, so I tried it. Then, ten minutes later, I had to stop trying it because it kept crashing and/or hanging at the slightest provocation. It has an impressive-looking array of features, and the editing timeline looks quite powerful. Evidently, you can do some fairly impressive things with Cinelerra, provided you can identify and avoid all its weak spots.

Pitivi
The last time I tried this, it was unreliable, under-featured, and incredibly slow. Just loading a one hour-long video clip into the timeline took several minutes as it tried to generate thumbnails and an audio waveform for the clip.

OpenShot
Assuming I'm remembering this package correctly, all it does is assemble edits -- that is, you can tack together a bunch of clips one after the other to create a larger work. If you want to do any effects or titling, you're SOL. Perhaps the Kickstarter-funded upgrade will yield some improvements.

Lightworks
I had to learn something the hard way with this package: This is a professional package. By that, I don't mean it has a ton of features (although it certainly does). I mean it expects a certain level of media asset before it will operate on it in the manner you expect. Us mere proles are satisfied to use MP4 or MKV or ($(GOD) help us) AVI files. However, in the pro space, you have files that contain not just compressed audio and video, but also timecode. And not just timecode measured relative to when you last pressed the RECORD button, but also a master timecode from an achingly accurate central timecode generator fed to all your cameras and microphones. This not only means all your cameras and mics are in precise sync ('cause otherwise their internal clocks will drift relative to each other), but you can trivially sync all your master footage and then intercut shots without even thinking about it. Also, near as I can tell, there's no such thing as inter-frame compression in professional video. Each frame is atomic, which means you can cleanly cut anywhere, but it doesn't compress anywhere near as small as, say, H.264.

The result is that, if you don't have equipment that generates all this metadata for you, then you need to convert it from the puny consumer format you're likely using. This means having truly monstrous amounts of disk available just to store the working set, and tons of RAM to make it all work. And hopefully your conversion script(s) didn't cough up bogus timecode.

So, yes, Lightworks is very very nice, if you have the proper resources to feed it. I don't, so I've set it aside for that glorious day when I get some proper equipment :-).

Kdenlive
Kdenlive is built on top of the MLT framework, and is about the best and most reliable thing I've found out there that doesn't cost actual money (either directly or indirectly). It has a non-linear timeline editor, it supports a wide variety of media formats, and it has a modest collection of audio and video effects (almost none of which you will use).

One of the more amazing things Kdenlive does is transparently convert sample and frame rates. Without thinking about it, my first video involved using a 44KHz WAV file, a 48KHz WAV file, and a 44KHz MP3 file, with the output audio to be 48KHz AAC. I feared I was going to have to convert all the sources to the same format, but Kdenlive quietly resampled them all when compiling the output video file, and everything came out undistorted and in sync.

Kdenlive does occasionally crash, which is annoying, but it has never destroyed my work. It has a fairly robust crash recovery mechanism, and you may lose your most recent one or two tweaks to the timelines, but you won't lose hours of work.

Kdenlive is not perfect, of course. It has limitations and annoyances that occasionally make me search for another video editor. But if, as I was, you're new to video editing, it will take you a while to find those limitations. Kdenlive has certainly served me very well in the meantime, and I think it's the most reliable, most capable, and most easily accessible Open Source video editor out there.