Fedora10 설치 가이드 링크

from Info/OS 2009/02/27 13:26 view 46911
원문 : http://www.my-guides.net/
  1. Upgrading from Fedora 7/8/9
  2. Configuring sudo
  3. Configuring yum
  4. Configuring Services
  5. Installing video drivers
  6. Installing Microsoft fonts
  7. Configuring Nautilus
  8. Configuring Firefox
  9. Configuring e-mail client
  10. MP3 and Audio players
  11. DVD & Video
  12. IRC Clients
  13. MSN Messenger Clients
  14. Author, Burn and BackUp CD/DVDs
  15. Download managers
  16. PDF Readers
  17. Torrent Clients
  18. Other Useful Applications
  19. Accessing Windows Partitions
  20. Accessing Windows Shares
  21. Compiz-fusion
  22. KDE
  23. JAVA
  24. Plymouth Graphical Boot

Fedora Network Manger(고정IP사용)

from Info/Tools 2009/02/27 12:27 view 65519
cmd #1

/etc/init.d/NetworkManager stop
(NetworkManager 해지, network 체크)
(고정아이피및, DNS추가)
(network 사용 체크, 사용하고자 하는 고정IP 체크)
service network restart
init 6

cmd #2
ping sendto: Network is unreachable 이 발생했을 때 이런 방법으로 해결..

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever device)

IPADDR=*insert IP address here"
NETMASK=*insert netmask here*
NETWORK=*insert network address here*
BROADCAST=*insert broadcast address here*
GATEWAY=_insert gateway address here*
ONBOOT="yes" = interface will be active at boot time.
       "no"  = interface will NOT be active at boot time.

.If you have X-Windows set up, you can also use RH's "Network Configurator" (/usr/bin/netcfg) which actually writes to these files.
Additionally, after editing the file, do a "ifup eth0" to activate it and ifdown eth0 to deactivate it.

NetworkManager #1

NetworkManager provides automatic network detection and configuration for the system. Once enabled, the NetworkManager service also monitors the network interfaces, and may automatically switch to the best connection at any given time. Applications that include NetworkManager support may automatically switch between on-line and off-line modes when the system gains or loses network connectivity.

These facilities are most useful for modern laptops, where the user may move between wireless networks, and plug in to a variety of wired networks, but NetworkManager also provides features that are relevant to workstations. Current versions of NetworkManager support modem connections, and certain types of VPN. Development of these features is ongoing.

NetworkManager requires Fedora to have drivers for the wired and wireless interfaces on the computer. Many manufacturers of modems and wireless devices provide limited support for Linux. You may need to install additional drivers or firmware on your Fedora system in order to activate these interfaces.

Drivers first
NetworkManager may only work with network interfaces once the relevant drivers are correctly installed on your system. Reboot your system after installing a new firmware or a new driver in order to ensure that the changes take effect.

Enabling NetworkManager on Fedora

Command line way

The installation process for Fedora automatically provides NetworkManager. To enable it, enter the following commands in a terminal window:

1. Set the main service to automatically start on boot: su -c '/sbin/chkconfig --level 345 NetworkManager on' 1. Start the service: su -c '/sbin/service NetworkManager start

For each su command, enter the root password at the prompt.

Graphical Way

Start the system-config-services program, enter your root password and activate the NetworkManager service for runlevel 5.

Gnome-specific information

The NetworkManager tray icon automatically appears on your desktop once the services are started. If the NetworkManager service is active, then the tray icon appears each time that you log in to your desktop.

NetworkManager also stores any encryption keys in the gnome-keyring manager. If your are prompted to enter the keyring password after login, then keep reading. If your login password & the keyring password are the same, then there is a tool built to open the keyring for you on login. The package is called pam_keyring. To configure your system first install pam_keyring with yum:

su -c 'yum -y install pam_keyring'

Second you'll need to modify your /etc/pam.d/gdm file.

su -c 'gedit /etc/pam.d/gdm'

Add the following lines

auth    optional    pam_keyring.so try_first_pass
session optional pam_keyring.so

The order in which this lines are placed in this file are important, here is a copy from a working system

auth required pam_env.so
auth optional pam_keyring.so try_first_pass <---
auth include system-auth
account required pam_nologin.so
account include system-auth
password include system-auth
session optional pam_keyinit.so force revoke
session include system-auth
session required pam_loginuid.so
session optional pam_console.so
session optional pam_keyring.so <---

Now reboot your computer. After login the keyring will be unlocked for you. If your keyring password is different from your login password, don't worry, there is a tool available to change it.

su -c 'yum -y install gnome-keyring-manager gnome-keyring pam_keyring

Once you have installed pam_keyring and gnome-keyring, you will need to log out and back on. Then you can run

/usr/libexec/pam-keyring-tool -c

to change the default password. Alternatively you can now change a password through gnome-keyring-manager. Download and install gnome-keyring-manager. Then highlight the keyring and select Change Keyring Password from the Keyring menu of gnome-keyring-manager.

KDE specific information

To control NetworkManager by a system tray applet you need to install and start the program knetworkmanager of the same named package. The keys to the different networks are stored automatically in KDE's password storage system kwalletmanager.

Further Information

Retrieved from "https://fedoraproject.org/wiki/Tools/NetworkManager"

NetworkManager #2

Fedora 10 uses NetworkManager by default. The primary settings for any network devices will be automatically selected at installation time. Since there is no screen for selecting networking options, most devices will default to using DHCP.

Using NetworkManager has greatly improved networking for many wireless and some less common devices (mobile broadband, GSM, etc.), it may still have problems with some configurations. NetworkManager development and integration into Fedora is still an ongoing effort.

NOTE: The following steps do NOT apply to all users. NetworkManager is highly recommended for Laptop users, especially using wireless with security.

Disabling NetworkManager and Enabling network Service

On machines with a fixed networking device and a fixed IP address (e.g. desktop, server, appliance), it might be more practical to disable NetworkManager and use the older network service. Additionally users requiring virtual device types (bridging, bonding, or VLANs) will also need to use the network service.

Note that the Fedora 10 installer disables the network service by default. To switch to using the network service:

First disable NetworkManager and prevent it from automatically loading:

[mirandam@charon ~]$ sudo /etc/init.d/NetworkManager stop
Stopping NetworkManager daemon: [ OK ]

[mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 NetworkManager off

Next, configure your network settings:

[mirandam@charon ~]$ sudo system-config-network

You should have an eth0 device already showing. To configure the IP settings click on Edit. Do not forget to set DNS on the DNS tab (if you're using fixed IP's). Make sure the eth0 is selected as Active. Then File > Save and quit.

Next, enable the service and make sure it loads at next boot:

[mirandam@charon ~]$ sudo /etc/init.d/network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]

[mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 network on

While it may be possible to re-activate your network without a reboot, it may be recommended to reboot.

Startup Applications Requiring Network

Some applications require the network to be initialized during boot. If you are using NetworkManager and having these problems, edit /etc/sysconfig/network as 'root' and add the following line:

[mirandam@charon ~]$ sudo su -c 'echo NETWORKWAIT=1 >> /etc/sysconfig/network'

Some related information can be found on the Fedora Wiki.

점심먹고 나서 비스타로 부팅하려던 순간 비스타 부팅후 시간이 지나면 공포의 파란화면이 발생했다.

설마 소프트웨어 문제인가 싶어 안전모드로 접속했더니 멀쩡하다 해서 의심되는 소프트웨어 몇개를 간추려 보았다.

커널쪽에 접근하는거 중에 내심 불안한 보안툴!! 알약을 지웠더니 정상부팅이 되었는데....

결국 이스트소프트 - 알약 홈페이지에 공지가 나오는구나 ㅜ_ㅜ... 시댕... 잘좀해요!! 다시 깔아야 하나.. 신용도 하락중..그래도 써야지-_-...

[긴급공지] 일부 비스타 PC의 재부팅 현상 복구 방법

Tag | ,


from Study/Network 2009/02/27 09:37 view 24816

1. RTP & RTSP connection


2. RTP

  • 실시간 Application 을 위한 종단 간 네트워크 전송 기능 제공.

  • 실시간 세션에 관한 정보가 포함되어 있으므로 Application은 지터 잘못된 패킷 순서 및 삭제된 패킷을 쉽게 조정 가능.

  • 자원예약이 없으므로 서비스 품질 보장 없음.

  • 맞춤형 프로토콜 - 헤더를 Application 에 따라 변경가능하다.

  • UDP/IP 로 패킷을 전송한다. Payload 부분에 멀티미디어 데이터가 포함된다.


  • RTP 와 결합하여 작동하는 제어 프로토콜로써 동작한다.

  • 데이터 품질에 대한 피드백과 맴버쉽정보를 전달한다..

  • 패킷손실률, 지터, 라운드트립 지연등.

  • 이를 바탕으로 흐름제어, 에러제어등을 수행할 수 있다.


  • 미디어 플레이어가 매체 스트림의 전송을 제어 할 수 있는 프로토콜.

  • 실시간 멀티미디어 데이터 저송제어로써 HTTP 의 확장.

  • 실제 데이터를 전송하지는 않는다.

  • 네트워크 원격제어 역할을 수행한다.

  • UDP나 TCP 상으로 전송될 수 있다.

5. RTSP 흐름도


이 글은 스프링노트에서 작성되었습니다.

Tag |


from Link 2009/02/27 02:44 view 27566


IBM KLDP Sgi c++ QT catch22 드라이버온라인 wiki codeguru phrack Devpia winapi codeproject msdn whdc debuglab gpgstudy alhem codase LinuxQuestions lwn 리눅스내부소스 리눅스리뷰 리눅스잡지

Tag | ,