구차니의 잡동사니 모음

오늘 부모님댁에 가려다가 급 취소되는 바람에
테크노마트에서 잠시 서성이게 되었다.

한 판매점에서 고심을 하다가 결국에는 왕창 카드로 사버렸다.
고민꺼리는, 키보드를 어떤 타입으로 살지 어떤걸 살지라는 거다.

USB로 살지, 표준형 키보드로 살지, 아니면 미니 키보드 혹은 고무키보드를 살까 하고 말이다.
한참을 머리를 굴리다가, 광명이 내려왔다!!!


아항! 메인 컴퓨터를 PS/2로 연결하고
이전에 사용하던 USB 키보드를 PS/2 변환해서 세컨PC에 연결하거나 노트북에 연결하면 되는구나!



아아~
늙어 간다는건 서러운거다 ㅠ.ㅠ (응?)

우리 징글징글 징글벨~ 사랑하는 애인님이 하사하신 크리스마스 선물!
근데.. 칼로리 대박 ㅠ.ㅠ (2개에 145KCal)

그나저나 플래시 터트렸더니 적절하게 제품명이 가려지는 센스 ㅋ


곰돌이

분위기 매우매우 다운 -ㅁ-!
크리스마스에는 산타를 잡아서 루돌프를 보상으로 받아야지!



(응?)

udhcp는 dhcp client 겸, network setting tool이다.
아무튼 busybox에서 채택하고 있는 dhcp client 이며, 나름 쓸만한 녀석이다.

###################################################################### # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # # A "#" character in the very first column makes the rest of the line # be ignored. Blank lines are ignored. Lines may be indented freely. # A "\" character at the very end of the line indicates the next line # should be treated as a continuation of the current one. # # The "pre-up", "up", "down" and "post-down" options are valid for all # interfaces, and may be specified multiple times. All other options # may only be specified once. # # See the interfaces(5) manpage for information on what options are # available. ###################################################################### # We always want the loopback interface. # # auto lo # iface lo inet loopback # An example ethernet card setup: (broadcast and gateway are optional) # # auto eth0 # iface eth0 inet static #     address 192.168.0.42 #     network 192.168.0.0 #     netmask 255.255.255.0 #     broadcast 192.168.0.255 #     gateway 192.168.0.1 # A more complicated ethernet setup, with a less common netmask, and a downright # weird broadcast address: (the "up" lines are executed verbatim when the # interface is brought up, the "down" lines when it's brought down) # # auto eth0 # iface eth0 inet static #     address 192.168.1.42 #     network 192.168.1.0 #     netmask 255.255.255.128 #     broadcast 192.168.1.0 #     up route add -net 192.168.1.128 netmask 255.255.255.128 gw 192.168.1.2 #     up route add default gw 192.168.1.200 #     down route del default gw 192.168.1.200 #     down route del -net 192.168.1.128 netmask 255.255.255.128 gw 192.168.1.2 # A more complicated ethernet setup with a single ethernet card with # two interfaces. # Note: This happens to work since ifconfig handles it that way, not because # ifup/down handles the ':' any differently. # Warning: There is a known bug if you do this, since the state will not # be properly defined if you try to 'ifdown eth0' when both interfaces # are up. The ifconfig program will not remove eth0 but it will be # removed from the interfaces state so you will see it up until you execute: # 'ifdown eth0:1 ; ifup eth0; ifdown eth0' # BTW, this is "bug" #193679 (it's not really a bug, it's more of a # limitation) # # auto eth0 eth0:1 # iface eth0 inet static #     address 192.168.0.100 #     network 192.168.0.0 #     netmask 255.255.255.0 #     broadcast 192.168.0.255 #     gateway 192.168.0.1 # iface eth0:1 inet static #     address 192.168.0.200 #     network 192.168.0.0 #     netmask 255.255.255.0 # "pre-up" and "post-down" commands are also available. In addition, the # exit status of these commands are checked, and if any fail, configuration # (or deconfiguration) is aborted. So: # # auto eth0 # iface eth0 inet dhcp #     pre-up [ -f /etc/network/local-network-ok ] # # will allow you to only have eth0 brought up when the file # /etc/network/local-network-ok exists. # Two ethernet interfaces, one connected to a trusted LAN, the other to # the untrusted Internet. If their MAC addresses get swapped (because an # updated kernel uses a different order when probing for network cards, # say), then they don't get brought up at all. # # auto eth0 eth1 # iface eth0 inet static #     address 192.168.42.1 #     netmask 255.255.255.0 #     pre-up /path/to/check-mac-address.sh eth0 11:22:33:44:55:66 #     pre-up /usr/local/sbin/enable-masq # iface eth1 inet dhcp #     pre-up /path/to/check-mac-address.sh eth1 AA:BB:CC:DD:EE:FF #     pre-up /usr/local/sbin/firewall # Two ethernet interfaces, one connected to a trusted LAN, the other to # the untrusted Internet, identified by MAC address rather than interface # name: # # auto eth0 eth1 # mapping eth0 eth1 #     script /path/to/get-mac-address.sh #     map 11:22:33:44:55:66 lan #     map AA:BB:CC:DD:EE:FF internet # iface lan inet static #     address 192.168.42.1 #     netmask 255.255.255.0 #     pre-up /usr/local/sbin/enable-masq $IFACE # iface internet inet dhcp #     pre-up /usr/local/sbin/firewall $IFACE # A PCMCIA interface for a laptop that is used in different locations: # (note the lack of an "auto" line for any of these) # # mapping eth0 #    script /path/to/pcmcia-compat.sh #    map home,*,*,*                  home #    map work,*,*,00:11:22:33:44:55  work-wireless #    map work,*,*,01:12:23:34:45:50  work-static # # iface home inet dhcp # iface work-wireless bootp # iface work-static static #     address 10.15.43.23 #     netmask 255.255.255.0 #     gateway 10.15.43.1 # # Note, this won't work unless you specifically change the file # /etc/pcmcia/network to look more like: # #     if [ -r ./shared ] ; then . ./shared ; else . /etc/pcmcia/shared ; fi #     get_info $DEVICE #     case "$ACTION" in #         'start') #             /sbin/ifup $DEVICE #             ;; #         'stop') #             /sbin/ifdown $DEVICE #             ;; #     esac #     exit 0 # An alternate way of doing the same thing: (in this case identifying # where the laptop is is done by configuring the interface as various # options, and seeing if a computer that is known to be on each particular # network will respond to pings. The various numbers here need to be chosen # with a great deal of care.) # # mapping eth0 #    script /path/to/ping-places.sh #    map 192.168.42.254/24 192.168.42.1 home #    map 10.15.43.254/24 10.15.43.1 work-wireless #    map 10.15.43.23/24 10.15.43.1 work-static # # iface home inet dhcp # iface work-wireless bootp # iface work-static static #     address 10.15.43.23 #     netmask 255.255.255.0 #     gateway 10.15.43.1 # # Note that the ping-places script requires the iproute package installed, # and the same changes to /etc/pcmcia/network are required for this as for # the previous example. # Set up an interface to read all the traffic on the network. This # configuration can be useful to setup Network Intrusion Detection # sensors in 'stealth'-type configuration. This prevents the NIDS # system to be a direct target in a hostile network since they have # no IP address on the network. Notice, however, that there have been # known bugs over time in sensors part of NIDS (for example see # DSA-297 related to Snort) and remote buffer overflows might even be # triggered by network packet processing. # # auto eth0 # iface eth0 inet manual #     up ifconfig $IFACE 0.0.0.0 up #       up ip link set $IFACE promisc on #       down ip link set $IFACE promisc off #       down ifconfig $IFACE down # Set up an interface which will not be allocated an IP address by # ifupdown but will be configured through external programs. This # can be useful to setup interfaces configured through other programs, # like, for example, PPPOE scripts. # # auto eth0 # iface eth0 inet manual #       up ifconfig $IFACE 0.0.0.0 up #       up /usr/local/bin/myconfigscript #       down ifconfig $IFACE down [링크 : http://www.cyberciti.biz/faq/setting-up-an-network-interfaces-file/]

[링크 : http://www.cyberciti.biz/tips/howto-ubuntu-linux-convert-dhcp-network-configuration-to-static-ip-configuration.html]

[링크 : http://pig.cs.upt.ro/cgi-bin/man/man2html?interfaces+5]

Graphics Card Hierarchy Chart
GeForce	Radeon	Intel
	Discrete: HD 5970
Discrete: GTX 295	Discrete: HD 4870 X2
	Discrete: HD 5870
Discrete: GTX 280, GTX 285	Discrete: HD 4850 X2, HD 5850
Discrete: 9800 GX2, GTX 260, GTX 275	Discrete: HD 4870, HD 4890, HD 5770
Discrete: 8800 Ultra, 9800 GTX, 9800 GTX+, GTS 250	Discrete: HD 3870 X2, HD 4850, HD 5750
Discrete: 8800 GTX, 8800 GTS 512 MB Go (mobile): 280M	Discrete: HD 4770
Discrete: 8800 GT 512 MB, 9800 GT Go (mobile): 260M (112)	Discrete: HD 4830
Discrete: 8800 GTS 640 MB, 9600 GT, GT 240 (GDDR5)	Discrete: HD 2900 XT, HD 3870
Discrete: 8800 GS, 9600 GSO, GT 240 (DDR3) Go (mobile): 260M (96)	Discrete: HD 3850 512 MB, HD 4670 Mobility: 3870
Discrete: 8800 GT 256 MB, 8800 GTS 320 MB, GT 220 Go (mobile): 8800M	Discrete: HD 2900 PRO, HD 3850 256 MB Mobility: 3850
Discrete: 7950 GX2	Discrete: X1950 XTX, HD 4650 (DDR3)
Discrete: 7800 GTX 512, 7900 GTO, 7900 GTX	Discrete: X1900 XT, X1950 XT, X1900 XTX
Discrete: 7800 GTX, 7900 GT, 7950 GT	Discrete: X1800 XT, X1900 AIW, X1900 GT, X1950 PRO, HD 2900 GT
Discrete: 7800 GT, 7900 GS, 8600 GTS, 9500 GT (GDDR3) Go (mobile): 7950 GTX	Discrete: X1800 XL, X1950 GT, HD 4650 (DDR2) Mobility X1800 XT
Discrete: 6800 Ultra, 7600 GT, 7800 GS, 8600 GT (GDDR3), 9500 GT (DDR2) Go (mobile): 7800 GTX, 7900 GTX	Discrete: X800 XT (& PE), X850 XT (& PE), X1650 XT, X1800 GTO, HD 2600 XT, HD 3650 (DDR3), HD 3670, Mobility: X1900, 3670
Discrete: 6800 GT, 6800 GS (PCIe), 8600 GT (DDR2) Go (mobile): 7800, Go 7900 GS	Discrete: X800 XL, X800 GTO2/GTO16, HD 2600 PRO, HD 3650 (DDR2), Mobility: X800 XT, HD 2600 XT, 3650
Discrete: 6800 GS (AGP) Go (mobile): 6800 Ultra, 7600 GT, 8600M GT, 8700M GT	Discrete: X800 GTO 256 MB, X800 PRO, X850 PRO, X1650 GT Mobility: HD 2600
Discrete: 6800, 7300 GT GDDR3, 7600 GS, 8600M GS Go (mobile): 6800, 7700	Discrete: X800, X800 GTO 128 MB, X1600 XT, X1650 PRO Mobility: X1800
Discrete: 6600 GT, 6800LE, 6800 XT, 7300 GT (DDR2), 8500 GT, 9400 GT Go (mobile): 7600 (128-bit)	Discrete: 9800 XT, X700 PRO, X800 GT, X800 SE, X1300 XT, X1600 PRO, HD 2400 XT, HD 4350, HD 4550 Mobility: X800, 3470 Integrated: HD 3300
Discrete: FX 5900, FX 5900 Ultra, FX 5950 Ultra, 6600 (128-bit) Go (mobile): 6800 (128-bit) Integrated: 9300, 9400	Discrete: 9700, 9700 PRO, 9800, 9800 PRO, X700, X1300 PRO, X1550, HD 2400 PRO Mobility: X1450, X1600, X1700, 2400 XT, X2500, 3450 Integrated: HD 3200, HD 4200
Discrete: FX 5800 Ultra, FX 5900 XT Go (mobile): 6600, Go 7600 (64-bit)	Discrete: 9500 PRO, 9600 XT, 9800 PRO (128-bit), X600 XT, X1050 (128-bit) Mobility: 9800, X700, X1350, X1400, X2300, HD 2400
Discrete: 4 Ti 4600, 4 Ti 4800, FX 5700 Ultra, 6200, 8300, 8400 G, G 210, G 310	Discrete: 9600 PRO, 9800 LE, X600 PRO, HD 2300 Mobility: 9700 (128-bit), X600, X1300 Integrated: Xpress 1250
Discrete: 4 Ti4200, 4 Ti4400, 4 Ti4800 SE, FX 5600 Ultra, FX 5700, 6600 (64-bit), 7300 GS, 8400M GS, 9300M G, 9300M GS	Discrete: 9500, 9550, 9600, X300, X1050 (64-bit) Mobility: 9600
Discrete: 3 Ti500, FX 5200 Ultra, FX 5600, FX 5700 LE, 6200 TC, 6600 LE, 7200 GS, 7300 LE Go (mobile): 5700, 8200M, 9200M GS, 9100 Integrated: 8200, 8300	Discrete: 8500, 9100, 9000 PRO, 9600 LE, X300 SE, X1150 Mobility 9700 (64-bit)	GMA X4500
Discrete: 3, 3 Ti200, FX 5200 (128-bit), FX 5500, Go (mobile): 5600, 6200, 6400, 7200, 7300, 7400 (64-bit)	Discrete: 9000, 9200, 9250 Mobility: 9600 (64-bit), X300
Discrete: FX 5200 (64 bit) Go (mobile): 7200, 7400 (32-bit) Integrated: 6100, 6150	Discrete: 9200 SE Integrated: Xpress 200M, Xpress 1000, Xpress 1150	GMA X3000, X3100, X3500
Discrete: 2 GTS, 4 MX 440, 2 Ultra, 2 Ti, 2 Ti 200	Discrete: 7500	GMA 3000, 3100
Discrete: 256, 2 MX 200, 4 MX 420, 2 MX 400	Discrete: SDR, LE, DDR, 7000, 7200	GMA 500, 900, 950
Discrete: Nvidia TNT	Discrete: Rage 128	Intel 740

[링크 : http://www.tomshardware.com/reviews/geforce-310-5970,2491-7.html]
[링크 : http://k.daum.net/qna/view.html?qid=3zUjr]


확실히 8800이 성능이 좀 안드로메다급인듯 -ㅁ-

간만에 마음을 바로잡고(응?)
UFO:AI 번역을 다시하면서 가고 있었는데

50대 정도의 아저씨께서 신기했는지 타블렛을 보고 이리저리 꼬치꼬치 물어 보신다.
발음이 이상한지 못 알아 들으셔서 타블렛(tablet)이라고 펜으로 끄적끄적 써서 보여드리고 ^^;

아무튼 그 분들의 눈에는
타블렛 PC는 노트북이나 데스크탑과는 다르며 UMPC나 PMP와도 다르게 보이나 보다.
물론 모든 장비가 마찬가지이지만, 컴퓨터 역시 주인이 어떻게 쓰냐에 따라서 다른 장비인데
나의 경우에는 웬만한 데스크탑 뺨치게 사용하고, TC-1100이 워낙 성능이 좋은편이라
웬만한 요즘 나오는 넷북이상의 성능을 뽑아 주는데(배터리 빼고 ㄱ-)
이런저런 이야기 하신다고 해서 알아듣기에는 시간이 부족하실꺼 같아서

"노트북은 노트북은데 분류가 다른 노트북이요 ^^;" 라고 얼버무렸다.



이야기는 계속흘러 어떤일을 하냐까지 물어 보시게 되고
어느덧 이야기는 점점 안드로메다에서 애플로 흘러갔다(-_-)

"핸드폰용 게임 만들어서 대박이라는데, 그런건 어때요?"
라고 하시는데 머.. 내가 아이폰 유저도 아니고 -ㅁ-

아무튼 하루에 수십만개의 프로그램이 올라오고 무료도 있고 유료도 있는데
그중에서 그렇게 팔리는건 몇가지 안된다고 말씀드리니 끄덕끄덕



무슨 바람이 불었는지
오픈소스 이야기도 하게 되었는데, 프로그램 소스라고 하면 이해 못하실테니

"설계도까지 공개해요" 라고 하니
"아니 왜 그런 미친짓을?" 라고 하시는 모습에

오픈 소스의 이념이 그렇게도 생소한 것일려나.. 라는 생각이 들었다.




쓰고 보니 먼가 매우 재미 없는 이야기의 나열.txt

스왑이 부족한데, 파티션 조정은 힘드니 파일로 스왑을 하는 방법이 있다고 한다.

dd if=/dev/zero of=/swapfile bs=1024 count=1000 mkswap /swapfile swapon /swapfile

dd 로 생성할때는 bs는 Blocksize로 byte 단위이다.

[링크 : http://ask.nate.com/qna/view.html?n=8735836]
[링크 : http://linux.die.net/man/8/swapon]


스왑파일은 어디서 생성하던 상관은 없지만,
NFS Client 일 경우에는, 외부 디스크에만 스왑이 되는 듯한 현상이 발생했다.

# swapon swapfile swapon: swapfile has holes swapon: swapfile: Invalid argument

안될때는 이렇게 나오고(NFS 상의 디렉토리에서 수행)

# swapon swapfile Adding 992k swap on swapfile.  Priority:-1 extents:1 across:992k

되면 이렇게 곱게 나와주신다. (USB 로 파일 이전후 시도)


swap filesystem을 지원하지 않아서 그런것 같다는 말도 있긴 하지만,
단순하게 디스크를 옮김으로서 해결이 된것봐서는, swapfile의 위치 제약이 존재하는 듯 하다.
[링크 : http://www.0x61.com/forum/busybox-linux-f110/filesystem-v1-10-0-swapon-swapfile-has-holes-blocksize-t50097.html]

[링크 : https://www.snoopybox.co.kr/1964]

이런걸 보면.. 고양이를 길러보고 싶어진다 -ㅁ-

[링크 : http://bbs2.agora.media.daum.net/gaia/do/kin/read?bbsId=K156&articleId=15776]
[링크 : http://bbs2.agora.media.daum.net/gaia/do/kin/read?bbsId=K156&articleId=15802&RIGHT_KIN=R6]

resolv.conf 는 DNS 서버의 아이피가 들어감
nsswitch.conf 는 호스트 이름을 resolve할 순서를 정의함
hosts 는 static 한 resolve 이름을 정의한다. (예를 들어 리눅스 로컬 서버들끼리의 alias)

삼바에서는
lmhossts 파일을 통해 할 수 있고,
smb.conf 에서 resolve할 순서를 정의할 수 있다.

[링크 : http://linux.die.net/man/5/resolv.conf]
[링크 : http://linux.die.net/man/5/nsswitch.conf]
[링크 : http://linux.die.net/man/5/hosts]
[링크 : http://linux.die.net/man/5/hosts.allow]
[링크 : http://linux.die.net/man/5/hosts.deny]

[링크 : http://linux.die.net/man/7/samba]
[링크 : http://linux.die.net/man/5/smb.conf]
[링크 : http://linux.die.net/man/5/lmhosts]

검색은 해봤지만, 딱히 추천할 만한 조합은 아니라고 한다.

NFS is known for having locking problems. That is why it is never used for shared directories. Usually you would mount an NFS directory read only or as a home folder where only one user can open and lock each file. I recommend dropping NFS and using only Samba shares. Samba handles file locking very well and it also has user authentication whereas NFS handles only host based authentication. Plus Windows utilities for NFS are very rare and poor in design. Samba is called The NFS Bloodbath. NFS has litteraly been fazed out by Samba. Another very promissing file sharing method is sshfs which is user based and with high encryption (excellent sharing directories over WAN connections). [링크 : http://www.linuxquestions.org/questions/linux-software-2/samba-on-nfs-file-locking-476005/]

No, it will always be both slower and more dangerous to run Samba on an NFS client.  Slower, because the traffic must traverse 2 network links. More dangerous, because Samba cannot detect NFS access to the files it shares, and therefore Oplocks break. Always run just one file-server, sharing out multiple protocols (if possible). [링크 : http://www.unixresources.net/linux/lf/56/archive/00/00/06/13/61337.html]

아무튼 현재 겪고 있는 증상은,
smbtree 명령을 이용해서 NFS Client에서 네트워크를 검색하면
\\LOCALHOST와 NFS 서버의 이름만 나온다는 점이다.