Well, if it does actually have to do with there being two library versions temporarily present, then do the math. The answer would be no. Remember, you're changing the library that next to everything on the system runs against. Preventing it could mask a major underlying problem. It's the same thing as upgrading the kernel. The system is in somewhat a state of desync which can only be remedied by rebooting :P But aside from all of that, everything is mounted. You upgrade glibc. Obviously the next major status change to the file system would be to umount it. Nothing more that can really be done. If there is a way to do it.. beware of masking problems. In other news, glibc 2.2 was just released :P I'm connected to my system remotely and using my pretty ethernet to do stuff. I'm also checking to see how much crap this Windows box throws out onto the network (which it's good for doing). -Statux P.S. Whenever I use pine remotely, I just like to see myself type so you have to add an ego factor :) _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
