I still don’t get what you guys have against Windows. Bill Gates has done so much good for the world.
(My body is ready.)
Bill Gates actually was pretty cool, it’s windows after Bill Gates that’s terrible. I can’t say there was anything Bill Gates did that I didn’t like, he was like the Gabe Newell of operating systems before steamdeck.
Put your phone on vibrate, etc…
I don’t mind all the ads, they’re always for things I was just thinking I needed to buy anyway.
Wow there, easy, you’re gonna end up on ER.
At the very least take a smal phone.
Razzzzz
I’m still waiting for them to get DNS and user services working. Then it’ll finally be usable.
DNS
There’s
systemd-resolved. I don’t know if you mean that it has some kind of limitation.It doesn’t work with private DNS servers or forward DNS over VPN. Removing it is always the first thing I have to do with new Linux installs.
It doesn’t work with private DNS servers or forward DNS over VPN.
Like, you want to have it query some particular DNS server?
From
man 5 resolved.conf:DNS= A space-separated list of IPv4 and IPv6 addresses to use as system DNS servers. For compatibility reasons, if this setting is not specified, the DNS servers listed in /etc/resolv.conf are used instead, if that file exists and any servers are configured in it.If you specify your private server there, it should work. For VPN, I mean, whatever VPN software you’re using will need to plonk it in there. Maybe yours is not aware of systemd-resolved, is modifying
/etc/resolv.confaftersystemd-resolvedhas already started, and it doesn’t watch it for updates?In my /etc/nsswitch.conf, I have:
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dnsI’m assuming that the “resolve” entry is for
systemd-resolved.kagis
https://www.procustodibus.com/blog/2022/03/wireguard-dns-config-for-systemd/
With systemd-resolved, however, instead of using that DNS setting, add the following PostUp command to the [Interface] section of your WireGuard config file:
PostUp = resolvectl dns %i 9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net; resolvectl domain %i ~.When you start your WireGuard interface up, this command will direct systemd-resolved to use the DNS server at 9.9.9.9 (or at 149.112.112.112, if 9.9.9.9 is not available) to resolve queries for any domain name.
Bzzzzz
Well, that’s one way to “use” systemd, I guess.
I dislike systemd less than I dislike sysvinit, so it has that going for it.
yesss
This not a kill tony joke?
No, kill Tony just sticks his thumb up his butt for Joe Rogan. Nothing to do with Linux.
The other day I wrote I like snaps and shot more rope than Spiderman.
Flatpak is amazing especially with storage being so cheap these days.
OK, Satan.
I still remember the bad old days of stale repositories and compiling from scratch. Never again.
There was 25 years between
c;m;miand lennart’s cancer, filled with excellent choices better than either.
Just replying to keep the vibes going.
I just had an issue with the vscodium flatpak, been using it for two months with no issue in an online course, got to learning GUIs, import module, doesn’t exist. I couldn’t figure out why it wasn’t there, installed three different python versions of it three different ways, still nothing. Couldn’t even get vscodium to point to a different interpreter that I knew was there (yet it doesn’t say it’s not there, just that some things won’t work). Still nothing. Three hours later, after trying everything I could think of, I realized that it was because I installed the flatpak version when it clicked that it worked in Geany and I didn’t have python 3.13 in my repos, yet that was the only one I could see in vscodium.
That sounds like user error.
Vscodium isn’t in the repos for opensuse, but yes, this user should have found a way to install it on bare metal in the first place.
Have you tried butterflies?
From a broad enough perspective, everything is user error
Good boy.
My biggest complaint with systemd…
Service xxx stop/start/restart is so much easier than
Systemctl stop/start/restart xxx
It fucking annoys me
I mean, you could write a shell function or script to just wrap it if it bothered you that much?
I’d rather complain
alias service="systemctl"Or even
alias s="systemctl"Note the order of the commands. I don’t mind typing aystemctl
service() { systemctl $2 $1 }
I love you all solutioning for something I don’t care enough about. I just find it annoying that systemctl reversed the order for some stupid reason.
Understandable, have a nice day
It seems like every Linux distro I’ve used both of those will work fine.
I neaver bothered me too much, can you not alias stop to sudo sytemctl stop xxx
Like that you can write “stop wpa_supplicant” instead od “Sudo systemctl stop wpa_supplicant. “
Systemd has simplified my life on a few occasions, and it seems to be reliable from what I can tell. At the end of the day if I can get the OS to do what I want in a relatively simple matter, that’s all I care about.
In all seriousness, I’ve yet to encounter a situation where Systemd made any meaningful negative difference in my Linux experience.
I’ve never had problems with any init system, Systemd or otherwise.
may i ask you to kindly provide the source of this image?
frenky_hw, here’s the specific image: twitter (hopefully it is, twitter doesn’t work for me rn)
twitter doesn’t work for me rn)
https://nitter.space/moschino_bunny/status/1457773412957376530
Tal out here giving solutions
An admirable example of working harder, not smarter
tysm❤️
Please tell me your phone has a flared base?
it’s fine
they’re fine
we’re fine
it’s fine
