mysql backup - restore

membackup
mysqldump -uroot -p nama_database > nama_file_backup


merestore
mysql -u root -p nama_database < nama_file_backup

Persistence VLAN Configuration

To make configuration persistence, open /etc/rc.conf:

# vi /etc/rc.conf

Append / modify as follows:

cloned_interfaces="vlan0"
ifconfig_vlan0="inet x.x.x.x netmask y.y.y.y vlan 2 vlandev em0"

Lost Browser Icon BlackBerry

You need to resend your service books. Options - Advanced Options - Host Routing Table -Highlight one of the addresses in there - hit the menu button (right of the green call button) and click register now.

http://forums.crackberry.com/blackberry-storm-f86/lost-browser-my-storm-help-99289/

Debian Kiosk

I have configured a kiosk using Debian GNU/Linux with blackbox window manager.

The challenges:
1. Touchscreen configuration.
2. Autometic login and start X server.
3. Start desired application for kiosk.
4. A boot splash for booting and shutdown.
 
1. Touchscreen configuration:
First, setup touchscreen driver and configure it according to your device specification.
I was using eGalax driver, which I have downloaded from
source: http://home.eeti.com.tw/web20/eg/drivers.htm 

2. Automatic login:
Edit /etc/inittab and comment the following line:

#1:2345:respawn:/sbin/getty 38400 tty1

add the following line below:

1:2345:respawn:/bin/login -f USER_LOGIN tty1 /dev/tty1 2>&1 

Edit .bash_profile (create if require) and add the following line at bottom:

startx

source: http://www.debianadmin.com/how-to-auto-login-and-startx-without-a-display-manager-in-debian.html

Blackbox window manager:
Edit ~/.xinitrc (or ~/.Xsession), create if require, and add the following line:

exec blackbox

3. Autostart application:
To autostart iceweasel/firefox:
Again edit ~/.xinitrc (or ~/.Xsession) and add the following line:

firefox &
exec blackbox

source: http://blackboxwm.sourceforge.net/BlackboxFAQ/StartupAndShutdown

Install iceweasel/firefox plugin "R-kiosk" from https://addons.mozilla.org/en-US/firefox/addon/1659

3. Bootsplash:
Install a bootsplash

apt-get install splashy

Create your own bootsplash and set it

# splashy_config -c

To enable splashy, you may need to edit grub.config and add the following after "kernel...ro quiet"

vga=791 splash

source: http://splashy.alioth.debian.org/wiki/faq

Tips and tricks:
"X: user not authorized to run the X server"
You can allow the user to use run startx by:

#dpkg-reconfigure x11-common

or edit  /etc/X11/Xwrapper.config

allowed_users=anybody 

"Auto login problem"
 If you have setup GDM (XDM) earlier, then you need to disable it for automatic log in

#update-rc.d -f gdm remove

If you want to enable it simply run (experiment purpose):

#update-rc.d -f gdm defaults

source: http://www.debianadmin.com/howto-boot-debian-in-text-mode-instead-of-graphical-mode-gui.html

Kiosk performance tuning:
Install the CPU frequency related tools and configure it.
details: http://wiki.debian.org/HowTo/CpuFrequencyScaling

resources:
http://salahuddin66.blogspot.com/2010/04/debian-kiosk.html

http://www.debianadmin.com/debirf-build-a-kernel-and-initrd-to-run-debian-from-ram.html
http://cmrg.fifthhorseman.net/wiki/debirf

LinuxMint Tips

If you've configured some things brocken in your panel or simply delete it by mistake (like me) then
- open a terminal (Alt-F2) and enter
gconftool --recursive-unset /apps/panel
that should reset the complete panel to mint defaults.

Edit: Thanks to Redsandro:
You can also remove the configuration. For gnome:

mv ~/.gconf/apps/panel ~/.gconf/apps/panel.old

Then logout and login again.

http://community.linuxmint.com/tutorial/view/333

----

"Sound volume too low"
Just go to "Terminal" , then type "alsamixer"
----

"Setting ip address"
Go to "Terminal"
#nano -w /etc/networking/network-scripts/ifcfg-eth0
masukkan script berikut ini ..

auto eth0
iface eth0 inet static
address 192.168.23.13
netmask 255.255.255.240
broadcast 192.168.23.15
network 192.168.23.0
gateway 192.168.23.14

#/etc/init.d/networking restart
Selesai ...

root: unknown user

This problem occurs because the file /etc/master.passwd damaged

1. Start FreeBSD server
2. Enter key at boot loader
    At Welcome to FreeBSD! boot menu press spacebar key to pause default booting
    Type number 4 key (type 4 number) to boot into single user mode

3. Press Enter Key, When prompted Enter full pathname of shell or RETURN for /bin/sh:
4. You need to remount / (root) file system in read and write mode with mount command, type the following commands:
    # mount -u /
    # mount -a
5.restoring /etc/master.passwd
    #cp /var/backups/master.passwd.bak /etc/master.passwd
    #pwd_mkdb -C /etc/master.passwd
    #pwd_mkdb -p /etc/master.passwd
    #pwd_mkdb /etc/master.passwd
6. change the root password
    #passwd root
7. reboot ...

http://www.cyberciti.biz/tips/howto-freebsd-reset-recover-root-password.html

Lost password Windows 7

Just folow the following steps and everything will be ok:

1. Boot from Windows PE/RE and start the command prompt
2. Use the following command to create a copy of the Stick Keys application: copy c:/windows/system32/sethc.exe c:/ (where c is the drive letter where your OS is installed)
3. The next command will replace the Sticky Keys application with command prompt: copy /y c:/windows/system32/cmd.exe c:/windows/system32/sethc.exe
4. Reboot your computer and when you see the log-on screen and press Shift key five times.
5. Now you will see a command prompt window. Here you will use the following command: net user you_user_name new_password
6. That’s it. Now you can use your new password to log in.
7. Don’t forget to restore the Sticky Keys application:  copy /y c:/sethc.exe c:/windows/system32/sethc.exe.

   http://www.pctips3000.com/how-to-reset-your-administrator-password-in-windows-7/
   

Multi-AP Roaming Network Background

There's no magic to making multiple-AP (roaming) 802.11 networks work. Wireless clients just assume that all APs with the same SSID are configured similarly and are all just different points of access to the same underlying wired network. A client will scan all channels looking for APs publishing the SSID it wants, and will pick whichever one suits it needs best (usually that means whichever one shows the highest signal strength).

Once on the network, clients stay with the same AP as long as it's meeting the client's needs (i.e. as long as it's signal strength is above a "good enough" threshold). If the client later thinks it could be better off with another AP on that network, it'll do periodic scans of all channels looking for other APs publishing that SSID. If a scan turns up a candidate AP that's enough better than the AP it's currently on, it'll automatically roam to the other AP, usually without so much as a missed frame.

Assuming both APs are configured similarly and are connected to the same underlying network, roaming is seamless and invisible to the user (except nerds like me who run tools to watch for these things). Roaming events are invisible to applications using the network, although some low-level parts of the network stack might be notified of the event, so that, for example, your DHCP client can double-check that this new AP really is connected to the same network, so it can be sure your DHCP lease is still valid on this network.

Some other users' Answers and Comments on this question erroneously suggested that wireless protocols or features like wireless relay or WDS might be needed for roaming, but this is absolutely incorrect. Those features are just ways to replace a wired Ethernet backhaul with a wireless one.

For the sake of completeness, I should mention that there is a set of technologies, some proprietary, some standardized in IEEE 802.11F, known generally as Inter-Access Point Protocol. IAPP is a method by which generally enterprise-class APs can communicate with each other over the backhaul to optimize client roaming. But that's just an optimization, not a prerequisite for roaming. Roaming works "well enough" on networks both small and large without any IAPP going on.

Configuration Suggestions

Give both APs the same network name (SSID), the same security type (WPA2-PSK recommended), and the same wireless security passphrase. Many clients assume that these kinds of settings will be the same across all APs with the same SSID.

Since you already have the cabling in place, use wired Ethernet as your backhaul. This saves your wireless bandwidth for your portable/mobile devices that actually need it, instead of wasting in on stationary devices like APs that could reasonably be cabled up.

If you have another device on the network, such as a broadband home gateway, providing NAT and DHCP service, then put both APs in bridge mode (turn off NAT and DHCP service). You generally only want one box on your network acting as a NAT gateway or serving DHCP. If you don't already have another device on your network doing NAT and DHCP, and you need those services, then you can have one of your APs do it. Have the more "upstream" AP (the one that's closer, topologically, to your broadband modem) do NAT and DHCP, and make sure that the wired Ethernet connection to the other AP comes from the first AP's LAN port. Also make sure that the "downstream" AP is in bridge mode. I call this out because I've seen people make the mistake of leaving NAT and DHCP enabled on both their APs, and I've seen clients that aren't smart enough to realize that, say, the 192.168.1.x/24 network they're on now is not the same 192.168.1.x/24 network they were on a moment ago in the other room. I've also seen users get confused in this situation where two laptops in the same house had 192.168.1.x addresses, but couldn't ping each other because they really on two separate IP networks behind two separate NATs.

Channel is one key setting you do want to vary from AP to AP in a roaming (multiple AP) 802.11 network. To maximize bandwidth, leave your APs to automatically select the channel to use, or you can manually pick different, non-overlapping, and hopefully unoccupied channels to use. You don't want transmissions to/from one AP to compete for bandwidth with transmissions to/from the other AP.

Additional Considerations

The rest of this answer is just a bunch of general "how to maximize your home 802.11 network bandwidth" tips, not specific to your question of two APs with the same SSID.

Consider taking this opportunity to fully modernize

If you're already buying a new AP and taking the time to reconfigure things, I'd recommend using this opportunity to replace your existing AP as well, by buying two of the latest APs that support simultaneous dual-band 802.11n technology. That way you can support both the 2.4GHz band for older clients that are 2.4GHz only, as well as the less busy 5GHz band for more bandwidth. It's becoming a "best practice" to set your 2.4GHz 802.11n radio to 20MHz (HT20) channels so that it leaves some of the band free for things like Bluetooth to use. This limits your 802.11n transmission rates in 2.4GHz to ~130mbps instead of 300mbps, but allows other non-802.11 2.4GHz devices to still work okay. In 5GHz, where there are many more channels available and they're all generally much less busy, you're encouraged to use 40MHz (HT40) channels to get maximum throughput.

I know that Apple's latest AirPort Extreme and Time Capsule (but not AirPort Express) are simultaneous dual-band 802.11n, and they also support 3-stream (a.k.a. "3x3") 802.11n, for transmission rates up to 450mbps once you get if you have 3-stream clients that can do it (Apple's clients are currently still on 2x2, so 300mbps max Apple's March 2011 "Thunderbolt" renewal of the MacBook Pro line quietly added 3x3 radios).

If you're stuck with older single-band-at-a-time APs

If you don't need to support any older 2.4GHz-only devices, use the 5GHz band since it is generally less busy, and you can use HT40 without starving Bluetooth and other uses.

If you're stuck supporting 2.4GHz-only devices with single-band-at-a-time APs, be careful of your channel selection. In the 2.4GHz band, the channels overlap to a great degree. However, channels 1, 6, and 11 don't overlap at all, so those are good choices to pick manually. You could use a Wi-Fi network scanner like NetStumbler, iStumbler, many "war driving" tools, etc. to see which channels are in use by other APs visible from where you are. If you suspect you have non-802.11 2.4GHz interferers in your area, such as Bluetooth, microwave ovens, and many (but not all) cordless phones, baby monitors, wireless webcams, and wireless room-to-room A/V senders, you could go all-out and get a spectrum analyzer like a Metageek Wi-Spy to find which channels are the least noisy where you are.

update

Setelah spliting table di database utama, tiba-tiba tombol update saya bermasalah.

solusi :

tambahkan opsi --safe-updates di bawah [mysqld] dan [mysqld_safe]

rsync

error code : rsync: link_stat "." (in squid) failed: Permission denied (13)

use chroot = yes
read only = yes

[squid]
path = /var/log/squid
comment = squid logs
include = *.log
list = yes
uid = proxy
gid = proxy
auth users = squid
secrets file = /var/log/squid/rsync.secrets
hosts allow = 192.168.0.254

Clock Synchronization with NTP

FreeBSD

#ntpdate -v -b 3.id.pool.ntp.org

rc.conf

ntpdate_enable="YES"
ntpdate_hosts="3.id.pool.ntp.org"

OpenBSD

rc.conf

ntpd_flags="-s"

MySQL FreeBSD Install

#
# pw groupadd mysql
# mkdir /server1/
# mkdir /server1/etc/
# chown -R mysql:mysql /server1/
# cp my.cnf /server1/etc/
# nano -w  /etc/hosts
127.0.0.1 localhost db1
# /usr/local/bin/mysql_install_db --defaults-extra-file=/server1/etc/my.cnf &
# echo "mysql_enable="YES" >> /etc/rc.conf
#

cpu info freebsd

db1# sysctl -a | egrep -i 'kern.version|hw.machine|hw.model|hw.ncpu'
kern.version: FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011
hw.machine: amd64
hw.model: Intel(R) Xeon(R) CPU           E5507  @ 2.27GHz
hw.ncpu: 4
hw.machine_arch: amd64

fix for disappearing system tray icons

XP : HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TrayNotify
VISTA/7: HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify

- Setelah itu delete IconStreams dan PastIconsStream
- Restart explore.exe (smadav-tool-system editor-apply & restart explore.exe)

rndc-OpenBSD 4.8

Generate configuration

#rndc-confgen
# Start of rndc.conf
key "rndc-key" {
        algorithm hmac-md5;
        secret "OOHUU7Jfc1lYydmaF+y+NA==";
};

options {
        default-key "rndc-key";
        default-server 127.0.0.1;
        default-port 953;
};
# End of rndc.conf

# Use with the following in named.conf, adjusting the allow list as needed:
# key "rndc-key" {
#       algorithm hmac-md5;
#       secret "OOHUU7Jfc1lYydmaF+y+NA==";
# };
#
# controls {
#       inet 127.0.0.1 port 953
#               allow { 127.0.0.1; } keys { "rndc-key"; };
# };
# End of named.conf

Buat file rndc.conf yg disimpan di /etc
#nano -w /etc/rndc.conf
key "rndc-key" {
        algorithm hmac-md5;
        secret "OOHUU7Jfc1lYydmaF+y+NA==";
};

options {
        default-key "rndc-key";
        default-server 127.0.0.1;
        default-port 953;
};

Sisipkan hasil confgen ke /var/named/etc/named.conf
#nano -w /var/named/etc/named.conf
 key "rndc-key" {
       algorithm hmac-md5;
       secret "OOHUU7Jfc1lYydmaF+y+NA==";
  };

  controls {
       inet 127.0.0.1 port 953
               allow { 127.0.0.1; } keys { "rndc-key"; };
  };

Coba hasilnya ...
#rndc reload
server reload successful

boot command pfsense

Buat file *.sh , kemudian simpan di /usr/local/etc/*
i.e : staticarp.sh

#!/bin/sh
/usr/sbin/arp -s 172.16.0.71 00:15:6D:DB:89:42 permanent

note : tested at pfSense_1.2.3