Tuesday, July 10, 2007

L2S: Process List

When you do a process list on Linux, you get the process in age order. I don't know how Solaris is ordering them. Here's the closest solution so far:

Linux: ps -ef
Solaris: ps -ef | sort -n +2

No Video For You



Here's an experiment that didn't work. The idea was to post video from my phone to the blog. No go. We got the preview image, but no video. Too bad.

Wednesday, July 04, 2007

Independance Day, Baltimore Inner Harbor, Pt4


Horrible, horrible, rain. Heavy winds. Fireworks starts in 20 minutes, but its just too bad to stay. So sad.

Independance Day, Baltimore Inner Harbor, Pt3


The black thing in the middle of the harbor is the launch platform. This means any point along the shore will have a good view.

Independance Day, Baltimore Inner Harbor, Pt2


USS Constitution. They fired one of the cannon earlier, and scared everyone half to death.

Independance Day, Baltimore Inner Harbor


Cloudy day, waiting for nightfall to see the fireworks.

Monday, June 18, 2007

L2S: Determine runlevel

Solaris does not have the runlevel command. Furthermore, they are still using BSD init scripts, thus requiring the system to move from one level to the next. To determine a system's current runlevel:
Linux: runlevel
Solaris: who -r

Sunday, June 17, 2007

Saturday In DC



Driving down Louisianna Avenue.

Thursday, June 14, 2007

Solaris vi Defeated: Part 1

I'm finally making some headway in my downgrade from Linux to Solaris. The biggest productivity killer has been learning to use vi. Don't get me wrong... I've been using vi for over a decade. The problem is that the version used by Solaris is so old that it is missing all but the most basic of functionality.

What has frustrated me the most is that if you strike an arrow key to navigate while in the insert mode, it spluges letters on the screen. This is terminal emulation problem. Solution:
From bash: export TERM=ansi

Next, the annoyance of not knowing whether you're in insert or command mode. This can be fixed with a set option. Solution:
From bash: alias vi='vi +"set showmode"'

(I also chose to implement ignorecase.)

These items will, of course, be lost on exit from the session. I've added these lines to my user's .profile, which gets sourced at login.

It would be nice to be able to map the , , , , , and keys, but I haven't found thier translations yet. I found the function keys:
map #1 :set nu[crtl]-[v][enter]
map #2 :set nonu[crtl]-[v][enter]

Upon pressing F1, the system displays line numbers. In order for the sequence to be automatic, we have to add an "Enter" sequence. This is done by pressing and holding the "Control" key, tapping the letter "V", followed by "Enter". It displays as ^M.

The map and set commands could also be issues on a per session basis, but would be better stored in ~/.exrc.

Wednesday, June 13, 2007

Oops... I Crashed Windows XP Pro

In theory... It should have worked. I installed Fedora 7 on the company laptop without incident, but when I went to install Solaris 10, I didn't have a primary partition for a Solaris /boot. My primary concern was the old issue of an OS not being able to boot if its first sector was beyond 1G.

I tried to use Partition Magic to get generate two primary partitions in front of the WXP install, but it failed with a nondescript error. It could shuffle the NTFS partition, but could not reassign the partition numbers. Sounds like a job for fdisk.

In theory, fdisk only edits the partition table and has no impact on data. Since the NTFS partition was between cylinders 20 and 2039, it should have been a simple case of rebuilding the partition table. Guess what? It didn't work. So, on my fourth day on the new job, I get to take their laptop in and explain that I blew up Windows.

So what went wrong? I'll have to research this, because I've used fdisk a thousand times before, without any problems. A few differences: I've not tried this trick with WXP, and I've never done it under F-7. I'm inclined to think that this is an NTFS issue.