XPost: comp.mobile.android, alt.comp.os.windows-10   
   From: nospam@needed.invalid   
      
   On Mon, 2/3/2025 2:00 PM, candycanearter07 wrote:   
   > Janis Papanagnou  wrote at 15:04 this   
   Sunday (GMT):   
   >> On 02.02.2025 15:50, Carlos E.R. wrote:   
   > [snip]   
   >>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).   
   >>   
   >> Yes, I know. For some reasons inferiors concepts are invented and   
   >> they also don't die once they've got widely spread.   
   >>   
   >> Janis   
   >   
   >   
   > It's hard to stop momentum, sometimes. Windows refusing to switch to a   
   > different FS for external medium also doesn't help.   
   >   
      
   On hardware, partition tables exist, to give a "hint" what   
   subset of file systems might be involved. The 0x07 for   
   example, might be NTFS/HPFS/ExFAT. You then have to look   
   at the first sector in the partition, to determine what it is exactly.   
   There weren't enough codes to go around, which is why the codes today,   
   lack the precision they once had.   
      
   On GPT, a partition type could be declared as a Basic Data Type,   
   then you again have to check the header sector for the details.   
   On Windows, you see the BLKID and the GUID. On Linux, the   
   gdisk utility hides the GUID (ugly) string and shows you some   
   fake (pseudo) codes, such as 0x0700 for a Basic Data Partition.   
   But once you get into the GPT partition table with your hex editor,   
   you'll see that the two entries do not involve "0x0700".   
      
   Hardware devices do not need to have a partition table.   
   You can lay a file system into a hardware device without one.   
   Then the OS has to try all of its filesystem types, for a match   
   on the header sector.   
      
   SD cards have certain expectations of filesystems, based on what   
   wears the SD the least. That's how FAT32 or ExFAT get on the card.   
   Journaled filesystems are a non-preferred choice. Neither NTFS nor EXT4   
   are preferred for an SD.   
      
   I don't know what the OS policy is, when the OS discovers a filesystem   
   outside [FAT32, ExFAT]. FAT32 is needed because the devices could be   
   larger ones. Maybe at some point in the past, an SD had a   
   small enough capacity that FAT12 or FAT16 would work.   
      
   You can use the "disktype" utility on Linux, to indicate what is   
   on a hardware device. I use the Cygwin version of that utility on   
   Windows for that purpose.   
      
      sudo disktype /dev/sda   
      disktype.exe  /dev/sda     # because it's Cygwin, it uses a non-Windows   
   namespace   
      
   I would take the SD out of my camera right now and run it, but   
   it's just going to be a raw FAT32. My camera isn't new enough   
   to know what ExFAT is.   
      
   And you don't even *format* an SD on your desktop OS. If you're   
   using it in a camera, it is the responsibility of a camera menu   
   item to "format" inserted media. This ensures first and foremost,   
   that the media works in the camera. The computer end has a lot   
   more flexibility regarding access. But based on what cameras do   
   to SD, there isn't going to be a problem mounting an SD that   
   was formatted by the camera.   
      
   The behavior could also change, depending on the device used.   
   Maybe when a camera with an SD is plugged in, a different handler   
   (PTP/MPT) handles the camera end, than when a USB stick with SD hole   
   in it, presents an SD. These are experiments you can run,   
   as an experienced forensic expert :-)   
      
   Someone with a wider collection of hardware, can run these   
   experiments for me. I don't have any MTP devices, I also   
   don't have any smartphone to play with.   
      
      Paul   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)