DOCSLIB.ORG

Majordomo: How I Manage 17 Mailing Lists Without Answering "-Request" Mail D

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Majordomo: How I Manage 17 Mailing Lists Without Answering Majordomo: How I Manage 17 Mailing Lists Without Answering "-request" Mail D. Brent Chapman – Great Circle Associates ABSTRACT Majordomo is a perl program written to handle routine administration of Internet mailing lists with as little human intervention as possible. Modeled after the Listserv implementations common on BITNET (but unfortunately rare on the Internet), it automates the administration of mailing lists by allowing users to perform the most frequent operations ("subscribe" and "unsubscribe") themselves, while allowing the list owners to either "approve" each of these operations (or initiate them on behalf of a user), or merely monitor them as they are automatically approved. It also automates response to certain other common queries from users, such as "what lists are served by this Majordomo server?", "what is the topic of list ’foobar’?", "who is already on list ’foobar’?", and "which lists managed by this Majordomo server am I already on?". Majordomo allows individual list owners to manage their own lists (subscribe and unsubscribe users, and change the general information message for their list) without any action by the overall Majordomo owner. It serves both "open" lists (where users can add themselves to the list, and the list owner is merely informed of this action) and "closed" lists (where a subscription request from a user generates an approval request from the Majordomo server to the list owner, who can then either approve or ignore the request). Finally, all interactions with Majordomo by both users and list owners take place totally by electronic mail, so users and list owners do not require login access (nor even direct TCP/IP connectivity) to the machine Majordomo is running on, and no special client software is required. Introduction turnaround on their requests) while spending as little time as possible in the long run on administrivia. A Anyone who has ever managed a significant BITNET-style Listserv seemed to be an appropriate electronic mailing list by hand (which is, on the solution, so I started investigating alternatives. Internet at least, the usual method) knows how much time it takes to process the endless requests from Defining the Problem users of the form "please subscribe me to your list", "please unsubscribe me from your list", "please tell The first step was to identify just what func- me about your list", "please tell me if I’m already on tionality I desired. First and foremost, I wanted your list", and so forth. It’s a time-consuming, bor- something that would handle routine "subscribe" and ing, repetitive task; just the sort of thing that’s a per- "unsubscribe" requests automatically, with no human fect candidate to be automated. intervention required for routine requests (though I wanted to give the owner of a given list the option When SAGE (the System Administrators Guild, of passing judgement on all subscription requests, if a USENIX Special Technical Group) was formed, they so desired). Second, I wanted something that the founding members decided to establish over a could easily handle many mailing lists simultane- dozen mailing lists for various purposes (one for the ously; I had 17 to begin with, and I was sure that board of directors, one for each of the 16 initial more would be added as time passed. Third, I working groups, one the chairs of all the working wanted something that could automatically handle groups, and so forth). The USENIX Association other user requests (such as "what lists are avail- volunteered the USENIX.ORG machine as a home able?", "please tell me about list ’foobar’", and for these mailing lists, but didn’t have the staff "which of your lists am I on?") that, while less com- resources to set up and operate the mailing lists. I mon than "subscribe" and "unsubscribe", still occur volunteered to act as Postmaster for SAGE, and han- relatively frequently. dle all the mailing lists. As an independent consul- tant, my schedule is rather erratic, and I don’t have a The first thing I did was look around for suit- company paying my salary while I pursue volunteer able publicly available software that might already work like this; thus, I wished to automate the job as exist, or that might be easily adapted to my needs. much as possible, so that I could provide a high Searches of the common Internet software archives, level of service to the users (including fast queries to the "Archie" anonymous FTP indexing 1992 LISA VI – October 19-23, 1992 – Long Beach, CA 135 Majordomo: How I Manage 17 Mailing Lists ... Chapman service, and email to certain acquaintances who I "majordomo", which the dictionary defines as "a per- thought might know of such software produced two son who speaks, makes arrangements, or takes results: an implementation of the BITNET Listserv charge for another", and which seems perfectly written in C for UNIX (from the comp.sources.unix appropriate given the nature of the software. archives), and several different programs named "listserv" written in perl. Designing a Solution I first examined the BITNET Listserv C pack- My first step in designing a solution was to age from the comp.sources.unix newsgroup archives. decide on the general approach I was going to take. It looked like it would do most of what I wanted, First, I decided that all routine interactions with but it also looked like it did a lot of things I didn’t Majordomo would take place asynchronously via really care about (there appeared to be features for email. Second, since the software was going to coordinating activities between multiple Listserv spend most of its time parsing emailed instructions, servers on different machines, for instance). It processing text files (the actual mailing lists) accord- appeared to be rather short on documentation, and ing to those instructions, and generating emailed what documentation there was seemed to assume responses to users, I wanted to write it in a language that the reader was already familiar with BITNET well-suited for that task; perl seemed the natural Listserv implementation and operation. All in all, it choice. looked like it would be a real headache for me to In the Majordomo world model, there are three install, configure, and maintain, since I’m not fami- types of people: users (without any special liar with BITNET Listserv implementation and privileges), mailing list owners, and the owner of the operation. Majordomo server itself. Interactions with users The next things I looked at were several perl take place strictly by email; the user mails a set of scripts from a variety of sources that were sup- requests to Majordomo, and Majordomo processes posedly Listserv-like servers. Some of these scripts those requests and sends back appropriate replies. were pointed out to me by folks on the net who Interactions with list owners also take place strictly knew I was looking for such a thing, and I found by email, but a list owner can do a few things that a others by searching through Archie for "listserv". normal user can’t; the commands that are restricted Unfortunately, these various scripts all turned out to to list owners are protected with a per-list password be more what I’d call "archive servers" than "list- (though it’s very weak password protection, since the serv" implementations; they were written to auto- password is passed in the clear through the email; mate retrieval of files from archives via email, for the goal is not absolute security, but to avoid people folks who don’t have access to anonymous FTP. making a nuisance of themselves by abusing the When I examined one of these scripts that claimed Majordomo server). The Majordomo owner is the to support "subscribe" and "unsubscribe" requests, I person responsible for maintaining the Majordomo found that what it did with such requests was for- server itself, and for performing tasks such as creat- ward them by email to the mailing list owner for ing new mailing lists to be served by Majordomo. manual processing; this was exactly what I was try- The software needs to support multiple mailing ing to avoid! lists, each owned by different individuals. Some In the end, I decided to implement my own owners wish to approve all "subscribe" requests for version of Listserv, so that I could get exactly what I their list (a "closed" list), while other owners wish wanted. The name for my software was provided by routine "subscribe" requests to be approved automat- Eliot Lear of Silicon Graphics, Inc.; he suggested ically (an "open" list), with notification to the owner. Command Description subscribe list [address] Subscribe yourself (or address, if specified) to list unsubscribe list [address] Unsubscribe yourself (or address, if specified) from list which [address] Find out which lists you (or address, if specified) are on who list Show the members of list info list Show the general introductory information for list lists Show the lists handled by this Majordomo server help Retrieve a help message, explaining these commands end Stop processing commands (useful if your mailer automatically adds a signature to your messages) Figure 1: Majordomo user commands 136 1992 LISA VI – October 19-23, 1992 – Long Beach, CA Chapman Majordomo: How I Manage 17 Mailing Lists ... Routine "unsubscribe" requests are approved way to think about "approve", by the way, is that the automatically, with notification to the list owner, for list owner is telling Majordomo "I approve this com- both open and closed lists. Owners have a way (the mand; just do it!", not "I approve this request you "approve" command) to approve all "subscribe" sent me earlier". Majordomo doesn’t keep track of requests on closed lists, as well as non-routine "sub- outstanding requests; when an "approve" command scribe" and "unsubscribe" requests on open lists.
Load more

Recommended publications
  • (GNU Mailman) Mailing Lists
    Usability and efficiency improvements of the (GNU Mailman) mailing lists Rudy Borgstede ([email protected]) System and Network Engineering University of Amsterdam July 5, 2008 Versions Version Date Changes 0.0.1 18 May 2008 First setup of the report 0.0.2 9 June 2008 Release Candidate 1 of the project proposal 0.1.1 17 June 2008 A rewrite of the document because of the change of project result. The project will deliver an advice rather then a product like a patch or add-on for GNU Mailman. This means that the report becomes an consultancy report instead of a project proposal. 1.0.0 30 June 2008 Final version 1 of the report. 1.0.1 1 July 2008 A spelling check of the report. 1.0.2 5 July 2008 Extending the conclusion en future work chapters. Participants Name Contact Information University of Amsterdam Rudy Borgstede (Student) [email protected] Cees de Laat (Supervisor) [email protected] NLnet Michiel Leenaars (Supervisor) [email protected] Abstract This report is the result of a research project of four weeks at the NLnet Foundation1 in Amster- dam. The NLnet Foundation is a foundation who financially supports the open-source community and their projects. The purpose of the project is to improve the usability and the administration of the mailing lists (of the foundation) and giving a more clear view on mailing list server software to anyone who is interested in using mailing list server software or developing new mail or mail- ing list server software. The report describes the research of the usability of several open-source mailing list server software for scalable environments with several well known mail servers.
    [Show full text]
  • Sendmail, Mailing Lists, Email Clients, and POP/IMAP (Remote Connections)
    Email 9 Sendmail, mailing lists, email clients, and POP/IMAP (remote connections) This chapter shows you how to set up sendmail, set up sim- ple mailing lists for customers, clients, or groups of people, review some of the email clients available, and set up remote connections using the POP (Post Office Protocol) and IMAP (Internet Message Access Protocol) mail standards. Email (electronic mail) was one of the first methods for communicating over what is now the Internet. Email allowed short messages to route across vari- ous machines. In the early days (1987), you often had to manually specify all the machines (or hops) an email message would have to route through to get to the end host. With TCP/IP as the communication method, things are a bit smarter in that you don’t need to know how to get to the end host—as long as some machine along the way knows how to route the email for you. The tech- nical name for the email that you get on the Internet is known as Simple Mail Transfer Protocol (SMTP). There are a few other protocols that work with SMTP, such as POP and IMAP, but we’ll get to those later. You can find more information about SMTP in RFC 821. 159 160 Chapter 9 • Email The primary program that is the Mail Transport Agent (or MTA) is send- mail. There are others available, but sendmail is pretty much the standard for most Linux installations. You may have seen that really thick book with a bat1 on it that gets you into the nitty-gritty of sendmail.
    [Show full text]
  • Openbsd Frequently Asked Questions
    OpenBSD Frequently Asked Questions Language: en [teams] de fr nl pl pt Documentation and Frequently Other Documents Asked Questions Upgrade Guide Following -current Commonly Encountered Issues Recent updates Following -stable Port Testing Guide Using AnonCVS This FAQ is supplemental documentation to the man pages, available both in the installed Using CVSup system and online. The FAQ covers the active release of OpenBSD, currently v4.0. There Manual pages are likely features and changes to features in the development version (-current) of Bug Reporting OpenBSD that are not covered in this FAQ. Mailing lists PF User's Guide The FAQ in PDF and plain text form is available in the pub/OpenBSD/doc directory OpenSSH FAQ from the FTP mirrors, along with other documents. PDF files OpenBSD FAQ PF User's Guide 1 - Introduction to OpenBSD Text files ● 1.1 - What is OpenBSD? ● OpenBSD FAQ 1.2 - On what systems does OpenBSD run? ● PF User's Guide 1.3 - Is OpenBSD really free? ● 1.4 - Why might I want to use OpenBSD? ● 1.5 - How can I help support OpenBSD? Back to OpenBSD ● 1.6 - Who maintains OpenBSD? ● 1.7 - When is the next release of OpenBSD? ● 1.8 - What is included with OpenBSD? ● 1.9 - What is new in OpenBSD 4.0? ● 1.10 - Can I use OpenBSD as a desktop system? ● 1.11 - Why is/isn't ProductX included? 2 - Other OpenBSD Information Resources ● 2.1 - Web Pages ● 2.2 - Mailing Lists ● 2.3 - Manual Pages ● 2.4 - Reporting Bugs 3 - Obtaining OpenBSD ● 3.1 - Buying an OpenBSD CD set ● 3.2 - Buying OpenBSD T-Shirts ● 3.3 - Does OpenBSD provide an ISO image for download? http://www.openbsd.org/faq/index.html (1 of 7) [30/04/2007 10:35:20] OpenBSD Frequently Asked Questions ● 3.4 - Downloading via FTP, HTTP or AFS ● 3.5 - Obtaining Current Source Code 4 - OpenBSD 4.0 Installation Guide ● 4.1 - Overview of the OpenBSD installation procedure.
    [Show full text]
  • The Qmail Handbook by Dave Sill ISBN:1893115402 Apress 2002 (492 Pages)
    < Free Open Study > The qmail Handbook by Dave Sill ISBN:1893115402 Apress 2002 (492 pages) This guide begins with a discussion of qmail s history, architecture and features, and then goes into a thorough investigation of the installation and configuration process. Table of Contents The qmail Handbook Introduction Ch apt - Introducing qmail er 1 Ch apt - Installing qmail er 2 Ch apt - Configuring qmail: The Basics er 3 Ch apt - Using qmail er 4 Ch apt - Managing qmail er 5 Ch apt - Troubleshooting qmail er 6 Ch apt - Configuring qmail: Advanced Options er 7 Ch apt - Controlling Junk Mail er 8 Ch apt - Managing Mailing Lists er 9 Ch apt - Serving Mailboxes er 10 Ch apt - Hosting Virtual Domain and Users er 11 Ch apt - Understanding Advanced Topics er 12 Ap pe ndi - How qmail Works x A Ap pe ndi - Related Packages x B Ap pe ndi - How Internet Mail Works x C Ap pe ndi - qmail Features x D Ap pe - Error Messages ndi x E Ap pe - Gotchas ndi x F Index List of Figures List of Tables List of Listings < Free Open Study > < Free Open Study > Back Cover • Provides thorough instruction for installing, configuring, and optimizing qmail • Includes coverage of secure networking, troubleshooting issues, and mailing list administration • Covers what system administrators want to know by concentrating on qmail issues relevant to daily operation • Includes instructions on how to filter spam before it reaches the client The qmail Handbook will guide system and mail administrators of all skill levels through installing, configuring, and maintaining the qmail server.
    [Show full text]
  • Qmail Quickstarter: Install, Set up and Run Your Own Email Server
    Qmail Quickstarter Install, Set Up, and Run your own Email Server A fast-paced and easy-to-follow, step-by-step guide that gets you up and running quickly Kyle Wheeler BIRMINGHAM - MUMBAI Qmail Quickstarter Install, Set Up, and Run your own Email Server Copyright © 2007 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: June 2007 Production Reference: 1040607 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847191-15-1 www.packtpub.com Cover Image by Vinayak Chittar ([email protected]) [ FM- ] Credits Author Editorial Manager Kyle Wheeler Dipali Chittar Reviewer Project Coordinator Russell Nelson Abhijeet Deobhakta Development Editor Indexer Nanda Padmanabhan Bhushan Pangaonkar Assistant Development Editor Proofreader Rashmi Phadnis Chris Smith Technical Editor Production Coordinator Saurabh Singh Manjiri Nadkarni Code Testing Cover Designer Ankur Shah Manjiri Nadkarni Project Manager Patricia Weir [ FM- ] About the Author Kyle Wheeler is a PhD candidate at the University of Notre Dame in the Computer Science and Engineering Department.
    [Show full text]
  • How Qmail Works
    APPENDIX A How qmail Works You DON'T NEED TO UNDERSTAND how qmail works to install or use qmail. And you don't have to be an auto mechanic to operate a car or a watchmaker to tell time. Eut if you really want to master qmail, knowing exactly how it does what it does is crucial. Luckily, qmail's simple, modular design makes understanding how it works easy for a system as complex as a Mail Transfer Agent (MTA). This appendix takes a top-down approach: first looking at how the modules interact with each other, then looking at how each module does its job. High-Level Overview The grand division in qmail is between the modules that accept new messages and place them into the queue and the modules that deliver them from the queue. We'll call these functions receivingand sending. The separation between receiving and sending is complete: Either of these functions can be fully oper­ ational while the other is shut down. Figure A-l shows the high-level organization of qmail. Incoming Receiving Queue Sending Delivered Messages Messages Figure A -1. High-level qmail organization Receiving Messages enter the queue through two main routes: local injection using qmail-inject or sendmail and network injection using qmail-smtpd, qmail-qmtpd 417 AppendixA or qmail-qmqpd. Both ofthese routes use qmail-queue to actually inject their mes­ sages into the queue. Figure A-2 shows the organization ofthe receiving function. QMQP tcpserver QMTP tcpserver SMTP tcpserver Queue Local------------­ MUA Figure A-2. The receivingfunction Sending Messages are delivered from the queue through two main routes: local delivery using qma il-loca 1 and remote delivery using qma il-remote.
    [Show full text]
  • Absolute Openbsd: UNIX for the Practical Paranoid
    Absolute OpenBSD: UNIX for the Practical Paranoid by Michael W. Lucas ISBN:1886411999 No Starch Press © 2003 Back Cover ...............................................................................................................................- 17 - ACKNOWLEDGMENTS........................................................................................................- 20 - Chapter 0: Introduction.............................................................................................................- 21 - Overview ..............................................................................................................................- 21 - What Is BSD? .......................................................................................................................- 21 - BSD Goes Public..................................................................................................................- 22 - AT&T UNIX ........................................................................................................................- 22 - What Is OpenBSD? ..............................................................................................................- 23 - Other BSDs...........................................................................................................................- 24 - NetBSD.............................................................................................................................- 24 - FreeBSD ...........................................................................................................................-
    [Show full text]
  • Sympa a Mailing List Management Software Reference Manual
    ! " # $ %&'( )*+ ,- " . / )*+$ 0 1 " . 2 133 3 3 34" . 5 " # . 2 133 3 3 34" # .3 5 ,2 133 3 335 & ) ) ( + ) 0 % ' , , ) - - 6 7 8 76 8 ) 798 ' 7: 8 7 8 ; 1 sur 189 ; ) < < ; ) )= 6< )= !=;> 6 ( 6 ;=;& ! ! ; )= * ) , 6 ' ' ' '6% 6 ( ? $ @ 2 sur 189 , A A A A A AA AB A@ A@" A A- A A A A A A A A$A, A A A A A A A A A AA # * A A A - -A A $ A A $A, A 3 sur 189 A A $ A A A #.CDA A- A A A A$A A A A A A- A A A A E$ ,A A, F A A< A A< < < < < < < < < < < AA< AA< AA< AA< AA< AA< AA< AA< AA< AA . ; , 4 sur 189 A A A - A 9 A A A A A A A E$ $ A A A A A A A A A A A A A A A A@A A A#A AA -$ A A A A A A & A A - A A < A A A A * AA-A A A A A A A A A A A A A- A A A- A A A AA A A$ A A A A 5 sur 189 A A A A A A A ( A A$ A A A A A A A A $ 3';': - - A 4 A A A ) < ; ):6( * 9 * * * ; ; $ - ; - ' :$ - G G , ; ; $ ! + H; 6 sur 189 A A A $ 4 A- A A- A$ A A A A A I A I @I A ABI@ * - ( + '% - 6 ; ; , ; , & *- 4- & % 6 6 A A A AA 7 sur 189 ) ) ; ! " .
    [Show full text]
  • Openbsd F.A.Q
    OpenBSD F.A.Q. August 1, 2010 Contents Foreword iii 1 Introduction to OpenBSD 1 1.1 What is OpenBSD? . 2 1.2 On what systems does OpenBSD run? . 2 1.3 Why might I want to use OpenBSD? . 3 1.4 Is OpenBSD really free? . 3 1.5 How can I help support OpenBSD? . 4 1.6 Who maintains OpenBSD? . 5 1.7 When is the next release of OpenBSD? . 5 1.8 What is included with OpenBSD? . 5 1.9 What is new in OpenBSD 4.7? . 7 1.10 Can I use OpenBSD as a desktop system? . 7 1.11 Why is/isn't ProductX included? . 7 2 Getting to know OpenBSD 9 2.1 Web Pages of Interest . 10 2.2 Mailing Lists . 10 2.3 Manual Pages . 11 2.3.1 Getting started . 11 2.3.2 For more advanced users . 12 3 Getting started with OpenBSD 15 3.1 Buying an OpenBSD CD set . 16 3.2 Buying OpenBSD T-Shirts . 16 3.3 Does OpenBSD provide an ISO image for download? . 16 3.4 Downloading via FTP, HTTP or AFS . 17 3.5 Selecting Hardware . 17 3.6 What is an appropriate ”first system" to learn OpenBSD on? . 19 4 OpenBSD 4.7 Installation Guide 21 4.1 Overview of the OpenBSD installation procedure . 22 4.2 Pre-installation checklist . 24 4.3 Creating bootable OpenBSD install media . 24 4.3.1 Making a CD-ROM . 25 4.3.2 Creating floppies on Unix . 26 4.3.3 Creating floppies on Windows . 26 i Contents 4.4 Booting OpenBSD install media .
    [Show full text]
  • Life with Qmail
    Life with qmail Life with qmail Table of Contents 1. Introduction........................................................................................................................................1 1.1. Audience..............................................................................................................................1 1.2. What is qmail?.....................................................................................................................1 1.3. Why use qmail?...................................................................................................................1 1.4. History.................................................................................................................................2 1.5. Features................................................................................................................................2 1.6. Related packages..................................................................................................................4 1.7. Architecture.........................................................................................................................5 1.8. License.................................................................................................................................5 1.9. Comparison with other MTA's............................................................................................5 1.10. Documentation...................................................................................................................5
    [Show full text]
  • Deploying DNS and Sendmail
    Deploying DNS and Sendmail Hal Pomeranz Deer Run Associates All material in this course Copyright © Hal Pomeranz and Deer Run Associates, 1998-2001. All rights reserved. Hal Pomeranz * Founder/CEO * [email protected] Deer Run Associates * PO Box 20370 * Oakland, CA 94620 +1 510-339-7740 (voice) * +1 510-339-3941 (fax) http://www.deer-run.com/ Sample configuration files supplied in the Appendices can be downloaded as text files from http://www.deer-run.com/~hal/dns-sendmail/ 1 Introduction • About This Course • Agenda This space intentionally left blank. 2 What is This Course? • An introduction to configuring and managing DNS and Sendmail • Hopefully enough to allow you to do basic administration on your own • A preparation for more advanced courses in DNS and Sendmail mgmt This course will hopefully give you enough information to manage DNS and mail services for site, assuming you've been handed the job with no other training. It's not enough just to learn how to configure BIND and Sendmail, you have to understand something about good architectural principals, as well as have the knowledge to manage mailing lists, write your own mail programs and auto- responders, and deal with virtual domains. With any luck, this course will also prepare you to get additional knowledge on your own. There are many excellent books and other tutorials which cover more advanced topics in this area (including Sendmail courses from Eric Allman, the author of Sendmail, and DNS courses from Paul Vixie, the current maintainer of BIND). 3 What isn't This Course? • Complete coverage of the subject • Free of religious belief • For people who want PC-based mail • For experienced DNS/mail admins • "Hacker's Guide" to DNS or Sendmail This course should in no way be considered complete coverage of the subject matter.
    [Show full text]
  • Openbsd Frequently Asked Questions
    OpenBSD Frequently Asked Questions Language: [en] [cs] [de] [es] [fr] [id] [ja] [pl] [pt] [zh-cn] [zh-tw] Documentation and Frequently Asked Questions Other Documents Commonly Encountered Issues Recent updates Upgrade-MiniFAQ Ports and Packages Port Testing Guide This FAQ is supplemental documentation to the man pages, available both in the installed Using AnonCVS system and online. The FAQ covers the active release of OpenBSD, currently v3.4. Note Stable that the development version (-current) of OpenBSD is not covered by this FAQ. Using CVSup Manual pages The FAQ in PDF and plain text form is available in the pub/OpenBSD/doc directory Bug Reporting from the FTP mirrors, along with other documents. Mail lists PF User's Guide OpenSSH FAQ PDF files 1 - Introduction to OpenBSD OpenBSD FAQ ● 1.1 - What is OpenBSD? PF User's Guide ● 1.2 - On what systems does OpenBSD run? ● 1.3 - Is OpenBSD really free? Text files ● 1.4 - Why might I want to use OpenBSD? ● OpenBSD FAQ 1.5 - How can I help support OpenBSD? ● PF User's Guide 1.6 - Who maintains OpenBSD? ● 1.7 - When is the next release of OpenBSD? ● 1.8 - What is included with OpenBSD? Back to OpenBSD ● 1.9 - What is new in OpenBSD 3.4? 2 - Other OpenBSD Information Resources ● 2.1 - Web Pages ● 2.2 - Mailing Lists ● 2.3 - Manual Pages ● 2.4 - Reporting Bugs 3 - Obtaining OpenBSD ● 3.1 - Buying an OpenBSD CD ● 3.2 - Buying OpenBSD T-Shirts ● 3.3 - Does OpenBSD provide an ISO image for download? ● 3.4 - Downloading via FTP or AFS ● 3.5 - Obtaining Current Source Code http://www.openbsd.org/faq/index.html (1 of 6) [30/04/2004 07:12:45] OpenBSD Frequently Asked Questions 4 - OpenBSD 3.4 Installation Guide ● 4.1 - Overview of the OpenBSD installation procedure.
    [Show full text]