summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorHans Ulrich Niedermann <gp@n-dimensional.de>2002-03-13 17:10:00 +0000
committerHans Ulrich Niedermann <gp@n-dimensional.de>2002-03-13 17:10:00 +0000
commit22f2a07e85c5ea5d27e4a6431f0b40308a4af540 (patch)
treef4b6f671e91c8b62f7f9cf5d8b8890593fafe7cc /INSTALL
parent1277cd6daa19751ce32e9b82b59604b622736c27 (diff)
downloadlibgphoto2-22f2a07e85c5ea5d27e4a6431f0b40308a4af540.tar.gz
added reference to docs instead of just adding docs here
git-svn-id: https://svn.code.sf.net/p/gphoto/code/trunk/libgphoto2@4275 67ed7778-7388-44ab-90cf-0a291f65f57c
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL17
1 files changed, 13 insertions, 4 deletions
diff --git a/INSTALL b/INSTALL
index 6eec3e3cf..206e89446 100644
--- a/INSTALL
+++ b/INSTALL
@@ -67,10 +67,19 @@ The installation procedure should be quite simple:
you can build .deb packages and install these. The packages will
be located in FIXME.
-gphoto2 is not designed to be installed as a setuid/setgid program. Doing
-so will open up a security hole in your system! If you have permission
-problems when accessing your camera, you will probably want to create a
-new user group for the users that are to have camera access and change the
+3) ready to rock
+
+Note that gphoto2 is not designed to be installed as a setuid/setgid
+program. Running ANY gphoto2 frontend as root or setuid root or in a
+similar fashion will open up a SECURITY HOLE in your system!
+
+Read doc/FAQ if you run into problems.
+Read doc/gphoto2.txt for more general information about how to
+configure gphoto2.
+
+If you have permission problems when accessing your camera, read
+doc/gphoto2.txt -- you will probably want to create a new user group
+for the users that are to have camera access and change the
permissions of the serial or USB device to match.