Samba VS osxfuse

Samba

The TLDR is that you create the filesystem on Linux/Raspberry Pi. Then you "export" that file system via some software to remote computers. You can use Samba (https://www.samba.org/) to create CIFS shares which can be mounted by either Linux or Microsoft Windows devices. There are of course other software/protocols you can use to export the filesystems like NFS, iSCSI, CEPHFS, etc; but these are a bit more complicated than what a novice can deploy. I would start with Samba/CIFS and then branch out once you get more experienced.

You could try to use samba via cgo.

I think you want a CIFS/SMB client? A quick search turned up smbc, which looks like it does what you want. All three crates are based on libsmbclient, which is a C implementation from the Samba project.

Remember kids, there is always Samba.

> First, the article doesn't say that "Linux is not ready for the desktop" - or concern itself with this as an abstract question.

Well, it does, but in a sarcastic manner:

"Yeah, let's consider Linux an OS ready for the desktop :-)."

> Also, I find the "GNU/Linux is already ready for the desktop; I and others use it" argument tired. I've used GNU/Linux for the desktop in 1998, but it sure as hell wasn't ready then.

Conversely, that it doesn't work for certain people does not mean that "it is not ready", which the post does state (sarcastically) as I pointed out above.

> Many use cases aside...

I'm not sure how the browsing, docs and email is miserable, maybe you can expand on that. The video editing is indeed a bit limited from my experience too. However, I don't think "limited proprietary options" is a problem. The community largely and specifically avoids proprietary software. Proprietary incursions into the community are generally seen as a negative thing. And for the lack of codecs, software patents for the most part are to blame.

And then it just comes to my original statement; many things stated in the article are non-issues to most Linux users or just falsehoods:

- Neither Mozilla Firefox nor Google Chrome use video decoding and output acceleration in Linux.

Firefox does.

- NVIDIA Optimus technology is a pain

NVIDIA is a pain.

- You don't play games, do you?

I do.

- Linux still has very few native AAA games.

So "it's not ready" because it doesn't have AAA games? What a pitty.

- To be fair you can now run thousands of Windows games through DirectX to Vulkan/OpenGL translation (Wine, Proton, Steam for Linux) but this incurs translation costs and decreases performance sometimes significantly.

No, not 'significantly' for dxvk.

- Also, anti-cheat protection usually doesn't work in Linux.

For good reason. Blame the dev, and don't make it work on Linux.

- Microsoft Office is not available for Linux

Thankfull.

- LibreOffice often has major troubles properly opening, rendering or saving documents created in Microsoft Office.

And whose fault is this? Use ODT.

- Several crucial Windows applications are not available under Linux.

Thankfully. Also, 'crucial' is subjective.

- In 2022 there's still no alternative to Windows Network File Sharing.

It's available since 1992: https://www.samba.org/

- Linux doesn't have a reliably working hassle-free fast native (directly mountable via the kernel; FUSE doesn't cut it) MTP implementation.

I can transfer files to my phone just fine.

- Too many things in Linux require manual configuration using text files.

No.

etc.

I have a media server that runs ubuntu, and today I wanted to copy some files off of it from my windows laptop. But the samba shares weren't showing up in file explorer (but they showed up on fine on my macbook).

brew info samba samba: stable 4.16.0 (bottled) SMB/CIFS file, print, and login server for UNIX https://www.samba.org/ Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/samba.rb License: GPL-3.0-or-later ==> Dependencies Build: [email protected] ✔ Required: gnutls ✘, krb5 ✔ ==> Caveats To avoid conflicting with macOS system binaries, some files were installed with non-standard name: - smbd: /usr/local/sbin/samba-dot-org-smbd - profiles: /usr/local/bin/samba-dot-org-profiles ==> Analytics install: 1,477 (30 days), 3,287 (90 days), 6,917 (365 days) install-on-request: 1,459 (30 days), 3,246 (90 days), 6,863 (365 days) build-error: 5 (30 days)

Install macFUSE, thank me later: https://osxfuse.github.io

I didn't exactly use any 'tutorial'. Assumming you can already SSH to the target machine, you just need to install both these pkgs then reboot to 1TR Recovery Mode and choosing Reduced Security and choose to enable Kernel Extension and then reboot again goto Security & Privacy and Allow the extension, and that's it you can now use it.

Yeah, FUSE is Linux only. But for completeness, for macs there is macFUSE, and for Windows there is winfsp. Both of these have fewer filesystems than FUSE, and I've used neither so I don't know how well they work.

https://github.com/osxfuse/osxfuse/wiki/List-of-macFUSE-File...

https://winfsp.dev/doc/Known-File-Systems/

Weird. Where did you download (lat/new)est MacFuse from? https://osxfuse.github.io/ I hope!

I lead a project that included shipping a filesystem driver and a virtual disk on Windows.

What I did to learn the lower-level APIs, and perform initial testing on the driver, was write a "mirror" drive. The user-mode code pointed to a folder on disk, the driver made a virtual disk drive, and all reads and writes in the virtual disk drive went to the mirror folder.

On Windows, you can implement something like that using Dokany, Dokan, or Winfsp. On linux, there's the Fuse API. On Mac, there's MacFUSE.

Even if you don't do a "mirror" drive, understanding the callbacks that libraries like Dokany, Dokan, Winfsp, and Fuse do helps you understand how IO happens in the driver. Many IO methods provided in popular languages provide abstractions above what the OS does. (For example, the Windows kernel has no concept of the "Stream" that's in your C# program. The "Stream"'s Position property is purely a construct within the .Net framework.)

https://dokan-dev.github.io/

https://github.com/dokan-dev/dokany

https://osxfuse.github.io/

Another place to start is the OS's documentation itself. For example, you can start with Window's CreateFileA function. This typically is what gets called "under the hood" in most programming languages when you open or create a file: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/...

"FUSE-T is a kext-less implementation of FUSE for macOS that uses NFS v4 local server instead of a kernel extension. The main motivation for this project is to replace macfuse (https://osxfuse.github.io/) that implements its own kext to make fuse work. With each version of macOS it's getting harder and harder to load kernel extensions. Apple strongly discourages it and, for this reason, software distributions that include macfuse are very difficult to install. Additionally, the macfuse kext is unstable, may cause frequent system crashes and kernel lock-ups. Given those limitations many software publishers are unable to use macfuse anymore. FUSE-T doesn't make use of kernel extension, it implements its own userspace server that converts between FUSE protocol and NFS calls and let macOS mount NFS volume instead of a kernel filesystem."

MacFuse (ntfs-3g) and a Foolproof way of getting it working via Homebrew.

macos doesn’t support many Linux file system formats. You’ll have to use something like macFUSE https://osxfuse.github.io/