fidzu : geeks

UK project aims to build record of past storms to help project future ones.

22 Mar 2019 1:33pm GMT

This sporty crossover is all kinds of fun to drive, even if if feels like a beta sometimes.

22 Mar 2019 1:12pm GMT

Tesla Dashcam video highlights weakness of Tesla's testing regime.

22 Mar 2019 1:02pm GMT

An anonymous reader quotes a report from The Guardian: Facebook employees were aware of concerns about "improper data-gathering practices" by Cambridge Analytica months before the Guardian first reported, in December 2015, that the political consultancy had obtained data on millions from an academic. The concerns appeared in a court filing by the attorney general for Washington DC and were subsequently confirmed by Facebook. The new information "could suggest that Facebook has consistently mislead [sic]" British lawmakers "about what it knew and when about Cambridge Analytica," tweeted Damian Collins, the chair of the House of Commons digital culture media and sport select committee (DCMS) in response to the court filing. In a statement, a company spokesperson said: "Facebook absolutely did not mislead anyone about this timeline." After publication of this article, the spokesperson acknowledged that Facebook employees heard rumors of data scraping by Cambridge Analytica in September 2015. The spokesperson said that this was a "different incident" from Cambridge Analytica's acquisition of a trove of data about as many as 87 million users that has been widely reported on for the past year. "In September 2015 employees heard speculation that Cambridge Analytica was scraping data, something that is unfortunately common for any internet service," the spokesperson said. "In December 2015, we first learned through media reports that Kogan sold data to Cambridge Analytica, and we took action. Those were two different things." The filing raised questions about when Facebook first learned about the misuse of personal data by Cambridge Analytica, the now defunct political consultancy.

Read more of this story at Slashdot.

22 Mar 2019 1:00pm GMT

Google's Stadio cloud-gaming service may be intercepted by a similar service from Walmart. According to a report from US Gamer, the American retail giant is looking into launching its own cloud gaming service. From the report: Multiple sources familiar with Walmart's plans, who wish to remain anonymous, confirmed to USG that the retail giant is exploring its own platform to enter in the now-competitive video game streaming race. No other details were revealed other than it will be a streaming service for video games, and that Walmart has been speaking with developers and publishers since earlier this year and throughout this year's Game Developers Conference. Walmart's discussions with developers for its streaming service have been secretive, and it's unclear how far along the service is in-development. But our sources are confident that this is a space Walmart is trying to move into. Though Walmart might sound like a strange company to be jumping into the streaming tech space, the move isn't wholly unexpected. In recent years due to competition from Amazon, Walmart has been increasingly looking into more tech-focused markets beyond its traditional physical retail chain. Over time, Walmart has integrated its physical stores with its large online presence, offering deliveries, app integrations, and in-store pick up services. Walmart also has a technology arm in Silicon Valley called Walmart Labs, which has 6,000 employees and develops tech for Walmart's digital presence. In addition it boasts tools like Cruxlux, which is a search engine designed to reveal the connection between any two people, places, or things. Finally, Walmart has a data center unofficially called Area 71 in Caverna, Missouri which holds over 460 trillion bytes of data. Data centers are a centerpiece of Google's Stadia streaming service and companies like Microsoft, Amazon, and Apple also own powerful data facilities, all of whom are also coincidentally working in streaming technology.

Read more of this story at Slashdot.

22 Mar 2019 10:00am GMT

The recent Boeing 737 MAX crashes involving an Ethiopian Airlines flight and a Lion Air flight may have been a result of two missing safety features that Boeing charged airlines extra for (Warning: source may be paywalled; alternative source). The New York Times reports that many low-cost carriers like Indonesia's Lion Air opted not to buy them so they could save money, even though some of these systems are fundamental to the plane's operations. "Now, in the wake of the two deadly crashes involving the same jet model, Boeing will make one of those safety features standard as part of a fix to get the planes in the air again," the report says. From the report: It is not yet known what caused the crashes of Ethiopian Airlines Flight 302 on March 10 and Lion Air Flight 610 five months earlier, both after erratic takeoffs. But investigators are looking at whether a new software system added to avoid stalls in Boeing's 737 Max series may have been partly to blame. Faulty data from sensors on the Lion Air plane may have caused the system, known as MCAS, to malfunction, authorities investigating that crash suspect. The jet's software system takes readings from one of two vanelike devices called angle of attack sensors that determine how much the plane's nose is pointing up or down relative to oncoming air. When MCAS detects that the plane is pointing up at a dangerous angle, it can automatically push down the nose of the plane in an effort to prevent the plane from stalling. Boeing's optional safety features, in part, could have helped the pilots detect any erroneous readings. One of the optional upgrades, the angle of attack indicator, displays the readings of the two sensors. The other, called a disagree light, is activated if those sensors are at odds with one another. The angle of attack indicator will remain an option that airlines can buy. Neither feature was mandated by the Federal Aviation Administration. All 737 Max jets have been grounded. "Boeing will soon update the MCAS software, and will also make the disagree light standard on all new 737 Max planes," the report adds, citing a person familiar with the changes. "Boeing started moving on the software fix and the equipment change before the crash in Ethiopia." Slashdot reader Futurepower(R) adds to the story: The FBI has joined the criminal investigation into the certification of the Boeing 737 MAX, lending its considerable resources to an inquiry already being conducted by U.S. Department of Transportation agents, according to people familiar with the matter. "The federal grand jury investigation, based in Washington, D.C., is looking into the certification process that approved the safety of the new Boeing plane, two of which have crashed since October.

Read more of this story at Slashdot.

22 Mar 2019 7:00am GMT

Well, it's hanging on in there, but why didn't it conquer the world?

Analysis Does European Commissioner for Competition Margrethe Vestager's team pay close attention to the tech news? If not, perhaps they should.…

19 Oct 2016 10:24am GMT

Linus Torvalds teaches devs a lesson with early rc1 release

Google may have killed off its modular smartphone Project Ara idea, but some of the code that would have made it happen looks like coming to the Linux Kernel.…

17 Oct 2016 6:58am GMT

Your weekly Windows entertainment large and small

This week's worldwide BSOD roundup starts with what looks to your writer like a virtualisation launch bug. Submitter Alexander tells us it came from Peterborough Station, in Cambridgeshire.…

17 Oct 2016 6:28am GMT

To anyone who has been reading anything on the web over the past few months, this shouldn't come as a surprise. Barnes & Noble is currently embroiled in a patent lawsuit started by Microsoft, after the bookseller/tablet maker refused to pay protection money to Redmond. Barnes & Noble has now openly said what we already knew, and has filed an official complaint at the US Department of Justice: Microsoft is engaging in anticompetitive practices.

09 Nov 2011 4:13pm GMT

"Sources close to Adobe that have been briefed on the company's future development plans have revealed this forthcoming announcement to ZDNet: Our future work with Flash on mobile devices will be focused on enabling Flash developers to package native apps with Adobe AIR for all the major app stores. We will no longer adapt Flash Player for mobile devices to new browser, OS version or device configurations.. . ."

09 Nov 2011 6:34am GMT

"The following are major features for Fedora 16: enhanced cloud support including Aeolus Conductor, Condor Cloud, HekaFS, OpenStack and pacemaker-cloud; KDE Plasma workspaces 4.7; GNOME 3.2; a number of core system improvements including GRUB 2 and the removal of HAL; an updated libvirtd, trusted boot, guest inspection, virtual lock manager and a pvops based kernel for Xen all improve virtualization support."

08 Nov 2011 10:45pm GMT

Tyrs is a microblogging client, supporting Twitter and Status.net (identi.ca), it's based on console using the NCurses module from Python. The release of the 0.5.0 version is a good excuse to introduce Tyrs. Tyrs aims to get a good interaction with a fairly intuitive interface that can provide support ncurses. Tyrs tries also not to [...]

06 Nov 2011 9:43pm GMT

After one year of managing a network of 10 servers with Cfengine I'm currently building two clusters of 50 servers with Puppet (which I'm using for the first time), and have various notes to share. With my experience I had a feeling Cfengine just isn't right for this project, and didn't consider it seriously. These servers are all running Debian GNU/Linux and Puppet felt natural because of the good Debian integration, and the number of users whom also produced a lot of resources. Chef was out of the picture soon because of the scary architecture; CouchDB, Solr and RabbitMQ... coming from Cfengine this seemed like a bad joke. You probably need to hire a Ruby developer when it breaks. Puppet is somewhat better in this regard.

Puppet master needs Ruby, and has a built-in file server using WEBrick. My first disappointment with Puppet was WEBrick. Though PuppetLabs claim you can scale it up to 20 servers, that proved way off, the built-in server has problems serving as little as 5 agents/servers, and you get to see many dropped connections and failed catalog transfers. I was forced to switch to Mongrel and Nginx as frontend very early in the project, on both clusters. This method works much better (even though Apache+Passenger is the recommended method now from PuppetLabs), and it's not a huge complication compared to WEBrick (and Cfengine which doesn't make you jump through any hoops). Part of the reason for this failure is my pull interval, which is 5 minutes with a random sleep time of up to 3 minutes to avoid harmonics (which is still a high occurrence with these intervals and WEBrick fails miserably). In production a customer can not wait on 30/45 minute pull intervals to get his IP address whitelisted for a service, or some other mundane task, it must happen within 10 minutes... but I'll come to these kind of unrealistic ideas a little later.

Unlike the Cfengine article I have no bootstrapping notes, and no code/modules to share. By default the fresh started puppet agent will look for a host called "puppet" and pull in what ever you defined to bootstrap servers in your manifests. As for modules, I wrote a ton of code and though I'd like to share it, my employer owns it. But unlike Cfengine v3 there's a lot of resources out there for Puppet which can teach you everything you need to know, so I don't feel obligated to even ask.

Interesting enough, published modules would not help you get your job done. You will have to write your own, and your team members will have to learn how to use your modules, which also means writing a lot of documentation. Maybe my biggest disappointment is getting disillusioned by most Puppet advocates and DevOps prophets. I found articles and modules most of them write, and experiences they share have nothing to do with the real world. It's like they host servers in a magical land where everything is done in one way and all servers are identical. Hosting big websites and their apps is a much, much different affair.

Every customer does things differently, and I had to write custom modules for each of them. Just between these two clusters a module managing Apache is different, and you can abstract your code a lot but you reach a point where you simply can't push it any more. Or if you can, you create a mess that is unusable by your team members, and I'm trying to make their jobs better not make them miserable. One customer uses an Isilon NAS, the other has a content distribution network, one uses Nginx as a frontend, other has chrooted web servers, one writes logs to a NFS, other to a Syslog cluster... Now imagine this on a scale with 2,000 customers and 3 times the servers and most of the published infrastructure design guidelines become laughable. Instead you find your self implementing custom solutions, and inventing your own rules, best that you can...

I'm ultimately here to tell you that the projects are in a better state then they would be with the usual cluster management policy. My best moment was an e-mail from a team member saying "I read the code, I now understand it [Puppet]. This is fucking awesome!". I knew at that moment I managed to build something good (or good enough), despite the shortcomings I found, and with nothing more than using PuppetLabs resources. Actually, that is not completely honest. Because I did buy and read the book Pro Puppet which contains an excellent chapter on using Git for collaboration on modules between sysadmins and developers, with proper implementation of development, testing and production (Puppet)environments.

05 Nov 2011 11:17pm GMT

Creating json is now ten times easier.

05 Nov 2011 3:10am GMT

Many of you have commented that our NewsVac section hasn't been refreshed since the middle of last month. Others have noticed that our story volume has dropped off. Changes are coming to Linux.com, and until they arrive, you won't see any new stories on the site.

01 Jan 2009 2:00pm GMT

The free and open source software community has been waiting for the G1 cell phone since it was first announced in July. Source code for Google's Android mobile platform has been available, but the G1 marks its commercial debut. It's clearly a good device, but is it what Linux boosters and FOSS advocates have long been anticipating?

31 Dec 2008 2:00pm GMT

Many public administrations already use open source Geographic Information Systems (GIS) to let citizens look at public geographic data trough dedicated Web sites. Others use the same software to partially open the data gathering process: they let citizens directly add geographic information to the official, high-quality GIS databases by drawing or clicking on digital maps.

30 Dec 2008 2:00pm GMT