35 messages in com.redhat.fedora-listRE: Problem booting after Yum update ...
FromSent OnAttachments
Min ChenNov 27, 2005 4:00 pm 
David G. Miller (aka DaveAtFraud)Nov 27, 2005 5:28 pm 
Michael A. PetersNov 27, 2005 6:41 pm 
Min ChenNov 27, 2005 7:04 pm 
Min ChenNov 27, 2005 7:15 pm 
Rey CruzNov 27, 2005 7:31 pm 
Sam VarshavchikNov 27, 2005 7:42 pm 
Neil CherryNov 27, 2005 8:58 pm 
Min ChenNov 27, 2005 9:10 pm 
David G. Miller (aka DaveAtFraud)Nov 27, 2005 9:26 pm 
Min ChenNov 27, 2005 9:46 pm 
Michael A. PetersNov 28, 2005 12:17 am 
David G. Miller (aka DaveAtFraud)Nov 28, 2005 4:53 am 
John SummerfiedNov 28, 2005 5:35 am 
Charles E "Rick" Taylor IVNov 28, 2005 6:41 am 
Hans MüllerNov 28, 2005 8:46 am 
Neil CherryNov 28, 2005 5:10 pm 
John SummerfiedNov 28, 2005 9:36 pm 
Min ChenDec 1, 2005 3:32 pm 
David G. Miller (aka DaveAtFraud)Dec 1, 2005 6:16 pm 
Min ChenDec 1, 2005 9:25 pm 
David G. Miller (aka DaveAtFraud)Dec 1, 2005 10:04 pm 
Tony FosterDec 1, 2005 11:09 pm 
Min ChenDec 3, 2005 10:36 pm 
Hans MüllerDec 4, 2005 12:49 am 
James WilkinsonDec 5, 2005 1:26 pm 
Tony FosterDec 5, 2005 4:15 pm 
TimDec 6, 2005 4:10 am 
James WilkinsonDec 8, 2005 12:20 am 
TimDec 8, 2005 7:59 am 
Mike McCartyDec 8, 2005 8:37 am 
Tony FosterDec 8, 2005 9:20 am 
James WilkinsonDec 8, 2005 9:37 am 
Mike McCartyDec 8, 2005 11:03 am 
TimDec 9, 2005 2:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: Problem booting after Yum update of FC4Actions...
From:Tony Foster (Tony@surewest.net)
Date:Dec 8, 2005 9:20:42 am
List:com.redhat.fedora-list

I tend to agree that more then a couple of minutes would be abusive. I was not planning on trying that test model. I can understand some value in pointing out that this could be abusive and easily traced back to the sender. So for others viewing this string the discussion was necessary. Bottom line if you are using others equipment to trouble shoot your problems make sure you have agreement/permission.

Status of the original problem I reinstalled the FC4 core system on a clean disk AGAIN. I instaalled the desktop environment instead of the server environment and ran a find immediately. The issue with find and the /proc directory tree was present.

I updated the system with Yum and in this case it booted fine. Kernel id 2.6.11-1.1644SMP So I reran find and now I get the error in the /sys directory tree so I still do not have a kernel that is robust. Does anyone have a kernel ID that is known to resolve this issue. I can run find from / as long as I exclude the /sys directory tree.

"Any sufficiently advanced technology is virtually indistinguishable from magic." (Arthur C. Clarke)