Recently I had cause to buy a scanner. Being in a reasonably small home I was eager to save on desk-space, and so decided to upgrade my ageing inkjet printer at the same time. Having looked around I eventually went for an HP Photosmart C5180 device. This is my experience of installing it on Debian Lenny.
Before you start shouting at me, I know. Nestcape Navigator will soon be no more. After many years of faithful service, and before Firefox and Flock were a mere twinkle in a web developer's glinting eye, AOL has announced that the browser will be retired at the beginning of February and put out to pasture in its nonage. You might be thinking that installing a browser with a death sentence hanging over its head is about as sensible as a portable defibrillator in a funeral parlour, but read on.
Ever since I first fired up KDE on openSuSE, I’ve been in love. The KDE interface just swept me off my feet. But there’s always been one nagging thing. Firefox and Thunderbird stick out like two sore thumbs. They don’t look like KDE apps (see figure 1 and figure 4), they don’t work with KDE programs (like KPrinter), and they just don’t feel like they belong in KDE. Luckily, since both of these apps have support for add-ons, it is easy to remedy this.
Backing up is one of those tedious jobs that has to be done but is usually relegated to the end of the To Do list. Enter Backup Manager, which is a set of Bash and Perl scripts that alleviate the tediousness of performing backups. Taking away some of the complexity of backup tools and combining others, Backup Manager is similar to other backup programs like my pc backup in that it brings simplicity to backing up. Obtaining a higher level view of backups also allows easier management of archives including retention. What follows is a method of backing up a single workstation daily and managing those backups.
Spicy food should cause chemical burns, or spontaneous human combustion. Your mouth should feel as if it’s tangled with an angry badger. Capillaries in your nose should burst. Your gut should sue for punitive damages. If not, your food just isn’t spicy enough.
At least, that’s how I feel. So, when I say things like, “Here, try some of these mild command-line recipes; they’re really quite tasty”, you might keep that in mind. One man’s “mild” is another man’s, “I think you’ve poisoned me”.
If you are ready, settle in, dish up, and keep a nice lager handy. You’ll probably need it before we’re done.
What do you do when you find a bug?
Installing software on a GNU/Linux system is often as simple asopening a package management interface, selecting with the mouse whichpackages you want installed, and letting the package management systeminstall the wanted packages—plus, any dependencies required forthe package to run. But what can you do if you want to install softwarewhich is not already packaged in your distribution of choice, and youstill want it to be registered in your package management system foreasy maintenance?
Create your own package, of course. Which doesn't have to be all thathard.
Two weeks ago, I explained how to set up a Kerberos realm; and last week, I went on to describe how to actually do something useful with it by doing Kerberized NFS. But there’s so much more interesting stuff that can be done with Kerberos, and it would be a shame to ignore those.
GSSAPI, SASL, and negotiation
NFS is a network protocol with which many UNIX-administrators have a love/hate relationship. On the one hand, it’s the ideal protocol if you need to export a filesystem from a UNIX-like system. On the other, it has a bit of a reputation of being insecure. Since a rogue system can just tell an NFS server that “hey, I’m representing a user with UID 1000, please remove all the files in my home directory”, this reputation may not be totally undeserved.
Or is it?
Usually, I get annoyed at having to authenticate myself to each and every service I set up; after all, my passwords are the same everywhere, since I make sure of that myself. On Windows, I wouldn’t have to do that; once I log in, Windows is able to communicate credentials to each and every service that asks for them. But something similar is impossible on GNU/Linux, right? Wrong.
Last time, I had found a quiet resting place in the
OOP menu which is, alas, not an undo menu. But one cannot hide forever. Time to reenter the dragon-filled wasteland called Blender.
After taking a few minutes to calm down, I decide to continue on my way. I’ve got to go back to the 3D interface. I steel myself, and click the grid icon to change back to 3D. I remember that the pictures in the tutorials had more than one 3D screen, so I decide that I am going to try to make the current screen into two screens.
One tutorial says...
Last time, my mind had become completely blank in the face of the Blender interface. Now, we shall dive on into the murky depths of the abyss known as Blender.
First, I do a search on Google and I find a tutorial with a reassuring sounding title.
That's a very reassuring title. It says to me, DON'T PANIC! I like that, so I switch screens and begin reading.
WARNING: The author of this tutorial takes no responsibility for you breaking your computer, initializing your harddrive, making a dumb-ugly image, or anything else that may happen if you take this blog too seriously. Remember what your mom said. “If everyone else jumped off of a cliff, would you?” If your answer was “Yes!”, then you deserve what you get.