Bug#345101: [Pkg-alsa-devel] alsa-tools

Thomas Hood jdthood at yahoo.co.uk
Fri Dec 30 22:04:17 UTC 2005

Michael Prokop wrote:
> Yes, this seems to apply for Debian sarge. But this does not seem to
> apply for Debian unstable (or even Ubuntu as someone reported to me
> when asking for checking):
> root at grml ~ # grep PATH /proc/1/environ
> root at grml ~ #

I conclude that there's a bug in /sbin/init.

> ...
> So running /lib/udev/udevsynthesize with above modprobe.d-entry does
> not provide a $PATH entry in /tmp/modprobe-env-dump. JFTR: There
> also does not exist a $PATH entry if I switch /bin/sh to /bin/bash.
> [...]
> It's a problem to use /etc/init.d/udev in the bootup process
> (resulting in 'snd_...: Unknown symbol snd_...' because of failed
> modprobe calls) with current Linux kernel on Debian unstable when
> /bin/sh isn't /bin/bash but /bin/zsh.
>> That's why the current /etc/modprobe.d/alsa-base works for many,
>> many people.
> That's just because many, many people use /bin/bash as /bin/sh. ;-)

But you say that when /bin/sh -> bash, PATH is still not set.  So the
bug ought to be biting bash users too.  But it isn't biting us---at
least not yet.  Any ideas about why this is affecting you and not
other people?

More information about the Pkg-alsa-devel mailing list