From cad70ca6eda6498db9acdae97fade2c615c3ce5b Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij Table of Contents
+ Table of Contents
When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
setup program unable to complete the installation.
@@ -9,9 +8,9 @@ permissions The problem is that MS Office Setup checks that a file is
rdonly by trying to open it for writing.
Admin users can always open a file for writing, as they run as root.
-You just have to install as a non-admin user and then use "chown -R"
+You just have to install as a non-admin user and then use "chown -R"
to fix the owner.
-
Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
product that resides on a shared resource, or from which that product can be
@@ -37,7 +36,7 @@ set the following parameters on the share containing it:
[MSOP95]
path = /where_you_put_it
comment = Your comment
- volume = "The_CD_ROM_Label"
+ volume = "The_CD_ROM_Label"
read only = yes
available = yes
share modes = no
@@ -45,8 +44,8 @@ set the following parameters on the share containing it:
browseable = yes
public = yes
Now you are ready to run the setup program from the Microsoft Windows
-workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup
-
Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg
-Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open. Make sure that you open the database as 'shared' and to 'lock modified records' Of course locking must be enabled for the particular share (smb.conf)
Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open. |
Make sure that you open the database as 'shared' and to 'lock modified records' |
Of course locking must be enabled for the particular share (smb.conf) |
+
-- cgit