This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
build:basics [2005/07/30 14:19] 206.197.251.61 |
build:basics [2010/11/13 13:46] (current) SLUUG Administration |
||
---|---|---|---|
Line 7: | Line 7: | ||
===== Systems ===== | ===== Systems ===== | ||
+ | We've got 2 ProLiant 6400R systems. They're pretty substantial. See the [[hardware]] page for full details. | ||
+ | The primary system is named **bud**. It will likely host most of the production services. The secondary system is named **budlight**. The systems have equivalent specs, except that **bud** has a second (currently unused) NIC. | ||
+ | |||
+ | We have a history of naming our systems after Anheuser-Busch products. I (Craig) have no idea when or why that started, but it has nothing to do with the fact that I've worked at A-B for the past 4 years --- SLUUG has been using the names before I was a SLUUG member, and before I ever worked at A-B. Of course, I did push to keep the tradition and selected the names of these 2 systems... ;-) | ||
===== Old New Systems ===== | ===== Old New Systems ===== | ||
- | The primary (larger) system was to be called **bud**. Unfortunately, we weren't able to get Debian to play nice with the hardware. Our secondary system is called **budlight**. Currently, that's our only system, so it's effectively the primary. | + | We originally tried using a Compaq ProLiant 5500R for **bud**. Unfortunately, we weren't able to get Debian to play nice with the hardware. The original **budlight** was a loaner system, courtesy of Craig Buchek. |
- | + | ||
- | **Budlight** is actually a loaner system, courtesy of Craig Buchek. We're not sure what we'll replace it with at this point. We may just buy a replacement system for Craig and use the current system. We may build new systems from components, or we may buy a used server off eBay. | + | |
- | + | ||
- | We have a history of naming our systems after Anheuser-Busch products. I (Craig) have no idea when or why that started, but it has nothing to do with the fact that I've worked at A-B for the past 4 years --- SLUUG has been using the names before I was a SLUUG member, and before I ever worked at A-B. Of course, I did push to keep the tradition and selected the names of these 2 systems... ;-) | + | |
===== Decision Making ===== | ===== Decision Making ===== | ||
Line 26: | Line 26: | ||
* Access will be granted by way of //sudo// commands | * Access will be granted by way of //sudo// commands | ||
* **Please do not post any passwords to the wiki** | * **Please do not post any passwords to the wiki** | ||
- | |||
===== Debian ===== | ===== Debian ===== | ||
Line 32: | Line 31: | ||
We chose Debian, because most of our members felt that Debian was most appropriate for a server OS. We ran several polls at our meetings over the previous several months. Debian was the clear leader in recommended server-based Linux distributions, and was also the most familiar Linux distro to our members. In fact, it was the most familiar of all UNIX / POSIX systems among our users. Even many of us who are not familiar with Debian believed that it was the appropriate choice for our group. | We chose Debian, because most of our members felt that Debian was most appropriate for a server OS. We ran several polls at our meetings over the previous several months. Debian was the clear leader in recommended server-based Linux distributions, and was also the most familiar Linux distro to our members. In fact, it was the most familiar of all UNIX / POSIX systems among our users. Even many of us who are not familiar with Debian believed that it was the appropriate choice for our group. | ||
- | We chose to go with Debian 3.1 (sarge) even though it has not yet been released. We installed a release candidate dated from late January 2005. Release seems to be pretty close, so it should be fairly stable. We felt that Debian 3.0 was too old for us to install at this point in time, as we'd then want to upgrade to 3.1 shortly after. | + | On our test/development system, we chose to go with Debian 3.1 (sarge) even though it had not yet been released. We installed a release candidate dated from late January 2005. Release seemed to be pretty close. We felt that Debian 3.0 was too old for us to install at this point in time, as we'd then want to upgrade to 3.1 shortly after. |
+ | |||
+ | By the time we got our production servers, Debian 3.1 had been out for approximately a month. It seemed like the perfect time to use it. | ||
+ | |||
+ | ==== Debian Idiosyncrasies ==== | ||
+ | |||
+ | Debian does some things differently than other distributions. Here are a few pointers to help those of us not quite so familiar with the Debian way. | ||
+ | |||
+ | * Re-run the installation configuration system: \\ | ||
+ | ''base-config'' | ||
+ | * Search for a package with a given name: \\ | ||
+ | ''apt-cache search //string//'' | ||
+ | * List installed packages: \\ | ||
+ | ''dpkg --list'' | ||
+ | * Show information about a package: \\ | ||
+ | ''apt-cache showpkg //packagename//'' | ||
+ | * Show which installed package owns a given file: \\ | ||
+ | ''dpkg -S __file__'' | ||
+ | * List files that belong to a package: \\ | ||
+ | ''dpkg -L //package//'' | ||
+ | * Enable service to start at boot time: \\ | ||
+ | ''update-rc.d //service// defaults'' | ||
+ | * Disable a service: \\ | ||
+ | ''update-rc.d //service// stop 0 1 2 3 4 5 6'' | ||
+ | * Run a service in runlevels 3 and 4, with (boot-sequence) priority of 20: \\ | ||
+ | ''update-rc.d //service// start 20 3 4 . stop 20 0 1 2 5 6'' | ||
+ | * Make a kernel package: \\ | ||
+ | ''make-kpkg --initrd --revision=2:my.1.0 --rootcmd fakeroot --uc --us //kernel-image//'' | ||
+ | |||
+ | See also [[http://www.shallowsky.com/linux/debnotes.html | Debian Notes]] and the [[http://people.debian.org/~debacle/refcard/refcard-en-lt.pdf | Debian Reference Card]] | ||
===== Documentation ===== | ===== Documentation ===== | ||
Line 46: | Line 74: | ||
# exit | # exit | ||
- | To replay the script use the **replay** command. | + | To replay the script use the **replay** command. |
# replay script.timing script.out | # replay script.timing script.out | ||
- | |||
- | |||
===== Blame ===== | ===== Blame ===== | ||
- | There's plenty of blame to go around. Lots of our members helped out in various ways, including moral support, and just general having fun. | + | There's plenty of blame^H^H^H^H^Hcredit to go around. Lots of our members helped out in various ways, including moral support, and just general having fun. |
- | The following people helped build the development server on 2005-07-30: | + | The following people helped build the development server on 2005-02-19: |
(TODO: Get list of people who helped on 2005-02-19 from Stan.) | (TODO: Get list of people who helped on 2005-02-19 from Stan.) | ||
Line 68: | Line 94: | ||
* Gary Meyer | * Gary Meyer | ||
+ | The following people helped finish building the production servers on 2005-09-10: | ||
+ | |||
+ | (TODO) | ||
+ | |||
+ | The following people helped move the production servers to Primary Networks on 2006-01-16: | ||
+ | |||
+ | * Lee Lammert | ||
+ | * Craig Buchek | ||
+ | * Jeff Muse | ||
+ | * Ted Palmer | ||
+ | * Gary Meyer | ||
+ | |||
+ | The following people met on 2006-03-18 to come up with a migration plan and continue working on adding services: | ||
+ | |||
+ | * Mike Knight | ||
+ | * Fred Smith | ||
+ | * Lee Lammert | ||
+ | * Craig Buchek | ||
+ | * Gary Meyer | ||
+ | * Ed Wehner | ||
+ | * Carl Fitch | ||
+ | * Phil Bunch | ||
+ | * Anthony Lordi | ||
+ | |||
+ | The following people met on 2006-05-20 to work on email, mailing lists, and webmin: | ||
+ | * Lee Lammert | ||
+ | * Craig Buchek | ||
+ | * Stan Reichardt | ||
+ | * Gary Meyer | ||
+ | * Ed Wehner | ||
+ | * Fred Smith | ||
+ | * Anthony Lordi | ||
+ | |||
+ | The following people met on 2010-11-13 to work on RedHook (Possible Bud Light replacement): | ||
+ | * Lee Lammert | ||
+ | * Jeff Muse | ||
+ | * Don Ellis |