On Tuesday, 18 June 2019 17:03:38 BST Dale wrote:
> Alan Mackenzie wrote:
> > Hello, Dale.
> > 
> > On Tue, Jun 18, 2019 at 10:12:32 -0500, Dale wrote:
> >> Howdy,
> >> I been working on the profile switch.  I followed the directions in the
> >> news item up until the rm part in #12.  I did a equery b for a few files
> >> in the two directories and it has files that equery shows belonging to
> >> packages.  They are not orphans since they are owned.  Here is a list of
> >> the files:
> >> root@fireball / # ls -al /lib32/
> >> total 3956
> >> drwxr-xr-x 14 root root    4096 Jun 17 23:14 .
> >> drwxr-xr-x 22 root root   36864 Jun 17 01:18 ..
> >> lrwxrwxrwx  1 root root      12 Jun 17 19:25 cpp -> /usr/bin/cpp
> >> drwxr-xr-x  3 root root    4096 Jun 17 19:46 dhcpcd
> >> drwxr-xr-x 70 root root   12288 Jun 17 19:19 firmware
> >> drwxr-xr-x  2 root root    4096 Jun 17 19:21 gentoo
> >> drwxr-xr-x  3 root root    4096 Dec  9  2010 grub
> >> -rw-r--r--  1 root root       0 Nov 17  2010 .keep
> > 
> > [ .... ]
> > 
> >> -rw-r--r--  1 root root      773 Jun 17 02:51 tclooConfig.sh
> >> lrwxrwxrwx  1 root root       17 Jun 17 03:22 terminfo ->
> >> ../share/terminfo
> >> drwxr-xr-x  2 root root     4096 Jun 17 21:35 tmpfiles.d
> >> drwxr-xr-x  2 root root     4096 Apr  1 06:50 upower
> >> drwxr-xr-x  2 root root     4096 Jun 17 10:55 vdpau
> >> -rw-r--r--  1 root root      266 Jun 17 03:26 xml2Conf.sh
> >> root@fireball / #
> >> 
> >> As one can see, some of those could be important.  I noticed grub,
> >> nvidia, dracut and others that could cause issues if they failed.  Is it
> >> really safe to just rm them or did I miss something?  Do I need to do
> >> something else not mentioned in the news item for this? 
> > 
> > At this stage, /lib32 should be a symlink.  I think that step 12 means
> > just the symlink should be removed, NOT all the stuff inside what it
> > points to.
> > 
> > So I think what you should do is:
> >     $ rm /lib32
> > 
> > , but definitely NOT a recursive rm on that symlink.
> > 
> > I had to remove one of these two symlinks by hand (I can't remember
> > which one), and I've not had any trouble since.  ("Since" meaning Saturday
> > evening.)
> > 
> >> The rest of the todo list worked fine. I'm just concerned about removing
> >> these files when they are owned by packages. 
> >> Thoughts?? 
> > 
> > As above, DON'T remove the files, just the symlink.
> > 
> >> Dale
> >> 
> >> :-)  :-) 
> 
> Ahhhh.  I didn't catch that it is only removing the symlinks.  Now that
> makes me feel a little better about doing that.  Since I have it set to
> keep a binary of all my packages anyway, I just may run emerge -K world 
> and let it do its thing afterwards just to be sure.  I guess that would
> work. 
> 
> Thanks for that info.  I read it but it didn't hit me as to what it meant. 
> 
> Dale
> 
> :-)  :-) 


What Alan said.  List the two directories /lib32 and /usr/lib32 *without* a 
"/" at the end.  They should indicate they are a symlink.

-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to