From: Fred.van.Kempen@microwalt.nl (Fred N. van Kempen)
Subject: [pups] It all works!!
Date: Tue, 27 Aug 2002 13:54:44 +0200 [thread overview]
Message-ID: <7AD18F04B62B7440BE22E190A3F7721401FF7E@mwsrv04.microwalt.nl> (raw)
Ian King wrote:
> > I suggest you now find a multi-port beer card, insert that into a
free
> > slot, add /dev/beer to the kernel, and abuse it lots... :)
> >
> > (rumor is, that 2.9bsd has much more space available for /dev/beer
> > buffers, though, so if 2.11 doesn't allow enough of it, just take
the
> > plunge and downgrade to 2.9... ;-)
> > Should he implement uubp?
Well, that's kinda store-and-forward. A bit dated, innit? Why
not go the modern way and go straight for the splattering-type
mbdp? For those who dunno: Multicast Beer Distribution Protocol.
One catch... given the kind of stuff we want distributed, we'd better
not have any (memory and/or session) leaks...
--f
next reply other threads:[~2002-08-27 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 11:54 Fred N. van Kempen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 10:15 Fred N. van Kempen
2002-08-22 13:04 Kevin Murrell
2002-08-27 11:12 ` Robin Birch
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=7AD18F04B62B7440BE22E190A3F7721401FF7E@mwsrv04.microwalt.nl \
--to=fred.van.kempen@microwalt.nl \
/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).