From: dan@djph.net   
      
   On 2025-09-05, pinnerite wrote:   
   > On Thu, 4 Sep 2025 19:36:44 -0000 (UTC)   
   > Dan Purgert  wrote:   
   >   
   >> On 2025-09-04, pinnerite wrote:   
   >> > Ever since I  backed up to a second machine I had been using samba.   
   >> > As a result I mounted using cifs and included username, password and   
   >> > domain in the command line.   
   >> >   
   >> > I no longer need Samba and so reduced my mount statement to a minimal:   
   >> >   
   >> > $ sudo mount -t ext4 -o rw //192.168.1.120/backups/data/   /mnt/monty/data   
   >> >   
   >> > That doesn't work because [...]   
   >>   
   >> it's completely invalid for an ext4 filesystem, among other things.   
   >>   
   >> I'm going to assume this is an NFS mount, in which case   
   >>   
   >>   mount -t nfs 192.168.1.120:/backups/data /mnt/monty/data   
   >>   
   >> assuming, of course, "/backups/data" is the correct path on the remote   
   >> machine.   
   >>   
   >   
   > The nfs-kernel-server had not been installed on the local machine but   
   > was on the remote(?) Now remedied.   
      
   You only need "nfs-kernel-server" on the machine(s) that are acting as   
   servers.  Clients only need "nfs-common" (or something close to that)   
      
   > mount -t nfs 192.168.1.120:/backups/data /mnt/monty/data is correct but   
   > it just times out.   
      
   "just times out" sounds like either   
      
   (A) the machine "192.168.1.120" is not actually running an NFS server OR   
   (B) the firewall on that machine is blocking the connection.   
      
   --   
   |_|O|_|   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)