From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: [Vision for new platform] syslog, sed, cron
Date: Wed, 22 Aug 2012 19:31:49 +0200 [thread overview]
Message-ID: <CAPLrYEQ_y5wGHLZb49co4TRDwP2Dq8G+QPZ65iHyujrQyZOkZg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
Hi,
Rich started with basic tools for unix (noXCUse):
http://git.etalabs.net/cgi-bin/gitweb.cgi?p=noxcuse;a=summary
...and this is a good time to talk about other tools/daemons.
syslog
----------
rsyslog, syslog-ng - seems to be quite a hard choice. syslog-ng needs glib etc.
sysklogd - is an old and good, but today might be a little too outdated.
socklog - recommended by suckless.org etc., http://smarden.org/socklog/
metalog - (http://metalog.sourceforge.net/). Require PCRE, but it is a
very lightweight solution. The original release has ugly gnulib dep. I
deleted the extraneous code (gnulib) and packed everything into one
file (mlog.tar). The whole is adapted to musl. This stuff requires
further work (Makefile +-DOPTIONS)...
sed
-----
sed can be a big problem. I noticed that some programs require gnu sed
for proper installation (configure, Makefile).
minised is very interesting and worth a recommendation.
http://www.exactcode.de/site/open_source/minised/
Unfortunately, even with minised I can't build packages such as
e2fsprogs, findutils or find etc.
from my find's build.log:
checking whether gcc and cc understand -c and -o together... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for a sed that does not truncate output... configure: error:
no acceptable sed could be found in $PATH
We can prepare a patches etc... but if autotools will push gnu sed
this issue will return in the future as well as with other programs...
btw. I also ported to musl/linux bsd sed (from OpenBSD), but it has
worse compatibility with gnu sed than minised.
cron
------
I recommend ncron. Works very well with musl.
http://kain.us/nk/projects/
best regards,
Daniel
[-- Attachment #2: mlog.tar --]
[-- Type: application/x-tar, Size: 71680 bytes --]
next reply other threads:[~2012-08-22 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 17:31 Daniel Cegiełka [this message]
2012-08-22 18:38 ` Kurt H Maier
2012-08-22 18:53 ` Rich Felker
2012-08-22 18:56 ` Christian Neukirchen
2012-08-22 19:47 ` orc
2012-08-22 19:48 ` Daniel Cegiełka
2012-08-22 20:08 ` Christian Neukirchen
2012-08-22 22:46 ` Rich Felker
2012-08-23 0:11 ` John Spencer
2012-08-23 9:15 ` Jens Staal
2012-08-23 9:33 ` orc
2012-08-23 12:20 ` Rich Felker
2012-08-23 12:23 ` Kurt H Maier
2012-08-23 12:31 ` Rich Felker
2012-08-22 19:12 ` Daniel Cegiełka
2012-08-22 20:43 ` Daniel Cegiełka
2012-08-22 19:54 ` orc
2012-08-22 20:08 ` Daniel Cegiełka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPLrYEQ_y5wGHLZb49co4TRDwP2Dq8G+QPZ65iHyujrQyZOkZg@mail.gmail.com \
--to=daniel.cegielka@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).