| 1 |
<hr/> |
| 2 |
|
| 3 |
- FreeBSD(stable): |
| 4 |
o read more about BSD package systems (pkg, cvsup) |
| 5 |
x for simple package installation/de-installation use pkg |
| 6 |
x install downloaded package: |
| 7 |
:# pkg_add {package}-{version}.tgz |
| 8 |
x install package via remote server(only if package is available as *latest*): |
| 9 |
pkg_add -r {package}.tgz |
| 10 |
x using cvsup |
| 11 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html |
| 12 |
x newbies could use cvsupit: |
| 13 |
:# pkg_add -r cvsupit.tgz |
| 14 |
- cvsupit will proberly ask you for the default values it |
| 15 |
place at /etc/cvsupfile, which is used by cvsup |
| 16 |
- after that it will start cvsup to update your system |
| 17 |
x if /etc/cvsupfile already exists and you know what you do, |
| 18 |
this command will update your system (maybe run it via cron...): |
| 19 |
:# /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile |
| 20 |
where '-g' tells cvsup not to use a GUI, '-L 2' sets default output level to 2 |
| 21 |
x for available cvs tags, look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html |
| 22 |
o whats about daemon start-stop scripts (like at linux: /etc/init.d/) ? |
| 23 |
x some daemons (only installed ports?) start-stop-scripts are placed at '/usr/local/etc/rc.d/' |
| 24 |
o how at '/etc/rc.conf' toogled start-up scripts can be run manually(e.g. /etc/rc.firewall)? |
| 25 |
x configure and compile custom kernel: |
| 26 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html |
| 27 |
x create custom kernel conf-file |
| 28 |
- cd usr/src/sys/i386/conf/ |
| 29 |
- copy default kernel GENERIC to eg MYKERNEL |
| 30 |
- edit/modify MYKERNEL |
| 31 |
x configure sources(really?) |
| 32 |
- run /usr/sbin/config MYKERNEL |
| 33 |
x build kernel |
| 34 |
- cd ../../MYKERNEL |
| 35 |
- make depend |
| 36 |
- make |
| 37 |
- make install |
| 38 |
x use packet fiters (firewall): |
| 39 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html |
| 40 |
x some options at the kernel have to be enabled: |
| 41 |
- options IPFIREWALL |
| 42 |
Compiles into the kernel the code for packet filtering. |
| 43 |
- options IPFIREWALL_VERBOSE |
| 44 |
Enables code to allow logging of packets through syslogd. |
| 45 |
Without this option, even if you specify that packets should be logged in the filter rules, |
| 46 |
nothing will happen. |
| 47 |
- options IPFIREWALL_VERBOSE_LIMIT=10 |
| 48 |
Limits the number of packets logged through syslogd on a per entry basis. |
| 49 |
You may wish to use this option in hostile environments in which you want to log firewall activity, |
| 50 |
but do not want to be open to a denial of service attack via syslog flooding. |
| 51 |
When a chain entry reaches the packet limit specified, logging is turned off for that particular entry. |
| 52 |
To resume logging, you will need to reset the associated counter using the ipfw(8) utility: |
| 53 |
:# ipfw zero 4500 |
| 54 |
Where 4500 is the chain entry you wish to continue logging. |
| 55 |
- options IPFIREWALL_DEFAULT_TO_ACCEPT |
| 56 |
This changes the default rule action from ``deny'' to ``allow''. |
| 57 |
This avoids the possibility of locking yourself out if you happen to boot a kernel with IPFIREWALL support but have not configured your firewall yet. |
| 58 |
It is also very useful if you often use ipfw(8) as a filter for specific problems as they arise. |
| 59 |
Use with care though, as this opens up the firewall and changes the way it works. |
| 60 |
x firewall is enabled at /etc/rc.conf (or /etc/rc.conf.local) |
| 61 |
firewall_enabled = "YES" |
| 62 |
firewall_type = "{firewall_type}" |
| 63 |
x where {firewall_type} is either a case at /etc/rc.firewall (/etc/rc.firewall6 for ipv6) |
| 64 |
or some custom file to read rules from. |
| 65 |
x Use firewall_type = "OPEN" for default policy 'OPEN' (allow all) |
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
- Backup: |
| 70 |
x bacula (http://www.bacula.org) |
| 71 |
Bacula is a set of computer programs that permit you (or the system administrator) to manage backup, |
| 72 |
recovery, and verification of computer data across a network of computers of different kinds. |
| 73 |
In technical terms, it is a network client/server based backup program. |
| 74 |
Bacula is relatively easy to use and efficient, while offering many advanced storage management features |
| 75 |
that make it easy to find and recover lost or damaged files. |
| 76 |
Bacula source code has been released under the GPL version 2 license. |
| 77 |
x created debian package, cause we can't found any other |
| 78 |
x wrote some notes about how to build an debian binary package |
| 79 |
http://www.netfrag.org/~jonen/computing/docs/build_bacula_deb.html |
| 80 |
o create 'postinst' and 'prerm' scripts for saving configs on update, etc. |
| 81 |
x tested network backup with Director, Storage Daemon and File Daemon(Client) |
| 82 |
at different hosts, works great! |
| 83 |
x tested backup to FileStorage, instead of using tapes drives |
| 84 |
(if someone would like to sponsor some tape drive, you're more than welcome!) |
| 85 |
notes: |
| 86 |
x remember to use different 'LabelFormat' filename at each pool ! |
| 87 |
x use compression at 'FileSet' definition, where GZIP is equal to GZIP6, means compression-level 6 (1-9) |
| 88 |
example: |
| 89 |
# ====== snip FileSet ============ |
| 90 |
FileSet { |
| 91 |
Name = "Full Set" |
| 92 |
Include = signature=MD5 compression=GZIP { |
| 93 |
/home |
| 94 |
} |
| 95 |
Exclude = { *.o } |
| 96 |
} |
| 97 |
# ====== snip FileSet ============ |
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
- Linux & Wireless Lan: |
| 102 |
x install modules: |
| 103 |
x prims2 chipset based: |
| 104 |
- if debian kernel-image is used |
| 105 |
:#apt-get install linux-wlan-ng-modules-{your_arch} |
| 106 |
- if not, cd to some temp dir and |
| 107 |
:#apt-get source linux-wlan-ng or wget sources manually if other dist is used |
| 108 |
:#cd linux-wlan-ng-{version} |
| 109 |
:#./Configure |
| 110 |
:#make all install |
| 111 |
x configure at debian: |
| 112 |
x add SSID to dev at /etc/wlan/wlan.conf e.g.: |
| 113 |
SSID_wlan0="WGATEWAY" |
| 114 |
ENABLE_wlan0=y |
| 115 |
x create and edit cutom config related to SSID |
| 116 |
:#cp /etc/wlan/wlancfg-DEFAULT /etc/wlan/wlancfg-WGATEWAY |
| 117 |
:#nano /etc/wlan/wlancfg-WGATEWAY |
| 118 |
x notes!: |
| 119 |
- prism2-based USB devices mostly needs hardware reset to get changes work! |
| 120 |
this is caused of the firmware and could only be solved by a firmware-upgrade |
| 121 |
of the vendor responsible for these devices. |
| 122 |
o get WEP really work at heterogen enviroments(eg. between Win and Linux) |
| 123 |
o WEP is unsecure! (see http://wepcrack.sourceforge.net/) |
| 124 |
o use IPSEC |
| 125 |
o or some other ideas? |
| 126 |
|
| 127 |
|
| 128 |
|
| 129 |
- Linux & Bluetooth |
| 130 |
With some tweaking bluetooth works as expected. |
| 131 |
You will need the above mentioned patch patch-2.4.20-mh6 to have full functionality with 2.4.20. Then add |
| 132 |
|
| 133 |
deb http://bluez.sourceforge.net/download/debian/woody/ ./ |
| 134 |
deb-src http://bluez.sourceforge.net/download/debian/woody/ ./ |
| 135 |
|
| 136 |
to your /etc/apt/sources.list for woody and install at least the packages "bluez-bluefw" |
| 137 |
for loading the firmware into the usb bluetooth device. You will need "bluez-utils" for hci and rfcomm communications. |
| 138 |
You need to add this line |
| 139 |
|
| 140 |
bluefw 0x0003 0x044e 0x3001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 |
| 141 |
|
| 142 |
to your /etc/hotplug/usb/bluefw.usermap to let the bluefw automatically load the appropriate firmware |
| 143 |
into your dongle once it shows up. |
| 144 |
|
| 145 |
I am using bluetooth with a Siemens S55, but e.g. Nokia 6310i goeas the same way. |
| 146 |
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. |
| 147 |
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". |
| 148 |
Afterwards i put the rfcomm config into the /etc/bluetooth/rfcomm.conf |
| 149 |
|
| 150 |
rfcomm0 { |
| 151 |
device 00:02:EE:B8:50:C5; |
| 152 |
channel 1; |
| 153 |
comment "S55 Dialup connection"; |
| 154 |
} |
| 155 |
|
| 156 |
rfcomm1 { |
| 157 |
device 00:02:EE:B8:50:C5; |
| 158 |
channel 9; |
| 159 |
comment "S55 OBEX"; |
| 160 |
} |
| 161 |
|
| 162 |
For dialing out via ppp you now can use /dev/rfcomm0 which should lead to your phone asking you to accept the connection. |
| 163 |
For debugging you can use these commands: |
| 164 |
|
| 165 |
:~$ sudo hcitool scan |
| 166 |
Scanning ... |
| 167 |
00:02:EE:B8:50:C5 6310i.rfc822 |
| 168 |
:~$ sudo hcitool info 00:02:EE:B8:50:C5 |
| 169 |
Requesting information ... |
| 170 |
BD Address: 00:02:EE:B8:50:C5 |
| 171 |
Device Name: 6310i.rfc822 |
| 172 |
LMP Version: 1.1 (0x1) LMP Subversion: 0x22c |
| 173 |
Manufacturer: Nokia Mobile Phones (1) |
| 174 |
Features: 0xbf 0x28 0x21 0x00 |
| 175 |
<3-slot packets> <5-slot packets> <encryption> <slot offset> |
| 176 |
<timing accuracy> <role switch> <sniff mode> <SCO link> |
| 177 |
<HV3 packets> <CVSD> |
| 178 |
:~$ sudo sdptool browse |
| 179 |
Inquiring ... |
| 180 |
Browsing 00:02:EE:B8:50:C5 ... |
| 181 |
Service Name: Fax |
| 182 |
Service RecHandle: 0x10000 |
| 183 |
Service Class ID List: |
| 184 |
"Fax" (0x1111) |
| 185 |
"Generic Telephony" (0x1204) |
| 186 |
Protocol Descriptor List: |
| 187 |
"L2CAP" (0x0100) |
| 188 |
"RFCOMM" (0x0003) |
| 189 |
Channel: 2 |
| 190 |
Language Base Attr List: |
| 191 |
code_ISO639: 0x656e |
| 192 |
encoding: 0x6a |
| 193 |
base_offset: 0x100 |
| 194 |
Profile Descriptor List: |
| 195 |
"Fax" (0x1111) |
| 196 |
Version: 0x0100 |
| 197 |
................. |
| 198 |
|
| 199 |
- Hardware Notes: |
| 200 |
x Broadcom 2033 chipset (tested with an ALLNET 7031 Class1 USB Adapter) |
| 201 |
- Make sure you have bluefw and hotplug installed, then everything works fine right out of the box. |
| 202 |
x on debian using default or for newer packages above sources: |
| 203 |
:#apt-get install bluez-bluefw |
| 204 |
- DO NOT enable the bluetooth.o module to avoid it being loaded by hotplug!! |
| 205 |
x this can be done by adding 'bluetooth' to '/etc/hotplug/blacklist' |
| 206 |
|
| 207 |
The Bluetooth device in this laptop is a USB Bluetooth device. |
| 208 |
By default, Linux provides two different device drivers for USB Bluetooth devices: bluetooth.o and hci_usb.o. |
| 209 |
The hci_usb.o is the correct driver for this device. Both drivers are loaded when the Bluetooth button is pushed |
| 210 |
but unfortunately bluetooth.o obtains the device first, not allowing hci_usb.o to use the device. |
| 211 |
In order for the Bluetooth device to be function, the bluetooth.o driver must not load. |
| 212 |
One way to stop the bluetooth.o driver from loading is to remove the driver from the system. This is accomplished by doing: |
| 213 |
|
| 214 |
:#rm /lib/modules/2.4.18-14/kernel/drivers/usb/bluetooth.o |
| 215 |
:#depmod -a |
| 216 |
|
| 217 |
Now, if inserting th usb device only the hci_usb.o should be loaded. |
| 218 |
|
| 219 |
|
| 220 |
- ACPI |
| 221 |
x get suspend work |
| 222 |
- compile kernel with 'Software Suspend Support' |
| 223 |
- some interesting post: |
| 224 |
from http://lists.debian.org/debian-laptop/2002/debian-laptop-200208/msg00349.html |
| 225 |
#------- begin post ----------------------- |
| 226 |
From: "Bem Ajani Jones-Bey" <ajani@OCF.Berkeley.EDU> |
| 227 |
> On Fri, Aug 23, 2002 at 01:14:06PM +0200, Erich Schubert wrote: |
| 228 |
> > Well, S1 is sleep mode, so your BIOS claims to not support sleep mode! |
| 229 |
> > Try getting a bios update, that might help. |
| 230 |
> > S5 is poweroff... S3 or S4 are suspend levels i think... one might be |
| 231 |
> > power-off, maybe that was S3... |
| 232 |
S4 is suspend-to-disk, S3 is suspend-to-RAM. |
| 233 |
> So, last I checked, Linux ACPI didn't support suspend to memory or |
| 234 |
> suspend to disk; the software suspend patch is the only way to get an |
| 235 |
> ACPI laptop to do anything resembling sleeping. I was also under the |
| 236 |
> impression that this wasn't going to work for awhile; at least until |
| 237 |
> 2.6. I admit I haven't looked at ACPI in a couple months, but last time |
| 238 |
> I looked, they were projecting that suspend./sleep wouldn't happen any |
| 239 |
> time soon. |
| 240 |
Last I checked, ACPI does suspend to memory or disk, using swsusp. It's |
| 241 |
even all integrated into the 2.5 kernels (though the CONFIG_SWSUSP option is |
| 242 |
buried in the kernel hacking section rather than ACPI). If you don't want to |
| 243 |
run an experimental kernel, then you can patch 2.4.x from the acpi.sf.net site. |
| 244 |
#-------- end post ------------------------------- |
| 245 |
|
| 246 |
|
| 247 |
- misc: |
| 248 |
x finding processes using special device(module) and kill them(example for alsa modules): |
| 249 |
:# lsof -t /dev/{audio,dsp,midi,mixer,music,sequencer,sndstat} | xargs kill |
| 250 |
|
| 251 |
|
| 252 |
|
| 253 |
<hr/> |
| 254 |
$Id: notes_2003-03.twingle,v 1.1 2003/04/07 01:28:41 jonen Exp $ |
Parent Directory
| 
Revision Log
