Fuzbolero . (fuzbolero)'s Public Profile in the Diigo Community

I am interested in Information sharing,projects and communities management,information security.. My favorite music are doorbell.

Member since Jun 02, 2007, follows 1 people, 12 public groups, 1478 public bookmarks (10666 total).

More »

Tags

Recent Tags:	drupal(0), cms(0), showcase(0), reference(0), security(0), 2009(0), qroykm(0), content-management(0), news(0), cms-related(0), events(0), programming(0), server(0), search(0), development(0), documentation(0), software(0), performance(0), file-management(0), opensource(0)
Top Tags:	d-imp(458), drupal(2654), cms(577), reference(893), security(1078), development(512), opensource(277), software(473), 1click-uncategorized-2007-06(99), Web2.0(114)

More »

Recent Bookmarks and Annotations

BTRFS - Linux file system - Wikipedia.org description on 2009-11-18
- 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]
- 4 more annotations...
- - Btrfs was merged into the 2.6.29-rc1 prerelease of the mainline Linux kernel, but remains marked as experimental and not ready for production use.
  - The developers advise users to not use it for anything but testing as the on-disk format is not finalized
  - Features
    
    Btrfs claims a "focus on fault tolerance, repair and easy administration.".^[8] As of 2009,^[update] it is still in heavy development and lacks many basic features. Theodore Ts'o, developer of ext3 and ext4 filesystems, said that Btrfs "has a number of the same design ideas that reiser3/4 had".^[9] Btrfs includes, or has plans for:^[10]
    
    Space-efficient packing of small files and indexed directories
    Dynamic inode allocation (no maximum number of files set at file-system creation time)
    Writable snapshots and snapshots of snapshots
    Subvolumes (separate internal filesystem roots)
    Object-level mirroring and striping
    Checksums on data and metadata (for strong integrity assurance; currently CRC-32C, alternatives are planned^[11])
    Compression (zlib; enabled by the mount option -o compress)
    Copy-on-write logging for all data and metadata
    Strong integration with device mapper for multiple device support, with several built-in RAID algorithms
    Online filesystem check and very fast offline filesystem check
    Efficient incremental backup and file-system mirroring
    Upgrading of filesystems from ext3 to Btrfs, and conversion back to the point of upgrading^[12]
    Solid-state drive (SSD) optimized mode (activated through the mount option -o ssd; no additional wear levelling through filesystem^[13])
    Online defragmentation
    Seed device support^[14]
  - Although Btrfs has no native feature that would make it a distributed or networked filesystem by itself, Oracle has started implementing CRFS (Coherent Remote File System), a network filesystem protocol specifically designed and optimized for networked storage on Btrfs.
Drupal wins best open source PHP CMS for second year in a row | drupal.org on 2009-11-12
- Drupal has won best open source PHP Content Management System for the second year in a row in the Packt Publishing 2009 Open Source CMS Awards. Drupal won by popular vote and a critical selection by a panel of judges. This award reflects the strong support of the Drupal community and our focus on quality which leads to critical acclaim and rapid adoption for large, high quality projects. Drupal won best overall open source CMS in 2007 and 2008.
Drupal 6 Book release: Search Engine Optimization | drupal.org on 2009-10-23
Web Open Font Format for Firefox 3.6 at hacks.mozilla.org on 2009-10-21
Support Drupal by Voting in Packt Publishing's Open Source CMS Award Competition | drupal.org on 2009-10-19
- go to Packt Publishing's Open Source CMS Award Web site before October 30 and cast your vote in the following categories:
  
  Hall of Fame
  Best Open Source PHP CMS
Delay-tolerant networking - Wikipedia.org on 2009-10-11
- Delay-tolerant networking (DTN) is an approach to computer network architecture that seeks to address the technical issues in heterogeneous networks that may lack continuous network connectivity. Examples of such networks are those operating in mobile or extreme terrestrial environments, or planned networks in space.
Drupal CMS contributed module: 2 Way Video Chat module | drupal.org on 2009-09-03
- 2 Way Video Chat (by VideoWhisper) is a premium high definition video communication software designed for instant 1 on 1 online video conferencing. It's a solution for conducting easy to setup face to face meetings without leaving your office or home. It's the easiest and most cost-effective way to meet somebody and discuss one on one.
JSON.org - lightweight data interchange format on 2009-09-03
- JSON (JavaScript Object Notation) is a lightweight data-interchange
  format. It is easy for humans to read and write. It is easy for machines to
  parse and generate. It is based on a subset of the
  JavaScript
  Programming Language,
  Standard
  ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely
  language independent but uses conventions that are familiar to programmers of
  the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python,
  and many others. These properties make JSON an ideal data-interchange language.
Drupal CMS and contributed modules: How to report a security issue | drupal.org on 2009-09-02
- If you discover a vulnerability in Drupal core or contributed module, keep it confidential. Mail us at security@drupal.org, do not post in the issue tracker. The security team will investigate your report and create a fix. When the issue is about a contributed module, the team coordinates with a module maintainer. When a fix is ready, an advisory urging users to upgrade is published.
- Some bugs take time to correct and the process may involve a review of the codebase for similar problems. Coordinating across time zones and work schedules can be time-consuming.
- 3 more annotations...
- - Do not disclose the vulnerability to anyone before the advisory is issued.
  - Provide us with a detailed report. As a minimum:
    
    Drupal version or module version.
    Steps to reproduce.
  - If you report a previously unknown vulnerability to the Drupal security team, you will be credited in the security announcement.
Coding standards | drupal.org on 2009-09-02
- The Drupal Coding Standards applies to code within Drupal and its contributed modules. This document is loosely based on the PEAR Coding standards.
- 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).
- 24 more annotations...
- - All binary operators (operators that come between two values), such as +, -, =, !=, ==, >, etc. should have a space before and after the operator, for readability. For example, an assignment should be formatted as $foo = $bar; rather than $foo=$bar;. Unary operators (operators that operate on only one value), such as ++, should not have a space between the operator and the variable or number they are operating on.
  - Control structures include if, for, while, switch, etc.
  - Control statements should have one space between the control keyword and opening parenthesis, to distinguish them from function calls.
  - You are strongly encouraged to always use curly braces even in situations where they are technically optional. Having them increases readability and decreases the likelihood of logic errors being introduced when new lines are added.
  - Functions should be called with no spaces between the function name, the opening parenthesis, and the first parameter; spaces between commas and each parameter, and no space between the last parameter, the closing parenthesis, and the semicolon.
  - Arguments with default values go at the end of the argument list. Always attempt to return a meaningful value from a function if one is appropriate.
  - Arrays should be formatted with a space separating each element (after the comma), and spaces around the => key association operator, if applicable
  - Drupal does not have a hard standard for the use of single quotes vs. double quotes. Where possible, keep consistency within each module, and respect the personal style of other developers.
  - With that caveat in mind: single quote strings are known to be faster because the parser doesn't have to look for in-line variables. Their use is recommended except in two cases
  - Always use a space between the dot and the concatenated parts to improve readability.
  - When using the concatenating assignment operator ('.='), use a space on each side as with the assignment operator
  - Inline documentation for source files should follow the Doxygen formatting conventions.
  - Non-documentation comments are strongly encouraged. A general rule of thumb is that if you look at a section of code and think "Wow, I don't want to try and describe that", you need to comment it before you forget how it works.
    
    Non-documentation comments should use capitalized sentences with punctuation. Sentences should be separated by single spaces. All caps are used in comments only when referencing constants, for example TRUE. Comments should be on a separate line immediately before the code line or block they reference.
  - Always use <?php ?> to delimit PHP code, not the shorthand, <? ?>. This is required for Drupal compliance and is also the most portable way to include PHP code on differing operating systems and set-ups.
  - The PHP language requires semicolons at the end of most lines, but allows them to be omitted at the end of code blocks. Drupal coding standards require them, even at the end of code blocks.
  - All source code files in the core Drupal distribution should contain the following comment block in the header:
  - This tag will be expanded by CVS to contain useful information
  - Functions should be named using lowercase, and words should be separated with an underscore. Functions should in addition have the grouping/module name as a prefix, to avoid name collisions between modules.
  - Constants should always be all-uppercase, with underscores to separate words.
  - If you need to define global variables, their name should start with a single underscore followed by the module/theme name and another underscore.
  - Classes should be named using "CamelCase."
  - Class methods and properties should use "lowerCamelCase"
  - All documentation files should have the file name extension ".txt" to make viewing them on Windows systems easier. Also, the file names for such files should be all-caps (e.g. README.txt instead of readme.txt) while the extension itself is all-lowercase (i.e. txt instead of TXT).
  - There is a helper command line script included with Drupal to check your code for style compliance. The code-style.pl file is located in the /scripts directory. To use the script just give your file as an argument when you execute the script (make sure the script is executable):
    
    ./code-style.pl path/to/file/example.module
    
    This will output a list of suggestions for where to improve your code.

More »

Groups

CMS-tech

5 members, 395 items

Collection of tech links related to CMS tools (Content Management Systems). Audience: "geeks" and also "normal people with an interest of managing their own personal information system.
Collaboration

528 members, 1182 items

Collaboration is an exciting domain given the Internet's ability to transcend boundaries, uniting individuals and networks in common goals. Let's celebrate and document this phenomena as it evolves before our eyes. Now that's collaboration!
Diigo Community

1078 members, 3441 items

Share your review, tips, tricks, and ideas for using Diigo here, and discuss our features, ideas for new features, anything Diigo related. Note that bookmarks posted to this group have no relation to 'Hot Bookmarks from the Diigo Community'.
Diigo Feature Requests Community

32 members, 35 items

Share & Discuss Which New Features u want to see in Diigo site & Toolbar. As An Obsessed Diigo User I Created this Group to Consolidate all Diigo Feature Requests . I Hope It will Help Diigo Creators to View all Requests in 1 Place. Lets Make Diigo BEST Social Website :)
Drupal performance issues

2 members, 1 items