<?xml version="1.0" encoding="GB2312"?>
<rss version="2.0">
<channel>
<title><![CDATA[My Blog Homepage]]></title>
<link>http://blog.edu.cn/user1/13760/index.shtml</link>
<description><![CDATA[My Blog Homepage]]></description>
<item>
<title><![CDATA[phrase appeared in moive]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2008/2088113.shtml</link>
<description><![CDATA[<P>Actually, It's starting to feel like home.</P>
<P>As far as know, there ain't fish in scottdale.</P>
<P>Get out of my car.</P>
<P>Why don't you give it the secret knock so that he know it's you?</P>
<P>What make you think I have the combination.</P>
<P>Just do what he says, huh.</P>
<P>How many times you gonna pull the little thing out?</P>
<P>As many times as I feel necessary.</P>
<P>What, you think it make you look strong?</P>
<P>All it does is magnify your weekness.</P>
<P>I was gonna tell you all about this.</P>
<P>But you ain't go nowhere.</P>
<P>How you finishing up the hole?</P>
<P>Promise me you will take XX with you.</P>
<P>He is the only one who figure this plan out.</P>
<P>Too bad you won't be around to enjoy it.</P>
<P>Offer me a branch of cash to talk behind your back.</P>
<P>How can I believe anything anymore?</P>
<P>We need some kind of support brace for the tunnel.<BR>Or what, or the whole thing collapses, and we're buried alive.</P>
<P>I'll kill him myself If I have to , all right</P>
<P>I want scofield dead as much as you.</P>
<P>But not at cost of an uprising.</P>
<P>They wanted to talk to you about the helicopter. right?</P>
<P>I don't know what you're talking about , and neither do you.</P>
<P>Maybe I didn't enunciate myself.</P>
<P>Hey, we need somebody to stay outside in case XX returns.</P>
<P>I thought we couldn't dig through this stuff.</P>
<P>It's all going to come down on our head.</P>
<P>All would have been forgiven.</P>
<P>I can't even run shipments from one dock to the other, but I still keep you by my side.</P>
<P>I'll let you walk out of here, out of respect what you were.</P>
<P>We should start looking for pieces about four feet in length.</P>
<P>Anyone got problem with that?</P>
<P>That's who you want to talk to.</P>
<P>I need to meet with susan.</P>
<P>tell her whatever you think she wants to hear.</P>
<P>How you dealing with the animals here?</P>
<P>&nbsp;</P>
<P>There's one way to make certain of that.</P>
<P>I need more men sent to me at once.</P>
<P>sit tight</P>
<P>If I don't get another chance, I want you to know to that I appreciate everything you've </P>
<P>done.</P>
<P>How'd you find us?</P>
<P>What do you think happened to XX?</P>
<P>Why don't you just tell us what you know?</P>
<P>You won't wind up being beaten half to death like your friends.</P>
<P>We already had this discussion back at the beach.</P>
<P>You're making a terrible mistake.</P>
<P>If I knew you boys partied in sona like this. I never would have tried to escape.</P>
<P>Always with the wise talk.</P>
<P>Never saying anything we want to hear.</P>
<P>What is the place where we're gonna to make the exchange.</P>
<P>assuming you're still alive....you still talking?</P>
<P>Think this will work.</P>
<P>I don't care what he says. He's a piece of garbage.</P>
<P>I don't know anything about ** guy.</P>
<P>Here's everthing we have on the escaped prisons.</P>
<P>you sure you don't want to change your story?</P>
<P>This should help make you a decent brace.</P>
<P>Should be able to see them comming from up here?</P>
<P>It's just a matter of fact.</P>
<P>I was gonna to kill you at the beach, but I didn't want to do anything that was gonna to get us caught.</P>
<P>I'm gonna give you the courtesy you never gave him.</P>
<P>What are we gonna do now?</P>]]></description>
<author>erictb</author>
<pubDate>2008-3-28 1:36:00</pubDate>
</item>
<item>
<title><![CDATA[some tips of recent thinking point]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2008/2033122.shtml</link>
<description><![CDATA[<P>1, &nbsp;独狼 与 群狼</P>
<P>2, 过程控制，F(X)</P>
<P>3, 服务: 企业运营的模式，面向服务；管理者的管理理念，服好务， ps： IBM的SOA，IBM盈利最主要来源。</P>]]></description>
<author>erictb</author>
<pubDate>2008-1-19 0:21:00</pubDate>
</item>
<item>
<title><![CDATA[vsftpd 安装及其他问题]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2008/2021218.shtml</link>
<description><![CDATA[<P>(一) vsftpd 安装问题</P>
<P>安装：rpm -ivh vsftpd-1.1.3-8.i386.rpm<BR>删除：rpm -e vsftpd</P>
<P>1. 修改/etc/vsftpd/vsftpd.conf <BR>将 listen=YES 改为 listen=NO </P>
<P>2. 在/etc/xinetd.d/里新增一个档案vsftpd： <BR>#vi /etc/xinetd.d/vsftpd <BR>service vsftpd <BR>{ <BR>disable = no <BR>socket_type = stream <BR>wait = no <BR>user = root <BR>server = /usr/sbin/vsftpd <BR>port = 21 <BR>log_on_success += PID HOST DURATION <BR>log_on_failure += HOST <BR>} </P>
<P>3.重新启动xinetd <BR>/sbin/service xinetd restart Stopping xinetd: [ OK ] <BR>Starting xinetd: [ OK ] <BR>#</P>
<P>(二) 为了使editplus全程连接到linux中的文件并进行编辑：<BR>修改<BR>/etc/vsftpd.ftpusers<BR>/etc/vsftpd.user_list<BR>注释掉root那一行</P>
<P><BR>(三) service vsftpd restart 出现：<BR>“vsftpd 已死，但是 subsys 被锁” 的提示</P>
<P>vim /etc/vsftpd/vsftpd.conf<BR>chroot_local_user=YES 这一行本来是注释，现取消注释</P>
<P>/sbin/service xinetd restart<BR>service vsftpd restart<BR>现在editplus远程无法连接到linux中的文件</P>
<P>解决办法：再将chroot_local_user=YES 注释掉<BR>/sbin/service xinetd restart<BR>service vsftpd restart</P>
<P>就ok了</P>
<P>&nbsp;</P>]]></description>
<author>erictb</author>
<pubDate>2008-1-4 16:56:00</pubDate>
</item>
<item>
<title><![CDATA[Some Tips for Writing Paper]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2007/1935731.shtml</link>
<description><![CDATA[<P><SPAN style="FONT-SIZE: 12pt"><STRONG>Typical Paper Structure:</STRONG></SPAN><BR><SPAN style="FONT-SIZE: 10pt">&nbsp;-Title<BR>&nbsp;-Abstract<BR>&nbsp;-Introduction<BR>&nbsp;-Optional: Background<BR>&nbsp;-Related Work (alternatively put before conclusion)<BR>&nbsp;-Approach/Modeling/Framework/Solution/Algorithms…….<BR>&nbsp;-Implementation<BR>&nbsp;-Performance Evaluation/Comparison / Experiment/Case Studies/Examples<BR>&nbsp;-Discussion&nbsp;<BR>&nbsp;-Conclusions (and Future work)</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 12pt"><STRONG>Title</STRONG></SPAN><BR><SPAN style="FONT-SIZE: 10pt">?Suggest: a cute name that <STRONG><SPAN style="COLOR: #0000cd">sticks in people's minds<BR></SPAN><SPAN style="COLOR: #0000cd">?Use adjectives that describe the distinctivefeatures of your work</SPAN></STRONG><BR>-e.g., reliable, scalable, high-performance, robust, low-complexity, or low-cost, etc.<BR>?Some sample titles<BR>-“Latency-sensitive hashing for collaborative Web caching”<BR>-“Core-Stateless Fair Queueing: Achieving Approximately Fair Bandwidth Allocations in High Speed Networks”<BR>-“Exploiting Idle Communication Power to Improve Wireless Network Performance and Energy Efficiency”</SPAN></P>
<DIV><SPAN style="FONT-SIZE: 10pt">Title writing pitfall:<BR>&nbsp;-Don't put uncommon buzzwords there, Otherwise, bad for paper search engines or readers who would like to understand what the paper is about by reading the title<BR>&nbsp;-Be specific enough but not too specific<BR>&nbsp;-Be careful in using “new”“novel”in title<BR>&nbsp;-Be careful in using “performance evaluation”etc. in title</SPAN></DIV>
<DIV><BR><SPAN style="FONT-SIZE: 10pt"><STRONG>Abstract</STRONG></SPAN><BR><SPAN style="FONT-SIZE: 10pt">?Abstract structure:<BR><STRONG><SPAN style="COLOR: #0000cd">&nbsp;-Short motivation (problem); Proposed solution; Evaluation; Evaluation results.</SPAN></STRONG></SPAN></DIV>
<DIV><SPAN style="FONT-SIZE: 10pt">?Abstract writing pitfall:<BR>&nbsp;-Don’t put unexplained or undefined terms whose meanings are not well known<BR>&nbsp;-must not contain references<BR>&nbsp;-Avoid general motivation.<BR>&nbsp; e.g., U do not have to justify the importance of the Internet orexplain what QoS is.<BR>&nbsp;-Avoid equations and math. <BR>&nbsp; Exceptions: Your paper proposes E = m c2.</SPAN></DIV>
<P><BR><SPAN style="FONT-SIZE: 10pt"><SPAN style="FONT-SIZE: 12pt; COLOR: #0000cd"><STRONG>Introduction Structure</STRONG></SPAN><BR>?Sufficient motivation, problem to be solved, why existing solutions are not sufficient<BR>?Proposed solution and brief summary<BR>&nbsp;-Using such as “In this paper, we address the problem of….”<BR>?Optional: brief mention of related work if it is very related and explain differences<BR>?Evaluation and evaluation results<BR>?Optional: “The paper makes the following main contributions: + bulleted items”<BR>&nbsp;-Easy for reviewers to dig out major contributions<BR>?Structure layout of the paper<BR>&nbsp;-to give readers high level ideas how different parts are related to each other<BR>&nbsp;-Similar principle applied throughout the paper for subsections<BR>?Don’t overclaim(even throughout the paper)!<BR>&nbsp;-But it is good to put your work in a bigger picture and a largerbackground<BR>?If you want to claim some unjustified points, it is better to put them in conclusion or </SPAN><SPAN style="FONT-SIZE: 10pt">discussion section<BR>?Be careful on wording<BR>&nbsp;-“Our approach provides a foundation for this new field.”<BR>&nbsp;-“We believe our work in this paper create a new research filed…”<BR>&nbsp;-“We completely and generally solved …”<BR>?Similarly don’t over-criticize other’s work (even throughout the paper)!</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><SPAN style="FONT-SIZE: 12pt"><STRONG>5-paragraph rule on writing Introduction</STRONG></SPAN><BR>?Introductory paragraph:<BR>&nbsp;-Very briefly: What is the problem<BR>&nbsp;-why is it relevant?<BR>?Background paragraph<BR>&nbsp;-Elaborate on why the problem is hard,<BR>&nbsp;-critically examining prior work, trying to tease out one or two central shortcomings that </SPAN><SPAN style="FONT-SIZE: 10pt">your solution overcomes<BR>?Transition paragraph:<BR>&nbsp;-What keen insight did apply to overcome the shortcomings of other approaches?<BR>?Details paragraph<BR>&nbsp;-What technical challenges did you have to overcome<BR>&nbsp;-what kinds of validation did you perform?<BR>?Assessment paragraph:<BR>&nbsp;-Assess your results and briefly state the broadly interesting conclusions that these </SPAN><SPAN style="FONT-SIZE: 10pt">results support.<BR>&nbsp;-followed by an overview of the structure of the paper with interleaved section callouts.</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="FONT-SIZE: 12pt">Background and Related Work</SPAN></STRONG><BR><STRONG><SPAN style="COLOR: #0000cd">?You can organize related work with subsections or group them in several categories</SPAN></STRONG><BR><STRONG><SPAN style="COLOR: #0000cd">?Don’t simply list related work without Relatingto your own work!</SPAN></STRONG><BR>&nbsp;-keywords to use: whereas, in contrast, but, however, …<BR>&nbsp;-“excuses”to use: , “focus on different problems”, “complement with each other”, …<BR>&nbsp;-you can describe several similar related approaches together and compare them at once with </SPAN><SPAN style="FONT-SIZE: 10pt">yours<BR>?Don’t make unjustified unobvious criticismson related work if you don’t have experimental </SPAN><SPAN style="FONT-SIZE: 10pt">results to back you up.<BR>&nbsp;-But you can cite others’experiments to back you up.<BR>?Don’t overclaim your work without justification<BR>?Don’t intentionally leave out your own very related previous papers (reviewers can find </SPAN><SPAN style="FONT-SIZE: 10pt">them out easily)<BR>&nbsp;-maybe even need to mention them in Introduction section and explain why the new work is </SPAN><SPAN style="FONT-SIZE: 10pt">different<BR>?Put in PC members’work (for conference paper) if relevant</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="FONT-SIZE: 12pt">Approach/Modeling/Framework/Solution/Algorithms…….</SPAN></STRONG><BR>?<STRONG><SPAN style="COLOR: #0000cd">Generalizeyour work in an abstraction level, <BR></SPAN></STRONG>&nbsp;e.g., positioning it as a framework rather than a tool<BR>&nbsp;-What you develop should be beyond your own implementation<BR>?Try to separate the ideas from (a particular) concrete implementation<BR><STRONG><SPAN style="COLOR: #0000cd">?Explain some details with examples</SPAN></STRONG><BR>?Typical and meaningful<BR>?A simple example<BR>&nbsp;-Include: where it comes from; brief description<BR>&nbsp;-Throughout the paper, it is important to have illustrating examplesfor those places that </SPAN><SPAN style="FONT-SIZE: 10pt">contain “dry”descriptions of your approach<BR>?Optional part of the section: high level description of applying your approach on the </SPAN><SPAN style="FONT-SIZE: 10pt">example</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><SPAN style="FONT-SIZE: 12pt"><STRONG>Implementation ( such as “Considerations for Realization of….”)</STRONG></SPAN><BR>?Detailed implementations of each step in your framework<BR><STRONG><SPAN style="COLOR: #0000cd">?List complications of implementing a certain idea and how you get around them</SPAN></STRONG><BR>&nbsp;-if some complications are important and general, you may move them to the framework </SPAN><SPAN style="FONT-SIZE: 10pt">section.</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="FONT-SIZE: 12pt">Performance Evaluation/Comparison</SPAN></STRONG><BR>experiment writing structure:<BR>?<STRONG><SPAN style="COLOR: #0000cd">Hypotheses/Questions to be answered</SPAN></STRONG><BR>?Performance metrics you use to answer these questions (higher better?)<BR>?Experiment setup<BR>?Experimental results<BR><STRONG><SPAN style="COLOR: #0000cd">&nbsp;-Illustrate how to read your table/diagrams (columns, x/yaxis, etc.)</SPAN></STRONG><BR>&nbsp;-Explain what does the curve or data mean, e.g., “We observed that …”, “The experimental </SPAN><SPAN style="FONT-SIZE: 10pt">results show …”<BR><STRONG><SPAN style="COLOR: #0000cd">&nbsp;-Summarize your findings, remember to get back to answer the hypotheses and questions; it is </SPAN></STRONG></SPAN><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="COLOR: #0000cd">ok to have an undecisive or negative answer based on the experimental results</SPAN></STRONG><BR>&nbsp;-Optional: discussion subsection; or you can put it as a separatesection</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="FONT-SIZE: 12pt">Discussion</SPAN></STRONG><BR><STRONG><SPAN style="COLOR: #0000cd">?Limitations and issues your approach/implementation currently cannot address</SPAN></STRONG><BR><STRONG><SPAN style="COLOR: #0000cd">&nbsp;-Optional: how are you going to address them in future work</SPAN></STRONG><BR>?scope of your approach<BR><STRONG><SPAN style="COLOR: #0000cd">?It is often a good idea to list (obvious) limitations and discuss possible solutions for </SPAN></STRONG></SPAN><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="COLOR: #0000cd">them rather than hiding them</SPAN></STRONG><BR>&nbsp;-Reviewers can often identify obvious limitations even if you don’t state them; then they </SPAN><SPAN style="FONT-SIZE: 10pt">will criticize your work on these limitations (you often don’t have a rebuttal against these </SPAN><SPAN style="FONT-SIZE: 10pt">criticisms in conference reviews).<BR>&nbsp;-If your paper discusses these obvious limitations as well as their potential solutions, the </SPAN><SPAN style="FONT-SIZE: 10pt">situation can be alleviated<BR>?Possible applications of your approach that you haven’t validated but are convincingly </SPAN><SPAN style="FONT-SIZE: 10pt">feasible or effective.</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt"><STRONG><SPAN style="FONT-SIZE: 12pt">Conclusions (and Future Work)</SPAN></STRONG><BR>?Often easy to write conclusions<BR>&nbsp;-nothing here should surprise readers; simply summarize your contributions and findings<BR>&nbsp;-In the introduction, “We propose a new approach …”vs. In the conclusions, “We have proposed a new approach …”<BR>?You can state the broader impacts of your approach<BR>?You can optionally describe limitations here if you don’t have a discussion section for them and propose future work</SPAN></P>]]></description>
<author>erictb</author>
<pubDate>2007-11-18 16:53:00</pubDate>
</item>
<item>
<title><![CDATA[防御DDoS项目阶段性总结]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2007/1781206.shtml</link>
<description><![CDATA[<DIV><SPAN style="FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 今天上午，实验室老师对我们项目中的基于Octeon处理器的防御DDoS系统进行测试检查。就此，我的任务算到一个段落，剩下的是专利工作和项目组协调，组织的工作。<BR>&nbsp; 回想去年12月15日，Octeon北京方面进行技术培训到现在已经整整半年。项目组的工作：</SPAN></DIV>
<DIV><BR><SPAN style="FONT-SIZE: 10pt">&nbsp; 06年12月--07年1月：熟悉硬件，概要设计说明书初稿<BR>&nbsp; 07年01月--寒假&nbsp;&nbsp; ：系统各模块接口设计<BR>&nbsp; 07年03月--07年5月：系统的代码编写，单元测试。<BR>&nbsp; 07年05月--现在&nbsp;&nbsp; ：重写概要设计说明书，详细设计说明书，系统测试。</SPAN></DIV>
<DIV><SPAN style="FONT-SIZE: 10pt">&nbsp; 注：硬件上C代码1.1万行，监控管理中心C代码2000行，PHP代码6400行，代码总计2万行。</SPAN></DIV>
<P><SPAN style="FONT-SIZE: 10pt">&nbsp; 项目组的工作难点：<BR>&nbsp; 1，硬件上开发系统，项目组中没有一个人有相关开发经验。<BR>&nbsp; 2，硬件上的一些问题，只有在硬件资料中或者通过做实验找答案，网络上，书本上根本没有相关参考资料。<BR>&nbsp; 3，实验室在DDoS检测和防御方面上，没有相关的经验积累。</SPAN></P>
<P><BR><SPAN style="FONT-SIZE: 10pt">&nbsp; 我的工作：<BR>&nbsp; 1，项目组的协调，带头工作。个人感觉这个任务是让人心累的工作。<BR>&nbsp; 2，系统整体框架的设计，以及在硬件上程序框架的设计。<BR>&nbsp; 3，完成‘静态特征防御’，‘异常检测’，‘SYN Flood防御’，‘数据挖掘’模块的设计和代码编写。&nbsp; <BR>&nbsp; 4，协助管理项目中另一个项目‘南山之桥’，辅助设计该项目的框架，以及其中‘数据挖掘’模块设计和代码编写。</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt">&nbsp; 这个项目总的来说对我的锻炼很大<BR>&nbsp; 1，发现自己的工作作风有了变化。<BR>&nbsp; 2，项目组有10余人，体会到项目管理一些需要注意的地方。<BR>&nbsp; 3，知道如何与组员进行沟通，使项目能顺利进行。<BR>&nbsp; 4，学会如何与技术支持，产品经理，技术服务人员打交道。<BR>&nbsp; 5，学会如何与老师沟通，把老师的想法能更有效地贯彻到项目中。</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt">&nbsp; 也有做的不好的地方：<BR>&nbsp; 1，项目组中有时候有效的沟通还是偏少了些。<BR>&nbsp; 2，有些时候，月计划的执行力不够，任务完成情况有滞后。<BR>&nbsp; 3，发现项目组要形成项目组的特有的‘团队文化’是件比较难的事情，有些理念性的东西，很难被每一个项目组人员接受。<BR>&nbsp; 4，实验室里面一些特有的东西，使实验室项目的管理工作不太好做。</SPAN></P>
<DIV><SPAN style="FONT-SIZE: 10pt">&nbsp; 项目管理的经验和教训：<BR>&nbsp; 1，不能事必恭亲，以责任落实到每一个人头上。<BR>&nbsp; 2，制定明确的计划，一定要让组员明确下一步应该做什么。否则就是项目组组长的问题。<BR>&nbsp; 3，项目组中的每一个人都有他的特长和弱项，既然在一个团队，就应该发挥他的长处，调动其积极性，使他在他的长处上多为项目组做贡献，而不应该让他做他并不擅长的事情。<BR>&nbsp; 4，调动组员的积极性并是一件好办的事情，要讲究一定的方法和技巧。<BR>&nbsp; 5，要充分体谅组员的难处，在适当的情况下，给予充分理解和适当的帮助。<BR>&nbsp; 6，如何更好地制定项目组的计划，掌握好制定计划的粒度（什么计划可以做的很细致，什么计划可以较宏观的制定），要充分考虑组员的计划执行力。</SPAN></DIV>
<DIV><SPAN style="FONT-SIZE: 10pt"></SPAN>&nbsp;</DIV>
<DIV><SPAN style="FONT-SIZE: 10pt">补充：统计软件Practiline Source Code Line Counter，可对代码进行统计。</SPAN></DIV>]]></description>
<author>erictb</author>
<pubDate>2007-6-27 17:38:00</pubDate>
</item>
<item>
<title><![CDATA[cj60lib库的介绍]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2007/1632453.shtml</link>
<description><![CDATA[<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><PRE><SPAN style="FONT-SIZE: 10pt">刚才在网上看到一个关于界面开发的东西,叫cj60lib,下载来看,它是对MFC 一些界面类的扩展,以达</SPAN></PRE></DIV></BLOCKQUOTE><PRE dir=ltr><SPAN style="FONT-SIZE: 10pt">到界面开发的快速性.这个<STRONG>cj60libsrc</STRONG>支持<STRONG>Use MFC in a static library </STRONG>和 <STRONG>Use MFC in a shared</STRONG></SPAN></PRE><PRE dir=ltr><SPAN style="http://www.blog.edu.cn/FONT-SIZE: 10pt"><STRONG>DLL ,</STRONG>从而产生两个 CJ60StaticLibd.lib 和 CJ60Libd.lib, CJ60Libd.dll,调用时候只需要加入</SPAN></PRE><PRE dir=ltr><SPAN style="FONT-SIZE: 10pt; COLOR: #808000"><EM>#include &lt;CJ60Lib.h&gt; </EM><SPAN style="FONT-SIZE: 10pt; COLOR: #000000">和相应扩展类的头文件即可,非常方便.扩展类如下图:</SPAN></SPAN></PRE><PRE dir=ltr><SPAN style="COLOR: #808000"><SPAN style="COLOR: #000000"><IMG alt="" src="http://www.blog.edu.cn/UploadFiles/2007-1/128636019.gif" border=0></SPAN></SPAN></PRE>]]></description>
<author>erictb</author>
<pubDate>2007-1-28 0:02:00</pubDate>
</item>
<item>
<title><![CDATA[samba,nfs 配置]]></title>
<link>http://blog.edu.cn/user1/13760/archives/2006/1540427.shtml</link>
<description><![CDATA[<P>&nbsp;&nbsp; 这两天配置samba, nfs服务，老是是出问题。是一些细节的地方没有设置好。</P>
<P>1、配置samba服务<BR>&nbsp;&nbsp; <BR>&nbsp;&nbsp; smbd:smb服务器的主要程序，处理来自客户的连接，处理文件<BR>&nbsp;&nbsp; nmdb: NetBios名称服务器（name server）负责帮助客户端找出服务器位置</P>
<P>&nbsp;&nbsp; 可以用ntsysv ，系统服务设置samba服务启动<BR>&nbsp;&nbsp; chkconfig --level 5 smb on :系统运行在级别5的时候会自动启动samba<BR>&nbsp;&nbsp; chkconfig --list | grep smb :查看系统各个级别，是否启动了samba服务</P>
<P>&nbsp;&nbsp; 首先，设置/etc/services, 要使以netbios-开头的记录都执行，即去掉;注释。<BR>&nbsp;&nbsp; 设置/etc/samba/lmhosts文件，添加 ip地址 机器名,例如： 202.115.30.194 nsitb<BR>&nbsp;&nbsp; 设置/etc/samba/smb.conf<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;workgroup = MSHOME (这里要和windows系统中的工作组一致)<BR>&nbsp;server string = TongBin's Samba Server<BR>&nbsp;security = user (这里可以设置为share, user, server, domain其中一个)<BR>&nbsp;share: windows访问samba服务不需要提供用户名和密码<BR>&nbsp;user:windows访问samba服务需要提供用户名和密码,在这里使用该方式，所以需要encrypt passwords 和 smb passwd file&nbsp; 选项<BR>&nbsp;&nbsp; &nbsp;encrypt passwords = yes (是否设置用户密码，是否用加密方式加密密码，由于windows已使用加密方式，所以一般使用)<BR>&nbsp;&nbsp; &nbsp;smb passwd file = /etc/samba/smbpasswd （samba服务所使用的密码文件）<BR>&nbsp;interfaces = 202.115.30.194/24 (samba服务器的网络接口)<BR>&nbsp;<BR>&nbsp;设置共享目录<BR>&nbsp;#this is samba text\<BR>&nbsp;[projectshare]<BR>&nbsp;comment = project's samba share<BR>&nbsp;path = /ddos/pbak<BR>&nbsp;public = yes<BR>&nbsp;writable = no</P>
<P>&nbsp;用testparm 检查&nbsp;/etc/samba/smb.conf语法错误</P>
<P>&nbsp;建立samba密码文件/etc/samba/smbpasswd<BR>&nbsp;首先在linux系统上新建一个访问smb服务的用户名<BR>&nbsp;cat /etc/passwd|mksmbpasswd.sh &gt; /etc/samba/smbpasswd ：将linux系统的用户导入到smb<BR>&nbsp;smbpasswd &lt;用户名&gt; ：重新设置用户的密码</P>
<P>&nbsp;启动smb:/etc/rc.d/init.d/smb start<BR>&nbsp;重新启动smb:/etc/rc.d/init.d/smb restart<BR>&nbsp;查看smb状态:/etc/rc.d/init.d/smb status</P>
<P>1、配置nfs服务</P>
<P>&nbsp;&nbsp; &nbsp;可以用ntsysv ，系统服务设置nfs服务启动<BR>&nbsp;&nbsp; &nbsp;chkconfig --level 5 nfs on :系统运行在级别5的时候会自动启动samba<BR>&nbsp;&nbsp; &nbsp;chkconfig --list | grep nfs :查看系统各个级别，是否启动了samba服务</P>
<P>&nbsp;启动nfs:/etc/rc.d/init.d/nfs start<BR>&nbsp;重新启动nfs:/etc/rc.d/init.d/nfs restart<BR>&nbsp;查看nfs状态:/etc/rc.d/init.d/smb status</P>
<P>&nbsp;在进行nfs通信的时候，需要用到rpc调用，同时需要启动portmap服务<BR>&nbsp;rpcinfo -p 202.115.30.194 ：查看portmap服务是否正常运行<BR>&nbsp;<BR>&nbsp;设置/etc/exports<BR>&nbsp;例如：<BR>&nbsp;/ddos 202.115.30.0/255.255.255.0(ro) <BR>&nbsp;注意：()前后不能有空格<BR>&nbsp;<BR>&nbsp;必须用exportfs -rv命令检查/etc/exports，同时，这个命令将/etc/exports文件复制到/var/lib/nfs/etab，当客户端需要访问共享目录的时，mountd就会检查/var/lib/nfs/etab</P>
<P>&nbsp;访问nfs服务<BR>&nbsp;mkdir /mnt/ddos<BR>&nbsp;mount 202.115.30.194:/ddos /mnt/ddos<BR>&nbsp;umount /mnt/ddos</P>]]></description>
<author>erictb</author>
<pubDate>2006-11-1 9:21:00</pubDate>
</item>

</channel>
</rss>