cruxbot has quit [Remote host closed the connection]
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
deltahotel has joined #crux
lavaball has quit [Remote host closed the connection]
deltahotel has quit [Quit: deltahotel]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
fr5dh has joined #crux
fr5dh has quit [Client Quit]
deltahotel has joined #crux
deltahotel has quit [Client Quit]
deltahotel has joined #crux
deltahotel has quit [Client Quit]
deltahotel has joined #crux
deltahotel has quit [Quit: deltahotel]
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
ppetrov^ has quit [Quit: Leaving]
ppetrov^ has joined #crux
<ppetrov^>
so, is CRUX 3.8 going to drop /usr/etc in favour of having just /etc
<ukky>
if it would be up to me, I would keep both.
<SiFuh>
If it would be up to me, /etc would be the only place to find the system configurations
<ppetrov^>
heh
<ppetrov^>
so, it's up to whom, then?
<ppetrov^>
i actually like to have both, so "secondary" stuff goes to /usr/etc, but then the Handbook should clearly state what goes one place or another. Or give some suggestions/examples and guidelines
<SiFuh>
CRUX dev team
<ukky>
Well-known system configuration files must be in /etc. Like /etc/resolv.conf. But package-specific files could/may/should be in /usr/etc/
<SiFuh>
OpenBSD moved everything into /etc
<ppetrov^>
ukky, yes that's how I see it, as well
<ppetrov^>
SiFuh, but OpenBSD also has /usr/local, while CRUX does not use that at all, right?
<SiFuh>
I understand ukky's point of view and I agree with it in a different prespective but all system wide configs should be in one place
<SiFuh>
OpenBSD got rid of /usr/etc and /usr/local/etc because it was just way to messy
<ppetrov^>
is /usr/etc found in other distros, too?
<SiFuh>
FreeBSD
<ppetrov^>
and Linux?
<ukky>
ppetrov^: Check section 5.6.2 of Handbook 3.7
<ppetrov^>
Void or sth?
<ppetrov^>
ukky, thanks i will
<SiFuh>
OpenBSD ports are installed to /usr/local but the etc is still /etc
<ppetrov^>
yes, actually it's already written there, so what I was asking was redundant
<ukky>
SiFuh is right, system-wide files must be in /etc
<SiFuh>
The question I'd like to ask is why is their a system wide config for a program that is not core?
<SiFuh>
their/there*
<SiFuh>
For example. Kismet has a local user config and a system wide config. Why bother with the system wide config?
<ppetrov^>
SiFuh, isn't it used as a config template/example or sth?
<farkuhar>
SiFuh: when did OpenBSD get rid of /usr/etc and /usr/local/etc? I haven't used it as a daily driver since 2019, so they must have made the change within the past 5 years.
<SiFuh>
So if you look deeper into the OpenBSD ports, most of the system wide configs are stripped as they are not needed
<SiFuh>
farkuhar: Before 2019
<farkuhar>
Huh, maybe I misremembered how the config files were laid out back then.
<SiFuh>
ppetrov^: OpenBSD has examples under /etc/examples but they are rarely used for ports
<SiFuh>
farkuhar: Maybe, because it was one of the things I hated about FreeBSD
<ppetrov^>
well, i wouldn't know. Never used any BSD
<SiFuh>
ppetrov^: The suggestion of ukky [Not exactly] is cool because OpenBSD follows it nicely. Core OS goes to /. OpenBSD programs go to /usr. Ports (contrib you could say?) goes into /usr/local/
<ppetrov^>
yep, i remember you telling me about their "contrib" ports going to /usr/local
<SiFuh>
The /etc thing though is a different topic altogether though even though it is similar
<ppetrov^>
so for you, an ideal CRUX would put contrib there, too? :P
<SiFuh>
Yes
<ppetrov^>
and repackaged bins to /opt
<SiFuh>
I want core in / and opt in /usr and contrib in /usr/local
<ppetrov^>
how about stuff that is not part of a package?
stoffepojken has joined #crux
<ppetrov^>
has this been discussed?
<SiFuh>
All system wide stuff to /etc but must be real system wide stuff not garbage programs.
<farkuhar>
These are the ports that put stuff into /usr/etc: i3 unixodbc at-spi2-core binutils pangox-compat lftp libreoffice mutt iptables a2ps nano libblockdev gtk chktex yapo mailx davfs2 ostree dar xorg lm_sensors mono gnome-keyring tslib enscript mc gimp lynx rust-bin slang spectrwm irssi openbox imagemagick
<SiFuh>
Yes and no, but not really. Dev's seem to avoid it because it means more work for the port maintainers and a possible rewrite of ports
<ppetrov^>
farkuhar, shouldn't yapo use /etc?
<ppetrov^>
i mean, it deals with ports
<ppetrov^>
not that it bothers me, really...
<SiFuh>
farkuhar: With the exception of gtk, xorg, lm_sensors (I don't know what is a yapo) the rest should NOT have a system wide configuration.
<ppetrov^>
SiFuh, yapo is a CLI for dealing with ports
<ppetrov^>
pretty nice, IMHO
<SiFuh>
Oh I think I might remember that
<farkuhar>
ppetrov^: don't ask me, yapo was jue's creation, he gets to decide where its config lives.
<SiFuh>
If yapo is to do with ports then it can have a system wide config
<ppetrov^>
farkuhar, true that
tilman has quit [Read error: error:0A00010B:SSL routines::wrong version number]
tilman has joined #crux
tarxvfz has joined #crux
<darfo>
when disks used to be ungodly expensive/small /etc was used to get the system booted enough to NFS mount /usr
<darfo>
then /usr/etc contained configs for shared software in /usr/bin and /usr/sbin
<darfo>
saved a lot of local disk space
<remiliascarlet>
I think putting configs in /usr/etc is a bad idea.
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
<remiliascarlet>
In FreeBSD and NetBSD they put configs of 3rd party programs under /usr/local/etc, which feels very retarded. Only OpenBSD (among the BSD's) puts them all under /etc.
stoffepojken has joined #crux
<darfo>
in the NFS scheme /usr/local/etc was to configure software differnently for one workstation
<darfo>
unpriveleged users could write /usr/local/? and install third-party software
<darfo>
if things broke first thing we told user was unmount /usr/local and see if problem disappeared :)
<SiFuh>
remiliascarlet: Not true
<SiFuh>
darfo: True
<SiFuh>
remiliascarlet: Untrue because OpenBSD ports creators basically stripped the right to use /etc altogether. Unless it is was an important system used application then /etc sure. Anything else got nothing but $HOME.
<remiliascarlet>
SiFuh: Weird, because everything I install under OpenBSD that has a system-wide configuration always tends to go to /etc.
<SiFuh>
Yes
<SiFuh>
But many ports no longer go there at all now.
<remiliascarlet>
I don't use the ports collection on OpenBSD, because I found that there's next to no difference in versioning from the binary packages anyway.
<SiFuh>
If they are not important to the system then /etc access is abolished
<SiFuh>
They are the same thing
<SiFuh>
Binary or ports are the same thing. One is compiled by you and one is not
<remiliascarlet>
I know.
<remiliascarlet>
And every BSD has both binaries and ports.
<remiliascarlet>
Meanwhile, Linux is either the one or the other, except for Gentoo since recently.