Slackware general thread

> 14.2 http://www.slackware.com/getslack/torrents.php >current https://slackware.nl/slackware/slackware64-current-iso/ >wiki https://docs.slackware.com/ >3rd party package managers https://sbopkg.org/downloads.php https://pink-mist.github.io/sbotools/downloads/ >beginners guide https://docs.slackware.com/slackware:beginners_guide >Change log (x86_64) http://www.slackware.com/changelog/current.php?cpu=x86_64 >slackbuilds (build system) faq https://slackbuilds.org/faq/ >slackbuild script writing tutorial https://slackwiki.com/Writing_A_SlackBuild_Script >Slackware Security Advisories http://www.slackware.com/security/list.php?l=slackware-security&y=2021 happy slacking

I used it for a while back when it was Slackware 14.1. It was pretty cool to learn on and get my bearings, but ultimately moved on to Fedora.

>>42840 bump. Slackware is based desu. Been using it for about a year now and it's been pretty comfy as my first linux distro.

Slackware saved my ass once. I software-flashed my own ROM of coreboot on a Thinkpad T60 and I think there was something wrong with graphics initialization because every single Linux distro I tried to boot either reported an error or made the screen all glitchy. Every single one except Slackware that is. I used it to restore the stock BIOS.

So what's the best way to install packages that require newer version of glibc? The glibc version in 14.2 is quite old now (5 years) and some of the software I want is asking for (often unnecessarily) newer versions. I've seen Guix recommended for this, any other suggestions? On a personal note, I've been running Slackware on an old netbook and it has been great. Basically using all suckless software (dwm, st, slstatus, dmenu) and thoroughly enjoying it. Extremely simple to setup and use, no need to learn some archaic config files or scripting language.

>Mon Feb 15 19:23:44 UTC 2021 >Here we go again... upgraded to glibc-2.33 and one last mass rebuild for >Slackware 15.0. The only packages upgraded in this batch are glibc and the >kernels - everything else is just a rebuild against the new glibc. Not >rebuilt in this batch: devs (best to just leave this alone), glibc-zoneinfo, >kernel-firmware, rust, linux-faqs, linux-howtos, aspell-en, mozilla-firefox, >mozilla-thunderbird, and seamonkey. There's a new Rust compiler but Firefox >and Thunderbird will need to be patched to use it, so we'll hold off on >those until they're ready for the new Rust either with patches or new >upstream releases. Until we have that and a few more scheduled upgrades I'm >not quite ready to call this beta yet, but you can call it 15.0-alpha1. :-) Haipu desu

15.0 when? Kernel version 5+ when? Please don’t tell me to use current; I need stability. Also, what are the odds that sbopkg becomes native in the Slackware iso? It’s unusable without the builds, and setting those up is inconvenient.

>>42893 >I need stability current is more stability than debian testing. Don't worry. I use this almost everyday and I have not experienced any mistakes. >sbopkg If there's a case for it then create a community tool or spin and see if it's popular. If it is then Pat might consider inclusion like they did for slackpkg. >>42844 I use arch btw.

Can you compile slackware and it's packages on another computer? I have a soykafty laptop from 8 years ago and don't want to wait 20 hrs for a web browser to compile

>>43005 Slackware isn't like Gentoo that makes you compile every package or anything. In fact Slackware barely has a package manager. If it's not in Slackware's p minimal repository then you'll need to download it from the package's own website. If they offer a binary then it should work fine, otherwise you'll have to compile it yourself. Any web browser should offer a Linux binary afaik. >Can you compile slackware and it's packages on another computer? Sure, gcc and most other compilers have options for cross-compilation, nothing new.

bumpe with 9 page Sed ut perspiciatis, unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt, explicabo. Nemo enim ipsam voluptatem, quia voluptas sit, aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos, qui ratione voluptatem sequi nesciunt, neque porro quisquam est, qui dolorem ipsum, quia dolor sit, amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt, ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit, qui in ea voluptate velit esse, quam nihil molestiae consequatur, vel illum, qui dolorem eum fugiat, quo voluptas nulla pariatur? [33] At vero eos et accusamus et iusto odio dignissimos ducimus, qui blanditiis praesentium voluptatum deleniti atque corrupti, quos dolores et quas molestias excepturi sint, obcaecati cupiditate non provident, similique sunt in culpa, qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio, cumque nihil impedit, quo minus id, quod maxime placeat, facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Temporibus autem quibusdam et aut officiis debitis aut rerum necessitatibus saepe eveniet, ut et voluptates repudiandae sint et molestiae non recusandae. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.

>>42870 This is honestly some of the most heartwarming news I've heard in a long time. I cut my teeth on Slackware 3.4 over two decades ago. I'm eager to return to my roots. I've been debating doing LFS again (I do it every couple of years to stay updated on what happens under-the-hood in Linux) and building my own Slackware-alike, since Slackware itself seemed on unofficial-hiatus. But now I may just wait for the official release. >>43026 >In fact Slackware barely has a package manager. To be fair, Slackware has a perfectly functional package manager. What it doesn't have is a dependency manager.

>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! :-) hype hype

Awesome. I've not tried slackware yet but its definitely on my todo list

I have been running Slackware64-current on my home server for a few years. I had a free weekend a few weeks ago and after -15alpha was released I finally got around to installing it on my MacBook Pro to use as my daily driver. It's great, it's easy as hell to use and even though it has its quirks it is such a fundamentally simple distribution that the mental map required to understand it is tiny. I especially like being able to write SlackBuild scripts like they're nothing. The only downside really is that it can be hard to find help sometimes, since the documentation is often outdated. But this is something where the community (including me) needs to step up and do the work ... once Slackware 15 comes out hopefully there will be some movement towards updating the SlackBook. For me, I can't figure out suspend-then-hibernate (and now hibernate doesn't work properly at all), and sometimes when resuming from suspend my WiFi driver soykafs the bed - but ultimately these are not issues with the distribution but with the software and my hardware. Keen as for Slackware 15.

>>42893 Unlikely I think, because unlike slackpkg which performs a unique function, sbopkg is one of a few different SlackBuild-based package managers, including slapt-get, slpkg, and sbotools. I don't think Pat would make an opinionated choice about adding a particular third-party package manager, especially since Slackware doesn't strictly support out-of-distribution packages. I could see slackpkg+ being included in extra/ though, since it extends already existing functionality in a unique way and performs a common function. But again, Slackware doesn't support packages outside the distribution, so he probably doesn't want to open the gates to bug reports about packages which aren't part of Slackware.

>>44932 >It's great, it's easy as hell to use and even though it has its quirks it is such a fundamentally simple distribution that the mental map required to understand it is tiny. I especially like being able to write SlackBuild scripts like they're nothing. install gentoo, configure slackware and therefore, IMO without ansible, slackware is pain in ass as a daily driver. On daily driver i use arch - admittedly don't like it, but it has AUR.

>>44935 Gentoo looks neato and I want to give it a shot one day. Ebuilds look very nice too. But my laptop is old and gets too hot easily, so I don't want to build everything, therefore Gentoo is not on the table for me right now. I don't know how Ansible would make Slackware any easier to use. Of course for production I wouldn't use it, I only use it on a home server and a laptop.

>>44938 ansible it's manager configuration, this is comparable to a looped bash to configure multiple computers from one place (no need any agent, just SSH) or solutions known from NixOS. >>44664 >To be fair, Slackware has a perfectly functional package manager. What it doesn't have is a dependency manager. i wonder, each distribution has its own package manager and if you miss something in the repository, you have to install from source. The problem with something like this is that it leaves the system in an inconsistent state. what you guys think, porting slackware package manager for this purpose sounds like a good idea?

>>44943 I don't think you could call what Slackware uses a package manager. It's more of a DIY distribution.

>>44945 plop linux it linux distro which actually doesn't have package manager slackware have package manager but without depency resolution. And it is the lack of this feature that I think would do the job perfectly in distributions where there is no application for your package manager and you need to install from source.

>>44945 pkgtools manages packages, you can install, remove, and upgrade packages in place and atomically. What else is a package manager? >>44943 I still don't see how ansible makes running Slackware as a daily driver any easier (or harder). You can use slackpkg to keep your system up to date.

>>44974 ansible isn't a package manager, it is a configuration management, If you use slackware, you probably know exactly how long it took for you to configure it. By default, after installation, you don't even have a user created, just root. Ansible makes declarative system configuration model known from NixOS but distribution-agnostic and reproducible to any number of computers.

>>44981 That does sound pretty cool ... but for a computer you throw in your backpack, which presumably you keep a backup of and don't need to reinstall or replace often (maybe once every couple of years), it sounds overkill. Certainly useful if you need to maintain a number of machines, or if you're constantly blowing through computers, but for a PC it's a bit much. That being said, how do you use ansible exactly? Do you have any pastebins or gists you can share? - I'm definitely curious.

>>44981 >>45006 At some point I would also just go with Nix or Guix too (though I found Guix to be quite difficult to wrap my head around when I needed to make non-standard changes to application config, I used it for a few months on an older laptop and never managed to figure this one out).

>>45007 What kind of changes? For some, you'd have to modify the build phases and apply patches.

>>45022 Just modifying a program’s configuration file in /etc (for instance, changing sshd_config to only allow keyed login). If I did a guix system reconfigure, it was gone - of course it was, because it is a functional, declarative OS, so in-place changes to program configuration will be gone unless you change your system declaration. I never managed to figure out how to get around this though - I suppose you have to specify the configuration text file you want to use instead of the default, or provide a diff patch?

>>45024 Yeah you'd either make that part of the files generated by the package which it'd symlink automatically in your profile, or you'd go full Guix way and create a service definition for it. Also the Guix thread seems to be gone? I couldn't find it earlier, I was going to suggest moving this conversation there...

>>45022 NixOS is only compatible with itself. Ansible works everywhere Rollbacks too. ZFS have snapshots, effect the same I just don't know an alternative to the application in different versions it is indeed a unique NixoOS option. In other systems, I see no other option than chrooting.

> unique NixoOS unique to NixOS and Guix System

>>45006 >That being said, how do you use ansible exactly? Do you have any pastebins or gists you can share? - I'm definitely curious. https://docs.slackware.com/howtos:slackware_admin:slackware_automation_using_ansible ansible only uses yaml, so just ignore perl files. I don't know why the author rewritten what he did in ansible files into perl. In general, with ansible you can do anything what you usually do with the command line (shell: command) but only thanks to the learning of the ansible way, you gain declarativeness. Unlike imperatively written programs, the programmer describes the conditions that must be met by the final solution (what we want to achieve), not a detailed sequence of steps leading to it (how to do it). Example: you use touch command but what if second machine there is no such program or someone forgot about the dependency - real life example, just look: https://unix.stackexchange.com/questions/577050/bash-fdisk-command-not-found and this issue still exists, fuarrrking dumbian. Thanks for the ansible, you just say tasks: - name: Create file with ansible module file: path: /tmp/new_file_ansible.txt state: touch Ansible have own touch and don't use command line touch. Therefore it will work regardless of what is missing from the system, are portable. the exact same method can be used if you have linux distributions with different package managers, and more.

>>45054 https://dev.to/jbkahn/ansible-or-how-i-learned-to-stop-wasting-time-setting-up-my-computer-and-script-it-24hk

>>45054 >>45271 Ansible doesn't provide the same guarantees as Guix/Nix, it has its place, but it's not a replacement or an equivalent. Tertiary concerns like the source and verification of code, replicable building, etc, are none of its concern. When your playbook consists mostly of shell snippets and checking return codes on scripts you wrote yourself, you notice Ansible's limitations quite sharply. In addition to this, adding new support for things to Ansible is a major hassle. It would make managing the configuration of an heterogeneous fleet of machines easier, but for example right now it supports neither Guix or Nix package managers, so you're back to using shell and command module hacks. If you have many such computers, you could make a template for the intended system configuration and have Guix/Nix apply it, while maintaining Ansible's idempotency ideals.

>>45276 I say the last time, ansible it's configuration management, not for packages, what were you expecting. Nix combined declarative config model, rollbacks and different version the same program. First two can solve for all distros by ansible + ZFS. Three i don't know, chrooting?

If you use Slackware it’s been scientifically proven that you have a larger than average penis

>>45276 >but for example right now it supports neither Guix or Nix package managers, so you're back to using shell and command module hacks https://github.com/ktosiek/ansible-nix

>>45440 Third-party non-mainlined support I would have to review the source for?

>>45409 >If you use Slackware it’s been scientifically proven that you have a larger than average penis Well yeah. But frankly I already knew that. I suffer from the opposite of big-truck syndrome. I have to drive a non-flashy little sedan as compensation for my colossal wang and heavy-hanging sack.

bump before dead A constant force, acting on a particle of mass m, will produce a constant acceleration a. Let us choose the x-axis to be in the common direction of F and a. What is the work done by this force on the particle in causing a displacement x? We have, for constant acceleration, the relations a = ( V - v ) / t and x = ½ ( V + v ) t. Here v is the particle's speed at t = 0 and V is its speed at time t. The the work done is W = F x = m a x = m ( ( V - v ) / t ) ( ½ ( V + v ) ) t = ½ m V² - ½ m v². We call one-half the product of the mass of a body and the square of its speed the kinetic energy of the body. If we represent kinetic energy by the symbol K, then K = ½ m v². We may then state the above equation in this way: The work done by the resultant force acting on a particle is equal to the change in the kinetic energy of the particle.

which packages do you guys use on the tagfile install?

>>47139 i check on arch and i tested which are really needed. In most cases, half of the required packages are unnecessary.

This thread has convinced me to check it out. I have used Debian netinst primarily for almost 7 years. Anything I shoud be aware of in particular? I like making my OS look like crunchbang.

>>47344 I'm afraid I don't know what crunchbang is, but the main thing to be aware of is that 14.2 is 5 years old now and not worth going all-in on. Unless you have some particular use-case which requires Linux 4.4 and glibc 2.23, you want Slackware64-current which will become Slackware64 15.0 eventually. When updating you will want to check the ChangeLog for any breaking changes, but at this stage in the development of the next release there are no major nasties expected. Slackware64-current is not a rolling release, it is a development branch, so it can break - but it is more stable than most rolling releases. Look into Alien Bob's Liveslak build, which you can find here https://download.liveslak.org/latest/ Look into slackware64-live-current.iso which gives you a full Slackware64 installation. Try installing it on a VM and seeing what the installation process is like. Good luck!

do slackware users still reference subgenius, or is that something that's fallen away? I was going to post "Bob" but I'm afraid the image would be deleted for too much resembling an anime girl.

>Mon Aug 16 05:28:16 UTC 2021 >Hey everyone, long time no see! No, I wasn't out fishing. Sadly, I haven't had >a fishing rod in my hand (or even a fishing license in my wallet) for this >entire season, but there may yet be a chance for that this year. Along with the >usual suspects, I've been trying to clear out the list of things that needed >to get done in order to reach the standard of excellence demanded from a >Slackware release, and I think we've gotten it pretty close. GCC was bumped to >version 11.2.0 (because we just can't send this out 2 versions behind), and >everything was verified to build properly or fixed up so that it did. I don't >see any benefit to another public mass rebuild, so we're not going to do one. >Anyway, without further ado, here is Slackware 15.0 release candidate one. >Consider most things frozen and the focus now to be any remaining blocker bugs. >We'll more than likely take that next Plasma bugfix release, but it's soon >time to get off this treadmill. Enjoy! :-) Nearly at 15.0, we even have 15.0 in the /etc/slackware-version file.

The story of Slackware is pretty darn interesting, when you start to dig a little deeper. Perhaps the most compelling element to the narrative is its longevity. Some twenty-five years after it was first released to the world, Slackware is indeed still going strong. It remains a preferred Linux distribution method by many. As of this writing, it is also still being updated at a decently steady pace. If you’re just starting to learn about Linux distribution options, you will hear about Slackware a lot. There are several reasons as to why that is the case. An Introduction To Slackware In order to better appreciate the longevity of Slackware, we have to cover two major subjects. First, let’s take a quick at the history of Slackware. That begins in 1993, although work began on it even earlier than that. With this foundation, we can then move on to the benefits of Slackware. These are benefits that have remained consistent through the decades. They can go a long way towards explaining the appeal of Slackware in 2019. As of this year, Slackware is the longest-standing Linux distribution choice that is still being updated. A Brief History Of Slackware Working from an even older Linux distribution known as Softlanding Linux, Patrick Volkerding created Slackware in 1993. It was released to the world at large in April of that year, and it has been well-regarded and updated ever since. One of the main purposes for the creation of Slackware in the first place was to establish the most Unix-like distribution option for Linux. Many believe they have succeeded in this regard time and time again. Both stability and simplicity in design have always been the goals of Slackware. According to Scott Chow of Theblogstarter.com, Slackware continues to aspire to make as few changes as humanly possible to software packages that come from the upstream. Furthermore, it also tries to avoid anticipating use cases, or precluding the decisions of the user. There is nothing in the way of a graphical procedure for installation. You also won’t find automatic dependency resolutions for any given software package. It utilizes plain text files, and utilizes a small set of shell scripts, when it comes to configuration and administration. Booting it will take you to an environment of what can be described as a common-line interface. Slackware has been updated a few times throughout the years. Volkerding continues to spearhead these updates, which is perhaps why Slackware has maintained such impressive consistency from 1993 to the present. The most recent update was released in June of 2016—just two years ago. As we get ready for a more detailed look at the benefits of Slackware, let’s take a quick look at some of the main Slackware features you can expect. Slackware Features One of the great things about Slackware is that it covers a lot of different needs right out of the gate. It is designed in such a way that you should be able to start working with it pretty quickly, and that would be regardless of your level of experience. We won’t cover every single Slackware feature here, but let’s unpack some of the top things to expect: • X-Window Systems • Developmental environments for both C and C++ • The ability to use Perl • Various utilities related to networking • A server for mail • A server for the web • A server for FTP-related needs • GNU Image Manipulation capabilities As you can see, Slackware brings a lot to the table from the beginning. That is certainly an impressive benefit unto itself, but there are so many other potential advantages of using Slackware to keep in mind. Slackware Benefits Explained Ultimately, it is obviously up to you to decide if Slackware is right for your needs. The great thing about Slackware is that you will know the answer to that almost immediately. Many find it to be a straightforward collection of features that they can engage immediately. Others see management and administration of Slackware as being riddled with tedious challenges and time-consuming requirements. For now, let’s explore some of the most commonly-cited benefits of using Slackware for Linux: • Stability: Even the people who find Slackware to be too challenging will tell you that it at least benefits from being enormously stable. Over the course of the past twenty-five years, Slackware has continued to function without a whole lot of problems. It has moved nicely with the times, but it really hasn’t changed all that much. Few things related to computers have such stability. • Security: Even for Linux distributions, there are traps and pitfalls that need to be constantly kept in mind. By and large, Slackware doesn’t have that problem. It probably helps that new versions of Slackware do not come out until everything is absolutely ready. • Neutral: Remember that Slackware isn’t dependent upon a package manager. This is largely due to the fact that the applications are installed through a source. Slackware is not affiliated with any company either. Distribution was community-driven in the early 90s, and Slackware remains committed to that a quarter of a century later. • Speediness: Another thing to keep in mind with Slackware is that it will only install what you absolutely want. Because of this, and keeping in mind the release policy we mentioned above, Slackware tends to run the fastest of the Linux distributions. • Clean configuration: One of the big knocks against Slackware is that it doesn’t have graphical config utilities. No matter what you want to do, you are going to need to use the command line. Some people find this frustrating, but others would argue that this gives you the cleanest possible config files to work with. • Want to understand Linux: There are other benefits to Slackware, but this one might just be our favorite. Even if you initially think Slackware has a higher learning curve than other distributions, there is a strong argument to be made that it will be worth the extra effort. Some don’t even experience this extra effort. However, if you do, think about Linux in broader terms. If you need to have a comprehensive understanding of Linux, you really can’t ask for a better teacher than Slackware. When you’ve mastered everything there is to know about Slackware, you will have pretty much mastered using Linux, as well. Conclusion Slackbuilds and strong IT cred are two more benefits that are worth taking to heart. At the end of the day, nothing in the world of Linux distributions can exist without a certain measure of controversy and disagreement. People also tend to be fiercely passionate and loyal about their favorite distribution. Nonetheless, Slackware has a staying power that would be absurd to ignore. It has worked for an incredibly long time, and it has done so in a field that has little time or patience for things that can’t be intensely/comprehensively useful. You could certainly make the argument that it has done more for bringing people to the world of Linux than just about anything else. Is Slackware right for you? At this point, you are in the best position possible to make that determination. As we mentioned before, Slackware is best experienced in a hands-on capacity. You can research the subject to death, and you still won’t really know for sure. The only thing we can promise you, as we mentioned before, is that you are going to be able to decide how you feel about Slackware pretty quickly. It could be one of the best decisions you have ever made, in terms of working with a distribution that helps you meet your goals.

>>49635 Very sweet, slackware was my first distro. I ditched it later but im gonna use it again somehow.

>>51234 that's a very good write up lain, do you have a blog? I would say slack is quite uniquely positioned, it sounds like there aren't any comparable distros, are there? Do you know other distros that tick similar boxes?

>>51234 Or you could just drop a link to the article https://www.slackware.org/

>Wed Nov 17 20:50:35 UTC 2021 >Clearly we're going to have to tread more carefully for things to settle down, so consider this RC2 and a much harder freeze

17 Jan 22 - pencil it in for release of Slackware 15.0 >>Quote: >>Originally Posted by Exaga >>Oh... a sweepstake! How quaint. >>I'll take January 17 2022. >This is an extremely good guess. I mean, I would have liked 2021-12-21 to prove the Mayans were pretty close, but the kernel patch to fix mem= still hasn't landed. But we have Plasma 5.23.5 coming on the 4th, new 21.12.1 applications on the 6th, and a new Frameworks 5.90 on the 8th. Give an additional week to find and fix any regressions. But that's a Saturday, and Eugenia from OSNews always used to ridicule me for releasing on a Friday or Saturday saying the media would ignore it. The following Monday is the 17th. https://www.linuxquestions.org/questions/slackware-14/mr-volkerding-please-release-15-0-as-soon-as-possible-even-sooner-4175703386/page24.html#post6310775

>>55020 Great to hear, i hope we get to see a new stable version in 2022.

>>55024 That’s Patrick’s comment so I think it’s a pretty sure thing :-)

Hello slackers and hackers, this'll be the slackware thread, the People's Distro headed by Head Codecel Patrick Volkerding. For without Comrade Patrick, there would be no new Release 15 COMING OUT THIS YEAR! Also, for those not in the know. NO SYSTEMD, NO PACKAGE MANAGEMENT, only good, old fashioned slackbuilds and init scripts, not that you'll need to install anything after booting into slack, unlike other distros, Slack prides itself on being one of the most obese out of the box, with the entire ubuntu repository preinstalled and ready to go, with a wide variety of.. ALL THE DESKTOP environments, but with KDE as the default. Additionally, all the installed software is STABLE and has been carefully kept vanilla, but seamlessly usable. Variety is truly the spice of life.(I combined your thread with the one it is now in. Please see the catalog before posting threads in the future.)

cant wait for slackware 15, the wait has been too long

>>56295 I feel like I'm too dumb to use Slackware, and yet also I'm not sure what I would get out of slackware that I would not get out of other distros.

>>56298 An absolutely slackeriffic computing experience, of course.

>>56297 Ditto, 2022 with a slackware release would be rad, cant have it all i guess, but lets see. >>56314 If you look for the oldschool hacker experience that would be your thing.

>>56295 >NO SYSTEMD, NO PACKAGE MANAGEMENT Slackware is awesome, but have you tried this new distro called Arch Linux..? It's similar, but it also includes a kickass package manager called pacman. There is also a community run repository of PKGBUILD files called AUR. Check it out!

>>56295 >>56349 Oh, and due to automatic package management it doesn't have to ship all the available software out-of-the-box. You can install anything you want from official repositories or AUR. Therefore the default image is much more minimal and you can keep only what you will use.

>>56349 Pacman is like kicking dead whales down the beach, rpm and portage are better.

>>56349 I like both, and in fact I use Arch because of how similar PKGBUILDs and SlackBuilds are. Problem is that there's no stable version of Arch.

>>56361 What is like kicking dead whales down the beach about pacman? Can you elaborate on your opinions?

http://www.slackware.com/announce/15.0.php Rejoice, for it is a joyous day!

I’ve never been a Slackware -stable user - I only dabbled in it when I was a kid in the late 90s, and while I’ve used it over the past few years I’ve only used -current. It feels very novel to be on the stable release now. How good is this :-) Just waiting for SlackBuilds.org to be rebased from Ponce’s repository so I can switch my sbotools over to 15.0 as well. One of these days I’ll wipe my computer and do a clean install too.

>>56641 SWEEEEEEEEEEEEEEEEEEEET! Time to party with slackware.

Does sbotools not allow you to check SlackBuilds before actually installing them? I whipped out some soykafty ad-hoc solution with bash and awk but there has to be a better way.

>>56678 What do you mean 'check SlackBuilds'? If you're just looking to inspect a SlackBuild script, there's an option to view the files in the SlackBuild

>>56767 Yeah, I want to read the slackbuilds with the dependencies. I didn't see an option in sboinstall.

i see that official site still don't update torrents to 15 version: magnet:?xt=urn:btih:ccf87debed487d8623404e93b22d2f3ff86a67b6&dn=slackware64-15.0-iso&tr=udp%3a%2f%2ftracker.bitsearch.to%3a1337%2fannounce&tr=https%3a%2f%2ftracker.lilithraws.org%3a443%2fannounce&tr=https%3a%2f%2ftracker.nanoha.org%3a443%2fannounce&tr=udp%3a%2f%2fbt1.archive.org%3a6969%2fannounce&tr=udp%3a%2f%2fbt2.archive.org%3a6969%2fannounce&tr=udp%3a%2f%2fexplodie.org%3a6969%2fannounce&tr=udp%3a%2f%2fopen.stealth.si%3a80%2fannounce&tr=udp%3a%2f%2fopentracker.i2p.rocks%3a6969%2fannounce&tr=udp%3a%2f%2fretracker.lanta-net.ru%3a2710%2fannounce&tr=udp%3a%2f%2ftracker-udp.gbitt.info%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.dler.org%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&ws=https%3a%2f%2fmirrors.slackware.com%2fslackware%2fslackware-iso%2fslackware64-15.0-iso%2fslackware64-15.0-install-dvd.iso https://seedbox.slackware.uk/

ayy slackware 15 boyz we eating good

Does the installer account for the presence of the patches directory on remote servers?

I find slackware's lack of systemd disturbing.

>>56863 What benefits would systemD have? From what I understand, systemD is rather bloated for an init system and offers an unnecessarily large attack surface as consequence. The current unit system used by slackware just werks.

>>56350 >Oh, and due to automatic package management it doesn't have to ship all the available software out-of-the-box. You can install anything you want from official repositories or AUR. When installing slackware, the user can select what packages they want to install and can go for as minimal an installation as they want. >Therefore the default image is much more minimal and you can keep only what you will use. Your argument is irrelevant.

why do people who have obviously never used slackware go "this distro sux! mine is teh b3st!", and make stupid claims based on half-formed misunderstanding instead of just acknowledging and respecting a much loved and historically important distribution? t. never used slackware either, but still celebrating the new release

>>56863 Sure, Lennart, because every GNU/Linux user has to be raped by your soykafware.

>>56890 the kde set kinda is like kicking dead whales down the beach you gotta admit. it has like 400 packages of soykaf you'll never use. a lot of it belongs in extra/ or its own set if you ask me. what slackware user NEEDS educational software?

>>56784 Sorry, I was thinking of sbopkg instead of sbotools - you're right, there is no way to check a SlackBuild before installing them using sbotools. (This is a function available in sbopkg, but then you don't get automatic dependency resolution ...) When you use sbotools, the entire SlackBuilds repository is stored under /usr/sbo/repo. If you are happy to look at files before installation this way then that would work. However, if you need to look at the SlackBuilds of dependencies I'm not sure this is possible, and even a bash and awk based solution looks hard because you need to handle nested dependencies I'm not sure sbotools is being actively developed so you might not have much luck asking the maintainer, you could try though

>>56860 Don't think so - I think you need to install and then apply patches, either downloading them and running installpkg or using slackpkg to do it for you

>>42840 >Slackware Security Advisories http://www.slackware.com/security/list.php?l=slackware-security&y=2021 >Security >http I know it really doesn't matter but slacks website needs a major over hall like artix has a better website and layout then slack >if the site looks nice more people will be more "trusting" https://artixlinux.org/

>>56983 Yeah, I could probably whip something up using sbofind and various pipes. Though I don't know if it's even worth it considering the inactivity for slackware 15.

>>56998 Do you mean on SlackBuilds.org? If you're not already aware, there is a repository https://github.com/Ponce/slackbuilds/ which is run by one of the maintainers of SlackBuilds website, where he tracked the -current branch for compatibility issues with Slackware -current. I think all he did for this was track up-to-date versions and made minor modifications to build scripts if they stopped working for some reason. (All other changes were rejected and people opening Issues on GitHub were asked to contact the package maintainers; eventually any larger changes upstream would be merged in) The SlackBuilds website _should_ be updated to support 15.0 soon, who knows when that will actually be though. You can pretty safely pull the Ponce SlackBuilds git though, that's what I'm using on 15.0 This doesn't help with reviewing SlackBuild scripts before you install them ... but there's plenty of activity on SlackBuilds, they are still actively supported and updated for new versions

>>57006 No, I know Slackbuilds are still being updated and I'm thankful for it. I was talking about sbotools, which I think makes more sense than sbopkg.

SlackBuilds.org was updated to support 15.0 a few days ago. Anyone still thinking about trying Slackware but holding back because of (easily discoverable) third party package support, there’s never been a better time than now.

Okay, I got the slack. Now what? Also, it's comfier than I expected, but docs could be a bit better.

>>58154 >Now what? Visit https://slackbuilds.org/ and/or Install Guix package manager (https://guix.gnu.org/en/#guix-in-other-distros). Then use it like any other GNU/Linux. If you are new to GNU/Linux, you should read https://linuxcommand.org/tlcl.php and learn a scripting language like Perl 5 (see perldoc perltoc ), Ruby (read the "pickaxe book"), Lua (https://www.lua.org/pil/contents.html), Tcl (https://wiki.tcl-lang.org/page/Tcl+Tutorial+Lesson+0 and the man-pages), Racket (https://docs.racket-lang.org/)...

>>58159 >Install Guix package manager That's a brilliant idea, I don't know why I haven't tried that before. Thanks, Lain!

>>58159 That was half-ironic, I (think I) know what to do - absolutely fuarrrking nothing, I have everything I need. I just compiled Blender from Slackbuilds and that's it. Also, I actually wanted to learn more about bash shell scripting, so thanks Lain! I am no stranger to GNU+Linux, but I only use the subset of bash sugar. I think I will skip on Guix for now, because I don't need that much software for now.

Does anyone know why with custom modules I can't use `insmod` on Slackware 15 anymore? I'm getting permission denied even on root.

>>58380 What exactly is the error you are getting? Is there a reason you don't want to use modprobe?

>>58382 >What exactly is the error you are getting? insmod: ERROR: could not insert module <module-name.ko>: Operation not permitted >Is there a reason you don't want to use modprobe? I'm a newbie and it's my custom module. Honestly, I don't know where to install it for modprobe to pick it up. There are no dependencies on other kernel modules. I had no issues on Slackware 14.2 nor Alpine Linux on kernel 5.15.

>>58385 >insmod: Operation not permitted Is the kernel built with modules loadable enabled? If lsmod returns nothing then that could be the problem. The other reason why leading modules won't work is if the kernel is a different version to the module. They both need to be built from the same kernel version.

>>58466 Good tips overall, but this time the issue was on me. >Is the kernel built with modules loadable enabled? On Slackware there are files under /boot/config-* with kernel configuration where you can also confirm that. >>58385 >Operation not permitted Apparently it must have been -EPERM from failing module_init (returning -1 by default is not the best practice). >Honestly, I don't know where to install it for modprobe to pick it up. Ok, now I know. We compile with: make -C /lib/modules/*/build M=$(PWD) modules and we can install with: make -C /lib/modules/*/build M=$(PWD) modules_install Then it's possible to use modprobe, but for quick hacking insmod should be perfectly fine.

>>58471 >returning -1 by default is not the best practice In C and unix 0 is success and everything else indicates an error.

>>58484 Yes, but in UNIX you should use errno(3). Also, see APUE. Or at least print something. Otherwise, the error won't be very helpful.

>>58486 Clearly you already know everything.

>>58159 Slackware * Download Slackware installation iso from a mirror and prepare an installation media (USB memory stick) and boot from the USB memory stick. During the boot, Slackware will ask you which kernel to use. Select "huge.s". * Log in as root and partition the disk using fdisk/gdisk. * Start the installer: % setup * Install all software sets (you can deselect Xfce4 and/or KDE if you want to) Post installation $EDITOR /etc/slackpkg/mirrors # select a mirror slackpkg update slackpkg upgrade-all # generate initramfs: # https://mirror.de.leaseweb.net/slackware/slackware64-current/README.initrd cd /boot mkinitrd -c -k 5.15.27 -m ext4 # if you want grub slackpkg remove lilo slackpkg search grub slackpkg install grub grub-install # ... grub-mkconfig -o /boot/grub/grub.cfg How to use Slackbuilds * Go to https://slackbuilds.org/howto/ * Pick a package, like SBCL: https://slackbuilds.org/repository/15.0/development/sbcl/ * Download the source from the link "sbcl-2.2.2-source.tar.bz2" * Also, Download the slackbuild script "sbcl.tar.gz" * Verify the checksums * Become root: % su --login root || sudo -i * untar the slackbuild tarball (in this case "sbcl.tar.gz") * Copy the source tarball (sbcl-2.2.2-source.tar.bz2) to the same directory where you extracted the contents of the slackbuild tarball. (you should now have the source tarball and the slackbuild script in the same dir) * cd to the dir that contains the contents of the slackbuild tarball (and the unextracted source tarball) * Read the README(s) * run the slackbuild script: ./sbcl.SlackBuild * the newly created packgage is in /tmp dir * install it by: installpkg /tmp/sbcl-2.2.2-x86_64-1_SBo.tgz Other options for more getting packages * a Gentoo Prefix https://wiki.gentoo.org/wiki/Project:Prefix * GNU Guix package manager https://guix.gnu.org/en/#guix-in-other-distros * Ravenports http://www.ravenports.com/ & https://github.com/jrmarino/Ravenports/wiki/quickstart-linux * Pkgsrc https://www.pkgsrc.org/#quickstart * Flatpaks...? (get it from Slackbuilds) Pkgsrc Download the Download the stable branch as a tarball from https://www.pkgsrc.org/ Prefer installing pkgsrc under your $HOME, unless you want to install daemons. cd pkgsrc/bootstrap # install under $HOME: ./bootstrap --unprivileged --make-jobs 4 # system-wide install # without specifying the prefix, pkgsrc will be installed to # /usr/pkg{bin,man} dir, unless you use --unprivileged option. #./bootstrap --prefix /opt/pkg-2022Q1 [--prefer-pkgsrc yes] --make-jobs 4 # update your user's PATH and MANPATH. # https://opensource.com/article/17/6/set-path-linux cd .. #bmake search racket # this takes a lot of time on the first time you search something. cd lang/racket bmake readme bmake bmake install

i tried slack once but didnt like the package management

>>59816 Fair enough, that's a good enough reason not to like a distro. For me the package management works fine once you pick the tools you like - I like slackpkg for packages which are part of the distribution, sbotools for SlackBuilds, and Flatpak for everything else (programs I can't be bothered compiling, update frequently, don't have SlackBuilds or don't have maintainers for their SlackBuilds, or are proprietary). I'll also use pkgtools directly for SlackBuilds which I have written myself rather than mucking around with submitting them to slackbuilds.org. I find the simple init system and the fact that you get the whole kitchen sink with a full install make up for the lack of general support for third party packages.

I use Slackware on my old Thinkpad X200. It's just a hobby/tinker laptop so I don't use it for anything work related, but there's something so satisfying behind the process of installing each dependency from SlackBuilds, I get into a zen-like state. On my main computer I use a normal person distro because I need it for work and certain hobbies, but I just love being on Slackware, it's comfy and only has what I need in the way that I need it, it really feels like my own custom OS at this point.

Installed slack this weekend and it seems like a distro that has both great defaults and great freedom for customizability. I don't really care for manually installing dependencies, so I'm using the Guix package manager and it's working as intended, as far as I can tell. Eventually I'd like to try my hand at changing whatever slack uses as PID 1 to GNU Shepherd, so I can have a Guix-like distro without the inconveniences of using Linux-libre on a 2022 laptop.

>>62315 >so I can have a Guix-like distro without the inconveniences of using Linux-libre on a 2022 laptop. You could use Guix System with Nonguix: >https://gitlab.com/nonguix/nonguix >https://wiki.systemcrafters.cc/guix/nonguix-installation-guide

>>62316 I tried that too, still didn't work sadly. It didn't list the drivers for my network card. It's weird because both were using linux 5.18, but well, not too much of an issue. Slack is working nicely.

Why are so many SlackBuilds behind? Kinda is like kicking dead whales down the beach to have to increment the version number yourself.

>>62230 I get that from openbsd with their documentation. Having all those manpages and other helpful docs in your system and being able to customize everything is something no other distro can achieve. By default everything works like they should, you can waste time only if you want to.

>>62444 >Why are so many SlackBuilds behind? I guess the Slackware community is not that large anymore and only certain % of people will become package maintainers. >>62446 >and being able to customize everything is something no other distro can achieve. The OpenBSD docs are great but I don't understand what you mean by this since you can customize any *BSD or GNU/Linux distro, too.

>>62447 >The OpenBSD docs are great but I don't understand what you mean by this since you can customize any *BSD or GNU/Linux distro, too. You are right, what I meant was that because of the documentation, it's a lot easier to customize than other bsd or linux distros.

I love how trivial creating Slackware packages is. I package pretty much everything I compile. All you need to do is point DESTDIR to some temporary folder and run makepkg in it.

Is adding the other non-alienbob repos in slackpkg+ recommended? I noticed the Salix repo has MPV already built along with its dependencies.

I fuarrrkING DID IT, NERDS! https://files.catbox.moe/zwqgfw.tgz I HAVE SUCCESSFULLY PORTED XBPS TO A SLACKWARE 15.0 BINARY! SLACKWARE LINUX NOW HAS A MODERN, LIGHTWEIGHT PACKAGE MANAGER.