you have to edit the file manually from sysconfig to activate it. they didn't put a link into the yast module. got that a few hours ago anyway... On 2002.09.29 17:33 paul kaiser wrote:

suse made a major transition from verion 7.3 to 8.0. most configuration was done within the /etc/rc.config file. and yast worked very well with that centralized file.

however, with 8.0, suse decentralized all its configuration files and put them in /etc/sysconfig. you will find personal-firewall and SuSEfirewall2 in this directory along with a lot of other significant configuration files. yast does allow you to interact with all the configuration files at one time using the yast --> system --> sysconfig editor. this is somewhat of a help, but there is not a lot of information presented while you are in the editor. personally, i prefer just editing the files in /etc/sysconfig using vi!

one suggestion to save yourself some frustration later on. when you have a configuration file set up the way you like it, make a backup copy with a unique suffix -- your initials or something else you will remember. yast has the annoying feature of running SuSEconfig when it terminates, which regenerates many configuration files based on its configuration scripts. it does recognize some changes to configuration files -- but not all! after yast has done its magic, i usually use "diff" to compare important configuration files with my backup copy -- if different, then it is easy to replace the updated yast file with my preferred customized configuration.

--- Susan Buczak <sbuczak2@comcast.net> wrote:

...

well it's in there for sure but all it ever says is 'Not initiated'.

I checked the run levels already, still all it ever says is 'not initiated'.

Suse 8.0 is kind of yasted out or am I missing something? The yast doesn't allow me to make custom configurations to my config files... and if there is some secret it's not in the book... I need to configure

...

this thing to my users and needs and yast wants to control everything... unfortunately it overlooks a lot of things... like hosts allow and access.conf just to get started...

someone else told me they did this yast deal with 8.0 that it was normal prior to that... is it safe to pull the yast deal off till the machine

...

is configured properly does anyone know, have they tried that? I don't mind yast watching the system after I have it configured for my needs but till then it's been a real monster, absolutely impossible to deal with...

----------------------------------------------

On 2002.09.29 10:11 paul kaiser wrote:

...

the personal firewall basically shuts down most if not all incoming traffic to your system. it has a default configuration. it is usually started at system boot.

look carefully when you boot the system, personal firewall kicks in at runlevel 3. you do not activate it from the command prompt.

in yast, you should look under security for the category runlevel editor. this will show you your current settings for personal firewall,

...

when >it is started, etc.

...