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.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by sevendogsbsd
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.
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?
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by bassmadrigal
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?
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.
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.
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.
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
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!
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;
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
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!
Last edited by onebuck; 05-17-2020 at 11:53 AM.
Reason: typo
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.