[ Pobierz całość w formacie PDF ]

visible when I use the command ls , but I can "cd" to it and my device will then mount. Don't ask me why it is so,
and how to use this automount in GUI. I don't know. The hacker stuff in my auto.misc is the cdrom and floppy
from another computer in my home network.
I automount to the directory /misc (not /mnt) so that I can also mount filesystems manually, without using
automount, to the directory /mnt.
4.2.9 How do I get my parallel-port (external) Zip drive recognized?
RedHat 6.0 and 6.1 The zipdrive (zip100 drive) installation did not work during my upgrade to RedHat 6.0 (the
installation program said that it couldn't find the zipdrive). So, after the installation was completed, I issued the
following commands to insert the modules for parallel port zip drive into the kernel (as root):
/sbin/insmod parport
/sbin/insmod ppa
To have these two lines executed automatically after each bootup, I added them at the end of the file
/etc/rc.d/rc.local (this file is something like autoexec.bat on DOS).
If this still does not work for you, you may also want to edit the file /etc/conf.modules. Mine contains such
a line:
alias parport_lowlevel parport_pc
and there is no line mentioning the "ppa" module.
For the newer Zip250 drive, I have the following two lines executed from my /etc/rc.d/rc.local file:
/sbin/insmod parport
/sbin/insmod imm
4.2.10 Can I set 32-bit hard drive I/O?
Newer Linux distributions (e.g., Mandrake 7.0) can automatically turn on the hard drive optimization: 32 bit
input/outup (I/O) and direct memory access (DMA). Here is how to turn on the hard drive optimization manually.
(Based on http://hardwarezone.community.com.sg/main.htm by Edward Choh.)
Part 4: Linux Newbie Administrator FAQ 66
Linux Newbie Guide by Stan, Peter and Marie Klimas 01/08/2003
This procedure worked fine for me, yet be warned that it can possibly harm the content of your harddrive, so do
not do it if you are a real PC newbie, don't feel geeky today, or have a weak heart--I can't guarantee it will work
for you.
The turning on of the 32-bit I/O and DMA has to be done by root, and I did it in a single-user mode (to minimize
the damage to the file system if something went wrong and I had to reboot). I definitely would not do it on a
system currently running many programs or X-windows, and would have a current backup of any precious data.
To boot your computer in a single-user mode, I type this at the lilo prompt (during bootup):
linux single
Say, I would like enable the 32-bit I/O on my first IDE harddrive, which is "hda". First, I time the harddrive
current performance, and note the score:
hdparm -t /dev/hda
Now, I display my current I/O and DMA settings:
hdparm -c /dev/hda
[my system showed 0, meaning that the 32-bit I/O is turned off and the default 16-bit access is used]
hdparm -d /dev/hda
[my system showed 0 again, meaning that the harddrive DMA access is turned off].
Now, I turn on the 32 bit IO and DMA:
hdparm -c 1 /dev/hda
hdparm -d 1 /dev/hda
Now, I can time the performance of the harddrive again to compare the score with the original one:
hdparm -t /dev/hda
If everything worked ok, and the performance has improved, I can "commit" the new settings, so they can survive
a soft reset:
hdparm -k 1 /dev/hda
To have the new settings in effect every time you reboot the machine, you may add a line at the end of the file
/etc/rc.d/rc.local (this file is something like AUTOEXEC.BAT in DOS):
hdparm -c 1 -d 1 -k 1 /dev/hda
If something did not work as expected, or the performance did not really improve, I can reboot at any time and the
old settings will be in effect as long as I did not perform the last operation.
I performed this tune-up on 4 hard drives on my home network. It was a success on 3 newer hardrives: the
performance improved by 30-300% and at least one computer "feels" faster than before. One harddrive (which is
always flaky) hanged the computer hard during the performance test and I had to reset the machine (no damage
done).
4.2.11 I reached the limit on the number of opened files (error message)
You can increase the limit via the /proc file system. This file system is entirely virtual--it is just a "window" to
see or set some parts of the Linux kernel. To read the maximum number of simultanously opened files on my
system, I use the following command:
cat /proc/sys/fs/file-max
On my system (Mandrake 7.2), the limit is 8192. To increase it, I use (as root):
Part 4: Linux Newbie Administrator FAQ 67
Linux Newbie Guide by Stan, Peter and Marie Klimas 01/08/2003
echo 16000 > /proc/sys/fs/file-max
You may also want to increase the limit on a related kernel variable:
echo 30000 > /proc/sys/fs/inode-max [ Pobierz całość w formacie PDF ]