blob: b6d50e05d601207a20f46061a2c4e068f651a8ea (
plain)
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Issues with dracut
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Issues%20with%20dracut&In-Reply-To=%3Cop.v83fegj0n7mcit%40hodgins.homeip.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011805.html">
<LINK REL="Next" HREF="011709.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Issues with dracut</H1>
<B>David W. Hodgins</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Issues%20with%20dracut&In-Reply-To=%3Cop.v83fegj0n7mcit%40hodgins.homeip.net%3E"
TITLE="[Mageia-dev] Issues with dracut">davidwhodgins at gmail.com
</A><BR>
<I>Fri Feb 3 09:04:54 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011805.html">[Mageia-dev] Adding a new license to rpmlint
</A></li>
<LI>Next message: <A HREF="011709.html">[Mageia-dev] Issues with dracut
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11703">[ date ]</a>
<a href="thread.html#11703">[ thread ]</a>
<a href="subject.html#11703">[ subject ]</a>
<a href="author.html#11703">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, 17 Jan 2012 07:22:30 -0500, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
><i> Are things working OK for you now with dracut or is it still busted?
</I>
Just to clarify why I think the problem is happening on single
core systems.
On a multi-core system, the bash and udevd processes will be
running on different cores.
When the script executes the udev settle command, it continues
to execute, so the loop checking to see if udev is done finds
it isn't, so it then looks for/runs the initqueue jobs.
On a single core system, the bash script waits for the settle
command to finish, so then finds it's done, and exits without
even trying to run the initqueue jobs.
The patch in my prior message is effectively changing the script
from "udev done or jobs done" to "udev done and jobs done".
Regards, Dave Hodgins
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011805.html">[Mageia-dev] Adding a new license to rpmlint
</A></li>
<LI>Next message: <A HREF="011709.html">[Mageia-dev] Issues with dracut
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11703">[ date ]</a>
<a href="thread.html#11703">[ thread ]</a>
<a href="subject.html#11703">[ subject ]</a>
<a href="author.html#11703">[ 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>
|
