Diary of a Network Geek

There’s a whole series of these.
TechRepublic has a whole series of these Ten Things You Should Know articles. I’ll post several over the coming weeks and months. Why? Because I like them and they’re a “no brainer” for content on this site. I’m all about easy content!
Anyway, this time it’s Ten Things You Should Know About the BASH Shell. There are a bunch of short-cuts here. Everything from running processes in the background (try that with a command prompt in Windows!) to doing calculations right there on the command line. Now, this might not be all that great for everyone, but, for a command-line junky like me, it’s pure gold. Also, if you’re running Mac OS X, you might check it out. These should all work on your command line, too, if you can find it amongst all those pretty graphics.
Don’t ignore the power of the command line!

Well, no kidding!
When I read this article on the Register about Novell using the upcoming, and potentially bug-filled, launch of “Longhorn” Microsoft’s newest Windows operating system as an opportunity to get their Linux desktop into corporate America, my thought was, “Well, DUH!” What else does this reporter think they’ve been doing?! I mean, c’mon, buddy, this isn’t exactlly a secret, you know? Novell has been talking about this for years. Though, I have to admit, this time I think they have a better strategy, and opportunity, than that “genius” idea to buy WordPerfect. Hey, I love WordPerfect, don’t get me wrong, but there’s just no way that suite of software was going to really compete with MS Office.
Of course, I think they’re being a little optimistic, but, hey, Jack’s heart is in the right place. Hopefully, though, this will keep them alive in the market for a couple more years.
Now, iff they can just hold out until I retire…

They’ve been waiting for me.
I can tell that the folks at my company have been waiting for a guy like me to show up. Today, I had three different persona PCs from three different employees in my cube. Mind, I mean three machines that they brought from home to have me look at for them, not machines from the office. Mostly, they just needed to be defragged and have their anti-virus files updated, but, c’mon, three? Obviously, these people have just been waiting for a “real” computer person to show up so that they can get me to do basic maintenance for them. Actually, come to think of it, I need to update my anti-virus signatures myself!
But, that doesn’t mean I have any less work that’s work related, either. Just this morning I was setting up a PC for yet another person from New Orleans. Which is a good thing, I guess, when you consider some of the alternatives. Of course, it would have been nice if they hadn’t promised that same cube to two different people without telling anyone. I was about to try and move his e-mail from the Windows 2000 machine he had in the office to his G4 Powerbook, but then we decided to take a “wait-and-see” stance instead. With all the miscommunication flying back and forth, we thought that was better. The chaos from Katrina has everyone sort of “runnin’ and gunnin'”, if you take my meaning, and that makes things extra challenging sometimes.
So, with all this craziness going on at the office, I find myself asking, “Should I be doing all this for people?” I mean, it’s not really my job, but the folks asking me to do this for them are the top-level managers. Should I be telling them “no”? I’d really rather not do that, since everyone seems to like me and the work I do for them. Granted, I’m not sure that most of them have any idea what I actually do on a day-to-day basis, but still, they seem pleased, so I’d rather not rock the boat.
Oh, and in recent updates, I did finally manage to get the satellite phone working, but now, since it took so long, we’re trying to return one. Not sure if we can do that at this point, but we’re trying. And, I’ve been messing around with all kinds of Windows 2000, NT and XP issues on the network. Getting all the folks from both offices working has been a bit of a challenge. In fact, if not for the DMZ port on my firewall, I’m not sure I could have had the two domains working together, since they’re named the same. I’m sure that would have caused problems if they’d seen each other on the network.
And, I really should be looking more closely at the version of Linux I want to run on that mythical server that I should be getting spec on. I’m leaning toward either Red Hat or SuSE, possibly even SuSE with all the Novell Open Enterprise Server stuff on it. I have to admit, if I were to get good install media, that could be really cool. All the stability and flexibility of Linux with the way cool administration tools from Novell. Those tools are, after all, what they’re known for developing. It’s the best “value added” product for Linux that I’ve seen so far.
Well, I guess I have some time before we’re really ready to do all that, so, while I wait, I’ll probably just read Sams Teach Yourself UNIX System Administration in 24 Hours, so that my skills are sharp when the time comes. But, now, I’m tired, so I think I’ll just go to bed.

Linux in your car.
Hey, why not? This guy did it and documented it at his website. Again, this might not be everyone’s idea of fun, but I am, after all, a network geek! I love the idea of having a built-in PC so that I could go war driving to the extreme. I mean, that would really redefine war driving, wouldn’t it? To have the PC running off the car, built-in and scanning literally as I drove to or from work would be so cool. Geeky as all get out, but cool to me.
Heck there’s even a book about doing that kind of thing, including the PC, called Geek My Ride. And, yes, I own it already.
God, help me, I am such a geek.

Well, anyway, if you’re feeling secure in your geek-hood, click the link and have some fun this weekend.

This is sort of the long way around, but…
Well, I have a dream. I dream of a single, giant PERL script that does a complete server inventory, no matter what version of operating system it’s running. Why? Look at my resume. Notice how many times I’ve changed jobs? Every time I hit a new gig, I look at their server documentation, if they have any, and ask how old it is. 80% of the time, no one knows how old it is. The rest of the time, it’s so old and out of date as to be totally irrelevant. Of course, no matter the state of their documentation, it always falls to me to create it or update it. Hence my quest for a single, glorious PERL script that checks everything that matters on an individual server and drops it into a report, or at least a text file that I can make into a report.
The biggest stumbling block to my vision of this splendiferous chunk of code has almost always been the first one: figuring out which operating system the target is running. Well, not any more. No, my faithful readers, including my ex-wife and her new meal-ticket, now I give you Step One in Uncle Jim’s Master Plan for Network Domination.
PERL OS Version checker

Well, at least yesterday wasn’t a total waste.

Hmm, this could be fun…
Lately, IBM has been really supportive of Linux. In fact, they have a whole section on their site dedicated to cool things you can accomplish with Linux. The latest of these is an article about how to use Linux to set up a wireless ISP. They suggest setting this up for a neighborhood or office, but I’m sure there are applications far beyond that. They take you through the basics, but, after skimming the article, I sure wouldn’t reccomend this for the Linux neophyte. The article does cover, in brief, all the aspects of this project, including hardware choices, but it focuses on a series of bash scripts written by the author to help you manage your WISP. That’s all well and good, but, of course, limited in scope.
So, why not add all that functionality to a backpack and make yourself a walking “hotspot”. Yeah, that’s not a joke. A guy actually took a backpack with solar panels built into it, added some wireless hardware, and made himself into a roving hotspot.

Now, that’s entertainment! And perfect for a fun, freaky Friday link.

Hmm, I’m wondering who has the real advantage here…
Well, if you read Slashdot, you’ve already seen this story about a Linux guy using wine to update a WGA game successfully. Apparently, he’d been running this game on wine quite well for a while, but it needed some kind of update. So, he used the update feature from within the game, while on Linux running the wine Windows emulator, and he was prompted for his Windows Genuine Advantage code. He put it in and the Microsoft website proceeded to tell him he was running “Genuine Windows” and update his game. So, what was that advantage again?

Oh, and it looks like I’ll be on the road tomorrow, just for the day. Off to Bellechasse, Louisiana to install a couple of desktops. Three, actually, in one day and transfer data and settings on two. It’s going to be a long, long day. At least the boss will be flying me, so I won’t have to hassle with airports! (Don’t worry Diary of a Network Geek junkies! I’ll post something before I leave.)

That’s Novell’s SUSE Linux Enterprise Server 9 for the acronym impaired.
Well, I’m evaluating flavors of Linux to replace our antique Windows NT server, in my copious spare time, at work. Of course, my first choice was to go to Novell’s site and download the free demo of SLES 9. It took the better part of a day and night to download the ISOs and burn them, but, again, I did that in the background.
First of all, the install was quite simple and found even the junky, old hardware that I scrounged together for a test machine. Though, I have to admit that I found it rather annoying that I only used three of the six CDs I burned to do the install. And, I only used the third of those because I was installing a SAMBA server to minimize my client-side changes. (Yes, I know to block all SAMBA traffic out to the ‘net. Thanks for worrying about me though.) If I get the time, I’ll go back and try to figure out what was on those last three disks. I figure it was documenation and source-code, mainly, but that’s only a slightly educated guess.
Now, I’ve never actually used SUSE before, so it was a little new to me. Bascially, it’s standard Linux and X-Windows, but what’s installed by default and the assorted management programs are a little different than what I’ve gotten used to on RedHat. But, once I got the hang of YaST, it wasn’t a problem. In fact, reconfiguring the server via YaST was how I got the SAMBA server installed, configured and running. I should point out that I did this all without the benefit of reading any documenation and it still only took me about five minutes. Very easy to use, even for a relativel newbie.
Mostly, it’s what I’ve come to expect from the modern distributions of Linux. It was easy to install, simple to configure, and pretty to look at while doing both. Oh, and on the old PII with 512Meg of RAM, it ran really well. Nice and smooth. I was able to connect to the SAMBA server, map a drive and copy a file without any issues or having to set it up as a PDC or BDC (that’s Primary Domain Controller and Backup Domain Controller, again for the acronym impaired). I haven’t done any security testing against it, but it’s tucked safely behind our new firewall, so I’m not too worried.
The one thing I noticed that I really liked was the fact that you had to enter a password to reboot the machine. In RedHat, at least the RedHat AS 2.1 I used, anyone who had physical access to the server could simply click the reboot button and it would. With SLES 9, after clicking that button, I was prompted for a password. Only after I supplied the root password did the machine actually reboot. Nice feature, that.

So, over all, nothing spectacular, but a good, solid offering from the newest Novell group, SUSE.

Why does this not surprise me?
According to this article on Groklaw, SCO had statements from an expert indicating that there was no infringing use of SCO proprietary code in Linux. Is this really a revelation? No, not really, but it is a little surprising to me that they would go ahead on their plan to attack Linux anyway. Apparently, they had the documents in which this information was discussed sealed so they could go on with their pointless lawsuits. Well, I guess they’d have had more of a point if they’d been successful. Of course, SCO did scare enough people running Linux that they bought, essentially, insurance policies to “protect” themselves from litigation. In light of this information, that seems like wasted money. Which, incidentally, is what I said from the very begining. I was asked by several people about this issue, in both my professional and personal life, and my response was the same. SCO’s alleged license infringement looked totally bogus and unwarranted, not to mention unprovable, so it wasn’t worth spending any money to “legalize” anything with them until the lawsuits had played out.
Gee, it’s nice to know I actually knew what I was talking about, isn’t it?

Man, I hate to admit this…
But, my home network is illin’, yo. I have run Netware at home for years. My firewall has been Bordermanager, because who the heck knows enough about it, besides me and the guys at Novell, to crack it? Yeah, yeah, I know, security through obscurity is a Bad Thing, but sometimes it does work. Anyway, I have one Netware server that crashes hard with the slightest power fluctuation, even with line conditioners in place. Just the littlest bit of power blip makes it shutdown. Not reboot, mind, but shutdown. And, several weeks ago when it did that, the data volume took a dump and never came back. I have no idea how much data I lost there, or how mad my wife is going to be because of the data she lost there, but I don’t think it’s coming back this time.
So, that got me thinking… Why should I stick with Netware? I’m more of a Linux guy now anyway, so maybe it’s time to look into Linux firewalls.
Any suggestions? And, anyone have any suggestions for ways to try and recover that crashed Netware data volume?