https://bugzilla.novell.com/show_bug.cgi?id=336942#c7
DERUMAUX Marc changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
--- Comment #7 from DERUMAUX Marc 2007-11-08 15:43:47 MST ---
Thanks for the advice. I've solved the problem with an automount NFS with a
short timeout (30s). But I have to admit that file sharing on a network of
laptops (that can open or suspend at any time) is not an easy task with NFS.
I'm not fan of windoze OS but it doesn't seem to be so touchy with a computer
shutdown in the network... I couldn't find another solution on Suse else than
automount, which can't be configured within Yast2.
Those remarks are not critics as I'm fully satisfied with my brand new 10.3,
that's only remarks from a non-specialist user that tries to solve his
problems. But may be it can help to make next Suse 11 still better !
I'm proud to affirm I've never booted again windows since my 10.3 install at
the end of september (RC1). I only lauched a virtualbox windows to drive my
canon scanner !
I switch back this bug at FIXED as the kicker bug did not appear again since I
solved the NFS issue.
Best regards,
Marc
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.