gnome-control-center    # 打开以下所有配置到界面

gnome-appearance-properties    # 设置桌面显示到外观和字体等
gnome-calculator    # 计算器
gnome-help        # 帮助
gnome-keybinding-properties    # 快捷键设置
gnome-network-properties    # 设置代理服务器
gnome-panel-screenshot    # 截屏，最好是用 -a 参数，进行区域截屏
gnome-power-preferences    # 电源设置
gnome-screenshot    # 同 gnome-panel-screenshot
gnome-search-tool    # 文件搜索工具
gnome-system-log    # 集中显示系统中的一些 log
gnome-system-monitor    # 相当于 Windows 中的任务管理器
gnome-text-editor    # 就是 Gedit

NIS - Network Information System，又叫 YP - Yellow Pages。

Server 端

首先安装 ypserv

1. 设置 NIS Domain name
# vi /etc/sysconfig/network
NISDOMAIN=DomainName
2. 将现有的 passwd, group 和 shadow 文件转化为 NIS DBM 格式。
/usr/lib/yp/ypinit -m
3. 之后如果添加了或删除用户，用户组，必须更新 NIS 数据库
make -C /var/yp
可以设置一个 cron job 定期更新
4. 启动服务
service ypserv start


Client 端

安装 yp-tools ypbind

1. 设置 NIS Domain name
# vi /etc/sysconfig/network
NISDOMAIN=DomainName
2. 配置
# vi /etc/yp.conf
domain domainname server somehost
# vi /etc/nsswitch.conf        # 修改顺序
passwd:     nis files nisplus
shadow:     nis files nisplus
group:      nis files nisplus

3. 删掉 Client 上的本地用户
4. service ypbind start    # 启动 NIS Client 服务

NetBackup Master Server Version: 6.5.3

今天在尝试通过 BMR 方式恢复系统时，在创建引导光盘时，出现：“Failed to update the shared resource tree information in the database”的报错。

#####
# 解决思路
##########################

BMR database 出错，一个方法是重建 database，这样做会导致清空当前的 BMR 信息，但是服务器在客户端下次发起 BMR 备份时会更新 BMR 信息。

#####
# 完整解决过程
######################

今天我的笔记本上的 IE7 总是 Crash，解决方法：

iexplore.exe -extoff

之后卸载不必要的 IE add-ons。

#####
# 如何手工下载最新的 Windows Defender 定义库
###############################################

Windows Defender 是微软发布的防间谍软件的免费工具，今天初步使用了下，在我机器上找出了 CNNIC 这个恶心的东西，删无豁！

32-bit (x86-based) of Windows
访问 http://go.microsoft.com/fwlink/?linkid=70631，会有下载的提示，安贞焕文件为：Mpas-fe.exe，可以使用 -q 参数，作用是 quite 模式。

64-bit version of Windows
访问 http://go.microsoft.com/fwlink/?linkid=70632

Itanium-based versions of Windows
访问 http://go.microsoft.com/fwlink/?linkid=70633

Windows Defender 与其他 Microsoft 反间谍软件和防病毒技术的比较
http://www.microsoft.com/china/athome/security/spyware/software/about/productcomparisons.mspx

Windows Defender 下载
http://www.microsoft.com/china/athome/security/spyware/software/default.mspx

来源：http://boincfaq.mundayweb.com/index.php?language=1&view=176

通过 $ less /proc/cpuinfo 可以查看 CPU 的一些参数，具体的参数解释如下： - 3DNOW
A multimedia extension created by AMD for its processors, based on MMX.

- 3DNOWEXT
3DNOW Extensions. Could also pertain to AMD's 3DNow! Enhanced/Extended.

- ACPI
Advanced Configuration and Power Interface.

- APIC
Advanced Programmable Interrupt Controller.

- CID+
Most probaly this stands for Certified Interconnect Designer. (A certification for experienced PCB design professionals.)

- CLFSH/CLFlush
Cache Line Flush.

- CMOV
Conditional Move/Compare Instruction.

- CMP_Legacy
Register showing the CPU is not Hyper-Threading capable.

- Constant_TSC
on Intel P-4s, the TSC runs with constant frequency independent of cpu frequency when EST is used.

- CR8Legacy
??

- CX8
CMPXCHG8B Instruction. (Compare and exchange 8 bytes. Also known as f00f (pronounced "foof"), an abbreviation of f0 0f c7 c8, is the hexadecimal encoding of an instruction that exhibits a design flaw in the majority of Intel Pentium, Pentium MMX, and Pentium OverDrive processors).

- CX16
CMPXCHG16B Instruction. (CMPXCHG16B allows for atomic operations on 128-bit double quadword (or oword) data types. This is useful for high resolution counters that could be updated by multiple processors (or cores). Without CMPXCHG16B the only way to perform such an operation is by using a critical section.)

- DE
Debugging Extensions.

- DS
Debug Store.

- DS_CPL
CPL qualified Debug Store.

- DTS
Digital Thermal Sensor.
or
Debug Trace Store.

- EM64T
Intel Extended Memory 64 Technology. Intel's derivative of AMD's 64bit CPU technology. Uses 64bit CPU registers and 64bit physical RAM addresses (page addresses) to support up to 1 tebibyte of RAM, which can later be extended (through future processor revisions) to 1 Pebibyte.

- EIST
Enhanced Intel SpeedStep.

- FID
Frequency IDentifier.

- FPU
x87 Floating Point Unit built into the CPU. This is where most mathematically intense calculations take place. Used to be a separate chip on the 80486SX and earlier (called the 80487 or 80387, etc. 80486DX had FPU built-in as well). All Pentium CPUs and later have this functionality built in.

- FXSR
FXSAVE/FXRSTOR. (The FXSAVE instruction writes the current state of the x87 FPU, MMX technology, Streaming SIMD Extensions, and Streaming SIMD Extensions 2 data, control, and status registers to the destination operand. The destination is a 512-byte memory location. FXRSTOR will restore the state saves).

- FXSR_OPT
??

- HT
Hyper-Transport.

- HTT
Hyper-Threading Technology. The ability to use one physical CPU as two separate logical CPUs by taking advantage of unused CPU registers during typical operation in an attempt to make the CPU more efficient. If multiple programs use the same registers by both logical CPUs, Hyper-threading can actually be known to slow down overall performance in some cases.

- LAHF_LM
Load Flags into AH Register, Long Mode.

- LM
Long Mode. (64bit Extensions).

- MCA
Machine Check Architecture.

- MCE
Machine Check Exception.

- MMX
It is rumoured to stand for MultiMedia eXtension or Multiple Math or Matrix Math eXtension, but officially it is a meaningless acronym trademarked by Intel.

- MMXEXT
MMX Extensions.

- MNI
Modular Network Interface.
or
Merom New Instruction. See SSSE3.

- MON (MONITOR)
CPU Monitor.

- MSR
RDMSR and WRMSR Support.

- MTRR
Memory Type Range Register.

- NNI
Nehalem New Instructions (NNI). See SSE4.

- NX
No eXecute. (the ability to not run code.)

- PAE
Physical Address Extensions. PAE is the added ability of the IA32 processor to address more than 4 GB of physical memory using Intel's 36bit page addresses instead of the standard 32bit page addresses to access a total of 64gibibytes of RAM. Most AMD chips support PAE as well.

PAE is the second method supported to access memory above 4 GB (PSE36 being the first); this method has been widely implemented. PAE maps up to 64 GB of physical memory into a 32-bit (4 GB) virtual address space using either 4-KB or 2-MB pages. The Page directories and the page tables are extended to 8 byte formats, allowing the extension of the base addresses of page tables and page frames to 24 bits (from 20 bits). This is where the extra four bits are introduced to complete the 36-bit physical address.

Windows supports PAE with 4-KB pages. PAE also supports a mode where 2-MB pages are supported. Many of the UNIX operating systems rely on the 2 MB-page mode. The address translation is done without the use of page tables (the PDE supplies the page frame address directly).

- PAT
Page Attribute Table.

- PBE
Pending Break Encoding.

- PGE
PTE Global Bit.

- PNI
Prescott New Instruction. This was the codename for SSE3 before it was released on the Intel Prescott processor (which was later added to the Pentium 4 family name).

- PSE
Page Size Extensions. (See PSE36).

- PSE36
Page Size Extensions 36. IA-32 supports two methods to access memory above 4 GB (32 bits). PSE (Page Size Extension) was the first method, which shipped with the Pentium II. This method offers a compatibility advantage because it kept the PTE (page table entry) size of 4 bytes. However, the only practical implementation of this is through a driver. This approach suffers from significant performance limitations, due to a buffer copy operation necessary for reading and writing above 4 GB. PSE mode is used in the PSE 36 RAM disk usage model.

PSE uses a standard 1K directory and no page tables to extend the page size 4-MB (eliminating one level of indirection for that mode). The Page Directory Entries (PDE) contains 14 bits of address, and when combined with the 22-bit byte index, yields the 36 bits of extended physical address. Both 4-KB and 4-MB pages are simultaneously supported below 4 GB, with the 4-KB pages supported in the standard way.

Note that pages located above 4 GB must use PSE mode (with 4-MB page sizes).

- SEP
SYSENTER and SYSEXIT.

- SS
Self-Snoop.

- SSE
Streaming SIMD Extensions. (70 new Single Instruction, Multiple Data instructions built in in the CPU.) Debuted with the Intel Pentium III processor. AMD's first chip to support SSE was the Athlon XP.

- SSE2
Streaming SIMD Extensions 2. (An additional 144 SIMDs.) Debuted with the Intel Pentium 4 processor. AMD's first chip to support SSE2 was the Athlon 64.

- SSE3
Streaming SIMD Extensions 3. (An additional 13 instructions) Debuted with the "Prescott" revision Intel Pentium 4 processors. AMD's first chip to support SSE3 was the Athlon 64 "Venice" revision.

- SSSE3
Supplemental Streaming SIMD Extension 3. (SSSE3 contains 16 new discrete instructions over SSE3. Each can act on 64-bit MMX or 128-bit XMM registers. Therefore, Intel's materials refer to 32 new instructions.) Debuted on Intel Core 2 Duo processors. No AMD chip supports SSSE3 yet.

- SSE4
Streaming SIMD Extentions 4. Future Intel SSE revision adding 50 new instructions which will debut on Intel's upcoming "Nehalem" processor in 2008. Also known as "Nehalem New Instructions (NNI)".

- SVM
Secure Virtual Machine. (AMD's virtualization extensions to the 64-bit x86 architecture.)

- SYSCALL
System Call. (the mechanism used by an application program to request service from the operating system.)

- TNI
Tejas New Instruction. See SSSE3.

- TM
Thermal Monitor.

- TM2
Thermal Monitor 2.

- TPR
Task Priority Register.

- TS
Thermal Sensor.

- TSC
Time Stamp Counter. (is used whenever possible to further improve the accuracy of the speed measurement.)

- TTP
Thermal Trip.

- VID
Voltage IDentifier.

- VME
Virtual-8086 Mode Enhancement.

- VMX
An AltiVec floating point and integer SIMD instruction set. (Used by Apple, IBM, Motorola and Freescale Semiconductor.)

- XTPR
TPR register chipset update control messenger. Part of the APIC code.

#####
# 使用 yum 管理软件
#################

原文：http://mirror.centos.org/centos/4/docs/html/yum/index.html
适用于 CentOS

su -c 'yum install tsclient'
su -c 'yum groupinstall "MySQL Database"'

su -c 'yum update tsclient'
su -c 'yum groupupdate "MySQL Database"'

su -c 'yum remove tsclient'
su -c 'yum groupremove "MySQL Database"'

su -c 'yum list tsclient'
su -c 'yum list tsclient-0.132'

su -c 'yum search PalmPilot' # search 参数会查询 names, descriptions, summaries and listed package maintainers.
su -c 'yum provides libneon' # provides 参数会查询 packages 包含的文件以及 software 提供的功能。

如果使用 wildcards，需要使用在 wildcards 前使用 \，如"\?", "\*"，
su -c 'yum list tsc\*'

注意：
su -c 'yum update' # 会升级系统中所有软件到最新

如何让 yum 每天自动升级系统？
su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'
这一句的作用是通过 chkconfig 设置 yum 在运行级别 345 时自动启动，然后通过 service yum start 立刻运行 yum，这时会调用 /etc/rc.d/init.d/yum，继而调用 /etc/cron.daily/yum.cron，这将启动 cron 服务在每天早上 4 点自动运行 yum。

关于 yum 使用代理：http://mirror.centos.org/centos/4/docs/html/yum/sn-yum-proxy-server.html
By default, yum accesses network repositories with HTTP. All yum HTTP operations use HTTP/1.1, and are compatible with web proxy servers that support this standard. You may also access FTP repositories, and configure yum to use an FTP proxy server. The squid package provides a proxy service for both HTTP/1.1 and FTP connections.

举例：
# vi /etc/yum.conf # 在 yum.conf 中配置将试这台机器的所有用户都使用这个配置。
# The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
# The account details for yum connections
proxy_username=yum-user
proxy_password=qwerty

# vi ~/.bash_profile # 修改用户的 shell 配置文件，可以让 yum 的代理配置只适用于这个用户
# The Web proxy server, with the username and password for this account
http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
export http_proxy

SSH 登陆到服务器service console 后，切换到 root 用户，

[root@blade13 root]# esxcfg-firewall --enableService ntpClient # 在防火墙上设置允许
     # 这一步只有 ESX 3.0 以上版本才需要
[root@blade13 root]# cp /etc/ntp.conf /etc/ntp.conf.bk  # 备份 ntp.conf 文件
[root@blade13 root]# vi /etc/ntp.conf
server 172.32.226.1   # 在文件的末尾添加时间服务器，可以是 IP，
server server2.examplentp.org  # 也可以是 DNS 名称形式，如果写为 DNS 名称形式，
server server3.examplentp.org  # 最好手工添加到 host 文件中
[root@blade13 root]# cp /etc/ntp/step-tickers /etc/ntp/step-tickers.bk # 备份 step-tickers 文件
[root@blade13 root]# vi /etc/ntp/step-tickers
172.32.226.1  # 添加 NTP server，每行一个。可以是 IP 形式
server2.examplentp.org # 也可以是 DNS 名称形式
server3.examplentp.org
[root@blade13 root]# service ntpd restart # 重启 ntpd 服务
Shutting down ntpd:                                        [FAILED]
ntpd: Synchronizing with time server:                      [  OK  ]
Starting ntpd:                                             [  OK  ]
[root@blade13 root]# chkconfig --level 345 ntpd on # 设置每次开机自动启动 ntpd
[root@blade13 root]# hwclock --systohc  # 设置主板 BIOS 时间和当前 ntp 时间同步
[root@blade13 root]# date  # 查看当前时间
Wed Mar 26 14:13:36 CST 2008

2008年3月，微软新推出了 ConfigMgr 2007 的认证考试，对应 Exam 70-401，通过考试将获得 MCTS 认证 （Technical Specialist）。

官方网址：http://www.microsoft.com/learning/exams/70-401.mspx

Microsoft online resources

各知识点比重：

Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the exam, regardless of its format.

ConfigMgr 2007 对应认证考试为 70-401，通过认证考试后获得 MCTS 认证。

原文：http://www.microsoft.com/learning/syllabi/en-us/6451afinal.mspx

Prerequisites
Before attending this course, students must have:
• A base-level understanding of Systems Management Server 2003.
• System Administrator–level working knowledge of:
• Deployment, configuration, and troubleshooting for Windows-based personal computers
• TCP/IP networking
• SQL Server
• Active Directory
• Basic Public Key Infrastructure concepts  

Five days 课程大纲

Module 1: Overview of Configuration Manager 2007

This module provides an overview of Configuration Manager 2007 features. It also provides an overview of the Configuration Manager site architecture and clients.

Lessons

After completing this module, students will be able to:

Module 2: Planning and Deploying a Single-Site Architecture

This module explains how to prepare for and deploy a Configuration Manager site. It also describes how to discover resources and how to upgrade an SMS 2003 site to Configuration Manager 2007.

Lessons

Lab A: Deploying a Configuration Manager Site Server

Lab B: Managing Users and Configuring Boundaries and Discovery Methods

After completing this module, students will be able to:

Module 3: Planning and Deploying Configuration Manager 2007 Clients

This module explains how to prepare for and deploy Configuration Manager clients. It also describes how to manage client installations and how to troubleshoot client deployment issues.

Lessons

Lab A: Deploying Configuration Manager Clients

Lab B: Reviewing Client Deployment

After completing this module, students will be able to:

Module 4: Collecting Inventory and Metering Software Usage

This module explains how to collect and manage hardware and software inventory. It also describes how to configure software metering.

Lessons

Lab A: Collecting Inventory

Lab B: Configuring Software Metering

After completing this module, students will be able to:

Module 5: Querying and Reporting Data

This module explains how to create and run queries and reports. It also describes how to create and run dashboards.

Lessons

Lab A: Creating Queries

Lab B: Creating a Reporting Point

Lab C: Creating Reports

Lab D: Creating a Dashboard

After completing this module, students will be able to:

Module 6: Preparing for and Managing Software Distribution

This module explains how to configure and manage software distribution. It also describes how to monitor and troubleshoot software distribution.

Lessons

Lab A: Preparing a Site for Software Distribution

Lab B: Deploying an Application Using Software Distribution

After completing this module, students will be able to:

Module 7: Deploying Operating Systems Using Configuration Manager 2007

This module explains how to deploy operating systems using Configuration Manager. It also describes how to configure operating system deployments using PXE.

Lessons

Lab A: Capturing a Reference Computer Using Configuration Manager 2007

Lab B: Deploying Operating Systems Using PXE

After completing this module, students will be able to:

Module 8: Deploying and Managing Software Updates

This module explains how to prepare for and manage software updates in Configuration Manager. It also describes how to monitor and troubleshoot software updates.

Lessons

Lab: Deploying and Managing Software Updates

After completing this module, students will be able to:

Module 9: Working with Desired Configuration Management in Configuration Manager 2007

This module explains how to configure desired configuration management in Configuration Manager. It also describes how to view compliance results.

Lessons

Lab: Configuring Desired Configuration Management

After completing this module, students will be able to:

Module 10: Using Remote Tools and Wake On LAN Features

This module explains how to work with Configuration Manager remote tools. It also describes how to configure and monitor Wake On LAN.

Lessons

Lab A: Configuring and Using Remote Tools

Lab B: Configuring and Using Wake On LAN

After completing this module, students will be able to:

Module 11: Managing Mobile Devices Using Configuration Manager 2007

This module provides an overview of mobile device management. It also describes how to configure server and client settings and how to manage mobile devices.

Lessons

Lab A: Configuring the Site Server to Support Mobile Device Management

Lab: Managing Mobile Devices Using Configuration Manager 2007

After completing this module, students will be able to:

Module 12: Maintaining and Troubleshooting Configuration Manager 2007

This module explains how to maintain Configuration Manager 2007 and how to troubleshoot Configuration Manager issues. It also describes how to backup and recover data and how to work with troubleshooting tools.

Lessons

Lab: Maintaining and Troubleshooting a Configuration Manager Site System

After completing this module, students will be able to:

Module 13: Planning and Configuring a Multiple Site Hierarchy

This module explains how to plan and configure a multiple-site hierarchy including installing a secondary site and installing a proxy management point. It also describes how to decommission sites and hierarchies and how to roam in multiple-site hierarchies.

Lessons

Lab A: Planning a Configuration Manager 2007 Hierarchy

Lab B: Installing Secondary Sites and Proxy Management Points

Lab C: Roaming Between Configuration Manager 2007 Sites

After completing this module, students will be able to:

FreeBSD 7.0 发布了，最大的一个特性是增加了对 SUN 的 ZFS 文件系统的支持。Greg Larkin 为我们提供了一个 FreeBSD 7.0 的 VMware image，这样大家就可以无痛体验 FreeBSD 的新特性啦！！都来尝试一下吧！

VMware Image 文件下载地址：http://torrents.sourcehosting.net:10692/torrents/FreeBSD_7.0_VMware.zip.torrent?BA9886D479184512A1B428C3C25AB29FED632BAD

#####
# 原帖如下
##########################

原帖网址：http://blog.sourcehosting.net/2008/03/18/freebsd-70-vmware-image/

FreeBSD 7.0 已经可以支持 ZFS 文件系统了，不过还处于测试阶段，不推荐用于生产环境。

推荐阅读 ZFS 最佳实践指南：http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide

#####
# 手工指定的方式
################################

# ipconfig fxp0 192.168.8.33/24     # 添加网卡ip
# route add default 192.168.8.1     # 添加路由（也可理解为网关）
立即生效，但是重启后失效。

如何重启后仍然保持呢？
# ee /etc/rc.conf
ifconfig_fxp0="inet 192.168.8.8 netmask 255.255.255.0 "  # fxp0 网卡地址和子网掩码
defaultrouter="192.168.8.10"     # 网关地址
hostname="study.nowire.com.cn"     # 机器名
ifconfig_wi0="inet 192.168.8.55  netmask 255.255.255.0"  # wi0 网卡地址，对应无线网卡

修改 /etc/rc.conf 配置之后可以通过如下方式生效：
第一种方法：# sh /etc/rc
第二种方法：# /etc/netstart
第三种方法：重启机器

#####
# DHCP 方式
################################

在 /etc/rc.conf 中添加：
ifconfig_fxp0="DHCP"
需要根据具体情况指定网卡名称。

修改 /etc/rc.conf 配置之后可以通过如下方式生效：
第一种方法：# sh /etc/rc
第二种方法：# /etc/netstart
第三种方法：重启机器

#####
# 关于 DNS 地址的配置
################################

# ee /etc/resolv.conf
nameserver 202.96.209.133
nameserver 202.96.209.5

#####
# 控制网卡的开关
################################

ifconfig fxp0 up
ifconfig fxp0 down

#####
# 路由方面的配置
################################

查看路由
netstat -rn

添加路由(相当于配置gateway)
route add default 192.168.8.1      # 192.168.8.1为网关地址

如果要修改当前路由配置，需要先删除，再新增一条，当然如果不是同名的，如不是default的可以直接添加
route delete default 192.168.8.1
route add default 192.168.8.10

#####
# DHCP release
################################

# dhclient -r    Release the current lease and exit the client.

Here's a clip of dhclient from the FreeBSD man pages;
"The client normally doesn't release the current lease as it is not required by the DHCP protocol. Some cable ISPs require their clients to notify the server if they wish to release an assigned IP address. The -r flag explicitly releases the current lease, and once the lease has been released, the client exits."
If you are getting kill: xxxx: No such process This means the dhclient process was already stopped

#####
# 指定 interface 通过 dhcp 获取 IP
################################

# dhclient xl0    Starts the dhclient process for interface xl0

I think its a good idea to specify an interface Otherwise you may notice your /var/log/messages filling up with "dhclient: send_packet: Address family not supported by protocol family"

Here's a clip of dhclient from the FreeBSD man pages;
"If no interface names are specified on the command line dhclient will normally identify all network interfaces, elimininating non-broadcast interfaces if possible, and attempt to configure each interface."

#####
# 指定某个 interface 在通过 DHCP 获取不成功的时候，限定一个固定 IP
################################

方法：
在 /etc/dhclient.conf 中添加
alias {
interface "xl0";
fixed-address 192.168.42.40;
option subnet-mask 255.255.255.0;
}

举例：
# ee /etc/dhclient.conf

# $FreeBSD: src/etc/dhclient.conf,v 1.2.2.1 2001/12/14 11:44:31 rwatson Exp $
#
#    This file is required by the ISC DHCP client.
#    See ``man 5 dhclient.conf'' for details.
#
#    In most cases an empty file is sufficient for most people as the
#    defaults are usually fine.
#
alias {
interface "xl0";
fixed-address 192.168.42.40;
option subnet-mask 255.255.255.0;
}

上例的作用是，当 dhclient 不能通过 DHCP server 获取 IP 时，则使用 192.168.42.40 这个固定 IP。