Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.

https://bugzilla.redhat.com/show_bug.cgi?id=815147

--- Comment #3 from Josh Boyer jwboyer@redhat.com 2012-05-02 07:05:06 EDT --- (In reply to comment #2)

(In reply to comment #1)

dist-oss.conf is essentially empty? Really?

install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-pcm-oss && /sbin/modprobe snd-seq-device && /sbin/modprobe snd-seq-oss

Yes, that line exists however it is installed as commented out. It does nothing unless someone manually edits it. Do you have a package in Fedora that requires it?

dist-alsa.oss installs sequencer support, so you're right, maybe no one in this universe wants it:

install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-seq

snd_pcm is still loaded in f17. snd-seq is still built and can still be loaded. Do you have a package that requires it?

You were right all the way through. Who needs OSS and sequencer support nowadays? All Fedora applications use ALSA/Pulse, so old and proprietary applications can just go the way of dodo. Thank you very much.

I can't comment on proprietary applications much. If they need OSS and sequencer support, perhaps whomever is packaging them can include the modprobe files.

I, for one, can pull these files from RPMs. With an attitude like this I don't think this bugs needs any positive resolution.

I really wasn't gving an "attitude". I asked if you were having a problem and you decided to become rather hostile. If there is something in Fedora broken by not shipping those files, we can possibly move them to another package. Kmod itself doesn't need to ship them.