<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Mark McLoughlin wrote:
<blockquote cite="mid1161957652.31200.18.camel@blaa" type="cite">
<pre wrap="">On Fri, 2006-10-27 at 15:38 +0200, Tim Lauridsen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Mark McLoughlin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Fri, 2006-10-27 at 14:18 +0200, Tim Lauridsen wrote:
</pre>
<blockquote type="cite">
<pre wrap=""># Core has lower priority than Updates, so packages from Updates cant
# overwrite packages from Core.
</pre>
</blockquote>
<pre wrap=""> Am I being stupid or does this sound backwards? If Core has lower
priority than Updates, shouldn't packages from Updates overwrite
packages from Core?
</pre>
</blockquote>
<pre wrap="">It might sound a little backwards, but it is the same with
cpu priorities in a multitasking environment
jobs with lower priority comes before job with higher priority. (lower
is better )
</pre>
</blockquote>
<pre wrap=""><!---->
Right ... but, at a guess, that's because some crufty old UNIX hacker
decades ago decided it would be nice[1] if the highest priority was
zero.
Maybe we're intending this to be some sort of selection process for
kernel hackers? "If you think this makes sense, *you* *too* could hack
the kernel!"
:-)
Cheers,
Mark.
[1] - yes, the pun is intended ...
_______________________________________________
Yum-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Yum-devel@linux.duke.edu">Yum-devel@linux.duke.edu</a>
<a class="moz-txt-link-freetext" href="https://lists.dulug.duke.edu/mailman/listinfo/yum-devel">https://lists.dulug.duke.edu/mailman/listinfo/yum-devel</a>
</pre>
</blockquote>
<span class="moz-smiley-s5"><span> :-D </span></span><br>
<br>
Tim<br>
</body>
</html>