Re: Putting a file into system image ~user/ but not on reconfigure

[Hartmut Goebel <h.goebel@crazy-compilers.com>]

Hello Efraim,

Am 13.08.23 um 16:58 schrieb Efraim Flashner:
> I feel compelled to ask if the key must be in
> ~vagrant/.ssh/authorized_keys or if /etc/ssh/authorized_keys.d/vagrant
> is acceptable.

I'm afraid it needs to be in ~vagrant/.ssh/authorized_keys: When first 
booting the machine, Vagrant logs into it and replaces the key. Thus the 
user vagrant must be allowed to change the respective file.

Why are you asking? What would be easier (in respect of not 
re-installing the key), if putting the key into 
/etc/ssh/authorized_keys.d/vagrant would work?

> Also, could you use /etc/services or another file in /etc/static as a
> marker that the system has been booted at least once before?

Such a marker would be okay. Anyhow to make this work, some respective 
new service would need to detect this quite early, before /etc/service 
gets linked. Otherwise the service could not distinguish between "first" 
and "at least once"- Or did I misse something?

Is there some means of ordering service execution/start?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          |h.goebel@crazy-compilers.com                |
|www.crazy-compilers.com  | compilers which you thought are impossible |