1 |
On Tue, Feb 25, 2014 at 5:12 AM, Joshua Kinard <kumba@g.o> wrote: |
2 |
> On 02/24/2014 12:17 PM, Mike Gilbert wrote: |
3 |
>> On Mon, Feb 24, 2014 at 11:43 AM, Ian Stakenvicius <axs@g.o> wrote: |
4 |
>>> On 24/02/14 10:55 AM, Mike Gilbert wrote: |
5 |
>>>> On Mon, Feb 24, 2014 at 7:58 AM, Thomas D. <whissi@××××××.de> |
6 |
>>>> wrote: |
7 |
>>>>> Hi, |
8 |
>>>>> |
9 |
>>>>> not everyone is using systemd. On my systems for example, I don't |
10 |
>>>>> have "/lib/systemd/" (INSTALL_MASK). |
11 |
>>>>> |
12 |
>>>>> The current news item draft raises question like "When the |
13 |
>>>>> 'actual configuration' is in |
14 |
>>>>> /lib/systemd/network/99-default.link... what will happen to |
15 |
>>>>> people without systemd (and a INSTALL_MASK set)?" |
16 |
>>>>> |
17 |
>>>>> Would be nice if the news item and Wiki could handle upgrade path |
18 |
>>>>> for systemd *and* non-systemd users... |
19 |
>>>>> |
20 |
>>>> |
21 |
>>>> You need to remove /lib/systemd/ from INSTALL_MASK. If you don't |
22 |
>>>> want unit files, mask /lib/systemd/system/ instead. |
23 |
>>>> |
24 |
>>> |
25 |
>>> ..it'd be worth adding this little tidbit to the news item, probably... |
26 |
>>> |
27 |
>> |
28 |
>> Yeah. I poked around on the wiki a bit to try and find any reference |
29 |
>> to INSTALL_MASK and systemd, but didn't find anything. |
30 |
> |
31 |
> Minor note, also not using systemd (or udev, for that matter), but out of |
32 |
> curiosity, I checked my x86_64 system and I don't have a /lib/systemd |
33 |
> directory. Looks like everything is in /usr/lib/systemd instead. So, this |
34 |
> might be a good item to document somewhere (possibly the wiki), so people |
35 |
> aren't confused and add the wrong directories to INSTALL_MASK (or other |
36 |
> relevant variables) |
37 |
> |
38 |
|
39 |
I really just meant to correct any existing documentation which may exist. |
40 |
|
41 |
Adding both /lib/systemd/systemd and /usr/lib/systemd/system should be |
42 |
fairly safe. |