-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask for clone to python #12
Comments
Hi @mamin27 , That shouldn't be too hard! I'd suggest you take a look at the Internals section of the readme (https://github.com/charlesbaynham/OSFS#internals) for a description of the file format. Let me know if you do start a clone, I'd be happy to give some feedback. C |
Thanks Charles, I would plan to look at all information and probably some new features. Firstly I will prepare some logical file system structure with your standards. I need also something like reserve space for file, appending file. Something like 'ls -ls' Add timestamp for file ... I will communicate with you about it. I would like to use your file system name. The Idea is also that the EEPROM content will be compatible with your code. Regards Marian |
Great, let’s stay in touch. Adding a timestamp to the OSFS spec is probably out of scope: that would make it mode complex which doesn’t really fit with the “overly simplified” theme! There’s nothing to stop you storing a timestamp in the “data” section of a file though, so you could use a python-based OSFS-compatible EEPROM driver to store your files, which include timestamp data and the file contents themselves.
|
Hello Charles,
I would like to clone your OSFS into python 3 version into my project https://github.com/mamin27/ecomet_i2c_raspberry_tools. I would like to use your code logic for EEPROM operation system.
I would like to know your opinion? The code will be different but I would like to use your logic of file storing into EEPROM. Currently I am working on some different code but after half year I would like to start.
Regards Marian Minar
The text was updated successfully, but these errors were encountered: