Hello everybody,
I use wicd at my laptop, since networkmanager didn’t work well for me.(unable to connect…) However wicd is not connected before fstab probes my nfs shares during boot, so I wold like either to delay the fstab mount command or make sure that the mount command is performed just after that the wireless connection to my home network is up and running.
Running mount -a in terminal works well, but I prefer not to run manual commands at every boot.
Opensuse 11.2, KDE 4.3
On Thu, 2010-04-15 at 21:16 +0000, Tarp wrote:
> Hello everybody,
> I use wicd at my laptop, since networkmanager didn’t work well for
> me.(unable to connect…) However wicd is not connected before fstab
> probes my nfs shares during boot, so I wold like either to delay the
> fstab mount command or make sure that the mount command is performed
> just after that the wireless connection to my home network is up and
> running.
> Running mount -a in terminal works well, but I prefer not to run manual
> commands at every boot.
> Opensuse 11.2, KDE 4.3
>
> Any suggestions appreciated
On alternative is to use automounts for this. Thus it isn’t mounted
until accessed. If you want to be VERY portable with version of Linux
and autofs, you need to use an indirect mount point.
For example you may have an /etc/auto.master with
a line like:
/misc /etc/auto.misc --timeout=30
(it might be commented out)
Then you could have an /etc/auto.misc with something like:
isos -fstype=nfs nas:/isos
Where nas:/isos is the exported NFS area to be mounted via the
automounter under /misc/isos
The Nas share contains digital photos, video and ogg files to be played with Amarok.
If I manually mount the share(s) after boot, a programme like Amarok starts scanning the whole music directory, while at my desktop computer, that is cable connected to the network, Amarok just starts without any scanning, since (I think) the amarokdatabase is compared with the actual directory right after boot.