顯示文章

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


文章 - 小圭

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


2
Network 討論版 / Re: 不同網段互連辦法?
« 於: 2012-12-26 22:09 »
謝謝2位前輩回答..
8年前在高雄上netman的LPI課程
6年前離開mis工作職位後從此就沒再上論壇po文
6年後沒想到我又回來了 ;D


3
Network 討論版 / Re: 不同網段互連辦法?
« 於: 2012-12-26 13:29 »
1. 用一台電腦看要新增一個 .0.x 的虛擬 IP 還是真實網卡
2. 新增印表機
3. 分享印表機
4. .1.x 的電腦直接安裝步驟一分享出來的印表機

不好意思第1步驟不太懂,是用一台電腦再裝一張網卡再設.0.x嗎?

所以這台電腦就不能關機?

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


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

5
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-20 15:36 »
你們的代管是怎麼談的? 怎麼會連更新資料都要代管業者處理? 自己連不進自己的機器嗎?

當初是請代管公司設計公司網頁 他們有做後台有個使用者界面給我們變更網站資料
但這使用者界面有些細節無法改 所以得麻煩代管公司
這家代管公司人力上好像也有點問題

我們目前和這家代管公司的關係就好像
甲幫乙這位好朋友組裝電腦 沒收多少$ 後來這乙朋友電腦一直當機 就得一直要甲做服務=.=
甲:裝你這台電腦我是虧錢在做耶
乙:怎麼你幫我裝的電腦一直有問題?

6
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-20 14:33 »
最近網站掛二次 都是老闆先發現
再加上先前要做部份網頁修改
代管那邊都得要一星期的作業時間 老闆又是急性子
今天老闆叫我去他朋友那兒也就是代管公司的老闆談
老闆希望我們可以自己來做網站修改
結果代管這邊 不願開放權限給我們 就算是修改幾個字也不願意
說什麼改完要編譯 還要重新發佈...
要我們把自己要的東西做好傳給他們弄就好
要加快作業時間 就是要$... :(



7
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-15 21:02 »
所以現在問題是:
機器給人家代管,但是代管機房竟熱當的現象,所以想把機器拉出來。
但是因為原本的代管廠商是老闆的朋友,所以不方便找其他家代管,
怕老闆的朋友說:「你不給我代管,竟然找別家代管。」
所以想把網站建置在自己公司的機房。
是這樣嗎?


RonLee兄:
老闆朋友這事不說 單就因發生熱當老闆才要我估價給他評估要不要把網站移回來
公司目前連mail server都沒對外聯絡信箱都還用 yaoo google hinet信箱 = =
移回來要怎麼搞都比較有彈性
可是我又剛回本行 很多技術都忘光了 移回來怕自己沒能力去維護
我心裡實在好矛盾... :'(




8
機房過熱...你是代管到哪家業者去了
太神奇

這...我也覺得好離譜

是老闆朋友的公司也不方便說什麼 :o

9
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-15 11:54 »
http://wlt.myweb.hinet.net/FTTB.htm
google一下有那麼難嗎?


謝啦 GOOGLE不難 我的首頁都是GOOGLE
看樣子是我的搜尋功力變弱了 感恩

10
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-14 23:20 »

你看到的是家用的,請看企業用的光纖到府線路,如果你公司不介意用家用形的網路的話,也是可以

damon兄:

我還是找不到每月7000的企業光纖  ???
我找到的這個 http://esmart.seed.net.tw/event/fttx_gift.asp

11
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-14 17:38 »
你怎麼算都不會比租idc便宜的,光對外網路頻寬的費用就夠了,別的不用算
cht的2m/2m一各月就要7千多,這個費用,你可以租到很好的idc了,更何況2m/2m這個對商業網站來說,頻寬根本不夠用

damon兄:

我查hinet adsl費率 20m/2m 只要 2750/月 不一樣的東西嗎?

http://www.cht.com.tw/PersonalCat.php?CatID=899&Module=Fee,Describe

12
MIS 討論區 / 回覆: 相關設備費用問題~
« 於: 2010-10-14 17:08 »
你怎麼算都不會比租idc便宜的,光對外網路頻寬的費用就夠了,別的不用算
cht的2m/2m一各月就要7千多,這個費用,你可以租到很好的idc了,更何況2m/2m這個對商業網站來說,頻寬根本不夠用

感謝damon兄 提供這些數據給我 很有幫助
也請其他版大再提供些數據給我 感恩

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

15
徒兒改玩 m$ 了丫?

還是妳是二棲類...

2003 似乎很耗資源..

使用 1G 的ram來跑 , 還是感覺很慢

16
Embedded 討論版 / Re: 蝦米蝦米是DOM?
« 於: 2005-06-08 00:27 »
引述: "小徒兒"
蝦米蝦米是DOM?聽都沒聽過耶 > _ <


http://www.sciformosa.com.tw/products/images/tc-ide-dom.jpg

一種儲存裝置,一種IDE界面的儲存裝置....
直接插在IDE插槽上..了嗎 ^__^




(千萬別問...什麼是IDE)

17
引述: "linwenwan"
哦..!  180人耶....雖然離我講過最大場的研討會還少一半,但要在180人如此大的教室站五六小時, 的確還是頭一遭...希望大家假日都抽空來聽課就要吸收進去......前天台南場..有幾個人睡著.....我....要回去反省反省...講的真是不夠精彩才有這樣的情況...希望台北場不會有這種情況啦....我會再度更新教材內容....


睡著...我招了 =.=

但吃飽後就緊接著下午的課程

並非是課程不精采 而是個人習慣午睡 拍謝拍謝@@

18
引述: "linwenwan"
釣魚???????????????
Q&A?????????真被誤會了.....明明就有說有問題隨時問的........
唉.......


林大師~抱歉~我到是忘了~~ ^^

也許過程中太精采了 而七個主題講完時間又捉的剛好

釣魚指的是肚辜啦 @_@

19
工作機會 / 急徵VB高手
« 於: 2005-05-23 23:55 »
引述: "netman"
VB? 我很熟啊, 不是就是鳥哥(VBird)嗎?  ^_^

哈....


有人來亂的...=.=

20
當天我也有去...人真的是超多
下午講防火牆時..

也許是粗太飽了~差點睡著
當我倉皇的醒來時~揉了一下臉~左右看了一下 深怕被旁邊的笑

結果...

坐我旁邊的國小女教師竟然在釣魚 ^^"

我比較有興趣的~~是要如何朝向資安人員來準備
很可惜..沒有Q&A時間
也沒聽到林大師以自己為例 說說自己的經歷 可惜.........

21
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.

22
我也投了~票數累積的真快哩@_@

23
embedded 這個好^_^

舉雙腿讚成

雖然我只有碰碰皮毛而已............=.=

24
對象好像只限學校教職人員厚~~>"<

25
雜七雜八 / Re: re: 裝電腦
« 於: 2005-04-20 21:32 »
引述: "duncanlo"
那就跟我一樣,
到B&Q花990買一個鐵力士架,


老哥~是不是這種東西
http://www.bnq.com.tw/product4.do?WSKU=119168

抱歉~把這麼久的文章挖了出來  :o

26
雜七雜八 / 台南在地朋友請幫個忙
« 於: 2005-04-19 18:44 »
老師~感恩了
我已請朋友聯絡你 ^___^

27
BSD 討論版 / 關於openwebmail 的怪問題!
« 於: 2005-04-19 14:30 »
沒有 virtual host 好像也可以~~
使用virtual host 可以省掉輸入一長串的垃址名稱
http://webmail.mydomain

如有錯誤歡迎指正  :o

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

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

好像是要用來擴充歌曲用

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

委托人:蔡先生
手機:0960127616

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

30
課後溫習+認證考試 / 請問一下這題??
« 於: 2005-03-25 21:59 »
考古題 參考題型就好 至於解答
配合N老的觀念實做過一次
這樣印象才會深刻...也才是正解 ^__^

頁: [1] 2 3 4