changing root pbuttword with Knoppix 930

Unruh No no, I know it's not a HD issue. But we have gigs of data spread over 5 PC's, including this Web server in the DMZ, so I was able to convince the beancounters that we need a seperate fileserver inside the protected LAN and not shared with a Web server that's accessable by the 'net. We don't have any place to put that data until those HD's get here.

Redundant machines, yep, indeed! Would be nice. =)

Fortunately this machine, in addition to having stored files that ARE at risk, it's just running a Web server (and ImageMagick to convert image files). Our DB and main Web server are on different machines in a hosted server farm off-site. This server in question is only for one particular vendor to be able to download ImageMagicked files for production. That's it. But, it's important enough that without it running, no production is run, and we lose money.

a. Take it off line (the best thing to do, I fully agree!) = lost money. or b. Keep it online, continue generating revenue for a cpl days and at worst, lose a few gigs of old data that won't kill us, just be an annoyance, and MAYBE have the vendor download interrupted.

Choice a. is a gaurenteed (sp) loss of money, choice b. is a MAYBE loss. We went with b.

See above, I am going to be rebuilding the Web server as well as a new machine to serve as a safe file server inaccessable from the 'Net. In the meantime, weighing the pros and cons, we've decided the definite loss of being off-line is worse than the maybe loss of online and something additional bad happening.

This this were our main server, I'd pull it off in a second! But like I said, our main Web server, our database, all the main workings of the co. are on different managed servers. This is a small, 1-task only server with little more they can do to it than just shut it down themselves.

'fairnuff. I'm just saying, there's nothing else inetc-pbuttwd except root that's important. No one else is at risk.

Thanks for replying!