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
signature.asc
Description: This is a digitally signed message part.
