Options for those not wanting systemd as Wheezy EOL looms

If it doesn't relate to Debian, but you still want to share it, please do it here

Re: Options for those not wanting systemd as Wheezy EOL loom

Postby Wheelerof4te » 2017-08-22 19:23

^Yeah, antiX is great for older 32-bit systems. Don't mix repos, though.

@HuangLao
Agreed, let's keep it simple. This topic is mainly for Wheezy users, we aren't trying to switch people to using rc-init or sysv. I have an old desktop PC unplugged in my room that might run FreeBSD (it's Intel Celeron D CPU single core with ancient Nvidia card). If I find time, I will try messing with it. It has Xubuntu 14.04 on it, but that is EOL since April this year anyway.
Options for users who don't like systemd as Wheezy EOL draws near
Debian 9 GNOME
Intel Pentium 3825U Broadwell
AMD Radeon R5 330m
8GB DDR3 RAMesting
User avatar
Wheelerof4te
 
Posts: 394
Joined: 2015-08-30 20:14

Re: Options for those not wanting systemd as Wheezy EOL loom

Postby Lysander » 2017-08-23 11:39

HuangLao wrote:yeah, KDE is lighter then it was but in comparison to the hippo it used to be its still heavy. 1GB of RAM would be better for Xfce or a WM. There is LXDE or even LXQt in slackbuilds.org or you can use prebuilt binaries from Salix or AlienBobs repo (a slackware dev. Eric H.).

aliens x86 repo: http://slackware.uk/people/alien/sbrepos/14.2/x86_64/
alien restricted repo (vlc with codecs) http://slackware.uk/people/alien/restri ... .2/x86_64/
alien kde 5 packages: http://slackware.uk/people/alien-kde/14.2/5/x86_64/

Keep in mind aliens repos do not track dependencies, so read the info/readme for the main package and it will list the dependencies. His VLC package has all the dependencies included in the package. Just install VLC and you get everything it needs including codecs.

If you are going to use repos other than main slackware that comes in install, then install slackpkg+ which is an extension for slackpkg that allows third party repos. https://alien.slackbook.org/blog/introd ... ositories/

Of course, you could also use slapt-get on Slackware and get the packages from Salix. ;) Happy Slacking.


I think my question about KDE may have been answered, apparently Virtual Box and KDE don't like each other much [yes that topic is two years old but I would be surprised if the issue had been completely solved, especially drawing from my own experience].

This list of programs like slaptpkg, slapt-get and slapt-src can get a little confusing but I think I have my head around it. From what I can see neither slapt-get nor slapt-src are entirely necessary especially if one does a full install. However, I will install them because I like the apt system of doing things and it's good to have options.

Slackware 14.2 uses Mesa 11.x - not sure whether I should use these or the proprietary ATI drivers instead?
User avatar
Lysander
 
Posts: 332
Joined: 2017-02-23 10:07
Location: London

Re: Options for those not wanting systemd as Wheezy EOL loom

Postby HuangLao » 2017-08-23 16:08

Lysander wrote: I think my question about KDE may have been answered, apparently Virtual Box and KDE don't like each other much [yes that topic is two years old but I would be surprised if the issue had been completely solved, especially drawing from my own experience].

This list of programs like slaptpkg, slapt-get and slapt-src can get a little confusing but I think I have my head around it. From what I can see neither slapt-get nor slapt-src are entirely necessary especially if one does a full install. However, I will install them because I like the apt system of doing things and it's good to have options.

Slackware 14.2 uses Mesa 11.x - not sure whether I should use these or the proprietary ATI drivers instead?


Stock install should work fine for drivers. Regarding package managers on Slackware, for those that like the benefit of the package manager not automatically installing dependencies then slackpkg and the extension slackpkg+, and sbopkg for slackbuilds source scripts are more then enough. slapt-get and slapt-src are for those that want dependencies automatically installed each time they install a program.
User avatar
HuangLao
 
Posts: 332
Joined: 2015-01-27 01:31

Re: Options for those not wanting systemd as Wheezy EOL loom

Postby HuangLao » 2017-08-25 17:18

A Slackware thread that I thought could be of interest here:
https://www.linuxquestions.org/question ... 175608156/
User avatar
HuangLao
 
Posts: 332
Joined: 2015-01-27 01:31


Re: Options for those not wanting systemd as Wheezy EOL loom

Postby kedaha » 2017-08-26 08:10

I am a pragmatic Debian user and prefer to use a system which I know well rather than chop and change.

My knowledge is essentially practical: I know stuff like how to set up and configure systems, backport programs and to solve many problems by consulting the man pages and online searches; however, I know very little about systemd and how it works. Similarly I knew very little about init. Like the linux kernel, the operating system itself, the inner workings of systemd are completely invisible to me except when I use certain commands to troubleshoot services.

So I know how to make things work but I don't know much about how they work. I know that if I follow a guide to installing, for example, postfixadmin, I can get it up and running but more often than not I don't know the whys and wherefores.

My pragmatism does not extend to using nonfree software just because it works; in fact I avoid it entirely.
I am not a programmer (beyond a sprinkling of of html and the hello world program) or a developer; the only thing I can do is systems administration using bash or dash. So I don't have the technical expertise to know whether systemd is better or worse than init for me as a user,

Having said this, I would mention that I've converted an installation of "jessie" to Devuan and signed up for the forum over there. I think maintaining different options is better than a one-size-fits all approach and I hope to learn more about both init and systemd over the course of time.
I have an interest in other operating systems like the BSDs but I already have more than enough on my plate with the complexity of perfecting just my email system to up sticks and move to, for example, FreeBSD, certainly not on my server.

I think I'd have far fewer problems in using a BSD as a desktop system and I definitely would move to a BSD if I were unable to use the Open Sound System (OSSv4) instead of ALSA in Debian.
Mate DE & OSSv4.
LaMp, WordPress; ispmail
Debian Stable & Software

Words, as is well known, are the great foes of reality. Joseph Conrad.
User avatar
kedaha
 
Posts: 2797
Joined: 2008-05-24 12:26

Previous

Return to Offtopic

Who is online

Users browsing this forum: No registered users and 1 guest

fashionable