On 03/11/2016 10:34 PM, Linda Walsh wrote:
There is NO NEED FOR AN ENTRY IN /etc/fstab !!
Oh? I didn't see him give any of the 'user' options on his mount option besides which they wouldn't work unless he was root.
I stand by my statement that there is no need for an entry in /etc/fstab for pluggable devices such as USB sticks. The kernel sees the 'event' of the USB stick being inserted and triggers udev for the appropriate rules. The stick gets mounted under /run/media I forget when this was introduced to the kernel, but it pre-dates the kernel distributed with 13.1 and I doubt very much it has been removed as it still works with my 4.4 kernels. You can demonstrate this quite easily by doing a 'tail -f /var/log/messages' while inserting and removing a USB stick **WITHOUT THERE BEING AN ENTRY FOR USB IN THE /etc/fstab**. Not all systems seem to have the necessary udev rules, it seems the Pi lacks them: http://www.axllent.org/docs/view/auto-mounting-usb-storage/ For example, I get 2016-03-12T12:13:40.856891-05:00 Mainbox kernel: [174321.320028] usb 1-4: new high-speed USB device number 6 using ehci-pci 2016-03-12T12:13:40.988721-05:00 Mainbox mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4" 2016-03-12T12:13:40.988935-05:00 Mainbox kernel: [174321.452880] usb 1-4: New USB device found, idVendor=abcd, idProduct=1234 2016-03-12T12:13:40.988942-05:00 Mainbox kernel: [174321.452887] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2016-03-12T12:13:40.988944-05:00 Mainbox kernel: [174321.452891] usb 1-4: Product: 2016-03-12T12:13:40.988945-05:00 Mainbox kernel: [174321.452894] usb 1-4: Manufacturer: General 2016-03-12T12:13:40.988946-05:00 Mainbox kernel: [174321.452898] usb 1-4: SerialNumber: Љ 2016-03-12T12:13:40.988948-05:00 Mainbox kernel: [174321.453311] usb-storage 1-4:1.0: USB Mass Storage device detected 2016-03-12T12:13:40.988949-05:00 Mainbox kernel: [174321.453453] scsi host10: usb-storage 1-4:1.0 2016-03-12T12:13:41.005765-05:00 Mainbox mtp-probe: bus: 1, device: 6 was not an MTP device 2016-03-12T12:13:41.988901-05:00 Mainbox kernel: [174322.452798] scsi 10:0:0:0: Direct-Access General 5.00 PQ: 0 ANSI: 2 2016-03-12T12:13:41.988922-05:00 Mainbox kernel: [174322.453097] sd 10:0:0:0: Attached scsi generic sg3 type 0 2016-03-12T12:13:41.988924-05:00 Mainbox kernel: [174322.453652] sd 10:0:0:0: [sdb] 7987200 512-byte logical blocks: (4.09 GB/3.81 GiB) 2016-03-12T12:13:41.988926-05:00 Mainbox kernel: [174322.454371] sd 10:0:0:0: [sdb] Write Protect is off 2016-03-12T12:13:41.988927-05:00 Mainbox kernel: [174322.454378] sd 10:0:0:0: [sdb] Mode Sense: 0b 00 00 08 2016-03-12T12:13:41.988928-05:00 Mainbox kernel: [174322.455024] sd 10:0:0:0: [sdb] No Caching mode page found 2016-03-12T12:13:41.988929-05:00 Mainbox kernel: [174322.455027] sd 10:0:0:0: [sdb] Assuming drive cache: write through 2016-03-12T12:13:41.996981-05:00 Mainbox kernel: [174322.461779] sdb: sdb1 2016-03-12T12:13:42.000951-05:00 Mainbox kernel: [174322.465020] sd 10:0:0:0: [sdb] Attached SCSI removable disk 2016-03-12T12:13:42.281331-05:00 Mainbox kernel: [174322.747787] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. 2016-03-12T12:13:42.291391-05:00 Mainbox udisksd[24555]: Mounted /dev/sdb1 at /run/media/anton/88D8-01F5 on behalf of uid 501 which is followed by my KDE Device Notifier producing a popup from my bottom panel, as I described in my earlier email, asking me what I want to do with this new device. Similarly I can simply pull that disk, but the 'unmounting' may not necessarily be reliable. I repeat, for pluggable devices THERE IS NO NEED FOR AN ENTRY IN /etc/fstab -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org