Not enough info, so no point

[JD]

On 06/03/11 08:38, n2xssvv.g02gfr12930 wrote:
> On 06/03/2011 03:41 PM, Louis Lagendijk wrote:
>> On Fri, 2011-06-03 at 15:15 +0100, n2xssvv.g02gfr12930 wrote:
>>
>>> Currently nothing is attached to the SCSI controller. So I'm wondering
>>> if I actually remove it, the problem will disappear.
>>>
>> The probability is quite (not to say very) high that this will solve the
>> issue, yes. If not, I would run e memtest to see if you have memory
>> issues.
>>
>>> I'm fairly sure the Fedora 15 install is mostly up to date, as I
>>> installed direct from the Fedora repos, release and updates.
>> Mount the F15 on /mnt including the additional mount point, chroot /mnt
>> and you run yum update as suggested in the other mail. No meed to stop
>> This should be a riskless operation. It is actually also what a rescue
>> operation does, but in this case you can use the F14 network setup that
>> makes it even easier. I would hoever recommend removing the SCSI
>> controller first
>>
>> Louis
>>
> Thanks for that Louis, although I'm still nervous. The yum update needs
> to run under chroot without affecting the currently running system, and
> I'm not entirely sure how to do that. I suppose I'll have to do some
> harmless experiments to determine how.
>
>
A user process (such as yum), even with root privs,
CANNOT JUMP OUT OF THE BOUNDARIES OF IT'S ROOT,
NAMELY (for example) /mnt/f15

So there is no danger that yum executed within a chrooted environment
will affect the enclosing host's yum database (in this case F14).