Setting up internal repo...

Jeffrey_L_Mendoza at Dell.com Jeffrey_L_Mendoza at Dell.com
Mon Apr 6 11:46:43 CDT 2009


Patrick,

Yes, the firmware repo is not up to date. You should be able to use the
dell-dup package to convert DUPs to rpms. You could get all the latest
DUPs off of SUU.

We've tried addressing the .htaccess issue in the hardware repo, by
having them be symlinks to files in the _tools dir. Is this working for
you?

Thanks,
Jeff 

> -----Original Message-----
> From: firmware-tools-devel-bounces at lists.us.dell.com 
> [mailto:firmware-tools-devel-bounces at lists.us.dell.com] On 
> Behalf Of Flaherty, Patrick
> Sent: Monday, April 06, 2009 11:34 AM
> To: firmware-tools-devel at lists.us.dell.com
> Subject: RE: Setting up internal repo...
> 
> I've had similar problems to BJ,
> Last year when the hardware/software repos were installed on 
> a machine, say a 2950:
> 
>  # yum -y install firmware-addon-dell
>  # yum -y update
>  # yum -y install $(bootstrap_firmware -b)  # update_firmware
> 
> update_firmware would install the latest available bios. 
> That's no longer the case. I forget the exact version, but 
> update firmware now reports I have the latest everything, 
> where as suu has updates for bios and perc. So I switched 
> back to copying around suu disks and mounting them loopback.
> 
> The other annoying thing I've found with setting up a local 
> repo, is the .htaccess files aren't rsync'd, so if the cgis 
> ever move I have to go screwing about in my http conf files. 
> Here's my rsync command.
>  # /usr/bin/rsync -av --delete rsync://linux.dell.com/repo"
> 
> Patrick
> 
> > -----Original Message-----
> > From: firmware-tools-devel-bounces at lists.us.dell.com
> > [mailto:firmware-tools-devel-bounces at lists.us.dell.com] On 
> Behalf Of 
> > Matt_Domsch at dell.com
> > Sent: Friday, April 03, 2009 3:19 PM
> > To: wdierkes at 5dollarwhitebox.org;
> > firmware-tools-devel at lists.us.dell.com
> > Subject: RE: Setting up internal repo...
> > 
> > These are presently available as "dell-dup" RPMs (meaning 
> they require 
> > firmware-tools, and the dell-dup RPM that's part of the 
> firmware-tools 
> > suite).
> > 
> > http://linux.dell.com/repo/firmware/cross-distro/RPMS/noarch/
> > 
> > Server_BIOS_componentid_00159_for_PowerEdge_2950-2.4.3-21.noarch.rpm
> > Server_BIOS_10G_componentid_00159_for_PowerEdge_r900-01.01.09-
> > 21.noarch.
> > rpm
> > Server_BIOS_componentid_00159_for_PowerEdge_2970-3.0.3-21.noarch.rpm
> > 
> > You will need the firmware-tools packages from the Dell Community 
> > repository http://linux.dell.com/repo/community/
> > to be able to install and use these.
> > 
> > Thanks,
> > Matt
> > 
> > --
> > Matt Domsch
> > Linux Technology Strategist, Dell Office of the CTO 
> linux.dell.com & 
> > www.dell.com/linux
> > 
> > -----Original Message-----
> > From: firmware-tools-devel-bounces at lists.us.dell.com
> > [mailto:firmware-tools-devel-bounces at lists.us.dell.com] On 
> Behalf Of 
> > BJ Dierkes
> > Sent: Friday, April 03, 2009 2:07 PM
> > To: firmware-tools-devel at lists.us.dell.com
> > Subject: Setting up internal repo...
> > 
> > Hello all,
> > 
> > Apologies for any lack of research, I'm trying to find all 
> the info I 
> > need else where, however am also working on a time line.  
> The firmware 
> > tools are working great for our project to update ...  
> well, a lot of 
> > Dell's BIOS.  The problem I'm coming across is that the repos out 
> > there do not provide the latest versions of bios firmware we need.
> > 
> > For example:
> > 
> > $ !om
> > omreport chassis bios
> > BIOS Information
> > 
> > Manufacturer : Dell Inc.
> > Version      : 2.3.1
> > Release Date : 04/29/2008
> > 
> > 
> > This is a 2950, and we need to go to the 2.4.3 release... 
> > actually my exact needs are:
> > 
> > 2950: 2.4.3
> > 2970: 3.0.3
> > R900: 1.1.9
> > 
> > 
> > I have all the .BIN files needed to manually update to 
> this, but using 
> > firmware tools I'm having a hard time finding:
> > 
> > a) Where firmware-tools pulls these .BIN files from
> > b) Where it stores them locally
> > 
> > 
> > If possible, I'd be perfectly happy with setting up my own repo to 
> > store the .BIN files we need...  but need a bit of insight 
> on how that 
> > would be possible.  Any docs out there on how .BIN files are stored
> > (repo) and obtained?
> > 
> > Because the BIOS versions we are getting from 
> firmware-tools are from 
> > last summer (I believe) I have a feeling I'm missing 
> something.  If it 
> > matters at all... the only thing I've really changed from the yum 
> > standpoint is I removed the 'baseurl' setting in 
> > /etc/yum.repos.d/dell- community-repository.repo and am 
> just using the 
> > mirrorlist= option to obtain the proper repo.
> > 
> > Thanks for any help!
> > _______________________________________________
> > firmware-tools-devel mailing list
> > firmware-tools-devel at lists.us.dell.com
> > http://lists.us.dell.com/mailman/listinfo/firmware-tools-devel
> > 
> > _______________________________________________
> > firmware-tools-devel mailing list
> > firmware-tools-devel at lists.us.dell.com
> > http://lists.us.dell.com/mailman/listinfo/firmware-tools-devel
> > 
> > 
> 
> _______________________________________________
> firmware-tools-devel mailing list
> firmware-tools-devel at lists.us.dell.com
> http://lists.us.dell.com/mailman/listinfo/firmware-tools-devel
> 



More information about the firmware-tools-devel mailing list