Go Back   openSUSE Forums > Archives > SLS Archives > ARCHIVES - SuSE Linux > ARCHIVES - 64bit Environments
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - 64bit Environments Running an AMD64 or Xeon system? Of course Linux is ready for it - but if you have any questions feel free to ask in here!

 
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 31-Oct-2007, 18:39
moueza
Guest
 
Posts: n/a
Default

Because I have a dualcore Pentium D 64bits, I have installed suse10.3 64bits. But of problems with java, and becase updater says news packages are available but when I ask for installing them -> but then,it says packages conflics ; I think the 64bits pakages are not ready to be implemented for a intensive use,whith many items.
So I want to replace my 64bits pakages by 32bits ones.
So how can I do ?
  #2 (permalink)  
Old 31-Oct-2007, 18:46
microchip
Guest
 
Posts: n/a
Default

Quote:
Because I have a dualcore Pentium D 64bits, I have installed suse10.3 64bits. But of problems with java, and becase updater says news packages are available but when I ask for installing them -> but then,it says packages conflics ; I think the 64bits pakages are not ready to be implemented for a intensive use,whith many items.
So I want to replace my 64bits pakages by 32bits ones.
So how can I do ?
[/b]
hmmm I use 64-bit SUSE for some time now and everything works without a problem here, from multi-media to Java. Replacing all of the 64-bit packages with 32-bit ones is a really hard process and you will fail and screw up everything if you don't know what you are doing. Also some of the 64-bit packages on your system may not be replaceable

The best way to go back to 32-bit SUSE is if you download the 32-bit version and do a fresh install. Make sure to backup stuff first if you don't have a separate /home partition - altho even if you have a separate /home partition, it is usually a good thing to back it up before (re)installing
  #3 (permalink)  
Old 01-Nov-2007, 05:32
eberhard
Guest
 
Posts: n/a
Default

I second MC's opinion. I also have a pentium D with a 64bit base system. For some packages, like firefox, java and flash-player I installed the 32bit versions. In the yast-package-manager just select the 32bit packages instead of the 64bit versions and resolve all dependencies. Works fine.
  #4 (permalink)  
Old 01-Nov-2007, 08:27
moueza
Guest
 
Posts: n/a
Default

If I select a 32bits package, it prints me a solver with a lot of dependencies to manually solve, but it 'll take me centuries
Just for info: how many package do you have (rpm -qa |wc) ?



Quote:
I second MC's opinion. I also have a pentium D with a 64bit base system. For some packages, like firefox, java and flash-player I installed the 32bit versions. In the yast-package-manager just select the 32bit packages instead of the 64bit versions and resolve all dependencies. Works fine.
[/b]
  #5 (permalink)  
Old 01-Nov-2007, 08:30
broch
Guest
 
Posts: n/a
Default

actually, you can't replace 64-bit with 32-bit
any piece of software that communicates with hardware (e.g. drivers) must be 64-bit if kernel is 64-bit or 32-bit if kernel is 32-bit.

now from 64-bit kernel, 64-bit drivers, 64-bit libs and so on to 32-bit is very long way. First thing is that actually you will be forced to build 32-bit system.....

So installing 32-bit OS is the best option. Don't worry, you are not loosing much as to get full advantage of 64-bit system you would have to double quite expensive pieces of your hardware and only handful desktop apps can really take advantage of 64-bit.

64-bit OS is the future irrelevant of actual desktop gains, but for now this really does not matter much.
  #6 (permalink)  
Old 01-Nov-2007, 10:26
eberhard
Guest
 
Posts: n/a
Default

Quote:
actually, you can't replace 64-bit with 32-bit
[/b]
But this is not true! I'm running 32bit firefox, java and flash-player (flash-player is 32bit only anyways). You get dependency-messages then, of course. Just select 32bit packages then for every message until you are through. It's easy.
  #7 (permalink)  
Old 01-Nov-2007, 12:15
broch
Guest
 
Posts: n/a
Default

read my post, I am talking about replacing 64-bit OS with 32-bit OS

I have run 64-bit suse since 9.1, please don't try to explain that you can run 32-bit apps on hybrid systems (suse is hybrid, meaning that suse has /lib64 and /lib32).

His post suggests simply that he is trying to install 32-bit software that must be 64-bit or he is lacking some 32-bit libs. First case requires installation of 32-bit kernel/OS (architecture change).
  #8 (permalink)  
Old 01-Nov-2007, 14:20
moueza
Guest
 
Posts: n/a
Default

hi, back from 64 to 32bits: it goes far better!

I think that if somebody wants to swap architecture, he has 2 choices: with something with like "rpm -qa|sed -e 's/\(\)\(\_64\)/yum remove \1\2 ; yum install\1_586.rpm/g"|sh or something like this ie a script OR a whole reinstallation

But if in yast under 64architectute ,if I select the 32bits version it ask to solve dependance with other package and again and so one,and I am ready to bet that it continues until you have removed almost all your 64bits pakages,because they are almost all linked to another.And it takes time to do it manually

During a former 64bits installation, they're was a dependency error during the installation itself: so what is the use of the DVDs if they can't solve the dependencies of the packages they provide?
Just from my mind, linux DISTRIBUTIONS are not ready because of fewer 64packages than 32.

Moreover certain people say all is ok with 64bits: but give me the number of your packages?
Me I had more than 1600


Quote:
read my post, I am talking about replacing 64-bit OS with 32-bit OS

I have run 64-bit suse since 9.1, please don't try to explain that you can run 32-bit apps on hybrid systems (suse is hybrid, meaning that suse has /lib64 and /lib32).

His post suggests simply that he is trying to install 32-bit software that must be 64-bit or he is lacking some 32-bit libs. First case requires installation of 32-bit kernel/OS (architecture change).
[/b]
  #9 (permalink)  
Old 01-Nov-2007, 14:44
microchip
Guest
 
Posts: n/a
Default

Quote:
Just from my mind, linux DISTRIBUTIONS are not ready because of fewer 64packages than 32.

Moreover certain people say all is ok with 64bits: but give me the number of your packages?
Me I had more than 1600
[/b]
the number of 64-bit packages is the same as the one for 32-bit. All you have to do is to compile the program with a 64-bit aware compiler and you have a 64-bit package, that's what the repository maintainers do, at least for SUSE. This doesn't mean that it makes the program you're compiling really 64-bit as this depends if the program is written to take advantage of 64-bit. It only makes it to run on a 64-bit system/OS
  #10 (permalink)  
Old 01-Nov-2007, 14:45
eberhard
Guest
 
Posts: n/a
Default

Quote:
But if in yast under 64architectute ,if I select the 32bits version it ask to solve dependance with other package and again and so one,and I am ready to bet that it continues until you have removed almost all your 64bits pakages,
[/b]
It's just not true
 
Page 1 of 2 1 2

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2