Norm (ノーム) :CastoriceBlushing: (@norm)

@norm@shrimp.biribiri.dev

was kinda curious about where /etc/default came from, and it's basically a vestige of when distros used sysvinit for managing services

not sure why grub of all things decided to put their bootloader config in there too though

Norm (ノーム)

@norm@shrimp.biribiri.dev

On alpine linux, the only thing in /etc/default is the grub config lol

Debian and ubuntu has more stuff in there, though since the former does still technically support sysvinit that kinda checks out

Laru @laru@pleroma.laru.dsrv.x7q.eu

@norm /etc/default isnt even part of the standard (see refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf or man hier for a tldr version)

Norm (ノーム)

@norm@shrimp.biribiri.dev

@laru the really interesting thing is that some init systems like openrc actually do the opposite where defaults are in /etc/init.d, but customizations to those scripts are in a separate /etc/conf.d, which kinda makes more sense

(and then systemd has the whole thing with package defaults in /usr/lib/systemd and custom stuff in /etc/systemd instead)

[GRLC]

@novenary@akko.wtf

@norm @laru I agree with the way systemd does it, in fact a huge pet peeve of mine is software that puts mutable state in /etc instead of /var (which is equivalent to using ~/.config for general purpose data storage)

Norm (ノーム)

@norm@shrimp.biribiri.dev

@novenary @laru same here, kinda like having config separate from data if I can

[GRLC]

@novenary@akko.wtf

@norm @laru i mount /etc read-only :P

Wolf480pl @wolf480pl@mstdn.io

@norm
it's kinda like "end vars used by the config-generating template"

Norm (ノーム)

@norm@shrimp.biribiri.dev

@wolf480pl In a way I can see it as being the "default" values that result in what's in the real config file (/boot/grub/grub.cfg or similar) but often times it's /etc/default/grub that's configured by the admin and grub.cfg itself is often advised to not mess with.