On Thursday 05 Jun 2003 3:44 pm, Tom Brinkman wrote: > On Thursday June 5 2003 05:43 am, Robin Turner wrote: > > rikona wrote: > > > Hello, > > > > > > In trying to restore things back to normal after opening, but > > > not doing anything in linuxconf, I found that linuxconf had set > > > up a set of iptable scriipts to build a firewall, and activated > > > it to block everything! > > > > > > I reconfigured (not with linuxconf) to restore shorewall, set > > > it up, and now I can see the net again. > > > > > > So - be careful - just *opening* and exiting linuxconf can > > > change your configuration. Alternatively, when you exit > > > linuxconf, make sure you DO NOT update the configuration. Be > > > aware that linuxconf may configure parts that you DID NOT > > > change if you do have it update the config. > > > > > > This is the way it seems from what happened - if this is not > > > correct, please let me know. > > > > I haven't encountered this particular problem, but it doesn't > > surprise me. > > > > Never use linuxconf. Don't even install it. It was a great boon > > back in the days when it was pretty much the only all-in-one > > graphical configuration tool, but it doesn't play nice. Anything > > you can't do with MCC, do by hand. > > > > Sir Robin > > There's been a discussion on the cooker list in just the past > few days about moving linuxconf to /contribs (ie, no longer > supported), or dropping it altogether. I agree with your > assessment of linuxconf Robin, and rikona's warning. Mandrake's > drake* tools are much more capable and safer to use.
I haven't used it on over a year. It gave me some unpleasant moments, too, so I avoid it. Anne
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
