What do you think about including Mate desktop in Slackware?
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.
So? Slackware is NOT a Democracy and it never was. I guess you missed, but the letter D from BDFL stands for Dictator.
It's not really dictatorship. If to build analogy in this direction, this is more like feudalism with all the attributes like feudal fragmantation with couple of seniors and nominal king, serfs and subsistence economy.
It's a benevolent dictatorship. Our maintainer has the final say on what is added and removed from Slackware. Period. Mr. Volkerding makes the final call on Slackware development.
He has a trusted group of Slackware developers who do an amazing job assisting him with our next stable release. This development model works.
In general you need initrd no matter if your kernel is huge or generic. Think about LUKS and/or LVM, for example. You will just not boot the system without initrd.
This is false. You need an initrd if your specific system requires it. If you're not using LUKS or LVM (which based on the forum, is probably the vast majority of people using Slackware) and using a huge kernel, you don't need an initrd.
And the -current installer now generates an initrd and sets the system to boot off the generic kernel. Pat has long preferred people using the generic kernels (and has said so in the documentation on the installation media), but has finally decided to make it automatically use the generic kernel.
Quote:
Originally Posted by I.G.O.R
Slackware setup forces you to do most of the important things manually. The rest of the things like boot loader and fstab you will most likely reject/rewrite. And there is huge list of missing features.
You mistake that since you need to do things to the bootloader or fstab after that everyone does. I was able to boot that test system without touching the bootloader or fstab beyond what the installer does.
Quote:
Originally Posted by I.G.O.R
Do you really believe that inability to install Slackware with usbboot+wireless can be considered as "fundamentals"?
How hard is to to download the whole ISO and write it to a USB drive? I really don't think using the usbboot is very common.
Quote:
Originally Posted by I.G.O.R
I would be happy to use Slackware installer, but I do not see any reason. I don't use buggy/incomplete/bad things and I don't want to lie to myself. You may call me not intended Slackware user or whatever labels accepted by local tribe cult.
You're not required to use the installer. The installer is there to help people install Slackware, but you can still install Slackware without it.
Keep calling us a cult even though we are no different than passionate users in other distros. We like Slackware as it does what it needs to do for us. If Slackware were changed for every user who came in here and complained about something (or many things) they don't like, Slackware wouldn't be what it is anymore. That might be better for you, but it wouldn't necessarily be good for the current Slackware user base.
This is false. You need an initrd if your specific system requires it. If you're not using LUKS or LVM (which based on the forum, is probably the vast majority of people using Slackware)
Well, if most of the "intended" slackers do full install, I am not surprised about low demands of an "average" slackware user. They really don't need anything, they can just switch to NT 4.0 SP7.
Well, if most of the "intended" slackers do full install, I am not surprised about low demands of an "average" slackware user. They really don't need anything, they can just switch to NT 4.0 SP7.
They don't need anything special in the installer. If you stay on the forum, you'll see a lot of people have modified Slackware to fit their needs. Some have added systemd, others have made it into a DAW, others have rebuilt it from scratch.
Slackware, and its installer, is designed to get someone to a good starting point. Where they decide to go from there is up to them.
Quote:
Originally Posted by I.G.O.R
Are you talking about -current? :-)
Stable release ISOs are obviously available on pretty much any Slackware mirror, but -current ISOs are generated by Alien Bob and provided through several different mirrors. A simple google search of "slackware current iso" will lead you to several of those mirrors. You can also generate your own ISO using his handy "mirror-slackware-current.sh" script, which is designed to mirror -current, but can be used for any Slackware tree on a mirror. I use it to mirror -current and 14.2 onto my personal network.
Quote:
Originally Posted by I.G.O.R
Slackware installer doesn't help, it misleads and distracts potentially new users.
How does it mislead and distract new users? Other than a few times specific input is needed, generally hitting enter a bunch of times will lead to the installer succeeding in installing Slackware. From there, you reboot and you're greeted with a login. Continuing to read the documentation will lead you to create a user and issue startx.
If new users are keen on setting up lvm or luks, they probably have enough experience with Linux to be able to make the needed adjustments that the installer doesn't provide. Pat does not intend on Slackware being a distro for everyone.
Slackware installer doesn't help, it misleads and distracts potentially new users.
The last stable version is 14.2 . This is what can we really talk about. It is outdated but there is no other stable release. Anyone running -current should be aware that it is unstable system. Such person should be ready to resolve issues on its own. And be ready that problems, crashes may appear. So who is that hypothetic new potential user? The picture tells us that the person needs to be advanced Linux user first of all. Do you see many such people around willing to stop using distro they use now to switch to Slackware? Don't think so. We may talk about new potentiall users when Slackware 15.0 will be officialy released.
The last stable version is 14.2 . This is what can we really talk about. It is outdated but there is no other stable release. Anyone running -current should be aware that it is unstable system. Such person should be ready to resolve issues on its own. And be ready that problems, crashes may appear. So who is that hypothetic new potential user? The picture tells us that the person needs to be advanced Linux user first of all. Do you see many such people around willing to stop using distro they use now to switch to Slackware? Don't think so. We may talk about new potentiall users when Slackware 15.0 will be officialy released.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.