Hi all
最近mdadm有更新,更新信息里面写道, It is recommended that users remake their initramfs images they boot from after installing this update and then reboot their machine to verify that the new mdadm package does not prevent proper booting of their computer. For safety sake, it's possible to create a totally new initramfs, modify your boot loader configuration to add a test boot instance that uses the new initramfs image as the initrd, and then boot to that test image before updating their known working initramfs images. This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts. In order to fully test this update, users need to not only install the package, but also rebuild their initramfs images using dracut and then reboot their machine to test that the newly generated initramfs images still work properly on reboot (this obviously only applies to systems that have their root partition on an md handled raid device). This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts.
我还没有尝试过remake initramfs,不知是否有风险。 另外,mdadm是不是raid相关的软件。我不用raid是不是可以不去更新mdadm, 甚至可以删除相关软件?
alick
其实没什么风险的……另外经过个人检验不生成 ramdisk 也可以的……
注意现在需要用 dracut 生成 ramdisk,而不是原先的 mkinitrd 命令。
所谓的 ramdisk 就是 /boot 分区里的 initramfs 开头的一系列文件,每个内核 vmlinuz 有自己的 initramfs 对应。
如果要重建当前内核的 ramdisk 的话,参考使用如下命令:
mv initramfs-$(uname -r).img initramfs-$(uname -r).img.bak // 首先备份 dracut initramfs-$(uname -r).img $(uname -r) //然后创建新的
2010/12/11 alick alick9188@gmail.com:
Hi all
最近mdadm有更新,更新信息里面写道, It is recommended that users remake their initramfs images they boot from after installing this update and then reboot their machine to verify that the new mdadm package does not prevent proper booting of their computer. For safety sake, it's possible to create a totally new initramfs, modify your boot loader configuration to add a test boot instance that uses the new initramfs image as the initrd, and then boot to that test image before updating their known working initramfs images. This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts. In order to fully test this update, users need to not only install the package, but also rebuild their initramfs images using dracut and then reboot their machine to test that the newly generated initramfs images still work properly on reboot (this obviously only applies to systems that have their root partition on an md handled raid device). This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts.
我还没有尝试过remake initramfs,不知是否有风险。 另外,mdadm是不是raid相关的软件。我不用raid是不是可以不去更新mdadm, 甚至可以删除相关软件?
alick _______________________________________________ Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
敢问dracut 和以前的mkinird的区别? 为什么现在必须用dracut了? 多谢
在 2010年12月13日 上午11:34,Tommy He lovenemesis@fedoraproject.org 写道:
其实没什么风险的……另外经过个人检验不生成 ramdisk 也可以的……
注意现在需要用 dracut 生成 ramdisk,而不是原先的 mkinitrd 命令。
所谓的 ramdisk 就是 /boot 分区里的 initramfs 开头的一系列文件,每个内核 vmlinuz 有自己的 initramfs 对应。
如果要重建当前内核的 ramdisk 的话,参考使用如下命令:
mv initramfs-$(uname -r).img initramfs-$(uname -r).img.bak // 首先备份 dracut initramfs-$(uname -r).img $(uname -r) //然后创建新的
2010/12/11 alick alick9188@gmail.com:
Hi all
最近mdadm有更新,更新信息里面写道, It is recommended that users remake their initramfs images they boot from after installing this update and then reboot their machine to verify that the new mdadm package does not prevent proper booting of their computer. For safety sake, it's possible to create a totally new initramfs, modify your boot loader configuration to add a test boot instance that uses the new initramfs image as the initrd, and then boot to that test image before updating their known working initramfs images. This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts. In order to fully test this update, users need to not only install the package, but also rebuild their initramfs images using dracut and then reboot their machine to test that the newly generated initramfs images still work properly on reboot (this obviously only applies to systems that have their root partition on an md handled raid device). This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts.
我还没有尝试过remake initramfs,不知是否有风险。 另外,mdadm是不是raid相关的软件。我不用raid是不是可以不去更新mdadm, 甚至可以删除相关软件?
alick _______________________________________________ Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
-- Take a Deep Breath out of Windows
https://fedoraproject.org/wiki/User:Lovenemesis _______________________________________________ Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
据说 dracut 做出来的 initrd 开机可以快点。
http://fedoraproject.org/wiki/Dracut http://fedoraproject.org/wiki/Dracut Fedora && Debian User, former Ubuntu User My Page: http://www.liangsuilong.info Fedora Project Contributor -- Packager && Ambassador https://fedoraproject.org/wiki/User:Liangsuilong
2010/12/13 shaoning shaoning.fan@gmail.com
敢问dracut 和以前的mkinird的区别? 为什么现在必须用dracut了? 多谢
在 2010年12月13日 上午11:34,Tommy He lovenemesis@fedoraproject.org 写道:
其实没什么风险的……另外经过个人检验不生成 ramdisk 也可以的……
注意现在需要用 dracut 生成 ramdisk,而不是原先的 mkinitrd 命令。
所谓的 ramdisk 就是 /boot 分区里的 initramfs 开头的一系列文件,每个内核 vmlinuz 有自己的 initramfs
对应。
如果要重建当前内核的 ramdisk 的话,参考使用如下命令:
mv initramfs-$(uname -r).img initramfs-$(uname -r).img.bak // 首先备份 dracut initramfs-$(uname -r).img $(uname -r) //然后创建新的
2010/12/11 alick alick9188@gmail.com:
Hi all
最近mdadm有更新,更新信息里面写道, It is recommended that users remake their initramfs images they boot from after installing this update and then reboot their machine to verify that the new mdadm package does not prevent proper booting of their computer. For safety sake, it's possible to create a totally new initramfs, modify your boot loader configuration to add a test boot instance that uses the new initramfs image as the initrd, and then boot to that test image before updating their known working initramfs images. This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts. In order to fully test this update, users need to not only install the package, but also rebuild their initramfs images using dracut and then reboot their machine to test that the newly generated initramfs images still work properly on reboot (this obviously only applies to systems that have their root partition on an md handled raid device). This update brings mdadm to the latest upstream git repo plus a number of specific bug fixes. It addresses far more issues than the short bug list here depicts.
我还没有尝试过remake initramfs,不知是否有风险。 另外,mdadm是不是raid相关的软件。我不用raid是不是可以不去更新mdadm, 甚至可以删除相关软件?
alick _______________________________________________ Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
-- Take a Deep Breath out of Windows
https://fedoraproject.org/wiki/User:Lovenemesis _______________________________________________ Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
Chinese mailing list Chinese at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/chinese
chinese@lists.fedoraproject.org