Having recently revived and updated my KDE Linux install, I went looking for the context menu to manipulate images. This tool makes life easier. Like when you want to toss an image into your blog post, but WordPress complains it is too large, it is nice to be able to simply right click on the image and in a click or two resize it (or rotate it, or maybe do other things to it). Historically there was a tool called KIM (KDE Image Management) that did this, but this seems to be no longer maintained and is not that easy to install. Instead, install “ReImage” from KDE Services Menu. Look for the “deb” link on that page if deb is your preferred install method. There is also a tar file there for other architectures.
NOAA will be adding two new Cray computers (one operational and one backup) to replace existing hardware used in weather forecasting. According to a press release, “the computers — each with a 12 petaflop capacity — will be operational and ready to implement model upgrades by early 2022 after a period of code migration and testing. They will replace the existing Cray and Dell systems, “Luna” and “Mars” in Reston, Virginia, and “Surge” and “Venus” in Orlando, Florida.”
When combined with other hardware that will remain in use, the total capacity will rise to 40 petaflops. (A petaflop is a measure of computing speed equal to one thousand million million (1015) floating-point operations per second.) Given upgrades in storage and connectivity, and this increasing computing power, there will be a noticeable increase in resolution and other features of NOAA’s modeling of earth systems.
There is a rumor that the Trump Whitehouse plans to sell off the hardware to some friends who live out near the airport in Queens, and replace it with lower grade equipment that Trump claims works just as well (see illustration).
Though the press release does not give details, a spokesperson for NOAA just informed me that these computers will run the Linux operating system. I had assumed so, but wanted to check. Linux is the standard operating system for super computers, because it is a super operating system. Nobody wants to see the Blue Screen of Death in the middle of their tornado warning.
Specifically, the computers will run the Cray Shasta Linux Environment. This is a high performance suit designed to run large and complex applications on more than a half a million cores, with docker container support, and the robust Cray system management support including staged upgrading capabilities and the low overhead Cray system snapshot analyze.
One: set up Dropbox and, as it syncs your files from the cloud, go outside and mow your lawn or rake your leaves.
Two: Start using your computer.
Three: Cancel the order for the new laptop because your old laptop is faster now.
You may have been expecting one of those posts that tell you the “ten things to do after installing [Linux Distribution]” but this ain’t it. In fact, for the most part, those posts have become fairly useless. Consider these “things to do”: Continue reading Things To Do After Installing Xubuntu or XFCE
If you have a PDF file and need to extract a subset of pages, creating a new PDF file with those pages in it, you can do that.
I like PDF Lab‘s PDFtk aka PDF toolkit. This is not OpenSource and there is both a non free pro and free version of it. I’ve tried the free version (example below) and was impressed. Next time I need to do a lot of PDF work I’ll probably fork out the 399 for the pro version. (That’s 399 pennies, quite cheap. It is developed by Sid Steward, the author of PDF Hacks: 100 Industrial-Strength Tips & Tools.
So, for example, I can get pages 11-20 of a larger file called big.pdf extracted into a smaller file called extracted.pdf like this:
pdftk A=bigpdf cat A11-20 output extracted.pdf
That line of code makes almost no sense to me, but it works.
I learned about this tip at a Linux Journal Tech Tip page on extracting pages from a PDF, where you will find several other approaches.
There are a lot of books out there to help you learn command line tools, and of course, they mostly cover the same things because there is a fixed number of things you need to learn to get started down this interesting and powerful path.
Small, Sharp, Software Tools: Harness the Combinatoric Power of Command-Line Tools and Utilities by Brian P. Hogan is the latest iteration (not quite in press yet but any second now) of one such book.
I really like Hogan’s book. Here’s what you need to know about it.
First, and this will only matter to some but is important, the book does cover using CLI tools across platforms (Linux, Mac, Windows) in the sense that it helps get you set up to use the bash command line system on all three.
Second, this book is does a much better than average job as a tutorial, rather than just as a reference manual, than most other books I’ve seen. You can work from start to finish, with zero knowledge at the start, follow the examples (using the provided files that you are guided to download using command line tools!) and become proficient very comfortably and reasonably quickly. The topic are organized in such a way that you can probably skip chapters that interest you less (but don’t skip the first few).
Third, the book does give interesting esoteric details here and there, but the author seems not compelled to obsessively fill your brain with entirely useless knowledge such as how many arguments the POSIX standard hypothetically allows on a command line (is it 512 or 640? No one seems to remember) as some other books do.
I found Small, Sharp, Software Tools a very comfortable, straight forward, well organized, accurate read from Pragmatic.
If you write shell scrips, you should check out Dave Taylor’s latest article in Linux Journal.
He gives key examples of what can go wrong if you don’t pay attention to certain things.
For example, if you have a dot in (especially at the start of) your PATH variable, you risk running a Trojan horse that snuck sneakily into your /tmp directory. If you want the dot, put it last.
Anyway, a simple straight forward article with a few pieces of good advice: Writing Secure Shell Scripts
A computer program is like a memo. Often, a vague memo.
You are the boss. You want a pile of files to be put away. You could do it yourself, but instead you instruct someone else to do it. There are a lot of them and they are all mixed up. So you write a memo to an employee that says “put the files away” and sis-bam-boom you’re all set.
Linux has a kernel, there is a desktop manager, a desktop environment, a distribution, and a whole bunch of other stuff. All these things and other things have version numbers and similar information associated with them. If you are a casual user, you probably don’t know the exact version of any or all of these things you are running at any one moment in time. Then, suddenly, you find out that “Version this-or-that of this thing-or-another is out, have you tried it?” or “The whatchamacalit version of the thingimijob is broken, if you have that upgrade or you will all die!!!” or similar. So then, you want to know what version you are running.
Here are a few ways to find out that information. Continue reading How do I tell what version of everything I’m running (Linux)
Here’s an idea. You have an old beat up computer running, say, Windows. You want to make it faster, crisper, more secure, and generally, better.
What can you do short of buying a new computer? Well, install Linux. Linux is so much more efficient as an operating system, your computer will simply run better. Guaranteed. Continue reading This year’s biggest ripoff is also this year’s best gift idea
I’ve reached a very nice resting point in the ongoing effort to develop a very useful, powerful, stable, and cool computer setup.
This started a while back when I built a computer. In particular, this computer. There are several advantages to building a computer. You can save money or get more bang for your buck even if you don’t pay less. On the saving money side, maybe you have components on hand that you don’t have to buy. I did, mainly mass storage. The case I had, thinking I’d save money there, ended up not working out. You get more bang for the buck because the parts you buy will be better than the ones in the equivilant off the line but cheaper computer, and you’ll have more control over what happens in future upgrades. Continue reading A really good computer setup
I’ve noticed that many file managers in Linux are changing in the way many Linux desktop environments are changing. They are becoming simpler. That is a bad thing. File management has not gotten simpler. If anything, it has gotten more complicated. I need a powerful tool, not a dumbed down stick. That’s why I like the KDE file manager, Dolphin.
Here are a few tips and tricks to tweak the dolphin.
Some of the most obvious things you can do are right in front of you, but this will depend on exactly what version of Dolphin you have. When I open Dolphin, I see a “preview” and a “split” icon on top. The utility of these buttons is obvious, and both are useufl. Note that with preview you can use a scaling bar at the bottom of the window to change the size of the preview.
I also see a “control” button over to the right. That leads to the menu that does most of the work in configuring the software. Play around with it. Below are a few specific suggestions that generally involve diving deepish into the menu structure.
Also, don’t forget to right click on everything until you’ve found out what all the right clicking mojo is. There is a lot of right-click mojo in KDE generally, and in Dolphin in particular.
Adding information to icons in Icon View
Dolphin has three modes for viewing files. One is “details” and to be honest, that’s all I want to know most of the time. But if you use the “Icon view” you may want to see the file size under the filename (below the icon) and the number of files under the folder icon, for each item. Or, you might want other info, like creation date, or file type. If you do, change the view mode to Icon, then under Control pick “Additional Information” and click whatever info you want to appear with the icon.
Obviously this also works with the detailed view to give you new columns on which to sort things. It also works with “compact” mode.
Making all folders behave the same way
One of the nice things about Dolphin, and this is true of many file managers, is that you can set individual folders to have specific behaviors, and those behvaviors will be there when you reopen the folder at another time. You can always change the behavior if you need to. But, an even nicer thing in Dolphin (but not in many other file managers) for some people is this: You can tell Dolphin to “Use Common Properties for All Folders” by going to Control, then Configure Dolphin, then under the “General” page, pick the Behavior tab, then check “Use common properties for all folders” as opposed to “Remember properties for each folder.”
Personally I prefer to have each folder remember its properties, but you may prefer the consistancy across all folders.
Group folders and files
Under “Control” you can select “show in groups.” Interesting things happen. Mainly, the files and folders get grouped up either alphabetically or by time. It is kinda freaky. You might like it.
Panels that show more information
Under Control >> Panel you can select several cool options.
A “details” panel appears on the right, and is like a “properties” tab, with information like file size, type, when it was modified, etc. There is additonal information that depends on file type. A picture will show the size of the picture, a video the length of the video, etc. This panel allows you to add tags and comments, and rate a file.
A “terminal” panel appears down below the file manager. As you switch around between directories, the termnial changes directory (and you can even see the cd [directory] command being implemented).
The “Places” Panel is probably on by default, and that is the strip to the left of the icon or details area. A navigation tree is also a panel, and it apears on the left.
You can resize the panels. And, if you unlock them (right click) you can move them around to a certain extent!
Depending on where on Dolphin you right click, you can bring up a menu with the various panels listed, as well as the main tool bar.
So, one thing you can easily do, is to set Dolphin to show previews, be in a folder with pictures you want to review, then turn off all the panels so your pictures can take up maximum room on your screen. Then you’ve got what acts like a dedicated photo album viewer, sort of.
I usually do nothing fancy with my windows. I open them. Later, I close them. In between, I may maximize them or unmaximize them. I move them around the screen.
The two fancy things I do are: 1) “Maximize” a window onto a portion of a screen using drag magic of some kind (most Linux desktop environments have this) or b) tell a window to move itself to a different workspace.
Most, nay, all, desktop environments have a larger set of fancy window behavior control than this. The whole idea of controlling, or even having, windows in which software runs, is fundamental to the *Nix environment, and Linux is the modern and most widely used version of *Nix. But I think it is possible that KDE has the mostest and bestest of these abilities.
For example. You can right click on the top bar on the window and pick “more actions” from the context menu. This gives you “move,” “resize” and such, which you have access to in other ways. GBut it also gives you check boxes to “keep above others” or “keep below others” which is very hand when your multiple monitors start to fill up with stuff because your workflow has gone fractal.
Burrow deeper and you can get to “special window settings.” This allows you to control behavior of a particular window in very detailed and even scary ways. You should probably not do any of this, but you should have a look.
In between these two cantos of configuration, you can find “Windows Manager Settings” in the window title bar context menu. This allows you to mess with windows decorations, screen edges, desktop effects, etc. You can get to all this via other configuration tools, but this is a handy way to make adjustments on the fly while you are actually using software.
One thing you may want to adjust here is when and how windows become translucent. I never used that feature before, and having the windows become semi-translucent when being moved is the default in KDE. I think people like this because it is a quick and dirty way to see what is behind the window. I find it a bit disconcerting because I sometimes am still reading what it is a window while I’m moving it. I wonder if there is a way to make a window go translucent optionally. Probably. OK just checked, there is.
A key feature you will want to adjust is active screen edges and corners. Here you can turn on or off features that maximize, either to a full screen or a “tile,” the window you drag to an edge. This allows for quarter tiling. Right now I have the ability to mazimize a window by dragging the title area of the title bar to the top middle of a screen, to tile over the left or right half by dragging it to the appropriate side edge, or quarter-tiling the window by dragging it to a corner. It is a bit funky when I drag towards the second monitor … can get confused as to which monitor to tile the window on.
Windows. Not just for Windows any more. Never were, really.
In some Linux desktops, what you get is what you get when it comes to desktop icons.
You can usually specify if you want network locations or storage devices shown as icons, or maybe a trash can, shown, but not much else. This is where Linux looks stupid compared to at least some earlier versions of Windows and the Mac, where you can do more with icons.
But in KDE, icons are very very configurable.
In KDE, you can right click on the desktop, then chose “icons” on the context menu.
You can then arrange the icons horizontally or vertically on the screen.
You can align them to the left or right of the screen.
You can sort them by the usual sorting criteria.
You can specify sizes, ranging from “tiny” to “huge.”
And you can lock them. When unlocked, you can move them around.
The images shown here are exemplars of some of these options, in various combinations.
I’m pretty sure the very first Linux desktop I ever used was KDE. I didn’t realize that it was actually a bit painful until I later discovered Gnome. I switched to Gnome because it worked better for me, and seemed to use fewer resources.
I never left Gnome, but Gnome left me. I won’t go into the details here, but as most Linux users know, Gnome 2.x was the high point of that particular world of Linux desktops (see THIS POST for definition of term “desktop”). With the demise of Good Gnome, mainly caused by Ubuntu (a distribution I otherwise have a great deal of respect for), I poked around among the various Gnome 2.0 desktop alternatives. Among them eventually emerged Mate, which at first, I thought was great. I used it as my main desktop for several years, until just recently.
But Mate had two major flaws. The first flaw was an attempt to simply everything. Mate never made an application to be part of its own desktop environment, but rather, it took old Gnome applications, then broke them slightly or failed to maintain them (but the Mate project developers did rename them all, to take credit for them, and add confusion). The second flaw was not fully maintaining the parts of the desktop environment it was responsible for, or fixing basic problems. For example, it has always been true that most people have a hard time grabbing window boundaries with their mouse in Mate. To fix this you have to go down into configuration files and manually change numbers. That is a bug that should have been fixed three years ago. I can only assume that the maintainers of Mate don’t have that problem on their particular desktops.
Among the main functions of a maintained desktop environment is keeping basic system configuration tools clean and neat and functional, but Mate messed that up from the beginning. I vaguely remember that an early version of Mate left off the screen saver software, so in order to have or use a screen saver, you had to install the old Gnome screensaver. The configuration and settings capacities of the Mate desktop are distributed across three or four different applications, at least one of which you have to find out about, find, install, and learn to use yourself, just to carry out simple functions. Basic categories of settings or configurations are distributed among these applications in a haphazard way. To do basic things like change the desktop appearance or mess with screen savers, etc, you have to be a power user.
But I thought Mate was still better than KDE partly because KDE was so strange. For one thing, single clicking in KDE was like double clicking everywhere else in the universe. Yes, you could reconfigure that, but it is still strange. The nature of the desktop, of panels, or widgets, of all of it, was just a little odd for me. Everything felt a little funny.
But over time, KDE did two things that Mate did not do. First, KDE continued to maintain, develop, improve, debug, make more efficient and powerful, all of its software. Instead of key software components going brain dead or not being maintained, or losing functionality like in Mate, KDE software got more powerful and more useful. At the same time, the software, and the overall desktop environment, got slicker, cleaner, more like the old Gnome 2.0 in many ways, and leaner, and less strange (single clicking is no longer a default!).
In the old days, it was probably true that Gnome used fewer of your computer’s resources than KDE. But the most current versions of Gnome and gnome like alternatives such as Mate probably use about 25% more resources than KDE out of the box. And, KDE out of the box is more configurable and overall more cool than Mate and many other desktops.
Here’s the key thing. When I first started using Linux, the feature I fell in love with was the workspace switcher, allowing one to maintain a number of virtual desktops, each with various things open on them. This is how I organize my work. It isn’t all that systematic, but in a given day, I’ll organically end up with all my stuff related to one project on one virtual desktop, and another project on a different virtual desktop. Gnome and gnome variants actually moved away from this standard. You can still have virtual desktops in current Gnome, but they are not there by default. Mate still has them by default, but I don’t trust Mate maintaners to maintain that.
But it is easily done in KDE, and with extra (mostly unnecessary) perks. In the KDE desktop environment, I can have the desktop background be different on my different virtual desktops on my desktop computer. Which sits on my desk. I can have other things be different on the different desktops. For me, this doesn’t do much because, as noted, my virtual workspaces evolve organically over time frames of hours or days. But someday, I may want a special desktop configured all special for some special purpose.
A couple of months ago, I had some problems with Mate. I uncovered an important and easily fixed bug. I told the maintainers about it. They told me to screw off. So I told them to screw off, and I started to explore other desktop environments. After realizing that they had been too rude to me, the Mate maintainers, to their credit, did fix the bug and tried to make nice. But I had already moved on. It did not take me long to get KDE up and running and configured as I like. And, I’ve hardly explored all the cool stuff it can do.
But I am exploring it now, and I’ll keep you posted.
See: KDE Icon Magic
1) Uninstall it. It is flawed in key ways. It will be difficult to get your Dropbox working, if you use that, installing software form .deb files is not automatic and requires hacking. There are some other problems too.
2) Check back here in a few months, see if I’ve updated with good news. Meanwhile, get back to whatever you were doing, because you don’t want to be doing this.
I tried to get info from Mate about the problems I encountered. They really provide no way to do that, so I tweeted about it referring to their handle, so they would see.
The tweeted back two responses. The first one said a combination of “nothing is broken” and “tough luck.” The second twee is shown in this screen grab:
That is a moving GIF with the boy’s eyes blinking. It is intended to mean, “tough shit, sucker!” or words to that effect.
(I provide a screen shot because I assume cooler heads will prevail, maybe, at Mate HQ, and the immature dickhead who tweeted that will be countermanded. Or maybe not. We don’t ever hear anything good about their development community. Only bad things.)
So, don’t look for an Ubuntu Mate explainer on this blog.
Preparing to install Xubuntu right now!