원글 : http://bongjaemoon.wordpress.com/2012/05/25/ffmpeg-x264-compile-for-using-with-android-ndk-on-mac-osx/

1. Toolchain for compile (This NDK version is r8)
a. Android’s NDK allows we to create toolchain installation using “make-standalone-toolchain.sh” script.
b. Execute like below.
$> $NDK/build/tools/make-standalone-toolchain.sh –platform=android-14 –install-dir=/work/my-android-toolchain
c. You can use directly with PATH, CC setting.
export PATH=/work/my-android-toolchain/bin:$PATH
export CC=arm-linux-androideabi-gcc
d. Done

2. Compile & Build x264 project for FFMpeg library.
a. Download x264 project (http://www.videolan.org/developers/x264.html)
b. Configuration for arm compile. (prefix option is very important for FFMpeg compiling.)
$> ./configure –host=arm-linux \
–cross-prefix=arm-linux-androideabi- \
–enable-shared \
–enable-static \
–prefix=/work/my-android-toolchain/sysroot/usr
c. make / install
$> make
$> make install
d. Done. You can find the library & include files in –prefix option’s directory.

3. Compile & Build FFMpeg project.
a. Download FFMpeg source code from http://ffmpeg.org/download.html (This case is FFmpeg 0.10.3 “Freedom” version)
b. Configuration for arm compile.
$> ./configure –enable-shared \
–enable-libx264 \
–cross-prefix=arm-linux-androideabi- \
–enable-cross-compile \
–target-os=linux \
–arch=arm \
–enable-gpl \
–prefix=/work/my-android-toolchain/sysroot/usr
c. Configuration for detailed module selection.
$> ./configure –prefix=../ffmpeg_build \
–enable-gpl \
–enable-shared \
–disable-doc \
–disable-ffmpeg \
–disable-ffplay \
–disable-ffprobe \
–disable-ffserver \
–disable-avdevice \
–disable-debug \
–disable-network \
–disable-protocols \
–disable-devices \
–disable-encoders \
–disable-decoders \
–disable-muxers \
–disable-demuxers \
–disable-parsers \
–disable-bsfs \
–disable-filters \
–enable-encoder=h264 \
–enable-libx264 \
–extra-cflags=-U__STRICT_ANSI__ \
–target-os=linux \
–extra-cflags=”-fno-short-enums” \
–extra-ldflags=”-mandroid -lm” \
–enable-cross-compile \
–cross-prefix=arm-linux-androideabi- \
–arch=arm
d. Make
$> make

e. Make install

$> make install

f. Done. You can see the library and header in ../ffmepg_build directory (in the prefix option)

patch-edid.rb

Force RGB mode in Mac OS X to fix the picture quality of an external monitor

I recently bought a MacBook Pro (with ‘Retina’ screen), but when I hooked it up to my Dell U2410 monitor via HDMI cable I was shocked by the poor picture quality. The contrast was all wrong and text was misshapen. No amount of calibration in the monitor or software would fix it.

Short answer: OS X thinks my monitor is a TV, and is using the YCbCr colour space rather than RGB. I had to override an EDID setting to force the RGB colour space, and it is now working correctly.

Long answer: I haven’t owned a Mac for a while and had forgotten how difficult much of the “Apple community” can be when it comes to anything that can’t be adjusted in System Preferences. Googling for problems with external monitors on MacBooks found dozens of threads on official and unofficial Apple forums, all full of people with the same problem. The most common response was to blame the monitor, despite assurances from the stricken users that the monitor worked beautifully in Linux and Windows, even on the same machine under Boot Camp.

“You just haven’t calibrated it!”, “You are just too used to Retina now!”, “You just need to buy a Thunderbolt display!” Apple people also like to solve problems by throwing more money at it. (I realise that owning a Mac makes me an Apple person, too. Hypocritical self-loather?)

My lucky break was reading that the current colour space was “YCbCr” when I was browsing the monitor’s settings menu. I was sure that it was using RGB when hooked up to my PC, so I started searching instead for forcing RGB mode in OS X. It didn’t appear to be available out-of-the-box, but I have had some experience in overriding EDID settings for similar purposes so I searched instead for that.

I found this thread on the EmbDev.net forums. Mr Schwarz, thanks very much. Your thread and script was incredibly helpful and informative. It was written to fix problems connecting an external monitor via DisplayPort, but it fixed my HDMI issue just the same. I’ve summarised the required steps below.

My last word is to wonder what Apple is playing at. It seems that this problem has been reported by a lot of people for a long time, and I expect it would require a fairly simple software update. Do they just not care about those using third-party components, or are they actively attempting to force people on to Thunderbolt displays?

How to force RGB in Mac OS X

1. Download the patch-edid.rb script from the forums thread above and put it in your home directory.
2. Connect only the external monitor(s) in question (I closed my MacBook lid, for example). The script will make override files for any connected monitor.
3. Type “ruby patch-edid.rb” in Terminal.
4. A new folder will be created in your home directory. Move it into the “/System/Library/Displays/Overrides” folder. If Finder tells you that you are overwriting an existing folder, consider backing it up first.
5. Restart your computer, enjoy your monitor.

To undo the changes, either delete the folder you had copied to the Overrides folder (if it didn’t already exist) or replace it with the folder you had backed up.

Updates

If you’re having trouble with any of these steps, please have a look through the comments below (and note that there are multiple pages). Many questions have been answered with helpful tips from others.

Update, 27 Oct 2013: If you’ve applied this fix before, the OS X Mavericks update will overwrite it. I’ve successfully re-applied the fix by following exactly the same steps, and other commenters below have done so, too.

Update, 13 Nov 2013: Andrew comments below that he has modified the script to add some useful new features, and provides a link to his GitHub for those wishing to use it instead.

1) GRANT 명령을 통한 추가 (한방에 추가(명령 한번으로 사용자를 추가))

   GRANT ALL PRIVILEGES ON 접근 허용 할 DB 이름.* TO 'new_user_id'@'%' IDENTIFIED BY 'new_user_password' WITH GRANT OPTION;

   모든 테이블에 접근 하기위해서는  접근 허용 할 DB 이름.*  ==> *.*

   'new_user_id'@'%' 에서 '%'의 의미는 신규 계정이 접속할 위치의 제한을 두지 않겠다는 의미.

   예) 'new_user_id'@'localhost' localhost 로 접속을 하였을 경우만 허용

         'new_user_id'@'127.0.0.1' 127.0.0.1 로 접속 하였을 경우만 허용

         'new_user_id'@'192.168.0.100' '192.168.0.100' 에서만 접속 허용.

[출처] MySQL 사용자 추가 및 삭제|작성자 콩이아부지

pear install log4php/Apache_log4php

[원문]
http://www.yongbok.net/blog/how-to-install-mongodb-on-centos/

 

How to install MongoDB on CentOS

1. keytool 필요

java/jre/bin 폴더에 있음

저같은 경우에는 C:\Program Files (x86)\Java\jre6\bin

2. openssl 설치

http://downloads.sourceforge.net/gnuwin32/openssl-0.9.8h-1-setup.exe 설치

3. Path 설정

윈도우 7 기준 > 제어판\시스템 및 보안\시스템 > 고급 시스템 설정 > 환경 변수 > 시스템변수 > Path 수정

저 같은 경우 맨 뒤에 C:\Program Files (x86)\Java\jre6\bin\;C:\Program Files (x86)\Git\bin\ 추가

앞 경로는 keytool, 뒤는 openssl <자신의 pc의 경로 확인> 

4. cmd 실행

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64
붉은 글씨 부분에 자신의 경로로 수정

저 같은 경우 C:\Users\Administrator\.android

debug.keystore 파일의 경로를 입력 해줌

그래서

keytool -exportcert -alias androiddebugkey -keystore C:\Users\Administrator\.android\debug.keystore| openssl sha1 -binary | openssl base64 입력 

 

여기서 만약 keystore 암호를 묻지 않고 그냥 해시 코드가 출력 된다면 잘못된 해시 코드이니 낚이지 않도록 주의 !! 

암호는 android 라고 입력

이 후, 출력되는 값이 진짜 해시 코드 이다.

대부분 많이 하는 실수가 대충 입력해서 나온 잘못된 해시코드로 페이스북 설정에 등록하는 경우가 많은데 이를 주의 해야 함...

vi /etc/selinux/config

SELINUX=disabled

yum install mod_ssl 하여 mod_ssl을 인스톨한다.

openssl 도 인스톨되어 있는지 확인하고 없으면 인스톨한다.

공개키, 개인키, 싸인을 생성한다.

# Generate private key 

openssl genrsa -out ca.key 1024

# Generate CSR 
openssl req -new -key ca.key -out ca.csr

# Generate Self Signed Key
openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt


생성된 키파일들을 지정된 위치에 옮긴다.
# Move the files to the correct locations
mv ca.crt /etc/pki/tls/certs
mv ca.key /etc/pki/tls/private/ca.key
mv ca.csr /etc/pki/tls/private/ca.csr

vi +/SSLCertificateFile /etc/httpd/conf.d/ssl.conf 한 후에,

SSLCertificateFile 항목과 SSLCertificateKeyFile항목을 아래와 같이 설정한다.

SSLCertificateKeyFile /etc/pki/tls/private/ca.key


SSLCertificateFile /etc/pki/tls/certs/ca.crt

httpd 서비스를 새로 시작한다.

/etc/init.d/httpd restart