« October 2003 | Main | December 2003 »

November 25, 2003

iTunes Music Store Broken?

What's up with the iTunes music store this morning? I'm trying to browse but no matter what link I click on from the front page I go to today's #1 top song, which happens to be No Doubt's It's My Life. Also, if I click on any of the blue arrows to scroll through the new releases, exclusives etc the page gets reloaded and is formatted in a way that I can't see all the New Releases (goes under the "Top" lists on the right).

I did a Software Update and rebooted just to make sure it wasn't something on my machine.

Guess I'll work for a bit and see if something clears up.

Posted by mike at 9:06 AM

November 21, 2003

Webalizer Funky Behavior

I use webalizer for site statistics, and have been puzzled by something and recently figured it out.

You see, webalizer only handles 12 months of data at a time, but I like to keep multiple years worth of stats for comparing across years. My solution is to keep a set of logs broken down by year and then run webalizer for each set of year logs into one directory. This way I can have stats for 12-month increments over many years. I set the HTMLBody option to output a few links to allow navigation between the years.

The issue was that in some instances I was getting two sets of links, I searched high and low for a problem in my HTML that might trigger this to happen.

I finally figured it out when I recently ran the webalizer command with absolute paths from my home directory. Previously I was running it within /home/stats directory where I keep a local, tweaked copy of the configuration file. My command:

/usr/bin/webalizer -c /home/stats/webalizer.conf /home/stats/logs/all_2003.log
If I run this from the /home/stats dir webalizer automatically loads the options in the local webalizer.conf, and then sees the command line switch to load a config file and loads that up as well. The second load appends the HTMLBody options to what was loaded the first time.

I'm pretty sure, now that I've been through this, that when I first started using webalizer I read documentation on how the config files are handled. Unfortunately that kind of stuff never comes to mind until *after* you figure it out for yourself the hard way.

Posted by mike at 5:21 PM

November 20, 2003

Listening to the Voices of Evil (SCO)

Haven't written much about SCO (or anything for that matter), but can't resist. It's a complex saga, and often hard to figure out exactly where the different parties are coming from. It's very difficult for me to imagine why a company would go after the open source community *in this manner.* A couple things of note while listening to the SCO-published conference call:

How can SCO continue to move forward without making the violations clear? Doesn't that seem like it would be the first step? I guess if they make them all clear now they give the open source community more time to clean up and get moved off the violating kernel.

McBride says:

If it turns out the way SCO is saying, the ability to yank a million lines of code, roughly, out of a five million-line kernel that's there today is substantial.
I could be led to believe there would be some chunks of code, but a million lines?

At one time I understood that cleaning the Linux code up would not right the wrong. McBride was asked:

The Linux community is saying that they want to take the code out of Linux, and as you go through the IBM lawsuit, if you have to disclose the elements that are part of Unix that have been contributed into Linux, won't the Linux community just simply rewrite that? So what is the mechanism to disclose that code without losing your confidentiality?
McBride's responds by saying that the 2.6 kernel will have removed the SCO-published violations, but existing 2.4 kernels will continue to have those violations, and companies using the 2.4 kernel will need to license. That story is a lot different from the "all derivative works" we were hearing a few months back. Get the list of SCO-claimed violations, rewrite the code and march forward. I think the community would be willing to take a hit and have to upgrade Linux kernels across the board to get past this mess.

I've heard SCO deny there is any intention of making moves in hopes of being acquired. Twice during the conference call provisions for cases where the company is purchased were mentioned.

Posted by mike at 10:00 AM

November 12, 2003

A Mac Version of Windows?

Someone's a little confused over at vnunet.com, where a recent article on the latest Microsoft security patches indicates:

Both Mac and PC versions of Windows are affected by the fourth flaw, rated as important.
Just a little something to chuckle about.

Posted by mike at 4:17 PM

November 5, 2003

Fresh Look at Solaris Package Management

I was recently pointed to the blastwave.org site as an alternative to sunfreeware.org. I assumed it would be just another place to get precompiled and build Solaris packages, not quite.

Blastwave brings a new take on managing Solaris packages. All packages are CSW (Community SoftWare) packages, and are managed with a Debian-like set of tools. A core set of contributors manage the package base and end-users subscribe to these packages. When installing the package is pulled from a mirror and installed, rather than having to maintain local copies of the packages. Using pkg-get to grab packages takes care of installing dependancies.

Blastwave provides details on each package with helpful information about required packages.

Wondering what risks might be associated with using a system like this.

Posted by mike at 6:05 PM