LinuxQuestions.org - So you want to be a Slacker! What do I do next?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - So you want to be a Slacker! What do I do next? (https://www.linuxquestions.org/questions/slackware-14/so-you-want-to-be-a-slacker-what-do-i-do-next-644746/)

Quote:

Originally Posted by cwizardone (Post 6084667)

Even manually it is easy using AlienBob's step by step instructions.

Very true! Eric is great with his documentation.

Quote:

Originally Posted by sevendogsbsd (Post 6084677)

I think the thing I found daunting was the whole experience. I had a working system after a couple of evenings of work (not long overall) but then when I started to read about how to implement multilib and then wine and steam, I got discouraged. I wanted a bit of tweaking but not THAT much. I know you all say it's easy and I certainly have the skill, but for whatever reason I didn't want to tackle that much for my main machine. I am back on my true love (!) FreeBSD. I do have a second machine though, and am thinking about setting that up with Slackware so I can play with it and learn how to do these things at my leisure.

I really like the idea of Slackware and the fact it is a "rebel" if you will (no systemd, cult following, KISS principle). I am a rebel as well, both in my profession and my long time use and promotion of FOSS.

When I get a free weekend I am going to set up my spare machine with Slackware and work through these things slowly. I'll reach out if I have questions, thanks.

Just a minor correction, Slack is not a rebel, it was the other distros that rebelled and lost their Slack (others never had it to lose). Slack is holding the fort and maintaining the road since its inception.

This thread will be of interest when you decide to play with your other rig : https://www.linuxquestions.org/quest...on-4175637636/

By rebel what I meant was the rest of the horde ran off in a different direction and Slackware refused to follow. I do the same thing generally :)

pulseaudio
now in current playing with pam ..
next are systemd ..

be a rebel.

Quote:

Originally Posted by sevendogsbsd (Post 6084686)

By rebel what I meant was the rest of the horde ran off in a different direction and Slackware refused to follow. I do the same thing generally :)

Haha, using that definition, the Amish are rebels. All that technology... If the Amish are already rebels, what does that make people who were raised Amish and decided to embrace technology? :D

Quote:

Originally Posted by bassmadrigal (Post 6084707)

Haha, using that definition, the Amish are rebels. All that technology... If the Amish are already rebels, what does that make people who were raised Amish and decided to embrace technology? :D

Mennonite :hattip:

Maybe the last posts in this thread would better fit here or there?

Quote:

Originally Posted by sevendogsbsd (Post 6084677)

If you ain't Slackin' you ain't rebel enough ;)

Hi,

Very interesting ...

From ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt

Quote:

Wed Feb 12 21:51:35 UTC 2020
a/aaa_terminfo-6.2-x86_64-1.txz: Upgraded.
d/git-2.25.0-x86_64-2.txz: Rebuilt.
Fixed uncompressed Git.3pm man page. Thanks to Xsane.
d/gnucobol-2.2-x86_64-3.txz: Rebuilt.
Fixed uncompressed man pages. Thanks to Xsane.
l/libarchive-3.4.2-x86_64-1.txz: Upgraded.
This update includes security fixes in the RAR5 reader.
(* Security fix *)
l/ncurses-6.2-x86_64-1.txz: Upgraded.
l/sdl-1.2.15-x86_64-8.txz: Rebuilt.
Added SDL_sound-1.0.3.
n/ModemManager-1.12.6-x86_64-1.txz: Upgraded.
n/NetworkManager-1.22.6-x86_64-2.txz: Rebuilt.
Fixed hardlinked/uncompressed man pages. Thanks to Xsane.
n/dovecot-2.3.9.3-x86_64-1.txz: Upgraded.
testing/packages/PAM/dovecot-2.3.9.3-x86_64-1_pam.txz: Upgraded.
Fixed missing /etc/pam.d/dovecot.
+--------------------------+
Wed Feb 12 05:05:50 UTC 2020
Hey folks! PAM has finally landed in /testing. Some here wanted it to go
right into the main tree immediately, and in a more normal development cycle
I'd have been inclined to agree (it is -current, after all). But it's
probably better for it to appear in /testing first, to make sure we didn't
miss any bugs and also to serve as a warning shot that we'll be shaking up
the tree pretty good over the next few weeks. I'd like to see this merged
into the main tree in a day or two, so any testing is greatly appreciated.
Switching to the PAM packages (or reverting from them) is as easy as
installing all of them with upgradepkg --install-new, and if reverting then
remove the three leftover _pam packages. After reverting, a bit of residue
will remain in /etc/pam.d/ and /etc/security/ which can either be manually
deleted or simply ignored. While there are many more features available in
PAM compared with plain shadow, out of the box about the only noticable
change is the use of cracklib and libpwquality to check the quality of a
user-supplied password. Hopefully having PAM and krb5 will get us on track
to having proper Active Directory integration as well as using code paths
that are likely better audited these days. The attack surface *might* be
bigger, but it's also a lot better scrutinized.
Thanks to Robby Workman and Vincent Batts who did most of the initial heavy
lifting on the core PAM packages as a side project for many years. Thanks
also to Phantom X whose PAM related SlackBuilds were a valuable reference.
And thanks as well to ivandi - I learned a lot from the SlackMATE build
scripts and was even occasionally thankful for the amusing ways you would
kick my ass on LQ. ;-) You're more than welcome to let us know where we've
messed up this time.
The binutils and glibc packages in /testing were removed and are off the
table for now. I'm not seeing much upside to heading down that rabbit hole
at the moment. Next we need to be looking at Xfce 4.14 and Plasma 5.18 LTS
and some other things that have been held back since KDE4 couldn't use them.
Cheers! :-)
a/kernel-generic-5.4.19-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.19-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.19-x86_64-1.txz: Upgraded.
a/lvm2-2.03.08-x86_64-1.txz: Upgraded.
a/shadow-4.8.1-x86_64-2.txz: Rebuilt.
Automatically backup /etc/login.defs and install the new version if
incompatible PAM options are detected.
d/kernel-headers-5.4.19-x86-1.txz: Upgraded.
k/kernel-source-5.4.19-noarch-1.txz: Upgraded.
VALIDATE_FS_PARSER y -> n
xap/mozilla-thunderbird-68.5.0-x86_64-1.txz: Upgraded.
This release contains security fixes and improvements.
For more information, see:
https://www.mozilla.org/en-US/thunde.../releasenotes/
https://www.mozilla.org/en-US/securi...s/mfsa2020-07/
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6793
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6794
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6795
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6797
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6798
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6792
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2020-6800
(* Security fix *)
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
testing/packages/PAM/ConsoleKit2-1.2.1-x86_64-1_pam.txz: Added.
testing/packages/PAM/at-3.2.1-x86_64-1_pam.txz: Added.
testing/packages/PAM/cifs-utils-6.10-x86_64-2_pam.txz: Added.
testing/packages/PAM/cracklib-2.9.7-x86_64-1_pam.txz: Added.
testing/packages/PAM/cups-2.3.1-x86_64-1_pam.txz: Added.
testing/packages/PAM/cyrus-sasl-2.1.27-x86_64-2_pam.txz: Added.
testing/packages/PAM/dovecot-2.3.9.2-x86_64-1_pam.txz: Added.
testing/packages/PAM/gnome-keyring-3.34.0-x86_64-1_pam.txz: Added.
testing/packages/PAM/hplip-3.19.12-x86_64-2_pam.txz: Added.
testing/packages/PAM/kde-workspace-4.11.22-x86_64-6_pam.txz: Added.
testing/packages/PAM/libcap-2.31-x86_64-1_pam.txz: Added.
testing/packages/PAM/libcgroup-0.41-x86_64-5_pam.txz: Added.
testing/packages/PAM/libpwquality-1.4.2-x86_64-1_pam.txz: Added.
testing/packages/PAM/mariadb-10.4.12-x86_64-1_pam.txz: Added.
testing/packages/PAM/netatalk-3.1.12-x86_64-2_pam.txz: Added.
testing/packages/PAM/netkit-rsh-0.17-x86_64-2_pam.txz: Added.
testing/packages/PAM/openssh-8.1p1-x86_64-1_pam.txz: Added.
testing/packages/PAM/openvpn-2.4.8-x86_64-1_pam.txz: Added.
testing/packages/PAM/pam-1.3.1-x86_64-1_pam.txz: Added.
testing/packages/PAM/polkit-0.116-x86_64-1_pam.txz: Added.
testing/packages/PAM/popa3d-1.0.3-x86_64-3_pam.txz: Added.
testing/packages/PAM/ppp-2.4.7-x86_64-3_pam.txz: Added.
testing/packages/PAM/proftpd-1.3.6b-x86_64-1_pam.txz: Added.
testing/packages/PAM/samba-4.11.6-x86_64-1_pam.txz: Added.
testing/packages/PAM/screen-4.8.0-x86_64-1_pam.txz: Added.
testing/packages/PAM/shadow-4.8.1-x86_64-2_pam.txz: Added.
testing/packages/PAM/sudo-1.8.31-x86_64-1_pam.txz: Added.
testing/packages/PAM/system-config-printer-1.5.12-x86_64-2_pam.txz: Added.
testing/packages/PAM/util-linux-2.35.1-x86_64-1_pam.txz: Added.
testing/packages/PAM/vsftpd-3.0.3-x86_64-5_pam.txz: Added.
testing/packages/PAM/xdm-1.1.11-x86_64-9_pam.txz: Added.
testing/packages/PAM/xlockmore-5.62-x86_64-1_pam.txz: Added.
testing/packages/PAM/xscreensaver-5.43-x86_64-1_pam.txz: Added.
testing/packages/binutils-2.34-x86_64-1.txz: Removed.
testing/packages/glibc-2.31-x86_64-1.txz: Removed.
testing/packages/glibc-i18n-2.31-x86_64-1.txz: Removed.
testing/packages/glibc-profile-2.31-x86_64-1.txz: Removed.
testing/packages/glibc-solibs-2.31-x86_64-1.txz: Removed.
usb-and-pxe-installers/usbboot.img: Rebuilt.

Hope this helps.
Have fun & enjoy Slackware!
:hattip:

Security needs for your Slackware install

Hi,

I use Slackware64 but I also use other sources for information to aid me when working with my system(s).

You may find this to be helpful; 3 antimalware solutions for Linux systems

Quote:

If you still believe that Linux can't be infected by malware, think again and then install these three applications to detect and prevent problems.

Even if you use Tripwire, you should realize that malicious attackers can still plant bad software on your system without your knowledge. In this article, you'll learn how to install and run three different antimalware applications that can help you keep your system free of malicious irritants that make users call you at the least convenient times: chkrootkit, rkhunter, and ClamAV.

Hope this helps.
Have fun & enjoy Slackware!
:hattip:

EDIT: BTW, you can get the tool kits from SBO;
https://slackbuilds.org/repository/1...earch=rkhunter
https://slackbuilds.org/repository/1...em/chkrootkit/
https://slackbuilds.org/repository/14.2/system/clamav/

EDIT2: From Slackware Doc Project;
howtos:security:basic_security

Hi,

I normally use Mozilla Firefox ruario's re-package script to get the new Firefox update when available. I had some issue when using the script today after getting updates available notice.

I looked through the script and realized I could just get the new file via about Firefox and use the updates available to download link or use from https://www.mozilla.org/en-US/firefo...paign=whatsnew Moved the downloaded bz2 file to my local firefox archive. Then launch the 'lastest firefox' with filename for the new firefox-76.0.1.tar.bz2; Note that you must have the latest-firefox script and downloaded file in the same directory or use absolute paths

Code:

/arc3/firefox# ./latest-firefox firefox-76.0.1.tar.bz2

Worked like champ! Upgraded the new Firefox Slackware64 package. Launched with new issues. I restarted with

Code:

about:profiles

in a new tab then choosing my old profile by setting it as default then launch in new browser. I then logged out of my desktop and restarted because no linked pages would launch via Thunderbird or anywhere else.

After a new desktop I launched

Code:

about:profiles

and removed the new created new profile from the upgradepkg operation thus leaving my original profile as wanted.

I still need to find out the issue with launching the latest-firefox script. But I do know a work around exists when I have issues.
Hope this helps.
Have fun & enjoy Slackware!
:hattip:

Slackware64 Live

Hi,

I have a large TODO list and some things are at the bottom that need attention. I want to utilize the new slackware-live/ editions. So I setup my archive to use;

Code:

rsync -avzhP rsync://slackware.uk/people/alien-slacklive/latest/slackware64-live-current.iso ./

I got all the newer ISO from both http://slackware.uk/people/alien-slacklive/latest/ & http://bear.alienbase.nl/mirrors/slackware-live/latest/ to compare download speeds. Very satisfied with both! Sure, you can use wget but realize that rsync will;

Quote:

man rsync

rsync - a fast, versatile, remote (and local) file-copying tool

SYNOPSIS
Local: rsync [OPTION...] SRC... [DEST]

Access via remote shell:
Pull: rsync [OPTION...] [USER@]HOST:SRC... [DEST]
Push: rsync [OPTION...] SRC... [USER@]HOST:DEST

Access via rsync daemon:
Pull: rsync [OPTION...] [USER@]HOST::SRC... [DEST]
rsync [OPTION...] rsync://[USER@]HOST[:PORT]/SRC... [DEST]
Push: rsync [OPTION...] SRC... [USER@]HOST::DEST
rsync [OPTION...] SRC... rsync://[USER@]HOST[:PORT]/DEST

Usages with just one SRC arg and no DEST arg will list the source files instead of copying.

DESCRIPTION
Rsync is a fast and extraordinarily versatile file copying tool. It can copy locally, to/from another host over any remote shell, or
to/from a remote rsync daemon. It offers a large number of options that control every aspect of its behavior and permit very flexible
specification of the set of files to be copied. It is famous for its delta-transfer algorithm, which reduces the amount of data sent
over the network by sending only the differences between the source files and the existing files in the destination. Rsync is widely
used for backups and mirroring and as an improved copy command for everyday use.

Rsync finds files that need to be transferred using a "quick check" algorithm (by default) that looks for files that have changed in size
or in last-modified time. Any changes in the other preserved attributes (as requested by options) are made on the destination file
directly when the quick check indicates that the file's data does not need to be updated.

I have found 'rsync' to be a reliable method when syncing. Each to his/her own! Look at; rsync or docs rsync

For wget look at basic network utilities or Look at

Quote:

man wget

Wget - The non-interactive network downloader.

SYNOPSIS
wget [option]... [URL]...

DESCRIPTION
GNU Wget is a free utility for non-interactive download of files from the Web. It supports HTTP, HTTPS, and FTP protocols, as well as
retrieval through HTTP proxies.

Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a
retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user's
presence, which can be a great hindrance when transferring a lot of data.

Wget can follow links in HTML, XHTML, and CSS pages, to create local versions of remote web sites, fully recreating the directory
structure of the original site. This is sometimes referred to as "recursive downloading." While doing that, Wget respects the Robot
Exclusion Standard (/robots.txt). Wget can be instructed to convert the links in downloaded files to point at the local files, for
offline viewing.

Wget has been designed for robustness over slow or unstable network connections; if a download fails due to a network problem, it will keep retrying until the whole file has been retrieved. If the server supports regetting, it will instruct the server to continue the
download from where it left off.

Hope this helps!
Have fun & enjoy Slackware64 Live!
:hattip:

New slackware users will find helpful information at Slackware Doc Project

Hi,

Slackware Doc Project contains helpful information for new & old Slackware users;

Quote:

Welcome to the Slackware Documentation Project

We aim to become your primary source for Slackware Linux documentation on the web.
Getting Started with Slackware

Slackware installation: a guide through the whole process of installing and configuring Slackware Linux; written for new and experienced users alike.

Configure your new Slackware System; how to proceed after the installation has completed.

Getting Involved: describes various ways Slackers (both new and experienced users) can contribute to the Slackware community.

Slackware Live Edition: if you want to try a Live Edition of Slackware before committing it to your hard drive.

Links and pointers: other sites on the web offering Slackware related information.

You can find other useful links in my signature that will help you with Slackware.
Have fun & enjoy Slackware.
Hope this helps.
:hattip:

Thank you, onebuck! The Slackware Documentation Project does indeed have quite a bit of useful information for new and experienced Slackware users. It could have much more. If any of you feel that you can contribute tips, tricks, methods, procedures, etc. that you yourselves utilize in everyday use of your Slackware, please don't hesitate to contribute. There are also articles on the site that assist you in utilizing the wiki properly and efficiently when writing and publishing your helpful information.

Thanks to all!

And a quick shout out to Eric Hameleers (AlienBob) and Nicolas Kovacs (kikinovac) for their initialization and continuing support on the Slackware Documentation Project. This was their baby! :)

Also, a brief note/request regarding staff members of this project:

Many of you (editors) have become inactive at the project, myself included to some extent. Real Life® occasionally infringes on our participation online. If you are reading this and are still interested in remaining editors of the project, please reply here and reaffirm your support. Thank you.

On a completely unrelated note: after a bit of thought, I am going to build a "hack from Slack" VM because Kali Linux is a giant PITA. I only need cli tools (niko, nmap, curl, metasploit, sqlmap) so those are all either in 14.2 or on slackbuilds. My goal is to have a stable platform that is on an isolated (host only) network that I don't have to muck with constantly. Should do the trick! Since a VM, 14.2 should be fine and I won't need anything from -current.

@vtel57 should you wish to "re-activate" but not sure where to start editing or make clarification on errors i know exist, may i mentioned this contribution :

https://docs.slackware.com/howtos:mi...f_a_slackbuild

The idea is that its complementary "attempt" of an explanation of what goes on in a SlackBuild mainly aimed at less tech/able people (like myself) to complement a real life slackbuild that can be downloaded:

https://slackbuilds.org/repository/1...rch=latex2html

Its slightly out of date since i updated the SlackBuild taking into account new source release

Hi @captain_sensible!

Are you the original contributor of that How-To on the docs.slackware.com site?

Hi @vtel57 thanks for reply. Eric set me straight at the beginning rather embarrassingly with English (i'm English he's not ) and syntax. Apart from that i'm the only contributor.

I did it after reading through template for slackbuild, trying to understand it and applying it to do a SlackBuild for Latex2html which i submitted.

it should really not be a "how to " since now you don't really write a SlackBuild anymore just adapt a SlackBuild template. Thus it was meant to be an explanation to go with the SlackBuild you can find on slackbuilds.Also that its meant for people like myself.

As you can see from my rating I don't have much ability but when I was trying to get my latex2html accepted I couldn't find an up todate explanation and i noted in the docs.slackware.com the line

"Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets." which i interpreted as, it doesn't matter if your not that able or clever your welcome and can still contribute.

There is a section which I tried to interpret but am probably wrong, which means there may be erroneous material. I did put a shout out to editors last line of

https://docs.slackware.com/talk:slackdocs:news discussion tab

Quote:

Originally Posted by captain_sensible (Post 6135969)

it should really not be a "how to " since now you don't really write a SlackBuild anymore just adapt a SlackBuild template. Thus it was meant to be an explanation to go with the SlackBuild you can find on slackbuilds.Also that its meant for people like myself.

That was a good write up. Enjoyed reading it.

I am one of those who does write my own scripts. Of course I started out using the SlackBuild scripts and SBo scripts before I branched out to do my own. I wanted some extras that SBo scripts don't and can't provide, plus my build environment is also different that SBo's.

Quote:

Originally Posted by captain_sensible (Post 6135969)

"Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets." which i interpreted as, it doesn't matter if your not that able or clever your welcome and can still contribute.

There is a section which I tried to interpret but am probably wrong, which means there may be erroneous material. I did put a shout out to editors last line of

https://docs.slackware.com/talk:slackdocs:news discussion tab

In the beginning, we had quite a few active editors to screen submissions. Nowadays, though, it's pretty much Eric H. and myself... and I've been somewhat remiss about keeping an eye on things there.

As Chris says above, I read your article and thought it to be quite well done. A long time in the past, I attempted a few SlackBuilds "from scratch", but I found that most SlackBuilds I needed on my system were already in existence, so I didn't bother anymore. For this reason, I cannot second guess your thesis on its technical merits. E. Hameleers or R. Workman or others are going to be MUCH more qualified to check on it for you. I'm good at grammar/spelling/punctuation. ;) If there is erroneous information in the article, it's going to require a smarter person than I to detect and edit it.

On a submission-driven wiki like docs.slackware.com, there's always going to be some information submitted that's not necessarily accurate. It happens. Editors are supposed to catch it and correct it.

Anyway, all's well for the moment.

Have a great weekend! #Stay_Healthy!

the erroneous material is i think my explanation :

If i understand the above block of code correctly its using the “find” on the basis of permissions and following symbolic links using the “-L flag”. If i understand this correctly its basically setting directories to 755 in order to enable a “cd” into them and files so that root can read write. If this is true I might have expected

-type d -exec chmod 775 {}

For directories and

-type f -exec chmod 644 {}
on the actual block :

Code:

find -L . \

 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \

  -o -perm 511 \) -exec chmod 755 {} \; -o \

 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \

  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

Is there a way to get notified of new submissions to SlackDocs? I like reading contributions to it, but there aren't enough for me to add the site to my daily sites to check, because after so long without updates, I'll forget to keep going there.

I'll have to read through the SlackBuild article once I get some time.

> Is there a way to get notified of new submissions to SlackDocs?

I seem to remember as an Admin at docs.slackwere.com that I used to get email notifications of changes to the wiki. I do NOT get them as a regular Editor, though.

Eric H. (AlienBob) will have to answer this one, bassmadrigal. Sorry. I have insufficient data and/or memory. ;)

Quote:

Originally Posted by bassmadrigal (Post 6136191)

Is there a way to get notified of new submissions to SlackDocs?

There's a RSS feed but it's not limited to new submissions.

Ah, yes! Thanks. I had completely forgotten about the RSS. Unfortunately, even that would require regular monitoring by those interested in the new submissions. I haven't loaded up my RSS feeds in months. :(

Quote:

Originally Posted by gegechris99 (Post 6136382)

There's a RSS feed but it's not limited to new submissions.

Thanks. Maybe I'll have to get akregator up and running again. I used to use that, but it crashed at some point and lost me all my feeds and I was too lazy to set it back up.

Slackware UK mirror and hosting service help needed

Hi,

I am posting the quote here to hopefully help;
EDIT: From https://www.linuxquestions.org/quest...uk-4175670721/

Quote:

Originally Posted by tadgy (Post 6097014)

Hi,
As some of you may know, I am the founder, maintainer and systems administrator for the Slackware UK mirror and hosting service specifically targeted at the Slackware Linux community.

I am making this post to request your support for the service via the Slackware UK Patreon page.

The service has been running for over 10 years now - I started out small, with a PC under a desk and a 2Mbits/sec SDSL connection. From simply offering a mirror of Slackware Linux, the service has grown
and grown into what it is today - dedicated servers with Gigabit connectivity for all things Slackware!

I would like to think Slackware UK has grown to be one of the largest repositories of Slackware related projects and files on the internet - in fact, I cannot think of anywhere else that provides access to so many resources in one location.

Slackware UK isn't just about mirroring software that you can find elsewhere on the internet - I offer free full file hosting to Slackware related projects, distributions and package maintainers. There are several projects which use Slackware UK as their primary hosting solution; including SlackwareARM, Absolute Linux, Freeslack, Slint, Cinnamon SlackBuild (CSB) and MATE SlackBuild (MSB), to name but a few. I also offer a mirror of the entire Slackware Linux trees and other projects such as Zenwalk, and packages provided by alienBOB (Eric Hameleers) and rworkman (Robby Workman). I also maintain an in-house (with thanks to alienBOB) cumulative archive of all packages distributed since the very first release of Slackware64.

So, why am I asking for Patrons? Simply to cover some of the costs and expenses for running the service. I am not looking to profiteer on the back of Slackware Linux or Patrick's work - in fact, I encourage you to visit Pat's Patreon page and sign up to become one of his patrons also. I only ask that, if you regularly use Slackware UK or one of the projects that I host, you would kindly consider becoming a patron of the service, if you have the means.

Any donations are gratefully received and every little helps. If you wish to donate as a one off or an amount which is not available on Patreon, please see the Slackware UK website for PayPal links.

Thank you for reading :)

Hopefully you can help.
Have fun & enjoy Slackware!
:hattip:

AlienBob's recent email

Hi,

Eric is still working hard on liveslak;

Quote:

Portion of subscribed email from AlienBob;

The liveslak project received some interesting new features.
Most importantly, the hard disk installer of the Slackware Live Edition - called "setup2hd" - was expanded. In the past, it used to allow only the installation of the Live OS to your hard drive. But I received requests to also make it possible for setup2hd to install regular Slackware like the official installer does. It sounded like a good idea, and starting with liveslak release 1.3.7 the "setup2hd" program will let you choose from more package SOURCES than just the Live OS. In addition to the Live OS, you can now choose to install regular Slackware from a NFS, HTTP, FTP or Samba server. In other words, Slackware's network install feature was added.
Why is this different from the setup program on the official Slackware ISO? Well, the most obvious improvement is that you are working in a graphical desktop environment (the Live OS). You can run the setup2hd hard disk installation in an X terminal while you keep doing other stuff like reading online materials or watching a video to pass the time. Moreover, you can install stable Slackware 14.2 from the Live OS. That means MMC and NVMe drives are supported during installation (which is something the official Slackware 14.2 installer does not provide for).
And to top it off, I am now also adding "setup2hd" to the small XFCE ISOs. Word of caution: the XFCE ISOs do not contain a "huge" kernel which means if you want to install the stripped-down XFCE OS to your hard drive, you will have to do a manual "chroot" after installation completes and before you reboot, to edit /etc/lilo.conf and add a section for the "generic" kernel. and then run the "lilo" command to make it stick. Hopefully the "liloconfig" command will learn how to do that for you, sometime soon. You can always perform a Slackware network installation from the XFCE Live OS of course! The second new feature is the ability of liveslak to configure a custom background image for Plasma5-based Live OS. The custom image is used when generating the Live ISO, as the background for the SDDM login greeter, your desktop wallpaper, and for the lock-screen backdrop.
What I still want to achieve is adding similar functionality to the XFCE and Gnome based Live variants. The snag is that the configuration needs to be scriptable, i.e. when the "live" user logs in everything must already be in place and pre-configured. For Plasma5 that was not trivial to work out, and I have zero Gnome and XFCE scripted desktop configuration knowledge. Suggestions and code snippets are welcome.

If you wish to get updated by AlienBob's blog or what he is currently working on then sign up at https://alien.slackbook.org/blog/

Hope this helps.
Have fun & enjoy Slackware!
:hattip:

Plasma in /testing

Hi,

WOW!

From ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt

Code:

Wed Nov  4 02:31:05 UTC 2020 [2903]: Getting ChangeLog.txt...

0a1,424

> Tue Nov  3 22:32:22 UTC 2020

> Welcome to vtown, volkerdi's friendly takeover of alienBOB's ktown Plasma 5

> packages! Enormous thanks are due to alienBOB for maintaining and leading

> testing of Plasma 5 on the side, even as I wore out his patience (and likely

> others as well). But now this has made it into /testing and it won't be all

> that long before it'll hit the main tree, so test it out and let me know if

> anything broke. Several packages have been given back their upstream names

> since there's no real reason to do otherwise unless we were going to support

> installing KDE4 at the same time, and we aren't. Qt4 won't even be sticking

> around, but probably slackbuilds.org will take it up. I dropped kaudiocreator

> (won't build), ktuberling and klettres (rather bloated for the probably limited

> appeal), user-manager (seems to have been dropped by upstream), kdelibs (KDE4

> library, not going to support that), kwebkitpart, and kpat (not adding three

> new dependences only used for a solitaire game). In addition, it's probable

> that digikam and its dependencies will be dropped. It's a great program, but

> in my opinion it's just a little too big (especially the source) to ship by

> default. To install the vtown packages, first you'll want to remove any KDE4

> packages (the KDE and KDEI series in the main tree), any previous ktown packages

> from alienBOB, and then install all of the packages in vtown/deps and vtown/kde

> using upgradepkg --install-new. The previous advice on ConsoleKit2 was to remove

> it since we've switched to elogind, but if you've got the latest rc.M it

> shouldn't matter since ConsoleKit2 will not be started if elogind is installed.

> Speaking of elogind, you'll probably notice that once elogind is installed X

> or Wayland sessions will launch in the current console rather than on console 7.

> Regarding the build numbers, the one before _vtown_ is the build number that

> will be used when the merge to the main tree happens, and the one after _vtown_

> is used in case any rebuilds need to happen while vtown is in /testing.  That's

> about it for the notes on this one. Thanks again to alienBOB, and to my friends

> in the US - don't forget to vote. :-)

Thanks PV & AlienBob!!
Have fun & enjoy Slackware!
:hattip:

Blessed be he did it!

They both did it! (PV and AlienBOB)

:hattip:

Hi,

Things are looking good!

Code:

Tue Jan 19 05:38:09 EST 2021 [2691]: Getting ChangeLog.txt...

0a1,39

> Mon Jan 18 13:50:16 UTC 2021

> Hey folks, a little status update here. First, huge thanks are due to

> nobodino for helping to shake out packages that weren't building from source.

> With all those fixes in place (plus a few more), we have tested and found that

> everything in the tree compiles cleanly against glibc-2.32. So, the plan is to

> have another mass rebuild soon against that. Although the ABI didn't

> technically change, I've heard that libpthread may not be 100% compatible in

> some corner cases, so we'll err on the side of caution. Hopefully we can get a

> little testing done on the recompiled system and then go through it all again

> at the beginning of next month when glibc-2.33 is released. Other than that,

> how's Mesa working these days? If there are still issues that are resolved by

> dropping back to the previous branch, let's try to figure those out. I'd rather

> not revert Mesa unless there's no other choice. I'm hoping that the (probably

> unrelated) issues with Intel video hardware will be helped by today's

> xorg-server patch that uses the modesetting driver with newer chipsets. Please

> report any improvement on the LQ thread.

> Beta approaches. :-)

> a/sysklogd-2.2.0-x86_64-1.txz:  Upgraded.

> d/distcc-3.3.5-x86_64-2.txz:  Rebuilt.

>  Properly install distccmon-gnome.desktop. Thanks to marco70.

> d/python-setuptools-51.3.3-x86_64-1.txz:  Upgraded.

> l/imagemagick-7.0.10_58-x86_64-1.txz:  Upgraded.

> l/libodfgen-0.1.8-x86_64-1.txz:  Upgraded.

> l/libsigsegv-2.13-x86_64-1.txz:  Upgraded.

> n/inetd-1.79s-x86_64-12.txz:  Rebuilt.

>  Rebuilt to link with libtirpc. Thanks to nobodino.

> n/nftables-0.9.8-x86_64-1.txz:  Upgraded.

> n/postfix-3.5.9-x86_64-1.txz:  Upgraded.

> n/tcp_wrappers-7.6-x86_64-4.txz:  Rebuilt.

>  Use strerror(), not sys_errlist(). Thanks to nobodino.

> x/xorg-server-1.20.10-x86_64-3.txz:  Rebuilt.

>  Only use the Intel DDX with pre-gen4 hardware. Newer hardware will use the

>  modesetting driver.

> x/xorg-server-xephyr-1.20.10-x86_64-3.txz:  Rebuilt.

> x/xorg-server-xnest-1.20.10-x86_64-3.txz:  Rebuilt.

> x/xorg-server-xvfb-1.20.10-x86_64-3.txz:  Rebuilt.

> x/xorg-server-xwayland-1.20.10-x86_64-3.txz:  Rebuilt.

> xfce/xfce4-appfinder-4.16.1-x86_64-1.txz:  Upgraded.

:hattip:

Windows 10??? Hang your head in shame!!! :)

Quote:

Originally Posted by brianL (Post 6209502)

Windows 10??? Hang your head in shame!!! :)

I mean, individually, each of those words in that sentence have some meaning on their own, it's just put next to each other that they don't make sense.
:D

Other than that - I's time for big hype and big time now, we're nearing beta! wooot!

Go Slackware, go!

Hi

From Changelog

Quote:

> +--------------------------+
> Tue Apr 6 19:54:52 UTC 2021
> Thanks to nobodino and ponce for help fixing a few sources that wouldn't
> build properly. Overnight I tested recompiling everything using gcc-10.3.0-RC
> and had no build failures, so we'll be taking gcc-10.3.0 once it (and new
> kernels) arrive probably sometime next week. And then I think we'll be calling
> this a beta. Cheers! :-)

:hattip:

Hi,

Quote:

> Mon Apr 12 20:07:12 UTC 2021
> I'm going to go ahead and call this a beta even though there's still no fix
> for the illegal instruction issue with 32-bit mariadb. But there should be
> soon (thanks ponce!) No build regressions noted with the official gcc-10.3
> release. Please report any new (or old) issues on the LQ Slackware forum.
> Enjoy! :-)

:hattip:

Hi,

Quote:

Originally Posted by brianL (Post 6209502)

Windows 10??? Hang your head in shame!!! :)

I know that I am late to respond, just reading your response but my main system is Slackware64 and Firefox with a user agent to switch between agents when posting. So no need to hang my head in shame.
:hattip:

Quote:

Originally Posted by onebuck (Post 3164548)

Hi,

Welcome to Slackware® and the Slackware® LQ Forum!

Edit2: 10-19-09 so READ on! My last edit to the original post was on 12-08-08 as I belief the continuity of the thread should be fluid without edits other than to correct major mistakes.

Slackware® 13 which supports x86_32 & x86_64 has been released. You can utilize a lot of the information contained within this sticky that relates to Slackware® in general and the releases for Slackware® 12, 12.1, 12.2, 13. The later posts do have information for Slackware® 13 x86_32 & x86_64. HTH! /edit2 end/

Slackware® 12.1 distribution is available at the Slackware® store. By purchasing the distribution through the store you will be supporting Slackware® directly therefore insuring the continuance of the best Linux distribution.

If You don't purchase Slackware® 12.1 at this time then you will first need to download the Slackware® 12.1 Distribution via a Slackware® 12.1 official mirror or 'Official List of Mirrors'. Be sure to get the '.md5' file(s) for your iso(s). For a M$ user you can use 'WGET for Windows (win32)' or bittorent;

Please note the cd contents above. You will need cd1,cd2 and cd3(KDE/KDEI) for a installation or download the dvd for everything with any form of download for a installation, either by ftp, bittorrent or other download means. You may need cd4 if you plan to use anything within /extra.

Note: I will be presenting a cd/dvd installation at this time. But note that you can do a network installation if so desired then look here or etherboot.

Once You get the iso downloaded then you should do a md5sum check on the downloaded iso(s) image(s). This can be done using a M$ Windows application such as 'md5sum.exe' to check the md5sum. Or for Linux from the cli you would do;

Code:

~#cd /downloadisolocation      #cdromiso.iso cdromiso.md5 



~#md5sum -c cdromiso.md5      #substitute the correct name to check

Once you are sure that everything is OK then you can burn the 'ISO IMAGE' to your selected media. Please note that some users must burn the iso image at a slower speed to insure a good burn. By slowing the burn speed you may insure that a good copy will be created if the image is indeed valid.

Once the image has been burned to the media then a 'CdromMd5sumsAfterBurning' check would be advised. Your burn application can fail so a check of the final media would prevent you from some possible headaches.

Patience!

Don't be in a rush to boot the Slackware® install cd/dvd. I would suggest that you first read the documentation that PV has provided; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT. Plus the other text files relevant to your needs. All the text files are available on your install cd/dvd.

The above text files have valuable information for you that will aid in the Slackware® installation. You will be presented with information that may prevent you from falling into some pit falls that a lot of new users have fell into. If they had just read the text information file(s) before the install then no ones time would have been wasted.

I have read more than enough threads where a user failed to read the referenced text files because of the M$ mindset that the 'README' type files don't contain pertinent information. Slackware® Linux does require one to be able to READ and investigate in order to complete tasks on or within the system.

Now that the text rant is out of the way then let us get that new Slackware® install going. You should have your BIOS boot order setup so as the 'CD/DVD' is the first order of the BOOT sequence. Place the Slackware® 12.1 install cd1/DVD in your drive. Reboot the machine. You should get the Slackware® boot screen.

Reference: the Slackware 12.1 Howto 3.2 Booting the Slackware CD-ROM;

At this boot screen you will see the 'boot:' line. You will also get booting information along with some prompt information. It is here that you will input a different kernel if you need one along with kernel parameters. The desired information for 'YOUR' install will depend on the hardware that you are installing too. The before mentioned text files will dictate to you as to what should be passed to the install kernels. If you want to use the default kernel and not pass any parameters then just press return at the boot prompt.

Note: Remember that the Slackware® 12.1 install cd1/dvd are bootable and can be used to recover from errors with your install/filesystem errors.

If you anticipate 'acpi' with your equipment then pass the parameter 'apci=off'. If 'apic' then pass 'noapic' to the kernel.

If you have or expect a hdd/sata device probe problem then pass the 'hdn=noprobe' where n=a,b,c,d.

Other possible parameters are nolapic noioapic, you can google or search LQ for any possible parameters that you may need for your specific equipment. Or you could look at 'Linux Kernel Parameters' for a good list of kernel parameters.

Example:

boot: hugesmp.s append = "acpi=off noapic hda=noprobe"<Enter/Return>

Please see 'CHANGES_AND_HINTS.TXT'

Why re-invent the wheel. Please read the files that PV and the Slackware® team have provided. If you read the Slackware® 12.1 Howto and follow the steps you should create a good Slackware® 12.1 installation.

Reference: the Slackware 12.1 Howto Along with the; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT.

The below reference is abbreviated and can be used as a simple guideline/flowchart to give you an example of a installation. That is why I suggest that you print the 'Slackware® 12.1 Howto'.

Code:

abbreviated so please see Slackware 12.1 Howto for complete information.



3.3  Using Linux fdisk to create Linux partitions



4.0  Installing the Slackware distribution using setup.



4.1 The ADDSWAP option:



4.2 The TARGET option:



4.3 The SOURCE option:



4.4 The SELECT option:



The SELECT option lets you select software to install.



4.5 The INSTALL option:



This option actually installs the selected packages to the hard drive.



4.6 The CONFIGURE option:



The setup's CONFIGURE option does the basic configuration your system needs, such as 

setting up your mouse, setting your timezone, and more.



4.7 LILO



LILO is the Linux Loader, a program that allows you to boot Linux (and other operating 

systems) directly from your hard drive.  If you installed the LILO package, you now have

an opportunity to set it up.



4.8 Networking



Another configuration menu allows you to configure your machine's networking setup.  First, 

enter a hostname for your machine. The default hostname after installation is "darkstar," 

but you can enter any name you like.  Next, you'll be asked to provide a domain name. If 

you're running a stand-alone machine (possibly using a dialup link to an Internet Service

Provider) then you can pick any name you like. The default domain name is

"example.net".  If you are going to add the machine to a local network, you'll need to use 

the same domain name as the rest of the machines on your network.  If you're not sure

what this is, contact your network administrator for help.  Once you've specified the 

hostname and domain name, you'll be asked which type of setup you would like: "static IP",

"DHCP", or "loopback".



5. Booting the installed Slackware system



If you've installed LILO, make sure you don't have a disk in your floppy drive -- when

your machine reboots it should start LILO. Otherwise, insert the bootdisk made for your

system during the configuration process and use it to boot.  Also, make sure to remove

the CD-ROM to avoid booting it, or disable your machine's

CD-ROM booting feature in the BIOS settings.



The kernel will go through the startup process, detecting your hardware, checking your

partitions and starting various processes. Eventually you'll be 

given a login prompt:



darkstar login:



Log into the new system as "root".



6. Post-installation configuration

Once the system is running, most of the work is complete. However, there are still a few

programs you'll need to configure. We'll cover the most important in this section.



6.1 /etc/rc.d/rc.modules



This file contains a list of Linux kernel modules.

A kernel module is like a device driver under DOS. You can think 

of the /etc/rc.d/rc.modules file as similar to DOS's CONFIG.SYS. 

The file specifies which modules the system needs to load to

support the machine's hardware.  After booting your machine, you

may find that some of your hardware isn't detected (usually an

Ethernet card). To provide the support, you'll need to load the

correct kernel module. Note that modern Linux kernels include a

feature that allows the kernel to load its own modules, called

udev. This will load many modules automatically without any need

to edit rc.modules, and when using udev it might be better to

tell it how to load the modules you want automatically rather

than loading them at boot time with rc.modules. This is an

advanced topic, and outside the scope of this document. If

you're interested in this, "man udev" is a good place to start

reading.



In any case, it's best to not edit rc.modules unless you find

that the modules you want to use are not being loaded

automatically by udev.  You can see a list of the modules that

were loaded with the "lsmod" command.  Likewise, in the majority

of cases "alsaconf" is not required to configure sound.



Rather, the "alsamixer" tool is used to unmute the Master and

PCM channels and turn up the volume, and the "alsactl store" is 

used to save the sound defaults.



6.2 Configuring the X Window System



Configuring X can be a complex task.



xorgsetup

---------



This is a simple menu driven frontend that's similar in feel to

the Slackware installer.



xorgconfig

----------



This is a text-based X configuration program that's designed for

the advanced system administrator.



xorgconfig



This will present a screen full of information about xorgconfig.

To continue, press enter.



6.3 Hardware acceleration with X



If you've used xorgsetup or xorgconfig to configure for your

card, and it's one that can take advantage of X's direct

rendering support, you'll certainly want to enable this.



6.4 User Accounts



You should make a user account for yourself.  Using "root" as

your everyday account is dangerous, and is considered bad form

(at the very least) since you can accidentally damage your

system if you mistype a command.  If you're logged in as a

normal user, the effects of bad commands will be much more

limited.  Normally you'll only log in as root to perform system

administration tasks, such as setting or changing the root

password, installing, configuring, or removing system software,

and creating or deleting user accounts.



To make an account for yourself, use the 'adduser' program.

To start it, type 'adduser' at a prompt and follow the

instructions.  Going with the default selections for user ID,

group ID, and shell should be just fine for most users.

You'll want to add your user to the cdrom, audio, video plugdev

(plugable devices like USB cameras and flash memory) and scanner

groups if you have a computer with multimedia peripherals and

want to be able to access these.  Add these group names, comma

separated, at the following prompt: cdrom, audio, video,

plugdev, lp



Note: plugdev, audio and lp are gotchas' for a lot of newbies. Make sure

to add your users to the right groups. You can use the up-arrow

to see the suggested groups.



7. For more information



For more information, visit our web site at http://www.slackware.com



To shop for fine Slackware products (and help keep the project funded), 

please visit http://store.slackware.com.  :-)



        Email: info@slackware.com          (Information or general inquiries)

        FTP:  ftp://ftp.slackware.com    (Updates)

        WWW:  http://www.slackware.com    (News)

        Security issues:  security@slackware.com

        General Hotline:  volkerdi@slackware.com



8. Trademarks



Slackware is a registered trademark of Slackware Linux, Inc.

Linux is a Registered Trademark of Linus Torvalds.

All trademarks are property of their respective owners.

Please read the files that PV and the Slackware® team have provided.

I would suggest that new users at least print out the Slackware 12.1 Howto.

If you are experiencing network headaches (wired or wireless) then I suggest that you look at Alien_Bob's 'Configuring your network in Slackware'. This should help you setup a network that is functional.

These links and others can be found at 'Slackware-Links' .
More than just Slackware® links!

Happy Slacking!

Neither this post nor I (Onebuck) officially represent Slackware® in any way.

Partition
Just like dos 5.0 need a swap partition.
format
install
This is the best distro ever Kiss

Hi,
I have noticed some posted issue(s) for getting Mozilla Firefox for Slackware.

A gentle reminder for Firefox users. I will download my updates from https://www.mozilla.org/en-US/firefox/new/ then use that Linux download from a local directory to use from a terminal as root; https://gist.github.com/ruario/9672798 script to create a Slackware64 package;

Code:

/arc3/firefox# mv /home/gws/Downloads/firefox-89.0.tar.bz2 ./



/arc3/firefox# ./latest-firefox firefox-89.0.tar.bz2



Slackware package "/tmp/mozilla-firefox-89.0-x86_64-1ro.tgz" created.

buckXPS:/arc3/firefox# mv /tmp/mozilla-firefox-89.0-x86_64-1ro.tgz ./



/arc3/firefox# upgradepkg mozilla-firefox-89.0-x86_64-1ro.tgz

Hope this helps.
Have fun & enjoy Firefox with Slackware64!
:hattip:

@onebuck...

Hey, my friend. Are there any dependencies needed to satisfy to run the newest FF on 14.2? I ask this because in the past I attempted to build a newer version of FF for Slackware and did not succeed because of the dependencies that were not in place. I started to hunt them down, but swirled into Dependency Heck and gave the project up at that point.

I'd love to run FF 89.x on my 14.2 instead of this old 68.x ESR that I'm currently running.

Just curious about this. I'll check in later and see what you have to say.

Regards,

~Eric

Quote:

Originally Posted by onebuck (Post 6255942)

Code:

/arc3/firefox# mv /home/gws/Downloads/firefox-89.0.tar.bz2 ./



/arc3/firefox# ./latest-firefox firefox-89.0.tar.bz2



Slackware package "/tmp/mozilla-firefox-89.0-x86_64-1ro.tgz" created.

buckXPS:/arc3/firefox# mv /tmp/mozilla-firefox-89.0-x86_64-1ro.tgz ./



/arc3/firefox# upgradepkg mozilla-firefox-89.0-x86_64-1ro.tgz

Hope this helps.
Have fun & enjoy Firefox with Slackware64!
:hattip:

In case you didn't know, you don't need to download the update. The latest-firefox.sh script will do it for you. You can even specify the Firefox channel you want to follow (beta or ESR), but it defaults to "latest".

It will even install the package if you pass -i to the latest-firefox.sh script.

Quote:

Originally Posted by vtel57 (Post 6255954)

I haven't checked with the latest version, but as of Firefox v84, it worked fine on 14.2 (Firefox is not my primary browser). I think all new dependencies are strictly for compiling. The only thing you won't get with the binary from Mozilla (which is what the ruario's latest-firefox.sh script downloads) is it was not compiled with --enable-alsa, so for those running pure alsa setups, you may not have any audio support.

@bassmadrigal... thanks for the info. I may attempt the upgrade of FF. The note about ALSA is also helpful. However, I was too lazy to revert back to pure ALSA on my system... although, I'm considering that, too, because I just prefer ALSA.

Well, this'll keep me busy for a while. :)

Quote:

Originally Posted by vtel57 (Post 6255985)

Ruario's script does make it easy. You can run it with the -i, let it do its thing, and the check and see if it runs. If it doesn't, just revert back to the official package (or your previous one if you were using something other than the official).

COOL! The older I get, the more I like "easy". ;)

DAYUM! That was easier than falling off my chair after three bourbons on the rocks. OUTSTANDING! :)

Now running FF 89.0 fully sync'd and customized. It's noticeably faster -- and I MEAN noticeably -- than ol' v68.x ESR, for sure. Also, it seems to be much less of a CPU cycle hog. About 450M RAM with 11 tabs open and one of them playing music on YouTube. CPU sitting at 1.2%. Can't complain about that.

Thank you Ruari Oedegaard and drgibbon (credit for a fix)!

And thank you, onebuck and bassmadrigal for your assistance!

I'm a HAPPY Firefox user! Been pretty loyal to Mozilla since waaaay back on Mozilla Browser in Win 98. ;)

By the way, upgrading FF using Ruario's script needs to have its own thread here in the Slackware forums,if it doesn't already. Mod split this one off, maybe?

Hi,

Quote:

Originally Posted by vtel57 (Post 6256023)

I too feel that FF 89 has crisp response and works better. I like the new theme choices available, especially 'light'. I am also glad to see other members contribute their use of Ruari's script. I have my habits and usually do things my own way (reason for using Slackware for the past 3 decades). I like to see things being performed manually. Just habits from pre-GUI days. I like things out in the open and performed in a manner acceptable to me.

EDIT: You might find this link interesting; https://www.tweaksforgeeks.com/firef...rface-changes/

Have fun & enjoy FF 89 on Slackware64!
:hattip:

At first, I didn't like the simplified interface. The toolbar icons are plain and simple like in Chromium. However, Ive quickly got used to it. It actually looks just like my Thunderbird. Took me a bit to appreciate the "floating" tabs, but I kinda' like it now. :)

Screenshot:

Very interesting!!

Hi,

Food for thought;

Quote:

./mirror-slackware-current.sh
#
# Mirroring slackware64-current from rsync://slackware.mirrors.tds.net/slackware/slackware64-current ...
#
Changing to /mnt/sdc2/slackware//slackware64-current ...
Mon Jun 7 21:52:44 CDT 2021 [1452]: Getting ChangeLog.txt...
0a1,131
> Mon Jun 7 18:53:49 UTC 2021
> Hey folks! Sorry about the delay in getting this batch out but I had other
> distractions going on here last week that prevented getting this one wrapped
> up. Anyway, probably the highlight of this update set is that we've decided
> to abandon the 5.10 LTS kernel in favor of following the latest one. We've
> never really had a policy that required LTS in a stable release although that
> is how it has been done for years, but based on comments from the Slackware
> community it seems like 5.10 LTS isn't getting a lot of love and lacks
> hardware support that people need now. Conversely, the reports on 5.12 have
> been almost entirely positive, so we're going to provide what we think is the
> best available kernel. It's unlikely that we'll see another LTS prior to
> release, so the plan for maintenance is to keep following the latest kernels
> as needed for security purposes. If that means we have to jump to a new branch
> while supporting the stable release, we'll start the kernel out in testing
> first until we've had some feedback that it's safe to move it to the patches
> directory. Sooner or later we will end up on an LTS kernel again, and at that
> point we'll just roll with that one. Feel free to comment (or complain) about
> this plan on LQ... I'll be curious to see what people think. Anyway, enjoy!

Have fun & enjoy Slackware!
:hattip:

Quote:

Originally Posted by vtel57 (Post 6256863)

Took me a bit to appreciate the "floating" tabs, but I kinda' like it now. :)

One thing I didn't care for was the fatness (too tall) of the tabs in the new Proton interface.

I've fixed that today, though...

To make tabs thinner:

- About:config -> browser.compact.mode.show -> make True
- R-click toolbar -> Density Setting -> Compact mode (not supported)

---

This thins the tabs down about 25%... just the right size for me now. :)

Hi,

PV has made the kernel move to /testing;

Quote:

# ./mirror-slackware-current.sh
#
# Mirroring slackware64-current from rsync://slackware.mirrors.tds.net/slackware/slackware64-current ...
#
Changing to /mnt/sdc2/slackware//slackware64-current ...
Wed Jul 7 21:33:40 CDT 2021 [20294]: Getting ChangeLog.txt...
0a1,26
> Wed Jul 7 20:50:57 UTC 2021
> a/kernel-generic-5.12.15-x86_64-1.txz: Upgraded.
> a/kernel-huge-5.12.15-x86_64-1.txz: Upgraded.
> a/kernel-modules-5.12.15-x86_64-1.txz: Upgraded.
> a/libbytesize-2.6-x86_64-1.txz: Upgraded.
> a/mcelog-177-x86_64-1.txz: Upgraded.
> d/kernel-headers-5.12.15-x86-1.txz: Upgraded.
> d/ruby-3.0.2-x86_64-1.txz: Upgraded.
> This update fixes bugs and security issues:
> Trusting FTP PASV responses vulnerability in Net::FTP.
> StartTLS stripping vulnerability in Net::IMAP.
> For more information, see:
> https://cve.mitre.org/cgi-bin/cvenam...CVE-2021-31810
> https://cve.mitre.org/cgi-bin/cvenam...CVE-2021-32066
> (* Security fix *)
> k/kernel-source-5.12.15-noarch-1.txz: Upgraded.
> l/python-pillow-8.3.1-x86_64-1.txz: Upgraded.
> isolinux/initrd.img: Rebuilt.
> kernels/*: Upgraded.
> testing/packages/linux-5.13.x/kernel-generic-5.13.1-x86_64-1.txz: Upgraded.
> testing/packages/linux-5.13.x/kernel-headers-5.13.1-x86-1.txz: Upgraded.
> testing/packages/linux-5.13.x/kernel-huge-5.13.1-x86_64-1.txz: Upgraded.
> testing/packages/linux-5.13.x/kernel-modules-5.13.1-x86_64-1.txz: Upgraded.
> testing/packages/linux-5.13.x/kernel-source-5.13.1-noarch-1.txz: Upgraded.
> usb-and-pxe-installers/usbboot.img: Rebuilt.

Have fun & enjoy Slackware!
:hattip: