freebsd-update

  • Ersteller Gelöschtes Mitglied 73729
  • Erstellt am
G

Gelöschtes Mitglied 73729

Guest
Hallo zusammen,

komme leider bei einem Update nicht weiter. Kann mir bitte jemand weiterhelfen? Vielen Dank!

Code: 
# uname -r
10.1-RELEASE-p6

Code: 
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files will be updated as part of updating to 10.1-RELEASE-p9:
/bin/freebsd-version
/boot/boot1.efi
/boot/boot1.efifat
/boot/kernel/kernel
/boot/kernel/kernel.symbols
/usr/libexec/bsdinstall/zfsboot
/usr/sbin/ntpd

Code: 
# freebsd-update -r 10.1-RELEASE-p9 upgrade
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic world/base world/lib32

The following components of FreeBSD do not seem to be installed:
world/doc world/games

Does this look reasonable (y/n)? y

Fetching metadata signature for 10.1-RELEASE-p9 from update6.freebsd.org... failed.
Fetching metadata signature for 10.1-RELEASE-p9 from update5.freebsd.org... failed.
Fetching metadata signature for 10.1-RELEASE-p9 from update4.freebsd.org... failed.
Fetching metadata signature for 10.1-RELEASE-p9 from update2.freebsd.org... failed.
Fetching metadata signature for 10.1-RELEASE-p9 from update3.freebsd.org... failed.
No mirrors remaining, giving up.

Code: 
# more /etc/freebsd-update.conf
# $FreeBSD: releng/10.1/etc/freebsd-update.conf 258121 2013-11-14 09:14:33Z glebius $

# Trusted keyprint.  Changing this is a Bad Idea unless you've received
# a PGP-signed email from <security-officer@FreeBSD.org> telling you to
# change it and explaining why.
KeyPrint 800651ef4b4c71c27e60786d7b487188970f4b4169cc055784e21eb71d410cc5

# Server or server pool from which to fetch updates.  You can change
# this to point at a specific server if you want, but in most cases
# using a "nearby" server won't provide a measurable improvement in
# performance.
ServerName update.FreeBSD.org

# Components of the base system which should be kept updated.
#Components src world kernel
Components world kernel

# Example for updating the userland and the kernel source code only:
# Components src/base src/sys world

# Paths which start with anything matching an entry in an IgnorePaths
# statement will be ignored.
IgnorePaths

# Paths which start with anything matching an entry in an IDSIgnorePaths
# statement will be ignored by "freebsd-update IDS".
IDSIgnorePaths /usr/share/man/cat
IDSIgnorePaths /usr/share/man/whatis
IDSIgnorePaths /var/db/locate.database
IDSIgnorePaths /var/log

# Paths which start with anything matching an entry in an UpdateIfUnmodified
# statement will only be updated if the contents of the file have not been
# modified by the user (unless changes are merged; see below).
UpdateIfUnmodified /etc/ /var/ /root/ /.cshrc /.profile

# When upgrading to a new FreeBSD release, files which match MergeChanges
# will have any local changes merged into the version from the new release.
MergeChanges /etc/ /boot/device.hints

### Default configuration options:

# Directory in which to store downloaded updates and temporary
# files used by FreeBSD Update.
# WorkDir /var/db/freebsd-update

# Destination to send output of "freebsd-update cron" if an error
# occurs or updates have been downloaded.
# MailTo root

# Is FreeBSD Update allowed to create new files?
# AllowAdd yes

# Is FreeBSD Update allowed to delete files?
# AllowDelete yes

# If the user has modified file ownership, permissions, or flags, should
# FreeBSD Update retain this modified metadata when installing a new version
# of that file?
# KeepModifiedMetadata yes

# When upgrading between releases, should the list of Components be
# read strictly (StrictComponents yes) or merely as a list of components
# which *might* be installed of which FreeBSD Update should figure out
# which actually are installed and upgrade those (StrictComponents no)?
# StrictComponents no

# When installing a new kernel perform a backup of the old one first
# so it is possible to boot the old kernel in case of problems.
# BackupKernel yes

# If BackupKernel is enabled, the backup kernel is saved to this
# directory.
# BackupKernelDir /boot/kernel.old

# When backing up a kernel also back up debug symbol files?
# BackupKernelSymbolFiles no
 
Nach dem "freebsd-update fetch" einfach nur ein "freebsd-update install" ausführen, fertig. Du solltest die Version von FreeBSD mit freebsd-version anzeigen lassen. Sollte der Kernel nicht aktualisiert werden, zeigt er dir nicht die tatsächliche "Version" an.
HTH
 
Vielen Dank! Deine Antwort hat mir weitergeholfen, es hat funktioniert. :)
 
http://update4.freebsd.org/
zum Beispiel, ist einer der "UPDATE Server". Hier findest du alle in Frage kommenden Releases für freebsd-update.
Mit der Option -r kannst du von einem niedrigeren Release zu einem hier gelisteten höheren Release upgraden
Code: 
     -r newrelease
                  Specify the new release to which freebsd-update should
                  upgrade (upgrade command only).
FreeBSD-VERSION-pn1 zu FreeBSD-VERSION-pn2 ist kein Release-Upgrade, deshalb nichts für -r.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben