[gentoo-embedded] busybox init scripts

[gentoo-embedded] busybox init scripts

[Marc Blumentritt]

Hi,

is someone working on Gentoo init scripts for busybox tools like
syslogd, hdparm, etc? I would be willing to help creating these. Perhaps
they could be included in busybox package and installed as an option?

Regards
Marc

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] busybox init scripts

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

On Saturday 27 October 2007, Marc Blumentritt wrote:
> is someone working on Gentoo init scripts for busybox tools like
> syslogd, hdparm, etc?

the only thing that could be changed is having init.d scripts be written in 
POSIX shell rather than bash.  but this has already been done, so i dont see 
what else there is to do.

> I would be willing to help creating these. Perhaps 
> they could be included in busybox package and installed as an option?

no
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-embedded] busybox init scripts

[Natanael Copa]

On Sun, 2007-10-28 at 19:43 -0400, Mike Frysinger wrote:
> On Saturday 27 October 2007, Marc Blumentritt wrote:
> > is someone working on Gentoo init scripts for busybox tools like
> > syslogd, hdparm, etc?
> 
> the only thing that could be changed is having init.d scripts be written in 
> POSIX shell rather than bash.  but this has already been done, so i dont see 
> what else there is to do.

busybox could provide a virtual/logger so you don't need to use metalog,
sdsc-syslog, socklog, sysklogd, syslog-ng or syslogread.

Same goes with other busybox tools. hdparm is mentioned, but htere is
also a web server etc.

Problem is just that there are no init.d scripts in busybox for those.

> > I would be willing to help creating these. Perhaps 
> > they could be included in busybox package and installed as an option?
> 
> no

just an idea... There could be an additional busybox-initd package with
those scripts. The ebuild could have busybox as dependency and if for
example USE=syslog, it would install check the busybox config if syslog
is enabled and it would provide a virtual/logger.


I have some simplified init.d scripts in my alpine-baselayout.

http://dev.alpinelinux.org/alpine/alpine-baselayout/
svn://svn.alpinelinux.org/alpine-portage/trunk/sys-apps/alpine-baselayout

-nc


-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] busybox init scripts

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

On Monday 29 October 2007, Natanael Copa wrote:
> On Sun, 2007-10-28 at 19:43 -0400, Mike Frysinger wrote:
> > On Saturday 27 October 2007, Marc Blumentritt wrote:
> > > is someone working on Gentoo init scripts for busybox tools like
> > > syslogd, hdparm, etc?
> >
> > the only thing that could be changed is having init.d scripts be written
> > in POSIX shell rather than bash.  but this has already been done, so i
> > dont see what else there is to do.
>
> busybox could provide a virtual/logger so you don't need to use metalog,
> sdsc-syslog, socklog, sysklogd, syslog-ng or syslogread.
>
> Same goes with other busybox tools. hdparm is mentioned, but htere is
> also a web server etc.
>
> Problem is just that there are no init.d scripts in busybox for those.

sorry, i see what you mean now ... i thought Marc was proposing rewriting 
existing POSIX init.d scripts to work in busybox's shell and the answer there 
is "no"

> > > I would be willing to help creating these. Perhaps
> > > they could be included in busybox package and installed as an option?
> >
> > no
>
> just an idea... There could be an additional busybox-initd package with
> those scripts. The ebuild could have busybox as dependency and if for
> example USE=syslog, it would install check the busybox config if syslog
> is enabled and it would provide a virtual/logger.

i think the best from a support stand point would be to have a busybox-initd 
package that'd parse the busybox config file to see what is enabled, and then 
copy the relevant init.d scripts from the portage tree.  creating independent 
scripts is just a maintenance nightmare.

so if busybox supports hdparm, it'd do:
newinitd ${PORTDIR}/sys-apps/hdparm/files/hdparm-init-8 hdparm
newconfd ${PORTDIR}/sys-apps/hdparm/files/hdparm-conf.d.3 hdparm
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

[gentoo-embedded] Re: busybox init scripts

[Marc Blumentritt]

Mike Frysinger schrieb:
>>>> I would be willing to help creating these. Perhaps
>>>> they could be included in busybox package and installed as an option?
>>> no
>> just an idea... There could be an additional busybox-initd package with
>> those scripts. The ebuild could have busybox as dependency and if for
>> example USE=syslog, it would install check the busybox config if syslog
>> is enabled and it would provide a virtual/logger.
I had this idea, too, but after I have send my email.

> 
> i think the best from a support stand point would be to have a busybox-initd 
> package that'd parse the busybox config file to see what is enabled, and then 
> copy the relevant init.d scripts from the portage tree.  creating independent 
> scripts is just a maintenance nightmare.
> 
> so if busybox supports hdparm, it'd do:
> newinitd ${PORTDIR}/sys-apps/hdparm/files/hdparm-init-8 hdparm
> newconfd ${PORTDIR}/sys-apps/hdparm/files/hdparm-conf.d.3 hdparm

That sounds really interesting. Never realized, that something like this
could be used. But if you do this, all scripts have to work with
"standard" tool and bb version, e.g. bb syslogd does not create a pid
file in /var/run. There are also some things, which work different with
bb, e.g. setting consolefont and keymap. And there are some tools, where
I do not see a comparing standard tool (or at least I think there is no
tool), e.g. httpd of busybox.

So perhaps the best method would be making standard tools of bb like
syslogd or hdparm working with the init scripts and create init scripts
for all other bb tools of interest, where no init script exists? In case
of hwclock this is already done by Roy in baselayout-2, but for
consolefont and keymap loading he proposes to create separate init
scripts, since the bb tools do work completely different.

Regards
Marc

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Re: busybox init scripts

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

On Monday 29 October 2007, Marc Blumentritt wrote:
> So perhaps the best method would be making standard tools of bb like
> syslogd or hdparm working with the init scripts and create init scripts
> for all other bb tools of interest, where no init script exists?

yessum ... get busybox to match the behavior of the tools they replace rather 
than adding special case code to the init script.

> In case 
> of hwclock this is already done by Roy in baselayout-2, but for
> consolefont and keymap loading he proposes to create separate init
> scripts, since the bb tools do work completely different.

sounds like those tools need to get fixed rather than the init.d code.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

RE: [gentoo-embedded] busybox init scripts

[thomas.cooksey]

>busybox could provide a virtual/logger so you don't need to use
metalog,
>sdsc-syslog, socklog, sysklogd, syslog-ng or syslogread.

>just an idea... There could be an additional busybox-initd package with
>those scripts. The ebuild could have busybox as dependency and if for
>example USE=syslog, it would install check the busybox config if syslog
is >enabled and it would provide a virtual/logger.

Could you not just add a few use flags to the busybox ebuild itself
which would not only install the relevant init scripts but also modify
the busybox config to include the syslog etc. too? If the use flag's not
set, you don't get the init scripts and busybox is built without the
package.


Cheers,

Tom
--
gentoo-embedded@gentoo.org mailing list

[gentoo-embedded] Re: busybox init scripts

[Marc Blumentritt]

Mike Frysinger schrieb:
> i think the best from a support stand point would be to have a busybox-initd 
> package that'd parse the busybox config file to see what is enabled, and then 
> copy the relevant init.d scripts from the portage tree.  creating independent 
> scripts is just a maintenance nightmare.
> 
> so if busybox supports hdparm, it'd do:
> newinitd ${PORTDIR}/sys-apps/hdparm/files/hdparm-init-8 hdparm
> newconfd ${PORTDIR}/sys-apps/hdparm/files/hdparm-conf.d.3 hdparm

I tried to find packages, which could provide init scripts for bb
syslogd and bb crond, but could not find some "general" init scripts.
E.g. syslog-ng looks for syslog-ng and not syslogd. Therefore I think,
that at least most bb system and network daemons require their own init
scripts or did I miss packages, which could be used for this?

Regards,
Marc

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Re: busybox init scripts

[Natanael Copa]

On Fri, 2007-11-02 at 19:42 +0100, Marc Blumentritt wrote:
> Mike Frysinger schrieb:
> > i think the best from a support stand point would be to have a busybox-initd 
> > package that'd parse the busybox config file to see what is enabled, and then 
> > copy the relevant init.d scripts from the portage tree.  creating independent 
> > scripts is just a maintenance nightmare.
> > 
> > so if busybox supports hdparm, it'd do:
> > newinitd ${PORTDIR}/sys-apps/hdparm/files/hdparm-init-8 hdparm
> > newconfd ${PORTDIR}/sys-apps/hdparm/files/hdparm-conf.d.3 hdparm
> 
> I tried to find packages, which could provide init scripts for bb
> syslogd and bb crond, but could not find some "general" init scripts.
> E.g. syslog-ng looks for syslog-ng and not syslogd. Therefore I think,
> that at least most bb system and network daemons require their own init
> scripts or did I miss packages, which could be used for this?

I think it sounds reasonable. Reusing scripts might work in a few cases
but I suspect it would be easier to just make all the init.d script for
busybox.

-nc


-- 
gentoo-embedded@gentoo.org mailing list

[gentoo-embedded] Re: busybox init scripts

[Marc Blumentritt]

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

Marc Blumentritt schrieb:
> Hi,
> 
> is someone working on Gentoo init scripts for busybox tools like
> syslogd, hdparm, etc? I would be willing to help creating these. Perhaps
> they could be included in busybox package and installed as an option?
> 
Finally I got to a point, where I really needed these init scripts, so I
wrote some for loadfont, loadkmap, hdparm, and syslogd (s. attached tar
ball). They are small and simple, nothing fancy. If you need other
tools, have a look at these scripts for ideas. Thanks go out for
Natanael, whose scripts I used as example.

Regards,
Marc

[-- Attachment #2: busybox_init_scripts.tar.bz2 --]
[-- Type: application/x-bzip, Size: 1543 bytes --]