顯示文章

這裡允許您檢視這個會員的所有文章。請注意, 您只能看見您有權限閱讀的文章。


主題 - 小圭

頁: [1]
1
Windows 討論版 / 網站首頁顯示 index of
« 於: 2013-03-07 15:36 »
和各位求救一下,這個網站首頁變成這樣,好像是目錄指向錯誤?
能否給小弟一個方向來除錯,謝謝


2
Network 討論版 / 不同網段互連辦法?
« 於: 2012-12-26 12:59 »


太久沒碰網路一直卡住,請問各位
因公司印表機只能透過無線網路取得ip(192.168.0.x)
使用網路線因不同網段就找不到印表機(192.168.1.x)
請問有什麼方法能解決?

3
MIS 討論區 / 相關設備費用問題~
« 於: 2010-10-14 16:45 »
好久沒來這了 離開資訊業四五年跑去做業務 這陣重回本行當mis 一切都好陌生

公司卻只有我一個工程師 也沒人和我交接 實在是好惶恐

這是我們公司網站 http://www.bank1688.com.tw/

公司網站是請人代管 今天早上發生機房過熱導至當機網站無法連入

老闆對此事很不開心因老闆有花錢在做關鍵字廣告

故問我說如果把主機拉回來 買個不斷電系統(咦?當機和不斷電有什關係)

要我把移機會用的相關設備估價給他 他要去和代管網站公司談

我想了一下 應需一條專線、UPS、A主機掛掉會由B主機繼續服務的機制(是cluster嗎)

是否請有經驗的版大們就所需設備費用提供給我參考 感恩

(PS:公司目前沒屬於自己DOMAIN的郵件伺服)

4
如果此篇po在此版不適合的話,麻煩幫我移至適當位置

小弟原本是網管工程師,為追求高薪和個性上的關係,想轉換當業務

朋友知道這消息後,一直要拉我去做保險

他說 資訊界收入無法和保險業相比

實情是這樣的嗎??煩請有經驗的大大幫我解答

我想說憑藉著原本資訊專業的技能轉戰業務,就不用再重頭學@@

5
Embedded 討論版 / Glibc_vs_uClibc_Differences
« 於: 2005-05-15 23:53 »
開版第一砲~
先來分享自己收集的其中一篇文章

 uClibc and Glibc are not the same -- there are a number of differences which may or may not cause you problems.  This document attempts to list these differences and, when completed, will contain a full list of all relevant differences.


1) uClibc is smaller than glibc.  We attempt to maintain a glibc compatible
interface, allowing applications that compile with glibc to easily compile with uClibc.  However, we do not include _everything_ that glibc includes, and therefore some applications may not compile.  If this happens to you, please report the failure to the uclibc mailing list, with detailed error messages.

2) uClibc is much more configurable then glibc.  This means that a developer may have compiled uClibc in such a way that significant amounts of functionality have been omitted.  

3) uClibc does not even attempt to ensure binary compatibility across releases.When a new version of uClibc is released, you may or may not need to recompile all your binaries.

4) malloc(0) in glibc returns a valid pointer to something(!?!?) while in
uClibc calling malloc(0) returns a NULL.  The behavior of malloc(0) is listed as implementation-defined by SuSv3, so both libraries are equally correct.
This difference also applies to realloc(NULL, 0).  I personally feel glibc's
behavior is not particularly safe.  To enable glibc behavior, one has to
explicitly enable the MALLOC_GLIBC_COMPAT option.

4.1) glibc's malloc() implementation has behavior that is tunable via the
MALLOC_CHECK_ environment variable.  This is primarily used to provide extra malloc debugging features.  These extended malloc debugging features are not available within uClibc.  There are many good malloc debugging libraries available for Linux (dmalloc, electric fence, valgrind, etc) that work much better than the glibc extended malloc debugging.  So our omitting this functionality from uClibc is not a great loss.

5) uClibc does not provide a database library (libdb).

6) uClibc does not support NSS (/lib/libnss_*), which allows glibc to easily
support various methods of authentication and DNS resolution.  uClibc only supports flat password files and shadow password files for storing
authentication information.  If you need something more complex than this,you can compile and install pam.

7) uClibc's libresolv is only a stub.  Some, but not all of the functionality
provided by glibc's libresolv is provided internal to uClibc.  Other functions
are not at all implemented.

8) libnsl provides support for Network Information Service (NIS) which was originally called "Yellow Pages" or "YP", which is an extension of RPC invented by Sun to share Unix password files over the network.  I personally think NIS is an evil abomination and should be avoided.  These days, using ldap is much more effective mechanism for doing the same thing.  uClibc provides a stub libnsl, but has no actual support for Network Information Service (NIS). We therefore, also do not provide any of the headers files provided by glibc under /usr/include/rpcsvc.   I am open to implementing ldap based password authentication, but I do not personally intend to implement it (since I have no use for it).

9) uClibc's locale support is not 100% complete yet.  We are working on it.

10) uClibc's math library only supports long double as inlines, and even
then the long double support is quite limited.

11) uClibc's libcrypt does not support the reentrant crypt_r, setkey_r and
encrypt_r, since these are not required by SuSv3.

12) uClibc directly uses the kernel types to define most opaque data types.

13) uClibc directly uses the linux kernel's arch specific 'stuct stat'.

<other things as we notice them>



******************************  Manuel's Notes  ******************************

Some general comments...

The intended target for all my uClibc code is ANSI/ISO C99 and SUSv3
compliance.  While some glibc extensions are present, many will eventually
be configurable.  Also, even when present, the glibc-like extensions may
differ slightly or be more restrictive than the native glibc counterparts.
They are primarily meant to be porting _aides_ and not necessarily
drop-in replacements.

Now for some details...

time functions
--------------
1) Leap seconds are not supported.
2) /etc/timezone and the whole zoneinfo directory tree are not supported.
   To set the timezone, set the TZ environment variable as specified in
   http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html
   or you may also create an /etc/TZ file of a single line, ending with a
   newline, containing the TZ setting.  For example
   echo CST6CDT > /etc/TZ
3) Currently, locale specific eras and alternate digits are not supported.
   They are on my TODO list.

wide char support
-----------------
1) The only multibyte encoding currently supported is UTF-8.  The various
   ISO-8859-* encodings are (optionally) supported.  The internal
   representation of wchar's is assumed to be 31 bit unicode values in
   native endian representation.  Also, the underlying char encoding is
   assumed to match ASCII in the range 0-0x7f.
2) In the next iteration of locale support, I plan to add support for
   (at least some) other multibyte encodings.

locale support
--------------
1) The target for support is SUSv3 locale functionality.  While nl_langinfo
   has been extended, similar to glibc, it only returns values for related
   locale entries.
2) Currently, all SUSv3 libc locale functionality should be implemented
   except for wcsftime and collating item support in regex.

stdio
-----
1) Conversion of large magnitude floating-point values by printf suffers a loss
   of precision due to the algorithm used.
2) uClibc's printf is much stricter than glibcs, especially regarding positional
   args.  The entire format string is parsed first and an error is returned if
   a problem is detected.  In locales other than C, the format string is checked
   to be a valid multibyte sequence as well.  Also, currently at most 10 positional
   args are allowed (although this is configurable).
3) BUFSIZ is configurable, but no attempt is made at automatic tuning of internal
   buffer sizes for stdio streams.  In fact, the stdio code in general sacrifices
   sophistication/performace for minimal size.
4) uClibc allows glibc-like custom printf functions.  However, while not
   currently checked, the specifier must be <= 0x7f.
5) uClibc allows glibc-like custom streams.  However, no in-buffer seeking is
   done.
6) The functions fcloseall() and __fpending() can behave differently than their
   glibc counterparts.
7) uClibc's setvbuf is more restrictive about when it can be called than glibc's
   is.  The standards specify that setvbuf must occur before any other operations
   take place on the stream.
8) Right now, %m is not handled properly by printf when the format uses positional
   args.
9) The FILEs created by glibc's fmemopen(), open_memstream(), and fopencookie()
   are not capable of wide orientation.  The corresponding uClibc routines do
   not have this limitation.
10) For scanf, the C99 standard states "The fscanf function returns the value of
    the macro EOF if an input failure occurs before any conversion."  But glibc's
    scanf does not respect conversions for which assignment was surpressed, even
    though the standard states that the value is converted but not stored.

glibc bugs that Ulrich Drepper has refused to acknowledge or comment on
  ( http://sources.redhat.com/ml/libc-alpha/2003-09/ )
-----------------------------------------------------------------------
1) The C99 standard says that for printf, a %s conversion makes no special
   provisions for multibyte characters.  SUSv3 is even more clear, stating
   that bytes are written and a specified precision is in bytes.  Yet glibc
   treats the arg as a multibyte string when a precision is specified and
   not otherwise.
2) Both C99 and C89 state that the %c conversion for scanf reads the exact
   number of bytes specified by the optional field width (or 1 if not specified).
   uClibc complies with the standard.  There is an argument that perhaps the
   specified width should be treated as an upper bound, based on some historical
   use.  However, such behavior should be mentioned in the Conformance document.
3) glibc's scanf is broken regarding some numeric patterns.  Some invalid
   strings are accepted as valid ("0x.p", "1e", digit grouped strings).
   In spite of my posting examples clearly illustrating the bugs, they remain
   unacknowledged by the glibc developers.
4) glibc's scanf seems to require a 'p' exponent for hexadecimal float strings.
   According to the standard, this is optional.
5) C99 requires that once an EOF is encountered, the stream should be treated
   as if at end-of-file even if more data becomes available.  Further reading
   can be attempted by clearing the EOF flag though, via clearerr() or a file
   positioning function.  For details concerning the original change, see
   Defect Report #141.  glibc is currently non-compliant, and the developers
   did not comment when I asked for their official position on this issue.
6) glibc's collation routines and/or localedef are broken regarding implicit
   and explicit UNDEFINED rules.

6
雜七雜八 / 台南在地朋友請幫個忙
« 於: 2005-04-16 17:16 »
我一個台南朋友的老闆買了一台點唱機卡拉OK

需要格式一顆160G的HD為EXT3 另建名稱為95~99的五個資料夾

好像是要用來擴充歌曲用

因小弟人在屏東 故麻煩在地朋友幫個忙 我朋友會直接拿硬碟給你處理^^

委托人:蔡先生
手機:0960127616

如可幫忙請直接聯絡委托人~或是留個言 謝謝

7
鳥哥臨時公佈欄 / 東森cable又連不上
« 於: 2004-10-05 13:15 »
下午1:15..
有誰和我一樣用 東森的 ...

機車 又連不上 凸

8
鳥哥臨時公佈欄 / [問題]鳥站過中秋了嗎?
« 於: 2004-09-28 07:37 »
幫我連一下鳥站測試看看..

現在早上7:35..

使用東森cable 現在連線討論區 好慢.......好慢

9
雜七雜八 / [新聞]中華vs義大利 4:5 輸了
« 於: 2004-08-20 19:04 »
比賽一結束
各大棒球討論區砲聲連連...
全部球連焦點都在攻擊徐總
==========================
唉 該怎麼說呢?
不管如何 還不是完全沒希望
明天對日本 中華......................




加油(心需=.=")

10
課後溫習+認證考試 / [問題]>> append ??
« 於: 2004-08-06 05:12 »
在做 LX02 Unit 11 後面習題 NO. 22 Hints 有幾行command 如下:

$ ls -lR / >big 2>&1
$ ls -lR / >>big 2>>&1

題意是要把 big檔變大 所以利用 append 功能
但第二行顯示如下:

bash: syntax error near unexpected token '&'
看來問題出在 2>>&1 了...
看來 STDERR 沒領悟"道"的真理....於是改成

$ ls -lR / >>big 2>&1

之後卻實可以APPEND了....^^
另外...做個test

$ ls XXX 2>>big (XXX為不存在檔案)
STDERR是可以append的...

一點小小的發現^^"不知是不是課本印錯了
不知同學是不是也有相同問題??
來企睏丫....
ps:機車咧..怎麼從linux複製command丫...
     要打個錯誤訊息 kvm切了七,八次..>"<

11
那位同學可以和我說一下...
老師說完回到家就忘了 :o

完蛋了...記憶曲線

12
$ cat animals
dog.2
cat.4
penguin.10

$ sort +0.1 animals
cat.4
penguin.10
dog.2

$ sort -t. -n +1 animals
dog.2
cat.4
penguin.10

在第二個例子裡..老師說+0.1是指預設欄位
也就是第1欄位第1個字元做sort....
我try了老半天 感覺好像是以第二個字元做sort...???

最後一個例子以"."做分隔符號 做數字sort..
實在是不太了解2 4 10 是指第2欄位還是第1欄位...
和老師你check一下^^" 好像有點出入...

13
鳥哥臨時公佈欄 / 零晨3:40分....
« 於: 2004-06-26 03:41 »
正在和梁兄在鳥哥討論區回覆文章..
結果突然連不進去 =.=
梁老大...
你也一樣嗎? :o

14
這幾天...姨丈跑來問我
家裡頭一台電腦三個小孩搶著要玩
問我有沒有什麼辦法可以限制一個小孩玩二個小時
時間到就關機
有什麼軟體還是用什麼方案能解決呢?
不要和我說買三台電腦給他們用哩 @@

頁: [1]