On 12/9/23 16:55, DJ Delorie wrote:
Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> writes:
I'm not entirely sure if you're just doing Friday trolling or if
you're serious.
Serious. I have many machines and VMs, and every time I do a Fedora
install, I have a list of your choices I have to revert because they
don't work for me. It's tiring.
I fear this will end like the /tmp fiasco where one /tmp became many tmp
directories, and no consistent rule about which one to use.
/tmp is generally backed by RAM and does not survive a reboot.
Not on any of my machines. I want tmp files around after a reboot so I
can figure out what caused the reboot.
This can be achieved without "empty /etc" as a goal. For example, why
can't we use podman's overlay filesystem to mount /usr/etc under /etc so
that all the configuration appears in /etc but installed vs changed
files are kept segregatable?
(FTR, not "podman's". The filesystem is a kernel thing.)
If the goal was to just move everything wholesale, that'd be a
I meant, rpms install into the lower fs, and the user edits the upper
fs. You can "revert" to "factory settings" by wiping just the upper fs.
You can expose the two layers elsewhere (like /usr/etc) if that helps
with the merging.
(Another problem is that this scheme only works "live". If you want
to look *into* an image from the outside, the overlay wouldn't be
assembled, so the tools need to know how to handle the config split
manually.)
If you get your way, /etc would be empty anyway ;-)
For example, /etc/services is a list of port:service mappings, and people
maybe used to edit that twenty years ago,
I still edit this one.
Great for you. So you can be the one person who uses the override
mechanism for this file.
That you assume I'm the only one is part of the problem.
Another common case is "empty" configuration files, i.e. templates
that show the default configuration.
I find these VERY helpful when trying to fix configuration issues on my
machines.
Right. I'm not saying that those should go away. Quite the opposite.
If you move them away from where I expect to find them, effectively
they've gone away. Instead of having everything I need in the one spot,
I have to go hunting for it. If history is right, everyone will choose
a different spot and finding info will become very difficult. Even
*documenting* where to find this information will become difficult,
because everyone puts their docs in different places.
Please figure out a way to make upgrades more reliable without having to
retrain millions of Linux users or turn Fedora into Windows. I'm not
sure I'm exaggerating here.
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
ostree does something like this. Having a lower /usr/etc and a upper
/var/etc mapped at /etc, would be interesting. although there would be
no ability to merge, the upper overrides the lower.
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
