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:
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
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
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
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]
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
-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
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
. 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
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
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
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
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,
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
: 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
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
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
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
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,
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
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
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,
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
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]
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
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
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
41 matches
Mail list logo
