mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-27 02:30:10 +08:00
清除过期文章，回收过期未完成文章
以下诸位逾期未完成的文章收回： @barney-ro @mdjsjdqe @felixonmars (3篇！) @CHINAANSHE @forsil
This commit is contained in:
wxy
parent
dffdcdb118
commit
b3235ccc86
@ -1,38 +0,0 @@
|
||||
Translating By instdio
|
||||
"Fork Debian" Project Aims to Put Pressure on Debian Community and Systemd Adoption
|
||||
================================================================================
|
||||
> There is still a great deal of resistance in the Debian community towards the upcoming adoption of systemd
|
||||
|
||||
**The Debian project decided to adopt systemd a while ago and ditch the upstart counterpart. The decision was very controversial and it's still contested by some users. Now, a new proposition has been made, to fork Debian into something that doesn't have systemd.**
|
||||
|
||||
|
||||
|
||||
systemd is the replacement for the init system and it's the daemon that starts right after the Linux kernel. It's responsible for initiating all the other components in a system and it's also responsible for shutting them down in the correct order, so you might imagine why people think this is an important piece of software.
|
||||
|
||||
The discussions in the Debian community have been very heated, but systemd prevailed and it looked like the end of it. Linux distros based on it have already started to make the changes. For example, Ubuntu is already preparing to adopt systemd, although it's still pretty far off.
|
||||
|
||||
### Forking Debian, not really a solution ###
|
||||
|
||||
Developers have already forked systemd, but the projects resulted don't have a lot of support from the community. As you can imagine, systemd also has a big following and people are not giving up so easily. Now, someone has made a website called debianfork.org to advocate for a Debian without systemd, in an effort to put pressure on the developers.
|
||||
|
||||
"We are Veteran Unix Admins and we are concerned about what is happening to Debian GNU/Linux to the point of considering a fork of the project. Some of us are upstream developers, some professional sysadmins: we are all concerned peers interacting with Debian and derivatives on a daily basis. We don't want to be forced to use systemd in substitution to the traditional UNIX sysvinit init, because systemd betrays the UNIX philosophy."
|
||||
|
||||
"We contemplate adopting more recent alternatives to sysvinit, but not those undermining the basic design principles of 'do one thing and do it well' with a complex collection of dozens of tightly coupled binaries and opaque logs," reads the [website][1], among a lot of other things.
|
||||
|
||||
Basically, the new website is not actually about a Debian fork, but more like a form of pressure for the [upcoming vote][2] that will be taken for the "Re-Proposal - preserve freedom of choice of init systems." This is a general resolution made by Ian Jackson and he hopes to get enough support in order to turn back the decision made by the Technical Committee regarding systemd.
|
||||
|
||||
It's clear that the debate is still not over in the Debian community, but it remains to be seen if the decisions already made can be overturned.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Fork-Debian-Project-Started-to-Put-Pressure-on-Debian-Community-and-Systemd-Adoption-462598.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:http://debianfork.org/
|
||||
[2]:https://lists.debian.org/debian-vote/2014/10/msg00001.html
|
||||
@ -1,30 +0,0 @@
|
||||
Red Hat acquires FeedHenry to get mobile app chops
|
||||
================================================================================
|
||||
Red Hat wants a piece of the enterprise mobile app market, so it has acquired Irish company FeedHenry for approximately $82 million.
|
||||
|
||||
The growing popularity of mobile devices has put pressure on enterprise IT departments to make existing apps available from smartphones and tablets -- a trend that Red Hat is getting in on with the FeedHenry acquisition.
|
||||
|
||||
The mobile app segment is one of the fastest growing in the enterprise software market, and organizations are looking for better tools to build mobile applications that extend and enhance traditional enterprise applications, according to Red Hat.
|
||||
|
||||
"Mobile computing for the enterprise is different than Angry Birds. Enterprise mobile applications need a backend platform that enables the mobile user to access data, build backend logic, and access corporate APIs, all in a scalable, secure manner," Craig Muzilla, senior vice president for Red Hat's Application Platform Business, said in a [blog post][1].
|
||||
|
||||
FeedHenry provides a cloud-based platform that lets users develop and deploy applications for mobile devices that meet those demands. Developers can create native apps for Android, iOS, Windows Phone and BlackBerry as well as HTML5 apps, or a mixture of native and Web apps.
|
||||
|
||||
A key building block is Node.js, an increasingly popular platform based on Chrome's JavaScript runtime for building fast and scalable applications.
|
||||
|
||||
From Red Hat's point of view, FeedHenry is a natural fit with the company's strengths in enterprise middleware and PaaS (platform-as-a-service). It adds better mobile capabilities to the JBoss Middleware portfolio and OpenShift PaaS offerings, Red Hat said.
|
||||
|
||||
Red Hat plans to continue to sell and support FeedHenry's products, and will continue to honor client contracts. For the most part, it will be business as usual, according to Red Hat. The transaction is expected to close in the third quarter of its fiscal 2015.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.computerworld.com/article/2685286/red-hat-acquires-feedhenry-to-get-mobile-app-chops.html
|
||||
|
||||
作者：[Mikael Ricknäs][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.computerworld.com/author/Mikael-Rickn%C3%A4s/
|
||||
[1]:http://www.redhat.com/en/about/blog/its-time-go-mobile
|
||||
@ -1,58 +0,0 @@
|
||||
Suse enterprise Linux can take your system back in time
|
||||
================================================================================
|
||||
> Suse Linux Enterprise Server 12 features a new system snapshot and rollback capability
|
||||
|
||||
The newest enterprise edition of the Suse Linux distribution allows administrators to go back in time, for instance, to immediately before they made that fatal system-crippling mistake.
|
||||
|
||||
Suse Linux Enterprise Server 12 (SLES 12) features a system snapshot and rollback capability that allows the user to boot the system to an earlier configuration, should the latest one unexpectedly fail.
|
||||
|
||||
Such a capability can be handy for undoing a system configuration change that did not turn out as expected. For instance, an administrator might have the SLES computer in a perfectly fine running state, but then install a botched software update, or make a change that destroys the kernel. Typically, Unix systems have been unforgiving about such mistakes, forcing the administrator to reinstall the system software from scratch, should they not know how to undo the unfortunate change.
|
||||
|
||||
"This stuff happens, for whatever reason," said Matthias Eckermann, Suse senior product manager. "So the admin has an emergency exit, so to speak."
|
||||
|
||||
Users of Microsoft Windows and Apple Macintosh systems have long enjoyed rollback functionality within their respective OSes, but this capability had been missing in Unix-based systems such as Linux, at least as a native function of the OS.
|
||||
|
||||
For this functionality, the Suse team used the [Btrfs][1] file system (B-tree file system, often pronounced as "Butter FS"), an open-source file system developed by Oracle engineer Chris Mason ([now at Facebook][2]). Mason created Btrfs to address emerging enterprise requirements such as the ability to make snapshots and to scale across multiple storage nodes.
|
||||
|
||||
Although Btrfs is supported in the mainline Linux kernel, SLES is the first major Linux distribution to use Btrfs as the default file system. "Over the last five years, we specifically focused on making Btrfs enterprise-ready," Eckermann said.
|
||||
|
||||
The rollback capability also relies on the open-source tool [Snapper][3], first developed by Suse, to manage the snapshots.
|
||||
|
||||
The Suse team integrated Snapper with SLES so that users now have the ability, when the OS is first being loaded, to boot into an earlier snapshot of the system. "Whoever installs SLES 12 gets this capability by default," Eckermann said.
|
||||
|
||||
SLES also integrated Btrfs with the [Samba Windows file server][4], which makes Linux files accessible to Windows machines. For Windows users, SLES can now make multiple snapshots of a file appear as different versions of a file, which are all accessible.
|
||||
|
||||
Initially, Enterprise Suse supports rollbacks for only system changes, though users can also deploy it to handle changes in a user's home directory, in which data is typically kept. "We already have it running, but it is not supported," Eckermann said. Users can continue to use ext3, ext4 or some other traditional Linux file system as their default.
|
||||
|
||||
SLES 12, released Monday, comes with a number of other features as well. Like other distributions, SLES has [caught the fever for Docker containers][5] and now comes with a built-in framework to run this virtualization technology. For the first time, the package also provides geo-clustering, which allows the user to build replicate clusters across different geographic regions.
|
||||
|
||||
An organization could use geo-clustering, for instance, to set up multiple copies of a single cluster in data centers around the world, so if one or more regions go offline, the others can continue operations unabated, Eckermann said.
|
||||
|
||||
Suse [is among the world's most widely used distributions][6] of Linux, along with Ubuntu/Debian, and Red Hat Enterprise Linux. A free version is available under OpenSuse and Suse Linux offers a commercial edition packaged for enterprise usage.
|
||||
|
||||
Suse Linux's parent company, Attachmate, is in the process of merging with Micro Focus. Eckermann expects no major changes in the operations of Suse Linux resulting from the new ownership.
|
||||
|
||||
SLES 12 is [offered at an annual subscription][7] of US$349 per server. A free 60-day trial is also available.
|
||||
|
||||
|
||||
|
||||
Through the combined powers of the Btrfs file system and the Snapper utility, SUSE Enterprise Linux can now take snapshots of the system, and roll back to an earlier configuration if necessary.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.computerworld.com/article/2838950/suse-enterprise-linux-can-take-your-system-back-in-time.html
|
||||
|
||||
作者：[Joab Jackson][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.computerworld.com/author/Joab-Jackson/
|
||||
[1]:https://btrfs.wiki.kernel.org/index.php/Main_Page
|
||||
[2]:http://www.phoronix.com/scan.php?page=news_item&px=MTUzNTE
|
||||
[3]:http://snapper.io/
|
||||
[4]:http://www.samba.org/
|
||||
[5]:http://www.pcworld.com/article/2838452/canonical-celebrates-cloud-freedoms-with-new-ubuntu.html
|
||||
[6]:http://distrowatch.com/table.php?distribution=suse
|
||||
[7]:https://www.suse.com/products/server/how-to-buy/
|
||||
@ -1,41 +0,0 @@
|
||||
Mozilla to Launch Brand New Developer Web Browser Next Week
|
||||
================================================================================
|
||||
**When you woke up this morning you probably didn’t expect to come online and see the words ‘Mozilla’, ‘New’, and ‘Web Browser’ writ large across the web. **
|
||||
|
||||
But that my bed-headed compadre is precisely what you’re looking at.
|
||||
|
||||
注：youtube 地址，发布的时候不行做个链接吧
|
||||
<iframe width="750" height="422" frameborder="0" allowfullscreen="" src="https://www.youtube.com/embed/Ehv5u-5rE8c?feature=oembed"></iframe>
|
||||
|
||||
### Mozilla – Pushing Boundaries ###
|
||||
|
||||
Mozilla has always been at the forefront of pushing open source, open standards and open access. They steer one of the most popular desktop browsers in the world. Their open-source Linux mobile OS [is sold on 12 smartphones from 13 operators in 24 countries][1]. They’re [even taking on the Google Chromecast][2]!
|
||||
|
||||
Their desire to democratise the web shows no sign of abating. In a teaser posted on the Mozilla Blog this morning the company has announced a new effort to push boundaries further — this time for developers rather than users.
|
||||
|
||||
Teased as something “unique but familiar”, the company intend to release a brand new browser based on Firefox but designed by developers, for developers. Mozilla say it integrates “powerful new tools like [WebIDE][3] and the [Firefox Tools Adapter][4]”.
|
||||
|
||||
> “When building for the Web, developers tend to use a myriad of different tools which often don’t work well together. This means you end up switching between different tools, platforms and browsers which can slow you down and make you less productive.”
|
||||
|
||||
### #Fx10 ###
|
||||
|
||||
The “Firefox Developer Browser” is being touted for an initial release date of November 10. It’s not yet known what platforms it will target but since this is a) Mozilla and b) aimed at developers it’d be a huge shock if Linux builds weren’t readily available on day dot.
|
||||
|
||||
Mozilla say those interested should sign up for their [Hacks newsletter][5] to receive notification when the browser is released.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/mozilla-launch-brand-new-developer-focused-web-browser
|
||||
|
||||
作者：[ Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:https://twitter.com/firefox/status/522175938952716289
|
||||
[2]:http://www.omgchrome.com/mozillas-chromecast-rival-leaks-online/
|
||||
[3]:https://hacks.mozilla.org/2014/06/webide-lands-in-nightly/
|
||||
[4]:https://hacks.mozilla.org/2014/09/firefox-tools-adapter/
|
||||
[5]:https://hacks.mozilla.org/newsletter/
|
||||
@ -1,36 +0,0 @@
|
||||
Ubuntu Touch RTM Gets Major Update – Video Tour
|
||||
================================================================================
|
||||
**new Ubuntu Touch RTM version has been released and the developers have made a number of important fixes, not to mention all the improvements that have been made to the backend.**
|
||||
|
||||
The Ubuntu Touch RTM stable images don't arrive all that often. Only six have been launched so far and each new version is sensibly better than the previous one. The current release is no exception, although it seems to have a longer and more complex changelog than the previous one.
|
||||
|
||||
Long gone are the days when a Mir update would break Ubuntu, but now all sorts of smaller problems are cropping up. In fact, all landings have been suspended before this new update was released, in an effort to track down and correct all the major bugs. Some problems still remain, but none of them should be an inconvenience.
|
||||
|
||||
### This is just the RTM branch, not the final version ###
|
||||
|
||||
Ubuntu Touch is still a work in progress, but, from the looks of it, the developers are homing in the final version. It shouldn't take too long now and we might get it in a month or so. That would be a fair assessment, if Meizu's plans to launch an Ubuntu phone in December holds.
|
||||
|
||||
"Good news! As per earlier announcement we promoted a new image to the ubuntu-rtm/14.09 channel! Please enjoy image #6 (previously known as #140 for krillin, #118 for mako and #112 for x86). Because of those we plan on promoting another image as soon as possible if those issues get fixed. But no worries - no freezes required this time. The landing gates will remain opened until the next serious promotion! Once again big thanks to everyone involved!" [said][1] Canonical's Łukasz Zemczak.
|
||||
|
||||
There are still a few minor issues, they will be corrected very soon. For example, the user metrics that could be found on the lock screen are no longer changing with a double tap, the media hug might strain the CPU in certain situations, and the Unity 8 environment might crash from time to time.
|
||||
|
||||
On the upside, Ubuntu Touch should be much more stable now, the video playback now works properly in landscape mode, the Unity 8 desktop has been updated, and a lot of critical changes have been made.
|
||||
|
||||
Users can test Ubuntu Touch RTM on Nexus 4 and Nexus 7 devices, and the official website has comprehensive [wiki][2] that details the installation.
|
||||
|
||||
youtu.be链接地址：[http://youtu.be/_DtNvz_WVu8][3]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Ubuntu-Touch-RTM-Gets-Major-Update-Video-Tour-464075.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:https://lists.launchpad.net/ubuntu-phone/msg10368.html
|
||||
[2]:https://wiki.ubuntu.com/Touch/DualBootInstallation
|
||||
[3]:http://youtu.be/_DtNvz_WVu8
|
||||
@ -1,39 +0,0 @@
|
||||
Canonical Launches LXD Open Source Virtualization Container
|
||||
================================================================================
|
||||
> Canonical is launching a new container-based virtualization hypervisor for its open source Ubuntu Linux operating system, called LXD. How will it get along with Docker?
|
||||
|
||||
As open source container-based virtualization explodes in popularity, perhaps it was only a matter of time before [Canonical][1] announced its own, homegrown virtualization container system to contend with [Docker][2]. That's what the company has now done with the launch of [LXD][3] for [Ubuntu Linux][4].
|
||||
|
||||
Canonical announced the hypervisor— which the company is pronouncing "lex-dee," the better, I suppose, to avoid confusion with the Schedule 1 drug of similar nomenclature—Nov. 4. The pitch for the tool, which is basically a server for the [LXC][5] virtualized container system built into the Linux kernel, goes like this:
|
||||
|
||||
> Imagine you could launch a new machine in under a second, and that you could launch hundreds of them on a single server. Hundreds! Now, imagine that you have hardware-guaranteed security to ensure that those machines can’t pry or spy on one another. Imagine you can connect them separately and securely to networks. And imagine that you can run that on a single node or a million, live migrate machines between those nodes, and talk to all of it through a clean, extensible REST API. That's what LXD sets out to deliver.
|
||||
|
||||
LXD will also feature tight integration with OpenStack—in fact, it's part of Canonical's [OpenStack][6] Juno for Ubuntu—as well as hardware-level security protections, according to the company, which said it is working with chip manufacturers (it hasn't indicated which ones) on the latter technology.
|
||||
|
||||
This is all pretty cool. If Canonical fully implements these features, LXD could go a long way toward making LXC a truly enterprise-ready containerized virtualization platform.
|
||||
|
||||
But to do that, Canonical needs to siphon off some of the momentum Docker is currently enjoying and reorient part of the open source container-based virtualization world toward LXD. So far, Canonical appears eager to position LXD as a technology that can complement and enhance Docker, not compete directly with it. That makes sense to a degree, since LXD and Docker are somewhat different sorts of beasts, at least for now. But Canonical has stated its ambition "to bring much of the awesome security and isolation of LXD to docker [sic] as well," an idea that may not sit well with the Docker community, especially if LXD remains closely intertwined with Ubuntu rather than being distribution-agnostic.
|
||||
|
||||
It doesn't help that what Canonical is doing with LXD is very similar to what it has already done with technologies including [Unity][7], the desktop interface it designed for Ubuntu. Like LXD, Unity was a way for Canonical to replace a major part of the Ubuntu software stack—specifically, the [GNOME][8] desktop environment—with a homegrown alternative, providing the company more control over Ubuntu, yet also making Ubuntu less readily compatible with many open source apps that were not designed for Ubuntu and Unity. The move engendered more than a little ill-will among the Ubuntu user base, although most of that sentiment has long since dissipated.
|
||||
|
||||
It's hard to imagine Canonical marginalizing Docker in the same way it has GNOME, and even harder to imagine many people feeling emotional about this in the way they did when Unity replaced GNOME. But time will tell.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://thevarguy.com/ubuntu/110514/canonical-launches-lxd-open-source-virtualization-container
|
||||
|
||||
作者：[Christopher Tozzi][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://thevarguy.com/author/christopher-tozzi
|
||||
[1]:http://canonical.com/
|
||||
[2]:http://docker.com/
|
||||
[3]:http://www.ubuntu.com/cloud/tools/lxd
|
||||
[4]:http://ubuntu.com/
|
||||
[5]:https://linuxcontainers.org/
|
||||
[6]:http://openstack.org/
|
||||
[7]:http://unity.ubuntu.com/
|
||||
[8]:http://www.gnome.org/
|
||||
@ -1,43 +0,0 @@
|
||||
Massive 20% Improvement to Land in Intel's Mesa Driver Thanks to Valve's Efforts
|
||||
================================================================================
|
||||
> A group of devs from LunarG found a bottleneck in the driver
|
||||
|
||||
**Intel users should see a major improvement with their hardware after a group of developers from LunarG found out that there was a bottleneck in the DRM driver.**
|
||||
|
||||
|
||||
|
||||
The drivers on the Linux platform are not stellar, and most of the time, pieces of hardware work better on other operating systems, like Windows, for example. It might be strange that the same game, on the same hardware, works better on one platform than it does on the other, but things have been like this forever and no one expects any kind of big breakthroughs.
|
||||
|
||||
To be fair, the drivers from AMD, NVIDIA, and Intel have been improving in the last couple of years, especially after Steam for Linux was released. Actually, LunarG works with Valve to improve the state of the Intel drivers and to find ways to boost the performance on Linux. They had a big breakthrough and a kernel update should arrive very soon.
|
||||
|
||||
### Users with Intel-powered machines should be very happy ###
|
||||
|
||||
Valve tasked LunarG with improving the Intel drivers, which are lagging a little bit behind the competition, at least in terms of graphics. Some of the latest Intel processors are pretty powerful and you would expect them to be able to perform much better, at least as well as on Windows, but there was a problem.
|
||||
|
||||
The guys from LunarG worked on a piece of software called GlassyMesa, which drastically improved Intel's shader compiler stack. They also made a number of improvements in the past few months, but none of these changes was reflected in the driver's performance. This led them to believe that there had to be a bottleneck somewhere along the line.
|
||||
|
||||
"We started to suspect there was a bigger bottleneck masking the improvements, and sure enough we were able to generate a test program that showed a huge performance issue with how the hardware samplers were working as compared to the OpenGL driver running under windows. Something was slowing down the samplers on Linux, and we were determined to find out what," wrote the devs on their blog.
|
||||
|
||||
They did all sorts of testing, but they don't have access to the way the hardware is set up. Therefore, they sent the test program to Intel and the engineers found the problem and corrected it. As you can imagine, the people at Intel didn't say anything about what they actually corrected.
|
||||
|
||||
### 20% increase in performance is no small matter ###
|
||||
|
||||
In any case, LunarG also published some of the improvements they saw, and one of them is a 20% increase in game framerate.
|
||||
|
||||
- Left4Dead2 with frames that have hordes of zombies we've seen an increase of 17-25%
|
||||
- Counter-Strike GO: 16-20%
|
||||
- Lightsmark increased on a GT2 by 60% (HD4600) 4770
|
||||
|
||||
A kernel patch is required to make all these improvements available to users. It's not clear whether it will be available in Linux kernel 3.18 or 3.19, but it's coming. It also means that the kernel patch will be backported to the SteamOS kernel as well.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Massive-20-Improvement-to-Land-in-Intel-s-Mesa-Driver-Thanks-to-Valve-s-Efforts-464233.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
@ -1,48 +0,0 @@
|
||||
Prizes Ahoy! Ubuntu Scope Showdown Kicks Off
|
||||
================================================================================
|
||||
|
||||
|
||||
**SDK at the ready: Ubuntu has launched a new development competition for its mobile platform, with some swish prizes up for grabs for the winners.**
|
||||
|
||||
The ‘[Ubuntu Scope Showdown][1]‘ is the third such initiative to be held by the project and the second pitched squarely at mobile.
|
||||
|
||||
But this time around amateur and l33t developers alike are being tasked with a new brief: creating custom home screen experiences — ‘[Scopes][2]’ — for Ubuntu on phones.
|
||||
|
||||
### Er, What Is a Scope? ###
|
||||
|
||||
We often refer to Scopes as mini search engines, little portals that help you find content from a specific web site, service or topic — think ‘eBay’, ‘Cat gifs’, or ‘Restaurants Nearby’ — from the home screen, no need to open an app.
|
||||
|
||||
|
||||
|
||||
Thanks to the rich variety of result layouts content can be surfaced and previewed in interesting, intuitive ways. And when you’re happy with what you’ve found you can (typically) click through to open it up in an app or a new tab in the Ubuntu web browser.
|
||||
|
||||
Scopes can be added, removed, re-ordered and ‘favourited’ for easy access. Some Scopes can search multiple sources, others just the one.
|
||||
|
||||
It’s because of this multifariousness that makes the lack of a traditional home screen as we know it from Android, iOS and other mobile platforms (pages and pages of scopes) less of a negative. There’s no desktop; no custom wallpaper you can cover with icons, folders, shortcuts and widgets, but there is, quite literally, a world of information at your fingertips.
|
||||
|
||||
### The Competition ###
|
||||
|
||||
The Ubuntu Scope Showdown runs for five weeks (October 30 – December 3) giving participants just about enough time to take a project from concept to completion using the Ubuntu SDK and submitted to the Ubuntu Store.
|
||||
|
||||
The overall winner (decided by a judging panel of which, disclaimer ahoy, I am part of), will bag a brand new Dell XPS 13 Laptop (Developer Edition) preloaded with Ubuntu.
|
||||
|
||||
Runners up nab a Logitech UE Boom Bluetooth speaker, a Nexus 7 (2013) running Ubuntu, or one of two bundles of Ubuntu merchandise.
|
||||
|
||||
Interested in taking part? You’ll find more details on the entry requirements plus links to all the documentation you can eat on the [developer.ubuntu.com mini-site][3].
|
||||
|
||||
Will you be taking part?
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/ubuntu-scope-showdown-competition-launched
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://developer.ubuntu.com/2014/10/scope-development-competition/
|
||||
[2]:http://developer.ubuntu.com/scopes/
|
||||
[3]:http://developer.ubuntu.com/
|
||||
@ -1,36 +0,0 @@
|
||||
Ubuntu's Click Packages Might End the Linux Packaging Nightmare
|
||||
================================================================================
|
||||
> It's time to have one type of package for all distros
|
||||
|
||||
**The new Click packages that are already used on the Ubunu Touch platform by Canonical are also coming to the desktop and they might be able to change the Linux packaging paradigm.**
|
||||
|
||||
|
||||
|
||||
Ubuntu is the most used Linux operating system, so it's very likely that, if something really catches on with users of this distribution, it will probably shake things up in the Linux ecosystem as well. For now, the app packaging for Linux operating systems is a mess. It has improved over the years, but it still poses many problems.
|
||||
|
||||
There isn't any kind of unification and different distros use different packages. Debian-based distros use .deb and Fedora-based ones use .rpm, but you can also find packages with .sh or .run. The main problem is that they depend very much on the libraries that are already installed or available in the repos. Even if you have a .deb file for your Ubuntu system, it's not a guarantee that it will work. It might very well depend on a library that's not available for that particular version.
|
||||
|
||||
### One package to rule them all ###
|
||||
|
||||
For now, only the Ubuntu SDK can make Click packages, but they present some advantages over regular ones. For example, they are much safer than regular packages, mostly because there are no maintainer scripts that can run as root. In conjunction with the Ubuntu Software Center and Apparmor, the Click packages are pretty safe.
|
||||
|
||||
One of the best features of Click packages is that they have no external dependencies, which means that you can basically run them on any system, regardless of the available libraries installed or in the repositories. Martin Albisetti from Canonical explains this feature in more detail on his [blog][1].
|
||||
|
||||
"Clicks, by design, can't express any external dependencies other than a base system (called a 'framework'). That means that if your app depends on a fancy library that isn't shipped by default, you just bundle it into the Click package and you're set. You get to update it whenever it suits you as a developer, and have predictability over how it will run on a user's computer (or device!). That opens up the possibility of shipping newer versions of a library, or just sticking with one that works for you."
|
||||
|
||||
Another cool feature is that Click packages for different versions of the same app can be run on the same system. There are numerous applications out there that need to be alone on the system, otherwise they create problems for users, but the confinement provided by Click packages solves this issue.
|
||||
|
||||
These are just a few of the features that are already implemented. It will take a while until they reach the desktop, however. They will land along with Unity 8, but they are coming nonetheless. We can only hope that other distros will adopt this kind of format and not do their own similar thing, which would preserve the current packaging problems.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Ubuntu-s-Click-Packages-Might-End-the-Linux-Packaging-Nightmare-464271.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:http://beuno.com.ar/archives/334
|
||||
@ -1,54 +0,0 @@
|
||||
Open-Source Vs Groupon: GNOME Battle To Protect Their Trademark
|
||||
================================================================================
|
||||
|
||||
|
||||
**GNOME is a name synonymous with open-source software, but if the billion-dollar company Groupon has its way it could soon mean something different.**
|
||||
|
||||
[Groupon][1], famed for its ‘deal-of-the-day’ website, recently unveiled a “tablet-based platform“ called ‘GNOME’, and has filed requisite trademark filings — 10 so far — seeking ownership of the name.
|
||||
|
||||
Naturally, this has the GNOME Foundation ‘concerned’. GNOME is a [registered trademark][2] of the foundation, and has been since 2006. This mark was issued under a number of sections, including ‘operating system’ – which the Chicago-based Groupon is also claiming against.
|
||||
|
||||
Could it just be that they’ve never heard of GNOME before? Highly unlikely.
|
||||
|
||||
|
||||
|
||||
Groupon’s POS system. Ahem.
|
||||
|
||||
Even the most Saul Goodman-y of lawyers would first check existing trademarks and investigate the company(s) owning or contesting. Even assuming that lapse in professionalism, most would have at least given the name a quick Google. Damningly, the company has previously [claimed to be ‘fuelled by open-source’][3].
|
||||
|
||||
Groupon clearly knows of GNOME, knows what it does, what it stands for and how long it’s been around yet considers itself better placed to “own” the name for its brand of hokey in-store point-of-sale terminals.
|
||||
|
||||
*Hrm.*
|
||||
|
||||
### Campaign to Protect GNOME ###
|
||||
|
||||
Ask not what GNOME can do for you, but what you can do for GNOME. This morning the GNOME Foundation [launched a campaign][4] to raise (an estimated) US$80,000 to battle the first found of marks Groupon has applied to register.
|
||||
|
||||
“**We must not let a billion-dollar-company take the well-established name of one of the biggest Free Software communities,**” says Tobias Mueller, a GNOME Foundation director.
|
||||
|
||||
**“If you want to help GNOME defend its trademark and promote Free Software, visit the campaign’s page, share the link, and let Groupon know that they behaved terribly”.**
|
||||
|
||||
Lucas Nussbaum, **Debian Project Leader**, sums the whole situation up succinctly:
|
||||
|
||||
“**This legal defense is not just about protecting GNOME’s trademark; it is about asserting to the corporate world that FLOSS trademarks can and will be guarded. Not just by the project in question, but by the community as a whole. As a result, all FLOSS trademarks will be strengthened at once.**”
|
||||
|
||||
More details can be found on the GNOME Groupon Campaign page.
|
||||
|
||||
- [GNOME vs Groupon Campaign Page][5]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/gnome-groupon-trademark-battle
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://groupon.com/
|
||||
[2]:http://tsdr.uspto.gov/#caseNumber=76368848&caseType=SERIAL_NO&searchType=statusSearch
|
||||
[3]:https://engineering.groupon.com/2014/open-source/sharing-is-caring-open-source-at-groupon/
|
||||
[4]:https://mail.gnome.org/archives/foundation-list/2014-November/msg00020.html
|
||||
[5]:http://www.gnome.org/groupon/
|
||||
@ -1,56 +0,0 @@
|
||||
Chakra Linux 2014.11 Brings a Custom and Cool KDE 4.14.2 Desktop – Gallery
|
||||
================================================================================
|
||||
> A new version of Chakra Linux has been released
|
||||
|
||||
**Chakra Linux, a distribution specially built to take advantage of KDE Software Compilation and the Plasma desktop, has been upgraded to version 2014.11 and is now ready for download.**
|
||||
|
||||
The developers of this distribution usually choose names of famous scientists. The current iteration of the Chakra Linux, which is actually the second version in the branch, has been dubbed Euler, after Swiss mathematician and physicist Leonhard Euler, who refined calculus and graph theory. Because it follows the KDE releases, it means that we will probably get another version in a few months.
|
||||
|
||||
Surprisingly, if you already have Chakra Linux installed, it won't be enough just to keep your system up to date. Upgrading the OS with the provided ISO is quite easy, but if you're doing it manually, then you'll have to follow a rather intricate tutorial on how to do it properly. It's not unusual for developers to make such big changes that result in the usual updating process not working, but sometimes it's necessary.
|
||||
|
||||
### The latest Chakra Linux is using KDE 4.14.2 ###
|
||||
|
||||
The Chakra Linux developers are following the latest KDE branch very closely, but not the latest version. Case in point, KDE 4.14.3 was released yesterday, but Chakra features KDE 4.14.2. On the other hand, the developers go through great lengths to customize the KDE desktop so that it's unique to this particular distribution.
|
||||
|
||||
"The Chakra team is happy to announce the second release of the Chakra Euler series, which follows the KDE Applications and Platform 4.14 releases. The main reason for providing this new ISO, in addition to providing a new KDE release, is that Chakra has now implemented the /usr merge changes. If you already have Chakra installed on your system manual intervention is needed, so please follow the [instructions][1] on how to properly update. For new installations using this ISO, this is of course not needed."
|
||||
|
||||
"The extra repository, which is disabled by default, provides the must-have GTK-based applications and their dependencies. Kapudan, our desktop greeter which runs after the first boot, will allow you to enable it. Please have in mind that our installer, Tribe, does not currently officially support UEFI, RAID, LVM and GPT, although you might find some workarounds in our forums," [reads][2] the official website.
|
||||
|
||||
The developers also say that the Linux kernel has been updated to version 3.16.4, the systemd component has been updated to version 216, and all of the video drivers, free or proprietary, have been updated as well.
|
||||
|
||||
A complete list of new features and updates can be found in the official announcement.
|
||||
|
||||
Download Chakra Linux 2014.11:
|
||||
|
||||
- [Chakra GNU/Linux 2014.11 (ISO) 64-bitFile size: 1.7 GB][3]
|
||||
- [MD5][4]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Chakra-Linux-2014-11-Brings-a-Custom-and-Cool-KDE-4-14-2-Desktop-Gallery-464889.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:http://chakraos.org/news/index.php?/archives/134-Warning-Manual-intervention-needed-on-your-next-major-update.html
|
||||
[2]:http://chakraos.org/news/index.php?/archives/135-Chakra-2014.11-Euler-released.html
|
||||
[3]:http://sourceforge.net/projects/chakra/files/2014.11/chakra-2014.11-euler-x86_64.iso
|
||||
[4]:http://chakra-project.org/get/checksums.txt
|
||||
@ -1,50 +0,0 @@
|
||||
GNOME 3.14.2 Officially Released, Finally Drops SSLv3
|
||||
================================================================================
|
||||
> Users will find the new version in the repositories
|
||||
|
||||
|
||||
|
||||
**The GNOME development team has released the second update for the for GNOME 3.14.x branch and it brings a large number of fixes and improvements for a lot of the packages from the stack.**
|
||||
|
||||
GNOME 3.14 was initially released a few weeks ago and the developers are still ironing out a few issues. The new version has been received very well by the community and it's been adopted already by numerous Linux distributions. It's very likely that GNOME 3.14.2 will be integrated in most of the big repositories, as soon as possible.
|
||||
|
||||
The GNOME project managed to stay on track and the new release has arrived on time. Not all of the packages in the stack have been updated, but there are more than enough to get the users interested. It's a good idea to upgrade your desktop environment as soon as possible in order to get all of these enhancement.
|
||||
|
||||
### GNOME 3.14.2 gets a ton of improvements ###
|
||||
|
||||
Just like the previous iteration, the 3.14.2 release does have a few things that really stand out. For example, the NetworkManager dependency of GNOME Shell has been removed, the queued up notifications are now summarized, the handling of multi-day events has been improved, the GtkMenu use has been refined, various fixes for Mutter have been added, and the SSLv3 use has been disabled.
|
||||
|
||||
"Here comes our second update to GNOME 3.14, it has many fixes, various improvements, documentation and translation updates, we hope you'll enjoy it. Individual modules may get new stable 3.14 releases but our focus is now on the development branches, we released a first snapshot as 3.15.1 two weeks ago and will get another one by the end of the month.," [says][1] GNOME developer Frederic Peters.
|
||||
|
||||
GNOME 3.14.2 comes with updates for these core apps: Adwaita Icon Theme, Eye of GNOME, Epiphany, evolution-data-server, Glib, GNOME Calculator, GNOME Contacts, GNOME Desktop, GNOME Shell, GNOME Terminal, Mutter, Nautilus, Tracker, and more.
|
||||
|
||||
The apps that receive upgrades in the 3.14.2 branch include Aisleriot, Bijiben, Brasero, Cheese, Evolution, File Roller, Gedit, Four in a Row, GNOME Boxes, GNOME Maps, GNOME Music, Hitori, Orca, Rygel, Vinagre, and more.
|
||||
|
||||
We [detailed the GNOME 3.14.x release][2] when it was made available and you can find more details in the original report.
|
||||
|
||||
Download the GNOME 3.14.2 stack
|
||||
|
||||
- [GNOME 3.14.2 Stable Sources][3]
|
||||
- [GNOME 3.14.2 Stable Modules][4]
|
||||
- [GNOME 3.15.1 Unstable Sources][5]
|
||||
- [GNOME 3.15.1 Unstable Modules][6]
|
||||
|
||||
But keep in mind that these are the source packages. If you want an easy upgrade or install, be sure to check the repositories.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/GNOME-3-14-2-Officially-Released-Finally-Drops-SSLv3-464903.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:http://permalink.gmane.org/gmane.comp.gnome.devel.announce/397
|
||||
[2]:http://news.softpedia.com/news/GNOME-3-14-Officially-Released-Screenshot-Tour-and-Video-459865.shtml
|
||||
[3]:https://download.gnome.org/core/3.14/3.14.2/sources/
|
||||
[4]:https://download.gnome.org/teams/releng/3.14.2/
|
||||
[5]:https://download.gnome.org/core/3.15/3.15.1/sources/
|
||||
[6]:https://download.gnome.org/teams/releng/3.15.1/
|
||||
@ -1,100 +0,0 @@
|
||||
Budgie Desktop v8 Released With Improved Menu, Panel
|
||||
================================================================================
|
||||
|
||||
|
||||
**A new version of [Evolve OS][1]‘s simple ‘[Budgie Desktop Environment][2]‘ has been released, and the improvements under its wing are impressive.**
|
||||
|
||||
Made up of 78 commits, the lightweight desktop lands with a host of new options and applets to play with. Its plumage has also benefitted from a bit of TLC, with key parts of the shell feeling fresher and looking more refined.
|
||||
|
||||
But will the changes ruffle the feathers of the Budgie flock or leave them squawking in awe? Let’s take a closer look.
|
||||
|
||||
### Budgie v8 ###
|
||||
|
||||
#### Menu Changes ####
|
||||
|
||||
The **Budgie Menu** now uses a narrower compact layout by default. This style lists the applications in categories (as previously) but sorted by usage rather than name.
|
||||
|
||||
Software that you open most often sit nearer the top of each category header. It’s an efficacious decision that should help save time for those who hunt n’ scroll for apps rather than use the handy search filter.
|
||||
|
||||
|
||||
|
||||
The Menu uses ‘compact’ mode by default
|
||||
|
||||
The old two-pane setup that featured in earlier builds remains available; you can toggle it back on in Budgie’s preferences (**right click on the menu applet > Preferences**).
|
||||
|
||||
The power option menu that previously
|
||||
resided in the main menu has been moved over to the System Tray applet (i.e., ‘volume‘). Additionally, you can now access System Settings entries from the menu itself — no more scratching of heads!
|
||||
|
||||
#### Panel Changes ####
|
||||
|
||||
|
||||
|
||||
Quicklist support in Budgie 0.8
|
||||
|
||||
The Budgie Panel and task list applet both benefit from a raft of improvements, including new auto-hide options, dynamic theming support and a new ‘GNOME 2′-style menu bar option.
|
||||
|
||||
- Auto-hide (optional)
|
||||
- Quicklist support
|
||||
- Dark theme support
|
||||
- Application pinning
|
||||
- App ‘attention’ hint
|
||||
- GNOME Panel theming
|
||||
- Old-school ‘Menu Bar’ applet (optional)
|
||||
|
||||
|
||||
|
||||
#### Elsewhere ####
|
||||
|
||||
Other changes include support for GNOME 3.10 and up; improved animations when changing wallpapers; and the run dialog has been hugely improved in design, sporting an almost Alfred/GNOME-Do-esque design. Mmmhm!
|
||||
|
||||
|
||||
|
||||
Run, Run, Run
|
||||
|
||||
### Install Budgie Desktop on Ubuntu ###
|
||||
|
||||
Budgie 0.8 is, as with previous releases, available to install in Ubuntu 14.04 LTS and Ubuntu 14.10 by way of an official PPA. The desktop can be installed alongside Unity, GNOME Shell and Cinnamon without much (if any) issue.
|
||||
|
||||
To install, open a new Terminal window and enter the following commands. Enter your password where prompted.
|
||||
|
||||
sudo add-apt-repository ppa:evolve-os/ppa
|
||||
|
||||
sudo apt-get update && sudo apt-get install budgie-desktop
|
||||
|
||||
After the install has completed you will need to log out of Unity (or whichever desktop you’re currently using). At the Unity Greeter click the Ubuntu logo emblem, select the Budgie session from the session list, and then log in as normal. The Budgie desktop will load.
|
||||
|
||||
|
||||
|
||||
#### Notes for Ubuntu Users ####
|
||||
|
||||
|
||||
|
||||
Expect Odd Theming Issues in Ubuntu
|
||||
|
||||
While Budgie is now easy for Ubuntu users to install it is not designed for it specifically (the Evolve OS distribution is the best way to experience it).
|
||||
|
||||
Naturally, you might not fancy upheaving to another OS. That’s fine, but if you plan on keeping Budgie caged in Ubuntu you’ll need to note the following caveats (lest you end up bird-brained).
|
||||
|
||||
First up, **Budgie is under active development**. Several key features remain missing, including native network management support. An applet can be added to the panel that supports Ubuntu’s Indicator Applets, but it’s a little rough around the edges.
|
||||
|
||||
You should also expect some theming issues when using the shell with Ambiance/Radiance. The Adwaita theme (and other GNOME themes) work best. You should also disable Ubuntu’s Overlay Scrollbars.
|
||||
|
||||
Finally, logout (volume > power button) **does not work under Ubuntu**. To log out you should use the run dialog (Alt+F2) and the following command:
|
||||
|
||||
gnome-session-quit
|
||||
|
||||
If all of that sounds like fun rather than faff, there’s plenty to enjoy in Budgie – and not just its minimal system footprint! Let us know your own thoughts on it, what you’d like to see it add next, etc. in the comments below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/budgie-desktop-0-8-released-big-changes
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://evolve-os.com/
|
||||
[2]:http://www.omgubuntu.co.uk/2014/07/install-budgie-evolve-os-desktop-ubuntu-14-04
|
||||
@ -1,51 +0,0 @@
|
||||
Ubuntu 15.04 Gets Tentative Release Date of April 23, 2015
|
||||
================================================================================
|
||||
|
||||
|
||||
**Doing anything special on April 23 next year? You might well be — it’s the tentative release date being given for Ubuntu 15.04 ‘Vivid Vervet’.**
|
||||
|
||||
The date, along with those of various other development milestones, is listed as part of a [draft release schedule][1] on the Ubuntu Wiki page for the ‘V’ update. As of writing all dates are subject to approval from the Ubuntu release team and are therefore **not final**.
|
||||
|
||||
Ubuntu’s previous spring release, 14.04 LTS, went live on April 17, 2014.
|
||||
|
||||
### Veracity Potential is Void ###
|
||||
|
||||
|
||||
|
||||
Dates not yet ready to be inked in
|
||||
|
||||
Draft means just that, but having covered some 10 Ubuntu release over five years I do know that the proposed dates don’t tend to differ too wildly from those that go final (famous last words, I’m sure!).
|
||||
|
||||
Even so, take the proposals with a pinch of optimism for now. I’ll be keeping both this page and the fancy-schmancy graphic updated as, if or when anything changes.
|
||||
|
||||
### Key Ubuntu 15.04 Release Dates ###
|
||||
|
||||
As with all releases post-13.04, Ubuntu proper only makes fleeting appearances in select milestone releases, specifically the ‘final beta’ and the ‘release candidate’ stages.
|
||||
|
||||
Ubuntu’s family of flavours, which may include Ubuntu MATE this cycle, take full advantage of the testing opportunities at hand.
|
||||
|
||||
- **Alpha 1** – December 18th (for flavours)
|
||||
- **Alpha 2** – January 22nd (for flavours)
|
||||
- *Feature Freeze* — February 19th
|
||||
- **Beta 1** – August 28th (for flavours)
|
||||
- *UI Freeze* — March 12th
|
||||
- **Final Beta** – March 26th
|
||||
- *Kernel Freeze* — April 9th
|
||||
- **Release Candidate** – April 16th
|
||||
|
||||
The final release of the Vivid Vervet in all its vivacious glory is pencilled in for release on:
|
||||
|
||||
- **Ubuntu 15.04 Final** – April 23rd
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/ubuntu-15-04-release-schedule-date-vivid-vervet
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
|
||||
@ -1,42 +0,0 @@
|
||||
Systemd fallout: Two Debian technical panel members resign
|
||||
================================================================================
|
||||
|
||||
|
||||
**Two well-known and experienced Debian developers, both members of the project's technical committee, have announced they will be leaving the committee.**
|
||||
|
||||
The resignations of [Colin Watson][1] and [Russ Allberry][2] from the panel come soon after senior developer Joey Hess [resigned][3] from the project altogether.
|
||||
|
||||
There has been much acrimony recently over the adoption of the systemd init system as the default for Jessie, the next release of Debian, which is expected to come out in the next few months.
|
||||
|
||||
The Debian Technical Committee [decided][4] back in February, via the casting vote of panel chief Bdale Garbee, to adopt systemd as the default. This decision came after months of discussion.
|
||||
|
||||
Recently, there has been [another push][5] for reconsideration led by another technical committee member, Ian Jackson, and [a general resolution][6] was put up for vote. It is open for voting until midnight on November 18, UTC (10am on Wednesday AEST). There are a few options proposed by others, including one from the Debian Project leader Lucas Nussbaum, besides the main resolution.
|
||||
|
||||
In the initial vote back in February, Allberry supported systemd as the default, while Watson, an employee of Canonical, the company that creates the Ubuntu GNU/Linux distribution, expressed a preference for upstart. Jackson also backed upstart.
|
||||
|
||||
In [a post][7] explaining his decision, Watson, one of the first batch to join Canonical, attributed it to a general move on his part to start spending his Debian time on things he found enjoyable. Late last month, [he asked][8] to be moved from the Ubuntu Foundations team to the Launchpad engineering team. Watson has given the Debian Technical Committee time to appoint someone in his place before he moves on.
|
||||
|
||||
In contrast, Allberry's [resignation post][9] said he wanted to leave immediately, though he later added that he would stay on for a while if needed.
|
||||
|
||||
His frustration was clear: "If any part of this doesn't make sense, or if any of it feels like an attack or a reaction to any single person or event, I'm happy to clarify. I would appreciate it if people would ask for clarification rather than making assumptions, as assumptions about other people's motives are one of the things that I find the most demoralising about the Debian project right now."
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.itwire.com/business-it-news/open-source/66153-systemd-fallout-two-debian-technical-panel-members-resign
|
||||
|
||||
作者：[Sam Varghese][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.itwire.com/business-it-news/open-source/itemlist/user/902-samvarghese
|
||||
[1]:https://lists.debian.org/debian-ctte/2014/11/msg00052.html
|
||||
[2]:https://lists.debian.org/debian-ctte/2014/11/msg00071.html
|
||||
[3]:http://www.itwire.com/business-it-news/open-source/66014-systemd-fallout-joey-hess-quits-debian-project
|
||||
[4]:http://www.itwire.com/business-it-news/open-source/63121-garbees-casting-vote-means-systemd-is-debian-init
|
||||
[5]:http://www.itwire.com/business-it-news/open-source/65781-pushback-against-systemd-in-debian-gathers-steam
|
||||
[6]:https://www.debian.org/vote/2014/vote_003
|
||||
[7]:https://lists.debian.org/debian-ctte/2014/11/msg00052.html
|
||||
[8]:http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2014-10-26-moving-on-but-not-too-far.html
|
||||
[9]:https://lists.debian.org/debian-ctte/2014/11/msg00071.html
|
||||
@ -1,61 +0,0 @@
|
||||
Firefox 34 Arrives with Plugin-Free Video Calling and Powerful WebIDE
|
||||
================================================================================
|
||||
|
||||
|
||||
**It’s been a busy few months for Mozilla, what with agreeing to a deal to switch its default search provider to Yahoo!, launching a custom version of its browser packed full of developer goodies, and launching Firefox OS handsets in new territories.**
|
||||
|
||||
Today, Mozilla has released Firefox 34 for Windows, Mac and Linux desktops, the first stable release since last month’s security n’ bug fix update.
|
||||
|
||||
### Headline Feature ###
|
||||
|
||||
Despite the rapid release cycle Mozilla once again manages to deliver some great new features.
|
||||
|
||||
Making its first appearance in a stable release is **Firefox Hello**, Mozilla’s WebRTC feature.
|
||||
|
||||
Though not enabled for all (you can manually turn it on via about:config), the feature bring plugin-free video and voice calls to the browser. No Skype, no add-ons, no hassle. You simple click the Firefox Hello icon, send your share link to the recipient to initiate a connection (assuming they’re also using a WebRTC-enabled browser, like Google Chrome or Opera).
|
||||
|
||||
|
||||
|
||||
The ‘Hello Firefox’ Popup
|
||||
|
||||
Signing in with a Firefox account will give you more features, including a contacts book with one-click calling (no need to share links).
|
||||
|
||||
#### Other Changes ####
|
||||
|
||||
Version 34 also makes it easier to **switch themes** (formerly known as ‘personas’), with live previews and a switcher menu now available on the **Customising canvas**:
|
||||
|
||||
|
||||
|
||||
Ad-hoc theme switching
|
||||
|
||||
The first major search engine change arrives in this release, with Yandex shipping as default for Belarusian, Kazakh, and Russian locales. Yahoo! will be enabled for US users in the near future. But remember: [this does not affect the version of Firefox provided in Ubuntu][1].
|
||||
|
||||
US users get secure **HTTPS** Wikipedia searching from the search box:
|
||||
|
||||
|
||||
|
||||
Secure Wikipedia Searches for English US Users
|
||||
|
||||
In addition to improved HTML5 support (largely around WebCrypto features) a [**new WebIDE tool**][2] ships in this release, and is packed full of great tools for developers.
|
||||
|
||||
From Android connectivity and an in-app editor to support for deploying and testing apps in a Firefox OS simulator. If you haven’t tried Firefox OS in a while, v2.2 (unstable) has plenty to play with including edge swiping, new home screen arranging features, and some new APIs.
|
||||
|
||||
|
||||
|
||||
### Download Firefox 34 ###
|
||||
|
||||
Canonical will roll out Firefox 34 to users of Ubuntu 12.04, 14.04 and 14.10 in the next 24 hours or so, so keep an eye out. If you’re super impatient the release can also be downloaded from Mozilla servers directly.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/12/firefox-34-changes-include-hello-html5-webide
|
||||
|
||||
作者：[Joey-Elijah Sneddon ][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/11/firefox-set-yahoo-default-search-engine-ubuntu-not-affected
|
||||
[2]:https://developer.mozilla.org/en-US/docs/Tools/WebIDE
|
||||
@ -1,78 +0,0 @@
|
||||
From Mint to Trisquel: The Top Linux Distro Releases in November 2014
|
||||
================================================================================
|
||||
**November wasn’t heavy on new Linux distribution releases, but still had more than enough to keep distro-hoppers bouncing from download server to ISO mirror and back again.**
|
||||
|
||||
From the free software ethic of **Trisquel** to the nostalgic glow of **Ubuntu MATE**, let’s take a look at the major Linux distribution releases made in November 2014.
|
||||
|
||||
|
||||
|
||||
### Linux Mint 17.1 ###
|
||||
|
||||
Linux Mint 17.1 ‘Rebecca’ is the big hitter on this list, going stable just in time to make it.
|
||||
|
||||
Based on Ubuntu 14.04 and using Linux kernel 3.13, the update also comes loaded with the **latest [Cinnamon 2.4][1] desktop environment, a customisable version of the Nemo file manager**, and improvements to the Update Manager to make package upgrades safer, saner and swifter.
|
||||
|
||||
Other changes see the ‘**Background**’, ‘**Login**’ and ‘**Theme**’ settings panes redesigned, and **‘Privacy’ and ‘Notification’ sections** added. The default **system font has been switched to Noto Sans**, while fans of customisation will enjoy new colors added to the Mint-X theme package.
|
||||
|
||||
Linux Mint 17.1 delivers a set of solid, well thought out changes and performance improvements, important for an LTS release supported until 2019.
|
||||
|
||||
More information and those all important downloads can be found on the official project website.
|
||||
|
||||
- [Visit the Linux Mint Website][2]
|
||||
|
||||
### Ubuntu Mate 14.04 LTS ###
|
||||
|
||||
|
||||
|
||||
It may have [arrived after the release of Ubuntu MATE 14.10][3] (**timey-wimey**), but as the first Long Term Support release of the flavor Ubuntu MATE 14.04 was welcomed with warm arms, especially by those who love to bask in the green-hued glow of GNOME 2 nostalgia.
|
||||
|
||||
Packed with security updates, MATE 1.8.1, and new software included out of the box, Ubuntu MATE 14.04 LTS is a notable update with plenty to tempt those on the newer (but older) 14.10 release.
|
||||
|
||||
For full hardware requirements, support information and download links, head on over to the official project website.
|
||||
|
||||
- [Download Ubuntu MATE 14.04 LTS][4]
|
||||
|
||||
### Trisquel 7.0 ###
|
||||
|
||||
|
||||
|
||||
The [latest stable release of Trisquel][5], an Ubuntu-based distribution endorsed by the Free Software Foundation (FSF), arrived in the middle of November — and was met by **a lot** of interest.
|
||||
|
||||
The free (as in freedom) distribution is built on Ubuntu 14.04 LTS but ships without any of the proprietary bits and pieces. It’s a “pure” Linux experience that may require some workarounds, but serves to flag up the areas where more attention is needed in FOSS hardware support and app alternatives.
|
||||
|
||||
The Libre Linux 3.13 Kernel, GNOME 3.12 ‘Flashback’ desktop and the Firefox-based Abrowser 33 are among the changes to be found in Trisquel 7.
|
||||
|
||||
- [Download Trisquel 7][6]
|
||||
|
||||
### Other Notable Releases ###
|
||||
|
||||
|
||||
|
||||
Outside of the Ubuntu-based bubble November 2014 saw releases of other popular Linux distributions, including beta milestones of Mageia 5 and Fedora 21, and a new stable release of Scientific Linux 6.6.
|
||||
|
||||
Joining them is openSUSE 13.2 (stable) — the first release to follow a change in the way openSUSE development takes place, the first to adopt the new openSUSE design guidelines and the first to ship with a streamlined (if still unwieldy) installer.
|
||||
|
||||
The release has been getting great reviews from the geek press, who gave particular praise for the GNOME 3.14 implementation.
|
||||
|
||||
Coming from Ubuntu, where “everything just works”, the cultural and technical gulf can be daunting at first. But if you have some free time, like the color green and relish a challenge, the official openSUSE 13.2 [release announcement][7] should be your starting point.
|
||||
|
||||
**Have you tried any of these releases above? Let us know what you made of them in the space down below .**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/11/linux-distro-releases-round-november-2014
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/11/install-cinnamon-2-4-ubuntu-14-04-lts
|
||||
[2]:http://www.linuxmint.com/download.php
|
||||
[3]:http://www.omgubuntu.co.uk/2014/11/ubuntu-mate-14-04-download-released
|
||||
[4]:https://ubuntu-mate.org/longterm/
|
||||
[5]:http://www.omgubuntu.co.uk/2014/11/download-trisquel-7-0-kernel-3-13
|
||||
[6]:https://trisquel.info/en/download
|
||||
[7]:https://news.opensuse.org/2014/11/04/opensuse-13-2-green-light-to-freedom/
|
||||
@ -1,38 +0,0 @@
|
||||
Linus Torvalds Thanks Microsoft for a Great Black Friday Monitor Deal
|
||||
================================================================================
|
||||
|
||||
|
||||
> The creator of the Linux kernel now has a UHD display
|
||||
|
||||
**Linus Torvalds is the creator of the Linux Kernel, he advocated for years against Microsoft's practices and he often talked about Windows. These are just some of the reasons why it's funny to see him thank Microsoft, even if it's probably done sarcastically.**
|
||||
|
||||
The rhetoric regarding the Linux vs. Windows subject has subsided a great deal in the last few years. There have been some issues with UEFI and other similar problems, but for the most part things have quieted down.
|
||||
|
||||
There is no one left at the Redmond campus to call Linux a cancer and no one is making fun of Windows for crashing all the time. In fact, there has been some sort of reconciliation between the two sides, which seems to benefit everyone.
|
||||
|
||||
It's not like Microsoft is ready to adopt the Linux kernel for their operating system, but the new management of the company talks about Linux as a friend, especially in the cloud.
|
||||
|
||||
They can no longer ignore it, even if they want to. The same happened with Linus Torvalds who hasn't said anything bad about Microsoft and Windows for a long time, and that is a good thing.
|
||||
|
||||
### Linus Torvalds saying "thanks" to Microsoft is not something you see every day ###
|
||||
|
||||
The creator of the Linux kernel talked about a great Black Friday deal he got from the Microsoft store, for a UHD monitor. He shared this piece of info on Google+ and some of the users also found it amusing to read that he's giving sincere thanks to Microsoft for their great deal.
|
||||
|
||||
"Whee. Just installed a new monitor. 3840x2160 resolution - it's the Dell 28" UHD panel - for $299 (€241) thanks to Microsoft's black Friday deal. Thanks MS! Ok, I have to admit that it's not actually a great panel: very clear color shifts off-center, 30Hz refresh etc. But still - I'm a nut for resolution, and at $299 (€241) I decided that this will carry me over until better panels start showing up at good prices," wrote Linus on [Google+][1].
|
||||
|
||||
In the meantime, he is also working on the latest kernel branch, 3.18, which will probably be released sometime at the end of this week. It's not clear how things will evolve after that, especially given the fact that the holidays are approaching fast, and devs might be a little sluggish when it comes to pushing patches and new features for the next 3.19 branch.
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Linus-Torvalds-Thanks-Microsoft-for-a-Great-Black-Friday-Monitor-Deal-466599.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:https://plus.google.com/+LinusTorvalds/posts/4MwQKZhGkEr
|
||||
@ -1,42 +0,0 @@
|
||||
Apparently This Trojan Virus May Have Infected Linux Systems For Years
|
||||
================================================================================
|
||||
|
||||
|
||||
One of the first few argument in [why should you switch to Linux][1] is that Linux is secure and virus free. It is widely perceived by most of the Linux users that Linux is immune to viruses, which is true to an extent but not entirely.
|
||||
|
||||
Like any other OS, Linux too is not immune to malware, trojan, rootkit, virus etc. There have been several [famous Linux viruses][2]. But if you compare those to that of Windows, the number is infinitesimal. So, why am I talking about Linux viruses today then? Because a new trojan has been detected in market which might be impacting Linux systems.
|
||||
|
||||
### Turla infects Linux systems as well ###
|
||||
|
||||
Few months back a sophisticated cyber espionage program, nicknamed [Turla][3], was detected. It was supposed to be originated in Russia, allegedly with Russian government backing. The spyware program was targeting government organizations in Europe and the United States for four years.
|
||||
|
||||
In a recent report, researchers at [Kaspersky][4] has found that Turla was not only affecting Windows system but also Linux operating system. Kaspersky researchers have termed it the ‘missing piece of Turla puzzle’. As per the report:
|
||||
|
||||
> “This newly found Turla component supports Linux for broader system support at victim sites. The attack tool takes us further into the set alongside the Snake rootkit and components first associated with this actor a couple years ago. We suspect that this component was running for years at a victim site, but do not have concrete data to support that statement just yet.”
|
||||
|
||||
### What is this Linux module of Turla and how dangerous it is? ###
|
||||
|
||||
Going by the Kaspersky report,
|
||||
|
||||
> The Linux Turla module is a C/C++ executable statically linked against multiple libraries, greatly increasing its file size. It was stripped of symbol information, more likely intended to increase analysis effort than to decrease file size. Its functionality includes hidden network communications, arbitrary remote command execution, and remote management. Much of its code is based on public sources.
|
||||
|
||||
Report also mentions that this trojan doesn’t require elevated privileges (read root) while running arbitrary remote commands and it cannot be discovered by commonly used administrative tools. Personally, I doubt their claims.
|
||||
|
||||
So, as a Linux desktop user, should you be scared? In my opinion, it is too early to go in to panic mode as we experienced with [ShellShock Linux bug][5]. Turla was originally intended for government organization, not common users. Let’s wait and watch for more concrete news. I’ll keep on updating this article. Till then enjoy Linux.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://itsfoss.com/apparently-trojan-virus-infected-linux-systems-years/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://itsfoss.com/author/Abhishek/
|
||||
[1]:http://itsfoss.com/reasons-switch-linux-windows-xp/
|
||||
[2]:http://www.unixmen.com/meet-linux-viruses/
|
||||
[3]:http://www.reuters.com/article/2014/03/07/us-russia-cyberespionage-insight-idUSBREA260YI20140307
|
||||
[4]:https://securelist.com/blog/research/67962/the-penquin-turla-2/
|
||||
[5]:http://itsfoss.com/linux-shellshock-check-fix/
|
||||
@ -1,55 +0,0 @@
|
||||
First Ubuntu Phone Will Launch In Europe This February
|
||||
================================================================================
|
||||
|
||||
|
||||
**Bq Aquaris e4.5The first Ubuntu Phone will go on sale in Europe in the second week of February.**
|
||||
|
||||
Made by Spanish device company Bq, the handset will mark the first time that an Ubuntu Phone is sold directly to consumers
|
||||
|
||||
### The First Phone: Specifications ###
|
||||
|
||||
For its first Ubuntu Phone Bq is launching a repurposed version of the its popular [Aquaris e4.5 handset][1] preloaded with Ubuntu for Phones.
|
||||
|
||||
Unlike the version that developers can (and have) been downloading and flashing to their Nexus devices, the commercial version of Ubuntu on phones will ship with a number of differences in software, including new ‘Aggregator Scopes’ and support for paid content.
|
||||
|
||||
As smartphones go Aquaris e4.5 is a capable daily driver, a dependable and competent handset.
|
||||
|
||||
No, it’s not the most flashy or high-end of devices but that’s not what Ubuntu’s debut devices needed to be. It needed to balance price and performance so that hesitant developers and enthusiasts can pick one up to tinker with.
|
||||
|
||||
Inside it offers:
|
||||
|
||||
- 4.5-inch screen (qHD resolution @ 540×960)
|
||||
- 1.3 GHz Quad Core ARM Cortex A7 (MediaTek)
|
||||
- Mali 400 GPU @ 500 MHz (MediaTek)
|
||||
- 8GB eMMC Storage
|
||||
- 1GB RAM
|
||||
- 2150 mAh Battery
|
||||
- Dual micro-SIM
|
||||
|
||||
As for pricing, while Canonical hasn’t given us any firm details has been suggested to us, albeit with a wry wink and a cheeky smile, that buyers won’t pay more than the ~€149 or so that Bq sells the Android version at.
|
||||
|
||||
### Looking Ahead ###
|
||||
|
||||
|
||||
|
||||
The Bq Handset In Hand
|
||||
|
||||
The elephant in the room is the USA. Initially Bq will only sell their Ubuntu phone in Europe, and that through their website. US plans are yet to be divulged, and it’s not clear if it will be Bq, Meizu or an as yet unannounced partner jumping through the hoops required to launch a cellular device there.
|
||||
|
||||
Looking ahead, I think it’s likely that we’ll see Bq launch an Ubuntu version of its 4G-equipped Aquaris 5 model later in the year. The model is a little larger than the e4.5 and features an HD IPS screen screen and marginally faster processor. It’s this device that was launched at [Bq’s ‘mystery press event’ last month][2], alongside several new Android tablets.
|
||||
|
||||
A video advert directed by renowned Spanish filmmaker Álex de la Iglesia premiered at that event — an advert I’ve a hunch we’ll be seeing a little more in the near future… ;)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/12/bq-ubuntu-phone-launches-in-europe-this-february
|
||||
|
||||
作者：[JoeDanger][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.omgubuntu.co.uk/author/joedanger
|
||||
[1]:http://www.bq.com/gb/products/aquaris-e4-5.html
|
||||
[2]:http://www.omgubuntu.co.uk/2014/11/bq-event-delivers-expecting-nothing-ubuntu-phone
|
||||
@ -1,5 +1,3 @@
|
||||
barney-ro translating
|
||||
|
||||
5 Awesome Open Source Backup Software For Linux and Unix-like Systems
|
||||
================================================================================
|
||||
A good backup plan is essential in order to have the ability to recover from
|
||||
|
||||
@ -1,4 +1,3 @@
|
||||
mdjsjdqe translating...
|
||||
11 Useful Utilities To Supercharge Your Ubuntu Experience
|
||||
================================================================================
|
||||
**Whether you’re a relative novice or a seasoned pro, we all want to get the most from our operating system. Ubuntu, like most modern OSes, has more to offer than what is presented at first blush.**
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
[felixonmars translating...]
|
||||
|
||||
Upstream and Downstream: why packaging takes time
|
||||
================================================================================
|
||||
Here in the KDE office in Barcelona some people spend their time on purely upstream KDE projects and some of us are primarily interested in making distros work which mean our users can get all the stuff we make. I've been asked why we don't just automate the packaging and go and do more productive things. One view of making on a distro like Kubuntu is that its just a way to package up the hard work done by others to take all the credit. I don't deny that, but there's quite a lot to the packaging of all that hard work, for a start there's a lot of it these days.
|
||||
|
||||
@ -1,103 +0,0 @@
|
||||
Why Is Huffington Post Running A Multi-Part Series To Promote The Lies Of A Guy Who Pretended To Invent Email?
|
||||
================================================================================
|
||||
**from the that's-just-wrong dept**
|
||||
|
||||
I thought this story had ended a few years ago. Back in 2012, we wrote about how The Washington Post and some other big name media outlets were claiming that a guy named V.A. Shiva Ayyadurai had "invented email" in 1978. The problem was that [it wasn't even close to true][1] and relied on a number of total misconceptions about email, software and copyright law. Ayyadurai and some of his friends have continued to play up the claim that he "invented" email, but it simply was never true, and it's reaching a level that seems truly bizarre. Ayyadurai may have done some interesting things, but his continued false insistence that he invented email is reaching really questionable levels. And, now it's gone absolutely nutty, with the Huffington Post running [a multi-part series][2] (up to five separate articles so far -- all done in the past 10 days) all playing up misleading claims saying that Ayyadurai invented email, even though even a basic understanding of the history shows he did not.
|
||||
|
||||
Let's take care of the basics first, and then we'll dig in on what's going on here, because it's really quite ridiculous. First off, no one denies that V.A. Shiva Ayyadurai -- an apparently very bright 14-year-old at the time -- wrote an email software program for the University of Medicine and Dentistry of New Jersey (UMDNJ) in 1978. By all accounts, it was a perfectly decent email system that allowed the UMDNJ staff to send electronic messages. Further, no one doubts that, in 1981, Ayyadurai registered the copyright on his program, which was called EMAIL. The problems are that (1) email was invented long before 1978, (2) the copyright is merely on the specific software code, not the idea of email, and (3) while Ayyadurai may have independently recreated the basics of email (and even added a nice feature), none of his work was even remotely related to what later became the standards of email. What's most sickening about this is that as part of this new PR campaign, Ayyadurai is ridiculously arguing that the reason no one believes him isn't because he's simply wrong, but because they can't stand to believe that "a dark-skinned immigrant kid, 14 years old," invented email, and that it was done in "one of the poorest cities in the US" rather than at a famous university.
|
||||
|
||||
Again, that might make for a nice story line if there were some factual basis behind it, but there isn't. The history of email [is well-documented][3] from [multiple sources][4] and it began way, way before 1978. And while early versions were somewhat crude, by 1978 they had basically everything that Ayyadurai claims to have invented (it is entirely believable that Ayyadurai, as a bright kid, independently came up with the same ideas, but he was hardly the first). There was a messaging system called MAILBOX at MIT in 1965. You can read [all the details of it here][5], including source code. Ray Tomlinson is frequently credited with inventing the modern concept of email for the internet by establishing the @ symbol (in 1972) as a way of determining both the user and which computer to send the email to. By 1975, there were things like email folders (invented by Larry Roberts) and some other basic email apps. As is noted, by 1976 -- two years before Ayyadurai wrote his app -- email was *75% of all ARPANET traffic*.
|
||||
|
||||
So, let's get to the Huffington Post trying to whitewash all of this factual history out of existence.
|
||||
|
||||
It started on August 20th, with an article by Larry Weber, CEO of Racepoint Global, kicking off a supposed "series" called "The History of Email." Except that the series has little to do with the history of email at all. It's just about Ayyadurai writing his particular email program in 1978. Great story. Smart kid done good. Has nothing to do with the invention of email. Weber, though, calls it [The Boy Who Invented Email][6]. At this point, it should be worth questioning why Weber suddenly decided this was such an interesting story. If you don't know, Weber is one of PR's [biggest names][7], having built one of the most successful PR companies in history. It seems odd that he "just happened" to come across Ayyadurai's fake story and decided to help create a 5-part series about it. I have reached out to both Weber and the Huffington Post to ask if Weber has any financial relationship with Ayyadurai. As I publish this, neither has responded. The post will be updated if I hear from either. None of the posts in the series disclose any such relationship. Nor does the Huffington Post indicate that this is a "sponsored" post as far as I can tell.
|
||||
|
||||
The [second][8] and [third][9] articles in the series are both written by Leslie Michelson, the Director of High Performance and Research Computing at Rutgers Medical School (which took over UMDNJ a while back). More importantly, in 1978 he was the Director of the Laboratory Computer Network at UMDNJ, and apparently "challenged" Ayyadurai to create an electronic interoffice mail system. The [fourth article][10] in the series is by Robert Field, a technologist at Rutgers Medical School and, in 1978, a colleague of Ayyadurai at UMDNJ. See a pattern? Huffington Post also [interviewed Ayyadurai][11] for HuffPost Live in which he mostly attacks anyone who challenges his story, comparing himself to Philo T. Farnsworth -- except in that case, Farnsworth actually invented TV before anyone else. Ayyadurai did not do that with email. Apparently there are two more in this series that are still to come.
|
||||
|
||||
When you look at the collection of articles, they all repeat the same basic things: Ayyadurai did create an email system and "it was recognized by the federal government." This is misleading in the extreme. It's amusing how they all use the exact same language. Larry Weber claims:
|
||||
|
||||
> On August 30, 1982, **the US government officially recognized V.A. Shiva Ayyadurai as the inventor of email** by awarding him the first US Copyright for "Email," "Computer Program for Electronic Mail System," for his 1978 invention. This was awarded at a time when Copyright was the only way to protect software inventions.
|
||||
|
||||
Leslie Michaelson says:
|
||||
|
||||
> On August 30,1982, V.A. Shiva Ayyadurai **received official recognition as the inventor of email from the U.S. government**, for the work he had done in 1978.
|
||||
|
||||
Every article in the series includes this image of his copyright registration:
|
||||
|
||||
[][12]
|
||||
|
||||
Except, if you know anything about copyright, you know that what they're claiming is not at all true. The registration of copyrights is about as close to a rubber-stamping process as is possible. It has nothing to do with "inventions" at all, but is rather a copyright for the specific software program. Ayyadurai received a copyright on his email program and that's it. It has absolutely nothing to do with him being the inventor of email.
|
||||
|
||||
Microsoft holds a copyright on Windows, but no one claims it "invented" the glass things you look outside your building with. Hell, no one even claims that Microsoft invented windowing user interfaces, because it did not. The name of the program and the fact that you can copyright it does not make you the "inventor" of the concept behind it.
|
||||
|
||||
Weber, Ayyadurai and his friends try to counter the "it's a copyright, not a patent" claim with an incredibly misleading response. Here's Michelson:
|
||||
|
||||
> On August 30, 1982, Shiva was issued the first Copyright for "Email", "Computer Program for Electronic Mail System." At that time, Copyright was the equivalent of a patent, as there was no other way to protect software inventions. Only in 1980 was the Copyright Act of 1976 amended to protect software. Patent law had not even caught up to software in 1980
|
||||
|
||||
Copyright was not, and has never been "the equivalent of a patent." Copyright and patents are two very different things. Copyright protects specific expression. Patents protect inventions. That's why copyright protected only the specific code that Ayyadurai wrote, rather than the concept of email. While it's true that software wasn't considered patentable by many at the time, that doesn't, in any way, mean that a copyright on a particular piece of software was the equivalent in any way, to a patent at the time.
|
||||
|
||||
To further their argument, both Weber and Michelson include nearly identical, but slightly different, infographics on the history of email, which (of course) start in 1978 with Ayyadurai's work. According to those charts, email was barely even a thing outside of UMDNJ until 1985 when offline email readers come about. The infographic is the work of the impressive sounding International Center for Integrative Systems. What's left out is that the "[Founder and Chairman][13]" of the International Center for Integrative Systems happens to be... a guy named V.A. Shiva Ayyadurai. The same infographic tosses in a "milestone" in email in 1995, when "Echomail" launched. Doesn't sound familiar? Echomail was a company started by... V.A. Shiva Ayyadurai.
|
||||
|
||||
The rest of the articles seem to just focus on attacking those who actually were involved in the invention of email and who dared to speak out against Ayyadurai's claims. The story, which includes no actual support, is that the folks at BBN decided in the early 80s that email security was a big business opportunity and rewrote history. Whether or not BBN played up their role in the history of email is debatable, but none of that changes the fact that they (and many others) were using email, and had email software, long before Ayyadurai did anything. At no point do any of them address the long history of email systems long before Ayyadurai arrived on the scene. Instead, they just talk about this grand conspiracy theory, claiming (ridiculously) that if BBN were outed as not being the inventor of email (even though no one really claims the company was the inventor of email) it would harm its business. That makes no sense at all. First of all, BBN's history of work related to the internet is long and well-detailed (there's even a [fantastic book][14] about it). Even if it had nothing to do with email, it's other work is much more impressive. Second, the company is currently owned by defense contracting giant Raytheon. Does anyone honestly think Raytheon cares one way or the other who "invented email"?
|
||||
|
||||
All of their "debunking" claims rest entirely on a RAND report written by David Crocker in 1977, where they take two sentences totally out of context. Here's what Ayyadurai, Weber and their friends claim Crocker said:
|
||||
|
||||
> "At this time, no attempt is being made to emulate a full-scale, inter-organizational mail system. The fact that the system is intended for use in various organizational contexts and by users of differing expertise makes it almost impossible to build a system which responds to all users' needs."
|
||||
|
||||
It's telling that Ayyadurai and his friends never actually tell you the name of the report or link to it. Because actually reading what Crocker wrote would undermine their argument. The report is called "Framework and Functions of the 'MS' Personal Message System" and you can read it here. Not only do Ayyadurai and his friends take Crocker entirely out of context, the two sentences above are not even contiguous sentences. They're not even on the same page. The first sentence is on page 18 of the paper. And it just says that this particular implementation (the program called MS) is focused on certain facets, and for MS "no attempt is being made to emulate a full-scale inter-organization mail system" even though the entire point of the paper is how various email implementations are clearly replicating inter-organizational mail systems. The second sentence comes on page 21 (with lots in between) and just focuses on the fact that lots of users have very different requests and desires, and it's impossible to satisfy everyone -- and that it, alone, is beyond the scope of this project. He's not, as Ayyadurai implies, claiming that building an interoffice email system is impossible. He's claiming that creating a full system that satisfies absolutely everyone is impossible. However, he does make it clear that other components are being worked on, and when combined could create a more functional email system. Here's that part, back in context:
|
||||
|
||||
> To construct a fully-detailed and monolithic message processing environment requires a much larger effort than has been possible with MS. In addition, the fact that the system is intended for use in various organizational contexts and by users of differing expertise makes it almost impossible to build a system which responds to all users' needs. Consequently, important segments of a full message environment have received little or no attention and decisions have been made with the expectation that other Unix capabilities will be used to augment MS. For example, MS has fairly primitive data-base management filing and cataloging) facilities and message folders have been implemented in a way which allows them to be modified by programs, such as text editors, which access them directly, rather than through the message system.
|
||||
|
||||
From the actual source documents (which, again, Ayyadurai and his friends fail to link to and totally misrepresent), it's clear that all Crocker is saying is that no single system will satisfy everyone's current interests. He's not saying it's impossible to create an interoffice email system. He's just saying that lots of different people have lots of different needs for an interoffice email system, and for the team building MS, it would be too difficult to satisfy everyone's exact requests, so they're focusing on certain features, knowing others will add other components later. And, given that people are still working to improve upon email today, it seems that's still basically true.
|
||||
|
||||
Back to the rest of the paper, which actually does a tremendous job undermining basically all of Ayyadurai's claims (again, which suggests why no one names or links to the full paper) -- in the very first paragraph (again, this is prior to Ayyadurai doing anything) it talks about research for "computer software" for "electronic mail." Ooops. It goes on:
|
||||
|
||||
> This report describes the design of one such program--the "MS" message system. Early electronic mail systems have existed on the larger computers. MS incorporates and expands upon many of the functions and concepts of such systems within an integrated package...
|
||||
|
||||
In other words, the very paper that Ayyadurai and his friends insist prove that there was no email prior to 1978 talks in depth about a variety of email programs. Again, remember that this was written in 1977. This is not historical revisionism. It goes on:
|
||||
|
||||
> One of the earliest and most popular applications of the ARPANET computer communications network has been the transfer of text messages between people using different computers. This "electronic mail" capability was originally grafted onto existing informal facilities; however, they proved inadequate. A large network greatly expands the base of potential communicators; when coupled with the communication convenience of a message system, there results a considerable expansion to the list of features desired by users. Systems which have responded to these increased user needs have resided on medium- and large-scaled computers.
|
||||
|
||||
In other words, lots of folks are working on email systems. Ayyadurai tries to brush all those aside by saying that his actually included things like "folders." But again, Crocker's paper notes:
|
||||
|
||||
> Messages reside in file "folders" and may contain any number of fields, or "components."
|
||||
|
||||
It actually has a whole section on folders. It also shows some sample messages at the time, showing "to," "from," "cc," "subject," and "message" fields, showing that the very basics of interoffice mail (such as "cc" -- standing for carbon copy, which was a standard bit of interoffice mail) had already moved into email. Here's a screenshot (which you can click for a larger version):
|
||||
|
||||
[][15]
|
||||
|
||||
Ayyadurai has built up his entire reputation around the (entirely false) claim that he "invented" email. His bio, his Twitter feed and his website all position himself as having invented email. He didn't. It looks like he wrote an implementation of an email system in 1978, long after others were working on similar things. He may have added some nice features, including the "blind carbon copy/bcc" concept (Update: Nope, bcc was in a [1977 RFC][16]). He also appears to have potentially been ahead of others in making a full address book be a part of the email system. He may, in fact, be the first person who shortened "electronic mail" to "email" which is cool enough, and he'd have an interesting claim if that's all he claimed. Unfortunately, he's claiming much, much more than that. He's set up [an entire website][17] in which he accuses lots of folks, including Techdirt, of unfairly "attacking" him. He apparently believes that some of the attacks on him are [because][18] he spoke out against corruption in India. Or because people think only rich white people can invent stuff. None of that is accurate. There's a simple fact, and it's that Ayyadurai did not invent email.
|
||||
|
||||
He does not even attempt to counter any of the actual facts. The documents that are presented are misleading or out of context. He misrepresents what a copyright registration means. And his main "smoking gun," in support of his claim that people are trying to unfairly write him out of history, is presented in a misleading way, out of context, with two entirely separate sentences pushed together to pretend they say something they didn't.
|
||||
|
||||
He's clearly quite proud of the email software he wrote in 1978, and that's great. He should be. It may have made some incremental improvements on what else was already out there, but it is not inventing email. It's also entirely possible that he was wholly unaware of everything else that was out there. And, again, that's great. We've talked many times in the past about multiple people coming up with the same ideas around the same time. Ayyadurai should be quite proud of what he's done. But he's simply not telling the truth when he claims to have invented email. His website is full of accolades from the past, including his Westinghouse award (which is a prestigious award for high schoolers), his copyrights and his later patents. There are local newspaper clippings. That's all great. It reminds me of the folder my mother has on all the nice things that happened to me as a kid. But none of it means he invented email.
|
||||
|
||||
It's unclear why Huffington Post is publishing this ludicrous and disproven narrative. It's unclear why one of the biggest names in PR is involved in all of this, though you can take some guesses. But there are facts, and they include that "electronic mail" existed long before V.A. Shiva Ayyadurai wrote his program as a precocious teenager. Huffington Post is either not disclosing a paid-for series of posts (which would be a massive ethical breach) or they've been taken for a ride. Neither option speaks well of HuffPo and its journalistic integrity.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.techdirt.com/articles/20140901/07280928386/huffpo-publishes-bizarre-misleading-factually-incorrect-multi-part-series-pretending-guy-invented-email-even-though-he-didnt.shtml
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://www.techdirt.com/articles/20120222/11132917842/how-guy-who-didnt-invent-email-got-memorialized-press-smithsonian-as-inventor-email.shtml
|
||||
[2]:http://www.huffingtonpost.com/news/the-history-of-email/
|
||||
[3]:http://www.nethistory.info/History%20of%20the%20Internet/email.html
|
||||
[4]:http://www.ir.bbn.com/~craig/email.pdf
|
||||
[5]:http://www.multicians.org/thvv/mail-history.html
|
||||
[6]:http://www.huffingtonpost.com/larry-weber/the-history-of-email-boy-who-invented-email_b_5690783.html
|
||||
[7]:http://en.wikipedia.org/wiki/Larry_Weber
|
||||
[8]:http://www.huffingtonpost.com/leslie-p-michelson/the-history-of-email-invention-of-email_b_5707913.html
|
||||
[9]:http://www.huffingtonpost.com/leslie-p-michelson/history-of-email-introduction_b_5726018.html
|
||||
[10]:http://www.huffingtonpost.com/robert-field/history-of-email-first-email-system_b_5722000.html
|
||||
[11]:http://www.huffingtonpost.com/2014/08/28/email-shiva-ayyadurai_n_5731606.html
|
||||
[12]:https://imgur.com/AscOfQh
|
||||
[13]:http://integrativesystems.org/board.asp
|
||||
[14]:http://www.amazon.com/gp/product/0684832674/ref=as_li_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=0684832674&linkCode=as2&tag=techdirtcom-20&linkId=OSP5B7BVSLAG5XNX
|
||||
[15]:https://imgur.com/KJW7BnA
|
||||
[16]:http://tools.ietf.org/html/rfc733
|
||||
[17]:http://www.inventorofemail.com/index.asp
|
||||
[18]:http://gizmodo.com/5888702/corruption-lies-and-death-threats-the-crazy-story-of-the-man-who-pretended-to-invent-email
|
||||
@ -1,48 +0,0 @@
|
||||
CoreOS breaks with Docker
|
||||
================================================================================
|
||||
> Summary: CoreOS, a new enterprise Linux company and a Docker partner, is now proposing its own alternative to Docker's container technology.
|
||||
|
||||
[Docker][1] exploded out of nowhere in 2014 to make container technology white hot in cloud and datacenter technical circles. Even [Microsoft joined its open-source virtualization revolution][2]. Now, however, early Docker supporter [CoreOS][3], a new large-scale Linux distributor vendor, is turning its back on it and developing its own container technology: [Rocket][4].
|
||||
|
||||
|
||||
|
||||
While [CoreOS][5] is relatively unknown outside of Linux circles and Silicon Valley, it's seen by those in the know as an up and coming Linux distribution for datacenters and clouds. It's not an insignificant company crying foul, because [Docker's take on virtualization has proven to be so popular][6]. Indeed, CoreOS currently requires Docker to work well, and Brandon Philips, CoreOS' co-founder and CTO, has been a top Docker contributor and was serving on the Docker governance board.
|
||||
|
||||
So, why is CoreOS breaking with Docker? First, because "We believe strongly in the Unix philosophy: Tools should be independently useful, but have clean integration points." However, it also said that "Docker now is building tools for launching cloud servers, systems for clustering, and a wide range of functions: Building images, running images, uploading, downloading, and eventually even overlay networking, all compiled into one monolithic binary running primarily as root on your server."
|
||||
|
||||
In short, instead of Docker being a Unix-style, simple reusable component, CoreOS sees Docker becoming a platform. And CoreOS has no interest in that.
|
||||
|
||||
Instead, with Rocket, they propose going back to the [original Docker proposal][7] for what a container should be.
|
||||
|
||||
CoreOS spells out that Rocket will be:
|
||||
|
||||
- **Composable**: All tools for downloading, installing, and running containers should be well integrated, but independent and composable.
|
||||
- **Secure**: Isolation should be pluggable, and the crypto primitives for strong trust, image auditing, and application identity should exist from day one.
|
||||
- **Image distribution**: Discovery of container images should be simple and facilitate a federated namespace and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.
|
||||
- **Open**: The format and runtime should be well specified and developed by a community. We want independent implementations of tools to be able to run the same container consistently.
|
||||
|
||||
To do this, CoreOS is not forking Docker. Alex Polvi, CoreOS' CEO, wrote, "From a security and composability perspective, the Docker process model — where everything runs through a central daemon — is fundamentally flawed. To 'fix' Docker would essentially mean a rewrite of the project, while inheriting all the baggage of the existing implementation."
|
||||
|
||||
CoreOS already has an [alpha version of Rocket on GitHub][8], but it's still open to other ideas on how to build a Docker alternative. At the same time, however, CoreOS states that it won't be leaving Docker behind. "We will continue to make sure CoreOS is the best place to run Docker ... [and] expect Docker to continue to be fully integrated with CoreOS as it is today."
|
||||
|
||||
While I can understand CoreOS' concerns, I find it hard to imagine that its attempt to come up with a successful alternative to Docker will come to anything. Docker certainly isn't perfect, but in a matter of mere months, it gathered support from almost everyone in the enterprise operating system business. The only way I can see CoreOS' Rocket launching successfully will be if Docker falls flat on its face, and I just don't see that happening.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.zdnet.com/coreos-breaks-with-docker-7000036331/#ftag=RSS06bb67b
|
||||
|
||||
作者：[Steven J. Vaughan-Nichols][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.zdnet.com/meet-the-team/us/steven-j-vaughan-nichols/
|
||||
[1]:https://www.docker.com/
|
||||
[2]:http://www.zdnet.com/docker-container-support-coming-to-microsofts-next-windows-server-release-7000034708
|
||||
[3]:https://coreos.com/
|
||||
[4]:https://coreos.com/blog/rocket
|
||||
[5]:http://www.zdnet.com/coreos-linux-for-the-cloud-and-the-datacenter-7000031137/
|
||||
[6]:http://www.zdnet.com/what-is-docker-and-why-is-it-so-darn-popular-7000032269/
|
||||
[7]:https://github.com/docker/docker/commit/0db56e6c519b19ec16c6fbd12e3cee7dfa6018c5
|
||||
[8]:https://github.com/coreos/rocket
|
||||
@ -1,49 +0,0 @@
|
||||
CoreOS Team Develops Rocket, Breaks with Docker
|
||||
================================================================================
|
||||
|
||||
|
||||
[Docker][1] has easily emerged as one of the top open source stories of the year, and has helped many organizations [benefit from container technology][2]. As we’ve reported, even Google is [working closely][3] with it, and Microsoft is as well.
|
||||
|
||||
However, the folks behind CoreOS, a very popular Linux flavor for use in cloud deployments, are developing their own container technology, [dubbed Rocket][4], which will actually compete with Docker. Here are the details.
|
||||
|
||||
Rocket is a new container runtime, designed for composability, security, and speed, according to the CoreOS team. The group has released a [prototype version on GitHub][5] to begin getting community feedback.
|
||||
|
||||
“When Docker was first introduced to us in early 2013, the idea of a “standard container” was striking and immediately attractive: a simple component, a composable unit, that could be used in a variety of systems. The Docker repository [included a manifesto][6] of what a standard container should be. This was a rally cry to the industry, and we quickly followed. We thought Docker would become a simple unit that we can all agree on.”
|
||||
|
||||
“Unfortunately, a simple re-usable component is not how things are playing out. Docker now is building tools for launching cloud servers, systems for clustering, and a wide range of functions: building images, running images, uploading, downloading, and eventually even overlay networking, all compiled into one monolithic binary running primarily as root on your server. The standard container manifesto [was removed][7]. We should stop talking about Docker containers, and start talking about the Docker Platform.”
|
||||
|
||||
“We still believe in the original premise of containers that Docker introduced, so we are doing something about it. Rocket is a command line tool, rkt, for running App Containers. An ‘App Container’ is the specification of an image format, container runtime, and a discovery mechanism.”
|
||||
|
||||
There is a specification coming for App Container Images (ACI). Anyone can [Read about and contribute to the ACI draft][8].
|
||||
|
||||
The Register also [notes this interesting aspect][9] of Rocket:
|
||||
|
||||
“Significantly, all of CoreOS's tools for working with App Container will be integrated, yet independent from one another. Rocket can run as a standalone tool on any flavor of Linux, not just CoreOS.”
|
||||
|
||||
In a [blog post][10], Docker CEO Ben Golub voiced disagreement with CoreOS's move, and he writes:
|
||||
|
||||
“There are technical or philosophical differences, which appears to be the case with the recent announcement regarding Rocket. We hope to address some of the technical arguments posed by the Rocket project in a subsequent post.”
|
||||
|
||||
It sounds like a standards skirmish is going to come of all this, but, as is often the case with standards confrontations, users may benefit from the competition.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ostatic.com/blog/coreos-team-develops-rocket-breaks-with-docker
|
||||
|
||||
作者：[Sam Dean][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://ostatic.com/member/samdean
|
||||
[1]:https://www.docker.com/
|
||||
[2]:http://ostatic.com/blog/linux-containers-with-docker
|
||||
[3]:http://ostatic.com/blog/google-sets-sights-squarely-on-docker-with-new-container-engine
|
||||
[4]:https://coreos.com/blog/rocket/
|
||||
[5]:https://github.com/coreos/rocket
|
||||
[6]:https://github.com/docker/docker/commit/0db56e6c519b19ec16c6fbd12e3cee7dfa6018c5
|
||||
[7]:https://github.com/docker/docker/commit/eed00a4afd1e8e8e35f8ca640c94d9c9e9babaf7
|
||||
[8]:https://github.com/coreos/rocket/blob/master/app-container/SPEC.md#app-container-image
|
||||
[9]:http://www.theregister.co.uk/2014/12/01/coreos_rocket_announcement/
|
||||
[10]:http://blog.docker.com/2014/12/initial-thoughts-on-the-rocket-announcement/
|
||||
@ -1,57 +0,0 @@
|
||||
Interview: Apache Software Foundation Elevates Drill to Top-Level Project
|
||||
================================================================================
|
||||
|
||||
|
||||
The Apache Software Foundation (ASF) has [announced][1] that [Apache Drill][2] has graduated from the Apache Incubator to become a Top-Level Project (TLP).
|
||||
|
||||
Apache Drill is billed as the world's first schema-free SQL query engine that delivers real-time insights by removing the constraint of building and maintaining schemas before data can be analyzed.
|
||||
|
||||
Drill enables rapid application development on Apache Hadoop and also allows enterprise BI analysts to access Hadoop in a self-service fashion. OStatic caught up with Tomer Shiran (shown here), a member of the Drill Project Management Committee, to get his thoughts. Here they are in an interview.
|
||||
|
||||
**Can you provide a brief overview of what Drill is and what kinds of users it can make a difference for?**
|
||||
|
||||
Drill is the world's first distributed, schema-free SQL engine. Analysts and developers can use Drill to interactively explore data in Hadoop and other NoSQL databases, such as HBase and MongoDB. There's no need to explicitly define and maintain schemas, as Drill can automatically leverage the structure that's embedded in the data.
|
||||
|
||||
This enables self-service data exploration, which is not possible with traditional data warehouses or SQL-on-Hadoop solutions like Hive and Impala, in which DBAs must manage schemas and transform the data before it can be analyzed.
|
||||
|
||||
**What level of community involvement with Drill already exists?**
|
||||
|
||||
Drill is an Apache project, so it's not owned by any vendor. Developers in the community can contribute to Drill. MapR currently employs the largest number of contributors, but we're seeing an increasing number of contributions from other companies, and that trend has been accelerating in recent months.
|
||||
|
||||
For example, the MongoDB storage plugin (enabling queries on MongoDB) was contributed by developers at Intuit.
|
||||
|
||||
**Hadoop has a lot of momentum on the Big Data front. How can Drill help organizations leveraging Hadoop?**
|
||||
|
||||
Drill is the ideal interactive SQL engine for Hadoop. One of the main reasons organizations choose Hadoop is due to its flexibility and agility. Unlike traditional databases, getting data into Hadoop is easy, and users can load data in any shape or size on their own. Early attempts at SQL on Hadoop (eg, Hive, Impala) force schemas to be created and maintained even for self-describing data like JSON, Parquet and HBase tables.
|
||||
|
||||
These systems also require data to be transformed before it can be queried. Drill is the only SQL engine for Hadoop that doesn't force schemas to be defined before data can be queried, and doesn't require any data transformations. In other words, Drill maintains the flexibility and agility paradigms that made Hadoop popular, thus making it the natural technology for data exploration and BI on Hadoop.
|
||||
|
||||
**What does Drill's status as a top-level project at Apache mean for its development and future?**
|
||||
|
||||
Drill's graduation to a top-level project is an indication that Drill has established a strong community of users and developers. Graduation is a decision made by the Apache Software Foundation (ASF) board, and it provides confidence to Drill's potential users and contributors that the project has a strong foundation. From a governance standpoint, a top-level project has its own board (also known as PMC). The PMC Chair (Jacques Nadeau) is a VP at Apache.
|
||||
|
||||
**How do you think Drill will evolve over the next several years?**
|
||||
|
||||
Drill has a large and growing community of contributors. Drill 1.0 will be out in Q1'15. We'll see many new features over the next several years. Here are a just a few examples of initiatives that are currently under way:
|
||||
|
||||
Drill currently supports HDFS, HBase and MongoDB. Additional data sources are being added, including Cassandra and RDBMS (all JDBC-enabled databases, including Oracle and MySQL). A single query can incorporate/join data from different sources. In the next year, Drill will become the standard SQL engine for modern datastores (which are all schema-free in nature): Hadoop, NoSQL databases - HBase/MongoDB/Cassandra, and search - Elasticsearch/Solr.
|
||||
|
||||
A single enterprise or cloud provider will be able to serve multiple groups/departments/organizations, each having its own workloads and SLA requirements. For example, in Drill 1.0 will support user impersonation, meaning that a query can only access the data that the user is authorized to access, and this will work with all supported data sources (Hadoop, HBase, MongoDB, etc.)
|
||||
|
||||
Drill will support not only SELECT and CREATE TABLE ... AS SELECT (CTAS) queries, but also INSERT/UPDATE/DELETE, enabling Drill to be used for operational applications (in addition to data exploration and analytics). Drill will also support the ultra-low latency and high concurrency required for such use cases.
|
||||
|
||||
Full TPC-DS support. Unlike other SQL-on-Hadoop technologies, Drill is designed to support the ANSI SQL standard as opposed to a SQL-like language. This provides better support for BI and other tools. Drill will be able to run TPC-DS, unmodified, in 2015.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ostatic.com/blog/interview-apache-software-foundation-elevates-drill-to-top-level-project
|
||||
|
||||
作者：[Sam Dean][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://ostatic.com/member/samdean
|
||||
[1]:https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces66
|
||||
[2]:http://drill.apache.org/
|
||||
@ -1,4 +1,3 @@
|
||||
惊现译者～CHINAANSHE 翻译!!
|
||||
How to configure HTTP load balancer with HAProxy on Linux
|
||||
================================================================================
|
||||
Increased demand on web based applications and services are putting more and more weight on the shoulders of IT administrators. When faced with unexpected traffic spikes, organic traffic growth, or internal challenges such as hardware failures and urgent maintenance, your web application must remain available, no matter what. Even modern devops and continuous delivery practices can threaten the reliability and consistent performance of your web service.
|
||||
|
||||
@ -1,143 +0,0 @@
|
||||
7 Things to Do After Installing Ubuntu 14.10 Utopic Unicorn
|
||||
================================================================================
|
||||
After you’ve installed or [upgraded to Ubuntu 14.10][1], known by its codename ‘Utopic Unicorn’, there are a few things you should do to get it up and running in tip-top shape.
|
||||
|
||||
Whether you’ve performed a fresh install or upgraded an existing version, here’s our biannual checklist of post-install tasks to get started with.
|
||||
|
||||
### 1. Get Acquainted ###
|
||||
|
||||
|
||||
|
||||
The Ubuntu Browser
|
||||
|
||||
The majority of changes rocking up in Ubuntu 14.10 aren’t immediately visible (save for some new wallpapers). That said, there are a bunch of freshly updated apps to get familiar with.
|
||||
|
||||
Preinstalled are the latest versions of workhouse staples **Mozilla Firefox**, **Thunderbird**, and **LibreOffice**. Dig a little deeper and you’ll also find Evince 3.14, and a brand new version of the “Ubuntu Web Browser” app, used for handling web-apps.
|
||||
|
||||
While you’re getting familiar, be sure to fire up the Software Updater tool to **check for any impromptu issues Ubuntu has found and fixed** post-release. Yes, I know: you only just upgraded. But, even so — bugs don’t adhere to deadlines like developers do!
|
||||
|
||||
### 2. Personalise The Desktop ###
|
||||
|
||||
|
||||
|
||||
New wallpapers in 14.10
|
||||
|
||||
It’s your desktop PC, so don’t put off making it look, feel and behave how you like.
|
||||
|
||||
Your first port of call might be changing the desktop wallpaper to one of the [twelve stunning new backgrounds][2] included in 14.10, ranging from retro record player to illustrated unicorn.
|
||||
|
||||
Wallpapers and a host of other theme and layout options are accessible from the **Appearance Settings** pane of the System Settings app. From here you can:
|
||||
|
||||
- Switch to a different theme
|
||||
- Adjust launcher size & behaviour
|
||||
- Enable workspaces & desktop icons
|
||||
- Put app menus back into app windows
|
||||
|
||||
For some nifty new themes be sure to check out our **‘themes & icons’ category** here on the site.
|
||||
|
||||
### 3. Install Graphics Card Drivers ###
|
||||
|
||||
|
||||
|
||||
If you plan on playing the [latest Steam games][3], watching high-definition video or working with graphically intensive software you’ll want to enable the latest Linux graphics drivers available for your hardware.
|
||||
|
||||
Ubuntu makes this easy:
|
||||
|
||||
- Open up the Software & Updates tool from the Unity Dash
|
||||
- Click the ‘Additional Drivers‘ tab
|
||||
- Follow any on-screen prompts to check, install and apply changes
|
||||
|
||||
### 4. Enable Music & Video Codecs ###
|
||||
|
||||
|
||||
|
||||
Games sorted, now to make **music and video files work just as well**.
|
||||
|
||||
Most popular formats, .mp3, .m4a, .mov, etc., will work fine in Ubuntu — after a little cajoling. Patent-encumbered codecs cannot ship in Ubuntu for legal reasons, leaving you unable to play popular audio and video formats out of the (invisible) box.
|
||||
|
||||
Don’t panic. To play music or watch video you can install all of the codecs you need quickly, and through the Ubuntu Software Center.
|
||||
|
||||
- [Install Third-Party Codecs][4]
|
||||
|
||||
### 5. Pimp Your Privacy ###
|
||||
|
||||
|
||||
|
||||
The Unity Dash is a great one-stop hub for finding stuff, be it a PDF file lurking on your computer or the current weather forecast in Stockholm, Sweden.
|
||||
|
||||
But the diversity of data surfaced through the Dash in just a few keystrokes doesn’t suit everyone’s needs. So you may want to dial down the noise and restrict what shows up.
|
||||
|
||||
To stop certain files and folders from searched in the Dash and/or to disable all ‘online’ results returned for a query, head to the **Privacy & Security** section in System Settings.
|
||||
|
||||
Here you’ll find all the tools, options and configuration switches you need, including options to:
|
||||
|
||||
- Choose what apps & files can be searched from the Dash
|
||||
- Whether to require a password on waking from suspend
|
||||
- Disable sending error reports to Canonical
|
||||
- Turn off all ‘online’ features of the Dash
|
||||
|
||||
### 6. Swap The Default Apps For Your Faves ###
|
||||
|
||||
|
||||
|
||||
Make it yours
|
||||
|
||||
Ubuntu comes preloaded with a tonne of apps, including a web browser (Mozilla Firefox), e-mail client (Thunderbird), music player (Rhythmbox), office suite (LibreOffice) and instant messenger (Empathy Instant Messenger).
|
||||
|
||||
All well and good, they’re not everyone’s cup of tea. The Ubuntu Software Center is home to a slew of app alternatives, including:
|
||||
|
||||
- VLC – Versatile media player
|
||||
- Steam – Games distribution platform
|
||||
- [Geary — Easy-to-use desktop e-mail app][5]
|
||||
- GIMP – Advanced image editor similar to Photoshop
|
||||
- Clementine — Stylish, fully-featured music player
|
||||
- Chromium open-source version of Google Chrome (without Flash)
|
||||
|
||||
The Ubuntu Software Center plays host to a huge range of other apps, many of which you might not have heard of before. Since most apps are free, don’t be scared to try things out!
|
||||
|
||||
### 7. Grab The Essentials ###
|
||||
|
||||
|
||||
|
||||
Netflix in Chrome on Ubuntu
|
||||
|
||||
Software Center apps aside, you may also wish to grab big-name apps like Skype, Spotify and Dropbox.
|
||||
|
||||
Google Chrome is also a must if you wish to watch Netflix natively on Ubuntu or benefit from the latest, safest version of Flash.
|
||||
|
||||
Most of these apps are available to download directly from their respective websites and can be installed on Ubuntu with a couple of clicks.
|
||||
|
||||
- [Download Skype for Linux][6]
|
||||
- [Download Google Chrome for Linux][7]
|
||||
- [Download Dropbox for Linux][8]
|
||||
- [How to Install Spotify in Ubuntu][9]
|
||||
|
||||
Talking of Google Chrome — did you know you can (unofficially) [install and run Android apps through it?][9] Oh yes ;)
|
||||
|
||||
#### Finally… ####
|
||||
|
||||
The items above are not the only ones applicable post-upgrade. Read through and follow the ones that chime with you, and feel free to ignore those that don’t.
|
||||
|
||||
Secondly, this is a list for those who’ve upgraded to or installed Ubuntu 14.10. We’re not going walk you through carving it up into something that isn’t Ubuntu. If Unity isn’t your thing that’s fine, but be logical about it; save yourself some time and install one of the official flavours or offshoots instead.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/10/7-things-to-do-after-installing-ubuntu-14-10-utopic-unicorn
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/10/ubuntu-14-10-release-download-now
|
||||
[2]:http://www.omgubuntu.co.uk/2014/09/ubuntu-14-10-wallpaper-contest-winners
|
||||
[3]:http://www.omgubuntu.co.uk/category/gaming
|
||||
[4]:https://apps.ubuntu.com/cat/applications/ubuntu-restricted-extras/
|
||||
[5]:http://www.omgubuntu.co.uk/2014/09/new-shotwell-geary-stable-release-available-to-downed
|
||||
[6]:http://www.skype.com/en/download-skype/skype-for-linux/
|
||||
[7]:http://www.google.com/chrome
|
||||
[8]:https://www.dropbox.com/install?os=lnx
|
||||
[9]:http://www.omgubuntu.co.uk/2013/01/how-to-install-spotify-in-ubuntu-12-04-12-10
|
||||
[10]:http://www.omgubuntu.co.uk/2014/09/install-android-apps-ubuntu-archon
|
||||
@ -1,5 +1,3 @@
|
||||
[felixonmars translating...]
|
||||
|
||||
“ntpq -p” output
|
||||
================================================================================
|
||||
The [Gentoo][1] (and others?) [incomplete man pages for “ntpq -p”][2] merely give the description: “*Print a list of the peers known to the server as well as a summary of their state.*”
|
||||
|
||||
@ -1,4 +1,3 @@
|
||||
[felixonmars translating...]
|
||||
How To Use Emoji Anywhere With Twitter's Open Source Library
|
||||
================================================================================
|
||||
> Embed them in webpages and other projects via GitHub.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
forsil translating ...
|
||||
|
||||
Undelete Files on Linux Systems
|
||||
================================================================================
|
||||
Often times, a computer user will delete a needed file accidentally and not have an easy way to regain or recreate the file. Thankfully, files can be undeleted. When a user deletes a file, it is not gone, only hidden for some time. Here is how it all works. On a filesystem, the system has what is called a file allocation list. This list keeps track of what files are where on the storage unit (hard-drive, MicroSD card, flash-drive, etc.). When a file is deleted, the filesystem will perform one of two tasks on the allocation table. The file's entry on the file allocation table marked as "free space" or the file's entry on the list is erased and then the space is marked as free. Now, if a file needs to be placed on the storage unit, the operating system will put the file in the space marked as empty. After the new file is written to the "empty space", the deleted file is now gone forever. When a deleted file is to be recovered, the user must not manipulate any files because if the "empty space" is used, then the file can never be retrieved.
|
||||
|
||||
@ -1,249 +0,0 @@
|
||||
文章重复
|
||||
How to create a custom backup plan for Debian with backupninja
|
||||
================================================================================
|
||||
Backupninja is a powerful and highly-configurable backup tool for Debian based distributions. In the [previous tutorial][1], we explored how to install backupninja and how to set up two backup actions for the program to perform. However, we should note that those examples were only "the tip of the iceberg," so to speak. In this post we will discuss how to leverage custom handlers and helpers that allow this program to be customized in order to accomplish almost any backup need that you can think of.
|
||||
|
||||
And believe me - that is not an overstatement, so let's begin.
|
||||
|
||||
### A Quick Review of Backupninja ###
|
||||
|
||||
One of backupninja's distinguishing features is the fact that you can just drop plain text configuration or action files in /etc/backup.d, and the program will take care of the rest. In addition, we can write custom scripts (aka "handlers") and place them in /usr/share/backupninja to handle each type of backup action. Furthermore, we can have these scripts be executed via ninjahelper's ncurses-based interactive menus (aka "helpers") to guide us to create the configuration files we mentioned earlier, minimizing the chances of human error.
|
||||
|
||||
### Creating a Custom Handler and Helper ###
|
||||
|
||||
Our goal in this case is to create a script to handle the backup of chosen home directories into a tarball with either gzip or bzip2 compression, excluding music and video files. We will simply name this script home, and place it under /usr/backup/ninja.
|
||||
|
||||
Although you could achieve the same objective with the default tar handler (refer to /usr/share/backupninja/tar and /usr/share/backupninja/tar.helper), we will use this approach to show how to create a useful handler script and ncurses-based helper from scratch. You can then decide how to apply the same principles depending on your specific needs.
|
||||
|
||||
Note that since handlers are sourced from the main script, there is no need to start with #!/bin/bash at the top.
|
||||
|
||||
Our proposed handler (/usr/share/backupninja/home) is as follows. It is heavily commented for clarification. The getconf function is used to read the backup action's configuration file. If you specify a value for a variable here, it will override the corresponding value present in the configuration file:
|
||||
|
||||
# home handler script for backupninja
|
||||
|
||||
# Every backup file will identify the host by its FQDN
|
||||
getconf backupname
|
||||
|
||||
# Directory to store backups
|
||||
getconf backupdir
|
||||
|
||||
# Default compression
|
||||
getconf compress
|
||||
|
||||
# Include /home directory
|
||||
getconf includes
|
||||
|
||||
# Exclude files with *.mp3 and *.mp4 extensions
|
||||
getconf excludes
|
||||
|
||||
# Default extension for the packaged backup file
|
||||
getconf EXTENSION
|
||||
|
||||
# Absolute path to date binary
|
||||
getconf TAR `which tar`
|
||||
|
||||
# Absolute path to date binary
|
||||
getconf DATE `which date`
|
||||
|
||||
# Chosen date format
|
||||
DATEFORMAT="%Y-%m-%d"
|
||||
|
||||
# If backupdir does not exist, exit with fatal error
|
||||
if [ ! -d "$backupdir" ]
|
||||
then
|
||||
mkdir -p "$backupdir" || fatal "Can not make directory $backupdir"
|
||||
fi
|
||||
|
||||
# If backupdir is not writeable, exit with fatal error as well
|
||||
if [ ! -w "$backupdir" ]
|
||||
then
|
||||
fatal "Directory $backupdir is not writable"
|
||||
fi
|
||||
|
||||
# Set the right tar option as per the chosen compression format
|
||||
case $compress in
|
||||
"gzip")
|
||||
compress_option="-z"
|
||||
EXTENSION="tar.gz"
|
||||
;;
|
||||
"bzip")
|
||||
compress_option="-j"
|
||||
EXTENSION="tar.bz2"
|
||||
;;
|
||||
"none")
|
||||
compress_option=""
|
||||
;;
|
||||
*)
|
||||
warning "Unknown compress filter ($tar_compress)"
|
||||
compress_option=""
|
||||
EXTENSION="tar.gz"
|
||||
;;
|
||||
esac
|
||||
|
||||
# Exclude the following file types / directories
|
||||
exclude_options=""
|
||||
for i in $excludes
|
||||
do
|
||||
exclude_options="$exclude_options --exclude $i"
|
||||
done
|
||||
|
||||
# Debugging messages, performing backup
|
||||
debug "Running backup: " $TAR -c -p -v $compress_option $exclude_options \
|
||||
-f "$backupdir/$backupname-"`$DATE "+$DATEFORMAT"`".$EXTENSION" \
|
||||
$includes
|
||||
|
||||
# Redirect standard output to a file with .list extension
|
||||
# and standard error to a file with .err extension
|
||||
$TAR -c -p -v $compress_option $exclude_options \
|
||||
-f "$backupdir/$backupname-"`$DATE "+$DATEFORMAT"`".$EXTENSION" \
|
||||
$includes \
|
||||
> "$backupdir/$backupname-"`$DATE "+$DATEFORMAT"`.list \
|
||||
2> "$backupdir/$backupname-"`$DATE "+$DATEFORMAT"`.err
|
||||
|
||||
[ $? -ne 0 ] && fatal "Tar backup failed"
|
||||
|
||||
Next, we will create our helper file (/usr/share/backupninja/home.helper) so that our handlers shows up as a menu in ninjahelper:
|
||||
|
||||
# Backup action's description. Separate words with underscores.
|
||||
HELPERS="$HELPERS home:backup_of_home_directories"
|
||||
|
||||
home_wizard() {
|
||||
home_title="Home action wizard"
|
||||
|
||||
backupname=`hostname --fqdn`
|
||||
|
||||
# Specify default value for the time when this backup actions is supposed to run
|
||||
inputBox "$home_title" "When to run this action?" "everyday at 01"
|
||||
[ $? = 1 ] && return
|
||||
home_when_run="when = $REPLY"
|
||||
|
||||
# Specify default value for backup file name
|
||||
inputBox "$home_title" "\"Name\" of backups" "$backupname"
|
||||
[ $? = 1 ] && return
|
||||
home_backupname="backupname = $REPLY"
|
||||
backupname="$REPLY"
|
||||
|
||||
# Specify default directory to store the backups
|
||||
inputBox "$home_title" "Directory where to store the backups" "/var/backups/home"
|
||||
[ $? = 1 ] && return
|
||||
home_backupdir="backupdir = $REPLY"
|
||||
|
||||
# Specify default values for the radiobox
|
||||
radioBox "$home_title" "Compression" \
|
||||
"none" "No compression" off \
|
||||
"gzip" "Compress with gzip" on \
|
||||
"bzip" "Compress with bzip" off
|
||||
[ $? = 1 ] && return;
|
||||
result="$REPLY"
|
||||
home_compress="compress = $REPLY "
|
||||
|
||||
REPLY=
|
||||
while [ -z "$REPLY" ]; do
|
||||
formBegin "$home_title: Includes"
|
||||
formItem "Include:" /home/gacanepa
|
||||
formDisplay
|
||||
[ $? = 0 ] || return 1
|
||||
home_includes="includes = "
|
||||
for i in $REPLY; do
|
||||
[ -n "$i" ] && home_includes="$home_includes $i"
|
||||
done
|
||||
done
|
||||
|
||||
REPLY=
|
||||
while [ -z "$REPLY" ]; do
|
||||
formBegin "$home_title: Excludes"
|
||||
formItem "Exclude:" *.mp3
|
||||
formItem "Exclude:" *.mp4
|
||||
# Add as many “Exclude” text boxes as needed to specify other exclude options
|
||||
formItem "Exclude:"
|
||||
formItem "Exclude:"
|
||||
formDisplay
|
||||
[ $? = 0 ] || return 1
|
||||
home_excludes="excludes = "
|
||||
for i in $REPLY; do
|
||||
[ -n "$i" ] && home_excludes="$home_excludes $i"
|
||||
done
|
||||
done
|
||||
|
||||
# Save the config
|
||||
get_next_filename $configdirectory/10.home
|
||||
cat > $next_filename <<EOF
|
||||
$home_when_run
|
||||
$home_backupname
|
||||
$home_backupdir
|
||||
$home_compress
|
||||
$home_includes
|
||||
$home_excludes
|
||||
|
||||
# tar binary - have to be GNU tar
|
||||
TAR `which tar`
|
||||
DATE `which date`
|
||||
DATEFORMAT "%Y-%m-%d"
|
||||
EXTENSION tar
|
||||
|
||||
EOF
|
||||
# Backupninja requires that configuration files be chmoded to 600
|
||||
chmod 600 $next_filename
|
||||
}
|
||||
|
||||
### Running Ninjahelper ###
|
||||
|
||||
Once we have created our handler script named home and the corresponding helper named home.helper, let's run ninjahelper command to create a new backup action:
|
||||
|
||||
# ninjahelper
|
||||
|
||||
And choose create a new backup action.
|
||||
|
||||
|
||||
|
||||
We will now be presented with the available action types. Let's select "backup of home directories":
|
||||
|
||||
|
||||
|
||||
The next screens will display the default values as set in the helper (only 3 of them are shown here). Feel free to edit the values in the text box. Particularly, refer to the scheduling section of the documentation for the right syntax for the when variable.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
When you are done creating the backup action, it will show in ninjahelper's initial menu:
|
||||
|
||||
|
||||
|
||||
Then you can press ENTER to show the options available for this action. Feel free to experiment with them, as their description is quite straightforward.
|
||||
|
||||
Particularly, "run this action now" will execute the backup action in debug mode immediately regardless of the scheduled time:
|
||||
|
||||
|
||||
|
||||
Should the backup action fail for some reason, the debug will display an informative message to help you locate the error and correct it. Consider, for example, the following error messages that were displayed after running a backup action with bugs that have not been corrected yet:
|
||||
|
||||
|
||||
|
||||
The image above tells you that the connection needed to complete the backup action could not be completed because the remote host seems to be down. In addition, the destination directory specified in the helper file does not exist. Once you correct the problems, re-run the backup action.
|
||||
|
||||
A few things to remember:
|
||||
|
||||
|
||||
- If you create a custom script in /usr/share/backupninja (e.g., foobar) to handle a specific backup action, you also need to write a corresponding helper (e.g., foobar.helper) in order to create, through ninjahelper, a file named 10.foobar (11 and onward for further actions as well) in /etc/backup.d, which is the actual configuration file for the backup action.
|
||||
- You can execute your backups at any given time via ninjahelper as explained earlier, or have them run as per the specified frequency in the when variable.
|
||||
|
||||
### Summary ###
|
||||
|
||||
In this post we have discussed how to create our own backup actions from scratch and how to add a related menu in ninjahelper to facilitate the creation of configuration files. With the previous [backupninja article][2] and the present one I hope I've given you enough good reasons to go ahead and at least try it.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://xmodulo.com/create-custom-backup-plan-debian.html
|
||||
|
||||
作者：[Gabriel Cánepa][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://xmodulo.com/author/gabriel
|
||||
[1]:http://xmodulo.com/backup-debian-system-backupninja.html
|
||||
[2]:http://xmodulo.com/backup-debian-system-backupninja.html
|
||||
Loading…
Reference in New Issue
Block a user