![](https://seccdn.libravatar.org/avatar/ef1422786dc780e25acccea52f06bff8.jpg?s=120&d=mm&r=g)
Hello list users: What is the way in openSUSE 10.3 to create permanent symlinks in /dev? Eg I want to make symlinks like /dev/modem -> /dev/ttyS0, /dev/dvdburner -> /dev/sr0 /dev/dvdrom -> /dev/sr TIA, IG HÁZTARTÁSI GÉPET szeretnél? RENDELJ MOST! AEG-ELECTROLUX gépek AKCIÓS áron ORSZÁGOS kiszállítással az ELECTROLUXshop.hu-tól http://ad.adverticum.net/b/cl,1,6022,239723,284071/click.prm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/4302315541574064a521c84aefd10a7f.jpg?s=120&d=mm&r=g)
Istvan Gabor wrote:
Hello list users:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I'll assume that none of the links you're trying to make will cause problems or confusion. If they do, it's your problem, not mine.
Eg I want to make symlinks like /dev/modem -> /dev/ttyS0,
ln -s /dev/ttyS0 /dev/modem
/dev/dvdburner -> /dev/sr0
ln -s /dev/sr0 /dev/dvdburner
/dev/dvdrom -> /dev/sr
ln -s /dev/sr /dev/dvdrom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/ef1422786dc780e25acccea52f06bff8.jpg?s=120&d=mm&r=g)
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I'll assume that none of the links you're trying to make will cause problems or confusion.
If they do, it's your problem, not mine. Is this want to be a joke? Very funny.
Eg I want to make symlinks like /dev/modem -> /dev/ttyS0,
ln -s /dev/ttyS0 /dev/modem
/dev/dvdburner -> /dev/sr0
ln -s /dev/sr0 /dev/dvdburner
/dev/dvdrom -> /dev/sr
ln -s /dev/sr /dev/dvdrom
These symlinks will be gone after reboot. See the subject: permanent symlink. IG HÁZTARTÁSI GÉPET szeretnél? RENDELJ MOST! AEG-ELECTROLUX gépek AKCIÓS áron ORSZÁGOS kiszállítással az ELECTROLUXshop.hu-tól http://ad.adverticum.net/b/cl,1,6022,239723,284071/click.prm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/4302315541574064a521c84aefd10a7f.jpg?s=120&d=mm&r=g)
Istvan Gabor wrote:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I'll assume that none of the links you're trying to make will cause problems or confusion.
If they do, it's your problem, not mine. Is this want to be a joke? Very funny.
Eg I want to make symlinks like /dev/modem -> /dev/ttyS0,
ln -s /dev/ttyS0 /dev/modem
/dev/dvdburner -> /dev/sr0 ln -s /dev/sr0 /dev/dvdburner
/dev/dvdrom -> /dev/sr ln -s /dev/sr /dev/dvdrom
These symlinks will be gone after reboot. See the subject: permanent symlink.
I forgot, /dev isn't on the root partition any more like it used to be. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/5208f59307a2705ba9811a153406f094.jpg?s=120&d=mm&r=g)
On Jan 21, 08 22:00:23 -0500, Aaron Kulkis wrote:
Istvan Gabor wrote:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I have attempted /etc/udev/rules.d/99-cdrom.conf containing: KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule" udev happily ignores this rule. I'd expect to get a /dev/cdrom symlink. But nothing is created, even after reboot. Any hints how to debug? cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Novell is committed to creating a work environment that embraces clarity." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Tue, 2008-01-22 at 12:32 +0100, Juergen Weigert wrote:
On Jan 21, 08 22:00:23 -0500, Aaron Kulkis wrote:
Istvan Gabor wrote:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Does the kernel really call the device 'dvd1'? The KERNEL name is what the kernel calls the device, not the name you would like. You don't have much control over that name. It is probably whatever the /dev/ name is before you do anything. Maybe it is something like sr0? The SYMLIMK value is what you want your link called. It can be any legal name.
udev happily ignores this rule. I'd expect to get a /dev/cdrom symlink. But nothing is created, even after reboot. Any hints how to debug?
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/5208f59307a2705ba9811a153406f094.jpg?s=120&d=mm&r=g)
On Jan 22, 08 16:48:13 +0100, Roger Oberholtzer wrote:
On Tue, 2008-01-22 at 12:32 +0100, Juergen Weigert wrote:
On Jan 21, 08 22:00:23 -0500, Aaron Kulkis wrote:
Istvan Gabor wrote:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev?
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Does the kernel really call the device 'dvd1'? The KERNEL name is what the kernel calls the device, not the name you would like. You don't have much control over that name. It is probably whatever the /dev/ name is before you do anything. Maybe it is something like sr0?
The SYMLIMK value is what you want your link called. It can be any legal name.
KERNEL=="sr0" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule" Also does nothing. sigh, Jw -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Novell is committed to creating a work environment that embraces clarity." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/11b4b3cf016b1d6a62454324eaaacc59.jpg?s=120&d=mm&r=g)
On Tuesday 22 January 2008 10:42:00 am Juergen Weigert wrote:
On Jan 22, 08 16:48:13 +0100, Roger Oberholtzer wrote:
On Tue, 2008-01-22 at 12:32 +0100, Juergen Weigert wrote:
On Jan 21, 08 22:00:23 -0500, Aaron Kulkis wrote:
Istvan Gabor wrote:
> What is the way in openSUSE 10.3 to create permanent
symlinks in /dev?
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Does the kernel really call the device 'dvd1'? The KERNEL name is what the kernel calls the device, not the name you would like. You don't have much control over that name. It is probably whatever the /dev/ name is before you do anything. Maybe it is something like sr0?
The SYMLIMK value is what you want your link called. It can be any legal name.
KERNEL=="sr0" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Also does nothing.
Maybe file 99-cdrom.conf is ignored by udev? Try /etc/udev/rules.d/99-cdrom.rules -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/5208f59307a2705ba9811a153406f094.jpg?s=120&d=mm&r=g)
On Jan 22, 08 11:34:53 -0600, Rajko M. wrote:
On Tuesday 22 January 2008 10:42:00 am Juergen Weigert wrote:
On Jan 22, 08 16:48:13 +0100, Roger Oberholtzer wrote:
On Tue, 2008-01-22 at 12:32 +0100, Juergen Weigert wrote:
On Jan 21, 08 22:00:23 -0500, Aaron Kulkis wrote:
Istvan Gabor wrote:
>> What is the way in openSUSE 10.3 to create permanent
symlinks in /dev?
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Does the kernel really call the device 'dvd1'? The KERNEL name is what the kernel calls the device, not the name you would like. You don't have much control over that name. It is probably whatever the /dev/ name is before you do anything. Maybe it is something like sr0?
The SYMLIMK value is what you want your link called. It can be any legal name.
KERNEL=="sr0" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
Also does nothing.
Maybe file 99-cdrom.conf is ignored by udev? Try /etc/udev/rules.d/99-cdrom.rules
I typed the name wrong in my email. It is already called /etc/udev/rules.d/99-cdrom.rules I know that udev reads the file, if I misspell a keyword, I get an appropriate error message in /var/log/messages. cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "Novell is committed to creating a work environment that embraces clarity." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/5a94d2f8a5845d5f1c1ea1556fc0cb72.jpg?s=120&d=mm&r=g)
On 01/22/2008 07:32 PM, Juergen Weigert wrote:
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
udev happily ignores this rule. I'd expect to get a /dev/cdrom symlink. But nothing is created, even after reboot. Any hints how to debug?
It is controlled by 60-cdrom_id.rules, which calls a program called cdrom_id, and 70-persistent-cd.rules contains the rules created by the write_cd_rules script. For example, mine is: # This file was automatically generated by the /lib/udev/write_cd_rules # program, probably run by the cd-aliases-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line # and set the $GENERATED variable. # DVD_RW_ND-3520AW (pci-0000:00:0f.1-scsi-1:0:0:0) ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1" -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Wed, 2008-01-23 at 08:19 +0800, Joe Morris (NTM) wrote:
On 01/22/2008 07:32 PM, Juergen Weigert wrote:
I have attempted /etc/udev/rules.d/99-cdrom.conf
containing:
KERNEL=="dvd1" SYMLINK="cdrom", MODE="666" OPTIONS="last_rule"
udev happily ignores this rule. I'd expect to get a /dev/cdrom symlink. But nothing is created, even after reboot. Any hints how to debug?
It is controlled by 60-cdrom_id.rules, which calls a program called cdrom_id, and 70-persistent-cd.rules contains the rules created by the write_cd_rules script. For example, mine is: # This file was automatically generated by the /lib/udev/write_cd_rules # program, probably run by the cd-aliases-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line # and set the $GENERATED variable.
# DVD_RW_ND-3520AW (pci-0000:00:0f.1-scsi-1:0:0:0) ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1" ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:0f.1-scsi-1:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
The rules files are read alphabetically. Or, numerically, in fact. The number at the beginning controls the order the rules are added. If there is no last_rule directive, udev appends each appropriate rule in the order the rules files are read. So one need not modify this file as it contains no last_rule directives. Just add a rule that will be read in later that does what is wanted. In this case, the name of the rule file should be > 60. The trick here is finding what rules are consulted for each device. The udevmonitor program is nice for pluggable devices. I have never been able to find an easy human usable method to get the same info for static devices, like a built-in cd drive. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-01-23 at 09:08 +0100, Roger Oberholtzer wrote:
The trick here is finding what rules are consulted for each device. The udevmonitor program is nice for pluggable devices. I have never been able to find an easy human usable method to get the same info for static devices, like a built-in cd drive.
Maybe there is a mtehod to tell the daemon to log things as they are done, but I don't know who calls the daemon: udevd - event managing daemon ... log_priority=value Set the internal log level of udevd. Valid values are the numerical syslog priorities or their textual representations: err, info and debug. Ah, it is "/etc/init.d/boot.udev". It uses: udevd_args="--daemon" so probably the way would be to modify that line in the script to add the log priority. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHlxMItTMYHG2NR9URAqYoAJ4pebkYKCQ0jllhNdsCnCy/e7iPdgCgj6V6 HGHVauvXe6cGWqZP1Xz4qGU= =bf2n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/54e7c145ef2402a084a020a528f109d6.jpg?s=120&d=mm&r=g)
Am Mittwoch, 23. Januar 2008 schrieb Roger Oberholtzer:
[...]. The trick here is finding what rules are consulted for each device. The udevmonitor program is nice for pluggable devices. I have never been able to find an easy human usable method to get the same info for static devices, like a built-in cd drive.
For me, the output of "udevtest /sys/block/sr0" (my built-on dvd writer) looks quite verbose. HTH Jan -- You can have peace or you can have freedom. Don't ever count on having both at once. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Wed, 2008-01-23 at 20:43 +0100, Jan Ritzerfeld wrote:
Am Mittwoch, 23. Januar 2008 schrieb Roger Oberholtzer:
[...]. The trick here is finding what rules are consulted for each device. The udevmonitor program is nice for pluggable devices. I have never been able to find an easy human usable method to get the same info for static devices, like a built-in cd drive.
For me, the output of "udevtest /sys/block/sr0" (my built-on dvd writer) looks quite verbose.
But part of the trick when debugging new rules is knowing that the name of the device in this context is /sys/block/sr0. This gets more interesting for pluggable devices. You have to know the name to find out about it. But where do you get a list of those udev-compatible complete device name in the first place? What is missing from udevtest's list is which name will be called, for example, KERNEL, when the rule is used. udevmonitor can be made to do this, but only for pluggable devices. Unless one changes daemon default startup parameters and reboots. A neat tool would be one that listed all the variables supplied to udev rules for all devices currently in the system. By combining a couple of programs and changing some system daemon options, perhaps with a boot or two added, the info can eventually be obtained. There has to be an easier way. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Mon, 2008-01-21 at 19:07 +0100, Istvan Gabor wrote:
Hello list users:
What is the way in openSUSE 10.3 to create permanent symlinks in /dev? Eg I want to make symlinks like /dev/modem -> /dev/ttyS0, /dev/dvdburner -> /dev/sr0 /dev/dvdrom -> /dev/sr
One way is in udev rules. I link /dev/gps, for example, to /dev/ttyS1, and make nice permissions with this rule: KERNEL=="ttyS1", SYMLINK="gps", MODE="666", OPTIONS="last_rule" I put this in a file called /etc/udev/rules.d/99-rsoft.rules Also, if there is no /dev/ttyS1, I do not get a symlimk that points nowhere. No device, no symlink. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/ef1422786dc780e25acccea52f06bff8.jpg?s=120&d=mm&r=g)
What is the way in openSUSE 10.3 to create permanent symlinks in /dev? Eg I want to make symlinks like /dev/modem -> /dev/ ttyS0, /dev/dvdburner -> /dev/sr0 /dev/dvdrom -> /dev/sr
One way is in udev rules. I link /dev/gps, for example, to / dev/ttyS1, and make nice permissions with this rule:
KERNEL=="ttyS1", SYMLINK="gps", MODE="666", OPTIONS="last_rule"
I put this in a file called /etc/udev/rules.d/99-rsoft.rules
Also, if there is no /dev/ttyS1, I do not get a symlimk that points nowhere. No device, no symlink.
Thanks Robert, I was thinking something similar but was afraid that my rule would interfere with the systems own rules. And I did not know 'last_rule' option. I will give a try. Thanks for your answer. IG HÁZTARTÁSI GÉPET szeretnél? RENDELJ MOST! AEG-ELECTROLUX gépek AKCIÓS áron ORSZÁGOS kiszállítással az ELECTROLUXshop.hu-tól http://ad.adverticum.net/b/cl,1,6022,239723,284071/click.prm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Aaron Kulkis
-
Carlos E. R.
-
Istvan Gabor
-
Jan Ritzerfeld
-
Joe Morris (NTM)
-
Juergen Weigert
-
Rajko M.
-
Roger Oberholtzer