Honest, the money was burning a hole in my pocket!

Dave Farquhar General , , , , , ,

I went out shopping yesterday for a white gold rope to go with a white gold cross pendant I bought a month or so ago. I’m no expert on jewelry, but my sister knows as much about jewelry as I do about computers and baseball combined, and she said I shouldn’t buy silver unless I was going to wear it all the time. I don’t wear jewelry all the time, so I took her advice and bought white gold.
I found the chain.

Then I wandered over to the electronics aisle. I saw a $129 KDS 17″ monitor. Pass. I saw other monitors of varying sizes and qualities. Then I walked down the next aisle, where I saw HP Pavilion and Sony VAIO computers. Nothing earth-shattering. Then I saw something that made me do a couple of quadruple takes. A Lexmark color laser printer. Price? Seven hundred bucks. I was shocked. I’m pretty sure the last time I looked, the cheapest color laser you could find was $1500. I remember in the summer of 1994 selling a number of color inkjet printers for $649. So $700 for a color laser printer is a significant milestone, and it’s reason not to pay more than $100-$150 for a color inkjet. If you’re serious about color printing, that laser will give far better output, much faster, and at a much lower cost per page.

Yes, I’d love to have one. But I’ve got a Lexmark 4039 I bought in 1996. It still works fabulously. It also still has the toner cartridge that came from the factory in it. Needless to say, I don’t print a lot. So I really don’t know how I could justify a color laser printer.

So I walked on. I spied some DVDs. I flipped through them. Just a bunch of mediocre movies, most of which I’d never bothered seeing, so I wouldn’t have any inclination to pay $12.99 for them either. Then I turned around. Camcorders! I saw some Sony and Hitachi models, VHS-C and Digital-8, priced very nicely. Very nicely. At $200, I don’t understand why camcorders aren’t as common as VCRs were 10 years ago. You can get a nice camcorder now for what a nice VCR cost then. But that wasn’t what I was looking for.

Next section: JVC and Sony camcorders. Much pricier, but they had the magic word I was looking for: miniDV. I looked at the price: $480 on the entry model. That was about half what the entry models cost the last time I looked. I played around with it. The picture was awfully nice. I played around with the more expensive models. The picture wasn’t any nicer. So I wrote down the model numbers. At $480, I was almost ready to buy right then and there. But $480 is too much to spend casually, so I did a little research online.

Camcorder tip: Go ahead and search the Web for camcorder specs and reviews, but expect not to find much. Searching the web gives the impression the JVC GR-DVL805 doesn’t exist. The low-end JVC GR-DVL100 did have some positive reviews. I searched Google groups and found lots of good insights on both models. (If I find a consensus amongst a bunch of hobbyists who bought a product with their own money and used it long enough to get an opinion on it, I generally trust them. I certainly trust them more than a salesman, and there are problems these people will notice that a video magazine won’t due to lack of time with the unit.)

The DVL100 is lightweight, does a great job of gathering light (most JVCs do, in my limited experience), reasonably easy to use, and the price is right. Only complaint I could find: the tape motor is close to the mic, so you’ll get some motor noise. That’s not much concern for me.

The 805 is essentially the same camera, but it can double as a 0.8-megapixel digital still camera. Other than that, it has the same strengths and weaknesses as its cheaper brother. Since a 0.8-megapixel digital still camera is essentially worthless unless you’re shooting pictures for the Web, that feature isn’t useful to me.

Both camcorders had a few other weaknesses: You can’t plug an external mic into them, and while you can dump video from the camera into the computer via a firewire port, you can’t dump edited video from the computer back to the camera. Those are higher-end features. Neither of those matter much to me either. When I’m doing really serious work that requires those, I’ll be borrowing my church’s professional-grade JVC camera, which does everything but autofocus and make coffee. For projects where I record the audio separately (which is common), this camera will be fine. And as a second camera, it’ll be great.

So I bought it.

I’m amazed at how much video recording and editing power you can buy for $2,000 these days. For 2 grand, you can get a Pinnacle DV500 editing board (with Adobe Premiere bundled) and a low-end digital camcorder and still have plenty left over to buy a computer to connect it all to.

A couple of quick things

Dave Farquhar General , ,

Scanners in Windows 2000. While those two pompous, arrogant gits were out romping about and insulting one another, I was helping Gatermann put together an all-SCSI Windows 2000 system. I talked about that earlier this week. After much wrestling, we got the system booting and working, but his expensive Canon film scanner, which was the reason for all of this adventuring in the first place–his eclectic mix of Ultra160 and SCSI-2 and internal and external components was too much for his old card to handle–wouldn’t work under 2000. It worked fine in Win98, however. But if you’re scanning film, you’re pretty serious about your work, and 2000’s lack of stability is bad enough, while Win98’s lack of stability is enraging.
Side note: His scanner worked just fine in Linux with SANE and GIMP. The SANE driver was alpha-quality, but once he figured out the mislabeled buttons, it worked. Though flawed, it was no worse than a lot of drivers people ship for Windows, and it wasn’t any harder to set up either. Not bad, especially considering what he paid for it.

Gatermann, being a resourceful sort, did a search on Google groups and found a suggestion that he update his ASPI drivers. Since he had an Adaptec card, he could freely download and use Adaptec’s ASPI layer. He did, and the scanner started working.

It’s been a long time since I’ve had to do that to get a scanner going, but it’s been a long time since I’ve set up a SCSI scanner too.

Debian. At work on Friday, I booted the computer on my desk into Linux out of protest (more on that later… a lot more) and I figured while I was in Linux reading and responding to e-mail and keeping up with the usual news sources (I wasn’t having to do any NT administration at the time, which was why I was able to protest), I’d run apt-get update and apt-get upgrade. I run Debian Unstable at work, because Debian Unstable, though it’s considered alpha, is still every bit as stable as the stuff Mandrake and Red Hat have been pushing out the door the past 18 months. It’s also about as close to cutting-edge as I want to live on. Well, it had been a while since I did an update, and I was pleasantly surprised to find I suddenly had antialiased text in Galeon. That’s been my only gripe about Galeon until recently; the fonts looked OK, but they looked a whole lot better in Windows or on a Mac. The quality of the antialiasing still isn’t as good as in Windows, which in turn isn’t as good as on the Mac, but it’s better than none at all.

Galeon was already faster than any Windows-based browser I’d seen, but a recent Galeon build combined with the 0.99 build of Mozilla seemed even faster, and Web sites that previously didn’t render quite right (like Dan’s Data now rendered the same way as in that big, ugly browser from that monopolist in Redmond.

I expect with these last couple of updates, I’ll be spending even more time in Linux from here on out. I already have a full-time Linux station, but I use it about half the time and my Windows 2000 station about half the time. I may limit the Windows 2000 station to video editing very soon. And with some of the cool video programs out there for Linux now, it may share time. I suspect I’ll be doing editing on the Windows box, post-production on the Linux box, and then outputting the results to tape on the Windows box.

Dinner with an old friend

Dave Farquhar General , ,

Whew. I’m glad that’s over. Well, I’m not so sure it’s over. But that was a little too weird for me.
I had dinner last night with a former colleague I hadn’t seen in a while. Too long, really. When I first met him, I was an ignoramus with some ambition. I knew where I wanted to go, but I had no idea how to get there. He took me under his wing and showed me the road. And for a time, we traveled that road together.

I continued down the road after we parted ways, and I still haven’t arrived at that destination, but I’m not sure we ever do. No matter what we accomplish, it’s never enough. We never know enough, see enough, or have enough. The destination always moves. Not that that’s always a bad thing.

We reflected on that, and he shared some wisdom. I’m frustrated. He helped me sort some of that out. Not everyone wants to go along for the ride, it seems. So things change, and sometimes we’re disappointed.

Just as importantly, he brought his new girlfriend along. I was glad to meet her. She’s a nice girl, down to earth, and doesn’t take herself too seriously. She can take a lot of good-natured ribbing, and she’s not afraid to dish it out either. She came across as being more than just pleasant to be around–she was fun to be around.

At one point in the conversation, he started talking about “his girlfriend” as if she wasn’t there, describing her, saying what he liked about her. I could tell part of her enjoyed hearing it, but part of her was embarrassed. I was impressed. I’ve done that in the past. The last girl I did that to was too full of herself to be embarrassed. (The embrace I got afterward was pretty cool. Too bad it was worth about as much as the advice that was dished out in these pages yesterday.)

I just smiled knowingly as he went on and on about her. He was doing good. “Stop it,” she said. “You’re embarrassing me.”

“You know her?” he asked.

Bzzt. Wrong answer, Jack.

She let him get by with it. The cool ones always do.

She left the table for a minute and he told me a few things. Things he didn’t want her to know, at least not yet. I’ve forgotten what they were, which is just as well. He mentioned some potential red flags that never rose. Good signs all. I gave him my observations, for what they were worth, based on living for three years with about 30 guys, most of whom had girlfriends, and from other friends’ relationships. He didn’t have anything to learn from my personal experience.

I looked over my shoulder a few times as I was talking. It would have been awkward if she’d returned in the middle of a sentence, potentially. I saw her out of the corner of my eye. I had one last thing to say, and I finished it as she was sitting back down at the table:

“…and you can see it in their choices of where they go to school, or where they start their careers,” I said.

She sat back down. She didn’t demand to know what we’d been talking about when we were gone. She didn’t ask what that was about. Nothing.

I was severely impressed.

We shifted gears in the conversation a couple of times. She has a brother who’s going to be starting at the University of Missouri, majoring in journalism, soon. I told her I’d answer any questions he had. I told her about a few of my misadventures in my four years there. I had more than a few. The head of my sequence still remembers me, to this day, and not because I was one of his most brilliant students (I got an A in his class, by the skin of my teeth). We tangled bitterly. If duels had been legal, I would have challenged him to one. I never backed down. I wasn’t going to let him intimidate me, no matter who he was. And he was somebody–ultimately, the decision whether I got into the program and could continue my major rested with him. He backed down. He won a battle, definitely. But I won the war.

He’s one of two professors who teach that class. When her brother asks which professor to take, I’ll be torn.

She asked if he could call me. I said certainly. Actually she asked me for my phone number.

“I see,” my friend said. “I take you out to dinner with one of my friends, and the next thing I know, you’re getting his phone number.”

She had trouble finding a pen. “And now you’re going to ask me for my pen so you can write down his phone number,” he said.

She found her pen. I told her my number. I look forward to talking about journalism with her brother.

I don’t know what the future holds for them, and two hours does not a final impression make, but I know most guys settle for a whole lot worse.

Pretentious Pontifications: Meet R. Collins Farquhar IV

Dave Farquhar General , , , , , ,

Hello. David’s taking a day off. I’m sure I need no introduction. I am R. Collins Farquhar IV. After writing all the good parts of David’s book and not getting any credit whatsoever, I’ve spent the last couple of years working as a playwright, trying to follow in the footsteps of my slightly more famous ancestor, George Farquhar. It went OK. My ideal job, though, would allow me to sit on the floor all day and pontificate, and people, wowed by my vast intellect, would pay me.
I’m still waiting for the phone to ring. Something is very wrong with this world.

But a good friend did pass me an invitation last night. He’s a French nobleman, the closest thing I’ve found to being worthy of my company. His name is something along the lines of Jacques Luc Pepe “Ham’n’Cheese” Croissant Crepe de Raunche. He’s not quite worthy of my company, which is why I never bother to remember his proper name completely. He gets annoyed when I just call him Raunche. He gets even more annoyed when I call him Steve.

Raunche invited me to the new home he just finished building. “Will you be joining me for cigars and old cognac tonight?” he wrote me. “But of course,” I wrote back. And I offered to provide the music. In typical French fashion, he declined. Rudely.

I was going to fly in my private jet, but Raunche is in the habit of letting his dogs roam free on it. I didn’t want to dirty up my plane, so I drove. Well, actually, I was driven. I couldn’t help but notice he lives off a road called Bentley Park. It’s very appropriate, what with a Bentley being a car for a man who can’t quite handle a Rolls. I told him that upon my arrival, after he greeted me in a gruff voice.

He said he’s already got one.

Vivaldi was playing in the background. How cliche. I told him that too. He said something about taunting me a second time.

I’m still wondering if I went to the right place, because there were no cigars and no old cognac. No new cognac either, for that matter. All he had was Girl Scout cookies and chocolate soy milk. And Vivaldi. He didn’t even have the decency to play it on a tube receiver. It’s impossible to hear music the way it was meant to be heard on transistor equipment. But he insisted on playing it on — get this — a COMPUTER.

Was I wondering whether I went to the right house? Strike that thought. Playing Vivaldi on a computer is just like Raunche. He’s always more interested in trying to show off his computer skills than he is in doing things right.

So we sat around and talked about what he needed for his firewall. David fancies himself the computer expert in the family, but his intellect is no match for mine. He can’t possibly know as much as I know. He doesn’t even know as much as Raunche. So Raunche and I laid out some plans, and I tried not to think about David being out and about, doing middle-class things:

Intel D850MV motherboard (dual processor)
(2) 2.2 GHz Intel Pentium 4 CPUs
4 GB RDRAM
Adaptec 39160 dual-channel Ultra160 SCSI controller
(2) Seagate Cheetah X15 36LP 36-GB hard drives
Pioneer DVD-305S SCSI DVD-ROM drive
1 Quantum DLT 8000 40/80 GB tape drive
Asus V8200 GeForce3 video card
Intel Pro/1000 XT Gigabit Ethernet adapter
Microsoft humpback keyboard
5-button Microsoft Intellimouse Explorer optical mouse

Raunche and I argued about the specs for a long time. I wanted Fibre Channel hard drives, but Raunche didn’t like that idea. Finally I relented. This isn’t going to be a serious computer, after all. It’s just going to be a firewall and a router. Raunche asked about GeForce4 cards, but they’re still a little bit hard to find. I wouldn’t put anything less than a GeForce3 in a server-class machine, but I’m not too interested in waiting for a GeForce4. People say we never get anything done and just sit around pontificating too much already.

Raunche said the board would only take 2 GB of memory, but that’s nonsense. I read somewhere recently that Linux will run in as little as 4 MB of memory. Obviously that was a typo and they meant to say GB. So if Linux requires a minimum of 4 GB of memory, we should get 4 GB of memory. Obviously if we build a computer so that it will run Linux well, it will also run Windows well. That’s just common sense. Still, computer hardware has gotten so cheap, he’ll be able to build himself a nice simple little firewall for around $10,000.

I really wish Intel would go back to making memory and high-end video chipsets and cards, and I wish they would get into the SCSI controller business. There are two hardware companies I trust: Intel and Microsoft. Raunche agrees.

With our plans laid out, Raunche bid me adieu late in the night. I’d have liked to have stayed and debated longer, but the upper crust need their sleep.

As I left, I thought it was rather nice of me to drive in rather than flying in. That way I wouldn’t awaken his neighbors by taking off in a jet late at night. Not that they care, I’m sure. One must make provisions to live in such close proximity to the upper crust.

In fact, I’m sure some of the neighbors were disappointed not to get the chance to see my plane. I’ll have to get on to Raunche about having his runway cleaned.

Adventure in SCSI

Dave Farquhar General ,

Gatermann called me last night. He’d gotten his new Adaptec 19160, but Windows 2000 wouldn’t recognize it. Unfortunately, he’d reformatted his main drive too, so there was no going back and cheating by installing both his old and new SCSI cards side by side, then installing the driver, then pulling the old card and moving the drive.
We tried a couple of things over the phone. No go. I suggested he try installing Linux just to make sure the card was good.

By the time I arrived, he had a working Red Hat 7.2 configuration. Put that in your pipe and smoke it, Microsoft.

We downloaded the latest Adaptec PCI drivers, using his other Linux box. Windows 2000 didn’t like them. We downloaded the previous version. That one, unlike the other, had a dedicated Adaptec 19160 driver. We installed that and it actually worked.

Forty minutes later, we had a working all-SCSI Windows configuration.

I like Linux more and more every day.

How to build a reliable PC.

Dave Farquhar General , , , ,

We touched on the topic of reliability last week. I figure I might as well give a more thorough discussion of what makes a PC reliable.
1. Power supply. I see more power supply failures than any other single component. Good power supplies fail without a whimper and don’t damage the rest of your equipment. Bad power supplies take other stuff with ’em when they die. Antec and Sparkle are examples of good basic power supplies. The power supplies that come in InWin and other brand-name cases tend to be fine as well. A notch above that is Enermax, maker of the ultimate in show-off power supplies, with plated finger guards and odd colors. Top-tier is PC Power and Cooling. If I wanted to build a computer and have absolute assurance it would still work in five years, I’d start with a PCP&C or at the very least, an Enermax.

Buy more wattage than you think you need. The power supply will run cooler and last longer if you do. Besides, you never know what you’ll want to stick in the case down the road.

2. Memory. Last time I checked, you could get 64-meg PC133 sticks for under $5. I wouldn’t trust ’em with my archenemy’s work though. Cheap memory may be untested, the PCB may not be a good design, or even worse, it may have chips that were tested and deemed unsuitable for use in PCs (but fine in other less-demanding devices). Unscrupulous makers sometimes buy up these chips and take their chances. It may seem foolhardy to pay $100 for a 256-meg stick from Crucial, but I haven’t just heard horror stories about commodity memory. I’ve seen it with my own eyes. I’ve had more than 1,000 brand-name modules cross my desk. Three were defective. I’ve had fewer than 50 commodity modules cross my desk. More than half proved defective. Some wouldn’t even work–the system would just beep at you. The worse ones appeared to work for a while, but the system was always crashing. Don’t take chances on your memory. I tend to buy my memory over-spec as well. Even if a motherboard takes PC100 memory, I go ahead and buy PC133 CAS2 memory. The chips will run just fine at a lower speed, so I have an overengineered system for a while, and if I ever upgrade I’m more likely to be able to take the memory with me.

3. Motherboards. Buy brand-name boards. I’ve never had an Asus board fail. (Watch one fail next week now that I’ve said that. But I’m happy with the reliability and longevity of Asus boards.) I’ve done well with other brands too, like AOpen, Abit, FIC, and Tyan. I know MSI boards are popular but I don’t have any personal experience with them. Asus has impressed me with their farsighted engineering–in my experience, you’re more likely to be able to upgrade an Asus board in three or four years than others.

Most people know to check the hardware enthusiast sites when researching a board. I urge you to also check the Usenet newsgroups. You’ll find some good advice. Finding very little on a board can be a good sign too-it’s an indication that a board doesn’t have many problems. Years ago, I was researching the Asus SP97V motherboard, because it was dirt cheap, but it was an Asus. I searched on Usenet and found very little about it–maybe a half-dozen messages. Most of it was just idle chatter. One message was talking about various boards, including the offhanded comment, “The SP97V is a good board for the money, BTW. I’ve used three of them.” That clinched it. Nobody was talking bad about the thing. I had one positive, and very little talk overall, which generally indicates satisfaction. Satisfied people rarely talk about stuff unless its quality blows them away.

4. CPU fans. Never go cheap on CPU fans. There’s a humongous roundup of currently available fans. Get a heavy-duty fan, even if you don’t overclock. Remember, the CPU you’re protecting is a lot more valuable than the fan. A good fan will keep your CPU well within its specified operating temperature range, and I’d like to think that the pricier fans will have a longer life. Get a ball-bearing fan rather than a sleeve-bearing fan; a cheap sleeve-bearing fan is quieter but it’s also likely to conk out on you in a couple of years if you leave your systems on 24/7.

Bookmark that site, by the way. Dan’s one of the better technology writers out there today, and he doesn’t take himself too seriously. He’s an entertaining read, explains things well, knows what he’s doing (and he’s pretty open about his methodology), and he’s probably a certifiable genius, but he’s not pretentious. In fact, he seems to enjoy making people think he’s not quite sane. I make sure I pay that site a visit at least twice a week.

5. Case fans. It’s a good idea to put a supplemental fan in the machine. Two is usually overkill unless you’ve got some really hot hard drives, and it’ll make your computer louder. You can quiet them by manipulating the voltage. Dan’s Data talks a lot about them too, including how to slow them down. For typical users, a simple ball-bearing case fan is sufficient.

6. Hard drives. IBM currently recommends you not run their drives more than 8 hours a day. So that eliminates IBM from the running. That’s a shame, because they used to make spectacular drives. (I still like their laptop drives better than any others I’ve seen though, and I’m not the only one.) I’ve seen fewer dead Quantum and Maxtor drives than any other brand, although Samsung really has surprised me with their reliability, and the drives are cheap. Seagate has a good reputation but I have very limited experience with their recent drives. Maxtor’s a safe choice at the mid range and high end, while Samsung is tough to beat for the low end.

7. Cabling. The cables that come with brand-name PC motherboards seem to be of good quality, as are the cables I’ve seen bundled in Maxtor retail kits. If an IDE cable looks flimsy, don’t buy it. Problematic cables slow you down due to the need to retransmit data. Also never buy an IDE cable that’s longer than 18 inches. Longer cables are available, but IDE specs state 18 inches as the maximum. Longer cables may work, but it’s questionable. If you have to reach the top bays in a tall tower case, you’ll have to go SCSI. Sorry.

Rounded cables will improve airflow, but be careful. Rounding shortens cables, so the wires inside a long rounded cable are even longer than stated. While a relatively new practice on the desktop, I saw rounded SCSI cables in IBM servers and workstations as long ago as 1995.

Linux Performance Tuning

Dave Farquhar General , , , , ,

I found a very superficial Linux Journal article on performance tuning linked from LinuxToday this week. I read the article because I’m a performance junkie and I hoped to maybe find something I hadn’t heard before.
The article recommended a kernel recompile, which many people don’t consider critical anymore. It’s still something I do, especially on laptops, since a kernel tuned to a machine’s particular hardware boots up faster–often much faster. While the memory you save by compiling your own kernel isn’t huge and was much more critical back when a typical computer had 8 MB of RAM, since Linux’s memory management is good, I like to give it as much to work with as possible. Plus, I’m of the belief that a simple system is a more secure system. The probability of a remote root exploit through the parallel port driver is so low as to be laughable, but when my boss’ boss’ boss walks into my cube and asks me if I’ve closed all possible doors that are practical to close, I want to be able to look him in the eye and say yes.

The same goes for virtual consoles. If a system runs X most of the time, it doesn’t need more than about three consoles. A server needs at most three consoles, since the only time the sysadmin will be sitting at the keyboard is likely to be during setup. The memory savings isn’t always substantial, depending on what version of getty the system is running. But since Linux manages available memory well, why not give it everything you can to work with?

The best advice the article gave was to look at alternative window managers besides the ubiquitous KDE and Gnome. I’ve found the best thing I’ve ever done from a performance standpoint was to switch to IceWM. KDE and Gnome binaries will still run as long as the libraries are present. But since KDE and Gnome seem to suffer from the same feature bloat that have turned Windows XP and Mac OS X into slow pigs, using another window manager speeds things along nicely, even on high-powered machines.

I take issue with one piece of advice in the article. Partitioning, when done well, reduces fragmentation, improves reliability, and allows you to tune each filesystem for its specific needs. For example, if you had a separate partition for /usr or /bin, which hold executable files, large block sizes (the equivalent of cluster sizes in Windows) will improve performance. But for /home, you’ll want small block sizes for efficiency.

The problem is that kernel I/O is done sequentially. If a task requires reading from /usr, then /home, then back to /usr, the disk will move around a lot. A SCSI disk will reorder the requests and execute them in optimal order, but an IDE disk will not. So partitioning IDE disks can actually slow things down. So generally with an IDE disk, I’ll make the first partition a small /boot partition so I’m guaranteed not to have BIOS issues with booting. This partition can be as small as 5 megs since it only has to hold a kernel and configuration files. I usually make it 20 so I can hold several kernels. I can pay for 20 megs of disk space these days with the change under my couch cushions. Next, I’ll make a swap partition. Size varies; Linus Torvalds himself uses a gig. For people who don’t spend the bulk of their time in software development, 256-512 megs should be plenty. Then I make one big root partition out of the rest.

With a multi-drive system, /home should be on a separate disk from the rest. That way, if a drive fails, you’ve halved your recovery time because you’ll either only have to install the OS on a replacement drive, or restore your data from backups on a replacement drive. Ideally, swap should be on a separate disk from the binaries (it can be on the same disk as /home unless you deal with huge data files). The reason should be obvious: If the system is going to use swap, it will probably be while it’s loading binaries.

Still, I’m very glad I read this article. Buried in the comments for this article, I found a gem of a link I’ve never seen referenced anywhere else before: Linux Performance Tuning. This site attempts to gather all the important information about tuning Linux to specific tasks. The pros know a lot of this stuff, but this is the first time I’ve seen this much information gathered in one place. If you build Linux servers, bookmark that page. You’ll find yourself referring back to it frequently. Contributors to the site include kernel hackers Rik van Riel and Dave Jones.

The penguins are coming!

Dave Farquhar Linux , , , , , , ,

The penguins are coming! Word came down from the corner office (the really big corner office) that he wants us to get really serious about Linux. He sees Linux as a cheap and reliable solution to some of the problems some outside clients are having. This is good. Really good.
My boss asked if it would be a capable answer to our needs, namely, for ISP-style e-mail and for Web caching. But of course. Then he asked if I was interested in pursuing it. Now that’s a silly question.

Now it could be that FreeBSD would be even better, but I know Linux. I don’t know FreeBSD all that well. I’ve installed it once and I was able to find my way around it, but I can fix Linux much more quickly. The two of us who are likely to be asked to administer this stuff both have much more Linux experience than we have BSD experience. Plus you can buy Linux support; I don’t know if you can buy FreeBSD support. I doubt we will, but in my experience, clients want to know (or at least think) that some big company is standing behind us. They’re more comfortable if we can buy support from IBM.

So maybe my days of Linux being a skunkworks project are over. The skunkworks Linux boxes were really cleverly disguised too–they were Macintoshes. They’re still useful for something I’m sure. I expect I’ll draft one of them for proof-of-concept duty, which will save us from having to pull a Compaq server from other duty.

I spent a good portion of the day installing Debian 3.0 on an old Micron Trek 2 laptop. It’s a Pentium II-300 with 64 megs of RAM. It boots fast, but current pigware apps tend to chew up the available memory pretty fast. I recompiled the kernel for the hardware actually in the machine and it helped some. It’s definitely useful for learning Linux, which is its intended use.

I’ve noticed a lot of people interested in Linux lately. One of our NT admins has been browsing my bookshelf, asking about books, and he borrowed one the other day. Our other NT admin wants to borrow it when he’s done with it. The Trek 2 I installed today is for our senior VMS admin, who wants a machine to learn with. My boss, who’s been experimenting with Linux for a couple of years, has been pushing it aggressively of late.

I don’t know if this situation is unique, but it means something.

—

I spent a good part of the evening at the batting cages. I messed my timing up something fierce. I hit the first few pitches to the opposite field, some of them weakly, but soon I was hitting everything–and I mean everything–to the third-base side. So my bat speed came back pretty fast, and I was getting way out in front of a lot of the pitches. So I started waiting on the ball longer, hoping to start hitting the ball where it’s pitched. The end result was missing about a quarter of the time, slashing it foul to the third-base side a quarter of the time, hitting it weakly where it was pitched a quarter of the time, and hitting it solidly where it was pitched a quarter of the time. Good thing the season doesn’t start until June–I’ve got some work to do.

Afterward, I drove to my old high school, hoping to be able to run a lap or two around the track. I was hoping for two; realistically I knew I’d probably be doing well to manage one. There was something going on there, and I couldn’t tell if the track was in use or not, so I kept driving. Eventually I ended up at a park near my apartment. I parked my car, found a bit of straightaway, and ran back and forth until I was winded. It didn’t take long.

I can still run about as fast as I could when I was a teenager, but my endurance is gone. I’m hoping I can pick that back up a little bit. I was a catcher last season, filling in occasionally at first base and in left field. In the league I play in, we usually play girls at second and third base, and we’ve got a couple of guys who can really play shortstop, so I’ll probably never play short. When I was young I played mostly left field and second. I’d like to roam left field again. Not that I mind catching, but there’s a certain nostalgia about going back to my old position.