On Sun, Sep 16, 2007 at 11:52:56AM +0200, Avi Kivity wrote:
> Ferry Huberts wrote:
> > Avi Kivity wrote:
> >> Ferry Huberts wrote:
> >>
> >>
> >> I really recommend against using the kvm initscript... it is fragile
> >> is broken. On Fedora, you can use the standard initscripts (well,
> >> they
Ferry Huberts wrote:
Avi Kivity wrote:
>
>
> I really recommend against using the kvm initscript... it is fragile
> is broken. On Fedora, you can use the standard initscripts (well,
> they are fragile and broken too, but they are more complete than the
> kvm initscript):
>
> [EMAIL PROTECTED] ~
Ferry Huberts wrote:
> Avi Kivity wrote:
>> Ferry Huberts wrote:
>>> Hi list,
>>>
>>> I mailed about this earlier (may 7th, 2007) but the issue is still
>>> there: the handling surrounding DHCP clients could be a bit improved...
>>>
>>> Currently every dhcp client gets killed after which a very ba
Avi Kivity wrote:
> Ferry Huberts wrote:
>> Hi list,
>>
>> I mailed about this earlier (may 7th, 2007) but the issue is still
>> there: the handling surrounding DHCP clients could be a bit improved...
>>
>> Currently every dhcp client gets killed after which a very basic dhcp
>> client is started
Ferry Huberts wrote:
> Hi list,
>
> I mailed about this earlier (may 7th, 2007) but the issue is still
> there: the handling surrounding DHCP clients could be a bit improved...
>
> Currently every dhcp client gets killed after which a very basic dhcp
> client is started for the dst interface, whi
Hi list,
I mailed about this earlier (may 7th, 2007) but the issue is still there: the
handling surrounding DHCP clients could be a bit improved...
Currently every dhcp client gets killed after which a very basic dhcp client is
started for the dst interface, which is not really inline with wh
