On Thursday 05 Jun 2003 7:13 pm, JoeHill wrote:
> On Thu, 5 Jun 2003 09:44:51 -0500
>
> Tom Brinkman <[EMAIL PROTECTED]> uttered:
> > 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 alto
On Thu, 5 Jun 2003 09:44:51 -0500
Tom Brinkman <[EMAIL PROTECTED]> uttered:
> 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 Rob
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
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 bl
Hello Derek,
Thursday, June 5, 2003, 2:24:26 PM, you wrote:
DJ> edit /etc/sysconfig/network
That's what I did, as suggested here in another thread.
DJ> That is all linuxconf does.
U. except for all the other things it seemed to do that I
didn't tell it to do. :-)
--
Thank you,
rikon
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
