On 04/01, Jóhann B. Guðmundsson wrote:
> That makes no sense that an boot is not market completed until it manage
> to contact it's update servers but inline with other hacks coreOS is
> doing in relation with systemd.
To what hacks, exactly, are you referring?
-Alex
signature.asc
On 04/01, Tobias Hunger wrote:
> IIRC both coreos and chormeOS only mark a boot as successful after
> talking to their respective update servers. The assumption apparently
> is that the OS can fix itself when it is able to communicate properly
> with its own update server.
This isn't quite right.
On 12/23, Lennart Poettering wrote:
> On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
> > What usescases do you see for it's existence.
>
> Well, the usecase that this is what's out there right now, and we have
> to stay compatible. It's not precisely an exotic feature,
On 12/23, Jóhann B. Guðmundsson wrote:
> The usual underlying cause of usage of Environment or EnvironmentFile in
> type units is more or less always due to the fact that the
> daemon/service cannot read configuration file on startup thus the answer
> is you would use a daemon that was written
I don't mean to be pedantic, but I think any would be a better choice.
-Alex
On Mon, Jul 14, 2014 at 1:54 AM, Tom Gundersen t...@jklm.no wrote:
On Mon, Jul 7, 2014 at 10:56 AM, Colin Guthrie gm...@colin.guthr.ie
wrote:
'Twas brillig, and Tom Gundersen at 06/07/14 23:32 did gyre and gimble:
