GVasco

True that!

N is the number elements to be parsed by the function

n = 1 and you have O(1)

Because there is practically no risk of damaging the device and bricking it. If you knew anything about the the distribution, it’s inhalation and android you’d know that the risk is almost nonexistent and reversible. I understand you don’t want to run any risk, sure, it’s a valid reason, but to damage the device is practically impossible just from installing another android variant.

All modern phones come with a locked bootloader. This is to protect the OS and the User data, preventing anyone with physical access to the devixe from reseting the device and installing their own software without permissikn. I had to unlock mine on my 1+ 7P before installing /e/OS. It might just be that carrier locked phones might need something extra to unlock them not sure.

There’s almost no risk, you can install it from the browser, the bootloader gets relocked so no issues with banking apps and rooted device, and you can still have play services on the phone but without it being able to access the whole storage and device info. You seem to literally just be spewing words without knowing anything about the subject.

If you don’t want it I’d be willing to take it and experiment myself with graphene OS.

Switch to graphene OS

Using K-9 and quite liking it, otherwise just browse F-droid everything there is Foss.

For sure! Yeah I was just remembering that shares get mounted as a drive when you access them. So makes sense.

Great to know! Thanks!

Maybe! I’d start checking dmesg logs and check the smart info provided you do regular tests. Otherwise do some SMART tests and check the results after.

Why? They are built for datacenter environment, with the right drives for high density storage they should be just as fine as in a regular server.

Yeah I agree! Used iPhone in past, switched to android a few years back and now recently switched to /e/OS and I’m not looking back at using a Googled Android or iPhone. Considering getting a Pixel to install GrapheneOS but hate giving money to google to get a more private experience.

on an off note, use links starting with a bang “!” without the “http(s)://“ this allows users to be forwarded via their instance.

could try finding a cheap jbod

It’s neither, it’s a limitation of SMB, if you have multiple shares set-up that mount to the root of the SMB share, you can’t hardlink accross them, but inside a single share in the root of the SMB share apparently it’s not an issue.

Sure *are apps might not have a way of knowing but they are still limited by SMB’s limitations. If you’re sharing individual folders you simply can’t hardlink across them. But my bad for thinking SMB didn’t allow hardlink inside the same share mount point.

CIFS is SMB under a diferent name, and it might be that inside a share you can hardlink, but not across shares in the same filesystem.

Are you sharing the top folder holding both folders where you’re creating the hardlinks or are you creating individual shares for each folder?

Check you ISP connections limits, remember that uploading from an external device will be downloaded by your home router and vice versa.

one caveat is the need for *rr apps to have direct access to the storage filesystem, and not connect through some filesharing protocol (smb, NFS, etc…) afaik. ISCSI might be good since it’s presented as an actual system drive, speculating.