[opensuse] ODF files on SMB/CIFS share
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on? Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manne Merak wrote:
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on?
Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day.
Have you considered mounting the share rather than dynamically accessing it? see man mount.cifs - -- ============================================================================== 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 iD8DBQFIZLM7asN0sSnLmgIRAihCAJ0XcmctFJdf8LrBZf2NPnN7zPvW0gCfV4I8 BP6auRMajKLZwSgWympvcdQ= =rqpI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Manne Merak wrote:
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on?
Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day.
You can configure the Windows ID and password in "Personal Settings". Click on Interent & Network > Local Network Browser. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Manne Merak wrote:
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on?
Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day.
You can configure the Windows ID and password in "Personal Settings". Click on Interent & Network > Local Network Browser.
Thats how I always do it (they must really add a check box for using the system user and passwd). But the problem is OO dont use it. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Manne Merak wrote:
James Knott wrote:
Manne Merak wrote:
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on?
Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day.
You can configure the Windows ID and password in "Personal Settings". Click on Interent & Network > Local Network Browser.
Thats how I always do it (they must really add a check box for using the system user and passwd). But the problem is OO dont use it.
Manne
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: #!/bin/bash ## check_root if [[ $UID != "0" ]]; then echo -e "\n\n\tThis program must be run as 'root', you with UID=$UID won't do.\n" exit 1 fi ## define variables and mount share 1 SERVER="//zion" OPTS=$(cat /home/david/bin/mntops_dcr) SHARE="/config" MPOINT="/mnt/zion-cfg" if mount | grep -q "on ${MPOINT} type"; then echo "${MPOINT} already mounted" else if [[ ! -d ${MPOINT} ]]; then mkdir -p ${MPOINT} >/dev/null 2>&1 fi mount.cifs ${SERVER}${SHARE} ${MPOINT} ${OPTS} fi ## define and mount share 2 SHARE="/david" MPOINT="/mnt/zion-david" if mount | grep -q "on ${MPOINT} type"; then echo "${MPOINT} already mounted" else if [[ ! -d ${MPOINT} ]]; then mkdir -p ${MPOINT} >/dev/null 2>&1 fi mount.cifs ${SERVER}${SHARE} ${MPOINT} ${OPTS} fi exit 0 Your credential file "mntops_dcr" would contain: -o username=david,uid=1000,password=xxxyyyzzz -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Manne Merak wrote:
James Knott wrote:
Manne Merak wrote:
I have some XLS and ODT files on a Windows AD server (CIFS share). When openning the XLS files using KIO (Konq or Krusader with smb://) OpenOffice pops up and asks for a Win domain password (which I give) and everything opens as expected. When I do the same for the ODT file I get get an OpenWith popup from KDE. If I navigate to Calc it works. When copying the file to the local drive it works as expected; so the file associations is fine. Whats going on?
Manne ps. is there is way to tell OpenOffice to get my Win domain password from KDE or Kerberos or where-ever. Very annoying to have to type it in about 20 times a day.
You can configure the Windows ID and password in "Personal Settings". Click on Interent & Network > Local Network Browser.
Thats how I always do it (they must really add a check box for using the system user and passwd). But the problem is OO dont use it.
Manne
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? 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. I really believe the smb/nfs/fish(sshfs) (network share abstraction layer) should be managed totally abstracted from the program using it. 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-30 at 09:50 +0100, G T Smith wrote:
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).
There is a problem here. If the file is used by several people on a room, it makes more sense references like smb://link instead of /filesystemfile because it will be the same on all computers, be them linux or windows. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIaK4btTMYHG2NR9URAn8XAJ9hJ2vwtK7C+uXsfcVM4txPsCi4cACfSKIJ EEVyZw4vbwLSZvfJoN0z208= =wo/j -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Monday 2008-06-30 at 09:50 +0100, G T Smith wrote:
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).
There is a problem here. If the file is used by several people on a room, it makes more sense references like smb://link instead of /filesystemfile because it will be the same on all computers, be them linux or windows.
I have into problems with open office in the past due differences in the path specification in between Windows and Linux. If a path specification get embedded in a document written on one OS reading it on the other OS may be problematic. IIRC smb://link: is not a legitimate way of grabbing Windows network resources from Windows machines anyway (a bit specific to samba and *NIX), UNC being the standard route on Windows and would create some confusion for Windows users. Unless OO can translate smb: into a UNC path on a Windows machine one may have a problem with this. But it is a long time since I last used Windows so I could be wrong. However, I would suggest having such a mixed client environment this would only be the start of the support issues. Windows client does not play nicely with Linux clients at the best of times.
-- Cheers, Carlos E. R.
- -- ============================================================================== 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 iD8DBQFIaSSxasN0sSnLmgIRAvYrAJoCeKz9um3IOfRX2+3X2ZSUVRuOJgCbBUQI sQrVbqJIrFMFozOKbGvwbgc= =/kQw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Carlos E. R. wrote:
The Monday 2008-06-30 at 09:50 +0100, G T Smith wrote:
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). There is a problem here. If the file is used by several people on a room, it makes more sense references like smb://link instead of /filesystemfile because it will be the same on all computers, be them linux or windows.
IIRC smb://link: is not a legitimate way of grabbing Windows network resources from Windows machines anyway (a bit specific to samba and *NIX), UNC being the standard route on Windows and would create some confusion for Windows users. Unless OO can translate smb: into a UNC path on a Windows machine one may have a problem with this. But it is a long time since I last used Windows so I could be wrong.> -- Cheers,
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manne Merak wrote:
G T Smith wrote:
Carlos E. R. wrote:
The Monday 2008-06-30 at 09:50 +0100, G T Smith wrote:
<snip>
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
Interesting, this is new, IIRC earlier versions did not do this. But this does open a can of worms as in more complex environment objects can have both local and networked UNC paths on the Windows side. Should be fine for the SOHO user most of the time... However, the plot thickens. The smb:\\ url spec is in the process of being formalised by IETF but as far as I can work out has not been finalised and to what extent this may cause problems to the various people who have jumped the gun is a moot point. The cifs support currently (at least according to the man page) does not support the URL format only the UNC spec. The whole thing is looking a little messy.... - -- ============================================================================== 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 iD8DBQFIaeqiasN0sSnLmgIRAvzCAKCsGakdtWoSsWSvstWnJGIr5m3x/ACfRkPb zDawRId8Gm4Ma02FRm6lKeg= =YlpK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Manne Merak wrote:
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
That's where the beauty of mounting the shares is the best solution. OO sees the files as part of the local file system, and it works the same in a mixed environment. As long as the links are to files that are on the mounted filesystem, there should be no difference in files on the cifs mount or local files. In fact comparing, "map drive" in windows to the mount.cifs on a linux client work equally well. We run a mixed network with 5 windows clients for every linux client and all both clients are able to access files that reside on the 10.3 server, including following links from spreadsheets to the original source documents for the data. We haven't run into any problems with any file access for the past 8 years. The only change over that course of time has been the move from smbmount to mount.cifs. The only thing I can think of is some strange oplock behavior for your setup. You might try updating the samba/cifs package to see of that help. You can simply add the samba repositories and get the stable release for opensuse from the samba folks that is generally 4-8 releases ahead of the opensuse package: for 10.3, just add the repository to yast/zypper; http://us1.samba.org/samba/ftp/Binary_Packages/SuSE/3.0/10.3/ for 11.0 http://us1.samba.org/samba/ftp/Binary_Packages/SuSE/3.0/11.0/ -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Manne Merak wrote:
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
That's where the beauty of mounting the shares is the best solution. OO sees the files as part of the local file system, and it works the same in a mixed environment. As long as the links are to files that are on the mounted filesystem, there should be no difference in files on the cifs mount or local files.
In fact comparing, "map drive" in windows to the mount.cifs on a linux client work equally well. We run a mixed network with 5 windows clients for every linux client and all both clients are able to access files that reside on the 10.3 server, including following links from spreadsheets to the original source documents for the data. We haven't run into any problems with any file access for the past 8 years. The only change over that course of time has been the move from smbmount to mount.cifs. How do you format the hyperlinks to files, on the network, in the spreadsheets so that it will work in Win and Lin environment.?
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file. Dare I say it?, mimic the way WinXP handles shares. KDE and Gnome (others?) are already doing this - but its the wrong place to do it - it should be handled by a low level "share automounter". Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Manne Merak wrote:
David C. Rankin wrote:
Manne Merak wrote:
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
That's where the beauty of mounting the shares is the best solution. OO sees the files as part of the local file system, and it works the same in a mixed environment. As long as the links are to files that are on the mounted filesystem, there should be no difference in files on the cifs mount or local files.
In fact comparing, "map drive" in windows to the mount.cifs on a linux client work equally well. We run a mixed network with 5 windows clients for every linux client and all both clients are able to access files that reside on the 10.3 server, including following links from spreadsheets to the original source documents for the data. We haven't run into any problems with any file access for the past 8 years. The only change over that course of time has been the move from smbmount to mount.cifs. How do you format the hyperlinks to files, on the network, in the spreadsheets so that it will work in Win and Lin environment.?
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file. Dare I say it?, mimic the way WinXP handles shares. KDE and Gnome (others?) are already doing this - but its the wrong place to do it - it should be handled by a low level "share automounter".
Manne
Manne, The links are the links native to OO or MS office. For example take the function for X2 created in OO Calc and create a chart in OO Calc. Paste the chart into OO writer and a link is created between the OO calc file and the chart shown in OO writer. Both files exist on //nirvana/home/david/tmp/xsquared.odt with //nirvana/home/david mounted as /mnt/nirvana-david. Opening OO writer and opening the chart will open the OO calc file. The behavior is the same with excell and word. The only caveat is if someone is useing 64-bit linux client. Then none of the links work because the OO links rely on Java, and currently the java environment for x86_64 linux doesn't exist in a usable form unless you track down, install and configure either V1.6 "opensdk" or 1.7 "icedtea". Neither of which I have done, but have been advised of. If you use 64 bit clients, then that might explain your problems. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Manne Merak wrote:
David C. Rankin wrote:
Manne Merak wrote:
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
In fact comparing, "map drive" in windows to the mount.cifs on a linux client work equally well. We run a mixed network with 5 windows clients for every linux client and all both clients are able to access files that reside on the 10.3 server, including following links from spreadsheets to the original source documents for the data. We haven't run into any problems with any file access for the past 8 years. The only change over that course of time has been the move from smbmount to mount.cifs. How do you format the hyperlinks to files, on the network, in the spreadsheets so that it will work in Win and Lin environment.?
Manne
Manne,
The links are the links native to OO or MS office. For example take the function for X2 created in OO Calc and create a chart in OO Calc. Paste the chart into OO writer and a link is created between the OO calc file and the chart shown in OO writer. Both files exist on //nirvana/home/david/tmp/xsquared.odt with //nirvana/home/david mounted as /mnt/nirvana-david.
Interesting, what does the links look like? Im sure it has to be relative paths because Win wouldnt understand /mnt/nirvana-david? and Lin not //nirvana/home/david.......? Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Manne Merak wrote:
David C. Rankin wrote:
Manne Merak wrote:
Well, OO 2.4 (not sure about previous versions) does exactly this - it parses hyperlinks and translates \\server\share\file to smb://server/share/file on and then back to when saving the sheet as XLS (well there is a bug still open on it, but the developer is on it as I type). But again this is way beyond what OO should be worried about - no wonder its getting bloated.
Manne
That's where the beauty of mounting the shares is the best solution. OO sees the files as part of the local file system, and it works the same in a mixed environment. As long as the links are to files that are on the mounted filesystem, there should be no difference in files on the cifs mount or local files.
In fact comparing, "map drive" in windows to the mount.cifs on a linux client work equally well. We run a mixed network with 5 windows clients for every linux client and all both clients are able to access files that reside on the 10.3 server, including following links from spreadsheets to the original source documents for the data. We haven't run into any problems with any file access for the past 8 years. The only change over that course of time has been the move from smbmount to mount.cifs. How do you format the hyperlinks to files, on the network, in the spreadsheets so that it will work in Win and Lin environment.?
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file. Dare I say it?, mimic the way WinXP handles shares. KDE and Gnome (others?) are already doing this - but its the wrong place to do it - it should be handled by a low level "share automounter".
Manne
Manne,
The links are the links native to OO or MS office. For example take the function for X2 created in OO Calc and create a chart in OO Calc. Paste the chart into OO writer and a link is created between the OO calc file and the chart shown in OO writer. Both files exist on //nirvana/home/david/tmp/xsquared.odt with //nirvana/home/david mounted as /mnt/nirvana-david.
Wow, just tried it with fusesmb (mount -f cifs will also do), and it just works as you describe. I see the links are made relative to the document so thats how its portable over OSes. I see Excel wont link over to another server share - only relative to current domain and server. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/03/2008 01:38 AM, Manne Merak wrote:
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file.
Do you mean like the startup service smbfs? -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote:
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file.
Do you mean like the startup service smbfs?
Yes/No, it should work as KDE and Gnome smb:// works, just have it done by something lower down in the services structure. For example; I can go to Kate and open-file smb://server/share/file; edit and save. But when I try the same with Gimp it wont understand smb:// (because its not using the KDE kio file-open libs). Now if all apps (KDE, Gnome, commandline, ...) passed their requests to this underlying automounter they will all just use the resulting file handle as if its on the local machine (the automounter will mount the share locally and pass back an alias, ie smb://server/.....). As I remember smbfs was replaced by cifs(fs)? Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Manne Merak wrote:
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote:
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file.
Do you mean like the startup service smbfs?
Yes/No, it should work as KDE and Gnome smb:// works, just have it done by something lower down in the services structure. For example; I can go to Kate and open-file smb://server/share/file; edit and save. But when I try the same with Gimp it wont understand smb:// (because its not using the KDE kio file-open libs). Now if all apps (KDE, Gnome, commandline, ...) passed their requests to this underlying automounter they will all just use the resulting file handle as if its on the local machine (the automounter will mount the share locally and pass back an alias, ie smb://server/.....). As I remember smbfs was replaced by cifs(fs)?
Manne
Manne, Did you by chance update to cifs-mount-3.2.0-24.1.122 (the latest for openSuSE at samba.org)? If so, cifs is broken in that package. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote:
(Repeating myself) Im all for mounting the share and have it act like a local resource - my issue is that it ought to be an OS function - just like my USB stick is automounted I would like my CIFS shares to be "automounted" and returned to the requesting process, on the fly, as a local file.
Do you mean like the startup service smbfs?
Well, I did n bit of Googling and, like most great ideas :), there is a solution out there. http://www.ricardis.tudelft.nl/~vincent/fusesmb/ It describes almost exactly what I want. Will try it out tonight. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manne Merak wrote:
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote: Well, I did n bit of Googling and, like most great ideas :), there is a solution out there. http://www.ricardis.tudelft.nl/~vincent/fusesmb/ It describes almost exactly what I want. Will try it out tonight.
Manne
Tried this some time ago and the performance was pretty poor. Spends a significant amount of time authenticating and not a lot of time on servicing files which is BTW the major issue with the approach that you describe, each request for a resource requires an authentication request (whether or not authentication is actually required). It is an extremely inefficient way of doing things. If you have a very small legacy workgroup it may be useful but it essentially does the same thing as cifs but slower. They may have improved things since... - -- ============================================================================== 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 iD8DBQFIbIzTasN0sSnLmgIRAl3sAKD58EX2S994YBCmnoS7Yk9DElONHQCeJ7Uk 4dEhm9qhEXc+T0dYQPbU7gI= =2idt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Manne Merak wrote:
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote: Well, I did n bit of Googling and, like most great ideas :), there is a solution out there. http://www.ricardis.tudelft.nl/~vincent/fusesmb/ It describes almost exactly what I want. Will try it out tonight.
Manne
Tried this some time ago and the performance was pretty poor. Spends a significant amount of time authenticating and not a lot of time on servicing files which is BTW the major issue with the approach that you describe, each request for a resource requires an authentication request Well, that is just bad implementation, nothing wrong with the approach. Windows does this very efficiently.
(whether or not authentication is actually required). It is an extremely inefficient way of doing things. If you have a very small legacy workgroup it may be useful but it essentially does the same thing as cifs but slower.
They may have improved things since...
As I understand it just mounts the share with smbmount (mount.cifs), so if they can just streamline the authentication it should be fine. (I see this from the point of view of one of my desktop-user friends running Kubuntu (he does ruby def on Ununtu servers and need the debian environment, dont ask) - he can help himself around a PC but will not be interested in fiddling with the fstab file or "mount -cifs" when someone comes around with a laptop and share some files on the network.) Office environment is something else. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Manne Merak wrote:
Joe Morris wrote:
On 07/03/2008 01:38 AM, Manne Merak wrote: Well, I did n bit of Googling and, like most great ideas :), there is a solution out there. http://www.ricardis.tudelft.nl/~vincent/fusesmb/ It describes almost exactly what I want. Will try it out tonight.
Manne
Tried this some time ago and the performance was pretty poor. Spends a significant amount of time authenticating and not a lot of time on servicing files which is BTW the major issue with the approach that you describe, each request for a resource requires an authentication request (whether or not authentication is actually required). It is an extremely inefficient way of doing things. If you have a very small legacy workgroup it may be useful but it essentially does the same thing as cifs but slower.
They may have improved things since...
fusesmb I have found my solution (now just to get KDE and Gnome to play along en use this instead of its own impl). It works beautifully. Is slower because of auth everytime you go to new share, but its negligible and far outweigh it usefulness for adhoc sharing. Thanks for the discussion Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Manne Merak wrote:
David C. Rankin wrote:
Manne Merak wrote:
James Knott wrote:
Manne Merak wrote:
<snip>
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
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.
Well, I cant really see why die transport medium should matter to the "normal" user. Yes, if you have specific needs for FTP or SSHfs etc then it matters, but most people, including me just want to get the file, edit and save irrelevant of physical location or medium. Single sign-on AD (or any other directory service) is not really necessary in SOHO environments, the servers and shares usually stay put. Its essential for centralized user/resource management thou. Again, I am currently happy with smb://,nfs://,ftp:// and fish:// ; it works and it works as expected - I just dont want KDE, Gnome or OO to manage it - it should be moved "down" into an abstraction layer for all programs to use transparently. Manne -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manne Merak wrote:
G T Smith wrote:
<snip>
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).
My error should read "does not need" ...
Well, I cant really see why die transport medium should matter to the "normal" user. Yes, if you have specific needs for FTP or SSHfs etc then it matters, but most people, including me just want to get the file, edit and save irrelevant of physical location or medium. Single sign-on AD (or any other directory service) is not really necessary in SOHO environments, the servers and shares usually stay put. Its essential for centralized user/resource management thou. Again, I am currently happy with smb://,nfs://,ftp:// and fish:// ; it works and it works as expected - I just dont want KDE, Gnome or OO to manage it - it should be moved "down" into an abstraction layer for all programs to use transparently.
For SOHO use of for NFS and cifs this is what a static mount point is good for in *NIX, it keeps things relatively simple once set up and working. I would agree that in smaller environments single sign on is overkill.
Manne
- -- ============================================================================== 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 iD8DBQFIaSTBasN0sSnLmgIRAvgCAKD2e8FZar/yfKLRyxh/T+DSVMeKugCcDj8T 8UWKv3/FciHhzH6R/m6C0Kg= =o72k -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
For SOHO use of for NFS and cifs this is what a static mount point is good for in *NIX, it keeps things relatively simple once set up and working. I would agree that in smaller environments single sign on is overkill.
100% agree. We run our 1 samba server in "stand alone" mode and manage access with smbpasswd. For the 10-15 users we have at any one time, this is the best solution. No backends (kerbose, etc.) to worry about, the setup is simple, and it is absolutely bulletproof. mount.cifs is the perfect solution here. Mount the share, and forget about it, it is persistent. It doesn't matter if you take the server down, reboot, whatever, after you mount the share on the client, it is just there and talks to the server when it is up and simply gives an access error if for some reason the server is off-line. For each user I generally mount 2 shares: (1) the main share directory and (2) the user's home directory. I reserve a 3rd config share to me alone of /. Our directory structure for shared files is all done under the main share like: /home/samba /home/samba/law /home/samba/law/egwfiles /home/samba/law/egwfiles/workflow /home/samba/law/egwfiles/home /home/samba/law/egwfiles/backup /home/samba/law/egwfiles/mydms /home/samba/law/joint /home/samba/law/joint/rankinallen /home/samba/law/joint/rankinguillory /home/samba/law/joint/rankinbertin /home/samba/law/joint/rga /home/samba/law/joint/bertinguillory /home/samba/law/computer /home/samba/law/computer/software /home/samba/law/computer/hardware /home/samba/law/computer/videotemp /home/samba/law/rankin /home/samba/law/rankin/judicial_campaign /home/samba/law/rankin/clients_rejected /home/samba/law/rankin/investigation /home/samba/law/rankin/tbpe /home/samba/law/rankin/office /home/samba/law/rankin/accounting /home/samba/law/rankin/clients /home/samba/law/rankin/personal /home/samba/law/rankin/clients_potential /home/samba/law/rankin/LLC /home/samba/law/scans /home/samba/law/office /home/samba/law/office/CLE Downloads and Essays /home/samba/law/office/ooo-2.o /home/samba/law/office/Legislation /home/samba/law/office/Copiers /home/samba/law/office/Calendars /home/samba/law/office/Insurance /home/samba/law/office/Office /home/samba/law/office/Templates /home/samba/law/office/Organization /home/samba/law/office/Politics /home/samba/law/office/Shared Files /home/samba/law/office/State Bar of Texas /home/samba/law/office/Projects /home/samba/law/office/Commercial Bank /home/samba/law/office/cv_biographies /home/samba/law/office/clients /home/samba/law/office/TWC /home/samba/law/office/Accounting /home/samba/law/office/IRS /home/samba/law/office/Firm /home/samba/law/office/Lylian - Office /home/samba/law/office/Ochiltree /home/samba/law/forms /home/samba/law/forms/life expectancy /home/samba/law/forms/cases-other /home/samba/law/forms/Trial /home/samba/law/forms/briefs /home/samba/law/forms/mediation /home/samba/law/forms/llc /home/samba/law/forms/deposition /home/samba/law/forms/appeal-civil /home/samba/law/forms/Pretrial /home/samba/law/forms/Office /home/samba/law/forms/PJC <snip> I have never had any problems with this approach. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
David C. Rankin -
G T Smith -
James Knott -
Joe Morris -
Manne Merak