http://www.3g4g.co.uk/Tutorial/ZG/zg_pdp

Packet Data Protocol (PDP) A Packet Data Protocol (PDP) context offers a packet data connection over which the UE and the network can exchange IP packets. Usage of these packet data connections is restricted to specific services. These services can be accessed via so-called access points. Packet Data Protocol Context is one of the most important concepts for the UMTS Packet Data Architecture. The PDP Context has a record of parameters, which consists of all the required information for establishing an end-to-end connection: PDP Type PDP address type QoS profile request (QoS parameters requested by user) QoS profile negotiated (QoS parameters negotiated by network) Authentication type (PAP or CHAP) DNS type (Dynamic DNS or Static DNS) The PDP Context is mainly designed for two purposes for the terminal. Firstly PDP Context is designed to allocate a Packet Data Protocol (PDP) address, either IP version 4 or IP version 6 type of address, to the mobile terminal. Secondly it is used to make a logical connection with QoS profiles, the set of QoS attributes negotiated for and utilized by one PDP context, through the UMTS network. Multiple PDP Context As mobile phones develop, there will be a need to serve parallel applications running on them with simultaneous PS calls. These PS calls can differ in their QoS (Quality of Service) parameters, and/or in the target network (PDN � Packet Data Network) to which they provide connection. Multiple PDP Contexts means that one mobile terminal can have multiple PDP contexts. Each of the Multiple PDP Contexts can at the same time have different QoS profiles. The primary PDP Context is a normal PDP Context with default QoS profile attributes and it is always activated first. For the multiple primary PDP Contexts, each context has different PDP Address and different APN Multiple PDP contexts will have special significance when IMS is introduced and all the services will be PS (IP) based. In an IMS based network the MS can (and will) activate separate PDP contexts for SIP based signaling and for all the sessions of different, eventually parallel services (e.g. parallel VoIP call and PS data call, etc.). A different QoS � which matches the application - will be used for each connection. The data flow (user plane) of a particular PDP context can terminate either in the Mobile Terminal (MT) itself or in the connected Terminal Equipment (TE) as shown in Figure below. The application for which the connection is provided is running either on the MT or on the TE respectively. An example for the first possibility is a video telephony client running on the mobile, for the second possibility a web browser running on the connected notebook.  In IMS based systems it is expected that several embedded applications will run on the MT, requiring multiple PDP contexts. For the TE (e.g. connected PC) one additional PDP context may be also active. Multiple PDP contexts have two sub-categories: multiple primary PDP contexts: they provide connections to different PDNs secondary PDP contexts: they provide connections to the same PDN but with different QoS Multiple Primary PDP Contexts Multiple primary PDP contexts are two or more PDP contexts independent from one another, each of them using one unique PDP address. They give the possibility to have simultaneous connections to different PDNs � e.g. to the internet for one application, while to a private network for another one. Beside the unique PDP address, each PDP context has its own QoS and NSAPI (Network Layer Service Access Point Identifier, see later) assigned. Each PDP context has a separate RAB (Radio Access Bearer) and GTP tunnel to transfer user plane data. The PDP contexts typically terminate in different access points on the network side (although it is allowed that they terminate in the same access point). The terminating access points can be located in the same or in different GGSNs. The example in Figure below shows the user plane path for three primary PDP contexts providing connections to three different PDNs:  Primary PDP contexts can be activated or deactivated independently from one another. QoS of any of the active PDP contexts can be modified with the PDP context modification procedure initiated by the MS or by the network. (See Below for details) Secondary PDP Contexts A secondary PDP context is always associated with a primary PDP context. PDP address (IP address) and access point (AP) is re-used from the primary context. Hence the primary and the associated secondary PDP context provide connection to the same PDN with different guaranteed QoS. One primary PDP context might have multiple secondary contexts assigned. Each PDP context (i.e. the primary and all secondary) has its own RAB and GTP tunnel to transfer user plane data. Also, each context is identified by a unique NSAPI (Network Layer Service Access Point Identifier). The primary PDP context has to be active prior to activating an associated secondary PDP context. Any secondary PDP context can be deactivated while keeping the associated primary context (and eventual other secondary PDP contexts) active. If a primary PDP context is deactivated, this will also deactivate all the assigned secondary PDP contexts. QoS of any active primary or secondary PDP context can be modified with the PDP context modification procedure initiated by the MS or by the network. (See below for details) As the PDP address (IP address) is common for the primary and for (all) the associated secondary PDP contexts, the TFT (Traffic Flow Template) is introduced to route downlink user plane data into the correct GTP tunnel and hence into the correct RAB for each context. The example in Figure below shows the user plane for a primary and two associated secondary PDP contexts:  Combination of multiple primary PDP contexts and secondary PDP contexts is also possible. For example, two primaries with one secondary context for each will result in four active PDP contexts in total. The maximum number of supported PDP contexts is terminal dependent. Traffic Flow Template (TFT) The Traffic Flow Template (TFT) is used by GGSN to discriminate between different user payloads. The TFT incorporates from one to eight packet filters; a unique packet filter identifier identifies each filter. Filtering can be based on one or more of the following filter attributes: Source address (with subnet mask) IPv4 protocol number Destination port range Source port range IPSec Security Parameter Index (SPI) Type of Service (TOS) (IPv4) The TFT is provided by the MS in the Activate Secondary PDP Context Request message, it is stored by the GGSN, and is examined when routing downlink user plane data. The TFT can be modified or deleted with the MS initiated PDP context modification procedure. A TFT may be also assigned to a primary PDP context by means of the MS initiated PDP context modification procedure. A TFT is built up from Packet Filters (minimum 1, maximum 8 of them) to provide flexibility in filtering. The relationship between PDP contexts, TFTs and Packet Filters is illustrated in Figure below: PDP context procedures Primary PDP context activation This procedure is used to establish a logical connection with the Quality of Service (QoS) functionality through the network from the UE to the GGSN. PDP context activation is initiated by the UE and changes the session management state to active, creates the PDP context, receives the IP address and reserves radio resources. After a PDP context activation the UE is able to send IP packets over the air interface. The UE can have up to 11 PDP contexts active concurrently. Secondary PDP context activation A secondary PDP context activation allows the subscriber to establish a second PDP context with the same IP address as the primary PDP context. The two contexts may have different QoS profiles, which makes the feature useful for applications that have different QoS requirements (e.g., IP multimedia). The access point name, though, will be the same for the primary and secondary PDP contexts. PDP context modification The UE, the SGSN or the GGSN initiate this procedure for updating the corresponding PDP context. Additionally, the radio access network is able to request a PDP context modification from the SGSN (e.g., when coverage to the UE has been lost). The procedures modify parameters that were negotiated during an activation procedure for one or several PDP contexts. PDP context deactivation This procedure is used to delete a particular logical connection between the UE and the GGSN. The initiative to deactivate a PDP context can come from the UE, the SGSN, the Home Location Register (HLR) or the GGSN.  Access points Access points can be understood as IP routers that provide the connection between the UE and the selected service. Examples of such services are: Multimedia Messaging Service (MMS); Wireless Application Protocol (WAP); direct Internet access; IP Multimedia Subsystem (IMS). Depending on the operator of the network, more than one of these services might be provided by the same access point. The UE needs to be aware of an Access Point Name (APN) � the address of a GGSN � which gives access to the service-providing entity (e.g., an MMSC, the Internet or the P-CSCF). One GGSN may provide different services that can be accessed by different APNs. When establishing a primary PDP context with an APN the UE receives an IP address or � in the case of IPv6 � an IPv6 prefix that it has to use when communicating over that PDP context. This means that when a UE has established several connections to different APNs the UE will have different IP addresses for each of the provided services. REFERENCES [1] The IMS: IP Multimedia Concepts and Services, Second Edition Miikka Poikselk�, Georg Mayer, Hisham Khartabil and Aki Niemi  [2] Multiple PDP Contexts in UMTS - ESG Group, Qualcomm  [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description"  [4] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols"  [5] What are Secondary PDP Contexts Good For? - Martins Mobile Technology Blog  [6] Using Traffic Flow Templates (TFTs) on BGAN - Inmarsat

Ubuntu apt-get 저장소 일괄 바꾸기

sudo sed -i -re 's/([a-z]{2}\.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list

/* 기존 저장소 덤프 */
svnadmin dump /svn/repos/siwon > siwon.dump
svnadmin dump /svn/repos/yeonwoo > yeonwoo.dump

/* 새 저장소 생성 */
svnadmin create /svn/repos/newrepos

/* 새 저장소 안에 복구할 디렉토리 각각 생성 */
svn mkdir svn://server/repos/newrepos/siwon
svn mkdir svn://server/repos/newrepos/yeonwoo

/* 복구 */
svnadmin load /svn/repos/newrepos --parent-dir siwon < siwon.dump
svnadmin load /svn/repos/newrepos --parent-dir yeonwoo < yeonwoo.dump

최종적으로 아래의 경로에 생성이 된다.

/svn/repos/newrepos/siwon
/svn/repos/newrepos/yeonwoo

http://blog.naver.com/e1seung/110172460781

윈도우 시작->실행->cmd 입력후 다음의 명령어를 입력할 것 

netsh interface set interface "무선 네트워크 연결" enable

netsh interface set interface "무선 네트워크 연결" disable

netsh wlan connect ssid=YOURSSID name=PROFILENAME interface="무선 네트워크 연결"

netsh wlan disconnect

[번역] PHP 코드를 최적화하는 40가지 팁

Windows 7 계산기는 XP용 계산기에 비해 많은 기능이 추가되었다.

직업상 Hex데이타를 처리할 일이 많은데, [프로그래머용]을 사용한다.

하지만 [프로그래머용]에서는 소수점 처리가 안된다.

[공학용]으로 전환해야 한다.

Windows XP용 계산기에서는 이 두가지가 메뉴를 클릭하지 않고도 가능했었다.

그래서 결국 XP용 계산기로 돌아가기로 했다.

첨부를 다운받아, [C:\WINDOWS\system32] 폴더에 복사해 넣을 것

calc.zip

WinCVS 실행하면 한번은 죽어버리고, 다시 실행하면 위와 같은 에러창이 뜬다. 

[아니요]를 클릭하면 진행이 되긴하는데, 매번 이러기 귀찮아서 찾아보니 방법이 있었다.

결론은 cygwin bin디렉토리에서 tcl84.dll을 지웠다.

아래 WinCVS사이트의 코멘트 참조

I have got Cygwin 1.5.7 or later installed and WinCvs hangs or crashes right on startup. What should I do?

This is a known issue that is caused by the TCL DLL distributed with Cygwin which also affects a few other Windows applications which attempt to load the TCL interpreter DLL, e.g. WinGaim. Apparently the Cygwin flavour of tcl84.dll depends on the Cygwin environment being loaded as well which is not the case for WinCvs and shouldn't have to be. This causes the host application (in this case WinCvs) to crash or hang while trying to load the DLL. Other than not even trying to load the DLL there isn't really anything sensible that could be done about this from WinCvs' point of view (see below).

The workaround is to make sure that WinCvs either finds a different tcl84.dll first or none at all. This could be accomplished by any of the following:

• Rearrange your PATH environment variable so a folder that contains a non-Cygwin tcl84.dll (recommended is the one included in the standard Pythondistribution) comes before the Cygwin one.
• Uninstall the Tcltk package from your Cygwin installation.
• Rename or delete the tcl84.dll in your Cygwin bin directory.
• Remove the Cygwin bin directory from your PATH altogether.

Note that this problem only applies when you have put your Cygwin bin directory on your PATH as that is where WinCvs will by default search for a TCL DLL to use. This could not really be recommended even if this particular issue did not exist (even though it seems that the Cygwin people are actually recommending to do so...). Cygwin effectively creates its own sub-Operating System environment so "letting it out in the open to mix and match" with the Windows-native applications could lead to unpredictable results.

Recent releases of WinCvs have implemented a partial remedy: When a hang or crash occurred while loading DLLs they will detect this and on next startup will offer the option to not load any external DLLs. This will allow users to start WinCvs without crash or hang and then simply go to the preferences to specify a different DLL (on the WinCvs tab of Admin|Preferences.

You can read more about this issue in this thread from the Cygwin mailing list and this report in the CVSGUI bug tracker. Furthermore, the archives of theCVSGUI mailing list are full of posts on the issue as well.

http://cvsgui.sourceforge.net/newfaq.htm#cygwinTcl

# ps -ef | grep httpd | awk '{print $2}' | xargs kill -9

# killall httpd

http://www.linux.co.kr/home/lecture/index.php?cateNo=1&secNo=27&theNo=&leccode=10801

taskkill /f /im xxx.exe

taskkill /f /pid xxx

TASKKILL [/S 시스템 [/U 사용자 이름 [/P [암호]]]]
         { [/FI 필터] [/PID 프로세스 id | /IM 이미지 이름] } [/T] [/F]

설명:
    이 도구는 프로세스 ID(PID) 또는 이미지 이름으로 작업을 종료하는 데
    사용합니다.

매개 변수 목록:
    /S    시스템           연결할 원격 시스템을 지정합니다.

    /U    [도메인\]사용자  명령을 실행해야 하는 사용자 컨텍스트를
                           지정합니다.

    /P    [암호]           해당 사용자 컨텍스트의 암호를 지정합니다.
                           생략한 경우에는 물어봅니다.

    /FI   필터             작업 집합을 선택하는 필터를 적용합니다.
                           "*"를 사용할 수 있습니다. 예: imagename eq acme*

    /PID  프로세스_ID      종료할 프로세스의 PID를 지정합니다.
                           TaskList를 사용하여 PID를 얻을 수 있습니다.

    /IM   이미지 이름      종료할 프로세스의 이미지 이름을
                           지정합니다. 와일드카드 문자 '*'를 사용하여
                           모든 작업 또는 이미지 이름을 지정할 수 있습니다.

    /T                     지정된 프로세스와 그 프로세스로부터 시작된
                           모든 자식 프로세스를 종료합니다.

    /F                     프로세스를 강제로 종료하도록 지정합니다.

    /?                     이 도움말 메시지를 표시합니다.

필터:
    필터 이름     유효한 연산자             유효한 값
    -----------   ---------------           -------------------------
    STATUS        eq, ne                    RUNNING |
                                            NOT RESPONDING | UNKNOWN
    IMAGENAME     eq, ne                    이미지 이름
    PID           eq, ne, gt, lt, ge, le    PID 값
    SESSION       eq, ne, gt, lt, ge, le    세션 번호.
    CPUTIME       eq, ne, gt, lt, ge, le    CPU 시간 형식
                                            hh:mm:ss
                                            hh - 시간,
                                            mm - 분, ss - 초
    MEMUSAGE      eq, ne, gt, lt, ge, le    메모리 사용(KB)
    USERNAME      eq, ne                    사용자 이름([domain\]user
                                            형식)
    MODULES       eq, ne                    DLL 이름
    SERVICES      eq, ne                    서비스 이름
    WINDOWTITLE   eq, ne                    창 제목

    참고
    ----
    1) /IM 스위치에 대한 와일드카드 문자 '*'는 필터가 적용될 때만
    사용할 수 있습니다.
    2) 원격 프로세스는 항상 강제적으로(/F) 종료될 수 있습니다.
    3) 원격 컴퓨터가 지정되면 "WINDOWTITLE"  및 "STATUS" 필터는 
       지원되지 않습니다.

예:
    TASKKILL /IM notepad.exe
    TASKKILL /PID 1230 /PID 1241 /PID 1253 /T
    TASKKILL /F /IM cmd.exe /T 
    TASKKILL /F /FI "PID ge 1000" /FI "WINDOWTITLE ne untitle*"
    TASKKILL /F /FI "USERNAME eq NT AUTHORITY\SYSTEM" /IM notepad.exe
    TASKKILL /S 시스템 /U domain\username /FI "USERNAME ne NT*" /IM *
    TASKKILL /S 시스템 /U 사용자 이름 /P 암호 /FI "IMAGENAME eq note*"