Looks like there's on open bug on this issue.

I was able to configure iTerm2 to use byobu locally on OS X as well as remotely over ssh on an Ubuntu 14.04 server.

Using:

  • OS X version: 10.9.5 Build 13F34
  • iTerm2 version: Build 1.0.0.20140629

First, in your OS X system preferences, edit your keyboard settings and remove or change any shortcut settings that may conflict with byobu (i.e. Ctrl + F1-F12).

Option 1: Workaround using escape sequences

Here's a workaround that will work without adding full functionality to the FN keys. This will allow you to split windows vertically using the byobu escape key:

  1. Start byobu.

  2. Set your desired Ctrl-A behavior by running: byobu-ctrl-a. I chose to go with Emacs-mode.

  3. Run byobu-config and choose or change your escape sequence. I went with the new default Ctrl + S. The F12 key is also an escape sequence

  4. Now you can issue a command with your escape sequence. Try F12 then % or Ctrl + sthen % to split a window vertically. For a full list of commands, try Ctrl + s then ? or F12 then ?.

Option 2: Setting iTerm2 key mappings to fully use all FN keys.

You can add some key mappings to your iTerm2 profile to get the CTRLALTSHIFT, and FNkeys to work with byobu. This is tedious, but I went through the exercise and it seems to work. I don't think there's an automated way to save these key mappings with iTerm2.

  1. Open iTerm2 preference and select Profiles.
  2. Choose the profile you'd like to use.
  3. Open the Terminal pane and under "Report terminal type" choose "linux".
  4. Open the Keys pane and manually add the following key bindings. Here's an example how to add one key binding:

    • Click the '+' icon.
    • Enter the keyboard shortcut being mapped in the first field. Example: CTRL + F2
    • Select "Send Escape Sequence" in the Action field.
    • Enter the characters in the third field. Example: [1;5Q

You can determine the control characters for any key sequence not listed here by referring to the tmux source code.

Repeat this for all of these mappings to make the corresponding byobu command work:

  • CTRL + F2 : [1;5Q
  • CTRL + SHIFT + F2 : [1;6Q
  • ALT + LEFT : [1;3D
  • ALT + RIGHT : [1;3C
  • ALT + UP : [1;3A
  • ALT + DOWN : [1;3B
  • CTRL + F3 : [1;5R
  • CTRL + F4 : [1;5S
  • CTRL + SHIFT + F3 : [1;6R
  • CTRL + SHIFT + F4 : [1;6S
  • SHIFT + ALT + LEFT : [1;4D
  • SHIFT + ALT + RIGHT : [1;4C
  • SHIFT + ALT + UP : [1;4A
  • SHIFT + ALT + DOWN : [1;4B
  • CTRL + F5 : [15;5~
  • CTRL + SHIFT + F5 : [15;6~
  • ALT + F6 : [17;3~
  • CTRL + F6 : [17;5~
  • ALT + PPAGE : [5;3~
  • ALT + NPAGE : [6;3~
  • CTRL + F8 : [19;5~
  • ALT + SHIFT + F8 : [19;4~
  • CTRL + SHIFT + F8 : [19;6~
  • CTRL + F9 : [20;5~
  • ALT + F11 : [23;3~
  • CTRL + F11 : [23;5~
  • ALT + F12 : [24;3~
  • CTRL + F12 : [24;5~
  • ALT + INS[2;3~

Summary

To get things to work we needed to:

  • Remove conflicts with OS X keyboard shortcuts.
  • Edit the terminal key mappings to send the correct escape sequences when using function keys.
  • Set the iTerm2 terminal type to "Linux", which sets the TERM environmental variable to be "linux". Byobu and/or Tmux seemed to be sensitive to this.

Some other references on escape sequences: SO link and xterm-keys.c


Default directory for new windows and panes

It looks like there are some difference in tmux window default directory between tmux 1.8 and tmux 1.9 (SrcSrcSrc). If you are using byobu with tmux 1.9 you can try adding this to your ~/.byobu/keybindings.tmux file so that when you create new windows or vertical/horizontal splits that they open in the same directory as the current pane:

unbind-key -n F2
bind-key -n F2 display-panes \; new-window -c "#{pane_current_path}" -n -
unbind-key -n C-F2
bind-key -n C-F2 display-panes \; split-window -hc "#{pane_current_path}"
unbind-key -n  S-F2
bind-key -n S-F2 display-panes \; split-window -vc "#{pane_current_path}"
unbind-key %
bind-key % display-panes \; split-window -hc "#{pane_current_path}"
unbind-key |
bind-key | display-panes \; split-window -vc "#{pane_current_path}"

Press F5 to reload settings.

출처 : http://kiboard.tistory.com/8

맥에서 CD/DVD를 이미지 파일 (iso, dmg, cdr)로 만들기

요즘 CD나 DVD를 많이 이용하지는 않지만, 가끔 CD/DVD를 이미지로 만들어 두어야 할 일이 생기곤 하죠.
윈도우에는 nero, ultraISO와 같은 유명한 소프트웨어에 이러한 기능들이 들어있고, daemon에서도 이미지 생성기능이 있다고 들은 것 같기도 합니다.

아무튼!!


맥에는 "디스크 유틸리티" 라는 내장된 프로그램을 이용하여 이미지 만들기가 가능하고, 그 방법에는 여러가지가 있습니다. (터미널 명령어 이용 등.)
디스크 유틸리티를 이용하면, 보통 dmg나 cdr 이미지로 생성이 됩니다. 하지만 윈도우에서도 함께 이용할 수 있으려면, ISO로 만들어 두는 것이 여러가지로 유용하겠죠?

그럼 ISO 이미지 파일을 생성하는 두가지 방법을 소개하도록 하겠습니다. 




첫번째. 디스크 유틸리티 + 터미널 명령어 (hdiutil)을 이용한 ISO 만들기


  1. Spot light 을 이용하여 "디스크 유틸리티" 실행

     

     

  2. 왼쪽 항목에 CD/DVD 목록 클릭
  3. 상단의 새로운 이미지 아이콘을 클릭
  4. 별도저장 이라는 칸에 원하는 이미지 이름 넣고 저장 경로 선택 (현재는 데스크탑으로 설정)
  5. 이미지 포맷을 "DVD/CD 마스터" 선택 후 저장 버튼을 누르면 monkey.cdr 파일 생성됨
  6. Spotlight 을 이용하여 "터미널" 실행


     
  7. 이미지 파일이 저장된 경로 (현재는 데스크탑)로 이동

    $ cd ~/Desktop


    $ hdiutil makehybrid 
    라고 입력하면 아래와 같이 사용법이 나온다. 

    hdiutil: makehybrid: no source specified 
    Usage: hdiutil makehybrid -o 
    hdiutil makehybrid -help 


    변환하는 명령어는
    $ hdiutil makehybrid -iso -joliet -o money.iso monkey.cdr 

    Creating hybrid image... 

    ........................................................................................................................
    명령어를 입력하면 위와 같은 메세지가 보이면서 iso 이미지가 따로 생성이 된다.



두번째, 터미널에서 drutil 명령어로 ISO 이미지 파일 만들기



  1. 터미널을 열고 디스크 유틸리티를 이용해 디스크 상태를 본다.
    $ drutil status

    그러면 아래와 같이 CD-ROM 정보가 표시가 된다.




  2. CD/DVD 디스크의 마운트를 해제 한다.

    위에 정보를 보면 name: /dev/disk2 라고 보인다. 이름이 disk2 인 것이다.
    $ diskutil unmountDisk disk2 

    Unmount of all volumes on disk2 was successful 이라는 메세지가 나오면 마운트가 해제된 것.



  3. dd 유틸리티를 이용하여 ISO 이미지를 기록한다.
    $ dd if=/dev/disk2 of=mokey.iso

    /dev/disk2 의 볼륨을 monkey.iso 로 만들라는 의미
    위의 명령어를 입력하면, 한참동안 머물러 있는데, 이것은 이미지 기록을 준비하는 것이니 기다려야 합니다. 기록이 완료되면 아래와 같은 메세지가 출력됩니다.

    1484047+1 records in 
    1484047+1 records out 
    759832416 bytes transferred in 493.307023 secs (1540283 bytes/sec) 
     


  4. mount 해제 했던 것을 다시 mount 해준다.
    $ diskutil mountDisk disk2


출처 : http://hyunjong.tistory.com/entry/OSX-MacPort-사용법


MacPorts: BSD의 포트시스템을 OSX에서도 사용할수 있도록 진행된 프로젝트.(예전엔 DarwinPorts였단다.)
http://www.macports.org/ 가서 설치.. 귀차니즘으로 인한 DMG설치 추천. ~_~

- MacPorts 갱신(-d:debug)
$sudo port -d selfupdate 

- 패키지 목록(tree) 업데이트
$sudo port sync 

- 패키지 검색
$sudo port search PACKAGENAME

- 패키지 정보
$sudo port info PACKAGENAME

- 의존성 검사
$sudo port deps PACKAGENAME

- 설치
$sudo port install PACKAGENAME

- 제거
$sudo port uninstall PACKAGENAME

- 모든 페키지 제거
$ sudo port -f uninstall installed
$ sudo port clean all

보다 다양한 명령어: http://guide.macports.org/#using.port

Home/End/Page Up/Page Down / Ctrl+C/X/V 등 재 맵핑하기

그냥 KeyReMap4MacBook 이란 프로그램을 설치한 다음 For PC Users 란에서 해당 항목 선택하면 끝.

홈페이지 http://pqrs.org/macosx/keyremap4macbook 여기서 다운~

필요한건 개인이 설정해서 쓸수도 있다.

나는 오른쪽 Shift+ Space를 한영전환키로 쓰는데 미리 맵핑된것이 없어서 

private.xml에 추가했다. 방법은 

1. "Misc&Unistall"탭에서 "Open Private.xml" 선택하면 해당 파일이 있는 위치가 열린다.

2. 메모장으로 첨부내용을 덮어 쓴다.(필요한 경우 편집)

private.xml

3. "Change Key" 탭에 가서 "ReloadXML" 버튼을 누르면 내가 추가한 항목이 나타난다.








NTFS WRITE SUPPORT ON OSX LION WITH NTFS-3G

출처 : http://fernandoff.posterous.com/ntfs-write-support-on-osx-lion-with-ntfs-3g-f

Update 2: Check out this post for a prebuilt binary installer for NTFS-3G that can be used with the Fuse4X solution detailed below (i.e., if you're not willing to go through all the steps of installing XCode, MacPorts, etc. that's detailed below, you can just install Fuse4X binary (fromhere) and the NTFS-3G installer I'm providing on the post linked above).

Update: Thanks to some suggestions from Marcos on the comments below, I kicked myself back into trying to solve the mount problem with uids/gids on fuse4x / ntfs-3g. I've updated the script below, it now improves things somewhat. It's still not perfect - it'll work fine if your user logs in automatically, otherwise, it'll try to wait for 20 seconds (adjustable on the TIMEOUT variable) until the user session is active and it picks up the user id from the session started, and if that too fails, it falls back to the old behavior (fixed uids/gids). There's also an alternative solution for that provided by Marcos on the comments area of his post, check it out (in portuguese - Google Translate is your friend).


It's a well known fact that OSX had NTFS read support for a long time, but write support could only be easily enabled either by:

  • Buying third-party solutions, from Paragon or Tuxera. The latter is actually a product-fied version of the open-source solution mentioned below;
  • Enabling manually on the native driver by messing around with system files. That option is known to be very unstable and can potentially corrupt your NTFS partition, so it's strongly NOT recommended. Also, this worked only on early versions of Snow Leopard - apparently Apple disabled this "feature" later (though it seems nobody tried it again with Lion). It's obvious that with this move Apple was clearly saying that the driver is not reliable for write support and should not be used as such.
  • A port of MacFuse and NTFS-3G provided by Tuxera. The official versions are old and don't work at all on 64-bit kernels (i.e. Lion).

    On the last case, there are unofficial builds of MacFuse that work on 64-bit kernels, but not without a few issues - this post will outline the steps on getting this unofficial version of MacFuse working along with the older version of NTFS-3G (the version that was still free, before Tuxera went completely commercial with it). Also, while most of the procedures detailed here were tested in my OSX Lion installation, it should in theory work on Snow Leopard too, I just have no way to confirm this at this time. Feedback is welcome on that.

    I'm also going to outline the steps on getting to work a solution based purely on MacPorts, a package manager for OSX that works by downloading the source code to a package, compiling it on your machine, and installing it. That solution works fine for the most part, with only a small caveat, that may or may not affect you depending on how you work with your Mac. In my opinion, though, this solution is also more robust and (hopefully, once the small kinks get worked out) bug-free solution and easier to maintain and update (thanks to MacPorts) on the long term, and I hope it gets noticed by the developers involved because of that. I'm personally using this solution right now, but due to it being somewhat more cumbersome to setup, it probably should be taken as geared towards power users - if you want something a bit easier to setup, you're probably better off with the MacFuse + Tuxera's NTFS-3G solution presented below.

    Before we start: While the steps I outline here are more or less foolproof, you'll be in fact messing around with a little bit of the inner workings of OSX. In theory, what you'll do shouldn't completely wreck your system (at worst, you'll no longer be able to mount your NTFS partitions), but the standard disclaimers apply: Any problems caused by what you'll do henceforth are entirely YOUR responsibility, not mine. If your system stops working correctly, if your NTFS partition gets corrupted, if your system blows up to pieces, etc. - it's YOUR fault. Also, since the procedures outlined here modifies system files and needs you to work mostly on the Terminal, some experience with working with the terminal and the bash shell is, while not required, advised, specially in the case you bump into problems. If you're not confortable with that and absolutely need NTFS write support, do me and yourself a favor, and buy one of the paid solutions mentioned above.

    I'll start with the easier solution (for now), since I suppose this will be the one that most people will end up going with as it requires less pre-setup procedures.

    And before you start either of the procedures below, umount your NTFS volume first(right-click / ctrl+click the volume icon on the desktop and select "Eject").

     

    MacFuse + NTFS-3G (older open-source release from Tuxera)

    Get the latest open-source version of NTFS-3G by Tuxera from here and only here - don't get anything newer than that, that would be Tuxera's commercial version, and it'll require you to buy it after the 15-day trial.

    For a 64-bit supported MacFuse, there are two options: this (use the link for the file macfuse-core-10.5-2.1.9.zip) or this. The former is the last open-source version of MacFuse from Tuxera patched by an independent developer to work on 64-bit. The latter is a patched version of a newer version (2.1.15) meant for Wuala's app - although, for our purposes, it should work with NTFS-3G just as well. There are no notable or even documented differences between the older and the newer, so the choice is up to you - during testing, I've used both without problems.

    Unpack the zip file for MacFuse and double-click the pkg file to install. Next, install NTFS-3G from the link above. Once it's done, you'll be requested to restart - do so.

    Once it comes back up, a few moments after the desktop comes up, you'll be greeted by something like this:

    Yeah, that's the issue I mentioned early on. It's not an usability issue, i.e. the partition will be mounted read-write correctly (even though it says on the dialog it wasn't), and you'll be able work with it without any problems or corruption issues, as far as I'm aware. The issue is really just that nagging dialog that pops up every time you mount a NTFS volume, including on boot in this case, if you've got a Windows install on your Mac like me. In short, everything works fine despite that dialog.

    The problem seems to stem from the binary "fuse_wait" from NTFS-3G that's run as a final part of the mounting procedure - for some reason it can't detect that ntfs-3g mounted the volume and stays on a hopeless loop trying to detect this condition until it gives up after 15 seconds. So my workaround involves replacing the fuse_wait binary with a script that does more or less the same thing, but actually detecting (sort of) the mount operation and not timing out.

    Open a Terminal window. First of all, make a backup of the original binary:

    sudo mv /usr/local/bin/fuse_wait /usr/local/bin/fuse_wait.orig

    Then create the file that'll hold our script and setup the proper permissions for it:

    sudo touch /usr/local/bin/fuse_wait
    sudo chmod 0755 /usr/local/bin/fuse_wait
    sudo chown 0:0 /usr/local/bin/fuse_wait

    Now, let's edit the file so we can paste our script into it:

    sudo nano /usr/local/bin/fuse_wait

    Here's the script, paste it into the editor:

    #!/bin/bash
    
    MNTPOINT=$1
    shift
    TIMEOUT=$1
    shift
    MNTCMD=$1
    shift
    
    $MNTCMD "$@" &> /var/log/ntfsmnt.log
    MNTCMD_RETVAL=$?
    
    if [ $MNTCMD_RETVAL -eq 0 ]; then
            until [ `/sbin/mount | /usr/bin/grep -c "$MNTPOINT"` -ge 1 ] || [ $TIMEOUT -eq 0 ]
            do
                           sleep 1
                    let TIMEOUT--
            done
    fi
    
    [ $TIMEOUT -eq 0 ] && RETVAL=1 || RETVAL=$MNTCMD_RETVAL
    
    exit $RETVAL;

    Press CTRL+X, say Yes to save the file, and press Enter to accept the file name.

    Next, we'll edit another file. Still on the Terminal, type:

    sudo nano /System/Library/Filesystems/ntfs-3g.fs/ntfs-3g.util

    We're on nano again. Find the line that looks like this:

    DEFAULT_NTFS_MOUNT_OPTIONS="auto_xattr"

    Add some options to the end so it looks like this:

    DEFAULT_NTFS_MOUNT_OPTIONS="auto_xattr,noatime,auto_cache"

    Again, CTRL+X, say Y to save and press Enter.

    That's it. Reboot, and you should no longer get the error dialog the next time you mount your NTFS partition. If you have any problems, look into the file /var/log/ntfsmnt.log, it should contain some description of any problems found during mount, but I hadn't any so far.

     

    Fuse4x + NTFS-3G from MacPorts

    Fuse4x is a fork of MacFuse intended to bring the old and abandoned MacFuse codebase up to date, and also improve compatibility with the Fuse upstream project, while maintaining compatibility with existing filesystems for MacFuse.

    To get it working, you'll need to install Xcode on your system - if you're on Lion, Xcode's a free download from the App Store. Since MacPorts works by compiling every package you ask to install, there's no way to escape that. You may uninstall Xcode after you install the packages you need, but then you'll lose the ability to easily upgrade packages (using port upgrade) once new versions are released - you'll need to install Xcode again for that.

    Once you get Xcode installed, get MacPorts and install it.

    Done? Ok, after you get all this installed, open a terminal window and type:

    javac

    That should pop up an Apple Update window asking if you'd like to install a Java update and some such. Do that. That's really just a small precaution - if you don't do that now, that window will popup during the build process on MacPorts - in my case, since I wasn't prepared for it, the Java update kept downloading on the background while MacPorts was still building the dependencies for Fuse4x and NTFS-3G. The build process completed sucessfully despite that though, so Java is probably not a required dependency, but it doesn't hurt to be careful, so I recommend to get this missing Java dependency installed first so your build process go without surprises.

    Now that you have the Java dependency installed, we can get to the real meat. First, if you haven't done that yet, update your MacPorts repository:

    sudo port selfupdate
    sudo port upgrade outdated

    Install NTFS-3G - as NTFS-3G now depends on Fuse4x by default (which wasn't the case back when this article was first written), using the command below should install Fuse4x automatically before installing NTFS-3G:

    sudo port install ntfs-3g

    Ok, at this point you should have a functional fuse4x and ntfs-3g install. Unfortunately, since most MacPorts packages are really just the straight source-code for their upstream project with only a few patches to make it compilable on OSX, those packages most often don't really integrate well with the workflow of the system, specially UI-wise (e.g., there are no preference panes for Fuse4x or NTFS-3G). Most importantly, that means that this ntfs-3g install won't automount NTFS volumes at boot or volume insertion (for removable disks) - this would still be done by the standard NTFS driver on OSX. Due to the nature of how most packages are ported over to MacPorts, you'd be expected to mount your NTFS volumes via NTFS-3G manually, via the terminal, which sucks. We'll have to hack our way around to get that working somewhat better.

    The idea is to trick OSX into redirecting the automount procedure for OSX's native NTFS to use NTFS-3G instead. Still on the terminal, make a backup of the file mount_ntfs, which is responsible for mounting NTFS volumes with the native driver:

    sudo mv /sbin/mount_ntfs /sbin/mount_ntfs.orig

    Again, create an empty file, setup the permissions, and open it in an editor:

    sudo touch /sbin/mount_ntfs
    sudo chmod 0755 /sbin/mount_ntfs
    sudo chown 0:0 /sbin/mount_ntfs
    sudo nano /sbin/mount_ntfs

    Ok, we're almost there. Paste this script in the editor:

    #!/bin/bash
    
    VOLUME_NAME="${@:$#}"
    VOLUME_NAME=${VOLUME_NAME#/Volumes/}
    USER_ID=501
    GROUP_ID=20
    TIMEOUT=20
    
    if [ `/usr/bin/stat -f "%u" /dev/console` -eq 0 ]; then
            USERNAME=`/usr/bin/defaults read /library/preferences/com.apple.loginwindow | /usr/bin/grep autoLoginUser | /usr/bin/awk '{ print $3 }' | /usr/bin/sed 's/;//'`
            if [ "$USERNAME" = "" ]; then
                    until [ `stat -f "%u" /dev/console` -ne 0 ] || [ $TIMEOUT -eq 0 ]; do
                            sleep 1
                            let TIMEOUT--
                    done
                    if [ $TIMEOUT -ne 0 ]; then
                            USER_ID=`/usr/bin/stat -f "%u" /dev/console`
                            GROUP_ID=`/usr/bin/stat -f "%g" /dev/console`
                    fi
            else
                    USER_ID=`/usr/bin/id -u $USERNAME`
                    GROUP_ID=`/usr/bin/id -g $USERNAME`
            fi
    else
            USER_ID=`/usr/bin/stat -f "%u" /dev/console`
            GROUP_ID=`/usr/bin/stat -f "%g" /dev/console`
    fi
    
    /opt/local/bin/ntfs-3g \
            -o volname="${VOLUME_NAME}" \
            -o local \
            -o negative_vncache \
            -o auto_xattr \
            -o auto_cache \
            -o noatime \
            -o windows_names \
            -o user_xattr \
            -o inherit \
            -o uid=$USER_ID \
            -o gid=$GROUP_ID \
            -o allow_other \
            "$@" &> /var/log/ntfsmnt.log
    
    exit $?;

    Press Ctrl+X, say Y to save, press Enter to accept the file name.

    Now, note the option -uid and -gid. It teels ntfs-3g which OSX user and group should own the files on the mounted volume. If you don't provide these options, ntfs-3g will default to the root user, which will allow you to do most writing operations on the volume except write/modify to existing files - to be able modify files, you should then specify the uid and gid for the login you use on your system. In a standard OSX installation, the uid 501 and gid 20 should be the first standard user you provided on OSX install, and the "staff" group, respectively. To make sure these uid and gid pair match the ones for the user you use on your system, type in the Terminal (make sure you're not on a root ("#") prompt):

    id -u && id -g

    This should output two lines, the first containing the id for your user, and the second the id of the default group for your user. If they don't match the ones on the script, edit the script again and modify it accordingly. Update: This is needed only in a worst case scenario where you have autologin disabled and you don't login manually within 20 seconds (adjustable in the TIMEOUT variable).

    Now, here's the caveat with the whole Fuse4x method: since we had to explicitly provide the uid and gid for the user/group that'll own the files on the volume in order to have full access to it, this means that this method will have problems in multi-user Mac stations.

    For example, if you have two users - say, john, and mary - on your Mac, john will have a uid of 501 and mary will have a uid of 502. If the mount script is setup as above, john will have full access to the volume, but mary, while being able to mount NTFS volumes just fine, won't be able to modify existing files on the volume, just like mentioned earlier when you don't provide the uid/gid parameter.

    There's no way out of that, as far as I know. I've tried a ton of argument combinations for ntfs-3g while trying to avoid the uid/gid arguments, nothing worked. I welcome suggestions. But for now, it works well enough for me as it is, I'm the only user on my Mac anyway, and I suppose that's the case for most Mac users, so I didn't bother to sweat about it too much. If that's really a problem for you though, then you should be better off with the MacFuse + Tuxera-NTFS-3G solution, that doesn't have this problem.

    Phew, that was a long one. Comments are welcome, of course. Cheers!

    • Favicon of http://timberlandbotases.com BlogIcon sandalias timberland mujer 2012.12.19 16:37

      A business travel by chartered airplane is beneficial in many ways, http://timberlandbotases.com zapatos timberland mujer. Corporate jet charter not only lowers the costs of traveling but also saves lots of time when you travel in a public or regular airline. Time is very crucial when it comes to traveling for business purpose and for a business man time has always more value than money, http://timberlandbotases.com zapatos timberland hombre. Biggest benefits of a business air charter it that you can use a private jet so that your employees can travel together. On the way to making an important business deal they can sit together and have a last time discussion on the matter. This thing is not possible when you are traveling in conventional commercial airline. Also there is less restriction while traveling in a private charter e, http://timberlandbotases.com zapatillas timberland mujer.g, http://timberlandbotases.com timberland botas niño. you are not bound to luggage restrictions, http://timberlandbotases.com timberland españa tiendas. You can bring and access your laptop while traveling, http://timberlandbotases.com timberland españa relojes.Related articles:


      http://blog.sohu.com/people/anyano171/249038455.html http://blog.sohu.com/people/anyano171/249038455.html

      http://tcsc.info/viewthread.php?tid=421687&extra= http://tcsc.info/viewthread.php?tid=421687&extra=

    • Favicon of http://www.moncleroutletespain.com/ BlogIcon moncler españa 2013.01.04 13:37

      Un homme a été ma, http://www.moncleroutletespain.com/ http://www.moncleroutletespain.com/?trisé par des passagers mercredi lors d'une tentative de détournement d'un avion effectuant la liaison entre Oslo et Istanbul, http://www.moncleroutletespain.com/ moncler, rapporte la presse turque, http://www.moncleroutletespain.com/ moncler españa, citant d'autres passagers, http://www.moncleroutletespain.com/ moncler chaquetas.Related articles:


      http://poisontongue.sisain.co.kr/1167 http://poisontongue.sisain.co.kr/1167

      http://www.myaudiologist.kr/344 http://www.myaudiologist.kr/344

    • Favicon of http://www.moncleroutletespain.com/ BlogIcon moncler chaquetas 2013.01.04 16:32

      Act-Up Paris a appelé jeudi l'ex-secrétaire d'Etat à la Ville Fadela Amara, http://www.moncleroutletespain.com/ moncler outlet, nommée inspectrice générale des affaires sociales, http://www.moncleroutletespain.com/ moncler chaquetas, à "communiquer" sur la "censure" par le gouvernement d'un rapport de l'Igas sur l'aide médicale d'Etat (AME), http://www.moncleroutletespain.com/ moncler online. France Mandat d'arrêt à l'encontre des cambrioleurs de Ségolène Royal France Disparition d'une tombe dans un cimetière : Lille condamnéeRelated articles:


      http://share-archive.tistory.com/176 http://share-archive.tistory.com/176

      http://aams.tistory.com/474 http://aams.tistory.com/474

    • Favicon of http://www.moncleroutletespain.com/ BlogIcon moncler españa 2013.01.05 16:25

      Une mère de famille de 40 ans est suspectée d'avoir tenté de se suicider et de tuer ses deux filles, http://www.moncleroutletespain.com/ moncler outlet, dont l'une est lourdement polyhandicapée, http://www.moncleroutletespain.com/ moncler, en ouvrant le gaz à leur domicile de Neuves-Maisons (Meurthe-et-Moselle), http://www.moncleroutletespain.com/ http://www.moncleroutletespain.com/, a-t-on appris vendredi de source judiciaire, http://www.moncleroutletespain.com/ moncler chaquetas.Related articles:


      http://wyseburn.tistory.com/216 http://wyseburn.tistory.com/216

      http://kbar.tistory.com/guestbook?page=4 http://kbar.tistory.com/guestbook?page=4

    출처 : http://x86osx.com/bbs/view.php?id=osxtips&no=1946&ksn=1&kss=1&ksc=0&kst=1&ksm=1&kw=gpt%20mbr

    GUID partition (GPT) 와 Mastar Boot Record (MBR PC BIOS) partition, 그리고 hybrid MBR까지..


    OSX 를 깐다고 삽을 드셨다면, GPT (GUID partition table) 와 MBR 에 대해 들어보셨을 겁니다. 이 글에서는 두 파티션 테이블을 철저히 해부하고 분해해 보도록 하겠습니다. 기술적인 부분이 아닌, 사용자 입장에서 말이지요.

    PC BIOS 기반에서 MS-DOS 시절부터 일반적인 윈도우, 예전 버젼 리눅스 등에서 사용하던 방식이 MBR based partition 입니다. 오랜 역사를 가지고 있지요.

    이 오래된 MBR partition table 의 문제를 해결하고자 나온 것이, EFI 시스템에서 주로 사용하는 GUID partition table (GPT) 입니다.

    일단 두 파티셔닝 방식의 차이를 표를 통해 보겠습니다.



    일단 네줄 요약:

    1. GPT 가 나중에 나왔으니, 당연히 기능은 MBR보다 다 좋습니다. 윈도 쓸 일이 없다면 GPT 쓰시면 됩니다.

    2. 하지만 결정적인 문제는 윈도우에서 GPT가 부팅디바이스로 원래 지원이 안된다는겁니다.

    3. 그래도 hybrid MBR 을 사용하면 윈도 설치 및 활용이 가능합니다.

    4. hybrid MBR 사용이 아주 쉽지만은 않습니다. 위에 나열된 GPT의 장점을 활용할 일이 없다면, 그냥 MBR을 쓰는 것도 좋은 선택입니다.



    자, 그럼 이번엔 3번에 관심있는분. 즉 GPT 디스크에서 윈도우를 설치하고 싶은 분들을 위해 hybrid MBR  에 대해 설명드리겠습니다.

    먼저, GPT 디스크에 OSX와 Windows 모두 설치방법:

    1. OSX 설치프로그램으로 디스크를 GPT 로 파티셔닝합니다. 윈도우 깔 공간은 따로 만들어놔야겠지요.

    2. OSX 가 다 깔린 후 Windows를 설치합니다.

    3. fdisk 로 active partition 을 OSX 파티션으로 바꾸면 OSX 로 부팅됩니다.

    너무 간단해서 뭔가 이상한가요? 사실 2번은 위의 대전제를 엎고 시작합니다. GPT 파티션에 그냥 Windows를 설치한다고 하니까요. Microsoft 기술문서에도 저건 보통 안된다고 나와있고, 비스타나 XP 를 설치하려고 할 때, "GPT 디스크에는 설치할 수 없습니다." 라는 에러를 보신 분들도 있을겁니다.

    저기서 마법은, OSX 에서 디스크 유틸리티로 파티셔닝을 한다는 겁니다. 디스크 유틸리티는 hybrid MBR을 지원하고, 저기서 Boot Camp 용으로 파티셔닝 되어있다는 이야기는 지금 hybrid MBR 이 적용되어 있다는 의미입니다.



    *** Hybrid MBR & gptsync ***

    여기서 hybrid MBR 이 뭔지 짚고 넘어가죠. 사실 GPT는 MBR이 들어가는 자리를 사용하지 않고 남겨둡니다. 그리고 거기다가 MBR 파티셔닝 방식으로, "이 디스크는 통째로 GPT가 사용하고 있습니다." 라고 기록해두죠.

    hybrid MBR은, 현재 GPT로 파티셔닝된 정보를 MBR 파티셔닝 방법으로도 기록해두는걸 뜻합니다. 이 방법을 사용하면 GPT가 지원하는 프로그램에서 보면 GPT 디스크지만, MBR만 지원하는 프로그램에서 보면 MBR 디스크로 보이는거죠. 그래서 윈도우를 설치할 수 있는겁니다.

    OSX의 디스크 유틸리티는 기본적으로 hybrid MBR을 지원합니다. 그래서 저 1,2,3 방법이 먹히는거고요. 하지만 어떤 이유로든 (주로 리눅스 파티셔닝 툴을 쓸때 발생하는 문제입니다만) GPT 파티셔닝과 MBR 파티셔닝 정보가 어긋나게 되면 큰일이 납니다. 파티션 테이블이 깨진거니까요. 부팅이 안될수도 있고, 다른 파티션의 데이터를 덮을수도 있습니다. 따라서 파티션 관련 작업을 한 후엔 gptsync 프로그램을 사용하여 GPT 정보를 MBR 로 동기화 시켜주는것이 좋습니다.

    Ubuntu Linux 같은 경우는 sudo install gptsync 명령어를 통해 gptsync 프로그램을 설치할 수 있습니다. 설치 후, sudo gptsync /dev/sda 라고 하면 sda 디스크의 GPT 정보를 MBR 로 동기합니다.

    OSX 용 gptsync 는 http://www.insanelymac.com/forum/index.php?showtopic=177505 여기서 다운받을 수 있습니다. 전 이 gptsync 를 더 좋아하는데요, 이 enhanced 0.2 버젼은 어떤 파티션을 MBR로 동기화할지 정할 수 있기 때문입니다.

    예를 들어, 제 디스크는 GPT로 4개의 파티션이 있습니다. Windows 파티션, Linux 파티션, OSX 파티션, 데이터 파티션. 데이터 파티션은 FAT32로 포맷되어 있어 설치된 모든 OS 에서 자유롭게 자료를 저장할 수 있습니다.

    아참, 저 표에서 MBR은 primary partition 이 4개밖에 안된다고 그랬죠? 그런데 사실 GPT 파티션엔 맨 앞에 200M짜리 EFI 파티션이 하나 생깁니다. 그럼 총 5개네요. 그러면 앞부터 선착순으로 하면 데이터 파티션은 MBR 에 동기화시켜줄 수 없어요. 이게 일반적인 gptsync 의 방식입니다.

    하지만 저 OSX용 enhanced gptsync 는 동기화 시킬 파티션 지정이 가능합니다. sudo gptsync /dev/rdisk0  2 4 5+ 라고 명령어를 주면, OSX HFS+ 파티션은 빼고 데이터 파티션을 포함해 동기화를 시킵니다. 그러면 윈도에서 데이터 파티션을 접근할 수 있지요. 물론 빼먹은 OSX 파티션은 "할당하지 않은 공간" 으로 표시됩니다. 건드리면 큰일나요!

    diskutil list 하면 현재 파티션 번호 및 상태를 볼수 있다. 파티션 번호 뒤에 + 를 붙이면 Active 파티션이 된다. (윈도 파티션에 해줄것)

    (표에 있는것처럼 XP 64bit, Vista+ 에서는 GPT 파티션 인식이 가능합니다. 하지만 hybrid MBR 파티션 정보가 있는 경우는 MBR 파티션으로 인식합니다.)


    *** 다시 요약 ***

    정리하면, 솔직히 GPT 사용해서 그렇게 부귀영화를 누릴 수 있는것은 아닙니다. OSX 쓰는 입장에서 1. 오리지날과 뭔가 비슷하다는 느낌, 2. 파티션 크기 조절이 가능하다는것, 3. OSInstall 파일을 패치할 필요가 없다는것 정도가 실질적 장점이겠죠. 2T 이상 파티션 쓰거나 하지 않는다면 말에요.

    위 장점이 그다지 필요없고 윈도우를 같이 쓴다면, 속편하게 MBR partition scheme 를 사용하시는것이 좋습니다. 일단 깔리고 나면 잘 돌아가니까요.

    Linux 는 MBR, GPT 군말없이 잘 깔리고 지원하기는 합니다. 다만 Linux의 파티션 유틸리티를 사용하면 hybrid MBR 정보가 전부 날아가요. gptsync 를 꼭 해줘야 합니다.

    표에 있는것처럼 OSX, Linux 공통으로 fdisk 커맨드는 MBR을 작업합니다. GPT 작업은 다른 유틸리티를 사용하고요. active(boot flag) 정보가 서로 다를 수 있으니 주의하세요. 경험상 Vista의 부트로더는 hybrid MBR 에서 지정되어있는 boot partition 으로 부팅합니다.


    http://refit.sourceforge.net/myths/ 여기에 GPT, EFI 에 대한 진실 혹은 거짓이 잘 정리되어있습니다. 대부분의 오해와 진실을 정확하게 알기 좋죠. 다만, GRUB이 GPT 를 인식 못한다는건 GRUB1 이야기고, GRUB2는 GPT를 잘 지원합니다.



    망가진 윈도 부트 영역 복구법
    1) 윈도우7 부팅이 되지않는 PC에  윈도우7 CD를 넣어서 부팅
    2) 설치초기화면에서 shift +  F10 눌러서 CMD창을 띄운다
    3) bcdboot c:\windows /s c:\ /l ko-KR  명령을 실행한다.

    C:\> diskpart
    DISKPART> list disk
    DISKPART> select disk 0
    DISKPART> list partition
    DISKPART> select partition 4
    DISKPART> active


    4) 리부팅한다.  ^^


    잘안되면 아래로
    1) 윈도 7 CD로 부팅
    2) 키보드 언어 설정후 / 하단의 복구 선택 -> 첫번째 복구 유틸 사용 선택 -> 시동 복구 선택
    3) 리부팅