close
Warning:
Can't synchronize with repository "(default)" (Unsupported version control system "svn": /usr/lib/python2.7/dist-packages/libsvn/_repos.so: failed to map segment from shared object: Cannot allocate memory). Look in the Trac log for more information.
- Timestamp:
-
May 7, 2009, 2:42:26 PM (17 years ago)
- Author:
-
jazz
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v7
|
v8
|
|
| 20 | 20 | * [http://dbus.freedesktop.org/doc/dbus-tutorial.html D-Bus Tutorial] |
| 21 | 21 | * [[Image(http://dbus.freedesktop.org/doc/diagram.png, width=400)]] |
| | 22 | |
| | 23 | == Embedded == |
| | 24 | |
| | 25 | * 昨天就看到 Debian Developer 寫說要改用 [http://www.eglibc.org/ Embedded GLIBC (EGLIBC)] 來取代現行的 glibc。大概看了一下 FAQ 跟 maintainer 都是來自嵌入式的重量級大廠(Ex.Montavista, Wind River, etc)。大家第一個疑惑一定是 EGLIBC 跟 uClibc 的差異,嚴格講起來 EGLIBC 的目的是為了維護針對嵌入式裝置,特別是 PowerPC 與 MIPS 架構的 C 函式庫進行維護,因為官方 glibc 只希望維護 x86 架構的部分。Debian 向來以支援多種 CPU 架構聞名,更是做 Embedded 移植的最佳選擇( NAS / Wireless AP 改機者的最愛 ),為了後續在產生跨 CPU 架構的套件維護上,改採 EGLIBC 勢必會有其優勢。官方網站提到了幾點 EGLIBC 與 uClibc 的重點差異: |
| | 26 | * '''Binary Compatible''' : uClibc is designed to be source compatible with GLIBC, but it is not binary compatible. - 意思就是縱使 Debian 全面改採 ELIBC 也不需要全部改用 ELIBC 重編跟 C 相依的套件,這就是 Binary Compatible。 |
| | 27 | * '''MMU Support''' - uClibc supports uClinux, whereas EGLIBC will likely only work on GNU/Linux systems with an MMU. - uClibc/uClinux 的特點是可以移植到 Non-MMU 的 CPU 架構,而 EGLIBC 則針對具備 MMU 的 CPU 架構。 |
| | 28 | * '''Development Status''' - uClibc is available today, and is already shipping on a large number of systems. EGLIBC is a new project. - uClibc 已經很成熟了,也已經移植到非常多嵌入式裝置;而 EGLIBC 才剛開始,所以穩定度上可能還有一些缺陷。 |
| 22 | 29 | |
| 23 | 30 | == Networking == |