The Asus Eee: How Close Did the World Come to a Linux Desktop?

It was white, not much bigger than my hands held side by side, weighed
about as much as a bottle of wine, and it came in a shiny, faux-leather case. It
was the $199 Asus Eee 901, and I couldn’t believe that a computer could be
that powerful, that light and that much fun.

This is the story of the brief, shining history of the Asus Eee, the
first netbook—a small, cheap and mostly well-made laptop that dominated
the computer industry for two or three years about a decade go. It’s not so
much that the Eee was ahead of its time, which wasn’t that difficult in an
industry then dominated by pricey and bulky laptops that didn’t always have
a hard drive and by desktop design hadn’t evolved much past the first IBM
8086 box.

Rather, the Eee was ahead of everyone’s time. It ran a Linux
operating system with a tabbed interface and splashy icons, and the hardware
included wireless, Bluetooth, a webcam and an SSD hard drive—all in a
machine that weighed just 2.5 pounds. In this, it teased many of the concepts
that tech writer Mark Wilson says we take for granted in today’s cloud,
smartphone and Chromebook universe.

The Eee was so impressive that even Microsoft, whose death grip on the
PC world seemed as if it would never end, took notice. As everyone from Dell to
HP to Samsung to Toshiba to Sony to Acer to one-offs and “never-weres” raced
netbooks into production, Microsoft offered manufacturers a version of Windows
XP (and later a truncated Windows 7) to cram onto the machines. Because we
can’t have the masses running a Linux OS, can we?

“The Eee gave regular people something they couldn’t have
before”, says Dan Ackerman, a longtime section editor at CNET who wrote
some of the website’s original Eee and netbook reviews. “Laptops had
always been ridiculously expensive. The Eee wasn’t, and it gave regular
people a chance to buy a laptop that was smaller and more portable and that
they could be productive with. I always gave Asus credit—they understood
the role of form and function.”

Netbook History

The computer world never had really seen anything like the first Eee,
which didn’t even have a name when it was launched in 2007 (although it
later would be called both the 701 and the 4G). In fact, say those who reviewed the
701, it wasn’t so much a product but a proof of concept—that Asus
could make something that small and that cheap that worked.

There had been small laptops before, of course, like the Intel
Classmate PC and the OLPC X0-1, each part of the One Laptop per Child project.
But those were specialized machines designed to bring computing and the
internet to students throughout the world, and not necessarily consumer
products.

The netbook’s immediate predecessors were probably the palmtop and
the personal digital assistant, or PDA. These were handheld devices like the
Psion 7 and the HP Jornada 720 that did some computer things, including word
processing and email (and faxes in the late 1990s models). But they were slow
and under-powered (remember Windows CE?), and it wasn’t easy to work with the
tiny screens. In many ways, they were unsophisticated smartphones that
couldn’t make phone calls.

I used a Jornada 720 around the turn of the century. It was cheaper and
more reliable than my previous two laptops, which were buggy, crash-prone and
always seemed to have something wrong with the disk drive. I could sort of type
on the Jornada’s downsized QWERTY keyboard, and it synced with my desktop
(though the modem never really worked).

But the netbook’s true predecessor was almost certainly Radio
Shack’s legendary TRS-80 model 100—or as we lovingly called in in the
newspaper business, the Trash 80. It ran on Microsoft Basic and had a more or
less full-sized keyboard, a monochromatic screen that displayed about ten lines
of type and a 300-baud modem. The Trash 80 weighed about three pounds, and I
lugged it to football games, bike races and city council meetings in the late
1980s. There, I would write the story, hook the modem up to a phone jack
(acoustic couplers before that) and send it to the paper by hitting a
combination of buttons located just above the keyboard. Would that any of my
laptops had worked that well.

In other words, there hadn’t been anything quite like the Eee 701
in 20 years.

“I can’t say I remember exactly walking into the room when Asus
showed us the first Eee, but I do remember that I had never seen anything quite
like it”, says Ackerman. “It was an amazing accomplishment for the
price.”

Yes, the price. In 2005, the average laptop cost about $1,000, and you
didn’t get all that much for a grand—an HDD drive, wireless, a
touchpad and maybe an optical drive. But you also got a bulky machine that
weighed five or six pounds with crummy battery life—often as little as two
hours.

The 701, on the other hand, cost $199, weighed half as much as the
$1,000 laptop, sometimes had better battery life, and it came with some of the
same hardware (minus the optical drive). And, you could argue that its tiny SSD
drive was an improvement over the era’s 20 and 30GB laptop hard
drives—quieter, less power hungry and more nimble. Yes, the processor
wasn’t as fast, it had less RAM, and the screen was smaller, but that
didn’t seem to matter.

“It was a crazy concept, but there was an incredible response”,
says Wilson, today a senior writer at Fast Company. “Within six months, it
seemed like every computer maker was cloning it.”

Get Me Linux

How did Asus get the price so low? Cutting the weight helped. Using
cheaper materials for the body, keyboard and screen made a difference too, as
did the less expensive processor and memory. But one of the most important
factors was substituting Linux for Windows.

An Asus spokesman did not respond to several requests for information
for this story, but those with knowledge of the company’s thinking said
choice of operating system was crucial in lowering the Eee’s price. A
Microsoft license, depending on who you talk to, could have cost almost as much
as the netbook’s suggested retail price. Even if Asus had absorbed some of
the license fee, it would have been almost impossible to hit $199, then
considered the sweet spot for pricing.

Enter Xandros, the operating system that Asus used on the Linux-powered
versions of the Eee. It was perhaps the machine’s greatest asset and its
biggest weakness. Since it was Linux, there was no Microsoft licensing fee,
making it easier for Asus to hit $199. But Xandros was not quite open-source
Linux—it was a commercial product from the same-named British company
whose revenue came from “partnering” with OEMs. Which, of course, is
what Microsoft did.

And, as anyone who knows anything about the Linux community will tell
you, any open-source company with a Microsoft-like business plan can’t
really be open-source or true to the spirit of Linux. In this, Asus alienated
the people who should have been the Eee’s biggest supporters. Look on
bulletin board and Reddit posts, and you’ll still see some of the
resentment at the choice of Xandros.

Xandros’ other problem? It was just a little too Linux for the
millions of people who bought it and who were used to Windows. It’s not to
say that Xandros didn’t try—the company’s mission was to be a
Windows-like interface to Linux, and it was based on Debian, just like Ubuntu
and Linux Mint.

But those of us who came to Linux through the Eee had never seen
anything quite like Xandros. It was was funky, to say the least, and this comes
from someone who had had his fill of Windows by then (Windows ME, anyone?). I
was desperate to run something that didn’t make me pound the keyboard in
frustration at every crash, Control-Alt-Delete and hanging screen.

Today, a browser-based OS like Chrome is second nature; in 2007, it
could be befuddling to anyone who grew up pointing and clicking in Windows 95.
Xandros, save for the word processor, email and browser, was a
mystery—to this day, I still don’t know what something called mediaU was supposed
to do. It was almost impossible to add new software, and if you wanted to do
anything other than basic software updates, you had to use the command line. I
had been through that with DOS—I didn’t want to do it again. And, of
course, support was non-existent.

To be fair, Asus was limited in its choices. Mint was still in its
early stages, Ubuntu wouldn’t release its netbook OS until 2009, and Fedora
probably wasn’t quite right for something like this. But, as Wilson says
with a laugh: “Xandros was the kind of Linux that reminded people why they
didn’t want to use Linux.”

Running Scared

It’s almost impossible to believe, a decade later, how popular
netbooks were in the wake of the Eee. Way past popular, actually: the netbook
was the best-selling computer in the world in 2009, with seven-fold growth from
2008 and some 20 million sold. That accounted for almost 10% of the
entire computer market at a time when the recession saw desktop computer sales
fall 12%, the worst decline in its history.

Asus gloried in the Eee’s success. It updated the netbook every
couple of months, adding power and improving screen size and resolution. CNET
reviewed eight versions in 12 months, and even the most expensive cost one-half
of a typical laptop of the time.

The 900, the first real production model, had a 9″ screen, a 4GB
SSD and 1 GB of RAM. I literally wore it out, using it until I cracked the
keyboard and broke the A key off. I replaced it with the Eee 1005 a year
later, which had a 10″ screen, 2GB of RAM, a 160GB HHD and four hours of
battery life. I still have it, and it works as well as it ever did. The 1101,
meanwhile, had an 11.6″ screen and a 160GB HDD and still weighed just
three pounds.

Netbooks and the Eee were so successful, in fact, that research
analysts who followed Apple—whose top executives had famously called the
machines “junk”—warned the company that it had better do
something to compete. Mac sales fell in 2008, the first decline in five and
a half
years, and an analyst told Computerworld: “Vendors are waking up to the
fact that people respond to so-called ‘good-enough’ computing. They
don’t really need all the power of a Core 2 Duo CPU most of the time.”

But Apple wasn’t the only company that saw the netbook as a threat.
So did Microsoft, whose abhorrence of Linux was part of the company’s DNA
(remember “Linux is a cancer”?). A Microsoft spokesman did not respond
to several requests for information for this story, so it’s difficult to
know exactly what the company thought. But, says Wilson, “though I
don’t presume to speak for Microsoft, for about six months to a year, they
had to be worried. There were not a lot of phenomenons in the laptop world at
the time.”

The Microsoft dilemma: it was phasing out Windows XP, which could and
did run on some early netbooks, in favor of Windows Vista. But, reported the
New York Times in April 2009, it was “downright embarrassing that Vista is
too tubby to run well on on the best-selling laptops in the market”. Hence,
Microsoft had to find a way to cram the desktop version of Windows 7 onto a
netbook.

Which it did, though the results left much to be desired. I
“activated” the so-called Windows 7 Starter version on a friend’s
netbook; it literally took all night to install, clacking and churning and
rebooting. And then rebooting some more. “They got Windows working on
netbooks”, says Ackerman, “and if it didn’t work well, it worked
well enough”.

More important, Microsoft cut the Windows 7 licensing fee for
netbooks by one-third. It was $75 a copy for a desktop, but only $25 for
netbooks (which it had apparently charged for XP on netbooks too).

This was the beginning of the end. Wrote the Times: “[C]onsumers
have shown their preference for Windows on netbooks….Linux went from
almost 100 percent share on netbooks in the early days to just 20 percent after
Microsoft started offering Windows XP on the systems.”

A Fond Memory

So much for Linux for the masses. But worse was yet to come for the
Eee: Apple released and refined the iPad and the iPod Touch during the next
couple years. Even more important, it unveiled the iPhone 3GS in June 2009.
One million 3GSes were sold in three days, and consumers—thanks to
the revolutionary Apple app store—discovered they didn’t need a
computer to send email, listen to music or browse the web. And, at $99, the
3GS undercut the Eee on price. The modern smartphone had arrived.

The Eee and netbooks didn’t go away immediately, of course. Genuine
efforts were made to keep it relevant—Asus released the $500 1201 in
2010, with a 12.1″ screen and more-or-less desktop resolution. The Linux
community, meanwhile, offered operating systems like Ubuntu netbook,
EasyPeasy/Ubuntu Eee, Joliecloud and Peppermint OS. But the 1201 wasn’t so
much a netbook as the forerunner to the ultrabook, and only those of us who
wanted to run Linux instead of Windows would spend the time to install one of
the new OSes over Windows and the few Xandros machines that were still
being sold.

The end came in 2012, when Acer said it would stop production, and Asus
discontinued the Eee. Tellingly, more tablets were sold than netbooks that
year. But the Eee lives on, and not just because those of us who still have one
or two will pop a thumbdrive into one of its slots, load Puppy or Antix or
Lubuntu, and give it a whirl.

Today’s high-end laptops adapted the Eee’s strengths—battery life and
weight, among others—and combined it with high-end
specs. And, frankly, anyone who has negotiated a smartphone home screen,
flicking those big, shiny icons, is doing about what we did with Xandros and
its home screen on the Eee 901.

And it lives on in the Chromebook: a simple, inexpensive and
lightweight laptop that does what most people need a computer to do—send
email, browse the internet and do word processing. And it does it all through
a browser window without the blue screen of death, Control-Alt-Delete, and
updates that need to reboot and reboot and reboot. And then reboot again.

And isn’t that what computing should be about?

Source

Two Open Source Mobile App Development Frameworks To Make Mobile Dev Easier | Linux.com

Mobile apps have been a boon for developers. With Android the most widely used platform on the planet, it makes perfect sense for developers to ply their trade in the mobile market. Not only do developers have the chance to get their work seen, they can make money from the Google Play Store or the iOS App Store. For those who have yet to delve into the mobile development market, however, the process may be a bit daunting. What tools are available? More importantly, what open source tools are available? After all, if you’re developing on the Linux platform, you probably don’t want to work with proprietary software.

So, to get started creating the greatest mobile app on the planet, you need to get the right tools. One such tool is a framework. In programming terms, a framework is an abstraction in which common code (that provides a generic or general functionality) can be used and rewritten to provide a specific functionality. Say you need Function X for your app, but you don’t want to write all the necessary code for that function. You can use a framework that offers Function X and modify that function so it perfectly fits your needs. In other words, a framework is a way to make development easier and more efficient.

Are there open source frameworks available for mobile development? There certainly are. Let’s take a look at two tools available for this particular task.

Ionic

Ionic is both 100 percent free and open source. This project, licensed under MIT, enables you to build fully cross-platform, progressive web and native mobile apps for every major app store… all from a single codebase. You can develop Ionic apps on any platform you like. Of course, our platform of choice is Linux. Fortunately, Ionic offers a simple command-line interface (CLI) that can be used to create, build, test, and deploy your apps to any platform. Ionic also features:

  • Ionic Native, which allows you to unlock native APIs (and other features), by wrapping Cordova plugins in TypeScript.
  • Live Reload, which allows you to compile and re-deploy an app at every development step.
  • Ionicons, which is an icon pack that includes hundreds of the most common app icons (all MIT licensed and ready to use).
  • Deeplinking, which allow you to start your app from a web link (and can even load a specific view out of the box).
  • AoT Compiling, which helps your apps to load faster.

Create a free Ionic account here and then install Ionic on your distribution. For example, if you’re using Ubuntu as your development platform, to install Ionic you must first install Node.js and npm like so:

  1. Open a terminal window.
  2. Issue the command sudo apt install curl
  3. Add the necessary repository with the command curl -sL https://deb.nodesource.com/setup_10.x | sudo bash –
  4. Install node.js and npm with the command sudo apt install nodejs

Install Ionic with the command:

sudo npm install -g ionic

You can now begin creating and working with your project. To create a new project, issue the command:

ionic start PROJECT_NAME blank –type ionic1

where PROJECT_NAME is the name of your project. You should see a newly created folder (with the same name as your project), that includes a number of new files and folders (Figure 1).

For more information on using the Ionic CLI, check out the official Ionic Guide.

PhoneGap

PhoneGap is an open source distribution of Adobe Cordova that makes it possible to develop your mobile app using web development technologies (e.g., HTML, CSS, and JavaScript) in just a few minutes. If you don’t want to work from the command line, PhoneGap does offer a desktop app (which is only available for macOS and Windows). The desktop app uses the same libraries found in the CLI, but it makes it a bit less daunting for those who prefer a more point and click-friendly method of app development.

PhoneGap includes the following:

  • PhoneGap Developer is a mobile app to connect your devices to your development machine (to see changes you make instantly).
  • PhoneGap Build enables you get app-store ready apps without having to maintain native SDKs for each mobile environment.
  • Plugin Library gets you access to a robust library of plugins to extend the capability of your mobile apps.
  • Third party tools is where you can find additional tools, created by the PhoneGap community, to help test, debug, and manage apps.
  • Developer community allows you to connect to thousands of developers working with PhoneGap.
  • Mobile App helps you pair your mobile device to the desktop app, so you can preview your new app.

To install the PhoneGap CLI tool, you’ll need jode.js and npm installed (as described above). Once that is taken care of, you can install the PhoneGap CLI tool with the command:

sudo npm install -g phonegap@latest

Once you’ve install the CLI, issue the command phonegap to see the help file (and show that the tool was successfully installed—Figure 2).

You might find you run into a permissions issue, when running the phonegap command. To resolve that, issue the command:

sudo chown -R USER:USER ~/.config/configstore

Where USER is your Linux username.

You should now be able to create your first project with the command:

phonegap create PROJECT_NAME

Where PROJECT_NAME is the name of your project.

To find out more on how to use the PhoneGap CLI, check out this reference.

There’s more to be found

There are plenty more open source mobile developer frameworks to be found. These two tools, however, can be thought of as a great launching point to help you get started with your mobile development journey. They are certainly not the only players on the field, but offer quite a lot in the way of power, flexibility, and feature sets. Give one of these tools a try and see if it doesn’t empower your mobile app development with the help of open source.

Learn more about Linux development in the Introduction to Open Source Development, Git, and Linux training course, and sign up now to start your open source journey.

Source

The First Social Network » Linux Magazine

Before the web as we know it existed, Usenet performed the same tasks now done by web forums and social networks. Despite its declining popularity, Usenet is still employed to publish articles, sustain mailing lists, and even upload files.

Usenet, is a gigantic Internet forum with thousands of subforums. The Usenet system is designed as a federated network, which means you just need to connect to one Usenet server in order to have access to all of Usenet. The most common tool for connecting to Usenet is a Network News Transfer Protocol (NNTP) client. See the box titled “The Nature of Federated Networks” for more information.

The Usenet network is a giant bulletin board that is divided into hierarchical sections, called newsgroups. Newsgroups are to Usenet what subforums are to web-based forums, and each one deals with a particular topic. For example, rec.sport.soccer is dedicated to discussions about soccer. Usenet netizens are supposed to use their clients to subscribe to the newsgroups they want to be active in, in much the same way they would subscribe to a mailing list. Subscribing to a newsgroup means that your client will pull new messages from the newsgroups each time you connect or at regular intervals, depending on your client. Despite the name, newsgroups are actually discussion groups. Newsgroups got their name because they were originally intended to host news.

Any user can post an article to a newsgroup. An article can receive answers from other Usenet users, thus creating discussion threads, much like a mailing list. Some newsgroups are moderated, and posts need to be approved by the newsgroup administrator before publication.

[…]

Use Express-Checkout link below to read the full article (PDF).

Source

Ubuntu 3805-2: curl vulnerability – The Community’s Center for Security

Posted by Anthony Pell

Ubuntu
Several security issues were fixed in curl. ==========================================================================
Ubuntu Security Notice USN-3805-2
November 01, 2018

curl vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

– Ubuntu 12.04 ESM

Summary:

Several security issues were fixed in curl.

Software Description:
– curl: HTTP, HTTPS, and FTP client and client libraries

Details:

USN-3805-1 fixed a vulnerability in curl. This update provides
the corresponding update for Ubuntu 12.04 ESM.

Original advisory details:

Brian Carpenter discovered that the curl command-line tool incorrectly
handled error messages. A remote attacker could possibly use this
issue to obtain sensitive information. (CVE-2018-16842)

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 12.04 ESM:
curl 7.22.0-3ubuntu4.24
libcurl3 7.22.0-3ubuntu4.24
libcurl3-gnutls 7.22.0-3ubuntu4.24
libcurl3-nss 7.22.0-3ubuntu4.24

In general, a standard system update will make all the necessary
changes.

References:
https://usn.ubuntu.com/usn/usn-3805-2
https://usn.ubuntu.com/usn/usn-3805-1
CVE-2018-16842

Source

Testing REST API Using Postman

Postman is a software which you can use to test REST APIs. Postman has an easy to use graphical user interface. It also has many helpful features to help you with testing your REST API. Postman is available for Windows, Mac and Linux. Postman is also available as a Chrome plugin. So, you can use Postman inside your Google Chrome browser. Postman has a free version and paid versions. You can do almost everything with the free version. I will use the free version in this article.

Source

Free and open source racing game ‘Yorg’ has a new release with a new track, a new camera and more

For those who love their arcade-style racing games Yorg is actually quite amusing. The developers just release Yorg 0.10 and it’s quite an improvement.

This fresh release includes a new track, a new rear camera view, user interface improvements, the ability to register for online play directly in the game, a better driving model and updated translations.

Naturally, it also has a dose of bug fixes included along with a new trailer:

The online multiplayer could use some big improvements. Especially since it allowed me to make an account with no password—woops. On top of that, the system to actually make an online match isn’t great. Myself and Samsai tried it and it’s extremely unclear and didn’t seem to actually work.

You invite someone from the online list (icons appear when you hover over someone’s name) and they’re supposed to get a notification to join a match. Samsai didn’t get my invite and it got stuck claiming we were both in a game. We logged out and back in, this time Samsai invited me which worked. Then, after picking a car and Samsai started the game it completely froze for me and Samsai got a black screen. Sadly, they’ve got a bit of work to do to actually make online play be clear in how it works and actually work properly.

At least singleplayer works okay…

Check it out on the official site or use itch.io with their client to keep it easily up to date.

Source

The Linux Throwie: Powering a Linux Server with a 300mW Solar Panel

Have you ever had one of those moments, when you’re rummaging through your spare parts heap, and have a rather bizarre project idea that you can’t quite get out of your head? You know, the ones that have no clear use, but simply demand to be born, of glass and steel and silicon?

This time, the stubborn idea in question was sort of like a solar-rechargeable LED throwie, but instead of a blinking light, it has a fully cloud-accessible embedded Linux server in the form of a Raspberry Pi 3 Model B+. Your choice of embedded Linux board should work — I just happen to have a lot of these due to a shipping error.

There were two main challenges here: First, it would have to combine the smallest practical combination of solar panel, power supply, and battery that could run the Raspberry Pi. Second, we’ll need to remotely activate and access the Pi regardless of where it is, as well as be able to connect it to WiFi without direct physical access. In this article we’ll be dealing with the first set of problems — stay tuned for the rest.

One time I stuck a bunch together to make a ‘Dyson Lampshade’, which is of course a Dyson Sphere rendered less large, less spherical, and more absurd.

Sipping on Solar

I approached the first challenge from the standpoint that the Raspberry Pi doesn’t need to be on all that often. An ESP8266 (Wemos D1 Mini) running NodeMCU can provide battery management, and receive commands over MQTT to activate it, while staying in deep sleep mode most of the time. This consumes very little power, allowing a small 5 volt solar module to trickle-charge a lithium battery large enough to power the server for a few hours of run time.

The solar modules are worth a quick mention. They are the LR0GC02 (PDF) from Sharp, designed to trickle charge a variety of mobile electronics. Unlike a lot of modules out there, they are both extremely well encapsulated and very thin (about 1mm). They also come with detailed specifications. A single 300mW module is enough for this project, but I used three in parallel during development to speed up various tests. This tiny solar power module would also have been an interesting choice.

Managing the power from these modules is where things get a little hairy. We have a 4-5V power source charging a lithium cell that has a nominal output voltage of 3.7V. Then we have an ESP8266 module, which runs at 3.3V but can accept higher through an integrated linear regulator, as long as you watch the dropout voltage. Finally, we need a 5V output that can be easily toggled to power the Raspberry Pi. Also it would be nice to have a 12V line for future expansion.

Magnificence of Modern Modules

Thankfully that all sounds worse than it actually is, and there are some very common modules that will sort this out for us:

From left to right: A USB lithium cell charger, a DC-DC boost converter, and a DC-DC buck converter. They cost about a US dollar each, which was great value!

The first stage is a USB lithium cell charging module. These accept the ~5 V output from our solar panels, and will safely charge a lithium cell. The output of the module is whatever the battery voltage is.

Next in line, I added a DC-DC boost converter module set to output 12V. These modules are better than 90% efficient, accept a range of voltages, and will output a fixed voltage that is set by a trimpot. The 12V output is connected to the linear regulator on the ESP8266. This way, even if the battery voltage drops below around 3.7V, it will continue to function. This is critical as the ESP8266 monitors the battery and switches the server on and off. If we were to connect its linear regulator directly to the battery output, it would shut down due to power loss while there was still quite a bit of usable power in the system. We do lose a bit of efficiency here, but the ESP8266 is off most of the time, so I can tolerate that.

The 12V output is then fed into a DC-DC buck converter to drop the voltage down to 5V for the Raspberry Pi. It’s important to use a buck converter with an enable pin, so we can control the output state using the ESP8266 later on. Otherwise you’ll need to add a MOSFET or similar to control the power output.

Responsible Battery Management

At this point, we have all the voltage levels we need, and charge control circuitry to prevent our battery from engaging in spontaneous unplanned combustion. However, when lithium cells are discharged too far, they cannot be safely charged again. We need to monitor the battery and prevent it from rendering itself into an unusual paperweight.

The solution is quite straightforward: the ESP8266 has an analog to digital converter. It can only accept up to 3.3V, and our battery can supply more than this, so I used a couple of 100kΩ resistors set up as a voltage divider to drop the voltage – we don’t exactly need high precision here.

To start our control program, I set a timer to run the ESP8266 for 11 seconds before sleeping for 10 minutes, this is plenty of time for the chip to check for commands online. Then, if the battery voltage is below 3.4 volts, it will immediately sleep for 16 minutes instead.

function checkvolt()
x = adc.read(0)
print (x)
if x < 528 then
print(“low battery, sleeping longer”)
node.dsleep(960000000)
end
end

checkvolt()

function sleeping()
node.dsleep(600000000)
end

tmr.alarm(0,11000,0,sleeping)

Some rough calculations suggest that the module will consume an average of around 1.5 mA normally, and around 0.2mA if the battery is low. In reality there will be some current consumed by all the parts even while the system sleeps. I’m told that the sun shines at least once every month or so (I’ll check at some point), and the battery should not have trouble maintaining charge. In any case, if the former assumption is wrong, I have bigger problems to deal with.

Regulating the Voltage Regulator

Finally, we need to be able to control the output of 5V from the last voltage regulator. While I purchased a module that had an ‘enable’ pin available, there was no documentation as to how it worked, and the exact chip used in my module was unclear. Looking at datasheets for a few ICs from different DC-DC converters, it looked like it was probably an active-high enable pin that was pulled up with a resistor on the module.

I tried pulling it back down with a 50kΩ resistor, and the voltage output dropped to zero. Supplying 3.3 volts from one of the GPIO pins of the ESP8266 triggered the enable pin, and it output 5V again.

I discharged the battery a little, then left it running in the sun for an hour – it recharged a bit as expected, prompting the requisite maniacal laughter. Power stages… complete!

Where’s the Linux?

It’s small, it’s solar powered, but other than lounging about in the sun, it doesn’t really do anything yet. Most computing hardware requires software and obviously this is no exception — so how do we make this into a lean, green, Linux machine?

In the next article, we’ll cover how to control this system via MQTT, set up remote configuration (for example if I need to change my WiFi password), and set up a reverse-SSH tunnel so we can connect to the Raspberry Pi without having to reconfigure our network to accommodate it.

The irony that my servers now get more sun than I do is not lost on me. I live near the equator though, and sunbathing for extended periods is an activity reserved for tourists – one that they normally learn to avoid pretty quickly!

Source

Download Bitnami CMS Made Simple Stack Linux 2.2.8-1

Bitnami CMS Made Simple Stack is a free and multiplatform software project that has been especially designed to simplify the deployment of the CMS Made Simple content management system, as well as of its runtime dependencies, on desktop computers and laptops.

What is CMS Made Simple?

CMS Made Simple is a free, open source, fast and web-based application designed from the ground up to act as a powerful CMS (Content Management System) software that allows users to easily manage the contents of their current websites.

Installing Bitnami CMS Made Simple Stack

Bitnami provides native installers for the CMS Made Simple application, which work on the GNU/Linux, Microsoft Windows and Mac OS X operating systems, supporting both 32-bit and 64-bit hardware architectures.

To install CMS Made Simple on your personal computer, you will have to download the package that corresponds to your computer’s hardware architecture, run it and follow the instructions displayed on the screen.

Run CMS Made Simple in the cloud

Thanks to Bitnami, users will be able to run the CMS Made Simple application in the cloud with their own hosting platform or by using the pre-built cloud images for the Windows Azure and Amazon cloud hosting platforms.

Virtualize CMS Made Simple on VirtualBox or VMware

In addition to running CMS Made Simple in the cloud or installing it on your personal computer, you can also run it on top of a VMware ESX, ESXi and Oracle VirtualBox virtualization software. The virtual appliance is based on the latest LTS (Long Term Support) release of the Ubuntu Linux operating system.

The Bitnami CMS Made Simple Module and Docker container

Besides the Bitnami CMS Made Simple Stack product reviewed here, users can also download an all-in-one installer that greatly simplifies the installation of CMS Made Simple on Bitnami’s LAMP, WAMP and MAMP stacks. A CMS Made Simple Docker container will also be available for download on the project’s homepage.

Source

Creative Commons Working with Flickr, OSI Announces $200,000 Donation from Handshake, Intel’s OTC Adopts Contributor Covenant, Artifact Digital Card Game Coming Soon to Linux and Facebook Open-Sources Suite of Kernel Components and Tools

News briefs for November 2, 2018.

Creative Commons is working with Flickr and SmugMug, Flickr’s parent
company, to protect the Commons following
Flickr’s recent announcement that it will
be limiting free accounts to 1,000 images.
Ryan Merkley, Creative Commons CEO, writes, “We want to ensure that
when users share their works that they are available online in
perpetuity and that they have a great experience.” But he also admits
that “the business models that have powered the web for so long are
fundamentally broken. Storage and bandwidth for hundreds of millions
(if not billions) of photos is very expensive. We’ve all benefited
from Flickr’s services for so long, and I’m hopeful we will
find a way forward together.”

The Open Source Initiative announces a $200,000 donation from Handshake, “the largest single donation in organizational
history”. Patrick Masson, the OSI’s general manager, says “Handshake’s
funding will allow us to extend the reach and impact of our Working
Groups and Incubator Projects, many which were established to confront
the growing efforts to manipulate open source through ‘fauxpen source
software’ and ‘open-washing’.”

Intel’s Open-Source Technology Center (OTC) has adopted the Contributor
Covenant for all of its open-source projects. Phoronix
reports
that it chose the Contributor Covenant because
“it’s well written and represented, provides a clear expression of
expectations, and represents open-source best practices.” You can read
the Contributor Covenant here.

Valve’s digital card game Artifact is scheduled to be released
November 28th with Linux support. According to Gaming
on Linux
, the new game will also have a built-in tournament
feature. See the official Artifact site for more details.

Facebook recently announced it’s open-sourcing a new suite of Linux
kernel components and related tools
“that address critical fleet
management issues. These include resource control, resource
utilization, workload isolation, load balancing, measuring, monitoring,
and much more”. According to the Facebook blog post, “the kernel
components and tools included in this release can be adapted to solve a
virtually limitless number of production problems.”

Source

Introducing Zink, an OpenGL implementation on top of Vulkan (Collabora blog) [LWN.net]

[Posted November 1, 2018 by jake]

Introducing Zink, an OpenGL implementation on top of Vulkan (Collabora blog)

[Development] Posted Nov 1, 2018 17:55 UTC (Thu) by jake

Over at the Collabora blog, Erik Faye-Lund writes about Zink, which is an effort to create an OpenGL driver on top of Vulkan that he has been working on with Dave Airlie. “One problem is that OpenGL is a big API with a lot of legacy stuff that has accumulated since its initial release in 1992. OpenGL is well-established as a requirement for applications and desktop compositors.

But since the very successful release of Vulkan, we now have two main-stream APIs for essentially the same hardware functionality.

It’s not looking like neither OpenGL nor Vulkan is going away, and the software-world is now hard at work implementing Vulkan support everywhere, which is great. But this leads to complexity. So my hope is that we can simplify things here, by only require things like desktop compositors to support one API down the road. We’re not there yet, though; not all hardware has a Vulkan-driver, and some older hardware can’t even support it. But at some point in the not too far future, we’ll probably get there.

This means there might be a future where OpenGL’s role could purely be one of legacy application compatibility. Perhaps Zink can help making that future a bit closer?”

Source

WP2Social Auto Publish Powered By : XYZScripts.com