Optical Illusion
I saw this today. I thought it was interesting.

[/musings] [permanent link]

WTF?
I'm used to guitarists mocking the bass and bassists. It doesn't bother me too much. But this... This irritated me. A lot.
Today at work there was a group of people talking about Rock Band and Guitar Hero 3. None of them actually know how to play intstruments but they claim to be great at these games. They seem to believe this entitles them mock bassists.

• "Oh man, bass is so easy. It's the guitar that's the hard part. Yeah, I'm on expert on the guitar."
• "Yeah, bass is so stupid."
• "So It's me, my brother, and my sister. I play guitar, he's on drums, and my sister sings."
  "what about bass?"
  "My friend just got Guitar Hero 3. I'll make him play bass."
  [Both laugh]
• After making statements indicating this person believes he actually is better than Tom Morello, "After you make Tom Morello or Slash your bitch, they play bass for you."

[/musings] [permanent link]

chdir(2)
So today at work another developer many years my senior, with many more years experience than I, came to me with a Unixy problem.
"When I have a program, how can I have it so the current working directory for all processes it starts isn't the one that it started in?"
"chdir."
"No, I want so that if this process starts something like ls, when ls stats 'dot' I want 'dot' to be the directory that process wants it to be, not the directory that process was started from."
After about 15 minutes of me suggesting chdir while he said that's not what he wanted but then describing chdir, I finally wrote something along the lines of the following

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

int
main (int argc, char *argv[])
{
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/tmp");
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/etc");
  system("/bin/pwd");
  system("/bin/ls");
  chdir("/");
  system("/bin/pwd");
  system("/bin/ls");
  return 0;
}

I compiled that, ran it, showed him the output. He said, "Yeah, that's what I want to do."
I showed him the code.
"chdir does that?"

[/unix] [permanent link]

Alpha
Due to the power failure, there was the loss of several hours of work. Last night I installed FreeBSD 6.2-RELEASE on an old DEC AlphaStation 200 I have. I had started building a new, smaller kernel for it around 23:30 last night. It had not completed by the time of the power outage. I have restarted that build.
Any one reading this would reasonably ask, "Why are you not as confused/angry/annoyed with a compile that was not finished in 7 hours as you were about one that took 3 hours?"
The answer is simple. This AlphaStation is powered by a 100MHz DEC Alpha EV4 CPU and has 64MB of RAM. To the best of my knowledge, DEC made this machine around 1994 or 1995. I expected the build to take a long time; the machine is around a dozen years old.

[/unix] [permanent link]

How long does it take to build a linux kernel?
It has been a number of years since I built a linux kernel. Slackware 9.1 was the last GNU/Linux distro I used before switching back to BSD. Tonight I put together a machine from some old parts (1.2GHz celeron with 256KB cache, 256MB RAM, 20GB hard drive) and installed Slackware 12. I customized a kernel configuration and attempted to build it. I don't remember the 2.4 kernel taking as long to build as this 2.6 kernel. It took nearly two hours. Granted, this machine is fairly old, but 2 hours? After I complete the tasks for which I needed this setup, I'm going to install an older Slackware with the 2.4 kernel and build that. I may also install FreeBSD and NetBSD and build their kernels. I'd like to get an idea how long it takes to compile other kernels on this rig.

[/unix] [permanent link]

Initial Thoughts on Windows 10 -- UPDATED!
I'm done with Microsoft for any platform that is not a telephone. Windows 10 attempts to "fix" the abomination that was windows 8 on the desktop, but just makes things worse.

The "search" "app" that replaces the previous existing search feature really only sends a query to bing. I'm looking for a file somewhere in a subdirectory on my hard drive. I didn't want to search the web for 20141020*.txt. The UI looks like crap. Slapping a titlebar on top of the "modern" "apps" does not make them usable on the desktop. The start menu has returned, but it has never been this useless. And the ability to revert to the "classic" start menu, the behavior introduced in windows 95, and refined in win98 and Windows 2000, has been removed. I shouldn't be surprised by that given that Windows 7 also lacked the "classic" start menu. At least Windows 7 allowed a "Windows Classic" theme for the rest of the UI.

Ever since Service Pack 3 for Windows XP, MS has been slowly and surely trying to make things "easier." However, what they deem "easier" often means removing features and behaviors I relied on to get work done. Windows 10 continues this tradition.

I never really had a problem with Microsoft, I never avoided their software for ideological reasons. I believe in using the right tool for the job. Windows 10 is the wrong tool for any job.

UPDATE!!!

Using the Windows Update mechanism, MS pushed out a new build of Windows 10. This upgraded the installation from build 9841 to build 9860. After a lengthy download, installation, and a very long reboot, I was able to log in again, Only to be greeted by this:



And this lovely error when I tried to open the new "Notification Center":



Now isn't that special?

[/musings] [permanent link]