Diary of a Network Geek

Got it licked!

Thanks to a little help from a fresh pair of eyes, that is. I’d been having trouble working with the image of our Dell Precision 670 Workstation series, until one of the other guys pointed out something in the registry for me. Now, I’d manually edited the registry file via a text editor, but, somehow, that didn’t make a difference. So, I changed it in another tool (Console One, actually), and the entire image worked! (To refresh your memory, the surviving Mike aka The Messiah, figured out a way to use SNAPShot to make addon images. So, I’ve been exporting the registry changes from the NAL objects I created in Console One, hence the above statement. Make sense now?)
And, I’ve redone the image for the GX280 the same way. Fortunately, I didn’t have the same problems with that image that I had with the SCSI based ones. Now, I’m working on updating the d400 image. It’s a little tedious, but at least I’m making progress again. Finally!

I had some minor setbacks at work this week.

I say minor because, as far as I’m concerned, anything short of termination or death is minor. So, first the ZENWorks imaging thing that I thought I’d worked out last week didn’t work this week. Or, rather, it didn’t work all the time or even consistently. So, I’m working on that. Again. Oh, joy.

Then, I’ve been doing a lot of Linux server work lately and that had some small snags. Mainly, it was me being tired, a little depressed, and somewhat distracted. I forgot a couple of little, “detail” items, like chaning IP addresses and cleaning out temp files before running a backup. Stuff like that. The only “show-stopper” was something entirely out of my hands. (Hey, that seems like a theme in my life these days!) The server that I’d been working on, and getting prepared to install on a remote SAN, can’t be shipped until we get the additional processor and power supply from Dell. They’ve been on order for almost a month now. *sigh* Oh, well, my end is almost done. Just a little bit of testing left to do and then…. I wait. (Unfortunately, that seems like a theme in my life right now, too. Always waiting…)

All in all, though, it’s not been a bad week. Nice and quiet. So far…

After some long struggles, VICTORY!

In recent weeks I have posted less and less about my job. Why, you ask? Well, aside from a serious bout of depression, things have not been going well on my projects. Oh, the Linux stuff was okay, mostly, except for a nasty little problem with that mkCDrec program and our SAN. Something about the way it makes the boot partition on the ISO just didn’t like the drivers for the QLogic cards we use. It would never recognize more than one partition at a time. Even after we recompiled it with multiple LUN support. But, I digress….

So, I’ve been banging away at this ZENWorks desktop imaging system deal for weeks. Well, it hasn’t been smooth, but we have a way that *seems* to work well. And, get this, we use snapshot! Yeah, I know, it sounds crazy, but it works. So, here’s the thing, we want to have one base image for XP and then just have addon images for everything else. But, we have at least one SCSI-based workstation. So, what does that mean? Trouble, that’s what. Ultimately, here’s what I did…

I started with a base XP image then added just enough to get it to boot on the SCSI machine (a Dell Precision 670). Next, on a second partition, I loaded all the snapshot files and started that process. Then, I loaded all the Dell drivers and such as appropriate and capped off the snapshot. Finally, I make the app and use filedef.txt to create a BAT file that copies the converted files to their original names and directories. From that, I make the ZENWorks image. And, viola! It works like a charm. Okay, so it’s a bit ’round-about, but it *does* work and a whole lot better than using sysprep, too. At least, for me.

So, all in all, it was a pretty good week! Now, all I need is to get a working car….

Well, maybe….

According to this article on Groklaw, the recent spate of cases that Novell has brought against Micro$oft may, in fact, have far-reaching implications in the legal realm of intellectual property and anti-competition. Specifically, how these cases are handled may have some direct impact on the rest of the pending Linux infringement cases that have been SCO’s bread-and-butter. So, in short, the author (“marbux”), encourages us to pay attention to the outcome of these cases. They matter and can effect the lives of Linux geeks everywhere.

Been a while in between Novell stories…

So, I thought I’d remind all my regular readers about NUI, Netware Users International.
First of all, if you use Netware, you’re probably already familiar with NUI. Novell did a pretty big marketing campaign a couple of years ago when NUI was just starting to get big. Well, now they’re big.
Secondly, it doesn’t cost anything to join. Yep, that’s right, it’s free.
Thirdly, you actually get benefits! Yeah, no charge to sign up, but you still get membership benefits. Cool!

So, anyway, if you haven’t signed up, or even thought about NUI, lately, you might want to check it out. Hey, it’s free, what have you got to loose?

Wow, there’ve been a lot of stories about Novell in the past two days!

Let’s see, where to start…. First off, Novell whupped Micro$oft to the tune of $536 Million, according to this press release from the networking giant. Apparently, Novell and Micro$oft agreed to “settle potential antitrust litigation related to Novell’s NetWare operating system in exchange for $536 million in cash.” Hmm, not a bad deal. I wonder what that will do to their stock? What’s even more interesting to me, is that Novell also announced it will file “an antitrust suit against Microsoft in the United States District Court in Utah seeking unspecified damages in connection with alleged harm to Novell’s WordPerfect application software business in the mid-1990s.” More cash? One can only hope.

In other Novell news, my favorite Open Source company has released a “new” Linux desktop. Yes, that’s right, they’ve got a Linux desktop, with the option to purchase support. I guess there really are advantages to living way out in Orem and not having anything else to do during the winter months but think! If you follow that link, by the way, you can download a free trial. I know I will be!

Yea, Novell! You go!

I’m finally getting it!

Okay, so it only took three months and a visit from a Novell Service Engineer for me to finally get it, but I have. Here’s the big secret to making ZENWorks imaging Linux boot CDs: key information is not anywhere to be found on the web. But, of course, the Network Geek will share with his loyal readers.
Now, I’ll do this in more detail later, but here it is in a nutshell. To update the bootable CD, first, get a good image and, using the instructions for adding a driver to the ZEN Boot image, get into the initrd.gz file on a machine that has the kernel version you want to update the CD to use. Now, copy all the drivers you want to use from the patched/updated server to the mounted initrd filesystem. Unmount that and re GZIP it. Now, copy your bzImage, or whatever, to a temp directory and rename it to “kernel”. Now, copy both of these files into the ISO, or make a new one with everything else on the CD. Burn it and go.

Yeah, yeah, I know, I went too fast, I’ll do it again with more detail later. I just was excited about it and had to throw that out there. Way cool!

Now, that’s my kind of error message!

Okay, I finally got a document that has all the details on how Novell builds their bootable ZENWorks CDs. More Linux work for me! Yea! So, this week, I’ve been building a Linux server and learning about updating/recompiling the kernel. As you can tell from the title of this entry, I haven’t been too successful. But, I’m getting there! I’m really headed into unknown waters at this point, but they’re the most fun. Never know what’s going to happen next.
I’m really becoming quite a Linux expert now, whether I like it or not. Luckily, I like it. Linux is fun, to me, even if it is a bit confusing and challenging sometimes. I’m usually pretty good at figuring out what’s wrong and fixing it, or making a work-around. It’s not exactlly rocket science, after all. Now, I just have to figure out what I did wrong that caused the kernel panic. And, now, why my “mkinitrd” is returning an error about an MPT device. But, at least I have a clue where to look, thanks to the error message, and I have a hope of solving the problem. If only my personal life were so simple and straight-forward…

Ah, well, back to the ol’ uranium mines!

Oh, this is cool.

Okay, so I’ve been doing a lot of work on Linux lately. Not only for the bootable ZENWorks imaging system, but just plain Linux stuff.
Last week, I set up a Red Hat AS2.1 machine for use as an FTP server, but, just as I was starting this for the folks who need it inhouse, they start talking about needing a Windows 2000 server to run some specialized print server for eMatrix, which is what the FTP server was for. So, my boss suggests that we use VMWare for Linux. Brilliant! Of course, most people are running VMWare on a Win32 machine and emulating Linux, but we think outside the box. No problem, I get it all installed and running, though the first time I ran the VMWare PERL script that set up the program, it failed. No reason for it to fail, as far as I could tell, because it ran the second time. Great, so I get it all installed an running and let the boss know. Then, he asks me, so what are we going to manage this machine with? Er…. VNC, I guess.
Right, so I get that setup on the Windows machine in VMWare without a hitch. Getting it installed on Red Hat wasn’t a problem, but getting it running…. Well, thankfully, I finally figured out that the Real VNC website has the answer on a page called Native X display Support. The only thing is I need to edit XF86Config-4 instead of XF86Config. No problem! Now the VNC server autostarts. And the boss asks me if I can get the VMWare session to automatically launch at reboot. Er…. Well, I can see what Google turns up!
What I eventually came up with was a shell script I called “xvmstart” that was as follows:

#!/bin/sh
# Written by JKH on 10-13-04
. /usr/bin/vmware -x /vmcfg/Windows2000Server/Windows2000Server.vmx

(Where vmcfg is where you stored your configurations for the virtual machines. Oh, and if the last line wraps around, that should be a three line script.)
I saved that file in /root/.kde/Autostart and rebooted. As soon as I logged in, BAM! VMWare loaded like a charm. So, now, I had to make this badboy autologin… Er, back to Google.
I finally found a forum that told me I had to edit /usr/share/config/kdm/kdmrc to set AutoLoginEnable=true and AutoLoginUser=skippy (or, whatever you want to autologin as). KerPlow! A fully automated solution brought to you by Linux, Google, VMWare, VNC, and me, the Network Geek.

I love my job!

A follow up to yesterday’s entry.

Okay, so, if you follow Slashdot, you’ve seen this, but I thought it was worth reposting. Of course, part of that is because I’m just a little bit of a Novell zealot. To put it mildly.
I thought the article was interesting. I especially liked the way that Mr. Schlaeger emphasized the idea that Novell was really supporting Linux, KDE and OpenSource. It’s really the way of the future with IT and computers in general. I have a friend that used to work for Microsoft and is now totally hooked on Netware, Linux, and Mozilla. All it took was a little push from your friendly, neighborhood technology pusher (i.e. ME!) and the rest was as easy as blue-screening a Windows server.
In any case, the interview over at KDE.org is worth reading if you have anything invested in Linux of any flavor, Novell, or KDE. I hope it’s a continuing trend for both Linux and Novell.