u/freelsjd

I have a paid filen subscription for my linux desktop, and other android devices (phone, chromebooks, etc.). I really enjoy using filen, but have run into some limitations I would like to ask (4) questions about.

When I started using filen, I was stricly using the desktop app with a goal of two-way sync on a few filesystems of my linux machine. What I found was that for larger filesystems, the sync would hang up and basically fail. Question #1 - what are some numbers for failure for large filesystems in terms of GB overall size, number of files, number of directories, etc. ??

So, from what I read here and elsewhere, the solution to this problem was use rclone, for which, filen is well suited. Already familiar with rclone on several other platforms (Google Drive, OneDrive, protondrive, Dropbox, etc.), I found this works great and sync, resync, and bisync for rclone is working fine. However, the limitation here is that you have to specific via crontabs how often to do the syncs. So, instead of when the file changes, or a small time span, it is reasonable to run rclone/bisync say a few times a day at most. This is much less frequent than the sync updates that I see on the filen GUI. Question #2 - What frequency at most would you expect rclone updates for large filesystems to bisync (20GB-400 GB) ?

Now, what I am wondering is can I take an existing rclone bisync and convert it via GUI to a filen two-way sync. Just stop the rclone on the linux side, given identical archives on both ends, and turn it on (release the pause) once setup via the GUI. This is Question #3.

If this is too much to ask, another question for anyone who has tried this. I am trying it now. If I take a large file system, and start with a small two-way sync, say 1GB and 5000 files. Then use the .filenignore file to gradually release one directory at a time in increments. Pause, comment out an ignore, unpause. These 3 steps repeatedly until all have been synced. Would this work any differently than running the entire two-way sync at once initially ? This is Question #4. I will report back here for my attempt on this.

Thanks.

There is so much negativity in this subred about no direct linux support for protondrive. In particular, no syncer as in most cloud drivers on Winders and other platforms. Then it hit me today why. Proton is hell bent on providing many of the same apps for users that Google has. The main differene, of course, being end-2-end encrypted. Well, guess what, Google has no supoport for Linux as far as a syncer either ! So, Proton has no incentive to provide one either !

I have a free version of filen installed on my Linux Debian 13.6 machine for testing purposes. So far until now, it seems to work beautifully, and I am seriously considering a purchased version. However, my last big test was to try out the remote drive feature. The GUI method to set it up did not work for me. Therefore, I am going down the rclone method to manually mount the remote from the CLI. However, in order to do either method, It seems I must run the command

Filen export-api-key

to retrieve the api-key for rclone to function. Unfortunately, the key is not displayed. When I run the command, I get nothing back and no messages are displayed at all; including any error messages. It is as if it is not running.

Do I need to stop the filen sync while I setup the remote drive ?

Any other ideas why this is happening ?

I am considering purchasing the MeerKAT miniPC from System76 with PopOS, Ubuntu26.04, or Debian Trixie (Debian user since 1994).. It would be fully loaded with maximum cpu, memory, and storage and looks like it may cost about $7556 which is a lot of money for me. One of the main things I want to do with this machine (aside from normal PC stuff) is run COMSOL Multiphysics as a developement platform. Even for smaller simulations, this may require long-running cases. So, my primary question is how is the thermal performance of this beast? Will it hold up for several hours at a time if need be with the cpu full speed? It appears the MeerKAT has no cpu fan. The main appeal to me about this option is the small size and quiet in a home environment.

Any experiences with MeerKAT are welcome to comment please.

Thanks.

I am considering purchasing the MeerKAT miniPC from System76 with PopOS, Ubuntu26.04, or Debian Trixie (Debian user since 1994).. It would be fully loaded with maximum cpu, memory, and storage and looks like it may cost about $7556 which is a lot of money for me. One of the main things I want to do with this machine (aside from normal PC stuff) is run COMSOL Multiphysics as a developement platform. Even for smaller simulations, this may require long-running cases. So, my primary question is how is the thermal performance of this beast? Will it hold up for several hours at a time if need be with the cpu full speed? It appears the MeerKAT has no cpu fan. The main appeal to me about this option is the small size and quiet in a home environment.

Any experiences with MeerKAT are welcome to comment please.

Thanks.

I am considering purchasing the MeerKAT miniPC from System76 with PopOS, Ubuntu26.04, or Debian Trixie (Debian user since 1994).. It would be fully loaded with maximum cpu, memory, and storage and looks like it may cost about $7556 which is a lot of money for me. One of the main things I want to do with this machine (aside from normal PC stuff) is run COMSOL Multiphysics as a developement platform. Even for smaller simulations, this may require long-running cases. So, my primary question is how is the thermal performance of this beast? Will it hold up for several hours at a time if need be with the cpu full speed? It appears the MeerKAT has no cpu fan. The main appeal to me about this option is the small size and quiet in a home environment.

Any experiences with MeerKAT are welcome to comment please.

Thanks.

Note to mod: this is not a change to ChromeOS, only asking about how to use a feature of chromeos. I recently wiped my Linux off an up-2-date ChromeOS. I then started a new Linux in order to gain a new features and Trixie base. However, I am surprised to see while Debian is 13.5 Trixie, the kernel remains at 6.6 whereas, 6.12 is the normal kernel level outside the ChromeOS. Why is this? Why aren't we running the newer version Linux kernel under ChromeOS?