Slug installation, part 2

From the first part we inherited a slug (= a Linksys NSLU2) with a debian installer started. Now, the slug doesn’t have a console, so we need to access the installer through SSH:

ssh installer@192.168.1.6

Accept the new RSA key fingerprint (you may have to delete the previous key first, the RSA key is regenerated when you reflash), and type in the password “install”. You should be greeted by this screen:

Choose “Start menu” to be taken to the installer. Then you have to chose a mirror to download the Debian archives from. I think the list shows all servers, although we’re really only interested in those that has packages for ARM. Use the Debian mirror list to make sure the mirror you select carries packages for the ARM architecture before you continue. (I’ve had problem with ftp.sunet.se before, although when I check now I see that it actually has ARM packages. Well, maybe it was something else that didn’t work then.) The primary mirror for your country is usually a sensible choice.

Next up is choosing which modules to load for the installer. The guide I followed recommended these modules:

• ext3-modules…
• partman-auto
• partman-ext3
• scsi-core-modules…
• usb-storage-modules…

We won’t use automatic partitioning, so I don’t know if partman-auto and partman-ext3 is really necessary, but it doesn’t hurt anyway.

Then we go for partitioning the disk. I used manual partioning and created a root partition (ext3), and a swap partition on the USB memory stick. Since we will be running LDAP on this box, I figured I need some swap for caching and doubled the minimum requirement of 128MB (to 260MB). Write your partitions to disk and format them (you didn’t choose to format them at the partition screen? then go back and do it right).
Next you are told to choose a language, but I don’t know what this choice really means. It certainly doesn’t change the language (I chose Sweden, but didn’t get Swedish). Maybe it is the time settings; At least it says “configuring the clock” next. Anyway, just chose your country and continue.

Then it is time to create users. First you create a root user (you only have to give a password for him) and then you also set up a regular (non-privileged) account.

After you’ve set up users the base system will be downloaded and installed to the USB stick. Answer any questions about these packages that may come up (it shouldn’t be too difficult). After installation the tasksel dialog appears:

The “Standard system” should be enough here, we will install the packages we need for the file server later. Now it will download and install some more packages, and this should take a while (I didn’t take time, but upwards an hour perhaps). When it is done you should see the following message:

Choose “Continue”; You will then be disconnected from the slug. Wait a while (ten minutes?) and then log in with the login credentials for the user you created before (you could log in as root, but it is prudent not to).

And that’s it. You can start playing around with your new toy, as will do now with mine.

Slug installation

Our first task is to reflash the Linksys NSLU2. This box will later be used as a file server at Valhall, though it currently stands silently at Bilskirnir.

Now, I actually already reflashed it with Debian/NSLU2, but I though I’d redo it to document the process. There is already a quite good document describing the installation process. This installation guide will be more specific, however, describing how I got things to work.

A look at what we need for this task:

• A slug (not a slimy one, I mean a Linksys NSLU2)
• A installation medium for Debian (it won’t fit in internal flash); I used a 2 GB memory stick
• A computer running Kubuntu
• A switch and some network cables
• A lot of patience (the Slug isn’t very fast) and some coffee

First, we put all the equipment in place:

1. Connect the slug to a power outlet.
2. Connect a network cable from the slug to the switch.
3. Connect a network cable from the computer to the switch (I use wireless normally, but this don’t work for reflashing with upslug2).
4. Connect the memory stick to USB port 1 on the slug (port 2 probably works, but I haven’t tested so I can’t confirm this).

Power on the slug and set it to receive a IP address via DHCP. (Information about this can be found in the manual, I think.) When done, power off the slug again.

Ok, let’s download all the programs we need to the laptop. The binary image for the Debian Installer (with Intel’s proprietary network driver) can be found at slug-firmware.net. At the time of writing the most up to date image is Etch RC2, so I grabbed that one. You have to accept Intel’s license before you download. I don’t think there’s any indecent stuff there, but then I just skimmed it (and I’m certainly not a lawyer). We also need the upslug2 tool which I downloaded with apt (for Kubuntu, it is in the Universe repository, be sure you enable this first):

sudo apt-get install upslug2

Next, put the slug in upgrade mode:

1. Press and hold the reset button with a metal clip (the hole is quite deep, so a pen won’t do)
2. Power on the slug without releasing the reset button
3. The top diode () shines yellow for approximately 10 seconds – keep the reset button down.
4. When the top diode turns to amber (the change is quite subtle, be sure to do this in a dark room) immediately release the reset button (you have at least a second I think).
5. The diode should now flash amber. If not, restart the process.

As far as I can tell, the slug will stay in upgrade mode until you reboot it, so you don’t have to hurry starting the reflash.

Now go back to the Konsole window you should have started, and type:

cd
mkdir slug
mv download/debian-etch-rc2-20070308.zip slug/
cd slug
unzip debian-etch-rc2-20070308.zip

Now run the upslug2 tool to reflash (upslug2 has to be run as root because of how it interacts with the network interface):

sudo upslug2 -i di-nslu2.bin

The installation process should begin. The upslug2 tool will report the MAC address for the slug. Use this to set up a static lease for it. I set it to 192.168.1.6 for this.
When the installation finished (it says “Rebooting… done”) you have to wait a while (5 minutes perhaps) before you can log on to your debian installation via SSH.

Coming up, the Debian Installer….

The beginning

First, let’s see what we’ve got to work with. This project won’t build a network from scratch, but rather build upon the things that already are there. Much of the existing equipment will be rebuilt however to make things more streamlined. Today, it’s just one step away from chaos, and a lot of work will be devoted to shaping things up, with a proper network layout.

The current network is spread across four different locations, which will be called Bilskirnir, Trudvang, Glitner and Valhall. Bilskirnir has internet access through a wireless link to Trudvang, the other locations (including Trudvang) has direct access to the internet.

At Bilskirnir we have the following equipment:

• A laptop running Kubuntu (this is where I’m writing this from)
• An old desktop PC running Ubuntu server (and nothing else really)
• An even older desktop PC running Kubuntu (I think, haven’t started it for a while)
• A somewhat newer desktop PC running Debian (this was my main box before the laptop came along)
• A network attached printer
• A Linksys wireless AP to connect to Trudvang
• A Linksys NSLU2 (commonly called a slug)
• A switch, some network cables and other stuff

At Trudvang there is:

• A desktop PC running Windows (this box won’t really be used in this project, it just shares the internet connection with the other boxen)
• A laptop running Windows (this won’t be used on the network either for now, but possibly later)
• A Linksys router (WRT54G) running DD-WRT
• Some cabling and stuff

I’m not quite sure what equipment there is at Valhall, but something like this:

• A laptop running Windows
• Another laptop running Windows (this computer belongs to another company and can’t really be used in the network)
• An old desktop PC running Windows
• A hub to connect these boxen to the Net (they will thus have separate public IPs)
• A local printer
• Network cables all over the place (since there is no wireless) and some small stuff not worth mentioning

At Glitner there is also some uncertainty about what equipment there is, but it should be:

• A laptop running Mac OSX
• Another laptop running Windows (won’t be used on the network I think)
• A wireless router of unknown model (I know it isn’t a Linksys)
• Cables and stuff of course

Well, I think that’s it. I probably forgot some stuff, but nevermind. We can cover that later.