From yasir27 at mail.ru Sat Jan 2 15:10:05 2010
From: yasir27 at mail.ru (Yasir)
Date: Sat, 2 Jan 2010 15:04:14 GMT
Subject: docs/142243: Netcat (nc(1)) manual mistake
Message-ID: <201001021504.o02F4EAU016709@www.freebsd.org>
>Number: 142243
>Category: docs
>Synopsis: Netcat (nc(1)) manual mistake
>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 Jan 02 15:10:04 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Yasir
>Release: 7.1-RELEASE
>Organization:
>Environment:
FreeBSD conductor.loc 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root at logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
man 1 nc states in TALKING TO SERVERS section:
[..]
For example, to retrieve the home page of a web site:
$ echo -n "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80
[..]
But this kind of request often returns either nothing or something irrelevant, maybe due to a strong server implementation (e.g. meets RFCs).
>How-To-Repeat:
According to man one could do the following:
$ echo "GET / HTTP/1.0\r\n\r\n" | nc example.com 80
But nothing is returned upon request.
Another attempt which also fails:
$ echo "HEAD / HTTP/1.0\r\n\r\n" | nc ya.ru 80
400 Bad Request
400 Bad Request
nginx
>Fix:
There should have been used printf(1) instead.
Man should be corrected, namely, sed 's/echo -n/printf/'
>Release-Note:
>Audit-Trail:
>Unformatted:
From swehack at gmail.com Sat Jan 2 16:09:38 2010
From: swehack at gmail.com (Stefan Midjich)
Date: Sat, 2 Jan 2010 16:46:00 +0100
Subject: Writing Device Drivers needs updating?
Message-ID:
Hi
I'm trying to find the file of majors, /usr/src/sys/conf/majors, as i was
advised to read it from the online handbook.
http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-char.html
I cannot find it though, does anyone know if it has been replaced or
something? I obviously have the full ssys set for 8.0-RELEASE but i've also
tried on an older 7.0 installation and it is not there either.
Perhaps this documentation needs updating.
Also the manual for mknod(8) mentions this file.
My question is where is the new version of the file?
--
Med v?nliga h?lsningar / With kind regards
Stefan Midjich
http://swehack.se/cv
https://www.swehack.se/cv
From yarsanukaev at gmail.com Sat Jan 2 16:50:03 2010
From: yarsanukaev at gmail.com (Yasir Arsanukaev)
Date: Sat, 2 Jan 2010 16:50:03 GMT
Subject: docs/142243: Netcat (nc(1)) manual mistake
Message-ID: <201001021650.o02Go3wq075091@freefall.freebsd.org>
The following reply was made to PR docs/142243; it has been noted by GNATS.
From: Yasir Arsanukaev
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/142243: Netcat (nc(1)) manual mistake
Date: Sun, 3 Jan 2010 02:26:45 +1000
--00032555843a449031047c30f459
Content-Type: text/plain; charset=UTF-8
While echo in bash(1), sh(1) and csh(1) don't handle '\n' and '\r' properly,
I've discovered echo works correctly in zsh(1).
Patch is attached and can be applied this way:
$ patch /usr/src/contrib/netcat/nc.1 < nc.1.diff
The other way is to mention that example works only in zsh.
--00032555843a449031047c30f459
Content-Type: application/octet-stream; name="nc.1.diff"
Content-Disposition: attachment; filename="nc.1.diff"
Content-Transfer-Encoding: base64
X-Attachment-Id: file0
LS0tIG5jLjEJMjAwOC0xMS0yNSAxMjo1OToyOS4wMDAwMDAwMDAgKzEwMDAKKysrIG5jLjEubmV3
CTIwMTAtMDEtMDMgMDM6MTg6MzMuMDAwMDAwMDAwICsxMDAwCkBAIC0zMzEsNyArMzMxLDcgQEAK
IGluIHJlc3BvbnNlIHRvIGNvbW1hbmRzIGlzc3VlZCBieSB0aGUgY2xpZW50LgogRm9yIGV4YW1w
bGUsIHRvIHJldHJpZXZlIHRoZSBob21lIHBhZ2Ugb2YgYSB3ZWIgc2l0ZToKIC5CZCAtbGl0ZXJh
bCAtb2Zmc2V0IGluZGVudAotJCBlY2hvIC1uICJHRVQgLyBIVFRQLzEuMFxlclxlblxlclxlbiIg
fCBuYyBob3N0LmV4YW1wbGUuY29tIDgwCiskIHByaW50ZiAiR0VUIC8gSFRUUC8xLjBcZXJcZW5c
ZXJcZW4iIHwgbmMgaG9zdC5leGFtcGxlLmNvbSA4MAogLkVkCiAuUHAKIE5vdGUgdGhhdCB0aGlz
IGFsc28gZGlzcGxheXMgdGhlIGhlYWRlcnMgc2VudCBieSB0aGUgd2ViIHNlcnZlci4K
--00032555843a449031047c30f459--
From pluknet at gmail.com Sat Jan 2 16:58:59 2010
From: pluknet at gmail.com (pluknet)
Date: Sat, 2 Jan 2010 19:58:53 +0300
Subject: Writing Device Drivers needs updating?
In-Reply-To:
References:
Message-ID:
2010/1/2 Stefan Midjich :
> Hi
>
> I'm trying to find the file of majors, /usr/src/sys/conf/majors, as i was
> advised to read it from the online handbook.
>
> http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-char.html
>
> I cannot find it though, does anyone know if it has been replaced or
> something? I obviously have the full ssys set for 8.0-RELEASE but i've also
> tried on an older 7.0 installation and it is not there either.
>
> Perhaps this documentation needs updating.
No, since the example mentioned in the article describes 4.x era.
Though it should be removed entirely as obsolete.
>
> Also the manual for mknod(8) mentions this file.
No longer in HEAD (should be fixed in 8.x past .0 as well, but not yet).
--
wbr,
pluknet
From dougb at FreeBSD.org Sat Jan 2 19:00:08 2010
From: dougb at FreeBSD.org (Doug Barton)
Date: Sat, 2 Jan 2010 19:00:08 GMT
Subject: docs/142243: Netcat (nc(1)) manual mistake
Message-ID: <201001021900.o02J08Ug086194@freefall.freebsd.org>
The following reply was made to PR docs/142243; it has been noted by GNATS.
From: Doug Barton
To: Yasir
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: docs/142243: Netcat (nc(1)) manual mistake
Date: Sat, 02 Jan 2010 10:57:44 -0800
Yasir wrote:
>> Fix:
> There should have been used printf(1) instead.
> Man should be corrected, namely, sed 's/echo -n/printf/'
printf should always work, yes. In our sh and in bash, 'echo -e' will
also work.
hth,
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
From masoom.shaikh at gmail.com Sun Jan 3 06:55:17 2010
From: masoom.shaikh at gmail.com (Masoom Shaikh)
Date: Sun, 3 Jan 2010 12:02:37 +0000
Subject: Fwd: COMPAT_LINUX instead if COMPAT_LINUX32 in man page
Message-ID: <201001031202.37217.masoom.shaikh@gmail.com>
-------------- next part --------------
An embedded message was scrubbed...
From: Masoom Shaikh
Subject: COMPAT_LINUX instead if COMPAT_LINUX32 in man page
Date: Fri, 1 Jan 2010 12:16:26 +0000
Size: 1215
URL:
From linimon at FreeBSD.org Sun Jan 3 07:35:26 2010
From: linimon at FreeBSD.org (linimon at FreeBSD.org)
Date: Sun, 3 Jan 2010 07:35:26 GMT
Subject: docs/142256: Re: docs/140075: [patch] release notes: missing
word "NOT", whichanges all the meaning of stage
Message-ID: <201001030735.o037ZQ7m085904@freefall.freebsd.org>
Old Synopsis: Re: [patch] docs/140075: release notes: missing word "NOT", which
New Synopsis: Re: docs/140075: [patch] release notes: missing word "NOT", whichanges all the meaning of stage
State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sun Jan 3 07:31:50 UTC 2010
State-Changed-Why:
Misfiled followup to docs/140075; content migrated.
Responsible-Changed-From-To: gnats-admin->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Jan 3 07:31:50 UTC 2010
Responsible-Changed-Why:
http://www.freebsd.org/cgi/query-pr.cgi?pr=142256
From wblock at wonkity.com Sun Jan 3 22:50:04 2010
From: wblock at wonkity.com (Warren Block)
Date: Sun, 3 Jan 2010 22:50:03 GMT
Subject: docs/110376: [patch] add some more explanations for the iwi/ipw
firmware inclusion
Message-ID: <201001032250.o03Mo3UD082039@freefall.freebsd.org>
The following reply was made to PR docs/110376; it has been noted by GNATS.
From: Warren Block
To: bug-followup at FreeBSD.org, rea-fbsd at codelabs.ru
Cc:
Subject: Re: docs/110376: [patch] add some more explanations for the iwi/ipw
firmware inclusion
Date: Sun, 3 Jan 2010 15:47:52 -0700 (MST)
ipw and iwi now use firmware(9) and so references to ifwfw(4) are
obsolete:
"This driver requires the firmware built with the ipwfw module to
work."
This sentence can be eliminated.
"For the loaded firmware to be enabled for use the license at"
Should probably be changed to
"For the IBM firmware to be enabled for use the license at"
Also, the references to ipwfw(4) in the SEE ALSO section should be
removed.
-Warren Block * Rapid City, South Dakota USA
From wblock at wonkity.com Sun Jan 3 22:50:32 2010
From: wblock at wonkity.com (Warren Block)
Date: Sun, 3 Jan 2010 15:50:31 -0700 (MST)
Subject: ipw(4)/iwi(4) reference obsolete ipwfw(4)
Message-ID:
I just submitted a followup to docs/110376 about these outdated
references to ipwfw(4). If needed, I can submit a patch, although it
would be preferable for someone more familiar with those modules to
check it first.
-Warren Block * Rapid City, South Dakota USA
From wblock at wonkity.com Sun Jan 3 23:10:01 2010
From: wblock at wonkity.com (Warren Block)
Date: Sun, 3 Jan 2010 23:01:17 GMT
Subject: docs/142281: firmware(9) references nonexistent sample file
Message-ID: <201001032301.o03N1HAU076836@www.freebsd.org>
>Number: 142281
>Category: docs
>Synopsis: firmware(9) references nonexistent sample file
>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: Sun Jan 03 23:10:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Warren Block
>Release: 8-STABLE
>Organization:
>Environment:
FreeBSD lightning 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Dec 29 21:00:58 MST 2009 root at lightning:/usr/obj/usr/src/sys/LIGHTNING i386
>Description:
man 9 firmware:
..
SEE ALSO
module(9), kld(4)
/usr/share/examples/kld/firmware
/usr/share/examples/kld/firmware does not exist, although it is present under /usr/src/.
>How-To-Repeat:
man 9 firmware
% ls /usr/share/examples/kld/firmware
ls: /usr/share/examples/kld/firmware: No such file or directory
>Fix:
Either modify installworld to install the directory or change the man page to point to /usr/src.
>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org Mon Jan 4 11:06:07 2010
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon, 4 Jan 2010 11:06:06 GMT
Subject: Current unassigned doc problem reports
Message-ID: <201001041106.o04B66jH064179@freefall.freebsd.org>
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)
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.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/142281 doc firmware(9) references nonexistent sample file
o docs/142243 doc Netcat (nc(1)) manual mistake
p docs/142204 doc bad link in bsd-family-tree
o docs/142168 doc ld(1): ldd(1) not mentioned in ld(1) manpage
o docs/141765 doc [handbook] [patch] Added note about architectures when
o docs/141636 doc [handbook] [patch] Updated info about Firefox in Handb
o docs/141350 doc [patch] if_bridge(4) man page incorrectly says a bridg
o docs/141316 doc ntpd(8): ntpd does not honor -d flag
o docs/141125 doc [patch] Typo of "NUL" in getline.3 man page
o docs/140989 doc man page errors: security(7), VFS(9)
o docs/140918 doc [handbook] update 8.0 handbook about serial port /dev
s docs/140847 doc [request] add documentation on ECMP and new route args
o docs/140814 doc [handbook][patch] Chapter 15 - Jails: add section on c
o docs/140703 doc [patch] add xorg-minimal as alternative for X11 Distri
o docs/140495 doc [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140494 doc [patch] Man page fix for getc(3)
o docs/140474 doc signal(3) missing reference to NSIG
o docs/140458 doc [patch] Grammar fix for to{upper,lower}(3)
o docs/140457 doc [patch] Grammar fix for isspace(3)
o docs/140444 doc [patch] New Traditional Chinese translation of custom-
o docs/140435 doc ls(1), section STANDARD: the -A is exception from POSI
o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369 doc [patch] src/contrib/pf/man/pf.4
o docs/140082 doc [handbook] handbook/jails: russian translation is miss
o docs/140075 doc release notes: missing word "NOT", which changes all t
o docs/139682 doc [PATCH] dialog(1) man page does not mention radiolist
o docs/139336 doc [request] ZFS documentation suggestion
o docs/139165 doc gssapi.3 man page out of sync with between crypto and
o docs/139153 doc [patch] the hier(7) man page needs to be updated
o docs/139018 doc translation of submitting.sgml from docproj/submitting
o docs/138887 doc manpage ports(7) incorrect
o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663 doc system(3) man page confuses users about "return value
o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca
o docs/138206 doc [patch] ntp(1): not enabled function, and false manual
o docs/137762 doc [handbook] proposed: mention "make delete-old" in sec
o docs/136918 doc [patch] grammar fixes to locking.9
o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa
o docs/136666 doc [handbook] Configure serial port for remote kernel deb
o docs/136035 doc ftpchroot(5) omits an important option
p docs/136029 doc MALLOC_PRODUCTION knob should be mentioned somewhere,
o docs/135999 doc Netgear GS105v3 should be added to list of switches th
o docs/135676 doc FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516 doc pax(1) manual not mentioning chflags unawareness
o docs/135475 doc [patch] jot(1) manpage and behaviour differ
o docs/135165 doc [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376 doc pthread(3): pthread manpages don't mention that PTHREA
o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222 doc installation failure of japanese docs
o docs/134123 doc The RUNQUEUE(9) man page is out of date
o docs/134074 doc [patch] locking.9 man page slight enhancements
o docs/133567 doc [patch] doc/Makefile switch to csup
o docs/133245 doc french handbook 27.3.5 amd.map amd.conf
o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959 doc [patch] description mismatches on xterm/termcap, fortu
o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839 doc [patch] Fix example script in ldap-auth article
o docs/132718 doc [handbook] Information about adding a new mirror is ou
o docs/132311 doc [patch] man5/nsmb.conf.5
o docs/132260 doc dhcpd(8) pid not stored in documented location
o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113 doc [handbook] Update handbook jails creation
o docs/131918 doc [patch] Fixes for the BPF(4) man page
o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by
o docs/131590 doc [patch] whitespace-only change of developers-handbook/
o docs/130895 doc [patch] No man page installed for padlock(4) on amd64
o docs/130364 doc Man page for top needs explanation of CPU states
o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or
o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson
o docs/129095 doc ipfw(8): Can not check that packet originating/destine
o docs/128524 doc No geom documentation for loading gjournal(8)
s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages
o docs/127908 doc [patch] readdir(3) error documentation
s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps
o docs/126484 doc libc function res-zonscut2 is not documented
o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in
o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052 doc minor update on handbook section 20.7.1
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541 doc [request] no man pages for wlan_scan_ap
o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/120539 doc Inconsistent ipfw's man page
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
a docs/119536 doc a few typos in French handbook (basics)
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118214 doc close(2) error returns incomplete
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747 doc 'break' system call needs a man page
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/116116 doc mktemp (3) re/move note
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/111425 doc Missing chunks of text in historical manpages
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111147 doc hostapd.conf is not documented
o docs/110999 doc carp(4) should document unsupported interface types
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max
o docs/109981 doc No manual entry for post-grohtml
o docs/109977 doc No manual entry for ksu
o docs/109973 doc No manual entry for c++filt
o docs/109972 doc No manual entry for zless/bzless
f docs/109226 doc [request] No manual entry for sntp
o docs/109201 doc [request]: manual for callbootd
a docs/108980 doc list of missing man pages
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
o docs/107924 docs [usb67] usbd(8) does not call detach
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/105608 doc fdc(4) debugging description staled
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand
o docs/83820 doc getino(3) manpage not installed
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596 doc Updates to mt(1) manual page
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/43823 doc [patch] update to environ(7) manpage
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/38556 doc EPS file of beastie, as addition to existing examples
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
a docs/30008 doc [patch] French softupdates document should be translat
o docs/27605 doc [patch] Cross-document references ()
o docs/26286 doc *printf(3) etc should gain format string warnings
o docs/24786 doc missing FILES descriptions in sa(4)
s docs/20028 doc ASCII docs should reflect tags in the sourc
177 problems total.
From jhb at freebsd.org Mon Jan 4 19:53:10 2010
From: jhb at freebsd.org (John Baldwin)
Date: Mon, 4 Jan 2010 10:02:23 -0500
Subject: docs/142281: firmware(9) references nonexistent sample file
In-Reply-To: <201001032301.o03N1HAU076836@www.freebsd.org>
References: <201001032301.o03N1HAU076836@www.freebsd.org>
Message-ID: <201001041002.23356.jhb@freebsd.org>
On Sunday 03 January 2010 6:01:17 pm Warren Block wrote:
>
> >Number: 142281
> >Category: docs
> >Synopsis: firmware(9) references nonexistent sample file
> >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: Sun Jan 03 23:10:01 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Warren Block
> >Release: 8-STABLE
> >Organization:
> >Environment:
> FreeBSD lightning 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Dec 29 21:00:58 MST
2009 root at lightning:/usr/obj/usr/src/sys/LIGHTNING i386
> >Description:
> man 9 firmware:
>
> ..
>
> SEE ALSO
> module(9), kld(4)
>
> /usr/share/examples/kld/firmware
>
> /usr/share/examples/kld/firmware does not exist, although it is present
under /usr/src/.
>
> >How-To-Repeat:
> man 9 firmware
> % ls /usr/share/examples/kld/firmware
> ls: /usr/share/examples/kld/firmware: No such file or directory
> >Fix:
> Either modify installworld to install the directory or change the man page
to point to /usr/src.
This is already fixed in HEAD to install the example, the fix just needs to be
MFC'd. The MFC is currently scheduled for January 12th.
--
John Baldwin
From antoine at FreeBSD.org Mon Jan 4 19:59:45 2010
From: antoine at FreeBSD.org (antoine at FreeBSD.org)
Date: Mon, 4 Jan 2010 19:59:44 GMT
Subject: docs/142281: firmware(9) references nonexistent sample file
Message-ID: <201001041959.o04Jxi2Q037812@freefall.freebsd.org>
Synopsis: firmware(9) references nonexistent sample file
State-Changed-From-To: open->patched
State-Changed-By: antoine
State-Changed-When: Mon Jan 4 19:58:10 UTC 2010
State-Changed-Why:
Already fixed in head
Responsible-Changed-From-To: freebsd-doc->antoine
Responsible-Changed-By: antoine
Responsible-Changed-When: Mon Jan 4 19:58:10 UTC 2010
Responsible-Changed-Why:
Take
http://www.freebsd.org/cgi/query-pr.cgi?pr=142281
From brueffer at FreeBSD.org Mon Jan 4 22:26:45 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Mon, 4 Jan 2010 23:26:44 +0100 (CET)
Subject: docs/140989: man page errors: security(7), VFS(9)
Message-ID: <201001042226.o04MQix7068548@freefall.freebsd.org>
Synopsis: man page errors: security(7), VFS(9)
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Mon Jan 4 23:23:17 CET 2010
State-Changed-Why:
Fixed the security(9) manpage. The VFS_VPTOFH(9) problem stemmed from the fact that
the manpage was repo-copied to VOP_VPTOFH(9) almost three years ago but the references
weren't updated accordingly. Thanks for the submission!
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Mon Jan 4 23:23:17 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140989
From jbarton at cascribe.com Tue Jan 5 20:46:35 2010
From: jbarton at cascribe.com (John P. Barton)
Date: Tue, 5 Jan 2010 12:15:38 -0800
Subject: Compiling the kernel
Message-ID: <001201ca8e43$ddbbb5e0$993321a0$@com>
I read the handbook section 8.5 {Building a Kernel} many times. I cannot
resolve the phrase "make buildkernel KERNCONF=MYKERNEL". I know that
MYKERNEL refers to the name I give to the new kernel I want to build but
neither buildkernel nor installkernel exists in the make command. Can you
clear this up for me. I'm trying to add the IPDIVERT option to a new build
so I can implement NAT. I cannot seem to figure this out and yes, I am very
new to Linux. However, I've been in the computer world since 1977 and have
mastered 14 computer languages so I'm not exactly a rookie at these things.
This thing though, has got me stumped.
Thanks in advance.
John
From linimon at FreeBSD.org Tue Jan 5 20:53:20 2010
From: linimon at FreeBSD.org (linimon at FreeBSD.org)
Date: Tue, 5 Jan 2010 20:53:19 GMT
Subject: docs/142341: jail(8): Jail escape when cwd is moved from the
host system
Message-ID: <201001052053.o05KrJFW095324@freefall.freebsd.org>
Old Synopsis: [jail] Jail escape when cwd is moved from the host system
New Synopsis: jail(8): Jail escape when cwd is moved from the host system
State-Changed-From-To: open->analyzed
State-Changed-By: linimon
State-Changed-When: Tue Jan 5 20:52:25 UTC 2010
State-Changed-Why:
Apparently this is the expected behavior and just needs to be documented.
Responsible-Changed-From-To: freebsd-jail->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Jan 5 20:52:25 UTC 2010
Responsible-Changed-Why:
http://www.freebsd.org/cgi/query-pr.cgi?pr=142341
From dougb at FreeBSD.org Tue Jan 5 21:31:31 2010
From: dougb at FreeBSD.org (Doug Barton)
Date: Tue, 05 Jan 2010 13:31:35 -0800
Subject: Compiling the kernel
In-Reply-To: <001201ca8e43$ddbbb5e0$993321a0$@com>
References: <001201ca8e43$ddbbb5e0$993321a0$@com>
Message-ID: <4B43AFB7.6050300@FreeBSD.org>
For future reference, the best list to start with is always
freebsd-questions at freebsd.org. If you're sure your question is
specific only to a port, then use freebsd-ports at freebsd.org.
John P. Barton wrote:
> I read the handbook section 8.5 {Building a Kernel} many times. I cannot
> resolve the phrase "make buildkernel KERNCONF=MYKERNEL". I know that
> MYKERNEL refers to the name I give to the new kernel I want to build but
> neither buildkernel nor installkernel exists in the make command. Can you
> clear this up for me. I'm trying to add the IPDIVERT option to a new build
> so I can implement NAT. I cannot seem to figure this out and yes, I am very
> new to Linux.
A) This is not Linux, it's FreeBSD. Both are open source Unix
operating systems, but they have very different infrastructures.
B) As far as I can see you're seriously overthinking this. Let's say
that your kernel config file is named FRED. You would do this on the
command line:
make buildkernel KERNCONF=FRED
That's it. It would probably be a lot easier for you to put the
following in /etc/src.conf:
KERNCONF= FRED
You should read 'man src.conf' for more information.
C) Unlike Linux, you really don't want to build just the kernel,
unless you are sticking with the same set of sources that match the
system you already have installed. Then, at minimum you'll still have
to build the necessary infrastructure in the object tree to be able to
build the kernel. Your best bet is to do 'make buildworld' first, then
edit src.conf as described above, then do 'make kernel'.
good luck,
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
From matt.thyer at gmail.com Wed Jan 6 00:50:08 2010
From: matt.thyer at gmail.com (Matthew Thyer)
Date: Wed, 6 Jan 2010 00:49:39 GMT
Subject: docs/142367: wlan(4) does not document requirement for kernel
option "IEEE80211_DEBUG"
Message-ID: <201001060049.o060ndRJ024696@www.freebsd.org>
>Number: 142367
>Category: docs
>Synopsis: wlan(4) does not document requirement for kernel option "IEEE80211_DEBUG"
>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 Jan 06 00:50:07 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Matthew Thyer
>Release: 8-STABLE
>Organization:
>Environment:
FreeBSD soekris-builder8 8.0-STABLE FreeBSD 8.0-STABLE #0 r200974: Fri Dec 25 12
:30:51 CST 2009 root at soekris-builder8:/usr/obj/usr/src/sys/MYGENERIC i386
>Description:
Use of the "wlandebug" command produces the error message:
wlandebug: sysctl-get(net.wlan.0.debug): No such file or directory
This is due to the "IEEE80211_DEBUG" option not being present in the GENERIC ker
nel (for both 8-STABLE and HEAD).
The wlan(4) manual page does not describe the need for this kernel option and so
the end user has to search the web to gain a clue as to what the problem is.
I suggest that this requirement be mentioned in the "DEBUGGING" section of the w
lan(4) manual page.
Sam Leffler notes this requirement in a message to the FreeBSD-CURRENT mailing l
ist with Message-ID: 481A2748.7080801 at freebsd.org, Subject: "Re: Connection prob
lems with wme enabled" & date: "Thu, 01 May 2008 13:25:44 -0700".
Quote:
"Looks like I failed to include IEEE80211_DEBUG in the default kernel
configs; you'll need that to get wlan debug msgs."
>How-To-Repeat:
Run "wlandebug" with a GENERIC kernel and you'll get the error message:
wlandebug: sysctl-get(net.wlan.0.debug): No such file or directory
>Fix:
Add text to the "DEBUGGING" section of the wlan(4) manual page similar to:
The kernel option "IEEE80211_DEBUG" is required to use debugging controls.
Patch attached with submission follows:
--- /usr/src/share/man/man4/wlan.4 2009-12-24 15:14:38.000000000 +1030
+++ /usr/src/share/man/man4/wlan.4.new 2010-01-06 11:01:04.000000000 +1030
@@ -156,6 +156,8 @@
defines the initial value of the debugging flags for each cloned
.Nm
interface; this is useful to enable debug messages during interface creation.
+.Pp
+The kernel option "IEEE80211_DEBUG" is required to use debugging controls.
.Sh COMPATIBILITY
The module name of
.Nm
>Release-Note:
>Audit-Trail:
>Unformatted:
From pgollucci at p6m7g8.com Thu Jan 7 06:28:44 2010
From: pgollucci at p6m7g8.com (Philip M. Gollucci)
Date: Thu, 7 Jan 2010 06:28:41 +0000
Subject: Compiling the kernel
In-Reply-To: <4B43AFB7.6050300@FreeBSD.org>
References: <001201ca8e43$ddbbb5e0$993321a0$@com>
<4B43AFB7.6050300@FreeBSD.org>
Message-ID: <4B457F19.7010809@p6m7g8.com>
>> I know that
>> MYKERNEL refers to the name I give to the new kernel I want to build but
>> neither buildkernel nor installkernel exists in the make command.
I think a simple is all you forgot
$ cd /usr/src
THEN
$ make buildkernel .....
--
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci at p6m7g8.com) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
From linimon at FreeBSD.org Thu Jan 7 15:31:31 2010
From: linimon at FreeBSD.org (linimon at FreeBSD.org)
Date: Thu, 7 Jan 2010 15:31:30 GMT
Subject: docs/142418: [PATCH] newfs_msdos(8) doc fix
Message-ID: <201001071531.o07FVUUL001627@freefall.freebsd.org>
Old Synopsis: [PATCH] sbin/newfs_msdos doc fix
New Synopsis: [PATCH] newfs_msdos(8) doc fix
Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jan 7 15:30:52 UTC 2010
Responsible-Changed-Why:
reclassify.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142418
From jhelfman at e-e.com Thu Jan 7 17:30:03 2010
From: jhelfman at e-e.com (Jason Helfman)
Date: Thu, 7 Jan 2010 17:24:04 GMT
Subject: docs/142429: USERS directive doesn't work as documented in Porter's
Handbook
Message-ID: <201001071724.o07HO4rB089209@www.freebsd.org>
>Number: 142429
>Category: docs
>Synopsis: USERS directive doesn't work as documented in Porter's Handbook
>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 Jan 07 17:30:03 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Jason Helfman
>Release: 8.0-RELEASE-p2
>Organization:
Experts Exchange
>Environment:
8.0-RELEASE-p2
>Description:
It seems when using the USERS or GROUPS directives in a Makefile, that the user will be installed, but the INSTALL macros will fail. I've only been able to verify this when the "configure" script is not used.
>How-To-Repeat:
Add to some test port:
USERS=
do-install:
${INSTALL_SCRIPT} ${WRKSRC}/script.sh ${PREFIX}/bin
.include
>Fix:
Not known, as of yet. The only thing it seems this could be is either a bug in bsd.port.mk or a bug in the Documentation as for the correct process. In looking at other ports, it seems that it is broken, as scripts that add users use the PRE-INSTALL script method.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/users-and-groups.html
>Release-Note:
>Audit-Trail:
>Unformatted:
From jhelfman at e-e.com Thu Jan 7 21:30:04 2010
From: jhelfman at e-e.com (Jason Helfman)
Date: Thu, 7 Jan 2010 21:25:17 GMT
Subject: docs/142437: [request] Errata Notices Index missing
Message-ID: <201001072125.o07LPHi2098235@www.freebsd.org>
>Number: 142437
>Category: docs
>Synopsis: [request] Errata Notices Index missing
>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: Thu Jan 07 21:30:04 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Jason Helfman
>Release: 7.2-RELEASE-p6
>Organization:
Experts Exchange
>Environment:
7.2-RELEASE-p6
>Description:
Errata Notices Index missing.
Compared with Securities Advisories, Errata Notices doc view is radically different.
I mentioned this to Colin, and he thinks that adding a page with a list of errata is a good idea.
>How-To-Repeat:
Click on "More" for Security Advisories @ http://www.freebsd.org
compare this with:
Click on "More" for Errata Notices @ http://www.freebsd.org
>Fix:
Not sure how to patch this, as I am a beginner at the documentation, however I am still looking into how to fix this. In the meanwhile, I thought I would submit a PR.
>Release-Note:
>Audit-Trail:
>Unformatted:
From brueffer at FreeBSD.org Fri Jan 8 21:53:09 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Fri, 8 Jan 2010 22:53:08 +0100 (CET)
Subject: docs/141125: [patch] Typo of "NUL" in getline.3 man page
Message-ID: <201001082153.o08Lr8Wd093385@freefall.freebsd.org>
Synopsis: [patch] Typo of "NUL" in getline.3 man page
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Fri Jan 8 22:51:41 CET 2010
State-Changed-Why:
Matteo committed the change I suggested in r200600. Thanks for the submission!
Responsible-Changed-From-To: freebsd-doc->matteo
Responsible-Changed-By: brueffer
Responsible-Changed-When: Fri Jan 8 22:51:41 CET 2010
Responsible-Changed-Why:
Matteo, could you also handle the MFC?
http://www.freebsd.org/cgi/query-pr.cgi?pr=141125
From brueffer at FreeBSD.org Fri Jan 8 22:04:13 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Fri, 8 Jan 2010 23:04:13 +0100 (CET)
Subject: docs/140494: [patch] Man page fix for getc(3)
Message-ID: <201001082204.o08M4DHg002026@freefall.freebsd.org>
Synopsis: [patch] Man page fix for getc(3)
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Fri Jan 8 22:59:49 CET 2010
State-Changed-Why:
Committed a combination of your and Bruce's changes, thanks!
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Fri Jan 8 22:59:49 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140494
From dfilter at FreeBSD.ORG Sat Jan 9 09:40:06 2010
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sat, 9 Jan 2010 09:40:05 GMT
Subject: docs/141350: commit references a PR
Message-ID: <201001090940.o099e5lA036772@freefall.freebsd.org>
The following reply was made to PR docs/141350; it has been noted by GNATS.
From: dfilter at FreeBSD.ORG (dfilter service)
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/141350: commit references a PR
Date: Sat, 9 Jan 2010 09:30:24 +0000 (UTC)
Author: brueffer
Date: Sat Jan 9 09:30:09 2010
New Revision: 201888
URL: http://svn.freebsd.org/changeset/base/201888
Log:
bridge(4) acts like a switch, not like a hub.
PR: 141350
Submitted by: brucec
Reviewed by: thompsa
MFC after: 1 week
Modified:
head/share/man/man4/bridge.4
Modified: head/share/man/man4/bridge.4
==============================================================================
--- head/share/man/man4/bridge.4 Sat Jan 9 06:30:40 2010 (r201887)
+++ head/share/man/man4/bridge.4 Sat Jan 9 09:30:09 2010 (r201888)
@@ -35,7 +35,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd June 8, 2009
+.Dd January 9, 2010
.Dt IF_BRIDGE 4
.Os
.Sh NAME
@@ -111,7 +111,7 @@ by-default.
A bridge can be used to provide several services, such as a simple
802.11-to-Ethernet bridge for wireless hosts, and traffic isolation.
.Pp
-A bridge works like a hub, forwarding traffic from one interface
+A bridge works like a switch, forwarding traffic from one interface
to another.
Multicast and broadcast packets are always forwarded to all
interfaces that are part of the bridge.
_______________________________________________
svn-src-all at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe at freebsd.org"
From brueffer at FreeBSD.org Sat Jan 9 09:41:24 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Sat, 9 Jan 2010 10:41:24 +0100 (CET)
Subject: docs/141350: [patch] if_bridge(4) man page incorrectly says a
bridge works like a hub
Message-ID: <201001090941.o099fOQm045981@freefall.freebsd.org>
Synopsis: [patch] if_bridge(4) man page incorrectly says a bridge works like a hub
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Sat Jan 9 10:40:52 CET 2010
State-Changed-Why:
Committed, thanks!
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Sat Jan 9 10:40:52 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=141350
From steve at stephen-fisher.com Sun Jan 10 01:50:05 2010
From: steve at stephen-fisher.com (Stephen Fisher)
Date: Sun, 10 Jan 2010 01:45:53 GMT
Subject: docs/142560: FreeBSD Handbook - Freebsd Update section: List config
filename before config options are discussed
Message-ID: <201001100145.o0A1jrIe082324@www.freebsd.org>
>Number: 142560
>Category: docs
>Synopsis: FreeBSD Handbook - Freebsd Update section: List config filename before config options are discussed
>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 Jan 10 01:50:04 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Stephen Fisher
>Release: 8.0-RELEASE
>Organization:
>Environment:
FreeBSD shadow-freebsd.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root at mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
Please consider adding the filename of the default freebsd-update configuration file (/etc/freebsd-update.conf) higher in the handbook page on freebsd-update, preferably before the configuration file's options are being discussed. Section 24.2.1: "The Configuration File" seems like the right place for this. Right now, it is only listed further down under sections 24.2.2 and 24.2.4. The filename on a 8.0-RELEASE base install is /usr/local/share/doc/freebsd/handbook/updating-upgrading-freebsdupdate.html (on my English system, the /usr/local/share/doc/freebsd/handbook links to /usr/local/share/doc/freebsd/en_US.ISO8859-1/books/handbook). I encountered this minor issue when reading the handbook online at http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.html. Thanks!
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From manolis at FreeBSD.org Sun Jan 10 10:26:13 2010
From: manolis at FreeBSD.org (manolis at FreeBSD.org)
Date: Sun, 10 Jan 2010 10:26:12 GMT
Subject: docs/142560: [handbook] [request] FreeBSD Update section: List
config filename before config options are discussed
Message-ID: <201001101026.o0AAQC7F076505@freefall.freebsd.org>
Synopsis: [handbook] [request] FreeBSD Update section: List config filename before config options are discussed
State-Changed-From-To: open->closed
State-Changed-By: manolis
State-Changed-When: Sun Jan 10 10:25:52 UTC 2010
State-Changed-Why:
Fixed, thanks!
http://www.freebsd.org/cgi/query-pr.cgi?pr=142560
From dfilter at FreeBSD.ORG Sun Jan 10 10:30:04 2010
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun, 10 Jan 2010 10:30:04 GMT
Subject: docs/142560: commit references a PR
Message-ID: <201001101030.o0AAU4rS076720@freefall.freebsd.org>
The following reply was made to PR docs/142560; it has been noted by GNATS.
From: dfilter at FreeBSD.ORG (dfilter service)
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/142560: commit references a PR
Date: Sun, 10 Jan 2010 10:25:00 +0000 (UTC)
manolis 2010-01-10 10:24:51 UTC
FreeBSD doc repository
Modified files:
en_US.ISO8859-1/books/handbook/cutting-edge chapter.sgml
Log:
Mention default freebsd-update.conf location before program options are discussed.
PR: docs/142560
Submitted by: Stephen Fisher
Revision Changes Path
1.246 +2 -1 doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
_______________________________________________
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 bruce at cran.org.uk Sun Jan 10 15:50:02 2010
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun, 10 Jan 2010 15:41:30 GMT
Subject: docs/142573: [patch] fix mistakes in "errors" section of sctp
manual pages
Message-ID: <201001101541.o0AFfUxe037663@www.freebsd.org>
>Number: 142573
>Category: docs
>Synopsis: [patch] fix mistakes in "errors" section of sctp manual pages
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jan 10 15:50:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Bruce Cran
>Release: 8.0-STABLE
>Organization:
>Environment:
FreeBSD router.draftnet 8.0-STABLE FreeBSD 8.0-STABLE #0: Sun Jan 3 23:30:01 GMT 2010 brucec at router.draftnet:/usr/obj/usr/src/sys/ROUTER i386
>Description:
The ERRORS section of the sctp manual pages contains a few mistakes in the first sentence. The attached patch corrects them.
>How-To-Repeat:
man sctp_bindx
man sctp_connectx
man sctp_getaddrlen
man sctp_getassocid
man sctp_getpaddrs
man sctp_opt_info
man sctp_send
man sctp_sendmsg
>Fix:
Patch attached with submission follows:
--- /usr/src/lib/libc/net/sctp_bindx.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_bindx.3 2010-01-10 15:27:26.000000000 +0000
@@ -90,7 +90,7 @@
.Sh ERRORS
The
.Fn sctp_bindx
-can return the following errors.
+function can return the following errors:
.Bl -tag -width Er
.It Bq Er EINVAL
This value is returned if the
--- /usr/src/lib/libc/net/sctp_connectx.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_connectx.3 2010-01-10 15:27:45.000000000 +0000
@@ -84,7 +84,7 @@
.Sh ERRORS
The
.Fn sctp_connectx
-can return the following errors.
+function can return the following errors:
.Bl -tag -width Er
.It Bq Er EINVAL
An address listed has an invalid family or no
--- /usr/src/lib/libc/net/sctp_getaddrlen.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_getaddrlen.3 2010-01-10 15:28:30.000000000 +0000
@@ -76,7 +76,7 @@
.Sh ERRORS
The
.Fn sctp_getaddrlen
-function can return the following errors.
+function can return the following errors:
.Bl -tag -width Er
.It Bq Er EINVAL
The address family specified does NOT exist.
--- /usr/src/lib/libc/net/sctp_getassocid.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_getassocid.3 2010-01-10 15:28:46.000000000 +0000
@@ -58,7 +58,7 @@
.Sh ERRORS
The
.Fn sctp_getassocid
-function can return the following errors.
+function can return the following errors:
.Bl -tag -width Er
.It Bq Er ENOENT
The address does not have an association setup to it.
--- /usr/src/lib/libc/net/sctp_getpaddrs.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_getpaddrs.3 2010-01-10 15:29:29.000000000 +0000
@@ -76,7 +76,7 @@
.Fa addrs
upon success.
.Sh ERRORS
-The functions can return the following errors.
+The functions can return the following errors:
.Bl -tag -width Er
.It Bq Er EINVAL
An address listed has an invalid family or no
--- /usr/src/lib/libc/net/sctp_opt_info.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_opt_info.3 2010-01-10 15:29:42.000000000 +0000
@@ -90,7 +90,7 @@
.Sh ERRORS
The
.Fn sctp_opt_info
-function can return the following errors.
+function can return the following errors:
.Bl -tag -width Er
.It Bq Er EINVAL
The argument
--- /usr/src/lib/libc/net/sctp_send.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_send.3 2010-01-10 15:30:20.000000000 +0000
@@ -294,7 +294,7 @@
The
.Fn sctp_send
system call
-fail if:
+fails if:
.Bl -tag -width Er
.It Bq Er EBADF
An invalid descriptor was specified.
--- /usr/src/lib/libc/net/sctp_sendmsg.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_sendmsg.3 2010-01-10 15:30:31.000000000 +0000
@@ -271,7 +271,7 @@
The
.Fn sctp_sendmsg
system call
-fail if:
+fails if:
.Bl -tag -width Er
.It Bq Er EBADF
An invalid descriptor was specified.
>Release-Note:
>Audit-Trail:
>Unformatted:
From bruce at cran.org.uk Sun Jan 10 16:50:02 2010
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun, 10 Jan 2010 16:45:46 GMT
Subject: docs/142576: [patch] fix typos and missing params in the sctp man
pages
Message-ID: <201001101645.o0AGjkVd005073@www.freebsd.org>
>Number: 142576
>Category: docs
>Synopsis: [patch] fix typos and missing params in the sctp man pages
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jan 10 16:50:00 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Bruce Cran
>Release: 8.0-STABLE
>Organization:
>Environment:
FreeBSD router.draftnet 8.0-STABLE FreeBSD 8.0-STABLE #0: Sun Jan 3 23:30:01 GMT 2010 brucec at router.draftnet:/usr/obj/usr/src/sys/ROUTER i386
>Description:
The sctp manual pages contain a few mistakes including missing words, markup errors and missing parameter names. The attached patch fixes them.
>How-To-Repeat:
man sctp_connectx
man sctp_getpaddrs
man sctp_opt_info
man sctp_recvmsg
man sctp_sendmsg
>Fix:
Patch attached with submission follows:
--- /usr/src/lib/libc/net/sctp_recvmsg.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_recvmsg.3 2010-01-10 16:27:20.000000000 +0000
@@ -160,7 +160,7 @@
.Pp
The
.Fa sinfo->sinfo_ppid
-is an opaque 32 bit value that is passed transparently
+field is an opaque 32 bit value that is passed transparently
through the stack from the peer endpoint.
Note that the stack passes this value without regard to byte
order.
@@ -180,12 +180,13 @@
When this flag is absent the message
was delivered in order within the stream it was received.
.Pp
+The
.Fa sinfo->sinfo_stream
-is the SCTP stream that the message was received on.
+field is the SCTP stream that the message was received on.
Streams in SCTP are reliable (or partially reliable) flows of ordered
messages.
.Pp
-The
+The
.Fa sinfo->sinfo_context
field is used only if the local application set an association level
context with the
@@ -197,7 +198,7 @@
.Pp
The
.Fa sinfo->sinfo_ssn
-will hold the stream sequence number assigned
+field will hold the stream sequence number assigned
by the peer endpoint if the message is
.Em not
unordered.
@@ -205,7 +206,7 @@
.Pp
The
.Fa sinfo->sinfo_tsn
-holds a transport sequence number (TSN) that was assigned
+field holds a transport sequence number (TSN) that was assigned
to this message by the peer endpoint.
For messages that fit in or less
than the path MTU this will be the only TSN assigned.
@@ -215,14 +216,14 @@
.Pp
The
.Fa sinfo->sinfo_cumtsn
-holds the current cumulative acknowledgment point of
+field holds the current cumulative acknowledgment point of
the transport association.
Note that this may be larger
or smaller than the TSN assigned to the message itself.
.Pp
-The
+The
.Fa sinfo->sinfo_assoc_id
-is the unique association identification that was assigned
+field is the unique association identification that was assigned
to the association.
For one-to-many (SOCK_SEQPACKET) type
sockets this value can be used to send data to the peer without
@@ -232,10 +233,10 @@
(see
.Xr sctp 4 ) .
.Pp
-The
+The
.Fa sinfo->info_timetolive
field is not used by
-.Fa sctp_recvmsg .
+.Fn sctp_recvmsg .
.Sh RETURN VALUES
The call returns the number of characters sent, or -1
if an error occurred.
--- /usr/src/lib/libc/net/sctp_opt_info.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_opt_info.3 2010-01-10 15:56:26.000000000 +0000
@@ -45,7 +45,7 @@
.In sys/socket.h
.In netinet/sctp.h
.Ft int
-.Fn sctp_opt_info "int s" "sctp_assoc_t" "int opt" "void *arg" "socklen_t *size"
+.Fn sctp_opt_info "int s" "sctp_assoc_t asocid" "int opt" "void *arg" "socklen_t *size"
.Sh DESCRIPTION
The
.Fn sctp_opt_info
--- /usr/src/lib/libc/net/sctp_getpaddrs.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_getpaddrs.3 2010-01-10 16:00:48.000000000 +0000
@@ -64,7 +64,7 @@
.Fa addrs
upon success.
.Pp
-After the caller is through the function
+After the caller is finished, the function
.Fn sctp_freepaddrs
or
.Fn sctp_freeladdrs
--- /usr/src/lib/libc/net/sctp_connectx.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_connectx.3 2010-01-10 16:32:28.000000000 +0000
@@ -44,7 +44,7 @@
.In sys/socket.h
.In netinet/sctp.h
.Ft int
-.Fn sctp_connectx "int s" "struct sockaddr *" "int addrcnt" "sctp_assoc_t *"
+.Fn sctp_connectx "int s" "struct sockaddr *addrs" "int addrcnt" "sctp_assoc_t *asocid"
.Sh DESCRIPTION
The
.Fn sctp_connectx
--- /usr/src/lib/libc/net/sctp_sendmsg.3 2009-08-03 09:13:06.000000000 +0100
+++ sctp_sendmsg.3 2010-01-10 16:42:58.000000000 +0000
@@ -324,7 +324,7 @@
.Xr sendmsg 3 ,
.Xr sctp 4
.Sh BUGS
-Because in the one-to-many style socket the
+Because in the one-to-many style socket
.Fn sctp_sendmsg
or
.Fn sctp_sendmsgx
>Release-Note:
>Audit-Trail:
>Unformatted:
From bruce at cran.org.uk Sun Jan 10 17:30:04 2010
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun, 10 Jan 2010 17:30:03 GMT
Subject: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Message-ID: <201001101730.o0AHU3wI044682@freefall.freebsd.org>
The following reply was made to PR docs/142576; it has been noted by GNATS.
From: Bruce Cran
To: bug-followup at FreeBSD.org, bruce at cran.org.uk
Cc:
Subject: Re: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Date: Sun, 10 Jan 2010 17:24:28 +0000
I've also noticed that most (all?) of the sctp manual pages contain the
original 4 clause BSD license which attributes the copyright to UCB,
which is probably a mistake.
--
Bruce Cran
From bruce at cran.org.uk Sun Jan 10 20:00:15 2010
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun, 10 Jan 2010 20:00:14 GMT
Subject: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Message-ID: <201001102000.o0AK0EOp076574@freefall.freebsd.org>
The following reply was made to PR docs/142576; it has been noted by GNATS.
From: Bruce Cran
To: bug-followup at FreeBSD.org, bruce at cran.org.uk
Cc:
Subject: Re: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Date: Sun, 10 Jan 2010 19:56:57 +0000
--MP_/PG.BK4Fu4y6MNURPRLK0usW
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
There are also errors in sctp_peeloff(2), sctp_generic_sendmsg(2) and
sctp_generic_recvmsg(2). The attached patch fixes those errors.
--
Bruce Cran
--MP_/PG.BK4Fu4y6MNURPRLK0usW
Content-Type: text/diff
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=sctp_man.diff.txt
--- /usr/src/lib/libc/sys/sctp_peeloff.2 2009-08-03 09:13:06.000000000 +0100
+++ sctp_peeloff.2 2010-01-10 19:43:42.000000000 +0000
@@ -36,7 +36,7 @@
.Os
.Sh NAME
.Nm sctp_peeloff
-.Nd detach an association from a one-to-many socket to its on fd
+.Nd detach an association from a one-to-many socket to its own fd
.Sh LIBRARY
.Lb libc
.Sh SYNOPSIS
@@ -58,7 +58,7 @@
.Sh ERRORS
The
.Fn sctp_peeloff
-can return the following errors.
+system call can return the following errors:
.Bl -tag -width Er
.It Bq Er ENOTCONN
The
--- /usr/src/lib/libc/sys/sctp_generic_sendmsg.2 2009-08-03 09:13:06.000000000 +0100
+++ sctp_generic_sendmsg.2 2010-01-10 19:47:20.000000000 +0000
@@ -49,7 +49,6 @@
.Ft int
.Fn sctp_generic_sendmsg_iov "int s" "struct iovec *iov" "int iovlen" "struct sockaddr *to" "struct sctp_sndrcvinfo *sinfo" "int flags"
.Sh DESCRIPTION
-The
.Fn sctp_generic_sendmsg
and
.Fn sctp_generic_sendmsg_iov
--- /usr/src/lib/libc/sys/sctp_generic_recvmsg.2 2009-08-03 09:13:06.000000000 +0100
+++ sctp_generic_recvmsg.2 2010-01-10 19:48:50.000000000 +0000
@@ -46,14 +46,13 @@
.Ft int
.Fn sctp_generic_recvmsg "int s" "struct iovec *iov" "int iovlen" "struct sockaddr *from" "socklen_t *fromlen" "struct sctp_sndrcvinfo *sinfo" "int *msgflags"
.Sh DESCRIPTION
-The
.Fn sctp_generic_recvmsg
-is the true system calls used by the
+is the true system call used by the
.Fn sctp_recvmsg
function call. This call is more efficient since it is a
-true system calls but it is specific to FreeBSD and
+true system call but it is specific to FreeBSD and
can be expected NOT to be present on any other Operating
-System. For detailed useage please see either the
+System. For detailed usage please see the
.Fn sctp_recvmsg
function call.
.Sh RETURN VALUES
--MP_/PG.BK4Fu4y6MNURPRLK0usW--
From bruce at cran.org.uk Sun Jan 10 22:30:15 2010
From: bruce at cran.org.uk (Bruce Cran)
Date: Sun, 10 Jan 2010 22:30:14 GMT
Subject: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Message-ID: <201001102230.o0AMUE1h011868@freefall.freebsd.org>
The following reply was made to PR docs/142576; it has been noted by GNATS.
From: Bruce Cran
To: bug-followup at FreeBSD.org, bruce at cran.org.uk
Cc:
Subject: Re: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Date: Sun, 10 Jan 2010 22:22:46 +0000
There's also a bug in sctp_getpaddrs(3): the title is missing the last
's'.
--- /usr/src/lib/libc/net/sctp_getpaddrs.3 2009-08-03
09:13:06.000000000 +0100 +++ sctp_getpaddrs.3 2010-01-10
22:19:16.000000000 +0000 @@ -33,7 +33,7 @@
.\" $FreeBSD: src/lib/libc/net/sctp_getpaddrs.3,v 1.3.10.1 2009/08/03
08:13:06 kensmith Exp $ .\"
.Dd December 15, 2006
-.Dt SCTP_GETPADDR 3
+.Dt SCTP_GETPADDRS 3
.Os
.Sh NAME
.Nm sctp_getpaddrs ,
From bugmaster at FreeBSD.org Mon Jan 11 11:06:07 2010
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon, 11 Jan 2010 11:06:06 GMT
Subject: Current unassigned doc problem reports
Message-ID: <201001111106.o0BB666S033901@freefall.freebsd.org>
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)
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.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/142576 doc [patch] fix typos and missing params in the sctp man p
o docs/142573 doc [patch] fix mistakes in "errors" section of sctp manua
o docs/142437 doc [request] Errata Notices Index missing
o docs/142429 doc USERS directive doesn't work as documented in Porter's
o docs/142418 doc [PATCH] newfs_msdos(8) doc fix
o docs/142367 doc [patch] wlan(4) does not document requirement for kern
a docs/142341 doc jail(8): Jail escape when cwd is moved from the host s
o docs/142243 doc Netcat (nc(1)) manual mistake
p docs/142204 doc bad link in bsd-family-tree
o docs/142168 doc ld(1): ldd(1) not mentioned in ld(1) manpage
o docs/141765 doc [handbook] [patch] Added note about architectures when
o docs/141636 doc [handbook] [patch] Updated info about Firefox in Handb
o docs/141316 doc ntpd(8): ntpd does not honor -d flag
o docs/140918 doc [handbook] update 8.0 handbook about serial port /dev
s docs/140847 doc [request] add documentation on ECMP and new route args
o docs/140814 doc [handbook][patch] Chapter 15 - Jails: add section on c
o docs/140703 doc [patch] add xorg-minimal as alternative for X11 Distri
o docs/140495 doc [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140474 doc signal(3) missing reference to NSIG
o docs/140458 doc [patch] Grammar fix for to{upper,lower}(3)
o docs/140457 doc [patch] Grammar fix for isspace(3)
o docs/140444 doc [patch] New Traditional Chinese translation of custom-
o docs/140435 doc ls(1), section STANDARD: the -A is exception from POSI
o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369 doc [patch] src/contrib/pf/man/pf.4
o docs/140082 doc [handbook] handbook/jails: russian translation is miss
o docs/140075 doc release notes: missing word "NOT", which changes all t
o docs/139682 doc [PATCH] dialog(1) man page does not mention radiolist
o docs/139336 doc [request] ZFS documentation suggestion
o docs/139165 doc gssapi.3 man page out of sync with between crypto and
o docs/139153 doc [patch] the hier(7) man page needs to be updated
o docs/139018 doc translation of submitting.sgml from docproj/submitting
o docs/138887 doc manpage ports(7) incorrect
o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663 doc system(3) man page confuses users about "return value
o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca
o docs/138206 doc [patch] ntp(1): not enabled function, and false manual
o docs/137762 doc [handbook] proposed: mention "make delete-old" in sec
o docs/136918 doc [patch] grammar fixes to locking.9
o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa
o docs/136666 doc [handbook] Configure serial port for remote kernel deb
o docs/136035 doc ftpchroot(5) omits an important option
p docs/136029 doc MALLOC_PRODUCTION knob should be mentioned somewhere,
o docs/135999 doc Netgear GS105v3 should be added to list of switches th
o docs/135676 doc FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516 doc pax(1) manual not mentioning chflags unawareness
o docs/135475 doc [patch] jot(1) manpage and behaviour differ
o docs/135165 doc [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376 doc pthread(3): pthread manpages don't mention that PTHREA
o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222 doc installation failure of japanese docs
o docs/134123 doc The RUNQUEUE(9) man page is out of date
o docs/134074 doc [patch] locking.9 man page slight enhancements
o docs/133567 doc [patch] doc/Makefile switch to csup
o docs/133245 doc french handbook 27.3.5 amd.map amd.conf
o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section
o docs/132959 doc [patch] description mismatches on xterm/termcap, fortu
o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839 doc [patch] Fix example script in ldap-auth article
o docs/132718 doc [handbook] Information about adding a new mirror is ou
o docs/132311 doc [patch] man5/nsmb.conf.5
o docs/132260 doc dhcpd(8) pid not stored in documented location
o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113 doc [handbook] Update handbook jails creation
o docs/131918 doc [patch] Fixes for the BPF(4) man page
o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by
o docs/131590 doc [patch] whitespace-only change of developers-handbook/
o docs/130895 doc [patch] No man page installed for padlock(4) on amd64
o docs/130364 doc Man page for top needs explanation of CPU states
o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or
o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson
o docs/129095 doc ipfw(8): Can not check that packet originating/destine
o docs/128524 doc No geom documentation for loading gjournal(8)
s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages
o docs/127908 doc [patch] readdir(3) error documentation
s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps
o docs/126484 doc libc function res-zonscut2 is not documented
o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in
o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052 doc minor update on handbook section 20.7.1
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541 doc [request] no man pages for wlan_scan_ap
o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/120539 doc Inconsistent ipfw's man page
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
a docs/119536 doc a few typos in French handbook (basics)
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118214 doc close(2) error returns incomplete
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747 doc 'break' system call needs a man page
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/116116 doc mktemp (3) re/move note
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/111425 doc Missing chunks of text in historical manpages
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111147 doc hostapd.conf is not documented
o docs/110999 doc carp(4) should document unsupported interface types
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max
o docs/109981 doc No manual entry for post-grohtml
o docs/109977 doc No manual entry for ksu
o docs/109973 doc No manual entry for c++filt
o docs/109972 doc No manual entry for zless/bzless
f docs/109226 doc [request] No manual entry for sntp
o docs/109201 doc [request]: manual for callbootd
a docs/108980 doc list of missing man pages
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
o docs/107924 docs [usb67] usbd(8) does not call detach
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/105608 doc fdc(4) debugging description staled
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand
o docs/83820 doc getino(3) manpage not installed
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596 doc Updates to mt(1) manual page
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/43823 doc [patch] update to environ(7) manpage
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/38556 doc EPS file of beastie, as addition to existing examples
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
a docs/30008 doc [patch] French softupdates document should be translat
o docs/27605 doc [patch] Cross-document references ()
o docs/26286 doc *printf(3) etc should gain format string warnings
o docs/24786 doc missing FILES descriptions in sa(4)
s docs/20028 doc ASCII docs should reflect tags in the sourc
179 problems total.
From dfilter at FreeBSD.ORG Mon Jan 11 21:20:06 2010
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Mon, 11 Jan 2010 21:20:05 GMT
Subject: docs/132959: commit references a PR
Message-ID: <201001112120.o0BLK5sO067430@freefall.freebsd.org>
The following reply was made to PR docs/132959; it has been noted by GNATS.
From: dfilter at FreeBSD.ORG (dfilter service)
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/132959: commit references a PR
Date: Mon, 11 Jan 2010 21:18:01 +0000 (UTC)
Author: gavin
Date: Mon Jan 11 21:17:49 2010
New Revision: 202115
URL: http://svn.freebsd.org/changeset/base/202115
Log:
Our standard "xterm" termcap entry supports colour, so this tip is redundant.
As it happens, "xterm-color" has just been an alias for "xterm" since
src/share/termcap/termcap.src 1.131 in September 2002.
PR: docs/132959
Approved by: ed (mentor)
Modified:
head/games/fortune/datfiles/freebsd-tips
Modified: head/games/fortune/datfiles/freebsd-tips
==============================================================================
--- head/games/fortune/datfiles/freebsd-tips Mon Jan 11 21:01:35 2010 (r202114)
+++ head/games/fortune/datfiles/freebsd-tips Mon Jan 11 21:17:49 2010 (r202115)
@@ -50,18 +50,6 @@ If you are in the C shell and have just
be able to run it unless you first type "rehash".
-- Dru
%
-If you are running xterm, the default TERM variable will be 'xterm'. If you
-set this environment variable to 'xterm-color' instead, a lot of programs will
-use colors. You can do this by
-
- TERM=xterm-color; export TERM
-
-in Bourne-derived shells, and
-
- setenv TERM xterm-color
-
-in csh-derived shells.
-%
If you do not want to get beeps in X11 (X Windows), you can turn them off with
xset b off
_______________________________________________
svn-src-all at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe at freebsd.org"
From pieterverberne at xs4all.nl Tue Jan 12 09:11:03 2010
From: pieterverberne at xs4all.nl (Pieter Verberne)
Date: Tue, 12 Jan 2010 09:52:51 +0100
Subject: Handbook 3.2.2: Freebsd a multiprocessing system?
Message-ID: <20100112085245.GA89307@xs4all.nl>
Hi all,
Section 3.2.2 of the FreeBSD handbook says:
"FreeBSD is a multiuser, multiprocessing system. This is the formal
description that is usually given to a system that can be used by many
different people, who simultaneously run a lot of programs on a single
machine."
Isn't running programs simultaneously called time-sharing?
Wikipedia says:
"Multiprocessing is the use of two or more central processing units
(CPUs) within a single computer system."
Okay, FreeBSD might use more than one CPU at the time, but the handbook
is still incorrect I think.
Pieter Verberne
From gavin at FreeBSD.org Tue Jan 12 11:42:54 2010
From: gavin at FreeBSD.org (gavin at FreeBSD.org)
Date: Tue, 12 Jan 2010 11:42:52 GMT
Subject: docs/132959: [patch] description mismatches on xterm/termcap,
fortune/freebsd-tips
Message-ID: <201001121142.o0CBgq4T063049@freefall.freebsd.org>
Synopsis: [patch] description mismatches on xterm/termcap, fortune/freebsd-tips
State-Changed-From-To: open->patched
State-Changed-By: gavin
State-Changed-When: Tue Jan 12 11:42:25 UTC 2010
State-Changed-Why:
Fixed in HEAD, will MFC in a week
Responsible-Changed-From-To: freebsd-doc->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Tue Jan 12 11:42:25 UTC 2010
Responsible-Changed-Why:
Mine
http://www.freebsd.org/cgi/query-pr.cgi?pr=132959
From parshi at msicanada.net Tue Jan 12 13:31:46 2010
From: parshi at msicanada.net (Peter Arshi)
Date: Tue, 12 Jan 2010 07:56:18 -0500
Subject: E-commerce Gateway
Message-ID: <27538c4fbf4869041de6a67000186938@msicanada.net>
?
E-commerce Payment Gateway Solution:
(E-commerce Gateway Solution for United States and Canadian Merchants)
?
Federated Payments- USA Merchant Accounts
MSI Canada- Canadian Merchant Accounts
?
?
About Us
Federated Payments / MSI Canada is a credit card payment processor in the United
States and Canadian marketplace.? We have an ?A? Industry Rating with the BBB
(Better Business Bureau) and annually process over 2 billion dollars in credit
card payment transactions. Established in 1998, Federated Payments recently
took its place as one of the Top 50 Payment Processors in the Industry and
is considered the fastest growing Processor according to the Neilson Report.?
We service more than 20,000 merchants across the country and employ 150 sales
support and technical staff in the United States and Canada. Federated Payments
operates as Merchant Services Inc. Canada (MSI Canada) as its Canadian operations.
?
Recognizing the Gateway Problem
We are aware of the difficulties web developers experience when adding shopping
carts to sites and then to face security compliance issues when Payment Gateways
are to be integrated.? In most cases, the client?s bank does not support an
online payment gateway solution. This begins the clients search to find the
right bank that will approve or provide a payment gateway that can comply to
the shopping cart security standards.?? After this step is complete, the client
is left to babysit the bank to ensure correspondence is maintained with the
web developer until task is complete.?
?
For any developer, dropping the ball at the end is simply bad practice hence
integrating PayPal saves the client from anguish and despair temporarily. PayPal
charges high credit card processing rates which leads to even more client despair
in the end. Professionalism is lost when the gateway page re-directs the customer
to a process he is not interested in fulfilling. ?PayPal should be considered
an additional feature and not the primary gateway function. Required customer
sign-ups and account verification processes deter customers from returning
to PayPal sites. Client loses retention momentum.
?
SafePay Solution
The SafePay Gateway Program is a solution for merchants to process online in
a secured manner without giving up large profits for processing. We offer the
?Lowest Rate Guarantee? to every client that comes on board. Included with
the SafePay Program is the Backend Gateway which enables clients a backend
to enter orders manually, to put customers on recurring payments, pull reports,
customizable fields, download/upload Quick Books file feature , multiple user
with Admin control features and much more. ?A demo will be provided to your
client for training by our technicians.
?
?
SafePay Payment Gateway Solution Features:
???????? Enables real-time online transaction processing
???????? Fully CISP and PCI Certified
???????? Free Quick Click Shopping Cart- Or connect with over 80 certified
shopping carts
???????? Recurring Billing- Bill your customers daily, weekly or monthly for
as many payments as requires
???????? Cardholder Authentication Card Programs: Verified by Visa, MasterCard
SecureCode
???????? Virtual Terminal-? With a Level 3 intuitive user interface, you will
be able to authorize, process and manage credit card transactions manually
from any computer that has an internet connection.
???????? API Integration- With API Integration solution your merchants will
utilize the highest level of secure transaction infrastructure available.
???????? Batch Upload Process- With batch upload processing you will be able
to control and approve transactions manually prior to settlement.? The batch
processing system automatically allocates the batches in 1/16 bins and reduces
overall processing time to a fraction of your competitors.
???????? Electronic Check- Electronic Check is a payment solution that enables
online and traditional merchants to accept and process electronic check payments
directly from their Web site?s storefront or through the Virtual Terminal.?
By accepting electronic checks, you are able to expand the payment options
available to your customers and thereby increase sales. ?
?
?
Solution Option 1
Federated Payments and MSI Canada offers one of the best Payment Gateway programs
in the industry known as Safepay. To simplify the shopping cart integration
to our payment gateway, here are some free shopping carts we support:
?
Free Supported Shopping Carts:
?
OsCommerce.com, nopdesign.com, virtuemart.net, zencart.com, precisionweb.net?
?
?
Solution Option 2
Our technicians are equipped to handle any type of shopping cart in the marketplace.
Custom built designs are accepted with additional security compliance testing.
This means that the majority of shopping carts fall into compliance with our
payment gateway solution after testing.
?
Simple Process
???????? When an e-commerce site is ready for a Payment Gateway, a member of
our team will need to contact your client and provide the best credit card
rates for their industry.
???????? ?Send an e-mail to Mr. Arshi with the client and designated developer
details.
???????? As part of the package, we will offer your clients the ?Lowest Rate
Guarantee?.? For any bank, association or processor that can beat our credit
card rates, we will match or beat them over and over again. Guaranteed. ??This
leaves your client to have the best possible rates all the time.
Contact:
Peter Arshi
Regional Sales Executive
(International Partnerships Program)
tf:?? +1-888-743-5458
fx:?? +1-888-743-5457
ce:? +1-647-284-4678
em: parshi at msicanada.net
???????? We offer very competitive online transaction rates for Visa, MasterCard,
Amex, Discover, JCB,? and Diners Club. Merchant rates will range based on sales
volumes, credit card type and nature of business. Rates will vary.
???????? Once the contract is complete and approval is obtained from our head
office, one of our technicians will be in contact with the designated developer
for gateway integration and testing via e-mail.? The Developer will be provided
with style choices for the Payment Gateway and/or Shopping Cart for client
for review.
???????? Once the style(s) are selected, the gateway and/or shopping cart code
will be connected by our technician with the help of your developer.? This
arrangement can be further discussed with technician.
???????? Once functionality and security compliance are tested and passed,
your client is ready to make his first sale on his website.
?
We are introducing Safepay to web developers as it is an essential tool to
maintain and sustain retention in this competitive marketplace.? Our strong
reputation as a Payment Processor will enable your company to provide a ?Complete?
E-commerce solution to your clients from start to finish. We guarantee it.
?If have any questions, please contact Mr. Peter Arshi.
?
?
?
Peter Arshi
MSI Canada
Regional Sales Executive
(International Partnerships Program)
tf:?? +1-888-743-5458
fx:?? +1-888-743-5457
ce:? +1-647-284-4678
em: parshi at msicanada.net
?
In Association with:
????????????? ????????
If you would like to be removed from this list, please reply with "remove"
in the subject line.
From deeplunacy at gmail.com Tue Jan 12 14:33:57 2010
From: deeplunacy at gmail.com (Michael Vorobyov)
Date: Tue, 12 Jan 2010 17:03:17 +0300
Subject: Possible mistype in 3.3.1 of the handbook
Message-ID: <321506cf1001120603u2fd25130l82a27c834ec376b7@mail.gmail.com>
Dear sirs!
In paragraph 3.3.1 of the Handbook it is said
that permission "All" is also called?"world".
The example follows then saying:
=====================================
For example the following command will remove
the group and ?world? write permission on FILE,
then it adds the execute permissions for everyone:
% chmod go-w,a+x FILE
=====================================
Here we can see that by "world" author means
permission "Other".
Could you please define which is the correct?
Best regards,
Michael Vorobyov
From cswiger at mac.com Tue Jan 12 17:55:16 2010
From: cswiger at mac.com (Chuck Swiger)
Date: Tue, 12 Jan 2010 09:55:15 -0800
Subject: Handbook 3.2.2: Freebsd a multiprocessing system?
In-Reply-To: <20100112085245.GA89307@xs4all.nl>
References: <20100112085245.GA89307@xs4all.nl>
Message-ID:
Hi--
On Jan 12, 2010, at 12:52 AM, Pieter Verberne wrote:
> Section 3.2.2 of the FreeBSD handbook says:
> "FreeBSD is a multiuser, multiprocessing system. This is the formal
> description that is usually given to a system that can be used by many
> different people, who simultaneously run a lot of programs on a single
> machine."
>
> Isn't running programs simultaneously called time-sharing?
No. A time-sharing or batch processing system traditionally used to process entire jobs to completion-- think of Hollerith card based machines or early cooperative multitasking implementations and you'll get the idea. Because FreeBSD has a scheduler interrupt firing at typically HZ=100 or 1000, which will pre-empt any userland task and allow other userland tasks to run without any of them being explicitly coded to yield the CPU, FreeBSD is correctly described as a "preemptive multitasking OS".
> Wikipedia says:
> "Multiprocessing is the use of two or more central processing units
> (CPUs) within a single computer system."
>
> Okay, FreeBSD might use more than one CPU at the time, but the handbook
> is still incorrect I think.
FreeBSD does support multiprocessing per that definition also.
Regards,
--
-Chuck
From brueffer at FreeBSD.org Tue Jan 12 21:45:53 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Tue, 12 Jan 2010 22:45:52 +0100 (CET)
Subject: docs/142573: [patch] fix mistakes in "errors" section of sctp
manual pages
Message-ID: <201001122145.o0CLjqSX083312@freefall.freebsd.org>
Synopsis: [patch] fix mistakes in "errors" section of sctp manual pages
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Tue Jan 12 22:45:21 CET 2010
State-Changed-Why:
Committed, thanks!
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Tue Jan 12 22:45:21 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142573
From brueffer at FreeBSD.org Tue Jan 12 21:47:18 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Tue, 12 Jan 2010 22:47:18 +0100 (CET)
Subject: docs/142576: [patch] fix typos and missing params in the sctp
man pages
Message-ID: <201001122147.o0CLlIPU083380@freefall.freebsd.org>
Synopsis: [patch] fix typos and missing params in the sctp man pages
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Tue Jan 12 22:46:06 CET 2010
State-Changed-Why:
Committed, thanks! I think I discussed the licensing issue with
rrs before, will ping him again.
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Tue Jan 12 22:46:06 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142576
From parshi at msicanada.net Wed Jan 13 03:46:05 2010
From: parshi at msicanada.net (Peter Arshi)
Date: Tue, 12 Jan 2010 22:15:46 -0500
Subject: E-commerce Gateway
Message-ID:
?
E-commerce Payment Gateway Solution:
(E-commerce Gateway Solution for United States and Canadian Merchants)
?
Federated Payments- USA Merchant Accounts
MSI Canada- Canadian Merchant Accounts
?
?
About Us
Federated Payments / MSI Canada is a credit card payment processor in the United
States and Canadian marketplace.? We have an ?A? Industry Rating with the BBB
(Better Business Bureau) and annually process over 2 billion dollars in credit
card payment transactions. Established in 1998, Federated Payments recently
took its place as one of the Top 50 Payment Processors in the Industry and
is considered the fastest growing Processor according to the Neilson Report.?
We service more than 20,000 merchants across the country and employ 150 sales
support and technical staff in the United States and Canada. Federated Payments
operates as Merchant Services Inc. Canada (MSI Canada) as its Canadian operations.
?
Recognizing the Gateway Problem
We are aware of the difficulties web developers experience when adding shopping
carts to sites and then to face security compliance issues when Payment Gateways
are to be integrated.? In most cases, the client?s bank does not support an
online payment gateway solution. This begins the clients search to find the
right bank that will approve or provide a payment gateway that can comply to
the shopping cart security standards.?? After this step is complete, the client
is left to babysit the bank to ensure correspondence is maintained with the
web developer until task is complete.?
?
For any developer, dropping the ball at the end is simply bad practice hence
integrating PayPal saves the client from anguish and despair temporarily. PayPal
charges high credit card processing rates which leads to even more client despair
in the end. Professionalism is lost when the gateway page re-directs the customer
to a process he is not interested in fulfilling. ?PayPal should be considered
an additional feature and not the primary gateway function. Required customer
sign-ups and account verification processes deter customers from returning
to PayPal sites. Client loses retention momentum.
?
SafePay Solution
The SafePay Gateway Program is a solution for merchants to process online in
a secured manner without giving up large profits for processing. We offer the
?Lowest Rate Guarantee? to every client that comes on board. Included with
the SafePay Program is the Backend Gateway which enables clients a backend
to enter orders manually, to put customers on recurring payments, pull reports,
customizable fields, download/upload Quick Books file feature , multiple user
with Admin control features and much more. ?A demo will be provided to your
client for training by our technicians.
?
?
SafePay Payment Gateway Solution Features:
???????? Enables real-time online transaction processing
???????? Fully CISP and PCI Certified
???????? Free Quick Click Shopping Cart- Or connect with over 80 certified
shopping carts
???????? Recurring Billing- Bill your customers daily, weekly or monthly for
as many payments as requires
???????? Cardholder Authentication Card Programs: Verified by Visa, MasterCard
SecureCode
???????? Virtual Terminal-? With a Level 3 intuitive user interface, you will
be able to authorize, process and manage credit card transactions manually
from any computer that has an internet connection.
???????? API Integration- With API Integration solution your merchants will
utilize the highest level of secure transaction infrastructure available.
???????? Batch Upload Process- With batch upload processing you will be able
to control and approve transactions manually prior to settlement.? The batch
processing system automatically allocates the batches in 1/16 bins and reduces
overall processing time to a fraction of your competitors.
???????? Electronic Check- Electronic Check is a payment solution that enables
online and traditional merchants to accept and process electronic check payments
directly from their Web site?s storefront or through the Virtual Terminal.?
By accepting electronic checks, you are able to expand the payment options
available to your customers and thereby increase sales. ?
?
?
Solution Option 1
Federated Payments and MSI Canada offers one of the best Payment Gateway programs
in the industry known as Safepay. To simplify the shopping cart integration
to our payment gateway, here are some free shopping carts we support:
?
Free Supported Shopping Carts:
?
OsCommerce.com, nopdesign.com, virtuemart.net, zencart.com, precisionweb.net?
?
?
Solution Option 2
Our technicians are equipped to handle any type of shopping cart in the marketplace.
Custom built designs are accepted with additional security compliance testing.
This means that the majority of shopping carts fall into compliance with our
payment gateway solution after testing.
?
Simple Process
???????? When an e-commerce site is ready for a Payment Gateway, a member of
our team will need to contact your client and provide the best credit card
rates for their industry.
???????? ?Send an e-mail to Mr. Arshi with the client and designated developer
details.
???????? As part of the package, we will offer your clients the ?Lowest Rate
Guarantee?.? For any bank, association or processor that can beat our credit
card rates, we will match or beat them over and over again. Guaranteed. ??This
leaves your client to have the best possible rates all the time.
Contact:
Peter Arshi
Regional Sales Executive
(International Partnerships Program)
tf:?? +1-888-743-5458
fx:?? +1-888-743-5457
ce:? +1-647-284-4678
em: parshi at msicanada.net
???????? We offer very competitive online transaction rates for Visa, MasterCard,
Amex, Discover, JCB,? and Diners Club. Merchant rates will range based on sales
volumes, credit card type and nature of business. Rates will vary.
???????? Once the contract is complete and approval is obtained from our head
office, one of our technicians will be in contact with the designated developer
for gateway integration and testing via e-mail.? The Developer will be provided
with style choices for the Payment Gateway and/or Shopping Cart for client
for review.
???????? Once the style(s) are selected, the gateway and/or shopping cart code
will be connected by our technician with the help of your developer.? This
arrangement can be further discussed with technician.
???????? Once functionality and security compliance are tested and passed,
your client is ready to make his first sale on his website.
?
We are introducing Safepay to web developers as it is an essential tool to
maintain and sustain retention in this competitive marketplace.? Our strong
reputation as a Payment Processor will enable your company to provide a ?Complete?
E-commerce solution to your clients from start to finish. We guarantee it.
?If have any questions, please contact Mr. Peter Arshi.
?
?
?
Peter Arshi
MSI Canada
Regional Sales Executive
(International Partnerships Program)
tf:?? +1-888-743-5458
fx:?? +1-888-743-5457
ce:? +1-647-284-4678
em: parshi at msicanada.net
?
In Association with:
????????????? ????????
If you would like to be removed from this list, please reply with "remove"
in the subject line.
From amaya-request at ml.free.fr Wed Jan 13 10:24:16 2010
From: amaya-request at ml.free.fr (Listar)
Date: Wed, 13 Jan 2010 11:06:11 +0100 (CET)
Subject: Listar command results: -- No attachments (even text) are allowed --
Message-ID:
Request received for list 'amaya' via request address.
---
Gestionnaire de liste Listar/0.42 - fin de traitement/job execution complete.
From LCRTRIfFu91c710azO2Y at live.co.uk Thu Jan 14 05:10:01 2010
From: LCRTRIfFu91c710azO2Y at live.co.uk (Lachlan Kang)
Date: Thu, 14 Jan 2010 05:08:40 GMT
Subject: docs/142815: [patch] namei(9) required include
Message-ID: <201001140508.o0E58euf020676@www.freebsd.org>
>Number: 142815
>Category: docs
>Synopsis: [patch] namei(9) required include
>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 Jan 14 05:10:00 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Lachlan Kang
>Release: FreeBSD 8.0-RELEASE
>Organization:
>Environment:
>Description:
namei(9) should specify under SYNOPSIS that sys/fcntl.h needs to be included.
The macro NDINIT which is described in namei(9), uses the value AT_FDCWD, which is defined in sys/fcntl.h.
If a program that uses NDINIT() is written and it does not include sys/fcntl.h, then it will not be able to compile.
>How-To-Repeat:
man 9 namei
>Fix:
Just add sys/fcntl.h as one of the required includes under SYNOPSIS.
Patch attached with submission follows:
Index: head/share/man/man9/namei.9
===================================================================
--- head/share/man/man9/namei.9 (revision 202273)
+++ head/share/man/man9/namei.9 (working copy)
@@ -46,6 +46,7 @@
.In sys/param.h
.In sys/proc.h
.In sys/namei.h
+.In sys/fcntl.h
.Ft int
.Fn namei "struct nameidata *ndp"
.Ft void
>Release-Note:
>Audit-Trail:
>Unformatted:
From LCRTRIfFu91c710azO2Y at live.co.uk Thu Jan 14 05:30:03 2010
From: LCRTRIfFu91c710azO2Y at live.co.uk (Lachlan Kang)
Date: Thu, 14 Jan 2010 05:20:54 GMT
Subject: docs/142816: [patch] namei(9) return values
Message-ID: <201001140520.o0E5KsgU030632@www.freebsd.org>
>Number: 142816
>Category: docs
>Synopsis: [patch] namei(9) return values
>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 Jan 14 05:30:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Lachlan Kang
>Release: FreeBSD 8.0-RELEASE
>Organization:
>Environment:
>Description:
The manpage namei(9) does not specify the return value of the function namei().
The function namei() returns 0 on success, or errno on failure.
I skimmed through the namei() source code (src/sys/kern/vfs_lookup.c) and added a simple RETURN VALUES and ERRORS section to the namei(9) manpage.
The error code descriptions were simply copied from intro(2).
>How-To-Repeat:
man 9 namei
>Fix:
Add a RETURN VALUES and ERRORS section to namei(9).
Patch attached with submission follows:
Index: head/share/man/man9/namei.9
===================================================================
--- head/share/man/man9/namei.9 (revision 202273)
+++ head/share/man/man9/namei.9 (working copy)
@@ -315,6 +315,30 @@
.Fn NDFREE
function.
.El
+.Sh RETURN VALUES
+If successful,
+.Fn namei
+will return 0, otherwise it will return an error.
+.Sh ERRORS
+Errors which
+.Fn namei
+may return:
+.Bl -tag -width Er
+.It Bq Er ENOENT
+No such file or directory. A component of a specified pathname did not exist, or the pathname was an empty string.
+.It Bq Er ACCES
+Permission denied. An attempt was made to access a file in a way forbidden by its file access permissions.
+.It Bq Er ENOTDIR
+Not a directory. A component of the specified pathname existed, but it was not a directory, when a directory was expected.
+.It Bq Er EISDIR
+Is a directory. An attempt was made to open a directory with write mode specified.
+.It Bq Er EROFS
+Read-only file system. An attempt was made to modify a file or directory on a file system that was read-only at the time.
+.It Bq Er ELOOP
+Too many levels of symbolic links. A path name lookup involved more than 32 (MAXSYMLINKS) symbolic links.
+.It Bq Er ENAMETOOLONG
+File name too long. A component of a path name exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
+.El
.Sh FILES
.Bl -tag
.It Pa src/sys/kern/vfs_lookup.c
>Release-Note:
>Audit-Trail:
>Unformatted:
From roam at FreeBSD.org Thu Jan 14 09:39:30 2010
From: roam at FreeBSD.org (roam at FreeBSD.org)
Date: Thu, 14 Jan 2010 09:39:29 GMT
Subject: docs/142367: [patch] wlan(4) does not document requirement for
kernel option "IEEE80211_DEBUG"
Message-ID: <201001140939.o0E9dTfm024449@freefall.freebsd.org>
Synopsis: [patch] wlan(4) does not document requirement for kernel option "IEEE80211_DEBUG"
State-Changed-From-To: open->patched
State-Changed-By: roam
State-Changed-When: Thu Jan 14 09:38:45 UTC 2010
State-Changed-Why:
Fixed in -CURRENT with slightly different wording, I'll merge the change
into the stable branches in two weeks' time. Thanks for reporting this!
Responsible-Changed-From-To: freebsd-doc->roam
Responsible-Changed-By: roam
Responsible-Changed-When: Thu Jan 14 09:38:45 UTC 2010
Responsible-Changed-Why:
My MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142367
From dfilter at FreeBSD.ORG Thu Jan 14 14:40:06 2010
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Thu, 14 Jan 2010 14:40:06 GMT
Subject: docs/142815: commit references a PR
Message-ID: <201001141440.o0EEe692087877@freefall.freebsd.org>
The following reply was made to PR docs/142815; it has been noted by GNATS.
From: dfilter at FreeBSD.ORG (dfilter service)
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/142815: commit references a PR
Date: Thu, 14 Jan 2010 14:36:53 +0000 (UTC)
Author: jhb
Date: Thu Jan 14 14:36:39 2010
New Revision: 202284
URL: http://svn.freebsd.org/changeset/base/202284
Log:
- Update required headers for namei() to add and remove
.
- Add RETURN VALUES and ERROR sections for namei()'s error return values.
- Add a missing link to NDHASGIANT.9.
PR: docs/142815, docs/142816
Submitted by: Lachlan Kang (1, 2)
MFC after: 3 days
Modified:
head/share/man/man9/Makefile
head/share/man/man9/namei.9
Modified: head/share/man/man9/Makefile
==============================================================================
--- head/share/man/man9/Makefile Thu Jan 14 14:30:54 2010 (r202283)
+++ head/share/man/man9/Makefile Thu Jan 14 14:36:39 2010 (r202284)
@@ -903,7 +903,8 @@ MLINKS+=mutex.9 mtx_assert.9 \
mutex.9 mtx_unlock_spin.9 \
mutex.9 mtx_unlock_spin_flags.9
MLINKS+=namei.9 NDFREE.9 \
- namei.9 NDINIT.9
+ namei.9 NDINIT.9 \
+ namei.9 NDHASGIANT.9
MLINKS+=pbuf.9 getpbuf.9 \
pbuf.9 relpbuf.9 \
pbuf.9 trypbuf.9
Modified: head/share/man/man9/namei.9
==============================================================================
--- head/share/man/man9/namei.9 Thu Jan 14 14:30:54 2010 (r202283)
+++ head/share/man/man9/namei.9 Thu Jan 14 14:36:39 2010 (r202284)
@@ -44,7 +44,7 @@
.Nd pathname translation and lookup operations
.Sh SYNOPSIS
.In sys/param.h
-.In sys/proc.h
+.In sys/fcntl.h
.In sys/namei.h
.Ft int
.Fn namei "struct nameidata *ndp"
@@ -315,6 +315,34 @@ flag can be passed to the
.Fn NDFREE
function.
.El
+.Sh RETURN VALUES
+If successful,
+.Fn namei
+will return 0, otherwise it will return an error.
+.Sh ERRORS
+Errors which
+.Fn namei
+may return:
+.Bl -tag -width Er
+.It Bq Er ENOTDIR
+A component of the specified pathname is not a directory when a directory is
+expected.
+.It Bq Er ENAMETOOLONG
+A component of a pathname exceeded 255 characters,
+or an entire pathname exceeded 1023 characters.
+.It Bq Er ENOENT
+A component of the specified pathname does not exist,
+or the pathname is an empty string.
+.It Bq Er ACCES
+An attempt is made to access a file in a way forbidden by its file access
+permissions.
+.It Bq Er ELOOP
+Too many symbolic links were encountered in translating the pathname.
+.It Bq Er EISDIR
+An attempt is made to open a directory with write mode specified.
+.It Bq Er EROFS
+An attempt is made to modify a file or directory on a read-only file system.
+.El
.Sh FILES
.Bl -tag
.It Pa src/sys/kern/vfs_lookup.c
_______________________________________________
svn-src-all at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe at freebsd.org"
From dfilter at FreeBSD.ORG Thu Jan 14 14:40:08 2010
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Thu, 14 Jan 2010 14:40:08 GMT
Subject: docs/142816: commit references a PR
Message-ID: <201001141440.o0EEe8sx087925@freefall.freebsd.org>
The following reply was made to PR docs/142816; it has been noted by GNATS.
From: dfilter at FreeBSD.ORG (dfilter service)
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: docs/142816: commit references a PR
Date: Thu, 14 Jan 2010 14:36:54 +0000 (UTC)
Author: jhb
Date: Thu Jan 14 14:36:39 2010
New Revision: 202284
URL: http://svn.freebsd.org/changeset/base/202284
Log:
- Update required headers for namei() to add and remove
.
- Add RETURN VALUES and ERROR sections for namei()'s error return values.
- Add a missing link to NDHASGIANT.9.
PR: docs/142815, docs/142816
Submitted by: Lachlan Kang (1, 2)
MFC after: 3 days
Modified:
head/share/man/man9/Makefile
head/share/man/man9/namei.9
Modified: head/share/man/man9/Makefile
==============================================================================
--- head/share/man/man9/Makefile Thu Jan 14 14:30:54 2010 (r202283)
+++ head/share/man/man9/Makefile Thu Jan 14 14:36:39 2010 (r202284)
@@ -903,7 +903,8 @@ MLINKS+=mutex.9 mtx_assert.9 \
mutex.9 mtx_unlock_spin.9 \
mutex.9 mtx_unlock_spin_flags.9
MLINKS+=namei.9 NDFREE.9 \
- namei.9 NDINIT.9
+ namei.9 NDINIT.9 \
+ namei.9 NDHASGIANT.9
MLINKS+=pbuf.9 getpbuf.9 \
pbuf.9 relpbuf.9 \
pbuf.9 trypbuf.9
Modified: head/share/man/man9/namei.9
==============================================================================
--- head/share/man/man9/namei.9 Thu Jan 14 14:30:54 2010 (r202283)
+++ head/share/man/man9/namei.9 Thu Jan 14 14:36:39 2010 (r202284)
@@ -44,7 +44,7 @@
.Nd pathname translation and lookup operations
.Sh SYNOPSIS
.In sys/param.h
-.In sys/proc.h
+.In sys/fcntl.h
.In sys/namei.h
.Ft int
.Fn namei "struct nameidata *ndp"
@@ -315,6 +315,34 @@ flag can be passed to the
.Fn NDFREE
function.
.El
+.Sh RETURN VALUES
+If successful,
+.Fn namei
+will return 0, otherwise it will return an error.
+.Sh ERRORS
+Errors which
+.Fn namei
+may return:
+.Bl -tag -width Er
+.It Bq Er ENOTDIR
+A component of the specified pathname is not a directory when a directory is
+expected.
+.It Bq Er ENAMETOOLONG
+A component of a pathname exceeded 255 characters,
+or an entire pathname exceeded 1023 characters.
+.It Bq Er ENOENT
+A component of the specified pathname does not exist,
+or the pathname is an empty string.
+.It Bq Er ACCES
+An attempt is made to access a file in a way forbidden by its file access
+permissions.
+.It Bq Er ELOOP
+Too many symbolic links were encountered in translating the pathname.
+.It Bq Er EISDIR
+An attempt is made to open a directory with write mode specified.
+.It Bq Er EROFS
+An attempt is made to modify a file or directory on a read-only file system.
+.El
.Sh FILES
.Bl -tag
.It Pa src/sys/kern/vfs_lookup.c
_______________________________________________
svn-src-all at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe at freebsd.org"
From jhb at freebsd.org Thu Jan 14 15:03:51 2010
From: jhb at freebsd.org (John Baldwin)
Date: Thu, 14 Jan 2010 09:30:43 -0500
Subject: docs/142816: [patch] namei(9) return values
In-Reply-To: <201001140520.o0E5KsgU030632@www.freebsd.org>
References: <201001140520.o0E5KsgU030632@www.freebsd.org>
Message-ID: <201001140930.43322.jhb@freebsd.org>
On Thursday 14 January 2010 12:20:54 am Lachlan Kang wrote:
>
> >Number: 142816
> >Category: docs
> >Synopsis: [patch] namei(9) return values
> >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 Jan 14 05:30:02 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Lachlan Kang
> >Release: FreeBSD 8.0-RELEASE
> >Organization:
> >Environment:
> >Description:
> The manpage namei(9) does not specify the return value of the function
namei().
> The function namei() returns 0 on success, or errno on failure.
> I skimmed through the namei() source code (src/sys/kern/vfs_lookup.c) and
added a simple RETURN VALUES and ERRORS section to the namei(9) manpage.
> The error code descriptions were simply copied from intro(2).
> >How-To-Repeat:
> man 9 namei
> >Fix:
> Add a RETURN VALUES and ERRORS section to namei(9).
>
> Patch attached with submission follows:
Thanks! I've modified this slightly (added missing line breaks to ease
translation work) and changed the error descriptions to more closely match
what is used in open(2).
--
John Baldwin
From jhb at FreeBSD.org Thu Jan 14 15:04:38 2010
From: jhb at FreeBSD.org (jhb at FreeBSD.org)
Date: Thu, 14 Jan 2010 15:04:38 GMT
Subject: docs/142815: [patch] namei(9) required include
Message-ID: <201001141504.o0EF4chL012963@freefall.freebsd.org>
Synopsis: [patch] namei(9) required include
State-Changed-From-To: open->closed
State-Changed-By: jhb
State-Changed-When: Thu Jan 14 15:03:37 UTC 2010
State-Changed-Why:
Fix committed, thanks!
http://www.freebsd.org/cgi/query-pr.cgi?pr=142815
From jhb at freebsd.org Thu Jan 14 15:10:05 2010
From: jhb at freebsd.org (John Baldwin)
Date: Thu, 14 Jan 2010 15:10:05 GMT
Subject: docs/142816: [patch] namei(9) return values
Message-ID: <201001141510.o0EFA5bQ013091@freefall.freebsd.org>
The following reply was made to PR docs/142816; it has been noted by GNATS.
From: John Baldwin
To: freebsd-doc at freebsd.org
Cc: Lachlan Kang ,
freebsd-gnats-submit at freebsd.org
Subject: Re: docs/142816: [patch] namei(9) return values
Date: Thu, 14 Jan 2010 09:30:43 -0500
On Thursday 14 January 2010 12:20:54 am Lachlan Kang wrote:
>
> >Number: 142816
> >Category: docs
> >Synopsis: [patch] namei(9) return values
> >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 Jan 14 05:30:02 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Lachlan Kang
> >Release: FreeBSD 8.0-RELEASE
> >Organization:
> >Environment:
> >Description:
> The manpage namei(9) does not specify the return value of the function
namei().
> The function namei() returns 0 on success, or errno on failure.
> I skimmed through the namei() source code (src/sys/kern/vfs_lookup.c) and
added a simple RETURN VALUES and ERRORS section to the namei(9) manpage.
> The error code descriptions were simply copied from intro(2).
> >How-To-Repeat:
> man 9 namei
> >Fix:
> Add a RETURN VALUES and ERRORS section to namei(9).
>
> Patch attached with submission follows:
Thanks! I've modified this slightly (added missing line breaks to ease
translation work) and changed the error descriptions to more closely match
what is used in open(2).
--
John Baldwin
From jhb at FreeBSD.org Thu Jan 14 15:26:13 2010
From: jhb at FreeBSD.org (jhb at FreeBSD.org)
Date: Thu, 14 Jan 2010 15:26:13 GMT
Subject: docs/142816: [patch] namei(9) return values
Message-ID: <201001141526.o0EFQDa8030289@freefall.freebsd.org>
Synopsis: [patch] namei(9) return values
State-Changed-From-To: open->closed
State-Changed-By: jhb
State-Changed-When: Thu Jan 14 15:25:45 UTC 2010
State-Changed-Why:
Fix committed, thanks!
http://www.freebsd.org/cgi/query-pr.cgi?pr=142816
From bland at FreeBSD.org Fri Jan 15 14:49:11 2010
From: bland at FreeBSD.org (bland at FreeBSD.org)
Date: Fri, 15 Jan 2010 14:49:11 GMT
Subject: docs/140082: [handbook] handbook/jails: russian translation is
missing
Message-ID: <201001151449.o0FEnB79073205@freefall.freebsd.org>
Synopsis: [handbook] handbook/jails: russian translation is missing
Responsible-Changed-From-To: freebsd-doc->bland
Responsible-Changed-By: bland
Responsible-Changed-When: Fri Jan 15 14:48:48 UTC 2010
Responsible-Changed-Why:
Take.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140082
From royce.williams at gmail.com Fri Jan 15 21:59:16 2010
From: royce.williams at gmail.com (Royce Williams)
Date: Fri, 15 Jan 2010 12:28:56 -0900
Subject: new IANA IP blocks reserved for documentation
Message-ID: <9dd082311001151328i7b9d7a3ax18dfc232b430905d@mail.gmail.com>
>From the recently-announced RFC 5737:
http://tools.ietf.org/html/rfc5737
The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2),
and 203.0.113.0/24 (TEST-NET-3) are provided for use in
documentation.
[...]
Addresses within the TEST-NET-1, TEST-NET-2, and TEST-NET-3 blocks
SHOULD NOT appear on the public Internet and are used without any
coordination with IANA or an Internet registry [RFC2050]. Network
operators SHOULD add these address blocks to the list of non-
routeable address spaces, and if packet filters are deployed, then
this address block SHOULD be added to packet filters.
These blocks are not for local use, and the filters may be used in
both local and public contexts.
Royce
From tomek.cedro at gmail.com Sat Jan 16 13:41:30 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sat, 16 Jan 2010 13:13:18 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
Message-ID: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
Hello world!
I have a remark regarding the DVD/BluRay recording, as described in
the Handbook, that it currently requires cdrtools-devel package first
installed instead of cdrtools, to be able to create filesystem image
that supports >4GB per-file-size. Current cdrtools package was
released in September 2004 and is outdated as hell, it does not
support "-iso-level 3" switch, so it propagates problems to all
related recording software like dvd+rw-utils, brasero, k3b, dvdtk,
etc...
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
Please take a look at comp.unix.bsd.freebsd.misc / cdrkit vs.
dvd+rw-tools and the dvd iso 4gb max filesize problem
The author of the cdrtools suite is involved in the discussion and he
declares a new release soon, so the problem might be solved, however I
think that it is good idea to add this information about
cdrtools-devel package into Handbook documentation, in case of future
troubles with cdrtools releases.
Best regards,
Tomek Cedro
ps/2: is it the proper way to add modifications to the FreeBSD Handbook? :-)
--
CeDeROM, http://www.tomek.cedro.info
From blackend at FreeBSD.org Sat Jan 16 14:44:24 2010
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Sat, 16 Jan 2010 15:44:20 +0100
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
Message-ID: <20100116144420.GC1272@gothic.blackend.org>
On Sat, Jan 16, 2010 at 01:13:18PM +0000, CeDeROM wrote:
> Hello world!
>
> I have a remark regarding the DVD/BluRay recording, as described in
> the Handbook, that it currently requires cdrtools-devel package first
> installed instead of cdrtools, to be able to create filesystem image
> that supports >4GB per-file-size. Current cdrtools package was
> released in September 2004 and is outdated as hell, it does not
> support "-iso-level 3" switch, so it propagates problems to all
> related recording software like dvd+rw-utils, brasero, k3b, dvdtk,
> etc...
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
>
> Please take a look at comp.unix.bsd.freebsd.misc / cdrkit vs.
> dvd+rw-tools and the dvd iso 4gb max filesize problem
>
> The author of the cdrtools suite is involved in the discussion and he
> declares a new release soon, so the problem might be solved, however I
> think that it is good idea to add this information about
> cdrtools-devel package into Handbook documentation, in case of future
> troubles with cdrtools releases.
>
We can add a note to the Handbook but it'd a better idea to have the fix in
default cdrtools port, I mean the one used by all burning applications.
I let marius@ (the port maintainer) choosing the best solution.
--
Marc
From tomek.cedro at gmail.com Sat Jan 16 15:54:18 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sat, 16 Jan 2010 15:54:07 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <20100116153838.GE18141@alchemy.franken.de>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
Message-ID: <3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
On Sat, Jan 16, 2010 at 3:38 PM, Marius Strobl
wrote:
>> We can add a note to the Handbook but it'd a better idea to have the fix in
>> default cdrtools port, I mean the one used by all burning applications.
>>
>> I let marius@ (the port maintainer) choosing the best solution.
>
> Patching cdrtools is a complicated topic as the author is very strict
> about the license so it typically means creating an unsupported fork
> which needs to be compiled with -DSOURCE_MODIFIED etc. Backporting
> features to 2.01 also isn't easily possible as for most parts it's
> GPL in 2.01 versus CDDL in 2.01.01. As long a the release engineering
> depends on a working mkisofs I'm also reluctant to change the version
> tracked by sysutils/cdrtools to the alpha releases. If a port requires
> features from 2.01.01 it should just depend on sysutils/cdrtools-devel
> explicitly. There are some differences in pkg-plist files of the two
> cdrtools ports which should make this actually possible.
Thank you Marius, my opinion is the same. I will try to ask author of
the cdrtools for some explict date of the new release.
Marc - I still think there is a need to add info about "-iso-level 3"
and the "-udf -iso-level 3" switch of mkisofs to the Handbook, as this
option allows burning files with per-file-size limit >4GB and use
level 3 of the ISO-9660. This option must be applied to mkisofs and
dvd+rw-tools, neverthless of the mkisofs release, so giving this hint
explictly in a Handbook will help commandline users. The other thing
is that it works only in releases older than 2.01.01aXXX and should
work with nearest stable release.
Please follow discussion on the usenet - there are all of the details
necessary to acknowlege my point of view.
Best regards,
Tomek Cedro
--
CeDeROM, http://www.tomek.cedro.info
From blackend at FreeBSD.org Sat Jan 16 15:55:44 2010
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Sat, 16 Jan 2010 16:55:32 +0100
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <20100116153838.GE18141@alchemy.franken.de>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
Message-ID: <20100116155532.GD1272@gothic.blackend.org>
On Sat, Jan 16, 2010 at 04:38:38PM +0100, Marius Strobl wrote:
> On Sat, Jan 16, 2010 at 03:44:20PM +0100, Marc Fonvieille wrote:
> > On Sat, Jan 16, 2010 at 01:13:18PM +0000, CeDeROM wrote:
> > > Hello world!
> > >
> > > I have a remark regarding the DVD/BluRay recording, as described in
> > > the Handbook, that it currently requires cdrtools-devel package first
> > > installed instead of cdrtools, to be able to create filesystem image
> > > that supports >4GB per-file-size. Current cdrtools package was
> > > released in September 2004 and is outdated as hell, it does not
> > > support "-iso-level 3" switch, so it propagates problems to all
> > > related recording software like dvd+rw-utils, brasero, k3b, dvdtk,
> > > etc...
> > >
> > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
> > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
> > >
> > > Please take a look at comp.unix.bsd.freebsd.misc / cdrkit vs.
> > > dvd+rw-tools and the dvd iso 4gb max filesize problem
> > >
> > > The author of the cdrtools suite is involved in the discussion and he
> > > declares a new release soon, so the problem might be solved, however I
> > > think that it is good idea to add this information about
> > > cdrtools-devel package into Handbook documentation, in case of future
> > > troubles with cdrtools releases.
> > >
> >
> > We can add a note to the Handbook but it'd a better idea to have the fix in
> > default cdrtools port, I mean the one used by all burning applications.
> >
> > I let marius@ (the port maintainer) choosing the best solution.
> >
>
> Patching cdrtools is a complicated topic as the author is very strict
> about the license so it typically means creating an unsupported fork
> which needs to be compiled with -DSOURCE_MODIFIED etc. Backporting
> features to 2.01 also isn't easily possible as for most parts it's
> GPL in 2.01 versus CDDL in 2.01.01. As long a the release engineering
> depends on a working mkisofs I'm also reluctant to change the version
> tracked by sysutils/cdrtools to the alpha releases. If a port requires
> features from 2.01.01 it should just depend on sysutils/cdrtools-devel
> explicitly. There are some differences in pkg-plist files of the two
> cdrtools ports which should make this actually possible.
>
Ok thanks Marius, your answer is clear. No need to change something.
If one wants to burn a > 4GB .iso file sysutils/cdrtools-devel must be
installed instead of sysutils/cdrtools. I'll update the Handbook on
this point.
--
Marc
From marius at alchemy.franken.de Sat Jan 16 16:14:21 2010
From: marius at alchemy.franken.de (Marius Strobl)
Date: Sat, 16 Jan 2010 16:38:38 +0100
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <20100116144420.GC1272@gothic.blackend.org>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
Message-ID: <20100116153838.GE18141@alchemy.franken.de>
On Sat, Jan 16, 2010 at 03:44:20PM +0100, Marc Fonvieille wrote:
> On Sat, Jan 16, 2010 at 01:13:18PM +0000, CeDeROM wrote:
> > Hello world!
> >
> > I have a remark regarding the DVD/BluRay recording, as described in
> > the Handbook, that it currently requires cdrtools-devel package first
> > installed instead of cdrtools, to be able to create filesystem image
> > that supports >4GB per-file-size. Current cdrtools package was
> > released in September 2004 and is outdated as hell, it does not
> > support "-iso-level 3" switch, so it propagates problems to all
> > related recording software like dvd+rw-utils, brasero, k3b, dvdtk,
> > etc...
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
> >
> > Please take a look at comp.unix.bsd.freebsd.misc / cdrkit vs.
> > dvd+rw-tools and the dvd iso 4gb max filesize problem
> >
> > The author of the cdrtools suite is involved in the discussion and he
> > declares a new release soon, so the problem might be solved, however I
> > think that it is good idea to add this information about
> > cdrtools-devel package into Handbook documentation, in case of future
> > troubles with cdrtools releases.
> >
>
> We can add a note to the Handbook but it'd a better idea to have the fix in
> default cdrtools port, I mean the one used by all burning applications.
>
> I let marius@ (the port maintainer) choosing the best solution.
>
Patching cdrtools is a complicated topic as the author is very strict
about the license so it typically means creating an unsupported fork
which needs to be compiled with -DSOURCE_MODIFIED etc. Backporting
features to 2.01 also isn't easily possible as for most parts it's
GPL in 2.01 versus CDDL in 2.01.01. As long a the release engineering
depends on a working mkisofs I'm also reluctant to change the version
tracked by sysutils/cdrtools to the alpha releases. If a port requires
features from 2.01.01 it should just depend on sysutils/cdrtools-devel
explicitly. There are some differences in pkg-plist files of the two
cdrtools ports which should make this actually possible.
Marius
From blackend at freebsd.org Sat Jan 16 18:49:12 2010
From: blackend at freebsd.org (Marc Fonvieille)
Date: Sat, 16 Jan 2010 19:49:03 +0100
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
Message-ID: <20100116184903.GA3235@gothic.blackend.org>
On Sat, Jan 16, 2010 at 03:54:07PM +0000, CeDeROM wrote:
> On Sat, Jan 16, 2010 at 3:38 PM, Marius Strobl
> wrote:
> >> We can add a note to the Handbook but it'd a better idea to have the fix in
> >> default cdrtools port, I mean the one used by all burning applications.
> >>
> >> I let marius@ (the port maintainer) choosing the best solution.
> >
> > Patching cdrtools is a complicated topic as the author is very strict
> > about the license so it typically means creating an unsupported fork
> > which needs to be compiled with -DSOURCE_MODIFIED etc. Backporting
> > features to 2.01 also isn't easily possible as for most parts it's
> > GPL in 2.01 versus CDDL in 2.01.01. As long a the release engineering
> > depends on a working mkisofs I'm also reluctant to change the version
> > tracked by sysutils/cdrtools to the alpha releases. If a port requires
> > features from 2.01.01 it should just depend on sysutils/cdrtools-devel
> > explicitly. There are some differences in pkg-plist files of the two
> > cdrtools ports which should make this actually possible.
>
> Thank you Marius, my opinion is the same. I will try to ask author of
> the cdrtools for some explict date of the new release.
>
> Marc - I still think there is a need to add info about "-iso-level 3"
> and the "-udf -iso-level 3" switch of mkisofs to the Handbook, as this
> option allows burning files with per-file-size limit >4GB and use
> level 3 of the ISO-9660. This option must be applied to mkisofs and
> dvd+rw-tools, neverthless of the mkisofs release, so giving this hint
> explictly in a Handbook will help commandline users. The other thing
> is that it works only in releases older than 2.01.01aXXX and should
> work with nearest stable release.
>
> Please follow discussion on the usenet - there are all of the details
> necessary to acknowlege my point of view.
>
So, does the following is Ok for addition to the Handbook?
--
Note:
If you need to burn files larger than 4.38 GB, for example in the case
of a double layer media, the -iso-level 3 option must be passed to
mkisofs(8). Therefore this option has to be added to any growisofs(1)
command line, e.g.:
# growisofs -dvd-compat -Z /dev/cd0 -iso-level 3 -J -R /path/to/data
or
# growisofs -dvd-compat -Z /dev/cd0=imagefile.iso -iso-level 3
Be sure to have the sysutils/cdrtools-devel port installed instead of
sysutils/cdrtools. This later comes with a mkisofs(8) version that does
not work very well with the -iso-level 3 option.
--
--
Marc
From tomek.cedro at gmail.com Sat Jan 16 19:43:16 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sat, 16 Jan 2010 19:43:11 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <20100116184903.GA3235@gothic.blackend.org>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
Message-ID: <3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
Hello Marc!
On Sat, Jan 16, 2010 at 6:49 PM, Marc Fonvieille wrote:
> So, does the following is Ok for addition to the Handbook?
>
> --
> Note:
> If you need to burn files larger than 4.38 GB, for example in the case
> of a double layer media, the -iso-level 3 option must be passed to
> mkisofs(8). ?Therefore this option has to be added to any growisofs(1)
> command line, e.g.:
>
> # growisofs -dvd-compat -Z /dev/cd0 -iso-level 3 -J -R /path/to/data
>
> or
>
> # growisofs -dvd-compat -Z /dev/cd0=imagefile.iso -iso-level 3
>
> Be sure to have the sysutils/cdrtools-devel port installed instead of
> sysutils/cdrtools. ?This later comes with a mkisofs(8) version that does
> not work very well with the -iso-level 3 option.
> --
>
>
> --
> Marc
>
To doublecheck that:
%growisofs -dvd-compat -R -J -iso-level 3 -Z /dev/cd1 /path/to/data/*
And it is working. The "-iso-level 3" is required to burn DVD with
per-file-size >4GB, that is some large audio or video file.
Then I have created an ISO file form these files, to test the iso
burning, but I got this error:
growisofs: no mkisofs options are permitted with =, aborting...
So I suppose this switch is only aplicable at creating the iso image
stage. When a valid iso image is already created (ie. with "-iso-level
3" switch) no additional switch is necessary for growisofs. Please
note that I am already using the cdrtools-devel package (in cdrtools I
did not have this warning). Also old version of mkisofs did not
complain about -iso-level 3 switch but gave an error that some large
files will not fit on image.
To confirm the image burning from an iso containing the large files
with no -iso-level 3 switch:
%mkisofs -R -J -iso-level 3 -o ../dvd.iso *
(...)
99.18% done, estimate finish Sat Jan 16 20:03:51 2010
99.40% done, estimate finish Sat Jan 16 20:03:50 2010
99.62% done, estimate finish Sat Jan 16 20:03:51 2010
99.84% done, estimate finish Sat Jan 16 20:03:50 2010
Total translation table size: 0
Total rockridge attributes bytes: 713
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
2288723 extents written (4470 MB)
%cd ..
%growisofs -dvd-compat -R -J -Z /dev/cd1=dvd.iso -iso-level 3
growisofs: no mkisofs options are permitted with =, aborting...
%growisofs -dvd-compat -Z /dev/cd1=dvd.iso
WARNING: /dev/cd1 already carries isofs!
About to execute 'builtin_dd if=dvd.iso of=/dev/pass1 obs=32k seek=0'
Sleeping for 5 sec...
(...)
4623237120/4687304704 (98.6%) @4.0x, remaining 0:11 RBU 100.0% UBU 99.8%
4641751040/4687304704 (99.0%) @4.0x, remaining 0:08 RBU 100.0% UBU 100.0%
4660232192/4687304704 (99.4%) @4.0x, remaining 0:04 RBU 80.8% UBU 100.0%
4678713344/4687304704 (99.8%) @4.0x, remaining 0:01 RBU 25.7% UBU 93.4%
builtin_dd: 2288736*2KB out @ average 4.0x1352KBps
/dev/pass1: flushing cache
/dev/pass1: writing lead-out
And after checking - the files are on the disk (the large file is
automatically split into two and works well).
Therefore I would recommend something like this:
--
Note:
If you need to burn directly to a disk or create an ISO file
containing files larger than 4.38 GB, the "-iso-level 3" option must
be passed to mkisofs(8). Therefore this option has to be added to any
mkisofs(8) commandline while creating the ISO image, or growisofs(1)
command line used for burning directly to a disk, e.g.:
%mkisofs -R -J -iso-level 3 -o ../dvd.iso *
%growisofs -dvd-compat -R -J -iso-level 3 -Z /dev/cd0 /path/to/data/*
When you have an ISO image containing large files already inside, no
additional options are required for growisofs(1) to burn the image on
a disk.
Also, be sure that you have cdrtools version >2.01, as the older ones
does not contain large file support. This propagates issues in other
GUI-based applications. Currently only the sysutils/cdrtools-devel
port contains alpha version fresh enough to support large files, so if
you experience troubles please move to the development package.
--
Best regards!
Tomek Cedro
--
CeDeROM, http://www.tomek.cedro.info
From tomek.cedro at gmail.com Sat Jan 16 20:33:31 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sat, 16 Jan 2010 20:33:24 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
<3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
Message-ID: <3fcfb0ba1001161233y2c158c1bq79aca541a42df046@mail.gmail.com>
Marc, please wait with publishing - I have verified files inside of a
disk - the files generted this way looks corrupted :-(
This is theoretically the only way to have support for large files,
somehow confirmed by other users, but it looks also teher are still
some issues.
My knowledge is too small - I will have to wait for support on the
usenet and probably the author of the mkisofs.
Regards,
Tomek
--
CeDeROM, http://www.tomek.cedro.info
From tomek.cedro at gmail.com Sat Jan 16 23:09:49 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sat, 16 Jan 2010 23:03:11 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
<3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
Message-ID: <3fcfb0ba1001161503m5dde00d3x6e167830060d8de@mail.gmail.com>
Marc, sorry the last post, I just want the information to be complete
and true - after some experimenting it turns out that the only working
option for large files is to use "mkisofs -udf -iso-level 3" and then
mount disk as an UDF volume - if mounted as ISO9660 the large files
will be doubled and truncated. I am waiting for confirmation on a
usenet, you can also verify this solution please to be sure.
Below is the updated note:
==
Note:
In order to have working files larger than 4.38GB in your compilation,
an UDF/ISO-9660 hybrid must be created by passing additional "-udf
-iso-level 3" parameter to a mkisofs(8) and all related programs (ie.
growisofs(1)). This is required only when creating an ISO image file,
or writing files directly to a disk. Disk created this way must be
mounted as an UDF filesystem with mount(8) utility - so it will be
usable only on an UDF aware Operating System - otherwise it will look
as if it contains corrupted files.
To create an ISO file:
%mkisofs -R -J -udf -iso-level 3 -o ../dvd.iso *
To burn files directly to a disk:
%growisofs -dvd-compat -R -J -udf -iso-level 3 -Z /dev/cd0 /path/to/data/*
When you have an ISO image containing large files already inside, no
additional options are required for growisofs(1) to burn that image on
a disk.
Also, be sure that you have cdrtools version >2.01, as the older ones
does not contain large files support. This propagates issues in other
GUI-based applications. Currently only the sysutils/cdrtools-devel
port contains alpha version fresh enough to support large files, so if
you experience troubles please move to the development package.
==
Best regards,
Tomek Cedro
--
CeDeROM, http://www.tomek.cedro.info
From tomek.cedro at gmail.com Sun Jan 17 16:29:18 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Sun, 17 Jan 2010 16:29:15 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001161503m5dde00d3x6e167830060d8de@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
<3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
<3fcfb0ba1001161503m5dde00d3x6e167830060d8de@mail.gmail.com>
Message-ID: <3fcfb0ba1001170829n2fb71473u5ec60b7f4401c0e1@mail.gmail.com>
Hello again!
Just as the discussion advances, there is one more proposition from my
side for the lat sentence of the note:
==
Currently only the sysutils/cdrtools-devel port contains alpha version
fresh enough to support large files, so if you experience troubles
please move to the development package - and don't forget to read the
new manual page, as it contains lots of new information.
==
Regarding the cdrtools suite it is in fact very hard nut to crack :-\
Best regards!
Tomek
--
CeDeROM, http://www.tomek.cedro.info
From vermaden at interia.pl Sun Jan 17 23:00:16 2010
From: vermaden at interia.pl (vermaden)
Date: Sun, 17 Jan 2010 22:52:22 GMT
Subject: docs/142917: top(1) man page does not include information about
VCSW and IVCSW
Message-ID: <201001172252.o0HMqMUj025099@www.freebsd.org>
>Number: 142917
>Category: docs
>Synopsis: top(1) man page does not include information about VCSW and IVCSW
>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: Sun Jan 17 23:00:13 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: vermaden
>Release: 8.0-RELEASE
>Organization:
>Environment:
Stock 8.0-RELEASE output.
>Description:
top(1) man page does not include information about VCSW and IVCSW, which can be easily updated for example by by data from here:
http://lists.freebsd.org/pipermail/freebsd-questions/2007-September/158479.html
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From turutani at scphys.kyoto-u.ac.jp Mon Jan 18 03:30:08 2010
From: turutani at scphys.kyoto-u.ac.jp (Tsurutani Naoki)
Date: Mon, 18 Jan 2010 12:24:29 +0900 (JST)
Subject: docs/142925: k8temp(4) should be renamed
Message-ID: <201001180324.o0I3OTuN011096@h116.65.226.10.32118.vlan.kuins.net>
>Number: 142925
>Category: docs
>Synopsis: k8temp(4) should be renamed
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jan 18 03:30:08 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Tsurutani Naoki
>Release: FreeBSD 7.2-STABLE amd64
>Organization:
>Environment:
System: FreeBSD h116.65.226.10.32118.vlan.kuins.net 7.2-STABLE FreeBSD 7.2-STABLE #20: Mon Jun 22 09:33:07 JST 2009 turutani at h116.65.226.10.32118.vlan.kuins.net:/usr/local/work/usr/obj/usr/src/sys/POLYMER13 amd64
>Description:
man page of k8temp(4) tells k8temp.ko exists,
but it does not exists, for the name "k8temp" is renamed to
"amdtemp" on rev.192654.
>How-To-Repeat:
>Fix:
rename k8temp to amdtemp, and fix the contents.
>Release-Note:
>Audit-Trail:
>Unformatted:
From murray at stokely.org Mon Jan 18 07:57:18 2010
From: murray at stokely.org (Murray Stokely)
Date: Sun, 17 Jan 2010 23:57:17 -0800
Subject: Proposed new doc hierarchy for closed-captions / transcripts from
conferences
Message-ID: <2a7894eb1001172357t754cee36u760d9ddd1d6a7665@mail.gmail.com>
As some of you might be aware I have been working on getting closed
captions for the videos of FreeBSD related talks at conferences. In
the last month I've started using the YouTube Machine Learning to
produce the first automatic transcript and then paying human editors
through Amazon Mechanical Turk to improve the technical vocabulary /
general editing of the transcripts.
There are now four videos in the BSD Conferences YouTube channel with
relatively good quality human-edited english language transcripts.
(e.g. pointers at
http://freebsd.stokely.org/2010/01/improved-conference-captions-from.html)
The caption files themselves are simple ASCII text files with one line
for the start/end time of the text to be displayed, 1 or 2 lines for
the text to be displayed, and a blank line to separate the next
record.
I would like to start checking in these text files under
doc/en_US.ISO8859-1/captions/ for a number of reasons.
1. I want to make it easier for others to correct any mistakes in the captions.
2. I want to make it easier to translators to produce localized
captions for the most popular videos.
3. Keep a centralized repository of the captions outside of YouTube,
so other hosting sites or systems are able to use them.
4. Increase discoverability of technical content discussed in the
conference talks with indexable transcripts open to search engines.
The blog post above has some example text files that I'd like to check
in. It then becomes a matter of choosing the hierarchy.
I might suggest:
doc/${LANG}/captions/${YEAR}/${CONFERENCE}/${TALK}
e.g.
doc/en_US.ISO8859-1/captions/2009/asiabsdcon/mckusick-kernelinternals.sbv
Thoughts?
- Murray
From bugmaster at FreeBSD.org Mon Jan 18 11:06:07 2010
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon, 18 Jan 2010 11:06:06 GMT
Subject: Current unassigned doc problem reports
Message-ID: <201001181106.o0IB66PY046782@freefall.freebsd.org>
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)
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.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/142925 doc k8temp(4) should be renamed
o docs/142917 doc top(1) man page does not include information about VCS
o docs/142437 doc [request] Errata Notices Index missing
o docs/142429 doc USERS directive doesn't work as documented in Porter's
o docs/142418 doc [PATCH] newfs_msdos(8) doc fix
a docs/142341 doc jail(8): Jail escape when cwd is moved from the host s
o docs/142243 doc Netcat (nc(1)) manual mistake
p docs/142204 doc bad link in bsd-family-tree
o docs/142168 doc ld(1): ldd(1) not mentioned in ld(1) manpage
o docs/141765 doc [handbook] [patch] Added note about architectures when
o docs/141636 doc [handbook] [patch] Updated info about Firefox in Handb
o docs/141316 doc ntpd(8): ntpd does not honor -d flag
o docs/140918 doc [handbook] update 8.0 handbook about serial port /dev
s docs/140847 doc [request] add documentation on ECMP and new route args
o docs/140814 doc [handbook][patch] Chapter 15 - Jails: add section on c
o docs/140703 doc [patch] add xorg-minimal as alternative for X11 Distri
o docs/140495 doc [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140474 doc signal(3) missing reference to NSIG
o docs/140458 doc [patch] Grammar fix for to{upper,lower}(3)
o docs/140457 doc [patch] Grammar fix for isspace(3)
o docs/140444 doc [patch] New Traditional Chinese translation of custom-
o docs/140435 doc ls(1), section STANDARD: the -A is exception from POSI
o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369 doc [patch] src/contrib/pf/man/pf.4
o docs/140075 doc release notes: missing word "NOT", which changes all t
o docs/139682 doc [PATCH] dialog(1) man page does not mention radiolist
o docs/139336 doc [request] ZFS documentation suggestion
o docs/139165 doc gssapi.3 man page out of sync with between crypto and
o docs/139153 doc [patch] the hier(7) man page needs to be updated
o docs/139018 doc translation of submitting.sgml from docproj/submitting
o docs/138887 doc manpage ports(7) incorrect
o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663 doc system(3) man page confuses users about "return value
o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca
o docs/138206 doc [patch] ntp(1): not enabled function, and false manual
o docs/137762 doc [handbook] proposed: mention "make delete-old" in sec
o docs/136918 doc [patch] grammar fixes to locking.9
o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa
o docs/136666 doc [handbook] Configure serial port for remote kernel deb
o docs/136035 doc ftpchroot(5) omits an important option
p docs/136029 doc MALLOC_PRODUCTION knob should be mentioned somewhere,
o docs/135999 doc Netgear GS105v3 should be added to list of switches th
o docs/135676 doc FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516 doc pax(1) manual not mentioning chflags unawareness
o docs/135475 doc [patch] jot(1) manpage and behaviour differ
o docs/135165 doc [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376 doc pthread(3): pthread manpages don't mention that PTHREA
o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222 doc installation failure of japanese docs
o docs/134123 doc The RUNQUEUE(9) man page is out of date
o docs/134074 doc [patch] locking.9 man page slight enhancements
o docs/133567 doc [patch] doc/Makefile switch to csup
o docs/133245 doc french handbook 27.3.5 amd.map amd.conf
o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section
o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839 doc [patch] Fix example script in ldap-auth article
o docs/132718 doc [handbook] Information about adding a new mirror is ou
o docs/132311 doc [patch] man5/nsmb.conf.5
o docs/132260 doc dhcpd(8) pid not stored in documented location
o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113 doc [handbook] Update handbook jails creation
o docs/131918 doc [patch] Fixes for the BPF(4) man page
o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by
o docs/131590 doc [patch] whitespace-only change of developers-handbook/
o docs/130895 doc [patch] No man page installed for padlock(4) on amd64
o docs/130364 doc Man page for top needs explanation of CPU states
o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or
o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson
o docs/129095 doc ipfw(8): Can not check that packet originating/destine
o docs/128524 doc No geom documentation for loading gjournal(8)
s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages
o docs/127908 doc [patch] readdir(3) error documentation
s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage
o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps
o docs/126484 doc libc function res-zonscut2 is not documented
o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in
o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052 doc minor update on handbook section 20.7.1
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541 doc [request] no man pages for wlan_scan_ap
o bin/121424 doc [patch] [ipfw] Rectify ambiguous English in manual
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/120539 doc Inconsistent ipfw's man page
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
a docs/119536 doc a few typos in French handbook (basics)
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118214 doc close(2) error returns incomplete
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747 doc 'break' system call needs a man page
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/116116 doc mktemp (3) re/move note
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/111425 doc Missing chunks of text in historical manpages
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111147 doc hostapd.conf is not documented
o docs/110999 doc carp(4) should document unsupported interface types
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max
o docs/109981 doc No manual entry for post-grohtml
o docs/109977 doc No manual entry for ksu
o docs/109973 doc No manual entry for c++filt
o docs/109972 doc No manual entry for zless/bzless
f docs/109226 doc [request] No manual entry for sntp
o docs/109201 doc [request]: manual for callbootd
a docs/108980 doc list of missing man pages
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
o docs/107924 docs [usb67] usbd(8) does not call detach
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/105608 doc fdc(4) debugging description staled
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand
o docs/83820 doc getino(3) manpage not installed
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596 doc Updates to mt(1) manual page
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/43823 doc [patch] update to environ(7) manpage
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/38556 doc EPS file of beastie, as addition to existing examples
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
a docs/30008 doc [patch] French softupdates document should be translat
o docs/27605 doc [patch] Cross-document references ()
o docs/26286 doc *printf(3) etc should gain format string warnings
o docs/24786 doc missing FILES descriptions in sa(4)
s docs/20028 doc ASCII docs should reflect tags in the sourc
176 problems total.
From blackend at freebsd.org Mon Jan 18 19:36:50 2010
From: blackend at freebsd.org (Marc Fonvieille)
Date: Mon, 18 Jan 2010 20:36:39 +0100
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <3fcfb0ba1001170829n2fb71473u5ec60b7f4401c0e1@mail.gmail.com>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
<3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
<3fcfb0ba1001161503m5dde00d3x6e167830060d8de@mail.gmail.com>
<3fcfb0ba1001170829n2fb71473u5ec60b7f4401c0e1@mail.gmail.com>
Message-ID: <20100118193639.GA1294@gothic.blackend.org>
Hello Tomek,
I committed a slightly modified version of your text to the Handbook.
Thanks for your contribution.
--
Marc
From tomek.cedro at gmail.com Mon Jan 18 19:42:04 2010
From: tomek.cedro at gmail.com (CeDeROM)
Date: Mon, 18 Jan 2010 19:42:02 +0000
Subject: cdrecord and burning disks on FreeBSD with filesize over 4GB
In-Reply-To: <20100118193639.GA1294@gothic.blackend.org>
References: <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com>
<20100116144420.GC1272@gothic.blackend.org>
<20100116153838.GE18141@alchemy.franken.de>
<3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
<20100116184903.GA3235@gothic.blackend.org>
<3fcfb0ba1001161143v5fe48bb6ne756deaaf26651fa@mail.gmail.com>
<3fcfb0ba1001161503m5dde00d3x6e167830060d8de@mail.gmail.com>
<3fcfb0ba1001170829n2fb71473u5ec60b7f4401c0e1@mail.gmail.com>
<20100118193639.GA1294@gothic.blackend.org>
Message-ID: <3fcfb0ba1001181142n1f2ae58fi2be6cd75f4bd8e61@mail.gmail.com>
On Mon, Jan 18, 2010 at 7:36 PM, Marc Fonvieille wrote:
> Hello Tomek,
>
> I committed a slightly modified version of your text to the Handbook.
> Thanks for your contribution.
Thank You guys for FreeBSD! :-)
--
CeDeROM, http://www.tomek.cedro.info
From jhelfman at e-e.com Mon Jan 18 20:30:11 2010
From: jhelfman at e-e.com (Jason)
Date: Mon, 18 Jan 2010 20:30:10 GMT
Subject: docs/142429: USERS directive doesn't work as documented in
Porter's Handbook
Message-ID: <201001182030.o0IKUAK0034355@freefall.freebsd.org>
The following reply was made to PR docs/142429; it has been noted by GNATS.
From: Jason
To: bug-followup at freebsd.org
Cc:
Subject: Re: docs/142429: USERS directive doesn't work as documented in
Porter's Handbook
Date: Mon, 18 Jan 2010 12:22:00 -0800
Correction. It does work.
Format of the UID is a little different, and after correcting my local
version, it worked as noted in the Porter's Handbook.
As a suggestion, it may be a good idea to add an example of a new UID
example that would work.
This can be closed.
-jgh
From linimon at FreeBSD.org Mon Jan 18 22:02:00 2010
From: linimon at FreeBSD.org (linimon at FreeBSD.org)
Date: Mon, 18 Jan 2010 22:01:59 GMT
Subject: docs/142429: USERS directive doesn't work as documented in
Porter's Handbook
Message-ID: <201001182201.o0IM1xfJ020470@freefall.freebsd.org>
Synopsis: USERS directive doesn't work as documented in Porter's Handbook
State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Mon Jan 18 22:01:47 UTC 2010
State-Changed-Why:
Closed at submitter's request.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142429
From linimon at FreeBSD.org Mon Jan 18 22:34:00 2010
From: linimon at FreeBSD.org (linimon at FreeBSD.org)
Date: Mon, 18 Jan 2010 22:33:58 GMT
Subject: docs/142938: [kld] share/examples: fix warnings
Message-ID: <201001182233.o0IMXwe7047501@freefall.freebsd.org>
Old Synopsis: [share/examples] [kld] fix warnings
New Synopsis: [kld] share/examples: fix warnings
Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Jan 18 22:33:12 UTC 2010
Responsible-Changed-Why:
make this a docs PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142938
From dragonz.payment at gmail.com Tue Jan 19 05:55:24 2010
From: dragonz.payment at gmail.com (Dragonz World Company)
Date: Tue, 19 Jan 2010 07:32:38 +0200
Subject: Fwd: Question
In-Reply-To: <6b0733101001182131u367d631cn921876e1df5baad9@mail.gmail.com>
References: <6b0733101001182131u367d631cn921876e1df5baad9@mail.gmail.com>
Message-ID: <6b0733101001182132i65f56c67ia04851de482cfebf@mail.gmail.com>
---------- Forwarded message ----------
From: Dragonz World Company
Date: Tue, Jan 19, 2010 at 7:31 AM
Subject: Question
To:
Hello
and i install socks5 script to run socks5 service in my dedicated server - i
want make security as example : only ips on this link can running socks5
service ( www.sitess.com/ips.txt ) and other people cant run this socks
service - i installed socks5 script and ipfw firewall can FreeBSD team make
this for my server - even for fees thanks and waiting ur kind reply
Thanks
--
Dragonz World Company 2010
--
Dragonz World Company 2010
From Meyser at xenet.de Tue Jan 19 15:30:08 2010
From: Meyser at xenet.de (Matthias Meyser)
Date: Tue, 19 Jan 2010 15:26:25 GMT
Subject: docs/142970: FreeBSD 8.0 Hardware Notes still mention ISDN cards
Message-ID: <201001191526.o0JFQPMl022326@www.freebsd.org>
>Number: 142970
>Category: docs
>Synopsis: FreeBSD 8.0 Hardware Notes still mention ISDN cards
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jan 19 15:30:08 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Matthias Meyser
>Release: FreeBSD 8-stable
>Organization:
XeNEt GmbH
>Environment:
FreeBSD intserv1.intern 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Jan 14 21:53:46 CET 2010 root at intserv1.intern:/usr/obj/usr/src/sys/INTSERV1 i386
>Description:
http://www.freebsd.org/releases/8.0R/hardware.html
still lists ISDN cards as supported.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From brueffer at FreeBSD.org Tue Jan 19 22:45:42 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Tue, 19 Jan 2010 23:45:41 +0100 (CET)
Subject: docs/142970: FreeBSD 8.0 Hardware Notes still mention ISDN cards
Message-ID: <201001192245.o0JMjflN034718@freefall.freebsd.org>
Synopsis: FreeBSD 8.0 Hardware Notes still mention ISDN cards
State-Changed-From-To: open->patched
State-Changed-By: brueffer
State-Changed-When: Tue Jan 19 23:44:39 CET 2010
State-Changed-Why:
Oops, very true, hardware notes in HEAD updated. Thanks!
Responsible-Changed-From-To: freebsd-doc->brueffer
Responsible-Changed-By: brueffer
Responsible-Changed-When: Tue Jan 19 23:44:39 CET 2010
Responsible-Changed-Why:
MFC reminder.
http://www.freebsd.org/cgi/query-pr.cgi?pr=142970
From brueffer at FreeBSD.org Wed Jan 20 17:25:25 2010
From: brueffer at FreeBSD.org (brueffer at FreeBSD.org)
Date: Wed, 20 Jan 2010 18:25:24 +0100 (CET)
Subject: docs/142938: [kld] share/examples: fix warnings
Message-ID: <201001201725.o0KHPOpw093877@freefall.freebsd.org>
Synopsis: [kld] share/examples: fix warnings
Responsible-Changed-From-To: freebsd-doc->wkoszek
Responsible-Changed-By: brueffer
Responsible-Changed-When: Wed Jan 20 18:24:13 CET 2010
Responsible-Changed-Why:
Wojciech worked in this area recently. Wojciech, could you take a look?
http://www.freebsd.org/cgi/query-pr.cgi?pr=142938
From robertjenssen at ozemail.com.au Thu Jan 21 00:40:02 2010
From: robertjenssen at ozemail.com.au (Robert Jenssen)
Date: Thu, 21 Jan 2010 00:36:46 GMT
Subject: docs/143041: doc/en__US.ISO8859-1 refers to slip, slirp,
slattach and pppd
Message-ID: <201001210036.o0L0ak43036660@www.freebsd.org>
>Number: 143041
>Category: docs
>Synopsis: doc/en__US.ISO8859-1 refers to slip, slirp, slattach and pppd
>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 Jan 21 00:40:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Robert Jenssen
>Release: 8-STABLE
>Organization:
>Environment:
FreeBSD kraken 8.0-STABLE FreeBSD 8.0-STABLE #0: Wed Jan 20 07:40:20 EST 2010 root at kraken:/usr/obj/usr/src/sys/KRAKEN i386
>Description:
slip, slirp, slattach and pppd have been removed from FreeBSD but they are still referred to in the documentation.
(There are still references to slip, slirp, slattach and pppd under /usr/src.)
>How-To-Repeat:
>Fix:
I have attached patches for
en_US.ISO8859-1/articles/dialup-firewall/article.sgml
en_US.ISO8859-1/books/faq/book.sgml
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
en_US.ISO8859-1/books/handbook/preface/preface.sgml
Patch attached with submission follows:
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file". Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# article.sgml.diff
# book.sgml.diff
# chapter.sgml.diff
# preface.sgml.diff
#
echo x - article.sgml.diff
sed 's/^X//' >article.sgml.diff << '2523653e9c26f6a06853ddd875789c39'
X*** orig/en_US.ISO8859-1/articles/dialup-firewall/article.sgml 2010-01-21 10:25:12.000000000 +1100
X--- new/en_US.ISO8859-1/articles/dialup-firewall/article.sgml 2010-01-21 10:37:14.000000000 +1100
X***************
X*** 269,304 ****
X tun1, tun2 and so
X on.
X
X! You should also note that &man.pppd.8; uses the
X! ppp0 interface instead, so if you
X! start the connection with &man.pppd.8; you must substitute
X! tun0 for
X! ppp0. A quick way to edit the
X! firewall rules to reflect this change is shown below. The
X! original rule set is backed up as
X! fwrules_tun0.
X!
X! &prompt.user; cd /etc/firewall
X! /etc/firewall&prompt.user; su
X! Password:
X! /etc/firewall&prompt.root; mv fwrules fwrules_tun0
X! /etc/firewall&prompt.root; cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules
X!
X!
X! To know whether you are currently using &man.ppp.8; or
X! &man.pppd.8; you can examine the output of
X! &man.ifconfig.8; once the connection is up. E.g., for a
X! connection made with &man.pppd.8; you would see something
X! like this (showing only the relevant lines):
X!
X! &prompt.user; ifconfig
X! (skipped...)
X! ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1524
X! inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx netmask 0xff000000
X! (skipped...)
X!
X!
X! On the other hand, for a connection made with
X &man.ppp.8; (user-ppp) you should see
X something similar to this:
X
X--- 269,275 ----
X tun1, tun2 and so
X on.
X
X! For a connection made with
X &man.ppp.8; (user-ppp) you should see
X something similar to this:
X
2523653e9c26f6a06853ddd875789c39
echo x - book.sgml.diff
sed 's/^X//' >book.sgml.diff << 'c0b1393dc42e3eff0b4aab955f5d387c'
X*** orig/en_US.ISO8859-1/books/faq/book.sgml 2010-01-21 10:25:12.000000000 +1100
X--- new/en_US.ISO8859-1/books/faq/book.sgml 2010-01-21 10:48:32.000000000 +1100
X***************
X*** 7687,7715 ****
X
X
X
X!
X! Does &os; support SLIP and PPP?
X
X
X
X! Yes. See the manual pages for &man.slattach.8;,
X! &man.sliplogin.8;, &man.ppp.8;, and &man.pppd.8;.
X! &man.ppp.8; and &man.pppd.8; provide support for both
X! incoming and outgoing connections, while &man.sliplogin.8;
X! deals exclusively with incoming connections, and
X! &man.slattach.8; deals exclusively with outgoing
X! connections.
X
X For more information on how to use these, please see the
X Handbook chapter on PPP and SLIP.
X
X-
X- If you only have access to the Internet through a
X- shell account, you may want to have a look at
X- the net/slirp package.
X- It can provide you with (limited) access to services such as
X- ftp and http direct from your local machine.
X
X
X
X--- 7687,7705 ----
X
X
X
X!
X! Does &os; support PPP?
X
X
X
X! Yes. See the manual pages for &man.ppp.8;.
X! &man.ppp.8; provides support for both
X! incoming and outgoing connections.
X
X For more information on how to use these, please see the
X Handbook chapter on PPP.
X
X
X
X
X***************
X*** 8956,8963 ****
X This normally happens on server machines with slow disks
X that are spawning a &man.getty.8; on the port, and executing
X &man.ppp.8; from a login script or program after login.
X! There were reports of it happening consistently when using
X! slirp. The reason is that in the time taken between
X &man.getty.8; exiting and &man.ppp.8; starting, the
X client-side &man.ppp.8; starts sending Line Control Protocol
X (LCP) packets. Because ECHO is still switched on for the
X--- 8946,8952 ----
X This normally happens on server machines with slow disks
X that are spawning a &man.getty.8; on the port, and executing
X &man.ppp.8; from a login script or program after login.
X! The reason is that in the time taken between
X &man.getty.8; exiting and &man.ppp.8; starting, the
X client-side &man.ppp.8; starts sending Line Control Protocol
X (LCP) packets. Because ECHO is still switched on for the
X***************
X*** 9719,9725 ****
X Serial Communications
X
X This section answers common questions about serial
X! communications with &os;. PPP and SLIP are covered in the Networking section.
X
X
X--- 9708,9714 ----
X Serial Communications
X
X This section answers common questions about serial
X! communications with &os;. PPP is covered in the Networking section.
X
X
c0b1393dc42e3eff0b4aab955f5d387c
echo x - chapter.sgml.diff
sed 's/^X//' >chapter.sgml.diff << 'caa8c35a33a0bbab5ed23ad5917fd940'
X*** orig/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml 2010-01-21 10:25:12.000000000 +1100
X--- new/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml 2010-01-21 10:35:57.000000000 +1100
X***************
X*** 4,10 ****
X $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.192 2009/02/01 09:38:25 manolis Exp $
X -->
X
X!
X
X
X
X--- 4,10 ----
X $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.192 2009/02/01 09:38:25 manolis Exp $
X -->
X
X!
X
X
X
X***************
X*** 16,36 ****
X
X
X
X! PPP and SLIP
X
X!
X Synopsis
X
X PPP
X
X-
X- SLIP
X-
X
X FreeBSD has a number of ways to link one computer to
X another. To establish a network or Internet connection through a
X dial-up modem, or to allow others to do so through you, requires
X! the use of PPP or SLIP. This chapter describes setting up
X these modem-based communication services in detail.
X
X After reading this chapter, you will know:
X--- 16,33 ----
X
X
X
X! PPP
X
X!
X Synopsis
X
X PPP
X
X
X FreeBSD has a number of ways to link one computer to
X another. To establish a network or Internet connection through a
X dial-up modem, or to allow others to do so through you, requires
X! the use of PPP. This chapter describes setting up
X these modem-based communication services in detail.
X
X After reading this chapter, you will know:
X***************
X*** 40,48 ****
X How to set up user PPP.
X
X
X- How to set up kernel PPP.
X-
X-
X How to set up PPPoE (PPP over
X Ethernet).
X
X--- 37,42 ----
X***************
X*** 50,69 ****
X How to set up PPPoA (PPP over
X ATM).
X
X-
X- How to configure and set up a SLIP client and
X- server.
X-
X
X
X
X PPP
X user PPP
X
X-
X- PPP
X- kernel PPP
X-
X
X PPP
X over Ethernet
X--- 44,55 ----
X***************
X*** 77,83 ****
X
X
X Understand the basics and purpose of a dialup connection
X! and PPP and/or SLIP.
X
X
X
X--- 63,69 ----
X
X
X Understand the basics and purpose of a dialup connection
X! and PPP.
X
X
X
X***************
X*** 87,100 ****
X This is expensive in terms of copying the data between the kernel
X and userland, but allows a far more feature-rich PPP implementation.
X User PPP uses the tun device to communicate
X! with the outside world whereas kernel PPP uses the
X! ppp device.
X
X
X Throughout in this chapter, user PPP will simply be
X referred to as ppp unless a distinction
X! needs to be made between it and any other PPP software such as
X! pppd. Unless otherwise stated, all of
X the commands explained in this chapter should be executed as
X root.
X
X--- 73,85 ----
X This is expensive in terms of copying the data between the kernel
X and userland, but allows a far more feature-rich PPP implementation.
X User PPP uses the tun device to communicate
X! with the outside world.
X
X
X Throughout in this chapter, user PPP will simply be
X referred to as ppp unless a distinction
X! needs to be made between it and any other PPP software.
X! Unless otherwise stated, all of
X the commands explained in this chapter should be executed as
X root.
X
X***************
X*** 255,262 ****
X configuration
X
X
X! Both ppp and pppd
X! (the kernel level implementation of PPP) use the configuration
X files located in the /etc/ppp directory.
X Examples for user ppp can be found in
X /usr/share/examples/ppp/.
X--- 240,246 ----
X configuration
X
X
X! ppp uses the configuration
X files located in the /etc/ppp directory.
X Examples for user ppp can be found in
X /usr/share/examples/ppp/.
X***************
X*** 1305,1797 ****
X
X
X
X-
X-
X-
X-
X- Gennady B.
X- Sorokopud
X- Parts originally contributed by
X-
X-
X- Robert
X- Huff
X-
X-
X-
X-
X- Using Kernel PPP
X-
X-
X- Setting Up Kernel PPP
X-
X-
X- PPP
X- kernel PPP
X-
X-
X- Before you start setting up PPP on your machine, make sure
X- that pppd is located in
X- /usr/sbin and the directory
X- /etc/ppp exists.
X-
X- pppd can work in two modes:
X-
X-
X-
X- As a client — you want to connect your
X- machine to the outside world via a PPP serial connection or
X- modem line.
X-
X-
X-
X- PPP
X- server
X-
X-
X-
X- As a server — your machine is located on
X- the network, and is used to connect other computers using
X- PPP.
X-
X-
X-
X- In both cases you will need to set up an options file
X- (/etc/ppp/options or
X- ~/.ppprc if you have more than one user on
X- your machine that uses PPP).
X-
X- You will also need some modem/serial software (preferably
X- comms/kermit), so you can dial and
X- establish a connection with the remote host.
X-
X-
X-
X-
X-
X-
X- Trev
X- Roydhouse
X- Based on information provided by
X-
X-
X-
X-
X-
X- Using <command>pppd</command> as a Client
X-
X-
X- PPP
X- client
X-
X-
X-
X- Cisco
X-
X-
X- The following /etc/ppp/options might be
X- used to connect to a Cisco terminal server PPP line.
X-
X- crtscts # enable hardware flow control
X- modem # modem control line
X- noipdefault # remote PPP server must supply your IP address
X- # if the remote host does not send your IP during IPCP
X- # negotiation, remove this option
X- passive # wait for LCP packets
X- domain ppp.foo.com # put your domain name here
X-
X- :remote_ip # put the IP of remote PPP host here
X- # it will be used to route packets via PPP link
X- # if you didn't specified the noipdefault option
X- # change this line to local_ip:remote_ip
X-
X- defaultroute # put this if you want that PPP server will be your
X- # default router
X-
X- To connect:
X-
X- Kermit
X- modem
X-
X-
X- Dial to the remote host using
X- Kermit (or some other modem
X- program), and enter your user name and password (or whatever
X- is needed to enable PPP on the remote host).
X-
X-
X-
X- Exit Kermit (without
X- hanging up the line).
X-
X-
X-
X- Enter the following:
X-
X- &prompt.root; /usr/sbin/pppd /dev/tty0119200
X-
X- Be sure to use the appropriate speed and device name.
X-
X-
X-
X- Now your computer is connected with PPP. If the connection
X- fails, you can add the option to the
X- /etc/ppp/options file, and check console messages
X- to track the problem.
X-
X- Following /etc/ppp/pppup script will make
X- all 3 stages automatic:
X-
X- #!/bin/sh
X- pgrep -l pppd
X- pid=`pgrep pppd`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing pppd, PID=' ${pid}
X- kill ${pid}
X- fi
X- pgrep -l kermit
X- pid=`pgrep kermit`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing kermit, PID=' ${pid}
X- kill -9 ${pid}
X- fi
X-
X- ifconfig ppp0 down
X- ifconfig ppp0 delete
X-
X- kermit -y /etc/ppp/kermit.dial
X- pppd /dev/tty01 19200
X-
X-
X- Kermit
X-
X-
X- /etc/ppp/kermit.dial is a
X- Kermit script that dials and makes all
X- necessary authorization on the remote host (an example of such a
X- script is attached to the end of this document).
X-
X- Use the following /etc/ppp/pppdown script
X- to disconnect the PPP line:
X-
X- #!/bin/sh
X- pid=`pgrep pppd`
X- if [ X${pid} != "X" ] ; then
X- echo 'killing pppd, PID=' ${pid}
X- kill -TERM ${pid}
X- fi
X-
X- pgrep -l kermit
X- pid=`pgrep kermit`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing kermit, PID=' ${pid}
X- kill -9 ${pid}
X- fi
X-
X- /sbin/ifconfig ppp0 down
X- /sbin/ifconfig ppp0 delete
X- kermit -y /etc/ppp/kermit.hup
X- /etc/ppp/ppptest
X-
X- Check to see if pppd is still running by
X- executing /usr/etc/ppp/ppptest, which should look
X- like this:
X-
X- #!/bin/sh
X- pid=`pgrep pppd`
X- if [ X${pid} != "X" ] ; then
X- echo 'pppd running: PID=' ${pid-NONE}
X- else
X- echo 'No pppd running.'
X- fi
X- set -x
X- netstat -n -I ppp0
X- ifconfig ppp0
X-
X- To hang up the modem, execute
X- /etc/ppp/kermit.hup, which should
X- contain:
X-
X- set line /dev/tty01 ; put your modem device here
X- set speed 19200
X- set file type binary
X- set file names literal
X- set win 8
X- set rec pack 1024
X- set send pack 1024
X- set block 3
X- set term bytesize 8
X- set command bytesize 8
X- set flow none
X-
X- pau 1
X- out +++
X- inp 5 OK
X- out ATH0\13
X- echo \13
X- exit
X-
X- Here is an alternate method using chat
X- instead of kermit:
X-
X- The following two files are sufficient to accomplish a
X- pppd connection.
X-
X- /etc/ppp/options:
X-
X- /dev/cuad1 115200
X-
X- crtscts # enable hardware flow control
X- modem # modem control line
X- connect "/usr/bin/chat -f /etc/ppp/login.chat.script"
X- noipdefault # remote PPP serve must supply your IP address
X- # if the remote host doesn't send your IP during
X- # IPCP negotiation, remove this option
X- passive # wait for LCP packets
X- domain your.domain # put your domain name here
X-
X- : # put the IP of remote PPP host here
X- # it will be used to route packets via PPP link
X- # if you didn't specified the noipdefault option
X- # change this line to local_ip:remote_ip
X-
X- defaultroute # put this if you want that PPP server will be
X- # your default router
X-
X- /etc/ppp/login.chat.script:
X-
X-
X- The following should go on a single line.
X-
X-
X- ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDTphone.number
X- CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: login-id
X- TIMEOUT 5 sword: password
X-
X- Once these are installed and modified correctly, all you need
X- to do is run pppd, like so:
X-
X- &prompt.root; pppd
X-
X-
X-
X- Using <command>pppd</command> as a Server
X-
X- /etc/ppp/options should contain something
X- similar to the following:
X-
X- crtscts # Hardware flow control
X- netmask 255.255.255.0 # netmask (not required)
X- 192.114.208.20:192.114.208.165 # IP's of local and remote hosts
X- # local ip must be different from one
X- # you assigned to the Ethernet (or other)
X- # interface on your machine.
X- # remote IP is IP address that will be
X- # assigned to the remote machine
X- domain ppp.foo.com # your domain
X- passive # wait for LCP
X- modem # modem line
X-
X- The following /etc/ppp/pppserv script
X- will tell pppd to behave as a
X- server:
X-
X- #!/bin/sh
X- pgrep -l pppd
X- pid=`pgrep pppd`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing pppd, PID=' ${pid}
X- kill ${pid}
X- fi
X- pgrep -l kermit
X- pid=`pgrep kermit`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing kermit, PID=' ${pid}
X- kill -9 ${pid}
X- fi
X-
X- # reset ppp interface
X- ifconfig ppp0 down
X- ifconfig ppp0 delete
X-
X- # enable autoanswer mode
X- kermit -y /etc/ppp/kermit.ans
X-
X- # run ppp
X- pppd /dev/tty01 19200
X-
X- Use this /etc/ppp/pppservdown script to
X- stop the server:
X-
X- #!/bin/sh
X- pgrep -l pppd
X- pid=`pgrep pppd`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing pppd, PID=' ${pid}
X- kill ${pid}
X- fi
X- pgrep -l kermit
X- pid=`pgrep kermit`
X- if [ "X${pid}" != "X" ] ; then
X- echo 'killing kermit, PID=' ${pid}
X- kill -9 ${pid}
X- fi
X- ifconfig ppp0 down
X- ifconfig ppp0 delete
X-
X- kermit -y /etc/ppp/kermit.noans
X-
X- The following Kermit script
X- (/etc/ppp/kermit.ans) will enable/disable
X- autoanswer mode on your modem. It should look like this:
X-
X- set line /dev/tty01
X- set speed 19200
X- set file type binary
X- set file names literal
X- set win 8
X- set rec pack 1024
X- set send pack 1024
X- set block 3
X- set term bytesize 8
X- set command bytesize 8
X- set flow none
X-
X- pau 1
X- out +++
X- inp 5 OK
X- out ATH0\13
X- inp 5 OK
X- echo \13
X- out ATS0=1\13 ; change this to out ATS0=0\13 if you want to disable
X- ; autoanswer mode
X- inp 5 OK
X- echo \13
X- exit
X-
X- A script named /etc/ppp/kermit.dial is
X- used for dialing and authenticating on the remote host. You will
X- need to customize it for your needs. Put your login and password
X- in this script; you will also need to change the input statement
X- depending on responses from your modem and remote host.
X-
X- ;
X- ; put the com line attached to the modem here:
X- ;
X- set line /dev/tty01
X- ;
X- ; put the modem speed here:
X- ;
X- set speed 19200
X- set file type binary ; full 8 bit file xfer
X- set file names literal
X- set win 8
X- set rec pack 1024
X- set send pack 1024
X- set block 3
X- set term bytesize 8
X- set command bytesize 8
X- set flow none
X- set modem hayes
X- set dial hangup off
X- set carrier auto ; Then SET CARRIER if necessary,
X- set dial display on ; Then SET DIAL if necessary,
X- set input echo on
X- set input timeout proceed
X- set input case ignore
X- def \%x 0 ; login prompt counter
X- goto slhup
X-
X- :slcmd ; put the modem in command mode
X- echo Put the modem in command mode.
X- clear ; Clear unread characters from input buffer
X- pause 1
X- output +++ ; hayes escape sequence
X- input 1 OK\13\10 ; wait for OK
X- if success goto slhup
X- output \13
X- pause 1
X- output at\13
X- input 1 OK\13\10
X- if fail goto slcmd ; if modem doesn't answer OK, try again
X-
X- :slhup ; hang up the phone
X- clear ; Clear unread characters from input buffer
X- pause 1
X- echo Hanging up the phone.
X- output ath0\13 ; hayes command for on hook
X- input 2 OK\13\10
X- if fail goto slcmd ; if no OK answer, put modem in command mode
X-
X- :sldial ; dial the number
X- pause 1
X- echo Dialing.
X- output atdt9,550311\13\10 ; put phone number here
X- assign \%x 0 ; zero the time counter
X-
X- :look
X- clear ; Clear unread characters from input buffer
X- increment \%x ; Count the seconds
X- input 1 {CONNECT }
X- if success goto sllogin
X- reinput 1 {NO CARRIER\13\10}
X- if success goto sldial
X- reinput 1 {NO DIALTONE\13\10}
X- if success goto slnodial
X- reinput 1 {\255}
X- if success goto slhup
X- reinput 1 {\127}
X- if success goto slhup
X- if < \%x 60 goto look
X- else goto slhup
X-
X- :sllogin ; login
X- assign \%x 0 ; zero the time counter
X- pause 1
X- echo Looking for login prompt.
X-
X- :slloop
X- increment \%x ; Count the seconds
X- clear ; Clear unread characters from input buffer
X- output \13
X- ;
X- ; put your expected login prompt here:
X- ;
X- input 1 {Username: }
X- if success goto sluid
X- reinput 1 {\255}
X- if success goto slhup
X- reinput 1 {\127}
X- if success goto slhup
X- if < \%x 10 goto slloop ; try 10 times to get a login prompt
X- else goto slhup ; hang up and start again if 10 failures
X-
X- :sluid
X- ;
X- ; put your userid here:
X- ;
X- output ppp-login\13
X- input 1 {Password: }
X- ;
X- ; put your password here:
X- ;
X- output ppp-password\13
X- input 1 {Entering SLIP mode.}
X- echo
X- quit
X-
X- :slnodial
X- echo \7No dialtone. Check the telephone line!\7
X- exit 1
X-
X- ; local variables:
X- ; mode: csh
X- ; comment-start: "; "
X- ; comment-start-skip: "; "
X- ; end:
X-
X-
X-
X
X
X
X--- 1289,1294 ----
X***************
X*** 2480,3202 ****
X
X
X
X-
X-
X-
X-
X- Satoshi
X- Asami
X- Originally contributed by
X-
X-
X-
X-
X- Guy
X- Helmer
X- With input from
X-
X-
X- Piero
X- Serini
X-
X-
X-
X-
X- Using SLIP
X- SLIP
X-
X-
X- Setting Up a SLIP Client
X-
X-
X- SLIP
X- client
X-
X-
X- The following is one way to set up a FreeBSD machine for SLIP
X- on a static host network. For dynamic hostname assignments (your
X- address changes each time you dial up), you probably need to
X- have a more complex setup.
X-
X- First, determine which serial port your modem is connected to.
X- Many people set up a symbolic link, such as
X- /dev/modem, to point to the real device name,
X- /dev/cuadN.
X- This allows you to abstract the actual device
X- name should you ever need to move the modem to a different port. It
X- can become quite cumbersome when you need to fix a bunch of files in
X- /etc and .kermrc files all
X- over the system!
X-
X-
X- /dev/cuad0
X- is
X- COM1, /dev/cuad1
X- is
X- COM2, etc.
X-
X-
X- Make sure you have the following in your kernel configuration
X- file:
X-
X- device sl
X-
X- It is included in the GENERIC kernel, so
X- this should not be a problem unless you have deleted it.
X-
X-
X- Things You Have to Do Only Once
X-
X-
X-
X- Add your home machine, the gateway and nameservers to
X- your /etc/hosts file. Ours looks like
X- this:
X-
X- 127.0.0.1 localhost loghost
X- 136.152.64.181 water.CS.Example.EDU water.CS water
X- 136.152.64.1 inr-3.CS.Example.EDU inr-3 slip-gateway
X- 128.32.136.9 ns1.Example.EDU ns1
X- 128.32.136.12 ns2.Example.EDU ns2
X-
X-
X-
X- Make sure you have files before
X- dns in the hosts:
X- section of your /etc/nsswitch.conf
X- file. Without these parameters funny things may
X- happen.
X-
X-
X-
X- Edit the /etc/rc.conf file.
X-
X-
X-
X- Set your hostname by editing the line that
X- says:
X-
X- hostname="myname.my.domain"
X-
X- Your machine's full Internet hostname should be
X- placed here.
X-
X-
X- default route
X-
X- Designate the default router by changing the
X- line:
X-
X- defaultrouter="NO"
X-
X- to:
X-
X- defaultrouter="slip-gateway"
X-
X-
X-
X-
X-
X- Make a file /etc/resolv.conf which
X- contains:
X-
X- domain CS.Example.EDU
X- nameserver 128.32.136.9
X- nameserver 128.32.136.12
X-
X- nameserver
X- domain name
X- As you can see, these set up the nameserver hosts. Of
X- course, the actual domain names and addresses depend on your
X- environment.
X-
X-
X-
X- Set the password for root and
X- toor (and any other
X- accounts that do not have a password).
X-
X-
X-
X- Reboot your machine and make sure it comes up with the
X- correct hostname.
X-
X-
X-
X-
X-
X- Making a SLIP Connection
X-
X-
X- SLIP
X- connecting with
X-
X-
X-
X-
X- Dial up, type slip at the prompt,
X- enter your machine name and password. What is required to
X- be entered depends on your environment. If you use
X- Kermit, you can try a script like
X- this:
X-
X- # kermit setup
X- set modem hayes
X- set line /dev/modem
X- set speed 115200
X- set parity none
X- set flow rts/cts
X- set terminal bytesize 8
X- set file type binary
X- # The next macro will dial up and login
X- define slip dial 643-9600, input 10 =>, if failure stop, -
X- output slip\x0d, input 10 Username:, if failure stop, -
X- output silvia\x0d, input 10 Password:, if failure stop, -
X- output ***\x0d, echo \x0aCONNECTED\x0a
X-
X- Of course, you have to change the username and password
X- to fit yours. After doing so, you can just type
X- slip from the
X- Kermit prompt to connect.
X-
X-
X- Leaving your password in plain text anywhere in the
X- filesystem is generally a bad idea.
X- Do it at your own risk.
X-
X-
X-
X-
X- Leave the Kermit there (you can
X- suspend it by
X-
X- Ctrl
X- z
X- ) and as root, type:
X-
X- &prompt.root; slattach -h -c -s 115200 /dev/modem
X-
X- If you are able to ping hosts on the
X- other side of the router, you are connected! If it does not
X- work, you might want to try instead of
X- as an argument to
X- slattach.
X-
X-
X-
X-
X-
X- How to Shutdown the Connection
X-
X- Do the following:
X-
X- &prompt.root; kill -INT `cat /var/run/slattach.modem.pid`
X-
X- to kill slattach. Keep in mind you must be
X- root to do the above. Then go back to
X- kermit (by running fg if you
X- suspended it) and exit from it (q).
X-
X- The &man.slattach.8; manual page says you have
X- to use ifconfig sl0 down
X- to mark the interface down, but this does not
X- seem to make any difference.
X- (ifconfig sl0 reports the same thing.)
X-
X- Some times, your modem might refuse to drop the carrier.
X- In that case, simply start kermit and quit
X- it again. It usually goes out on the second try.
X-
X-
X-
X- Troubleshooting
X-
X- If it does not work, feel free to ask on &a.net.name; mailing
X- list. The things that people tripped over so far:
X-
X-
X-
X- Not using or in
X- slattach (This should not be fatal,
X- but some users have reported that this solves their
X- problems.)
X-
X-
X-
X- Using instead of
X- (might be hard to see the difference on
X- some fonts).
X-
X-
X-
X- Try ifconfig sl0 to see your
X- interface status. For example, you might get:
X-
X- &prompt.root; ifconfig sl0
X- sl0: flags=10<POINTOPOINT>
X- inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00
X-
X-
X-
X- If you get no route to host
X- messages from &man.ping.8;, there may be a problem with your
X- routing table. You can use the netstat -r
X- command to display the current routes :
X-
X- &prompt.root; netstat -r
X- Routing tables
X- Destination Gateway Flags Refs Use IfaceMTU Rtt Netmasks:
X-
X- (root node)
X- (root node)
X-
X- Route Tree for Protocol Family inet:
X- (root node) =>
X- default inr-3.Example.EDU UG 8 224515 sl0 - -
X- localhost.Exampl localhost.Example. UH 5 42127 lo0 - 0.438
X- inr-3.Example.ED water.CS.Example.E UH 1 0 sl0 - -
X- water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
X- (root node)
X-
X- The preceding examples are from a relatively busy system.
X- The numbers on your system will vary depending on
X- network activity.
X-
X-
X-
X-
X-
X-
X-
X- Setting Up a SLIP Server
X-
X-
X- SLIP
X- server
X-
X-
X- This document provides suggestions for setting up SLIP Server
X- services on a FreeBSD system, which typically means configuring
X- your system to automatically start up connections upon login for
X- remote SLIP clients.
X-
X-
X-
X-
X- Prerequisites
X- TCP/IP networking
X- This section is very technical in nature, so background
X- knowledge is required. It is assumed that you are familiar with
X- the TCP/IP network protocol, and in particular, network and node
X- addressing, network address masks, subnetting, routing, and
X- routing protocols, such as RIP. Configuring SLIP services on a
X- dial-up server requires a knowledge of these concepts, and if
X- you are not familiar with them, please read a copy of either
X- Craig Hunt's TCP/IP Network Administration
X- published by O'Reilly & Associates, Inc. (ISBN Number
X- 0-937175-82-X), or Douglas Comer's books on the TCP/IP
X- protocol.
X-
X- modem
X- It is further assumed that you have already set up your
X- modem(s) and configured the appropriate system files to allow
X- logins through your modems. If you have not prepared your
X- system for this yet, please see for details on dialup services
X- configuration.
X- You may also want to check the manual pages for &man.sio.4; for
X- information on the serial port device driver and &man.ttys.5;,
X- &man.gettytab.5;, &man.getty.8;, & &man.init.8; for
X- information relevant to configuring the system to accept logins
X- on modems, and perhaps &man.stty.1; for information on setting
X- serial port parameters (such as clocal for
X- directly-connected serial interfaces).
X-
X-
X-
X- Quick Overview
X-
X- In its typical configuration, using FreeBSD as a SLIP server
X- works as follows: a SLIP user dials up your FreeBSD SLIP Server
X- system and logs in with a special SLIP login ID that uses
X- /usr/sbin/sliplogin as the special user's
X- shell. The sliplogin program browses the
X- file /etc/sliphome/slip.hosts to find a
X- matching line for the special user, and if it finds a match,
X- connects the serial line to an available SLIP interface and then
X- runs the shell script
X- /etc/sliphome/slip.login to configure the
X- SLIP interface.
X-
X-
X- An Example of a SLIP Server Login
X-
X- For example, if a SLIP user ID were
X- Shelmerg, Shelmerg's
X- entry in /etc/master.passwd would look
X- something like this:
X-
X- Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin
X-
X- When Shelmerg logs in,
X- sliplogin will search
X- /etc/sliphome/slip.hosts for a line that
X- had a matching user ID; for example, there may be a line in
X- /etc/sliphome/slip.hosts that
X- reads:
X-
X- Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp
X-
X- sliplogin will find that matching line,
X- hook the serial line into the next available SLIP interface,
X- and then execute /etc/sliphome/slip.login
X- like this:
X-
X- /etc/sliphome/slip.login 0 19200 Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp
X-
X- If all goes well,
X- /etc/sliphome/slip.login will issue an
X- ifconfig for the SLIP interface to which
X- sliplogin attached itself (SLIP interface
X- 0, in the above example, which was the first parameter in the
X- list given to slip.login) to set the
X- local IP address (dc-slip), remote IP address
X- (sl-helmer), network mask for the SLIP
X- interface (0xfffffc00), and
X- any additional flags (autocomp). If
X- something goes wrong, sliplogin usually
X- logs good informational messages via the
X- syslogd daemon facility, which usually
X- logs to /var/log/messages (see the manual
X- pages for &man.syslogd.8; and &man.syslog.conf.5; and perhaps
X- check /etc/syslog.conf to see to what
X- syslogd is logging and where it is
X- logging to).
X-
X-
X-
X-
X- Kernel Configuration
X-
X-
X- kernel
X- configuration
X-
X-
X-
X- SLIP
X-
X-
X- &os;'s default kernel (GENERIC)
X- comes with SLIP (&man.sl.4;) support; in case of a custom
X- kernel, you have to add the following line to your kernel
X- configuration file:
X-
X- device sl
X-
X- By default, your &os; machine will not forward packets.
X- If you want your FreeBSD SLIP Server to act as a router, you
X- will have to edit the /etc/rc.conf file and
X- change the setting of the gateway_enable variable
X- to . This will make sure that setting the
X- routing option will be persistent after a reboot.
X-
X- To apply the settings immediately you can execute the
X- following command as root:
X-
X- &prompt.root; /etc/rc.d/routing start
X-
X- Please refer to on
X- Configuring the FreeBSD Kernel for help in
X- reconfiguring your kernel.
X-
X-
X-
X- Sliplogin Configuration
X-
X- As mentioned earlier, there are three files in the
X- /etc/sliphome directory that are part of
X- the configuration for /usr/sbin/sliplogin
X- (see &man.sliplogin.8; for the actual manual page for
X- sliplogin): slip.hosts,
X- which defines the SLIP users and their associated IP
X- addresses; slip.login, which usually just
X- configures the SLIP interface; and (optionally)
X- slip.logout, which undoes
X- slip.login's effects when the serial
X- connection is terminated.
X-
X-
X- <filename>slip.hosts</filename> Configuration
X-
X- /etc/sliphome/slip.hosts contains
X- lines which have at least four items separated by
X- whitespace:
X-
X-
X-
X- SLIP user's login ID
X-
X-
X-
X- Local address (local to the SLIP server) of the SLIP
X- link
X-
X-
X-
X- Remote address of the SLIP link
X-
X-
X-
X- Network mask
X-
X-
X-
X- The local and remote addresses may be host names
X- (resolved to IP addresses by
X- /etc/hosts or by the domain name
X- service, depending on your specifications in the file
X- /etc/nsswitch.conf), and the network mask
X- may be a name that can be resolved by a lookup into
X- /etc/networks. On a sample system,
X- /etc/sliphome/slip.hosts looks like
X- this:
X-
X- #
X- # login local-addr remote-addr mask opt1 opt2
X- # (normal,compress,noicmp)
X- #
X- Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp
X-
X- At the end of the line is one or more of the
X- options:
X-
X-
X-
X- — no header
X- compression
X-
X-
X-
X- — compress
X- headers
X-
X-
X-
X- — compress headers if
X- the remote end allows it
X-
X-
X-
X- — disable ICMP packets
X- (so any ping packets will be dropped instead
X- of using up your bandwidth)
X-
X-
X-
X- SLIP
X- TCP/IP networking
X- Your choice of local and remote addresses for your SLIP
X- links depends on whether you are going to dedicate a TCP/IP
X- subnet or if you are going to use proxy ARP on
X- your SLIP server (it is not true proxy ARP, but
X- that is the terminology used in this section to describe it).
X- If you are not sure which method to select or how to assign IP
X- addresses, please refer to the TCP/IP books referenced in
X- the SLIP Prerequisites ()
X- and/or consult your IP network manager.
X-
X- If you are going to use a separate subnet for your SLIP
X- clients, you will need to allocate the subnet number out of
X- your assigned IP network number and assign each of your SLIP
X- client's IP numbers out of that subnet. Then, you will
X- probably need to configure a static route to the SLIP
X- subnet via your SLIP server on your nearest IP router.
X-
X- Ethernet
X- Otherwise, if you will use the proxy ARP
X- method, you will need to assign your SLIP client's IP
X- addresses out of your SLIP server's Ethernet subnet, and you
X- will also need to adjust your
X- /etc/sliphome/slip.login and
X- /etc/sliphome/slip.logout scripts to use
X- &man.arp.8; to manage the proxy ARP entries in the SLIP
X- server's ARP table.
X-
X-
X-
X- <filename>slip.login</filename> Configuration
X-
X- The typical /etc/sliphome/slip.login
X- file looks like this:
X-
X- #!/bin/sh -
X- #
X- # @(#)slip.login 5.1 (Berkeley) 7/1/90
X-
X- #
X- # generic login file for a slip line. sliplogin invokes this with
X- # the parameters:
X- # 1 2 3 4 5 6 7-n
X- # slipunit ttyspeed loginname local-addr remote-addr mask opt-args
X- #
X- /sbin/ifconfig sl$1 inet $4 $5 netmask $6
X-
X- This slip.login file merely runs
X- ifconfig for the appropriate SLIP interface
X- with the local and remote addresses and network mask of the
X- SLIP interface.
X-
X- If you have decided to use the proxy ARP
X- method (instead of using a separate subnet for your SLIP
X- clients), your /etc/sliphome/slip.login
X- file will need to look something like this:
X-
X- #!/bin/sh -
X- #
X- # @(#)slip.login 5.1 (Berkeley) 7/1/90
X-
X- #
X- # generic login file for a slip line. sliplogin invokes this with
X- # the parameters:
X- # 1 2 3 4 5 6 7-n
X- # slipunit ttyspeed loginname local-addr remote-addr mask opt-args
X- #
X- /sbin/ifconfig sl$1 inet $4 $5 netmask $6
X- # Answer ARP requests for the SLIP client with our Ethernet addr
X- /usr/sbin/arp -s $5 00:11:22:33:44:55 pub
X-
X- The additional line in this
X- slip.login, arp -s
X- $5 00:11:22:33:44:55 pub, creates an ARP entry
X- in the SLIP server's ARP table. This ARP entry causes the
X- SLIP server to respond with the SLIP server's Ethernet MAC
X- address whenever another IP node on the Ethernet asks to
X- speak to the SLIP client's IP address.
X-
X-
X- Ethernet
X- MAC address
X-
X-
X- When using the example above, be sure to replace the
X- Ethernet MAC address (00:11:22:33:44:55) with the MAC address of
X- your system's Ethernet card, or your proxy ARP
X- will definitely not work! You can discover your SLIP server's
X- Ethernet MAC address by looking at the results of running
X- netstat -i; the second line of the output
X- should look something like:
X-
X- ed0 1500 <Link>0.2.c1.28.5f.4a 191923 0 129457 0 116
X-
X- This indicates that this particular system's Ethernet MAC
X- address is 00:02:c1:28:5f:4a
X- — the periods in the Ethernet MAC address given by
X- netstat -i must be changed to colons and
X- leading zeros should be added to each single-digit hexadecimal
X- number to convert the address into the form that &man.arp.8;
X- desires; see the manual page on &man.arp.8; for complete
X- information on usage.
X-
X-
X- When you create
X- /etc/sliphome/slip.login and
X- /etc/sliphome/slip.logout, the
X- execute bit (i.e., chmod 755
X- /etc/sliphome/slip.login /etc/sliphome/slip.logout)
X- must be set, or sliplogin will be unable
X- to execute it.
X-
X-
X-
X-
X- <filename>slip.logout</filename> Configuration
X-
X- /etc/sliphome/slip.logout is not
X- strictly needed (unless you are implementing proxy
X- ARP), but if you decide to create it, this is an
X- example of a basic
X- slip.logout script:
X-
X- #!/bin/sh -
X- #
X- # slip.logout
X-
X- #
X- # logout file for a slip line. sliplogin invokes this with
X- # the parameters:
X- # 1 2 3 4 5 6 7-n
X- # slipunit ttyspeed loginname local-addr remote-addr mask opt-args
X- #
X- /sbin/ifconfig sl$1 down
X-
X- If you are using proxy ARP, you will want to
X- have /etc/sliphome/slip.logout remove the
X- ARP entry for the SLIP client:
X-
X- #!/bin/sh -
X- #
X- # @(#)slip.logout
X-
X- #
X- # logout file for a slip line. sliplogin invokes this with
X- # the parameters:
X- # 1 2 3 4 5 6 7-n
X- # slipunit ttyspeed loginname local-addr remote-addr mask opt-args
X- #
X- /sbin/ifconfig sl$1 down
X- # Quit answering ARP requests for the SLIP client
X- /usr/sbin/arp -d $5
X-
X- The arp -d $5 removes the ARP entry
X- that the proxy ARP
X- slip.login added when the SLIP client
X- logged in.
X-
X- It bears repeating: make sure
X- /etc/sliphome/slip.logout has the execute
X- bit set after you create it (i.e., chmod 755
X- /etc/sliphome/slip.logout).
X-
X-
X-
X-
X- Routing Considerations
X-
X- SLIP
X- routing
X-
X- If you are not using the proxy ARP method for
X- routing packets between your SLIP clients and the rest of your
X- network (and perhaps the Internet), you will probably
X- have to add static routes to your closest default router(s) to
X- route your SLIP clients subnet via your SLIP server.
X-
X-
X- Static Routes
X- static routes
X-
X- Adding static routes to your nearest default routers
X- can be troublesome (or impossible if you do not have
X- authority to do so...). If you have a multiple-router
X- network in your organization, some routers, such as those
X- made by Cisco and Proteon, may not only need to be
X- configured with the static route to the SLIP subnet, but
X- also need to be told which static routes to tell other
X- routers about, so some expertise and
X- troubleshooting/tweaking may be necessary to get
X- static-route-based routing to work.
X-
X-
X-
X-
X
X
X