Re: PPPoA section of FreeBSD Handbook
On Tue, 20 Nov 2012 11:51:51 +1100 andrew clarke wrote: On Tue 2012-11-20 11:49:38 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: In the meantime I've switched to using mpd5 (/usr/ports/net/mpd5) and /sbin/ipnat. So far, so good: # ifconfig ng0 ng0: flags=88d1UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST metric 0 mtu 1492 inet 124.170.51.116 -- 203.215.7.251 netmask 0x Incidentally the PPPoA section of the FreeBSD is very out of date: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pppoa.html The ambiguously named net/pppoa port in section 28.6.1 has been marked as broken since 2009. (Ambiguous since it's only for a particular brand of USB ASDL modem.) In section 28.6.2 the example provided is a config file for mpd 4.x which does not work in mpd 5.x. net/mpd4 was deleted from the ports tree 11 months ago. net/mpd5 doesn't seem to support PPPoA, only PPPoE. I could find no reference to PPPoA in the manual or source code. Not many people really need that these days. PPPoA support is needed for obsolete USB modems which pass-through ATM for the host to terminate. There are also some pci modems supported by Linux, but I don't think they've been well supported on FreeBSD, if at all. These days there are better options that only require standards-based support in the host. Most PPPoA-based ISPs also support PPPoE over ATM - even if they don't advertise it or tell their low-level technical support. Alternatively you can: - use a NAT router that terminate PPPoA - use a router/modem that bridges PPPoA to PPPoE - use a router/modem that terminates PPPoA and passes the public IP address to the host ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PPPoA section of FreeBSD Handbook
On Tue 2012-11-20 11:49:38 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote: In the meantime I've switched to using mpd5 (/usr/ports/net/mpd5) and /sbin/ipnat. So far, so good: # ifconfig ng0 ng0: flags=88d1UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST metric 0 mtu 1492 inet 124.170.51.116 -- 203.215.7.251 netmask 0x Incidentally the PPPoA section of the FreeBSD is very out of date: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pppoa.html The ambiguously named net/pppoa port in section 28.6.1 has been marked as broken since 2009. (Ambiguous since it's only for a particular brand of USB ASDL modem.) In section 28.6.2 the example provided is a config file for mpd 4.x which does not work in mpd 5.x. net/mpd4 was deleted from the ports tree 11 months ago. net/mpd5 doesn't seem to support PPPoA, only PPPoE. I could find no reference to PPPoA in the manual or source code. The net/pptpclient port listed in section 28.6.3 does build but issues errors when run: # pptp 192.168.1.1 iinet /bin/ip: not found /bin/ip: not found Plus it's not clear what advantage it's supposed to have over the regular /usr/sbin/ppp. The pptp source code doesn't mention PPPoA, despite what the FreeBSD handbook suggests. Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD handbook
On 3/15/07, neo neo [EMAIL PROTECTED] wrote: hello ; i am new at FreeBSD . Where can i get FreeBSD commands list? thankz . ZAW HTET AUNG Hello, Welcome to FreeBSD, please check http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/basics.html and http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD handbook.
It's /usr/share/examples/cvsup/doc-supfile so: cvsup /usr/share/examples/cvsup/doc-supfile should work, although you'll need to set a server in the supfile first... The source will be put in /usr/doc/ On Thu, 02 Mar 2006 18:21:27 -, Iantcho Vassilev [EMAIL PROTECTED] wrote: Use one of the supplied cvs-up files(/usr/local/share/example/cvsup - i think) On 3/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, How can I get the sgml #sources# of the FreeBSD handbook? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD handbook.
Hi, How can I get the sgml #sources# of the FreeBSD handbook? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD handbook.
Use one of the supplied cvs-up files(/usr/local/share/example/cvsup - i think) On 3/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, How can I get the sgml #sources# of the FreeBSD handbook? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about FreeBSD Handbook
Arseny Solokha [EMAIL PROTECTED] writes: I'v partially read FreeBSD Handbook. To my mind this documentation had been wrote most about releases 4 and 5 newest than 5.2.1. The intention is to keep everything up to date, while keeping it relevant to any release from (at least) the last two or three years. 5.2.1 was an early adopters release (http://be-well.ilk.org/FreeBSD/releases/5.2.1R/early-adopter.html), so it is intentionally not documented as carefully as releases that were intended for general use. In beginning of the documentation, in chapter 2.3.2 you wrote about Kernel Configuration. How to start Kernel Configuration in release 5.2.1? Should I edit kernel configuration file and rebuild a kernel? By this way, I have troubles while I rebuild a kernel! 'Make' returns errors while kernel linking was started. Go back to the GENERIC kernel and make a few changes at a time, so that you will be easily able to figure out which change was the problem. Or just stay with the GENERIC kernel, if it works fine for you. I should attach my kernel configuration file but BSD works on virtual machine and I need to copy this file on a USB flash but I don't know how to connect it to BSD. There is a FAQ entry on that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Question about FreeBSD Handbook
Hello! I'v partially read FreeBSD Handbook. To my mind this documentation had been wrote most about releases 4 and 5 newest than 5.2.1. In beginning of the documentation, in chapter 2.3.2 you wrote about Kernel Configuration. How to start Kernel Configuration in release 5.2.1? Should I edit kernel configuration file and rebuild a kernel? By this way, I have troubles while I rebuild a kernel! 'Make' returns errors while kernel linking was started. I should attach my kernel configuration file but BSD works on virtual machine and I need to copy this file on a USB flash but I don't know how to connect it to BSD. ? ?? ?? ?? ?? mailto:[EMAIL PROTECTED] ? ?, ??? ?? 05.11.2005 21:16 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD handbook, 16.3.2.2
Quoting the FreeBSD Handbook: 16.3.2.2 Dedicated If you will not be sharing the new drive with another operating system, you may use the dedicated mode. Remember this mode can confuse Microsoft operating systems; however, no damage will be done by them. IBM's OS/2(r) however, will appropriate any partition it finds which it does not understand. # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # disklabel -Brw da1 auto # disklabel -e da1 # create the `e' partition # newfs -d0 /dev/da1e # mkdir -p /1 # vi /etc/fstab # add an entry for /dev/da1e # mount /1 # disklabel -Brw da1 auto what did the -r option do, why is it used in this example when bsdlabel doesn't support it. # disklabel -e da1 # create the `e' partition Why do I have to make the 'e' partition, explain why 'e' is used and why can't use other ones like a, c, or d? An explanation of what to do when your editing the partition table would also be nice. # newfs -d0 /dev/da1e This command doesn't even work! and what about -O2 and -U options? if it did work I would have made a UFS1 partition with no soft-updates. # mkdir -p /1 -p? what do I need that for? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD handbook, 16.3.2.2
Nikolas Britton [EMAIL PROTECTED] writes: # disklabel -Brw da1 auto what did the -r option do, why is it used in this example when bsdlabel doesn't support it. It enabled the labeling of an unlabeled disk. It's used because the handbook is still in transition from the old disklabel. My copy has a note there saying to omit the -r on =5.1. # disklabel -e da1 # create the `e' partition Why do I have to make the 'e' partition, explain why 'e' is used and why can't use other ones like a, c, or d? An explanation of what to do when your editing the partition table would also be nice. Yup, but if you're just complaining -- please don't, and if you're trying to get it changed, please learn the proper channels. Problem reports are recommended or at least sending your complaint to the doc@ mailing list, though neither of those methods is very likely to get things changed much faster than it would anyway, unless you can provide some alternative text -- preferably as a diff -u of the SGML source files, but OK as plain text. # newfs -d0 /dev/da1e This command doesn't even work! and what about -O2 and -U options? if it did work I would have made a UFS1 partition with no soft-updates. On 5.x? I think the default is UFS2 and you could turn on the soft updates at a later time. But I get your point. # mkdir -p /1 -p? what do I need that for? Looks useless to me too. Maybe somebody never uses mkdir without it. Some good reading: http://www.freebsd.org/docproj/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating wrote: Either way, I'll be using / populating that thing with as much quality info as I can. Thanks! Are you in charge of this? No, you should talk to the Jimbo guy (Jimbo is a FreeBSD enthusiast / professional / zealot, depending on who you ask, and is the maintainer of this wiki.) For more information about him try your luck with 'whois freebsdwiki.net' -- Regards, Karel Miklav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
This is great! I'd love to contribute my mediawiki template and graphic design knowledge to spice it up a bit if you're interested. Either way, I'll be using / populating that thing with as much quality info as I can. Thanks! Are you in charge of this? - bpk On 5/4/05, Karel Miklav [EMAIL PROTECTED] wrote: Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. -- Regards, Karel Miklav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating ([EMAIL PROTECTED]) [050504 10:00]: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! Seconded. I read it and wish for such a thing (rather than the bug-patch-wait-wait-wait cycle). Wish we'd had MediaWiki on hand for Mozilla 1.0 three years ago. - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Karel Miklav ([EMAIL PROTECTED]) [050504 21:19]: Benjamin Keating wrote: A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. If it fits in enough with what they want to do, it might be just the right place for a wiki-developed version of the Handbook. (The PR-patch-wait-wait-wait cycle really is incredibly painful and a frequently convincing reason to just not bother.) - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On 2005-05-03 17:29, Benjamin Keating [EMAIL PROTECTED] wrote: On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. A wiki would eliminate that bottle neck (PR). A wiki comes with its own set of problems though. It's not easy to mirror, its markup language is arbitrarily defined (as opposed to DocBook/SGML), it still requires constant review by a group of dedicated freebsd-doc people, etc. Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Useful comments can always posted to freebsd-doc for discussion. Helpful comments are not only those that contain patches, but also comments of the form: This section sucks a bit. I can't really understand what the exact steps to rebuild my kernel are. Things like that bring noise to this mailing list. It's ok. This is part of the purpose of having the list :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. -- Regards, Karel Miklav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On May 4, 2005, at 2:30 AM, Giorgos Keramidas wrote: On 2005-05-03 17:29, Benjamin Keating [EMAIL PROTECTED] wrote: Things like that bring noise to this mailing list. It's ok. This is part of the purpose of having the list :) You wouldn't think so from the flak some people have received for not googling for a common problem or searching through the mailing list archives...Or maybe I'm confusing this with another list? *shrug* oh well, it's only Wednesday :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. -- Regards, Karel Miklav I am a long-time FreeBSD user. I rarely consult the handbook because of the problems mentioned in this thread. A Wikipedia approach would be great but it would require constant attention by a dedicated group of people. A compromise approach could be to do what www.php.net does. On this site they have the official manual, which has the same flaws as the FBSD handbook (out of date pages, obtuse descriptions, ...). In addition, postings from users are attached to each page. These postings often contain information more pertinent to a particular query than the manual page itself. With this scheme, it is easy for a manual user to distinguish the official information from the information from general users. So one can apply the appropriate mental filters on the information. I am sure there is some monitoring and selection of posts by some responsible people. But the effort involved should be considerably less than that required for the Wikipedia model. dayton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
I would love to see a wiki for FreeBSD. I think that it would be really beneficial for the project. It would take some work to establish it but if there were enough participants, it could turn into a very robust documentation project. Some hard work would be required to make the wiki healthy and to police it but the spirit of a wiki is many users reviewing each other. Benjamin Keating wrote: A wiki would eliminate that bottle neck (PR). Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Things like that bring noise to this mailing list. Idon't know about you but I'd rather just add my new found info to the site rather find a PR addy, submit it and wait for it to be added. We have software that does this now. Lets use it! :) - bpk On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Ryan Cavicchioni GPG ID: C271BCA8 GPG Public Key: http://confabulator.net/gpg/ryan.asc GPG Fingerprint: 83E4 2495 6194 0F66 ED85 22B4 4CC0 DA01 C271 BCA8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On 5/3/2005 at 5:29 PM Benjamin Keating wrote: |A wiki would eliminate that bottle neck (PR). |Some parts are out of date. Others fail to mention FAQ , etc. that |could really help. For instance, the NAT/DHCP articles could easily |include a 'typical home user' HOWTO rather then tricking the user into |reading that one line where it says you have to recompile your kernel |with IPFIREWALL support. | |Things like that bring noise to this mailing list. Idon't know about |you but I'd rather just add my new found info to the site rather find |a PR addy, submit it and wait for it to be added. We have software |that does this now. Lets use it! :) = When I found a spot in the Handbook that was a bit sparce, I send in an email describing what I was looking for, what I found, and what i expected to find. The Handbook was updated within a few days, and the update was much better than what I could have written. Maybe a wiki would supplement the Handbook, rather than replace it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan J. Cavicchioni wrote: I would love to see a wiki for FreeBSD. I think that it would be really beneficial for the project. It would take some work to establish it but if there were enough participants, it could turn into a very robust documentation project. Some hard work would be required to make the wiki healthy and to police it but the spirit of a wiki is many users reviewing each other. Benjamin Keating wrote: A wiki would eliminate that bottle neck (PR). Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Things like that bring noise to this mailing list. Idon't know about you but I'd rather just add my new found info to the site rather find a PR addy, submit it and wait for it to be added. We have software that does this now. Lets use it! :) - bpk On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Wiki's in general are a great idea, I agree. However, you must still consider that anyone can add to a wiki, and the content within could become very cumbersome to maintain. It would (still) require the FreeBSD development team considerable time to verify what is in it and make sure that it isn't going to throw people off. For official documentation, I would have to say that a wiki is not the best idea (unless it is exclusively maintained by the FreeBSD team). Don't get me wrong, wiki's are really cool, but if you want to get down to the facts in official documentation, you can't allow it to get out of hand. My 2 cents...any thoughts? :-) - -Trevor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCeN/CoGycRpOgdeERAu0yAJ9nPTcBrW5unJyr4ljWd03t/+a2UgCdHnp0 7tT7lRLsLqHJnmMCZBtLOjU= =BdIK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On Wed, May 04, 2005 at 08:54:10AM -0400, [EMAIL PROTECTED] wrote: A compromise approach could be to do what www.php.net does. On this site they have the official manual, which has the same flaws as the FBSD handbook (out of date pages, obtuse descriptions, ...). In addition, postings from users are attached to each page. These postings often contain information more pertinent to a particular query than the manual page itself. With this scheme, it is easy for a manual user to distinguish the official information from the information from general users. So one can apply the appropriate mental filters on the information. FWIW, enabling discussions like these on otherwise more tightly controlled pages is fairly trivial in Plone (http://plone.org/). If someone would like to set up a plone site with the handbook as content, and with enabled discussions, perhaps the official handbook pages could point to the inofficial pages which would also contain the discussions (links like: - user discussions)? Wether linked to or not, the REAL problem here would be that the handbook gets updated now and then, and keeping the plone site (together with its discussions) in sync with the official handbook looks like a major time sink and will soon be abandoned eventually. I am sure there is some monitoring and selection of posts by some responsible people. But the effort involved should be considerably less than that required for the Wikipedia model. dayton Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On Wed, 04 May 2005 09:12:09 -0400 MikeM [EMAIL PROTECTED] wrote: On 5/3/2005 at 5:29 PM Benjamin Keating wrote: |A wiki would eliminate that bottle neck (PR). |Some parts are out of date. Others fail to mention FAQ , etc. that |could really help. For instance, the NAT/DHCP articles could easily |include a 'typical home user' HOWTO rather then tricking the user into |reading that one line where it says you have to recompile your kernel |with IPFIREWALL support. | |Things like that bring noise to this mailing list. Idon't know about |you but I'd rather just add my new found info to the site rather find |a PR addy, submit it and wait for it to be added. We have software |that does this now. Lets use it! :) = When I found a spot in the Handbook that was a bit sparce, I send in an email describing what I was looking for, what I found, and what i expected to find. The Handbook was updated within a few days, and the update was much better than what I could have written. Maybe a wiki would supplement the Handbook, rather than replace it. There's some benefits to the present documentation approach that are being overlooked. It has a revision control system. This enables you to obtain a version of a handbook for any given date thru CVS. This magic is also what allows you to update your local documentation and use a minimum of bandwidth. It can produce output in a number of formats (HTML, PDF, PS, etc) from a single set of sources. Don't forget that the FreeBSD Handbook is also published occasionally from these same sources. The documentation is available in a variety of languages due to the efforts of the translation teams. They use the revision control system to determine when updated translations are needed. The documentation is available as part of the system and web access isn't required. It can also be freely distributed whereas I'm not sure who owns the content of a wiki. As others have mentioned, peer review is very important especially with documentation. The wording and syntax needs to be very clear since many users do not speak english as a first language. I'm probably overlooking some other aspects of the benefits but the present system does produce documentation that many consider to be the best of any comprable OS's. Granted, the centralized approach to documentation doesn't produce instant gratification that a wiki might but it seems to lend itself well for a variety of uses in a quality manner. In the end, its the content that is important and not the method. It probably doesn't take any more time on the part of a user to fill out a wiki-form than it takes to send-pr. There might be some niche that a wiki might be useful but I'd need to see a rough implementation showing how it addresses something that is lacking in the present method. There's always room for improvement. I just thought I'd throw a few things out for thought before we continue building the Big Bikeshed ;-) Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
MikeM wrote: On 5/3/2005 at 5:29 PM Benjamin Keating wrote: |A wiki would eliminate that bottle neck (PR). |Some parts are out of date. Others fail to mention FAQ , etc. that |could really help. For instance, the NAT/DHCP articles could easily |include a 'typical home user' HOWTO rather then tricking the user into |reading that one line where it says you have to recompile your kernel |with IPFIREWALL support. | |Things like that bring noise to this mailing list. Idon't know about |you but I'd rather just add my new found info to the site rather find |a PR addy, submit it and wait for it to be added. We have software |that does this now. Lets use it! :) = When I found a spot in the Handbook that was a bit sparce, I send in an email describing what I was looking for, what I found, and what i expected to find. The Handbook was updated within a few days, and the update was much better than what I could have written. Maybe a wiki would supplement the Handbook, rather than replace it. Now I think that would be a better idea. It would be cool to have a very active handbook wiki but just like forums, starting and running a successful one is not easy work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Ryan Cavicchioni GPG ID: C271BCA8 GPG Public Key: http://confabulator.net/gpg/ryan.asc GPG Fingerprint: 83E4 2495 6194 0F66 ED85 22B4 4CC0 DA01 C271 BCA8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
Trevor Sullivan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 know it's off-topic, but I thought it might surprise some folks, and it's possible it could prove important to some, I guess. Notice the words above, about him using the sha-1 hash. You realize it's been broken? The crypto world is unambiguous about it, and firmly reocmmening that everyone immediately move over to using the sha256, which is already implemented on FreeBSD. Since it's already here, and hopefully possible (maybe) to modify your amil system to use it, I thought I would toss in the data here. If you would like (as I usually do) to read it from the hourses mouth, Bruce Schneier is the best authority around, and here's his take on it: http://http://www.schneier.com/blog/archives/2005/02/sha1_broken.htmlwww.schneier.com/blog/archives/2005/02/sha1_broken.html BTW, if you haven't bought his Applied Cryptography, shame on you. He wrote this thing, and it alone tosses his name up against lights such as Richard Stevens, because he explains ALL of the horrible math, explains all of the algorithms in detail enouigh to program from, actually manages to make it entertaining, and I hope he lives forever. Ryan J. Cavicchioni wrote: I would love to see a wiki for FreeBSD. I think that it would be really beneficial for the project. It would take some work to establish it but if there were enough participants, it could turn into a very robust documentation project. Some hard work would be required to make the wiki healthy and to police it but the spirit of a wiki is many users reviewing each other. Benjamin Keating wrote: A wiki would eliminate that bottle neck (PR). Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Things like that bring noise to this mailing list. Idon't know about you but I'd rather just add my new found info to the site rather find a PR addy, submit it and wait for it to be added. We have software that does this now. Lets use it! :) - bpk On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Wiki's in general are a great idea, I agree. However, you must still consider that anyone can add to a wiki, and the content within could become very cumbersome to maintain. It would (still) require the FreeBSD development team considerable time to verify what is in it and make sure that it isn't going to throw people off. For official documentation, I would have to say that a wiki is not the best idea (unless it is exclusively maintained by the FreeBSD team). Don't get me wrong, wiki's are really cool, but if you want to get down to the facts in official documentation, you can't allow it to get out of hand. My 2 cents...any thoughts? :-) - -Trevor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCeN/CoGycRpOgdeERAu0yAJ9nPTcBrW5unJyr4ljWd03t/+a2UgCdHnp0 7tT7lRLsLqHJnmMCZBtLOjU= =BdIK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
The FreeBSD Handbook, in Wiki form.
Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. A wiki would be a great way to acheive this. If there isn't a project like it yet, I'd like to propose we set one up. I can contribute quite a bit of time and resources towards this. Save me wiki.freebsd.org and I'll get a move on! - bpk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The FreeBSD Handbook, in Wiki form.
On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris pgpZe0jH1II8e.pgp Description: PGP signature
Re: The FreeBSD Handbook, in Wiki form.
A wiki would eliminate that bottle neck (PR). Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Things like that bring noise to this mailing list. Idon't know about you but I'd rather just add my new found info to the site rather find a PR addy, submit it and wait for it to be added. We have software that does this now. Lets use it! :) - bpk On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The FreeBSD Handbook, in Wiki form.
Sure any public person can post junk to wiki and that is just what is wrong with it for official handbook. There would be no peer review of info for correctness. There is no single person who knows everything about FreeBSD and has time to review all the personal opinions posted to some wiki. And if you search this questions archives you will see that there is all ready an wiki for FreeBSD and it has very little activity. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Benjamin Keating Sent: Tuesday, May 03, 2005 8:29 PM To: Kris Kennaway Cc: freebsd-questions@freebsd.org Subject: Re: The FreeBSD Handbook, in Wiki form. A wiki would eliminate that bottle neck (PR). Some parts are out of date. Others fail to mention FAQ , etc. that could really help. For instance, the NAT/DHCP articles could easily include a 'typical home user' HOWTO rather then tricking the user into reading that one line where it says you have to recompile your kernel with IPFIREWALL support. Things like that bring noise to this mailing list. Idon't know about you but I'd rather just add my new found info to the site rather find a PR addy, submit it and wait for it to be added. We have software that does this now. Lets use it! :) - bpk On 5/3/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating wrote: Is there anything being done to help keep the handbook just a little more updated? It's a great handbook, if it's content wasn't so out of date. What is out of date? Generally, if you want to improve something in the handbook, just submit a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Handbook typo?
First off I have to say this is my first time ever using any kind of mailing list. I'm not even really sure if this is where I should post this. In the FreeBSD Handbook, page 24.5 The IPFILTER (IPF) Firewall, section 24.5.19.1 Assigning Ports to Use, I believe there is a typo. It gives an example map dc0 192.168.1.0/24 - 0.32 and I think it should say map dc0 192.168.1.0/24 - 0/32 notice the 0/32. It is repeated several times. I noticed this when I kept having problems with it. It gave me an error about the netmask. Just thought I'd try and let you all know, hope this helps. Thanks. Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Handbook typo?
On Fri, 04 Feb 2005 20:02:25 + [EMAIL PROTECTED] wrote: In the FreeBSD Handbook, page 24.5 The IPFILTER (IPF) Firewall, section 24.5.19.1 Assigning Ports to Use, I believe there is a typo. It gives an example map dc0 192.168.1.0/24 - 0.32 and I think it should say map dc0 192.168.1.0/24 - 0/32 notice the 0/32. It is repeated several times. I noticed this when I kept having problems with it. It gave me an error about the netmask. Just thought I'd try and let you all know, hope this helps. I don't think this mailinglist is the right place, but you're absolutely right. The example in the handbook is wrong. The rule should be: map dc0 192.168.1.0/24 and the hand book states 192.168.1.0/29 This is absolutely wrong! I corrected your message. You forgor the xx/29 ;-) -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How can I upgrade my FreeBSD Handbook?
Hi, I've already upgraded my freebsd 4.9 to 4.10 using make buildworld and installworld. I also have rebuilded the kernel. I'm totally sure that when I used cvsup to fetch the sources for FreeBSD 4.10, I have included an src-all line in the cvsup file, but when I visited freebsd.org, their handbook says: Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 4.10-RELEASE and FreeBSD 5.2.1-RELEASE. When I look into my handbook inside the /usr/share/doc/handbook.. it still says: Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 4.9-RELEASE and FreeBSD 5.1-RELEASE. Questions: Does the make buildworld process also upgrades my Handbook? 'Coz it wasn't what i saw after doing such. If not, then how will I do that?..I mean, can I fetch its sources and run a make? And that would be all.. thanks! -jay __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How can I upgrade my FreeBSD Handbook?
On Tue, 22 Jun 2004 20:35:31 -0700 (PDT) Mark Jayson Alvarez [EMAIL PROTECTED] wrote: Hi, I've already upgraded my freebsd 4.9 to 4.10 using make buildworld and installworld. I also have rebuilded the kernel. I'm totally sure that when I used cvsup to fetch the sources for FreeBSD 4.10, I have included an src-all line in the cvsup file, but when I visited freebsd.org, their handbook says: Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 4.10-RELEASE and FreeBSD 5.2.1-RELEASE. When I look into my handbook inside the /usr/share/doc/handbook.. it still says: Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 4.9-RELEASE and FreeBSD 5.1-RELEASE. Questions: Does the make buildworld process also upgrades my Handbook? 'Coz it wasn't what i saw after doing such. Hi Jay, The make buildworld process only deals with the system sources. There are three separate trees (src, ports and docs) that most users are concerned with. Each one uses its own toolchains to do the updating. If not, then how will I do that?..I mean, can I fetch its sources and run a make? Its pretty easy actually. The first thing that needs to be done is to install the tools needed to build the documents from the sources. The textproc/docproj port is a meta-port which will install all the necessary tools: # cd /usr/ports/textproc/docproj/ # make JADETEX=yes install clean I show JADETEX=yes since you can only make HTML or ASCII text output if you install the tools using JADETEX=no. JADETEX is a large port so if HTML/ASCII is sufficient for your needs then there's no reasont to build with JADETEX. You can always add it later if you change your mind. Doing the build will take a little while since there are quite a few dependencies, so be patient. After this, the steps involved in keeping your local documents current is simple. You need to cvsup document sources first. Take the example doc-supfile: /usr/share/examples/cvsup/doc-supfile and modify it by changing the line: *default host=CHANGE_THIS.FreeBSD.org to a cvsup server close to you as you did for your source supfile and cvsup the sources. Once you have the new doc sources, then you can build them: # cd /usr/doc/en_US.ISO8859-1 # make install clean This will build all the english Books and Articles and doesn't take all that long. The process is similar for other languages. Building in the directory /usr/doc would build *all* languages if that is what you wanted to do. This would, of course, take a bit longer. That's the basic process involved. If you're interested in more detail of how all this magic works, take a look at: http://www.freebsd.org/docproj/index.html And that would be all.. thanks! -jay You're welcome... enjoy the new toys ;-) Best regards, Randy -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can the FreeBSD handbook be sold?
On Thursday, 26 June 2003 at 12:50:04 +0200, Alex de Kruijff wrote: On Thu, Jun 26, 2003 at 11:53:28AM +0200, Miguel Mendez wrote: Hi, I came across this: http://store.fultus.com/product_info.php?cPath=5_10products_id=1 These guys are selling a pdf version of the handbook for 35 bucks a pop. Is that legal? Because, if it is, I'll wget the online doc, pipe it to a pdf creator and sell it for $25 ;-P I'm just curious about the status of documentation. I beleave the handbook has the same licence as the system, which is BSD. As long as they don't act against this licence then its legal. And there is a lot you are allowed to do. Yes, it's legal. I don't understand why anybody would pay this kind of money, though. As it says at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html, you can download it for free from ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Can the FreeBSD handbook be sold?
Hi, I came across this: http://store.fultus.com/product_info.php?cPath=5_10products_id=1 These guys are selling a pdf version of the handbook for 35 bucks a pop. Is that legal? Because, if it is, I'll wget the online doc, pipe it to a pdf creator and sell it for $25 ;-P I'm just curious about the status of documentation. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com pgp0.pgp Description: PGP signature
Re: Can the FreeBSD handbook be sold?
On Thu, Jun 26, 2003 at 11:53:28AM +0200, Miguel Mendez wrote: Hi, I came across this: http://store.fultus.com/product_info.php?cPath=5_10products_id=1 These guys are selling a pdf version of the handbook for 35 bucks a pop. Is that legal? Because, if it is, I'll wget the online doc, pipe it to a pdf creator and sell it for $25 ;-P I'm just curious about the status of documentation. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com I beleave the handbook has the same licence as the system, which is BSD. As long as they don't act against this licence then its legal. And there is a lot you are allowed to do. Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
errata in FreeBSD handbook
Hello! I find same errata in FreeBSD handbook: cuai0N (must cuaiaN) cual0N (must cualaN) For example, see: 17.2.4 Device Special Files Most devices in the kernel are accessed through ``device special files'', which are located in the /dev directory. The sio devices are accessed through the /dev/ttydN (dial-in) and /dev/cuaaN (call-out) devices. FreeBSD also provides initialization devices (/dev/ttyidN and /dev/cuai0N) and locking devices (/dev/ttyldN and /dev/cual0N) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Handbook NIS/YP Instructions
From: Mike Hogsett [EMAIL PROTECTED] portmap is also required for NIS. True, and it says so in the handbook, which is the point I was trying to make. Speaking for myself, at least, following the handbook to the letter got NIS working just fine. -Bill From: Adam Stroud [EMAIL PROTECTED] Since NIS uses RPC, do I need to configure inetd.conf to allow RPC on the NIS server and clients? The handbook does not make any mention of editing the inetd.conf file. inetd doesn't handle RPC. Use the rc.conf settings suggested in the tutorial and the necessary rpc servers will be started at boot time by /etc/rc Once you've got everything running, you can use ps -ax | grep rpc to see what rpc servers were started. I don't actually remember what's started for NIS, although I believe rpc.statd at least needs to run. -Bill _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
FreeBSD Handbook NIS/YP Instructions
I am tryin to setup a NIS/YP domain. I just get done reading that chapter in the FreeBSD handbook and I just have a quick question. Since NIS uses RPC, do I need to configure inetd.conf to allow RPC on the NIS server and clients? The handbook does not make any mention of editing the inetd.conf file. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: FreeBSD Handbook NIS/YP Instructions
From: Adam Stroud [EMAIL PROTECTED] Since NIS uses RPC, do I need to configure inetd.conf to allow RPC on the NIS server and clients? The handbook does not make any mention of editing the inetd.conf file. inetd doesn't handle RPC. Use the rc.conf settings suggested in the tutorial and the necessary rpc servers will be started at boot time by /etc/rc Once you've got everything running, you can use ps -ax | grep rpc to see what rpc servers were started. I don't actually remember what's started for NIS, although I believe rpc.statd at least needs to run. -Bill _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: FreeBSD Handbook NIS/YP Instructions
portmap is also required for NIS. - Mike From: Adam Stroud [EMAIL PROTECTED] Since NIS uses RPC, do I need to configure inetd.conf to allow RPC on the NIS server and clients? The handbook does not make any mention of editing the inetd.conf file. inetd doesn't handle RPC. Use the rc.conf settings suggested in the tutorial and the necessary rpc servers will be started at boot time by /etc/rc Once you've got everything running, you can use ps -ax | grep rpc to see what rpc servers were started. I don't actually remember what's started for NIS, although I believe rpc.statd at least needs to run. -Bill _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
