SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ich have found slackware os as one of the top ten linux server os.
Now i want to install it on my vs2-free, but currently i can not install it via customer panel.
Is there an alternative option to install slackware on it.
ich have found slackware os as one of the top ten linux server os.
Now i want to install it on my vs2-free, but currently i can not install it via customer panel.
Is there an alternative option to install slackware on it.
Did you told them that your intention is to install Slackware, which does not have systemd?
Permit me to doubt that Slackware is compatible with a server driven by systemd, which uses Linux Containers...
Because the Slackware does NOT uses systemd, but a customized SysV init - with EUDEV and ELOGIND, which both are parts of systemd, split on stand-alone trees.
I am not a server administrator, but friends of mine who are says that's pretty bad idea to run a Linux Container using ELOGIND on top a host which uses systemd. And that the vice-versa is valid too.
Yeah, this seems to be a disadvantage of Slackware swimming against the river.
I for one, I will recommend you to install one of their system images and call a day.
OR, you can as well make your own Slackware with systemd (replacing SysV init, EUDEV and ELONGID with it) for installing on that server.
Quote:
Originally Posted by iamsteff
is there a Slackware rootfs image present?
In the end, you are looking for an image ... for what? There are hundreds of solutions based on Linux Containers. Which one is used by that server host?
Last edited by LuckyCyborg; 06-01-2023 at 04:39 AM.
Did you told them that your intention is to install Slackware, which does not have systemd?
Permit me to doubt that Slackware is compatible with a server driven by systemd, which uses Linux Containers...
Because the Slackware does NOT uses systemd, but a customized SysV init - with EUDEV and ELOGIND, which both are parts of systemd, split on stand-alone trees.
I am not a server administrator, but friends of mine who are says that's pretty bad idea to run a Linux Container using ELOGIND on top a host which uses systemd. And that the vice-versa is valid too.
Yeah, this seems to be a disadvantage of Slackware swimming against the river.
I for one, I will recommend you to install one of their system images and call a day.
OR, you can as well make your own Slackware with systemd (replacing SysV init, EUDEV and ELONGID with it) for installing on that server.
In the end, you are looking for an image ... for what? There are hundreds of solutions based on Linux Containers. Which one is used by that server host?
Hi,
thanks for your help. I didn't know that lxc requires systemd. From what I read, lxc is a paravirtualization based on the kernel. So chroot on steroids (based on kernel namespaces, network namespaces and cgroups). Well, I learned something again.
thanks for your help. I didn't know that lxc requires systemd. From what I read, lxc is a paravirtualization based on the kernel. So chroot on steroids (based on kernel namespaces, network namespaces and cgroups). Well, I learned something again.
Nope, the LXC itself does not require systemd.
But systemd and elogind steps on each other shoes when they run side by side, and exactly like you said, LXC it's something like "a chroot in steroids" , BUT not a Virtual Machine where you can run anything you want. That is what the people refuse to understand: LXC is NOT really a virtualization solution, but a better chrooting.
So, IF you run a Slackware server host (based on elogind), probably the best is to run also Slackware in a LXC container, BUT not RHEL or Ubuntu (based on systemd), for example.
Idea is simple: you should have same solution on the server host and container. Either systemd and systemd, or elogind and elogind.
You shouldn't believe me. Go ahead and install Slackware in that free server and see what happens.
Honestly, what amaze me is that, considering the server market and compatibility with it, nobody maintains (yet?) a true Slackware derivative which is systemd based, fully compatible with these "virtualization" solutions available on the Wild.
Last edited by LuckyCyborg; 06-02-2023 at 03:55 AM.
How the heck someone can install Slackware 15.0 on 100MB storage space, when only the kernel and its modules has over 300MB?
And how the heck will boot Slackware 15.0 on 64MB RAM when even the generic kernel, when extracted on memory has around 80MB, with NO additional modules loaded and NO initrd loaded? You will get "out of memory" right on bootloader.
I am all for positive articles about Slackware, BUT I for one I believe that they should present something at least barely related to reality...
Last edited by LuckyCyborg; 06-02-2023 at 08:13 AM.
Based on my notes and obvious matters, slackware 15.0 should have:
384MB RAM to boot the install disk
128MB RAM to boot finished install to shell
But if you go a more traditional install method, you're gonna need 384MB anyway
Some people have suggested very small minimum installs, so I'd guess a minimum is probable with 2GB of disk (and have extra space), but the smallest of my VPS uses 4GB, so recommended would have to be 6GB-8GB.
Of course, at least 586 processor, but I suspect the higher RAM and larger disk systems will be more common somewhere in the Pentium 2 or 3 era.
I don't think the article is based on first hand information.
For those looking for a base Slackware image you can use usbboot.img it has all you need to install Slackware. I used to mount this as rescue and install Slackware in the VPS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.