On Fri, 2005-04-22 at 10:58 +0000, Kosta Todorovic wrote:
> It seems the /etc/nessus directory is empty.

Does nessus normally configure itself?  I thought it did not ship with a
working configuration, since it requires some SSL generation and to add
a user manually.

> I'm not entirely sure but it seems most of the package /etc/dirs are
> empty. For some reason default config files did not get copied over or
> stage2 emptied them. Unfortunately I cant seem to find why.

> I'm aware that that a filesystem overlay can be used and I have tried
> to do that but I must be doing something wrong.
> 
> I dont exactly understand the difference with:
> #livecd/overlay: /root/catalyst/overlay
> #livecd/root_overlay: /root/catalyst/overlay

livecd/overlay adds files outside the livecd loop.  This is where things
like the Handbook go.

livecd/root_overlay adds files inside the livecd loop.  This is where
files in /etc go and so on.

> Also, what exactly is supposed to be stored in /root/catalyst/overlay.
> Is it a directory? A text config file? Shrug.

It is an overlay.  It looks exactly like your filesystem that you want
overlaid over the root filesystem of your CD.  If you want to add a file
to /etc/nessus, then you need to make
a /root/catalyst/overlay/etc/nessus directory and stick your files in
it.

> Any suggestions would help. Or if anyone has successfully got Nessusd
> the config files would be really helpful.

USE="doc examples" emerge catalyst

This will give you the new example files
in /usr/share/doc/catalyst-1.1.9/examples, which are much more complete
in their documentation and explanations.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux