메인 콘텐츠로 건너뛰기
블로그 리눅스 아치 리눅스 템플릿 업데이트

아치 리눅스 템플릿 업데이트

업데이트된 아치 리눅스(Arch Linux 2012.07) 배포 템플릿이 Linode Manager 내에서 즉시 배포할 수 있음을 발표하게 되어 기쁩니다. 새 템플릿에는 '/lib'를 심링크로 변경하는것이 포함된 최신 시스템 업데이트가 설치되어 있습니다. Linode 관리자 내에서 배포에 대한 자세한 내용은 Linode 라이브러리에서 이 문서를 참조하세요.

Arch Linux의 새 배포의 경우 처음으로 사용하려고 시도하기 전에 pacman 키링을 초기화해야 합니다.  또한 아치 리눅스를 배포하는 모든 사용자가 아치 리눅스 뉴스 아카이브에눈을 유지하는 것이 좋습니다. 완료하려면 일정 수준의 수동 개입이 필요할 수 있는 새 업데이트에 관한 정보가 아카이브에 제공됩니다.

우리는 당신이 업데이트 된 아치 리눅스 템플릿을 즐길 수 있기를 바랍니다!

- 팀

댓글 (14)

  1. Author Photo

    Very cool! It can be a pain to deploy/update a new Arch install if it has been a long time since the package snapshot.

  2. Author Photo

    Awesome, thank you! You guys must have read my mind (or you’ve been looking at the logs), as I was just encountering issues with installing from the old image last night. Especially with the recent changes to glibc, updating a new Arch node seemed to be quite broken.

    Keeping the template fairly up-to-date is important in a rolling release distro, especially when we are not able to do a typical netinstall.

    I was just about to post a bug/feature request, and then noticed this post.

  3. Author Photo
  4. Author Photo

    Awesome stuff Linode! Do keep up the great stuff!

  5. Author Photo

    For new deployments of Arch Linux, you will need to initialize the pacman keyring before attempting to use it for the first time.

  6. Author Photo

    Great, Linode, superb as always!
    Now, for all you archers out there. A shell script that will generate entropy, initialize and populate the keyring.
    http://linux.vrnw.org/arch/scripts/pacman_key_init.sh
    The idea for this script was inspired by a forum post.
    http://forum.linode.com/viewtopic.php?t=9143&p=52602#p52574

    Enjoy!

  7. Author Photo

    Hey,

    You may want to make the following adjustment to your script:

    “mandb > /dev/null 2>1” becomes “mandb 2>&1 > /dev/null”

    The 2>&1 redirection needs to come first so that both go to /dev/null, and it needs the ampersand to redirect properly.

  8. Author Photo

    Hi,
    Done, although, I never saw where the ampersand was supposed to go. It should work better now, though.

  9. Author Photo

    Hi Blake,

    Wouldn’t running mandb in a loop produce terrible entropy? From what I’ve understood, the idea is to gather something so long and random that it’s not easily guessable (like input from someone banging on the keyboard like a monkey and disk timings from regular use).

    I am not a cryptoanalist, but in theory at least, if every Arch user ran the same mandb command on the same set of manpages, they would get the same or somehow similar keys, right? That can’t be good.

    Wander

  10. Author Photo

    Wander:

    Running mandb or similar commands like that isn’t pumping output from mandb or whatever command you run into your /dev/random; the idea is to cause lots of system activity from which entropy is drawn. The nature of the activity is largely irrelevant, as the entropy is drawn from the system *doing things*, not piped in directly from what it’s doing.

  11. Author Photo

    “The 2>&1 redirection needs to come first so that both go to /dev/null, and it needs the ampersand to redirect properly.”

    This is incorrect. The following redirects both stdout and stderr to /dev/null:

    mandb > /dev/null 2>&1

    Any Bourne shell variant (bash, dash, etc.) will read this line as “redirect stdout to /dev/null, and redirect stderr to wherever stdout is being sent”.

  12. Author Photo

    Hi,
    I updated the script as of three, four weeks ago when I realized your statement was correct, though hadn’t been posted at the time. The script, as it is now, will redirect correctly.

  13. Author Photo

    Does the current image handle the switch to systemd?

  14. Author Photo

    Stephen Tanner:

    The current image uses systemd by default, so no switch is necessary.

    Blake

댓글 남기기

이메일 주소는 게시되지 않습니다. 필수 필드가 표시됩니다 *