|
<h3>jonen's notes - 2003-02</h3> |
|
1 |
<hr/> |
<hr/> |
2 |
|
|
3 |
- Unix-Systems |
- Unix-Systems |
27 |
where '-g' tells cvsup not to use a GUI, '-L 2' sets default output level to 2 |
where '-g' tells cvsup not to use a GUI, '-L 2' sets default output level to 2 |
28 |
x for available cvs tags, look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html |
x for available cvs tags, look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html |
29 |
o whats about daemon start-stop scripts (like at linux: /etc/init.d/) ? |
o whats about daemon start-stop scripts (like at linux: /etc/init.d/) ? |
30 |
|
x some daemons (only installed ports?) start-stop-scripts are placed at '/usr/local/etc/rc.d/' |
31 |
|
o how at '/etc/rc.conf' toogled start-up scripts can be run manually(e.g. /etc/rc.firewall)? |
32 |
x configure and compile custom kernel: |
x configure and compile custom kernel: |
33 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html |
34 |
x create custom kernel conf-file |
x create custom kernel conf-file |
72 |
x Use firewall_type = "OPEN" for default policy 'OPEN' (allow all) |
x Use firewall_type = "OPEN" for default policy 'OPEN' (allow all) |
73 |
|
|
74 |
|
|
75 |
|
- Linux & Wireless Lan: |
76 |
|
x install modules: |
77 |
|
x prims2 chipset based: |
78 |
|
- if debian kernel-image is used |
79 |
|
:#apt-get install linux-wlan-ng-modules-{your_arch} |
80 |
|
- if not, cd to some temp dir and |
81 |
|
:#apt-get source linux-wlan-ng or wget sources manually if other dist is used |
82 |
|
:#cd linux-wlan-ng-{version} |
83 |
|
:#./Configure |
84 |
|
:#make all install |
85 |
|
x configure at debian: |
86 |
|
x add SSID to dev at /etc/wlan/wlan.conf e.g.: |
87 |
|
SSID_wlan0="WGATEWAY" |
88 |
|
ENABLE_wlan0=y |
89 |
|
x create and edit cutom config related to SSID |
90 |
|
:#cp /etc/wlan/wlancfg-DEFAULT /etc/wlan/wlancfg-WGATEWAY |
91 |
|
:#nano /etc/wlan/wlancfg-WGATEWAY |
92 |
|
x notes!: |
93 |
|
- prism2-based USB devices mostly needs hardware reset to get changes work! |
94 |
|
this is caused of the firmware and could only be solved by a firmware-upgrade |
95 |
|
of the vendor responsible for these devices. |
96 |
|
o get WEP really work at heterogen enviroments(eg. between Win and Linux) |
97 |
|
o WEP is unsecure! (see http://wepcrack.sourceforge.net/) |
98 |
|
o use IPSEC |
99 |
|
o or some other ideas? |
100 |
|
|
101 |
|
- Linux & Bluetooth |
102 |
|
|
103 |
|
With some tweaking bluetooth works as expected. |
104 |
|
You will need the above mentioned patch patch-2.4.20-mh6 to have full functionality with 2.4.20. Then add |
105 |
|
|
106 |
|
deb http://bluez.sourceforge.net/download/debian/woody/ ./ |
107 |
|
deb-src http://bluez.sourceforge.net/download/debian/woody/ ./ |
108 |
|
|
109 |
|
to your /etc/apt/sources.list for woody and install at least the packages "bluez-bluefw" |
110 |
|
for loading the firmware into the usb bluetooth device. You will need "bluez-utils" for hci and rfcomm communications. |
111 |
|
You need to add this line |
112 |
|
|
113 |
|
bluefw 0x0003 0x044e 0x3001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 |
114 |
|
|
115 |
|
to your /etc/hotplug/usb/bluefw.usermap to let the bluefw automatically load the appropriate firmware |
116 |
|
into your dongle once it shows up. |
117 |
|
|
118 |
|
I am using bluetooth with a Siemens S55, but e.g. Nokia 6310i goeas the same way. |
119 |
|
For an initial pairing you will need a pin in /etc/bluetooth/pin which at least needs to have 5 digits which is documented near nowhere. |
120 |
|
Once you do the pairing (Entered pin on the X requester popping up and on the cellphone) you can set your phone to not "Ask on connection". |
121 |
|
Afterwards i put the rfcomm config into the /etc/bluetooth/rfcomm.conf |
122 |
|
|
123 |
|
rfcomm0 { |
124 |
|
device 00:02:EE:B8:50:C5; |
125 |
|
channel 1; |
126 |
|
comment "S55 Dialup connection"; |
127 |
|
} |
128 |
|
|
129 |
|
rfcomm1 { |
130 |
|
device 00:02:EE:B8:50:C5; |
131 |
|
channel 9; |
132 |
|
comment "S55 OBEX"; |
133 |
|
} |
134 |
|
|
135 |
|
For dialing out via ppp you now can use /dev/rfcomm0 which should lead to your phone asking you to accept the connection. |
136 |
|
For debugging you can use these commands: |
137 |
|
|
138 |
|
:~$ sudo hcitool scan |
139 |
|
Scanning ... |
140 |
|
00:02:EE:B8:50:C5 6310i.rfc822 |
141 |
|
:~$ sudo hcitool info 00:02:EE:B8:50:C5 |
142 |
|
Requesting information ... |
143 |
|
BD Address: 00:02:EE:B8:50:C5 |
144 |
|
Device Name: 6310i.rfc822 |
145 |
|
LMP Version: 1.1 (0x1) LMP Subversion: 0x22c |
146 |
|
Manufacturer: Nokia Mobile Phones (1) |
147 |
|
Features: 0xbf 0x28 0x21 0x00 |
148 |
|
<3-slot packets> <5-slot packets> <encryption> <slot offset> |
149 |
|
<timing accuracy> <role switch> <sniff mode> <SCO link> |
150 |
|
<HV3 packets> <CVSD> |
151 |
|
:~$ sudo sdptool browse |
152 |
|
Inquiring ... |
153 |
|
Browsing 00:02:EE:B8:50:C5 ... |
154 |
|
Service Name: Fax |
155 |
|
Service RecHandle: 0x10000 |
156 |
|
Service Class ID List: |
157 |
|
"Fax" (0x1111) |
158 |
|
"Generic Telephony" (0x1204) |
159 |
|
Protocol Descriptor List: |
160 |
|
"L2CAP" (0x0100) |
161 |
|
"RFCOMM" (0x0003) |
162 |
|
Channel: 2 |
163 |
|
Language Base Attr List: |
164 |
|
code_ISO639: 0x656e |
165 |
|
encoding: 0x6a |
166 |
|
base_offset: 0x100 |
167 |
|
Profile Descriptor List: |
168 |
|
"Fax" (0x1111) |
169 |
|
Version: 0x0100 |
170 |
|
|
171 |
|
Service Name: OBEX Object Push |
172 |
|
Service RecHandle: 0x10001 |
173 |
|
Service Class ID List: |
174 |
|
"OBEX Object Push" (0x1105) |
175 |
|
Protocol Descriptor List: |
176 |
|
"L2CAP" (0x0100) |
177 |
|
"RFCOMM" (0x0003) |
178 |
|
Channel: 9 |
179 |
|
"OBEX" (0x0008) |
180 |
|
Language Base Attr List: |
181 |
|
code_ISO639: 0x656e |
182 |
|
encoding: 0x6a |
183 |
|
base_offset: 0x100 |
184 |
|
Profile Descriptor List: |
185 |
|
"OBEX Object Push" (0x1105) |
186 |
|
Version: 0x0100 |
187 |
|
|
188 |
|
Service Name: Audio Gateway |
189 |
|
Service RecHandle: 0x10002 |
190 |
|
Service Class ID List: |
191 |
|
"Headset Audio Gateway" (0x1112) |
192 |
|
"Generic Audio" (0x1203) |
193 |
|
Protocol Descriptor List: |
194 |
|
"L2CAP" (0x0100) |
195 |
|
"RFCOMM" (0x0003) |
196 |
|
Channel: 12 |
197 |
|
Language Base Attr List: |
198 |
|
code_ISO639: 0x656e |
199 |
|
encoding: 0x6a |
200 |
|
base_offset: 0x100 |
201 |
|
Profile Descriptor List: |
202 |
|
"Headset" (0x1108) |
203 |
|
Version: 0x0100 |
204 |
|
|
205 |
|
Service Name: COM 1 |
206 |
|
Service RecHandle: 0x10003 |
207 |
|
Service Class ID List: |
208 |
|
"Serial Port" (0x1101) |
209 |
|
Protocol Descriptor List: |
210 |
|
"L2CAP" (0x0100) |
211 |
|
"RFCOMM" (0x0003) |
212 |
|
Channel: 3 |
213 |
|
Language Base Attr List: |
214 |
|
code_ISO639: 0x656e |
215 |
|
encoding: 0x6a |
216 |
|
base_offset: 0x100 |
217 |
|
|
218 |
|
Service Name: Voice Gateway |
219 |
|
Service RecHandle: 0x10004 |
220 |
|
Service Class ID List: |
221 |
|
"" (0x111f) |
222 |
|
"Generic Audio" (0x1203) |
223 |
|
Protocol Descriptor List: |
224 |
|
"L2CAP" (0x0100) |
225 |
|
"RFCOMM" (0x0003) |
226 |
|
Channel: 13 |
227 |
|
Language Base Attr List: |
228 |
|
code_ISO639: 0x656e |
229 |
|
encoding: 0x6a |
230 |
|
base_offset: 0x100 |
231 |
|
Profile Descriptor List: |
232 |
|
"" (0x111e) |
233 |
|
Version: 0x0100 |
234 |
|
|
235 |
|
Service Name: Dial-up networking |
236 |
|
Service RecHandle: 0x10009 |
237 |
|
Service Class ID List: |
238 |
|
"Dialup Networking" (0x1103) |
239 |
|
"Generic Networking" (0x1201) |
240 |
|
Protocol Descriptor List: |
241 |
|
"L2CAP" (0x0100) |
242 |
|
"RFCOMM" (0x0003) |
243 |
|
Channel: 1 |
244 |
|
Language Base Attr List: |
245 |
|
code_ISO639: 0x656e |
246 |
|
encoding: 0x6a |
247 |
|
base_offset: 0x100 |
248 |
|
Profile Descriptor List: |
249 |
|
"Dialup Networking" (0x1103) |
250 |
|
Version: 0x0100 |
251 |
|
|
252 |
|
- Hardware Notes: |
253 |
|
x Broadcom 2033 chipset (tested with an ALLNET 7031 Class1 USB Adapter) |
254 |
|
- Make sure you have bluefw and hotplug installed, then everything works fine right out of the box. |
255 |
|
x on debian using default or for newer packages above sources: |
256 |
|
:#apt-get install bluez-bluefw |
257 |
|
- DO NOT enable the bluetooth.o module to avoid it being loaded by hotplug!! |
258 |
|
x this can be done by adding 'bluetooth' to '/etc/hotplug/blacklist' |
259 |
|
|
260 |
|
The Bluetooth device in this laptop is a USB Bluetooth device. |
261 |
|
By default, Linux provides two different device drivers for USB Bluetooth devices: bluetooth.o and hci_usb.o. |
262 |
|
The hci_usb.o is the correct driver for this device. Both drivers are loaded when the Bluetooth button is pushed |
263 |
|
but unfortunately bluetooth.o obtains the device first, not allowing hci_usb.o to use the device. |
264 |
|
In order for the Bluetooth device to be function, the bluetooth.o driver must not load. |
265 |
|
One way to stop the bluetooth.o driver from loading is to remove the driver from the system. This is accomplished by doing: |
266 |
|
|
267 |
|
:#rm /lib/modules/2.4.18-14/kernel/drivers/usb/bluetooth.o |
268 |
|
:#depmod -a |
269 |
|
|
270 |
|
Now, if inserting th usb device only the hci_usb.o should be loaded. |
271 |
|
|
272 |
|
- ACPI |
273 |
|
x get suspend work |
274 |
|
- compile kernel with 'Software Suspend Support' |
275 |
|
- some interesting post: |
276 |
|
from http://lists.debian.org/debian-laptop/2002/debian-laptop-200208/msg00349.html |
277 |
|
#------- begin post ----------------------- |
278 |
|
From: "Bem Ajani Jones-Bey" <ajani@OCF.Berkeley.EDU> |
279 |
|
> On Fri, Aug 23, 2002 at 01:14:06PM +0200, Erich Schubert wrote: |
280 |
|
> > Well, S1 is sleep mode, so your BIOS claims to not support sleep mode! |
281 |
|
> > Try getting a bios update, that might help. |
282 |
|
> > S5 is poweroff... S3 or S4 are suspend levels i think... one might be |
283 |
|
> > power-off, maybe that was S3... |
284 |
|
S4 is suspend-to-disk, S3 is suspend-to-RAM. |
285 |
|
> So, last I checked, Linux ACPI didn't support suspend to memory or |
286 |
|
> suspend to disk; the software suspend patch is the only way to get an |
287 |
|
> ACPI laptop to do anything resembling sleeping. I was also under the |
288 |
|
> impression that this wasn't going to work for awhile; at least until |
289 |
|
> 2.6. I admit I haven't looked at ACPI in a couple months, but last time |
290 |
|
> I looked, they were projecting that suspend./sleep wouldn't happen any |
291 |
|
> time soon. |
292 |
|
Last I checked, ACPI does suspend to memory or disk, using swsusp. It's |
293 |
|
even all integrated into the 2.5 kernels (though the CONFIG_SWSUSP option is |
294 |
|
buried in the kernel hacking section rather than ACPI). If you don't want to |
295 |
|
run an experimental kernel, then you can patch 2.4.x from the acpi.sf.net site. |
296 |
|
#-------- end post ------------------------------- |
297 |
|
|
298 |
|
|
299 |
- Backup: |
- Backup: |
300 |
x bacula (http://www.bacula.org) |
x bacula (http://www.bacula.org) |
301 |
Bacula is a set of computer programs that permit you (or the system administrator) to manage backup, |
Bacula is a set of computer programs that permit you (or the system administrator) to manage backup, |
423 |
o convert all howto's to LaTex format ( look at 'nfo/doc/computing/sysadmin/linux/example_latex_howto.lyx' ) |
o convert all howto's to LaTex format ( look at 'nfo/doc/computing/sysadmin/linux/example_latex_howto.lyx' ) |
424 |
|
|
425 |
|
|
426 |
|
- news.netfrag.org: |
427 |
|
o create remote functions to implement e.g.: |
428 |
|
o a mozilla button for creating new newsgroups |
429 |
|
|
430 |
|
|
431 |
future: |
future: |