1 |
Alin Năstac wrote: |
2 |
> Doug Goldstein wrote: |
3 |
>> The only reason why OpenRC has not come up for stabilization by it's |
4 |
>> maintainers is the fact that everytime there's a new version readied |
5 |
>> for release, on the horizon there's new incompatible changes being |
6 |
>> planned for the next version. The OpenRC maintainers in Gentoo have |
7 |
>> always chosen to wait until OpenRC settles down a little bit. Now with |
8 |
>> the plan to drop support for certain features (ADSL and PPP support in |
9 |
>> the networking code), it's going to rewrite more Gentoo people to step |
10 |
>> up to develop and maintain this code. |
11 |
>> |
12 |
> rp-pppoe support should be removed because its scripts don't work well |
13 |
> under baselayout, but are you sure OpenRC mantainers also plan to drop |
14 |
> generic PPP support? |
15 |
|
16 |
I don't usually troll -dev anymore, but I feel urged to reply to this. |
17 |
|
18 |
Basically as Doug said, each OpenRC version comes with a few big |
19 |
chances. Well not massive as in "your box will break now", but just a |
20 |
different spin on how things should work. OpenRC-0.5 will have the |
21 |
biggest re-spin to date - net.lo (net.eth0 etc) is considered deprecated. |
22 |
|
23 |
Instead OpenRC now ships with network (provides net) which is a simple |
24 |
wrapper around calling ifconfig (or ip) and with the ability to run |
25 |
shell scripts. Attached is the new conf.d/net sample. You'll notice it's |
26 |
a lot smaller than the old one as it relies heavily on the user being |
27 |
able to read and understand man pages for userland tools requires to do |
28 |
the job. |
29 |
|
30 |
Now, the one weakness with this approach is that the Linux userland |
31 |
tools are quite frankly crap compared to the BSD counterparts. Why is |
32 |
there the need for many badly written tools to configure a network |
33 |
interface? As such, a side project I've started is a new ifconfig tool |
34 |
[1] to handle everything from vlans, to bridging, to bonding, to |
35 |
wireless (up to WEP) with a similar syntax to the BSD ifconfig. |
36 |
|
37 |
However, work on this has stopped as a side product of this means I have |
38 |
to get some wpa_supplicant changes I have pushed upstream so it can |
39 |
start on any wireless interface - and when it appears (pcmcia, etc). |
40 |
|
41 |
One side effect of this is that daemons such was wpa_supplicant and PPP |
42 |
are now init scripts proper - this is good. The only downside is that |
43 |
you lose the ability to control each interface via init.d. Instead I |
44 |
propose you control this via ifconfig. |
45 |
|
46 |
This decision is heavily influenced by NetBSD (disclaimer - I'm now a |
47 |
NetBSD dev). |
48 |
|
49 |
FWIW, the only re-spin I have on my list is to remove dependencies from |
50 |
rc and runscript so that dependencies are only taken into account when |
51 |
rc is run and not for each script. Essentially, making rc and runscript |
52 |
light shell wrappers and removing a few tools so that it's smaller for |
53 |
space critical devices. |
54 |
|
55 |
Thanks |
56 |
|
57 |
Roy |