> This bug seems obvious, because I presume not everyone is using the
> "default
> install", and if you disable the _STARTUP SCRIPT ONLY_ devfsd
requirement
> alsa works just fine.
>
> Checking http://www.alsa-project.org I find _NO_ reference to a devfsd
> _requirement_. The following is all it says on the subject:
>
First, you do not understand.
devfs != devfsd
devfs != mounted devfs
Second, checking sources:
alsa-driver-0.5.11/kernel/info.c:snd_info_init()
#ifndef CONFIG_DEVFS_FS
p = create_proc_entry("dev", S_IFDIR | S_IRUGO | S_IXUGO,
snd_proc_root)
;
if (p == NULL)
return -ENOMEM;
snd_info_entry_prepare(p);
snd_proc_dev = p;
#endif
alsa-driver-0.5.11/kernel/sound.c:alsa_sound_init():
#ifdef CONFIG_DEVFS_FS
devfs_handle = devfs_mk_dir(NULL, "snd", NULL);
if (devfs_register_chrdev(snd_major, "alsa", &snd_fops)) {
#else
if (register_chrdev(snd_major, "alsa", &snd_fops)) {
#endif
Which means, that /proc/asound/dev is not created if you have devfs. And
if you do not have devfs mounted /dev/snd is not created either.
> > Run the ./snddevices script to create new sound devices in /dev
> directory. Skip this step, if you have a kernel with the DEVFS
support.
>
> And this is what it has to say on DEVFS:
>
> > DEVFS.
> >
> > The ALSA driver fully supports the devfs extension. You should
add
> the
> following lines to your devfsd.conf file to make things work properly:
> >
> > Tip: LOOKUP EXECUTE snd /sbin/modprobe snd
> > REGISTER sound/.* PERMISSIONS root.audio 660
> > REGISTER snd/.* PERMISSIONS root.audio 660
>
> This seems pretty clear that you should run ./snddevices _IF AND ONLY
IF_
> devfsd is running.
>
Dammit, you should run this script _IF_AND_ONLY_IF_ devfs is not there.
It is irrelevant if devfsd is running.
> Unfortunately that won't work here because the startup script
_REMOVES_
> /dev/snd on shutdown!
>
Startup script assumes that devices are managed by ALSA subsystems
*ONLY*. It does not assume that you manually create any devices. I can
well understand it. It removes it so it does not point to stale
location.
> Fix the broken startup script and it will work fine.
>
It is not broken. If you prefer do things in broken way it is your own
decision.
> I have been upgrading from cooker releases since pre-7.2. Never once
has
> an
> installation script of the kernel, initscripts, devfsd (which _IS_
> installed
> but not running) modified my lilo config to add "mount=devfsd".
>
mount=devfs dammit! Again, you are running cooker. You are expected to
follow the development. If you need installation for dummies, wait for
release.
> Requiring devfs given the number of security holes seems questionable,
but
> then again, this is not targeted as a server platform.
>
Judging by your comments, you do not fully understand what devfs is and
how it works. How can you comment on security of it?
> Mandrake: I certainly hope devfsd is _DISABLED_ in the default
_SERVER_
> installation.
>
_SERVER_? You need sound on *SERVER*? Are you kidding?
> Of course, people are not likely to need sound in a server install,
unless
> they have audio alerting of process failures <grin>.
>
Ah, O.K. now we agree :-)
-andrej
> -J.
> --
> John P. Silva [EMAIL PROTECTED]
