From: sl@9front.org
To: 9front@googlegroups.com
Subject: 9FRONT "STUCK CHUCK" Released
Date: Wed, 9 Jan 2013 17:26:28 -0600 [thread overview]
Message-ID: <bbe96e185e7d15855bbed9c652b16577@9front.org> (raw)
New 9front release "BUGGED BERT" *
http://r-36.net/9front/9front-2265.7a98d62b5005.iso.bz2.torrent
http://r-36.net/9front/9front-2265.7a98d62b5005.iso.bz2
ape: fix getsockname() byte swaped ports (by yarikos)
audio(1): various cleanups
aux/vga: add fixbios() for patching bogus vesa bios
devtls: fix hmac buffer size for SHA1 hashes (from erik)
hjfs: network announce/listen support
libdraw: fix wrong menusel() calculation for menuhit() (noticable with
small fonts)
ndb/dnsdebug: make sure request is initialized (import from sources)
vga: avoid setting vgactl type vesa multiple times, dont confuse io
bar with mem bar in vgas3 and vgavesa
tbl: fix wrong register count calculation (found by erik)
add intel 82598 10gb ethernet to pcf and pccpuf configuration, add
support for 82599 (from sources)
fix ec(2), hjfs(4), hjfs(8), tlssrv(8), usb(3), vac(1) man pages
---
-sl
* http://img.stanleylieber.com/src/14840/img/1357773871.jpg
next reply other threads:[~2013-01-09 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 23:26 sl [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-03 23:07 sl
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=bbe96e185e7d15855bbed9c652b16577@9front.org \
--to=sl@9front.org \
--cc=9front@googlegroups.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.
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).