• More findings..

    From Nicholas Boel@1:154/10 to Andrew Leary on Fri Jan 20 08:31:02 2017
    Hello Andrew,

    For the time being, you may want to comment out any and all Arch Linux and Manjaro related stuff in installinit.sh until proper systemd scripts are created for them.

    After reporting to you that the search for Manjaro also needed to be done in installinit.sh, I realized there are no init scripts to be installed, and since
    both Manjaro and Arch Linux are systemd based now (as well as others, I'm sure), the current state of both in MBSE are not going to install proper startup scripts.

    installinit.sh includes:

    cp init.Arch $DISTINIT

    but there is no init.Arch in the script directory, so this will not work. Just as well, I'm not even sure Arch Linux supports sysvinit any more unless you go out of your way to make it do so.

    So at the moment, you could probably just comment out (or remove) the complete "# Adding scripts for Arch Linux" section in installinit.sh, and everything should still work as expected. Both Arch Linux and Manjaro will still be labeled and installed properly, just without any kind of startup script or service file installed at the moment.

    I began working on a little something, but need more time. Until then, the above should be okay - and on both Arch Linux and Manjaro mbtask will need to be run manually by the MBSE admin user. When I get something working as far as systemd goes, I'll let you know.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Andrew Leary@1:320/219 to Nicholas Boel on Fri Jan 20 18:34:13 2017
    Hello Nicholas!

    20 Jan 17 08:31, you wrote to me:

    For the time being, you may want to comment out any and all Arch Linux
    and Manjaro related stuff in installinit.sh until proper systemd
    scripts are created for them.

    Noted.

    After reporting to you that the search for Manjaro also needed to be
    done in installinit.sh, I realized there are no init scripts to be installed, and since both Manjaro and Arch Linux are systemd based now
    (as well as others, I'm sure), the current state of both in MBSE are
    not going to install proper startup scripts.

    installinit.sh includes:

    cp init.Arch $DISTINIT

    but there is no init.Arch in the script directory, so this will not
    work. Just as well, I'm not even sure Arch Linux supports sysvinit any more unless you go out of your way to make it do so.

    So at the moment, you could probably just comment out (or remove) the complete "# Adding scripts for Arch Linux" section in installinit.sh,
    and everything should still work as expected. Both Arch Linux and
    Manjaro will still be labeled and installed properly, just without any 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.

    I began working on a little something, but need more time. Until then,
    the above should be okay - and on both Arch Linux and Manjaro mbtask
    will need to be run manually by the MBSE admin user. When I get
    something working as far as systemd goes, I'll let you know.

    Keep in touch here or via netmail.

    Andrew

    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Nicholas Boel@1:154/10 to Andrew Leary on Sat Jan 21 07:57:26 2017
    Hello Andrew,

    On Fri Jan 20 2017 18:34:12, Andrew Leary wrote to Nicholas Boel:

    I need to setup a machine with Arch Linux so I can figure out what is needed in the systemd way of doing things.

    It's not that big a deal. Just a simple .service file is usually required, although the one I started yesterday failed possibly due to the fact that the MBSE admin user needs to start it, and not root (which I think is default for systemd service files). So I'll just have to look into starting it as a user or
    even passing it off to the user once it's started.

    I began working on a little something, but need more time. Until
    then, the above should be okay - and on both Arch Linux and
    Manjaro mbtask will need to be run manually by the MBSE admin
    user. When I get something working as far as systemd goes, I'll
    let you know.

    Keep in touch here or via netmail.

    Will do.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Jan 21 16:51:14 2017
    Hi,

    On 2017-01-21 07:57:26, Nicholas Boel wrote to Andrew Leary:
    about: "More findings..":

    It's not that big a deal. Just a simple .service file is usually
    required, although the one I started yesterday failed possibly due to
    the fact that the MBSE admin user needs to start it, and not root
    (which I think is default for systemd service files). So I'll just
    have to look into starting it as a user or even passing it off to the
    user once it's started.

    You can specify the user and group in the .service file:

    User=, Group=
    Sets the Unix user or group that the processes are executed as, respectively. Takes a single user or group name or ID as argument. If no group is set, the default group of the user is chosen.


    Bye, Wilfred.


    --- FMail-W32 1.73.12.67-B20170120
    * Origin: Native IPv6 connectable node (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sat Jan 21 16:38:02 2017
    Hello Wilfred,

    On Sat Jan 21 2017 16:51:14, Wilfred van Velzen wrote to Nicholas Boel:

    It's not that big a deal. Just a simple .service file is usually
    required, although the one I started yesterday failed possibly
    due to the fact that the MBSE admin user needs to start it, and
    not root (which I think is default for systemd service files). So
    I'll just have to look into starting it as a user or even passing
    it off to the user once it's started.

    You can specify the user and group in the .service file:

    User=, Group=
    Sets the Unix user or group that the processes are executed as, respectively. Takes a single user or group name or ID as argument. If
    no group is set, the default group of the user is chosen.

    I was trying to come up with one quickly at the time of the original writing. I
    got caught in a snag and stopped before I decided to divulge faulty and/or rushed information without testing, so it would actually be an asset to the software rather than anything else.

    When I get a little free time I'll give it another go with a little more patience, rather than trying to whip one up on the spot.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)