Hello SlackWorld:
I heard about hostus.us from
this thread, and, wanting a slackware VPS, I signed up for unmanaged VPS, logged in, chose rebuild and selected the slackware64-14.1 minimal template. Once it was done and I could ssh into the VPS I did the following:
- I created a directory to contain slackware64-14.1 tree, and then used rsync to obtain a local copy of the slackware tree, because I use many packages that didn't come with the minimal template, such as zsh, emacs, etc.
- I don't want to mess up my virtual container, so I thought I would play inside a fresh chroot. I created a directory (myroot) for the fresh chroot, and then used i
Code:
nstallpkg --root myroot a/*.t?z ap/*.t?z e/*.t?z
, and did this for everything except kde, x, xap, and y, which I don't need because I don't plan on running X inside this container.
- I did the
Code:
mount -o bind /proc /myroot/proc
and the same thing for /sys and for /dev, and then I attempted chroot and received error:
Code:
root@lax:~# chroot /myroot
FATAL: kernel too old
Hmm... so I tried to learn about the kernel:
Code:
root@lax:~# uname -srov
Linux 2.6.32-042stab113.11 #1 SMP Fri Dec 18 17:32:04 MSK 2015 GNU/Linux
. The same command, on any other slackware64-14.1 system I have installed yields
Code:
uname -srov
Linux 3.10.17 #2 SMP Wed Oct 23 16:34:38 CDT 2013 GNU/Linux
I concluded that the openvz container is running an old kernel... I check /boot and it's empty.
Is there a way to get linux kernel 3.10.17 functionality out of the hostus.us slackware vps?