On Tue, Aug 27, 2002 at 04:30:43PM -0700, Morgan Sackett wrote:
> I'd like to use updateclient to sync up with some changes on my image.
> However using the -dry-run option shows that some files will be deleted
> that I don't want to disappear. Is there a way to have it not do this?
The way arround this is to tune the /etc/systemimager/updateclient.local.excludes
file in the image, then push it out to the clients first. First add any
files that you think should not be deleted to that file. Then run the
following commands in order on the clients (you can use cexec to run them).
cexec updateclient --image=oscarimage --directory=/etc/systemimager
--nobootloader
cexec updateclient --image=oscarimage
> Also, I've noticed that I have to have the -nobootloader option if I
> want it to boot again. I get a kernel panic: can't find init on reboot
> if I don't put it in.
It is known at this point that lilo.conf doesn't end up in the excludes
file, which is a problem. We haven't yet tuned SystemImager's update
mechanism to work right in OSCAR yet. That is planned for a future release.
-Sean
--
_______________________________________________________________________
Sean Dague [EMAIL PROTECTED] http://dague.net
There is no silver bullet. Plus, werewolves make better neighbors than
zombies, and they tend to keep the vampire population down.
_______________________________________________________________________
Attachment Converted: "c:\documents and settings\ngorsuch\eudora\attach\Re
[Oscar-users] updateclient "
