Attachment 91810 Details for Bug 111551 – external-devices.diff

[patch] external-devices.diff

external-devices.diff (text/plain), 17.14 KB, created by Dimitry Bradt (RETIRED) on 2006-07-15 11:54:49 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dimitry Bradt (RETIRED)

Created: 2006-07-15 11:54:49 UTC

Size: 17.14 KB

patch

obsolete

>--- old-ed.xml	2006-07-15 20:53:17.000000000 +0200
>+++ external-devices.xml	2006-05-12 23:10:40.000000000 +0200
>@@ -1,156 +1,149 @@
> <?xml version="1.0" encoding="UTF-8"?>
>+
>+<!DOCTYPE guide SYSTEM "guide.dtd">
> 
>-<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
>-
>-<guide link="/doc/en/external-devices.xml">
>+<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.
>+	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>
> 
> <p>
>-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
>+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.
> </p>
> 
> <p>
> 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 <path>/mnt</path>. Extra info:
>-<uri>http://www.ometer.com/hardware.html</uri>
>+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. Extra info : <uri>http://www.ometer.com/hardware.html</uri>
> </p>
>-
> </body>
> </section>
> <section>
> <title>configuring HAL</title>
> <body>
> 
> <p>
>-Before emerging the needed programs you should enable <c>KOBJECT_UEVENT</c> and
>-<c>CONFIG_HOTPLUG</c> in your kernel. Search after these options with <c>/</c>,
>-or adapt the <path>.config</path> located in
>-<path>/usr/src/linux/.config</path>.
>+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.
> </p>
> 
> <pre caption="/usr/src/linux/.config">
> <var>KOBJECT_UEVENT=y</var>
> <var>CONFIG_HOTPLUG=y</var>
> </pre>
> 
> <p> 
>-Before emerging you need to enable the <c>hal</c> USE flag.
>+Before emerging you need to enable the hal use flag.
> </p>
> 
> <note>
>-You could also emerge <c>kde-base/kioslaves</c> with the <c>hal</c> USE flag.
>-KDE Has make some nice hal support. Read more at
>+You could also emerge <c>kde-base/kioslaves</c> with the <c>hal</c> use flag.
>+KDE Has make some nice hal support. Read more at 
> <uri>http://wiki.kde.org/tiki-index.php?page=DBUS</uri>
> </note>
> 
>-<pre caption="Enable 'hal' use flag">
>+<pre caption="enable 'hal' use flag">
> # <i>euse -E hal</i>
> # <i>emerge -v hal dbus hotplug</i>
> # <i>rc-update add dbus default</i>
> # <i>/etc/init.d/dbus start</i>
> # <i>rc-update add hald default</i>
> # <i>/etc/init.d/hald start</i>
> </pre>
> 
> <p> 
>-Instead of configuring our software; we could just use some applications to do
>-this for us.
>+Instead of configuring our software; we could just use some
>+applications to do this for us.
> </p>
> 
>-<pre caption="Autoconf software">
>+<pre caption="autoconf software">
> # <i>echo "sys-apps/pmount ~x86" >> /etc/portage/package.keywords</i>
> # <i>emerge -v pmount</i>
> # <i>emerge -v ivman</i>
> </pre>
> 
> <note>
> At this point you may test this by typing <c>media:/</c> in your Konqueror.
> (You will need to insert an external storage device into your USB-port.)
> </note>
> 
> <note>
>-We put <c>sys-apps/ivman</c> in this howto because it gives the user a nice
>+We putted <c>sys-apps/ivman</c> in this howto because it gives the user a nice
> pup-up window and asks the user where he'd like to mount the <e>new</e>
> hardware.
> </note>
> 
> <p>
>-Now your window manager automatically asks you where he has 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.
>+Now your window manager automaticly asks you where he has 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.
> </p>
> 
>-<pre caption="/etc/udev/rules.d/hal.rules">
>-BUS=="usb", 
>+<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>
> 
> <p>
>-and also edit <path>/etc/fstab</path>:
>+and also edit /etc/fstab
> </p>
> 
> <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>
>+<chapter><title>external storage posibilities</title>
>+<section><title>configuring the kernel</title>
> <body>
> 
>+
> <p> 
>-Make sure the options below are marked like said below in your kernel config
>+Make sure the options below are marked like said below in your kernel config 
> that is found at <path>/usr/src/linux/.config</path>.
> </p>
> 
> <note>
> These kernel-options are just generally. You should really look fist at your
>-<c>lspci</c> output and see for yourself if you need OHCI or UHCI. The options
>-below are set for UHCI.
>+<c>lspci</c> output and see for yourself if you need OHCI or UHCI. 
>+The options below are set for UHCI.
> </note>
> 
> <pre caption="configuring your kernel">
> # <i>vim /usr/src/linux/.config</i>
> MSDOS_FS=y
> VFAT_FS=y
>@@ -162,115 +155,109 @@
> USB_OHCI_HCD=n
> </pre>
> 
> </body>
> </section>
> <section>
>-<title>Build the kernel</title>
>+<title>build the kernel</title>
> <body>
> 
>-<pre caption="Installing your new kernel">
>+<pre caption="installing your new kernel">
> # <i>make</i>
> # <i>mount /boot/</i>
> # <i>cp arch/<const>your arch</const>/boot/bzImage
> # /boot/linux-<const>$ver</const>-gentoo-<const>$release</const></i>
> </pre>
> 
> <p>
>-Now you should reboot and move further from this point after you reboot.
>+now you should reboot and move further from this point after you reboot
> </p>
> 
> </body>
> </section>
>-<section>
>-<title>Checking if hotplug detected your devices well</title>
>+<section><title>checking if hotplug detected your devices well</title>
> <body>
> 
>-<pre caption="Check dmesg">
>+<pre caption="check dmesg">
> # <i>dmesg | grep usb-storage</i>
> </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>
> 
> <note>
>-If this happens, it means you did not configure your kernel well. You should
>+If this happens, It means you did not configure your kernel well. You should
> look at your lspci and restart from where you started after the reboot.
> </note>
> 
> <p>
>-You can do this automatically by putting your driver name in
>+you can do this automaticly by putting your driver name in 
> <path>/etc/modules.autoload.d/kernel-2.{4|6}</path>.
> </p>
> 
>-<pre caption="For scsi interface">
>+<pre caption="for scsi interface">
> # <i>emerge sg3_utils</i>
>-# Description: apps for querying the sg SCSI interface
>+# Description: apps for querying the sg SCSI interface 
> (contains rescan_scsi_bus.sh)
> </pre>
> 
> <p>
>-And right after that:
>+and right after that :
> </p>
> 
>-<pre caption="Mounting the drive">
>+<pre caption="mounting the drive">
> # <i>mkdir /mnt/usbstick</i>
> # <i>mount -t vfat /dev/sda1 /mnt/usbstick</i>
> </pre>
> 
> <p>
>-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.
>-<path>/dev/sdb1</path>). You can also try with auto or msdos (for small cards)
>-as the filesystem type (<c>mount -t msdos /dev/x /mnt/x</c>).
>+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).
> </p>
> 
>-<pre caption="Looking for firewire devices">
>+<pre caption="looking for firewire devices">
> # <i>sg_scan -i</i>
> # <i>sg_map</i>
> </pre>
> 
> </body>
> </section>
> </chapter>
> 
>-<chapter>
>-<title>Editing your fstab</title>
>-<section>
>-<title>Mounting your external usb-devices</title>
>+<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>
> 
> <p>
>-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 transferring
>-data to it. You don't need to use vfat in the fstab file as long as
>-<path>/etc/filesystems</path> is set up properly.
>+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.
> </p>
>-
> </body>
>-</section>
>-<section>
>-<title>Configuring your filesystems</title>
>+</section><section><title>configuring your filesystems</title>
> <body>
> 
> <p> 
>-Specifically, if vfat exists in <path>/etc/filesystems</path> 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. 
>+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. 
> </p>
> 
> <pre caption="/etc/filesystems">
> #
> # This file defines the filesystems search order used by a
> # 'mount -t auto' command.
>@@ -287,16 +274,14 @@
> </pre>
> 
> </body>
> </section>
> </chapter>
> 
>-<chapter>
>-<title>Mounting your Windows partitions</title>
>-<section>
>-<title>The different filesystem types</title>
>+<chapter><title>Mounting your windows partitions</title>
>+<section><title>the different filesystem types</title>
> <body>
> 
> <pre caption="mount -t type device mountpoint">
> # <i>mount -t ntfs /dev/hda1 /mnt/win</i>
> # <i>mount -t vfat /dev/hda2 /mnt/data</i>
> </pre>
>@@ -305,34 +290,30 @@
> </section>
> <section>
> <title>user permissions</title>
> <body>
> 
> <p>
>-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
>+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 <c>id $user</c>. 
> </p>
> 
> <p>
>-umask: octal file permissions<br />
>+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:
> </p>
> 
> <ul>
>-  <li>
>-    Character '0': Indicates that this is an octal number, not decimal
>-  </li>
>-  <li>First digit: owner user permissions</li>
>-  <li>Second digit: owner group permissions</li>
>-  <li>
>-    Third digit: world permissions (every other user on the system).
>-  </li>
>+<li>character '0': Indicates that this is an octal number, not decimal.</li>
>+<li>first digit: owner user permissions</li>
>+<li>second digit: owner group permissions</li>
>+<li>third digit: world permissions (every other user on the system)</li>
> </ul>
> 
> <note>
> M | R W X
> -------------
> 0 | * * *
>@@ -343,79 +324,77 @@
> 5 | - * -
> 6 | - - *
> 7 | - - -
> </note>
> 
> <pre caption="/etc/fstab">
>-# my windows partition
>+#my windows partition
> /dev/hda1  /mnt/ntfs  ntfs  uid=1000,gid=100  0 0
> </pre>
> 
> <p>
>-<b>utf8</b><br />
>-You may also add utf8 option, if you can't see some files with international
>-characters in filenames.
>+<b>utf8</b> You may also add utf8 option, if you can't see some files with 
>+international characters in filenames 
> </p>
> 
> <pre caption="/etc/fstab">
>-/etc/fstab /dev/hda1  /mnt/vfat  vfat  ro,utf8  0 0
>+e.g. /etc/fstab : /dev/hda1  /mnt/vfat  vfat  ro,utf8  0 0
> </pre>
> 
> <p>
>-For more options:
>+for more options :
> </p>
> 
>-<pre caption="See more?">
>-# <i>man mount 8</i>
>+<pre caption="see more?">
>+# <i>man mount(8)</i>
> </pre>
> 
> </body>
> </section>
>-<section>
>-<title>Captive NTFS</title>
>+<section><title>
>+captive ntfs</title>
> <body>
> 
> <p>
>-We need <c>sys-fs/captive</c> (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:
>+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
> </p>
> 
>-<pre caption="Unmasking captive">
>+<pre caption="/etc/portage/package.keywords">
> # <i>echo "sys-fs/captive ~x86" >> /etc/portage/package.keywords</i>
> </pre>
> 
> <p>
>-Let's emerge captive now:
>+let's emerge captive now
> </p>
> 
> <pre caption="emerge captive">
> # <i>emerge captive</i>
> </pre>
> 
> <p>
>-Now load the appropriate kernel module and make it load at boot
>+Now load the apropriate kernel module and make it load at boot
> </p>
> 
>-<pre caption="Loading the ap[ropriate kernel module">
>+<pre caption="loading the apropriate kernel module">
> # <i>modules-update</i>
> # <i>modprobe fuse</i>
> # <i>echo "fuse" >> /etc/modules.autoload.d/kernel-2.6</i>
> </pre>
> 
> <p> 
>-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 appropriate drivers from
>-<uri>http://microsoft.com</uri> (You need a Windows SP2 license to do this
>-legal.) (It doens't matter if your partitions are mounted or not; The program
>-looks for itself after the right partitions.) Caution: you need X-windows for
>-this app.
>+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.
> </p>
> 
>-<pre caption="Acquiring the necessary filesystems">
>+<pre caption="acquire the necessary filesystems">
> # <i>captive-install-acquire</i>
> </pre>
> 
> <p> 
> After you walked through the wizard you should now be able to mount your
> windows partitions read/write. 
>@@ -432,21 +411,20 @@
> 
> <pre caption="/etc/fstab">
> /dev/hda2          /windows          captive-ntfs     users      0 0
> </pre>
> 
> <p> 
>-Caution: You'll need to recompile fuse if you update your kernel!
>+Caution : You'll need to recompile fuse if you update your kernel !
> </p>
> 
>-<pre caption="After kernel update">
>+<pre caption="after kernel update">
> # <i>modprobe -r fuse</i>
> # <i>emerge sys-fs/fuse</i>
> # <i>modules-update</i>
> # <i>modprobe fuse</i>
> </pre>
> 
> </body>
> </section>
> </chapter>
> </guide>
>-

Actions: View | Diff

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