t0m5k1 @ t0m5k1 @lemmy.world

🤞🏻🇺🇦 ✌🏻🙏🏻 🤜🏻👈🏿 🐧🖥

---

Read more

Posts

3

Comments

178

Joined

2 yr. ago

Well done rishi, screwed us as chancellor and now following through as a pm. 👍🏻

Just one junta supplying another junta.

Cheers.

Yaaaay another black market. Just what the government needs, gotta keep the black budget funded.

I've not used conky since 2018.

My authy came from aur, no snap required.

Yup, windows is calling you.

Bye

Keep telling yourself that, meanwhile we'll all see your obvious dislike of of general userland tools.

You clearly didn't read did you:

The makedeb Package Repository (abbreviated MPR) is a user-maintained repository of build files (PKGBUILDs) that can be built with makedeb and then installed with APT.

Here's a handy chart for you

https://wiki.gentoo.org/wiki/Comparison_of_init_systems

As you can see many have the ability to start services in parallel. Some script magic with graphviz will also do similar to analyse blame.

What's wrong? Too many tools, way too fragmented and poorly integrated. It is very, very easy to get into trouble if you simply setup a dual stack system with IPv6-PD with those tools. With systemd it all works of the box with simples configuration files and its way more intuitive. For eg. cron is a mess, systemd timers share the unit config format which is way better and more scalable.

Do you honestly beloved thie mental gymnastics your getting into just to prove your point, go back to windows. Lol

Well done on using systemd how you wish, now move on and let others use it how they wish or remove it.

Why anyone would buy into this crap is beyond me.

That list of "features" never needed to be replaced by systemd and for the most part are provided by the other init offerings.

As for logging you may find yourself one with a system using systemd that has faced an error and cannot boot good luck reading the binary journal it makes, yes these entries can be pushed out to text file or syslog but if systemd falls over hard it will log to the default binary journal and you'll need to use another install with systemd to run journalctl --file /path/to/mounted/journal which in an emergency is a true PITA.

It is not an outlet for those who you choose to espouse as "People who don't want linux to evolve" far from it most of them just want systemd to stop trying to replace things that are not broken and for other projects to stop having it as a hard dependency. Yes it is modular, yes these can be disabled but it has so many tentacles that it is clear the intentions are wider than just being an init.

What's wrong with ip, iproute2, iptables/nftables, ufw, firewalld, ntp, dnscrypt, privoxy, dnsmasq, openresolve, crond, sudo, mount, syslog-ng?

Are they somehow obsolete now?

If you want a basic bootloader your UEFI has one built in and/or you can boot the kernel directly with efistub, systemd-boot is so basic it's pointless to the point that an unconfigured install of refind is a truckload better.

I get that this is a hot topic but waaay too many people are just adding pointless opinion and toxic opinion into this debate that doesn't help anyone make what they want is a decent informed choice and tbh when I see Gnome make a hard dependency of systemd it makes me think either systemd is doing too much, is not modular enough, devs got lazy or all of the above.

And a final FYI I use systemd and have disabled much of it but can't uninstall the parts I don't need/want.

The kind of suggestion that does fuck all. Don't force your myopic ignorance on others.

He was only mentioned because of JavaScript and evading it. Really helps when someone tries to draw all the focus on one tiny part of an article.

If you're a new user you'd be better off moving on from here and not paying much attention. It's a hot topic full of opinions that everyone will want to force on you.

If you really want to swap out the init system there are some things you need to know.

First, do you need a desktop environment(DE)/window manager(WM)? If so you'll need to find a DE/WM that is not going to demand you use the mainstream init choice which currently is SystemD. If you want to use Gnome from your chosen distro repo's then chances are it will pull SystemD with it.

If you want Gnome but not SystemD you're gonna be building that beast from source every update and for the most part you'll need to go direct to Gnome for any issue/bug you fall over and this too will be painful.

Simpler WMs will be more forgiving and will only rely on either xorg or wayland and will happily run on any init.

There will be other packages out there that also demand you use SystemD, so you'll have to find them and decide if you need them or if there are alternatives that don't have a hard dependency on SystemD.

All the current usable inits are written in C or C+ (except for GNU Shepherd, this is written in guile).

The benefit of swapping out the init system is mainly down to choice, necessity but again this all boils down to what the installation is for and what will it be doing.

For a good run down of the features of the init systems refer to these 2 urls: https://wiki.gentoo.org/wiki/Comparison_of_init_systems https://wiki.archlinux.org/title/Init

All of the init's (except for epoch) provide parallel service startup so if boot time is a focus test each to find the fastest for your platform, Not all of them provide per-service config.

For example one can cobble together: minirc, busybox, syslogng, crond, iptables, lighttpd.

And the end result would be a relatively secure webserver with a small footprint, you could further extend this with nginx to sit in front of lighttpd to provide waf and cache features.

The biggest bug bear with SystemD is that it writes to binary log files and even though it can be configured to generate plain text, if it falls over in a bad way you will still only get a binary log file and if you're in a situation where your only access is say busybox for emergencies. In this instance your only option is to boot from another systemd distro and mount the broken install and run:

$ journalctl --file /var/log/journal/system.journal

Other than that many take issue with SystemD trying replace parts of the system that many say don't really need replacing like sudo, fstab, resolv.conf, etc but again these statements get full of opinion and don't help us truly way up the differences and some of the SystemD alternatives misbehave or become hard dependencies other projects which makes it harder to disable parts and swap out to your chosen package.

I've tried to be more objective with this response and keep as much of my personal opinion out of this, But here is mine:

I don't really like it but to make it easier to get support for my OS I put up with it, I daily drive arch and so must accept it. I could rip it out or run artix, I've gone down this path and got fed up with jumping hurdles to get what I wanted so went back to Arch and now I disable parts of it I don't need/want, have it generate text log files, use openresolv and other choices.

But all 5 points can be said for all other distros running a DE.

This isnt rice, it's that fine chopped pasta that can be used as rice!

😉

For convenience online there is always a trade off, When I do my update runs on windows each month this is one of my bookmarks. If I can't be arsed I use SDI origins.

Sorry, I've never had to sign in to anything to be able to download and install an nVidia driver. I've been using their cards for decades. No idea where/how you're getting them. Geforce experience is an optional add on if that is what you talk about.

I use arch too and dualboot with windows.

How are you updating drivers without sign in?

I have a local account in windows.

I see the AUR as suspicious until I establish a basic form of trust for what I want just like most .exe files and installers, I'd recommend you take this approach to the AUR too as it fundamentally is an obvious untrusted source.

Sorry but it just can't be boiled down to that sentence. I daily drive Linux and still disagree even though windows has obvious flaws.