On Tue 16 Jan 2024 at 06:08:35 (-0500), Felix Miata wrote:
> Tom Furie composed on 2024-01-16 08:18 (UTC):
> > Felix Miata writes:
>
> >> /dev/sdc 18 /dev/disk/by-id/usb-Brother_MFC-J6920DW_BROG5F229909-0:0 #
> >> How does a printer get a storage device assignment???
>
> > By having some kind of SD card slot or similar.
>
> So this pollution only results from a USB-connected printer? IP printer
> connections don't cause it too?
AIUI (not very well), you only get a /dev/sdX when the linux kernel
is what's writing the blocks on the filesystem.
So when I plug in my Galaxy 4 mobile and tap the appropriate buttons
on its screen, /dev/sdb{,1} appear as a block device and partition:
sdb 8:16 1 29.7G 0 disk
└─sdb1 8:17 1 29.7G 0 part
so I can run fdisk on the SD card while in the phone, for example:
$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Disk model: S5360 Card
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x03399e11
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 62333951 62331904 29.7G c W95 FAT32 (LBA)
$
OTOH with my A13 phone, I don't get a block device created, but just
a FUSE wrapper round the filesystems that Android is running, both
internal and any SD card:
$ mount
[ … ]
aft-mtp-mount on /media/samsungd type fuse.aft-mtp-mount
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
$
Cheers,
David.
