[arch-dev-public] [signoff] udev 118-4

[Tobias Powalowski]

Am Sonntag, 9. März 2008 schrieb Tobias Powalowski:
> Am Sonntag, 9. März 2008 schrieb Aaron Griffin:
> > On Sun, Mar 9, 2008 at 1:33 AM, Tobias Powalowski <t.powa at gmx.de> wrote:
> > > Am Samstag, 8. März 2008 schrieb Aaron Griffin:
> > > > On Sat, Mar 8, 2008 at 4:24 PM, Daniel Isenmann
> > > > <daniel.isenmann at gmx.de>
> > >
> > >  wrote:
> > >  > > On Sat, 8 Mar 2008 15:37:24 -0600 "Aaron Griffin"
> > >
> > >  <aaronmgriffin at gmail.com> wrote:
> > >  > >  > c) The *only* thing that is appropriate is to autoblacklist
> > >  > >  > them via modprobe rules.. Doing it the previous way is absolute
> > >  > >  > crap.
> > >  > >
> > >  > >  I have done this and it works. I manually add the nvidiafb to
> > >  > >  modprobe.conf, but that's not a solution, just a workaround for
> > >  > > me. It should be placed in a modprobe.d/ file instead, if we will
> > >  > > do it.
> > >  >
> > >  > Right, the reason I bring this up is that apparently some people are
> > >  > against using a modprobe.d file for this.
> > >  >
> > >  > Funny question though, if we make a
> > >  > /etc/modprobe.d/framebuffer_blacklist file, or something, what
> > >  > package does it belong to? I almost think it should be part of the
> > >  > kernel, but that seems weird.
> > >
> > >  It should belong to udev because udev loads it, kernel doesn't make
> > > sense.
> >
> > Er? No. Modprobe loads it. udev calls a script that calls modprobe. We
> > are not talking about where the CURRENT frambuffer blacklist exists,
> > because I'm sure we all agree it is inefficient and broken. I'm
> > talking about where it SHOULD be.
>
> A file which belongs to a package that will affect also an other is bad.
> Placing it in kernel package is bad because it might interfere with an
> other kernel package.
> Placing the file in udev affects all kernels the same and udev is our
> primary module loader for now.
>
> greetings
> tpowa

Just for your information, i have a full splitup rule udev here now.

about blacklisting, problem with modprobe.d/frambuffer would be if a 
modprobe.conf is present it ignores the modprobe.d/ directory completly :(

greetings
tpowa

-- 
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tpowa at archlinux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://archlinux.org/pipermail/arch-dev-public/attachments/20080309/bef4af1c/attachment.pgp>