Auf dem Weg zu FreeBSD 10.0

Yamagi

Yamagi

Possessed With Psi Powers
Teammitglied
Soeben wurde ein weiterer Schritt auf dem Weg zu FreeBSD 10.0 gegangen, die neue 10-STABLE Branch wurde erstellt. Zugleich wurden die Debug-Optionen aus dem neuen 10-STABLE entfernt. Wer bisher 10-CURRENT folgte und mit zu 10.0 segeln möchte, muss nun also den Zweig wechseln. Ansonsten landet man im neuen FreeBSD 11-CURRENT.
Code: 
Author: gjb
Date: Thu Oct 10 17:56:30 2013
New Revision: 256281
URL: http://svnweb.freebsd.org/changeset/base/256281

Log:
  Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
  Approved by:    re (implicit)
  Sponsored by:    The FreeBSD Foundation

Added:
  stable/10/
     - copied from r256279, head/
 
Das "jail" rc-Script unterstützt nun die jail.conf und konvertiert automatisch:
Code: 
Author: hrs
Date: Thu Oct 10 09:32:27 2013
New Revision: 256256
URL: http://svnweb.freebsd.org/changeset/base/256256

Log:
  - Update rc.d/jail to use a jail(8) configuration file instead of
    command line options.  The "jail_<jname>_*" rc.conf(5) variables for
    per-jail configuration are automatically converted to
    /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
    This is transparently backward compatible.
  - Fix a minor bug in jail(8) which prevented it from returning false
    when jail -r failed.
  Approved by:    re (glebius)
 
Wird das eigentlich mit dem pkg.freebsd.org mal irgendwann was?
Nach jeder Installation muss man sich immer irgendwelche dubiosen PACKACKSITES zusammensuchen
 
Und ZFS/GELI-Unterstützung für bsdinstall:
Code: 
Author: dteske
Date: Fri Oct 11 23:12:05 2013
New Revision: 256361
URL: http://svnweb.freebsd.org/changeset/base/256361

Log:
  MFC revisions 256321-256323,256331,256333,256335,256343:
  Bring in a new zfsboot auto script for performing automatic setup of a boot
  pool (optionally encrypted) with many other options, validations, features.
  Originally submitted by Allan Jude; modified in collaboration.
  MFC revisions 256325,256330,256345:
  Rewrite the keymap selection menu to display keymaps and provide a test
  mechanism. Test mechanism originally submitted by Warren Block; modified.
  MFC r256347:
  Prominently display "Wireless" for each wireless network interface. Part
  of PR bin/161547; submitted by Warren Block; slightly modified.
  MFC r256348:
  Remove the dumpdev configuration dialog, merge it into the regular
  services configuration and enable it by default. Originally submitted by
  Allan Jude; slightly modified.
  PR:        bin/161547
  Submitted by:    Allan Jude, Warren Block <wblock@wonkity.com>
  In collaboration with:    Allan Jude <freebsd@allanjude.com>
  Approved by:    re (glebius)
 
Super, dann hört endlich das Geheule auf, dass FreeBSD unbenutzbar wäre weil der Installer kein ZFS anbietet. :)
 
Die Packagesite ist auch noch keine offizielle. Der Name lässt es vermuten. Ich denke man will keine Beschwerden haben wenn man etwas in einer Testumgebung nicht passt.
 
Nunja, wenn man schon Alpha auf ne Version packt, sollte man jetzt nicht sagen, dass man Angst vor negativen Reaktionen hat und deshalb lieber gar keine packagesite reinpacken. Allein der Name pkgtest oder pkgbeta sollte das wohl genug ausdrücken. Und mal ehrlich: die Zielgruppe von FreeBSD ist jetzt nicht gerade der Meganoob
 
Und wir sind bei BETA1:
Code: 
Author: gjb
Date: Sat Oct 12 20:01:36 2013
New Revision: 256393
URL: http://svnweb.freebsd.org/changeset/base/256393

Log:
  Update stable/10 to -BETA1 as part of the 10.0-RELEASE cycle.
  Approved by:    re (implicit)
  Sponsored by:    The FreeBSD Foundation
 
Und nun auch offiziell:
Code: 
The first BETA build of the 10.0-RELEASE release cycle is now available
on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and
sparc64 architectures.

The image checksums follow at the end of this email.

ISO images and, for architectures that support it, the memory stick images
are available here:

  ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/

(or any of the FreeBSD mirror sites).

If you notice problems you can report them through the normal GNATS PR
system or here on the -current mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "stable/10" branch.

Important note to freebsd-update(8) users:  Due to a last minute problem
found in the 10.0-BETA1 freebsd-update(8) builds, freebsd-update(8) is
NOT supported for 10.0-BETA1 upgrades.  Please do not use
freebsd-update(8) to upgrade to 10.0-BETA1.

Please be aware that cvsup and CVS are not supported methods of updating
the src/ tree.

Also note, due to the size of the images, the ports.txz distribution is
not included in 10.0-BETA1, however is expected to be included with
disc1.iso for subsequent builds during the release cycle.

The ports tree can be fetched either with the portsnap(8) utility, or
using svnlite using any of the mirrors listed here:

    http://www.freebsd.org/doc/en/books/handbook/svn-mirrors.html

Changes between -ALPHA5 and -BETA1 include:

    o Introduce freebsd-version(1), which is intended to be used as an
      auditing tool, to determine the userland patch level when it
      differs from what 'uname -r' reports.

    o Improve ZFS lzjb decompress performance.
   
    o Add two new MIPS CPU families - mips24k and mips74k.

    o The "jail_<jname>_*" rc.conf(5) variables for per-jail
      configuration are automatically converted to
      /var/run/jail.<jname>.conf before the jail(8) utility is invoked,
      so the new jail.conf(5) syntax is used.

    o Remove most of the ATF tools and the _atf user.

    o Updates to random(4).  Please note the following:
    - In 10.0-BETA1, it is not possible for random(4) to be loaded
     as a kernel module via kldload(8).  If not using GENERIC, and
     the system kernel configuration excludes 'device random',
     please include random(4) in the kernel configuration file.
     The fix for this issue is pending review, and is expected to
     be fixed in 10.0-BETA2.

    o Updates to bsdinstall(8).  Please note the following:
    - 10.0-BETA1 introduces a number of updates to bsdinstall(8),
     notably the ability to install to a full ZFS filesystem.
     Please keep in mind that this is an experimental feature.
    - If using the ZFS installation option in *and* have enabled
     full-disk encryption is enabled, a few entries will need to be
     manually added to loader.conf(5) before the 'bootpool' zpool
     will be available after the system boots.  This manual step
     is expected to be fixed in 10.0-BETA2.

     The entries that need to be added are:

       zpool_cache_load="YES"
       zpool_cache_type="/boot/zfs/zpool.cache"
       zpool_cache_name="/boot/zfs/zpool.cache"

     This can be done at the final menu of bsdinstall(8), when
     prompted to boot into the newly-installed system;
     alternatively, this can be done post-install, in which case,
     the following must be run before appending loader.conf(5):

       # zpool import -f bootpool

Pre-installed virtual machine images for 10.0-BETA1 are also available
for amd64 and i386 architectures.

The images are located under the 'snapshots' directory on FTP, here:

    ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/20131012/10.0-BETA1/

The disk images are available in both QCOW2 and VMDK format.  The image
download size is approximately 136 MB, which decompress to a 20GB sparse
image.

The partition layout is:

    - 512k - freebsd-boot GPT partition type (bootfs GPT label)
    - 1GB  - freebsd-swap GPT partition type (swapfs GPT label)
    - ~17GB - freebsd-ufs GPT partition type (rootfs GPT label)


ISO Checksums:

amd64
    SHA256 (FreeBSD-10.0-BETA1-amd64-bootonly.iso) = d3c28a2b972fb38f6b2981729d72b50fcbb5ca07835e9d4e3cfa014e27527631
    SHA256 (FreeBSD-10.0-BETA1-amd64-disc1.iso) = 226b88265e11accd4a873d5fa49e4eaf87f22c00a6580c23879bd18cdb6077b3
    SHA256 (FreeBSD-10.0-BETA1-amd64-memstick.img) = 1ff5f2e25a212a213873e8670b88cbbf88e55105844ad44e425f73a99ebfd795

    MD5 (FreeBSD-10.0-BETA1-amd64-bootonly.iso) = 13879ecb4dd06a8931c5373db61af4bc
    MD5 (FreeBSD-10.0-BETA1-amd64-disc1.iso) = 4a6ba36de48ac51a5f1c060b328e01c4
    MD5 (FreeBSD-10.0-BETA1-amd64-memstick.img) = 85a2ae840db8b7cf59a002f4bc014d38

i386
    SHA256 (FreeBSD-10.0-BETA1-i386-bootonly.iso) = 07c53db7588db0bf350bf374fe11b1973908ddf875cf110a306fb524760385d8
    SHA256 (FreeBSD-10.0-BETA1-i386-disc1.iso) = 2d57b022f47359b2f3e117707058aa0d4e410705563a5e2cd74b5e516ca299b5
    SHA256 (FreeBSD-10.0-BETA1-i386-memstick.img) = 6a4e065c78799921675d9ed219e605326a2d362c4a52b039ce99ce8af3874f23

    MD5 (FreeBSD-10.0-BETA1-i386-bootonly.iso) = b9f43e74e2d33dad5d3ef4eb1f8720e1
    MD5 (FreeBSD-10.0-BETA1-i386-disc1.iso) = 552be24b9b6a18b649c4a7fb97af72f6
    MD5 (FreeBSD-10.0-BETA1-i386-memstick.img) = 7f77b584dcd47c7ef506c150cd4b6823

ia64
    SHA256 (FreeBSD-10.0-BETA1-ia64-bootonly.iso) = 50a63645a25fe32dc4a798e62c1223b4f30338094dd29d721c5b3d09af8a8ebd
    SHA256 (FreeBSD-10.0-BETA1-ia64-disc1.iso) = a92d5b7ffc6976b2c1c72469feaec02b24a5f743c2db4937002cbafc9054359c
    SHA256 (FreeBSD-10.0-BETA1-ia64-memstick.img) = fa74b5d72590e6c8961fa77a3bcd9f8f4f16e8e1115be05be6a694efcf7b9807

    MD5 (FreeBSD-10.0-BETA1-ia64-bootonly.iso) = 4dfdab8653c6e23cf0d5da624985c568
    MD5 (FreeBSD-10.0-BETA1-ia64-disc1.iso) = 94ed426913097ebdda68382e8b37db9d
    MD5 (FreeBSD-10.0-BETA1-ia64-memstick.img) = ab9710f1f17ccd06a37b46ff23831c56

powerpc
    SHA256 (FreeBSD-10.0-BETA1-powerpc-bootonly.iso) = 526d97055f4dbd4899cdfc453609c24e3c3184562d61a295b617a8412a93aed0
    SHA256 (FreeBSD-10.0-BETA1-powerpc-disc1.iso) = 0afcfdd26ed6cb188222606fbf7cb1488343f460c70c3be6a7426093860d8a51
    SHA256 (FreeBSD-10.0-BETA1-powerpc-memstick.img) = f6772e05f966d67c0e6e5c82986b4ec1eeeb44622a756638ff2f73aed66346ea

    MD5 (FreeBSD-10.0-BETA1-powerpc-bootonly.iso) = f28cd0dea86733c9384b0cda5aacb72b
    MD5 (FreeBSD-10.0-BETA1-powerpc-disc1.iso) = f0c440bcb952bd86e15962554ae24b16
    MD5 (FreeBSD-10.0-BETA1-powerpc-memstick.img) = 42661e222189530f3faae69c428bd0ce

powerpc64
    SHA256 (FreeBSD-10.0-BETA1-powerpc-powerpc64-bootonly.iso) = f62dad40a593a6e690dc54100a6d26b0f2029af1bda4144bd10b12076aaeb513
    SHA256 (FreeBSD-10.0-BETA1-powerpc-powerpc64-disc1.iso) = 6aaa5d392cb4cdb555e4ef6e1805b9d7efcbf3eb92c142298def1415410ce092
    SHA256 (FreeBSD-10.0-BETA1-powerpc-powerpc64-memstick.img) = 5db7fc6e448870ff53c1ea1b40008d244f27962b38dbdaa3232b162b2e2e00d0

    MD5 (FreeBSD-10.0-BETA1-powerpc-powerpc64-bootonly.iso) = 603fce7c27f8fd4c55fa9e7380ae5542
    MD5 (FreeBSD-10.0-BETA1-powerpc-powerpc64-disc1.iso) = b67d0fe1d5b019d6961dbb3dcc04fa13
    MD5 (FreeBSD-10.0-BETA1-powerpc-powerpc64-memstick.img) = e4083c808a7263aa26c9fb943bd2c8dc

sparc64
    SHA256 (FreeBSD-10.0-BETA1-sparc64-bootonly.iso) = 6c8ebc06be941ad3d7ebbd7bcbc289fd8d150664eb71171ca98f8eef27941b0f
    SHA256 (FreeBSD-10.0-BETA1-sparc64-disc1.iso) = 60761fb88c7eb3b9397e59a170ea02cb6e95ada7aa6f3b50ef5c99f6c3aaf5fe

    MD5 (FreeBSD-10.0-BETA1-sparc64-bootonly.iso) = 07c959194946873e2326dc1a34c3b75d
    MD5 (FreeBSD-10.0-BETA1-sparc64-disc1.iso) = 5173acba64d32f6ab7cf45ee55620fa2


VM Image Checksums:
amd64:
    SHA256 (FreeBSD-10.0-BETA1-amd64.qcow2.xz) = 6d837b0f7b9f460e99dfb915d77c04d498faaf795edba42aaaec9745de20bd15
    SHA256 (FreeBSD-10.0-BETA1-amd64.vmdk.xz) = 694ded4fc767c9aa58f3f9f08b3fc52a6db293a2e6219ea01dc9dee12a6cc11f

    MD5 (FreeBSD-10.0-BETA1-amd64.qcow2.xz) = 3b99ca17904304d2bd1d2c23aa559146
    MD5 (FreeBSD-10.0-BETA1-amd64.vmdk.xz) = b55f45265a275bb9aa5361d823b78770

i386:
    SHA256 (FreeBSD-10.0-BETA1-i386.qcow2.xz) = 914aa8df98d7a6c4cafe8bddc2fa20b985612d36ad1b209fc3283959cc89c6a0
    SHA256 (FreeBSD-10.0-BETA1-i386.vmdk.xz) = c585975b94bf15129e5a68dc69c9e8e1b02c970468361a9327230b3a045152c7

    MD5 (FreeBSD-10.0-BETA1-i386.qcow2.xz) = dad81ab2ea0b15bdacdb5fa7c6842e60
    MD5 (FreeBSD-10.0-BETA1-i386.vmdk.xz) = f89ddca64717043e7988ace7b18904b1


Glen
 
Sind in der BETA1 eigentlich noch irgendwelche größeren Debugoptionen aktiviert?
Hab heute das erste mal FreeBSD auf nem arm getestet und die Performance ist mehr als unterirdisch. (reicht von CPU Performance bis zu I/O)
 
Ich bin nach dem Update immer noch am Ports bauen. Inzwischen bin ich in der Phase in der ich Patches an Maintainer schicke. Manchmal reicht ein USE_GCC, aber meistens muss man wegen iconv etwas intensiver eingreifen.
 
bananenBrot schrieb:
Sind in der BETA1 eigentlich noch irgendwelche größeren Debugoptionen aktiviert?
Zum Vergrößern anklicken....
Kommt in der ARM-Welt auf die Plattform drauf an. Wenn das sehr auf die Performance schlagende WITNESS aktiviert ist, sagt er es in der dmesg.
 
Kamikaze schrieb:
Ich bin nach dem Update immer noch am Ports bauen. Inzwischen bin ich in der Phase in der ich Patches an Maintainer schicke. Manchmal reicht ein USE_GCC, aber meistens muss man wegen iconv etwas intensiver eingreifen.
Zum Vergrößern anklicken....

Ich habe nach 2 Tagen Ports bauen aufgegeben. Ich weiss nicht, ob bei mir beim update von 9.2 auf 10.0 irgendwas in die Hosen gegangen ist. Aktuell mache ich ein Backup, und dann installier ich 10.0 neu.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben