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.
sure... I just thought it would save newcomers some time and headaches when they boot their system and are left wondering why it fails to boot, and it's a simple fix...
sure... I just thought it would save newcomers some time and headaches when they boot their system and are left wondering why it fails to boot, and it's a simple fix...
OK, I looked it over again and fixed a minor bug with it (if the RAID device had no partitions you'd get error spew). I'll take it after all.
For me, its absolutely essential, that the Slackware installer doesn't touch anything by itself!
Because of this, Slackware is also *the* one true rescue system out there.
After pseudo logging in, set everything up manually.
Type "setup" and there you go.
After playing with Slackware a litte bit, you will understand,
why this is one of Slackware's many features.
...
this is a heads-up that there will be Samba security updates for 4.13 , 4.14 and 4.15 on Monday, January 31 2022. Please make sure that your Samba servers will be updated soon after the release!
Impacted components:
- File server (CVSS 4.2, Medium)
- AD DC (CVSS 8.8, High)
- VFS Modules (CVSS 9.9, Critical)
...
- Copy image to clipboard option
- Fix MacOS problems
- Multi-threaded find duplicates
- Generate sRGB thumbnails for images with embedded color profile
- External image decoder option
- AppImage supported
- Support jpeg xl format
- Automated cache maintenance
- Support archive (e.g. zip) files
- Use system theme background color
And as usual:
- Many small improvements
- Many bug fixes
- Updated language support
- Copy image to clipboard option
- Fix MacOS problems
- Multi-threaded find duplicates
- Generate sRGB thumbnails for images with embedded color profile
- External image decoder option
- AppImage supported
- Support jpeg xl format
- Automated cache maintenance
- Support archive (e.g. zip) files
- Use system theme background color
And as usual:
- Many small improvements
- Many bug fixes
- Updated language support
Didier, sérieusement!
You really think my post has any influence on this?
Everybody maybe has one.
Quote:
It's a bug fix release, right?
Yes. So what? Are these bugs show stoppers? Anyway there will always remain bugs. If someone prefers a rolling release model, they can go for Arch. Do you think that Patrick decided to change Slackware's release model but did not announce that yet?
Last edited by Didier Spaier; 01-25-2022 at 11:31 AM.
Everybody maybe has one.
Yes. So what? Are these bugs show stoppers? Anyway there will always remain bugs. If someone prefers a rolling release model, they can go for Arch. Maybe Patrick decided to change Slackware's release model but did not announce that yet?
Maybe Patrick do as he wants?
Nevermind ;-)
It's been a long time since this thread has really been about requests but rather a software release log and you keep thinking that 15.0 will be released when no one posts here anymore
I have always been fine with that. Meanwhile, knowing what he intends to do and approximately when helps users, at least if themselves need to make plans.
Last edited by Didier Spaier; 01-25-2022 at 11:36 AM.
...
this is a heads-up that there will be Samba security updates for 4.13 , 4.14 and 4.15 on Monday, January 31 2022. Please make sure that your Samba servers will be updated soon after the release!
Impacted components:
- File server (CVSS 4.2, Medium)
- AD DC (CVSS 8.8, High)
- VFS Modules (CVSS 9.9, Critical)
...
Well, I have found a reference for this looking around a bit. With the word out I wonder if they'll actually wait until Monday. After missing the last soft deadline for release, I was targeting next Monday but it seems that's not a good day. We really don't want to release with a network service package in the main tree containing a 9.9 critical security issue.
I'm now targeting Wednesday 2022-02-02. We'll hope Slackware doesn't see its shadow that day.
Re EFI and kernel updates,
I just got my first EFI machine so am starting from 0 on this, so am I even taking the correct approach?
Maybe a reminder in the places that we mention re-running LILO or regenerating the initrd that both copied also to /boot/efi/EFI/Slackware?
eliloconfig overwrites /boot/efi/EFI/Slackware/elilo.conf meaning any local changes eg resume=/dev/... are gone
Maybe a really quick idiots guide to EFI?
Do the recommended full install with UEFI (elilo), since that is the type of your machine, before you change anything. IE get it working first.
HTH
john
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
