From jpb at sixshooter.v6.thrupoint.net  Wed Oct  1 00:36:41 2003
From: jpb at sixshooter.v6.thrupoint.net (Jim Brown)
Date: Tue, 30 Sep 2003 20:36:37 -0400
Subject: Quick review requested
In-Reply-To: <20030930180215.7438ba73.trhodes@FreeBSD.org>
References: <20030930180215.7438ba73.trhodes@FreeBSD.org>
Message-ID: <20031001003637.GB84749@sixshooter.v6.thrupoint.net>

* Tom Rhodes <trhodes at FreeBSD.org> [2003-09-30 18:03]:
> Gang,
> 
> I'd really appreciate some feedback on the text below.  If anyone
> would like the full patch (images, Makefile, etc) please speak up
> and I'll send it.
> 
> Whitespace in added text will be fixed before the initial cvs ci,
> so comments on short/long lines are not required.
> 
> Thanks!
> 
> -- 
> Tom Rhodes
> 


Comments inline- sorry.  I don't have my doc stuff set up on this system
so I can't check what it looks like visually.



> --- doc.old/en_US.ISO8859-1/books/handbook/install/chapter.sgml	Mon Sep 29 13:40:57 2003
> +++ doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml	Mon Sep 29 18:39:26 2003
> @@ -3382,6 +3382,233 @@
>  	post-installation configuration.</para>
>      </sect2>
>  
> +    <sect2 id="network-services">
> +      <title>Configure Additional Network Services</title>
> +
> +      <para>Configuring the network services can be a daunting
> +	task for new users if they lack any previous network configuration knowledge.
> +	Configuring a network
> +	is an important aspect of &os;, therefore users should at least
> +	have an understanding of various services available to them.</para>

"Configuring the network..." followed by "configuration" followed by "Configuring the network.."
is somewhat repetitive.  Can you choose a different word or make it flow
a bit better?  Also '... the network ...' followed by '... a netowrk ...' seemed
to clash for me.  Might be just too much coffee though.




> +
> +      <para>Selecting the <quote>Networking</quote> option will bring forth a menu
> +	similar to the one below:</para>

s/bring forth/display/
seems a bit better to me.


> +
> +      <figure id="network-configuration">
> +	<title>Network Configuration Upper-level</title>
> +
> +	<mediaobject>
> +	  <imageobject>
> +	    <imagedata fileref="install/net-config-menu1" format="PNG">
> +	  </imageobject>
> +	</mediaobject>
> +      </figure>
> +
> +      <para>The first option, Interfaces, was previously covered during
> +	the Network Device Configuration section; thus we can bypass
> +	this option.</para>

You are in the first person here.



> +
> +      <para>Selecting the <option>AMD</option> option adds
> +	support for the <acronym>BSD</acronym> auto mount utility.
> +	This is usually used in conjunction with the
> +	<acronym>NFS</acronym> protocol (see below)
> +	for automatically mounting remote file systems.
> +	No special configuration
> +	is required here.</para>
> +
> +      <para>Next in line is the <acronym>AMD</acronym> flags
> +	option.  When selected, a menu will pop up for you
> +	to enter specific <acronym>AMD</acronym> flags.
> +	The menu already contains a set of default options:</para>
> +
> +      <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map</screen>
> +
> +      <para>The <literal>-a</literal> option specifies the default mount
> +	location which is listed here as <filename>/.amd_mnt</filename>.
> +	The <literal>-l</literal> option specifies the default
> +	<filename>log</filename> file; however, when &man.syslogd.8; is

I would use <literal>syslog</literal> here.  The option should never look
like 'syslog(8)'.  Might confuse a newbie.


> +	specified all log activity will be sent to the system log daemon.
> +	The <filename>/host</filename> is used to mount an exported
> +	file system from a remote hostname, while
> +	<filename>/net</filename> is used to mount an exported file
> +	system from an <acronym>IP</acronym> address.  The
> +	<filename>/etc/amd.map</filename> defines the default options
> +	for <acronym>AMD</acronym> exports.</para>
> +
> +      <para>The Anon <acronym>FTP</acronym> should be
> +	self explanatory.  Select this option to permit anonymous

If I'm a newbie, I won't know what is self explanatory.  I would offer:
"<para>The Anon <acronym>FTP</acronym> option permits anonymous ..."
or something similar.


> +	<acronym>FTP</acronym> logins.  Be aware of the security risks
> +	involved with this option.  Another menu will be displayed to
> +	explain the security risks and configuration in depth.</para>
> +
> +      <para>The <option>Gateway</option> configuration menu will set
> +	the machine up to be a gateway as explained previously.  This
> +	can be used to unset the gateway option if you accidentally
> +	selected it during the installation process.</para>
> +
> +      <para>The <option>Inetd</option> option can be used to configure or
> +	completely disable the &man.inetd.8; daemon as discussed above.</para>
> +
> +      <para>The <option>Mail</option> is used to configure the system's
> +	default <acronym>MTA</acronym> or mail server.  Selecting this
> +	option will bring forth the following menu:</para>
> +
> +      <figure id="mta-selection">
> +	<title>Select a default MTA</title>
> +
> +	<mediaobject>
> +	  <imageobject>
> +	    <imagedata fileref="install/mta-main" format="PNG">
> +	  </imageobject>
> +	</mediaobject>
> +      </figure>
> +
> +      <para>Here the user is given a choice as to which
> +	<acronym>MTA</acronym>, or Mail Transfer Agent to install
> +	and set as the default.  An <acronym>MTA</acronym> is nothing
> +	more than a mail server which delivers email to users on the
> +	system or the Internet.</para>
> +
> +      <para>Selecting <application>Sendmail</application> will install
> +	the popular <application>Sendmail</application> server which
> +	is the &os; default.  The <option>Sendmail local</option> option
> +	will set <application>Sendmail</application> to be the default
> +	<acronym>MTA</acronym>, but disables its ability to receive
> +	incoming email from the Internet.  The other options here,
> +	<application>Postfix</application> and
> +	<application>Exim</application> act similar to
> +	<application>Sendmail</application>, as in they both deliver

"as in they both" doesn't work for me.  Perhaps:

"<application>Sendmail</application>. They both deliver ..."


> +	email; however, selecting either of these is more of a user
> +	preference than anything else.</para>
> +
> +      <para>After selecting an <acronym>MTA</acronym>, or choosing
> +	not to select an MTA, we are back at the default menu with

First person.  See note at end.


> +	the next option being <acronym>NFS</acronym> client.</para>
> +
> +      <para>The <acronym>NFS</acronym> client will
> +	set the machine to work as a client for an
> +	<acronym>NFS</acronym> server.  An <acronym>NFS</acronym> server
> +	exports remotely mounted file systems to other machines on the local
> +	network via the <acronym>NFS</acronym> protocol.  If this is
> +	a stand alone machine, this option can remain unselected.  The
> +	system may require more configuration later, see
> +	<xref linkend="network-nfs"> for more
> +	information about client and server configuration.</para>
> +
> +      <para>Below that option is the
> +	<acronym>NFS</acronym> server option,
> +	permitting a user to set the system up as an
> +	<acronym>NFS</acronym> server.  This adds the required
> +	information to start up the <acronym>RPC</acronym> remote
> +	procedure call services.  <acronym>RPC</acronym> is used to
> +	coordinate connections between hosts and programs.</para>
> +
> +      <para>Next in line is the <option>Ntpdate</option> option,
> +	which deals with time synchronization.  When selected, a menu
> +	like the one below shows up:</para>
> +
> +      <figure id="Ntpdate-config">
> +	<title>Ntpdate Configuration</title>
> +
> +	<mediaobject>
> +	  <imageobject>
> +	    <imagedata fileref="install/ntp-config" format="PNG">
> +	  </imageobject>
> +	</mediaobject>
> +      </figure>
> +
> +      <para>From this menu, select the server which is the closest
> +	to your location.  Selecting a close one will make the time
> +	synchronization more accurate as a server further from your
> +	location may have more connection latency.</para>
> +
> +      <para>Our next option is the
> +	<acronym>PCNFSD</acronym> selection.  This
> +	option will install the
> +	<filename role="package">net/pcnfsd</filename> package from
> +	the ports collection.  This is a useful utility which provides
> +	<acronym>NFS</acronym> authentication services for systems which
> +	are unable to provide their own.  For instance, Microsoft's
> +	<acronym>DOS</acronym> operating system.</para>
> +
> +      <para>Now we must scroll down a bit to see the other options:</para>
> +
> +      <figure id="Network-configuration-cont">
> +	<title>Network Configuration Lower-level</title>
> +
> +	<mediaobject>
> +	  <imageobject>
> +	    <imagedata fileref="install/net-config-menu2" format="PNG">
> +	  </imageobject>
> +	</mediaobject>
> +      </figure>
> +
> +      <para>The &man.rpcbind.8;, &man.rpc.statd.8;, and
> +	&man.rpc.lockd.8; utilities are all used for Remote Procedure
> +	Calls (<acronym>RPC</acronym>).  The <command>rpcbind.8</command>
> +	utility handles the communication between <acronym>NFS</acronym>
> +	servers, their clients, and is required for
> +	<acronym>NFS</acronym> servers to operate correctly.  The
> +	<command>rpc.statd</command> daemon interacts with the
> +	<command>rpc.statd</command> daemon on other hosts to provide
> +	status monitoring.  The reported status is usually held in the
> +	<filename>/var/db/statd.status</filename> file.  The final
> +	option listed here is the <command>rpc.lockd</command> option,
> +	which, when selected, will provide for file locking.  This is
> +	usually used with <command>rpc.statd</command> to monitor what
> +	hosts are requesting locks and how frequent they request them.
> +	While these last two options are marvelous for debugging, they
> +	are not required for <acronym>NFS</acronym> servers and clients
> +	to operate correctly.</para>
> +
> +      <para>As we progress down the list the next item here is
> +	<option>Routd</option>, which is the route daemon.  The

Is the option really 'Routd' or 'Routed'?  I don't have a way to check
this at the moment.

> +	&man.routed.8; utility manages the network routing tables,
> +	discovers multicast routers, and supplies a copy of the routing
> +	tables to any physically connected host on the network upon
> +	request.  This is mainly used for routing
> +	<quote>connectionless</quote> protocols (see &man.icmp.4 and
> +	&man.udp.4;).  When selected, a menu will be presented
> +	requesting the default location of the utility.  The default
> +	location is already defined for you and can be selected with
> +	the <keycap>Enter</keycap> key.  You will then be presented
> +	with yet another menu, this time asking for the flags you wish
> +	to be passed on to <command>routed</command>.  The default is
> +	<literal>-q</literal> and it should already appear on the
> +	screen.</para>
> +
> +      <para>Next in line is the <option>Rwhod</option> option which,
> +	when selected, will have the &man.rwhod.8; daemon start up
> +	during system initialization.  The <command>rwhod</command>
> +	utility broadcasts system messages across the network
> +	periodically, or collects them when in <quote>consumer</quote>
> +	mode.  This utility is great for monitoring the status of
> +	machines on the network, but can be highly annoying when in
> +	<quote>producer mode</quote> as it will broadcast messages
> +	every three minutes or so.</para>
> +
> +      <para>Next to the last option in the list we have the

Usually seen as:

<para>The next to last option in the list we have the ...



> +	&man.sshd.8; daemon.  This is the secure shell server for
> +	<application>OpenSSH</application> and it is highly recommended
> +	over the standard <command>telnet</command> and
> +	<acronym>FTP</acronym> servers.  The <command>sshd</command>
> +	server is used to create a secure connection from one host to
> +	another by using encryption connections.</para>

s/encryption/encrypted/
seems better to me.


> +
> +      <para>Finally there is the <acronym>TCP</acronym> Extensions
> +	option.  This enables the <acronym>TCP</acronym> Extensions
> +	as defined by <acronym>RFC</acronym>&nbsp;1323 and
> +	<acronym>RFC</acronym>&nbsp;1644.  While on many hosts this can
> +	speed up connections, but can also cause some connections to

s/but/it/
seems better to me.


> +	or be dropped.  It is not recommended for servers but may be

s/or//


> +	beneficial for stand alone machines.</para>
> +
> +      <para>Now that we have configured the network services, we can
> +	scroll up to the very top item which is <option>Exit</option>
> +	and continue on to the next configuration section.</para>
> +
> +    </sect2>
> +
>      <sect2 id="x-server">
>        <title>Configure X Server</title>


General Note:

The text fluctuates between first, second, and third  person- sometimes in
close proximity.  You may wish to review this as it causes an unnecessary
shift in perspective for the reader.


Quite a good effort overall.

As always all comments meant with Best Regards,

jpb
===



From kensmith at cse.Buffalo.EDU  Wed Oct  1 01:00:43 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue, 30 Sep 2003 18:00:42 -0700 (PDT)
Subject: docs/57434: Typo in pthread_mutex_init manpage
Message-ID: <200310010100.h9110gl4081789@freefall.freebsd.org>

The following reply was made to PR docs/57434; it has been noted by GNATS.

From: Ken Smith <kensmith at cse.Buffalo.EDU>
To: Benjamin Lutz <benlutz at datacomm.ch>
Cc: FreeBSD-gnats-submit at freebsd.org
Subject: Re: docs/57434: Typo in pthread_mutex_init manpage
Date: Tue, 30 Sep 2003 20:56:37 -0400

 On Wed, Oct 01, 2003 at 01:23:33AM +0200, Benjamin Lutz wrote:
 
 > >Description:
 > There's a typo in the pthread_mutex_init manpage. In the ERRORS section,
 > at [EAGAIN], the text reads "The temporarily lacks the resources..."
 > when it (I assume) should read "The process temporarily lacks...".
 > >How-To-Repeat:
 > man pthread_mutex_init
 > 
 
 I checked the definition of pthread_mutex_init in:
 
 	-current /usr/src/lib/libpthread/thread/thr_mutex.c
 	-stable /usr/src/lib/libc_r/uthread/uthread_mutex.c
 
 Unless I missed something neither is capable of returning EAGAIN.
 The other errors listed in the manpage are possible. :-)
 
 Is there a procedure for following up on this with a developer to
 make sure I'm not mistaken?
 
 -- 
 						Ken Smith
 - From there to here, from here to      |       kensmith at cse.buffalo.edu
   there, funny things are everywhere.   |
                       - Theodore Geisel |


From chern at FreeBSD.org  Wed Oct  1 02:00:14 2003
From: chern at FreeBSD.org (Chern Lee)
Date: Tue, 30 Sep 2003 19:02:43 -0700 (PDT)
Subject: Binary Formats in UNIX Basics
Message-ID: <20030930190117.W63397@mall.freebsdmall.com>

Section 3.12, Binary Formats,
http://www.FreeBSD.org/doc/handbook/binary-formats.html, surely doesn't
belong in the UNIX Basics chapter.

I believe it is probably more appropriate somewhere in the Appendix, but
we don't have an appropriate section there either.

Any suggestions on where it belongs?

- chern


From kensmith at cse.Buffalo.EDU  Wed Oct  1 02:10:32 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue, 30 Sep 2003 22:10:29 -0400
Subject: Binary Formats in UNIX Basics
In-Reply-To: <20030930190117.W63397@mall.freebsdmall.com>
References: <20030930190117.W63397@mall.freebsdmall.com>
Message-ID: <20031001021029.GC28258@electra.cse.Buffalo.EDU>

On Tue, Sep 30, 2003 at 07:02:43PM -0700, Chern Lee wrote:
> Section 3.12, Binary Formats,
> http://www.FreeBSD.org/doc/handbook/binary-formats.html, surely doesn't
> belong in the UNIX Basics chapter.
> 
> I believe it is probably more appropriate somewhere in the Appendix, but
> we don't have an appropriate section there either.
> 
> Any suggestions on where it belongs?

I'm not totally sure, but PR docs/54461 has some extra stuff that
could be added to it where it sits now that makes it a *little*
more introductory in nature.  :-)

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From pepper at reppep.com  Wed Oct  1 04:17:52 2003
From: pepper at reppep.com (Chris Pepper)
Date: Wed, 1 Oct 2003 00:13:44 -0400
Subject: Quick review requested
In-Reply-To: <20030930180215.7438ba73.trhodes@FreeBSD.org>
References: <20030930180215.7438ba73.trhodes@FreeBSD.org>
Message-ID: <p06100302bb9ffc71a931@[66.92.104.201]>

At 6:02 PM -0400 2003/09/30, Tom Rhodes wrote:

Tom,

	As someone who went through the options tonight, I found this 
very helpful. I have lots of niggles, though...

>--- doc.old/en_US.ISO8859-1/books/handbook/install/chapter.sgml 
>	Mon Sep 29 13:40:57 2003
>+++ doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml	Mon 
>Sep 29 18:39:26 2003
>@@ -3382,6 +3382,233 @@
>  	post-installation configuration.</para>
>      </sect2>
>
>+    <sect2 id="network-services">
>+      <title>Configure Additional Network Services</title>
>+
>+      <para>Configuring the network services can be a daunting

	s/the network/network/ (any network services; not a canonical set)

>+	task for new users if they lack any previous network 
>configuration knowledge.

	s/lack any previous/lack previous/ (people might have some, 
but still be intimidated)

>+	Configuring a network
>+	is an important aspect of &os;, therefore users should at least
>+	have an understanding of various services available to them.</para>

	Nah, networking is an important aspect of FreeBSD; 
configuring a network is an important aspect of managing a FBSD 
system.

	I actually think "have an understanding of various services" 
is too ambitious -- most users don't know about most of the network 
ports that are available. How about:

	Networking (including the Internet) is critical to all modern 
operating systems, including &os;; as a result, it's very useful to 
have some understanding &os;'s extensive networking capabilities.

>+      <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net 
>/etc/amd.map</screen>
>+
>+      <para>The <literal>-a</literal> option specifies the default mount
>+	location which is listed here as <filename>/.amd_mnt</filename>.

	s/location which is listed/location, which is specified/

>+	The <literal>-l</literal> option specifies the default
>+	<filename>log</filename> file; however, when &man.syslogd.8; is
>+	specified all log activity will be sent to the system log daemon.
>+	The <filename>/host</filename> is used to mount an exported

	s/is used/argument is used/

>+	file system from a remote hostname, while

	s/hostname,/host,/

>+	<filename>/net</filename> is used to mount an exported file
>+	system from an <acronym>IP</acronym> address.  The
>+	<filename>/etc/amd.map</filename> defines the default options

	s/defines/file defines/

>+	for <acronym>AMD</acronym> exports.</para>

>+      <para>The <option>Mail</option> is used to configure the system's

	s/is/option is/

>+	default <acronym>MTA</acronym> or mail server.  Selecting this

	s/<acronym>MTA</acronym> or/<acronym>MTA</acronym>, "Mail 
Transport Agent, or/ (spell it out the first time, not later)

>+	option will bring forth the following menu:</para>

	s/forth/up/

>+      <para>Selecting <application>Sendmail</application> will install
>+	the popular <application>Sendmail</application> server which
>+	is the &os; default.  The <option>Sendmail local</option> option
>+	will set <application>Sendmail</application> to be the default
>+	<acronym>MTA</acronym>, but disables its ability to receive

	s/disables/disable/

>+	incoming email from the Internet.  The other options here,
>+	<application>Postfix</application> and
>+	<application>Exim</application> act similar to

	s/<application>Exim</application> 
act/<application>Exim</application>, act/

>+	<application>Sendmail</application>, as in they both deliver

	s/as in/in that/

>+	email; however, selecting either of these is more of a user
>+	preference than anything else.</para>

	s/selecting either of these is more of a user preference than 
anything else./some people prefer these alternatives to the Sendmail 
MTA.

>+      <para>The <acronym>NFS</acronym> client will
>+	set the machine to work as a client for an
>+	<acronym>NFS</acronym> server.  An <acronym>NFS</acronym> server

	s/set the machine to work as a client for an 
<acronym>NFS</acronym> server./configures the system to communicate 
with a server via <acronym>NFS</acronym>.

>+	exports remotely mounted file systems to other machines on the local

	s/exports remotely mounted file systems/makes file systems available/
	s/local//

>+	network via the <acronym>NFS</acronym> protocol.  If this is
>+	a stand alone machine, this option can remain unselected.  The
>+	system may require more configuration later, see

	s/later, see/later; see/

>+	<xref linkend="network-nfs"> for more
>+	information about client and server configuration.</para>

>+      <para>Our next option is the
>+	<acronym>PCNFSD</acronym> selection.  This
>+	option will install the
>+	<filename role="package">net/pcnfsd</filename> package from
>+	the ports collection.  This is a useful utility which provides
>+	<acronym>NFS</acronym> authentication services for systems which
>+	are unable to provide their own.  For instance, Microsoft's

	s/their own.  For instance,/their own, such as/

>+	<acronym>DOS</acronym> operating system.</para>

>+      <para>The &man.rpcbind.8;, &man.rpc.statd.8;, and
>+	&man.rpc.lockd.8; utilities are all used for Remote Procedure
>+	Calls (<acronym>RPC</acronym>).  The <command>rpcbind.8</command>
>+	utility handles the communication between <acronym>NFS</acronym>

	s/handles the communication/manages communication/

>+	servers, their clients, and is required for

	s/servers, their clients/servers and clients/

>+	<acronym>NFS</acronym> servers to operate correctly.  The
>+	<command>rpc.statd</command> daemon interacts with the
>+	<command>rpc.statd</command> daemon on other hosts to provide
>+	status monitoring.  The reported status is usually held in the
>+	<filename>/var/db/statd.status</filename> file.  The final
>+	option listed here is the <command>rpc.lockd</command> option,
>+	which, when selected, will provide for file locking.  This is

	s/will provide for for file locking./provides file locking services./

>+	usually used with <command>rpc.statd</command> to monitor what
>+	hosts are requesting locks and how frequent they request them.

	/frequent/frequently/

>+	While these last two options are marvelous for debugging, they
>+	are not required for <acronym>NFS</acronym> servers and clients
>+	to operate correctly.</para>
>+
>+      <para>As we progress down the list the next item here is
>+	<option>Routd</option>, which is the route daemon.  The

	s/Routd/Routed/
	s/route daemon./routing daemon./

>+	&man.routed.8; utility manages the network routing tables,

	s/the network/network/ (other programs may manage such tables 
separately)

>+	discovers multicast routers, and supplies a copy of the routing
>+	tables to any physically connected host on the network upon
>+	request.  This is mainly used for routing
>+	<quote>connectionless</quote> protocols (see &man.icmp.4 and
>+	&man.udp.4;).  When selected, a menu will be presented
>+	requesting the default location of the utility.  The default
>+	location is already defined for you and can be selected with
>+	the <keycap>Enter</keycap> key.  You will then be presented
>+	with yet another menu, this time asking for the flags you wish
>+	to be passed on to <command>routed</command>.  The default is

	s/to be passed on to/to pass on/

>+	<literal>-q</literal> and it should already appear on the
>+	screen.</para>
>+
>+      <para>Next in line is the <option>Rwhod</option> option which,
>+	when selected, will have the &man.rwhod.8; daemon start up

	s/will have the &man.rwhod.8; daemon start up/will start the 
&man.rwhod.8; daemon/

>+	during system initialization.  The <command>rwhod</command>
>+	utility broadcasts system messages across the network
>+	periodically, or collects them when in <quote>consumer</quote>
>+	mode.  This utility is great for monitoring the status of
>+	machines on the network, but can be highly annoying when in
>+	<quote>producer mode</quote> as it will broadcast messages
>+	every three minutes or so.</para>
>+
>+      <para>Next to the last option in the list we have the
>+	&man.sshd.8; daemon.  This is the secure shell server for
>+	<application>OpenSSH</application> and it is highly recommended
>+	over the standard <command>telnet</command> and
>+	<acronym>FTP</acronym> servers.  The <command>sshd</command>
>+	server is used to create a secure connection from one host to
>+	another by using encryption connections.</para>

	s/another by using encryption connections/another using 
encrypted connections/
	or /another using encrypted communications/

>+      <para>Finally there is the <acronym>TCP</acronym> Extensions
>+	option.  This enables the <acronym>TCP</acronym> Extensions
>+	as defined by <acronym>RFC</acronym>&nbsp;1323 and

	s/as defined by/defined in/ (it doesn't enable all extensions)

>+	<acronym>RFC</acronym>&nbsp;1644.  While on many hosts this can
>+	speed up connections, but can also cause some connections to

	s/but can/it can/

>+	or be dropped.  It is not recommended for servers but may be
>+	beneficial for stand alone machines.</para>

	It's the default in my 4.9-rc1 install running now; should it 
be turned off? Where is more info on the implications available?


					Chris Pepper
-- 
Chris Pepper:               <http://www.reppep.com/~pepper/>
Rockefeller University:     <http://www.rockefeller.edu/>


From www at FreeBSD.org  Wed Oct  1 09:24:43 2003
From: www at FreeBSD.org (World Wide Web Owner)
Date: Wed, 1 Oct 2003 02:24:42 -0700 (PDT)
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200310010924.h919OguQ097826@www.freebsd.org>

install -c  -o www -g www -m 444 book.html /w/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
/w/www/build/www/es/doc/es -> /w/www/build/www/es/doc/es_ES.ISO8859-1
===> ../ru
(cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/usr/local/www/www.freebsd.org/data/ru/FAQ all)
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  send-pr.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ru > send-pr.html ||  (/bin/rm -f send-pr.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  send-pr.html
===> ../ru/security
===> ../ru/commercial
===> ../ru/docproj
===> ../ru/news
===> ../ru/news/1996
===> ../ru/news/1997
===> ../ru/news/1998
===> ../ru/news/1999
===> ../ru/news/2000
===> ../ru/news/2001
===> ../ru/FAQ
(cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/usr/local/www/www.freebsd.org/data/ru/FAQ all)
===> ../ru/handbook
===> ../ru/internal
===> ../ru/java
===> ../ru/java/dists
===> ../ru/java/docs
===> ../ru/java/links
===> ../ru/copyright
===> ../ru/search
===> ../ru/gallery
===> ../ru/projects
===> ../ru/platforms
===> ../ru/releases
===> ../ru/smp
===> ../ru/donations
===> ../ru/ports
(cd /w/www/build/www/ru/ports;  make  -f /w/www/build/www/ru/ports/Makefile.inc0 all)
===> ../ru/relnotes
cd: can't cd to /w/www/build/www/ru/relnotes
*** Error code 2

Stop in /w/www/build/www/ru.
*** Error code 1

Stop in /w/www/build/www/en.
     3708.15 real      2180.00 user       133.05 sys


From jan at husar.info  Wed Oct  1 13:00:50 2003
From: jan at husar.info (Jan 'rejden' Husar)
Date: Wed, 1 Oct 2003 15:00:47 +0200 (CEST)
Subject: Translation of documents to slovak language (slovakia / slovak 
 republic)
Message-ID: <1125.194.154.232.120.1065013247.squirrel@webmail.servery.cz>

Hi,
i`m translating some freebsd Books and Articles to slovak language and i
want to ask in which format you want it, i`m doing it all in pdf, the
freebsd handbook is 70% translated and other will follow, so if u can
navigate me a little into what you need, also i want translate all system
manuals (but in future of course :)
If u have any other documents/articles/manuals you want to translate, i
will do it.
Please answear me as soon as you can,

ps : i love opensource :]

Sincerely your`s


-- 
               Jan "rejden" Husar
business:                                personel:
www.husar.info             www.hysteria.sk/rejden/
jan at husar.info                  rejden at hysteria.sk
+421904361878                       ICQ: 146301796


From kensmith at FreeBSD.org  Wed Oct  1 17:05:40 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Wed, 1 Oct 2003 10:05:40 -0700 (PDT)
Subject: docs/57434: Typo in pthread_mutex_init manpage
Message-ID: <200310011705.h91H5eiQ049491@freefall.freebsd.org>

Synopsis: Typo in pthread_mutex_init manpage

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Wed Oct 1 10:04:38 PDT 2003
Responsible-Changed-Why: 

I'll take this one.


http://www.freebsd.org/cgi/query-pr.cgi?pr=57434


From trhodes at FreeBSD.org  Wed Oct  1 19:07:34 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Wed, 1 Oct 2003 15:07:12 -0400
Subject: Quick review requested
In-Reply-To: <p06100302bb9ffc71a931@[66.92.104.201]>
References: <20030930180215.7438ba73.trhodes@FreeBSD.org>
	<p06100302bb9ffc71a931@[66.92.104.201]>
Message-ID: <20031001150712.630b1c27.trhodes@FreeBSD.org>

On Wed, 1 Oct 2003 00:13:44 -0400
Chris Pepper <pepper at reppep.com> wrote:

> At 6:02 PM -0400 2003/09/30, Tom Rhodes wrote:
> 
> Tom,
> 
> 	As someone who went through the options tonight, I found this 
> very helpful. I have lots of niggles, though...

[SNIP]

> 
> >+	or be dropped.  It is not recommended for servers but may be
> >+	beneficial for stand alone machines.</para>
> 
> 	It's the default in my 4.9-rc1 install running now; should it 
> be turned off? Where is more info on the implications available?

>From what I've been told (and even read at one point?), if you are
running apache, these should be disabled.  I've been told it can
cause problems for almost any server/service running.  Verification
would be helpful from someone with more knowledge in this area though
(Jeffery Hsu?).

-- 
Tom Rhodes


From trhodes at FreeBSD.org  Wed Oct  1 19:15:54 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Wed, 1 Oct 2003 15:15:33 -0400
Subject: Quick review requested
In-Reply-To: <20031001003637.GB84749@sixshooter.v6.thrupoint.net>
References: <20030930180215.7438ba73.trhodes@FreeBSD.org>
	<20031001003637.GB84749@sixshooter.v6.thrupoint.net>
Message-ID: <20031001151533.2ee29ba5.trhodes@FreeBSD.org>

On Tue, 30 Sep 2003 20:36:37 -0400
Jim Brown <jpb at sixshooter.v6.thrupoint.net> wrote:

> * Tom Rhodes <trhodes at FreeBSD.org> [2003-09-30 18:03]:
> > Gang,
> > 
> > I'd really appreciate some feedback on the text below.  If anyone
> > would like the full patch (images, Makefile, etc) please speak up
> > and I'll send it.
> > 
> > Whitespace in added text will be fixed before the initial cvs ci,
> > so comments on short/long lines are not required.
> > 
> > Thanks!
> > 
> > -- 
> > Tom Rhodes
> > 
> 
> 
> Comments inline- sorry.  I don't have my doc stuff set up on this system
> so I can't check what it looks like visually.
> 

Thank you Jim, and everyone who sent me comments either on list or
off.  They are always extremely helpful in noticing my sometimes
trivial mistakes.

-- 
Tom Rhodes


From itetcu at apropo.ro  Thu Oct  2 02:28:56 2003
From: itetcu at apropo.ro (Ion-Mihai Tetcu)
Date: Thu, 2 Oct 2003 05:28:49 +0300
Subject: Translation of documents to slovak language (slovakia / slovak
 republic)
In-Reply-To: <1125.194.154.232.120.1065013247.squirrel@webmail.servery.cz>
References: <1125.194.154.232.120.1065013247.squirrel@webmail.servery.cz>
Message-ID: <20031002052849.2639b2ab.itetcu@apropo.ro>

On Wed, 1 Oct 2003 15:00:47 +0200 (CEST)
"Jan 'rejden' Husar" <jan at husar.info> wrote:

> Hi,
> i`m translating some freebsd Books and Articles to slovak language
> and i want to ask in which format you want it, i`m doing it all in
> pdf, the freebsd handbook is 70% translated and other will follow,
> so if u can navigate me a little into what you need, also i want
> translate all system manuals (but in future of course :)
> If u have any other documents/articles/manuals you want to
> translate, i will do it.
> Please answear me as soon as you can,
> 
> ps : i love opensource :]
> 
> Sincerely your`s

Read: /usr/share/doc/en_US.ISO8859-1/books/fdp-primer/book.html
(or http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/).

It will be of little use if doing it in pdf.
And it's not hard to write it right, SGML' DTD are like html, so to speak, so if you want to value you time do it this way. Use the doc make system to generate html, pdf, ps, etc.

Pay attention to the locale your using, as you need "extra characters" apart from standard asci (western, ISO8859-1), probably ISO8859-2.

My suggestion is to cvsup the docs-all to work on the most recent version and the one of the existing version like template, and to the translation "on place".


IOnut
 


-- 
IOnut
FreeBSD unregistered ;) user


From jpb at sixshooter.v6.thrupoint.net  Thu Oct  2 02:32:10 2003
From: jpb at sixshooter.v6.thrupoint.net (Jim Brown)
Date: Wed, 1 Oct 2003 22:32:07 -0400
Subject: Translation of documents to slovak language (slovakia / slovak
	republic)
In-Reply-To: <1125.194.154.232.120.1065013247.squirrel@webmail.servery.cz>
References: <1125.194.154.232.120.1065013247.squirrel@webmail.servery.cz>
Message-ID: <20031002023207.GA87080@sixshooter.v6.thrupoint.net>

* Jan 'rejden' Husar <jan at husar.info> [2003-10-01 09:54]:
> Hi,
> i`m translating some freebsd Books and Articles to slovak language and i
> want to ask in which format you want it, i`m doing it all in pdf, the


See   http://www.FreeBSD.org/docproj/docproj.html
for information about the FreeBSD Documentation project.
This overview contains links on the documentation set,
submitting documentation and translations.



> freebsd handbook is 70% translated and other will follow, so if u can
> navigate me a little into what you need, also i want translate all system

What 'we' need is what 'you' need.  Feel free to translate as many
documents as you wish. See http://www.FreeBSD.org/docproj/translations.html
for examples of what other translation teams have done.
Perhaps you can set up a website for your translations so others
can get access your work.


> manuals (but in future of course :)
> If u have any other documents/articles/manuals you want to translate, i
> will do it.
> Please answear me as soon as you can,
> 
> ps : i love opensource :]

Glad to hear it.  Welcome aboard.


> 
> Sincerely your`s
> 
> 
> -- 
>                Jan "rejden" Husar
> business:                                personel:
> www.husar.info             www.hysteria.sk/rejden/
> jan at husar.info                  rejden at hysteria.sk
> +421904361878                       ICQ: 146301796
> _______________________________________________
> freebsd-doc at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe at freebsd.org"
> 


Best Regards,
Jim B.


From brueffer at FreeBSD.org  Thu Oct  2 10:33:36 2003
From: brueffer at FreeBSD.org (Christian Brueffer)
Date: Thu, 2 Oct 2003 12:33:30 +0200 (CEST)
Subject: docs/57090: [patch] article/contributors: add Lukas Ertl
Message-ID: <200310021033.h92AXUCe034835@freefall.freebsd.org>

Synopsis: [patch] article/contributors: add Lukas Ertl

State-Changed-From-To: open->closed
State-Changed-By: brueffer
State-Changed-When: Thu Oct 2 12:33:11 CEST 2003
State-Changed-Why: 
Committed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=57090


From ofsen at enderunix.org  Thu Oct  2 12:12:13 2003
From: ofsen at enderunix.org (Omer Faruk Sen)
Date: Thu, 02 Oct 2003 15:11:54 +0300
Subject: Turkish Translation Project
Message-ID: <200310021211.h92CBsvq056624@istanbul.enderunix.org>

Hi, 

We as EnderUNIX.ORG have started to translate FreeBSD Documents in to 
Turkish language.  We have translated some documents in both www and doc. I 
have successfully compiled and installed www pages and there seems to be no 
mistake.  But as of know I can not compile doc tree because another document 
isn't compiling but the part that we have translated should compile without 
any problem. Before submitting changes with send-pr I think it is a good 
idea to inform both -doc and -www mailing list thus list members can try 
that patches. I am sending the link of patches since adding them here is 
inconvenient for all of us. 

 -----------start-of-adv-------------------------
EnderUNIX.ORG is trying to promote BSD operating systems in various ways. We 
write both Turkish and English BSD spesific documents and also host an 
emailing list for Turkish speaking people which is also in www.freebsd.org's 
international maling list. It is archived at http://lists.enderunix.org
 ----------end-of-adv-------------------------- 


Patches for www and doc tree are located at 

http://www.enderunix.org/trans_proj/tr_doc.diff  (for doc tree)
http://www.enderunix.org/trans_proj/tr_webpages.diff2 (for www tree) 


REGARDS 

 

 -----------------------
Omer Faruk Sen
http://www.EnderUNIX.ORG
Software Development Team @ Turkey
http://www.Faruk.NET
For Public key: http://www.enderunix.org/ofsen/ofsen.asc
******************************************************** 

FreeBSD - because Unix isn't just #include <linux.h> ! 


From gs_stoller at juno.com  Thu Oct  2 16:07:52 2003
From: gs_stoller at juno.com (Gerald S Stoller)
Date: Wed, 1 Oct 2003 19:33:05 -0400
Subject: color in messages
Message-ID: <20031002.120620.-165803.0.GS_Stoller@juno.com>

          It is possible to put color in the  FreeBSD  messages, I have
seen the font color change when I used 'ls -G'.  I would also like to
change the color of the background.  Unfortunately i have seen no
documentation on how to do this.  May i suggest that something brief be
written about this so people can start using color (ASAP) and send me a
copy, then do a more extensive version (if needed for a formal release.
         I tried to find special characters in the output of 'ls -G' by
piping it through a  tee  but it seems that  ls  checks on the
destination of its  STDOUT  and if it not directly to the screen it
removes the color modifying code from it.  Were i to have coded  ls , I
would leave the color modifying code always in the output and maybe
provide another utiliity that removes it through which one could pipe the
output if one wanted the color modifying code removed.
       Probably this question is better directed at the  XFree86  people
but I haven't gotten a good reply from them.


From blackend at freebsd.org  Thu Oct  2 16:53:22 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Thu, 2 Oct 2003 18:29:57 +0200
Subject: Turkish Translation Project
In-Reply-To: <200310021211.h92CBsvq056624@istanbul.enderunix.org>
References: <200310021211.h92CBsvq056624@istanbul.enderunix.org>
Message-ID: <20031002162957.GC555@nosferatu.blackend.org>

On Thu, Oct 02, 2003 at 03:11:54PM +0300, Omer Faruk Sen wrote:
> Hi, 
[...]

Merhaba Omer

> 
> Patches for www and doc tree are located at 
> 
> http://www.enderunix.org/trans_proj/tr_doc.diff  (for doc tree)
> http://www.enderunix.org/trans_proj/tr_webpages.diff2 (for www tree) 
> 

I'll try to add at least the doc/ part on tomorrow or this weekend.

Marc


From naddy at FreeBSD.org  Fri Oct  3 00:45:18 2003
From: naddy at FreeBSD.org (Christian Weisgerber)
Date: Thu, 2 Oct 2003 17:45:17 -0700 (PDT)
Subject: docs/57027: timed.8 nits
Message-ID: <200310030045.h930jHYv075009@freefall.freebsd.org>

Synopsis: timed.8 nits

State-Changed-From-To: open->closed
State-Changed-By: naddy
State-Changed-When: Thu Oct 2 17:44:34 PDT 2003
State-Changed-Why: 
Committed after consulting with simon.

http://www.freebsd.org/cgi/query-pr.cgi?pr=57027


From roam at ringlet.net  Fri Oct  3 07:55:25 2003
From: roam at ringlet.net (Peter Pentchev)
Date: Fri, 3 Oct 2003 10:55:18 +0300
Subject: color in messages
In-Reply-To: <20031002.120620.-165803.0.GS_Stoller@juno.com>
References: <20031002.120620.-165803.0.GS_Stoller@juno.com>
Message-ID: <20031003075518.GE546@straylight.oblivion.bg>

On Wed, Oct 01, 2003 at 07:33:05PM -0400, Gerald S Stoller wrote:
>           It is possible to put color in the  FreeBSD  messages, I have
> seen the font color change when I used 'ls -G'.  I would also like to
> change the color of the background.  Unfortunately i have seen no
> documentation on how to do this.  May i suggest that something brief be
> written about this so people can start using color (ASAP) and send me a
> copy, then do a more extensive version (if needed for a formal release.
>          I tried to find special characters in the output of 'ls -G' by
> piping it through a  tee  but it seems that  ls  checks on the
> destination of its  STDOUT  and if it not directly to the screen it
> removes the color modifying code from it.  Were i to have coded  ls , I
> would leave the color modifying code always in the output and maybe
> provide another utiliity that removes it through which one could pipe the
> output if one wanted the color modifying code removed.
>        Probably this question is better directed at the  XFree86  people
> but I haven't gotten a good reply from them.

No, not exactly XFree86.  Using colors in a terminal window predates
XFree86 (and even the X Window System) by a long shot :)

There are basically two ways for a program to display text in a
different color (or background): the easy, but possibly very, very wrong
way of using ANSI (CSI) escape sequences directly, and the somewhat
harder, but much more portable and mostly guaranteed to work better way
of querying the database of terminal capabilities.

The ANSI escape sequences are a more or less established standard for
common ways for a program to control its output on most terminals out
there.  They consist of sending an Escape character (ASCII code 27,
0x1C) followed by a '[' character, then some optional parameters, and a
command character (usually a letter).  For a list of the available
commands see e.g. <URL:http://www.vmunix.com/~gabor/ansi.html>.
However, using ANSI escape sequences unconditionally may be a Bad
Thing(tm) on a terminal that does not support them - it will either
output lots and lots of garbage (quite confusing for the user), or it
might even interpret the sequences as some different set of commands and
do something entirely unexpected.  Most terminals out there support most
ANSI sequences, but.. be warned :)

The better, more portable way to do this would be to see if the OS (or
rather, its application libraries such as libc) supports the termcap
database - a unified database of information about the display
capabilities of a wide range of terminals.  This is done using the
tgetent() and similar functions, described in the termcap(3) manual
page.  The basic idea is that the database contains an entry for each of
the common (and some quite uncommon) terminal types as defined by the
TERM environment variable, so that the program knows whether the
terminal can e.g. change colors or move the cursor to a desired position
or change characters and so on, and what exactly is the character
sequence that will make it do so.  For more information on the termcap
database, take a look at
<URL:http://www.cs.utah.edu/dept/old/texinfo/termcap/termcap_toc.html>.

Hope this helped a bit :)

G'luck,
Peter

-- 
Peter Pentchev	roam at ringlet.net    roam at sbnd.net    roam at FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
The rest of this sentence is written in Thailand, on
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031003/97b4b296/attachment.sig>

From roam at ringlet.net  Fri Oct  3 08:15:40 2003
From: roam at ringlet.net (Peter Pentchev)
Date: Fri, 3 Oct 2003 11:15:34 +0300
Subject: color in messages
In-Reply-To: <20031003075518.GE546@straylight.oblivion.bg>
References: <20031002.120620.-165803.0.GS_Stoller@juno.com>
	<20031003075518.GE546@straylight.oblivion.bg>
Message-ID: <20031003081534.GF546@straylight.oblivion.bg>

On Fri, Oct 03, 2003 at 10:55:18AM +0300, Peter Pentchev wrote:
[snip]
> The better, more portable way to do this would be to see if the OS (or
> rather, its application libraries such as libc) supports the termcap
> database - a unified database of information about the display
> capabilities of a wide range of terminals.  This is done using the
> tgetent() and similar functions, described in the termcap(3) manual
> page.  The basic idea is that the database contains an entry for each of
> the common (and some quite uncommon) terminal types as defined by the
> TERM environment variable, so that the program knows whether the
> terminal can e.g. change colors or move the cursor to a desired position
> or change characters and so on, and what exactly is the character
> sequence that will make it do so.  For more information on the termcap
> database, take a look at
> <URL:http://www.cs.utah.edu/dept/old/texinfo/termcap/termcap_toc.html>.

...and, of course, the termcap(5) and termcap(3) manual pages :)

G'luck,
Peter

-- 
Peter Pentchev	roam at ringlet.net    roam at sbnd.net    roam at FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031003/13b1a30d/attachment.sig>

From mark at remotelab.org  Fri Oct  3 14:50:22 2003
From: mark at remotelab.org (mark at remotelab.org)
Date: Fri, 3 Oct 2003 16:48:04 +0200 (CEST)
Subject: 	docs/57541: Some suggestions for the Basics chapter of the Handbook 
Message-ID: <200310031448.h93Em4ms000368@einstein.lab>


>Number:         57541
>Category:       docs
>Synopsis:       Some suggestions for the Basics chapter of the Handbook
>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:   Fri Oct 03 07:50:17 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Marco T.
>Release:        FreeBSD 4.9-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD einstein.lab 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Sun Sep 28 19:14:04 CEST 2003 root at einstein.lab:/usr/obj/usr/src/sys/EINSTEIN i386


	
>Description:

-add new item in Synopsis;
-correct one command prompt;
-tags,images and links adjustment (install --> basics);
-adapt two sentence into new context of basics chapter;

Some files in the handbook/install directory should be removed:
disk-layout.kil
example-dir1.dot
example-dir2.dot
example-dir3.dot
example-dir4.dot
example-dir5.dot

and some files in the doc/share/images/books/handbook/install directory should
be moved in a new doc/share/images/books/handbook/basics directory:
disk-layout.eps
example-dir1.eps
example-dir2.eps
example-dir3.eps
example-dir4.eps
example-dir5.eps
	
>How-To-Repeat:
	
>Fix:

	

--- all.diff begins here ---
--- chapter.sgml.old	Fri Oct  3 16:34:35 2003
+++ chapter.sgml	Fri Oct  3 16:34:15 2003
@@ -44,6 +44,9 @@
 	<para>The default &os; file system layout.</para>
       </listitem>
       <listitem>
+	<para>The &os; disk organization.</para>
+      </listitem>
+      <listitem>
 	<para>How to mount and unmount file systems.</para>
       </listitem>
       <listitem>
@@ -176,7 +179,7 @@
 
       <para>You should see the <acronym>MOTD</acronym> or message of
 	the day followed by a command prompt (a <literal>#</literal>,
-	<literal>$</literal>, or <literal>$</literal> character).  This
+	<literal>$</literal>, or <literal>%</literal> character).  This
 	indicates you have successfully logged into FreeBSD.</para>
     </sect2>
 
@@ -894,7 +897,7 @@
 
       <mediaobject>
 	<imageobject>
-	  <imagedata fileref="install/example-dir1" format="EPS">
+	  <imagedata fileref="basics/example-dir1" format="EPS">
 	</imageobject>
 
 	<textobject>
@@ -914,7 +917,7 @@
 
       <mediaobject>
 	<imageobject>
-	  <imagedata fileref="install/example-dir2" format="EPS">
+	  <imagedata fileref="basics/example-dir2" format="EPS">
 	</imageobject>
 
 	<textobject>
@@ -942,7 +945,7 @@
 
       <mediaobject>
 	<imageobject>
-	  <imagedata fileref="install/example-dir3" format="EPS">
+	  <imagedata fileref="basics/example-dir3" format="EPS">
 	</imageobject>
 
 	<textobject>
@@ -968,7 +971,7 @@
 
       <mediaobject>
 	<imageobject>
-	  <imagedata fileref="install/example-dir4" format="EPS">
+	  <imagedata fileref="basics/example-dir4" format="EPS">
 	</imageobject>
 	
 	<textobject>
@@ -994,7 +997,7 @@
 
       <mediaobject>
 	<imageobject>
-	  <imagedata fileref="install/example-dir5" format="EPS">
+	  <imagedata fileref="basics/example-dir5" format="EPS">
 	</imageobject>
 
 	<textobject>
@@ -1079,8 +1082,8 @@
       </itemizedlist>
     
       <para>Filesystems are contained in partitions.  This does not have the
-	same meaning as the earlier usage of the term partition in this
-	chapter, because of FreeBSD's &unix; heritage.  Each partition is
+	same meaning as the common usage of the term partition (for example, DOS
+	partition), because of FreeBSD's &unix; heritage.  Each partition is
 	identified by a letter from <literal>a</literal> through to
 	<literal>h</literal>.  Each partition can contain only one filesystem,
 	which means that filesystems are often described by either their
@@ -1150,7 +1153,7 @@
 
       <para>Each partition-that-contains-a-filesystem is stored in what
 	FreeBSD calls a <firstterm>slice</firstterm>.  Slice is FreeBSD's term
-	for what were earlier called partitions, and again, this is because of
+	for what common call partitions, and again, this is because of
 	FreeBSD's &unix; background.  Slices are numbered, starting at 1,
 	through to 4.</para>
 
@@ -1183,16 +1186,16 @@
 	starts with a code that indicates the type of disk, and then a number,
 	indicating which disk it is.  Unlike slices, disk numbering starts at
 	0.  Common codes that you will see are listed in 
-	<xref linkend="install-dev-codes">.</para>
+	<xref linkend="basics-dev-codes">.</para>
 
       <para>When referring to a partition FreeBSD requires that you also name
 	the slice and disk that contains the partition, and when referring to
 	a slice you should also refer to the disk name.  Do this by listing
 	the disk name, <literal>s</literal>, the slice number, and then the
 	partition letter.  Examples are shown in 
-	<xref linkend="install-disk-slice-part">.</para>
+	<xref linkend="basics-disk-slice-part">.</para>
 
-      <para><xref linkend="install-concept-disk-model"> shows a conceptual
+      <para><xref linkend="basics-concept-disk-model"> shows a conceptual
 	model of the disk layout that should help make things clearer.</para>
 
       <para>In order to install FreeBSD you must first configure the disk
@@ -1200,7 +1203,7 @@
 	FreeBSD, and then create a filesystem (or swap space) in each
 	partition, and decide where that filesystem will be mounted.</para>
 
-      <table frame="none" id="install-dev-codes">
+      <table frame="none" id="basics-dev-codes">
 	<title>Disk Device Codes</title>
 
 	<tgroup cols="2">
@@ -1249,7 +1252,7 @@
 	</tgroup>
       </table>
       
-      <example id="install-disk-slice-part">
+      <example id="basics-disk-slice-part">
 	<title>Sample Disk, Slice, and Partition Names</title>
 	
 	<informaltable frame="none">
@@ -1286,7 +1289,7 @@
 	</informaltable>
       </example>
 
-      <example id="install-concept-disk-model">
+      <example id="basics-concept-disk-model">
 	<title>Conceptual Model of a Disk</title>
 
 	<para>This diagram shows FreeBSD's view of the first IDE disk attached
@@ -1304,7 +1307,7 @@
 
         <mediaobject>
           <imageobject>
-            <imagedata fileref="install/disk-layout" format="EPS">
+            <imagedata fileref="basics/disk-layout" format="EPS">
           </imageobject>
  
           <textobject>
--- Makefile.old	Fri Oct  3 16:34:58 2003
+++ Makefile	Fri Oct  3 16:34:42 2003
@@ -39,6 +39,12 @@
 IMAGES_EN = advanced-networking/isdn-bus.eps
 IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps
 IMAGES_EN+= advanced-networking/natd.eps
+IMAGES_EN+= basics/disk-layout.eps
+IMAGES_EN+= basics/example-dir1.eps
+IMAGES_EN+= basics/example-dir2.eps
+IMAGES_EN+= basics/example-dir3.eps
+IMAGES_EN+= basics/example-dir4.eps
+IMAGES_EN+= basics/example-dir5.eps
 IMAGES_EN+= install/userconfig.scr
 IMAGES_EN+= install/userconfig2.scr
 IMAGES_EN+= install/hdwrconf.scr
@@ -96,14 +102,7 @@
 IMAGES_EN+= install/adduser2.scr
 IMAGES_EN+= install/adduser3.scr
 IMAGES_EN+= install/mainexit.scr
-IMAGES_EN+= install/disk-layout.eps
 IMAGES_EN+= install/edit-inetd-conf.scr
-
-IMAGES_EN+= install/example-dir1.eps
-IMAGES_EN+= install/example-dir2.eps
-IMAGES_EN+= install/example-dir3.eps
-IMAGES_EN+= install/example-dir4.eps
-IMAGES_EN+= install/example-dir5.eps
 IMAGES_EN+= security/ipsec-network.pic
 IMAGES_EN+= security/ipsec-crypt-pkt.pic
 IMAGES_EN+= security/ipsec-encap-pkt.pic
--- all.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:


From trhodes at FreeBSD.org  Fri Oct  3 17:03:14 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 3 Oct 2003 10:03:13 -0700 (PDT)
Subject: docs/57541: Some suggestions for the Basics chapter of the
	Handbook
Message-ID: <200310031703.h93H3Dbg060511@freefall.freebsd.org>

Synopsis: Some suggestions for the Basics chapter of the Handbook

Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Fri Oct 3 10:02:24 PDT 2003
Responsible-Changed-Why: 
This conflicts with a WIP of mine, take it as to avoid patch application difficulties.

http://www.freebsd.org/cgi/query-pr.cgi?pr=57541


From rgwaycott at bellsouth.net  Fri Oct  3 18:18:37 2003
From: rgwaycott at bellsouth.net (Robert G. Waycott)
Date: Fri, 03 Oct 2003 14:18:53 -0400
Subject: Open doc problems/needs
Message-ID: <1065205132.43714.28.camel@localhost>

Dear FDP:
  I have this beautifully lengthy list of currently unassigned doc
projects, dated from Monday. How can I find out more on each of these
specific problems? I have read a great deal of the Primer, but may have
missed something in there that instructs me how to access a formal
explanation of each problem so I can grab one up to work on.  I
appreciate any and all assistance. Thank you.

Esse quam videri,

Bob Waycott


From trhodes at FreeBSD.org  Fri Oct  3 18:24:20 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 3 Oct 2003 14:23:57 -0400
Subject: Open doc problems/needs
In-Reply-To: <1065205132.43714.28.camel@localhost>
References: <1065205132.43714.28.camel@localhost>
Message-ID: <20031003142357.64fe22c4.trhodes@FreeBSD.org>

On Fri, 03 Oct 2003 14:18:53 -0400
"Robert G. Waycott" <rgwaycott at bellsouth.net> wrote:

> Dear FDP:
>   I have this beautifully lengthy list of currently unassigned doc
> projects, dated from Monday. How can I find out more on each of these
> specific problems? I have read a great deal of the Primer, but may have
> missed something in there that instructs me how to access a formal
> explanation of each problem so I can grab one up to work on.  I
> appreciate any and all assistance. Thank you.

Robert,

If you would like to help us close some problem reports, we would
be extremely grateful.  Please point your web browser to the following
location and click on the desired task.

http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=docs&responsible=.

Reading the articles about problem reports, located at:

http://www.FreeBSD.org/docs.html

may help you to understand the 'system' at which these reports are
worked.

Thanks!

-- 
Tom Rhodes


From ru at FreeBSD.org  Fri Oct  3 21:34:24 2003
From: ru at FreeBSD.org (Ruslan Ermilov)
Date: Fri, 3 Oct 2003 14:34:23 -0700 (PDT)
Subject: bin/48210: make -q only does what the manpage says in NonCompat
	mode.
Message-ID: <200310032134.h93LYNZ4019318@freefall.freebsd.org>

Synopsis: make -q only does what the manpage says in NonCompat mode.

Responsible-Changed-From-To: freebsd-doc->freebsd-bugs
Responsible-Changed-By: ru
Responsible-Changed-When: Fri Oct 3 14:33:38 PDT 2003
Responsible-Changed-Why: 
Fixed category.

http://www.freebsd.org/cgi/query-pr.cgi?pr=48210


From ru at FreeBSD.org  Fri Oct  3 21:48:56 2003
From: ru at FreeBSD.org (Ruslan Ermilov)
Date: Fri, 3 Oct 2003 14:48:55 -0700 (PDT)
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
Message-ID: <200310032148.h93LmtFt020557@freefall.freebsd.org>

Synopsis: make release fails with NO_OPENSSH and ! NOKERBEROS

State-Changed-From-To: open->closed
State-Changed-By: ru
State-Changed-When: Fri Oct 3 14:47:38 PDT 2003
State-Changed-Why: 
Sorry, but we don't currently support building releases
without the crypto dists.

http://www.freebsd.org/cgi/query-pr.cgi?pr=50349


From stijn at win.tue.nl  Fri Oct  3 22:57:31 2003
From: stijn at win.tue.nl (Stijn Hoop)
Date: Sat, 4 Oct 2003 00:56:26 +0200
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <200310032148.h93LmtFt020557@freefall.freebsd.org>
References: <200310032148.h93LmtFt020557@freefall.freebsd.org>
Message-ID: <20031003225626.GA60720@pcwin002.win.tue.nl>

On Fri, Oct 03, 2003 at 02:48:55PM -0700, Ruslan Ermilov wrote:
> Synopsis: make release fails with NO_OPENSSH and ! NOKERBEROS
> 
> State-Changed-From-To: open->closed
> State-Changed-By: ru
> State-Changed-When: Fri Oct 3 14:47:38 PDT 2003
> State-Changed-Why: 
> Sorry, but we don't currently support building releases
> without the crypto dists.

As I discovered :)

2 things:

- why not document the NOKERBEROS knob anyway?
- Just out of curiosity's sake, what would be the major obstacle to making this
  work (a release without crypto dists)? If you don't know it's ok, but if you
  have some pointers I might convince my boss to let me take another look at
  this (hmm it just hit me that I could also build a release with the crypto
  present and then just not install it...)

--Stijn

-- 
This sentence contradicts itself -- no actually it doesn't.
		-- Hofstadter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031004/73344529/attachment.sig>

From janec at zoominternet.net  Fri Oct  3 23:20:25 2003
From: janec at zoominternet.net (Jane Cowan)
Date: Fri, 03 Oct 2003 19:16:45 -0400
Subject: Document not found -
	http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/porting.html
Message-ID: <3F7E035D.1040105@zoominternet.net>

http://www.kc2.kc.ru/ports/README.html


From strick at covad.net  Sat Oct  4 10:00:31 2003
From: strick at covad.net (Dan Strick)
Date: Sat, 4 Oct 2003 02:53:32 -0700 (PDT)
Subject: docs/57568: errors in FreeBSD Architecture Handbook
Message-ID: <200310040953.h949rWDm000719@ice.nodomain>


>Number:         57568
>Category:       docs
>Synopsis:       errors in FreeBSD Architecture Handbook
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 04 03:00:28 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dan Strick
>Release:        FreeBSD 4.8-RELEASE i386
>Organization:
>Environment:
System: FreeBSD ice 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Sun Apr 6 21:47:39 PDT 2003 root at ice:/usr/src/sys/compile/ICE i386

>Description:
  This is not a report of a bug in a FreeBSD release but a report of errors in
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/index.html.

  All of the examples given in sections 5.3.2 and 5.3.3 on the "Using Sysinit"
  page are wrong.  All of the usages of the SYSINIT macro are missing the
  "uniquifier" argument and have the "func" argument in its place and the
  "ident" argument is supposed to be a pointer to something (or NULL).
  Perhaps the examples are actually for the previous implementation of the
  Sysinit facility and were not changed after it was last reimplemented.
  (wild guess)

  Suggestion (not related to the bug described above): since linker sets
  are used for things besides the SYSINIT macro, perhaps most of the
  information in the first paragraph of section 5.2 (Sysinit Operation)
  should be moved to the explanation of Linker Set in section
  5.1 (Terminology) and be made more explicit.  It might be nice to
  explain to the reader that the facility depends on the Gnu C __asm__
  feature, the Gnu Assembler .section/.previous directives, the Gnu
  linker support for those features and on the gensetdefs(8) program.
  The linker set facility is *very* hard to understand unless you are
  familiar with all those features and examine a kernel Makefile and
  the kernel.h/linker_set.h files in the system sources to discover
  the glue that binds those features together.

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


From strick at covad.net  Sat Oct  4 10:10:26 2003
From: strick at covad.net (Dan Strick)
Date: Sat, 4 Oct 2003 03:04:24 -0700 (PDT)
Subject: docs/57569: error on gensetdefs(8) man page
Message-ID: <200310041004.h94A4OTt001111@ice.nodomain>


>Number:         57569
>Category:       docs
>Synopsis:       error on gensetdefs(8) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 04 03:10:24 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dan Strick
>Release:        FreeBSD 4.8-RELEASE i386
>Organization:
>Environment:
System: FreeBSD ice 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Sun Apr 6 21:47:39 PDT 2003 root at ice:/usr/src/sys/compile/ICE i386

>Description:
	There is an error on the man page for gensetdefs(8).
	The program does not write the DEFINE_SET lines to stdout.
	It writes them into a file with a fixed name, setdefs.h.
	It also creates two other files, setdef0.c and setdef1.c
	at the same time.

	The man page also misplaces the file /sys/i386/conf/Makefile.i386.
	It is actually in /sys/conf.

>How-To-Repeat:
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


From mark at remotelab.org  Sat Oct  4 15:53:09 2003
From: mark at remotelab.org (Marco Trentini)
Date: Sat, 04 Oct 2003 17:53:05 +0200
Subject: docs/57541: Some suggestions for the Basics chapter of the
	Handbook
In-Reply-To: <200310031703.h93H3Dbg060511@freefall.freebsd.org>
References: <200310031703.h93H3Dbg060511@freefall.freebsd.org>
Message-ID: <3F7EECE1.90308@remotelab.org>

Tom Rhodes wrote:

> Synopsis: Some suggestions for the Basics chapter of the Handbook
> 
> Responsible-Changed-From-To: freebsd-doc->trhodes
> Responsible-Changed-By: trhodes
> Responsible-Changed-When: Fri Oct 3 10:02:24 PDT 2003
> Responsible-Changed-Why: 
> This conflicts with a WIP of mine, take it as to avoid patch application difficulties.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=57541

Ok I've got it. So, these patchs are included in your WIP, aren't they?.



-- 
Marco Trentini                mark at remotelab.org
http://www.remotelab.org/


From ru at FreeBSD.org  Sat Oct  4 19:04:18 2003
From: ru at FreeBSD.org (Ruslan Ermilov)
Date: Sat, 4 Oct 2003 22:03:37 +0300
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <20031003225626.GA60720@pcwin002.win.tue.nl>
References: <200310032148.h93LmtFt020557@freefall.freebsd.org>
	<20031003225626.GA60720@pcwin002.win.tue.nl>
Message-ID: <20031004190337.GB94900@sunbay.com>

On Sat, Oct 04, 2003 at 12:56:26AM +0200, Stijn Hoop wrote:
> On Fri, Oct 03, 2003 at 02:48:55PM -0700, Ruslan Ermilov wrote:
> > Synopsis: make release fails with NO_OPENSSH and ! NOKERBEROS
> > 
> > State-Changed-From-To: open->closed
> > State-Changed-By: ru
> > State-Changed-When: Fri Oct 3 14:47:38 PDT 2003
> > State-Changed-Why: 
> > Sorry, but we don't currently support building releases
> > without the crypto dists.
> 
> As I discovered :)
> 
> 2 things:
> 
> - why not document the NOKERBEROS knob anyway?
> 
Good idea.  Please submit a patch for make.conf(5).  ;)

> - Just out of curiosity's sake, what would be the major obstacle to making this
>   work (a release without crypto dists)? If you don't know it's ok, but if you
>   have some pointers I might convince my boss to let me take another look at
>   this (hmm it just hit me that I could also build a release with the crypto
>   present and then just not install it...)
> 
It can be done, by teaching release/Makefile to build world with NOCRYPT
and a lot of other hacking that will obfuscate it, but I just don't see
much point doing this -- it seems much easier to me to remove the crypto
distribution from the release media.

Mark, what do you think?


Cheers,
-- 
Ruslan Ermilov		Sysadmin and DBA,
ru at sunbay.com		Sunbay Software Ltd,
ru at FreeBSD.org		FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031004/24258b6f/attachment.sig>

From mark at grondar.org  Sat Oct  4 19:35:25 2003
From: mark at grondar.org (Mark Murray)
Date: Sat, 04 Oct 2003 20:30:12 +0100
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS 
In-Reply-To: Your message of "Sat, 04 Oct 2003 22:03:37 +0300."
             <20031004190337.GB94900@sunbay.com> 
Message-ID: <200310041930.h94JUCYJ065458@grimreaper.grondar.org>

Ruslan Ermilov writes:
> It can be done, by teaching release/Makefile to build world with NOCRYPT
> and a lot of other hacking that will obfuscate it, but I just don't see
> much point doing this -- it seems much easier to me to remove the crypto
> distribution from the release media.

Yeah. This is about right. There have been may years' worth of
crypto-insanity in FreeBSD, and we are trying to remove it, not
entrench it.

The crypto stuff in nicely separated out, and I wouldn't mind seeing
further separation (dev tools, LPR, sendmail, etc) done as separately
installable components, similar to the crypto install.

release/* is already a horrendous hack, and to make it take into
account build options would make it _horrible_.

> Mark, what do you think?

I think we need to aim for further simplification :-) If you don't
like crypto, 'rm -rf' is your friend.

M
--
Mark Murray
iumop ap!sdn w,I idlaH


From kensmith at cse.Buffalo.EDU  Sun Oct  5 04:14:37 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sun, 5 Oct 2003 00:14:32 -0400
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <200310041930.h94JUCYJ065458@grimreaper.grondar.org>
References: <20031004190337.GB94900@sunbay.com>
	<200310041930.h94JUCYJ065458@grimreaper.grondar.org>
Message-ID: <20031005041432.GC9334@electra.cse.Buffalo.EDU>

On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:

> The crypto stuff in nicely separated out, and I wouldn't mind seeing
> further separation (dev tools, LPR, sendmail, etc) done as separately
> installable components, similar to the crypto install.

A current interest is having some sort of binary updates system
in place.  Everyone I talk to about the various issues, projects in
motion, etc. say this further separation of stuff would help that
effort a LOT.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From ru at freebsd.org  Sun Oct  5 18:46:59 2003
From: ru at freebsd.org (Ruslan Ermilov)
Date: Sun, 5 Oct 2003 21:46:29 +0300
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <20031005041432.GC9334@electra.cse.Buffalo.EDU>
References: <20031004190337.GB94900@sunbay.com>
	<200310041930.h94JUCYJ065458@grimreaper.grondar.org>
	<20031005041432.GC9334@electra.cse.Buffalo.EDU>
Message-ID: <20031005184629.GB37106@sunbay.com>

On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> 
> > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > further separation (dev tools, LPR, sendmail, etc) done as separately
> > installable components, similar to the crypto install.
> 
> A current interest is having some sort of binary updates system
> in place.  Everyone I talk to about the various issues, projects in
> motion, etc. say this further separation of stuff would help that
> effort a LOT.
> 
The (crypto) stuff is already well separated, it's just that
we don't want to further complicate release/Makefile to
account for the NOCRYPT option -- it's much easier to remove
the unneeded bits after release is rolled.


Cheers,
-- 
Ruslan Ermilov		Sysadmin and DBA,
ru at sunbay.com		Sunbay Software Ltd,
ru at FreeBSD.org		FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031005/8f665bc4/attachment.sig>

From daniel+gnats at pelleg.org  Sun Oct  5 23:50:24 2003
From: daniel+gnats at pelleg.org (Dan Pelleg)
Date: Sun,  5 Oct 2003 19:43:06 -0400 (EDT)
Subject: docs/57624: update to handbook: linux MATLAB
Message-ID: <20031005234306.07085AEF@lank.here>


>Number:         57624
>Category:       docs
>Synopsis:       update to handbook: linux MATLAB
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 05 16:50:18 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dan Pelleg
>Release:        FreeBSD 4.9-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD lank 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Tue Sep 16 20:15:41 EDT 2003


	
>Description:
Clarification and tip following discussion with user of current documentation.
>How-To-Repeat:
	
>Fix:

	

743c743
< 	      <filename>$MATLAB/etc/license.dat</filename> before the
---
> 	      <filename>$MATLAB/license.dat</filename> before the
843a844,851
>     <tip><para>Depending on your version of <filename>linux_base</filename>,
>           you may run into errors when running this script. To avoid
>           that, edit the file $MATLAB/bin/matlab, and change the line that says:
>           </para>
>           <programlisting>if [ `expr "$lscmd" : '.*-&gt;.*'` -ne 0 ]; then</programlisting>
>           <para>(in version 13.0.1 it is on line 410) to this line:</para>
>           <programlisting>if test -L $newbase; then</programlisting>
>     </tip>
>Release-Note:
>Audit-Trail:
>Unformatted:


From blackend at FreeBSD.org  Mon Oct  6 10:19:02 2003
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Mon, 6 Oct 2003 03:19:01 -0700 (PDT)
Subject: docs/57624: update to handbook: linux MATLAB
Message-ID: <200310061019.h96AJ1Fe067520@freefall.freebsd.org>

Synopsis: update to handbook: linux MATLAB

Responsible-Changed-From-To: freebsd-doc->blackend
Responsible-Changed-By: blackend
Responsible-Changed-When: Mon Oct 6 03:18:12 PDT 2003
Responsible-Changed-Why: 
This one is for me :)

http://www.freebsd.org/cgi/query-pr.cgi?pr=57624


From stijn at win.tue.nl  Mon Oct  6 10:20:11 2003
From: stijn at win.tue.nl (Stijn Hoop)
Date: Mon, 6 Oct 2003 12:20:06 +0200
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <20031005184629.GB37106@sunbay.com>
References: <20031004190337.GB94900@sunbay.com>
	<200310041930.h94JUCYJ065458@grimreaper.grondar.org>
	<20031005041432.GC9334@electra.cse.Buffalo.EDU>
	<20031005184629.GB37106@sunbay.com>
Message-ID: <20031006102006.GA76051@pcwin002.win.tue.nl>

On Sun, Oct 05, 2003 at 09:46:29PM +0300, Ruslan Ermilov wrote:
> On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> > On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> > 
> > > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > > further separation (dev tools, LPR, sendmail, etc) done as separately
> > > installable components, similar to the crypto install.
> > 
> > A current interest is having some sort of binary updates system
> > in place.  Everyone I talk to about the various issues, projects in
> > motion, etc. say this further separation of stuff would help that
> > effort a LOT.
> > 
> The (crypto) stuff is already well separated, it's just that
> we don't want to further complicate release/Makefile to
> account for the NOCRYPT option -- it's much easier to remove
> the unneeded bits after release is rolled.

What about this then:

[stijn at pcwin002] <~> ldd /usr/bin/fetch 
/usr/bin/fetch:
        libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28076000)
        libssl.so.3 => /usr/lib/libssl.so.3 (0x28083000)
        libcrypto.so.3 => /lib/libcrypto.so.3 (0x280b5000)
        libc.so.5 => /lib/libc.so.5 (0x281c3000)

It seems to me that a release build with crypto and installed without
will miss /usr/bin/fetch, or will it simply not work? Haven't tried yet,
but I was just wondering.

--Stijn

-- 
"Diane, 2:15 in the afternoon, November 14. Entering town of Twin Peaks.
 Five miles south of the Canadian border, twelve miles west of the state
 line. Never seen so many trees in my life. As W.C. Fields would say, I'd
 rather be here than Philadelphia."
		-- Special Agent Dale Cooper, "Twin Peaks"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031006/ebd13ffd/attachment.sig>

From lahaye at snu.ac.kr  Mon Oct  6 10:56:49 2003
From: lahaye at snu.ac.kr (Rob Lahaye)
Date: Mon, 06 Oct 2003 19:56:43 +0900
Subject: cvsup docs...and then?
Message-ID: <3F814A6B.9020700@snu.ac.kr>



Hi,

I have cvsup-ed the docs. What should I do next?

This ends with an error:

# cd /usr/doc
# make
===> en_US.ISO8859-1
===> en_US.ISO8859-1/articles
===> en_US.ISO8859-1/articles/5-roadmap
/usr/local/bin/jade -V nochunks -ioutput.html -d /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/default.dsl -V %generate-legalnotice-link% -V %generate-article-toc% -ioutput.html.images   -D /usr/obj/usr/doc/en_US.ISO8859-1/articles/5-roadmap -c /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../en_US.ISO8859-1/share/sgml/catalog -c /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml > article.html ||  (/bin/rm -f article.html && false)
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:70:63:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V4.1//EN"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:71:13:E: reference to entity "orig-docbook" for which no system identifier could be generated
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:70:0: entity was defined here
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:78:24:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:78:38:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:91:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:94:26:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:94:40:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:96:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:97:0:E: delimiter ">" invalid: only name and parameter separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:99:27:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:99:41:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:101:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:102:0:E: delimiter ">" invalid: only name and parameter separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:104:28:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:104:42:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:106:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:107:0:E: delimiter ">" invalid: only name and parameter separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:109:28:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:109:42:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:111:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:112:0:E: delimiter ">" invalid: only name and parameter separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:114:25:E: parameter entity "cptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:114:39:E: delimiter ")" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:116:17:E: parameter entity "common.attrib" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:117:0:E: delimiter ">" invalid: only name and parameter separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:125:25:E: parameter entity "smallcptr.char.mix" not defined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:125:44:E: delimiter "|" invalid: only data tag group, model group, element token, "#PCDATA" and token separators are allowed
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:28:0:E: DTD did not contain element declaration for document type name
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:30:8:E: element "ARTICLE" undefined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:31:14:E: element "ARTICLEINFO" undefined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:32:10:E: element "TITLE" undefined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:34:16:E: element "AUTHORGROUP" undefined
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml:35:17:E: element "CORPAUTHOR" undefined

[...snip...]

/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:984:7:E: "element" is not the name of any flow object class
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:978:10:E: reference to undefined variable "has-ancestor-member?"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:224:42:E: reference to undefined variable "$mono-seq$"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:225:13:E: reference to undefined variable "$mono-seq$"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:217:37:E: reference to undefined variable "normalize"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:210:19:E: reference to undefined variable "$italic-seq$"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:211:19:E: reference to undefined variable "$charseq$"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:209:20:E: reference to undefined variable "%refentry-xref-italic%"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:194:39:E: reference to undefined variable "normalize"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:193:51:E: reference to undefined variable "normalize"
/usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd.dsl:192:51:E: reference to undefined variable "normalize"
*** Error code 1

Stop in /usr/doc/en_US.ISO8859-1/articles/5-roadmap.
*** Error code 1

Stop in /usr/doc/en_US.ISO8859-1/articles.
*** Error code 1

Stop in /usr/doc/en_US.ISO8859-1.
*** Error code 1

Stop in /usr/doc.






From simon at FreeBSD.org  Mon Oct  6 11:01:27 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Mon, 6 Oct 2003 13:01:24 +0200
Subject: cvsup docs...and then?
In-Reply-To: <3F814A6B.9020700@snu.ac.kr>
References: <3F814A6B.9020700@snu.ac.kr>
Message-ID: <20031006110122.GA392@FreeBSD.org>

On 2003.10.06 19:56:43 +0900, Rob Lahaye wrote:

> I have cvsup-ed the docs. What should I do next?

Probably install the textproc/docproj port, to get all the needed
DocBook DTD's and so on installed.

> This ends with an error:
> 
> # cd /usr/doc
> # make
> ===> en_US.ISO8859-1
> ===> en_US.ISO8859-1/articles
> ===> en_US.ISO8859-1/articles/5-roadmap
> /usr/local/bin/jade -V nochunks -ioutput.html -d 
> /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/default.dsl 
> -V %generate-legalnotice-link% -V %generate-article-toc% 
> -ioutput.html.images   -D 
> /usr/obj/usr/doc/en_US.ISO8859-1/articles/5-roadmap -c 
> /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../en_US.ISO8859-1/share/sgml/catalog -c /usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /usr/doc/en_US.ISO8859-1/articles/5-roadmap/article.sgml > article.html ||  (/bin/rm -f article.html && false)
> /usr/local/bin/jade:/usr/doc/en_US.ISO8859-1/articles/5-roadmap/../../../share/sgml/freebsd41.dtd:70:63:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V4.1//EN"

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031006/de6a4b92/attachment.sig>

From ru at freebsd.org  Mon Oct  6 11:53:28 2003
From: ru at freebsd.org (Ruslan Ermilov)
Date: Mon, 6 Oct 2003 14:53:01 +0300
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <20031006102006.GA76051@pcwin002.win.tue.nl>
References: <20031004190337.GB94900@sunbay.com>
	<200310041930.h94JUCYJ065458@grimreaper.grondar.org>
	<20031005041432.GC9334@electra.cse.Buffalo.EDU>
	<20031005184629.GB37106@sunbay.com>
	<20031006102006.GA76051@pcwin002.win.tue.nl>
Message-ID: <20031006115301.GA52277@sunbay.com>

On Mon, Oct 06, 2003 at 12:20:06PM +0200, Stijn Hoop wrote:
> On Sun, Oct 05, 2003 at 09:46:29PM +0300, Ruslan Ermilov wrote:
> > On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> > > On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> > > 
> > > > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > > > further separation (dev tools, LPR, sendmail, etc) done as separately
> > > > installable components, similar to the crypto install.
> > > 
> > > A current interest is having some sort of binary updates system
> > > in place.  Everyone I talk to about the various issues, projects in
> > > motion, etc. say this further separation of stuff would help that
> > > effort a LOT.
> > > 
> > The (crypto) stuff is already well separated, it's just that
> > we don't want to further complicate release/Makefile to
> > account for the NOCRYPT option -- it's much easier to remove
> > the unneeded bits after release is rolled.
> 
> What about this then:
> 
> [stijn at pcwin002] <~> ldd /usr/bin/fetch 
> /usr/bin/fetch:
>         libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28076000)
>         libssl.so.3 => /usr/lib/libssl.so.3 (0x28083000)
>         libcrypto.so.3 => /lib/libcrypto.so.3 (0x280b5000)
>         libc.so.5 => /lib/libc.so.5 (0x281c3000)
> 
> It seems to me that a release build with crypto and installed without
> will miss /usr/bin/fetch, or will it simply not work? Haven't tried yet,
> but I was just wondering.
> 
cd /usr/src/release && make -V FIXCRYPTO

You should see the usr.bin/fetch there; this means that the release.3
stage of "make release" recompiles it without crypto support and puts
the crypto-free binary into the "base" distribution.


Cheers,
-- 
Ruslan Ermilov		Sysadmin and DBA,
ru at sunbay.com		Sunbay Software Ltd,
ru at FreeBSD.org		FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031006/c546280b/attachment.sig>

From stijn at win.tue.nl  Mon Oct  6 12:04:35 2003
From: stijn at win.tue.nl (Stijn Hoop)
Date: Mon, 6 Oct 2003 14:04:35 +0200
Subject: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
In-Reply-To: <20031006115301.GA52277@sunbay.com>
References: <20031004190337.GB94900@sunbay.com>
	<200310041930.h94JUCYJ065458@grimreaper.grondar.org>
	<20031005041432.GC9334@electra.cse.Buffalo.EDU>
	<20031005184629.GB37106@sunbay.com>
	<20031006102006.GA76051@pcwin002.win.tue.nl>
	<20031006115301.GA52277@sunbay.com>
Message-ID: <20031006120435.GB76051@pcwin002.win.tue.nl>

On Mon, Oct 06, 2003 at 02:53:01PM +0300, Ruslan Ermilov wrote:
> On Mon, Oct 06, 2003 at 12:20:06PM +0200, Stijn Hoop wrote:
> > On Sun, Oct 05, 2003 at 09:46:29PM +0300, Ruslan Ermilov wrote:
> > > On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> > > > On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> > > > 
> > > > > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > > > > further separation (dev tools, LPR, sendmail, etc) done as separately
> > > > > installable components, similar to the crypto install.
> > > > 
> > > > A current interest is having some sort of binary updates system
> > > > in place.  Everyone I talk to about the various issues, projects in
> > > > motion, etc. say this further separation of stuff would help that
> > > > effort a LOT.
> > > > 
> > > The (crypto) stuff is already well separated, it's just that
> > > we don't want to further complicate release/Makefile to
> > > account for the NOCRYPT option -- it's much easier to remove
> > > the unneeded bits after release is rolled.
> > 
> > What about this then:
> > 
> > [stijn at pcwin002] <~> ldd /usr/bin/fetch 
> > /usr/bin/fetch:
> >         libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28076000)
> >         libssl.so.3 => /usr/lib/libssl.so.3 (0x28083000)
> >         libcrypto.so.3 => /lib/libcrypto.so.3 (0x280b5000)
> >         libc.so.5 => /lib/libc.so.5 (0x281c3000)
> > 
> > It seems to me that a release build with crypto and installed without
> > will miss /usr/bin/fetch, or will it simply not work? Haven't tried yet,
> > but I was just wondering.
> > 
> cd /usr/src/release && make -V FIXCRYPTO
> 
> You should see the usr.bin/fetch there; this means that the release.3
> stage of "make release" recompiles it without crypto support and puts
> the crypto-free binary into the "base" distribution.

OK, good to know, thanks for your time!

--Stijn

-- 
Nostalgia ain't what it used to be.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031006/001f6f79/attachment.sig>

From blackend at freebsd.org  Mon Oct  6 17:13:27 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Mon, 6 Oct 2003 19:12:18 +0200
Subject: cvsup docs...and then?
In-Reply-To: <3F814A6B.9020700@snu.ac.kr>
References: <3F814A6B.9020700@snu.ac.kr>
Message-ID: <20031006171218.GA596@nosferatu.blackend.org>

On Mon, Oct 06, 2003 at 07:56:43PM +0900, Rob Lahaye wrote:
> 
> 
> Hi,
> 
> I have cvsup-ed the docs. What should I do next?
>
[...]

Here's a little "howto" on what to do:

http://www.bsdnews.org/02/freebsd_doc.php

Marc


From bugmaster at freebsd.org  Mon Oct  6 18:00:44 2003
From: bugmaster at freebsd.org (FreeBSD bugmaster)
Date: Mon, 6 Oct 2003 11:00:37 -0700 (PDT)
Subject: Current unassigned doc problem reports
Message-ID: <200310061800.h96I0bT9059576@freefall.freebsd.org>

Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

Bugs can be in one of several states:

o - open
     A problem report has been submitted, no sanity checking performed.

a - analyzed
     The problem is understood and a solution is being sought.

f - feedback
     Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
     A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

s - suspended
     The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
     A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
a [2001/10/31] i386/31671  doc         4.4 installer hangs at " Mounting root fr

1 problem total.

Serious problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
s [1999/10/04] i386/14135  doc         lpt1 nolonger exists after 3.2-RELEASE
s [2000/07/18] docs/20028  doc         ASCII docs should reflect <emphasis> tags
o [2001/05/23] docs/27605  doc         Cross-document references (<olink>)
o [2002/01/15] docs/33929  doc         Section 15.15 of the FreeBSD Porter's Han
s [2002/03/08] docs/35678  doc         docproj Makefiles for web are broken for 
o [2002/03/21] docs/36168  doc         -pthread/_THREAD_SAFE docs missing in gcc
o [2002/09/13] docs/42762  doc         ppp.8 has no description of $env and ~use
o [2002/11/14] docs/45303  doc         Bug in PDF DocBook rendering
f [2003/02/19] docs/48472  doc         Documentation unreadable.
o [2003/09/15] docs/56894  doc         umass man page: "mount -t msdos" instead 
o [2003/10/04] docs/57568  doc         errors in FreeBSD Architecture Handbook

11 problems total.

Non-critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
o [2001/02/01] docs/24786  doc         missing FILES descriptions in sa(4)
o [2001/04/29] docs/26943  doc         [patch] description of :C modifier is mis
o [2001/07/26] docs/29245  doc         top(1) manpage doesn't understand SMP
a [2001/08/23] docs/30008  doc         This document should be translated, comme
o [2001/09/27] docs/30873  doc         ``ip'' man page does not specify byte ord
o [2001/10/07] docs/31109  doc         replace gif images w/ png ones due to pat
o [2001/11/15] docs/32020  doc         loader.8 manpage missing tunables
o [2002/01/05] docs/33589  doc         Patch to doc.docbook.mk to post process .
o [2002/01/13] docs/33852  doc         split(1) man page implies that input file
o [2002/01/14] docs/33877  doc         Documentet behaviour of SF_flags for non-
o [2002/02/15] bin/34955   doc         [PATCH] ps(1) is out of touch with realit
a [2002/02/16] docs/35011  doc         There are no commands called "diskless" o
o [2002/02/22] docs/35222  doc         mailing list archive URL regexp suboptima
o [2002/03/06] docs/35602  doc         dump(8)/restore(8) pages don't explain "a
o [2002/03/06] docs/35607  doc         dump(1) page needs discussion of scary er
o [2002/03/06] docs/35608  doc         mt(1) page uses "setmark" without explana
o [2002/03/06] docs/35609  doc         mt(1) page needs explanation of "long era
o [2002/03/06] docs/35612  doc         ps(1) page "state" description doesn't me
o [2002/03/07] docs/35642  doc         lo(4) page maybe should document optional
o [2002/03/07] docs/35644  doc         lo(4) page presumes familiarity with prin
o [2002/03/07] docs/35646  doc         cp(1) page needs a "Bugs" section.
o [2002/03/07] docs/35647  doc         www; combine query-by-number and multi-fi
o [2002/03/07] docs/35648  doc         rc.conf; add note about "flags" to both f
o [2002/03/08] docs/35686  doc         blackhole(4) page seems to contradict its
o [2002/03/08] docs/35687  doc         /etc/nsmb.conf missing mention of readers
o [2002/03/09] docs/35711  doc         the "gnats page" should move to its own s
o [2002/03/10] docs/35732  doc         adduser(8) page has obsolete reference an
o [2002/03/15] docs/35943  doc         at(1) config files are misplaced in /var/
o [2002/03/15] docs/35953  doc         hosts.equiv(5) manual is confusing or wro
o [2002/03/20] misc/36154  doc         Getting USB mouse to work: usbd and mouse
o [2002/03/28] docs/36432  doc         Proposal for doc/share/mk: make folded bo
o [2002/03/28] docs/36449  doc         symlink(7) manual doesn't mention trailin
o [2002/05/03] docs/37719  doc         Detail VOP_ naming in a relevant man-page
s [2002/05/07] docs/37843  doc         manual for pthread_setschedparam is wrong
o [2002/05/18] docs/38225  doc         change "CDROM" to "CD-ROM"
o [2002/05/25] docs/38556  doc         EPS file of beastie, as addition to exist
o [2002/05/27] docs/38620  doc         Committers Guide and CVS
o [2002/05/31] docs/38772  doc         firewall_type feature not mentioned on Ha
o [2002/06/07] docs/38982  doc         developers-hanbook/Jail fix
o [2002/06/12] docs/39213  doc         No rc(4) man page
o [2002/06/15] docs/39348  doc         kenv fetch of hostname requires dhcp/boot
o [2002/06/19] docs/39530  doc         access(2) man page has unnecessarily broa
o [2002/06/19] docs/39532  doc         'find' man page should
o [2002/06/24] docs/39824  doc         Various tweaks for doc/en_US.ISO8859-1/bo
o [2002/07/04] docs/40196  doc         man find does not describe -follow
o [2002/07/10] docs/40423  doc         Keyboard(4)'s definition of parameters to
o [2002/07/10] docs/40443  doc         Update books/faq/book.sgml for USB .ko's 
o [2002/07/21] docs/40851  doc         [PATCH] "mergemaster -p" in UPDATING's "C
o [2002/07/28] docs/41089  doc         pax -B option does not mention interactio
o [2002/08/02] docs/41270  doc         confusing directions for kernelconfig cha
o [2002/08/07] docs/41423  doc         Update FAQ: attrib command for windows du
o [2002/08/18] docs/41761  doc         Update for /ru/internal/ part of site
o [2002/08/19] docs/41787  doc         man page for route (Section 8) missing de
o [2002/08/19] docs/41791  doc         Documentation formatting error
o [2002/08/19] docs/41807  doc         natd -punch_fw "bug"
o [2002/08/20] docs/41820  doc         Device driver confusion in Handbook (2.3)
a [2002/08/27] docs/42058  doc         Documentation: Installing Oracle 8i onto 
o [2002/10/01] docs/43569  doc         src/share/examples/worm/README out-of-dat
o [2002/10/04] docs/43651  doc         stab(5) incorrectly states to include jus
o [2002/10/09] docs/43861  doc         non-trivial typo in wicontrol man page
o [2002/10/11] docs/43941  doc         Rationale for Upgrade Sequence
o [2002/10/14] docs/44074  doc         ln(1) manual clarifications [patch]
o [2002/10/23] docs/44400  doc         ipfw(8) has contradictions in bridged and
o [2002/10/24] docs/44435  doc         sysctl manpage: add example for tcsh
o [2002/10/29] docs/44594  doc         Handbook doesn't mention drivers.flp for 
o [2002/11/17] docs/45371  doc         man page for exports lacks information on
o [2002/12/02] docs/45940  doc         burncd missing info
o [2002/12/11] docs/46181  doc         "make fetch-recursive" target description
o [2002/12/11] docs/46196  doc         Missing return value in (set_)menu_format
o [2002/12/11] docs/46200  doc         fix for ru_RU.KOI8-R/books/porters-handbo
o [2002/12/16] docs/46291  doc         correlation between HZ kernel config para
o [2002/12/16] docs/46295  doc         please add information to Nvi recovery em
o [2003/01/02] docs/46709  doc         tables in terminfo.5 are broken
o [2003/01/05] docs/46793  doc         DEVICE_POLLING can not be used with SMP, 
o [2003/01/14] docs/47085  doc         boot(8) manpage is incomplete according t
o [2003/01/27] docs/47575  doc         Clarify requirements for IPFW2 in STABLE
o [2003/01/28] docs/47594  doc         [PATH] passwd(5) incorrectly states allow
o [2003/01/30] docs/47690  doc         builtin(1) manpage is wrong about externa
o [2003/01/30] docs/47705  doc         wc(1) manpage has poor explanations.
f [2003/02/02] docs/47818  doc         ln(1) manpage is confusing
f [2003/02/07] docs/48038  doc         [PATCH] add Tips and Tricks section into 
o [2003/02/28] docs/48767  doc         wrong key numbers for left/right windows 
o [2003/03/06] docs/48980  doc         [PATCH] nsgmls -s errors and sect. 3.2.1 
o [2003/03/14] docs/50013  doc         [PATCH] add much more russian holydays
o [2003/03/23] docs/50211  doc         [PATCH] Fix textfile creation
f [2003/03/28] docs/50391  doc         Incorrect information in a man
o [2003/04/03] docs/50573  doc         return values for res_query/res_search/re
f [2003/04/07] docs/50677  doc         [PATCH] update doc/en_US.ISO8859-1/books/
o [2003/04/10] docs/50773  doc         NFS problems by jumbo frames to mention i
o [2003/05/06] docs/51875  doc         atkbd(4) adjustment
o [2003/05/06] docs/51891  doc         DIAGNOSTICS in ed driver manpage don't ma
o [2003/05/07] docs/51921  doc         ls(1) manpage lacks some information abou
o [2003/05/11] docs/52071  doc         [PATCH] Add more information about soft u
o [2003/05/25] docs/52672  doc         Porter's Handbook: couple of corrections
o [2003/06/02] docs/52878  doc         [PATCH] security(7): small clairification
o [2003/06/13] docs/53303  doc         mount(2) man page error
o [2003/06/14] docs/53315  doc         [PATCH] remove extraneous whitespace at t
o [2003/06/18] docs/53454  doc         wrong sample code in manpage of wcwidth(3
o [2003/06/19] docs/53501  doc         [PATCH] Handbook: update snapshots sectio
o [2003/06/20] docs/53575  doc         Change to Handbook Section 20.9
o [2003/06/21] docs/53596  doc         Updates to mt manual page
o [2003/06/25] docs/53732  doc         quota output and man page do not document
o [2003/06/26] docs/53751  doc         bus_dma(9) incorrectly documents BUS_DMA_
o [2003/07/11] docs/54380  doc         [PATCH] document additional perl variable
o [2003/07/11] docs/54391  doc         Document that glob(3) respects LC_COLLATE
o [2003/07/20] docs/54678  doc         [patch] add PACKAGESITE to packages chapt
o [2003/07/22] docs/54752  doc         bus_dma explained in ISA section: should 
o [2003/07/22] docs/54769  doc         [patch] updates to FAQ
o [2003/07/23] docs/54789  doc         [PATCH] brush up the "New Users" article
o [2003/07/24] docs/54806  doc         [patch] adds fvwm2 to x11-wm
o [2003/07/25] docs/54879  doc         man 1 jot, -r description
o [2003/07/28] docs/54995  doc         Error in accept(2) man page
o [2003/07/28] docs/54999  doc         Documentation Project Primer doesn't conf
o [2003/08/03] docs/55207  doc         [patch] update acroread section & add loc
o [2003/08/06] docs/55306  doc         [patch] adds filemanagers to desktop appl
o [2003/08/11] docs/55458  doc         [patch] add useful content & hints to por
o [2003/08/11] docs/55482  doc         DUMP has access to block devices in a JAI
o [2003/08/13] docs/55538  doc         [patch] add screenshots to desktop chapte
o [2003/08/16] docs/55653  doc         chflags.1 - note that not all tools chfla
o [2003/08/22] docs/55883  doc         advanced-networking/chapter.sgml
o [2003/09/04] docs/56408  doc         [PATCH] add <filename> around app-default
o [2003/09/04] docs/56452  doc         [patch]Add EXTRACT_DEPENDS&PATCH_DEPENDS 
o [2003/09/13] docs/56745  doc         Some suggestions for the Bibliography cha
o [2003/09/14] docs/56872  doc         [Patch] Talk about EVFILT_NETDEV in kqueu
o [2003/09/14] docs/56883  doc         Inadequately-documented charter for freeb
o [2003/09/15] docs/56901  doc         [patch] articles/diskless-x: fix bad engl
o [2003/09/15] docs/56902  doc         [patch] articles/fbsd-from-scratch: add/f
o [2003/09/15] docs/56903  doc         [patch] articles/fonts: add application t
o [2003/09/16] docs/56915  doc         [patch] articles/fonts: update links
o [2003/09/16] docs/56932  doc         [patch] articles/releng-packages: add "no
o [2003/09/16] docs/56936  doc         [patch] articles/java-tomcat: add applica
o [2003/09/18] docs/56981  doc         man terminfo(5) from libncurses does not 
o [2003/09/22] docs/57118  doc         
o [2003/09/24] docs/57153  doc         S_IRWXU missing in fstat(2) man page?
o [2003/09/25] docs/57209  doc         [patch] article/mh: add missing docbook t
o [2003/09/29] docs/57388  doc         INSTALL.TXT enhancement: mention ok promp
o [2003/10/04] docs/57569  doc         error on gensetdefs(8) man page

137 problems total.


From ted at erg.sri.com  Mon Oct  6 18:10:13 2003
From: ted at erg.sri.com (Ted Nolan)
Date: Mon, 6 Oct 2003 14:08:33 -0400 (EDT)
Subject: docs/57669: IFMIB(4) man page uses sysctl(3) incorrectly in example
	code
Message-ID: <200310061808.h96I8Xds019326@colanix0.ga.erg.sri.com>


>Number:         57669
>Category:       docs
>Synopsis:       IFMIB(4) man page uses sysctl(3) incorrectly in example code
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 06 11:10:10 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ted Nolan
>Release:        FreeBSD 4.6.2-RELEASE i386
>Organization:
SRI International
>Environment:
System: FreeBSD colanix0 4.6.2-RELEASE FreeBSD 4.6.2-RELEASE #0: Wed Aug 14 21:23:26 GMT 2002 murray at builder.freebsdmall.com:/usr/src/sys/compile/GENERIC i386


	
>Description:

The man page for ifmib(4) gives a code sample defining a function
get_ifmib_general().  This function uses the sysctl(3) function, but
with incorrect parameters.  The 4th parameter to sysctl(3) is the
_address_ of a location to read and store the size of the data;
however the example code places the actual size here, not the _location_
of the size.  The code will therefore give compilation warnings and
likely fail if run.

>How-To-Repeat:
Enter the code from the example, attempt to compile it with warnings
enabled.
>Fix:

One way to fix it would be to declare a variable
	size_t len;

and replace the given sysctl() line with 2 lines:

	len = sizeof(*ifmd);
	return sysctl(name, 6, ifmd, &len, (void *)0, 0);
>Release-Note:
>Audit-Trail:
>Unformatted:


From rathan at poornam.com  Thu Oct  9 13:46:36 2003
From: rathan at poornam.com (Rathan Varghese)
Date: Thu, 9 Oct 2003 19:20:41 +0530
Subject: NIS Installation
Message-ID: <200310091920.41869.rathan@poornam.com>

Sir,

	Can u please mention the NIS installation Procedure briefly. 

Because when I am installing, 

	1. When i am giving ypinit -m command, it says more port names as duplicate 
key & skipping 

	2. When I give the make command from  /var/yp, it says the same  but after it 
says successfully updated.


After this i am unable to login to the server using the NIS U/N & Passwd.


Can u please help me regarding this


Thanking you,
Rathan


From vangyzen at stat.duke.edu  Thu Oct  9 14:00:38 2003
From: vangyzen at stat.duke.edu (Eric van Gyzen)
Date: Thu, 9 Oct 2003 09:58:25 -0400 (EDT)
Subject: docs/57799: pam_self(8) man page is wrong
Message-ID: <200310091358.h99DwP3H029668@stat.duke.edu>


>Number:         57799
>Category:       docs
>Synopsis:       pam_self(8) man page is wrong
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 09 07:00:36 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Eric van Gyzen
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
FreeBSD 5.1-RELEASE

>Description:
The pam_self(8) man page says
    If the current real user ID is non-zero, authentication will fail,
    unless the allow_root option was specified.
but the code -- and my intuition -- says
    if (uid == 0 && !openpam_get_option(pamh, OPT_ALLOW_ROOT))
        return (PAM_AUTH_ERR);

>How-To-Repeat:
N/A

>Fix:
If I correctly understand the intended usage of the pam_self(8) module,
the man page should be corrected to say
    If the current real user ID is zero, authentication will fail,
                                   ^^^^
    unless the allow_root option was specified.
>Release-Note:
>Audit-Trail:
>Unformatted:


From eugen at www.svzserv.kemerovo.su  Fri Oct 10 02:40:23 2003
From: eugen at www.svzserv.kemerovo.su (Eugene Grosbein)
Date: Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
Subject: docs/57824: ed(4) man page does not mention that ed requires miibus
Message-ID: <200310100234.h9A2Y3iY038411@www.svzserv.kemerovo.su>


>Number:         57824
>Category:       docs
>Synopsis:       ed(4) man page does not mention that ed requires miibus
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 09 19:40:21 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Eugene Grosbein
>Release:        FreeBSD 4.8-STABLE i386
>Organization:
Svyaz Service JSC
>Environment:
System: FreeBSD www.svzserv.kemerovo.su 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Aug 5 13:13:56 KRAST 2003 eu at www.svzserv.kemerovo.su:/home4/obj/home/src/sys/WWW i386

>Description:
	device ed requires device miisbus since 4.4-STABLE.
	ed(4) man page does not document this dependency still.
	Ian Dowse said once this is fixed in CURRENT.

>How-To-Repeat:
	man 4 ed

>Fix:

	Perform MFC, it's time.
>Release-Note:
>Audit-Trail:
>Unformatted:


From trhodes at FreeBSD.org  Fri Oct 10 15:10:24 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 10 Oct 2003 08:10:23 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101510.h9AFANoJ080066@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Tom Rhodes <trhodes at FreeBSD.org>
To: Eugene Grosbein <eugen at www.svzserv.kemerovo.su>
Cc: FreeBSD-gnats-submit at FreeBSD.org, iedowse at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 11:02:58 -0400

 On Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
 Eugene Grosbein <eugen at www.svzserv.kemerovo.su> wrote:
 
 > 
 > >Number:         57824
 > >Category:       docs
 > >Synopsis:       ed(4) man page does not mention that ed requires miibus
 
 NAME
      ed -- ethernet device driver
 
 SYNOPSIS
      device miibus
      device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
 
 That is in my STABLE tree.
 
 NAME
      ed -- ethernet device driver
 
 SYNOPSIS
      device miibus
      device ed
 
 That is on my current box.
 
 Which branch did you want the MFC to?
 
 -- 
 Tom Rhodes


From alexander.haderer at charite.de  Fri Oct 10 15:10:27 2003
From: alexander.haderer at charite.de (Alexander Haderer)
Date: Fri, 10 Oct 2003 17:07:09 +0200 (CEST)
Subject: docs/57838: missing in docu: port Makefile target
	'package-recursive'
Message-ID: <200310101507.h9AF79nd004818@ogava.str.charite.de>


>Number:         57838
>Category:       docs
>Synopsis:       missing in docu: port Makefile target 'package-recursive'
>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:   Fri Oct 10 08:10:23 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alexander Haderer
>Release:        FreeBSD 4.8-RELEASE i386
>Organization:
Charite Hospital Berlin - Germany
>Environment:
System: FreeBSD ogava.str.charite.de 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Tue May 13 20:42:13 CEST 2003 root at ogava.str.charite.de:/usr/src/sys/compile/OGAVAD i386


>Description:
Systems newer than 4.8R / the current cvsupped ports collection has a new 
target 'package-recursive' that is not mentioned in the docs:
faq, handbook, porters-handbook, man page --> nothing

This target makes packages for the current package as well as for all
depending packages.

>How-To-Repeat:

>Fix:

Here is a patch for the manpage ports(7). Please apply in /usr/src. Original 
sources are from 4.8R CDROM.


--- share/man/man7/ports.7.orig	Fri Oct 10 16:57:19 2003
+++ share/man/man7/ports.7	Fri Oct 10 16:57:27 2003
@@ -204,6 +204,10 @@
 .Va PKGREPOSITORY
 and
 .Va PKGFILE .
+.It Cm package-recursive
+Like 
+.Cm package
+but makes a package for each depending port as well.
 .It Cm readmes
 Create a port's
 .Pa README.html .

>Release-Note:
>Audit-Trail:
>Unformatted:


From maxim at macomnet.ru  Fri Oct 10 15:30:23 2003
From: maxim at macomnet.ru (Maxim Konovalov)
Date: Fri, 10 Oct 2003 08:30:21 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101530.h9AFULdL081284@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Maxim Konovalov <maxim at macomnet.ru>
To: Tom Rhodes <trhodes at freebsd.org>
Cc: bug-followup at freebsd.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 19:27:11 +0400 (MSD)

 On Fri, 10 Oct 2003, 08:10-0700, Tom Rhodes wrote:
 
 > The following reply was made to PR docs/57824; it has been noted by GNATS.
 >
 > From: Tom Rhodes <trhodes at FreeBSD.org>
 > To: Eugene Grosbein <eugen at www.svzserv.kemerovo.su>
 > Cc: FreeBSD-gnats-submit at FreeBSD.org, iedowse at FreeBSD.org
 > Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 >  miibus
 > Date: Fri, 10 Oct 2003 11:02:58 -0400
 >
 >  On Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
 >  Eugene Grosbein <eugen at www.svzserv.kemerovo.su> wrote:
 >
 >  >
 >  > >Number:         57824
 >  > >Category:       docs
 >  > >Synopsis:       ed(4) man page does not mention that ed requires miibus
 >
 >  NAME
 >       ed -- ethernet device driver
 >
 >  SYNOPSIS
 >       device miibus
 >       device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
 >
 >  That is in my STABLE tree.
 >
 >  NAME
 >       ed -- ethernet device driver
 >
 >  SYNOPSIS
 >       device miibus
 >       device ed
 >
 >  That is on my current box.
 >
 >  Which branch did you want the MFC to?
 
 From docs/57824:
 
 >Release:        FreeBSD 4.8-STABLE i386
 
 -- 
 Maxim Konovalov, maxim at macomnet.ru, maxim at FreeBSD.org


From oliver at FreeBSD.org  Fri Oct 10 15:45:44 2003
From: oliver at FreeBSD.org (Oliver Lehmann)
Date: Fri, 10 Oct 2003 17:45:35 +0200
Subject: HP-UX online man pages are not displaying options
In-Reply-To: <20030925160639.3db9d795.oliver@freebsd.org>
References: <20030925160639.3db9d795.oliver@freebsd.org>
Message-ID: <20031010174535.4fe5d703.oliver@FreeBSD.org>

Oliver Lehmann wrote:

> 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?

Is somebody working on this?

-- 
 Oliver Lehmann
        @home: lehmann at ans-netz.de
      @office: oliver.lehmann at mgi.de
         @www: http://www.pofo.de/  |  http://wishlist.ans-netz.de/


From trhodes at FreeBSD.org  Fri Oct 10 15:57:24 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 10 Oct 2003 11:57:02 -0400
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
In-Reply-To: <200310101530.h9AFULdL081284@freefall.freebsd.org>
References: <200310101530.h9AFULdL081284@freefall.freebsd.org>
Message-ID: <20031010115702.3dbfff82.trhodes@FreeBSD.org>

On Fri, 10 Oct 2003 08:30:21 -0700 (PDT)
Maxim Konovalov <maxim at macomnet.ru> wrote:

> The following reply was made to PR docs/57824; it has been noted by GNATS.
> 
> From: Maxim Konovalov <maxim at macomnet.ru>
> To: Tom Rhodes <trhodes at freebsd.org>
> Cc: bug-followup at freebsd.org
> Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
>  miibus
> Date: Fri, 10 Oct 2003 19:27:11 +0400 (MSD)
> 
>  On Fri, 10 Oct 2003, 08:10-0700, Tom Rhodes wrote:
>  
>  > The following reply was made to PR docs/57824; it has been noted by GNATS.
>  >
>  > From: Tom Rhodes <trhodes at FreeBSD.org>
>  > To: Eugene Grosbein <eugen at www.svzserv.kemerovo.su>
>  > Cc: FreeBSD-gnats-submit at FreeBSD.org, iedowse at FreeBSD.org
>  > Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
>  >  miibus
>  > Date: Fri, 10 Oct 2003 11:02:58 -0400
>  >
>  >  On Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
>  >  Eugene Grosbein <eugen at www.svzserv.kemerovo.su> wrote:
>  >
>  >  >
>  >  > >Number:         57824
>  >  > >Category:       docs
>  >  > >Synopsis:       ed(4) man page does not mention that ed requires miibus
>  >
>  >  NAME
>  >       ed -- ethernet device driver
>  >
>  >  SYNOPSIS
>  >       device miibus
>  >       device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
>  >
>  >  That is in my STABLE tree.
>  >
>  >  NAME
>  >       ed -- ethernet device driver
>  >
>  >  SYNOPSIS
>  >       device miibus
>  >       device ed
>  >
>  >  That is on my current box.
>  >
>  >  Which branch did you want the MFC to?
>  
>  From docs/57824:
>  
>  >Release:        FreeBSD 4.8-STABLE i386

It's fixed for the next release; is it normal to MFC something
this trivial to a past release branch?  The GENERIC config file
explains what devices require miibus(4).  So does the handbook,
and the LINT file.

-- 
Tom Rhodes


From trhodes at FreeBSD.org  Fri Oct 10 16:00:39 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 10 Oct 2003 09:00:38 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101600.h9AG0cUY083127@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Tom Rhodes <trhodes at FreeBSD.org>
To: Maxim Konovalov <maxim at macomnet.ru>
Cc: freebsd-doc at FreeBSD.org, bug-followup at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 11:57:02 -0400

 On Fri, 10 Oct 2003 08:30:21 -0700 (PDT)
 Maxim Konovalov <maxim at macomnet.ru> wrote:
 
 > The following reply was made to PR docs/57824; it has been noted by GNATS.
 > 
 > From: Maxim Konovalov <maxim at macomnet.ru>
 > To: Tom Rhodes <trhodes at freebsd.org>
 > Cc: bug-followup at freebsd.org
 > Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 >  miibus
 > Date: Fri, 10 Oct 2003 19:27:11 +0400 (MSD)
 > 
 >  On Fri, 10 Oct 2003, 08:10-0700, Tom Rhodes wrote:
 >  
 >  > The following reply was made to PR docs/57824; it has been noted by GNATS.
 >  >
 >  > From: Tom Rhodes <trhodes at FreeBSD.org>
 >  > To: Eugene Grosbein <eugen at www.svzserv.kemerovo.su>
 >  > Cc: FreeBSD-gnats-submit at FreeBSD.org, iedowse at FreeBSD.org
 >  > Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 >  >  miibus
 >  > Date: Fri, 10 Oct 2003 11:02:58 -0400
 >  >
 >  >  On Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
 >  >  Eugene Grosbein <eugen at www.svzserv.kemerovo.su> wrote:
 >  >
 >  >  >
 >  >  > >Number:         57824
 >  >  > >Category:       docs
 >  >  > >Synopsis:       ed(4) man page does not mention that ed requires miibus
 >  >
 >  >  NAME
 >  >       ed -- ethernet device driver
 >  >
 >  >  SYNOPSIS
 >  >       device miibus
 >  >       device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
 >  >
 >  >  That is in my STABLE tree.
 >  >
 >  >  NAME
 >  >       ed -- ethernet device driver
 >  >
 >  >  SYNOPSIS
 >  >       device miibus
 >  >       device ed
 >  >
 >  >  That is on my current box.
 >  >
 >  >  Which branch did you want the MFC to?
 >  
 >  From docs/57824:
 >  
 >  >Release:        FreeBSD 4.8-STABLE i386
 
 It's fixed for the next release; is it normal to MFC something
 this trivial to a past release branch?  The GENERIC config file
 explains what devices require miibus(4).  So does the handbook,
 and the LINT file.
 
 -- 
 Tom Rhodes


From maxim at macomnet.ru  Fri Oct 10 16:00:55 2003
From: maxim at macomnet.ru (Maxim Konovalov)
Date: Fri, 10 Oct 2003 20:00:51 +0400 (MSD)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
In-Reply-To: <20031010115702.3dbfff82.trhodes@FreeBSD.org>
References: <200310101530.h9AFULdL081284@freefall.freebsd.org>
 <20031010115702.3dbfff82.trhodes@FreeBSD.org>
Message-ID: <20031010195956.H24600@news1.macomnet.ru>

[...]
> >  >Release:        FreeBSD 4.8-STABLE i386
>
> It's fixed for the next release; is it normal to MFC something
> this trivial to a past release branch?  The GENERIC config file
> explains what devices require miibus(4).  So does the handbook,
> and the LINT file.

I am pretty sure we can wait until after 4.9.

-- 
Maxim Konovalov, maxim at macomnet.ru, maxim at FreeBSD.org


From maxim at macomnet.ru  Fri Oct 10 16:10:20 2003
From: maxim at macomnet.ru (Maxim Konovalov)
Date: Fri, 10 Oct 2003 09:10:19 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101610.h9AGAJi4086833@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Maxim Konovalov <maxim at macomnet.ru>
To: Tom Rhodes <trhodes at FreeBSD.org>
Cc: freebsd-doc at FreeBSD.org, bug-followup at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 20:00:51 +0400 (MSD)

 [...]
 > >  >Release:        FreeBSD 4.8-STABLE i386
 >
 > It's fixed for the next release; is it normal to MFC something
 > this trivial to a past release branch?  The GENERIC config file
 > explains what devices require miibus(4).  So does the handbook,
 > and the LINT file.
 
 I am pretty sure we can wait until after 4.9.
 
 -- 
 Maxim Konovalov, maxim at macomnet.ru, maxim at FreeBSD.org


From roam at ringlet.net  Fri Oct 10 16:30:18 2003
From: roam at ringlet.net (Peter Pentchev)
Date: Fri, 10 Oct 2003 09:30:14 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
	miibus
Message-ID: <200310101630.h9AGUEjS088866@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Peter Pentchev <roam at ringlet.net>
To: Maxim Konovalov <maxim at macomnet.ru>
Cc: Tom Rhodes <trhodes at FreeBSD.org>, bug-followup at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires miibus
Date: Fri, 10 Oct 2003 19:20:29 +0300

 On Fri, Oct 10, 2003 at 08:00:51PM +0400, Maxim Konovalov wrote:
 > [...]
 > > >  >Release:        FreeBSD 4.8-STABLE i386
 > >
 > > It's fixed for the next release; is it normal to MFC something
 > > this trivial to a past release branch?  The GENERIC config file
 > > explains what devices require miibus(4).  So does the handbook,
 > > and the LINT file.
 > 
 > I am pretty sure we can wait until after 4.9.
 
 Erm... What do you mean, 'wait'?  What Tom is saying is that
 the branch currently referred to as -STABLE, which *is* what was
 formerly known as 4.8-STABLE, but is right now called 4.9-RC due
 to the pending 4.9-RELEASE -- well, that branch already documents
 that ed needs miibus.  I can also confirm that: my ed(4) manpage
 shows 'device miibus' in the synopsis section.
 
 This was already MFC'd in ed.4 rev. 1.19.2.10 from February 17th,
 committed by - surprise, surprise - Tom Rhodes :)
 
 G'luck,
 Peter
 
 -- 
 Peter Pentchev	roam at ringlet.net    roam at sbnd.net    roam at FreeBSD.org
 PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
 If this sentence were in Chinese, it would say something else.


From trhodes at FreeBSD.org  Fri Oct 10 17:10:15 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Fri, 10 Oct 2003 10:10:14 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101710.h9AHAEC0096503@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Tom Rhodes <trhodes at FreeBSD.org>
To: Peter Pentchev <roam at ringlet.net>
Cc: Maxim Konovalov <maxim at macomnet.ru>, bug-followup at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 13:03:31 -0400

 On Fri, 10 Oct 2003 19:20:29 +0300
 Peter Pentchev <roam at ringlet.net> wrote:
 
 > On Fri, Oct 10, 2003 at 08:00:51PM +0400, Maxim Konovalov wrote:
 > > [...]
 > > > >  >Release:        FreeBSD 4.8-STABLE i386
 > > >
 > > > It's fixed for the next release; is it normal to MFC something
 > > > this trivial to a past release branch?  The GENERIC config file
 > > > explains what devices require miibus(4).  So does the handbook,
 > > > and the LINT file.
 > > 
 > > I am pretty sure we can wait until after 4.9.
 > 
 > Erm... What do you mean, 'wait'?  What Tom is saying is that
 > the branch currently referred to as -STABLE, which *is* what was
 > formerly known as 4.8-STABLE, but is right now called 4.9-RC due
 > to the pending 4.9-RELEASE -- well, that branch already documents
 > that ed needs miibus.  I can also confirm that: my ed(4) manpage
 > shows 'device miibus' in the synopsis section.
 > 
 > This was already MFC'd in ed.4 rev. 1.19.2.10 from February 17th,
 > committed by - surprise, surprise - Tom Rhodes :)
 
 I've done so much -doc that I completely forgot that I did this!
 
 Thanks for pointing this out, I think this PR can be closed now.  What
 does our submitter say?
 
 -- 
 Tom Rhodes


From maxim at macomnet.ru  Fri Oct 10 17:30:22 2003
From: maxim at macomnet.ru (Maxim Konovalov)
Date: Fri, 10 Oct 2003 10:30:21 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Message-ID: <200310101730.h9AHULoJ098537@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Maxim Konovalov <maxim at macomnet.ru>
To: Peter Pentchev <roam at ringlet.net>
Cc: bug-followup at freebsd.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requires
 miibus
Date: Fri, 10 Oct 2003 21:28:51 +0400 (MSD)

 [...]
 >  > I am pretty sure we can wait until after 4.9.
 >
 >  Erm... What do you mean, 'wait'?  What Tom is saying is that
 >  the branch currently referred to as -STABLE, which *is* what was
 >  formerly known as 4.8-STABLE, but is right now called 4.9-RC due
 >  to the pending 4.9-RELEASE -- well, that branch already documents
 >  that ed needs miibus.  I can also confirm that: my ed(4) manpage
 >  shows 'device miibus' in the synopsis section.
 >
 >  This was already MFC'd in ed.4 rev. 1.19.2.10 from February 17th,
 >  committed by - surprise, surprise - Tom Rhodes :)
 
 You are quite right :-)
 
 -- 
 Maxim Konovalov, maxim at macomnet.ru, maxim at FreeBSD.org


From chris at unixpages.org  Fri Oct 10 19:27:18 2003
From: chris at unixpages.org (Christian Brueffer)
Date: Fri, 10 Oct 2003 21:27:11 +0200
Subject: NIS Installation
In-Reply-To: <200310091920.41869.rathan@poornam.com>
References: <200310091920.41869.rathan@poornam.com>
Message-ID: <20031010192711.GB643@unixpages.org>

On Thu, Oct 09, 2003 at 07:20:41PM +0530, Rathan Varghese wrote:
> Sir,
> 
> 	Can u please mention the NIS installation Procedure briefly. 
> 
> Because when I am installing, 
> 
> 	1. When i am giving ypinit -m command, it says more port names as duplicate 
> key & skipping 
> 
> 	2. When I give the make command from  /var/yp, it says the same  but after it 
> says successfully updated.
> 
> 
> After this i am unable to login to the server using the NIS U/N & Passwd.
> 
> 
> Can u please help me regarding this
> 

Hi,

I this question is better suited for the questions@ mailing list.  This
list is for discussions about the FreeBSD documentation only.

Last time I used NIS, I followed the describtions in the FreeBSD handbook:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-nis.html

Worked without problems for me.  Have you read this?

- Christian

-- 
Christian Brueffer	chris at unixpages.org	brueffer at FreeBSD.org
GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031010/38912d39/attachment.sig>

From kensmith at FreeBSD.org  Fri Oct 10 22:07:51 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Fri, 10 Oct 2003 15:07:51 -0700 (PDT)
Subject: docs/57568: errors in FreeBSD Architecture Handbook
Message-ID: <200310102207.h9AM7pET042002@freefall.freebsd.org>

Synopsis: errors in FreeBSD Architecture Handbook

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Fri Oct 10 15:07:20 PDT 2003
Responsible-Changed-Why: 

I'll give this one a try.


http://www.freebsd.org/cgi/query-pr.cgi?pr=57568


From rvdalen at yahoo.co.uk  Sun Oct 12 16:32:28 2003
From: rvdalen at yahoo.co.uk (=?iso-8859-1?q?Rouan=20van=20Dalen?=)
Date: Sun, 12 Oct 2003 17:32:26 +0100 (BST)
Subject: FreeBSD Internals
Message-ID: <20031012163226.63067.qmail@web86106.mail.ukl.yahoo.com>

Hi guys !!!
 
My nme is ROUAN, im am 20.  I am studying OS development.
 
I am writing my own ebook about FreeBSD called "FreeBSD Internals".
But I need a lot of detailed information that is hard to come by.
 
There are numerous reasons why I am writing this book :
 
1) It is essentially a learning process for me.
 
2) I want to provide a source of detailed, in-depth knowledge to anyone
interrested in how an OS works & more specifically how FreeBSD
works.
 
3) I want to give something back to the FreeBSD community for
providing us with such a fantastic OS.
 
The above are just a few.
 
The ebook will be totally free (carrying on the tradition of the FreeBSD
community) because I feel that knowledge should be free.  It will be
published in PDF format.
 
Anyone who provides information will be honered by listing their names 
at the sectiion they provided me with info (if they wish their names to be 
private they should just let me know).
 
Right ...
 
What I need now is the most detailed & in-depth information on 
FreeBSD's boot sequence.  more specifically : 
 
1) What files are related to the FreeBSD boot process.
2) What is each files purpose
3) What order are the files loaded & executed
4) What exactly does the boot manager look for.
5) The structure of the FreeBSD boot record.
6) Source code of the boot record & boot manager, etc.
 
Any other information that pertains to the FreeBSD boot process.
 
It can be links to web pages, attached files, any info possible.
Thnx !!!
 
The help will be much appreciated.  I look forward to working with you
guys to provide the best and most accurate book on FreeBSD.


---------------------------------
Want to chat instantly with your online friends??Get the FREE Yahoo!Messenger


From horikawa at FreeBSD.org  Mon Oct 13 01:50:16 2003
From: horikawa at FreeBSD.org (Kazuo Horikawa)
Date: Sun, 12 Oct 2003 19:43:51 -0600 (MDT)
Subject: docs/57926: amd.conf.5 poorly format as it has both man(7) and
	mdoc(7)
Message-ID: <20031012.194351.74754956.horikawa@attbi.com>


>Number:         57926
>Category:       docs
>Synopsis:       amd.conf.5 poorly format as it has both man(7) and mdoc(7)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 12 18:50:12 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Kazuo Horikawa
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
jpman project
>Environment:
	amd.conf.5 comes with 5.1-CURRENT-20031005-JPSNAP
>Description:
	Revision 1.14 of src/contrib/amd/scripts/amd.conf.5
	has some man(7) macros while the most of this file is written
	in mdoc(7).

	The result is lines marked up with man(7) are poorly formatted.
	
>How-To-Repeat:
	$ gzcat /usr/share/man/man5/amd.conf.5.gz | \
	/usr/bin/groff -mandoc -Tascii -mtty-char -z -ww 
	<standard input>:128: warning: macro `BR' not defined
	<standard input>:131: warning: macro `I' not defined
	[snip]

>Fix:

	Apply the following diff to src/contrib/amd/scripts/amd.conf.5.

--- amd.conf.5.bak	Sun Oct 12 18:37:36 2003
+++ amd.conf.5	Sun Oct 12 19:38:17 2003
@@ -121,56 +121,99 @@
 calls.  This means you could run for example
 .Xr ls 1
 and see what keys are available to mount in that directory.  Not all entries
-are made visible to readdir(3): the "/default" entry, wildcard
-entries, and those with a "/" in them are not included.  If you specify
-"full" to this option, all but "/default" will be visible.
+are made visible to
+.Xr readdir 3 :
+the
+.Qq Pa /default
+entry, wildcard entries, and those with a
+.Qq Pa /
+in them are not included.
+If you specify
+.Qq full
+to this option, all but
+.Qq Pa /default
+will be visible.
 Note that if you run a command which will attempt to
-.BR stat (2)
-the entries, such as often done by "ls -l" or "ls -F", amd will attempt to
-mount
-.I every
-entry in that map.  This is often called a ``mount storm''.
-
-.TP
-.BR map_options " (string, default no options)"
+.Xr stat 2
+the entries, such as often done by
+.Qq ls -l
+or
+.Qq ls -F ,
+.Nm amd
+will attempt to mount
+.Em every
+entry in that map.
+This is often called a
+.Em mount storm .
+.It Ic map_options Xo
+(string, default no options)
+.Xc
 This option is the same as specifying map options on the command line to
-amd, such as "cache:=all".
-
-.TP
-.BR map_type " (string, default search all map types)"
-If specified, amd will initialize the map only for the type given.  This is
+.Nm amd ,
+such as
+.Ql cache\&:\&=all .
+.It Ic map_type Xo
+(string, default search all map types)
+.Xc
+If specified, amd will initialize the map only for the type given.
+This is
 useful to avoid the default map search type used by amd which takes longer
 and can have undesired side-effects such as initializing NIS even if not
-used.  Possible values are
-
-.nf
-\fBfile\fR      plain files
-\fBhesiod\fR    Hesiod name service from MIT
-\fBldap\fR      Lightweight Directory Access Protocol
-\fBndbm\fR      (New) dbm style hash files
-\fBnis\fR       Network Information Services (version 2)
-\fBnisplus\fR   Network Information Services Plus (version 3)
-\fBpasswd\fR    local password files
-\fBunion\fR     union maps
-.fi
-
-.TP
-.BR mount_type " (string, default=nfs)"
-All amd mount types must be NFS.  That is, amd is an NFS server on the
-map mount points, for the local host it is running on.  If "autofs" is
-specified, amd will log an error and convert it to NFS.
-
-.TP
-.BR search_path " (string, default no search path)"
-This provides a (colon-delimited) search path for file maps.  Using a search
+used.
+Possible values are
+.Pp
+.Bl -tag -width "nisplus" -compact
+.It Ic file
+plain files
+.It Ic hesiod
+Hesiod name service from MIT
+.It Ic ldap
+Lightweight Directory Access Protocol
+.It Ic ndbm
+(New) dbm style hash files
+.It Ic nis
+Network Information Services (version 2)
+.It Ic nisplus
+Network Information Services Plus (version 3)
+.It Ic passwd
+local password files
+.It Ic union 
+union maps
+.El
+.It Ic mount_type Xo
+(string, default=nfs)
+.Xc
+All
+.Nm amd
+mount types must be
+.Tn NFS .
+That is,
+.Nm amd
+is an
+.Tn NFS
+server on the
+map mount points, for the local host it is running on.
+If
+.Qq autofs
+is specified,
+.Nm amd
+will log an error and convert it to
+.Tn NFS .
+.It Ic search_path Xo
+(string, default no search path)
+.Xc
+This provides a
+(colon-delimited)
+search path for file maps.
+Using a search
 path, sites can allow for local map customizations and overrides, and can
 distributed maps in several locations as needed.
-
-.\" **************************************************************************
-.SS Parameters applicable to the global section only
-
-.TP
-.BR arch " (string, default to compiled in value)"
+.El
+.Ss "Parameters applicable to the global section only"
+.Bl -tag -width 4n
+.It Ic arch Xo
+(string, default to compiled in value)
+.Xc
 Allows you to override the value of the
 .Va arch
 .Nm amd
@@ -410,7 +453,7 @@
 (numeric, default=110)
 .Xc
 Same as the
-.Ic counter
+.Ar counter
 part of the
 .Fl t Ar interval.counter
 option to
@@ -420,97 +463,162 @@
 (numeric, default=8)
 .Xc
 Same as the
-.B \-x
-option to amd.  Specify any logging options for amd.  Options are comma
-delimited, and can be preceded by the string "no" to negate their meaning.
-The "debug" logging option is only available if am-utils was configured with
---enable-debug.  You can get the list of supported debugging and logging
-options by running amd \-H.  Possible values are:
-
-.nf
-\fBall\fR       all messages
-\fBdebug\fR     debug messages
-\fBerror\fR     non-fatal system errors
-\fBfatal\fR     fatal errors
-\fBinfo\fR      information
-\fBmap\fR       map errors
-\fBstats\fR     additional statistical information
-\fBuser\fR      non-fatal user errors
-\fBwarn\fR      warnings
-\fBwarning\fR   warnings
-.fi
-
-.TP
-.BR nfs_vers " (numeric, default to trying version 3 then 2)"
-By default, amd tries version 3 and then version 2.  This option forces the
-overall NFS protocol used to version 3 or 2.  It overrides what is in the
+.Fl x
+option to
+.Nm amd .
+Specify any logging options for
+.Nm amd .
+Options are comma
+delimited, and can be preceded by the string
+.Qq no
+to negate their meaning.
+The
+.Qq debug
+logging option is only available if am-utils was configured with
+--enable-debug.
+You can get the list of supported debugging and logging
+options by running
+.Nm amd Fl H .
+Possible values are:
+.Pp
+.Bl -tag -width "warning" -compact
+.It Ic all
+all messages
+.It Ic debug
+debug messages
+.It Ic error
+non-fatal system errors
+.It Ic fatal
+fatal errors
+.It Ic info
+information
+.It Ic map
+map errors
+.It Ic stats
+additional statistical information
+.It Ic user
+non-fatal user errors
+.It Ic warn
+warnings
+.It Ic warning
+warnings
+.El
+.It Ic nfs_vers Xo
+(numeric, default to trying version 3 then 2)
+.Xc
+By default,
+.Nm amd
+tries version 3 and then version 2.
+This option forces the
+overall
+.Tn NFS
+protocol used to version 3 or 2.
+It overrides what is in the
 amd maps, and is useful when amd is compiled with NFSv3 support that may not
-be stable.  With this option you can turn off the complete usage of NFSv3
+be stable.
+With this option you can turn off the complete usage of NFSv3
 dynamically (without having to recompile amd) until such time as NFSv3
 support is desired again.
-
-.TP
-.BR nfs_retransmit_counter " (numeric, default=11)"
+.It Ic nfs_retransmit_counter Xo
+(numeric, default=11)
+.Xc
 Same as the
-.I retransmit
+.Ar retransmit
 part of the
-.BI \-t " timeout.retransmit"
-option to amd.
-Specifies the number of NFS retransmissions that the kernel will use to
-communicate with amd.
-
-.TP
-.BR nfs_retry_interval " (numeric, default=8)"
+.Fl t Ar timeout.retransmit
+option to
+.Nm amd .
+Specifies the number of
+.Tn NFS
+retransmissions that the kernel will use to
+communicate with
+.Nm amd .
+.It Ic nfs_retry_interval Xo
+(numeric, default=8)
+.Xc
 Same as the
-.I timeout
+.Ar timeout
 part of the
-.BI \-t " timeout.retransmit"
-option to amd.  Specifies the NFS timeout interval, in
-.I tenths
-of seconds, between NFS/RPC retries (for UDP only).
+.Fl t Ar timeout.retransmit
+option to
+.Nm amd .
+Specifies the
+.Tn NFS
+timeout interval, in
+.Em tenths
+of seconds, between NFS/RPC
+retries (for UDP only).
 This is the value that the kernel will use to
-communicate with amd.
-
-Amd relies on the kernel RPC retransmit mechanism to trigger mount retries.
+communicate with
+.Nm amd .
+.Pp
+.Nm Amd
+relies on the kernel RPC retransmit mechanism to trigger mount retries.
 The values of the
-.B nfs_retransmit_counter
+.Ar nfs_retransmit_counter
 and the
-.B nfs_retry_interval
-parameters change the overall retry interval.  Too long an interval gives
+.Ar nfs_retry_interval
+parameters change the overall retry interval.
+Too long an interval gives
 poor interactive response; too short an interval causes excessive retries.
-
-.TP
-.BR nfs_proto " (string, default to trying version tcp then udp)"
-By default, amd tries TCP and then UDP.  This option forces the overall NFS
-protocol used to TCP or UDP.  It overrides what is in the amd maps, and is
-useful when amd is compiled with NFSv3 support that may not be stable.  With
+.It Ic nfs_proto Xo
+(string, default to trying version tcp then udp)
+.Xc
+By default,
+.Nm amd
+tries TCP and then UDP.
+This option forces the overall
+.Tn NFS
+protocol used to TCP or UDP.
+It overrides what is in the amd maps, and is
+useful when amd is compiled with NFSv3 support that may not be stable.
+With
 this option you can turn off the complete usage of NFSv3 dynamically
 (without having to recompile amd) until such time as NFSv3 support is
 desired again.
-
-.TP
-.BR nis_domain " (string, default to local NIS domain name)"
-Same as the
-.B \-y
-option to amd.  Specify an alternative NIS domain from which to fetch the
-NIS maps.  The default is the system domain name.  This option is ignored if
-NIS support is not available.
-
-.TP
-.BR normalize_hostnames " (boolean, default=no)"
-Same as the
-.B \-n
-option to amd.  If "yes", then the name refereed to by ${rhost} is
-normalized relative to the host database before being used.  The effect is
-to translate aliases into ``official'' names.
-
-.TP
-.BR os " (string, default to compiled in value)"
-Same as the
-.B \-O
-option to amd.  Allows you to override the compiled-in name of the operating
-system.  Useful when the built-in name is not desired for backward
-compatibility reasons.  For example, if the build in name is
+.It Ic nis_domain Xo
+(string, default to local NIS domain name)
+.Xc
+Same as the
+.Fl y
+option to
+.Nm amd .
+Specify an alternative
+.Tn NIS
+domain from which to fetch the
+.Tn NIS
+maps.
+The default is the system domain name.
+This option is ignored if
+.Tn NIS
+support is not available.
+.It Ic normalize_hostnames Xo
+(boolean, default=no)
+.Xc
+Same as the
+.Fl n
+option to
+.Nm amd .
+If
+.Qq yes ,
+then the name refereed to by
+.Va ${rhost}
+is normalized relative to the host database before being used.
+The effect is
+to translate aliases into
+.Qq official
+names.
+.It Ic os Xo
+(string, default to compiled in value)
+.Xc
+Same as the
+.Fl O
+option to
+.Nm amd .
+Allows you to override the compiled-in name of the operating system.
+Useful when the built-in name is not desired for backward
+compatibility reasons.
+For example, if the build in name is
 .Dq sunos5 ,
 you can override it to
 .Dq sos5 ,
>Release-Note:
>Audit-Trail:
>Unformatted:


From horikawa at FreeBSD.org  Mon Oct 13 02:40:22 2003
From: horikawa at FreeBSD.org (Kazuo Horikawa)
Date: Sun, 12 Oct 2003 19:40:21 -0700 (PDT)
Subject: docs/57926: amd.conf.5 poorly format as it has both man(7) and
 mdoc(7)
Message-ID: <200310130240.h9D2eLfY077273@freefall.freebsd.org>

The following reply was made to PR docs/57926; it has been noted by GNATS.

From: Kazuo Horikawa <horikawa at FreeBSD.org>
To: FreeBSD-gnats-submit at freebsd.org
Cc:  
Subject: Re: docs/57926: amd.conf.5 poorly format as it has both man(7) and
 mdoc(7)
Date: Sun, 12 Oct 2003 20:27:23 -0600 (MDT)

 Please use the following diff instead.
 
 It contains diffs appeared on the vendor branch that are
 not included in the previous diff or revision 1.14
 (e.g., descriptions of "full_os" and "vendor" parameters).
 
 --- amd.conf.5.bak	Sun Oct 12 18:37:36 2003
 +++ amd.conf.5	Sun Oct 12 20:21:44 2003
 @@ -121,56 +121,99 @@
  calls.  This means you could run for example
  .Xr ls 1
  and see what keys are available to mount in that directory.  Not all entries
 -are made visible to readdir(3): the "/default" entry, wildcard
 -entries, and those with a "/" in them are not included.  If you specify
 -"full" to this option, all but "/default" will be visible.
 +are made visible to
 +.Xr readdir 3 :
 +the
 +.Qq Pa /default
 +entry, wildcard entries, and those with a
 +.Qq Pa /
 +in them are not included.
 +If you specify
 +.Qq full
 +to this option, all but
 +.Qq Pa /default
 +will be visible.
  Note that if you run a command which will attempt to
 -.BR stat (2)
 -the entries, such as often done by "ls -l" or "ls -F", amd will attempt to
 -mount
 -.I every
 -entry in that map.  This is often called a ``mount storm''.
 -
 -.TP
 -.BR map_options " (string, default no options)"
 +.Xr stat 2
 +the entries, such as often done by
 +.Qq ls -l
 +or
 +.Qq ls -F ,
 +.Nm amd
 +will attempt to mount
 +.Em every
 +entry in that map.
 +This is often called a
 +.Em mount storm .
 +.It Ic map_options Xo
 +(string, default no options)
 +.Xc
  This option is the same as specifying map options on the command line to
 -amd, such as "cache:=all".
 -
 -.TP
 -.BR map_type " (string, default search all map types)"
 -If specified, amd will initialize the map only for the type given.  This is
 +.Nm amd ,
 +such as
 +.Ql cache\&:\&=all .
 +.It Ic map_type Xo
 +(string, default search all map types)
 +.Xc
 +If specified, amd will initialize the map only for the type given.
 +This is
  useful to avoid the default map search type used by amd which takes longer
  and can have undesired side-effects such as initializing NIS even if not
 -used.  Possible values are
 -
 -.nf
 -\fBfile\fR      plain files
 -\fBhesiod\fR    Hesiod name service from MIT
 -\fBldap\fR      Lightweight Directory Access Protocol
 -\fBndbm\fR      (New) dbm style hash files
 -\fBnis\fR       Network Information Services (version 2)
 -\fBnisplus\fR   Network Information Services Plus (version 3)
 -\fBpasswd\fR    local password files
 -\fBunion\fR     union maps
 -.fi
 -
 -.TP
 -.BR mount_type " (string, default=nfs)"
 -All amd mount types must be NFS.  That is, amd is an NFS server on the
 -map mount points, for the local host it is running on.  If "autofs" is
 -specified, amd will log an error and convert it to NFS.
 -
 -.TP
 -.BR search_path " (string, default no search path)"
 -This provides a (colon-delimited) search path for file maps.  Using a search
 +used.
 +Possible values are
 +.Pp
 +.Bl -tag -width "nisplus" -compact
 +.It Ic file
 +plain files
 +.It Ic hesiod
 +Hesiod name service from MIT
 +.It Ic ldap
 +Lightweight Directory Access Protocol
 +.It Ic ndbm
 +(New) dbm style hash files
 +.It Ic nis
 +Network Information Services (version 2)
 +.It Ic nisplus
 +Network Information Services Plus (version 3)
 +.It Ic passwd
 +local password files
 +.It Ic union 
 +union maps
 +.El
 +.It Ic mount_type Xo
 +(string, default=nfs)
 +.Xc
 +All
 +.Nm amd
 +mount types must be
 +.Tn NFS .
 +That is,
 +.Nm amd
 +is an
 +.Tn NFS
 +server on the
 +map mount points, for the local host it is running on.
 +If
 +.Qq autofs
 +is specified,
 +.Nm amd
 +will log an error and convert it to
 +.Tn NFS .
 +.It Ic search_path Xo
 +(string, default no search path)
 +.Xc
 +This provides a
 +(colon-delimited)
 +search path for file maps.
 +Using a search
  path, sites can allow for local map customizations and overrides, and can
  distributed maps in several locations as needed.
 -
 -.\" **************************************************************************
 -.SS Parameters applicable to the global section only
 -
 -.TP
 -.BR arch " (string, default to compiled in value)"
 +.El
 +.Ss "Parameters applicable to the global section only"
 +.Bl -tag -width 4n
 +.It Ic arch Xo
 +(string, default to compiled in value)
 +.Xc
  Allows you to override the value of the
  .Va arch
  .Nm amd
 @@ -226,7 +269,7 @@
  .Nm amd Fl v .
  Possible values are:
  .Pp
 -.Bl -tag -width "daemon" -compact
 +.Bl -tag -width "xdrtrace" -compact
  .It Ic all 
  all options
  .It Ic amq
 @@ -247,12 +290,18 @@
  use local
  .Pa ./mtab
  file
 +.It Ic readdir
 +show browsable_dirs progress
  .It Ic str
  debug string munging
  .It Ic test
  full debug but no daemon
  .It Ic trace
 -protocol trace
 +RPC protocol trace and
 +.Tn NFS
 +mount arguments
 +.It Ic xdrtrace
 +trace XDR routines
  .El
  .It Ic dismount_interval Xo
  (numeric, default=120)
 @@ -263,6 +312,19 @@
  .Nm amd .
  Specify, in seconds, the time between attempts to dismount file systems that
  have exceeded their cached times. 
 +.It Ic full_os Xo
 +(string, default to compiled in value)
 +.Xc
 +The full name of the operating system, along with its version.
 +Allows you
 +to override the compiled-in full name and version of the operating system.
 +Useful when the compiled-in name is not desired.
 +For example, the full
 +operating system name on linux comes up as
 +.Qq linux ,
 +but you can override
 +it to
 +.Qq linux-2.2.5 .
  .It Ic fully_qualified_hosts Xo
  (string, default=no)
  .Xc
 @@ -309,6 +371,8 @@
  (string, default not set)
  .Xc
  Specify the base name for LDAP.
 +This often includes LDAP-specific
 +values such as country and organization.
  .It Ic ldap_cache_maxmem Xo
  (numeric, default=131072)
  .Xc
 @@ -320,7 +384,7 @@
  .It Ic ldap_hostports Xo
  (string, default not set)
  .Xc
 -Specify LDAP-specific values such as country and organization.
 +Specify the LDAP host and port values.
  .It Ic local_domain Xo
  (string, default no sub-domain)
  .Xc
 @@ -393,6 +457,10 @@
  non-fatal system errors
  .It Ic fatal
  fatal errors
 +.It Ic hrtime
 +print high resolution time stamps (only if
 +.Xr syslog 3
 +is not used)
  .It Ic info
  information
  .It Ic map
 @@ -410,7 +478,7 @@
  (numeric, default=110)
  .Xc
  Same as the
 -.Ic counter
 +.Ar counter
  part of the
  .Fl t Ar interval.counter
  option to
 @@ -420,97 +488,162 @@
  (numeric, default=8)
  .Xc
  Same as the
 -.B \-x
 -option to amd.  Specify any logging options for amd.  Options are comma
 -delimited, and can be preceded by the string "no" to negate their meaning.
 -The "debug" logging option is only available if am-utils was configured with
 ---enable-debug.  You can get the list of supported debugging and logging
 -options by running amd \-H.  Possible values are:
 -
 -.nf
 -\fBall\fR       all messages
 -\fBdebug\fR     debug messages
 -\fBerror\fR     non-fatal system errors
 -\fBfatal\fR     fatal errors
 -\fBinfo\fR      information
 -\fBmap\fR       map errors
 -\fBstats\fR     additional statistical information
 -\fBuser\fR      non-fatal user errors
 -\fBwarn\fR      warnings
 -\fBwarning\fR   warnings
 -.fi
 -
 -.TP
 -.BR nfs_vers " (numeric, default to trying version 3 then 2)"
 -By default, amd tries version 3 and then version 2.  This option forces the
 -overall NFS protocol used to version 3 or 2.  It overrides what is in the
 +.Fl x
 +option to
 +.Nm amd .
 +Specify any logging options for
 +.Nm amd .
 +Options are comma
 +delimited, and can be preceded by the string
 +.Qq no
 +to negate their meaning.
 +The
 +.Qq debug
 +logging option is only available if am-utils was configured with
 +--enable-debug.
 +You can get the list of supported debugging and logging
 +options by running
 +.Nm amd Fl H .
 +Possible values are:
 +.Pp
 +.Bl -tag -width "warning" -compact
 +.It Ic all
 +all messages
 +.It Ic debug
 +debug messages
 +.It Ic error
 +non-fatal system errors
 +.It Ic fatal
 +fatal errors
 +.It Ic info
 +information
 +.It Ic map
 +map errors
 +.It Ic stats
 +additional statistical information
 +.It Ic user
 +non-fatal user errors
 +.It Ic warn
 +warnings
 +.It Ic warning
 +warnings
 +.El
 +.It Ic nfs_vers Xo
 +(numeric, default to trying version 3 then 2)
 +.Xc
 +By default,
 +.Nm amd
 +tries version 3 and then version 2.
 +This option forces the
 +overall
 +.Tn NFS
 +protocol used to version 3 or 2.
 +It overrides what is in the
  amd maps, and is useful when amd is compiled with NFSv3 support that may not
 -be stable.  With this option you can turn off the complete usage of NFSv3
 +be stable.
 +With this option you can turn off the complete usage of NFSv3
  dynamically (without having to recompile amd) until such time as NFSv3
  support is desired again.
 -
 -.TP
 -.BR nfs_retransmit_counter " (numeric, default=11)"
 +.It Ic nfs_retransmit_counter Xo
 +(numeric, default=11)
 +.Xc
  Same as the
 -.I retransmit
 +.Ar retransmit
  part of the
 -.BI \-t " timeout.retransmit"
 -option to amd.
 -Specifies the number of NFS retransmissions that the kernel will use to
 -communicate with amd.
 -
 -.TP
 -.BR nfs_retry_interval " (numeric, default=8)"
 +.Fl t Ar timeout.retransmit
 +option to
 +.Nm amd .
 +Specifies the number of
 +.Tn NFS
 +retransmissions that the kernel will use to
 +communicate with
 +.Nm amd .
 +.It Ic nfs_retry_interval Xo
 +(numeric, default=8)
 +.Xc
  Same as the
 -.I timeout
 +.Ar timeout
  part of the
 -.BI \-t " timeout.retransmit"
 -option to amd.  Specifies the NFS timeout interval, in
 -.I tenths
 -of seconds, between NFS/RPC retries (for UDP only).
 +.Fl t Ar timeout.retransmit
 +option to
 +.Nm amd .
 +Specifies the
 +.Tn NFS
 +timeout interval, in
 +.Em tenths
 +of seconds, between NFS/RPC
 +retries (for UDP only).
  This is the value that the kernel will use to
 -communicate with amd.
 -
 -Amd relies on the kernel RPC retransmit mechanism to trigger mount retries.
 +communicate with
 +.Nm amd .
 +.Pp
 +.Nm Amd
 +relies on the kernel RPC retransmit mechanism to trigger mount retries.
  The values of the
 -.B nfs_retransmit_counter
 +.Ar nfs_retransmit_counter
  and the
 -.B nfs_retry_interval
 -parameters change the overall retry interval.  Too long an interval gives
 +.Ar nfs_retry_interval
 +parameters change the overall retry interval.
 +Too long an interval gives
  poor interactive response; too short an interval causes excessive retries.
 -
 -.TP
 -.BR nfs_proto " (string, default to trying version tcp then udp)"
 -By default, amd tries TCP and then UDP.  This option forces the overall NFS
 -protocol used to TCP or UDP.  It overrides what is in the amd maps, and is
 -useful when amd is compiled with NFSv3 support that may not be stable.  With
 +.It Ic nfs_proto Xo
 +(string, default to trying version tcp then udp)
 +.Xc
 +By default,
 +.Nm amd
 +tries TCP and then UDP.
 +This option forces the overall
 +.Tn NFS
 +protocol used to TCP or UDP.
 +It overrides what is in the amd maps, and is
 +useful when amd is compiled with NFSv3 support that may not be stable.
 +With
  this option you can turn off the complete usage of NFSv3 dynamically
  (without having to recompile amd) until such time as NFSv3 support is
  desired again.
 -
 -.TP
 -.BR nis_domain " (string, default to local NIS domain name)"
 -Same as the
 -.B \-y
 -option to amd.  Specify an alternative NIS domain from which to fetch the
 -NIS maps.  The default is the system domain name.  This option is ignored if
 -NIS support is not available.
 -
 -.TP
 -.BR normalize_hostnames " (boolean, default=no)"
 -Same as the
 -.B \-n
 -option to amd.  If "yes", then the name refereed to by ${rhost} is
 -normalized relative to the host database before being used.  The effect is
 -to translate aliases into ``official'' names.
 -
 -.TP
 -.BR os " (string, default to compiled in value)"
 -Same as the
 -.B \-O
 -option to amd.  Allows you to override the compiled-in name of the operating
 -system.  Useful when the built-in name is not desired for backward
 -compatibility reasons.  For example, if the build in name is
 +.It Ic nis_domain Xo
 +(string, default to local NIS domain name)
 +.Xc
 +Same as the
 +.Fl y
 +option to
 +.Nm amd .
 +Specify an alternative
 +.Tn NIS
 +domain from which to fetch the
 +.Tn NIS
 +maps.
 +The default is the system domain name.
 +This option is ignored if
 +.Tn NIS
 +support is not available.
 +.It Ic normalize_hostnames Xo
 +(boolean, default=no)
 +.Xc
 +Same as the
 +.Fl n
 +option to
 +.Nm amd .
 +If
 +.Qq yes ,
 +then the name refereed to by
 +.Va ${rhost}
 +is normalized relative to the host database before being used.
 +The effect is
 +to translate aliases into
 +.Qq official
 +names.
 +.It Ic os Xo
 +(string, default to compiled in value)
 +.Xc
 +Same as the
 +.Fl O
 +option to
 +.Nm amd .
 +Allows you to override the compiled-in name of the operating system.
 +Useful when the built-in name is not desired for backward
 +compatibility reasons.
 +For example, if the build in name is
  .Dq sunos5 ,
  you can override it to
  .Dq sos5 ,
 @@ -633,13 +766,13 @@
  mounted.  Whenever one of these would have been auto-mounted,
  .Nm amd
  inherits it.
 -.It Ic selectors_on_default Xo
 +.It Ic selectors_in_default Xo
  (boolean, default=no)
  .Xc
  If
  .Dq yes ,
  then the
 -.Pa /default
 +.Pa /defaults
  entry of maps will be looked for and process any selectors before setting
  defaults for all other keys in that map.  Useful when you want to set
  different options for a complete map based on some parameters.  For example,
 @@ -653,6 +786,7 @@
      wire==slip-net;opts:=intr,rsize=1024,wsize=1024 \\
      wire!=slip-net;opts:=intr,rsize=8192,wsize=8192
  .Ed
 +Deprecated form: selectors_on_default
  .It Ic show_statfs_entries Xo
  (boolean, default=no)
  .Xc
 @@ -685,6 +819,17 @@
  option or
  .Fl r
  flag are used.
 +.It Ic vendor Xo
 +(string, default to compiled in value)
 +.Xc
 +The name of the vendor of the operating system.
 +Overrides the compiled-in vendor name.
 +Useful when the compiled-in name is not desired.
 +For example,
 +most Intel based systems set the vendor name to
 +.Qq unknown ,
 +but you can set it to
 +.Qq redhat .
  .El
  .Ss "Parameters applicable to regular map sections"
  .Bl -tag -width 4n
 @@ -722,7 +867,7 @@
  log_options =            all
  #debug_options =         all
  plock =                  no
 -selectors_on_default =   yes
 +selectors_in_default =   yes
  # config.guess picks up "sunos5" and I don't want to edit my maps yet
  os =                     sos5
  # if you print_version after setting up "os", it will show it.


From eugen at kuzbass.ru  Mon Oct 13 04:20:23 2003
From: eugen at kuzbass.ru (Eugene Grosbein)
Date: Sun, 12 Oct 2003 21:20:22 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed
	requiresmiibus
Message-ID: <200310130420.h9D4KMrC097083@freefall.freebsd.org>

The following reply was made to PR docs/57824; it has been noted by GNATS.

From: Eugene Grosbein <eugen at kuzbass.ru>
To: Tom Rhodes <trhodes at FreeBSD.org>
Cc: Eugene Grosbein <eugen at www.svzserv.kemerovo.su>,
	FreeBSD-gnats-submit at FreeBSD.org, iedowse at FreeBSD.org
Subject: Re: docs/57824: ed(4) man page does not mention that ed requiresmiibus
Date: Mon, 13 Oct 2003 12:17:12 +0800

 Tom Rhodes wrote:
 > 
 > On Fri, 10 Oct 2003 10:34:03 +0800 (KRAST)
 > Eugene Grosbein <eugen at www.svzserv.kemerovo.su> wrote:
 > 
 > >
 > > >Number:         57824
 > > >Category:       docs
 > > >Synopsis:       ed(4) man page does not mention that ed requires miibus
 > 
 > NAME
 >      ed -- ethernet device driver
 > 
 > SYNOPSIS
 >      device miibus
 >      device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
 > 
 > That is in my STABLE tree.
 
 I'm sorry, my 'man 4 ed' shows me /usr/share/man/cat4/ed.4.gz
 that is staled since 2001. Please close this PR.
 
 Eugene Grosbein


From roam at FreeBSD.org  Mon Oct 13 07:16:23 2003
From: roam at FreeBSD.org (Peter Pentchev)
Date: Mon, 13 Oct 2003 00:16:22 -0700 (PDT)
Subject: docs/57824: ed(4) man page does not mention that ed requires
	miibus
Message-ID: <200310130716.h9D7GMkr036534@freefall.freebsd.org>

Synopsis: ed(4) man page does not mention that ed requires miibus

State-Changed-From-To: open->closed
State-Changed-By: roam
State-Changed-When: Mon Oct 13 00:15:57 PDT 2003
State-Changed-Why: 
Submitter agrees that the change has already been MFC'd :)
Still, thanks for reporting what you thought was a genuine FreeBSD problem!

http://www.freebsd.org/cgi/query-pr.cgi?pr=57824


From kensmith at cse.Buffalo.EDU  Mon Oct 13 17:40:21 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 13 Oct 2003 13:40:18 -0400
Subject: Architecture Handbook
Message-ID: <20031013174018.GA7787@electra.cse.Buffalo.EDU>


I was looking over the Architecture Handbook in general as part of
looking into the SYSINIT PR I'm working on.

There are a few sections marked with * - e.g. "*UFS", "*AFS".  Are
those supposed to be markers for sections someone is working on, or
are they sections someone wishes someone was working on?

The divisions for UFS and AFS don't quite make sense IMO.  Might
be better to just have a chapter "Filesystem Support", make the
first part the infrastructure that's common to all of the filesystems
(mount issues, buffer cache, vnodes), and then specific sub-sections
for the different filesystem types.  Especially now with "What is
UFS?" being even more complicated than before (since there are now
two things that are UFS, not to mention UFS itself had been more or
less FFS before, ...).

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From kensmith at cse.Buffalo.EDU  Mon Oct 13 17:55:25 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 13 Oct 2003 13:55:23 -0400
Subject: FreeBSD Internals
In-Reply-To: <20031012163226.63067.qmail@web86106.mail.ukl.yahoo.com>
References: <20031012163226.63067.qmail@web86106.mail.ukl.yahoo.com>
Message-ID: <20031013175523.GA8912@electra.cse.Buffalo.EDU>

On Sun, Oct 12, 2003 at 05:32:26PM +0100, Rouan van Dalen wrote:

> What I need now is the most detailed & in-depth information on 
> FreeBSD's boot sequence.  more specifically : 
>  
> 1) What files are related to the FreeBSD boot process.
> 2) What is each files purpose
> 3) What order are the files loaded & executed
> 4) What exactly does the boot manager look for.
> 5) The structure of the FreeBSD boot record.
> 6) Source code of the boot record & boot manager, etc.

A lot of the information you are looking for is in:

  http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/

See the chapter on "Bootstrapping and kernel initialization".
Have you looked that over yet?

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From bugmaster at freebsd.org  Mon Oct 13 18:00:59 2003
From: bugmaster at freebsd.org (FreeBSD bugmaster)
Date: Mon, 13 Oct 2003 11:00:50 -0700 (PDT)
Subject: Current unassigned doc problem reports
Message-ID: <200310131800.h9DI0ois043324@freefall.freebsd.org>

Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

Bugs can be in one of several states:

o - open
     A problem report has been submitted, no sanity checking performed.

a - analyzed
     The problem is understood and a solution is being sought.

f - feedback
     Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
     A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

s - suspended
     The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
     A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
a [2001/10/31] i386/31671  doc         4.4 installer hangs at " Mounting root fr

1 problem total.

Serious problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
s [1999/10/04] i386/14135  doc         lpt1 nolonger exists after 3.2-RELEASE
s [2000/07/18] docs/20028  doc         ASCII docs should reflect <emphasis> tags
o [2001/05/23] docs/27605  doc         Cross-document references (<olink>)
o [2002/01/15] docs/33929  doc         Section 15.15 of the FreeBSD Porter's Han
s [2002/03/08] docs/35678  doc         docproj Makefiles for web are broken for 
o [2002/03/21] docs/36168  doc         -pthread/_THREAD_SAFE docs missing in gcc
o [2002/09/13] docs/42762  doc         ppp.8 has no description of $env and ~use
o [2002/11/14] docs/45303  doc         Bug in PDF DocBook rendering
f [2003/02/19] docs/48472  doc         Documentation unreadable.
o [2003/09/15] docs/56894  doc         umass man page: "mount -t msdos" instead 
o [2003/10/09] docs/57799  doc         pam_self(8) man page is wrong

11 problems total.

Non-critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
o [2001/02/01] docs/24786  doc         missing FILES descriptions in sa(4)
o [2001/04/29] docs/26943  doc         [patch] description of :C modifier is mis
o [2001/07/26] docs/29245  doc         top(1) manpage doesn't understand SMP
a [2001/08/23] docs/30008  doc         This document should be translated, comme
o [2001/09/27] docs/30873  doc         ``ip'' man page does not specify byte ord
o [2001/10/07] docs/31109  doc         replace gif images w/ png ones due to pat
o [2001/11/15] docs/32020  doc         loader.8 manpage missing tunables
o [2002/01/05] docs/33589  doc         Patch to doc.docbook.mk to post process .
o [2002/01/13] docs/33852  doc         split(1) man page implies that input file
o [2002/01/14] docs/33877  doc         Documentet behaviour of SF_flags for non-
o [2002/02/15] bin/34955   doc         [PATCH] ps(1) is out of touch with realit
a [2002/02/16] docs/35011  doc         There are no commands called "diskless" o
o [2002/02/22] docs/35222  doc         mailing list archive URL regexp suboptima
o [2002/03/06] docs/35602  doc         dump(8)/restore(8) pages don't explain "a
o [2002/03/06] docs/35607  doc         dump(1) page needs discussion of scary er
o [2002/03/06] docs/35608  doc         mt(1) page uses "setmark" without explana
o [2002/03/06] docs/35609  doc         mt(1) page needs explanation of "long era
o [2002/03/06] docs/35612  doc         ps(1) page "state" description doesn't me
o [2002/03/07] docs/35642  doc         lo(4) page maybe should document optional
o [2002/03/07] docs/35644  doc         lo(4) page presumes familiarity with prin
o [2002/03/07] docs/35646  doc         cp(1) page needs a "Bugs" section.
o [2002/03/07] docs/35647  doc         www; combine query-by-number and multi-fi
o [2002/03/07] docs/35648  doc         rc.conf; add note about "flags" to both f
o [2002/03/08] docs/35686  doc         blackhole(4) page seems to contradict its
o [2002/03/08] docs/35687  doc         /etc/nsmb.conf missing mention of readers
o [2002/03/09] docs/35711  doc         the "gnats page" should move to its own s
o [2002/03/10] docs/35732  doc         adduser(8) page has obsolete reference an
o [2002/03/15] docs/35943  doc         at(1) config files are misplaced in /var/
o [2002/03/15] docs/35953  doc         hosts.equiv(5) manual is confusing or wro
o [2002/03/20] misc/36154  doc         Getting USB mouse to work: usbd and mouse
o [2002/03/28] docs/36432  doc         Proposal for doc/share/mk: make folded bo
o [2002/03/28] docs/36449  doc         symlink(7) manual doesn't mention trailin
o [2002/05/03] docs/37719  doc         Detail VOP_ naming in a relevant man-page
s [2002/05/07] docs/37843  doc         manual for pthread_setschedparam is wrong
o [2002/05/18] docs/38225  doc         change "CDROM" to "CD-ROM"
o [2002/05/25] docs/38556  doc         EPS file of beastie, as addition to exist
o [2002/05/27] docs/38620  doc         Committers Guide and CVS
o [2002/05/31] docs/38772  doc         firewall_type feature not mentioned on Ha
o [2002/06/07] docs/38982  doc         developers-hanbook/Jail fix
o [2002/06/12] docs/39213  doc         No rc(4) man page
o [2002/06/15] docs/39348  doc         kenv fetch of hostname requires dhcp/boot
o [2002/06/19] docs/39530  doc         access(2) man page has unnecessarily broa
o [2002/06/19] docs/39532  doc         'find' man page should
o [2002/06/24] docs/39824  doc         Various tweaks for doc/en_US.ISO8859-1/bo
o [2002/07/04] docs/40196  doc         man find does not describe -follow
o [2002/07/10] docs/40423  doc         Keyboard(4)'s definition of parameters to
o [2002/07/10] docs/40443  doc         Update books/faq/book.sgml for USB .ko's 
o [2002/07/21] docs/40851  doc         [PATCH] "mergemaster -p" in UPDATING's "C
o [2002/07/28] docs/41089  doc         pax -B option does not mention interactio
o [2002/08/02] docs/41270  doc         confusing directions for kernelconfig cha
o [2002/08/07] docs/41423  doc         Update FAQ: attrib command for windows du
o [2002/08/18] docs/41761  doc         Update for /ru/internal/ part of site
o [2002/08/19] docs/41787  doc         man page for route (Section 8) missing de
o [2002/08/19] docs/41791  doc         Documentation formatting error
o [2002/08/19] docs/41807  doc         natd -punch_fw "bug"
o [2002/08/20] docs/41820  doc         Device driver confusion in Handbook (2.3)
a [2002/08/27] docs/42058  doc         Documentation: Installing Oracle 8i onto 
o [2002/10/01] docs/43569  doc         src/share/examples/worm/README out-of-dat
o [2002/10/04] docs/43651  doc         stab(5) incorrectly states to include jus
o [2002/10/09] docs/43861  doc         non-trivial typo in wicontrol man page
o [2002/10/11] docs/43941  doc         Rationale for Upgrade Sequence
o [2002/10/14] docs/44074  doc         ln(1) manual clarifications [patch]
o [2002/10/23] docs/44400  doc         ipfw(8) has contradictions in bridged and
o [2002/10/24] docs/44435  doc         sysctl manpage: add example for tcsh
o [2002/10/29] docs/44594  doc         Handbook doesn't mention drivers.flp for 
o [2002/11/17] docs/45371  doc         man page for exports lacks information on
o [2002/12/02] docs/45940  doc         burncd missing info
o [2002/12/11] docs/46181  doc         "make fetch-recursive" target description
o [2002/12/11] docs/46196  doc         Missing return value in (set_)menu_format
o [2002/12/11] docs/46200  doc         fix for ru_RU.KOI8-R/books/porters-handbo
o [2002/12/16] docs/46291  doc         correlation between HZ kernel config para
o [2002/12/16] docs/46295  doc         please add information to Nvi recovery em
o [2003/01/02] docs/46709  doc         tables in terminfo.5 are broken
o [2003/01/05] docs/46793  doc         DEVICE_POLLING can not be used with SMP, 
o [2003/01/14] docs/47085  doc         boot(8) manpage is incomplete according t
o [2003/01/27] docs/47575  doc         Clarify requirements for IPFW2 in STABLE
o [2003/01/28] docs/47594  doc         [PATH] passwd(5) incorrectly states allow
o [2003/01/30] docs/47690  doc         builtin(1) manpage is wrong about externa
o [2003/01/30] docs/47705  doc         wc(1) manpage has poor explanations.
f [2003/02/02] docs/47818  doc         ln(1) manpage is confusing
f [2003/02/07] docs/48038  doc         [PATCH] add Tips and Tricks section into 
o [2003/02/28] docs/48767  doc         wrong key numbers for left/right windows 
o [2003/03/06] docs/48980  doc         [PATCH] nsgmls -s errors and sect. 3.2.1 
o [2003/03/14] docs/50013  doc         [PATCH] add much more russian holydays
o [2003/03/23] docs/50211  doc         [PATCH] Fix textfile creation
f [2003/03/28] docs/50391  doc         Incorrect information in a man
o [2003/04/03] docs/50573  doc         return values for res_query/res_search/re
f [2003/04/07] docs/50677  doc         [PATCH] update doc/en_US.ISO8859-1/books/
o [2003/04/10] docs/50773  doc         NFS problems by jumbo frames to mention i
o [2003/05/06] docs/51875  doc         atkbd(4) adjustment
o [2003/05/06] docs/51891  doc         DIAGNOSTICS in ed driver manpage don't ma
o [2003/05/07] docs/51921  doc         ls(1) manpage lacks some information abou
o [2003/05/11] docs/52071  doc         [PATCH] Add more information about soft u
o [2003/05/25] docs/52672  doc         Porter's Handbook: couple of corrections
o [2003/06/02] docs/52878  doc         [PATCH] security(7): small clairification
o [2003/06/13] docs/53303  doc         mount(2) man page error
o [2003/06/14] docs/53315  doc         [PATCH] remove extraneous whitespace at t
o [2003/06/18] docs/53454  doc         wrong sample code in manpage of wcwidth(3
o [2003/06/19] docs/53501  doc         [PATCH] Handbook: update snapshots sectio
o [2003/06/20] docs/53575  doc         Change to Handbook Section 20.9
o [2003/06/21] docs/53596  doc         Updates to mt manual page
o [2003/06/25] docs/53732  doc         quota output and man page do not document
o [2003/06/26] docs/53751  doc         bus_dma(9) incorrectly documents BUS_DMA_
o [2003/07/11] docs/54380  doc         [PATCH] document additional perl variable
o [2003/07/11] docs/54391  doc         Document that glob(3) respects LC_COLLATE
o [2003/07/20] docs/54678  doc         [patch] add PACKAGESITE to packages chapt
o [2003/07/22] docs/54752  doc         bus_dma explained in ISA section: should 
o [2003/07/22] docs/54769  doc         [patch] updates to FAQ
o [2003/07/23] docs/54789  doc         [PATCH] brush up the "New Users" article
o [2003/07/24] docs/54806  doc         [patch] adds fvwm2 to x11-wm
o [2003/07/25] docs/54879  doc         man 1 jot, -r description
o [2003/07/28] docs/54995  doc         Error in accept(2) man page
o [2003/07/28] docs/54999  doc         Documentation Project Primer doesn't conf
o [2003/08/03] docs/55207  doc         [patch] update acroread section & add loc
o [2003/08/06] docs/55306  doc         [patch] adds filemanagers to desktop appl
o [2003/08/11] docs/55458  doc         [patch] add useful content & hints to por
o [2003/08/11] docs/55482  doc         DUMP has access to block devices in a JAI
o [2003/08/13] docs/55538  doc         [patch] add screenshots to desktop chapte
o [2003/08/16] docs/55653  doc         chflags.1 - note that not all tools chfla
o [2003/08/22] docs/55883  doc         advanced-networking/chapter.sgml
o [2003/09/04] docs/56408  doc         [PATCH] add <filename> around app-default
o [2003/09/04] docs/56452  doc         [patch]Add EXTRACT_DEPENDS&PATCH_DEPENDS 
o [2003/09/13] docs/56745  doc         Some suggestions for the Bibliography cha
o [2003/09/14] docs/56872  doc         [Patch] Talk about EVFILT_NETDEV in kqueu
o [2003/09/14] docs/56883  doc         Inadequately-documented charter for freeb
o [2003/09/15] docs/56901  doc         [patch] articles/diskless-x: fix bad engl
o [2003/09/15] docs/56902  doc         [patch] articles/fbsd-from-scratch: add/f
o [2003/09/15] docs/56903  doc         [patch] articles/fonts: add application t
o [2003/09/16] docs/56915  doc         [patch] articles/fonts: update links
o [2003/09/16] docs/56932  doc         [patch] articles/releng-packages: add "no
o [2003/09/16] docs/56936  doc         [patch] articles/java-tomcat: add applica
o [2003/09/18] docs/56981  doc         man terminfo(5) from libncurses does not 
o [2003/09/22] docs/57118  doc         
o [2003/09/24] docs/57153  doc         S_IRWXU missing in fstat(2) man page?
o [2003/09/25] docs/57209  doc         [patch] article/mh: add missing docbook t
o [2003/09/29] docs/57388  doc         INSTALL.TXT enhancement: mention ok promp
o [2003/10/04] docs/57569  doc         error on gensetdefs(8) man page
o [2003/10/06] docs/57669  doc         IFMIB(4) man page uses sysctl(3) incorrec
o [2003/10/10] docs/57838  doc         missing in docu: port Makefile target 'pa
o [2003/10/12] docs/57926  doc         amd.conf.5 poorly format as it has both m

140 problems total.


From l.ertl at univie.ac.at  Mon Oct 13 18:37:24 2003
From: l.ertl at univie.ac.at (Lukas Ertl)
Date: Mon, 13 Oct 2003 20:36:11 +0200 (CEST)
Subject: Architecture Handbook
In-Reply-To: <20031013174018.GA7787@electra.cse.Buffalo.EDU>
References: <20031013174018.GA7787@electra.cse.Buffalo.EDU>
Message-ID: <20031013203514.N596@korben.in.tern>

On Mon, 13 Oct 2003, Ken Smith wrote:

> There are a few sections marked with * - e.g. "*UFS", "*AFS".  Are
> those supposed to be markers for sections someone is working on, or
> are they sections someone wishes someone was working on?

I think the latter - these sections need to be written.

regards,
le

-- 
Lukas Ertl                             eMail: l.ertl at univie.ac.at
UNIX Systemadministrator               Tel.:  (+43 1) 4277-14073
Vienna University Computer Center      Fax.:  (+43 1) 4277-9140
University of Vienna                   http://mailbox.univie.ac.at/~le/


From kensmith at cse.Buffalo.EDU  Mon Oct 13 19:07:21 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 13 Oct 2003 15:07:19 -0400
Subject: Architecture Handbook
In-Reply-To: <20031013203514.N596@korben.in.tern>
References: <20031013174018.GA7787@electra.cse.Buffalo.EDU>
	<20031013203514.N596@korben.in.tern>
Message-ID: <20031013190719.GA10024@electra.cse.Buffalo.EDU>

On Mon, Oct 13, 2003 at 08:36:11PM +0200, Lukas Ertl wrote:

> > There are a few sections marked with * - e.g. "*UFS", "*AFS".  Are
> > those supposed to be markers for sections someone is working on, or
> > are they sections someone wishes someone was working on?
> 
> I think the latter - these sections need to be written.

Hmm, figures...

I could have gotten them started at least but can't do it right now
due to a fairly major conflict of interests (I'm proof-reading a
textbook).  Maybe later. :-(

I've spent a week or so of the past three years setting it up so
students could muck around with the UFS code without killing the
entire machine, so I've actually "worked a bit" on the UFS code...
Doing that to the new UFS-2 code was such a pain last time I've
got a student writing "edufs" and we'll use that for the Kernel
Hacking class projects instead of making a "copy" of the UFS code
next Spring.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From res17fyz at verizon.net  Mon Oct 13 20:20:16 2003
From: res17fyz at verizon.net (jc.sb)
Date: Mon, 13 Oct 2003 13:10:48 -0700
Subject: docs/57974: man page apropos for select macros (FD_SET, etc) doesnt
	exist
Message-ID: <BMEPILKCGAMLADKPFPHAAEFECBAA.res17fyz@verizon.net>


>Number:         57974
>Category:       docs
>Synopsis:       man page apropos for select macros (FD_SET, etc) doesnt exist
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 13 13:20:13 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan Cline
>Release:        FreeBSD 4.8-RELEASE i386
>Organization:
none
>Environment:
System: FreeBSD d2fs1.xyz.local 4.8-RELEASE FreeBSD 4.8-RELEASE #1: Thu May
8 17:24:15 PDT 2003 root at d2fs1.xyz.local:/usr/src/sys/compile/D2FS1 i386


>Description:

While a man page for select() from sys/select.h exists,
the macros relating
to that function are not apropos.  Presumably because they're
macros, rather than functions, though they are publically
callable and well-used.

>How-To-Repeat:
	'man FD_SET'    - yields nothing
      'man -k FD_SET' - yields nothing
      'man select'    - as expected
      'man -k select' - as expected
>Fix:
Unknown.




>Release-Note:
>Audit-Trail:
>Unformatted:


From tkatayam at VCSEL.org  Mon Oct 13 22:50:57 2003
From: tkatayam at VCSEL.org (tkatayam at VCSEL.org)
Date: 13 Oct 2003 22:46:21 -0000
Subject: docs/57978: Type miss of GPIB in Hardware Notes
Message-ID: <20031013224621.45471.qmail@PML.VCSEL.org>


>Number:         57978
>Category:       docs
>Synopsis:       Type miss of GPIB in Hardware Notes
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 13 15:50:18 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     KATAYAMA Takeo
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:

	
>Description:
	I found an error in Section 3.15 "Miscellaneous" of FreeBSD/i386 
	5.1-RELEASE Hardware Notes and newer than 4.3R. The 4th item is
	denoted as "GPB and Transputer drivers".  I consider "GPB" to be
	an error of "GPIB".

>How-To-Repeat:
	
>Fix:

	
>Release-Note:
>Audit-Trail:
>Unformatted:


From kensmith at FreeBSD.org  Tue Oct 14 01:58:17 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Mon, 13 Oct 2003 18:58:17 -0700 (PDT)
Subject: docs/57799: pam_self(8) man page is wrong
Message-ID: <200310140158.h9E1wH65017150@freefall.freebsd.org>

Synopsis: pam_self(8) man page is wrong

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Mon Oct 13 18:57:23 PDT 2003
Responsible-Changed-Why: 

I'll try this one.


http://www.freebsd.org/cgi/query-pr.cgi?pr=57799


From kensmith at cse.Buffalo.EDU  Tue Oct 14 03:48:40 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 13 Oct 2003 23:48:38 -0400
Subject: SYSINIT() fixes for Architecture Manual
Message-ID: <20031014034838.GA20484@electra.cse.Buffalo.EDU>


Murray suggested I just send this here, and he'd chime in if nobody
else feels like enough of an authority to say whether or not I'm
lying.  :-)

While working on PR docs/57568 to fix the SYSINIT() examples I
decided to try and clarify a little bit what SYSINIT() is/isn't
used for.  Can anyone say one way or another if I hit the target?

Thanks.

--- chapter.sgml_orig	Sat Oct 11 20:07:09 2003
+++ chapter.sgml	Mon Oct 13 21:23:37 2003
@@ -49,17 +49,27 @@
 
     <para>Sysinit uses two priorities when ordering the functions for
       execution.  The first priority is a subsystem ID giving an
-      overall order Sysinit's dispatch of functions. Current predeclared
-      ID's are in <filename>&lt;sys/kernel.h></filename> in the enum
+      overall order for Sysinit's dispatch of functions. Current predeclared
+      ID's are in <filename>&lt;sys/kernel.h&gt;</filename> in the enum
       list <literal>sysinit_sub_id</literal>. The second priority used
       is an element order within the subsystem. Current predeclared
       subsystem element orders are in
-      <filename>&lt;sys/kernel.h></filename> in the enum list
+      <filename>&lt;sys/kernel.h&gt;</filename> in the enum list
       <literal>sysinit_elem_order</literal>.</para>
 
     <para>There are currently two uses for Sysinit. Function dispatch
       at system startup and kernel module loads, and function dispatch
-      at system shutdown and kernel module unload.</para>
+      at system shutdown and kernel module unload.  Kernel subsystems
+      often use system startup Sysinits to initialize data structures,
+      for example the process scheduling subsystem uses a Sysinit to
+      initialize the run queue data structures.  Device drivers
+      should avoid using <literal>SYSINIT()</literal> directly.
+      Instead drivers for real devices that are part of a bus structure
+      should use <literal>DRIVER_MODULE()</literal> to provide a
+      function that detects the device and, if it is present, initializes
+      the device. It will do a few things specific to devices and then calls
+      <literal>SYSINIT()</literal> itself.  For pseudo-devices, which are
+      not part of a bus structure, use <literal>DEV_MODULE()</literal>.</para>
   </sect1>
 
 
@@ -72,14 +82,14 @@
       <sect3>
         <title>Headers</title>
 
-          <programlisting>&lt;sys/kernel.h></programlisting>
+          <programlisting>&lt;sys/kernel.h&gt;</programlisting>
       </sect3>
 
       <sect3>
         <title>Macros</title>
 
         <programlisting>SYSINIT(uniquifier, subsystem, order, func, ident)
-        SYSUNINIT(uniquifier, subsystem, order, func, ident)</programlisting>
+SYSUNINIT(uniquifier, subsystem, order, func, ident)</programlisting>
       </sect3>
     </sect2>
 
@@ -90,21 +100,22 @@
         necessary sysinit data in Sysinit's startup data set for
         Sysinit to sort and dispatch a function at system startup and
         module load.  <literal>SYSINIT()</literal> takes a uniquifier
-        that Sysinit uses identify the particular function dispatch
+        that Sysinit uses to identify the particular function dispatch
         data, the subsystem order, the subsystem element order, the
         function to call, and the data to pass the function. All
         functions must take a constant pointer argument.
         </para>
 
-      <para>For example:</para>
+      <example>
+	<title>Example of a <literal>SYSINIT()</literal></title>
 
-      <programlisting>#include &lt;sys/kernel.h>
+        <programlisting>#include &lt;sys/kernel.h&gt;
 
 void foo_null(void *unused)
 {
         foo_doo();
 }
-SYSINIT(foo_null, SI_SUB_FOO, SI_ORDER_FOO, NULL);
+SYSINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_null, NULL);
 
 struct foo foo_voodoo = {
         FOO_VOODOO;
@@ -115,26 +126,34 @@
         struct foo *foo = (struct foo *)vdata;
         foo_data(foo);
 }
-SYSINIT(foo_arg, SI_SUB_FOO, SI_ORDER_FOO, foo_voodoo);
-      </programlisting>
+SYSINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, foo_voodoo);
+        </programlisting>
+      </example>
+
+      <para>Note that <literal>SI_SUB_FOO</literal> and
+	<literal>SI_ORDER_FOO</literal> need to be in the
+	<literal>sysinit_sub_id</literal> and
+	<literal>sysinit_elem_order</literal> enum's as mentioned above.
+	Either use existing ones or add your own to the enum's.</para>
     </sect2>
 
     <sect2>
       <title>Shutdown</title>
 
-      <para>The <literal>SYSUNINIT()</literal> macro behaves similarly
+      <para>The <literal>SYSUNINIT()</literal> macro behaves similar
         to the <literal>SYSINIT()</literal> macro except that it adds
         the Sysinit data to Sysinit's shutdown data set.</para>
 
-      <para>For example:</para>
+      <example>
+	<title>Example of a <literal>SYSUNINIT()</literal></title>
 
-      <programlisting>#include &lt;sys/kernel.h>
+	<programlisting>#include &lt;sys/kernel.h&gt;
 
 void foo_cleanup(void *unused)
 {
         foo_kill();
 }
-SYSUNINIT(foo_cleanup, SI_SUB_FOO, SI_ORDER_FOO, NULL);
+SYSUNINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_cleanup, NULL);
 
 struct foo_stack foo_stack = {
         FOO_STACK_VOODOO;
@@ -143,8 +162,9 @@
 void foo_flush(void *vdata)
 {
 }
-SYSUNINIT(foo_flush, SI_SUB_FOO, SI_ORDER_FOO, foo_stack);
-      </programlisting>
+SYSUNINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, foo_stack);
+	</programlisting>
+      </example>
     </sect2>
   </sect1>
 </chapter>


-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From rf358197 at ohio.edu  Tue Oct 14 11:20:13 2003
From: rf358197 at ohio.edu (Russell Francis)
Date: Tue, 14 Oct 2003 04:20:11 -0700 (PDT)
Subject: docs/57669: IFMIB(4) man page uses sysctl(3) incorrectly
	inexample code
Message-ID: <200310141120.h9EBKBx4083759@freefall.freebsd.org>

The following reply was made to PR docs/57669; it has been noted by GNATS.

From: Russell Francis <rf358197 at ohio.edu>
To: freebsd-gnats-submit at FreeBSD.org, ted at erg.sri.com
Cc:  
Subject: Re: docs/57669: IFMIB(4) man page uses sysctl(3) incorrectly in example
 code
Date: Tue, 14 Oct 2003 07:19:53 -0400

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig058844B390B808621B29F43D
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Ted,
 
 I saw your bug report at FreeBSD and thought I would let you know that
 the changes you suggested have allready been made.  If you cvsup a more
 recent version of FreeBSD you should see them.
 
 Thanks,
 Russ
 
 --------------enig058844B390B808621B29F43D
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.1 (FreeBSD)
 
 iD8DBQE/i9vil8gE/LToDToRAqLyAJ9gj14WNjLneiAGWcg+/lhMmfXysACgirW5
 e9gy2xu0b6sX4DQTi9p0Jqc=
 =wjMj
 -----END PGP SIGNATURE-----
 
 --------------enig058844B390B808621B29F43D--
 


From j.el-rayes at daemon.li  Tue Oct 14 20:25:35 2003
From: j.el-rayes at daemon.li (Josef El-Rayes)
Date: Tue, 14 Oct 2003 22:26:53 +0200
Subject: correct spelling?
Message-ID: <20031014202653.GA271@jenny.daemon.li>

hi!

as i did not find correct spelling for these two words, in our word list
and on the o'reilly word list, i ask if somebody could tell me whether
it is:

	o operating system or operating-system
	o core team or core-team

(i expect without '-')

-josef
-- 
www: http://www.daemon.li
nic-hdl: JER1080312-NICAT
BSD in AT: www.bsdcode.at
"Make World - Not War!"


From trhodes at FreeBSD.org  Tue Oct 14 20:32:23 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue, 14 Oct 2003 16:31:52 -0400
Subject: correct spelling?
In-Reply-To: <20031014202653.GA271@jenny.daemon.li>
References: <20031014202653.GA271@jenny.daemon.li>
Message-ID: <20031014163152.02f49504.trhodes@FreeBSD.org>

On Tue, 14 Oct 2003 22:26:53 +0200
Josef El-Rayes <j.el-rayes at daemon.li> wrote:

> hi!
> 
> as i did not find correct spelling for these two words, in our word list
> and on the o'reilly word list, i ask if somebody could tell me whether
> it is:
> 
> 	o operating system or operating-system
> 	o core team or core-team
> 
> (i expect without '-')
> 

I have always seen these used without the hyphen.

-- 
Tom Rhodes


From jhb at FreeBSD.org  Tue Oct 14 21:38:23 2003
From: jhb at FreeBSD.org (John Baldwin)
Date: Tue, 14 Oct 2003 17:38:26 -0400 (EDT)
Subject: SYSINIT() fixes for Architecture Manual
In-Reply-To: <20031014034838.GA20484@electra.cse.Buffalo.EDU>
Message-ID: <XFMail.20031014173826.jhb@FreeBSD.org>


On 14-Oct-2003 Ken Smith wrote:
> 
> Murray suggested I just send this here, and he'd chime in if nobody
> else feels like enough of an authority to say whether or not I'm
> lying.  :-)
> 
> While working on PR docs/57568 to fix the SYSINIT() examples I
> decided to try and clarify a little bit what SYSINIT() is/isn't
> used for.  Can anyone say one way or another if I hit the target?
> 
> Thanks.
> 
> [ snip ]
>  
>  void foo_null(void *unused)
>  {
>          foo_doo();
>  }
> -SYSINIT(foo_null, SI_SUB_FOO, SI_ORDER_FOO, NULL);
> +SYSINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_null, NULL);
>  
>  struct foo foo_voodoo = {
>          FOO_VOODOO;
> @@ -115,26 +126,34 @@
>          struct foo *foo = (struct foo *)vdata;
>          foo_data(foo);
>  }
> -SYSINIT(foo_arg, SI_SUB_FOO, SI_ORDER_FOO, foo_voodoo);
> -      </programlisting>
> +SYSINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, foo_voodoo);
> +        </programlisting>
> +      </example>
> +
> +      <para>Note that <literal>SI_SUB_FOO</literal> and
> +     <literal>SI_ORDER_FOO</literal> need to be in the
> +     <literal>sysinit_sub_id</literal> and
> +     <literal>sysinit_elem_order</literal> enum's as mentioned above.
> +     Either use existing ones or add your own to the enum's.</para>
>      </sect2>

You should make sure both SYSINITs have uniqe uniqifiers, maybe
use 'bar' instead of 'foo' for the second example.  Also, you might
want to note that you can do math on the SYSINITs.  For example,
you can do something like this:

static void
mptable_register(void *dummy __unused)
{

        apic_register_enumerator(&mptable_enumerator);
}
SYSINIT(mptable_register, SI_SUB_TUNABLES - 1, SI_ORDER_FIRST,
    mptable_register, NULL)


Also, using 'Sysinit' seems really odd.  I would either go with
'sysinit', 'SYSINIT', or 'system initialization function'.

>      <sect2>
>        <title>Shutdown</title>
>  
> -      <para>The <literal>SYSUNINIT()</literal> macro behaves similarly
> +      <para>The <literal>SYSUNINIT()</literal> macro behaves similar
>          to the <literal>SYSINIT()</literal> macro except that it adds
>          the Sysinit data to Sysinit's shutdown data set.</para>

similar is an adjective, not an adverb.  You are describing how it
behaves, so it should be the adverb form: similarly.  Even if it is
a mouthful to say. :)

> @@ -143,8 +162,9 @@
>  void foo_flush(void *vdata)
>  {
>  }
> -SYSUNINIT(foo_flush, SI_SUB_FOO, SI_ORDER_FOO, foo_stack);
> -      </programlisting>
> +SYSUNINIT(foo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, foo_stack);
> +     </programlisting>
> +      </example>
>      </sect2>
>    </sect1>
>  </chapter>

Again, make sure you have uniqe uniqifiers in this example as
well.

-- 

John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


From kensmith at cse.Buffalo.EDU  Wed Oct 15 01:26:53 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue, 14 Oct 2003 21:26:50 -0400
Subject: Second change to Architecture Manual
Message-ID: <20031015012650.GC15466@electra.cse.Buffalo.EDU>


This is a second change I was thinking might make a good addition
to the Architecture Manual.  Virtually every book that talks about
UNIX devices describes character and block devices.  Developers new
to FreeBSD sometimes wonder what happened to block devices.  And a
lot of places in lots of manual pages, books, etc. still at least
slightly suggest there could be more than just Character devices.

Is this worth adding?  Thanks...

--- chapter.sgml_orig	Fri Oct 10 09:37:18 2003
+++ chapter.sgml	Tue Oct 14 21:21:07 2003
@@ -527,6 +527,22 @@
     </para>
   </sect1>
 
+  <sect1 id="driverbasics-block">
+    <title>Block Devices (Are Gone)</title>
+
+    <para>Developers familiar with other UNIX systems expect there to
+      be a second type of device known as block devices.  On those other
+      UNIX systems block devices are associated with the buffer cache.
+      Data blocks from block devices are buffered inside the kernel 
+      and filesystems get mounted on block devices.  This improves
+      I/O efficiency.  &os; has shifted the management of the buffer
+      cache away from block devices.  It is associated it with the virtual
+      memory system and vnode system used to keep track of open files inside
+      the kernel.  As a result &os; no longer needs block devices and they
+      have been removed from the system.  Only character devices remain.
+    </para>
+  </sect1>
+
   <sect1 id="driverbasics-net">
     <title>Network Drivers</title>
 


-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From ache at nagual.pp.ru  Wed Oct 15 11:29:25 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 15:29:21 +0400
Subject: hiding e-mail adresses needed badly
Message-ID: <20031015112920.GA36404@nagual.pp.ru>

Due to increased activity of SPAM harvesters what are our plans to hide 
our addresses from public WWW? I mean all browseable mailing lists, 
FreeBSD site, CVS via WWW, PRs, ports and docs.

As I think, simple <user [at] domain.com> form will be enough to stop 
them.

-- 
Andrey Chernov | http://ache.pp.ru/


From wkb at freebie.xs4all.nl  Wed Oct 15 13:25:55 2003
From: wkb at freebie.xs4all.nl (Wilko Bulte)
Date: Wed, 15 Oct 2003 15:25:51 +0200
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015112920.GA36404@nagual.pp.ru>
References: <20031015112920.GA36404@nagual.pp.ru>
Message-ID: <20031015132551.GA94612@freebie.xs4all.nl>

On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:


I fail to see why this is relevant to -current but OK.. I think that
the opportunity to do this has long since passed. Just type your name
in Google and see what happens..

Wilko

> Due to increased activity of SPAM harvesters what are our plans to hide 
> our addresses from public WWW? I mean all browseable mailing lists, 
> FreeBSD site, CVS via WWW, PRs, ports and docs.
> 
> As I think, simple <user [at] domain.com> form will be enough to stop 
> them.
> 
> -- 
> Andrey Chernov | http://ache.pp.ru/
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
---end of quoted text---

-- 
|   / o / /_  _   		wilko at FreeBSD.org
|/|/ / / /(  (_)  Bulte				


From ache at nagual.pp.ru  Wed Oct 15 13:36:46 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 17:36:35 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015132551.GA94612@freebie.xs4all.nl>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
Message-ID: <20031015133634.GA37556@nagual.pp.ru>

On Wed, Oct 15, 2003 at 15:25:51 +0200, Wilko Bulte wrote:
> 
> I fail to see why this is relevant to -current but OK.. I think that

Maybe developers@ ?

> the opportunity to do this has long since passed. Just type your name
> in Google and see what happens..

I know, but increasing it at FreeBSD sites make things worse.

> > Due to increased activity of SPAM harvesters what are our plans to hide 
> > our addresses from public WWW? I mean all browseable mailing lists, 
> > FreeBSD site, CVS via WWW, PRs, ports and docs.
> > 
> > As I think, simple <user [at] domain.com> form will be enough to stop 
> > them.

-- 
Andrey Chernov | http://ache.pp.ru/


From phk at phk.freebsd.dk  Wed Oct 15 14:02:24 2003
From: phk at phk.freebsd.dk (Poul-Henning Kamp)
Date: Wed, 15 Oct 2003 16:02:16 +0200
Subject: hiding e-mail adresses needed badly 
In-Reply-To: Your message of "Wed, 15 Oct 2003 17:36:35 +0400."
             <20031015133634.GA37556@nagual.pp.ru> 
Message-ID: <43618.1066226536@critter.freebsd.dk>

In message <20031015133634.GA37556 at nagual.pp.ru>, Andrey Chernov writes:
>On Wed, Oct 15, 2003 at 15:25:51 +0200, Wilko Bulte wrote:
>> 
>> I fail to see why this is relevant to -current but OK.. I think that
>
>Maybe developers@ ?
>
>> the opportunity to do this has long since passed. Just type your name
>> in Google and see what happens..
>
>I know, but increasing it at FreeBSD sites make things worse.

This is water under the bridge, down the river and into the ocean
by now.

And I personally think that by "hiding" the email addresses, you concede
defeat to the spammers.  I don't want to let a bunch of low-life
con-men decide how I can and should use the InterNet.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


From keramida at ceid.upatras.gr  Wed Oct 15 14:39:14 2003
From: keramida at ceid.upatras.gr (Giorgos Keramidas)
Date: Wed, 15 Oct 2003 17:35:45 +0300
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015133634.GA37556@nagual.pp.ru>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<20031015133634.GA37556@nagual.pp.ru>
Message-ID: <20031015143545.GA1667@gothmog.gr>

On 2003-10-15 17:36, Andrey Chernov <ache at nagual.pp.ru> wrote:
>On Wed, Oct 15, 2003 at 15:25:51 +0200, Wilko Bulte wrote:
>>
>> I fail to see why this is relevant to -current but OK.. I think that
>
> Maybe developers@ ?
>
>> the opportunity to do this has long since passed. Just type your name
>> in Google and see what happens..
>
> I know, but increasing it at FreeBSD sites make things worse.

Once an email address has been public it's always public.  You can't
stop spammers from sharing addresses they harvested already by hiding
those addresses now.  They already have them.

Bearing this in mind, it's obvious why hiding your address now won't
solve your immediate spam problem.  It might help in avoiding similar
troubles of future subscribers, but I doubt it will prevent it altogether.


From ache at nagual.pp.ru  Wed Oct 15 15:15:54 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 19:15:43 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015143545.GA1667@gothmog.gr>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<20031015133634.GA37556@nagual.pp.ru> <20031015143545.GA1667@gothmog.gr>
Message-ID: <20031015151542.GA38522@nagual.pp.ru>

On Wed, Oct 15, 2003 at 17:35:45 +0300, Giorgos Keramidas wrote:
> Once an email address has been public it's always public.  You can't
> stop spammers from sharing addresses they harvested already by hiding
> those addresses now.  They already have them.

I mean new spammers and their harvesters, not old ones.

> Bearing this in mind, it's obvious why hiding your address now won't
> solve your immediate spam problem.  It might help in avoiding similar
> troubles of future subscribers, but I doubt it will prevent it altogether.

I solve immediate spam problem in different ways. Suggesting that I mean 
to reduce not immediate but future problems.

-- 
Andrey Chernov | http://ache.pp.ru/


From ache at nagual.pp.ru  Wed Oct 15 15:21:08 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 19:21:03 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <43618.1066226536@critter.freebsd.dk>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk>
Message-ID: <20031015152102.GB38522@nagual.pp.ru>

On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:

> And I personally think that by "hiding" the email addresses, you concede
> defeat to the spammers.  I don't want to let a bunch of low-life
> con-men decide how I can and should use the InterNet.

It sounds heroic, but the position alone not helps to stop low-life 
con-men's invasion.

-- 
Andrey Chernov | http://ache.pp.ru/


From dfr at nlsystems.com  Wed Oct 15 15:50:46 2003
From: dfr at nlsystems.com (Doug Rabson)
Date: 15 Oct 2003 16:49:51 +0100
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015151542.GA38522@nagual.pp.ru>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<20031015143545.GA1667@gothmog.gr>
	<20031015151542.GA38522@nagual.pp.ru>
Message-ID: <1066232987.19154.2.camel@builder02.qubesoft.com>

On Wed, 2003-10-15 at 16:15, Andrey Chernov wrote:
> On Wed, Oct 15, 2003 at 17:35:45 +0300, Giorgos Keramidas wrote:
> > Once an email address has been public it's always public.  You can't
> > stop spammers from sharing addresses they harvested already by hiding
> > those addresses now.  They already have them.
> 
> I mean new spammers and their harvesters, not old ones.
> 
> > Bearing this in mind, it's obvious why hiding your address now won't
> > solve your immediate spam problem.  It might help in avoiding similar
> > troubles of future subscribers, but I doubt it will prevent it altogether.
> 
> I solve immediate spam problem in different ways. Suggesting that I mean 
> to reduce not immediate but future problems.

Unfortunately, your email address is all over the various mail archives
and uncounted mirrors and caches of those archives. The damage is done -
your email address is irreparably compromised, as is mine, sadly.



From jwd at FreeBSD.org  Wed Oct 15 15:58:26 2003
From: jwd at FreeBSD.org (John)
Date: Wed, 15 Oct 2003 11:53:58 -0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015152102.GB38522@nagual.pp.ru>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk> <20031015152102.GB38522@nagual.pp.ru>
Message-ID: <20031015155358.GA87693@BSDWins.Com>

----- Andrey Chernov's Original Message -----
> On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:
> 
> > And I personally think that by "hiding" the email addresses, you concede
> > defeat to the spammers.  I don't want to let a bunch of low-life
> > con-men decide how I can and should use the InterNet.
> 
> It sounds heroic, but the position alone not helps to stop low-life 
> con-men's invasion.

How about if we all pool our resources and come up with a 
freebsd website were we can accumulate all the ways we deal
with the problem. Ports, sendmail rules, postfix, procmail, etc, etc..

-John


From ohlund at woodwrecker.com  Wed Oct 15 16:39:53 2003
From: ohlund at woodwrecker.com (Mark Ohlund)
Date: Wed, 15 Oct 2003 12:39:53 -0400 (EDT)
Subject: Problems with .zip PDF handbook
Message-ID: <60771.12.147.199.194.1066235993.squirrel@www.woodwrecker.com>

It appears the .pdf format of the FreeBSD handbook compressed into .zip
files is bad on the main site plus a number of the mirror sites.

The book ends on page 604 without any of the appendicies and the table of
contents is fouled up.



~Mark.



From ache at nagual.pp.ru  Wed Oct 15 17:33:15 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 15:29:21 +0400
Subject: hiding e-mail adresses needed badly
Message-ID: <20031015112920.GA36404@nagual.pp.ru>

Due to increased activity of SPAM harvesters what are our plans to hide 
our addresses from public WWW? I mean all browseable mailing lists, 
FreeBSD site, CVS via WWW, PRs, ports and docs.

As I think, simple <user [at] domain.com> form will be enough to stop 
them.

-- 
Andrey Chernov | http://ache.pp.ru/
_______________________________________________
freebsd-current at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"


From gurney_j at efn.org  Wed Oct 15 18:13:13 2003
From: gurney_j at efn.org (John-Mark Gurney)
Date: Wed, 15 Oct 2003 11:13:07 -0700
Subject: hiding e-mail adresses needed badly
In-Reply-To: <43618.1066226536@critter.freebsd.dk>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk>
Message-ID: <20031015181307.GA533@funkthat.com>

Poul-Henning Kamp wrote this message on Wed, Oct 15, 2003 at 16:02 +0200:
> And I personally think that by "hiding" the email addresses, you concede
> defeat to the spammers.  I don't want to let a bunch of low-life
> con-men decide how I can and should use the InterNet.

I object to any obfuscating of email addresses.  Once we start doing
that we are no long are easily visible project.  I personlly think
projects that obfuscate email addresses are lame and won't pay
much attention to the project.  If we do start obfuscating email
addresses, I request that my email address NOT be.  I do not want to
hide behind a fake barrier.

Do you really think that email harvesters haven't learned how to deal
with obfuscated email addresses?  Then there are always the really
funny ones that put in their webpage:
<a href="mailto:someone at somedomain.com">someone at somedomain dot com</a>
Ummm, hello!! you just put your bloody email address in the clear in the
href!!  Stupid!

Spam needs to be addressed at a different level than simply trying to
hide your email.  Remeber the whole security through obscurity is no
security at all?  This is just another part of it.

It would be good to get a list of rules that do things like have a
list of people that are known to always sign their email with a pgp/gpg
key, and always accept mail from them, etc.

Sorry for the little rant about this.  I don't want to see the FreeBSD
project alienate it's users due to trying to block developers from spam.

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."


From ache at nagual.pp.ru  Wed Oct 15 18:54:37 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Wed, 15 Oct 2003 22:54:30 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015181307.GA533@funkthat.com>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk> <20031015181307.GA533@funkthat.com>
Message-ID: <20031015185430.GA41141@nagual.pp.ru>

On Wed, Oct 15, 2003 at 11:13:07 -0700, John-Mark Gurney wrote:
> I object to any obfuscating of email addresses.  Once we start doing
> that we are no long are easily visible project.  I personlly think

It depends on obfuscating technique.

> Do you really think that email harvesters haven't learned how to deal
> with obfuscated email addresses?  Then there are always the really
> funny ones that put in their webpage:
> <a href="mailto:someone at somedomain.com">someone at somedomain dot com</a>
> Ummm, hello!! you just put your bloody email address in the clear in the
> href!!  Stupid!

That's you say so and nobody else suggest this so far. Most simple way is
using [at] without mailto: at all. More complex way with maximum
functionality and maximum protection:

<SCRIPT TYPE="text/javascript" SRC="achemail.js"></SCRIPT><NOSCRIPT>
ache [at] nagual.pp.ru</NOSCRIPT>

achemail.js:
------------------------------------------------------
emailname = "ache"
emailserver = "nagual.pp.ru"

document.write("<a href='mailto:" + emailname + "&#64;" + emailserver + "'>");
document.write(emailname + "&#64;" + emailserver);
document.write("</a>");
-------------------------------------------------------

-- 
Andrey Chernov | http://ache.pp.ru/


From des at des.no  Wed Oct 15 20:10:13 2003
From: des at des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=)
Date: Wed, 15 Oct 2003 22:10:05 +0200
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015152102.GB38522@nagual.pp.ru> (Andrey Chernov's message
 of "Wed, 15 Oct 2003 19:21:03 +0400")
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk>
	<20031015152102.GB38522@nagual.pp.ru>
Message-ID: <xzpn0c28dpe.fsf@dwp.des.no>

Andrey Chernov <ache at nagual.pp.ru> writes:
> On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:
> > And I personally think that by "hiding" the email addresses, you concede
> > defeat to the spammers.  I don't want to let a bunch of low-life
> > con-men decide how I can and should use the InterNet.
> It sounds heroic, but the position alone not helps to stop low-life 
> con-men's invasion.

Stop whining and install SpamAssassin.

DES
-- 
Dag-Erling Sm?rgrav - des at des.no


From underway at comcast.net  Wed Oct 15 20:37:20 2003
From: underway at comcast.net (Gary W. Swearingen)
Date: Wed, 15 Oct 2003 13:32:02 -0700
Subject: correct spelling?
Message-ID: <cyd6cyqm2l.6cy@mail.comcast.net>

Josef El-Rayes <j.el-rayes at daemon.li> writes:

> as i did not find correct spelling for these two words, in our word list
> and on the o'reilly word list, i ask if somebody could tell me whether
> it is:
>
> 	o operating system or operating-system
> 	o core team or core-team

I'm glad you asked that.  Many geeks seem to just ignore the existence
of hyphens.  If schools bother to teach about hyphenation rules, they
probably do little more than mention them, so hyphens are often
omitted even in formal writing by people who write for a living.  I
suspect that are increasingly making a feature of their bug by
teaching that hyphens are obsolete.  But it makes for some awkward
(and annoying) reading, IMO.

I must admit that I'm unable to state any hyphenation rules, but the
general principle is to use hyphens to help readers' brains group
words properly while reading quickly.  (Otherwise, the brain tends to
stumble to make sense of nonsensical grouping.) Examples:

  Language-based printers, such as PostScript printers...
    -- If it was "Language based printers, ...", the brain
       can stop and wonder what a "based printer" is, because
       English tends to add adjectives from right to left, as
       in "long coal train" and not "coal long train".)

   The most-often-seen omission is the one in "*-based".
    -- I omitted the second hyphen in my first draft, FWIW.

  The FreeBSD operating system is good.
     -- Normal adjective rules apply.

  The operating-system software is good.
     -- To help the reader not read this as "The operating
        system-software is good.

  Having operating system-software is better than having
  non-operating system-software.
     -- I don't know if these hyphens "should" be there or not,
     but I think they help and I'd use them.

Treat "core team" (and "open source" and etc.) similarly.  I suppose
that there are words that are always hypenated, but I can't think of
any at the moment.

I see one example in the Handbook where a commonly-hyphenated phrase
is used in a situation where it probably should not be hyphenated:

   ...work on it full-time, ...


From des at des.no  Wed Oct 15 20:55:31 2003
From: des at des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=)
Date: Wed, 15 Oct 2003 22:55:23 +0200
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015203428.GA42399@nagual.pp.ru> (Andrey Chernov's message
 of "Thu, 16 Oct 2003 00:34:28 +0400")
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk>
	<20031015152102.GB38522@nagual.pp.ru> <xzpn0c28dpe.fsf@dwp.des.no>
	<20031015203428.GA42399@nagual.pp.ru>
Message-ID: <xzpismq8blw.fsf@dwp.des.no>

Andrey Chernov <ache at nagual.pp.ru> writes:
> On Wed, Oct 15, 2003 at 22:10:05 +0200, Dag-Erling Sm?rgrav wrote:
> > Stop whining and install SpamAssassin.
> I use 4 filters combined already + spam back report tools.  This includes
> bogofilter which gives better results for me than SpamAssasin. All that is
> not enough.

Try

use_bayes 0
use_dcc 1
use_razor2 1

score MICROSOFT_EXECUTABLE 5.0
score RAZOR2_CHECK 5.0
score DCC_CHECK 2.5

in SpamAssassin's local.cf, and ditch all the other crap.

DES
-- 
Dag-Erling Sm?rgrav - des at des.no


From mjohnston at skyweb.ca  Wed Oct 15 21:29:58 2003
From: mjohnston at skyweb.ca (Mark Johnston)
Date: Wed, 15 Oct 2003 16:29:53 -0500
Subject: correct spelling?
In-Reply-To: <cyd6cyqm2l.6cy@mail.comcast.net>
References: <cyd6cyqm2l.6cy@mail.comcast.net>
Message-ID: <20031015212952.GD1069@omoikane.mb.skyweb.ca>

Josef El-Rayes wrote (quoted by "Gary W. Swearingen"):
> > as i did not find correct spelling for these two words, in our word list
> > and on the o'reilly word list, i ask if somebody could tell me whether
> > it is:
> >
> > 	o operating system or operating-system
> > 	o core team or core-team

These depend, as hyphenation often does, on how you are using the
phrases.  I don't remember the exact grammatical terms, but when you're
using "core team" as a noun (the core team), it's not hyphenated.  When
you use it as a compound adjective (the core-team mailing list), it's
hyphenated.

The mailing list for the core team is core at FreeBSD.org.
The core-team mailing list is core at FreeBSD.org.

You can use sysctl(8) to adjust many settings of your operating system.
You can use sysctl(8) to adjust many operating-system settings.

"Gary W. Swearingen" wrote:
>   Language-based printers, such as PostScript printers...
>     -- If it was "Language based printers, ...", the brain
>        can stop and wonder what a "based printer" is, because
>        English tends to add adjectives from right to left, as
>        in "long coal train" and not "coal long train".)

Right - same principle as above.  PostScript printers are language
based.  Language-based printers include PostScript printers.

>    The most-often-seen omission is the one in "*-based".
>     -- I omitted the second hyphen in my first draft, FWIW.
> 
>   The FreeBSD operating system is good.
>      -- Normal adjective rules apply.
> 
>   The operating-system software is good.
>      -- To help the reader not read this as "The operating
>         system-software is good.

As above.  "operating-system" is used as an adjective here.

>   Having operating system-software is better than having
>   non-operating system-software.
>      -- I don't know if these hyphens "should" be there or not,
>      but I think they help and I'd use them.

I don't believe that the system-software hyphens are correct here.

> Treat "core team" (and "open source" and etc.) similarly.  I suppose
> that there are words that are always hypenated, but I can't think of
> any at the moment.

Your use of "non-" earlier was a good example.

> I see one example in the Handbook where a commonly-hyphenated phrase
> is used in a situation where it probably should not be hyphenated:
> 
>    ...work on it full-time, ...

I work full time at my full-time job.


From ache at nagual.pp.ru  Wed Oct 15 21:59:15 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Thu, 16 Oct 2003 01:59:08 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <xzpismq8blw.fsf@dwp.des.no>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk> <20031015152102.GB38522@nagual.pp.ru>
	<xzpn0c28dpe.fsf@dwp.des.no> <20031015203428.GA42399@nagual.pp.ru>
	<xzpismq8blw.fsf@dwp.des.no>
Message-ID: <20031015215907.GA43137@nagual.pp.ru>

On Wed, Oct 15, 2003 at 22:55:23 +0200, Dag-Erling Sm?rgrav wrote:

> score MICROSOFT_EXECUTABLE 5.0

I already reject all executable attachments using sentinel.

> score RAZOR2_CHECK 5.0
> score DCC_CHECK 2.5

When I play with SpamAssassin before, I use something like that. It not
helps much since spammers tends to write completely new texts each time
nowdays and obfuscate words to not much even fuzzy checksums.

In any case, I don't want this discussion to turn into 'how to prevent 
current SPAM', I handle it well (99% rejected at the milter level, but 1% 
still is big enough). My point of view is: if spammer don't have my 
address, it can't do even 1%.

-- 
Andrey Chernov | http://ache.pp.ru/


From kensmith at cse.Buffalo.EDU  Thu Oct 16 01:05:27 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Wed, 15 Oct 2003 21:05:25 -0400
Subject: PR docs/21708
Message-ID: <20031016010525.GA14918@electra.cse.Buffalo.EDU>


What is the procedure for suggesting a PR that appears to be old and
forgotten be closed?

PR docs/21708 complains that the wording for the "timeout" value
in kevent(2) is ambiguous.  I don't know if someone fixed it on their
own but the current wording is:

     If
     timeout is a non-NULL pointer, it specifies a maximum interval to wait
     for an event, which will be interpreted as a struct timespec.  If timeout
     is a NULL pointer, kevent() waits indefinitely.  To effect a poll, the
     timeout argument should be non-NULL, pointing to a zero-valued timespec
     structure.  The same array may be used for the changelist and eventlist.

That does seem to address the originator's concerns - "specifies a maximum
interval" sounds like it is a relative value to me.

Thanks.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From trhodes at FreeBSD.org  Thu Oct 16 08:15:33 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 16 Oct 2003 04:15:23 -0400
Subject: PR docs/21708
In-Reply-To: <20031016010525.GA14918@electra.cse.Buffalo.EDU>
References: <20031016010525.GA14918@electra.cse.Buffalo.EDU>
Message-ID: <20031016041523.33fd236a.trhodes@FreeBSD.org>

On Wed, 15 Oct 2003 21:05:25 -0400
Ken Smith <kensmith at cse.Buffalo.EDU> wrote:

> 
> What is the procedure for suggesting a PR that appears to be old and
> forgotten be closed?
> 
> PR docs/21708 complains that the wording for the "timeout" value
> in kevent(2) is ambiguous.  I don't know if someone fixed it on their
> own but the current wording is:
> 

If it seems to be fixed either close it or set it to feedback for
a period of time.  I think the PR doc has more information on this
that I can comment on.

-- 
Tom Rhodes


From trhodes at FreeBSD.org  Thu Oct 16 08:16:02 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 16 Oct 2003 03:46:35 -0400
Subject: Second change to Architecture Manual
In-Reply-To: <20031015012650.GC15466@electra.cse.Buffalo.EDU>
References: <20031015012650.GC15466@electra.cse.Buffalo.EDU>
Message-ID: <20031016034635.02278753.trhodes@FreeBSD.org>

On Tue, 14 Oct 2003 21:26:50 -0400
Ken Smith <kensmith at cse.Buffalo.EDU> wrote:

> 
> This is a second change I was thinking might make a good addition
> to the Architecture Manual.  Virtually every book that talks about
> UNIX devices describes character and block devices.  Developers new
> to FreeBSD sometimes wonder what happened to block devices.  And a
> lot of places in lots of manual pages, books, etc. still at least
> slightly suggest there could be more than just Character devices.
> 
> Is this worth adding?  Thanks...
> 
> --- chapter.sgml_orig	Fri Oct 10 09:37:18 2003
> +++ chapter.sgml	Tue Oct 14 21:21:07 2003
> @@ -527,6 +527,22 @@
>      </para>
>    </sect1>
>  
> +  <sect1 id="driverbasics-block">
> +    <title>Block Devices (Are Gone)</title>
> +
> +    <para>Developers familiar with other UNIX systems expect there to
> +      be a second type of device known as block devices.  On those other
> +      UNIX systems block devices are associated with the buffer cache.
> +      Data blocks from block devices are buffered inside the kernel 
> +      and filesystems get mounted on block devices.  This improves
> +      I/O efficiency.  &os; has shifted the management of the buffer
> +      cache away from block devices.  It is associated it with the virtual
> +      memory system and vnode system used to keep track of open files inside
> +      the kernel.  As a result &os; no longer needs block devices and they
> +      have been removed from the system.  Only character devices remain.
> +    </para>
> +  </sect1>
> +
>    <sect1 id="driverbasics-net">
>      <title>Network Drivers</title>

I think it would add value.  I'm sure someone will read it, hell, I
just read over it.

You may want to use the &unix; entity, use 'file systems', and perhaps
use a semicolon to 'hook' the last sentence to the previous.

How does that sound?  :)

-- 
Tom Rhodes


From jmt at twilley.org  Thu Oct 16 08:20:11 2003
From: jmt at twilley.org (Jack Twilley)
Date: Thu, 16 Oct 2003 01:10:35 -0700 (PDT)
Subject: docs/58111: Handbook 12.4.3 Rebuilding ATA RAID1 Arrays contains
	errors 
Message-ID: <20031016081035.9EE2D3F546@duchess.twilley.org>


>Number:         58111
>Category:       docs
>Synopsis:       Handbook 12.4.3 Rebuilding ATA RAID1 Arrays contains errors
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 16 01:20:09 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Jack Twilley
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
self 
>Environment:
System: FreeBSD duchess.twilley.org 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Mon Jun 16 07:00:17 PDT 2003 root@:/usr/obj/usr/src/sys/DUCHESS i386


	
>Description:
        Section 12.4.3 of the FreeBSD Handbook discusses rebuilding
        ATA RAID1 arrays.  The example case is of a Promise IDE RAID
        card.  I have one of these, and recently had the need to rebuild
        the RAID array.  During this process, I discovered two errors
        in the documentation:

         * step 3 is incomplete
           "Reattach the disk as a spare:" has a command to reattach 
           the disk, but no command to attach the new disk to the array
           as a spare disk.

         * step 5 is obsolete
           The documentation reports that the rebuild command hangs until
           complete.  In fact, the rebuild command returns immediately
           and the disk is rebuilt in the background.

	
>How-To-Repeat:
	
>Fix:
        Replace the old step 3 with something like this:

        3.  Reattach the disk as a spare:

		# atacontrol attach 3
		Master:  ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5
		Slave:   no device present
		# atacontrol addspare ar0 ad6
		<appropriate output here, stupidly didn't save it>

        Replace the old step 5 with something like this:

        5.  The rebuild command returns immediately.  You can check on
            the progress by issuing the following command:

	


>Release-Note:
>Audit-Trail:
>Unformatted:


From dot at dotat.at  Thu Oct 16 09:19:17 2003
From: dot at dotat.at (Tony Finch)
Date: Thu, 16 Oct 2003 10:19:00 +0100
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015215907.GA43137@nagual.pp.ru>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk> <20031015152102.GB38522@nagual.pp.ru>
	<xzpn0c28dpe.fsf@dwp.des.no> <20031015203428.GA42399@nagual.pp.ru>
	<xzpismq8blw.fsf@dwp.des.no> <20031015215907.GA43137@nagual.pp.ru>
Message-ID: <20031016091900.GA32662@chiark.greenend.org.uk>

On Thu, Oct 16, 2003 at 01:59:08AM +0400, Andrey Chernov wrote:
> 
> In any case, I don't want this discussion to turn into 'how to prevent 
> current SPAM', I handle it well (99% rejected at the milter level, but 1% 
> still is big enough).

	"Instead of thinking of spam as a disease that might be eliminated,
	it is more useful to think of it like crime, war and cockroaches.
	It is not realistic to expect to eliminate any of these, no matter
	how much anyone might wish otherwise. Therefore the best we can
	hope to accomplish is to bring spam under reasonable control"
		-- Dave Crocker

Tony.
-- 
f.a.n.finch  <dot at dotat.at>  http://dotat.at/
RATTRAY HEAD TO BERWICK ON TWEED: SOUTH OR SOUTHEAST 4. FAIR, PATCHY CLOUD AT
TIMES. GOOD. SLIGHT TO MODERATE.


From pmes at btinet.net  Thu Oct 16 09:43:54 2003
From: pmes at btinet.net (Peter Schultz)
Date: Thu, 16 Oct 2003 04:43:27 -0500
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015132551.GA94612@freebie.xs4all.nl>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
Message-ID: <3F8E683F.9050200@btinet.net>

At this point in time it's downright irresponsible not to hide our 
addresses.

I've been lurking on this list about a month to get caught up with 
-current issues.  Friday was both the first mail I sent to the list,
and the first use of this e-mail address.  The only incoming mail was 
from the FreeBSD lists I subscribed to.  However, since that fateful 
e-mail I have been viciously attacked by spammers posing as Microsoft 
security updaters.  These spams include attachments making them all 
around 150KB in size.  Maybe others of you have seen them?

As far as I can tell, these guys are targeting the FreeBSD lists, 
exploiting them terribly!  This list's charter states that spam will be 
blocked.  Please enforce the list charter, with prejudice.

It would be best if subscribers could just choose to have their address 
published or not.  I can understand being so dedicated to the cause that 
you're willing to take on some spam.  Non-subscribers addresses should 
definitely not be published.

Sincerely,
Pete...

Wilko Bulte wrote:
> On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:
> 
> 
> I fail to see why this is relevant to -current but OK.. I think that
> the opportunity to do this has long since passed. Just type your name
> in Google and see what happens..
> 
> Wilko
> 
> 
>>Due to increased activity of SPAM harvesters what are our plans to hide 
>>our addresses from public WWW? I mean all browseable mailing lists, 
>>FreeBSD site, CVS via WWW, PRs, ports and docs.
>>
>>As I think, simple <user [at] domain.com> form will be enough to stop 
>>them.
>>
>>-- 
>>Andrey Chernov | http://ache.pp.ru/
> 
> ---end of quoted text---
> 



From steve at sohara.org  Thu Oct 16 10:56:02 2003
From: steve at sohara.org (Steve O'Hara-Smith)
Date: Thu, 16 Oct 2003 12:49:38 +0100
Subject: hiding e-mail adresses needed badly
In-Reply-To: <3F8E683F.9050200@btinet.net>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<3F8E683F.9050200@btinet.net>
Message-ID: <20031016124938.354fe903.steve@sohara.org>

On Thu, 16 Oct 2003 04:43:27 -0500
Peter Schultz <pmes at btinet.net> wrote:

> However, since that fateful 
> e-mail I have been viciously attacked by spammers posing as Microsoft 
> security updaters.  These spams include attachments making them all 
> around 150KB in size.  Maybe others of you have seen them?

	Certainly have - they're not spammers it's a worm, called Swen.
It targets an amazing variety of things, including every email address
it can get hold of. One of my accounts gets about a hundred a day of
these *still*. If you get infected it filters your inbox and removes
attempts to reinfect you so that you don't see it at all.


From ertr1013 at student.uu.se  Thu Oct 16 11:04:03 2003
From: ertr1013 at student.uu.se (Erik Trulsson)
Date: Thu, 16 Oct 2003 13:03:57 +0200
Subject: hiding e-mail adresses needed badly
In-Reply-To: <3F8E683F.9050200@btinet.net>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl> <3F8E683F.9050200@btinet.net>
Message-ID: <20031016110356.GA5037@falcon.midgard.homeip.net>

On Thu, Oct 16, 2003 at 04:43:27AM -0500, Peter Schultz wrote:
> At this point in time it's downright irresponsible not to hide our 
> addresses.
> 
> I've been lurking on this list about a month to get caught up with 
> -current issues.  Friday was both the first mail I sent to the list,
> and the first use of this e-mail address.  The only incoming mail was 
> from the FreeBSD lists I subscribed to.  However, since that fateful 
> e-mail I have been viciously attacked by spammers posing as Microsoft 
> security updaters.  These spams include attachments making them all 
> around 150KB in size.  Maybe others of you have seen them?

I guess you are referring to the W32.Swen worm?  I guess most people
have seen that one by now.

> 
> As far as I can tell, these guys are targeting the FreeBSD lists, 
> exploiting them terribly!  This list's charter states that spam will be 
> blocked.  Please enforce the list charter, with prejudice.

The FreeBSD lists are not targeted specially.
That worm mainly harvests e-mail addresses from newsgroups (and from
files stored on infected computers.)
There are several mail<->news gateways for this list (and other freebsd
lists), so this is probably where it got your mail-address.
Since these gateways are not under the control of FreeBSD.org there
isn't much that can be done about it.
These spams are mainly not sent through the lists so they can't be
blocked there (even though lots and lots of spam is blocked by the
FreeBSD list servers.)

> 
> It would be best if subscribers could just choose to have their address 
> published or not.  I can understand being so dedicated to the cause that 
> you're willing to take on some spam.  Non-subscribers addresses should 
> definitely not be published.
> 
> Sincerely,
> Pete...
> 
> Wilko Bulte wrote:
> >On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote:
> >
> >
> >I fail to see why this is relevant to -current but OK.. I think that
> >the opportunity to do this has long since passed. Just type your name
> >in Google and see what happens..
> >
> >Wilko
> >
> >
> >>Due to increased activity of SPAM harvesters what are our plans to hide 
> >>our addresses from public WWW? I mean all browseable mailing lists, 
> >>FreeBSD site, CVS via WWW, PRs, ports and docs.

Note that there are many web-archives of the mailing lists. Lots of
them are run by other people.  You need to talk to them too.

> >>
> >>As I think, simple <user [at] domain.com> form will be enough to stop 
> >>them.
> >>

-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013 at student.uu.se


From max at love2party.net  Thu Oct 16 12:31:53 2003
From: max at love2party.net (Max Laier)
Date: Thu, 16 Oct 2003 14:31:44 +0200
Subject: hiding e-mail adresses needed badly
In-Reply-To: <20031015112920.GA36404@nagual.pp.ru>
References: <20031015112920.GA36404@nagual.pp.ru>
Message-ID: <892502734.20031016143144@love2party.net>

Hello Andrey,

Wednesday, October 15, 2003, 1:29:21 PM, you wrote:
AC> Due to increased activity of SPAM harvesters what are our plans to hide
AC> our addresses from public WWW? I mean all browseable mailing lists,
AC> FreeBSD site, CVS via WWW, PRs, ports and docs.

AC> As I think, simple <user [at] domain.com> form will be enough to stop
AC> them.

OT: mail/procmail mail/relaydb mail/spamd mail/bmf ... etc. pp.
http://www.benzedrine.cx/relaydb.html

So would you please stop whining and configure your procmail okay.
What you suggest is "Security Through Obscurity", which does not work!

-- 
Best regards,
 Max                            mailto:max at love2party.net
                                ^^^SPAM HERE!!! =)


From green at FreeBSD.org  Thu Oct 16 16:45:51 2003
From: green at FreeBSD.org (Brian F. Feldman)
Date: Thu, 16 Oct 2003 12:45:45 -0400
Subject: hiding e-mail adresses needed badly 
In-Reply-To: Message from des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) 
   of "Wed, 15 Oct 2003 22:10:05 +0200." <xzpn0c28dpe.fsf@dwp.des.no> 
Message-ID: <200310161645.h9GGjj0t016455@green.bikeshed.org>

des at des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) wrote:
> Andrey Chernov <ache at nagual.pp.ru> writes:
> > On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:
> > > And I personally think that by "hiding" the email addresses, you concede
> > > defeat to the spammers.  I don't want to let a bunch of low-life
> > > con-men decide how I can and should use the InterNet.
> > It sounds heroic, but the position alone not helps to stop low-life 
> > con-men's invasion.
> 
> Stop whining and install SpamAssassin.

Seconded.  I get about two spam messages a week that get through to the 
inbox, and the rest picked off by SpamAssassin with a good spamfolder to 
assist it with Bayesian filtering (I don't delete spam, I move it all to the 
spam folder if I see it in my inbox).  Actually, you know what I'd like?  
Absolutely no protection for my address at all.  I don't want it hidden or 
obfuscated and I especially don't want hidden restrictions about who I can 
and can't send e-mail to/receive e-mail from dictated solely by the mail 
server (i.e. can't receive mail from or send to my uncle using AOL... not 
using @FreeBSD.org as my address...)


-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green at FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\



From kris at obsecurity.org  Thu Oct 16 16:59:50 2003
From: kris at obsecurity.org (Kris Kennaway)
Date: Thu, 16 Oct 2003 09:59:46 -0700
Subject: hiding e-mail adresses needed badly
In-Reply-To: <200310161645.h9GGjj0t016455@green.bikeshed.org>
References: <xzpn0c28dpe.fsf@dwp.des.no>
	<200310161645.h9GGjj0t016455@green.bikeshed.org>
Message-ID: <20031016165946.GA71469@rot13.obsecurity.org>

On Thu, Oct 16, 2003 at 12:45:45PM -0400, Brian F. Feldman wrote:
> des at des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) wrote:
> > Andrey Chernov <ache at nagual.pp.ru> writes:
> > > On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:
> > > > And I personally think that by "hiding" the email addresses, you concede
> > > > defeat to the spammers.  I don't want to let a bunch of low-life
> > > > con-men decide how I can and should use the InterNet.
> > > It sounds heroic, but the position alone not helps to stop low-life 
> > > con-men's invasion.
> > 
> > Stop whining and install SpamAssassin.
> 
> Seconded.  I get about two spam messages a week that get through to the 
> inbox, and the rest picked off by SpamAssassin with a good spamfolder to 
> assist it with Bayesian filtering (I don't delete spam, I move it all to the 
> spam folder if I see it in my inbox).  Actually, you know what I'd like?  
> Absolutely no protection for my address at all.  I don't want it hidden or 
> obfuscated and I especially don't want hidden restrictions about who I can 
> and can't send e-mail to/receive e-mail from dictated solely by the mail 
> server (i.e. can't receive mail from or send to my uncle using AOL... not 
> using @FreeBSD.org as my address...)

Since I also have a working spam-filter (and download bandwidth is not
a constraint for me) I'm quite sympathetic to this viewpoint as well.

I highly encourage everyone in need of better spam protection to
install bogofilter - after training, it catches >98% of my spam with 0
false positives in at least the last 6 months.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031016/233ea2d9/attachment.sig>

From tlambert2 at mindspring.com  Thu Oct 16 18:30:49 2003
From: tlambert2 at mindspring.com (Terry Lambert)
Date: Thu, 16 Oct 2003 11:29:36 -0700
Subject: hiding e-mail adresses needed badly
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<20031016124938.354fe903.steve@sohara.org>
Message-ID: <3F8EE390.47F355D3@mindspring.com>

Steve O'Hara-Smith wrote:
> Peter Schultz <pmes at btinet.net> wrote:
> > However, since that fateful
> > e-mail I have been viciously attacked by spammers posing as Microsoft
> > security updaters.  These spams include attachments making them all
> > around 150KB in size.  Maybe others of you have seen them?
> 
>         Certainly have - they're not spammers it's a worm, called Swen.
> It targets an amazing variety of things, including every email address
> it can get hold of. One of my accounts gets about a hundred a day of
> these *still*. If you get infected it filters your inbox and removes
> attempts to reinfect you so that you don't see it at all.

But you still get to pay to download them.

I got so pissed off, I wrote a program to proactively delete them
out of my mailbox at intervals, without downloading them.

Earthlink often sucks in terms of customer service.  If they would
just designate a couple of common markers as "known SPAM", the
problem would have gone away for me, and a couple million other
people forced to use Earthlink ("forced", because no matter where
I go, Earthlink buys up my damn ISP -- no one talks about *that*
monocoluture being a threat).

Another pain in the ass is that people without direct Internet
connections *somewhere* are stuck with POP3 maildrops going over
quota because of these damn things, which is a denial of service
attack (all messages to you bounce as "over quota", and most of
the mailing list software in the world will auto-unsubscribe you
when that happens).  This is probably the biggest threat to the
Internet yet, since communication in general, and email in
particular, is still *the* killer application for the Internet.

This is an inherent flaw in a store-with-quota+pickup-transiently
model, which is what any POP3/IMAP4 forces their users into, and
that means *any* ISP, even ones that give you full time connections,
when they refuse to let you run your own mail server, either by
explicitly disallowing it, or by not providing you a static IP.  A
non-quotaed maildrop would fix it.  The ISP mail server admins
growing a clue and not transiting executable attachments would fix
it.  And ASMTP would fix it (as long as there wasn't a queue quota).

Again, Earthlink is no help, since they transit these damn
things to the maildrop, against their customer's will, and, for
most of their customers, this means propagating the damn things
further.

Can you imagine if someone wrote one of these things to *actively*
target an ISP with a stupid network topology like Earthlink?  You
could drive the company out of business by chasing all their
subscribers away by denying them the ability to receive communications
from almost anyone else on the Internet.  I'm really surprised these
idiots are unwilling to do anything about saving their business model
from extinction.

In any case, my suggestion is that you write a program to delete off
files with certain sizes from a "list" and/or certain content from a
"head", and find a kind soul you trust to not abuse your password,
which would have to be cleartext somewhere (command line or compiled
in), and have the worms deleted out before they become an issue for
you.

-- Terry


From tlambert2 at mindspring.com  Thu Oct 16 18:32:44 2003
From: tlambert2 at mindspring.com (Terry Lambert)
Date: Thu, 16 Oct 2003 11:31:57 -0700
Subject: hiding e-mail adresses needed badly
References: <20031015112920.GA36404@nagual.pp.ru>
	<892502734.20031016143144@love2party.net>
Message-ID: <3F8EE41D.F9E62438@mindspring.com>

Max Laier wrote:
> Wednesday, October 15, 2003, 1:29:21 PM, you wrote:
> AC> Due to increased activity of SPAM harvesters what are our plans to hide
> AC> our addresses from public WWW? I mean all browseable mailing lists,
> AC> FreeBSD site, CVS via WWW, PRs, ports and docs.
> 
> OT: mail/procmail mail/relaydb mail/spamd mail/bmf ... etc. pp.
> http://www.benzedrine.cx/relaydb.html
> 
> So would you please stop whining and configure your procmail okay.
> What you suggest is "Security Through Obscurity", which does not work!

Cluebat:

Neither does your solution, without having a static IP address
and your own SMTP server with a full time broadband connection.

-- Terry


From PeterJeremy at optushome.com.au  Fri Oct 17 07:25:03 2003
From: PeterJeremy at optushome.com.au (Peter Jeremy)
Date: Fri, 17 Oct 2003 17:24:59 +1000
Subject: hiding e-mail adresses needed badly
In-Reply-To: <3F8EE390.47F355D3@mindspring.com>
References: <20031015112920.GA36404@nagual.pp.ru>
	<20031015132551.GA94612@freebie.xs4all.nl>
	<20031016124938.354fe903.steve@sohara.org> <3F8EE390.47F355D3@mindspring.com>
Message-ID: <20031017072459.GB1668@cirb503493.alcatel.com.au>

[This may get duplicated if my outgoing work e-mail gets fixed]

On 2003-Oct-16 11:29:36 -0700, Terry Lambert <tlambert2 at mindspring.com> wrote:
>Earthlink often sucks in terms of customer service.  If they would
>just designate a couple of common markers as "known SPAM", the
>problem would have gone away

There's a fine line between 'blocking a couple of common markers'
and arbitrarily blocking domains, IP addresses and all mails containing
specific words - which some large ISPs do.  What's needed is a filter
system that allows users to control what they receive - not one where
the ISP gets to decide what is/isn't delivered.

When W32.Swen first hit, I was getting "mailbox near quota" messages
if I didn't empty my home mailbox for about 8 hours.  I asked my ISP
when they would be implementing something to let me control what was
delivered into my mailbox and eventually managed to get a "we're
looking into the problem" response.  I started running fetchmail as a
work-around (which stops the quota DOS but does nothing to help my
download bandwidth).  AFAIK, they still haven't done anything.

And Australia's biggest ISP (Telstra BigPond) is currently getting
unfavourable mentions in Parliament and the media because it's e-mail
system can't cope - users are claiming e-mails are being delayed a
week or more, or just aren't arriving.

>people forced to use Earthlink ("forced", because no matter where
>I go, Earthlink buys up my damn ISP -- no one talks about *that*
>monocoluture being a threat).

Mumble years ago, I heard a talk on this phenomenom.  They problem
boils down to ISP interconnect agreements - they generally wind up
meaning the small ISP has to pay the big ISP (or Internet wholesaler)
whatever the big ISP asks because their customers need to exchange
packets with IP addresses "owned" by the big ISP and the big ISP
doesn't have as much incentive to route packets to the smaller ISP.
This is a positive feedback loop with the bigger ISP absorbing all the
smaller ones.

>This is an inherent flaw in a store-with-quota+pickup-transiently
>model, which is what any POP3/IMAP4 forces their users into, and
>that means *any* ISP, even ones that give you full time connections,
>when they refuse to let you run your own mail server, either by
>explicitly disallowing it, or by not providing you a static IP.

Optus Internet (my home ISP) state that they block incoming traffic
to TCP/25 to prevent them being being black-listed for allowing
people to run promiscuous SMTP relays.  This is probably at least
partly true.

>  A non-quotaed maildrop would fix it.

How do you stop the weenies never deleting e-mail so their mailboxes
grow indefinitely?  A better solution would be a soft-quota'd
maildrop.  As long as you get to it every few days you don't get DOS'd
but if you never delete your mail you get bitten.  Of course, from an
ISP perspective, there's the problem of several thousand mailboxes
each receiving several hundred 200KB mails each day - that's an awful
lot of maildrop disk space to have to find in a hurry.

>Can you imagine if someone wrote one of these things to *actively*
>target an ISP with a stupid network topology like Earthlink?

Do you know of any ISPs that do a better job of upstream filtering?

>  You
>could drive the company out of business by chasing all their
>subscribers away by denying them the ability to receive communications
>from almost anyone else on the Internet.  I'm really surprised these
>idiots are unwilling to do anything about saving their business model
>from extinction.

The problem is that it doesn't really hurt the ISP - they (typically)
charge for downlink usage, so they're making more money by not blocking
SPAM.  The customers have to put up with it because they know the
competing ISPs aren't any better.

"Death of USENET predicted ... Film at 11" can probably be updated.

Peter


From bmgirishm at yahoo.com  Fri Oct 17 15:53:18 2003
From: bmgirishm at yahoo.com (bmgirish marigoudar)
Date: Fri, 17 Oct 2003 08:53:17 -0700 (PDT)
Subject: Regarding drivers of Tough connect 10 Base T(LPC2-CTL)
Message-ID: <20031017155317.3335.qmail@web11003.mail.yahoo.com>

Respected sir,
 
 I am having the
 [BUFFALO Tough connect 10 Base-T(LPC2-CTL)]
 Card.
 
 I need the drivers of this card for the OS
 (UNIX) and for Windows nt4.0,
 Could you please let me know from where i can
download
 the drivers..
 
 I hope my request will be considered..
 
 Thanks...
 Gireesh.B.M


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


From sem at ciam.ru  Fri Oct 17 22:21:14 2003
From: sem at ciam.ru (Sergey Matveychuk)
Date: Sat, 18 Oct 2003 02:21:10 +0400
Subject: searching
Message-ID: <3F906B56.8000204@ciam.ru>

Why when I search (http://www.freebsd.org/search/) I've got only one 
page of results everytime? I know they are bigger but I can't get newxt 
page.

-- 
Sem.


From nik at crf-consulting.co.uk  Sat Oct 18 12:50:24 2003
From: nik at crf-consulting.co.uk (Nik Clayton)
Date: Sat, 18 Oct 2003 13:43:46 +0100 (BST)
Subject: docs/58202: handbook doesn't mention kldload'ness of ipfw
Message-ID: <200310181243.h9IChkiG048223@clan.nothing-going-on.org>


>Number:         58202
>Category:       docs
>Synopsis:       handbook doesn't mention kldload'ness of ipfw
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 18 05:50:21 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Nik Clayton
>Release:        FreeBSD 4.8-RC i386
>Organization:
>Environment:
System: FreeBSD clan.nothing-going-on.org 4.8-RC FreeBSD 4.8-RC #3: Fri Mar 28 07:59:28 GMT 2003 nik at clan.nothing-going-on.org:/local/1/usr/src/sys/compile/CLAN i386


>Description:

The Handbook's section on enabling ipfw (10.8.3) doesn't mention it's
kldload'ness, just that a kernel recompile is necessary.  Since rc.conf
will load ipfw.ko on demand, this deserves a mention (along with necessary 
anti-foot shooting incantations to avoid looking yourself out of the box).

>How-To-Repeat:
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


From kensmith at FreeBSD.org  Sat Oct 18 13:25:23 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Sat, 18 Oct 2003 06:25:22 -0700 (PDT)
Subject: docs/58202: handbook doesn't mention kldload'ness of ipfw
Message-ID: <200310181325.h9IDPMT3068841@freefall.freebsd.org>

Synopsis: handbook doesn't mention kldload'ness of ipfw

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Sat Oct 18 06:23:49 PDT 2003
Responsible-Changed-Why: 

I'll take this one, it meshes a little bit with an older PR I was
looking at regarding IPFW in the advanced networking section.


http://www.freebsd.org/cgi/query-pr.cgi?pr=58202


From kensmith at FreeBSD.org  Sat Oct 18 13:30:38 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Sat, 18 Oct 2003 06:30:37 -0700 (PDT)
Subject: docs/55883: advanced-networking/chapter.sgml
Message-ID: <200310181330.h9IDUbI7069277@freefall.freebsd.org>

Synopsis: advanced-networking/chapter.sgml

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Sat Oct 18 06:28:02 PDT 2003
Responsible-Changed-Why: 

I'm going to try and clean up a few places IPFW is described to clean
up mentioning IPFW_DEFAULT_TO_ACCEPT exists and what it's used for.


http://www.freebsd.org/cgi/query-pr.cgi?pr=55883


From simon at FreeBSD.org  Sat Oct 18 14:15:14 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Sat, 18 Oct 2003 07:15:13 -0700 (PDT)
Subject: docs/56902: [patch] articles/fbsd-from-scratch: add/fix sgml
	tags
Message-ID: <200310181415.h9IEFDrI078862@freefall.freebsd.org>

Synopsis: [patch] articles/fbsd-from-scratch: add/fix sgml tags

State-Changed-From-To: open->closed
State-Changed-By: simon
State-Changed-When: Sat Oct 18 07:14:07 PDT 2003
State-Changed-Why: 
Committed with some modifications, mainly to seperate whitespace
changes from content changes.
Thanks for the submission!

http://www.freebsd.org/cgi/query-pr.cgi?pr=56902


From kensmith at cse.Buffalo.EDU  Sat Oct 18 15:12:41 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sat, 18 Oct 2003 11:12:35 -0400
Subject: Results of "Hiding email addresses" discussion
Message-ID: <20031018151235.GA20037@electra.cse.Buffalo.EDU>


[ Just to docs at ... ]

It might be a good idea for us to decide what the outcome of that
hiding email addresses discussion on developers@ (and elsewhere...)
was.  It could have an effect on new work if nothing else.

Do you think it's fair to say we should probably start limiting places
where we put email addresses of people who have not directly "joined
the project"?  Using the example of the mirror system only because I'm
most familiar with it, I have no expectation that my email address
should be hidden away because I have chosen to join the project.  But
I recently went through and removed the email addresses of the cvsup
site maintainers because they're a mixture of people who have joined
the project and people who simply needed a cvsup server for their
own purposes and are willing to let other people use it.

It seemed like the issue of hiding addresses of people who have chosen
to join the project isn't going to get resolved, at least any time
soon - strong views on both ends of the spectrum.

Thoughts?

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From simon at FreeBSD.org  Sat Oct 18 16:12:54 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Sat, 18 Oct 2003 09:12:53 -0700 (PDT)
Subject: docs/57209: [patch] article/mh: add missing docbook tags
Message-ID: <200310181612.h9IGCrn9092300@freefall.freebsd.org>

Synopsis: [patch] article/mh: add missing docbook tags

State-Changed-From-To: open->closed
State-Changed-By: simon
State-Changed-When: Sat Oct 18 09:12:46 PDT 2003
State-Changed-Why: 
Commited, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=57209


From simon at FreeBSD.org  Sat Oct 18 20:53:11 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Sat, 18 Oct 2003 13:53:11 -0700 (PDT)
Subject: misc/36154: Getting USB mouse to work: usbd and moused conflict
Message-ID: <200310182053.h9IKrBaf018710@freefall.freebsd.org>

Synopsis: Getting USB mouse to work: usbd and moused conflict

Responsible-Changed-From-To: freebsd-doc->simon
Responsible-Changed-By: simon
Responsible-Changed-When: Sat Oct 18 13:53:00 PDT 2003
Responsible-Changed-Why: 
I'm looking into this one.

http://www.freebsd.org/cgi/query-pr.cgi?pr=36154


From davmo024 at student.liu.se  Sat Oct 18 22:13:52 2003
From: davmo024 at student.liu.se (David Montag)
Date: Sun, 19 Oct 2003 00:13:47 +0200
Subject: New language
Message-ID: <9e5e389e28c7.9e28c79e5e38@liu.se>

I've started the FreeBSD Swedish Documentation Translation Project. Official website for now is http://freebsd.movnet.org. Appreciate help with this.

/David Montag


From bmah at freebsd.org  Sun Oct 19 06:13:15 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Sat, 18 Oct 2003 23:13:10 -0700
Subject: HEADS-UP:  doc/ tree slushie
Message-ID: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>

Let me start by apologizing for the short notice.

Tagging of doc/ for 4.9-RELEASE will happen within the next few days
(probably 20 or 21 October).  Given this, we'd like to slow the rate of
change to doc/en_US.ISO8859-1 in order to give translation teams time 
to make any last-minute catch-ups that they need to do.

This doesn't mean "suspend all work", but it's probably a good idea to
postpone large structural changes (i.e. reorganizing a document) for a
little while.  Also, we need to be extra-careful to keep doc/ in a
buildable state for the next few days.

I'll give a more precise date and time for doc/ tagging once I've had a 
chance to discuss this with some of the other re@ folks.  My best guess 
would be late afternoon (GMT-0700) on 20 September.

Thanks for your help, and once again, my apologies for the short notice 
and any inconvenience this may cause.

Bruce.
(speaking more-or-less for re@)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 223 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031018/32667b0c/attachment.sig>

From fox at vader.aacc.cc.md.us  Sun Oct 19 18:08:26 2003
From: fox at vader.aacc.cc.md.us (Michel Lavondes)
Date: Sun, 19 Oct 2003 14:08:14 -0400 (EDT)
Subject: Online 5-current release notes: s/dev_db/dev_mkdb/ throughout
Message-ID: <Pine.LNX.4.44.0310191344280.11062-100000@vader.aacc.edu>

The following URLs use dev_db to refer to what I suspect is actually 
dev_mkdb (unless it was renamed between 4.x and 5.x). Context:

   The dev_db utility is unnecessary due to the mandatory presence of
   devfs, and has been removed.

(Sorry, I know the HTML docs are generated from other files, but I don't 
have 5-current docs installed locally, so I can't grep them, and I thought 
that accurate, possibly incomplete information was better than possibly 
misleading guesses from the RCS/CVS data in the HTML docs. Also, I 
assumed, perhaps incorrectly, that this wasn't specific to the web-based 
docs.)

http://www.freebsd.org/relnotes/CURRENT/relnotes/i386/article.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/i386/new.html#USERLAND
http://www.freebsd.org/relnotes/CURRENT/relnotes/pc98/article.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/pc98/new.html#USERLAND
http://www.freebsd.org/relnotes/CURRENT/relnotes/alpha/article.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/alpha/new.html#USERLAND
http://www.freebsd.org/relnotes/CURRENT/relnotes/sparc64/index.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/sparc64/new.html#USERLAND
http://www.freebsd.org/relnotes/CURRENT/relnotes/ia64/article.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/ia64/new.html#USERLAND
http://www.freebsd.org/relnotes/CURRENT/relnotes/amd64/article.html
http://www.freebsd.org/relnotes/CURRENT/relnotes/amd64/new.html#USERLAND

-- 
Remember: i before e, except on Unix machines.


From cheerawathana at yahoo.com  Thu Oct  2 02:34:53 2003
From: cheerawathana at yahoo.com (cheerawat suriyawongpaisarn)
Date: Thu, 02 Oct 2003 02:34:53 -0000
Subject: how to subscript  freebsd document project 
Message-ID: <20031002023452.62075.qmail@web10108.mail.yahoo.com>

Dear Sir 
My name is Tawaee Moonton. I am Thai . I am
interesting in FreeBSD project. I try to use it for 3
years but it very difficult to use because no document
in Thai language. I am not good at English but I can
do it with myself try and more try. Now I can use
FreeBSD for my company with more powerful of it. Why
do I writing this letter? The reason is I want to
translate ?The FreeBSD handbook? from English to Thai.
When I was newbie in FreeBSD it very hard to
understand if I have thai document it will be use more
less time to do, to understand it. And my goal is
making a document for Thai FreeBSD newbie. I think it
will be easier than me at the fist time that I trying
to use it
I wish that I would get a welcome from The FreeBSD
document project. Now I am free.  I resign from my
work. I will have more time to do this project
Best regard
Tawee Moonton


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


From ache at nagual.pp.ru  Wed Oct 15 20:34:33 2003
From: ache at nagual.pp.ru (Andrey Chernov)
Date: Thu, 16 Oct 2003 00:34:28 +0400
Subject: hiding e-mail adresses needed badly
In-Reply-To: <xzpn0c28dpe.fsf@dwp.des.no>
References: <20031015133634.GA37556@nagual.pp.ru>
	<43618.1066226536@critter.freebsd.dk> <20031015152102.GB38522@nagual.pp.ru>
	<xzpn0c28dpe.fsf@dwp.des.no>
Message-ID: <20031015203428.GA42399@nagual.pp.ru>

On Wed, Oct 15, 2003 at 22:10:05 +0200, Dag-Erling Sm?rgrav wrote:
> Andrey Chernov <ache at nagual.pp.ru> writes:
> > On Wed, Oct 15, 2003 at 16:02:16 +0200, Poul-Henning Kamp wrote:
> > > And I personally think that by "hiding" the email addresses, you concede
> > > defeat to the spammers.  I don't want to let a bunch of low-life
> > > con-men decide how I can and should use the InterNet.
> > It sounds heroic, but the position alone not helps to stop low-life 
> > con-men's invasion.
> 
> Stop whining and install SpamAssassin.

I use 4 filters combined already + spam back report tools.  This includes
bogofilter which gives better results for me than SpamAssasin. All that is
not enough.

-- 
Andrey Chernov | http://ache.pp.ru/


From bmah at freebsd.org  Mon Oct 20 04:14:21 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Sun, 19 Oct 2003 21:14:18 -0700
Subject: HEADS-UP: doc/ tree slushie 
In-Reply-To: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org> 
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
Message-ID: <200310200414.h9K4EInB049618@intruder.kitchenlab.org>

If memory serves me right, Bruce A. Mah wrote:

> I'll give a more precise date and time for doc/ tagging once I've had a 
> chance to discuss this with some of the other re@ folks.  My best guess 
> would be late afternoon (GMT-0700) on 20 September.

Barring any complications or major objections, I'll tag the doc/ tree 
around 1600, 20 September (PST).  (That's 2300, 20 September UTC.)

Thanks for bearing with us...

Bruce.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 223 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031019/efb7af87/attachment.sig>

From anderson at centtech.com  Mon Oct 20 05:03:14 2003
From: anderson at centtech.com (Eric Anderson)
Date: Mon, 20 Oct 2003 00:02:54 -0500
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <200310200414.h9K4EInB049618@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
Message-ID: <3F936C7E.9020904@centtech.com>

Bruce A. Mah wrote:

>If memory serves me right, Bruce A. Mah wrote:
>
>  
>
>>I'll give a more precise date and time for doc/ tagging once I've had a 
>>chance to discuss this with some of the other re@ folks.  My best guess 
>>would be late afternoon (GMT-0700) on 20 September.
>>    
>>
>
>Barring any complications or major objections, I'll tag the doc/ tree 
>around 1600, 20 September (PST).  (That's 2300, 20 September UTC.)
>
>Thanks for bearing with us...
>

Must be a rough night - I think you mean October.. :)

Eric

-- 
------------------------------------------------------------------
Eric Anderson	   Systems Administrator      Centaur Technology
All generalizations are false, including this one.
------------------------------------------------------------------



From kgilpin_uk at yahoo.co.uk  Mon Oct 20 05:14:36 2003
From: kgilpin_uk at yahoo.co.uk (=?iso-8859-1?q?Kevin?=)
Date: Mon, 20 Oct 2003 06:14:35 +0100 (BST)
Subject: Linux users coming to FreeBSD 
Message-ID: <20031020051435.79555.qmail@web86203.mail.ukl.yahoo.com>

Hi,

Look at your website.  I saw you are looking at people to write about
there move from Linux to BSD.  Are you still looking for people to help
with this project?

Kind regards,

Kevin Gilpin

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk


From durandeau at ams-avia.com  Mon Oct 20 12:08:28 2003
From: durandeau at ams-avia.com (Durandeau Jerome)
Date: Mon, 20 Oct 2003 14:08:20 +0200
Subject: Out of Office AutoReply: Happy Allhallowmas
Message-ID: <1F4AF51DB71769409031AAC596D98C89170563@srzrhdc-002.datacair.com>

Out of office until further notice. 
Address your messages to : cdg at ams-avia.com


From mail at agorainstitute.com  Mon Oct 20 12:51:45 2003
From: mail at agorainstitute.com (Agora Institute)
Date: Mon, 20 Oct 03 08:51:06 -0400
Subject: I have the perfect Coaching & Training directory for your business.
Message-ID: <B0017369538@mc1app2.expresstech.net>

In fact, I founded this directory for the same reasons which you've probably found frustrating-a lack of internet traffic.  We all know that when we're not on one of the top three or four search engine pages, we're out of the loop.

We noticed a few months ago that the search engines are moving away from keywords and metatags as a source of indexing.  We wondered what they knew that we didn't!  

After we studied the drift of the big engines, we came up with a two-pronged solution for anyone who wants more traffic to their site:
1)	Netword
2)	A Business-specific Directory

Netword is the future of the Internet when it comes to global and regional searches.  The good news is that we've bought the Networds which are exclusive to  your industry to build a giant Directory, with specific sub-categories, so that you are at the Top of your Business category, rather than buried on page 50.

The other good news is that Netword is just now reaching its exponential growth phase
this means that you're in a position to guarantee your future Placement on Internet searches which pertain to your industry-i.e. at the Top of Your Category in your Business Domain as Networds propagate globally throughout the Internet universe.

Take a look at our Directory at http://www.agorainstitute.com  

If you like what you see, either check the Advertise Here page (button on the left menu) or send us an e-mail via the Contact Us page on the Directory site.

You'll be guaranteeing your placement on an Industry-exclusive directory that is simply going to continue growing in the future.

Regards,

J Hook
Director:  Gateway for Strategic Performance and Growth 

To be removed from our list, please reply with "remove " as the subject line.



From www at FreeBSD.org  Mon Oct 20 12:52:21 2003
From: www at FreeBSD.org (WWW pseudo-user)
Date: Mon, 20 Oct 2003 05:52:20 -0700 (PDT)
Subject: FreeBSD web build failed on freefall.freebsd.org
Message-ID: <200310201252.h9KCqK9T063702@freefall.freebsd.org>

install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
===> ../es/doc/books/faq
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
===> ../es/doc/books
===> ../es/doc/books/faq
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
===> ../es/doc/books/faq
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /c/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
/c/www/build/www/es/doc/es -> /c/www/build/www/es/doc/es_ES.ISO8859-1
===> ../ru
(cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/data/ru/FAQ all)
make: don't know how to make security/advisories.xml. Stop
*** Error code 2

Stop in /c/www/build/www/en.
     1779.29 real      1097.34 user        62.71 sys


From ceri at FreeBSD.org  Mon Oct 20 13:59:38 2003
From: ceri at FreeBSD.org (Ceri Davies)
Date: Mon, 20 Oct 2003 14:59:33 +0100
Subject: FreeBSD web build failed on freefall.freebsd.org
In-Reply-To: <200310201252.h9KCqK9T063702@freefall.freebsd.org>
References: <200310201252.h9KCqK9T063702@freefall.freebsd.org>
Message-ID: <20031020135933.GC3708@submonkey.net>

On Mon, Oct 20, 2003 at 05:52:20AM -0700, WWW pseudo-user wrote:

> ===> ../ru
> (cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/data/ru/FAQ all)
> make: don't know how to make security/advisories.xml. Stop
> *** Error code 2
> 
> Stop in /c/www/build/www/en.
>      1779.29 real      1097.34 user        62.71 sys

Wow, this is ugly, but it fixes the build.

Ceri

-- 
-------------- next part --------------
Index: www/ru/Makefile
===================================================================
RCS file: /home/ncvs/www/ru/Makefile,v
retrieving revision 1.25
diff -u -r1.25 Makefile
--- www/ru/Makefile	16 Oct 2003 17:57:44 -0000	1.25
+++ www/ru/Makefile	20 Oct 2003 13:57:43 -0000
@@ -87,6 +87,9 @@
 DATA+=		index.html
 CLEANFILES+=	index.html
 
+security/advisories.xml:
+	(cd security; ${MAKE} advisories.xml)
+
 index.html: index.xsl news/news.xml news/press.xml includes.xsl news/includes.xsl security/advisories.xml
 	${XSLTPROC} ${XSLTPROCOPTS} -o ${.TARGET} \
 		${.CURDIR}/index.xsl ${.CURDIR}/news/news.xml
Index: www/ru/security/Makefile
===================================================================
RCS file: /home/ncvs/www/ru/security/Makefile,v
retrieving revision 1.4
diff -u -r1.4 Makefile
--- www/ru/security/Makefile	20 Oct 2003 11:23:44 -0000	1.4
+++ www/ru/security/Makefile	20 Oct 2003 13:55:23 -0000
@@ -19,10 +19,13 @@
  
 .include "${WEB_PREFIX}/share/mk/web.site.mk"
 
-CLEANFILES+= advisories.html.inc
+CLEANFILES+= advisories.html.inc advisories.xml
 
 security.html: advisories.html.inc
 
-advisories.html.inc: mkindex.xsl ../../en/security/advisories.xml
+advisories.xml:
+	${CP} ../../en/security/advisories.xml advisories.xml
+
+advisories.html.inc: advisories.xml mkindex.xsl
 	${XSLTPROC} ${XSLTPROCOPTS} -o ${.TARGET} \
-		${.CURDIR}/mkindex.xsl ${.CURDIR}/../../en/security/advisories.xml
+		${.CURDIR}/mkindex.xsl advisories.xml
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/c170479c/attachment.sig>

From hrs at eos.ocn.ne.jp  Mon Oct 20 14:35:10 2003
From: hrs at eos.ocn.ne.jp (Hiroki Sato)
Date: Mon, 20 Oct 2003 23:31:09 +0900 (JST)
Subject: FreeBSD web build failed on freefall.freebsd.org
In-Reply-To: <20031020135933.GC3708@submonkey.net>
References: <200310201252.h9KCqK9T063702@freefall.freebsd.org>
	<20031020135933.GC3708@submonkey.net>
Message-ID: <20031020.233109.89039796.hrs@eos.ocn.ne.jp>

Ceri Davies <ceri at freebsd.org> wrote
  in <20031020135933.GC3708 at submonkey.net>:

ceri> Wow, this is ugly, but it fixes the build.

 No, the cause is that index.xsl still uses security/advisories.xml.
 The attached patch should fix the build.

 BTW, I think I will move advisories.xml to www/share, a language
 independent place.  Sorry for confusing, but please check carefully
 if www/ tree can be built.

-- 
| Hiroki SATO
-------------- next part --------------
Index: index.xsl
===================================================================
RCS file: /home/ncvs/www/ru/index.xsl,v
retrieving revision 1.7
diff -d -u -I\$FreeBSD:.*\$ -I\$NetBSD:.*\$ -I\$OpenBSD:.*\$ -I\$Id:.*\$ -I\$hrs:.*\$ -r1.7 index.xsl
--- index.xsl	14 Oct 2003 08:48:06 -0000	1.7
+++ index.xsl	20 Oct 2003 14:19:13 -0000
@@ -483,16 +483,16 @@
                            <font size="-1">
                              ????????? ??????????:
                              <xsl:value-of
-                               select="document('security/advisories.xml')/descendant::month[position() = 1]/name"/>
+                               select="document('../en/security/advisories.xml')/descendant::month[position() = 1]/name"/>
                              <xsl:text> </xsl:text>
                              <xsl:value-of
-                               select="document('security/advisories.xml')/descendant::day[position() = 1]/name"/>
+                               select="document('../en/security/advisories.xml')/descendant::day[position() = 1]/name"/>
                              <xsl:text>, </xsl:text>
                              <xsl:value-of
-                               select="document('security/advisories.xml')/descendant::year[position() = 1]/name"/>
+                               select="document('../en/security/advisories.xml')/descendant::year[position() = 1]/name"/>
                              <br/>
                              <!-- Pull in the 10 most recent security advisories -->
-                             <xsl:for-each select="document('security/advisories.xml')/descendant::advisory[position() &lt; 10]">
+                             <xsl:for-each select="document('../en/security/advisories.xml')/descendant::advisory[position() &lt; 10]">
                                &#183; <a>
                                  <xsl:attribute name="href">ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/<xsl:value-of select="name"/>.asc</xsl:attribute>
                                  <xsl:value-of select="name"/>
Index: Makefile
===================================================================
RCS file: /home/ncvs/www/ru/Makefile,v
retrieving revision 1.25
diff -d -u -I\$FreeBSD:.*\$ -I\$NetBSD:.*\$ -I\$OpenBSD:.*\$ -I\$Id:.*\$ -I\$hrs:.*\$ -r1.25 Makefile
--- Makefile	16 Oct 2003 17:57:44 -0000	1.25
+++ Makefile	20 Oct 2003 14:19:37 -0000
@@ -87,7 +87,7 @@
 DATA+=		index.html
 CLEANFILES+=	index.html
 
-index.html: index.xsl news/news.xml news/press.xml includes.xsl news/includes.xsl security/advisories.xml
+index.html: index.xsl news/news.xml news/press.xml includes.xsl news/includes.xsl ../en/security/advisories.xml
 	${XSLTPROC} ${XSLTPROCOPTS} -o ${.TARGET} \
 		${.CURDIR}/index.xsl ${.CURDIR}/news/news.xml
 .if !defined(NO_TIDY)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/5e8199b4/attachment.sig>

From ceri at FreeBSD.org  Mon Oct 20 15:00:56 2003
From: ceri at FreeBSD.org (Ceri Davies)
Date: Mon, 20 Oct 2003 16:00:45 +0100
Subject: FreeBSD web build failed on freefall.freebsd.org
In-Reply-To: <20031020.233109.89039796.hrs@eos.ocn.ne.jp>
References: <200310201252.h9KCqK9T063702@freefall.freebsd.org>
	<20031020135933.GC3708@submonkey.net>
	<20031020.233109.89039796.hrs@eos.ocn.ne.jp>
Message-ID: <20031020150045.GD3708@submonkey.net>

On Mon, Oct 20, 2003 at 11:31:09PM +0900, Hiroki Sato wrote:
> Ceri Davies <ceri at freebsd.org> wrote
>   in <20031020135933.GC3708 at submonkey.net>:
> 
> ceri> Wow, this is ugly, but it fixes the build.
> 
>  No, the cause is that index.xsl still uses security/advisories.xml.
>  The attached patch should fix the build.

The end result is the same, so the below is fine with me.

>  BTW, I think I will move advisories.xml to www/share, a language
>  independent place.  Sorry for confusing, but please check carefully
>  if www/ tree can be built.

Would it not also be useful/prudent to have the path to it in an
xsl:variable?  The diff to index.xsl is much larger than it deserves to be.

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/730fc888/attachment.sig>

From bmah at freebsd.org  Mon Oct 20 15:12:13 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 08:12:09 -0700
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <3F936C7E.9020904@centtech.com>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
Message-ID: <20031020151209.GA55608@intruder.kitchenlab.org>

If memory serves me right, Eric Anderson wrote:
> Bruce A. Mah wrote:

[snip]

> >Barring any complications or major objections, I'll tag the doc/ tree 
> >around 1600, 20 September (PST).  (That's 2300, 20 September UTC.)
> >
> >Thanks for bearing with us...
> >
> 
> Must be a rough night - I think you mean October.. :)

Grrmph.  Yes to both counts.  :-)

I intend to tag doc/ about eight hours from now.

Thanks!

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/058fa67d/attachment.sig>

From hrs at eos.ocn.ne.jp  Mon Oct 20 15:16:09 2003
From: hrs at eos.ocn.ne.jp (Hiroki Sato)
Date: Tue, 21 Oct 2003 00:13:34 +0900 (JST)
Subject: FreeBSD web build failed on freefall.freebsd.org
In-Reply-To: <20031020150045.GD3708@submonkey.net>
References: <20031020135933.GC3708@submonkey.net>
	<20031020.233109.89039796.hrs@eos.ocn.ne.jp>
	<20031020150045.GD3708@submonkey.net>
Message-ID: <20031021.001334.34764842.hrs@eos.ocn.ne.jp>

Ceri Davies <ceri at FreeBSD.org> wrote
  in <20031020150045.GD3708 at submonkey.net>:

ceri> >  BTW, I think I will move advisories.xml to www/share, a language
ceri> >  independent place.  Sorry for confusing, but please check carefully
ceri> >  if www/ tree can be built.
ceri> 
ceri> Would it not also be useful/prudent to have the path to it in an
ceri> xsl:variable?  The diff to index.xsl is much larger than it deserves to be.

 Yes, I agree with this.  I am planning to add such a variable definition
 as the location is moved.  Thank you for the suggestion!

-- 
| Hiroki SATO
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031021/40620d17/attachment.sig>

From bmah at freebsd.org  Mon Oct 20 15:19:56 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 08:19:52 -0700
Subject: Online 5-current release notes: s/dev_db/dev_mkdb/ throughout
In-Reply-To: <Pine.LNX.4.44.0310191344280.11062-100000@vader.aacc.edu>
References: <Pine.LNX.4.44.0310191344280.11062-100000@vader.aacc.edu>
Message-ID: <20031020151952.GA55657@intruder.kitchenlab.org>

If memory serves me right, Michel Lavondes wrote:
> The following URLs use dev_db to refer to what I suspect is actually 
> dev_mkdb (unless it was renamed between 4.x and 5.x). Context:
> 
>    The dev_db utility is unnecessary due to the mandatory presence of
>    devfs, and has been removed.

You're quite right (as far as I know).  I've fixed this, although it
might take a day or so for a Web site rebuild to pick up the change.
Thanks for pointing this out!

> (Sorry, I know the HTML docs are generated from other files, but I don't 
> have 5-current docs installed locally, so I can't grep them, and I thought 
> that accurate, possibly incomplete information was better than possibly 
> misleading guesses from the RCS/CVS data in the HTML docs. Also, I 
> assumed, perhaps incorrectly, that this wasn't specific to the web-based 
> docs.)

You're right...all versions of the release notes (whether they're
displayed on the Web site, my snapshot page, or on the release media)
are generated from a single set of SGML files.

Thanks again!

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/49fa8f30/attachment.sig>

From ceri at FreeBSD.org  Mon Oct 20 15:29:48 2003
From: ceri at FreeBSD.org (Ceri Davies)
Date: Mon, 20 Oct 2003 16:29:39 +0100
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020151209.GA55608@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
Message-ID: <20031020152939.GE3708@submonkey.net>

On Mon, Oct 20, 2003 at 08:12:09AM -0700, Bruce A. Mah wrote:
> If memory serves me right, Eric Anderson wrote:
> > Bruce A. Mah wrote:
> 
> [snip]
> 
> > >Barring any complications or major objections, I'll tag the doc/ tree 
> > >around 1600, 20 September (PST).  (That's 2300, 20 September UTC.)
> > >
> > >Thanks for bearing with us...
> > >
> > 
> > Must be a rough night - I think you mean October.. :)
> 
> Grrmph.  Yes to both counts.  :-)
> 
> I intend to tag doc/ about eight hours from now.

Could I throw out the idea of committing the attached diff before that
happens?  I know that we normally do this after doc/ has been tagged,
but that has always seemed strange to me, as the documentation tagged
as 4.9-RELEASE doesn't contain any references to it.

Of course, the downside is that the website will reflect things that
don't exist yet.

Just an idea,

Ceri

-- 
-------------- next part --------------
Index: en_US.ISO8859-1/articles/hubs/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/hubs/article.sgml,v
retrieving revision 1.36
diff -u -r1.36 article.sgml
--- en_US.ISO8859-1/articles/hubs/article.sgml	14 Aug 2003 19:54:05 -0000	1.36
+++ en_US.ISO8859-1/articles/hubs/article.sgml	20 Oct 2003 15:17:52 -0000
@@ -79,7 +79,7 @@
         complete. The CVS repository and the web pages should
         always be mirrored completely. Also note that the
         numbers stated here are reflecting the current
-        state (at 4.8-RELEASE/5.1-RELEASE). Further development and
+        state (at 4.9-RELEASE/5.1-RELEASE). Further development and
         releases will only increase the required amount.
         Also make sure to keep some (ca. 10-20%) extra space
         around just to be sure.
Index: en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v
retrieving revision 1.326
diff -u -r1.326 chapter.sgml
--- en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml	10 Oct 2003 19:54:31 -0000	1.326
+++ en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml	20 Oct 2003 15:21:35 -0000
@@ -4292,6 +4292,15 @@
       </varlistentry>
 
       <varlistentry>
+	<term>RELENG_4_9</term>
+
+	<listitem>
+	  <para>The release branch for FreeBSD-4.9, used only 
+	    for security advisories and other seriously critical fixes.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
 	<term>RELENG_4_8</term>
 
 	<listitem>
@@ -4380,6 +4389,14 @@
 
 	<listitem>
 	  <para>FreeBSD 5.1</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>RELENG_4_9_0_RELEASE</term>
+
+	<listitem>
+	  <para>FreeBSD 4.9</para>
 	</listitem>
       </varlistentry>
 
Index: en_US.ISO8859-1/books/porters-handbook/book.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
retrieving revision 1.334
diff -u -r1.334 book.sgml
--- en_US.ISO8859-1/books/porters-handbook/book.sgml	17 Oct 2003 17:33:38 -0000	1.334
+++ en_US.ISO8859-1/books/porters-handbook/book.sgml	20 Oct 2003 15:22:14 -0000
@@ -5169,6 +5169,11 @@
 		  </row>
 
 		  <row>
+		    <entry>4.9-RELEASE</entry>
+		    <entry>490000</entry>
+		  </row>
+
+		  <row>
 		    <entry>5.0-CURRENT</entry>
 		    <entry>500000</entry>
 		  </row>
Index: share/sgml/freebsd.ent
===================================================================
RCS file: /home/ncvs/doc/share/sgml/freebsd.ent,v
retrieving revision 1.37
diff -u -r1.37 freebsd.ent
--- share/sgml/freebsd.ent	14 Sep 2003 21:21:12 -0000	1.37
+++ share/sgml/freebsd.ent	20 Oct 2003 15:22:35 -0000
@@ -30,8 +30,8 @@
 <!ENTITY rel.current.errata 'http://www.FreeBSD.org/releases/&rel.current;R/errata.html'>
 
 <!-- Entities for multiple "latest" versions of FreeBSD -->
-<!ENTITY rel2.current CDATA "4.8">
-<!ENTITY rel2.current.date CDATA "March 2003">
+<!ENTITY rel2.current CDATA "4.9">
+<!ENTITY rel2.current.date CDATA "October 2003">
 <!ENTITY rel2.current.notes 'http://www.FreeBSD.org/releases/&rel2.current;R/notes.html'>
 <!ENTITY rel2.current.hardware 'http://www.FreeBSD.org/releases/&rel2.current;R/hardware.html'>
 <!ENTITY rel2.current.errata 'http://www.FreeBSD.org/releases/&rel2.current;R/errata.html'>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/54ab328b/attachment.sig>

From bmah at FreeBSD.org  Mon Oct 20 16:16:12 2003
From: bmah at FreeBSD.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 09:16:06 -0700
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020152939.GE3708@submonkey.net>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
Message-ID: <20031020161606.GA56817@intruder.kitchenlab.org>

If memory serves me right, Ceri Davies wrote:

> Could I throw out the idea of committing the attached diff before that
> happens?  I know that we normally do this after doc/ has been tagged,
> but that has always seemed strange to me, as the documentation tagged
> as 4.9-RELEASE doesn't contain any references to it.
> 
> Of course, the downside is that the website will reflect things that
> don't exist yet.

Well, the way I usually like to do this is to tag first (with the doc/
tree in a usable state), then change certain files that have version
numbers in them, and then slide the tags on those files.  As you
correctly implied, it doesn't always work that way.  :-)

The benefit is that we reduce (OK, just slightly) the amount of time
that the doc tree displayed on the Web site reflects things that don't
exist yet.  On the other hand, I'm not opposed to trying it your way,
especially since we should be branching and going to final builds soon
anyways.  Lemme think about this a bit...my morning (.ca.us time)
caffeine hasn't taken effect yet.

> Index: en_US.ISO8859-1/articles/hubs/article.sgml
> ===================================================================
> RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/hubs/article.sgml,v
> retrieving revision 1.36
> diff -u -r1.36 article.sgml
> --- en_US.ISO8859-1/articles/hubs/article.sgml	14 Aug 2003 19:54:05 -0000	1.36
> +++ en_US.ISO8859-1/articles/hubs/article.sgml	20 Oct 2003 15:17:52 -0000
> @@ -79,7 +79,7 @@
>          complete. The CVS repository and the web pages should
>          always be mirrored completely. Also note that the
>          numbers stated here are reflecting the current
> -        state (at 4.8-RELEASE/5.1-RELEASE). Further development and
> +        state (at 4.9-RELEASE/5.1-RELEASE). Further development and
>          releases will only increase the required amount.
>          Also make sure to keep some (ca. 10-20%) extra space
>          around just to be sure.

Yeeek, what are those hard-coded version numbers doing in there?!?
Actually...are there some other related constants (i.e. amount of disk
space) that might need to be changed or otherwise track a version
number?  I haven't read the hubs article lately.

Thanks!

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/c83e20fe/attachment.sig>

From kensmith at cse.Buffalo.EDU  Mon Oct 20 16:31:21 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 20 Oct 2003 12:31:17 -0400
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020161606.GA56817@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
Message-ID: <20031020163117.GB1370@electra.cse.Buffalo.EDU>

On Mon, Oct 20, 2003 at 09:16:06AM -0700, Bruce A. Mah wrote:

> Yeeek, what are those hard-coded version numbers doing in there?!?
> Actually...are there some other related constants (i.e. amount of disk
> space) that might need to be changed or otherwise track a version
> number?  I haven't read the hubs article lately.

The numbers were adjusted to current reality 2 or 3 months ago.  That
said the hubs article does need more work.  We were trying to come to
something resembling consensus on what being an Official Mirror Site
meant but that discussion was going on at the same time we were
planning changes to the content of the site (dropping branches/) so
it seemed like it would be best to procrastinate a bit on trying to
finish the discussion.  I'm not tracking more information about the
sites and started to incorporate some of it into the article as well,
which effects some of what's there (e.g. I added what access methods
are available to the list of FTP mirror sites which makes the section
about rsync hosts possibly defunct, but there was also http added
as an access method and keeping separate lists of hosts for all three
access methods seems a bit much...).

The disk space numbers can't *really* be linked straight to an OS
version because there is so much other stuff in the site.  The
size of the ports/distfiles and to some extent the -current package
sets fluctuate based on non-release-issues.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From bugmaster at freebsd.org  Mon Oct 20 18:00:39 2003
From: bugmaster at freebsd.org (FreeBSD bugmaster)
Date: Mon, 20 Oct 2003 11:00:35 -0700 (PDT)
Subject: Current unassigned doc problem reports
Message-ID: <200310201800.h9KI0Zbg097924@freefall.freebsd.org>

Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

Bugs can be in one of several states:

o - open
     A problem report has been submitted, no sanity checking performed.

a - analyzed
     The problem is understood and a solution is being sought.

f - feedback
     Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
     A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

s - suspended
     The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
     A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
a [2001/10/31] i386/31671  doc         4.4 installer hangs at " Mounting root fr

1 problem total.

Serious problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
s [1999/10/04] i386/14135  doc         lpt1 nolonger exists after 3.2-RELEASE
s [2000/07/18] docs/20028  doc         ASCII docs should reflect <emphasis> tags
o [2001/05/23] docs/27605  doc         Cross-document references (<olink>)
o [2002/01/15] docs/33929  doc         Section 15.15 of the FreeBSD Porter's Han
s [2002/03/08] docs/35678  doc         docproj Makefiles for web are broken for 
o [2002/03/21] docs/36168  doc         -pthread/_THREAD_SAFE docs missing in gcc
o [2002/09/13] docs/42762  doc         ppp.8 has no description of $env and ~use
o [2002/11/14] docs/45303  doc         Bug in PDF DocBook rendering
f [2003/02/19] docs/48472  doc         Documentation unreadable.
o [2003/09/15] docs/56894  doc         umass man page: "mount -t msdos" instead 

10 problems total.

Non-critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
o [2001/02/01] docs/24786  doc         missing FILES descriptions in sa(4)
o [2001/04/29] docs/26943  doc         [patch] description of :C modifier is mis
o [2001/07/26] docs/29245  doc         top(1) manpage doesn't understand SMP
a [2001/08/23] docs/30008  doc         This document should be translated, comme
o [2001/09/27] docs/30873  doc         ``ip'' man page does not specify byte ord
o [2001/10/07] docs/31109  doc         replace gif images w/ png ones due to pat
o [2001/11/15] docs/32020  doc         loader.8 manpage missing tunables
o [2002/01/05] docs/33589  doc         Patch to doc.docbook.mk to post process .
o [2002/01/13] docs/33852  doc         split(1) man page implies that input file
o [2002/01/14] docs/33877  doc         Documentet behaviour of SF_flags for non-
o [2002/02/15] bin/34955   doc         [PATCH] ps(1) is out of touch with realit
a [2002/02/16] docs/35011  doc         There are no commands called "diskless" o
o [2002/02/22] docs/35222  doc         mailing list archive URL regexp suboptima
o [2002/03/06] docs/35602  doc         dump(8)/restore(8) pages don't explain "a
o [2002/03/06] docs/35607  doc         dump(1) page needs discussion of scary er
o [2002/03/06] docs/35608  doc         mt(1) page uses "setmark" without explana
o [2002/03/06] docs/35609  doc         mt(1) page needs explanation of "long era
o [2002/03/06] docs/35612  doc         ps(1) page "state" description doesn't me
o [2002/03/07] docs/35642  doc         lo(4) page maybe should document optional
o [2002/03/07] docs/35644  doc         lo(4) page presumes familiarity with prin
o [2002/03/07] docs/35646  doc         cp(1) page needs a "Bugs" section.
o [2002/03/07] docs/35647  doc         www; combine query-by-number and multi-fi
o [2002/03/07] docs/35648  doc         rc.conf; add note about "flags" to both f
o [2002/03/08] docs/35686  doc         blackhole(4) page seems to contradict its
o [2002/03/08] docs/35687  doc         /etc/nsmb.conf missing mention of readers
o [2002/03/09] docs/35711  doc         the "gnats page" should move to its own s
o [2002/03/10] docs/35732  doc         adduser(8) page has obsolete reference an
o [2002/03/15] docs/35943  doc         at(1) config files are misplaced in /var/
o [2002/03/15] docs/35953  doc         hosts.equiv(5) manual is confusing or wro
o [2002/03/28] docs/36432  doc         Proposal for doc/share/mk: make folded bo
o [2002/03/28] docs/36449  doc         symlink(7) manual doesn't mention trailin
o [2002/05/03] docs/37719  doc         Detail VOP_ naming in a relevant man-page
s [2002/05/07] docs/37843  doc         manual for pthread_setschedparam is wrong
o [2002/05/18] docs/38225  doc         change "CDROM" to "CD-ROM"
o [2002/05/25] docs/38556  doc         EPS file of beastie, as addition to exist
o [2002/05/27] docs/38620  doc         Committers Guide and CVS
o [2002/05/31] docs/38772  doc         firewall_type feature not mentioned on Ha
o [2002/06/07] docs/38982  doc         developers-hanbook/Jail fix
o [2002/06/12] docs/39213  doc         No rc(4) man page
o [2002/06/15] docs/39348  doc         kenv fetch of hostname requires dhcp/boot
o [2002/06/19] docs/39530  doc         access(2) man page has unnecessarily broa
o [2002/06/19] docs/39532  doc         'find' man page should
o [2002/06/24] docs/39824  doc         Various tweaks for doc/en_US.ISO8859-1/bo
o [2002/07/04] docs/40196  doc         man find does not describe -follow
o [2002/07/10] docs/40423  doc         Keyboard(4)'s definition of parameters to
o [2002/07/10] docs/40443  doc         Update books/faq/book.sgml for USB .ko's 
o [2002/07/21] docs/40851  doc         [PATCH] "mergemaster -p" in UPDATING's "C
o [2002/07/28] docs/41089  doc         pax -B option does not mention interactio
o [2002/08/02] docs/41270  doc         confusing directions for kernelconfig cha
o [2002/08/07] docs/41423  doc         Update FAQ: attrib command for windows du
o [2002/08/18] docs/41761  doc         Update for /ru/internal/ part of site
o [2002/08/19] docs/41787  doc         man page for route (Section 8) missing de
o [2002/08/19] docs/41791  doc         Documentation formatting error
o [2002/08/19] docs/41807  doc         natd -punch_fw "bug"
o [2002/08/20] docs/41820  doc         Device driver confusion in Handbook (2.3)
a [2002/08/27] docs/42058  doc         Documentation: Installing Oracle 8i onto 
o [2002/10/01] docs/43569  doc         src/share/examples/worm/README out-of-dat
o [2002/10/04] docs/43651  doc         stab(5) incorrectly states to include jus
o [2002/10/09] docs/43861  doc         non-trivial typo in wicontrol man page
o [2002/10/11] docs/43941  doc         Rationale for Upgrade Sequence
o [2002/10/14] docs/44074  doc         ln(1) manual clarifications [patch]
o [2002/10/23] docs/44400  doc         ipfw(8) has contradictions in bridged and
o [2002/10/24] docs/44435  doc         sysctl manpage: add example for tcsh
o [2002/10/29] docs/44594  doc         Handbook doesn't mention drivers.flp for 
o [2002/11/17] docs/45371  doc         man page for exports lacks information on
o [2002/12/02] docs/45940  doc         burncd missing info
o [2002/12/11] docs/46181  doc         "make fetch-recursive" target description
o [2002/12/11] docs/46196  doc         Missing return value in (set_)menu_format
o [2002/12/11] docs/46200  doc         fix for ru_RU.KOI8-R/books/porters-handbo
o [2002/12/16] docs/46291  doc         correlation between HZ kernel config para
o [2002/12/16] docs/46295  doc         please add information to Nvi recovery em
o [2003/01/02] docs/46709  doc         tables in terminfo.5 are broken
o [2003/01/05] docs/46793  doc         DEVICE_POLLING can not be used with SMP, 
o [2003/01/14] docs/47085  doc         boot(8) manpage is incomplete according t
o [2003/01/27] docs/47575  doc         Clarify requirements for IPFW2 in STABLE
o [2003/01/28] docs/47594  doc         [PATH] passwd(5) incorrectly states allow
o [2003/01/30] docs/47690  doc         builtin(1) manpage is wrong about externa
o [2003/01/30] docs/47705  doc         wc(1) manpage has poor explanations.
f [2003/02/02] docs/47818  doc         ln(1) manpage is confusing
f [2003/02/07] docs/48038  doc         [PATCH] add Tips and Tricks section into 
o [2003/02/28] docs/48767  doc         wrong key numbers for left/right windows 
o [2003/03/06] docs/48980  doc         [PATCH] nsgmls -s errors and sect. 3.2.1 
o [2003/03/14] docs/50013  doc         [PATCH] add much more russian holydays
o [2003/03/23] docs/50211  doc         [PATCH] Fix textfile creation
f [2003/03/28] docs/50391  doc         Incorrect information in a man
o [2003/04/03] docs/50573  doc         return values for res_query/res_search/re
f [2003/04/07] docs/50677  doc         [PATCH] update doc/en_US.ISO8859-1/books/
o [2003/04/10] docs/50773  doc         NFS problems by jumbo frames to mention i
o [2003/05/06] docs/51875  doc         atkbd(4) adjustment
o [2003/05/06] docs/51891  doc         DIAGNOSTICS in ed driver manpage don't ma
o [2003/05/07] docs/51921  doc         ls(1) manpage lacks some information abou
o [2003/05/11] docs/52071  doc         [PATCH] Add more information about soft u
o [2003/05/25] docs/52672  doc         Porter's Handbook: couple of corrections
o [2003/06/02] docs/52878  doc         [PATCH] security(7): small clairification
o [2003/06/13] docs/53303  doc         mount(2) man page error
o [2003/06/14] docs/53315  doc         [PATCH] remove extraneous whitespace at t
o [2003/06/18] docs/53454  doc         wrong sample code in manpage of wcwidth(3
o [2003/06/19] docs/53501  doc         [PATCH] Handbook: update snapshots sectio
o [2003/06/20] docs/53575  doc         Change to Handbook Section 20.9
o [2003/06/21] docs/53596  doc         Updates to mt manual page
o [2003/06/25] docs/53732  doc         quota output and man page do not document
o [2003/06/26] docs/53751  doc         bus_dma(9) incorrectly documents BUS_DMA_
o [2003/07/11] docs/54380  doc         [PATCH] document additional perl variable
o [2003/07/11] docs/54391  doc         Document that glob(3) respects LC_COLLATE
o [2003/07/20] docs/54678  doc         [patch] add PACKAGESITE to packages chapt
o [2003/07/22] docs/54752  doc         bus_dma explained in ISA section: should 
o [2003/07/22] docs/54769  doc         [patch] updates to FAQ
o [2003/07/23] docs/54789  doc         [PATCH] brush up the "New Users" article
o [2003/07/24] docs/54806  doc         [patch] adds fvwm2 to x11-wm
o [2003/07/25] docs/54879  doc         man 1 jot, -r description
o [2003/07/28] docs/54995  doc         Error in accept(2) man page
o [2003/07/28] docs/54999  doc         Documentation Project Primer doesn't conf
o [2003/08/03] docs/55207  doc         [patch] update acroread section & add loc
o [2003/08/06] docs/55306  doc         [patch] adds filemanagers to desktop appl
o [2003/08/11] docs/55458  doc         [patch] add useful content & hints to por
o [2003/08/11] docs/55482  doc         DUMP has access to block devices in a JAI
o [2003/08/13] docs/55538  doc         [patch] add screenshots to desktop chapte
o [2003/08/16] docs/55653  doc         chflags.1 - note that not all tools chfla
o [2003/09/04] docs/56408  doc         [PATCH] add <filename> around app-default
o [2003/09/04] docs/56452  doc         [patch]Add EXTRACT_DEPENDS&PATCH_DEPENDS 
o [2003/09/13] docs/56745  doc         Some suggestions for the Bibliography cha
o [2003/09/14] docs/56872  doc         [Patch] Talk about EVFILT_NETDEV in kqueu
o [2003/09/14] docs/56883  doc         Inadequately-documented charter for freeb
o [2003/09/15] docs/56901  doc         [patch] articles/diskless-x: fix bad engl
o [2003/09/15] docs/56903  doc         [patch] articles/fonts: add application t
o [2003/09/16] docs/56915  doc         [patch] articles/fonts: update links
o [2003/09/16] docs/56932  doc         [patch] articles/releng-packages: add "no
o [2003/09/16] docs/56936  doc         [patch] articles/java-tomcat: add applica
o [2003/09/18] docs/56981  doc         man terminfo(5) from libncurses does not 
o [2003/09/22] docs/57118  doc         
o [2003/09/24] docs/57153  doc         S_IRWXU missing in fstat(2) man page?
o [2003/09/29] docs/57388  doc         INSTALL.TXT enhancement: mention ok promp
o [2003/10/04] docs/57569  doc         error on gensetdefs(8) man page
o [2003/10/06] docs/57669  doc         IFMIB(4) man page uses sysctl(3) incorrec
o [2003/10/10] docs/57838  doc         missing in docu: port Makefile target 'pa
o [2003/10/12] docs/57926  doc         amd.conf.5 poorly format as it has both m
o [2003/10/13] docs/57974  doc         man page apropos for select macros (FD_SE
o [2003/10/13] docs/57978  doc         Type miss of GPIB in Hardware Notes
o [2003/10/16] docs/58111  doc         Handbook 12.4.3 Rebuilding ATA RAID1 Arra

139 problems total.


From bmah at FreeBSD.org  Mon Oct 20 18:05:13 2003
From: bmah at FreeBSD.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 11:05:05 -0700
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020163117.GB1370@electra.cse.Buffalo.EDU>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020163117.GB1370@electra.cse.Buffalo.EDU>
Message-ID: <20031020180505.GA58041@intruder.kitchenlab.org>

If memory serves me right, Ken Smith wrote:
> On Mon, Oct 20, 2003 at 09:16:06AM -0700, Bruce A. Mah wrote:
> 
> > Yeeek, what are those hard-coded version numbers doing in there?!?
> > Actually...are there some other related constants (i.e. amount of disk
> > space) that might need to be changed or otherwise track a version
> > number?  I haven't read the hubs article lately.
> 
> The numbers were adjusted to current reality 2 or 3 months ago.

OK, sounds good.

> That
> said the hubs article does need more work.  We were trying to come to
> something resembling consensus on what being an Official Mirror Site
> meant but that discussion was going on at the same time we were
> planning changes to the content of the site (dropping branches/) so
> it seemed like it would be best to procrastinate a bit on trying to
> finish the discussion.  I'm not tracking more information about the
> sites and started to incorporate some of it into the article as well,
> which effects some of what's there (e.g. I added what access methods
> are available to the list of FTP mirror sites which makes the section
> about rsync hosts possibly defunct, but there was also http added
> as an access method and keeping separate lists of hosts for all three
> access methods seems a bit much...).

I'm actually not worried about the main content so much because it
seems to be that it's still being defined.  That's perfectly OK.

> The disk space numbers can't *really* be linked straight to an OS
> version because there is so much other stuff in the site.  The
> size of the ports/distfiles and to some extent the -current package
> sets fluctuate based on non-release-issues.

OK, sounds good.  I just didn't want us to be in a state where we were
changing version numbers but not other quantities that were strongly
related to the version numbers.

I was tempted to remove or rework the words "current state" from the
document and just manually increment the version numbers and space
requirements as new information becomes available.  But we're probably
fine for now by changing "4.8" to "4.9", as ceri's patch did.

Thanks!

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/0b9b90bb/attachment.sig>

From ceri at FreeBSD.org  Mon Oct 20 22:19:34 2003
From: ceri at FreeBSD.org (Ceri Davies)
Date: Mon, 20 Oct 2003 23:19:29 +0100
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020161606.GA56817@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
Message-ID: <20031020221929.GF3708@submonkey.net>

On Mon, Oct 20, 2003 at 09:16:06AM -0700, Bruce A. Mah wrote:
> If memory serves me right, Ceri Davies wrote:
> 
> > Could I throw out the idea of committing the attached diff before that
> > happens?  I know that we normally do this after doc/ has been tagged,
> > but that has always seemed strange to me, as the documentation tagged
> > as 4.9-RELEASE doesn't contain any references to it.
> > 
> > Of course, the downside is that the website will reflect things that
> > don't exist yet.
> 
> Well, the way I usually like to do this is to tag first (with the doc/
> tree in a usable state), then change certain files that have version
> numbers in them, and then slide the tags on those files.  As you
> correctly implied, it doesn't always work that way.  :-)

I didn't actually realise that you slid the tags at a later date; if
that's the case then you should pretend I never said anything.

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/cf8aef66/attachment.sig>

From bmah at FreeBSD.org  Mon Oct 20 22:27:26 2003
From: bmah at FreeBSD.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 15:27:24 -0700
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020221929.GF3708@submonkey.net>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020221929.GF3708@submonkey.net>
Message-ID: <20031020222724.GA60569@intruder.kitchenlab.org>

If memory serves me right, Ceri Davies wrote:

> I didn't actually realise that you slid the tags at a later date; if
> that's the case then you should pretend I never said anything.

I could pretend you never said anything and that you mysteriously
dropped a patch to me that just happens to contain all the changes
that we need to do the version number bumps.  :-)

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/5ade49fa/attachment.sig>

From setantae at submonkey.net  Mon Oct 20 22:33:21 2003
From: setantae at submonkey.net (Ceri Davies)
Date: Mon, 20 Oct 2003 23:33:15 +0100
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020222724.GA60569@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020221929.GF3708@submonkey.net>
	<20031020222724.GA60569@intruder.kitchenlab.org>
Message-ID: <20031020223315.GH3708@submonkey.net>

On Mon, Oct 20, 2003 at 03:27:24PM -0700, Bruce A. Mah wrote:
> If memory serves me right, Ceri Davies wrote:
> 
> > I didn't actually realise that you slid the tags at a later date; if
> > that's the case then you should pretend I never said anything.
> 
> I could pretend you never said anything and that you mysteriously
> dropped a patch to me that just happens to contain all the changes
> that we need to do the version number bumps.  :-)

I could pretend I never said anything and that you mysteriously
dropped a glass to me that just happens to contain all the^W^Wbeer ;-)

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/beb594f4/attachment.sig>

From bmah at FreeBSD.org  Mon Oct 20 23:43:30 2003
From: bmah at FreeBSD.org (Bruce A. Mah)
Date: Mon, 20 Oct 2003 16:43:27 -0700
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020223315.GH3708@submonkey.net>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020221929.GF3708@submonkey.net>
	<20031020222724.GA60569@intruder.kitchenlab.org>
	<20031020223315.GH3708@submonkey.net>
Message-ID: <20031020234327.GA61488@intruder.kitchenlab.org>

If memory serves me right, Ceri Davies wrote:

> I could pretend I never said anything and that you mysteriously
> dropped a glass to me that just happens to contain all the^W^Wbeer ;-)

Heh.  This droppage would, of course, depend on deployment of the
Remote Beer Protocol.  :-)

Back on topic, I've tagged doc/ with the RELEASE_4_9_0 tag and I'm
doing a test build to make sure it's all happy now.  If all goes well,
I'll wait some appropriate amount of time and then commit the version
number bump patch and slide the tags.

Thanks all,

Bruce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031020/1ef5d24e/attachment.sig>

From fullermd at over-yonder.net  Tue Oct 21 02:01:28 2003
From: fullermd at over-yonder.net (Matthew D. Fuller)
Date: Mon, 20 Oct 2003 21:01:22 -0500
Subject: HEADS-UP: doc/ tree slushie
In-Reply-To: <20031020234327.GA61488@intruder.kitchenlab.org>
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020221929.GF3708@submonkey.net>
	<20031020222724.GA60569@intruder.kitchenlab.org>
	<20031020223315.GH3708@submonkey.net>
	<20031020234327.GA61488@intruder.kitchenlab.org>
Message-ID: <20031021020122.GI97507@over-yonder.net>

On Mon, Oct 20, 2003 at 04:43:27PM -0700 I heard the voice of
Bruce A. Mah, and lo! it spake thus:
> If memory serves me right, Ceri Davies wrote:
> 
> > I could pretend I never said anything and that you mysteriously
> > dropped a glass to me that just happens to contain all the^W^Wbeer ;-)
> 
> Heh.  This droppage would, of course, depend on deployment of the
> Remote Beer Protocol.  :-)

You're thinking of UUBP (I've got a manpage for it somewhere in the
pigsty that is $HOME...)


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

"The only reason I'm burning my candle at both ends, is because I
      haven't figured out how to light the middle yet"


From kdk at daleco.biz  Tue Oct 21 05:40:12 2003
From: kdk at daleco.biz (Kevin Kinsey)
Date: Tue, 21 Oct 2003 00:33:52 -0500 (CDT)
Subject: docs/58318: missing modifier in crontab(5) manpage (changes
	meaning...)
Message-ID: <200310210533.h9L5XqXV060412@ezekiel.daleco.biz>


>Number:         58318
>Category:       docs
>Synopsis:       missing modifier in crontab(5) manpage (changes meaning...)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 20 22:40:10 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Kevin Kinsey
>Release:        FreeBSD 4.9-PRERELEASE i386
>Organization:
DaleCo, S.P.
>Environment:
System: FreeBSD ezekiel.daleco.biz 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #7: Mon Sep 22 17:20:53 CDT 2003 kadmin at ezekiel.daleco.biz:/usr/obj/usr/src/sys/GENERIC i386


>Description:
	Examination of context clearly shows that the word "Not" should appear
	in the statement "Lists and ranges are allowed to co-exist in the
	same field...."
>How-To-Repeat:
	$man 5 crontab
	# read the "Extensions" paragraph(s)
>Fix:

	Diff submitted...

*** crontab.5   Fri Dec 27 06:15:36 2002
--- crontab.5.edit      Tue Oct 21 00:30:51 2003
***************
*** 230,236 ****
  .Tn ATT
  seem to disagree about this.
  .Pp
! Lists and ranges are allowed to co-exist in the same field.  "1-3,7-9" would
  be rejected by
  .Tn ATT
  or
--- 230,236 ----
  .Tn ATT
  seem to disagree about this.
  .Pp
! Lists and ranges are not allowed to co-exist in the same field.  "1-3,7-9" would
  be rejected by
  .Tn ATT
  or


>Release-Note:
>Audit-Trail:
>Unformatted:


From rc1977 at o2.pl  Tue Oct 21 11:42:43 2003
From: rc1977 at o2.pl (=?Windows-1250?B?UmFkb3OzYXcgQ2ljaHk=?=)
Date: Tue, 21 Oct 2003 13:51:21 +0200
Subject: Bug in article.
Message-ID: <7213362559.20031021135121@o2.pl>

Hello

I've found bug in article "Filtering bridges"

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/article.html

In Chapter 4 "Enabling the Bridge" has been written :

# sysctl net.link.ether.bridge_cfg=fxp0:0,xl0:0
# sysctl net.link.ether.bridge_ipfw=1
# sysctl net.link.ether.bridge=1

But bridge configuration should be done AFTER bringing it UP (and that agrees to
manual for bridge module).

I spend 3 days doing it this way before I caught the bug :)

Greetings from Poland
Radek Cichy

BTW: In polish translation of this article there's bug too.


From sysadmin at alexdupre.com  Tue Oct 21 12:09:05 2003
From: sysadmin at alexdupre.com (Alex Dupre)
Date: Tue, 21 Oct 2003 14:06:47 +0200
Subject: Bug in article.
In-Reply-To: <7213362559.20031021135121@o2.pl>
References: <7213362559.20031021135121@o2.pl>
Message-ID: <12004875298.20031021140647@alexdupre.com>

Tuesday, October 21, 2003, 1:51:21 PM, you wrote:

RC> I've found bug in article "Filtering bridges"

RC> But bridge configuration should be done AFTER bringing it UP

That's not true, I always set up the bridge BEFORE enabling it.

-- 
Alex Dupre                             sysadmin at alexdupre.com
http://www.alexdupre.com/              alex at sm.FreeBSD.org

Today's excuse: Plate voltage too low on demodulator tube



From skylus at hotmail.com  Tue Oct 21 18:10:31 2003
From: skylus at hotmail.com (Tham Kok Seng)
Date: Wed, 22 Oct 2003 02:10:30 +0800
Subject: Regarding download into FPGA chip
Message-ID: <BAY1-F76543TuylJc0x00000564@hotmail.com>


     _________________________________________________________________

   Hi Sir,

   I am college student, and now having the problem to download my final
   project ( DMA controller). Can you teach me the step for download VHDL
   program into FPGA? And the connection for the fpga after download....

   For this projet I need to communicate with microproccessor with port i
   should connect (parallel port or serial port or others).

   Thank and regards

   From:
   Dennis
     _________________________________________________________________

   Add photos to your e-mail with [1]MSN 8. Get 2 months FREE*.

References

   1. http://g.msn.com/8HMBEN/2746??PS=


From watchman at ludd.luth.se  Tue Oct 21 20:10:19 2003
From: watchman at ludd.luth.se (Joachim Strombergson)
Date: Tue, 21 Oct 2003 22:02:24 +0200
Subject: docs/58347: Wrong include path in man (9) for rijndael
Message-ID: 1066766533@fetis.ninja.se


>Number:         58347
>Category:       docs
>Synopsis:       Wrong include path in man (9) for rijndael
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 21 13:10:12 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Joachim Strombergson
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
>Environment:


System: FreeBSD fetis.ninja.se 5.1-CURRENT FreeBSD 5.1-CURRENT #13: Sun Sep 28 11:03:31 CEST 2003     js at fetis.ninja.se:/usr/obj/usr/src/sys/ATHLON i386  


>Description:


The manual page for rijndael contains an include path that is incorrect. The manual states:

SYNOPSIS
     #include <sys/types.h>
     #include <crypto/rijndael/rijndael.h>

But, Rijndael is actually locates in:
/usr/include/crypto/rijndael.h

That is, in the crypto subdir, not in a specific Rijndael directory.


>How-To-Repeat:


man rijndael and then try to use the includes found in the man page in an application that uses Rijndael:

<qote>
gcc -O -o testRijndael rijndael_regtest.c
rijndael_regtest.c:20:38: crypto/rijndael/rijndael.h: No such file or directory
*** Error code 1
</quote>



>Fix:


Apply the following patch:

--- /usr/src/share/man/man9/rijndael.9  Fri Apr 12 07:23:16 2002
+++ /usr/src/share/man/man9/rijndael.9  Tue Oct 21 21:58:58 2003
@@ -39,7 +39,7 @@
 .Nd AES encryption
 .Sh SYNOPSIS
 .In sys/types.h
-.In crypto/rijndael/rijndael.h
+.In crypto/rijndael.h
 .Ft int
 .Fo rijndael_makeKey
 .Fa "keyInstance *key"



>Release-Note:
>Audit-Trail:
>Unformatted:


From ceri at FreeBSD.org  Tue Oct 21 21:00:35 2003
From: ceri at FreeBSD.org (Ceri Davies)
Date: Tue, 21 Oct 2003 14:00:33 -0700 (PDT)
Subject: docs/58318: missing modifier in crontab(5) manpage (changes
	meaning...)
Message-ID: <200310212100.h9LL0XOI044021@freefall.freebsd.org>

The following reply was made to PR docs/58318; it has been noted by GNATS.

From: Ceri Davies <ceri at FreeBSD.org>
To: Kevin Kinsey <kdk at daleco.biz>
Cc: FreeBSD-gnats-submit at FreeBSD.org
Subject: Re: docs/58318: missing modifier in crontab(5) manpage (changes meaning...)
Date: Tue, 21 Oct 2003 21:57:53 +0100

 On Tue, Oct 21, 2003 at 12:33:52AM -0500, Kevin Kinsey wrote:
 > 
 > >Description:
 > 	Examination of context clearly shows that the word "Not" should appear
 > 	in the statement "Lists and ranges are allowed to co-exist in the
 > 	same field...."
 > >How-To-Repeat:
 > 	$man 5 crontab
 > 	# read the "Extensions" paragraph(s)
 
 I think you'll find that they *are* allowed (that is the nature of the extension).
 Read the paragraph again, bearing in mind that you are reading about Vixie cron:
 
      Lists and ranges are allowed to co-exist in the same field.  "1-3,7-9"
      would be rejected by ATT or BSD cron -- they want to see "1-3" or "7,8,9"
      ONLY.
 
 i.e. this cron does allow it.
 
 Ceri
 
 -- 


From wblock at wonkity.com  Tue Oct 21 22:46:53 2003
From: wblock at wonkity.com (Warren Block)
Date: Tue, 21 Oct 2003 16:46:50 -0600 (MDT)
Subject: docs/58318: missing modifier in crontab(5) manpage (changes
 meaning...)
In-Reply-To: <200310212100.h9LL0XOI044021@freefall.freebsd.org>
References: <200310212100.h9LL0XOI044021@freefall.freebsd.org>
Message-ID: <20031021163829.R57162@wonkity.com>

On Tue, 21 Oct 2003, Ceri Davies wrote:

> I think you'll find that they *are* allowed (that is the nature of the
> extension).  Read the paragraph again, bearing in mind that you are
> reading about Vixie cron:
>
>   Lists and ranges are allowed to co-exist in the same field.
>   "1-3,7-9" would be rejected by ATT or BSD cron -- they want to see
>   "1-3" or "7,8,9" ONLY.
>
>  i.e. this cron does allow it.

Some slight editing might be in order:

    Lists and ranges are allowed to co-exist in the same field.
    (Traditional ATT or BSD cron would reject "1-3,7-9" -- they
    want to see "1-3" or "7,8,9" ONLY.)

Or something like that.

-Warren Block * Rapid City, South Dakota USA


From barner at in.tum.de  Tue Oct 21 23:30:12 2003
From: barner at in.tum.de (Simon Barner)
Date: Wed, 22 Oct 2003 01:22:56 +0200 (CEST)
Subject: docs/58355: bktr(4) man page: location for fxtv port
Message-ID: <20031021232256.876B6B7C@zi025.glhnet.mhn.de>


>Number:         58355
>Category:       docs
>Synopsis:       bktr(4) man page: location for fxtv port
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 21 16:30:10 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 at zi025.glhnet.mhn.de:/usr/src/sys/compile/KISTE i386

>Description:

Reflect the fact that fxtv is found in ports/multimedia/fxtv now also in
the bktr(4) man page.

>How-To-Repeat:
>Fix:

--- share/man/man4/bktr.4.orig	Wed Oct 22 01:19:39 2003
+++ share/man/man4/bktr.4	Wed Oct 22 01:20:02 2003
@@ -154,7 +154,7 @@
 .Bl -tag -width /usr/share/examples/meteor -compact
 .It Pa /usr/share/examples/meteor
 Examples of what you can do with the (similarly designed) Meteor driver.
-.It Pa /usr/ports/graphics/fxtv
+.It Pa /usr/ports/multimedia/fxtv
 A TV and Camera display program utilizing the bktr driver - requires that
 .Em The X Window System
 and
>Release-Note:
>Audit-Trail:
>Unformatted:


From simon at FreeBSD.org  Tue Oct 21 23:37:30 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Tue, 21 Oct 2003 16:37:29 -0700 (PDT)
Subject: docs/58355: bktr(4) man page: location for fxtv port
Message-ID: <200310212337.h9LNbTRi061312@freefall.freebsd.org>

Synopsis: bktr(4) man page: location for fxtv port

State-Changed-From-To: open->closed
State-Changed-By: simon
State-Changed-When: Tue Oct 21 16:37:03 PDT 2003
State-Changed-Why: 
Commited, thanks for the submission!

http://www.freebsd.org/cgi/query-pr.cgi?pr=58355


From linimon at FreeBSD.org  Wed Oct 22 06:53:58 2003
From: linimon at FreeBSD.org (Mark Linimon)
Date: Tue, 21 Oct 2003 23:53:57 -0700 (PDT)
Subject: docs/58033: [PATCH] getenv(3) manpage doesn't state the return
	value of getenv.
Message-ID: <200310220653.h9M6rvQj005707@freefall.freebsd.org>

Synopsis: [PATCH] getenv(3) manpage doesn't state the return value of getenv.

Responsible-Changed-From-To: gnats-admin->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Oct 21 23:52:22 PDT 2003
Responsible-Changed-Why: 
Reassign to proper category.

http://www.freebsd.org/cgi/query-pr.cgi?pr=58033


From hmp at FreeBSD.org  Wed Oct 22 09:57:36 2003
From: hmp at FreeBSD.org (Hiten Pandya)
Date: Wed, 22 Oct 2003 02:57:35 -0700 (PDT)
Subject: docs/58347: Wrong include path in man (9) for rijndael
Message-ID: <200310220957.h9M9vZgS026289@freefall.freebsd.org>

Synopsis: Wrong include path in man (9) for rijndael

Responsible-Changed-From-To: freebsd-doc->hmp
Responsible-Changed-By: hmp
Responsible-Changed-When: Wed Oct 22 02:57:16 PDT 2003
Responsible-Changed-Why: 
I will commit a fix.


http://www.freebsd.org/cgi/query-pr.cgi?pr=58347


From adamw at FreeBSD.org  Wed Oct 22 19:32:23 2003
From: adamw at FreeBSD.org (Adam Weinberger)
Date: 22 Oct 2003 15:32:18 -0400
Subject: a reminder to PR submitters
In-Reply-To: <Pine.LNX.4.44.0310220135110.4822-100000@pancho>
References: <Pine.LNX.4.44.0310220135110.4822-100000@pancho>
Message-ID: <20031022193218.GM96543@toxic.magnesium.net>

I'm cc'ing this to freebsd-doc and Ceri, resident bugmeister, as their
input in this is important.

>> (10.22.2003 @ 0242 PST): Mark Linimon said, in 0.9K: <<
> Please do not set the Confidential field on your PRs to "yes".
> We really don't have a mechanism to deal with confidential
> PRs in GNATS due to the fact that the database itself can be
> replicated, via cvsup, to anyone's machine, and thus itself is
> inherently insecure.  Setting this field to "yes" merely makes
> your PR disappear into this limbo-category called "pending" which
> is dark and scary and filled with big spiders and stuff :-)
>> end of "a reminder to PR submitters" from Mark Linimon <<

There are a number of fields within GNATS that mean things to us (the
committers) that don't make sense to submitters, and there are fields
that have no use for us whatsoever.

Confidential
	This field is, as you have pointed out, useless to us, and
	simply causes the PR to disappear. The field should be removed
	from the send-pr interface, or some mechanism for handling
	confidential PRs should be introduced. I suggest the former.
Severity/Priority
	These are relatively redundant, and are simply mechanisms for
	people to artificially elevate the position of the PR in the
	search lists -- which, in my experience, causes them to be seen
	LAST.
Class
	Seriously. The classes in here make sense to us, because we're
	used to dealing with them. For ports, we need fields that
	indicate the following:
		* update/upgrade
		* fix/new functionality
		* error report
		* other
Submitter-Id
	"current-users" doesn't mean a thing. Submitter-Id should be
	usable as "user" or "maintainer," depending upon who submits the
	PR. If a maintainer wishes to submit a PR for an update to a
	port she maintains, she should be able to choose
	Class:update/upgrade, and Submitter-Id:maintainer.

Additionally, text should be added to the bracketed text in the blank
send-pr template indicating the use of each section for docs/ports/www
PRs:
Description
	<precise description of the problem (multiple lines)>
	<for new ports, description of application>
Fix
	<how to correct or work around the problem, if known (multiple lines)>
	<shar of new port, diffs for port/documentation updates>

You know, stuff like that. These things can help make send-pr(1) a more
usable tool.

# Adam


--
Adam Weinberger
vectors.cx	>>  adam at vectors.cx	>>  http://www.vectors.cx
magnesium.net	<<  adamw at magnesium.net	<<  http://www.magnesium.net/~adamw
FreeBSD		>>  adamw at FreeBSD.org	>>  http://people.freebsd.org/~adamw
#vim:set ts=8: 8-char tabs prevent tooth decay.


From marck at rinet.ru  Wed Oct 22 20:00:18 2003
From: marck at rinet.ru (Dmitry Morozovsky)
Date: Wed, 22 Oct 2003 13:00:17 -0700 (PDT)
Subject: docs/41761 cvs commit: www/ru/internal about.sgml
 internal.sgmlphotos.sgml statistic.sgml (fwd)
Message-ID: <200310222000.h9MK0Hwa061114@freefall.freebsd.org>

The following reply was made to PR docs/41761; it has been noted by GNATS.

From: Dmitry Morozovsky <marck at rinet.ru>
To: bug-followup at freebsd.org
Cc:  
Subject: Re: docs/41761 cvs commit: www/ru/internal about.sgml internal.sgmlphotos.sgml
 statistic.sgml (fwd)
Date: Wed, 22 Oct 2003 23:51:31 +0400 (MSD)

 From cvs commit list:
 
 Sincerely,
 D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
 ------------------------------------------------------------------------
 *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
 ------------------------------------------------------------------------
 
 ---------- Forwarded message ----------
 Date: Wed, 22 Oct 2003 23:45:19 +0400 (MSD)
 From: Dmitry Morozovsky <marck at rinet.ru>
 To: Denis Peplin <den at freebsd.org>
 Cc: doc-committers at freebsd.org, cvs-doc at freebsd.org, cvs-all at freebsd.org
 Subject: Re: cvs commit: www/ru/internal about.sgml
     internal.sgmlphotos.sgml statistic.sgml
 
 On Wed, 22 Oct 2003, Denis Peplin wrote:
 
 DP> > Please close outdated docs/41761 PR. Thank you for your efforts!
 DP>
 DP> I'm forgot to look into PR database before commiting. Sorry.
 DP>
 DP> But docs/41761 is not completly outdated - it contains
 DP> new translations (bylaws.sgml, expire-bits.sgml, new-account.sgml) and patch
 DP> to machines.sgml.
 DP>
 DP> Could submit followup with original revisions for this files?
 DP>
 DP> Thanks!
 
 Ouch. I suppose they were just up to date for the point of PR submission, so
 cvs get -D20020818 www/en/internal
 would do the trick ;-)
 
 Here they are:
 
 bylaws.sgml:
      $FreeBSD: www/en/internal/bylaws.sgml,v 1.3 2002/05/03 18:23:44 imp Exp $
 expire-bits.sgml:
      $FreeBSD: www/en/internal/expire-bits.sgml,v 1.1 2002/04/06 15:35:30 rwatson Exp $
 new-account.sgml:
      $FreeBSD: www/en/internal/new-account.sgml,v 1.2 2002/03/16 08:13:04 murray Exp $
 machines.sgml:
      $FreeBSD: www/en/internal/machines.sgml,v 1.31 2002/08/03 19:59:08 blackend Exp $
 
 BTW, I would be glad to help Russian Translation Team in your process; if you
 or your coordinator interested, please contact me.
 
 Thanks again.
 
 Sincerely,
 D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
 ------------------------------------------------------------------------
 *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
 ------------------------------------------------------------------------
 _______________________________________________
 cvs-all at freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe at freebsd.org"


From www at FreeBSD.org  Wed Oct 22 20:24:43 2003
From: www at FreeBSD.org (World Wide Web Owner)
Date: Wed, 22 Oct 2003 13:24:42 -0700 (PDT)
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200310222024.h9MKOgMP052212@www.freebsd.org>

install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/faq
===> ../es/doc/books/handbook
install -c  -o www -g www -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 book.html /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
install -c  -o www -g www -m 444 docbook.css /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook
/w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/handbook.html -> /w/www/build/www/es/doc/es_ES.ISO8859-1/books/handbook/index.html
/w/www/build/www/es/doc/es -> /w/www/build/www/es/doc/es_ES.ISO8859-1
===> ../ru
(cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/usr/local/www/www.freebsd.org/data/ru/FAQ all)
===> ../ru/security
===> ../ru/commercial
===> ../ru/docproj
===> ../ru/news
===> ../ru/news/1996
===> ../ru/news/1997
===> ../ru/news/1998
===> ../ru/news/1999
===> ../ru/news/2000
===> ../ru/news/2001
===> ../ru/news/2002
===> ../ru/FAQ
(cd ../../../doc/ru_RU.KOI8-R/books/faq; make 'FORMATS=html-split html' DESTDIR=/usr/local/www/www.freebsd.org/data/ru/FAQ all)
===> ../ru/handbook
===> ../ru/internal
===> ../ru/java
===> ../ru/java/dists
===> ../ru/java/docs
===> ../ru/java/links
===> ../ru/copyright
===> ../ru/search
===> ../ru/gallery
===> ../ru/projects
===> ../ru/platforms
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  alpha.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ru/platforms > alpha.html ||  (/bin/rm -f alpha.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  alpha.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  amd64.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ru/platforms > amd64.html ||  (/bin/rm -f amd64.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  amd64.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  ia64.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ru/platforms > ia64.html ||  (/bin/rm -f ia64.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  ia64.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  index.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ru/platforms > index.html ||  (/bin/rm -f index.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  index.html
make: don't know how to make x86-64.html. Stop
*** Error code 2

Stop in /w/www/build/www/ru.
*** Error code 1

Stop in /w/www/build/www/en.
      141.57 real        73.55 user        43.18 sys


From linimon at lonesome.com  Wed Oct 22 20:25:15 2003
From: linimon at lonesome.com (Mark Linimon)
Date: Wed, 22 Oct 2003 15:25:08 -0500 (CDT)
Subject: a reminder to PR submitters
In-Reply-To: <20031022193218.GM96543@toxic.magnesium.net>
Message-ID: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>

While these are all good points, a GNATS upgrade is in the
works, so there's little reason to try to fix the existing one.
IIRC des has been insistent on deprecating the severity/priority
fields (as you note, the data in them are 90%+ bogus).

However, worse than all these problems is the fact that no
one has come up with code to reenable the web-based send-pr,
and IMHO that's a more important (but related) task to all
the above.

Note that I'm not volunteering any patches to any of the
above at this time :-)

Well, maybe I might for the templates, since they're pretty
busted, anwyays.

mcl



From anderson at centtech.com  Wed Oct 22 20:30:58 2003
From: anderson at centtech.com (Eric Anderson)
Date: Wed, 22 Oct 2003 15:30:36 -0500
Subject: a reminder to PR submitters
In-Reply-To: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
Message-ID: <3F96E8EC.7010609@centtech.com>

Mark Linimon wrote:

>While these are all good points, a GNATS upgrade is in the
>works, so there's little reason to try to fix the existing one.
>IIRC des has been insistent on deprecating the severity/priority
>fields (as you note, the data in them are 90%+ bogus).
>
>However, worse than all these problems is the fact that no
>one has come up with code to reenable the web-based send-pr,
>and IMHO that's a more important (but related) task to all
>the above.
>
>Note that I'm not volunteering any patches to any of the
>above at this time :-)
>
>Well, maybe I might for the templates, since they're pretty
>busted, anwyays.
>  
>

I'd be willing to work on a replacement for the web-send-pr cgi 
program.  I looked at it a year or so ago, and got distracted by other 
things. 

Can someone give me a list of "requirements" for the new program?

Eric

-- 
------------------------------------------------------------------
Eric Anderson	   Systems Administrator      Centaur Technology
All generalizations are false, including this one.
------------------------------------------------------------------



From linimon at lonesome.com  Wed Oct 22 20:36:21 2003
From: linimon at lonesome.com (Mark Linimon)
Date: Wed, 22 Oct 2003 15:36:12 -0500
Subject: a reminder to PR submitters
In-Reply-To: <3F96E8EC.7010609@centtech.com>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
	<3F96E8EC.7010609@centtech.com>
Message-ID: <200310221536.12270.linimon@lonesome.com>

> Can someone give me a list of "requirements" for the new program?

The primary goal would be to be able to block abusive users.
Whether via a blacklist, a whitelist, or manual intervention (yuck!)
isn't that relevant to me, but unfortunately without that there's no
reason to even go down that road :-(

mcl


From eikemeier at fillmore-labs.com  Wed Oct 22 21:09:19 2003
From: eikemeier at fillmore-labs.com (Oliver Eikemeier)
Date: Wed, 22 Oct 2003 23:09:09 +0200
Subject: a reminder to PR submitters
In-Reply-To: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
Message-ID: <3F96F1F5.7040707@fillmore-labs.com>

Mark Linimon wrote:

> While these are all good points, a GNATS upgrade is in the
> works, so there's little reason to try to fix the existing one.

Who is working on the upgrade?



From sem at ciam.ru  Thu Oct 23 00:19:24 2003
From: sem at ciam.ru (Sergey Matveychuk)
Date: Thu, 23 Oct 2003 04:17:37 +0400
Subject: a reminder to PR submitters
In-Reply-To: <20031022193218.GM96543@toxic.magnesium.net>
References: <Pine.LNX.4.44.0310220135110.4822-100000@pancho>
	<20031022193218.GM96543@toxic.magnesium.net>
Message-ID: <3F971E21.1020402@ciam.ru>

Adam Weinberger wrote:
> Submitter-Id
> 	"current-users" doesn't mean a thing. Submitter-Id should be
> 	usable as "user" or "maintainer," depending upon who submits the
> 	PR. If a maintainer wishes to submit a PR for an update to a
> 	port she maintains, she should be able to choose
> 	Class:update/upgrade, and Submitter-Id:maintainer.

It's a something new for me. And I think must be documented somewhere.

----
Sem.


From sem at ciam.ru  Thu Oct 23 00:25:04 2003
From: sem at ciam.ru (Sergey Matveychuk)
Date: Thu, 23 Oct 2003 04:23:18 +0400
Subject: a reminder to PR submitters
In-Reply-To: <3F96E8EC.7010609@centtech.com>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
	<3F96E8EC.7010609@centtech.com>
Message-ID: <3F971F76.90308@ciam.ru>

Eric Anderson wrote:
> I'd be willing to work on a replacement for the web-send-pr cgi 
> program.  I looked at it a year or so ago, and got distracted by other 
> things.
> Can someone give me a list of "requirements" for the new program?

It's may be not for cgi-program, but I'd like to have a mechanism to 
watch for some PR's. Like bugzilla or freshports.org have.

----
Sem.


From linimon at lonesome.com  Thu Oct 23 00:46:35 2003
From: linimon at lonesome.com (Mark Linimon)
Date: Wed, 22 Oct 2003 19:46:34 -0500 (CDT)
Subject: a reminder to PR submitters
In-Reply-To: <3F971F76.90308@ciam.ru>
Message-ID: <Pine.LNX.4.44.0310221934350.22984-100000@pancho>

> It's may be not for cgi-program, but I'd like to have a mechanism to 
> watch for some PR's. Like bugzilla or freshports.org have.

I have the code to scan PRs, but I do not have the subscription-
based back end like Dan (=freshports) has.  Failing that, I am
reluctant to just "send out" PR reminders.

The code I am working on is a batch-based reminder list that
would only go to a) people who do not have an @FreeBSD.org
address (because they can be assigned the PR in GNATS and
thus automatically reminded) intersection with b) PRs are
that more than "some number of days" old (I think my
prototype is set for 60 or 90).

The main problem with this is not technical, it's political.
I do not wish to unilaterally impose any post-facto burden
on maintainers.

The secondary problem is that my PR classification algorithm
generates false positives.  Thus before any run of the
notification code, my database must be manually preened to
remove them.  (I cannot imagine anything more irritating
than to get an automated complaint about something that
isn't really your problem and thus really can't do anything
about).

I was actively working on the batch code until I got a commit bit
a week or so ago and have been fixing other stuff since then :-)

In the meantime you can get an HTML page with your ports at
http://lonesome.dyndns.org:4802/bento/errorlogs/portsconcordanceformaintainer.py
and bookmark the result once you put in your own email address.

mcl


From ryan at tribug.org  Thu Oct 23 08:00:32 2003
From: ryan at tribug.org (Ryan Younce)
Date: Thu, 23 Oct 2003 04:19:09 -0400 (EDT)
Subject: docs/58413: kill(2) contains an error regarding sending SIGCONT
Message-ID: <20031023081909.C849911532@turing.vangyzen.net>


>Number:         58413
>Category:       docs
>Synopsis:       kill(2) contains an error regarding sending SIGCONT
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 23 01:00:27 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ryan Younce
>Release:        FreeBSD 5.1-BETA i386
>Organization:
>Environment:
System: FreeBSD turing.vangyzen.net 5.1-BETA FreeBSD 5.1-BETA #0: Tue May 6 12:07:36 GMT 2003 root at hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386

>Description:

The kill(2) manual page for CURRENT states "A single exception is the
signal SIGCONT, which may always be sent to any descendent of the current
process."

In CURRENT, however, this provision is false:  the process can send
SIGCONT to any other process in the caller's session (to align with POSIX).

Behavior has been tested, also reference:
p_cansignal() function in /sys/kern/kern_prot.c

>How-To-Repeat:

man 2 kill

>Fix:

Change sentence in question to:

	"A single exception is the signal SIGCONT, which may always be sent
	to any process with the same session ID as the caller."

or something similar.
>Release-Note:
>Audit-Trail:
>Unformatted:


From fox at vader.aacc.cc.md.us  Thu Oct 23 11:12:07 2003
From: fox at vader.aacc.cc.md.us (Michel Lavondes)
Date: Thu, 23 Oct 2003 07:11:59 -0400 (EDT)
Subject: No ssh or sshd online manpages?
Message-ID: <Pine.LNX.4.44.0310230700490.5367-100000@vader.aacc.edu>

(Mostly annoying, as I can read through the source of manpages imported
into the FreeBSD version I'm preparing to upgrade to.)

Trying to access the online manpages for ssh and sshd (any 4.x or 5.x 
version) with lynx2.8.4rel.1 gets me the following instead:

                                       FreeBSD Hypertext Man Pages: sshd
                 FreeBSD Hypertext Man Pages [littlelogo.gif]
   Man Page or Keyword Search: sshd________________ Submit Reset
   (*) Man [All Sections______________] [FreeBSD 4.8-stable_______]
   ( ) Apropos Keyword Search (all sections) [html__] Output format
   Index Page and Help | FAQ | Copyright
     _________________________________________________________________
Sorry, no data found for `sshd'.
You may look for other FreeBSD Search Services.

To reproduce:

lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
FreeBSD+4.8-stable&format=html

(same result with ssh and or other FreeBSD releases)

No clue as to what a fix may be.

System and or lynx config available on request.

-- 
Remember: i before e, except on Unix machines.


From setantae at submonkey.net  Thu Oct 23 11:27:46 2003
From: setantae at submonkey.net (Ceri Davies)
Date: Thu, 23 Oct 2003 12:27:37 +0100
Subject: a reminder to PR submitters
In-Reply-To: <20031022193218.GM96543@toxic.magnesium.net>
References: <Pine.LNX.4.44.0310220135110.4822-100000@pancho>
	<20031022193218.GM96543@toxic.magnesium.net>
Message-ID: <20031023112737.GD350@submonkey.net>

On Wed, Oct 22, 2003 at 03:32:18PM -0400, Adam Weinberger wrote:
> I'm cc'ing this to freebsd-doc and Ceri, resident bugmeister, as their
> input in this is important.
> 
> >> (10.22.2003 @ 0242 PST): Mark Linimon said, in 0.9K: <<
> > Please do not set the Confidential field on your PRs to "yes".
> > We really don't have a mechanism to deal with confidential
> > PRs in GNATS due to the fact that the database itself can be
> > replicated, via cvsup, to anyone's machine, and thus itself is
> > inherently insecure.  Setting this field to "yes" merely makes
> > your PR disappear into this limbo-category called "pending" which
> > is dark and scary and filled with big spiders and stuff :-)
> >> end of "a reminder to PR submitters" from Mark Linimon <<
> 
> There are a number of fields within GNATS that mean things to us (the
> committers) that don't make sense to submitters, and there are fields
> that have no use for us whatsoever.
> 
> Confidential
> 	This field is, as you have pointed out, useless to us, and
> 	simply causes the PR to disappear. The field should be removed
> 	from the send-pr interface, or some mechanism for handling
> 	confidential PRs should be introduced. I suggest the former.

These used to get spammed at core.  Whether they still do is unknown to
me at this point, but there was strong feeling that there wasn't much
point in this.  It would be pretty easy to remove it from send-pr if that's
what people want.

> Severity/Priority
> 	These are relatively redundant, and are simply mechanisms for
> 	people to artificially elevate the position of the PR in the
> 	search lists -- which, in my experience, causes them to be seen
> 	LAST.

I'd recommend that committers correct the priorities to something more
realistic when they deal with a PR.  Other than that, I'm not sure what
else we can do with these.

> Class
> 	Seriously. The classes in here make sense to us, because we're
> 	used to dealing with them. For ports, we need fields that
> 	indicate the following:
> 		* update/upgrade
> 		* fix/new functionality
> 		* error report
> 		* other

I mailed portmgr on September 18th asking them if they'd be interested in
something along these lines.  No response yet.

> Submitter-Id
> 	"current-users" doesn't mean a thing. Submitter-Id should be
> 	usable as "user" or "maintainer," depending upon who submits the
> 	PR. If a maintainer wishes to submit a PR for an update to a
> 	port she maintains, she should be able to choose
> 	Class:update/upgrade, and Submitter-Id:maintainer.

That's a good idea.

> Additionally, text should be added to the bracketed text in the blank
> send-pr template indicating the use of each section for docs/ports/www
> PRs:
> Description
> 	<precise description of the problem (multiple lines)>
> 	<for new ports, description of application>
> Fix
> 	<how to correct or work around the problem, if known (multiple lines)>
> 	<shar of new port, diffs for port/documentation updates>

That's also a good idea.

I'd invite any further discussion to continue on the bugbusters@ mailing list;
follow-ups set accordingly.

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031023/cb8d4225/attachment.sig>

From setantae at submonkey.net  Thu Oct 23 11:34:13 2003
From: setantae at submonkey.net (Ceri Davies)
Date: Thu, 23 Oct 2003 12:34:06 +0100
Subject: a reminder to PR submitters
In-Reply-To: <3F96E8EC.7010609@centtech.com>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
	<3F96E8EC.7010609@centtech.com>
Message-ID: <20031023113406.GE350@submonkey.net>

On Wed, Oct 22, 2003 at 03:30:36PM -0500, Eric Anderson wrote:
> Mark Linimon wrote:
> 
> >While these are all good points, a GNATS upgrade is in the
> >works, so there's little reason to try to fix the existing one.
> >IIRC des has been insistent on deprecating the severity/priority
> >fields (as you note, the data in them are 90%+ bogus).
> >
> >However, worse than all these problems is the fact that no
> >one has come up with code to reenable the web-based send-pr,
> >and IMHO that's a more important (but related) task to all
> >the above.
> >
> >Note that I'm not volunteering any patches to any of the
> >above at this time :-)
> >
> >Well, maybe I might for the templates, since they're pretty
> >busted, anwyays.
> 
> I'd be willing to work on a replacement for the web-send-pr cgi 
> program.  I looked at it a year or so ago, and got distracted by other 
> things. 
> 
> Can someone give me a list of "requirements" for the new program?

Don't spam the PR database.

As it happened, the open proxy checking that I added a year ago only
had a week to run before we turned it off altogether, so it may be that
it would be OK as it stands.

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031023/42a08162/attachment.sig>

From setantae at submonkey.net  Thu Oct 23 11:35:22 2003
From: setantae at submonkey.net (Ceri Davies)
Date: Thu, 23 Oct 2003 12:35:11 +0100
Subject: a reminder to PR submitters
In-Reply-To: <3F96F1F5.7040707@fillmore-labs.com>
References: <Pine.LNX.4.44.0310221519490.17050-100000@pancho>
	<3F96F1F5.7040707@fillmore-labs.com>
Message-ID: <20031023113511.GF350@submonkey.net>

On Wed, Oct 22, 2003 at 11:09:09PM +0200, Oliver Eikemeier wrote:
> Mark Linimon wrote:
> 
> >While these are all good points, a GNATS upgrade is in the
> >works, so there's little reason to try to fix the existing one.
> 
> Who is working on the upgrade?

Ditto.

(Although I have been looking at it locally, I haven't told anyone.
 Can you see me? ;-)

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031023/c0e771a5/attachment.sig>

From lars at domesjo.com  Thu Oct 23 13:30:20 2003
From: lars at domesjo.com (Lars Domesjö)
Date: 23 Oct 2003 13:22:16 -0000
Subject: docs/58425: Error in the manpage of pccbb(4)
Message-ID: <20031023132216.3706.qmail@acidjazz.net>


>Number:         58425
>Category:       docs
>Synopsis:       Error in the manpage of pccbb(4)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 23 06:30:17 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Lars Domesj?
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
-
>Environment:
System: FreeBSD acidjazz.net 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Sat Aug 16 12:21:07 CEST 2003 root at acidjazz.net:/usr/src/sys/i386/compile/acidjazz i386

	PII-350, FreeBSD 5.1, i386
>Description:
	The manpage of pccbb(4) says you should use device pccbb although
	what you really should use is device cbb.
>How-To-Repeat:
	man pccbb
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


From Alexander at Leidinger.net  Thu Oct 23 14:44:57 2003
From: Alexander at Leidinger.net (Alexander Leidinger)
Date: Thu, 23 Oct 2003 16:43:55 +0200
Subject: a reminder to PR submitters
In-Reply-To: <Pine.LNX.4.44.0310221934350.22984-100000@pancho>
References: <3F971F76.90308@ciam.ru>
	<Pine.LNX.4.44.0310221934350.22984-100000@pancho>
Message-ID: <20031023164355.106947a0.Alexander@Leidinger.net>

On Wed, 22 Oct 2003 19:46:34 -0500 (CDT)
Mark Linimon <linimon at lonesome.com> wrote:

> The code I am working on is a batch-based reminder list that
> would only go to a) people who do not have an @FreeBSD.org
> address (because they can be assigned the PR in GNATS and
> thus automatically reminded)

What if more than one committer is interested in getting such a mail?

Bye,
Alexander.

-- 
              To boldly go where I surely don't belong.

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7


From anderson at centtech.com  Thu Oct 23 14:46:34 2003
From: anderson at centtech.com (Eric Anderson)
Date: Thu, 23 Oct 2003 09:46:03 -0500
Subject: a reminder to PR submitters
In-Reply-To: <20031023164355.106947a0.Alexander@Leidinger.net>
References: <3F971F76.90308@ciam.ru>
	<Pine.LNX.4.44.0310221934350.22984-100000@pancho>
	<20031023164355.106947a0.Alexander@Leidinger.net>
Message-ID: <3F97E9AB.8060503@centtech.com>

Alexander Leidinger wrote:

>On Wed, 22 Oct 2003 19:46:34 -0500 (CDT)
>Mark Linimon <linimon at lonesome.com> wrote:
>
>  
>
>>The code I am working on is a batch-based reminder list that
>>would only go to a) people who do not have an @FreeBSD.org
>>address (because they can be assigned the PR in GNATS and
>>thus automatically reminded)
>>    
>>
>
>What if more than one committer is interested in getting such a mail?
>  
>

How about something like google news alerts -
You put in some keywords, and if those keywords are found, it sends you 
a link to that PR.

Eric

-- 
------------------------------------------------------------------
Eric Anderson	   Systems Administrator      Centaur Technology
All generalizations are false, including this one.
------------------------------------------------------------------



From blackend at freebsd.org  Thu Oct 23 17:00:15 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Thu, 23 Oct 2003 18:59:11 +0200
Subject: No ssh or sshd online manpages?
In-Reply-To: <Pine.LNX.4.44.0310230700490.5367-100000@vader.aacc.edu>
References: <Pine.LNX.4.44.0310230700490.5367-100000@vader.aacc.edu>
Message-ID: <20031023165911.GA575@nosferatu.blackend.org>

On Thu, Oct 23, 2003 at 07:11:59AM -0400, Michel Lavondes wrote:
> (Mostly annoying, as I can read through the source of manpages imported
> into the FreeBSD version I'm preparing to upgrade to.)
> 
> Trying to access the online manpages for ssh and sshd (any 4.x or 5.x 
> version) with lynx2.8.4rel.1 gets me the following instead:
> 
>                                        FreeBSD Hypertext Man Pages: sshd
>                  FreeBSD Hypertext Man Pages [littlelogo.gif]
>    Man Page or Keyword Search: sshd________________ Submit Reset
>    (*) Man [All Sections______________] [FreeBSD 4.8-stable_______]
>    ( ) Apropos Keyword Search (all sections) [html__] Output format
>    Index Page and Help | FAQ | Copyright
>      _________________________________________________________________
> Sorry, no data found for `sshd'.
> You may look for other FreeBSD Search Services.
> 
> To reproduce:
> 
> lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
> FreeBSD+4.8-stable&format=html
> 
> (same result with ssh and or other FreeBSD releases)
> 
> No clue as to what a fix may be.

Try:

http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0&manpath=OpenBSD+3.3&format=html

you have to use OpenBSD as OS.

Marc


From blackend at freebsd.org  Thu Oct 23 17:21:21 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Thu, 23 Oct 2003 19:20:29 +0200
Subject: No ssh or sshd online manpages?
In-Reply-To: <20031023165911.GA575@nosferatu.blackend.org>
References: <Pine.LNX.4.44.0310230700490.5367-100000@vader.aacc.edu>
	<20031023165911.GA575@nosferatu.blackend.org>
Message-ID: <20031023172029.GE575@nosferatu.blackend.org>

On Thu, Oct 23, 2003 at 06:59:11PM +0200, Marc Fonvieille wrote:
> 
> Try:
> 
> http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0&manpath=OpenBSD+3.3&format=html
> 
> you have to use OpenBSD as OS.
>

Ahah this one is funny :) I meant in the query :)

Marc


From bmah at freebsd.org  Thu Oct 23 18:07:37 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Thu, 23 Oct 2003 11:07:34 -0700
Subject: No ssh or sshd online manpages? 
In-Reply-To: <20031023172029.GE575@nosferatu.blackend.org> 
References: <Pine.LNX.4.44.0310230700490.5367-100000@vader.aacc.edu>
	<20031023165911.GA575@nosferatu.blackend.org>
	<20031023172029.GE575@nosferatu.blackend.org>
Message-ID: <200310231807.h9NI7YnB063346@intruder.kitchenlab.org>

If memory serves me right, Marc Fonvieille wrote:
> On Thu, Oct 23, 2003 at 06:59:11PM +0200, Marc Fonvieille wrote:
> > 
> > Try:
> > 
> > http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0&manpath=Op
> enBSD+3.3&format=html
> > 
> > you have to use OpenBSD as OS.
> >
> 
> Ahah this one is funny :) I meant in the query :)

I thought you were implying that our Web server runs one of the versions
of pf that supports OS detection.  :-)

Bruce.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 223 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031023/8317c077/attachment.sig>

From plexus at snafu.de  Thu Oct 23 18:12:48 2003
From: plexus at snafu.de (Oliver Fischer)
Date: Wed, 22 Oct 2003 19:02:09 +0200
Subject: DocBook version of "PMake - A Tutorial"
Message-ID: <3F96B811.5070205@snafu.de>

Hello!

In recent times I read the pmake tutorial very often. Unfortunately
there is no 'online' version of the tutorial. Is it possible to create a 
DocBook version? If yes, I would volunter for this work.

Regards,

Oliver Fischer


From sziszi at bsd.hu  Thu Oct 23 19:36:47 2003
From: sziszi at bsd.hu (Szilveszter Adam)
Date: Thu, 23 Oct 2003 21:36:50 +0200
Subject: DocBook version of "PMake - A Tutorial"
In-Reply-To: <3F96B811.5070205@snafu.de>
References: <3F96B811.5070205@snafu.de>
Message-ID: <20031023193649.GA48426@momo.buza.adamsfamily.xx>

Hello,

On Wed, Oct 22, 2003 at 07:02:09PM +0200, Oliver Fischer wrote:
> Hello!
> 
> In recent times I read the pmake tutorial very often. Unfortunately
> there is no 'online' version of the tutorial. Is it possible to create a 
> DocBook version? If yes, I would volunter for this work.

If you mean "is it technically possible to do this?" then the answer is
definitely yes. If you mean "is it permitted to do this?" then I think
the answer would be yes too. (it seems to be under the BSDL)

What needs to be done is: You take the source file (you can find it on
your FreeBSD system probably, under src/usr.bin/make/PSD.doc/) remove
the groff formatting, and mark up the text using DocBook tags. It could
possibly even be automated to a degree, although you would still need to
invest time for manual work as well.

If you feel like doing this, I think this would be welcome. For help
with DocBook, I recommend the docbook-tdg port, which installs the book:
DocBook: The Definitive Guide in electronic form.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary


From www at FreeBSD.org  Thu Oct 23 20:24:38 2003
From: www at FreeBSD.org (World Wide Web Owner)
Date: Thu, 23 Oct 2003 13:24:37 -0700 (PDT)
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200310232024.h9NKOb5g003159@www.freebsd.org>

===> doc/articles/dialup-firewall
===> doc/articles/diskless-x
===> doc/articles/euro
===> doc/articles/explaining-bsd
===> doc/articles/fbsd-from-scratch
===> doc/articles/filtering-bridges
===> doc/articles/fonts
===> doc/articles/formatting-media
===> doc/articles/freebsd-questions
===> doc/articles/hats
===> doc/articles/hubs
===> doc/articles/ipsec-must
===> doc/articles/laptop
===> doc/articles/java-tomcat
===> doc/articles/mh
===> doc/articles/multi-os
===> doc/articles/new-users
===> doc/articles/pam
===> doc/articles/pr-guidelines
===> doc/articles/problem-reports
===> doc/articles/programming-tools
===> doc/articles/pxe
===> doc/articles/releng
===> doc/articles/releng-packages
===> doc/articles/serial-uart
===> doc/articles/solid-state
===> doc/articles/storage-devices
===> doc/articles/vinum
===> doc/articles/vm-design
===> doc/articles/zip-drive
===> doc/books
===> doc/books/arch-handbook
/usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/doc/en_US.ISO8859-1/books/arch-handbook/../../../share/sgml/default.dsl -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images   -D /usr/obj/w/www/build/doc/en_US.ISO8859-1/books/arch-handbook -c /w/www/build/doc/en_US.ISO8859-1/books/arch-handbook/../../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/doc/en_US.ISO8859-1/books/arch-handbook/../../../share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/docbook/catalog -c /usr/local/share/sgml/jade/catalog -t sgml /w/www/build/doc/en_US.ISO8859-1/books/arch-handbook/book.sgml
/usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml:151:27:E: general entity "mptable" not defined and no default entity
*** Error code 1

Stop in /w/www/build/doc/en_US.ISO8859-1/books/arch-handbook.
*** Error code 1

Stop in /w/www/build/doc/en_US.ISO8859-1/books.
*** Error code 1

Stop in /w/www/build/doc/en_US.ISO8859-1.
*** Error code 1

Stop in /w/www/build/www/en/doc.
*** Error code 1

Stop in /w/www/build/www/en.
       86.95 real        66.90 user         4.09 sys


From fox at vader.aacc.cc.md.us  Thu Oct 23 20:32:45 2003
From: fox at vader.aacc.cc.md.us (Michel Lavondes)
Date: Thu, 23 Oct 2003 16:32:32 -0400 (EDT)
Subject: No ssh or sshd online manpages?
In-Reply-To: <20031023165911.GA575@nosferatu.blackend.org>
Message-ID: <Pine.LNX.4.44.0310231611380.8146-100000@vader.aacc.edu>

On Thu, 23 Oct 2003, Marc Fonvieille wrote:

> On Thu, Oct 23, 2003 at 07:11:59AM -0400, Michel Lavondes wrote:
> > 
> > lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
> > FreeBSD+4.8-stable&format=html
> 
> Try:
> 
> http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0
> &manpath=OpenBSD+3.3&format=html
> 
> you have to use OpenBSD as OS.

Hmm, I'm not sure what's the rationale for this. For all I know, there may 
be copyright, license, policy, or other non-technical reasons for doing 
this. However, it looks inconsistent with the way other imported stuff is 
handled. Eg, to look at the newstyle rc(8) manpage, I can specify I'm 
interested in FreeBSD5.1 instead of asking for NetBSD manpages.

What am I missing? (besides humility, that is. :-) )

-- 
Remember: i before e, except on Unix machines.


From kensmith at FreeBSD.org  Thu Oct 23 21:50:17 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Thu, 23 Oct 2003 14:50:15 -0700 (PDT)
Subject: docs/58413: kill(2) contains an error regarding sending SIGCONT
Message-ID: <200310232150.h9NLoFDa043812@freefall.freebsd.org>

Synopsis: kill(2) contains an error regarding sending SIGCONT

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Thu Oct 23 14:49:40 PDT 2003
Responsible-Changed-Why: 

I'll give this a try.


http://www.freebsd.org/cgi/query-pr.cgi?pr=58413


From home at clef.at  Fri Oct 24 00:29:43 2003
From: home at clef.at (Harald Muehlboeck)
Date: 24 Oct 2003 02:29:48 +0200
Subject: broken link to LPRng site
Message-ID: <86u15zscjn.fsf@tuha.clef.at>

Hello,

In the Freebsd Handbook, chapter 11.6 "Alternatives to the Standard
Spooler"
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-lpd-alternatives.html
the link to the "main site for LPRng"
<http://www.astart.com/lprng/LPRng.html> seems to be broken and should
probalby be replaced by <http://www.lprng.com>

regards,
Harald Muehlboeck


From lexxx_h at yahoo.com.au  Fri Oct 24 04:30:24 2003
From: lexxx_h at yahoo.com.au (Lex Hider)
Date: Fri, 24 Oct 2003 14:32:12 +1000
Subject: Babe in the Woods: A Linux User Migrates to FreeBSD updated
Message-ID: <200310241432.12400.lexxx_h@yahoo.com.au>

Hi,
for press page.
There is a 2nd part to the babe in the woods article.
http://www.ofb.biz/modules.php?name=News&file=article&sid=269
Lex.


From roam at ringlet.net  Fri Oct 24 06:31:34 2003
From: roam at ringlet.net (Peter Pentchev)
Date: Fri, 24 Oct 2003 09:31:29 +0300
Subject: broken link to LPRng site
In-Reply-To: <86u15zscjn.fsf@tuha.clef.at>
References: <86u15zscjn.fsf@tuha.clef.at>
Message-ID: <20031024063129.GA58429@straylight.oblivion.bg>

On Fri, Oct 24, 2003 at 02:29:48AM +0200, Harald Muehlboeck wrote:
> Hello,
> 
> In the Freebsd Handbook, chapter 11.6 "Alternatives to the Standard
> Spooler"
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-lpd-alternatives.html
> the link to the "main site for LPRng"
> <http://www.astart.com/lprng/LPRng.html> seems to be broken and should
> probalby be replaced by <http://www.lprng.com>

I just committed a change to the handbook referencing
http://www.lprng.org/.  The change will show up on the FreeBSD website
after the next automated build, probably within 12-24 hours.  Thanks for
the notification!

G'luck,
Peter

-- 
Peter Pentchev	roam at ringlet.net    roam at sbnd.net    roam at FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
I am jealous of the first word in this sentence.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031024/6d36f3a2/attachment.sig>

From mathwire at wolfram.com  Fri Oct 24 06:45:30 2003
From: mathwire at wolfram.com (Wolfram Research)
Date: Thu, 23 Oct 2003 13:36:00 -0500 (CDT)
Subject: MATHwire: Information for Mathematica Users
Message-ID: <20031023183600.D717225FD5@mercury.wolfram.com>

October 2003

---------------
Announcements
---------------

Download Mathematica and other Wolfram Research products
immediately. The Wolfram web store newly supports worldwide
direct downloads to your computer for many products...
http://store.wolfram.com

Try Mathematica or CalculationCenter for free! Fully functional,
time-limited trial downloads are now available...
http://www.wolfram.com/products/mathematica/trial.cgi
http://www.wolfram.com/products/calculationcenter/trial.cgi

gridMathematica 1.1 brings the power of Mathematica 5 to the grid
to provide the best high-performance computing environment...
http://www.wolfram.com/products/gridmathematica

With the new semester and annual editions of Mathematica for
Students, students can gain the Mathematica advantage for one
class (up to six months) or for one year. Download today for less
than the cost of most textbooks...
http://www.wolfram.com/timedstudent.html

The new Mathematica Homeschool Kit makes math and science
education in the home come alive...
http://www.wolfram.com/products/homeschoolkit

Advanced Modern Control supplements the Control System
Professional application package suite, providing methods for
modern controller design, model reduction, and system
evaluation...
http://www.wolfram.com/products/applications/amc

Wolfram Education Group's fall course calendar includes training
courses throughout the U.S. and abroad...
http://www.wolfram.com/weg/calendar.cgi

Mark your calendars now for the Wolfram Technology Conference to
be held October 21-23, 2004! Submit suggestions and
recommendations for session topics and session leaders to:
conference-info at wolfram.com


--------------------
New in Print
--------------------

"Computing with Mathematica" by Hartmut F. and Margret H. Hoft...
http://store.wolfram.com/view/book/ISBN0123516609.str

"Mathematica Computer Guide" by E. Kreyszig and E. J.
Norminton...
http://store.wolfram.com/view/book/ISBN0471386693.str

"Mathematical Methods Using Mathematica: For Students of Physics
and Related Fields" by Sadri Hassani...
http://store.wolfram.com/view/book/ISBN0387955232.str

"Modelling Metabolism with Mathematica" by Peter J. Mulquiney and
Philip W. Kuchel...
http://store.wolfram.com/view/book/ISBN0849314682.str


------------------
Did you know...?
------------------

...you can solve large-scale linear programming problems in
Mathematica 5 using an efficient interior-point method. Similar
functionality has until now been available only in expensive
special-purpose packages...
http://www.wolfram.com/mathematica/newin5/performance/largescalelinear.html

...in Mathematica you can evaluate selected expressions in place
with Ctrl-Shift-Enter (Windows and Unix) or Command-Return
(Macintosh)...
http://documents.wolfram.com/v5/FrontEnd/MenuCommands/KernelMenu/Evaluation/EvaluationEvaluateInPlace.html


----------------
In the news...
----------------

Mathematica 5 for Linux on Intel Itanium 2 unites high-
performance technologies to provide a native 64-bit environment
for intensive computing applications...
http://www.wolfram.com/news/itanium2.html

"[T]he numeric improvements are so spectacular that most current
Mathematica users will want to upgrade," says PC Magazine about
Mathematica 5...
http://www.pcmag.com/article2/0,4149,1217139,00.asp

See what others are saying about Wolfram Research and Mathematica
5 on our new recent media coverage page...
http://www.wolfram.com/news/coverage.html


-----------------

If you wish to be removed from the MATHwire mailing list, please
visit:
http://www.wolfram.com/unsubscribe/?email=freebsd-doc at freebsd.org&mid=MW1003

If you wish to be removed from the Wolfram Research mailing list,
please visit:
http://www.wolfram.com/unsubscribe/?email=freebsd-doc at freebsd.org&mid=PMmw10

If you wish to change the email address we have on file for you,
please visit:
http://www.wolfram.com/emailchange/?email=freebsd-doc at freebsd.org&mid=MW1003

-----------------

This message was sent to <freebsd-doc at freebsd.org>.


From priit.piipuu at mail.ee  Fri Oct 24 11:15:04 2003
From: priit.piipuu at mail.ee (Priit Piipuu)
Date: Fri, 24 Oct 2003 14:14:18 +0300
Subject: DocBook version of "PMake - A Tutorial"
In-Reply-To: <3F96B811.5070205@snafu.de>
References: <3F96B811.5070205@snafu.de>
Message-ID: <3F99098A.80607@mail.ee>

Oliver Fischer wrote:

> Hello!
>
> In recent times I read the pmake tutorial very often. Unfortunately
> there is no 'online' version of the tutorial. Is it possible to create 
> a DocBook version? If yes, I would volunter for this work.


This is already done, look at http://www.ten15.org/docs/make/
Note, that there may be differencies between PMake in FreeBSD and PMake
attached with TenDRA.





From kensmith at FreeBSD.org  Fri Oct 24 19:38:51 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Fri, 24 Oct 2003 12:38:50 -0700 (PDT)
Subject: docs/35607: dump(1) page needs discussion of scary
	error-ignoring bug.
Message-ID: <200310241938.h9OJcoLb040993@freefall.freebsd.org>

Synopsis: dump(1) page needs discussion of scary error-ignoring bug.

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Fri Oct 24 12:34:58 PDT 2003
Responsible-Changed-Why: 

Sorry for the delay.  I'll try to take care of this.  FYI, I think
the code seems to say dump will stop, asking for operator intervention,
only after 32 bread errors but it prints warning messages about all
bread errors it encounters while running.


http://www.freebsd.org/cgi/query-pr.cgi?pr=35607


From kensmith at FreeBSD.org  Fri Oct 24 19:39:52 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Fri, 24 Oct 2003 12:39:52 -0700 (PDT)
Subject: docs/35602: dump(8)/restore(8) pages don't explain "active file
	systems".
Message-ID: <200310241939.h9OJdqNj041066@freefall.freebsd.org>

Synopsis: dump(8)/restore(8) pages don't explain "active file systems".

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Fri Oct 24 12:39:12 PDT 2003
Responsible-Changed-Why: 

Sorry for the delay.  I'll try to take care of this.


http://www.freebsd.org/cgi/query-pr.cgi?pr=35602


From peter at k6.xs4all.nl  Fri Oct 24 19:51:52 2003
From: peter at k6.xs4all.nl (Peter Terpstra)
Date: Fri, 24 Oct 2003 21:51:48 +0200 (CEST)
Subject: Kernelpath & arplookup.
Message-ID: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>

Dear readers,

A few weeks ago I installed FreeBSD an I liked it very much, its easier than
Linux I think. No problems with installing/configuring  X or ssh or Postfix.

My questions:
I compiled a new (lighter) kernel and it works great but I found the path
mentioned in dmesg or `uname -v' a bit strange, its the place of compile:

peter at k7:~:0>uname -v
FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
root at k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6

Does that mean I cannot remove the old kernel-source?
I did a `configure MYKERNEL-K6;make depend;make; make install' just as
mentioned in the on-line FreeBSD handbook.
Why isn't the path something with /boot/kernel?

arp:
Frequently I get this message on the first console:
arplookup 213.84.240.105 failed: host is not on local network

I searched the inter-net, but I did not found a satisfying answer.
213.84.240.105 is hanging on the inter-net, an FreeBSD has a local IP-adres.
So why this arplookup? What causes this lookup?

With kind regards,

	Peter Terpstra

-- 
Date & time: vrijdag 24 oktober : 21 uur, 10 minuten en 17 seconden.
Uptime:  9:10pm  up 9 days, 21:40,  2 users,  load average: 0.63, 0.27, 0.16
https://k6.xs4all.nl  mailto:peter at k6.xs4all.nl  http://www.votenowar.org


From m.seaman at infracaninophile.co.uk  Fri Oct 24 20:14:15 2003
From: m.seaman at infracaninophile.co.uk (Matthew Seaman)
Date: Fri, 24 Oct 2003 21:14:02 +0100
Subject: Kernelpath & arplookup.
In-Reply-To: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
References: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
Message-ID: <20031024201402.GA54905@happy-idiot-talk.infracaninophile.co.uk>

On Fri, Oct 24, 2003 at 09:51:48PM +0200, Peter Terpstra wrote:

> I compiled a new (lighter) kernel and it works great but I found the path
> mentioned in dmesg or `uname -v' a bit strange, its the place of compile:
> 
> peter at k7:~:0>uname -v
> FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
> root at k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6
> 
> Does that mean I cannot remove the old kernel-source?
> I did a `configure MYKERNEL-K6;make depend;make; make install' just as
> mentioned in the on-line FreeBSD handbook.
> Why isn't the path something with /boot/kernel?

As you say, that isn't the location in the file system where the
kernel is installed: it's where the kernel was compiled.  To find
where the kernel was booted from try:

    % sysctl kern.bootfile

You can certainly clear out your kernel compile directory without
affecting the operation of the system.

While the way you compiled the kernel certainly works, it's actually
the 'old' way.  Nowadays the commonest way to build and install a
kernel is:

    # cd /usr/src
    # make buildkernel KERNCONF=MYKERNEL-K6
    # make installkernel KERNCONF=MYKERNEL-K6

In thins case, you'll find that the kernel compile path is
/usr/obj/usr/src/sys/MYKERNEL-K6

As to quite why it's like this I'm not sure.  I think it's one of
those things that has always been that way, and because it's been like
that for so long no one is going to change it now.
 
> arp:
> Frequently I get this message on the first console:
> arplookup 213.84.240.105 failed: host is not on local network

Yes.  This isn't necessarily an error.  All it means is that there is
a host on the same physical network segment but with an IP number that
belongs to a different network than your machine.  If this isn't a
misconfiguration then you can suppress the error message by:

    # sysctl net.link.ether.inet.log_arp_wrong_iface 0

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031024/fcbfbd88/attachment.sig>

From sziszi at bsd.hu  Fri Oct 24 20:30:03 2003
From: sziszi at bsd.hu (Szilveszter Adam)
Date: Fri, 24 Oct 2003 22:30:09 +0200
Subject: Kernelpath & arplookup.
In-Reply-To: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
References: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
Message-ID: <20031024203009.GB13183@momo.buza.adamsfamily.xx>

Hello,

On Fri, Oct 24, 2003 at 09:51:48PM +0200, Peter Terpstra wrote:
> A few weeks ago I installed FreeBSD an I liked it very much, its easier than
> Linux I think. No problems with installing/configuring  X or ssh or Postfix.

I think everybody here is glad to hear that. I hope you will have many
pleasant experinces in the land of FreeBSD :-)

> My questions:
> I compiled a new (lighter) kernel and it works great but I found the path
> mentioned in dmesg or `uname -v' a bit strange, its the place of compile:
> 
> peter at k7:~:0>uname -v
> FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
> root at k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6

Yes, your observation is correct.

> Does that mean I cannot remove the old kernel-source?

No, you may be confused a bit here. The "path" mentioned in uname is
just there so that you know when and from what kernel config file you
compiled your kernel. But your kernel always lives in /kernel if you are
on FreeBSD version 4.x, or under /boot/kernel/kernel if you are under
version 5.x. You can delete the kernel source if you do not need it, it
is not required for running. You can also simply use "make clean" in
your kernel compile dir after you know that your new kernel performs as
it should, and thus save the disk space, but conserve the config file
with your settings, so that you can reuse it later.

> I did a `configure MYKERNEL-K6;make depend;make; make install' just as
> mentioned in the on-line FreeBSD handbook.
> Why isn't the path something with /boot/kernel?

It is, if you look at your /var/log/messages, it will even tell it to
you upon each boot.

> arp:
> Frequently I get this message on the first console:
> arplookup 213.84.240.105 failed: host is not on local network
> 
> I searched the inter-net, but I did not found a satisfying answer.
> 213.84.240.105 is hanging on the inter-net, an FreeBSD has a local IP-adres.
> So why this arplookup? What causes this lookup?

This has come up a couple of times lately, but I do not know the answer
off-hand. It may have something to do with your host having more than
one network card and some packets not arriving on the interface FreeBSD
would expect them to.

But really, I am not sure. Maybe someone else can tell.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary


From peter at k6.xs4all.nl  Fri Oct 24 21:39:05 2003
From: peter at k6.xs4all.nl (Peter Terpstra)
Date: Fri, 24 Oct 2003 23:39:02 +0200 (CEST)
Subject: Kernelpath & arplookup.
In-Reply-To: <20031024201402.GA54905@happy-idiot-talk.infracaninophile.co.uk>
References: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
 <20031024201402.GA54905@happy-idiot-talk.infracaninophile.co.uk>
Message-ID: <Pine.LNX.4.58.0310242306060.2715@k6.xs4all.nl>

In <20031024201402.GA54905 at happy-idiot-talk.infracaninophile.co.uk>,
op de datum 2003-10-24 om 21:14, Matthew Seaman schreef:

>> I did a `configure MYKERNEL-K6;make depend;make; make install' just as
>> mentioned in the on-line FreeBSD handbook.
>> Why isn't the path something with /boot/kernel?
>
>As you say, that isn't the location in the file system where the
>kernel is installed: it's where the kernel was compiled.  To find
>where the kernel was booted from try:
>
>    % sysctl kern.bootfile

kern.bootfile: /boot/kernel/kernel

seems to bee good.

>You can certainly clear out your kernel compile directory without
>affecting the operation of the system.
>
>While the way you compiled the kernel certainly works, it's actually
>the 'old' way.  Nowadays the commonest way to build and install a
>kernel is:
>
>    # cd /usr/src
>    # make buildkernel KERNCONF=MYKERNEL-K6
>    # make installkernel KERNCONF=MYKERNEL-K6
>
>In thins case, you'll find that the kernel compile path is
>/usr/obj/usr/src/sys/MYKERNEL-K6
>
>As to quite why it's like this I'm not sure.  I think it's one of
>those things that has always been that way, and because it's been like
>that for so long no one is going to change it now.

Ah, thanks.

>> Frequently I get this message on the first console:
>> arplookup 213.84.240.105 failed: host is not on local network

>Yes.  This isn't necessarily an error.  All it means is that there is
>a host on the same physical network segment but with an IP number that
>belongs to a different network than your machine.  If this isn't a
>misconfiguration then you can suppress the error message by:

>    # sysctl net.link.ether.inet.log_arp_wrong_iface 0


This:
root at k7:~:0>sysctl net.link.ether.inet.log_arp_wrong_iface=0
net.link.ether.inet.log_arp_wrong_iface: 1 -> 0

seems to work.

With kind regards,

	Peter Terpstra

-- 
Date & time: vrijdag 24 oktober : 23 uur, 06 minuten en 06 seconden.
Uptime: 11:06pm  up 9 days, 23:36,  2 users,  load average: 0.00, 0.04, 0.06
https://k6.xs4all.nl  mailto:peter at k6.xs4all.nl  http://www.votenowar.org


From kensmith at cse.Buffalo.EDU  Sat Oct 25 01:17:49 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Fri, 24 Oct 2003 21:17:46 -0400
Subject: RFC - OSI Course Starter Kit...
Message-ID: <20031025011746.GA7080@electra.cse.Buffalo.EDU>


Marc has been helping me figure out whether bothering to do this is
worthwhile.  So far the answer is maybe.  ;-)  Before I follow through
with the work that packaging this up would be (I can find other things
to do if this isn't worthwhile) I'd like to ask you folks to see if
this is useful.

I have the starts of what could be an Article on the Web site that
would basically be an Instructor's Manual for setting up a lab to be
used for a 2nd semester course teaching Operating Systems using
(surprise...) FreeBSD as the base system.  The starts of it are
at http://www.cse.buffalo.edu/~kensmith/FreeBSD/crashlab.html though
it needs some more work.  Marc suggested adding more details about
exactly what it takes to get the server set up for NFS and that
sort of thing.

Along with that there is a Lab Manual, equally in need of work but what
I used for the Spring 2003 semester is at
http://www.cse.buffalo.edu/~kensmith/FreeBSD/Lab_Manual.html.

These materials along with McKusick's book he's currently working on
should make setting up and teaching a kernel hacking class fairly
straighforward.

I was thinking about the crashlab.html becoming an Article on the Web
site, and the Lab Manual being provided as an OpenOffice document
because they'd need to be able to edit it (they wouldn't have the same
machine names I use, would probably have their own additions to the
Lab procedures, etc...).

Thoughts?  Is it worth doing?  Should it be done, but done differently?
Any suggestions about what to add other than more details on how to
configure the lab in the Instructors' Manual?

Thanks.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From linimon at FreeBSD.org  Sat Oct 25 03:58:09 2003
From: linimon at FreeBSD.org (Mark Linimon)
Date: Fri, 24 Oct 2003 20:58:08 -0700 (PDT)
Subject: docs/41761: Update for /ru/internal/ part of site
Message-ID: <200310250358.h9P3w8gg091679@freefall.freebsd.org>

Synopsis: Update for /ru/internal/ part of site

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Fri Oct 24 20:56:03 PDT 2003
State-Changed-Why: 
Closed by submitter request to cvs-doc and doc-committers
on 10/21/03 11:25 am.  (Changes have already been incorporated).


Responsible-Changed-From-To: freebsd-doc->linimon
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Oct 24 20:56:03 PDT 2003
Responsible-Changed-Why: 
Closed by submitter request to cvs-doc and doc-committers
on 10/21/03 11:25 am.  (Changes have already been incorporated).

http://www.freebsd.org/cgi/query-pr.cgi?pr=41761


From wmoran at potentialtech.com  Fri Oct 24 20:10:00 2003
From: wmoran at potentialtech.com (Bill Moran)
Date: Fri, 24 Oct 2003 16:09:58 -0400
Subject: Kernelpath & arplookup.
In-Reply-To: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
References: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
Message-ID: <3F998716.3040300@potentialtech.com>

[I'm moving this to questions at freebsd.org, because that is the correct list
for this type of question]

Peter Terpstra wrote:
> Dear readers,
> 
> A few weeks ago I installed FreeBSD an I liked it very much, its easier than
> Linux I think. No problems with installing/configuring  X or ssh or Postfix.
> 
> My questions:
> I compiled a new (lighter) kernel and it works great but I found the path
> mentioned in dmesg or `uname -v' a bit strange, its the place of compile:
> 
> peter at k7:~:0>uname -v
> FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
> root at k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6
> 
> Does that mean I cannot remove the old kernel-source?

No.

> I did a `configure MYKERNEL-K6;make depend;make; make install' just as
> mentioned in the on-line FreeBSD handbook.
> Why isn't the path something with /boot/kernel?

Because it's the path of your kernel config file.  The actual, compiled
kernel is always in /boot/kernel, so it's not really mentioned.

> arp:
> Frequently I get this message on the first console:
> arplookup 213.84.240.105 failed: host is not on local network

This means your network is configured strangely, although a lot of ISPs
seem to think this is the way to do it.

> I searched the inter-net, but I did not found a satisfying answer.
> 213.84.240.105 is hanging on the inter-net, an FreeBSD has a local IP-adres.
> So why this arplookup? What causes this lookup?

You have computers on your hub that have a network number that doesn't
jive with the IP/netmask you've assigned to the network card.  If you
don't care, you can ignore the messages.  All it means is that ARP was
not able to turn the IP address into a MAC address.

I believe there is a way to disable these messages, but I don't remember
for sure.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com


From hmp at FreeBSD.org  Sat Oct 25 16:06:32 2003
From: hmp at FreeBSD.org (Hiten Pandya)
Date: Sat, 25 Oct 2003 09:06:31 -0700 (PDT)
Subject: docs/58425: Error in the manpage of pccbb(4)
Message-ID: <200310251606.h9PG6Vah038442@freefall.freebsd.org>

Synopsis: Error in the manpage of pccbb(4)

State-Changed-From-To: open->closed
State-Changed-By: hmp
State-Changed-When: Sat Oct 25 09:06:15 PDT 2003
State-Changed-Why: 
This has been fixed in HEAD branch.  Thanks!


http://www.freebsd.org/cgi/query-pr.cgi?pr=58425


From maneo at bsdpro.com  Sun Oct 26 01:50:24 2003
From: maneo at bsdpro.com (Christian S.J.Peron)
Date: 26 Oct 2003 01:44:56 -0000
Subject: docs/58546: [patch] document how system security levels impact klds
Message-ID: <20031026014456.41710.qmail@staff.seccuris.com>


>Number:         58546
>Category:       docs
>Synopsis:       [patch] document how system security levels impact klds
>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 Oct 25 18:50:20 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Christian S.J. Peron
>Release:        FreeBSD 4.8-RELEASE-p13 i386
>Organization:
>Environment:
System: FreeBSD movl 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 #1: Sat Oct 25 16:45:55 UTC 2003 cperon at movl:/usr/src/sys/compile/STAFF i386


	
>Description:

The kld(4) manual page does not document how system
security levels can impact the loading and unloadng of
kernel modules.


	
>How-To-Repeat:
N/A
>Fix:

--- share/man/man4/kld.4.old	Sat Oct 25 19:38:06 2003
+++ share/man/man4/kld.4	Sat Oct 25 19:57:57 2003
@@ -88,6 +88,10 @@
 .Xr kldstat 8
 program is used to check the status of the modules currently loaded into the
 system.
+.Pp
+Kernel modules may only be loaded or unloaded if the system security level
+.Dq kern.securelevel
+is less than one. 
 .Sh "MODULE TYPES"
 .Bl -ohang
 .It Em "Device Driver modules"
@@ -125,7 +129,8 @@
 .Xr devd 8 ,
 .Xr kldload 8 ,
 .Xr kldstat 8 ,
-.Xr kldunload 8
+.Xr kldunload 8 ,
+.Xr sysctl 8
 .Sh BUGS
 If a module B, is dependent on another module A, but is not compiled with
 module A as a dependency, then
>Release-Note:
>Audit-Trail:
>Unformatted:


From kensmith at FreeBSD.org  Sun Oct 26 02:30:29 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Sat, 25 Oct 2003 19:30:28 -0700 (PDT)
Subject: docs/58546: [patch] document how system security levels impact
	klds
Message-ID: <200310260230.h9Q2USvg022495@freefall.freebsd.org>

Synopsis: [patch] document how system security levels impact klds

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Sat Oct 25 19:29:12 PDT 2003
Responsible-Changed-Why: 

I'll do this one, I recently hunted down who needs to review security
related kernel stuff for another PR.


http://www.freebsd.org/cgi/query-pr.cgi?pr=58546


From www at FreeBSD.org  Sun Oct 26 10:38:22 2003
From: www at FreeBSD.org (World Wide Web Owner)
Date: Sun, 26 Oct 2003 02:38:21 -0800 (PST)
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200310261038.h9QAcLt9086454@www.freebsd.org>

===> ../ja/releases/4.6.2R
/w/www/build/www/ja/releases/4.6.2R/../../../ja/prehtml -revcheck "../.." "releases/4.6.2R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.6.2R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/4.7R
/w/www/build/www/ja/releases/4.7R/../../../ja/prehtml -revcheck "../.." "releases/4.7R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.7R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/4.7R/../../../ja/prehtml -revcheck "../.." "releases/4.7R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.7R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/4.8R
===> ../ja/releases/5.0R
/w/www/build/www/ja/releases/5.0R/../../../ja/prehtml -revcheck "../.." "releases/5.0R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.0R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/5.0R/../../../ja/prehtml -revcheck "../.." "releases/5.0R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.0R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/5.1R
/w/www/build/www/ja/releases/5.1R/../../../ja/prehtml -revcheck "../.." "releases/5.1R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.1R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/5.1R/../../../ja/prehtml -revcheck "../.." "releases/5.1R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.1R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/smp
/w/www/build/www/ja/smp/../../ja/prehtml -revcheck ".." "smp"  index.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/smp > index.html ||  (/bin/rm -f index.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  index.html
*** Error code 1 (ignored)
===> ../ja/conspectus
===> ../ja/ports
/usr/bin/touch packages.exists
/bin/rm -f *.sgml
/usr/bin/perl5 /w/www/build/www/ja/ports/portindex INDEX /w/www/build/www/ja/ports
echo DOCS= *.sgml > Makefile.gen
cd /w/www/build/www/ja/ports;  make  -f /w/www/build/www/ja/ports/Makefile.inc0 all
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  index.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/ports > index.html ||  (/bin/rm -f index.html && false)
/usr/local/bin/sgmlnorm:<OSFD>0:13:4:E: end tag for "UL" which is not finished
*** Error code 1

Stop in /w/www/build/www/ja/ports.
*** Error code 1

Stop in /w/www/build/www/ja/ports.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/ja.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/en.
     4452.55 real      2596.82 user       213.32 sys


From www at FreeBSD.org  Sun Oct 26 10:38:22 2003
From: www at FreeBSD.org (World Wide Web Owner)
Date: Sun, 26 Oct 2003 02:38:21 -0800 (PST)
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200310261038.h9QAcLlH086446@www.freebsd.org>

===> ../ja/releases/4.6.2R
/w/www/build/www/ja/releases/4.6.2R/../../../ja/prehtml -revcheck "../.." "releases/4.6.2R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.6.2R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/4.7R
/w/www/build/www/ja/releases/4.7R/../../../ja/prehtml -revcheck "../.." "releases/4.7R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.7R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/4.7R/../../../ja/prehtml -revcheck "../.." "releases/4.7R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/4.7R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/4.8R
===> ../ja/releases/5.0R
/w/www/build/www/ja/releases/5.0R/../../../ja/prehtml -revcheck "../.." "releases/5.0R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.0R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/5.0R/../../../ja/prehtml -revcheck "../.." "releases/5.0R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.0R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/releases/5.1R
/w/www/build/www/ja/releases/5.1R/../../../ja/prehtml -revcheck "../.." "releases/5.1R"  announce.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.1R > announce.html ||  (/bin/rm -f announce.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  announce.html
*** Error code 1 (ignored)
/w/www/build/www/ja/releases/5.1R/../../../ja/prehtml -revcheck "../.." "releases/5.1R"  relnotes.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/releases/5.1R > relnotes.html ||  (/bin/rm -f relnotes.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  relnotes.html
===> ../ja/smp
/w/www/build/www/ja/smp/../../ja/prehtml -revcheck ".." "smp"  index.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/smp > index.html ||  (/bin/rm -f index.html && false)
/usr/local/bin/tidy -i -m -raw -preserve -f /dev/null -asxml  index.html
*** Error code 1 (ignored)
===> ../ja/conspectus
===> ../ja/ports
/usr/bin/touch packages.exists
/bin/rm -f *.sgml
/usr/bin/perl5 /w/www/build/www/ja/ports/portindex INDEX /w/www/build/www/ja/ports
echo DOCS= *.sgml > Makefile.gen
cd /w/www/build/www/ja/ports;  make  -f /w/www/build/www/ja/ports/Makefile.inc0 all
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'  index.sgml |  /usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d  -c /usr/local/share/sgml/html/catalog -D /w/www/build/www/ja/ports > index.html ||  (/bin/rm -f index.html && false)
/usr/local/bin/sgmlnorm:<OSFD>0:13:4:E: end tag for "UL" which is not finished
*** Error code 1

Stop in /w/www/build/www/ja/ports.
*** Error code 1

Stop in /w/www/build/www/ja/ports.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/ja.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/en.
     4452.55 real      2596.82 user       213.32 sys


From pauline.webermv at new.billboard.cz  Sun Oct 26 13:08:22 2003
From: pauline.webermv at new.billboard.cz (Pauline Weber)
Date: Mon, 27 Oct 2003 04:17:05 +0000
Subject: slcchqherp
Message-ID: <1e3601c39c41$978ae7aa$82bd4768@pjkvfkb>





From tms2 at mail.ptd.net  Sun Oct 26 14:55:32 2003
From: tms2 at mail.ptd.net (T.M. Sommers)
Date: Sun, 26 Oct 2003 09:55:28 -0500
Subject: typo in elf(5)
Message-ID: <3F9BE060.1000305@mail.ptd.net>

In elf(5), in the description of st_shndx, "Every symbol table entry 
is ``defined'' in relation to some action." should read "Every symbol 
table entry is ``defined'' in relation to some section."




From god at rn-re142b10.uwaterloo.ca  Sun Oct 26 18:55:09 2003
From: god at rn-re142b10.uwaterloo.ca (Yonas)
Date: Sun, 26 Oct 2003 13:55:41 -0500
Subject: Installing Maple
Message-ID: <20031026185541.GA88463@rn-re142b10.uwaterloo.ca>

When installing Maple 8 ("Linux Single User Installation" according to
their installation guide) on FreeBSD, I only had to follow step 4.
Nothing else was needed to get it running properly (it asks for the
serial number during install, as well).

Maybe a note could/should be added to the handbook that step 2,3, and
5 are not needed if using Maple 8. I haven't tested this on any other
version of Maple.

uname:
FreeBSD rn-re142b10 5.1-CURRENT-20031010-JPSNAP FreeBSD 5.1-CURRENT-20031010-JPSNAP #1: Sat Oct 25 18:59:20 EDT 2003     yonas at rn-re142b10:/usr/src/sys/i386/compile/LAPTOP  i386

Thanks,
Yonas


From kensmith at cse.Buffalo.EDU  Sun Oct 26 22:30:46 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Sun, 26 Oct 2003 17:30:44 -0500
Subject: Darwin...
Message-ID: <20031026223044.GA13291@electra.cse.Buffalo.EDU>


There are places on the Web site that list other related projects (NetBSD,
OpenBSD, etc.).  Does anyone object to adding Darwin, probably the site
http://www.opendarwin.org?  if I was to do it are there others that
should be added?  It's the only other stable project with BSD roots I'm aware
of but I don't "get out" much...

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From maneo at bsdpro.com  Mon Oct 27 01:30:17 2003
From: maneo at bsdpro.com (Chris S.J.Peron)
Date: 27 Oct 2003 01:20:53 -0000
Subject: docs/58586: [patch] ng_one2many interface status requirements
Message-ID: <20031027012053.46047.qmail@staff.seccuris.com>


>Number:         58586
>Category:       docs
>Synopsis:       [patch] ng_one2many interface status requirements
>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:   Sun Oct 26 17:30:15 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Chris S.J. Peron
>Release:        FreeBSD 4.8-RELEASE-p13 i386
>Organization:
>Environment:
System: FreeBSD staff 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 #1: Sat Oct 25 16:45:55 UTC 2003 yboily at staff:/usr/src/sys/compile/STAFF i386


	
>Description:
ng_one2many(4) does not tell the users their network
interface must be ``up'' before they can link them
into a group properly.


	
>How-To-Repeat:
	N/A
Fix:

--- share/man/man4/ng_one2many.4.0	Sun Oct 26 02:38:51 2003
+++ share/man/man4/ng_one2many.4	Sun Oct 26 02:15:05 2003
@@ -71,6 +71,17 @@
 Packets are never delivered out a many hook that is down.
 How a link is determined to be up or down depends on the node's
 configured link failure detection algorithm.
+.Pp
+Before an interface or link can be plumbed into a group, its status
+must be marked as being
+.Dq up .
+This is normally setup during the initial boot stages by
+.Xr rc.conf 5 . 
+It's also possible to change an interfaces status to
+.Dq up 
+by using the
+.Xr ifconfig 8
+utility. 
 .Sh TRANSMIT ALGORITHMS
 .Bl -tag -width foo
 .It NG_ONE2MANY_XMIT_ROUNDROBIN
@@ -179,22 +190,29 @@
 .Dv fxp3 :
 .Bd -literal -offset 0n
   # Plumb nodes together
+
   ngctl mkpeer fxp0: one2many upper one
   ngctl connect fxp0: fxp0:upper lower many0
   ngctl connect fxp1: fxp0:upper lower many1
   ngctl connect fxp2: fxp0:upper lower many2
   ngctl connect fxp3: fxp0:upper lower many3
+
   # Allow fxp1 through fxp3 to xmit/recv fxp0 frames
+
   ngctl msg fxp1: setpromisc 1
   ngctl msg fxp2: setpromisc 1
   ngctl msg fxp3: setpromisc 1
   ngctl msg fxp1: setautosrc 0
   ngctl msg fxp2: setautosrc 0
   ngctl msg fxp3: setautosrc 0
+
   # Configure all four links as up
+
   ngctl msg fxp0:upper \\
     setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 1 1 ] }"
+
   # Bring up interface
+
   ifconfig fxp0 192.168.1.1 netmask 0xfffffffc
 .Ed
 .Pp
@@ -206,6 +224,7 @@
 More transmit and link failure algorithms should be supported.
 A good candidate is Cisco's Etherchannel.
 .Sh SEE ALSO
+.Xr ifconfig 8 ,
 .Xr netgraph 4 ,
 .Xr ng_bridge 4 ,
 .Xr ng_ether 4 ,
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


From kensmith at FreeBSD.org  Mon Oct 27 03:28:04 2003
From: kensmith at FreeBSD.org (Ken Smith)
Date: Sun, 26 Oct 2003 19:28:03 -0800 (PST)
Subject: docs/37719: Detail VOP_ naming in a relevant man-page
Message-ID: <200310270328.h9R3S3jF004489@freefall.freebsd.org>

Synopsis: Detail VOP_ naming in a relevant man-page

Responsible-Changed-From-To: freebsd-doc->kensmith
Responsible-Changed-By: kensmith
Responsible-Changed-When: Sun Oct 26 19:27:38 PST 2003
Responsible-Changed-Why: 

I can give this a try.


http://www.freebsd.org/cgi/query-pr.cgi?pr=37719


From ofsen at enderunix.org  Mon Oct 27 09:23:44 2003
From: ofsen at enderunix.org (Omer Faruk Sen)
Date: Mon, 27 Oct 2003 11:23:33 +0200
Subject: Docbook editor
Message-ID: <200310270923.h9R9NYlS097358@istanbul.enderunix.org>

Hi, 

I am about to advise a visual editor for my friends to translate fdp. Some 
of them never used FreeBSD and knows nothing about Docbook. 

Can you advise me a good docbook editor that works on Windows or Linux? 
Since the main concentration is translation it will be good for them to 
start translation as soon as possible without spending time with "learning 
curve" of SGML. 

REGARDS! 


 -----------------------
Omer Faruk Sen
http://www.EnderUNIX.ORG
Software Development Team @ Turkey
http://www.Faruk.NET
For Public key: http://www.enderunix.org/ofsen/ofsen.asc
******************************************************** 

FreeBSD - because Unix isn't just #include <linux.h> ! 


From hmp at nxad.com  Mon Oct 27 11:50:27 2003
From: hmp at nxad.com (Hiten Pandya)
Date: Mon, 27 Oct 2003 03:50:25 -0800
Subject: Darwin...
In-Reply-To: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
References: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
Message-ID: <20031027115025.GA30221@perrin.nxad.com>

On Sun, Oct 26, 2003 at 05:30:44PM -0500, Ken Smith wrote:
: 
: There are places on the Web site that list other related projects (NetBSD,
: OpenBSD, etc.).  Does anyone object to adding Darwin, probably the site
: http://www.opendarwin.org?  if I was to do it are there others that
: should be added?  It's the only other stable project with BSD roots I'm aware
: of but I don't "get out" much...

	You might also need to add a copyright/registered entry or such.
	This should be done for things like Sun Solaris and any other
	commercial Operating System mentioned on the web site.  I am
	sure the Microsoft Windows is already been done.

	Regards,

-- 
Hiten Pandya
hmp at FreeBSD.ORG


From hmp at nxad.com  Mon Oct 27 11:53:53 2003
From: hmp at nxad.com (Hiten Pandya)
Date: Mon, 27 Oct 2003 03:53:52 -0800
Subject: RFC - OSI Course Starter Kit...
In-Reply-To: <20031025011746.GA7080@electra.cse.Buffalo.EDU>
References: <20031025011746.GA7080@electra.cse.Buffalo.EDU>
Message-ID: <20031027115352.GB30221@perrin.nxad.com>

On Fri, Oct 24, 2003 at 09:17:46PM -0400, Ken Smith wrote:
: 
: Marc has been helping me figure out whether bothering to do this is
: worthwhile.  So far the answer is maybe.  ;-)  Before I follow through
: with the work that packaging this up would be (I can find other things
: to do if this isn't worthwhile) I'd like to ask you folks to see if
: this is useful.
:
: [.... excellent stuff ....]
:
: Thoughts?  Is it worth doing?  Should it be done, but done differently?
: Any suggestions about what to add other than more details on how to
: configure the lab in the Instructors' Manual?

	Worth doing?  Yes.

	You might wanna have a look at Matthew Dillon's development(7)
	manual page for information on the setup that he has been using
	for doing kernel and other types of development.  It should
	contains a lot of practical insight and give you hints and tips
	on improving your article (I haven't looked at it, yet, but
	should do soon!).

	Hope that helps,

	Regards,

-- 
Hiten Pandya
hmp at FreeBSD.ORG


From ivan.dolezal at vsb.cz  Mon Oct 27 12:56:08 2003
From: ivan.dolezal at vsb.cz (=?ISO-8859-2?Q?Ivan_Dole=BEal?=)
Date: Mon, 27 Oct 2003 13:56:05 +0100
Subject: could current RELEASE-patchlevel be more "visible"?
Message-ID: <3F9D15E5.7070500@vsb.cz>


Hello,

    this is just a simple suggestion regarding a design of 
www.freebsd.org webpages:

    If you put on some visible place of security page an information 
saying something like

+--------------------+
|current RELEASE     |
|patchlevels:        |
|                    |
|5.1-RELEASE-p10     |
|5.0-RELEASE-p12     |
|4.8-RELEASE-p23     |
| ...                |
|older not maintained|
+--------------------+


it would help (me) sometimes to keep eye on proper security patching of 
my systems by just confronting `uname -a` with the page.

    Pardon me, if I am blind so I couldn't find it.

    Thank you in advance!


Ivan Dolezal




From kensmith at cse.Buffalo.EDU  Mon Oct 27 13:47:40 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Mon, 27 Oct 2003 08:47:37 -0500
Subject: Darwin...
In-Reply-To: <20031027115025.GA30221@perrin.nxad.com>
References: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
	<20031027115025.GA30221@perrin.nxad.com>
Message-ID: <20031027134736.GC24973@electra.cse.Buffalo.EDU>

On Mon, Oct 27, 2003 at 03:50:25AM -0800, Hiten Pandya wrote:

> 	You might also need to add a copyright/registered entry or such.
> 	This should be done for things like Sun Solaris and any other
> 	commercial Operating System mentioned on the web site.  I am
> 	sure the Microsoft Windows is already been done.

Thanks, I'll watch for that sort of stuff if/when browsing.

I can't find a Trademark for Darwin but it looks like NetBSD has
a trademark registered.  Though the place I was checking thinks
FreeBSD's Trademark is registered to Walnut Creek so I'm not sure
how accurate this is given Murray's fun with that.  This is the
search tool I found:

http://tess2.uspto.gov/bin/gate.exe?f=searchstr&state=geuq4q.1.1

It says NetBSD is a Trademark of "NetBSD Foundation".
No records found for OpenBSD.
Lots of records found for Darwin but none that seem to apply to
the Darwin OS.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From simon at FreeBSD.org  Mon Oct 27 14:09:21 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Mon, 27 Oct 2003 15:09:17 +0100
Subject: No ssh or sshd online manpages?
In-Reply-To: <Pine.LNX.4.44.0310231611380.8146-100000@vader.aacc.edu>
References: <20031023165911.GA575@nosferatu.blackend.org>
	<Pine.LNX.4.44.0310231611380.8146-100000@vader.aacc.edu>
Message-ID: <20031027140915.GA420@arthur.nitro.dk>

On 2003.10.23 16:32:32 -0400, Michel Lavondes wrote:
> On Thu, 23 Oct 2003, Marc Fonvieille wrote:
> 
> > On Thu, Oct 23, 2003 at 07:11:59AM -0400, Michel Lavondes wrote:
> > > 
> > > lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
> > > FreeBSD+4.8-stable&format=html
> > 
> > Try:
> > 
> > http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0
> > &manpath=OpenBSD+3.3&format=html
> > 
> > you have to use OpenBSD as OS.
> 
> Hmm, I'm not sure what's the rationale for this. For all I know, there may 
> be copyright, license, policy, or other non-technical reasons for doing 
> this. However, it looks inconsistent with the way other imported stuff is 
> handled. Eg, to look at the newstyle rc(8) manpage, I can specify I'm 
> interested in FreeBSD5.1 instead of asking for NetBSD manpages.
> 
> What am I missing? (besides humility, that is. :-) )

It was a "bug" on www.FreeBSD.org, which has been fixed by Wolfram
Schneider (wosch@).

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031027/e79d2f60/attachment.sig>

From simon at FreeBSD.org  Mon Oct 27 14:17:25 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Mon, 27 Oct 2003 15:17:21 +0100
Subject: RFC - OSI Course Starter Kit...
In-Reply-To: <20031025011746.GA7080@electra.cse.Buffalo.EDU>
References: <20031025011746.GA7080@electra.cse.Buffalo.EDU>
Message-ID: <20031027141721.GB420@arthur.nitro.dk>

On 2003.10.24 21:17:46 -0400, Ken Smith wrote:
> 
> I was thinking about the crashlab.html becoming an Article on the Web
> site, and the Lab Manual being provided as an OpenOffice document
> because they'd need to be able to edit it (they wouldn't have the same
> machine names I use, would probably have their own additions to the
> Lab procedures, etc...).
> 
> Thoughts?  Is it worth doing?  Should it be done, but done differently?
> Any suggestions about what to add other than more details on how to
> configure the lab in the Instructors' Manual?

I haven't had the time to read your current documents more closely (busy
with a Computer Science project :-) ), but I think the it would be a
real nice thing to have as part of the FreeBSD documentation.  Perhaps
it would even inspire some universities to look more at FreeBSD, or at
least help anyone who is looking at using FreeBSD.

-- 
Simon L. Nielsen
FreeBSD Documentation Team
Computer Science student, University of Copenhagen, Denmark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031027/155840fb/attachment.sig>

From simon at FreeBSD.org  Mon Oct 27 14:34:12 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Mon, 27 Oct 2003 15:34:10 +0100
Subject: Darwin...
In-Reply-To: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
References: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
Message-ID: <20031027143408.GC420@arthur.nitro.dk>

On 2003.10.26 17:30:44 -0500, Ken Smith wrote:
> 
> There are places on the Web site that list other related projects (NetBSD,
> OpenBSD, etc.).  Does anyone object to adding Darwin, probably the site
> http://www.opendarwin.org?  if I was to do it are there others that

Since Darwin, through MacOS X, is probably the BSD with most users (at
least on the desktop), I think it would just fine to add it, where
appropriate.

> should be added?  It's the only other stable project with BSD roots I'm aware
> of but I don't "get out" much...

The only other BSD that I know of, which is not just a relabeled version
of one of the major BSD's, is DragonFly BSD.  While DraonFly is of
course still mainly FreeBSD and is still infancy, it does looks like
it's here to stay.  Whether DragonFly should be added depend on the
context, since it is probably not interesting to end users yet.

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031027/5ffa8d21/attachment.sig>

From simon at FreeBSD.org  Mon Oct 27 14:58:50 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Mon, 27 Oct 2003 15:58:48 +0100
Subject: Darwin...
In-Reply-To: <20031027134736.GC24973@electra.cse.Buffalo.EDU>
References: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
	<20031027115025.GA30221@perrin.nxad.com>
	<20031027134736.GC24973@electra.cse.Buffalo.EDU>
Message-ID: <20031027145846.GD420@arthur.nitro.dk>

On 2003.10.27 08:47:37 -0500, Ken Smith wrote:
> On Mon, Oct 27, 2003 at 03:50:25AM -0800, Hiten Pandya wrote:
> 
> > 	You might also need to add a copyright/registered entry or such.
> > 	This should be done for things like Sun Solaris and any other
> > 	commercial Operating System mentioned on the web site.  I am
> > 	sure the Microsoft Windows is already been done.

Solaris and similar known trademarks should be marked up correctly, but
of course I won't rule out that I might have missed some instances.

> Thanks, I'll watch for that sort of stuff if/when browsing.
>
> I can't find a Trademark for Darwin but it looks like NetBSD has
> a trademark registered.  Though the place I was checking thinks

I don't think it's registered, but they are in the process of
registering it.

> FreeBSD's Trademark is registered to Walnut Creek so I'm not sure
> how accurate this is given Murray's fun with that.  This is the

I think that is still correct with the current status. (Since Walnut
Creek is Wind River Systems, after BSDi bought Walnut Creek, and WRS
bought BSDi.)

> search tool I found:
> 
> http://tess2.uspto.gov/bin/gate.exe?f=searchstr&state=geuq4q.1.1

Due to USPTO's use of sessions, that URL will only work a very short
time (doesn't work now).

> It says NetBSD is a Trademark of "NetBSD Foundation".
> No records found for OpenBSD.
> Lots of records found for Darwin but none that seem to apply to
> the Darwin OS.

Darwin doesn't appear on Apple's trademark list[1], so I don't think it
is a trademark.

BTW, also note that some trademarks (even registered trademarks) doesn't
require you to use trademark symbols.

[1] http://www.apple.com/legal/appletmlist.html

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031027/026c3cc3/attachment.sig>

From trhodes at FreeBSD.org  Mon Oct 27 15:39:24 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Mon, 27 Oct 2003 11:39:05 -0500
Subject: Docbook editor
In-Reply-To: <200310270923.h9R9NYlS097358@istanbul.enderunix.org>
References: <200310270923.h9R9NYlS097358@istanbul.enderunix.org>
Message-ID: <20031027113905.1305845d.trhodes@FreeBSD.org>

On Mon, 27 Oct 2003 11:23:33 +0200
Omer Faruk Sen <ofsen at enderunix.org> wrote:

> Hi, 
> 
> I am about to advise a visual editor for my friends to translate fdp. Some 
> of them never used FreeBSD and knows nothing about Docbook. 
> 
> Can you advise me a good docbook editor that works on Windows or Linux? 
> Since the main concentration is translation it will be good for them to 
> start translation as soon as possible without spending time with "learning 
> curve" of SGML. 
> 
> REGARDS! 

If they use KDE, Quanta seems nice.  I haven't used it that much
(beyond opening it and playing with a few options), but it should be
what you're looking for.

-- 
Tom Rhodes


From bugmaster at freebsd.org  Mon Oct 27 19:00:57 2003
From: bugmaster at freebsd.org (FreeBSD bugmaster)
Date: Mon, 27 Oct 2003 11:00:50 -0800 (PST)
Subject: Current unassigned doc problem reports
Message-ID: <200310271900.h9RJ0ohQ055495@freefall.freebsd.org>

Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

Bugs can be in one of several states:

o - open
     A problem report has been submitted, no sanity checking performed.

a - analyzed
     The problem is understood and a solution is being sought.

f - feedback
     Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
     A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

s - suspended
     The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
     A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
a [2001/10/31] i386/31671  doc         4.4 installer hangs at " Mounting root fr

1 problem total.

Serious problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
s [1999/10/04] i386/14135  doc         lpt1 nolonger exists after 3.2-RELEASE
s [2000/07/18] docs/20028  doc         ASCII docs should reflect <emphasis> tags
o [2001/05/23] docs/27605  doc         Cross-document references (<olink>)
o [2002/01/15] docs/33929  doc         Section 15.15 of the FreeBSD Porter's Han
s [2002/03/08] docs/35678  doc         docproj Makefiles for web are broken for 
o [2002/03/21] docs/36168  doc         -pthread/_THREAD_SAFE docs missing in gcc
o [2002/09/13] docs/42762  doc         ppp.8 has no description of $env and ~use
o [2002/11/14] docs/45303  doc         Bug in PDF DocBook rendering
f [2003/02/19] docs/48472  doc         Documentation unreadable.
o [2003/09/15] docs/56894  doc         umass man page: "mount -t msdos" instead 
o [2003/10/14] docs/58033  doc         [PATCH] getenv(3) manpage doesn't state t

11 problems total.

Non-critical problems

S  Submitted   Tracker     Resp.       Description
-------------------------------------------------------------------------------
o [2001/02/01] docs/24786  doc         missing FILES descriptions in sa(4)
o [2001/04/29] docs/26943  doc         [patch] description of :C modifier is mis
o [2001/07/26] docs/29245  doc         top(1) manpage doesn't understand SMP
a [2001/08/23] docs/30008  doc         This document should be translated, comme
o [2001/09/27] docs/30873  doc         ``ip'' man page does not specify byte ord
o [2001/10/07] docs/31109  doc         replace gif images w/ png ones due to pat
o [2001/11/15] docs/32020  doc         loader.8 manpage missing tunables
o [2002/01/05] docs/33589  doc         Patch to doc.docbook.mk to post process .
o [2002/01/13] docs/33852  doc         split(1) man page implies that input file
o [2002/01/14] docs/33877  doc         Documentet behaviour of SF_flags for non-
o [2002/02/15] bin/34955   doc         [PATCH] ps(1) is out of touch with realit
a [2002/02/16] docs/35011  doc         There are no commands called "diskless" o
o [2002/02/22] docs/35222  doc         mailing list archive URL regexp suboptima
o [2002/03/06] docs/35608  doc         mt(1) page uses "setmark" without explana
o [2002/03/06] docs/35609  doc         mt(1) page needs explanation of "long era
o [2002/03/06] docs/35612  doc         ps(1) page "state" description doesn't me
o [2002/03/07] docs/35642  doc         lo(4) page maybe should document optional
o [2002/03/07] docs/35644  doc         lo(4) page presumes familiarity with prin
o [2002/03/07] docs/35646  doc         cp(1) page needs a "Bugs" section.
o [2002/03/07] docs/35647  doc         www; combine query-by-number and multi-fi
o [2002/03/07] docs/35648  doc         rc.conf; add note about "flags" to both f
o [2002/03/08] docs/35686  doc         blackhole(4) page seems to contradict its
o [2002/03/08] docs/35687  doc         /etc/nsmb.conf missing mention of readers
o [2002/03/09] docs/35711  doc         the "gnats page" should move to its own s
o [2002/03/10] docs/35732  doc         adduser(8) page has obsolete reference an
o [2002/03/15] docs/35943  doc         at(1) config files are misplaced in /var/
o [2002/03/15] docs/35953  doc         hosts.equiv(5) manual is confusing or wro
o [2002/03/28] docs/36432  doc         Proposal for doc/share/mk: make folded bo
o [2002/03/28] docs/36449  doc         symlink(7) manual doesn't mention trailin
s [2002/05/07] docs/37843  doc         manual for pthread_setschedparam is wrong
o [2002/05/18] docs/38225  doc         change "CDROM" to "CD-ROM"
o [2002/05/25] docs/38556  doc         EPS file of beastie, as addition to exist
o [2002/05/27] docs/38620  doc         Committers Guide and CVS
o [2002/05/31] docs/38772  doc         firewall_type feature not mentioned on Ha
o [2002/06/07] docs/38982  doc         developers-hanbook/Jail fix
o [2002/06/12] docs/39213  doc         No rc(4) man page
o [2002/06/15] docs/39348  doc         kenv fetch of hostname requires dhcp/boot
o [2002/06/19] docs/39530  doc         access(2) man page has unnecessarily broa
o [2002/06/19] docs/39532  doc         'find' man page should
o [2002/06/24] docs/39824  doc         Various tweaks for doc/en_US.ISO8859-1/bo
o [2002/07/04] docs/40196  doc         man find does not describe -follow
o [2002/07/10] docs/40423  doc         Keyboard(4)'s definition of parameters to
o [2002/07/10] docs/40443  doc         Update books/faq/book.sgml for USB .ko's 
o [2002/07/21] docs/40851  doc         [PATCH] "mergemaster -p" in UPDATING's "C
o [2002/07/28] docs/41089  doc         pax -B option does not mention interactio
o [2002/08/02] docs/41270  doc         confusing directions for kernelconfig cha
o [2002/08/07] docs/41423  doc         Update FAQ: attrib command for windows du
o [2002/08/19] docs/41787  doc         man page for route (Section 8) missing de
o [2002/08/19] docs/41791  doc         Documentation formatting error
o [2002/08/19] docs/41807  doc         natd -punch_fw "bug"
o [2002/08/20] docs/41820  doc         Device driver confusion in Handbook (2.3)
a [2002/08/27] docs/42058  doc         Documentation: Installing Oracle 8i onto 
o [2002/10/01] docs/43569  doc         src/share/examples/worm/README out-of-dat
o [2002/10/04] docs/43651  doc         stab(5) incorrectly states to include jus
o [2002/10/09] docs/43861  doc         non-trivial typo in wicontrol man page
o [2002/10/11] docs/43941  doc         Rationale for Upgrade Sequence
o [2002/10/14] docs/44074  doc         ln(1) manual clarifications [patch]
o [2002/10/23] docs/44400  doc         ipfw(8) has contradictions in bridged and
o [2002/10/24] docs/44435  doc         sysctl manpage: add example for tcsh
o [2002/10/29] docs/44594  doc         Handbook doesn't mention drivers.flp for 
o [2002/11/17] docs/45371  doc         man page for exports lacks information on
o [2002/12/02] docs/45940  doc         burncd missing info
o [2002/12/11] docs/46181  doc         "make fetch-recursive" target description
o [2002/12/11] docs/46196  doc         Missing return value in (set_)menu_format
o [2002/12/11] docs/46200  doc         fix for ru_RU.KOI8-R/books/porters-handbo
o [2002/12/16] docs/46291  doc         correlation between HZ kernel config para
o [2002/12/16] docs/46295  doc         please add information to Nvi recovery em
o [2003/01/02] docs/46709  doc         tables in terminfo.5 are broken
o [2003/01/05] docs/46793  doc         DEVICE_POLLING can not be used with SMP, 
o [2003/01/14] docs/47085  doc         boot(8) manpage is incomplete according t
o [2003/01/27] docs/47575  doc         Clarify requirements for IPFW2 in STABLE
o [2003/01/28] docs/47594  doc         [PATH] passwd(5) incorrectly states allow
o [2003/01/30] docs/47690  doc         builtin(1) manpage is wrong about externa
o [2003/01/30] docs/47705  doc         wc(1) manpage has poor explanations.
f [2003/02/02] docs/47818  doc         ln(1) manpage is confusing
f [2003/02/07] docs/48038  doc         [PATCH] add Tips and Tricks section into 
o [2003/02/28] docs/48767  doc         wrong key numbers for left/right windows 
o [2003/03/06] docs/48980  doc         [PATCH] nsgmls -s errors and sect. 3.2.1 
o [2003/03/14] docs/50013  doc         [PATCH] add much more russian holydays
o [2003/03/23] docs/50211  doc         [PATCH] Fix textfile creation
f [2003/03/28] docs/50391  doc         Incorrect information in a man
o [2003/04/03] docs/50573  doc         return values for res_query/res_search/re
f [2003/04/07] docs/50677  doc         [PATCH] update doc/en_US.ISO8859-1/books/
o [2003/04/10] docs/50773  doc         NFS problems by jumbo frames to mention i
o [2003/05/06] docs/51875  doc         atkbd(4) adjustment
o [2003/05/06] docs/51891  doc         DIAGNOSTICS in ed driver manpage don't ma
o [2003/05/07] docs/51921  doc         ls(1) manpage lacks some information abou
o [2003/05/11] docs/52071  doc         [PATCH] Add more information about soft u
o [2003/05/25] docs/52672  doc         Porter's Handbook: couple of corrections
o [2003/06/02] docs/52878  doc         [PATCH] security(7): small clairification
o [2003/06/13] docs/53303  doc         mount(2) man page error
o [2003/06/14] docs/53315  doc         [PATCH] remove extraneous whitespace at t
o [2003/06/18] docs/53454  doc         wrong sample code in manpage of wcwidth(3
o [2003/06/19] docs/53501  doc         [PATCH] Handbook: update snapshots sectio
o [2003/06/20] docs/53575  doc         Change to Handbook Section 20.9
o [2003/06/21] docs/53596  doc         Updates to mt manual page
o [2003/06/25] docs/53732  doc         quota output and man page do not document
o [2003/06/26] docs/53751  doc         bus_dma(9) incorrectly documents BUS_DMA_
o [2003/07/11] docs/54380  doc         [PATCH] document additional perl variable
o [2003/07/11] docs/54391  doc         Document that glob(3) respects LC_COLLATE
o [2003/07/20] docs/54678  doc         [patch] add PACKAGESITE to packages chapt
o [2003/07/22] docs/54752  doc         bus_dma explained in ISA section: should 
o [2003/07/22] docs/54769  doc         [patch] updates to FAQ
o [2003/07/23] docs/54789  doc         [PATCH] brush up the "New Users" article
o [2003/07/24] docs/54806  doc         [patch] adds fvwm2 to x11-wm
o [2003/07/25] docs/54879  doc         man 1 jot, -r description
o [2003/07/28] docs/54995  doc         Error in accept(2) man page
o [2003/07/28] docs/54999  doc         Documentation Project Primer doesn't conf
o [2003/08/03] docs/55207  doc         [patch] update acroread section & add loc
o [2003/08/06] docs/55306  doc         [patch] adds filemanagers to desktop appl
o [2003/08/11] docs/55458  doc         [patch] add useful content & hints to por
o [2003/08/11] docs/55482  doc         DUMP has access to block devices in a JAI
o [2003/08/13] docs/55538  doc         [patch] add screenshots to desktop chapte
o [2003/08/16] docs/55653  doc         chflags.1 - note that not all tools chfla
o [2003/09/04] docs/56408  doc         [PATCH] add <filename> around app-default
o [2003/09/04] docs/56452  doc         [patch]Add EXTRACT_DEPENDS&PATCH_DEPENDS 
o [2003/09/13] docs/56745  doc         Some suggestions for the Bibliography cha
o [2003/09/14] docs/56872  doc         [Patch] Talk about EVFILT_NETDEV in kqueu
o [2003/09/14] docs/56883  doc         Inadequately-documented charter for freeb
o [2003/09/15] docs/56901  doc         [patch] articles/diskless-x: fix bad engl
o [2003/09/15] docs/56903  doc         [patch] articles/fonts: add application t
o [2003/09/16] docs/56915  doc         [patch] articles/fonts: update links
o [2003/09/16] docs/56932  doc         [patch] articles/releng-packages: add "no
o [2003/09/16] docs/56936  doc         [patch] articles/java-tomcat: add applica
o [2003/09/18] docs/56981  doc         man terminfo(5) from libncurses does not 
o [2003/09/22] docs/57118  doc         
o [2003/09/24] docs/57153  doc         S_IRWXU missing in fstat(2) man page?
o [2003/09/29] docs/57388  doc         INSTALL.TXT enhancement: mention ok promp
o [2003/10/04] docs/57569  doc         error on gensetdefs(8) man page
o [2003/10/06] docs/57669  doc         IFMIB(4) man page uses sysctl(3) incorrec
o [2003/10/10] docs/57838  doc         missing in docu: port Makefile target 'pa
o [2003/10/12] docs/57926  doc         amd.conf.5 poorly format as it has both m
o [2003/10/13] docs/57974  doc         man page apropos for select macros (FD_SE
o [2003/10/13] docs/57978  doc         Type miss of GPIB in Hardware Notes
o [2003/10/16] docs/58111  doc         Handbook 12.4.3 Rebuilding ATA RAID1 Arra
o [2003/10/20] docs/58318  doc         missing modifier in crontab(5) manpage (c
o [2003/10/26] docs/58586  doc         [patch] ng_one2many interface status requ

137 problems total.


From dodell at sitetronics.com  Tue Oct 28 04:32:01 2003
From: dodell at sitetronics.com (Devon H. O'Dell)
Date: Tue, 28 Oct 2003 05:31:47 +0100
Subject: Printer Setup (11.3.1.1.1)
Message-ID: <3F9DF133.3000104@sitetronics.com>

In this section there's the text:
In general, serial interfaces are slower than parallel interfaces. 
Parallel interfaces usually offer just one-way communication (computer 
to printer) while serial gives you two-way. Many newer parallel ports 
and printers can communicate in both directions under FreeBSD when a 
IEEE1284 compliant cable is used.

Shouldn't the second sentence s/serial/parallel/ s/Parallel/serial/ ?

--Devon


From fox at vader.aacc.cc.md.us  Tue Oct 28 06:44:55 2003
From: fox at vader.aacc.cc.md.us (Michel Lavondes)
Date: Tue, 28 Oct 2003 01:44:46 -0500 (EST)
Subject: No ssh or sshd online manpages?
In-Reply-To: <20031027140915.GA420@arthur.nitro.dk>
Message-ID: <Pine.LNX.4.44.0310280134470.10032-100000@vader.aacc.edu>

On Mon, 27 Oct 2003, Simon L. Nielsen wrote:

> On 2003.10.23 16:32:32 -0400, Michel Lavondes wrote:
> > On Thu, 23 Oct 2003, Marc Fonvieille wrote:
> > 
> > > On Thu, Oct 23, 2003 at 07:11:59AM -0400, Michel Lavondes wrote:
> > > > 
> > > > lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
> > > > FreeBSD+4.8-stable&format=html
> > > 
> > > http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0
> > > &manpath=OpenBSD+3.3&format=html
> > 
> > What am I missing? (besides humility, that is. :-) )
> 
> It was a "bug" on www.FreeBSD.org, which has been fixed by Wolfram
> Schneider (wosch@).

Thanks. Looks like the change took... but only for 4.8-RELEASE. 4.8-stable 
and 4.9-RELEASE still claim not to know about it. (But for 4.9R, it could 
be because there ain't no sich animal yet.) I haven't bothered to check 
other 4.x and 5.x manpages, as I'm not sure when the ssh*_config.5 
manpages were split from the corresponding ssh_.1 manpages.

Also, in sshd_config.5 (the local version, not the one fresh from the 
openssh tree):

     PasswordAuthentication
             Specifies whether password authentication is allowed.  The
             default is ``yes''.  Note that ChallengeResponseAuthentication is
Shirley there should be an "if" there? ---^^^
             ``yes'', and the PAM authentication policy for sshd includes

Anal-retentive nitpicker? Moi?

-- 
Remember: i before e, except on Unix machines.


From blackend at freebsd.org  Tue Oct 28 08:23:15 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Tue, 28 Oct 2003 09:23:05 +0100
Subject: Printer Setup (11.3.1.1.1)
In-Reply-To: <3F9DF133.3000104@sitetronics.com>
References: <3F9DF133.3000104@sitetronics.com>
Message-ID: <20031028082305.GA583@nosferatu.blackend.org>

On Tue, Oct 28, 2003 at 05:31:47AM +0100, Devon H. O'Dell wrote:
> In this section there's the text:
> In general, serial interfaces are slower than parallel interfaces. 
> Parallel interfaces usually offer just one-way communication (computer 
> to printer) while serial gives you two-way. Many newer parallel ports 
> and printers can communicate in both directions under FreeBSD when a 
> IEEE1284 compliant cable is used.
> 
> Shouldn't the second sentence s/serial/parallel/ s/Parallel/serial/ ?
>

Ok, I fixed it in revision 1.79 of the chapter, Thanks!

Marc


From roam at ringlet.net  Tue Oct 28 10:34:43 2003
From: roam at ringlet.net (Peter Pentchev)
Date: Tue, 28 Oct 2003 12:34:25 +0200
Subject: Printer Setup (11.3.1.1.1)
In-Reply-To: <20031028082305.GA583@nosferatu.blackend.org>
References: <3F9DF133.3000104@sitetronics.com>
	<20031028082305.GA583@nosferatu.blackend.org>
Message-ID: <20031028103425.GV430@straylight.oblivion.bg>

On Tue, Oct 28, 2003 at 09:23:05AM +0100, Marc Fonvieille wrote:
> On Tue, Oct 28, 2003 at 05:31:47AM +0100, Devon H. O'Dell wrote:
> > In this section there's the text:
> > In general, serial interfaces are slower than parallel interfaces. 
> > Parallel interfaces usually offer just one-way communication (computer 
> > to printer) while serial gives you two-way. Many newer parallel ports 
> > and printers can communicate in both directions under FreeBSD when a 
> > IEEE1284 compliant cable is used.
> > 
> > Shouldn't the second sentence s/serial/parallel/ s/Parallel/serial/ ?
> >
> 
> Ok, I fixed it in revision 1.79 of the chapter, Thanks!

Errrr... I'm not sure it needed fixing :)  Rather, IMHO rev. 1.79 might
need to be reverted.

Historically, parallel ports did indeed offer only one-way
communication: the computer sent data to the printer, and that was it.
Then things like EPP (the extended printer port) interface and friends
were developed, and the parallel port grew two-way communication, too -
this is exactly what the *last* sentence is talking about (EPP and ECP
were standardized in IEEE 1284, http://www.fapo.com/ieee1284.htm for
more info).

Serial port communications have always been two-way, AFAIK, albeit some
of them were just half-duplex, so only one side could talk at a time.

Thus, I think the text was correct as it was, before rev. 1.79 -
parallel ports were once only capable of one-way communication, but with
IEEE 1284 (EPP, ECP) they can do two-way now, while serial ports have
always been capable of two-way communication.

G'luck,
Peter

-- 
Peter Pentchev	roam at ringlet.net    roam at sbnd.net    roam at FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
"yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031028/d6d7d270/attachment.sig>

From blackend at freebsd.org  Tue Oct 28 11:32:19 2003
From: blackend at freebsd.org (Marc Fonvieille)
Date: Tue, 28 Oct 2003 12:32:12 +0100
Subject: Printer Setup (11.3.1.1.1)
In-Reply-To: <20031028103425.GV430@straylight.oblivion.bg>
References: <3F9DF133.3000104@sitetronics.com>
	<20031028082305.GA583@nosferatu.blackend.org>
	<20031028103425.GV430@straylight.oblivion.bg>
Message-ID: <20031028113212.GB583@nosferatu.blackend.org>

On Tue, Oct 28, 2003 at 12:34:25PM +0200, Peter Pentchev wrote:
> 
> Errrr... I'm not sure it needed fixing :)  Rather, IMHO rev. 1.79 might
> need to be reverted.
> 
> Historically, parallel ports did indeed offer only one-way
> communication: the computer sent data to the printer, and that was it.
> Then things like EPP (the extended printer port) interface and friends
> were developed, and the parallel port grew two-way communication, too -
> this is exactly what the *last* sentence is talking about (EPP and ECP
> were standardized in IEEE 1284, http://www.fapo.com/ieee1284.htm for
> more info).
> 
> Serial port communications have always been two-way, AFAIK, albeit some
> of them were just half-duplex, so only one side could talk at a time.
>

Oh you're right, I just had that half-duplex in mind.  I always thought
serial printers used half-duplex.

> Thus, I think the text was correct as it was, before rev. 1.79 -
> parallel ports were once only capable of one-way communication, but with
> IEEE 1284 (EPP, ECP) they can do two-way now, while serial ports have
> always been capable of two-way communication.
> 

I reverted the commit and added EPP, ECP in the last sentence, it will
be less confusing.

Marc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031028/3007fd0e/attachment.sig>

From marck at rinet.ru  Tue Oct 28 12:00:37 2003
From: marck at rinet.ru (Dmitry Morozovsky)
Date: Tue, 28 Oct 2003 14:58:29 +0300 (MSK)
Subject: docs/58615: update for Vinum chapter of Handbook: describe raid5
	plexes
Message-ID: <200310281158.h9SBwTrD066612@woozle.rinet.ru>


>Number:         58615
>Category:       docs
>Synopsis:       update for Vinum chapter of Handbook: describe raid5 plexes
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 28 04:00:34 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dmitry Morozovsky
>Release:        FreeBSD 4-STABLE i386
>Organization:
Cronyx Plus LLC (RiNet ISP)
>Environment:
System: FreeBSD 4-STABLE 


>Description:

Vinum Chapter (Number 13 as of current Handbook) mostly had been written in the
epoch of FreeBSD 3.x, where raid5 Vinum capabilities were strict-licensed. This
is no longer the case for RELENG_4; however, raid5 has been described in
"conceptual" sections but not in "implementation" ones. Here is update for two
level1 sections.

Next update for Vinum chapter should be bringing real configuration examples to
consistent state. But I suppose it should be different PR.

>How-To-Repeat:

>Fix:


Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml,v
retrieving revision 1.24
diff -u -r1.24 chapter.sgml
--- chapter.sgml	31 Aug 2003 16:41:36 -0000	1.24
+++ chapter.sgml	28 Oct 2003 11:51:27 -0000
@@ -362,7 +362,7 @@
     <sect2>
       <title>Which Plex Organization?</title>
       <para>The version of Vinum supplied with FreeBSD &rel.current; implements
-	two kinds of plex:</para>
+	three kinds of plex:</para>
     
       <itemizedlist>
 	<listitem>
@@ -386,11 +386,24 @@
 	    (fractionally) more complex code and restrictions on
 	    subdisks: they must be all the same size, and extending a
 	    plex by adding new subdisks is so complicated that Vinum
-	    currently does not implement it.  Vinum imposes an
+	    currently does not implement it (actually, you have to reconstruct
+	    file system after adding or removing subdisks to the underlying plex).  
+	    Vinum imposes an
 	    additional, trivial restriction: a striped plex must have
 	    at least two subdisks, since otherwise it is
 	    indistinguishable from a concatenated plex.</para>
 	</listitem>
+
+	<listitem>
+	  <para>raid5
+	    plexes implement redundancy with low volume overhead for the price
+	    of higher CPU load and relatively low write speed.  As for striped
+	    plexes, subdisks involved must be the same size, and extending
+	    raid5 plex will need its complete reformatting.  Minimal raid5 plex
+	    must contain at least 3 subdisks; due to performance reasons, 5 or
+	    more subdisks (all on different drives, of course) are
+	    recommended.</para>
+	</listitem>
       </itemizedlist>
     
       <para><xref linkend="vinum-comparison"> summarizes the advantages
@@ -427,6 +440,15 @@
 	      <entry>High performance in combination with highly concurrent
 		access</entry>
 	    </row>
+	    
+	    <row>
+	      <entry>radi5</entry>
+	      <entry>3</entry>
+	      <entry>no</entry>
+	      <entry>yes</entry>
+	      <entry>High read performance in combination with redundancy such
+	        as large data archives</entry>
+	    </row>
 	  </tbody>
 	</tgroup>
       </table>
@@ -708,6 +730,30 @@
 	  <graphic fileref="vinum/vinum-raid10-vol">
         </figure>
       </para>
+    </sect2>
+
+    <sect2>
+      <title>Resilience and Performance: Hard Way</title>
+
+      <para><anchor id="vinum-raid5">With sufficient hardware and CPU power,
+	especially when most of disc activities are reads, it would be useful
+	to make raid5 volume, which consumes only 1/n of disk volume for
+	resilience instead of 1/2 for mirrored volumes, and still achieves
+	great read performance.  A typical configuration file might
+	be:</para>
+
+      <programlisting>
+	volume raid5
+      plex org raid5 512k
+        sd length 102480k drive a
+        sd length 102480k drive b
+        sd length 102480k drive c
+        sd length 102480k drive d
+        sd length 102480k drive e</programlisting>
+
+      <para>Note we have single plex here because raid5 provides
+	fault-tolerance itself.</para>
+
     </sect2>
   </sect1>
   
>Release-Note:
>Audit-Trail:
>Unformatted:


From gabrielcbarros at uol.com.br  Tue Oct 28 14:00:56 2003
From: gabrielcbarros at uol.com.br (Gabriel C. de Barros)
Date: Tue, 28 Oct 2003 12:00:41 -0200
Subject: lack in the firewall chapter
Message-ID: <3F9E7689.9020200@uol.com.br>

Hi,

i've spend two days trying to set ipfw or ipf .. before i understant that i should lower my kernel security settings before messing with the rules.

I think the handbook should mention that, at least in a footnote or something.

It was hard to find the answer, but while searching for it, i realized it's a very common new-user mistake.

Thanks,
Gabriel Barros


From kensmith at cse.Buffalo.EDU  Tue Oct 28 14:09:08 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Tue, 28 Oct 2003 09:09:06 -0500
Subject: lack in the firewall chapter
In-Reply-To: <3F9E7689.9020200@uol.com.br>
References: <3F9E7689.9020200@uol.com.br>
Message-ID: <20031028140906.GA24568@electra.cse.Buffalo.EDU>

On Tue, Oct 28, 2003 at 12:00:41PM -0200, Gabriel C. de Barros wrote:

> i've spend two days trying to set ipfw or ipf .. before i understant that i 
> should lower my kernel security settings before messing with the rules.
> 
> I think the handbook should mention that, at least in a footnote or 
> something.
> 
> It was hard to find the answer, but while searching for it, i realized it's 
> a very common new-user mistake.

I have a couple of ipfw related PR's I need to work on, I can take
care of this as part of finishing those up.

Basically you're saying if you have raised the security level of the
kernel above 0 you can no longer change the ipfw rules.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From simon at FreeBSD.org  Tue Oct 28 14:19:37 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Tue, 28 Oct 2003 15:19:33 +0100
Subject: lack in the firewall chapter
In-Reply-To: <20031028140906.GA24568@electra.cse.Buffalo.EDU>
References: <3F9E7689.9020200@uol.com.br>
	<20031028140906.GA24568@electra.cse.Buffalo.EDU>
Message-ID: <20031028141931.GA415@arthur.nitro.dk>

On 2003.10.28 09:09:06 -0500, Ken Smith wrote:
> On Tue, Oct 28, 2003 at 12:00:41PM -0200, Gabriel C. de Barros wrote:
> 
> > i've spend two days trying to set ipfw or ipf .. before i understant that i 
> > should lower my kernel security settings before messing with the rules.
> > 
> > I think the handbook should mention that, at least in a footnote or 
> > something.
> > 
> > It was hard to find the answer, but while searching for it, i realized it's 
> > a very common new-user mistake.
> 
> I have a couple of ipfw related PR's I need to work on, I can take
> care of this as part of finishing those up.
> 
> Basically you're saying if you have raised the security level of the
> kernel above 0 you can no longer change the ipfw rules.

From ipfw(8):

     ?   The ipfw filter list may not be modified if the system security level
         is set to 3 or higher (see init(8) for information on system security
         levels).

I haven't tested it, and I seem to remember some problems with
securelevel and ipfw not being honored correctly in the past, so you
might want to check the source.

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031028/d075beef/attachment.sig>

From pepper at reppep.com  Tue Oct 28 15:57:25 2003
From: pepper at reppep.com (Chris Pepper)
Date: Tue, 28 Oct 2003 10:56:29 -0500
Subject: Darwin...
In-Reply-To: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
References: <20031026223044.GA13291@electra.cse.Buffalo.EDU>
Message-ID: <p06100207bbc441c14cd0@[129.85.219.160]>

At 5:30 PM -0500 2003/10/26, Ken Smith wrote:
>There are places on the Web site that list other related projects (NetBSD,
>OpenBSD, etc.).  Does anyone object to adding Darwin, probably the site
>http://www.opendarwin.org?  if I was to do it are there others that
>should be added?  It's the only other stable project with BSD roots I'm aware
>of but I don't "get out" much...

	OpenDarwin is good, but you should also link to Apple's 
Darwin site <http://developer.apple.com/darwin/projects/darwin/>, 
since Apple owns & controls Darwin. OpenDarwin is an umbrella 
organization for contributing work to Darwin, but it's not the 'main' 
project currently.


						Chris
-- 
Chris Pepper:               <http://www.reppep.com/~pepper/>
Rockefeller University:     <http://www.rockefeller.edu/>


From lid at ufrima.imag.fr  Wed Oct 29 01:35:33 2003
From: lid at ufrima.imag.fr (LI Dong)
Date: Wed, 29 Oct 2003 02:35:30 +0100
Subject: Announcement of FreeBSD Chinese Simplified Documentation
	Translation Project
Message-ID: <003c01c39dbc$f06fd820$0100a8c0@daemonlite>

Hello,

I am coordinator of The FreeBSD China Project, and the goal of our project
is to adapter FreeBSD to China market.

We have created a sub-project, FreeBSD Chinese Simplified Documentation
Translation Project, and the translation has been organized properly. We
have also translated some FreeBSD documents, such as web pages, handbook,
porters handbook, etc., but in SGML format now.

So, that the problem is, I have created our local CVS Repository correctly
and imported the documents translated, but I need some important information
to finish the final setup. At lest, the official name of our translation
project (stay in 'FreeBSD Chinese Simplified Documentation Translation
Project' or need make some changes to fit the policy of The FreeBSD
Project), the path name of our translation('zh' or 'zh_CN' or 'cn'). These
informations are very important, please tell me as soon as possible.

And, I noticed that one of your translation projects is Chinese
Documentation Project, currently maintained by people from Taiwan and in
Chinese Traditional. I think it should not be called Chinese Documentation
Project, but Chinese Traditional Documentation Project, because the reason
everyone knows. And I believe that split Chinese Documentation Project to
two parts, Chinese Simplified and Chinese Traditional will take the benefits
and reflect the *respect* for both the contributors and users from China
Mainland, Hong Kong and Taiwan.

Sincerely yours,
LI Dong

UFR IMA, Universit? Joseph Fourier http://www-ufrima.imag.fr/
The FreeBSD China Project http://www.freebsd.org.cn/


From dgl at dlee.org  Wed Oct 29 02:20:18 2003
From: dgl at dlee.org (Doug Lee)
Date: Tue, 28 Oct 2003 21:11:17 -0500 (EST)
Subject: docs/58669: Mistyped file name in cvs.info for v1.11.5: .csvsrc
	(line 4978)
Message-ID: <200310290211.h9T2BHmV083132@bart.bartsite.com>


>Number:         58669
>Category:       docs
>Synopsis:       Mistyped file name in cvs.info for v1.11.5: .csvsrc (line 4978)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 28 18:20:16 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Doug Lee
>Release:        FreeBSD 4.8-RC i386
>Organization:
Bartimaeus Group
>Environment:
System: FreeBSD bart.bartsite.com 4.8-RC FreeBSD 4.8-RC #0: Sat Mar 22 16:23:09 EST 2003 dlee at bart.bartsite.com:/var/unbacked/usr/obj/usr/src/sys/BART i386


	
>Description:
Line 4978 of cvs.info for CVS v1.11.5 says:

* ~/.cvsrc::                    Default options with the ~/.csvrc file

and should say

* ~/.cvsrc::                    Default options with the ~/.cvsrc file

>How-To-Repeat:
	
>Fix:
--- cvs.info.orig	Tue Oct 28 16:02:50 2003
+++ cvs.info	Tue Oct 28 21:05:14 2003
@@ -4975,7 +4975,7 @@
 
 * Structure::                   Overall structure of CVS commands
 * Exit status::                 Indicating CVS's success or failure
-* ~/.cvsrc::                    Default options with the ~/.csvrc file
+* ~/.cvsrc::                    Default options with the ~/.cvsrc file
 * Global options::              Options you give to the left of cvs_command
 * Common options::              Options you give to the right of cvs_command
 * admin::                       Administration
>Release-Note:
>Audit-Trail:
>Unformatted:


From wosch at cs.tu-berlin.de  Wed Oct 29 14:32:08 2003
From: wosch at cs.tu-berlin.de (Wolfram Schneider)
Date: Wed, 29 Oct 2003 15:27:38 +0100
Subject: No ssh or sshd online manpages?
In-Reply-To: <Pine.LNX.4.44.0310280134470.10032-100000@vader.aacc.edu>
References: <20031027140915.GA420@arthur.nitro.dk>
	<Pine.LNX.4.44.0310280134470.10032-100000@vader.aacc.edu>
Message-ID: <20031029142737.GA16577@freno.cs.tu-berlin.de>

On 2003-10-28 01:44:46 -0500, Michel Lavondes wrote:
> > On 2003.10.23 16:32:32 -0400, Michel Lavondes wrote:
> > > On Thu, 23 Oct 2003, Marc Fonvieille wrote:
> > > 
> > > > On Thu, Oct 23, 2003 at 07:11:59AM -0400, Michel Lavondes wrote:
> > > > > 
> > > > > lynx http://www.FreeBSD.org/cgi/man.cgi?query=sshd&apropos=0&sektion=0&manpath=
> > > > > FreeBSD+4.8-stable&format=html
> > > > 
> > > > http://www.freebsd.org/cgi/man.cgi?query=ssh&apropos=0&sektion=0
> > > > &manpath=OpenBSD+3.3&format=html
> > > 
> > > What am I missing? (besides humility, that is. :-) )
> > 
> > It was a "bug" on www.FreeBSD.org, which has been fixed by Wolfram
> > Schneider (wosch@).
> 
> Thanks. Looks like the change took... but only for 4.8-RELEASE. 4.8-stable 
> and 4.9-RELEASE still claim not to know about it. (But for 4.9R, it could 
> be because there ain't no sich animal yet.) I haven't bothered to check 

I just fixed it for 4.9-RELEASE.

-Wolfram

-- 
Wolfram Schneider <wosch at FreeBSD.org> http://wolfram.schneider.org


From bsd at panke.de.FreeBSD.org  Wed Oct 29 15:31:15 2003
From: bsd at panke.de.FreeBSD.org (Wolfram Schneider)
Date: Wed, 29 Oct 2003 16:28:20 +0100
Subject: DocBook version of "PMake - A Tutorial"
In-Reply-To: <3F96B811.5070205@snafu.de>
References: <3F96B811.5070205@snafu.de>
Message-ID: <20031029152820.GA538@paula.panke.de.freebsd.org>

On 2003-10-22 19:02:09 +0200, Oliver Fischer wrote:
> In recent times I read the pmake tutorial very often. Unfortunately
> there is no 'online' version of the tutorial. Is it possible to create a 
> DocBook version? If yes, I would volunter for this work.

Hi Oliver,

the pmake tutorial is available at

http://docs.freebsd.org/44doc/
http://docs.freebsd.org/44doc/psd/12.make/paper.html

-Wolfram

-- 
Wolfram Schneider <wosch at freebsd.org> http://wolfram.schneider.org


From hiroo at oikumene.gcd.org  Wed Oct 29 16:30:24 2003
From: hiroo at oikumene.gcd.org (Hiroo Ono)
Date: Thu, 30 Oct 2003 01:18:48 +0900 (JST)
Subject: docs/58686: grammer correction in faq/book.sgml
Message-ID: <200310291618.h9TGImEk000833@barleycoren.oikumene.gcd.org>


>Number:         58686
>Category:       docs
>Synopsis:       grammer correction in faq/book.sgml
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 29 08:30:21 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Hiroo Ono
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
none
>Environment:
System: FreeBSD barleycoren.oikumene.gcd.org 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Wed Oct 22 00:22:53 JST 2003 hiroo at barleycoren.oikumene.gcd.org:/build/usr/src/sys/BARLEYCOREN i386


>Description:
	I think "...are likely be to be installed" should be
	"...are likely to be installed". It is in the question
	regarding toor-account.
>How-To-Repeat:

>Fix:
patch against rev.1.597

--- book.sgml.orig	2003-10-29 10:51:35.000000000 +0900
+++ book.sgml	2003-10-29 10:53:04.000000000 +0900
@@ -8922,7 +8922,7 @@
             you do not have to change <username>root</username>'s default
             shell. This is important as shells which are not part of the
             base distribution (for example a shell installed from ports or
-            packages) are likely be to be installed in
+            packages) are likely to be installed in
             <filename>/usr/local/bin</filename> which, by default, resides
             on a different filesystem. If <username>root</username>'s shell
             is located in <filename>/usr/local/bin</filename> and

>Release-Note:
>Audit-Trail:
>Unformatted:


From blackend at FreeBSD.org  Wed Oct 29 18:37:44 2003
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Wed, 29 Oct 2003 10:37:43 -0800 (PST)
Subject: docs/58686: grammer correction in faq/book.sgml
Message-ID: <200310291837.h9TIbhK1053006@freefall.freebsd.org>

Synopsis: grammer correction in faq/book.sgml

State-Changed-From-To: open->closed
State-Changed-By: blackend
State-Changed-When: Wed Oct 29 10:37:16 PST 2003
State-Changed-Why: 
Fixed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=58686


From adamw at magnesium.net  Thu Oct 30 04:15:59 2003
From: adamw at magnesium.net (Adam Weinberger)
Date: 29 Oct 2003 23:15:58 -0500
Subject: main page improvement
Message-ID: <20031030041558.GM96543@toxic.magnesium.net>

I made an improvement to the freebsd.org main page.

You can see the improvement at:

	http://magnesium.net/~adamw/tmp/fbsd/

marcus@ indicated that I should run it by you guys before I commit.

# Adam


--
Adam Weinberger
vectors.cx	>>  adam at vectors.cx	>>  http://www.vectors.cx
magnesium.net	<<  adamw at magnesium.net	<<  http://www.magnesium.net/~adamw
FreeBSD		>>  adamw at FreeBSD.org	>>  http://people.freebsd.org/~adamw
#vim:set ts=8: 8-char tabs prevent tooth decay.


From trhodes at FreeBSD.org  Thu Oct 30 05:12:55 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 30 Oct 2003 01:12:48 -0500
Subject: main page improvement
In-Reply-To: <20031030041558.GM96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
Message-ID: <20031030011248.625593be.trhodes@FreeBSD.org>

On 29 Oct 2003 23:15:58 -0500
Adam Weinberger <adamw at magnesium.net> wrote:

> I made an improvement to the freebsd.org main page.
> 
> You can see the improvement at:
> 
> 	http://magnesium.net/~adamw/tmp/fbsd/
> 
> marcus@ indicated that I should run it by you guys before I commit.

You're kidding, right?  Are the stars intentional here?

Note, I'm not trying to be rude or anything, I'm just asking.

-- 
Tom Rhodes


From adamw at FreeBSD.org  Thu Oct 30 05:20:24 2003
From: adamw at FreeBSD.org (Adam Weinberger)
Date: 30 Oct 2003 00:20:22 -0500
Subject: main page improvement
In-Reply-To: <20031030011248.625593be.trhodes@FreeBSD.org>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
Message-ID: <20031030052022.GP96543@toxic.magnesium.net>

>> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> On 29 Oct 2003 23:15:58 -0500
> Adam Weinberger <adamw at magnesium.net> wrote:
> 
> > I made an improvement to the freebsd.org main page.
> > 
> > You can see the improvement at:
> > 
> > 	http://magnesium.net/~adamw/tmp/fbsd/
> > 
> > marcus@ indicated that I should run it by you guys before I commit.
> 
> You're kidding, right?  Are the stars intentional here?
> 
> Note, I'm not trying to be rude or anything, I'm just asking.
> 
> -- 
> Tom Rhodes
>> end of "Re: main page improvement" from Tom Rhodes <<

Noone can claim that *BSD is dead when the frontpage is so obviously
full of glittery life!

# Adam


--
Adam Weinberger
vectors.cx	>>  adam at vectors.cx	>>  http://www.vectors.cx
magnesium.net	<<  adamw at magnesium.net	<<  http://www.magnesium.net/~adamw
FreeBSD		>>  adamw at FreeBSD.org	>>  http://people.freebsd.org/~adamw
#vim:set ts=8: 8-char tabs prevent tooth decay.


From kensmith at cse.Buffalo.EDU  Thu Oct 30 05:24:14 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Thu, 30 Oct 2003 00:24:12 -0500
Subject: main page improvement
In-Reply-To: <20031030041558.GM96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
Message-ID: <20031030052412.GC15105@electra.cse.Buffalo.EDU>

On Wed, Oct 29, 2003 at 11:15:58PM -0500, Adam Weinberger wrote:
> I made an improvement to the freebsd.org main page.
> 
> You can see the improvement at:
> 
> 	http://magnesium.net/~adamw/tmp/fbsd/
> 
> marcus@ indicated that I should run it by you guys before I commit.

If I have a vote it would be 'please no'.  Other peoples' opinions
vary but in my case motion on a Web page I tend to hover on drives me
nuts.  It makes the text a bit harder for me to read even though I
have no color viewing disabilities (I'm aware of anyway), so that
could cause problems for people who do have [partial] color blindness.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From trhodes at FreeBSD.org  Thu Oct 30 05:29:41 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 30 Oct 2003 01:29:35 -0500
Subject: main page improvement
In-Reply-To: <20031030052022.GP96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
	<20031030052022.GP96543@toxic.magnesium.net>
Message-ID: <20031030012935.7accd561.trhodes@FreeBSD.org>

On 30 Oct 2003 00:20:22 -0500
Adam Weinberger <adamw at freebsd.org> wrote:

> >> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> > On 29 Oct 2003 23:15:58 -0500
> > Adam Weinberger <adamw at magnesium.net> wrote:
> > 
> > > I made an improvement to the freebsd.org main page.
> > > 
> > > You can see the improvement at:
> > > 
> > > 	http://magnesium.net/~adamw/tmp/fbsd/
> > > 
> > > marcus@ indicated that I should run it by you guys before I commit.
> > 
> > You're kidding, right?  Are the stars intentional here?
> > 
> > Note, I'm not trying to be rude or anything, I'm just asking.
> > 
> > -- 
> > Tom Rhodes
> >> end of "Re: main page improvement" from Tom Rhodes <<
> 
> Noone can claim that *BSD is dead when the frontpage is so obviously
> full of glittery life!

Well, it's a bit to happy for me.  Perhaps, since we are in Halloween
in America, we use coffins?  Other countries can design the decore around
their 'holidays'.  :)

-- 
Tom Rhodes


From adamw at FreeBSD.org  Thu Oct 30 05:32:38 2003
From: adamw at FreeBSD.org (Adam Weinberger)
Date: 30 Oct 2003 00:32:37 -0500
Subject: main page improvement
In-Reply-To: <20031030012935.7accd561.trhodes@FreeBSD.org>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
	<20031030052022.GP96543@toxic.magnesium.net>
	<20031030012935.7accd561.trhodes@FreeBSD.org>
Message-ID: <20031030053237.GQ96543@toxic.magnesium.net>

>> (10.30.2003 @ 0129 PST): Tom Rhodes said, in 0.9K: <<
> On 30 Oct 2003 00:20:22 -0500
> Adam Weinberger <adamw at freebsd.org> wrote:
> 
> > >> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> > > On 29 Oct 2003 23:15:58 -0500
> > > Adam Weinberger <adamw at magnesium.net> wrote:
> > > 
> > > > I made an improvement to the freebsd.org main page.
> > > > 
> > > > You can see the improvement at:
> > > > 
> > > > 	http://magnesium.net/~adamw/tmp/fbsd/
> > > > 
> > > > marcus@ indicated that I should run it by you guys before I commit.
> > > 
> > > You're kidding, right?  Are the stars intentional here?
> > > 
> > > Note, I'm not trying to be rude or anything, I'm just asking.
> > > 
> > > -- 
> > > Tom Rhodes
> > >> end of "Re: main page improvement" from Tom Rhodes <<
> > 
> > Noone can claim that *BSD is dead when the frontpage is so obviously
> > full of glittery life!
> 
> Well, it's a bit to happy for me.  Perhaps, since we are in Halloween
> in America, we use coffins?  Other countries can design the decore around
> their 'holidays'.  :)
> 
> -- 
> Tom Rhodes
>> end of "Re: main page improvement" from Tom Rhodes <<

I'm not sure that animated coffins would relay the sentiment that *BSD
is NOT dead.

# Adam


--
Adam Weinberger
vectors.cx	>>  adam at vectors.cx	>>  http://www.vectors.cx
magnesium.net	<<  adamw at magnesium.net	<<  http://www.magnesium.net/~adamw
FreeBSD		>>  adamw at FreeBSD.org	>>  http://people.freebsd.org/~adamw
#vim:set ts=8: 8-char tabs prevent tooth decay.


From trhodes at FreeBSD.org  Thu Oct 30 05:46:45 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 30 Oct 2003 01:46:36 -0500
Subject: main page improvement
In-Reply-To: <20031030053237.GQ96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
	<20031030052022.GP96543@toxic.magnesium.net>
	<20031030012935.7accd561.trhodes@FreeBSD.org>
	<20031030053237.GQ96543@toxic.magnesium.net>
Message-ID: <20031030014636.6a129cf8.trhodes@FreeBSD.org>

On 30 Oct 2003 00:32:37 -0500
Adam Weinberger <adamw at freebsd.org> wrote:

> >> (10.30.2003 @ 0129 PST): Tom Rhodes said, in 0.9K: <<
> > On 30 Oct 2003 00:20:22 -0500
> > Adam Weinberger <adamw at freebsd.org> wrote:
> > 
> > > >> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> > > > On 29 Oct 2003 23:15:58 -0500
> > > > Adam Weinberger <adamw at magnesium.net> wrote:
> > > > 
> > > > > I made an improvement to the freebsd.org main page.
> > > > > 
> > > > > You can see the improvement at:
> > > > > 
> > > > > 	http://magnesium.net/~adamw/tmp/fbsd/
> > > > > 
> > > > > marcus@ indicated that I should run it by you guys before I commit.
> > > > 
> > > > You're kidding, right?  Are the stars intentional here?
> > > > 
> > > > Note, I'm not trying to be rude or anything, I'm just asking.
> > > > 
> > > > -- 
> > > > Tom Rhodes
> > > >> end of "Re: main page improvement" from Tom Rhodes <<
> > > 
> > > Noone can claim that *BSD is dead when the frontpage is so obviously
> > > full of glittery life!
> > 
> > Well, it's a bit to happy for me.  Perhaps, since we are in Halloween
> > in America, we use coffins?  Other countries can design the decore around
> > their 'holidays'.  :)
> > 
> > -- 
> > Tom Rhodes
> >> end of "Re: main page improvement" from Tom Rhodes <<
> 
> I'm not sure that animated coffins would relay the sentiment that *BSD
> is NOT dead.

Perhaps a few skulls then...  I think the coffines would be neat though.

:)

-- 
Tom Rhodes


From adamw at FreeBSD.org  Thu Oct 30 05:50:21 2003
From: adamw at FreeBSD.org (Adam Weinberger)
Date: 30 Oct 2003 00:50:16 -0500
Subject: main page improvement
In-Reply-To: <20031030014636.6a129cf8.trhodes@FreeBSD.org>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
	<20031030052022.GP96543@toxic.magnesium.net>
	<20031030012935.7accd561.trhodes@FreeBSD.org>
	<20031030053237.GQ96543@toxic.magnesium.net>
	<20031030014636.6a129cf8.trhodes@FreeBSD.org>
Message-ID: <20031030055016.GR96543@toxic.magnesium.net>

>> (10.30.2003 @ 0146 PST): Tom Rhodes said, in 1.4K: <<
> On 30 Oct 2003 00:32:37 -0500
> Adam Weinberger <adamw at freebsd.org> wrote:
> 
> > >> (10.30.2003 @ 0129 PST): Tom Rhodes said, in 0.9K: <<
> > > On 30 Oct 2003 00:20:22 -0500
> > > Adam Weinberger <adamw at freebsd.org> wrote:
> > > 
> > > > >> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> > > > > On 29 Oct 2003 23:15:58 -0500
> > > > > Adam Weinberger <adamw at magnesium.net> wrote:
> > > > > 
> > > > > > I made an improvement to the freebsd.org main page.
> > > > > > 
> > > > > > You can see the improvement at:
> > > > > > 
> > > > > > 	http://magnesium.net/~adamw/tmp/fbsd/
> > > > > > 
> > > > > > marcus@ indicated that I should run it by you guys before I commit.
> > > > > 
> > > > > You're kidding, right?  Are the stars intentional here?
> > > > > 
> > > > > Note, I'm not trying to be rude or anything, I'm just asking.
> > > > > 
> > > > > -- 
> > > > > Tom Rhodes
> > > > >> end of "Re: main page improvement" from Tom Rhodes <<
> > > > 
> > > > Noone can claim that *BSD is dead when the frontpage is so obviously
> > > > full of glittery life!
> > > 
> > > Well, it's a bit to happy for me.  Perhaps, since we are in Halloween
> > > in America, we use coffins?  Other countries can design the decore around
> > > their 'holidays'.  :)
> > > 
> > > -- 
> > > Tom Rhodes
> > >> end of "Re: main page improvement" from Tom Rhodes <<
> > 
> > I'm not sure that animated coffins would relay the sentiment that *BSD
> > is NOT dead.
> 
> Perhaps a few skulls then...  I think the coffines would be neat though.
> 
> :)
> 
> -- 
> Tom Rhodes
>> end of "Re: main page improvement" from Tom Rhodes <<

OK. That's it. I'm making a goth lingua type that spits out angsty
poetry for all system messages.

# Adam


--
Adam Weinberger
vectors.cx	>>  adam at vectors.cx	>>  http://www.vectors.cx
magnesium.net	<<  adamw at magnesium.net	<<  http://www.magnesium.net/~adamw
FreeBSD		>>  adamw at FreeBSD.org	>>  http://people.freebsd.org/~adamw
#vim:set ts=8: 8-char tabs prevent tooth decay.


From trhodes at FreeBSD.org  Thu Oct 30 05:56:29 2003
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu, 30 Oct 2003 01:56:21 -0500
Subject: main page improvement
In-Reply-To: <20031030055016.GR96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030011248.625593be.trhodes@FreeBSD.org>
	<20031030052022.GP96543@toxic.magnesium.net>
	<20031030012935.7accd561.trhodes@FreeBSD.org>
	<20031030053237.GQ96543@toxic.magnesium.net>
	<20031030014636.6a129cf8.trhodes@FreeBSD.org>
	<20031030055016.GR96543@toxic.magnesium.net>
Message-ID: <20031030015621.70c94cd6.trhodes@FreeBSD.org>

On 30 Oct 2003 00:50:16 -0500
Adam Weinberger <adamw at freebsd.org> wrote:

> >> (10.30.2003 @ 0146 PST): Tom Rhodes said, in 1.4K: <<
> > On 30 Oct 2003 00:32:37 -0500
> > Adam Weinberger <adamw at freebsd.org> wrote:
> > 
> > > >> (10.30.2003 @ 0129 PST): Tom Rhodes said, in 0.9K: <<
> > > > On 30 Oct 2003 00:20:22 -0500
> > > > Adam Weinberger <adamw at freebsd.org> wrote:
> > > > 
> > > > > >> (10.30.2003 @ 0112 PST): Tom Rhodes said, in 0.4K: <<
> > > > > > On 29 Oct 2003 23:15:58 -0500
> > > > > > Adam Weinberger <adamw at magnesium.net> wrote:
> > > > > > 
> > > > > > > I made an improvement to the freebsd.org main page.
> > > > > > > 
> > > > > > > You can see the improvement at:
> > > > > > > 
> > > > > > > 	http://magnesium.net/~adamw/tmp/fbsd/
> > > > > > > 
> > > > > > > marcus@ indicated that I should run it by you guys before I commit.
> > > > > > 
> > > > > > You're kidding, right?  Are the stars intentional here?
> > > > > > 
> > > > > > Note, I'm not trying to be rude or anything, I'm just asking.
> > > > > > 
> > > > > > -- 
> > > > > > Tom Rhodes
> > > > > >> end of "Re: main page improvement" from Tom Rhodes <<
> > > > > 
> > > > > Noone can claim that *BSD is dead when the frontpage is so obviously
> > > > > full of glittery life!
> > > > 
> > > > Well, it's a bit to happy for me.  Perhaps, since we are in Halloween
> > > > in America, we use coffins?  Other countries can design the decore around
> > > > their 'holidays'.  :)
> > > > 
> > > > -- 
> > > > Tom Rhodes
> > > >> end of "Re: main page improvement" from Tom Rhodes <<
> > > 
> > > I'm not sure that animated coffins would relay the sentiment that *BSD
> > > is NOT dead.
> > 
> > Perhaps a few skulls then...  I think the coffines would be neat though.
> > 
> > :)
> > 
> > -- 
> > Tom Rhodes
> >> end of "Re: main page improvement" from Tom Rhodes <<
> 
> OK. That's it. I'm making a goth lingua type that spits out angsty
> poetry for all system messages.


I love you.  :)

I can see it now:

syslogd with hand stapled to forehead: *bad poetry about something
that usually errors goes here*

-- 
Tom Rhodes


From ryany at pobox.com  Thu Oct 30 08:40:12 2003
From: ryany at pobox.com (Ryan Younce)
Date: Thu, 30 Oct 2003 03:32:17 -0500 (EST)
Subject: docs/58710: killpg(2) contains an error regarding sending SIGCONT
Message-ID: <20031030083217.F0A4B11460@turing.vangyzen.net>


>Number:         58710
>Category:       docs
>Synopsis:       killpg(2) contains an error regarding sending SIGCONT
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 30 00:40:08 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ryan Younce
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
FreeBSD kara 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Mon Oct  6 22:31:51 GMT 2003     root at kara:/usr/src/sys/i386/compile/KARA  i386

>Description:

	This is akin to PR docs/58413.

	The killpg(2) manual page in /usr/src/lib/libc/compat-43/killpg.2
	has the same error the kill(2) manpage had before the commit for
	the aforementioned PR, specifically the text:

	"As a single special case the continue signal SIGCONT may be sent
	to any process that is a descendant of the current process."

	This is incorrect:  as in the case for kill(2), SIGCONT may be
	sent, regardless of credentials, to any process in the same
	session; it is neither sufficient nor necessary for the recipient
	to be a descendent if user IDs differ.

	Since killpg() relies on kill(), which relies on killpg1() in
	/sys/kern/kern_sig.c, which relies on p_cansignal() in
	/sys/kern/kern_prot.c, the semantics are the same.  This has 
	also been tested.

>How-To-Repeat:

	man 2 killpg

>Fix:

	Change sentence in question to:

	"As a single special case the continue signal SIGCONT may be sent
	to any process with the same session ID as the caller.
>Release-Note:
>Audit-Trail:
>Unformatted:


From setantae at submonkey.net  Thu Oct 30 10:31:05 2003
From: setantae at submonkey.net (Ceri Davies)
Date: Thu, 30 Oct 2003 10:30:56 +0000
Subject: main page improvement
In-Reply-To: <20031030041558.GM96543@toxic.magnesium.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
Message-ID: <20031030103056.GF38355@submonkey.net>

On Wed, Oct 29, 2003 at 11:15:58PM -0500, Adam Weinberger wrote:
> I made an improvement to the freebsd.org main page.
> 
> You can see the improvement at:
> 
> 	http://magnesium.net/~adamw/tmp/fbsd/
> 
> marcus@ indicated that I should run it by you guys before I commit.

If I asked you once, I asked you a thousand times; I *still* don't see
those dancing daemons and I *still* don't hear the Can Can.

Ceri

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031030/9fa26ac3/attachment.sig>

From kensmith at cse.Buffalo.EDU  Thu Oct 30 11:19:03 2003
From: kensmith at cse.Buffalo.EDU (Ken Smith)
Date: Thu, 30 Oct 2003 06:19:01 -0500
Subject: main page improvement
In-Reply-To: <20031030103056.GF38355@submonkey.net>
References: <20031030041558.GM96543@toxic.magnesium.net>
	<20031030103056.GF38355@submonkey.net>
Message-ID: <20031030111901.GA20772@electra.cse.Buffalo.EDU>

On Thu, Oct 30, 2003 at 10:30:56AM +0000, Ceri Davies wrote:

> If I asked you once, I asked you a thousand times; I *still* don't see
> those dancing daemons and I *still* don't hear the Can Can.

And I still haven't learned to keep my mouth shut until seeing
what a few of the people who have been around longer than me
have to say...

Sigh.  Sorry Adam.

I once dressed a VAX-11 up for Halloween.  At the time we had
a couple around - I ran a few running 4.3BSD and the Computing
Center had a couple running VMS.  I rewrote login(8) to make
it look exactly like a VMS login, and had "Happy Halloween,
how do you like gort's constume" in the motd.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


From bdaniel7 at yahoo.com  Fri Oct 31 08:57:22 2003
From: bdaniel7 at yahoo.com (=?iso-8859-1?q?Daniel=20Blendea?=)
Date: Fri, 31 Oct 2003 08:57:18 +0000 (GMT)
Subject: questions about the site
Message-ID: <20031031085718.57108.qmail@web40412.mail.yahoo.com>

Hello, i'm a very enthusiastic user, promoter of FreeBSD and while visiting the main site i've found this:
"

...build a new central server machine, which has replaced freefall.FreeBSD.org at one point, by donating the following items:

   
...and his employer, ..., donated a Pentium Pro (P6) 200MHz CPU


"

is this true? freebsd.org sits on a P2 at 200MHz?
if not, i'm curious about the main hardware detalis: cpu, ram, hdd
 
Thank you very much,
 
Daniel


---------------------------------
Want to chat instantly with your online friends??Get the FREE Yahoo!Messenger


From rushani at bl.mmtr.or.jp  Fri Oct 31 10:13:01 2003
From: rushani at bl.mmtr.or.jp (Hideyuki KURASHINA)
Date: Fri, 31 Oct 2003 19:12:03 +0900 (JST)
Subject: questions about the site
In-Reply-To: <20031031085718.57108.qmail@web40412.mail.yahoo.com>
References: <20031031085718.57108.qmail@web40412.mail.yahoo.com>
Message-ID: <20031031.191203.99879832.rushani@bl.mmtr.or.jp>

Hi,

>>> On Fri, 31 Oct 2003 08:57:18 +0000 (GMT), Daniel Blendea <bdaniel7 at yahoo.com> said:

> is this true? freebsd.org sits on a P2 at 200MHz?
> if not, i'm curious about the main hardware detalis: cpu, ram, hdd

Look at following page for details.  The answer has to be found.

  The FreeBSD.org Network
    http://www.FreeBSD.org/internal/machines.html

thanks,

-- rushani


From bmah at freebsd.org  Fri Oct 31 15:39:13 2003
From: bmah at freebsd.org (Bruce A. Mah)
Date: Fri, 31 Oct 2003 07:39:09 -0800
Subject: HEADS-UP: doc/ tree slushie 
In-Reply-To: <20031020234327.GA61488@intruder.kitchenlab.org> 
References: <200310190613.h9J6DAnB035928@intruder.kitchenlab.org>
	<200310200414.h9K4EInB049618@intruder.kitchenlab.org>
	<3F936C7E.9020904@centtech.com>
	<20031020151209.GA55608@intruder.kitchenlab.org>
	<20031020152939.GE3708@submonkey.net>
	<20031020161606.GA56817@intruder.kitchenlab.org>
	<20031020221929.GF3708@submonkey.net>
	<20031020222724.GA60569@intruder.kitchenlab.org>
	<20031020223315.GH3708@submonkey.net>
	<20031020234327.GA61488@intruder.kitchenlab.org>
Message-ID: <200310311539.h9VFd91j016727@intruder.kitchenlab.org>

I wrote:

> Back on topic, I've tagged doc/ with the RELEASE_4_9_0 tag and I'm
> doing a test build to make sure it's all happy now.  If all goes well,
> I'll wait some appropriate amount of time and then commit the version
> number bump patch and slide the tags.

This message was intended to mark the end of the doc/ slush, but it's
been pointed out to me that I never explicitly said "the doc/ tree is
open".  Thanks to Simon Nielsen for reminding me of this...sorry if this
caused any inconvenience.

Once again:  doc/ is wide open, commit at will.

Bruce.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 223 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031031/a0993aab/attachment.sig>

From mark at summersault.com  Fri Oct 31 20:40:15 2003
From: mark at summersault.com (Mark Stosberg)
Date: 31 Oct 2003 20:30:57 -0000
Subject: docs/58783: crontab	man could mention MAILTO supports mult.
	addresses
Message-ID: <20031031203057.93688.qmail@tanagra.summersault.com>


>Number:         58783
>Category:       docs
>Synopsis:       crontab	man could mention MAILTO supports mult. addresses
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 31 12:40:12 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Mark Stosberg
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
System: FreeBSD tanagra.summersault.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 root at builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC i386
>Description:
Today I discovered that I can set "MAILTO" to a comma separated list of addresses in my crontab. 
>From "man 5 crontab", it made no mention of using more than one address.
I think it would be a welcome, if minor, enhancement to mention this in the man page. 

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


From simon at FreeBSD.org  Fri Oct 31 21:52:39 2003
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Fri, 31 Oct 2003 22:52:37 +0100
Subject: No ssh or sshd online manpages?
In-Reply-To: <Pine.LNX.4.44.0310280134470.10032-100000@vader.aacc.edu>
References: <20031027140915.GA420@arthur.nitro.dk>
	<Pine.LNX.4.44.0310280134470.10032-100000@vader.aacc.edu>
Message-ID: <20031031215235.GI404@arthur.nitro.dk>

On 2003.10.28 01:44:46 -0500, Michel Lavondes wrote:

> Also, in sshd_config.5 (the local version, not the one fresh from the 
> openssh tree):

The text is only in the FreeBSD version of the manual page.

> 
>      PasswordAuthentication
>              Specifies whether password authentication is allowed.  The
>              default is ``yes''.  Note that ChallengeResponseAuthentication is
> Shirley there should be an "if" there? ---^^^
>              ``yes'', and the PAM authentication policy for sshd includes

Indeed you are correct.  I just committed a fix to -CURRENT.

Thanks for letting us know about it.

-- 
Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20031031/3e5e5acb/attachment.sig>

From fox at vader.aacc.cc.md.us  Fri Oct 31 22:28:53 2003
From: fox at vader.aacc.cc.md.us (Michel Lavondes)
Date: Fri, 31 Oct 2003 17:28:41 -0500 (EST)
Subject: No ssh or sshd online manpages?
In-Reply-To: <20031031215235.GI404@arthur.nitro.dk>
Message-ID: <Pine.LNX.4.44.0310311725270.30653-100000@vader.aacc.edu>

On Fri, 31 Oct 2003, Simon L. Nielsen wrote:

> On 2003.10.28 01:44:46 -0500, Michel Lavondes wrote:
> 
> > Also, in sshd_config.5 (the local version, not the one fresh from the 
> > openssh tree):
> 
> The text is only in the FreeBSD version of the manual page.

I know. That was just me checking the "I know there are 2 versions, and
I'm reporting it here because the version with the problem is the FreeBSD
one, not because I'm too lazy or clueless to bother looking" box. :-)

-- 
Remember: i before e, except on Unix machines.