summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Update for 185401, errors now go to stderr.stefanf2008-11-281-0/+0
|
* Add tools-level test for POSIX.1e functionality.trasz2008-11-253-0/+632
| | | | Approved by: rwatson (mentor)
* This actually works on Linux, I just had wrong directory permission.pjd2008-11-241-4/+0
| | | | Found by: trasz
* Include TODO messages even if tests succeeds, so we can detect when somethingpjd2008-11-241-6/+18
| | | | suddenly started to work.
* Add a test for r185231.stefanf2008-11-231-0/+9
|
* Mark all the places where Linux is not POSIX-compilant. Tested on ext3.pjd2008-11-233-0/+8
|
* fstest for Linux:pjd2008-11-239-56/+53
| | | | | | | - Use -- when needed so Linux getopt(3) won't get confused. - Follow POSIX more closely. Submitted by: Szabolcs Szakacsits <szaka@ntfs-3g.org>
* fstest for Linux:pjd2008-11-231-2/+26
| | | | Automatically detect file system type.
* FreeBSD's way of handling rmdir("..") is not POSIX-compilant.pjd2008-11-231-9/+3
|
* Shorter version.pjd2008-11-231-14/+4
|
* Add support for pathconf(2).pjd2008-11-231-1/+57
|
* Detect operating system automatically.pjd2008-11-231-5/+21
|
* fstest for Linux:pjd2008-11-231-4/+27
| | | | | - Use /dev/urandom, it is more portable. - Implement todo() function which allows to mark known failures.
* IFp4: Regression tests for FreeBSD/ZFS chflags(2)/lchflags(2).pjd2008-11-2214-88/+136
|
* Update ZFS from version 6 to 13 and bring some FreeBSD-specific changes.pjd2008-11-1754-0/+12014
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bring huge amount of changes, I'll enumerate only user-visible changes: - Delegated Administration Allows regular users to perform ZFS operations, like file system creation, snapshot creation, etc. - L2ARC Level 2 cache for ZFS - allows to use additional disks for cache. Huge performance improvements mostly for random read of mostly static content. - slog Allow to use additional disks for ZFS Intent Log to speed up operations like fsync(2). - vfs.zfs.super_owner Allows regular users to perform privileged operations on files stored on ZFS file systems owned by him. Very careful with this one. - chflags(2) Not all the flags are supported. This still needs work. - ZFSBoot Support to boot off of ZFS pool. Not finished, AFAIK. Submitted by: dfr - Snapshot properties - New failure modes Before if write requested failed, system paniced. Now one can select from one of three failure modes: - panic - panic on write error - wait - wait for disk to reappear - continue - serve read requests if possible, block write requests - Refquota, refreservation properties Just quota and reservation properties, but don't count space consumed by children file systems, clones and snapshots. - Sparse volumes ZVOLs that don't reserve space in the pool. - External attributes Compatible with extattr(2). - NFSv4-ACLs Not sure about the status, might not be complete yet. Submitted by: trasz - Creation-time properties - Regression tests for zpool(8) command. Obtained from: OpenSolaris
* Add a test for the "or more" part of the following POSIX specification.dds2008-11-112-1/+3
| | | | | | "A function can be preceded by one or more '!' characters, in which case the function shall be applied if the addresses do not select the pattern space."
* Make test for write access to the directory being moved a little moretrasz2008-11-071-5/+9
| | | | | | specific. Approved by: rwatson (mentor)
* Improve output when a test fails.trasz2008-11-071-2/+2
| | | | Approved by: rwatson (mentor)
* Change ZFS behaviour to match UFS: when moving (rename(2)) a subdirectorytrasz2008-11-061-0/+38
| | | | | | | from one parent directory to another, in addition to the usual access checks one also needs write access to the subdirectory being moved. Approved by: rwatson (mentor), pjd
* Implement support for RPCSEC_GSS authentication to both the NFS clientdfr2008-11-034-0/+725
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
* o unbreak ani stat displaysam2008-10-291-5/+9
| | | | o improve some labels
* sync w/ driver updates; this also brings in ani statssam2008-10-273-19/+270
|
* add regdomain knobsam2008-10-271-0/+3
|
* #ifdef out the lock-against-self test. I'm not sure it makes sense, anddes2008-10-201-0/+4
| | | | | | it relies on non-portable flock(2) semantics. Not only is flock(2) not portable, but on some OSes that do have it, it is implemented in terms of fcntl(2) locks, which are per-process rather than per-descriptor.
* add -n option to suppress clearing the build tree and add -DNO_CLEANsam2008-10-191-2/+18
| | | | to buildworld and/or buildkernel
* Avoid failing if the directory already exists (when restarting at customize).n_hibma2008-10-091-1/+1
| | | | MFC after: 2 days
* Update udpzerobyte to understand that passing 0 as a length to recv(2)rwatson2008-10-071-5/+26
| | | | | | | | will cause it to return 0, not EAGAIN. Add UNIX domain socket support to udpzerobyte, which suggests this regression test should be moved to the general sockets test area rather than netinet.
* Add IPv6 support to zero-size UDP transmit/receive test.rwatson2008-10-071-27/+47
|
* Regression test for the loopback handling of zero-length UDP packets, whichrwatson2008-10-072-0/+111
| | | | should be delivered but without payload.
* Add very simple regression test for fstat(2) on sockets: make sure itrwatson2008-10-062-0/+80
| | | | | returns success for various socket types. It's easy to imagine this being enhanced to validate the returned data, but...
* In cust_install_files() we ignore CVS directories. In a similar way nowsimon2008-09-231-1/+1
| | | | also ignore .svn directories.
* - Change all "echo #..." into using a progress print function to make itsimon2008-09-231-41/+65
| | | | | | | | | | | possible to make NanoBSD output more quite or verbose. The default output should remain mostly unchanged. [1] - Add missing shift for -i. - Clean up usage() so it's now (mostly) sorted alphabetically. - Make command line argument handling more consistent in the code and remove redundant semicolons. Reviwed by: phk [1]
* add missing optionssam2008-09-232-0/+7
|
* add missing optionssam2008-09-232-0/+5
|
* * Add USB boot support.bms2008-09-221-5/+52
| | | | | | | | | | * Allow the image name to be renamed via NANO_IMGNAME. * Propagate TARGET_ARCH into src top level make targets explicitly to support cross-building. * Increase the default size of NanoBSD media from 488MB to 584MB to accomodate a -CURRENT world. Reviewed by: phk
* Mark the first slice of a NanoBSD image 'active' by default.bms2008-09-221-0/+4
| | | | | | | This fixes USB boot (not yet merged to HEAD) with 3 flavours of BIOS I've seen. Approved by: phk
* add new build knobs and jigger some existing controls to improvesam2008-09-2126-0/+99
| | | | | | | | control over the result of buildworld and installworld; this especially helps packaging systems such as nanobsd Reviewed by: various (posted to arch) MFC after: 1 month
* Include $NANO_NAME in the completed message. This is nice if you aresimon2008-09-211-1/+1
| | | | | building multiple NanoBSD images at once to keep track of what is running and what isn't.
* eliminate hardwired lists; use the media type to autoconfigsam2008-09-211-3/+17
|
* Add files to remove when WITHOUT_HESIOD is set.antoine2008-09-131-3/+7
| | | | | | | This fixes "make check-old" when WITH_HESIOD is set. PR: 122406 MFC after: 1 month
* o Correct a comment: a test file size is a four pages not three.maxim2008-09-101-1/+1
|
* Change space -> tab in printed usage output to make it look consistent.simon2008-09-071-1/+1
|
* Regression tests for bugs in gdtoa.das2008-09-031-11/+17
|
* Fix typo in comment.thomas2008-09-021-1/+1
|
* Add simple cd to dvd conversion script.rik2008-08-311-0/+267
|
* Update README to reflect removal of netatm/harp test parts some time ago.rwatson2008-08-311-5/+2
| | | | MFC after: 3 days
* Connect a forgotten test case to Makefile.jkim2008-08-291-1/+1
|
* Do not pass validatation level since all issues are fixed now.jkim2008-08-291-1/+1
|
* Merge local copy of bpf_validate() with bpf_filter.c.jkim2008-08-291-11/+14
|
* By default backup geli metadata to a file. It is quite critical 512 bytes,pjd2008-08-2915-17/+123
| | | | | | | | | | | | | | | | | | | | | | | once it is lost, all data is gone. Option '-B none' can by used to prevent backup. Option '-B path' can be used to backup metadata to a different file than the default, which is /var/backups/<prov>.eli. The 'geli init' command also prints backup file location and gives short procedure how to restore metadata. The 'geli setkey' command now warns that even after passphrase change or keys update there could be version of the master key encrypted with old keys/passphrase in the backup file. Add regression tests to verify that new functionality works as expected. Update other regression tests so they don't create backup files. Reviewed by: keramida, rink Dedicated to: a friend who lost 400GB of his live by accidentally overwritting geli metadata MFC after: 2 weeks
OpenPOWER on IntegriCloud