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.
Is there any way to bootstrap Slackware from a source medium like the way that Gentoo installs?
From what I read, Slackware is not a source based distribution like Gentoo, but it is shipped as a set of binary packages, just like Fedora or Ubuntu.
There is a project named Slackware From Scratch, which has the objective, well... to build the Slackware from scratch, but I do not think it is of general interest as a way to install Slackware, but rather to find a way to (re)build Slackware by the advanced users and/or developers.
Last edited by ZhaoLin1457; 06-01-2019 at 02:26 PM.
Thank you. Seriously appreciate the offer. I was thinking of a way to install Slackware from source which is a little over the top. About to enter some certification courses for RHCSE and more. Want to try to get an old Friend (Slackware) working on relatively new hardware. A project of sorts. Ill try a standard SMP kernel tomorrow and with Aliens upslack.sh script I can upgrade the kernel on usb stick as long as its a Slackware package or existing image. Adds fallback menu entry automatically too. If I do a nop on boot it should avoid persistence and make for a clean way to do. Need to get working DRM on amdgpu in a gui before committing to installation.
Thank you. Seriously appreciate the offer. I was thinking of a way to install Slackware from source which is a little over the top. About to enter some certification courses for RHCSE and more. Want to try to get an old Friend (Slackware) working on relatively new hardware. A project of sorts. Ill try a standard SMP kernel tomorrow and with Aliens upslack.sh script I can upgrade the kernel on usb stick as long as its a Slackware package or existing image. Adds fallback menu entry automatically too. If I do a nop on boot it should avoid persistence and make for a clean way to do. Need to get working DRM on amdgpu in a gui before committing to installation.
Thanks again!
If you just need things that are more recent, you can always try -current. It is the development version that will eventually become Slackware 15.0. There is always the possibility of bugs with it, but it usually runs great with the occasionally rare breakage.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Here we go, again.
Another round of updates has been scheduled for release on Wednesday morning, GMT.
If no problems are found while testing the release candidates, they might be available sometime Tuesday (depending on your time zone).
There will be fewer patches this time around. Forty for 5.1.7, thirty-six for 5.0.21 and thirty-two for 4.19.48.
And, please keep in mind.....
Quote:
Note, this is going to be the LAST 5.0.y kernel release. After this one, it is
end-of-life, please move to 5.1.y at this point in time. If there is anything
wrong with the 5.1.y tree, preventing you from moving to 5.1.y, please let me
know......
Thanks for the heads up, cwizardone, did you notice any reason why 5.0.x is so quickly coming to EOL?
This is pretty common on non-LTS kernels. They'll release a new kernel and the next month they'll EOL the previous one (unless it is an LTS, obviously). So, since 5.1 was released in May 2019, 5.0 will be EOL in June 2019.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Usually, every fifth kernel release is designated, LTS. If Greg K-H continues to follow that policy it could be October before we see the next Long Term Service kernel.
Usually, every fifth kernel release is designated, LTS. If Greg K-H continues to follow that policy it could be October before we see the next Long Term Service kernel.
Which means Slackware 15.0 wouldn't be out till at least early Autumn.
Which means Slackware 15.0 wouldn't be out till at least early Autumn.
Unless Pat releases it with the current 4.19 kernel, which is a LTS one (although all recent kernels - even the LTS ones - are not very stable yet and it isn't likely 5.3 will be more so).
Kernel updates from 4.9 upwards still happen at least once a week and the 4.19 and 5.x ones TWICE a week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.