samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-10	r5672: Use switch_type() and the token storage mechanism for unions:	Jelmer Vernooij	1	-2/+2
	- Makes union handling less special - Allows unions in arrays, etc - Compatible with midl - Pidl will warn about switch_type() and the type of the switch_is() variable being different (This used to be commit dc6b4ffc82a191631bc16a4b93a4916a39183ec6)
2007-10-10	r5661: Be a little stricter on syntax regarding arrays. A pointer to an	Jelmer Vernooij	1	-2/+2
	array can now only be : type name[]; rather then : type name; which was supported in the past. Warnings will be given when the first syntax is used. Reasons for this change in behaviour include improved readability and the fact that the second format makes dealing with multiple levels of pointers harder. (This used to be commit a416de5825c540fd3741731c4be05e9a659a6fdb)
2007-10-10	r5362: Add pointer_default() support to pidl. pointer_default()	Jelmer Vernooij	1	-1/+2
	is assumed to be "ptr" if not specified (just like midl). The validator will warn when "ptr" is used at the moment, because pidl only supports unique, ref and relative at the moment. (This used to be commit 31bed62a9a6f7830f523d509b67970648d40aaef)
2007-10-10	r5034: - added a type mapping function in pidl, so the type names in our IDL	Andrew Tridgell	1	-6/+6
	files don't need to match the type names in the generated headers - with this type mapping we no longer need definitions for the deprecated "int32", "uint8" etc form of types. We can now force everyone to use the standard types int32_t, uint8_t etc. - fixed all the code that used the deprecated types - converted the IDL types "int64" and "uint64" to "dlong" and "udlong". These are the 4 byte aligned 64 bit integers that Microsoft internally define as two 32 bit integers in a structure. After discussions with Ronnie Sahlberg we decided that calling these "int64" was confusing, as it implied a true 8 byte aligned type - fixed all the cases where we incorrectly used things like "NTTIME_hyper" in our C code. The generated API now uses a NTTIME for those. The fact that it is hyper-aligned on the wire is not relevant to the API, and should remain just a IDL property (This used to be commit f86521677d7ff16bdc4815f9524e5286026f10f3)
2007-10-10	r3939: - added "posix:fakeoplocks" option for testing with oplocks forced on	Andrew Tridgell	1	-1/+17
	- added support for sticky write times after a setfileinfo, by using a write_time field in the DosAttrib xattr structure. (This used to be commit 4a52fae82d8305e999f94f1947daa21dab54cdfd)
2007-10-10	r3838: use "security.NTACL" instead of "security.NTAcl" for the xattr name ↵	Andrew Tridgell	1	-1/+1
	for ACLs (This used to be commit db72290bbe87644a89385c465855629a1f881e4f)
2007-10-10	r3833: NTACL is a better xattr name than DosAcl (tpot suggested this)	Andrew Tridgell	1	-7/+6
	(This used to be commit 17911eea5995c12a2300dd3928612c77f8f0883e)
2007-10-10	r3832: added NT ACL query/set to the posix NTVFS backend. The default ACL is	Andrew Tridgell	1	-0/+23
	based on the current nttoken, which is completely wrong, but works as a start. The ACL is stored in the xattr system.DosAcl, using a NDR encoded IDL union with a version number to allow for future expansion. pvfs does not yet check the ACL for file access. At the moment the ACL is just query/set. We also need to do some RPC work to allow the windows ACL editor to be used. At the moment is queries the ACL fine, but displays an error when it fails to map the SIDs via rpc. (This used to be commit 3a1f20d874ab2d8b2a2f2485b7a705847abf1263)
2007-10-10	r3806: added support to smb_server and pvfs for the NTTRANS Create call. This	Andrew Tridgell	1	-0/+2
	call has an optional sec_desc and ea_list. (This used to be commit 8379ad14e3d51a848a99865d9ce8d56a301e8a3c)
2007-10-10	r3798: added support for alternate data streams in xattrs into pvfs.	Andrew Tridgell	1	-2/+6
	The trickiest part about this was getting the sharing and locking rules right, as alternate streams are separate locking spaces from the main file for the purposes of byte range locking, and separate for most share violation rules. I suspect there are still problems with delete on close with alternate data streams. I'll look at that next. (This used to be commit b6452c4a2068cf7e837778559da002ae191b508a)
2007-10-10	r3747: - added some of the infrastructure needed for streams support in pvfs	Andrew Tridgell	1	-0/+19
	(the IDL, and the load/save meta-data logic) - changed pvfs_resolve_name() to default to non-wildcard, needing PVFS_RESOLVE_WILDCARD to enable wildcards. Most callers don't want wildcards, so defaulting this way makes more sense. - fixed deletion of EAs (This used to be commit e7afd4403cc1b7e0928776929f8988aa6f15640b)
2007-10-10	r3573: added trans2open support to smbd and pvfs, and fine-tuned the ↵	Andrew Tridgell	1	-1/+0
	open->generic ntvfs mapping code. (This used to be commit ed844192d7f7ed487290f719df65f256a5b0b9bc)
2007-10-10	r3549: added support for DOS extended attribute lists (name/value pairs)	Andrew Tridgell	1	-2/+18
	stored in posix xattrs (This used to be commit bad6a88371264cffce2bf5d6ce904b7b357081de)
2007-10-10	r3545: initial support for using extended attributes to hold extended dos ↵	Andrew Tridgell	1	-0/+35
	attributes of files. I decided to use IDL/NDR to encode the attribute, as it gives us a simple way to describe and extend the saved attributes. The xattr code needs to hook into quite a few more places in the pvfs code, but this at least gets the basics done. I will start encoding alternate data streams streams, DOS EAs etc soon using the same basic mechanism. I'll probably stick to "version 1" for the xattr.idl for quite a while even though it will be changing, as I don't expect anyone to be deploying this in production just yet. Once we have production users we will need to keep compatibility by supporting all the old version numbers in xattr.idl. (This used to be commit c54253ed1b7dce1d14f43e747da61089aea87094)