[Pkg-alsa-devel] Bug#602887: Bug#602887: alsa-utils: only stores levels for current system instead of supporting booting on multiple systems

Paul Wise pabs at debian.org
Wed Nov 10 01:35:57 UTC 2010


On Tue, 2010-11-09 at 19:15 +0100, Elimar Riesebieter wrote:

> I am using netenv in such cases. You can define a per hostname
> dependend /var/lib/alsa. This is the place where the soundcontrols
> are stored. As well you can define a asoundrc (etc or $home) per
> hostname for the diffrent sound devices and you're done.

Per-hostname is insufficient since it is the same Debian install on one
hard drive, but I am booting it on different hardware.

> > Store the mixer settings in a per-system or per-audio-device file.
> > 
> > Have a cron job delete mixer settings for cards that haven't been used
> > in 6 months or so.
> 
> Isn't that to complicated?

It would meet my needs and the needs of other roaming Debian users. I
think it would be exactly enough flexibility to support all users.

> Nice idea, but you know unixes are providing many solutions and are
> always a challenge. If one uses a stick or hd for more than one
> machine we can expect that user can handle those comfortable ideas
> with provided tools by himself, isn't it?

It would be almost trivial to support this within alsa-utils and there
are zero to minimal downsides for non-roaming users so I don't see why
it couldn't be implemented within alsa-utils (apart from lack of time).

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/attachments/20101110/8cba1100/attachment.pgp>


More information about the Pkg-alsa-devel mailing list