diff options
author | ng0 <ng0@infotropique.org> | 2017-10-27 15:20:35 +0000 |
---|---|---|
committer | ng0 <ng0@infotropique.org> | 2017-10-27 15:20:35 +0000 |
commit | 1291d66e66c751b485d6afacd83d87aa446f3cad (patch) | |
tree | 37f0ab7a453cd90b180880cbba000eb2d19bd341 /doc | |
parent | c0dc50248992fe1eaaafca3aa0dc423287e81a7b (diff) | |
download | gnunet-1291d66e66c751b485d6afacd83d87aa446f3cad.tar.gz gnunet-1291d66e66c751b485d6afacd83d87aa446f3cad.zip |
doc/documentation/chapters/developer.texi: GNU -> GNU/Linux
(in parts where it is technically correct and not just the kernel is referenced).
Diffstat (limited to 'doc')
-rw-r--r-- | doc/documentation/chapters/developer.texi | 52 |
1 files changed, 29 insertions, 23 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi index fa9094268..f3f12405b 100644 --- a/doc/documentation/chapters/developer.texi +++ b/doc/documentation/chapters/developer.texi | |||
@@ -3881,9 +3881,11 @@ ask on the IRC channel. | |||
3881 | @subsection What do I need to use the Bluetooth plugin transport? | 3881 | @subsection What do I need to use the Bluetooth plugin transport? |
3882 | @c %**end of header | 3882 | @c %**end of header |
3883 | 3883 | ||
3884 | If you are a Linux user and you want to use the Bluetooth transport plugin | 3884 | If you are a GNU/Linux user and you want to use the Bluetooth |
3885 | you should install the BlueZ development libraries (if they aren't already | 3885 | transport plugin you should install the |
3886 | installed). For instructions about how to install the libraries you should | 3886 | @command{BlueZ development libraries} (if they aren't already |
3887 | installed). | ||
3888 | For instructions about how to install the libraries you should | ||
3887 | check out the BlueZ site | 3889 | check out the BlueZ site |
3888 | (@uref{http://www.bluez.org/, http://www.bluez.org}). If you don't know if | 3890 | (@uref{http://www.bluez.org/, http://www.bluez.org}). If you don't know if |
3889 | you have the necesarry libraries, don't worry, just run the GNUnet | 3891 | you have the necesarry libraries, don't worry, just run the GNUnet |
@@ -3910,7 +3912,7 @@ The Bluetooth transport plugin uses virtually the same code as the WLAN | |||
3910 | plugin and only the helper binary is different. The helper takes a single | 3912 | plugin and only the helper binary is different. The helper takes a single |
3911 | argument, which represents the interface name and is specified in the | 3913 | argument, which represents the interface name and is specified in the |
3912 | configuration file. Here are the basic steps that are followed by the | 3914 | configuration file. Here are the basic steps that are followed by the |
3913 | helper binary used on Linux: | 3915 | helper binary used on GNU/Linux: |
3914 | 3916 | ||
3915 | @itemize @bullet | 3917 | @itemize @bullet |
3916 | @item it verifies if the name corresponds to a Bluetooth interface name | 3918 | @item it verifies if the name corresponds to a Bluetooth interface name |
@@ -3975,8 +3977,9 @@ the device and to send some particular commands to it. | |||
3975 | @subsection How do I configure my peer2? | 3977 | @subsection How do I configure my peer2? |
3976 | @c %**end of header | 3978 | @c %**end of header |
3977 | 3979 | ||
3978 | On Linux, you just have to be sure that the interface name corresponds to | 3980 | On GNU/Linux, you just have to be sure that the interface name |
3979 | the one that you want to use. Use the @code{hciconfig} tool to check that. | 3981 | corresponds to the one that you want to use. |
3982 | Use the @code{hciconfig} tool to check that. | ||
3980 | By default it is set to hci0 but you can change it. | 3983 | By default it is set to hci0 but you can change it. |
3981 | 3984 | ||
3982 | A basic configuration looks like this: | 3985 | A basic configuration looks like this: |
@@ -4008,8 +4011,8 @@ transport service. | |||
4008 | @subsection How can I test it? | 4011 | @subsection How can I test it? |
4009 | @c %**end of header | 4012 | @c %**end of header |
4010 | 4013 | ||
4011 | If you have two Bluetooth devices on the same machine which use Linux you | 4014 | If you have two Bluetooth devices on the same machine and you are using |
4012 | must: | 4015 | GNU/Linux you must: |
4013 | 4016 | ||
4014 | @itemize @bullet | 4017 | @itemize @bullet |
4015 | 4018 | ||
@@ -4065,7 +4068,7 @@ plugin: it acceses the interface and then it forwards traffic in both | |||
4065 | directions between the Bluetooth interface and stdin/stdout of the | 4068 | directions between the Bluetooth interface and stdin/stdout of the |
4066 | process involved. | 4069 | process involved. |
4067 | 4070 | ||
4068 | The Bluetooth plugin transport could be used both on Linux and Windows | 4071 | The Bluetooth plugin transport could be used both on GNU/Linux and Windows |
4069 | platforms. | 4072 | platforms. |
4070 | 4073 | ||
4071 | @itemize @bullet | 4074 | @itemize @bullet |
@@ -4089,8 +4092,9 @@ platforms. | |||
4089 | @subsubsection Linux functionality | 4092 | @subsubsection Linux functionality |
4090 | @c %**end of header | 4093 | @c %**end of header |
4091 | 4094 | ||
4092 | In order to implement the plugin functionality on Linux I used the BlueZ | 4095 | In order to implement the plugin functionality on GNU/Linux I |
4093 | stack. For the communication with the other devices I used the RFCOMM | 4096 | used the BlueZ stack. |
4097 | For the communication with the other devices I used the RFCOMM | ||
4094 | protocol. Also I used the HCI protocol to gain some control over the | 4098 | protocol. Also I used the HCI protocol to gain some control over the |
4095 | device. The helper binary takes a single argument (the name of the | 4099 | device. The helper binary takes a single argument (the name of the |
4096 | Bluetooth interface) and is separated in two stages: | 4100 | Bluetooth interface) and is separated in two stages: |
@@ -4245,7 +4249,7 @@ but you should keep in mind that you should have the latest updates | |||
4245 | (especially the @emph{ws2bth} header). | 4249 | (especially the @emph{ws2bth} header). |
4246 | 4250 | ||
4247 | Besides the fact that it uses the Windows Sockets, the Windows | 4251 | Besides the fact that it uses the Windows Sockets, the Windows |
4248 | implemenation follows the same principles as the Linux one: | 4252 | implemenation follows the same principles as the GNU/Linux one: |
4249 | 4253 | ||
4250 | @itemize @bullet | 4254 | @itemize @bullet |
4251 | @item It has a initalization part where it initializes the | 4255 | @item It has a initalization part where it initializes the |
@@ -4265,17 +4269,19 @@ In order to register the service I used the @emph{WSASetService} function | |||
4265 | and I generated the @emph{Universally Unique Identifier} with the | 4269 | and I generated the @emph{Universally Unique Identifier} with the |
4266 | @emph{guidgen.exe} Windows's tool. | 4270 | @emph{guidgen.exe} Windows's tool. |
4267 | 4271 | ||
4268 | In the loop section the only difference from the Linux implementation is | 4272 | In the loop section the only difference from the GNU/Linux implementation |
4269 | that I used the GNUNET_NETWORK library for functions like @emph{accept}, | 4273 | is that I used the @code{GNUNET_NETWORK} library for |
4270 | @emph{bind}, @emph{connect} or @emph{select}. I decided to use the | 4274 | functions like @emph{accept}, @emph{bind}, @emph{connect} or |
4271 | GNUNET_NETWORK library because I also needed to interact with the STDIN | 4275 | @emph{select}. I decided to use the |
4272 | and STDOUT handles and on Windows the select function is only defined for | 4276 | @code{GNUNET_NETWORK} library because I also needed to interact |
4273 | sockets, and it will not work for arbitrary file handles. | 4277 | with the STDIN and STDOUT handles and on Windows |
4274 | 4278 | the select function is only defined for sockets, | |
4275 | Another difference between Linux and Windows implementation is that in | 4279 | and it will not work for arbitrary file handles. |
4276 | Linux, the Bluetooth address is represented in 48 bits while in Windows is | 4280 | |
4277 | represented in 64 bits. Therefore I had to do some changes on | 4281 | Another difference between GNU/Linux and Windows implementation is that in |
4278 | @emph{plugin_transport_wlan} header. | 4282 | GNU/Linux, the Bluetooth address is represented in 48 bits |
4283 | while in Windows is represented in 64 bits. | ||
4284 | Therefore I had to do some changes on @emph{plugin_transport_wlan} header. | ||
4279 | 4285 | ||
4280 | Also, currently on Windows the Bluetooth plugin doesn't have support for | 4286 | Also, currently on Windows the Bluetooth plugin doesn't have support for |
4281 | broadcast messages. When it receives a broadcast message it will skip it. | 4287 | broadcast messages. When it receives a broadcast message it will skip it. |