Re: goal: booting with an empty /etc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday, December 8, 2023 11:57:55 AM EST Adam Williamson wrote:
> On Fri, 2023-12-08 at 11:49 -0500, Steve Grubb wrote:
> > On Friday, December 8, 2023 11:23:29 AM EST Zbigniew Jędrzejewski-Szmek 
> > wrote:
> > 
> > > But yeah, there'll always be a few "special" files. But that's fine,
> > > we have mechanisms to handle those. For the other 99%, we should
> > > move them out of /etc.
> > 
> > 
> > The problem is that there would need to be a standard that all upstream 
> > authors agree on. There are some like systemd which have a [SECTION_NAME]
> > 
 followed by config items. Others do not make sections. What if the
> > config is in yaml, json, or XML? How can you see the end result? We
> > would need to have a standard library that everyone can use. From that,
> > we need a utility to compile the actual configuration that would be
> > consumed by the service so we can inspect it during troubleshooting.
> 
> Eh? What does the format of the files have to do with where they live?

At face value, it shouldn't matter. But when you have the first override, now 
you need to have a reproducible, correct assembly of the configuration. Each 
format has peculiarities about how to place the override in the correct spot.
 
> I don't see any reason we can have heterodox config file formats in
> /etc, but not in /usr. (Indeed, practically speaking, we already have
> lots of different formats in both places).

Because it's in one place and not expected to be built up by looking all over 
the place for the pieces. Making this easy for security scanner and upstream 
developer adoption really needs to be considered. Don't misunderstand that 
I'm against the idea...I'm just trying to say we need to consider the 
ramifications across the broader ecosystem.

-Steve

--
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux