Subj : More findings..
To : Nicholas Boel
From : Andrew Leary
Date : Fri Jan 20 2017 06:34 pm
Hello Nicholas!
20 Jan 17 08:31, you wrote to me:
NB> For the time being, you may want to comment out any and all Arch Linux
NB> and Manjaro related stuff in installinit.sh until proper systemd
NB> scripts are created for them.
Noted.
NB> After reporting to you that the search for Manjaro also needed to be
NB> done in installinit.sh, I realized there are no init scripts to be
NB> installed, and since both Manjaro and Arch Linux are systemd based now
NB> (as well as others, I'm sure), the current state of both in MBSE are
NB> not going to install proper startup scripts.
NB> installinit.sh includes:
NB> cp init.Arch $DISTINIT
NB> but there is no init.Arch in the script directory, so this will not
NB> work. Just as well, I'm not even sure Arch Linux supports sysvinit any
NB> more unless you go out of your way to make it do so.
NB> So at the moment, you could probably just comment out (or remove) the
NB> complete "# Adding scripts for Arch Linux" section in installinit.sh,
NB> and everything should still work as expected. Both Arch Linux and
NB> Manjaro will still be labeled and installed properly, just without any
NB> kind of startup script or service file installed at the moment.
I need to setup a machine with Arch Linux so I can figure out what is needed
in the systemd way of doing things.
NB> I began working on a little something, but need more time. Until then,
NB> the above should be okay - and on both Arch Linux and Manjaro mbtask
NB> will need to be run manually by the MBSE admin user. When I get
NB> something working as far as systemd goes, I'll let you know.
