<br><br><div><span class="gmail_quote">On 7/12/07, <b class="gmail_sendername">Nic James Ferrier</b> <<a href="mailto:nferrier@tapsellferrier.co.uk">nferrier@tapsellferrier.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Andrew Guard" <<a href="mailto:andrew07@andrewguard.com">andrew07@andrewguard.com</a>> writes:<br><br>> Alright I have no idea how this going to be done but believe it could be done.<br>><br>> First of all it must have a day to day zero maintenance system. I am
<br>> just lazy and do not need the phone calls everyday.<br>><br>> They would like to be able to access files on a "server". Over a LAN<br>> and WAN, easily. They don't mind if there access files over WAN is via
<br>> web service. But gain access to files LAN should be working accessible<br>> with Windows.<br>><br>> So got them to agree to these sort of idea's then found out what<br>> "server" set up was.
<br>><br>> Pentium 2<br>> 64M Ram<br>><br>> So can it be done, or it just to tight?<br><br>Bit small.<br><br>I'd try lighttpd/webdav.</blockquote><div><br>As soon as you do *anything* CPU intensive, such as SSL access, SSH access, virtual hosts, serving more than a few users at a time, you're going to start swapping like nobody's business. This is going to dog any noticeable performance even worse than the slow CPU will. Like handcarving your own doorknobs, it's usually easier and faster just to buy them or even salvage them.
<br></div></div>