Re: [systemd-devel] Extending os-release
Sounds like a better fit for /etc/machine-info, as it's really not a distro thing. -- Mantas Mikulėnas graw...@gmail.com // sent from phone On Jul 7, 2014 10:41 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote: Hi I've noticed repeated problem through history where administrators seem to be struggling with clearly identify the server environment they are working in. Some try to come up with terminal colours associated with it, others use hostnaming scheme etc, so I was wondering if we could not solve that by introducing a new option to os-release called ENVIRONMENT which would be string that uniquely identifies the system environment in an three-tier server scheme as in Development, Staging, and Production ( or simply have it free for administrators own definition) as in ENVIRONMENT=Development ENVIRONMENT=Staging ENVIRONMENT=Production Thoughts? JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Extending os-release
Hi I've noticed repeated problem through history where administrators seem to be struggling with clearly identify the server environment they are working in. Some try to come up with terminal colours associated with it, others use hostnaming scheme etc, so I was wondering if we could not solve that by introducing a new option to os-release called ENVIRONMENT which would be string that uniquely identifies the system environment in an three-tier server scheme as in Development, Staging, and Production ( or simply have it free for administrators own definition) as in ENVIRONMENT=Development ENVIRONMENT=Staging ENVIRONMENT=Production Thoughts? JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Extending os-release
On 07/07/2014 08:38 PM, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Jul 07, 2014 at 08:02:19PM +, Jóhann B. Guðmundsson wrote: On 07/07/2014 08:00 PM, Tom Gundersen wrote: On Mon, Jul 7, 2014 at 9:44 PM, Mantas Mikulėnas graw...@gmail.com wrote: Sounds like a better fit for /etc/machine-info, as it's really not a distro thing. Yeah, this sort of info should probably not go in /etc/os-release (we are moving that to /usr/lib/os-release, which should make it clearer that this is really static info given by the distro, rather than config stuff for the admin). Right it's an better fit there and accommodates chassis= nicely as in...| CHASSIS=server Environment=Production s/Environment/ENVIRONMENT/ I'd like to see ANSI_COLOR in machine-info too. Maybe systemd (or something else) could generate one randomly when populating machine-info. Then a suitable shell prompt could use that. I had pinged Karel Zak on G+ since I had noticed he has been working on bringing consistency in terminal colorized output in the core/baseOS, with the idea and question if each environment could have an different terminal colour profile associated with it as in: ENVIRONMENT=Development could be associated with green terminal colour profile ENVIRONMENT=Staging could be associated with yellow terminal colour profile ENVIRONMENT=Production could be associated with red terminal colour profile No environment entry would just use the system defaults. So when an administrator logs into a server he would immediately know if he was operating on development server or an production server based on the terminal colour profile he was greeted with when he logged in. JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
