9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9/Inferno Birds of a Feather at OSDI: Summary
Date: Tue,  7 Dec 2004 12:12:58 -0800	[thread overview]
Message-ID: <20041207201258.GW44345@cassie.foobarbaz.net> (raw)
In-Reply-To: <e0ac85f904120711447de6356e@mail.gmail.com>

I've been working on porting codecs and multimedia in
general. It is mostly just audio, at this point, but I
will probably be starting on video in the near future.

Currently ported:
libogg-1.1.2
libvorbis-1.1.0
flac-1.1.1
bladeenc-0.94.2
faac-1.24
oggenc

I've poked around for a reasonable mp4 library in C
and didn't find one, so I may write a native plan9
version.

When I ripped and encoded my CD collection, I decided
to use FLAC because it's lossless, so my music library
is made up of whole CDs ripped and encoded in FLAC. As
you can imagine, that's very cumbersome. I've been
going through the process of splitting the albums into
tracks, re-encoding them in ogg, and tagging the
files. I have a (currently) rough rc script that does
all of this automagically based on data from a cue
sheet. I intend to add cddb/freedb support and
parallelise it a bit such that you can give it a list
of cpu servers and it will spread the encoding process
across them.

I also have plans for a streaming audio server akin to
icecast or shoutcast. The nice part is it can probably
be easily written as an rc script.

I have quite a few other works-in-progress, but I
don't really feel they're worth mentioning until I
have more code.

On Tue, Dec 07, 2004 at 11:30:16AM -0600, Eric Van Hensbergen wrote:
> 
> 
> Okay, I'm a really bad person and didn't take any sort of good notes
> on things.  I apologize in advance for omissions and
> misinterpretations.
> 
> There was maybe a dozen or so people that attended the BoF, but we
> were fortunate to have lots of folks who have worked or are actively
> working on Plan 9.
> 
> As far as new stuff, I think the most exciting piece was Ron's
> discussion (and demonstration) of his Xen Plan 9 port.  Overall it
> seems much snappier than vmware and Ron is actively working to get the
> code released.  In addition to the discussion and demo, there was some
> discussion on hypervisors, para-virtualization and why this is a good
> thing for Plan 9.
> 
> I talked a bit about progress with v9fs (Linux support for 9P2000),
> and it seemed like the general consensus that this combined with Russ'
> plan9port applications are a really good thing.
> 
> I also talked a bit about the stuff that I'm doing as part of my
> research - namely looking at using 9P to share resources between
> para-virtualized partitions.
> 
> Ron Minnich talked a bit about 9grid along with talking about the
> status of DOE funding for 64-bit compilers and a 64-bit Opteron port.
> The short summary is there has been a bureaucratic snag with the funds
> - but hopefully it'll be straighted out real soon now and things can
> really get going.
> 
> The general consensus on the 9grid stuff is it really needs someone to
> step up and kinda take ownership of doing some of the logistical
> overhead (setting up accounts, answering setup questions, etc.)
> 
> Geoff told us a bit about 9netics and what they are working on.
> Sounds like he, Brucee, and Skip have found a way to be paid for
> working on Plan 9 stuff.
> 
> As far as core Plan 9 progress goes - there seems to be a steady
> stream of patches and fixes going into the code.  There are mechanisms
> to see what changes are going in on a day to day basis, but there is
> not always a good description of why the changes went in.  I'm going
> to work on trying to come up with some sort of automated digest of the
> changes and post them to the plan9dev mailing list on a weekly basis.
> 
> One of the biggest problem with the code at this point is that it has
> drifted out of sync with the documentation.  If people are looking to
> help out, going over the documentation, man pages, and wiki and
> aligning them with reality would be a great service to the community.
> 
> There was a little discussion on what happens when Lucent shuts off
> the lights.  There seems to be a high level of confidence that all the
> vital pieces have been replicated by enough folks that we could have
> core community services (web, wiki, and more importantly sources) back
> up within a few days.
> 
> We talked a bit about the FOAF/web-of-trust authentication model.  And
> it seemed that folks thought that this was a bad idea.  We really need
> to try using the existing centralized authentication facilities as a
> community.  Let's not create problems that may or may not exist.
> 
> That's about it.  There was some other discussions, but memory is
> fuzzy.  Other folks that were there please feel free to fill in any of
> the details I might have missed or misinterpreted.
> 
>           -eric
> 
> 
> 
> -- 
> Christopher Nielsen
> "They who can give up essential liberty for temporary
> safety, deserve neither liberty nor safety." --Benjamin Franklin

-- 
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin


       reply	other threads:[~2004-12-07 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e0ac85f904120711447de6356e@mail.gmail.com>
2004-12-07 20:12 ` Christopher Nielsen [this message]
2004-12-09  1:55   ` Kenji Okamoto
     [not found]     ` <0726e041132290767a478fa8f4ef16a8@granite.cias.osakafu-u.ac .jp>
2004-12-09  1:59       ` Andrew Simmons
2004-12-09  2:19         ` Kenji Okamoto
     [not found]   ` <c9bf8185dd331fc73fa77cd7ee6f66ca@granite.cias.osakafu-u.ac.jp>
2004-12-09  2:42     ` Christopher Nielsen
2004-12-09  3:39       ` Kenji Okamoto
2004-12-09 18:40         ` Christopher Nielsen
2004-12-07 17:30 Eric Van Hensbergen
2004-12-07 23:49 ` Jack Johnson
2004-12-08 13:50   ` Vester Thacker

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=20041207201258.GW44345@cassie.foobarbaz.net \
    --to=cnielsen@pobox.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).