April 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

32 bit packages on 64 bit (auto-)installation?
by Andreas Vetter 04 Apr '06

04 Apr '06

Hi, is it possible to autoinstall a machine with mostly x86_64 rpms, but force some special rpms (e.g. java-*-sun* ) to be i586 ? Question is for 10.1 and SLES10. Regards, Andreas -- Andreas Vetter

1 0

Re: [Bug 162915] dependency: gtk-sharp2-doc
by Martin Vogt 04 Apr '06

04 Apr '06

bugzilla_noreply(a)novell.com wrote: > https://bugzilla.novell.com/show_bug.cgi?id=162915 > > > mgross(a)suse.de changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution| |INVALID > > > > > ------- Comment #1 from mgross(a)suse.de 2006-04-03 08:18 MST ------- > From which installation source do you install? > The source is available at CD1 of the CD-set: > > CD1/suse/noarch/mono-tools-1.1.11-14.noarch.rpm > > Problems with incomplete FTP-mirrors should be reported to the appropriate > server maintainers. I'm closing this now. > > > Nope. Its a valid iso image, mounted and put into an autoyast installation. Verified with x86_64 and x86 The dependency was ok, in suse 10.1 beta6 and beta8. Here is a similar report: https://bugzilla.novell.com/show_bug.cgi?id=162706 The conflict comes in before any packet is installed, its a resolver error in the packages file, in the dialog, before "start install". Its an automated installation with a configured package list. (It has nothing to do which files are actually present on the CD/network) rpm needs the dependency list, which is generated from the packages file in suse/setup/desc during the pre-installation step. (Similar to hdlist in redhat, btw) These are the selected packages: <software> <base>default</base> <kernel>k_smp</kernel> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Fonts</addon> <addon>Games</addon> <addon>Gnome</addon> <addon>Gnome-Devel</addon> <addon>Hacker</addon> <addon>Java</addon> <addon>Kde</addon> <addon>Kde-Desktop</addon> <addon>Kde-Devel</addon> <addon>Kernel-Devel</addon> <addon>Laptop</addon> <addon>Latex</addon> <addon>Mobile</addon> <addon>Mono</addon> <addon>Multimedia</addon> <addon>Network</addon> <addon>Non-OSS</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>Tcl-Development</addon> </addons> </software> The packe files list: =Pkg: gtk-sharp2-complete 2.8.2 6 x86_64 =Cks: SHA1 d20811c205c495d3818b0d3f440ae4a0c32e1a4e +Req: gtk-sharp2-doc = 2.8.2-6 ... On the iso cds its in: ./CD2/suse/x86_64/gtk-sharp2-doc-2.8.2-6.x86_64.rpm (rpm -qpi works on this package) In /var/log/Yast2/y2log: ResolverContex.cc(addError):1138 There are no installable providers of mono-tools for gtk-sharp2-doc Trigger: none Because the automated installation worked in beta6 and 8 without this error I think its a bug.(maybe related to autoyast, so I CC) -- ============================================= Martin Vogt ITWM - Fraunhofer Institut fuer Techno- und Wirtschaftsmathematik Fraunhofer-Platz 1 D-67663 Kaiserslautern, Germany Tel. +49 (0) 631/31600 4356, Fax -5356 =============================================

2 1

Autoyast + LDAP
by Joachim.Tork＠gad.de 03 Apr '06

03 Apr '06

Hi, I like to put information about my machine that I want to install in an LDAP Server, i.e. partitioning, swap size, etc. .... . Is there a possibility to persuade autoyast to read the information during the installation prozess ? Best regards Joachim Tork p.s.: I thought of building an autoinst.xml file in the very first initrd before autoyast is started. But that seems to be very difficult because I have to start a network und put all librariers for querying the ldap server in the initrd.

1 0

RE: [suse-autoinstall] installing SP2 using autoyast
by BENISTY Daniel 03 Apr '06

03 Apr '06

John, The problems seems that autoyast need to know where are the rpms for that it use the order & instorder files located on the primary installation source witch is for you the SLES9 CD1. In that case autoyast cannot ask you to insert any SP CD because they are not referenced on the CD1 of SLES9. Maybe you should try different methods. 1) Use the CD1 of SP2 when installing and not the CD1 of SLES9 so it load the right order/instorder. 2) Create a custom CD with CD Creator with yast2 that include all needed files using an SP2 source (NFS or local or any other form) 3) Create an nfs source that's include SP2 and use it as the install source for autoyast instead of CD. 4) Dunno but i'm sure there are lot's of other ways to solve your problem also. Hope this could help you. Daniel BENISTY -----Message d'origine----- De : jaiber john [mailto:jaiber.john@gmail.com] Envoyé : mardi 7 mars 2006 16:25 À : suse-autoinstall(a)suse.com Objet : [suse-autoinstall] installing SP2 using autoyast Hello, I'm working on a software that lets user install SLES9 and the drivers required on a machine automatically. It does this by collecting essential user inputs and creating the autoyast.xml. This xml file is copied to a hard-disk location along with the vmlinux and initrd from CD1 to the hard-disk which is then made bootable by installing LILO (with kernel and initrd lines pointing to the files copied above). The linuxrc.config is modified within the initrd to set installation source as CD, etc. The following lines were added to linuxrc.config before re-creating the initrd: ------------------------------------------------------- AutoYast: file:///autoyast.xml Exec: modprobe ext3 InstMode: cd ------------------------------------------------------- On re-boot from hard-disk, it'd request SLES9 CD1,2,3,... and the OS would get installed. The drivers would get installed through post-install scripts. This techinique worked well for SLES9 but not with SP2. If I do the same with SP2 (i.e, copying the kernel, initrd from SP2 CD1 to hard-disk), on reboot, it requests for core SLES9 CD1 and then on, only SLES9 installation proceeds, the SP2 cds were not asked and hence they dont get installed. Are there any provision in linuxrc.config or info file to direct autoyast to install SP2 and hence request specifically for SP2 CD1 on reboot? -- Thanks <Jaiber John>

1 0

autoyast with qemu
by Norbert Wegener 02 Apr '06

02 Apr '06

I want to setup an autoinstallation system using qemu. qemu -cdrom meine.iso -boot d -hda linux.img The meine.iso contains an autoinstall.xml file with the following seqence for the partitioning: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Autoyast starts up, but when reaching the partitioning part it stops with an error message: Fehler bei der Konfiguration der Partitionen. Bitte erneut versuchen. or in english something like: Error configuring partitions. Please try again. Is there something wrong in the configuration file or has this to do with the fact, that all is running under qemu? Thanks Norbert Wegener

1 1