On 31/10/2019 08:47, RobH wrote:
> On 30/10/2019 21:18, Roger Bell_West wrote:
>> On 2019-10-30, Mike wrote:
>>> You've got systemd now, no idea what that does about it :)
>>
>> It will need to be told that this particular filesystem shouldn't be
>> mounted before the network is up. That may happen automatically.
>>
>> However, my experience of systemd has been that if it tries to mount a
>> networked filesystem before the network is up, it will spot the
>> failure and happily hang the entire system rather than let you get in
>> and fix it.
>>
> Basically then from what people have said, the fstab file doesn't mount
> any folders untill the network is up, which makes sense. And if it
> isn't, then the folders are not mounted.
>
> It seems like some kind of bug with the raspberry pi.

No. Because mine DOES.

Its a bug in some verions of Linux - a complex bug that no one takes
ownership of.

Previously mount seemd to get reinvoked after the network was up but
systemd broke that. Obviously the first thing you do when booting is
mount your local file systems. If the networking is delayed, then you
wont mount the networked drives.



>
> Oh well, c'est la vie.

It bloody well shouldn't be.

--
I would rather have questions that cannot be answered...
...than to have answers that cannot be questioned

Richard Feynman

--- SoupGate-Win32 v1.05