Bullet M2 Issues - Can see network but does not connect.

Login to the GUI console, then go to
Advanced -- AirMax Settings -- Enable AirMax (uncheck this option)

http://www.ubnt.com/forum/archive/index.php/t-16920.html

Error code: ssl_error_ssl_disabled

Error yang muncul di firefox saat membuka site-site yang butuh security lebih (fb, ymail, blogger, gmail, e.t.c)Solution :
Ketik %APPDATA%\Mozilla\Firefox\Profiles\ di RUN
Kemudian klik bla-bla-bal.default
Temukan file cert8.db
HAPUS file itu

Rate algorithm performance

Hi everyone, somebody has experiencie working with rate algorithm (Optimistic Algorithm, Conservative Algorithm, EWMA Algorithm) can tell me when you uses and for what.

Thanks.

-----

A simplification is....

Optimistic means it tries the best speed, but more sensitive to noise problems.
Conservative is less prone to noise, but slower.

Channel Spectrum Width: Semakin kecil semakin bagus (5Mhz)
Output Power: Power besar, belum tentu data lancar. Pertimbangkan antara jarak dan stablitas link (25db untuk 6km)
Distance: Point ini berpegaruh besar dalam QOS link

error vr0 pada pfsense

Oct 16 02:19:46 captive-portal kernel: vr0: link state changed to DOWN
Oct 16 02:19:48 captive-portal kernel: vr0: link state changed to UP
Oct 16 02:19:50 captive-portal check_reload_status: rc.linkup starting
Oct 16 02:19:50 captive-portal php: : Processing vr0 - start
Oct 16 02:19:50 captive-portal php: : Processing star

---

System > Advanced (very bottom)
Disable Hardware Checksum Offloading : Checking this option will disable hardware checksum offloading. Checksum offloading is broken in some hardware, particularly some Realtek cards. Rarely, drivers may have problems with checksum offloading and some specific NICs.

Resetter Epson T20

Berikut ini aplikasi/software resetter waste ink level pada Printer Epson T20. Aplikasi ini benar-benar bekarja sebagaimana mestinya.
1. Cukup jalankan adjprog.exe dan pilih partikular Adjusment Mode
2. Pilih Waste Ink Pad Counter, Klick OK
3. Klick Check, setelah keluar angka di main pad counter,
4. klick intialization.
Setelah itu printer anda akan di reset. Klick Oke lalu Finish..

Sekarang printer Epson T20 anda telah ter reset.
http://www.enterupload.com/rf2agya2ijhn/Epson_T20e_Reseter.zip.html  // pass : anakwarok
link repair printer : http://ekohasan.blogspot.com

Webserver Optimizations by Yahoo!

The Yahoo! Exceptional Performance team has identified a number of best practice rules for making web pages fast. They have identified 34 rules which are divided into seven categories.

Check this @ :

http://developer.yahoo.com/performance//rules.html

blank page dologin.php@daloradius

#cd /usr/ports/databases/pear-DB
#make clean
#make && make install
#pkg_info |grep pear
pear-1.9.0          PEAR framework for PHP
pear-DB-1.7.13,1    PEAR Database Abstraction Layer

buka browser, trs cek dalo.xxx.net.id dan coba login, traraaa....
Ternyata tadi kurang pear-nya
[solved]

Mencari Driver Unknown Device

My Computer Klik Kanan -- Properties -- Hardware -- Device Manager
Klik Kanan pada device yang belum terinstall drivernya (warna kuning) -- Properties -- Details 

Pilih Device Instance Id 

Informasi yang diperlukan hanyalah kode VENDOR (VEN_) dan kode DEVICE (DEV_)

              i.e : HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_10......

Setelah ditemukan kode vendor dan kode device, maka driver dapat diketahui dengan menggunakan http://www.pcidatabase.com/

mysql dump from windows to linux (sebaliknya)

lower_case_table_names=0 for Unix
lower_case_table_names=2 for Windows

Updating port collection FreeBSD

Proses UPDATE
 Mendownload file update ke dalam /var/db/portsnap

# portsnap fetch

Mengextract file update 

# portsnap extract
# portsnap update

----

This isn't an amazingly difficult upgrade.  However there are a few
gotchas you should be aware of.

    *) MySQL 5.0.x is pretty much backwards compatible with 4.1.x -- ie.
       everything that's in 4.1.x is also in 5.0.x (but the converse is
       not true).  On disk data formats may be slightly changed, but you
       should be able to run the mysql_upgrade script to convert everything
       to 5.0.x style.  mysql_upgrade comes as part of the mysql-client-5.0.x
       port/package

       You should certainly take good backups of your 4.1.x databases,
       but if everything goes according to plan, you won't actually need
       to load them into the upgraded MySQL server.

    *) Upgrade the MySQL client port and its dependencies first.  MySQL
       client 5.0 will interoperate pretty well with MySQL server 4.1 but
       not necessarily vice versa.  You will also need to recompile
       anything that links against the MySQL shlibs, as the ABI has
       changed between the versions.  Using portupgrade makes that fairly
       simple, and portupgrade's feature of preserving any shlibs removed
       from old ports in /usr/local/lib/compat/pkg means the old 4.1
       dependent stuff will still continue to work even after you've updated --
       again, not that you should be planning to use mysql dependent
       programs while upgrading, but having that capability is useful if
       you run into problems.

    *) Make sure to shut down the mysql daemon before attempting to upgrade
       it.  I know this is bleeding obvious, but it's also easy to forget.
       Not doing this can lead to data corruption, and in fact the port will
       automatically kill any running mysql at re-install time. But do be sure
       to double check.

The sequence of thing you'll need to do is as follows:

    0) You've got good backups, haven't you?

    i) Examine the output of 'pkg_info -R mysql-client-\*' and note down
       any daemon processes that depend on MySQL.  You should shut those down
       for the duration of the upgrade process.  Alternatively you could
       drop to single user mode to carry out this whole procedure.

   ii) Edit /etc/make.conf and insert in it:

         WITH_MYSQL_VER= 50

       You can put extra compile time flags for the mysql port into
       /etc/make.conf at the same time.  eg. I tend to use something
       like this, which you should modify to suit your own needs:

         .if ${.CURDIR:M*/databases/mysql*}
         WITH_CHARSET=latin1
         WITH_XCHARSET=none
         WITH_COLLATION=latin1_swedish_ci
         WITH_OPENSSL=yes
         BUILD_OPTIMIZED=yes
         WITH_INNODB=yes
         WITH_ARCHIVE=yes
         WITH_FEDERATED=yes
         WITH_NDB=yes
         .endif 

       Or you can use the MAKE_ARGS array in pkgtools.conf to achieve a similar
       effect.  (Note that pkgtools.conf only applies to portupgrade et al,
       /etc/make.conf applies generally to any way of using the ports)

  iii) Make sure the database is shut down:

         /usr/local/etc/rc.d/mysql-server stop

   iv) Upgrade mysql-client, replacing mysql-client-4.1.x in the dependencies
       between your installed ports:

        portupgrade -o databases/mysql50-client -f mysql-client-\*

   iv) Upgrade mysql-server, replacing mysql-server-4.1.x in the dependencies
       between your installed ports:

        portupgrade -o databases/mysql50-server -f mysql-server-\*

    v) Force a recompile of everything else that depends on mysql-client so
       that they all link against the upgraded shlib:

        portupgrade -Nfi -r mysql-client-\* -x mysql-client -x mysql-server

       Certain MySQL related ports are specific to one mysql version, such
       as eg. p5-DBD-mysql50-3.0006 or mysql-scripts-5.0.24 and you may have
       to use the 'portupgrade -o port/name -f pkg' style of command to get
       them upgraded properly.

   vi) Restart mysql-server.  Immediately run the mysql-upgrade program:

        mysql_upgrade -v -b /usr/local -d /var/db/mysql -u root

       (Will prompt you for the root at localhost password to the DB)
       That should fix up anything that needs fixing, especially the user
       grant tables.

       Examine /var/db/mysql/$HOSTNAME.err to see if there are any obvious
       problems, and do whatever tests you need to on the contents of your
       DB to assure yourself it has come through intact.

  vii) Restart all mysql client programs.  Test that they function correctly.

 viii) Make haste to nearest public house and order yourself a pint of
       your favourite beer.  You've earned it.

 Cheers,

 Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       7 Priory Courtyard
                                                      Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey         Ramsgate
                                                      Kent, CT11 9PW

Remote Backups With Rsync

By Noel Davis

In this article we explain how to automate the backup of files on remote machines to a centralized server using rsync.

rsync is a command line utility that is used to synchronize files between two computers over a network to synchronize files between two filesystems. It was written as a replacement for rcp but with many new features. For example it uses an algorithm that will only transfer files that have been modified. SSH will be used to authenticate between the machines and to encrypt the network traffic.

The situation: We have four machines named: server, machine1, machine2, and machine3. The server has a tape drive that is used to do nightly backups. machine1 is used as a development box and has files that need to be backed up in /src and in /home. machine2 is used for mail and needs /home and /mail to be backed up. machine3 is a web server and needs /home, /var/www, and /etc/httpd backed up.

Create a shell script for each machine. Simplify your maintenance by placing the scripts in a central location. I like to use /root/scripts. Decide on where you want to log your output. I like /root/logs but another common option is to have the script mail you the output.

Add entries to your crontab to call the scripts. Make sure you leave enough time before your normal backups of the server that the rsync jobs complete.

Each night the following will occur:

1. rsync machine1 -> Server
2. rsync machine2 -> Server
3. rsync machine3 -> Server
4. backup server to tape

Let's take a look at the flags used for rsync in the examples:

rsync -ave ssh --numeric-ids --delete machine1:/home /machine1

* -a:
Archive mode
* -v:
Verbose output
* -e ssh:
Specify the remote shell as ssh
* --numeric-ids:
Tells rsync to not map user and group id numbers local user and group names
* --delete:
Makes server copy an exact copy of the source by removing any files that have been removed on the remote machine
* machine1:/home:
The remote machine name, then the directory to be backed up
* /machine1:
The directory to place the backup

Next generate a public private key pair with ssh. Place the public key in the ~/.ssh/authorized_keys file in an account on machine1, machine2, and machine3 that has read access to the directories that need to be backed up. It is best not to use the root account on the remote machines, but you should evaluate the risk in your environment. Test that you can login to these accounts using ssh without using a password.

Test each one of the rsync scripts. The first time you run rsync will take the longest as it will need to copy all the files from the remote machines and not just the files that have changed.

Add the /machine1, /machine2, and /machine3 (or whatever you have named them) directories to the servers backup script.

While this process does not backup the entire remote machine, it will ensure that you will not lose irreplaceable data.

Starting with the example scripts included in this tutorial there are many changes that can be made to fit your specific circumstances.

The frequency of the rsyncs can be modified to occur more often or at different times. Simply by adding additional crontab lines the backup from the remote machines could be done everyday at lunch, multiple times a day or even hourly.

The scripts could also be changed to rotate between multiple backups on the server or could be changed to do some sort of processing on the files before they are backed up. For example if the home directories you are backing up contain web browser caches, they could be removed after the rsync but before the system backup.

Using this article as a starting point you should create a backup plan that fit your needs.

Example rsync script for machine1:

#!/bin/bash

rsync -ave ssh --numeric-ids --delete machine1:/home /machine1
rsync -ave ssh --numeric-ids --delete machine1:/src /machine1


Example rsync script for machine2:

#!/bin/bash

rsync -ave ssh --numeric-ids --delete machine2:/home /machine2
rsync -ave ssh --numeric-ids --delete machine2:/mail /machine2


Example rsync script for machine3:

#!/bin/bash

rsync -ave ssh --numeric-ids --delete machine3:/home /machine3
rsync -ave ssh --numeric-ids --delete machine3:/var/www /machine3
rsync -ave ssh --numeric-ids --delete machine3:/etc/httpd /machine3



Example crontab file logging to a directory:

# Scripts to rsync machines
59 20 * * * /root/scripts/sync-machine1.sh >/root/logs/sync-machine1.log 2>&1
59 21 * * * /root/scripts/sync-machine2.sh >/root/logs/sync-machine2.log 2>&1
59 22 * * * /root/scripts/sync-machine3.sh >/root/logs/sync-machine3.log 2>&1
#
# Nightly Backup script
59 23 * * * /root/scripts/backup.sh > /root/logs/backup.log 2>&1

Example crontab file mailing the output:

# Scripts to rsync machines
59 20 * * * /root/scripts/sync-machine1.sh
59 21 * * * /root/scripts/sync-machine2.sh
59 22 * * * /root/scripts/sync-machine3.sh
#
# Nightly Backup script
59 23 * * * /root/scripts/backup.sh

-----------
VERSI FREEBSD DIARY
-----------

This article originally appeared quite some time ago.  But for some unknown reason, it was lost from the indexes.  I've just come back to upgrade it with some new error observations.We now return you to your regularly scheduled read... rsync is an amazing and powerful tool for moving files around.   I know of people that use it for file transfers, keeping  dns server records up-to-date, and along with sshd to remote restart the services when rsync reports a file change (how they do that, I don't know, I'm just told they do it). This article describes how you can use rsync to synchronize file trees.  In this case, I'm using two websites to make sure one is a backup of the other.  As an example, I'll be making sure that one box contains the same files as the other box in case I need to put the backup box into production, should a failure occur.

Overview

rsync can be used in six different ways, as documented in man rsync: for copying local files. This is invoked when neither source nor destination path contains a : separator for copying from the local machine to a remote machine using a remote shell program as the transport (such as rsh or ssh). This is invoked when the destination path contains a single : separator. for copying from a remote machine to the local machine using a remote shell program. This is invoked when the source contains a : separator. for copying from a remote rsync server to the local machine. This is invoked when the source path contains a :: separator or a rsync:// URL. for copying from the local machine to a remote rsync server. This is invoked when the destination path contains a :: separator. for listing files on a remote machine. This is done the same way as rsync transfers except that you leave off the local destination. I'll only be looking at copying from a remote rsync server (4) to a local machine and when using a remote shell program (2).

Installing

This was an easy port to install (aren't they all, for the most part?).   Remember, I have the entire ports tree, so I did this: # cd /usr/ports/net/rsync # make install If you don't have the ports tree installed, you have a bit more work to do.... As far as I know, you need rsync installed on both client and server, although you do not need to be running rsyncd unless you are connecting via method 4.

Setting up the server

In this example, we're going to be using a remote rsync server (4). On the production web server, I created the /usr/local/etc/rsyncd.conf file.  The contents is based on man rsyncd.conf. uid = rsync gid = rsync use chroot = no max connections = 4 syslog facility = local5 pid file = /var/run/rsyncd.pid [www] path = /usr/local/websites/ comment = all of the websites You'll note that I'm running rsync as rsync:rsync.  I added lines to vipw and /etc/group to reflect the new user.  Something like this: rsync:*:4002:4002::0:0:rsync daemon:/nonexistent:/sbin/nologin and rsync:*:4002: Then I started the rsync daemon and verified it was running by doing this: # rsync --daemon # ps auwx | grep rsync root 30114 0.0 3.7 936 500 ?? Ss 7:10PM 0:00.04 rsync --daemon And I found this in /var/log/messages: rsyncd[30114]: rsyncd version 2.3.2 starting Then I verified that I could connect to the daemon by doing this: # telnet localhost 873 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. @RSYNCD: 21 I determined the port 873 by looking at man rsyncd.conf. See the security section for more information. You can also specify a login and user id.  But if you do that, I suggest you make /usr/local/etc/rsyncd.conf non-world readable: chmod 640 /usr/local/etc/rsyncd.conf This example is straight from the man page.  Add this to the configuration file: auth users = tridge, susan secrets file = /usr/local/etc/rsyncd.secrets The /usr/local/etc/rsyncd.secrets file would look something like this: tridge:mypass susan:herpass And don't forget to hide that file from the world as well: chmod 640 /usr/local/etc/rsyncd.secrets

Setting up the client

You may have to install rsync on the client as well.. There wasn't much to set up on the client.  I merely issued the following command.  The rsync server in question is ducky. rsync -avz ducky::www /home/dan/test In the above example, I'm connecting to ducky, getting the www collection, and putting it all in /home/dan/test. And rsync took off!  Note that I have not implemented any security here at all.   See the security section for that. I checked the output of my first rsync and decided I didn't want everything transferred.  So I modified the command to this: rsync -avz --exclude nz.freebsd.org/* --exclude wusage/* ducky::www /home/dan/test See the man pages for more exclusion options. I also wanted deleted server files to be deleted on the client.  So I did this: rsync -avz --delete ducky::www /home/dan/test Of course, you can combine all of these arguments to suit your needs. I found the --stats option interesting: Number of files: 2707 Number of files transferred: 0 Total file size: 16022403 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 44388 Total bytes written: 132 Total bytes read: 44465

Security

My transfers are occur on a trusted network and I'm not worried about the contents of the transfer being observed.  However, you can use ssh as the transfer medium by using the following command: rsync -e ssh -avz ducky:www test Note that this differs from the previous example in that you have only one : (colon) not two as in the previous example. See man rsync for details. In this example, we will be grabbing the contents of ~/www from host ducky using our existing user login. The contents of the remote directory will be synchronized with the local directory test. Now if you try an rsync, you'll see this: $ rsync -e ssh -avz --delete ducky:www /home/dan/test Password: @ERROR: auth failed on module www Here I supplied the wrong password and I didn't specify the user ID.  I suspect it used my login.  A check of the man page confirmed this.  This was my next attempt.  You can see that I added the user name before the host, ducky.. $ rsync -e ssh -avz --delete susan@ducky:www /home/dan/test Password: receiving file list ... done wrote 132 bytes read 44465 bytes 1982.09 bytes/sec total size is 16022403 speedup is 359.27 In this case, nothing was transferred as I'd already done several successful rsyncs. The next section deals with how to use a password in batch mode.

Do it on a regular basis

There's no sense in having an rsync set up if you aren't going to use it on a regular basis.  In order to use rsync from a cron job, you should supply the password in a non-world readable file.  I put my password in /home/dan/test/rsync.password.   Remember to chmod 640 that password file!I put the command into a script file (rsync.sh), which looks like this: #!/bin/sh /usr/local/bin/rsync -e ssh -avz --stats --delete susan@ducky::www /home/dan/test --password-file /home/dan/test/rsync.password Remember to chmod 740 the script file! Then I put this into /etc/crontab in order to run this command every hour (this should be all on one line): 7 * * * * root /usr/home/dan/rsync.sh 2>&1 | mail -s "rsync script" root The above will mail you a copy of the output. If you want to use ssh as your transport medium, I suggest using using the authorized_keys feature.

My comments

I think rsync is one of the most powerful tools I've seen for transferring files around a network and the Internet.  It is just so powerful! Although I actually use cvsup to publish the Diary, I am still impressed with rsync.

Some recent errors I encountered

I was recently adding some new files to my rsync tree.  I found these errors: receiving file list ... opendir(log): Permission denied opendir(fptest): Permission denied opendir(example.com): Permission denied opendir(example.org): Permission denied readlink dan: Permission denied opendir(default): Permission denied It took me a while to understand the problem.  It's a read issue.  rsyncd didn't have permission to read the files in question.  You can either make rsynd run as a different user, or change the permissions on the files. If you get the user id for rsync wrong, you'll see this error: $ rsync -avz xeon::www /home/dan/rsynctest @ERROR: invalid uid I had the rsync user misspelt as rysnc.

PHP Notice : Undefined index:

OPAC SENAYAN, tau kan?
Siang tadi dapet laporan dari webmin klo opac udah dipasang dengan release yg terbaru, tapi ternyata muncul error

PHP Notice:  Undefined index:  detail_button in /www/LIB/lib/biblio_list.inc.php on line 267
PHP Notice:  Undefined index:  detail_button in /www/LIB/lib/biblio_list.inc.php on line 267

Cek punya cek, "http://www.hotscripts.com/forums/php/36618-solved-getting-php-notice-undefined-index-http_referer-c-inetpub-cgi-bin-search5-php-o.html", berikut penuturan dari UnrealEd

this notive means that the key 'HTTP_REFERER' is not set in the $_SERVER array. Try using this code to see if the key exists, and then start doing stuff with it:

PHP Code:

if(isset($_SERVER['HTTP_REFERER'])){
  // do stuff} 

UnrealEd

Solusi untuk notice tersebut adalah dengan mengubat parameter 'error_reporting = E_ALL' yang ada di php.ini menjadi 'error_reporting = E_ALL ^ E_NOTICE' .
Kasus ini terjadi di nginx dengan fastcgi sebagai server API nya

Boot up radiusd

if [ -x /usr/local/bin/mysqld_safe ]; then
        /usr/local/bin/mysqld_safe >/dev/null 2>&1 &
        echo -n ' mysqld '
        sleep 10
        /usr/local/sbin/radiusd -X >/dev/null 2>&1 &
fi

Radiusd yang dikombinasikan dengan mysql terkadang mengalami permasalahan pada saat system boot-up. Permasalahan yang terjadi adalah radiusd tidak dapat terkoneksi dengan mysql, hal itu disebabkan karena mysql membutuhkan waktu sekian seconds untuk starting. Untuk mengakali hal tersebut maka "sleep 10" di perlukan untuk menambahkan delay antara starting mysql server dan radiusd.

Re: nginx No input file specified.

September 21, 2009 05:44AM     Registered: 6 months ago

Posts: 4

After some tweaking the problem came to the surface. It was the "open_basedir" option in php.ini. You should point that parameter to your document root directory like /var/www or /src/http. It should be the same as the "root" option in this section:

location ~ \.php$ {

                        root /var/www;

                        include /usr/local/nginx/conf/fastcgi_params;

                        fastcgi_pass   localhost:9000;

                        fastcgi_index  index.php;

               }

Thanks for the help.

blo

http://forum.nginx.org/read.php?11,7965,8079

------
nah ini yang di file php.ini-nya
open_basedir ="/www:/var/tmp"
upload_max_filesize = 8M

NOTES:
/www padake karo "root" sing di set nengi" location"
/var/tmp yen iki tmp default'e engine X
8M gen upload iso luweh ginuk-ginuk


padahal safe_mode=off lo, tapi kok open_basedir yo isih ngaruh?

----
Selanjutnya permasalah nginx dengan moodle, pada saat mengakses file "file.php". Intinya file tersebut berhubungan dengan slash sama backward, jadi di nginx.conf perlu sysntac kayak berikut ini

#  >>FastCGI<<
   location ~ \.php(.*)$ {
                root            /www/E-GURU;
                fastcgi_pass   127.0.0.1:9000;
                include        fastcgi_params;
                        if (!-e $request_filename) {
                                rewrite ^(.*\.php)(/)(.*)$ $1?file=/$3 last;
                }
        }
}
# >> end of php<<
-----
 >>php-cgi.sh , buat on-off in phpnya di nginx <<
PROVIDES=php-cgi
LIGHTTPD_FCGI=/usr/local/bin/spawn-fcgi
SERVER_IP=127.0.0.1
SERVER_PORT=9000
SERVER_USER=nginx
SERVER_GROUP=nginx
PHP_CGI=/usr/local/bin/php-cgi
PHP_FCGI_CHILDREN=10
PGREP=/bin/pgrep
KILLALL=/usr/bin/killall
### No editing below ####
cmd=$1

pcgi_start(){
   echo "Starting $PROVIDES..."
  $LIGHTTPD_FCGI -a $SERVER_IP -p $SERVER_PORT -u $SERVER_USER -g $SERVER_GROUP -f $PHP_CGI -C $PHP_FCGI_CHILDREN
}

pcgi_stop(){
 echo "Killing $PROVIDES..."
 $KILLALL $PROVIDES
}

pcgi_restart(){
 pcgi_stop
 sleep 1
 pcgi_start
}

pcgi_status(){
        $PGREP $PROVIDES > /dev/null
 [ $? -eq 0  ] && echo "$PROVIDES running" || echo "$PROVIDES NOT running"

}

pcgi_help(){
   echo "Usage: $0 {start|stop|restart|status}"
}

case ${cmd} in
[Ss][Tt][Aa][Rr][Tt]) pcgi_start;;
[Ss][Tt][Oo][Pp]) pcgi_stop;;
[Rr][Ee][Ss][Tt][Aa][Rr][Tt]) pcgi_restart;;
[Ss][Tt][Aa][Tt][Uu][Ss]) pcgi_status ;;
*)      pcgi_help ;;
esac

compile error [OpenBSD 4.5]

../../../../arch/i386/pci/

pci_machdep.c: In function `pci_intr_map':

../../../../arch/i386/pci/pci_machdep.c:446: error: `PCI_INT_VIA_ISA' undeclared (first use in this function)

../../../../arch/i386/pci/pci_machdep.c:446: error: (Each undeclared identifier is reported only once

../../../../arch/i386/pci/pci_machdep.c:446: error: for each function it appearsin.)

*** Error code 1

Stop in /usr/src/sys/arch/i386/compile/Diajeng.Net (line 92 of /usr/share/mk/sys.mk).

====== solved with option below ======

pcibios0 at bios0 flags 0x0000 # use 0x30 for a total verbose

============================

gscpcib.o(.text+0xb0): In function `gscpcib_attach':

: undefined reference to `gpiobus_print'

acpi.o(.text+0x58): In function `acpi_gasio':

: undefined reference to `acpiec_read'

acpi.o(.text+0x6d): In function `acpi_gasio':

: undefined reference to `acpiec_write'

*** Error code 1

====== solved with option below ======

acpiec* at acpi?

============================

gcc: Internal error: Killed: 9 (program cc1)

Gejala kekurangan memory saat compile!
NB : 64MB nggk kuat buat compile libxml , prediksi memory usage untuk compile yang lain mungkin sama pula. OS free 7.0-release

SNR=84% BER=0

Satelite configuration >> Non Standar User defind configuration >>

Satelit position = 108 OE NS II Telkom 1 CBand
LNB = 0
LOF/L = 05150
LOF/H = 05150
Threshold = 11700

22 Khz = Off
Voltage = 18v

#SAVE

====
Manual transpoder Scan

Freq = 03807
Polar = H
FEC = 3/4
Symboli rate = 04000


Trans-7 Jayapura TVE+Radio
F=03989 F=03797 F=03785
Sys=06002 Sys=03902 Sys=04000
P=H P=H P=v

Telkom Indo JTV
F=03792 F=04095
Sym=03001 Sys=03123
P=H P=H

Comparision between Nanostation2 and NS2 Loco

NS2 has
Integrated 10dBi Dual Pol + External SMA antenna and connector
TX Power 26dBm, +/-2dB
RX Sensitivity -97dBm +/-2dB

NS2 Loco has?
Antenna Integrated 10dBi Dual Pol

TX Power 20dBm, +/-1dB
RX Sensitivity -95dBm +/-1dB

Now let's check distances
IN NS2 it is over 15 km
In loco it is Over 5Km.

Conclusion:
Loco is cheap but not good for long distances. You may use it with in 2-3 miles by using 802.11b

dslreports.com

#sysctl HACKS

#OpenBSD
net.bpf.bufsize=2097152
net.bpf.maxbufsize=4194304 
net.inet.tcp.recvspace=65535
net.inet.tcp.sendspace=65535
net.inet.ip.maxqueue=2048
kern.somaxconn=2048
net.bpf.bufsize=2097152
net.bpf.maxbufsize=4194304
net.inet.ip.portfirst=32768
net.inet.ip.portlast=49151
net.inet.ip.porthifirst=49152
net.inet.ip.porthilast=65535
kern.shminfo.shmmax=67018864
kern.shminfo.shmall=32768



#FreeBSD 8.0
net.inet.tcp.inflight.enable=1
net.inet.tcp.inflight.min=6144
net.inet.tcp.inflight.max=1073725440
net.inet.tcp.inflight.stab=20
net.inet.tcp.recvspace=65536
net.inet.ip.redirect=0
net.inet.tcp.syncookies=1
net.inet.tcp.delayed_ack=0
kern.coredump=0
kern.maxfiles=65536
kern.maxfilesperproc=32768
kern.maxprocperuid=16384
kern.ipc.maxsockbuf=2097152
kern.ipc.nmbclusters=32768
net.inet.udp.maxdgram=57344
kern.threads.max_threads_per_proc=40000
kern.threads.max_groups_per_proc=40000
net.inet.ip.portrange.first=32768
net.inet.ip.portrange.last=49151
net.inet.ip.portrange.hifirst=49152
net.inet.ip.portrange.hilast=65535
kern.ipc.somaxconn=1024
kern.ipc.shmmax=67108864
kern.ipc.shmall=32768
net.inet.ip.maxfragpackets=1600

#FreeBSD Older Versions (Check your sysctl values)
net.tcp.inflight.enable=1
net.inet.tcp.inflight.min=6144
net.inet.tcp.inflight.max=1073725440
net.inet.tcp.inflight.stab=20
net.inet.tcp.recvspace=65536
net.inet.ip.redirect=0
net.inet.tcp.syncookies=1
net.inet.tcp.delayed_ack=0
kern.coredump=0
kern.maxfiles=65536
kern.maxfilesperproc=32768
kern.maxprocperuid=16384
kern.ipc.maxsockbuf=2097152
kern.ipc.nmbclusters=32768
net.inet.udp.maxdgram=57344
kern.threads.max_threads_per_proc=40000
kern.threads.max_groups_per_proc=40000
net.inet.ip.portrange.first=32768
net.inet.ip.portrange.last=49151
net.inet.ip.portrange.hifirst=49152
net.inet.ip.portrange.hilast=65535
kern.ipc.somaxconn=1024
kern.ipc.shmmax=67108864
kern.ipc.shmall=32768
net.inet.ip.maxfragpackets=1600



#Good settings for updating stuff
#NOTE: Make sure to pick servers close to you.

CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs
export CVSROOT
PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/4.4/packages/i386/
export PKG_PATH

#First checkout the source
cd /usr
cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_4 -P src
cd /usr
cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_4 -P ports

#Get Source
cd /usr/src;
cvs -q up -rOPENBSD_4_4 -Pd;

#Get Ports
cd /usr/ports;
cvs -q up -rOPENBSD_4_4 -Pd;

#Rebuilding the kernel
#To rebuild the default kernel from stable:

cd /usr/src/sys/arch/i386/conf
/usr/sbin/config GENERIC
cd /usr/src/sys/arch/i386/compile/GENERIC
make clean && make depend && make

#Replace i386 with your architecture, e.g. sparc, alpha, etc.
#Rebooting with the new kernel

#To reboot with the newly compiled kernel:

cd /usr/src/sys/arch/i386/compile/GENERIC
cp /bsd /bsd.old          (Save an old copy of your kernel)
cp bsd /bsd               (Copy the new kernel into place)
reboot

#As above, substitute your architecture for i386. If your system has trouble booting the new kernel, you can easily go back and reboot from the old kernel, now called bsd.old.
#Rebuilding the binaries

#To rebuild the system binaries:

rm -rf /usr/obj/*
cd /usr/src
make obj
cd /usr/src/etc && env DESTDIR=/ make distrib-dirs
cd /usr/src
make build

#This will take awhile... 

#FreeBSD install 6.3(WuTang Style)
#OS
cvsup supfile && cd /usr/src && make buildworld && make buildkernel KERNCONF=foo && make installkernel && make installworld && reboot

#Ports
cvsup ports && cd /usr/ports/pathto/port && make deinstall && make install clean


#FreeBSD install 7.2 (Updated Style)

#Binary only updates:
freebsd-update fetch install

#The Real Deal
csup -g -L 2 /etc/stable-cvsup.conf && cd /usr/src && make buildworld && make buildkernel KERNCONF=FOO && make installkernel KERNCONF=FOO && mergemaster -pai && make installworld && make delete-old && mergmaster -Uai && reboot

#Port Updates:
portaudit -Fda
portsnap fetch extract
portupgrade -fa

www.shirkdog.us