Open data can play a crucial role in helping us navigate such mazes. In the world of business, the key store of open information is OpenCorporates, which I've written about several times. But OpenCorporates is just the start; what's really exciting is the way that people are starting to use its growing resources to investigate companies and their industries. A particularly good example of this is a project called OpenOil
I opened a link from the linux subreddit today. I meant to bookmark it, but forgot. I don't know how to search for it. The title of it was something like "Learn enough about linux to attract employers" or something like that.
Thanks for any help!submitted by TheRealDonahue
[link] [1 comment]
Hi, Rob from Linux User & Developer magazine here.
We're just trying to get an informal feel for what you guys like in the kind of discs you get in Linux mags. We have one ourselves with packages, (some) live-booting distros, tutorial files, etc, and we're wondering if we could focus on any one thing or make any changes to make it better.
Don't read our mag? We'd still like to hear what you say.submitted by robthez
[link] [8 comments]
The UK economy is growing at its fastest rate since 2007, according to the Office of National Statistics, and the financial services sector is playing a major role in supporting this recovery. Renewed confidence in the City is driving up demand for effective IT. However, mirroring austerity measures put in place to help get national economies back on track, most (if not all) banks these days have cost reduction programmes in place.
So, I managed to get everything setup xRDP to call x11vnc and direct traffic to a local port.
However I cannot seem to understand how to get the next step of integrating SSH into this process.
Xrdp listens on 3389 - I intend to work on that next. Xrdp passes the session locally to X11vnc which shares the existing desktop.
Can someone point me to the right material to get to the next step of integrating SSH into this step.. and if you know of a resource to get me started to moving xRDP to another port that would be awesome too. (I told it to listen to another and it does.. but its listening still on 3389 not sure what thats about..)submitted by I_DOWNVOTE_STUPID
[link] [1 comment]
Finland’s Jolla Takes Its Sailfish-Powered Smartphone To India, Via Snapdeal.
Jolla, the Finnish smartphone startup that used the MeeGo open source OS as a jumping off point for its own Android-app compatible Sailfish OS — and which last November released its first Sailfish-powered handset in its home market — has now expanded availability of the phone to India.
Jolla’s handset is priced at Rs. 16,499 in India (around $270), and is selling exclusively via local ecommerce giant Snapdeal.
While Fedora 21 is being dragged out agonizingly long for day-to-day Fedora users, the alpha release is out today and it's great and comes with many new features. Having not run Fedora Rawhide in several weeks now as the latest development code, Fedora 21 is turning out fairly nicely and with my early morning tests thus far the Fedora 21 Alpha release is stable and running quite nicely.
Long story short, in the case mentioned above, the SiS driver works much better than the generic xf86-video-vesa and xf86-video-fbdev generic drivers and now this user running their aging system on the latest Fedora Linux development code is left without the dedicated DDX. In that case, the user discovered that Mageia's SiS DDX driver that's packaged happens to be ABI compatible with the Fedora X Server (at least temporarily), so he's back to using his preferred driver without burdening the Fedora developers in supporting an out-of-date, open-source GPU driver.
While Linux is commonly referred to as being able to run on almost anything, especially aging PCs, more Linux developers are realizing the burden in trying to maintain support and compatibility for older hardware; in some cases there's just regressions while in other instances the latest code can be completely broken for months until a user notices. What's your views on Linux maintaining support for old hardware? Let us know in the forums.
For Apple, the launch of iPhone 6 and the iPhone 6 Plus is a big deal. Literally. The iPhones were starting to look tiny in front of flagship Android phones. But with the iPhone 6 and the iPhone 6 Plus, which have bigger screens, Apple is back in the game.
On the software side, with the iOS 8, which is the latest version of the software that powers iPhones and iPads, Apple has tried to close the feature gap with Android.
The four freedoms are only meaningful if they result in real-world benefits to the entire population, not a privileged minority. If your approach to releasing free software is merely to ensure that it has an approved license and throw it over the wall, you're doing it wrong. We need to design software from the ground up in such a way that those freedoms provide immediate and real benefits to our users. Anything else is a failure.
Matthew was pessimistic about the prospects of ACPI for ARM. Matthew explained that now Linux (Android) is the dominant platform on ARM rather than Microsoft Windows, we could run into problems, "Software development is hard, and firmware development is software development with worse compilers. Firmware is inevitably going to rely on undefined behaviour. It's going to make assumptions about ordering. It's going to mishandle some cases. And it's the operating system's job to handle that. On x86 we know that systems are tested against Windows, and so we simply implement that behaviour. On ARM, we don't have that convenient reference. We are the reference. And that means that systems will end up accidentally depending on Linux-specific behaviour. Which means that if we ever change that behaviour, those systems will break. So far we've resisted calls for Linux to provide a contract to the firmware in the way that Windows does, simply because there's been no need to - we can just implement the same contract as Windows. How are we going to manage this on ARM? The worst case scenario is that a system is tested against, say, Linux 3.19 and works fine. We make a change in 3.21 that breaks this system, but nobody notices at the time. Another system is tested against 3.21 and works fine. A few months later somebody finally notices that 3.21 broke their system and the change gets reverted, but oh no! Reverting it breaks the other system. What do we do now? The systems aren't telling us which behaviour they expect, so we're left with the prospect of adding machine-specific quirks. This isn't scalable."