ndt-users list created

[Scott Fringer <>]

Richard;
  Alas, dmesg is empty and messages and syslog have no entries
pertaining to any USB drives being mounted.
  I followed your steps given to Clarke, and while it *appears* to have
mounted the drive (I was required to supply a fstype to the mount
command - and chose usbfs) - but I cannot write to the device.  Again,
the USB drive is connected prior to powering on the system.

Scott

Richard Carlson wrote:
> Hi Scott;
> 
> OK, make sure that sda1 is the right drive.  Look at the message log or
> use the dmesg command to find out what drive is actually installed.  For
> example, on my home system with multiple USB ports plugging a drive into
> the front port gets me
> usb 1-8: new high speed USB device using ehci_hcd and address 4
> usb 1-8: configuration #1 chosen from 1 choice
> scsi5 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 4
> usb-storage: waiting for device to settle before scanning
>   Vendor: LEXAR     Model: JUMPDRIVE ELITE   Rev: 1000
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> SCSI device sdg: 252928 512-byte hdwr sectors (129 MB)
> sdg: Write Protect is off
> sdg: Mode Sense: 43 00 00 00
> sdg: assuming drive cache: write through
> SCSI device sdg: 252928 512-byte hdwr sectors (129 MB)
> sdg: Write Protect is off
> sdg: Mode Sense: 43 00 00 00
> sdg: assuming drive cache: write through
>  sdg: sdg1
> sd 5:0:0:0: Attached scsi removable disk sdg
> sd 5:0:0:0: Attached scsi generic sg6 type 0
> usb-storage: device scan complete
> SELinux: initialized (dev sdg1, type vfat), uses genfs_contexts
> 
> So I the drive is now sdg1 not sda1.  A properly functioning automount
> system would simplify this.  .-)
> 
> Rich