Re: Linuxconf not losing info.
On Tue, 2 Jun 1998, Shaya Potter wrote: Sorry for not responding directly, I only get debian-devel-digest, so I can only respond to what I catch. I believe linuxconf will version every change that it makes, i.e. if you make changes w/ linuxconf and see that it didn't work, you can go back to your previous configuration or any one of many previous configurations, this will probably work if you edited it outside of linuxconf, you then edited the file manually, and then went into linuxconf, somehow or another linuxconf messed up the file (though when I was playing with it last year, it couldn't grok our dns setup, and just complained, didn't mess with it), you should theoreticly be able to go back to the version you modified by hand, because linuxconf should have saved it before modifying the file. good. i like the sound of that. does it use RCS or similar to store the previous versions? if not, how hard would it be to make it do so? craig -- craig sanders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linuxconf not losing info.
On Wed, 3 Jun 1998, Shaya Potter wrote: does it use RCS or similar to store the previous versions? if not, how hard would it be to make it do so? don't know, as it's been a year since I've played with it on debian. However, that was one of the big things I requested, and from reading the linuxconf web pages, it seems he has added it, though I'm not sure how it does it. Why RCS? if it uses it's own system of just versioning the files, wouldn't that be good enough as well? if it works, then yeah it's fine. however, why re-invent a perfectly good wheel which happens to have lots of compatible utilities? e.g. various diff utils like rcsdiff and tkdiff. i prefer incremental, evolutionary growth built upon existing tools. sometimes (rarely) you have to throw out the old stuff and start afresh, but usually not. it's unfortunately very common for wheels to be re-invented simply because people don't know that they already exist or how to use them, or it never occurs to them that a tool which is well-known for one particular use (e.g. make) is also very useful for another (e.g. building and managing config files instead of compiling programs) craig -- craig sanders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
