Today, July 26, 2016, Canonical and The Document Foundation (TDF) announced that the company behind the popular Ubuntu operating system had joined the LibreOffice project Advisory Board.
If you're using the Ubuntu Linux OS on your personal computer, you are aware of the fact that the award-winning LibreOffice office suite is installed by default. Canonical chose to use LibreOffice as the default office suite for its widely-used GNU/Linux operating system since the first release of the open-source software in early 2011.
Now that Canonical announced the availability of Snaps as universal binary packages for Ubuntu and other supported GNU/Linux distributions, many application developers decided to offer their software in the Snap package format, and it looks like The Document Foundation is among the first to adopt the latest Snappy technologies for LibreOffice.
The first time I installed Ubuntu on my computer, when I was sixteen, I was astonished by the number of filesystems that were available for the system installation. There were so many that I was left overwhelmed and confused. I was worried that if I picked the wrong one my system might run too slow or that it might be more problematic than another. I wanted to know which was the best.
Since then, things have changed quite a bit. Many Linux distributions offer a ‘standard’ filesystem that an installation will default to unless otherwise specified. I think this was a very good move because it assists newcomers in making a decision and being comfortable with it. But, for those that are still unsure of some of the contemporary offerings, we’ll be going through them today.
- The Death of Software Patents and Microsoft’s Coup Against Yahoo! Made the Company Worthless
- Munich Attack Mentioned by EPO But Not Ansbach
- Kluwer Thinks People Are Clueless About the Unitary Patent System and Pretends It’s Business as Usual
- Almost Everything That the Government Accountability Office Says is Applicable to the EPO
- Microsoft Says It Loves Linux, But Its Anti-Linux Patent Trolls Are Still Around and Active
- Links 26/7/2016: Microsoft Growing Desperate, Linux 4.8 Visions
- Links 25/7/2016: Linux 4.7 Final, PostgreSQL 9.6 Beta 3
KDE released the second maintenance update for the KDE Plasma 5.7 desktop environment series, which has already been adopted by several popular GNU/Linux operating systems.
The Linaro Developer Cloud has gone live, and users can apply to test an ARM-based server with Linux
Just one day after the announcement of the GA release of the Linux 4.7 kernel, the SparkyLinux developers inform their users that they can now test drive the new kernel from the unstable repository.
It looks like there's a whole lot of options for PDF viewers out there, so I'm hoping someone can offer a recommendation based on what I actually need.
I'm looking for four things basically: * Supports images * Can do text selection (and copying) * Can display multiple pages at once (continuous mode) * As fast as possible while satisfying the above three requirements. I'm going to be using this on limited hardware, so efficiency is more important than features. This is also the reason I don't just use one of the browser-integrated viewers.
I'm using evince right now, which is reasonably fast, but I don't like the way smooth scroll is implemented, and can't find a way to disable it.
Thanks!submitted by /u/Unknownloner
Hi folks, Im considering setting up wakeonlan for my ubuntu machine...there seems to be a few good guides and options out there for how to do it...but non of them cover this ......how do i send the command to wake on lan??? Is it possible to do this from a chromebook? (not running crouton)submitted by /u/danmoxon1
As I was fixing a README for the nth time, I got to thinking. I usually put in what I think is useful, but that's not necessarily what everyone else wants.
Based on hanging around here for a few years, here's what I've come up with:
- Name of the project (duh)
- Description of the project (also duh)
- Run time dependencies (questionable perhaps)
- Build time dependencies (also questionable)
- Up to date screenshots (if applicable)
- Build instructions
- Example usage
- Slim troubleshooting section
What I probably wouldn't put in:
- Package information (unless it's distro specific, such as an Arch install script or something)
- Extensive examples
What am I missing? What would/do you put in your READMEs?submitted by /u/cac2573