By Unknown Lamer from Slashdot's building-rms-a-new-laptop department
Via Phoronix comes news that Debian has been ported to the OpenRISC architecture
by Christian Svensson. Quoting his mailing list post:"Some people know that I've been working on porting Glibc and doing some
toolchain work. My evil master plan was to make a Debian port, and today
I'm a happy hacker indeed! ... If anyone want to try this on real hardware (would be very cool to see how
this runs IRL), ping me on IRC [#openrisc on freenode] and I'll set you up with instructions how to
use debootstrap - just point to a repo with the debs and you're all set,
the wonders of binary distributions."
For those who don't know, OpenRISC
is the completely open source RISC processor intended as the crown jewel of the Opencores project. A working port of glibc and a GNU/Linux distribution is a huge step toward making use of OpenRISC practical. There's a screencast of the system in action
, and source on Github
(at posting time, it was a month out of date from the looks of it). Christian Svensson's Github account also has repos for the rest of the toolchain
.Read Replies (0)
By Unknown Lamer from Slashdot's like-emacs-but-...-no-basically-it's-emacs department
hypnosec writes "Github has introduced Atom, its new 'web native' code editor which has been in development for more than six years. Atom is available as a part of an invite-only beta program. GitHub describes Atom as an attempt to create an editor 'that will be welcoming to an elementary school student on their first day learning to code, but also a tool they won't outgrow as they develop into seasoned hackers.'"
You can request an invite on atom.io
. The source to supporting libraries has already been released
any less messy than Emacs-Lisp though?). A preliminary user guide
and customization guide
are available to all.Read Replies (0)
By Unknown Lamer from Slashdot's fire-ten-hire-three department
dcblogs writes with news that the rumored IBM layoffs have begun
. "IBM is laying off U.S. employees this week as part of a $1B restructuring, and is apparently trying keep the exact number of cuts secret. The Alliance@IBM, the main source of layoff information at IBM, says the company has stopped including in its resource action documents, given to cut employees, the number of employees selected for a job cut. The union calls it a 'disturbing development.' Meanwhile, two days prior to the layoffs, NY Governor Cuomo announced that it reached a new minimum staffing level agreement with IBM to 'maintain 3,100 high-tech jobs in the Hudson Valley and surrounding areas.' The governor's office did not say how many IBM jobs are now there, but others put estimate it at around 7,000. Lee Conrad, a national coordinator for the Alliance, said the governor's announcement raises some questions for workers and the region. 'Yes, you're trying to protect 3,100 jobs but what about the other 3,900 jobs?' The Alliance estimates that anywhere from 4,000 to 6,000 U.S. workers could be impacted by the latest round of layoffs. IBM says it has more than 3,000 open positions in the U.S., and says the cuts are part of a 'rebalancing' as it shifts investments into new areas of technology, such as cognitive computing."
Alliance@IBM has a page collecting reports from people terminated
today.Read Replies (0)
By Roblimo from Slashdot's documentation-makes-software-more-usable department
There is this guy, Eric Holscher
, who has been doing FOSS
development for quite a while. He's been on GitHub since 2008
, and got involved in Gittip
not long after it started in 2012. Not long after that
, Eric started thinking about how open source software developers have all kinds of conferences and have many communities they can join and learn from each other, while those who write documentation, especially for FOSS, typically work all alone in a vacuum.
So why not have a conference for documentation writers (and developers who want to hook up with writers who can help them make high-quality docs)? Don't limit it to FOSS, but make sure that's the emphasis. Call the conference 'Write the Docs' and have the first conference
in Portland, Oregon, in 2013. Which is exactly what Eric did.A year later, a second 'Write the Docs' conference is scheduled in Budapest (Hungary) for at the end of March
, and the next Portland conference is set for April 8th
.Read Replies (0)
By Unknown Lamer from Slashdot's breaking-your-mind-reforms-you department
Hugh Pickens DOT Com writes "Joseph Stromberg writes in Smithsonian Magazine that while the practice of solitary confinement is being discontinued in most countries, it's become increasingly routine within the American prison system. It is estimated that between 80,000 and 81,000 prisoners are in some form of solitary confinement nationwide. Once employed largely as a short-term punishment, it's now regularly used as way of disciplining prisoners indefinitely, isolating them during ongoing investigations, coercing them into cooperating with interrogations and even separating them from perceived threats within the prison population at their request.
Most prisoners in solitary confinement spend at least 23 hours per day restricted to cells of 80 square feet, not much larger than a king-size bed, devoid of stimuli (some are allowed in a yard or indoor area for an hour or less daily), and are denied physical contact on visits from friends and family ... A majority of those surveyed experienced symptoms such as dizziness, heart palpitations, chronic depression, while 41 percent reported hallucinations, and 27 percent had suicidal thoughts...
< article continued at Slashdot
>Read Replies (0)
By Unknown Lamer from Slashdot's using-pflow-for-fun-and-profit department
badger.foo writes "Have you ever wanted to know what's really going on in your network? Some free tools with surprising origins can help you to an almost frightening degree. Peter Hansteen shares some monitoring insights, anecdotes and practical advice in his latest column on how to really know your network. All of it with free software, of course."
From the article: "
The NetFlow protocol was invented at Cisco in the early 1990s. It's designed to collect traffic metadata, where the basic unit of reference is the flow, defined as the source and destination IP address pair, the matching source and destination port for protocols that use them, the protocol identifier, time started and ended, number of packets sent, number of bytes sent, and a few other fields that have varied somewhat over the NetFlow versions. ...
On OpenBSD, various netflow sensors and collectors had been available for a while when the new network pseudo device pflow
debuted in OpenBSD 4.5."Read Replies (0)