On 12-07-18 08:40 AM, Michael Biebl wrote:
you are aware you sent a patch for upstart while debian uses sysvinit?
Yes, I am aware of that. I didn't think it would be too much of a
stretch for one to understand what that upstart init script was doing
and how a sysvinit implementation of it w
On 12-07-03 09:07 AM, Michael Biebl wrote:
I think you are underestimating the complexity involved.
That said, I'd be willing to review a detailed proposal or patch.
You have not yet made any comment on my last update including
implementation. I would appreciate knowing why you think it's so
On 18.07.2012 14:36, Brian J. Murrell wrote:
> On 12-07-03 09:07 AM, Michael Biebl wrote:
>>
>> I think you are underestimating the complexity involved.
>> That said, I'd be willing to review a detailed proposal or patch.
>
> You have not yet made any comment on my last update including
> impleme
On Tue, 2012-07-03 at 15:07 +0200, Michael Biebl wrote:
>
> I think you are underestimating the complexity involved.
I must be since in a few hours I seem to have come up with a few
modifications (all new files, no patching of existing files necessary)
that achieves the goal.
> That said, I'd be
On 03.07.2012 14:50, Brian J. Murrell wrote:
> Yes, indeed, the process Stefan is using is the correct process, IMHO,
> and should be formalized.
>
> That is, after booting a given kernel (and it does need to be done
> immediately during/after booting so that a same-version upgrade doesn't
> repla
Yes, indeed, the process Stefan is using is the correct process, IMHO,
and should be formalized.
That is, after booting a given kernel (and it does need to be done
immediately during/after booting so that a same-version upgrade doesn't
replace it), that kernel and it's initrd should be "stashed" a
6 matches
Mail list logo
