On Wed, 22 Mar 2006 20:36:21 +0100, Rafael Sorto <[EMAIL PROTECTED]> wrote:
> On 3/22/06, Aaron Griffin <[EMAIL PROTECTED]> wrote: >> >> 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 What about just (sed?) put the module into rc.conf and post a msg about having done that on install? This is probably what someone might call a 'hack' though, but it should be safe right? and if this became common then one might be closer to the goal of being able to just set up a machine, update it and leave it and get everything working. ofcourse if this is the kinda thing which might fsck the rc.conf because of di- fferent locales or whatever then i suppose we would want to leave it alone. then again *IF* it did fsck the rc.conf it will 99% sure just add weird characters to the left and right of new_module_name and then a message on install saying something like: "blabla has been modularized, you now need to load it on bootup. We have added it to yor rc.conf but because of different locales this might not have worked flawlessly, please check your rc.conf to be sure." and then checking to see if it were there and going "ahh, then that's done!" would be much nicer than having to add the module yourself. It's just going that extra mile to please everyone that makes up that pleasant environment. ofcourse it's easy for me to say; i'm lazy sometimes too. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
