From owner-svn-doc-all@FreeBSD.ORG Mon Nov 12 20:14:49 2012 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B1BBA1; Mon, 12 Nov 2012 20:14:49 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by mx1.freebsd.org (Postfix) with ESMTP id 64ACB8FC12; Mon, 12 Nov 2012 20:14:47 +0000 (UTC) X-AuditID: 12074424-b7fce6d000000925-8a-50a157847c7a Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id CB.FF.02341.48751A05; Mon, 12 Nov 2012 15:09:40 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id qACK9ekd013157; Mon, 12 Nov 2012 15:09:40 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qACK9cGc007956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Nov 2012 15:09:39 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qACK9bJI001574; Mon, 12 Nov 2012 15:09:37 -0500 (EST) Date: Mon, 12 Nov 2012 15:09:37 -0500 (EST) From: Benjamin Kaduk To: Eitan Adler Subject: Re: svn commit: r39982 - head/en_US.ISO8859-1/books/faq In-Reply-To: <201211112229.qABMT3dL009319@svn.freebsd.org> Message-ID: References: <201211112229.qABMT3dL009319@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMIsWRmVeSWpSXmKPExsUixCmqrNsSvjDA4OVTG4sfHw8xWez6O4fZ 4sai/UwWu/t7mR1YPGZ8ms8SwBjFZZOSmpNZllqkb5fAlbHm2Dr2glOKFf+PPGZrYOyU6mLk 5JAQMJF4++4hE4QtJnHh3nq2LkYuDiGBfYwSl+Z/YYFwNjBKfN73jgnCOcEksfrRIlYIp4FR Yl7bErB+FgFtiW8rbzKD2GwCKhIz32xkA7FFgOzv+3+C1TALREnsWdrICmILCzhIHHkxgwXE 5hSwkli07wZYLy9QfNmzd2C9QgKWEv9vXQCrERXQkVi9fwoLRI2gxMmZT1ggZlpKnPtznW0C o+AsJKlZSFILGJlWMcqm5Fbp5iZm5hSnJusWJyfm5aUW6Zrr5WaW6KWmlG5iBIUtu4vKDsbm Q0qHGAU4GJV4eA3cFwYIsSaWFVfmHmKU5GBSEuX9FggU4kvKT6nMSCzOiC8qzUktPsQowcGs JML7++6CACHelMTKqtSifJiUNAeLkjjv9ZSb/kIC6YklqdmpqQWpRTBZGQ4OJQlelzCgoYJF qempFWmZOSUIaSYOTpDhPEDDzUBqeIsLEnOLM9Mh8qcYFaXEeZ1BEgIgiYzSPLheWFp5xSgO 9IowbyRIFQ8wJcF1vwIazAQ0eP02kKuLSxIRUlINjAb+Aa1Ptnu9uvJTSv1hqManzClrjab4 h2o1Lkv8cfd86kSRwy3Zm8+djjndqeZwrc307NNL2hbHy0/8PX20O+CjzKzM1XdvfQsNOPJs 6pKW4PdO7q5npOJ7Q5cZMTQGSPhJcllHaj74lMzU2lF2cuG30276hx7WZmeobXtu5+ghY6BY LjlnohJLcUaioRZzUXEiAIl4N3QGAwAA Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 20:14:49 -0000 On Sun, 11 Nov 2012, Eitan Adler wrote: > Author: eadler > Date: Sun Nov 11 22:29:03 2012 > New Revision: 39982 > URL: http://svnweb.freebsd.org/changeset/doc/39982 > > Log: > Modernize the removable-drives FAQ. > > Reviewed by: Richard Yao > Reviewed by: koobs.freebsd@gmail.com > Approved by: bcr (mentor) > > Modified: > head/en_US.ISO8859-1/books/faq/book.xml > > Modified: head/en_US.ISO8859-1/books/faq/book.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/faq/book.xml Sun Nov 11 22:29:01 2012 (r39981) > +++ head/en_US.ISO8859-1/books/faq/book.xml Sun Nov 11 22:29:03 2012 (r39982) > @@ -5125,69 +5125,38 @@ C:\="DOS" The question is unfortunately cut off; "I have a new removable drive, how do I use it?" > > > > - Whether it is a removable drive like a &iomegazip; or an > - EZ drive (or even a floppy, if you want to use it that way), > - or a new hard disk, once it is installed and recognized by > - the system, and you have your cartridge/floppy/whatever > - slotted in, things are pretty much the same for all > - devices. > + If the drive already has a > + file system on it, you can use a command like this: > > - (this section is based on - url="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html">Mark Mayo's ZIP FAQ) > - > - > - If it is a ZIP drive or a floppy, you have already got a > - DOS file system on it, you can use a command like this: > - > - &prompt.root; mount -t msdosfs /dev/fd0c /floppy > - > - if it is a floppy, or this: > - > - &prompt.root; mount -t msdosfs /dev/da2s4 /zip > - > - for a ZIP disk with the factory configuration. > - > - For other disks, see how they are laid out using > - &man.fdisk.8; or &man.sysinstall.8;. > - > - The rest of the examples will be for a ZIP drive on > - da2, the third SCSI disk. > - > - Unless it is a floppy, or a removable you plan on > - sharing with other people, it is probably a better idea to > - stick a BSD file system on it. You will get long filename > - support, at least a 2X improvement in performance, and a lot > - more stability. First, you need to redo the DOS-level > - partitions/file systems. You can either use &man.fdisk.8; > - or &man.sysinstall.8;, or for a small drive that you do not > - want to bother with multiple operating system support on, > - just blow away the whole FAT partition table (slices) and > - just use the BSD partitioning: > - > - &prompt.root; dd if=/dev/zero of=/dev/rda2 count=2 > -&prompt.root; disklabel -Brw da2 auto > + &prompt.root; mount /dev/da0s1 /mnt > Last I checked, our mount.8 did not have magic to guess the file system type; a new removable media is unlikely to come preformatted with a FreeBSD UFS file system on it, so this command would not work. The '-t msdosfs' seems like a better bet. > - You can use &man.disklabel.8; or &man.sysinstall.8; to > - create multiple BSD partitions. You will certainly want to > - do this if you are adding swap space on a fixed disk, but it > - is probably irrelevant on a removable drive like a > - ZIP. > + If the drive will only be used with &os; > + systems it is better idea to > + stick a BSD file system on it, like UFS or ZFS. And this block no longer has meaning, since "better idea" can only be with respect to the previous example, which currently assumes ... a BSD file system. -Ben Kaduk > + You will get long filename > + support, at least a 2X improvement in performance, > + and a lot more stability. If the drive will be > + used by other operating systems a more portable > + choice, such as msdosfs, is better. > + [trim]