Write Commands

[Raimmaster]

Hey, man, really cool project you have here. We've been working with an ext2 implementation with FUSE, and your project helps a lot.

Is there any way you would implement a write command in this project? Would the saveInode function serve that role?

[TheCodeArtist]

The saveInode() function currently is used by the simple cp command implemented.

The currently implemented feature-set is fairly limited. For example cp assumes the files are only 1 inode in size; unlike real files on ext2 that can span multiple inodes.

Source: https://www.kernel.org/doc/Documentation/filesystems/ext2.txt

There are pointers to the first 12 blocks which contain the file's data
in the inode. There is a pointer to an indirect block (which contains
pointers to the next set of blocks), a pointer to a doubly-indirect
block (which contains pointers to indirect blocks) and a pointer to a
trebly-indirect block (which contains pointers to doubly-indirect blocks).

---

A write command within the ext-shell sounds intriguing.

What do you propose the write command should do?
Obtain a string from the user and save it as a file(limited to size 1inode currently) in the current directory?

...or do you have something else in mind for it?

[TheCodeArtist]

@Raimmaster any suggestions?...

[Raimmaster]

Pardon me, finals and illness hindered my coming here. I like that the scope and implementation of the project is simple. So a simple write example would be best. I thought giving paths to files in the main computer, and writing those files with new file names in the mounted disk would be a good example for write.

[TheCodeArtist]

Sorry, was busy with work. Haven't been able to spend time on this yet.

As i mentioned in the above comment :

The currently implemented feature-set is fairly limited.
For example cp assumes the files are only 1 inode in size;
unlike real files on ext2 that can span multiple inodes.
this would make it error-prone to support copying files between an actual ext2 filesystem and the fairly simple ext2 subset currently supported by ext2-parser.

An alternative might be to allow a write command within the ext-shell in ext2-parser that supports saving a string passed to the write command as a file. (limit on strong length to fit it in a single inode currently).
NOTE: Similar to copy con on MS-DOS "back in the days".

Am open to any simple alternate approaches OR reviewing/integrating a patch/PR along these lines.