Installing Debian with SATA based RAIDLate breaking news (4/05)The newer Debian installers have Raid (and also LVM) working, so this guide should not be needed unless you are transitioning from a standard set up to raid without reinstalling. It might also be helpful if you are debugging a broken raid.Now for 2.6 kernel versionI've read that there will soon be an installer that will do raid
installs and The basic idea was |
常用脚本命令集| 代码: |
| #!/bin/bash if [ $# -ne 2 ]; then fi file=$1 size=$2 if [ ! -f $file ]; then fi #TODO: test if $size is a valid integer filesize=`/bin/ls -l $file | awk '{print $5 |
整合Apache+Tomcat
Tomcat 是Sun和Apache合作, 做出来的JSP Server, 支持Servlet
和JSP.Tomcat本身可以做为Web Server,
当处理静态页面时,Tomcat不如Apache迅速,不象Apache一样可配置,强壮.
Apache做为最流行的Web服务器功能强大,高效,但并不支持JSP及servlet,所以通常的做法是把它们整合起来,让Apache处理静态页
面,而把动态页面的请求交给Tomcat处理,发挥各自的优势.
通过在Apache中加载整合模块和进行设置,Apache就能够根据URL,把不属于自己的请求转给Tomcat.
要让Apache和 Tomcat联合工作,还必需有一个连接器把它们联系起来.Connector对于性能、配置的方便性有很重要的影响,目前大致上有JK1.x,JK2, |
This document should help you get your Hardware running Debian GNU/Linux on Software RAID 1. This was born out of two week's worth of frustration and lack of documentation on this specific combination. I will write this as a step-by-step guide, and point out issues that arise and reasons as we go.
I recommend that you read and re-read the Software RAID HOWTO and Boot + Root + RAID + LILO HOWTO before going any further. I found that these two documents explained enough to get me started. However, using them alone I repeatedly got kernel panics as I tried to mo
(Updated: 2005-05-24)
Instructions for installing a very clean Debian GNU/Linux system that boots from RAID 1, and has RAID 1 or RAID 5 root and data filesystems.
The examples assume two identical harddrives, sda and sdb, on which after a small boot partition, 1 GB is used for swap, 25 GB is used for the root filesystem and everything else is for a big 'data' partition that will hold non-system stuff.
Although I personally prefer /boot to be readonly, this guide doesn't add the ro flag in /etc/fstab, because that'll only lead to complaints about lilo upgrades not going smoothly. (Which is exactly the point of having it readonly in the first place...)
They also assume some specific tools that you may or may not like, and a kernel without module support. This is how I prefer to do things for servers. Please don't try to persuade me to use kernel packages, grub, modules, or whatever.
