[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ftpfs & no internet (Was: Hurd Tips)
From: |
Samuel Thibault |
Subject: |
ftpfs & no internet (Was: Hurd Tips) |
Date: |
Sat, 26 Oct 2024 13:21:37 +0200 |
Joshua Branson, le ven. 25 oct. 2024 22:28:30 -0400, a ecrit:
> - ftpfs doesn't work so well without internet (obviously)
> - settrans -c \~/hurd-iso /hurd/iso9660fs
> $HOME/ftp://ftp.someftpserver.org/img.iso
> - Often times I will be working offline editing the wiki, and I will
> type `ls ~/`, which will take one minute to list the directory
> contents.
Ah, that'd probably the TCP connection timeout delay indeed. It'd be
the same with a faulty nfs mount on linux for instance. Having your
mounts directly in your home will always get such concerns, better make
yourself a ~/net directory.
> C-c, works but really slowly (30 second lag).
Ftpfs should be taught the interrupt_operation protocol for C-c to be
immediate.
> It would
> be nice if during ftpfs startup, it could check if the Hurd has an
> active internet connection. If the IP address is 0.0.0.0 maybe
> that means no internet?
That completely depends on the situation you have.
If your network is really down (no route to the Internet), you'll get
an immediate "Network is unreachable" error. If your network is not
actually down (pfinet has an IP and a route, packets just don't get
answers), there is no real possibility for pfinet to know it but losing
patience after some timeout.
Samuel
- ftpfs & no internet (Was: Hurd Tips),
Samuel Thibault <=