Fun Conversations
The DeLorean often leads to conversations one wouldn't normally expect. Case in point: today I had to call my auto insurance provider for an issue with my daily driver. After taking some info to pull up my account the conversation went something like this:

Agent: Which car is this?
Me: The Pontiac.
Agent: Am I reading this right?
Me: Reading what?
Agent: I'm sorry, do you have a DeLorean?
Me: Yes.
Agent: I never thought I'd see someone with a policy on a DeLorean.
Me: Well, you've insured both of mine...
Agent: You've had two DeLoreans?
Me: Yes.

At that point there were a few more questions and then we got back to the issue which my phone call had been about originally.

[/dmc] [permanent link]

Happy Birthday Aisling!!!!
My DeLorean, #5333, was built in October of 1981. This month, the car will be 35 years old and she looks and handles like the day she came off the assembly line.

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

[/musings] [permanent link]

1381017534
Good night, demonslayers.

==================================================================
This mobile text message is brought to you by AT&T

[/mobile] [permanent link]

1381006292
--_CEEC49CB-DE1D-4A1E-9DFE-114E3B54D3CB_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="Windows-1252"

Test blog

Sent from my Windows Phone=

--_CEEC49CB-DE1D-4A1E-9DFE-114E3B54D3CB_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="Windows-1252"


pe>

=

--_CEEC49CB-DE1D-4A1E-9DFE-114E3B54D3CB_--

[/mobile] [permanent link]

1381005175
Corning is a quaint little town. Looking forward to exploring.

==================================================================
This mobile text message is brought to you by AT&T

[/mobile] [permanent link]

1380987012
test
test

[/mobile] [permanent link]

Removing Windows 7 Boot Loader
Removing the Windows7 boot loader is just like removing the Vista boot loader. The key being running the command

\boot\bootsect.exe /nt52 ALL /force

from the Win7 install DVD. More info at this site.

[/musings] [permanent link]