SysAdmin Adventures

My DRBD SlackBuild has been updated for 8.3.7 and split into two: drbd-tools and drbd-kernel.

They have been submitted to SlackBuilds.Org and are pending submission. They have been updated for proper Slackware64 compatibility and include notes regarding DRBD entering the Linux Kernel as of kernel 2.6.33.

TAKE NOTE:
Slackware{,64}-current has moved to kernel 2.6.33. DRBD’s kernel code is now part of the Linux kernel. You should not attempt to install drbd-kernel on a system with a 2.6.33 or later kernel. While it is technically possible, version 8.3.7 will not compile externally against 2.6.33. A fix is pending for the next release of DRBD but is nonetheless not required.

Users of Slackware{,64}-13.0 and earlier should use both packages.

DRBD v8.3.7 Kernel Module SlackBuild
DRBD v8.3.7 Userland Tools SlackBuild

Finally got around to making a SlackBuild for DRBD. Made a little easier by the introduction of a configure script into the DRBD source.

The script is available below and has also been submitted to SlackBuilds.Org.

Have fun.

DRBD SlackBuild (v8.3.6)

• SlackBuild updated on 12/11/2009 for better handling of kernel source dir.

UPDATE 20100304:
DRBD 8.3.7 has been released and new SlackBuilds are available:
http://blog.tpa.me.uk/2010/03/04/drbd-8-3-7-slackbuilds/

I have a new page up detailing my adventures in putting together a brand new storage system here at work with the primary purpose of increasing redundancy, reducing cost and increasing efficiency.

The page itself doesn’t look very good because I am still fighting with wordpress. I finally pick a theme I like, but the header css is god-awful. I’m no graphic designer and I thought WordPress was supposed to take care of that, well it doesn’t.

The link:

http://blog.tpa.me.uk/high-availability-storage-with-slackware-drbd-pacemaker/

Ok, so your box is completely locked up, nothing you do with the keyboard and mouse does anything with the OS. You’re about to hold in the power button for a forced reset..

WAIT!

Try the Magic SysRq key. All the Slackware default kernel have it compiled-in.

It’s not easy finger-wise, but hold down Alt and the SysRq key and while doing so, type in the following in order:

R E I S U B

Fingers crossed you just rebooted your machine without breaking it.

For more information:
http://en.wikipedia.org/wiki/Magic_SysRq_key

Ok, so I’ve made clear how I feel about using an initrd to boot your generic kernel. I also think that running the huge kernel on a permanent basis is equally insane. So I guess I’d better tell you about the alternative: compiling your own kernel.

I should make it clear straight away that by no means do I consider the kernel an easy topic for most people to deal with, nor do I think I have a full grasp on every nuance myself; but I do think that the best thing you can ever do for your system is to build your own. Needless to say there are already a million billion kernel compilation guides out there, but they all make such a big deal out of what is an unbelievably simple process, especially in Slackware.

So.. give me five minutes of your time and I will show you the process I follow for each and every Slackware box I administer that gives me a generic kernel, no initrd, and endless options for customisation should I choose to take them. It’s simple, trust me.


Compiling your own kernel in Slackware Linux in 10 easy steps…

I understand that there are rare situations in which an initrd can be useful. For example, when hardware is constantly being swapped out, or when you absolutely must have an identical kernel image, or if you are using LUKS for your / partition. However, in general an initrd is, in my opinion, a completely pointless level of complexity that you are better off without.

I’m currently managing in excess of 15 completely different Slackware installs across lots of different hardware and not one of them is running a “huge” kernel, or an initrd. If a module is absolutely essential to your system’s ability to boot, why in hell haven’t you compiled it into your kernel? It’s like having a your starter-motor in your car disconnected from the battery, but having a relay on its own mini-battery connect it up when you turn the ignition.. why would you do it? What’s the point? The car will not start without it, why is it not hard wired into the system? It’s the same for the kernel. If the system won’t start without it, compile it into the kernel. Don’t play about with an injection system you don’t even need.

Ok, so your root device is inside RAID & LVM on a GPT partition. So, compile in mdadm support for your RAID level, LVM support and GPT partition support; job done.

For the less experienced, it’s also a good way to learn the basics of kernel compilation without needing to do much more than follow a standard process. All you need to do is use the config from the generic kernel you were going to boot anyway, and knowledge of what filesystem your root device is installed with and what storage controller your disk uses. Go into the kernel config, add them in [*], make, make modules_install, move and symlink the new kernel, update lilo, reboot. Once you’ve done it twice, it becomes so routine and easy you’ll wonder why you haven’t been doing it forever.

Then, once you’re more familiar with the process, you can start removing other parts of the kernel you don’t need, especially hardware controllers for hardware you don’t have, with each step making your kernel smaller and your system leaner and faster.

Have kernel, will compile.

Post followed-up by:
Compiling your own Slackware kernel