The conversation

Lessons learnedExperience excerpt · English

The problem is Linux is, as he puts it, hard to learn and hard to master

The problem is Linux is, as he puts it, hard to learn and hard to master. So once I've gone through the learning phase for fun and learned what to do, I really want to just keep using it and not have all my hard work undone at a whim. Perhaps ironically systemd is one case I would point to as being an acceptable breakage. The software itself definitely fulfils the license's promise of "NOT FIT FOR ANY PURPOSE", but as an idea it's mostly sound. It suffers from bad design in that e.g. it has no concept of "ready state" so there is no way to express "The VPN service needs the network to be online" and "The NFS mount needs the VPN to be connected"; thus it also has no way to express "you must wait for the NFS to be cleanly unmounted before stopping the VPN" - only "you must execute umount before tearing down the VPN (but without waiting)". Similarly if you have a bind mount you can't make it wait for the target to be mounted before the bind mount is executed (i.e. …

Original discussionI spent 18 years in the Linux console143 source comments · at import
2

What was this responding to?

Parent context · original excerpt

VK

While I have been using Linux since 1996 or so, and do have quite an opinionated workflow, I never could agree with this kind of ultraconservative approach to things. History never stops. Things change. Linux changes. Not every day, not every month, but every couple of years something has to go. And that's ok.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

05

> Similarly if you have a bind mount you can't make it wait for the target to be mounted before the bind mount is executed Have you tried RequiresMountsFor/WantsMountsFor ? You'd have to create a new unit that just does the bind mount though..

Full original
FN

On macOS I have a compatibility layer for Linux ip (since I've grown to use it, and besides the BSD ifconfig and route (and friends) has always been different from Linux. But when I am on OPNsense, the only other BSD I use, I don't have such, sadly. With regards to Windows I use ways from NT era, Windows Vista/7, and Windows 10 to configure Windows, and I bet they added stuff in 11, too. It is a mess, supposedly by a company which makes a super user friendly UI (/s) NFS is a very simple yet archaic filesystem, with nice throughput, but it comes from a LAN era where LAN clients were trusted. I don't know if it got modernized but I just use SSH over FUSE or CIFS over Wireguard.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.