On Mon, Jun 11, 2012 at 12:24 PM, solsTiCe d'Hiver <
solstice.dhi...@gmail.com> wrote:
> @rodrigo: +1 for .include but it does not work if one have to change an
> already defined directive.
>
Yes, that is unfortunate. But systemd is still a WIP, so maybe they will
eventually make up something for
@tom @rodrigo. Ok. Thank you to make it more clear for me.
And I thought the gpm arg declared in /etc/conf.d/gpm was needed. It is
not here. But others might need it. Hence the bug (feature request) not
opened by me.
Yes. The only needed part was the [Install] one
So, configuration will be handl
On Mon, Jun 11, 2012 at 10:59 AM, solsTiCe d'Hiver <
solstice.dhi...@gmail.com> wrote:
> For me, systemd service/unit file are just meant to be that, tailored to
> archlinux.
>
> I think that they talk about the lines
EnvironmentFile=/etc/conf.d/gpm
ExecStart=/usr/sbin/gpm $GPM_ARGS
The
On Mon, Jun 11, 2012 at 10:59 AM, solsTiCe d'Hiver
wrote:
> Systemd is made to boot/init a linux distro. But our distro here is archlinux
> and we are making archlinux package, right ?
> I understand we ship unpatched upstream package, but do we want to ship
> broken package so that they stay unto
hi.
So I was playing with an archlinux guest in vbox to learn a bit about
systemd.
And I found out that the gpm.service was broken. systemctl enable or
systemctl start does not work for gpm.service.
I looked for bugs and found FS#30053
https://bugs.archlinux.org/task/30053
I just copied and paste
5 matches
Mail list logo
