HY-D-V1 Desktop is a new desktop interface built atop GNOME 3 using a combination of Webkit, JavaScript, Python and HTML. It is the desktop environment on Hybryde Fusion, a Linux desktop distribution based on Ubuntu Desktop. See some screen shots here.

Hybryde Fusion is the work of Larrieu Olivier, a French software developer. This tutorial shows how to install HY-D-V1 Desktop on Ubuntu 13.04 from the developer’s PPA (Personal Package Archives). It can also be installed on Ubuntu 12.04 LTS.

Note that as at the time of writing this article, the package can only be installed on the 32-bit editions, as the 64-bit packages failed to build.
:

1. Add the PPA to your system: Launch a shell terminal and type:

sudo add-apt-repository ppa:olivelinux36/hydv1-desktop-dev-raring

2. Update the package database: From the same shell terminal, type sudo apt-get update.

3. Install HY-D-V1 Desktop: Complete this step by typing sudo apt-get install hydv1desktop

4.Logout: Yep, you need to logout.

5. Log in with HY-D-V1 Desktop: Log back in, but not before selecting HY-D-V1 from the Session menu.

6. Enjoy!: Here are a few of screen shots from my test installation.

Both the left and right panels are retractable. The left one holds your favorite applications. Add applications on it by clicking on the “+” sign to the right of an application in the menu.

To remove an application from the Favorite panel, simply right-click on it.

Another screen shot showing a different desktop background. Note that with this installation on Ubuntu, you are not going to be able to test-drive other desktop environments like you would be able to from the origial distribution. That is, from Hybryde Fusion.

The post Install HY-D-V1 desktop on Ubuntu 13.04 appeared first on LinuxBSDos.com.

Hybryde Fusion is a new desktop distribution based on Ubuntu Desktop. Unlike most other Ubuntu-based distributions, it brings a few interesting features to the table.

Hybryde Fusion 13.04 is the distribution’s first release and the developer, Larrieu Olivier, is based in France. I’m still playing with a test installation, so this is not a review, but a presentation of a bunch of screen shots just to show what this distribution has to offer.

From the release number, you can probably guess that it is based on Ubuntu Desktop 13.04. But what you cannot guess from the name or release number is that it ships with its own desktop environment called HY-D-V1. It also makes it super easy to test-drive other desktop environments from the same installation, without ever rebooting the computer or logging out of the current desktop. I’ll get to that feature further down.

HY-D-V1 (I think that’s HY-D version 1 or HY Desktop version 1) is coded from GTK, Python, Webkit and JavaScript. The developer has made it clear that it is still in concept stage, but from what I’ve seen so far, it brings a very exciting graphical interface to the Linux desktop.

This is what HY-D-V1 desktop looks like. It has a top and a bottom panel. For the default install, the top panel simply holds the audio control and network manager applets. On the bottom panel are the date applet and five tabs.

On click, the tab at the extreme right of the bottom panel gives you access to the folders in your home directory, a utility to change the desktop background, applications menu, and access to system information.

Out of the box, there are 24 desktop background images to choose from. Just click on your choice and the background changes.

Clicking on the Apps Manager tab brings up an application menu window on the desktop. This is the same menu that you get by clicking on the Application tab to the left of the desktop.

Click on the Info tab and you get a window on the desktop that provides some details about HY-D-V1.

Aside from the first two sections of the Info window, the rest are in French. Unfortunately, my French is not that good to attempt a translation, and copying-and-pasting from the window is not supported, so I could not use a machine translation service to translate it. If you can read the language, I’ll post several screen shots of the window for you to translate.

Not quite sure what the tab to the far left of the desktop is for, but it looks like it is designed to show recently or frequently-used applications. Right next to it is the Applications tab, which functions like any other applications menu. It has some semblance to the Cinnamon menu. Applications under each category are revealed on hover, not on click.

This screen shot shows what you’ll see if the Magic tab is clicked. It is an overlay that shows date and time information as well as access to the APPS, SYS and CLOSE buttons.

The APPS button duplicates the function of the Applications tab, but offers the view of installed applications in a different and more visually-appealing manner. Application categories are represented by buttons in a top bar, and to the bottom-left of that bar is a search box.

Use the search box to look for installed applications.

Or click on an application category to reveal the applications under it.

The SYS button provides system information, as shown in this screen shot.

The post Hybryde Fusion: A very unique Linux distribution appeared first on LinuxBSDos.com.

Antergos Linux is a desktop distribution based on Arch Linux. The distribution started under the Cinnarch moniker with the objective of providing a Cinnamon-only desktop distribution using the same rolling release development model as its parent distribution.

It got its new name after the developers came to the conclusion that it was going to be extremely difficult to reconcile the Cinnamon and Arch Linux development models, opting instead to use GNOME 3 as the default desktop environment and provide support for other desktop environments.

This is my first review of the distribution. What I typically look for in desktop distributions are a good graphical installation, a sane and sensible default desktop configuration that just work, and all the graphical tools that will make managing the desktop easy for all users, especially those not familiar or not willing to use the command-line. In other words, a desktop distribution that you can install and start using without having to mess with configuration files or install simple tools that should have been installed out of the box is my type of distribution.

Does this first release of Antergos meet those criteria? Read on to find out.

Antergos features that are user-friendly: When reviewing a desktop distribution, I look at it from the perspective of a new user. That is somebody not familiar with the ins and outs of Linux and is looking for a modern desktop operating that just work and does not carry the unwanted baggage of a Microsoft operating system. For such a user, graphical interfaces that are easy to use are a must.

So what features does Antergos offer such a user?

Like almost all Linux distributions, the installation image is a Live CD image, and on boot, users are offered the options shown in the image below. (Note that if you opt to try the Live desktop, the system boots into a GNOME 3 desktop.)

If after trying the Live desktop and you want to install the system to your hard drive, or you chose the Graphical Installer option without booting into the Live desktop, what you get is a graphical installation program that is very intuitive to use. Cnchi, as it’s called, has the same look and feel as Ubiquity, the graphical installation program of Ubuntu Desktop. And like Ubiquity, offers manual and automated disk partitioning options.

This image shows the disk partitioning methods. The automated partitioning option works just like Ubiquity’s except that it create three partitions by default (Ubiquity creates primary and logical partitions and only creates two – / and Swap). The partitions created by Cnchi are mounted at /boot, Swap and / (root), and are all primary partitions.

The manual disk partitioning tool is very basic, just like that of Ubiquity.

This image shows the file systems supported by the installer. By default, ext2 is used for the boot partition, while ext4 is used for the root partition.

A GNOME 3 desktop, which the system boots into if you opt to try the Live system, is not your only choice of desktop environments. The installer offers three other desktop environments to choose from, though GNOME 3 is the default. This is much better than making separate installation images for each desktop environment, as many distributions do. So this is a plus for Cnchi.

Aside from aspects of the installer that are done right, the other nice feature of Antergos is PacmanXG, the graphical application manager. Regardless of the desktop environment you chose during installation, PacmanXG will be the graphical interface that you’ll be using to manage applications on Antergos, aside from also being able to use pacman from the command-line.

Unlike other graphical application managers, it is not dependent on Gtk or Qt, and is very fast and responsive. I do find that the right panel has one too many dropdown menus to choose from.

The options window of PacmanXG.

The autocomplete feature of the search utility returns results in a flash. It is many times faster than searching on Apper, the graphical package manager on Fedora.

Another nice feature of Antergos is the LibreOffice installer, which makes it easy to choose what component of the popular Free Software Office suite to install. Initially, I thought that with PacmanXG, an application-specific installer of this sort is not necessary, but on second thoughts, having a standalone installer used for installing an application with many different components is not necessarily a bad thing.

The post Antergos Linux 2013.05.12 review appeared first on LinuxBSDos.com.

It’s been in beta mode since it was announced back in January, but now, the NVIDIA SHIELD is ready for prime time. Or at least, you can pre-order it now.

NVIDIA SHIELD is a portable gaming device powered by the Tegra 4 processor, the same processor you’ll find inside HP’s SlateBook and a few other mobile computing devices. The Tegra 4 is a 5-core (4+1 core), ARM Cortex-A15 processor with a maximum clock speed of 1.9 GHz, powerful GeForce graphics, and 2 GB RAM. You may view the full specs here.

On the software side, it will ship with Android Jelly Bean, Google Play, NVIDIA TegraZone and a few popular games – Sonic 4 Episode II THD, Expendable: Rearmed, Hulu Plus, TwitchTV.

It also features an experimental (beta) version of Play PC, NVIDIA’s PC game streaming technology that enables you to wirelessly interface with your GeForce® GTX-powered computer from the SHIELD. The downside to Play PC is that streaming is only supported from Windows 7 or 8. It’s a major disappointment when a mobile Linux distribution fails to support regular desktop Linux distributions.

In any case, here’s a really cool video showcasing the SHIELD in action. The unit retails for US$349.00. Residents in the US and Canada may pre-order from here.

The post NVIDIA SHIELD: Android game console, with Tegra 4 inside appeared first on LinuxBSDos.com.

The Tegra 4-powered SlateBook x2 running Android Jelly Bean (4.2.2) is the latest split-personality portable computer from HP.

Detailed hardware specs have not be made available, but we do know that if will have an IPS panel with a screen resolution of 1920×1200, USB and HDMI ports. That’s about all we know about the hardware, but I’m sure it will come with other standards, like WiFi, Bluetooth, camera (hopefully, front and rear), etc.

The beauty of these new HP hybrids, is they come with dual battery, one in the detachable tablet portion, and another in the base. The HP Split x2, a similar device powered by an Intel Core i3, also has dual storage capability – an SSD in the tablet portion, and room for a standard laptop HDD in the base, so I expect the SlateBook x2 to have the same storage options. That will make for fun hardware configuration.

I don’t have an Android device and I’m not in a hurry to get one (my HP TouchPad is still kicking), but the Tegra 4 is a quad core ARM Cortex-A15 processor with a maximum clock speed of 1.9 GHz, powerful GeForce graphics, and 4 GB RAM, so my interest here is to check out the possibility of loading my favorite desktop distribution on it. And if it passes the desktop distro test, the dual-storage option will make dual-booting more fun and easier.

Google’s ChromeBook Pixel looks good and cool and is seems to have more fancy hardware features, but it has an Apple-high price tag. The Slatebook x2 on the other hand, when it’s starts shipping in August, will start at US$480.00. Dual-storage models will probably carry a higher price tag. More about it SlateBook x2 here.

The post SlateBook x2: Tegra 4-powered Android hybrid appeared first on LinuxBSDos.com.

ROSA Desktop Fresh LXDE is the end-user edition of ROSA Desktop that uses the Lightweight X11 Desktop Environment. This is not the same as the LXDE edition which was released in June 2012. That one is the enterprise edition, which ships with Debian-style stable Linux kernel and software, and uses the Marathon code name. (See ROSA 2012 LXDE review
.)

This alpha release, like the other end-user releases, uses the Fresh code name, and ships with bleeding-edge software and the latest or close-to-the-latest Linux kernel. Note that the default desktop environment of both the Marathon and Fresh line of ROSA Desktop is KDE. And there is also a GNOME 3 edition. You may view screen shots from a test installation of the pre-release version of that GNOME 3 edition here.

Since this release is the first alpha edition, it is not feature complete, but some important components are already in place, while some others have yet to be implemented. A short list of the main features that are already in place follows:

• Kernel 3.8.x (in the beta edition, the kernel will be 3.8.5)
• LightDM as default desktop manager
• Systemd DM setup (you need now use systemctl enable/disable xyzDM for setup)
• NetworkManager in place of ROSA drakx-net network scripts
• X-server 1.13.3 with detect improvements
• Intel driver 2.21.6
• Some initscrips improvements

Features that are yet to be completed are:

• GTK3 theme
• lxde-control-center is still buggy
• Rewriting of drakedm for use with systemd
• Lighdm still needs some improvements
• List of installed and available software is incomplete

Here are a few screen shots of this alpha release taken from a test installation in a virtual environment. Please note that installation images have not be made available for public download. And I’ve not been told when that will happen.

The default desktop.

The output of uname -r.

The control center.

another view of the control center.

An advanced view of the control center.

The graphical software manager.

The beauty of this edition of ROSA Desktop is it will provide users (when it becomes available for public download) with a beautifully configured lightweight desktop that will run just as smoothly on computers will low resources as it will on the latest hardware. Plus all the bleeding-edge software and kernel you expect to find on any edition of ROSA Desktop Fresh line. Stay tuned!

The post ROSA Desktop Fresh LXDE alpha preview appeared first on LinuxBSDos.com.

The release of Apache OpenOffice 4 will not happen tomorrow, but it is getting close. How close? Well, let’s just say it will happen soon. In months time, not weeks.

To usher in what will be a milestone release for the Free Software Office suite, The Apache Software Foundation (ASF) wanted a new logo to replace the old OpenOffice logo, and requested design submissions from the community. There were 40 entries.

Users were then asked to vote on their favorite entries in a survey conducted between April 24 and May 2 of this year. Six of the 40 entries receiving the most votes were announced by the ASF in a blog post on May 10. Designers of those top entries were then asked to refine and fine tune their entries using user feedback as a guide.

The six entries are shown below. If you did not participate in the original survey, this is your chance to have an input. I did not participate in the original survey, but if I did, the order that these images are shown below shows how I would have rated them, from highest to lowest.

1. One: This would have been my top pick mostly because of the symbolism of the open book. I would rather have the feather positioned like a pen writing on the open book. That’d be the perfect logo for Apache OpenOffice.

2. Two: If what this stands for doesn’t make sense to you, that’s an “a” merged with an infinity symbol. This looks nice too, but it does not carry the same symbolic weight as the first one. My only suggestion for this will be to make the “a” a little bit more obvious.

3. Three: The remaining four are just minor variations of the original OpenOffice logo. Which one of the six logos would be your choice, and what refinements will you suggest? Let the designers know your thoughts here.

4. Four:

5. Five:

6. Six:

See the survey here

The post Apache OpenOffice: Help pick a new logo appeared first on LinuxBSDos.com.

The Software Freedom Conservancy has launched a fundraising or crowdfunding campaign for a FOSS accounting software for non-profit organizations (NPOs).

The need for such an accounting software “usable by non-technical bookkeepers, accountants, and non-profit managers” arose because NPOs are spending significant amounts of money for licensing proprietary accounting applications.

The goal of this fundraising campaign is to raise $75,000 USD that will be used to hire a full time developer to work on this application, with development to be completed in two phases – Phase 0 and Phase 1.

The task for the first phase, Phase 0, will be to study existing FOSS accounting applications and choosing the one most suitable to base the project on.

The second phase is when modification and improvement of the chosen codebase will begin, with the goal of creating an application with the following features:

• Basic accounts payable/receivable (with invoicing)
• Tracking and reporting of non-profit income types (related business income, unrelated business taxable income, donations, etc.)
• Basic backup documentation tracking for expenses and payments
• Basic bank statement reconciliation reporting
• Basic annual audit preparation reporting
• Ability to easily handle all these features on a project-by-project subset of the accounts, and to easily export and excise that subset from the system.
• Multi-currency support and reporting

Read more about the campaign and how to donate here.

The post Crowdfunding a FOSS accounting software for NPOs appeared first on LinuxBSDos.com.

Why does your government want a backdoor in all popular Internet products and services? That’s like asking why a prostitute wants you to pay for her services, or why a politician wants a bribe (or is that a campaign contribution?).

A backdoor in all telecommunications devices and services is already made possible by CALEA, the Communications Assistance to Law Enforcement Act. (See also CALEA FAQ.) Now they want to step it up a notch and compel popular Internet companies and social networks like Facebook and Google to give law enforcement agencies real time monitoring capabilities of all online communication. It’s not enough that they can already get anything they want by just submitting a letter to these online services.

According to a Washington Post report, “a government task force is preparing legislation that would pressure companies such as Face­book and Google to enable law enforcement officials to intercept online communications as they occur.”

Joe Hall, a staff technologist at the Center for Democracy & Technology, said the “proposal has the potential to make our communications less secure,” because “once you build a wiretap capability into products and services, the bad guys will find a way to use it.”

That makes sense to me, but try telling that to a group that loves power. If this does not want you to always use Free Software services and applications, nothing will. And if these guys succeed in making this bad idea law, it will give service like Identi.ca an opportunity to be very popular, at least for folks like us.

The post A backdoor in all Internet products and services? appeared first on LinuxBSDos.com.

As somebody who fully embraces the Free Software principle, I have no need for Windows 8 in my environment. Never used any version of Windows, and never will.

Previous versions of Windows were bad enough, but Windows 8, with its Restricted Boot requirements, have made dual-booting a Linux distribution with Windows 8 on store-bought computers a royal pain in the rear end.

Since we don’t have the political clout to bribe (lobby) our elected officials to break the unholy alliance between Microsoft and hardware vendors, educating Windows users on the benefits of using Linux is the best we can do – for now.

Most of my Windows-using friends have refused to upgrade to Windows 8. The few that have, are not very happy with it. I wage a personal campaign, using dual-booting as the gateway. To make it easier to convince your friends to “Close Windows and open doors,” the Free Software Foundation has set up a Web page that you can send to your friends. The message is simple, but effective. Upgrade from Windows 8.

We frown upon drinking and driving, and texting and driving. Add using Windows 8 to that list. Note that trying to get your friends to quit cold-turkey is not the best way. Getting them to test-drive your favorite Linux distribution from a CD or USB stick is much better.

The post Windows 8: The most important reason to switch to Linux appeared first on LinuxBSDos.com.

IFC6410 is a single-board, SoC computer powered by Qualcomm’s Snapdragon S4 Pro processor, the same processor that powers Google’s Nexus tablet computer and several other mobile devices.

I’ve become interested in single-board computers that are not controlled by an industry monopoly because I think they present the best technical opportunity to break the strangle-hold that Microsoft has on hardware and hardware vendors.

Efforts are underway to see how we can take advantage of these Pico-ITX form-factor single-board, SoC computers. I just profiled the EMB-2500 from Habey USA. It looks like a nice unit and I might be able to get my hands on a test unit.

This 1.7 GHz quad core Snapdragon S4 Pro-powered unit looks good too. It’s also production-ready, so you can order one – for $149. It’s manufactured by Inforce Computing, an embedded hardware vendor with offices in Bangalore, India, and Fremont, California USA.

Here are some of the specs (detailed specs here):

• Krait CPU, 4-core. Independent clock-scaling per core
• Gigabit Ethernet, 802.11 b/g/n WiFi and Bluetooth 4.0
• Micro SD card connector, 4 GB eMMC, and external SATA
• Micro HDMI and LVDS display connectors
• up to 20MP camera support

As an end-user (non-dev), the EMB-2500 looks more appealing than this unit, but there’s lots of room for improvements for both units. Here’s the introductory video.

The post IFC6410: Snapdragon S4 Pro-based single board computer appeared first on LinuxBSDos.com.

The EMB-2500 is the latest single-board, SoC computer to be released this year. Ever since the Raspberry Pi hit the streets and became hugely popular with its target audience, there has been several similar attempts to outdo it, but none has shipped with standard storage connectivity that the average computer user can use.

With the EMB-2500, SATA storage connectivity has come to an ITX form-factor, single-board SoC computer.

The EMB-2500 is manufactured by Habey USA, a subsidiary of NORCO Intelligent Technology Co., a hardware manufacturing outfit base in Shenzhen, China. What sets the EMB-2500 apart from similar, Pico-ITX form-factor boards is that it comes with almost all the connectivity you’ll find on a standard motherboard. And that’s why I think it will be a good buy.

At the core of the EMB-2500 is a 1 GHz Freescale i.MX6 processor, which could be single core, dual core or quad core, with 1 GB on-board DDR3 RAM.

Here are other pertinent specs of the EMB-2500 (detailed specs here):

• OS: Linux and Android 4 support
• Storage: 1x SATA 3Gb/s, 1x SD, on-board NAND flash (4GB default
• Network: Gigabit Ethernet. Optional on-board WiFi
• Connectivity: HDMI 1.4, VGA, LVDS (Resolution in the 1920 x 1080 range). 2x USB2.0, 2x USB2.0 header, 1x mini USB2.0 OTG.
• Integrated 3D graphics and 1080p video codec engine

Prices for the boards have not been released yet, but I’ve been told that for retail, expect to be able to buy one for between $140.00 to $180.00, depending on the processor and other configuration options. If I’m lucky, I should be able to get one for review, so check back for a possible hands-on review later.

The post ARM-based EMB-2500: Like Raspberry Pi, but much better appeared first on LinuxBSDos.com.

Kali Linux is the latest incarnation of BackTrack Linux, a distribution designed for penetration testing and security professionals. The last edition of BackTrack was BackTrack 5 R3, with GNOME 2 and KDE installation images for 32- and 64-bit architectures made available for download. Released Kali Linux ISO image is for the GNOME 3 desktop, with a customized GNOME Shell.

However, Kali Linux’s build system makes it relatively easy to roll your own (custom) installation image using other well-known desktop environments, like KDE, MATE, LXDE, and Xfce. This article shows how to build a custom installation image built around KDE.

NOTE: If you are still using BackTrack, you might want to consider switching to Kali Linux. It’s based on Debian and offers more features than its predecessor.

A custom Kali Linux image can be built from an existing installation of Kali Linux, or form any other Linux distribution, The easiest route is to download Kali Linux 1.0 and install it in a virtual environment. From it, you can then build a custom image with your choice of desktop environment.

The instruction for building a custom Kali Linux ISO image is pretty simple. I chose to build mine using a combination of the default setting in the build environment and the installation instructions. The result is a 2.2 GB installation image of Kali Linux KDE.

There’s nothing special to it, but if you want to build one, these are the steps I took.

1. Install Kali Linux 1.0 in a virtual environment. You may download an installation image from here.

2. Set up the build environment. To prepare the build environment, the official documentation called for the installation of four packages. However, I found that two of those packages (git and kali-archive-keyring) were already installed on a new installation of Kali Linux 1.0, so I only needed to install the other two, which are cdebootstrap and kali-archive-keyring.

Therefore to prepare the build environment, issue the following commands:

I. Install required packages with this command: apt-get install cdebootstrap kali-archive-keyring.

II. Clone the build environment with: git clone git://git.kali.org/live-build-config.git.

III. The build environment is in a directory called live-build-config. The next step is to change (cd) into that directory and start messing with it. So type this command: cd live-build-config.

IV. Then run this command: lb build. The system will respond with an error message, and will output a command for you to run that will take care of the cause of the error. The command it will output is: ln -sf wheezy /usr/share/live/build/data/debian-cd/kali.

This image shows the commands as I used them in my test installation.

This one shows the output of the lb build command without the error message.

3. Configuring the Kali ISO Build In the official documentation, this step is optional, but this is where you have to choose the desktop environment you wish to use for the build. The file to modify is kali.list.chroot in the config/package-lists directory. So change to that directory with: cd config/package-lists and open the file with; nano -w kali.list.chroot.

This is section of the file that you have to modify to use the desktop environment that you prefer. To use KDE, just uncomment everything, but the KDE line. Note that the default in this file is slightly different from what you’ll find in the official documentation.

This is the same file with the KDE lines uncommented. The two lines shown here worked just fine for me.

4. Build the ISO After modifying the file, type: lb config --architecture i386. Follow that with: lb build. That last command will take more than a few hours to build, so take a break or a nap. When it’s completed, you should see an ISO file of about 2.2 GB. That’s your custom Kali Linux ISO KDE image. You may know burn it to a DVD or transfer it to a USB key or flash drive.

This image shows a test installation of Kali Linux ISO KDE with the classic menu.

And this shows it with the Kickoff menu. Corrections, suggestions and requests are welcome.

The post Kali Linux ISO: Build a custom KDE image appeared first on LinuxBSDos.com.

While we are waiting for some kind of reform of the US patent system, it’s good too see a major technology outfit like Google going solo with regards to taking legal action on a particular category of patent it owns. It’s a patent pledge that goes like this: We won’t be the first to sue.

It’s a stance Google calls The Open Patent Non-Assertion Pledge. The OPN Pledge, for short. The official language of The Pledge states that Google will “…not to sue any user, distributor or developer of open-source software on specified patents, unless first attacked.” (Note the emphasis.)

But patent pledge does not apply to all patents. That’d be counter productive to a commercial company. It just applies to free or open software “to which Google has contributed little or no code, or has not otherwise incurred any patent license obligations under patents it owns.”

The main points of the patent pledge are:

• Transparency. Patent holders determine exactly which patents and related technologies they wish to pledge, offering developers and the public transparency around patent rights.
• Breadth. Protections under the OPN Pledge are not confined to a specific project or open- source copyright license. (Google contributes a lot of code under such licenses, like the Apache or GNU GPL licenses, but their patent protections are limited.) The OPN Pledge, by contrast, applies to any open-source software—past, present or future—that might rely on the pledged patents.
• Defensive protection. The Pledge may be terminated, but only if a party brings a patent suit against Google products or services, or is directly profiting from such litigation.
• Durability. The Pledge remains in force for the life of the patents, even if we transfer them.

Of all the patents that Google owns to which this pledge can apply, only 10, all related to MapReduce, are covered under the pledge. But that’s sure to change, as the company has promised to add more to the list. A detailed FAQ is available here.

The post Google’s patent pledge: We won’t be the first to sue appeared first on LinuxBSDos.com.