Re: Init system deba{te|cle}
On Mon, Nov 4, 2013 at 4:50 PM, Conrad Nelson <yaro@marupa.net> wrote:
> On 11/04/2013 10:22 AM, Tom H wrote:
>> On Sun, Nov 3, 2013 at 2:33 PM, Jonathan Dowland <jmtd@debian.org> wrote:
>>> On Sun, Nov 03, 2013 at 10:23:02AM +0100, Marko Randjelovic wrote:
>>>>
>>>> I find shell scripts the most efficient way to automate system adin
>>>> tasks. It could be because I am a programmer, but at least init
>>>> scripts are already provided, and small modifications should not be a
>>>> problem even for non-programmers. For new scripts you have 'skeleton'
>>>> file that can be easily adjusted for a particular work.
>>>
>>> Amongst other problems, how do you (or the package system) reconcile
>>> when you have made a local modification to an init script and the
>>> upstream package has made another in an update?
>>
>> Also how many init scripts are admins editing or is this theoretical?
>>
>> And if it's to fix lacunas in the scripts shipped by Debian, are bug
>> reports being filed for these scripts to be patched?
>
> The argument seems specious to me. Admins make changes to system configs all
> the time, it's part of what they do.
I've written (or helped a developer write) sysvinit scripts for
home-grown apps but I'd be sacked if I made a change to a sysvinit
script without showing that there's a technical problem with that
script and without filing a bug report.
Reply to: