update: file structure

파일 구조의 전체적인 개편
다음은 현재 커밋에 대한 tree . -L 3 의 결과입니다.
.
├── core
│   └── scripts
│       ├── kfeature-eval.sh
│       └── kupdate.sh
├── external-tools
│   └── john-the-ripper
│       └── john-1.8.0
├── feature-evals
│   ├── copy_file_range
│   │   └── generate-random-file.sh
│   └── schedutil
│       └── schedutil-auto-test
├── images
│   └── hello.img
├── LICENSE
├── logs
│   └── hello.log
└── README.md

먼저, 최상위 경로에 core, feature-evals, external-tools, images 그리고 logs 디렉토리가 생성 되었습니다.

[directory]core
- 가상 머신 구동이나 설정, 커널 이미지 만들기, 해당 커널 이미지로 부팅하기 등 프로젝트에 중요한 부분에 해당하는 scripts, binaries, source등이 포함되는 디렉토리입니다.
- 이전 scripts 디렉토리를 포함하고 있습니다.
- 이전 scripts/chk 는 core/scripts/kupdate.sh 로 이름이 변경 되었습니다.
- 이전 scripts/schedutil-auto-test 는 feature-evals 디렉토리 하위로 옮겨졌습니다.
- 이전 scripts/generate-random-file 은 feature-evals 디렉토리 하위로 옮겨졌습니다.

[directory]external-tools
- 성능 측정을 위해 직접 만든 도구가 아닌 외부 도구를 포함하는 디렉토리 입니다.
- cpufreq 성능 측정을 위해 사용했던 password cracker 도구인 john-the-ripper 추가했습니다.

[directory]feature-evals
- 특징에 대한 평가 도구/방법을 포함하는 디렉토리 입니다.
- copy_file_range 특징을 측정하기 위해 사용한 스크립트 scripts/generate-random-file은 feature-evals/copy_file_range/generate-random-file.sh 로 옮겨졌습니다.
- cpugovernor 중 하나인 schedutil의 특징을 측정하기 위해 사용한 스크립트 scripts/schedutil-auto-test는 feature-evals/schedutil/schedutil-auto-test.sh로 옮겨졌습니다.
- 현재 schedutil-auto-test.sh는 동작하지 않습니다.

[directory]images
- 성능 측정에 사용하는 커널 이미지를 저장하는 디렉토리 입니다.
- 게스트 OS에서 만들어진 커널 이미지는 이곳에 복사되어 호스트 OS에서도 접근 가능합니다.
- 이전에 성능 측정을 했을 시, 새로 커널 이미지를 만들지 않고 이 디렉토리에서 해당 커널 이미지를 찾아 게스트 OS로 복사 후 성능 측정을 진행합니다.
- hello.img는 실제 커널 이미지가 아닌 커밋을 위한 가짜 파일입니다.

[directory]logs
- 성능 측정에 대한 기록인 로그 파일을 저장하는 디렉토리 입니다.
- hello.log는 실제 로그가 아닌 커밋을 위한 가짜 파일입니다.

**파일 또는 디렉토리 이름에 대한 의견을 남겨 주세요**

**feature-evals나 external-tools은 tools라는 상위 디렉토리로 통합이 필요해 보입니다. feature와 evaluation 부분을 구분지어 생각하는 것이 좋을 것 같습니다. feature에 대한 것은 커널에 구현된 부분, 커널 이미지(version/configure)이고 evaluation은 그것을 평가하는 방법/수단으로 이 두 가지가 1:1 관계가 아닌 1:N 또는 N:M 관계가 가능하기 때문입니다. 실제로 feature에 종속되는듯한 이름의 schedutil-auto-test.sh은 external-tools라고 분류한 john-the-ripper를 사용하기
때문입니다.(schedutil-auto-test.sh 스크립트는 아직 미완성입니다.)**

external-tools/john-the-ripper/john-1.8.0/README

@@ -0,0 +1 @@
+doc/README

external-tools/john-the-ripper/john-1.8.0/doc/CONFIG

@@ -0,0 +1,125 @@
+	Customizing John the Ripper.
+
+John the Ripper's behavior can be customized by editing its
+configuration file.  The configuration file can be named either
+john.conf (on Unix-like systems) or john.ini (on systems which have a
+notion of filename "extensions" and limit them to 3 characters).
+
+This file is searched for in private John's "home directory" and, if
+not found in the private directory and John is installed system-wide,
+also in John's system-wide shared data files directory.
+
+You can set global options, define wordlist and "single crack" mode
+rules, define parameters for "incremental" modes, or even define a new
+external cracking mode.
+
+The configuration file consists of several sections.  Each section
+starts with a line containing its name, in brackets ("[...]").  Sections
+consist either of "variable = value" assignments (each on its own line)
+or of some other content specific to the particular section's type
+(names of such sections start with "List.").  Section and variable names
+are not case sensitive.  Comment lines start with a hash character ("#")
+or a semicolon (";") and are ignored.  Also ignored are any empty lines.
+
+
+	General options.
+
+Some global options can be defined in the [Options] section.  Currently,
+you can set the following options:
+
+Wordlist = FILENAME
+
+Set this to your wordlist file name, to be used in batch mode (which is
+activated when you start John with password files, but not specifying a
+cracking mode).  The default is "$JOHN/password.lst", that is, the file
+named "password.lst" in John's "home directory".
+
+Idle = Y|N
+
+If set to "Y" (yes), John will try to use idle processor cycles only,
+thereby greatly reducing its impact on other system processes.  The
+impact on performance of John itself is negligible except on otherwise
+overloaded systems.  This setting does not affect John's startup time
+and non-cracking invocations of John; it only affects the actual
+cracking.  The default is "Y" (yes).
+
+Starting with version 1.7.7, this setting is ignored for OpenMP-enabled
+hash types when the actual number of threads is greater than 1.
+Unfortunately, it did not work right at least with GNU libgomp on Linux.
+
+Save = SECONDS
+
+This is the time interval (in seconds) between crash recovery file
+updates.  The default is 600 seconds (10 minutes).
+
+Beep = Y|N
+
+If set to "Y" (yes), John will beep when a password is found.  On
+Unix-like systems, it does this by sending the bell character (ASCII
+code 7) to the "standard error" file descriptor (which is normally
+directed to the terminal).  The default is "N" (no).
+
+
+	Defining wordlist and "single crack" modes rules.
+
+The word mangling rules for wordlist and "single crack" modes are
+defined in separate sections, [List.Rules:Wordlist] and
+[List.Rules:Single], respectively.  John the Ripper uses an extension of
+Crack's syntax for the rules.  John supports all of the commands of
+Crack 5.0a plus a few more and, most importantly, it adds a
+preprocessor, which can generate multiple rules from a single source
+line.
+
+When defining rules, simply place one rule (which may include
+preprocessor commands) per line.  See RULES for information on the rules
+syntax and on the preprocessor.
+
+
+	"Incremental" mode parameters.
+
+To define the incremental mode parameters you need to create a section
+called [Incremental:MODE], where MODE is any name that you assign to the
+mode.  There are some pre-defined incremental modes in the default
+configuration file supplied with John, you can use them as templates.
+
+The following parameters are supported:
+
+File = FILENAME
+
+Set this to your charset file name.  See EXAMPLES for an example on how
+to generate a custom charset file.  There's no default.
+
+MinLen = LENGTH
+
+Minimum password length (the number of characters) to try.  The default
+is 0.
+
+MaxLen = LENGTH
+
+Maximum password length to try.  The default is 8 (or CHARSET_LENGTH as
+defined in src/params.h at compile time).
+
+CharCount = COUNT
+
+This allows you to limit the number of different characters (or rather,
+character indices) used.  The effect is that John would favor simple
+longer candidate passwords over more complicated shorter ones, and would
+never attempt rare characters and character combinations, not even for
+really short passwords.  Most of the time, this is undesired.  Another
+use for this option is to make John print a warning if the charset only
+defines less than CharCount characters; this is how the pre-defined
+"incremental" modes use it.  The default is to use as many different
+characters as are defined.
+
+Extra = CHARACTERS
+
+This can be used to make John try some extra characters that don't
+appear in the charset file.  Just list all those characters here and
+they will be added, but considered the least probable.
+
+
+	Defining an external mode.
+
+See EXTERNAL.
+
+$Owl: Owl/packages/john/john/doc/CONFIG,v 1.5 2011/02/27 07:16:16 solar Exp $

external-tools/john-the-ripper/john-1.8.0/doc/CONTACT

@@ -0,0 +1,30 @@
+John the Ripper homepage is located at:
+
+	http://www.openwall.com/john/
+
+There you will find instructions on joining the john-users mailing list.
+You will also be able to browse archives of past discussions.  Please
+share your experience with using John the Ripper and ask questions
+(preferably advanced ones) on the list.  Be sure to specify an
+informative message subject whenever you post to the list (that is,
+something better than "question" or "problem") and mention the version
+of John the Ripper, operating system, compiler, make target, etc. that
+you're using (if applicable).  If you need to provide a binary file,
+place it on a private URL and post that, do not attach the file to your
+message.
+
+If you absolutely need to contact me (the original author of John the
+Ripper) privately, please e-mail me at:
+
+	Solar Designer <solar at openwall.com>
+
+although most messages should really be directed to the list instead
+(and you're more likely to receive a response if you write to the list).
+
+Please don't ask questions until you read the FAQ.
+
+Commercial support for John the Ripper is available from Openwall:
+
+	http://www.openwall.com/services/
+
+$Owl: Owl/packages/john/john/doc/CONTACT,v 1.4 2013/05/30 00:10:11 solar Exp $