Debian 進階使用者 ▶ 這份教學指南針對重要功能進行介紹, 但也許會有疏漏之處 ▶ 所以你需要閱讀更多文件 ▶ 文件大部份的內容也適用於 Debian 衍生的 Linux發行版 ▶ 其中包含 Ubuntu Debian 套件打包教學指南 2 / 90 大綱 1 介紹 2 製作原始碼套件 3 構建並測試套件 4 實際演練 1: 修改 grep 套件 5 進階打包主題 6 維護 Debian 這份教學指南: 以 Debian 風格來製作 Debian 套件 Debian 套件打包教學指南 7 / 90 開發必需之工具 ▶ 一台能以 root 權限存取的 Debian (or Ubuntu) 系統 ▶ 一些必需套件: ▶ build-essential: 和 Debian 套件有相依性並假定已安裝在開發者的機 器上 (不需在套件中的 control 欄位特別指定 Build-Depends: Debian 修訂版 上游版本 ▶ 可以手動編輯或者透過 dch ▶ 為一個新的發行版創建一條歷程記錄dch -i ▶ 具備特殊格式並自動將 Debian 或 Ubuntu 的缺陷結案 Debian: Closes: #595268; Ubuntu: LP: #616929 ▶ 安裝在 /usr/share/doc/package /changelog.Debian.gz mpich2 (1.2.1

等 Java EE 規 格，Struts/Spring/Hibernate 等 Open Source Framework，與 JBoss AS、 GlassFish 等 Application Server。 自認為會的技術不多，但是學不會的 也不多，最擅長把老闆交代的工作， 以及找不到老師教的技術，想辦法變 成自己的專長。 目前負責 Java 與 .NET 雲端運算相 關技術的推廣，主要包括 Hbase, Pig, Avro, etc.) and the fully operational operating systems with its distributions (RedHat, Ubuntu, Fedora, Debian etc.) 所以，市面上就有了一堆大同小異的 Hadoop Distribution： Cloudera 有 Cloudera Distribution for

called Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(@async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) Task their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

called Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(@async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) Task their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

called Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(@async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) Task their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

called Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(@async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) Task their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

called Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(@async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) Task their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(Threads.@spawn begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(Threads.@spawn begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

Sockets. Let's first create a simple server: julia> using Sockets julia> errormonitor(Threads.@spawn begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end) their usage is somewhat simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that