Thursday, November 20, 2014

Sudo on Minix 3.1.8

Minix 3.3.0 came out a while ago and I had all kinds of fun playing with it.  I'd long been running 3.2.1 but never gave 3.1.8 a try at all.  The fun I had with 3.3.0 got me motivated though and a few weeks back I gave it a shot.

It was fairly straightforward, for the most part.  A few things here and there reminded me of 2.0 but the overall user experience was similar to 3.2.1.  Getting various bits of software running required many of the same tweaks that 3.3.0 and 3.2.1 required, but the most difficult bit by far was sudo.

Sudo 1.7.something-or-other is available via pkgin but it dumps core whenever you do anything with it.

Sudo version 1.6.9p23 has been reliably portable for me though, so I gave it a try.  It took a while to work around various issues, but eventually I got it working.  If anyone out there is interested, here are the tricks:

The code requires a little hackery.

Add the following line after the includes in interfaces.c

#define IFF_LOOPBACK IFF_UP

Edit sudo.tab.c and comment out:

# include <search.h>

it should look like this when you're done:

/*# include <search.h>*/

Minix 3.1.8's implementation of getgroups always returns -1.  This causes a few problems for sudo.  To solve them, edit set_perms.c and make 3 modifications.

Make the declaration of runas_groups (around line 376) look like:

static GETGROUPS_T *runas_groups = NULL;
Update a section of the function runas_setgroups() as follows:

...
    if (runas_ngroups <= 0) {
        pw = runas_pw ? runas_pw : sudo_user.pw;
        if (initgroups(pw->pw_name, pw->pw_gid) < 0)
            log_error(USE_ERRNO|MSG_ONLY, "can't set runas group vector");

        if ((runas_ngroups = getgroups(0, NULL)) > 0) {
            runas_groups = emalloc2(runas_ngroups, sizeof(GETGROUPS_T));
            if (getgroups(runas_ngroups, runas_groups) < 0)
                log_error(USE_ERRNO|MSG_ONLY, "can't get runas group vector");
        }

    } else {
...

Update the function restore_groups() as follows:

static void
restore_groups()
{
    if (user_ngroups > 0) {
        if (setgroups(user_ngroups, user_groups) < 0)
            log_error(USE_ERRNO|MSG_ONLY, "can't reset user group vector");
    }
}

That third modification is actually a workaround for a bug (or feature) in setgroups().  It goes completely haywire if user_ngroups is -1.  I'll bet that this is the problem that the version of sudo available via pkgin has too.  There might be a libc update that fixes this issue but for now we'll just work around it.

Now build and install.  Some options needs to be enabled in the header files with the _POSIX_SOURCE macro, so we'll pass that in.  I also like to install it under it's own directory tree, so I use the --prefix option for that.

CPPFLAGS="-D_POSIX_SOURCE" ./configure --prefix=/usr/local/sudo-1.6.9p23
make
su
make install

The default permissions are wrong for Minix though, so they need to be set manually:

chmod 555 /usr/local/sudo-1.6.9p23/bin/sudo
chmod u+s /usr/local/sudo-1.6.9p23/bin/sudo

Now add a line for your user (dmuse in my case) to /etc/sudoers.

dmuse ALL=(ALL) NOPASSWD: ALL

Yes, the sudoers file is installed under /etc independent of the --prefix option used earlier.  The NOPASSWD option makes it so you don't have to enter a password.

And the last step is to add /usr/local/sudo-1.6.9p23/bin to your PATH in ~/.ashrc

export PATH=$HOME/bin:/usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin:\
/usr/pkg/X11R6/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/llvm/bin:\
/usr/local/sudo-1.6.9p23/bin

And that's it.  Re-login and sudo should work as expected.

$ sudo ls -l /
total 44
drwxr-xr-x  2 root  operator   2880 Sep  4  2010 bin
drwxr-xr-x  3 root  operator    384 Sep  4  2010 boot
drwxr-xr-x  2 root  operator  29120 Sep 20 02:47 dev
drwxr-xr-x  3 root  operator   2304 Nov 20 22:53 etc
drwxrwxrwx  5 bin   bin         320 Sep 20 02:55 home
drwxrwxrwx  2 root  operator    128 Sep 20 02:45 mnt
drwx------  2 root  operator    768 Sep 20 04:09 root
drwxr-xr-x  2 root  operator    896 Sep  4  2010 sbin
drwxrwxrwt  2 root  operator    640 Nov 20 23:52 tmp
drwxrwxrwx 23 bin   bin        1536 Sep 20 03:27 usr
drwxr-xr-x  3 root  operator    256 Sep 20 02:45 var

Woohoo!  Sudo on Minix 3.1.8.

Thursday, October 23, 2014

Solaris 2.6 x86

Introduction

If you search eBay for "Solaris" you'll find a lot of people selling old copies of 2.6, but all of these copies are for the SPARC platform. 2.6 for Intel was alleged to exist, but after leaving a fruitless search going for months and months, I started to wonder if it was a myth.

And then, one day, out of the blue, something turned up. It was too good to be true. I didn't believe it at first. But there it was. Solaris 2.6 for Intel.

Woohoo!

When it came in the mail, I was even happier. The packaging might have been reused from something else, but boy was it cute.

solaris 2.6 - 1. packaging

Also, the shipper included a little note on cat-themed stationery thanking me for my purchase, AND refunding me my change from shipping! kri-bri - best seller ever.

I was so wrapped up admiring the packaging that I almost forgot about what was inside. But there it was, the mythical Solaris 2.6 for Intel, shiny and still shrink-wrapped.

solaris 2.6 - 2. box

It almost felt wrong to open it. "Fortunately" I didn't have to right away. I was really busy at the time so all I could do for a week or more was put it on the shelf and wait for a break.

VM Configuration

(Two Weeks Later)

Not terribly long ago I'd managed to get the unexpectedly less-rare Solaris 2.5.1 x86 running in VMware 8.0.6. It had required jumping through a few hoops. Even longer ago I'd installed Solaris 7 x86, and in comparison, it had required jumping through flaming hoops while riding a unicycle. I was curious where 2.6 would fall on this spectrum and a little nervous that it might require some set of new gymnastics.

Turned out there were few surprises.

Through trial and error I discovered that 2.6 only supports about a 4G disk. Or, at least that a 4G disk image works but an 8G does not. You can install to an 8G disk, but you can't boot from it after installation. Or at least I couldn't get that to work. So, 4G disk.

128mb of memory seemed to be enough. I told VMware that the guest OS was Solaris 8. I removed the sound card, and aimed the virtual floppy at the Solaris Device Configuration Manager image.

Installation

Right away I got an odd error:

    Loading driver blogic.bef
Failed to initialize host adapter

It looked like Solaris wasn't too happy with VMware's Buslogic implementation. My virtual drives were on the virtual IDE controller though, and it turned out I could just hit return to keep going.

The rest of the installation was straightforward-ish. It was a lot like other Solaris installations, with some of the same quirks. It didn't ask for DNS info or a default route. Several times it tried to get me to run kdmconfig and I had to either Bypass or Bypass and Suppress it.

The oddest thing was disk partitioning, but it was no odder than usual. In fact it was exactly the same as 2.5.1 and 7. You have to uncheck and re-check c0d0 (c-zero d-zero) or the installer will think that it has partitions defined even though it doesn't. Also, the default filesystem layout includes a small root and large /export/home and the editor for removing /export/home and resizing root isn't very intuitive.

But I was used to that, did that, and pretty soon it looked like this:

solaris 2.6 - 2. install

The main installer ran for a while, then it appeared to install some updates. I'd told it to not to auto-reboot so I'd be able to remove the floppy. When it was done it dropped me to a root prompt, I removed the floppy, halted the system and rebooted.

solaris 2.6 - 3. first boot

All right!

Post-Install Tweaks

Everything wasn't perfect yet though.

Even though I'd bypassed and suppressed configuration of the graphical environment it still tried to start anyway, so I disabled it for real.

dtconfig -d

Fortunately the emulated PCNet NIC was recognized (unlike in 2.5.1), but the installer didn't ask for a default route or DNS info so I configured that manually too.

Default route:

echo "192.168.123.254" > /etc/defaultrouter

/etc/resolv.conf

domainname firstworks.com
nameserver 192.168.123.37
search firstworks.com

/etc/nsswitch.conf

hosts: files dns

I rebooted after that step to make sure everything network-related came back up correctly on restart, and it did.

The default path didn't include some important stuff, so I updated /etc/profile

PATH=$PATH:/usr/ccs/bin:/usr/ucb:/usr/openwin/bin:/usr/openwin/demo:/usr/dt/bin
...
export LOGNAME PATH

I'd told the installer not to create a /export/home partition, but if you don't create the partition then the directory doesn't even get created. This is where home directories are created by default though, so I added it.

mkdir /export/home

I also added a user for myself.

useradd -m -d /export/home/dmuse dmuse
passwd dmuse

And I added /usr/local and /opt/sfw because I intended to install some software in those locations later.

mkdir /usr/local
chmod 777 /usr/local
mkdir /opt/sfw
chmod 777 /opt/sfw

As with Solaris 2.5.1 and 7, software was difficult to come by. There's plenty of source code out there but what was I going to compile it with?

Also as with 2.5.1 and 7, the solution was to build a compiler targeted for 2.6 on a different version of Solaris. This time I built gcc 2.95.3 on Solaris 9. I first tried building on 11 and 10 but the versions of gcc that I had installed on those systems appeared to be too new to build 2.95.3.

On Solaris 9, I ran:

./configure --prefix=/usr/local/gcc-2.95.3 --host=i386-pc-solaris2.6 --target=i386-pc-solaris2.6 --enable-shared
gmake
gmake install

Then I tarred up /usr/local/gcc-2.95.3, ftp'ed it over to the 2.6 VM, untarred it in /usr/local and added /usr/local/gcc-2.95.3/bin to my PATH.

As if by magic, I could now build software in my 2.6 VM.

Magic!

Software

Now that I had a working compiler, I rebuilt gcc natively and installed it under /opt/sfw.

CC=gcc ./configure --prefix=/opt/sfw --enable-shared
make
make install

I removed /usr/local/gcc-2.95.3, removed it from my path, added /opt/sfw/bin to my path (and /opt/sfw/lib to my LD_LIBRARY_PATH) and used the new gcc to build a bunch of other stuff: gzip-1.3.12, bash-1.14.7, sudo-1.6.9p23, perl-5.003_07, openssl-0.9.6h, zlib-1.2.8, openssh-3.1p1, GNU tar-1.13, apache-2.0.65, lynx-2.8.7, wget-1.5.3, cvs-1.11.23, GNU make-3.82, vim-7.4... Maybe some other stuff too.

I configured everything to install under /opt/sfw and just about everything compiled cleanly.

openssh required line 58 of openbsd-compat/bsd-snprintf.c to be commented out:

/*# undef HAVE_VSNPRINTF*/

I think that was all though.

Remote Access

It's fun to work on the console for a while, but it does get old. After building and installing openssh, I created an init script for it at /etc/init.d/ssh

#!/bin/sh

case "$1" in
  start)
        /opt/sfw/sbin/sshd
        ;;
  stop)
        killall sshd
        ;;
  *)
        echo $"Usage: $0 {start|stop}"
        exit 1
esac

exit 0

...and set it up to run at boot:

chmod 755 /etc/init.d/sshd
cd /etc/rc3.d
ln -s ../init.d/sshd S90sshd

I tried enabling X-Forwarding in /opt/sfw/etc/sshd_config

X11Forwarding yes

...but for whatever reason it never worked.

But, after starting ssh

/etc/init.d/sshd start

I could log in remotely.

solaris 2.6 - 4. ssh

I could also scp files back and forth.

The Web

I'd built and installed lynx and wget earlier and they both worked as expected.

Netscape 4.78 was available and worked but struggled hilariously with modern websites.

solaris 2.6 - 5. netscape

It did support PNG's though, which I didn't expect.

The hotjava web browser was also available but it struggled even more. Side note though... I think Solaris 2.6 was the first version to support java (version 1.1.3 no less), or at least to ship with support for it.

On the server side, I was able to get Apache working but I had to do the same Group trick that I did under Solaris 7. By default, Apache is configured to run as Group #-1. On most systems, group id's are 16-bit, -1 translates to 2^16-2, and the "nobody" group has that group id. Apparently, on Solaris, group id's are 32-bit, "nobody" has an id like 60001, and it couldn't make any sense of #-1. This fixed it though:

#Group #-1
Group nobody

I added an init script for it too, at /etc/init.d/httpd

#!/bin/sh

case "$1" in
  start)
        /opt/sfw/bin/apachectl start
        ;;
  stop)
        /opt/sfw/bin/apachectl stop
        ;;
  *)
        echo $"Usage: $0 {start|stop}"
        exit 1
esac

exit 0

...and configured it to run at boot.

chmod 755 /etc/init.d/httpd
cd /etc/rc3.d
ln -s ../init.d/httpd S90httpd 
X Windows

Solaris 2.6 comes with Sun's X server but it doesn't support VESA framebuffers so under VMware it's limited to 16-color VGA mode at 640x480.

But!

Binaries of XFree86 4.7.0 are available for Solaris 2.6 at http://ftp.xfree86.org/pub/XFree86/4.7.0/binaries/Solaris. And they work!

They do take a little coercion though.

To get it working, I downloaded the following files:

    Xbin.tgz
    Xdoc.tgz
    Xetc.tgz
    Xf100.tgz
    Xfcyr.tgz
    Xfenc.tgz
    Xfnts.tgz
    Xfscl.tgz
    Xfsrv.tgz
    Xhtml.tgz
    Xinstall.sh
    Xlib.tgz
    Xman.tgz
    Xmod.tgz
    Xnest.tgz
    Xpdf.tgz
    Xprog.tgz
    Xprt.tgz
    Xps.tgz
    Xrc.tgz
    Xvfb.tgz
    Xxserv.tgz
    extract 

Then I ran:

sudo sh Xinstall.sh

The prompts were intuitive and I installed all optional components but I told it not to create links for opengl or rstart.

I also added /usr/X11R6/bin ahead of other paths in the PATH variable and added /usr/X11R6/lib ahead of other paths in the LD_LIBRARY_PATH variable.

Configuring XFree86 (xf86config) took some trial-and-error but I eventually got it. The important settings are:

  • mouse protocol: 1. Auto
  • monitor: 2 31.5 - 35.1; Super VGA, 800x600 @ 56 Hz
  • vertical sync range: 4 40-150
  • yes, look at a card database
  • card: 0 * Generic VESA compatible
  • video memory: 3 1024K
  • color depth by default: 4 16 bits (65536 colors)

The color depth appears to have to be the same as the depth of the host display.

After configuration the mouse didn't work, but editing /etc/X11/XF86Config manually and commenting out the following line seemed to fix it:

    #Option "Device"      "/dev/mouse"

After all that I was able to get a simple X session running with startx.

Running openwin gave me an OPENLOOK session.

solaris 2.6 - 7. openwin

I was able to get a CDE session by creating an .xinitrc with:

/usr/dt/bin/Xsession

...and running startx.

solaris 2.6 - 8. cde

A graphical login was a little more difficult.

It turns out that the dtlogin program runs /usr/openwin/bin/Xsun directly, and passes it an option that the XFree86 server doesn't understand, so I replaced it with a script that removes the option:

#!/bin/sh

ARGS=`echo $@ | sed -e "s|-nobanner||g"`

/usr/X11R6/bin/X $ARGS

I'd had the same issue with Solaris 7 though, so the solution was familiar.

Enabling dtlogin was simple.

dtconfig -e

It didn't work perfectly though. As on Solaris 7, I could login and run a CDE session, but I had to use ctrl-backspace to exit the session and get back to the login.

Development

I had previously built and installed all the tools I usually use to build my software, so I gave it a try.

Rudiments required one modification. I'd added a hack at some point for FSU pthreads on SCO something-or-other, but then later disabled FSU pthreads support but forgot to remove the hack. The hack caused a problem on Solaris 2.6 and removing it solved it.

Everything else built cleanly and I was able to run the SQL Relay client software.

solaris 2.6 - 9. sqlrsh

I'd really like to get the SQL Relay server running on Solaris though.

I'm still looking for a version of Oracle or Sybase or DB2 or something that'll run on older Solaris x86. I remember seeing Oracle 8.0.5 on eBay once, but only once. I guess I should have jumped on it then.

I probably should try to build MySQL, PostgreSQL, Firebird and SQLite. I'm not sure how much work that would be but if I could get it going then it'd at least be something.

Eh, something to work on later.

Endearing Features

Solaris 2.6 has the standard set of Solaris quirks: you have to use delete for backspace on the console, home directories are created in /export/home, the default shell doesn't understand ~/, filesytem performance is not so good under VMware (untarring and rm -rf'ing take a while) and setting the domain in /etc/resolv.conf requires the "domainname" keyword rather than "domain".

2.6 also only supports 4g disks, which make sense, given its vintage - 1998. Unfortunately it also makes host cpu run at 100%. I can't say that was unexpected either though, as both 2.5.1 and 7 do the same.

So there you have it. Solaris 2.6 x86. About what I expected. Not too surprising. Not too disappointing.

I'll have to try to get more software running on it though - databases, maybe some old java. Yeah, that would be fun.

Friday, September 19, 2014

Minix 3.3.0 x86

Introduction

It's all over the web... Minix 3.3.0 is out! And it's got a long list of improvements over 3.2.1, not the least of which are support for shared object libraries and ARM platforms.

In case you don't know much about Minix, Wikipedia can do a much better job describing it and microkernels and the famous debate over microkernels vs. monolithic kernels than I can. So I'll leave that to them.

I love new software, almost as much as I love old software, so for that past few days, I've been giving Minix 3.3.0 a spin.

Installation

The 3.3.0 iso is available at http://download.minix3.org/iso/minix_R3.3.0-588a35b.iso.bz2. I downloaded it from there, aimed my (admittedly aging) VMware 8.0.6 at it, and let the magic happen.

The VM configuration was straightforward. I gave it a 2G disk image, 256M of ram, and removed the devices I didn't intend to use, like the floppy, sound card and printer.

The Minix installation was as simple as powering on the VM and following the directions. Log in as root (with no password), run "setup", choose "automatic mode"... the directions are explicit and the process is intuitive.

Minix 3.3.0 x86 - 1. install

The only marginally tricky step is if you manually configure ethernet, make sure to give the fully qualified domain name (eg. minix330x86.firstworks.com rather than just minix303x86) or later if you install apache, it will complain that it can't determine the fully qualified domain name.

Upon reboot, I seemed to have a working system.

Minix 3.3.0 x86 - 2. first boot

Post-Install Tweaks

...but it turned out that I did have to configure a few things manually.

The installer didn't ask me for my domain name and didn't extract it from the hostname, so I added a search command to /etc/resolv.conf.

# Use Minix nonamed for now
nameserver 127.0.0.1
search firstworks.com

The system didn't appear to know its hostname either, which turned out to be the result of duplicate entries in /etc/hosts. Commenting out the line that correlated the system's IP with %nameserver fixed that.

#192.168.123.157        %nameserver     #minix330x86.firstworks.com
192.168.123.37  %nameserver     #DNS 1

192.168.123.157 minix330x86.firstworks.com

I also gave root a password, updated pkgin, installed openssh...

# passwd
Changing local password for root.
New password:
Retype new password:
# pkgin update
...
# pkgin install openssh
...

...and rebooted again to enable ssh.

Adding a User

Adding a user was straightforward:

useradd -m dmuse
passwd dmuse

I could log in as me now and access the VM via remotely but I can't live without sudo and pkgin didn't have any idea what I was talking about when I tried to install it.

# pkgin install sudo
sudo is not available on the repository
calculating dependencies... done.
nothing to do.

Hmmm... Yeah, I remember that from 3.2.1 too.

I've built sudo from source on a bunch of systems though, perhaps it could be built on Minix too. I never tried on 3.2.1, I just used root for everything. Sad, I know.

Turns out, yes, you can build sudo from source, but it takes a little effort.

First, you need a compiler. The documentation alleges that gcc and clang are both available but gcc isn't on the CD and pkgin didn't appear to know anything about a native gcc toolchain. Surprisingly, it knew about a mingw32 cross-compiler, but nothing native. It did know about clang though, so I gave it a try.

# pkgin install clang
...
# pkgin install binutils
...

Sudo version 1.6.9p23 has worked well for me on various old RedHat and Solaris platforms, so I tried building it. It needed a little coaxing, but only a little.

First off, configure had never heard of clang so I created some symlinks.

# cd /usr/pkg/bin
# ln -s clang cc
# ln -s clang++ c++

I also had to edit interfaces.c and add a line like:

#define IFF_LOOPBACK 0x8

after the includes. Minix doesn't define an IFF_LOOPBACK flag and after looking at the code, it appeared harmless to define it. After that, sudo built and installed smoothly.

$ ./configure --prefix=/usr/local/sudo-1.6.9p23
configure: Configuring Sudo version 1.6.9
...
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
...
$ make
cc -c -I. -I. -O2 -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440  check.c
cc -c -I. -I. -O2 -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440  env.c
cc -c -I. -I. -O2 -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440  getspwuid.c
cc -c -I. -I. -O2 -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440  gettime.c
...
cc -o sudo check.o env.o getspwuid.o gettime.o goodpath.o fileops.o find_path.o  interfaces.o logging.o parse.o set_perms.o sudo.o sudo_edit.o  tgetpass.o zero_bytes.o  sudo_auth.o passwd.o sudo.tab.o lex.yy.o alloc.o defaults.o   -lcrypt  
cc -c -I. -I. -O2 -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440  visudo.c
cc -o visudo visudo.o fileops.o gettime.o goodpath.o find_path.o zero_bytes.o  sudo.tab.o lex.yy.o alloc.o defaults.o
$ su
Password:
# make install
...

And I added /usr/local/sudo-1.6.9p23/bin to the PATH environment variable in /etc/profile and added a line for myself at the end of /etc/sudoers...

dmuse ALL=(ALL) NOPASSWD: ALL

...but it didn't work. Turns out on Minix, programs need read and execute permissions to run. Execute alone isn't good enough.

# cd /usr/local/sudo-1.6.9p23/bin
# chmod 555 sudo
# chmod u+s sudo

Ha! That made it work.

$ sudo ls /
bin          boot_monitor home         proc         service      usr
boot         dev          lib          root         sys          var
boot.cfg     etc          mnt          sbin         tmp

Woohoo!

Remote Access and File Transfer

Minix 3.3.0 was looking pretty good from a remote access and file transfer standpoint, at least from the command line.

I could ssh in and out, transfer files with scp, sftp and regular ftp. Wget and lynx were available from pkgin. Tar, gzip, bzip2 and unzip were all installed by default. Zip wasn't but it was available from pkgin.

Ping was installed by default, but oddly telnet wasn't and it also wasn't available from pkgin. It's difficult to track down some connectivity issues without telnet, but I hoped I wouldn't need it.

The Web

Apache was available via pkgin, version 2.0.65nb2 to be precise. I installed it but it wouldn't start. After digging through the logs I eventually discovered that it needs the directory /usr/pkg/var/run to exist. After creating that, it ran just fine.

I did have trouble getting it to run cgi's. I configured it the same way I've configured it dozens of times before, but it just wouldn't work. The mod_cgi module didn't appear to be installed and didn't appear to be linked in statically either.

Between this and gcc, I got to looking around in the pkgin repository a little. Several apache modules were in there, but many more were missing. Other odd combinations of things were in there too. For example, various firefox language packs were available, but firefox itself wasn't. Hmm... This release just came out. I'll bet that some packages still need a little patching and so they and everything that depends on them isn't getting built yet. Maybe in a few weeks or months more will be available.

X Windows

X was a total loss. It wasn't installed as part of the base distribution, no x11 package was available and attempts to aim pkgin at the 3.2.1 repository failed pretty badly too.

I guess I could have tried building from source. Maybe later. Or maybe if I wait a few weeks or months a package will just appear one day.

Development

I had working C and C++ compilers, and Minix 3.3.0 alleged to support shared object libraries.

I was itching to try and get my software running.

Almost immediately I ran into trouble though. CVS wasn't available through pkgin. Fortunately version 1.11.23 built cleanly from source. Then there were issues with libtool, and clang throws a lot more warnings that gcc, and there were goofy problems with threads, and Minix doesn't like it if you use ioctl to set blocking/nonblocking IO on sockets, you have to use fcntl.

That sounds like a lot but as usual, though it took a while to track down solutions, in the end it just took some minor tweaks to the Rudiments library and a few even more minor tweaks to my build script to get the SQL Relay client software running.

Minix 3.3.0 x86 - 3. sqlrsh

Look at that, accessing an Oracle database from Minix. Who'd have thought it was possible?

And look at that:

$ ldd /usr/local/firstworks/bin/sqlrsh
/usr/local/firstworks/bin/sqlrsh:
        -lsqlrutil-0.57.1 => /usr/local/firstworks/lib/libsqlrutil-0.57.so.1
        -lrudiments-0.48.1 => /usr/local/firstworks/lib/librudiments-0.48.so.1
        -lmthread.0 => /usr/lib/libmthread.so.0
        -lpthread.20 => /usr/pkg/lib/libpthread.so.20
        -lc.12 => /usr/lib/libc.so.12
        -lssl.1.0.0 => /usr/pkg/lib/libssl.so.1.0.0
        -lcrypto.1.0.0 => /usr/pkg/lib/libcrypto.so.1.0.0
        -lpcre.1 => /usr/pkg/lib/libpcre.so.1
        -lcrypt.1 => /usr/lib/libcrypt.so.1
        -lc++.1 => /usr/lib/libc++.so.1
        -lm.0 => /usr/lib/libm.so.0
        -lsqlrclient-0.57.1 => /usr/local/firstworks/lib/libsqlrclient-0.57.so.1
        -lreadline.6 => /usr/pkg/lib/libreadline.so.6
        -lterminfo.1 => /usr/lib/libterminfo.so.1
        -lhistory.6 => /usr/pkg/lib/libhistory.so.6

Dynamic linking! On Minix!

PostgreSQL was available from pkgin too, so I installed it and SQL Relay compiled against it just fine, but I couldn't get the SQL Relay server to run because the kernel wasn't compiled with support for semaphores. Shared memory, yes. Semaphores, no.

$ ipcs

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status

kernel not configured for semaphores

Grrr.

This caused problems on reboot too, when the PostgreSQL server tried to run.

I figured I'd try recompiling the kernel with support for semaphores, but I couldn't find the kernel source anywhere. It wasn't installed, it's not hidden away on the CD, and it's not available via pkgin. How does one get a hold of the Minix 3.3.0 kernel source? If somebody knows, please clue me in.

Conclusions

Minix 3.3.0 seems to run a bit more smoothly than 3.2.1. Now that I think about it, I can't remember exactly what problems I had with 3.2.1, but it seems like I had problems running certain programs after ssh'ing in and then su'ing and also running out of memory from time to time. I didn't run into any trouble like that at all with 3.3.0. For certain, 3.3.0 is at least as stable as 3.2.1.

I was able to tune it down to 96M of RAM too and everything continued to run fine, even software builds. I might even be able to tune it down more.

Lack of X, gcc and other packages was a drag, but I expect that they'll be available eventually. Fuel for another article, I guess.

Lack of built-in support for semaphores and lack of kernel source was a serious drag. The source has got to be available somewhere though. Maybe I'll find it if I dig a little bit.

Of course, every OS has it's share of endearing features. Here are a few that I ran into while playing around.

  • tab-completion doesn't work after su'ing
  • the route command is implemented as 3 commands: add_route, del_route, pr_routes
  • setsockopt errors for various unsupported options are displayed on the screen from time to time
  • clang requires -Wno-overloaded-virtual to work with rudiments socketclient
  • clang requires -Wno-mismatched-tags to compile sqlrelay c api
  • libtool doesn't know that Minix can create dynamic libs yet, must configure with --with-system-libtool
  • must include -lmthread before -L/usr/pkg/lib -lpthread (or use -pthread instead of both)
  • FIONBIO can't be used on sockets with ioctl, must use fcntl instead

Arguably the clang issues are bugs in my software. I guess I shouldn't count those. The libtool thing is just because this version of Minix is so new and the libtool patches haven't gone mainstream yet.

The mthread thing is a little weird.

It's a brand new release though, with lots of changes under the hood. A few endearing features are to be expected.

I hope X and gcc are available soon, I can't wait to play around with them.

In the mean time though, it's stable enough and doesn't slam the host CPU. I think I'll keep a Minix 3.3.0 VM running and add it to my build farm.

Thursday, August 28, 2014

Coherent 4.2.10

Introduction

Back in the 80's and 90's, there was this OS floating around called Coherent. Don't call it Coherent Unix because it's not, it's just Coherent. It is very unix-like but as far as I know, it's a clean-room implementation of a unix'ish system, not a derivative of any prior work. From what I've heard, early versions were less unix'ish than later versions, but I've never seen any of those, so who knows?

I'm not sure where I first saw Coherent. I know that I never saw it running anywhere. I think I saw a set of installation disks at a company I worked for in New Orleans in the 90's, but that could be a false memory. I know that it's impossible, but it seems like I've just always known about it. Funny how memory works.

I know for sure that I've run into it archived at The Unix Heritage Society. I was always a nervous about giving it a run it though, as distribution would require permission but it was unclear whether that had ever actually been given. There's open-source software in the archive and updates which Robert Chalmers got permission to distribute, but no word about the install disks themselves...

Until recently.

In 2012 Hans Bezemer tracked down the right guy (Bob Schwartz) and got permission to put together a redistributable root image. Sort-of. He's allowed to distribute it. But just him. Not you!

From The Beez's post:

I've had permission from Robert Swartz himself to distribute the
first perfectly legal Coherent 4.2.10 QEMU image as long as you
comply with the following conditions:

    You may use the software on this image free of charge for personal,
    non-commercial use. You may NOT redistribute this image or the software it
    contains without written permission from the copyright holder. The software
    is provided on an "as is" basis without warranty of any kind.

Well, maybe you could distribute it if you got permission too.

I wasn't looking to go bugging people for that though. I just downloaded the image and started playing with it.

That was like a year ago or more.

It ran great, but it was a little small, 42mb I think. I wanted to play with X and gcc. X barely fit on the root and I only got gcc to install after making a copy of the image, mounting it at /u1 and deleting all of the files. There was barely any room left on root, the kernel didn't appear to support more than 2 disks, no support for cross-partition links or symlinks... Red lights at every turn.

There had to be a better way.

Making More Space

I tried in vain to create a larger disk image but for some reason, every time I'd run a mkfs it would hose the root. I'm not sure if I was doing something wrong, or if there were bugs in QEMU back then, but a few days ago I got the urge to fiddle with it again, and, under QEMU 2.1.0, it worked great.

So, to make a bigger root, here's what you do...

Create a 512m disk image on the VM host.

dd if=/dev/zero of=coherent-bigger.img bs=1024 count=524288

I had all kinds of problems with larger disks, but 512m worked fine.

Boot qemu with the public image and the bigger disk image.

qemu -hda coherent.public.img -hdb coherent-bigger.dd -boot c -m 32

Log in as root with password rootroot

Partition the bigger drive and, while you're at it, install a master boot record.

fdisk -b /conf/mboot /dev/at1x

The -b option specifies the a master boot record to use. /conf has a bunch of bootloader images in it. mboot is the master boot record. /dev/at1x refers to the second drive. /dev/at0x is the first drive. The "x" means "whole drive" as opposed to individual partitions which are "a","b","c" and "d".

fdisk is interactive and friendly but very different from fdisk on other unixes.

You must:

  • zero the partition table
  • change active partition to partition 4
  • change one logical partition (partition 4)
  • specify partition sizes in cylinders
  • yes, create a coherent partition
  • accept defaults for base cylinder and partition size
  • make note of the number of blocks in the partition
  • quit
  • write the partition table

Now that the partition is defined, it's accessible via /dev/at1a. Format it!

mkfs /dev/at1a 1032129

What's that crazy number off the end there? That's the number of 512-byte blocks in the partition. It ought to still be on the screen from fdisk. Yes, it's essential to provide that number. Yes, it will hose all kinds of things if you use too large of a number.

Now, mount the new partition, copy everything from the root over to it, then sync and unmount it.

mount /dev/at1a /mnt
tar cvfp mnt/root.tar .exrc .lastlogin .profile autoboot bin coherent* conf dev etc f0 f1 home lib lost+found tboot tmp tmp.pipe update usr
cd mnt
tar xvfp root.tar
rm root.tar
mkdir mnt
chmod 777 mnt
cd /
sync
umount /dev/at1a

About the boot process... Coherent has a three-stage boot. The master boot loader looks for a bootable partition and runs whatever boot loader is installed in the first sector. This secondary boot loader looks on the root file system for /tboot and runs it. tboot (the tertiary boot loader) looks for autoboot which is usually a link to the current coherent kernel and runs that. At various points you have the option to specify a different partition or kernel to boot, but that's the general idea.

fdisk installed the master boot loader, but we still need the secondary boot loader on the primary partition. Fortunately that's easy to install.

dd if=/conf/boot of=/dev/at1a count=1

Also fortunately (for me), the man pages for "boot" and "fdisk" described all of this very clearly.

And that's it. Now we just need to shut down...

cd /
shutdown halt 0

...and restart qemu with the larger disk as hda.

qemu-system-i386 -hda coherent-bigger.img -boot c -m 32

Woohoo!

Coherent 4.2.10 - 1. first boot

And look at all that space!

Coherent 4.2.10 - 2. df
Post-Install Tweaks

The Beez created a user for himself in the public image but I'm not him, so I wanted to get rid of him and add myself. Turns out that you have to manually edit /etc/passwd, /etc/shadow and /etc/group to do this and then run passwd on the command like to set the new user's password. You also have to manually remove and create the home directories too, and there's no /etc/skel to copy into the new home.

Also, the chown command doesn't support setting the group, so you have to run chown and chgrp to properly set permissions for the home directory.

Ok! I did all of that, and I could now log in as me and poke all around the system.

There was a C compiler, an older vi clone (elvis), some games in /usr/games (but sadly no advent), uucp, and the standard set of unixy commands.

Disk access was exceptionally slow though. Exceptionally. File caching on the host helped a lot, but things were slow until it kicked in, and then got slow again as blocks got pushed out. Seems unlikely that Coherent would have run that way on real hardware. I imagine that QEMU's virtual disk controller doesn't emulate some particular thing that Coherent's looking for to decide whether to use DMA or something. Ehh. What are you going to do? Try SCSI instead of IDE? Seems like I tried that once, long ago. Might be worth checking into again though.

X Windows

Onward...

I really wanted to get X and gcc installed. Both were tricky. After much trial and error, here's what I ended up with...

Install X first. The gcc installer asks you to swap the linker post-install and the new linker causes problems for the X installer. Also, X ONLY supports serial mice. Fortunately QEMU does too, but you have to shutdown Coherent and restart QEMU using:

qemu-system-i386 -hda coherent-bigger.img -boot c -m 32 -chardev msmouse,id=msmouse -device isa-serial,chardev=msmouse

The X installer disk images are available in the TUHS Archive.

The installation process is simple except for 1 thing. You have to tell the installer the name of the package you want to install. You can't just tell it "install everything on the disk". There's no apparent way to do that at least. How does one determine the name of the package provided by the set of floppies? Maybe it was written on the outside of the physical media. It's definitely not in any of the FAQ's or any other obvious place. I randomly discovered the names of the X and gcc packages when googling for something else, unrelated. Some guy had torn his hair out figuring them out and happened to mention them in a post about something else. As far as I know, that post is the only place on the internet that the package names are given.

But! Once you know them, the installation process is straightforward.

install CohX /dev/fva0 2

CohX is the name of the X package. /dev/fva0 is floppy drive 0. 2 is the number of disks in the set.

Use the QEMU monitor to insert and swap disk images when prompted.

The installation is interesting. It relinks some binaries and builds others from source. When prompted, select a Microsoft Serial Mouse, at 1200 baud. Uncompress the manual pages.

When the installation is complete, add /usr/X11/bin to the PATH in /etc/profile. Then edit /usr/X11/lib/Xconfig and remove "640x480" from the two lines that it's found in. Then log out and back in to reset your PATH.

To get an X session, run:

startx
Coherent 4.2.10 - 3. X11R5

Classy.

Backspace doesn't work properly in the xterm, nor does vi, but xcalc does and xeyes does and so do various other X Windows distractions.

This is X11R5 though, and a seemingly stripped down version of it. ftp.x.org is still around though, so maybe some day I'll try to get some other software running.

The color X server doesn't work, but if you want to try it, remove /usr/X11/bin/X and create a hard link to X386color.

cd /usr/X11/bin/X
rm X
ln X386color X

Maybe it can be made to work under bochs or some other emulator. Something to try later.

GCC

The GCC installer disk images are also available in the TUHS Archive.

GCC was a little trickier to install than X. CohGCC is the name of the package. Knowing that, the install command was straightforward:

install CohGCC /dev/fva0 4

However disks 3 and 4 are mislabeled. Disk 4 is Disk 3 and vice versa. Ha!

Wild.

When the installation is finished, replace the default linker with a gcc-compatible linker.

mv /bin/ld /bin/ld.pregcc
mv /bin/ld.pre11 /bin/ld

Add /u1/gnu/bin to PATH in /etc/profile, relogin and bam!

Coherent 4.2.10 - 4. g++

C++!

Unfortunately there's not too much to compile. There are some programs under /usr/src, but ideally I'd want to try to get some modern software running.

File Transfer

Hmmm... According to the FAQs, Coherent supports NE2000 ethernet cards, TCP/IP and SLIP. If it does though, the version I have doesn't. The kernel doesn't appear to and there don't appear to be any networky programs installed anywhere. If any of that was available on the original 4.2 distribution, it didn't get installed. I don't imagine it was though, being only 4 floppies and all.

So, what options did I have?

The Beez recommends a floppy image formatted for MSDOS. Coherent has various utilities for reading those, you can loopback mount the image under most unixes, and QEMU allows you to insert and eject the image easily. But what if I want to transfer 15 meg of data. No way I'm tarring, splitting, dd'ing, copying and catting those together.

Coherent appears to come with various serial-line file transfer solutions though. Taylor UUCP was on there, but UUCP is a nightmare to set up. Kermit was also available though. Hmmm...

I set up a getty on com2 by editing /etc/ttys and updating the second line:

1lScom2l

That cryptic jumble means: run a login (1), local device (l), 38400 baud (S), device /dev/com2l (com2l). 38400 is unfortunately the fastest speed available.

Then I re-ran qemu with a second serial port redirected to a telnet server on port 10000.

qemu-system-i386 -hda coherent-bigger.img -boot c -m 32 -chardev msmouse,id=msmouse -device isa-serial,chardev=msmouse -chardev socket,id=socket,host=0.0.0.0,port=10000,ipv4,nodelay,server,nowait -device isa-serial,chardev=socket

And then I could use kermit on linux and ckermit on Coherent to transfer files. It's a little tricky and long-winded to explain, but basically you connect over, log in, run kermit over there, start a receive process, escape back locally, start a transfer, and wait...

Coherent 4.2.10 - 5. kermit

And I do mean wait.

No way I'm waiting that long...

It was cool for small files, but not for anything big.

In the end, it was faster to tar up a bunch of files, reboot QEMU using the tar file as the second disk...

qemu-system-i386 -hda coherent-bigger.img -hdb files.tar -boot c -m 32 -chardev msmouse,id=msmouse -device isa-serial,chardev=msmouse

...and then untar it in Coherent as root.

tar xvf /dev/at1x

Unfortunately this requires a reboot every time you want to transfer a bunch of files, but it's faster than any of the alternatives.

Software?

I really hoped to get bash working and a newer version of vi, and maybe eventually some of my own software, but it was a losing battle from the start. Even bash 1.14.7 requires a lot of tweaking, and I still haven't gotten it to fully compile. There's a 14 character filename limit too. C++ source has to have a .C extension rather than .cpp ...

Hurdles.

Not the downhill run I'd hoped for. But, on the bright side, it's something to look forward to tinkering with later.

Endearing Features

Coherent has a lot of these.

  • QEMU doesn't detect the idle loop and slams the host cpu.
  • It only appears to support 2 drives.
  • Disk access is incredibly slow.
  • Symlinks are not supported.
  • Cross-device links are not supported.
  • X only supports serial mice.
  • backspace and vi don't work in xterms.
  • The shutdown command is odd - shutdown halt|reboot
  • Gcc requires .C extensions on C++ sources.
  • There's a 14 character filename limit.
  • The filesystem appears to be quite sensitive. Any improper reboot hoses the filesystem. Fsck is not automatically run at startup. When you run it manually, it ends up asking you to remove corrupted files almost every time.
  • Y2K issues galore.

There were more too but those were the most significant. Sounds like a lot, but given the age of the distribution, I expected even more.

I guess it's also worth mentioning that The Mark Williams Company was a small outfit, tiny compared to SCO and the Linux community with whom they ultimately had to compete. That they were able to build a unix-like OS for PC with the features that it had and maintain it for so long is quite a feat.

And Finally...

All right! I finally have a working Coherent installation. It seems pretty stable. There's plenty of space to play with. Lots of stuff works and lots of opportunities remain for tinkering. Hopefully I'll figure out color graphics and get some more modern software to compile soon. Maybe I'll even find some vintage software to run on it. I'd ideally like to get some kind of networking going too. I might have to wait on The Beez to finagle that though.

Friday, June 27, 2014

DB2 6.1 Personal Edition

Introduction

I'm a sucker for old-timey software. I especially like it when I can shoehorn it into some semi-modern environment somehow. That's always fun. I especially like old database systems, so whenever somebody puts something like DB2 6.1 Personal Edition on eBay for like $6.00, I'm not too slow to grab it up.

Such was the case recently.

Installation

What does DB2 6.1 PE even run on? The CD said Windows 95, 97 and NT. I have Personal Oracle 7.2.2 running on Windows 95, so I figured I'd try that first.

It's probably not impossible to get it working on Windows 95, but I couldn't figure out how. Everything installed but nothing ran. Rather than wrestle with it, I figured I'd just try it on NT and see if it went any better.

It did. Much better.

After one false start trying to install it as myself, I logged in as the Administrator, and the installation was straightforward.

I installed all product options.

DB2 6.1 PE - 1. Options

It asked for a user to run everything as. I accepted the default db2admin user. Oddly, some default password was given but it was also starred out. I guess I could have clicked Next and gotten whatever password it was, but I wouldn't have known it. So, just to be safe, I deleted the default passwords and typed in my own.

DB2 6.1 PE - 2. User

DB2 security is a little different from other DB's. When you create an instance, a system-level user is created and the instance runs as that user. If you're logged in as that user, you can access the DB without supplying credentials, but if you want to access it as another user, then you have to supply the system-level credentials.

It's funny though, when I was first learning DB2, none of the examples I ever saw showed how to supply credentials. For a long time, I thought you had to log in as the owner of the instance to be able to access that instance at all. It was all fairly confusing and it got even more confusing when I wanted access databases on remote machines, but that's another story...

The point is that the DB2 installation actually created an NT user named db2admin. This would be important later.

The rest of the install went smoothly.

DB2 6.1 PE - 3. Install

I eventually had to restart the system and when it came back up I was presented with some "First Steps".

DB2 6.1 PE - 4. First Steps

The Local Database

The first of the first steps was to create a sample database. I clicked that and it failed. Strange... I tried again (for some reason thinking it would work the second time) and got the same result. The Task Manager showed a bunch of db2-ish processes running. What the heck?

Ohhh... Heh. db2admin.

After reboot, I'd logged in as myself rather than the db2admin user that the installation process created.

The create-the-sample-db process was trying to run as me. I have no permissions. After logging out and back in as db2admin, creating the sample DB worked as expected.

The second of the first-steps led to the Command Center - basically a semi-graphical database shell.

DB2 6.1 PE - 5. Command Center

I used it to poke around in the sample database a bit.

The third led to the Control Center...

DB2 6.1 PE - 6. Control Center

...which allowed me to poke around a little bit more.

The fourth of the first-steps led to the Information Center (online documentation).

DB2 6.1 PE - 7. Information Center

The documentation viewer relied on Netscape to display the actual docs and the version of Netscape I had on there was a little flaky. It would complain about not being able to open a page, and then go ahead and open it. Fortunately the DB2 docs were about as old as Netscape itself and it didn't have any trouble rendering them.

Everything worked, but everything also ran terribly slowly. It turned out I'd configured the VM with 64m of ram and that just wasn't enough to run the DB. After bumping it up to 128m, everything ran really well.

Remote Access

So I had a working instance of DB2 in my NT VM and I could poke around in it with the provided tools. What kind of remote access could I get working though?

These days configuring remote access usually just means supplying a host name or address and port. That is, an IP address and TCP port. DB2 has been around for a while though, since long before TCP/IP emerged as the dominant protocol. Even Personal Edition supports TCP/IP, IPX/SPX, NetBIOS and APPC (whatever that is). As such, remote databases are abstracted out a bit beyond host and port.

DB2 achieves this via two catalogs: "nodes" and "databases". Nodes identify servers and databases identify instances of DB2 running on those servers. DB2 clients can be told what database to connect to, and they use the local catalog to figure out how to connect to it.

To add a node to the catalog, you have to specify the network protocol, name of the node, and protocol specific info. To add a database to the catalog, you have to tell specify the instance name (as it's known on the remote machine), a local alias for that instance, and the node it's running on.

I have several versions of DB2 running on various Linux VM's, including an instance of 7.2 running in a Redhat 6.2 VM and an instance of 10.5 in Fedora 19 VM.

I first tried connecting to 6.1 from the Linux VM's. This involved logging in as the db2inst1 user on Linux (the user the Linux instances are running under) and running commands like:

db2 "catalog tcpip node winnt remote winnt server 50000"
db2 "catalog database sample as sample61 at node winnt authentication server"
db2 "terminate"

The first command creates a node named "winnt" aimed at port 50000 on the host named "winnt". The second creates a database known locally as "sample61" aimed at "sample" on node "winnt". The third commits the configuration.

I could then try to access the 6.1 instance from Linux using the db2 shell interactively.

From DB2 7.2 on Redhat 6.2, it worked great.

db2 => connect to sample61 user db2admin using mypassword

   Database Connection Information

 Database server        = DB2/NT 6.1.0
 SQL authorization ID   = DB2ADMIN
 Local database alias   = SAMPLE61

db2 => select * from employee where job='CLERK'

EMPNO  FIRSTNME     MIDINIT LASTNAME        WORKDEPT PHONENO HIREDATE   JOB      EDLEVEL SEX BIRTHDATE  SALARY      BONUS       COMM
------ ------------ ------- --------------- -------- ------- ---------- -------- ------- --- ---------- ----------- ----------- -----------
000120 SEAN                 O'CONNELL       A00      2167    12/05/1963 CLERK         14 M   10/18/1942    29250.00      600.00     2340.00
000230 JAMES        J       JEFFERSON       D21      2094    11/21/1966 CLERK         14 M   05/30/1935    22180.00      400.00     1774.00
000240 SALVATORE    M       MARINO          D21      3780    12/05/1979 CLERK         17 M   03/31/1954    28760.00      600.00     2301.00
000250 DANIEL       S       SMITH           D21      0961    10/30/1969 CLERK         15 M   11/12/1939    19180.00      400.00     1534.00
000260 SYBIL        P       JOHNSON         D21      8953    09/11/1975 CLERK         16 F   10/05/1936    17250.00      300.00     1380.00
000270 MARIA        L       PEREZ           D21      9001    09/30/1980 CLERK         15 F   05/26/1953    27380.00      500.00     2190.00

  6 record(s) selected.

db2 =>

Woohoo!

It didn't work so well from DB2 10.5 on Fedora 19 though.

db2 => connect to sample61 user db2admin using mypassword
SQL30081N  A communication error has been detected. Communication protocol
being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location
where the error was detected: "192.168.123.68".  Communication function
detecting the error: "recv".  Protocol specific error code(s): "*", "*", "0".
SQLSTATE=08001
db2 =>

Not so well indeed.

I tried in in reverse too - accessing 7.2 and 10.5 on Linux from 6.1 on Windows NT. I ran analogous catalog commands using Command Center on Windows and got similar results. I could access 7.2 just fine but attempts to access 10.5 resulted in:

SQL5048N  The release level of the client is not supported by the 
release level of the database server.

Yeah, I figured as much. The two versions are separated by over a decade. Got to break back-compatibility at some point, I guess.

So I could connect back and forth between 6.1 on Windows NT and 7.2 on Redhat 6.2. It's a start, but I'd need another link in the chain to be able to get to 6.1 from a modern OS.

SQL Relay

It's been longer than I can remember since I tried running SQL Relay against DB2 7.2. I knew it would build, and there are even #ifdef's in the code for some 7.2 quirks, but would it work?

Turns out no. Not at first at least. DB2 7.2 has a "feature" where if you connect to the DB, then fork the process, the child loses the connection and all subsequent queries fail. At some point I had logic in SQL Relay to deal with that feature, but newer versions of DB2 don't have the problem and the logic had long been removed. It took me a while to figure out what was going on, but once I did I remembered the bug and it was easy to fix. I even fixed it in a more elegant manner than I had in the past.

So Relay could talk to 7.2. Could it talk to 6.1 via 7.2's catalog?

Turns out yes!

DB2 6.1 PE - 8. Access From Fedora 20 x64

Woohoo again!

I now had access to DB2 6.1 Personal Edition from Fedora 20 x64.

And what a contrived chain of software was involved:

SQL Relay client on Fedora 20 x64 ->
SQL Relay server on Redhat 6.2 x86 ->
DB2 7.2 on Redhat 6.2 x86 ->
DB2 6.1 on Windows NT

But hey, it worked.

After a few modifications, I was able to run my standard DB2 test script too.

IDENTIFY:
success
PING:
success
CREATE TEMPTABLE:
success
INSERT:
success
BIND BY POSITION:
success success success
ARRAY OF BINDS BY POSITION:
success
INSERT:
success success success success
AFFECTED ROWS:
success
LONG BLOB:
success success success
SELECT:
success
COLUMN COUNT:
success
COLUMN NAMES:
success success success success success success success success success success success success success success success success success success success success success success
COLUMN TYPES:
success success success success success success success success success success success success success success success success success success success success success success
...

I did have to make a few tweaks to SQL Relay to get blobs and clobs working. There's still some issue with blob binds, but spending time on that is low on my list.

Endearing Features

Once I had everything running, I played with it for a while and began to discover some of the differences between 6.1 and newer versions.

Some of the more interesting ones...

The maximum size for a Blob or Clob column has to be specified during the create statement. For example:

create table test (col1 clob(1M), col2 blob(100K))

You can specify the maximum size in bytes, or use K, M or G.

Conversion errors are somewhat common and you often have to cast values, especially NULL values using CAST(X as CHAR(4)). I never did get a good feel for when this was necessary, but I ran into it a bit.

There's no obvious way to get the hostname from within the DB. In newer versions, you can run:

select host_name from table(sysproc.env_get_sys_info())

...but not in 6.1. I imagine that's another artifact of all the network protocols that it supports.

And my favorite... Stored procedures can only be written in C, Java or COBOL. There's no SQL PL. I guess it just hadn't been invented yet. Ha! I love it.

Ok, so that's it for DB2 6.1 PE, for now at least. Maybe I'll discover more weird stuff later and write more about it.

Maybe.

Thursday, May 29, 2014

Solaris 2.5.1 x86

Introduction

Versions of Solaris x86 prior to 7 are a little difficult to come by. Yeah, I'm sure you can download them from somewhere, but that's not really my style. I guess I should say that physical media is hard to come by.

But!

A while back I came by some.

solaris 2.5.1 - 1. packaging

eBay to the rescue yet again.

Man, that's some fancy packaging.

Unfortunately it languished in my closet for weeks before I had any time to give it a run. Actually I had a hurdle to jump too. The installer boot media is a floppy and I didn't have a floppy drive. Microcenter had one floppy drive in the entire store but it was an internal. I'd have bought it but my motherboard doesn't even have floppy controller on it. What modern board does? USB was my only hope. I'd borrowed a USB drive from the shop down the road last time, but not wanting to make a nuisance of myself, I declined to bother them again, and just ordered one of those off of eBay too. Then I took a little vacation... All of that took weeks.

But, a few days ago I had an opportunity. It wasn't exactly free time, but the project I'm working on right now regularly requires that you let it run for 3-5 minutes and wait for it to finish. So, in those 3-5 minute blocks, I managed to get Solaris 2.5.1 running in VMware.

"How?" you might ask.

Like this...

VM Configuration

Solaris 2.5.1 has two fairly significant limitations that took me quite a bit of trial and error to discover. The biggest hard drive that it supports is somewhere between 1G and 2G, and though it supports PCNet ethernet cards, it doesn't recognize VMware's emulated PCNet card. Actually, the boot disk does, but Solaris itself doesn't. Go figure.

I ultimately ended up configuring the VM with 128m of ram, three 2G hard disks, no sound card and no ethernet card. I also made sure that the first disk was on IDE 0:0, second on IDE 0:1, cdrom on IDE 1:0 and third disk on IDE 1:1. Rather than installing directly from the media, I made backup images of the CD's and boot floppy, aimed the cdrom at the "Software" CD image and aimed the floppy at the boot floppy image.

I did want some kind of networking, so I added a serial port, using a named pipe and made "this end" the client and "the other end" a virtual machine. More about that later though...

Why not just use Qemu or Bochs, whose NICs might be recognizable? I tried both. Neither were able to run the installer from the CD. I tried lots of different configurations - IDE, SCSI, converting the cdrom to a hard disk image, etc. Nothing worked.

Installation

At any rate...

The installer was similar to Solaris 7 but a bit more primitive. That's one of the things that I love about tinkering with old OS'es though. It's fun to watch the evolution of systems, even in reverse.

Most of the prompts were intuitive. The installer asked for precious little networking info, only the host name actually. I bypassed Graphics Device configuration as I usually do with Solaris installations. The date defaulted to 1911 and upon seeing that, I wondered what Y2K bugs I'd run into later. I selected a Standalone system type and installed the Entire Distribution.

Disk partitioning was a little tricky. I was presented with all 3 disks and one-by-one, chose to Auto-layout Solaris Partitions. This created a 1858mb partition on each disk. I also chose to Auto-layout File Systems and unchecked /usr and /opt.

On the File System and Disk Layout screen, I was presented with 3 partitions: c0d0 contained root and /export/home filesystems, c0d1 had /export/home0 and c0d1 had /export/home1. Though each partition was about 1.6G, the file systems only used about 1G of that and I was unable to make them larger - something about a 1023 cylinder limit. Between the 3 disks, I had about 3G of space though, which ought to be plenty.

I planned on building software in my home directory under /export/home and installing it under /opt/sfw, so I did rename the partitions. On c0d0 I removed /export/home altogether and changed the root to 876mb (or 876 blocks or cylinders, or whatever units the partition manager used). On c0d1, I renamed /export/home0 to just plain /export/home. On c1d1, I renamed /export/home1 to /opt.

This gave me 1 filesystem per partition and about 1G of space in each filesystem.

It's funny, disk space these days isn't unlimited, but for the purposes of downloading, building and installing software, it might as well be. Long gone are the days where you have to think hard about how to layout your disks so you don't run out of space building software. Playing with Solaris 2.5.1 brought all of that back though.

I told the installer not to worry about remote file systems and not to automatically reboot. If something went wrong, I wanted to see it on the screen, not discover it way later after an auto-reboot.

And, voila!

solaris 2.5.1 - 2. install

Installation!

The install went smoothly. The first boot required a little post-install configuration, like selecting the keyboard layout and entering a root password. I bypassed Graphics Devices again.

Aside from some safe-to-ignore CD-related error messages, the system came up cleanly and gave me a login.

solaris 2.5.1 - 3. boot

Woohoo!

I added a user for myself, created /usr/local and /opt/sfw directories and tweaked everyone's path in /etc/profile:

PATH=$PATH:/usr/ccs/bin:/usr/ucb:/usr/openwin/bin:/usr/openwin/demo:/usr/dt/bin
...
export LOGNAME PATH

Everything was running smoothly.

Networking

I needed to get some kind of networking going though.

This was not quick and easy by any stretch. I spent hours fiddling with configuration files, manually loading kernel modules, applying and re-applying patches... Nothing. The PCNet NIC was unidentifiable and e1000 was even more hopeless. I'm not saying that it's impossible to get it to work, but I couldn't figure out how. In the end, I resorted to PPP.

There are a lot of links on the web pointing to Solaris PPP configuration tutorials, but almost all of them are dead. I did find one though, and between it, man pages and comments in various files, I extrapolated out the following, working PPP configuration.

On the solaris VM, I mentioned earlier that I set up a serial port to a named pipe, with "this end" the client and "the other end" a VM. On a separate Linux VM, I also added a serial port to the same named pipe, with "this end" the server and "the other end" a VM. It's important that one end be the sever and the other the client. Declaring both ends the server causes VMware to complain at boot that another VM is holding the pipe. I assume the same would be true if both ends were declared to be the client, but I didn't test that.

On the Solaris VM, I configured the following files, in the following ways:

/etc/hosts

192.168.123.136 solaris251-ppp
192.168.123.137 solaris251

solaris251 is the local host name and 192.168.123.137 is the local IP. solaris251-ppp is the other end of the PPP connection and will have address 192.168.123.136. Solaris' PPP requires these host file entries. Leaving them out creates difficult-to-debug errors.

/etc/asppp.cf

ifconfig ipdptp0 plumb solaris251 solaris251-ppp up
path
  interface ipdptp0
  peer_system_name solaris251-ppp
  inactivity_timeout 0

This configures a network interface named ipdptp0 with the IP for "solaris251" on this end and the IP for "solaris251-ppp" on the other end. Solaris PPP leans heavily on UUCP for actually connecting between systems. As such, the peer_system_name directive tells PPP to use the UUCP definition for "solaris251-ppp". The inactivity_timeout directive of 0 tells PPP not to close the link due to inactivity.

/etc/uucp/Systems

solaris251-ppp Any Direct 115200 - -

Now we're delving into deeper magic. UUCP! Anyone remember that? Fortunately the Solaris UUCP config files are pretty thoroughly commented. This line defines a system named "solaris251-ppp" that can be connected to at Any time of day, using the Direct dialer, at 115200 baud with no phone number (the first -) and no login script (the second -).

/etc/uucp/Dialers

Direct cua/a - Any direct

Even deeper magic. This line defines a dialer named Direct that uses serial port cua/a. I'm not sure what the - or Any mean in this file but "direct" means to use the a device named "direct" from the Devices file. This line actually already existed in the Dialers file, but used cua/b (the second serial port) rather than cua/a. I just updated it to use cua/a. I found it odd that it would default to the second port rather than the first. I'm sure it was conventional to have something else on the first port back in the 90's, but what that might have been is lost to history.

The /etc/uucp/Devices file defines configurations for modems or direct serial cable interfaces. It already had a "direct" device definition and I didn't modify it.

/etc/resolv.conf

domainname firstworks.com
nameserver 192.168.123.37
search firstworks.com

/etc/nsswitch.conf

hosts: files dns

I just updated that one line.

/etc/defaultrouter

192.168.123.136

I also added an init script to ping the remote system and cause the ppp connection to come up. It's possible that there's some directive that I could have added to asppp.cf to make the connection come up, but I couldn't figure it out.

/etc/init.d/pppup

#!/bin/sh

case "$1" in
  start)
        /usr/sbin/ping solaris251-ppp > /dev/null 2>&1
        ;;
  stop)
        ;;
  *)
        echo $"Usage: $0 {start|stop}"
        exit 1
esac

exit 0

And to make it actually run at boot...

chmod 755 /etc/init.d/pppup
cd /etc/rc3.d
ln -s ../init.d/pppup S90pppup

All that was just on the Solaris side. The other end of the ppp connection, on the Linux machine, had to be configured too. This was fortunately a lot simpler. All I had to do there was add an init script.

/etc/init.d/pppserver

#! /bin/bash

# See how we were called.
case "$1" in
  start)

        # pppd for solaris 2.5.1
        /sbin/pppd noauth crtscts lock passive persist proxyarp ktune 192.168.123.136:192.168.123.137 /dev/ttyS0 115200
        ;;
  stop)
        # kill pppds
        killall pppd

        # disable ip forwarding
        echo 0 > /proc/sys/net/ipv4/ip_forward
        ;;
  restart|reload|force-reload)
        $0 stop
        $0 start
        rc=$?
        ;;
  *)
        echo $"Usage: $0 {start|stop|restart}"
        exit 2
esac

exit $rc

The pppd options are all very important. "noauth" means the Solaris VM doesn't have to to PAP/CHAP authentication. "crtscts" sets up flow control. "lock" establishes a lock file so accidentally starting another pppd won't wreak havoc. "passive" tells pppd to wait for connections rather than giving up and exiting if it can't establish one itself. "persist" means not to exit if the other end closes its connection. "ktune" causes pppd to enable IP forwarding. I could have done that manually but it was an option, so I used it.

The "proxyarp" option is very important and also hard to explain. It causes pppd to add an ARP entry containing the hardware address of the local ethernet card and the IP address of the Solaris machine. This makes it appear that the Solaris VM is on the local network, even though technically it is sitting behind the Linux VM. Packets destined for the Solaris VM will be routed to the Linux VM. Once they're on the Linux VM, they'll be routed to the Solaris machine via local routing rules. It's kind of a hack, but it obviates the need for NAT and connection tracking.

I set up the PPP server to run at boot too:

chmod 755 /etc/init.d/pppserver
cd /etc/rc3.d
ln -s ../init.d/pppserver S99pppserver

There is probably some more official way to configure PPP that would cause it to come up automatically without the need for the init script, but this way seemed easier and more portable, and at the time I just wanted to get it working quickly.

So. After all that, and after recovering from a little misconfiguration. I ran the init script on Linux, rebooted Solaris and BAM! Networking!

I could ping yahoo. I could telnet all over the place. I could ftp to ftp.gnu.org...

solaris 2.5.1 - 4. networking

I was really happy until I remembered that it was running at 115200 baud. The actual throughput was around 3 kilobit. Downloading software from GNU took minutes. The setup was ok for telnetting into the Solaris system, but it was infinitely faster to transfer files by making an ISO image of them, aiming VMware's fake cdrom at the image and copying them off.

I tried higher baud rates but I couldn't get anything working higher than 115200. There might be some way, but I couldn't figure it out.

Ha!

Oh well. It was still fun to get it all working.

Software

Software for Solaris 2.5.1 is outright impossible to find. If that's an exaggeration, it's only a slight one. I ended up building everything I needed from source, just as I'd done on Solaris 7. I even used the same versions of software.

To summarize...

On my Solaris 7 VM, I built a version of gcc that runs on Solaris 2.5.1 and build software for Solaris 2.5.1:

./configure --prefix=/usr/local/gcc-2.95.3 --host=i386-pc-solaris2.5.1 --target=i386-pc-solaris2.5.1 --enable-shared
gmake
gmake install

(I probably could have build gcc for 2.5.1 on any version of Solaris, not just 7, but I was pulling other software off of that VM at the time, so I used it to build gcc too.)

Then tarred it up and copied it over to Solaris 2.5.1 and used it to build gzip and rebuild gcc, both of which I installed under /opt/sfw. Rebulding gcc required that I set CC=gcc during the configure step...

CC=gcc ./configure --prefix=/opt/sfw --enable-shared

...but otherwise went smoothly.

I added /opt/sfw/bin to everyone's PATH and /opt/sfw/lib to everyone's LD_LIBRARY_PATH and everything else was downhill from there.

I built and installed bash, sudo, perl, openssl, zlib and openssh. None of the manual tweaks that I'd applied when building on Solaris 7 were necessary though I did have to specify --without-pam when configuring sudo. I set up ssh to run at boot just as I had on Solaris 7, and was soon able to ssh into the VM.

solaris 2.5.1 - 5. ssh

I also built gnu tar, lynx, wget, cvs, make and vim. I couldn't get apache 2.0.65 to build though. The configure script stalls out during a TCP_NODELAY test. Maybe an older or newer version will work though. I have yet to try it out. Netscape 4.78 for Solaris 2.5.1 x86 was also a failure. Though the filename alleges Solaris 2.5.1 support, it appears to require a newer version of libresolv than the default installation comes with. Perhaps some patch will fix that. I didn't look too hard for that.

Graphics

Getting a graphical environment working was also difficult and disappointing.

The default installation comes with the openlook windowing system. I ran kdmconfig -c and followed the intuitive prompts but all I could get was 16 colors at 640x480.

solaris 2.5.1 - 6. openwin

Cute, but not all that impressive.

I'd had the same issue with Solaris 7 though, and installed XFree86 4.7.0 to resolve it. Unfortunately the same solution wasn't all that workable on 2.5.1. I tried installing every version of XFree86 from 3.3.6 to 4.7.0. The 4.X series all fail because __ctype_mask, snprintf and vsnprintf are undefined on Solaris 2.5.1. After some monumental hackery, I was eventually able to get the X server from 4.7.0 to run as root but the system wasn't generally workable. 3.3.6 installed cleanly but its SVGA driver didn't work with VMware. I may eventually get decent graphics working, but doing so will be enough for its own article.

CDE comes on a second CD with the Solaris 2.5.1 distribution and I installed it.

cd /cdrom/cdrom0
cd CDE/x86
sudo ./install-cde

The installer is semi-intuitive and you have to reboot afterwards. CDE worked but it looked terrible in 16 colors and all I used it for was to log in, run a terminal and disable dtlogin.

dtlogin -e
Development

The ultimate goal of all of this is, of course, to get a development platform working.

I had enough for that, and with a few small tweaks my software built and ran. As was the case on Solaris 7, I wasn't able to get any database software to build and I had to disable openssl support because for some reason, the version of openssl that I've been using only builds static libraries on Solaris platforms.

But I was able to run the client-side and access Oracle 12c.

solaris 2.5.1 - 7. sqlr

Again, not so impressive, as Oracle did at one point release software for Solaris 2.5.1, but it's also difficult to come by these days. I did see version 7.3.4 on eBay a while back for Sparc Solaris 2.X and I think a few copies of 8.0.5 for Sparc Solaris are out there right now, but being for Sparc platforms, those don't really do me a lot of good.

Other Software

The distribution came with a second CD containing CDE, WABI and ODBC. I installed CDE but without decent graphics, it wasn't much to write about. WABI would no-doubt be equally drab without good graphics so I didn't even bother to install it. If I can get some good graphics going I'll write another article about that. I guess I could try out ODBC. I'm curious if it comes with any drivers.

Fuel for future writing.

Quirks

...or endearing features as I prefer to call them.

  • Supports 1.8g partitions but only uses 1g of that space.
  • You have to use the Delete key to Backspace.
  • The default shell doesn't understand ~/ but does understand $HOME.
  • Filesystem performance is not so good, untarring and rm -rf'ing take a while.
  • Setting the domain in /etc/resolv.conf uses the domainname keyword rather than domain.
  • The CPU doesn't idle, so running it as a VM slams the host OS's CPU
  • libc contains working versions of __snprintf and __vsnprintf but they aren't defined in the header files.

Ok, so that was kind-of fun, especially PPP. I wish I'd been able to get the web stuff and better graphics working though. The web stuff probably won't take too much work.

Graphics though... Hmm... Maybe someday.

Saturday, April 19, 2014

Hurd 2013

Introduction

Back in 2013, an updated version of Debian Hurd came out, aptly titled Hurd 2013. I downloaded the ISO but never got around to even trying to install it until yesterday.

While other GNU projects have basically driven the state of the art forward on a regular basis, the Hurd might get the award for the most slowly advancing project of all time. I'd put it right behind the Enlightenment window manager. It does keep moving forward though, inch by inch.

What is this Hurd you speak of? Basically it's GNU's take on the kernel. It's different from most kernels though because it implements a microkernel architecture.

What is this microkernel architecture you speak of? Well, I hope I explain this inoffensively accurately...

Most kernels are one big block of code, occupying a single address space. If an app wants to read a chunk of data from a file, it asks the kernel (via a system call) to read the chunk into a specified block of memory. Inside the kernel, the request trickles down through various subsystems and drivers. Something like: virtual file system subsystem -> ext3 driver -> virtual block device subsystem -> sata subsystem -> specific sata driver -> sata controller... To achieve this, each subsystem or driver makes a function call to the layer below it. Since all of this is done in the same address space, it's fast, but a bug in any one subsystem or driver could crash the entire system.

In a microkernel system, the microkernel is small and discrete. It manages virtual memory, schedules processes and provides a mechanism for proceses to talk to each other: Interprocess Communication (or IPC). That's all. Kernel components run as separate processes on top of a microkernel, each in their own address space, and communcate with each other and with user-space apps via IPC. If an app wants to read a chunk of data from a file, the request has to trickle down through an analogous set of subsystems and drivers, but rather than making function calls, the subsystems in the chain communicate via IPC. This involves a lot of copying and synchronization, and is potentially slower, but much more robust. Since everything runs in separate address spaces, it's much harder for a bug in one subsystem or driver to take down the entire system.

The Hurd isn't the only microkernel OS out there. Minix, QNX, Tru64 and OS X are all microkernel-based. There are many others too, but those come to mind immediately. Which architecture is superior? The jury is still out. There have been some famous debates on the subject, major vendors have gone both ways, but no clear winner has emerged.

Installation

At any rate, I'd played around with Debian Hurd 0.3 years ago but never got around to trying the current version until yesterday.

I installed it in VMware and ran into a few issues, but nothing I didn't eventually figure out how to work around.

Hurd 2013 - 1. install

I had to give the VM 512mb of ram for the installer to run at all.

The graphical installer only sort-of worked. It didn't display the "Go Back" and "Continue" buttons, and eventually hung extracting files. The text and pseudo-graphical installers worked fine though.

VMware usually puts the hard drive at IDE 0:0, but sometimes, randomly, puts it at IDE 1:1. I'm not sure why, but if it's not at 0:0, then the installer will eventually fail near the end, unable to find the CD. Making sure that the hard drive is at IDE 0:0 fixes this. Go figure.

The installer is also a little confusing because it sees the CD as just another hard drive, or at least presents it that way. When partitioning disks and installing the bootloader, it gives you the option of partitioning the CD or installing the bootloader on the CD. Not a problem, but it made me smile when I saw it.

There was also a problem near the end of the installation. It asks what additional software you want to install, but any attempt to install additional software fails. Accepting the default set of software works fine though.

So, after figuring all of that out...

Hurd 2013 - 2. first login

Woohoo!

I was running the Hurd.

Post-Install Tweaks

During the boot process, /proc errors litter the screen. It turned out that the /etc/fstab had no entry for /proc, so I added one:

proc /proc procfs defaults 0 0

But there was still some issue. Attempts to mount /proc failed.

mount: cannot start translator /hurd/procfs: Translator died

Hmmm....

Good example there though. A system with a monolithic kernel might have crashed entirely.

I did a bunch of research and digging around but I never got it working. /proc did work in 0.3 though, so I guess that's a regression.

On the plus side though, /etc/network/interfaces worked just like in other Debian releases, and I was able to use it to give the system a static IP. In 0.3 I'd had to set the IP address manually using fsysopts, but not in 2013.

Progress!

I didn't have to tweak much else. I'd created a user for myself during installation, sudo was installed by default, and the ssh server just worked.

The Web

Wget was installed by default, but nothing else. I installed lynx, iceweasel and apache2 using apt-get, just like on any other Debian system.

Lynx worked. X-forwarding didn't, so I couldn't run iceweasel yet.

Apache was tricky to configure. The config files are spread out over a bunch of different directories. I guess it's the same on modern Debian Linux systems too but it was tricky to find everything.

I actually kicked apache around for a while. I'd configured it correctly, as it turned out, but the server wouldn't start until after I installed the apache2-dev, libapr1-dev and php5-dev packages. Apparently one of them added some important file. Even then though, the server would run, but wouldn't run CGI's. I eventually rebooted for an unrelated reason and was surprised to find CGI's working after the reboot, with no changes to the apache configuration.

Weird.

X Windows

In 0.3, I'd had a hell of a time getting X windows working. I eventually got twm running, but nothing else.

In Hurd 2013 it was easy to get XFCE running.

Hurd 2013 - 3. xfce

I just installed the xorg and xfce4 packages, created an .xinitrc file with:

xfce4-session

And ran startx.

There is some security setting though, that prevents a non-root user from running X on the console. I'm not sure if Debian Linux has the same issue or not. I poked around a bit but never figured it out.

I didn't bother getting a graphical login working because I didn't plan on running X most of the time.

Xterm and the other basic XFCE components worked fine but my luck with other software wasn't as good.

X-forwarding hadn't worked over ssh. I'd hoped to be able to run iceweasel in the X session but unfortunately it failed to start there too.

apt-cache search turned up openoffice.org and libreoffice but it appeared that some of the necessary dependencies were unavailable.

I tried Gnome and KDE too but, as with the office packages, it appeared that some of their dependencies haven't been built yet, or at least haven't made it into the repository.

Darn!

Well, who knows. I'll give it a few months and try again.

Development

The development tools, languages and libraries that I needed were all available - gcc, make, cvs, vim, pcre, ssl, readline, perl, python, php, ruby, tcl, erlang, mysql, postgresql, sqlite, freetds, firebird, odbc and mdbtools. Yeah, there's no Oracle, Sybase or DB for Hurd, but that's kind of the point of SQL Relay. One of them at least.

Hurd 2013 - 4. sqlrsh

Oracle from Hurd!

One of the shortcomings of Hurd 0.3 was lack of support for SysV IPC - semaphores, shared memory and message queues. I'd hoped that Hurd 2013 had them, but I was out of luck there:

dmuse@hurd2013:~$ ipcs

kernel not configured for shared memory

kernel not configured for semaphores

kernel not configured for message queues

So, no SQL Relay server.

I looked around a bit for how to recompile the kernel. Maybe IPC is supported, just not enabled. I didn't get too far with that though.

Something to do later.

Conclusions

The most obvious improvements over 0.3 were support for /etc/network/interfaces and XFCE. Those are pretty big steps from a usability standpoint. I'm sure that a bunch of stuff was improved behind the scenes too, but those stood out.

It's unfortunate that /proc no longer worked, but hey, sometimes you've got to break a few eggs.

The only serious problem I ran into was general stability. My 0.3 VM sits idle most of the time. Every now and then I do an automated build on it, and it's always there waiting. 2013 doesn't seem so stable. I've had to restart the VM after leaving it idle for a few hours, several times, and sometimes it hangs at boot and has to be restarted again. It kind of feels like a filesystem problem, and a few times I've fsck'ed it and then fsck'ed it again, only to find more errors on the second pass. Hmmm. I see tune2fs, mkfs.ext3 and mkfs.ext4, maybe I can migrate the filesystem to ext3 or 4. It's not clear whether the kernel supports those filesystems or not though.

Fingers crossed.