Language Selection

English French German Italian Portuguese Spanish

Death of Vista 7 as Opportunity for GNU/Linux

Filed under
GNU
Linux
Microsoft
  • Free Software Foundation suggests Microsoft 'upcycles' Windows 7... as open source

    More than 10 years on from its campaign to persuade users to dump Windows 7 for a non-proprietary alternative, the Free Software Foundation (FSF) has kicked off a petition to urge Microsoft to open-source the recently snuffed software.

    On the face of it, the logic seems pretty simple. On 14 January Windows 7 reached its end of life as Microsoft turned off the free security update taps with a final fix (which seemed to bork desktop wallpapers for some users).

    "Its life doesn't have to end," cried the foundation. "We call on Microsoft to upcycle it instead."

    Unfortunately, the FSF couldn't resist a final dig, saying the killing of the OS had brought to an end "its updates as well as its 10 years of poisoning education, invading privacy, and threatening user security."

  • Windows 7 Alternatives

    Lets go over all the alternatives you can switch to if you are stuck on Windows 7 still. This will go over upgrading to Windows 10, Linux, or Other...

  • A new glimmer of hope for Linux

    Linux desktop operating system struggle after it won the title of the best server system “undisputedly”, so the GNU Linux developers began making plans to bring in more users, but it was not as effective as expected (in another article, we will take a look at these plans and the reasons for their lack of effectiveness).

    On January 14, 2020, and in light of repeated disappointments, a new glimmer of hope appeared, as Microsoft announced the end of support for Windows 7, which has a market share of more than 28%, which is a percentage that it cannot be taken lightly, as if the GNU Linux developers succeed in attracting Windows 7 refugees, it will be the linux century deal that will attract investors and major software companies (Adobe and others) and the painful blow to Microsoft that will make the company think many times before any step.

The orignal post (prank?) from FSF

  • Tell Microsoft to upcycle Windows 7. Set it free!

    It was just last week that Windows 7 crossed into the afterlife. While we can't say we've been in mourning, we have spent that time thinking back on Windows 7's legacy of abusing users, and reflecting on Microsoft's change in tone over the last few years. For one, they now state clearly that Microsoft "loves open source" (sic).

    But things were not always this way, and we can thank software activists around the world for making the message of software freedom too loud to ignore. In the headlines we've seen many stories of people feeling burned by the support cutoff, and justifiably angry by being forced to upgrade. Microsoft is leaving its users high and dry, but they don't have to. There is another option.

    Microsoft has taken a few steps in the right direction, such as releasing some small but important components of Windows as free software. We want to push them to go further. We need Microsoft to prove to the world that their "love" of free software isn't just an ad campaign, and that they aren't just reaping the benefits of free software in order to exploit users.

Free Software Foundation Asks Microsoft To Release Windows 7

  • Free Software Foundation Asks Microsoft To Release Windows 7 Code

    The Free Software Foundation this week announced that it has established a petition demanding that Microsoft release its proprietary Windows 7 code as free software.

    The foundation aims to get 7,777 signatures to that effect. By "free," the organization means that "the users have the freedom to run, copy, distribute, study, change and improve the software," according to its definition. The organization claims that free software is different from open source software in terms of "values."

    Windows 7 reached its end-of-life stage on Jan. 14, meaning that Microsoft no longer distributes free software patches for it, although a paid Extended Security Updates program is available. The operating system is considered to be "unsupported" software by Microsoft, and it's thought to be potentially insecure to use it, since Microsoft won't patch software vulnerabilities, even if they are publicly known.

  • Free Software Foundation 'demands' Windows 7 be released as free software

    WTF?! The Free Software Foundation (FSF), the same group behind the 2009-era Windows 7 "sins" campaign that encouraged users to throw Windows 7 in the trash, has now started another initiative -- one that demands Windows 7 be opened up as free software.

    The FSF has launched the "Upcycle Windows 7" petition, and if the opening paragraph doesn't persuade Microsoft to open source Windows 7, then I don't know what will.

    "On January 14th, Windows 7 reached its official 'end-of-life,' bringing an end to its updates as well as its ten years of poisoning education, invading privacy, and threatening user security. The end of Windows 7's lifecycle gives Microsoft the perfect opportunity to undo past wrongs, and to upcycle it instead," the petition reads.

    Yikes. At any rate, most users probably agree that Windows 7 already undid Microsoft's past wrongs, being absolved for the sins of Windows Vista. Hey, maybe the FSF should ask for Windows Vista instead. You know, shoot for the moon and land in the stars kind of thing. Something's better than nothing.

    [...]

    Then there's the not insignificant fact that much of the codebase in Windows 7 lives on in Windows 10. In other words, the chance of seeing Windows 7 in a GitHub repo anytime soon is unlikely, to say the least.

Windows 7 As Open Source? Petition Filed To Upcycle Microsoft

  • Windows 7 As Open Source? Petition Filed To Upcycle Microsoft's OS

    Windows 7 reached its “end-of-life” on January 14, 2020, as Microsoft stopped releasing any free security updates for the operating system. However, on January 23, 2020, the Free Software Foundation filed a petition urging Microsoft to open-source Windows 7 and upcycle the OS.

    “Microsoft’s support of Windows 7 is over, but its life doesn’t have to end. We call on Microsoft to upcycle it instead,” said the foundation.

Laughable article or spam?

  • Fund SPO demanded that Microsoft open source code Windows 7

    The representatives of the Free Software Foundation, an organization promoting the idea of free software was published online petition in support of the proposal to enable independent programmers to improve Windows 7. For the implementation of this idea requires access to the OS code. Fund SPO offers Microsoft to allow third-party developers to modify and distribute the software to respect the users, not to force them to move to other operating systems because of the lack of choice. In the organization plan to receive from the Corporation of evidence of user support. The Fund SPO 7777 intend to collect signatures to petition Upcycle Windows 7 and he set the example of the production of utilities of the OS in the form of freely available programs, which is practiced now.

Vista 7 should live on as open source, spectacularly optimistic

  • Windows 7 should live on as open source, spectacularly optimistic petition demands

    After all, Microsoft is huge on everything open source these days, right? It’s all about open source, listening to user feedback, and acting on it.

    The feedback from FSF might raise a few hackles at Microsoft, though, as the wording of the petition is, shall we say, on the strong and blunt side.

    It reads: “On January 14th, Windows 7 reached its official ‘end-of-life,’ bringing an end to its updates as well as its ten years of poisoning education, invading privacy, and threatening user security. The end of Windows 7’s lifecycle gives Microsoft the perfect opportunity to undo past wrongs, and to upcycle it instead.

    “We call on them to release it as free software, and give it to the community to study and improve. As there is already a precedent for releasing some core Windows utilities as free software, Microsoft has nothing to lose by liberating a version of their operating system that they themselves say has ‘reached its end.’”

    And FSF further directly addresses Microsoft executives to “demand that Windows 7 be released as free software”, and urges them “to respect the freedom and privacy of your users – not simply strongarm them into the newest Windows version.”

Microsoft Must Open Source Windows 7, Free Software Foundation

  • Microsoft Must Open Source Windows 7, Free Software Foundation Says

    The organization claims that by open-sourcing Windows 7, Microsoft can allow the community to “study, modify, and share” code in the operating system. This would also allow the company to “respect the freedom and privacy” of users, FSF continues.

    “We call on them to release it as free software, and give it to the community to study and improve. As there is already a precedent for releasing some core Windows utilities as free software, Microsoft has nothing to lose by liberating a version of their operating system that they themselves say has ‘reached its end,’” the Free Software Foundation adds.

    At the time of writing, the petition has nearly 5,000 supporters.

    Of course, Microsoft hasn’t responded to the petition, but it goes without saying that you shouldn’t expect the company to open-source Windows 7. There are many reasons the company won’t do this, including the fact that Windows 7 shares much of the code with Windows 10, and open-sourcing the 2009 OS would obviously expose its successors.

Microsoft urged: Open-source Windows 7 to 'undo past wrongs'

  • Microsoft urged: Open-source Windows 7 to 'undo past wrongs'

    But Microsoft is unlikely to cave into the Windows 7 demands that FSF outlined in a petition launched last week, asking Microsoft to "give it to the community to study and improve".

    FSF argues that Microsoft has "nothing to lose by liberating a version of their operating system that they themselves say has reached its end.

    The petition was aiming to gather at least 7,777 supporters and today has exceeded that by 1,000.

    [...]

    Also, as The Register points out, there are still portions of Windows 7 code in Windows 10, so it's probably not in the company's best interests to release a free version of Windows 7.

    A free Windows has been a consistent demand of Stallman, who retired from FSF last year. He gave a speech at Microsoft Research last year outlining 10 demands, including that Microsoft "publicly take back Microsoft's attacks on copyleft made in the 2000s" and to release the source code of Windows under the GNU GPL.

Petitioners Demand Microsoft Release a Free Windows 7

  • Petitioners Demand Microsoft Release a Free Windows 7

    The Free Software Foundation wants Microsoft to keep Windows 7 alive as a free operating system. Microsoft stopped providing free security patches and support for Windows 7 earlier this month.

    Although the popular operating system reached its 10th birthday last fall, some 200 million PCs around the globe still run it, according to industry estimates. Users include small business owners, some larger companies, government agencies, and hordes of consumers worldwide.

    Microsoft expects most Windows 7 users to migrate to Windows 10, but it continues to provide patches and support for Windows 7 Pro and Enterprise, which are eligible for extended security update support for three years, for a fee. Windows 7 Home editions and Ultimate editions are not included in the options to purchase extended support.

    The FSF this week launched the "Upcycle Windows 7" petition. The organization is still collecting signatures, though it has surpassed its goal of getting 7,777 people to sign on to make Windows 7 available for free. The current tally is approaching 10,000.

    Making the OS free would allow users "the freedom to run, copy, distribute, study, change and improve the software," according to the foundation.

Microsoft Asked to Unshackle Windows 7 From Proprietary Tyranny

  • Microsoft Asked to Unshackle Windows 7 From Proprietary Tyranny

    The Free Software Foundation (FSF) is asking Microsoft to 'upcycle' Windows 7 and allow the community to continue to improve it after its end of life.

    "On January 14th, Windows 7 reached its official 'end-of-life,' bringing an end to its updates as well as its ten years of poisoning education, invading privacy, and threatening user security," says the FSF in a petition published on its website.

    The end of Windows 7's lifecycle gives Microsoft the perfect opportunity to undo past wrongs, and to upcycle it instead."

    The non-profit organization, founded by Richard Stallman in 1985 to support and promote the free software movement, wants Redmond to give its EoL OS to the community, to be studied and improved upon.

    In support of this demand, the FSF uses the release of the Microsoft Calculator app as open-source on GitHub under MIT license.

Petition asking Microsoft to open-source Windows 7

  • Petition asking Microsoft to open-source Windows 7 sails past 7,777-signature goal

    Good news everybody! The Free Software Foundation has blown through its self-imposed target of 7,777 signatories in its efforts to persuade Microsoft to make Windows 7 open source.

    We noted last week the GNU-gang's attempt to coax the born-again open-sourcerer formerly known as "The Beast Of Redmond" into making a surprise deposit into GitHub.

    The thinking was that since Windows 7 has now come to the end of the road, as far as free security updates are concerned, then perhaps Microsoft might release it as open software?

    We put it to the Free Software Foundation that it might be more complicated than that – after all, Windows 7 contains all manner of codecs and the like licensed from third parties, as well as code licensed back to those same customers.

    The FSF's Greg Farough told us: "We want all software to be free software." The clue, after all, is in the name. "But Microsoft freeing just the operating system itself would satisfy our demand here."

    But what of those enterprises that have already paid for support? Should Microsoft start lobbing out refunds or fork the freshly open-sourced code base?

Free Software Foundation behind petition to Open Source Windows

  • Free Software Foundation behind petition to Open Source Windows 7

    When Windows 7 was first released Microsoft and open-source software appeared to be at diametric opposites of the spectrum, but since then Microsoft has actively adopted free software development principles internally, and contribute to numerous open-source software projects, including famously the Chromium rendering engine.

    It may have been this change of heart which encouraged Greg Farough, Campaigns Manager at the Free Software Foundation to pen a petition demanding Microsoft open-source Windows 7, now that the software has reached End of Life.

  • Microsoft Should Release Windows 7 as Free Software to “Undo Past Wrongs,” FSF Says

    Windows 7 reached its end of life on January 14, which means Microsoft will only be sending updates to paying customers. Users have been advised to upgrade to Windows 10 to avoid security issues. But, there are some who believe Microsoft should open source the operating system.

    The Free Software Foundation (FSF) has said that users can continue receiving updates if Microsoft open sources the operating system enabling the community to maintain it.

FSF calls on Microsoft to open source Windows 7

  • FSF calls on Microsoft to open source Windows 7

    The foundation hopes that if Windows 7 is open sourced, it will give the community the opportunity to study, modify, and share it. It also stated two other demands of Microsoft: “We urge you to respect the freedom and privacy of your users – not simply strongarm them into the newest Windows version. We want more proof that you really respect users and user freedom, and aren’t just using those concepts as marketing when convenient.”

    To support their goals, the FSF started a petition with a goal of 7,777 signatures. At the time of this writing, it has 9,600 signers.

There’s a petition to turn Windows 7 into an open-source OS

  • There’s a petition to turn Windows 7 into an open-source OS

    A year ago, Microsoft announced that Windows 7 would not be receiving any more support, starting from the 14th of January 2020. Based on the official termination of the support to the OS, FSF (Free Software Foundation) has created a petition calling for Microsoft to make Windows 7 open-source.

    The petition asks for 7777 signatures so that Microsoft ‘upcycles’ Windows 7, turning it free for everyone to use, study and improve. The petition already surpassed its objective, with 10574 signatures at the time of writing.

    As written in the petition’s official webpage, by turning Windows 7 into an open-source application, Microsoft would “undo past wrongs”, such as “poisoning education, invading privacy, and threatening user security”.

Thinking About an Open-Source Windows

Canonical Really Wants Windows 7 Users to Install Ubuntu

  • Canonical Really Wants Windows 7 Users to Install Ubuntu

    When it comes to the latter, the Linux world has long been recommended as a possible destination for Windows 7 users, with many anticipating an influx of Linux adopters once the 2009 Microsoft operating system is retired.

    Canonical, the maker of Ubuntu, obviously wants to benefit from this potential en-masse migration, so in the last few weeks, the company has been publishing several articles to explain “why you should upgrade Windows 7 to Ubuntu” and to highlight the hardware and software considerations when planning to switch to Ubuntu.

Why freeing Windows 7 opens doors

  • Why freeing Windows 7 opens doors

    Since its launch on January 24th, we've had an overwhelming amount of support in our call to "upcycle" Windows 7. Truthfully, the signature count flew far faster than we ever expected it to, even despite our conservative (if aptly numbered) goal of 7,777 signatures. We have seen the campaign called quixotic and even "completely delusional," but in every case, people have recognized the "pragmatic idealism" that is at the core of the FSF's message. Even where this campaign has been attacked, it's nevertheless been understood that the FSF really does want all software to be free software. We recommend every fully free operating system that we are aware of, and want to be able to expand that list to include every operating system. So long as any remain proprietary, we will always work to free them.

    Over the last few weeks, we have been carefully watching the press coverage, and are glad to see the message of software freedom popping up in so many places at once. We received a lot of support, and have responded to dozens of comments expressing support, concern, and even outrage over why the FSF would think that upcycling Windows 7 was a good idea, and why it was something we would want to demand.

An Alternative to Windows 7

  • An Alternative to Windows 7

    Probably not that many are familiar with the name of Mark Shuttleworth; more may be aware of his accomplishments. In the mid-1990s he founded Thawte Consulting. The company, specialized in digital certificates and internet security, was later acquired by VeriSign, earning Shuttleworth a substantial amount of money. From 2004, Shuttleworth invested in developing Ubuntu Linux.

    For a long time, the public perception of Linux software has been that is only something IT professionals are able to use, requiring a lot of additional coding and fine-tuning. While this is true for a specific part of the Linux ecosystem, there are many projects designed to bring Linux as close as possible to everyday users. Ubuntu is one of them. So what are the pros and cons of considering Ubuntu Linux as a replacement for Windows 7.

Programmers Push Microsoft to Open Windows

  • Programmers Push Microsoft to Open Windows

    The Free Software Foundation is giving Microsoft’s move away from proprietary software a helpful hug.

    Can opening Windows 7 to open-source developers, which the foundation promotes, advance Microsoft’s digital transformation?

    The alliance, which is committed to user control of the software that runs electronic devices, is circulating a petition that calls on Microsoft to put the retired operating system into the public domain.

    The Redmond, Washington, tech giant stopped supporting Windows 7 for most users at mid-month.
    Programmers Push Microsoft to Open Windows

Calling FSF "Open-Source Group"

  • Open-Source Group Sends Microsoft Blank Hard Drive to Copy Windows 7 Source Code

    The Free Software Foundation publicly requested Microsoft to open-source Windows 7 shortly after the 2009 operating system reached the end of support on January 14, and now the group is ready for the next move.

    Last week, the FSF mailed Microsoft a blank hard drive which the company should use for copying Windows 7 source code and then sending it back to the organization.

Open Source Group Wants Windows 7 Source Code In A Blank...

  • Open Source Group Wants Windows 7 Source Code In A Blank Hard drive

    Just when Microsoft ended the support for Windows 7, Free Software Foundation filed a petition demanding Windows 7 to be open source. Now, the open-source community went a little further by making another bold move.

    Reportedly, the FSF mailed a blank upcycled hard drive to Microsoft. The foundation wants Microsoft to send back the hard drive, but after copying Windows 7 source code in it, along with license notice.

"Hard Drive Delivered to Microsoft HQ to Copy Windows 7 Source"

  • Hard Drive Delivered to Microsoft HQ to Copy Windows 7 Source Code – Company Asked to Open Source Windows 7 to Prove It’s Not Fooling Its Users

    Windows 7 hit its end of service deadline on January 14 and things have since got interesting. From free Windows 10 upgrade offer that was supposed to have expired back in 2016 to people demanding Microsoft to open source the operating system, who knew pulling the plug would end up giving Windows 7 even more life.

    We reported a few weeks back that the Free Software Foundation along with some other groups were asking Microsoft to open source Windows 7 to "undo past wrongs." The Foundation has now delivered a hard drive to Microsoft asking the company to copy the source code and give it a license note to prove that "they really do love free software."

Free Software Foundation strategy: associate with Windows

  • Free Software Foundation sends hard drive to Microsoft to get Windows 7 source code

    On January 14, Microsoft pulled the plug on Windows 7 closing the chapter on what was one of the most popular Operating Systems in the world. Even though Windows 7 has reached the end-of-life, the OS is still used by millions around the world.

    Ever since Microsoft decided to end the support for Windows 7, several groups have been asking the company to release the source code of Windows 7 to allow to independent developers to work and provide support to the existing users. A couple of weeks back, we reported about an online petition demanding Microsoft open-source Windows 7. The petition was penned by Greg Farough, Campaigns Manager at the Free Software Foundation. The petition gained a lot of traction from Windows 7 fans and it had more than 13,000 signatures. Now that the petition has closed, Free Software Foundation has sent the signatures along with an empty hard drive. The foundation wants Microsoft to copy the source code of Windows 7 along with the license notice on to the drive and send it back. Not only that, but the foundation has also offered Microsoft to help with the transfer of the code.

Windows 7 Source Code To Become Open Source... (No)

  • Windows 7 Source Code To Become Open Source For Better Development Of Security Updates After End Of Life?

    Windows 7 crossed its End of Life Support date about a month ago. Since then, 0Patch has come forth with a micro-patch for a security vulnerability. In fact, even Microsoft sent out a patch to address an issue the company caused through the last official security update. However, with the operating system still currently running on millions of computers, there has been an increasingly vocal demand about making Windows 7 Source Code as Open Source. This would allow third-party software vendors and security companies to better develop solutions for the now obsolete operating system.

    Even though Windows 7 has reached the end-of-life, the OS is still used by millions around the world. While the actual numbers vary, about 12 to 14 percent of computers are still actively running Windows 7. This is despite the fact that Microsoft has confirmed that it won’t send out any security patches even if new vulnerabilities are discovered. Hence, independent developers and several groups have now begun to ask Microsoft to make Windows 7 Source Code as Open Source.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

GNU: GDB (Debugger), Project's History, and GCC (Compiler)

  • GDB Debugger Adds Support For Debuginfod Web Server

    Debuginfod is the Red Hat led debug information HTTP web server distributed as part of elfutils and able to supply on-demand source code and ELF/DWARF debug files to debuggers / IDEs / other compiler tooling. The GDB debugger can now tap debuginfod for on-demand source files and debug information that isn't present on the local system. The motivation with debuginfod is to carry less developer "baggage" on local systems when it comes to debug files and potentially even source files. Particularly for organizations or cases like Linux distributions, a centralized debuginfod server could in turn supply the needed files to clients based upon the requested build ID. Red Hat has been working to expand the debuginfod support both for the GNU toolchain and also LLVM, among other possible users.

  • When is GOTS not in the national interest?

    The modern open-source software (OSS) movement can be traced back to the early 1980s with the birth of Richard Stallman’s GNU Project and the Free Software Foundation. [...] However, cost is a red herring for the real challenge presented by GOTS software solutions. On the surface, GOTS seems very similar to OSS which implies that it has the larger structural advantages of OSS. If handled cautiously, it can have those advantages, but care needs to be taken about what sort of existing software is being commoditized. The U.S. has a national interest in maintaining a strong software development capability. We are fortunate to be the dominant software-building country in the world. According to the Forbes 2000 list, the total market capitalization of U.S. internet, software, and computer services companies is close to $4.7 trillion — more than twice the rest of the world combined. Software tech is an enormous comparative advantage for the U.S. As a result, it is clearly in the national interest to have the government avoid directly competing against and potentially weakening the U.S. private sector.

  • New compiler added to popular studio for ARM and Cortex-M IDE

    The studio for ARM/Cortex-M is now supplied with three different compilers: GCC, Clang and the company's own compiler. The new compiler outperforms GCC and regular Clang on most benchmarks, decreasing both size of generated code as well as its execution speed.

Kernel: LWN and Phoronix Articles About Latest Discussions and Linux Developments

  • Filesystem UID mapping for user namespaces: yet another shiftfs

    The idea of an ID-shifting virtual filesystem that would remap user and group IDs before passing requests through to an underlying real filesystem has been around for a few years but has never made it into the mainline. Implementations have taken the form of shiftfs and shifting bind mounts. Now there is yet another approach to the problem under consideration; this one involves a theoretically simpler approach that makes almost no changes to the kernel's filesystem layer at all. ID-shifting filesystems are meant to be used with user namespaces, which have a number of interesting characteristics; one of those is that there is a mapping between user IDs within the namespace and those outside of it. Normally this mapping is set up so that processes can run as root within the namespace without giving them root access on the system as a whole. A user namespace could be configured so that ID zero inside maps to ID 10000 outside, for example; ranges of IDs can be set up in this way, so that ID 20 inside would be 10020 outside. User namespaces thus perform a type of ID shifting now. In systems where user namespaces are in use, it is common to set them up to use non-overlapping ranges of IDs as a way of providing isolation between containers. But often complete isolation is not desired. James Bottomley's motivation for creating shiftfs was to allow processes within a user namespace to have root access to a specific filesystem. With the current patch set, instead, author Christian Brauner describes a use case where multiple containers have access to a shared filesystem and need to be able to access that filesystem with the same user and group IDs. Either way, the point is to be able to set up a mapping for user and group IDs that differs from the mapping established in the namespace itself.

  • Keeping secrets in memfd areas

    Back in November 2019, Mike Rapoport made the case that there is too much address-space sharing in Linux systems. This sharing can be convenient and good for performance, but in an era of advanced attacks and hardware vulnerabilities it also facilitates security problems. At that time, he proposed a number of possible changes in general terms; he has now come back with a patch implementing a couple of address-space isolation options for the memfd mechanism. This work demonstrates the sort of features we may be seeing, but some of the hard work has been left for the future. Sharing of address spaces comes about in a number of ways. Linux has traditionally mapped the kernel's address space into every user-space process; doing so improves performance in a number of ways. This sharing was thought to be secure for years, since the mapping doesn't allow user space to actually access that memory. The Meltdown and Spectre hardware bugs, though, rendered this sharing insecure; thus kernel page-table isolation was merged to break that sharing. Another form of sharing takes place in the processor's memory caches; once again, hardware vulnerabilities can expose data cached in this shared area. Then there is the matter of the kernel's direct map: a large mapping (in kernel space) that contains all of physical memory. This mapping makes life easy for the kernel, but it also means that all user-space memory is shared with the kernel. In other words, an attacker with even a limited ability to run code in the kernel context may have easy access to all memory in the system. Once again, in an era of speculative-execution bugs, that is not necessarily a good thing.

  • Revisiting stable-kernel regressions

    Stable-kernel updates are, unsurprisingly, supposed to be stable; that is why the first of the rules for stable-kernel patches requires them to be "obviously correct and tested". Even so, for nearly as long as the kernel community has been producing stable update releases, said community has also been complaining about regressions that make their way into those releases. Back in 2016, LWN did some analysis that showed the presence of regressions in stable releases, though at a rate that many saw as being low enough. Since then, the volume of patches showing up in stable releases has grown considerably, so perhaps the time has come to see what the situation with regressions is with current stable kernels. As an example of the number of patches going into the stable kernel updates, consider that, as of 4.9.213, 15,648 patches have been added to the original 4.9 release — that is an entire development cycle worth of patches added to a "stable" kernel. Reviewing all of those to see whether each contains a regression is not practical, even for the maintainers of the stable updates. But there is an automated way to get a sense for how many of those stable-update patches bring regressions with them. The convention in the kernel community is to add a Fixes tag to any patch fixing a bug introduced by another patch; that tag includes the commit ID for the original, buggy patch. Since stable kernel releases are supposed to be limited to fixes, one would expect that almost every patch would carry such a tag. In the real world, about 40-60% of the commits to a stable series carry Fixes tags; the proportion appears to be increasing over time as the discipline of adding those tags improves.

  • Finer-grained kernel address-space layout randomization

    The idea behind kernel address-space layout randomization (KASLR) is to make it harder for attackers to find code and data of interest to use in their attacks by loading the kernel at a random location. But a single random offset is used for the placement of the kernel text, which presents a weakness: if the offset can be determined for anything within the kernel, the addresses of other parts of the kernel are readily calculable. A new "finer-grained" KASLR patch set seeks to remedy that weakness for the text section of the kernel by randomly reordering the functions within the kernel code at boot time.

  • Debian discusses how to handle 2038

    At this point, most of the kernel work to avoid the year-2038 apocalypse has been completed. Said apocalypse could occur when time counted in seconds since 1970 overflows a 32-bit signed value (i.e. time_t). Work in the GNU C Library (glibc) and other C libraries is well underway as well. But the "fun" is just beginning for distributions, especially those that support 32-bit architectures, as a recent Debian discussion reveals. One of the questions is: how much effort should be made to support 32-bit architectures as they fade from use and 2038 draws nearer? Steve McIntyre started the conversation with a post to the debian-devel mailing list. In it, he noted that Arnd Bergmann, who was copied on the email, had been doing a lot of the work on the kernel side of the problem, but that it is mostly a solved problem for the kernel at this point. McIntyre and Bergmann (not to mention Debian as a whole) are now interested in what is needed to update a complete Linux system, such as Debian, to work with a 64-bit time_t. McIntyre said that glibc has been working on an approach that splits the problem up based on the architecture targeted. Those that already have a 64-bit time_t will simply have a glibc that works with that ABI. Others that are transitioning from a 32-bit time_t to the new ABI will continue to use the 32-bit version by default in glibc. Applications on the latter architectures can request the 64-bit time_t support from glibc, but then they (and any other libraries they use) will only get the 64-bit versions of the ABI. One thing that glibc will not be doing is bumping its SONAME (major version, essentially); doing so would make it easier to distinguish versions with and without the 64-bit support for 32-bit architectures. The glibc developers do not consider the change to be an ABI break, because applications have to opt into the change. It would be difficult and messy for Debian to change the SONAME for glibc on its own.

  • UEFI Boot Support Published For RISC-V On Linux

    As we've been expecting to happen with the Linux EFI code being cleaned up before the introduction of a new architecture, the RISC-V patches have been posted for bringing up UEFI boot support. Western Digital's Atish Patra sent out the patch series on Tuesday for adding UEFI support for the RISC-V architecture. This initial UEFI Linux bring-up is for supporting boot time services while the UEFI runtime service support is still being worked on. This RISC-V UEFI support can work in conjunction with the U-Boot bootloader and depends upon other recent Linux kernel work around RISC-V's Supervisor Binary Interface (SBI).

  • Linux Kernel Seeing Patches For NVIDIA's Proprietary Tegra Partition Table

    As an obstacle for upstreaming some particularly older NVIDIA Tegra devices (namely those running Android) is that they have GPT entry at the wrong location or lacking at all for boot support. That missing or botched GPT support is because those older devices make use of a NVIDIA proprietary/closed-source table format. As such, support for this proprietary NVIDIA Tegra Partition Table is being worked on for the Linux kernel to provide better upstream kernel support on these consumer devices. NVIDIA Tegra devices primarily rely on a special partition table format for their internal storage while some also support traditional GPT partitions. Those devices with non-flakey GPT support can boot fine but TegraPT support is being worked on for handling the upstream Linux kernel with the other devices lacking GPT support or where it's at the wrong sector. This issue primarily plagues Tegra 2 and Tegra 3 era hardware like some Google Nexus products (e.g. Nexus 7) while fortunately newer Tegra devices properly support GPT.

  • Intel Continues Bring-Up Of New Gateway SoC Architecture On Linux, ComboPHY Driver

    Besides all the usual hardware enablement activities with the usual names by Intel's massive open-source team working on the Linux kernel, one of the more peculiar bring-ups recently has been around the "Intel Gateway SoC" with more work abound for Linux 5.7. The Intel Gateway SoC is a seemingly yet-to-be-released product for high-speed network packet processing. The Gateway SoC supports the Intel Gateway Datapath Architecture (GWDPA) and is designed for very fast and efficient network processing. Outside of Linux kernel patches we haven't seen many Intel "Gateway" references to date. Gateway appears to be (or based on) the Intel "Lightning Mountain" SoC we were first to notice and bring attention to last summer when patches began appearing for that previously unknown codename.

Security: Updates, DNS Features in IPFire, Shodan and Canonical's Role in Robot Operating System (ROS 2)

  • Security updates for Wednesday

    Security updates have been issued by Debian (python-pysaml2), Mageia (clamav, graphicsmagick, opencontainers-runc, squid, and xmlsec1), Oracle (kernel, ksh, python-pillow, systemd, and thunderbird), Red Hat (rh-nodejs12-nodejs), Scientific Linux (ksh, python-pillow, and thunderbird), and SUSE (nodejs6, openssl, ppp, and squid).

  • What you can do with the new DNS features in IPFire

    Every time you try to access a website - for example ipfire.org - you will ask a DNS server for the IP address to connect to. They won't see anything past "the slash" in the URL, but that is not necessary to know what you probably have in mind to do. That DNS server now knows which bank you are with, where you work, where you do your online shopping, who is hosting your emails and many things more... Although this data is not too interesting about one individual, it becomes very relevant when you are looking at many profiles. People who shop at a certain place or are with a certain bank might be high earners. People who shop at another place might have trouble to stay afloat financially. Now I know what advertisements I need to show to which group so that they will become my customers. In short, your whole browser history tells a lot about you and you might be giving it away for free to the advertising industry or other parties who will use your data against you.

  • How Shodan Has Been Improved to Help Protect Energy Utilities

    Shodan is a well-known security hacking tool that has even been showcased on the popular Mr. Robot TV show. While Shodan can potentially be used by hackers, it can also be used for good to help protect critical infrastructure, including energy utilities. At the RSA Conference in San Francisco, Michael Mylrea, Director of Cybersecurity R&D (ICS, IoT, IIoT) at GE Global Research, led a session titled "Shodan 2.0: The World’s Most Dangerous Search Engine Goes on the Defensive," where he outlined how Shodan has been enabled to help utilities identify risks in critical energy infrastructure. Shodan, to the uninitiated, is a publicly available search engine tool that crawls the internet looking for publicly exposed devices. Mylrea explained that utilities are often resource constrained when it comes to cybersecurity and are typically unaware of their risk. In recent years, there have been a number of publicly disclosed incidents involving utilities. To help solve that challenge, Mylrea proposed a project to the US Department of Energy (DoE) to enhance Shodan for utilities so they could use the tool to find risks quickly.

  • Canonical takes leadership role in security for ROS

    Canonical is committed to the future of robotics, as proven a short time ago when we joined the Technical Steering Committee of the second version of the Robot Operating System (ROS 2). We’re also dedicated to building a foundation of enterprise-grade, industry leading security practices within Ubuntu, so we’re excited to join both of these strengths with our own Joe McManus taking the helm of the ROS 2 Security Working Group. We believe robots based on Linux are cheaper to develop, more flexible, faster to market, easier to manage, and more secure. While ROS began as an academic project over a decade ago, it has grown to become the most popular middleware for creating Linux-powered robots. It has harnessed the power of open source, allowing for many of the complex problems faced by robotics to be solved through collaboration. The ROS developer community has continued to grow, and ROS now enjoys an increasing amount of commercial use and supported robots. In response, the ROS community has completely overhauled the ROS codebase and started distributing ROS 2.

Audiocasts/Shows/Screencasts: The Linux Link Tech Show, FLOSS Weekly, Linux Headlines and Arch/Manjaro

  • The Linux Link Tech Show Episode 846

    nodejs 12, raspberry pi, 3d printing, air frying

  • FLOSS Weekly 567: DeepCode

    DeepCode alerts you about critical vulnerabilities you need to solve in your code. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection with 90% precision.

  • 2020-02-26 | Linux Headlines

    Brave joins forces with the Wayback Machine, the Linux Foundation teams up with IBM to fight climate change, and The Document Foundation puts out a call to the community.

  • Linux Apps I Use At Work

    Linux Apps I Use At Work This video will go over all the applications I use on my Work PC. I go over my email, file browser, and many other features. As a life long Windows user, I was able to optimize my workflow once I moved to Linux and pick up a lot of productivity.

  • Manjaro 19.0 KDE Plasma Edition overview | #FREE OPERATING SYSTEM.

    In this video, I am going to show an overview of Manjaro Linux 19.0 KDE Plasma Edition and some of the applications pre-installed.

  • Manjaro 19.0 XFCE Run Through

    In this video, we are looking at Manjaro 19.0 XFCE.