OMSA is not officially supported on 32-bit SLES, though many(most?) people on this list run OMSA on non-supported distros. All the prereq rpms come from the community repo: http://linux.dell.com/repo/community/.
-Jeff > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of Nicole Hähnel > Sent: Thursday, July 09, 2009 5:51 AM > To: linux-poweredge-Lists > Subject: Re: Using local OMSA repository > > Hi, > > I changed bootstrap.sh for my needs and it works on sles10 x86_64. > But finally I miss the platform_independent rpms for sles i386. > So I can not use the repo for i386 sles servers? > > Thanks! > Nicole > > [email protected] schrieb: > > Hi, > > > > I thought rsync -a would get the .htaccess symlinks, but I > guess not. Good to hear that it is working. > > > > About yum on sles, I took a look at our bootstrap script > and it only checks for rug or zypper on sles 10/11. For rhel4 > it checks for yum before defaulting to up2date. The same yum > code would need to be under the sles sections that is there > for rhel4. Feel free to make the change to your own > _tools/bootstrap.sh file. > > > > I can take a stab at it and provide it for personal use, > but I can't update the official repo without pushing the > change through test. So, that won't be until the next OMSA release. > > > > Thanks, > > Jeff > > > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of > >> Nicole Hähnel > >> Sent: Wednesday, July 08, 2009 4:51 AM > >> To: linux-poweredge-Lists > >> Subject: Re: Using local OMSA repository > >> > >> Ok, I have to copy htaccess_repo_topdir and htaccess_tools to the > >> correct folders as .htaccess. > >> This works now. > >> > >> Is it possible to use the OMSA repository with yum on sles servers? > >> We are only using yum for all updates instead of zmd / rug on our > >> sles10 servers. > >> > >> Thanks! > >> Nicole > >> > >> [email protected] schrieb: > >> > >>> The bootstrap symlink should be how it was. It sounds like > >>> > >> cgi is not > >> > >>> enabled on your web server. Make sure you have the > .htaccess files > >>> with the repo and that your apache config is allowing the proper > >>> overrides that the .htaccess files use. See the bottom of: > >>> http://linux.dell.com/wiki/index.php/Repository/FAQ > >>> > >>> -Jeff > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: [email protected] > >>>> [mailto:[email protected]] On Behalf Of > >>>> Nicole Hähnel > >>>> Sent: Tuesday, July 07, 2009 3:29 AM > >>>> To: linux-poweredge-Lists > >>>> Subject: Re: Using local OMSA repository > >>>> > >>>> Hi, > >>>> > >>>> do I have to run the bootstrap.cgi on my server or from the dell > >>>> server? > >>>> I tried "wget -q -O - > >>>> http://myserver/repo/hardware/latest/bootstrap.cgi > >>>> | bash " and get these errors: > >>>> > >>>> bash: line 3: import: command not found > >>>> bash: line 4: import: command not found > >>>> bash: line 5: import: command not found > >>>> bash: line 6: import: command not found > >>>> bash: line 8: sys.stderr: command not found > >>>> bash: line 10: serverXref: command not found > >>>> bash: line 11: geeko.linuxdev.us.dell.com:: command not found > >>>> bash: line 12: syntax error near unexpected token `}' > >>>> bash: line 12: ` }' > >>>> > >>>> If I look at the bootstrap.cgi on my webserver, I see a > >>>> > >> python script > >> > >>>> instead of a bash script like on the dell server. > >>>> hardware/latest/bootstrap.cgi is linked to > _tools/bootstrap.cgi I > >>>> changed the symlink to _tools/bootstrap.sh and tried > >>>> > >> again, but all > >> > >>>> was downloaded from the dell server. > >>>> > >>>> wget -q -O - > >>>> http://myserver/repo/dell/community/bootstrap.cgi |bash > >>>> > >> Downloading > >> > >>>> GPG key: > >>>> http://linux.dell.com/repo/community/RPM-GPG-KEY-dell > >>>> Key already exists in RPM, skipping Downloading GPG key: > >>>> http://linux.dell.com/repo/community/RPM-GPG-KEY-libsmbios > >>>> Key already exists in RPM, skipping Downloading GPG key: > >>>> http://linux.dell.com/repo/community/mirrors.cgi?osname=el5&ba > >>>> > >>>> > >>> search=x86_64&redirpath=/repodata/repomd.xml.key > >>> > >>> > >>>> Key already exists in RPM, skipping Write repository > >>>> configuration Downloading repository RPM Installing > repository rpm: > >>>> http://linux.dell.com/repo/community/content/el5-x86_64/noarch > >>>> > >>>> > >>> /dell-community-repository-1-10.3.el5.noarch.rpm > >>> > >>> > >>>> Done! > >>>> > >>>> > >>>> > >>>> Thanks! > >>>> Nicole > >>>> > >>>> [email protected] schrieb: > >>>> > >>>> > >>>>> Hi, > >>>>> > >>>>> Please re-run your rsync, as I just added yum-dellsysid > >>>>> > >>>>> > >>>> which split from smbios-utils-python recently. > >>>> > >>>> > >>>>> Make sure your apache config allows the proper overrides > >>>>> > >>>>> > >>>> that are in > >>>> > >>>> > >>>>> the .htaccess files of the repo. See: > >>>>> http://linux.dell.com/wiki/index.php/Repository/FAQ > >>>>> > >>>>> On the client side, run the bootstrap command. For the dell > >>>>> > >>>>> > >>>> server it is: 'wget -q -O - > >>>> http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | > >>>> > >> bash' If > >> > >>>> you navigate your web browser to your local mirror, the URL will > >>>> automatically be correct in the command. > >>>> > >>>> > >>>>> Thanks, > >>>>> Jeff > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: [email protected] > >>>>>> [mailto:[email protected]] On > Behalf Of > >>>>>> Nicole Hähnel > >>>>>> Sent: Monday, July 06, 2009 5:33 AM > >>>>>> To: linux-poweredge-Lists > >>>>>> Subject: Using local OMSA repository > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I created a local OMSA mirror with rsync -avrHt --delete > >>>>>> rsync://linux.dell.com/repo. > >>>>>> What steps are necessary for setup on the client side? > >>>>>> How can I include the dellsysidplugin? > >>>>>> > >>>>>> Thanks! > >>>>>> > >>>>>> Nicole > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Linux-PowerEdge mailing list > >>>>>> [email protected] > >>>>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge > >>>>>> Please read the FAQ at http://lists.us.dell.com/faq > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>> _______________________________________________ > >>>> Linux-PowerEdge mailing list > >>>> [email protected] > >>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge > >>>> Please read the FAQ at http://lists.us.dell.com/faq > >>>> > >>>> > >>>> > >> _______________________________________________ > >> Linux-PowerEdge mailing list > >> [email protected] > >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge > >> Please read the FAQ at http://lists.us.dell.com/faq > >> > >> > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
