On Fri, 2006-09-22 at 08:40 -0400, William L. Maltby wrote: > On Thu, 2006-09-21 at 23:17 -0400, Ted Miller wrote: > > William L. Maltby wrote: > > > On Sun, 2006-09-17 at 22:22 -0400, Ted Miller wrote: > > >>William L. Maltby wrote: > > >>>On Sun, 2006-09-17 at 09:27 -0400, Ted Miller wrote: > > >>> > > >>>><snip> > This probably means you were not in the right directory level after you > did "cd xxxx". Maybe too "high" or "low" in the tree. To see where you > should have been, do the uncompress thing on one of the original CentOS > installed archives and pipe output to cpio using -itc (add a v if more > info is desired). OOPS! Another possibility is the form of the find? I'm not sure it would have an effect, but since I'm not *that* intimate with the booting details (its screwed me a lot, but I've not been able to screw it ;-).. "find ." is not the same as "find *" or find {x,y,z} When the archive is extracted, relative path vs. absolute path considerations may come into play. When you do the extract with the "cpio -ict", if the patches begin with "./", then "find ." is good. If they do not have a leading ".", that may be the problem. > <snip> -- Bill _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos