From Fedora Project Wiki
m
Line 1: Line 1:
 
{{autolang}}
 
{{autolang}}
  
{{admon/note|新软件和文档|FedUp 是随 Fedora 18 而来的一款新软件,因而将在 Fedora 18 发布之前不断完善。如果您发现本文档有错误或是过期了,请修正它或者报告给相关人员。}}
+
{{admon/note|这是新东西!|FedUp 是随 Fedora 18 而来的一个新系统,因而将在 Fedora 18 发布之前不断完善。如果您发现本文档有错误或是过期了,请修正它或者报告给相关人员。}}
  
 +
{{admon/warning|安全考虑|当您通过网络升级时,FedUp 还不确保只有从 Fedora 获取的受信任软件正在系统上运行。具体请查看 [[rhbug:877623|Bugzilla: #877623]]。You can download the ISO release image and verify the authenticity independently before perfoming a upgrade with Fedup via media or ISO images methods to workaround this issue.  Note that neither Anaconda not Preupgrade verified the authenticity of the source either and this is not a regression. }}
  
{{admon/caution|Upgrading before F18 GA|Some parts of fedup rely on variables which are not set until Fedora 18 is released. There are other side-effects of upgrading before GA (currently scheduled for 2013-01-15) which can cause minor issues on your system including not upgrading the kernel and not upgrading various Fedora 17 packages. This does not mean that the upgrade didn't work - you'll just have to either update to updates-testing or wait until the Fedora 18 updates repo is populated}}
+
= 什么是 FedUp? =
  
{{admon/warning|Security Considerations| FedUp does not yet ensure that only trusted software from Fedora is run on your system when you are doing upgrade over the network.  Refer to [[rhbug:877623|Bugzilla: #877623]] for more details.  You can download the ISO release image and verify the authenticity independently before perfoming a upgrade with Fedup via media or ISO images methods to workaround this issue.  Note that neither Anaconda not Preupgrade verified the authenticity of the source either and this is not a regression. }}
+
FedUp (FEDora UPgrader) 是一个升级 Fedora 的新工具。它已替换了所有在之前 Fedora 版本上推荐的更新方式(例如通过 [[PreUpgrade]] 升级和 DVD 升级)。Anaconda,Fedora 的安装器,从 Fedora 18 后将不会自带更新功能,所有全部交给 FedUp。
  
= What is FedUp? =
+
目前,FedUp 可以通过网络安装源完美升级 Fedora 17 至 Fedora 18,类似于之前 [[PreUpgrade]] 的工作方式。更多升级的方法目前已经处于计划之中,当它们可行后本页也会继续更新。
  
FedUp (FEDora UPgrader) is the name of a new system for upgrading Fedora installs in Fedora 18 and above releases. It replaces all of the currently recommended upgrade methods ([[PreUpgrade]] and DVD) that have been used in previous Fedora releases.  Anaconda, the Fedora installer does have not any in-built upgrade functionality in Fedora 18 or above releases.  It has been completely delegated to Fedup.
+
{{admon/warning|针对 Fedora 16 和更老的版本|FedUp 客户端尚未在任何早于 Fedora 17 的系统上构建或运行。如果您想更新,请首先[[Upgrade|'''更新''']]Fedora 17。}}
  
Currently, FedUp is capable of upgrading Fedora 17 installs to Fedora 18 using a networked repository, similar to how [[PreUpgrade]] worked. More methods for upgrade are currently planned and this page will be updated as those features are completed.
+
= FedUp 做了些什么? =
  
{{admon/warning|Fedora 16 and Older|The FedUp client does not build or run on anything older than Fedora 17. If you want to upgrade an older Fedora installation, please [[Upgrade|upgrade]] to Fedora 17 before continuing.}}
+
FedUp 系统有两个组成部分 - 客户端被用作下载软件包并准备升级和预启动环境,实际更新工作由 [[Systemd|systemd]] 和 yum 完成。详细信息请访问 [http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ FedUp 主作者对它的介绍] 页面。
  
= What Does FedUp do? =
+
== FedUp 客户端 ==
  
The FedUp system consistes of two parts - the client used to download packages and prepare for the upgrade and a pre-boot environment which does the actual upgrade using [[Systemd|systemd]] and yum. More details are available in [http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ a blog post written by FedUp's primary author]
+
FedUp 运行于准备升级的系统上。它获取所有需要升级的软件包和内核。目前只有命令行版本,不过图形界面版本已经在准备了。
  
== The FedUp Client ==
+
== 升级过程 ==
  
The FedUp client runs on the system to be upgraded. It gathers the packages needed for upgrade in addition to downloading the required initramfs and kernel needed for the actual upgrade. At this time, only the fedup command-line interface is implemented but a GUI interface is expected before Fedora 18 is released.
+
从运行 FedUp 客户端之后重启开始实际上的升级。文件系统会在启动时被挂载,已下载的包会被安装并且一些有关升级的任务也会开始执行。在升级过程中,将会使用一个特别的包含升级进度条显示的 plymouth 主题。
  
== The Upgrade ==
+
= 常见问题解答 =
 +
== 我能使用 FedUp 更新我的 Fedora 16 吗? ==
 +
不行。目前不可用。FedUp 客户端目前尚未在 Fedora 16 上构建或运行,所以您至少需要 Feora 17。请首先使用 Preupgrade 升级至 Fedora 17。
  
The actual upgrade takes place when the system has been rebooted after running the FedUp client. The filesystems are mounted during boot, the already downloaded packages are installed and some upgrade-related tasks are performed. During the upgrade process, a special plymouth theme is used which has a progress bar to indicate current upgrade progress.
+
== 我该如何汇报升级出现的问题? ==
 +
这取决于您出现的问题。
  
= Frequently Asked Questions =
+
===升级准备时的问题 ===
== Can I upgrade a Fedora 16 system with FedUp? ==
+
如果您在重启前使用 FedUp 客户端遇到问题({{package|fedup}}),请搜索之前有关 fedup 的 bug,或者针对您'''升级前系统的版本'''提交。
No, this is not currently possible. The FedUp client does not currently build or run on Fedora 16 and you need to be running at least Fedora 17 in order to run the client.  If you are upgrading from Fedora 16, use Preupgrade to upgrade to Fedora 17 first.
 
  
== How do I report issues that I find with upgrades? ==
+
=== 升级过程中的问题 ===
The answer to this depends on the exact issue that you hit.
 
 
 
=== Issues with upgrade preparation ===
 
If you hit issues when using the FedUp client ({{package|fedup}}) before reboot, search for or file a bug against fedup using the version you are upgrading '''from'''.
 
 
 
=== Issues During Upgrade ===
 
 
If you hit issues after upgrade preparation and the initial reboot, search for or file a bug against {{package|fedup-dracut}} using the version you are upgrading '''to'''.
 
If you hit issues after upgrade preparation and the initial reboot, search for or file a bug against {{package|fedup-dracut}} using the version you are upgrading '''to'''.
  
=== Issues After Upgrade ===
+
=== 升级后的问题 ===
 
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.
 
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.
  
== How do I Debug Issues During Upgrade ==
+
== 我该如何在升级过程中调试出现的问题 ==
 
A troubleshooting and debug guide will be written soon and linked to from here.
 
A troubleshooting and debug guide will be written soon and linked to from here.
  
Line 50: Line 47:
 
This is a planned feature. See [https://bugzilla.redhat.com/show_bug.cgi?id=877623 Bug 877623] for a status update.
 
This is a planned feature. See [https://bugzilla.redhat.com/show_bug.cgi?id=877623 Bug 877623] for a status update.
  
== Where can I ask Questions ==
+
== 哪里可以问我的问题? ==
 
For now, the best place to ask questions is probably #fedora-qa on Freenode IRC or the [https://admin.fedoraproject.org/mailman/listinfo/test Fedora Test list].
 
For now, the best place to ask questions is probably #fedora-qa on Freenode IRC or the [https://admin.fedoraproject.org/mailman/listinfo/test Fedora Test list].
  
= How Can I Upgrade My System with FedUp? =
+
= 我如何使用 FedUp 更新我的系统? =
  
 
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.
 
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.
  
== Preparing for the Upgrade ==
+
== 升级准备 ==
 
{{admon/important|Latest fedup|Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-01-08), that is fedup-0.7.2-1.fc17}}
 
{{admon/important|Latest fedup|Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-01-08), that is fedup-0.7.2-1.fc17}}
 
# Do a full system update and reboot to ensure that any kernel changes are running
 
# Do a full system update and reboot to ensure that any kernel changes are running
Line 65: Line 62:
 
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc.).
 
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc.).
  
=== Network ===
+
=== 网络 ===
 
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.
 
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.
 
{{admon/caution|Upgrading Before F18 Final GA|If you're following these instructions before F18 goes GA (currently scheduled for 2013-01-15), you '''do''' need to use the --instrepo argument as shown here. You may also end up with many fc17 packages on your system after upgrade - this is not a bug with fedup but a side effect of the release process. Once F18 goes GA, the updates repository will be available and this problem should go away}}
 
  
 
# Start the upgrade prep by executing following command
 
# Start the upgrade prep by executing following command
#* {{command|sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/alt/qa/fedup/f18-RC4/<arch>/}}
+
#* {{command|sudo fedup-cli --network 18 --debuglog fedupdebug.log}}
 
#* <arch> is the arch of the system that you are upgrading - either i386 or x86_64
 
#* <arch> is the arch of the system that you are upgrading - either i386 or x86_64
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
  
=== ISO File ===
+
=== ISO 文件 ===
 
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-18.iso but you will need to replace all instances of that path with the actual path of the iso. Updates will be pulled in if you have network access on the machine to be upgraded.
 
In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-18.iso but you will need to replace all instances of that path with the actual path of the iso. Updates will be pulled in if you have network access on the machine to be upgraded.
  
# Download the {{FedoraVersion}} iso appropriate for the arch that you are running
+
# 下载适合您正运行的架构的 Fedora {{FedoraVersion}} 的 ISO 文件。
 
#* For the sake of example, we will assume that the iso exists at {{filename|/home/user/fedora-18.iso}} but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO.
 
#* For the sake of example, we will assume that the iso exists at {{filename|/home/user/fedora-18.iso}} but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO.
 
# Start the upgrade prep by executing the following command
 
# Start the upgrade prep by executing the following command
Line 84: Line 79:
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
  
=== Other Device ===
+
=== 其他设备 ===
 
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.
 
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.
  
Line 93: Line 88:
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
 
# Once the preparations have completed, check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}}
  
== Executing the Upgrade ==
+
== 执行升级 ==
 
{{admon/warning|Needs Reference|This section still needs a reference to the 'esc kills plymouth' bug once a suitable summary has been written}}
 
{{admon/warning|Needs Reference|This section still needs a reference to the 'esc kills plymouth' bug once a suitable summary has been written}}
  
Line 104: Line 99:
 
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu
 
# Once the upgrade process has completed, the system will reboot and an option to boot {{FedoraVersion|long|next}} will be on the grub menu
  
== GRUB Updates ==
+
== GRUB 更新 ==
 
{{admon/note|Somewhat Optional|While updating GRUB on your upgraded system isn't strictly required, it is recommended for BIOS systems and '''very strongly''' recommended for UEFI systems due to the transition from grub-efi to grub2-efi}}
 
{{admon/note|Somewhat Optional|While updating GRUB on your upgraded system isn't strictly required, it is recommended for BIOS systems and '''very strongly''' recommended for UEFI systems due to the transition from grub-efi to grub2-efi}}
  
=== Updating GRUB2 (BIOS systems) ===
+
=== 更新 GRUB2 (BIOS 系统) ===
  
 
* After upgrade, the grub2 you're booting from will still be the F17 version; upgrading must be done manually
 
* After upgrade, the grub2 you're booting from will still be the F17 version; upgrading must be done manually
 
* Follow the steps in [[GRUB_2|this grub2 page]] to reinstall and update grub
 
* Follow the steps in [[GRUB_2|this grub2 page]] to reinstall and update grub
  
=== Updating GRUB (UEFI systems) ===
+
=== 更新 GRUB (UEFI 系统) ===
 
{{admon/note|Problems Upgrading Grub on UEFI|Late in testing, we found some potentially serious problems with manually upgrading grub-efi to grub2-efi. Until this is figured out, we recommend that users continue to use grub-efi as it should work for the near future}}
 
{{admon/note|Problems Upgrading Grub on UEFI|Late in testing, we found some potentially serious problems with manually upgrading grub-efi to grub2-efi. Until this is figured out, we recommend that users continue to use grub-efi as it should work for the near future}}
 
<!-- This is commented out due to some problems found late in testing fedup on EFI, will modify once this gets worked out
 
<!-- This is commented out due to some problems found late in testing fedup on EFI, will modify once this gets worked out
Line 162: Line 157:
 
-->
 
-->
  
== Cleaning Up Post Upgrade ==
+
== 清理 ==
  
 
{{admon/warning|Pending|This part of the documentation is still being written }}
 
{{admon/warning|Pending|This part of the documentation is still being written }}
 
<!-- Some of the stuff from [http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup this post upgrade cleanup guide] might be wise -->
 
<!-- Some of the stuff from [http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup this post upgrade cleanup guide] might be wise -->
 
= Docs TODO =
 
* Write fedup troubleshooting and debug guide
 
* add details for secureboot/shim installation
 
* write commonbugs entries and link to them from this page
 
* add note about blob drivers if needed
 
* add notes about how to use other repos or link to discussion/instructions
 

Revision as of 06:34, 16 January 2013

Note.png
这是新东西!
FedUp 是随 Fedora 18 而来的一个新系统,因而将在 Fedora 18 发布之前不断完善。如果您发现本文档有错误或是过期了,请修正它或者报告给相关人员。
Warning.png
安全考虑
当您通过网络升级时,FedUp 还不确保只有从 Fedora 获取的受信任软件正在系统上运行。具体请查看 Bugzilla: #877623。You can download the ISO release image and verify the authenticity independently before perfoming a upgrade with Fedup via media or ISO images methods to workaround this issue. Note that neither Anaconda not Preupgrade verified the authenticity of the source either and this is not a regression.

什么是 FedUp?

FedUp (FEDora UPgrader) 是一个升级 Fedora 的新工具。它已替换了所有在之前 Fedora 版本上推荐的更新方式(例如通过 PreUpgrade 升级和 DVD 升级)。Anaconda,Fedora 的安装器,从 Fedora 18 后将不会自带更新功能,所有全部交给 FedUp。

目前,FedUp 可以通过网络安装源完美升级 Fedora 17 至 Fedora 18,类似于之前 PreUpgrade 的工作方式。更多升级的方法目前已经处于计划之中,当它们可行后本页也会继续更新。

Warning.png
针对 Fedora 16 和更老的版本
FedUp 客户端尚未在任何早于 Fedora 17 的系统上构建或运行。如果您想更新,请首先更新到 Fedora 17。

FedUp 做了些什么?

FedUp 系统有两个组成部分 - 客户端被用作下载软件包并准备升级和预启动环境,实际更新工作由 systemd 和 yum 完成。详细信息请访问 FedUp 主作者对它的介绍 页面。

FedUp 客户端

FedUp 运行于准备升级的系统上。它获取所有需要升级的软件包和内核。目前只有命令行版本,不过图形界面版本已经在准备了。

升级过程

从运行 FedUp 客户端之后重启开始实际上的升级。文件系统会在启动时被挂载,已下载的包会被安装并且一些有关升级的任务也会开始执行。在升级过程中,将会使用一个特别的包含升级进度条显示的 plymouth 主题。

常见问题解答

我能使用 FedUp 更新我的 Fedora 16 吗?

不行。目前不可用。FedUp 客户端目前尚未在 Fedora 16 上构建或运行,所以您至少需要 Feora 17。请首先使用 Preupgrade 升级至 Fedora 17。

我该如何汇报升级出现的问题?

这取决于您出现的问题。

升级准备时的问题

如果您在重启前使用 FedUp 客户端遇到问题(Package-x-generic-16.pngfedup),请搜索之前有关 fedup 的 bug,或者针对您升级前系统的版本提交。

升级过程中的问题

If you hit issues after upgrade preparation and the initial reboot, search for or file a bug against Package-x-generic-16.pngfedup-dracut using the version you are upgrading to.

升级后的问题

If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.

我该如何在升级过程中调试出现的问题

A troubleshooting and debug guide will be written soon and linked to from here.

Does FedUp verify the software it runs or installs during upgrade?

This is a planned feature. See Bug 877623 for a status update.

哪里可以问我的问题?

For now, the best place to ask questions is probably #fedora-qa on Freenode IRC or the Fedora Test list.

我如何使用 FedUp 更新我的系统?

As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.

升级准备

Important.png
Latest fedup
Make sure that you install the latest version of the fedup client on the system to be upgraded. At the time of this writing (2013-01-08), that is fedup-0.7.2-1.fc17
  1. Do a full system update and reboot to ensure that any kernel changes are running
  2. Install Package-x-generic-16.pngfedup
    • Be sure to get the latest release, this may involve enabling updates-testing (put --enablerepo=updates-testing between yum and install on the command line)

There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc.).

网络

Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.

  1. Start the upgrade prep by executing following command
    • sudo fedup-cli --network 18 --debuglog fedupdebug.log
    • <arch> is the arch of the system that you are upgrading - either i386 or x86_64
  2. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup-cli

ISO 文件

In order to use an ISO file, it needs to exist locally on the filesystem of the system to be upgraded. The documentation is written as if that file is /home/user/fedora-18.iso but you will need to replace all instances of that path with the actual path of the iso. Updates will be pulled in if you have network access on the machine to be upgraded.

  1. 下载适合您正运行的架构的 Fedora 31 的 ISO 文件。
    • For the sake of example, we will assume that the iso exists at /home/user/fedora-18.iso but it can be anwhere in the filesystem as long as you alter the path below to reflect the actual location of the ISO.
  2. Start the upgrade prep by executing the following command
    • sudo fedup-cli --iso /home/user/fedora-18.iso --debuglog=fedupdebug.log
  3. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup-cli

其他设备

Optical drives and other mountable storage can also be used as a package source for upgrade preparations.

  1. Mount the source material
    • For the sake of example, we will assume that this source is mounted at /mnt/fedora but you can mount it anywhere as long as you replace /mnt/fedora in the command below with the actual mounted location of the upgrade source.
  2. Start the upgrade preparations by executing the following command
    • sudo fedup-cli --device /mnt/fedora --debuglog=fedupdebug.log
  3. Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup-cli

执行升级

Warning.png
Needs Reference
This section still needs a reference to the 'esc kills plymouth' bug once a suitable summary has been written
  1. Reboot the system if fedup has completed without error.
  2. Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade.
    • Adding rd.upgrade.debugshell would be a decent idea
  3. Select the System Upgrade option from the GRUB menu
  4. The system should boot into the upgrade process and a plymouth boot screen should be displayed
    • If you press 'esc', a more detailed log of progress will be desplayed but if you switch back to the graphical progress indicator, it will remain at 0% for the remainder of the upgrade but that does not mean the upgrade has stopped. See Need section reference here once it's written
  5. Once the upgrade process has completed, the system will reboot and an option to boot Fedora 32 will be on the grub menu

GRUB 更新

Note.png
Somewhat Optional
While updating GRUB on your upgraded system isn't strictly required, it is recommended for BIOS systems and very strongly recommended for UEFI systems due to the transition from grub-efi to grub2-efi

更新 GRUB2 (BIOS 系统)

  • After upgrade, the grub2 you're booting from will still be the F17 version; upgrading must be done manually
  • Follow the steps in this grub2 page to reinstall and update grub

更新 GRUB (UEFI 系统)

Note.png
Problems Upgrading Grub on UEFI
Late in testing, we found some potentially serious problems with manually upgrading grub-efi to grub2-efi. Until this is figured out, we recommend that users continue to use grub-efi as it should work for the near future

清理

Warning.png
Pending
This part of the documentation is still being written