move from support/1.0.27 to feature/1.0.27

1 files changed, 0 insertions, 126 deletions

diff --git a/README.linux b/README.linux
index 6f7aec0..f255c3b 100644
--- a/README.linux
+++ b/README.linux
@@ -45,132 +45,6 @@ Gentoo information:
 Gentoo users: If your USB scanner is not detected at all check that USE=usb is
 set when emerging.
 
-Quick install:
---------------
-
-$ ./configure
-$ make
-$ make install
-
-Step by step install on Linux 2.6.* and 3.*, both with udev:
-------------------------------------------------------------
-
-1. Install with your preferred package manager:
-   (a) the development environment for your Linux distibution
-       - mandatory: gcc, make, kernel header files
-       - optional:  git
-   (b) missing development packages
-	   - libusb-dev or libusb-devel or libusb-compat-devel
-
-2. Get the latest SANE backend from git:
-	You can download "daily git snapshot" from here:
-
-	http://www.sane-project.org/snapshots/
-
-	If you prefer to use git, you can fetch a read-only copy of the git tree
-	with this command:
-
-	$ git clone git://git.debian.org/sane/sane-backends.git
-
-	If you already are using a self compiled SANE backend and just fetched a
-	new copy of the git tree or if you patched some source files, there is no
-	need to follow the installation procedure again. You only need to make and
-	install libsane:
-
-	$ make && sudo make install
-
-3. Configure, make and install latest SANE backend:
-	We install a new SANE dynamically linked shared object library in
-	/usr/local/lib beside your system's SANE library.
-
-	$ ./configure
-	$ make && sudo make install
-
-3.1. SANE library:
-	Register new installed SANE dynamically linked shared object library.
-
-	$ sudo ldconfig -v | grep libsane
-		libsane.so.1 -> libsane.so.1.0.25
-		libsane.so.1 -> libsane.so.1.0.23
-
-	This example shows that the system first find version 1.0.25 and then 1.0.23.
-	This is the correct order.
-
-	If your system first find the old version and then the new installed one,
-	then you must change the order for library paths in /etc/ld.so.conf or you
-	must create the new configuration file /etc/ld.so.conf.d/1-sane.conf.
-
-	$ echo "/usr/local/lib" | sudo tee -a /etc/ld.so.conf.d/1-sane.conf
-
-	Then you must repeat this step.
-
-3.2. Localization file:
-
-	$ cd /usr/share/locale/<language>/LC_MESSAGES
-	$ sudo ln -sf /usr/local/share/locale/<language>/LC_MESSAGES/sane-backends.mo .
-	$ cd -
-
-3.3. udev rules file:
-
-	$ sudo cp tools/udev/libsane.rules /etc/udev/rules.d
-
-	Reconnect your scanner to the USB bus to activate the new rules file.
-
-3.4. Use the scanner with normal user rights:
-
-	Your user must be a member of the group scanner.
-
-	$ cat /etc/group | grep scanner
-	scanner:x:107:<user>
-
-	Create a new group scanner, if it doesn't exist.
-
-	$ sudo addgroup scanner
-
-	Add an existing user to group scanner.
-
-	$ sudo adduser <username> scanner
-
-	After this you must logoff and login again.
-
-4. Test your scanner:
-
-4.1. Check the used backend version:
-
-	The programs must use the installed SANE backend version, e.g. 1.0.25.
-
-	$ scanimage -V
-	scanimage (sane-backends) 1.0.25git; backend version 1.0.25
-
-	This example shows that backend and scanimage are version 1.0.25.
-
-	$ /usr/bin/scanimage -V
-	scanimage (sane-backends) 1.0.23; backend version 1.0.25
-
-	This example shows that an old scanimage (1.0.23) uses the backend 1.0.25.
-
-	If you want to use xsane, start xsane and check the used version with
-	CTRL - i.
-
-4.2. Access scanner with normal user rights:
-
-	$ scanimage -L
-
-	If your scanner isn't recognised here, try this:
-
-	$ sudo scanimage -L
-
-	If this works, your user doesn't have the rights to access the scanner.
-
-	However, please check and redo the installation described above.
-	If this doesn't help, you can ask the mailing list
-	<sane-devel@lists.alioth.debian.org> for further support.
-
-4.3. Testscan:
-
-	$ cd ~
-	$ scanimage > test.pnm
-
 Information about SCSI scanners:
 ================================