Attachment 86662 Details for Bug 111551 – external-devices.xml

external-devices.xml

external-devices.xml (text/plain), 10.14 KB, created by Dimitry Bradt (RETIRED) on 2006-05-12 10:50:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dimitry Bradt (RETIRED)

Created: 2006-05-12 10:50:59 UTC

Size: 10.14 KB

patch

obsolete

><?xml version="1.0" encoding="UTF-8"?>
><!DOCTYPE guide SYSTEM "www.gentoo.org/dtd/guide.dtd">
>
>
><guide link="external-devices.xml" lang="en">
><title>Gentoo Documentation Guide</title>
>
><author title="Author">
> <mail link="diox@swords.be">Dimitry bradt</mail>
></author>
>
><abstract>
>	This howto will show you how to use external (usb/firewire) storage devices
></abstract>
>
>
>
><license/>
>
><version>1.0</version>
><date>2006-05-12</date>
>
><chapter>
><title>HAL/pmount</title>
><section>
><title>Info</title>
><body>
>
>Hardware Abstraction Layer. It provides an easy way for applications to discover the hardware 
>on the system.
>
>HAL is a hardware abstraction layer, which is a piece of software that provides a view of 
>the various hardware attached to a system. In addition to this, HAL keeps detailed metadata 
>for each piece of hardware and provides hooks such that system and desktop-level software
>can react to changes in the hardware configuration in order to maintain system policy.
>
>The most important goal of HAL is to provide plug-and-play facilities for UNIX-like desktops 
>with focus on providing a rich and extensible description of device characteristics and 
>features. One example of the functionality provided by HAL is when you plug in a USB storage 
>device. HAL can automatically create an appropriate entry in the /etc/fstab file and create 
>the corresponding mount point in /mnt.
><uri>extra info : http://www.ometer.com/hardware.html</uri>
>
>
></body>
></section>
><section><title>configuring HAL</title>
><body>
>Before emerging the needed programs you should enable KOBJECT_UEVENT and CONFIG_HOTPLUG in your kernel. Search after these options with "/", or adapt the .config located in /usr/src/linux/.config 
><pre caption="/usr/src/linux/.config">
><var>KOBJECT_UEVENT=y</var>
><var>CONFIG_HOTPLUG=y</var>
></pre>
> Before emerging you need to enable the hal use flag.
><pre caption="enable 'hal' use flag">
># euse -E hal
># emerge -v hal dbus hotplug
># rc-update add dbus default
># /etc/init.d/dbus start
># rc-update add hald default
># /etc/init.d/hald start
></pre>
> Instead of configuring our software; we could just use some applications to do this for us. 
><pre caption="autoconf software">
># echo "sys-apps/pmount ~x86" >> /etc/portage/package.keywords
># emerge -v pmount
># emerge -v ivman
></pre>
>
>Now your window manager automaticly asks you to mount your external devices.
>The only thing we could renice is let hal make symlinks of our devices.
>We do this by making sure it is owned by group hal.
>
><pre caption="/etc/udev/rules.d/hal.rules">
>BUS=="usb", SYSFS{serial}=="123456789011121314", SYSFS{product}=="JUMPDRIVE", KERNEL=="sd?1", NAME="%k", SYMLINK="usbdrive", GROUP="hal"
>BUS=="usb", SYSFS{manufacturer}=="Sony", SYSFS{product}=="PSP Type A", KERNEL=="sd?1", NAME="%k", SYMLINK="psp", GROUP="hal"
>BUS=="usb", SYSFS{manufacturer}=="Apple", SYSFS{product}=="iPod", KERNEL=="sd?2", NAME="%k", SYMLINK="ipod", GROUP="hal"
></pre>
><pre caption="/etc/fstab">
>/dev/usbdrive /mnt/usbdrive auto noauto,rw,user 0 0
>/dev/ipod /mnt/ipod auto noauto,rw,user 0 0
>/dev/psp /mnt/psp auto noauto,rw,user 0 0
></pre>
></body>
></section>
></chapter>
><chapter><title>external storage posibilities</title>
><section><title>configuring the kernel</title>
><body>
> Make sure the options below are marked like said below in your kernel config.
><pre caption="configuring your kernel">
># vim /usr/src/linux/.config
>MSDOS_FS=y
>VFAT_FS=y
>BLK_DEV_SD=y
>CHR_DEV_ST=y
>CHR_DEV_SG=y
>USB_STORAGE=y
>USB_UHCI_HCD=y
>USB_OHCI_HCD=n
></pre>
></body>
></section>
><section>
><title>build the kernel</title>
><body>
><pre caption="installing your new kernel">
># make
># mount /boot/
># cp arch/<const>your arch</const>/boot/bzImage /boot
></pre>
>now you should reboot and move further from this point after you reboot
></body>
></section>
><section><title>checking if hotplug detected your devices well</title>
><body>
><pre caption="check dmesg">
># dmesg | grep usb-storage
></pre>
><pre caption="modprobe your device if not loaded">
>usb.c: USB device 4 (vend/prod 0xdda/0x2005) is not claimed by any active driver.
></pre>
>you can do this automaticly by putting your driver name in 
>/etc/modules.autoload.d/kernel-2.{4|6}.
>
><pre caption="for scsi interface">
># emerge sg3_utils
># Description: apps for querying the sg SCSI interface (contains rescan_scsi_bus.sh)
></pre>
><pre caption="mounting the drive">
># mkdir /mnt/usbstick
># mount -t vfat /dev/sda1 /mnt/usbstick
></pre>
>
>If you can't mount then try the alternative kernel config above that enables SCSI 
>generic support. Then run the following that should give you the correct device name. 
>You can now mount with the correct name (Eg. /dev/sdb1). You can also try with auto or 
>msdos (for small cards) as the filesystem type (mount -t msdos /dev/x /mnt/x).
>
><pre caption="looking for firewire devices">
># sg_scan -i
># sg_map
></pre>
></body>
></section>
></chapter>
><chapter><title>editing your fstab</title>
><section><title>mounting your external usb-devices</title>
><body>
><pre caption="/etc/fstab">
># MY USB STICK
>/dev/sda1 /mnt/stick vfat noauto,user,exec,sync 0 0
></pre>
>
>please note that you have to use vfat in the fstab file, because if you choose auto you won't 
>get the full name but only the first 8 chars. Add the option "sync" to have synchronous changes
>between the actual usb mass storage device and the place that it's been mounted. Otherwise it 
>would be done while you unmount it. This has the advantage of not losing data if you forgot to 
>unmount a device and also you would see how long it will take when you are transfering data to 
>it. You don't need to use vfat in the fstab file as long as /etc/filesystems is set up properly.
>
></body>
></section><section><title>configuring your filesystems</title>
><body>
>
>Specifically, if vfat exists in /etc/filesystems before other fat file systems or by itself 
>with an asterisk on the last line, it will be tried first during a mount. Read the mount (8) 
>man page for more details. 
>
><pre caption="/etc/filesystems">
>#
># This file defines the filesystems search order used by a
># 'mount -t auto' command.
>#
># Uncomment the following line if your modular kernel has vfat
># support and you want mount to try vfat.
>vfat
># Uncomment the following line if your modular kernel has udf
># support and you want mount to try udf before iso9660.
>udf
># Keep the last '*' intact as it directs mount to use the
># filesystems list available at /proc/filesystems also.
># Don't remove it unless you REALLY know what you are doing!
>*
></pre>
></body>
></section>
></chapter>
><chapter><title>Mounting your windows partitions</title>
><section><title>the different filesystem types</title>
><body>
><pre caption="mount -t type device mountpoint">
># mount -t ntfs /dev/hda1 /mnt/win
># mount -t vfat /dev/hda2 /mnt/data
></pre>
></body>
></section>
><section>
><title>user permissions</title>
><body>
>
>On all three filesystems (MS-DOS, VFAT, NTFS), mount lets you pass the uid and gid options, 
>which let you set the user and group IDs of who the files are chown'd to when the filesystem 
>is mounted. To find out the values for uid and gid, run id $user. 
>
>umask: octal file permissions
>You can change permissions using the parameter umask. But be aware that it must be the bitmask of permissions that are not present for the mountpoint. It is an octal number, formed like this:
> * character '0': Indicates that this is an octal number, not decimal.
> * first digit: owner user permissions
> * second digit: owner group permissions
> * third digit: world permissions (every other user on the system) 
>
><pre caption="/etc/fstab">
>#my windows partition
>/dev/hda1 /mnt/ntfs ntfs uid=1000,gid=100 0 0
></pre>
>
>*utf8
>You may also add utf8 option, if you can't see some files with international characters 
>in filenames.
>e.g. /etc/fstab : /dev/hda1 /mnt/vfat vfat ro,utf8 0 0
>
><pre caption="see more?">
>for more options : 
># man mount(8)
></pre>
></body>
></section>
><section><title>
>captive ntfs</title>
><body>
>We need 'sys-fs/captive' (Description: Captive uses binary Windows drivers for full NTFS r/w access.) to get this to work. For now Captive is masked so you need to unmask it first
><pre caption="/etc/portage/package.keywords">
># echo "sys-fs/captive ~x86" >> /etc/portage/package.keywords
></pre>
>let's emerge captive now
><pre caption="emerge captive">
># emerge captive
></pre>
>Now load the apropriate kernel module and make it load at boot
><pre caption="loading the apropriate kernel module">
># modules-update
># modprobe fuse
># echo "fuse" >> /etc/modules.autoload.d/kernel-2.6
></pre>
> Congrats; Captive is now installed. To acquire the necessary filesystems drivers you should run the following command to locate your ntfs drives in a nice wizard. You should choose to download the propriate drivers from microsoft.com (You need a Windows SP2 license to do this legal.)
>(It doens't matter if your partitions are mounted or not; The programm looks for itself after the right partitions.) Caution : you need X-windows for this app.
><pre caption="acquire the necessary filesystems">
># captive-install-acquire
></pre>
> After you walked through the wizard you should now be able to mount your windows partitions read/write. 
><pre caption="remount your windows partitions">
># umount /mnt/win
># mount -t captive-ntfs /dev/hda1 /mnt/win
></pre>
>If the following works without errors you may want to put it in your /etc/fstab
><pre caption="/etc/fstab">
>/dev/hda2 /windows captive-ntfs users 0 0
></pre>
> Caution : You'll need to recompile fuse if you update your kernel !
><pre caption="after kernel update">
># modprobe -r fuse
># emerge sys-fs/fuse
># modules-update
># modprobe fuse
></pre>
></body>
></section>
></chapter>
></guide>

Actions: View

Attachments on bug 111551: 86657 | 86658 | 86660 | 86661 | 86662 | 86663 | 86664 | 86665 | 86671 | 86672 | 86673 | 91810 | 91823 | 91834 | 91841 | 92348 | 92655 | 92656 | 92708 | 92712