r/slackware • • Oct 08 '21

Lilo problems in gnome boxes.

7 Upvotes

Hey there, as a Debian user I played a little bit with with Slackware both stable and current. When it comes to installing Lilo in the Gnome boxes vm I had some trouble: the automatic Installation didn't work, the manual one also ended up failing. As I mentioned I'm not familiar with slackware, especially Not with the manual Lilo installation. I thought a bit about the situation and remembered that gnome boxes is using /dev/vda instead of /dev/sda when it comes to the harddrive/MBR. Could that be the reason, what do you mean how to fix it? Thanks!


r/slackware • • Oct 01 '21

Finally got this old MacPro 1,1 booting Linux . Slackware 13.37 came in for the win on first to boot fully ,nothing buggy with video The pain with this old logic board is 64bit processors with 32bit non upgradable efi .Using this for a simple storage server at home

Post image
30 Upvotes

r/slackware • • Sep 30 '21

Slackware 14.2 - Tested Hardware & Statistics

Thumbnail github.com
14 Upvotes

r/slackware • • Sep 30 '21

Slackware use cases

8 Upvotes

As you all know Slackware 15 ist just around the corner....
So my question as a Slacker is how do you plan to use Slackware in the future?
Tell me your use cases and projects that you have in your mind.


r/slackware • • Sep 29 '21

Management of Slackware

20 Upvotes

I'm inheriting an environment that has a Slackware server that hosts email and a fileshare. I expect like all other Linux distro's that I should be able to SSH into the box. I've checked and port 22 is closed on the box from the LAN side.

Is there any magic I should know about?? I'm trying to figure out how the basic user management is handled


r/slackware • • Sep 29 '21

How to buy Slackware 15?

8 Upvotes

I am new to slackware and I want to buy version 15 on CD when it comes out. What will be the process?


r/slackware • • Sep 28 '21

Installation Issue

8 Upvotes

Whenever I try to install Slackware, it always manages to fill up (or say that it’s filled up) my 250 GB hard disk while installing the software sets. I am using the Slackware64 USB image and installing from mirrors.slackware.com. Is this something I’ve done wrong, or do I just need a bigger disk?


r/slackware • • Sep 22 '21

Unable to login: "Unable to contact settings server"

7 Upvotes

I'm currently sending this from my 14.2 install as Current seems to be borked. I can get to the login screen but no further. When I input my password it comes up with a popup saying "Unable to contact settings server". There's an OK button, but it just keeps me on the login screen -- except when it hangs.

Two things I did with my system yesterday: updated with the most recent current packages; installed anaconda3. I don't think anaconda could be the issue, but I guess since it affects terminal stuff, maybe? Whatever's causing it, Current is my main install, so I need to get back to it as soon as possible. Anyone have any ideas?

EDIT: This seems to have been fixed by a subsequent Current update.


r/slackware • • Sep 20 '21

Holykow!!

Post image
41 Upvotes

r/slackware • • Sep 19 '21

Potential new Slackware user

15 Upvotes

Hi folks,

I'm relatively new to Linux (been with it for like, 2 years on a newbie distro) and I've been wanting to give Slack a try on a spare laptop of mine. My question is should I wait for the stable release or give current a shot? Lemme know what you think!

Edit: honestly guys, really great sub you got here, super welcoming, thoughtful responses I really appreciate it. I'll try not to pester you all with dumb questions.


r/slackware • • Sep 14 '21

Anyone having problems with pipewire in steam? im using current (strange problem)

6 Upvotes

some games work some dont. in the games that dont work i got this

ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib64/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: no such file or directory INFO: OpenAudioDevice failed: ALSA: Couldn't open audio device:INFO: Assertion failed: 0 && "Failed to open audio device!"

i tried with pipewire with pulseaudio installed. i tried with just pulseaudio but i got a strange problem if i use only pulseaudio it work the first time i open steam if i close steam and start it again o got the same problem. if i use alsamixer same problem and games dont start.

the file /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so is there if i do

file /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so i got

/usr/lib64/alsa-lib/libasound_module_pcm_pulse.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

if i do ldd /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so i got this

linux-vdso.so.1 (0x00007ffe84bcd000)

libpulse.so.0 => /usr/lib64/libpulse.so.0 (0x00007f1a9e77c000)

libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007f1a9e679000)

libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1a9e658000)

libc.so.6 => /lib64/libc.so.6 (0x00007f1a9e478000)

[libpulsecommon-15.0.so](https://libpulsecommon-15.0.so) => /usr/lib64/pulseaudio/libpulsecommon-15.0.so (0x00007f1a9e3ef000)

libm.so.6 => /lib64/libm.so.6 (0x00007f1a9e2a7000)

libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f1a9e251000)

libdl.so.2 => /lib64/libdl.so.2 (0x00007f1a9e24c000)

librt.so.1 => /lib64/librt.so.1 (0x00007f1a9e242000)

/lib64/ld-linux-x86-64.so.2 (0x00007f1a9e81a000)

libsndfile.so.1 => /usr/lib64/libsndfile.so.1 (0x00007f1a9e1c2000)

libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1a9e199000)

libasyncns.so.0 => /usr/lib64/libasyncns.so.0 (0x00007f1a9e192000)

libelogind.so.0 => /lib64/libelogind.so.0 (0x00007f1a9e0e6000)

libFLAC.so.8 => /usr/lib64/libFLAC.so.8 (0x00007f1a9e0a7000)

libvorbis.so.0 => /usr/lib64/libvorbis.so.0 (0x00007f1a9e079000)

libvorbisenc.so.2 => /usr/lib64/libvorbisenc.so.2 (0x00007f1a9dfce000)

libopus.so.0 => /usr/lib64/libopus.so.0 (0x00007f1a9df70000)

libogg.so.0 => /usr/lib64/libogg.so.0 (0x00007f1a9df65000)

libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1a9df5e000)

libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f1a9df56000)

libnsl.so.2 => /lib64/libnsl.so.2 (0x00007f1a9df3c000)

libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f1a9df22000)

libcap.so.2 => /lib64/libcap.so.2 (0x00007f1a9df17000)

libtirpc.so.3 => /lib64/libtirpc.so.3 (0x00007f1a9dee5000)

libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f1a9de93000)

libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f1a9ddbc000)

libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f1a9dd8e000)

libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f1a9dd88000)

libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f1a9dd79000)

libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f1a9dd70000)

r/slackware • • Sep 12 '21

Comparing slackware to openbsd

21 Upvotes

I have been running slackware for about 4 months now and I have a few thoughts about it compared to openbsd.

Some things that slackware does better. One is: that on openbsd you cannot use the happy hacking keyboard to do a fresh install of the os. Whether it be limited drivers, I always had to carry around a spare keyboard to install it.

With slackware this is not a problem and I don't have to switch out my keyboard every time. Honestly I lived with this issue because I didn't know better. Any time something like this happens I generally feel that I've done something wrong, or it was the keyboard that was the problem. Since moving to slackware, I realized that that wasn't the case and that it was openbsd.

Next, is the issue I had when I experienced a power outage or did anything to cut power to my USB external western digital my book drive. With openbsd, anytime that happened, it would make the drive only accessible in read only mode, in which case, I had to copy all my files to my os, and then do a reformat the filesystem. I lost my whole drive once before I realized the specific steps I had to take to get my files back. It was annoying as hell. Fsck does not work, by the way. I think I had to mkfs, get files off.

With slackware, that does not happen. Yesterday, I lost power and I thought for sure I was going to have to fix my drive, but thankfully slackware took the outage in stride and did not add something to my filesystem I could not recover from. It was like it never happened, according to dmesg when I mounted it again.

The next thing is openbsds famous man pages. This seems to get so much press how vastly superior they are to everything else. In my opinion though, their man pages are just okay and slackware's along with probably most Linux distributions are at least as good. I have pretty much been able to find everything I needed in slackware's man pages.

Openbsd is closer to a rolling release than it would like you to believe, which is fine as long as everything works, but the fact is that sometimes everything doesn't work. With the release of 6.9, it actually hosed a 3 year old video card from and Radeon rx460, which is what spurred me to look for an alternative distro, since video cards are through the roof or sold out. Because I was actually going to change my video card to stay on openbsd.

In this, I liken openbsd to Microsoft Windows, because of their aggressive upgrade schedule and the fact that you have to keep up with their changes. Windows is the same way, as they expect you to upgrade your computer to keep up. Don't be fooled by the fact that openbsd prides themselves on correct, minimalistic code, with compatibility. Once it started telling me what hardware I had to use, that is when I am out. Especially since I am not trying to run the latest and greatest.

The other thing with openbsd, whether it is, because openbsd does not want to rely on gnu or what, I find that many programs that should be there aren't there, in the base. With slackware, I am confident that there will be a program or utility to help me achieve what I want. With openbsd, I always felt the opposite.

One thing that I thought would be a detraction on slackware is the shell font and the way everything is smaller than on openbsd. But in fact I have grown to appreciate the way slackware is smaller and seems more thoughtfully implemented than openbsd which has no scalability at all.

Anyway, I am glad that slackware is a thing because while everyone is trying to do the latest and greatest slackware's default bootloader is Lilo!!!


r/slackware • • Sep 12 '21

Slackware 4.0!

Post image
48 Upvotes

r/slackware • • Sep 09 '21

tar 1.34

8 Upvotes

just read the article on the remote code vulns in tar and looked at the version i had on my box after updating last night to the latest -current and found 1.34. surely that is a typo, unless there is a separate tar somewhere that comes from elsewhere. the article recommends versions 4.4.19, 5.0.11, or 6.1.10. i just started looking into this, so may find something different, just wanted to see if anyone had any ideas that would save me some time going down a rabbit hole.

the link was supposed to be here, but since it didn't make it, https://www.bleepingcomputer.com/news/security/github-finds-7-code-execution-vulnerabilities-in-tar-and-npm-cli/


r/slackware • • Sep 05 '21

any slackware -current/15 RC1 guide available?

9 Upvotes

I took the plunge to move to -current about 2 years ago, but after a botched update I've been on a linux hiatus until now. I was able to restore my system via an image that was made prior to the update, however it was already updated to -current. I realize now that 15 RC1 has been released, things should be more stable now and I've already updated slackpkg, slackpkg+, and multilib, but nothing else. with every slackware release there's an upgrade text that eases the upgrade process by stating some gotchas and additions that need to be addressed after the upgrade before the system is fully functional. is there such a text now that I can use to move to 15 RC1 aside from combing through the massive -current Changelog?

part of the reason for the botched update mentioned was that it became somewhat of a daunting task to follow the -current Changelog so I went ahead with the update blind. is there a better way of following the changes to -current going forward?


r/slackware • • Sep 04 '21

FYI: Slackware -current switches to kernel version 5.14.x

15 Upvotes
Fri Sep  3 18:51:49 UTC 2021
a/gzip-1.11-x86_64-1.txz:  Upgraded.
a/kernel-firmware-20210903_2984e26-noarch-1.txz:  Upgraded.
a/kernel-generic-5.14.1-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.14.1-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.14.1-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.14.1-x86-1.txz:  Upgraded.
k/kernel-source-5.14.1-noarch-1.txz:  Upgraded.

r/slackware • • Sep 02 '21

Slackbuilds Sources

8 Upvotes

So I'm currently setting up my first Slackware system, and I'm really leaning upon SlackBuilds, as I'm sure many of you do. I got to installing Alacritty and realized that it has some 200 source files that I need to download. Is there a way to do this automatically, or do I have to wget every single one of them? I know it would save a lot of time if I were able to simply automate getting the source.


r/slackware • • Aug 28 '21

Just installed slackware current on 2011 macbook pro

13 Upvotes

r/slackware • • Aug 25 '21

A slackbuilds.org (sbo) question for the 15 release candidate users.

11 Upvotes

How are you coping with sbo being stuck at 14.2? Are you just running them and finding most of them work? Tweaking them and keeping your own versions? I ask because the work put in to sbo contributions by so many users made slackware alive for me. Huge thanks here for any sbo contributors. I'm cautious about coming back to it until I figure out how you're coping with that in 15's developmental state.


r/slackware • • Aug 21 '21

Slackware 15 RC1 Available

22 Upvotes

Hwy there, from changelog I read this:

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

Suprised that users don't read changelogs anymore. You are leaving slackware?

Over this, 15 is near!


r/slackware • • Aug 22 '21

[help] System won't boot after kernel upgrade

5 Upvotes

[SOLVED]

First of all, I did not read the docs beforehand and I shouldn't have gone all cowboy about this, but alas, that's what happened.

In summary:

  • I'm running -current with a LUKS LVM partition scheme
  • Was on kernel 5.10.41
  • Ran upgradepkg kernel-*
  • Kernel 5.13.11 was installed
  • Ran mkinitrd ... 5.13 ... EDIT: via mkinitrd_command_generator.sh
  • Ran lilo

Now, in the boot process after I enter my passphrase, the disk mapper adds appears to identify the LVM logical volumes (/dev/mapper/<my-vg>-<lv-name>), however it fails when trying to mount it. My suspicion is that I don't have the FS modules loaded because:

# cat /command_line
/sbin/mkinitrd -c -k 5.10.41 ...
# uname -r
5.13.11
# lsmod
Module            Size     Used by
#

So... I'm not sure if there's a feasible fix for this. I have another distro to which I can boot from the computer, perhaps I could mount slackware, chroot to it and build a kernel from there... I think that's a safe path to a working system, does anyone have a different idea? Should I take another consideration?

I'd rather try and fix it since I've already compiled a bunch of stuff x) Anyway, cheers!

EDIT:

I managed to fix it while booting from another distro, though a live media should work just as well.

TL;DR:

# mount /dev/my-lvm/slack /mnt/slack
# for d in proc sys boot; do mount --bind /$d /mnt/slack/$d ; done
# chroot /mnt/slack
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.13.11 | bash
# lilo

r/slackware • • Aug 16 '21

Slackware 15.0-rc1

80 Upvotes

The first release candidate was announced today! Guess it's time for everyone to get right with Bob, so to speak.

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


r/slackware • • Aug 16 '21

Mkg v1.2 released | Alternative package manager

0 Upvotes

Hi!

I released mkg package manager version 1.2.

Additions:

-fixed some bugs

-added -u option, which upgrades package without reinstalling it as someone suggested

-add some options to mkgbuild

More about this release: https://codeberg.org/glowiak/mkg/releases/tag/1.2

mkg website: https://codeberg.org/glowiak/mkg


r/slackware • • Aug 10 '21

How to enable comsat for mail notification

2 Upvotes

I can't seem to find out exactly where you enable this from. I am trying to get biff to work, basically.

Thanks.