On Wed, 23 Aug 2006 22:15:17 +0200, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:

On 8/23/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> Yes, of course. The Task can just 'source' gobohide.conf and append
> the extra entries to the operation. I can do that later, or you can
> make your commits to the package, in the same way as the kernel
> modules are handled in the UserDefinedModules array at BootOptions /
> BootScripts/BootUp.
>
My idea was that all directories should be selected from the .conf file,
not just the extras, to ensure full customability (is that a word? :) )

I don't see that as an advantage, as there's always a static "base"
which is going to be hidden.
Are there really a static base? What about those users that don't want, for example, /proc hidden? There could exist such a user and is it a bad thing to have all directories customizable?

If one don't want some entry from that
base to be hidden, just take it out from the task.

Isn't that's against the idea of having a conf file? And then again, one have to manually edit the task every time one updates GoboHide.

--
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to