Hi Robert, no I didn't try this. But will test it soon! Thanks! Bye, Peer On 24.06.2016 10:29, Robert Klein wrote:
Hi,
did you try to add the update repositories to the initial installation instead of changing the SLES repository?
(My autoYaST xml files look like this:
<add-on> <add_on_products config:type="list"> <!-- you got the first also via the “pxe install=” line --> <listentry> <media_url><![CDATA[ftp://reposerver/repos/sle11sp3/sles11sp3-x86_64/CD1]]></media_url> <product>SLES 11 SP3 (x86_64)</product> <product_dir>/</product_dir> <name>sles-x86_64</name> </listentry> <listentry> <media_url><![CDATA[http://USER:PASS@EXTERNAL_REPOSERVER/Y....]]></media_url> <product>SLES 11 SP3 (x86_64) Updates</product> <product_dir>/</product_dir> <name>sles-x86_64-updates</name> </listentry> ...
Best regards Robert
On Fri, 24 Jun 2016 09:57:47 +0200 "Dr.Peer-Joachim Koch" <pkoch@bgc-jena.mpg.de> wrote:
Hi,
the installation is working very well now using this kind of repository. However when I'm trying to use the YAST tool for auto installation to work on the package list, I get an error. Whenever I select "modify" the system is working for some time, but I never get into the subsection to select packages. I will stay in the top level menu again. Any idea ?
Bye, Peer
On 15.04.2016 20:15, Peer-Joachim Koch wrote:
Hi Oliver,
seems to be exactly what I'm looking for! Nice and detailed description.
Thanks a lot!
Bye, Peer Am 15.04.2016 um 17:56 schrieb Oliver Schweikert:
Hi Peer,
1. Copy the SLES-11-SP3 repository from DVD to $REPO and replace/add your packages below $REPO/suse/*/ as you need.
2. Update the package metadata:
#> create_package_descr -d $REPO/suse -o $REPO/suse/setup/descr
(create_package_descr is part of the inst-source-utils package)
3. Remove all "META SHA1 .... packages*" lines from $DIR/content and
4. add the new hashs to the same file:
#> (cd $REPO/suse/setup/descr && sha1sum packages* | \ while read LINE; \ do echo META SHA1 $LINE;done ) >> $REPO/content
At this point you can install manually, but you will get disturbed by signature and security warnings, which you have to commit.
5. Configure the signature handling in your AutoYaST profile:
<general>
...
<signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> </general>
6. Install with "autoyast=<theprofile> insecure=1".
Regards, Oliver
Am 15.04.2016 um 13:32 schrieb Dr.Peer-Joachim Koch:
Hi,
we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome!
-- Mit freundlichem Grüßen, Peer-Joachim Koch ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705