Title: Re: [Sisuite-devel] ia64 success!
Welcome back! :-)
 
I'd like to set the seeder with /etc/init.d/systemimager-server-bittorrent.
 
Okay, how about we keep a checksum of the image directory /var/lib/systemimager/images/<image> and before we start seeding, we check to see if it has changed - if it has, then we run it with the --update option - would that work?
 
Cheers,
 
Bernard


From: Andrea Righi [mailto:[EMAIL PROTECTED]
Sent: Sat 06/05/2006 10:31
To: Bernard Li
Cc: Brian Elliott Finley; sisuite-devel@lists.sourceforge.net
Subject: Re: [Sisuite-devel] ia64 success!

Bernard Li wrote:
> Hi Brian:

> Regarding grub - are you using SystemConfigurator at all?  From my tests
> on x86 and x86_64, I have not encountered issues with grub on
> RHEL4/FC4/FC5, etc. - but I only test it via SystemInstaller/OSCAR.

> If we use UYOK and pxeboot, is there a good way to automatically set
> ramdisk_size in the kernel append with the appropriate size such that it
> doesn't try to boot and kernel panic?

> I have not had much time to test UYOK but from my minimal tests it seems
> to be working. (si_mkbootpackage is still on my wish list)

> The only other thing I'd like to add to your list is, make
> si_installbtimage a daemon (Andrea where are you??? :-) )

I'm here.. :-) do you mean to put the seeder on
/etc/init.d/systemimager-server-bittorrent, instead of using
si_installbtimage? The only disadvantage I see with this approach is how
to update the tarballs and torrents of the images when they are updated
on /var/lib/systemimager/images... with si_installbtimage there's the
--update option, how to do that with a init script?

If you mean to simply daemonize the command si_installbtimage, I
agree... we can simply set the --quiet option as default and add the
--stop option to kill the seeder. Other ideas?

Cheers,
-Andrea

Reply via email to