diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-February/011977.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-February/011977.html | 146 |
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-February/011977.html b/zarb-ml/mageia-dev/2012-February/011977.html new file mode 100644 index 000000000..b3efe599f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/011977.html @@ -0,0 +1,146 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] New Dracut: Please test + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20Dracut%3A%20Please%20test&In-Reply-To=%3C4F3B8448.9080905%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011972.html"> + <LINK REL="Next" HREF="011980.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] New Dracut: Please test</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20Dracut%3A%20Please%20test&In-Reply-To=%3C4F3B8448.9080905%40mageia.org%3E" + TITLE="[Mageia-dev] New Dracut: Please test">tmb at mageia.org + </A><BR> + <I>Wed Feb 15 11:09:12 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011972.html">[Mageia-dev] New Dracut: Please test +</A></li> + <LI>Next message: <A HREF="011980.html">[Mageia-dev] New Dracut: Please test +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11977">[ date ]</a> + <a href="thread.html#11977">[ thread ]</a> + <a href="subject.html#11977">[ subject ]</a> + <a href="author.html#11977">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Colin Guthrie skrev 15.2.2012 11:35: +><i> 'Twas brillig, and David W. Hodgins at 14/02/12 23:21 did gyre and gimble: +</I>>><i> On Tue, 14 Feb 2012 10:55:17 -0500, Colin Guthrie +</I>>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: +</I>>><i> +</I>>>><i> Can everyone please test the new dracut please? Especially those of you +</I>>><i> +</I>>><i> I'll test it shortly. I think there is a slight problem when dracut gets +</I>>><i> updated at the same time as the kernel, udev, or anything else that is +</I>>><i> going to get installed in the initramfs. +</I>>><i> +</I>>><i> Rather then triggering the running of dracut when the kernel gets +</I>>><i> installed, +</I>>><i> I think it would be better to have something that runs at the end of urpmi +</I>>><i> or MageiaUpdate, that check to see if dracut or anything in the existing +</I>>><i> initramfs has been updated, and if so, then run dracut. +</I> +The best I can do from kernel pov is to change %post into %posttrans so +creating initrd would happend at end of install transaction + +><i> +</I>><i> Strangely enough I was thinking vaguely along the same lines. My issue +</I>><i> was udev specifically. Sadly working out exactly when to rebuild the +</I>><i> initramfs is pretty tricky, e.g. if lvm or dm tools are updated do we +</I>><i> really need them in this particular setup's initramfs? Should we rebuild +</I>><i> anyway (it should be safe) and accept the unnecessary work in those +</I>><i> cases? Might be a reasonable thing to do... +</I>><i> +</I> +"it should be safe" - famous last words... :) + +><i> I guess then a filetrigger could be written that checks for files +</I>><i> certain locations and triggers an initrd rebuild. For the kernel it +</I>><i> would only build one, but for udev, dm, lvm etc. it would rebuild all of +</I>><i> them... +</I>><i> +</I> +We should _never_ rebuild all initrds. +If/when one of the updated packaged has a critical systemcrashing bug, +we render the whole system unbootable. + +><i> Might confuse some people however and create cases working systems are +</I>><i> hosed unnecessarily, and I'm not sure how much of real, practical +</I>><i> problem it is to simply have a slightly outdated tools in the initram +</I>><i> fs? Perhaps we just need to get ordering better on updates such that +</I>><i> udev, lvm, dm etc. are all ordered before kernel during updates? Maybe +</I>><i> that will solve 95% of the issues? +</I>><i> +</I> +That could be an option of we can get the tools to differentiate between +high-priority (glibc/rpm/urpm*/...), priority (udev/lvm/dm/...) and the +rest... + +Otoh, most of the issues we see now is Cauldron -> Cauldron updates. +in a stable release many of the packages wont change. + +Of course that still leaves distro upgrades, but maybe that can be +handled in the installer or by adding versionated conflicts to kernel +to help urpmi figure out the order to update... + +-- +Thomas + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011972.html">[Mageia-dev] New Dracut: Please test +</A></li> + <LI>Next message: <A HREF="011980.html">[Mageia-dev] New Dracut: Please test +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11977">[ date ]</a> + <a href="thread.html#11977">[ thread ]</a> + <a href="subject.html#11977">[ subject ]</a> + <a href="author.html#11977">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |