Steps to manually mount a USB flash drive in GNU/Linux
Submitted by srlinuxx on Sat, 03/17/2007 - 00:52.
I recently got hold of a 1 GB USB memory stick. But when I tried to mount it in a bare bones Linux distribution (a distribution which has just enough software as is needed), it was not mounted automatically. This is because the auto mounting takes place by means of a program known as hotplug which detects the USB device that is inserted in real time and then mounts it in the desired location.
So is it possible to mount a USB device (in my case the USB stick) manually ? Yes, it is possible. The idea is that the USB ports are detected by GNU/Linux as /dev/sdax - where 'x' in sdax stands for the number of the USB port. And once the USB device is connected to the USB port of your machine, you have to mount it manually.
These are the steps I followed to successfully mount the USB memory stick on my bare bones Debian Etch machine.
What is hotplug in Linux ?
Hotplug in Linux 2.4.x is installed on bootup in /Dev. It connects USB devices coldplugged.
If your distro has Linux 2.6.x kernels added; then the boot USB installation is delayed one second for kernel 2.6.x to take over. USB devices plugged in already will not be installed. No one in Linux community explains that.
You have to reinsert the USB device to create an event of hotplug to mount the USB device automatically after hotplug(hot means power is on). Coldplug is you left the USB device connected before power is turned on.
Mepis is the first distro to use events for hotplug in Kernel 2.6.x Linux. The logic is /Dev drivers is changed to drivers udev in /usr in kernel 2.6.x.
Footnote:
Early days of Linux 2.6.x kernel created many confusion because of unionfs for data synchronization between centralized data storage solution and the priority of local distributed data storage in drams.
Then Andrew added udev and /usr drivers for ambiguous devices using DSP. Xvesa is in /dev, but Xorg is in /usr. Keyboard and mouse are in /dev. but USB device drivers are in /usr.
It took two years for distros to learn how to handle the 2.6.x kernel design. But unionfs is still not understood well enough even today; because of lack of practice in any enterprise systems.
We hope thru Novell and its enterprise venture, to get unionfs[synchronization of data in ramdisk to mainframe(local compressed drive in terabyte USB Or other hdd) data storage and back to all other ramdisks], worked out in small ethernet intranet or websites on the internet? Its really only packet creation in different systems?
What is unionfs ?
Unionfs is packet creation either ethernet or dotnet packet format with the latest data input(usually database such as mySQL) as the content of the packet. The header of the packet would have batched processing of destinations and storage instructions(broadcasting) to ramdisks and compressed drives in hdd. And the tail will have quality control of checksum and other codec version switches?