Systemd on vivid beta

[Colin Law]

On 10 March 2015 at 00:38, Bruce Ferrell <bferrell at baywinds.org> wrote:
> On 03/09/2015 03:02 PM, Tom H wrote:
>> On Mon, Mar 9, 2015 at 3:56 PM, Colin Law <clanlaw at gmail.com> wrote:
>>> On 9 March 2015 at 18:08, Tom H <tomh0665 at gmail.com> wrote:
>>
>>>> I'd start by adding "$network" to your "Required-Start" and
>>>> "Required-Stop" lines. It might create a better dependency translation
>>>> when a systemd .service unit is generated from the sysvinit script.
>>> More research led me to do that just a few minutes before receiving
>>> this, but it does not seem to have helped. Is the generated unit human
>>> readable?
>> Under "/run/systemd/".
>>
>>
>>>> Longer-term, you should look into migrating your mounts to systemd .mount units.
>>> OK. I am slightly put off by the fact that I got round to learning a
>>> bit about upstart and converting one of my scripts just before it was
>>> announced that ubuntu was changing to systemd :(
>> With systemd mount units, you can cheat.
>>
>> Set up an fstab line for your cifs mount, reboot, and look at the
>> .mount unit that systemd-fstab-generator will have created under
>> "/run/systemd/".
>>
> Gee... We used to be able to "cheat" and just add the mount line to /etc/fstab without a "noauto" option.  then mount -a did the trick... I guess that too complex for systemd to handle

Can one no longer do that?  It is not what I want though, I have a
dynamic network with devices coming and going, and the script
automatically mounts/unmounts them as they come and go.

Colin