-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manne Merak wrote:
David C. Rankin wrote:
Manne Merak wrote:
James Knott wrote:
Manne Merak wrote:
<snip>
Manne,
I second GT's (not Grant's) suggestion that you mount the drive instead of accessing it dynamically. I would also suggest you use a batch file to do it (saves typing and you call create a convenient alias in .bashrc) Here is an example of a script that can mount multiple shares and your credentials are contained in a separate file for safe keeping. Just change the variable as needed:
Its to bad that OO doesn't handle this kind of thing more gracefully. The XLS file I work with contains a lot of hyperlinks to other XLS files on the smb share. Will OO access these shares through the mount I created or will it just spawn a new smb:// link?
Yes.. if the links are specified as links in the file space rather than on the network. (Opening multiple network connections seems to be a rather inefficient way of handling this anyway). If the share is one that is used a lot it could be be mounted either via /etc/fstab if you are the sole user of the machine or possibly pam.mount or a login script if the machine is multi-user...
The smb:// layer (kio in KDE) is very useful, it makes accessing shares more "natural", as it should be. I dont "mount" every ftp server by hand I go to why should smb be different.
see below
I really believe the smb/nfs/fish(sshfs) (network share abstraction layer) should be managed totally abstracted from the program using it.
see below
OO should just ask for file smb://server/share/file.xls and the OS should handle the file transactions (not OO itself). (smb:// is almost there, IMHO it just needs to move down from Gnome and KDE into some independent "network share abstraction layer" with some refining around user:passw delivery) Well, my 2c worth Manne
In this situation one would ideally be using some form of single sign on and there is no reason this cannot be implemented within a mixed AD/Windows, Linux environment with currently available technologies but it is far from trivial to do so. Ideally all files can then be viewed as residing in the local directory structure independent of which server they are actually located on, the user then does need to be aware of the network (and things such as kio become redundant). BTW comparing cifs to ftp or ssh is comparing chalk and cheese, the more appropriate comparison is cifs and NFS/NISS. ftp/sftp/ssh and CIFS/NFS/NISS do different jobs and trying to make them appear the same is probably a bad idea. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIaJ5QasN0sSnLmgIRAlbRAJ4okKyW5faAc+LAOkt1+aHPRmK0JQCgrAcP XPxU4pNXE7wT9eSzoxE8PMY= =bYsr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org