I'm not sure the lxc-user alias will take an file attachment or not.   If
not I'll try something else.

I tried to document everything I did to finally get sound working in an LXC
container on my Ubuntu 13.10 system.

I've attached that as a .ODT (librewriter) file to this email because I
tried to be verbose in describing all the steps I did.

My approach could be way off base for all I know ... wouldn't be the first
time <g>.

But after 3 weeks of searching the web to no avail for a How-To Guide or
writeup by anyone including distros (Arch, Debian, Ubuntu etc)  on LXC &
Sound.

I at least wanted to write-up everything I've found out or tried so far and
would appreciate any ideas, corrections, solutions.

As I said at the bottom of the doc I think LXC could have a great future
for User Desktops as everything works including Sound but with the caveats
regarding sound that I describe in the .ODT file.

brian mullan



On Mon, Nov 11, 2013 at 4:46 PM, Serge Hallyn <serge.hal...@ubuntu.com>wrote:

> Quoting brian mullan (bmullan.m...@gmail.com):
> > As soon as I do, I will in a few days try to document what I've done so
> > others interested in the same don't have to go through
> > the same research.
>
> Thanks, I look forward to seeing it.  The current
> pulseaudio/consolekit/logind/udev/whatever-is-messing-with-me
> setup isn't clear to me either.
>

Attachment: LXC and Sound.odt
Description: application/vnd.oasis.opendocument.text

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to