While I don't think linode allows to install an OS directly from an ISO, they do allow you to transfer your own OS images. Here are instructions on how to build and transfer an image on linode. This can be good if you want to deploy your own customized image(s) more quickly (see Running a Custom Linux Distribution on a Linode in below link). There is instructions for deploying distro specific/custom kernels as well. This lacks slackware specific instructions, but could work if you want to go this route.
https://www.linode.com/docs/tools-re...rnels-distros/

The stock image is very barebones, but really the problem with it was since they left you with a mostly empty packages dir as you could not see what they did.

I suppose you are already well past this, as am I. But if there is a next time, this is what I am keeping in mind.

I would think running a custom kernel would be bad. (custom as in a kernel not chosen by linode) Linode choose a kernel that support their hardware and runs well inside a VM. One reason you'd need a newer kernel is hardware support ... but that'll never be the case in a VM. The noop scheduler is probably the best for VM's so really, what would you need a different kernel for?

On the off chance Xen can merge (or share) common code pages between multiple vm's, then having 10 VM all running the same kernel could save a good chunk of ram.

linode kernels should have a decent tick rate MHz (or even tickless). (you want to be a good neighbor, right?)

Tech support wise, the linode devops will be able to help you if you are running a kernel they understand.

All I see are pluses for running linodes recommended kernels. No minuses.

1 members found this post helpful.

All good points.

I was initially surprised to find that I was not running a Slackware kernel, then a little confused until I had a chance to think through how that affected my uses. Then I thought, "OK, let's continue and see where this becomes a problem...".

So far it hasn't, and I like the performance of my baby sized linode.

Do you know if they enforce upgrades of their kernels on installed linodes, or do I run with this one until I decide otherwise?

It is quite difficult to get all this up and running indeed. It took me a while to get a nice mail server up and running with Postfix and Dovecot but then my ISP decided to give us private addresses. And that was the end of that!

Heh:

$ uptime
14:05:25 up 234 days, 19:17, 1 user, load average: 0.00, 0.01, 0.05

$ uname -a
Linux 3.14.5-x86_64-linode42 #1 SMP Thu Jun 5 15:22:13 EDT 2014 x86_64 Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz GenuineIntel GNU/Linux

I kinda recall a config page where you could select your kernel. But its been 234 days since I've even reboot it, let alone choose a kernel. Not even sure, do they even have kernel 3.14.5 as an option anymore?

Ok, I was curious, so had to go look. Its in the Configuration Profile, there's a drop down for the kernels. 3.14.5 is listed, and even still supported. 3.18.3 is current.

I am using the linode 3.18.3 kernel. I agree with what you said on customizing your own kernel. There is no reason to add your own here since the linode kernel already is built to the target system. And there is usually no issue with using newer kernel than what came with slackware.

For any still interested, I have written a first cut of a how-to based on my own virtual mail server now running on my VPS...

Creating a Virtual Mail Server with Postfix, Dovecot and MySQL

I hope someone finds it useful - all constructive comments appreciated, others ignored!

4 members found this post helpful.

Hi,

My LINODE server: Last reboot was not really required...
Almost non-stop since I registered a LINODE VPS 2 years ago. I've been using it happily for 2 years for another company before that.

Great uptime, great service. Slackware + Linode is a pleasure.

Enjoy.

This is a great and welcome addition to docs.slackware, and one I will definitely be using. Good work.

Thanks! I hope you find it useful!

I have a few additions and changes to make to the Slackdocs article, but I ran up against the clock getting it posted yesterday. So while I think it is complete and correct as it is now, you should see a few improvements later in the week, hope they do not confuse.

All feedback appreciated - please let me know if you have any problems!

My Linode uptime

Hi,

I found this post helpful since I want to move my VPS to linode.

Currently I have a VPS at Digital Ocean and I installed slackware64-current using kexec over an Ubuntu kernel, so I boot the kernel provided by DO and then I run kexec to load the slackware current kernel and an initrd.gz, so I can use the packages from current. I would like to know if could I use the slackware64-current packages with the kernel provided by linode? or is slackware-14.1 the latest that I can run on linode?

My idea is to migrate the server through rsync as it is configure now.

Thanks in advance.

The Linode Slackware 14.1 is actually Slackware-current. The mirrors are configured to point to current out-of-the-box.

1 members found this post helpful.

You mean slackpkg is configured to point to slackware-current. The linode image is certainly 14.1 and not current.