How on earth can shit like this even be legal? I’m still hella mad for all the SMR shenanigans that got me two low-performing hard drives

I gave Tidal a shot this year. Lasted about 3 months before the user experience pushed me – go on and scold me – back to Spotify.

I listen to music in my car a lot which has an aftermarket Android head unit fitted. Within the first week of my trial they revamped the UI, which entailed not being able to add the currently playing song to a playlist UNLESS I leave the player view, go SEARCH the title and select it from the results. That’s something I’m definitely NOT doing while driving.

This in itself would be a dealbreaker for me if it wasn’t for Spotify’s awful business practices. So I tried to ignore it. But even then, I got nowhere close to the amount of artists and tracks that I discovered each week when on Spotify. I noticed how I listened to music less and less each day because it was either frustrating or meant listening to the same songs over and over.

I’m actually kind of embarrassed to be back on Spotify because of all the reasons mentioned in this thread (and everywhere else, obviously). But I need music to stay sane, I can’t deal with it being such a pain.

That sounds like so much fun

Even with bar exported to this client, it cannot see its subdirectories’ contents. What the hell is going on? Just to be clear, I did run exportfs -arv after every change to /etc/exports.

Thanks, I misunderstood the usage of /24. I thought in order to export to a whole subnet, I had to put the subnet address 192.168.0.0/24 while 192.168.0.20/24 would imply a single client within that subnet. I removed the prefix length entirely as CallMeAl suggested, so that’s sorted out.

There’s another issue remaining, see my reply to Al’s comment if you’d like.

Thank you. I’m closer to what I want now. Can you help me explain this behavior though:

For testing purposes, I commented out every line in /etc/exports but these:

/srv/nfsv4              192.168.0.10(ro,sync,secure,root_squash,subtree_check,fsid=0) \
                        192.168.0.20(ro,sync,secure,root_squash,subtree_check,fsid=0)

Client 192.168.0.20 can mount nfs-server:/ and listing the contents gives both directories foo and bar. It cannot see the contents of foo, as intended, but it can see what’s inside bar (EDIT: it can see down one level, so the subdirectories of bar, but nothing further down). I cannot figure out why? I rebooted the machine in hopes it was just a caching thing, to no avail.

Apart from that, I was hoping 192.168.0.20 could not even mount foo, but as long as its contents are hidden, I can live with that for now.

That can’t be right. For exposing it to a whole subnet, it would have to be 192.168.0.0/24, wouldn’t it?

Non-sysadmin here, I could only find some generic info on ISO 27002/27001, what does it say about containerized applications?