tanner-g / iknowdediscovery Goto Github PK

takes an file name, returns an inode

when calling scripts from main.sh, there is:
./orphanNodes <partition_path>
./inodes.sh <partition_path> <partition_type>

(will update with more)

Find all inodes that have been freed in X/given timeframe

possiblly done with fsstat

oh my...
we have hit a file organization problem....

we have files everywhere....

so.. when its not 2:18 am, lets make folders for each subroutine within /scripts/ so that i can better ensure that we didn't lose anything

i think we talked about making a command line front end to start out with and depending on what our time looks like towards the end we can incorporate a GUI. Does that sound like a good idea?

So, where are we getting an ext2 file system???. i forgot that we need to make one and test from it.

i think we may need to add error handling for orphannodes script on the line 12:" inodes.pop"..

i got popping an empty list, but I think that might be because the inodes.sh didn't work.
at meeting, we should look at error, and see if we can figure out what is generating this problem. atm, im going to try to add try/catches for it.

is one reliant upon the other? if so, i should change the option menu I wrote

network graph on plotly

mapping inodes and file name stats?

i think we talked about writing all the bash commands we need to get information for out "stats".

initial group meeting to discuss design and work load.

Given all files in a directory AND all other files which share inodes, find/show files which are open and/or open and marked for deletion

@tjz3497 i think i have an idea about why we get the hardlink detection problem

there might not have been any hardlinks present in the dir it was running in. does it handle an empty set? just a thought i had at 2:20 am...

i think a quote would make it more complete

we suggested:
-python
-ruby
-bash

Bash script
Take in a directory path and find all file names
Find their inodes
Find all other files with those inodes

keep track of what dependencies we get along the way

do we need a prompt that says a "report.txt" was generated... not a selection, but a notification type menu?

Describe each file you have authored in a brief statement in the readme.md

create some ascii art that shows the start of the script tha twill then call the script to detect the type

type --> ext2 or ext3/4

Given a directory, find (and eventually visualize) whether any of the files are open and/or open and marked for deletion

i might have a ./iKnowdeDiscovery thing and maybe package the project somehow...