| 1 |
I sort of missed this conversation, so apologies in advance if this |
| 2 |
has already been covered, but wanted to say that gentoo's initscripts |
| 3 |
are generally not suited for embedded systems. |
| 4 |
|
| 5 |
So making baselayout busybox-compatible doesn't seem to be worth the |
| 6 |
disruption and headaches it would cause. It would be disruptive for |
| 7 |
gentoo developers who would need to be extra-careful in maintaining |
| 8 |
their initscripts to ensure busybox compatibility. Not to mention the |
| 9 |
potential disruption for users. |
| 10 |
|
| 11 |
If you are building an embedded system using busybox, then generally |
| 12 |
you will want a single /etc/init.d/rcS script that starts all the |
| 13 |
stuff you need. |
| 14 |
|
| 15 |
-Daniel |
| 16 |
|
| 17 |
On 2/8/07, Mike Frysinger <vapier@g.o> wrote: |
| 18 |
> On Thursday 08 February 2007, Roy Marples wrote: |
| 19 |
> > Mike Frysinger <vapier@g.o> wrote: |
| 20 |
> > > On Wednesday 07 February 2007, Roy Marples wrote: |
| 21 |
> > > > In the current code I'm running it's only the network stuff that |
| 22 |
> > > > uses arrays. If you're thinking about /sbin/functions.sh, well that |
| 23 |
> > > > can stay as bash as it's not used by baselayout anymore. |
| 24 |
> > > |
| 25 |
> > > some init.d scripts use arrays as well |
| 26 |
> > |
| 27 |
> > Do we know which ones? |
| 28 |
> |
| 29 |
> grep for it :p |
| 30 |
> netmount for sure right now |
| 31 |
> |
| 32 |
> > The actual scripts themselves can be re-worked if they need to be - |
| 33 |
> > this problem only when the arrays are used in config files. |
| 34 |
> |
| 35 |
> i guess my point was i think we really need to be consistent here ... either |
| 36 |
> arrays are OK for init.d scripts or they're not OK |
| 37 |
> |
| 38 |
> did you get a chance to see how hard it would be to integrate the bash array |
| 39 |
> code ? |
| 40 |
> -mike |
| 41 |
> |
| 42 |
> |
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives