From: ldo@nz.invalid   
      
   On Tue, 16 Sep 2025 13:09:50 -0400, Paul wrote:   
      
   > Let's run blkid.   
   >   
   > PS> bash   
   > $ blkid   
   > $   
   >   
   > Well, don't give up just yet. Who needs error messages really.   
   >   
   > $ sudo blkid   
   > [sudo] password for paul:   
   > [blkid now produces reasonable-looking output]   
      
   While on my genuine Linux system blkid is in /usr/sbin, and therefore   
   not in the usual $PATH for a nonprivileged user, it works for such a   
   user nonetheless:   
      
       ldo@theon:~> /usr/sbin/blkid   
       /dev/nvme0n1p3: UUID=[etc etc]   
      
   So another incompatibility with genuine Linux?   
      
   (And by the way, I normally use lsblk for displaying information about   
   block devices, as it lets you customize its display.)   
      
   > C:\             124109820  78975248  45134572  64% /mnt/c   
   > D:\              20968444     59656  20908788   1% /mnt/d          <===   
   Added a drive letter "fixed disk", just not a USB stick   
   > H:\             135264344  60774972  74489372  45% /mnt/h   
   > S:\             715167740 630943408  84224332  89% /mnt/s   
      
   This seems really, really dumb to me. /mnt is supposed to be reserved   
   for *temporary* mount points, for sysadmin use. Your OS installation   
   shouldn’t be keeping stuff there on an ongoing basis.   
      
   > There is more to WSL than some bland handwaving. I don't know   
   > if the details of "what is missing" is documented somewhere. It   
   > could be. But it is not just a Linux kernel and HyperV.   
      
   Does seem that way.   
      
   > And WSL is not a place for writing USB sticks. Not even   
   > remotely close to suitable for the purpose. /dev layer is not   
   > proper.   
      
   When it comes to Linux, accept no substitutes. And WSL2 is a poor   
   substitute indeed.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)