The Empirical Manifesto

To install OpenBSD on a softraid mirror:

Boot from CD then drop to a shell (s)

# sysctl hw.disknames

(sd0 for SCSI devices, wd0 for IDE devices)

# cd /dev/
# sh MAKEDEV sd0 (or wd0)
# sh MAKEDEV sd1 (or wd1)

# fdisk -iy sd0 (or wd0)
# fdisk -iy sd1 (or wd1)


# disklabel -E wd0
Label editor (enter '?' for help at any prompt)
[s,w]d0> a <-- select partition a
partition [a]
offset: [64]
size: [16771796]
FS type: [4.2BSD] raid <-- enter fs type raid
> q
Write new label?: [y]

# disklabel [s,w]d0 > dumplabel
# disklabel -R [s,w]d1 dumplabel

# bioctl -c 1 -l [s,w]d0a,[s,w]d1a softraid0 <-- -c 1 for RAID1, -c 0 for RAID0
sd0 at scsibus1 targ 1 lun 0: SCSI2 0/direct fixed
sd0: 10236MB, 512 bytes/sector, 20964233 sectors
softraid0: SR RAID 1 volume attached as (sd0 for IDE devices, sd2 for SCSI devices)

# bioctl -h sd[0,2] <-- for status

CTRL-D to exit ^D

Then (I)nstall to your new RAID device [s,w]d0!

TO REPLACE A FAILED DRIVE:

Insert new disk

vopenbsd# bioctl -h sd0                                                                                                         
Volume      Status               Size Device  
softraid0 0 Degraded             8.0G sd0     RAID1 
          0 Online               8.0G 0:0.0   noencl 
          1 Offline                0B 0:1.0   noencl <>

# sysctl hw.disknames

# cd /dev/

# sh MAKEDEV sd2

# fdisk -iy sd2

# disklabel sd1 > dumplabel
# disklabel -R sd2 dumplabel

bioctl -R /dev/sd2a sd0
softraid0: rebuild of sd0 started on wd0a

vopenbsd# bioctl -h sd0                                                                                                         
Volume      Status               Size Device  
softraid0 0 Degraded             8.0G sd0     RAID1 
          0 Online               8.0G 0:0.0   noencl 
          1 Rebuild              8.0G 0:1.0   noencl 

---

Thanks to Claud Computing

The ADC is on I-30 and 360. My client location is on I-20 and I35W. I've been taking I30 to I35W to I-20. That's quick and efficient. However, here lately, I've been traveling 360 to I-20 and coming straight across. There's less traffic, and it seems quicker. But less traffic means less radar clutter to get lost in as I traverse all 3 lanes at 85mph. Its a lot like pod racing. There's 4 lanes on I20, fewer vehicles, hence I drive slower. Slower but at a more consistent speed. Further evaluation needs to be done to determine the quickest route.

Fixed my SB100 problem. Apparently the Symbios SCSI interface card could not simultaneously send LVD and SE data across both the VHCDI ports, so I added a Qlogic SCSI interface card and attached the LVD array to that and the SE DLT's to the Symbios. Problem solved. Now I'm working a samba issue on a Red Hat box. I think this is the first time I've ever logged into Red Hat. This client loves them some Red Hat on vmware. Someone apparently installed samba, but not swat, on this box, and it appears to be a install-time option. So I'm downloading a Red Hat RPM of samba. Yes, I know swat is a crutch for the smb.conf file, but these people have samba installed on every unix box here, cross mounted to every windows desktop. Someday I'm going to create ONE samba server and ONE nfs server. But not today.

I was supposed to get a dual P4 3.0GHz *MB cache workstation to replace my aging laptop. Today the boss asks me to justify the purchase. I told him, "Forget it. You had offered it and I jumped on it." It looks like the Dell laptop POS stays. I had wanted the increased speed and memory configuration to run a varity of operating systems, possibly with a base OS of FreeBSD, but I don't need this drama in my life.

Tony crapped out on the couch last night while I watched White Chicks. I haven't laughed that much in a long time. Odd, the spell checker recognizes "Free BSD" and "Free-BSD" (which are both incorrect) but not "FreeBSD" which I believe is the correct spelling. Heh, it also suggests 'vaporware' as a replacement for 'vmware'. Funny.