On 29/07/2014 19:41, Karl Palsson wrote:
>
> On Tue, Jul 29, 2014 at 07:05:01PM +0200, Matthias Schiffer wrote:
>> Our Freifunk firmware framework Gluon [1] based on OpenWrt
>> provides a special first-run wizard, the config mode/setup mode.
>> In this mode, almost no normal services are started
On Tue, Jul 29, 2014 at 07:05:01PM +0200, Matthias Schiffer wrote:
> Our Freifunk firmware framework Gluon [1] based on OpenWrt provides a
> special first-run wizard, the config mode/setup mode. In this mode,
> almost no normal services are started, and a minimal (failsafe-like)
> network configur
hi,
ok, please don't start coding yet. i need a couple of days to think
about this.
i'll let you know what we come up with as an idea. i really want to
avoid using the legacy runlevel pattern.
John
On 29/07/2014 19:05, Matthias Schiffer wrote:
> Our Freifunk firmware framework Gluon [1] ba
Our Freifunk firmware framework Gluon [1] based on OpenWrt provides a
special first-run wizard, the config mode/setup mode. In this mode,
almost no normal services are started, and a minimal (failsafe-like)
network configuration is used (via netifd's -c switch which was added by
an earlier patch by
please explain the use case that this will solve.
at the time of design we decided to not support run levels as we had no
valid uses cases that required run levels
On 29/07/2014 17:06, Matthias Schiffer wrote:
> Hi,
> I'd like to add a feature similar to runlevels to procd; I don't need
> switch
Hi,
I'd like to add a feature similar to runlevels to procd; I don't need
switching at runtime though. So far my plan is to make the following
three changes:
* Allow reading sysinit initscipts from a different directory than
/etc/rc.d (maybe by adding a third parameter to the runrc handler?)
* Al
