Are you mounting it via NFS? If so, all you need to do is open 2049/udp and 111/tcp in your firewall. My linux/iptables script uses the following:
-A INPUT -p udp -m udp --dport 2049 -j ACCEPT
-A INPUT -p udp -m udp --dport 111 -j ACCEPT
You can add "-s ip.of.client" if you're paranoid.
Tried that, zadfrack, and no dice. (RPC timeouts!) Some sources elsewhere claim that various nfs-using services on the server use essentially random ports. (Actually, I didn't use this -m option ... I'll give it a shot.)
Do you have a good explanation for why you need this much storage space? Philosophers should be impoverished, so you can't afford audiovisual materials and are too scrupulous to download them illegally. Philosophers also don't write much, and you could store every word of philosophy ever published in a fraction of that space, I'm guessing. With a better state security apparatus--think East Germany--we'd get good answers to these questions.
Ah, yes. I was trying to remember why I opened port 1500 in my iptables script.
You have to pick a high-numbered port, e.g. 1500, and set your NFS mountd to always use this port. Then open that port (udp) in your iptables script.
If this is a RedHat-ish distro, you can set
MOUNTD_PORT=1500
in /etc/sysconfig/network.
If not, add "-p 1500" to your startup script wherever it starts up mountd.
Anyone with a ready opinion on the bestest external HD? I think I want something with a Firewire 400 connexion.
You have to pick a high-numbered port, e.g. 1500, and set your NFS mountd to always use this port.
Unfortunately, the mounted drive resides on a sealed box to which I don't have telnet or ssh access. There are various hackish tricks to get root access to it, none of which I've tried yet (it looks as if smbclient can access directories with system binaries, though I don't know if I could replace them with my own).
This isn't a perfect solution, but you could run "rpcinfo -p servername" on the client to ask the server's portmapper what port mountd is running on, and open that one up. (Only the udp port matters.)
Of course, that'll change every time the NFS daemons are restarted, but how often will that be?
5:Music or movies, of course. No not movies, nobody shuffles movies. I have 500G installed, and HD's on the shelves like CD's. In fact, I think a set of 100s or 250s, slung in and out, is a better plan. Got jazz on one, xlassical on another, etc.
The further question involves why, since it only takes 5-10 minutes to load a disc and transfer, ones demands the randomness of a huge library instead of a more direct choice and control of what is listened to. That is a good question.
Finally, if w-lfs-n is into lossless, we are talking a hundred megabytes per cd. At least? Is this right?
This isn't a perfect solution, but you could run "rpcinfo -p servername" on the client to ask the server's portmapper what port mountd is running on, and open that one up. (Only the udp port matters.)
Of course, that'll change every time the NFS daemons are restarted, but how often will that be?
Oh, good idea. It doesn't really matter how often it's restarted (not often, hopefully; one of the neat things about this box is that it's got wireless connectivity so that if it's too noisy I can stash it somewhere not in my room), because that kind of info is available at boot-time and greppable; hence iptables can be updated correctly if it's changed automagically. I already do something like that just for dhcp-related matters.