Niki Kovacs a écrit :
Since the aim is lowcost, would it be wrong to install that fileserver on a no-name desktop PC with a 64bit processor and enough RAM, and then simply put 2 x 2 To hard disks in it, either with a mirroring RAID (can never remember which does what in 0, 1 and 5) or some rsync script regularly copying over the first disk to the second? Or do you have something more apt to suggest?
Thanks for all your detailed answers. Seems the story resolved itself in a quite curious manner. The lab already has a "sysadmin", e. g. a guy who openly claims to be "no computer specialist, but my machines are running anyway, better than the ones built by the pros". I asked him if he could fill me in on some details, like what should the IP address of the server be, netmask, gateway, dns, so that I could integrate it into his network. I planned to first make a "dummy" server with my laptop just to do some testing, ping around, etcetera. The following surrealistic dialogue followed:
- "You know, I can't really let you know this, this is a very special network."
- "Yes, but you asked me to install a server in your network. If you want me to do that, I have to know some network specifications. For example, will the machine be statically configured, or do you plan to handle it with DHCP and a fixed address based on the MAC address?"
- "This is neither DHCP nor static, you know, we have an internal network." (!)
- "So you can't tell me your network specs, if I get you right. You know, when you ask a plumber to install a bathtub or a jacuzzi, you ought to tell him at least where your bathroom is, and where he can find the water tap."
- "I only asked for a server. I don't know why you have to know all this."
And so on. In the end, I decided not to bother and just left.
:o)
Niki