1 |
On 2/8/07, Ned Ludd <solar@g.o> wrote: |
2 |
> As somebody that's had to hand write many of those kinds of scripts. A |
3 |
> single rcS is not very ideal. Our init scripts are in fact mostly usable |
4 |
> by busybox. Granted there are a few special special cases, but then Roy |
5 |
> is offering to update those for free. One of the larger problems really |
6 |
> boils down to many packages provide default init.d scripts and these |
7 |
> expect the existing baselayout only. That will be a bigger feat to deal |
8 |
> with later on down the road. |
9 |
|
10 |
Developers will then need to test their init.d scripts to ensure that |
11 |
they are compatible with busybox. This is asking a lot of work of |
12 |
people just so you can use Gentoo's initscripts for something they are |
13 |
not really ideal for. Any time a script is updated a new rev of a |
14 |
package is required, and this does impact users and will cause |
15 |
packages to be rebuilt when a user does "emerge -u". So I think this |
16 |
should be weighed against the potential benefits of baselayout + |
17 |
busybox. |
18 |
|
19 |
If you are targetting something smaller than 32MB, then maybe busybox |
20 |
is appropriate. But you are trying to go really small, then you |
21 |
probably don't want all the extra junk in our initscripts. And if you |
22 |
are _not_ trying to go really small, then put bash in your filesystem, |
23 |
not busybox, and the initscripts will work. If bash isn't fast enough |
24 |
from a boot time perspective, then the gentoo initscripts certainly |
25 |
aren't going to be fast enough either. |
26 |
|
27 |
In other words: |
28 |
|
29 |
busybox + single rcS file = fastest and simplest, smallest, best for |
30 |
very small filesystems, not as flexible |
31 |
|
32 |
bash + gentoo baselayout = most flexible, biggest, slower, best for |
33 |
feature-rich systems |
34 |
|
35 |
busybox + gentoo baselayout = ? |
36 |
|
37 |
I think that in 99 out of 100 cases, if you have room for baselayout, |
38 |
then you probably have room for bash too. And in 99 out of 100 cases, |
39 |
if you can deal with the load time of baselayout, then you can deal |
40 |
with the overhead that might be incurred from having bash. |
41 |
|
42 |
I'm just pointing out that it's not an obviously good combination. In |
43 |
the grand scheme of things, maybe it's not a great use of developer |
44 |
resources. Or, maybe I'm wrong and it is a great idea. |
45 |
|
46 |
Personally I think that "baselayout + busybox" may be cool, but adding |
47 |
an aftermarket sunroof to your car can be cool too. But that doesn't |
48 |
mean it's worth the effort :) |
49 |
|
50 |
Really, it's hard for me to imagine many scenarios where you really |
51 |
need the flexibility of baselayout but can't squeeze in bash. And I |
52 |
have a pretty good imagination. |
53 |
|
54 |
-Daniel |
55 |
-- |
56 |
gentoo-dev@g.o mailing list |