From brueffer at FreeBSD.org Sat Nov 1 03:58:30 2008 From: brueffer at FreeBSD.org (brueffer@FreeBSD.org) Date: Sat Nov 1 03:58:37 2008 Subject: docs/128089: [patch] Incorrect type in archive_write(3) manpage Message-ID: <200811011058.mA1AwUSv077639@freefall.freebsd.org> Synopsis: [patch] Incorrect type in archive_write(3) manpage Responsible-Changed-From-To: freebsd-doc->kientzle Responsible-Changed-By: brueffer Responsible-Changed-When: Sat Nov 1 11:58:03 CET 2008 Responsible-Changed-Why: Tim, could you take a look at this? http://www.freebsd.org/cgi/query-pr.cgi?pr=128089 From brueffer at FreeBSD.org Sat Nov 1 07:50:58 2008 From: brueffer at FreeBSD.org (Christian Brueffer) Date: Sat Nov 1 07:51:04 2008 Subject: zd1211 chip wlan / new supported hardware report In-Reply-To: <20081030203735.46470d45@dell> References: <20081030203735.46470d45@dell> Message-ID: <20081101142054.GA1236@haakonia.hitnet.RWTH-Aachen.DE> On Thu, Oct 30, 2008 at 08:37:35PM +0100, Horvath Andras wrote: > Hi There! > > I recently have bought a new USB Wlan device and i'd like to report > that i tested it and it works perfectly on the following platform: > > FreeBSD 7.0-RELEASE (stable/amd64) - Perfect with 'if_zyd.ko' kernel > modul > > Type = MyTek MWU-201 Wlan USB adapter > > lsusb: > Bus 007 Device 003: ID 0ace:1215 ZyDAS WLA-54L WiFi > > > I'm not entirely sure which mailing list i should send it to. Hope I > chose the right one ;) I would like to contribute with hardware testing. > I've added the adapter to the manpage. Thanks for letting us know! - Christian -- Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081101/d28d4dbb/attachment.pgp From preston.sumner at gmail.com Sun Nov 2 00:10:18 2008 From: preston.sumner at gmail.com (Preston Sumner) Date: Sun Nov 2 00:10:25 2008 Subject: VESA kernel option unavailable on AMD64 Message-ID: <4817D67D-CB41-419B-8382-C2F2C7F597AE@gmail.com> http://www.freebsd.org/doc/en/books/handbook/consoles.html It may be helpful to mention on that page that the VESA kernel option for console video mode is unavailable on the AMD64 platform. I just found this out the hard way! :) Preston From eitanadlerlist at gmail.com Sun Nov 2 09:29:32 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sun Nov 2 09:29:39 2008 Subject: What is perl? Message-ID: <490DE377.4040005@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At the moment man perl man perlfaq1 man perlintro lang/perl5/pkg-descr Each give a different answer to the question "what is perl?". I think the documentation should be consistent. Can we come up with "one definition to rule them all"? - -- GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkN43cACgkQtl8kq+nCzNFTUwCfej7Nxyk5SGXs0GQHjKT+++kP gtoAnjlptMTo6EcpjKbIF9yKw0yTVKff =bodO -----END PGP SIGNATURE----- From EitanAdlerList at gmail.com Sun Nov 2 10:10:02 2008 From: EitanAdlerList at gmail.com (Eitan Adler) Date: Sun Nov 2 10:10:08 2008 Subject: docs/128543: [patch] remove extra line in developers handbook (tools chapter) Message-ID: <200811021805.mA2I51de087609@www.freebsd.org> >Number: 128543 >Category: docs >Synopsis: [patch] remove extra line in developers handbook (tools chapter) >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 Nov 02 18:10:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Eitan Adler >Release: N/A >Organization: >Environment: N/A >Description: This will produce a debug version of the program. on http://www.freebsd.org/doc/en/books/developers-handbook/tools-compiling.html is not needed >How-To-Repeat: >Fix: Patch attached with submission follows: --- oldchapter.sgml 2008-11-02 12:58:57.000000000 -0500 +++ chapter.sgml 2008-11-02 12:59:13.000000000 -0500 @@ -514,9 +514,6 @@ - This will produce a debug version of the - program. - Note, we did not use the flag to specify the executable name, so we will get an >Release-Note: >Audit-Trail: >Unformatted: From eitanadlerlist at gmail.com Sun Nov 2 14:26:24 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sun Nov 2 14:26:31 2008 Subject: change to sgml-primer example Message-ID: <490E2907.5090907@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone comment on the attached patch to be run from /usr/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer - -- GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkOKQcACgkQtl8kq+nCzNF6pACfXl362SlqAL1BtgDgP1KuH2V1 LFgAn2++bPmiZq0mBkPUVluAKhRExlrD =/oXj -----END PGP SIGNATURE----- -------------- next part -------------- --- chapter.sgml 2008-10-31 08:23:35.000000000 -0400 +++ newchapter.sgml 2008-11-02 17:21:54.000000000 -0500 @@ -862,6 +862,7 @@ Erroneous SGML comments + The SGML parser will treat ]]> - The SGML parser will treat this as though it were actually: + as though it were actually: <!THIS IS OUTSIDE THE COMMENT> This is not valid SGML, and may give confusing error messages. + Because "--" delimitates the end of a comment do do not write comments like this: + ]]> - As the example suggests, do not write - comments like that. + This is a (slightly) better approach, but it still potentially confusing to people new to SGML: ]]> - That is a (slightly) better approach, but it still potentially - confusing to people new to SGML. -------------- next part -------------- A non-text attachment was scrubbed... Name: change_sgml_example.udiff.patch.sig Type: application/octet-stream Size: 72 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081102/52f7fa8f/change_sgml_example.udiff.patch.obj From ceri at FreeBSD.org Sun Nov 2 14:42:24 2008 From: ceri at FreeBSD.org (ceri@FreeBSD.org) Date: Sun Nov 2 14:42:30 2008 Subject: docs/63570: [patch] Language cleanup for the Handbook's DNS section Message-ID: <200811022242.mA2MgN7b022996@freefall.freebsd.org> Synopsis: [patch] Language cleanup for the Handbook's DNS section Responsible-Changed-From-To: ceri->freebsd-doc Responsible-Changed-By: ceri Responsible-Changed-When: Sun Nov 2 22:41:42 UTC 2008 Responsible-Changed-Why: I don't really belong in the FreeBSD project anymomre. http://www.freebsd.org/cgi/query-pr.cgi?pr=63570 From ceri at FreeBSD.org Sun Nov 2 14:43:07 2008 From: ceri at FreeBSD.org (ceri@FreeBSD.org) Date: Sun Nov 2 14:43:43 2008 Subject: docs/70583: [patch] Update freebsd-glossary Message-ID: <200811022243.mA2Mh7IK023045@freefall.freebsd.org> Synopsis: [patch] Update freebsd-glossary Responsible-Changed-From-To: ceri->freebsd-doc Responsible-Changed-By: ceri Responsible-Changed-When: Sun Nov 2 22:42:32 UTC 2008 Responsible-Changed-Why: I don't really belong in the FreeBSD project any more, so sorry for sitting on this for so long. http://www.freebsd.org/cgi/query-pr.cgi?pr=70583 From ceri at FreeBSD.org Sun Nov 2 14:44:31 2008 From: ceri at FreeBSD.org (ceri@FreeBSD.org) Date: Sun Nov 2 14:44:37 2008 Subject: docs/91174: [REQUEST] Handbook: Addition of Oracle 9i installation documentation Message-ID: <200811022244.mA2MiURC023171@freefall.freebsd.org> Synopsis: [REQUEST] Handbook: Addition of Oracle 9i installation documentation Responsible-Changed-From-To: ceri->freebsd-doc Responsible-Changed-By: ceri Responsible-Changed-When: Sun Nov 2 22:44:04 UTC 2008 Responsible-Changed-Why: I don't really belong in the FreeBSD project any more, so sorry for sitting on this for so long. I couldn't get 10g working, btw. http://www.freebsd.org/cgi/query-pr.cgi?pr=91174 From marcs at draenor.org Sun Nov 2 21:20:29 2008 From: marcs at draenor.org (Marc Silver) Date: Sun Nov 2 21:20:42 2008 Subject: What is perl? In-Reply-To: <490DE377.4040005@gmail.com> References: <490DE377.4040005@gmail.com> Message-ID: Hi there, I may be wrong, but I always assumed that these man pages were part of the Perl package themselves and as such, not maintained by FreeBSD-doc. That said, since Perl has a reputation for performing any single task in many different ways, it seems quite fitting that there is no one explanation. :) Cheers, Marc On Sun, Nov 2, 2008 at 7:29 PM, Eitan Adler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > At the moment > man perl > man perlfaq1 > man perlintro > lang/perl5/pkg-descr > > Each give a different answer to the question "what is perl?". > I think the documentation should be consistent. > > Can we come up with "one definition to rule them all"? > > - -- > GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkkN43cACgkQtl8kq+nCzNFTUwCfej7Nxyk5SGXs0GQHjKT+++kP > gtoAnjlptMTo6EcpjKbIF9yKw0yTVKff > =bodO > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > -- Our deepest fear is not that we are inadequate. Our deepest fear is that we are powerful beyond measure. It is our light, not our darkness, that most frightens us. From pgj at FreeBSD.org Sun Nov 2 22:22:22 2008 From: pgj at FreeBSD.org (pgj@FreeBSD.org) Date: Sun Nov 2 22:22:31 2008 Subject: docs/128543: [patch] remove extra line in developers handbook (tools chapter) Message-ID: <200811030622.mA36ML3c068733@freefall.freebsd.org> Synopsis: [patch] remove extra line in developers handbook (tools chapter) Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: pgj Responsible-Changed-When: Mon Nov 3 06:14:08 UTC 2008 Responsible-Changed-Why: Snatch http://www.freebsd.org/cgi/query-pr.cgi?pr=128543 From pgj at FreeBSD.org Mon Nov 3 00:14:20 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Nov 3 00:14:26 2008 Subject: change to sgml-primer example In-Reply-To: <490E2907.5090907@gmail.com> References: <490E2907.5090907@gmail.com> Message-ID: <490EADFA.3020708@FreeBSD.org> Eitan Adler wrote: > Can anyone comment on the attached patch to be run from > /usr/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer ------------------------------------------------------------------------ --- chapter.sgml 2008-10-31 08:23:35.000000000 -0400 +++ newchapter.sgml 2008-11-02 17:21:54.000000000 -0500 @@ -862,6 +862,7 @@ Erroneous SGML comments + The SGML parser will treat ]]> - The SGML parser will treat this as though it were actually: + as though it were actually: I would not prefer splitting paragraphs around elements, as I have already fought against this before [1]. <!THIS IS OUTSIDE THE COMMENT> This is not valid SGML, and may give confusing error messages. + Because "--" delimitates the end of a comment do do not write comments like this: + ]]> - As the example suggests, do not write - comments like that. + This is a (slightly) better approach, but it still potentially confusing to people new to SGML: ]]> - That is a (slightly) better approach, but it still potentially - confusing to people new to SGML. In my very humble opinion, I am good with the original text. Cheers, :g [1] http://www.freebsd.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml From bugmaster at FreeBSD.org Mon Nov 3 03:06:07 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 3 03:06:36 2008 Subject: Current unassigned doc problem reports Message-ID: <200811031106.mA3B66gM009937@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/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128325 doc README.snapshots still refers to snaphots as "alpha-te o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128129 doc Sysinstall color problem in xterm o docs/128128 doc Sysinstall not mentioned in 4.4 "Using the Packages Sy o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127923 doc Please mention qemu in the FreeBSD Handbook o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/127406 doc [patch] update umodem man page: Sony Ericsson W810i o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122470 doc [patch] exit status on fetch(1) manual page o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o 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 docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121197 doc [patch] edits to books/porters-handbook 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/120628 doc PAE documentation errror in handbook 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/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) s docs/119404 doc [request] events page should list only last 2 years wo o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu 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/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument 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/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported 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/112481 doc bug in ppp.linkup example 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/111263 doc [request] Information on $EDITOR variable in section 3 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/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout 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 o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n 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/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym 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/98759 doc [patch] sbp_targ(4) man page missing reference to devi 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/95139 doc FAQ to move filesystem to new disk fails: incorrect pe 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/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous 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/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI 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 o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt 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/47818 doc [patch] ln(1) manpage is confusing 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 o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. 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 170 problems total. From skreuzer at exit2shell.com Mon Nov 3 11:00:15 2008 From: skreuzer at exit2shell.com (Steven Kreuzer) Date: Mon Nov 3 11:00:21 2008 Subject: docs/128563: Update to 1.4 in FreeBSD Developers' Handbook Message-ID: <200811031853.mA3IrtHN022626@www.freebsd.org> >Number: 128563 >Category: docs >Synopsis: Update to 1.4 in FreeBSD Developers' Handbook >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Nov 03 19:00:11 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Steven Kreuzer >Release: 6.3-STABLE >Organization: >Environment: FreeBSD slurry.exit2shell.com 6.3-STABLE FreeBSD 6.3-STABLE #1: Fri May 23 20:22:28 EDT 2008 root@biggierat.sddi.net:/usr/obj/usr/src/sys/SMP amd64 >Description: Attached patch will update chapter 1.4 The Layout of /usr/src adding details for two new directories: cddl and compat >How-To-Repeat: >Fix: Patch attached with submission follows: Index: en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml =================================================================== RCS file: /usr/share/cvs/freebsd/doc/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml,v retrieving revision 1.18 diff -u -r1.18 chapter.sgml --- en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml 5 Jan 2006 20:03:34 -0000 1.18 +++ en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml 3 Nov 2008 18:47:50 -0000 @@ -114,6 +114,17 @@ + cddl/ + Utilities covered by the Common Development and Distribution + License. + + + + compat/ + Source files for interoperability. + + + contrib/ Source for files from contributed software. >Release-Note: >Audit-Trail: >Unformatted: From sahil at tandon.net Mon Nov 3 21:25:14 2008 From: sahil at tandon.net (Sahil Tandon) Date: Mon Nov 3 21:25:20 2008 Subject: What is perl? In-Reply-To: References: <490DE377.4040005@gmail.com> Message-ID: <20081104050757.GA20279@shepherd> Marc Silver wrote: > I may be wrong, but I always assumed that these man pages were part of the > Perl package themselves and as such, not maintained by FreeBSD-doc. > > That said, since Perl has a reputation for performing any single task in > many different ways, it seems quite fitting that there is no one > explanation. :) TMTOWTDI indeed! -- Sahil Tandon From pgj at FreeBSD.org Tue Nov 4 09:47:07 2008 From: pgj at FreeBSD.org (pgj@FreeBSD.org) Date: Tue Nov 4 09:47:14 2008 Subject: docs/128563: [patch] Update to section 1.4 (Introduction) in FreeBSD Developers' Handbook Message-ID: <200811041747.mA4Hl7Nk026353@freefall.freebsd.org> Synopsis: [patch] Update to section 1.4 (Introduction) in FreeBSD Developers' Handbook Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: pgj Responsible-Changed-When: Tue Nov 4 17:46:40 UTC 2008 Responsible-Changed-Why: Take http://www.freebsd.org/cgi/query-pr.cgi?pr=128563 From dhenscheid at cox.net Tue Nov 4 09:46:15 2008 From: dhenscheid at cox.net (dhenscheid@cox.net) Date: Tue Nov 4 10:09:40 2008 Subject: Possible missing word in the FreeBSD handbook online. Message-ID: <20081104122949.9EZYZ.192760.imail@fed1rmwml25> To whom it may concern, First off: I have been pouring through the FreeBSD Handbook lately, and I believe there may be a missing word in one of the sections. On this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/tcpwrappers.html one of the sentences in the first paragraph reads: "While a firewall has a wide variety of uses, there are some things that a firewall not handle such as sending text back to the connection originator." The sentence is a little confusing in the main sentence. "... there are some things that a firewall <> handle..." Is this supposed to be "cannot", "should not", "will not", etc? Second off: Thank you very much for providing this handbook. It's been an invaluable tool for me and learning how FreeBSD works. It is well formatted, concise, and very easy to follow. I find the examples easy to understand and can set up FreeBSD on my laptop with minimal problems. Regards, Daniel From sonic2000gr at gmail.com Tue Nov 4 11:27:12 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Nov 4 11:27:18 2008 Subject: Possible missing word in the FreeBSD handbook online. In-Reply-To: <20081104122949.9EZYZ.192760.imail@fed1rmwml25> References: <20081104122949.9EZYZ.192760.imail@fed1rmwml25> Message-ID: <4910A204.2000008@gmail.com> dhenscheid@cox.net wrote: > To whom it may concern, > > First off: > I have been pouring through the FreeBSD Handbook lately, and I believe there may be a missing word in one of the sections. On this page: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/tcpwrappers.html > > one of the sentences in the first paragraph reads: > > "While a firewall has a wide variety of uses, there are some things that a firewall not handle such as sending text back to the connection originator." > > The sentence is a little confusing in the main sentence. "... there are some things that a firewall <> handle..." Is this supposed to be "cannot", "should not", "will not", etc? > > You are right, I just fixed it and it will appear in the online version of the Handbook in the next 24 hours. Thanks for submitting this! > Second off: > Thank you very much for providing this handbook. It's been an invaluable tool for me and learning how FreeBSD works. It is well formatted, concise, and very easy to follow. I find the examples easy to understand and can set up FreeBSD on my laptop with minimal problems. > > Rest assured we enjoy working on the documentation as much as you enjoy reading it! Thanks, manolis@ From blackend at freebsd.org Tue Nov 4 11:52:13 2008 From: blackend at freebsd.org (Marc Fonvieille) Date: Tue Nov 4 11:52:20 2008 Subject: Bad link on FAQ In-Reply-To: <000501c93b4a$3ef3e600$0100000a@arthur> References: <8CAF35BAC880BC2-7D4-8D@FRR4-L30.sis.aol.com> <20081003112509.GA1043@gothic.blackend.org> <000501c93b4a$3ef3e600$0100000a@arthur> Message-ID: <20081104195204.GA7509@abigail.blackend.org> On Fri, Oct 31, 2008 at 12:17:21PM +0100, Emmanuel BERNARD wrote: > Marc > > I've choosed a chapter and currently translating it but I'd like to know > what is your favourite file format to send it: word, rft or html..? Please don't use these formats, I'll not be able to open the files or it'll be just very difficult to convert them to SGML. You have to use the original SGML file (see http://www.freebsd.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/faq/book.sgml) and just replace the english with the french translation. For that, you will have to use a text editor, here too don't use any windows tool: I mean no notepad but real editor like Vi or Emacs that does not "pollute" the content and/or the layout of the file. -- Marc From mmshop10 at mgm51.com Tue Nov 4 12:20:31 2008 From: mmshop10 at mgm51.com (Mike Miller) Date: Tue Nov 4 12:20:37 2008 Subject: Typo in FeeeBSD handbook Message-ID: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html near the bottom of the page: ----------------------------------------------- 20.2.2.4 Data Verification As previously mentioned, ZFS uses checksums to verify the integrity of stored data. They are enabled automatically upon creation of file systems and may be disabled using the following command: # zfs set checksum=off storage/home This is not a wise idea; however, as checksums take very little storage space and are more useful enabled. There also appear to be no noticeable costs having them enabled. While enabled, it is possible to have ZFS check data integrity using checksum verification. This process is known as “scrubing.” To verify the data integrity of the storage pool, issue the following command:..." ----------------------------------------------- "scrubbing" has two "b"'s This process is known as “scrubbing.” From blackend at FreeBSD.org Tue Nov 4 12:35:29 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Tue Nov 4 12:35:36 2008 Subject: Typo in FeeeBSD handbook In-Reply-To: References: Message-ID: <20081104203526.GB7509@abigail.blackend.org> On Tue, Nov 04, 2008 at 03:00:55PM -0500, Mike Miller wrote: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html > > near the bottom of the page: > > ----------------------------------------------- > 20.2.2.4 Data Verification > > As previously mentioned, ZFS uses checksums to verify the integrity of > stored data. They are enabled automatically upon creation of file systems > and may be disabled using the following command: > > # zfs set checksum=off storage/home > > This is not a wise idea; however, as checksums take very little storage > space and are more useful enabled. There also appear to be no noticeable > costs having them enabled. While enabled, it is possible to have ZFS check > data integrity using checksum verification. This process is known as > “scrubing.” To verify the data integrity of the storage pool, > issue the following command:..." > ----------------------------------------------- > > > "scrubbing" has two "b"'s > Fixed (should appear soon on the web version). Thanks. -- Marc From danger at FreeBSD.org Tue Nov 4 13:17:47 2008 From: danger at FreeBSD.org (Daniel Gerzo) Date: Tue Nov 4 13:17:53 2008 Subject: Bad link on FAQ In-Reply-To: <20081104195204.GA7509@abigail.blackend.org> References: <8CAF35BAC880BC2-7D4-8D@FRR4-L30.sis.aol.com> <20081003112509.GA1043@gothic.blackend.org> <000501c93b4a$3ef3e600$0100000a@arthur> <20081104195204.GA7509@abigail.blackend.org> Message-ID: <851610715.20081104220320@rulez.sk> Hello Emmanuel, Tuesday, November 4, 2008, 8:52:04 PM, you wrote: > For that, you > will have to use a text editor, here too don't use any windows tool: I > mean no notepad but real editor like Vi or Emacs that does not "pollute" > the content and/or the layout of the file. On windows, you may try notepad++: http://notepad-plus.sourceforge.net/uk/site.htm -- Best regards, Daniel mailto:danger@FreeBSD.org From eitanadlerlist at gmail.com Tue Nov 4 16:16:28 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Tue Nov 4 16:16:35 2008 Subject: [patch] for handbook (browsers page) Message-ID: <4910E5D6.1020600@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Could people here please review this patch. A few changes are made: 1) the list at the top of handbook/desktop-browsers.html is changed to a list of major browsers in the system 2) An Entry for dillo and links is added 3) Another column for "license" is added to the top list 4) some "ids" are added so that works properly 5) A note of support for linux flash9 on -STABLE is added 6) Some other minor changes that I don't remember - -- GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkQ5dYACgkQtl8kq+nCzNFqjACfTQfc+j+A+c9wtO1Y6fgIQFLs M0UAmgJheFBzxUnm6Ky2CFYezGIAJ/bP =IN2Z -----END PGP SIGNATURE----- -------------- next part -------------- --- oldchapter.sgml 2008-11-04 18:46:33.000000000 -0500 +++ chapter.sgml 2008-11-04 19:11:54.000000000 -0500 @@ -118,13 +118,7 @@ Please refer to for more information on how to set up these complete desktops. - If you are looking for light-weight browsers, you should - investigate the Ports Collection for - www/dillo, - www/links, or - www/w3m. - - This section covers these applications: + The following browsers can be found using the freeBSD ports system: @@ -134,6 +128,7 @@ Resources Needed Installation from Ports Major Dependencies + License @@ -143,6 +138,7 @@ heavy heavy Gtk+ + Tri-License @@ -159,19 +155,43 @@ medium heavy Gtk+ + Tri-License - - Konqueror - medium - heavy - KDE Libraries + + Konqueror + medium + heavy + KDE Libraries + GPL and LGPL + + + + Dillo + light + light + FLTK2 + GPL v3 + + + Lynx/Links + light + light + - + + + w3m + light + light + ? + + - + Mozilla Mozilla @@ -228,7 +248,7 @@ &prompt.user; mozilla -mail - + Firefox Firefox @@ -306,8 +326,11 @@ large port. The next step is to install the www/linux-flashplugin7 port. Once - this port is installed, the plugin must be installed by each + role="package">www/linux-flashplugin7 port. If you are running 7-STABLE + or later then www/linux-flashplugin9 will also work. + However you need to change to the 2.6.16 version of the kernel first: + &prompt.root sysctl compat.linux.osrelease=2.6.16 + Once this port is installed, the plugin must be installed by each user with nspluginwrapper: &prompt.user; nspluginwrapper -v -a -i @@ -380,6 +403,28 @@ Konqueror is available at . + + Dillo + + + Dillo + + + + Dillo is a stand-alone lightweight web browser which is known for its fast speed and small size. + + To browse the Web with Dillo, install the package: + + &prompt.root; pkg_add -r dillo + + Some FTP sites do not have all the packages, but Dillo can still be obtained + through the Ports Collection by typing: + + &prompt.root; cd /usr/ports/www/dillo +&prompt.root; make install clean + + + From blackend at freebsd.org Wed Nov 5 00:14:46 2008 From: blackend at freebsd.org (Marc Fonvieille) Date: Wed Nov 5 00:14:53 2008 Subject: [patch] for handbook (browsers page) In-Reply-To: <4910E5D6.1020600@gmail.com> References: <4910E5D6.1020600@gmail.com> Message-ID: <20081105081442.GA18783@abigail.blackend.org> On Tue, Nov 04, 2008 at 07:16:22PM -0500, Eitan Adler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Could people here please review this patch. > A few changes are made: > 1) the list at the top of handbook/desktop-browsers.html is changed to a > list of major browsers in the system > 2) An Entry for dillo and links is added > 3) Another column for "license" is added to the top list Is the license information mandatory? I'm not sure it's an important criteria for most users when they choose a browser. > 4) some "ids" are added so that works properly > 5) A note of support for linux flash9 on -STABLE is added The linprocfs part is missing I think. This must be really tested on many different installations, I mean we must provide a way that works out of the box to prevent many complaints :) > 6) Some other minor changes that I don't remember > > - -- > GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkkQ5dYACgkQtl8kq+nCzNFqjACfTQfc+j+A+c9wtO1Y6fgIQFLs > M0UAmgJheFBzxUnm6Ky2CFYezGIAJ/bP > =IN2Z > -----END PGP SIGNATURE----- > --- oldchapter.sgml 2008-11-04 18:46:33.000000000 -0500 > +++ chapter.sgml 2008-11-04 19:11:54.000000000 -0500 > @@ -118,13 +118,7 @@ > Please refer to for more information on > how to set up these complete desktops. > > - If you are looking for light-weight browsers, you should > - investigate the Ports Collection for > - www/dillo, > - www/links, or > - www/w3m. > - Why remove that part? It's interesting for newcomers. > - This section covers these applications: > + The following browsers can be found using the freeBSD ports system: > > > > @@ -134,6 +128,7 @@ > Resources Needed > Installation from Ports > Major Dependencies > + License > > > > @@ -143,6 +138,7 @@ > heavy > heavy > Gtk+ > + Tri-License > > > > @@ -159,19 +155,43 @@ > medium > heavy > Gtk+ > + Tri-License > > > - > - Konqueror > - medium > - heavy > - KDE Libraries > + > + Konqueror > + medium > + heavy > + KDE Libraries > + GPL and LGPL > + > + > + > + Dillo > + light > + light > + FLTK2 > + GPL v3 > > + > + > + Lynx/Links lynx is not links :) > + light > + light > + - > + > + > + w3m > + light > + light > + ? > + > + > > > > > - > + > Mozilla > > Mozilla > @@ -228,7 +248,7 @@ > &prompt.user; mozilla -mail > > > - > + > Firefox > > Firefox > @@ -306,8 +326,11 @@ > large port. > > The next step is to install the - role="package">www/linux-flashplugin7 port. Once > - this port is installed, the plugin must be installed by each > + role="package">www/linux-flashplugin7 port. If you are running 7-STABLE > + or later then www/linux-flashplugin9 will also work. > + However you need to change to the 2.6.16 version of the kernel first: > + &prompt.root sysctl compat.linux.osrelease=2.6.16 > + Once this port is installed, the plugin must be installed by each > user with nspluginwrapper: > > &prompt.user; nspluginwrapper -v -a -i > @@ -380,6 +403,28 @@ > Konqueror > is available at . > > + > + Dillo > + > + > + Dillo > + > + > + > + Dillo is a stand-alone lightweight web browser which is known for its fast speed and small size. > + > + To browse the Web with Dillo, install the package: > + > + &prompt.root; pkg_add -r dillo > + > + Some FTP sites do not have all the packages, but Dillo can still be obtained > + through the Ports Collection by typing: > + > + &prompt.root; cd /usr/ports/www/dillo > +&prompt.root; make install clean > + > + > + > > > > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" -- Marc From gregmo72 at yahoo.com Wed Nov 5 13:18:45 2008 From: gregmo72 at yahoo.com (Greg Mosier) Date: Wed Nov 5 15:15:04 2008 Subject: Bad link on FAQ Message-ID: <234515.87510.qm@web31306.mail.mud.yahoo.com> --- On Tue, 11/4/08, Daniel Gerzo wrote: > On windows, you may try notepad++: > http://notepad-plus.sourceforge.net/uk/site.htm I'd recommend Programmer's File Editor: http://www.download.com/Programmer-s-File-Editor-32-bit-/3000-2352_4-10002157.html Cheers, GregMo From eitanadlerlist at gmail.com Wed Nov 5 15:38:44 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Wed Nov 5 15:38:50 2008 Subject: [patch] for handbook (browsers page) In-Reply-To: <20081105081442.GA18783@abigail.blackend.org> References: <4910E5D6.1020600@gmail.com> <20081105081442.GA18783@abigail.blackend.org> Message-ID: <49122E7B.6000007@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc Fonvieille wrote: > On Tue, Nov 04, 2008 at 07:16:22PM -0500, Eitan Adler wrote: > Could people here please review this patch. > A few changes are made: > 1) the list at the top of handbook/desktop-browsers.html is changed to a > list of major browsers in the system > > > 2) An Entry for dillo and links is added > 3) Another column for "license" is added to the top list > >> Is the license information mandatory? I'm not sure it's an important >> criteria for most users when they choose a browser. Mandatory no? Informative yes? And it doesn't add that much space. I can remove it from the next diff ;). > > 4) some "ids" are added so that works properly > 5) A note of support for linux flash9 on -STABLE is added > >> The linprocfs part is missing I think. This must be really tested on >> many different installations, I mean we must provide a way that works >> out of the box to prevent many complaints :) I'll copy from nox-'s checklist. > > 6) Some other minor changes that I don't remember > - - If you are looking for light-weight browsers, you should - - investigate the Ports Collection for - - www/dillo, - - www/links, or - - www/w3m. - - > Why remove that part? It's interesting for newcomers. Its been moved the list below > lynx is not links :) True - I should have added separate entries *goes to edit edits...* - -- GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkSLnsACgkQtl8kq+nCzNGiNwCeIBCEvb/68Ek4VkZXgLpFt0UA AAAAnROjIc6uLN9XKAcvSnwzNB9b/DY/ =e9va -----END PGP SIGNATURE----- From eitanadlerlist at gmail.com Wed Nov 5 17:47:30 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Wed Nov 5 17:47:37 2008 Subject: [patch] for handbook (browsers page) In-Reply-To: <49122E7B.6000007@gmail.com> References: <4910E5D6.1020600@gmail.com> <20081105081442.GA18783@abigail.blackend.org> <49122E7B.6000007@gmail.com> Message-ID: <49124CA8.2020805@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Newer patch attached. Applied _without_ my original patch. Changes from previous patch: 1) Added a bunch of linux flash 9 steps from nox-'s checklist 2) Removed license column 3) Made links to port pkg-descr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkSTKgACgkQtl8kq+nCzNG3GQCeLvbsYn4St9N1YiIV8YeLvYPK b5gAnR4rPa3Y81tP6b/uxlySfeFZoqT5 =Ezg8 -----END PGP SIGNATURE----- -------------- next part -------------- --- chapter.sgml.orig 2008-10-25 13:16:32.000000000 -0400 +++ chapter.sgml.try.2 2008-11-05 20:44:02.000000000 -0500 @@ -118,13 +118,7 @@ Please refer to for more information on how to set up these complete desktops. - If you are looking for light-weight browsers, you should - investigate the Ports Collection for - www/dillo, - www/links, or - www/w3m. - - This section covers these applications: + The following browsers can be found using the freeBSD ports system: @@ -139,14 +133,14 @@ - Mozilla + www/mozilla heavy heavy Gtk+ - Opera + www/opera light light FreeBSD and Linux versions available. The Linux @@ -155,23 +149,50 @@ - Firefox + www/firefox3 medium heavy Gtk+ - - Konqueror - medium - heavy - KDE Libraries + + konqueror + medium + heavy + KDE Libraries + + + www/dillo + light + light + FLTK2 + + + + www/lynx + light + light + - + + + www/links + light + light + - + + + www/w3m + light + light + ? + + - + Mozilla Mozilla @@ -228,7 +249,7 @@ &prompt.user; mozilla -mail - + Firefox Firefox @@ -306,8 +327,27 @@ large port. The next step is to install the www/linux-flashplugin7 port. Once - this port is installed, the plugin must be installed by each + role="package">www/linux-flashplugin7 port. + If you are running 7-STABLE or later then www/linux-flashplugin9 will also work. + However you need certain prerequisites. + 1) You need to be running -STABLE from at least Mon Oct 20 11:15:57 2008 UTC + 2) You nead change to the 2.6.16 version of the linux kernel: + &prompt.root sysctl compat.linux.osrelease=2.6.16 + Adding this line to sysctl.conf should also work. + 3) Make sure linprocfs is mounted to /compat/linux/proc + 4) Make sure www/nspluginwrapper, www/linux-flashplugin9 and dependencies are installed and up to date. + (the default emulators/linux_base-fc4 should work, if you want to use a later one don't forget to set + compat.linux.osrelease=2.6.16 in sysctl.conf and OVERRIDE_LINUX_BASE_PORT + to whichever version you use in make.conf. Note however that on 6, only the default compat.linux.osrelease=2.4.2 really works.) + + To run flash from native firefox you need www/nspluginwrapper. + If the plugin doesnt show up in firefox' about:plugins, run + &prompt.user nspluginwrapper -i /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so + and restart firefox. + + + + Once this port is installed, the plugin must be installed by each user with nspluginwrapper: &prompt.user; nspluginwrapper -v -a -i @@ -380,6 +420,28 @@ Konqueror is available at . + + Dillo + + + Dillo + + + + Dillo is a stand-alone lightweight web browser which is known for its fast speed and small size. + + To browse the Web with Dillo, install the package: + + &prompt.root; pkg_add -r dillo + + Some FTP sites do not have all the packages, but Dillo can still be obtained + through the Ports Collection by typing: + + &prompt.root; cd /usr/ports/www/dillo +&prompt.root; make install clean + + + -------------- next part -------------- A non-text attachment was scrubbed... Name: try2.patch.sig Type: application/octet-stream Size: 72 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081106/55a23150/try2.patch.obj From xiazhongqi at huawei.com Wed Nov 5 22:32:41 2008 From: xiazhongqi at huawei.com (Sam Xia) Date: Thu Nov 6 04:07:29 2008 Subject: Request complete feature list In-Reply-To: <20081105120019.767B910656D6@hub.freebsd.org> Message-ID: <000001c93fd6$ce1147c0$2f096f0a@china.huawei.com> hi all, Now I want to summarize a comlete list of feature provided by FreeBSD. but i don't know where to find useful resource. Anyone could help me? Best Regards, Sam Xia From eitanadlerlist at gmail.com Thu Nov 6 20:43:01 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Thu Nov 6 20:43:07 2008 Subject: spell check - how to? Message-ID: <4913C74C.80606@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [cc to -questions as it might be a general question] I'm looking to do a full spell check/fix on the handbook. I found "make spellcheck-txt" which apparently removed certain items that would not go well through a spell checker - however I don't know how to actually run the spellcheck itself. I have aspell installed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkTx0wACgkQtl8kq+nCzNHfcACeLHva5seuXKoCX8GT4JBTJfwx lTgAn2RjPnpyU1KkoR51O+hQ1MJLIYGD =ISoq -----END PGP SIGNATURE----- From keramida at freebsd.org Thu Nov 6 22:17:00 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Nov 6 22:17:06 2008 Subject: spell check - how to? In-Reply-To: <4913C74C.80606@gmail.com> (Eitan Adler's message of "Thu, 06 Nov 2008 23:42:52 -0500") References: <4913C74C.80606@gmail.com> Message-ID: <87d4h884c3.fsf@kobe.laptop> On Thu, 06 Nov 2008 23:42:52 -0500, Eitan Adler wrote: > [cc to -questions as it might be a general question] Hi Eitan :-) > I'm looking to do a full spell check/fix on the handbook. I found > "make spellcheck-txt" which apparently removed certain items that > would not go well through a spell checker - however I don't know how > to actually run the spellcheck itself. > > I have aspell installed. You will probably have to tweak the ISPELLOPTS to use aspell. The current spellcheck targets use a default ISPELLOPTS with a value of: %%% doc/el/share/mk/doc.project.mk:ISPELL?= ispell doc/el/share/mk/doc.project.mk:ISPELLOPTS?= -l -p /usr/share/dict/freebsd ${ISPELLFLAGS} %%% The -l option is not supported by aspell, so the following spellcheck run fails: : % pwd : /ws/doc/en_US.ISO8859-1/articles/contributing : % env ISPELL=aspell make FORMATS=txt spellcheck : Spellcheck article.txt : Error: You must specify a parameter for "-l". : *** Error code 1 : But you can set ISPELL and ISPELLOPTS in the runtime environment to pass aspell-compatible options: : % env ISPELL=aspell ISPELLOPTS='list' make FORMATS=txt spellcheck : Spellcheck article.txt : jcamou : IEEE : ... Unfortunately, the wordlist at `/usr/share/dict/freebsd' is not usable with aspell right now, so if you try to use it you will get errors like: : env ISPELL=aspell \ : ISPELLOPTS='-p /usr/share/dict/freebsd ${ISPELLFLAGS}' \ : ISPELLFLAGS='list' make FORMATS=txt spellcheck : Spellcheck article.txt : Error: The file "/usr/share/dict/freebsd" is not in the proper format. : *** Error code 1 The main drawback of being unable to use the `freebsd' wordlist is that you will get many false positives for words that are perfectly valid for FreeBSD documentation but are not standard English words. From roberthuff at rcn.com Fri Nov 7 05:43:27 2008 From: roberthuff at rcn.com (Robert Huff) Date: Fri Nov 7 05:43:34 2008 Subject: spell check - how to? In-Reply-To: <87d4h884c3.fsf@kobe.laptop> References: <4913C74C.80606@gmail.com> <87d4h884c3.fsf@kobe.laptop> Message-ID: <18708.16205.131542.449645@jerusalem.litteratus.org> Giorgos Keramidas writes: > The main drawback of being unable to use the `freebsd' wordlist > is that you will get many false positives for words that are > perfectly valid for FreeBSD documentation but are not standard > English words. I have a script which does something similar, using ispell. It's based on the Perl script - found on-line - appended below. I pseudo-fixed that running the output through sort and starting with least frequent hits. Attempts to build a project-specific dictionary proved too confusing and it was ultimatly not worth the effort. Robert Huff #!/usr/local/bin/perl -W # WordFreq.pl -- Count word frequency in a text file $ver = "v1.0"; # 05-Dec-2001 JP Vossen {jp@jpsdomain.org> # Basics from 8.3, page 280 of _Perl_Cookbook_ # Added stop words (($myname = $0) =~ s/^.*(\/|\\)|\..*$//ig); # remove up to last "\" or "/" and after any "." $Greeting = ("$myname $ver Copyright 12001 JP Vossen (http://www.jpsdomain.org/)\n"); $Greeting .= (" Licensed under the GNU GENERAL PUBLIC LICENSE:\n"); $Greeting .= (" See http://www.gnu.org/copyleft/gpl.html for full text and details.\n"); # Version and copyright info %seen = (); # Create the hash # Define the stopwords @stopwords = ("a", "an", "and", "are", "as", "at", "be", "but", "by", "does", "for", "from", "had", "have", "her", "his", "if", "in", "is", "it", "not", "of", "on", "or", "that", "the", "this", "to", "was", "which", "with", "you"); if (("@ARGV" =~ /\?/) || (@ARGV > 5) || (@ARGV < 0)) { #if wrong # of args, or a ? in args - die print STDERR ("\n$Greeting\n\tUsage: $myname -i {infile} [-s]\n"); print STDERR ("\nIf -s is used, the list of stop words will NOT be used.\n"); print STDERR ("The stopwords currently defined are:\n\n "); foreach $stopword (@stopwords) { print STDERR ("$stopword "); } # end of foreach stopword die ("\n"); } use Getopt::Std; # User Perl5 built-in program argument handler getopts('i:o:s'); # Define possible args. if (! $opt_i) { $opt_i = "-"; } # If no input file specified, use STDIN if (! $opt_o) { $opt_o = "-"; } # If no output file specified, use STDOUT open (INFILE, "$opt_i") || die "$myname: error opening $opt_i $!\n"; open (OUTFILE, ">$opt_o") || die "$myname: error opening $opt_o $!\n"; print STDERR ("\n$Greeting\n"); while () { # Read the input file while ( /(\w['\w-]*)/g ) { # If we have a "word" $seen{lc $1}++; # Count it in the hash } # end of while words } # end of while input if (! $opt_s) { # If we're using stopwords foreach $stopword (@stopwords) { # for each stopword delete($seen{$stopword}); # Remove it from the hash } # end of foreach stopword # This way we only test once for each } # end of if using stopwords stopword, rather than in a loop! # Print the results, sorted most frequent words at the top foreach $word ( sort { $seen{$b} <=> $seen{$a} } keys %seen) { printf OUTFILE ("%6d %s\n", $seen{$word}, $word); } # end of foreach word From ycrc at math.rutgers.edu Fri Nov 7 05:46:27 2008 From: ycrc at math.rutgers.edu (Yves Capdeboscq) Date: Fri Nov 7 05:46:34 2008 Subject: Obsolete email address Message-ID: <200811071327.mA7DRJl26687@math.rutgers.edu> Thank you for your email. I have left the Rutgers Mathematics Department in 2002. Due to the considerable amount of spam I received at this address, your email concerning "Delivery reports about your e-mail" will not be forwarded to my current email address. With my best regards, Yves Capdeboscq From drew at mykitchentable.net Sat Nov 8 08:44:02 2008 From: drew at mykitchentable.net (Drew Tomlinson) Date: Sat Nov 8 08:44:08 2008 Subject: Suggestion For Handbook Addition Regarding sendmail Message-ID: <4915BB76.3020606@mykitchentable.net> I hope this is the right list. If not, please nudge me appropriately. :) I've been using FreeBSD since 4.0 but never learned anything about Sendmail. It seemed very complicated and therefore I chose Postfix for my little home servers. I have never looked back. However I recently installed FreeBSD at work for an application that was not supported on Solaris. The only mail function this machine requires is the ability to send outbound mail from local accounts, i.e. "root". Thus installing postfix seemed overkill. Since the default install of sendmail is already limited to outbound only, I just needed to configure sendmail send via an outbound relay. For such a seemingly common scenario, I turned to the Handbook. I was a little disappointed that section 29.3 did not cover this and found the information in /usr/src/contrib/sendmail/cf/README confusing. I knew I was looking for some *.mc file to edit somehow and then generate the sendmail.cf some way. I suppose that for most *nix admins, this is considered common knowledge. However for a newbie, I was confused. My "Google-fu" turned up lots of links that suggested sendmail be configured to relay via one's ISP relay but no specific instructions on how to achieve this. Finally, I found this FAQ (http://www.technoids.org/freebsdsendmailfaqs.html) to be very helpful for learning how to make a sendmail.cf file the FreeBSD way. If it does break any copyright laws, including this info in the Handbook would help other newbies. Thanks, Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com From EitanAdlerList at gmail.com Sat Nov 8 17:20:03 2008 From: EitanAdlerList at gmail.com (Eitan Adler) Date: Sat Nov 8 17:20:09 2008 Subject: docs/128711: Re: [patch] for handbook browsers page Message-ID: <200811090119.mA91JU1B009107@www.freebsd.org> >Number: 128711 >Category: docs >Synopsis: Re: [patch] for handbook browsers page >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 09 01:20:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Eitan Adler >Release: N/A >Organization: >Environment: N/A >Description: 1) the list at the top of handbook/desktop-browsers.html is changed to a list of major browsers in the system 2) An Entry for dillo and links is added 4) some "ids" are added so that works properly 5) A note of support for linux flash9 on -STABLE is added 6) Made links to port pkg-descr 7) Some other minor changes that I don't remember Patch attached. >How-To-Repeat: >Fix: Patch attached with submission follows: --- chapter.sgml.orig 2008-10-25 13:16:32.000000000 -0400 +++ chapter.sgml.try.2 2008-11-05 20:44:02.000000000 -0500 @@ -118,13 +118,7 @@ Please refer to for more information on how to set up these complete desktops. - If you are looking for light-weight browsers, you should - investigate the Ports Collection for - www/dillo, - www/links, or - www/w3m. - - This section covers these applications: + The following browsers can be found using the freeBSD ports system: @@ -139,14 +133,14 @@ - Mozilla + www/mozilla heavy heavy Gtk+ - Opera + www/opera light light FreeBSD and Linux versions available. The Linux @@ -155,23 +149,50 @@ - Firefox + www/firefox3 medium heavy Gtk+ - - Konqueror - medium - heavy - KDE Libraries + + konqueror + medium + heavy + KDE Libraries + + + www/dillo + light + light + FLTK2 + + + + www/lynx + light + light + - + + + www/links + light + light + - + + + www/w3m + light + light + ? + + - + Mozilla Mozilla @@ -228,7 +249,7 @@ &prompt.user; mozilla -mail - + Firefox Firefox @@ -306,8 +327,27 @@ large port. The next step is to install the www/linux-flashplugin7 port. Once - this port is installed, the plugin must be installed by each + role="package">www/linux-flashplugin7 port. + If you are running 7-STABLE or later then www/linux-flashplugin9 will also work. + However you need certain prerequisites. + 1) You need to be running -STABLE from at least Mon Oct 20 11:15:57 2008 UTC + 2) You nead change to the 2.6.16 version of the linux kernel: + &prompt.root sysctl compat.linux.osrelease=2.6.16 + Adding this line to sysctl.conf should also work. + 3) Make sure linprocfs is mounted to /compat/linux/proc + 4) Make sure www/nspluginwrapper, www/linux-flashplugin9 and dependencies are installed and up to date. + (the default emulators/linux_base-fc4 should work, if you want to use a later one don't forget to set + compat.linux.osrelease=2.6.16 in sysctl.conf and OVERRIDE_LINUX_BASE_PORT + to whichever version you use in make.conf. Note however that on 6, only the default compat.linux.osrelease=2.4.2 really works.) + + To run flash from native firefox you need www/nspluginwrapper. + If the plugin doesnt show up in firefox' about:plugins, run + &prompt.user nspluginwrapper -i /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so + and restart firefox. + + + + Once this port is installed, the plugin must be installed by each user with nspluginwrapper: &prompt.user; nspluginwrapper -v -a -i @@ -380,6 +420,28 @@ Konqueror is available at . + + Dillo + + + Dillo + + + + Dillo is a stand-alone lightweight web browser which is known for its fast speed and small size. + + To browse the Web with Dillo, install the package: + + &prompt.root; pkg_add -r dillo + + Some FTP sites do not have all the packages, but Dillo can still be obtained + through the Ports Collection by typing: + + &prompt.root; cd /usr/ports/www/dillo +&prompt.root; make install clean + + + >Release-Note: >Audit-Trail: >Unformatted: From blackend at FreeBSD.org Sun Nov 9 00:30:06 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sun Nov 9 00:30:12 2008 Subject: docs/128711: Re: [patch] for handbook browsers page Message-ID: <200811090830.mA98U57v067519@freefall.freebsd.org> The following reply was made to PR docs/128711; it has been noted by GNATS. From: Marc Fonvieille To: Eitan Adler Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/128711: Re: [patch] for handbook browsers page Date: Sun, 9 Nov 2008 09:25:07 +0100 On Sun, Nov 09, 2008 at 01:19:30AM +0000, Eitan Adler wrote: > > >Number: 128711 > >Category: docs > >Synopsis: Re: [patch] for handbook browsers page > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Sun Nov 09 01:20:03 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: Eitan Adler > >Release: N/A > >Organization: > >Environment: > N/A > >Description: > 1) the list at the top of handbook/desktop-browsers.html is changed to a list of major browsers in the system The goal of this section is indeed talking about major browsers, the audience is the newcomer to FreeBSD. Firefox (and Mozilla, well Mozilla part should be removed since Firefox is now preferred), Opera and Konqueror can be seen as major browsers since they can really render any site. Dillo, links, lynx, w3m, etc. are light-weight browsers, they can't be seen as major browsers for obvious reasons... The current layout of the page is not bad and I don't see the need to add links, lynx, w3m to the table since we don't talk about them. I've no objection about adding something regarding Dillo, but we must be honest with the reader: Dillo cannot render correctly and be used on every websites around the world. > 2) An Entry for dillo and links is added > 4) some "ids" are added so that works properly > 5) A note of support for linux flash9 on -STABLE is added [...] This part is a bit "messy", it must be reworked and be sure it's working and stable. I have to do some tests. -- Marc From blackend at FreeBSD.org Sun Nov 9 00:31:31 2008 From: blackend at FreeBSD.org (blackend@FreeBSD.org) Date: Sun Nov 9 00:31:41 2008 Subject: docs/128711: Re: [patch] for handbook browsers page Message-ID: <200811090831.mA98VVvX075056@freefall.freebsd.org> Synopsis: Re: [patch] for handbook browsers page Responsible-Changed-From-To: freebsd-doc->blackend Responsible-Changed-By: blackend Responsible-Changed-When: Sun Nov 9 08:30:57 UTC 2008 Responsible-Changed-Why: I'll work on an update of the browsers page. http://www.freebsd.org/cgi/query-pr.cgi?pr=128711 From blackend at FreeBSD.org Sun Nov 9 00:45:53 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sun Nov 9 00:46:13 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <200811090424.mA94OlN6087438@repoman.freebsd.org> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> Message-ID: <20081109084551.GB1058@gothic.blackend.org> On Sun, Nov 09, 2008 at 04:24:47AM +0000, Chin-San Huang wrote: > chinsan 2008-11-09 04:24:47 UTC > > FreeBSD doc repository > > Modified files: > share/misc docbook.css > Log: > - Decorating BLOCKQUOTE box. > This is something we needed but we have to think about the colours and fix the layout for Notes. Let's compare both: http://people.freebsd.org/~blackend/doc/en_US.ISO8859-1/books/handbook/x-config.html and http://www.netbsd.org/docs/guide/en/chap-x.html I think NetBSD way is a bit cleaner than ours. Our Note appears more as a "warning" than just a note. The way they render keyboard inputs and programlisting is also more elegant than ours. It'd be great if everyone could think about all this and if we could reach a consensus with a great docbook.css that also fits with colors set used on http://www.freebsd.org/ website. -- Marc From sonic2000gr at gmail.com Sun Nov 9 01:12:11 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Sun Nov 9 01:12:17 2008 Subject: docs/128711: Re: [patch] for handbook browsers page In-Reply-To: <200811090831.mA98VVvX075056@freefall.freebsd.org> References: <200811090831.mA98VVvX075056@freefall.freebsd.org> Message-ID: <4916A49F.8030709@gmail.com> blackend@FreeBSD.org wrote: > Synopsis: Re: [patch] for handbook browsers page > > Responsible-Changed-From-To: freebsd-doc->blackend > Responsible-Changed-By: blackend > Responsible-Changed-When: Sun Nov 9 08:30:57 UTC 2008 > Responsible-Changed-Why: > I'll work on an update of the browsers page. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=128711 > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > While you are at it, it might also be worth mentioning that firefox3 plug-ins directory is /usr/local/lib/firefox3/plugins and plug-ins might have to be symlinked from the usual browser_plugins place. I am not certain whether this is a temporary condition though. From keramida at freebsd.org Sun Nov 9 09:14:57 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Sun Nov 9 09:15:09 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <20081109084551.GB1058@gothic.blackend.org> (Marc Fonvieille's message of "Sun, 9 Nov 2008 09:45:51 +0100") References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> Message-ID: <87hc6gbz3t.fsf@kobe.laptop> On Sun, 9 Nov 2008 09:45:51 +0100, Marc Fonvieille wrote: > On Sun, Nov 09, 2008 at 04:24:47AM +0000, Chin-San Huang wrote: >> chinsan 2008-11-09 04:24:47 UTC >> >> FreeBSD doc repository >> >> Modified files: >> share/misc docbook.css >> Log: >> - Decorating BLOCKQUOTE box. >> > > This is something we needed but we have to think about the colours and > fix the layout for Notes. > > Let's compare both: > http://people.freebsd.org/~blackend/doc/en_US.ISO8859-1/books/handbook/x-config.html Maybe something like this? http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css.diff I don't really like ``width: 800px;'' in our current stylesheet. In wide monitors, or with lagre font sizes, explicitly using pixels for the width of document elements means that the reader may end up with stuff like this screenshot: http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-bug.png The current elements stand out too much for my taste too, so I removed ``background-color: #DEE3E7;'' from , but added a border (similar to the one of elements) to . You can see the effect of the stylesheet changes of `css.diff' in the two sets of pages: [before] http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/install-pre.html http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/x-config.html [after] http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/install-pre.html http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/x-config.html If these changes look ok, I can commit them some time later this week. From blackend at freebsd.org Sun Nov 9 11:25:11 2008 From: blackend at freebsd.org (Marc Fonvieille) Date: Sun Nov 9 11:25:28 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87hc6gbz3t.fsf@kobe.laptop> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> Message-ID: <20081109192507.GB1030@gothic.blackend.org> On Sun, Nov 09, 2008 at 07:14:46PM +0200, Giorgos Keramidas wrote: > On Sun, 9 Nov 2008 09:45:51 +0100, Marc Fonvieille wrote: > > On Sun, Nov 09, 2008 at 04:24:47AM +0000, Chin-San Huang wrote: > >> chinsan 2008-11-09 04:24:47 UTC > >> > >> FreeBSD doc repository > >> > >> Modified files: > >> share/misc docbook.css > >> Log: > >> - Decorating BLOCKQUOTE box. > >> > > > > This is something we needed but we have to think about the colours and > > fix the layout for Notes. > > > > Let's compare both: > > http://people.freebsd.org/~blackend/doc/en_US.ISO8859-1/books/handbook/x-config.html > > Maybe something like this? > > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css.diff > > I don't really like ``width: 800px;'' in our current stylesheet. In > wide monitors, or with lagre font sizes, explicitly using pixels for the > width of document elements means that the reader may end up with stuff > like this screenshot: > > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-bug.png > > The current elements stand out too much for my taste too, so I > removed ``background-color: #DEE3E7;'' from , but added a border > (similar to the one of elements) to . > > You can see the effect of the stylesheet changes of `css.diff' in the > two sets of pages: > > [before] > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/install-pre.html > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/x-config.html > > [after] > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/install-pre.html > http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/x-config.html > The new x-config.html is fine for me. For the new install-pre.html, the way is rendered looks oldish, maybe using the same scheme as for might do the trick. -- Marc From keramida at freebsd.org Sun Nov 9 12:37:33 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Sun Nov 9 12:37:44 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <20081109192507.GB1030@gothic.blackend.org> (Marc Fonvieille's message of "Sun, 9 Nov 2008 20:25:07 +0100") References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> Message-ID: <87k5bc4ovw.fsf@kobe.laptop> On Sun, 9 Nov 2008 20:25:07 +0100, Marc Fonvieille wrote: >> Maybe something like this? >> >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css.diff >> >> I don't really like ``width: 800px;'' in our current stylesheet. In >> wide monitors, or with lagre font sizes, explicitly using pixels for the >> width of document elements means that the reader may end up with stuff >> like this screenshot: >> >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-bug.png >> >> The current elements stand out too much for my taste too, so I >> removed ``background-color: #DEE3E7;'' from , but added a border >> (similar to the one of elements) to . >> >> You can see the effect of the stylesheet changes of `css.diff' in the >> two sets of pages: >> >> [before] >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/install-pre.html >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/x-config.html >> >> [after] >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/install-pre.html >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/x-config.html > > The new x-config.html is fine for me. > For the new install-pre.html, the way is > rendered looks oldish, maybe using the same scheme as for > might do the trick. The bold red text is kind of `old school' for me too. I'll wait to see if there are flames^W^H err, objections about the rest and update the style too :) From r.c.ladan at gmail.com Sun Nov 9 12:43:34 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Sun Nov 9 12:43:40 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate Message-ID: <49174B71.9080800@gmail.com> Hi, the current version of the Committers Guide (1.278 2008-08-16 21:42:35 pgj) uses CVS for everything, but as of last June the src repository uses SVN. I can write a preliminary patch for the article if you want me too. I think it would be possible to just refer to the wiki in some cases. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From sonic2000gr at gmail.com Sun Nov 9 13:06:53 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Sun Nov 9 13:06:59 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <49174B71.9080800@gmail.com> References: <49174B71.9080800@gmail.com> Message-ID: <491750E9.4070204@gmail.com> Rene Ladan wrote: > Hi, > > the current version of the Committers Guide (1.278 2008-08-16 21:42:35 > pgj) > uses CVS for everything, but as of last June the src repository uses SVN. > > I can write a preliminary patch for the article if you want me too. That would be nice :) > I think > it would be possible to just refer to the wiki in some cases. IMHO, it would serve better if the guide is self contained, so someone can print it and keep as reference without having to resort to the wiki. Though the wiki should appear as a link of course. From gavin at FreeBSD.org Mon Nov 10 02:34:14 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Mon Nov 10 02:34:25 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87k5bc4ovw.fsf@kobe.laptop> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> Message-ID: <1226311326.84196.1.camel@buffy.york.ac.uk> On Sun, 2008-11-09 at 22:37 +0200, Giorgos Keramidas wrote: > On Sun, 9 Nov 2008 20:25:07 +0100, Marc Fonvieille wrote: > > The new x-config.html is fine for me. > > For the new install-pre.html, the way is > > rendered looks oldish, maybe using the same scheme as for > > might do the trick. > > The bold red text is kind of `old school' for me too. I'll wait to see > if there are flames^W^H err, objections about the rest and update the > style too :) FWIW, I like the look of the new style sheet nore than the old one, but do agree with Marc about the new font used on - I assume this is due to the removal of "font-family: arial;" from BLOCKQUOTE.IMPORTANT. Gavin From bugmaster at FreeBSD.org Mon Nov 10 03:06:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 10 03:06:32 2008 Subject: Current unassigned doc problem reports Message-ID: <200811101106.mAAB65aL048773@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/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128325 doc README.snapshots still refers to snaphots as "alpha-te o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128129 doc Sysinstall color problem in xterm o docs/128128 doc Sysinstall not mentioned in 4.4 "Using the Packages Sy o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127923 doc Please mention qemu in the FreeBSD Handbook o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/127406 doc [patch] update umodem man page: Sony Ericsson W810i o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122470 doc [patch] exit status on fetch(1) manual page o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o 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 docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121197 doc [patch] edits to books/porters-handbook 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/120628 doc PAE documentation errror in handbook 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/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) s docs/119404 doc [request] events page should list only last 2 years wo o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu 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/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument 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/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported 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/112481 doc bug in ppp.linkup example 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/111263 doc [request] Information on $EDITOR variable in section 3 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/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout 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 o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n 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/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym 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/98759 doc [patch] sbp_targ(4) man page missing reference to devi 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/95139 doc FAQ to move filesystem to new disk fails: incorrect pe 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/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous 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/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI 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 o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt 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/47818 doc [patch] ln(1) manpage is confusing 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 o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. 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 170 problems total. From r.c.ladan at gmail.com Mon Nov 10 04:08:53 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Nov 10 04:09:00 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <491750E9.4070204@gmail.com> References: <49174B71.9080800@gmail.com> <491750E9.4070204@gmail.com> Message-ID: 2008/11/9 Manolis Kiagias : > Rene Ladan wrote: >> >> Hi, >> >> the current version of the Committers Guide (1.278 2008-08-16 21:42:35 >> pgj) >> uses CVS for everything, but as of last June the src repository uses SVN. >> >> I can write a preliminary patch for the article if you want me too. > > That would be nice :) > Nobody seems to object (or I'm too fast concluding it ;) ), so I'll start working on a patch after I've finished the translation of the "Contributing to FreeBSD" article. Keep an eye on //depot/projects/docproj_nl/... in perforce for progress. >> I think >> it would be possible to just refer to the wiki in some cases. > > IMHO, it would serve better if the guide is self contained, so someone can > print it and keep as reference without having to resort to the wiki. Though > the wiki should appear as a link of course. > Sound ok to me. I think the Committers Guide should cover the basic/common operations, the more exotic ones can be in the wiki. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From pgj at FreeBSD.org Mon Nov 10 07:29:51 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Nov 10 07:29:57 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <49174B71.9080800@gmail.com> References: <49174B71.9080800@gmail.com> Message-ID: <49184BDB.5070707@FreeBSD.org> Hello, Rene Ladan wrote: > the current version of the Committers Guide (1.278 2008-08-16 21:42:35 pgj) > uses CVS for everything, but as of last June the src repository uses SVN. Yeah, but do not forget many committers (two out of three kinds) still using and going to use CVS for a time being. Merging des's SVN Primer [1] into this guide would be a good idea, but note that some of its parts have been already put into developers-handbook [2]. While you are at committers-guide, it would be worth to mention FreeBSD wiki accounts [3] too, because it is "default" for developers now. I also wanted to revise some other sections of the committers-guide, for example (without the claim of completeness): - "Note: If you are a developer but not a committer, you will not be subscribed to the committers or developers mailing lists; the subscriptions are derived from the access rights." -- Is it still true? For example, bug busters are not committers but members of the developers' mailing list. - CVS Tags should be updated. - I am sure that contents of "Who's Who" should be also updated. - There is some information needed about the servers (i.e. freefall, hub, pointyhat etc.) a developer may access, at least their hostname. I remember it did not find these servers first time :) Of course, they are listed on the Project's internal page, but at least a link would be welcome to that page. - I am not sure that "A Free 4-CD Set or DVD Subscription" is still available for committers. :g [1] http://wiki.freebsd.org/SubversionPrimer [2] http://www.freebsd.org/doc/en/books/developers-handbook/policies-contributed.html [3] http://wiki.freebsd.org/AboutWiki From keramida at freebsd.org Mon Nov 10 09:28:18 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 10 09:28:30 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <1226311326.84196.1.camel@buffy.york.ac.uk> (Gavin Atkinson's message of "Mon, 10 Nov 2008 10:02:06 +0000") References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> <1226311326.84196.1.camel@buffy.york.ac.uk> Message-ID: <87fxlza3tj.fsf@kobe.laptop> On Mon, 10 Nov 2008 10:02:06 +0000, Gavin Atkinson wrote: >On Sun, 2008-11-09 at 22:37 +0200, Giorgos Keramidas wrote: >>On Sun, 9 Nov 2008 20:25:07 +0100, Marc Fonvieille wrote: >>> The new x-config.html is fine for me. >>> For the new install-pre.html, the way is >>> rendered looks oldish, maybe using the same scheme as for >>> might do the trick. >> >> The bold red text is kind of `old school' for me too. I'll wait to see >> if there are flames^W^H err, objections about the rest and update the >> style too :) > > FWIW, I like the look of the new style sheet nore than the old one, but > do agree with Marc about the new font used on - I assume > this is due to the removal of "font-family: arial;" from > BLOCKQUOTE.IMPORTANT. It's the line-height that makes things look funny. How about something that makes Important notes stand out a bit like this version? http://people.freebsd.org/~keramida/bsd-css/2008.11.10/install-pre.html The changes to the `blockquote.IMPORTANT' class are: * Remove `color: red', `font-family: arial', `font-weight: bold' and the custom `line-height'. * Add a bit of padding to avoid bumping into any
borders. * Add a red border with a thick left side that highlights the block. This way the font family is the same as the rest of the text and it doesn't look weird if your default sans-serif font is, say, DejaVu instead of Arial :) [ I'm undecided between making .IMPORTANT stand out with a red background and this. A red background seems like something that can hurt my eyes if I stare at it for a long time. This is _different_ that the rest of the .NOTE, .EXAMPLE and so on. ] From r.c.ladan at gmail.com Mon Nov 10 09:31:47 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Nov 10 09:31:54 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87fxlza3tj.fsf@kobe.laptop> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> <1226311326.84196.1.camel@buffy.york.ac.uk> <87fxlza3tj.fsf@kobe.laptop> Message-ID: 2008/11/10 Giorgos Keramidas : > On Mon, 10 Nov 2008 10:02:06 +0000, Gavin Atkinson wrote: >>On Sun, 2008-11-09 at 22:37 +0200, Giorgos Keramidas wrote: >>>On Sun, 9 Nov 2008 20:25:07 +0100, Marc Fonvieille wrote: >>>> The new x-config.html is fine for me. >>>> For the new install-pre.html, the way is >>>> rendered looks oldish, maybe using the same scheme as for >>>> might do the trick. >>> >>> The bold red text is kind of `old school' for me too. I'll wait to see >>> if there are flames^W^H err, objections about the rest and update the >>> style too :) >> >> FWIW, I like the look of the new style sheet nore than the old one, but >> do agree with Marc about the new font used on - I assume >> this is due to the removal of "font-family: arial;" from >> BLOCKQUOTE.IMPORTANT. > > It's the line-height that makes things look funny. How about something > that makes Important notes stand out a bit like this version? > > http://people.freebsd.org/~keramida/bsd-css/2008.11.10/install-pre.html > > The changes to the `blockquote.IMPORTANT' class are: > > * Remove `color: red', `font-family: arial', `font-weight: bold' and > the custom `line-height'. > > * Add a bit of padding to avoid bumping into any
borders. > > * Add a red border with a thick left side that highlights the block. > > This way the font family is the same as the rest of the text and it > doesn't look weird if your default sans-serif font is, say, DejaVu > instead of Arial :) > > [ I'm undecided between making .IMPORTANT stand out with a red > background and this. A red background seems like something that can > hurt my eyes if I stare at it for a long time. This is _different_ that > the rest of the .NOTE, .EXAMPLE and so on. ] > > The result looks reasonable to me. I would not use an entirely red background for the warnings: they scream too much that way. I wonder if there are any standards on text formatting... Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From keramida at freebsd.org Mon Nov 10 10:33:34 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 10 10:33:41 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: (Rene Ladan's message of "Mon, 10 Nov 2008 18:31:45 +0100") References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> <1226311326.84196.1.camel@buffy.york.ac.uk> <87fxlza3tj.fsf@kobe.laptop> Message-ID: <87fxlz4ej1.fsf@kobe.laptop> CC list trimmed a bit. This is freebsd-doc material, AFAICT. On Mon, 10 Nov 2008 18:31:45 +0100, "Rene Ladan" wrote: >2008/11/10 Giorgos Keramidas : >> [ I'm undecided between making .IMPORTANT stand out with a red >> background and this. A red background seems like something that can >> hurt my eyes if I stare at it for a long time. This is _different_ that >> the rest of the .NOTE, .EXAMPLE and so on. ] > > The result looks reasonable to me. I would not use an entirely red background > for the warnings: they scream too much that way. Right. That's what I thought too :) > I wonder if there are any standards on text formatting... CSS formatting or just text formatting in general, including styles for print output? From r.c.ladan at gmail.com Mon Nov 10 11:14:47 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Nov 10 11:14:54 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87fxlz4ej1.fsf@kobe.laptop> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> <1226311326.84196.1.camel@buffy.york.ac.uk> <87fxlza3tj.fsf@kobe.laptop> <87fxlz4ej1.fsf@kobe.laptop> Message-ID: <49188822.60400@gmail.com> Giorgos Keramidas schreef: > CC list trimmed a bit. This is freebsd-doc material, AFAICT. > > On Mon, 10 Nov 2008 18:31:45 +0100, "Rene Ladan" wrote: >> 2008/11/10 Giorgos Keramidas : >>> [ I'm undecided between making .IMPORTANT stand out with a red >>> background and this. A red background seems like something that can >>> hurt my eyes if I stare at it for a long time. This is _different_ that >>> the rest of the .NOTE, .EXAMPLE and so on. ] >> The result looks reasonable to me. I would not use an entirely red background >> for the warnings: they scream too much that way. > > Right. That's what I thought too :) > We could make warnings all red and add some arrows in 5 colors pointing to them :-p >> I wonder if there are any standards on text formatting... > > CSS formatting or just text formatting in general, including styles for > print output? > (Printed) Text formatting in general. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From keramida at freebsd.org Mon Nov 10 12:24:44 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 10 12:24:50 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <49188822.60400@gmail.com> (Rene Ladan's message of "Mon, 10 Nov 2008 20:14:42 +0100") References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> <1226311326.84196.1.camel@buffy.york.ac.uk> <87fxlza3tj.fsf@kobe.laptop> <87fxlz4ej1.fsf@kobe.laptop> <49188822.60400@gmail.com> Message-ID: <87iqqvs518.fsf@kobe.laptop> On Mon, 10 Nov 2008 20:14:42 +0100, Rene Ladan wrote: >Giorgos Keramidas schreef: >>> I wonder if there are any standards on text formatting... >> >> CSS formatting or just text formatting in general, including styles >> for print output? > > (Printed) Text formatting in general. Not `standards' in Internet sense, no. But I have insinuated most of my typesetting experience from tinkering with groff, Texinfo, TeX and LaTeX, and by reading books mentioned in their documentation. From victor at bsdes.net Mon Nov 10 14:20:02 2008 From: victor at bsdes.net (Victor Balada Diaz) Date: Mon Nov 10 14:20:08 2008 Subject: docs/128768: Missing documentation about tmpfs mount options Message-ID: <20081110215817.F021D119D91@alf.bsdes.net> >Number: 128768 >Category: docs >Synopsis: Missing documentation about tmpfs mount options >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 10 22:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Victor Balada Diaz >Release: FreeBSD 7.1-BETA2 amd64 >Organization: >Environment: FreeBSD 7.1 -BETA2 amd64 >Description: tmpfs have mount options that should be documented in mount(8). This options are uid, gid, size, owner, inodes, mode. You can find a detailed description of what they do in: http://netbsd.gw.com/cgi-bin/man-cgi?mount_tmpfs+8+NetBSD-current Also i find weird that FFS man page is no section 7 and tmpfs man page is on section 5. Shouldn't tmpfs be on 4 or 7? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From webmaster at psy.miami.edu Tue Nov 11 17:20:54 2008 From: webmaster at psy.miami.edu (Webmaster) Date: Tue Nov 11 17:21:01 2008 Subject: relevance of FreeBSD From Scratch Message-ID: <491A2B3D.5050107@psy.miami.edu> Jens, I am getting ready to utilize your scripts for FreeBSD from scratch. I just wondered whether you are still installing/upgrading your systems with these scripts for FreeBSD 7 releases or if there is something cooler you have moved onto. Any tips would be appreciated. Thanks, Derek From freebsdbugs.20.awinder at spamgourmet.com Tue Nov 11 17:30:01 2008 From: freebsdbugs.20.awinder at spamgourmet.com (Winder) Date: Tue Nov 11 17:30:08 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector Message-ID: <200811120121.mAC1LtSF082839@www.freebsd.org> >Number: 128804 >Category: docs >Synopsis: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 12 01:30:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Winder >Release: 7.1-PRERELEASE >Organization: >Environment: FreeBSD DEV2 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Fri Nov 7 19:54:41 MST 2008 windrider@DEV2:/usr/obj/usr/src/sys/packetcheckv1-fileserv amd64 >Description: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html This geom mirroring documentation shows a way to convert the boot drive into a gmirror raid. This guide misleads in assuming your whole drive has not been used. The problem is that gmirror truncates the last sector of the drive for metadata; thus, any data stored in that sector when adding the drive into the RAID is lost. Sysinstall uses the entire drive by default. Following these instructions, then, could cause loss of data or a corrupt partition, as it will reach one sector beyond the end of the geom mirror device. mightn't it be better to make an example from a blank disk? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From trhodes at FreeBSD.org Wed Nov 12 00:00:12 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Nov 12 00:00:58 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector Message-ID: <200811120800.mAC80Cm2038380@freefall.freebsd.org> The following reply was made to PR docs/128804; it has been noted by GNATS. From: Tom Rhodes To: Winder Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector Date: Wed, 12 Nov 2008 02:18:59 -0500 On Wed, 12 Nov 2008 01:21:55 GMT Winder wrote: Hi, > > >Number: 128804 > >Category: docs > >Synopsis: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Nov 12 01:30:01 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: Winder > >Release: 7.1-PRERELEASE > >Organization: > >Environment: > FreeBSD DEV2 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Fri Nov 7 19:54:41 MST 2008 windrider@DEV2:/usr/obj/usr/src/sys/packetcheckv1-fileserv amd64 > >Description: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html > > This geom mirroring documentation shows a way to convert the boot drive into a gmirror raid. This guide misleads in assuming your whole drive has not been used. > > The problem is that gmirror truncates the last sector of the drive for metadata; thus, any data stored in that sector when adding the drive into the RAID is lost. Sysinstall uses the entire drive by default. Following these instructions, then, could cause loss of data or a corrupt partition, as it will reach one sector beyond the end of the geom mirror device. > > mightn't it be better to make an example from a blank disk? I would think that converting the disk device to a software RAID, at least the boot disk, would be the way most people wanted to use it. And in most cases, I think that it's one of the first things done during an installation - though, YMMV. If the last sector is filled with user data - there are larger problems, possibly, than just where GEOM places metadata. If you feel a warning is required here, I'll gladly add one, but it never crossed my mind initially that someone would actually be using the last sector on the drive for data. Thanks, -- Tom Rhodes From fender0107401 at gmail.com Wed Nov 12 05:25:27 2008 From: fender0107401 at gmail.com (Li) Date: Wed Nov 12 05:25:33 2008 Subject: Preface need update. Message-ID: <1226494693.1809.10.camel@localhost> Hello Everyone: I am a FreeBSD fan, and I like reading the . Recently, I note that some new contents(chapter 20 File Systems Support, chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. But the preface section have not corresponding introduction. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html fender -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081112/90b64ff7/attachment.pgp From rsmith at xs4all.nl Wed Nov 12 05:40:02 2008 From: rsmith at xs4all.nl (Roland Smith) Date: Wed Nov 12 05:40:09 2008 Subject: docs/128816: [PATCH] Enhance the explanation of using of mount options in fstab(5) Message-ID: <20081112131559.5B44CBA8A@slackbox.xs4all.nl> >Number: 128816 >Category: docs >Synopsis: [PATCH] Enhance the explanation of using of mount options in fstab(5) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Nov 12 13:40:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Roland Smith >Release: FreeBSD 7.1-PRERELEASE amd64 >Organization: >Environment: System: FreeBSD slackbox.xs4all.nl 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Sep 25 16:47:48 CEST 2008 rsmith@slackbox.xs4all.nl:/usr/obj/usr/src/sys/QUADSLACK amd64 >Description: The fstab manual page (and others) imply that only the -o options of different mount commands can be used in fstab. Other flags can be used as well, but this is not documented. >How-To-Repeat: Read fstab(5) >Fix: Apply one of the following patches to /usr/src/share/man/man5/fstab.5. The first patch is against HEAD (r1.30), while the second is against 7.1-PRERELEASE (r1.26). ----- patch for fstab.5 (r1.30) ----- --- fstab.5.orig 2008-11-12 13:32:14.000000000 +0100 +++ fstab.5 2008-11-12 14:02:58.000000000 +0100 @@ -32,7 +32,7 @@ .\" @(#)fstab.5 8.1 (Berkeley) 6/5/93 .\" $FreeBSD: src/share/man/man5/fstab.5,v 1.30 2008/02/11 09:36:43 mpp Exp $ .\" -.Dd February 11, 2008 +.Dd November 12, 2008 .Dt FSTAB 5 .Os .Sh NAME @@ -91,15 +91,29 @@ It is formatted as a comma separated list of options. It contains at least the type of mount (see .Fa fs_type -below) plus any additional options -appropriate to the file system type. +below) plus any additional options appropriate to the file system type. See the options flag .Pq Fl o in the .Xr mount 8 page and the file system specific page, such as .Xr mount_nfs 8 , -for additional options that may be specified. +for additional options that may be specified. All options that can be given +to the file system specific mount commands can be used in +.Nm +as well. They just need to be formatted differently. The arguments of the +.Fl o +option can be used without the preceding +.Fl o +flag. Other options need the flag and its argument separated by an equal +sign. So for e.g. mounting an +.Xr msdosfs 5 +filesystem, the options +.Dq -o sync -o noatime -m 644 -M 755 -u foo -g bar +on the command-line become +.Dq sync,noatime,-m=644,-M=755,-u=foo,-g=bar +in +.Nm . .Pp If the options ``userquota'' and/or ``groupquota'' are specified, the file system is automatically processed by the ----- patch for fstab.5 (r1.30) ----- ----- patch for fstab.5 (r1.26) ----- --- fstab.5.orig 2008-11-12 14:09:39.000000000 +0100 +++ fstab.5 2008-11-12 14:10:53.000000000 +0100 @@ -32,7 +32,7 @@ .\" @(#)fstab.5 8.1 (Berkeley) 6/5/93 .\" $FreeBSD: src/share/man/man5/fstab.5,v 1.26 2004/07/03 18:29:22 ru Exp $ .\" -.Dd June 5, 1993 +.Dd November 12, 2008 .Dt FSTAB 5 .Os .Sh NAME @@ -98,15 +98,29 @@ It is formatted as a comma separated list of options. It contains at least the type of mount (see .Fa fs_type -below) plus any additional options -appropriate to the file system type. +below) plus any additional options appropriate to the file system type. See the options flag .Pq Fl o in the .Xr mount 8 page and the file system specific page, such as .Xr mount_nfs 8 , -for additional options that may be specified. +for additional options that may be specified. All options that can be given +to the file system specific mount commands can be used in +.Nm +as well. They just need to be formatted differently. The arguments of the +.Fl o +option can be used without the preceding +.Fl o +flag. Other options need the flag and its argument separated by an equal +sign. So for e.g. mounting an +.Xr msdosfs 5 +filesystem, the options +.Dq -o sync -o noatime -m 644 -M 755 -u foo -g bar +on the command-line become +.Dq sync,noatime,-m=644,-M=755,-u=foo,-g=bar +in +.Nm . .Pp If the options ``userquota'' and/or ``groupquota'' are specified, the file system is automatically processed by the ----- patch for fstab.5 (r1.26) ----- >Release-Note: >Audit-Trail: >Unformatted: From fbsdlists at gmail.com Wed Nov 12 07:16:37 2008 From: fbsdlists at gmail.com (Bob Johnson) Date: Wed Nov 12 07:16:44 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector In-Reply-To: <200811120800.mAC80Cm2038380@freefall.freebsd.org> References: <200811120800.mAC80Cm2038380@freefall.freebsd.org> Message-ID: <54db43990811120654l213596f1j844c3f185c3eb577@mail.gmail.com> The user has no control over whether the last sector of the drive is used for data. Data is scattered all over the drive, in something that resembles a random fashion, and I know of no reason the last sector is not just as likely to have data stored to it as any other sector on the drive (but I am certainly not an authority on the filesystem algorithms). I think a warning is very much in order (that there is a small chance that data will be lost by this procedure). - Bob On 11/12/08, Tom Rhodes wrote: > The following reply was made to PR docs/128804; it has been noted by GNATS. > > From: Tom Rhodes > To: Winder > Cc: freebsd-gnats-submit@FreeBSD.org > Subject: Re: docs/128804: Gmirror handbook instructions convert boot-drive > to gmirror, truncating last sector > Date: Wed, 12 Nov 2008 02:18:59 -0500 > > On Wed, 12 Nov 2008 01:21:55 GMT > Winder wrote: > > Hi, > > > > > > >Number: 128804 > > >Category: docs > > >Synopsis: Gmirror handbook instructions convert boot-drive to > gmirror, truncating last sector > > >Confidential: no > > >Severity: non-critical > > >Priority: medium > > >Responsible: freebsd-doc > > >State: open > > >Quarter: > > >Keywords: > > >Date-Required: > > >Class: doc-bug > > >Submitter-Id: current-users > > >Arrival-Date: Wed Nov 12 01:30:01 UTC 2008 > > >Closed-Date: > > >Last-Modified: > > >Originator: Winder > > >Release: 7.1-PRERELEASE > > >Organization: > > >Environment: > > FreeBSD DEV2 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Fri Nov 7 > 19:54:41 MST 2008 > windrider@DEV2:/usr/obj/usr/src/sys/packetcheckv1-fileserv amd64 > > >Description: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html > > > > This geom mirroring documentation shows a way to convert the boot drive > into a gmirror raid. This guide misleads in assuming your whole drive has > not been used. > > > > The problem is that gmirror truncates the last sector of the drive for > metadata; thus, any data stored in that sector when adding the drive into > the RAID is lost. Sysinstall uses the entire drive by default. Following > these instructions, then, could cause loss of data or a corrupt partition, > as it will reach one sector beyond the end of the geom mirror device. > > > > mightn't it be better to make an example from a blank disk? > > I would think that converting the disk device to a software > RAID, at least the boot disk, would be the way most people > wanted to use it. And in most cases, I think that it's one > of the first things done during an installation - though, > YMMV. If the last sector is filled with user data - there > are larger problems, possibly, than just where GEOM places > metadata. > > If you feel a warning is required here, I'll gladly add one, > but it never crossed my mind initially that someone would > actually be using the last sector on the drive for data. > > Thanks, > > -- > Tom Rhodes > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > -- -- Bob Johnson fbsdlists@gmail.com From sonic2000gr at gmail.com Wed Nov 12 08:13:24 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Nov 12 08:13:29 2008 Subject: Preface need update. In-Reply-To: <1226494693.1809.10.camel@localhost> References: <1226494693.1809.10.camel@localhost> Message-ID: <491B009E.8050408@gmail.com> Li wrote: > Hello Everyone: > > I am a FreeBSD fan, and I like reading the . > > Recently, I note that some new contents(chapter 20 File Systems Support, > chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. > > But the preface section have not corresponding introduction. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html > > fender > You are right, the "Organization of this book" section jumps from chapter 19 to chapter 21 and from 24 to 27, exactly the places of the new chapters. I will try to create a patch for this Thanks! manolis@ From sonic2000gr at gmail.com Wed Nov 12 13:47:51 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Nov 12 13:47:58 2008 Subject: Preface need update. In-Reply-To: <1226494693.1809.10.camel@localhost> References: <1226494693.1809.10.camel@localhost> Message-ID: <491B4F01.9020403@gmail.com> Li wrote: > Hello Everyone: > > I am a FreeBSD fan, and I like reading the . > > Recently, I note that some new contents(chapter 20 File Systems Support, > chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. > > But the preface section have not corresponding introduction. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html > > fender > A fix has just been committed, and will appear on the website in the next 24 hours. Thanks for reporting this! manolis@ From murray at stokely.org Wed Nov 12 16:36:54 2008 From: murray at stokely.org (Murray Stokely) Date: Wed Nov 12 16:37:01 2008 Subject: Preface need update. In-Reply-To: <491B4F01.9020403@gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> Message-ID: <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> Thanks Manolis. Maybe we should add a comment to the Makefile so that when authors commit new chapters they remember to also update the preface summary. Or alternatively, we could put some kind of one sentence chapter description in of each chapter and pull it out of each file dynamically when building the preface. I'd probably recommend the low tech first suggestion as good enough. - Murray On Wed, Nov 12, 2008 at 1:47 PM, Manolis Kiagias wrote: > Li wrote: >> >> Hello Everyone: >> >> I am a FreeBSD fan, and I like reading the . >> >> Recently, I note that some new contents(chapter 20 File Systems Support, >> chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. >> >> But the preface section have not corresponding introduction. >> >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html >> >> fender >> > > A fix has just been committed, and will appear on the website in the next 24 > hours. > > Thanks for reporting this! > manolis@ > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > From trhodes at FreeBSD.org Wed Nov 12 17:04:58 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Nov 12 17:05:10 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector In-Reply-To: <54db43990811120654l213596f1j844c3f185c3eb577@mail.gmail.com> References: <200811120800.mAC80Cm2038380@freefall.freebsd.org> <54db43990811120654l213596f1j844c3f185c3eb577@mail.gmail.com> Message-ID: <20081112200454.3ddb9b89.trhodes@FreeBSD.org> On Wed, 12 Nov 2008 09:54:49 -0500 "Bob Johnson" wrote: > The user has no control over whether the last sector of the drive is > used for data. Data is scattered all over the drive, in something that > resembles a random fashion, and I know of no reason the last sector is > not just as likely to have data stored to it as any other sector on > the drive (but I am certainly not an authority on the filesystem > algorithms). > > I think a warning is very much in order (that there is a small chance > that data will be lost by this procedure). > > - Bob Don't Unix file systems attempt to lump data closer together in order to reduce this fragmentation which scatters data across the entire drive, making it unlikely to have data in that last sector unless one went beyond the 8% boundry? > > > On 11/12/08, Tom Rhodes wrote: > > The following reply was made to PR docs/128804; it has been noted by GNATS. > > > > From: Tom Rhodes > > To: Winder > > Cc: freebsd-gnats-submit@FreeBSD.org > > Subject: Re: docs/128804: Gmirror handbook instructions convert boot-drive > > to gmirror, truncating last sector > > Date: Wed, 12 Nov 2008 02:18:59 -0500 > > > > On Wed, 12 Nov 2008 01:21:55 GMT > > Winder wrote: > > > > Hi, > > > > > > > > > > >Number: 128804 > > > >Category: docs > > > >Synopsis: Gmirror handbook instructions convert boot-drive to > > gmirror, truncating last sector > > > >Confidential: no > > > >Severity: non-critical > > > >Priority: medium > > > >Responsible: freebsd-doc > > > >State: open > > > >Quarter: > > > >Keywords: > > > >Date-Required: > > > >Class: doc-bug > > > >Submitter-Id: current-users > > > >Arrival-Date: Wed Nov 12 01:30:01 UTC 2008 > > > >Closed-Date: > > > >Last-Modified: > > > >Originator: Winder > > > >Release: 7.1-PRERELEASE > > > >Organization: > > > >Environment: > > > FreeBSD DEV2 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Fri Nov 7 > > 19:54:41 MST 2008 > > windrider@DEV2:/usr/obj/usr/src/sys/packetcheckv1-fileserv amd64 > > > >Description: > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html > > > > > > This geom mirroring documentation shows a way to convert the boot drive > > into a gmirror raid. This guide misleads in assuming your whole drive has > > not been used. > > > > > > The problem is that gmirror truncates the last sector of the drive for > > metadata; thus, any data stored in that sector when adding the drive into > > the RAID is lost. Sysinstall uses the entire drive by default. Following > > these instructions, then, could cause loss of data or a corrupt partition, > > as it will reach one sector beyond the end of the geom mirror device. > > > > > > mightn't it be better to make an example from a blank disk? > > > > I would think that converting the disk device to a software > > RAID, at least the boot disk, would be the way most people > > wanted to use it. And in most cases, I think that it's one > > of the first things done during an installation - though, > > YMMV. If the last sector is filled with user data - there > > are larger problems, possibly, than just where GEOM places > > metadata. > > > > If you feel a warning is required here, I'll gladly add one, > > but it never crossed my mind initially that someone would > > actually be using the last sector on the drive for data. > > > > Thanks, > > > > -- > > Tom Rhodes > > _______________________________________________ > > freebsd-doc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > > > -- > -- Bob Johnson > fbsdlists@gmail.com > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > -- Tom Rhodes From trhodes at FreeBSD.org Wed Nov 12 17:07:58 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Nov 12 17:08:05 2008 Subject: Preface need update. In-Reply-To: <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> Message-ID: <20081112200755.66c52a48.trhodes@FreeBSD.org> On Wed, 12 Nov 2008 16:05:55 -0800 "Murray Stokely" wrote: > Thanks Manolis. Maybe we should add a comment to the Makefile so that > when authors commit new chapters they remember to also update the > preface summary. Or alternatively, we could put some kind of one > sentence chapter description in of each chapter and pull > it out of each file dynamically when building the preface. I'd > probably recommend the low tech first suggestion as good enough. > > - Murray Yea, because I forget this every time I add a new chapter. :( > > On Wed, Nov 12, 2008 at 1:47 PM, Manolis Kiagias wrote: > > Li wrote: > >> > >> Hello Everyone: > >> > >> I am a FreeBSD fan, and I like reading the . > >> > >> Recently, I note that some new contents(chapter 20 File Systems Support, > >> chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. > >> > >> But the preface section have not corresponding introduction. > >> > >> > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html > >> > >> fender > >> > > > > A fix has just been committed, and will appear on the website in the next 24 > > hours. > > > > Thanks for reporting this! > > manolis@ > > _______________________________________________ > > freebsd-doc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > -- Tom Rhodes From trhodes at FreeBSD.org Wed Nov 12 19:04:43 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Nov 12 19:04:55 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector In-Reply-To: <20081112200454.3ddb9b89.trhodes@FreeBSD.org> References: <200811120800.mAC80Cm2038380@freefall.freebsd.org> <54db43990811120654l213596f1j844c3f185c3eb577@mail.gmail.com> <20081112200454.3ddb9b89.trhodes@FreeBSD.org> Message-ID: <20081112220431.3e451c3e.trhodes@FreeBSD.org> On Wed, 12 Nov 2008 20:04:54 -0500 Tom Rhodes wrote: > On Wed, 12 Nov 2008 09:54:49 -0500 > "Bob Johnson" wrote: > > > The user has no control over whether the last sector of the drive is > > used for data. Data is scattered all over the drive, in something that > > resembles a random fashion, and I know of no reason the last sector is > > not just as likely to have data stored to it as any other sector on > > the drive (but I am certainly not an authority on the filesystem > > algorithms). > > > > I think a warning is very much in order (that there is a small chance > > that data will be lost by this procedure). > > > > - Bob > > > Don't Unix file systems attempt to lump data closer together > in order to reduce this fragmentation which scatters data > across the entire drive, making it unlikely to have data in > that last sector unless one went beyond the 8% boundry? Sorry, I really hope this didn't come off as rude. While I know the user has no control over where data is stored on the hard disk, I would also assume a warning about this to be in the manual page as well. It's very possible that the metadata is stored in a location not touchable by a filesystem. Thus, I have sent an email to Pawel for further examination. Thanks, > > > > > > > > On 11/12/08, Tom Rhodes wrote: > > > The following reply was made to PR docs/128804; it has been noted by GNATS. > > > > > > From: Tom Rhodes > > > To: Winder > > > Cc: freebsd-gnats-submit@FreeBSD.org > > > Subject: Re: docs/128804: Gmirror handbook instructions convert boot-drive > > > to gmirror, truncating last sector > > > Date: Wed, 12 Nov 2008 02:18:59 -0500 > > > > > > On Wed, 12 Nov 2008 01:21:55 GMT > > > Winder wrote: > > > > > > Hi, > > > > > > > > > > > > > > >Number: 128804 > > > > >Category: docs > > > > >Synopsis: Gmirror handbook instructions convert boot-drive to > > > gmirror, truncating last sector > > > > >Confidential: no > > > > >Severity: non-critical > > > > >Priority: medium > > > > >Responsible: freebsd-doc > > > > >State: open > > > > >Quarter: > > > > >Keywords: > > > > >Date-Required: > > > > >Class: doc-bug > > > > >Submitter-Id: current-users > > > > >Arrival-Date: Wed Nov 12 01:30:01 UTC 2008 > > > > >Closed-Date: > > > > >Last-Modified: > > > > >Originator: Winder > > > > >Release: 7.1-PRERELEASE > > > > >Organization: > > > > >Environment: > > > > FreeBSD DEV2 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Fri Nov 7 > > > 19:54:41 MST 2008 > > > windrider@DEV2:/usr/obj/usr/src/sys/packetcheckv1-fileserv amd64 > > > > >Description: > > > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html > > > > > > > > This geom mirroring documentation shows a way to convert the boot drive > > > into a gmirror raid. This guide misleads in assuming your whole drive has > > > not been used. > > > > > > > > The problem is that gmirror truncates the last sector of the drive for > > > metadata; thus, any data stored in that sector when adding the drive into > > > the RAID is lost. Sysinstall uses the entire drive by default. Following > > > these instructions, then, could cause loss of data or a corrupt partition, > > > as it will reach one sector beyond the end of the geom mirror device. > > > > > > > > mightn't it be better to make an example from a blank disk? > > > > > > I would think that converting the disk device to a software > > > RAID, at least the boot disk, would be the way most people > > > wanted to use it. And in most cases, I think that it's one > > > of the first things done during an installation - though, > > > YMMV. If the last sector is filled with user data - there > > > are larger problems, possibly, than just where GEOM places > > > metadata. > > > > > > If you feel a warning is required here, I'll gladly add one, > > > but it never crossed my mind initially that someone would > > > actually be using the last sector on the drive for data. > > > > > > Thanks, > > > > > > -- > > > Tom Rhodes > > > _______________________________________________ > > > freebsd-doc@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > > > > > > > -- > > -- Bob Johnson > > fbsdlists@gmail.com > > _______________________________________________ > > freebsd-doc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > > > -- > Tom Rhodes > -- Tom Rhodes From fender0107401 at gmail.com Wed Nov 12 20:13:33 2008 From: fender0107401 at gmail.com (Li) Date: Wed Nov 12 20:13:40 2008 Subject: Preface need update. In-Reply-To: <491B009E.8050408@gmail.com> References: <1226494693.1809.10.camel@localhost> <491B009E.8050408@gmail.com> Message-ID: <1226549600.1571.2.camel@localhost> Thank you very much for the reply, I will see it. :) fender On Wed, 2008-11-12 at 18:13 +0200, Manolis Kiagias wrote: > Li wrote: > > Hello Everyone: > > > > I am a FreeBSD fan, and I like reading the . > > > > Recently, I note that some new contents(chapter 20 File Systems Support, > > chapter 25 Dtrace, and chapter 26 Updating FreeBSD) added to the book. > > > > But the preface section have not corresponding introduction. > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html > > > > fender > > > You are right, the "Organization of this book" section jumps from > chapter 19 to chapter 21 and from 24 to 27, exactly the places of the > new chapters. > I will try to create a patch for this > > Thanks! > > manolis@ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081113/dca3f416/attachment.pgp From sonic2000gr at gmail.com Wed Nov 12 22:18:04 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Nov 12 22:18:11 2008 Subject: Preface need update. In-Reply-To: <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> Message-ID: <491BC698.6030701@gmail.com> Murray Stokely wrote: > Thanks Manolis. Maybe we should add a comment to the Makefile so that > when authors commit new chapters they remember to also update the > preface summary. Or alternatively, we could put some kind of one > sentence chapter description in of each chapter and pull > it out of each file dynamically when building the preface. I'd > probably recommend the low tech first suggestion as good enough. > > - Murray > > Yes, I think the Makefile solution is good enough. I always read the comments on important files, and hopefully most committers do, so it won't go unnoticed. Cheers, Manolis From sonic2000gr at gmail.com Thu Nov 13 06:30:04 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 13 06:30:10 2008 Subject: Preface need update. In-Reply-To: <20081112200755.66c52a48.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> Message-ID: <491C39E7.7040609@gmail.com> Tom Rhodes wrote: > On Wed, 12 Nov 2008 16:05:55 -0800 > "Murray Stokely" wrote: > > >> Thanks Manolis. Maybe we should add a comment to the Makefile so that >> when authors commit new chapters they remember to also update the >> preface summary. Or alternatively, we could put some kind of one >> sentence chapter description in of each chapter and pull >> it out of each file dynamically when building the preface. I'd >> probably recommend the low tech first suggestion as good enough. >> >> - Murray >> > > Yea, because I forget this every time I add a new chapter. :( > > > To take this idea one step further, I suggest we add the following comment to the Makefile: ----------------------------------------------------------------------------------------------------------------- To add a new chapter to the Handbook: - Update this Makefile, chapters.ent and book.sgml - Add a descriptive entry for the new chapter in preface/preface.sgml ----------------------------------------------------------------------------------------------------------------- Do you think this is good enough? Manolis From trhodes at FreeBSD.org Thu Nov 13 15:53:36 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Thu Nov 13 15:53:50 2008 Subject: Preface need update. In-Reply-To: <491C39E7.7040609@gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> Message-ID: <20081113185333.25a73ebf.trhodes@FreeBSD.org> On Thu, 13 Nov 2008 16:29:59 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > On Wed, 12 Nov 2008 16:05:55 -0800 > > "Murray Stokely" wrote: > > > > > >> Thanks Manolis. Maybe we should add a comment to the Makefile so that > >> when authors commit new chapters they remember to also update the > >> preface summary. Or alternatively, we could put some kind of one > >> sentence chapter description in of each chapter and pull > >> it out of each file dynamically when building the preface. I'd > >> probably recommend the low tech first suggestion as good enough. > >> > >> - Murray > >> > > > > Yea, because I forget this every time I add a new chapter. :( > > > > > > > To take this idea one step further, I suggest we add the following > comment to the Makefile: > > ----------------------------------------------------------------------------------------------------------------- > To add a new chapter to the Handbook: > > - Update this Makefile, chapters.ent and book.sgml > - Add a descriptive entry for the new chapter in preface/preface.sgml > ----------------------------------------------------------------------------------------------------------------- > > Do you think this is good enough? Yes. And I need to look at the "changes since the third edition" data as well. :) -- Tom Rhodes From joeb at a1poweruser.com Fri Nov 14 00:07:02 2008 From: joeb at a1poweruser.com (joeb) Date: Fri Nov 14 00:07:10 2008 Subject: updateing splash screen faq Message-ID: Would like to update this FAQ. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/x.html#INSTALL-SPLASH The current FAQ documentation on activating the boot splash screen is not up to date. It was written for FreeBSD 3.1 and is missing some undocumented functions. Change the FAQ to say; FreeBSD has a feature to allow the display of a "splash screen" in place of seeing the boot messages rolling by. This makes for a visually cleaner experience getting to the Xorg Desktop Display Manager logon screen and/or virtual console logon prompt. The "splash screen" function only supports 256 color bitmap (*.bmp) or ZSoft PCX (*.pcx) files. In addition, the splash image files must have a resolution of 320x200 or less to work because that is the default video support FreeBSD provides during the boot process. Your 320x200 "splash screen" image will be displayed as a small block in the center of a solid white background screen. If you want support for larger video resolutions up to the max of your video card you have to add VESA support by loading the VESA module during system boot. VESA support gives you the ability to display a "splash screen" image that fills the whole display screen. While the "splash screen" is being displayed during the booting process you can hit any keyboard key to return to the boot message display. The "splash screen" defaults to becoming your screen saver. After a time period of non-use your screen will change to the "splash screen" and cycles through steps of changing intensity of the image, from bright intensity to a very dark intensity and over again. You can override this default "splash screen" (screen saver) behavior by adding the saver= option (screen saver) statement in /etc/rc.conf. The saver= option has several built-in screen savers to choose from. Such as saver="warp". This default "splash screen" screen saver and /etc/rc.conf, saver= option screen saver only applies to virtual consoles. It has no effect on Xorg desktop display managers. At boot time you still see a few boot messages leading up to and including the boot options menu and the timed wait count down prompt before the "splash screen" is displayed. For default boot display resolution (256 color, 320x200 or less); Your "splash screen" (*.bmp) or (*.pcx) file has to be placed in the /boot directory. Edit /boot/loader.conf so it contains the following: bitmap_load="YES" bitmap_name="/boot/splash.bmp" or bitmap_name="/boot/splash.pcx" For larger video resolutions up to the max of your video card; Your "splash screen" (*.bmp) or (*.pcx) file has to be placed in the /boot directory. Edit /boot/loader.conf so it contains the following: vesa_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" or bitmap_name="/boot/splash.pcx" You are not restricted to using "splash" as the file name. You can name it anything you want as long as it's a .bmp or .pcx file type. Such as splash_640x400.bmp There are 2 another loader.conf options you may be interested in. Loader_logo="beastie" This will replace the default words "FREE BDS" which are displayed to the right of the boot menu with the colored beastie logo like releases in the past had. beastie_disable="YES" Will stop the boot options menu from being displayed. You will still get the timed wait count down prompt. Now all you need is a splash screen. For that you can surf on over to the gallery at http://www.baldwin.cx/splash/. From pgj at FreeBSD.org Fri Nov 14 00:23:41 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Nov 14 00:23:48 2008 Subject: updateing splash screen faq In-Reply-To: References: Message-ID: <491D3577.3090208@FreeBSD.org> joeb wrote: > Would like to update this FAQ. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/x.html#INSTALL-SPLASH > > The current FAQ documentation on activating the boot splash screen is not up > to date. It was written for FreeBSD 3.1 and is missing some undocumented > functions. Okay, thanks for the report! I will work on it, and let you know when it is fixed. Cheers, :g From joeb at a1poweruser.com Fri Nov 14 01:12:25 2008 From: joeb at a1poweruser.com (joeb) Date: Fri Nov 14 01:12:32 2008 Subject: updateing splash screen faq In-Reply-To: <491D3577.3090208@FreeBSD.org> Message-ID: Sorry just found another hidden function so corrected the faq I posted before. Change the FAQ to say; FreeBSD has a feature to allow the display of a "splash screen" in place of seeing the boot messages rolling by. This makes for a visually cleaner experience getting to the Xorg Desktop Display Manager logon screen and/or virtual console logon prompt. The "splash screen" function only supports (*.bmp) or (*.pcx) files of any resolution supported by VESA. An 320x200 "splash screen" image will be displayed as a small block in the center of a solid white background screen. An 640x400 or larger "splash screen" image fills the whole display screen. The "splash screen" function will interrogate the "splash screen" file pointed to by the (bitmap_name=) option and auto load VESA to support the required resolution for you. While the "splash screen" is being displayed during the booting process you can hit any keyboard key to return to the boot message display. The "splash screen" defaults to becoming your screen saver. After a time period of non-use your screen will change to the "splash screen" and cycles through steps of changing intensity of the image, from bright intensity to a very dark intensity and over again. You can override this default "splash" screen" (screen saver) behavior by adding the saver= option (screen saver) statement in /etc/rc.conf. The saver= option has several built-in screen savers to choose from. Such as saver="warp". This default "splash screen" screen saver and /etc/rc.conf, saver= option screen saver only applies to virtual consoles. It has no effect on Xorg desktop display managers. At boot time you still see a few boot messages leading up to and including the boot options menu and the timed wait count down prompt before the "splash screen" is displayed. To enable the "splash screen" function; Place your "splash screen" (*.bmp) or (*.pcx) file in the /boot directory. Edit /boot/loader.conf so it contains the following: bitmap_load="YES" bitmap_name="/boot/splash.bmp" or bitmap_name="/boot/splash.pcx" You are not restricted to using "splash" as the file name. You can name it anything you want as long as it's a .bmp or .pcx file type. Such as splash_640x400.bmp There are 2 another loader.conf options you may be interested in. Loader_logo="beastie" This will replace the default words "FREE BDS" which are displayed to the right of the boot menu with the colored beastie logo like releases in the past had. beastie_disable="YES" Will stop the boot options menu from being displayed. You will still get the timed wait count down prompt. Now all you need is a splash screen. For that you can surf on over to the gallery at http://www.baldwin.cx/splash/. From dovid.lubin at veryant.com Fri Nov 14 08:26:18 2008 From: dovid.lubin at veryant.com (Dovid Lubin) Date: Fri Nov 14 09:35:31 2008 Subject: what tool did you use Message-ID: <03E6D62726AA40068685998B0874EFDF@gwpc06> Hi, I like your online docs, especially the load speed. What tool(s) did you use to create the online docs? Dovid Lubin | Veryant 2415 East Camelback Road, Suite 700 Phoenix, AZ 85016 USA | www.veryant.com T +1.708.912.2723 | F +1.602.391.2415 From sonic2000gr at gmail.com Fri Nov 14 09:41:47 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Fri Nov 14 09:41:54 2008 Subject: what tool did you use In-Reply-To: <03E6D62726AA40068685998B0874EFDF@gwpc06> References: <03E6D62726AA40068685998B0874EFDF@gwpc06> Message-ID: <491DB853.4040700@gmail.com> Dovid Lubin wrote: > Hi, > > > > I like your online docs, especially the load speed. What tool(s) did you use > to create the online docs? > > Dovid Lubin | Veryant > 2415 East Camelback Road, Suite 700 Phoenix, AZ 85016 USA | > www.veryant.com > T +1.708.912.2723 | F +1.602.391.2415 > > > > Have a look at this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ and feel free to ask any questions you may have ;) From r.c.ladan at gmail.com Fri Nov 14 09:49:50 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Fri Nov 14 09:49:57 2008 Subject: what tool did you use In-Reply-To: <03E6D62726AA40068685998B0874EFDF@gwpc06> References: <03E6D62726AA40068685998B0874EFDF@gwpc06> Message-ID: <491DBA39.9060008@gmail.com> Dovid Lubin schreef: > Hi, > > > > I like your online docs, especially the load speed. What tool(s) did you use > to create the online docs? > /usr/ports/textproc/docproj see also http://www.freebsd.org/doc/en/books/fdp-primer/tools.html Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From pgj at FreeBSD.org Fri Nov 14 12:06:17 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Nov 14 12:06:28 2008 Subject: updateing splash screen faq In-Reply-To: References: Message-ID: <491DDA22.7070801@FreeBSD.org> Hi joeb, I started to review your proposed changes, and I have some comments: > "This makes for a visually cleaner experience getting to the Xorg > Desktop Display Manager logon screen and/or virtual console logon > prompt." Sorry, I do not understand this sentence. > The "splash screen" function only supports (*.bmp) or (*.pcx) files > of any resolution supported by VESA. An 320x200 "splash screen" image > will be displayed as a small block in the center of a solid white > background screen. An 640x400 or larger "splash screen" image fills > the whole display screen. The "splash screen" function will > interrogate the "splash screen" file pointed to by the (bitmap_name=) > option and auto load VESA to support the required resolution for you. > > [..] I do not think you should mention every detail. In my opinion, it would be better to put all the text into the Handbook, then reference it from the FAQ (if you want to write all these things down step by step). Or why do not simply reference the corresponding manual pages for example? I think your changes make the answer too long, a FAQ entry should be more compact, a quick way to answer a problem, as it is the original version. To be honest, I am reluctant a bit to include all of your text in the FAQ in the first round. I would prefer a simple fix to remove the /boot/loader.rc part and include some manual page references. Well, here is my recommendation: 11.18. How do I install a splash screen and where do I find them? FreeBSD have a feature to allow the display of "splash" screens during the boot messages. The splash screens currently must be a 256 color bitmap (*.BMP) or ZSoft PCX (*.PCX) file. In addition, they must have a resolution of 320x200 or less to work on standard VGA adapters. If you compile VESA support into your kernel (see vga(4)), then you can use larger bitmaps up to 1024x768. The actual VESA support can either be compiled directly into the kernel with the VESA kernel config option or by loading the VESA kernel module during bootup. To use a splash screen, you need to modify /boot/loader.conf to contain the following: splash_bmp_load="YES" bitmap_load="YES" This assumes you are using /boot/splash.bmp for your splash screen. If you would rather use a PCX file, copy it to /boot/splash.pcx, modify /boot/loader.conf to contain: splash_pcx_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.pcx" Now all you need is a splash screen. For that you can surf on over to the gallery at http://www.baldwin.cx/splash/. For further options, please see the splash(4), loader.conf(5) manual pages. Cheers, :g From fbsd1 at a1poweruser.com Sat Nov 15 02:02:01 2008 From: fbsd1 at a1poweruser.com (Fbsd1) Date: Sat Nov 15 02:02:15 2008 Subject: Adding splash screen section to handbook In-Reply-To: References: Message-ID: <491E9A3E.2070201@a1poweruser.com> Had to use my other email address so i could bottom post. > > -----Original Message----- > From: P?LI G?bor J?nos [mailto:pali.gabor@googlemail.com]On Behalf Of Gabor > PALI > Sent: Saturday, November 15, 2008 4:06 AM > To: joeb@a1poweruser.com > Cc: doc@FreeBSD.org > Subject: Re: updateing splash screen faq > > Hi joeb, > > I started to review your proposed changes, and I have some comments: > > >> "This makes for a visually cleaner experience getting to the X11 >> Desktop Display Manager login screen and/or virtual console login >> prompt." > > Sorry, I do not understand this sentence. > > There are 2 basic environments available in Freebsd, The first is the default command line environment which has 8 virtual consoles controlled by the F1 - F8 keys. When you boot the system you arrive at the F1 virtual console login prompt. The is the environment a user would see after a new install from cd. The second environment is the X11 Desktop environment. After a user installs Xorg and one of the desktop managers, gnome, kde, or Xfce like explained in the handbook they can launch the desktop from the command line by using the startx command. Some X11 users may select NOT to stop at the virtual console login prompt at boot time but go directlly to the X11 desktop. They would use the display manager of Xorg called xdm, or the the display manager of gnome called gdm or the the display manager of kde called kdm. These display managers basically provides a graphical login screen in place of the virtual console login prompt. In virtual console command line environment the splash screen would hide all the boot probe messages and startup messages before displaying the login prompt. In X11 environments the users would get a visually clearer system start up experience resembling something closer to what an ms/xp user would see. > > I do not think you should mention every detail. In my opinion, it would > be better to put all the text into the Handbook, then reference it from > the FAQ (if you want to write all these things down step by step). Or > why do not simply reference the corresponding manual pages for example? > > I think your changes make the answer too long, a FAQ entry should be > more compact, a quick way to answer a problem, as it is the original > version. To be honest, I am reluctant a bit to include all of > your text in the FAQ in the first round. > > I would prefer a simple fix to remove the /boot/loader.rc part and > include some manual page references. Well, here is my recommendation: > First of all, the handbook does not have any reference to the splash screen function. The only documentation on the splash screen is in the FAQ. You should know that all ready. I agree with you that the splash screen documentation should be removed from the FAQ and placed in the handbook. Complete and full documentation is what is needed and the handbook is the place it belongs. On that point I do not think the splash screen belongs under the section dealing with X11 because it really has nothing to do with X11. I think it should be in a new sub-section, in section "3.0 UNIX Basics" after 3.2 Virtual Consoles and Terminals, titled 3.3 Boot time Splash screen. So I have rewritten what I posted before and made some technical corrections and added some more explanation background text. If you check out the handbook Chapter 31 Firewalls you will see that I wrote the whole chapter. I don't have the time nor the patiences to work through the handbook SGML coding and approval process. So I am going to hand off this new handbook section to you to do as you want with it. Just give me my credit do as "Contributed by Joseph J. Barbish". Handbook Section 3.0 UNIX Basics - 3.3 Boot time Splash screen FreeBSD has a feature to allow the display of a "splash screen" in place of seeing the boot messages rolling by. This makes for a clearer visually experience getting to the legacy UNIX virtual console text login prompt and/or the X-Display Manager graphical login screen. There are 2 basic environments available in FreeBSD. The first is the default legacy UNIX virtual console text command line environment that has 8 virtual consoles controlled by the F1 - F8 keyboard keys. When you boot the system you arrive at the F1 virtual console text login prompt. The second environment is the X11 Desktop graphical environment. After a user installs X11. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-install.html And one of the graphical desktop managers, gnome, kde, or Xfce. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html They can launch the X11 desktop from the command line by using the startx command. Some X11 users may select NOT to stop at the virtual console login prompt at boot time, but go directly to the X11 desktop display manager's graphical login screen. They could use the display manager of Xorg called xdm, or the display manager of gnome called gdm or the display manager of kde called kdm or one of the other display managers provided in the ports system. These display managers basically provides a graphical login screen in place of the default legacy UNIX virtual console text login prompt and after a successful login, puts the user in their graphical windowed desktop. In the virtual console text command line environment the splash screen would hide all the boot probe messages and task startup messages before displaying the login prompt. In X11 environment the users would get a visually clearer system start up experience resembling something closer to what a (Microsoft Windows or non-unix type system) user would experience. 3.3.1 Splash Screen Function; The "splash screen" function only supports 256 color bitmap (*.bmp) or ZSoft PCX (*.pcx) files. In addition, the splash image files must have a resolution of 320x200 or less to work because that is the default video support FreeBSD provides. Your 320x200 "splash screen" image will be displayed as a small block in the center of a solid white background screen. If you want support for larger video resolutions up to the max of your video card you have to add VESA support by loading the VESA module during system boot. VESA support gives you the ability to display a "splash screen" image that fills the whole display screen. While the "splash screen" is being displayed during the booting process you can hit any keyboard key to return to the boot message display. The "splash screen" defaults to becoming your screen saver. After a time period of non-use your screen will change to the "splash screen" and cycles through steps of changing intensity of the image, from bright intensity to a very dark intensity and over again. You can override this default "splash screen" (screen saver) behavior by adding the saver= option (screen saver) statement in /etc/rc.conf. The saver= option has several built-in screen savers to choose from. Such as saver="warp". This default "splash screen" screen saver and /etc/rc.conf, saver= option screen saver only applies to virtual consoles. It has no effect on X11 desktop display managers. At boot time with the "splash screen" enabled you still see a few boot loader messages leading up to and including the boot options menu and the timed wait count down prompt before the "splash screen" is displayed. Sample splash screen files can be downloaded from the gallery at http://www.baldwin.cx/splash/. 3.3.2 Enabling the Splash Screen Function; Your "splash screen" (*.bmp) or (*.pcx) file has to be placed in the /boot directory. For default boot display resolution (256 color, 320x200 or less); Edit /boot/loader.conf so it contains the following: splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" For larger video resolutions up to the max of your video card; Edit /boot/loader.conf so it contains the following: vesa_load="YES" splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" The above assumes you are using /boot/splash.bmp for your splash screen. If you would rather use a PCX file, use these statements plus the vesa_load="YES" statement depending on the resolution. splash_pcx_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.pcx" You are not restricted to using "splash" as the file name. You can name it anything you want as long as it's a .bmp or .pcx file type. Such as splash_640x400.bmp or blue_wave.bmp. There are 2 another loader.conf options you may be interested in. beastie_disable="YES" Will stop the boot options menu from being displayed. You will still get the timed wait count down prompt. Even with the display of the boot options menu disabled, entering an 1-6 option selection at the timed wait count down prompt will enact that boot option. Loader_logo="beastie" This will replace the default words "FREE BDS" which are displayed to the right of the boot options menu with the colored beastie logo like releases in the past had. From www at FreeBSD.org Sun Nov 16 08:54:24 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Sun Nov 16 08:54:30 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200811161654.mAGGsNXD003505@www.freebsd.org> U relnotes6/man4/man4.i386/wl.4 U relnotes6/man4/man4.sparc64/Makefile U relnotes6/man4/man4.sparc64/auxio.4 U relnotes6/man4/man4.sparc64/central.4 U relnotes6/man4/man4.sparc64/clkbrd.4 U relnotes6/man4/man4.sparc64/creator.4 U relnotes6/man4/man4.sparc64/ebus.4 U relnotes6/man4/man4.sparc64/eeprom.4 U relnotes6/man4/man4.sparc64/fhc.4 U relnotes6/man4/man4.sparc64/machfb.4 U relnotes6/man4/man4.sparc64/ofw_console.4 U relnotes6/man4/man4.sparc64/openfirm.4 U relnotes6/man4/man4.sparc64/openprom.4 U relnotes6/man4/man4.sparc64/rtc.4 U relnotes6/man4/man4.sparc64/sbus.4 U relnotes6/man4/man4.sparc64/snd_audiocs.4 /bin/mkdir -p /w/www/build/doc/en_US.ISO8859-1/share/sgml env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/catalog-cwd.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog-common.xml file:///w/www/build/www/en/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs --param 'transtable.xml' "'/w/www/build/doc/share/sgml/transtable.xml'" --param 'transtable-target-element' "'country'" --param 'transtable-word-group' "'country'" --param 'transtable-mode' "'sortkey'" /w/www/build/doc/share/sgml/transtable-local.xsl /w/www/build/doc/share/sgml/mirrors.xml | env -i LANG="en_US.ISO8859-1" /usr/bin/sort -f > / w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort.tmp env -i /usr/bin/grep "^ /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort echo "" >> /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort env -i /usr/bin/awk '/@sortkey@/ {sub(/@sortkey@/, ++line); print;}' < /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort.tmp >> /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort echo '' >> /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/catalog-cwd.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog-common.xml file:///w/www/build/www/en/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs -o /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml --param 'transtable.xml' "'/w/www/build/doc/share/sgml/transtable.xml'" --param 'transtable-target-element' "'country'" --param 'transtable-word-group' "'country'" --param 'transtable-sortkey.xml' "'/w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort'" /w/www/build/doc/share/ sgml/transtable-local.xsl /w/www/build/doc/share/sgml/mirrors.xml /bin/rm -f /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort /w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml.sort.tmp install /w/www/build/www/share/sgml/catalog-cwd.xml /w/www/build/www/en/catalog-cwd.xml echo '' > /w/www/build/www/en/autogen.ent env SGML_CATALOG_FILES= XML_CATALOG_FILES="file:///w/www/build/www/en/catalog-cwd.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog.xml file:///w/www/build/doc/share/sgml/catalog-common.xml file:///w/www/build/www/en/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog.xml file:///w/www/build/www/share/sgml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --stringparam LOCALBASE /usr/local --stringparam WEB_PREFIX /w/www/build/www --nonet --catalogs -o index.html --param transtable.xml "'/w/www/build/doc/share/sgml/transtable.xml'" --param mirrors.xml "'/w/www/build/doc/en_US.ISO8859-1/share/sgml/mirrors.xml'" --param news.project.xml-master "'/w/www/build/www/share/sgml/news.xml'" --param news.project.xml "'/w/www/build/www/share/sgml/news.xml'" --param news.press.xml-master "'/w/www/build /www/share/sgml/press.xml'" --param news.press.xml "'/w/www/build/www/share/sgml/press.xml'" --param events.xml-master "'/w/www/build/www/share/sgml/events.xml'" --param events.xml "'/w/www/build/www/share/sgml/events.xml'" --param advisories.xml "'/w/www/build/www/share/sgml/advisories.xml'" --param notices.xml "'/w/www/build/www/share/sgml/notices.xml'" index.xsl /w/www/build/www/share/sgml/news.xml /w/www/build/www/share/sgml/news.xml:52: parser error : Opening and ending tag mismatch: p line 50 and event ^ /w/www/build/www/share/sgml/news.xml:53: parser error : Opening and ending tag mismatch: event line 41 and day ^ /w/www/build/www/share/sgml/news.xml:102: parser error : Opening and ending tag mismatch: day line 38 and month ^ /w/www/build/www/share/sgml/news.xml:805: parser error : Opening and ending tag mismatch: month line 35 and year ^ /w/www/build/www/share/sgml/news.xml:1616: parser error : Opening and ending tag mismatch: year line 32 and news ^ /w/www/build/www/share/sgml/news.xml:1617: parser error : Premature end of data in tag news line 25 ^ unable to parse /w/www/build/www/share/sgml/news.xml *** Error code 6 Stop in /w/www/build/www/en. 0.69 real 0.18 user 0.10 sys From pgj at FreeBSD.org Mon Nov 17 01:45:04 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Nov 17 01:45:11 2008 Subject: Adding splash screen section to handbook In-Reply-To: <491E9A3E.2070201@a1poweruser.com> References: <491E9A3E.2070201@a1poweruser.com> Message-ID: <49213D0B.4020404@FreeBSD.org> Dear Joe, >>> "This makes for a visually cleaner experience getting to the X11 >>> Desktop Display Manager login screen and/or virtual console >>> login prompt." >> >> Sorry, I do not understand this sentence. >> > [..] In X11 environments the users would get a visually clearer > system start up experience resembling something closer to what an > ms/xp user would see. Okay, thank you for the clarification. > First of all, the handbook does not have any reference to the splash > screen function. The only documentation on the splash screen is in > the FAQ. You should know that all ready. Yes, you are right. > I agree with you that the splash screen documentation should be > removed from the FAQ and placed in the handbook. Complete and full > documentation is what is needed and the handbook is the place it > belongs. On that point I do not think the splash screen belongs under > the section dealing with X11 because it really has nothing to do > with X11. I think it should be in a new sub-section, in section "3.0 > UNIX Basics" after 3.2 Virtual Consoles and Terminals, titled 3.3 > Boot time Splash screen. Oh, thank you for your contribution! > I don't have the time nor the patiences to work through the handbook > SGML coding and approval process. So I am going to hand off this new > handbook section to you to do as you want with it. Just give me my > credit do as "Contributed by Joseph J. Barbish". I will do the SGML coding and review your work. Thank you again. Cheers, :g From bugmaster at FreeBSD.org Mon Nov 17 03:06:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 17 03:06:36 2008 Subject: Current unassigned doc problem reports Message-ID: <200811171106.mAHB65qi081593@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/128816 doc [PATCH] Enhance the explanation of using of mount opti o docs/128804 doc Gmirror handbook instructions convert boot-drive to gm o docs/128768 doc Missing documentation about tmpfs mount options o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128325 doc README.snapshots still refers to snaphots as "alpha-te o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128129 doc Sysinstall color problem in xterm o docs/128128 doc Sysinstall not mentioned in 4.4 "Using the Packages Sy o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127923 doc Please mention qemu in the FreeBSD Handbook o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/127406 doc [patch] update umodem man page: Sony Ericsson W810i o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122470 doc [patch] exit status on fetch(1) manual page o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o 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 docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121197 doc [patch] edits to books/porters-handbook 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/120628 doc PAE documentation errror in handbook 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/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) s docs/119404 doc [request] events page should list only last 2 years wo o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu 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/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument 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/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported 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/112481 doc bug in ppp.linkup example 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/111263 doc [request] Information on $EDITOR variable in section 3 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/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout 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 o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n 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/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym 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/98759 doc [patch] sbp_targ(4) man page missing reference to devi 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/95139 doc FAQ to move filesystem to new disk fails: incorrect pe 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/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous 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/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI 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 o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt 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/47818 doc [patch] ln(1) manpage is confusing 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 o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. 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 173 problems total. From balusoft at gmail.com Mon Nov 17 21:47:38 2008 From: balusoft at gmail.com (balaji cherukuri) Date: Tue Nov 18 04:32:31 2008 Subject: Reg kernal internals Message-ID: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> Hi FreeBSD-Doc Team, I need freeBSD kernel internals, can you please provide any doc.? Thanks, Balaji C. From r.c.ladan at gmail.com Tue Nov 18 04:44:06 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Tue Nov 18 04:44:12 2008 Subject: Reg kernal internals In-Reply-To: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> References: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> Message-ID: 2008/11/18 balaji cherukuri : > Hi FreeBSD-Doc Team, > I need freeBSD kernel internals, can you please provide any doc.? > Yes, some pointers: - manual pages in category 9 describing kernel functions, see intro(9). - the kernel section in the developers handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel.html - the architecture handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/ - the FreeBSD kernel cross reference (processed source code): http://fxr.watson.org/ HTH, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From balusoft at gmail.com Tue Nov 18 04:53:51 2008 From: balusoft at gmail.com (balaji cherukuri) Date: Tue Nov 18 04:55:12 2008 Subject: Reg kernal internals In-Reply-To: References: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> Message-ID: <2e17cda30811180453x7f53daa6ua020eee70725235d@mail.gmail.com> ThanQ verymuch, Do you have any docs which will talk more about NULLFS, VFS and process structure. This would be a great help for me. Thanks, Balaji C. On Tue, Nov 18, 2008 at 6:14 PM, Rene Ladan wrote: > 2008/11/18 balaji cherukuri : > > Hi FreeBSD-Doc Team, > > I need freeBSD kernel internals, can you please provide any doc.? > > > Yes, some pointers: > - manual pages in category 9 describing kernel functions, see intro(9). > - the kernel section in the developers handbook: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel.html > - the architecture handbook: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/ > - the FreeBSD kernel cross reference (processed source code): > http://fxr.watson.org/ > > HTH, > Rene > -- > http://www.rene-ladan.nl/ > > GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 > (subkeys.pgp.net) > From r.c.ladan at gmail.com Tue Nov 18 06:23:05 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Tue Nov 18 06:23:11 2008 Subject: Reg kernal internals In-Reply-To: <2e17cda30811180453x7f53daa6ua020eee70725235d@mail.gmail.com> References: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> <2e17cda30811180453x7f53daa6ua020eee70725235d@mail.gmail.com> Message-ID: 2008/11/18 balaji cherukuri : > ThanQ verymuch, > Do you have any docs which will talk more about NULLFS, VFS and process > structure. > - 'apropos VFS' returns a bunch of VFS manual pages. - NULLFS has no manual pages, but you can look at the source in /usr/src/sys/fs/nullfs and /usr/src/sbin/mount_nullfs What exactly do you mean with 'process structure' ? schedulers? Rene > On Tue, Nov 18, 2008 at 6:14 PM, Rene Ladan wrote: >> >> 2008/11/18 balaji cherukuri : >> > Hi FreeBSD-Doc Team, >> > I need freeBSD kernel internals, can you please provide any doc.? >> > >> Yes, some pointers: >> - manual pages in category 9 describing kernel functions, see intro(9). >> - the kernel section in the developers handbook: >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel.html >> - the architecture handbook: >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/ >> - the FreeBSD kernel cross reference (processed source code): >> http://fxr.watson.org/ >> >> HTH, >> Rene >> -- >> http://www.rene-ladan.nl/ >> >> GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 >> (subkeys.pgp.net) > > -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From balusoft at gmail.com Tue Nov 18 08:31:20 2008 From: balusoft at gmail.com (balaji cherukuri) Date: Tue Nov 18 08:31:26 2008 Subject: Reg kernal internals In-Reply-To: References: <2e17cda30811172120w59e43980l77895345b7fce3c1@mail.gmail.com> <2e17cda30811180453x7f53daa6ua020eee70725235d@mail.gmail.com> Message-ID: <2e17cda30811180831v2c7fca2fle88f8919eb1b1229@mail.gmail.com> actually I need details regarding "struct proc", "struct ucred" and any/all other structures which will represent the process information and/or user credential information. And also how to use that structures. On Tue, Nov 18, 2008 at 7:53 PM, Rene Ladan wrote: > 2008/11/18 balaji cherukuri : > > ThanQ verymuch, > > Do you have any docs which will talk more about NULLFS, VFS and process > > structure. > > > - 'apropos VFS' returns a bunch of VFS manual pages. > - NULLFS has no manual pages, but you can look at the source in > /usr/src/sys/fs/nullfs > and /usr/src/sbin/mount_nullfs > > What exactly do you mean with 'process structure' ? schedulers? > > Rene > > > On Tue, Nov 18, 2008 at 6:14 PM, Rene Ladan wrote: > >> > >> 2008/11/18 balaji cherukuri : > >> > Hi FreeBSD-Doc Team, > >> > I need freeBSD kernel internals, can you please provide any doc.? > >> > > >> Yes, some pointers: > >> - manual pages in category 9 describing kernel functions, see intro(9). > >> - the kernel section in the developers handbook: > >> > >> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel.html > >> - the architecture handbook: > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/ > >> - the FreeBSD kernel cross reference (processed source code): > >> http://fxr.watson.org/ > >> > >> HTH, > >> Rene > >> -- > >> http://www.rene-ladan.nl/ > >> > >> GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 > >> (subkeys.pgp.net) > > > > > > > > -- > http://www.rene-ladan.nl/ > > GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 > (subkeys.pgp.net) > From www at FreeBSD.org Tue Nov 18 09:23:53 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Tue Nov 18 09:24:08 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200811181723.mAIHNreT032068@www.freebsd.org> /bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum install -C -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-simple-vol.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum /bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum install -C -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-striped-vol.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum /bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum install -C -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-striped.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/handbook.html -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/index.html ===> doc/books/pmake (install) install -C -o www -g wwwadm -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake install -C -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake install -C -o www -g wwwadm -m 444 book.html /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake install -C -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake ===> doc/books/porters-handbook (install) install -C -o www -g wwwadm -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www -g wwwadm -m 444 imagelib/callouts/1.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/2.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/3.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/4.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/5.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/6.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/7.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/8.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/9.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/10.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 book.html /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www -g wwwadm -m 444 imagelib/callouts/1.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/2.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/3.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/4.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/5.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/6.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/7.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/8.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/9.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www -g wwwadm -m 444 imagelib/callouts/10.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts /w/www/build/www/en/doc/faq -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/faq /w/www/build/www/en/doc/handbook -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook /w/www/build/www/en/doc/en -> /w/www/build/www/en/doc/en_US.ISO8859-1 /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/pgpkeys/pgpkeys-developers.sgml:459:7:E: general entity "pgpkey.pho" not defined and no default entity /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/pgpkeys/pgpkeys-developers.sgml:460:11:E: end tag for "SECT2" which is not finished *** Error code 1 Stop in /w/www/build/www/en/doc. *** Error code 1 (ignored) *** Error code 1 Stop in /w/www/build/www/en. 100.25 real 56.60 user 30.05 sys From linimon at FreeBSD.org Tue Nov 18 11:26:43 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue Nov 18 11:26:54 2008 Subject: docs/128968: [patch] rwlock(9) man page typo Message-ID: <200811181926.mAIJQgmw076273@freefall.freebsd.org> Old Synopsis: rwlock man page typo New Synopsis: [patch] rwlock(9) man page typo Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Tue Nov 18 19:26:14 UTC 2008 Responsible-Changed-Why: docs PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=128968 From maxim at FreeBSD.org Tue Nov 18 12:15:47 2008 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Tue Nov 18 12:15:53 2008 Subject: docs/128968: [patch] rwlock(9) man page typo Message-ID: <200811182015.mAIKFkd1014442@freefall.freebsd.org> Synopsis: [patch] rwlock(9) man page typo State-Changed-From-To: open->patched State-Changed-By: maxim State-Changed-When: Tue Nov 18 20:12:03 UTC 2008 State-Changed-Why: The issue is already fixed in HEAD. I'll MFC the delta to RELENG_7 after 7.0-RELEASE if pjd@ doesn't do before me. http://www.freebsd.org/cgi/query-pr.cgi?pr=128968 From blackend at freebsd.org Tue Nov 18 12:30:04 2008 From: blackend at freebsd.org (Marc Fonvieille) Date: Tue Nov 18 12:30:14 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87k5bc4ovw.fsf@kobe.laptop> References: <200811090424.mA94OlN6087438@repoman.freebsd.org> <20081109084551.GB1058@gothic.blackend.org> <87hc6gbz3t.fsf@kobe.laptop> <20081109192507.GB1030@gothic.blackend.org> <87k5bc4ovw.fsf@kobe.laptop> Message-ID: <20081118203001.GB1030@gothic.blackend.org> On Sun, Nov 09, 2008 at 10:37:23PM +0200, Giorgos Keramidas wrote: > On Sun, 9 Nov 2008 20:25:07 +0100, Marc Fonvieille wrote: > >> Maybe something like this? > >> > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css.diff > >> > >> I don't really like ``width: 800px;'' in our current stylesheet. In > >> wide monitors, or with lagre font sizes, explicitly using pixels for the > >> width of document elements means that the reader may end up with stuff > >> like this screenshot: > >> > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-bug.png > >> > >> The current elements stand out too much for my taste too, so I > >> removed ``background-color: #DEE3E7;'' from , but added a border > >> (similar to the one of elements) to . > >> > >> You can see the effect of the stylesheet changes of `css.diff' in the > >> two sets of pages: > >> > >> [before] > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/install-pre.html > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/x-config.html > >> > >> [after] > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/install-pre.html > >> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/x-config.html > > > > The new x-config.html is fine for me. > > For the new install-pre.html, the way is > > rendered looks oldish, maybe using the same scheme as for > > might do the trick. > > The bold red text is kind of `old school' for me too. I'll wait to see > if there are flames^W^H err, objections about the rest and update the > style too :) > Maybe it's time to close the thread and commit something, at least the width: 85% fix and perhaps even the rest... -- Marc From blackend at FreeBSD.org Tue Nov 18 13:19:08 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Tue Nov 18 13:19:15 2008 Subject: Tag slip Message-ID: <20081118211905.GD1030@gothic.blackend.org> Hello, Just a quick note to say that doc/ tree has been retagged for both 6.4-R and 7.1-R. That means all changes since previous tagging operation will be part of these releases. -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081118/89fa09d7/attachment.pgp From sonic2000gr at gmail.com Tue Nov 18 13:25:12 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Nov 18 13:25:18 2008 Subject: Tag slip In-Reply-To: <20081118211905.GD1030@gothic.blackend.org> References: <20081118211905.GD1030@gothic.blackend.org> Message-ID: <492332B1.6090004@gmail.com> Marc Fonvieille wrote: > Hello, > > Just a quick note to say that doc/ tree has been retagged for both 6.4-R > and 7.1-R. That means all changes since previous tagging operation will > be part of these releases. > > That's actually good news for the Greek Documentation Project ;) Lots of fixes (and entire chapters) have been committed since the previous tagging. Thanks for the update! manolis@ From tabthorpe at FreeBSD.org Tue Nov 18 13:40:03 2008 From: tabthorpe at FreeBSD.org (Thomas Abthorpe) Date: Tue Nov 18 13:40:09 2008 Subject: docs/128973: Spelling mistake in ntp-keygen.8 Message-ID: <200811182133.mAILXCTn075642@www.freebsd.org> >Number: 128973 >Category: docs >Synopsis: Spelling mistake in ntp-keygen.8 >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: Tue Nov 18 21:40:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Thomas Abthorpe >Release: 7-STABLE >Organization: FreeBSD.GoodKing.Ca >Environment: FreeBSD goodking.goodking.ca 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Nov 10 00:08:20 EST 2008 root@goodking.goodking.ca:/usr/obj/usr/src/sys/GOODKING i386 >Description: Lists recommended path to generated keys as /ust/local/etc >How-To-Repeat: >Fix: Patch attached with submission follows: --- /usr/local/tinderbox/jails/7-STABLE/src/usr.sbin/ntp/doc/ntp-keygen.8 2006-09-30 15:07:03.000000000 -0400 +++ /usr/src/usr.sbin/ntp/doc/ntp-keygen.8 2008-11-18 16:27:30.000000000 -0500 @@ -126,7 +126,7 @@ program is logged in directly as root. The recommended procedure is change to the keys directory, usually -.Pa /ust/local/etc , +.Pa /usr/local/etc , then run the program. When run for the first time, or if all >Release-Note: >Audit-Trail: >Unformatted: From danger at FreeBSD.org Tue Nov 18 15:35:14 2008 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Tue Nov 18 15:35:20 2008 Subject: docs/128973: Spelling mistake in ntp-keygen.8 Message-ID: <200811182335.mAINZDHu066382@freefall.freebsd.org> Synopsis: Spelling mistake in ntp-keygen.8 Responsible-Changed-From-To: freebsd-doc->danger Responsible-Changed-By: danger Responsible-Changed-When: Tue Nov 18 23:35:03 UTC 2008 Responsible-Changed-Why: Take http://www.freebsd.org/cgi/query-pr.cgi?pr=128973 From fbsdlists at gmail.com Wed Nov 19 10:32:07 2008 From: fbsdlists at gmail.com (Bob Johnson) Date: Wed Nov 19 10:32:13 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector In-Reply-To: <20081112220431.3e451c3e.trhodes@FreeBSD.org> References: <200811120800.mAC80Cm2038380@freefall.freebsd.org> <54db43990811120654l213596f1j844c3f185c3eb577@mail.gmail.com> <20081112200454.3ddb9b89.trhodes@FreeBSD.org> <20081112220431.3e451c3e.trhodes@FreeBSD.org> Message-ID: <54db43990811191032qb4462d6y10104e63c8671298@mail.gmail.com> On 11/12/08, Tom Rhodes wrote: > On Wed, 12 Nov 2008 20:04:54 -0500 > Tom Rhodes wrote: > >> On Wed, 12 Nov 2008 09:54:49 -0500 >> "Bob Johnson" wrote: >> >> > The user has no control over whether the last sector of the drive is >> > used for data. Data is scattered all over the drive, in something that >> > resembles a random fashion, and I know of no reason the last sector is >> > not just as likely to have data stored to it as any other sector on >> > the drive (but I am certainly not an authority on the filesystem >> > algorithms). >> > >> > I think a warning is very much in order (that there is a small chance >> > that data will be lost by this procedure). >> > >> > - Bob >> Well, I got distracted and never replied to this, but since the PR is still open, here's more: >> >> Don't Unix file systems attempt to lump data closer together >> in order to reduce this fragmentation which scatters data >> across the entire drive, making it unlikely to have data in >> that last sector unless one went beyond the 8% boundry? In general, no, it is pretty much the opposite. It would be more accurate to view it as intentionally fragmenting the drive in a controlled way so that the problems caused by fragmentation are minimized. The heuristic used probably tends to favor leaving the last sector of the filesystem empty longer than most other sectors, but it can still be used long before the entire filesystem is full (assuming there isn't some other consideration I don't know about -- I'm no expert on the details of the algorithms used). This is because, in general, the goal of the filesystem layout scheme is to avoid completely filling any physical region (cylinder group) if it can be avoided, so it spreads data out among the cylinder groups. This strategy helps keep large chunks of empty space available, so that new data has a good chance of being stored on contiguous sectors. The blocks that belong to one file will tend to be physically close to each other so that the file can be read quickly, but the files themselves end up scattered all over the disk. There are a few ways in which a file can end up being stored on a specific cylinder group, but the result is that the group at the physical end of the filesystem is likely to be used long before the entire filesystem is full. If it happens that the files stored on the last cylinder group are large, or there are many of them, it is possible to write the last sector long before the entire filesystem is full. There is some degree of random chance in the process. -- Bob Johnson fbsdlists@gmail.com From pgj at FreeBSD.org Thu Nov 20 03:08:04 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu Nov 20 03:08:11 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <491E9A3E.2070201@a1poweruser.com> References: <491E9A3E.2070201@a1poweruser.com> Message-ID: <492544FC.9090504@FreeBSD.org> Dear members, A few days ago we received a generous contribution from Joseph J. Barbish on using splash screens in FreeBSD [1]. Initially, it started as a fix for the FAQ, but after I suggested Joe to insert the descriptive part of his work into the Handbook, he offered an entire section for referencing from the FAQ. He recommended to put this section into Chapter 3 ("UNIX Basics"), but I would like to receive some comments on this before I start to integrate it into that chapter. (Do you think it is needed, if yes, it is a good place for that and so on.) Of course, after it has been moved to the Handbook, it would shorten the corresponding FAQ entry to contain only the necessary references and to avoid unnecessary duplication of the content. Thank you for your comments in advance. Cheers, :g [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html From keramida at freebsd.org Thu Nov 20 06:01:53 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Nov 20 06:02:21 2008 Subject: cvs commit: doc/share/misc docbook.css Message-ID: <87bpwa4slo.fsf@kobe.laptop> On Tue, 18 Nov 2008 21:30:01 +0100, Marc Fonvieille wrote: >On Sun, Nov 09, 2008 at 10:37:23PM +0200, Giorgos Keramidas wrote: >>>> [before] >>>> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/install-pre.html >>>> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-old/x-config.html >>>> >>>> [after] >>>> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/install-pre.html >>>> http://people.freebsd.org/~keramida/bsd-css/2008.11.09/css-new/x-config.html >>> >>> The new x-config.html is fine for me. >>> For the new install-pre.html, the way is >>> rendered looks oldish, maybe using the same scheme as for >>> might do the trick. >> >> The bold red text is kind of `old school' for me too. I'll wait to see >> if there are flames^W^H err, objections about the rest and update the >> style too :) > > Maybe it's time to close the thread and commit something, at least the > width: 85% fix and perhaps even the rest... Yep. I didn't see any major objections to the [after] style, so I will commit the new style-sheet later today. From DS at praxisvermittlung24.de Thu Nov 20 06:20:12 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 06:20:19 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <492544FC.9090504@FreeBSD.org> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> Message-ID: <49256AE4.3030604@praxisvermittlung24.de> Gabor PALI wrote: > Dear members, > > > A few days ago we received a generous contribution from Joseph J. > Barbish on using splash screens in FreeBSD [1]. Initially, it started > as a fix for the FAQ, but after I suggested Joe to insert the > descriptive part of his work into the Handbook, he offered an entire > section for referencing from the FAQ. > > He recommended to put this section into Chapter 3 ("UNIX Basics"), but I > would like to receive some comments on this before I start to integrate > it into that chapter. (Do you think it is needed, if yes, it is a good > place for that and so on.) Of course, after it has been moved to the > Handbook, it would shorten the corresponding FAQ entry to contain only > the necessary references and to avoid unnecessary duplication of the > content. > > > Thank you for your comments in advance. Dear Gabor, thank you and Joseph for your work! Please go for it, a lot of desktop users want it. Chapter 3 seems appropriate for me. Wouldn't it be nice to have some FreeBSD specific splash screens in the artwork section or elsewhere and you mention it in your section? Maybe it would be good idea to ask on advocacy for proposals? Best regards, Daniel From sonic2000gr at gmail.com Thu Nov 20 06:26:45 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 20 06:26:51 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <492544FC.9090504@FreeBSD.org> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> Message-ID: <4925739E.4060208@gmail.com> Gabor PALI wrote: > Dear members, > > > A few days ago we received a generous contribution from Joseph J. > Barbish on using splash screens in FreeBSD [1]. Initially, it started > as a fix for the FAQ, but after I suggested Joe to insert the > descriptive part of his work into the Handbook, he offered an entire > section for referencing from the FAQ. > > He recommended to put this section into Chapter 3 ("UNIX Basics"), but I > would like to receive some comments on this before I start to integrate > it into that chapter. (Do you think it is needed, if yes, it is a good > place for that and so on.) Of course, after it has been moved to the > Handbook, it would shorten the corresponding FAQ entry to contain only > the necessary references and to avoid unnecessary duplication of the > content. > > > Thank you for your comments in advance. > > > Cheers, > :g > > [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html > I followed the discussion and I think this is useful info that should be part of the documentation. The submitted text looks ok more or less (and I am quite sure you will it touch it up anyway ;) ). I am more concerned about the placement of this info though. Supposedly the first part of the Handbook is more or less introductory and designed to teach fundamental UNIX concepts. Granted, this rule is violated a few times, some parts are way more advanced and refer to later sections. However I believe we should keep chapter 3 focused on exactly the title: UNIX basics. Imagine yourself being a beginner and trying to find some useful info on basic UNIX commands. Would you rather find the discussion of a splash screen useful? I doubt it. What's more, you would not be able to fully understand what is going on. There is another possible section for this info: Chapter 12 (boot). If you come to think about it, the splash screen is more related to booting than actual system operation (the "basics"). In fact there is a section on loader.conf in chapter 12 and I think this info could be adjusted to fit the chapter nicely. There are could also be other places, but this is the only that comes to mind at the moment. One could also argue we need something of a "Misc settings" chapter, where all this useful but maybe hard to categorize stuff would go. But then again, this maybe the role of the FAQ. By the way, the above is just a suggestion, if the general consensus is to merge it into the Basics chapter, I won't object :) manolis@ From pgj at FreeBSD.org Thu Nov 20 08:16:56 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu Nov 20 08:17:03 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49256AE4.3030604@praxisvermittlung24.de> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> Message-ID: <49258D61.9060206@FreeBSD.org> Daniel Seuffert wrote: > Please go for it, a lot of desktop users want it. Thanks for the support :) > Chapter 3 seems appropriate for me. Well, I would accept Manolis' suggestion, but I will write about it in a direct reply. > Wouldn't it be nice to have some FreeBSD specific splash screens in > the artwork section or elsewhere and you mention it in your section? Artwork section? Do you mean creating an artwork section? > Maybe it would be good idea to ask on advocacy for proposals? Do you mean the freebsd-advocacy mailing list? What kind of proposals? Cheers, :g From pgj at FreeBSD.org Thu Nov 20 08:46:41 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu Nov 20 08:46:48 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925739E.4060208@gmail.com> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <4925739E.4060208@gmail.com> Message-ID: <49259459.1000700@FreeBSD.org> Manolis Kiagias wrote: > I followed the discussion and I think this is useful info that should > be part of the documentation. Thanks for the support. > The submitted text looks ok more or less (and I am quite sure you > will it touch it up anyway ;) ). Yep, it is very probable :) > I am more concerned about the placement of this info though. Initially, I had the very same concern about this contribution, but when I looked through Chapter 3, I found a lot of FreeBSD-specific information in it. > Supposedly the first part of the Handbook is more or less > introductory and designed to teach fundamental UNIX concepts. [..] But I have to agree with you. > Would you rather find the discussion of a splash screen useful? I > doubt it. What's more, you would not be able to fully understand what > is going on. There is another possible section for this info: Chapter > 12 (boot). Hm, I think it is a great idea! What do you think of appending it to section ``12.3 The Boot Manager and Boot Stages'' (as a sub-section)? > There are could also be other places, but this is the only that comes > to mind at the moment. One could also argue we need something of a > "Misc settings" chapter, where all this useful but maybe hard to > categorize stuff would go. But then again, this maybe the role of the > FAQ. I recommended to not to include the entire text in the FAQ itself for Joe because I think the FAQ should be "compact and quick". Joe wrote a complete and precise description on the topic, so it should be placed in the Handbook and referenced (only) from the FAQ. I am trying to defer the introduction of a potential "Misc Settings" chapter until we really encounter things that do not fit in the actual contents or outgrew their limits. > By the way, the above is just a suggestion, if the general consensus > is to merge it into the Basics chapter, I won't object :) At the moment, I would prefer to inject it into Section 12.3. If there is no explicit objection in the next few days, I will try start to work on its SGML version and send a patch to the list for review. Comments are still welcome. Cheers, :g From sonic2000gr at gmail.com Thu Nov 20 08:58:04 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 20 08:58:10 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49259459.1000700@FreeBSD.org> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <4925739E.4060208@gmail.com> <49259459.1000700@FreeBSD.org> Message-ID: <49259716.6040207@gmail.com> Gabor PALI wrote: > > >> Would you rather find the discussion of a splash screen useful? I >> doubt it. What's more, you would not be able to fully understand what >> is going on. There is another possible section for this info: Chapter >> 12 (boot). >> > > Hm, I think it is a great idea! What do you think of appending it to > section ``12.3 The Boot Manager and Boot Stages'' (as a sub-section)? > > > Yes, exactly what I had in mind. I was reading section 12.3.3 where /boot/loader is discussed while writing the previous reply. >> There are could also be other places, but this is the only that comes >> to mind at the moment. One could also argue we need something of a >> "Misc settings" chapter, where all this useful but maybe hard to >> categorize stuff would go. But then again, this maybe the role of the >> FAQ. >> > > I recommended to not to include the entire text in the FAQ itself for > Joe because I think the FAQ should be "compact and quick". Joe wrote a > complete and precise description on the topic, so it should be placed in > the Handbook and referenced (only) from the FAQ. > > I am trying to defer the introduction of a potential "Misc Settings" > chapter until we really encounter things that do not fit in the actual > contents or outgrew their limits. > > > I agree. Most of the misc topics still seem to fit in the standard chapters if studied carefully. >> By the way, the above is just a suggestion, if the general consensus >> is to merge it into the Basics chapter, I won't object :) >> > > At the moment, I would prefer to inject it into Section 12.3. If there > is no explicit objection in the next few days, I will try start to work > on its SGML version and send a patch to the list for review. > Well, let's call all the "usual suspects" ;) to comment... From DS at praxisvermittlung24.de Thu Nov 20 09:04:03 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 09:04:10 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49258D61.9060206@FreeBSD.org> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <49258D61.9060206@FreeBSD.org> Message-ID: <4925987F.2020300@praxisvermittlung24.de> Gabor PALI wrote: > Daniel Seuffert wrote: >> Please go for it, a lot of desktop users want it. > > Thanks for the support :) > > >> Chapter 3 seems appropriate for me. > > Well, I would accept Manolis' suggestion, but I will write about it in a > direct reply. I wouldn't object any other place because users will find it any way if searching by Google or any other means. >> Wouldn't it be nice to have some FreeBSD specific splash screens in >> the artwork section or elsewhere and you mention it in your section? > > Artwork section? Do you mean creating an artwork section? No, not necessarily. We have http://www.freebsd.org/art.html Imho we should have "official" FreeBSD splashs there too in any form. It's some sort of marketing and imho there should be at least three of them available. Imagine both FreeBSD distributions (PC-BSD and DesktopBSD) have their specific boot splashs enabled by default because most desktop users want it. Disclaimer: I'm NOT propagating shipping FreeBSD with a default splash! >> Maybe it would be good idea to ask on advocacy for proposals? > > Do you mean the freebsd-advocacy mailing list? What kind of proposals? Yes, I mean't freebsd-advocacy. If we want to ease using splashs why don't we ask our users providing some examples? Or even write a news announcing an "splash contest"? - Daniel From gnemmi at gmail.com Thu Nov 20 09:15:34 2008 From: gnemmi at gmail.com (Gonzalo Nemmi) Date: Thu Nov 20 09:15:42 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49256AE4.3030604@praxisvermittlung24.de> References: <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> Message-ID: <200811201515.31281.gnemmi@gmail.com> On Thursday 20 November 2008 11:49:24 am Daniel Seuffert wrote: > Gabor PALI wrote: > > Dear members, > > > > > > A few days ago we received a generous contribution from Joseph J. > > Barbish on using splash screens in FreeBSD [1]. Initially, it started > > as a fix for the FAQ, but after I suggested Joe to insert the > > descriptive part of his work into the Handbook, he offered an entire > > section for referencing from the FAQ. > > > > He recommended to put this section into Chapter 3 ("UNIX Basics"), but I > > would like to receive some comments on this before I start to integrate > > it into that chapter. (Do you think it is needed, if yes, it is a good > > place for that and so on.) Of course, after it has been moved to the > > Handbook, it would shorten the corresponding FAQ entry to contain only > > the necessary references and to avoid unnecessary duplication of the > > content. > > > > > > Thank you for your comments in advance. > > Dear Gabor, > > thank you and Joseph for your work! > > Please go for it, a lot of desktop users want it. > > Chapter 3 seems appropriate for me. > > Wouldn't it be nice to have some FreeBSD specific splash > screens in the artwork section or elsewhere and you mention > it in your section? Maybe it would be good idea to ask > on advocacy for proposals? Indeed .. I've been thinking about this for a long time ... there's a severe lack of FreeBSD related artwork .. so much so that I was thinking on paying some artists I know to come up with a series of FreeBSD boot/splash/backgrounds/sleeves and CD-DVD cover images ... Peer Schaefer's work (CD-ROM labels, sleeves and cases for FreeBSD) is impecable, but he seems to be the only one working on FreeBSD art: http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork/ I translated the text on his CD-ROM labels, sleeves and cases for FreeBSD into spanish in order to get some "globalized" advocacy: http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork-es/ On august this year, Daniel Seuffert was asking for posters to use at events: http://lists.freebsd.org/pipermail/freebsd-advocacy/2008-August/003701.html I believe OpenBSD sets the standar on this one .. with new OpenBSD related art on every release, posters, t-shirts, lots of stickers and so on ... http://images.kd85.com/notforsale/blowfishsticker.pdf http://eurobsd.org/2005-WhatTheHack/reports/wvdputte-20050730/tn/DSC03983.JPG.html http://images.kd85.com/notforsale/openbsd-en-flyer-1.9.3.v8.pdf http://kd85.com/notforsale.html I've been hesitant on wether or not to bring this issue up on freebsd-advocacy but if I'm not alone on this one, I'm willing to do so. I thought that Anton Gural's work would have put an end to this ... but it did not :( > Best regards, Daniel > > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" Just in case you are wondering; yes .. i know this mail should have been sent to advocacy@ .. but the thread started in here ... so .. if I'm not alone and there's consensus, I'll resend it to advocacy@ when the time comes. Regards -- Blessings Gonzalo Nemmi From sonic2000gr at gmail.com Thu Nov 20 09:19:10 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 20 09:19:16 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925987F.2020300@praxisvermittlung24.de> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <49258D61.9060206@FreeBSD.org> <4925987F.2020300@praxisvermittlung24.de> Message-ID: <49259C07.4030700@gmail.com> Daniel Seuffert wrote: > >>> Wouldn't it be nice to have some FreeBSD specific splash screens in >>> the artwork section or elsewhere and you mention it in your section? >> >> Artwork section? Do you mean creating an artwork section? > > No, not necessarily. We have > > http://www.freebsd.org/art.html > > Imho we should have "official" FreeBSD splashs there too in any form. > It's some sort of marketing and imho there should > be at least three of them available. This is a nice idea actually, and I don't think anyone would object. That's the purpose of the artwork section. We would need some original work though. There are some FreeBSD splash screens floating around the Net, but we really need new stuff. > > Imagine both FreeBSD distributions (PC-BSD and DesktopBSD) have their > specific boot splashs enabled by default because > most desktop users want it. > > Disclaimer: I'm NOT propagating shipping FreeBSD with a default splash! > >>> Maybe it would be good idea to ask on advocacy for proposals? >> >> Do you mean the freebsd-advocacy mailing list? What kind of proposals? > > Yes, I mean't freebsd-advocacy. If we want to ease using splashs why > don't we ask our users providing some examples? > Or even write a news announcing an "splash contest"? > freebsd-advocacy would be a good place to ask people for artwork. Though the list is rather low volume, and it may go unnoticed. Another idea would be a post in the new forums.freebsd.org, where it will be seen by lots of (real world) users. I am quite certain you will find more people with artistic talents there, than these lists. (Technology oriented people can rarely draw a straight line ;) ) From gnemmi at gmail.com Thu Nov 20 09:32:57 2008 From: gnemmi at gmail.com (Gonzalo Nemmi) Date: Thu Nov 20 09:33:04 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925739E.4060208@gmail.com> References: <492544FC.9090504@FreeBSD.org> <4925739E.4060208@gmail.com> Message-ID: <200811201452.16175.gnemmi@gmail.com> On Thursday 20 November 2008 12:26:38 pm Manolis Kiagias wrote: > Gabor PALI wrote: > > Dear members, > > > > > > A few days ago we received a generous contribution from Joseph J. > > Barbish on using splash screens in FreeBSD [1]. Initially, it started > > as a fix for the FAQ, but after I suggested Joe to insert the > > descriptive part of his work into the Handbook, he offered an entire > > section for referencing from the FAQ. > > > > He recommended to put this section into Chapter 3 ("UNIX Basics"), but I > > would like to receive some comments on this before I start to integrate > > it into that chapter. (Do you think it is needed, if yes, it is a good > > place for that and so on.) Of course, after it has been moved to the > > Handbook, it would shorten the corresponding FAQ entry to contain only > > the necessary references and to avoid unnecessary duplication of the > > content. > > > > > > Thank you for your comments in advance. > > > > > > Cheers, > > > > :g > > > > [1] > > http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html > > I followed the discussion and I think this is useful info that should be > part of the documentation. The submitted text looks ok more or less (and > I am quite sure you will it touch it up anyway ;) ). I am more concerned > about the placement of this info though. > Supposedly the first part of the Handbook is more or less introductory > and designed to teach fundamental UNIX concepts. Granted, this rule is > violated a few times, some parts are way more advanced and refer to > later sections. However I believe we should keep chapter 3 focused on > exactly the title: UNIX basics. Imagine yourself being a beginner and > trying to find some useful info on basic UNIX commands. Would you rather > find the discussion of a splash screen useful? I doubt it. What's more, > you would not be able to fully understand what is going on. > There is another possible section for this info: Chapter 12 (boot). If > you come to think about it, the splash screen is more related to booting > than actual system operation (the "basics"). In fact there is a section > on loader.conf in chapter 12 and I think this info could be adjusted to > fit the chapter nicely. First: Thanks Joseph and Gabor for your work. Now, and for what is worth, I've been following the thread too and 1) Yes .. I think it's Joseph's work should be available on the Handbook. 2) I agree with Manolis for the same reasons he exposed. Even if Chapter 3 is a good enough place to insert this info, Chapter 12 seems to be an even better one. > There are could also be other places, but this is the only that comes to > mind at the moment. One could also argue we need something of a "Misc > settings" chapter, where all this useful but maybe hard to categorize > stuff would go. But then again, this maybe the role of the FAQ. > > By the way, the above is just a suggestion, if the general consensus is > to merge it into the Basics chapter, I won't object :) > > manolis@ > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" Once again, thank you Joseph and Gabor for your work .. and just in case, a friend and I have fooled around with splash screen and boot splash a not so long time ago .. in case you are interested (discussion is in spanish but C code is not =P ): http://www.penguinpower.com.ar/foro/viewtopic.php?t=2494 http://www.penguinpower.com.ar/foro/viewtopic.php?t=2493 Regards -- Blessings Gonzalo Nemmi From DS at praxisvermittlung24.de Thu Nov 20 10:53:19 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 10:53:27 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49259C07.4030700@gmail.com> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <49258D61.9060206@FreeBSD.org> <4925987F.2020300@praxisvermittlung24.de> <49259C07.4030700@gmail.com> Message-ID: <4925B21B.2030703@praxisvermittlung24.de> Manolis Kiagias wrote: > Daniel Seuffert wrote: >> don't we ask our users providing some examples? >> Or even write a news announcing an "splash contest"? >> > > freebsd-advocacy would be a good place to ask people for artwork. Though > the list is rather low volume, and it may go unnoticed. Another idea > would be a post in the new forums.freebsd.org, where it will be seen by > lots of (real world) users. I am quite certain you will find more > people with artistic talents there, than these lists. (Technology > oriented people can rarely draw a straight line ;) ) Posting it in forums.freebsd.org is REALLY a good idea! - Daniel From sonic2000gr at gmail.com Thu Nov 20 10:59:37 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 20 10:59:43 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925B21B.2030703@praxisvermittlung24.de> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <49258D61.9060206@FreeBSD.org> <4925987F.2020300@praxisvermittlung24.de> <49259C07.4030700@gmail.com> <4925B21B.2030703@praxisvermittlung24.de> Message-ID: <4925B393.1060009@gmail.com> Daniel Seuffert wrote: > Manolis Kiagias wrote: >> Daniel Seuffert wrote: >>> don't we ask our users providing some examples? >>> Or even write a news announcing an "splash contest"? >>> >> >> freebsd-advocacy would be a good place to ask people for artwork. Though >> the list is rather low volume, and it may go unnoticed. Another idea >> would be a post in the new forums.freebsd.org, where it will be seen by >> lots of (real world) users. I am quite certain you will find more >> people with artistic talents there, than these lists. (Technology >> oriented people can rarely draw a straight line ;) ) > > > Posting it in forums.freebsd.org is REALLY a good idea! > > - Daniel > Well, I just did actually: http://forums.freebsd.org/showthread.php?t=403 So let's continue the discussion there ;) From kurin at delete.org Thu Nov 20 11:01:54 2008 From: kurin at delete.org (Toby Burress) Date: Thu Nov 20 11:02:01 2008 Subject: some more errors In-Reply-To: <87iqqifj18.fsf@rubin.l4b.de> References: <87iqqifj18.fsf@rubin.l4b.de> Message-ID: <20081120185607.GB60958@lithium.delete.org> On Thu, Nov 20, 2008 at 05:40:03PM +0100, Dieter Kluenter wrote: > Hi, > now reading > http://www.freebsd.org/doc/en/articles/ldap-auth/secure.html > > there are better ways to model this sort of access control (example 8 > and example 9) man slapd.access(5) describes a 'privilege model' that > is more applicable. Your examples are not wrong but only state of the > art in 1998, and OpenLDAP has been developed actively since then. heh, you think that's bad, you should see the tree I inherited in my current job. I'll see if I can rework that section. > > The examaple 10 creating a management group, is absolutely bogus. > The attribute type memberuid has syntax IA5string, but your example > shows attribute values of distinguishedName syntax. I believe that is a result of my understanding of the way pam_ldap handled memberUid on FreeBSD. Basically, if you have a group, and you only want members of that group to be able to auth via PAM, you need the entire DN in that group's memberUid attributes. I show this in 3.1.1 of the article. From kurin at delete.org Thu Nov 20 11:06:54 2008 From: kurin at delete.org (Toby Burress) Date: Thu Nov 20 11:07:00 2008 Subject: LDAP Authentication In-Reply-To: <87myfufl8u.fsf@rubin.l4b.de> References: <87myfufl8u.fsf@rubin.l4b.de> Message-ID: <20081120184803.GA60958@lithium.delete.org> On Thu, Nov 20, 2008 at 04:52:17PM +0100, Dieter Kluenter wrote: > Hi, > I just stumpled upon > http://www.freebsd.org/doc/en/articles/ldap-auth/client.html > > In examples 7 you are presenting a ruby script to modify a > userpassword. In this script you use some sort of ldapmodify to change > the password value. This is a NO NO. Never modify a password this > way and please do not propagate this. > The proper way is to call the extended operation passwordModify > (RFC-3062). The shell script of example 6 calls ldappasswd(1), which > calls this extended operation. Unfortunately it doesn't look like ruby-ldap supports RFC-3062. This specific example, iirc, was adapted from a script I wrote to modify passwords in an Active Directory server, which requires a specific (crazy) kind of ldapmodify. However, from the RFC it looks like this extension is specifically to allow the directory to manage the password backend even when such backend isn't the directory itself (which my article doesn't cover). While I'll add a section about this and the passwordModify operation, I think it is not terrible to use ldapModify to change passwords, as long as (a) the users are in fact kept in the directory, and (b) the admin is aware that he'll have to change his scripts if that changes in the future. From DS at praxisvermittlung24.de Thu Nov 20 11:20:23 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 11:20:29 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <200811201515.31281.gnemmi@gmail.com> References: <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <200811201515.31281.gnemmi@gmail.com> Message-ID: <4925B4C8.8080306@praxisvermittlung24.de> Gonzalo Nemmi wrote: >> Wouldn't it be nice to have some FreeBSD specific splash >> screens in the artwork section or elsewhere and you mention >> it in your section? Maybe it would be good idea to ask >> on advocacy for proposals? > > Indeed .. I've been thinking about this for a long time ... there's a severe > lack of FreeBSD related artwork .. so much so that I was thinking on paying > some artists I know to come up with a series of FreeBSD > boot/splash/backgrounds/sleeves and CD-DVD cover images ... > > Peer Schaefer's work (CD-ROM labels, sleeves and cases for FreeBSD) is > impecable, but he seems to be the only one working on FreeBSD art: > > http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork/ > > I translated the text on his CD-ROM labels, sleeves and cases for FreeBSD into > spanish in order to get some "globalized" advocacy: > > http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork-es/ I suggest you have a look at: http://misc.allbsd.de/CD-Stuff/ You can find any CD-/DVD-label I have ever produced for an event and afaik there's every BSD you might need (if I have forgotten something please let me know). > On august this year, Daniel Seuffert was asking for posters to use at events: > > http://lists.freebsd.org/pipermail/freebsd-advocacy/2008-August/003701.html Yes, that was me. We have 2 posters available now: http://misc.allbsd.de/Poster/FreeBSD-Blue-PosterA2.tif (designed by Aron Schlesinger) http://misc.allbsd.de/Poster/beastie_end.pdf (designed by Lars Engels aka lme@FreeBSD.org) I want to have more posters (5 or more) if possible > I believe OpenBSD sets the standar on this one .. with new OpenBSD related art > on every release, posters, t-shirts, lots of stickers and so on ... no doubt > I've been hesitant on wether or not to bring this issue up on freebsd-advocacy > but if I'm not alone on this one, I'm willing to do so. we should pick up the idea from Manolis with the new forum imho as well as advocacy > I thought that Anton Gural's work would have put an end to this ... but it did > not :( artwork is a never ending story, you cannot have to much of it... On a side note: Just in case you haven't seen it yet: We have a lot of flyers available in English, French, German http://misc.allbsd.de/Flyer/FreeBSD/ Maybe somebody is willing to translate to Spanish? ;-) - Daniel From sonic2000gr at gmail.com Thu Nov 20 11:34:29 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Nov 20 11:34:35 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925B4C8.8080306@praxisvermittlung24.de> References: <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <200811201515.31281.gnemmi@gmail.com> <4925B4C8.8080306@praxisvermittlung24.de> Message-ID: <4925BBBB.1090307@gmail.com> Daniel Seuffert wrote: > > artwork is a never ending story, you cannot have to much of it... > > On a side note: > Just in case you haven't seen it yet: We have a lot of flyers > available in English, French, German > > http://misc.allbsd.de/Flyer/FreeBSD/ > > Maybe somebody is willing to translate to Spanish? ;-) > > - Daniel Thanks for posting the links! This is really nice work. I will consider translating some of this to Greek too. I've started a thread on the forum for collecting this stuff, and will keep notes so we can decide how to deal with it. Either link to it from the website, create a new page or whatever. From DS at praxisvermittlung24.de Thu Nov 20 11:52:23 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 11:52:29 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925BBBB.1090307@gmail.com> References: <492544FC.9090504@FreeBSD.org> <49256AE4.3030604@praxisvermittlung24.de> <200811201515.31281.gnemmi@gmail.com> <4925B4C8.8080306@praxisvermittlung24.de> <4925BBBB.1090307@gmail.com> Message-ID: <4925BFF3.9010207@praxisvermittlung24.de> Manolis Kiagias schrieb: > Daniel Seuffert wrote: >> >> artwork is a never ending story, you cannot have to much of it... >> >> On a side note: >> Just in case you haven't seen it yet: We have a lot of flyers >> available in English, French, German >> >> http://misc.allbsd.de/Flyer/FreeBSD/ >> >> Maybe somebody is willing to translate to Spanish? ;-) >> >> - Daniel > > Thanks for posting the links! This is really nice work. I will consider > translating some of this to Greek too. > I've started a thread on the forum for collecting this stuff, and will > keep notes so we can decide how to deal with it. Either link to it from > the website, create a new page or whatever. Hi Manolis, created directories for gr ;-) If you need any help or an account to directly upload any files please let me know. Please note the font used in all flyers (headlines are in VGA Rounded by Volkswagen AG, free for non-commercial use) is Gentium for a good reason: There are greek fonts as well as kyrillic etc. ;-) Thank you for opening the thread! Best regards, Daniel From dieter at dkluenter.de Thu Nov 20 12:40:59 2008 From: dieter at dkluenter.de (Dieter Kluenter) Date: Thu Nov 20 12:41:07 2008 Subject: some more errors In-Reply-To: <20081120185607.GB60958@lithium.delete.org> (Toby Burress's message of "Thu, 20 Nov 2008 13:56:07 -0500") References: <87iqqifj18.fsf@rubin.l4b.de> <20081120185607.GB60958@lithium.delete.org> Message-ID: <87bpwa167e.fsf@rubin.l4b.de> Toby Burress writes: > On Thu, Nov 20, 2008 at 05:40:03PM +0100, Dieter Kluenter wrote: >> Hi, >> now reading >> http://www.freebsd.org/doc/en/articles/ldap-auth/secure.html >> >> there are better ways to model this sort of access control (example 8 >> and example 9) man slapd.access(5) describes a 'privilege model' that >> is more applicable. Your examples are not wrong but only state of the >> art in 1998, and OpenLDAP has been developed actively since then. > > heh, you think that's bad, you should see the tree I inherited in > my current job. I can imagine :-) > > I'll see if I can rework that section. This would be great. >> The examaple 10 creating a management group, is absolutely bogus. >> The attribute type memberuid has syntax IA5string, but your example >> shows attribute values of distinguishedName syntax. > > I believe that is a result of my understanding of the way pam_ldap > handled memberUid on FreeBSD. Basically, if you have a group, and > you only want members of that group to be able to auth via PAM, you > need the entire DN in that group's memberUid attributes. I show > this in 3.1.1 of the article. PAM can be configured to look either for groupOfNames member groupOfUniqueNames uniqueMember posixGroup memberUid All three attribute types have different syntaxes and values. Just as a request from my side, doen't use groupOfUniqueNames unless you have read and understood RFC-4517, section 3.3.21, and you really want to implement it. -Dieter -- Dieter Kl?nter | Systemberatung http://www.dpunkt.de/buecher/2104.html sip: +49.180.1555.7770535 GPG Key ID:8EF7B6C6 53?08'09,95"N 10?08'02,42"E From dieter at dkluenter.de Thu Nov 20 12:43:56 2008 From: dieter at dkluenter.de (Dieter Kluenter) Date: Thu Nov 20 12:44:02 2008 Subject: LDAP Authentication In-Reply-To: <20081120184803.GA60958@lithium.delete.org> (Toby Burress's message of "Thu, 20 Nov 2008 13:48:03 -0500") References: <87myfufl8u.fsf@rubin.l4b.de> <20081120184803.GA60958@lithium.delete.org> Message-ID: <87bpwatanr.fsf@rubin.l4b.de> Toby Burress writes: > On Thu, Nov 20, 2008 at 04:52:17PM +0100, Dieter Kluenter wrote: >> Hi, >> I just stumpled upon >> http://www.freebsd.org/doc/en/articles/ldap-auth/client.html >> >> In examples 7 you are presenting a ruby script to modify a >> userpassword. In this script you use some sort of ldapmodify to change >> the password value. This is a NO NO. Never modify a password this >> way and please do not propagate this. >> The proper way is to call the extended operation passwordModify >> (RFC-3062). The shell script of example 6 calls ldappasswd(1), which >> calls this extended operation. > > Unfortunately it doesn't look like ruby-ldap supports RFC-3062. > This specific example, iirc, was adapted from a script I wrote to > modify passwords in an Active Directory server, which requires a > specific (crazy) kind of ldapmodify. I gave up unsing ruby, as the 2 available modules, net-ldap and ruby-ldap are not actively maintained. As far as I remember both modules were able to call controls. AD doesn't store passwords, authentication is handeled by kerberos. At least the few AD's I had to integrate. > > However, from the RFC it looks like this extension is specifically > to allow the directory to manage the password backend even when > such backend isn't the directory itself (which my article doesn't > cover). While I'll add a section about this and the passwordModify > operation, I think it is not terrible to use ldapModify to change > passwords, as long as (a) the users are in fact kept in the directory, > and (b) the admin is aware that he'll have to change his scripts > if that changes in the future. Well you may do what ever you want in your own network, but as a official FreeBSD publication, it should refer to the standards and best practice rules. This documentation is aimed at people who are new to FreeBSD and to OpenLDAP and it should be our mutual aim to present samples best practice and compliance. We at OpenLDAP suffer from bad written docs that are spread all over the net. -Dieter -- Dieter Kl?nter | Systemberatung http://www.dpunkt.de/buecher/2104.html sip: +49.180.1555.7770535 GPG Key ID:8EF7B6C6 53?08'09,95"N 10?08'02,42"E From gnemmi at gmail.com Thu Nov 20 13:21:49 2008 From: gnemmi at gmail.com (Gonzalo Nemmi) Date: Thu Nov 20 13:21:56 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <4925B4C8.8080306@praxisvermittlung24.de> References: <200811201515.31281.gnemmi@gmail.com> <4925B4C8.8080306@praxisvermittlung24.de> Message-ID: <200811201921.43412.gnemmi@gmail.com> On Thursday 20 November 2008 5:04:40 pm Daniel Seuffert wrote: > Gonzalo Nemmi wrote: > >> Wouldn't it be nice to have some FreeBSD specific splash > >> screens in the artwork section or elsewhere and you mention > >> it in your section? Maybe it would be good idea to ask > >> on advocacy for proposals? > > > > Indeed .. I've been thinking about this for a long time ... there's a > > severe lack of FreeBSD related artwork .. so much so that I was thinking > > on paying some artists I know to come up with a series of FreeBSD > > boot/splash/backgrounds/sleeves and CD-DVD cover images ... > > > > Peer Schaefer's work (CD-ROM labels, sleeves and cases for FreeBSD) is > > impecable, but he seems to be the only one working on FreeBSD art: > > > > http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork/ > > > > I translated the text on his CD-ROM labels, sleeves and cases for FreeBSD > > into spanish in order to get some "globalized" advocacy: > > > > http://www.wolldingwacht.de/foss/freebsd/cdrom-artwork-es/ > > I suggest you have a look at: > http://misc.allbsd.de/CD-Stuff/ > > You can find any CD-/DVD-label I have ever produced for an > event and afaik there's every BSD you might need (if I have > forgotten something please let me know). You don't have an idea how much time I spent looking for those CD-/DVD-labels ... Finally .. there they are !! _Thank_You_! If you ever come up with some CD/DVD sleeves and cases, just let me know and I'll do the spanish translation :) ... and .. ahm .. DragonFlyBSD seems to be missing ;) > > On august this year, Daniel Seuffert was asking for posters to use at > > events: > > > > http://lists.freebsd.org/pipermail/freebsd-advocacy/2008-August/003701.ht > >ml > > Yes, that was me. We have 2 posters available now: > http://misc.allbsd.de/Poster/FreeBSD-Blue-PosterA2.tif > (designed by Aron Schlesinger) > > http://misc.allbsd.de/Poster/beastie_end.pdf > (designed by Lars Engels aka lme@FreeBSD.org) > > I want to have more posters (5 or more) if possible > > > I believe OpenBSD sets the standar on this one .. with new OpenBSD > > related art on every release, posters, t-shirts, lots of stickers and so > > on ... > > no doubt > > > I've been hesitant on wether or not to bring this issue up on > > freebsd-advocacy but if I'm not alone on this one, I'm willing to do so. > > we should pick up the idea from Manolis with the new forum > imho as well as advocacy You guys lead, I'll follow :) > > I thought that Anton Gural's work would have put an end to this ... but > > it did not :( > > artwork is a never ending story, you cannot have to much of > it... > > On a side note: > Just in case you haven't seen it yet: We have a lot of > flyers available in English, French, German > > http://misc.allbsd.de/Flyer/FreeBSD/ > > Maybe somebody is willing to translate to Spanish? ;-) Will do ;) > - Daniel > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" Regards -- Blessings Gonzalo Nemmi From gamato at users.sf.net Thu Nov 20 13:22:38 2008 From: gamato at users.sf.net (martinko) Date: Thu Nov 20 13:22:50 2008 Subject: Adding splash screen section to handbook In-Reply-To: <491E9A3E.2070201@a1poweruser.com> References: <491E9A3E.2070201@a1poweruser.com> Message-ID: Fbsd1 wrote: > Had to use my other email address so i could bottom post. > >> >> -----Original Message----- >> From: P?LI G?bor J?nos [mailto:pali.gabor@googlemail.com]On Behalf Of >> Gabor >> PALI >> Sent: Saturday, November 15, 2008 4:06 AM >> To: joeb@a1poweruser.com >> Cc: doc@FreeBSD.org >> Subject: Re: updateing splash screen faq >> >> Hi joeb, >> >> I started to review your proposed changes, and I have some comments: >> >> >>> "This makes for a visually cleaner experience getting to the X11 >>> Desktop Display Manager login screen and/or virtual console login >>> prompt." >> >> Sorry, I do not understand this sentence. >> >> > > There are 2 basic environments available in Freebsd, The first is the > default command line environment which has 8 virtual consoles controlled > by the F1 - F8 keys. When you boot the system you arrive at the F1 > virtual console login prompt. The is the environment a user would see > after a new install from cd. The second environment is the X11 Desktop > environment. After a user installs Xorg and one of the desktop managers, > gnome, kde, or Xfce like explained in the handbook they can launch the > desktop from the command line by using the startx command. Some X11 > users may select NOT to stop at the virtual console login prompt at boot > time but go directlly to the X11 desktop. They would use the display > manager of Xorg called xdm, or the the display manager of gnome called > gdm or the the display manager of kde called kdm. These display managers > basically provides a graphical login screen in place of the virtual > console login prompt. > > In virtual console command line environment the splash screen would hide > all the boot probe messages and startup messages before displaying the > login prompt. > > In X11 environments the users would get a visually clearer system start > up experience resembling something closer to what an ms/xp user would see. > >> >> I do not think you should mention every detail. In my opinion, it would >> be better to put all the text into the Handbook, then reference it from >> the FAQ (if you want to write all these things down step by step). Or >> why do not simply reference the corresponding manual pages for example? >> >> I think your changes make the answer too long, a FAQ entry should be >> more compact, a quick way to answer a problem, as it is the original >> version. To be honest, I am reluctant a bit to include all of >> your text in the FAQ in the first round. >> >> I would prefer a simple fix to remove the /boot/loader.rc part and >> include some manual page references. Well, here is my recommendation: >> > > First of all, the handbook does not have any reference to the splash > screen function. The only documentation on the splash screen is in the > FAQ. You should know that all ready. I agree with you that the splash > screen documentation should be removed from the FAQ and placed in the > handbook. Complete and full documentation is what is needed and the > handbook is the place it belongs. On that point I do not think the > splash screen belongs under the section dealing with X11 because it > really has nothing to do with X11. I think it should be in a new > sub-section, in section "3.0 UNIX Basics" after 3.2 Virtual Consoles and > Terminals, titled 3.3 Boot time Splash screen. > > So I have rewritten what I posted before and made some technical > corrections and added some more explanation background text. If you > check out the handbook Chapter 31 Firewalls you will see that I wrote > the whole chapter. I don't have the time nor the patiences to work > through the handbook SGML coding and approval process. So I am going to > hand off this new handbook section to you to do as you want with it. > Just give me my credit do as "Contributed by Joseph J. Barbish". > > > > > Handbook Section 3.0 UNIX Basics - 3.3 Boot time Splash screen > > > FreeBSD has a feature to allow the display of a "splash screen" in place > of seeing the boot messages rolling by. This makes for a clearer > visually experience getting to the legacy UNIX virtual console text > login prompt and/or the X-Display Manager graphical login screen. > > There are 2 basic environments available in FreeBSD. The first is the > default legacy UNIX virtual console text command line environment that > has 8 virtual consoles controlled by the F1 - F8 keyboard keys. When you > boot the system you arrive at the F1 virtual console text login prompt. > The second environment is the X11 Desktop graphical environment. After a > user installs X11. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-install.html > > And one of the graphical desktop managers, gnome, kde, or Xfce. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html > > They can launch the X11 desktop from the command line by using the > startx command. Some X11 users may select NOT to stop at the virtual > console login prompt at boot time, but go directly to the X11 desktop > display manager's graphical login screen. They could use the display > manager of Xorg called xdm, or the display manager of gnome called gdm > or the display manager of kde called kdm or one of the other display > managers provided in the ports system. These display managers basically > provides a graphical login screen in place of the default legacy UNIX > virtual console text login prompt and after a successful login, puts the > user in their graphical windowed desktop. > > In the virtual console text command line environment the splash screen > would hide all the boot probe messages and task startup messages before > displaying the login prompt. > > In X11 environment the users would get a visually clearer system start > up experience resembling something closer to what a (Microsoft Windows > or non-unix type system) user would experience. > > > 3.3.1 Splash Screen Function; > > The "splash screen" function only supports 256 color bitmap (*.bmp) or > ZSoft PCX (*.pcx) files. In addition, the splash image files must have a > resolution of 320x200 or less to work because that is the default video > support FreeBSD provides. Your 320x200 "splash screen" image will be > displayed as a small block in the center of a solid white background > screen. > > If you want support for larger video resolutions up to the max of your > video card you have to add VESA support by loading the VESA module > during system boot. VESA support gives you the ability to display a > "splash screen" image that fills the whole display screen. > > While the "splash screen" is being displayed during the booting process > you can hit any keyboard key to return to the boot message display. > > The "splash screen" defaults to becoming your screen saver. After a time > period of non-use your screen will change to the "splash screen" and > cycles through steps of changing intensity of the image, from bright > intensity to a very dark intensity and over again. You can override this > default "splash screen" (screen saver) behavior by adding the saver= > option (screen saver) statement in /etc/rc.conf. The saver= option has > several built-in screen savers to choose from. Such as saver="warp". > This default "splash screen" screen saver and /etc/rc.conf, saver= > option screen saver only applies to virtual consoles. It has no effect > on X11 desktop display managers. > > At boot time with the "splash screen" enabled you still see a few boot > loader messages leading up to and including the boot options menu and > the timed wait count down prompt before the "splash screen" is displayed. > > Sample splash screen files can be downloaded from the gallery at > http://www.baldwin.cx/splash/. > > > 3.3.2 Enabling the Splash Screen Function; > > Your "splash screen" (*.bmp) or (*.pcx) file has to be placed in the > /boot directory. > > For default boot display resolution (256 color, 320x200 or less); > Edit /boot/loader.conf so it contains the following: > splash_bmp_load="YES" > bitmap_load="YES" > bitmap_name="/boot/splash.bmp" > > > For larger video resolutions up to the max of your video card; > Edit /boot/loader.conf so it contains the following: > vesa_load="YES" > splash_bmp_load="YES" > bitmap_load="YES" > bitmap_name="/boot/splash.bmp" > > > The above assumes you are using /boot/splash.bmp for your splash screen. > If you would rather use a PCX file, use these statements plus the > vesa_load="YES" statement depending on the resolution. > splash_pcx_load="YES" > bitmap_load="YES" > bitmap_name="/boot/splash.pcx" > > You are not restricted to using "splash" as the file name. You can name > it anything you want as long as it's a .bmp or .pcx file type. Such as > splash_640x400.bmp or blue_wave.bmp. > > > There are 2 another loader.conf options you may be interested in. > > beastie_disable="YES" > Will stop the boot options menu from being displayed. > You will still get the timed wait count down prompt. > Even with the display of the boot options menu disabled, entering an 1-6 > option selection at the timed wait count down prompt will enact that > boot option. > > Loader_logo="beastie" > This will replace the default words "FREE BDS" which are displayed to > the right of the boot options menu with the colored beastie logo like > releases in the past had. > Hi, As I've just replied to original thread: IIRC even with VESA there's a limit of 1024x768 for boot splash images. You may want to mention sysutils/bsd-splash-changer port with which you can have splash image chosen from your collection randomly at each boot. M. From gamato at users.sf.net Thu Nov 20 13:22:39 2008 From: gamato at users.sf.net (martinko) Date: Thu Nov 20 13:22:50 2008 Subject: updateing splash screen faq In-Reply-To: <491DDA22.7070801@FreeBSD.org> References: <491DDA22.7070801@FreeBSD.org> Message-ID: Gabor PALI wrote: > Hi joeb, > > I started to review your proposed changes, and I have some comments: > > >> "This makes for a visually cleaner experience getting to the Xorg >> Desktop Display Manager logon screen and/or virtual console logon >> prompt." > > Sorry, I do not understand this sentence. > > >> The "splash screen" function only supports (*.bmp) or (*.pcx) files >> of any resolution supported by VESA. An 320x200 "splash screen" image >> will be displayed as a small block in the center of a solid white >> background screen. An 640x400 or larger "splash screen" image fills >> the whole display screen. The "splash screen" function will >> interrogate the "splash screen" file pointed to by the (bitmap_name=) >> option and auto load VESA to support the required resolution for you. >> >> [..] > > I do not think you should mention every detail. In my opinion, it would > be better to put all the text into the Handbook, then reference it from > the FAQ (if you want to write all these things down step by step). Or > why do not simply reference the corresponding manual pages for example? > > I think your changes make the answer too long, a FAQ entry should be > more compact, a quick way to answer a problem, as it is the original > version. To be honest, I am reluctant a bit to include all of > your text in the FAQ in the first round. > > I would prefer a simple fix to remove the /boot/loader.rc part and > include some manual page references. Well, here is my recommendation: > > > 11.18. How do I install a splash screen and where do I find them? > > FreeBSD have a feature to allow the display of "splash" screens during > the boot messages. The splash screens currently must be a 256 color > bitmap (*.BMP) or ZSoft PCX (*.PCX) file. In addition, they must have a > resolution of 320x200 or less to work on standard VGA adapters. If you > compile VESA support into your kernel (see vga(4)), then you can use > larger bitmaps up to 1024x768. The actual VESA support can either be > compiled directly into the kernel with the VESA kernel config option or > by loading the VESA kernel module during bootup. > > To use a splash screen, you need to modify /boot/loader.conf to contain > the following: > > splash_bmp_load="YES" > bitmap_load="YES" > > This assumes you are using /boot/splash.bmp for your splash screen. If > you would rather use a PCX file, copy it to /boot/splash.pcx, modify > /boot/loader.conf to contain: > > splash_pcx_load="YES" > bitmap_load="YES" > bitmap_name="/boot/splash.pcx" > > Now all you need is a splash screen. For that you can surf on over to > the gallery at http://www.baldwin.cx/splash/. For further options, > please see the splash(4), loader.conf(5) manual pages. > > > Cheers, > :g > Hi, IIRC even with VESA there's a limit of 1024x768 for boot splash images. You may want to mention sysutils/bsd-splash-changer port with which you can have splash image chosen randomly from your collection. M. From gnemmi at gmail.com Thu Nov 20 13:23:03 2008 From: gnemmi at gmail.com (Gonzalo Nemmi) Date: Thu Nov 20 13:23:10 2008 Subject: Add a Splash Screen Section to the Handbook? Message-ID: <200811201922.58163.gnemmi@gmail.com> On Thursday 20 November 2008 12:26:38 pm Manolis Kiagias wrote: > Gabor PALI wrote: > > Dear members, > > > > > > A few days ago we received a generous contribution from Joseph J. > > Barbish on using splash screens in FreeBSD [1]. Initially, it started > > as a fix for the FAQ, but after I suggested Joe to insert the > > descriptive part of his work into the Handbook, he offered an entire > > section for referencing from the FAQ. > > > > He recommended to put this section into Chapter 3 ("UNIX Basics"), but I > > would like to receive some comments on this before I start to integrate > > it into that chapter. (Do you think it is needed, if yes, it is a good > > place for that and so on.) Of course, after it has been moved to the > > Handbook, it would shorten the corresponding FAQ entry to contain only > > the necessary references and to avoid unnecessary duplication of the > > content. > > > > > > Thank you for your comments in advance. > > > > > > Cheers, > > > > :g > > > > [1] > > http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html > > I followed the discussion and I think this is useful info that should be > part of the documentation. The submitted text looks ok more or less (and > I am quite sure you will it touch it up anyway ;) ). I am more concerned > about the placement of this info though. > Supposedly the first part of the Handbook is more or less introductory > and designed to teach fundamental UNIX concepts. Granted, this rule is > violated a few times, some parts are way more advanced and refer to > later sections. However I believe we should keep chapter 3 focused on > exactly the title: UNIX basics. Imagine yourself being a beginner and > trying to find some useful info on basic UNIX commands. Would you rather > find the discussion of a splash screen useful? I doubt it. What's more, > you would not be able to fully understand what is going on. > There is another possible section for this info: Chapter 12 (boot). If > you come to think about it, the splash screen is more related to booting > than actual system operation (the "basics"). In fact there is a section > on loader.conf in chapter 12 and I think this info could be adjusted to > fit the chapter nicely. First: Thanks Joseph and Gabor for your work. Now, and for what is worth, I've been following the thread too and 1) Yes .. I think it's Joseph's work should be available on the Handbook. 2) I agree with Manolis for the same reasons he exposed. Even if Chapter 3 is a good enough place to insert this info, Chapter 12 seems to be an even better one. > There are could also be other places, but this is the only that comes to > mind at the moment. One could also argue we need something of a "Misc > settings" chapter, where all this useful but maybe hard to categorize > stuff would go. But then again, this maybe the role of the FAQ. > > By the way, the above is just a suggestion, if the general consensus is > to merge it into the Basics chapter, I won't object :) > > manolis@ > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" Once again, thank you Joseph and Gabor for your work .. and just in case, a friend and I have fooled around with splash screen and boot splash a not so long time ago .. in case you are interested (discussion is in spanish but C code is not =P ): http://www.penguinpower.com.ar/foro/viewtopic.php?t=2494 http://www.penguinpower.com.ar/foro/viewtopic.php?t=2493 Regards -- Blessings Gonzalo Nemmi From linimon at FreeBSD.org Thu Nov 20 14:41:22 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Nov 20 14:41:35 2008 Subject: docs/129024: [patch] ipfw(8) improvements Message-ID: <200811202241.mAKMfLGP064584@freefall.freebsd.org> Old Synopsis: IPFW improvements New Synopsis: [patch] ipfw(8) improvements Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Thu Nov 20 22:40:32 UTC 2008 Responsible-Changed-Why: Reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=129024 From trhodes at FreeBSD.org Thu Nov 20 16:28:11 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Thu Nov 20 16:28:24 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <49259716.6040207@gmail.com> References: <491E9A3E.2070201@a1poweruser.com> <492544FC.9090504@FreeBSD.org> <4925739E.4060208@gmail.com> <49259459.1000700@FreeBSD.org> <49259716.6040207@gmail.com> Message-ID: <20081120191301.1e3ed12e.trhodes@FreeBSD.org> On Thu, 20 Nov 2008 18:57:58 +0200 Manolis Kiagias wrote: > Gabor PALI wrote: > > > > > >> Would you rather find the discussion of a splash screen useful? I > >> doubt it. What's more, you would not be able to fully understand what > >> is going on. There is another possible section for this info: Chapter > >> 12 (boot). > >> > > > > Hm, I think it is a great idea! What do you think of appending it to > > section ``12.3 The Boot Manager and Boot Stages'' (as a sub-section)? > > > > > > > > Yes, exactly what I had in mind. I was reading section 12.3.3 where > /boot/loader is discussed while writing the previous reply. > > >> There are could also be other places, but this is the only that comes > >> to mind at the moment. One could also argue we need something of a > >> "Misc settings" chapter, where all this useful but maybe hard to > >> categorize stuff would go. But then again, this maybe the role of the > >> FAQ. > >> > > > > I recommended to not to include the entire text in the FAQ itself for > > Joe because I think the FAQ should be "compact and quick". Joe wrote a > > complete and precise description on the topic, so it should be placed in > > the Handbook and referenced (only) from the FAQ. > > > > I am trying to defer the introduction of a potential "Misc Settings" > > chapter until we really encounter things that do not fit in the actual > > contents or outgrew their limits. > > > > > > > > I agree. Most of the misc topics still seem to fit in the standard > chapters if studied carefully. > > >> By the way, the above is just a suggestion, if the general consensus > >> is to merge it into the Basics chapter, I won't object :) > >> > > > > At the moment, I would prefer to inject it into Section 12.3. If there > > is no explicit objection in the next few days, I will try start to work > > on its SGML version and send a patch to the list for review. > > > > Well, let's call all the "usual suspects" ;) to comment... > _______________________________________________ No objection. :) -- Tom Rhodes From cursos at inforedwbcc.net Thu Nov 20 17:56:33 2008 From: cursos at inforedwbcc.net (Fundacion Infored) Date: Thu Nov 20 17:56:49 2008 Subject: CURSOS GRATUITOS TIC DEL INEM CON INSERCION LABORAL Message-ID: <41547-2200811420215054187@A7S14> Publicidad [in=] [mi=] ???????? [IN=] ??????????????? AVISO ? CONVOCATORIA ?LTIMAS PLAZ DESEMPLEADOS CON COMPROMISO DE INSERCI?N LABORAL & ??????????? P puede realizar la preinscripci?n para los cursos en Tecnolog?as que convoca la Fundaci?n Infored en colaboraci?n c on el INEM-Fondo Social Europeo-Ministerio de Trabajo e Inmigraci?n. Se est?n o disponibles.< ??????????? S que se imparten en Madrid y que est?n dirigidos a Est?n financiados por el INEM por lo que son totalmente gra tuitos. Adem?s son preparatorios de las certificaciones oficiales de Microsoft, Cisco o Sun Microsystems: Java, .Net, Cisco, Solari s, Windows, etc. Y cuentan con una inserci?n laboral asegurada p ara el 60% de los alumnos. Sesiones informativas presenciales-proceso de selecci?n Todos los d?as a las 11: de cita Si desea m?s informaci?n consulte la [1]www.inforedwbcc.net y env? [2]wilma@inforedwbcc.net< informaci?n por correo ele telef?nicamente deber? ?indicarnos en su e mail un n?m tel?fono para que nos pongamos en contacto con usted. Si quiere asist proceso de admisi?n, le rogamos nos indique el d?a y la hora elegida (v?ase el recuadro superior para posibles horas y d?as de cita) cita. La aceptaci?n de candidaturas ve disponibilidad de plazas libres. ??????????? A ??????????? F &nb < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:wh ite'>CURSOS < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:wh ite'>INICIO < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:wh ite'>HORARIO < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:wh ite'>MATR?CULA Programador Visual Basic/ASP.NET 15 dic. 1430 a < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:bl ue'>Abierta Programador Java J2SE/J2EE [DEL: :DEL] 24 nov. 14:30 a < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:re d'>?ltimas plazas < Cisco CCNA 18 dic. 08:00 a < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:bl ue'>Abierta Cisco CCNA 15 dic. 14:30 a < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:bl ue'>Abierta Programador Java con Oracle 24 nov. 08.00 a 14.00 < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:re d'>?ltimas plazas Solaris 17 dic. 08.30 a 14.00 < style='font-family:"Calibri","sans-serif";mso-ascii-theme-font:min or-latin; mso-hansi-theme-font:minor-latin;mso-bidi-font-family:Arial;color:bl ue'>Abierta En cumplimiento de lo dispuesto en la Ley Org?nica 15/1999 (B.O.E. Protecci?n de Datos de Car?cter Pe que sus datos est?n incluidos en un fichero de personal, cuyo fin es el env?o de informaci?n comerc titular y responsable del mismo es Infored., con domicilio social en derechos d dirigiendo una carta a Fu mencionada o al correo electr?nico < href="mailto:bajas@inforedwbcc.net?subject=Baja%20de%20Base%20de cual o cuales derechos quiere ejercitar. [3]Pol?tica de privacidad References 1. 3D"http://www.inforedwbc=/ 2. 3D"mailto:wilma@inforedwbc 3. 3D"http://www.inforedwbcc.net/web2007/PoliticadePrivacidad. From DS at praxisvermittlung24.de Thu Nov 20 23:16:39 2008 From: DS at praxisvermittlung24.de (Daniel Seuffert) Date: Thu Nov 20 23:16:47 2008 Subject: Add a Splash Screen Section to the Handbook? In-Reply-To: <200811201921.43412.gnemmi@gmail.com> References: <200811201515.31281.gnemmi@gmail.com> <4925B4C8.8080306@praxisvermittlung24.de> <200811201921.43412.gnemmi@gmail.com> Message-ID: <49266054.5070703@praxisvermittlung24.de> Gonzalo Nemmi wrote: > On Thursday 20 November 2008 5:04:40 pm Daniel Seuffert wrote: >> Gonzalo Nemmi wrote: > You don't have an idea how much time I spent looking for those > CD-/DVD-labels ... Finally .. there they are !! > > _Thank_You_! You're welcome :) > If you ever come up with some CD/DVD sleeves and cases, just let me know and > I'll do the spanish translation :) > > ... and .. ahm .. DragonFlyBSD seems to be missing ;) Uh, ah, oh, shame on me! http://misc.allbsd.de/CD-Stuff/DragonFly%20BSD/ If you need any help or an account to upload the spanish files as well as plain text files please let me know asap via private mail. Best regards and thank you for your work! Daniel From keramida at freebsd.org Thu Nov 20 23:33:09 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Nov 20 23:33:20 2008 Subject: cvs commit: doc/share/misc docbook.css In-Reply-To: <87bpwa4slo.fsf@kobe.laptop> (Giorgos Keramidas's message of "Thu, 20 Nov 2008 12:08:51 +0200") References: <87bpwa4slo.fsf@kobe.laptop> Message-ID: <87prkp5yc9.fsf@kobe.laptop> On Thu, 20 Nov 2008 12:08:51 +0200, Giorgos Keramidas wrote: > Yep. I didn't see any major objections to the [after] style, so I > will commit the new style-sheet later today. Committed in rev 1.14 of `docbook.css'. Thanks to everyone who looked at the new pages and wrote back with comments :) From kes-kes at yandex.ru Sun Nov 23 09:20:02 2008 From: kes-kes at yandex.ru (Eugen Konkov) Date: Sun Nov 23 09:20:08 2008 Subject: docs/129095: Can not check that packet originating/destined for local host Message-ID: <200811231711.mANHBK2r006910@www.freebsd.org> >Number: 129095 >Category: docs >Synopsis: Can not check that packet originating/destined for local host >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 Nov 23 17:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Eugen Konkov >Release: 7.1-PRERELEASE >Organization: ISP Konkov >Environment: FreeBSD home.kes.net.ua 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #: Sun Nov 23 17:19:12 EET 2008 kes@home.kes.net.ua:/usr/obj/usr/src/sys/KES_KERN_v7 i386 >Description: man ipfw ... A packet may not have a receive or transmit interface: packets originating from the local host have no receive interface, while packets destined for the local host have no transmit interface. How to check that packet originating from the local host? ipfw allow all from any to any out recv null ipfw allow all from any to any in xmit null null stands for there is not receive/transmit interface >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From keramida at FreeBSD.org Sun Nov 23 11:42:59 2008 From: keramida at FreeBSD.org (keramida@FreeBSD.org) Date: Sun Nov 23 11:43:06 2008 Subject: docs/128816: [PATCH] Enhance the explanation of using of mount options in fstab(5) Message-ID: <200811231942.mANJgxFf087523@freefall.freebsd.org> Synopsis: [PATCH] Enhance the explanation of using of mount options in fstab(5) Responsible-Changed-From-To: freebsd-doc->keramida Responsible-Changed-By: keramida Responsible-Changed-When: Sun Nov 23 19:42:46 UTC 2008 Responsible-Changed-Why: I'll handle this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=128816 From bugmaster at FreeBSD.org Mon Nov 24 03:06:09 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 24 03:06:39 2008 Subject: Current unassigned doc problem reports Message-ID: <200811241106.mAOB68FA018960@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/129095 doc ipfw(8): Can not check that packet originating/destine o docs/129024 doc [patch] ipfw(8) improvements p docs/128968 doc [patch] rwlock(9) man page typo o docs/128804 doc Gmirror handbook instructions convert boot-drive to gm o docs/128768 doc Missing documentation about tmpfs mount options o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128325 doc README.snapshots still refers to snaphots as "alpha-te o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128129 doc Sysinstall color problem in xterm o docs/128128 doc Sysinstall not mentioned in 4.4 "Using the Packages Sy o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127923 doc Please mention qemu in the FreeBSD Handbook o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/127406 doc [patch] update umodem man page: Sony Ericsson W810i o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122470 doc [patch] exit status on fetch(1) manual page o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o 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 docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121197 doc [patch] edits to books/porters-handbook 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/120628 doc PAE documentation errror in handbook 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/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) s docs/119404 doc [request] events page should list only last 2 years wo o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu 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/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument 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/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported 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/112481 doc bug in ppp.linkup example 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/111263 doc [request] Information on $EDITOR variable in section 3 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/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout 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 o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n 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/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym 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/98759 doc [patch] sbp_targ(4) man page missing reference to devi 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/95139 doc FAQ to move filesystem to new disk fails: incorrect pe 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/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous 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/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI 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 o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt 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/47818 doc [patch] ln(1) manpage is confusing 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 o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. 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 175 problems total. From sonic2000gr at gmail.com Mon Nov 24 09:36:13 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 09:36:20 2008 Subject: A patch for the 'geom' chapter Message-ID: <492AE607.4020208@gmail.com> Hey all, I recently completed the Greek translation of the geom chapter and (as it has become customary) I also created a patch for the English version. So I 'd thought to call all my usual reviewers (and anyone else who cares to comment): http://people.freebsd.org/~manolis/geom.txt A brief description of (some) changes: - Added the messages returned by a gstripe command (as requested by the original author) - Change the /mnt as a permanent mount point in fstab, suggested in an example. Since /mnt is normally used for temporary administrator mounts, it makes sense to create a specific mount point for a permanent mount. - Convert a vi editing session to a . The user is free to choose his editor - although the original vi instructions are handy and should not be removed - It seems glabel can create both permanent and temporary labels that are not file system specific. Reworded the relevant paragraphs - Add a complete example of labeling a boot disk's partitions, so it can be used on another controller, or indeed, system - Journaling does not store the log on the last sector (only metadata that shows the volume is journaled) - Loading the geom_journal module during startup - or building it into a custom kernel - Add a reference to my gjournal-desktop article ;) - Minor rewording in paragraphs above / below the actual changes to avoid repeating the same information This is a somewhat lengthy patch, for those that feel better reading the build, here it is: http://people.freebsd.org/~manolis/geom.html Any and all comments appreciated :) Cheers, manolis@ From trhodes at FreeBSD.org Mon Nov 24 10:51:19 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Nov 24 10:51:30 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492AE607.4020208@gmail.com> References: <492AE607.4020208@gmail.com> Message-ID: <20081124135107.06a8af26.trhodes@FreeBSD.org> On Mon, 24 Nov 2008 19:36:07 +0200 Manolis Kiagias wrote: > Hey all, > > I recently completed the Greek translation of the geom chapter and (as > it has become customary) I also created a patch for the English > version. So I 'd thought to call all my usual reviewers (and anyone > else who cares to comment): > > http://people.freebsd.org/~manolis/geom.txt > > A brief description of (some) changes: > > - Added the messages returned by a gstripe command (as requested by the > original author) > - Change the /mnt as a permanent mount point in fstab, suggested in an > example. Since /mnt is normally used for temporary administrator mounts, > it makes sense to create a specific mount point for a permanent mount. > - Convert a vi editing session to a . The user is free to choose > his editor - although the original vi instructions are handy and should > not be removed > - It seems glabel can create both permanent and temporary labels that > are not file system specific. Reworded the relevant paragraphs > - Add a complete example of labeling a boot disk's partitions, so it can > be used on another controller, or indeed, system > - Journaling does not store the log on the last sector (only metadata > that shows the volume is journaled) > - Loading the geom_journal module during startup - or building it into a > custom kernel > - Add a reference to my gjournal-desktop article ;) > - Minor rewording in paragraphs above / below the actual changes to > avoid repeating the same information > > This is a somewhat lengthy patch, for those that feel better reading the > build, here it is: > > http://people.freebsd.org/~manolis/geom.html > > Any and all comments appreciated :) This looks pretty good actually. I would probably change the following: + + Labeling Your Boot Disk's Partitions to: Labeling Partitions on the Boot Disk And there are a lot of "You" references. I've tried to write this without invoking the user as much as possible and may make reading the entire chapter difficult. I would prefer we not talk to the user though. -- Tom Rhodes From keramida at freebsd.org Mon Nov 24 11:17:06 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 24 11:17:12 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <20081124135107.06a8af26.trhodes@FreeBSD.org> (Tom Rhodes's message of "Mon, 24 Nov 2008 13:51:07 -0500") References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> Message-ID: <87abbp3q5o.fsf@kobe.laptop> On Mon, 24 Nov 2008 13:51:07 -0500, Tom Rhodes wrote: > On Mon, 24 Nov 2008 19:36:07 +0200 > Manolis Kiagias wrote: >> http://people.freebsd.org/~manolis/geom.txt > This looks pretty good actually. I would probably change the > following: > > + > + Labeling Your Boot Disk's Partitions > > to: > > Labeling Partitions on the Boot Disk > > And there are a lot of "You" references. I've tried to write this > without invoking the user as much as possible and may make reading the > entire chapter difficult. I would prefer we not talk to the user > though. I am not sure if I will have the time to read the full patch tonight, but Tom is quite right about avoiding "you" when possible. From sonic2000gr at gmail.com Mon Nov 24 11:34:39 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 11:34:46 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <87abbp3q5o.fsf@kobe.laptop> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> Message-ID: <492B01C4.6090707@gmail.com> Giorgos Keramidas wrote: > On Mon, 24 Nov 2008 13:51:07 -0500, Tom Rhodes wrote: > >> On Mon, 24 Nov 2008 19:36:07 +0200 >> Manolis Kiagias wrote: >> >>> http://people.freebsd.org/~manolis/geom.txt >>> > > >> This looks pretty good actually. I would probably change the >> following: >> >> + >> + Labeling Your Boot Disk's Partitions >> >> to: >> >> Labeling Partitions on the Boot Disk >> >> And there are a lot of "You" references. I've tried to write this >> without invoking the user as much as possible and may make reading the >> entire chapter difficult. I would prefer we not talk to the user >> though. >> > > I am not sure if I will have the time to read the full patch tonight, > but Tom is quite right about avoiding "you" when possible. > > Thanks. I will try to rephrase most parts into passive voice where possible. I guess I am somewhat influenced by the Greek translations, where sometimes passive voice sounds unnatural ;) Cheers, manolis From r.c.ladan at gmail.com Mon Nov 24 12:06:17 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Nov 24 12:06:24 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B01C4.6090707@gmail.com> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> Message-ID: 2008/11/24 Manolis Kiagias : > Giorgos Keramidas wrote: >> On Mon, 24 Nov 2008 13:51:07 -0500, Tom Rhodes wrote: >> >>> On Mon, 24 Nov 2008 19:36:07 +0200 >>> Manolis Kiagias wrote: >>> >>>> http://people.freebsd.org/~manolis/geom.txt >>>> >> >> >>> This looks pretty good actually. I would probably change the >>> following: >>> >>> + >>> + Labeling Your Boot Disk's Partitions >>> >>> to: >>> >>> Labeling Partitions on the Boot Disk >>> >>> And there are a lot of "You" references. I've tried to write this >>> without invoking the user as much as possible and may make reading the >>> entire chapter difficult. I would prefer we not talk to the user >>> though. >>> >> >> I am not sure if I will have the time to read the full patch tonight, >> but Tom is quite right about avoiding "you" when possible. >> >> > Thanks. I will try to rephrase most parts into passive voice where > possible. I guess I am somewhat influenced by the Greek translations, > where sometimes passive voice sounds unnatural ;) > I think the same is true for the Dutch language. Using passive voice sometimes sounds too formal/distant IMHO (it makes me think of legal texts). Active voice also involves the reader more. It also makes it possible to refer to e.g. 'their computer' instead of 'a computer', which can be useful in examples. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From keramida at freebsd.org Mon Nov 24 12:25:55 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 24 12:26:01 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B01C4.6090707@gmail.com> (Manolis Kiagias's message of "Mon, 24 Nov 2008 21:34:28 +0200") References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> Message-ID: <87prkkx457.fsf@kobe.laptop> On Mon, 24 Nov 2008 21:34:28 +0200, Manolis Kiagias wrote: > Thanks. I will try to rephrase most parts into passive voice where > possible. I guess I am somewhat influenced by the Greek translations, > where sometimes passive voice sounds unnatural ;) That's true. In Greek translations passive voice is considered 'slightly bad'. Some of the prominent translators who have done academic work (like translating ancient Greek texts to modern Greek) have written about this too. I. Th. Kakrides mentions that it is some times preferable to be a bit verbose and avoid passive voice in his booklet titled "The Translation Problem". I'm really glad you have reached the same conclusion, after doing so much of the FreeBSD Greek translation work :-) From trhodes at FreeBSD.org Mon Nov 24 12:34:22 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Nov 24 12:34:34 2008 Subject: A patch for the 'geom' chapter In-Reply-To: References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> Message-ID: <20081124153358.7a539e67.trhodes@FreeBSD.org> On Mon, 24 Nov 2008 20:57:14 +0100 "Rene Ladan" wrote: > 2008/11/24 Manolis Kiagias : > > Giorgos Keramidas wrote: > >> On Mon, 24 Nov 2008 13:51:07 -0500, Tom Rhodes wrote: > >> > >>> On Mon, 24 Nov 2008 19:36:07 +0200 > >>> Manolis Kiagias wrote: > >>> > >>>> http://people.freebsd.org/~manolis/geom.txt > >>>> > >> > >> > >>> This looks pretty good actually. I would probably change the > >>> following: > >>> > >>> + > >>> + Labeling Your Boot Disk's Partitions > >>> > >>> to: > >>> > >>> Labeling Partitions on the Boot Disk > >>> > >>> And there are a lot of "You" references. I've tried to write this > >>> without invoking the user as much as possible and may make reading the > >>> entire chapter difficult. I would prefer we not talk to the user > >>> though. > >>> > >> > >> I am not sure if I will have the time to read the full patch tonight, > >> but Tom is quite right about avoiding "you" when possible. > >> > >> > > Thanks. I will try to rephrase most parts into passive voice where > > possible. I guess I am somewhat influenced by the Greek translations, > > where sometimes passive voice sounds unnatural ;) > > > I think the same is true for the Dutch language. Using passive voice > sometimes sounds too formal/distant IMHO (it makes me think of legal > texts). Active voice also involves the reader more. It also makes it > possible to refer to e.g. 'their computer' instead of 'a computer', which > can be useful in examples. While true, it does have a few flaws, including it can make incorrect assumptions about the reader's sex, environment, etc. and adds a little less professionalism. So I try to write all my documentation carefully to avoid addressing the reader. Sometimes it would be easier, but that doesn't really make it right. In translations, though, I think it should be up to the initial teams. It could be very different for languages which I do not speak, whether passive voice is incorrect. :) -- Tom Rhodes From sonic2000gr at gmail.com Mon Nov 24 12:47:39 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 12:47:45 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <20081124153358.7a539e67.trhodes@FreeBSD.org> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> Message-ID: <492B12E3.3000109@gmail.com> Tom Rhodes wrote: > While true, it does have a few flaws, including it can make > incorrect assumptions about the reader's sex This will not happen in Greek, when the reader is addressed in 'courtesy' plural (or whatever this may be called in English, which simply does not have this 'feature' ;) ) On the other hand I've seen Greek translations (in fact I just saw a few in some Linux project today) addressing the reader in *first* person, which is absolutely horrible. > , environment, > etc. and adds a little less professionalism. > > So I try to write all my documentation carefully to avoid > addressing the reader. Sometimes it would be easier, but that > doesn't really make it right. > True, the English version of the Handbook is mostly using passive voice, and for the most part it is not a problem > In translations, though, I think it should be up to the initial > teams. It could be very different for languages which I > do not speak, whether passive voice is incorrect. :) > > As Giorgos just said, passive voice in Greek can sound 'slightly bad'. Some verbs are simply not meant to be used passively and often whole sentences sound weird when attempting to keep the original's passive voice. I've come to recognize these and switch them. And yes, it is not difficult after so many thousand lines of translations ;) From sonic2000gr at gmail.com Mon Nov 24 14:41:22 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 14:41:29 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <20081124153358.7a539e67.trhodes@FreeBSD.org> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> Message-ID: <492B2D8C.4090807@gmail.com> After our discussion, here again is the "second take" of this patch: http://people.freebsd.org/~manolis/geom.txt And the build starts here: http://people.freebsd.org/~manolis/geom.html I tried to address most points, but feel free to send more comments and fixes. Take your time, as I won't be looking at this further tonight (it will only get worse if I do ;) ) Thank you all! manolis@ From sonic2000gr at gmail.com Mon Nov 24 14:55:44 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 14:55:49 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B2FCF.5060503@kovesdan.org> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <492B2FCF.5060503@kovesdan.org> Message-ID: <492B30EA.5040807@gmail.com> G?bor K?vesd?n wrote: > Manolis Kiagias escribi?: >> After our discussion, here again is the "second take" of this patch: >> >> http://people.freebsd.org/~manolis/geom.txt >> >> And the build starts here: >> >> http://people.freebsd.org/~manolis/geom.html >> >> I tried to address most points, but feel free to send more comments and >> fixes. >> Take your time, as I won't be looking at this further tonight (it will >> only get worse if I do ;) ) >> > Hi Manolis, > > I've reviewed this second patch. Nice work, thanks for your efforts! I > only found a little nit: > > + geom_journal.ko kernel will also have to be > > > > It should be "kernel module" instead of "kernel". > > Cheers, > Aha, this is indeed too small and I will fix immediately ;) Thanks! From gabor at kovesdan.org Mon Nov 24 15:09:51 2008 From: gabor at kovesdan.org (=?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?=) Date: Mon Nov 24 15:10:01 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B2D8C.4090807@gmail.com> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> Message-ID: <492B2FCF.5060503@kovesdan.org> Manolis Kiagias escribi?: > After our discussion, here again is the "second take" of this patch: > > http://people.freebsd.org/~manolis/geom.txt > > And the build starts here: > > http://people.freebsd.org/~manolis/geom.html > > I tried to address most points, but feel free to send more comments and > fixes. > Take your time, as I won't be looking at this further tonight (it will > only get worse if I do ;) ) > Hi Manolis, I've reviewed this second patch. Nice work, thanks for your efforts! I only found a little nit: + geom_journal.ko kernel will also have to be It should be "kernel module" instead of "kernel". Cheers, -- K?vesd?n G?bor EMAIL: gabor@kovesdan.org WWW: http://www.kovesdan.org From hrs at FreeBSD.org Mon Nov 24 17:26:07 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Mon Nov 24 17:26:14 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B2D8C.4090807@gmail.com> References: <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> Message-ID: <20081125.102512.193370295.hrs@allbsd.org> Manolis Kiagias wrote in <492B2D8C.4090807@gmail.com>: so> After our discussion, here again is the "second take" of this patch: so> so> http://people.freebsd.org/~manolis/geom.txt One thing: + Permanent labels can be created with the tunefs + or newfs commands. They will then be created I think the &man.tunefs.8; and &man.newfs.8; are better than foo here. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081125/31fea033/attachment.pgp From sonic2000gr at gmail.com Mon Nov 24 20:27:01 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Nov 24 20:27:07 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <20081125.102512.193370295.hrs@allbsd.org> References: <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <20081125.102512.193370295.hrs@allbsd.org> Message-ID: <492B7E8E.4070508@gmail.com> Hiroki Sato wrote: > Manolis Kiagias wrote > in <492B2D8C.4090807@gmail.com>: > > so> After our discussion, here again is the "second take" of this patch: > so> > so> http://people.freebsd.org/~manolis/geom.txt > > One thing: > > + Permanent labels can be created with the tunefs > + or newfs commands. They will then be created > > I think the &man.tunefs.8; and &man.newfs.8; are better than > foo here. > > -- > | Hiroki SATO > True, will change these. Thanks! From pgj at FreeBSD.org Mon Nov 24 23:01:10 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Nov 24 23:02:09 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B2D8C.4090807@gmail.com> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> Message-ID: <492BA2AF.1000907@FreeBSD.org> Manolis Kiagias wrote: > After our discussion, here again is the "second take" of this patch [..] > I tried to address most points, but feel free to send more comments and > fixes. I hardly find any problems with your proposed patch, it is a really nice work. I am not in GEOM (however, I should really try these things some time), so I have just checked it from the side of markups. I think I found a subtle inconsistency only: initially, you refer to the geom_stripe kernel module without the .ko extension, but after then you refer to geom_journal with a .ko extension. I think you may simply omit the extension in the latter case too. Sorry for my bad habit in advance, but I think I can tell more about this patch when it gets committed and I have to translate it. By the way, I agree with Tom regarding the use of passive voice, it is very common in technical English. In Hungarian, we also employ the mentioned 'courtesy' plural, however I am trying to avoid talking to anybody in the translations. Passive voice in our tongue is not so natural (however people will understand it), so sometimes I have to do some tricks when translating it. I usually fight against the different "-isms" in the translations, I try to suit the sentences to the actual language context. (Well, sometimes it a "sport" for me to speak in Hungarian without addressing anybody...) As far as I remember, only the welcome message in the Handbook translation is (more or less) personal, all the other sentences are composed in a strict technical manner. Hopefully, there are only a few schemes to be adapted to Hungarian, after then the entire translation process could be done without too much thinking. That is why it is kind of a relaxation technique for me. Nice work! :g From keramida at freebsd.org Mon Nov 24 23:55:09 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Nov 24 23:55:15 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492B7E8E.4070508@gmail.com> (Manolis Kiagias's message of "Tue, 25 Nov 2008 06:26:54 +0200") References: <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <20081125.102512.193370295.hrs@allbsd.org> <492B7E8E.4070508@gmail.com> Message-ID: <873ahggs02.fsf@kobe.laptop> On Tue, 25 Nov 2008 06:26:54 +0200, Manolis Kiagias wrote: > Hiroki Sato wrote: >> Manolis Kiagias wrote >> in <492B2D8C.4090807@gmail.com>: >> >> so> After our discussion, here again is the "second take" of this patch: >> so> >> so> http://people.freebsd.org/~manolis/geom.txt >> >> One thing: >> >> + Permanent labels can be created with the tunefs >> + or newfs commands. They will then be created >> >> I think the &man.tunefs.8; and &man.newfs.8; are better than >> foo here. > > True, will change these. I just finished reading the new patch. Excellent work :) Just a minor point that may make the gjournal parts friendlier to mirror admins. You don't have to hardcode `www.freebsd.org' or the path to the gjournal article into the Handbook. This part: + Please refer to the article Implementing UFS Journaling on a Desktop PC + for detailed instructions on this task. Can be written as: + Please refer to the article Implementing UFS Journaling on + a Desktop PC for detailed instructions on this task. I have updated `doc/share/sgml/urls.ent' to include URL entities for our current set of articles, including gjournal-desktop, so if you update from CVS the patch should build fine either way. Patch approved by me too. From PublicServicePartnershipLtd_769894 at dotmailer.co.uk Tue Nov 25 02:24:37 2008 From: PublicServicePartnershipLtd_769894 at dotmailer.co.uk (Mike Cross) Date: Tue Nov 25 02:24:43 2008 Subject: Emailing to the Public Sector Made Easy Message-ID: From PublicServicePartnershipLtd_769894 at dotmailer.co.uk Tue Nov 25 02:26:07 2008 From: PublicServicePartnershipLtd_769894 at dotmailer.co.uk (Mike Cross) Date: Tue Nov 25 02:26:19 2008 Subject: Emailing to the Public Sector Made Easy Message-ID: From sonic2000gr at gmail.com Tue Nov 25 05:37:44 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Nov 25 05:38:15 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492BA2AF.1000907@FreeBSD.org> References: <492AE607.4020208@gmail.com> <20081124135107.06a8af26.trhodes@FreeBSD.org> <87abbp3q5o.fsf@kobe.laptop> <492B01C4.6090707@gmail.com> <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <492BA2AF.1000907@FreeBSD.org> Message-ID: <492BFFA1.4010205@gmail.com> Gabor PALI wrote: > Manolis Kiagias wrote: > >> After our discussion, here again is the "second take" of this patch [..] >> I tried to address most points, but feel free to send more comments and >> fixes. >> > > I hardly find any problems with your proposed patch, it is a really nice > work. I am not in GEOM (however, I should really try these things some > time), so I have just checked it from the side of markups. > Which I really count on you to do :) > I think I found a subtle inconsistency only: initially, you refer to the > geom_stripe kernel module without the .ko extension, but after then you > refer to geom_journal with a .ko extension. I think you may simply omit > the extension in the latter case too. > Cheers, I'll have a look at this. > Sorry for my bad habit in advance, but I think I can tell more about > this patch when it gets committed and I have to translate it. > > By the way, I agree with Tom regarding the use of passive voice, it is > very common in technical English. In Hungarian, we also employ the > mentioned 'courtesy' plural, however I am trying to avoid talking to > anybody in the translations. Passive voice in our tongue is not so > natural (however people will understand it), so sometimes I have to do > some tricks when translating it. I usually fight against the different > "-isms" in the translations, I try to suit the sentences to the actual > language context. (Well, sometimes it a "sport" for me to speak in > Hungarian without addressing anybody...) > In Greek sometimes the passive voice sounds completely unnatural. I am now used to switching styles when needed. Besides in Greek we don't have the too many "you"s problem, since the verbs change form according to person, hence these references are not needed. > As far as I remember, only the welcome message in the Handbook > translation is (more or less) personal, all the other sentences are > composed in a strict technical manner. Hopefully, there are only a few > schemes to be adapted to Hungarian, after then the entire translation > process could be done without too much thinking. That is why it is kind > of a relaxation technique for me. > > > Nice work! > > Thanks for the review ;) From sonic2000gr at gmail.com Tue Nov 25 05:44:04 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Nov 25 05:44:09 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <873ahggs02.fsf@kobe.laptop> References: <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <20081125.102512.193370295.hrs@allbsd.org> <492B7E8E.4070508@gmail.com> <873ahggs02.fsf@kobe.laptop> Message-ID: <492C011D.4040707@gmail.com> Giorgos Keramidas wrote: > On Tue, 25 Nov 2008 06:26:54 +0200, Manolis Kiagias wrote: > >> Hiroki Sato wrote: >> >>> Manolis Kiagias wrote >>> in <492B2D8C.4090807@gmail.com>: >>> >>> so> After our discussion, here again is the "second take" of this patch: >>> so> >>> so> http://people.freebsd.org/~manolis/geom.txt >>> >>> One thing: >>> >>> + Permanent labels can be created with the tunefs >>> + or newfs commands. They will then be created >>> >>> I think the &man.tunefs.8; and &man.newfs.8; are better than >>> foo here. >>> >> True, will change these. >> > > I just finished reading the new patch. Excellent work :) > Thanks :) > Just a minor point that may make the gjournal parts friendlier to mirror > admins. You don't have to hardcode `www.freebsd.org' or the path to the > gjournal article into the Handbook. > > This part: > > + Please refer to the article + url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop">Implementing UFS Journaling on a Desktop PC > + for detailed instructions on this task. > > Can be written as: > > + Please refer to the article + url="&url.articles.gjournal-desktop;">Implementing UFS Journaling on > + a Desktop PC for detailed instructions on this task. > > I have updated `doc/share/sgml/urls.ent' to include URL entities for our > current set of articles, including gjournal-desktop, so if you update > from CVS the patch should build fine either way. > > Patch approved by me too. > > > I knew there would be another way for this long link. Thanks, I'll change it and will probably commit later today. Many thanks to anyone who took the time to review this! manolis@ From trhodes at FreeBSD.org Tue Nov 25 07:02:24 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Tue Nov 25 07:02:30 2008 Subject: A patch for the 'geom' chapter In-Reply-To: <492C011D.4040707@gmail.com> References: <20081124153358.7a539e67.trhodes@FreeBSD.org> <492B2D8C.4090807@gmail.com> <20081125.102512.193370295.hrs@allbsd.org> <492B7E8E.4070508@gmail.com> <873ahggs02.fsf@kobe.laptop> <492C011D.4040707@gmail.com> Message-ID: <20081125100159.6229cffa.trhodes@FreeBSD.org> On Tue, 25 Nov 2008 15:43:57 +0200 Manolis Kiagias wrote: > Giorgos Keramidas wrote: > > On Tue, 25 Nov 2008 06:26:54 +0200, Manolis Kiagias wrote: > > > >> Hiroki Sato wrote: > >> > >>> Manolis Kiagias wrote > >>> in <492B2D8C.4090807@gmail.com>: > >>> > >>> so> After our discussion, here again is the "second take" of this patch: > >>> so> > >>> so> http://people.freebsd.org/~manolis/geom.txt > >>> > >>> One thing: > >>> > >>> + Permanent labels can be created with the tunefs > >>> + or newfs commands. They will then be created > >>> > >>> I think the &man.tunefs.8; and &man.newfs.8; are better than > >>> foo here. > >>> > >> True, will change these. > >> > > > > I just finished reading the new patch. Excellent work :) > > > > Thanks :) > > Just a minor point that may make the gjournal parts friendlier to mirror > > admins. You don't have to hardcode `www.freebsd.org' or the path to the > > gjournal article into the Handbook. > > > > This part: > > > > + Please refer to the article > + url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop">Implementing UFS Journaling on a Desktop PC > > + for detailed instructions on this task. > > > > Can be written as: > > > > + Please refer to the article > + url="&url.articles.gjournal-desktop;">Implementing UFS Journaling on > > + a Desktop PC for detailed instructions on this task. > > > > I have updated `doc/share/sgml/urls.ent' to include URL entities for our > > current set of articles, including gjournal-desktop, so if you update > > from CVS the patch should build fine either way. > > > > Patch approved by me too. > > > > > > > I knew there would be another way for this long link. Thanks, I'll > change it and will probably commit later today. > > Many thanks to anyone who took the time to review this! This has my rubber stamp too - I think all my issues have been pointed out and fixed. Thanks! -- Tom Rhodes From shurd at sasktel.net Tue Nov 25 16:10:01 2008 From: shurd at sasktel.net (Stephen Hurd) Date: Tue Nov 25 16:10:07 2008 Subject: docs/129196: Inconsistent errno in strtol() Message-ID: <200811260005.mAQ058Is091716@www.freebsd.org> >Number: 129196 >Category: docs >Synopsis: Inconsistent errno in strtol() >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: Wed Nov 26 00:10:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Stephen Hurd >Release: 7.0-RELEASE >Organization: >Environment: FreeBSD server.hurd.local 7.0-RELEASE FreeBSD 7.0-RELEASE #4: Mon Mar 10 23:00:02 PDT 2008 admin@server.hurd.local:/usr/obj/usr/src/sys/SERVER i386 >Description: ``strtol("0", NULL, 0);'' and ``strtol("0x", NULL, 0);'' return zero and does not set errno, but ``strtol("", NULL, 0);'' does. Since the documentation says that an octal value is /0?([0-7]+)/ and a hex value is /(?:0x)?([0-9a-zA-Z])/ in none of the cases can a conversion be performed. At least SUSv2 states that EINVAL indicates an invalid base argument, not an invalid nptr argument (I don't have the other standards available) so all of those examples should be consistent with each other (most likely not setting errno). >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From avg at icyb.net.ua Tue Nov 25 16:12:09 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Tue Nov 25 16:12:16 2008 Subject: typo in handbook zfs section Message-ID: <492C78A2.4020607@icyb.net.ua> I am reading this now: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/filesystems-zfs.html in section 20.2.1.3 Loader Tunables there is the following obvious typo: vm.kmem_slze="330M" ^- here -- Andriy Gapon From pgj at FreeBSD.org Tue Nov 25 20:59:50 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Tue Nov 25 20:59:56 2008 Subject: typo in handbook zfs section In-Reply-To: <492C78A2.4020607@icyb.net.ua> References: <492C78A2.4020607@icyb.net.ua> Message-ID: <492CD7BB.1000203@FreeBSD.org> Dear Andriy, You wrote: > in section 20.2.1.3 Loader Tunables there is [..] (an) obvious typo Thank you for your report. I have fixed this, the corrected version should appear on the web site soon. Happy reading, :g From gfherd at yahoo.com.tw Fri Nov 28 05:05:05 2008 From: gfherd at yahoo.com.tw (gfherd@yahoo.com.tw) Date: Fri Nov 28 05:05:11 2008 Subject: =?iso-8859-1?q?Yahoo!=A9=5F=BC=AF=A5=CD=AC=A1+_-_=A7K=B6O=B8=D5?= =?iso-8859-1?q?=AC=DD=A4U=B8=FC=B3=CC=B7s=B0=AA=B5e=BD=E8AV=A5=FA?= =?iso-8859-1?q?=BA=D0=2420=A4=B8vshy0?= Message-ID: <200811281235.mASCZKoB087818@w1.mtf.tpc.yahoo.com> 請-到Ｙ-Ａ-Ｈ-Ｏ-Ｏ-首-頁搜 尋 ~爆 爆 爽 Ａ 片 網~ 寄了一則最新活動給你喔!! ------------------------------------------------------------ 給您的留言： 最新更新: 性愛調教女王立花里子~訓服多個頑固的痴漢u345m 最夯最HIGH的高畫質AV光碟 單片25~39元買10送2買20送4 平均每片僅需30元購滿1000元立即贈送跳跳蛋一個 您將最優惠的價格買到最優良的影片 包裝隱密、買的放心、播放流暢、看的安心 歡迎按此查看最新影片 另有超夯A片線上看和下載全面免費cr38tvi32 請在雅虎 搜尋上打『爆爆爽免費成人影片』查詢網站 請點我→→ i8yr3c06k6http://y6f2wi4k1j809u6~l4fiv81m9u2d.PDFDDPG.TK#j5trn773qs15o5.com#5te40q73mw6r9@8jw8tiadr2.un2a111g80p6p.com uj2l558o3k86r/ p6fchdppd 免費試看下載最新高畫質AV光碟$20元vshy0 http://tw.news.yahoo.com/article/url/d/a/081118/5/19na4.html ------------------------------------------------------------ Yahoo!奇摩生活+ http://lifestyle.yahoo.com.tw/ 版權所有 Yahoo!奇摩 From www at FreeBSD.org Fri Nov 28 09:33:33 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Nov 28 09:33:39 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200811281733.mASHXWtG057590@www.freebsd.org> install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/installation-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/installation-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/readme.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-ia64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-i386.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/docbook.css /usr/local/www/www.freebsd.org/data/releases/6.2R ===> releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/announce.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/schedule.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/errata.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/readme.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/docbook.css /usr/local/www/www.freebsd.org/data/releases/6.3R ===> releases/6.4R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.4R/announce.html /usr/local/www/www.freebsd.org/data/releases/6.4R install: /usr/local/www/www.freebsd.org/data/releases/6.4R/announce.html: Permission denied *** Error code 71 Stop in /w/www/build/www/en/releases/6.4R. *** Error code 1 Stop in /w/www/build/www/en/releases. *** Error code 1 Stop in /w/www/build/www/en. 22.53 real 5.61 user 9.75 sys From www at FreeBSD.org Fri Nov 28 10:24:33 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Nov 28 10:24:40 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200811281824.mASIOX6A082145@www.freebsd.org> install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/installation-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/installation-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/readme.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-ia64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-i386.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/relnotes-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.2R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.2R/docbook.css /usr/local/www/www.freebsd.org/data/releases/6.2R ===> releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/announce.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/schedule.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/errata.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/hardware-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/installation-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/readme.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-alpha.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-amd64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-i386.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-pc98.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-powerpc.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/relnotes-sparc64.html /usr/local/www/www.freebsd.org/data/releases/6.3R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.3R/docbook.css /usr/local/www/www.freebsd.org/data/releases/6.3R ===> releases/6.4R install -C -o www -g wwwadm -m 664 /w/www/build/www/en/releases/6.4R/announce.html /usr/local/www/www.freebsd.org/data/releases/6.4R install: /usr/local/www/www.freebsd.org/data/releases/6.4R/announce.html: chown/chgrp: Operation not permitted *** Error code 71 Stop in /w/www/build/www/en/releases/6.4R. *** Error code 1 Stop in /w/www/build/www/en/releases. *** Error code 1 Stop in /w/www/build/www/en. 17.39 real 5.20 user 8.83 sys From frank at solensky.org Fri Nov 28 10:40:03 2008 From: frank at solensky.org (Frank Solensky) Date: Fri Nov 28 10:40:08 2008 Subject: docs/129263: Obsolete info on collecting a crash dump prior to "dumpon" Message-ID: <200811281836.mASIaasu084176@www.freebsd.org> >Number: 129263 >Category: docs >Synopsis: Obsolete info on collecting a crash dump prior to "dumpon" >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 28 18:40:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Frank Solensky >Release: FreeBSD 7.1 Beta2 >Organization: >Environment: n/a >Description: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN. The second paragraph of "Configuring the Dump Device" is as follows: Alternatively, the dump device can be hard-coded via the dump clause in the config(5) line of a kernel configuration file. This approach is deprecated and should be used only if a kernel is crashing before dumpon(8) can be executed. It's more than deprecated. Running "config" off a kernel configuration file with "config dump " included results in a "root/dump/swap specification obsolete" error. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From eitanadlerlist at gmail.com Fri Nov 28 12:23:11 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Fri Nov 28 12:23:17 2008 Subject: tcsh man page Message-ID: <49305325.9070703@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 in man 1 tcsh http://tcshrc.source-forge.net should not have the "-" The relevant line in src/contrib/tcsh/tcsh.man is \fIhttp://tcshrc.sourceforge.net\fR. which does not have a - Why does the "-" show up? How can it be fixed? - -- Eitan Adler GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkwUyUACgkQtl8kq+nCzNFaDQCdE9HxJBFk9lCCbt264PnwB0Cr NNIAoIuQ9DF7Yh2DDT7/8fVaV7fc+n46 =NO7J -----END PGP SIGNATURE----- From gamato at users.sf.net Fri Nov 28 15:13:53 2008 From: gamato at users.sf.net (martinko) Date: Fri Nov 28 15:14:01 2008 Subject: Installation Instructions mention vmware2 and not Qemu Message-ID: Hallo, I've just noticed in FreeBSD 6.4-RELEASE Installation Instructions that in chapter 1.6.6. "Can I run other Operating Systems under FreeBSD?" we point to emulators/vmware2 port which doesn't seem to be in the ports tree anymore. At the same time we don't mention emulators/qemu at all while Qemu is likely the best cross-platform VM solution on FreeBSD at the moment. Cheers, Martin From pgj at FreeBSD.org Fri Nov 28 17:44:58 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Nov 28 17:45:05 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer Message-ID: <49309E91.7050006@FreeBSD.org> Hello, I encountered some interesting parts in the SGML Markup chapter [1] during translation of the FDP Primer [2], so I decided to fix them up and send the corresponding patch in small pieces to this list. I would like you to check and comment these patches before I commit them. My proposed changes are as follows: http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/1.diff I think there is no need for this "baroque" notation, since I could not find any other instances in the document. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/2.diff Oh, yeah. Ports Collection should be capitalized. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/3.diff I think word "of" should be "or" because we are talking about "rowspan and/or colspan attributes", so it would rhyme with "number of rows or columns" or "number of rows and/or columns". http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/4.diff In my opinion, some literals and attributes want a element. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/5.diff Remove leftovers of the first-person narration, add more generalization to the text, refer to the Handbook just as an example. Update path and names of the Handbook sources. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/6.diff Add some missing text to the
example. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/7.diff I think there is no example of tables with borders, however the text mentions it. Perhaps it would be a better idea to show a table with borders and a table without borders. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/8.diff Simplify some parts of the manual page markup example, and fix all sendmail-related manual page sections from 8 to 1 (Whoops). http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/9.diff Host bento.FreeBSD.org does not exist. Replace it with pointyhat. Let us have a working example. http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/10.diff I think the example for elements includes some unnecessary tags :) http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/11.diff Add missing parentheses. Thanks for the replies. Regards, :g [1] http://www.freebsd.org/doc/en/books/fdp-primer/sgml-markup.html [2] http://www.freebsd.org/doc/en/books/fdp-primer/ From gabor at FreeBSD.org Fri Nov 28 18:06:50 2008 From: gabor at FreeBSD.org (=?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?=) Date: Fri Nov 28 18:06:57 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer In-Reply-To: <49309E91.7050006@FreeBSD.org> References: <49309E91.7050006@FreeBSD.org> Message-ID: <4930A131.60108@FreeBSD.org> Wow! The new pgj patchbombs are arriving. :) > > http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/2.diff > > Oh, yeah. Ports Collection should be capitalized. > We could even put   between them. It is a proper name, it would look strange separated. > > http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/3.diff > > I think word "of" should be "or" because we are talking about "rowspan > and/or colspan attributes", so it would rhyme with "number of rows or > columns" or "number of rows and/or columns". > I think you are right here. And I agree with the other ones, as well, I think they are all reasonable suggestions. Best, -- Gabor Kovesdan EMAIL: gabor@FreeBSD.org WWW: http://www.kovesdan.org From pgj at FreeBSD.org Fri Nov 28 18:10:07 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Nov 28 18:10:19 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer In-Reply-To: <4930A131.60108@FreeBSD.org> References: <49309E91.7050006@FreeBSD.org> <4930A131.60108@FreeBSD.org> Message-ID: <4930A475.2010908@FreeBSD.org> G?bor K?vesd?n wrote: > Wow! The new pgj patchbombs are arriving. :) > Sorry, I think I missed to upload and link the largest one: http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/0.diff In this patch, I suggest a capitalization according to the "headline style" of Chicago Manual of Style (15th Edition), paragraph 8.167. Thanks! :g From sonic2000gr at gmail.com Fri Nov 28 22:52:04 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Fri Nov 28 22:52:10 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer In-Reply-To: <4930A475.2010908@FreeBSD.org> References: <49309E91.7050006@FreeBSD.org> <4930A131.60108@FreeBSD.org> <4930A475.2010908@FreeBSD.org> Message-ID: <4930E68E.4090903@gmail.com> Gabor PALI wrote: > G?bor K?vesd?n wrote: > >> Wow! The new pgj patchbombs are arriving. :) >> >> > > Sorry, I think I missed to upload and link the largest one: > > http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/0.diff > > In this patch, I suggest a capitalization according to the "headline > style" of Chicago Manual of Style (15th Edition), paragraph 8.167. > > > Thanks! > > :g > _______________________________________________ > All the patches look fine to me too ;) Funny what subtle (and sometimes not so subtle) things can one find while translating... manolis@ From r.c.ladan at gmail.com Sat Nov 29 05:47:42 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Sat Nov 29 05:47:48 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer In-Reply-To: <4930A475.2010908@FreeBSD.org> References: <49309E91.7050006@FreeBSD.org> <4930A131.60108@FreeBSD.org> <4930A475.2010908@FreeBSD.org> Message-ID: 2008/11/29 Gabor PALI : > G?bor K?vesd?n wrote: >> Wow! The new pgj patchbombs are arriving. :) >> > > Sorry, I think I missed to upload and link the largest one: > > http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/0.diff > > In this patch, I suggest a capitalization according to the "headline > style" of Chicago Manual of Style (15th Edition), paragraph 8.167. > > The patches look fine to me. Maybe you can replace some instances of "FreeBSD" with "&os;" while you're at it. I'm slightly amazed that the book built with incorrect tags (see patch 11). But the documentation seems to build with missing end tags in general. Is there a way to check this automatically? Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From gabor at FreeBSD.org Sat Nov 29 06:06:33 2008 From: gabor at FreeBSD.org (=?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?=) Date: Sat Nov 29 06:06:39 2008 Subject: RFR: A Pack of Patches for Chapter "SGML Markup" in FDP Primer In-Reply-To: References: <49309E91.7050006@FreeBSD.org> <4930A131.60108@FreeBSD.org> <4930A475.2010908@FreeBSD.org> Message-ID: <49314C64.7000203@FreeBSD.org> Rene Ladan escribi?: > 2008/11/29 Gabor PALI : > >> G?bor K?vesd?n wrote: >> >>> Wow! The new pgj patchbombs are arriving. :) >>> >>> >> Sorry, I think I missed to upload and link the largest one: >> >> http://people.freebsd.org/~pgj/patches/2008/11/29/doc.en.books.fdp-primer.sgml-markup.patch/0.diff >> >> In this patch, I suggest a capitalization according to the "headline >> style" of Chicago Manual of Style (15th Edition), paragraph 8.167. >> >> >> > The patches look fine to me. Maybe you can replace some instances of > "FreeBSD" with "&os;" while you're at it. > > I'm slightly amazed that the book built with incorrect tags > (see patch 11). > But the documentation seems to build with missing end tags in general. Is there > a way to check this automatically? > In fact, missing end tags are not always incorrect. :) This is a feature of SGML, which is not true any more in XML. Among the other ones it is one reason why XML is considered cleaner and more practical. SGML also contains some additonal markup minimalization techniques because in the glorious days of SGML, when the capacity of the media was an important bottleneck, it was considered to be an advantage. Some weird SGML examples: This is a paragraph with a filename. Hello there, A few weeks ago Joseph J. Barbish has contributed a section on boot time splash screens for the FreeBSD Handbook [1], and after a short discussion it was requested for comments whether to be really included it or not [2]. It received a very positive feedback on the topic, so I created the SGML version of it, that you can study in form of a patch [3] and a compiled HTML page [4]. Please, review, comment and send me your ideas on how to make it better (and fix it up). Obviously, because I am not a native speaker of English, it may contain mistakes (I am sure), so review of native speakers are the most welcome, however review of avid users of the presented boot time splash screen feature are also important for this patch. Thank you for the replies in advance. Cheers, :g PS: For your information, after its commit, I plan to rewrite the corresponding FAQ entry about splash screens to reference this section of the Handbook. [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html [2] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/015007.html [3] http://people.freebsd.org/~pgj/patches/2008/11/29/splash.screen.section.patch.diff [4] http://people.freebsd.org/~pgj/patches/2008/11/29/html/boot-blocks.html#BOOT-SPLASH From sonic2000gr at gmail.com Sat Nov 29 07:43:11 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Sat Nov 29 07:43:18 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <493155ED.8020004@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> Message-ID: <49316309.1050407@gmail.com> Gabor PALI wrote: > Hello there, > > A few weeks ago Joseph J. Barbish has contributed a section on boot time > splash screens for the FreeBSD Handbook [1], and after a short > discussion it was requested for comments whether to be really included > it or not [2]. It received a very positive feedback on the topic, so I > created the SGML version of it, that you can study in form of a patch > [3] and a compiled HTML page [4]. > > Please, review, comment and send me your ideas on how to make it better > (and fix it up). Obviously, because I am not a native speaker of > English, it may contain mistakes (I am sure), so review of native > speakers are the most welcome, however review of avid users of the > presented boot time splash screen feature are also important for this patch. > > Thank you for the replies in advance. > > Cheers, > :g > > > PS: For your information, after its commit, I plan to rewrite the > corresponding FAQ entry about splash screens to reference this section > of the Handbook. > > [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html > [2] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/015007.html > [3] > http://people.freebsd.org/~pgj/patches/2008/11/29/splash.screen.section.patch.diff > [4] > http://people.freebsd.org/~pgj/patches/2008/11/29/html/boot-blocks.html#BOOT-SPLASH > > Once again very nice work! Here are a few nits you may want to act on. I have not used splash screens for a long time as I don't need them (my desktop literally does not know what a 'reboot' is), so I can't tell about technical accuracy. It does seem ok though. "After the system finished booting, a virtual..." should probably be: "After the system finishes booting..." "...put the user in a graphical desktop" : I don't like using "put" for this (yes, my bikeshed is green), I would probably rephrase it to something like "...present the user with a graphical desktop" "Note that, a 320x200 ?splash screen? image will be displayed as a small block in the center of a solid white background screen." => I don't understand what you mean by this. Since the resolution at boot will be 320x200, the splash screen will still fill the entire screen. Do you mean to compare the size of the image to a typical desktop? "To support larger video resolutions up to the maximum of the video card is, activate...": The "is" here is obviously a mistake. You can rephrase this in a number of ways. I would go with something to avoid repeating words like "resolution" and "support" many times in the same sentence. Example: "To use larger images, up to the maximum resolution supported by {the|your} video card, activate..." "will change to the splash screen and cycles through": "cycle" instead of "cycles" While discussing text mode screensavers, it might be worth mentioning that you can get the list of available savers by ls /boot/kernel/*saver.ko or something along that line. " When a PCX file desired, use these statements plus.." => If a PCX file is desired... (the missing 'is' is the problem, you can keep "when") "It is not restricted to use ?splash? as file name,..." => Haha, let me revenge the passive voice here :) What you really want to say here is "You are not restricted to use "splash"..." but since we are not talking to the user, we must rephrase. You just can't start with "It" because at this point it does not refer to anything. Something like: "The file name is not really restricted to "splash" as shown in the above example. It can be anything..." "There are 2 another possible" => "There are another 2..." (or better, "two") "be still present" => "still be present" I also feel some longer sentences could use a few commas. I did not make any notes on these (I was too lazy...) but you will probably get them from reading the build. I've only peeked at the SGML, but I am sure there is nothing to fix there :) Cheers, manolis@ From lgusenet at be-well.ilk.org Sat Nov 29 09:57:24 2008 From: lgusenet at be-well.ilk.org (Lowell Gilbert) Date: Sat Nov 29 09:57:31 2008 Subject: tcsh man page In-Reply-To: <49305325.9070703@gmail.com> (Eitan Adler's message of "Fri\, 28 Nov 2008 15\:23\:01 -0500") References: <49305325.9070703@gmail.com> Message-ID: <44ljv2qw1t.fsf@lowell-desk.lan> eitanadlerlist@gmail.com (Eitan Adler) writes: > in man 1 tcsh > http://tcshrc.source-forge.net should not have the "-" > The relevant line in src/contrib/tcsh/tcsh.man is > \fIhttp://tcshrc.sourceforge.net\fR. > which does not have a - > Why does the "-" show up? How can it be fixed? That's the line-wrap caused by the URL being split across two lines. I'm not sure what the right fix would be; is there a way to keep a string from being split? Maybe forcing a newline first would be the best that can be done? And such a fix would have to be portable enough to be accept upstream... From yuri at tsoft.com Sat Nov 29 13:10:09 2008 From: yuri at tsoft.com (Yuri) Date: Sat Nov 29 13:10:15 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200811292104.mATL4EmQ005786@www.freebsd.org> >Number: 129281 >Category: docs >Synopsis: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 29 21:10:08 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Yuri >Release: 7.1-PRERELEASE >Organization: >Environment: >Description: In the Handbook section "18.6.5 Duplicating Audio CDs" it's recommended to treat SCSI and ATAPI drives differently. For ATAPI drives the use of dd/burncd combination is recommended. In reality burncd doesn't work on all drives -- there is a long standing bug: bin/118207: burncd(8) gives I/O error writing CD on Pioneer DVDR-112D/1.21 And 'cdrecord' command that I tried instead expects different endianness than the one produced by 'dd'. Also 'dd' command doesn't always work on audio devices, here is the excerpt from the conversation with Joerg Schilling where he expressed these arguments: Here is a list of cons for dd even on FreeBSD: - dd may not work with all drives - Do you know what byteorder you get from a MMC CD-ROM drive on FreeBSD/Sparc? You would need network byteorder on Sparc but the MMC CD-ROM drive delivers intel byteorder due to a bug in the MMC standard cdrecord always asumes network byte order for RAW audio data, this is reasonable - Why would you deal with raw audio data at all if there are audio file formats that include a notation for byte order and sampling rates? - There is no jitter check and no quality control with dd on FreeBSD, cdda2wav works on all OS and has jitter control and qualiti control with e.g. libparanoia. - There is no way to get the correct CD structure back if you use dd. Cdda2wav reads meta-data and puts them into *.inf files. - With dd, you cannot read intentionally defective media as sold by the music mafia. It's much better to always deal with endianness-safe commands/formats. My proposition: Sub-section "ATAPI Drives" should be deleted. Title of "SCSI Drives" should be changed to "SCSI/ATAPI Drives". ATAPI drives are exposed as SCSI devices so there should be no problem. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From EitanAdlerList at gmail.com Sat Nov 29 20:20:01 2008 From: EitanAdlerList at gmail.com (Eitan Adler) Date: Sat Nov 29 20:20:08 2008 Subject: docs/129285: [patch] df man page Message-ID: <200811300418.mAU4IuIf057122@www.freebsd.org> >Number: 129285 >Category: docs >Synopsis: [patch] df man page >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 30 04:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Eitan Adler >Release: -CURRENT >Organization: >Environment: N/A >Description: df was updated in r185200 to include a -T option. This is yet undocumented. >How-To-Repeat: man df >Fix: --- df.1.old 2008-11-29 23:16:18.000000000 -0500 +++ df.1 2008-11-29 23:15:49.000000000 -0500 @@ -140,6 +140,8 @@ .Xr lsvfs 1 command can be used to find out the types of file systems that are available on the system. +.It Fl T +File system type will be included in output. .El .Sh ENVIRONMENT .Bl -tag -width BLOCKSIZE >Release-Note: >Audit-Trail: >Unformatted: From eitanadlerlist at gmail.com Sat Nov 29 20:50:06 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sat Nov 29 20:50:15 2008 Subject: docs/129285: [patch] df man page Message-ID: <200811300450.mAU4o6dQ038101@freefall.freebsd.org> The following reply was made to PR docs/129285; it has been noted by GNATS. From: Eitan Adler To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/129285: [patch] df man page Date: Sat, 29 Nov 2008 23:22:27 -0500 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Updated patch: I forgot the line at the top - --- df.1.old 2008-11-29 23:16:18.000000000 -0500 +++ df.1 2008-11-29 23:19:12.000000000 -0500 @@ -37,7 +37,7 @@ .Nd display free disk space .Sh SYNOPSIS .Nm - -.Op Fl b | g | H | h | k | m | P +.Op Fl b | g | H | h | k | m | P | T .Op Fl aciln .Op Fl t Ar type .Op Ar file | filesystem ... @@ -140,6 +140,8 @@ .Xr lsvfs 1 command can be used to find out the types of file systems that are available on the system. +.It Fl T +File system type will be included in output. .El .Sh ENVIRONMENT .Bl -tag -width BLOCKSIZE - -- Eitan Adler GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkyFQMACgkQtl8kq+nCzNEQqQCeKisQS8+CaomclqN7sHvH4UmS h5gAni0JK8Aimqwjdk+6jA3nT9QQjfcZ =xKtx -----END PGP SIGNATURE----- From blackend at FreeBSD.org Sat Nov 29 23:50:06 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sat Nov 29 23:50:17 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200811300750.mAU7o6Mb009239@freefall.freebsd.org> The following reply was made to PR docs/129281; it has been noted by GNATS. From: Marc Fonvieille To: Yuri Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Date: Sun, 30 Nov 2008 08:46:34 +0100 On Sat, Nov 29, 2008 at 09:04:14PM +0000, Yuri wrote: > > >Number: 129281 > >Category: docs > >Synopsis: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Sat Nov 29 21:10:08 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: Yuri > >Release: 7.1-PRERELEASE > >Organization: > >Environment: > >Description: > In the Handbook section "18.6.5 Duplicating Audio CDs" it's recommended to treat SCSI and ATAPI drives differently. For ATAPI drives the use of dd/burncd combination is recommended. > > In reality burncd doesn't work on all drives -- there is a long standing bug: > bin/118207: burncd(8) gives I/O error writing CD on Pioneer DVDR-112D/1.21 > And 'cdrecord' command that I tried instead expects different > endianness than the one produced by 'dd'. > > Also 'dd' command doesn't always work on audio devices, here is the > excerpt from the conversation with Joerg Schilling > where he expressed these > arguments: > > > Here is a list of cons for dd even on FreeBSD: > > - dd may not work with all drives > > - Do you know what byteorder you get from a MMC CD-ROM drive > on FreeBSD/Sparc? You would need network byteorder on Sparc > but the MMC CD-ROM drive delivers intel byteorder due to a > bug in the MMC standard > > cdrecord always asumes network byte order for RAW audio data, > this is reasonable > > - Why would you deal with raw audio data at all if there are > audio file formats that include a notation for byte order and > sampling rates? > > - There is no jitter check and no quality control with dd on FreeBSD, > cdda2wav works on all OS and has jitter control and qualiti control > with e.g. libparanoia. > > - There is no way to get the correct CD structure back if you use dd. > Cdda2wav reads meta-data and puts them into *.inf files. > > - With dd, you cannot read intentionally defective media as sold by > the music mafia. > > > It's much better to always deal with endianness-safe commands/formats. > > My proposition: > Sub-section "ATAPI Drives" should be deleted. > Title of "SCSI Drives" should be changed to "SCSI/ATAPI Drives". > > ATAPI drives are exposed as SCSI devices so there should be no problem. The fact one or some burners fail with burncd(8) is not a reason to delete documentation. The "7.3.2 Ripping CD Audio Tracks" section documents cdda2wav for both interfaces. I'd not remove/rename the ATAPI Drives since it's a feature provided by FreeBSD, people are free to use or not the "/dev/acddtnn" feature especially when the ripped file can be directly used by burncd(8). (Don't forget both come with the base system). But I think we can slightly reword this "18.6.5 Duplicating Audio CDs" section to mention ATAPI interface supports both cdda2wav and dd(1) method and that cdda2wav may be a better choice in many cases. -- Marc From sziszi at bsd.hu Sun Nov 30 02:10:23 2008 From: sziszi at bsd.hu (Szilveszter Adam) Date: Sun Nov 30 02:10:30 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands In-Reply-To: <200811292104.mATL4EmQ005786@www.freebsd.org> References: <200811292104.mATL4EmQ005786@www.freebsd.org> Message-ID: <20081130093744.GA1800@baranyfelhocske.buza.adamsfamily.xx> On Sat, Nov 29, 2008 at 09:04:14PM +0000, Yuri wrote: > My proposition: > Sub-section "ATAPI Drives" should be deleted. > Title of "SCSI Drives" should be changed to "SCSI/ATAPI Drives". > > ATAPI drives are exposed as SCSI devices so there should be no problem. I do not particularly care for the self-advertisement of Joerg for his own software, but at least the last sentence is not true. On FreeBSD, exposing ATAPI devices as SCSI is just a choice that the user is free to make (or not). The use of the atapicam module or kernel option is just that, entirely optional. Also, atapicam may have at least as many problems with particular hardware/software combinations as burncd, so YMMV. I for one use burncd and I am perfectly happy with it. Note: One other reason people used to prefer "cdrecord" was that it was a standard staple on linux, and so a lot of pretty GUI frontends were written for it that do little more than call cdrecord with the correct arguments. For me, this is not important, burning from the command line just works(TM). -- Regards: Szilveszter ADAM Budapest Hungary From sziszi at bsd.hu Sun Nov 30 02:20:04 2008 From: sziszi at bsd.hu (Szilveszter Adam) Date: Sun Nov 30 02:20:11 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200811301020.mAUAK300030151@freefall.freebsd.org> The following reply was made to PR docs/129281; it has been noted by GNATS. From: Szilveszter Adam To: freebsd-doc@freebsd.org, freebsd-gnats-submit@freebsd.org Cc: Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Date: Sun, 30 Nov 2008 10:37:45 +0100 On Sat, Nov 29, 2008 at 09:04:14PM +0000, Yuri wrote: > My proposition: > Sub-section "ATAPI Drives" should be deleted. > Title of "SCSI Drives" should be changed to "SCSI/ATAPI Drives". > > ATAPI drives are exposed as SCSI devices so there should be no problem. I do not particularly care for the self-advertisement of Joerg for his own software, but at least the last sentence is not true. On FreeBSD, exposing ATAPI devices as SCSI is just a choice that the user is free to make (or not). The use of the atapicam module or kernel option is just that, entirely optional. Also, atapicam may have at least as many problems with particular hardware/software combinations as burncd, so YMMV. I for one use burncd and I am perfectly happy with it. Note: One other reason people used to prefer "cdrecord" was that it was a standard staple on linux, and so a lot of pretty GUI frontends were written for it that do little more than call cdrecord with the correct arguments. For me, this is not important, burning from the command line just works(TM). -- Regards: Szilveszter ADAM Budapest Hungary From maxim at FreeBSD.org Sun Nov 30 07:06:52 2008 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Sun Nov 30 07:07:03 2008 Subject: docs/129285: [patch] df man page Message-ID: <200811301506.mAUF6p1r087676@freefall.freebsd.org> Synopsis: [patch] df man page State-Changed-From-To: open->closed State-Changed-By: maxim State-Changed-When: Sun Nov 30 15:04:31 UTC 2008 State-Changed-Why: -T flag is documented in df(1) man page. http://www.freebsd.org/cgi/query-pr.cgi?pr=129285 From yuri at rawbw.com Sun Nov 30 10:50:04 2008 From: yuri at rawbw.com (Yuri) Date: Sun Nov 30 10:50:10 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200811301850.mAUIo3Ln078157@freefall.freebsd.org> The following reply was made to PR docs/129281; it has been noted by GNATS. From: Yuri To: Marc Fonvieille Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Date: Sun, 30 Nov 2008 10:18:56 -0800 Marc Fonvieille wrote: > But I think we can slightly reword this "18.6.5 Duplicating Audio CDs" > section to mention ATAPI interface supports both cdda2wav and dd(1) > method and that cdda2wav may be a better choice in many cases. > There is another pitfall of dd method: kern/115232: [ata] Audio CD tracks not displayed properly by atapi driver The warning about this should also be added to the section describing the use of dd/burncd method if this section is left there anyway. -- Yuri From blackend at FreeBSD.org Sun Nov 30 11:13:34 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sun Nov 30 11:13:41 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands In-Reply-To: <200811301850.mAUIo3Ln078157@freefall.freebsd.org> References: <200811301850.mAUIo3Ln078157@freefall.freebsd.org> Message-ID: <20081130191331.GB43869@gothic.blackend.org> On Sun, Nov 30, 2008 at 06:50:03PM +0000, Yuri wrote: > The following reply was made to PR docs/129281; it has been noted by GNATS. > > From: Yuri > To: Marc Fonvieille > Cc: freebsd-gnats-submit@FreeBSD.org > Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend > the use of non endianness safe dd/burncd commands > Date: Sun, 30 Nov 2008 10:18:56 -0800 > > Marc Fonvieille wrote: > > But I think we can slightly reword this "18.6.5 Duplicating Audio CDs" > > section to mention ATAPI interface supports both cdda2wav and dd(1) > > method and that cdda2wav may be a better choice in many cases. > > > > There is another pitfall of dd method: kern/115232: [ata] Audio CD > tracks not displayed properly by atapi driver > The warning about this should also be added to the section describing > the use of dd/burncd method This is documented: -- Make sure the appropriate files exist in /dev. If the entries are missing, force the system to retaste the media: # dd if=/dev/acd0 of=/dev/null count=1 -- which is a workaround to the problem you experienced. -- Marc From blackend at FreeBSD.org Sun Nov 30 11:20:03 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Sun Nov 30 11:20:09 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200811301920.mAUJK3IE000706@freefall.freebsd.org> The following reply was made to PR docs/129281; it has been noted by GNATS. From: Marc Fonvieille To: Yuri Cc: freebsd-doc@FreeBSD.org Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Date: Sun, 30 Nov 2008 20:13:31 +0100 On Sun, Nov 30, 2008 at 06:50:03PM +0000, Yuri wrote: > The following reply was made to PR docs/129281; it has been noted by GNATS. > > From: Yuri > To: Marc Fonvieille > Cc: freebsd-gnats-submit@FreeBSD.org > Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend > the use of non endianness safe dd/burncd commands > Date: Sun, 30 Nov 2008 10:18:56 -0800 > > Marc Fonvieille wrote: > > But I think we can slightly reword this "18.6.5 Duplicating Audio CDs" > > section to mention ATAPI interface supports both cdda2wav and dd(1) > > method and that cdda2wav may be a better choice in many cases. > > > > There is another pitfall of dd method: kern/115232: [ata] Audio CD > tracks not displayed properly by atapi driver > The warning about this should also be added to the section describing > the use of dd/burncd method This is documented: -- Make sure the appropriate files exist in /dev. If the entries are missing, force the system to retaste the media: # dd if=/dev/acd0 of=/dev/null count=1 -- which is a workaround to the problem you experienced. -- Marc From pgj at FreeBSD.org Sun Nov 30 13:49:40 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Sun Nov 30 13:49:46 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <49316309.1050407@gmail.com> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> Message-ID: <49330A66.8040801@FreeBSD.org> Manolis Kiagias wrote: > Here are a few nits you may want to act on. Thank you for your review. I fixed all the problems you pointed out and created a new version [1][2]. > I can't tell about technical accuracy. Hm, it seems I should really test the description myself :) > "Note that, a 320x200 ?splash screen? image will be displayed as a > small block in the center of a solid white background screen." => I > don't understand what you mean by this. Since the resolution at boot > will be 320x200, the splash screen will still fill the entire screen. > Do you mean to compare the size of the image to a typical desktop? To be honest, it was (blindly) imported from the original text. As far as I remember (I used splash screens about three years ago), it wants to tell you something like "if you have a 320x200 image but the resolution is higher, then it will be put in the middle of the screen". Anyway, I removed this sentence, since I do not see any clear connection with the other sentences. > While discussing text mode screensavers, it might be worth mentioning > that you can get the list of available savers by ls > /boot/kernel/*saver.ko or something along that line. Instead of this, I simply referenced the splash(4) manual page, it should be enough. > I also feel some longer sentences could use a few commas. I tried to insert those commas, and split some longer sentences up into smaller ones. > I've only peeked at the SGML, but I am sure there is nothing to fix > there :) Thank you for trusting my SGML skills :) Note for native speakers: please, review! Regards, :g [1] http://people.freebsd.org/~pgj/patches/2008/11/30/splash.screen.section.patch.diff [2] http://people.freebsd.org/~pgj/patches/2008/11/30/html/boot-blocks.html#BOOT-SPLASH