Language Selection

English French German Italian Portuguese Spanish

Linuxinsight

Syndicate content
LinuxInsight - aggregated feeds
Updated: 1 hour 19 min ago

Reddit: Is the Mate Terminal just a different name for ordinary Bash?

Saturday 23rd of December 2017 11:53:02 PM

Is that also the case with the terminals of other desktop environments?

Those who use terminals a lot, do you take the terminal into account when choosing your desktop environment?

submitted by /u/nextoy
[link] [comments]

TuxMachines: Automotive Grade Linux, Red Hat Earns Common Criteria Certification and More

Saturday 23rd of December 2017 11:50:26 PM

read more

TuxMachines: Software and howtos

Saturday 23rd of December 2017 11:49:09 PM

read more

TuxMachines: OSS Leftovers

Saturday 23rd of December 2017 11:45:45 PM
  • Coreboot Picks Up Support For Some Older ThinkPads

    Coreboot is now able to replace the proprietary BIOS on some older Lenovo ThinkPads.

    Coreboot has already offered pretty good coverage of older Intel-powered ThinkPads while two more models were added this week.

    The ThinkPad X131e is now supported by upstream Coreboot. This laptop shipped with SandyBridge and IvyBridge CPU options and under Coreboot most of the laptop should be working except for Fn keys and ACPI S4 hibernation and potentially wireless.

  • Apache Hadoop 3.0.0 Boosts Big Data App Ecosystem

    Fours years after Hadoop 2 became generally available, the open-source Big Data platform takes a giant step forward, with new capabilities to support containers.

    In the world of Big Data, one project has long loomed larger than all the rest - Hadoop. The open-source Apache Hadoop project provides the core framework on which dozens of other Big Data efforts rely.

    The Apache Hadoop v.3.0.0 milestone became generally available on Dec. 14, marking the first major version change for the project since Hadoop 2 debuted in 2013.

    "Hadoop 3 is a major milestone for the project, and our biggest release ever," Andrew Wang, Apache Hadoop 3 release manager stated.

  • LinuXatUNI held last meeting of the year

    The local Linux community in Lima, Peru held the last meeting today sharing a breakfast. Peruvians usually take “chocolatada” (made with chocolate and milk) with paneton for Christmass holidays, and we are not the exception.

  • Mitigating Cyber Security Risks Arising From Open Source Software

    A recent report indicated that Linux and other open source software (OSS) are emerging as serious malware targets. The report is a helpful reminder of the need to carefully consider the terms and conditions of OSS licenses and the resulting risks assumed by both software developers and end users in using OSS, including as it relates to cyber security. The increasing occurrence of cyber attacks should be a significant concern for most organizations. Understanding how OSS is licensed, and developing appropriate open source policies, is an important part of an organization's overall solution for managing cyber security risks.

  • Apple's open source machine learning software, smartphone microscopes, and more
  •  

  • The power of open source: Why GitLab’s move to a Developer Certificate of Origin benefits the developer community

    After being approached by Debian developers, GitLab decided to ditch the industry standard Contributor License Agreement in favor of adopting a license that is developer friendly — the Developer Certificate of Origin.

    We’re grateful to Debian for bringing their objection to the CLA to our attention, inspiring us to reconsider what we’re asking of our contributors. It’s now one of the reasons both Debian and GNOME plan to migrate their communities to GitLab. We want to be an option for everyone, and hopefully, this change is another step in that direction.

read more

LXer: Slackware-Based SlackEX Distro Released with Linux Kernel 4.14.8 and KDE 4.14.38

Saturday 23rd of December 2017 11:32:51 PM
GNU/Linux developer Arne Exton released today a new build of his Slackware-based SlackEX distro, bringing various updated applications and core components.

TuxMachines: Mesa 17.2.8 Released

Saturday 23rd of December 2017 11:28:52 PM
  • mesa 17.2.8

    Mesa 17.2.8 is now available.

    In this release we have:

    The SPIR-V compiler has seen corrected a possible SEGFAULT.

    The Intel i965 driver includes a correction for Haswell involving
    doubles management.

    The AMD drivers have also received some fixes. A couple have gone for
    radv and radeon's VCE while r600 has seen corrected some glitches
    detected with This War of Mine.

    Gallium has also received a patch fixing a problem affecting the VMware
    driver and the st/nine state tracker.

    The endianness detection in Windows platform has been corrected to
    default to little endian.

    Finally, the X11 driver has been improved to notify properly a mesa
    warning rather than using fprintf.

  • Mesa 17.2.8 Released With Just Over One Dozen Fixes

    For those still riding the older Mesa 17.2 series rather than the current Mesa 17.3 series that saw its v17.3.1 update this week, v17.2.8 is now available.

read more

TuxMachines: Mozilla Announces Firefox 60 as Next ESR (Extended Support Release) Branch

Saturday 23rd of December 2017 11:22:13 PM

Mozilla recently announced that the next ESR (Extended Support Release) branch of its open-source and cross-platform web browser would be Firefox 60, due for release next year in early May.

Since their initial launch, Firefox ESR releases have become more and more popular among various organizations that aim to offer customers a stable, long-term supported, and reliable browsing experience. Firefox ESR is known to be used in schools, universities, as well as small and medium-sized businesses.

The current Firefox ESR branch is based on Firefox 52, but it's nearing its end of life in six months, so Mozilla now plans to promote the upcoming Firefox 60 release to the ESR channel, along with a new policy engine that promises to make Firefox deployments and integration into existing infrastructures a lot simpler for sysadmins.

read more

Reddit: Top 10 Most Popular Linux Distributions of 2017

Saturday 23rd of December 2017 11:18:16 PM

TuxMachines: Slackware: SlackEX Gets a Lift, Slackware’s Plasma 5 Gets Upgrade

Saturday 23rd of December 2017 11:12:58 PM
  • SlackEX Build 171223 (Slackware 14.2) live dvd/usb with KDE 4.14.38, kernel 4.14.8-x86_64-efi-exton, Nvidia 384.98 and VirtualBox 5.2.4

    New features in version 171223 of SlackEX
    I have replaced kernel 4.12.9-x86_64-exton with kernel 4.14.8-x86_64-efi-exton with support for “everything”. Kernel 4.14.8 was released 171220. KDE is upgraded to version 4.14.38 (latest KDE version). All other component software is also upgraded to the latest Slackware Current version by now. I may also mention in particular GParted 0.29.0, VirtualBox 5.2.4 (latest, not in Slackware’s repositories), Google Chrome 60.0.3112 (not in Slackware’s repositories – you can download my build at SourceForge.net), Gimp 2.8.10 (installed from source), GSlapt 0.5.4b, Slackpkg 2.82.1, Firefox 57.0.2, Thunderbird 52.5.0, Samba 4.7.3 and GCC 7.2.0. Furthermore I have installed Grub2, which can be used as boot loader (if you want) after a hard drive install. Study the full package LIST. Note: I have replaced Wicd with NetworkManager. It works better in SlackEX.

  • Slackware-Based SlackEX Distro Released with Linux Kernel 4.14.8 and KDE 4.14.38

    GNU/Linux developer Arne Exton released today a new build of his Slackware-based SlackEX distro, bringing various updated applications and core components.

    The sole purpose of SlackEX is to make Slackware Linux more accessible to those who want to install a GNU/Linux distribution on their personal computers. SlackEX promises to be as easy to install and use like popular Linux Mint and Ubuntu distros.

    Based on Slackware 14.2, SlackEX Build 171223 is here with both the Slackpkg and GSlapt package management systems pre-installed to make installation of additional programs a breeze. It also includes developer's 4.14.8-x86_64-efi-exton kernel with extra hardware support.

    "Any novice can quickly learn to use Ubuntu they say. My remaster of Slackware Current (14.2), which I call SlackEX 14.2/Current 64-bit Linux Live DVD/USB, is however just as easy to use as Ubuntu and/or Linux Mint," said Arne Exton in the release announcement.

  • December packages for Slackware’s Plasma 5 – focus shift

    Jingle Bells galore! I have some goodies for you, right before Christmas. If your winter holiday starts today, there’s some nice new stuff to play with – especially if you have not dared touch slackware-current until now. Perhaps it’s time to free up a partition on your hard drive now?

    The KDE Applications 17.12 have been released by the KDE community. This set of KDE applications is completely free of the legacy KDE4 stuff (kdelibs4). The KDE developers have removed everything from their regular release cycles that is still based on kdelibs4 and/or unmaintained or broken anyway.

read more

Reddit: The Ken Thompson Hack

Saturday 23rd of December 2017 11:12:27 PM

TuxMachines: Give Your Linux Desktop a Festive Feel with these Xmas Tux Wallpapers

Saturday 23rd of December 2017 10:57:35 PM

Yup, you don’t need to turn to turn to Google to track down a badly GIMP’d xmas scene featuring a pasted pixelated tux.

Mark Riedesel, better known by the handle ‘Klowner’, creates a new Christmas Tux wallpaper each and every year – and has done so since 2004! His fully festive backdrops are made using a selection box of open-source graphics apps like Inkscape and Blender.

His latest design, sat atop of this post like a wobbly tree topper, is one of the best yet. It features Tux and a cat looking out over a christmassy tabletop village featuring festive looking penguins amid snow topped houses.

read more

TuxMachines: Best Xfce distro of 2017

Saturday 23rd of December 2017 10:53:33 PM

One more. After exploring the ups and downs of the Gnome and KDE/Plasma crop of this year, we now focus on what Xfce can deliver us. Arguably, this is the third largest, most important desktop environment in the open-source universe, straddling the chasm between the two opposing philosophies of the G and K worlds.

Back in 2016, I found Xfce to be a very vibrant, healthy, innovative technology, with a good string of successes, and a range of balanced, practical distributions. There were no cardinal revolutions, but then also, there were no wild swings in quality, either. It was all rather stolid. Now, let’s see what 2017 can tell us.

read more

Slashdot: Updated Debian Linux 9.3 and 8.10 Released

Saturday 23rd of December 2017 10:26:40 PM

Slashdot: Linux Pioneer Munich Confirms Switch To Windows 10

Saturday 23rd of December 2017 10:26:40 PM

Reddit: TARTARUS gets a native release on Steam

Saturday 23rd of December 2017 08:46:52 PM

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30