x86_64 and i386 rpms

[Paul F. Johnson]

Hi,

I have duplicate copies of x86_64 and i386 rpms installed on my box
(this appears to have occured when I did the full install a few weeks
back on the new 64bit box).

Is there any problem with me ditching the i386 rpms or to they provide
something the 64 bit versions don't?

TTFN

Paul
-- 
main(t,_,a) char*a;{return!0<t?t<3?main(-79,-13,a+main(-87,1-_,main(-86,
0,a+1 )+a)):1,t<_?main(t+1,_,a ):3,main (-94,-27+t,a)&&t==2?_<13?main(2,
_+1,"%s %d
%d\n"):9:16:t<0?t<-72?main(_,t,"@n'+,#'/*{}w+/w#cdnr/+,{}r/*de}
+,/*{*+,/w{%+,/w#q#n+,/#{l,+,/n{n+,/+#n+,/#;#q#n+,/+k#;*+,/'r :'d*'3,}{w+K 
w'K:'+}e#';dq#'l
q#'+d'K#!/+k#;q#'r}eKK#}w'r}eKK{nl]'/#;#q#n'){)#}w'){){nl]
'/+#n';d}rw' i;# ){nl]!/n{n#'; r{#w'r nc{nl]'/#{l,+'K {rw'
iK{;[{nl]'/w#q#n
'wk nw' iwk{KK{nl]!/w{%'l##w#' i;
:{nl]'/*{q#'ld;r'}{nlwb!/*de}'c ;;{nl'-{}
rw]'/+,}##'*}#nc,',#nw]'/+kd'+e}+;#'rdq#w! nr'/ ')
}+}{rl#'{n' ')# }'+}##
(!!/"):t<-50?_==*a?putchar(31[a]):main(-65,_,a+1):main((*a=='/')+t,_,a+1
):0<t?main(2,2,"%s"):*a=='/'||main(0,main(-61,*a,"!ek;dc
i@bK'(q)-[w]*%n+r3#l
,{}:\nuwloca-O;m .vpbks,fxntdCeghiry"),a+1);}

[Tom Lane]

Paul <paul(a)all-the-johnsons.co.uk&gt; writes:
>  I have duplicate copies of x86_64 and i386 rpms installed on my box
>  (this appears to have occured when I did the full install a few weeks
>  back on the new 64bit box). 
>  Is there any problem with me ditching the i386 rpms or to they
> provide
>  something the 64 bit versions don't? 
This is actually standard operating procedure for 64-bit platforms
(ppc64 and s390x do the same thing).  The point is that if you've got
any 32-bit executables hanging about on your machine, you need the
32-bit libraries to support them.  You can remove the 32-bit versions
if you're certain you don't need to run any old binaries without
recompiling 'em ... but don't be too surprised if you find yourself
putting back those libraries at some point.

I believe that the RPM "requires" infrastructure will keep you from
removing any 32-bit packages that are properly referenced by other
RPMs.  The risk factor comes in with homegrown or locally-built
applications.

			regards, tom lane