From owner-freebsd-doc@FreeBSD.ORG Sat May 31 19:30:17 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 184FD37B401 for ; Sat, 31 May 2003 19:30:17 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2AC943F85 for ; Sat, 31 May 2003 19:30:16 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h512UGUp062108 for ; Sat, 31 May 2003 19:30:16 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h512UGJ3062107; Sat, 31 May 2003 19:30:16 -0700 (PDT) Date: Sat, 31 May 2003 19:30:16 -0700 (PDT) Message-Id: <200306010230.h512UGJ3062107@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Chuck Swiger Subject: Re: docs/52666: "package list creation" document error X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chuck Swiger List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 02:30:17 -0000 The following reply was made to PR docs/52666; it has been noted by GNATS. From: Chuck Swiger To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: docs/52666: "package list creation" document error Date: Sat, 31 May 2003 22:21:53 -0400 Thanks for the comments, and I supposed I've gotten what I deserve for trimming output, but the problem I had with "find -d . -type d" was due to "find" being expanded to "noglob find" via a shell alias. -Chuck From owner-freebsd-doc@FreeBSD.ORG Sat May 31 19:56:52 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C61937B401 for ; Sat, 31 May 2003 19:56:52 -0700 (PDT) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [211.6.83.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id B74DC43F85 for ; Sat, 31 May 2003 19:56:49 -0700 (PDT) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (p59248-adsao12honb4-acca.tokyo.ocn.ne.jp [220.96.141.248]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 4BCB93C40 for ; Sun, 1 Jun 2003 11:56:48 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) h512u6Jp001449 for ; Sun, 1 Jun 2003 11:56:06 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 01 Jun 2003 11:52:10 +0900 (JST) Message-Id: <20030601.115210.97269893.hrs@eos.ocn.ne.jp> To: doc@freebsd.org From: Hiroki Sato In-Reply-To: <200306010140.h511evS9057031@freefall.freebsd.org> References: <200306010140.h511evS9057031@freefall.freebsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 3.2 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: ports/52640: New port: xmlcatmgr and patches to use this instead of mkcatalog for SGML/XML stuff X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 02:56:52 -0000 Foxfair Hu wrote in <200306010140.h511evS9057031@freefall.freebsd.org>: foxfair> Synopsis: New port: xmlcatmgr and patches to use this instead of mkcatalog for SGML/XML stuff Hmmm, could anyone please review this? xmlcatmgr can generate SGML and XML catalog, and this change should not affect the current structure of SGML catalogs. -- | Hiroki SATO / From owner-freebsd-doc@FreeBSD.ORG Sat May 31 23:20:15 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EED8037B401 for ; Sat, 31 May 2003 23:20:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E50D743FAF for ; Sat, 31 May 2003 23:20:13 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h516KDUp083757 for ; Sat, 31 May 2003 23:20:13 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h516KDuw083756; Sat, 31 May 2003 23:20:13 -0700 (PDT) Date: Sat, 31 May 2003 23:20:13 -0700 (PDT) Message-Id: <200306010620.h516KDuw083756@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Hiten Pandya Subject: Re: docs/52514, Bluetooth Handbook Chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hiten Pandya List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 06:20:15 -0000 The following reply was made to PR docs/52514; it has been noted by GNATS. From: Hiten Pandya To: bug-followup@FreeBSD.ORG Cc: pav@oook.cz Subject: Re: docs/52514, Bluetooth Handbook Chapter Date: Sat, 31 May 2003 23:17:41 -0700 Hello Pav. Thanks for this nice documentation what it is needed most. Here are some comments on your Bluetooth documentation: First of all, this chapter should be in the ``Desktop'' section, just as Murray pointed out. --- chapter.sgml.orig Tue May 20 21:11:44 2003 +++ chapter.sgml Tue May 20 23:15:03 2003 @@ -6687,6 +6687,388 @@ + + + + + Pav + Lucistnik + Written by + +
pav@oook.cz
+ + + + + Bluetooth Some would help: Bluetooth, Wi-Fi, Ad-hoc etc. You should provide for the various acronyms and abbreviations used throughout this chapter. It will make it easier to find information in the printed version of the Handbook. + + + Introduction + Bluetooth is a wireless technology for creating personal networks + operating in the 2.4 GHz unlicensed band, with a range of 10 meters. + Networks are usually formed ad-hoc from portable devices like mobile + phones, handhelds and laptops. Unlike the other popular wireless + technology, Wi-Fi, Bluetooth offers higher level service profiles, This could probably be: "Unlike its counterpart, Wi-Fi," ... + The Bluetooth stack in FreeBSD is implemented using Netgraph. + A Broad variety of USB dongles is supported by the &man.ng.ubt.4; driver. The Bluetooth stack in FreeBSD is implemented using the Netgraph facility (see &man.netgraph.4;). A broad variety of USB dongles ... + The 3Com PC Card 3CRWB60-A is supported by the &man.ng.bt3c.4; driver. + Serial and UART based Bluetooth devices are supported via + &man.ng.h4.4; and &man.hcseriald.8;. This chapter describes using + a USB Bluetooth dongle. Bluetooth support is available only on + FreeBSD 5.0 and newer systems. Bluetooth support is available in FreeBSD 5.0 and newer systems ... (Also, you must note somewhere that the core Netgraph module is required if its loaded via a KLD. You should also explan the various Bluetooth kernel configuration options, and how to utilise them) + + HCI and Inquiry + + Now it is time to discover some nearby bluetooth devices. s/bluetooth/Bluetooth/ + Discovering devices and many other interesting tasks is done with "Interesting taks like discovering devices, and such are done with..." + BD_ADDR is the unique address of a bluetooth device, similar to MAC BD_ADDR + If you perform a discovery on a different bluetooth device, it will find s/bluetooth/Bluetooth/, this should be done whereever you have used "bluetooth. + Pairing of Devices + + By default, Bluetooth communication is not authorized and any device Isn't ``authenticatied'' a better word instead of ``authorized''? Because at start of the chapter, you said its unlicensed, and available for personal networks; which makes ``authorized'' sound a little obfuscated, IMHO. + + You can choose any PIN you like. Note that some devices, like + headsets, have a fixed PIN built in. Start hcsecd -d. + The switch forces the daemon to stay in the + terminal and not fork to the background, so we can see what is happening. + Set the remote device to receive pairing and initiate the HCI connection + to the remote device. The remote device should say that pairing was + accepted, and let you enter the PIN. Enter the same PIN as you have in your + hcsecd.conf. Now your PC and remote device are paired. + Alternatively, you can initiate pairing on the remote device. + This will appear in the hcsecd output: Use &man.hcsecd.8; ? + + Service Discovery Protocol (SDP) + If you want to know which services a Bluetooth device offers, and + on which RFCOMM channels, build libbluetooth + and sdp-1.0rc3 from Maksim Evmenkin's Erm, hmm. According to his emails to me. His surname is ``Yevmenkin.'' + + Dial-up Networking (DUN) and Local Area Network (LAN) + + Bluetooth can be used for connecting to the Internet, either over + PPP (mobile phones) or the local network (access points). The Dial-up Networking + profile on FreeBSD is implemented with &man.ppp.8; and Use &os;, instead of FreeBSD. This should be done everywhere. + to something ppp can operate with. Create ppp labels in s/ppp/PPP/, wherever ``ppp'' is used. + url="http://www.geocities.com/m_evmenkin/">Maksim Evmenkin's See my comment above. + + Troubleshooting + + + A remote device cannot connect to us + Some older devices do not support role switching. By default, + when FreeBSD is accepting a connection, it tries to switch roles + to become a master. Devices which do not support this will not + be able to connect. Role switching is performed when a connection + is being established, so we cannot ask the remote device if it does + support role switching. There is a driver option to disable role + switching on our side: + &prompt.root; hccontrol -n ubt0hci write_node_role_switch 0 + + + + Something is going wrong, can I see what exactly is happening? + Yes, you can. Use the hcidump tool &man.hcidump. (I don't recall its section number) + from Maksim Evmenkin's + snapshot, which works much like &man.tcpdump.1;. You can + use it to display the content of Bluetooth packets on the terminal + and to record Bluetooth communication for later analyzation. + Lastly, you should use formal structure instead of ``Question and Answer'' type structure for this (Troubleshooting) section. We are trying to cut down on QA sections in the Handbook, last time I checked. Thanks Pav. Hope my comments help. -- Hiten (hmp@FreeBSD.ORG) From owner-freebsd-doc@FreeBSD.ORG Sun Jun 1 04:50:19 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFFC437B401 for ; Sun, 1 Jun 2003 04:50:19 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC0D44003 for ; Sun, 1 Jun 2003 04:50:18 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h51BoIUp016689 for ; Sun, 1 Jun 2003 04:50:18 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h51BoIJW016686; Sun, 1 Jun 2003 04:50:18 -0700 (PDT) Date: Sun, 1 Jun 2003 04:50:18 -0700 (PDT) Message-Id: <200306011150.h51BoIJW016686@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Pav Lucistnik Subject: Re: docs/52514, Bluetooth Handbook Chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pav Lucistnik List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 11:50:20 -0000 The following reply was made to PR docs/52514; it has been noted by GNATS. From: Pav Lucistnik To: Hiten Pandya Cc: bug-followup@FreeBSD.ORG Subject: Re: docs/52514, Bluetooth Handbook Chapter Date: 01 Jun 2003 13:43:49 +0200 --=-xhrw/zZeuo+fqFQCDfUF Content-Type: text/plain Content-Transfer-Encoding: 7bit V ne, 01. 06. 2003 v 08:17, Hiten Pandya napsal: > Hello Pav. > > Thanks for this nice documentation what it is needed most. Here are > some comments on your Bluetooth documentation: > > First of all, this chapter should be in the ``Desktop'' section, just as > Murray pointed out. I must disagree here. Look at the Desktop chapter, it contains some tips on commonly used applications on FreeBSD. Technical section like Bluetooth does not fit there, it's completely something different. Bluetooth best fits to Advanced Networking chapter IMHO, it belongs where Wi-Fi already is. > Some would help: > > Bluetooth, Wi-Fi, Ad-hoc etc. > > You should provide for the various acronyms and > abbreviations used throughout this chapter. It will make it > easier to find information in the printed version of the > Handbook. Ok, added indexterms for Bluetooth, pairing, HCI, L2CAP, SDP and Obex. Wi-Fi have it's own Handbook section, Ad-hoc is Wi-Fi terminus. > + > + Introduction > + Bluetooth is a wireless technology for creating personal networks > + operating in the 2.4 GHz unlicensed band, with a range of 10 meters. > + Networks are usually formed ad-hoc from portable devices like mobile > + phones, handhelds and laptops. Unlike the other popular wireless > + technology, Wi-Fi, Bluetooth offers higher level service profiles, > > This could probably be: > "Unlike its counterpart, Wi-Fi," ... I don't think that Bluetooth is a counterpart of Wi-Fi. It's companion, or supplement. These two technologies are not competitors. > + The Bluetooth stack in FreeBSD is implemented using Netgraph. > + A Broad variety of USB dongles is supported by the &man.ng.ubt.4; driver. > > The Bluetooth stack in FreeBSD is implemented using the Netgraph > facility (see &man.netgraph.4;). A broad variety of USB dongles ... Ok, used. > + The 3Com PC Card 3CRWB60-A is supported by the &man.ng.bt3c.4; driver. > + Serial and UART based Bluetooth devices are supported via > + &man.ng.h4.4; and &man.hcseriald.8;. This chapter describes using > + a USB Bluetooth dongle. Bluetooth support is available only on > + FreeBSD 5.0 and newer systems. > > Bluetooth support is available in FreeBSD 5.0 and newer > systems ... Ok, used. > (Also, you must note somewhere that the core Netgraph module is > required if its loaded via a KLD. Used will never load modules by hand, with only exception of device driver if user wants the device be recognized during boot. All module loading, bluetooth stack and netgraph, is done with rc.bluetooth script. Users are encouraged to use this script. > You should also explan the > various Bluetooth kernel configuration options, and how to > utilise them) There aren't any. Bluetooth is meant to be build as modules, I'm not sure if compiling it into kernel is supported. It's similar as with soundcard drivers. And you don't need to add anything to your GENERIC to build these modules. > + > + HCI and Inquiry > + > + Now it is time to discover some nearby bluetooth devices. > > s/bluetooth/Bluetooth/ Ok, changed them all. > + Discovering devices and many other interesting tasks is done with > > "Interesting taks like discovering devices, and such are done with..." Ok, that sounds better. I dropped "interesting" as it's not really that interesting, they are low level stuff that user should never have to use directly. > + BD_ADDR is the unique address of a bluetooth device, similar to MAC > > BD_ADDR Ok, changed. > + Pairing of Devices > + > + By default, Bluetooth communication is not authorized and any device > > Isn't ``authenticatied'' a better word instead of ``authorized''? > Because at start of the chapter, you said its unlicensed, and > available for personal networks; which makes ``authorized'' > sound a little obfuscated, IMHO. Yes, when you think about it, you're right. Changed to "authenticated". > + > + You can choose any PIN you like. Note that some devices, like > + headsets, have a fixed PIN built in. Start hcsecd -d. > + The switch forces the daemon to stay in the > + terminal and not fork to the background, so we can see what is happening. > + Set the remote device to receive pairing and initiate the HCI connection > + to the remote device. The remote device should say that pairing was > + accepted, and let you enter the PIN. Enter the same PIN as you have in your > + hcsecd.conf. Now your PC and remote device are paired. > + Alternatively, you can initiate pairing on the remote device. > + This will appear in the hcsecd output: > > Use &man.hcsecd.8; ? I already have this one paragraph before. What's the policy in situations like this, when the name of a command repeats many times in a short section of the text - should we use man entities everywhere, or should we use it only in the first appearance and leave rest alone? > + > + Service Discovery Protocol (SDP) > + If you want to know which services a Bluetooth device offers, and > + on which RFCOMM channels, build libbluetooth > + and sdp-1.0rc3 from + url="http://www.geocities.com/m_evmenkin/">Maksim Evmenkin's > > Erm, hmm. According to his emails to me. His surname is ``Yevmenkin.'' *sigh* I'm sorry. The surprising part is that this text got his approval and he haven't complained/noticed. Also his geocities account is "Evmenkin" ... Changed it all to "Yevmenkin". > + > + Dial-up Networking (DUN) and Local Area Network (LAN) > + > + Bluetooth can be used for connecting to the Internet, either over > + PPP (mobile phones) or the local network (access points). The Dial-up Networking > + profile on FreeBSD is implemented with &man.ppp.8; and > > Use &os;, instead of FreeBSD. This should be done everywhere. I don't see this done in other sections of advanced-networking.sgml, is it new policy? Replaced everywhere in my section. > + to something ppp can operate with. Create ppp labels in > > s/ppp/PPP/, wherever ``ppp'' is used. Changed. > + > + Something is going wrong, can I see what exactly is happening? > + Yes, you can. Use the hcidump tool > &man.hcidump. (I don't recall its section number) hcidump(1) but I can't use this entity, because hcidump is not part of FreeBSD, it's third party application, and thus the man page reference will leads to nowhere. > + from Maksim Evmenkin's > + snapshot, which works much like &man.tcpdump.1;. You can > + use it to display the content of Bluetooth packets on the terminal > + and to record Bluetooth communication for later analyzation. > + > > Lastly, you should use formal structure instead of ``Question and > Answer'' type structure for this (Troubleshooting) section. We > are trying to cut down on QA sections in the Handbook, last time > I checked. How should it look like? I have no idea. Can you point me to some example elsewhere in the Handbook? Thanks. Updated patch is attached. -- Pav Lucistnik Buh je realny, pokud nebyl deklarovan jako integer. --=-xhrw/zZeuo+fqFQCDfUF Content-Disposition: attachment; filename=patch Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; name=patch; charset=ISO-8859-2 --- original.sgml Sun May 25 12:34:18 2003 +++ chapter.sgml Sun Jun 1 13:31:56 2003 @@ -6732,6 +6732,395 @@ support AAAA records. + + + + + + Pav + Lucistnik + Written by + +
pav@oook.cz
+ + + + + Bluetooth + =20 + Bluetooth + + Introduction + Bluetooth is a wireless technology for creating personal netwo= rks + operating in the 2.4 GHz unlicensed band, with a range of 10 meter= s. + Networks are usually formed ad-hoc from portable devices like mobi= le + phones, handhelds and laptops. Unlike the other popular wireless + technology, Wi-Fi, Bluetooth offers higher level service profiles, + e.g. FTP-like file servers, file pushing, voice transport, serial + line emulation and more. + =20 + The Bluetooth stack in &os; is implemented using the Netgraph + facility (see &man.netgraph.4;). + A Broad variety of USB dongles is supported by the &man.ng.ubt.4; = driver. + The 3Com PC Card 3CRWB60-A is supported by the &man.ng.bt3c.4; dri= ver. + Serial and UART based Bluetooth devices are supported via + &man.ng.h4.4; and &man.hcseriald.8;. This chapter describes using + a USB Bluetooth dongle. Bluetooth support is available + in &os; 5.0 and newer systems. + + =20 + + Plugging in the Device + Device drivers are by default available as kernel modules. + Before attaching a device, you need to load the driver into the + kernel: + =20 + &prompt.root; kldload ng_ubt + =20 + If the Bluetooth device is present in the system during system + startup, load the module from /boot/loader.conf: + =20 + ng_ubt_load=3D"YES" + =20 + Plug in your USB dongle. Similar output will appear on the co= nsole + (or in syslog): + =20 + ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 +ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D= 0x2 +ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3= ; + wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 + =20 + Copy /usr/src/share/examples/netgraph/bluetooth/rc.b= luetooth + to some convenient place, like /etc/rc.bluetooth. + This script is used to start and stop the Bluetooth stack. It is = a good idea + to stop the stack before unplugging the device, but it is not (usu= ally) + fatal. When starting the stack, you will receive output similar t= o this: + =20 + &prompt.root; /etc/rc.bluetooth start ubt0 +BD_ADDR: 00:02:72:00:d4:1a +Features: 0xff 0xff 0xf 00 00 00 00 00=20 +<3-Slot> <5-Slot> <Encryption> <Slot offset> +<Timing accuracy> <Switch> <Hold mode> <Sniff mode>= ; +<Park mode> <RSSI> <Channel quality> <SCO link> +<HV2 packets> <HV3 packets> <u-law log> <A-law log>= ; <CVSD> +<Paging scheme> <Power control> <Transparent SCO data>=20 +Max. ACL packet size: 192 bytes +Number of ACL packets: 8 +Max. SCO packet size: 64 bytes +Number of SCO packets: 8 + =20 + + =20 + HCI + + HCI and Inquiry + + Now it is time to discover some nearby Bluetooth devices. + Tasks like discovering devices, and such are done with + the &man.hccontrol.8; utility. You will receive a list of discove= rable + devices in a few seconds: + + &prompt.user; hccontrol -n ubt0hci inquiry +Inquiry result, num_responses=3D1 +Inquiry result #0 + BD_ADDR: 00:80:37:29:19:a4 + Page Scan Rep. Mode: 0x1 + Page Scan Period Mode: 00 + Page Scan Mode: 00 + Class: 52:02:04 + Clock offset: 0x78ef +Inquiry complete. Status: No error [00] + + BD_ADDR is the unique address of a Bluetoot= h device, similar to MAC + addresses of network cards. This address is needed for further + communication with a device. Let us try to read the device's name= : + + &prompt.user; hccontrol -n ubt0hci remote_name_re= quest 00:80:37:29:19:a4 0 0 0 +BD_ADDR: 00:80:37:29:19:a4 +Name: Pav's T39 + + If you perform a discovery on a different Bluetooth device, it= will find + your computer as your.host.name (ubt0). + + You can list active baseband connections: + + &prompt.user; hccontrol -n ubt0hci read_connectio= n_list +Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State +00:80:37:29:19:a4 41 ACL 0 MAST NONE 0 0 OPEN + + Handle is useful for manually disconnecting a connection: + + &prompt.root; hccontrol -n ubt0hci disconnect 41<= /userinput> +Connection handle: 41 +Reason: Connection terminated by local host [0x16] + + Refer to hccontrol help for a complete list= ing of + available commands. Note that the majority of commands does not r= equire + superuser privileges. + =20 + + =20 + L2CAP + + L2CAP + + L2CAP is a higher level of connection in Bluetooth standards. + A useful command is &man.l2ping.8;, which can be used to ping + other devices. Some devices might not return all of the data + send to them, so 0 bytes as in this example + is a normal state. + + &prompt.root; l2ping -a 00:80:37:29:19:a4 +0 bytes from 0:80:37:29:19:a4 seq_no=3D0 time=3D48.633 ms result=3D0=20 +0 bytes from 0:80:37:29:19:a4 seq_no=3D1 time=3D37.551 ms result=3D0=20 +0 bytes from 0:80:37:29:19:a4 seq_no=3D2 time=3D28.324 ms result=3D0=20 +0 bytes from 0:80:37:29:19:a4 seq_no=3D3 time=3D46.150 ms result=3D0 + + The &man.l2control.8; utility is used to configure L2CAP nodes + and read their state. This example shows file transfer to a Palm + handheld: + + &prompt.user; l2control -a 00:02:72:00:d4:1a read= _channel_list +L2CAP channels: +Remote BD_ADDR SCID/ DCID PSM IMTU/ OMTU State +00:07:e0:00:0b:ca 66/ 64 3 132/ 672 OPEN +&prompt.user; l2control -a 00:02:72:00:d4:1a read_connection_li= st +L2CAP connections: +Remote BD_ADDR Handle Flags Pending State +00:07:e0:00:0b:ca 41 O 0 OPEN + + Another diagnostic tool is &man.btsockstat.1;. It does a simi= lar + job as &man.netstat.1; does, but for Bluetooth sockets, logical + connections on top of baseband connections. The example output sh= ows + the same connection as l2control above: + + &prompt.user; btsockstat +Active L2CAP sockets +PCB Recv-Q Send-Q Local address/PSM Foreign address CID Sta= te +c2afe900 0 0 00:02:72:00:d4:1a/3 00:07:e0:00:0b:ca 66 OPE= N +Active RFCOMM sessions +L2PCB PCB Flag MTU Out-Q DLCs State +c2afe900 c2b53380 1 127 0 Yes OPEN +Active RFCOMM sockets +PCB Recv-Q Send-Q Local address Foreign address Chan DLCI State +c2e8bc80 0 250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3 6 OPEN<= /screen> + + + =20 + pairing + + Pairing of Devices + + By default, Bluetooth communication is not authenticated and a= ny device + can talk to any other device. Some devices, like mobile phones, r= equire + authentication for some functionality, like Internet connections. = This + is done with PIN numbers - you enter the same (up to 16 digits lon= g) + number on both devices. This operation is called pairin= g. + The daemon that answers pairing requests is &man.hcsecd.8;. Copy + /usr/src/usr.sbin/bluetooth/hcsecd/hcsecd.conf + to /usr/local/etc and edit it. The following= is an + example section for a mobile phone, with the PIN arbitrarily set to 1234:= + + device { + bdaddr 00:80:37:29:19:a4; + name "Pav's T39"; + key nokey; + pin "1234"; + } + + You can choose any PIN you like. Note that some devices, like + headsets, have a fixed PIN built in. Start hcsecd -d. + The switch forces the daemon to stay in the + terminal and not fork to the background, so we can see what is hap= pening. + Set the remote device to receive pairing and initiate the HCI conn= ection + to the remote device. The remote device should say that pairing w= as + accepted, and let you enter the PIN. Enter the same PIN as you ha= ve in your + hcsecd.conf. Now your PC and remote device a= re paired. + Alternatively, you can initiate pairing on the remote device. + This will appear in the hcsecd output: + +hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', = remote bdaddr 0:80:37:29:19:a4 +hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name = 'Pav's T39', link key doesn't exist +hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bda= ddr 0:80:37:29:19:a4 +hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:= 80:37:29:19:a4 +hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name = 'Pav's T39', PIN code exists +hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:= 37:29:19:a4 + + + =20 + SDP + + Service Discovery Protocol (SDP) + If you want to know which services a Bluetooth device offers, = and + on which RFCOMM channels, build libbluetooth + and sdp-1.0rc3 from Maksim Yevmenkin's + snapshot. Then, run sdptool an= d + observe (the output is snipped a bit, as this tool is quite talky)= : + + &prompt.root; sdptool browse 00:80:37:29:19:a4 +Browsing 00:80:37:29:19:A4 ... +Service Name: Dial-up Networking +Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 1 + +Service Name: Fax +Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 2 + +Service Name: Voice gateway +Service Class ID List: + "Headset Audio Gateway" (0x1112) + "Generic Audio" (0x1203) +Protocol Descriptor List:=20 + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 3 + + + ... and so on. You will need the channel number later for usi= ng + a given service. Some devices do not support browsing, they retur= n + an empty list, but you can try searching for a specific service. + + &prompt.root; sdptool search --bdaddr 00:07:e0:00= :0b:ca OPUSH + =20 + Offering services on &os; to other devices is done using the + sdpd server. + &prompt.root; sdpd + =20 + Registering a given Bluetooth service to a RFCOMM channel numb= er: + &prompt.root; sdptool add --channel=3D7 LAN + =20 + Checking services offered by our computer: + &prompt.root; sdptool browse ff:ff:ff:00:00:00 + + + + Dial-up Networking (DUN) and Local Area Network (LAN) + + Bluetooth can be used for connecting to the Internet, either o= ver + PPP (mobile phones) or the local network (access points). The Dia= l-up Networking + profile on &os; is implemented with &man.ppp.8; and + &man.rfcomm.pppd.8;, a wrapper that converts RFCOMM Bluetooth conn= ections + to something PPP can operate with. Create PPP labels in + /etc/ppp/ppp.conf, examples from the &man.rfc= omm.pppd.8; + manual page can be used. + =20 + Connecting to the Internet through a mobile phone (DUN profile= ). First, find + out the correct RFCOMM channel on the remote device using + sdptool. Then, use &man.rfcomm.pppd.8;= : + + &prompt.root; rfcomm_pppd -a 00:80:37:29:19:a4 -c= -C 1 -l rfcomm-dialup + =20 + Running a Bluetooth access point on &os;. First, register a + RFCOMM channel for LAN service on the local sdpd. + Then, start the PPP server. Use BD_ADDR of the= local Bluetooth device and + the channel number registered with sdpd= . + =20 + &prompt.root; rfcomm_pppd -a 00:02:72:00:d4:1a -s= -C 7 -l rfcomm-server + =20 + + + OBEX + + OBEX Push (OPUSH) + OBEX is a widely used protocol for simple file transfers betwe= en + mobile devices. It's main use is in infrared communication, where= it is + used for generic file transfers between notebooks or Palm handheld= s, + and for sending business cards or calendar entries between mobile + phones and other devices with PIM applications. + =20 + The OBEX client is implemented in the + obexapp utility from Maksim Yevmenkin's + snapshot. It needs the openobex + library from same package and the + devel/glib12 port. Note tha= t + obexapp does not require root privilege= s + to operate. + =20 + OBEX client. First, find which channel on the remote device i= s IrMC + Synchronization or OBEX Object Push. After that, use + obexapp. Here is an example session wh= ere + we download a file (device info from a mobile phone) and send + a file (business card to the phone's directory): + =20 + &prompt.user; obexapp -a 00:80:37:29:19:a4 -C 10<= /userinput> +obex> get +get: remote file> telecom/devinfo.txt +get: local file> devinfo-t39.txt +Success, response: OK, Success (0x20) +obex> put +put: local file> new.vcf +put: remote file> new.vcf +Success, response: OK, Success (0x20) +obex> di +Success, response: OK, Success (0x20) + + OBEX server. First, register the OPUSH service with the local + sdpd. If OPUSH does not work, + you can try the FTRN service instead. Then, start the OBEX daemon + using the channel number registered with sdpd: + =20 + &prompt.root; obexapp -s -C 10 + =20 + Received files will appear in /var/spool/obex. + This can be overriden with the switch. Make s= ure + the directory exists, obexapp will not + create it. On a typical workstation with a single user it is usef= ul + to set a default owner of received files. See obexapp(1) + for details. + =20 + + + + Serial Port Profile (SP) + Bluetooth can be used to emulate serial port connections. + To connect to a remote device, first locate the RFCOMM channel wit= h the + Serial Port profile. Then, start the Serial Port Profile Daemon + &man.rfcomm.sppd.1; with a free pseudo tty: + + &prompt.root; rfcomm_sppd -a 00:07:E0:00:0B:CA -c= 1 -t /dev/ttyp6 +rfcomm_sppd[94692]: Starting on /dev/ttyp6... + + Now connect this pseudo tty to your actual terminal: + =20 + &prompt.root; cu -l ttyp6 + + + =20 + + Troubleshooting + =20 + + A remote device cannot connect to us + Some older devices do not support role switching. By defaul= t, + when &os; is accepting a connection, it tries to switch roles + to become a master. Devices which do not support this will not + be able to connect. Role switching is performed when a connecti= on + is being established, so we cannot ask the remote device if it d= oes + support role switching. There is a driver option to disable rol= e + switching on our side: + &prompt.root; hccontrol -n ubt0hci write_node_r= ole_switch 0 + + =20 + + Something is going wrong, can I see what exactly is happeni= ng? + Yes, you can. Use the hcidump to= ol + from Maksim Ye= vmenkin's + snapshot, which works much like &man.tcpdump.1;. You can + use it to display the content of Bluetooth packets on the terminal + and to record Bluetooth communication for later analyzation. + + =20 + + + + =20 rpcbind_enable Also, *** On the NFS server: # portmap # nfsd -u -t -n 4 # mountd -r *** portmap --> rpcbind Thanks, -- Adam From owner-freebsd-doc@FreeBSD.ORG Thu Jun 5 19:51:15 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5CAA37B401 for ; Thu, 5 Jun 2003 19:51:15 -0700 (PDT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id C533443F85 for ; Thu, 5 Jun 2003 19:51:14 -0700 (PDT) (envelope-from rmika@worldnet.att.net) Received: from athlon (81.knoxville-15rh15rt-ca.dial-access.att.net[12.93.244.81]) by mtiwmhc12.worldnet.att.net (mtiwmhc12) with SMTP id <2003060602511211200o034me>; Fri, 6 Jun 2003 02:51:12 +0000 Message-ID: <003301c32bd6$79152350$a2f55d0c@athlon> From: "Richard Mika" To: Date: Thu, 5 Jun 2003 21:50:56 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: 56k PCI modem configuration X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 02:51:15 -0000 I installed FreeBSD 4.7 with KDE windows having a problem to configure = internal 56K USR modem recognised by system (sio1 moving to sio4). How should I rebuild the = kernel? Thanks, Richard From owner-freebsd-doc@FreeBSD.ORG Thu Jun 5 20:23:13 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F53E37B401 for ; Thu, 5 Jun 2003 20:23:13 -0700 (PDT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4658F43F3F for ; Thu, 5 Jun 2003 20:23:10 -0700 (PDT) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com ([192.168.0.5]) by pittgoth.com (8.12.9/8.12.9) with SMTP id h563N5HW033115; Thu, 5 Jun 2003 23:23:05 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Thu, 5 Jun 2003 23:03:36 -0400 From: Tom Rhodes To: "Richard Mika" Message-Id: <20030605230336.04cb0cd2.trhodes@FreeBSD.org> In-Reply-To: <003301c32bd6$79152350$a2f55d0c@athlon> References: <003301c32bd6$79152350$a2f55d0c@athlon> X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-doc@FreeBSD.org Subject: Re: 56k PCI modem configuration X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 03:23:13 -0000 On Thu, 5 Jun 2003 21:50:56 -0500 "Richard Mika" wrote: > I installed FreeBSD 4.7 with KDE windows having a problem to configure internal 56K USR modem > recognised by system (sio1 moving to sio4). How should I rebuild the kernel? > Hello Richard, This list is normally used for FreeBSD documentation. But I'll try to give you some hints on where what docs you want to read for this. First off, the handbook has an in depth chapter on working with PPP and modems. You can view this information here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip.html And for configuring your kernel, you can check: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html Hope this helps. If you require more help, please try the FreeBSD-questions mailing list: FreeBSD-questions@FreeBSD.org Take care, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Thu Jun 5 23:37:00 2003 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A361737B401; Thu, 5 Jun 2003 23:37:00 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42CE543FB1; Thu, 5 Jun 2003 23:37:00 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from freefall.freebsd.org (des@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h566b0Up044845; Thu, 5 Jun 2003 23:37:00 -0700 (PDT) (envelope-from des@freefall.freebsd.org) Received: (from des@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h566b0Pu044841; Thu, 5 Jun 2003 23:37:00 -0700 (PDT) Date: Thu, 5 Jun 2003 23:37:00 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200306060637.h566b0Pu044841@freefall.freebsd.org> To: archie@dellroad.org, des@FreeBSD.org, freebsd-doc@FreeBSD.org Subject: Re: docs/43776: /etc/sshd_config settings overridden by PAM but not documented X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 06:37:01 -0000 Synopsis: /etc/sshd_config settings overridden by PAM but not documented State-Changed-From-To: open->closed State-Changed-By: des State-Changed-When: Thu Jun 5 23:36:59 PDT 2003 State-Changed-Why: Fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=43776 From owner-freebsd-doc@FreeBSD.ORG Fri Jun 6 04:29:22 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFC4037B401; Fri, 6 Jun 2003 04:29:22 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6741843F85; Fri, 6 Jun 2003 04:29:21 -0700 (PDT) (envelope-from bzeeb-lists@zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5A8691FFF23; Fri, 6 Jun 2003 13:29:19 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 2B0871FFBD3; Fri, 6 Jun 2003 13:29:18 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 89BC215380; Fri, 6 Jun 2003 11:28:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7ED5715329; Fri, 6 Jun 2003 11:28:52 +0000 (UTC) Date: Fri, 6 Jun 2003 11:28:52 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org, freebsd-security@freebsd.org, freebsd-doc@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 Subject: Request for documenting IPSec, NAT/divert, ipfw, ipfilter ... in kernel flow ? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 11:29:23 -0000 Hi, sorry for cross-mailing. Reply-to: set to freebsd-net. I have seen some discussion on freebsd-security etc. about some parts of the subject. I have seen older messages in archives. Regularly the same questions seem to come up. I have not found an all-including description of the answer to s.th. like: "Can anybody tell me the order packets get processed in kernel related to IPSec, NAT/divert, ipfw, ipfilter, ... for incoming, outgoing, forwarding... ?". What about bpf, ... ? Is there any chance that some of the gurus can draw one or more ascii arts or xfig or whatever images that show the in kernel packet flow/processing ? Perhaps the doc project would also be happy to include it in the handbook or somewhere else. Would make life much more easier for many people. TIA -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-doc@FreeBSD.ORG Fri Jun 6 06:21:32 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED95937B401 for ; Fri, 6 Jun 2003 06:21:32 -0700 (PDT) Received: from web14811.mail.yahoo.com (web14811.mail.yahoo.com [66.163.172.95]) by mx1.FreeBSD.org (Postfix) with SMTP id AF0F043F93 for ; Fri, 6 Jun 2003 06:21:32 -0700 (PDT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20030606132132.22614.qmail@web14811.mail.yahoo.com> Received: from [192.114.47.54] by web14811.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 06:21:32 PDT Date: Fri, 6 Jun 2003 06:21:32 -0700 (PDT) From: Rostislav Krasny To: freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: small typo in release notes X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 13:21:33 -0000 "The DRM_LINUX kernel option hsa been removed" "The DRM_LINUX kernel option has been removed" Do you have some spell checker software? __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From owner-freebsd-doc@FreeBSD.ORG Fri Jun 6 06:39:09 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBF8237B401 for ; Fri, 6 Jun 2003 06:39:09 -0700 (PDT) Received: from web14802.mail.yahoo.com (web14802.mail.yahoo.com [216.136.224.218]) by mx1.FreeBSD.org (Postfix) with SMTP id 6D4D743FBD for ; Fri, 6 Jun 2003 06:39:09 -0700 (PDT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20030606133909.59519.qmail@web14802.mail.yahoo.com> Received: from [192.114.47.54] by web14802.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 06:39:09 PDT Date: Fri, 6 Jun 2003 06:39:09 -0700 (PDT) From: Rostislav Krasny To: freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: small typo in release notes X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 13:39:10 -0000 This is in release notes of FreeBSD 5.1-RC1. I forgot to indicate it, sorry. --- Rostislav Krasny wrote: > "The DRM_LINUX kernel option hsa been removed" > "The DRM_LINUX kernel option has been removed" > > Do you have some spell checker software? __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From owner-freebsd-doc@FreeBSD.ORG Fri Jun 6 06:49:07 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1588237B401 for ; Fri, 6 Jun 2003 06:49:07 -0700 (PDT) Received: from exgw2.lumeta.com (exgw2.lumeta.com [65.198.68.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C542943F3F for ; Fri, 6 Jun 2003 06:49:05 -0700 (PDT) (envelope-from tal@lumeta.com) Received: from lucy.corp.lumeta.com (h65-246-245-10.lumeta.com [65.246.245.10]) by exgw2.lumeta.com (Postfix) with ESMTP id 3D5D037383F; Fri, 6 Jun 2003 09:49:05 -0400 (EDT) Received: from localhost (localhost.corp.lumeta.com [127.0.0.1]) by lucy.corp.lumeta.com (Postfix) with ESMTP id 0A8DDA897A; Fri, 6 Jun 2003 09:49:05 -0400 (EDT) Received: from lucy.corp.lumeta.com ([127.0.0.1]) by localhost (lucy.corp.lumeta.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37154-04; Fri, 6 Jun 2003 09:49:04 -0400 (EDT) Received: from lumeta.com (talmacmm.corp.lumeta.com [65.246.246.66]) by lucy.corp.lumeta.com (Postfix) with ESMTP id 916ABA8974; Fri, 6 Jun 2003 09:49:04 -0400 (EDT) Date: Fri, 6 Jun 2003 09:49:06 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: docs@freebsd.org From: Tom Limoncelli Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) X-Virus-Scanned: by amavisd-new at lumeta.com cc: akruijff@dds.nl Subject: Fwd: Can I synchronise local time with some NTP-server? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 13:49:07 -0000 Alex, I'm glad you liked my article about setting up NTP on FreeBSD systems. As you suggested, I'm sending it to docs@freebsd.org for inclusion. It's now being hosted on the NTP Twiki (my first Twiki experience! oooh aaaaahhh!). http://www.ntp.org/twiki/bin/view/NTP/GettingStarted docs@freebsd.org may want to link to it. It's a shame that the man page can't make reference to it. The man system needs a "insert distribution-specific content here" marker :-) --Tom Begin forwarded message: > From: Alex de Kruijff > Date: Thu Jun 5, 2003 4:32:56 PM US/Eastern > To: Tom Limoncelli > Subject: Re: Can I synchronise local time with some NTP-server? > > On Thu, Jun 05, 2003 at 02:27:13PM -0400, Tom Limoncelli wrote: >> On Thursday, June 5, 2003, at 01:11 PM, Alex de Kruijff wrote: >> >> I agree. It's a shame that the first place that people turn for help >> (the man pages) doesn't refer to it. >> > > O about *your* aricle. If i where you then i would send it to > docs@freebsd.org (or is doc@ ?) It may very well be pointed to. > > Alex From owner-freebsd-doc@FreeBSD.ORG Fri Jun 6 07:16:43 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9B1037B401 for ; Fri, 6 Jun 2003 07:16:43 -0700 (PDT) Received: from rwcrmhc11.attbi.com (rwcrmhc11.attbi.com [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DD8E43F75 for ; Fri, 6 Jun 2003 07:16:43 -0700 (PDT) (envelope-from bmah@employees.org) Received: from bmah.dyndns.org ([12.240.204.110]) by attbi.com (rwcrmhc11) with ESMTP id <2003060614164201300alb39e>; Fri, 6 Jun 2003 14:16:42 +0000 Received: from intruder.bmah.org (localhost [127.0.0.1]) by bmah.dyndns.org (8.12.9/8.12.9) with ESMTP id h56EGf9c039807; Fri, 6 Jun 2003 07:16:41 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.9/8.12.9/Submit) id h56EGff3039806; Fri, 6 Jun 2003 07:16:41 -0700 (PDT) Date: Fri, 6 Jun 2003 07:16:41 -0700 From: "Bruce A. Mah" To: Rostislav Krasny Message-ID: <20030606141641.GA39675@intruder.bmah.org> References: <20030606133909.59519.qmail@web14802.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <20030606133909.59519.qmail@web14802.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-url: http://www.employees.org/~bmah/ cc: freebsd-doc@freebsd.org Subject: Re: small typo in release notes X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 14:16:44 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable If memory serves me right, Rostislav Krasny wrote: > This is in release notes of FreeBSD 5.1-RC1. I forgot to indicate it, > sorry. >=20 > --- Rostislav Krasny wrote: > > "The DRM_LINUX kernel option hsa been removed" > > "The DRM_LINUX kernel option has been removed" > >=20 > > Do you have some spell checker software? I thought I had run this through ispell, but apparently I didn't. Spell-checking technical documents with lots of acronyms, filenames, and variable names is kind of a hit-and-miss activity anyways. The release notes are frozen, so it's too late to fix. I could add an errata entry for this, but I'd rather save the errata for content changes and open issues. Thanks, Bruce. --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+4KJJ2MoxcVugUsMRAqpoAJ9yedtQkgxcTAWBbclNgzt7gegpXgCfVc6a +p5PvI7xObqDXikFdELAgv0= =vstJ -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-doc@FreeBSD.ORG Sat Jun 7 09:27:49 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1674437B401 for ; Sat, 7 Jun 2003 09:27:49 -0700 (PDT) Received: from shrike.submonkey.net (pc1-cdif2-5-cust38.cdif.cable.ntl.com [81.101.150.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45DBC43FCB for ; Sat, 7 Jun 2003 09:27:48 -0700 (PDT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.20) id 19OgXZ-0000dw-8C; Sat, 07 Jun 2003 17:27:37 +0100 Date: Sat, 7 Jun 2003 17:27:37 +0100 From: Ceri Davies To: Tomas Norre Mikkelsen Message-ID: <20030607162737.GA1286@submonkey.net> Mail-Followup-To: Ceri Davies , Tomas Norre Mikkelsen , doc@freebsd.org References: <1054144649.67972.11.camel@bart.milpoer.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <1054144649.67972.11.camel@bart.milpoer.dk> User-Agent: Mutt/1.5.4i Sender: Ceri Davies cc: doc@freebsd.org Subject: Re: Changes at mozilla java part. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 16:27:49 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 28, 2003 at 07:57:30PM +0200, Tomas Norre Mikkelsen wrote: > Hello.. >=20 > I don't know the normal procedure for contacting you, and how often and > when the documentation is updated. I have just installed FreeBSD 5.0 and > mozilla. I want java support, and goes to the documentation at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browser= s.html, but the mozilla part is outdated. The path with downloading the jav= a-files from sun is not correct anymore, according to the portstree.=20 >=20 > "This is due to license restrictions. While we are here, open the ``java > environment'' from > http://java.sun.com/webapps/download/Display?BundleId=3D7163. The filename > is j2sdk-1_3_1_06-linux-i586.bin"=20 >=20 > Should be corrected to. >=20 > "This is due to license restrictions. While we are here, open the "java > environment" from > http://java.sun.com/webapps/donwload/Display?BundleId=3D7905. The filename > is j2sdk-1_3_1_08-linux-u586.bin" >=20 > Probably you are already aware of this. Nope. Committed now, thank you. Ceri --=20 User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+4hJ4ocfcwTS3JF8RAisqAJkBXfjPrBllvoaKTx6UuHig4OE2OACgpnyH Icw1TczA8Q8FqwfB2AypGAM= =y/zN -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-doc@FreeBSD.ORG Sat Jun 7 09:44:00 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1133437B401 for ; Sat, 7 Jun 2003 09:44:00 -0700 (PDT) Received: from shrike.submonkey.net (pc1-cdif2-5-cust38.cdif.cable.ntl.com [81.101.150.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69A4743F93 for ; Sat, 7 Jun 2003 09:43:59 -0700 (PDT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.20) id 19OgnO-0000fv-6Y; Sat, 07 Jun 2003 17:43:58 +0100 Date: Sat, 7 Jun 2003 17:43:58 +0100 From: Ceri Davies To: Christopher Dempsey Message-ID: <20030607164358.GB1286@submonkey.net> Mail-Followup-To: Ceri Davies , Christopher Dempsey , doc@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: Ceri Davies cc: doc@freebsd.org Subject: Re: Grammar error in handbook/acpi-overview.html X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 16:44:00 -0000 --i0/AhcQY5QxfSsSZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 21, 2003 at 01:54:01PM -0700, Christopher Dempsey wrote: > "The hardware was either controlled by some sort of BIOS embedded > interface, i.e.: Plug and Play BIOS (PNPBIOS), Advanced Power Management > (APM) and so on." Thanks Chris; now corrected. Ceri --=20 User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com --i0/AhcQY5QxfSsSZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+4hZNocfcwTS3JF8RAsfKAJ0cixX92JNIufnvq6Rd5xS4WiSdNQCdHSUS fxXuTKfRZGxiI877pjQFBS4= =/j/g -----END PGP SIGNATURE----- --i0/AhcQY5QxfSsSZ-- From owner-freebsd-doc@FreeBSD.ORG Sat Jun 7 09:54:25 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB2DE37B401 for ; Sat, 7 Jun 2003 09:54:25 -0700 (PDT) Received: from n2.grp.scd.yahoo.com (n2.grp.scd.yahoo.com [66.218.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 5058B43F75 for ; Sat, 7 Jun 2003 09:54:25 -0700 (PDT) confirm-return-doc=freebsd.org@returns.groups.yahoo.com) X-eGroups-Return: confirm-return-doc=freebsd.org@returns.groups.yahoo.com Received: from [66.218.67.200] by n2.grp.scd.yahoo.com with NNFMP; 07 Jun 2003 16:54:25 -0000 Received: (qmail 9515 invoked by uid 7800); 7 Jun 2003 16:54:25 -0000 Date: 7 Jun 2003 16:54:25 -0000 Message-ID: <1055004865.93.9508.m8@yahoogroups.com> From: Yahoo!Groups To: doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Subject: Please confirm your request to join ac3filter_news X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: confirm-s2-JoVLseJnGeU6k4SAJtfRVh9tVWY-doc=freebsd.org@yahoogroups.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 16:54:26 -0000 Hello doc@freebsd.org, We have received your request to join the ac3filter_news group hosted by Yahoo! Groups, a free, easy-to-use community service. This request will expire in 21 days. TO BECOME A MEMBER OF THE GROUP: 1) Go to the Yahoo! Groups site by clicking on this link: http://groups.yahoo.com/i?i=JoVLseJnGeU6k4SAJtfRVh9tVWY&e=doc%40freebsd%2Eorg (If clicking doesn't work, "Cut" and "Paste" the line above into your Web browser's address bar.) -OR- 2) REPLY to this email by clicking "Reply" and then "Send" in your email program If you did not request, or do not want, a membership in the ac3filter_news group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ From owner-freebsd-doc@FreeBSD.ORG Sat Jun 7 21:40:28 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 078FD37B401 for ; Sat, 7 Jun 2003 21:40:28 -0700 (PDT) Received: from rslx01.fht-esslingen.de (rslx01.fht-esslingen.de [134.108.32.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id D45D843F3F for ; Sat, 7 Jun 2003 21:40:26 -0700 (PDT) (envelope-from root@rslx01.fht-esslingen.de) Received: (from root@localhost) by rslx01.fht-esslingen.de (8.11.0/8.11.0) id h584eP910986 for doc@FreeBSD.org; Sun, 8 Jun 2003 06:40:25 +0200 Date: Sun, 8 Jun 2003 06:40:25 +0200 From: root Message-Id: <200306080440.h584eP910986@rslx01.fht-esslingen.de> To: doc@FreeBSD.org Subject: VIRUS IN YOUR MAIL TO zimmerma X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2003 04:40:28 -0000 V I R U S A L E R T Our viruschecker found a VIRUS in your email to "zimmerma". We stopped delivery of this email! Now it is on you to check your system for viruses For further information about this viruschecker see: http://aachalon.de/AMaViS/ AMaViS - A Mail Virus Scanner, licenced GPL ######################################################## FHTE eigene Bemerkung: ---------------------- Unser Antivirenprogramm hat in Ihrer Email an "zimmerma" einen Virus festgestellt. Die Auslieferung wurde daraufhin unterbunden. Bitte ueberpruefen Sie Ihren Rechner auf Viren. (Mailversender, Mailempfaenger und Systemadministration wurden benachrichtigt.) Ihr RZ der FHTE Zusatzinfo zum Virus: >>> Virus 'W32/Sobig-C' found in submited.pif