On Mon, 2006-01-09 at 18:30 -0800, Bernard Li wrote:
> Okay that makes sense.
>
> I don't really do updates so I'll let folks who use that comment on
> this.
>
I use a hybrid approach, Systemimager installs my boxes up to a certain
level. From there on it's back to package management and instal
OTECTED] On Behalf
> Of Ben Hartshorne
> Sent: Monday, January 09, 2006 18:22
> To: sisuite-users@lists.sourceforge.net
> Subject: Re: [Sisuite-users] overrides and timing issues
>
> On Mon, Jan 09, 2006 at 06:17:21PM -0800, Bernard Li wrote:
> > If you're updating, w
On Mon, Jan 09, 2006 at 06:17:21PM -0800, Bernard Li wrote:
> If you're updating, why wouldn't you just put the override files as the
> "stock" files and forget about the overrides altogether?
they don't go in the base image (do I mean the same thing by 'base
image' as you do by 'stock'?) because
> Sent: Monday, January 09, 2006 18:10
> To: sisuite-users@lists.sourceforge.net
> Subject: Re: [Sisuite-users] overrides and timing issues
>
> On Mon, Jan 09, 2006 at 04:08:48PM -0800, Bernard Li wrote:
> > You won't be running apache during imaging, the server needs to be
On Mon, Jan 09, 2006 at 04:08:48PM -0800, Bernard Li wrote:
> You won't be running apache during imaging, the server needs to be
> rebooted (into the SystemImager kernel) before imaging can occur.
>
> Updating is a different story though.
I'm sorry, I mispoke. I meant updating, not imaging. You
You won't be running apache during imaging, the server needs to be
rebooted (into the SystemImager kernel) before imaging can occur.
Updating is a different story though.
Cheers,
Bernard
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Ben Har
