Hi
Any idea, why this snippet doesn't work? Plymouth still shows "Fedora 10" during bootup
--
%post
sed -i -e 's/Fedora/Foo/g' /etc/fedora-release /etc/issue
# Update initrd. Otherwise plymouth says "Fedora 10" instead of Foo
/sbin/mkinitrd -f /boot/initrd-2.6.27.5-117.fc10.i686.img 2.6.27.5-117.fc10.i686
---
Rahul
Rahul Sundaram (sundaram@fedoraproject.org) said:
Any idea, why this snippet doesn't work? Plymouth still shows "Fedora 10" during bootup
This is live, correct? Now that I think about it, the live initrd is 'special' - you'd need to remake that, not just use mkinitrd.
Bill
Bill Nottingham wrote:
Rahul Sundaram (sundaram@fedoraproject.org) said:
Any idea, why this snippet doesn't work? Plymouth still shows "Fedora 10" during bootup
This is live, correct? Now that I think about it, the live initrd is 'special' - you'd need to remake that, not just use mkinitrd.
Yes, it is a live cd. How do I remake it? Since, this is a potential trademark issue, I have been trying to fix this for the last couple of days. Any help is most appreciated.
Rahul
Rahul Sundaram (sundaram@fedoraproject.org) said:
This is live, correct? Now that I think about it, the live initrd is 'special' - you'd need to remake that, not just use mkinitrd.
Yes, it is a live cd. How do I remake it? Since, this is a potential trademark issue, I have been trying to fix this for the last couple of days. Any help is most appreciated.
Does using generic-release in your package set help? (Or replacing fedora-release with your own package.)
Bill
Bill Nottingham wrote:
Does using generic-release in your package set help? (Or replacing fedora-release with your own package.)
The problem is that, livna-release requires fedora-release directly instead of having a virtual dependency on system-release. rpmfusion release packages had the same problem and I reported and that got fixed. Meanwhile, I will see if I can workaround this issue.
Rahul