On Wed, Jun 05, Neal Gompa wrote:
> I agree about /usr/lib. Moreover, I think /usr/lib has been misused
> quite a lot for configuration files lately. The idea of a
> /usr/sysconfig makes a lot more sense to me. For the first time in a
> while, we're getting a descriptive name for it, and it's easily
> If I could wave a wand, I'd move all of the stuff we'd been putting in
> /usr/lib into /usr/sysconfig. :)
I started a discussion about the directory name on the fhs mailing list:
Please help and comment there, too, so that this discussion will not
end again with "use something below /usr/lib or /usr/share" and no
agreement on one directory.
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
According to the link https://coreos.com/ignition/docs/latest/boot-process.html, ignition only takes effect at the first boot.
But we want to make it effect later if we missed something in the first boot, or we want to debug ignition.
So question is: how can I set file coreos/first_boot in the EFI System Partition, or set 'coreos.first_boot=detected' in kernel parameter line in an existing
coreos qcow2 image which can be started, so that I can make ignition work?
Thanks a lot!