From owner-freebsd-doc Wed Jan 16 12:56:25 2002 Delivered-To: freebsd-doc@freebsd.org Received: from marvin.nildram.co.uk (marvin.nildram.co.uk [195.112.4.71]) by hub.freebsd.org (Postfix) with SMTP id 6F71C37B417 for ; Wed, 16 Jan 2002 12:56:04 -0800 (PST) Received: (qmail 27146 invoked from network); 16 Jan 2002 20:56:02 -0000 Received: from muttley.gotadsl.co.uk (HELO VicNBob) (213.208.123.26) by marvin.nildram.co.uk with SMTP; 16 Jan 2002 20:56:02 -0000 From: Matthew Whelan To: stable@FreeBSD.ORG, "John Nielsen" Cc: freebsd-doc@FreeBSD.ORG Date: Wed, 16 Jan 2002 20:55:53 -0000 X-Priority: 3 (Normal) In-Reply-To: <080801c19e6e$4712f360$0900a8c0@max> Message-Id: Subject: Re: typo in man ed (4) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------DI8Hk+OxDPTC0PXfZp0SoI" X-Mailer: Opera 6.0 build 1010 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ------------DI8Hk+OxDPTC0PXfZp0SoI Content-Type: text/plain; charset="iso-8859-1" CC'ed to docs@ who should be interested 16/01/2002 09:15:01, "John Nielsen" wrote: >This is something that's bitten me on the two occasions I've needed to use >it, so I'm hoping it can get fixed. > >In the CAVEATS section of the ed (4) manpage, it says this: > > 16bit Compex cards identify themselves as being 8bit. While these >cards > will work in 8bit mode, much higher performance can be achieved by >speci- > fying "flags 0x04" (force 16bit mode) in your kernel config file. In >addi- > tion, you should also specify "iosize 16384" to take advantage of the >extra > 8k of shared memory that 16bit mode provides. > >If you put the word "iosize" in a kernel config file it produces a syntax >error. It should be "iosiz" (without the 'e'). > >I'm not familiar with the procedure(s) for fixing typos like this, but if >one of you could enlighten me and/or just take care of it I'd be >appreciative. Thanks, > >JN Source for ed(4) is /usr/src/share/man/man4/ed.4, the attached patch should fix the problem. Normal procedure for getting this addressed would be to fire a mail at docs@ (as it is a documentation problem) and/or file a PR (using send-pr or http://www.freebsd.org/send-pr.html) Yours, Matthew ------------DI8Hk+OxDPTC0PXfZp0SoI Content-Disposition: attachment; filename="ed.4.patch" Content-Type: application/octet-stream; name="ed.4.patch" Content-Transfer-Encoding: Base64 KioqIGVkLjQJV2VkIEphbiAxNiAyMDoyOToyOSAyMDAyCi0tLSBlZC40Lm5l dwlXZWQgSmFuIDE2IDIwOjMwOjA3IDIwMDIKKioqKioqKioqKioqKioqCioq KiAxNzUsMTgxICoqKioKICAuRW0gImZsYWdzIDB4MDQiCiAgKGZvcmNlIDE2 Yml0IG1vZGUpIGluIHlvdXIga2VybmVsIGNvbmZpZyBmaWxlLgogIEluIGFk ZGl0aW9uLCB5b3Ugc2hvdWxkIGFsc28gc3BlY2lmeQohIC5FbSAiaW9zaXpl IDE2Mzg0IgogIHRvIHRha2UgYWR2YW50YWdlIG9mIHRoZSBleHRyYSA4ayBv ZiBzaGFyZWQgbWVtb3J5IHRoYXQgMTZiaXQgbW9kZSBwcm92aWRlcy4KICAu U2ggQlVHUwogIFRoZQotLS0gMTc1LDE4MSAtLS0tCiAgLkVtICJmbGFncyAw eDA0IgogIChmb3JjZSAxNmJpdCBtb2RlKSBpbiB5b3VyIGtlcm5lbCBjb25m aWcgZmlsZS4KICBJbiBhZGRpdGlvbiwgeW91IHNob3VsZCBhbHNvIHNwZWNp ZnkKISAuRW0gImlvc2l6IDE2Mzg0IgogIHRvIHRha2UgYWR2YW50YWdlIG9m IHRoZSBleHRyYSA4ayBvZiBzaGFyZWQgbWVtb3J5IHRoYXQgMTZiaXQgbW9k ZSBwcm92aWRlcy4KICAuU2ggQlVHUwogIFRoZQo= ------------DI8Hk+OxDPTC0PXfZp0SoI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message