I can see, that openSUSE mounts cdroms (at /media) according to cd label (eg. /media/data_dvd_x).
My problem is, that several applications (eg. a cd cataloguer) expecting to find the cd at /media/cdrom0, or something similar.
Is it possible to fix it? (Tell openSUSE to mount cds at a single point)?
Dunno why I see your message in capital letters :-?
> I CAN SEE, THAT OPENSUSE MOUNTS CDROMS (AT /MEDIA) ACCORDING TO CD
> LABEL (EG. /MEDIA/DATA_DVD_X).
> MY PROBLEM IS, THAT SEVERAL APPLICATIONS (EG. A CD CATALOGUER)
> EXPECTING TO FIND THE CD AT /MEDIA/CDROM0, OR SOMETHING SIMILAR.
> IS IT POSSIBLE TO FIX IT? (TELL OPENSUSE TO MOUNT CDS AT A SINGLE
> POINT)?
I can see 2 different approaches to this:
Configuring your apps (i.e. cd cataloguer) to point the right media path
Setting up a static mount point for cd media devices
Iād say the first option is the best way as nowadays any kind of devices
tend to follow that same rule of ādynamic mount pointsā, even hard disks
are mounted by ālabelā o by āIDā.
Anyway, there is a wiki article to get the second path. Itās a bit outdated,
so not sure if is still valid for newer versions:
Perhaps because you wrote your first post in some āfancyā non-standard font instead of using
the forumās default stuff and the NNTP-reader reformatted it to upper case.
>
> Strange!
> I donāt know! It appears normally lowercased here!
No problem
I am using nntp newsreader, your message reads ok in the web forums page.
> I didnāt found any active developing catalogers with such an option.
> Iāll try again!
Oh, well⦠it should be configurable, in a way or another :-?
> I tried (with cdrom, cdrom0, scd and scd0) but didnāt worked! :messed:
> Either it doesnāt apply to v.11.1 or I messed something.
>
> Here is my mountpoints.fdi:
Iām running openSUSE 10.2. Iāve tried to mount my CDROM to a static moint point, using the wiki page SDB:Mounting to Static Mount Points - openSUSE. Iāve had no success thus far. I followed every step very carefully.
Thanks for the replies, but unfortunately this doesnāt answer my question.
Simply put I want to use a fdi file to tell HAL to also mount a cdrom as a static mount point besides the dynamic mount point /media/<volume name>.
Iām trying to use my Linux distribution as a quite simple desktop operating system, but if new destributions become as layered as Windows, I cannot see the use of using Linux as my desktop operating system. The whole idea behind the automount system controlled by HAL is to prevent the (manual) use of fstab. It seems like I have to disable the automounting feature of my cdrom and manually add the fstab entry for my cdrom. From this point of view, Mac and Windows at least implement the controversy of layer on layer on layer well. In Windows, simply type cd d:/ and voila.
This shouldnāt be so complicated. Please, does someone have a fdi file to mount a cdrom to a static mount point besides the volume automount? Why does nobody update SDB:Mounting to Static Mount Points - openSUSE
I guess cstadegaart, I donāt understand the problem you state.
Simply put I want to use a fdi file to tell HAL to also mount a cdrom as a static mount point besides the dynamic mount point /media/<volume name>.
Since, device names like /dev/cdrom and /dev/dvd are in fact static. Further, you can determine all the names for any drive by using the terminal command:
/usr/sbin/hwinfo --cdrom
Check it out. Otherwise, I donāt see the problem here.
These are not mount points, just pointers to the device file. The file system of a cdrom gets mounted as /media/<volume>. Applications which cannot access the device itself, only the mounted file system, will never be able to access the cdrom content unless /media/<volume> is accessed (and not mounted while HAL daemon was already running). But discs (in my experience) rarely have the same volume name, so a static point is preferable. Besides that, every time you remove a disk and insert a new disk, youāll have to restart the HAL daemon in order to mount the new volume name. Again in tha latter case, a static mount point is preferable.
cstadegaart, you must help me understand the problem that you are seeing with the device naming in Linux. Since I can enter static device names such as /dev/dvd into say xineās or mplayerās setup or tell KDE that the default cdrom is called /dev/cdrom, I can access these drives without a problem and I donāt need to know the disk label. Further, some programs can read a cdrom no matter its designation such as Banshee, which is a feature within the application its self.
Since disk labels are surely mostly different, there is no standard method I know of to point there for all disks, when you could have more than one optical drive installed. If you remember, Windows uses fixed drive letters, which have the same basic problem as /dev/dvd. Many Windows programs require you to specify a default DVD drive or may assign one on its own. Those Windows programs that donāt are scanning all installed drives.
In any event, due to how device names work in Linux, what problem does this cause that you can not over come? Please give examples as to how this is a problem to standard Linux applications. Now, donāt get me wrong, I am not suggesting that device naming could not somehow be better, but it almost surely up to the application on how it will deal with the resources that are presented to it in Linux. Also, since I do not claim to know all about Linux, I must apologize up front if I have missed something obvious here, which has been known to happen.
>
>Thanks for the replies, but unfortunately this doesnāt answer my
>question.
>
>Simply put I want to use a fdi file to tell HAL to also mount a cdrom
>as a static mount point besides the dynamic mount point /media/<volume
>name>.
>
>Iām trying to use my Linux distribution as a quite simple desktop
>operating system, but if new destributions become as layered as Windows,
>I cannot see the use of using Linux as my -desktop- operating system.
>The whole idea behind the automount system controlled by HAL is to
>prevent the (manual) use of fstab. It seems like I have to disable the
>automounting feature of my cdrom and manually add the fstab entry for my
>cdrom. From this point of view, Mac and Windows at least implement the
>controversy of layer on layer on layer well. In Windows, simply type cd
>d:/ and voila.
>
>This shouldnāt be so complicated. Please, does someone have a fdi file
>to mount a cdrom to a static mount point besides the volume automount?
>Why does nobody update āSDB:Mounting to Static Mount Points - openSUSEā
>(http://en.opensuse.org/SDB:Mounting_to_Static_Mount_Points?)
I offered something i thought might be useful, you blew it off. Your
choice. I find it quite impolite to continue requesting assistance if
you blow off the suggestions you get.
JosephKK, Iām very sad to read thatās youāre taking my response so personal. Maybe you should ask yourself why it gets to you. I did not blow your solution off. To be more exact, I did look into the existing rules set. But these rules do not offer me a direct solution, probably because I do not know how to change or interpret them.
jdmcdaniel3, I think I know what youāre trying to tell me. Indeed, my problem is not what you think :(. KDE applications access the the device without problems. But when a program doesnāt use KDE to access the cdrom, it depends on a mounted file system.
Step by step to illustrate my problem. In this case Iāll use a cdrom with volume name āBackup 5-3-2010ā
I insert the disk and get a popup in KDE with ārecent connected devices: OpticalDisc Backup 5-3-2010ā
I open up Dolphin and open the cdrom file listing without problems. I close the Dolphin window! Nothing in KDE is now accessing the cdrom.
After once opening the disk it looks like HAL has restarted or HAL updated something, because in the same session which is already open in Konsole, I again type ls -la /media and the output is:
Notice that .hal-mtab is updated?
6) But the device files, which are used in some way by KDE, cannot be used in Konsole:
chris@PC-Chris:~> ls -la /dev/cdrom1
lrwxrwxrwx 1 root root 3 jul 6 17:52 /dev/cdrom1 -> sr1
chris@PC-Chris:~> ls -la /dev/sr1
brw-rw----+ 1 root cdrom 11, 1 jul 6 17:52 /dev/sr1
chris@PC-Chris:~> cd /dev/sr1
bash: cd: /dev/sr1: Is geen map
What I want is to access the cdrom with a static mount point, for example /media/cdrom. The Wiki document states that it is possible to achieve this by making a FDI file. But this doesnāt work for me. And I donāt want to screw up the whole automounting system by disabling it and manually add an fstab entry for the cdrom. This is exactly not what I want to do! I want to have a static mount point for my cdrom but still use the updated HAL system integrated with KDE (hope Iām having the theory right!).
Thatās it for now. Hopefully I am still welcome to ask for any help here :).
Up until KDE 4.4, only manual mounting of CD/DVDās was possible, although this is now user-configurable at the desktop level. Hal/udev are only responsible for media detection and naming, not the actual mounting.
If youāre wanting automounting without desktop involvement (runlevel 3 for example), and require hal detection and automounting, then ivman is the utility to use.
You may have to google for more advice concerning static cdrom mount-points, but it should be possible by configuring ivmanās IvmConfigActions.xml file or similar.
Thatās it for now. Hopefully I am still welcome to ask for any help here :).
You are absolutely welcome to stay and ask questions here cstadegaart. Just remain polite and remember not everyone is having a good day.
As for the issues you have with drives, are the basics of just how Linux mounts everything to a single unified file system and so I donāt have a better answer beyond the examples and information already provided here. All drives have to get mounted some how, or they canāt be accessed. I surely donāt know just what KDE or openSUSE is doing for sure in the background, but it is OK to hope for better and you are not crazy for doing so. I might say that one still must deal with the way the system works now while constantly looking for other/better solutions. There are a lot of very smart people that use and write Linux applications and code, perhaps you will find a solution in the future.
Good luck and I hope you find what you are looking for.