Re: [Cooker] what am I supposed to be doing with devfs these days?
Will Smith wrote: 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. You can't remoce devfsd because it is requires by kernel. If you do not want to use devfs do not mount it. Very simple. It is not mounted by default so almost the only difference between old and new kernel is /proc/partitions that is using new names even if devfs is not mounted. Or does new kernel mount devfs by default? -andrej
Re: [Cooker] what am I supposed to be doing with devfs these days?
Le Vendredi 17 Août 2001 06:29, vous avez écrit : Will Smith wrote: 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. You can't remoce devfsd because it is requires by kernel. If you do not want to use devfs do not mount it. Very simple. It is not mounted by default so almost the only difference between old and new kernel is /proc/partitions that is using new names even if devfs is not mounted. that's why I use --nodeps, and It works fine. The only drawback for the new kernel : theses sh.. of nvidia drivers that completly hang my system, even if I use agpgart. So 2 soluces : stick with the kernel-2.4.3-20mdk for 3D, or use 2.4.x-ymdk (with x 3) but use nv drivers (no 3D). If I'have to reboot in order to have 3D, I'd rather boot under windows. I think I will use cooker kernel with devfsd enable and nv drivers and boot under windows for 3D and Games, unfortunately. Or does new kernel mount devfs by default? -andrej -- Copyleft Faber's prod. 2001 Powered by Linux Mandrake 8.0
Re: [Cooker] what am I supposed to be doing with devfs these days?
Will Smith wrote: Le Vendredi 17 Août 2001 06:29, vous avez écrit : Will Smith wrote: 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. You can't remoce devfsd because it is requires by kernel. If you do not want to use devfs do not mount it. Very simple. It is not mounted by default so almost the only difference between old and new kernel is /proc/partitions that is using new names even if devfs is not mounted. that's why I use --nodeps, and It works fine. You missed the point. devfsd has *nothing* to do with the fact that you are actualy using devfs. See reply of Pixel - now they mount devfs by default. Actually in this case if you remove devfsd you are in much worse situation - devfsd provides you with compatibility device names that are missing with devfs pure. The only drawback for the new kernel : theses sh.. of nvidia drivers that completly hang my system, even if I use agpgart. You mean, nVidia works without devfs but hangs with devfs? With all other conditions alike? Too bad for them. Have you tried bug report? (Yes, they normally do not answer, but they do fix bugs. Of course, it may take awhile). I think I will use cooker kernel with devfsd enable and nv drivers and boot under windows for 3D and Games, unfortunately. Not devfsd, for God's sake! :-) Remove devfs=mount from boot flags and see if it helps. -andrej
Re: [Cooker] what am I supposed to be doing with devfs these days?
Pixel wrote: Borsenkow Andrej [EMAIL PROTECTED] writes: Or does new kernel mount devfs by default? drakx now add devfs=mount to the kernel cmdline, so even if kernel doesn't do it by default... Is it configurable? Looks like it belongs to drakboot ... Or, if you want to force it, why not just compile kernel with DEVFS_MOUNT? -andrej
Re: [Cooker] what am I supposed to be doing with devfs these days?
Borsenkow Andrej [EMAIL PROTECTED] writes: Or does new kernel mount devfs by default? drakx now add devfs=mount to the kernel cmdline, so even if kernel doesn't do it by default...
Re: [Cooker] what am I supposed to be doing with devfs these days?
On Wed, Aug 15, 2001 at 09:42:37AM -0400, Brian J. Murrell wrote: 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? Coz of hotplug I think you need devfs ... -- Geoffrey Lee [EMAIL PROTECTED] 李長風 http://www.wychk.org/~glee $ /usr/games/fortune Anything that can go wrong will go Segmentation fault (core dumped) $
Re: [Cooker] what am I supposed to be doing with devfs these days?
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
Re: [Cooker] what am I supposed to be doing with devfs these days?
On Wed, 15 Aug 2001, Will Smith wrote: 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 When I first saw devfsd, I loved the idea. But after seeing how hard it was to actually use, I haven't touched it since, and hopefully I won't have to anytime soon. -- Sincerely, David Walluck [EMAIL PROTECTED]
