Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Apr 20, 2014

  1. route.8: Remove NS remains.

    authored April 20, 2014
  2. Remove some XEROX Network Systems (NS) protocol remains.

    We removed most of it in 2011 (62b5ec1).
    authored April 20, 2014
  3. hammer2 - more dmsg/separation work, add nmasters field to inode

    * More separation and stability work
    
    * Remove unused HAMMER2_OPFLAG_SUPROOT (the super-root can be
      distinguished by pfs_type).
    
    * Add pfs_nmasters field to the inode structure.  This will be
      used to record how many hard masters a PFS has so the
      cluster code can determine the status of the cluster.
    authored April 19, 2014
  4. dmsg, hammer2 - refactor remove hammer2-specific code

    * More cleanups in libdmsg and various hammer2 utilities
    
    * Stability pass, get the hammer2 service demon working again.
    authored April 19, 2014
  5. hammer2 - Revise newfs_hammer2

    * Bring newfs_hammer2 up-to-date with the cluster mechanics I intend to use
      for the filesytem.
    
      Generally change the default label from "ROOT" to "LOCAL", the intention
      being that all formatted volumes will at least mount device@LOCAL in order
      to make a HAMMER2 volume available to the cluster protocol.  Once the
      volume is made available, the intension is to then allow other PFSs can
      be created/deleted/managed via the cluster protocol.
    
      newfs_hammer2 will also create a BOOT and ROOT PFS by default, intended for
      simple non-clustered configurations, and the -L label option works
      differently now.
    
    * Generally speaking, all block devices to be used in the cluster must be
      formatted with newfs_hammer2.  A formatted HAMMER2 volume can be used to
      host any number of PFSs (Pseudo-FileSystems).  Each PFS is independent
      and can be part of different clusters.
    authored April 19, 2014

Apr 19, 2014

  1. kernel: fix buildkernel by adding include to subr_diskiocom.c

    Include vfs/hammer2/hammer2_disk.h to sys/kern/subr_diskiocom.c
    authored April 19, 2014
  2. hammer2 - refactor libdmsg volume configuration

    * Move the libdmsg volume configuration structures and commands, which
      are hammer2-specific, over to hammer2.
    authored April 19, 2014
  3. libdmsg - refactor remove hammer2-specific code

    * Remove hammer2-specific code.
    
    * Refactor the callback API to allow the hammer service code to handle
      the H2-specific LNK_CONN commands... mostly VOLCONF.
    authored April 19, 2014
  4. Exclude libdmsg temporarily from the build until it is fixed.

    Requested-by: dillon
    authored April 19, 2014
  5. Antonio Huete Jiménez

    netinet/in - Fix yet another NULL pointer panic.

    DragonFly-bug: <http://bugs.dragonflybsd.org/issues/2662>
    Submitted-by: Vasily Postnicov
    
    This commit closes #2662
    authored April 15, 2014
  6. passwd(1): Allow password changes for PAM users

    * passwd(1) previously only allowed changes for local or NIS users, which
      doesn't make sense
    
    * Fixes FreeBSD PR bin/59638
      http://www.freebsd.org/cgi/query-pr.cgi?pr=59638
    
    * Tested with a DragonFly (password change) and a Debian system (login)
    authored April 19, 2014
  7. hammer2 - Shift dmsg structures around

    * Shift dmsg structures around so sys/dmsg.h does not contain hammer2-specific
      structures.  Move those structures to hammer2_disk.h
    authored April 18, 2014

Apr 17, 2014

  1. urtwn.4: Fix synopsis (usb4bsd -> usb).

    authored April 17, 2014
  2. Dynamic root: Add "/lib" to gold and ld linker search paths

    This fixes numerous new dports failures seen during linking.
    authored April 17, 2014 François Tigeot committed April 17, 2014

Apr 16, 2014

  1. mount{,d}(8): Use the pidfile(3) API for handling mountd's PID file.

    Taken-from: FreeBSD
    authored April 16, 2014
  2. libthread_xu - Clean up the red zone on library unload

    * If the main program is not linked against -pthread but dynamically
      loads a shared library that is via dlopen(), then dlclose()'s it,
      libthread_xu leaves red-zone and cached thread stacks dangling.
    
      The second attempt to (indirectly) load libthread_xu then fails with a
      red-zone panic.
    
    * Add a destructor for libthread_xu to unmap the red-zone and to clean out
      any cached thread stacks.
    
    * Note that neither libthread_xu nor most other large libraries are designed
      to be unloaded.  That is, even if loading/unloading works, numerous libraries
      will almost certainly leak memory.  This change prevents the fatal error but
      doesn't fix the general memory leakage problem.
    
      IMHO Only libraries designed to be unloadable should be unloaded.
    
    Reported-by: Vasily Postnicov <shamaz.mazum@gmail.com>
    authored April 16, 2014
  3. Fix a number of typos in messages and manual pages.

    authored April 16, 2014
  4. initrd: Fix installation during make release

    * mkinitrd needs to know ramdisk images are to be installed in
      ${DESTDIR}/boot/kernel and not just /boot/kernel
    
    * ${DESTDIR}/boot/kernel also has to exist first. Create it with
      mtree(8)
    authored April 16, 2014

Apr 15, 2014

  1. loader/acpi: Fix/remove some comments and remove a misleading error msg.

    authored April 15, 2014
  2. acpi: machdep.acpi_root should have the RSDP, so taking that should b…

    …e fine.
    authored April 15, 2014
  3. kernel/acpi: In the OS dependent layer, sync the debug code w/ FreeBSD.

    * Remove an unused function.
    
    * Enter the debugger only when ACPI_DEBUG is set.
    
    * Fix indent and whitespace.
    authored April 15, 2014
  4. initrd: Not everyone keeps their source in /usr/src.

    authored April 15, 2014
  5. units(1): Sync the manual page with FreeBSD too.

    While here, add back units.c's SVN ID.
    authored April 15, 2014
  6. Dynamic root: Remove old libraries from /usr/lib

    authored April 15, 2014
  7. Update the pciconf(8) database.

    April 14, 2014 snapshot from http://pciids.sourceforge.net/
    authored April 15, 2014

Apr 14, 2014

  1. units(1): bring in latest changes from FreeBSD

    In the interest of further compatibility with GNU units this brings in:
    :	-U for units file
    :	-v for verbose
    :	-V for version
    :	libedit support
    : 	-f support for multiple files
    
    And other additional improvements.
    
    Note that this introduces a breaking change from prior: -V and -v have been swapped (and a new -v has been added).
    authored April 14, 2014
  2. Fix typo

    authored April 15, 2014
  3. units(1): update to the latest library from FreeBSD

    This brings some new units along with enhanced compatibility with GNU units(1).
    authored April 14, 2014
  4. kernel: Sync ACPICA with Intel's version 20140325.

    As far as I can see, the most important change is a fix for the auto-
    serialization of control methods so that the currently executing AML
    SyncLevel is ignored when invoking such a method. This fixes an issue
    seen in some systems showing AE_AML_MUTEX exceptions since 20140214
    which had to set hw.acpi.auto_serialize_methods to 0 to work around
    the issue.
    
    This was actually reported for DragonFly by Andrey Oktyabrskiy (see
    http://lists.dragonflybsd.org/pipermail/users/2014-February/109376.html).
    
    See sys/contrib/dev/acpica/changes.txt for a complete list of all
    changes.
    authored April 14, 2014
  5. buildsystem: Fix libfoo.so links for /lib libraries

    * When installing to a non-default location by using DESTDIR on the make
      installworld command line, /usr/lib/libfoo.so links pointed to wrong
      locations
    
    * DESTDIR is used both as an installworld parameter and internally by the
      build system and these two cases expect different behaviors
    
    * Symlinks locations in /usr/obj must be relative to the host (builder)
      filesystem namespace
      libc.so -> /usr/obj/usr/src/world_x86_64/lib/libc.so
    
    * Symlinks locations in the final destination directory must be relative to
      the target world filesystem namespace
      libc.so -> /lib/libc.so
    
    * The symlinks themselves must be absolute in order to not break
      installations where /usr is a symlink
    
    Inspired-by: FreeBSD's historical transition to /lib
    authored April 14, 2014

Apr 13, 2014

  1. Dynamic root: Move required libraries to /lib

    * Add /lib to the standard run-time loader library search path
    
    * Ensure libxxx.so symbolic links stay in /usr/lib, the build
      tools won't pick them up in /lib
    authored April 13, 2014
  2. Dynamic root: Build /bin and /sbin dynamically

    * Introduce a NO_DYNAMICROOT variable for people wanting to keep
      fully static /bin and /sbin directories
    
    * Keep building /sbin/init statically
    
    * Keep a few other binaries static to avoid moving too many libraries
      to /lib and/or creating many symlinks.
      Those few binaries do not handle user names and thus don't need to be
      NSS aware/dynamically linked.
    
    * In particular, keeping udevd static allow us to avoid moving libpthread
      and its associated links to libc_r or libthread_xu
    authored April 13, 2014

Apr 12, 2014

  1. Dynamic root: Move ld-elf.so.2 to /libexec

    * Install it first to avoid breaking upgrades for systems previously
      having it located in /usr/libexec. install(1), beeing a dynamic binary,
      needs it at runtime.
    
    * Since ld-elf.so.2's path is embedded in ELF binaries, also create a
      symbolic link in the old location to support existing binaries.
    
    * Code to handle chflags attributes obtained from FreeBSD.
    authored April 12, 2014
  2. Dynamic root: Create /lib and /libexec

    Make the installer also install these directories
    authored April 12, 2014

Apr 11, 2014

  1. buildworld - Make auto-backup smarter.

    * Do not try to auto-backup the world if the backup location is
      read-only.
    authored April 11, 2014
Something went wrong with that request. Please try again.