Baseball season is here, and so’s Baseball Mogul 2003

Dave Farquhar General , , ,

The Kansas City Royals wised up on Friday and gave Mike Sweeney what he wanted. Well, at least enough of what he wanted that he signed. So Mike Sweeney is now $55 million richer, and the Royals have him locked in for five years, as long as they manage to reach .500 in either 2003 or 2004.
Personally, I wish they’d signed him to a longer deal, but it could be that the second-greatest Kansas City Royal of all time didn’t want more than five years.

To celebrate, I headed over to Sports Mogul to see if there was a new patch to fix some bugs in Baseball Mogul 2002. And I found that Baseball Mogul 2003 is out. I downloaded the demo and played around with it. The free-agency model seems to be more realistic now, and the players aren’t as rigid in their contract negotiations, which may or may not be realistic. The computer GMs offered trades, some stupid, others inspired.

The game crashed as the July 31 trading deadline approached. My Royals were in second place, thanks to a couple of shrewd acquisitions. Predictably, with one more really big stick in the lineup, Mike Sweeney and Mark Quinn hit a whole lot better. It crashed as I was wheeling and dealing, looking for a catcher with a little bit of pop in his bat and maybe a veteran starting pitcher. I’d signed Bret Saberhagen and David Cone as free agents for old times’ sake, but they had nothing left.

At any rate, for 20 bucks, why not get the full version, I figued, especially since I could plunk down the credit card, they’d ship me the retail box in mid-April, and in the meantime I could download and install a 75-meg package?

I like the new version better than the old one. And of course the old one was good enough that I once deemed it a necessity of life. The new one adds a few features, like letting you set prices for concessions (so I guess I can do a 10-cent beer night like Bill Veeck did one year in Chicago), and it adds play-by-play, which is tedious during the regular season, but great for watching games like the All-Star Game and the World Series.

What can I say? For a baseball strategy nut like me, Baseball Mogul is really hard to beat. It would be nice if it would do some more statistics, so you could do lefty/righty platoons. These days, there are managers who decide who’s playing based on whether there’s a right- or left-handed pitcher on the mound, whether it’s a day or night game, home or road game, and whether the game’s being played on turf or grass. You think I’m kidding.

The other feature I wish it had was hirable managers. The only game I’ve ever seen that had that feature was Earl Weaver Baseball, which was popular more than 10 years ago.

But even with those shortcomings, it’s still an incredibly addictive game. I haven’t found a better baseball sim yet. And despite its bad first impression, it’s less buggy than its predecessor.

Some video editing tips from the school of hard knocks

Dave Farquhar Video , , , , ,

Hi. My name is Dave. I attended the best journalism school there is for broadcasting.
I paid almost zero attention in the television units, because, well, I hate TV. So I learned nothing that would be of use to me at this stage of life. Aside from how to go get a story and ask questions and gather footage, which is pretty much the same no matter what your medium is, whether it’s a newspaper, a magazine, a video documentary, a Web page, or a research paper. We all have a sense for what’s interesting and relevant. Develop that, and you can tell a story in any medium.

OK, that’s all I know about video editing theory. That was easy, wasn’t it? Aren’t you glad you didn’t pay $200 per credit hour for it?

Now let’s get practical. This is going to be most practical if you have equipment similar to mine. If you don’t, hopefully it’ll tell you something useful.

Here’s what I use to make magic happen on the boob tube:

IBM-compatible PC

  • AMD Duron 700 MHz CPU

  • 384 MB PC133 memory

  • Adaptec 19160 Ultra160 SCSI card

  • Maxtor Atlas III 10,000 RPM 18GB Ultra160 SCSI hard drive

  • Quantum Fireball 15 GB UDMA66 hard drive

  • Plextor UltraPlex 40max SCSI CD-ROM for audio capture

    • Pinnacle DV500 Plus editing/capture card
    JVC GR-DVL100 miniDV camcorder

    You can capture video with Adobe Premiere, but there’s a lot of overhead involved. It’s better to use the bundled Pinnacle DVTools app. I was in the habit of capturing with DVTools, then using the freeware VirtualDub (do a Google search) to convert those files to Indeo 5.1 format to save space. I saved a lot of disk space, but I wasted a lot of time. A PC equipped with a DV500 can do most things to DV-formatted files in realtime, whereas my setup has to render other file formats. You’re looking at 2-4 frames per second to do the initial conversion, and then Premiere renders them at a similar rate. Get monster hard drives so you can hold those larger DV files, and you’ll save lots of render time. You’ll also completely eliminate generation loss, which is the whole point of digital video in the first place, although the generation loss from rendering DV to Indeo back to DV isn’t something anyone’s likely to notice. Realistically, you’ll lose more as the signal is being transmitted from the camera to your screen than you will from three generations of conversion.

    I find playback off my UDMA drive less than adequate. It doesn’t drop frames but the video has too many artifacts. It’s fine as a holding bin for clips I might use, or for editing, but before I do my final output to tape, I move the files over to my high-speed SCSI drive.

    On some platforms, you really want to have your OS and apps on one drive, your video on another, and your audio on yet another. I find the Atlas III is more than fast enough to hold all three and get away with it. If I had to do it all again though, I’d probably still get the Atlas, and I’d get another very large but slower SCSI drive.

    When you’re editing with Premiere, you may find your hard drives fill up at an alarming rate. Before starting a project, search for directories called Adobe Premiere Preview Files and clear their contents. I found a missing 4 gigs that way. Also defragment your drives before starting on a project. You want big, contiguous blocks to hold your huge video files.

    You can’t just plug a camcorder into your firewire port and go to File, Export Timeline, Print to Tape and expect it to work. You have to put your camcorder into VTR mode first, an operation that isn’t always obvious from looking at the camera. Check your manual. On my DVL100, turning the mode knob to Play does the trick.

    Also, you can’t plug a camcorder in hot. At least not any of the JVC cameras I’ve tried. The computer will see them, but it won’t be able to control them. Shut down the computer and turn off the camera, plug in, then power both up, and they’re happy.

    Although Pinnacle’s DVTools can export DV to tape, it’s faster to do it from Premiere. It takes Premiere forever to export a video to disk in DV format, and then of course the export to tape happens in real-time. Doing it from Premiere in the first place cuts the time required by 3/4.

    And here’s a principle I learned at a seminar earlier this year at Ginghamsburg United Methodist Church in Dayton, OH: There’s no such thing as junk video. Ginghamsburg’s video director actually advocates leaving your camera on at all times, even when you’re moving the camera, because a lot of times you’ll shoot good video unintentionally. I don’t have the battery life to be able to leave it on all the time, but I leave it on more than I normally would. I found in my last project, where I was filming fire, that the smoke and heat waves coming off the fire confused my camera’s autofocus, so the camera was trying to find what it was supposed to focus on, which futher accentuated the heat waves and produced a really haunting effect. People asked me how I did it, what it was, where I shot it. It was pretty anticlimatic, I’m sure, to hear it was just a tree off in the distance. And I got the shot strictly because I wasn’t paying attention. The fire had died down and I hadn’t noticed.

    All cameras have particular nuances. That scene probably would have looked different with another camera. I discovered later how to confuse my autofocus when I was trying to set the camera up for playback. The only way you’ll learn your camera’s nuances is to play with it. And be sure to try things with it you wouldn’t normally try. I discovered the autofocus thing when the camera was pointed at my desk at extremely close range. Believe me, there’s absolutely nothing compelling about that desk. It’s 18-year-old particle board.

    And a principle I learned myself: There are a couple of ways I find my best footage. One way is just to fast-forward through it and watch. If it’s compelling at 20x normal speed with fuzzy detail, it’s likely to be compelling when played the way it was shot. The other thing I’ll do is play the footage in my monitor, and watch out of my peripheral vision while I do something else. If it’s good enough to grab my attention, chances are it’s worth using. It’s a brutal way to edit, but if you have to condense several hours’ worth of footage into three minutes, it’s the fastest way I’ve found.

    Cult of Linux, and cheap cheap hardware

    Dave Farquhar Hardware , , ,

    Potpourri. I just have two little things to write about today, so that’s what I’ll do.
    The Cult of Linux, and cults of computing past. In yesterday’s comments, Dave Thorarinsson brought up an interesting phenomenon. He observed, when talking about his new Linux box and losing track of time learning it, “It pretty much feels like the time I had my Amiga.”

    I remember reading in the mail section of Amiga magazines, more than a decade ago, “I haven’t had this much fun since I got my C-64!” And the old Commodore magazines noted that their C-64s had a special place in their devotees’ hearts and asked, “Have you ever heard of anyone getting attached to a PC clone?”

    The inferred answer is no. And that doesn’t seem to have changed. Today, the biggest PC enthusiasts replace their machines frequently, relegating their old, unbeloved machines to grunt roles, or scrapping them for parts.

    The C-64, by contrast, was a simple machine. Although it only had one slot for expansion, the motherboard itself was simple enough that just about anyone with a little bit of patience could trace it out and understand it. There was some unused address space in it that you could add chips to. Common projects included speech synthesizers and an extra sound chip, so you could have six-voice, stereo sound. And it seemed like most C-64 owners had tried their hand writing at least simple programs.

    The Amiga was similar. It was harder to program, and a little harder to hack, but I had a subdirectory on my Amiga’s hard drive that was called “PD Hardware,” containing makeshift schematics for stuff I could build. I wired in a PAL/NTSC switch so I could change video standards and run European software correctly. I even designed an add-on board for it myself, once, to give myself an extra ROM socket. And of course I replaced much of the operating system with replacement utilities written by hobbyists that were smaller and faster, had more features, or both.

    You want to know why the Amiga and C-64 fanatics were so loyal? They knew their machines inside and out, and to a degree that just wasn’t possible with a PC clone.

    With Linux, the hardware doesn’t matter anymore, but you can customize the software to whatever extent you want. The hardest-core Linux people are doing just that. At a level below that, people compile the OS from source, from scratch. At a level below that, they just replace utilities with smaller and faster or more functional ones, like I was doing with my Amiga.

    The long and the short of it is tweakers have a lot more liberties with Linux than they’ll ever get out of Redmond.

    People who liked my book can certainly find a lot to like with Linux. People who fancy themselves experts but don’t really want to know how their computers work and who think books like mine are a waste of time will never be tied to Linux like the fanatics are.

    Cheap hardware. It’s a buyer’s market. I’m building an intranet server for my church, and they have lots of bits and pieces but not quite enough for a complete system, so I did some looking around at my favorite bottom-fishing holes. You can get an awful lot of computer for next to nothing these days.

    I’ve bought things at least once from each of these vendors, and they got stuff to me reasonably fast (within a week, ground shipping) so I feel reasonably comfortable recommending them.

    Slot-1 barebones systems — case, power supply, slot 1 mobo (66 MHz FSB, so you’re stuck with P2s up to 333 MHz or Celerons, and according to the manufacturer, Celerons will work), and a floppy drive. $24.50. $19.95 if you don’t mind some wear. Very nice.

    At the same place, scroll down and you can pick up Tier-1 business-class P2s for under $200. If you’re lucky you can sometimes even find a dual-capable machine. They go fast, but the getting’s good. Lots of businesses are dumping these due to their 3- or 4-year upgrade cycles. For someone who just wants to do word processing and e-mail, these systems are overkill. If you want to upgrade in pieces over the course of the next couple of years, the P2s with a 100 MHz FSB are workhorses and you can add lots of cheap memory, nice video cards, and fast, cheap hard drives. Gatermann just picked up an HP Vectra P2-266, dual capable, with SCSI, for $117. It will serve him well. He plans to run Debian on it, but I don’t know if he’s thinking of it as a server or a workstation. It’d make a fabulous server.

    72-pin SIMMs — if you’ve still got a system that takes them, nice deals on 4-16MB sticks, and good deals on bigger sticks.

    Low-end Pentium I desktops — P75-120, 16 meg of RAM, 1 MB video, who knows what else. $29.99. Nice for a low-end Linux box, or for a Win95 system that’s going to see limited use. Put a fast hard drive in it and it’ll surprise you. After you get yours, check and see what CPUs the system will take; a P200 can be had for as little as $16 and makes a nice upgrade. It’s a pretty big step up from 75 MHz to 200 MHz.

    Seagate 9-gig 5.25″ full-height SCSI HD — $12.95. If you’ve got two 5.25″ bays open and no spacer between them, here’s a cheap way to fill it with 9 gigs of storage. I know a couple of people who have these drives. They’re surprisingly quick (they hold their own next to 7200-rpm 3.5″ disks). Back up your data and buy some spares if the shipping doesn’t kill you. One of the guys I know has several of these, and he’s had one or two die on him.

    FIC AZ-11 ATX mobo — $34.95. It’ll take Durons and Athlon Thunderbirds. The fastest chip I’ve put in one is a 1 GHz Duron. No ISA slots and just 5 PCI slots, but it’s a capable board. I use one in my video editing workstation, and I paid more than 35 bucks for it. Totally obsolete, but when you can get a 1 GHz Duron and fan on this board for $89, who cares? It’ll still be a good computer in three years. Trust me.

    I keep seeing this board on the closeout places, so I expect even after the current supply dries up, there’ll be more.

    Speaking of closeout motherboards, there’s a variety of them over at Just Deals. You can get a Soyo Socket 370 board for $28 and various Socket A boards in the $35-$40 range. If it’s Slot 1 or even Slot A you’re looking for (maybe you’ve got a CPU laying around), you can find stuff there too.

    And if you need a cheap copy of Word 97, you can get the Works 99 suite for 30 bucks.

    Need an operating system for that new old computer? Prices range from $25 for Win95 to $180 for WinXP Pro.

    Dave installs Windows XP

    Dave Farquhar Windows , , , , , ,

    We needed an XP box at work for testing. Duty to do the dirty deed fell to me. So after ghosting the Windows 2000 station several of us share, I pulled out an XP CD. It installed surprisingly quickly–less than half an hour. The system is a P3-667 with 128 MB RAM and an IBM hard drive (I don’t know the model).
    It found the network and had drivers for all the hardware in the box. That doesn’t happen very often with Microsoft OSs, so it was nice.

    I booted into XP, to be greeted by a hillside that was just begging to be overrun by tanks, but instead of tanks, there was this humongo start menu. I right-clicked on the Start button, hit Properties, and picked Classic view. There. I had a Win95-like Start menu. While I was at it, I went back and picked small icons. I don’t like humongous Start menus.

    I also don’t like training wheels and big, bubbly title bars. The system was dog slow, so I right-clicked on the desktop to see what I could find to turn off. I replaced the Windows XP theme with the Classic theme. Then I turned off that annoying fade effect.

    Still, the system dragged. I went into Control Panel, System, Performance. Bingo. I could pick settings for best appearance (whose choices are certainly debatable–I guess they look good if you like bright colors and have a huge monitor) or best performance. Guess which I picked? Much better.

    Next, I went into Networking. I saw some QoS thing. I did a search. It’s intended to improve the quality of your network, at the price of 20% of your bandwidth. Forget that. I killed it.

    After I did all that stuff, XP was reasonably peppy. It logs on and off quickly. I installed Office 2000 and it worked fine. The apps loaded quickly–just a couple of seconds. That’s how it should be. If I went in and edited the shortcuts in the Start menu to turn off the splash screens, they’d load instantly.

    WinXP brings up a bunch of popups that I don’t like. If I wanted unexpected popup windows, I’d run a Web browser. I couldn’t quickly figure out how to disable those.

    I couldn’t run Windows Update. It froze every time I tried.

    I found a Windows XP tuning guide at ExtremeTech. I suspect turning off the eye candy will help more than most of the suggestions in that article. I suspect if I dug around I’d find other things. We’ll see if I get some time.

    XP isn’t as bad as I expected, I guess. But I’m still not going to buy it.

    This, on the other hand, is worth a second look. And a third. You can now run MS Office on Linux. No need to wait for Lindows, no need to abandon your current fave distro (at least if your fave distro is Red Hat, SuSE, Mandrake, Debian, or Caldera).

    It’s 55 bucks. It’s available today. It brings Office 97/2000 and Lotus Notes r5 to your Linux desktop. Other Windows apps work, but their functionality isn’t guaranteed.

    You can get some screenshots at CodeWeavers. It even makes the apps look like native Linux apps.

    Spontaneous system reboots

    Dave Farquhar Troubleshooting , , , , ,

    Steve DeLassus asked me the other day what I would do to fix a PC that was rebooting itself periodically. It’s not him who’s having the problem, he says, it’s someone he knows. He must be trying to show up someone at work or on the Web or something.
    So I gave him a few things I’d check, in order of likelihood.

    Static electricity. A big static shock can send a system down faster than anything else I’ve seen. Keep a humidifier in the computer room to reduce static electricity. If you’re really paranoid, put a metal strip on your desk and connect it to ground (on your electrical outlet, not on your PC) and touch it before touching your PC. Some people metalize and ground part of their mouse pad. That’s a bit extreme but it works.

    Power supply. This is the big one. A failing power supply can take out other components. And even if you have an expensive, big-brand box like a PCP&C or Enermax, they can fail. So I always keep a spare ATX power supply around for testing. It doesn’t have to be an expensive one–you just want something that can run the machine for a day or two to see if the problem goes away.
    Overheating. Check all your fans to make sure they’re working. An overheated system can produce all sorts of weird behavior, including reboots. The computer we produced our school newspaper on back in 1996 tended to overheat and reboot about 8 hours into our marathon QuarkXPress sessions.

    Memory. It’s extremely rare, but even Crucial produces the occasional defective module. And while bad memory is more likely to produce blue screens than reboots, it’s a possibility worth checking into. Download Memtest86 to exercise your memory.

    CPU. If you’re overclocking and experiencing spontaneous reboots, cut it out and see what happens. Unfortunately, by the time these reboots become common, it may be too late. That turned out to be the case with that QuarkXPress-running PC I mentioned earlier. Had we replaced the fans with more powerful units right away, we might have been fine, but we ended up having to replace the CPU. (We weren’t overclocking, but this was an early Cyrix 6×86 CPU, a chip that was notorious for running hot.) Less likely today, but still possible.

    Hard drive. I’m really reaching here. If you’re using a lot of virtual memory and you have bad sectors on your hard drive and the swapfile is using one or more of those bad sectors, a lot of unpredictable things can happen. A spontaneous reboot is probably the least of those. But theoretically it could happen.

    Operating system. This is truly the last resort. People frequently try to run an OS that’s either too new or too old to be ideal on a PC of a particular vintage. If the system is failing but all the hardware seems to be OK, try loading the OS that was contemporary when the system was new. That means if it’s a Pentium-133, try Win95 on it. If it’s a P4, try Windows 2000 or Windows XP on it. When you try to run a five-year-old OS on a new system, or vice-versa, you can run into problems with poorly tested device drivers or a system strapped for resources.

    Another good OS-related troubleshooting trick for failing hardware is to try to load Linux. Linux will often cause suspect hardware to fail, even if the hardware can run Windows successfully, because Linux pushes the hardware more than Microsoft systems do. So if the system fails to load Linux, start swapping components and try again. Once the system is capable of loading Linux successfully, it’s likely to work right in Windows too.

    Troubleshooting advice: When you suspect a bad component, particularly a power supply, always swap in a known-good component, rather than trying out the suspect component in another system to see if the problem follows it. The risks of damaging the system are too great, particularly when you try a bad power supply in another system.

    And, as always, you minimize the risks of these problems by buying high-quality components, but you never completely eliminate the risk. Even the best occasionally make a defective part.

    Sexual Harassment training

    Dave Farquhar St. Louis

    Warning: This entry is rated PG-13. No animals were harmed in the making of this post. And all other standard disclaimers apply.
    On Saturday, before the hammer fell, I was out chasing trains and airplanes in a train. Gatermann hadn’t ridden Metrolink (St. Louis’ light-rail system) on the East Side yet, so we went off sightseeing. Anyone from St. Louis will know the connotations the East Side has, but those weren’t the kinds of sights we were after. We were looking for modern ruins, not scantily-clad women. And we found some modern ruins, including an abandoned Drive-In Theater that must have been at least 30 years past its prime.

    We took another friend along, female. I won’t say her name because she gets mad when I write about her.

    We were on the train, with me sitting at a window seat, she in the window seat behind me, and Gatermann in the window seat across the aisle from her. Suddenly she tapped me on the shoulder. “Dave, help me.” I looked back at her. She was breathing OK, and as far as I could tell there wasn’t anything physically wrong with her. She beckoned behind her. I saw a guy sitting in a seat behind her, but he was looking the other direction and seemed to be minding his own business, reading (or pretending to read) a newspaper. I asked her what she needed. She beckoned in the direction of that same guy, whose face remained buried in that paper. Seeing the bewildered look on my face, Gatermann started wondering what was up, so he came over and sat next to her. She didn’t say anything. The train pulled to a stop, and the guy she’d been beckoning towards stood up and exited, giving us a quick sideways glance before heading off on his way.

    Once the train started moving, she mouthed the words, “Is he gone?”

    I said yes. She started to talk.

    “That guy,” she said, pointing at the seat he’d been sitting in, “He motioned towards me, then he said, ‘Hi.’ Then he mouthed the words, ‘I want to lick you.'”

    Gatermann and I started snickering, because, well, this guy wasn’t even close to being in her league, but besides that, the nerve of the guy! I’m the kind of guy who has trouble walking up to a girl I don’t know even if she’s acting extremely interested, and Gatermann makes me look like an extrovert, and here’s this skuzbucket saying that kind of stuff to a girl when he doesn’t even know her name?

    That kind of stuff happens to her a lot, and she asked why. It’s pretty simple. There are a lot of creeps out there looking for girls who’ll take them up on those offers, and if 99 out of 100 girls say no, he’s still happy because of the one who didn’t. Maybe he’s even happy if only 1 out of 1,000 girls say yes. By the time he was off the train he’d written her off. It’s no knock on her. He probably literally does say that to all the girls–at least all the girls he sees who aren’t wearing a ring on their left ringfinger.

    What made it really ironic was that she’d been griping all morning about having to go to sexual harrassment training last week, and Gatermann and I had been amusing ourselves by looking for signs or other things she wouldn’t be able to say at work.

    But I think that creepy guy came up with the most blatant violation.

    And now I know why no girls I know want to ride Metrolink alone.

    Personal problems.

    Dave Farquhar General

    I’ve got some personal problems going on right now. They’re not so much my problems as they are problems of a personal nature, and as much as I would love to get out my poison pen and machine gun a few people’s names in public, I’m not going to do that. Dragging people’s names through the mud doesn’t accomplish anything. They’ve tarnished the reputations of some of my family members by doing that to them, but I want to be above that.
    That said, it’s a really good thing I don’t have that Tu-144, because I’d be buzzing someone’s house at Mach 1 right now if I did, and I doubt that would be pretty.

    I don’t know what this means for anything else. Writing here helps me to focus and to take my mind off the garbage that goes on outside my front door. So I don’t expect any long hiatus or anything like that. What I intended to post right now isn’t going to happen. I’ve written a couple of paragraphs but that’s it. I might finish it tomorrow.

    So that’s what’s going on. Those of you who pray, if you’d say one for my family in general, I’d appreciate it. (I don’t want to get any more specific than that. God knows the situation, and He knows it a whole lot better than I do anyway.)

    I just got back from a Third Day concert

    Dave Farquhar General

    I just got back from a Third Day concert and I’m dead tired. I’ll say this about Third Day: they’re amazing musicians and they’re amazing men. Mac Powell was constantly reaching down to shake hands with people in front of the stage (and he let them be right up at the stage). If he didn’t have a guitar in his hands and he wasn’t singing, he was shaking someone’s hand. And at the end of the concert, all the band members handed their instruments to their techs, hugged each other, then went and spent several minutes shaking as many hands as they could.
    Third Day did a live album last year, and it’s really good–I like it better than some of their studio albums–but I don’t think that album did their live shows justice. The visuals were stunning, but seeing them at work makes a big difference. They’re four guys who’ve known each other more than 10 years, and from all indications onstage, are really good friends. They all look like guys I went to college with. They’re genuine people, doing what they enjoy doing, and they have no pretentions about them, even though they are extremely good at what they do.

    And “extremely good” is an understatement. You can always tell when a band sounds too good–you’ll never duplicate the studio sound onstage. But they adapted their songs for the live show and the songs didn’t sound at all compromised. I’ve seen a lot of bands live and heard even more live recordings, and these guys are the best. The two best live shows I’ve seen were U2 and The Cure, but these guys were better, although less flambouyant.

    I’ll be back later today to talk about other stuff. See you in a few hours.

    Linux reliability

    Dave Farquhar General , ,

    Linux reliability. Steve Mahaffey brought up a good point yesterday, while I was off on a consulting gig, where I learned one of the secrets of the universe–but since it’ll bore a lot of people to tears, I’ll save that for the end.
    I’ve found that text-based apps and servers in Linux are extremely reliable. As David Huff’s tagline reads, “Linux: Because reboots are for upgrades.” If you’re running a server, that’s pretty much true. Unless you have to upgrade the kernel or install hardware that requires you to open the case, you can go for months or years without upgrading it.

    The problem with Linux workstations is that up until very recently, the GUI apps people want to run the most have been in beta. The developers made no bones about their quality, but companies like Red Hat and Mandrake and SuSE have been shipping development versions of these apps anyway. On one hand, I don’t blame them. People want programs that will do what they’re used to doing in Windows. They want word processors that look like Word and mail clients that look like Outlook, and if they’re good enough–that is, they don’t crash much more than their Windows equivalents and they provide nearly as much functionality, or, in some cases, one or two things MS didn’t think of–they’ll put up with it. Because, let’s face it, for 50 bucks (or for nothing if you just download it off the ‘net) you’re getting something that’s capable of doing the job of Microsoft packages that would set you back at least $1,000. Even if you just use it for e-mail and Web access, you come out ahead.

    The bigger bone I have to pick with Red Hat and Mandrake and, to some extent, even SuSE is where they put experimental code. I don’t mind experimental desktop apps–I’ve been running Galeon since around version 0.8 or so. But when you start using bleeding-edge versions of really low-level stuff like the C compiler and system libraries just to try to eke out some more performance, that really bothers me. There are better ways to improve performance than using experimental compilers. Not turning on every possible daemon (server) is a good start.

    Compile beta-quality apps with a compiler that’s beta quality itself, and throw in every other bleeding-edge feature you can think of, and you’ll end up with a system that has the potential to rival Windows’ instability. Absolutely.

    That’s one reason I like Debian. Debian releases seem to take as long as the Linux kernel does, and that’s frustrating, but reassuring. You can install the current stable Debian package, then add one or more of the more desirable apps from either the testing or unstable tree (despite the name, Debian unstable’s stability seems comparable to Mandrake) and have the best of all worlds. And when a .01 release of something comes out (which it always seems to do, and quickly) it’s two commands to upgrade to it.

    It’ll be interesting to see how Lycoris (formerly Redmond Linux) pans out. Lycoris appears to take a more conservative approach, at least with the number of apps they install. If that conservatism extends to the versions of those packages they install, it’ll go a long way towards extending server Linux’s reliability to the desktop.

    Debian is intimidating. I find it less intimidating than Slackware, but it does zero handholding during installation. So generally I recommend someone start with SuSE or Mandrake or Red Hat, get comfortable with how things are laid out, and get familiar with PC hardware if not already, and then, once feeling brave, tackle Debian. Debian is hard to install, but its quality is pristine and it’s exceptionally easy to maintain. Debian developers try to justify the difficulty of installing it by saying no one ever has to install it twice on the same PC, and they’re right about the second part. Eventually I expect they’ll take the installer from another distro that’s based on Debian to make it easier, but it won’t be in Debian 3.0 and it may not make it into 3.1 either.

    The secret of consulting. My employer sent me off on a consulting gig yesterday. The main reason for it, I suspect, is because of my training as a journalist. It means I can ask questions, keep track of the answers, and make a PowerPoint presentation that looks decent.

    Consultants get a bad rap because they’re notorious for not knowing anything. You pay lots of money to have someone who knows nothing about you and potentially nothing about your problem come in and ask questions, then come back later and give you a dog-and-pony show featuring sugar-coated versions of your answers and little else.

    I won’t say who my client is, nor will I say who my employer is. What I will say is that my partner in this endeavor knows a whole lot more about the subject matter than I do. I’ll also say that the two of us are good researchers and can learn very quickly. Our regular job titles attest to that. We both have liberal arts degrees but we primarily work as systems administrators. We didn’t learn this stuff in school.

    Up until Monday, I knew nothing about our client. Absolutely nothing. Up until yesterday afternoon, I knew nothing meaningful about the client. I knew its name and what its logo looked like, the name of one person who worked there, and I had a vague notion what they wanted to know.

    I think that was an advantage. We both asked a lot of questions. I wrote down the answers quickly, along with whatever other information I could gleen. We left three hours later. I had six pages of typewritten notes and enough documents from them to fill a standard manilla file folder. We knew what they didn’t want, and we knew they were willing to throw money at the problem.

    There’s such thing as knowing too much. One of the solutions they’re considering is overkill. The other is underkill. The difference in price between them is about 3 times our consulting fee. It took me another hour’s worth of research to find something that will give them the bare minimum of what they need for about $500 worth of additional equipment on top of the low-ball figure. When you’re talking the high-ball figure costing in excess of $40,000, that’s nothing. I found another approach that basically combines the two that will double the cost of the low-ball figure, but still save them enough to more than justify our fee.

    I don’t know their internal politics or their priorities on the nice-to-have features. My job isn’t to tell them what to buy. Nor is it my job to give them my opinion on what they should buy. My job is to give them their options, based on the bare, basic facts. Whatever they buy, my feelings won’t be hurt, and there’s every possibility I’ll never see them again. They’ll make a better-informed decision than they would have if they’d never met me, and that’s the important thing to all involved.

    I never thought I’d be able to justify a role as a high-priced expert on nothing relevant. But in this case at least, being an expert on absolutely nothing relevant is probably the best thing I could have brought to the table.

    And since we haven’t done a whole lot of this kind of consulting before, I’ll get to establish some precedents and blaze a trail for future projects. That’s cool.

    That other thing. There’s a lot of talk about the current scandal in Roman Catholicism. It’s not a new scandal; it’s been a dirty little — and not very well-kept — secret for years. There’s more to the issue than we’re reading in the papers. I’ll talk about that tomorrow. I come neither to defend nor condemn the Roman Catholic church. Its problems aren’t unique to Catholicism and they’re not unique to the Christianity either. Just ask my former Scoutmaster, whose filthy deeds earned him some hefty jail time a decade and a half ago.

    Stay tuned.

    Pretentious Pontifications, Part II

    Dave Farquhar General

    David’s off on a gig. So I get to post again.
    I flew my private Tu-144 out to Hearst Castle last weekend, where I rented a room and set up sound equipment. It was a grand day. Because Hearst Castle is on the ocean, the waves beat against the castle.

    I sat down to pontificate, and I found that the sentient sound of the waves didn’t sound nearly as inveigling as the sound of my voice.

    I asked the audio engineer if he could filter out the sound of the waves. He said he could.

    So I picked up where I left off, pontificating about whatever came to mind.

    It was fabulous. I spoke with panache. I was laconic. It was completely unlike le Raunche a la Stenche’s recent bumptious platitudes, and way out of the league of most of the drivel I read on the Web.

    David actually found the Tu-144 for me. After the highly-publicized Concorde crash nearly two years ago, David read a story claiming that the Concorde was the only operational supersonic airliner. In a flash of memory that almost impressed me, he said, “The Soviets had an SST. What was it called, the Tu-144? Whatever happened to that?” So he did a Web search. Then he found out the Tu-144 last flew as a jetliner in 1978. He could have found that out a lot faster if he had just asked me, but he didn’t.

    But one of the pages he found listed a pair of Tu-144s for sale. His ignorance paid off, in the form of the private jet I’ve been looking for.

    As for le Raunche a la Stenche’s assertions about my aviation, astute readers will note that the Tu-144 page I linked to was from the Wayback Machine. The real page is no longer available, and for good reason. I bought the plane. It would truly be an anathema if they sold my plane, after I paid a perfectly good $10 million for it. Raunche is just mad that he couldn’t schmooze his way into getting them to give the plane to him for “evaluation and review.” That didn’t work for this. This is quality hardware.

    Too bad it wasn’t built by Intel.