﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>IT博客-存储设备及Unix学习笔记</title><link>http://www.cnitblog.com/smile-ttt/</link><description /><language>zh-cn</language><lastBuildDate>Wed, 29 Apr 2026 06:01:08 GMT</lastBuildDate><pubDate>Wed, 29 Apr 2026 06:01:08 GMT</pubDate><ttl>60</ttl><item><title>启动VNC图形界面</title><link>http://www.cnitblog.com/smile-ttt/archive/2010/09/14/68823.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Tue, 14 Sep 2010 09:29:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2010/09/14/68823.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/68823.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2010/09/14/68823.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/68823.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/68823.html</trackback:ping><description><![CDATA[编辑/root/.vnc/xstartup<br>把twm改成startkde<br>如果安装的是gnome<br>把twm改成exec gnome-session<br><br>然后vncserver<br>再重新连入vnc就进入图形界面了<br><br> <img src ="http://www.cnitblog.com/smile-ttt/aggbug/68823.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2010-09-14 17:29 <a href="http://www.cnitblog.com/smile-ttt/archive/2010/09/14/68823.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>AIX连接XIV会出现的问题</title><link>http://www.cnitblog.com/smile-ttt/archive/2010/04/11/65205.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Sun, 11 Apr 2010 03:54:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2010/04/11/65205.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/65205.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2010/04/11/65205.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/65205.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/65205.html</trackback:ping><description><![CDATA[使用AIX系统连接XIV后，装好XIV host attach的安装包后运行cfgmgr依然会出现这样一个warning：<br># cfgmgr<br>cfgmgr: 0514-621 WARNING: The following device packages are required for<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; device support but are not currently installed.<br>devices.fcp.array<br><img alt=""  src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/29.jpg"><br>不影响使用，暂未找到解决办法。<br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/65205.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2010-04-11 11:54 <a href="http://www.cnitblog.com/smile-ttt/archive/2010/04/11/65205.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>在Linux下设置环境变量</title><link>http://www.cnitblog.com/smile-ttt/archive/2010/03/30/64931.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Tue, 30 Mar 2010 05:58:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2010/03/30/64931.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/64931.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2010/03/30/64931.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/64931.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/64931.html</trackback:ping><description><![CDATA[临时修改环境变量<br>export PATH=/.../.../... （大小写敏感）<br>e.g.<br>export /usr/lpp/mmfs/bin<br>将GPFS的命令export出来，只对当前会话有效<br><br>永久修改环境变量<br>修改.bash_profile文件<br>在PATH变量后加上需要增加的内容<br><br>e.g.<br><br>PATH=$PATH:$HOME/bin<span style="color: #ff204a;">:/usr/lpp/mmfs/bin</span> （红色部分是新增内容）<br>保存后使用<br>source .bash_profile命令使修改生效。<br><br>这样操作可对当前用户的环境变量修改永久有效。<br><br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/64931.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2010-03-30 13:58 <a href="http://www.cnitblog.com/smile-ttt/archive/2010/03/30/64931.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>在AIX上用SDD命令查看DS4K/DS5K的prefer path</title><link>http://www.cnitblog.com/smile-ttt/archive/2010/03/15/64653.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Mon, 15 Mar 2010 10:17:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2010/03/15/64653.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/64653.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2010/03/15/64653.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/64653.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/64653.html</trackback:ping><description><![CDATA[sddpcm_get_config -Av <br>这个命令可以在主机端查看DS4K/5K的LUN是否分布在Prefer的controller上<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>AIX:/#sddpcm_get_config -Av&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>Frame id 0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Storage Subsystem worldwide name: 60ab8006e56e00004b85d99c&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Controller count: 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Partition count: 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Partition 0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Storage Subsystem Name = 'DS5100'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN #&nbsp;&nbsp; Ownership&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; User Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN02&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN04&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN05&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN06&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN07&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN08&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN09&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; A (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hdisk13&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11&nbsp;&nbsp; B (preferred)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LUN12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/64653.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2010-03-15 18:17 <a href="http://www.cnitblog.com/smile-ttt/archive/2010/03/15/64653.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Install VMware Tools</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/12/02/62978.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Wed, 02 Dec 2009 10:05:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/12/02/62978.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62978.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/12/02/62978.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62978.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62978.html</trackback:ping><description><![CDATA[在VMware ESX上装好Guest OS后点shut down后会提示你没有装vmware tool，这个动作是不能被执行的。VMware tool里有一些优化图形化界面，识别新设备（pvscsi）等driver。<br>安装VMware Tool不需要特别插入光盘。<br>点VM-&gt;Guest-&gt;Install/Upgrade VMware Tools即可。<br>Redhat5上，安装完RPM包后，需要执行：<br>/usr/bin/vmware-config-tools.pl<br>按照提示，完成后才能完成安装VMware tool。<br>Windows2008按照wizard提示即可完成安装。<br><br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/62978.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-12-02 18:05 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/12/02/62978.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Linux下的计划任务</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/11/30/62915.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Mon, 30 Nov 2009 15:14:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/11/30/62915.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62915.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/11/30/62915.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62915.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62915.html</trackback:ping><description><![CDATA[crontab：<br><br><span style="font-style: italic;">crontab -e</span>可以编辑linux下的计划任务，格式是<br>Min Hour Day Mon DoW CMD<br>分钟 小时 天 月 一周中的某一天 命令<br>如 <br><span style="font-style: italic;">1 1 * * 1 date</span><br>就是在每周一的1点零1分执行 <span style="font-style: italic;">date</span>这个命令，其他使用方式网上可以搜到很多类似的使用方式。<br><br>这里要说的是，<span style="font-style: italic;">crontab -e</span>命令将编辑的内容直接写入<span style="font-style: italic;">/etc/crontab</span> 这个文件，执行这个命令后，计划任务是可以直接被启用的，用<span style="font-style: italic;">crontab -l</span>命令可以看到。<br><br>也可以直接使用vi编辑<span style="font-style: italic;">/etc/crontab</span>文件，编辑好后用<span style="font-style: italic;">crontab -l</span>可能发现提示你当前用户下没有计划任务，这个时候不要觉得奇怪，只要<span style="font-style: italic;">crontab /etc/crontab</span>一下，就可以使用了。<br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/62915.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-11-30 23:14 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/11/30/62915.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>在VMware ESX Server 4上使用Buslogic SCSI controller安装Windows2003</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62750.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Sat, 21 Nov 2009 15:35:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62750.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62750.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62750.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62750.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62750.html</trackback:ping><description><![CDATA[在默认情况下，windows2003使用的SCSI controller是LSI Logic，如果有需要使用Buslogic，直接把Controller的类型改成Buslogic会有一些问题，我遇到过的问题有无法认出硬盘，开机后完全黑屏等。如果要成功的使用Buslogic安装windows2003，需要以下一些操作。<br><br>1）不要以默认方式创建虚拟机，要选择custom方式<br><img src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/5.JPG" border="0"><br>在选择SCSI Controller时选择BusLogic<br><img src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/6.JPG" border="0"><br>2)创建好之后，要将系统中自带的一个flp文件load进虚拟软驱里，并选择(Connected at power on)<br><img src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/7.JPG" border="0"><br>3）这个时候可以开机启动，现在就可以读到虚拟光驱里的安装文件（iso文件）了，在启动过程中按下F6键，将软驱中的driver读取进来，后边就可以正常安装了。<br><br>如果开机后认不到安装盘，可能是BIOS里，光驱不是作为第一个启动选项，可以在Edit Setting里，修改设置，强制系统开机后进入BIOS设置：<br><img  src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/cfgOptions.JPG" border="0"><br>然后到启动项，将光驱提升到第一个：<br><img  src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/bootOption.JPG" border="0"><br>这样就可以正常安装了。<br><br> <img src ="http://www.cnitblog.com/smile-ttt/aggbug/62750.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-11-21 23:35 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62750.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Linux下正在使用的文件可以被删除</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62744.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Fri, 20 Nov 2009 17:03:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62744.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62744.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62744.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62744.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62744.html</trackback:ping><description><![CDATA[真是惭愧，用了这么久的linux才意识到在linux下正在被使用的文件是可以被删除的，虽然这个早就知道，可是从来没有意识到。用惯了windows都知道，在winodws里一个文件正在使用的情况下是不能被删除的，系统会提示你正在被使用，但是linux下会不做任何提示的删除，不过文件所占用的空间直到使用结束后才被释放。所以在使用linux的情况下，删除重要文件的操作一定要谨慎哦~<br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/62744.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-11-21 01:03 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/11/21/62744.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Challenge-Handshake Authentication Protocol</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/11/20/62722.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Fri, 20 Nov 2009 06:21:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/11/20/62722.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62722.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/11/20/62722.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62722.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62722.html</trackback:ping><description><![CDATA[课本里学的信息安全，今天在工作中第一次实际使用，一开始很想翻译一下这个Challenge-Handshake Authentication Protocol，可是想了半天也没有想到什么合适的翻译，search了一下，发现中文翻译是：挑战握手协议，台湾的翻译是：验证通讯协议。现在我不得不承认有一些词语的翻译，还是台湾翻译的好一些，其实未必非要直译出来，否则听起来好奇怪。<br><br><strong style="color: #101fff;">挑战握手协议</strong><span style="color: #101fff;">（Challenge-Handshake Authentication Protocol，</span><strong style="color: #101fff;">CHAP</strong><span style="color: #101fff;">）是一个用来</span><a  href="http://zh.wikipedia.org/w/index.php?title=%E9%AA%8C%E8%AF%81&amp;action=edit&amp;redlink=1" style="color: #101fff;" class="new" title="验证（尚未撰写）">验证</a><span style="color: #101fff;">用户或网络提供者的协议。负责提供验证服务的机构，可以是</span><a  href="http://zh.wikipedia.org/zh-cn/%E4%BA%92%E8%81%AF%E7%B6%B2%E6%9C%8D%E5%8B%99%E4%BE%9B%E6%87%89%E5%95%86" style="color: #101fff;" title="互联网服务供应商" class="mw-redirect">互联网服务供应商</a><span style="color: #101fff;">，又或是其他的验证机构。</span><br style="color: #101fff;"><br style="color: #101fff;">
<p style="color: #101fff;">CHAP 用于使用3次握手周期性的验证对端身份。在链路建立初始化时这样做，也可以在链路建立后任何时间重复验证。</p>
<ol style="color: #101fff;">
    <li>在链路建立完成后，验证者向对端发送一个&#8220;challenge&#8221;信息。</li>
    <li>对端使用一个&#8220;one-way-hash&#8221;函数，例如<a  href="http://zh.wikipedia.org/zh-cn/MD5" title="MD5">MD5</a>，计算出的值响应这个信息。</li>
    <li>验证者使用自己计算的hash值校验响应值。如果两个值匹配，则验证是承认得，否则连接应该终止。</li>
    <li>在随机时间，验证端发送一个&#8220;challenge&#8221;给对端，重复1到3步。</li>
</ol>
<p style="color: #101fff;">CHAP通过增量改变标识和&#8220;challenge-value&#8221;的值避免&#8220;playback attack&#8221;攻击。验证的两端都需要知道&#8220;challenge&#8221;信息的明文，但不会在互联网上传播。</p>
注：以上内容来自维基百科。<br><br>
<h2 style="color: #101fff;">CHAP：挑战握手认证协议 （Challenge Handshake Authentication Protocol）</h2>
<p style="color: #101fff;">挑战握手认证协议（CHAP）通过三次握手周期性的校验对端的身份，在初始链路建立时完成，可以在链路建立之后的任何时候重复进行。</p>
<ol style="color: #101fff;">
    <li>链路建立阶段结束之后，认证者向对端点发送&#8220;challenge&#8221;消息。</li>
    <li>对端点用经过单向哈希函数计算出来的值做应答。</li>
    <li>认证者根据它自己计算的哈希值来检查应答，如果值匹配，认证得到承认；否则，连接应该终止。</li>
    <li>经过一定的随机间隔，认证者发送一个新的 challenge 给端点，重复步骤 1 到 3 。</li>
</ol>
<p style="color: #101fff;">通过递增改变的标识符和可变的挑战值，CHAP 防止了来自端点的重放攻击，使用重复校验可以限制暴露于单个攻击的时间。认证者控制验证频度和时间。</p>
<p style="color: #101fff;">该认证方法依赖于只有认证者和对端共享的密钥，密钥不是通过该链路发送的。</p>
<p style="color: #101fff;">虽然该认证是单向的，但是在两个方向都进行 CHAP 协商，同一密钥可以很容易的实现相互认证。</p>
<p style="color: #101fff;">由于 CHAP 可以用在许多不同的系统认证中，因此可以用 NAME 字段作为索引，以便在一张大型密钥表中查找正确的密钥，这样也可以在一个系统中支持多个 NAME/ 密钥对，并可以在会话中随时改变密钥。</p>
<p style="color: #101fff;">CHAP 要求密钥以明文形式存在，无法使用通常的不可回复加密口令数据库。</p>
<p style="color: #101fff;">CHAP 在大型网络中不适用，因为每个可能的密钥由链路的两端共同维护。</p>
<p style="color: #101fff;"><strong>协议结构</strong></p>
<p style="color: #101fff;">CHAP 的配置选项格式如下：</p>
<table style="color: #101fff;" border="1" bordercolor="#999999" cellpadding="5" cellspacing="0">
    <tbody>
        <tr align="center" bgcolor="#efefef">
            <td><strong>8</strong></td>
            <td><strong>16</strong></td>
            <td><strong>32</strong></td>
            <td><strong>40 bit</strong></td>
        </tr>
        <tr align="center">
            <td>Type</td>
            <td>Length</td>
            <td>Authentication-Protocol</td>
            <td>Algorithm</td>
        </tr>
    </tbody>
</table>
<ul style="color: #101fff;">
    <li>Type ― 3</li>
    <li>Length ― 5</li>
    <li>Authentication-Protocol ― 对于 CHAP，为 C223（Hex）。</li>
    <li>Algorithm ― Algorithm 字段为八位字节，表示使用的认证方法。</li>
</ul>
<p style="color: #101fff;">CHAP 数据包结构如下所示：</p>
<table style="color: #101fff;" border="1" bordercolor="#999999" cellpadding="5" cellspacing="0">
    <tbody>
        <tr align="center" bgcolor="#efefef">
            <td><strong>8</strong></td>
            <td><strong>16</strong></td>
            <td><strong>32 bit</strong></td>
            <td><strong>Variable</strong></td>
        </tr>
        <tr align="center">
            <td>Code&gt;</td>
            <td>Identifier</td>
            <td>Length</td>
            <td>Data . . .</td>
        </tr>
    </tbody>
</table>
<ul style="color: #101fff;">
    <li>Code ― 识别 CHAP 数据包类型。CHAP 代码具有以下几种：1、Challenge；2、Response；3、Success；4、Failure。</li>
    <li>Identifier ― 用于匹配 Challenges、Responses 和 Replies 信息。</li>
    <li>Length ― CHAP 数据包的长度，包括 Code、Identifier、Length 和 Data 字段。</li>
    <li>Data ― 0或更多八位字节。该字段格式取决于 Code 字段。对于 Success 和 Failure，Data 字段包括一个独立执行的可变信息字段</li>
</ul>
<p style="color: #101fff;">相关协议：<a  href="http://www.networkdictionary.cn/protocols/ppp.php" target="_blank">PPP</a>、<a  href="http://www.networkdictionary.cn/protocols/pppoe.php" target="_blank">PPPoE</a>、<a  href="http://www.networkdictionary.cn/protocols/pppoa.php" target="_blank">PPPoA</a>、<a  href="http://www.networkdictionary.cn/protocols/lcp.php" target="_blank">LCP</a>、<a  href="http://www.networkdictionary.cn/protocols/ncp.php" target="_blank">NCP</a>、<a  href="http://www.networkdictionary.cn/protocols/pap.php" target="_blank">PAP</a></p>
<p style="color: #101fff;">组织来源：CHAP 由 IETF（<a  href="http://www.ietf.org/" target="_blank">http://www.ietf.org/</a>）定义。</p>
<p style="color: #101fff;">相关链接：<a  href="http://www.javvin.com/protocol/rfc1994.pdf" target="_blank">http://www.javvin.com/protocol/rfc1994.pdf</a>: PPP Challenge Handshake Authentication Protocol （CHAP)</p>
（注：以上内容来自网络大典）<br><br>
<h1 class="firstHeading" id="firstHeading">Challenge-handshake authentication
protocol</h1>
<div style="color: #101fff;" id="bodyContent" sizcache="0" sizset="0"><!-- start content -->
<p>In <a  href="http://www.cnitblog.com/wiki/Computing" title="Computing">computing</a>, the
<strong>Challenge-Handshake Authentication Protocol (CHAP)</strong> <a  href="http://www.cnitblog.com/wiki/Authentication" title="Authentication">authenticates</a> a user or
network host to an authenticating entity. That entity may be, for example, an <a  href="http://www.cnitblog.com/wiki/Internet_service_provider" title="Internet service provider">Internet access provider</a>.</p>
<p><a  href="http://www.cnitblog.com/wiki/Request_for_Comments" title="Request for Comments">RFC</a>
1994: PPP Challenge Handshake Authentication Protocol (CHAP) defines the <a  href="http://www.cnitblog.com/wiki/Protocol_%28computing%29" title="Protocol (computing)">protocol</a>.</p>
<p>CHAP is an authentication scheme used by <a  href="http://www.cnitblog.com/wiki/Point_to_Point_Protocol" class="mw-redirect" title="Point to Point Protocol">Point to
Point Protocol (PPP)</a> servers to validate the identity of remote clients.
CHAP periodically verifies the identity of the <a  href="http://www.cnitblog.com/wiki/Client_%28computing%29" title="Client (computing)">client</a> by using a <a  href="http://www.cnitblog.com/wiki/Handshaking" title="Handshaking">three-way handshake</a>. This happens at the time of
establishing the initial <a  href="http://www.cnitblog.com/wiki/Data_link" title="Data link">link</a>,
and may happen again at any time afterwards. The verification is based on a <a  href="http://www.cnitblog.com/wiki/Shared_secret" title="Shared secret">shared secret</a> (such as the
client user's password).</p>
<ol>
    <li>After the completion of the link establishment phase, the authenticator
    sends a "challenge" message to the peer.
    </li>
    <li>The peer responds with a value calculated using a <a  href="http://www.cnitblog.com/wiki/One-way_function" title="One-way function">one-way hash
    function</a>, such as an <a  href="http://www.cnitblog.com/wiki/MD5" title="MD5">MD5</a> <a  href="http://www.cnitblog.com/wiki/Checksum" title="Checksum">checksum</a> <a  href="http://www.cnitblog.com/wiki/Hash_function" title="Hash function">hash</a>.
    </li>
    <li>The authenticator checks the response against its own calculation of the
    expected hash value. If the values match, the authenticator acknowledges the
    authentication; otherwise it should terminate the connection.
    </li>
    <li>At random intervals the authenticator sends a new challenge to the peer and
    repeats steps 1 through 3. </li>
</ol>
<p>CHAP provides protection against <a  href="http://www.cnitblog.com/wiki/Playback_attack" class="mw-redirect" title="Playback attack">playback attack</a> by the peer through the use of
an incrementally changing identifier and of a variable challenge-value. CHAP
requires that both the client and server know the plaintext of the secret,
although it is never sent over the network.</p>
<p><a  href="http://www.cnitblog.com/wiki/Microsoft" title="Microsoft">Microsoft</a> has implemented a
variant of the Challenge-handshake authentication protocol, called <a  href="http://www.cnitblog.com/wiki/MS-CHAP" title="MS-CHAP">MS-CHAP</a>, which does not require either
peer to know the plaintext.</p>
<table class="toc" id="toc" sizcache="0" sizset="0">
    <tbody sizcache="0" sizset="0">
        <tr sizcache="0" sizset="0">
            <td sizcache="0" sizset="0"><br></td>
        </tr>
    </tbody>
</table>
<h2>&nbsp;<span class="mw-headline" id="Working_Cycle">Working Cycle</span></h2>
<ul>
    <li>Challenge Packet (System to User)
    </li>
    <li>Response Packet (User to System)
    </li>
    <li>Success or failure packet (System to User) </li>
</ul>
<h2><span class="editsection"></span> <span class="mw-headline" id="CHAP_Packets">CHAP Packets</span></h2>
<table class="wikitable">
    <tbody>
        <tr>
            <th>Description</th>
            <th>1 byte</th>
            <th>1 byte</th>
            <th>2 bytes</th>
            <th>1 byte</th>
            <th>Variable</th>
            <th>variable</th>
        </tr>
        <tr>
            <td>Challenge</td>
            <td>Code = 1</td>
            <td>ID</td>
            <td>Length</td>
            <td>Challenge length</td>
            <td>Challenge value</td>
            <td>Name</td>
        </tr>
        <tr>
            <td>Response</td>
            <td>Code = 2</td>
            <td>ID</td>
            <td>Length</td>
            <td>Response Length</td>
            <td>Response value</td>
            <td>Name</td>
        </tr>
        <tr>
            <td>Success</td>
            <td>Code = 3</td>
            <td>ID</td>
            <td>Length</td>
            <td><br></td>
            <td>Message</td>
            <td><br></td>
        </tr>
        <tr>
            <td>Failure</td>
            <td>Code = 4</td>
            <td>ID</td>
            <td>Length</td>
            <td><br></td>
            <td>Message</td>
            <td><br></td>
        </tr>
    </tbody>
</table>
<p>CHAP packet embedded in a PPP frame. The protocol field has a value of
0xC223</p>
<table class="wikitable">
    <tbody>
        <tr>
            <th>Flag</th>
            <th>Address</th>
            <th>Control</th>
            <th>Protocol (0xC223)</th>
            <th>Payload (table above)</th>
            <th>FCS</th>
            <th>Flag</th>
        </tr>
    </tbody>
</table>
</div>
（注：以上内容来自英文维基百科）<br><br>今天我做的应用是在iSCSI SAN网络里对Server（host）和Storage端使用CHAP来加密，两端通过name字段来找到密钥进行验证，具体内容以后有机会再贴上来。<br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/62722.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-11-20 14:21 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/11/20/62722.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>在windows server 2008中禁用密码复杂性</title><link>http://www.cnitblog.com/smile-ttt/archive/2009/11/19/62695.html</link><dc:creator>笑笑</dc:creator><author>笑笑</author><pubDate>Thu, 19 Nov 2009 15:32:00 GMT</pubDate><guid>http://www.cnitblog.com/smile-ttt/archive/2009/11/19/62695.html</guid><wfw:comment>http://www.cnitblog.com/smile-ttt/comments/62695.html</wfw:comment><comments>http://www.cnitblog.com/smile-ttt/archive/2009/11/19/62695.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/smile-ttt/comments/commentRss/62695.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/smile-ttt/services/trackbacks/62695.html</trackback:ping><description><![CDATA[在安装windows2008之后，开机必须设置密码，且密码中必须包含大写字母，小写字母，数字，特殊字符中的至少3种类型，即使安装好之后想修改为简单密码也是不可以的，必须要先去禁用掉他的密码复杂性。<br><br>1）Start-&gt;Run: gpedit.msc 打开组策略编辑器<br>2）Local Computer Policy-&gt;Computer Configuration-&gt;Windows Settings-&gt;Security Settings-&gt;Account Policies-&gt;Password Policy<br>在这里把Password must meet complexity requirements properties设置成disabled<br><img  src="http://www.cnitblog.com/images/cnitblog_com/smile-ttt/4.JPG" border="0"><br>3）如果不想有密码过期的问题，可以把Maximum Password Age设成999（最大只能是999）<br><br><br>这样就不再限制你的密码复杂性，可以根据自己的需要来修改密码了。<br><br><br><img src ="http://www.cnitblog.com/smile-ttt/aggbug/62695.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/smile-ttt/" target="_blank">笑笑</a> 2009-11-19 23:32 <a href="http://www.cnitblog.com/smile-ttt/archive/2009/11/19/62695.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item></channel></rss>