On Tue, Feb 12, 2013 at 4:49 AM, Jan Engelhardt wrote:
>
> On Monday 2012-11-26 15:49, Kay Sievers wrote:
>>>
>>> I guess that answers the "binaries" bit, but probably doesn't answer why
>>> system units are in /usr/lib/systemd/system/ rather than, say,
>>> /usr/share/systemd/systemd. I think that
On Monday 2012-11-26 15:49, Kay Sievers wrote:
>>
>> I guess that answers the "binaries" bit, but probably doesn't answer why
>> system units are in /usr/lib/systemd/system/ rather than, say,
>> /usr/share/systemd/systemd. I think that's the "configuration files"
>> part of Dave's question.
>
>Our
On Sun, Nov 25, 2012 at 11:39 PM, Colin Guthrie wrote:
> 'Twas brillig, and Lennart Poettering at 24/11/12 23:11 did gyre and gimble:
>> On Sat, 24.11.12 10:18, Dave (Bob) ([email protected]) wrote:
>>
>>> The only thing that I would be interested to know, is why what I would
>>> see as exec
'Twas brillig, and Lennart Poettering at 24/11/12 23:11 did gyre and gimble:
> On Sat, 24.11.12 10:18, Dave (Bob) ([email protected]) wrote:
>
>> The only thing that I would be interested to know, is why what I would
>> see as executables and cofiguration files are put in the 'lib'
>
> The
On Sat, 24.11.12 10:18, Dave (Bob) ([email protected]) wrote:
> The only thing that I would be interested to know, is why what I would
> see as executables and cofiguration files are put in the 'lib'
The binaries in /usr/lib/systemd are binaries that are more or less
internal to systemd, an
On Fri, Nov 23, 2012 at 9:43 AM, David Humphreys wrote:
> I am just starting to experiment with systemd.
>
> My first 'problem' is that the build process does not seem to properly
> obey the --prefix= directive.
>
> I get some stuff installed where I tell it with --prefix, and some other
> stuff
