Package: oss-compat Severity: wishlist On Mon, Oct 02, 2006 at 12:38:49PM -0600, dann frazier wrote: > > > * Could the postinst do a modprobe snd instead of hardcoding > > > individual module names? I think this would avoid duplicating that > > > list of modules between the postinst and the oss-compat file and > > > should have the same affect. > > > > No, because that might gratuitously load snd on systems that didn't have any > > sound support. Duplicating the list is a minor issue compared to that. > > It shouldn't if you still check to see if snd is already loaded, e.g.: > > --- postinst.orig 2006-10-02 10:55:53.000000000 -0600 > +++ postinst 2006-10-02 10:56:32.000000000 -0600 > @@ -7,9 +7,7 @@ > Linux) > ln -sf /lib/oss-compat/linux /etc/modprobe.d/oss-compat > if lsmod | grep -q "^snd " ; then > - modprobe snd-seq-oss || true > - modprobe snd-mixer-oss || true > - modprobe snd-pcm-oss || true > + modprobe snd || true > fi > ;; > esac > > > Of course, if users aren't allowed to modify this file, the only issue > is the duplicate list of module names which is minor indeed. Thanks > for the response!
Good point. Let's make a bug out of it. =) -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
