AJAX for partial page reload

src:
http://www.sitepoint.com/quick-tip-xmlhttprequest-and-innerhtml/

notes:
14'3/30 : a way to update partial page. There is a way to use "gif" to reflect the download status

------------

Quick tip: XMLHttpRequest and innerHTML

Published August 5, 2004

XMLHttpRequest is one of modern DHTML’s best kept secrets. If you haven’t encountered it before, it’s a method of making an HTTP call back to the hosting web server without refreshing the whole page – a kind of remote scripting on steroids. Originally a Microsoft extension, it’s been adapted by both the Mozilla browser family and (as of version 1.2) Safari. The Sarissa library discussed previously offers an abstraction layer for the different browsers, or for a more lightweight approach this code from jibbering.com (which makes use of IE’s JScript conditional compilation) works perfectly.

Getting the most out of XMLHttpRequest generally involves using server-side generated XML, which can be retrieved by your JavaScript application, parsed and used in more complex logic. However, for a quick fix the following code will load an HTML fragment from a URL and insert it directly in to a page:

function loadFragmentInToElement(fragment_url, element_id) {
    var element = document.getElementById(element_id);
    element.innerHTML = '<p><em>Loading ...</em></p>';
    xmlhttp.open("GET", fragment_url);
    xmlhttp.onreadystatechange = function() {
        if (xmlhttp.readyState == 4 && xmlhttp.status == 200) {
            element.innerHTML = xmlhttp.responseText;
        }
    }
    xmlhttp.send(null);
}

Call the above function with the URL of the HTML fragment to be inserted and the ID of the element in which it should appear. It relies on the jibbering.com code to set up the xmlhttp variable.

It’s definitely quick and dirty, but it’s also a great quick demonstration of the power of the XMLHttpRequest extension.

CentOS 5 PHP 安裝

src:
http://iammic.pixnet.net/blog/post/6137313-centos-5-php-%E5%AE%89%E8%A3%9D

notes:
14'3/22 : PHP is not installed in advance.



---------------------------

• Apr 12 Mon 2010 11:49

• CentOS 5 PHP 安裝

在安裝 CentOS 過程中，Apache 預設將會安裝，而 PHP 並未於預設安裝，如果需要設

定安裝 Apache、PHP、MySQL 環境，可在稍後自行安裝，或者是在安裝 CentOS 過程

中選取安裝。

在安裝CentOS 過程中選取【立即自訂】點選下一步進行自訂安裝，

或者稍後透過 yum 進行安裝。

使用 yum 安裝 PHP

使用下方指令列出 PHP 相關套件，選擇需要安裝套件進行安裝

#yum list | grep php

執行下列指令進行 PHP 安裝

#yum install php php-mysql php-mbstring php-mcrypt php-gd

重新啟動 Apache

#service httpd restart

安裝完成後，來測試一下 PHP 是否可以順利執行，執行下方指令後點選Ctrl+Z 離開

在瀏覽器輸入 http://你的IP/test.php ，確定 PHP 程式是否正常執行

您可能會有興趣的文章

• 打造Linux下超級安全的LAMP服務器
• mysql莫名奇妙掛掉 又莫名奇妙解決事件
• PHP5 系統環境安裝 Windows XP+PHP+Apache (一)
• 美白+保濕，1瓶就做到！

iammic 發表在 痞客邦 PIXNET 留言(0) 引用(0) 人氣(4943)

E-mail轉寄 轉寄至留言板

src:
https://www.blogger.com/blogger.g?blogID=1480518346917712355#editor/target=post;postID=7727646429850891190

notes:


----------

手機解密- 六個你所不知道的手機隱藏密碼

KisPlay – 2014年3月17日 上午9:51

• 寄給朋友
• 分享130
• Plurk!
• 列印

曾經為大家介紹過透過手機中的密碼數字，可以讓訊號顯示從條碼變成數字。然而其實手機中內建的數字密碼可不只有這樣，快來一同來解開手機中隱藏的秘密數字功能吧！


除了在通話那邊輸入“ *3001#12345#* “可以改變訊號強度顯示設定以外，其實還有六組數字同樣可以在通話鍵盤中按下來啓用隱藏的功能喲！

1 " *#06# “-
在手機撥號鍵中按下 *#06# 會出現手機的 IMEI 號碼。而我們也可以從設定中來找尋到自己的手機中的專屬 IMEI 碼。

2 " *#21# “-
提供使用者查詢手機中的所有來電的啓用狀態，包括語音、簡訊等等。

3 " **21*電話號碼" -
設定來電轉接到指定的電話號碼中。

4 " ##21# “-
解除所有來電轉接設定。

5 " *#5005*7672# “-
查詢簡訊中心的號碼。

6 " *#62# “-
查訊這款裝置在沒有訊號或是關機狀態下的資訊狀況。

沒想到手機中的通話撥號鍵盤除了可以讓我們用來輸入想要撥打的電話以外，竟然還有透過 *、# 與數字的組合喚出這麼多的隱藏功能，除了這六種，大家還有發現隱藏在手機之中的"數字密碼"嗎?

來源出處：點子生活

src:
http://msdn.microsoft.com/en-us/windows/hardware/hh852365.aspx

notes:
14'3/18 : WDK is embedded in Vistual Studio package

----------

WDK and WinDbg downloads

This is the place to get your Windows Driver Kit (WDK, formerly DDK) and WinDbg downloads, including the Windows 7 release of the Debugging Tools for Windows, which works for Windows XP. The debugging tools are included in the WDK, but you can also download them separately here.

The WDK has the tools you need to develop drivers. WDK 8.1 is integrated into Visual Studio Professional 2013 and Visual Studio Ultimate 2013 and gives you most of the tools you need for developing, building, packaging, testing, and debugging drivers.

Not sure which kit to use? The tables in Windows Driver Development can help you make the right choice.

#pragma pack

src:
http://www.cplusplus.com/forum/general/14659/
http://blog.xuite.net/jackie.xie/bluelove/7788211

notes:
14'3/17 :
[1]
- For linux [declared in data structure only ? In one line]
__attribute__ ((packed))

- For Window [declared by range]
#pragma pack...

#pragma pack...


[2] declaration of #pragma
- format-1
#pragma pack(1 )  [begin]
#pragma pack( )  [end]

- format-2 (it's better?)

#pragma pack(push, 1)

#pragma pack(pop)

----------------

guestgulkan (2942)

(Very ) Basically the compiler unless otherwise directed will line up structure members on
2 byte or 4 byte boundaries - this makes it easier and faster for the processor to handle.
So the structure contains secret padding bytes to make this happen.

The pragma pack directive (in MS Compiler) allows you to change this alignment scheme.

Some things (particularly in relation to hardware) do not have the luxury to waste bytes like
this and they send their data in an exact fit.
This means that it is not wise to read data from a hardware device directly into a normal structure.

If you have want to read data that is an exact fit into a structure - you can tell the compiler
to make the structure an exact fit like this (microsoft compiler);

1 2 3 4 5 6 7 8

#pragma pack(push, 1) // exact fit - no padding struct MyStruct { char b; int a; int array[2]; }; #pragma pack(pop) //back to whatever the previous packing mode was

Without the pragma directive, the size of the structure is 16 bytes - with the packing of 1 - the size is 13 bytes

----------------

#pragma pack(1) "是表示什麼意思呢?!

在這裡我先解釋"#pragma"的作用,"#pragma"就像是compiler的功能選擇開關,也就是#pragma是用來設定complier的選項，跟你在complier後加 -Zp -Xk 等等設定是一樣的。使用它其實就如同你在dos下使用compiler時,在命令列輸入那些參數一樣,所達到的功能是一致的,像在 Watcom C/C++ 中 "#pragma off (check_stack)", 代表的是把WC++的stack檢查關閉,當然你也可以從命令列輸入參數做到一樣的功能,不過有點不一樣的,用"#pragma",你可以選擇所需要這麼處理的程式區段,所以比命令列更方便更好用.不過"#pragma"所提供的功能切換在不同的compiler上並不相同,所以要特別注意.

接下來進入主題,到底"#pragma pack(1)"是做什麼的?其實"#pragma pack( )"就是要compiler照我們的意思去做記憶體aligment(對齊)的工作,在Win32下為了提高記憶體存取效率,所以記憶體配置(對齊)的預設值是以DWORD(4BYTES也就是32bits)為單位,因此在配置struct的記憶體空間的時候,往往會造成struct內部的資料在記憶體位址上並不連續,在我們的程式之中,如果不是用指標去存取這些資料,可能還不會出錯,可是如果我們真的用指標去存取的話,由於資料排列不連續,我們可能會讀不到我們想要的值,這還不打緊,如果這個結構是傳址給Win API來取得資料,那就問題大條了,因為API會以為struct內部的記憶體位址是連續的,所以會造成錯誤,像我之前寫"在Win95/98下存取邏輯磁區"那篇文章的範例程式時,就為此吃足苦頭,不但結果不正確,還一直當機,後來才發現是記憶體aligment的問題,為了讓struct內部的記憶體位址是連續的,這時我們就必需要用"#pragma pack(1)"這個命令,來讓compiler把這個struct,以BYTE為單位做記憶體aligment,如此一來struct使用時就不會出錯了.

"#pragma pack()"有幾個值可供設定,如下所述,"#pragma pack(1)"是對齊BYTE,"#pragma pack(2)"是對齊WORD,而"#pragma pack( )"等於"#pragma pack(4)",就是對齊DWORD,另外,還有"#pragma pack(8)",以及"#pragma pack(16)"可以選用,所以我們只要將struct的定義區段,用"#pragma pack(1)"和"#pragma pack( )"包起來,就可以了使struct正確被存取了.以下是個示範aligment的程式:

////本程式在BCB5中順利編譯執行
#include <stdio.h>
#include <conio.h>
#include <windows.h>
int main(int argc, char* argv[])
{

    #pragma pack(4)
    ////記憶體對齊單位用DWORD
    typedef struct _aligment_DWORD{
        char a ;
        WORD test1;
        char b ;
        char c ;
        char d ;
    } aligment_DWORD;
    #pragma pack( )

    #pragma pack(1)
    ////記憶體對齊單位用BYTE
    typedef struct _aligment_BYTE{
        char e ;
        WORD test2 ;
        char f ;
        char g ;
        char h ;
    } aligment_BYTE;
    #pragma pack( )

    aligment_BYTE ali_byte ;
    aligment_DWORD ali_dw ;
    ali_dw.a = 'A' ;
    ali_dw.b = 'B' ;
    ali_dw.c = 'C' ;
    ali_dw.d = 'D' ;
    ali_byte.e = 'E' ;
    ali_byte.f = 'F' ;
    ali_byte.g = 'G' ;
    ali_byte.h = 'H' ;
    LPTSTR pointer ;

    printf("aligment_DWORD struct is %d BYTES \n",sizeof(ali_dw));
    printf("aligment_BYTE struct is %d BYTES\n",sizeof(ali_byte));
    pointer = (LPTSTR)(&ali_byte) ;
  
    //請注意記憶體的位址,和輸出的結果之間的關係
    printf("ali_byte.e is %c \n",*pointer);
    printf("ali_byte.f is %c \n",*(pointer + 3 ));
    printf("ali_byte.g is %c \n",*(pointer + 4 ));
    printf("ali_byte.h is %c \n",*(pointer + 5 ));

    pointer = (LPTSTR)(&ali_dw) ;
    printf("ali_byte.a is %c \n",*pointer);
    printf("ali_byte.b is %c \n",*(pointer + 4 ));
    printf("ali_byte.c is %c \n",*(pointer + 5 ));
    printf("ali_byte.d is %c \n",*(pointer + 6 ));

    getch();
    return 0;
}

    ////輸出結果如下

    aligment_DWORD struct is 8 BYTES
    aligment_BYTE struct is 6 BYTES
    ali_byte.e is E
    ali_byte.f is F
    ali_byte.g is G
    ali_byte.h is H
    ali_byte.a is A
    ali_byte.b is B
    ali_byte.c is C
    ali_byte.d is D

    ////////////////////////////////// 

讓我們來看上面這個程式還有它的輸出結果,程式中的兩個struct內容總共都是 6 BYTES,可是由於aligment設定的不同,一個size是正常的6 BYTES,另一個竟然變成是8 BYTES,為了輸出正確結果,那個aligment設為DWORD的struct,在printf( )中的位址變得很奇怪吧!!

所以如果我們要避免struct在Win32的程式中出錯,以後可別忘了加上"#pragma pack(1)"和"#pragma pack( )" !

#pragma pack(n)是用來讓struct的成員對齊記憶體用的，在32bit系統下基於處理器效率的考量，由於預設的對齊位置是4 bytes，所以所有的struct成員視為 #pragma pack(4)，但有時候我們希望struct裡成員是連績的，尤其是控制硬體相關的io位置，所以會設為#paragma pack(1)，讓struct的成員要用 Byte 來對齊。看以下例子：

struct pci_conf {
        WORD VendorID;
        WORD DeviceID;
        ...
} pci;

如果沒有用#pragma pack(1)，VendorID後會空2 bytes不用，以便對到4 bytes
(假設一開始是對齊的)，然後才配置DeviceID。
可是若沒留意這樣的問題，
(BYTE*) p = &pci;
預期*(p+0x2)是DeviceID就會出問題。
#pragma pack和數據對齊問題
結構數據存放時預設是按4 bytes對齊，考慮以下程序，輸出結果為：sizeof(A)=12

typedef struct _A
{
    int x;
    char z[7];
}A;

void main()
{
    int len = sizeof(A);
    printf("sizeof(A)=%d\n", len);    // len = 12
}


使用 #pragma pack，設置數據按1對齊，此時輸出結果為：sizeof(A)=11
#pragma pack(push)
#pragma pack(1)
typedef struct _A
{
    int x;
    char z[7];
}A;
#pragma pack(pop)

void main()
{
    int len = sizeof(A);
    printf("sizeof(A)=%d\n", len);    // len = 11
}

其中 : 

push 就是在改變為 1 之前先儲存原來的設定。 
pop 當然就是恢復原來的設定了。

__attribute__ ((packed))

src:
http://hi.baidu.com/weipatty/item/b5a9964daab2f1aadf2a9fd4

notes:

----------

__attribute__ ((packed)) 的作用

最近在看我们的代码的时候发现声明类型的时候有 __attribute__ ((packed））的结构体类型声明，不知道是什么意思，查了下知道是如下含义：

1. __attribute__ ((packed)) 的作用就是告诉编译器取消结构在编译过程中的优化对齐,按照实际占用字节数进行对齐，是GCC特有的语法。这个功能是跟操作系统没关系，跟编译器有关，gcc编译器不是紧凑模式的，我在windows下，用vc的编译器也不是紧凑的，用tc的编译器就是紧凑的。例如：

在TC下：struct my{ char ch; int a;} sizeof(int)=2;sizeof(my)=3;（紧凑模式）

在GCC下：struct my{ char ch; int a;} sizeof(int)=4;sizeof(my)=8;（非紧凑模式）

在GCC下：struct my{ char ch; int a;}__attrubte__ ((packed)) sizeof(int)=4;sizeof(my)=5

2. __attribute__关键字主要是用来在函数或数据声明中设置其属性。给函数赋给属性的主要目的在于让编译器进行优化。函数声明中的__attribute__((noreturn))，就是告诉编译器这个函数不会返回给调用者，以便编译器在优化时去掉不必要的函数返回代码。

GNU C的一大特色就是__attribute__机制。__attribute__可以设置函数属性（Function Attribute）、变量属性（Variable Attribute）和类型属性（Type Attribute）。

__attribute__书写特征是：__attribute__前后都有两个下划线，并且后面会紧跟一对括弧，括弧里面是相应的__attribute__参数。

__attribute__语法格式为：

__attribute__ ((attribute-list))

其位置约束：放于声明的尾部“；”之前。

函数属性（Function Attribute）：函数属性可以帮助开发者把一些特性添加到函数声明中，从而可以使编译器在错误检查方面的功能更强大。__attribute__机制也很容易同非GNU应用程序做到兼容之功效。

GNU CC需要使用 –Wall编译器来击活该功能，这是控制警告信息的一个很好的方式。

packed属性：使用该属性可以使得变量或者结构体成员使用最小的对齐方式，即对变量是一字节对齐，对域（field）是位对齐。

http://blogguan.blog.sohu.com/109697765.html

/* __attribute__ ((packed)) 的位置约束是放于声明的尾部“；”之前 */
struct str_struct{
        __u8    a;
        __u8    b;
        __u8    c;
        __u16   d;
} __attribute__ ((packed));

/* 当用到typedef时，要特别注意__attribute__ ((packed))放置的位置，相当于：
   * typedef struct str_stuct str;
   * 而struct str_struct 就是上面的那个结构。
*/
typedef struct {
        __u8    a;
        __u8    b;
        __u8    c;
        __u16   d;
} __attribute__ ((packed)) str;

/* 在下面这个typedef结构中，__attribute__ ((packed))放在结构名str_temp之后，其作用是被忽略的，注意与结构str的区别。*/
typedef struct {
        __u8    a;
        __u8    b;
        __u8    c;
        __u16   d;
}str_temp __attribute__ ((packed));

http://rmax2005.spaces.live.com/blog/cns!4C2190641D9E68A!311.entry

CentOS 安裝 PPPoE 網路連線套件 rp-pppoe

src:
http://shaocian.blogspot.tw/2012/07/centos-pppoe-rp-pppoe.html

related:
http://linux.vbird.org/linux_server/redhat6.1/linux_21internet.php

notes:
14'3/17 part2:

0. download PPPoE
yum install rp-pppoe

1. erase NetworkManager
yum erase NetworkManager

2. create ifcfg-ethx in /etc/sysconfig/network-scripts/ifcfg-eth0
Ex:
DEVICE="eth0"
HWADDR="12:34:56:78:90:C1"
ONBOOT="yes"
BOOTPROTO=dhcp


3. enable network
chkconfig network on
chkconfig network --list

4. restart network
/etc/init.d/network restart

5. setup PPPoE
pppoe-setup

6. PPPoE oeration
# /sbin/ifup ppp0 --> connect
# /sbin/ifdown ppp0 --> disconnect
# /sbin/pppoe-status --> status check

7. need install other PPPoE module?
# mount /dev/cdrom /mnt
# cd /mnt/Packages
# rpm -ivh rp-pppoe* ppp* libpcap*


14'3/17 :
[1] the phy for PPPoE could be selected.
[2] Web service, it's necessary to execute a program to update IP to DDNS server
[3] NAS, do need to setup Virtual Server itself
[4] NetworkManager vs rp-pppoe. It looks like rp-pppoe is more user friendly but need to check whether disable NetworkManager will give rise to other problem


-------------

CentOS 安裝 PPPoE 網路連線套件 rp-pppoe

由於 NetworkManager 的問題實在很多，也遇到有時候連線失敗的問題，用來一般使用可能還好，作為伺服器的用途的話，穩定性實在令人擔憂，因此還是決定把NetworkManager移除掉，改安裝最原始的文字介面的 rp-pppoe 吧。

為了避免 NetworkManager 和 rp-pppoe 發生衝突，自己是只留一套運作，但是在移除NetworkManager 之前，記得先把 rp-pppoe 安裝好，否則沒網路當然就沒辦法下載套件了。

可以透過yum搜索功能，尋找 pppoe 的相關套件，可以找到 rp-pppoe

# yum search pppoe

# yum install rp-pppoe





安裝好後，先把 NetworkManager 移除掉

# yum erase NetworkManager

移除後開始設定 rp-pppoe，接下來會出現對話式的設定文字介面，照著輸入即可完成設定

# pppoe-setup
------------------------------------------------------------------------------------------------------------
Welcome to the PPPoE client setup.  First, I will run some checks on
your system to make sure the PPPoE client is installed properly...


LOGIN NAME

Enter your Login Name (default root): xxxxxxxx@ip.hinet.net 
這裡輸入您的連線帳號，若是中華電信的用戶，則會出現 @ 及後面那一段
 ip.hinet.net 或者是 hinet.net（前者是取得固定IP，後者是取得浮動IP）

INTERFACE

Enter the Ethernet interface connected to the PPPoE modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethX, where 'X' is a number.    
(default eth0):eth0
這裡輸入連接到數據機的網路卡介面，因為筆者只有一張網卡，所以預設就行了

Do you want the link to come up on demand, or stay up continuously?
If you want it to come up on demand, enter the idle time in seconds
after which the link should be dropped.  If you want the link to
stay up permanently, enter 'no' (two letters, lower-case.)    
NOTE: Demand-activated links do not interact well with dynamic IP
addresses.  You may have some problems with demand-activated links.
Enter the demand value (default no):no
選擇no保持連線

DNS

Please enter the IP address of your ISP's primary DNS server.
If your ISP claims that 'the server will provide dynamic DNS addresses',
enter 'server' (all lower-case) here.                              
If you just press enter, I will assume you know what you are        
doing and not modify your DNS setup.                                
Enter the DNS information here: 168.95.1.1 請填寫根據您網路廠商提供的 DNS 伺服器位址
Please enter the IP address of your ISP's secondary DNS server.    
If you just press enter, I will assume there is only one DNS server.
Enter the secondary DNS server address here: 168.95.192.2 一般來說會有兩組不同的 DNS

PASSWORD

Please enter your Password: 輸入連線的密碼（在這裡輸入過程不會出現星號）
Please re-enter your Password: 重覆再輸入一次

USERCTRL

Please enter 'yes' (three letters, lower-case.) if you want to allow
normal user to start or stop DSL connection (default yes): no 不要讓一般使用者去控制連線

FIREWALLING

Please choose the firewall rules to use.  Note that these rules are
very basic.  You are strongly encouraged to use a more sophisticated
firewall setup; however, these will provide basic security.  If you
are running any servers on your machine, you must choose 'NONE' and
set up firewalling yourself.  Otherwise, the firewall rules will deny
access to all standard servers like Web, e-mail, ftp, etc.  If you
are using SSH, the rules will block outgoing SSH connections which
allocate a privileged source port.                              

The firewall choices are:
0 - NONE: This script will not set any firewall rules.  You are responsible
          for ensuring the security of your machine.  You are STRONGLY
          recommended to use some kind of firewall rules.              
1 - STANDALONE: Appropriate for a basic stand-alone web-surfing workstation
2 - MASQUERADE: Appropriate for a machine acting as an Internet gateway
                for a LAN
Choose a type of firewall (0-2): 0 暫時先選0，防火牆的部分由我們手動設定

Start this connection at boot time

Do you want to start this connection at boot time?
Please enter no or yes (default no):yes 開機時自動連線

** Summary of what you entered **

Ethernet Interface: eth0
User name:          xxxxxxxx@ip.hinet.net
Activate-on-demand: No
Primary DNS:        168.95.1.1
Secondary DNS:      168.95.192.2
Firewalling:        NONE
User Control:       no
Accept these settings and adjust configuration files (y/n)? y 核對資料無誤按 y
Adjusting /etc/sysconfig/network-scripts/ifcfg-ppp0
Adjusting /etc/resolv.conf
  (But first backing it up to /etc/resolv.conf.bak)
Adjusting /etc/ppp/chap-secrets and /etc/ppp/pap-secrets
  (But first backing it up to /etc/ppp/chap-secrets.bak)
  (But first backing it up to /etc/ppp/pap-secrets.bak)


Congratulations, it should be all set up!

Type '/sbin/ifup ppp0' to bring up your xDSL link and '/sbin/ifdown ppp0'
to bring it down.
Type '/sbin/pppoe-status /etc/sysconfig/network-scripts/ifcfg-ppp0'
to see the link status.

------------------------------------------------------------------------------------------------------------

這樣就完成了設定！

# /sbin/ifup ppp0 連線
# /sbin/ifdown ppp0 斷線
# /sbin/pppoe-status 檢查目前狀態

如果是以 Minimal 的方式安裝的 CentOS，安裝好後沒有視窗介面，當然也沒有 NetworkManager，只能先利用光碟內或者上網自行下載套件後用隨身碟複製過去安裝了

這裡使用CentOS光碟的範例來說明：

# mount /dev/cdrom /mnt
# cd /mnt/Packages
# rpm -ivh rp-pppoe* ppp* libpcap*

由於rp-pppoe缺少一些相依套件，要順便一起安裝ppp及libpcap

安裝成功後一樣依照上面的設定跑一遍即可，也可以先測試看看重開機是否會自動連線。

src:
http://clonezilla.org/livepxe.php

Using Clonezilla with FreeNAS or Network Share to Backup a Hard Disk
http://mylinuxramblings.wordpress.com/2010/08/19/using-clonezilla-with-freenas-or-network-share-to-backup-a-hard-disk/



notes:

--------

Clonezilla The Free and Open Source Software for Disk Imaging and Cloning

About

News

Screenshots

Live CD/USB

Server Edition

Downloads

CD/USB key vendors

DRBL-winroll

Related LiveCD

Testimonials

Lecture Materials

Related Articles

Partners

FAQ/Q&A

Forum

Mailing Lists

Developers

Contributors

Related links

Local communities

Clonezilla Live - A small bootable GNU/Linux distribution for imaging and cloning

[About] [How to install] [How to use] [Step by step] [Accounts] [Advanced modes]

---

1. About Clonezilla Live

Clonezilla Live is a small bootable GNU/Linux distribution for x86/amd64 (x86-64) based computers. Clonezilla SE (Server Edition) has been developed from 2004, and it is used to deploy many computers simultaneously. It is an extremely useful tool, however, it does have several limitations. In order to use it, you must first prepare a DRBL server AND the machine to be deployed must boot from a network (e.g. PXE/iPXE). To address these limitations, we have combined Debian Live with Clonezilla as "Clonezilla Live," a software that can be used to easily image and clone individual machines. The primary benefit of Clonezilla Live is that it eliminates the need to set up a DRBL server ahead of time and the need for the computer being deployed to boot from a network. Clonezilla Live can be used to image or clone individual computers using a CD/DVD or USB flash drive. Though the image size is limited by the boot media's storage capacity, this problem can be eliminated by using a network filesystem such as sshfs or samba.

2. How to install Clonezilla Live ?

To install Clonezilla live, the basic steps are to download pre-build Clonezilla Live then put it in a boot media (CD, USB flash drive or USB hard drive). Two types of files are available, iso and zip. The former one is for CD, the latter is for USB flash drive. Besides, you can put Clonezilla live on hard drive or PXE server, too.

• For CD/DVD:
  
  Download an ISO file for CD/DVD. Then you can burn the iso file to a CD/DVD with any burnning program, such K3b on GNU/Linux orInfraRecorder on MS Windows, and remeber to choose "Burn Image" to burn the ISO file on the CD. The CD can then be used to boot the machine you want to image or clone.
• For USB flash drive or USB hard drive:
  
  To put Clonezilla live on a USB flash drive or USB hard drive, check this doc.
• For hard drive:
  
  To put Clonezilla live on a harddrive with OS installed already, check this doc.
• For PXE server:
  
  To put Clonezilla live on a PXE server and boot your client via PXE, check this doc.

If you are interested in creating the Clonezilla live iso or zip file from scratch, check this doc. //New for creating Clonezilla live 2.x!//.

3. How to use Clonezilla live ?

Please refer to this doc for more details.

4. Accounts

In Clonezilla live, two accounts are available: (1) account "user" with sudo privilege, password is "live", (2) administration account "root", no password. Therefore you can not login as root, the only way to get root privilege is to login as user, and run "sudo -i" or "sudo su -" to become root.
For better security, it is recommended to change the passwords of user and root by command "passwd" before you allow remote access. When Clonezilla live boots, the ssh service is NOT automatically started, and the setting in /etc/hosts.deny does NOT block any connection. If you want to remotely ssh login into your Clonezilla live, you have to start ssh service by "service ssh start".

5. Advanced modes

Some advanced modes are available:

• Create your own recovery CD or USB flash drive.
• Use your own script and run it on clonezilla live.
• Use boot parameters to pre-set some selections
• The reserved image and device names for the command ocs-sr

  

src:
http://docs.oracle.com/javase/1.5.0/docs/guide/jni/spec/jniTOC.html
https://drive.google.com/uc?export=download&id=0B543p5wfySTQaG0tZXRhNEJjRVU [mypdf]

notes:

---------------

Java Native Interface Specification—Contents

---

Contents | Previous | Next

1. Introduction

Java Native Interface OverviewBackground

JDK 1.0 Native Method InterfaceJava Runtime Interface
Raw Native Interface and Java/COM Interface

ObjectivesJava Native Interface Approach
Programming to the JNIChanges in JDK 1.1.2

2. Design Overview

JNI Interface Functions and PointersLoading and Linking Native Methods

Resolving Native Method NamesNative Method Arguments

Referencing Java Objects

Global and Local ReferencesImplementing Local References

Accessing Java Objects

Accessing Primitive ArraysAccessing Fields and Methods

Reporting Programming ErrorsJava Exceptions

Exceptions and Error CodesAsynchronous ExceptionsException Handling

3. JNI Types and Data Structures

Primitive Types
Reference Types
Field and Method IDs
The Value Type
Type Signatures
Modified UTF-8 Strings

4. JNI Functions

Interface Function Table
Version Information

GetVersion

Class Operations

DefineClassFindClassGetSuperclassIsAssignableFrom

Exceptions

ThrowThrowNew
ExceptionOccurredExceptionDescribe
ExceptionClearFatalErrorExceptionCheck

Global and Local References

NewGlobalRefDeleteGlobalRef
DeleteLocalRefEnsureLocalCapacityPushLocalFramePopLocalFrameNewLocalRef

Weak Global References

NewWeakGlobalRefDeleteWeakGlobalRef

Object Operations

AllocObjectNewObject, NewObjectA, and NewObjectV
GetObjectClassIsInstanceOf
IsSameObject

Accessing Fields of Objects

GetFieldIDGet<type>Field Routines
Set<type>Field Routines

Calling Instance Methods

GetMethodIDCall<type>Method Routines, Call<type>MethodA Routines, and Call<type>MethodV Routines
CallNonvirtual<type>Method Routines, CallNonvirtual<type>MethodA Routines, and CallNonvirtual<type>MethodV Routines

Accessing Static Fields

GetStaticFieldIDGetStatic<type>Field Routines
SetStatic<type>Field Routines

Calling Static Methods

GetStaticMethodIDCallStatic<type>Method Routines, CallStatic<type>MethodA Routines, and CallStatic<type>MethodV Routines

String Operations

NewStringGetStringLength
GetStringCharsReleaseStringChars
NewStringUTFGetStringUTFLength
GetStringUTFCharsReleaseStringUTFCharsGetStringRegionGetStringUTFRegionGetStringCriticalRelease StringCritical

Array Operations

GetArrayLengthNewObjectArray
GetObjectArrayElementSetObjectArrayElement
New<PrimitiveType>Array RoutinesGet<PrimitiveType>ArrayElements Routines
Release<PrimitiveType>ArrayElements RoutinesGet<PrimitiveType>ArrayRegion Routines
Set<PrimitiveType>ArrayRegion RoutinesGetPrimitiveArrayCriticalReleasePrimitiveArrayCritical

Registering Native Methods

RegisterNativesUnregisterNatives

Monitor Operations

MonitorEnterMonitorExit

NIO Support

NewDirectByteBufferGetDirectBufferAddressGetDirectBufferCapacity

Reflection Support

FromReflectedMethodFromReflectedFieldToReflectedMethodToReflectedField

Java VM Interface

GetJavaVM

5. The Invocation API

Overview

Creating the VMAttaching to the VM
Unloading the VM

Library and Version Management

JNI_OnLoadJNI_OnUnload

Invocation API Functions

JNI_GetDefaultJavaVMInitArgsJNI_GetCreatedJavaVMs
JNI_CreateJavaVMDestroyJavaVM
AttachCurrentThreadAttachCurrentThreadAsDaemonDetachCurrentThreadGetEnv

---

Contents | Previous | Next

Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved.