Fuzbolero .'s Library tagged reference →  View Popular

Btrfs (B-tree FS or "Butter FS"^[1][2]) is a copy-on-write file system for Linux announced by Oracle in 2007 and published under the GNU General Public License (GPL).^[3] It originated as a response to the ZFS filesystem and is expected to be free of many of the limitations that other Linux filesystems currently have.^{[citation needed]}

Btrfs is under heavy development and the current release is only intended for testing. Btrfs v0.18 was released January 2009.^[4] Plans existed for releasing Btrfs v1.0 (with finalized on-disk format) in late 2008,^[5] however this date has since passed and a new timeline for final release has not yet emerged as of April 2009^[update].

Btrfs ("B-tree FS," pronounced "Butter F S"^[1]) is a GPL-licensed copy-on-write file system for Linux announced by Oracle in 2007.^[2]

Btrfs is intended to address the lack of a file system in Linux with pooling, snapshots, checksums and integral multi-device spanning—features crucial as the use of Linux scales upward into larger storage configurations common in the enterprise.^[3] It is expected to offer a feature set comparable to that of Sun's ZFS.^[4] Chris Mason, the principal author of the filesystem, has stated its goal was "to let Linux scale for the storage that will be available. Scaling is not just about addressing the storage but also means being able to administer and to manage it with a clean interface that lets people see what's being used and makes it more reliable."^[5]

Oracle has also begun work on CRFS (Coherent Remote File System), a network filesystem protocol intended to leverage the Btrfs architecture to gain higher performance than existing protocols (such as NFS and CIFS) and to expose Btrfs features such as snapshots to remote clients.^[6]

Btrfs 1.0 (with finalized on-disk format) was originally slated for a late 2008 release,^[7] but as of August 2009^[update] is still not yet ready for production use. It has, however, been accepted into the mainline kernel for testing as of 2.6.29rc1.^[8]

The principal developer of the ext3 and ext4 file systems, Theodore Ts'o, has stated that ext4 is simply a stop-gap and that Btrfs is the way forward,^[9] having "a number of the same design ideas that reiser3/4 had".^[10]

Use an indent of 2 spaces, with no tabs.

Lines should have no trailing whitespace at the end.

Files should be formatted with \n as the line ending (Unix line endings), not \r\n (Windows line endings).

AMTSO Fundamental Principles of Testing


AMTSO Fundamental Principles of Testing as approved by the AMTSO meeting held in Oxford 31st October 2008.

AMTSO Best Practices for Dynamic Testing



AMTSO Best Practices for Dynamic Testing as approved by the AMTSO meeting held in Oxford 31st October 2008

AMTSO Best Practices for Validation of Samples



AMTSO Best Practices for validation of samples as approved by the AMTSO meeting held in Budapest 7th May 2009

AMTSO Best Practices for Testing In-the-Cloud Security Products



AMTSO Best Practices for Testing In-the-Cloud Security Products as approved by the AMTSO meeting held in Budapest 7th May 2009

AMTSO Analysis of Reviews Process



AMTSO Analysis of Reviews Process as approved by the AMTSO meeting held in Budapest 7th May 2009

Available Modules




There are many modules that provide some sort of slideshow / rotator functionality.



• Dynamic display block - Enables you to create and present blocks of content in a dynamic way. Uses the jQuery Cycle Plug-in.
• Views Rotator - a Views style plugin using the Cycle jQuery plugin with a small number of options for controlling transition behaviour.
• Views Cycle - a Views style plugin using the Cycle jQuery plugin, with an option for tabs, several transition effect options and other transition behavior settings.
• Views Slideshow - a Views style plugin using its own JavaScript for the rotation, also including a tabs option and a small number of transition behavior options. The Drupal 6 (dev) version is an extensible API that allows other cycles, rotators, and carousels to plug into the module, so they don't need to recreate the Views functionality.
• Views Slideshow: ImageFlow - offers an ImageFlow option to Views Slideshow, similar to Apple's CoverFlow.
• Slideshow Creator - adds an input format filter to allow you to add slideshow creation code to the body of a node. This module has been deprecated
• Featured Content Slider - select nodes based on content type and create up to 3 blocks of featured content.
• Slider - create a "slider" content type with a multi-value nodereference field to create carousel-style sliders of the referenced nodes.
• EasySlider - create a list-style view with a block display and the view results are displayed in a carousel style slider.
• Node Carousel - create carousels of nodes based on nodequeue or custom values using a hook in your own module.
• Views Carousel - a Views style plugin using the jCarousel jQuery plugin for the rotation, suitable for e.g. a scrollable thumbnail viewer.

The node access system determines who can do what to which nodes.

In determining access rights for a node, node_access() first checks
whether the user has the "administer nodes" permission. Such users have
unrestricted access to all nodes. Then the node module's hook_access()
is called, and a TRUE or FALSE return value will grant or deny access.
This allows, for example, the blog module to always grant access to the
blog author, and for the book module to always deny editing access to
PHP pages.

If node module does not intervene (returns NULL), then the
node_access table is used to determine access. All node access
modules are queried using hook_node_grants() to assemble a list of
"grant IDs" for the user. This list is compared against the table.
If any row contains the node ID in question (or 0, which stands for "all
nodes"), one of the grant IDs returned, and a value of TRUE for the
operation in question, then access is granted. Note that this table is a
list of grants; any matching row is sufficient to grant access to the
node.

In node listings, the process above is followed except that
hook_access() is not called on each node for performance reasons and for
proper functioning of the pager system. When adding a node listing to your
module, be sure to use db_rewrite_sql() to add
the appropriate clauses to your query for access checks.

To see how to write a node access module of your own, see
node_access_example.module.

In version 5, Drupal added Installation Profiles (sometimes also confusingly called distribution profiles) to its list of features. An installation profile is basically nothing more than a list of required modules and a variety of configuration code which gets performed during installation to give Drupal a bit more oomph out of the box.

A "distribution" of Drupal is one or more installation profiles included with Drupal itself and all of the required modules. Distributions can either be offered as a convenience to site builders by bundling together frequently used components, such as Acquia Drupal, or they can be used to offer a version of Drupal specifically targeted to a unique use case, such as Open Publish. Dries has some heavy things to think about for anyone interested in getting into the distribution business, so I'll pause for a moment while you go and read that link.

Back? Great! So you've decided you want to share your ultimate Drupal site for whatever reason, and you want to do it in the fastest way possible. Then this article is for you!

Step 4: Remove settings.php.

Not a lot of fun to send your database credentials out into the world. Check for any other sensitive files that might be lying around too, like SSL certificate keys, .htpasswd files, and the like.

Want to create a front page that's styled differently from the rest of your site? Perhaps you need a separate admin theme? Or how about a login page which only shows the login block and nothing else? With a little PHP knowledge these problems are easy to solve.

Note: You must be using the PHPTemplate theme engine for your theme. An easy way to determine this is by looking for files ending in .tpl.php within your site's theme folder. PHPTemplate is compatible with Drupal 4.6 and up. As a matter of fact, it's the default theme engine for Drupal 4.7 since it combines the best of both worlds for designers and programmers. Designers get an easy way to manipulate HTML lightly sprinkled with PHP variables for dynamic content, and developers get a fast rendering template system that's a snap to extend. Here's what a template looks like using PHPTemplate.

Memcached is a service that allows entire database tables to be stored in memory, drastically speeding up queries to those tables and alleviating database load. In Drupal, the Memcached module allows you to store all cache tables in memory.

We've covered how to install Memcached before on Debian and on Mac OS X. But server software can vary significantly between sites, and this guide can be used to set up Memcached on Red Hat Enterprise Linux (RHEL) or CentOS, which are architecturally the same.

The 'Views' module is one of the mainstays of Drupal site building. It allows non-programmers to build highly customized listings of data that match certain criteria, then present that data in a variety of ways. A thumbnail gallery of photos, an alphabetized listing of site contributors, and a calendar display of upcoming events are all common applications of Views.

In this series of articles, we'll be taking a quick look at the architecture of the Views module and how its pieces work together; touring the different plug-in points that Views offers developers; and building a simple 'argument handler' for Views that demonstrates how the approach looks in the real world. A bit of knowledge about SQL will be useful for the article, as well as some understanding of object-oriented programming concepts like 'inheritance', but the code samples should be simple enough to tweak even if you're not a pro.

Under the hood, the pieces of a View can be divided into two different groups: the 'data' (stuff that affects the underlying database query that Drupal uses to retrieve the information for the View) and the 'presentation' (stuff that affects how that data is displayed to a user of the web site).