----Next_Part(Tue_Sep_23_19:46:39_2003_273)----
----Security_Multipart0(Tue_Sep_23_19:46:39_2003_459)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQA/cCSPTyzT2CeTzy0RAgCyAJ0QofYSGG8sjCwub0D7f0qn9MjklgCgzcQM
M5CGWBjl1alBZ5ZaOXAcCTw=
=3LW0
-----END PGP SIGNATURE-----
----Security_Multipart0(Tue_Sep_23_19:46:39_2003_459)----
From owner-freebsd-doc@FreeBSD.ORG Tue Sep 23 05:49:02 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id ADF5E16A4B3; Tue, 23 Sep 2003 05:49:02 -0700 (PDT)
Received: from gw.celabo.org (gw.celabo.org [208.42.49.153])
by mx1.FreeBSD.org (Postfix) with ESMTP
id DB6FD43FE5; Tue, 23 Sep 2003 05:49:01 -0700 (PDT)
(envelope-from nectar@celabo.org)
Received: from madman.celabo.org (madman.celabo.org [10.0.1.111])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK))
by gw.celabo.org (Postfix) with ESMTP
id 7F6085482B; Tue, 23 Sep 2003 07:49:01 -0500 (CDT)
Received: by madman.celabo.org (Postfix, from userid 1001)
id 1B11D6D454; Tue, 23 Sep 2003 07:49:01 -0500 (CDT)
Date: Tue, 23 Sep 2003 07:49:01 -0500
From: "Jacques A. Vidrine"
To: Hiroki Sato
Message-ID: <20030923124900.GG44152@madman.celabo.org>
References:
<20030923.194639.16489841.hrs@eos.ocn.ne.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030923.194639.16489841.hrs@eos.ocn.ne.jp>
X-Url: http://www.celabo.org/
User-Agent: Mutt/1.5.4i-ja.1
cc: security-officer@FreeBSD.org
cc: doc@FreeBSD.org
cc: www@FreeBSD.org
Subject: Re: Latest security advisory not visible on front page
(FreeBSD-SA-03:13.sendmail)
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Tue, 23 Sep 2003 12:49:02 -0000
On Tue, Sep 23, 2003 at 07:46:39PM +0900, Hiroki Sato wrote:
> Hi,
>
> I would like to commit the attached patch. With this patch, a list of
> the advisories in security.sgml is generated from advisories.xml, and
> the security officer no longer needs to change the list; only needs to
> change advisories.xml.
>
> Comments or objections?
This sounds good to me--- please go ahead and commit. Thank you very
much!
Cheers,
--
Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal
nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se
From owner-freebsd-doc@FreeBSD.ORG Wed Sep 24 03:50:07 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 8601116A4B3
for ;
Wed, 24 Sep 2003 03:50:07 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP id 445C24400D
for ;
Wed, 24 Sep 2003 03:50:05 -0700 (PDT)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8OAo5FY037074
for ;
Wed, 24 Sep 2003 03:50:05 -0700 (PDT)
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8OAo5sc037070;
Wed, 24 Sep 2003 03:50:05 -0700 (PDT)
(envelope-from gnats)
Resent-Date: Wed, 24 Sep 2003 03:50:05 -0700 (PDT)
Resent-Message-Id: <200309241050.h8OAo5sc037070@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-doc@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
Simon Barner
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id BBD4216A4B3
for ;
Wed, 24 Sep 2003 03:41:16 -0700 (PDT)
Received: from mailout.informatik.tu-muenchen.de
(mailout.informatik.tu-muenchen.de [131.159.0.5])
by mx1.FreeBSD.org (Postfix) with ESMTP id 7DC9044005
for ;
Wed, 24 Sep 2003 03:41:13 -0700 (PDT)
(envelope-from barner@in.tum.de)
Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000)
id 3C89C3B4F5; Wed, 24 Sep 2003 12:40:18 +0200 (CEST)
Message-Id: <20030924104018.3C89C3B4F5@zi025.glhnet.mhn.de>
Date: Wed, 24 Sep 2003 12:40:18 +0200 (CEST)
From: Simon Barner
To: FreeBSD-gnats-submit@FreeBSD.org
X-Send-Pr-Version: 3.113
Subject: docs/57153: S_IRWXU missing in fstat(2) man page?
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Simon Barner
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Wed, 24 Sep 2003 10:50:07 -0000
>Number: 57153
>Category: docs
>Synopsis: S_IRWXU missing in fstat(2) man page?
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Wed Sep 24 03:50:04 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Simon Barner
>Release: FreeBSD 4.9-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD zi025.glhnet.mhn.de 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #1: Thu Sep 4 20:49:53 CEST 2003 simon@zi025.glhnet.mhn.de:/usr/src/sys/compile/KISTE i386
>Description:
Shouldn't the S_IRWXU constant from /usr/include/sys/stat.h also be mentioned
in the fstat(2) man page (and possibly others)
--> this one #define S_IRWXU 0000700 /* RWX mask for owner */
--> already there #define S_IRUSR 0000400 /* R for owner */
-"- #define S_IWUSR 0000200 /* W for owner */
-"- #define S_IXUSR 0000100 /* X for owner */
If you confirm this, I can prepare a patch.
>How-To-Repeat:
Compare /usr/include/sys/stat.h and fstat(2)
>Fix:
Add missing constants to man page.
>Release-Note:
>Audit-Trail:
>Unformatted:
From owner-freebsd-doc@FreeBSD.ORG Wed Sep 24 19:05:09 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id EF06216A4B3; Wed, 24 Sep 2003 19:05:09 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP
id 6EFF24400E; Wed, 24 Sep 2003 19:05:09 -0700 (PDT)
(envelope-from hmp@FreeBSD.org)
Received: from freefall.freebsd.org (hmp@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8P259FY091559;
Wed, 24 Sep 2003 19:05:09 -0700 (PDT)
(envelope-from hmp@freefall.freebsd.org)
Received: (from hmp@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8P259fo091555;
Wed, 24 Sep 2003 19:05:09 -0700 (PDT)
(envelope-from hmp)
Date: Wed, 24 Sep 2003 19:05:09 -0700 (PDT)
From: Hiten Pandya
Message-Id: <200309250205.h8P259fo091555@freefall.freebsd.org>
To: hmp@FreeBSD.org, freebsd-doc@FreeBSD.org, hmp@FreeBSD.org
Subject: Re: docs/55445: [PATCH] off-by-one bug in example code
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Thu, 25 Sep 2003 02:05:10 -0000
Synopsis: [PATCH] off-by-one bug in example code
Responsible-Changed-From-To: freebsd-doc->hmp
Responsible-Changed-By: hmp
Responsible-Changed-When: Wed Sep 24 19:04:50 PDT 2003
Responsible-Changed-Why:
I will work on this, after discussing with my mentor.
http://www.freebsd.org/cgi/query-pr.cgi?pr=55445
From owner-freebsd-doc@FreeBSD.ORG Wed Sep 24 19:06:05 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id 5397416A4B3; Wed, 24 Sep 2003 19:06:05 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP
id C937D43F3F; Wed, 24 Sep 2003 19:06:04 -0700 (PDT)
(envelope-from hmp@FreeBSD.org)
Received: from freefall.freebsd.org (hmp@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8P264FY094800;
Wed, 24 Sep 2003 19:06:04 -0700 (PDT)
(envelope-from hmp@freefall.freebsd.org)
Received: (from hmp@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8P264cl094796;
Wed, 24 Sep 2003 19:06:04 -0700 (PDT)
(envelope-from hmp)
Date: Wed, 24 Sep 2003 19:06:04 -0700 (PDT)
From: Hiten Pandya
Message-Id: <200309250206.h8P264cl094796@freefall.freebsd.org>
To: ahmetov@rain.ifmo.ru, hmp@FreeBSD.org, freebsd-doc@FreeBSD.org
Subject: Re: docs/55805: a little correction to the arch-handbook
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Thu, 25 Sep 2003 02:06:05 -0000
Synopsis: a little correction to the arch-handbook
State-Changed-From-To: open->closed
State-Changed-By: hmp
State-Changed-When: Wed Sep 24 19:05:47 PDT 2003
State-Changed-Why:
Same problem as: PR/55445
http://www.freebsd.org/cgi/query-pr.cgi?pr=55805
From owner-freebsd-doc@FreeBSD.ORG Thu Sep 25 05:10:07 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 2810216A4B3
for ;
Thu, 25 Sep 2003 05:10:07 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP id 55C5244037
for ;
Thu, 25 Sep 2003 05:10:04 -0700 (PDT)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8PCA4FY063857
for ;
Thu, 25 Sep 2003 05:10:04 -0700 (PDT)
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8PCA4eQ063856;
Thu, 25 Sep 2003 05:10:04 -0700 (PDT)
(envelope-from gnats)
Resent-Date: Thu, 25 Sep 2003 05:10:04 -0700 (PDT)
Resent-Message-Id: <200309251210.h8PCA4eQ063856@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-doc@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
Josef El-Rayes
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 520B016A4B3
for ;
Thu, 25 Sep 2003 05:06:03 -0700 (PDT)
Received: from octopussy.utanet.at (octopussy.utanet.at [213.90.36.45])
by mx1.FreeBSD.org (Postfix) with ESMTP id 6D67143FF3
for ;
Thu, 25 Sep 2003 05:05:58 -0700 (PDT)
(envelope-from shammer@daemon.li)
Received: from patricia.utanet.at ([213.90.36.8])
by octopussy.utanet.at with esmtp (Exim 4.12)
id 1A2Usf-0005xZ-00
for FreeBSD-gnats-submit@freebsd.org; Thu, 25 Sep 2003 14:05:57 +0200
Received: from dsl-242-85.utaonline.at ([212.152.242.85] helo=gina.at)
by patricia.utanet.at with esmtp (Exim 4.12)
id 1A2Usb-00062Y-00
for FreeBSD-gnats-submit@freebsd.org; Thu, 25 Sep 2003 14:05:53 +0200
Received: by gina.at (Postfix, from userid 1001)
id 838B160F2; Thu, 25 Sep 2003 14:05:42 +0200 (CEST)
Message-Id: <20030925120542.838B160F2@gina.at>
Date: Thu, 25 Sep 2003 14:05:42 +0200 (CEST)
From: Josef El-Rayes
To: FreeBSD-gnats-submit@FreeBSD.org
X-Send-Pr-Version: 3.113
Subject: docs/57209: [patch] article/mh: add missing docbook tags
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Josef El-Rayes
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Thu, 25 Sep 2003 12:10:07 -0000
>Number: 57209
>Category: docs
>Synopsis: [patch] article/mh: add missing docbook tags
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Thu Sep 25 05:10:03 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Josef El-Rayes
>Release: FreeBSD 5.1-CURRENT i386
>Organization:
>Environment:
System: FreeBSD gina.at 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sat Sep 13 13:22:16 CEST 2003 root@gina.at:/usr/obj/usr/src/sys/GINA i386
>Description:
docs/en_US.ISO8859-1/articles/mh/article.sgml:
o add missing application tags to "MH"
o add missing ")" to %(formataddr) function
o add missing literal tags to "To:" and "Subject:"
>How-To-Repeat:
>Fix:
--- article.sgml.diff begins here ---
--- article.sgml.orig Thu Sep 25 11:57:25 2003
+++ article.sgml Thu Sep 25 13:58:49 2003
@@ -36,7 +36,7 @@
- This document contains an introduction to using MH on
+ This document contains an introduction to using MH on
FreeBSD
@@ -44,23 +44,23 @@
Introduction
- MH started back in 1977 at the RAND Corporation, where the
- initial philosophies behind MH were developed. MH is not so much
+ MH started back in 1977 at the RAND Corporation, where the
+ initial philosophies behind MH were developed. MH is not so much
a monolithic email program but a philosophy about how best to
- develop tools for reading email. The MH developers have done a
+ develop tools for reading email. The MH developers have done a
great job adhering to the KISS principle: Keep It
Simple Stupid. Rather than have one large program for reading,
sending and handling email they have written specialized
- programs for each part of your email life. One might liken MH to
+ programs for each part of your email life. One might liken MH to
the specialization that one finds in insects and nature. Each
- tool in MH does one thing, and does it very well.
+ tool in MH does one thing, and does it very well.Beyond just the various tools that one uses to handle their
- email MH has done an excellent job keeping the configuration of
+ email MH has done an excellent job keeping the configuration of
each of these tools consistent and uniform. In fact, if you are
not quite sure how something is supposed to work or what the
arguments for some command are supposed to be, then you can
- generally guess and be right. Each MH command is consistent
+ generally guess and be right. Each MH command is consistent
about how it handles reading the configuration files and how it
takes arguments on the command line. One useful thing to
remember is that you can always add a to
@@ -68,9 +68,9 @@
command.The first thing that you need to do is to make sure that you
- have installed the MH package on your FreeBSD machine. If you
+ have installed the MH package on your FreeBSD machine. If you
installed from CDROM you should be able to execute the following
- to load mh:
+ to load MH:
&prompt.root; pkg_add /cdrom/packages/mh-6.8.3.tgz
@@ -84,14 +84,14 @@
URL="ftp://louie.udel.edu/">louie.udel.edu.This primer is not a full comprehensive explanation of how
- MH works. This is just intended to get you started on the road
+ MH works. This is just intended to get you started on the road
to happier, faster mail reading. You should read the manual pages
for the various commands. You might also want to read the comp.mail.mh newsgroup. Also
you can read the FAQ for MH.
- The best resource for MH is Jerry Peek's MH &
+ URL="http://www.faqs.org/faqs/mail/mh-faq/">FAQ for MH.
+ The best resource for MH is Jerry Peek's MH &
nmh: Email for Users & Programmers.
@@ -101,7 +101,7 @@
This section covers how to use inc,
show, scan, next,
prev, rmm, rmf, and
- msgchk. One of the best things about MH is the
+ msgchk. One of the best things about MH is the
consistent interface between programs. One thing to keep in
mind when using these commands is how to specify message lists.
In the case of inc this does not really make any
@@ -124,8 +124,8 @@
If you just type in inc and hit
return you will be well on your way to getting
- started with MH. The first time you run inc it
- will setup your account to use all the MH defaults and ask you
+ started with MH. The first time you run inc it
+ will setup your account to use all the MH defaults and ask you
about creating a Mail directory under your HOME directory. If you have mail waiting to
be downloaded you will see something that looks like:
@@ -144,7 +144,7 @@
you.A lot of people like to use POP for grabbing their email.
- MH can do POP to grab your email. You will need to give
+ MH can do POP to grab your email. You will need to give
inc a few command line arguments.
@@ -155,7 +155,7 @@
mail.pop.org to download your email, and that
your username on their system is username. The
option tells inc to use
- plain POP3 for downloading your email. MH has support for a
+ plain POP3 for downloading your email. MH has support for a
few different dialects of POP. More than likely you will never
ever need to use them though. While you can do more complex
things with inc such as audit files and scan format files this
@@ -210,7 +210,7 @@
33 01/16 Michael Smith Re: FBSD 2.1<<Nate Williams stands accused of sa
- Like just about everything in MH this display is very
+ Like just about everything in MH this display is very
configurable. This is the typical default display. It gives
you the message number, the date on the email, the sender, the
subject line, and a sentence fragment from the very beginning
@@ -235,7 +235,7 @@
rmm is used to remove a mail message. The
default is typically to not actually remove the message but to
- rename the file to one that is ignored by the MH commands. You
+ rename the file to one that is ignored by the MH commands. You
will periodically need to go through and physically delete the
removed messages.
@@ -327,7 +327,7 @@
Then if I wanted to read message number 27 I would do a
show 27 and it would be displayed. As you can
- probably tell from this sample session MH is pretty easy to
+ probably tell from this sample session MH is pretty easy to
use and looking through emails and displaying them is fairly
intuitive and easy.
@@ -338,12 +338,12 @@
Anybody who gets lots of email definitely wants to be able
to prioritize, stamp, brief, de-brief, and number their emails
- in a variety of different ways. MH can do this better than just
+ in a variety of different ways. MH can do this better than just
about anything. One thing that we have not really talked about is
the concept of folders. You have undoubtedly come across the
- folders concept using other email programs. MH has folders too.
- MH can even do sub-folders of a folder. One thing you should
- keep in mind with MH is that when you ran inc for
+ folders concept using other email programs. MH has folders too.
+ MH can even do sub-folders of a folder. One thing you should
+ keep in mind with MH is that when you ran inc for
the first time and it asked you if it could create a
Mail directory it began storing everything in that
directory. If you look at that directory you will find a
@@ -352,19 +352,19 @@
thrown anywhere else.Whenever you create a new folder a new directory is going to
- be created underneath your MH Mail directory, and
+ be created underneath your MHMail directory, and
messages in that folder are going to be stored in that
directory. When a new email message comes, it is thrown
into your inbox directory with a file name that is
equivalent to the message number. So even if you did not have
- any of the MH tools to read your email you could still use
+ any of the MH tools to read your email you could still use
standard &unix; commands to munge around in those directories and
just more your files. It is this simplicity that really gives you
a lot of power with what you can do with your email.Just as you can use message lists like 23 16
- 42 with most MH commands there is a folder option you can
- specify with just about every MH command. If you do a
+ 42 with most MH commands there is a folder option you can
+ specify with just about every MH command. If you do a
scan +freebsd it will scan your freebsd
folder, and your current folder will be changed to
freebsd. If you do a show +freebsd 23 16
@@ -374,7 +374,7 @@
will need to make sure you use it to make commands process
different folders. Remember you default folder for mail is
inbox so doing a folder +inbox should
- always get you back to your mail. Of course, in MH's infinite
+ always get you back to your mail. Of course, in MH's infinite
flexibility this can be changed but most places have probably
left it as inbox.
@@ -383,7 +383,7 @@
criteria
pick is one of the more complex commands in
- the MH system. So you might want to read the
+ the MH system. So you might want to read the
pick1 man
page for a more thorough understanding. At its simplest level
you can do something like
@@ -416,7 +416,7 @@
really an abbreviation of and
pick is just a sequence which contains the message
numbers that matched. You can use sequences with just about
- any MH command. So you could have done an rmm pick
+ any MH command. So you could have done an rmm pick
and all those messages would be removed instead. You sequence
can be named anything. If you run pick again it will overwrite
the old sequence if you use the same name.
@@ -513,7 +513,7 @@
&prompt.user; pick -to freebsd-hackers -or -cc freebsd-hackers
- That will grab all the email in your inbox that was sent
+ That will grab all the email in your inbox that was sent
to freebsd-hackers or cc'd to that list. The brace options
allow you to group search criteria together. This is sometimes
very necessary as in the following example
@@ -531,10 +531,10 @@
the subject line. Ordinarily you might have to worry about
something called operator precedence. Remember in math how you
evaluate from left to right and you do multiplication and
- division first and addition and subtraction second? MH has the
+ division first and addition and subtraction second? MH has the
same type of rules for pick. It is fairly complex
so you might want to study the manual page. This document is just
- to help you get acquainted with MH.
+ to help you get acquainted with MH.
@@ -547,7 +547,7 @@
used to switch between folders, pack them, and list them. At
its simplest level you can do a folder
+newfolder and you will be switched into
- newfolder. From there on out all your MH
+ newfolder. From there on out all your MH
commands like comp, repl,
scan, and show will act on that
newfolder folder.
@@ -597,7 +597,7 @@
which would keep 23 in your current inbox but
also list in your netfuture folder. You are
probably beginning to realize some of the really powerful
- things you can do with MH.
+ things you can do with MH.
@@ -605,12 +605,12 @@
Sending MailEmail is a two way street for most people so you want to be
- able to send something back. The way MH handles sending mail can
+ able to send something back. The way MH handles sending mail can
be a bit difficult to follow at first, but it allows for
- incredible flexibility. The first thing MH does is to copy a
+ incredible flexibility. The first thing MH does is to copy a
components file into your outgoing email. A components file is
- basically a skeleton email letter with stuff like the To: and
- Subject: headers already in it. You are then sent into your
+ basically a skeleton email letter with stuff like the To: and
+ Subject: headers already in it. You are then sent into your
editor where you fill in the header information and then type
the body of your message below the dashed lines in the message.
When you leave the editor, the whatnow program is run. When you are at the
@@ -629,9 +629,9 @@
The comp program has a few useful command line
options. The most important one to know right now is the
- option. When MH is installed the
+ option. When MH is installed the
default editor is usually a program called
- prompter which comes with MH. It is not a very
+ prompter which comes with MH. It is not a very
exciting editor and basically just gets the job done. So when
you go to compose a message to someone you might want to use
comp -editor /usr/bin/vi or comp -editor
@@ -697,7 +697,7 @@
me after the option to have
repl automatically add the various addresses to
the Cc: list in the message. You have probably noticed that the
- original message is not included. This is because most MH
+ original message is not included. This is because most MH
setups are configured to do this from the start.
@@ -708,7 +708,7 @@
The components file is usually in
/usr/local/lib/mh. You can copy that file
- into your MH Mail directory and edit to contain what you want
+ into your MH Mail directory and edit to contain what you want
it to contain. It is a fairly basic file. You have various
email headers at the top, a dashed line and then nothing. The
comp command just copies this
@@ -726,7 +726,7 @@
-------
- MH would then copy this components file and throw you into
+ MH would then copy this components file and throw you into
your editor. The components file is fairly
simple. If you wanted to have a signature on those messages
you would just put your signature in that
@@ -751,7 +751,7 @@
It is in the same basic format as the
components file but it contains quite a few extra
formatting codes. The %(lit) command makes room
- for the address. The %(formataddr is a function
+ for the address. The %(formataddr) is a function
that returns a proper email address. The next part is
%< which means if and the
{reply-to} means the reply-to field in the
@@ -765,14 +765,14 @@
message, %> endif.
- As you can tell MH formatting can get rather involved. You
+ As you can tell MH formatting can get rather involved. You
can probably decipher what most of the other functions and
variables mean. All of the information on writing these format
strings is in the MH-Format manual page. The really nice thing is
that once you have built your customized
replcomps file you will not need to touch it again.
No other email program really gives you the power and
- flexibility that MH gives you.
+ flexibility that MH gives you.
--- article.sgml.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
From owner-freebsd-doc@FreeBSD.ORG Thu Sep 25 05:15:29 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id EF99416A4B3
for ; Thu, 25 Sep 2003 05:15:29 -0700 (PDT)
Received: from mail.ac-net.at (secure.ac-net.at [212.24.125.8])
by mx1.FreeBSD.org (Postfix) with ESMTP id 175CB43FFB
for ; Thu, 25 Sep 2003 05:15:28 -0700 (PDT)
(envelope-from shammer@daemon.li)
Received: from localhost (server.ac-net.at [127.0.0.1])
with ESMTP id 6B5873F2E
for ; Thu, 25 Sep 2003 14:15:20 +0200 (CEST)
Received: from daemon.li (dsl-242-85.utaonline.at [212.152.242.85])
with SMTP id 3F0EA3EFA
for ; Thu, 25 Sep 2003 12:15:19 +0000 (UTC)
Received: (qmail 385 invoked from network); 25 Sep 2003 12:16:08 -0000
Received: from localhost (HELO daemon.li) (127.0.0.1)
by localhost with SMTP; 25 Sep 2003 12:16:08 -0000
Received: (from shammer@localhost)
by daemon.li (8.12.6/8.12.7/Submit) id h8PCG8fx000383
for freebsd-doc@freebsd.org; Thu, 25 Sep 2003 14:16:08 +0200 (CEST)
(envelope-from shammer)
Date: Thu, 25 Sep 2003 14:16:08 +0200
From: Josef El-Rayes
To: freebsd-doc@freebsd.org
Message-ID: <20030925121608.GA352@daemon.li>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Reply-Path: j.el-rayes@daemon.li
X-Operating-System: FreeBSD 4.8-STABLE
X-Virus-Scanned: by AMaViS 0.3.12 with AC-networks extensions
Subject: article/mh: update from mh to nmh?
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: j.el-rayes@daemon.li
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Thu, 25 Sep 2003 12:15:30 -0000
hi!
while i was adding some tags to the article i noticed that mh is not
available for freebsd since 2002, as it has been removed because of a
security issue dating back to ~2000. i was wondering whether i should
update the article to reflect these changes, like:
>" If you installed from CDROM you should be able to execute the
>following to load mh:
># pkg_add /cdrom/packages/mh-6.8.3.tgz
should become a paragraph about installing port mail/nmh, and some other
little changes in the article.
what do you think of it?
-josef
--
www: http://www.daemon.li
nic-hdl: JER1080312-NICAT
BSD in AT: www.bsdcode.at
"Make World - Not War!"
From owner-freebsd-doc@FreeBSD.ORG Thu Sep 25 07:07:00 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 2A5DD16A4B3
for ; Thu, 25 Sep 2003 07:07:00 -0700 (PDT)
Received: from avocado.salatschuessel.net (avocado.salatschuessel.net
[80.86.187.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9C5043FF3
for ; Thu, 25 Sep 2003 07:06:58 -0700 (PDT)
(envelope-from oliver@freebsd.org)
Received: (qmail 69652 invoked from network); 25 Sep 2003 14:06:55 -0000
Received: from unknown (HELO dill.salatschuessel.net) (217.82.10.94)
by avocado.salatschuessel.net with AES256-SHA encrypted SMTP;
25 Sep 2003 14:06:55 -0000
Received: (qmail 20437 invoked from network); 25 Sep 2003 14:06:39 -0000
Received: from unknown (HELO kartoffel.salatschuessel.net) (10.0.1.51)
by dill.salatschuessel.net with SMTP; 25 Sep 2003 14:06:39 -0000
Date: Thu, 25 Sep 2003 16:06:39 +0200
From: Oliver Lehmann
To: doc@FreeBSD.org
Message-Id: <20030925160639.3db9d795.oliver@freebsd.org>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386-portbld-freebsd4.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: HP-UX online man pages are not displaying options
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Thu, 25 Sep 2003 14:07:00 -0000
Hi,
for example the manpage for whereis(1)
http://www.freebsd.org/cgi/man.cgi?query=whereis&apropos=0&sektion=0&manpath=HP-UX+11.00&format=html
As you can see, the options are not displayed right... maybe a formataing
error?
Greetings, Oliver
--
Oliver Lehmann
@home: lehmann@ans-netz.de
@office: oliver.lehmann@mgi.de
@www: http://www.pofo.de/ | http://wishlist.ans-netz.de/
From owner-freebsd-doc@FreeBSD.ORG Thu Sep 25 17:02:25 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id 0767E16A4B3; Thu, 25 Sep 2003 17:02:25 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP
id 48E4043FF9; Thu, 25 Sep 2003 17:02:24 -0700 (PDT)
(envelope-from mheinen@FreeBSD.org)
Received: from freefall.freebsd.org (mheinen@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8Q02OFY098075;
Thu, 25 Sep 2003 17:02:24 -0700 (PDT)
(envelope-from mheinen@freefall.freebsd.org)
Received: (from mheinen@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8Q02NL7098071;
Thu, 25 Sep 2003 17:02:24 -0700 (PDT)
(envelope-from mheinen)
Date: Thu, 25 Sep 2003 17:02:24 -0700 (PDT)
From: Martin Heinen
Message-Id: <200309260002.h8Q02NL7098071@freefall.freebsd.org>
To: apeiron@comcast.net, mheinen@FreeBSD.org,
freebsd-doc@FreeBSD.org, mheinen@FreeBSD.org
Subject: Re: docs/54197: Mentioning of devfs is missing in the German
handbook section about sound cards
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 26 Sep 2003 00:02:25 -0000
Synopsis: Mentioning of devfs is missing in the German handbook section about sound cards
State-Changed-From-To: open->analyzed
State-Changed-By: mheinen
State-Changed-When: Thu Sep 25 16:58:25 PDT 2003
State-Changed-Why:
This chapter is based on (the very old) revision 1.33
of sound/chapter.sgml. Short of time to translate it
now, there is not much I could do.
Disconnecting it from the build would be an option,
if you feel the chapter is too outdated.
Responsible-Changed-From-To: freebsd-doc->mheinen
Responsible-Changed-By: mheinen
Responsible-Changed-When: Thu Sep 25 16:58:25 PDT 2003
Responsible-Changed-Why:
Over to me.
http://www.freebsd.org/cgi/query-pr.cgi?pr=54197
From owner-freebsd-doc@FreeBSD.ORG Thu Sep 25 20:56:55 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id 68E9316A4BF; Thu, 25 Sep 2003 20:56:55 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP
id D1E8D43FE9; Thu, 25 Sep 2003 20:56:54 -0700 (PDT)
(envelope-from kensmith@FreeBSD.org)
Received: from freefall.freebsd.org (kensmith@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8Q3usFY061718;
Thu, 25 Sep 2003 20:56:54 -0700 (PDT)
(envelope-from kensmith@freefall.freebsd.org)
Received: (from kensmith@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8Q3uswa061714;
Thu, 25 Sep 2003 20:56:54 -0700 (PDT)
(envelope-from kensmith)
Date: Thu, 25 Sep 2003 20:56:54 -0700 (PDT)
From: Ken Smith
Message-Id: <200309260356.h8Q3uswa061714@freefall.freebsd.org>
To: kensmith@FreeBSD.org, freebsd-doc@FreeBSD.org,
kensmith@FreeBSD.org
Subject: Re: docs/55613: su man page confusing, probably incorrect
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 26 Sep 2003 03:56:55 -0000
Synopsis: su man page confusing, probably incorrect
Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Thu Sep 25 20:55:23 PDT 2003
Responsible-Changed-Why:
I'll give this one a try.
http://www.freebsd.org/cgi/query-pr.cgi?pr=55613
From owner-freebsd-doc@FreeBSD.ORG Fri Sep 26 02:09:42 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id CD3DE16A4BF; Fri, 26 Sep 2003 02:09:42 -0700 (PDT)
Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13])
by mx1.FreeBSD.org (Postfix) with ESMTP
id 4BE6144003; Fri, 26 Sep 2003 02:09:41 -0700 (PDT)
(envelope-from wosch@cs.tu-berlin.de)
Received: from freno.cs.tu-berlin.de (wosch@freno.cs.tu-berlin.de
[130.149.17.167])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id LAA12698;
Fri, 26 Sep 2003 11:08:26 +0200 (MET DST)
Received: (from wosch@localhost)
by freno.cs.tu-berlin.de (8.9.3/8.9.3) id LAA23112;
Fri, 26 Sep 2003 11:08:26 +0200 (MET DST)
Date: Fri, 26 Sep 2003 11:08:26 +0200
From: Wolfram Schneider
To: "Gerald S. Stoller"
Message-ID: <20030926090825.GA23084@freno.cs.tu-berlin.de>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To:
User-Agent: Mutt/1.4.1i
cc: freebsd-doc@freebsd.org
cc: wosch@freebsd.org
cc: gs_stoller@juno.com
Subject: Re: man pages
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 26 Sep 2003 09:09:42 -0000
On 2003-09-26 01:50:52 -0400, Gerald S. Stoller wrote:
> I have noticed some problems with several man pages (in FreeBSD )
> but I don't know to whom to complain and send suggestions for correction.
> Looking at the man pages section of the FreeBSD website, your email
> address popped up. Are you the person with whom to confer about this? If
> not, can you please send me info about how to find the email address of the
> person responsible for a particular man page.
> Organizationally, I feel that FreeBSD should have email addresses
> for several topics (e.g., man-page@FreeBSD.org , kernel@FreeBSD.org
> , file-system@FreeBSD.org [included in the previous, but still logically
> distinct], boot@FreeBSD.org , ksh@FreeBSD.org , pdksh@FreeBSD.org , etc.)
> and have someone familiar with the topic and the personnel who maintain the
> topic monitor the mail drop of that topic to send the email to the
> appropriate person who could fix the problem.
Hi Gerald,
a FreeBSD mailinglist Summary is available at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL
if you found a bug in a manpage, please send your comments or the patch
to freebsd-bugs@freebsd.org or freebsd-doc@freebsd.org
-Wolfram
--
Wolfram Schneider http://wolfram.schneider.org
From owner-freebsd-doc@FreeBSD.ORG Fri Sep 26 20:12:22 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id 460BB16A4B3; Fri, 26 Sep 2003 20:12:22 -0700 (PDT)
Received: from tomts23-srv.bellnexxia.net (tomts23-srv.bellnexxia.net
[209.226.175.185]) by mx1.FreeBSD.org (Postfix) with ESMTP
id A5DF44402F; Fri, 26 Sep 2003 20:12:20 -0700 (PDT)
(envelope-from dmagda@magda.ca)
Received: from number6.magda.ca ([64.229.177.29])
by tomts23-srv.bellnexxia.netESMTP
<20030927023906.DHNX28694.tomts23-srv.bellnexxia.net@number6.magda.ca>;
Fri, 26 Sep 2003 22:39:06 -0400
Received: from number6.magda.ca (localhost.magda.ca [127.0.0.1])
by number6.magda.ca (8.12.9/8.12.9) with ESMTP id h8R2caxw002422
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri,: 38:36 -0400 (EDT)
(envelope-from dmagda@magda.ca)
Received: (from dmagda@localhost)
by number6.magda.ca (8.12.9/8.12.9/Submit) id h8R2caUF002421;
Fri,: 38:36 -0400 (EDT)
(envelope-from dmagda)
Date: Fri, 26 Sep 2003 22:38:36 -0400
From: David Magda
To: emoore@freebsd.org
Message-ID: <20030927023835.GA2383@number6.magda.ca>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
cc: docs@freebsd.org
cc: simon@freebsd.org
Subject: amr(4) and Perc4/DI support
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: David Magda
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sat, 27 Sep 2003 03:12:22 -0000
--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hello,
Rev. 1.1.2.8 of src/sys/dev/amr/amr_pci.c added support for the Dell
Perc4/DI but this is not mentioned in amr(4) or in the hardware
notes. Support for the PERC 3/DCL was added about 5 weeks ago but
this slipped through even though the code was added 9 months ago.
Perhaps someone could add a note?
--=20
David Magda , http://www.magda.ca/
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well=20
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI
--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE/dPgr2MrIoZGj+vYRAiMuAJwK6HUOuCwxseJCGOnw4mTQCEstLwCfRq15
3qyAeT4Xd09MXyRTgH5yI8k=
=l48/
-----END PGP SIGNATURE-----
--YZ5djTAD1cGYuMQK--
From owner-freebsd-doc@FreeBSD.ORG Fri Sep 26 07:25:13 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id DEEB116A4B3
for ; Fri, 26 Sep 2003 07:25:13 -0700 (PDT)
Received: from mailserver.projesom.com.br (mailserver.projesom.com.br
[200.251.161.13])
by mx1.FreeBSD.org (Postfix) with SMTP id 83B0144061
for ; Fri, 26 Sep 2003 07:25:03 -0700 (PDT)
(envelope-from alexprj@projesom.net)
Received: (qmail 18175 invoked from network); 26 Sep 2003 14:24:52 -0000
Received: from unknown (HELO Alex) (172.16.4.253)
by mailserver.projesom.com.br with SMTP; 26 Sep 2003 14:24:52 -0000
Message-ID: <006101c3843a$9aa3c6e0$fd0410ac@projesom.com.br>
From: "Alex"
To:
Date: Fri, 26 Sep 2003 11:29:31 -0300
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailman-Approved-At: Sat, 27 Sep 2003 06:51:51 -0700
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
Subject: questions about ICradius
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Fri, 26 Sep 2003 14:25:14 -0000
Which the configurations necessary to connect the InterNet atraves di a =
server and to legalize remotely in another server through the ICRadius?
From owner-freebsd-doc@FreeBSD.ORG Sat Sep 27 11:08:37 2003
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP
id 9D06B16A4B3; Sat, 27 Sep 2003 11:08:37 -0700 (PDT)
Received: from arthur.nitro.dk (port324.ds1-khk.adsl.cybercity.dk
[212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP
id 91DE24403F; Sat, 27 Sep 2003 11:08:36 -0700 (PDT)
(envelope-from simon@arthur.nitro.dk)
Received: by arthur.nitro.dk (Postfix, from userid 1000)
id 49EF610BF8C; Sat, 27 Sep 2003 20:08:35 +0200 (CEST)
Date: Sat, 27 Sep 2003 20:08:35 +0200
From: "Simon L. Nielsen"
To: David Magda
Message-ID: <20030927180833.GA844@FreeBSD.org>
References: <20030927023835.GA2383@number6.magda.ca>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG"
Content-Disposition: inline
In-Reply-To: <20030927023835.GA2383@number6.magda.ca>
User-Agent: Mutt/1.5.4i
cc: docs@freebsd.org
cc: emoore@freebsd.org
Subject: Re: amr(4) and Perc4/DI support
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sat, 27 Sep 2003 18:08:37 -0000
--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2003.09.26 22:38:36 -0400, David Magda wrote:
>=20
> Rev. 1.1.2.8 of src/sys/dev/amr/amr_pci.c added support for the Dell
> Perc4/DI but this is not mentioned in amr(4) or in the hardware
> notes. Support for the PERC 3/DCL was added about 5 weeks ago but
> this slipped through even though the code was added 9 months ago.
>=20
> Perhaps someone could add a note?
I just added it to the manual page in -CURRENT, and I plan to MFC after
4.9.
Thanks for reporting it.
--=20
Simon L. Nielsen
FreeBSD Documentation Team
--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/ddIhh9pcDSc1mlERAosHAKCvppIfiIdJ7UiCtv8pQpcMgo4roACglb+b
ZRidQWtiZy4b6N9avGkvQuI=
=z04U
-----END PGP SIGNATURE-----
--OgqxwSJOaUobr8KG--
From owner-freebsd-doc@FreeBSD.ORG Sat Sep 27 15:20:14 2003
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 2CCFD16A4EE
for ;
Sat, 27 Sep 2003 15:20:14 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP id 1BCA844003
for ;
Sat, 27 Sep 2003 15:20:12 -0700 (PDT)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h8RMKCFY025660
for ;
Sat, 27 Sep 2003 15:20:12 -0700 (PDT)
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h8RMKCl5025659;
Sat, 27 Sep 2003 15:20:12 -0700 (PDT)
(envelope-from gnats)
Resent-Date: Sat, 27 Sep 2003 15:20:12 -0700 (PDT)
Resent-Message-Id: <200309272220.h8RMKCl5025659@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-doc@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
Dan Pelleg
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 963EB16A4B3
for ;
Sat, 27 Sep 2003 15:19:02 -0700 (PDT)
Received: from gw.pelleg.org (gw.pelleg.org [205.201.13.235])
by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3144402B
for ;
Sat, 27 Sep 2003 15:18:54 -0700 (PDT)
(envelope-from dpelleg@cs.cmu.edu)
Received: from lank.here (lank.wburn [192.168.3.41])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(Client CN "gw.pelleg.org", Issuer "Dan Pelleg" (verified OK))
by gw.pelleg.org (Postfix) with ESMTP id 8C0D95A3A
for ;
Sat, 27 Sep 2003 18:18:52 -0400 (EDT)
Received: by lank.here (Postfix, from userid 7675)
id B853AB4A; Sat, 27 Sep 2003 18:18:49 -0400 (EDT)
Message-Id: <20030927221849.B853AB4A@lank.here>
Date: Sat, 27 Sep 2003 18:18:49 -0400 (EDT)
From: Dan Pelleg
To: FreeBSD-gnats-submit@FreeBSD.org
X-Send-Pr-Version: 3.113
Subject: docs/57298: Using compact flash cards
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Dan Pelleg
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sat, 27 Sep 2003 22:20:14 -0000
>Number: 57298
>Category: docs
>Synopsis: Using compact flash cards
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Sat Sep 27 15:20:11 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Dan Pelleg
>Release: FreeBSD 4.9-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD l 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Tue Sep 16 20:15:41 EDT 2003 d@p i386
>Description:
How to use removable media cards under FreeBSD. This is a lightly edited version
of a Daemon News article I wrote (published in the May 2003 issue).
Submitted as an addition to the multimedia chapter of the handbook,
although I'm not 100% sure there is no better place for it.
>How-To-Repeat:
>Fix:
--- en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml.orig Fri Sep 26 20:33:58 2003
+++ en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml Sat Sep 27 18:03:44 2003
@@ -1409,4 +1409,382 @@
+
+
+
+
+
+ Dan
+ Pelleg
+ Contributed by
+
+
+
+
+
+
+ Using Removable Memory Devices
+
+ Many consumer electronic devices now support removable memory
+ cards. They provide a fast and easy way to transfer information to
+ and from a PC. Here we explore the ways to use those cards under
+ &os;. Our goal is to minimize the administrative overhead for the
+ user - eliminating the need for root access or
+ manual mounts. For simple tasks such as uploading files from the
+ card we can even come up with a completely hands-off operation -
+ the user doesn't have to do anything but insert the card in, wait
+ for a while, and then pop it back out.
+
+
+ Introduction
+
+ The discussion refers to Compact Flash (CF) cards. However,
+ most of the instructions also apply, with slight modifications,
+ to other types of 'flash' media (SmartMedia, MMC, MemoryStick and
+ all their variations), as well as cameras, MP3 players, and other
+ devices supported by the &man.umass.4 device driver.
+
+ Compact Flash cards typically interface to a PC in one of
+ two ways: an external USB card-reader, or through the PC-CARD
+ (also known as "PCMCIA") slot. For the PC-CARD case, a cheap
+ adapter allows insertion of CF media to a standard PC-CARD slot.
+ Some laptops have a special CF slot, eliminating the need for an
+ adapter. The way &os; accesses your device will vary, depending
+ on the reader type. PC-CARD readers will show up as ATA disks,
+ while USB readers will show up as SCSI disks.
+
+ Once the "disks" show up, we can mount the filesystem on
+ them, and then manipulate it in the standard way - copying and
+ deleting files. We explore two approaches to doing this. The
+ first involves a script that handles the specific task of
+ uploading all of the new files from the CF card to the PC,
+ requiring no user intervention. The second is more general, and
+ uses the automounter to mount the filesystem as soon as it is
+ accessed, letting the user directly manipulate it.
+
+ To make things easy to follow, we first detail the steps
+ for USB readers, and then explain how the same procedures work
+ for PC-CARD devices.
+
+
+
+ USB-Based Compact-Flash Readers
+
+ Requirements
+
+ Support for USB readers requires the &man.umass.4
+ driver. As the manpage tells you, you will need the
+ following options in your kernel config:
+
+ device usb
+device ohci (OR device uhci)
+device umass
+device scbus
+device da
+device pass
+
+ Note that the GENERIC kernel that comes with 4.8
+ already includes them all. After recompiling your kernel
+ (or not, if you're using GENERIC), you should be able to
+ plug the reader into the USB slot and have it show up.
+ Usually, the media has to be already in the reader before
+ you plug in the USB connector. So, if things don't work
+ for you, unplug the reader from the USB slot, stick the
+ memory card in, and plug it into USB again.
+
+ The message log will tell you the device name for
+ the CF card. umass-attached
+ devices will show up like this:
+
+ da0 at umass-sim0 bus 0 target 0 lun 0
+
+ indicating that the device name is
+ da0. Note that if you already
+ have SCSI devices in the system, this might interfere
+ with whatever you have in &man.fstab.5;. To avoid nasty
+ surprises, you should wire down all of your other SCSI
+ devices so their numbering doesn't change.
+
+ If the reader is supported, at this point you
+ should be able to mount the device. If you are using a
+ card from a standard camera or music player, the
+ following command, typed as root, will mount it under
+ /mnt:
+
+ &prompt.root; mount -t msdos /dev/da0s1 /mnt
+
+ In theory, at this point you can become
+ root whenever you want and
+ mount the device. However the goal
+ here is to try and avoid this step. The following
+ section and describe two
+ different strategies that accomplish this.
+
+
+
+ Using an upload script
+
+ Most often, the computer is used as a backing store
+ for the small-capacity CF card. You take a few photos on
+ your digital camera, and want to make sure you have
+ copied them to a "real" disk so you can later process
+ them. We use a script that uploads all the new photos
+ from a CF card into the PC's disk-drive. Once installed,
+ it will go into action as soon as the CF media is
+ attached. It will mount the
+ filesystem, copy the new files over, and then unmount it.
+ The only thing the user has to do is insert the media and
+ later pull it out.
+
+ You can download a copy of the
+ script. We assume you have it installed at
+ /usr/local/sbin/copy-flash and
+ marked it as executable.
+
+ Next, you will need the USB daemon, &man.usbd.8;.
+ Add this line to /etc/rc.conf,
+ unless it's already there:
+
+ usbd_enable="YES"
+
+ To make the script run when a USB reader is
+ attached, add an entry to
+ /etc/usbd.conf. It will look like
+ this:
+
+ device "CF card"
+devname "umass[0-9]+"
+attach "/usr/local/sbin/copy-flash da0 /tmp/cf CFOWNER"
+
+ where da0 should be
+ substituted by whatever device you see in the message
+ log. Before you use this hook, replace the string
+ CFOWNER. It should be a user name, and the copied files
+ will be owned by that user. This is normally you or the
+ primary user of the machine. Also, create the target
+ directory into which the files will be copied. In this
+ example it is /tmp/cf. Make sure you
+ choose a partition that is big enough to contain all the
+ files you plan on using. Finally, don't forget to kill
+ and restart usbd.
+
+ The provided script will also sound a short melody
+ once the copying is done. This lets you know it is safe
+ to pull out the CF card. If you don't hear it, add the
+ &man.spkr.4 psuedo-device to your kernel.
+
+
+
+
+ PC-CARD readers
+
+ This section repeats the previous one, this time
+ explaining how to make a PC-CARD slot (or a dedicated CF
+ slot) work.
+
+
+ Requirements
+
+ Compared to USB readers, PC-CARD readers are
+ simpler. They only require the &man.pccardd.8 daemon
+ to run. In all likelihood, you already have it. If
+ not, add the following line to
+ /etc/rc.conf:
+
+ pccard_enable="YES"
+
+ Again, the message log will tell us the name of
+ the device. For example, one
+ pccardd-attached device shows up
+ as:
+
+ ad8: 124MB <SAMSUNG CF/ATA> [496/16/32] at ata4-master BIOSPIO
+
+ indicating that the device is ad8.
+
+
+
+ Using an upload script
+
+ The same script as
+ above can be used for PC-CARD readers. The only
+ difference is what runs it - in this case, it is
+ pccardd instead of
+ usbd. Add this entry to
+ /etc/pccardd.conf (create the file
+ if it doesn't exist on your system):
+
+ # GENERIC Flash ATA / ATA HDD
+ generic fixed_disk
+ config 0x1 "ata" ?
+ insert /usr/local/sbin/copy-flash $device /tmp/cf CFOWNER
+ logstr "GENERIC Flash ATA / ATA HDD"
+
+ Again, change CFOWNER to the name of the user you
+ want to have access to the files.
+
+
+
+ Using the automounter
+
+ Much of the information in this section is from a
+
+ Dæmon News article by Renaud Waldura . The
+ automounter can mount filesystems automatically whenever
+ they are accessed. That is, you simply
+ ls or cd to a
+ directory that represents a filesystem, and the
+ automounter intercepts the operation, and makes sure the
+ underlying filesystem is mounted. It is typically used
+ for managing NFS mounts, but here we use it for local
+ mounts.
+
+ Add these lines to /etc/amd.map:
+
+ localhost type:=auto;fs:=${map};pref:=${key}/
+
+localhost/cf type:=program;fs:=/mnt/cf;\
+ mount:="/sbin/mount mount /mnt/cf";\
+ unmount:="/sbin/umount umount /mnt/cf"
+
+ Next, add a line for the filesystem in
+ /etc/fstab. It will look like this,
+ assuming that in your system the reader appears as the
+ device /dev/ad8:
+
+/dev/ad8s1 /mnt/cf msdos rw,noauto 0 0
+
+ Note that we specify the first slice on the disk,
+ and the filesystem. Many digital
+ cameras expect their CF cards to be configured in this
+ way. We also need to create the mount point:
+
+ &prompt.root; mkdir -p /mnt/cf
+
+ To enable the automounter, add this line to
+ /etc/rc.conf:
+
+ portmap_enable=YES
+amd_enable="YES"
+amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map"
+
+ Once you start amd (or reboot),
+ any user should be able to access the CF card, simply by
+ doing a ls or cd on
+ the directory /host/localhost/cf
+
+ Remember that amd only unmounts
+ the filesystem after it has been idle for some time.
+ This means that before you take the CF card out of the
+ slot, you need to stop using it (remembering to
+ cd out of any directories on it), and
+ wait. Pulling out a mounted device can cause all kinds
+ of trouble, including data loss and system crashes. So
+ you want to make sure you unmount first. If you're in a
+ hurry and can't wait for amd to time
+ out, you can ask it to unmount the filesystem immediately
+ by doing:
+
+&prompt.user; amq -u /host/localhost/cf
+
+ This, again, is not a privileged operation and does
+ not require root access.
+
+
+
+ Summary
+
+ We eliminated the need for root access to read and
+ write files stored on CF media. We can let the
+ automounter do the mounting for us, or have a script that
+ does all the copying as well. In fact, both of these
+ solutions can co-exist: whenever media is inserted, new
+ files are immediately copied over. If the user later
+ wants to access the card and, say, delete some files,
+ they can do that and amd will take
+ care of mounting.
+
+ Once you start using the file-copy script, you will
+ probably discover that managing multiple copies of the
+ same data is hard. The original photo is kept on the CF
+ card, the script makes another one on your local disk,
+ and you will also probably make a final copy in your
+ electronic album. To make room and reduce clutter, you
+ will want to delete redundant copies. It is often
+ easiest to do this on the PC where you can easily view
+ the photos on a big screen. The problem is, the files
+ will re-appear the next time you pop the CF card in. One
+ solution is to wipe the CF card clean every time you
+ insert it. But it is wiser to give the good photos
+ another chance, just in case they get lost. A trick I
+ find useful is to create a text file in the directory
+ which stores the files from the CF card, and in that file
+ I record the name of each file that I delete from the PC
+ copy. This way, I can also quickly delete the same files
+ from the CF card whenever it fills up.
+
+
+
+ Acknowledgments
+
+ Scott Mitchell provided greatly valuable help for
+ this article. Thanks to Joshua Schachter and Nadav
+ Eiron.
+
+
+
+ Helper Script for Copying Files from CF Card
+ #!/bin/sh
+# Dan Pelleg, March 2003
+#
+# copy-flash: mount a compact-flash card, copy the contents over, unmount
+# usage: copy-flash [flash-device] [target-dir] [user]
+
+dev=${1:-da6}
+tgt=${2:-/tmp/foo}
+user=${3:-root}
+
+[ -e "$tgt" ] || mkdir -p $tgt && chown $user $tgt
+[ -e /mnt/cf ] || mkdir -p /mnt/cf
+
+# figure out if we were called with a device like ad8 or ata4. If it's
+# the latter, figure out the usable device name
+case ${dev} in
+ ata* )
+ channel=${dev##ata}
+
+ if [ -n ${channel} ]; then
+ realdev=$(atacontrol info $channel | grep ^Master | cut -d " " -f 3)
+ fi
+ ;;
+
+ ad* | da* )
+ realdev=${dev}
+ ;;
+esac
+
+if [ -n "${realdev}" ]; then
+ # on -CURRENT we might need to wait a bit before the device node appears
+ if [ ! -e /dev/${realdev} ]; then
+ sleep 5
+ fi
+ # if the slice doesn't yet exist, try to nudge
+ # things so it does. Might be necessary for some devices
+ # on -CURRENT
+ # This mount is not supposed to succeed, but it does
+ # sometime cause the device node to be created.
+ if [ ! -e /dev/${realdev}s1 ]; then
+ mount -t msdos /dev/${realdev} /mnt/cf && umount /mnt/cf
+ fi
+ mount -t msdos /dev/${realdev}s1 /mnt/cf && \
+ su ${user} -c "cp -nRp /mnt/cf/ ${tgt}" ; \
+ # play a tune to let the user know it's all over
+ umount /mnt/cf && echo "MLT250o3fc" > /dev/speaker
+fi
+
+
+
+
>Release-Note:
>Audit-Trail:
>Unformatted: