>
> Does anyone know any good step-by-step primers that cover writing init
> scripts from scratch?
most services just have a "start" and "stop" option. i'm used to add a
"restart" option like "${0} stop; sleep 3; ${0} start". but here
On 5 February 2010 16:14, Hops Error, Line 21, alcoholi.c
wrote:
> But there are two parts of the Linux OS that have always eluded me:
> init scripts, and device drivers. Obviously question two, being a dark
> art some people have devoted their lives to, is well beyond the scope
>
Hops Error, Line 21, alcoholi.c wrote:
> But there are two parts of the Linux OS that have always eluded me:
> init scripts, and device drivers.
Google for 'writing linux device drivers'. It's not arcane magic, but
you do need assembly language and to know the hardwar
, and I owe it that to
LFS.
But there are two parts of the Linux OS that have always eluded me:
init scripts, and device drivers. Obviously question two, being a dark
art some people have devoted their lives to, is well beyond the scope
of something I'd ask here. But the thing is, as hard as they
On 4 February 2010 21:48, Pol Vangheluwe wrote:
>
> I installed a lot of servers from the BLFS book and their associated boot
> scripts. I don't use some of them daily (sqlserver, dbus, …), so I have to
> disable them manually. BLFS has no tool to activate/deactivate boot scripts
> like most
Op 4-feb-2010, om 14:57 heeft Ken Moffat het volgende geschreven:
> The original post was about initscripts - the old way was to
> create static devices in /dev. That should still work for "traditional"
> devices (e.g. /dev/sdXn) but maybe not e.g. /dev/usb/lp0. This
> doesn't require an initscri
On 4 February 2010 17:29, Mike McCarty wrote:
> Ken Moffat wrote:
>> Not weird, no, but certainly asking for pain and a lot of learning
>> experiences ;)
>
> Depends on whether one considers learning to be painful :-)
>
Apart from banging my head against a wall in
frustration, or slapping mysel
Simon Geard wrote:
> On Wed, 2010-02-03 at 18:49 -0600, Mike McCarty wrote:
>> I was disappointed when I saw that LFS seemingly ineluctably
>> was wedded to udev. I see that BLFS has some hints for doing
>> things without it, but then leaves the sysadmin to his own
>> devices (no pun intended) ther
Ken Moffat wrote:
> On 4 February 2010 00:49, Mike McCarty wrote:
>
>> So, someone with the idea "my system, my rules" and "I don't
>> want udev messing around" doesn't sound weird to me at all.
>>
> Not weird, no, but certainly asking for pain and a lot of learning
> experiences ;)
Depends on
On 4 February 2010 00:49, Mike McCarty wrote:
> So, someone with the idea "my system, my rules" and "I don't
> want udev messing around" doesn't sound weird to me at all.
>
Not weird, no, but certainly asking for pain and a lot of learning
experiences ;)
The original post was about initscripts
On Wed, 2010-02-03 at 18:49 -0600, Mike McCarty wrote:
> I was disappointed when I saw that LFS seemingly ineluctably
> was wedded to udev. I see that BLFS has some hints for doing
> things without it, but then leaves the sysadmin to his own
> devices (no pun intended) thereafter, with a one senten
Ken Moffat wrote:
[...]
> Most of us manage to avoid writing initscripts until we have
> a concrete need. I'm slightly frightened by your premise that
> you need to create device nodes because udev doesn't.
>
> What sort of devices are these ?
>
> Rereading what you wrote, perhaps I'm confus
"S"
> or "K" and the run priority, etc, but I know if I sat down and tried
> to write some good init scripts, it would be an uphill battle.
>
> Does anyone know any good step-by-step primers that cover writing init
> scripts from scratch? The biggest gaps in my knowle
n and tried
to write some good init scripts, it would be an uphill battle.
Does anyone know any good step-by-step primers that cover writing init
scripts from scratch? The biggest gaps in my knowledge cover device
loading, with and without udev. For that matter, anything that teaches
me scriptable ways t
14 matches
Mail list logo
