> It looks like the stali curl_config.h sets CURL_CA_BUNDLE to
> /etc/ssl/certs/ca-certificates.crt[0]. I suspect that this is the
> detected location for the cert bundle on the system used to run curl's
> configure script.
I overlooked that.
> I don't know how it's meant to work on stali, but on
> I suggest just grabbing cert.pem from libressl.
Thanks for the quick reply. Do you know if there is a designated default path
for certs in stali?
>From what I see, stali's curl is not built with any certs default path or
>default bundle file. I don't know if it falls back to some libressl set
Hello,
what is the recommended way to obtain a decent bundle of CA certificates for
stali? Like the ones I find in /etc/ssl/certs in my current distro.
Thanks
Bruno
Yes, that's what I use. And I also installed svc to start things up. Not part
of stali, but of "suckless core".
Von: Cág
Gesendet: Dienstag, 18. Oktober 2016 21:08
An: dev mail list
Betreff: Re: [dev] [stali] The stali way to wifi
> dhclient? I thought that was, *relatively* speaking, loo
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 stali way.
Bruno
etreff: Re: [dev] [dvtm] Scrolling back
On Sat, Oct 15, 2016, at 08:40, Bruno Vetter wrote:
> Dear all,
>
> I just checked out dvtm on a stali installation with default config.h. As
> a default, mod+page up is configured for scrollback along with shift-page
> up, which see
Guten Tag,
trying out stali I see that manpages are included, but how can I actually view
them? Before I install anything I want to ensure to do it in the most suckless
way.
Thank you
Bruno
Dear all,
I just checked out dvtm on a stali installation with default config.h. As a
default, mod+page up is configured for scrollback along with shift-page up,
which seems more convenient for me.
>From my understanding, shift-page up is already sucked up by the fbdev based
>console so it scr
Legacy mode is only set in build.sh when using the -L flag. Which is the way to
build lksh according to the build documentation.
Von: Bruno Vetter
Gesendet: Montag, 10. Oktober 2016 19:05
An: dev mail list
Betreff: AW: [dev] [stali] Why lksh?
I built stali from source and I see some
ontag, 10. Oktober 2016 04:47
An: dev mail list
Betreff: Re: [dev] [stali] Why lksh?
Hi Bruno,
On 9 October 2016 at 10:06, Bruno Vetter wrote:
> i'm curious why you have chosen lksh as the stali shell. The manpage says:
Looks like a man page fault to me, probably lksh.1 is copied o
Guten Morgen,
i'm curious why you have chosen lksh as the stali shell. The manpage says:
...is a command interpreter intended exclusively for running legacy
shell scripts.
... is not suitable as a user's login shell, either; use mksh instead.
Cheers
Bruno
Hi Anselm,
yes, it's tedious and I understand that it's not crucial to have the toolchain
statically linked. Trying to do so also brings up a lot of questions that I
cannot answer easily. For example a statically linked linker apparently does
not support an lto plugin. I have no idea if that wo
auto-made makefiles.
Perhaps I will continue just to see what I end up with.
Von: Cág
Gesendet: Freitag, 7. Oktober 2016 10:23
An: dev mail list
Betreff: Re: [dev] [stali] Need musl based toolchain on stali installation
Bruno Vetter wrote:
> building several applications like this o
: Re: [dev] [stali] Need musl based toolchain on stali installation
Bruno Vetter wrote:
> Can someone give me some hints on how to achieve this?
Hi,
All you have to do is (at least how I've once tried it):
1. Create a directory for your build.
2. cd to it.
3. clone toolchain and src
Hi all,
I would like to experiment with stali and install built-from-source
applications on top of the base installation. For this I need a musl based
toolchain not for cross-compiling, but as part of my stali system. Can someone
give me some hints on how to achieve this?
My experience so f
15 matches
Mail list logo