- Latest Headlines
- Recent comments
- All-Time Popular Stories
- Hot Topics
- Latest Members
|Story||Android 7.0 Nougat||Roy Schestowitz||24/08/2016 - 11:53pm|
|Story||Leftovers: OSS and Sharing||Roy Schestowitz||24/08/2016 - 11:53pm|
|Story||FOSS in Government||Roy Schestowitz||24/08/2016 - 11:51pm|
|Story||Open/Hacker Hardware||Roy Schestowitz||24/08/2016 - 11:50pm|
|Story||Security Leftovers||Roy Schestowitz||24/08/2016 - 11:49pm|
|Story||Liberating PCs and "Mac"-branded PCs||Roy Schestowitz||24/08/2016 - 10:23pm|
|Story||Games for GNU/Linux||Roy Schestowitz||24/08/2016 - 10:20pm|
|Story||LinuxCon and Linux at 25||Roy Schestowitz||24/08/2016 - 10:09pm|
|Story||GNOME News||Roy Schestowitz||24/08/2016 - 9:33pm|
|Story||KDE Leftovers||Roy Schestowitz||24/08/2016 - 9:32pm|
Most people have at least heard of the term “open source” but the wide popularity of open source has been in software rather than hardware. Open source software is well known. Home computer users recognize it in downloads like Office Libre, GIMP, and the VLC media player. More serious computer users realize that much of the Internet itself was built on open source technologies like Linux and the Apache Web Server. Open source software can quickly be defined as source code that anyone can inspect, modify, and enhance.
In the photos of the laptop that David exposed and is keeping functional, the complexity of the design is clearly apparent. Huge heat sinks and heat pipes, a densely populated and really quite large PCB on both sides (which is costly to manufacture). Chances of repair and ongoing maintenance: absolutely zero. The only reason that David is even considering keeping this machine going is down to years of experience with computers - something that most people simply do not have time to do.
By contrast, the EOMA68 Laptop Housing is kept to a bare minimum out of pure necessity: it’s a simpler design that’s been made using tools that the average electronics engineer could conceivably imagine owning… so that they can make or repair these devices, for themselves, or for other people.
The main PCB (PCB1) is only 6” square with a small extension for the USB ports, and is approximately only 30% populated with components, only on one side. PCB2 (for the keyboard and mouse) is very small and has around 30 components on it, and PCB3 likewise. Here are some pictures taken last year: the first shows the 3 PCBs wired together and assembled in the 3D-printed case, whilst the second is a partially-populated PCB (USB2 connectors in the top left corner to give an idea of scale).
I’m glad to announce the second release of eiffel-iup. A wrapper that allow create graphical applications with Liberty Eiffel using the IUP toolkit. This second version add flat buttons and fix some errors. The main changes are in the names of some features, which now have names in the eiffel style. This is enough mature to create graphical interfaces. The package contains examples that show how use eiiffel-iup. So let me know if you have problems and Happy hacking!
I've been supporting student participation in humanitarian free and open source software (HFOSS) projects for over a decade. I've seen students get motivated and excited by working in a professional community while they learn and mature professionally. Out of the many reasons for supporting student participation in open source, here are five of the most compelling reasons.
After last weeks somewhat unusual patch statistics (only 1/6th
drivers), we're not back to the normal programming with rc3, and we
have the usual situation with roughly ~60% of the patch being driver
updates. It's spread out, but most of it tends to be networking, GPU,
USB and a new EDAC driver. But all of it is fairly small.
Outside of the driver department, we've got core networking, some
filesystem updates (mainly xfs, although in the diffstat afs shows up
too, but that's really from the networking changes) and a smattering
of updates all over: documentation, scheduler, some miinor arch
Continuing off from the fresh open-source AMDGPU test data from yesterday's AMDGPU-PRO vs. open-source Polaris + Fiji comparison, here are more AMD graphics cards tested from the Linux 4.8 development code paired with Mesa 12.1 Git.
The GPUs tested for this weekend benchmarking fun were the Radeon HD 6870. HD 7950. R7 260X. R9 270X, R9 285, R7 370, R9 Fury, RX 460, RX 470, and RX 480. All tests happened from Mesa 12.1-dev via the Padoka PPA this week on Ubuntu 16.04 LTS paired with the Linux 4.8 kernel from 18 August. Note that with Mesa Git on pre-GCN GPUs there is only OpenGL 4.4 support for the Radeon HD 5800/6900 series while all other cards such as the HD 6870 are still currently bound to OpenGL 3.3 due to lacking FP64 emulation support.
It is early days yet for bus1. Though it has been under development for a least eight months (based on Git history) and is based on even older ideas, there has been little public discussion. The follow-up comments on the kernel-summit email thread primarily involved people indicating their interest rather than commenting on the design. From my limited perspective, though, it is looking positive. The quality of the code and documentation is excellent. The design takes the best of binder, which is a practical success as a core part of the Android platform, and improves on it. And the development team appears to be motivated towards healthy informed community discussion prior to any acceptance. The tea-leaves tell me there are good things in store for bus1.
Open Source usage and participation has increased across the industry in the last few years, driving the spotlight towards the technology powering the future of open collaboration. Similarly, with the rise of software defined networking (SDN) and network function virtualization (NFV), networking is going through its own star studded moment. As an early pioneer in the SDN space, Open vSwitch has been at the forefront of both of these trends, and has helped pioneer not only the concepts we all understand as SDN, but in the open cloud platform as well. Open vSwitch enables developers to easily connect and move between separate cloud environments. We at IBM have contributed heavily to Open vSwitch as part of our dedication to building the cloud as an open, accessible foundation for innovation – not a destination in and of itself.
Kernel 4.4.19 has been released, bringing an impressive number of fixes.
The GNU Guix package-manager project recently released version 0.11, bringing with it support for several hundred new packages, a range of new tools, and some significant progress toward making an entire operating system (OS) installable using reproducible builds.
Guix is a "functional" package manager, built on many of the same ideas found in the Nix package manager. As the Nix site explains it, the functional paradigm means that packages are treated like values in a functional programming language—Haskell in Nix's case, Scheme in Guix's. The functions that build and install packages do so without side effects, so the system can easily offer nice features like atomic transactions, rollbacks, and the ability for individual users to build and install separate copies of a package without fear that they will interfere. Part of making such a system reliable is to ensure that builds are "reproducible"—meaning that two corresponding copies of a binary built on different systems at different times will be bit-for-bit identical.
To say the VeraCrypt audit, which begins today, got off to an inauspicious start would be an understatement.
On Sunday, two weeks after the announcement that the open source file and disk encryption software would be formally scrutinized for security vulnerabilities, executives at one of the firms funding the audit posted a notice that four emails between the parties involved had been intercepted.
Most coverage of the subject has been written in that panicky, alarmist prose that makes for exciting news, but the problem is that the invalidation of Secure Boot is a very positive development for everyone concerned, except for Microsoft. Yes, it shows why backdoors for “the good guys” are a terrible idea — yes, it even has far-reaching implications for every piece of computing technology using the UEFI standard. However, I maintain that it will have a positive influence on the direction of security and tech standards moving forward.
Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be released in about two weeks.
This is a last chance to modify new features in a way that is not backwards compatible. Once 8.0 is out we can’t make changes that would break plugins.
digiKam is digital photo management application for specially designed for KDE desktop environment. Digital photo management program designed to import, organize, enhance, search and export your digital images to and from your computer. It provides a simple interface which makes importing and organizing digital photographs a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam enables you to manage large numbers of digital photographs in albums and to organize these photographs for easy retrieval using tags (keywords), captions, collections, dates, geolocation and searches. It has many features for viewing, organizing, processing and sharing your images. Thus, digiKam is a formidable digital asset management (DAM) software including powerful image editing functions. An easy-to-use camera interface is provided, that will connect to your digital camera and download photographs directly into digiKam albums. More than 1000 digital cameras are supported by the gphoto2 library. Of course, any media or card reader supported by your operating system will interface with digiKam.
The newest tool for observing the Linux operating system is the “Berkeley Packet Filter” (BPF). BPF allows users to run a small piece of code quickly and safely inside the operating system. Originally used for packet filtering, it has since been enhanced from its eponymous use-case to support dynamic tracing of the Linux operating system. For example, it is possible to write a small BPF program that prints every time a particular file was accessed by a user.
Open source software is widely used today. While there is not a single development method for open source, many successful open source projects are based on widely distributed development models with many independent contributors working together. Traditionally, distributed software development has often been seen as inefficient due to the high level of communication and coordination required during the software development process. Open source has clearly shown that successful software can be developed in a distributed manner.
The open source community has over time introduced many collaboration systems, such as version control systems and mailing lists, and processes that foster this collaborative development style and improve coordination. In addition to implementing efficient collaboration systems and processes, it has been argued that open source development works because it aims to reduce the level of coordination needed. This is because development is done in parallel streams by independent contributors who work on self-selected tasks. Contributors can work independently and coordination is only required to integrate their work with others.
Relatively little attention has been paid to release management in open source projects in the literature. Release management, which involves the planning and coordination of software releases and the overall management of releases throughout the life cycle, can be studied from many different aspects. I investigated release management as part of my PhD from the point of view of coordination theory. If open source works so well because of various mechanism to reduce the level of coordination required, what implications does this have on release management which is a time in the development process when everyone needs to come together to align their work?