go-opsi
/
opsi.opsi-builder
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

minor changes

This commit is contained in:
DT Netsolution GmbH 2012-01-27 15:09:21 +01:00
parent 256f62b0ab
commit f07373a276
1 changed files with 19 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/README-aggregated-depot-unionfs.txt
View File

@ -1,18 +1,21 @@
--------------------------------------------------------------------------------------------------
** Our objective: Prevent mixing up custom related files with opsi packages
If you install opsi packages on the OPSI-Server, they will be
** Our objective: Prevent mixing up custom related files with OPSI packages
If you install OPSI packages on the OPSI-Server, they will be
extracted to /opt/pcbin/install. For some packages it's necessary to place
customized files inside this area (e.g. /opt/pcbin/install/<program>/custom/myconfig.cfg)
In this situation, opsi-packages are mixed up with private/individual files. This
could be a problem for maintenance, update or prtivacy reason.
In this situation, OPSI-packages are mixed up with private/individual files. This
could be a problem for maintenance, update or privacy reason.
** Solution: Separation of custom files
To separate the opsi-packages from the custom files, we setup a unionfs filesystem and
publish two directories as one, readonly aggregation filesystem.
To separate the OPSI-packages from the custom files, we setup a unionfs filesystem and
publish two directories as one, read-only aggregation filesystem.
---------------------------------------------------------------------------------------------------
** Installation of unionfs-fuse on a centos system
# Prerequirements for compiling unionfs
@ -33,7 +36,7 @@
modprobe fuse
** Configure the aggreeagated opsi depot
** Configure the aggreeagated OPSI depot
# Create a depot directory containing the customized files.
mkdir /srv/opsi/depot.custom
@ -86,4 +89,13 @@
service smb restart
# Testing using a OPSI client PC
On a windows client PC. connect to the OPSI depot networkshare
\\<opsi-server\opsi_depot and check the directory swaudit\custom. You
should have read-only access to the test file MY_INDIVIDUAL_FILE.txt
located in the individual/private directory on the OPSI-server.
--------------------------------------------------------------------------------------------------