-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Thursday 2007-02-01 at 13:32 -0600, Stevens wrote:
> On Thursday 01 February 2007 13:07, jdd wrote:
> > Stevens wrote:
> > > Yast was always able to read the DVD. That is not the problem. The
> > > problem is that hal cannot, therefore the DVD cannot be accessed by
> > > any other program EXCEPT Yast.
> >
> > hal have nothing mandatory.
> >
> > for years I used a kde icon, linked to fstab that opened any drive and
> > had a (right button) eject to do the job.
but now there is udev, its different.
> >
> > and video dvd don't have to be mounted to be played, mounting them is
> > only usefull to copy the files
> >
> True, up to a point. "Mounted" in this case means a process that allows the
> system to recognize that the drive and it's media are there and usable.
> This is what is not happening here. If that is not hal's job, then some
> other - unknown to me - process is not working correctly. The bottom line
> is that this system does not work as Suse designers think that it should.
I think you are right.
Hal is responsible to report the hardware to the OS (more or less). Then
udev creates the device nodes on the fly under /dev. If you don't have a
device node for your dvd there, even if you don't need to mount it to see
a movie dvd, you will not be able to watch it, nor do any thing with it.
The dvd does not exist, as far as the OS is concerned.
You could try to manually create the node (mknod), but I don't think that
will work. It did not work for me with a somewhat similar problem.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFFwqpgtTMYHG2NR9URAhq1AJ9TRciAWsSmPbSGlvYbnrm+NjAVzACfa6X3
35WhhMONNzIh4H+l/XxKoqY=
=OjCM
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
