Language Selection

English French German Italian Portuguese Spanish

Hoist your applications with petardfs

Filed under
Software

The petard filesystem is designed to produce only errors -- but you can stipulate what conditions generate the errors and what those errors should be. That makes petardfs useful for system and unit testing -- for example, making sure that an application gives a sane error message if it fails to open a file, or if there is a read error at byte 5000 of a file.

Petardfs uses Filesystem in Userspace (FUSE) to allow easy setup without requiring a kernel recompile or new kernel modules. In normal configuration you specify a "base filesystem" and give a mountpoint -- for example, saying that /home/ben/foo is the base filesystem and mounting the filesystem at /home/ben/petard-foo. Without any other configuration, any files in foo will be available in petard-foo unchanged. Petardfs uses an XML configuration file to tell which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37.

Building and installation of petardfs follows the conventional configure, make, make install procedure.

More Here




More in Tux Machines

grep-2.21 released [stable]

This is to announce grep-2.21, a stable release. There have been 94 commits by 3 people in the 25 weeks since 2.20. Read more Also: GNU Parallel 20141122 ('Rosetta') released

SUSE invests in software-defined storage

SUSE, the enterprise Linux company, is working on its own storage solution using open-source Ceph: SUSE Storage. Read more

Linux 3.18-rc6

Steady progress towards final release, although we still have a big unknown worry in a regression that Dave Jones reported and that we haven't solved yet. In the process of chasing that one down, there's been a fair amount of looking at various low-level details, and that found some dubious issues, but no smoking gun yet. But that explains some of the patches in rc6.. Read more

Open Source Code Contains Fewer Defects, But There's a Catch

Research suggests that software developed using open source code contains fewer defects than that built with proprietary code. The catch is that open source code rarely benefits from security teams specifically tasked with looking for bugs. Read more