I used Garuda in the past and was impressed. What's cool is they have a bunch of ther own services in addition to Lemmy.

Garuda Linux | Startpage - https://start.garudalinux.org/

Then resurrect it. Give it life by posting to it. 😏

I'm gonna have to give this one a try. Syncthing is being a pain in my backside.

Got Void running on an old laptop about a year ago. Very nice. The fact that it is not based on any of the others also made it appealing.

True. Luckily I don't have anything large (4GB+). I do plan to change the filesystem. I forgot to mention that I used to have Windows 7 on that old laptop. The other reason why the shared partition was FAT32/vfat.

Sorry for the really late response. Since one of the OSes is BSD I have one shared FAT32 partition mostly for basic getting-things-from-one-to-the-other stuff. Far as I know OpenBSD does not support ext4 (at least not r/w). It does support ext2.

Since all three OSes have the Nextcloud client it would have been cool to have its directory on a shared partition to reduce redundancy.

I may change things up, format it to ext2 and see if I can use it to share Documents, Music, Pictures, and Video across all three OSes. Maybe.

I have a triple boot laptop with MX Linux, Void Linux, and OpenBSD on an old laptop where VMing wouldn't work so well.

As others have pointed out a shared home directory is not a good idea. Shared data (documents, music, images, etc.) would be fine as mentioned previously.

Never really distro hopped. Went from DOSLinux to Slackware and stayed put as my main. Having multiple machines, some multi booters, meant I had/tried a bunch of others. Vector Linux, Xubuntu, Debian Wheezy, several Arch-based (up to Garuda), various BSDs, and two unices (OpenSolaris/OpenIndiana, IRIX). Got an old ancient ToughBook (Pentiun II, 192MB RAM) with Arch before systemd collecting dust.

[ Those machines had multiple Windows versions also from Win2k to Win7 including XP x64 Edition ] Dem were da days. 🥰

Currently, Main laptop: Slackware. 2nd laptop: MX Linux, Void Linux, OpenBSD. Mini PC: Slint (Slackware-based).

Well, for the mini PC I did distro hop. Went through a lot trying to find the right one. Most were Arch-based (but not Arch itself) and they would indeed break at the worst time. Nature of bleeding edge rolling release I guess. Mostly I was looking for something non-systemd. Eventually settled on Slint.

I have/had a bunch of these books. Some got lost but I have the electronic versions of them.

This is one other book I fondly remember. UNIX For Application Developers. From 1991 I think. I vaguely remember a statement in the intro along the lines of Windows being user friendly but UNiX being expert friendly. :-)

Couldn't find a better image.

cool-retro-term: A good looking terminal emulator which mimics the old cathode display...

Way back when DOSLinux existed the dev provided a Midnight Commander with a fully loaded F2 menu as well as setup associations. Could literally do almost anything and everything from within the file manager. I later moved the configs over to Slackware and pretty much lived in MC to get things done. At some point the MC code reduced the number of entries in the F2 menu so I would have to rebuild it to remove the limitation.

No longer use it like that today but MC is used constantly for file management locally and remotely (mostly to a Kodi box).

Using OFMs (Norton/Volkov/Midnight Commanders and FAR) has always been easier and faster to use than Explorer-style GUI FMs for me.

Oops, sorry. 😬

TEL

If one decides to mess with it, some notes. Last release was awhile back. I don't use Android 12/13 so no idea how well it works there.

Tel and Tel:API have same package names as Termux and Termux:API. Meaning there should be no trace of Termux on system before trying.

Not really battery friendly when using the default status info up top.

Powerful command line environment. Recommend that one is familiar / comfortable with the CLI.

Can use it as a launcher also I guess. Termux Expert Launcher.

Been awhile since I did that but it was really cool. An Xfce desktop from the phone onto my TV. Time to revisit that and play around some.

I temember when Slackware still included it. Used to recompile any apps that still supported the toolkit just to have a better look and feel. I miss OpenWindows.

NsCDE is my desktop on Slackware, Slint, Void, and OpenBSD. I guess I'm most comfortable with it.

I was just too impatient. Probably a periodic maintenance as it was up the next day.

Any idea how old that article is? Couldn't find a date but the mention of Windows 7 tells me it's not recent.

I still have my netscape.net address (AOL) and all the others (Yahoo, MS Live, Outlook). Also a second GMail address that was created/converted when TheBat service shutdown.

I use Thexyz and Purely Mail for normal use though.

Okay. 🙄

What ROM and what method did you use to install it?

On my ROMs/devices the zip from the link I posted never worked. Since all of my ROMs (custom, not OEM stock) are rooted I just manually placed the overlay apk where it needed to be (usually /vendor/overlay/ and permission set to 644) and then installed Mulch WebView. Reboot for good measure and it was available under Developer Options.

If not rooted then I figure the adb method should work.

The aforementioned Open WebView magisk module, which I've used in the past for Bromite, fails to install currently.

If you are rooted with Magisk then you can install an alternate webview. As mentioned the Bromite webview is stalled. Mulch webview (from DivestOS) is regularly updated and has been added to Open WebView module.

I use Mulch SystemWebView Overlay on my ROMs. It is a straight flashable zip but with alternate ways of installing if it does not work (like via adb). A Magisk module is also available. I use Mulch webview on all ROMs including Oreo. I do not run OEM stock so no comments/ideas on that front.

Once the webview is installed and visible it can be updated regularly using your preferred F-Droid client with Divest OS repo added.

GitHub - A4Alpha/mulch-webview-overlay: Easily install the security-hardened Mulch SystemWebView from DivestOS

Just for tinkering so far. I have a habit of tossing the devices aside for long periods of time when an OS breaks badly. 😁

Technically SailfishOS handles most of the requirements to make the device a daily-driver-in-training. All but one of my Android devices are VoIP now. Getting away from carrier-based stuff (and saving money). At the moment there isn't really anything usable on the mobile linux side (SIP, calls via XMPP - I have JMP.chat numbers) that I am aware of. On SFOS that is. Though I can use movim via browser.

Guess it is time I took the devices seriously and try to use them more regularly.

Have the PinePhone and PP Pro. Partial to SailfishOS on both. It has the most smartphone feel if you will. Like with most the camera is pretty much a no go but I rarely use them anyway.

Currently... Slackware on main laptop. Slint (Slackware-based) on mini-pc. MX Linux (fvwm respin), Void, and OpenBSD on old laptop. NsCDE is desktop on all except MX.

Ah okay. So nothing "evil". Was surprised to see your response in my notifications as my compose screen was still churning away after I hit POST. I thought nothing sent. :-)

Interesting that he mentioned Settings not working. Settings has been crashing on me for weeks, if not months. Never checked to find if it is a known issue (no one replied to me on Manjaro Matrix group).

Actually holding out for #SailfishOS to be fully working on the Pro.

I think I'll include this video in exit posts on whatever centralized services I'm still on.

I gave the app a test run. Ultra bright white with no dark mode. #WhiteUIMustDie

On the home screen all images are cropped and can't be fully viewed. Tapping does nothing. Selecting View Post doesn't show the full image either.

Quite different compared to PixelDroid 1.0beta21.

One could consider using a data-only SIM in that case. I've been trying out a couple. JMP is also in the process of offering data-only eSIM/SIM. Currently in testing.

Some folks don't like the fact that Microsoft owns GitHub so they want devs to move away from it.

Nothing dodgy about it. /e/OS uses microG which handles the push notifications. The deGoogling is in the ROM itself. Big difference. I have/had numerous ROMs with microG. On some I just don't enable Google device registration nor Cloud Messaging. Folks can do the same on /e/OS. I don't use/need push messaging anyway. I do believe they're looking into the other push systems.

One thing you may notice, if ever reading their forum, a majority of the users are regular Joes/Janes wanting to use general apps that don't support FOSS push systems anyway.

/e/ doesn't seem to be targeting the hardcore privacy crowd but provide an alternative to the Google ecosystem. As mentioned previously, an intermediary.

Blobs I guess. For some, deGoogled just means no GApps which was the case with almost any custom ROM. In that case Google-free, not deGoogled. For others it means removing Google stuff from within the ROM's source. Not using Google DNS or NTP (network time protocol). Removing any calls to Google. I'm only aware of three ROMs regarding the latter: GrapheneOS, CalyxOS, and /e/OS. None support the Moto G Stylus (Moto G Pro in Europe).

Closest one can get is similar to a ROM setup I have. No GApps nor microG. Using UnifiedNlp for location handling and then control Google on the network level. Either using DNScrypt with decloudus resolvers ("Easily deGoogle, deApple, deMicrosoft, etc any device at any level you choose.") or use a VPN like IVPN with its Hardcore AntiTracker turned on (completely blocks Google and Facebook domains).

Then to ease the pain, use UntrackMe Lite to redirect links: YouTube to Invidious, Instagram to Bibliogram, etc. Use Iceraven or SmartCookieWeb-Preview browsers that can use the Privacy Redirect Firefox add-on for in-browser redirects.

Though I have multiple devices, my daily driver is a Moto G5 Plus potter with MultiROM. The abovementioned setup is LineagOS 14.1 Nougat (July 2021 with back ported security patches - gotta love some of those XDA devs 😁 ). Few weeks and I don't feel I'm missing anything.

As far as I know, probably not. The main apps, TEL and TEL:API, have the same package names as Termux and Termux API respectively. TEL and its modules completely replace their Termux counterparts.

If, for example, the dev had his own repo, TEL would show up under the Termux entry in the F-Droid app (as it currently does). Well, actually, TEL would be the entry and Termux versions would show up under that. That would confuse users because when a new version of Termux is released it may show up as an update to TEL. Or it may not due to signature mismatch. All has to do with the order of the repos. Get hit by that often (my installed Bromite SystemWebView became Ungoogled SystemWebView after adding Ungoogled repo; FakeStore is Google Play Store because of Nanolx repo, etc. etc.). But I digress.

There was a long time between the old version and the current, much improved version so there isn't currently a bunch of regular builds. The dev does have a Telegram update channel for any new builds though.

Hah, this is like an old flashback. Feels like umpteen million years ago when I ran Kent Robotti's DOSLinux (UMSDOS, later LOOP), circa 1990something. Probably my first distro. The frailties of the underlying FAT filesystem was always a problem.

Anyway, your post resulted in me just finding the DOS Subsystem for Linux. An apparent alternative to WSL.

GitHub - haileys/doslinux: Run Linux programs on DOS - https://github.com/haileys/doslinux

I don't think it's really a good idea to run Linux on a non-native filesystem.

Ach, I should've said lemmys or lemmies.

Lemmurs or Lemmers? Just not "lee-murs". 😁