Difference between revisions of "Boot Manager/9.2/de"

From PC-BSD Wiki
Jump to: navigation, search
(Updating to match new version of source page)
Line 2: Line 2:
 
{{NavHeader/de|back=Active Directory & LDAP|forward=Hardware Compatibility|custompagename=Boot-Verwaltung}}</noinclude>
 
{{NavHeader/de|back=Active Directory & LDAP|forward=Hardware Compatibility|custompagename=Boot-Verwaltung}}</noinclude>
  
 +
THIS PAGE NEEDS UPDATING
  
'''Abbildung 8.4a: Verwalten von Boot-Umgebungen'''
+
PC-BSD® supports a feature of ZFS known as multiple boot environments (BEs). With multiple boot environments, the process of updating software becomes a low-risk operation as you can backup your current boot environment before upgrading or making software updates to your system. If needed, you also have the option of booting into a backup boot environment. For example:
 +
 
 +
'''Abbildung 8.4b: Verwalten der GRUB-Konfiguration'''
 +
 
 +
[[File:Boot3.png]]
 +
 
 +
* you can save multiple boot environments on your system and perform various updates on each of them as needed. For example, you can clone a boot environment by using the '''beadm create''' command. A clone is a bootable copy of a boot environment. You can install, test, and update different software packages on the original boot environment and on its clone.
 +
 
 +
* although only one boot environment can be active at a time, you can mount an inactive boot environment using the '''beadm mount''' command. You could then '''chroot''' into the mount point in order to update specific packages on the mounted environment.
 +
 
 +
* you can move a boot environment to another machine, physical or virtual, in order to check hardware support.
 +
 
 +
{{warning|icon64=for boot environments to work properly, ''' ''do not change the default ZFS layout during installation.'' ''' The default ZFS layout ensures that when you create multiple boot environments, the ''/usr/pbi/'', ''/usr/local/'', ''/usr/home/'', ''/usr/ports/'', ''/usr/src/'' and ''/var/'' directories remain untouched. This way, if you rollback to a previous boot environment, you will not lose data in your home directories, any installed applications, or downloaded src or ports.}}
 +
 
 +
=== Managing Boot Environments ===
 +
 
 +
Boot environments are managed with the '''beadm''' command which must be run as the superuser. The following example creates a BE named ''beforeupgrade''. The new BE is a clone of the current BE, the ZFS environment that you booted into.
 +
 
 +
{{txtbox|box='''beadm create beforeupgrade'''
 +
Created successfully}}
 +
 
 +
To view all BEs, use the '''list''' command
 +
 
 +
{{txtbox|box='''beadm list'''
 +
BE            Active Mountpoint Space Policy Created
 +
default      NR    /          6.05G static 2012-07-09 05:06
 +
beforeupgrade -      -            1K static 2012-07-10 12:25
 +
|txt=
 +
The possible flags in the "Active" field are as follows:
 +
 
 +
* '''R:''' active on reboot
 +
 
 +
* '''N:''' active now
 +
 
 +
* '''-:''' inactive}}
 +
 
 +
In this example, the current BE is called ''default'', it is active now, and at next reboot; and it is mounted. The newly created ''beforeupgrade'' BE exists, but is inactive and unmounted. To activate the new BE:
 +
 
 +
{{txtbox|box='''beadm activate beforeupgrade'''
 +
Activated successfully
 +
'''beadm list'''
 +
BE            Active Mountpoint Space Policy Created
 +
default      N      /          64.5K static 2012-07-09 05:06
 +
beforeupgrade R      -          6.05G static 2012-07-10 12:25}}
 +
 
 +
The flags now indicate that the system is currently booted into ''default'', but at next boot the system will boot into ''beforeupgrade''. Only one boot environment can be active at a time.
 +
 
 +
'''Figure 8.4a: Managing Boot Environments'''
  
 
[[File:Boot1.png]]
 
[[File:Boot1.png]]
  
'''Abbildung 8.4b: Verwalten der GRUB-Konfiguration'''
+
'''Figure 8.4b: Managing GRUB Configuration'''
  
 
[[File:Boot3.png]]
 
[[File:Boot3.png]]

Revision as of 10:19, 23 August 2013


Vorherige: Active Directory & LDAP Zurück zum Inhaltsverzeichnis Nächste: Hardware Compatibility
Boot-Verwaltung

Contents


THIS PAGE NEEDS UPDATING

PC-BSD® supports a feature of ZFS known as multiple boot environments (BEs). With multiple boot environments, the process of updating software becomes a low-risk operation as you can backup your current boot environment before upgrading or making software updates to your system. If needed, you also have the option of booting into a backup boot environment. For example:

Abbildung 8.4b: Verwalten der GRUB-Konfiguration

Boot3.png

  • you can save multiple boot environments on your system and perform various updates on each of them as needed. For example, you can clone a boot environment by using the beadm create command. A clone is a bootable copy of a boot environment. You can install, test, and update different software packages on the original boot environment and on its clone.
  • although only one boot environment can be active at a time, you can mount an inactive boot environment using the beadm mount command. You could then chroot into the mount point in order to update specific packages on the mounted environment.
  • you can move a boot environment to another machine, physical or virtual, in order to check hardware support.


WARNUNG For boot environments to work properly, do not change the default ZFS layout during installation. The default ZFS layout ensures that when you create multiple boot environments, the /usr/pbi/, /usr/local/, /usr/home/, /usr/ports/, /usr/src/ and /var/ directories remain untouched. This way, if you rollback to a previous boot environment, you will not lose data in your home directories, any installed applications, or downloaded src or ports.

Managing Boot Environments

Boot environments are managed with the beadm command which must be run as the superuser. The following example creates a BE named beforeupgrade. The new BE is a clone of the current BE, the ZFS environment that you booted into.

beadm create beforeupgrade Created successfully

To view all BEs, use the list command

beadm list

BE Active Mountpoint Space Policy Created default NR / 6.05G static 2012-07-09 05:06

beforeupgrade - - 1K static 2012-07-10 12:25
The possible flags in the "Active" field are as follows:
  • R: active on reboot
  • N: active now
  • -: inactive

In this example, the current BE is called default, it is active now, and at next reboot; and it is mounted. The newly created beforeupgrade BE exists, but is inactive and unmounted. To activate the new BE:

beadm activate beforeupgrade

Activated successfully beadm list BE Active Mountpoint Space Policy Created default N / 64.5K static 2012-07-09 05:06

beforeupgrade R - 6.05G static 2012-07-10 12:25

The flags now indicate that the system is currently booted into default, but at next boot the system will boot into beforeupgrade. Only one boot environment can be active at a time.

Figure 8.4a: Managing Boot Environments

Boot1.png

Figure 8.4b: Managing GRUB Configuration

Boot3.png


Verweise


Other languages:German 9% • ‎English 100% • ‎French 20%