kuanhung c

FreeNAS 當 iSCSI target server 的設定概念很有趣，以下是概念上的流程: 1. 先從實體的 disk 建立 ZFS Volume, 三顆以上可以選擇建成 RAIDZ 2. 建立好的 ZFS Volume 可以在上面開 data set, 這時候會有 mount point 3. 有了 data set 以後，在 iSCSI 設定裡面可以建立 extends 4. Extends 有分兩種，一種Device Extends 會把整個 data set 拿來用, 另一種 Extends是可以在data set 的 mount point 上設定一個任意指定大小的檔案。 5. 有了 Extends 後，還要設定 Targets. 基本上就是 ACL 6. 接來就是把把 Target 和 Extends link 起來, 這樣就可以變成一個 iSCSI target 了

Booting from GPT http://www.rodsbooks.com/gdisk/booting.html Windows and GPT FAQ http://msdn.microsoft.com/en-us/library/windows/hardware/gg463525.aspx Summary: 目前到 Windows 2012 為止，GPT disk 如果要當 boot volume 一定要透過 UEFI, 傳統的 BIOS 只能用 MBR 當 boot volume. 而 Linux 和 FreeBSD 則是有可能在傳統的 BIOS 用 MBR 和 GPT 當 boot volume. (應該沒誤解吧? Orz)

之前在ESXi 4/5上裝 Dell equallogic multipath plugin 的時候，還不太曉得確切的用途是甚麼。今天看到了兩篇文章，突然明白了。 簡而言之: 負載平衡與容錯。 VMKernel port 綁兩個IP的用意是，讓不同的IP建立不同的 IP Session 去存取 iSCSI target. 兩張網卡互相設定為 active / un-used 是為了容錯。 因此我們不需要在 Switch 上設定 LACP，在 ESXi OS level 就可以幫你處理掉。 因此可以兼顧效能與可用性。這是一個很簡單卻又漂亮的 practice, 我喜歡 :) REF: http://vlife.pixnet.net/blog/post/26926176 http://www.weithenn.org/cgi-bin/wiki.pl?VMware_MPIO http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2038869&sliceId=1&docTypeID=DT_KB_1_1&dialogID=501944480&stateId=1%200%20501958830

Tomato by Shibby For RT-N12-C1 we have to download from: K26RT-N – MIPSR2 – special builds for E4200, RT-N10U, RT-N12B1/C1, RT-N15U, RT-N53, RT-N66U, WNR3500Lv2 and newer Linksys E-series routers Step: 1. Reset AP to factory default 2. Setup staic IP for you desktop or laptop 3. Unplug power 4. Press the reset button in the back of AP the plug power 5. Wait until the pwoer led falsh slowly 6. Open browser and connect http://192.168.1.1 7. You should see a firmware upload page, select the tomato firmware and upload it 8. After upload success wait 5 minutes 9. Connect http://192.168.1.1, if you see the tomato webpage, you have done the job!

If you create a EC2 image from the the sanshot which is a wrong way, you will end up with below error message: EXT3-fs: sda1: couldn't mount because of unsupported optional features (240). EXT2-fs: sda1: couldn't mount because of unsupported optional features (244). Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)     The wrong way is: 1. Create sanpshot from the running instance volume 2. Click the created snapshot and create image from the snapshot 3. Launch instance with the created image   The correct way is: 1. Create image from the running instance 2. Launch instance with the created image   That's it!  

# download source and dependencies cd /usr/src apt-get source squid3 apt-get build-dep squid3 apt-get install libsasl2-dev #  Enable SSL cd squid3-3.1.19 vim debian/rules + --enable-ssl \ # re-configure with enable-ssl ./configure # build package debuild -us -uc -b # Install package under /usr/src dpkg -i squid3-dbg_3.1.19-1ubuntu3.12.04.1_amd64.deb squid-cgi_3.1.19-1ubuntu3.12.04.1_amd64.deb squidclient_3.1.19-1ubuntu3.12.04.1_amd64.deb squid-common_3.1.19-1ubuntu3.12.04.1_all.deb By doing this, you can repackge a new deb package with enable-ssl feature, you can verify by: squid3-v | grep ssl

Chrome and Firefox on windows 7 64 bit OS both are only support 32 bit application. Therefore, if you want to install java plugin in Firefox and Chrome, you need to install java jre 32 bit version instead of 64 bit. Another thing is if after jave jre installation, in java testing page, you still keep asking to install jave plugin, it might caused by some chrome plugins blocks the jave plugin installation. you can use "about:plugins" to disable some plugin or in extension page remove some extenstions.