9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 httpd/pegasus on unix?
Date: Thu, 28 Feb 2008 16:23:23 +0900	[thread overview]
Message-ID: <140e7ec30802272323n2ddc13bbu59050c05ba390be8@mail.gmail.com> (raw)
In-Reply-To: <20080227155247.GA23909@nibiru.local>

On Thu, Feb 28, 2008 at 12:52 AM, Enrico Weigelt <weigelt@metux.de> wrote:
> * John Barham <jbarham@gmail.com> wrote:
>
>  > If you just want to serve static content on Unix/FreeBSD, Dan
>  > Bernstein's HTTP server in his publicfile package
>  > (http://cr.yp.to/publicfile.html) is one option.  Considering his
>  > reputation for writing secure software it's probably as good a choice
>  > as any.
>
>  Beware: this reputation is limited to "secure" - installing and
>  maintenance of DJB-packages is really ugly ! (actally, I wouldn't
>  cause this stuff "packages", but collections of code fragments).
>
>  Did you ever try to building qmail ?

 Yes. On linux and netbsd. With and without various patches. Works perfectly.
 The only time in 2 years it has ever required "ugly maintenance" was
no fault of qmail's - about 2 weeks ago my ip-range got blacklisted by
some spam databases for consisting of dynamic ip assignments, so I had
to route outgoing mail through my ISP's mail server.

>  For some customer, I had to get it built in our automated image
>  builder (which does evrything from scratch wit an sysroot'ed
>  cross-toolchain).

$ uname -p
x86_64
$ echo cc -m32 -O2 -include /usr/include/errno.h >conf-cc
$ echo cc -m32 >conf-ld
$ make
...
$ objdump -f auto-gid
auto-gid:     file format elf32-i386
architecture: i386, flags 0x00000112:
...

 Granted, the -include is a bitch and took me awhile to work out. Some
TLS[1] related error which I don't have a good understanding of. Marks
my first qmail build failure - I blame centOS :P
 The sysroot requirement is a little harder to meet, but really just
requires a mount --bind /tmp/sysroot/var/qmail /var/qmail. Or, if
you're running qmail on the host and really can't afford to stop it
for a minute or two, a custom setup rule based on hier.c (or use a
chroot - oh if only lunix had private namespaces...).

[1] /usr/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss
mismatches non-TLS reference in substdio.a(substdo.o)

> Required me to completely rewrite all makefiles.

 Just like you had to fork libixp and rewrite all its makefiles?
 Look, if you have a penchant for reimplementing build systems, go for
it. You can rewrite makefiles in every spare second of your time and I
don't care. However, your apparent inability to grasp any build system
not written by yourself is no excuse to spread FUD about other
packages.
-sqweek


  parent reply	other threads:[~2008-02-28  7:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 21:22 lejatorn
2008-02-23 21:34 ` erik quanstrom
2008-02-23 22:13 ` Skip Tavakkolian
2008-02-25 11:00 ` maht
2008-02-25 15:25   ` ron minnich
2008-02-25 16:26     ` John Barham
2008-02-27 15:52       ` Enrico Weigelt
2008-02-27 17:50         ` Steve Simon
2008-02-28  5:24         ` John Barham
2008-02-28  7:23         ` sqweek [this message]
2008-02-28 17:27           ` Enrico Weigelt
2008-02-28 19:23             ` Chad Dougherty
2008-02-29 14:43               ` Enrico Weigelt
2008-02-29  0:26             ` sqweek
2008-02-29 18:16               ` Enrico Weigelt
2008-02-29 18:18                 ` erik quanstrom
2008-02-29 18:37                 ` Uriel
2008-02-29 18:44                 ` Russ Cox
2008-02-25 16:30     ` lejatorn
2008-02-25 16:48       ` Kernel Panic
2008-02-25 19:03 ` Uriel

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=140e7ec30802272323n2ddc13bbu59050c05ba390be8@mail.gmail.com \
    --to=sqweek@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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.
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).