Create a SLES-10 installation source
Hi everybody, since we build a lot of RPMs on our own I want to create my own installation source besides the original suse media. I realized that with SLES-9, but SLES-10 is different, isn't it? I tried the scripts available on the AutoYaST website. But without any luck. Maybe it is just a documentation issue. Here is what I do: sysadm@instserver:~> cd /srv/nfs/autoinstall/SUSE/SLES-10/X86 sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> la total 1 drwxr-xr-x 3 sysadm sysadm 80 2006-08-10 12:04 . drwxr-xr-x 4 sysadm sysadm 96 2006-08-10 11:22 .. drwxr-xr-x 10 sysadm sysadm 1024 2006-08-10 11:13 SUSE-DIST sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> mkdir MIT sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> create_update_source.sh MIT Creating MIT/updates.. /EXTRA_PROV not found, trying to find it elsewhere... using settings: datadirs: MIT/updates/ languages: english output dir: MIT/updates/ is not a directory: ignoring extra_provides: MIT/updates//EXTRA_PROV done processed 0 packages now recoding to UTF-8: packages packages.DU packages.en sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> find MIT MIT MIT/yast MIT/yast/order MIT/yast/instorder MIT/updates MIT/updates/directory.yast MIT/updates/content MIT/updates/packages MIT/updates/packages.DU MIT/updates/packages.en MIT/updates/media.1 MIT/updates/media.1/directory.yast MIT/updates/media.1/media MIT/updates/media.1/products MIT/updates/EXTRA_PROV sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> The next step documented online is not possible because I don't have any updates/suse/i586. Any help appreciated. Tobias This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.
On Thursday 10 August 2006 14:22, tobias.mucke@man-mit.com wrote:
Here is what I do:
sysadm@instserver:~> cd /srv/nfs/autoinstall/SUSE/SLES-10/X86 sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> la total 1 drwxr-xr-x 3 sysadm sysadm 80 2006-08-10 12:04 . drwxr-xr-x 4 sysadm sysadm 96 2006-08-10 11:22 .. drwxr-xr-x 10 sysadm sysadm 1024 2006-08-10 11:13 SUSE-DIST sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> mkdir MIT
do: create_update_source.sh SUSE-DIST don't create an empty directory and use that as paramter for the script. That can't work. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing God Module - Lucid
Hi,
I did not want to change the original SuSE media, but anyway. If I use the
SuSE way it works. I mean I am able to add my own RPMS without any
failures. But my already with AutoYaST installed SLES-10 do not see my own
packages. Did I miss something?
Tobias
Uwe Gansert
Here is what I do:
sysadm@instserver:~> cd /srv/nfs/autoinstall/SUSE/SLES-10/X86 sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> la total 1 drwxr-xr-x 3 sysadm sysadm 80 2006-08-10 12:04 . drwxr-xr-x 4 sysadm sysadm 96 2006-08-10 11:22 .. drwxr-xr-x 10 sysadm sysadm 1024 2006-08-10 11:13 SUSE-DIST sysadm@instserver:/srv/nfs/autoinstall/SUSE/SLES-10/X86> mkdir MIT
do: create_update_source.sh SUSE-DIST don't create an empty directory and use that as paramter for the script. That can't work. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing God Module - Lucid -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.
On Friday 11 August 2006 12:00, tobias.mucke@man-mit.com wrote:
I did not want to change the original SuSE media, but anyway. If I use the SuSE way it works. I mean I am able to add my own RPMS without any failures. But my already with AutoYaST installed SLES-10 do not see my own packages. Did I miss something?
did you register the add-on to the system via the yast2 add-on module? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Suicide Commando - Traumatize
I added my RPMs to the directory where the SuSE Distro resides. If I try to
add this with add on product YaST says that this is a already known
product. If I remove the installation source and try to add it with add-on
product it works, but no installation source is added. I am confused. What
is the difference between Installation Source and Add-on Product?
What is the best practice way? Add RPMs to the original SuSE Distro? Or try
to create a new directory for that?
Thanks for help
Tobias
Uwe Gansert
I did not want to change the original SuSE media, but anyway. If I use the SuSE way it works. I mean I am able to add my own RPMS without any failures. But my already with AutoYaST installed SLES-10 do not see my own packages. Did I miss something?
did you register the add-on to the system via the yast2 add-on module? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Suicide Commando - Traumatize -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.
On Friday 11 August 2006 12:45, tobias.mucke@man-mit.com wrote:
I added my RPMs to the directory where the SuSE Distro resides. If I try
actually, if you follow the instructions from the FAQ, you have created a new directory (updates) in parallel of your suse installation tree. You don't add RPMs to suse/i586 but to updates/suse/i586
to add this with add on product YaST says that this is a already known product.
you have to add the "updates" directory as an add-on source
What is the difference between Installation Source and Add-on Product?
An add-on product requires a base-product for example. But from my point of view too, installation source and add-on product are quite similar, you are right. That whole mechanism is new for me too.
What is the best practice way? Add RPMs to the original SuSE Distro? Or try to create a new directory for that?
create the directory with the create_update_source script and add your RPMs there. Today I took a look at a new yast2 module for creating add-on sources. So I hope in the future this task is more easy to handle and to understand. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug
participants (2)
-
tobias.mucke@man-mit.com
-
Uwe Gansert