/[cvs]/jonen/notes/notes_2003-02.txt
ViewVC logotype

Diff of /jonen/notes/notes_2003-02.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by jonen, Sun Mar 9 15:03:18 2003 UTC revision 1.3 by jonen, Sun Mar 9 16:15:01 2003 UTC
# Line 1  Line 1 
1    
2    - Unix-Systems/Debian:    - Unix-Systems
3      o learn howto move /etc of servers to cvs !!      o learn howto move/maintain /etc of servers at cvs !!
4      x search if new packages available, do 'apt-get --dry-run upgrade'!      Debian:
5       x build small systool script 'apt-get_remote.pl' which do a cronly 'apt-get --dry-run upgrade' and send output via mail        x search if new packages available, do 'apt-get --dry-run upgrade'!
6       o review 'apt-get_remote.pl'         x build small systool script 'apt-get_remote.pl' which do a cronly 'apt-get --dry-run upgrade' and send output via mail
7         o what's about parsing some response for comand like installing some marked packages         o review 'apt-get_remote.pl'
8             o what's about parsing some response for comand like installing some marked packages
9        FreeBSD(stable):
10          o read more about BSD package systems (pkg, cvsup)
11            x for simple package installation/de-installation use pkg
12              x install downloaded package:
13                  :# pkg_add <package>-<version>.tgz
14              x install package via remote server(only if package is available as *latest*):
15                    pkg_add -r <package>.tgz
16            x using cvsup
17              x newbies could use cvsupit (not what it really does..)
18                  :# pkg_add -r cvsupit.tgz
19                - cvsupit will proberly ask you for the default values it
20                  place at /etc/cvsupfile, which is used by cvsup
21                - after that it will start cvsup to update your system
22              x if /etc/cvsupfile already exists and you know what you do,
23                 this command will update your system (maybe run it via cron...):
24                  :# /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile
25          o whats about daemon start-stop scripts (like at linux: /etc/init.d/) ?
26          x configure and compile custom kernel:
27            x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
28            x create custom kernel conf-file
29              - cd usr/src/sys/i386/conf/
30              - copy default kenrnel GENERIC to eg MYKERNEL
31              - edit/modify MYKERNEL
32            x configure sources(really?)
33              - run /usr/sbin/config MYKERNEL
34            x build kernel
35              - cd ../../MYKERNEL
36              - make depend
37              - make
38              - make install
39          x use packet fiters (firewall):
40            x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html
41            x some options at the kernel have to be enabled:
42              options IPFIREWALL                       #Compiles into the kernel the code for packet filtering.
43              options IPFIREWALL_VERBOSE    #Enables code to allow logging of packets through syslogd.
44                                                                      # Without this option, even if you specify that packets should be logged in the filter rules,
45                                                                      #  nothing will happen.
46              options IPFIREWALL_VERBOSE_LIMIT=10      #Limits the number of packets logged through syslogd on a per entry basis.
47                                                                                        # You may wish to use this option in hostile environments in which you want to log firewall activity,
48                                                                                        # but do not want to be open to a denial of service attack via syslog flooding.
49                                                                                        # When a chain entry reaches the packet limit specified, logging is turned off for that particular entry.
50                                                                                        # To resume logging, you will need to reset the associated counter using the ipfw(8) utility:
51                                                                                        #        ipfw zero 4500
52                                                                                        #    Where 4500 is the chain entry you wish to continue logging.
53              options IPFIREWALL_DEFAULT_TO_ACCEPT     #This changes the default rule action from ``deny'' to ``allow''.
54                                                                                            # 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.
55                                                                                            # It is also very useful if you often use ipfw(8) as a filter for specific problems as they arise.
56                                                                                            # Use with care though, as this opens up the firewall and changes the way it works.
57            x firewall is enabled at /etc/rc.conf (or /etc/rc.conf.local)
58                 firewall_enabled = "YES"
59                 firewall_type = "<firewall_type>"
60              x <firewall_type> is either a case at /etc/rc.firewall (/etc/rc.firewall6 for ipv6)
61                 or some custom file to read rules from.
62              x  Use firewall_type = "OPEN" for default policy 'OPEN' (allow all)
63              
64          
65    
66    - QoS (Quality of Services)    - QoS (Quality of Services)
67      o check it out !      o check it out !

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

MailToCvsAdmin">MailToCvsAdmin
ViewVC Help
Powered by ViewVC 1.1.26 RSS 2.0 feed