From pgj at FreeBSD.org Sun Jun 1 01:17:23 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Sun Jun 1 01:17:27 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <8c50a3c30805301341o3f78e173q2bda4d13be01830a@mail.gmail.com>
References: <483C6E04.3070804@otenet.gr> <20080528.060009.127260270.hrs@allbsd.org> <483C7AD4.5090409@otenet.gr>
<20080528.063631.13709725.hrs@allbsd.org> <483C83D1.40609@otenet.gr>
<20080528030745.GD27463@soaustin.net> <20080528022942.75859b86.trhodes@FreeBSD.org>
<8c50a3c30805301341o3f78e173q2bda4d13be01830a@mail.gmail.com>
Message-ID: <4841F89E.8030600@FreeBSD.org>
> I am rather fond of the way posgres does there docs/faqs, you have a
> uneditable part for consumption and below there is an area for people
> to comment on the entry [..]
> it gives the editors control over the official content and anybody who
> wants to the ability to comment on it. It also has the advantage of
> being a working system that we might be able to get for the asking.
I think this could be also implemented in a wiki. Just think about our
proposed "-current" wiki pages as an area to comment on an entry (or
think about the wiki Talk pages) and "-stable" wiki pages as the
distilled content.
Cheers,
-pgj@
From minimarmot at gmail.com Sun Jun 1 03:39:38 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Sun Jun 1 03:39:42 2008
Subject: Reminder of FAQs pr docs/115000
Message-ID: <47d0403c0805312012k215d0154mc5baf84600e8f056@mail.gmail.com>
Hi all,
Catching up on my email, I see that there has been some interest in
updating the FAQs (which is great!). I figured I could point out
that I have docs/115000 open with some small changes (though
it seems that some of them are outdated (6.3 is released, now),
but the snapshot changes seem to still be valid (and the paren).
I guess we can change the subject to be FreeBSD 6.x and 7.x, too :)
Thanks,
Ben Kaduk
From simon at FreeBSD.org Sun Jun 1 11:57:31 2008
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Sun Jun 1 11:57:33 2008
Subject: FreeBSD FTP docs not updated
Message-ID: <20080601114055.GC1140@zaphod.nitro.dk>
Hey,
Just FYI, the FreeBSD docs for the FTP sites
(ftp://ftp.freebsd.org/pub/FreeBSD/doc/) are not currently updated as
the system which builds them finally broke enough that the build can't
succeed anymore.
I will work on getting this fixed, but I don't have a date yet.
Before people ask, no there currently isn't anything other people can
do to fix this, but if you were thinking of helping, thanks anyway
:-).
PS. this build is totally seperate from what ends up on the web sites.
--
Simon L. Nielsen
Hat: FreeBSD.org admins team
From simon at FreeBSD.org Sun Jun 1 15:44:14 2008
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Sun Jun 1 15:44:17 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <483C6E04.3070804@otenet.gr>
References: <4839B6E6.8040706@kovesdan.org> <4839E1BE.4080803@otenet.gr>
<483AEC99.2060202@FreeBSD.org> <483B10BE.1070903@otenet.gr>
<483B36C6.3020608@FreeBSD.org> <483B3E98.6040804@otenet.gr>
<483B92D1.4040500@FreeBSD.org> <483C6E04.3070804@otenet.gr>
Message-ID: <20080601154411.GD1140@zaphod.nitro.dk>
On 2008.05.27 23:24:36 +0300, Manolis Kiagias wrote:
> - Create a wiki style FAQ (while still maintaining the current version of
> the FAQ) with a possible future plan to limit the original SGML FAQ to
> questions related to the way the Project works, rather than technical
> stuff.
Hey,
The FAQ is in sad state, so in generally I'm happy to see work on
fixing that, but...
Do note that the current FreeBSD wiki (wiki.freebsd.org) has limited
access so only committers and known contributors have access to edit
pages, and there are no current plans to change this policy - it's
simply too much work to maintain with an more open policy. The
alternative is of course to have some separate setup for the FAQ, but
the bar for getting new official FreeBSD.org sites etc. is high mainly
due to the extra administration required. E.g. the wiki ran several
years unofficially before it got a real FreeBSD.org name.
I don't want to discourage people coming up with new ideas - but do
note that a lot of work and persistence will be required for getting
things like this off the ground.
--
Simon L. Nielsen
Hat: Grumpy old admin for FreeBSD.org in general and the FreeBSD wiki
From sonicy at otenet.gr Sun Jun 1 17:45:01 2008
From: sonicy at otenet.gr (Manolis Kiagias)
Date: Sun Jun 1 17:45:05 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <20080601154411.GD1140@zaphod.nitro.dk>
References: <4839B6E6.8040706@kovesdan.org> <4839E1BE.4080803@otenet.gr>
<483AEC99.2060202@FreeBSD.org> <483B10BE.1070903@otenet.gr>
<483B36C6.3020608@FreeBSD.org> <483B3E98.6040804@otenet.gr>
<483B92D1.4040500@FreeBSD.org> <483C6E04.3070804@otenet.gr>
<20080601154411.GD1140@zaphod.nitro.dk>
Message-ID: <4842E038.8030206@otenet.gr>
Simon L. Nielsen wrote:
> On 2008.05.27 23:24:36 +0300, Manolis Kiagias wrote:
>
>
>> - Create a wiki style FAQ (while still maintaining the current version of
>> the FAQ) with a possible future plan to limit the original SGML FAQ to
>> questions related to the way the Project works, rather than technical
>> stuff.
>>
>
> Hey,
>
> The FAQ is in sad state, so in generally I'm happy to see work on
> fixing that, but...
>
> Do note that the current FreeBSD wiki (wiki.freebsd.org) has limited
> access so only committers and known contributors have access to edit
> pages, and there are no current plans to change this policy - it's
> simply too much work to maintain with an more open policy. The
> alternative is of course to have some separate setup for the FAQ, but
> the bar for getting new official FreeBSD.org sites etc. is high mainly
> due to the extra administration required. E.g. the wiki ran several
> years unofficially before it got a real FreeBSD.org name.
>
> I don't want to discourage people coming up with new ideas - but do
> note that a lot of work and persistence will be required for getting
> things like this off the ground.
>
>
Hi
This is more of an experiment at this time, if it is proved to be
successful, I am sure people will step up and help get it off the
ground. At the moment, wiki.freebsd.org will suffice.
From remko at FreeBSD.org Sun Jun 1 18:27:37 2008
From: remko at FreeBSD.org (Remko Lodder)
Date: Sun Jun 1 18:27:41 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <4842E038.8030206@otenet.gr>
References: <4839B6E6.8040706@kovesdan.org>
<4839E1BE.4080803@otenet.gr> <483AEC99.2060202@FreeBSD.org>
<483B10BE.1070903@otenet.gr> <483B36C6.3020608@FreeBSD.org>
<483B3E98.6040804@otenet.gr> <483B92D1.4040500@FreeBSD.org>
<483C6E04.3070804@otenet.gr> <20080601154411.GD1140@zaphod.nitro.dk>
<4842E038.8030206@otenet.gr>
Message-ID: <4842E1F0.9080207@FreeBSD.org>
Manolis Kiagias wrote:
>
>
> Simon L. Nielsen wrote:
>> On 2008.05.27 23:24:36 +0300, Manolis Kiagias wrote:
>>
>>
>>> - Create a wiki style FAQ (while still maintaining the current
>>> version of the FAQ) with a possible future plan to limit the original
>>> SGML FAQ to questions related to the way the Project works, rather
>>> than technical stuff.
>>>
>>
>> Hey,
>>
>> The FAQ is in sad state, so in generally I'm happy to see work on
>> fixing that, but...
>>
>> Do note that the current FreeBSD wiki (wiki.freebsd.org) has limited
>> access so only committers and known contributors have access to edit
>> pages, and there are no current plans to change this policy - it's
>> simply too much work to maintain with an more open policy. The
>> alternative is of course to have some separate setup for the FAQ, but
>> the bar for getting new official FreeBSD.org sites etc. is high mainly
>> due to the extra administration required. E.g. the wiki ran several
>> years unofficially before it got a real FreeBSD.org name.
>>
>> I don't want to discourage people coming up with new ideas - but do
>> note that a lot of work and persistence will be required for getting
>> things like this off the ground.
>>
>>
> Hi
>
> This is more of an experiment at this time, if it is proved to be
> successful, I am sure people will step up and help get it off the
> ground. At the moment, wiki.freebsd.org will suffice.
>
Hello,
Personally I do not see a real gain by using the wiki instead of the
sgml files at the moment. Only contributors and committers can modify
the wiki, which they can "Easily" do as well in the regular tree
(ok there is a little higher burden there that only committers can
access that part); but beyond that I think it's not a good idea to
move documentation over to various points. We are strong in centralized
documentation and writing, putting it on a wiki decentralizes that
concept and could have impact on our overall appreciation of the
documentation set (yes a FAQ is needed, no doubt about that but I
personally enfavor the dcvs tree for it).
Thanks,
Remko
--
/"\ Best regards, | remko@FreeBSD.org
\ / Remko Lodder | remko@EFnet
X http://www.evilcoder.org/ |
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
From danger at FreeBSD.org Sun Jun 1 20:34:20 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Sun Jun 1 20:34:22 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <4842E1F0.9080207@FreeBSD.org>
References: <4839B6E6.8040706@kovesdan.org> <4839E1BE.4080803@otenet.gr>
<483AEC99.2060202@FreeBSD.org> <483B10BE.1070903@otenet.gr>
<483B36C6.3020608@FreeBSD.org> <483B3E98.6040804@otenet.gr>
<483B92D1.4040500@FreeBSD.org> <483C6E04.3070804@otenet.gr>
<20080601154411.GD1140@zaphod.nitro.dk>
<4842E038.8030206@otenet.gr> <4842E1F0.9080207@FreeBSD.org>
Message-ID: <763137209.20080601223341@rulez.sk>
Hello,
Sunday, June 1, 2008, 7:52:48 PM, has been written:
> Personally I do not see a real gain by using the wiki instead of the
> sgml files at the moment. Only contributors and committers can modify
+1; unless we move the whole site under some kind of CMS.
--
Best regards,
Daniel mailto:danger@FreeBSD.org
From linimon at lonesome.com Sun Jun 1 20:35:03 2008
From: linimon at lonesome.com (Mark Linimon)
Date: Sun Jun 1 20:35:07 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <4842E1F0.9080207@FreeBSD.org>
References: <4839E1BE.4080803@otenet.gr> <483AEC99.2060202@FreeBSD.org>
<483B10BE.1070903@otenet.gr> <483B36C6.3020608@FreeBSD.org>
<483B3E98.6040804@otenet.gr> <483B92D1.4040500@FreeBSD.org>
<483C6E04.3070804@otenet.gr>
<20080601154411.GD1140@zaphod.nitro.dk>
<4842E038.8030206@otenet.gr> <4842E1F0.9080207@FreeBSD.org>
Message-ID: <20080601203502.GA18744@soaustin.net>
On Sun, Jun 01, 2008 at 07:52:48PM +0200, Remko Lodder wrote:
> Personally I do not see a real gain by using the wiki instead of the
> sgml files at the moment.
At the moment, I think you're right, but in the long-run, I think that
an experiment may really help us.
The information in the FAQ is years stale. My opinion has been for a
while that that means we are not doing something right. Some of the
"short-term" stuff is obviously out of place if it's not going to be
updated. Is the right place the handbook? or some intro articles? or
something users can also update? I don't know exactly, but IMHO it's
worth trying something.
mcl
From bugmaster at FreeBSD.org Mon Jun 2 11:06:07 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jun 2 11:06:28 2008
Subject: Current unassigned doc problem reports
Message-ID: <200806021106.m52B66JZ092269@freefall.freebsd.org>
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:
o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the
originator or the community - possibly confirmation of
the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or
confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on
a repocopy operation within the CVS repository which
is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information
or resources. This is a prime candidate
for somebody who is looking for a project to do.
If the problem cannot be solved at all,
it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated,
documented, and tested -- or when fixing the problem is abandoned.
Critical problems
Serious problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/27605 doc [patch] Cross-document references ()
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/116080 doc PREFIX is documented, but not the more important LOCAL
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
12 problems total.
Non-critical problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s docs/20028 doc ASCII docs should reflect tags in the sourc
o docs/24786 doc missing FILES descriptions in sa(4)
o docs/26286 doc *printf(3) etc should gain format string warnings
a docs/30008 doc [patch] French softupdates document should be translat
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556 doc EPS file of beastie, as addition to existing examples
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/43823 doc [PATCH] update to environ(7) manpage
o docs/47818 doc [patch] ln(1) manpage is confusing
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/50211 doc [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/53596 doc Updates to mt(1) manual page
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652 doc [patch] New man page: portindex(5)
o docs/75865 doc comments on "backup-basics" in handbook
o docs/75995 doc hcreate(3) documentation(?) bug
o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138 doc [patch] Error in pre-installation section of installat
o docs/78240 doc [patch] handbook: replace with aroun
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne
o docs/84265 doc [patch] chmod(1) manpage omits implication of setting
o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806 doc mdoc(7) manpage has section ordering problems
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128 doc loader.conf(5) autoboot_delay incompletly described
o docs/85187 doc [patch] find(1) manpage missing block info for -ls
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/95139 doc FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148 doc The description of which Intel chips have EM64T is out
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403 doc man security should mention that the usage of the X Wi
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608 doc fdc(4) debugging description staled
o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/107432 doc Handbook's default partitioning schema is out-of-date
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
a docs/108980 doc list of missing man pages
o docs/109115 doc add Ultra 450 to hardware list for sparc64
o docs/109201 doc [request]: manual for callbootd
f docs/109226 doc [request] No manual entry for sntp
o docs/109972 doc No manual entry for zless/bzless
o docs/109973 doc No manual entry for c++filt
o docs/109975 doc No manual entry for elf2aout
o docs/109977 doc No manual entry for ksu
o docs/109981 doc No manual entry for post-grohtml
o docs/109983 doc No manual entry for protoize
o docs/110061 doc [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110999 doc carp(4) should document unsupported interface types
o docs/111147 doc hostapd.conf is not documented
o docs/111263 doc [request] Information on $EDITOR variable in section 3
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111425 doc Missing chunks of text in historical manpages
o docs/112481 doc bug in ppp.linkup example
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115000 doc [PATCH] nits and updates to FAQs (part 1)
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/115921 doc Booting from pst(4) is not supported
o docs/116116 doc mktemp (3) re/move note
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument
f docs/117308 doc Clarification of /etc/defaults/devfs.rules status
o docs/117747 doc 'break' system call needs a man page
o docs/117798 doc formatting oddity in sysmouse(4)
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214 doc close(2) error returns incomplete
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329 doc [patch] Fix misleading man 1 split
o docs/119338 doc gprof(1) refers to unmentioned option "-c"
s docs/119404 doc [request] events page should list only last 2 years wo
a docs/119536 doc a few typos in French handbook (basics)
o docs/119746 doc l10n chapter of handbook (Russian Language)
o docs/119907 doc Ports compatibility
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/120040 doc handbook: diskless operation: populate root doesn't po
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120248 doc [patch] getaddrinfo() implementation on FreeBSD 7 is i
o docs/120357 doc [patch] zone.9 - document also the _arg versions of th
o docs/120539 doc Inconsistent ipfw's man page
o docs/120628 doc PAE documentation errror in handbook
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197 doc [patch] edits to books/porters-handbook
o docs/121321 doc Handbook should reflect new pf.conf defaults
s docs/121541 doc [request] no man pages for wlan_scan_ap
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121713 doc man page for su contains errornous example.
o docs/121721 doc telnetd(8) not describing -X authentication types
o docs/121821 doc [patch] wpa_supplicant.conf.5 - provide pointer to sam
o docs/121863 doc IPSEC handbook update for FreeBSD 7 and later
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/122052 doc minor update on handbook section 20.7.1
o docs/122053 doc updaze on vinum(4) reference to newfs(8)
o docs/122351 doc [patch] update to PF section of handbook
o docs/122470 doc [patch] exit status on fetch(1) manual page
o docs/122818 doc [patch] system.2 missing ".Sh RETURN VALUES"
o docs/123010 doc Misleading Documentation in gzip(1)
o docs/123019 doc [patch] mkdir(2) can return EMLINK, but EMLINK is not
o docs/123035 doc [patch] bugs in refuse.README
o docs/123038 doc [patch] update to projects/c99/index.sgml
o docs/123043 doc [patch] Update to articles/problem-reports/article.sgm
o docs/123044 doc [patch] Update to www/en/send-pr.sgml
o docs/123111 doc link only unidirectional between cpufreq(4) and powerd
o docs/123255 doc mistake in ng_bpf(4) manpage
o docs/123400 doc gvinum startup in handbook
o docs/123579 doc readelf man page has duplicate -u option
p docs/124166 doc fortune: instant-workstation tip should go
145 problems total.
From ecsd at transbay.net Tue Jun 3 23:35:15 2008
From: ecsd at transbay.net (Eric Dynamic)
Date: Tue Jun 3 23:35:20 2008
Subject: Where is info for fixing broken X11?
Message-ID: <4845C71E.2030805@transbay.net>
Whatever happened to X11, ports will no longer install because
the new ports assume the new X11 structure and I'm using the
old X11 structure.
I cannot locate Anything on the freebsd.org website that reminds
one what to do to bring the X11 system up-to-date so the rest
of the stuff will work. I have seen messages to that effect from
ports, but cannot find it now - and a search for "upgrade X11"
returns nothing pertinent (in top returned entries.)
Please indicate what I do to upgrade X11 in place, or refer me
to a URL for that info - thanks in advance.
-ecsd
From brooks at freebsd.org Tue Jun 3 23:45:57 2008
From: brooks at freebsd.org (Brooks Davis)
Date: Tue Jun 3 23:45:59 2008
Subject: Where is info for fixing broken X11?
In-Reply-To: <4845C71E.2030805@transbay.net>
References: <4845C71E.2030805@transbay.net>
Message-ID: <20080603234606.GA72616@lor.one-eyed-alien.net>
On Tue, Jun 03, 2008 at 03:35:10PM -0700, Eric Dynamic wrote:
> Whatever happened to X11, ports will no longer install because
> the new ports assume the new X11 structure and I'm using the
> old X11 structure.
>
> I cannot locate Anything on the freebsd.org website that reminds
> one what to do to bring the X11 system up-to-date so the rest
> of the stuff will work. I have seen messages to that effect from
> ports, but cannot find it now - and a search for "upgrade X11"
> returns nothing pertinent (in top returned entries.)
>
> Please indicate what I do to upgrade X11 in place, or refer me
> to a URL for that info - thanks in advance.
See the 20070519 entry in /usr/ports/UPDATING.
-- Brooks
-------------- 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/20080603/d611f5b1/attachment.pgp
From linimon at FreeBSD.org Wed Jun 4 00:52:22 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Jun 4 00:52:25 2008
Subject: docs/124253: Broken command in the handbook for configuring a
wireless access point
Message-ID: <200806040052.m540qMrL025697@freefall.freebsd.org>
Synopsis: Broken command in the handbook for configuring a wireless access point
Responsible-Changed-From-To: freebsd-bugs->freebsd-doc
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jun 4 00:52:07 UTC 2008
Responsible-Changed-Why:
docs PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=124253
From dougb at FreeBSD.org Wed Jun 4 02:03:03 2008
From: dougb at FreeBSD.org (Doug Barton)
Date: Wed Jun 4 02:03:07 2008
Subject: Where is info for fixing broken X11?
In-Reply-To: <4845C71E.2030805@transbay.net>
References: <4845C71E.2030805@transbay.net>
Message-ID: <4845F195.5090307@FreeBSD.org>
Eric Dynamic wrote:
> Please indicate what I do to upgrade X11 in place, or refer me
> to a URL for that info - thanks in advance.
/usr/ports/UPDATING should always be your first place to look.
good luck,
Doug
--
This .signature sanitized for your protection
From trhodes at FreeBSD.org Wed Jun 4 08:52:08 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Wed Jun 4 09:00:05 2008
Subject: Wiki style FAQ proposal
In-Reply-To: <8c50a3c30805301341o3f78e173q2bda4d13be01830a@mail.gmail.com>
References: <483C6E04.3070804@otenet.gr>
<20080528.060009.127260270.hrs@allbsd.org>
<483C7AD4.5090409@otenet.gr>
<20080528.063631.13709725.hrs@allbsd.org>
<483C83D1.40609@otenet.gr> <20080528030745.GD27463@soaustin.net>
<20080528022942.75859b86.trhodes@FreeBSD.org>
<8c50a3c30805301341o3f78e173q2bda4d13be01830a@mail.gmail.com>
Message-ID: <20080530231355.4bf7d72c.trhodes@FreeBSD.org>
On Fri, 30 May 2008 16:41:07 -0400
"Marc Spitzer" wrote:
> On Wed, May 28, 2008 at 2:29 AM, Tom Rhodes wrote:
> > On Tue, 27 May 2008 22:07:45 -0500
> > linimon@lonesome.com (Mark Linimon) wrote:
> >
> >> On Wed, May 28, 2008 at 12:57:37AM +0300, Manolis Kiagias wrote:
> >> > In my opinion, the sgml FAQ should be limited to questions about the
> >> > project and maybe not so quickly changing technical stuff.
> >>
> >> This was my idea also the last time I looked at it (sigh) which appears
> >> to have been several years ago :-(
> >
> > With me at BSDCan actually. And I think we (or just I?) brought
> > the idea up with Murray. It never got off the ground sadly -
> > as have other efforts (see archives for my FAQ->Handbook patch)
> > and just a couple of weeks ago I was thinking of that FAQOMATIC.
> >
> > Then I was passed a work project and my desire to set one up
> > kind of bombed on me.
> >
> > --
> > 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"
> >
>
> I am rather fond of the way posgres does there docs/faqs, you have a
> uneditable part for consumption and below there is an area for people
> to comment on the entry:
> http://www.postgresql.org/docs/8.3/interactive/index.html
>
> it gives the editors control over the official content and anybody who
> wants to the ability to comment on it. It also has the advantage of
> being a working system that we might be able to get for the asking.
>
> Thanks,
>
> marc
>
> ps back to lurking ;)
> --
> Freedom is nothing but a chance to be better.
> Albert Camus
> _______________________________________________
> 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 gavin at FreeBSD.org Wed Jun 4 13:10:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Wed Jun 4 13:10:36 2008
Subject: docs/124269: [patch] More entries for the glossary
Message-ID: <200806041304.m54D4Twp033567@buffy.york.ac.uk>
>Number: 124269
>Category: docs
>Synopsis: [patch] More entries for the glossary
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jun 04 13:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Gavin Atkinson
>Release: FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
N/A
>Description:
More entries for the glossary. Also, cross reference a couple
of entries.
>How-To-Repeat:
N/A
>Fix:
--- glossary.diff begins here ---
Index: doc/en_US.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml
===================================================================
RCS file: /usr/cvs/doc/en_US.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml,v
retrieving revision 1.30
diff -u -r1.30 freebsd-glossary.sgml
--- doc/en_US.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml 28 May 2008 06:54:27 -0000 1.30
+++ doc/en_US.ISO8859-1/share/sgml/glossary/freebsd-glossary.sgml 4 Jun 2008 13:00:35 -0000
@@ -117,7 +117,8 @@
Access Control List
ACL
-
+ A list of permissions attached to an object, usually either a
+ file or a network device.
@@ -151,7 +152,11 @@
Advanced Power Management
APM
-
+ An API enabling the operating system to work
+ in conjunction with the BIOS in order to achieve
+ power management. APM has been superseded by
+ the much more generic and powerful ACPI
+ specification for most applications.
@@ -340,7 +345,8 @@
Challenge Handshake Authentication Protocol
CHAP
-
+ A method of authenticating a user, based on a secret shared
+ between client and server.
@@ -358,6 +364,7 @@
An RS232C signal giving the remote system
permission to send data.
+
@@ -455,6 +462,7 @@
An RS232C signal sent from the modem to the
computer or terminal indicating a readiness to send and receive
data.
+
@@ -482,7 +490,8 @@
Differentiated System Description Table
DSDT
-
+ An ACPI table, supplying basic configuration
+ information about the base system.
@@ -1135,7 +1144,9 @@
Network Address Translation
NAT
-
+ A tecnique where IP packets are rewritten
+ on the way through a gateway, enabling many machines behind the
+ gateway to effectively share a single IP address.
@@ -1161,7 +1172,7 @@
Network Time Protocol
NTP
-
+ A means of synchronizing clocks over a network.
@@ -1413,6 +1424,7 @@
POP
+
--- glossary.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
From gavin at FreeBSD.org Wed Jun 4 16:40:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Wed Jun 4 16:40:06 2008
Subject: docs/124277: [patch] Remove relative URLs from rendered text in
articles/version-guide
Message-ID: <200806041637.m54GbYE6034377@buffy.york.ac.uk>
>Number: 124277
>Category: docs
>Synopsis: [patch] Remove relative URLs from rendered text in articles/version-guide
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jun 04 16:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Gavin Atkinson
>Release: FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
N/A
>Description:
See http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/future-goals.html
Rather than absolute URLs, the rendered text contains relative URLs,
which look ugly. Absolute URLs are used everywhere else. I'm not suggesting
changing the link itself, just the way it is rendered.
>How-To-Repeat:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/future-goals.html
>Fix:
--- version-guide.diff begins here ---
Index: doc/en_US.ISO8859-1/articles/version-guide/article.sgml
===================================================================
RCS file: /usr/cvs/doc/en_US.ISO8859-1/articles/version-guide/article.sgml,v
retrieving revision 1.11
diff -u -r1.11 article.sgml
--- doc/en_US.ISO8859-1/articles/version-guide/article.sgml 4 Sep 2007 20:58:04 -0000 1.11
+++ doc/en_US.ISO8859-1/articles/version-guide/article.sgml 4 Jun 2008 16:32:55 -0000
@@ -302,14 +302,16 @@
-
+
+ &url.base;/releng/index.html#schedule
The Release Engineering Schedule
-
+
+ &url.base;/security/security.html#supported-branches
The Security Branch Schedule
--- version-guide.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
From clement.lavoillotte at free.fr Thu Jun 5 17:30:02 2008
From: clement.lavoillotte at free.fr (Clément Lavoillotte)
Date: Thu Jun 5 17:30:07 2008
Subject: docs/124306: ftpusers man page says /etc/ftpusers is mandatory to
enable ftp access, but it's not
Message-ID: <200806051725.m55HPCfU052588@www.freebsd.org>
>Number: 124306
>Category: docs
>Synopsis: ftpusers man page says /etc/ftpusers is mandatory to enable ftp access, but it's not
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jun 05 17:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Clément Lavoillotte
>Release: 6.3 and 7
>Organization:
iTeam
>Environment:
FreeBSD yellow.iteam.org 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:18:52 UTC 2008 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
According to ftpusers(5), "If the ftpusers file does not exist, all users are denied access.".
This appears to be incorrect. Since I can't find this feature in src/libexec/ftpd/ftpd.c, I suppose that the error is in the doc.
>How-To-Repeat:
- man ftpusers
- moving /etc/ftpusers to /etc/ftpusers.bak doesn't prevent user login
>Fix:
Remove the incorrect line from the doc.
>Release-Note:
>Audit-Trail:
>Unformatted:
From remko at FreeBSD.org Thu Jun 5 20:33:12 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Thu Jun 5 20:33:15 2008
Subject: docs/124306: ftpusers(5) man page says /etc/ftpusers is
mandatory to enable ftp access, but it's not
Message-ID: <200806052033.m55KXCUu089094@freefall.freebsd.org>
Synopsis: ftpusers(5) man page says /etc/ftpusers is mandatory to enable ftp access, but it's not
State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Thu Jun 5 20:33:12 UTC 2008
State-Changed-Why:
Lukemftpd has the ftusers(5).
http://www.freebsd.org/cgi/query-pr.cgi?pr=124306
From remko at FreeBSD.org Thu Jun 5 20:40:04 2008
From: remko at FreeBSD.org (Remko Lodder)
Date: Thu Jun 5 20:40:07 2008
Subject: docs/124306: ftpusers man page says /etc/ftpusers is mandatory
to enable ftp access, but it's not
Message-ID: <200806052040.m55Ke4Ba090131@freefall.freebsd.org>
The following reply was made to PR docs/124306; it has been noted by GNATS.
From: Remko Lodder
To: =?ISO-8859-1?Q?Cl=E9ment_Lavoillotte?=
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: docs/124306: ftpusers man page says /etc/ftpusers is mandatory
to enable ftp access, but it's not
Date: Thu, 05 Jun 2008 22:32:45 +0200
Clément Lavoillotte wrote:
You are wrong :-) We have two ftpd.c's.
# grep ftpusers /usr/src/contrib/lukemftpd/src/ftpd.c
/* check user in /etc/ftpusers, and setup class */
* Check if user is allowed by /etc/ftpusers
reply(0, "Deny bad ftpusers(5) quickly: %sabled",
lukemftpd has the ftpusers(5)..
--
/"\ Best regards, | remko@FreeBSD.org
\ / Remko Lodder | remko@EFnet
X http://www.evilcoder.org/ |
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
From clement.lavoillotte at free.fr Thu Jun 5 22:20:05 2008
From: clement.lavoillotte at free.fr (=?ISO-8859-1?Q?Cl=E9ment_Lavoillotte?=)
Date: Thu Jun 5 22:20:07 2008
Subject: docs/124306: ftpusers man page says /etc/ftpusers is mandatory
to enable ftp access, but it's not
Message-ID: <200806052220.m55MK5eP000837@freefall.freebsd.org>
The following reply was made to PR docs/124306; it has been noted by GNATS.
From: =?ISO-8859-1?Q?Cl=E9ment_Lavoillotte?=
To: Remko Lodder
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: docs/124306: ftpusers man page says /etc/ftpusers is mandatory to enable ftp access, but it's not
Date: Thu, 5 Jun 2008 23:53:43 +0200
Hi,
Ok sorry :)
Perhaps it should be mentioned in this line that it only applies to =20
lukemftpd ? It may be obvious for most users, but it wasn't for me =20
since I didn't see "lukemftpd" anywhere in ftpusers(5) [nor in ftpd(8) =20=
or the handbook ftpd page].
I'm quite new to FreeBSD, so I may not have searched long enough, but =20=
I think adding this note to the man page would help people like me to =20=
figure out the difference (and not to pollute your PR db) :)
Thanks for your time.
Regards,
Cl=E9ment
Le 5 juin 08 =E0 22:32, Remko Lodder a =E9crit :
> Cl=E9ment Lavoillotte wrote:
>
> You are wrong :-) We have two ftpd.c's.
>
> # grep ftpusers /usr/src/contrib/lukemftpd/src/ftpd.c
> /* check user in /etc/ftpusers, and setup =20
> class */
> * Check if user is allowed by /etc/ftpusers
> reply(0, "Deny bad ftpusers(5) quickly: %sabled",
>
>
> lukemftpd has the ftpusers(5)..
>
> --=20
>
> /"\ Best regards, | remko@FreeBSD.org
> \ / Remko Lodder | remko@EFnet
> X http://www.evilcoder.org/ |
> / \ ASCII Ribbon Campaign | Against HTML Mail and News
From gavin at FreeBSD.org Fri Jun 6 10:30:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Fri Jun 6 10:30:05 2008
Subject: docs/124347: [patch] Handbook CD-ROM retailers list is out of date
Message-ID: <200806061029.m56ATbiR043005@buffy.york.ac.uk>
>Number: 124347
>Category: docs
>Synopsis: [patch] Handbook CD-ROM retailers list is out of date
>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 Jun 06 10:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Gavin Atkinson
>Release: FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
N/A
>Description:
The list of CD-ROM suppliers at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html
has a couple of bad links, or points to domains now squatted. For links
that point to 404's, I've corrected them. Also removed "Linux CD Mall", as
according to their website, "The Linux CD Mall is now closed and I am no
longer shipping Linux or BSD on CD and DVD."
>How-To-Repeat:
>Fix:
--- handbook.mirrors.diff begins here ---
Index: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
===================================================================
RCS file: /usr/cvs/doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v
retrieving revision 1.443
diff -u -r1.443 chapter.sgml
--- doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml 6 Jan 2008 11:05:27 -0000 1.443
+++ doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml 6 Jun 2008 10:20:54 -0000
@@ -56,14 +56,6 @@
- BSD-Systems
- Email: info@bsd-systems.co.uk
- WWW:
-
-
-
-
-
FreeBSD Mall, Inc.
3623 Sanford Street
Concord, CA 94520-1405
@@ -107,17 +99,6 @@
- Linux CD Mall
- Private Bag MBE N348
- Auckland 1030
- New Zealand
- Phone: +64 21 866529
- WWW:
-
-
-
-
-
The Linux Emporium
Hilliard House, Lester Way
Wallingford
@@ -125,7 +106,7 @@
United Kingdom
Phone: +44 1491 837010
Fax: +44 1491 837016
- WWW:
+ WWW:
@@ -164,7 +145,7 @@
Russia
Phone: +7-812-3125208
Email: info@linuxcenter.ru
- WWW:
+ WWW:
--- handbook.mirrors.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org Fri Jun 6 16:23:58 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Fri Jun 6 16:24:00 2008
Subject: docs/115000: [PATCH] nits and updates to FAQs (part 1)
Message-ID: <200806061623.m56GNvbc042740@freefall.freebsd.org>
Synopsis: [PATCH] nits and updates to FAQs (part 1)
Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Fri Jun 6 16:20:27 UTC 2008
Responsible-Changed-Why:
Take.
http://www.freebsd.org/cgi/query-pr.cgi?pr=115000
From danger at FreeBSD.org Sat Jun 7 10:45:50 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Sat Jun 7 10:45:52 2008
Subject: docs/124306: ftpusers man page says /etc/ftpusers is
mandatory to enable ftp access, but it's not
In-Reply-To: <200806052220.m55MK5eP000837@freefall.freebsd.org>
References: <200806052220.m55MK5eP000837@freefall.freebsd.org>
Message-ID: <469281362.20080607124524@rulez.sk>
Hello Cl?ment,
Friday, June 6, 2008, 12:20:05 AM, you wrote:
> Perhaps it should be mentioned in this line that it only applies to =20
> lukemftpd ? It may be obvious for most users, but it wasn't for me =20
> since I didn't see "lukemftpd" anywhere in ftpusers(5) [nor in ftpd(8) =20=
>
The documentation of ftpds in the base system has been problematic for
years and it's a known problem; however nobody has ever really tried
to fix it.
When I got my commit bit I have proposed to remove either lukemftpd or
ftpd, because they both use very similar configuration files and the
man pages are so much confusing. Unfortunately that has never happened.
Somebody(tm) will need to take an axe and get the things right in the
future...
--
Best regards,
Daniel mailto:danger@FreeBSD.org
From gabor at FreeBSD.org Sat Jun 7 11:04:32 2008
From: gabor at FreeBSD.org (gabor@FreeBSD.org)
Date: Sat Jun 7 11:04:34 2008
Subject: docs/124269: [patch] More entries for the glossary
Message-ID: <200806071104.m57B4V2t009042@freefall.freebsd.org>
Synopsis: [patch] More entries for the glossary
Responsible-Changed-From-To: freebsd-doc->gabor
Responsible-Changed-By: gabor
Responsible-Changed-When: Sat Jun 7 11:04:20 UTC 2008
Responsible-Changed-Why:
Take.
http://www.freebsd.org/cgi/query-pr.cgi?pr=124269
From gabor at FreeBSD.org Sat Jun 7 11:04:48 2008
From: gabor at FreeBSD.org (gabor@FreeBSD.org)
Date: Sat Jun 7 11:04:49 2008
Subject: docs/124277: [patch] Remove relative URLs from rendered text in
articles/version-guide
Message-ID: <200806071104.m57B4ljj009078@freefall.freebsd.org>
Synopsis: [patch] Remove relative URLs from rendered text in articles/version-guide
Responsible-Changed-From-To: freebsd-doc->gabor
Responsible-Changed-By: gabor
Responsible-Changed-When: Sat Jun 7 11:04:20 UTC 2008
Responsible-Changed-Why:
Take.
http://www.freebsd.org/cgi/query-pr.cgi?pr=124277
From gabor at FreeBSD.org Sat Jun 7 11:05:06 2008
From: gabor at FreeBSD.org (gabor@FreeBSD.org)
Date: Sat Jun 7 11:05:08 2008
Subject: docs/124347: [patch] Handbook CD-ROM retailers list is out of
date
Message-ID: <200806071105.m57B56gC009126@freefall.freebsd.org>
Synopsis: [patch] Handbook CD-ROM retailers list is out of date
Responsible-Changed-From-To: freebsd-doc->gabor
Responsible-Changed-By: gabor
Responsible-Changed-When: Sat Jun 7 11:04:20 UTC 2008
Responsible-Changed-Why:
Take.
http://www.freebsd.org/cgi/query-pr.cgi?pr=124347
From danger at FreeBSD.org Sat Jun 7 11:17:07 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Sat Jun 7 11:17:10 2008
Subject: docs/124306: ftpusers(5) man page says /etc/ftpusers is
mandatory to enable ftp access, but it's not
In-Reply-To: <200806052033.m55KXCUu089094@freefall.freebsd.org>
References: <200806052033.m55KXCUu089094@freefall.freebsd.org>
Message-ID: <8810081063.20080607131641@rulez.sk>
Hello remko,
Thursday, June 5, 2008, 10:33:12 PM, you wrote:
> Synopsis: ftpusers(5) man page says /etc/ftpusers is mandatory to enable ftp access, but it's not
> Lukemftpd has the ftusers(5).
ftpd(8) has the ftpusers too, but its purpose is somewhat different.
While the lukemftpd's ftpusers provides access control for lukemftpd,
the /etc/ftpusers file lists users disallowed to log in over ftp when
used by ftpd(8).
--
Best regards,
Daniel mailto:danger@FreeBSD.org
From m.seaman at infracaninophile.co.uk Sat Jun 7 12:10:12 2008
From: m.seaman at infracaninophile.co.uk (Matthew Seaman)
Date: Sat Jun 7 12:10:15 2008
Subject: docs/124306: ftpusers(5) man page says /etc/ftpusers
is mandatory to enable ftp access, but it's not
In-Reply-To: <8810081063.20080607131641@rulez.sk>
References: <200806052033.m55KXCUu089094@freefall.freebsd.org>
<8810081063.20080607131641@rulez.sk>
Message-ID: <484A7A9C.6030407@infracaninophile.co.uk>
Daniel Gerzo wrote:
> Hello remko,
>
> Thursday, June 5, 2008, 10:33:12 PM, you wrote:
>
>> Synopsis: ftpusers(5) man page says /etc/ftpusers is mandatory to enable ftp access, but it's not
>> Lukemftpd has the ftusers(5).
>
> ftpd(8) has the ftpusers too, but its purpose is somewhat different.
> While the lukemftpd's ftpusers provides access control for lukemftpd,
> the /etc/ftpusers file lists users disallowed to log in over ftp when
> used by ftpd(8).
lukemftpd ftpusers file is a superset of the standard ftpusers
function -- if ftpusers just consists of a list of login names
then the effect is the same in either ftpd or lukemftpd: none of
the named users can log in via ftp. Of course, you can do a lot
more with lukemftpd's ftpusers file, but not without breaking
compatibility with ftpd.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080607/b0982903/signature.pgp
From jhb at FreeBSD.org Sat Jun 7 13:20:02 2008
From: jhb at FreeBSD.org (John Baldwin)
Date: Sat Jun 7 13:20:05 2008
Subject: docs/124373: exports(5) doesn't mention network prefixes or IPv6
Message-ID: <200806071316.m57DG1pZ090285@www.freebsd.org>
>Number: 124373
>Category: docs
>Synopsis: exports(5) doesn't mention network prefixes or IPv6
>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: Sat Jun 07 13:20:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: John Baldwin
>Release: 8-CURRENT, 6.3-RELEASE
>Organization:
>Environment:
>Description:
Back in the 5.x days when the ti-rpc RPC code was brought in, mountd was updated to support IPv6. This includes putting IPv6 addresses in /etc/exports for the -network flag. Also, any network address can now be followed by an optional /prefix instead of using -netmask. Thus, instead of:
/foo -network 192.168.0.0 -netmask 255.255.255.0
you can now do:
/foo -network 192.168.0.0/24
You can also do this now for IPv6:
/foo -network 1:2:3:4::/64
The exports(5) manpage was never updated to document this however and I only found out when I went to look at the code. I'm actually using IPv6 and /prefix on a box running 6.3, but have verified that HEAD's exports(5) is still missing the data.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From laoxue888888 at yahoo.cn Sun Jun 8 17:30:21 2008
From: laoxue888888 at yahoo.cn (Seven)
Date: Sun Jun 8 18:03:02 2008
Subject: docs/124306: ftpusers man page says /etc/ftpusers is mandatory to
enable ftp access, but it's not
Message-ID: <128044.8482.qm@web92207.mail.cnh.yahoo.com>
Seven
___________________________________________________________
????????????
http://cn.mail.yahoo.com/
From david at catwhisker.org Mon Jun 9 03:30:03 2008
From: david at catwhisker.org (David Wolfskill)
Date: Mon Jun 9 03:30:06 2008
Subject: docs/124406: New mailing list freebsd-wip-status
Message-ID: <200806090324.m593OsDQ083742@bunrab.catwhisker.org>
>Number: 124406
>Category: docs
>Synopsis: New mailing list freebsd-wip-status
>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 Jun 09 03:30:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: David Wolfskill
>Release: FreeBSD 6.3-STABLE i386
>Organization:
Wolfskill & Dowling Residence
>Environment:
System: FreeBSD g1-18.catwhisker.org 6.3-STABLE FreeBSD 6.3-STABLE #629: Fri Jun 6 05:03:26 PDT 2008 root@g1-18.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386
>Description:
New mailing list freebsd-wip-status created; this PR updates docs
accordingly (well, mostly).
>How-To-Repeat:
Note discrepancy between mailing lists shown at (e.g.) vs. those shown at .
>Fix:
Below will likely need some vetting, redaction, and other
editorial exercises. :-}
Index: en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
===================================================================
RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v
retrieving revision 1.184
diff -u -r1.184 chapter.sgml
--- en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 28 May 2008 00:40:13 -0000 1.184
+++ en_US.ISO8859-1/books/handbook/eresources/chapter.sgml 9 Jun 2008 03:16:05 -0000
@@ -576,6 +576,11 @@
+ &a.wip-status.name;
+ FreeBSD Work-In-Progress Status
+
+
+
&a.www.name;
Maintainers of www.FreeBSD.org
@@ -1522,6 +1527,33 @@
+
+ &a.wip-status.name;
+
+
+ FreeBSD Work-In-Progress Status
+
+ This mailing list can be used to announce creation
+ and progress of your FreeBSD related work. Messages
+ will be moderated. It is suggested to send the message
+ ``To:'' a more topical FreeBSD list and only ``BCC:''
+ this list. This way your WIP can also be discussed on
+ the topical list, as no discussion is allowed on this
+ list.
+
+ Look inside the archives for examples of suitable
+ messages.
+
+ An editorial digest of the messages to this list
+ might be posted to the FreeBSD website every few month
+ as part of the Status Reports[1]. You can find more
+ examples and past reports there, too.
+
+ [1] http://www.freebsd.org/news/status/
+
+
+
+
Index: en_US.ISO8859-1/share/sgml/mailing-lists.ent
===================================================================
RCS file: /cvs/freebsd/doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent,v
retrieving revision 1.58
diff -u -r1.58 mailing-lists.ent
--- en_US.ISO8859-1/share/sgml/mailing-lists.ent 28 May 2008 00:40:13 -0000 1.58
+++ en_US.ISO8859-1/share/sgml/mailing-lists.ent 9 Jun 2008 03:17:13 -0000
@@ -428,6 +428,10 @@
infrastructure">
freebsd-vuxml">
+
+FreeBSD Work-In-Progress Status">
+freebsd-wip-status">
+
FreeBSD Webmaster mailing list">
freebsd-www">
>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org Mon Jun 9 11:06:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jun 9 11:06:39 2008
Subject: Current unassigned doc problem reports
Message-ID: <200806091106.m59B66FX069826@freefall.freebsd.org>
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:
o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the
originator or the community - possibly confirmation of
the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or
confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on
a repocopy operation within the CVS repository which
is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information
or resources. This is a prime candidate
for somebody who is looking for a project to do.
If the problem cannot be solved at all,
it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated,
documented, and tested -- or when fixing the problem is abandoned.
Critical problems
Serious problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/27605 doc [patch] Cross-document references ()
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/116080 doc PREFIX is documented, but not the more important LOCAL
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
12 problems total.
Non-critical problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s docs/20028 doc ASCII docs should reflect tags in the sourc
o docs/24786 doc missing FILES descriptions in sa(4)
o docs/26286 doc *printf(3) etc should gain format string warnings
a docs/30008 doc [patch] French softupdates document should be translat
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556 doc EPS file of beastie, as addition to existing examples
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/43823 doc [PATCH] update to environ(7) manpage
o docs/47818 doc [patch] ln(1) manpage is confusing
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/50211 doc [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/53596 doc Updates to mt(1) manual page
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652 doc [patch] New man page: portindex(5)
o docs/75865 doc comments on "backup-basics" in handbook
o docs/75995 doc hcreate(3) documentation(?) bug
o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138 doc [patch] Error in pre-installation section of installat
o docs/78240 doc [patch] handbook: replace with aroun
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne
o docs/84265 doc [patch] chmod(1) manpage omits implication of setting
o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806 doc mdoc(7) manpage has section ordering problems
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128 doc loader.conf(5) autoboot_delay incompletly described
o docs/85187 doc [patch] find(1) manpage missing block info for -ls
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/95139 doc FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148 doc The description of which Intel chips have EM64T is out
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403 doc man security should mention that the usage of the X Wi
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608 doc fdc(4) debugging description staled
o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/107432 doc Handbook's default partitioning schema is out-of-date
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
a docs/108980 doc list of missing man pages
o docs/109115 doc add Ultra 450 to hardware list for sparc64
o docs/109201 doc [request]: manual for callbootd
f docs/109226 doc [request] No manual entry for sntp
o docs/109972 doc No manual entry for zless/bzless
o docs/109973 doc No manual entry for c++filt
o docs/109975 doc No manual entry for elf2aout
o docs/109977 doc No manual entry for ksu
o docs/109981 doc No manual entry for post-grohtml
o docs/109983 doc No manual entry for protoize
o docs/110061 doc [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110999 doc carp(4) should document unsupported interface types
o docs/111147 doc hostapd.conf is not documented
o docs/111263 doc [request] Information on $EDITOR variable in section 3
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111425 doc Missing chunks of text in historical manpages
o docs/112481 doc bug in ppp.linkup example
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/115921 doc Booting from pst(4) is not supported
o docs/116116 doc mktemp (3) re/move note
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument
f docs/117308 doc Clarification of /etc/defaults/devfs.rules status
o docs/117747 doc 'break' system call needs a man page
o docs/117798 doc formatting oddity in sysmouse(4)
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214 doc close(2) error returns incomplete
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329 doc [patch] Fix misleading man 1 split
o docs/119338 doc gprof(1) refers to unmentioned option "-c"
s docs/119404 doc [request] events page should list only last 2 years wo
a docs/119536 doc a few typos in French handbook (basics)
o docs/119746 doc l10n chapter of handbook (Russian Language)
o docs/119907 doc Ports compatibility
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/120040 doc handbook: diskless operation: populate root doesn't po
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120248 doc [patch] getaddrinfo() implementation on FreeBSD 7 is i
o docs/120357 doc [patch] zone.9 - document also the _arg versions of th
o docs/120539 doc Inconsistent ipfw's man page
o docs/120628 doc PAE documentation errror in handbook
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197 doc [patch] edits to books/porters-handbook
o docs/121321 doc Handbook should reflect new pf.conf defaults
s docs/121541 doc [request] no man pages for wlan_scan_ap
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121713 doc man page for su contains errornous example.
o docs/121721 doc telnetd(8) not describing -X authentication types
o docs/121821 doc [patch] wpa_supplicant.conf.5 - provide pointer to sam
o docs/121863 doc IPSEC handbook update for FreeBSD 7 and later
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/122052 doc minor update on handbook section 20.7.1
o docs/122053 doc [patch] update on vinum(4) reference to newfs(8)
o docs/122351 doc [patch] update to PF section of handbook
o docs/122470 doc [patch] exit status on fetch(1) manual page
o docs/122818 doc [patch] system.2 missing ".Sh RETURN VALUES"
o docs/123010 doc Misleading Documentation in gzip(1)
o docs/123019 doc [patch] mkdir(2) can return EMLINK, but EMLINK is not
o docs/123035 doc [patch] bugs in refuse.README
o docs/123038 doc [patch] update to projects/c99/index.sgml
o docs/123043 doc [patch] Update to articles/problem-reports/article.sgm
o docs/123044 doc [patch] Update to www/en/send-pr.sgml
o docs/123111 doc link only unidirectional between cpufreq(4) and powerd
o docs/123255 doc mistake in ng_bpf(4) manpage
o docs/123400 doc gvinum startup in handbook
o docs/123579 doc readelf man page has duplicate -u option
p docs/124166 doc fortune: instant-workstation tip should go
o docs/124253 doc Broken command in the handbook for configuring a wirel
o docs/124373 doc exports(5) doesn't mention network prefixes or IPv6
o docs/124406 doc New mailing list freebsd-wip-status
147 problems total.
From dindin at yandex-team.ru Mon Jun 9 14:56:01 2008
From: dindin at yandex-team.ru (Denis Barov)
Date: Mon Jun 9 14:56:05 2008
Subject: Documentation in SGML
In-Reply-To: <20080609144316.GD15238@sepulca.yandex.ru>
References: <20080609144316.GD15238@sepulca.yandex.ru>
Message-ID: <20080609145558.GE15238@sepulca.yandex.ru>
Sorry for dumb question, problem solved.
Mon, Jun 09, 2008 at 18:43 +0400 Denis Barov:
>
> Hello, list.
>
> Can I get dogumentation in SGML-format? If yes - where and how?
>
> --
> Cheers
> Denis Barov
--
Cheers
Denis Barov
From dindin at yandex-team.ru Mon Jun 9 15:05:39 2008
From: dindin at yandex-team.ru (Denis Barov)
Date: Mon Jun 9 15:05:49 2008
Subject: Documentation in SGML
Message-ID: <20080609144316.GD15238@sepulca.yandex.ru>
Hello, list.
Can I get dogumentation in SGML-format? If yes - where and how?
--
Cheers
Denis Barov
From edwin at mavetju.org Tue Jun 10 13:50:02 2008
From: edwin at mavetju.org (Edwin Groothuis)
Date: Tue Jun 10 13:50:09 2008
Subject: docs/124447: [patch] Bring www/en/multimedia into the age of SGML
Message-ID: <20080610134618.4D8388C@k7.mavetju>
>Number: 124447
>Category: docs
>Synopsis: [patch] Bring www/en/multimedia into the age of SGML
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: maintainer-update
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 10 13:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Edwin Groothuis
>Release: FreeBSD 7.0-RELEASE-p1 i386
>Organization:
-
>Environment:
System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed May 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386
>Description:
In cooperation with keramida@:
- Let the conversion script produce SGML output.
- Let the SGML files be translated the normal way to HTML files.
- Cleanup markup on input file to make sure that tidy likes it.
>How-To-Repeat:
>Fix:
Index: Makefile
===================================================================
RCS file: /home/dcvs/www/en/multimedia/Makefile,v
retrieving revision 1.2
diff -u -r1.2 Makefile
--- Makefile 15 May 2007 21:53:43 -0000 1.2
+++ Makefile 10 Jun 2008 13:10:19 -0000
@@ -10,30 +10,30 @@
.include "Makefile.inc"
.endif
-INDEXLINK= multimedia.html
-
-FXML = multimedia-input.xml
-FHTML = \
- multimedia.html.intro \
- multimedia.html.pre \
- multimedia.html.post
-FLIST = multimedia.created
-FSCRIPT = multimedia.pl
-
-.if exists(${FLIST})
-DATA!= cat ${FLIST}
-.else
-DATA= ${INDEXLINK}
-.endif
-
-all: ${FLIST}
+#all: build
+all: build
+ cd output && make all DIRPRFX=multimedia/output/
+
+install:
+ cd output && make install DIRPRFX=multimedia/output/
+
+TEMPLATES= multimedia.sgml.intro \
+ multimedia.sgml.post \
+ multimedia.sgml.pre \
+ multimedia.html.intro \
+ multimedia.html.post \
+ multimedia.html.pre \
+ multimedia-input.xml
clean:
- if test -f ${FLIST} ; then \
- xargs ${RM} < ${FLIST} && ${RM} ${FLIST} ; \
- fi
+ -${RM} output/*
-${FLIST}: ${FSCRIPT} ${FXML} ${FHTML}
- perl -Tw ${FSCRIPT}
+build:
+ (test -d output || ${MKDIR} output ) && \
+ cd output && \
+ ${LN} -fs ../Makefile.output Makefile && \
+ ( for f in ${TEMPLATES}; do ${LN} -fs ../$$f $$f; done ) && \
+ ${PERL} -Tw ../multimedia.pl && \
+ ${RM} -f *.html
.include "${WEB_PREFIX}/share/mk/web.site.mk"
Index: Makefile.inc
===================================================================
RCS file: Makefile.inc
diff -N Makefile.inc
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Makefile.inc 10 Jun 2008 13:10:19 -0000
@@ -0,0 +1,4 @@
+# $FreeBSD$
+
+WEBBASE?= /data/multimedia
+WEB_PREFIX?= ${.CURDIR}/../../..
Index: Makefile.output
===================================================================
RCS file: Makefile.output
diff -N Makefile.output
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Makefile.output 10 Jun 2008 13:10:19 -0000
@@ -0,0 +1,15 @@
+.if exists(../../Makefile.conf)
+.include "../../Makefile.conf"
+.endif
+.if exists(../../Makefile.inc)
+.include "../../Makefile.inc"
+.endif
+
+DOCS!= cat multimedia.sgml.created
+DATA= multimedia.xml
+
+WEBDIR= multimedia
+
+WEB_PREFIX:= ${WEB_PREFIX}/../
+
+.include "${WEB_PREFIX}/share/mk/web.site.mk"
Index: multimedia-input.xml
===================================================================
RCS file: /home/dcvs/www/en/multimedia/multimedia-input.xml,v
retrieving revision 1.3
diff -u -r1.3 multimedia-input.xml
--- multimedia-input.xml 30 May 2008 15:25:11 -0000 1.3
+++ multimedia-input.xml 10 Jun 2008 13:10:33 -0000
@@ -317,12 +317,12 @@
Certification.
See the following links for more information:
+
- - https://register.bsdcertification.org/register/get-a-bsdcg-id
-
- http://reedmedia.net/books/freebsd-basics
-
- http://www.osbr.ca
+
- https://register.bsdcertification.org/register/get-a-bsdcg-id
+ - http://reedmedia.net/books/freebsd-basics
+ - http://www.osbr.ca
-
]]>
http://bsdtalk.blogspot.com/2008/01/bsdtalk139-dru-lavigne.html
bsdtalk,interview,dru lavigne,the best of freebsd basics
@@ -347,17 +347,19 @@
-
Central Syslog
Setting up a central syslog server.
+
- - If you are concerned about the security of your logs, use a dedicated machine and lock it down.
-
- Keep clocks in sync.
-
- You may need to change log rotation schedule in /etc/newsyslog.conf. You can rotate based in size and/or time. This can be as much a policy decision as a hardware decision.
-
- On central log host, change syslogd flags to listen to network. Each BSD does this differently, so check the man pages. Also, check out the -n flag for busy environments.
-
- Make sure host firewall allows syslog traffic through.
-
- Be careful to limit syslog traffic to just the trusted network or hosts. FreeBSD man page refers to syslogd as a "remote disk filling service".
-
- For heavy logging environments, it is important to have a dedicated network. A down syslogd server can create a lot of "ARP who-has" broadcasts.
-
- Most network devices such as printers and commercial firewalls support sending to a central syslog server. Take a look at "Snare" for Windows hosts.
-
- To send messages from a Unix host, specify the host name prepended with @ instead of a file for logging in /etc/syslog.conf. For example, change /var/log/xferlog to @loghost.mydomain.biz. You can also copy and edit the line to have it log to both a local file and a remote host.
+
- If you are concerned about the security of your logs, use a dedicated machine and lock it down.
+ - Keep clocks in sync.
+ - You may need to change log rotation schedule in /etc/newsyslog.conf. You can rotate based in size and/or time. This can be as much a policy decision as a hardware decision.
+ - On central log host, change syslogd flags to listen to network. Each BSD does this differently, so check the man pages. Also, check out the -n flag for busy environments.
+ - Make sure host firewall allows syslog traffic through.
+ - Be careful to limit syslog traffic to just the trusted network or hosts. FreeBSD man page refers to syslogd as a "remote disk filling service".
+ - For heavy logging environments, it is important to have a dedicated network. A down syslogd server can create a lot of "ARP who-has" broadcasts.
+ - Most network devices such as printers and commercial firewalls support sending to a central syslog server. Take a look at "Snare" for Windows hosts.
+ - To send messages from a Unix host, specify the host name prepended with @ instead of a file for logging in /etc/syslog.conf. For example, change /var/log/xferlog to @loghost.mydomain.biz. You can also copy and edit the line to have it log to both a local file and a remote host.
]]>
http://bsdtalk.blogspot.com/2008/01/bsdtalk138-central-syslog.html
@@ -646,18 +648,20 @@
-
Why I like the CLI
Why I like the CLI:
+
- - Uses minimal resources. Less space, less memory, fewer dependencies.
-
- Transparency. GUI hides internals, limits options.
-
- Similar between Unix-like systems. GUI tools seem to change every week.
-
- Remote management. SSH rocks.
-
- Everything is text. Configs, devices, output. CLI is natural complement.
-
- Pipes and scripts. One time is hard, a thousand times is easy.
-
- Only need a few tools. Grep, sed, awk, vi, cron.
-
- Text config files. Easy to version, share, and comment.
-
- Requires reading skills instead of clicking skills.
-
- Much faster when you know what you are doing.
+
- Uses minimal resources. Less space, less memory, fewer dependencies.
+ - Transparency. GUI hides internals, limits options.
+ - Similar between Unix-like systems. GUI tools seem to change every week.
+ - Remote management. SSH rocks.
+ - Everything is text. Configs, devices, output. CLI is natural complement.
+ - Pipes and scripts. One time is hard, a thousand times is easy.
+ - Only need a few tools. Grep, sed, awk, vi, cron.
+ - Text config files. Easy to version, share, and comment.
+ - Requires reading skills instead of clicking skills.
+ - Much faster when you know what you are doing.
]]>
http://bsdtalk.blogspot.com/2007/08/bsdtalk127-why-i-like-cli.html
@@ -917,22 +921,22 @@
One Time Passwords
- Important when you don't trust the computer you are using, such as a library computer or internet kiosk.
- Available by default in Free/Net/Open BSD.
- FreeBSD uses OPIE, Net/Open use S/Key.
- One time passwords are based on your pass phrase, a non-repeating sequence number, and a seed.
- Initial setup should be done directly on the server.
- "skeyinit" for Net/Open, "opiepasswd -c" for FreeBSD.
- Enter a pass phrase that is not your regular account password.
- Find your current sequence number and seed with "opieinfo" or "skeyinfo", for example: "497 pc5246".
- Generate a list of the next 10 passwords and write them down, using "opiekey -n 10 497 pc5246" or "skey -n 10 497 pc5246".
- When you log in from a remote machine that might have a keystroke logger, you can now use a one time password instead of your regular password.
- For OpenBSD, log in as account:skey, for example "bob:skey", which will cause the system to present the s/key challenge.
- For NetBSD, the system will always present you with the s/key challenge if it is configured for your account, although you can still use your regular password.
- FreeBSD by default will force you to use a one time password if it is configured for your account.
- If you want both OPIE and password authentication, FreeBSD allows you to list trusted networks or hosts in /etc/opieaccess.
- Instead of carrying a list of passwords around, you can use s/key generators on a portable device that you trust, such as a palm pilot.
- For more info, check the man pages.
+ Important when you don't trust the computer you are using, such as a library computer or internet kiosk.
+ Available by default in Free/Net/Open BSD.
+ FreeBSD uses OPIE, Net/Open use S/Key.
+ One time passwords are based on your pass phrase, a non-repeating sequence number, and a seed.
+ Initial setup should be done directly on the server.
+ "skeyinit" for Net/Open, "opiepasswd -c" for FreeBSD.
+ Enter a pass phrase that is not your regular account password.
+ Find your current sequence number and seed with "opieinfo" or "skeyinfo", for example: "497 pc5246".
+ Generate a list of the next 10 passwords and write them down, using "opiekey -n 10 497 pc5246" or "skey -n 10 497 pc5246".
+ When you log in from a remote machine that might have a keystroke logger, you can now use a one time password instead of your regular password.
+ For OpenBSD, log in as account:skey, for example "bob:skey", which will cause the system to present the s/key challenge.
+ For NetBSD, the system will always present you with the s/key challenge if it is configured for your account, although you can still use your regular password.
+ FreeBSD by default will force you to use a one time password if it is configured for your account.
+ If you want both OPIE and password authentication, FreeBSD allows you to list trusted networks or hosts in /etc/opieaccess.
+ Instead of carrying a list of passwords around, you can use s/key generators on a portable device that you trust, such as a palm pilot.
+ For more info, check the man pages.
]]>
http://bsdtalk.blogspot.com/2007/06/bsdtalk117-one-time-passwords.html
@@ -1279,20 +1283,19 @@
Getting to know X
- Getting to know the X Window System.
+ Getting to know the X Window System.
Make sure you are in a text only mode. You might
need to change how the system boots, or boot into
single user mode.
-
+
- - "startx" to make sure X is working right.
-
- "X" by itself gives the basic grey screen.
-
- "ctrl" and "alt" and "backspace" keys at the same time will zap X.
-
- "X & xterm -display :0"
-
- "xterm -geometry +300+300"
-
- "twm" or "metacity"
+
- "startx" to make sure X is working right.
+ - "X" by itself gives the basic grey screen.
+ - "ctrl" and "alt" and "backspace" keys at the same time will zap X.
+ - "X & xterm -display :0"
+ - "xterm -geometry +300+300"
+ - "twm" or "metacity"
-
]]>
http://bsdtalk.blogspot.com/2007/03/bsdtalk104-getting-to-know-x.html
bsdtalk,X
@@ -3202,7 +3205,7 @@
UKUUG LISA 2006 took place in Durham, UK in March,
2006. On this page, you can find my slides from
this conference.
-
+
OpenBSM is a BSD-licensed implementation of Sun's
Basic Security Module (BSM) API and file format,
and is the foundation of the TrustedBSD audit
@@ -3235,12 +3238,12 @@
spanning the BSD's. On this page, you can find my
slides from the FreeBSD developer summit and full
conference.
-
+
Status report on the TrustedBSD Project: introduction
and status regarding Audit, plus a TODO list;
introduction to the priv(9) work recently merged
to 7.x.
-
+
The FreeBSD Project is one of the oldest and most
successful open source operating system projects,
seeing wide deployment across the IT industry. From
@@ -3332,7 +3335,7 @@
to attend the conference itself, and my talks were
presented in absentia by Poul-Henning Kamp and Ed
Maste, who have my greatest appreciation!
-
+
The FreeBSD SMPng Project has spent the past five
years redesigning and reimplementing SMP support
for the FreeBSD operating system, moving from a
@@ -3364,7 +3367,7 @@
BSDCan 2004 took place at the University of Ottawa
in Ottawa, Canada. On this page, you can find my
slides from the conference.
-
+
Robert Watson will describe a variety of pieces of
work done as part of the TrustedBSD Project, including
the TrustedBSD MAC Framework, Audit facilities for
@@ -3781,7 +3784,7 @@
as an IPv6 router and tunneling system will also
be covered.
- Bio
+ Bio
Gene Cronk, CISSP-ISSAP, NSA-IAM is a freelance
network security consultant, specializing in *NIX
solutions. He has been working with computers for
@@ -3862,19 +3865,19 @@
beat the price.
We plan on covering the following topics:
+
- - what it is
-
- how it works
-
- where to get it
-
- how to install it
-
- how to configure it
-
- how to customize it for your environment
-
- where the data is stored
-
- how to write a basic plug-in
+
- what it is
+ - how it works
+ - where to get it
+ - how to install it
+ - how to configure it
+ - how to customize it for your environment
+ - where the data is stored
+ - how to write a basic plug-in
-
- About the Speaker
+ About the Speaker
Marc Spitzer started as a VAX/VMS operator who
taught himself some basic scripting in DCL to help
me remember how to do procedures that did not come
@@ -3941,7 +3944,7 @@
surprisingly useful (and fun)- for developers,
sysadmins, and anyone working with BSD systems.
- About the speaker
+ About the speaker
Isaac Levy, (ike) is a freelance BSD hadker based
in NYC. He runs Diversaform Inc. as an engine to
make his hacking feed itself, (and ike). Diversaform
@@ -3984,7 +3987,7 @@
of such attacks on servers designed to provide
network intensive services such as HTTP or routing.
- About the speaker
+ About the speaker
Steven Kreuzer is currently employed by Right Media
as a Systems Administrator focusing on building and
managing high transaction infrastructures around
@@ -4102,7 +4105,7 @@
the global policy. Our goal is a coherent,
enterprise-wide response to any network threat.
- Biography
+ Biography
Matthew Burnside is a Ph.D. student in the Computer
Science department at Columbia University, in New
York. He works for Professor Angelos Keromytis in
@@ -4188,9 +4191,9 @@
New York City BSD Con 2006: BSD is Dying - A Cautionary Tale of Sex and Greed
- BSD is Dying
- A Cautionary Tale of Sex and Greed
- Jason Dixon
+ BSD is Dying
+ A Cautionary Tale of Sex and Greed
+ Jason Dixon
October 28, 2006
First and foremost, I would like to thank the unique
@@ -4333,23 +4336,23 @@
understandable by everyone, (even techs without
UNIX knowledge), and the gear is cheap - this saves
time and money.
-
+
In the meantime, the features of your average Linksys
or Netgear router often leave MUCH to be desired,
(https auth management, for one simple example).
-
+
Enter m0n0wall and PFSense, 2 BSD based packaged
router/firewall solutions that are as solid and
full featured as you`d expect from any BSD system-
PLUS THEY HAVE HTML WEB INTERFACES FOR MANAGEMENT!
-
+
m0n0wall and PFSense become an easy sell in any
small professional enviornment, any competent tech
can manage the network within minutes... At home,
in every hackers home network, they free the hacker
to have trusted tools available, but are as time-saving
as using any Linksys router.
-
+
m0n0wall and PFSense are both light and clean,
designed to run on embedded systems- (Soekris,
WRAP), but are monsters when unleashed on even
@@ -4358,7 +4361,7 @@
to manage the router for your DSL when you get home?
But then doesn`t it bug you to use a chincey Linksys
box?
-
+
Ike has been a member of NYC*BUG since we first
launched in January 2004. He is a long-time member
of the Lower East Side Mac Unix User Group. He has
@@ -4384,7 +4387,7 @@
millions of messages to OKCupid`s subscribers.
Topics covered will be system tuning and sendmail
hacks used in house to achieve massive throughput.
-
+
Alfred Perlstein is the CTO of OKcupid.com, the
largest free online dating site. He has been a
FreeBSD hacker for five years, he`s worked on NFS,
@@ -4458,14 +4461,14 @@
Episode 06 of "FreeBSD for all" uploaded
- This week we talk about-
+ This week we talk about
+
- - Macromedia plugin
-
- FreeBSD-Linux differences part 2
-
- John Baldwin Introduction
-
- Podcast anouncement - call for co-hosts!
+
- Macromedia plugin
+ - FreeBSD-Linux differences part 2
+ - John Baldwin Introduction
+ - Podcast anouncement - call for co-hosts!
-
]]>
http://freebsdforall.blogspot.com/2006/06/episode-06.html
freebsd for all,talk,john baldwin,freebsd vs linux
@@ -4497,10 +4500,10 @@
Our Topic:
FreeBSD's ACPI implementation: The details.
-
+
Our Speaker:
Nate Lawson, FreeBSD Committer.
-
+
Our Topic:
FreeBSD's ACPI implementation is based on code for ACPI released
by Intel. Nate and others wrote the glue code to make this code
@@ -4521,12 +4524,12 @@
Our Topic:
Network Protocol Development Tools and Techniques for FreeBSD
-
+
Our Speaker:
George Neville-Neil, co-author of the "Design and
Implementation of the FreeBSD Operating System"
"daemon" book.
-
+
Our Topic:
While computers have gotten faster and more powerful
the tools we use to develop network protocols, such
@@ -4538,10 +4541,10 @@
developing a library for use in protocol testing.
This talk will cover three topics:
- - Developing and testing kernel code with Virtual Machines
-
- Finding good tests for networking code
+
- Developing and testing kernel code with Virtual Machines
+ - Finding good tests for networking code
- Packet Construction Set (PCS) a new library for
- writing protocol tests
+ writing protocol tests
]]>
bafug,presentation,freebsd,packet construction set,george neville-neil
@@ -4960,7 +4963,7 @@
slides
-
+
1:06:07
Google Video
mp4
@@ -5065,13 +5068,13 @@
]]>
google,presentation,freebsd,freebsd project,robert watson
321 Mb
51 minutes
@@ -5728,7 +5731,7 @@
category in the FreeBSD ports tree and has
become the maintainer of over 20 of the hamradio
ports. She also contributed to the FreeBSD
+ href="http://www.hamsexy.com/wiki/index.php?title=FreeBSD&redirect=no">FreeBSD
entry at Hampedia, the Wikipedia for ham
operators.
@@ -6057,7 +6060,7 @@
bsdcan,bsdcan2008,devsummit,devsummit2008,freebsd,embedded,rafal jaworowski
-
+
6 pages
58 Kb
PDF file
@@ -6075,7 +6078,7 @@
bsdcan,bsdcan2008,devsummit,devsummit2008,freebsd,smp,robert watson
-
+
8 pages
70 Kb
PDF file
@@ -6093,7 +6096,7 @@
bsdcan,bsdcan2008,devsummit,devsummit2008,freebsd,portmgr,erwin lansing
-
+
14 pages
146 Kb
PDF file
@@ -6240,20 +6243,22 @@
PBI installer for PC-BSD desktops.
The presentation will be divided into two main sections:
-
+
The Push Button Installer (PBI) Format
+
- - The basics of the PBI format
-
- The PBI format construction
-
- Add & Remove scripting support within PBI
+
- The basics of the PBI format
+ - The PBI format construction
+ - Add & Remove scripting support within PBI
+
Building PBIs from Ports "Auto-magically"
+
- - The PBI build server & standalone software
-
- Module creation & configuration
-
- Converting messy ports into PBIs
+
- The PBI build server & standalone software
+ - Module creation & configuration
+ - Converting messy ports into PBIs
-
]]>
bsdcan,bsdcan2008,slides,pc-bsd,ports,pbi,kris moore
@@ -6478,7 +6483,7 @@
Beer, prizes, secrets, Works In Progress
The traditional closing...
-
+
with some new and interesting twists. Sleep in if
you must, but don't miss this session.
@@ -6637,40 +6642,39 @@
cover the in-kernel debugger DDB and the external
debugger kgdb which is used to perform post-mortem
analysis on kernel crash dumps.
-
+
Introduction to Debugging the FreeBSD Kernel
- Basic crash messages, what a crash looks like
- - typical panic() invocation
-
- page fault example
-
+ - typical panic() invocation
+ - page fault example
+
"live" debugging with DDB
- - stack traces
-
- ps
-
- deadlock examples
-
- show lockchain
-
- show sleepchain
-
- Adding new DDB commands
-
+ stack traces
+ ps
+ deadlock examples
+ show lockchain
+ show sleepchain
+ Adding new DDB commands
+
KGDB
- - inspecting processes and threads
-
- working with kernel modules
-
- using scripts to extend
-
+ inspecting processes and threads
+ working with kernel modules
+ using scripts to extend
+
examining crashdumps using utilities
+ ps, netstat, etc.
+
debugging strategies
- - kernel crashes
-
- system hangs
-
+ kernel crashes
+ system hangs
+
-
]]>
bsdcan,bsdcan2008,slides,paper,debugging,freebsd,john baldwin
@@ -6715,18 +6719,18 @@
This talk discusses the port of the DTrace facility
to FreeBSD and demonstrates examples on a live
FreeBSD system.
+
- - Introduction to the D language - probes, predicates and actions.
-
- dtrace(8) and libdtrace - the userland side of the DTrace story.
-
- The DTrace kernel module, it's ioctl interface to userland and the provider infrastructure in the kernel.
-
- DTrace kernel hooks and the problem of code licensed under Sun's CDDL.
-
- What does a DTrace probe actually do?
-
- DTrace safety and how it is implemented.
-
- Build system changes to add CTF (Compact C Type Format) data to objects, shared libraries and executables.
-
- The DTrace test suite.
-
- A brief list of things to do to port the DTrace facility to other BSD-derived operating systems.
+
- Introduction to the D language - probes, predicates and actions.
+ - dtrace(8) and libdtrace - the userland side of the DTrace story.
+ - The DTrace kernel module, it's ioctl interface to userland and the provider infrastructure in the kernel.
+ - DTrace kernel hooks and the problem of code licensed under Sun's CDDL.
+ - What does a DTrace probe actually do?
+ - DTrace safety and how it is implemented.
+ - Build system changes to add CTF (Compact C Type Format) data to objects, shared libraries and executables.
+ - The DTrace test suite.
+ - A brief list of things to do to port the DTrace facility to other BSD-derived operating systems.
-
]]>
bsdcan,bsdcan2008,slides,dtrace,freebsd,john birrell
@@ -6889,12 +6893,12 @@
to the user. Then we will shift gears and discuss
the extended socket API that is available to SCTP
users and will cover such items as:
+
- - The two socket programming models
-
- Extended system calls that support the SCTP feature set.
-
- What model may fit you best
+
- The two socket programming models
+ - Extended system calls that support the SCTP feature set.
+ - What model may fit you best
-
]]>
bsdcan,bsdcan2008,abstract,freebsd,sctp,randall stewart
@@ -6957,7 +6961,7 @@
Opening session
Welcome to BSDCan 2008
-
+
Traditional greetings
]]>
bsdcan,bsdcan2008,slides,dan langille
@@ -6976,8 +6980,8 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
- Kirk McKusick - Code Reading of Locally-Connected Sockets
+ The 2007 BSDCan conference
+ Kirk McKusick - Code Reading of Locally-Connected Sockets
]]>
bsdcan,bsdcan2007,talks,kirk mckusick
@@ -6995,8 +6999,8 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
- Erwin Lansing - The state of the FreeBSD Ports Tree
+ The 2007 BSDCan conference
+ Erwin Lansing - The state of the FreeBSD Ports Tree
]]>
bsdcan,bsdcan2007,talks,erwin lansing,ports
@@ -7032,8 +7036,8 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
- Kris Kennaway - Scalability Update 2007
+ The 2007 BSDCan conference
+ Kris Kennaway - Scalability Update 2007
Progress on FreeBSD SMP performance and scalablity
since BSDCan Dev Summit 2006
]]>
@@ -7053,7 +7057,7 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
+ The 2007 BSDCan conference
Qing Li - Routing, ARP and ND6
]]>
bsdcan,bsdcan2007,talks,qing li,routing arp and nd6
@@ -7072,7 +7076,7 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
+ The 2007 BSDCan conference
Marko Zec explains the vimage architecture
]]>
bsdcan,bsdcan2007,talks,marko zec,vimage
@@ -7091,7 +7095,7 @@
BSDCan-2007 - Videos
http://people.freebsd.org/~julian/BSDCan-2007/
+ The 2007 BSDCan conference
Max Laier - PFIL, firewalls and locking
]]>
bsdcan,bsdcan2007,talks,max laier,ipf
@@ -7202,7 +7206,7 @@
+ by Colin Percival (cperciva@FreeBSD.org)
(Note: use ^L to get back in non-fullscreen mode)
]]>
bsdcan,bsdcan2007,pdf,portsnap,freebsd,colin percival
Index: multimedia.pl
===================================================================
RCS file: /home/dcvs/www/en/multimedia/multimedia.pl,v
retrieving revision 1.2
diff -u -r1.2 multimedia.pl
--- multimedia.pl 30 May 2008 15:22:01 -0000 1.2
+++ multimedia.pl 10 Jun 2008 13:10:34 -0000
@@ -2,13 +2,14 @@
#
# $Id$
-# $FreeBSD: www/en/multimedia/multimedia.pl,v 1.2 2008/05/30 15:22:01 remko Exp $
+# $FreeBSD$
#
use strict;
use XML::Parser;
use Data::Dumper;
use POSIX;
+use IO::File;
my @months = (
"", "January", "February", "March",
@@ -17,7 +18,9 @@
"November", "December"
);
-my @createdfiles = ();
+my @createdhtml = ();
+my @createdsgml = ();
+my @createdxml = ();
my @tree = ();
my @values = ();
@@ -28,6 +31,7 @@
my %sources;
my $sid = "";
my %tags;
+my $tag = "";
sub addtags {
my $tags = shift;
@@ -78,12 +82,23 @@
&& $treeindex == 5) {
$items[$ci]{fc}++;
}
+
+ if ($treeindex == 3 &&
+ $element eq "tags") {
+ $tag = "";
+ }
}
sub xml_end {
my $expat = shift;
my $element = shift;
+ if ($treeindex == 3 &&
+ $element eq "tags") {
+ @{$items[$ci]{tags}} = split(/,/, $tag);
+ addtags($tag);
+ }
+
$values[$treeindex] = ();
$treeindex--;
}
@@ -122,8 +137,7 @@
return;
}
if ($tree[3] eq "tags") {
- @{$items[$ci]{tags}} = split(/,/, $value);
- addtags($value);
+ $tag .= $value;
return;
}
@@ -240,92 +254,110 @@
# HTML overview output
#
sub print_htmlitem {
+ my $fhandle = shift;
my $item = shift;
my %item = %{$item};
my $source = shift;
my %source = %{$source};
- print FOUT "";
+ print $fhandle "
";
if (defined $item{overview}) {
- print FOUT "$item{title}\n";
+ print $fhandle "$item{title}\n";
} else {
my %media = %{$item{files}{0}};
- print FOUT "$item{title}\n";
+ print $fhandle "$item{title}\n";
if (defined $media{size} || defined $media{length}) {
my $s = "";
- print FOUT "(";
+ print $fhandle "(";
if (defined $media{size}) {
- print FOUT "$media{size}";
+ print $fhandle "$media{size}";
$s = ", ";
}
if (defined $media{length}) {
- print FOUT "$s$media{length}";
+ print $fhandle "$s$media{length}";
$s = ", ";
}
- print FOUT ")";
+ print $fhandle ")";
}
}
- print FOUT "
Source: ",
+ print $fhandle "
Source: ",
$source{name}, "
\n";
- print FOUT "Added: ",
+ print $fhandle "Added: ",
substr($item{added}, 6, 2), " ",
$months[substr($item{added}, 4, 2)], " ",
substr($item{added}, 0, 4), "
\n";
- print FOUT "Tags: ";
+ print $fhandle "Tags: ";
{
my $first = 1;
foreach my $t (@{$item{tags}}) {
- print FOUT ", " if (!$first);
+ print $fhandle ", " if (!$first);
# join(", ", @{$item{$t}}), "
\n";
my $th = $t;
$th =~ s/ /_/g;
- print FOUT "$t";
+ print $fhandle "$t";
$first = 0;
}
}
- print FOUT "
\n";
+ print $fhandle "
\n";
if (defined $item{overview} && defined $item{files}) {
my $c = 0;
foreach my $m (keys(%{$item{files}})) {
my %file = %{$item{files}{$m}};
- print FOUT ", " if ($c++);
+ print $fhandle ", " if ($c++);
if (defined $item{prefix}) {
- print FOUT "$file{desc}";
+ print $fhandle "$file{desc}";
} else {
- print FOUT "$file{desc}";
+ print $fhandle "$file{desc}";
}
if (defined $file{size} || defined $file{length}) {
my $s = "";
- print FOUT " (";
+ print $fhandle " (";
if (defined $file{size}) {
- print FOUT "$file{size}";
+ print $fhandle "$file{size}";
$s = ", ";
}
if (defined $file{length}) {
- print FOUT "$s$file{length}";
+ print $fhandle "$s$file{length}";
$s = ", ";
}
- print FOUT ")";
+ print $fhandle ")";
}
}
- print FOUT "
\n";
+ print $fhandle "
\n";
}
- print FOUT "$item{desc}\n";
+ print $fhandle "
\n";
+ print $fhandle "$item{desc}\n";
+ print $fhandle "\n";
}
{
- $createdfiles[$#createdfiles+1] = "multimedia.html";
- open(FOUT, ">multimedia.html");
+ $createdhtml[$#createdhtml+1] = "multimedia.html";
+ $createdsgml[$#createdsgml+1] = "multimedia.sgml";
+ my $fhtml = new IO::File;
+ my $fsgml = new IO::File;
+
+ open($fhtml, ">multimedia.html");
open(FIN, "multimedia.html.pre");
my @lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
open(FIN, "multimedia.html.intro");
@lines = ;
close(FIN);
- print FOUT @lines;
- print FOUT "Newest resources
\n";
+ print $fhtml @lines;
+ print $fhtml "Newest resources
\n";
+
+ open($fsgml, ">multimedia.sgml");
+ open(FIN, "multimedia.sgml.pre");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ open(FIN, "multimedia.sgml.intro");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ print $fsgml "Newest resources
\n";
my $month = "";
@@ -333,38 +365,64 @@
my %item = %{$items[$order]};
my %source = %{$sources{$item{source}}};
if (substr($item{added}, 0, 6) ne $month) {
- print FOUT "", $months[substr($item{added}, 4, 2)+0], " ", substr($item{added}, 0, 4), "
";
+ if ($month ne "") {
+ print $fhtml "
\n";
+ print $fsgml "\n";
+ }
+ print $fhtml "", $months[substr($item{added}, 4, 2)+0], " ", substr($item{added}, 0, 4), "
";
+ print $fsgml "", $months[substr($item{added}, 4, 2)+0], " ", substr($item{added}, 0, 4), "
";
$month = substr($item{added}, 0, 6);
}
- print_htmlitem(\%item, \%source);
+ print_htmlitem($fhtml, \%item, \%source);
+ print_htmlitem($fsgml, \%item, \%source);
}
- print FOUT "
\n";
-
+ print $fhtml "
\n";
open(FIN, "multimedia.html.post");
@lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
+ close($fhtml);
- close(FOUT);
+ print $fsgml "\n";
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ close($fsgml);
}
#
# HTML cloud output
#
{
- $createdfiles[$#createdfiles+1] = "multimedia-tags.html";
- open(FOUT, ">multimedia-tags.html");
+ $createdhtml[$#createdhtml+1] = "tags.html";
+ $createdsgml[$#createdsgml+1] = "tags.sgml";
+ my $fhtml = new IO::File;
+ my $fsgml = new IO::File;
+ open($fhtml, ">tags.html");
+ open($fsgml, ">tags.sgml");
+
open(FIN, "multimedia.html.pre");
my @lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
open(FIN, "multimedia.html.intro");
@lines = ;
close(FIN);
- print FOUT @lines;
- print FOUT "Tags
\n";
+ print $fhtml @lines;
+ print $fhtml "Tags
\n";
+
+ open(FIN, "multimedia.sgml.pre");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ open(FIN, "multimedia.sgml.intro");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ print $fsgml "Tags
\n";
my $month = "";
@@ -377,16 +435,23 @@
foreach my $tag (sort size(keys(%tags))) {
my $ftag = $tag;
$ftag =~ s/ /_/g;
- print FOUT "$tag\n";
+ print $fhtml "$tag\n";
+ print $fsgml "$tag\n";
$size-- if ($c++%10 == 0 && $size > 2);
}
open(FIN, "multimedia.html.post");
@lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
- close(FOUT);
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+
+ close($fhtml);
+ close($fsgml);
}
#
@@ -394,21 +459,37 @@
#
{
foreach my $tag (keys(%tags)) {
+ my $fhtml = new IO::File;
+ my $fsgml = new IO::File;
+
my $ftag = $tag;
$ftag =~ s/ /_/g;
- $createdfiles[$#createdfiles+1] = "multimedia-tag-$ftag.html";
- open(FOUT, ">multimedia-tag-$ftag.html");
+ $createdhtml[$#createdhtml+1] = "tag-$ftag.html";
+ $createdsgml[$#createdsgml+1] = "tag-$ftag.sgml";
+ open($fhtml, ">tag-$ftag.html");
+ open($fsgml, ">tag-$ftag.sgml");
open(FIN, "multimedia.html.pre");
my @lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
open(FIN, "multimedia.html.intro");
@lines = ;
close(FIN);
- print FOUT @lines;
- print FOUT "Tag: $tag
\n";
- print FOUT "\n";
+ print $fhtml @lines;
+ print $fhtml "Tag: $tag
\n";
+ print $fhtml "\n";
+
+ open(FIN, "multimedia.sgml.pre");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ open(FIN, "multimedia.sgml.intro");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ print $fsgml "Tag: $tag
\n";
+ print $fsgml "\n";
foreach my $item (@items) {
my %item = %{$item};
@@ -435,16 +516,25 @@
}
}
- print_htmlitem(\%item, \%source) if ($found);
+ print_htmlitem($fhtml, \%item, \%source) if ($found);
+ print_htmlitem($fsgml, \%item, \%source) if ($found);
}
- print FOUT "
\n";
+ print $fhtml "
\n";
open(FIN, "multimedia.html.post");
@lines = ;
close(FIN);
- print FOUT @lines;
- close(FOUT);
+ print $fhtml @lines;
+ close($fhtml);
+
+ print $fsgml "
\n";
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ close($fsgml);
+
}
}
@@ -452,18 +542,35 @@
# HTML all-sources output
#
{
- $createdfiles[$#createdfiles+1] = "multimedia-sources.html";
- open(FOUT, ">multimedia-sources.html");
+ my $fhtml = new IO::File;
+ my $fsgml = new IO::File;
+
+ $createdhtml[$#createdhtml+1] = "sources.html";
+ $createdsgml[$#createdsgml+1] = "sources.sgml";
+ open($fhtml, ">sources.html");
+ open($fsgml, ">sources.sgml");
+
open(FIN, "multimedia.html.pre");
my @lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
open(FIN, "multimedia.html.intro");
@lines = ;
close(FIN);
- print FOUT @lines;
- print FOUT "Sources
\n";
- print FOUT "\n";
+ print $fhtml @lines;
+ print $fhtml "Sources
\n";
+ print $fhtml "\n";
+
+ open(FIN, "multimedia.sgml.pre");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ open(FIN, "multimedia.sgml.intro");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ print $fsgml "Sources
\n";
+ print $fsgml "\n";
+ print $fhtml "
\n";
open(FIN, "multimedia.html.post");
@lines = ;
close(FIN);
- print FOUT @lines;
- close(FOUT);
+ print $fhtml @lines;
+ close($fhtml);
+
+ print $fsgml "
\n";
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ close($fsgml);
+
}
#
# HTML per-source output
#
{
+ my $fhtml = new IO::File;
+ my $fsgml = new IO::File;
+
my $lastsource = "";
foreach my $item (@site_order) {
my %item = %{$item};
@@ -493,36 +612,67 @@
if ($lastsource ne $item{source}) {
if ($lastsource) {
- print FOUT "\n";
+ print $fhtml "\n";
+ print $fsgml "\n";
+
open(FIN, "multimedia.html.post");
my @lines = ;
close(FIN);
- print FOUT @lines;
- close(FOUT);
+ print $fhtml @lines;
+ close($fhtml);
+
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ close($fsgml);
+
}
- $createdfiles[$#createdfiles+1] = "multimedia-source-$item{source}.html";
- open(FOUT, ">multimedia-source-$item{source}.html");
+ $createdhtml[$#createdhtml+1] = "source-$item{source}.html";
+ $createdsgml[$#createdsgml+1] = "source-$item{source}.sgml";
+ open($fhtml, ">source-$item{source}.html");
+ open($fsgml, ">source-$item{source}.sgml");
+
open(FIN, "multimedia.html.pre");
my @lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
open(FIN, "multimedia.html.intro");
@lines = ;
close(FIN);
- print FOUT @lines;
+ print $fhtml @lines;
+
+ open(FIN, "multimedia.sgml.pre");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ open(FIN, "multimedia.sgml.intro");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+
$lastsource = $item{source};
- print FOUT "$source{name}
\n";
- print FOUT "\n";
+ print $fhtml "$source{name}
\n\n";
+ print $fsgml "$source{name}
\n\n";
}
- print_htmlitem(\%item, \%source);
+ print_htmlitem($fhtml, \%item, \%source);
+ print_htmlitem($fsgml, \%item, \%source);
}
- print FOUT "
\n";
+ print $fhtml "
\n";
+ print $fsgml "
\n";
+
open(FIN, "multimedia.html.post");
my @lines = ;
close(FIN);
- print FOUT @lines;
- close(FOUT);
+ print $fhtml @lines;
+ close($fhtml);
+
+ open(FIN, "multimedia.sgml.post");
+ @lines = ;
+ close(FIN);
+ print $fsgml @lines;
+ close($fsgml);
}
#
@@ -579,14 +729,14 @@
print FOUT "$date\n";
print FOUT "\n";
print FOUT "";
- print FOUT htmlentities("$item{title}
From: $source{name}
");
- print FOUT htmlentities("Tags: $tags
\n");
+ print FOUT htmlentities("$item{title}
From: $source{name}
");
+ print FOUT htmlentities("Tags: $tags
\n");
print FOUT htmlentities("$item{desc}");
print FOUT "\n";
print FOUT " \n";
}
- $createdfiles[$#createdfiles+1] = "multimedia.xml";
+ $createdxml[$#createdxml+1] = "multimedia.xml";
open(FOUT, ">multimedia.xml");
my @s = stat("multimedia-input.xml");
@@ -624,8 +774,14 @@
# Created files
#
{
- open(FOUT, ">multimedia.created");
- foreach my $f (@createdfiles) {
+ open(FOUT, ">multimedia.html.created");
+ foreach my $f (@createdhtml) {
+ print FOUT "$f\n";
+ }
+ close(FOUT);
+
+ open(FOUT, ">multimedia.sgml.created");
+ foreach my $f (@createdsgml) {
print FOUT "$f\n";
}
close(FOUT);
Index: multimedia.sgml.intro
===================================================================
RCS file: multimedia.sgml.intro
diff -N multimedia.sgml.intro
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ multimedia.sgml.intro 10 Jun 2008 13:10:34 -0000
@@ -0,0 +1,24 @@
+FreeBSD Multimedia Resources List
+
+Links on this page refer to multimedia resources (podcast, vodcast,
+audio recordings, video recordings, photos) related to FreeBSD or
+of interest for FreeBSD users.
+
+
+
+This list is available as chronological
+overview, as a tag cloud and
+via the sources.
+
+
+
+This list is also available as RSS feed
+
+
+
+If you know any resources not listed here, or notice any dead links,
+please send details to
+Edwin Groothuis so that
+it can be included or updated.
+
Index: multimedia.sgml.post
===================================================================
RCS file: multimedia.sgml.post
diff -N multimedia.sgml.post
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ multimedia.sgml.post 10 Jun 2008 13:10:35 -0000
@@ -0,0 +1,4 @@
+ &footer;
+