Bellicose Bumpkin

I’ve been posting recently about my problems with Windows and touting Linux. One of the main benefits of Linux is that updates are centrally controlled so that you get updates to the base operating system(Linux) and all the applications as well. This is in contrast to Windows which has one mechanism for keeping Windows itself up to date and applications such as web browsers and email clients are left to fend for themselves.
.
Once a week or so Linux automatically notifies me that updates are ready to install – like it did this morning. In this screenshot you can see updates to the very core of the OS – the kernel and a software development application – Eclipse. Press the button …. done.

Linux Ubuntu Update Manager

   Send article as PDF to

Image courtesy of Metin Seven, Seven's Heaven

If you have supported hardware I would maintain that setting up a Linux workstation is far easier than a Windows one. How many of you have installed Windows? I’d guess not many. If you have you’d know that after the install of the base operating system you don’t have much. You have to install drivers for every piece of hardware you have – printers, cameras, web cams, mp3 players, etc, etc – with many of the installs requiring a reboot. You don’t have any photo editing, music editing, or office suite. You have little more than a web browser(Internet Explorer), a simple text editor(Notepad), and a music/video player(Windows Media Player). When you install Linux – everything is there when you’re done. Install, one reboot, and you have a tremendous wealth of open source applications:

• Office suites
• Web browsers
• Audio editors
• Video editors
• Software development tools(compilers, programming editors, IDE’s
• Music players/management tools
• IM clients
• Internet telephony progrmas
• Image editors
• Photo management tools
• The list goes on and on and on and on

It is very true that if your hardware is not supported out of the box, it can be difficult or impossible to make it work with Linux. If it is supported however, it will be as easy or easier to get it working than Windows. It is also true that if you are setting up a server, you will need some technical chops or a lot of perseverence – but setting up a server under Windows is no picnic either.
.
I think the article had a slightly more negative tone than I would have liked but I think it sums up moving to Linux nicely:

Linux for kids
Once configured – Linux is easy to use. Here is an article titled “10 reasons why your kids should be using Linux”.

   Send article as PDF to

This CNET article discusses the decline and failure of Sun and success of Google based on this central idea:

I would disagree with this. I think Sun’s failure goes back further and gave birth to the child that ended up killing it – Linux.
.
Back when I was a just starting off in software engineering, our product line ran on Apollo’s DomainOS – a great operating system. It was dying out and we were porting to Sun’s Solaris operating system. I was new to Unix and soon developed an appreciation for this complex and powerful environment. Wanting to learn more, I started looking for a version of Unix to run on my home PC – so I could hack on it to my heart’s content without worrying about messing up one my company’s $15K workstations. First stop was Solaris x86 – a version of Solaris that could run on a home PC. As I recall, it was something like $300. Someone told me about Linux and I ordered a CD from TransAmeritech LinuxWare. It was cheap – certainly less thatn $50 and maybe down around $10 or $20 dollars.
.
After a minimum of fuss, I had it installed and I can still remember the first time my home PC booted up with it’s very own Unix-like system … Linux. I’ve been hooked ever since. It came with a compiler, several desktop environments, editors, games, and applications galore. In many ways it was far more usable as a desktop than my $15K Solaris machine. Sure the same applications were availabe but you had to download, compile, and install them yourself.
.
In 1991 when university student Linux Torvalds wanted a unix for his PC, he wrote Linux. Me and millions of other Unix users embraced it because of Sun’s failure to make a free version of Solaris available to home users. The opensource nature of Linux fostered a huge ecosystem that led to rapid development and better distributions and applications. Meanwhile Sun plodded along with their off-again on-again relationship with Solaris x86. Eventually Sun saw the light. They opensourced Solaris and started shipping GNU stalwarts like Perl and Gnome with the operating system — but it was too little to late. Us early Linux adopters were now sitting on top of a mature and totally free powerhouse. It ran on cheap hardware and we were in position to influence our companies to adopt Linux internally. I was one of people pushing to migrate a move to Linux within my company – which we did leaving Solaris behind.
.
That’s my story. Sun didn’t fail because they didn’t embrace Linux on x86 – they failed because they tried to keep all their technological marbles – creating an environment that encouraged Linux to thrive. Me and millions of others never would have touched Linux if Sun had a free or cheap version of Solaris or SunOS for our PC’s. It’s too bad. Sun hardware and OS are rock solid and crazy scalable. The company has been a good opensource citizen(OpenOffice, Mysql), innovative(Java, NFS, ZFX, Dtrace) and I’m sad to see them go.

   Send article as PDF to

So I’m converting my wav recordings of last night’s gig to mp3. Here’s a simple bash command line to convert all wav files in a the current directory to 192k MP3 files. The power of the command line on Linux and Unix-like systems is phenomenal. GUI’s are great but some things are so much quicker and easier on the command line.

 for f in *.wav
> do
> new=`echo $f | sed s/wav/mp3/`
> lame -b 192 "$f"  MP3/"$f"
> done

Terminal showing wav to mp3 conversion

   Send article as PDF to

This post is pure geek. You’ve been warned.

It’s called the oom-killer. Bwahahaha…

I came across this when my virtual machine died while running a build. The /var/log/messages log showed:

May 30 00:02:33 localhost kernel: oom-killer: gfp_mask=0xd0May 30 00:02:36 localhost kernel: cpu 0 hot: low 32, high 96, batch 16May 30 00:02:36 localhost kernel: cpu 0 cold: low 0, high 32, batch 16May 30 00:02:36 localhost kernel: cpu 1 hot: low 32, high 96, batch 16May 30 00:02:36 localhost kernel: cpu 1 cold: low 0, high 32, batch 16May 30 00:02:36 localhost kernel: May 30 00:02:36 localhost kernel: Free pages:       35932kB (19712kB HighMem)May 30 00:02:39 localhost kernel: HighMem free:19712kB min:512kB low:1024kB high:1536kB active:1002148kB                                   inactive:1422792kB present:2488324kB pages_scanned:0                                   all_unreclaimable? noMay 30 00:02:39 localhost kernel: protections[]: 0 0 0May 30 00:02:40 localhost kernel: DMA: 1*4kB 3*8kB 4*16kB 2*32kB 3*64kB 3*128kB 2*256kB 0*512kB 1*1024kB                                   1*2048kB 2*4096kB = 12508kBMay 30 00:02:43 localhost kernel: Free swap:       4176688kBMay 30 00:02:44 localhost kernel: 851457 pages of RAMMay 30 00:02:44 localhost kernel: 622081 pages of HIGHMEMMay 30 00:02:44 localhost kernel: 8252 reserved pagesMay 30 00:02:44 localhost kernel: 748042 pages sharedMay 30 00:02:44 localhost kernel: 2173 pages swap cachedMay 30 00:02:44 localhost kernel: Out of Memory: Killed process 4300 (vmware-vmx

The oom-killer is the Out Of Memory killer and is described here:

There are a number of ways of stopping this:

• Check for low memory exhaustion

  # egrep 'High|Low' /proc/meminfo

  # free -lm

  When low memory is exhausted, it doesn’t matter how much high memory is
  available, the oom-killer will begin whacking processes to keep the
  server alive.

• upgrade to 64-bit linux(not an option for most)
• If limited to 32-bit Linux, the best solution is to run the hugemem kernel. This kernel splits low/high memory differently, and in most cases should provide enough low memory to map high memory. In most cases this is an easy fix – simply install the hugemem kernel RPM & reboot.
• If running the 32-bit hugemem kernel isn’t an option either, you can try setting /proc/sys/vm/lower_zone_protection to a value of 250 or more. This will cause the kernel to try to be more aggressive in defending the low zone from allocating memory that could potentially be allocated in the high memory zone. As far as I know, this option isn’t available until the 2.6.x kernel. Some experimentation to find the best setting for your environment will probably be necessary. You can check & set this value on the fly via:

      # cat /proc/sys/vm/lower_zone_protection    # echo "250" > /proc/sys/vm/lower_zone_protection

  To set this option on boot, add the following to /etc/sysctl.conf:

      vm.lower_zone_protection = 250

• As a last-ditch effort, you can disable the oom-killer. This option can cause the server to hang, so use it with extreme caution (and at your own risk)!

      Check status of oom-killer:    # cat /proc/sys/vm/oom-kill
  
      Turn oom-killer off/on:    # echo "0" > /proc/sys/vm/oom-kill    # echo "1" > /proc/sys/vm/oom-kill
  
      To make this change take effect at boot time, add the following to /etc/sysctl.conf:    vm.oom-kill = 0

   Send article as PDF to