Slackware on linode
 

Hi All

I'm wondering if anyone has thoughts or tips regarding package updates/security fixes for Slackware running on Linode.

I generally keep to the most primitive package management tools (installpkg etc) on my desktop machines, and am perfectly happy with doing my own dependency management, so it's not a matter of tools...but given the somewhat non-standard installation of slackware on linode (kernels, default apps/libs etc) I'm a bit nervous just naively applying updates from the main slackware site in-case I break something. The slackware-specific docs on the linode site are mostly a nice overview of the options for package management, but don't seem to deal with linode-specifics (if indeed there are any to worry about)

Any tips?

Whether you use upgradepkg (you can't since linode image has a broken /var/log/packages), or installpkg, existing config files will not be overwritten. So if you did start with a linode image like I did, then it is simply identifying which packages and exact versions actually are on the system, and reinstalling them with installpkg. I guess if you are really anal about it, you could just repopulate /var/log/packages with the necessary files to reflect what is installed via a special script, before you do anything else, then upgradepkg. But installpkg'ing does give you the missing file, even if it is more work. And you can review what config files they changed.

The slackware 14.1 linode I tried out had what I believe was an improperly configured slackpkg config. You can use that to update your system, but please carefully check it. Personally I don't use slackpkg, but I checked it anyway as a clue to what they might have done to the image before posting it online. Then I fixed in case I ever use it. But I don't use it, and I loaded my own scripts that use pkgtools.

So did you install a slackware 14.2 image? I haven't tried that image. I did create a script to guess the packages installed on 14.1 because the broken package database. Somebody needs to tell the linode people not to break the package database...

Thanks the3dfxdude for your response. It is helpful.

I'm on 14.1 at the moment. I have not tried 14.2 either.

I will take your advice and stick to installpkg, but my main worry lies with feeling secure that I can use packages from the official Slackware security advisories pages (http://www.slackware.com/security/li...ecurity&y=2017 etc) without killing my server, esp when it comes to kernel-fixes and other low level bits.

I've only used the 14.1 image. As others have said, /var/log/packages is broken. They have -current selected by default in /etc/slackpkg/mirrors . You'll most likely need to slackpkg reinstall the a/, ap/, d/, l/, and n/ package series. If you set the date and then install glibc-zoneinfo /etc/localtime may get corrupted. I cancelled my account a few weeks ago so I can't check a new image quickly but as far as I remember they generated SSH keys for themselves in /etc/rc.d/rc.local or /etc/profile (probably for management). It could have been another provider, though. Last but not least, they use their own kernel. All in all I wouldn't recommend it. You're better off renting a cheap bare metal server and installing Slackware from scratch by booting a rescue CD, wgetting the minimal .iso, and chrooting. Loads of people recommend online.net. I use them too but be warned they have the worst support. Agents that don't care about customers and are rude. You put in a ticket and no one bothers to read it and recommends (asks) things that you've already taken care to explain. If you're absolutely sure you'll never submit a ticket then the pricing alone is worth it.

Linode
4GB RAM
2CPU
48GB SSD
$20 USD

16GB RAM
2.4ghz CPU
250GB SSD
$15.99 EUR ($17.00 USD)

I currently run three linode instances of Slackware 14.1.

Like others above I do not use slackpkg on it, but I use installpkg/upgradepkg and Slackware repo for most security updates.

I build my own apache on one and use the Slackware package on the others.

I have been very happy with this arrangement using the latest linode kernel (mostly). I originally built my own kernel on Linode, but that was more trouble than it was worth to me. I then selected a particular linode kernel for a while and finally went with the latest linode built kernel option. I have had no problems using their kernels and Slackware packages.

I too, have not yet deployed a 14.2 Linode.

When I mention using installpkg, I meant it only to fix the broken package database for the missing entries in /var/log/packages. After it is fixed, then you can use your update method as normal (i.e. upgradepkg/slackpkg)

By all means, ensure that you do obtain the security patches with the method you choose. I don't know how critical your server is, but I it was critical, I would stage the updates first, possibly in your own VM, work out the necessary changes, and then follow the learned steps. I think that slackpkg can be made to work, but make sure you move to a 14.1 mirror, and not use a -current mirror.

Thanks all. I appreciate your comments.

I get kind of worried, as I use a lot of custom packages on my remote server also.
What I do is run a mirror server in VirtualBox on my local box to test upgrades before I load them.

Don

I, too, run 14.1 on a linode vm. Downloading .txz packages to it via wget and installing them via installpkg was straightforward and I have no complaints.

I didn't really care for the Slackware image Linode provides, so I rolled my own. Currently running Slackware64 14.2 on a Linode fully virtualized guest (as opposed to the standard para-virtualized guest). Behavior is nearly identical to physical hardware. Package management is done the same way you would do on any machine. You can roll your own on a PV guest too.

Thanks again all. I appreciate all the input. Since the original post I am simultaneously running a 14.2 install also, and it's going well. I am sticking with good ol' installpkg for now in both cases.

One thing that surprised me on 14.2 was the lack of perl by default, which I can't remember being the case with 14.1.

Anyway, cheers.

I am not sure to understand what you mean, but perl (version 5.22.2) is of course included in Slackware 14.2. So you should have it if you made a full installation.

I think that he talks about the "stock image" provided by LINODE.

BTW, a bit late but I use slackware on Linode, I had to manually install some missing packages (like... package management :) ). But it works well with slackpkg too.

If I may, I have a question myself, at the time I rented my LINODE it was a 32bit machine, since then they migrated to 64bits machines, and I should do a "full-reinstall"... I'd like to know how you do for two things:
- get an image of the actual server (I have some kind of backups, and my work is inside git repos, but it could be "safer" to just flash everything in a ISO and download it.
- use a custom ISO to install..

I was thinking about renting a second LINODE just to be able to do the snapshot easily, but I'm not sure it'd really help.
Also I've read some stuff about using a custom image some time ago in the LINODE docs, but it was not clear. Now I see that there's a way through Finnix ?

Anyway, did anyone used that Finnix too to upload a custom Slack ISO (From the VM) ? I don't get how to translate the virtual disk to an usable "ISO" for LINODE (or did I miss something?). Also what might differs is that I use VMPlayer and not virtual box.

Info got from: https://www.linode.com/docs/tools-re...n-a-linode-vps

Anyone with this experience ?

Bests,

Garry.

Garry,

I think the simplest thing to start with is the kernel. The stock linode kernel should have everything needed to boot the vps. You don't have to build your own kernel. The rest of stuff are just the packages loaded. You shouldn't need to rebuild packages in slackware for the vm environment.

The linode tutorial about creating your custom image is sound. Just build your slackware image locally in a vm. Don't worry about the kernel too much, just build it based on available vm install guides. Then migrate it to linode just as they suggest and use their kernel.

Thank you, yeah in fact I just have to take the time to give it a try... It's just I'm in another universe than admin'ing my VPS right now ;).

BTW, your user name looks like 20 years old ! :) Did you work with the 3D FX at the time ? Or did you played some games (like Tomb Raider ?).