![[request] How fast could the train be, if everyone does the Flintstones thing with their full capabilities?](https://preview.redd.it/xa6d0oxez82h1.jpeg?auto=webp&s=07d4e2694dbccf907ae0ddc480d14e6c7693991e)
u/busytransitgworl
![[request] How fast could the train be, if everyone does the Flintstones thing with their full capabilities?](https://preview.redd.it/xa6d0oxez82h1.jpeg?auto=webp&s=07d4e2694dbccf907ae0ddc480d14e6c7693991e)
People in Highland Park, TX, USA decide to let public transport go
youtu.beNFS just refuses to work (doesn't connect, no error though)
I've been trying to get NFS running for days now and I seem to be a bit too dumb for it.
I followed this guide (https://help.ubuntu.com/community/SettingUpNFSHowTo) and also the NFS's guide (https://nfs.sourceforge.net/nfs-howto/ar01s03.html) but somehow there's just something going on.
Both my server and client are running Debian 13 with all the updates.
My server doesn't complain, it's on the same network as my client and there's also no firewall blocking anything (hopefully).
The issue seems to be on the server-side. I can ping my clients from my server without issues, the other way around though, nmap only shows results with -Pn:
user@client ~> nmap -Pn 192.168.10.30Starting Nmap 7.95 ( https://nmap.org ) at 2026-05-18 20:19 CESTNmap scan report for SERVER (192.168.10.30)Host is up (0.0061s latency).Not shown: 991 filtered tcp ports (no-response)PORT STATE SERVICE22/tcp open ssh89/tcp open su-mit-tg139/tcp open netbios-ssn445/tcp open microsoft-ds8000/tcp open http-alt8080/tcp open http-proxy8085/tcp open unknown8443/tcp open https-alt10000/tcp open snet-sensor-mgmt
No port 2049, that should be in that list, right?
When I try to mount my NFS share, it does absolutely nothing. Same when I use my Mac as a client, absolutely no success.
It always just times out.
user@debian-client ~ > sudo mount -t nfs4 192.168.10.30:/ /mnt/nfsmount.nfs4: Connection timed out for 192.168.10.30:/ on /mnt/nfs
According to rpcinfo, NFS is running on my server, I've restarted the service multiple times.
My /etc/exports has the IP of my client and it looks okay-ish?
/nfsexport/nas-folder 192.168.10.13(rw,nohide,insecure,no_subtree_check,sync)
Does anyone have an idea on what I'm missing?
Thanks in advance! <3
(.30 is the server, .13 my client, I've tried both v3 and v4 unsuccessfully)
American Fanta contains absolutely no fruit juice, quite different from Irish (5%) or Italian (9%) Fanta - And the US orange Fanta looks like a neon-orange highlighter, which it doesn't in the EU
Our canteen had a wrap with veggies and salad on the menu with guac on the side. I ordered "One wrap please, hold the guacamole though, thanks!" and got quite a nice looking meal.
Well, I could've asked if there was guacamole inside the wrap as well, I know, I didn't though.
And I really can't eat any of it, it's just awful. 🫠
Especially because I absolutely hate wasting food...
I'm currently on Fedora 44 which is running fine, but I want to harmonise my entire homelab setup which is basically running Debian and Ubuntu on the server-side of things, my PC though is Fedora.
In my mind, the following sounds like it's prone to fail.
- Debian 13 Stable
- KDE for my GUI stuff
- Btrfs as my filesystem for /
- Installing Snapper (or the Debian equivalent of it) afterwards - Really loved it with openSUSE
- (Connect PC to server via NFS)
It feels like Btrfs and Snapper might be a point-of-failure on Debian, even though it'll probably be absolutely fine.
I really appreciated the ease of use with Snapper snapshots under openSUSE Tumbleweed, it was so neatly integrated into the OS and I hope it'll be just as smooth under Debian.
I really never tinkered around with Debian itself. On one server it's just a basis for my NAS stuff and the other Ubuntu server is just a reverse proxy.
Thanks in advance for your feedback and advice! xxo