Hacker News Reader

I'm with you. HN pedants are so god damn annoying.

crazy_hombreon Running systemd without systemd-journald

An ethernet interface is not a netdev. Netdevs are always virtual interfaces.

crazy_hombreon Pwnkit: Local Privilege Escalation in polkit's pkexec (CVE-2021-4034)

Oh no, an application has bugs. Must get rid of it!

crazy_hombreon We're migrating many of our servers from Linux to FreeBSD

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 the same thing that init scripts do except in a much more concise and efficient manner. And as I said before, there's a ton of systemd service unit files on any Linux system that you can take a look at and use as inspiration for your own services. Taking a little time to learn the ways of systemd is not a huge burdensome task like you're making it seem to be. I don't see why you think everyone should conflate systemd with complexity.

And about the voluminous documentation, well man pages are supposed to be comprehensive and cover every single aspect of the tools being described. They're not there to just be an intro to systemd for new users and administrators. If you want something like that, look no further than the "systemd for Administrators" series of articles written by the systemd author himself. https://github.com/shibumi/systemd-for-administrators/blob/m....

crazy_hombreon We're migrating many of our servers from Linux to FreeBSD

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.

crazy_hombreon We're migrating many of our servers from Linux to FreeBSD

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 harp about their handbook..) And besides, there are already hundreds of systemd unit files on your system that you can easily copy and make relevant changes for your own services. Not having to deal with finicky shell features is a major advantage IMO.

crazy_hombreon We're migrating many of our servers from Linux to FreeBSD

ifconfig/netstat was deprecated more than a decade ago, that's more than a couple years don't you think?

crazy_hombreon We're migrating many of our servers from Linux to FreeBSD

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.

crazy_hombreon Systemd, 10 years later (2020)

There's no such thing as systemd-firewalld.

crazy_hombreon Behind the design of the fresh new Firefox coming June 1

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.

crazy_hombreon Migrate Everything from Linux to BSD

FreeBSD 13 is moving the i386 architecture to tier 2 status, so looks like the days of 32-bit support in FreeBSD might be numbered as well: https://lists.freebsd.org/pipermail/freebsd-announce/2021-Ja...

crazy_hombreon Wifi Dabba (YC W17) – Own a Piece of the Internet in India

That is a super mediocre website you got there. Not a great first impression.

crazy_hombreon Identifying Airtel middleboxes that censor HTTPS traffic

That's weird. I just get a 301 redirect to the HTTPS version when I visit http://duckduckgo.com.

crazy_hombreon Kubernetes YAML Generator

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).

crazy_hombreon Understanding Daemons

> 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 networking manager. You can easily replace timer units with cron. You can easily forward log messages to a syslog daemon. You can easily replace systemd-boot with grub or any other boot manager.

It should be pretty obvious how baseless the monolithic arguments against systemd are.

crazy_hombreon Understanding Daemons

> 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 syslog daemon).

crazy_hombreon Good Logging

> 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 messages from the journal. You can add custom fields to your log messages. You can even get the logs in JSON format to parse log message from any scripts. And you can even use the cursor feature of journalctl to keep reading the logs at regular intervals without having to keep a constantly running process and tail the logs.

I can understand people not liking systemd-journald on account of the binary logs, but I definitely don't understand calling journalctl the worst log viewing app.

crazy_hombreon FreeBSD 11.4

Well if it's working for everyone but a select few, then I'd argue the problem is with those select few and not the product.

crazy_hombreon FreeBSD 11.4

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 working on it.

Also, me and hundreds of other people have been booting off of ZFS on Linux for years. Your issue is most likely in your distro's initramfs setup or you must have botched the initramfs config yourself. If you're just used to FreeBSD, just stick to commenting about FreeBSD without maligning other operating systems.

crazy_hombreon Systemd, ten years later: a historical and technical retrospective

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 people don't get this.

crazy_hombreon Systemd, ten years later: a historical and technical retrospective

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 and doesn't go in a distro. They don't have to keep maintaining long init scripts for the hundreds of packages that they are responsible for. Unit files are so much easier to deal with.

crazy_hombreon Getting Started with WireGuard

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 since Linux 4.18: https://wiki.nftables.org/wiki-nftables/index.php/Performing...

crazy_hombreon Systemd Home Directories

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.