Skip to content
This repository has been archived by the owner on Sep 27, 2020. It is now read-only.

Changing Bios check behavior #25

Open
dginhoux opened this issue Sep 25, 2015 · 2 comments
Open

Changing Bios check behavior #25

dginhoux opened this issue Sep 25, 2015 · 2 comments
Labels

Comments

@dginhoux
Copy link

Just check bios file by comparing files md5 and required md5,if they match view a green dot, if not a red point

And check if every system has it's necessary bios file(s).... And the same system green/red

@sveetch
Copy link
Member

sveetch commented Sep 25, 2015

This is related to #17 where i stated to keep the current behavior (only checking on the fly when uploading a new bios).

Problem is, i hardly try to keep the Django instance ressources at the lowest level i can. Checking md5 for every existing bios on FS will probably be a huge CPU eater on the Raspberry2 (and more on rpi 1).

Also, i like your second idea, but it is the same problem than i said before, plus we can't really know what systems the user want to use or not, so checking all of them will often be more charge for nothing.

For now, this will stay as is, until i'm more confident about instance ressources usage, then we could think about another way of bios checking.

@sveetch sveetch changed the title Bios check Changing Bios check behavior Oct 17, 2015
@fufroma
Copy link

fufroma commented Apr 6, 2016

You can check it ONE time, and store the result in a cache file.
If the bios file is newer than the cache file, you know you have to re-check it. If the bios file is older, you know that the stored result is the "real" one.

OK, you can mess with this check, but you have to want to ;). So a "recheck" button who rebuild the cache can be a good idea.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants