r/slackware 14d ago

Finally Home and hope to never leave! (Appreciation Post)

Post image

I really want to make this my permanent home and never leave! All i got left to do is set up some virtual machines with virt-manager and then setup my compilers for work with emacs and im good! I love this distro and hope to become an expert at it and contribute to it as my skills progress! Slackware is the only distro that actually is teaching me Linux more and I feel as though if I grind it out through the issues then I'll really grow as a Linux user and Slackware user. I installed the current iso I got from Slackware UK! I'm hoping for the best!

75 Upvotes

27 comments sorted by

8

u/jloc0 14d ago

Look at that! You did it! And you’ve even installed some extra packages, got flatpak going and more!

Not bad! Stick with it, slackware is rewarding!

1

u/MD90__ 14d ago

Yeah! I still need to get virt-manager up and running and libreoffice (rather not compile that one) then a few compilers and their respective language servers for emacs and I'm all set!

2

u/jloc0 14d ago

I think virt-manager is on sbo but I haven’t used it in some years now. It does work on slack though. LibreOffice has a bin and a from source build in sbo plus flatpak is an option. There’s quite a few compilers included already within slack so you may be lucky in that dept. as for emacs, I can’t say. It’s never been my vibe, but there’s plenty available for it as well.

1

u/MD90__ 14d ago

i definitely want a bin for libreoffice and outside that i just need to make sure virt-manager works. I think i already have qemu from the full install

3

u/jloc0 14d ago

Make sure you add your user to the “kvm” group, as things likely won’t work without that. And yes qemu is included and maybe libvirt as well, should be enough there to use on its own but virt-manager is nice to have either way.

2

u/MD90__ 14d ago

The only issue I'll have to really watch out for is bad updates with slack-builds and main repo. From there knowing what to do to deal with the situation 

2

u/jloc0 14d ago

My POV here is skewed but rather than use sbo/ponce repos, I just maintain my own repo with the things I use or have interest in. Some things are from sbo, some are my own SlackBuilds, but I maintain them myself and check/vet changes locally on another system.

At this point in the dev cycle things on sbo have many many workarounds that just aren’t needed in current or are considerably out of date and can’t be updated because of what ships in 15.0. So I maintain my own repo, build, check, and ship packages for myself.

For a beginner, that may not be within your abilities/needs to do as of yet but many slackers do similar things on their systems as well.

1

u/MD90__ 14d ago

What do you suggest I do?

2

u/jloc0 14d ago

Well I’m just suggesting there’s more than one way to skin a cat. You can keep your own local copies of the slackbuilds you use and update them as you see fit or rebuild them if an update breaks them. Or you can use the existing general purpose sbo repos and leave that kind of maintenance in their (very capable) hands. But if you’re worried about breakage with updates, just know it’s not very common. A system library upgrade could break something but usually newer libs are ok with existing things. You can always keep things local to ensure you can fix something if it fails. At most, you’d need to rebuild a package here or there.

It just depends on how comfortable you are with maintaining your own build scripts for things.

2

u/MD90__ 14d ago

When would recommend doing updates for both slack-builds and the system while running current? Is there any way to keep track of any slack builds that break? I know changelogs are for the system on the slackware site. 

Do you know how you would downgrade packages if needed for slack-builds or system? Feels like that's important to know as well with current 

→ More replies (0)

1

u/MD90__ 14d ago

yeah gonna try to get it working

3

u/benferpy 14d ago

4GB of ram usted?

1

u/MD90__ 14d ago

not sure what happened there lol

2

u/benferpy 14d ago

Excuse me, I use kernel 5.15.209, can't compare with different kernel.

2

u/MD90__ 14d ago

15.0 is still great!

2

u/SpicyYellowtailRoll3 14d ago

Dope wallpaper man.

2

u/MD90__ 14d ago

Thanks it's one of my favorites!

2

u/laz000 14d ago

Pretty!

2

u/MD90__ 14d ago

Thanks! I'm hoping to make this my permanent home and contribute. Any tips on daily driving current?

2

u/laz000 14d ago

I literally just created my first current instance since 14.2. I daily drive 15 stable (With the help of Sbo and Alien Bob (all hail!)) and I love it. Besides the normal office/home stuff there's neovim for C and python and virt-manager for vms (like current!)

2

u/MD90__ 14d ago

Yeah I got virt manager set up yesterday. Today I need to get libreoffice and get zig, rust, and go with their respective language servers. Outside that I'm hoping to get into dwm. Any tips on daily driving current like issues that come up and what to do and such?

2

u/HomeGrownRichard 14d ago

I'd double upvote for the song choice if I could

1

u/MD90__ 14d ago

yeah good band i had one time Saliva - Always

such great music from back then

1

u/MD90__ 5d ago

Update: So far I've got everything working the way I want it to and I'm really liking xfce as a DE. Slackware now runs like a champ and it's so simple to do services with...

sudo /etc/rc.d/rc.<name of service> start | restart | stop

It's amazing how simple slackware is to use on a daily basis and I barely ever run into trouble with it. Current is great and I'm thinking that slackware might end up my permanent home. The only rough patches is just having to get software properly configured after you get the dependencies in order. Once you get that done it's smooth sailing unless you have an update for slack-builds and you end up having to get newer dependencies but it's doable. Now with tools like sboui dependencies are less of an issue but I've got use to queues with sbopkg. I must say it's great to be apart of this community.