Re: Glibc 2.16.0-2 and /lib problem : the answer ;)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sat, 7 Jul 2012 19:32:57 +0200, Geert Hendrickx wrote:

>On Sat, Jul 07, 2012 at 17:21:24 +0100, Jonathan Hudson wrote:
>> On Sat, 7 Jul 2012 18:18:28 +0200, Jan Steffens wrote:
>> >You used --force (-f) again. http://i.imgur.com/5Zd1w.png
>> 
>> 
>> I did NOT.
>
>
>Was /lib your current working dir when you ran pacman?
>Or did any other process have it open so it could not be removed?
>
>
>	Geert
>

Post event it's hard to tell. I previously removed obsolete
firmware, modules and udev directories, then ran the commands from a
previous thread (cut and paste, no --force).

# pacman -Syu --ignore glibc
# pacman -S glibc

The current directory was NOT /lib, and as the system is now pretty
much as loaded as prior, fuser /usr/lib (or /lib) shows no results.

-jh






[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux