I am working on an Ubuntu Linux 8.10 system that I do not want to reboot. For some reason, USB flash drives (mass storage devices) now no longer automount. I want to restore that functionality without rebooting. I can manually mount and unmount these things by doing:
I don't seem to be able to see the USB drive thing recognized in lsusb:
When I newly attach one of these things, I get this in my dmesg:
Hello all..
I have a Verbatim 2 GB flash drive. I also have Solaris 10 running on my workstation. If I am in the Windows environment, it detects the flash drive. But when I plug it while I am in solaris, nothing happens. How will solaris 10 detect my flash drive? What do I have to do?
any... (4 Replies)
hello forum..
i am using RHEL 4.0 and my system is dual boot.normally the usb flash drive should be auto mount , but in my system i am unable to mount the drive plz help...
i am a new user so plz give me in detail.
thank u in advance. (5 Replies)
Where can I get a driver that support usb flash drives for my unix machines. I need a solution to transfer data easily for techs. I am running C3750 and c8000 HP equipment.
Or is there a way to mount them and use them without adding drivers? thanks! (0 Replies)
Can someone help me with instructions on how to access a USB flash drive in SCO Unix 5.0.5? I need to copy ASCII text files that have been zipped onto the USB drive for transfer to a Windows computer. (0 Replies)
I wanna install grub on my flash drive for rescue usage.
My computer installs winxp, and I have fedora12 installed in vmware. I did like this:
step1: format the flash drive as FAT in winXP.
step2: in fedora12, mount the flash drive on /media/flash
step3: excute the command: grub-install... (10 Replies)
Dear friends,
I have the DVD image of solaris 10 but I don't have DVD writer to burn it onto a dvd R. I was wondering if I could install Solaris from my 4gb usb flash drive as my PC supports booting from usb. I have installed Windows 7 this way recently, I have no idea about Solaris. Could you... (2 Replies)
Hello All,
I faced a unique issue. I have written a script for transferring backup data on my host machine to a USB Flash drive. The Flash drive must be of 16GB size. So, my script creates two primary partitionon the USB flash drive. I require approx 5900 cylinders for the first partition on... (8 Replies)
I have a HP Proliant N40L server and in the internal USB socket I have a 16GB HP v195b flash drive on which I have a full copy of Debian installed from a copy of the DVD1 ISO image.
In as far as installation and operation goes my setup works okay, but I keep experiencing corruption of the file... (0 Replies)
Discussion started by: mij
0 Replies
LEARN ABOUT SUSE
udisks
UDISKS(7) udisks UDISKS(7)NAME
udisks - Storage Management
DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the
org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit.
DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include:
UDISKS_PRESENTATION_HIDE
If set to 1 this is a hint to presentation level software that the device should not be shown to the user.
UDISKS_PRESENTATION_NOPOLICY
If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g.
components of a multi-disk device).
UDISKS_DISABLE_POLLING
If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by
themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled.
UDISKS_PRESENTATION_NAME
The name to user for the device when presenting it to the user.
UDISKS_PRESENTATION_ICON_NAME
The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification.
The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main
block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media.
ID_DRIVE_EJECTABLE
Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media.
In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1)
since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property
is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered
ejectable).
ID_DRIVE_DETACHABLE
Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for
detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is
detachable (currently only devices connected through USB are detachable).
ID_DRIVE_CAN_SPINDOWN
Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down)
since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to
determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down).
ID_DRIVE_FLASH
The device is compatible with flash.
ID_DRIVE_FLASH_CF
The device is compatible with Compact Flash.
ID_DRIVE_FLASH_MS
The device is compatible with Memory Stick.
ID_DRIVE_FLASH_SM
The device is compatible with SmartMedia.
ID_DRIVE_FLASH_SD
The device is compatible with SecureDigital.
ID_DRIVE_FLASH_SDHC
The device is compatible with High-Capicity SecureDigital.
ID_DRIVE_FLASH_MMC
The device is compatible with MultiMediaCard.
ID_DRIVE_FLOPPY
The device is compatible with floppy disk.
ID_DRIVE_FLOPPY_ZIP
The device is compatible with Zip.
ID_DRIVE_FLOPPY_JAZ
The device is compatible with Jaz.
The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically
set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set.
ID_DRIVE_MEDIA_FLASH
The physical media currently inserted into the device is flash.
ID_DRIVE_MEDIA_FLASH_CF
The physical media currently inserted into the device is Compact Flash.
ID_DRIVE_MEDIA_FLASH_MS
The physical media currently inserted into the device is Memory Stick.
ID_DRIVE_MEDIA_FLASH_SM
The physical media currently inserted into the device is SmartMedia.
ID_DRIVE_MEDIA_FLASH_SD
The physical media currently inserted into the device is SecureDigital.
ID_DRIVE_MEDIA_FLASH_SDHC
The physical media currently inserted into the device is High-Capicity SecureDigital.
ID_DRIVE_MEDIA_FLASH_MMC
The physical media currently inserted into the device is MultiMediaCard.
ID_DRIVE_MEDIA_FLOPPY
The physical media currently inserted into the device is floppy disk.
ID_DRIVE_MEDIA_FLOPPY_ZIP
The physical media currently inserted into the device is Zip.
ID_DRIVE_MEDIA_FLOPPY_JAZ
The physical media currently inserted into the device is Jaz.
REMOTE CLIENTS
TODO: write me.
AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others.
BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at
http://bugs.freedesktop.org/enter_bug.cgi?product=udisks.
SEE ALSO udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1)udisks March 2008 UDISKS(7)