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.
It really grinds my gears when people just post me a link, ive seen this already and dont want it. Who is maintaining this? If it's one of the Slackware devs fine, otherwise I am not blindly trusting whoever made this. This wouldn't even be Slackware anymore IMO and it even says on the site it's experimental, I'd rather not run that on my server. What happens when 14.2 comes out, I would need to wait for these guys. Thanks but no thanks.
Do you also refuse to use http://slackbuilds.org/ because it isn't run *exclusively* by Slackware devs?!
Melikamp is a helluva nice guy and also provides SlackBuilds for the linux-libre kernel here:
You wouldn't need to wait for 14.2, you could conceivably build any kernel using that build. It seems rude to me to discard someone's hard work just because they aren't part of some group.
You wouldn't need to wait for 14.2, you could conceivably build any kernel using that build. It seems rude to me to discard someone's hard work just because they aren't part of some group.
What? You're comparing apples to oranges and you're treating me disrespectfully. Freeslack is a completely different than SlackBuilds as someone in the comments noted before, here is his quote. I don't refuse to use SlackBuilds, I love SlackBuilds.org and it actually makes sense. It provides a build script and the ORIGINAL SOURCE for software. Meaning its using the actual upstream software (can be checked via checksums/md5 or whatever) and the .SlackBuild script is so small/easy to understand that you can see if any shady shit is going on, not to mention things by SlackBuild get inspected. FreeSlack is changing the entire Slackware system with someone that one random person online made...why in the world would I do that when I plan to use Slackware on my server where I will be hosting personal things? Doesn't make any sense, I am not saying what he has done is shit but simply that I refuse to use it, if someone else wants to fine go ahead, if someone asked me if I recommend it I would say no.
As for saying I wouldn't need to wait for the FreeSlack dude if 14.2...yes I would, I am not talking about just the kernel. Doing freeslack requires me changing my repository no? I am stuck on their FreeSlack 14.1...yeah I could always just compile/install the shit myself from 14.2 but then what the fuck is the point of running FreeSlack if I am just gonna do that? Sometimes you guys just think weirdly, no offence. I like keeping things organized, not having a jumbled mess from this place, then another mess from here because if I stop going on the system for a while I will end up forgetting what comes from where.
Quote:
Originally Posted by ReaperX7
...By that site, you basically cripple the compiler. It recommends removing the kernel-headers and source and install the free headers. Um... no sorry, this doesn't work that way. The kernel-headers are tied to glibc. You can remove them, but if you install non-sanitized headers it will cripple the compiler. This has been discussed many a time by an unfortunate newbie who happened to remove the headers thinking they could update the headers from a new kernel source, and not rebuild glibc, and you can't rebuild glibc without a bootstrap or an existing header set. I seriously hope they included a libre-glibc package if they intend to replace the kernel-headers package with their own.
What? You're comparing apples to oranges and you're treating me disrespectfully. Freeslack is a completely different than SlackBuilds as someone in the comments noted before, here is his quote. I don't refuse to use SlackBuilds, I love SlackBuilds.org and it actually makes sense. It provides a build script and the ORIGINAL SOURCE for software. Meaning its using the actual upstream software (can be checked via checksums/md5 or whatever) and the .SlackBuild script is so small/easy to understand that you can see if any shady shit is going on, not to mention things by SlackBuild get inspected. FreeSlack is changing the entire Slackware system with someone that one random person online made...why in the world would I do that when I plan to use Slackware on my server where I will be hosting personal things? Doesn't make any sense, I am not saying what he has done is shit but simply that I refuse to use it, if someone else wants to fine go ahead, if someone asked me if I recommend it I would say no.
As for saying I wouldn't need to wait for the FreeSlack dude if 14.2...yes I would, I am not talking about just the kernel. Doing freeslack requires me changing my repository no? I am stuck on their FreeSlack 14.1...yeah I could always just compile/install the shit myself from 14.2 but then what the fuck is the point of running FreeSlack if I am just gonna do that? Sometimes you guys just think weirdly, no offence. I like keeping things organized, not having a jumbled mess from this place, then another mess from here because if I stop going on the system for a while I will end up forgetting what comes from where.
Wow. All you need to do is grab the SlackBuild for the libre kernel, grab a vanilla source from kernel.org, compile it, and blacklist your kernel. The only other part of FreeSlack is removing a set of packages, but there is no reason that you *have* to switch the repo over to use a libre kernel.
And the setup here is very similar to SlackBuilds.org, you can look at the SlackBuild, you can grab whatever kernel you want, you seem to be making conclusions that have no root in logic.
What? You're comparing apples to oranges and you're treating me disrespectfully. Freeslack is a completely different than SlackBuilds as someone in the comments noted before, here is his quote. I don't refuse to use SlackBuilds, I love SlackBuilds.org and it actually makes sense. It provides a build script and the ORIGINAL SOURCE for software. Meaning its using the actual upstream software (can be checked via checksums/md5 or whatever) and the .SlackBuild script is so small/easy to understand that you can see if any shady shit is going on, not to mention things by SlackBuild get inspected. FreeSlack is changing the entire Slackware system with someone that one random person online made...why in the world would I do that when I plan to use Slackware on my server where I will be hosting personal things? Doesn't make any sense, I am not saying what he has done is shit but simply that I refuse to use it, if someone else wants to fine go ahead, if someone asked me if I recommend it I would say no.
As for saying I wouldn't need to wait for the FreeSlack dude if 14.2...yes I would, I am not talking about just the kernel. Doing freeslack requires me changing my repository no? I am stuck on their FreeSlack 14.1...yeah I could always just compile/install the shit myself from 14.2 but then what the fuck is the point of running FreeSlack if I am just gonna do that? Sometimes you guys just think weirdly, no offence. I like keeping things organized, not having a jumbled mess from this place, then another mess from here because if I stop going on the system for a while I will end up forgetting what comes from where.
Do you realize the freeslack repo is just a mirrored slackware repo with the non-libre software removed and the libre-kernel added in? You don't have to use that repo at all. Just remove the packages mentioned on the site and then blacklist them on slackpkg. Now you can still use whatever mirror you want. Then you can just build a libre-kernel (it's up to you to determine if you can trust his config... I'm not sure if a mainline kernel config is compatible with a libre-kernel) and your Slackware is now running completely libre software.
In fact, that is the exact instructions listed on his site. The repo is only provided as a courtesy, but it certainly isn't needed.
Quote:
Sanitizing an Existing Installation
We assume that the user performed the full install.
Blacklist the offending Slackware packages in /etc/slackpkg/blacklist by adding the following lines. Make sure they are separate lines, and also free of white space.
kernel-firmware
kernel-generic
kernel-huge
kernel-modules
kernel-source
kernel-headers
getty-ps
lha
unarj
amp
bluez-firmware
ipw2100-fw
ipw2200-fw
trn
zd1211-firmware
xfractint
xgames
xv
Build and install a free kernel. Also, install the free headers if you want to compile stuff that makes system calls. The headers are expected in /usr/include, so you will have to uninstall the stock package at this point.
At this point you should be running the free kernel, so you can remove the non-free Slackware packages with
Optionally, you can replace some of the removed packages with free packages. lha can be replaced with lhasa, a free decompressor. unarj can be replaced with arj, which is actually an archiver too.
The repo they provide is still experimental (emphasis mine).
Quote:
For your convenience, we provide a free repository for use with slackpkg. It should be regarded as experimental, so please bear with us as we are ironing out the kinks. At the same time, we are already using it, and we love it. Still, read this entire section before making a switch, since our repository differs from the stock in several important ways.
As for 14.2, you'd need to check that any packages added into the system fall under the correct licenses to be libre, but otherwise, you can still follow what is listed on freeslack.net.
As with most everything Slackware, they provide you with the information, and it's up to you on how you implement it. The only thing you need to rely on freeslack.net for is that the packages they list are the only non-libre packages in the system.
Last edited by bassmadrigal; 11-19-2015 at 08:27 PM.
Do you realize the freeslack repo is just a mirrored slackware repo with the non-libre software removed and the libre-kernel added in? You don't have to use that repo at all. Just remove the packages mentioned on the site and then blacklist them on slackpkg. Now you can still use whatever mirror you want. Then you can just build a libre-kernel (it's up to you to determine if you can trust his config... I'm not sure if a mainline kernel config is compatible with a libre-kernel) and your Slackware is now running completely libre software.
In fact, that is the exact instructions listed on his site. The repo is only provided as a courtesy, but it certainly isn't needed.
The repo they provide is still experimental (emphasis mine).
As for 14.2, you'd need to check that any packages added into the system fall under the correct licenses to be libre, but otherwise, you can still follow what is listed on freeslack.net.
As with most everything Slackware, they provide you with the information, and it's up to you on how you implement it. The only thing you need to rely on freeslack.net for is that the packages they list are the only non-libre packages in the system.
I wasn't aware I could just remove the nonfree parts, I read about getty-ps and I read something on google about processes so I thought it wasn't safe to remove so that kind of just deterred me from looking at anything else. As for all of those kernel packages, if I am still using the default kernel I certainly can't block those right...or maybe only a few of them?
I've never tried running a kernel without those additional kernel packages installed. Personally, I wouldn't try it. It'd be best to get your libre-kernel up and running and verify it is working as you want it before you start excising your mainline kernel out of your system.
Yeah the installation of linux-libre would remove support for a lot of hardware that most people use. I don't doubt that most Slackers use non-free hardware. The ones that do aim for completely free hardware/software aren't going to come complaining about not having linux-libre installed, they will just do it themselves.
Quote:
Originally Posted by gmgf
It seems that the topic here is, (Desired updates to -current)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
