On 21 October 2016 at 10:01, Kamil Cholewiński wrote:
> On Thu, 20 Oct 2016, Laslo Hunhold wrote:
>> as an off-idea: How are startup-times of stali? Given the power of
>> machines today, there should not be many things limiting a startup in
>> just a few
On Thu, 20 Oct 2016, Laslo Hunhold wrote:
> as an off-idea: How are startup-times of stali? Given the power of
> machines today, there should not be many things limiting a startup in
> just a few seconds. Any data on that?
Oh just try it. I was truly amazed.
>From bootloader to
On Thu, 20 Oct 2016 07:57:44 +0200
Anselm R Garbe wrote:
Hey Anselm,
> Are you talking about svc? Actually I did not create them and never
> understood the need for them
>
> My take is to keep everything in rc.init resp. rc.exit. I don't need
> on demand services. If
On 19 October 2016 at 19:10, stephen Turner wrote:
> So i briefly viewed the svc scripts, it appears that you have for the
> most part recreated daemon-tools in script form?
Are you talking about svc? Actually I did not create them and never
understood the need for
So i briefly viewed the svc scripts, it appears that you have for the
most part recreated daemon-tools in script form?
Perhaps i over looked it but it also appears to have omitted a auto
restart of the service. I assume this is by design and a good choice i
would think for a number of reasons. Is
i use udhcpc from busybox
On Tue, 18 Oct 2016, Cág wrote:
> stali has sdhcp.
Thanks for the suggestion, I may include it in my setup at some point.
dhclient? I thought that was, *relatively* speaking, looked down on?
stali has sdhcp.
On Tue, 18 Oct 2016, Bruno Vetter wrote:
> Hi there,
>
> thanks for all the support so far.
> How would one connect to wifi in stali? For me, installing libnl-tiny and
> wpa_supplicant works, but I'd be interested to hear if/how this is meant to
> be achieved in a