Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Submission + - Free paper-based math game designed using LibreOffice Calc (pairsmathgame.com)

pshapiro writes: One of the best ways to address education equity issues is to boost learning opportunities in the home. This fun, free math game — designed at a public library — was created to spur conversations about numbers. Originally created for middle school students, versions for younger students have also been designed. All versions of the game may be freely downloaded, printed, and photocopied.

A large, vinyl banner can be purchased for mounting in a principal's office, community center, children's hospital, etc. The small vinyl banner is well-suited for school or public libraries who would like to circulate this game — as they would any loaned library item. This game might also appeal to the elderly who are interested in keeping their minds sharp.

Submission + - IP Stacks Commendary getting an update (satchell.net)

satch89450 writes: Back in 2000, I asked about funding sources for updating the book Linux IP Stacks Commentary. Things change. Here is what I posted on my LinkedIn account:

History: 20 years ago, Heather BJ Clifford and I wrote a book, Linux IP Stacks Commentary, which walked through the Linux TCP/IP stack code and commented it in detail. (Old-timers will remember the Lion's Unix Commentary, the book published by University xerographic copies on the sly. Same sort of thing.) CoriolisOpen published it. And a bit later sank into the west. Nothing has been done since, at least not by us.

Now: when I was released from my last job, I tried retirement. Wasn't for me. I started going crazy with nothing significant to do. So, going through old hard drives (that's another story), I found the original manuscript files, plus the page proof files, for that two-decade-old book. Aha! Maybe it's time for an update. But how to keep it fresh, as Torvalds continues to release new updates of the Linux kernel? Publish it on the Web. Carefully.

After four months (and three job interviews) I have the beginnings of the second edition up and available for reading. At the moment it's an updated, corrected, and expanded version of the "gray matter", the exposition portions of the first edition. In addition, I have put forth ideas for making the commentary portions easier to keep up to date, after they are initially written.

The URL for the alpha-beta version of this Web book is https://www.satchell.net/ipsta... for your reading pleasure. The companion e-mail address is up and running for you to provide feedback. There is no paywall.

Thanks to the work of Professor Donald Knuth (thank you!) on his WEB and CWEB programming languages, I have made modifications, to devise a method for integrating code from the GIT repository of the Linux kernel without making any modifications (let alone submissions) to said kernel code. The proposed method is described in the About section of the Web book. I have scaffolded the process and it works. But that's not the hard part.

The hard part is to write the commentary itself, and crib some kind of Markup language to make the commentary publishing quality. The programs I write will integrate the kernel code with the commentary verbiage into a set of Web pages. Or two slightly different sets of web pages, if I want to support a mobile-friendly version of the commentary.

Another reason for making it a web book is that I can write it and publish it as it comes out of my virtual typewriter. No hard deadlines. No waiting for the printers. And while this can save trees, that's not my intent.

The back-of-the-napkin schedule calls for me to to finish the expository text in September, start the Python coding for generating commentary pages at the same time, and start the writing the commentary on ICMP in October. By then, Linus should have version 6.0.0 of the Linux kernel released.

I really, really, really don't want to charge readers to view the web book. Especially as it's still in the virtual typewriter. There isn't any commentary (yet). One thing I have done is to make it as mobile-friendly as I can, because I suspect the target audience will want to read this on a smartphone or tablet, and not be forced to resort to a large-screen laptop or desktop. Also, the graphics are lightweight to minimize the cost for people who pay by the kilopacket. (Does anywhere in the world still do this? Inquiring minds want to know.)

I host this web site on a Protectli appliance in my apartment, so I don't have that continuing expense. The power draw is around 20 watts. My network connection is AT&T fiber — and if it becomes popular I can always upgrade the upstream speed.

The thing is, the cat needs his kibble. I still want to know if there is a source of funding available.

Also, is it worthwhile to make the pages available in a zip file? Then a reader could download a snapshot of the book, and read it off-line.

Submission + - Who should be Biden's CTO? More to the point: What's the US CTO's job? (businessinsider.com)

Esther Schindler writes: Biden hasn't named a CTO yet, but it behooves us (especially us techies) to contemplate what tasks lie ahead of that individual — and what the role ought to be. As Esther Schindler writes (behind a paywall), * The US CTO doesn't have a lot of direct power: Their job's real impact comes with working with different agencies to help them come up with tech-based strategies for everything from climate change to vaccine distribution."

A CTO can help form visionary approaches and also serve as a voice of reason. A government official can have a great idea that isn't feasible, for instance. "It's become even more of an imperative that the President have a perspective on technology that is commensurate with its true impact on its role in our society," said Andrew Rasiej, CEO and cofounder of Civic Hall.

Ultimately, says Danah Boyd, "They need someone who will work hard to unblock the barriers that existing talent faces so that those working in government agencies can thrive," she said. "This will require transforming procurement procedures, changing the hiring protocols and HR infrastructure, and building the processes to ensure that teams can work effectively and share information strategically."

Submission + - Where's the Yelp for open-source tools? (functionize.com)

Esther Schindler writes: Plenty of people have created systems to collect, judge, and evaluate open-source projects, including information about a project’s popularity, reliability, and activity. But each of those review sites – and their methodologies – have flaws. And sjvn gives an overview of the attempts — and perhaps, where the "wisdom of the crowd" might lead.

In 1997, well-known developer Patrick Lenz founded the first listing and announcement site for free and open-source software, freshmeat.net. It was meant to be the guide to open-source programs. But freshmeat never lived up to its promise.


Submission + - The Golden Age of computer user groups (arstechnica.com)

Esther Schindler writes: The Home-brew computer club where the Apple I got its start is deservedly famous. But throughout the 80s and into the 90s, computer user groups around the world helped hapless users figure out their computer systems, learn about technology trends, and get product demonstrations of the latest whiz-bang applications. Ready for a step into the wayback machine?
 

Submission + - SPAM: Inviting employees back to the office – if you dare

Esther Schindler writes: The day is coming when you no longer have to keep everyone out of the office. You can bring them back. ...Or can you? asks Wayne Rash.

At some point, it'll be safe enough for companies to take off the "everyone works from home" rules. But there are things an organization has to do before it's possible to bring staff back to the office, such as find a way to support social distancing. And that assumes you can convince people to return. Don’t count on that, writes Rash. At best, you can expect to support people both in the office and still at home... and that means changing the IT infrastructure for work-at-home in the long term.

Link to Original Source

Submission + - GNU GPLv3 At The Heart Of The Black Hole Image (www.tfir.io)

arnieswap writes: Free and Open Source software was at the heart of this image. The team used three different imaging software libraries to achieve the feat. Out of the three, two were fully open source libraries. The source code of the software is publicly available on GitHub. Richard M Stallman, the founder of the GNU Project will be glad to see that both libraries (Sparselab and ehtim) are released under GNU GPL v3. Yes, you read it right – GNU GPL v3.

Submission + - 8 ways sci-fi imagines data storage (hpe.com)

Esther Schindler writes: "Storage is a staple of both science and science fiction," writes Carol Pinchefsky. "It forms the basis, or a crucial component, of many a piece of speculative fiction. Looking back to look forward is always educational, or at least entertaining, so here are eight past visions of the storage future that either passed their error checks or succumbed to bit rot."

Why store vast quantities of data on a device when you can just slap it into someone's head?

Submission + - The songs of distant mirth: When technology is something to sing about

Esther Schindler writes: Carol Pinchefsky examined the relationship between music and technology in When technology is something to sing about, and "I realized the songs tend to be about the technology itself. Not 'My baby she wrote me a letter' but 'My baby she wrote me a letter with bitmapped fonts.' Most of these songs express angst and loneliness. They don’t make you reach for your tissues—just your benzodiazepines."

Ultimately she categorized technology-related songs in seven whole categories of depression, self-loathing, and yes, even humor. You think there should be more?

Submission + - 5 things we need to conquer to accelerate space exploration (hpe.com) 1

Esther Schindler writes: Sure, we all want to get humanity out into space. But there are practical barriers to doing so, at least for the long term, and many of them were discussed at at the Economist Space Summit, held Nov. 1 in New York. Several panelists shared their insights about space exploration, NASA’s strategies, and what we need to get to the final frontier.

Among them, for example, is space medicine:

Dava Newman, Apollo Professor of Aeronautics and Astronautics at MIT, warned that radiation is one of the biggest challenges to surviving and thriving in space. Once spacefarers pierce the atmosphere, they're subject to radiation from solar particles and cosmic rays, which increases the risk of cancer in the long term—and acute radiation sickness mid-mission.

Another is quick and reliable data transmission, given the lag time between, say, Mars and Earth. Not to mention computers that can cope with radiation.

Submission + - I'm from the government and I'm here to protect you

Esther Schindler writes: Top cybersecurity experts from the Department of Homeland Security, the Office of the Director of National Intelligence, and private industry came together at a recent event held at the Washington Post to discuss the cyberwar being waged with foreign adversaries as well as the overall threat landscape. Here are some of the insights shared on current and future threats, and what’s being done to combat them. This wasn't vague arm-waving. Preston Gralla wrote a summary.

For instance:

A major challenge in keeping elections safe from cyberattacks, said Homeland Security's Christopher Krebs, has less to do with technology than with the way in which elections are held in the United States. Elections, even those held for the office of the president and Congress, are run by state and local governments, not by the federal government. That means each state and, frequently, individual localities have their own way to hold elections, implementing different technologies—from paper ballots to multiple kinds of voting machines, including direct-recording electronic (DRE) voting machines, some of which do not produce a paper trail and therefore are vulnerable to being hacked.

Krebs put the conundrum this way: “It is the responsibility of the states to administer elections. It is the responsibility of the Department of Homeland Security and the federal government to provide for the national security and national defense of this country. There is a discussion that needs to happen between those two things.”

Submission + - Kill the (robot) ump!

Esther Schindler writes: Everyone who watches sports spends some amount of time yelling at the umpire or sports referee. For the past few years we've also been shouting, "Replace that ump with a robot!"

But is it technically feasible? Is the current level of AI and robotics tech up to the job? This article starts with the assumption that someone seriously wants to create a robot umpire or sports referee and then evaluates whether it possible to build an accurate and trustworthy augmented reality solution today.

Submission + - A new life for old AM broadcast towers

Esther Schindler writes: Video may have killed the radio star, but other media certainly make old AM radio towers superfluous. ...Maybe.

As once-loyal listeners tune away, most AM stations are barely holding onto life, slashing staff and budgets as deeply as they can while struggling to find a return to profitability. Once upon a time, having a broadcast license of any kind was like having a permit to print money. In today’s world, that's no longer true.

But, with 10,000 AM broadcast towers in the United States, stretching high into the sky, there may be an opportunity for wireless carriers who don't want to argue with community opposition from neighborhoods where residents don't want yet another cell tower. The amount of money an AM station owner can pocket by sharing its tower with a wireless partner varies widely, depending on the tower's location, height, and several other factors. But it's certainly more income — and a way to keep "old" technology from becoming obsolete.

Submission + - Coping with Spectre and Meltdown: What sysadmins are doing

Esther Schindler writes: In technical terms, Spectre and Meltdown are a security pain in the butt. In day-to-day terms, though, they're a serious distraction. Before you left on the holiday break, after all, you had a nice sensible To Do list for the projects you wanted to tackle after the new year.

Ha ha ha.

Instead, sysadmins have spent their time trying to keep up with the nature of the problem and its fixes (will it REALLY slow down computers that much? how can you tell that to the users?), and apply patches. Or, more specifically:

Ron, an IT admin, summarizes the situation succinctly: “More like applied, applied another, removed, I think re-applied, I give up, and have no clue where I am anymore.”

Feel like you're alone? Here's what other sysadmins have done so far, as well as their current plans and long-term strategy, not to mention how to communicate progress to management.

Submission + - Taking the plunge: Enterprise IT firsts over the decades

Esther Schindler writes: Technology trailblazers are everywhere these days, but early on, big corporations were reluctant to gamble on unproven startups. Which brave businesses were the first to put technology to use? Josh Fruhlinger enumerates a few early tech pioneers. Here’s the first business website, the first person given the title of CIO, and other things that’ll make you say Hmmm.

Slashdot Top Deals

Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them?

Working...