1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
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>
|
