December 2009 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] What-If ?
by Tim Kirby 11 Dec '09

11 Dec '09

Is there any way to do a 'what-if' run of autoyast to generate a list of what RPM's would be installed from a given autoyast.xml file? A "dry run", if you will, on a running system - in a scripted environment, though - not requiring a human running a GUI/Curses interface. I am also interested in differences in resolution models. I had a string of patches to be installed on a SLED11 box that required resolution if applied with yast or packagekit with an online update - for example, a conflict on kernel-syms as it tried to update ... yet zypper cheerfully resolved the whole thing. I can't work out if zypper is more stupid and just does things without realizing it should have seen a conflict, or smarter because it looked at what it would have in the end and realized it's all OK ? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] Command line tool for downloading SLES 10 updates *
by Eric Rothweiler 10 Dec '09

10 Dec '09

YUP - it's in the developers toolkit. > On Thu, Dec 10, 2009 at 8:24 AM, Enamul Haque <haqueme(a)yahoo.com> wrote: >> >> Is there a command line tool for downloading 10 updates? I used online_update in SLES 9, but online_update tool is not available in SLES 10. >> >> TIA, Enamul >> >> >> -- 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] Command line tool for downloading SLES 10 updates
by Enamul Haque 10 Dec '09

10 Dec '09

Is there a command line tool for downloading 10 updates? I used online_update in SLES 9, but online_update tool is not available in SLES 10. TIA, Enamul -- 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] AutoInstall problems on Dell optiplex 740 & 760
by Tim Kirby 04 Dec '09

04 Dec '09

Actually seen with SLED11, but I'm shooting for a wider view on the offchance that anyone is seeing this behavior in the open space too. Problem 1. The 740 It seems we have different vintages of 740. Some of the older machines have an irritating problem with a panic... http://lists4.opensuse.org/opensuse-bugs/2009-05/msg04704.html ... which we got past, but now I seem to have an issue where some of them go through to the first boot, then come up and land at the grub> prompt. Grub can correctly identify HD(0,0) or HD(0,1) (yes, I trued moving swap & root partitions around) as being a filesystem. We watched it install... but find seems to find nothing. rebooting the system into the installer with a startshell=1, I can mount the disk in question and everything appears to be where it should be... the menu.lst looks identical to machines that work. We even tried taking memory out in case memory size was a contributor. Now, I'm not necessarily looking for a magic answer here (though I'd take one if offered). I'm looking for any ideas on how to work out what's happening. Grub isn't terribly diagnostically helpful. Problem 2. The 760 I'd installed on a 760 a number of times (testing builds) when suddenly it gakked in the partitioning section. No obvious reason why - rebooting it cleared the error. <odd>. Then it did it again. Now it's consistent. I don't know why it changed - the behavior sometimes changed with a power cycle. The 760 doesn't have a floppy - rather, it has a 4-card reader that handles SD, CF cards etc. These devices are presented as SCSI disks (albeit with no media in them). What is happening, however, is that while a manual install happily sets up /dev/sda* devices, I clone the build, try to do an autoyast and it fails. Why? Because it has now decided that the card unit "comes first", so the disk is being presented as /dev/sde with /dev/sda,b,c & d being the accursed card readers. If I change the autoyast to use /dev/sde, it cheerfully partitions, installs, then reboots and hits the wall because - yes, you guessed it. The hard drive is now presenting as /dev/sda. I can edit /etc/fstab and change it to /dev/sda, reboot, and now it continues happily. BIOS is current on this box too. I've tried fiddling with the devices in the BIOS to no avail. I'm sure that removing the card readers would fix the problem, but that's loosely like cutting off ones head to cure a headache. I've googled and binged and burned more time than I care to admit on these two... in my dreams this is going to be simple and I'll just feel stupid. That's fine, I can live with that... Constructive thoughts and suggestions most welcome. Tim (Ready to throw both machines through the nearest window) -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2