[opensuse-autoinstall] is it possible to install latest SLES 10 SP1 patches during autoinstall?
I am using SLES 10 SP1 and AutoYaST. I have my autoyast profile setup to configure Novell Customer Center with the correct registration code and I verified that my server gets registered with NCC. Now I'd like to have AutoYaST install all the latest patches at the appropriate place during auto-installation. Is this possible? Thanks, Chris -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Chris Partridge wrote:
I am using SLES 10 SP1 and AutoYaST. I have my autoyast profile setup to configure Novell Customer Center with the correct registration code and I verified that my server gets registered with NCC. Now I'd like to have AutoYaST install all the latest patches at the appropriate place during auto-installation. Is this possible?
Thanks, Chris
I use our internal 'yum' patch server and patch the new server with a post installation job. No problem. Andre -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Friday 17 August 2007 21:24, Chris Partridge wrote:
I am using SLES 10 SP1 and AutoYaST. I have my autoyast profile setup to configure Novell Customer Center with the correct registration code and I verified that my server gets registered with NCC. Now I'd like to have AutoYaST install all the latest patches at the appropriate place during auto-installation. Is this possible?
I've had a lot of problems trying to do this. In theory, you need to do a "rug up -t patch", then restart zmd, wait until all the catalogues are active and then do a "rug up" However, for some reason I've had problems trying to do this. either zmd would not restart, or the download or install of the updates would hang at some point. etc etc You'd probably be better off downloading all your approved patches, and then doing a "rpm -Uvh *" on the downloaded directory. -- Simon Crute IS&T. Bracknell. UK. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hello - I have a question concerning the automatic partitioning in AutoYast. I've noticed that the calculated size for the swap partition is limited to 2048 (MB), as shown in the following snippet: /usr/share/YaST2/modules/Partitions.ycp Line 322 (SLES 10) if( swap_size > 2048 ) swap_size = 2048; I'd like to understand the rationale behind this limitation - does it still make sense when the total memory size is, say 16 GB? Thanks for your help! - Harry -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi,
I have a question concerning the automatic partitioning in AutoYast. I've noticed that the calculated size for the swap partition is limited to 2048 (MB), as shown in the following snippet:
/usr/share/YaST2/modules/Partitions.ycp Line 322 (SLES 10)
if( swap_size > 2048 ) swap_size = 2048;
I'd like to understand the rationale behind this limitation - does it still make sense when the total memory size is, say 16 GB?
There was a time when swap partitions were limited to a size of 2GB. Nowadays this limit is gone, but using more than 2G of swap makes only sense in certain rare cases, therefore the maximal Swap size configured by YaST2 ist still limited to 2G. Of course if someone knows he needs more than that for his special system requirements, he can create a larger swap partition and YaST2 can reues this larger swap partition on succeeding installation attempts on the same disk. ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Mon, Nov 19, 2007 at 10:05:24PM +0100, Uwe Gansert wrote:
There was a time when swap partitions were limited to a size of 2GB. Nowadays this limit is gone, but using more than 2G of swap makes only sense in certain rare cases, therefore the maximal Swap size configured by YaST2 ist still limited to 2G. Of course if someone knows he needs more than that for his special system requirements, he can create a larger swap partition and YaST2 can reues this larger swap partition on succeeding installation attempts on the same disk.
Fairly OT, but I was curious if many others are hearing similar things from vendors. I support EDA chip designers, and the ISVs we work with not only think that sticking to the 2x physical RAM is still a good thing in all cases.. some say that 4x is "even better." Yes, even when I ask them if they feel this way with large, 256Gig systems, they answer, "yes" without hesitation. Whee.. I try to explain that if they actually need that much swap space, that the job will likely take so long to finish running (and users freak out when a batch job pends for 2 minutes).. that it would basically be useless. But they don't care, they still push it. I have seen single processes (admitted bug in their sw in this case) run a 128Gig machine out of RAM to the point that the kernel seized up, inside of 5 minutes. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com "DOS Computers manufactured by companies such as IBM, Compaq, Tandy, and millions of others are by far the most popular, with about 70 million machines in use worldwide. Macintosh fans, on the other hand, may note that cockroaches are far more numerous than humans, and that numbers alone do not denote a higher life form." -- New York Times article -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (6)
-
Andre Konopka -
Chris Partridge -
Harry Hart -
Mike Marion -
Simon Crute -
Uwe Gansert