The following procedure worked instantly on Ubuntu 12.04:
REMARK:
The df
command shows that /dev/sdd show that d the last assigned drive in use. I need to know this to find the next available one, which is used in the subsequent sudo mount ...
command. In my case, the next drive will be /dev/sde .
You will need to determine the correct drive for your own system. For example, you might have /dev/sda, or sdb, or sdc.
So, first, to see the drive information:
df
Next, run mkdir
and mount
:
mkdir /mt/ee1
sudo mount -t vfat /dev/sde /mt/ee1 -o uid=1000
For automatic execution at boot time, I normally use Perl scripts, which detect and adapt automatically and give stable names to the partitions.
I do not need this at this point of time for floppies, and therefore I didn't optimize it. Perhaps the command "mount ...
" is not optimal....)
A more general but a bit primitive solution would be to create a bash/batch file with multiple lines as above with sudo...
, with the several probable possible variants /dev/sd...
on the specific PC.
Then there might be a call of this file in the settings of "Startup Applications".
I did not test this.
In addition, this does not deal with the aspect of removing or inserting a different floppy disk. This could be done in some automatic or at least semi-automatic manner....
I do not know if the way above is optimal. I just wanted to add helpful information, after having settled my own problem with the preceding answers.
unetbootin
is probably the best and the easiest way to make a bootable USB irrespective of the OS you are using to create the USB as it is crossplatform.
It has a very easy interface and options to choose between distributions straightaway from the menu and to select the desired iso image.
Also,creating a bootable USB using Unetbootin will give you a very very simple and easy interface when you boot your machine using the USB.
I would suggest to use this software straightaway without doubt...
Best Answer
/lib/modules/$(uname -r)/modules.alias
for the complete list.) These will look different based on the hardware interface. For example,pci:v0000102Bd00002527sv*sd*bc*sc*i*
for a PCI device vendor 102B, device 2527, and anything for subvendor, etc, or USB:usb:v2040p4982d*dc*dsc*dp*ic*isc*ip*
.udev
in userspace.udev
matches the notification against its list of rules in/lib/udev/rules.d/
and/etc/udev/rules.d
. From here, the behavior is extremely specialized, based on the rules.80-udisks.rules
file is likely the best place to work from. These rules will use things like blkid and other helpers to probe the type and contents of a disk, populating all sort of configuration values including things likeENV{UDISKS_PRESENTATION_HIDE}="1"
to ignore a disk for some reason. See "man 7 udisks" for details./usr/share/polkit-1/actions/org.freedesktop.udisks.policy
. (Who can mount, umount, etc.)DCIM
is found on a filesystem.