http://noneway.tistory.com

이사람 블로그에 감동먹었어...

우분투 사용법 및 모든것이 나와있는 이분의 블로그 사랑하겠다!!

2012년 열심히 파보자!!

*** 출처: 오유 - http://todayhumor.co.kr/board/view.php?kind=&ask_time=&search_table_name=&table=bestofbest&no=62458&page=1&keyfield=&keyword=&mn=&nk=&ouscrap_keyword=&ouscrap_no=&s_no=62458&member_kind=

신설 KTX 구간이 수서-평택 구간이다.

근데~수서가 어디~~게?

바로 내곡동 근처야 ㅋㅋㅋㅋㅋㅋㅋ

그리고 신규노선 언제 만들기로 했을까? 바로 2009년!!!

지금 내곡, 세곡, 수서는 개발제한이 걸려 있는데 여기가 개발제한 풀리면 완전 대박 터지는 곳이야. 그냥 대박이 아니라 초초초초초대박이야. 강남이랑 분당이랑 연결되는 곳이거덩.

참, 이 곳에는 이상득 의원과 오세훈 전 서울시장 부인도 땅이 있네. 오잉, 이게 무슨 우연이야?

정부가 KTX 민영화하면 요금이 20% 싸진데. 근데 KTX가 비싼간 교차보조라고 KTX 수익으로 다른 지방 철도 적자를 보전해주느라 비싼거야. 즉~~~KTX 민영화하면 다른 철도 적자는 더 커져.

그리고 정부 민영화 논리의 근간이 되는 한국교통연구원(KOTI), 여기가 또 골때려.

지금 인천공항철도 수요 예측한 곳이 어디~~게? ㅋㅋㅋ KOTI야 KOTI!!

첫해 하루 평균 21만명, 2021년에 82만명이 쓸거라고 했어 ㅋㅋㅋㅋㅋ 근데 지금은 2만명도 안 돼 ㅋㅋㅋㅋㅋㅋ

또 부산-김해 경전철 수요 예측 연구에서 개통 첫해 하루 17만명, 2030년 32만명 예측했어.

그런데 ㅋㅋㅋㅋㅋㅋ 하루 3만명 ㅋㅋㅋㅋㅋㅋㅋㅋ 으악 ㅋㅋㅋㅋㅋ

한마디로 KTX 민영화 논리의근간이 되는 KOTI는 그냥 정부가 까라면 까는 그런대야. 뭔가 하고 싶은데 연구결과가 필요할때 만들어주는거라고 ㅋㅋㅋㅋㅋㅋ

지금 허준영 철도공사 사장 물러가고 후임으로 김희국 국토부 2차관이 거런되거든? 근데 이 사람이 4대강 살리기 기획단장이고 추진본부장이야 ㅋㅋㅋㅋ 4대강만 망치기 아깝다 이거지 ㅋㅋㅋㅋ

민영화, 민영화 하니까 우리가 반대하잖아? 그래서 정부가 만든게 경쟁체제 도입 ㅋㅋㅋㅋ

장난해? ㅋㅋㅋ 말만 바꾸면 만사 오케이냐 ㅋㅋㅋㅋ

진짜 그 분은 정말 깨알같이 털어드시는거 같아 ㅋㅋㅋㅋ

내곡동 포에버다, 포에버!!

http://www.juniper.net/techpubs/software/junos/junos93/swconfig-cli/commit.html

commit

Syntax

commit <<at <"string">> <and-quit> <check> <comment <"comment-string">>

<confirmed> <display detail> <minutes> <synchronize<force>>

Release Information

Command introduced before JUNOS Release 7.4.

Description

Commit the set of changes to the database and cause the changes to take operational effect.

Options

at <"string">—(Optional) Save software configuration changes and activate the configuration at a future time, or upon reboot.

string is reboot or the future time to activate the configuration changes. Enclose the string value (including reboot) in quotation marks (“ ”). You can specify time in two formats:

• A time value in the form hh:mm[:ss] (hours, minutes, and optionally seconds)— Commit the configuration at the specified time, which must be in the future but before 11:59:59 PM on the day the commit at configuration command is issued. Use 24-hour time for the hh value; for example, 04:30:00 is 4:30:00 AM, and 20:00 is 8:00 PM. The time is interpreted with respect to the clock and time zone settings on the router.

• A date and time value in the form yyyy-mm-dd hh:mm[:ss] (year, month, date, hours, minutes, and, optionally, seconds)—Commit the configuration at the specified day and time, which must be after the commit at command is issued. Use 24-hour time for the hh value. For example, 2003-08-21 12:30:00 is 12:30 PM on August 21, 2003. The time is interpreted with respect to the clock and time zone settings on the router.

For example, commit at “18:00:00". For date and time, include both values in the same set of quotation marks. For example, commit at "2005-03-10 14:00:00".

A commit check is performed when you issue the commit at configuration mode command. If the result of the check is successful, then the current user is logged out of configuration mode, and the configuration data is left in a read-only state. No other commit can be performed until the scheduled commit is completed.

Note: If the JUNOS software fails before the configuration changes become active, all configuration changes are lost. You cannot issue the commit at configuration command when there is a pending reboot. You cannot issue the request system reboot command once you schedule a commit operation for a specific time in the future. You cannot commit a configuration when a scheduled commit is pending. For information about how to use the clear command to cancel a scheduled configuration, see the JUNOS System Basics and Services Command Reference.

and-quit—(Optional) Commit the configuration and, if the configuration contains no errors and the commit succeeds, exit from configuration mode.

check—(Optional) Verify the syntax of the configuration, but do not activate it.

comment <"comment-string">—(Optional) Add a comment that describes the committed configuration. The comment can be as long as 512 bytes and must be typed on a single line. You cannot include a comment with the commit check command. Enclose comment-string in quotation marks (" "). For example, commit comment "Includes changes recommended by SW Lab".

confirmed <minutes>—(Optional) Require that the commit be confirmed within the specified amount of time. To confirm a commit, enter either a commit or commit check command. If the commit is not confirmed within the time limit, the configuration rolls back automatically to the precommit configuration and a broadcast message is sent to all logged-in users. To show when a rollback is scheduled, enter the show system commit command.

Range: 1 through 65,535 minutes

Default: 10 minutes

display detail—(Optional) Monitors the commit process.

synchronize <force>—(Optional) If your router has two Routing Engines, you can manually direct one Routing Engine to synchronize its configuration with the other by issuing the commit synchronize command. The Routing Engine on which you execute this command (request Routing Engine) copies and loads its candidate configuration to the other (responding Routing Engine). Both Routing Engines then perform a syntax check on the candidate configuration file being committed. If no errors are found, the configuration is activated and becomes the current operational configuration on both Routing Engines. The commit synchronize command does not work if the responding Routing Engine has uncommitted configuration changes. However, you can enforce commit synchronization on the Routing Engines by using the force option. When you issue the commit synchronize command with the force option from one Routing Engine,the configuration sessions on the other Routing Engine will be terminated and its configuration synchronized with that on the Routing Engine from which you issued the command.

Note: When you issue the commit synchronize command, you must use the apply-groups re0 and re1 commands. For information about how to use groups, see Applying a Configuration Group. The responding Routing Engine must use JUNOS Release 5.0 or later.

Usage Guidelines

See Verifying a JUNOS Configuration, Committing a JUNOS Configuration, Scheduling a JUNOS Commit Operation, Deactivating and Reactivating Statements and Identifiers, Monitoring the JUNOS Commit Process, and Adding a Comment to Describe the Committed Configuration.

Required Privilege Level

configure—To enter configuration mode.

Note: If you are using JUNOS software in a Common Criteria environment, system log messages are created whenever a secret attribute is changed (for example, password changes or changes to the RADIUS shared secret). These changes are logged during the following configuration load operations: load mergeload replaceload overrideload update For more information, see the Secure Configuration Guide for Common Criteria and JUNOS-FIPS .

http://nettenna.tistory.com/398

오늘 오전에 방통대학교 입학지원을 했다.

물론 달님이의 응원으로 할 수 있었다.

자세히 알아보고 또 알아보면서 올해 Plan을 잡아야한다.

무조건 열심히!!