2009/11/29 Neal Becker <ndbecker2(a)gmail.com>:
> On Sunday 29 November 2009, Nicolas Chauvet wrote:
>> Thx for the suggestion, this message has been forwared on the "RPM
>> Fusion developers discussion list" for public audience.
>> Please answear there instead.(once subscribed).
>>
>> Few answears:
>> - setsebool will not be needed anymore (exept for the nvidia-smi
>> binary on x86 which is only used for tesla hardware).
>> - Creating a separate initramfs is probably the way to go. But I
>> wonder if that could be implemented as a dracut plugin instead, and
>> then generalised to others alternate proprietary drivers.
>> - There is improvements needed for a new packaging scheme that will
>> split installation and usage for proprietary driver. (it doesn't mean
>> the driver is installed that the driver is meant to be used).
>>
>> 2009/11/28 Walter Francis <wally(a)theblackmoor.net>:
>> > Bleh, just discovered that redhat-lsb is not installed in all paths, so
>> > probably better to use /etc/rpm/macros.dist to get the release number...
>> > Sorry for the spam, just didn't want to leave you with something that
>> > would be broken on Live installs.
>> >
>> > BTW, someone mentioned that the sebool stuff is probably better done
>> > outside of a postinstall script, but I'm no spec writer so I leave that
>> > up to you. ;-) Just suggestions here on what would be very nice to have
>> > done, how it's actually done is better decided by you. :) Unless I
find
>> > any other glaring mistakes I'll stop spamming you, hope I haven't
been a
>> > bother.
>> >
>> > #!/bin/sh
>> >
>> > if getsebool allow_execstack | grep -q off; then
>> > setsebool -P allow_execstack on
>> > fi
>> >
>> > # create new initrd/initramfs if necessary
>> > if lsmod | grep -q nouveau; then
>> > release=$(awk '/^%fedora/{print$2}' /etc/rpm/macros.dist)
>> > if [ $release -gt 11 ]; then
>> > # use new-kernel-pkg to create the initramfs and create a
>> > new boot entry (see below)
>> > /sbin/new-kernel-pkg --mkinitrd --dracut
>> > --initrdfile=/boot/initramfs-`uname -r`-nvidia.img
>> > --banner="Fedora NVidia" --make-default --install `uname -r`
>> > fi
>> > if [ $release -lt 12 ]; then
>> > # non-dracut, use initrd filename, no --dracut
>> > /sbin/new-kernel-pkg --mkinitrd
>> > --initrdfile=/boot/initrd-`uname -r`-nvidia.img
>> > --banner="Fedora NVidia" --make-default --install `uname -r`
>> > fi
>> > fi
>> >
>> > --
>> > Walter Francis
>> >
>> > khayts.us
>> >
theblackmoor.net
>> >
unlimitedphoto.com
>>
>
> Isn't adding rdblacklist=nouveau to grub.conf less intrusive?
not, the nouveau kms remains loaded and leave things in the unsafe random
side.
That might work for your hardware/usage , it will not work for others...
So that's even do not worth to be documented.
Nicolas (kwizart)
BTW all, my original email to Kwizart was just basically a suggestion on how
it would be nice to simplify things, with an example of "a way". It wasn't
to
suggest "the way" to do it. Sounds like you guys have thought it out better
than I have, in terms of a separate selinux package to handle the nvidia kmod
specific rules, etc. Just look forward to our end users being able to
hopefully just do two steps: 1) install rpmfusion, 2) yum install
[a]kmod-nvidia[-PAE].
--
Walter Francis
khayts.us