The Mandelbear's Musings

A few years ago I read an article about how to set up a Mac for distraction-free writing. I can't seem to find it anymore (okay, some rather large value of "a few"), but "there's an app for that" now. Many writers on my reading list are talking about distraction-free writing tools like iA Writer (seems to be the one people are most impressed by at the moment) and FocusWriter (free and cross-platform). There's even an Emacs mode.

These all work roughly the same way: run a text editor in full-screen mode, and write plain text with simplified markup in a fixed-width font. Worry about formatting later, if at all. Grey out everything but the sentence or paragraph you're working on. The article I can't find -- written before specialized writing programs and even before the web -- suggested getting the same effect by taking all of the icons off your screen and setting your default font to Courier.

If you're happily using one of these tools, you may want to skip ahead to the section on formatting, and maybe fill in the gaps later. If you're still using a word processor, or typing into a text field in a browser (even in "rich text" mode), you should probably stick with me.

What You See is All You Can Get

WYSIWYG (What You See Is What You Get) word processors are arguably the worst thing to have happened to writing in the last half-century. They have three huge problems:

The first is that they make a promise they can't deliver on. In fact, they should be called WYSIAYCG -- What You See Is All You Can Get. If your word processor doesn't support kerning, multiple fonts, paragraphs with hanging indents large initial capitals, mathematical notation, or internal cross-linking, you can't use them. If they make it difficult to use these features, you still won't use them unless you absolutely have to, and then you find yourself wasting time doing clumsy work-arounds. Think about how you'd go about formatting song lyrics with chords over them. Shudder. How about making the space between sentences equal to one-and-a-half times the space between words?

The second is related to the first: word processors target a specific page layout. If you want to make a printed book, a web page, and an eBook, you're going to have to do extra work to accommodate the differences, or settle for something that has about the same level of mediocrity in all of those environments.

At a lower level, word processors use proportional-spaced fonts. That means you have to peer over the tops of your glasses to see whether that character at the end of the sentence is a period or a comma, and if your hands are shaking from too much coffee you'll have trouble selecting it. Or putting the cursor in front of it without selecting it, if you want to add a few words.

The third is that they distract you from actually writing, tempting you to fiddle with fonts, reformat your footers, worry about word-wrapping and hyphenation, and place your page breaks to avoid widows and orphans, at a time when you should be concentrating on content.

There's a fourth, mostly unrelated, problem which is so pervasive these days that most people accept it as The Way Things Are: if you accidentally select something and then type, whatever you selected goes away. In almost all cases, even if your word processing has an "undo" feature, this can't be undone. So let's talk a little more about...

Editing

Anyone who's been hanging around me long enough is expecting me to mention GNU Emacs at some point, and I will. But there are plenty of other text editors, and most of them are perfectly usable. They're often called "programmers' editors".

I'm not going to tell you how to use a text editor here; I'm just going to tell you more about why, and point you at some resources. Michael Hartl's Learn Enough Text Editor to Be Dangerous is a pretty good introduction to most of them, though you may want to skip the chapter on Vim. It gives short shrift to Emacs, but fortunately the first thing on your screen after starting Emacs is the tutorial. Start there.

So, why would you, a writer, want to use a programmer's editor?

One reason is that programmers have been writing on computers for a quite a bit longer than writers have, so text editors have a considerable head start. More to the point, programmers use their own programs. This gives them a strong incentive to make their programs fast, efficient, and powerful. Not every programmer who has a problem with their text editor is going to fix it, but enough do to make them improve rapidly.

Word processors, on the other hand, are written by programmers, but they are usually written for ordinary users, not experts, and they're written to be products, not programming tools. As products, they have to appeal to their customers, which means that they have to be easy to learn and easy to use. They don't have to work well for people who spend their entire work day writing -- those are a tiny fraction of the customer base.

Another reason is that text editors use fixed-width fonts and encourage you to use comparatively short lines (typically 72 or 80 characters, for reasons that date back to the late 1880s). Paragraphs are separated by blank lines. Since line breaks inside of paragraphs are ignored by formatters, some authors like to start every sentence on a new line, which makes them particularly easy to move around, and makes it easier to spot differences between versions.

A text editor also makes you more efficient by giving you a wide range of keyboard commands -- you can write an entire book without ever taking your fingers off the keyboard. (This is, in part, due to their long history -- text editors predate graphical user interfaces by several decades.) And most modern text editors are extensible, so that if you want new commands or want them to behave differently for different kinds of markup, they're easy to add. (I have a set that I use for my band's lead sheets, for example, and another for my to-do files.)

Markup

Up until somewhere around 1990, everyone who did any serious writing knew how to edit a manuscript using proofreaders' marks. Manuscripts were typed double-spaced to leave room for insertions, corrections, and cryptic little marks between the lines and in the margins. This was, logically enough, called "marking up" the manuscript. You've probably heard of Markdown. You've certainly heard of HTML, which stands for "HyperText Markup Language". HTML, in turn, is a variant on SGML, "Standard General Markup Language". You may have heard of LaTeX, which is the standard for academic -- especially scientific -- writing.

Markup languages let you separate content writing from formatting. Semantic markup lets you add additional information about what the things you are marking up mean; it's up to a stylesheet to determine what they look like . In HTML, you don't have to <i>italicize</i> something, you can <em>emphasize</em> a talking point, or <cite>cite</cite> a book title. They usually look the same, so most people don't bother, until they decide to turn all the book titles in their two thousand blog posts into links.

You can see how using semantic markup can free you from having to think about formatting while you're writing. There's another, less obvious advantage: you aren't stuck with just one format. By applying different styles to your document you can make it a web page, a printed book, an eBook, a slide show, or an email.

Another advantage of markup languages is that all of the markup is visible. This week's xkcd: "Invisible Formatting", shows how you can accidentally make a boldface space in the middle of normal text, where it can distract you by making an insertion unexpecedly boldface. It may also make subtle changes in line and word spacing that are hard to track down down.

There are two main kinds of markup languages: ones like Markdown and Textile, that use simple conventions like **double asterisks** for strong emphasis, and the ones that use tags, like <cite>HTML</cite>. LaTeX and Restructured Text are somewhere in the middle, using both methods. You can be a lot more specific with HTML, but Markdown is far easier to type. Markdown and Textile let you mix in HTML for semantic tagging; Markdown, Textile, and Resturectured Text all use LaTeX for mathematical notation. Some formatters let you embed code with colored syntax highlighting.

These days, it looks as though Markdown is the most popular, in part thanks to GitHub; you can find it in static site generators like Hugo and Jekyll, and it's accepted by many blogging platforms (including Dreamwidth). Unfortunately they all accept different dialects of Markdown; there is an enormous number of Markdown-to-whatever converters. But the nice thing about markup languages is that you aren't stuck with just one. That brings us to...

Formatting

Once you have a file that says exactly what you want to say, the next thing you'll want to do is format it. Formatting programs (a category that includes LaTeX, web browsers, website generators like Jekyll and Hugo) all use some kind of style sheet that describes what each kind of markup is supposed to look like. You probably know about CSS, the "Cascading Style Sheets" that are used on the web. LaTeX has a different set, written in the typesetting language TeX.

If you wrote your file in HTML and you want to publish it on the web, you're done. You may want to make your own stylesheet or customize one of the thousands that are already out there, but you don't have to. Modern browsers do a perfectly reasonable job of formatting. CSS lets you specify a separate style for print, so when a reader wants a printed copy it actually looks like something you'd want to read on paper.

If you wrote your file in LaTeX and you want to publish it on paper, you're done -- it's safe to assume that LaTeX knows more about formatting and typesetting than you do, so you can just tell LaTeX what size your pages, pick one of the hundreds of available stylesheets (or write your own), and let it make you a PDF. You can change the page size or layout with just a few keystrokes.

If you wrote your file in Markdown or some other markup language, there are dozens of formatting programs that produces HTML, LaTeX, PDF, or some combination of those. (My favorite is Pandoc -- see below.) Markdown is also used by static website generators like Hugo or Jekyll, and accepted by everything from blogging sites to GitHub. If you're publishing on the web or in some other medium your formatter supports, you're done.

The advantage of separating content from format is that you're not stuck with one format. Web? Print? eBook? You don't have to pick one, you have all of them at your fingertips. There are hundreds of conversion programs around: html2latex, latex2html, kramdown (which GitHub uses),... For most purposes I recommend Pandoc. The subtitle of Pandoc's home page calls it "a universal document converter", and it is. It can convert between any of the the markup languages I've mentioned here, and more, in either direction. In addition it can output eBook, word processor, wiki, and documentation formats, not to mention PDF. As an example of what it can do, I write these posts in either HTML or Markdown as the mood takes me, and use Pandoc to convert them to HTML for Dreamwidth and plain text, stripping out the tags, so that I can get accurate word counts.

Version Control, etc.

Text files with short lines are ideal for other tools in the Linux (and Unix -- did you know that Unix was originally used by technical writers?) environment. When you compare two files, a line-by-line comparison (which is what diff gives you) is more useful than a paragraph-by-paragraph comparison (which is what diff gives you if you don't hard-wrap your text). Text editors can run formatters, spelling checkers, search tools, and others, and put the cursor on the exact line you're looking for. Want to search nearly 6500 blog posts for your favorite quote from G. K. Chesterton? Took me one line and a little over 4 seconds.

        time find . -type f -exec grep -nHi -e 'rules of architecture' {} +

Many formatting tools simply ignore single line breaks and use a blank line to separate paragraphs, examples include LaTeX and most (though not all) Markdown translators. HTML ignores line breaks altogether and relies on tags. I take advantage of that to make HTML more readable by indenting the text by four spaces, and using 80- or 90-character lines. If you want an example and you're reading this page in a browser, just hit Ctrl-U to look at the page source. Compare that to web pages made without hard-wrapped lines -- you may find yourself scrolling dozens, if not hundreds, of characters to the right because browsers don't do any wrapping when displaying source. Nor would you want them to.

The biggest advantage (in my not-so-humble opinion) is version control. (Those of you who've been around me were just waiting for me to mention git, weren't you?) Being able to find all the changes you made this week -- and why you made them -- can be incredibly useful. Being able to retrieve a file from three years ago that you accidentally deleted is priceless.

This post is already pretty long, so the next post in this series is going to be about version control (and the other things you can do with git and GitHub; it's not just version control) for writers. Stay tuned.

Resources

• GNU Emacs
• writeroom-mode for Emacs
• Atom
• Learn Enough Text Editor to Be Dangerous
• Pandoc
• Markdown
• Textile
• LaTeX - A document preparation system

Another fine post from The Computer Curmudgeon (also at computer-curmudgeon.com).

You may want to start with Part 1

Xmonad is a tiling window manager. That means that, with very few exceptions, it lays out all of the windows in your workspace so that they completely fill the screen. You can have multiple layouts, and flip between them with a single keystroke. You can bring a workspace (there are 9 by default, but you can add more) to your screen with a single keystroke, or send a window to a workspace.

And the whole thing is configured using a text file that is actually a program, written in the functional language Haskell. I'll get to that later.

One of my main gripes about Gnome, etc., and one of the things I miss the most about CTWM, is that when you first start a program its window shows up at some random location on the screen, with whatever size the program thinks is appropriate. If you don't like those choices you have to move and resize the window yourself, and then do it all over the next time you log in. (There are some exceptions -- many newer programs remember where you put them last, and older programs, from the CTWM era, can be given a starting geometry.)

Xmonad's layouts are all deterministic, which is to say, predictable. When you start a program, you know exactly where it's going to be on the screen. When you change the layout, you know where everything is going to go. If you want to move a window into the main position (most layouts have one; e.g. the left-hand column) it's (as usual) just one keystroke to put it there.

But the best thing, and the reason I switched to xmonad in the first place, is the way it treats multiple monitors: it simply assigns one workspace to each monitor.

Undock your laptop, and its screen stays exactly the same. The workspaces that were shown on the other screens simply go back into hiding with all the others, and are still only a keystroke away. When you have multiple screens, you can move a window to another screen, or bring a workspace to a screen, or warp the pointer to another screen, all with single keystrokes.

When you go to a conference room and plug in a projector, a workspace immediately shows up there and its layout automatically adjusts to the projector's resolution and aspect ratio. When you get a new computer -- all the developers at work got new laptops just a month or two ago -- just copy your configuration files to it and everything will be exactly the same as it was on the old one. (Sometime later I'll write about my portable configuration, which makes it possible for me to set up my entire working environment in mere minutes.)

So let's go a little deeper into those magic keystrokes. First of all, you have to know that all of the commands (you can't really call them shortcuts) include a key that xmonad calls "Mod" (short for "modifier", of course). Mod is initially defined as Alt, but the first thing any Emacs user is going to do is redefine it as something else, usually the "logo" key. (That's the one on the left between Ctrl and Alt that usually has a Windows logo on it. If your keyboard has replaceable keys you may be able to get a penguin for it.) On old laptops that don't have a logo key I use Ctrl-Alt, but that's a matter of taste.

You also probably want to know that Mod-? gets you a list of all the commands. And that there's a fantastic collection of tutorials, documentation, and sample configuration files at xmonad.org.

When xmonad starts up, you see a totally empty, black screen. Most people, myself included, add a status/navigation bar at the top, but you don't have to. I'll get to that later. You can start a program by typing Mod-P, or open a terminal window with Mod-Shift-Enter. You will immediately notice that the first window you open fills the screen. If you open another, xmonad will tile the screen with them, showing them side by side.

If you start a third program, it will get added to the right-hand column. You can probably see where this is going. When you move the mouse pointer into a window, it gets a thin red border to show you that it has "focus".

If you decide that you started things in the wrong order, move the pointer into the window you want to put in the left-hand column (the "master" column) and hit Mod-Enter. You close a window you're done with using Mod-Shift-C.

Here's where it gets interesting: Mod-Space will switch you to a new layout, with the master column turning into a master row, and all the other windows across the bottom. Hit Mod-Space again, and the currently-focused window goes full-screen. (I reconfigure my full-screen layout to put a row of tabs across the top. Wondering how to see the hidden windows? Mod-Tab moves focus to the next window in the stack. It also works in other layouts, so you don't need the mouse to move focus around. If you spend most of your time in a terminal and an editor like vim or emacs, you can throw your mouse away and still be productive. Mod-Shift-Tab moves focus to the previous window.

Mod-2 puts you into a second workspace. There are nine of them. (I add two more -- 0 and -.) If you want to move a window, say from workspace 2 to workspace 1, use Mod-Shift-1. That's kind of a recurring theme in xmonad -- Mod-something does one thing, and Mod-Shift-something does something related.

You can see that in action if you add an(other) monitor. Now, workspace 1 is in the left-hand screen, and 2 is in the right-hand screen. Think of the two of them as West and East.

Now, Mod-w will move the focus (and the mouse pointer) into the West screen, and Mod-e will move the focus into the East screen. Mod-1 through Mod-9 will bring that workspace into whatever screen has the focus. If the other workspace was already visible, they trade places. (Some people don't like that, so you can change it so that it just moves focus into the other screen if you select a workspace that's already visible.)

Add a third screen to the right of East, and call it Right. Now, Mod-r and Mod-Shift-R do exactly what you would expect. (There are no bindings for T, so I suppose that if you have space for a fourth screen you could use it for that.)

There are more key bindings, to move focus (Mod-j and Mod-k focus the next and previous window, respectively; shifted, they swap the focused window with the next or previous window), to shrink and enlarge the master area (Mod-h and Mod-l respectively), or increase or decrease the number of windows in the master area (Mod-Comma and Mod-Period respectively).

As I mentioned about a week ago, I've been trying to write more. And since my current obsession is a program called xmonad, well, ...

This is incomplete: it's about the first day's worth (I've been trying to write about 500 words per day). Comments and suggestions are, of course, welcome.

My new 27" monitors arrived at work; I took advantage of the change to rearrange my work space. Before, it was the set-up I've had for most of the last three years -- monitor in front on a stand, second monitor on the right, and my laptop on the left. The new laptop, however, has a decent keyboard (with trackpoint and three buttons), and the monitors between them occupy about 2/3 of the desk.

The new arrangement has the laptop dock under the "middle" monitor; the laptop, being a business-class Dell, has both a pointing stick and a middle "mouse" button. The laptop's keyboard is decent enough that it can replace the thinkpad keyboard I've been using for the last couple of years -- it's a high-end Dell, and has both a pointing stick and a middle button. (The middle button has part of the Unix desktop environment since the mid 1980s; it means "paste", and I use it all the time.) The monitors are about 50% bigger, pixel-wise, than the laptop, and are arranged "traditionally" with the laptop on the left.

You can probably see the problem with this arrangement. The total workspace is about 7000 pixels wide, and it's not even arranged in a straight line -- to get from the laptop to the "middle" monitor you have to move the cursor to the right, but the natural direction would be straight up. What's more, when you undock the laptop the whole thing collapses down to a "mere" 1920x1080. It's no wonder that most of the programmers in my team have opted for a single 30" monitor, and keep their laptop (almost invariably a mac) closed while they're using it.

Fortunately, I anticipated this problem months ago, and started using a window manager called xmonad.

One of the things I love most about Linux is the fact that the program that manages the layout of the screen and the behavior and appearance of the windows on it is not part of the operating system. It's a separate program, sensibly called a "window manager", and it runs in user space as a perfectly ordinary application that just happens to have a couple of extra hooks into X, which is the (also ordinary) program that actually controls the display, the keyboard, and the mouse.

Being an ordinary program -- and not even a terribly complicated one -- anybody can write one, and many people have. For a long time I was using one called TWM (Tabbed Window Manager, but the T originally stood for Tom's). Later I started using CTWM (Claude's Tabbed Window Manager), because it introduced the then unfamiliar notion of multiple workspaces. (Before CTWM, these could only be found in an experimental system at Xerox where they were called "rooms". Apple introduced them decades later, as part of MacOS X.)

You've probably heard of Gnome, KDE, and Ubuntu's horrible Unity desktop environments. Down at the bottom, they're just window managers plus a couple of utilities for doing things like putting up the familiar bar (Gnome calls it a "panel") full of menus, launcher buttons, clocks and other widgets. You can, in fact, run gnome-panel under any window manager, and I did for a while. They also include a "session manager", which handles things like starting the panel and making sure that applications get notified when you log out, so that they can save their state and exit cleanly. I've been using Gnome for years, and loved it for its configurability.

But Gnome's configurability comes with a cost -- every time you move to a new computer, you have to spend an hour clicking around in control panels and property windows to get everything set up the way you like it. And every time there's a major upgrade, something is a little different. It's a cost I no longer have to pay.

Part 2

Hmm. Long week. The week included a lot of moving stuff around setting things back up after the wedding; that's probably what's behind my current back problems. (See QOTD from yesterday.)

My loaner project at work is winding down, though not as quickly as I'd like. Not feeling very good about work right now.

On the gripping hand, the Great Room looks fantastic, with much more room in its new configuration (blue couch in the SE corner). And Colleen's new baker's rack nightstand has been installed, and looks great. And I upgraded Nova to Debian Jesse, which rocks. (Not entirely clear what I'll do with the extra monitor space; possibly mostly devote it to the to.do file, which I usually edit on Nova anyway when I'm at home. x2x rocks, too.

I have to tell you about x2x(1). (For those of you still stuck on legacy operating systems, the equivalent is synergy or, if one of your machines runs linux, x2vnc.) It's the exact opposite of a remote desktop application (which you get for free in Linux) -- it lets you share a mouse and keyboard between multiple computers. You just sit their displays side by side, tell x2x which edges are next to one another, and your mouse slides smoothly between them, taking the keyboard with it. Cut and paste work perfectly. Indispensable. I also set it up at work, between my desktop and laptop.

Links in the notes, as usual.

Hmm. Not as good a day as its two predecessors, though the morning included a really good, useful meeting on the web-services side of $PROJECT. But that and the switch to cold weather made for too many excuses not to go out for a walk.

And I made progress toward setting up a transfer from my bank to my credit union, but didn't get started soon enough for it to count toward Bank Transfer Day (which is today). I tend to get down on myself about the obvious negative effects of procrastination, but of course by then it's too late to fix them.

One of the good parts was figuring out -- remembering, really -- one of the last bits of magic required to make ssh port tunneling work. Still having trouble with X forwarding, though; it worked fine with Lenny.

As for links, I was pleased to note that Occupy rigs up human-power after generators are confiscated

I'm an old bear, and rather set in my ways. But now that Colleen has an Ubuntu-based netbook, we're looking for a good mail reader.

Requirements:

• Gnome or, preferably, desktop-independent. She doesn't use KDE.
• Must be able to handle multiple POP and IMAP accounts.
• Not too complex.

Another possibility would be to suck everything down using fetchmail, but she would still need a good mail reader. Feel free to discuss the advantages and disadvantages of fetchmail you have an opinion on it.

A good day. I felt very dragged out in the morning, and didn't do much in the way of journaling. It may have been mostly blood sugar, and I was ok by the time I got to work, A little while after that I got a happy, almost bubbly call from cflute that got the rest of the day off to a great start. We agreed that it was wonderful to have good things to talk about. The last year has been horrific for both our families; we're ready for Samhain to bring us a bright, shiny new one with good jobs for those who need them, good health for all of us, and homes filled with music, love and contentment.

I followed this with a walk around the pond; I took 10 minutes out for meditation, and another five or so to simply sit and watch the beautiful koi. I could feel my mood lighten. I returned to work and was contentedly productive for the rest of the afternoon, turning an ancient EeePC into an Unbuntu server that can be taken to Japan next week for a portable version of $DEMO.

There were too many conversations going on for me to sing, but I came out of my hole for some up-tempo noodling a couple of times.

Yeah; a good day. Let's have some more of them.

It just occurred to me that I can overlap three rather disagreeable major projects this weekend: moving thestarport.org's DNS and email, upgrading the fileserver, and cleaning the office.

I just realized that I have to do the first two in that order, or a lot of email will end up dropped on the floor. Most of that will be spam, of course, but the sheer volume of it means that if I don't move it, the tiny mailbox at my ISP will fill up and things will start bouncing.

But I also realized that having my fileserver out of service for a while will remove a major distraction that would normally keep me from cleaning out the office. Which direly needs it. Because I have to do a lot of that before I have the space to do the taxes. AAARGH!

I don't think I need help with this, just some good excuses to stop making excuses, if that makes any kind of sense. This post is a step in that direction.

There are actually three things I can burble about right now. The main one is that my coworker presented a paper this week on the project that our group has been working on. So there are things I can talk about! (And some that I still can't.) I can at least point to the abstract, which is here, though you probably have to be an ACM member in order to download the paper.

Basically the thing is an e-writer -- an e-reader with pen input that lets you write on things like forms and book pages. The next prototype version, due soon, is about the same form factor as the Kindle DX only with WiFi instead of cell, and (because it's a research prototype) Debian Linux.

The other two are the fact that I'm pretty much off the hook for the demo next week -- I've already mentioned that one -- and that the Dell Mini-10 that I won at OpenSourceWorld arrived yesterday.

The Dell came already defenestrated, with Ubuntu 8.04LTS installed. Plusses include the almost-full-size keyboard, scroll gestures on the trackpad, a gig of RAM, and 16 GB of solid-state disk. Minuses include the trackpad, the fact that one does not put swap on a flash drive, and the fact that it's just a little too big for the cases that used to hold my Magio laptop. Still, it's a sweet, shiny little thing. It hasn't been named yet.

Debian GNU/Linux 5.0 released. Read more at www.debian.org.

What I'm looking for is an open-source, cross-platform (Linux, Windows, and preferably also MacOS) program for music notation. Preferably with the ability to export to Lilypond (for typesetting), ABC, and MusicXML. Must import and export MIDI files and play via MIDI. Rosegarden would be absolutely ideal, except that it only runs on Linux (for a change).

Canorus looks plausible, but appears to be immature at this point. Definitely worth a try, though, since there are Windows binaries on the download page. It's based on the earlier Noteedit, which is Linux-only again.

Of course, we could always use VMWare and either run Lilypond on Windows, or a pirated version of Concertware on Linux. The latter is ancient, though, and stuck with proprietary formats.

... from both sides now. From Gizmodo, a matched pair of articles titled "Why I Hate Netbooks" and "Why I Love Netbooks". Both posted by the same author, apparently.

As for me, I want a netbook with a Happy Hacking keyboard. One of the old, clicky ones. That, or just run my XO in terminal mode with a Model M, except it wouldn't be particularly portable. Which was kinda the whole point.

This week was LinuxWorld; I went up to the Expo on Wednesday. In some previous years that would have been the high point of the week; you know Linux has gone mainstream when the most innovative products on the show floor were a new kind of ergonomic chair (which didn't seem to suit me) and some gorgeous, handmade wood mobius strips. OK, the 160GB flash drive on a PCIE card was pretty cool, too, streaming 256 movies simultaneously onto two large screens.

The point is that the real action has moved to more specialized conferences; all the open source developers were at OSCon two weeks ago in Portland, for example. As this blog post points out, that's not a bad thing. These days LinuxWorld is aimed primarily at IT departments considering making the move to Linux, or looking to upgrade their hardware or services.

It's an IT show, and I'm a hacker. Sold a CD to someone at the Creative Commons booth, though; easy sell, since all the music on it is CC. *shrug* I'll keep going as long as it's free and it's local. Let me know if there's an interesting conference or trade show in Seattle.

The Linux Picnic, which was this afternoon, was also smaller than in previous years, but still fun. Colleen came, and a visiting starless_knight substituting for the Y.D., who was off gaming with friends. I brought the XO, and Colleen brought her EeePC; I also brought Ruby and sang a couple of songs after lunch. No album sales, though.

Moving back in the week, we had a terrific talk Tuesday morning by our company president, on the history of $PARENT_COMPANY. It was followed by the company picnic; smaller than the Linux picnic, but the food was better.

All-in-all it's been a quiet week, but as I've said before, that's good. Very good. Compared to what many of our friends are going through...

Much of my creative energy has been going into the drafts of some River posts on conversation and communication. The first two (out of three) are just about ready, but I find that I like taking the time to work on them over the course of a couple of weeks. Plays hob with my other projects, though.

TG: Will you be coming out with a tailored version of Ubuntu for the ultraportable sector?

MS We're announcing it in the first week of June. It's called the Netbook Remix. We're working with Intel, which produces chips custom-made for this sector.

TG: Do you think that GNU/Linux will ever become a significant force on the desktop?

MS I think that depends on how people define a desktop. If people continue to define a desktop as the thing that they run Microsoft Word on, then Windows will retain its position. My sense, though, is that people are increasingly defining the desktop as the thing that they get access to the internet from. In that case, there's a real possibility that we're able to shift people onto different platforms. I think it's the emergence of the internet as the killer application, the thing that describes what you want from the computer, that opens the door to us.

Upgraded my ancient (IBM i series) laptop from DeMuDi (Debian Sarge-based) to Etch. Involved an hour or two resolving dependencies, and then another couple of hours re-hacking my config files to make them tiny-screen-friendly. I've been using wide screens both at home and at work for a while; it takes a bit of squeezing to fit things back onto 800x600. But I remembered how I'd done it, back when that was a big screen...

There are still a couple of bugs, but they're manageable.

Over the past six months or so, Asus, Everex, and HP have managed to bring low-cost ultraportable notebooks to market. But dozens of other computer makers have promised to bring out their own mini-notebooks. Some will run Linux, while others will be preloaded with Windows XP or Vista. Some will have flash memory, while others will have hard drives. But every one will be smaller, lighter, and cheaper than most existing laptop computers. Here's a roundup of some of the computers that have been announced or are already available.

No, I have NO FSCKING IDEA why my linux-based router won't route packets from the DMZ port to anywhere else. I'm guessing it's some piece of Shorewall misconfiguration that's been lingering around since the last time I tried banging my head against this particular problem.

However, my head is very damned sore now, and it at least continues to route from the internal network, so I was able to put the wireless router there where it used to be. At least it works now, even if it isn't as secure as I would like it to be. What's more, the WAP now seems willing to route to the internal network (it had damned-well better, since it's a host on it), so users of my internal web pages should be happy now.

I'm not happy. But it's less broken than it's been for several months, so I'm going to move on for now.

Note to self: any hostnames used in the firewall rules had better be in /etc/hosts, because you can't get to any DNS servers while the firewall is busy configuring itself.

Duh! It helps to enable masquerading for the interface. It helps to read the useful comment I left for myself in /etc/shorewall/masq. It would help even more if that solved the whole problem: it still doesn't route to the internal network. Grump.

The flower_cat's desktop computer (in the bedroom) appears to have finally bitten the dust -- Windows has been flaky for at least a month, and now Linux is having problems as well. Its CPU fan appears to have died, which has probably caused collateral damage elsewhere. This makes the second of our three Fry's XP boxes to die; the third is the one in the Y.D.'s room. I'll be surprised if that one makes it to the end of the year.

I'm reluctant to just go out and buy her another Windows box -- Fry's track record is pretty poor at this point, and she seems to be happy with Linux on the EeePC. And the budget is still blown all to hell from the wedding and FKO; I really don't need the expense just now. I've been trying to justify a new workstation for the office, because Harmony has become noticeably noisy, but I can't do that either right now, especially when I'm trying to save for an EeePC for the Cat.

So I think what I'll do for the moment is move Dantooine in from the office -- it's an ultra-quiet Mini-ITX system. Fanless, which eliminates that point of failure. We do need a Windows box or two, but that's what virtualization is for.

The other advantage of this move is that it will, at long last, completely defenestrate the computers downstairs. That's a Good Thing.

Well, the flakiness seen yesterday expanded into full-blown falling-apart today: I couldn't even boot. And I'll note in passing that an 8-day-old install CD of Hardy alpha required 600-odd updates. I don't think it's stable yet. I'm going to assume both that the drive is unhappy, and that Hardy Heron isn't ready; I put the old drive back.

On the plus side, I found the install disk for my 802-11g wireless card, and it worked in the Win98 partition. So the machine will be usable regardless. At some point I'm going to try both Gutsy (from the text installer) and Lenny. But not right now: there's a lot on my schedule today.

The following fifty proprietary programs are listed in no particular order within broad categories along with their open source alternatives. In some cases you could probably write your own book on frustrations with the proprietary programs shown here. In other cases, you’ll discover that the open source alternative isn’t quite up to snuff yet. And, in other cases still, you’ll learn that some proprietary programs are real gems, but that the open source advocate can replace those gems with equally shiny objects from the open source repertoire.

In this case, of course, Dorsai is the computer in the bedroom. (This being thestarport.org, all the machines are named after places that could plausibly have starports. The machines that are used for recording and editing music are, naturally, places mentioned in filksongs: the laptop is Argo, and the other workstation is Harmony.) Anyway, it works: I'm posting from it.

The little rolling desk isn't terribly solid, and because it overlaps the bookshelves on the left there isn't room for anything but my Lenovo Thinkpad keyboard. Which is pretty good, and has pointing devices that there otherwise wouldn't be room for, but it's not a Model M.

In addition, it's running Ubuntu Studio instead of Etch; not all my usual fonts are installed (so windows come out the wrong size and don't quite fit properly), (added 02-24: the font problem turned out to be a bad line in .Xdefaults) and it's running Emacs 22.1. I'm not quite ready to make the transition to the new Gnus. OTOH it's fast as a bat. I'd forgotten just how fast it is...

There are still a few piles of stuff scattered around the bedroom that were pulled out of the corner, and the chair isn't particularly comfortable. The recording rig hasn't been reconfigured yet; I'm not sure where the microphones and preamps belong, and there are no monitor speakers (so, basically, I don't have sound on this machine yet).

But, Colleen really likes having me in the bedroom with her, even though she can't see me from where she's sitting. And it does feel comfortable. Moving back and forth between the two systems is slightly painful: I have to kill the browser, and move my IM presence. Not a full solution. It'll take me a while to make the transition smooth; it will probably involve switching to Ubuntu or Lenny on all the clients.

The Wolfling is getting tutoring in math now. Hopefully that will get her through the two classes she needs to graduate. Since her tutor (a family friend) lives most of the way to Palo Alto, the Cat and I proceeded from dropping her off to dinner at Chef Chu's in honor of Chinese New Year. We decided going in that a whole fish, while tempting, wouldn't have given us enough variety, so we had hot and sour soup, tangerine peel chicken, eggplant in garlic sauce, and fried bananas for desert. Yum!

Chef Chu's was my intro to Szechuan cooking when I first came out to California for grad school, 29 years ago.

Coming home, I found that the VIA board had successfully started up X, after the various network-dependent processes timed out. Thus encouraged, I hacked on it for a while and discovered that the onboard ethernet was now eth2. Go figure. I think it has something to do with the hotplug code that I stopped using because it seemed flaky. But it works now: not super fast, but more useable than its predecessor, and totally silent.

The runtime on my UPS is now down from somewhere north of 45 minutes to 39; not too bad, considering.

Hopefully I'll be able to get back to actual (music) work soon.

For some reason Kat's monitor (an ageing 17" Hyundai) has lost the ability to tell the computer at the other end of its cable what its resolution is. We'd just installed a new KVM switch, so I spent quite a lot of time thinking the problem was in the switch. At first it seemed to be -- last time she had problems, I took out the switch, plugged the monitor directly into the computer, and it worked. This time it didn't.

Swapped it with the 17" Samsung on the public system in the office downstairs. Now everything is happy -- Debian Etch on the downstairs machine is set up for fixed resolution, so it ignores the stupid lying monitor and Just Works(TM).

Meanwhile the taxes aren't done and there's practicing to do.

And did I mention that crawling around under desks is bad for my knees?

The last couple of days I've been helping the chaoswolf install Ubuntu on her ageing HP Celeron system. The initial problem, of course, was to back up the old contents; I tried several hacks of varying effectiveness before discovering that the Seagate drive I was using came with a Windows partition-imaging program on its install CD. Who knew?

Once that was taken care of, actually doing the install was a piece of cake, modulo a crash scanning the partition table and its inability to shrink the existing NTFS partition as much as it should have been able to. (There may be a connection.) There may be some bad memory in that box; it's quite flaky.

The Wolfling seems to be pretty happy with Ubuntu, which is a good sign. Of course, she still has her shiny new XP machine; I'll get her a KVM switch tomorrow.

Nova was down again when I got up this morning; I took it as an excuse to disconnect the SATA drives (which I should have done yesterday, but it was getting late). If that fixes it, it's probably a controller issue. If not, it's probably memory. Worst case, I can replace it with Harmony (my current workstation), which has been absolutely solid since I bought it. In fact, that MB/CPU used to be in Nova. Would use more power, but a faster CPU would help for printing and some file operations.

Spent some good time this morning talking with the chaoswolf about upcoming web projects and setting her up with an Ubuntu box. We'll use her old HP Windows box with the new 320GB IDE drive that I originally intended for a USB drive.