Joining a GNU/Linux machine to a Microsoft Active Directory has been possible for years, but it’s always been a bit of a science project that involved touching half-a-dozen obscure config files and usually resulted in me getting completely locked out of the machine. Various commercial packages such as Likewise and Centrify aimed to smooth out the process, but they weren’t universally accessible across distros, and often produced inconsistent results.
After upgrading a system to Debian 8, I noticed a new option for joining the domain, courtesy of the folks at RedHat: realmd. Realmd puports to make joining an Active Directory domain dead simple. How does it do?
In the previous article of this series, I covered a variety of “remix” distributions of Linux aimed at older computers, and posed the question “why not build our own”? In this article, we’ll look at doing exactly that.
Our goal will be to set up a basic desktop system, using only the necessary components, such that it will run reasonably well on a roughly ten-year-old computer.
I’ve been coding Python in Emacs for years now, and for the most part it’s been a satisfactory experience. After experimenting with various python modes and utilities, I’ve had a pretty good environment that marries Emacs editing to syntax highlighting, real-time error highlighting, the ipython shell, linting tools like pylint and pep8, and various other goodies. But the one hole, the one sore spot in the whole works, was code completion. Something even idle can do out-of-the-box was simply beyond my ability to get functional in Emacs.
I’d tried just about every solution the internet could offer: PyMacs, company-mode, anything-mode, ipython completion, standard autocomplete-mode. Everything I tried either gave unacceptable results (like autocomplete-mode, which just scans the current buffer for completion information), or just flat-out didn’t work no matter how many tutorials I followed.
Here lately I’ve been trying to work a lot more on my Pythoning, so I decided to see if the state of the art has caught up with this need. Echo base, I’ve found it. Repeat: I’ve found it.
So often with Linux distributions, the choice is between running a bleeding-edge system, or sticking with stable (and sometimes stale) software. Most of us settle in to a distro that balances both to our liking, but there are times when you just have to have a little newer version of a package than the default repositories offer. While it’s great to find a backport repo or PPA that offers newer stuff, sometimes that’s not possible.
So for times like that, I’m going to describe a method by which Debian or Ubuntu users can backport their own software using handy little tool called “apt-src”.
Following on the heels of my google search hotkey in awesome, I decided to tackle expanding the functionality of the run prompt. Awesome’s run prompt, by default, is basically a command-launcher; it chokes on any input that doesn’t represent an executable file.
I wanted it to behave more like the run prompt in other desktops, so that typing in a URL would open the URL in an appropriate application.
With help from Alexander Yakushev on the awesome mailing list, I managed to figure it out….
I’m back to using AwesomeWM on my work desktop; not sure what brought me back, but I will say that overall I prefer the way it handles multiple monitors and multiple desktops a little better than how KDE does it. That, and KWin’s tiling mode is still useless with dual monitors even in 4.8.
Something about running a window manager like Awesome makes you uber-sensitive to operations that require you to do a lot of mouse-maneuvering or manual window management, and thus encourages you to streamline these operations. One such thing for me is searching google for something, an activity which I’m bound to do at least six dozen times during a workday, especially when developing (since I can’t remember API’s for squat).
With a little help from a bash script and surfraw, I came up with a pretty cool solution. (more…)
It’s a little unfortunate how much we rely on something as unreliable as a computer. There you are, working along, happily doing your thing, and suddenly Windows (or OSX, or Linux, or BEOS, or whatever it is that sits between your hardware and your web browser) pukes up some error and refuses to boot, work, or be otherwise useful.
Fixing the computer itself is just a matter of time and money; getting back those pictures, documents, emails, and other files that you always meant to back-up is another issue. So in this article I’m going to show you a simple way to recover documents from a system that won’t boot.
Long ago, before I ever knew a lick of BASH or even what an OS kernel was, my passion was not technology but music, music, and more music. Roughly the first half of my adult life was devoted to the writing, playing, and recording of music, and by around 2002 I’d built for myself a tidy little home recording & mixing setup centered on Cakewalk Sonar, Jeskola Buzz, and Windows XP. Alas, the years were not kind to my career or gear, and up until recently my music computer was busy being a game & education machine for the kids.
Thanks to a hard drive crash and the purchase of new machines for the kids, I got my old music machine back, albeit lacking a functioning operating system and software. So, I decided now was a good time to rebuild it. This time, though, I decided the time was right to kick XP and Cakewalk to the curb and go it Free Software style.
When tinkering with old computers, there is little about an operating system quite as endearing as flexibility at install time. The “Universal Operating System” is no slouch in this regard; the Debian installer will work quite happily from CD, DVD, USB drive, PXE boot (my personal fav), and even a Windows executable.
But what if none of those is an option? Suppose you’re stuck with a system with no optical media, no USB boot, no PXE boot, and no OS? Can we get Debian on such a machine?
You bet we can! (more…)
Back around 2006 our public library was in need of a cheap way for patrons to browse its web-based INNOPAC catalog. Thin clients running Windows CE had been purchased for this purpose, but they turned out to be buggy and limited. I was tasked with finding a solution to the problem “on the cheap”, and being a fairly new Linux fanatic at the time, I figured I’d see what I could do using free software. This led to my first kiosk project.
Since then, I’ve refined my approach time and again, deploying kiosks throughout my organization just about anywhere a web-browser kiosk can be put to use. The original library system has been completely rebuilt with newer hardware and software, but is fundamentally the same system I set up five years ago.
I often see people asking about how to set up a kiosk system with Linux, and like me they usually start out going about it the wrong way; so I thought I’d write this tutorial based on my years of experience to help those getting started.