casinee app
appca****@gmail*****
Tue Jun 26 17:30:03 JST 2012
I chose the AKARI. I downloaded the akari-1.0.27-20120505.tar.gz and uncompressed it to the root directory of kernel source code. Then i used commands below to compile it: # make SUBDIRS=$PWD/akari modules # make SUBDIRS=$PWD/akari modules_install After, i copied the *.ko files to the filesystem of the embedded device and used the command below to add it to the kernel: #insmod akari.ko The output is: one_wire_status: 4 security_ops=c0799ca4 find_task_by_vpid=c019be10 find_task_by_pid_ns=c019bdfc __d_path=c01f6664 AKARI: 1.0.27 2012/05/05 Access Keeping And Regulating Instrument registered. Is this correct??? After the kernel module, i compiled the usrspace tools ccs-tools-1.8.3-20120414.tar.gz. When i executed the command: # /usr/lib/ccs/init_policy --module_name=akari it work correctly, the output is: Creating policy directory... OK Creating configuration directory... OK Creating exception policy... OK Creating domain policy... OK Creating manager policy... OK Creating default profile... OK Creating stat policy... OK Creating module loader... OK Creating configuration file for ccs-editpolicy ... OK Creating configuration file for ccs-auditd ... OK Creating configuration file for ccs-patternize ... OK Creating configuration file for ccs-notifyd ... OK But when i use the ccs-editpolicy, there always is only the <kernel> domain. Does the AKARI is not work correctly？ 2012/6/19 Tetsuo Handa <from-****@i-lov*****>: > casinee app wrote: >> >> 2012/6/19 Tetsuo Handa <from-****@i-lov*****>: >> > casinee app wrote: >> >> > You can send me a tarball if you want me to make ccs-patch for your 2.6.30 >> >> > kernel. >> >> I've read the massage on the site you gave me, which files should be >> >> contained in the tarball? >> > >> > The tarball should contain files that will be patched by >> > http://sourceforge.jp/projects/tomoyo/svn/view/trunk/1.8.x/ccs-patch/patches/ccs-patch-2.6.30.diff?root=tomoyo&view=co&revision=HEAD&content-type=text%2Fplain . >> > Of course, you can use readymade patch if it applies cleanly. >> The attachment contains the files(34 files) described in the >> ccs-patch-2.6.30.diff. Thanks. > > ccs-patch-2.6.30.diff in ccs-patch-1.8.3-20120610.tar.gz will apply. > You can follow instructions at http://tomoyo.sourceforge.jp/1.8/android-arm.html or > http://tomoyo.sourceforge.jp/1.8/cat760-sh.html whichever suits better for your case. > ---------- > Applying patch ccs-patch-2.6.30.diff > patching file fs/compat.c > patching file fs/compat_ioctl.c > Hunk #2 succeeded at 2799 (offset -1 lines). > patching file fs/exec.c > patching file fs/fcntl.c > patching file fs/ioctl.c > patching file fs/namei.c > patching file fs/namespace.c > patching file fs/open.c > patching file fs/proc/version.c > patching file fs/stat.c > patching file include/linux/init_task.h > patching file include/linux/sched.h > patching file include/linux/security.h > patching file kernel/compat.c > patching file kernel/fork.c > Hunk #2 succeeded at 1098 (offset 13 lines). > Hunk #3 succeeded at 1296 (offset 10 lines). > patching file kernel/kexec.c > patching file kernel/module.c > patching file kernel/ptrace.c > patching file kernel/sched.c > Hunk #1 succeeded at 5678 (offset -1 lines). > patching file kernel/signal.c > patching file kernel/sys.c > patching file kernel/sysctl.c > Hunk #1 succeeded at 1709 (offset 2 lines). > patching file kernel/time.c > patching file kernel/time/ntp.c > patching file net/ipv4/inet_connection_sock.c > patching file net/ipv4/inet_hashtables.c > patching file net/ipv4/raw.c > patching file net/ipv4/udp.c > patching file net/ipv6/raw.c > patching file net/ipv6/udp.c > patching file net/socket.c > patching file net/unix/af_unix.c > patching file security/Kconfig > Hunk #1 succeeded at 139 (offset 20 lines). > patching file security/Makefile > > Now at patch ccs-patch-2.6.30.diff > > _______________________________________________ > tomoyo-dev-en mailing list > tomoy****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/tomoyo-dev-en
TOMOYO
Fork