|
Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc |
|
| #
f603807b |
| 26-Nov-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sys/dev/disk/dm: Remove dm/targets/ directory and move its entries to dm/
Device mapper targets' path
sys/dev/disk/dm/targets/<name>/dm_target_<name>.c
are too deep for no reason.
This commit remov
sys/dev/disk/dm: Remove dm/targets/ directory and move its entries to dm/
Device mapper targets' path
sys/dev/disk/dm/targets/<name>/dm_target_<name>.c
are too deep for no reason.
This commit removes targets/ directory which isn't necessary at all,
assuming userspace has no dependencies on this (and it shouldn't either).
Neither NetBSD (sys/dev/dm/dm_target_*.c) nor Linux kernel (drivers/md/dm*.c)
has a directory tree like this, which is better.
show more ...
|
|
Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
| #
8ce45526 |
| 07-Nov-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sys/dev/disk/dm: Whitespace cleanups
|
|
Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.4.3, v3.4.2, v3.4.1, v3.4.0, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0 |
|
| #
2443e96e |
| 07-Feb-2011 |
Justin C. Sherrill <justin@leaf.dragonflybsd.org> |
Merge branch 'master' of ssh://crater.dragonflybsd.org/repository/git/dragonfly
Conflicts:
UPDATING
|
| #
7115a22b |
| 01-Dec-2010 |
Alex Hornung <ahornung@gmail.com> |
dm - Modularize it fully
* Move each of the targets (except error and zero) into a subdirectory
in targets/.
* Change the macro DM_TARGET_MODULE to also let the module depend on dm.
* Add a new
dm - Modularize it fully
* Move each of the targets (except error and zero) into a subdirectory
in targets/.
* Change the macro DM_TARGET_MODULE to also let the module depend on dm.
* Add a new macro DM_TARGET_BUILTIN, which must be used instead of
DM_TARGET_MODULE for targets that are compiled into the main dm.ko
instead of a separate module. Not doing this will prevent dm.ko from
unloading.
* Enable automatic loading of target modules if they aren't builtin or
loaded yet. Automatically loaded modules can be unloaded via kldunload
safely via a little hack (see source).
* NOTE: automatic loading doesn't always work. /boot must be mounted
already, so if you are planning on encrypting your swap or similar
stuff, you need to *EXPLICITLY* load dm_target_crypt.ko via the
loader.
* NOTE: PLEASE NOTE THE NOTE ABOVE!
* Fix a little issue with dm_target_crypt that would print "unloaded"
even if it wouldn't unload.
* Change the name of dm_target_stripe to dm_target_striped, since the
target is actually called "striped".
* Move dm.h to sys/sys/dm.h
* Get rid of files.dm, a leftover from the import
show more ...
|
|
Revision tags: v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0 |
|
| #
670c949e |
| 12-Jul-2010 |
Samuel J. Greear <sjg@thesjg.com> |
Merge branch 'master' into kq_devices
|
| #
e8e2bcda |
| 06-Jul-2010 |
Alex Hornung <ahornung@gmail.com> |
dm - General printout cleanup
|
| #
dd9da8fe |
| 27-Jun-2010 |
Alex Hornung <ahornung@gmail.com> |
dm - Add crypt target
* Add an initial crypt target. It's WIP, full of bugs, but is a general
outline of how I want to approach the crypt target for dm.
* As per Aggelos' recommendation, I'm usin
dm - Add crypt target
* Add an initial crypt target. It's WIP, full of bugs, but is a general
outline of how I want to approach the crypt target for dm.
* As per Aggelos' recommendation, I'm using pbkdf2 and hmac sha from
other crypto implementations instead of rolling my own, for good
cryptography's sake :P
show more ...
|
| #
5b279a20 |
| 02-Jun-2010 |
Alex Hornung <ahornung@gmail.com> |
dm - Port to DragonFly
* port the device mapper kernel support to DragonFly
|
|
Revision tags: v2.6.3, v2.7.3 |
|
| #
ff56536e |
| 27-Apr-2010 |
Alex Hornung <ahornung@gmail.com> |
dm - Import verbatim from NetBSD
|