mysql 4.x를 RPM으로..
libiconv 도 prefix = "/usr" 로 설정하고 설치하고...
apache 1.3. x도 RPM으로 되었다면..
/usr/local/freetds 에 MSSQL 라이브러리를 설치하고 난뒤 사용한다.
Gd 라이브러리 포함(단 zlib를 RPM으로 설치되어 있어야함 )

./configure --with-apxs=/usr/sbin/apxs --with-imap=/usr --with-mysql=/usr --with-iconv=/usr --with-language=korean --with-charset=euc_kr --enable-track-vars --enable-module=so  --disable-cgi --with-config-file-path=/etc/httpd/conf --enable-versioning --with-kerberos --with-imap-ssl=/usr   --with-mssql=/usr/local/freetds --enable-msdblib --with-gd  --with-zlib-dir=/usr
728x90
Kernel Compile

  배경지식

기본적으로 커널 소스의 디렉토리는 /usr/src/linux 이다.
커널 컴파일 방법에는 3가지가 있다
make config -> 옵션을 잘못 선택하면 처음부터 다시해야하는 단점이 있다.
make menuconfig -> 가장 추천하는 방법(단, ncurses가 있어야 한다.)
make xconfig -> X에서 볼수 있다.( 화려하다. 그냥 구경한번 해보길...)
시스템 사양을 잘 알아야 한다.(이더넷 카드, 사운드 카드, CPU가 몇개(?)인지등...)
어떠한 환경에서 사용할건지 결정하여야 한다.(커널의 최적화를 위해...)
Kernel Compile Option
꼭 주의깊게 살펴볼것!!(나에게 어떤 옵션이 필요한지 볼것)
제 2회 리눅스 공동체 세미나 자료에서 추출(이규호님께 감사)
커널 2.4 Intro중 커널옵션설정
일반적인 데스크탑 PC사양에서 필요로하는 커널옵션들을 설명하고있다.
  따라하기

커널 소스를 받는다.( http://www.kr.kernel.org/pub/linux/kernel/)
소스를 /usr/src 방으로 옮긴다.(예: mv linux-2.2.12.tar.gz /usr/src )
전에 있던 커널소스 /usr/src/linux 디렉은 다른이름으로 바꾸던지 지워라.(예: mv linux linux-2.2.11)
만약 linux라는 이름으로 심벌릭 링크되어있다면 링크만 해제하라.(예: rm linux)
커널 소스를 푼다.(예: tar xvvzf 커널버전.tar.gz 또는 tar xvvIf 커널버전.tar.bz2)
linux라는 디렉토리가 생겼을 것이다. 그 디렉으로 들어간다.( cd linux )
# make menuconfig ( 현재 위치 /usr/src/linux )
커널 컴파일 옵션을 보고 시스템에 맞는걸 선택한다.(중요하다!)
# make clean (예전 오브젝트 파일 제거)
# make dep (의존성을 검사)
# make bzImage (커널 이미지를 압축생성한다.)
# mv arch/i386/boot/bzImage /boot/vmlinuz-커널버전 (예: mv arch/i386/boot/bzImage /boot/vmlinuz-2.2.12)
# mv System.map /boot/System.map-커널버전 (예: mv System.map /boot/System.map-2.2.12)
# vi /etc/lilo.conf ( 리로를 편집한다 )
     boot=/dev/hda
     map=/boot/map
     install=/boot/boot.b
     prompt
     timeout=50
     image=/boot/vmlinuz-2.2.12 -> 새로운 커널이미지를 linux라는
     label=linux              ?   레이블로 한다.
     root=/dev/hda1
     read-only

     image=/boot/vmlinuz-2.2.11 -> 혹시나 모를 커널 패닉에 대비하여          
     label=old                     예전 커널을 old란 레이블로 해놓는다.
     root=/dev/hda1                (예전 버전이 2.2.11일때)
     read-only
# /sbin/lilo ( lilo.conf의 내용을 인식시켜 주기위해 )
여기까지 커널 컴파일은 과정은 끝.
  모듈 인스톨 하기

커널 옵션에서 모듈(M)으로 선택한것을 컴파일 하기위해
# cd /usr/src/linux
# make modules
# make modules_install
위와같이 하면 '/lib/modules/커널버전' 디렉에 모듈들이 위치한다.


Kernel Patch


패치란 매번 커널이 바뀔때 마다 13MB가 넘는 커널 소스를 다시 받을 필요없이 바뀐 차이점만 담고있는 작은 용량의 파일로 커널을 업하는걸 말한다.
장점 : 적은용량으로 패치파일로 커널을 금방 업 할 수 있다.
단점 : 중간의 한 단계를 건너 뛸 수 없다. 예를들어 현재 커널 버전이 2.2.10 인데 바로 2.2.12로 패치 할 순없다.(꼭 2.2.11을 패치하고 나야 된다)
  따라하기

패치 파일을 다운받아 bzip2이든 gzip으로 압축되어있던지 간에 압축을 푼다.
압축을 푼후 /usr/src/linux 방으로 옮긴다.
# patch -p1 < 패치파일?
에러 없이 넘어가면 다음은 커널 컴파일 과정과 같다.
만약 압축을 풀지않고 패치하려면 gzip 또는 bzip2에 따라 다음과 같이한다.
# gzip -cd 패치파일.gz | patch -p1(물론 패치파일의 위치는 /usr/src/linux)
# bzip2 -cd 패치파일.bz2 | patch -p1
728x90
S(Source)RPM을 받았을 때 사용법

ncftp-3.1.3-6.src.rpm
을 받았다고 치면

# rpm -Uvh ncftp-3.1.3-6.src.rpm
# cd /usr/src/hancom/SPECS
# rpmbuild -ba ncftp.spec

빌드가 끝나면

# cd /usr/src/hancom/RPMS/i386
에 가면
ncftp-3.1.3-6.i386.rpm
이 만들어져 있을 것이다.

# rpm -Uvh ncftp-3.1.3-6.i386.rpm
하면 설치가 끝난다.

지금까지 소스RPM을 받아서 자신 컴에서 빌드하여 설치하는 것을 알아보았다.

그럼 해피 리눅싱~~

발췌 : 한컴 리눅스 >OS Tip & Tech > [팁] SRPM을 RPM으로 만들어서 설치하는 법(멀티)
http://kr.hancom.com/board/bbsView.php?zone=os&from=3&mode=0&sort=0&s_order=0&page=0&info_no=14&zone=os&key=title&value=srpm&cata=&goods=&num=301175
728x90

48-Bit LBA Support for ATAPI Disk Drives in Windows 2000

The information in this article applies to:
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
This article was previously published under Q305098

SYMPTOMS


Windows 2000 Service Pack 2 (SP2) and earlier versions of Windows 2000 do not support 48-bit Logical Block Addressing (LBA) as defined in the ATA/ATAPI 6.0 specification.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack




The English-language version of this fix should have the following file attributes or later:


Date Time Version Size File name
--------------------------------------------------------
10/19/2001 01:42 PM 5.0.2195.4529 86,768 Atapi.sys
04/19/2002 05:43 PM 214,938 Update.inf



The following conditions are necessary for the correct functioning of 48-bit LBA ATAPI support:

  • A computer with a 48-bit LBA-compatible Basic Input/Output System (BIOS) installed.
  • A computer with a hard disk that has a capacity of greater than 137 gigabytes (GB).
  • You must enable the support in the Windows registry by adding or changing the EnableBigLba registry value to 1 in the following registry subkey:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesatapiParameters



To enable 48-bit LBA large-disk support in the registry:

  1. Start Registry Editor (Regedt32.exe).
  2. Locate and then click the following key in the registry:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesAtapiParameters

  3. On the Edit menu, click Add Value, and then add the following registry value:


    Value name: EnableBigLba

    Data type: REG_DWORD

    Value data: 0x1

  4. Quit Registry Editor.
NOTE: If you enable 48-bit LBA ATAPI support by editing the preceding registry key, but your system does not meet the minimum requirements, you may observe the following behaviors:

  • Operating systems that do not have 48-bit LBA support enabled by default (such as Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), or Windows 2000) that are installed on a partition that spans beyond the 28-bit LBA boundary (137GB) will experience data corruption or data loss.
  • The installation of operating systems that do not have 48-bit LBA support enabled by default (such as Windows 98, Windows Me, or Windows 2000) on a partition that is beyond the 28-bit LBA boundary (137 GB) is unsuccessful and leaves behind a temporary installation folder.
  • If you install hotfixes that enable 48-bit LBA before you install Windows 2000 Service Pack 3 (SP3), the appropriate registry key will be automatically created during the installation of SP3 to preserve the data integrity of the hard disk.
  • After you enable 48-bit LBA support by adding the appropriate registry key, data corruption may occur if you remove the registry key or if you remove (uninstall) SP3 for Windows 2000.
  • If you install a copy of Windows 2000 that includes SP3 (SP3 integrated) on a large hard disk that has already been preformatted by using a 48-bit LBA-enabled operating system, the ATAPI subsystem may report hard-disk space greater than that which is addressable without the 48-bit LBA support (larger than approximately 137 GB) during the text-mode portion of Setup. In this case, the hard disk's partition table information has already been created. To fix the incorrect disk information, delete the partition by using either a disk partitioning utility or by deleting and then re-creating the partition during the text-mode portion of Setup. After you create the new partition, quit Setup by pressing F3, and then restart the Windows installation process. The ATAPI subsystem now correctly shows approximately 137 GB of hard disk space.
  • The EnableBigLba registry value is disabled:


    If you have a 48-bit compatible BIOS that can support a hard disk that has a capacity of more than 137 GB, only the first 137 GB of the hard disk is addressable. The remainder of the hard disk is not used.
  • The operating system must be installed on the first partition that is smaller or equal to 137 GB when the EnableBigLba registry value is enabled but when you do not have a 48-bit LBA compatible BIOS.


    If you enable the 48-bit LBA ATAPI support by editing the registry setting, but you lack both a 48-bit LBA compatible BIOS and a hard disk that has a capacity of more than 137 GB, the hard disk continues to function as a standard hard disk with an addressable limit of 137 GB.
  • The operating system must be installed on the first partition that is less than or equal to 137 GB and the rest of the hard disk divided into one or more remaining partitions when the EnableBigLba registry value is enabled on a computer without a 48-bit LBA compatible BIOS that has a hard disk with a capacity of more than 137 GB.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.Important Although support for 48-bit LBA is included in Windows 2000 Service Pack 3 (SP3) and later, it is still necessary to create the registry change that is described in the "Resolution" section of this article.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below
to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product


For additional information about how to install multiple hotfixes with only one reboot, click the following article number to view the article in the Microsoft Knowledge Base:

296861
How to Install Multiple Windows Updates or Hotfixes with Only One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below
to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Last Reviewed:7/4/2003
Keywords:kbbug kbfix kbOSWin2000fix kbWin2000sp3fix KB305098
728x90

키보드 Windows 키의 설정을 해제하는 방법


본 문서의 정보는 다음의 제품에 적용됩니다.
  • Microsoft Windows NT Workstation 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Workstation 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Workstation 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Workstation 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Workstation 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3 및 4.0 SP4
  • Microsoft Windows NT Server, Enterprise Edition 4.0 및 4.0 SP4
  • Microsoft Windows NT Server, Enterprise Edition 4.0 및 4.0 SP4
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
이 문서는 이전에 다음 ID로 출판되었음: KR216893

요약



요즘의 새로운 많은 컴퓨터 키보드에서 사용할 수 있는 Windows 키의 설정을 해제할 수 있습니다. 이 키는 대개 시작 단추나 다른 Windows NT 기능으로의 바로 가기 액세스를 제공합니다.

추가 정보





Windows 키의 설정을 해제하려면 아래 단계를 수행합니다.

  1. 시작을 누르고 실행을 누른 다음
    regedt32를 입력하고 확인을 누릅니다.
  2. 메뉴에서 HKEY_LOCAL_ MACHINE(로컬 시스템)을 누릅니다.
  3. SystemCurrentControlSetControl 폴더를 누른 다음 Keyboard Layout 폴더를 두 번 누릅니다.
  4. 편집 메뉴에서 값 추가를 누르고
    Scancode Map을 입력하고 데이터 형식으로 REG_BINARY를 누른 다음 확인을 누릅니다.
  5. 데이터 필드에
    00000000000000000300000000005BE000005CE000000000을 입력한 다음 확인을 누릅니다.

  6. 레지스트리 편집기를 닫고 컴퓨터를 다시 시작합니다.

728x90

How to Change Terminal Server's Listening Port



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition

  • Microsoft Windows 2000 Server

  • Microsoft Windows 2000 Advanced Server

  • Microsoft Windows 2000 Professional




This article was previously published under Q187623


IMPORTANT: This article contains information about modifying
the registry. Before you modify the registry, make sure to back it up and make
sure that you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge Base:



256986
Description of the Microsoft Windows Registry



SUMMARY


By default Terminal Server and Windows 2000 Terminal Services uses TCP port
3389 for client connections. Microsoft does not recommend that this value be
changed. However, if it becomes necessary to change this port, follow these
instructions.



MORE INFORMATION


WARNING: If you use Registry Editor incorrectly, you may
cause serious problems that may require you to reinstall your operating
system. Microsoft cannot guarantee that you can solve problems that result
from using Registry Editor incorrectly. Use Registry Editor at your own risk.



To change the default port for all new connections created on the Terminal
Server:



  1. Run Regedt32 and go to this key:

    HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal
    ServerWinStationsRDP-Tcp


    NOTE: The above registry key is one path; it has been
    wrapped for readability.




  2. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
    (3389). Modify the port number in Hex and save the new value.



    To change the port for a specific connection on the Terminal Server:

    • Run Regedt32 and go to this key:

      HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal
      ServerWinStationsconnection


      NOTE: The above registry key is one path; it has been
      wrapped for readability.




  3. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
    (3389). Modify the port number in Hex and save the new value.



    NOTE: Because the use of alternate ports has not been fully
    implemented for Terminal Server 4.0, support will be provided as "reasonable
    effort" only, and Microsoft may require you to set the port back to 3389, if
    any problems occur.


To Alter the Port on the Client Side



  1. Open Client Connection Manager.

  2. On the File menu, click New Connection,
    and then create the new connection. After running the wizard, you should
    have a new connection listed there.

  3. Making sure that the new connection is highlighted, on the File
    menu, click Export. Save it as name.cns.

  4. Edit the .cns file using Notepad changing "Server Port=3389" to "Server
    Port=xxxx" where xxxx is the new port that you
    specified on Terminal Server.

  5. Now import the file back into Client Connection Manager. You may be
    prompted to overwrite the current one, if it has the same name. Go ahead and
    overwrite it. You now have a client that has the correct port settings to
    match your change Terminal Server settings.


NOTE: The Terminal Server ActiveX client listens on TCP
port 3389 and this cannot be changed. The Remote Desktop Protocol (RDP) client
that is available in Microsoft Windows XP and Windows .NET (version 5.1 and
later) has this ability.

NOTE: You must restart the Terminal Server before the new
listening port becomes active, or recreate the RDP listener via Terminal
Services configuration.

728x90

How to Change the Listening Port in the Windows Terminal
Server Web Client



The information in this article applies to:

  • Microsoft Windows Server 2003, Datacenter Edition

  • Microsoft Windows Server 2003, Enterprise Edition

  • Microsoft Windows Server 2003, Standard Edition

  • Microsoft Windows Server 2003, Web Edition

  • Microsoft Windows XP Professional SP1




This article was previously published under Q326945


SUMMARY


By default, Windows Terminal Server uses TCP port 3389 for client
connections. As a security option, you may want to change this port.



This article describes how to change the default listening port in the
Terminal Server Web Client.



MORE INFORMATION


To change the Terminal Server listening port in the Windows XP Service Pack
(SP) 1 (or later) and Windows Server 2003 clients, follow these steps:



  1. Locate the Default.htm file in the %system root%WebTsWeb folder.

  2. Open Default.htm in Notepad or in another text editor.

  3. Locate the entries that start with "MsRdpClient.AdvancedSettings2".

  4. Add the following line after these entries

    MsRdpClient.AdvancedSettings2.RDPPort = xxxx


    where xxxx is the new port.



To make sure that you can connect with the new setting, append the port
number to that of the published URL (that is, www.xxx.xxx.xxx:PortNumber).



NOTE: Before SP1 the Windows XP client used the Connect.asp
file, not Default.htm, for these settings. You can make the change described
in step 4 to Connect.asp, but Microsoft recommends that instead you upgrade
the Terminal Services Web client as described in the following Microsoft
Knowledge Base article:




327521
MS02-046: Buffer Overrun in TSAC ActiveX Control Might Allow Code
Execution


For additional information about how to change the default listening port
in Terminal Server, click the article number below to view the article in the
Microsoft Knowledge Base:




187623
How to Change Terminal Server's Listening Port


728x90
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSFTPSVCParametersEnablePortAttack = 1


If its on your own machine, and u are in dos u can supposedly use 'rd \\.\D:
some\path\com1'
of course change the path to where u did it on your harddrive, but use all those
extra backlashes.
728x90

+ Recent posts

728x90