Hi Efraim,
hanks for sharing your thoughts. Meanwhile I learned two things:
* vagrant needs adjustment to detect and support Guix, which is
intended by vagrant and vagrant is extensible for this case, see
https://github.com/hashicorp/vagrant/tree/main/plugins/guests
* just replacing the
On Thu, Aug 17, 2023 at 09:30:24PM +0200, Hartmut Goebel wrote:
> 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
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
On Thu, Aug 10, 2023 at 02:38:24PM +0200, Hartmut Goebel wrote:
> Am 10.08.23 um 14:12 schrieb wolf:
> >
> > I guess you could have a script that would use the existence of the key
> > itself
> > as a marker. In that case you would likely want to recreate it if the
> > marker
> > (key) got
Am 10.08.23 um 14:12 schrieb wolf:
I guess you could have a script that would use the existence of the key itself
as a marker. In that case you would likely want to recreate it if the marker
(key) got deleted,
No! The key must not be recreated. The key is expected to be replaced by
a new
On 2023-08-10 00:11:55 +0200, Hartmut Goebel wrote:
>Hi,
>
>sorry for the hard to understand subject.
>
>I need to put a file into a system image (into ~user) which will not be
>recreated or touched when running "system reconfigure" later, even if
>not existent. So this is
