<br><br><div class="gmail_quote">2010/10/29 Bruno Wolff III <span dir="ltr"><<a href="mailto:bruno@wolff.to">bruno@wolff.to</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Oct 29, 2010 at 17:35:54 +0300,<br>
cornel panceac <<a href="mailto:cpanceac@gmail.com">cpanceac@gmail.com</a>> wrote:<br>
> > not yet, if possible i'll create a bug tomorrow. the behaviour is like<br>
> this: i boot rescue environment, maybe yum update the system to be rescued,<br>
> then reboot on the then reboot. ""Superblock etc" then immediately "file<br>
> system relabel is required". this happened several times today on a system<br>
> which was dvd upgraded from f13 to f14 rc1. the relabel doesn't show up when<br>
> i just rebooted the system.<br>
<br>
</div>There might be two problems. The superblock timestamp may have to do with<br>
timezone settings and how you have your bios clock set. If the rescue<br>
image and the normal image have different ideas about what the time of<br>
the bios clock means (say one assumes it is UTC and the other assumes it<br>
is localtime) I think you could see a symptom like this.<br>
<br>
For the update / selinux relabel issue, if you write to file systems<br>
with selinux disabled that is going to trigger needing a relabel.</blockquote><div><br>this happens without any writing (that i know about) occuring. just enter and exit rescue mode, with the partition(s) mounted rw.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> I think<br>
it is normal for updating stuff while using rescue mode to trigger a relabel,<br>
as if the policy of the rescue image weren't to match that of the installed<br>
system, when you did an update files could get incorrectly labelled.<br>
</blockquote></div><br><br clear="all"><br>