| |||||||||||||
Poettering: The Biggest MythsPoettering: The Biggest MythsPosted Jan 27, 2013 16:20 UTC (Sun) by dskoll (subscriber, #1630)In reply to: Poettering: The Biggest Myths by pizza Parent article: Poettering: The Biggest Myths
Have you actually tried to maintain a meaningful cross-distro init script? Why, yes. Yes, I have. Our (commercial) product runs on all flavors of Linux as well as any UNIX-like system (the BSDs, Solaris, etc.) I did the rather heretical thing of writing our init script in Perl. Our product requires Perl anyway, so we know that Perl is going to be available on the system. And it was quite easy. I'm not against systemd. I think it has some very nice features and probably is the way of the future; I just wanted to point out that writing portable init scripts is not that daunting.
(Log in to post comments)
Poettering: The Biggest Myths Posted Jan 27, 2013 20:59 UTC (Sun) by pizza (subscriber, #46) [Link]
>>Have you actually tried to maintain a meaningful cross-distro init script?
>Why, yes. Yes, I have. Our (commercial) product runs on all flavors of Linux as well as any UNIX-like system (the BSDs, Solaris, etc.)
Yay!
>I did the rather heretical thing of writing our init script in Perl. Our product requires Perl anyway, so we know that Perl is going to be available on the system. And it was quite easy.
Perl makes some things easier (if nothing else, it has real data structures!) but it doesn't simplify integrating into the rest of the system.
Indeed, I couldn't even rely on having *bash* because among the targets for aforementioned init scripts were embedded systems with 4MB flash -- certainly no room for perl either)
In my case I had to integrate into/with distro networking layers, which was about as insane as things could get.
|
|||||||||||||