installing x86_64 first, then i386

2010-09-17 Thread Arnau Bria
Hi all,

I've added a i386 repo to my x86_64 nodes and I'm seeing that, when
installing the node, yum sometimes installs many i386 packages and
sometimes not.
So, I'd like to set yum to install always x86_64 and then i386 (if
needed or specified).

Reading yum.conf man I saw :

multilib_policy Can be set to ’all’ or ’best’. All means install all
possible arches for any package you want to install. Therefore yum
install foo will install foo.i386 and foo.x86_64 on x86_64, if it is
available. Best means install the best arch for this platform, only.

so seems that is the param I want. Yum tries to install x86_64 but if I
specify foo.i386 it will install foo.i386 too.

But then I noticed a strange behaviour (bug? feature?) when installing
groups of packages. If multilib_policy is set to best, i386 packages
from the group are not installed:

# grep multilib_policy /etc/yum.conf
multilib_policy=best
# yum  groupinstall glite-WN
[]
No packages in any requested group available to install or update



# grep multilib_policy /etc/yum.conf
#multilib_policy=best
# yum  groupinstall glite-WN
[...]

Dependencies Resolved


 Package  Arch  
Version Repository  
   Size

Installing:
 dpm  i386  
1.7.4-7sec.sl5  gLite-WN-3.2-updates
  3.9 M
 dpm-develi386  
1.7.4-7sec.sl5  gLite-WN-3.2-updates
  609 k
 dpm-libs i386  
[...]


so here comes some questions:

1.-) I'm not a yum group expert, but a group is a list of packages to
be installed, so, why is yum bypassing i386 packages? Cause I can
install all missing packages by hand.

is it a problem in group's creation? 

2.-) Who may I configure yum so it install x86_64 packages always, and
only i386 if needed or specified? 


Many thanks in advance,
Arnau


source code for 3w-9xxx.ko on SL5.5

2010-09-17 Thread Faye Gibbins

Hi,

This might seem like a silly question but which RPM has the source code 
for the 3w-9xxx kernel module?


kernel-devel didn't have it and we don't use yum so I can't search it 
for 9xxx.c.


Yours
Faye

--
-
Faye Gibbins, Sys Admin.  GeoS KB.  Linux, Unix, Security
Beekeeper  - The Apiary Project, KB -   www.bees.ed.ac.uk
-
 (x(x_(X_x(O_o)x_x)_X)x)
  I grabbed at spannungsbogen before I knew I wanted it.
  Socrates: Question authority, question everything.
  Mermin:   If the maths works Shut up and calculate!

The University of Edinburgh is a charitable body,
registered in Scotland, with registration number SC005336.


Re: source code for 3w-9xxx.ko on SL5.5

2010-09-17 Thread Alan Bartlett
On 17 September 2010 12:03, Faye Gibbins fgibb...@staffmail.ed.ac.uk wrote:

 This might seem like a silly question but which RPM has the source code for
 the 3w-9xxx kernel module?

The corresponding kernel-2.6.18-whatever.src.rpm package, for SL 5.

Alan.


Re: installing x86_64 first, then i386

2010-09-17 Thread g
On 09/17/2010 09:24 AM, Arnau Bria wrote:
 Hi all,
 
 I've added a i386 repo to my x86_64 nodes and I'm seeing that, when
 installing the node, yum sometimes installs many i386 packages and
 sometimes not.
 So, I'd like to set yum to install always x86_64 and then i386 (if
 needed or specified).

i am not totally sure about this, but after going thru a lot of problems
with fedora 12 and 'repos', this may be reasonable answer.

you need to structure your 'sl.repo.local' or what ever you call it to
have structure similar to what standard 'sl.repo' has.

  baseurl=http://ftp.scientificlinux.org/linux/scientific/54/$basearch/SL

for your local repos;

  baseurl=http://path.to.local/linux/scientific/54/$basearch/SL

which may/can be shortened to;

  baseurl=http://path.to.local/54/$basearch/SL

note use of 54, $basearch, SL.


you will/may need to have i386 and x86_64 rpms in their respective
directories if i386 you need is not in x86_64.

open this link in you browser and follow thru relative directories to
see how they follow, especially when you get to $basearch

  http://ftp.scientificlinux.org/linux/

if i am in error, i am sure troy dawson or one of other maintainers will
correct.

-- 

peace out.

tc,hago.

g
.


in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/




signature.asc
Description: OpenPGP digital signature


Re: installing x86_64 first, then i386

2010-09-17 Thread Arnau Bria
On Fri, 17 Sep 2010 11:55:09 +
g g wrote:

 On 09/17/2010 09:24 AM, Arnau Bria wrote:
Hi g,


 i am not totally sure about this, but after going thru a lot of
 problems with fedora 12 and 'repos', this may be reasonable answer.
 
 you need to structure your 'sl.repo.local' or what ever you call it to
 have structure similar to what standard 'sl.repo' has.
our local repos are SL/SLC replicas. SO they have same structure.
 
   baseurl=http://ftp.scientificlinux.org/linux/scientific/54/$basearch/SL
notice that there are some i386/noarch packages under that repo.

Thanks for your reply,
Arnau


Re: installing x86_64 first, then i386

2010-09-17 Thread g
On 09/17/2010 01:11 PM, Arnau Bria wrote:
snip

 our local repos are SL/SLC replicas. SO they have same structure.

ok.

   baseurl=http://ftp.scientificlinux.org/linux/scientific/54/$basearch/SL
 notice that there are some i386/noarch packages under that repo.

yes. i did look before replying and it appeared that there were a lot
more 'noarch' than 'i386'.

problems i ran into were mostly with 'noarch'.

i presume that you did insure that what you are having problems with
you do have in your local repo.


 Thanks for your reply,

i wish i could be of more help.

hopefully, troy dawson will finish his coffee and be able to help you. ;)


-- 

peace out.

tc,hago.

g
.


in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/




signature.asc
Description: OpenPGP digital signature


Re: installing x86_64 first, then i386

2010-09-17 Thread Garrett Holmstrom

Arnau Bria wrote:

Hi all,

I've added a i386 repo to my x86_64 nodes and I'm seeing that, when
installing the node, yum sometimes installs many i386 packages and
sometimes not.
So, I'd like to set yum to install always x86_64 and then i386 (if
needed or specified).

Reading yum.conf man I saw :

multilib_policy Can be set to ’all’ or ’best’. All means install all
possible arches for any package you want to install. Therefore yum
install foo will install foo.i386 and foo.x86_64 on x86_64, if it is
available. Best means install the best arch for this platform, only.

so seems that is the param I want. Yum tries to install x86_64 but if I
specify foo.i386 it will install foo.i386 too.

But then I noticed a strange behaviour (bug? feature?) when installing
groups of packages. If multilib_policy is set to best, i386 packages
from the group are not installed:

# grep multilib_policy /etc/yum.conf
multilib_policy=best
# yum  groupinstall glite-WN
[]
No packages in any requested group available to install or update



# grep multilib_policy /etc/yum.conf
#multilib_policy=best
# yum  groupinstall glite-WN
[...]

Dependencies Resolved


 Package  Arch  
Version Repository  
   Size

Installing:
 dpm  i386  
1.7.4-7sec.sl5  gLite-WN-3.2-updates
  3.9 M
 dpm-develi386  
1.7.4-7sec.sl5  gLite-WN-3.2-updates
  609 k
 dpm-libs i386  
[...]



so here comes some questions:

1.-) I'm not a yum group expert, but a group is a list of packages to
be installed, so, why is yum bypassing i386 packages? Cause I can
install all missing packages by hand.


Like the man page says, when multilib_policy is set to best it will 
only install x86_64 when both versions are available but neither is 
installed.  Since you already seem to have dpm.x86_64 installed, yum has 
nothing to do in your first test since you told it to only install the 
best arch available.  When you made multilib_policy default back to 
all it noticed that the i386 version was not installed and offered to 
install it for you.


is it a problem in group's creation? 


No.


2.-) Who may I configure yum so it install x86_64 packages always, and
only i386 if needed or specified? 


Set multilib_policy to best and yum will install ix86 packages only 
when x86_64 versions are unavailable.  You cannot specify which package 
architecture to install in a yum group, so you must instead install the 
ix86 versions yourself when both are available to yum while 
multilib_policy is set that way.


--
Garrett Holmstrom
University of Minnesota School of Physics and Astronomy
Systems Staff


Re: installing x86_64 first, then i386

2010-09-17 Thread g
On 09/17/2010 02:17 PM, Arnau Bria wrote:
snip

 I think he will be busy patching last kernel bug :-)

looks like troy was not that busy. :)

i just wish his reply applied to my problems. but i will try to apply it
to see what results i get.

-- 

peace out.

tc,hago.

g
.


in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/




signature.asc
Description: OpenPGP digital signature