Le Mercredi 15 Ao�t 2001 09:42, vous avez �crit :
> I am confused. devfs has been staunchly rejected by the Cooker team
> in the past. Now devfsd is a requirement of the latest kernels. Are
> up-to-date Cooker machines supposed to be using devfs[d] or not?
If you don't want to use DevFS, remove the devfsd package :
$]$ rpm -e --nodeps devfsd
normally everything will be fine.
But you're right.
I'm thinking about nvidia users, often gamers a little newbie under linux (
people mdk aim to have). They install a mdk 8.1, and after install the nvidia
drivers, all is fine. A reboot later : NOTHING because devfs delete the
nvidia device. If nobody say that they have to remove this package ...
On top of that it's a pain !
Why the H... did mdk team make devfsd as a reqsuire for kernel ? it's better
to make it be optionnal
>
> I get the following error while trying to use arecord:
>
> [brian@pc brian]$ arecord -t 21600 -m -r -d 2 >/dev/null
> Arecord: version 0.5.10 by Jaroslav Kysela <[EMAIL PROTECTED]>
> Error: unable to obtain longname: No such file or directory
>
> and here is why:
>
> [brian@pc brian]$ strace -f arecord -t 21600 -m -r -d 2 >/dev/null
> execve("/usr/bin/arecord", ["arecord", "-t", "21600", "-m", "-r", "-d",
> "2"], [/* 44 vars */]) = 0 uname({sys="Linux", node="pc", ...}) = 0
> ..
> getpid() = 28365
> write(2, "Arecord: version 0.5.10 by Jaros"..., 59Arecord: version
> 0.5.10 by Jaroslav Kysela <[EMAIL PROTECTED]>
> ) = 59
> open("/dev/snd/controlC0", O_RDWR) = -1 ENOENT (No such file or
> directory) open("/dev/snd/controlC0", O_RDONLY) = -1 ENOENT (No such
> file or directory) open("/dev/aloadC0", O_RDONLY) = -1 ENOENT (No
> such file or directory) close(-1) = -1 EBADF
> (Bad file
> descriptor)
> open("/dev/snd/controlC0", O_RDWR) = -1 ENOENT (No such file or
> directory) write(2, "Error: unable to obtain longname"..., 60Error: unable
> to obtain longname: No such file or directory ) = 60
> _exit(1) = ?
>
> [brian@pc brian]$ ls -l /dev/snd
> ls: /dev/snd: No such file or directory
>
> So my ALSA devivces have disappeard. Is that because I am supposed to
> be mounting devfs and running devfsd? If not, what is supposed to
> create those devices. They don't seem to exist in the latest "dev"
> package.
>
> b.
--
Copyleft Faber's prod. 2001
Powered by Linux Mandrake 8.0