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.
This is the first installment of a series of articles I intend to write in early 2022. With Slackware 15.0 around the corner, I think it is a good time to show people that Slackware is as strong as ever a server platform. The core of this series is not about setting up a mail, print or web server – those are pretty well-documented already. I’m going to show what is possible with Slackware as your personal cloud platform.
This is a big contribution for the Slackware community!
Personally I am looking forward to this series of articles from Eric.
Thanks Eric.
7 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Tue Jan 25 08:22:34 EST 2022 [25720]: Getting ChangeLog.txt...
0a1,63
> Tue Jan 25 06:16:36 UTC 2022
> It may look like we're currently experiencing more stuckness, but this will
> lead us to Quality. We'll have this release in the can before you know it.
Wed Feb 2 22:22:22 UTC 2022 Slackware 15.0 x86_64 stable is released! Another too-long development cycle is behind us after we bit off more than we could chew and then had to shine it up to a high-gloss finish. Hopefully we've managed to get the tricky parts out of the way so that we'll be able to see a 15.1 incremental update after a far shorter development cycle.
Wed Feb 2 22:22:22 UTC 2022
Slackware 15.0 x86_64 stable is released!
Another too-long development cycle is behind us after we bit off more than
we could chew and then had to shine it up to a high-gloss finish. Hopefully
we've managed to get the tricky parts out of the way so that we'll be able
to see a 15.1 incremental update after a far shorter development cycle.
Certainly the development infrastructure has been streamlined here and things
should be easier moving forward. My thanks to the rest of the Slackware team,
all the upstream developers who have given us such great building materials,
the folks on LinuxQuestions.org and elsewhere for all the help with testing,
great suggestions, and countless bug fixes, and to everyone who helped
support this project so that the release could finally see the light of day.
I couldn't have done any of this without your help, and I'm grateful to all
of you. Thanks!
For more information, check out the RELEASE_NOTES, CHANGES_AND_HINTS.TXT,
and ANNOUNCE.15.0.
Have fun! :-)
EDIT2: I am currently downloading Slackware64-15.0 stable via mirror-slackware-current.sh and modifying the mirror-slackware-current.conf file to suit the Stable ISO build from RSYNCURLROOT="rsync://mirrors.kernel.org/slackware/". I do pass the '-r 15.0' to mirror-slackware-current.sh. Of course you will need to create the destination directories for the tree and ISO on your targets. Be patient!
EDIT3: 3.6G /mnt/sdc2/slackware//slackware64-15.0-iso/slackware64-15.0-install-dvd.iso Now to install the new SSD for 15.0.
Glad to finally have a stable release.
Last edited by onebuck; 02-03-2022 at 04:49 PM.
Reason: typo correction
An update from Slackware 15-CURRENT pre-release to Slackware 15-CURRENT post-release has basically made the boot process freeze at "Loading Linux". Amazing.
I'll investigate next week, I guess.
An update from Slackware 15-CURRENT pre-release to Slackware 15-CURRENT post-release has basically made the boot process freeze at "Loading Linux". Amazing.
I'll investigate next week, I guess.
A spin-off from our previous Episode in this series is this fifth article about using Slackware as your private/personal ‘cloud server’.
Check out the list below which shows past, present and future episodes in the series, if the article has already been written you’ll be able to click on the subject.
The first episode also contains an introduction with some more detail about what you can expect.
These articles are living documents, i.e. based on readers’ feedback I may add, update or modify their content.
Very useful and helpful for Slackware users who would like to have a cloud server.
As usual a very descriptive and thorough project by Eric!
Thank you!
For user(s) that would like to use liveslak 15.0 then;
Quote:
Live Edition of Slackware 15.0 (64-bit stable): available here!
You will find ISO images for Slackware Live Edition, created by the latest version of liveslak, in the "latest" folder below. Check the README for more detail.
The "bonus" folder contains live modules that add multilib, contain Nvidia binary drivers, expand your Live OS with a set of audio creation software, et cetera.
Also worth while:
After every update of Slackware-current's ChangeLog.txt a Slackware Live ISO will automatically be generated based on the latest & greatest. You can download and run this Live ISO image if you want to test or debug the bleeding edge of Slackware. Get it from slackware.nl!
And a Live Edition of Slackware 15.0 (64-bit stable) is always available too.
Things to remember when you boot any liveslak based ISO: ======================================================== Slackware Live does not log you on automatically! This is a demonstration environment, with the purpose of getting you acquainted with Slackware, remember? Therefore you will first see all these intimidating kernel messages scrolling across the screen while booting the OS. Then you need to login manually. The Slackware Live Edition comes with two user accounts: user "root" (with password "root") and user "live" (with password "live"). My advice is to login as user live and use "su" or "sudo" to get root access. Note: the "sudo" command will ask for the "live" user's password! Consult the documentation at: http://docs.slackware.com/slackware:...ters_explained for assistance with the various boot parameters you can use to tailor the Live OS to your needs. The syslinux boot has help screens behind the F2, F3, F4 and F5 function keys and the grub boot screen has a "help on boot parameters" menu entry.
BTW, anyways nice to have a live edition for helpful diagnostic and emergency work on your system(s).
Don't forget it's nice to have a pocket Linux for when you are away and need to Slack.
Hope this helps.
Have fun & enjoy Slackware!
Would be nice if the live edition would boot on my system. Just boots to a grub prompt.
Oh well, running and not afraid of the command line if something goes wrong from the install media.
If you find out why it is dumping you into a Grub shell instead of doing a proper boot, it may be useful to report this to Alien BOB (perhaps as a patch) so that he can fix his liveslak?
If it's grub> and not grub rescue> then GRUB has at least found its shell module. Probably it's the config file that's broken so it can't put a menu together. You can still boot from the GRUB command line. https://linuxconfig.org/introduction-to-grub-rescue
This happens when you make a slackware-live USB using 'dd' or 'cp' to copy the .iso directly to the USB drive. Grub's '$prefix' variable gets incorrectly set in these instances. When you boot a USB drive this way, you are dropped to the grub prompt. You can check the $prefix value here:
Code:
grub> echo $prefix
(hd0,msdos2)/EFI/BOOT
If you check this directory, there are no grub config files there:
Code:
grub> ls $prefix
bootx64.efi
The correct location for prefix is on (hd0), not (hd0,msdos2). You can define $prefix to point there with:
If the prefix were set to this directory properly, then grub would have automatically loaded the grub.cfg file and displayed its menu. However, since prefix was set to that (hd0,msdos2) location, nothing was found and it drops to the grub prompt.
You can load the config manually after redefining $prefix with:
Code:
grub> configfile $prefix/grub.cfg
At which point the grub menu will display and you can load the Slackware-Live OS properly.
Note that redefining the prefix variable isnt neccessary to manually boot the USB. The variable will still be set incorrectly so you will end up at the grub prompt. You can specifiy the grub config file manually with the full path:
Code:
grub> configfile (hd0)/BOOT/EFI/grub.cfg
However, some of the grub menu theming will be missing with $prefix still not being set properly.
I mentioned the prefix variable in the above because it is incorrectly set and the real fix would be to set it properly. The break happened after this commit in liveslak: https://git.slackware.nl/liveslak/co...02892abcd64c12
I've emailed Eric about this but he didnt want to revert that commit so I'm not sure what else to suggest for fixing it. What does work is to use his iso2usb.sh script to copy the .iso file over. When created that way, grub will find the config file and boot properly. I'm not sure exactly why, but the iso2usb script moves the filesystems around and adds persistance, so maybe the /BOOT/EFI location ends up matching the $prefix after that script is run.
Perhaps someone more familiar with booting grub could offer a fix other than reverting that commit?
Hi, rather than make a thread for such a small question I thought it'd be better to ask in here, I was wondering what font slackware uses on the installation ISO for the console. After installing Slackware 15.0 it's not using the same font the setup was using and I'd like to use that as my default console font. What is the font name and how do I do this? I tried searching for the font name but couldn't find any information, although I didn't try that hard.
EDIT: So after examining the installation ISO and checking the init.img, I found ter-114v inside the /usr/share/kbd/consolefonts directory. This seems correct. I ended up setting it as the default font by running `setconsolefont` as root.
Last edited by Swaggajackin; 04-29-2022 at 10:15 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.