ananonymoususer

Fortunately the house is in a state that makes it fairly easy to get a CCW permit, and I'm always carrying when I'm around that house.

The WSJ editorial was in response to the flood of mainstream coverage about the administration's announcement yesterday. I knew it was an editorial when I linked it and it should be obvious to anyone who reads it. Is there any question about the facts of the administration's policy statement?

"at no cost to you" other than the devaluation of your money via rampant inflation caused by irresponsible multi-trillion dollar spending bills.

X was developed on VAX, 68k, and later SPARC and then x86. VAX and x86 are little-endian, while 68k and SPARC are big-endian. Portability across these platforms was important and this was the inspiration for the RPC (now gRPC) platform-independent external data representation (XDR) standards.

Things were still not perfect with portability even back then. I remember taking a class in OSF Motif where everybody in the class was using SPARC while I was using x86 Linux. The code was somewhat portable between platforms, but many of the arguments to the (Metroworks) Motif library functions needed their endianness swapped in order to work properly on Linux, so the code examples from the course would not run on Linux without modification.

I realize that there may be some performance improvements realized by removing cross-platform compatibility, but I do not believe that the performance gains are worth the loss in platform compatibility. If X.org does this, it will eliminate one of the core reasons for sticking with X vs. Wayland.

Mine is in the smaller of my (two) garages.

I had to click and read the article to see whether CGI in this context was "Computer Generated Imagery" or "Common Gateway Interface". I've always been a fan of simple CGI interfaces. More middle-ware always means more bugs.

I agree it was a good story, but I became skeptical when I could not find the music (or any reference to it, or the composers) on-line.

It should have somehow been tagged as fiction.

Nothing is 100% secure, but I have opted for a high-quality gun/fire safe that's bolted to the foundation of my home (in a gated community), and protected by multiple monitored alarm systems and cameras. The safe has a lot more room than any bank's box would, it's cheaper in the long-run, and IMHO (especially after reading the fine article) more secure. Also, it's got a S&G spin-dial lock that I trust a lot more than any electronic garbage.

I use this all the time. It's a big time saver on multi-core machines (which is pretty much every desktop made in the past 20 years). It's available in all the repos, but not included by default (at least in Ubuntu/Mint). It is most useful for compressing disk images on-the-fly while backing them up to network storage. It's usually a good idea to zero unused space first:

(unprivileged commands follow)

dd if=/dev/zero of=~/zeros bs=1M; sync; rm ~/zeros

Compressing on the fly can be slower than your network bandwidth depending on your network speed, your processor(s) speed, and the compression level, so you typically tune the compression level (because the other two variables are not so easy to change). Example backup:

(privileged commands follow)

pv < /dev/sda | pigz -9 | ssh [email protected] dd of=compressed.sda.gz bs=1M

(Note that on slower systems the ssh encryption can also slow things down.)

Some sharp people may notice that it's not necessarily a good idea to back up a live system this way because the filesystem is changing while the system runs. It's usually just fine on an unloaded system that uses a journaling filesystem.