'2009/02'에 해당되는 글 8건

  1. 2009.02.24 세상이 너무 짜다.
  2. 2009.02.19 Maven
  3. 2009.02.18 이런저런 URL
  4. 2009.02.16 MindTouch (1)
  5. 2009.02.16 Subversion 설치
  6. 2009.02.12 10th Java Conference
  7. 2009.02.11 Ubuntu에서 Synergy 사용하기
  8. 2009.02.10 우분투(7.04)에서 자바 한글 폰트 설정하기

세상이 너무 짜다.

|
솔직히 나는 무교(無敎) 이다. 뭐 나름 '친불교성 무교'라고 명명하고는 있기는 하다.
내가 괜찮다고 생각하는 종교의 순위는 천주교 > 불교 > 기독교.. 뭐 친화성에 대해선 개인적인 것이니까.

오늘 "곪은 게 터진 교회, 이 지경까지 왔구나" 을 읽고, 이래저래 생각이 들어 짧게 적는다.

물론 성경에 기반하여, 진실된 신앙도가 없다는 것은 아니다.
내 친구중에도 8년여를 다니던 회사를 그만두고 신학교에 진학하여 목사의 꿈을 꾸고 있는 친구도 있으니 진실된 신앙도가 없다고 한다면, 그릇 그 친구 앞에서 욕을 하는 것과 진배가 없겠지만, 내심 진실로 성경의 말씀을 행하는 자는 몇명이나 될까 하는 의구심이 된다.

개인적으로 교회는 현재 막강한 이익단체가 아닌듯 싶다.
정치에서 학연, 지연 등등을 논하지만 교회는 종교에 기반한 이익단체의 또 다른 형태가 아닌가 싶다. 뭐뭐 교회가 멀리 가서 교인들 피납되고, 덤탱이는 국민이 쓰고... 에휴 내 세금.. ㅡㅡ; 국가와 사회보다 먼저한 교회... 충분한 이익단체인듯...

교회를 가서야 친구를 만나고, 지인과 이야기 할 수 있는 현대 사회의 차가움이 교회의 양적인 팽창에 지대한 기여를 하지 않았나 싶다.  결국 사람사는 사회가 차가워졌다는 이야기로 귀결... 어디가서 내 이야기를 들어주는 좋은 사람을 만날꼬....

교회의 사회 순화적인 면을 부정하지는 못한다. 모든 종교가 다 그렇듯 사회의 어려운 면에 대해서 과감한 조정과 노력, 헌신으로 봉사하였으니까.
내가 살아가는 현실에 있어서의 소금과 같이 꼭 필요한 기능을 수행하는... 정말 중요한...

그런데.... 요즈음 나는 "왜 세상이 짜게 느껴질까" 하는 의구심이 든다.

Trackback 0 And Comment 0

Maven

|
Mavne 설치

1. Maven을 설치한다.
$>sudo apt-get install maven2

꾸러미 목록을 읽는 중입니다... 완료
의존성 트리를 만드는 중입니다      
상태 정보를 읽는 중입니다... 완료
다음 꾸러미를 더 설치할 것입니다:
  ant ant-gcj ant-optional ant-optional-gcj antlr libantlr-java libantlr-java-gcj libbcel-java libclassworlds-java
  libcommons-cli-java libcommons-collections-java libcommons-httpclient-java libcommons-logging-java libcommons-net-java
  libcommons-openpgp-java libdoxia-java libganymed-ssh2-java libjdom0-java libjsch-java libjtidy-java liblogkit-java
  liboro-java libplexus-classworlds-java libplexus-component-api-java libplexus-container-default-java
  libplexus-interactivity-api-java libplexus-utils-java libplexus-velocity-java libregexp-java libservlet2.3-java
  libslide-webdavclient-java libwagon-java libwerken.xpath-java libxalan2-java libxalan2-java-gcj libxerces2-java
  libxerces2-java-gcj velocity
제안하는 꾸러미:
  ant-doc libbsf-java junit liblog4j1.2-java jython libjdepend-java libgnumail-java libxml-commons-resolver1.1-java javacc
  libbcel-java-doc libclassworlds-java-doc libcommons-httpclient-java-doc libavalon-framework-java
  libcommons-openpgp-java-doc libdoxia-java-doc libjtidy-java-doc libplexus-classworlds-java-doc
  libplexus-component-api-java-doc libplexus-container-default-java-doc libplexus-interactivity-api-java-doc
  libplexus-utils-java-doc libplexus-velocity-java-doc libwagon-java-doc libxalan2-java-doc libxsltc-java
  libxerces2-java-doc velocity-doc
다음 새 꾸러미를 설치할 것입니다:
  ant ant-gcj ant-optional ant-optional-gcj antlr libantlr-java libantlr-java-gcj libbcel-java libclassworlds-java
  libcommons-cli-java libcommons-collections-java libcommons-httpclient-java libcommons-logging-java libcommons-net-java
  libcommons-openpgp-java libdoxia-java libganymed-ssh2-java libjdom0-java libjsch-java libjtidy-java liblogkit-java
  liboro-java libplexus-classworlds-java libplexus-component-api-java libplexus-container-default-java
  libplexus-interactivity-api-java libplexus-utils-java libplexus-velocity-java libregexp-java libservlet2.3-java
  libslide-webdavclient-java libwagon-java libwerken.xpath-java libxalan2-java libxalan2-java-gcj libxerces2-java
  libxerces2-java-gcj maven2 velocity
0개 업그레이드, 39개 새로 설치, 0개 지우기 및 0개 업그레이드 안 함.
20.5M바이트 아카이브를 받아야 합니다.
이 작업 후 64.8M바이트의 디스크 공간을 더 사용하게 됩니다.
계속 하시겠습니까 [Y/n]?
'Yes'로 계속 진행하면, 관련 꾸러미까지 한꺼번에 설치된다.

설치 여부 확인
$> mvn -v

Maven version: 2.0.9
Java version: 1.6.0_0
OS name: "linux" version: "2.6.27-11-generic" arch: "i386" Family: "unix"

2. Maven Repository 설정
2.1 개인 설정
$>cd ~
$>ls -la '.m2'

만약 .m2 Directory가 없다면
$>mkdir '.m2'

settings.xml 화일 생성 (/etc/maven2 밑의 settings.xml을 복사하여 수정) : 붉은 부분을 추가
$>cp /etc/maven2/settings.xml ~/.m2/
$>vi ~/.m2/settings.xml

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in $HOME/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the system property:
 |
 |                 -Dorg.apache.maven.user-settings=/path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all maven
 |                 users on a machine (assuming they're all using the same maven
 |                 installation). It's normally provided in
 |                 ${maven.home}/conf/settings.xml.
 |
 |                 NOTE: This location can be overridden with the system property:
 |
 |                 -Dorg.apache.maven.global-settings=/path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings>
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ~/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->
  <localRepository>위치시킬 Reposiory</localRepository>

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net,some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->
   
    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
  </mirrors>
 
  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
      <id>jdk14</id>
      <name>Repository for JDK 1.4 builds</name>
      <url>http://www.myhost.com/maven/jdk14</url>
      <layout>default</layout>
      <snapshotPolicy>always</snapshotPolicy>
    </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |  
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
      <name>target-env</name>
      <value>dev</value>
    </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

설치 완료



Eclipse Plug In 설치 ( http://m2eclipse.codehaus.org/ )

인스톨을 실행

이상과 같이 진행 후 Maven을 이용하여 프로젝트를 진행한다.

Maven Repository 추가
http://docs.codehaus.org/display/M2ECLIPSE/Maven+Indexes+view


Trackback 0 And Comment 0

이런저런 URL

|
순서 없이 정리 합니다. ㅡㅡ;

1. Wiki
www.wikimatrix.org : 각종 위키를 비교해 줍니다. 개인적으론 dekiwiki을 사용하기로 결정했습니다. ^^

2. Eclipse
 plug-in  toString  http://eclipse-jutils.sourceforge.net/
   maven Repository Search  http://sourceforge.jp/projects/mrsp/
   Hibernate  http://download.jboss.org/jbosstools/updates/stable/
     


3. Maven
http://www.mvnrepository.com/ : maven 관련된 pom을 조회할 수 있습니다.

4. Hibernate


99. Ajax
http://echo.nextapp.com/site/
Trackback 0 And Comment 0

MindTouch

|
MindTouch 리포지터리 추가

"/etc/apt/sources.list" 파일을 편집하여 다음 줄을 추가합니다 : 

deb http://repo.mindtouch.com xUbuntu_9.04/

다음 명령어를 입력하여 패키지 인덱스를 갱신합니다:

$>sudo apt-get update

 

추천 패키지 설치

다음 명령어를 입력하여 Deki 위키의 모든 기능을 활성화 할 패키지들을 설치합니다:

$>sudo apt-get install html2ps poppler-utils html2text wv gs tidy links msttcorefonts cabextract mono-1.0-devel
(9.04 버전에선 아래와 같이)
$>sudo apt-get install html2ps poppler-utils html2text wv gs tidy links msttcorefonts cabextract mono-devel
주의: 몇몇 종속성을 설치하려면 상호작용이 필요합니다. 모든 인증/확인 질문에 "yes" 로 대답하십시오.

 

PrinceXML 설치

HTML-to-PDF 인쇄를 활성화하려면, 다음 명령어를 입력하여 PrinceXML 이 설치되어야만 합니다:

$>sudo wget http://www.princexml.com/download/prince_7.0b1-1_i386.deb
$>sudo dpkg -i prince_7.0b1-1_i386.deb

Deki 설치

Deki 위키를 다음 명령어를 사용하여 설치합니다 :
deki-enterprise을 설치하게 되면, 30일간의 사용이 가능한 Trial Version에 대한 License을
dekiwiki을 설치하게 되면, 영구히 사용가능한 Perpetual Version을 설치할 수 있습니다.

$>sudo apt-get install deki-enterprise
or
$>sudo apt-get install dekiwiki
주의: 몇몇 종속성을 설치하려면 상호작용이 필요합니다. 모든 인증/확인 질문에 "yes" 로 대답하십시오.

Trusted Roots Certificates 설치

다음을 입력하여 Mozilla LXR 웹사이트에서 trusted roots certificates  를 Mono certificate store 로 설치합니다:

$>sudo su dekiwiki

$> mozroots --import --sync
$> exit

아파치 가상 호스트 설정

설치가 끝난 후 /etc/apache2/sites-available/dekiwiki 를 편집하여 ServerName 을 위키로 가기위해 웹브라우저에 입력하게 될 URL과 동일하게 합니다. 이는 아파치 가상 호스트가 트래픽을 Deki 위키로 전달하게 합니다.

다음 명령어를 입력하여 아파치에서 Deki 위키를 활성화하고 아파치의 초기 기본 사이트를 비활성화합니다:

$>sudo a2ensite dekiwiki
$>sudo a2dissite default
위의 실행이 완료되었으면, 다음을 입력하여 아파치를 다시 로드합니다:
$>sudo /etc/init.d/apache2 reload

축하합니다! Deki 위키가 이제 설치되었고 "http://이곳에_귀하의_서버주소를_입력/config/index.php" 으로 연결하여 설정을 완료하실 수 있습니다.




상기 내역은 우분투 8.04 MindTouch Deki 엔터프라이즈 패키지 설치 에 자세히 설명된 내용입니다.
유의 하실 점은
deki-enterprise 설치가 아닌 dekiwiki을 설치해야 Enterprise 버젼이 아니라는 것 입니다.
즉, Trial 사용을 피하게 됩니다.

dekiwiki을 설치후 Apache reload시에 아래와 같은 메세지가 나오면서 Apache의 구동에 실패한다면,
syntax error on line 31 of /etc/apache2/sites-enabled/dekiwiki:
Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration
...fail!


아래 명령으로 php5 module을 활성화 시켜준다.
$>sudo a2enmod php5
$>sudo /etc/init.d/apache2 restart

나의 경우에는 이후 이상없이 Dekiwiki가 구동 되었다.
Trackback 0 And Comment 1

Subversion 설치

|
Ubuntu에서 Subversion 설치 및 svn protocol 이용

1. Subversion을 설치한다.
$>sudo apt-get install subversion

2. svn 그룹 생성
$>sudo addgroup svn

3. svn 그룹에 사용할 계정 연결
$>sudo adduser 계정명 svn

4. 저장소 생성
$>sudo mkdir /home/svn

5. 관리할 repository 생성 및 권한 설정
$>sudo svnadmin create --fs-type fsfs 레파지토리명

$>sudo chown -R 계정명:svn /home/svn/레파지토리명
$>sudo chmod -R g+ws /home/svn/레파지토리명

6. configure 화일 수정
$>vim /home/svn/레파지토리명/conf/svnserve.conf

### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository.  (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)

### Visit http://subversion.tigris.org/ for more information.

[general]
### These options control access to the repository for unauthenticated
### and authenticated users.  Valid values are "write", "read",
### and "none".  The sample settings below are the defaults.
anon-access = read
auth-access = write
### The password-db option controls the location of the password
### database file.  Unless you specify a path starting with a /,
### the file's location is relative to the directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### Uncomment the line below to use the default password file.
password-db = passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control.  Unless you specify a path
### starting with a /, the file's location is relative to the the
### directory containing this file.  If you don't specify an
### authz-db, no path-based access control is done.
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa.  The default realm
### is repository's uuid.
realm = 레파지토리명's Repository

[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256

7. 패스워드 설정
$>vim /home/svn/프로젝트명/conf/passwd

### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the
### example below it contains one section labelled [users].
### The name and password for each user follow, one account per line.

[users]
# harry = harryssecret
# sally = sallyssecret
사용자명 = 패스워드

8. 실행
$>sudo svnserve -d -r /home/svn

9. Service로 등록하기

9.1 Script 화일 생성
$>cd /etc/init.d/
$>sudo touch svnserve
$>sudo vi svnserve

# Start SVN
svnserve -d -r /home/svn

9.2 Script 화일 속성 변경
$>sudo chmod +x svnserve

9.3 Boot Sequence에 Script 추가
$>sudo update-rc.d svnserve defaults
결과
Adding system startup for /etc/init.d/svnserve ...
/etc/rc0.d/K20svnserve -> ../init.d/svnserve
/etc/rc1.d/K20svnserve -> ../init.d/svnserve
/etc/rc6.d/K20svnserve -> ../init.d/svnserve
/etc/rc2.d/S20svnserve -> ../init.d/svnserve
/etc/rc3.d/S20svnserve -> ../init.d/svnserve
/etc/rc4.d/S20svnserve -> ../init.d/svnserve
/etc/rc5.d/S20svnserve -> ../init.d/svnserve

참고 사이트 : http://www.pyrasis.com/main/Subversion-HOWTO

etc. Eclise Subversion Plug-in 추가 ('가' 혹은 '나'를 선택)
가. Subclipse
나. Subversive

※ 참고. 윈도우 환경이라면 '나'를 선택, Linux 환경이라면 '가'를 선택하여 사용 중입니다.

Trackback 0 And Comment 0

10th Java Conference

|
올해도 즐겁고 잼나게 행복한 시간이 되었으면 좋겠당..
제 10회 한국자바개발자 컨퍼런스
Trackback 0 And Comment 0

Ubuntu에서 Synergy 사용하기

|
잘 정리된 글입니다.
매번 Synergy 땜시 고생이 많은데..  쩝..

Starting the Synergy SERVER on boot up.

Sample configuration  file
section: screens
        youngseok7_lee:
        magpie-desktop:
                super = meta
end

section: links
        youngseok7_lee:
                left = magpie-desktop
        magpie-desktop:
                right = youngseok7_lee
end

section: options
        switchDelay = 0
end



Make a directory in /etc to store the configuration:

Code:
sudo mkdir /etc/synergy
Setup my synergy server configuration file:
Code:
sudo gedit /etc/synergy/synergy.conf
To make the server run when gdm runs, but before anyone has logged in:

edit /etc/gdm/Init/Default:
Code:
sudo gedit /etc/gdm/Init/Default
Added the following lines in the middle of the file BEFORE the "sysmodmap=/etc/X11/Xmodmap" line:

Code:
SYNERGYS=`gdmwhich synergys`
if [ x$SYNERGYS != x ] ; then
$SYNERGYS --config /etc/synergy/synergy.conf
fi
The only problem with that is once you log in it kills off the server, so you need to make it start again for you.

edited /etc/gdm/Init/Default:
Code:
sudo gedit /etc/gdm/PreSession/Default
Added the following lines in the middle of the file BEFORE the "XSETROOT=`gdmwhich xsetroot`" line:
Code:
SYNERGYS=`gdmwhich synergys`
if [ x$SYNERGYS != x ] ; then
$SYNERGYS --config /etc/synergy/synergy.conf
fi
Log out and back in again.

The synergy server should now startup and run whenever your gdm session does.




Starting the Synergy CLIENT on boot up.
These instructions should work for running the synergy client on your UBUNTU machine to connect to a locally networked computer running the synergy server. (I've not actually tried them myself.)
Let us know how you get on.

NOTE:
The <address of server machine> will probably be an ip address that looks something like 192.168.0.1 (DON'T put in the exact string <address of server machine>)

To make the client run when gdm runs, but before anyone has logged in:

edit /etc/gdm/Init/Default:
Code:
sudo gedit /etc/gdm/Init/Default
Added the following lines in the middle of the file BEFORE the "sysmodmap=/etc/X11/Xmodmap" line:

Code:
SYNERGYC=`gdmwhich synergyc`
if [ x$SYNERGYC != x ] ; then
$SYNERGYC <address of server machine>
fi
The only problem with that is once you log in it kills off the client, so you need to make it start again for you.

edited /etc/gdm/Init/Default:
Code:
sudo gedit /etc/gdm/PreSession/Default
Added the following lines in the middle of the file BEFORE the "XSETROOT=`gdmwhich xsetroot`" line:
Code:
SYNERGYC=`gdmwhich synergyc`
if [ x$SYNERGYC != x ] ; then
$SYNERGYC <address of server machine>
fi
Log out and back in again.

The synergy client should now startup and run whenever your gdm session does.

NOTE:
The <address of server machine> will probably be an ip address that looks something like 192.168.0.1 (DON'T put in the exact string <address of server machine>)

Trackback 0 And Comment 0

우분투(7.04)에서 자바 한글 폰트 설정하기

|

우분투(7.04)에서 자바(JRE6)의 한글폰트 설정하기 (가져온 글입니다. )


우분투에서 자바프로그램을 실행시키면 한글이 정상적으로 보이지 않는다.
이는 자바에서 기본값으로 설치된 한글폰트의 경로가 잘못되어 있기 때문이다.
(잘 보이는 수도 있습니다.)

1. fontcofig.properties 파일 생성

filename.-misc-baekmuk_batang-medium-r-normal--*-%d-*-*-c-*-iso10646-1=
  /usr/share/fonts/truetype/baekmuk/batang.ttf
filename.-misc-baekmuk_gulim-medium-r-normal--*-%d-*-*-c-*-iso10646-1=
  /usr/share/fonts/truetype/baekmuk/gulim.ttf
filename.-misc-kochi_gothic-medium-r-normal--*-%d-*-*-c-*-iso10646-1=
  /usr/share/fonts/ja/TrueType/kochi-gothic-subst.ttf
filename.-misc-kochi_mincho-medium-r-normal--*-%d-*-*-c-*-iso10646-1=
  /usr/share/fonts/ja/TrueType/kochi-mincho-subst.ttf

Trackback 0 And Comment 0
prev | 1 | next

티스토리 툴바