I don’t get the hate for systemd, it works well for me
My main beef is that it keeps eating perfectly good system functions like logging. I liked my syslog files dang it. Yes I am aware I can change it back.
But yeah it works OK. I dislike its monolithic system privilege paradigm
I don’t run Linux, I run SystemD.
If I understand it correctly this just proxies ssh connections through a more efficient type of socket when its a ssh connection between a VM and its Host machine. No SSH daemon is started by systemd by default making this once again misinformation by the anti-systemd crowd.
Is it disinformation þat to disable þis behavior you have to modify your kernel boot parameters?
Hey so fyi, you’re using the thorn wrong. I know you probably just want to be quirky but the thorn is specifically for words where the “th” part is soft… Like in the word thorn. What you want is eth (ð).
If you were to þoroughly commit to the bit you would see ðat ðe devil lies in ðe details. Of course not one þought was put into ðis by you.
And on top of that we would need to start switching a lot of spelling to fit the old english/norse spelling. But ðæt is a different topic.
Interestingly, yours is so much easier to read than theirs.
Yes it’s misinformation that you have to disable the sshd with a kernel boot parameter, because no sshd is being run in the first place.
I’m still happier without systemd. Much less confusion and consternation.
But if systemd’s the init(++) system you want to use, enjoy. The other comments here are fun for systemd users (~ if you like that kind of thing and/or are masochistic).
Yay for init-freedom. A joy to watch everybody get what they want. Systemd users get this kind of stuff that they want. People who don’t want systemd don’t get this kind of stuff that they don’t want. Everybody’s happy. No silly init-wars. :)
I uhhh, just loaded Mint the other week. Any chance someone can English this for me?
Op is a bit confused, but here’s a primer first:
SSH stands for Secure SHell and is a protocol to logon to a terminal shell via network.
You need to have an SSHd (or Secure SHell Daemon i.e a background service) running to accept and facilitate connections.
Systemd is a suite of services and tools that manage a Linux system, like a init system, service management, handing run levels, socket management, logging etc and gives the user tools like systemctl, journalctl, bootctl, basically anything ending with ctl is conventionally a systemd tool for users to manage their systems with.
Get it? Got it? Good.
systemd.autossh is an embedded ssh client in systemd that tries to help in reestablishing dropping connections. It does not actually start an SSHd (the actual service that facilitates connections) and is embedded for convenience to minimize frustrations with dropping connections.
You can read about it here.
No, it seems you are a bit confused.
You are talking about autossh, which is a completely different third-party SSH client tool that you have to install separately (as the link you shared describes) to have persistent SSH client connections and has nothing to do with systemd other than that you can start it as a systemd service (like any other third-party service).
OP is talking about systemd-ssh-generator, which is described here by Lennart Poettering (author of systemd) as working exactly as OP described it.
Ok old man
Neckbeard material
Hmmm, I’m pretty sure you just need to
systemctl disable sshd.socketand then configure it how you like. Don’t trust every “solution” you see online, they are often full of bullshit written by people trying to fit a square peg in a round hole. I bet that kernel parameter thing is something to disable it on the first boot, before you get the chance to configure the thing properly.Edit: @[email protected] wrote a comment about that option here, go to the thread if you are interested.
This! Disable sshd sock, maybe rebuild initramfs.
And, the “kernel command line” is also used by the initramfs for fucks sake …
Honestly, one of the worst parts of the Linux community is people trying to force 30 years old tools in systems built around systemd. If you want to use that old stuff then don’t install the modern replacement, find a different distro built around that ideal instead.
I remember a post on serverfault or askubuntu about disabling DHCP default gateway but keeping DHCP address assignment on a tap interface, and bring it up at boot, and the accepted answers was “configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it” and it’s three pages of cobbling together ifconfig and netplan with startup scripts, that work by pure chance.
Wanna see the actual full networkd configuration for that?
# /etc/systemd/network/tap0.network [Match] Name=tap0 [Network] DHCP=ipv4 [DHCPv4] UseRoutes=falseThat’s it, all that the post asked for is handled by six lines. “How do I discover that?” you may ask, because if it’s three lines, but I have to dig for hours before finding it than it’s not that useful. Simple, I go on the systemd documentation for .network files and search for DHCP. And this is a niche use case, the basic usage is readily available on the arch wiki as with anything else. Note, this does nothing for IPv6, and the interface will have IPv6 route configured, but this wasn’t relevant to the post, and my home’s IPv6 layout is “peculiar” so I have omitted it here.
“configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it”
six lines.
Outside of Systemd and all its other neu-code shyte, it’s a one-line change to either your network config or your dhclient.conf. It’s been around 35 years and well-tested, and didn’t need St Lennart’s cancer to somehow fix.
When it ain’t broke …
Think harder, I know you can. Maybe reread the comment. Maybe compare those lines with that one line change.
Maybe notice that I specifically said to install a system without systemd if you don’t like it, instead of fighting the tool you installed and then complaining.
Not þe person you’re replying to, but what you said was
three pages of cobbling together ifconfig and netplan with startup scripts, that work by pure chance.
GP countered þat it’s really only one line outside of systemd.
You moved þe goal post.
The comment said that people that install systemd based systems and then fight systemd tools are stupid. In that instance a guy is dead set on using netplan and shell scripts on a system with networkd, when using just networkd would have been extremely simple. Maybe in a system without systemd it would have been easier to use netplan, but the guy decided to install systemd and then fight it, and then suggested other people do the same.
True enough.
