April 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] autoyast in chroot
by Ragnar Kjørstad 26 Apr '07

26 Apr '07

Hi Is it possible to run autoyast in a mode where installs the distribution in a chroot on an existing system instead of installing a new system? In other words, the result would be a directory structure with the new OS installed inside the existing system directory structure. Thanks. -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com Scaling the Linux Datacenter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Looking for scripts
by King, Richard (CE1 UNIX Admin) 26 Apr '07

26 Apr '07

Hello, I was looking for the create_directory.yast & create_md5sums scripts, but I cannot seem to find them. Can someone direct me where I can find these scripts? Thanks! -- Rick King -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

Re: [opensuse-autoinstall] Problem going from DHCP to static address during autoinstall
by Jacob Emcken 26 Apr '07

26 Apr '07

Hi. ----- "Uwe Gansert" <ug(a)suse.de> wrote: > On Thursday 26 April 2007 13:52, you wrote: > > > <network_needed > config:type="boolean">true</network_needed> > > sorry, I meant "false", not true. Can you try "false". Thanks it seems it worked. Now my post scripts have access to the NFS shares because the machine uses the static ip address to connect to the NFS server instead of that DHCP address. Cheers mate. Kind regards Jacob Emcken -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] 10.2 Autoyast working but Bootmanager fails
by Ralf Prengel 25 Apr '07

25 Apr '07

Hallo, my problem: An Standard-Suse-10.2 Installation was rebuild with autoyast. the Installations works fine but after the first reboot of the clone grub stops with error 15. After booting the system from CD and repairing the bootmanger the clone works perfect. The same happens when using lilo instead of grub. Any ideas what is going wrong? -- i.A. Ralf Prengel Customer Care Manager Comline AG Hauert 8 D-44227 Dortmund/Germany Fon +49231 97575- 904 Fax +49231 97575- 905 EMail ralf.prengel(a)comline.de www.comline.de Vorstand Stephan Schilling Aufsichtsrat Dr. Franz Schoser (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] update in chroot non-interactive
by Ingo Wichmann 21 Apr '07

21 Apr '07

Hi! I install my computers with fai (fully automatic installation for debian), and it's usually working quite well. This time I want to install openSuSE 10.2 . The prinziple is simple: 0. A Debian-based installer boots over NFS 1. Partitions and filesystems are created 2. a tar-image is extracted 3. changes individual to the system are made One step within these changes is updating the system. Therefore I run the command: chroot /tmp/target zypper update -y And that's not working perfectly: ------------------- from the install log ----------------------------- [S1:0][package]kdelibs3-3.5.5-45.4.i586 Subprocess failed. Error: RPM failed: error: failed to stat /sys/kernel/debug: No such file or directory ------------------- from the install log ----------------------------- It seems, that rpm is expecting to have /sys/kernel/debug mounted as debugfs - but the debian kernel does not hat that feature. And later: ------------------- from the install log ----------------------------- [S1:0][package]kdebase3-3.5.5-102.3.i586 Subprocess failed. Error: RPM failed: error: failed to stat /sys/kernel/debug: No such file or directory Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only ERROR - can not find /dev/nfs/lib/YaST/SuSEconfig.functions!! This should not happen. Exit... error: %post(kdebase3-3.5.5-102.3.i586) scriptlet failed, exit status 1 (with nodeps+force)Invalid object (A)bort, (R)etry, (I)gnore? ------------------- from the install log ----------------------------- Well, I can give that rpm it's lib/YaST/SuSEconfig.functions , but why is it looking at /dev/nfs/lib/YaST/SuSEconfig.functions for it? I'll solve that with a symlink or mount --bind, but still: I don't like beeing asked questions when I'm away ... is there a better way to update a openSuSE 10.2 system in a chroot non-interactively? Is yum doing better? Are there some options to zypper I've missed? Ingo -- Linuxhotel, Inh. Reinhard Wiesemann, StNr. 111/5324/0471, UStID DE 180305557 Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

Re: [opensuse-autoinstall] About -1012 error while creating LVM partitions.
by Arkadiusz Kita 11 Apr '07

11 Apr '07

Hi, I have the same problem with openSUSE 10.2 with 2 identical machines so hardware failures could be excluded. I have already tested the same machine on SUSE Linux Enterprise Server and the same autoyast profile works on it. > Hi, > > I use opensue10.2 and want to use autoyast to setting LVM partitions. > > But I got a problem that -1012 error occurs while making simple LVM partitions, below message is at this problem. > > "Setting hda4 to type F" > > Othes type of partitions got no error. > I got same error only making "LVM" partitions. > > > Is this a BUG?? Any ideas? > > > > show below that section; > > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">ext3</filesystem> > <filesystem_id config:type="integer">131</filesystem_id> > <format config:type="boolean">true</format> > <mount>/boot</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">1</partition_nr> > <partition_type>primary</partition_type> > <size>73995264</size> > </partition> > <partition> > <filesystem_id config:type="integer">142</filesystem_id> > <lvm_group>system</lvm_group> > <partition_id config:type="integer">142</partition_id> > <partition_nr config:type="integer">2</partition_nr> > <partition_type>primary</partition_type> > <size>82269250560</size> > </partition> > </partitions> > <type config:type="symbol">CT_DISK</type> > <use>all</use> > </drive> > <drive> > <device>/dev/system</device> > <lvm2 config:type="boolean">true</lvm2> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">ext3</filesystem> > <format config:type="boolean">true</format> > <lv_name>home</lv_name> > <mount>/home</mount> > <size>26843545600</size> > </partition> > <partition> > <filesystem config:type="symbol">ext3</filesystem> > <format config:type="boolean">true</format> > <lv_name>root</lv_name> > <mount>/</mount> > <size>21474836480</size> > </partition> > <partition> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <lv_name>swap</lv_name> > <mount>swap</mount> > <size>922746880</size> > </partition> > </partitions> > <pesize>4M</pesize> > <type config:type="symbol">CT_LVM</type> > <use>all</use> > </drive> > </partitioning> > > > -- > K.F > casiopea@xxxxxxxxxxxxxxxxx > > > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx > For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx -- Best regards, kitarek -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Adding the SLES10 SDK to a repository?
by Michael T. Halligan 10 Apr '07

10 Apr '07

So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck: <add-on> <add_on_products config:type="list"> <listentry> <media_url>ftp://10.1.100.9/SLES10SDK</media_url> <product>SUSE-Linux-Enterprise-SDK-x86_64</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> What am I doing wrong? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4

[opensuse-autoinstall] Re: [suse-sles-e] installation_sources command?
by Michael T. Halligan 10 Apr '07

10 Apr '07

Thanks.. Was there logic behind this? I mean, when Redhat removed a bunch of rpms like php4-snmp in RHEL3U3 then brought it back in RHEL4, I switched to SLES due to a lack of faith. On Apr 9, 2007, at 11:02 PM, Marcus Meissner wrote: > On Mon, Apr 09, 2007 at 06:30:52PM -0700, Michael T. Halligan wrote: >> Does anybody know what installation_sources (SLES9: yast2- >> packagemanager) was replaced with? > > rug sl > > for SLE10 SP1 there will be a installation_sources again in the > "zypper" > RPM. > > Ciao, Marcus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] installation_sources command?
by Michael T. Halligan 10 Apr '07

10 Apr '07

Does anybody know what installation_sources (SLES9: yast2- packagemanager) was replaced with? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Re: Adding the SLES10 SDK to a repository?
by Michael T. Halligan 10 Apr '07

10 Apr '07

So, I'm wondering if anybody has ever successfully done it? There hasn't been much chatter about this on the list. I've tried creating the repository with autoyast, which is broken in 10 different ways. I've tried creating it manually. I've tried using Uwe's script which creates a mystical new driverupdate file to deal with license.zip. This is highly frustrating. It seems that year after year goes by, nobody is actually maintaining Autoyast. Is it perhaps just end of lifed with a better replacement that's actually d ocumented and supported by Novell, but nobody has told any of us? On Apr 9, 2007, at 4:08 PM, Michael T. Halligan wrote: > So, as with several other oddities, I've found my standard SLES9 > method of using Yast2 to import the SDK as an add-on product is no > longer possible. How would one go about adding SLES10's SDK to an > autoyast repository properly? I've attempted using yast2 to create > an installation source, and adding this (actually `yast autoyast` > added this) following xml to an autoinstall.xml, but with no luck: > > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>ftp://10.1.100.9/SLES10SDK</media_url> > <product>SUSE-Linux-Enterprise-SDK-x86_64</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> > > > What am I doing wrong? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0