/dev/fd0 | /mnt/floppy | ext2 | noauto,user | 0 | 0 | |||||
/dev/cdrom | /mnt/cdrom | iso9660 | noauto,ro,user | 0 | 0 |
But in the name of security, the user option implies noexec, nosuid and nodev, so you must explicitly put exec, suid or dev in the fstab entry if you want these features.
Memory: | cat /proc/meminfo | |
IRQ Assignments: | cat /proc/interrupts | |
PCI Assignments: | cat /proc/pci | |
I/O Addresses: | cat /proc/ioports |
If you have the SUSE distribution (my personal favorite), there is an excellent article by Rene Reucher which deals with the Voodoo3 and Voodoo Banshee cards under Suse linux. You can download the postscript version or the pdf version here. Alternatively, you can go to the original source which might have a later version (the versions here are version 1.1 dated 8July99).
There is another very good site which is distro independent, titled 3Dfx Voodoo3/Banshee Linux How-To.
There is also a Voodoo3/Banshee guide for newbies.
If you use Debian, there is a guide specifically for your distribution at http://crash.ihug.co.nz/~trmusson/home/3dfx/debianv3.html
There is a guide with hints and tips on how to set up Quake II and Quake III for a Voodoo3 and Voodoo Banshee card at http://web.missouri.edu/~ccblake.
By default, Linux uses very conservative settings for IDE (Integrated Drive Electronics) which are sure to slow your hard drive down. First, it doesn't use DMA, which means that data going to and from all IDE devices is processed by the CPU, byte by byte. By using DMA, the data goes into main memory without ever seeing the CPU.
The 2nd problem is that hardware interrupts are masked during IDE transfers, meaning that while data is getting bunched together for transfer to and from an IDE device, no other interrupts are processed. Basically, the machine is just waiting around until the IDE devices are done with their tasks. This slows performance with any other devices connected to the machine, such as modems, network devices and serial devices. This could freeze your PPP connection or make your mouse inactive.
Linux defaults to this lame behavior because there's some hardware out there, like CMD-640B and RZ1000, with bugs which cause errors in IDE data transfers or can cause massive filesystem corruption.
To enable DMA and interrupts during IDE transfers, use:
hdparm -u 1 -d 1 /dev/hdaif your hard drive is hda. This change will get wiped out during a reboot, so you'll prolly want to put this in a startup script so it gets run if you ever have to restart the computer.
See The Hardware HOWTO for more details.
If you're unsure about whether your modem is a winmodem or not, there's a monster site which keeps track of all modems and their compatibility with Linux. Everything you ever wanted to know about modems is either there or has a link at this site.
<port> stream tcp nowait root /usr/sbin/tcpd lprLeaving an open network service like this is considered extremely insecure, so you'll want to use ipchains to limit service to only your friend's IP address.
ipchains -A input -s a_friends_ip -d your_ip lpr_port -p tcp -j ACCEPT ipchains -A input -d your_ip lpr_port -p tcp -j DENYThere are more to the options than what I show below, but I intend to give you an overview of what the above lines mean, rather than all the possibilities.
-A input appends this rule at the end of the input chain.So when your friend's ip attaches to your ip's lpr port with tcp, the rule is "jump" to accept the packets. Otherwise, the rule is to "jump" to deny the packets.
-s is a source address: an IP, hostname or network.
-d is the destination address followed by the destination port.
-p is the protocol this rule will apply to (this will be tcp).
-j what to do when the rule matches. j stands for `jump'.
These chains will vanish after a reboot, so put them in a script that will be run at boot, ideally before inetd is run.
The short answer is that this drive uses the imm module. So as root on the console, type modprobe -a imm. This will load the module. Next, you need a mount directory. If you don't already have one, make a mount point (I like /zip).
Next, mount the drive with mount /dev/sd[x]4 -t vfat /zip. Here, [x] is the next available SCSI drive letter. For example, if you have a single SCSI device not including the zip, [x] would be b. If you have 2 devices, [x] would be c. The 4 means partition 4. Preformated zip disks are always vfat formatted on partition 4. I think this has something to do with where Macs look for data on a disk.