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

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).

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.

A not so short guide to TDD SaltStack formulas

One of the hardest parts about Infrastructure As Code and Configuration Management is establishing a discipline on developing, testing and deploying changes.
Developers follow established practices and tools have been built and perfected over the last decade and a half. On the other hand sysadmins and ops people do not have the same tooling and culture because estensive automation has only become a trend recently.

So if Infrastructure As Code allows you to version the infrastructure your code runs on, what good is it if then there are no tools or established practices to follow?

Luckily the situation is changing and in this post I'm outlining a methodology for test driven development of SaltStack Formulas.

The idea is that with a single command you can run your formula against a matrix of platforms (operating systems) and suites (or configurations). Each cell of the matrix will be tested and the result is a build failure or success much alike to what every half-decent developer of…