Date: Tue, 15 Feb 2011 14:51:39 +0100 From: Polytropon <freebsd@edvax.de> To: ajtiM <lumiwa@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: android Message-ID: <20110215145139.ac6c74d9.freebsd@edvax.de> In-Reply-To: <201102150557.33693.lumiwa@gmail.com> References: <201102141900.02996.lumiwa@gmail.com> <AANLkTik5hs319yxuoyQcFOBrDwM75=1GauSyw1xT-rNF@mail.gmail.com> <201102150557.33693.lumiwa@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Feb 2011 05:57:33 -0600, ajtiM <lumiwa@gmail.com> wrote: > I did what you suggested but it doesn't works: > no such fles or directory. According to your dmesg output da4 at umass-sim1 bus 1 scbus3 target 0 lun 0 da4: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da4: 40000 MB/s transfers the da4 device is the correct one. Check which access files are created: # ls -l /dev/da4* You can check the partitioning of the da4 device with # fdisk da4 which should show you what kind of partitions are available to access, and what type they are of. If you see a FAT partition, it will probably be /dev/da4s1, so (including security means, just for testing): # mount -t msdosfs -o ro /dev/da4s1 /mnt should mount it read-only. You can also use a per-filsystem identification using # file - < /dev/da4s1 for proper identification (at least this works with partitions containing UFS filesystems, no idea about FAT stuff). Check dmesg output in parallel to see if the Android didn't cut the wire due to a timeout. Take one step after another: First identify what is available, then identify it, and finally mount it for testing. If it all works, make a permanent option (e. g. in /etc/fstab) for it if you want. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110215145139.ac6c74d9.freebsd>