From owner-freebsd-questions@FreeBSD.ORG Fri Oct 16 00:18:01 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E80BB106568D for ; Fri, 16 Oct 2009 00:18:01 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id A91DA8FC14 for ; Fri, 16 Oct 2009 00:18:01 +0000 (UTC) Received: from r55.edvax.de (port-92-195-71-245.dynamic.qsc.de [92.195.71.245]) by mx01.qsc.de (Postfix) with ESMTP id D10CF3CA1B; Fri, 16 Oct 2009 02:17:59 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n9G0HxlN003184; Fri, 16 Oct 2009 02:17:59 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 16 Oct 2009 02:17:59 +0200 From: Polytropon To: PJ Message-Id: <20091016021759.f478642a.freebsd@edvax.de> In-Reply-To: <4AD7B8F0.20903@videotron.ca> References: <4AD79FE4.6010109@videotron.ca> <20091016012610.99efbf26.freebsd@edvax.de> <4AD7B8F0.20903@videotron.ca> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: usb key problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 00:18:02 -0000 On Thu, 15 Oct 2009 20:06:08 -0400, PJ wrote: > Anyway, I found the solution on the web... couldn't belive it was that > simple: just ignore the crap spewed out on the screen and just mount iit > as you would any other disk. > # mount -t msdosfs /dev/da0s1 /mnt > and that's it Additionally, when you use mount_msdosfs, you can specify masks (-m and -M) in order not to have +x attributes on all the files; the MS-DOS file system on the stick could give you unwanted results, for example if you have a .jpg file on the stick and want to open it (with the default app for .jpg file type), the system will try to execute it. > Now to see how I can use it to restore stuff. :-D If you want to use the stick for FreeBSD operations, why not give it a real file system (i. e. UFS) instead of some old FAT? You can simply # newfs /dev/da0 and then access it in the standard way: # mount /dev/da0 /mnt See that file owner:group, permissions and flags are now supported, and files that are not supposed to be executables don't have +x attribute (as in opposite to FAT / msdosfs). You could even add an entry in /etc/fstab like this: /dev/da0s1 /media/stick msdosfs rw,noauto,noatime 0 0 or, for proper UFS: /dev/da0 /media/stick ufs rw,noauto,noatime 0 0 Keep in mind that when using device names, it's a matter of in which sequence device are detected that result in the corresponding device name (da0, da1 etc.); using labels is the more elegant way here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...