Need a cheap NAS? Grab this floppy and an old Pentium and you’ve got it

I wanted to build a small-as-possible Linux for the purpose of creating a lightweight NAS a few years back. I even downloaded the uclibc development tools and started compiling for the purpose of doing it. Then I got distracted.

I guess it doesn’t matter. I think NASLite had beaten me to the punch anyway.Here’s how it works. You download the appropriate floppy for the network type (SMB for Windows networks, NFS for Unix) and network card you have. You find an old PC. As long as it has PCI slots, it’ll work. Drop in the NIC if there isn’t one there already, and then drop in as many as four IDE hard drives. (The disk will reformat the drives if there’s anything there, so make sure they’re new or scratch drives beforehand.) If the BIOS doesn’t support the drives because they’re too big, disable them in the BIOS. Don’t worry, Linux controls the drives directly so you don’t need the BIOS. Boot off the floppy, and it joins the network and you’ve got a bunch of disk space for the cost of the drives and possibly the NIC.

Nice, huh?

This isn’t suitable for use in most corporate environments since it creates wide-open storage (it might work well as a big file dump, so long as people realize there’s no security there, but I’ve learned the hard way that users tend not to listen, or at least not remember, when they’re told such things). For home networks it’s fine, unless you’ve got wireless, in which case anyone who can get into your wireless network would also be able to get to your NAS.

Even then, it’s useful if what you want is a central repository for programs like Irfanview and Mozilla Firefox that you install on all your PCs and want to keep handy.

At any rate, if you’re creative and careful and have a Linux box and know how to use the dd command (or have a fairly up-to-date copy of WinImage) to copy a 1.72-meg disk image to a floppy, this is a useful tool for you.

Coming back

The phone rang this morning, around 9 AM. I’ve gotten used to that; my recruiter’s been calling me around 9 for the last few days. But this time there was a different tone to his voice. He was nervous.

Great, I instantly thought. Another rejection. What is this, high school?But I let him finish, because he said he had some good news. "Dave, they’re excited about you. But there’s a problem. Do you think there’s any way you can start tomorrow?"

Tomorrow. He’d told me yesterday he thought they’d probably be interested in me, and that we’d be preparing for a start day of July 5. Being able to start tomorrow was about the last thing I expected.

I wasn’t the least bit prepared, but in reality, what did I have planned for tomorrow? A trip to the post office, certainly. A trip to a thrift store or two, most likely. Maybe I’d get ambitious and change the oil in my wife’s car, and maybe I wouldn’t. So I’d make $7, maybe $15, and I’d save another $20.

I figure that every day I didn’t work cost me between $150 and $200 (pre-tax). So you do the math. I told him I’ll start tomorrow.

Actually this was a longshot if there ever was one. The job position involves Unix administration. I’m not a stranger to Unix, but it’s been a year since I’ve done any Unix on a regular basis. I pulled out all the stops on the job interview, showing up in a suit and tie on a 90-plus degree day on just a couple of hours’ notice. It was all downhill from there. The entire department of five interviewed me, plus one guy who’d been recently promoted out of it. They peppered me with Unix and e-mail questions. One of them asked me why to never type "rm -rf /" and I asked him whether the "r" was uppercase or lowercase. Apparently in Solaris it doesn’t matter. It does in every Linux distribution I know. But I got the rest of the question right. I struck out on the others, sometimes badly.

I left the building with a little more than a thank-you for my time from the supervisor. I made a note to myself to make sure my recruiter briefed me better on what the responsibilities would be, and to get me enough time to actually brush up so I’d look like I know something, and not some idiot off the street who can barely spell "Unix."

Then they started interviewing other people. And with each passing interview, my recruiter felt more hopeful. I started to feel hopeful too. I didn’t count on anything–my wife and I all but started a business last week, and we’re profitable. It won’t pay the mortgage, let alone make us rich, but we made more than enough to pay the electric bill, and we did it on our terms.

And then the phone call came. A few hours later I drove 10 miles, signed some papers, and it was official. I’m a professional Unix administrator.

Microsoft buys and then discontinues Linux/Unix antivirus products

First GeCAD, now Sybari.

Microsoft has been buying smaller anti-virus firms and discontinuing their Linux and Unix product lines.

Trust, schmust. When your god is Big Business, that means Big Business can do no wrong, so when you’re the U.S. government, you let companies like Microsoft do whatever they want. The problem is that Unix antivirus products are extremely useful, especially in Microsoft shops. Unix viruses are rare, and the heterogenous nature of Unix–never knowing much about the underlying hardware, binary incompatibilities between various dialects even when running on the same hardware, and never knowing for certain which libraries are installed–creates a hostile environment for viruses anyway.

So what good is a Unix server that detects viruses that can’t survive in Unix anyway? It makes a great buffer between the hostile world and the soft and chewy Windows boxes inside corporate firewalls, that’s what.

I love to put Unix boxes in between the world and mail servers that may be running Windows. Just set it up to relay mail to your Exchange or Domino server, but have it scan the mail first. Better yet, have it running on weird hardware. A slightly elderly Macintosh or Alpha or Sun box works great. Since the Intel x86 instruction set is the most common, most buffer overflows use it. While non-x86 processors aren’t immune to buffer overflows, an overflow using x86 instructions will appear to be gibberish and it won’t run. It’s like telling me a lie in Japanese. You won’t fool me with the lie, because I don’t speak Japanese, so I won’t understand a word you’re saying.

Fortunately, there are still antivirus products for Unix and Linux out there. And once Microsoft establishes its antivirus product, it will be more difficult–I hope–for it to simply continue buying antivirus firms and discontinue their products, since now they would be buying off competitors, rather than just attempting to acquire technology that they don’t have the ability to develop internally.

And even if they do buy and discontinue everything, there’s always ClamAV.

A User Friendly waiting to happen

Your new customer service manager’s name is Dev Null. Please refer all further communication to Dev Null, who will handle your matter speedily and appropriately.

Or something like that.It sounds just believable enough that lots of people will fall for it. The problem is getting anyone with Unix familiarity to keep a straight face while saying it.

Coincidentally, BOFH fans will also know that /dev/null is an incredibly fast backup device.

A Linux-based GPL\’ed disk partition table recovery program

It seems like I’m recommending the program MBRwork to someone at least once a month. I recommended it two or three times just last week. But there are a couple of things I don’t like about it. One, it’s DOS. Creating DOS boot floppies isn’t as easy as it used to be. And two, it’s proprietary, so it could theoretically disappear any minute.

But similar tools exist for Linux.The most highly regarded is gpart (guess partition), which just happens to be included on the BG-Rescue Linux two-floppy rescue system. Download BG-Rescue Linux and burn the ISO image to a CD, or download the two-floppy version and write it to two floppies, and keep it in your toolbox. Or, of course, they’re on Knoppix.

When a partition table vanishes, or, a more likely scenario, a system quits booting mysteriously, you can boot BG-Rescue Linux and run gpart. You can also check FAT/FAT32 filesystems with dosfsck and NTFS partitions with ntfsfix.

Need to undelete some files in an emergency? You can even undelete files from NTFS partitions with ntfsundelete.

Clearly, skills with a handful of Unix utilities are very useful even in a strictly Windows shop.

Looks like I should explore these tools a bit more in-depth this week.

What pop singer is your OS?

Using Unix is the computing equivalent of listening only to music by David Cassidy.
–Unix pioneer (and Plan 9 co-creator) Rob Pike on Slashdot

Ah, the questions that inspires…If Unix is David Cassidy, then what’s Windows?

I nominate Britney Spears. She and her management can’t decide what her name is, she’s tempermental, unstable, lacks talent… You can have a heyday with that analogy.

Is Mac OS the Grateful Dead? Hmm…. There’s not only that “Flower Power” Imac, there’s also that cult following…

Amiga OS must be the Velvet Underground. Ahead of its time, obscure but not so obscure that nobody has heard of it, influenced virtually everything that came after it, and 20 years later, lots of things still haven’t completely caught up…

SCO obviously wants us to think Linux is Milli Vanilli.

So which OS has to be New Kids on the Block? Vanilla Ice? MC Hammer? David Hasselhof?

Any Unix gurus care to help me with mod_rewrite?

I’ve watched my search engine traffic decrease steadily for the past few months since I changed blogging software. It seems most engines don’t care much for the super-long arguments this software passes in its URLs.

The solution is mod_rewrite, and I think my syntax looks correct, but it’s not working for me.The goal is to fake out search engines to make them think they’re looking at static files. Search engines are reluctant to index database-driven sites for fear of overloading the site. Since I can’t tell them not to worry about it, I have to make the site look like a static site.

To that end, I created a section at the end of my httpd.conf file:

# rewrites for GL

RewriteEngine on
RewriteRule ^/article/([0-9]+)$ /article.php?id=$1 [NC,L]

This line should make the software respond to Thursday’s entry (https://dfarq.homeip.net/article.php?story=20040902200759738) if it’s addressed as https://dfarq.homeip.net/article/20040902200759738.

Once mod_rewrite is working, in theory I can modify the software to generate its links using that format and watch the search engines take more of a liking to me again. But I’ve got to get mod_rewrite going first, and I’m stumped.

Any expert advice out there?

Thanks in advance.

The big question: PC or Mac?

I haven’t stirred the pot in a while, so to prove that I am a professional writer after all, I’ll go tackle the most inflammatory question I can imagine, something that makes Bush vs. Kerry look like a game of paddy-cake.

What’s the better computer, a PC or a Macintosh?OS X closely follows the history of the first Macintosh in that the first version showed lots of promise, but had lots of problems, probably shipped too soon, and lacked some important capabilities. But Apple, to its credit, washed its dirty laundry in public, fixing the problems and adding capabilities. And now, OS X has a reputation as something that “just works.” And it has something to back it up with.

Windows XP, well, that joke about 32-bit extensions to a 16-bit graphical interface on top of an 8-bit operating system originally written for 4-bit computers by a 2-bit corporation that can’t stand 1 bit of competition is almost true. Microsoft bought the 8-bit OS from a company that may have stolen it. And while Gary Kildall‘s first operating system was 4-bit, he may have written CP/M from scratch. But I digress.

Unlike Apple, Windows XP tries really hard for backward compatibility. And for all the stink about the things SP2 breaks, I’ll bet you a dollar you can go download the 1981 edition of VisiCalc for MS-DOS and it’ll run just as well on your three-point-whatever gig Pentium 4 running XP as it did on the first IBM PC. And if you can find old copies of WordStar and dBASE II and Turbo Pascal, chances are they’ll run too. Old programs that break are at least as likely to break because of timing problems with CPUs that are almost a thousand times faster than they expect as they are because of Windows. Probably more.

Sure, you’ll find programs that break, but you’ll probably find a thousand that work for every one that breaks. Especially if you limit yourself to titles that aren’t games.

This is a blessing and a curse. The blessing is that software you bought almost a quarter century ago still runs if you need it. If you think that isn’t important, I’ll introduce you to one of my clients who’s still using dBASE II. It sure is important to him. The curse is all that spaghetti code you need to keep those billions and billions of old programs running.

I have a little bit more sympathy for Microsoft when I remember that Windows XP is really OS/2 1.3 with DOS bolted on, and Windows 3.1 and 98 bolted on next door.

Just a little.

When you look at it that way, is it any wonder that sometimes when you plug in your digital camera it acts goofy?

But truth be told, more often than not, your mouse and your digital camera and all your other stuff works, whether you plug it into a Windows box or a Mac. And when it doesn’t work, it’s every bit as infuriating on a Mac as it is on a Windows PC. When Windows has an error code, it spits one out in hexadecimal. The Mac spits out an error code in decimal. I guess that makes the Mac friendlier.

But I guess it doesn’t matter whether I say “deleterious” in English or in Pig Latin. It’s still not going to be a word you’re likely to have heard today, either way. And there’s a decent chance it’ll send you reaching for a dictionary (or Google).

I’ll be frank: I hated OS 9 and OS 8 and everything else that came before it. I tried to get the Mac Toss turned into an official olympic sport. If there are any old Macintoshes in the pond in front of the office building where I used to fix Macintoshes, I know nothing about them.

But Apple knew it was b0rken and threw it away and bought something better. I still think they bought the wrong something better and would have gotten here a lot sooner if they’d bought BeOS, but they bought NeXT and got Steve Jobs back, so here they are.

All things being equal, I’d go with a Mac, if only because it’s got a Unix layer underneath it.

But all things aren’t equal. Macintoshes cost a lot of money. And when you’re 2 percent of the market, you don’t have a lot of software to choose from. I know. I had long love affairs with Amiga and with OS/2 before I threw in the towel and installed Windows. And it wasn’t until 1997 that I actually used Windows as my everyday OS.

When someone hands me a disk, I can read it. When someone tells me I’ve gotta try out this new program, it runs.

On the other hand, there’s virtually no problem with viruses and spyware on the Macintosh. If I want to spy on people or cause enough damage to make the front page of USA Today, I’m going to set my sights on 90+% of the market instead of the Macintosh’s 2%. Being a minority can have its advantages.

But, after living for years with good computers and operating systems that were years or even decades ahead of their time but had no software availability, I run Windows most of the time and exercise caution to keep my system clean. I don’t use Internet Explorer, I keep my virus definitions up to date, I don’t read e-mail from strangers and don’t open unexpected attachments, and I don’t install freeware software unless it’s open source.

And guess what? I don’t have any problems with my computer either.

I know and respect other people who’ve gone the other way. For me, there never was much choice other than PC hardware. I can afford a Macintosh, but that’s money I really need to be putting towards paying off my car and my house sooner, or saving for retirement. Or any number of other things. I’m a legendary tightwad.

Other people may have had their own other reasons for making the same decision.

Go get ’em, SCO!

I’m sure you’ve read it 4.3 billion other places already, but Microsoft has been granted a patent on double-clicking.

Well, there’s something you probably have only read a few hundred other places. Apple obviously had people double-clicking more than a year before Microsoft did, seeing as Windows 1.0 was released in November 1985 and the first Macintosh shipped in early 1984. Commodore had Amigans double-clicking by the summer of 1985. So did Atari.

Guess who supplied Atari with its operating system, since Jack Tramiel failed to swindle his way into ownership of the Amiga?

Digital Research, that’s who. DR provided Atari with a version of CP/M-68K, with its GEM GUI running on top of it. Atari marketed the bundle as TOS, for Tramiel OS.

Digital Research got crushed by the Microsoft juggernaut a few years later and eventually sold out to Novell. Novell then attempted to compete head-on with Microsoft (buying up its Utah neighbor, WordPerfect, and part of Borland in the process) and failed spectacularly. Smelling a rat–Novell believed Microsoft sabotaged some of its applications so they would not run under DR-DOS–it then pawned the Digital Research portfolio off on Caldera, a Linux company run by former Novell executives. The catch? Caldera had to turn around and sue Microsoft. Which they did, successfully.

A few more years later, The Santa Cruz Operation, a small Unix firm, wanted out. It sold its Unix-on-Intel business, as well as the rights to the old AT&T Unix (purchased from Novell, ironically) to Caldera, who soon changed its name to The SCO Group to reflect this business.

Yes, this is the same SCO who is now on a legal rampage, suing anything that moves.

Now, whether Novell or SCO is the more rightful owner of the double-click “innovation” is arguable. But such matters never seem to matter to SCO. It’s a frivolous lawsuit, but Darl McBride and Co. have made frivolous and baseless lawsuits into an art form.

Go get ’em, Darl.

Well, I’m a Slowlaris administrator now

Let me run down <strike>my list of qualifications</strike> what I know about Solaris.1. They call it "Slowlaris" because it initially wasn’t as fast on the same hardware as its predecessor, SunOS.
2. I don’t know if Slowlaris 9 is faster than older versions of Slowlaris, so I don’t know if this counts as something I know about it.
3. Slowlaris is based on System V Unix. SunOS was based on BSD.
4. Slowlaris runs primarily on proprietary hardware from Sun, based on a CPU architecture called SPARC. A handful of Sun clones exist, but I think Fujitsu is the only big third-party manufacturer.
5. There is an x86 version of Slowlaris. Sun keeps going back and forth on whether to continue making it or not, since they don’t make much money off it. It’s being made now. Professional Slowlaris admins argue that its availability makes it easier for up-and-coming admins to learn the OS without buying expensive Sun hardware–they can run it on their six-month old computer that’s too slow to run Doom 3.
6. "Sun" was originally an acronym for "Stanford University Network."

So most of what I know about Slowlaris is either trivia, or holdover generic Unix know-how. But I told my boss since it’s System V, I should be able to adjust to it almost as easily as I could adjust to a Linux distribution from someone other than Debian. I’ll just be typing –help and grepping around in /etc even more than usual.

Yep, it’s been that kind of <strike>week</strike> month.