xmodulo: System administrators (sysadmins) are responsible for day-to-day operations of production systems and services.
According to IDC, the total combined market share of Android and iOS swelled to 96.4 percent during the second quarter, up from 92.6 percent a year ago. That left just 2.5 percent of the market to Windows Phone, down from 3.4 percent in a year’s time.
In part, that’s because the worldwide smartphone market swelled to 301.3 million phones, moving past 300 million phones for the first time in its history, according to IDC. That represents 25.3 percent growth from a year ago.
LinuxGizmos: A non-profit company is developing an open source, 64-bit "lowRISC" SoC that will enable fully open hardware, "from the CPU core to the development board
Today Recently in Linux news, Jack Wallen asks, "Will Linux ever be able to give consumers what they want?" Mark Gibbs relates his experience installing Ubuntu on an older netbook. Linux.com has a complete beginner's guide to Linux and Rob Zwetsloot looks at four popular download managers. And finally, Reiser4 has made a comeback and systemd is wreaking havoc again for some.
GCC 4.10 has been under development since the 4.9.0 release near the beginning of the year. However, at the GNU Tools Cauldron it was agreed upon that GCC 4.10 will most likely become GCC 5.0 upon its release in 2015. The GCC version scheme is also being shaken up for future releases. Years ago there was talk of GCC 5.0 being modular and more like LLVM but to date there's no "killer features" of GCC 5.0 at this point in its SVN code-base.
Reddit: Unaccountable 4 byte file size difference in files copied over NFS, also "Failed to preserve ownership" with 'cp -av'.
It's basically in the title. We have an autofs mounted NFS share. "Auto.share". I'm coping files from one server's export directory to the automounted directory. Every file is "cp: failed to preserve ownership for ...: Operation not permitted.
Then the file is copied over, it's owned by nfsnobody:nfsnobody.
BOTH servers authenticate through NIS, so users should be the same. Ownerhship should be preserved.
On the receiving server, the /etc/exports line for the relevant share is just (rw,sync).
Lastly as far as that goes, one example directory is 755 in its original location, but when copied becomes 700.
But if I can't solve the permissions/ownership, there's still the issue that files copied over lose 4 bytes. Not all, but many.
Looking in a single directory there's like a 112 byte difference total. And there's a pattern. It's a directory that holds data output. And the format is several .bin files. Like 8 or 9 per step. So like
A123.bin A124.bin A125.bin B123.bin B124.bin B125.bin C123.bin etc.
It's like every N125.bin that's missing 4 bytes when transferred. That's clearly a pattern, but it makes no sense.
I needed no_root_squash in the /etc/exports file for the receiving server. Added that, ran exportfs -r. Worked like a charm. Still don't know about the file size difference. When the copy is complete I'll check again.submitted by Sysa_Dmin
[link] [10 comments]
After a series of torture tests, I have decided the Brigadier is like the Terminator of smartphones. It looks durable and virtually indestructible. But what's a smartphone if you can't use it? I put it through one final test to see if it could still make calls.
The Brigadier is heavy -- weighing in at 6.6 ounces. It runs on Android 4.4 KitKat -- however it remained unclear what the future holds for operating system updates.
Turning your Raspberry Pi into a mobile phone is a lot simpler than you’d think, albeit a little chunky. Linux User talks to Dave Hunt about one of his many pet projects.
softpedia: elementary OS Freya Beta has been announced by its developers and it comes with an Ubuntu 14.04 base and lots of new features.
While it is possible to run X applications in a weston session by loading the xwayland.so module, this setup has weston manage the X client windows using its own built-in window manager. This makes it impossible to use X display managers (like GDM, LightDM, etc.) and window managers (like i3, OpenBox, Ratpoison, etc.) with weston.
Xweston approaches things the other way round: it launches Xwayland with an otherwise empty weston session, which should allow one to use it like any other X server. In particular, one can launch it using startx or using an X display manager (tested with LightDM).
Note that Xweston is still very experimental, it probably breaks every rule in the Wayland and weston books, and it may decide to have all your child processes for breakfast. But hey, it's open source (GPL) and on Github, so instead of dissing it, try developing it instead :)submitted by miki4242
[link] [2 comments]