Skip to main content

Boot ltsp from NT/2K/XP

This week I have been tasked with the setup of a Linux terminal server for a press room with 15 terminals (mostly used for OpenOffice, browsing and printing). The terminals are refurbished pcs with intel II processor and 128MB of ram.
In case the terminal servers failed I decided to keep the original hard drives and install NT4 on them. I also set a small FAT partition apart for installing the linux kernel necessary for bootstrapping the client.

I installed Fedora Core 3 on the two servers (they roughly share the load) and chose KDE as the default desktop environment. Then I installed LTSP.
For the initial phase I went with bootable floppies, but after the setup was considered stable I wanted something installed on the local hard drive of the terminals.
After some googling I found syslinux. SYSLINUX is a bootloader that can be used to boot the zlilo images from rom o' matic.
The installation is very easy: I downloaded and uncompressed syslinux on the NT box while I was running NT, then I ran win32/syslinux.exe and installed syslinux on partition d: (the partition must be FAT).
After that I copied the zlilo image in d: and renamed it to linux (this is the default kernel booted by syslinux).
At this point I needed to make the NT boot loader aware of syslinux, so I stripped off the boot sector of partition d: and added it the the boot.ini file.
This is a straightforward process: run the copybs utility that comes with syslinux and save the sector to the c:\ts.bss file. After that modify boot.ini to include the new entry, make it the default, shorten the timeout and reboot.
The whole process can be easily automated with the help of a trivial batch file.

Et voila'

Comments

Popular posts from this blog

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …