XPost: alt.os.linux.mint, alt.os.linux.mageia, alt.os.linux.fedora   
   XPost: alt.os.linux.pclinuxos   
   From: vallor@cultnix.org   
      
   On Sun, 09 Feb 2025 11:50:53 -0500, "David W. Hodgins"   
    wrote in   
   :   
      
   > On Sun, 09 Feb 2025 01:11:45 -0500, Jasen Betts   
   >  wrote:   
   >   
   >> On 2025-02-05, pinnerite  wrote:   
   >>> I need to be able to identify the partition address and its file   
   >>> address, particularly when I have two drives on-line.   
   >>>   
   >>> I tried a variety of live devices. Antix was the only one that came   
   >>> close.   
   >>>   
   >>> But years ago I remember a file manager that would allow the user to   
   >>> use a single click to switch the contents of the address line at the   
   >>> top from say /home/fred to /dev/sdb2 or back. I could not re-locate   
   >>> it.   
   >>>   
   >>> Does this strike a chord?   
   >>   
   >> assuming you don't actually mean /dev/sdb2 which is a block device, not   
   >> a mounted file system.   
   >>   
   >> Nautilus, has backwards, forwards, bookmarks, and tabs. It's the   
   >> standard GNOME file-manager.  For some reason GNOME call it "Files"   
   >   
   > I suspect it is /dev/sdb2 being referred to, for the purpose of making   
   > sure it's backed up etc.   
   >   
   > With complicated filesystem layouts, it's easy to forget what is where.   
   >   
   > I vaguely remember a gui file manager that had the device as an optional   
   > column. For the amount of time I needed it, I considered it a waste of   
   > screen space, so didn't use it and don't remember which file manager had   
   > it.   
   >   
   > I have a file called default.gpfl in my home directory. Assuming I want   
   > to find out what device it's on ...   
   >   
   > $ stat /home/dave/default.gpfl | grep ^Dev Device: 259,11  Inode:   
   > 5411522     Links: 1   
   >   
   > To find out what device 259,11 is replace the comma with a colon and   
   > preface it with "/sys/dev/block/".   
   >   
   > $ ls -l /sys/dev/block/259:11 lrwxrwxrwx 1 root root 0 Feb  8 19:33   
   > /sys/dev/block/259:11 ->   
   > ../../devices/pci0000:00/0000:00:02.4/0000:05:00.0/nvme/nvme1/nvme1n1/   
   nvme1n1p7/   
   >   
   > So it's /dev/nvme1n1p7 that would need to work with to ensure the file   
   > /home/dave/default.gpfl was included.   
   >   
   > On my system currently ...   
   > $ mount|grep nvme1n1p7 /dev/nvme1n1p7 on /data type ext4 (rw,relatime)   
   >   
   > I didn't put /home on a separate file system in this install when I   
   > created it as it was just a test installation. I moved it later and   
   > replaced it with a symlink ...   
   > $ ls -l / | grep home lrwxrwxrwx   1 root root    10 Dec 14 12:17 home   
   > -> /data/home/   
   >   
   > $ mount | grep ' / '   
   > /dev/ on / type ext4 (rw,relatime)   
   >   
   > With /home having been moved, anyone looking at just the mount command   
   > output would think files in /home/dave were in nvme1n1p8, not nvme1n1p7.   
   >   
   > This was one of the test installs till my main computer died. I then   
   > used my backup to restore my data into this install.   
   >   
   > Regards, Dave Hodgins   
      
   One can also run "df" on the directory in question, and it   
   will tell you what the device is:   
      
   _[/srv/Extreme_Pro]_(xxx@lm)🐧_   
   $ df .   
   Filesystem      1K-blocks      Used  Available Use% Mounted on   
   /dev/sda1      3844518728 862344652 2786808504  24% /srv/Extreme_Pro   
      
      
      
      
      
   --   
   -v   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)