I mean that if you always use same libc you only have to read it once,
but if every problem have its own you have to read all of them. I do
not think it changes it sucklessness. I just wasn't sure whether the
reason was to have a single compilation unit or if there was some
other point to it (as bo
On Tue, Sep 10, 2019 at 11:07:02PM +0200, Mattias Andrée wrote:
> I mean that if you always use same libc you only have to read it once,
> but if every problem have its own you have to read all of them. I do
> not think it changes it sucklessness. I just wasn't sure whether the
> reason was to have
On Tue, Sep 10, 2019 at 06:48:17PM +0200, Mattias Andrée wrote:
> What is the point of doing your own mini-libc within the
> program? Aren't you just making it less portable and
> adding more code to read?
More code to read? Have you read the code of a standard libc? Not to mention
the SDK deps? M
Hi,
What is the point of doing your own mini-libc within the
program? Aren't you just making it less portable and
adding more code to read?
Regards,
Mattias Andrée
On Tue, 10 Sep 2019 15:49:19 +
wrote:
> Hi,
>
> For those who might be interested:
>
> I did write a lean/suckless-ish sen
Hi,
For those who might be interested:
I did write a lean/suckless-ish sendmail like program:
https://rocketgit.com/user/sylware/syncsm
It is meant for devs/advanced sysadmins/very advanced users dealing themselves
with their "email server". I am currently using it (not on _this_ email address
