ssteuteville / makefs Goto Github PK

I'm a little confused about how to get this to work. I'll do some reading and try again tomorrow. If you figure it out and know the details be sure to share!

The error happens when trying to compile at commit: 3c22094

For some reason when I am using the filesytem I don't have the correct permissions to mkdir or do any kind of write. I'll be looking into this soon but let me know if you have any ideas.

Implement our make file generation design from the other issue.
system calls that have to do with this:

create - generating the makefile and the meta data file.
rename - updating makefile?
figure out which system call removes a file - update the meta data accordingly

This list isn't based on finite design decisions. We may decide to leave some of this out -- for now.

I know... I didn't write any comments!!

.< I'll do it soon lol.

Normally the system calls return the error in errno. We need to write a function that will change or retvals to -errno in error. This is FUSE convention.

We should try to understand fully the macros we are using and any other syntax we don't fully understand.

We need to make sure that all of the file names and paths we use are parsed correctly.

So far this is an issue for:
meta_path in the makefs_create function.
also in makefs_create this is an issue when comparing path to "/makefile"

So I was thinking and this whole idea would be so much better if we could add the name of files that are copied or moved into one of the file systems directories to the meta data.

This isn't a creat() type issue.

We would have to figure out which system call to update, but I don't think it would be too difficult.

This way already written projects can have makefiles generated as well.

We should break driver.c into functions. First we need to design how this is going to work. Time to go back to high level thinking?

Close all issues.

The next step in converting to c++.

I already stubbed this out. If we decide to do it we need to add this functionality to renaming and removing files, a bit of an issue.

We should focus on which system calls we will use.
We might not need to know how to implement them yet.
I just would like to say to Adam, "Here are the functions we think we are going to use. Does anything stand out to you that makes you think our understanding is incorrect? Would you suggest any changes to our design?"
Maybe he will even work an example with us to get us rolling.

Do eet.

So how do we want makefs to function?

Do we want it to create the makefile for us as we write?
OR
Do we want it to create the makefile for us when we execute a specific command?
I think it would be awesome if we could just type:
"run ..." within a directory and have the following happen:

1. A makefile is generated
2. The project is compiled/linked/etc
   3)The program runs

Also I like the idea of making the makefiles hidden. So, we should start looking into how to generate a hidden file via FUSE. Also how to over load a fuse system call to do what your program does. I'm going to start a design document that we can work on and go to Adam with on Monday.

Close all issues in this milestone.

We need to create a function that calculates the correct path relative to the root_dir. Then we need to go and use it to give the system calls that use paths the correct path.

note: I noticed that some of the "link" system call parameters also need to use this new function.

Add the noted functionality to mkdir

Big step for converting to C++.