Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do? Thanks
On 2/23/07, Dago Pacheco informatica@makimet.cl wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Beg and plead with the adobe (formerly macromedia) folks to make flash work on x86_64 hardware.... that or install the 32bit browser and requirements on the 32bit system. I've not personally done this before, but I'm sure someone on here has and will share the details.
Dago Pacheco wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Send a feature request to Adobe:
Florin Andrei wrote:
Dago Pacheco wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Send a feature request to Adobe:
I already made a feature request to Adobe, but I'd like to know how to install a 32bit browser (firefox) in my machine .
On Sat, 24 Feb 2007 at 2:07pm, Dago Pacheco wrote
Florin Andrei wrote:
Dago Pacheco wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Send a feature request to Adobe:
I already made a feature request to Adobe, but I'd like to know how to install a 32bit browser (firefox) in my machine .
yum install firefox.i386
On Sat, Feb 24, 2007 at 04:29:54PM -0500, Joshua Baker-LePain wrote:
Dago Pacheco wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Send a feature request to Adobe: http://www.adobe.com/go/wish
I already made a feature request to Adobe, but I'd like to know how to install a 32bit browser (firefox) in my machine .
yum install firefox.i386
And, since the x86_64 version is prefered by default if both are installed, follow that with "yum remove firefox.x86_64".
Matthew Miller wrote:
On Sat, Feb 24, 2007 at 04:29:54PM -0500, Joshua Baker-LePain wrote:
Dago Pacheco wrote:
Hi.. I'm using centos 4 over a x64 PC and i want to use flash.... what do i must to do?
Send a feature request to Adobe: http://www.adobe.com/go/wish
I already made a feature request to Adobe, but I'd like to know how to install a 32bit browser (firefox) in my machine .
yum install firefox.i386
And, since the x86_64 version is prefered by default if both are installed, follow that with "yum remove firefox.x86_64".
ok, but does it decrease the performance or does it generate problems?... by installing the 32bit version i mean
On Sat, Feb 24, 2007 at 07:04:26PM -0300, Dago Pacheco wrote:
ok, but does it decrease the performance or does it generate problems?... by installing the 32bit version i mean
Not that you're likely to notice.
Matthew Miller wrote:
On Sat, Feb 24, 2007 at 07:04:26PM -0300, Dago Pacheco wrote:
ok, but does it decrease the performance or does it generate problems?... by installing the 32bit version i mean
Not that you're likely to notice.
Maby is a stupid question, but i wanna be sure. There will be no problem with the profile, right?... i don't wanna loose it.
On Mon, 2007-02-26 at 12:07 -0300, Dago Pacheco wrote:
Matthew Miller wrote:
On Sat, Feb 24, 2007 at 07:04:26PM -0300, Dago Pacheco wrote:
ok, but does it decrease the performance or does it generate problems?... by installing the 32bit version i mean
Not that you're likely to notice.
Maby is a stupid question, but i wanna be sure. There will be no problem with the profile, right?... i don't wanna loose it.
The user profile should not be a problem, but the installation is a bit more complicated than described earlier as firefox.i386 is not in the x86_64 repos. I have worked around this in the past by creating a repo entry for the i386 version of the repos, disabled by default. Sample follows - excerpt from a modified /etc/yum.repos.d/CentOS-Base.repo (watch out for wrapping): -------------------------------------------------------------------------------------------------------------------------------- #released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1 --------------------------------------------------------------------------------------------------------------------------------
Should then be able to do:
# yum --enable update-i386 install firefox.i386 # yum remove firefox.x86_64
This will need to be handled manually whenever there is a firefox update, and this (along with some other 32/64-bit incompatibility issues) is the primary reason I'm running an i386 install rather than x86_64 on my dual Opteron desktop machine.
Phil
Phil Schaffner wrote:
On Mon, 2007-02-26 at 12:07 -0300, Dago Pacheco wrote:
Matthew Miller wrote:
On Sat, Feb 24, 2007 at 07:04:26PM -0300, Dago Pacheco wrote:
ok, but does it decrease the performance or does it generate problems?... by installing the 32bit version i mean
Not that you're likely to notice.
Maby is a stupid question, but i wanna be sure. There will be no problem with the profile, right?... i don't wanna loose it.
The user profile should not be a problem, but the installation is a bit more complicated than described earlier as firefox.i386 is not in the x86_64 repos. I have worked around this in the past by creating a repo entry for the i386 version of the repos, disabled by default. Sample follows - excerpt from a modified /etc/yum.repos.d/CentOS-Base.repo (watch out for wrapping):
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
Should then be able to do:
# yum --enable update-i386 install firefox.i386 # yum remove firefox.x86_64
This will need to be handled manually whenever there is a firefox update, and this (along with some other 32/64-bit incompatibility issues) is the primary reason I'm running an i386 install rather than x86_64 on my dual Opteron desktop machine.
Phil
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
I would put it in a separate file, e.g. firefox-i386.repo so that it isn't overwritten with upgrades to the package that owns CentOS-Base.repo. Otherwise, that's all you should need.
Matt
On Tue, 2007-02-27 at 10:41 -0500, Matt Hyclak wrote:
On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
I would put it in a separate file, e.g. firefox-i386.repo so that it isn't overwritten with upgrades to the package that owns CentOS-Base.repo. Otherwise, that's all you should need.
Good idea to put it in another file as it may be less confusing, but it should not be necessary to keep it from getting overwritten by an upgrade, which should create CentOS-Base.repo.rpmnew if the file has been modified. Either putting it in CentOS-Base.repo or in a new file will have the same effect.
The new file, if used, can be called anything with a .repo extension as long as it lives in /etc/yum.repos.d/ - but it helps if the name is something related to the contents. My suggestion would be "update-i386.repo" for the example I gave, as that will clue you in as to what the parameter to "yum --enable <repo> ..." should be.
Another consideration might be to avoid doing something like "yum --enable update-i386 update" as you might get more than you bargained for in the way of new i386 packages.
Phil
On Tue, Feb 27, 2007 at 03:31:32PM -0500, Phil Schaffner enlightened us:
On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
I would put it in a separate file, e.g. firefox-i386.repo so that it isn't overwritten with upgrades to the package that owns CentOS-Base.repo. Otherwise, that's all you should need.
Good idea to put it in another file as it may be less confusing, but it should not be necessary to keep it from getting overwritten by an upgrade, which should create CentOS-Base.repo.rpmnew if the file has been modified. Either putting it in CentOS-Base.repo or in a new file will have the same effect.
You're correct, a .rpmnew file would be created, but any changes made in that file would have to be hand applied. Better to let that file get automatically updated and keep your changes in another file, especially for a newbie.
Matt
Phil Schaffner wrote:
On Tue, 2007-02-27 at 10:41 -0500, Matt Hyclak wrote:
On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd... #baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
I would put it in a separate file, e.g. firefox-i386.repo so that it isn't overwritten with upgrades to the package that owns CentOS-Base.repo. Otherwise, that's all you should need.
Good idea to put it in another file as it may be less confusing, but it should not be necessary to keep it from getting overwritten by an upgrade, which should create CentOS-Base.repo.rpmnew if the file has been modified. Either putting it in CentOS-Base.repo or in a new file will have the same effect.
The new file, if used, can be called anything with a .repo extension as long as it lives in /etc/yum.repos.d/ - but it helps if the name is something related to the contents. My suggestion would be "update-i386.repo" for the example I gave, as that will clue you in as to what the parameter to "yum --enable <repo> ..." should be.
Another consideration might be to avoid doing something like "yum --enable update-i386 update" as you might get more than you bargained for in the way of new i386 packages.
Phil
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i created the .repo file and then used yum, an this is the output
------------------------------------------------------------------------------------------------------------------- [root@localhost ~]# yum --enable update-i386 install firefox.i386 Setting up Install Process Setting up repositories dag 100% |=========================| 1.1 kB 00:00 kde-all 100% |=========================| 951 B 00:00 kde 100% |=========================| 951 B 00:00 update 100% |=========================| 951 B 00:00 rpmforge 100% |=========================| 1.1 kB 00:00 update-i386 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 105 kB 00:00 update-i38: ################################################## 307/307 Added 307 new packages, deleted 0 old in 3.41 seconds primary.xml.gz 100% |=========================| 32 kB 00:00 extras : ################################################## 132/132 Added 3 new packages, deleted 0 old in 0.16 seconds Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for firefox to pack into transaction set. firefox-1.5.0.10-0.1.el4. 100% |=========================| 83 kB 00:00 ---> Package firefox.i386 0:1.5.0.10-0.1.el4.centos set to be updated --> Running transaction check --> Processing Dependency: libgnomeui-2.so.0 for package: firefox --> Processing Dependency: libgnome-2.so.0 for package: firefox --> Processing Dependency: libbonoboui-2.so.0 for package: firefox --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Downloading header for libgnome to pack into transaction set. libgnome-2.8.0-2.i386.rpm 100% |=========================| 22 kB 00:00 ---> Package libgnome.i386 0:2.8.0-2 set to be updated --> Running transaction check --> Processing Dependency: libgnomeui-2.so.0 for package: firefox --> Processing Dependency: libbonoboui-2.so.0 for package: firefox --> Finished Dependency Resolution Error: Missing Dependency: libgnomeui-2.so.0 is needed by package firefox Error: Missing Dependency: libbonoboui-2.so.0 is needed by package firefox -------------------------------------------------------------------------------------------------------------------------------------
For dependencies, should i use something like
/yum --enable update-i386 install <dependencies>/
or just/
yum install <dependencies>/
Dago Pacheco wrote:
Phil Schaffner wrote:
On Tue, 2007-02-27 at 10:41 -0500, Matt Hyclak wrote:
On Tue, Feb 27, 2007 at 12:19:41PM -0300, Dago Pacheco enlightened us:
i'm kinda newbie in centos.... so clear me something... you say that I must put this entry
#released i386 updates [update-i386] name=CentOS-$releasever - i386 Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=i386&repo=upd...
#baseurl=http://mirror.centos.org/centos/$releasever/updates/i386/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4 enabled=0 protect=1
in /etc/yum.repos.d/CentOS-Base.repo , right? is there anything else that i must consider?
I would put it in a separate file, e.g. firefox-i386.repo so that it isn't overwritten with upgrades to the package that owns CentOS-Base.repo. Otherwise, that's all you should need.
Good idea to put it in another file as it may be less confusing, but it should not be necessary to keep it from getting overwritten by an upgrade, which should create CentOS-Base.repo.rpmnew if the file has been modified. Either putting it in CentOS-Base.repo or in a new file will have the same effect.
The new file, if used, can be called anything with a .repo extension as long as it lives in /etc/yum.repos.d/ - but it helps if the name is something related to the contents. My suggestion would be "update-i386.repo" for the example I gave, as that will clue you in as to what the parameter to "yum --enable <repo> ..." should be.
Another consideration might be to avoid doing something like "yum --enable update-i386 update" as you might get more than you bargained for in the way of new i386 packages.
Phil
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i created the .repo file and then used yum, an this is the output
[root@localhost ~]# yum --enable update-i386 install firefox.i386 Setting up Install Process Setting up repositories dag 100% |=========================| 1.1 kB 00:00 kde-all 100% |=========================| 951 B 00:00 kde 100% |=========================| 951 B 00:00 update 100% |=========================| 951 B 00:00 rpmforge 100% |=========================| 1.1 kB 00:00 update-i386 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 105 kB 00:00 update-i38: ################################################## 307/307 Added 307 new packages, deleted 0 old in 3.41 seconds primary.xml.gz 100% |=========================| 32 kB 00:00 extras : ################################################## 132/132 Added 3 new packages, deleted 0 old in 0.16 seconds Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for firefox to pack into transaction set. firefox-1.5.0.10-0.1.el4. 100% |=========================| 83 kB 00:00 ---> Package firefox.i386 0:1.5.0.10-0.1.el4.centos set to be updated --> Running transaction check --> Processing Dependency: libgnomeui-2.so.0 for package: firefox --> Processing Dependency: libgnome-2.so.0 for package: firefox --> Processing Dependency: libbonoboui-2.so.0 for package: firefox --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Downloading header for libgnome to pack into transaction set. libgnome-2.8.0-2.i386.rpm 100% |=========================| 22 kB 00:00 ---> Package libgnome.i386 0:2.8.0-2 set to be updated --> Running transaction check --> Processing Dependency: libgnomeui-2.so.0 for package: firefox --> Processing Dependency: libbonoboui-2.so.0 for package: firefox --> Finished Dependency Resolution Error: Missing Dependency: libgnomeui-2.so.0 is needed by package firefox Error: Missing Dependency: libbonoboui-2.so.0 is needed by package firefox
For dependencies, should i use something like
/yum --enable update-i386 install <dependencies>/
or just/
yum install <dependencies>/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I can't find the dependencies for installing firefox.i386. Missing dependencies are libgnomeui and libbonoboui. I serched them by yum and web, but nothing (well, actually i found them in the web, but just lead me to broken lynks, or other distributions). I use kde in my CentOS 4, is that the problem?
I can't find the dependencies for installing firefox.i386. Missing dependencies are libgnomeui and libbonoboui. I serched them by yum and web, but nothing (well, actually i found them in the web, but just lead me to broken lynks, or other distributions). I use kde in my CentOS 4, is that the problem?
Nope. You have to install the i386 versions of those packages, though you might already have the x86_64 versions installed.
For desktop systems, I nearly always recommend folks use i386 even if the hardware is x86_64. It makes administration much easier.
Jim Perrin wrote:
I can't find the dependencies for installing firefox.i386. Missing dependencies are libgnomeui and libbonoboui. I serched them by yum and web, but nothing (well, actually i found them in the web, but just lead me to broken lynks, or other distributions). I use kde in my CentOS 4, is that the problem?
Nope. You have to install the i386 versions of those packages, though you might already have the x86_64 versions installed.
For desktop systems, I nearly always recommend folks use i386 even if the hardware is x86_64. It makes administration much easier.
so i must do yum --enable update-i386 install <dependecies>
if it that.. i already did it, but nothing happend....
[root@localhost ~]# yum --enable update-i386 install libgnomeui.i386 libbonoboui.i386 Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments No Match for argument: libgnomeui.i386 No Match for argument: libbonoboui.i386 Nothing to do [root@localhost ~]# yum --enable update-i386 install libgnomeui libbonoboui Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments Nothing to do
?????
-
Dago Pacheco -
Florin Andrei -
Jim Perrin -
Joshua Baker-LePain -
Matt Hyclak -
Matthew Miller -
Phil Schaffner