Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Something I will experimenting with soon will be a custom Slackware installation for desktop usage, for minimal WMs, or framebuffer/CLI-only usage. My plan is to omit all GTK and QT dependencies from the installation, but keep Xorg, the minimal WMs included with Slackware (twm, fvwm, blackbox, fluxbox), all the X apps that don't require GTK or QT, and of course all the wonderful CLI apps.
This thread will be a placeholder for this experiment, and I also encourage and welcome any input/advise/comments other Slackers might have as to this experiment.
As for inspiration, I look to the fine work done at LinuxBBQ with Debian sid (mostly). They have many fine releases with no GTK/QT dependencies, using a variety of lesser-known WMs, and framebuffer/CLI offerings.
You don't technically have to remove anything from Slackware. Just use OpenBox WM and xterm. A lot of problems can come up from removing packages from Slackware, which is why a full installation is always recommended, and you don't have to use anything you don't need right off hand.
You don't technically have to remove anything from Slackware. Just use OpenBox WM and xterm. A lot of problems can come up from removing packages from Slackware, which is why a full installation is always recommended, and you don't have to use anything you don't need right off hand.
Certainly, but then this wouldn't be the fun experiment that it's intended to be. Sure, I may totally bork it by not installing all the libs and such, but I will be taking a look at all the packages and carefully considering each one, based on my stated goal. For the record, I NEVER do a full installation, I always omit all KDE, and several other packages, and haven't had a broken system yet.
For a basic installation that has the base tools (including networking tools) you can see which packages are included in the mini root file systems for the ARM port: http://ftp.arm.slackware.com/slackwa..._minirootfs.sh
You'd need to add many more libraries and bits of X to get a working window manager, but it'd be a reasonable base from which to start.
Something I will experimenting with soon will be a custom Slackware installation for desktop usage, for minimal WMs, or framebuffer/CLI-only usage. My plan is to omit all GTK and QT dependencies from the installation, but keep Xorg, the minimal WMs included with Slackware (twm, fvwm, blackbox, fluxbox), all the X apps that don't require GTK or QT, and of course all the wonderful CLI apps.
This thread will be a placeholder for this experiment, and I also encourage and welcome any input/advise/comments other Slackers might have as to this experiment.
A very fine idea! Did you already come up with a solution for
- setting up network for road warriors (I was surprised that there is nm-applet in slackware, but you need additional software (trayers) for it to work with other window managers and I am still struggling with nmcli)
- power management (don't know about a CLI version or a light X version, so for latter I tried xfce4-power-manager, but its pop-up windows don't work well with windowmaker (pop-ups create new program icons on desktop), and if I already have to use that component from xfce, then I don't see a reason against using the rest of xfce4 either)
- suspend from CLI (well, I came up with my own script using dbus-send)
I did a minimal install back in the 12 days and it went fine. just tried with 14.1 and found that there are libraries that PHP needs in the X set and even though I installed those I still had issues. Seems things are more interrelated now.
A very fine idea! Did you already come up with a solution for
- setting up network for road warriors (I was surprised that there is nm-applet in slackware, but you need additional software (trayers) for it to work with other window managers and I am still struggling with nmcli)
- power management (don't know about a CLI version or a light X version, so for latter I tried xfce4-power-manager, but its pop-up windows don't work well with windowmaker (pop-ups create new program icons on desktop), and if I already have to use that component from xfce, then I don't see a reason against using the rest of xfce4 either)
- suspend from CLI (well, I came up with my own script using dbus-send)
I know wifi and power management are both doable from cli, but I'm doing this on a desktop machine, so I'm not worrying about those. Using anything from Xfce, including xfce4-power-manager, would require GTK and its libs, which I am avoiding.
Aside from links and lynx browsers, I am using Dillo, which works nicely. Tried netsurf, but it needed gtk stuff.
A Salix Core installation is exactly the same, no matter what iso image you used to make the installation.
After a Core mode installation, you get a total of 250 installed packages. Of those packages, the vast majority (233, 93.2%) are Slackware packages. The rest (17, 6.8%) are Salix-specific packages. The Salix packages are mainly the package manager, the Salix command line system tools and their dependencies and nothing more.
So, what you get with a Salix Core installation, is mainly a Slackware system that only works from the command line and only very few added packages by Salix. It's funny, because there are a lot of Slackware users that apparently look for a stripped down Slackware installation with no GUI, but never look at Salix.
Now, I've never tried it, but maybe you could check it out, remove Salix packages and start building up from there?
A very fine idea! Did you already come up with a solution for
- setting up network for road warriors (I was surprised that there is nm-applet in slackware, but you need additional software (trayers) for it to work with other window managers and I am still struggling with nmcli)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.