what Dazuko?? 被搞瘋了,不玩了-.-
Avira AntiVir for Linux 上會出現的怪東西><

[root@localhost antivir-workstation-pers-2.1.10-15]# ln -s /usr/lib/libc.so /usr/lib/libc.so.5
[root@localhost antivir-workstation-pers-2.1.10-15]# cd contrib/dazuko/
[root@localhost dazuko]# tar -zxvf dazuko-2.3.2.tar.gz
[root@localhost dazuko]# cd dazuko-2.3.2
[root@localhost dazuko-2.3.2]# ./configure
checking host system type... Linux
checking for make utility... ok (make)
checking for C compiler... none found
error: no C compiler found on this system

[root@localhost dazuko-2.3.2]# yum install gcc-c++
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for gcc-c++ to pack into transaction set.
gcc-c++-4.1.2-13.fc6.i386 100% |=========================|  56 kB    00:00    
---> Package gcc-c++.i386 0:4.1.2-13.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: gcc = 4.1.2-13.fc6 for package: gcc-c++
--> Processing Dependency: libstdc++-devel = 4.1.2-13.fc6 for package: gcc-c++
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for gcc to pack into transaction set.
gcc-4.1.2-13.fc6.i386.rpm 100% |=========================|  64 kB    00:00    
---> Package gcc.i386 0:4.1.2-13.fc6 set to be updated
---> Downloading header for libstdc++-devel to pack into transaction set.
libstdc++-devel-4.1.2-13. 100% |=========================| 135 kB    00:00    
---> Package libstdc++-devel.i386 0:4.1.2-13.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: libgomp.so.1 for package: gcc
--> Processing Dependency: libgomp = 4.1.2-13.fc6 for package: gcc
--> Processing Dependency: cpp = 4.1.2-13.fc6 for package: gcc
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for cpp to pack into transaction set.
cpp-4.1.2-13.fc6.i386.rpm 100% |=========================|  57 kB    00:00    
---> Package cpp.i386 0:4.1.2-13.fc6 set to be updated
---> Downloading header for glibc-devel to pack into transaction set.
glibc-devel-2.5-18.fc6.i3 100% |=========================| 108 kB    00:00    
---> Package glibc-devel.i386 0:2.5-18.fc6 set to be updated
---> Downloading header for libgomp to pack into transaction set.
libgomp-4.1.2-13.fc6.i386 100% |=========================|  54 kB    00:00    
---> Package libgomp.i386 0:4.1.2-13.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: glibc-headers for package: glibc-devel
--> Processing Dependency: glibc-headers = 2.5-18.fc6 for package: glibc-devel
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for glibc-headers to pack into transaction set.
glibc-headers-2.5-18.fc6. 100% |=========================| 142 kB    00:00    
---> Package glibc-headers.i386 0:2.5-18.fc6 set to be updated
--> Running transaction check

Dependencies Resolved

 Package                 Arch       Version          Repository        Size
 gcc-c++                 i386       4.1.2-13.fc6     updates           3.4 M
Installing for dependencies:
 cpp                     i386       4.1.2-13.fc6     updates           2.6 M
 gcc                     i386       4.1.2-13.fc6     updates           5.2 M
 glibc-devel             i386       2.5-18.fc6       updates           2.0 M
 glibc-headers           i386       2.5-18.fc6       updates           608 k
 libgomp                 i386       4.1.2-13.fc6     updates            75 k
 libstdc++-devel         i386       4.1.2-13.fc6     updates           9.4 M

Transaction Summary
Install      7 Package(s)        
Update       0 Package(s)        
Remove       0 Package(s)        

Total download size: 23 M
Is this ok [y/N]: y
Downloading Packages:
(1/7): cpp-4.1.2-13.fc6.i 100% |=========================| 2.6 MB    00:13    
(2/7): glibc-devel-2.5-18 100% |=========================| 2.0 MB    00:10    
(3/7): glibc-headers-2.5- 100% |=========================| 608 kB    00:02    
(4/7): libstdc++-devel-4. 100% |=========================| 9.4 MB    00:48    
(5/7): libgomp-4.1.2-13.f 100% |=========================|  75 kB    00:00    
(6/7): gcc-4.1.2-13.fc6.i 100% |=========================| 5.2 MB    00:26    
(7/7): gcc-c++-4.1.2-13.f 100% |=========================| 3.4 MB    00:17    
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: libgomp                      ######################### [1/7]
  Installing: libstdc++-devel              ######################### [2/7]
  Installing: glibc-headers                ######################### [3/7]
  Installing: glibc-devel                  ######################### [4/7]
  Installing: cpp                          ######################### [5/7]
  Installing: gcc                          ######################### [6/7]
  Installing: gcc-c++                      ######################### [7/7]

Installed: gcc-c++.i386 0:4.1.2-13.fc6
Dependency Installed: cpp.i386 0:4.1.2-13.fc6 gcc.i386 0:4.1.2-13.fc6 glibc-devel.i386 0:2.5-18.fc6 glibc-headers.i386 0:2.5-18.fc6 libgomp.i386 0:4.1.2-13.fc6 libstdc++-devel.i386 0:4.1.2-13.fc6
[root@localhost dazuko-2.3.2]# ./configure
checking host system type... Linux
checking for make utility... ok (make)
checking for C compiler... ok (cc)
kernel source in /lib/modules/2.6.20-1.2962.fc6/source... no
kernel build source in /lib/modules/2.6.20-1.2962.fc6/build... no
kernel build source in /usr/src/linux... no
kernel source in /usr/src/linux... no
error: no kernel source files found

what Dazuko??
還要 C Compiler @@" gcc-c++
裝完又說no kernel source orz..................

Coolaler BB滄者極限相關文獻:


Dazuko - it's time to get serious

A common interface across all platforms is needed for 3rd party file access control. With such an interface, focus could be redirected from OS hacking to solving real problems. The interface is here. It is called Dazuko.


Dazuko - 該變得嚴肅了

在全部平台的一個普通界面被為第3個聚會文件存取控制需要。 有這樣的界面,集中可能解決真正問題從黑客OS被使改方向。 界面在這裡。 它被叫為Dazuko。 

This project provides a device driver allowing 3rd-party (userland) applications to execute file access control. It was originally developed by Avira GmbH (formerly known as H+BEDV Datentechnik GmbH) to allow on-access virus scanning. Other uses include a file-access monitor/logger or external security implementations. It operates by intercepting file access calls and passing the file information to a 3rd-party application. The 3rd-party application then has the opportunity to tell the device driver to allow or deny the file access. The 3rd-party application also receives information about the access event, such as accessed file, type of access, process id, and user id.

Dazuko has been released as Free Software in order to allow users to compile the device driver for their own custom kernels. It also gives the project an opportunity to establish a common interface for 3rd-party file access control. Free Software provides the added benefit of increased robustness and security, having many eyes investigate the source code. Although Avira GmbH will continue to support the project and provide commercial software that utilizes the Dazuko driver via its interface, this project is Free Software and is in no way owned by Avira GmbH. This project provides a fully functional device driver with a well-defined interface, allowing any organization to develop software to utilize Dazuko.

The current status of the project is usable for Linux 2.2-2.6, Linux/RSBAC, and FreeBSD 4.x-6.x. However we would like to see the project expand to support other operating systems such as MacOS X, Solaris, OpenBSD, and Windows, as well as expand in functional capabilities.


這項工程提供一個設備驅動器允許執行文件存取控制的第3 聚會的(userland)申請。 (作為H+BEDV Datentechnik股份有限公司以前知道)允許關於進入的病毒掃描的Avira股份有限公司最初開發了它。 其他用途包括一台文件進入監視器/伐木工或者外部安全實施。 它以攔截進入叫的文件並且度過文件訊息隨著一3 聚會應用經營。 第3 聚會的應用然後有機會告訴設備驅動器允許或者否認文件進入。 第3 聚會的應用也得到關於進入事件的訊息,例如存取的文件,進入的類型,處理Id 和用戶Id。

Dazuko被釋放當時免費軟體為了允許要因他們自己果仁風俗的而編輯那些設備驅動器的用戶。 建立第3 聚會的文件存取控制的一個普通界面也給工程一次機會。 免費軟體提供增加的穩定性和安全的被增加的好處,讓很多眼睛調查源碼。 雖然Avira股份有限公司將繼續支持工程並且提供透過它的界面利用Dazuko 驅動器的商務軟體, 這項工程是免費軟體並且決不被Avira股份有限公司擁有。 這項工程用一個明確的界面提供一個完全功能的設備驅動器,允許任何組織開發軟體利用Dazuko。

工程的當今的地位對于Linux 2.2-2.6,Linux/RSBAC 和FreeBSD 4.x-6.x可用。 但是, 我們想要 看見工程擴大支持其他作業系統(例如MacOS X,Solaris,OpenBSD 和Windows),以及用功能的能力擴大。 

There are 4 basic steps to loading Dazuko. However, you should have experience with compiling your kernel. If you do not have this experience, it is suggested that you refer to the various available handbooks to learn about the kernel building process. Building your own kernel not only allows your system to run optimally, but also gives you a chance to work with and get a feel for the heart of your operating system.

Note: If you already have the source code to your kernel and simply want to build Dazuko without building a new kernel, then you can. However, you need to be certain that the source code you have is really the same as the kernel you are running.

Linux: Even though you have the Linux kernel source code, it may not be configured. See FAQ #10 for more information about this.


Step 1: Get your kernel source code  Dazuko is a kernel module. Once a kernel module is loaded, it becomes one with your kernel. Therefore, Dazuko will call and share the same set of functions as the kernel. This is why the kernel source code is required in order to build Dazuko.

It is highly recommended that you first build and install a kernel. Then it is certain that the kernel source code you use to build Dazuko matches the running kernel. If you do not know how to do this, read the opening paragraph above.

Many distributions provide packages with the kernel source code. If you do not plan on building a new kernel, make sure you install the proper kernel source packages for your distribution.

Linux: See FAQ #10 for information about configuring your Linux kernel source code.
Step 2: Compile Dazuko  Once the source code for your running kernel is available, you can build Dazuko. First a Makefile must be generated by running:


This will determine what kind of system you have and any special flags that need to be set. Then you can compile Dazuko with:


This will create the device driver as well as a couple example programs. Under Linux 2.2-2.4 the device driver is named dazuko.o. Under Linux 2.6 and FreeBSD it is named dazuko.ko.

If you get any warnings or errors from either of the steps above, something may not be correct. Please read over the FAQ if you encounter problems.
Step 3: Insert Dazuko  Once you have successfully compiled Dazuko, the final step is to insert the module into the kernel. To do this, you must have root priveledges. This can be done with the command:

Linux 2.2-2.4: /sbin/insmod dazuko.o
Linux 2.6: /sbin/insmod dazuko.ko
FreeBSD: /sbin/kldload dazuko.ko

If you don't get any messages, this is a good sign. To check if the module has been loaded type:

Linux 2.2-2.6: cat /proc/modules
FreeBSD: /sbin/kldstat

If you see "dazuko" listed then the Dazuko driver has been successfully loaded. Unless you are using devfs, the device node must now be created. With devfs, device nodes are created automatically.

Under Linux
The device major number for Dazuko must be found. This is done with:

cat /proc/devices

You should see "dazuko" listed along with its device major number (usually 254). For example purposes, I will assume this number is 254. The commands to create the device node are:

mknod -m 600 /dev/dazuko c 254 0
chown root:root /dev/dazuko

Under FreeBSD 4
mknod /dev/dazuko c 33 0
Step 4: Test Dazuko  So you've got Dazuko compiled and inserted into your kernel. Now what?

Once Dazuko is loaded, an application is able to handle file access control through the Dazuko device. To test Dazuko it is recommended that you try out the example program included (in the example_c subdirectory). You can build the example program with:

cd example_c

For security reasons Dazuko will only operate with processes that are running as root. Therefore you need to be root when you run the example program. The example program takes a list of paths to "watch" as arguments.

./example /home /usr/home

Once the example program is running, open up another terminal or shell. Open up some file within the /home directory (or any subdirectory thereof). As the files are accessed, the example program should output various information.

The example program always permits the accesses, however another application could be written that denies file accesses in certain conditions. This allows a 3rd party to write complex file access control schemes (or customized file access logging utilities).


對裝Dazuko有4種基本的措施。 不過,你應該有有編輯你的果仁的經驗。 如果你沒有這次經驗,建議你參考各種各樣的可得到的手冊了解果仁大樓過程。 建造你自己的果仁不僅允許你的系統最佳運轉, 而且給你機會與合作並且為你的作業系統的心拿到一種感覺。

注意到︰ 如果你已經對你的果仁有源碼並且僅僅想要建造Dazuko而不建造一顆新果仁, 然後你能。 不過,你需要確信你有的源碼真的與你正運轉的果仁相同。

Linux︰ 即使你有Linux 果仁源碼,它可能不成形。 為更多的關於這的訊息看見FAQ #10。


第1步︰得Dazuko的源碼果仁核心模塊。 一旦一個核心模塊被裝,它和你的果仁團結一致。 因此,Dazuko 將叫並且分享與果仁相同的套功能。 為了建造Dazuko,這是果仁源碼被要求的原因。

非常推薦為那你首先建造並且安裝一顆果仁。 然後,可以確信你使用的果仁源碼建造Dazuko比賽個跑的果仁。 如果你不知道怎樣做這,讀上面的開始段落。

很多配給為包提供果仁源碼。 如果你不打算建造一顆新果仁,保證你為你的分發安裝適當的果仁源包。

Linux︰ 為關於使你的Linux 果仁源碼成形的訊息看見FAQ #10。
第2步︰編輯Dazuko那些源碼一次適合你跑果仁可提供,你建造Dazuko 能。 首先Makefile 必須透過跑被產生︰


這將確定你有哪種系統和需要被確定的任何專用標記。 然後你能編輯Dazuko 用︰

這將建立設備驅動器和一個夫婦例子計畫。 在Linux 2.2-2.4下設備驅動器被命名為dazuko.o。 在Linux 2.6 和FreeBSD下它被命名為dazuko.ko。

如果你在上面從任何一個台階得到任何警告或者錯誤,某些事情可能不是正確的。 如果你遇到問題,請略讀FAQ。
第3步︰你一次插入Dazuko Dazuko成功編輯,那些最後步驟是把模件插入那些果仁中。 為了做這,你必須有根priveledges。 這可能被處理命令︰

Linux 2.2-2.4︰/sbin/insmod dazuko.o
Linux 2.6︰/sbin/insmod dazuko.ko
FreeBSD︰ /sbin/kldload dazuko.ko

如果你不得到任何消息,這是一個好標誌。 檢查是否模件是被裝的類型︰

Linux 2.2-2.6︰cat /proc/modules
FreeBSD︰ /sbin/kldstat

如果你看見"dazuko"被那時列舉,Dazuko 司機已經被成功裝。 除非你正使用devfs,否則設備節點現下必須被建立。 由於devfs,設備節點被自動建立。

Dazuko的設備主要的數目必須被發現。 這被處理︰

cat /proc/modules

你應該看"dazuko"與它的設備一起列舉主要的數目的(通常是254)。 例如目的,我將以為這數目是254。 創造節點的設備的命令︰

mknod -m 600 /dev/dazuko c 254 0
chown root:root /dev/dazuko

在FreeBSD 4下
mknod /dev/dazuko c 33 0
第4步︰測試Dazuko 如此你使編輯並且插入的Dazuko陷入果仁。 現下有什麼嗎?

一旦Dazuko被裝,應用能透過Dazuko 設備處理文件存取控制。 為了測試Dazuko,被推薦你試用包括的例子計畫(在例子裡 _ c子目錄)。 你能建造例子計畫用︰

cd example_c

由於安全原因Dazuko 只將用正作為根跑的過程操作。 當你營運例子計畫時,因此你需要是根。 例子節目花費一個通向"看"的路徑的目錄作為辯論。

./example /home /usr/home

一旦例子計畫運轉,打開末端的另一個或者殼。 打開文件一些在內/主目錄(或者任何程度其子目錄)。 因為文件被存取,例子計畫應該輸出各種各樣的訊息。

例子計畫總是允許出入口,但是,另一應用可能寫否認陸續編入出入口肯定狀況。 這允許第3 聚會寫信告訴複雜的文件訪問控制方案(或者定製文件進入記錄電力公司)。 

1.1 What is Dazuko?

Dazuko aims to be a cross-platform device driver that allows applications to control file access on a system. By installing the driver, your system will be able to support file access control applications that are based on Dazuko. As this project becomes more popular and more applications choose Dazuko for their file access needs, it is hoped that this driver will become a common component of most systems.


1.2 How do I use Dazuko?

In order to use Dazuko you must first build and insert the kernel module. This then adds a new device to your system (/dev/dazuko). Once you have the Dazuko device, you can run applications that take advantage of the file access control features Dazuko provides.

If you are interested in building your own applications, check out the Dazuko interface specification. You may also want to look at the example program provided with Dazuko for a working reference.

A list of applications known to work with Dazuko can be found on the applications page.


1.3 What operating systems are supported by Dazuko?

The current release of Dazuko supports Linux 2.2-2.6, Linux/RSBAC, and FreeBSD 4.x-6.x kernels. However, it is slowly being expanded to support other operating systems such as MacOS X, Solaris, NetBSD, OpenBSD, and Windows. Although all these operating systems have very different control mechanisms, it should still be possible to integrate Dazuko.


1.4 What license is Dazuko under?

In order to allow Dazuko to be used on as many operating systems (both proprietary and free) as possible and in order for all software (both proprietary and free) to be able to incorporate the driver's interface, Dazuko uses a BSD license. However, the Dazuko device driver has "extension modules" to implement platform-specific functionality. These extension modules will fall under the license of the operating system on which they will run, thus forcing the complete device driver to this license as well (at compile-time). Here is a quick summary:

Dazuko Application Interface (on all platforms): BSD License
Dazuko device driver (Linux): GPL License
Dazuko device driver (FreeBSD): BSD License


1.5 Does Dazuko detect file accesses over Samba, Netatalk, and NFS?

Yes, yes, and yes. This allows you to develop software to monitor, regulate, or protect file access on your Samba, Netatalk, or NFS File Server.

Note for Netatalk: In order to work correctly with Dazuko, Netatalk must be compiled using the --with-did=cnid option.

Note for NFS: In order to work correctly with Dazuko, the NFS User Server must be used (not the NFS Kernel Server). The NFS Kernel Server communicates over sockets directly from the kernel, thus bypassing Dazuko.


1.6 I don't know anything about compiling kernels. Can I just download a pre-compiled binary of Dazuko?

One of the greatest advantages of free operating systems is also for many a problem. That is, they can be customized to support exactly the hardware and features you desire thereby maximizing your system performance (and satisfaction). However, since Dazuko must load into the kernel itself, Dazuko must be compiled with exactly the same code that your kernel was compiled with. With so many different kernel configuration possibilities, it is impossible to precompile a binary for each one.

Therefore, the only way you can get a compiled Dazuko is by compiling it yourself. In the future, operating system distributors may offer Dazuko as a pre-compiled binary, which has already been built for their pre-compiled kernel. SuSE Linux is one such system that already provides a pre-compiled Dazuko driver "out-of-the-box". This makes Dazuko much easier for people to use. Hopefully Dazuko can evolve (politically) to the point where this is more common.


1.7 What does Avira GmbH (formerly known as H+BEDV Datentechnik GmbH) have to do with Dazuko?

Avira GmbH is an anti-virus company based in Tettnang, Germany. In order to allow on-access file scanning for the GNU/Linux operating system, they developed Dazuko (called the "AvGuard kernel module" at the time). However, it was felt that releasing the module source code as free software would not only broaden the available user base, but also provide an opportunity to create a common interface for 3rd party file access control. Avira GmbH continues to fund developers to work on the Dazuko project. Although Dazuko is still relatively young, it has become the basis for several products and thus will continue to have development interest from the community.


1.8 Where did the name "Dazuko" come from?

Since Dazuko originated from a german company, it was felt that the name should somehow reflect something german. Dazuko's main function is to provide an interface for "file access control", or in german, "Dateizugriffskontrolle". Alles klar?


1.9 How is "Dazuko" pronounced?



1.1 什麼是Dazuko嗎?

Dazuko目的是是對控制文件在一個系統上的進入允許申請的一個十字架平台設備驅動器。 在安裝司機時,你系統將能基于Dazuko的支援文件進入控制應用。 這工程變得更受歡迎和更多應用選擇給他們文件進入的Dazuko當時需要, 希望這台驅動器將成為一個大多數系統的普通組成部分。


1.2 我使用Dazuko的怎樣嗎?

為了使用Dazuko 你必須首先建造並且插入核心模塊。 這然後給添加一個新設備你系統(/dev/dazuko)。 一旦你有Dazuko 設備,你能營運應用利用Dazuko提供的文件存取控制特徵。

如果你有興趣建造你自己的申請,檢查Dazuko界面說明。 你可能也想要看例子計畫被為工作的參考由Dazuko提供。



1.3 Dazuko 支持什麼作業系統嗎?

Dazuko的最新消息支持Linux 2.2-2.6,Linux/RSBAC 和FreeBSD 4顆.x-6.x 果仁。 不過,支持其他作業系統(例如MacOS X,Solaris,NetBSD,OpenBSD 和Windows)正緩慢地被擴大。 雖然所有這些作業系統有非常不同的控制機構,但是結合Dazuko仍然應該是可能的。


1.4 什麼許可證是在下面的Dazuko嗎?

為了允許Dazuko被在儘可能多的作業系統(專賣和免費)上使用, 並且為了能合併驅動器的界面的全部軟體(專賣和免費),Dazuko使用一張BSD 許可證。 不過,Dazuko設備驅動器有"擴展模件"實現具體平台的功能性。 這些擴展模件將受到他們將跑的作業系統的許可證, 如此對這張許可證也(在編譯時間)迫使完全的設備驅動器。 這是一篇迅速的摘要︰

Dazuko 應用界面(在全部平台上)︰ BSD 許可證
Dazuko設備驅動器(Linux)︰ GPL 許可證
Dazuko設備驅動器(FreeBSD)︰ BSD 許可證


1.5 做Dazuko 識別文件出入口越過Samba,Netatalk 和NFS?

是的,是,和是。 這允許你開發軟體監控,調節,或者保護文件關於你的桑巴舞,Netatalk或者NFS 文件伺服器的進入。

為Netatalk注意到︰ 與Netatalk,Dazuko一起正確為了工作一定被編輯使用 --隨著做= cnid 選擇。

為NFS注意到︰ 為了用Dazuko 正確地工作,NFS 用戶伺服器必須被使用(並非NFS 果仁伺服器)。 NFS 果仁伺服器從果仁直接在插座上方交流,因此為Dazuko設旁路。


1.6 我不知道編輯果仁。 我能剛剛下載預編輯的Dazuko的二進製嗎?

免費作業系統的最大的優勢之一也是為許多問題。 即,他們可能被定製正好支持硬體和特徵你想要因此使你的系統性能(以及滿意)最大化。 不過,因為Dazuko 必須裝進果仁自己,Dazuko 必須被完全相同的代碼編輯你的果仁被編輯用。 隨著可能性構造那么多不同果仁,在precompile 不可能一二進製適合每一個。

因此,你能得到一編輯的Dazuko的唯一的模式透過親自編輯它。 將來,經銷人作業系統提供可能Dazuko當時一預編輯二進製,哪個已經被已經數他們的預編輯果仁那裡建造。 SuSE Linux是一這樣系統以致于"在箱子之外"已經提供一台預編輯的Dazuko 驅動器。 這使Dazuko 非常容易適合人使用。 有希望Dazuko 能在這更普通的地方(在政治上)逐步形成切中要點。


1.7 Avira股份有限公司(作為H+BEDV Datentechnik股份有限公司以前知道)研究的是Dazuko的嗎?

Avira股份有限公司是一家總部設在Tettnang,德國的反病毒的公司。 為了為gnu主題/ Linux作業系統允許關於進入的文件掃描,他們發展Dazuko(在那時叫"AvGuard核心模塊")。 但是, 它感到那鬆開模件源碼,因為免費軟體將不僅擴大可得到的用戶基礎, 而且提供一次機會建立第3個聚會文件存取控制的一個普通界面。 Avira股份有限公司繼續為開發者提供資金著手做Dazuko 工程。 雖然Dazuko仍然相對年輕,但是它已經為幾種產品成為基礎,因此將繼續讓發展從社區使感興趣。


1.8 名字"Dazuko"來自的在那裡嗎?

因為Dazuko起源于一家german 公司,感到名字應該設法反映出某些事情german。 Dazuko的主要功能是提供"文件存取控制"的一個界面,或者在german"Dateizugriffskontrolle"裡。 Alles klar嗎?


1.9 "Dazuko"念怎樣?

' dah-tsu-ko ' 

2007.07.27 又找了一些文獻:
gcc for C program. g++ for C plus program


看無,有空再研究 orz...
(dpkg in Debian, to Fedora is rpm)
節錄 dazuko,安裝方法:

dpkg -i dazuko-source_2.1.1-1_all.deb
sudo apt-get install module-assistant debhelper gcc-3.4
sudo module-assistant prepare
這個程序會自動下載某些你不具備的編譯工具。 http://chccd.com
sudo m-a a-i dazuko

sudo gedit /etc/modprobe.d/dazuko
install dazuko modprobe -r capability;\
modprobe -i dazuko; \
modprobe -i capability
sudo gedit /etc/modules
sudo rmmod capability
sudo modprobe dazuko
sudo modprobe capability



sudo gedit /etc/environment




    ca95 發表在 痞客邦 留言(1) 人氣()