Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Luciano Subject: Re: Backing up cygwin Date: Sat, 12 Jul 2003 11:23:25 +0000 (UTC) Lines: 26 Message-ID: References: <20030711220902 DOT GA20839 AT redhat DOT com> <20030711231007 DOT GA3876 AT redhat DOT com> <20030712010238 DOT GC5134 AT redhat DOT com> X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Xnews/5.04.25 >>Now, why not store these things in goold old fuzzy and warm text >>files? Registry sucks, and it sucks badly. >You seem to be missing the point that you shouldn't be worrying >about where such things as the mount table are stored. Just use >'mount -m'. No, I guess you miss my point. Especially considering I didn't make it quite clear. I have a backup system in place. It knows which files to copy, where they are and where to put them back when needed. That involves many .ini files, so I can restore programs and don't have to reconfigure them. The use of 'mount -m' is no big deal, but it's not so easy (automatic) to handle as merely hauling files. > It's really just sheer coincidence that cygwin works at all. > It's real job is just to royally piss people off with little > things like storing values in the registry and making it hard to > use network shares over ssh. What??? There are obstacles in the way of using network shares over ssh too??? Damn it, you can't do anything right, can you? -- Luciano ES Santos, SP - Brasil -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/