English Korean
System Utilities 시스템 유틸리티
Legacy GTK+ interface removed from Wireshark 와이어샤크에서 제거된 레거시 GTK+ 연결장치
Since release 2.0, the [application]*Wireshark* network protocol analyzer came with two graphical user interfaces - a legacy one in GTK+ and a new one using Qt. In this release, the legacy GTK+ interface has been removed and the developers are focusing on the actively maintained Qt-based interface, which allows them to bring in new updates. 출시 2.0 이후로, [application]*Wireshark* 네트워크 통신규약 분석기는 두 가지 사용자 연결장치와 함께 제공됩니다 - GTK+에서 레거시 인터페이스와 Qt를 사용하는 새로운 연결장치. 이와 같은 출시에서, 레거시 GTK+ 연결장치가 제거되었으며 개발자는 새로운 최신화를 가져올 수 있도록 적극적으로 유지 관리되는 Qt-기반 연결장치에 집중하고 있습니다.
Users will not be particularly affected by the removal of the legacy GUI as both interfaces look and behave the same even though the frameworks are different. 사용자는 프레임워크가 다를지라도 양쪽 연결장치가 동일하게 보이고 동작하므로 레거시 GUI를 제거해도 특별히 영향을 받지 않습니다.
See the link:++https://www.wireshark.org/docs/relnotes/++[upstream release notes] for additional information. 추가 정보를 위해 ink:++https://www.wireshark.org/docs/relnotes/++[업스트림 출시 기록]을 참고하세요.
tzdata transition to the vanguard format 뱅가드(vanguard) 형식으로 tzdata 전이
Starting with Fedora 29, the `tzdata` package, which contains rules for world time zones, is using the `vanguard` data format by default. This format was introduced in `tzdata` version `2018d` and became default in version `2018e` which is the default version in Fedora 29. This format includes POSIX-compliant implementations of negative DST offsets, which have previously been a problem for both Java and ICU parsers.
If you have any programs which parse `tzdata` files, make sure they are updated to be able to parse the new format. If you dump time zone data with `zdump`, you will now see negative DST offsets where applicable.
Additionally, `tzdata-2018e` changes the North Korea time zone from UTC+8:30 to UTC+9 as of May 5, 2018. 추가적으로, `tzdata-2018e`은 2018년 5월 5일 북한 시간 대역이 UTC+8:30에서 UTC+9으로 변경합니다.
GRUB menu hidden by default 기본설정으로 숨겨진 GRUB 메뉴
The GRUB boot loader is now configured to hide the boot menu by default if Fedora is the only operating system installed and if the previous boot succeeded. This results in a smoother boot experience on such systems. GRUB 부트로더는 이제 만약 페도라가 설치된 유일한 운영 체제이고, 이전 부트가 성공한 경우에 기본으로 부트 메뉴를 숨기도록 구성됩니다. 이는 이와 같은 시스템에서 더 부드러운 부트 경험을 갖도록 합니다.
To display the boot menu in order to boot an older or rescue kernel, you can now do one of the following: 이전 커널 또는 복구 커널로 부트하기 위해 부트 메뉴를 표시 하려면, 당신은 이제 다음 중 하나를 수행 할 수 있습니다:
Press the kbd:[Esc] key (this was also possible before this update). kbd:[Esc] 키를 눌러주세요 (이는 또한 이 최신화 전에 사용 할 수 있었습니다).
Press kbd:[F8] (the same key which also displays the Windows boot menu). kbd:[F8]을 눌러주세요 (윈도우 부트 메뉴도 표시하는 동일한 키 ).
Hold kbd:[Shift] during boot (you can hold the key down instead of trying to find the right time to press the key; additionally this is the same approach Ubuntu uses which makes it more discoverable).
The auto-hide functionality is automatically enabled on all new Fedora Workstation installations. Older installations will keep their original settings. To disable this function, use run the [command]#sudo grub2-editenv - unset menu_auto_hide# command in a terminal.
For additional information, see the link:++https://hansdegoede.livejournal.com/19224.html++[announcement post]. 추가 정보를 위하여, link:++https://hansdegoede.livejournal.com/19224.html++[공지글]을 참고하세요.
Stratis Storage 1.0 Stratis Storage 1.0
Fedora 29 provides version 1.0 of *Stratis Storage*, a local storage management solution. This will allow further testing and user feedback that will guide the development and stabilization of Stratis, and let us consider future integration into Anaconda and other more critical aspects of Fedora.
Stratis is a local storage system akin to *Btrfs*, *ZFS*, and *LVM*. Its goal is to enable easier setup and management of disks and SSDs, as well as enabling the use of advanced storage features such as thin provisioning, snapshots, integrity, and a cache tier without requiring expert-level storage administration knowledge. Furthermore, Stratis includes monitoring and repair capabilities, and a programmatic API, for better integration with higher levels of system management software.