USB Mount issue: 9.2
I've noticed this in Novell Linux Desktop and SuSE 9.2. My attached USB drive mounts as: /media/usb-000000000383:0:0:0p1. That's just odd. Any idea why? Also, my SCSI card is no longer supported, it seems. My internal ZIP drive doesn't show up anywhere and I don't see my adapter in dmesg. :( -- <<JAV>>
Joe, On Thursday 18 November 2004 15:04, Joe Polk wrote:
I've noticed this in Novell Linux Desktop and SuSE 9.2. My attached USB drive mounts as: /media/usb-000000000383:0:0:0p1. That's just odd. Any idea why? Also, my SCSI card is no longer supported, it seems. My internal ZIP drive doesn't show up anywhere and I don't see my adapter in dmesg. :(
My USB flash RAM pseudo-disk mounts on "/media/usb-storage-D235281419110:0:0:0p1/". The series of letters and numbers is derived from the serial number supplied by the device itself. Consider that memory stick's entry from /proc/usb/devices: T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05dc ProdID=0080 Rev= 0.01 S: Manufacturer=LEXAR MEDIA S: Product=JUMPDRIVE S: SerialNumber=D235281419110 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms Notice the relationship between the SerialNumber entry and the name assigned to the mount point created in /media. Presumably a similar process is used to generate the name for your USB-accessed drive. The good news is that the name is stable and dependent strictly on the particular USB device you insert, so you can reliably make a symbolic link with a more convenient and humanly meaningful name. I have a symbolic link named "lexar" (the brand name of my memory stick) in the root directory that points to the entry in /media.
-- <<JAV>>
Randall Schulz
Two things:
1) This is new. I haven't seen this in previous releases so why fsck up a good
thing? hehe
2) If I put a link in, it would break when I unplugged, no? Would it relink
when it remounts? Guess so...I should try this. :)
--
<<JAV>>
---------- Original Message -----------
From: Randall R Schulz
Joe,
On Thursday 18 November 2004 15:04, Joe Polk wrote:
I've noticed this in Novell Linux Desktop and SuSE 9.2. My attached USB drive mounts as: /media/usb-000000000383:0:0:0p1. That's just odd. Any idea why? Also, my SCSI card is no longer supported, it seems. My internal ZIP drive doesn't show up anywhere and I don't see my adapter in dmesg. :(
My USB flash RAM pseudo-disk mounts on "/media/usb-storage-D235281419110:0:0:0p1/". The series of letters and numbers is derived from the serial number supplied by the device itself.
Consider that memory stick's entry from /proc/usb/devices:
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05dc ProdID=0080 Rev= 0.01 S: Manufacturer=LEXAR MEDIA S: Product=JUMPDRIVE S: SerialNumber=D235281419110 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
Notice the relationship between the SerialNumber entry and the name assigned to the mount point created in /media.
Presumably a similar process is used to generate the name for your USB-accessed drive.
The good news is that the name is stable and dependent strictly on the particular USB device you insert, so you can reliably make a symbolic link with a more convenient and humanly meaningful name. I have a symbolic link named "lexar" (the brand name of my memory stick) in the root directory that points to the entry in /media.
-- <<JAV>>
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ------- End of Original Message -------
Joe, On Thursday 18 November 2004 16:38, you wrote:
Two things: 1) This is new. I haven't seen this in previous releases so why fsck up a good thing? hehe
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
2) If I put a link in, it would break when I unplugged, no? Would it relink when it remounts? Guess so...I should try this. :)
Symbolic links don't care whether their target exists. Their existence is independent of that of their target. You can, at will, create a symbolic link to a non-existent file: % ln -s noneSuch linkToNoneSuch % ls -l linkToNoneSuch lrwxrwxrwx 1 rschulz users 8 2004-11-18 16:45 linkToNoneSuch -> noneSuch % cat linkToNoneSuch cat: linkToNoneSuch: No such file or directory % echo "noneSuch" >noneSuch % cat linkToNoneSuch noneSuch The target of a symbolic link can come and go. Use the symbolic link when its target doesn't exist and you'll get an error. Use it later when the target is present and it will work just fine. Randall Schulz
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
No I don't think you understand. It worked before. It automounted and got a
device name. It may have been /dev/sda1 or something, but that is far more
reasonable that this cryptic desi, that's my point. From a user perspective,
it's uglier than before. This, in that respect, is bad.
--
<<JAV>>
---------- Original Message -----------
From: Randall R Schulz
Joe,
On Thursday 18 November 2004 16:38, you wrote:
Two things: 1) This is new. I haven't seen this in previous releases so why fsck up a good thing? hehe
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
2) If I put a link in, it would break when I unplugged, no? Would it relink when it remounts? Guess so...I should try this. :)
Symbolic links don't care whether their target exists. Their existence is independent of that of their target. You can, at will, create a symbolic link to a non-existent file:
% ln -s noneSuch linkToNoneSuch % ls -l linkToNoneSuch lrwxrwxrwx 1 rschulz users 8 2004-11-18 16:45 linkToNoneSuch -> noneSuch % cat linkToNoneSuch cat: linkToNoneSuch: No such file or directory % echo "noneSuch" >noneSuch % cat linkToNoneSuch noneSuch
The target of a symbolic link can come and go. Use the symbolic link when its target doesn't exist and you'll get an error. Use it later when the target is present and it will work just fine.
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ------- End of Original Message -------
On Friday 19 November 2004 19:24, Joe Polk wrote:
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
No I don't think you understand. It worked before. It automounted and got a device name. It may have been /dev/sda1 or something, but that is far more reasonable that this cryptic desi, that's my point. From a user perspective, it's uglier than before. This, in that respect, is bad.
I don't think the device name has changed, has it? Isn't it just the directory on which it is mounted? I think the point of it is that since the name is derived from the USB ID of the device, it will always be the same, so you will always get it in the same location, instead of as before having it be dependant on which order things were plugged in Lots of people were complaining about especially USB and SCSI, that there was no good way of predicting where things would end up, it varied according to which order it was connected, and which order it was scanned by the drivers. This way you know at least one thing: which directory you can use to access it
Okay I'll buy that. :)
I feel, however, that I've lost some functionality. I don't get desktop links
automatically and now my SCSI card no longer works. So to have this weird
mount point too means that my experience in 9.2 has been tainted. I think the
look of KDE is great. I like those changes. But this mount point, SCSI
failure, and weird monitor behavior means overall 9.2 appears buggy.
--
<<JAV>>
---------- Original Message -----------
From: Anders Johansson
On Friday 19 November 2004 19:24, Joe Polk wrote:
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
No I don't think you understand. It worked before. It automounted and got a device name. It may have been /dev/sda1 or something, but that is far more reasonable that this cryptic desi, that's my point. From a user perspective, it's uglier than before. This, in that respect, is bad.
I don't think the device name has changed, has it? Isn't it just the directory on which it is mounted?
I think the point of it is that since the name is derived from the USB ID of the device, it will always be the same, so you will always get it in the same location, instead of as before having it be dependant on which order things were plugged in
Lots of people were complaining about especially USB and SCSI, that there was no good way of predicting where things would end up, it varied according to which order it was connected, and which order it was scanned by the drivers. This way you know at least one thing: which directory you can use to access it
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ------- End of Original Message -------
Joe, On Friday 19 November 2004 10:24, Joe Polk wrote:
Why ask why? This is the way the current auto-mounting system works. You're now free of setting up /etc/fstab entries for this class of devices (including flash RAM disks and CD/DVD drives, as well). I'm willing to call it a good thing.
No I don't think you understand. It worked before. It automounted and got a device name. It may have been /dev/sda1 or something, but that is far more reasonable that this cryptic desi, that's my point. From a user perspective, it's uglier than before. This, in that respect, is bad.
But that old scheme doesn't extend itself well. If you have more than one such portable / removable device and you want to connect them both at the same time, then assigning devices in some arbitrary order leaves you without a stable means of referring to those devices. Among other things, the assigned device is going to be dependent on the order in which the devices are attached. Using an identifier, cryptic and long though it may be, that is derived from the device itself in a unique and stable way is functionally superior, though perhaps cosmetically inferior. As I said, create a symbolic link and be done with it. You'll never run the risk of inadvertently accessing the wrong device.
-- <<JAV>>
Randall Schulz
Joe Polk wrote:
I've noticed this in Novell Linux Desktop and SuSE 9.2. My attached USB drive mounts as: /media/usb-000000000383:0:0:0p1. That's just odd. Any idea why? Also, my SCSI card is no longer supported, it seems. My internal ZIP drive doesn't show up anywhere and I don't see my adapter in dmesg. :(
-- <<JAV>>
Mine does the same thing! Why is a good question. -- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316
The Idea is to mount it in the same place no matter in which USB port you stick it in, and no matter in which order you you plug in your USB devices... This is good, probably very good, just takes getting used to... Unfortunatetly, there are some USB & Firewire devices, out there so if you use such a device it is sometime mounted under USB, and some time under where ever the firewire go... IMHO they didn't go far enough... Jerry On Friday 19 November 2004 04:20, Donn Washburn wrote:
Joe Polk wrote:
I've noticed this in Novell Linux Desktop and SuSE 9.2. My attached USB drive mounts as: /media/usb-000000000383:0:0:0p1. That's just odd. Any idea why? Also, my SCSI card is no longer supported, it seems. My internal ZIP drive doesn't show up anywhere and I don't see my adapter in dmesg. :(
-- <<JAV>>
Mine does the same thing! Why is a good question.
-- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316
participants (5)
-
Anders Johansson -
Donn Washburn -
Jerry Westrick -
Joe Polk -
Randall R Schulz