Thoughts on National Computer Science Education Week
This week is apparently National Computer Science Education Week. Code.org is organizing the "hour of code" to promote teaching of Computer Science and Programming in schools. They're also organizing petitions to make CS courses count as credits in Mathematics or Science for High School graduation requirements.

In High School, my CS courses were by far my favorites, Programming in Pascal, AP Comp Sci in Pascal, Programming in C++, and AP Comp Sci in C++ ( the language for the exam switched my junior year). I learned a lot about structured code, elegant, efficient code. I learned enough about Data Structures and Algorithms that I didn't have to study for my college CS classes until Computational Structures (Discrete Math II with Scheme, essentially) in my third semester. I had an amazing Computer Science teacher who also taught me Calculus and the proper order of precedence in life: God, Family, Math. I wouldn't be where I am today without that educational opportunity I had in High School. I want others to have that opportunity too.

However, this is where I differ with the opinion of the Code.org folks. I do not believe that CS classes should count toward the Math or Science requirements. In this state, CS counts toward the "practical or performing art" requirements, I'm assuming under the "practical" label. I think this is a better place for it at the High School level.

Computer Science is not a hard Science. It's not Physics. It's not Biology. It's not Chemistry. There's a saying that if the subject has science in its name, it's not really a science. That is true with Computer Science. It's not studying the how and why of atoms, of molecules, of living systems, of anything really. It's not science.

Computer Science is really applied mathematics. I am very fortunate that the college program I went through was very strong in mathematics: Calc I and II, Linear (Matrix) Algebra, Discrete Math, Discrete Math II in the guise of Computational Structures, Probability and Statistics, Theory of Computation, Algorithmic Analysis... the list goes on. All of these mathematical foundations were then applied to a machine, to make the machine carry out a task in an efficient manner. It's those mathematical foundations that are the true core of Computer Science.

While mathematics is the core of Computer Science and Computer Science is essentially applied mathematics, I do not believe it should count toward the Math requirements. The CS classes would likely detract from other mathematics courses such as Geometry, Trigonometry, and Calculus. These courses are far too important to an education to be replaced by a Computer Science course. Many, maybe even most, High School Computer Science courses focus more on "programming" than the fundamental mathematical theories. They will pick the language du jour and teach you the syntax and semantics. They'll teach about basic data structures like arrays, and linked lists. The AP exam currently focuses not on implementing lists, trees, stacks, queues, and sorting and searching algorithms, but on arrays and lists using Java library calls. This is not math. This is learning Java syntax.

[/code] [permanent link]

Prince
I'll never forget the day I started liking Prince's music. I was with my friend in his car headed somewhere. We were listening to K-Rock and they had a "listener playlist" where for about an hour, all the music had been selected by a listener and this listener was on the phone, talking with the DJ about his selections and introducing songs.

The guy announced that the next song was from Prince. The DJ questioned this selection and he said, "No, this dude can shred. Just listen."

And we laughed.

And we listened.

And Prince shredded.

[/musings] [permanent link]

Blosxom 2.2.0
Apparently Blosxom development has been picked up again. There was a new release on 2024-02-03. Nice!

[/unix] [permanent link]

Trouble opening aterm in FreeBSD?
Here's a soltuion! https://forums.freebsd.org/threads/44941/

[/unix] [permanent link]

X11 Mouse Cursor Themes
Starting after installimg the binary nvidia drivers on both my laptop (Quadro K1100M) and my workstation (GeForce GT 630) Blackbox was defaulting to a mouse cursor that was suboptimal, a black, notched triangle.

The settings in the Xresources for the mouse cursor theme are honored by XDM at the graphical log in, but when Blackbox or Fluxbox start, the cursor would change to the black notched triangle. TWM honors the settings in Xresources, but TWM is just a little too minimalist, even for me.

But there's a simple fix!

Create a file in your home directory (if it doesn't already exist) .icons/default/index.theme. In this file, add the following lines:

[Icon Theme]
Inherits = polarblue

where polarblue is the name of the X11 mouse cursor theme you wish to use. FreeBSD installs many of the X11 cursor sets into /usr/local/lib/X11/icons/, your Unix flavor may be different. In theory, you can also install new themes of your choosing into ~/.icons/ and use those without the need for any elevated privileges.

Additionally, there's the option of creating a .Xdefaults file in the home directory and adding the line

Xcursor.theme: polarblue

Again, where polarblue is the name of theme you want to use.

[/unix] [permanent link]

FreeBSD Unix on Dell Precision M4800
I installed FreeBSD 10.3 on the laptop I recently acquired and almost eveything worked out of the box. The gigabit ethernet and wi-fi coards worked fine and by setting the BIOS to discrete graphics only, the nVidia Quadro was recognized.

I installed the binary driver from nVidia, because they support FreeBSD because they're awesome like that. The nvidia-xconfig(1) program was useful to streamline the process of getting X.org to use the Quadro.

There were a few things that did need some tewaking though. First there's the sound card. Because the quadro supports HDMI (in addition to VGA and DisplayPort), it includes an HDA-compliant sound card. This card is recognized before the primary HDA-compliant sound card in the machine, the one that's actually connected to the speakers.

I did some research and there were some suggestions about using sysctl(8) to control soundcard GPIO pins to connect the nVidia sound device to the speackers but what ultimately worked was using sysctl(8) to change the default primary sound device to the dedicated card. There were a few ways to make this happen but the one I found that actually worked was to place sysctl(8) command lines in /etc/rc.local.

First I found the device I wanted as the default:

mforde@gaz:~> cat /dev/sndstat 
Installed devices:
pcm0:  (play) default
pcm1:  (play)
pcm2:  (play) 
pcm3:  (play)

Device pcm2 was the one I wanted so I added the following lines to /etc/rc.local

sysctl hw.snd.default_unit=2
sysctl hw.snd.default_auto=2

Now when boot completes pcm2 is set to my default and sound "just works" and sndstat shows pcm2 as the default.

I found ACPI support has some weirdness as ACPI support often does. What I found was that Suspend works from console, but resume doesn't... HOWEVER After I start X ACPI suspend and resume work just fine. Normally I prefer to boot into a console and only start X if I really need it, but because I want suspend and resume to work "by default" I've enabled X to start at boot by allowing the xdm console in /etc/ttys.

But this had one last issue. See, when manually starting X, I added the -dpi 143 option to get graphics and text to be appropriately sized for my screen. XDM needed to know about this.

This probably wasn't the best place to do it, but I edited /usr/local/lib/X11/xdm/XServers and modified the call to X(7) to add the -dpi 143 option. Now when Xdm loads at start up, the DPI is set correctly.

The function keys for adjusting the screen brightness don't work; however, xbacklight(1) works just fine. Similarly the volume keys don't work but I can adjust the volume quite easily with aumix(1).

I've submitted my dmesg output to NYCBUG's dmesgd repository.

I suppose I've posted this for two reasons. The first is so I have a record of how I eventually got these little things working in case I have to do it again. The second is in case anyone has similar issues with their hardware; if they happen to stumble upon this, it might give them some hints.

[/unix] [permanent link]

Remapping Keys in Vim
While I love the keyboard on my relatively new Dell M4800, I'm not particularly fond of the placement of the Page Up and Page Down keys to the left and right of the Up arrow, and above the Left and Right arrow keys. I find myself accidently hitting those keys too frequently while editing code and jumping all over the file.

So I remapped them. It was quite simple, because Vim is awesome. I added the following lines to my .vimrc file:

map <PageUp> <Up>
map <PageDown> <Down>

This turns Page Up into a second Up arrow, and Page Down into a second Down arrow. For now, I'll leave it like that. I may remap them to the Left and Right arrows in the future. Or not.

[/unix] [permanent link]

How to Make VMWare suck less Tip #273
Find the .vmx file for your VM and add a line

bios.bootDelay = "15000"

That gives you 15 seconds before the virtual machine launches the boot loader, giving you plenty of time to do things like change the boot order so you start from a recovery CD.

[/unix] [permanent link]

Things I love about vim

• Tabbed interface in the 7.x line
• Macro recording
• Built-in sed
• :make
• Not needing to remember a thousand key combinations that require seventeen fingers to properly execute

[/unix] [permanent link]

Resetting Vim
On occasion while I'm coding, I'll mistype something and vim's code autoindenting will stop honoring my settings. Likely, I've done something stupid that has disabled or modifying the settings from the defaults I set in my .vimrc file.

If (when) this happens, Vim can be reset without exiting the procces by going into command mode and typing

:source $MYVIMRC

This reloads the settings of the .vimrc file without forcing you to restart the process, thus losing your place in your code.

[/unix] [permanent link]

... On man pages, a mini-rant
I really despise the linux man pages. They're useless at best and wrong at worst.

From the man page for setsockopt: "The include file <sys/socket.h> contains definitions for socket level options, described below."

1) The options are not "described below."
2) No, that file actually doesn't contain those definitions.

On the other hand... The FreeBSD man page for setsockopt does actually describe the options and under FreeBSD the <sys/socket.h> file does indeed contain the definitions.

[/unix] [permanent link]

[mini-rant]
I hate bash. I hate it. I hate how it bastardized bourne by adding half-assed implementations of features from ksh and tcsh.

[/unix] [permanent link]

Problems with loader.conf

First the background. The story of how I got into this mess:

I'm trying to get ACPI working on my laptop under FreeBSD. Specifically, I'm trying to get Resume to work properly. Suspend works, and resume seems to partially work. The fans spin up, the keyboard's backlight comes back on, but no screen. And without video, it's a little hard to figure out what's going on.

ACPI works great on my server. It's running the same FreeBSD 9.1 x86-64 build that the laptop is, but the biggest difference is that it's an intel motherboard. The laptop is an Alienware, for our purposes, I might as well just call it a Dell.

I started comparing the ASL output from both machines and noticed some things. First, the Alienware's ACPI implementation looks for the OS to be various forms of Windows or "Linux." The intel ACPI implementation also looks for these Windows variants and "Linux" but it has an additional OS string. It has an entry for "FreeBSD."

I figured the easiest next step was to use iasl co compile the intel ASL source and load that DSDT onto the laptop.

I calculated the odds it would work vs the odds I was doing something incredibly stupid... and I went ahead and did it anyway...

I compiled the asl and I set /boot/loader.conf to override the DSDT with the intel one I had just compiled and I rebooted. At first everything was good. The machine went down, I got the boot loader, and the FreeBSD kernel started to load. Seconds into the kernel load, it rebooted itself. After the second time, I powered off and tried a cold boot. Same problem just as I had feared.

Now i was in a situation where I couldn't successfully boot because of an error in loader.conf I needed to find a way to edit it.

And here's the solution:

The FreeBSD bootloader, like many others, works in stages. At a certain point, it can be interrupted at which point it provides a set of simple yet powerful commands to control various aspects of the loading process. If you still have that default menu at load, I beleive the option to chose is 6. I disable that menu so during a brief countdown I hit escape before the boot loader turns control over to the kernel.

Once in the boot loader prompt, I entered the following commands:

unload
load kernel
boot

Pretty simple right? The unload command does what it says, it unloads the kernel and any modules loader.conf had pulled into memory. The load kernel command grabs the kernel and loads it into memory... but only the kernel thus ignoring the broken DSDT in loader.conf. And of course boot tells the boot loader to continue booting the system.

Once booted, I removed the bad DSDT from loader.conf.

[/unix] [permanent link]

Excluding directories while using pax(1)
My primary disk is failing. There are large segments that are generating low level IO errors during read or write operations. Most of the files written to the bad area were under /usr/ports/ where the FreeBSD Ports collection is installed. A few files were under the web server's root.

Figuring I'd take care of things prior to the disk actually failing to the point of it being irrecoverable, I purchased a new disk early. I installed it, partitioned it, and formatted it.

To copy the data over, ignoring the areas that were causing the IO errors, I used mv to "move" the files from the web root under /usr/ports and used the following command as root:

pax -rwvpe -s':/usr/ports/.*::gp' -X / /mnt/newdisk/

The -X prevents pax from traversing into mount points that have a different device ID than the one on which it was started. This prevents an infinitely recursive loop from happening when the new disk's mount point would have been hit. It also prevents data on the non-failing disks from being copied as well.
the -s option allows for sed search and replace scripts to be run. In this example, the : is used as the delimiter and any path matching /usr/ports/* is replaced by a null string. With this replacement all directories under /usr/ports are excluded from the copy.

[/unix] [permanent link]

freebsd-update
I'm attempting to update my laptop from FreeBSD 9.1-Beta1 to 9.1-RC1. The freebsd-update(8) utilitly was reporting an error finding the public key. A quick search found this thread. As per tangram's suggestion, I used

env UNAME_r=9.0-RELEASE freebsd-update upgrade -r 9.1-RC1

and then the update began working.

[/unix] [permanent link]

Fun little alias
I use a console based RSS reader written in Ruby. It crashes often and will delete my list of feeds in the process. It also has a tendency to not fully exit, leaving a ruby process sitting in the background soaking up close to 100% CPU time. For such occasions, I've added the following alias to my .cshrc file.

alias killraggle kill -9 '`ps ax|grep raggle|grep -v grep|awk '\''{print $1;}'\''`'

[/unix] [permanent link]

FreeBSD 6.4 EoL
As of yesterday, FreeBSD 6.4, and with it the entire 6.x branch, has reached its End-of-Life. It's time to upgrade (or maybe upgrayedd, for a double dose of something-or-other).

So herein lies the problems. Months (years?) ago, I attempted to upgrade tak to FreeBSD 7.2. I plugged in a SATA disk into my workstation, installed the OS, reconfigured all the daemons, services, and functionalities tak has running, copied over a snapshot of all the data, and then edited the fstab to match the device names as they'd exist on tak.

I removed the IDE root disk and installed the new SATA disk and tak and watched the kernel fail to find the root disk. Or the other SATA disk in tak.

Based on the bug reports in the FreeBSD Gnats system, and various conversations in the mailing list, it seems Asus, who made the motherboard in tak, used a slightly non-standard SATA implementation on this particular board. Between the 6.x and 7.x line, some work had been done on the SATA drivers in FreeBSD and mad them more standards-compliant (a good thing). This, however, broke SATA on this Asus board.

Tak is about 6 years old now, and other than some over heating issues, serves its purpose well. So do upgrade to FreeBSD 8.x on an IDE disk and replace the other SATA disk with another ATA disk, or do I build a new, lower-power, higher-performance system?

If anyone actually reads this, feel free to use the new comments feature to give me feedback. I think it's working.

[/unix] [permanent link]

SATA Weirdness update
A BIOS update from Intel corrected this issue.

[/unix] [permanent link]

Gmail and mutt
I like mutt. Of all the mail clients I've used over the years, it sucks the least. It works well with my mail server.

Despite having my own domain and mail server, I still use gmail for certain things; things I don't mind being retained for 3 years after I delete them, or more specifically, things I want retained for 3 years after I delete them.

I don't like the gmail web interface. I find checking my gmail to be annoying because of this. I remembered gmail offering POP and IMAP. I figured I could use that to get my gmail. Shouldn't be too hard right?

A quick search of Mr. Yahoo and Mr. Google gave me two good starting points: Lifehacker.com and MattCutts.com.

I read the sites and the getmail man page and figured out what I needed to do. First I enabled IMAP for my gmail account. Next, I created the .getmail directory in my home directory then created a getmailrc file there. I want all gmail mail to be delivered to a specific mbox file without going through my normal mail delivery channels. The contents of the getmailrc file are quite simple:

[retriever]
type = SimpleIMAPSSLRetriever
server = imap.gmail.com
username = username@gmail.com
password = usernamespasswordgoeshere
mailboxes = ("inbox",)

[destination]
type = Mboxrd
path = /usr/home/mforde/Mail/GMAIL

The retriever section defines how getmail will retrieve the mail. In this case it uses IMAP over SSL to connect to imap.gmail.com. The mailboxes setting can be used to specify only certain gmail labels to retrieve, but I want anything in the inbox.

The destination section tells getmail what to do with the mail once it has grabbed it from gmail. This configuration dumps it into an mbox file I've named GMAIL.

I chose IMAP over POP because of the slightly-less-than-documented "feature" of gmail only allowing 99 messages at a time over POP.

So to get the initial batch of 7000+ emails, I ran

> getmail -vvv -l 

to get verbose output and to leave messages on the gmail server. When that was done I pointed mutt at the GMAIL mbox and like magic, there was my gmail, organized nicely in my terminal.

Now, I want to check to get the latest mail fairly often, and I don't want to download messages already copied over. To accomplish this, I added a crontab to run every 10 minutes and invoke

getmail -l -n -q

This tells getmail to leave copies on the server, only get new messages it hasn't already retrieved, and be quiet about it.

This has worked out well for me. If you're interested in setting up something like this, I highly recommend reading the article at matcutts.com. That article also links to several sample getmailrc files.

[/unix] [permanent link]

FreeBSD 8 Beta 3 Available
FreeBSD 8.0 Beta 3 is now available for download. The final release is expected in about a month.

[/unix] [permanent link]

BSD v. GPL
Jason Dixon gave a talk at this year's NYCBSDCon entitled "BSD v. GPL (a.k.a. not the sequel to "BSD is Dying")." It's a humorous look at the differences between the licenses and their supporters. Despite the humor, he made some good points.

You can find a copy of the presentation at The Dixon Group website.

[/unix] [permanent link]

Mailman
The other night I installed mailman on my server. I integrated it into the apache configuration and restarted that. The mailman web interface became available as expected.

I used the web interface to subscribe to the one list I had set up and I received an email asking me to confirm my subscription. I went to the included link, and all seemed to be good.

Another person joined the list successfully, then sent an email to the list. This email never arrived in her inbox. She told me about it, and I checked only to find I did not have a copy either. I sent a mail to the list and promptly received a message saying that [listname] was not a valid recipient at the domain.

That's when I realized I had forgotten to tell the mail server (postfix) about mailman. I had told apache about mailman, and mailman about postfix, but not postfix about mailman.

I used mailman to create an alias database for its single list, then updated postfix's configuration to use that as one of its alias maps. All seems to be working now.

In conclusion, I learned two things. One is always test your configuration before telling people it's ready. The other is, "I'm an idiot."

[/unix] [permanent link]

FreeBSD 7 SATA Weirdness
Over the weekend I installed the x86-64 build of FreeBSD 7 on my workstation, dib. I haven't had time yet to configure everything to my liking yet, but almost everything works.

The one really annoying issue centers around a SATA DVD burner. When this device is attached to the primary SATA controller (ICH7), the system refuses to boot from the hard drive. It reports that no system disk has been found. I've tried all of the SATA settings options in the BIOS and none work.

If I connect the SATA burner to the secondary Marvell "RAID" controller the system boots from the hard drive without issue. In Windows, this requires another driver (which for some reason installed a copy of apache along with it). Under FreeBSD 7; however, this second controller seems to be currently unsupported, leaving me with only the IDE burner available.

I may spend the $20 and get another IDE burner and just forget about the SATA issue, but I really would like to know what the problem is. If any one has any idea why the system would fail to boot from a SATA hard drive when a SATA optical drive is attached, please email me and give me some insight into this issue. Maybe the Unix category wasn't the best for this. I spent more time discussing the hardware/BIOS weirdness than the installation or configuration of FreeBSD7. In fact, FreeBSD 7 isn't a very good title for this either. I'm going to change that.

[/unix] [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]

Demo -- Update
Rskutins recorded his drum part and sent it to me via the wonders of TCP/IP netowrking. On Friday night I finally had enough time (and motivation) to start recording.

I spent a lot of time fighting with ProTools. It repeatedly crashed. Often, when it didn't crash, it simply stopped recording and reported that an error had occurred. I'm remembering this for the ProTools rant that will be coming in the future.

After 45 minutes I had recorded about 6 seconds of vocals and the 24 second bass line. The next block of Copious Free Time(TM) I have, I'll begin the rough mix of the three parts. Hopefully ProTools won't crash as often during that phase.

With any luck, it'll be mixed in the next week or two.

[/album] [permanent link]

Writing

"You need strong emotion, whether it's fiery or depressed, an extreme state of mind. I think in any art form it's the case." -- Daniel Ash

Maybe it's my lack of experience. Maybe it's my lack of talent. I tried to sit down and write music for the song known as Ravage in the new naming scheme, but I failed miserably. When I try to force it, like I did tonight, nothing comes out right. I have ideas, I can hear them in my head, but without that inspiration, without that emotion, nothing I produce sounds right.

I've been too happy recently and it's destroyed my creativity. I get the urge, I have the inspiration, to write when I feel negative emotions. I need anger; I need depression. It is in dealing with these emotions that I am able to write.

I have tried several times to force myself to feel this way. This usually buys me a few minutes in which I can write, but it often fails. Because the emotions are artificial, the results are mediocre at best.

I find this situation to be quite frustrating. I want to move forward with this album, but without that inspiration I am unable to do anything.

In the meantime, I'm slowly teaching myself to play guitar and, to a much lesser extent, a keyboard-style synthesizer. I've also been going through materials my music teacher friend gave me to learn some basic music theory. Hopefully once I find that needed inspiration, or find a way to work without being angry or depressed, this new knowledge will make things easier.

[/album] [permanent link]

Revision Control
One could argue that this should be filed under the Unix category, but this post is more about the album than it is about the Concurrent Versions System.

Friday night I created a CVS repository on this server to manage album related files. After discussing it with rskutins, we agreed on several key points.

First, with changes being made a little more frequently than before, it would be best to have some way to track what was going on, and to be able to roll back to a previous version if the changes don't quite work out. Second, we wanted to have a way to organize several files for each song, for instance, lyrics, notes, bass tabs, drum tabs, etc. Last, and maybe the most important reason for the reorganization, we wanted to move away from the numbering scheme that was in place. Each song was numbered from 0 to 17. This was fine until we realized 11 was likely to be the first track on the album.

Now the album is stored in a CVS repository. This will keep a version history of each file, allow us to simultaneously work on parts of the album, and merge our changes.

Within this repository we now have a tree structure where each song has its own directory. The directory will hold any and all files related to that song. In an effort to move away from the numbering scheme, an arbitrary naming convention was mutually agreed upon. The songs are now known by names such as Soundwave, Ravage, Frenzy, and Rumble.

The album is starting to come together. I feel motivated to work on it and recently I've found myself inspired to write. Now if only I had time.

Omlette listened to the Accidental Mix I posted (of the song now known as Soundwave) and gave me some feedback.

It sounded ominous. I don't know how else to describe it since I'm not familiar w/ either artist. Oh wait. Were you mixing your own stuff?

Ominous seems like it could be a good thing given the current direction of the album.

If anyone else takes the time to listen to it, I'd appreciate any comments or suggestions. If you don't have it, my contact information is on this page.

[/album] [permanent link]

Another Demo Update
Two weeks! Ha! It's been closer to two months.

A few days ago I had some time so I sat down with the ProTools set up again. After considering some advice from jlight, I decided to record a second track of the bass line. I decided to use my Yamaha for the second track, as I had used my Fender for the original recording back in June. The two instruments have different characteristics in their sounds and the two playing together seems to add a "fullness" to the sound.

So all I had to do was record 24 seconds of bass and put together a mix. This should take, what, 15 minutes? It took 45 just to record. Once again ProTools repeatedly crashed. When it wasn't crashing, it would report an error and stop recording. Does anyone know if there are updates for ProTools LE 7.1 that will fix this issue? As it stands now, I can't run ProTools for more than a few seconds without disabling multi-core support on my CPU. I have multiple processors. It is a multi-threaded application. It should run better... But I'll save this for that upcoming ProTools rant I keep promising.

Anyway, after about an hour and fifteen minutes, I got two mixes complete. One of them was accidental and sounds, "interesting." The other is closer to what I had in mind. While I wait for feedback on the actual mix from certain people, everyone is free to enjoy the accidental mix found here.

If anyone actually listens to it, I'd be happy to accept any comments and criticism.

[/album] [permanent link]

Demo -- Update
Rskutins recorded his drum part and sent it to me via the wonders of TCP/IP netowrking. On Friday night I finally had enough time (and motivation) to start recording.

I spent a lot of time fighting with ProTools. It repeatedly crashed. Often, when it didn't crash, it simply stopped recording and reported that an error had occurred. I'm remembering this for the ProTools rant that will be coming in the future.

After 45 minutes I had recorded about 6 seconds of vocals and the 24 second bass line. The next block of Copious Free Time(TM) I have, I'll begin the rough mix of the three parts. Hopefully ProTools won't crash as often during that phase.

With any luck, it'll be mixed in the next week or two.

[/album] [permanent link]

Demo
In the next few weeks we are going to attempt to record and roughly mix a demo of a short track which will serve as an introduction to the album.

Currently known as 11, it is a very short piece in 4/4 time at 80bpm. It is in the key of B minor and the spoken words are taken from a quote attributed to Nietzsche.

What upsets me is not that you lied to me, but that from now on I can no longer believe you.

This short demo will hopefully get me motivated enough to put more time into the album.

More information will be posted when it becomes available.

[/album] [permanent link]

A Brief History
Last Summer, my friend, rskutins, and I decided we were going to write an album. He got out his drum machine, being smaller and easier to store and carry than a full kit, and I got out my bass and we started putting together some pieces that were... not good.

We had little direction, I was afraid to play things outside of my comfort zone, and we had some problems communicating. This project quickly fell apart, but we never completely gave up the idea.

In March I found the inspiration I needed. I talked to rskutins and we started working on an album again. This time, fueled by strong emotion, both fiery and depressed, I started by writing lyrics.

Not all are complete, but there are about 15 sets of lyrics for us to use as a starting point. Rskutins has tweaked the lyrics in some places to make them fit a better rhythm while still maintaining the intent of the words. I am quite pleased by what he has done.

Based on these lyrics we have begun writing short pieces here and there when we feel inspired. Rskutins has laid down some pretty good beats to start with. I've been attempting to learn some basic music theory and trying to apply those ideas to the layers on top of what rskutins has written already.

And that's where we are now. Still learning, still writing. Our day jobs have slowed down our progress considerably so it could very well take until the Autumn before we're ready to record and mix the album.

[/album] [permanent link]

Best Buy Charges Customers for Exchanges
This weekend I witnessed a friend try to exchange an item at Best Buy. He had mistakenly purchased the full-screen version and wanted to exchange it for the wide-screen version. While he did not have his receipt, it still had the Best Buy sticker on the shrink wrap as well as the $19.99 price tag.

The signs on the shelf indicated that the wide-screen version was also $19.99 and as of January 22, both versions are $19.99 on the Best Buy website.

My friend waited online patiently for about 15 minutes to make his exchange. He handed the Blue Shirt both the full-screen version he had purchased and the wide-screen copy he picked up before going to the customer service line. The Blue Shirt asked if he had paid cash or credit and when my friend said credit, the Blue Shirt asked for his card.

The Blue Shirt swiped the card and pushed a bunch of buttons then told my friend he'd have to pay $5.35 ($5 plus 7% sales tax) due to a "difference in price."

When we questioned this "difference in price" we were told, "Wide-screen always costs more than full-screen."

I am boycotting Best Buy and I urge others to do the same. This company has a long history of using underhanded tactics to increase profitability at the expense of its employees and its customers.

[/musings] [permanent link]

An Awesome Christmas Present
I waited until to today to verify that it wasn't just a random occurrence. I checked again this morning and it was the same as yesterday.

I gave myself one of the best Christmas presents I've ever received. It took me about nine months to accomplish it, but I gave myself a new body, and more positive perspective on life.

As of yesterday, I have lost 101 pounds (45.8Kg for those of you who prefer the metric system) and over nine inches (22.86 cm) from my waistline.

A friend of mine told me tonight that, her doctor had told her recently that people can live much better lives, with fewer ailments, if they just made simple life changes. She said that having watched me over the last year transform my body, my mind, and my life, she found me to be a good model for positive changes people can make in their lives. As much as hitting the century mark meant to me, her words meant even more.

I've been thinking about this for a while and I think I'm going to become a motivational speaker. I want to help people change their lives for the better.

[/musings] [permanent link]

Product Review: ASICS Cumulus-11
This is the third installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my again I'm a liar. I'm still going to discuss the ASICS Cumulus-11, but it is no longer my current running shoe.

I purchased the Cumulus-11 based on my love of the Cumulus-10, without really trying them. This turned out to be a mistake. The Cumulus-11 is a fine update to the Cumulus-10; however, the changes are better for some runners than others.

The heel of the Cumulus-11 is noticeably firmer than that of the 10. Because of this change, I no longer get adequate compression and cushioning from these shoes. These shoes are not as firm as the Tailwinds previously reviewed either and are closer to the Cumulus-10 than to the Tailwinds. I never had the feeling of running in clogs with the Cumulus-11, but they were firm enough that old injuries were aggravated.

The Cumulus-11 is still on store shelves (at least it was at Fleet Feet this past weekend) and should also be available on-line through retailers such as EastBay. I recommend this shoe to a runner who liked the feel of the Cumulus-10 but had issues with it being too soft.

Next time, we'll discuss my current running shoe, the Nike Vomero+ 4. No really, I have three pairs of these to burn through, I'll be using them for a while.

[/running/reviews] [permanent link]

Product Review: ASICS Cumulus-10
This is the second installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my training has turned me into a liar. I'm still going to discuss the ASICS Cumulus-10, but it is no longer my current running shoe.

At this point, the Cumulus-10 can still be found, although supplies are limited. I recently tried to purchase a second pair of these and was unable to find them in my size. I could have had a 9.5 or a 12, but not the 10.5 I needed.

When the Nike Tailwinds no longer provided adequate cushioning, I had to find a new shoe, one that would work for a lighter runner. After reading reviews online and in magazines, particularly Runner's World, I went over to Fleet Feet in Montclair and talked to the sales staff there.

After trying on a few pairs, I decided on the Cumulus-10 but wanted to wait until after the Brooklyn Half Marathon, a week away, before breaking in new shoes. This is not what happened. Because of the lack of cushioning in the Tailwinds, I ended up with horrible shin splints during my lunch time run the day before Brooklyn. I called up fleet feet, asked them to hold a pair of the Cumulus-10s for me and I picked them up that evening. I ran in them for the first time the next morning in the Brooklyn Half.

Those shoes were amazing. They were soft enough to provide the compression needed for good cushioning at my weight. And while they were soft, they weren't mushy either. The ASICS GEL cushioning system is in place in both the heel and the forefoot, providing ample shock absorption for heel strikes and mid- to fore-foot strikes.

The toe box was slightly narrow, but starting the laces one hole up from the bottom provided enough extra space while keeping my foot firmly in place.

The sole in the forefoot is wide; wider than the sole in the Tailwinds. This provides support for the foot during the toe-off portion of the stride.

The Cumulus-10 served me well until I had put just under 600 miles on them. At that point the cushioning was worn down and not as effective as it once was. I retired them about a week after the NYC Half Marathon in August giving me about 12 weeks worth of running. In actuality, I should have retired them after about 10 weeks.

I recommend the ASICS Cumulus-10 for lighter runners with normal to low arches. Left over stock of the Cumulus-10 can be found at EastBay's website for $69.99 (both men's and women's), although many sizes are unavailable at this time.

Next time, we'll discuss my current running shoe, the ASICS Cumulus-11. I've been slacking a bit so I only have about 250 miles on this pair so far. Hopefully I'll post the review before I hit 500 miles and retire these.

[/running/reviews] [permanent link]

Product Review: Nike Tailwind 2008
Welcome to a new feature on this blog. I'm going spend some time writing what I think of various running related items such as shoes, clothes, and energy gels.

My first review is the Nike Tailwind 2008 running shoe. At this point, they're a little hard to find as they have been replaced by the Tailwind 2009. From what I've read about the 2009 edition, not much has changed so much of this should still be relevant.

What first drew me to this running shoe was the Air Max cushioning. Like many Nikes, the heel contained the Air pockets. Unlike many other Nikes, these also had the Air Max cushioning in the forefoot.

I tried them on and they were snug, but not too tight. Perfect. They were already on sale by time I was buying them. Even better.

I ran about 400 miles in my first pair in about six months time, and replaced them with another pair which lasted about another four months. During this time the shoes served me well on treadmills as well as road and trail courses.

These shoes, however, are best for heavier runners. The cushioning is very firm and needs extra weight to compress properly for maximum impact absorption. When I first started wearing the Tailwinds, I was about two months into my training and was about 210lbs. As I ran more, I lost more weight. At 180lbs the shoes were still quite good. At 160lbs they still provided adequate cushioning, although I started to feel my runs more.

The Tailwinds served me well until I was under 140lbs. Below that and they feel like running in clogs.

I recommend the Nike Tailwinds for heavier runners with normal to low arches. The men's Tailwind 2009 can be found on the EastBay website for $79.99 (99.99 for women's) as of this writing, making them a relatively affordable running shoe.

Next time, we'll discuss my current running shoe, the ASICS Cumulus-10.

[/running/reviews] [permanent link]