Jump to content

Search the Community

Showing results for tags 'linux'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 438 results

  1. The real Linus Torvalds stands up. Linux frontman Linus Torvalds thinks he's "more self-aware" these days and is "trying to be less forceful" after his brief absence from directing Linux kernel developers because of his abusive language on the Linux kernel mailing list. But true to his word, he's still not necessarily diplomatic in his communications with maintainers. Torvalds' post-hiatus outburst was directed at Dave Chinner, an Australian programmer who maintains the Silicon Graphics (SGI)-created XFS file system supported by many Linux distros. "Bullshit, Dave," Torvalds told Chinner on a mailing list. The comment from Chinner that triggered Torvalds' rebuke was that "the page cache is still far, far slower than direct IO" – a problem Chinner thinks will become more apparent with the arrival of the newish storage-motherboard interface specification known as Peripheral Express Interconnect Express (PCIe) version 4.0. Chinner believes page cache might be necessary to support disk-based storage, but that it has a performance cost. "That said, the page cache is still far, far slower than direct IO, and the gap is just getting wider and wider as nvme SSDs get faster and faster. PCIe 4 SSDs are just going to make this even more obvious – it's getting to the point where the only reason for having a page cache is to support mmap() and cheap systems with spinning rust storage," wrote Chinner. But the Finnish-born Linux creator essentially told the Australian not to come the raw prawn. "You've made that claim before, and it's been complete bullshit before too, and I've called you out on it then too," wrote Torvalds. "Why do you continue to make this obviously garbage argument?" According to Torvalds, the page cache serves its correct purpose as a cache. "The key word in the 'page cache' name is 'cache'," wrote Torvalds. Chinner had been debating the role of the page cache in an open email thread, commenting that "the page cache simply isn't designed to allow atomic range operations to be performed" and that he and fellow developers haven't been able "to drag it out of the 1980s". "We wrote the fs/iomap.c code so we could do range-based extent mapping for IOs rather than the horrible, inefficient page-by-page block mapping the generic page cache code does – that gave us a 30+ percent increase in buffered IO throughput because we only do a single mapping lookup per IO rather than one per page…," wrote Chinner. Torvalds didn't buy the argument and said anyone peddling this idea was "incompetent". "Caches work, Dave. Anybody who thinks caches don't work is incompetent. 99 percent of all filesystem accesses are cached, and they never do any IO at all, and the page cache handles them beautifully," Torvalds wrote. "When you say the page cache is slower than direct IO, it's because you don't even see or care about the *fast* case. You only get involved once there is actual IO to be done." Chinner, in response to Torvalds comment that "caches work, Dave", reminded the Linux kingpin about his commitment to "civil discussion" and attempting to create a professional environment for kernel developers: "Yes, they do," replied Chinner. "I see plenty of cases where the page cache works just fine because it is still faster than most storage. But that's not what I said." Chinner said Torvalds hadn't even bothered to ask him to clarify what he was referring to in the statement Torvalds quoted. "You've taken one single statement I made from a huge email about complexities in dealing with IO concurrency, the page cache and architectural flaws in the existing code, quoted it out of context, fabricated a completely new context and started ranting about how I know nothing about how caches or the page cache work," Chinner said. "Not very professional but, unfortunately, an entirely predictable and expected response. Linus, nobody can talk about direct IO without you screaming and tossing all your toys out of the crib. If you can't be civil or you find yourself writing a some condescending 'caching 101' explanation to someone who has spent the last 15+ years working with filesystems and caches, then you're far better off not saying anything." Source
  2. Ubuntu Linux Gets Intel MDS Mitigations for Intel Sandy Bridge CPUs, Update Now Canonical released another update for the intel-microcode firmware for all supported Ubuntu Linux operating systems to address recent Intel MDS (Microarchitectural Data Sampling) security vulnerabilities. Last month on May 14th, Intel published details about four new security vulnerabilities affecting several of its Intel microprocessor families. The company released updated microcode firmware to mitigate these hardware flaws, which quickly landed in the software repositories of all supported Ubuntureleases, but only some of the processor families were supported. Last week, intel-microcode firmware updates arrived in Ubuntu's repositories to mitigate these new security vulnerabilities on systems using Intel Cherry Trail and Intel Bay Trail processor families, and now Canonical released another update to fix the hardware flaws on the Intel Sandy Bridge processor family, for all supported Ubuntu releases. "USN-3977-1 and USN-3977-2 provided mitigations for Microarchitectural Data Sampling (MDS) vulnerabilities in Intel Microcode for a large number of Intel processor families. This update provides the corresponding updated microcode mitigations for the Intel Sandy Bridge processor family," reads the new security advisory.How to protect your Ubuntu computers agains the Intel MDS vulnerabilitiesIf you're using Ubuntu 19.04 (Disco Dingo), Ubuntu 18.10 (Cosmic Cuttlefish), Ubuntu 18.04 LTS (Bionic Beaver), Ubuntu 16.04 LTS (Xenial Xerus), or Ubuntu 14.04 ESM (Trusty Tahr) on a computer running one of the affected Intel CPUs, you should update the intel-microcode firmware right now to version 3.20190618.0, which you can download from the official software repositories. The new intel-microcode versions available are 3.20190618.0ubuntu0.19.04.1 for Ubuntu 19.04, 3.20190618.0ubuntu0.18.10.1 for Ubuntu 18.10, 3.20190618.0ubuntu0.18.04.1 for Ubuntu 18.04 LTS, 3.20190618.0ubuntu0.16.04.1 for Ubuntu 16.04 LTS, and 3.20190618.0ubuntu0.14.04.1 for Ubuntu 14.04 ESM. To update your system, follow the instructions provided by Canonical at https://wiki.ubuntu.com/Security/Upgrades. Also, make sure you also have the latest Linux kernel for your Ubuntu Linux release installed to fully mitigate these new security vulnerabilities. Source
  3. CentOS 7 and RHEL 7 Get Important Linux Kernel Update to Patch SACK Panic Flaws The Red Hat Enterprise Linux and CentOS Linux operating systems have received new Linux kernel security updates that are marked as important and address the recently disclosed TCP vulnerabilities affecting all GNU/Linux distributions. The new Linux kernel security updates patch an integer overflow flaw (CVE-2019-11477) discovered by Jonathan Looney in Linux kernel's networking subsystem processed TCP Selective Acknowledgment (SACK) segments, which could allow a remote attacker to cause a so-called SACK Panic attack (denial of service) by sending malicious sequences of SACK segments on a TCP connection that has a small TCP MSS value. "While processing SACK segments, the Linux kernel's socket buffer (SKB) data structure becomes fragmented," reads Red Hat's security advisory. "Each fragment is about TCP maximum segment size (MSS) bytes. To efficiently process SACK blocks, the Linux kernel merges multiple fragmented SKBs into one, potentially overflowing the variable holding the number of segments." Furthermore, the Linux kernel security update also fixes two other similar issues (CVE-2019-11478 and CVE-2019-11479), both discovered by Jonathan Looney in Linux kernel's TCP retransmission queue implementation, which could allow a remote attacker to cause a denial of service that may lead to excessive resource consumption and a system crash.Users are urged to update their systems immediatelyIn addition to the three SACK Panic security vulnerabilities mentioned above, the Linux kernel security update released for Red Hat Enterprise Linux 6 and CentOS Linux 6 operating system series also adds the Intel MDS mitigations for Intel Skylake CPUs and a missing md_clear flag in /proc/cpuinfo, ensures the Linux kernel now disables SMT with the mds=full,nosmt parameter, and fixes a double free issue in lib/idr.c. All users of the Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6, CentOS Linux 7, and CentOS Linux 6 operating system series are urged to update their systems as soon as possible. The new Linux kernel security updates are available for all supported variants of these operating systems on 64-bit, 32-bit, IBM z Systems (s390x), PowerPC 64-bit Big Endian (ppc64), and PowerPC 64-bit Little Endian (ppc64le) architectures. Source
  4. One of the biggest disadvantages of using pirated software is the increased risk of letting your computer get infected with malware. Cybercriminals often bundle the cracked versions of paid software on piracy websites with adware and cryptominer to earn free cash. So, if you’re installing such programs from unknown sources, the chances of you getting hacked are pretty good. The same attack vector is being used by hackers to distribute a new Mac cryptocurrency miner named Bird Miner. As Malwarebytes’ official blog explains, Bird Miner has been found to be bundled with a cracked installer of a software named Ableton Live, which is a tool for high-end music production. Malwarebytes found that Ableton Live 10’s cracked 2.6 GB installer is available on piracy website VST Crack. Security researchers from the firm became suspicious when they found that Bird Miner’s post installation script was busy copying installed files to new locations with random names. The new files with random names seem to have various functions, including the role of launch daemons. One such daemon launches a shell script called Crax, which makes sure that the malware is hidden from the security researchers. The malware further checks to see if your Mac’s CPU is operating at more than 85 percent load to avoid running the cryptomining script in this case. Bird Miner uses Tiny Core Linux emulation The last piece of the puzzle is the launch of an executable named Nigel, which is an old version of an open source emulator named Qemu. For those who don’t know, Qemu is a terminal-only virtualization software that lets one run Linux packages on non-Linux machines. The Qemu emulator further uses a file named Poaceae, which is a bootable Tiny Core Linux image. Finally, as soon as the Tiny Core system boots up, the xmrig miner starts running to mine the Monero cryptocurrency. The Malwarebytes researchers mention that familiarity with Linux could be the reason why creators of the malware chose the Linux route. This malware further shows why using pirated software increases the chances of getting infected very easily. Source
  5. Canonical Outs New Linux Kernel Live Patch for Ubuntu 18.04 LTS and 16.04 LTS Canonical released a new Linux kernel live patch for the Ubuntu 18.04 LTS (Bionic Beaver) and Ubuntu 16.04 LTS (Xenial Xerus) operating system series to address the recently disclosed TCP Denial of Service (DoS) vulnerabilities. Coming hot on the heels of the recent Linux kernel security updatespublished earlier this week for all supported Ubuntu releases, the new Linux kernel live patch is only targeted at Ubuntu versions that support the kernel live patch and are long-term supported, including Ubuntu 18.04 LTS (Bionic Beaver) and Ubuntu 16.04 LTS (Xenial Xerus). And it's here to address the same two security vulnerabilities (CVE-2019-11477 and CVE-2019-11478) discovered by Jonathan Looney in Linux kernel's TCP retransmission queue implementation when handling TCP Selective Acknowledgments (SACKs), which could allow a remote attacker to crash the system by causing a denial of service (resource exhaustion). The CVE-2019-11477 flaw is also known as SACK Panic.Users are urged to update their systems immediatelyCanonical urges all users of the Ubuntu 18.04 LTS (Bionic Beaver) and Ubuntu 16.04 LTS (Xenial Xerus) operating system series who use the Linux kernel live patch to update their installations as soon as possible to the new kernel versions. These are rebootless kernel updates, so you won't need to restart your computer to apply them. The new live kernel versions are 4.15.0-51.55 for Ubuntu 18.04.2 LTS systems with the HWE stack from Ubuntu 18.10, 4.15.0-51.55~16.04.1for Ubuntu 16.04.6 LTS systems with the HWE stack from Ubuntu 18.04.2 LTS, and 4.4.0-150.176 for Ubuntu 16.04 LTS systems. Check out Canonical's Livepatch Service website for details on how to use the kernel live patch. Source
  6. BRUSSELS (Reuters) - U.S. tech giant International Business Machines Corp is set to secure unconditional EU approval for its $34 billion bid for software company Red Hat, people familiar with the matter said on Wednesday. IBM is seeking to expand its subscription-based software offerings via the deal, its biggest to date, to counter slowing software sales and waning demand for mainframe servers. It would also help it catch up with Amazon, Alphabet Inc and Microsoft in the fast growing cloud computing business. The European Commission, which is scheduled to decide on the deal by June 27, and IBM declined to comment. Founded in 1993, Red Hat specializes in Linux operating systems, the most popular type of open-source software and an alternative to proprietary software made by Microsoft. U.S. regulatory authorities gave the green light to the deal last month without demanding concessions. Source
  7. One of the jobs of the Linux kernel—and all operating system kernels—is to manage the resources available to the system. When those resources get used up, what should it do? If the resource is RAM, there's not much choice. It's not feasible to take over the behavior of any piece of user software, understand what that software does, and make it more memory-efficient. Instead, the kernel has very little choice but to try to identify the software that is most responsible for using up the system's RAM and kill that process. The official kernel does this with its OOM (out-of-memory) killer. But, Linux descendants like Android want a little more—they want to perform a similar form of garbage collection, but while the system is still fully responsive. They want a low-memory killer that doesn't wait until the last possible moment to terminate an app. The unspoken assumption is that phone apps are not so likely to run crucial systems like heart-lung machines or nuclear fusion reactors, so one running process (more or less) doesn't really matter on an Android machine. A low-memory killer did exist in the Linux source tree until recently. It was removed, partly because of the overlap with the existing OOM code, and partly because the same functionality could be provided by a userspace process. And, one element of Linux kernel development is that if something can be done just as well in userspace, it should be done there. Sultan Alsawaf recently threw open his window, thrust his head out, and shouted, "I'm mad as hell, and I'm not gonna take this anymore!" And, he re-implemented a low-memory killer for the Android kernel. He felt the userspace version was terrible and needed to be ditched. Among other things, he said, it killed too many processes and was too slow. He felt that the technical justification of migrating to the userspace dæmon had not been made clear, and an in-kernel solution was really the way to go. In Sultan's implementation, the algorithm was simple—if a memory request failed, then the process was killed—no fuss, no muss and no rough stuff. There was a unified wall of opposition to this patch. So much so that it became clear that Sultan's main purpose was not to submit the patch successfully, but to light a fire under the asses of the people maintaining the userspace version, in hopes that they might implement some of the improvements he wanted. Michal Hocko articulated his opposition to Sultan's patch very clearly—the Linux kernel would not have two separate OOM killers sitting side by side. The proper OOM killer would be implemented as well as could be, and any low-memory killers and other memory finaglers would have to exist in userspace for particular projects like Android. Suren Baghdasaryan also was certain that multiple OOM killers in the kernel source tree would be a non-starter. He invited Sultan to approach the problem from the standpoint of improving the user-space low-memory killer instead. There also were technical problems with Sultan's code. Michal felt it didn't have a broad enough scope and was really good only for a single very specific use case. And, Joel Fernandes agreed that Sultan's approach was too simple. Joel pointed out that "a transient temporary memory spike should not be a signal to kill _any_ process. The reaction to kill shouldn't be so spontaneous that unwanted tasks are killed because the system went into panic mode." Instead, he said, memory usage statistics needed to be averaged out so that a proper judgment of which process to kill could be made. So, the userspace version was indeed slow, but the slowness was by design, so the code could make subtle judgments about how to proceed. But Suren, on the other hand, agreed that the userspace code could be faster, and that the developers were working on ways to speed it up. In this way, the discussion gradually transitioned to addressing the deficiencies in the userspace implementation and finding ways to address them. To that extent, Sultan's code provided a benchmark for where the user code would like to be at some point in the future. It's not unheard of for a developer to implement a whole feature, just to make the point that an existing feature gets it wrong. And in this case, it does seem like that point has been heard. Source
  8. A denial of service flaw found in the way recent Linux and FreeBSD kernels handle TCP networking can be exploited by remote attackers to trigger a kernel panic in vulnerable systems. In all, Netflix Information Security's Jonathan Looney found three vulnerabilities, two related to "the minimum segment size (MSS) and TCP Selective Acknowledgement (SACK) capabilities," and one related only to MSS, with the most serious one named SACK Panic being the one that can cause affected systems to panic and reboot. As per Red Hat, the issues which impact the kernel's TCP processing subsystem are tracked via multiple CVEs, with CVE-2019-11477 SACK Panic having been assigned an important severity with a 7.5 CVSS3 base score, while CVE-2019-11478 and CVE-2019-11479 are considered to be moderate severity vulnerabilities. Patches are already available as detailed in Netflix's NFLX-2019-001 security advisory, with mitigation measures also being available for machines where patching is not an immediate or easy option. The SACK Panic security flaw The SACK Panic vulnerability (Debian, Red Hat, Ubuntu, Suse, AWS) impacts Linux kernels 2.6.29 and later, and it can be exploited by "sending a crafted sequence of SACK segments on a TCP connection with small value of TCP MSS" which will trigger an integer overflow. To fix the issue, "Apply the patch PATCH_net_1_4.patch. Additionally, versions of the Linux kernel up to, and including, 4.14 require a second patch PATCH_net_1a.patch," says Netflix Information Security's advisory. To mitigate the issue, users and administrator can completely disable SACK processing on the system or block connections with a low MSS using the filters provided by Netflix Information Security HERE — the second mitigation measure will only be effective when TCP probing is also disabled. More denial of service vulnerabilies The other two vulnerabilities impact all Linux versions, with CVE-2019-11478 being exploitable by sending "a crafted sequence of SACKs which will fragment the TCP retransmission queue," while CVE-2019-11479 allows attackers to trigger a DoS state by sending "crafted packets with low MSS values to trigger excessive resource consumption." Linux and FreeBSD admins and users can fix the first one can by applying PATCH_net_2_4.patch, and the second one with the PATCH_net_3_4.patch and PATCH_net_4_4.patch security patches. As workarounds, both CVE-2019-11478 and CVE-2019-11479 can be mitigated by blocking remote network connections with a low MSS with Netflix Information Security-supplied filters available HERE — applying the filters might subsequently break low MMS legitimate connections. "The extent of impact is understood to be limited to denial of service at this time. No privilege escalation or information leak is currently suspected," says Red Hat. "Good system and application coding and configuration practices (limiting write buffers to the necessary level, monitoring connection memory consumption via SO_MEMINFO, and aggressively closing misbehaving connections) can help to limit the impact of attacks against these kinds of vulnerabilities," also notes Netflix Information Security in its advisory. Source
  9. brolly

    Any Linux Users Here?

    Hi guys I know there are lot of windows users in this forum. Are there any Linux users around. I use a linux distro as a host machine and i run windows in guest machines. It would be nice to have a linux chat and share views and ideas here
  10. Microsoft Edge Reddit AMA: Edge might come to Linux No "technical blockers" to prevent Microsoft from shipping Edge for Linux. Image: Microsoft The Microsoft Edge developer team has held an AMA (Ask Me Anything) session on Reddit today, and the company's engineers have revealed some of their plans on various current or upcoming features. The biggest tease the company dropped was its apparent willingness to release an Edge version for Linux -- a move that was once considered inconceivable. "We don't have any technical blockers to keep us from creating Linux binaries, and it's definitely something we'd like to do down the road," the Edge team said. "That being said, there is still work to make them 'customer ready' (installer, updaters, user sync, bug fixes, etc.) and something we are proud to give to you, so we aren't quite ready to commit to the work just yet. "Right now, we are super focused on bringing stable versions of Edge first to other versions of Windows (as well as macOS), and then releasing our Beta channels," Edge devs said. While the Chromium codebase on which the upcoming Edge version supports Linux builds, users were afraid that when Microsoft ripped out various Chromium features last year, it might have impacted Edge's ability to support cross-platform builds. However, today's comment comes to confirm a tweet published in April on the personal Twitter account of one of Edge's developers. At the time, the developer couldn't officially confirm officials plans for a Linux build. Microsoft didn't commit to a Linux build today either, but now we at least know there's no technical block that may prevent it from shipping an Edge for Linux version. Right now, as the Edge team made it pretty obvious, it's only a matter of taking baby steps. Devs would most likely want to have a stable release out for all Windows versions first, before committing to additional platforms. NO WORD ON THE AD BLOCKER PLANS In addition, the Edge team also answered a question on one of today's most important topics in technology -- Chrome's upcoming extensions API changes that may end up crippling ad blockers. Last week, representatives from Opera, Brave, and Vivaldi told ZDNet they didn't have any plans to cripple ad blockers in their products, despite the shared Chromium codebase. At the time, Microsoft did not reply to an official request for comment on the matter regarding this issue that ZDNet sent the company. In today's AMA, the browser maker remained as non-commital as last week, delaying an official answer, pending more talks with "popular extension developers and with the Chromium community." The good news is that yesterday, Google gave in to some of the demands put forward by extension devs and ad blockers, so in the end, Microsoft may not even have to answer these questions anymore. TRACKING PROTECTION COMING TO EDGE But there's more. According to Edge developers, the company is also planning on rolling out a Tracking Protection feature similar to the one that Firefox rolled out. "We are committed to building features that give users control and transparency over their privacy on the web," Edge devs said. "One of our first features is Tracking Prevention with 3 levels of control to choose from, with Balanced setting being the default." For now these are all the details available about this feature. Other notable answers on other topics are below: - Microsoft is incorporating Fluent UI components into Edge to evolve the browser's look and feel. - The main goal is "to ship a browser at such high quality that it could eventually become the default browser for all Microsoft devices." - Devs plan to port the reading list feature from the old Edge to the new Chromium-based Edge. - Settings and other pages will also respect the browser's dark theme. - An extensions syncing feature is coming soon. Source
  11. Collider scopes alternative The Large Hadron Collider at CERN INTERNATIONAL LEAGUE OF BOFFINS CERN is to switch to Linux to save costs. Last year, the company launched the 'Microsoft Alternatives Project' to examine ways that the company could work smarter by switching to Linux-based operating systems. Its initial goal was to "investigate the migration from commercial software products (Microsoft and others) to open-source solutions, so as to minimise CERN's exposure to the risks of unsustainable commercial conditions." Also to 'seek out new life and new civilisations, to bol…. Sorry, that's Star Trek. Moving on then. CERN appears to be one of the first major organisations switching to Linux as an alternative to switching to Windows 10 ahead of Windows 7 reaching end of life next January. The company also refers to 'licence fee increases' as a reason for the change. CERN has traditionally been allowed to take Microsoft products at the 'academic institution' rate but was recently forced to change to a 'by-the-seats' model based on the number of users. According to a ZDNet, the implementation of the scheme will begin this summer with a pilot of an open source mail service, initially for volunteers and the IT staff. This will then be rolled out across the complex later in the year. The change is not completely alien to the boffin brigade - OpenStack is already widely in use and has only recently stopped developing its own 'Scientific Linux' distro with Fermilab, based on Red Hat Enterprise Linux, after it became obvious that CentOS could fulfil the same functions out of the box. At present, there's no indication of what the replacement for Windows will be, or what existing distro (if any) it will be based on, nor when it will be rolled out, but there's little doubt that CERN is setting the tone for the next six months, where we're likely to see a lot more organisations voting with their feet over their future, post Windows 7. Source
  12. Your Linux Can Get Hacked Just by Opening a File in Vim or Neovim Editor Linux users, beware! If you haven't recently updated your Linux operating system, especially the command-line text editor utility, do not even try to view the content of a file using Vim or Neovim. Security researcher Armin Razmjou recently discovered a high-severity arbitrary OS command execution vulnerability (CVE-2019-12735) in Vim and Neovim—two most popular and powerful command-line text editing applications that come pre-installed with most Linux-based operating systems. On Linux systems, Vim editor allows users to create, view or edit any file, including text, programming scripts, and documents. Since Neovim is just an extended forked version of Vim, with better user experience, plugins and GUIs, the code execution vulnerability also resides in it. Code Execution Flaw in Vim and Neovim Razmjou discovered a flaw in the way Vim editor handles "modelines," a feature that's enabled-by-default to automatically find and apply a set of custom preferences mentioned by the creator of a file near the starting and ending lines in the document. Though the editor only allows a subset of options in modelines (for security reasons) and uses sandbox protection if it contains an unsafe expression, Razmjou revealed that using ":source!" command (with a bang [!] modifier) can be used to bypass the sandbox. Therefore, just opening an innocent looking specially crafted file using Vim or Neovim could allow attackers to secretly execute commands on your Linux system and take remote control over it. The researcher has also released two proof-of-concept exploits to the public, one of which demonstrates a real-life attack scenario wherein a remote attacker gains access to a reverse shell from the victim's system as soon as he/she opens a file on it. The maintainers of Vim (patch 8.1.1365) and Neovim (released in v0.3.6) have released updates for both utilities to address the issue, which users should install as soon as possible. Besides this, the researcher has also recommended users to: disable modelines feature, disable "modelineexpr" to disallow expressions in modelines, use "securemodelines plugin," a secure alternative to Vim modelines. Source
  13. The first beta candidate of LibreOffice 6.3 is out — and it brings some bad news for 32-bit Linux desktop users. Ahead of an expected summer release, The Document Foundation has today issued a call for testing on the first beta of what will become the next major version of its free office suite, LibreOffice. Planned LibreOffice 6.3 features include further performance improvements, better tools, feature enhancements, and better interoperability and compatibility with other office formats. But sadly the update won’t be available to everyone. Nestled amidst all of the 6.3 beta release announcement bumf is word that LibreOffice 6.3 will not support 32-bit GNU/Linux distributions If you’re a LibreOffice swot you might have had an inkling that this day was coming as TDF mentioned it in the release notes of the previous stable release, LibreOffice 6.2: But before you (or anyone) panics let me reassure you of a couple things. First, you can continue to use LibreOffice on a 32-bit Linux desktops — this news only affects the next version. You won’t be able to download and upgrade to LibreOffice 6.3 when it’s released in early August 2019, but old versions remain available (some of which are still supported) for use. The pseudo-LTS version, LibreOffice 6.1, will continue to get updates for 32-bit Linux desktops for a while longer yet. Secondly, this is open source code. It’s possible that the wider Linux community could step in to maintain unofficial 32-bit builds which you can use on 32-bit Linux distros like Peppermint OS. No surprise, though The deprecation of native 32 support will surprise no-one. Like a well-timed demolition, more and more Linux distributions are dropping support for 32-bit builds. Xubuntu 19.04 is among the latest. It’s not just distributions, either. Google Chrome axed 32-bit Linux support back in 2016. Download LibreOffice 6.3 Beta Interested in trying the latest beta? Well, if you’re using Windows 7, a supported version of macOS or a 64-bit Linux distribution (sorry, too soon?) you can! And while I haven’t tried it personally, you can apparently install and run beta builds of LibreOffice alongside the current stable version, which is pretty neat. You’ll find downloads, installers and more details over on The Document Foundation wiki page for this release. Source
  14. Unlike the Windows cybersecurity ecosystem, the threats concerning the Linux systems aren’t often discussed in much detail. The attacks either go undetected by the security mechanisms laid out by enterprises or they aren’t too severe to be reported widely by the security researchers. However, as pointed out by cybersecurity firm Intezer, malware with sophisticated evasion techniques, which often utilize the already available open source code, do appear on the horizon from time to time. One such recent malware discovered by the firm is HiddenWasp. What makes HiddenWasp pretty dangerous at the moment is the fact that it has a zero detection rate in all popular malware protection systems. How does HiddenWasp attack Linux machines? The first step of the HiddenWasp Linux malware involves the running of the initial script for the deployment of malware. The hidden script uses a user named ‘sftp’ with a hardocded password and cleans the system to eradicate older versions of malware in case the machine was already infected. Further, it proceeds to download an archive file from the server that contains all the components — including the rootkit and the trojan. The script also attempts to add the trojan binary to /etc/rc.local to work even after a reboot. The rootkit involved in the malware shares lots of similarities with the open source rootkit Azazel. It also shares parts of strings with ChinaZ malware, Adore-ng rootkit, and Mirai malware. Talking about the capabilities of this stealthy Linux malware, it can run commands on the terminal, execute files, download more scripts, etc. However, security researchers still don’t know the actual infection vector; they suspect that the malware was spread in systems already controlled by the hackers. So, it could be said that HiddenWasp is being used as a secondary payload. If you’re interested in knowing about HiddenWasp Linux malware in detail, feel free to read the technical analysis of the same on Intezer blog. Source
  15. Cinnamon, the popular desktop environment featured in Linux Mint, makes more sense as a distribution-agnostic package. Since time immemorial—or, more likely, the late 1990s—the intractable problem of "fragmentation of the Linux desktop" has been debated on the internet. While some contend that the wide variety of competing distributions offers more choice to users, that choice can also be overwhelming—making it too difficult for new users to decide on a distribution, or leading them to choose a distribution that is poorly-built or unsupported, providing a bad first experience. While these arguments have merit, they ignore a critical problem: The infrastructure and developer attention needed to maintain a distribution is extensive, and difficult to justify. Long-running Linux distributions have stopped operations due to a lack of resources, and it is time for Linux Mint to consider doing the same in order to prevent developer burnout, while transitioning Cinnamon into being a fully distribution-agnostic desktop environment. Popular Linux distributions are ceasing operations Shortly after the release of Red Hat Enterprise Linux 8 in May, Fermilab announced that there would be no new edition of Scientific Linux, ending Fermilab's 20-plus year history of maintaining their own Linux distribution. Scientific Linux is little more than a recompiled version of RHEL sources, with Red Hat's trademarks removed. This strategy made sense at the time, as RHEL is a paid, commercial distribution. Red Hat's 2014 acquisition of CentOS—a general-purpose free recompile of RHEL sources—made Scientific Linux functionally redundant, particularly with the introduction of CentOS Special Interest Groups (SIGs). CERN withdrew from Scientific Linux in 2015, beginning a migration to CentOS, with Fermilab announcing their own migration to CentOS 8 as part of the transition from their own distribution. Likewise, the Arch-based Antergos distribution announced plans to shut down, as the developers "no longer have enough free time to properly maintain Antergos," and that "continuing to neglect the project would be a huge disservice to the community." Certainly, community members have already announced their intent to continue under the name Endeavour, which will be a significant undertaking—building a user-friendly installer for Arch is an interesting science experiment, considering that this is more or less at odds with Arch's goal of reducing abstractions that complicate system management. Why Linux Mint became popular Linux Mint has the unique distinction of being pragmatically correct twice, relative to the history of Linux on the desktop. When Mint was introduced in 2006, patent-encumbered codecs were not straightforward to install in popular distributions like Ubuntu or Fedora; likewise, proprietary software like Adobe Flash required separate installation, which was itself often a challenge. In part, this was made possible due to Mint being distributed from the EU, where software patents are essentially unenforceable. Circumstances changed shortly thereafter, as Ubuntu added an extra screen to the installer to install codecs starting with Ubuntu 7.04, and in 2008, various third-party repositories for Fedora merged to form RPM Fusion, providing a single source for packages not provided by Fedora for legal reasons. By 2010, Google Chrome 5 was released, providing an embedded Flash plugin, and support for Linux (and Mac OS), making the process of using Flash on Linux more straightforward. Since then, Flash adoption has plummeted, with support ending at the end of 2020. Patents for MPEG-2, MP3, and Dolby AC3 have since expired, allowing Linux distributions to provide this capability freely, out of the box. While Mint was the first distribution to effectively solve this problem, the conceit that Mint is easier to use because it provides codecs installed by default no longer holds merit, as other distributions have since caught up. Mint has actually regressed in this position, as codecs are no longer installed by default as of Linux Mint 18, making this identical to other Linux distributions. The desktop environment debacle of the early 2010s Nearly simultaneously, every major OS made highly polarizing changes to the user interface. Microsoft introduced the "don't call it Metro" interface with Windows 8, in 2012, which landed with a thud, and in part, prompted the exit of Stephen Sinofsky. In 2014, OS X Yosemitie attempted to make Helvetica Neue the default font, and abandoned the idea a year later. Linux had their own schism, for desktop environments. Ubuntu Unity, originally developed for Netbooks, was introduced in 2010 to widespread derision, though had redeemed itself by the release of 12.04, with TechRepublic's Jack Wallen migrating back to Ubuntu after jumping ship following issues with the initial releases. Likewise, in 2011, the introduction of GNOME 3.0 on Fedora 15 was met with derision. GNOME 3 was intended for use with touchscreens, upending the usage patterns that users had become familiar with, prompting Linus Torvalds to declare it "unacceptable." Dirk Hohndel, then-chief Linux and open-source technologist at Intel, declared at the time that "Gnome 3 is just completely unusable as far as I'm concerned." None of these were nearly ready for primetime when they launched, and this drove users away. For a time, Linux Mint "just worked" in a way that other distributions struggled to do, because they pushed too-new software on users. Out of this chaos was born Cinnamon, the fork of GNOME 3 built for Linux Mint that uses the classic desktop paradigm introduced in Windows 95. It's familiar, and that's a good thing. Cinnamon, the raison d'être of Linux Mint Cinnamon's familiarity to millions, and the easy learning curve it provides by retaining a usage paradigm nearly 25 years old, is necessary, in a way that proponents of GNOME or KDE may be unwilling to admit. While Cinnamon is not the only desktop environment shipped by Mint, the distribution has jettisoned the KDE edition with the release of Mint 19. While Mint did not start with Cinnamon, for some time the bulk of original code produced by the Linux Mint team relates to Cinnamon—it is the reason the distribution has enduring popularity. That said, the process of developing a Linux distribution and developing a desktop environment are rather dissimilar. Clément Lefèbvre, the founder and project leader of Linux Mint, does a fantastic job of guiding development of Cinnamon, though noted his own frustrations with the project in the March Mint update. The post is difficult to summarize succinctly, though he notes that "I personally haven't enjoyed this development cycle so far," and notes a divide between the concept of "users" and "developers." The following month, Lefèbvre—who simply goes by Clem, in the Linux community—walked back the comments noting that he is not "depressed," despite some blogs reporting it as such, adding that "I also talked a tiny bit too much about what was going on within the team. On the one hand it is part of my role to report on the progress being done, on the other hand we're dealing with individuals, there are people involved, efforts being made, feelings which can be hurt and it's part of my role also to protect that." Clem doesn't need to carry the world on his shoulders Linux Mint is actually two distributions—the Ubuntu derivative, for which Cinnamon, MATE, and Xfce editions are provided, and the Cinnamon-based Linux Mint Debian Edition (LMDE), which exists "for the Linux Mint team to see how viable our distribution would be and how much work would be necessary if Ubuntu was ever to disappear." Notably, LMDE previously had Xfce and MATE editions, though those have been jettisoned as part of an increased focused on Cinnamon. Ubuntu is practically in the too-big-to-fail category, as Linux distributions go. While Canonical has abandoned development of Unity for Ubuntu—switching back to a modified GNOME 3—the distribution is continuing. Canonical is, at a minimum, solvent—particularly as expenditures for development of Unity stopped as programmers on that project were largely laid off. Ubuntu is not going anywhere. But, that only addresses why LMDE is unnecessary, not Mint overall. Maintaining this parallel plumbing for an alternative Mint for a doomsday scenario is paranoia, but it surfaces an interesting point: Cinnamon is, to an extent, developed to be distribution-agnostic, partially as a consequence of the existence of LMDE. Most of the original development for Mint is focuses on Cinnamon, though maintaining the plumbing for the Ubuntu and Debian-based distributions—and other infrastructure, such as the website—is a massive undertaking, and a time sink for a team this small. Cinnamon has momentum behind it, as the progressive, feature-rich implementation of the classic desktop paradigm for Linux users. (For comparison, MATE—while venerable—is essentially in maintenance mode.) Persisting in maintaining Linux Mint as a platform to showcase Cinnamon makes no sense, when the labor of maintaining a distribution is handled—better—by Ubuntu, Fedora, SuSE, and Arch, among a select few others. Ultimately, the benefit of Cinnamon can be realized as a truly distribution-agnostic desktop environment. Most of the work is already done: Fedora already has a Cinnamon spin, and can be installed in Debian, OpenSuSE, and Arch (among others). Transitioning Linux Mint development efforts to make Cinnamon an Ubuntu Flavor—adhering more tightly to Ubuntu's infrastructure and release timelines, rather than operating independently and running the risk causing package conflicts—would deduplicate a great deal of work, providing more time to further improve Cinnamon, and ease the strained schedules of Clem and other Linux Mint contributors. Source
  16. openSUSE Leap is the latest Linux distro to arrive on Windows 10 A giant (or at least sizeable) Leap for Linux-kind… Image credit: Pexels Windows 10 users interested in running Linux under the desktop operating system will doubtless be pleased to hear there’s another option available on the Microsoft Store in the form of openSUSE Leap 15.1. The new version of the distro only emerged last week, so has pretty swiftly made the leap (ahem) to Windows 10’s store, where you can download it right now. Version 15.1 boasts better support for modern hardware, along with improved YaST functionality. As the maker notes, the Windows 10 spin of the distro benefits from “true RPM package management using openSUSE’s package repositories”. Linux version of Winnti malware found All Chromebooks will now be Linux-ready The best rising Linux distros around As you might’ve seen, openSUSE makes the cut for our guide to the best Linux distros of 2019, although note that it is targeted at developers and system admins. Indeed, the Leap distribution has stability as a primary goal, being based on source code from SUSE Linux Enterprise. Growing support Still, even if this isn’t something that will interest you specifically, it’s great to see a growing raft of support for different Linux distros running under Windows 10 (via the Windows Subsystem for Linux). Operating systems like Ubuntu or Debian are already available, and more niche affairs are coming into play as we’ve already seen with the likes of Arch Linux (although that is an unofficial effort, so exercise some caution there – plus this distro really isn’t for the faint of heart, anyway, being a notoriously tricky beast to get up and running). Source
  17. Government Planning to Replace Windows 7 with Linux, Not Windows 10 With support for Windows 7 coming to an end in January 2020, more and more organizations and governments across the world are expected to begin the transition to Windows 10 in the coming months. But as far as the South Korean government is concerned, sticking with Windows is no longer an option, so the country is now gearing up for a massive move to Linux. The reason is as simple as it could be, according to information published by The Korea Herald: the government aims for reduced costs, as paying for licenses would no longer be necessary. While specifics on what Linux distro they want to embrace are not available, it looks like the first step towards this migration to the open-source world is a security audit that should help the government determine if their data is protected or not. Windows 7 EOL set of January 14, 2020 South Korean authorities are ready to spend some $655 million on the entire program, which includes not only the switch itself to Linux, but also new computers. However, the process will take place one step at a time, and it first includes a testing stage to find out “if the system could be run on private networked devices without security risks.” The South Korean government also wants to determine if their internal solutions can run on Linux, as this is obviously a challenge since they were originally developed with Windows in mind. Whether or not the South Korean government will switch to Linux is something that remains to be seen, but without a doubt, this can’t be good news for Microsoft. In fact, this decision to embrace Linux is living proof that with the Windows 7 end-of-support approaching, not everyone would be switching to Windows 10, but stepping closer to a non-Windows world too. Source
  18. Microsoft Edge Browser for Linux Possibly in the Works Microsoft is hard at work on migrating Edge browser from its very own EdgeHTML engine to Chromium, and after releasing preview builds for Windows 10, the company is now focusing on other platforms as well. For example, one of the short-term priorities for the software giant is to bring an early version of Microsoft Edge browser to macOS, and as we told you a few minutes ago, the download links are already live unofficially. Because it’s based on Chromium, Edge would be able to run on more than just Windows 10 and macOS, so it should technically land on any platform where Google Chrome is also available. According to a recent slide shown by Microsoft at the Build developer conference and spotted by Neowin, the Chromium-based Microsoft Edge could also make its way to Linux at some point in the future. The session, which was called “Moving the web forward with Microsoft Edge” focused on the efforts that Microsoft makes in the browser world and the features coming to the application.Chromium for LinuxThe slide you see here lists the platforms where Microsoft Edge will be able to run, and as you can see, it includes previous Windows versions, Windows 10, macOS, Android, iOS, and Linux. Microsoft Edge has already been confirmed on all platforms except for Linux, so it’s safe to assume that an announcement in this regard could follow very soon. Of course, we shouldn’t take this as a confirmation that Microsoft Edge is coming to Linux, albeit such a version of the browser simply makes sense. Chromium runs super-smoothly on Linux anyway, so there’s basically no reason for Microsoft not to bring its browser to the platform, especially given its Linux push recently. We have reached out to Microsoft hoping for a confirmation that Edge is coming to Linux and we’ll update the article when and if an answer is offered. Source
  19. Ubuntu Linux Is Now Supported on Microsoft's Windows Subsystem for Linux (WSL) 2 Canonical announced today that its popular Ubuntu Linux operating system is now fully supported on Microsoft's second generation of the Windows Subsystem for Linux (WSL). Windows Subsystem for Linux 2 was announced by Microsoft earlier today during its annual Microsoft Build conference, and it introduces a Linux kernel capable of providing the full set of functionality required for enterprise certification, as well as support for lightweight virtualisation, bringing Ubuntu on WSL to the same level as Azure and AzureStack's capabilities. "Performance optimisation of Ubuntu in Azure and WSL ensures total efficiency for enterprises developing new Linux applications on Microsoft platforms," said Kiko Reis, Vice President Cloud at Canonical. "Our commitment to security updates for the full stack on any cloud or virtualisation extends naturally to this new WSL environment."Canonical worked with Microsoft to certify Ubuntu on WSLIn order to simplify the developer experience with version control systems and Integrated Development Environments (IDEs) designed for the Windows operating system, Ubuntu on WSL now integrates Windows file sharing functionality, including Active Directory (AD) integration, as well as integration with other Windows services. Canonical's Director of Product Stephan Fabel said in a press release that Mark Shuttleworth's company has worked closer with Microsoft to certify the Ubuntu Linux on Windows Subsystem for Linux (WSL), including Snaps, Kubernetes, and Docker containers, to offers users a seamless computing environment for Ubuntu. The Windows Subsystem for Linux brings a compatibility layer on top of the latest Windows 10 operating system to let users run Linux binarys natively. It features a Linux-compatible kernel developed by Microsoft and it's compatible with several Linux OSes, including Ubuntu, Debian GNU/Linux, OpenSuSE, SUSE Linux Enterprise Server, and Kali Linux. Windows Subsystem for Linux 2 is much faster than the first version and promises to support even more apps. Source
  20. smallhagrid

    Linux launcher question...

    Hi Folks. I've set up my PC with Ubuntu-Mate 18.04.2 & have a windows guest already in use. When I start the VMWare app it is there & runs fine, no problems at all. What I seek is the way to make a desktop launcher that will start the app with the VMX file already open. I tried just making & using a link to the VMX file itself, but it didn't work. I've also searched as much as I could think of, but the searches seem to be too general & return unrelated results for me. (Even at the VMWare site - which is pretty useless when it comes to finding specific stuff...) Does anyone here know how this might be accomplished, please ?? Thanks for any helpful replies !!
  21. The ultimate all-in-one style mobile device has been a desire for years, and even though Canonical themselves tried and failed to fund their own Ubuntu phone, Samsung’s Linux on DeX beta has actually realised the full desktop OS on a mobile device experience. While we trialled the beta software at the tail end of last year on the Galaxy Note 9, it was only available to those who had access to the Note 9 or Galaxy Tab S4. That did leave a sour taste in the mouth for many wanting to try out Linux on their own Samsung handsets. Samsung has today confirmed that the Linux on DeX beta has now extended to a further set of devices, and now fully supports Android Pie and their own One UI OS skin. Users with the Galaxy S9, S9+, S10, S10e, S10+, S10 5G and the Tab S5e can now download the application and get started with Linux on their Galaxy devices. It’s worth noting that to download and install the app, you will need 8GB of free storage space on your device available. Galaxy devices supported Android Oreo Note9 Tab S4 Android Pie Note9 S9 & S9+ S10, S10e, S10+, S10 5G Tab S4 Tab S5e While fans of other Linux distros may not be too happy using Ubuntu, the ability to flick between Android and then a fully fledged desktop OS is still neat even if you’re a fervent advocate for another version fork of Linux. How to install Linux on DeX Download the Linux on DeX beta application. Ensure you have at least 8GB of storage remaining on your Galaxy device Once you are accepted to the Linux on DeX beta program you will receive a link to download the application on your Samsung device. Open the application and download the official Ubuntu build for Samsung DeX devices to your local storage. Once completed, you can assign storage limits before launching directly into your Ubuntu desktop. What can you do with Linux on DeX beta? Download your source code from Git repository and run and maintain your code base Manage and monitor your server using server CLI Create C/C++/Java projects using your favorite IDE Enjoy a true desktop PC experience using an Android-powered device Where can you get DeX? Get the Samsung DeX docking station Get the Samsung DeX Pad Get the Samsung DeX cable It’s worth noting that the Linux on DeX beta is not guaranteed to lead to a fully fledged release on Samsung devices in future. That said, the beta program being opened up to more devices is a great sign that we will eventually see Linux on future Galaxy devices. Source
  22. We brought you the list of the most popular programming languages as per the Stack Overflow’s annual developer survey. Being the largest survey of its kind, it’s able to deliver some fascinating insights regarding the current software development landscape. We, unsurprisingly, discovered that JavaScript continues to be the most popular programming language with about 70% of respondents using it. In the second article of that series, we are going to tell you about the preferred platforms for development. The development platform is critical as it can either make you fall in love with your work or just drive you nuts. That’s why Stack Overflow asked developers about the platforms they love working for and the ones they’ve actually worked for in the past year. 16 Most popular development platforms As the article’s title has already revealed, Linux is the most popular platform among the survey respondents. Out of the 80,144 responses, 53.3% were in favor of Linux. This means that they’d done development work for Linux over the past year. This number has increased from last year’s 48.3%, which is a really encouraging sign for the open source community. Linux was followed by its closed source nemesis Windows, which gained 50.5% votes. For the first time, Stack Overflow included container technologies in the survey, and Docker ended up at #3 with 31.5% votes. Platforms Votes Linux 53.30% Windows 50.70% Docker 31.50% Android 27.00% AWS 26.60% MacOS 22.20% Slack 20.90% Raspberry Pi 15.20% WordPress 14.50% iOS 13.00% Google Cloud Platform 12.40% Microsoft Azure 11.90% Arduino 10.70% Heroku 10.60% Kubernetes 8.50% IBM Cloud or Watson 1.90% 16 Most Loved Development Platforms Without a surprise, Linux also turned out to be the most loved platform for development with 83.1% votes. It means that developers surely loved working on Linux technologies. This is, again, an encouraging sign as this number has risen considerably as compared to last year’s 76.5%. Platforms Votes Linux 83.10% Docker 77.80% Kubernetes 76.80% Raspberry Pi 72.10% AWS 71.60% MacOS 70.50% iOS 68.10% Google Cloud Platform 66.80% Microsoft Azure 65.40% Slack 65.20% Android 64.50% Windows 64.20% Arduino 61.30% Heroku 52.70% IBM Cloud or Watson 44.60% WordPress 40.50% Keep reading, keep coding! Source
  23. Flatpak Linux App Sandboxing Gets New FUSE-Based System-Wide Installation Method The Flatpak development team released today a new stable version of their Linux application sandboxing and distribution framework that implements a new major feature around the system-wide installation method. Flatpak 1.3.2 is now available and it contains a major change in how installation of Flatpak apps is done system-wide as a user. The developers decided to rewrite the setup process of a Flatpak app due to the fact that the previous method caused unnecessary I/O and used more disk space. The new setup process relies on a custom FUSE file system. "The new setup uses a new custom fuse filesystem which the user writes to, and then when this is done we can safely revoke any access to this from the user, meaning the files can be directly imported into the system repository without needing to make a copy," explains Alexander Larsson in the GitHub announcement page. But it appears that there's also a downside of the new system-wide installation method, which apparently makes the packaging of a Flatpak app more complex due to it requiring to have a "flatpak" user already added in the package. Packagers can change the default user with the --with-system-helper-user=USERNAME parameter.Coming soon to a GNU/Linux distro near youIn addition to the new FUSE-based setup method, the Flatpak 1.3.2 release comes with a custom SELinux module, which can be enabled with the --enable-selinux-module parameters, to workaround an issue where the default SELinux policy prohibited Flatpak from passing a UNIX socket over the system bus. The selinux-module needs to be installed for this to work. Moreover, Flatpak 1.3.2 adds a new --socket=pcsc permission for accessing smart cards, a new runtime column to the "flatpak list" command, support for storing description, comment, icon and homepage fields from flatpakrepo files in the remote configuration, and lets users specify a rebasing version of end-of-life. Flatpak 1.3.2 will soon be available in the stable software repositories of your favorite GNU/Linux distribution. Source
  24. AV Linux to Drop 32-Bit Support, Focus Its Development on Debian 10 "Buster" The developers of the Debian-based AV Linux multimedia oriented GNU/Linux distribution have released a new version and announced some major upcoming changes in the development of the project. AV Linux is currently based on the stable Debian GNU/Linux 9 "Stretch" operating system series and features support for both 32-bit and 64-bit architectures, but AV Linux 2019.4.10 appears to be the last release with these features as the devs decided it's time for a change. They announced that the next major release of AV Linux will be based on the upcoming Debian GNU/Linux 10 "Buster" (currently developed under the Debian Testing umbrella), and that it will drop support for 32-bit installations. However, most probably current 32-bit installations will still be supported. "This release is basically an update of the ISO that fixes a couple of annoying bugs from the 2018.6.25 release with some notable updates and additions. It will mark the last release based on Debian Stretch and sadly it will also be the last release of the 32bit version," said the developer.What's new in AV Linux 2019.4.10AV Linux 2019.4.10 is the latest version of the Debian-based GNU/Linux distribution for musicians and video editors, shipping with some of the latest apps, including Mixbus Demo 5.2.191, LSP Plugins 1.1.9, LinVST 2.4.3, Dragonfly Reverb Plugins 1.1.2, KPP-Plugins 1.0+GIT, and AviDemux2.7.3. It also ships with a new Numix Circle theme and prepares users for the new Cinelerra-GG software by updating the repositories. The WineHQ and Spotify repository keys were refreshed as well, along with all the Debian GNU/Linux and third-party repositories, including those for the KXStudio application. Under the hood, the AV Linux 2019.4.10 release fixes the script responsible for removing the VBox Guest Additions package to keep the /etc/rc.local file executable and enable automatic mount of external drives, and fixes the missing "linvstconverttree" in LinVST. It also removes various obsoleted udev rules and the redundant "ArdourVST" build on the 32-bit ISO. You can download AV Linux 2019.4.10 right now from our free software portal if you want to install one of the best GNU/Linux distributions for audio and video production. Source
  25. In late 2017, Microsoft launched Windows 10 on ARM to let users run its operating system on the ARM processor-powered laptops, especially the ones powered by Snapdragon chips. The company also released a bunch of devices in partnership with OEMs like Asus, HP, and Lenovo, and marketed them as “Always Connected Devices.” Earlier this year, when a project named aarch64-laptops started gaining traction on GitHub, it seemed like a great idea to run Linux on ARM laptops. The project initially allowed users to run Ubuntu on Snapdragon-powered laptops like NovaGo TP370QL, HP Envy x2, and Lenovo Mixx 630. Now, it has been revealed that Red Hat is working with Fedora team to bring Fedora Linux to such devices. Red Hat is known for its commitment to the Linux hardware and it seems like this joint effort will be enough to clear different roadblocks. Red Hat’s Peter Robinson, in a tweet, mentioned that such Fedora running ARM laptops are coming “very soon.” What’s next for Linux on ARM? Just recently, we witnessed the release of Fedora 30 Beta and the final release is also around the corner. So don’t expect Fedora on the ARM laptop to ship in this cycle. To start with, the initial focus of this collaboration will be Lenovo devices running Snapdragon 850, which was introduced as a higher-binned version of 845. Yoga C630 and Miix 630 are a couple of great machines with this chip and it would be really interesting to see Linux running on these laptops that deliver ~20 hours battery life on Windows. Overall, it seems like a big development and I’d definitely love to use an ARM-based laptop running Linux. Source
  • Create New...