I'm with you. HN pedants are so god damn annoying.
An ethernet interface is not a netdev. Netdevs are always virtual interfaces.
Oh no, an application has bugs. Must get rid of it!
I genuinely don't see what's so complex about a service unit file. It's a simple INI file that has multiple sections that describes the service, tells what command to run and specifies any dependencies. It's literally…
If you need extra customization capabilities, just run a shell script via the ExecStart= parameter and boom, you have all the power of systemd and the shell combined.
Now you're just exaggerating. Are you really saying spending 5-10 mins skimming through a couple of man pages is that hard? Are you saying that a lot of documentation is a bad thing? (I thought FreeBSD fans liked to…
ifconfig/netstat was deprecated more than a decade ago, that's more than a couple years don't you think?
systemd unit files are text files, not binary blobs. And it is much easier to grok a unit file than a 500 line init script.
There's no such thing as systemd-firewalld.
I've been using Firefox on Wayland for the past year or so. There are still some minor hitches here and there, but it's very usable right now.
Isn't YAML supposed to be a superset of JSON? So technically, you should be able to use JSON files right now (barring a few exceptions).
> AFAIK it's not easy to replace various parts of systemd, it's very monolithic and it does too many things. You can easily replace timesyncd with any NTP daemon. You can easily replace networkd with any other…
> I like the init part, i could do without everything else. Then, do exactly that? None of the components you're complaining about are mandatory (except for journald, but you can easily forward log messages to a regular…
> The viewer journalctl is probably the worst log viewing app that exists Completely disagree there. I've had quite a pleasant experience with journalctl. It has sane arguments and you can easily grep any relevant log…
Stop spreading FUD. ".zfs/snapshot" has been working on Linux for years now. I don't know when you last used ZFS on Linux, but just because you haven't used ZoL for a while doesn't mean that the developers stopeed…
systemd isn't just an init system. It's a suite of tools that provides a system and service manager. It's not handling everything in one monolithic process. This has been said thousands of times before. I don't know why…
systemd did make package maintainer's lives a lot easier. We don't often see the shift to systemd from their perspective. They are the ones making the distros so I think they are the ones who really get to say what goes…
So unfortunately it makes less sense for one-liners. Case in point: to use the masquerade action in a postrouting/nat chain, you also have to register a (possibly empty) prerouting/nat chain. You don't have to do that…
You know you don't HAVE to use systemd-homed right? If it doesn't fit your use case, just keep doing what you're doing right now.
I'm with you. HN pedants are so god damn annoying.
An ethernet interface is not a netdev. Netdevs are always virtual interfaces.
Oh no, an application has bugs. Must get rid of it!
I genuinely don't see what's so complex about a service unit file. It's a simple INI file that has multiple sections that describes the service, tells what command to run and specifies any dependencies. It's literally…
If you need extra customization capabilities, just run a shell script via the ExecStart= parameter and boom, you have all the power of systemd and the shell combined.
Now you're just exaggerating. Are you really saying spending 5-10 mins skimming through a couple of man pages is that hard? Are you saying that a lot of documentation is a bad thing? (I thought FreeBSD fans liked to…
ifconfig/netstat was deprecated more than a decade ago, that's more than a couple years don't you think?
systemd unit files are text files, not binary blobs. And it is much easier to grok a unit file than a 500 line init script.
There's no such thing as systemd-firewalld.
I've been using Firefox on Wayland for the past year or so. There are still some minor hitches here and there, but it's very usable right now.
Isn't YAML supposed to be a superset of JSON? So technically, you should be able to use JSON files right now (barring a few exceptions).
> AFAIK it's not easy to replace various parts of systemd, it's very monolithic and it does too many things. You can easily replace timesyncd with any NTP daemon. You can easily replace networkd with any other…
> I like the init part, i could do without everything else. Then, do exactly that? None of the components you're complaining about are mandatory (except for journald, but you can easily forward log messages to a regular…
> The viewer journalctl is probably the worst log viewing app that exists Completely disagree there. I've had quite a pleasant experience with journalctl. It has sane arguments and you can easily grep any relevant log…
Stop spreading FUD. ".zfs/snapshot" has been working on Linux for years now. I don't know when you last used ZFS on Linux, but just because you haven't used ZoL for a while doesn't mean that the developers stopeed…
systemd isn't just an init system. It's a suite of tools that provides a system and service manager. It's not handling everything in one monolithic process. This has been said thousands of times before. I don't know why…
systemd did make package maintainer's lives a lot easier. We don't often see the shift to systemd from their perspective. They are the ones making the distros so I think they are the ones who really get to say what goes…
So unfortunately it makes less sense for one-liners. Case in point: to use the masquerade action in a postrouting/nat chain, you also have to register a (possibly empty) prerouting/nat chain. You don't have to do that…
You know you don't HAVE to use systemd-homed right? If it doesn't fit your use case, just keep doing what you're doing right now.