On Thu, 20 Sep 2001, Ross Macintyre wrote:
>Can anyone see any difficulties if I do this:
>Force the removal of glibc-2.2.2-10.i686.rpm and install the
>glibc-2.2.2-10.i386.rpm.
glibc is linked into virtually every program on your entire
system. Forcing its removal, will result in a system that is
almost totally non functional.
>The reason I want to do this is because I am in the process of making a
>lab of 100 odd Linux7.1 machines and I am using ghost to intstall.
>I want all my machines to be basically the same and nearly having
>finished I find that the image I created does not go on some older
>machines. I am fairly sure this is because of glibc. The (386) kernel
>boots fine but it hangs at "freeing unused kernel memory" and on
>browsing the net I am pretty sure the fault is with init being
>dependent on glibc for an i686.
>What I want is all the machines to run the same software and puting on
>glibc-2.2.2-10.i386.rpm seems a sensible way to do it.
>Unless of course that are some pitfalls up ahead that i haven't thought
>of.
Upgrade with nodeps
rpm -Uvh --nodeps glibc-2.2.2-10.i386.rpm glibc-common-2.2.2-10.i386.rpm
The key to knowledge is not to rely on people to teach you it.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
