CentOS - Mar 2016 - 32 bit programs and libraries on a 64 bit architecture

greetings.

today i attempted to update update for the nss-util. i selected the
x86_64, clicked apply, error message popped up showing a conflict
because the i686 was also installed.

opened yumex to see what i686 was installed and found a bunch of i686.

because system is a dual core 64 bit, i decided to remove all i686
packages, programs first, then lib files.

during reboot, thought hit that there may be some i686 packages that
should have been left in. maybe for wine.

this is same system that due to fresh install problems, i installed
via 64 bit live dvd.

in "closing the gate after the horses have left the corral", i am
asking is what i did good or bad.

tia.


-- 
peace out.

If Bill Gates got a dime for every time Windows crashes...
 ...oh, wait. He does. THAT explains it!
-+-
in a world with out fences, who needs gates.

CentOS GNU/Linux 6.7

tc,hago.

g
.

On 03/09/2016 10:12 AM, g wrote:
> in "closing the gate after the horses have left the corral", i am
> asking is what i did good or bad.
If you try to run a program and it doesn't run, then removing i686 might 
have been bad.  Wine is definitely one that will pull in a long list of 
i686 dependencies.

Generally what I recommend is this:  If you install a package that you 
then decide you don't want, use "yum history undo" or "yum
history
rollback" to remove that package.  Otherwise, just upgrade and don't 
look for things to remove.  The amount of disk space used by packages 
you don't actively use is measured in cents.  Your time is worth far more.

On 3/9/2016 1:20 PM, Gordon Messmer wrote:
> On 03/09/2016 10:12 AM, g wrote:
>> in "closing the gate after the horses have left the corral",
i am
>> asking is what i did good or bad.
>
> If you try to run a program and it doesn't run, then removing i686 
> might have been bad.  Wine is definitely one that will pull in a long 
> list of i686 dependencies.
>
> Generally what I recommend is this:  If you install a package that you 
> then decide you don't want, use "yum history undo" or
"yum history
> rollback" to remove that package.  Otherwise, just upgrade and
don't
> look for things to remove.  The amount of disk space used by packages 
> you don't actively use is measured in cents. Your time is worth far
more.

A minor(?) downside of too many unneeded packages is how much time yum 
update takes.



-- 
john r pierce, recycling bits in santa cruz

On 03/09/16 15:20, Gordon Messmer wrote:
> On 03/09/2016 10:12 AM, g wrote:
>> in "closing the gate after the horses have left the corral",
i am
>> asking is what i did good or bad.
>
> If you try to run a program and it doesn't run, then removing i686
might
> have been bad.  Wine is definitely one that will pull in a long list of 
> i686 dependencies.
>
--

ok. i am rounding up the horses now. ;-)

reinstalled all the wine i686. i have only used wine about 5 times from
day of it's 'birth', but at least i now have 32 bit back if i ever
need it.
> Generally what I recommend is this:  If you install a package that you 
> then decide you don't want, use "yum history undo" or
"yum history
> rollback" to remove that package.  Otherwise, just upgrade and
don't
> look for things to remove.  The amount of disk space used by packages 
> you don't actively use is measured in cents.  Your time is worth far
more.
>
--

for this one, went back over 'man yum', found;

  history
        The history command allows the user to view what has happened in
        past transactions (assuming the history_record config. option is
        set). You can use  info/list/packages-list/packages-info/summary
        to  view what happened, undo/redo/rollback to act on that infor-
        mation and new to start a new history file.

to check that history was enabled, ran 'grep' in /etc and /etc/yum/*,
all
i found is;

  yum]$ sudo grep history *
  [sudo] password for geo:
  aliases.conf:h  history
  aliases.conf:hi history info
  aliases.conf:hl history list
  aliases.conf:hs history summary
  aliases.conf:hp history package-list

  yum]$ sudo grep record *
  grep: pluginconf.d: Is a directory
  grep: protected.d: Is a directory
  grep: vars: Is a directory

nothing to enable history_record. ran 'yum history', history showed
usage 7 thru 26, so no problem. should have done that to start with.

as for drive space, diff before and after removal was about 200M in a
14.7GB partition. so no, no advantage, other than a lot of the i686 was
also x86_64.

reason all this came about was trying to update the x86_64 nss-util and
yumex complained about the i686 nss-util.

as for rest, like you say, i will find out what i686 i need when i run
various progs.

another day in my life has been blessed with more learning and a bit
wiser.

Gordon, thank you for replying and your advice. much appreciated.


-- 
peace out.

If Bill Gates got a dime for every time Windows crashes...
 ...oh, wait. He does. THAT explains it!
-+-
in a world with out fences, who needs gates.

CentOS GNU/Linux 6.7

tc,hago.

g
.