On 3/22/06, Judd Vinet <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 22, 2006 at 03:12:33PM +0100, Jaroslaw Swierczynski wrote:
> > I've just installed the new kernel from [testing] and in my opinion
> > the capability module should be loaded by default, no matter what. I
> > think there are very few people who need something else instead and
> > just having it as module should be enough for them, they will know
> > what to do. For everyone else - everything should be as before, this
> > change should go unnoticed.
>
> Hmmm... How about this... we could add a /etc/conf.d/kernel file. On
> bootup, rc.sysinit could read it and load the desired capability module
> based on a KERNEL_CAPABILITY setting or some such.
>
> Then no one needs to hack up rc scripts to override the default.
I really don't understand why it could not just go in the MODULES
array? Stick it in the default rc.conf and bam, done. Can anyone
give me a good reason (good, meaning, "I don't like that" doesn't
work) why that's bad?
We're now talking about hiding more and more of the init process
under-the-hood, which is fine for things that are typical (i.e.
mounting /sys and /proc), but when it comes to special purpose stuff
like the capabilities module (which I *know* I have no need for),
there's no need to abstract it away to all hell.
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
I totally agree with u , rc.conf its good enough
cheers
rdoggsv
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
