A common way to use a U disk in Red Hat

USB support is the key to drive, without the drive device mount execution is certainly not. The common way to use a U disk in Red Hat is as follows

First, do not insert a U disk,/sbin/lsmod see if there is usb-storage. If not:

Cd/lib/modules/2.4.20-8/kernel/drivers/usb

For V in *.O STORAGE/*.O; Do/sbin/insmod $v; Done

Two. Here again/sbin/lsmod, should have Usbcore, USB-OHCI (or USB-UHCI, according to the motherboard chipset and different), Usb-storage, Scsi_mod and so on. Where the usb-storage state should be

(unused).

Three. Insert U disk, Non-stop/sbin/lsmod, this period usb-storage state should be initializing, lasted about half a minute, in fact, the equivalent of windows in the lower right corner of the balloon balloons:)

Four. After initialization,/SBIN/FDISK-L should be able to see the/DEV/SDA1 device. At this time, the execution of Mount/dev/sda1/mnt/udisk to succeed. If it is msdos format, and want to see Chinese, you can

Mount-t Vfat/dev/sda1/mnt/udisk-o iocharset=gb2312.

(For the convenience can/etc/fstab add a line, later can mount/mnt/udisk on the line).

Five. Strange is sometimes fdisk is not see SDA1, but can also mount on the use of the above steps to hang a U disk basically can be said to be "foolproof." Desktops, notebooks, VMware are the same.

Mkdir/mnt/usb

Mount/dev/sda1/mnt/usb

Install Linux usage on notebooks like desktop

Ps:

First check the Lsmod|grep usb-storage This is a USB-enabled module. If not, it is the device that cannot operate the USB interface.

If not, can hand work modprobe usb-storage, general view USB disk can use Fdisk-l can be very clear to see this hardware device name, than guess hardware name to be more accurate.