| 1 |
On Mon, Feb 24, 2014 at 11:43 AM, Ian Stakenvicius <axs@g.o> wrote: |
| 2 |
> On 24/02/14 10:55 AM, Mike Gilbert wrote: |
| 3 |
>> On Mon, Feb 24, 2014 at 7:58 AM, Thomas D. <whissi@××××××.de> |
| 4 |
>> wrote: |
| 5 |
>>> Hi, |
| 6 |
>>> |
| 7 |
>>> not everyone is using systemd. On my systems for example, I don't |
| 8 |
>>> have "/lib/systemd/" (INSTALL_MASK). |
| 9 |
>>> |
| 10 |
>>> The current news item draft raises question like "When the |
| 11 |
>>> 'actual configuration' is in |
| 12 |
>>> /lib/systemd/network/99-default.link... what will happen to |
| 13 |
>>> people without systemd (and a INSTALL_MASK set)?" |
| 14 |
>>> |
| 15 |
>>> Would be nice if the news item and Wiki could handle upgrade path |
| 16 |
>>> for systemd *and* non-systemd users... |
| 17 |
>>> |
| 18 |
>> |
| 19 |
>> You need to remove /lib/systemd/ from INSTALL_MASK. If you don't |
| 20 |
>> want unit files, mask /lib/systemd/system/ instead. |
| 21 |
>> |
| 22 |
> |
| 23 |
> ..it'd be worth adding this little tidbit to the news item, probably... |
| 24 |
> |
| 25 |
|
| 26 |
Yeah. I poked around on the wiki a bit to try and find any reference |
| 27 |
to INSTALL_MASK and systemd, but didn't find anything. |
Archives