Language Selection

English French German Italian Portuguese Spanish

Games Leftovers

Filed under
Gaming
  • Surviving Mars’ upcoming “Opportunity” update will be adding several goodies based on player feedback

    The next big patch for the strategy title is in the works. The developers have shared a little of what we can expect and it’s looking good.

    [...]

    It’s a generally fun game that runs pretty well on Linux and I’ve personally sunk in about 30 hours since launch

  • Some thoughts on Pawarumi, a stylish and action-packed shoot ‘em up

    This eye-catching shoot ‘em up mixes constant action with Mesoamerican motifs and a story about revenge. I stuck with it despite dying a large amount of times and have some thoughts to share about the game.

  • Sega Is Bringing 15 Classic Games, Including Sonic, to the Switch This Summer

    There was a time when we thought that the Switch would be a perfect fit for the Virtual Console. While we wait for Nintendo to bring classic games to the Switch, Sega is already on the case.

    At a Sega fan event in Japan, the company announced the new Sega Ages initiative. Under this banner, the game developer will release titles for the Nintendo Switch, including the original Sonic the Hedgehog, Phantasy Star, and Thunder Force 4, starting this summer. The company said over fifteen games would be released on the platform, but only had these three titles to share so far. No word yet on whether the vastly superior later Sonic games will also be included.

More in Tux Machines

Review: System76 Oryx Pro Laptop

I should start by saying that although I'm definitely no newbie to Linux, I'm new to the world of dedicated Linux laptops. I started with Linux in 1996, when Red Hat 4.0 had just adopted the 2.0 kernel and Debian 1.3 hadn't yet been released. I've run a variety of distros with varying degrees of satisfaction ever since, always looking for the Holy Grail of a desktop UNIX that just plain worked. About 15 years ago after becoming frustrated with the state of Linux on laptop hardware (in a phrase, "nonexistent hardware support"), I switched my laptops over to Macs and didn't look back. It was a true-blue UNIX that just plain worked, and I was happy. But I increasingly found myself frustrated by things I expected from Linux that weren't available on macOS, and which things like Homebrew and MacPorts and Fink could only partly address. My last MacBook Pro is now four years old, so it was time to shop around again. After being underwhelmed by this generation of MacBooks, I decided to take the risk on a Linux laptop again. Read more

GNU Gets Its Own 'CoC'

  • Announcing the GNU Kind Communication Guidelines
    Announcing the GNU Kind Communication Guidelines The GNU Kind Communication Guidelines, initial version, have been published in https://gnu.org/philosophy/kind-communication.html. On behalf of the GNU Project, I ask all GNU contributors to make their best efforts to follow these guidelines in GNU Project discuaaions. In August, a discussion started among GNU package maintainers about the problem that GNU development often pushes women away.1 Clearly this is not a good thing.2 Some maintainers advocated adopting a "code of conduct" with strict rules. Some other free software projects have done this, generating some resistance.3 Several GNU package maintainers responded that they would quit immediately. I myself did not like the punitive spirit of that approach, and decided against it. I did not, however, wish to make that an excuse to ignore the problem. So I decided to try a different approach: to guide participants to encourage and help each other to avoid harsh patterns of communication. I identified various patterns of our conversation (which is almost entirely textual, not vocal) that seem likely to chase women away -- and some men, too. Some patterns came from events that happened in the discussion itself. Then I wrote suggestions for how to avoid them and how to help others avoid them. I received feedback from many of the participants, including some women. I practiced some of these suggestions personally and found that they had a good effect. That list is now the GNU Kind Communication Guidelines. The current version not set in stone; I welcome comments and suggestions for future revision. The difference between kind communication guidelines and a code of conduct is a matter of the basic overall approach. A code of conduct states rules, with punishments for anyone that violates them. It is the heavy-handed way of teaching people to behave differently, and since it only comes into action when people do something against the rules, it doesn't try to teach people to do better than what the rules require. To be sure, the appointed maintainer(s) of a GNU package can, if necessary, tell a contributor to go away; but we do not want to need to have recourse to that. The idea of the GNU Kind Communication Guidelines is to start guiding people towards kinder communication at a point well before one would even think of saying, "You are breaking the rules." The way we do this, rather than ordering people to be kind or else, is try to help people learn to make their communication more kind. I hope that kind communication guidelines will provide a kinder and less strict way of leading a project's discussions to be calmer, more welcoming to all participants of good will, and more effective. 1. I read that the fraction of women in the free software community overall is around 3%, whereas in the software field overall it is over 10%. 2. I disagree with making "diversity" a goal. If the developers in a specific free software project do not include demographic D, I don't think that the lack of them as a problem that requires action; there is no need to scramble desperately to recruit some Ds. Rather, the problem is that if we make demographic D feel unwelcome, we lose out on possible contributors. And very likely also others that are not in demographic D. There is a kind of diversity that would benefit many free software projects: diversity of users in regard to skill levels and kinds of usage. However, that is not what people usually mean by "diversity". 3. I'm not involved in those projects, even if in some cases I use the software they release, so I am not directly concerned about whatever internal arrangements they make. They are pertinent here only as more-or-less comparable situations.
  • Richard Stallman Announces GNU Kind Communication Guidelines
    Richard Stallman has announced the GNU Kind Communication Guidelines. The GNU founder hopes these guidelines will encourage women to get involved in free software development and be more kind in project discussions. The GNU Kind Communication Guidelines is an effort to "to start guiding people towards kinder communication." The GNU Kind Communication Guidelines differ from a Code of Conduct in that it's trying to be proactive about kindness around free software development over being rules with possible actions when breaking them.

Linus Torvalds is Back

  • ​Linus Torvalds is back in charge of Linux
    At Open Source Summit Europe in Scotland, Linus Torvalds is meeting with Linux's top 40 or so developers at the Maintainers' Summit. This is his first step back in taking over Linux's reins. A little over a month ago, Torvalds stepped back from running the Linux development community. In a note to the Linux Kernel Mailing List (LKML), Torvalds said, "I need to change some of my behavior, and I want to apologize to the people that my personal behavior hurt and possibly drove away from kernel development entirely. I am going to take time off and get some assistance on how to understand people's emotions and respond appropriately."
  • Linus Torvalds is back in charge as Linux kernel 4.19 is released
    After taking some time out from the Linux community to "change some of [his] behavior", Linux Torvalds is back. In a post to the Linux Kernel Mailing List announcing the release of Linux kernel 4.19, Greg Kroah-Hartman -- his temporary replacement -- handed back the reins. After writing about the changes to be found in the latest release, Kroah-Hartman signed off by saying: "Linus, I'm handing the kernel tree back to you. You can have the joy of dealing with the merge window :)".
  • Linux Kernel 4.19 “People’s Front” Released; Linus Torvalds Back For 4.20 Development
    The incidents that preceded (and accompanied) the Linux kernel 4.19 development cycle have has been one of the most critical ones faced by the Linux community. In order to bring some major changes to the community, Linus Torvalds took a break from kernel development and passed the baton to Greg Kroah-Hartman. A new Code of Conduct was also adopted. Now, after eight release candidates, Greg has released the Linux kernel 4.19. Underlining the ongoing challenges, he wrote in the release post: “It’s been a long strange journey for this kernel release…”
  • [Old] With Linux’s founder stepping back, will the community change its culture? [Ed: Bill Gates-connected site really sticking it in to Torvalds. Just watch carefully who wants him out and why. LF kicked community members out of the Board, gave seats there to Microsoft. So Microsoft now has more influence over the future/direction of Linux than community members (i.e. not large corporations).]
  • Intel's IWD Linux Wireless Daemon Out With Version 0.10
    IWD continues maintaining a very small footprint in order to be suitable for embedded/IoT use-cases with having minimal dependencies though supporting networkd/NetworkManager/ConnMan if present on the system. With the new IWD 0.10 release is support for using an external Embedded Linux Library (ELL). The ELL library is another open-source Intel project providing low-level functionality for Linux system daemons and having no dependencies in turn other than the Linux kernel and C standard library. ELL can scale up from embedded to desktop systems and more while providing a lot of features around D-Bus, signal handling, crypto, and other tasks.

Linux 4.19

  • Linux 4.19
    Hi everyone! It's been a long strange journey for this kernel release... While it was not the largest kernel release every by number of commits, it was larger than the last 3 releases, which is a non-trivial thing to do. After the original -rc1 bumps, things settled down on the code side and it looks like stuff came nicely together to make a solid kernel for everyone to use for a while. And given that this is going to be one of the "Long Term" kernels I end up maintaining for a few years, that's good news for everyone. A small trickle of good bugfixes came in this week, showing that waiting an extra week was a wise choice. However odds are that linux-next is just bursting so the next -rc1 merge window is going to be bigger than "normal", if there is such a thing as "normal" for our rate of development. And speaking of development, there's that other thing that happened this release cycle, that ended up making it such that I'm the one writing this instead of Linus. Allow me the guilty pleasure of taking a few minutes to talk about that.... I've been giving my "How the kernel is developed" talk all around the world for over a decade now. After the first year or so, I was amazed that it kept needing to be given as surely everyone knew how we did this type of thing, right? But my wife, someone much smarter than I, then told me, "Every year there is a new kindergarten class." And we all need to remember that, every year new people enter our community with the goal, or requirement, to get stuff done for their job, their hobby, or just because they want to help contribute to the tool that has taken over the world and enabled everyone to have a solid operating system base on which to build their dreams. And when they come into our community, they don't have the built-in knowledge of years of experience that thousands of us already do. Without that experience they make mistakes and fumble and have to learn how this all works. Part of learning how things work is dealing with the interaction between people, and trying to understand the basic social norms and goals that we all share. By providing a document in the kernel source tree that shows that all people, developers and maintainers alike, will be treated with respect and dignity while working together, we help to create a more welcome community to those newcomers, which our very future depends on if we all wish to see this project succeed at its goals. And that goal we all share is the key here. We _ALL_ want to create the best kernel that we possibly can. We can disagree on lots of different things in other parts of our lives, but we do share this one thing. And we should focus on that shared goal as it has pulled us all together in a way that has enabled us to create something that no other company or group of people has ever been able to accomplish. We used to joke that our goal was "Total World Domination", but it really wasn't a joke. We achieved that goal, Linux really does rule the world. All companies use it, contribute to it, and it has ended up making the world a much better place because of all of us working on it. In these talks I give, I also say that "the only thing that can stop us is ourselves, it is up to us to mess this up." And that's truer now than when I first started saying that a decade ago. There is no other operating system out there that competes against us at this time. It would be nice to have something to compete against, as competition is good, and that drives us to do better, but we can live with this situation for the moment :) These past few months has been a tough one for our community, as it is our community that is fighting from within itself, with prodding from others outside of it. Don't fall into the cycle of arguing about those "others" in the "Judean People's Front" when we are the "We're the People's Front of Judea!" That is the trap that countless communities have fallen into over the centuries. We all share the same goal, let us never loose sight of that. So here is my plea to everyone out there. Let's take a day or two off, rest, relax with friends by sharing a meal, recharge, and then get back to work, to help continue to create a system that the world has never seen the likes of, together. Personally, I'm going to take my own advice. I'll be enjoying this week in Edinburgh with many other kernel developers, drinking some good whiskey, and taking some time off of reading email, by spending it with the great friends I have made in this community. And with that, Linus, I'm handing the kernel tree back to you. You can have the joy of dealing with the merge window :) thanks, greg k-h
  • The 4.19 kernel is out
    Greg Kroah-Hartman has released the 4.19 kernel. Headline features in this release include the new AIO-based polling interface, L1TF vulnerability mitigations, the block I/O latency controller, time-based packet transmission, the CAKE queuing discipline, and much more.
  • Greg KH Releases Big Linux 4.19 Kernel, Codenamed "People's Front"
    Greg Kroah-Hartman went ahead and released the Linux 4.19 kernel. When releasing the Linux 4.19 kernel, he quietly changed the codename to "People's Front" -- a nod to the Code of Conduct happenings and more that have shook the kernel community the past several weeks. Greg did note that Linux 4.19 is larger than the past three kernel releases. In terms of why it's so big, see our Linux 4.19 feature overview.