Re: Running an editor from ANSI C

On 12/06/2024 13:10, Malcolm McLean wrote:

On 12/06/2024 11:37, tTh wrote:

On 6/12/24 10:08, Malcolm McLean wrote:
>

I'd expect to run ksh commands from within ksh, bash commands from
within bash, etc.
>
I wouldn't expect a filesystem to be part of the shell at all.
>

>
You'd expect to have a FileSystem file, and to type in at your ksh orz
zsh, cd "myfilesysyem.xml" and for ksh to mount it. But of course ksh
can't do that, because it doesn't recognise that format.

>
    Unless someone writes a module for fuse that allows this kind
    of manipulation.
>
    I've already come across this kind of thing, which made it
    possible to read images from floppy disks of old systems.
>

I'd be interested in doing that. And may thnaks to David Brown for mentining that this isnpossible. However it wouldn't be part of Baby X.
 I had a quick look at the fuse webite, and I couldn't for the life of me work out how to write a short fuse script to mount such a simple directory structure as a FileSystem XML file.
 I'm sure it's possible and not too hard to do. But it's the sort of thing people do for money.
 

I'm sure some people do it for money - but I think others make libfuse filesystems for fun.  Typical uses include accessing remote data (such as over ssh, webdav, google drives), supporting weird, awkward or outdated filesystems (like NTFS), accessing data within packed or encrypted files (like zip files or backup files), prototyping filesystems that you hope will make it to the Linux kernel one day, exposing interfaces or control information like a file system, and so on.
At its simplest, it's just a matter of implementing functions for listing a directory, opening and closing files, reading and writing them, and similar functions.  I'd imagine that write support for files within your XML file would be awkward, but I would be very surprised if anything in a libfuse solution is at all harder than implementing the same thing in your shell.