pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2015-11-03	Add SHA512 digests for distfiles for filesystems category	agc	1	-1/+2
	Existing SHA1 digests verified, all found to be the same on the machine holding the existing distfiles (morden). Existing SHA1 digests retained for now as an audit trail.
2012-10-03	Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.	asau	1	-3/+1

2012-08-17	filesystem/fuse-lzofs: mask O_LARGEFILE like NetBSD	marino	2	-4/+4
	Just piggyback on __NetBSD__ switches to fix DragonFly.
2008-03-03	Mechanical changes to add DESTDIR support to packages that install	jlam	1	-2/+4
	their files via a custom do-install target.
2007-03-16	use open() instead of mknod() to create regular files. avoids having	pooka	2	-7/+35
	to run the file server as root for most uses.
2007-03-15	Fix up CATEGORIES for filesystem	agc	1	-2/+2

2007-03-08	make pwd work	pooka	2	-11/+40

2007-02-21	aspell.	wiz	1	-5/+5

2007-02-20	Initial import of fuse-lzofs-20060306.	xtraeme	6	-0/+158
	LZOlayer Filesystem is a filesystem which allows you to use transparently compressed files, just as they would be normal files. Both read and write operations are possible, along with other most common system calls. It consumes little memory in my opinion, because files are divided into blocks, which can be decompressed separetly. In other words, if you (or an application) would like to read byte 4,500,000 in a file sized 5,000,000 bytes, it only decompresses a block which constain wanted data. Write operation is based on a packet gathering and after reaching its limit it 'syncs' the data. It allows it's user to write/modify files pretty fast, despite the fact it's block divided. LZOlayer FileSystem was meant to support only LZO compression algorythm, because it has extremely low compression/decompression time. However, currently it supports LZO and ZLIB (but only one at the run-time!) compression algorythms.