> > > But isn't this only for firmware loaded by the kernel? It sounds like > > AJ is talking about something firmware-like that's loaded by an > > application. >
Correct, it's a codec for an embedded processor. > You're right. I'd probably stick non-kernel firmware and loadable > modules in /usr/lib somewhere. Since there's no execute bit needed to > be set, I wouldn't put them in RH's /usr/libexec > Oh pooh... I already did the mkdir -p /usr/libexec and everything.... now I'm going to have to rmdir. How could I be so naive? AJ ONeal
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
