GNU Screen is one of the most useful utilities on a *nix system. On OpenBSD, it’s an installable package (”sudo pkg_add -i screen“) and it’s almost always the first package I install.

Scott (whose blog is not as fast as mine) and I played around with our ${HOME}/.screenrc and Scott helped me come up with this:

shell -$SHELL
startup_message off
defscrollback 1000
hardstatus alwayslastline '%{= wk}%?%-Lw%?%{r}(%{k}%n*%f%t%?(%u)%?%{r})%{k}%?%+Lw%?%?%= %m/%d %C%A'
activity ''
termcapinfo xterm* 'hs:ts=\\E]2;:fs=\\007:ds=\\E]2;screen\\007'

(more…)

I’ve been using my IBM Thinkpad T42p as a desktop at home a lot more lately (almost exclusively) and it works great! Just about all of the hardware works (dmesg) — I can’t think of any that doesn’t. It’s a reasonably fast machine, suspend works, audio works, wifi works…

As for my desktop environment, I’ve started using dwm because it’s extremely small, fast and easy to use with just keystrokes. Windows can be assigned tags which are like workspaces in other managers. There are 9 available tags. I usually have a full-screen xterm running screen on my local machine in tag 1, a full screen xterm running ssh to another box running screen in tag 2 (this screen session has mutt and irssi running in it along with other sessions I like to keep active all the time) and a full screen Firefox in tag 3.
(more…)

I’ve been playing with OpenBSD -current on my MacBook Pro. View the dmesg output.

Not all of the hardware works. Most notably: the ATI Radeon Mobility X1600, wireless, Fn key and acpi/apm.

I can get X working with the VESA driver at 1024×768 (xorg.conf).

So, I cannot right-click, recording through the azalia sound driver is not working (though deanna@ is making great strides with the Mac audio capabilities), none of the Fn-Fx keys (sound, brightness, …) are working, I cannot suspend or get any power status. But, it’s a fast, fast, fast build machine. :)