Language Selection

English French German Italian Portuguese Spanish

Blogs

Migrating TuxMachines to a Bigger Server

Filed under
Site News

We are in the process of moving the TuxMachines Web site to a better server with more capacity and better hardware. There may be temporarily odd behaviour on the site (if data is accessed which is out of date).

How can I Identify who SSH into my Linux System?

Filed under
Linux

Identifying who has logged into your system in Linux is way easier than the Windows Operating System.

In Linux System whenever someone tries to log in using SSH is recorded by the log file, the log file is located in /var/log/auth.log. location can be different in other distribution.

If you not found the auth.log file in your system try to execute the below command to view the log from systemctl.

journalctl -u sshd |tail -100

  • -u (Show the user journal for the current)
  • sshd (SSH user created by system by default)
  • tail -100 (Print top 100 result from log file)

journalctl of sshd
User logged in using SSH

Read more

Monitoring Tux Machines With Apachetop, Nmon and Htop

Filed under
Site News

Monitoring Tux Machines

Summary: A little glimpse at how we monitor this site for DDOS attacks and general performance, especially now that DDOS attacks have already become pervasive and routine (Apachetop helps identity attack patterns and visual, colourful alerts are triggered in Nmon and Htop)

Malicious Bots

Filed under
Site News

Choking on bots, cannot cope

TUX MACHINES may seem to have become rather slow if not unreachable at times. Over the past few months we've had issues with bots that request as many as 10,000 files per minute from the site's server, which is obviously unable to cope with the load/bandwidth and actually deliver what's requested. Sometimes it even resets Apache in order to regain order. At the moment we lack a permanent solution, but we have some mitigations in place.

More than 5 years ago we had to stop new account sign-ups due to spammers setting up loads of dummy accounts (hundreds per day), then directing these to vandalise the site. This inevitably led to tighter control from an editorial perspective and it reduced the number of comments.

Running a site is no picnic; it's a 24/7 responsibility. We do the best we can to maintain a reliable service whilst at the same time also pursuing the latest news stories of interest. This takes a huge amount of time and dedication.

If it is difficult to reach the site or if the site feels very slow, it's almost definitely due to those bots. The server's uptime is now 160 days.

Microsoft Loves Painting Apple (or "GAFA") as the Problem

Filed under
Just talk

Mask Me No Questions: The 'new' Microsoft; Mask Me No Questions

Summary: The latest twist in Microsoft's PR strategy is, divert attention and blame to other companies [1,2], even if their alleged abuses are in fact a copy of Microsoft's own

  • Microsoft Backs Epic’s Apple Battle on Game Technology Access

    The graphics technology, known as Unreal Engine, is a suite of software used by millions of developers to build 3-D games and other products. Cutting off Epic from Apple’s iOS and Mac developer tools would mean the gaming company can no longer distribute Unreal Engine to other developers, Epic said in its legal filing. Microsoft, which makes the Xbox, uses the technology for games developed for consoles, PCs and mobile devices.

  • Microsoft Supports Epic Games, Says Apple Blocking Access to Unreal Engine Would Harm Game Creators

    In a declaration in support of Epic Games [PDF], Microsoft gaming executive Kevin Gammill wrote that "Apple's discontinuation of Epic's ability to develop and support Unreal Engine for iOS or macOS will harm game creators and gamers." Specifically, Gammill said that games utilizing Unreal Engine will be put at a "substantial disadvantage," citing Microsoft's own racing game Forza Street for iPhone and iPad as an example.

Kangaroo on protest

Filed under
Humor

140,000 Reached

Filed under
Site News

Clock

THIS may be hard to believe, but after more than 16 years we've managed to put together 140,000 Drupal nodes (this one is the 140,000th). Most of these are news clippings and clusters of links. The rest are pages, blog posts and forum threads.

The next meaningful milestone will be the 150,000th node and our 20th anniversary (some time in 2024). We're quite certain we'll get there, along with 200,000 nodes, as this past week we've been in the region of all-time record traffic.

Susan is still involved sometimes, albeit behind the scenes. We thank her enormously for all the work she did.

3 Months From Home

Filed under
Site News

TM setup portrait


TUX MACHINES has been run from one single place over the past 3 months because of the COVID-19-induced lock-downs. We no longer travel far from home (it's impractical)... and we both work from home anyway.

The prolonged shut-down of businesses (they only reopened a fortnight ago) resulted in lack of access to some digital necessities, but that almost always meant more free time to rethink and reassess the workflow and the workspace with existing hardware (reshuffling what we already have, both new and old).

Last month I showed how the screens on my desk were split to handle multi-tasking. Last week I shuffled to portrait mode (as shown above). Rianne too uses 2 or 3 screens, but her setup is somewhat simpler. We basically both use a combination of RSS readers. I mostly use QuiteRSS and she uses Thunderbird and QuiteRSS in conjunction (best of both worlds). We're still hoping that an intern based in Africa will start participating soon. The pandemic has made access to the Internet a lot harder for him. He wants to cover programming and Web-related topics for us.

Message From the Editors

Filed under
Site News

Roy and Rianne

Summary: We're still running the site 24/7 every day/week of the year; we're managing to cope with slower news cycles

WE RECENTLY passed the sixteenth anniversary of this site, which is peaking in terms of traffic (record levels and all-time highs for several consecutive weeks). This weekend is very, very slow for news. Very.

We're typically managing to cope with the decline of journalism by digging deeper, finding lesser known sites such as blogs. We're hoping to reach the twentieth anniversary of the site. That's 2024.

Star Trek Thanksgiving: Did I tell you the joke about the flightless bird? Oh, don't get started, Worf... turned out it was a machine

For those who don't follow over RSS feeds (default and recommended as there are no middlemen; access is direct) there are also Twitter (proprietary) and the following accounts in Free software-based networks. Diaspora:

Diaspora logo

Mastodon:

Mastodon logo

Pleroma (Fediverse like Mastodon):

Pleroma logo

Thanks for choosing Tux Machines for news.

Sweet Sixteen

Filed under
Site News

Exuberant dog

TUX MACHINES is turning 16 today. Yes, 16. Not many sites last this long.

The interesting thing is, this past week we had an all-time traffic record and the same is true for the week prior. So for two weeks in a row, despite relatively slow news, we broke a record.

We aren't celebrating the birthday this year (we're still restricted in what can be done here, due to the virus), but maybe next year we'll do something and even share some photos.

Variscite Rises to Platinum Member of NXP Partner Program

Filed under
News

Variscite and NXP are taking their partnership to the next level with the promotion of Variscite to become a Platinum Member of NXP’s Partner Program.

Official Launch of Variscite’s i.MX8X System on Module

Filed under
News

Variscite has re-launched its VAR-SOM-MX8X System on Module, based on the i.MX8X processor with the latest NXP’s qualified silicon for full production. The SoM expands Variscite’s VAR-SOM Pin2Pin product family and offers built-in safety features, highly integrated multimedia support, and efficient power/performance architecture.

Peaking Again

Filed under
Site News

Summary: In terms of number of daily nodes, we're at the pinnacle still (despite slow news at times of lock-downs)

Tux Machines is turning 16 exactly one month from now. We've decided to plot activity over time, as measured by number of posts/nodes. It's not the most important measure (e.g. original articles), but it's something that's not too hard to plot.

Attached to this post is tux-posts.txt, which can be converted into tux-numbers.txt as follows:

sed 's/[\t ][\t ]*/ /g' < tux-posts.txt | cut -d' ' -f3,5 >tux-numbers.txt

We can then plot it:

gnuplot -p -e 'plot "./tux-numbers.txt" with linespoints linetype 1 pointtype 2 linecolor 10'

And voila!

Plot tuxmachines posts

In a month from now we might buy a cake.

Running Tux Machines

Filed under
Site News

Roy's deskop

Roy's deskop and laptop

Roy's deskop and laptop with text

Running Tux Machines with my wife (the lead editor, I mostly sweep up and cluster related stories) is a hobby but it feels like a full-time job, a 24/7 job that involves picking and sorting news as quickly as possible, almost non-stop around the clock. My own workflow -- not speaking about Rianne's -- can be shown in this annotated photo, which I took a couple of hours ago. Readers might find it interesting, knowing roughly how the site is run from my side (not Rianne's). The office is at home of course, as we're both remote workers in the area of computing. We're like sysadmins for a living and maintaining Tux Machines helps keep us abreast of the latest technologies.

Turning 16 This Summer

Filed under
Site News

No crisis for the "tuxmachiners"

tuxmachines at whois

AS keen observers may be aware, bearing in mind last year's anniversary party (when such parties were still permitted), we're soon turning 16. There won't be a party or anything; not even online (it's pointless).

This past year has been our strongest and for whatever reason since the pandemic began (epidemic escalated and declared "pandemic"), then soon thereafter lock-downs were enforced, we saw another uptick in traffic. We don't spy on visitors, but we merely observe the size of Apache logs, which are then wiped for privacy reasons.

When Rianne and I took over the site in 2013 it had already flourished, thanks to the love of care of Susan. We continue curating the news, clustering together related reports. The list of blogs we syndicate continues to grow because the mainstream media perishes, leaving a vacuum for people who are eager to find timely information, such as distro reviews and howtos.

If you run a GNU/Linux-oriented blog in the English language that we do not link to (most likely because we're not aware of its existence), let us know in the comments, in IRC, or other contact means. We soon turn 16 and we're quite confident that we'll make it to 20 as well. At the moment, as of this month, we also do server upgrades and we hope to add SSL soon. We've already moved one of this site's databases to a separate container in Alpine Linux. We make improvements while maintaining the site's spirit and long tradition.

Stay home. Save lives.

100,000 Tweets

Filed under
Site News

@tuxmachines in Twitter
The @tuxmachines account in Twitter as of this morning

We have been on Twitter for nearly a decade. It's proprietary and centralised, but some of our audience comes from there. In the start of March we'll have posted our 100,000th tweet in Twitter. A milestone? Maybe for Twitter. We try to focus on our presence in Free/libre networks, such as Mastodon, Pleroma and Diaspora. We joined Pleroma a year ago and have more followers there than we have in Twitter. Spring is fast approaching, which means we soon turn 16.

In the face of an Orangutan

Filed under
Just talk

Orangutan

Mother of two species.

The camels' outcry

Filed under
Just talk

Camel

When a human doesn't know what to do and people don't know how to tackle the real issue, the animals are becoming the sacrifice. Billion of animals were lost to bushfires alone and millions are slaughtered every day, yet the audacity to kill the camels is astonishing. I wonder what would be the humans' reaction if the animals called for human culling. Think about it.

Why Tux Machines Occasionally Adds Editorial Comments

Filed under
Just talk

Editorials

Summary: Editorial remarks (or Editor's comments, "Ed" for short) play a role in highlighting potential inaccuracies -- and manipulations of the mind -- when those aren't so shallow and aren't abundantly obvious

Recently, and as lately as a few hours ago, Richard Stallman exchanged some messages and we might meet again in a few months (he is traveling to the UK). Stallman and I share a concern about neglect of truth and history; for instance, many GNU programs are nowadays dubbed "LINUX COMMANDS" (I saw one example of that just 2 hours ago) and people sometimes lose sight of the important goals, focusing on brands instead of philosophy, political aspects and so on.

"Sometimes we link to something which isn't entirely accurate or can be misleading."

I would like to take this moment, on the last day of this year, to explain where we stand on issues pertaining to software freedom. A few times in the past one reader bemoaned my editorial comments (marked "Ed"), which typically bemoan something about the cited article/s. Sometimes we link to something which isn't entirely accurate or can be misleading. One example of that is openwashing. Another rather common and increasingly ubiquitous example concerns Microsoft "loving" Linux (it actually loves Windows).

We live in a world with Public Relations and marketing agencies. They exist to mislead; they shape perceptions -- that's their business model! To blindly link to just anything online without commentary or curation would likely lead us astray. Truth does matter. Facts need to be checked. This is what Tux Machines strives to achieve; throwing the word "LINUX" into something like Google News would expose one to loads of cruft, irrelevant stuff, plagiarism, pure spam and sometimes intentional lies. With no human operator or editor just about anything can be dunked into search results, owing to SEO manipulation and mishandling of indexes. I've seen that for well over a decade. Automation just doesn't work; someone who understands the problem domain needs to assess things for quality and accuracy.

"To be fair, comments are open, so readers can respond."

My adult life (since age 18 or so when I became a GNU/Linux user) involved very hard work and lifelong activism for software freedom. Not everyone agrees with me and if sometimes I may say something readers disagree with (e.g. in editorial comments), then it's likely because I try to be realistic, not jingoistic. Moreover, no two individuals will agree on everything 100% of the time. That's inevitable. So some readers might dislike these editorial comments. To be fair, comments are open, so readers can respond.

At the moment, the way I personally see it, Free software is under a number of attacks. There are different types of attacks. I think Free software will endure regardless. On a more positive note, Free software is nowadays used everywhere, it's just not being called that ("Open Source" is the term corporate media prefers) and it has been leveraged as a low-cost 'cushion' for DRM, surveillance, militarism etc. Think of companies like Facebook and Netflix (GNU and Linux at their back ends). Is this what we strive for? Closed systems that are merely built upon Freedom-respecting stacks?

"At the moment, the way I personally see it, Free software is under a number of attacks."

Software freedom is a huge objective in a world where almost everything becomes digital (only more so over time). I think it's up to us to somehow guide the world's software towards ethical uses, without necessarily imposing how it's used, and that is perhaps a future challenge for the Free Software Movement. It's a monumental challenge because politics can be a massive terrain to navigate. Over at Techrights I mostly focus on issues such as patents (laws), with emphasis on the U.S. Patent and Trademark Office (USPTO), the European Patent Office (EPO) granting software patents in Europe and so on. Patents on algorithms are one kind of barrier (among many) impeding Free software adoption.

The End of Tux Machines' Strongest Year

Filed under
Site News

Tux Machines 2020

TODAY is the last day of the last month of this year if not decade. We're pleased to close this year with record traffic levels. In 2019 we increased our coverage of programming-centric matters, especially when the underlying frameworks/languages were Free/libre software.

Earlier this year we also celebrated our 15th anniversary. There are three of us working behind the scenes to make the site up to date and keep it up (online). We're all passionate users of GNU/Linux who want to spread the word and encourage more people to use the platform.

In 2019 not only did we see record traffic levels; we also saw an unprecedented level of success for GNU/Linux in the adoption sense. Rianne is responsible for "Android leftovers" and remember that each Android device has Linux (or "Tux") in it. Google explored alternatives, but we haven't heard of these for months. It's nowadays very difficult to run a company or start a company without Linux -- no matter if in the server or device space. Let's hope Tux Machines will be around -- and online -- for many years to come. Happy new year.

Syndicate content

More in Tux Machines

EasyOS Dunfell 2.6.1 released for x86_64 PC

Yesterday announced EasyOS Dunfell 2.6.1 aarch64 for the Raspberry Pi4: https://bkhome.org/news/202101/easyos-dunfell-261-released-for-the-raspberry-pi4.html Today it is the turn for EasyOS Dunfell-series 2.6.1 64-bit on the PC. This is the first official release in this series. Same packages compiled in OpenEmbedded. Latest SeaMonkey 2.53.6. A different kernel for the PC build, 5.10.11. Read all about it here: http://distro.ibiblio.org/easyos/amd64/releases/dunfell/2.6.1/release-notes-2.6.1.htm As stated in the release notes, all three streams are being sync'ed to the same version number. The Buster-series 2.6.1 will probably be uploaded tomorrow. I have to compile the latest 5.4.x kernel, and SeaMonkey 2.53.6. As to which you would choose for the PC, it is like asking "which is better, strawberry icecream or chocolate icecream?" Read more

Top 20 Uses of Linux

The Linux OS and its related distros and flavors have transformed it from hardcore software into an industrial brand. Even if you are not a fan of it, the Linux OS might be as common as the air you breathe if you closely analyze your day to day interactive activities. Almost all the modern technologies that transform and innovate the tech industry have a Linux OS DNA imprinted on them. Those that are yet to be branded with their innovative uniqueness and recognition are waiting in line for the famed chance. Therefore, you might boldly claim that the Linux OS does not run your life, but the world around you cannot avoid the flirty pursuits of this open-source and free software. Nowadays, almost anything that can be described as cool is either pursuing Linux or is being pursued by Linux. It is the perfect symbiotic relationship in a world that tries to find a balance in technology and innovation. This article explores the awesomeness and outreach of the Linux OS in the world around us. It might even be an eye-opener for some of us to start taking our Linux skills to the next level. Top500 quotes Linux as the powerhouse or engine behind five-hundred fastest computers worldwide. I do not know of the speed of the computer composing this article or whether it qualifies to be among the listed five-hundred fastest computers worldwide. However, one thing is certain; it is 100% Linux DNA. On this note, let us start parading the top 20 uses of Linux. Read more

parted-3.4 released [stable]

Parted 3.4 has been released.  This release includes many bug fixes and new features. 
Here is Parted's home page: 
    http://www.gnu.org/software/parted/ 
For a summary of all changes and contributors, see: 
  https://git.savannah.gnu.org/cgit/parted.git/log/?h=v3.4 
or run this command from a git-cloned parted directory: 
  git shortlog v3.3..v3.4 (appended below) 
Here are the compressed sources and a GPG detached signature[*]: 
  http://ftp.gnu.org/gnu/parted/parted-3.4.tar.xz 
  http://ftp.gnu.org/gnu/parted/parted-3.4.tar.xz.sig 
Use a mirror for higher download bandwidth: 
  https://www.gnu.org/order/ftp.html 
[*] Use a .sig file to verify that the corresponding file (without the 
.sig suffix) is intact.  First, be sure to download both the .sig file 
and the corresponding tarball.  Then, run a command like this: 
  gpg --verify parted-3.4.tar.xz.sig 
If that command fails because you don't have the required public key, 
then run this command to import it: 
  gpg --keyserver keys.gnupg.net --recv-keys 117E8C168EFE3A7F 
and rerun the 'gpg --verify' command. 
This release was bootstrapped with the following tools: 
  Autoconf 2.69 
  Automake 1.16.1 
  Gettext 0.21 
  Gnulib v0.1-4131-g252c4d944a 
  Gperf 3.1 
Read more

Kernel: LWN's Latest and IO_uring Patches

  • Resource limits in user namespaces

    User namespaces provide a number of interesting challenges for the kernel. They give a user the illusion of owning the system, but must still operate within the restrictions that apply outside of the namespace. Resource limits represent one type of restriction that, it seems, is proving too restrictive for some users. This patch set from Alexey Gladkov attempts to address the problem by way of a not-entirely-obvious approach. Consider the following use case, as stated in the patch series. Some user wants to run a service that is known not to fork within a container. As a way of constraining that service, the user sets the resource limit for the number of processes to one, explicitly preventing the process from forking. That limit is global, though, so if this user tries to run two containers with that service, the second one will exceed the limit and fail to start. As a result, our user becomes depressed and considers a career change to goat farming. Clearly, what is needed is a way to make at least some resource limits apply on per-container basis; then each container could run its service with the process limit set to one and everybody will be happy (except perhaps the goats).

  • Fast commits for ext4

    The Linux 5.10 release included a change that is expected to significantly increase the performance of the ext4 filesystem; it goes by the name "fast commits" and introduces a new, lighter-weight journaling method. Let us look into how the feature works, who can benefit from it, and when its use may be appropriate. Ext4 is a journaling filesystem, designed to ensure that filesystem structures appear consistent on disk at all times. A single filesystem operation (from the user's point of view) may require multiple changes in the filesystem, which will only be coherent after all of those changes are present on the disk. If a power failure or a system crash happens in the middle of those operations, corruption of the data and filesystem structure (including unrelated files) is possible. Journaling prevents corruption by maintaining a log of transactions in a separate journal on disk. In case of a power failure, the recovery procedure can replay the journal and restore the filesystem to a consistent state. The ext4 journal includes the metadata changes associated with an operation, but not necessarily the related data changes. Mount options can be used to select one of three journaling modes, as described in the ext4 kernel documentation. data=ordered, the default, causes ext4 to write all data before committing the associated metadata to the journal. It does not put the data itself into the journal. The data=journal option, instead, causes all data to be written to the journal before it is put into the main filesystem; as a side effect, it disables delayed allocation and direct-I/O support. Finally, data=writeback relaxes the constraints, allowing data to be written to the filesystem after the metadata has been committed to the journal. Another important ext4 feature is delayed allocation, where the filesystem defers the allocation of blocks on disk for data written by applications until that data is actually written to disk. The idea is to wait until the application finishes its operations on the file, then allocate the actual number of data blocks needed on the disk at once. This optimization limits unneeded operations related to short-lived, small files, batches large writes, and helps ensure that data space is allocated contiguously. On the other hand, the writing of data to disk might be delayed (with the default settings) by a minute or so. In the default data=ordered mode, where the journal entry is written only after flushing all pending data, delayed allocation might thus delay the writing of the journal. To assure data is actually written to disk, applications use the fsync() or fdatasync() system calls, causing the data (and the journal) to be written immediately.

  • MAINTAINERS truth and fiction

    Since the release of the 5.5 kernel in January 2020, there have been almost 87,000 patches from just short of 4,600 developers merged into the mainline repository. Reviewing all of those patches would be a tall order for even the most prolific of kernel developers, so decisions on patch acceptance are delegated to a long list of subsystem maintainers, each of whom takes partial or full responsibility for a specific portion of the kernel. These maintainers are documented in a file called, surprisingly, MAINTAINERS. But the MAINTAINERS file, too, must be maintained; how well does it reflect reality? The MAINTAINERS file doesn't exist just to give credit to maintainers; developers make use of it to know where to send patches. The get_maintainer.pl script automates this process by looking at the files modified by a patch and generating a list of email addresses to send it to. Given that misinformation in this file can send patches astray, one would expect it to be kept up-to-date. Recently, your editor received a suggestion from Jakub Kicinski that there may be insights to be gleaned from comparing MAINTAINERS entries against activity in the real world. A bit of Python bashing later, a new analysis script was born.

  • Experimental Patches Allow For New Ioctls To Be Built Over IO_uring

    IO_uring continues to be one of the most exciting technical innovations in the Linux kernel in recent years not only for more performant I/O but also opening up other doors for new Linux innovations. IO_uring has continued adding features since being mainlined in 2019 and now the newest proposed feature is the ability to build new ioctls / kernel interfaces atop IO_uring. The idea of supporting kernel ioctls over IO_uring has been brought up in the past and today lead IO_uring developer Jens Axboe sent out his initial patches. These initial patches are considered experimental and sent out as "request for comments" - they provide the infrastructure to provide a file private command type with IO_uring handling the passing of the arbitrary data.