Same behavior as update via rpm (rpm -Uhv kernel...)
Reboot is an additional step.
Cheers
Dirk
--
From: "Mark Watts"
Sent: Tuesday, April 03, 2012 7:13 PM
To:
Subject: Re: [Spacewalk-list] Update behavior for kernel updates?
On 03/04/2012
Hi,
I'm trying to set up a kickstart file which, during the post install phase,
determines what extra software channels and configuration channels it wants to
join.
(For example, I am using RHEL 5, and for some boxes I want to add vmware tools,
or oracle packages, or physical hardware monitori
Is there a way to up the limit of configuration files in spacewalk from 128k?
To be clear, I am talking about the actual size of the file stored, not the
maximum size of a file that is editable in the browser.
Thanks!
Greg
___
Spacewalk-list mailing
Thanks Paul. I initially install 11GR2 with character set WE8MSWIN1252.
I'm not sure why this was the default when installing on a Linux node.
Anyway, I reinstalled and chose UTF8 or AL32UFT8. Installing spacewalk
was successful afterwards.
On Mon, Apr 2, 2012 at 5:33 PM, Paul Robert Marino wr
On 03/04/2012 17:51, visinix the great wrote:
Hi,
I'm currently in the middle of setting up a spacewalk server. I've been
trying to find documentation on the behavior of updates, namely kernel
updates.
Does spacewalk simply update the files, and server reboots become the
responsibility of the a
Hi,
I'm currently in the middle of setting up a spacewalk server. I've been
trying to find documentation on the behavior of updates, namely kernel
updates.
Does spacewalk simply update the files, and server reboots become the
responsibility of the administrator? Or does / can spacewalk reboot the
On 2012-04-03 4:20 AM, "Milan Zazrivec" wrote:
>> I've been provisioning both Vmware virtual machines and physical
>>hardware
>> successfully with Spacewalk and it's great. Our process is still not as
>> graceful as I want it to be because we have to provision our servers in
>>a
>> specific VL
> I've been provisioning both Vmware virtual machines and physical hardware
> successfully with Spacewalk and it's great. Our process is still not as
> graceful as I want it to be because we have to provision our servers in a
> specific VLAN and then migrate the server to it's final destination on
