Language Selection

English French German Italian Portuguese Spanish

Just talk

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.

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.

Koalas Need Our Help

Filed under
Just talk

Koalas Need Our Help

Watching videos/photos of Koalas being rescued from a charred/burning forests in Australia is heart-breaking and devastating. More than 350 Koalas are reported being dead and these numbers are growing. Those who live far from Australia (just like me) can't help physically rescue them, but a small amount of money/donation to sustain the hospital/facilities, volunteers and rescuers is of great help. Koala is just one of the many species that perish from the bushfire and they need our help, so please donate through the GoFundMe page and through other legitimate websites. Help those who support animal welfare.

Twins for Meng Meng and Jiao Qing

Filed under
Just talk

Meng Meng

About 8 months ago we had the chance to meet Meng Meng (above) and Jiao Qing, the female and male pandas on loan to Berlin Zoo in Germany. I took lots of photos with them and we stayed in their Pagoda sanctuary a little longer. Seeing them eating, napping and wandering inside their secured place brings joy to my heart. I don't really like seeing animals in the zoo, but if this is the only way to keep and protect them from any harm or from becoming extinct, then so be it. Today, in the news (video) the two adorable pandas became parents as they were having twins; this is good news and I'm so happy for them both. To Meng Meng and Jiao Qing (and also to Berlin Zoo), congratulations!

Slack: It Used to Be a GNU/Linux Distro, Now It's Surveillance Capitalism

Filed under
Just talk

I like "Freedo" (a symbol for freedom) better

Freedo

THE meaning of words can change over time, along with connotations that accompany these words. A little cat, for example, we can no longer call "pussy" and the word "gay" rarely means happy (colloquially). What about "Slack"?

Once upon a time I knew Slack as a solid, freedom-respecting distribution (GNU/Linux distro), whereas nowadays it is something to be stubbornly avoided as it threatens my freedom. It's technically spyware. It is a threat to everybody's freedom because of the network effect. When we use it we participate in a viral campaign of unwanted societal dependency. We help it spread exponentially. Like disease amongst anti-vaxxers. Richard Stallman had spoken about it in the context of Skype long before Microsoft entered the fray/picture. That's just common sense. The requirement of opening a Slack account to interact with other people is like the equivalent of an employer demanding the applicant has a Facebook account (despite all that is known about Facebook's incredible abuses). It can harm our neighbours, colleagues, family and friends as much as it harms ourselves.

As a little bit of background/context/polite remarks on this, I had been writing about Slack (the spyware, not the distro) for several years -- years before the prospects of actually using it. I never ever used it, but I know about it technically, from various angles (not just the shallow, user-centric end). Slack is proprietary at the front end and the back end. Only Slack employees know for sure what it does (and may do in the foreseeable future, as per secret roadmaps). They cannot speak out about it, for fear of retribution (so they're inherently gagged by fear over mortgage etc. or self-restraint that defies logic/ethics). Stallman has long warned about the morality of such circumstances and the ideology they breed. It was recently discovered that Facebook had targeted its critics (a huge number of them), subjecting them to Stasi-like treatment not for any government but for a private corporation, namely Facebook. It had been 'hunting' people using dubious and shallow justifications/pretexts. Nobody has yet been held accountable. Negative press has been the only cost/toll, so they got away with it with barely even a slap on the wrist. Others may imitate them, seeing that there are no fines, no arrests, no sanctions.

A colleague told me several months ago that someone at our company wanted to experiment with Slack; there was no final decision about it, so I assumed it was like our RT/OTRS 'dance' (choice of ticketing system half a decade ago). Sometimes we explore FOSS options/alternatives, which is a good thing! He sent me an invite, but he wasn't assertive about me joining as it was still an experimental thing (as I understood it back then, based on what I was told; I'll come to that in a moment). I thought we would, if it got adopted, still have options (duality). One colleague (at least) wasn't even sent an invite, so I took that as a sign of the adoption's semi-hearted nature (at the time). My colleagues never mentioned it since, except one person (who apparently liked Slack). Another colleague wondered why nobody had told her about it; as if she was left out, but she's happily using Kopete on KDE, so on she went with Jabber.

I've long been writing about Slack, maybe about 15 years (even when the name referred to a Live GNU/Linux distro, well before the name got 'hijacked'; it's Debian-based, it still has regular releases a few months apart, not the same as Slackware despite the names' similarity; BoycottNovell made a Slack-based distro called SUEME Linux 12 years ago); Tux Machines publishes announcements of Slack releases several times a year, but it's always about the distro. It's a European distro with pedigree; but I digress..

Nowadays "Slack" means something different; in a technical context, people no longer recognise it as the distro's name; Slack is now the darling of corporate media; myself and others could never quite explain why (we were rather baffled as it did not seem particularly innovative and we thus attributed most/all the press coverage to good marketing/PR); the name collision also raised legal questions because Slack is a well-known distro and the name is strictly used in the domain of software; it has been used for decades. Now the distro's development team needs to explain to people what came first and how this confusion came about.

OK, so now Slack is enjoying a valuation at $billions (as per very recent news headlines), with IPO rumours floated as well (making it easier to buy/subvert). Slack is relatively new a player/contender; it goes about 3-4 years back (in the mainstream), around the time we were in Alton Towers. I still remember that based on other events. Privacy activists had been warning about it and recently I kept seeing (also publicly writing about) more red flags. Slack, the company, is getting more invasive over time. It's like Facebook. Facebook for business. LinkedIn got picked by Microsoft, along with all that data (NSA PRISM comes to mind). Personal messages, passwords, social graphs, employment records and so on. Even location (picked every 60 seconds or so from one's phone through the 'app'). Same for Skype, which Microsoft added to PRISM just months after buying it (Microsoft was first in PRISM, based on Snowden's leaks -- it was one among the first stories to come out/emanate). Far less opinionated people than myself have blasted Slack for a variety of reasons. Some tweets of mine about it go ~3 years back (warning for 'opinionatedness'... I don't mince words much).

I still remember having to install Skype on an old phone for one company meeting. Back then the mere installation (for one hour, then deleted) meant sending Microsoft entire address books, entire call history and more. This phone of my wife is 7+ years old, so that's a lot of data, going a long way back. That's their business model. I'm usually apprehensive because some of my sources, e.g. for exclusive articles in Techrights (I published my 25,000th article last week in Techrights!), are named in files on my system. I'm no Free software 'purist' per se (I use proprietary drivers sometimes), but "Slack would be the surveillance capitalism competitor to Jabber," to quote something I read yesterday. They digest information, including corporate communications. There's a certain risk associated with this, including competitive risk. As a Free software-based company I think it's important to demonstrate that every piece of proprietary framework can be swapped with FOSS. There are quite a few Slack equivalents that are FOSS; a colleague told me that another colleague had brought some of these up. We might examine these soon, maybe test and adopt these. Time will tell. Maybe I'll write about some of these.

I am also reading about bridges between protocols that enable access to Slack, but yesterday when researching it I found that Slack is gradually burning these bridges/gateways. Not entirely surprising, as once they get to a certain point/market share they up/boost the lockin. Naturally. More so if they have obligations to shareholders. Twitter did this last August, shutting out all third-party apps/APIs for the first time ever (in the company's entire existence). Many of us were devastated because we had built interaction tools, custom-made around these APIs). So, basically, whatever a centralised platform gets adopted, we can always lose control as they can change everything they want at any time. Even, at worst, some company can just buy them for the data; they can start charging a lot, they can shut down, change ToS etc.

The bottom line is, Slack ought to be avoided. It's worse than proprietary because it's all centralised, even the data. There's no concept such as "private" or "privacy". These are only illusions.

Unixstickers

Filed under
Just talk

Unixstickers

Awesome products, will definitely get another bunch of some more stickers soon Smile

GitHub as the Latest Example of Microsoft Entryism in Free/Libre Software

Filed under
Just talk

"This is in effect the very same trick they did/pulled with Novell and SUSE (where Nat Friedman came from after his Microsoft internship) about a decade ago."

Postman

THE recent GitHub takeover, which has not formally been approved just yet (although there are no foreseen barriers to it), is definitely bad news; it is a lot of things to Microsoft however. It is good news only to Microsoft and GitHub shareholders, who basically sold out many developers without rewarding/compensating them for this unwanted (to them) takeover.

There are many aspects to it: First of all, it helps paint Microsoft as "open source" and it helps Microsoft gain leverage over developers, e.g. their choice process of framework/s and licence/s (Microsoft still dislikes copyleft); by leverage over platform they can suggest Azure, for example, or create bindings to it; they gain leverage over projects tied to governments, including some of our clients at work; Microsoft can vainly tell them, i.e. the governments and their developers: "look, you want FOSS? We're FOSS" (so they effectively become their own competitor!). In fact, there's so much more and I could easily name a couple dozen examples, but I know people pursue/need concision here. For an analogy, in politics this concept or strategy is known as "entrism" or "entryism".

Microsoft also uses patents to blackmail FOSS; there's that element too, albeit many people conveniently choose to forget it. Microsoft is sending patents to patent trolls, then offers "Azure IP Advantage". This is in effect the very same trick they did/pulled with Novell and SUSE (where Nat Friedman came from after his Microsoft internship) about a decade ago.

There are many other angles to it, including programming languages, frameworks (e.g. proprietary IDEs like MSVS), code editors and not just bindings to Microsoft as a host and API provider. People, especially developers of software, generally know how E.E.E. works; the basic precondition/premise is that you gain controls/leverage over that which threatens you (Nokia: Elop, Novell: Mono and lots more examples). So that's kind of a way of getting inside, gradually forming a partnership and then shutting down or sidelining whatever threatens you. Like Xamarin did to RoboVM, in effect killing it under Friedman's leadership. Friedman is going to be the chief of GitHub.

Microsoft can direct the opposition's decisions and its fate. Sadly, they already do this inside the Linux Foundation, where Microsoft staff already has chairs in the Board.

From what I can gather, developers ditching GitHub is becoming a fairy common thing this month. I already see the 1) active 2) large 3) non-Windows ones leaving, but it can take time; some told me they still rely on open bug reports and other 'vendor lockin'; that needs some work before they can migrate; the real alternative is self-hosted git.

"Sadly, they already do this inside the Linux Foundation, where Microsoft staff already has chairs in the Board."

In Memoriam: Robin "Roblimo" Miller, a Videographer and Free Software Champion

Filed under
Just talk

Videographer Robin Roblimo Miller

Robin "Roblimo" Miller was a clever, friendly, and very amicable individual who everyone I know has plenty of positive things to say about. I had the pleasure of speaking to him for several hours about anything from personal life and professional views. Miller was a very knowledgeable person whose trade as a journalist and video producer I often envied. I have seen him facing his critics in his capacity as a journalist over a decade ago when he arranged a debate about OOXML (on live radio). Miller, to me, will always be remembered as a strong-minded and investigative journalist who "did the right thing" as the cliché goes, irrespective of financial gain -- something which can sometimes be detrimental to one's longterm health. Miller sacrificed many of his later years to a cause worth fighting for. This is what we ought to remember him for. Miller was - and always will be - a FOSS hero.

May everything you fought for be fulfilled, Mr. Miller. I already miss you.

Syndicate content

More in Tux Machines

Security, Internet and Containers

  • Security updates for Tuesday

    Security updates have been issued by CentOS (dnsmasq, net-snmp, and xstream), Debian (mutt), Gentoo (cfitsio, f2fs-tools, freeradius, libvirt, mutt, ncurses, openjpeg, PEAR-Archive_Tar, and qtwebengine), openSUSE (chromium, mutt, stunnel, and virtualbox), Red Hat (cryptsetup, gnome-settings-daemon, and net-snmp), Scientific Linux (xstream), SUSE (postgresql, postgresql12, postgresql13 and rubygem-nokogiri), and Ubuntu (mutt). 

  •  
  • WordPress security & hardening, the definitive guide

    WordPress is massively popular. Around every one in five sites on the Internet uses WordPress in some form. Be that to run a humble blog, or a multi-site Content Management System (CMS) or eCommerce site. As a result, it is no surprise that WordPress websites are a very popular target for both experienced hackers and script-kiddies alike. The last thing any webmaster wants is to find out that their website has been hacked; maybe taken hostage and is part of a botnet, spreading malware, or partaking in Denial of Service (DoS) attacks. In this article we’ll be sharing a number of tips and strategies to help you harden your WordPress website.

  • The Mozilla Blog: Why getting voting right is hard, Part V: DREs (spoiler: they’re bad)

    This is the fifth post in my series on voting systems (catch up on parts I, II, III and IV), focusing on computerized voting machines. The technical term for these is Direct Recording Electronic (DRE) voting systems, but in practice what this means is that you vote on some kind of computer, typically using a touch screen interface. As with precinct-count optical scan, the machine produces a total count, typically recorded on a memory card, printed out on a paper receipt-like tape, or both. These can be sent back to election headquarters, together with the ballots, where they are aggregated.

  • Jessica Rosenworcel’s appointment is good for the internet

    With a new year comes change, and one change we’re glad to see in 2021 is new leadership at the Federal Communications Commission (FCC). On Thursday, Jan. 21, Jessica Rosenworcel, a longtime FCC commissioner, was appointed as acting chair. It’s an important role that will drive policy discussions affecting the internet and all of us who use it. Her appointment gives us hope that under her wing, the agency will develop strong policies that look out for everyday people. Here are a few reasons Jessica Rosenworcel’s appointment is good for the internet. [...] We look forward to working with the FCC to reinstate net neutrality protections and close the digital divide. Jessica Rosenworcel’s ascent to acting chair of the FCC bodes well for the future of both issues. And we can imagine a brighter future for a healthy internet if she were to be nominated for the role permanently.

  • Compute confidently at the Edge with Rancher and Longhorn 1.1 | SUSE Communities

    Today’s announcement of Longhorn 1.1, a Cloud Native Computing Foundation (CNCF) Sandbox project, is exciting news for users of Rancher, SUSE’s Kubernetes management platform and the Kubernetes community. Longhorn is an enterprise-grade, cloud native container storage solution that went GA in June 2020. Since then, adoption has increased by 235 percent. Now Longhorn is the first cloud native storage solution designed and built for the edge, with ARM64 support, new self-healing capabilities and increased performance visibility.

  • Longhorn 1.1 Offers ‘ReadWriteMany’ Support Across Containers

    SUSE has announced the release of Longhorn 1.1 which allows DevOps teams to manage persistent data volumes in any Kubernetes environment while bringing an enterprise-grade but vendor neutral approach to cloud-native storage.

Free Software Leftovers

  • Ingo Juergensmann: Migrating from Drupal to WordPress

    If you can read this on planet.debian.org then migrating my blog from Drupal to WordPress was successful and the feed has been successfully changed by the Debian Planet Maintainers (thanks!). I’ve been a long term Drupal user. I think I started to use Drupal since it was included in Debian. At some point Drupal was removed from Debian and I started to use Serendipity instead. Later Drupal was included in Debian again and I moved back to Drupal. I think this must have been around Drupal 4 or Drupal 5. No idea. I even became active in the Drupal community and went to one of the first Drupal barcamps in Germany, namely in Cologne. This was shortly before Dries Buytaert started a business off of Drupal and went to the USA. I met with many devs of Drupal in Cologne and enjoyed the community and started with others a local Drupal User Group in Rostock. [...] So, after all the years my Drupal journey will come to an end. It was a long time with you. Sometimes joyful, sometimes painful. I wish you all the best, Drupal!

  • The round-the-world trip to fix a bug

    Mrs. Vera Cavalcante (@veracape), from Brazil, a long-time contributor for the Portuguese documentation on LibreOffice, was reviewing the translation of the Calc Guide and double-checking the translated text, with respect to the current user interface and the Help pages. Vera noticed that the Help pages on conditional formatting were not correct any more, and reported in the Brazilian team Telegram group (Bugzilla is still very hard for non-native English speakers).…

  • Red Kubes Container Platform Flies Open Source Flag

    Red Kubes, a Dutch-based startup, open sourced a free community edition of its Otomi Container Platform in a bid to remedy the ongoing complexity surrounding Kubernetes configurations. The scalability, agility, and speed-to-market advantages that Kubernetes offers have been handsome enough to capture a growing share of the enterprise market, but this very strength can become an Achilles heel for container deployments. In this sense, it’s far too easy – and common – to create thousands or even tens of thousands of containers across applications. Not only does this create an operational money pit, but management becomes a herculean feat to any container newbie.

  • The Apache Software Foundation Announces Apache® ECharts™ as a Top-Level Project

    The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of more than 350 Open Source projects and initiatives, announced today Apache® ECharts™ as a Top-Level Project (TLP). Apache ECharts is an intuitive, interactive, and powerful charting and visualization library ideally suited for commercial-grade presentations. The project originated in 2013 at Baidu and entered the Apache Incubator in January 2018.

  • Shots fired in disputes over OSS-as-a-Service

    Cloud services are the great disruptor of both IT organizations and vendors, and wrapping open source software around a service is the latest flashpoint. The open source development model has proven to be an incredible incubator of innovative software by democratizing and distributing the conception, design, implementation and debugging of new titles, advantages that were thoroughly explored more than two decades ago in the book, The Cathedral and the Bazaar. Although open source has since been adopted, encouraged and sponsored by every major software company, its origins were decidedly non-commercial with utopian overtones of liberating code from the tyranny of proprietary shackles. The earliest open source projects, notably Gnu Emacs and other tools from the Gnu Project, embraced this idealistic ethos with a restrictive, comprehensive license, GPL, that applies to derivative work using the code.

  • AWS to Fork Elasticsearch as Elastic Moves Away from Open Source

    Elastic’s license change from open source ALv2 to SSPL appears to have moved Amazon Web Services to “launch new forks of both Elasticsearch and Kibana.” Elasticsearch’s move towards the more restrictive Server Side Public License has already begun to ruffle feathers among developers.

Programming Leftovers

  • Excellent Free Tutorials to Learn Tcl - LinuxLinks

    Tcl (Tool Command Language) is a dynamic programming/scripting language based on concepts of Lisp, C, and Unix shells. Here's our recommended free tutorials to learn Tcl.

  • ROC and Precision-Recall curves - How do they compare?

    Both curves offer two useful information: how to choose the positive class prediction threshold and what is the overall performance of the classification model. The former is determined by selecting the threshold which yield the best tradeoff, in adequation with the prediction task and operational needs. The latter is done by measuring the area under the curves which informs about how good the model is, because by measuring the area under the curves, one computes the overall probability that a sample from the negative class has a lower probability than a sample from the positive class. With scikit-learn, the values can be computed either by using the roc_auc attribute of the object returned by plot_roc_curve() or by calling roc_auc_score() directly for ROC curves and by using the average_precision attribute of the object returned by plot_precision_recall_curve() or by calling average_precision_score() directly for PR curves.

  • Write GIMP scripts to make image processing faster | Opensource.com

    Some time ago, I wanted to give a blackboard-style look to a typeset equation. I started playing around with the GNU Image Manipulation Program (GIMP) and was satisfied with the result. The problem was that I had to perform several actions on the image, I wanted to use this style again, and I did not want to repeat the steps for all the images. Besides, I was sure that I would forget them in no time.

  • Bash wait Command | Linuxize

    wait is a command that waits for the given jobs to complete and returns the exit status of the waited for command. Since the wait command affects the current shell execution environment, it is implemented as a built-in command in most shells. In this article, we’ll explore the Bash built-in wait command.

  • Santiago Zarate: Cron do not send me empty emails
  • Rust & the case of the disappearing stack frames | Inside Rust Blog

    Now that the FFI-unwind Project Group has merged an RFC specifying the "C unwind" ABI and removing some instances of undefined behavior in the "C" ABI, we are ready to establish new goals for the group. Our most important task, of course, is to implement the newly-specified behavior. This work has been undertaken by Katelyn Martin and can be followed here.

Open Hardware: Raspberry Pi, Arduino, Thomas Petazzoni (Bootlin) on Training

  • Qsync fixed on the Pi4 and FF compiled

    The Raspberry Pi4 does not have a hardware battery-backed clock, so relies on getting the date and time from an Internet time server. In EasyOS, Qsync is the utility that does that. At first bootup, QuickSetup has a checkbox to enable getting time from the Internet, which will launch Qsync. At first bootup on the Pi4, if you are going to connect to Internet via wifi, not ethernet, then there won't be an immediate Internet access. No problem, Qsync will run once the Internet connection is established. Qsync will run just once at bootup and after Internet connection. That's fine, but I couldn't understand why it would suddenly stop working. Then discovered that /etc/init.d/qsync was getting its executable-flag cleared.

  • Arduino Blog » This children’s console looks like something straight out of a superhero’s lair

    Kids have wonderful imaginations, and to help students at a primary school have a super time, creator “palladin” was asked to construct a console for them to use. The device features a variety of lights and sci-fi additions, including glowing “reactor” tubes that diffuse light using hair gel and a “memory bank” that emits flashing patterns for a 1950s supercomputer look.

  • Arduino Blog » This pen plotter draws detailed maps the size of walls

    Christopher Getschmann wanted a wall-sized map of the world. He soon realized, however, that it’s tough to actually buy such a map that’s both beautiful and detailed enough to satisfy his cartographic tastes. While many would simply move on to the next “thing,” Getschmann instead took things into his own hands, and built a pen plotter specifically to draw massive 2×3 meter map for his wall.

  • New training course: embedded Linux boot time optimization

    For many embedded products, the issue of how much time it takes from power-on to the application being fully usable by the end-user is an important challenge. Bootlin has been providing its expertise and experience in this area to its customers for many years through numerous boot time optimization projects, and we have shared this knowledge through a number of talks at several conferences over the past years. We are now happy to announce that we have a new training course Embedded Linux boot time optimization, open for public registration. This training course was already given to selected Bootlin customers and is now available for everyone.