On Fri, 01 Feb 2019 23:00:27 +0000, bob prohaska wrote:
> If I look at /dev on the Pi I see /dev/sda but no /dev/sda1. The little
> "eject" button at top-right on the screen reports "no ejectable devices"
> but it does the same thing on my camera and I can extract photos from
> it.
>
You mentioned cameras, so that was what I saw when I connected a
Panasonic TZ-70 to my RPi - I assumed that /dev/sda was the SD card in
the camera and /dev/sda1 was a partition or equivalent. As you could see,
I was able to mount /dev/sda1 on my Pi and then, cd into the directory it
was mounted on and see the directories etc in it that I knew were in the
card. The card also mounted as read-only and again that fit because
conecting the camera to this laptop (a Lenovo T440 running Fedora 28) on
a USB connection lets me open it with the file manager but it is only
ever mounted in read-only mode.
I've just put the card into the T440's SD card slot and pointed gparted
at it. This says the card contains one FAT32 7.4GB partition that it
refers to as /dev/mmcblk0p1 and 4MB of unallocated space - this is how
the camera formatted the SD card.
Since, on an RPi, /dev/mmcblk0p1 is similar (the same?) as the name of
its boot disk (and that's a FAT32 partition) and the Linux filing system
is in an ext4 partition referred to as /dev/sda, it looks as if the
mmcblk* type of name may be used by all modern Linuxes for FAT32
partitions. When mounted, 'df' shows it under this name too.
Your iPad will have formatted its memory to suit some flavour of IOS and
its quite likely that there are no RPi drivers capable of reading a chunk
of flash memory that's been formatted to suit IOS.
> It appears the iPad is locked down tight.
>
Not necessarily - just that it is only listening for iphone-sync TCP
connections on port 62078 - most likely that's a protocol that RPis don't
support.
> Thanks for writing!
>
No problem - its always interesting to mess about with tools like nmap to
find out what they can see - and its a very useful tool to have if you
have firewall problems.
The other one to bear in mind for trouble shooting is Wireshark, which
catches and analyses data packets on an Ethernet connection. I have it,
use it once a year at the most, but wouldn't want to be without it when
it comes to sorting some types of network connection problems.
--
Martin | martin at
Gregorie | gregorie dot org
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|