The next version of Google's smartwatch operating system is slated to arrive on February 9th, according to mobile reporter Evan Blass. The leak follows last week's report that Google had notified developers of Android Wear 2.0's upcoming release so they could prepare to update apps for continued support.
I'm sure all three Android Wear users are jumping up and down with excitement.
This document gives an overview of how security is designed into Google’s technical infrastructure. This global scale infrastructure is designed to provide security through the entire information processing lifecycle at Google. This infrastructure provides secure deployment of services, secure storage of data with end user privacy safeguards, secure communications between services, secure and private communication with customers over the internet, and safe operation by administrators.Google uses this infrastructure to build its internet services, including both consumer services such as Search, Gmail, and Photos, and enterprise services such as G Suite and Google Cloud Platform.
We will describe the security of this infrastructure in progressive layers starting from the physical security of our data centers, continuing on to how the hardware and software that underlie the infrastructure are secured, and finally, describing the technical constraints and processes in place to support operational security.
This document also touches on something I always find quite fascinating - Google is, actually, an incredibly successful hardware company.
A Google data center consists of thousands of server machines connected to a local network. Both the server boards and the networking equipment are custom-designed by Google.
I have no idea how many servers Google actually owns, but this could make them one of the biggest hardware companies in the world.
axle is a small UNIX-like hobby operating system. Everything used within axle is implemented from the ground up, aside from the bootloader, for which we use GRUB. axle is a multiboot compliant kernel. axle runs C on 'bare metal' in freestanding mode, meaning even the C standard library is not included. A subset of the C standard library is implemented within axle's kernel, and a userspace version is planned. axle is mainly interfaced through a shell.
Open source, custom educational operating system. The first public alpha release is out.
The sprawling investigation into President Park Geun-hye of South Korea took a dramatic turn on Monday with word that prosecutors were seeking the arrest of the de facto head of Samsung, one of the world's largest conglomerates, on charges that he bribed the president and her secretive confidante.
Nobody should be able to escape justice - not even CEOs. I know of a few others who need to follow in Lee's footsteps.
VSI (the men and women porting OpenVMS to x86 hardware) has released an update outlining some of the issues so far in porting this old battleship of an operating system to x86 and liberating it from IA64.
This update provides a high level view of our current efforts to port OpenVMS to the Intel x86 hardware platform. The report highlights topics including: Compilers, Objects & Images, Early Boot Path, Virtual Machines, Dump Kernel, Paravirtualization, and Condition Handling.
iPhone app purchasers may sue Apple Inc over allegations that the company monopolized the market for iPhone apps by not allowing users to purchase them outside the App Store, leading to higher prices, a U.S. appeals court ruled on Thursday.
Apple bloggers obviously kneejerk straight into defence mode in response to this news, but if you actually dive into the decision, the court makes a very compelling argument as to why this case ought to be allowed to continue, that preempts all the usual terrible analogies they tend to come up with and/or parrot from the party line:
Apple argues that it does not sell apps but rather sells "software distribution services to developers." In Apple's view, because it sells distribution services to app developers, it cannot simultaneously be a distributor of apps to apppurchasers. Apple analogizes its role to the role of an owner of a shopping mall that "leases physical space to various stores." Apple's analogy is unconvincing. In the case before us, third-party developers of iPhone apps do not have their own "stores." Indeed, part of the anti-competitive behavior alleged by Plaintiffs is that, far from allowing iPhone app developers to sell through their own "stores," Apple specifically forbids them to do so, instead requiring them to sell iPhone apps only through Apple's App Store.
Instead, we rest our analysis, as compelled by Hanover Shoe, Illinois Brick, UtiliCorp, and Delaware Valley, on the fundamental distinction between a manufacturer or producer, on the one hand, and a distributor, on the other. Apple is a distributor of the iPhone apps, selling them directly to purchasers through its App Store. Because Apple is a distributor, Plaintiffs have standing under Illinois Brick to sue Apple for allegedly monopolizing and attempting to monopolize the sale of iPhone apps.
Over on Twitter, John Gruber asked me "iPhones are their own market? Does BMW have a monopoly on BMWs?" This clearly demonstrates a lack of understanding of how the car market actually works (and, quite clearly, indicates Gruber didn't even read the actual decision quoted above). In fact, exactly because car manufacturers have a de facto monopoly on their own products, they are legally obliged to open up their specifications to allow other companies to manufacture competing, off-brand parts and to allow third parties to service and maintain the cars according to the manufacturer's own specifications.
As I've argued before, there's absolutely no reason why the technology world should be treated any differently. Computers have become integral parts of our society, much like cars, and as consumers we should not be forced into relying on just one company for servicing, maintaining, and using them. It's high time we stop treating technology companies like special little flower children, and force them to grow up and become real companies with real responsibilities.
In 1999, armed with a brand new copy of Metrowerks Codewarrior and a PowerMac running Mac OS 8.5.1, I wrote a basic implementation of Minesweeper to test out the Powerplant application development environment. It's the oldest project of mine that I've kept, so I wanted to see if I could get it running again for the first time in 17 years.
There's no Swift or Objective-C code in this article but there are disk-eating koalas, deliberately misspelled cities, Zernike polynomials, Cocoa software (but not the Cocoa you're thinking of), resource forks, master pointer blocks and in the end, I finally earn the admiration of my family.
Great, entertaining story, you learn something, and it mentions BeOS. I can't think of anything that would make this story even more likely to get posted on OSNews.
The Nintendo Switch will be released March 3 worldwide for $299, Nintendo announced today during a press briefing in Tokyo.
Nintendo will sell the Switch for 29,980 yen in Japan. In Europe, the price will vary by retailer. The Switch will be available in two configurations: one with gray Joy-Con controllers, and the other with neon red and blue Joy-Con devices. Otherwise, the hardware will be the same: 32 GB of internal storage with a 720p touchscreen.
I'm somewhat curious about the hardware, somewhat interested in the new Zelda they showed off, but I'm appalled at the pricing in Europe (you'll be plonking down around €400 for the console and a game), and disappointed in the weak launch line-up and pretty meagre collection of games they showed off for the coming year.
The Mario and Zelda franchises have basically become like Call of Duty - every year, we get pots, remakes, of a new game with a few new mechanics, and that's it. There's nothing wrong with that - if people enjoy them, they enjoy them, and that's great - but I feel like Nintendo could be doing so much more than this.
As some of you may undoubtedly know, I'm a bit of a sucker for Palm OS. These past few years, I've been busy collecting ROMs for the Palm OS emulator and simulator, making sure I have all the major Palm OS releases covered. There's really not much of a reason to do this - I have working devices which are a much better option than the emulators/simulators in most cases - other than to have a complete collection I can keep around forever.
From top left to bottom right, you're looking at Palm OS 1.0, 2.0, 3.0, 3.5, 4.0, 5.3 (a Palm Zire ROM), 5.4.9 (the last released version of Palm OS available on real devices), and Palm OS 6.1.0 Cobalt (the last version of Palm OS; no 6.x device has ever been released). This is a pretty complete collection, and while it doesn't contain every released version of Palm OS, it covers the most important ones, and provides a great overview of the development of the operating system.
One important version is actually missing from this screenshot: Palm OS 5.5, whose official name is actually Garnet OS 5.5. Garnet OS 5.5 was developed by ACCESS (current owner of Palm OS and the associated IP), but was never released on or for devices - its sole function was to serve as the operating system running inside the Garnet VM. Garnet VM was a virtual machine developed to allow Palm OS applications to run on the ACCESS Linux Platform, a Linux-based mobile operating system that never gained any traction; no ALP devices were ever released.
As some of you may remember, Garnet VM was also released for Nokia's Maemo. I have a Nokia N900 (maybe even two) that can run Garnet VM, and while it's no longer available from ACCESS itself, it's easy to find all around the web if you know where to look. I'm not sure if my N900 is properly set up (I think it is), but it would be trivial for me to install Garnet VM on it and play with it.
So, between my Palm/CLIÉ devices and all these emulators/simulators, every major Palm OS version seems covered, right? Well, no - not entirely. There's quite a few exotic devices, such as the AlphaSmart Dana, the TapWave Zodiac, or the Fossil Palm OS smartwatch, but those are disproportionately hard to come by. Setting those aside, I thought I had all my bases covered.
As it turns out, and entirely unbeknownst to me, ACCESS actually released the Garnet VM for Linux and Windows. After coming to the conclusion that this piece of software was entirely impossible to find online (try it), q3hardcore came to the rescue once again, and uploaded his or her copy of the package online. Questionable legality aside, I didn't have to think twice.
The purpose of the Garnet VM for Linux and Windows was to allow Palm OS application developers to test their Palm OS applications to see if they would run on the Garnet VM included in the ACCESS Linux Platform, and make changes if needed.
This Garnet VM is an amazing piece of technology. It's the Palm OS userland - version 5.5.0 - running on a Linux kernel running on an ARM emulator running on Windows or Linux. The ARM emulator in question is called Janeiro, and it emulates a Zylonite (PXA320) development board, revision B1. As it boots up, there's zero indication that it's running a Linux kernel - the X 'cross' appears briefly (at least, it looks like the X cross), but that's it.
The major difference between the Garnet VM and the Palm OS 5.x and 6.x simulators is that while the simulators run x86 Palm OS, Garnet VM runs an ARM Palm OS userland atop an ARM Linux kernel. This means - at least, in theory - that ARM Palm OS applications should run decently well on Garnet VM, something you can't do with the Palm OS simulator, because they would need to be recompiled to x86. I say 'in theory', because the Garnet VM documentation notes that not all Palm OS libraries and components are present, and that only "well-behaved" applications are compatible.
I've only had access to the Garnet VM for Windows for a short while, and I haven't yet had the time to really dive into it. For instance, I've yet to figure out how to get applications to run inside the VM, since the usual methods don't seem to want to cooperate. I'll spend some more of my free time on playing with it over the coming weeks to better figure out how it all works.
In any event, the Garnet VM for Windows and Linux is a unique piece of computing history, and I am absolutely delighted to be able to add it to my collection of Palm OS memorabilia. I've briefly considered zipping up all the emulators, simulators, and ROMs I have into a nice preconfigured, documented package for people to play with, but that's not something I can do for obvious copyright, trademark, and patent reasons. Most of this stuff isn't particularly hard to find, but it does require a bit of Palm experience to put it all together and document it. I don't think I'll ever get permission from ACCESS, so that's the end of that idea.
Still, I think it's important that I continue to collect these Palm OS ROMs and emulators/simulators, because as the years go by, more and more Palm devices will start to break down or get lost, leaving us without to ability to experience this amazingly lovable operating system.
A year ago, we set out to explore what web browsers might look like in years to come. Now, you can try Opera Neon - a concept browser that gives you a glimpse into the future of desktop browsers.
A little too quirky for my tastes, but hats off to Opera for trying out new approaches -browsers feel dead and lifeless at the moment.
I don't think we'll ever see Half-Life 2: Episode 3, and the cliffhanger conclusion makes Half-Life 3 unlikely as well. The best chance of Half-Life getting a second wind will likely come if J. J. Abrams and Bad Robot can get the Half-Life film to screen. If that comes to fruition, and it doesn't bomb like almost every game movie before it, maybe, just maybe there's a chance of Gordon Freeman’s story continuing. Roll your eyes at the movie mention if you want, but how else will this franchise get a pulse again?
The interview you are about to read sheds some insight into how Valve works as a developer. Yes, someone at Valve could just say, "Let's make another Half-Life" and do it, but there are huge risks and hurdles involved in doing that. Prior to this interview, I was in the camp of, "Valve just doesn't get it." Now I'm in the camp of, "Valve is probably doing the right thing, but it's disappointing."
This interview opened my eyes to Valve's unique way of developing games, but also provided a bit of closure for someone who wants to see Half-Life continue. In the days before publishing this story, I reached out to Valve one last time for comment, but my request went unanswered. Without further delay, here's the interview.
This is a must-read.
That's where the company's new software tool Qbsolv comes in. Qbsolv is designed to help developers program D-Wave machines without needing a background in quantum physics. A few of D-Wave's partners are already using the tool, but today the company released Qbsolv as open source, meaning anyone will be able to freely share and modify the software.
"Not everyone in the computer science community realizes the potential impact of quantum computing," says Fred Glover, a mathematician at the University of Colorado, Boulder who has been working with Qbsolv. "Qbsolv offers a tool that can make this impact graphically visible, by getting researchers and practitioners involved in charting the future directions of quantum computing developments."
VentureBeat has a great, in-depth sourced look at the rise of and fall of Ara, Google's modular phone project. One paragraph in particular stands out to me.
"One of the modules that we were working on was basically like a tiny aquarium for your phone," said the source. "It was a little tiny biome that would go inside of a module and it would have a microscope on the bottom part, and it would have live tardigrades and algae - some people call them water bears. They are the tiniest living organism. We had this idea to build a tardigrade module and we'd build a microscope with it. So you'd have this app on your phone and you could essentially look at the tardigrades up close and watch them floating around." Brooklyn-based art, design, and technology agency Midnight Commercial conceived the idea, and was commissioned by Google to build it, demonstrating the depth of what developers could create.
If the people working on Ara had the guts to come up with and actually build things like this, they were on the right track. This is exactly the kind of crazy, outlandish stuff that would be a perfect fit and marketing gimmick for a crazy, outlandish product like Ara.
I am incredibly sad that Ara has been cancelled. I realise full well it would never be the kind of massive product like the Galaxy series or the iPhone, but I don't care - I just really, really like the idea, the concept, and the possibilities, mass appeal be damned.
The beauty of the internet: there's always someone else who is also interested in the things you're interested in. It turns out, even people who are working on trying to bring Mac OS 9 to the PowerPC G5 can find each other online. Now, it's important to note that even the people themselves acknowledge that this project is a very, very long shot and unlikely to succeed - but that doesn't mean it isn't worth trying and learning something along the way.
This project (we call it "CountDown G5") is ambitious, sure, and unlikely to succeed. But a few things make it worthwhile:
- I am learning a lot about low-level kernel programming, which I find fascinating as a hobby.
- We are crafting a build system in MPW, inspired by that source leak, for very low-level assembly and linking of a NewWorld ROM. This will be useful to other hackers in the future.
- We have an intermediate goal of increasing the usable logical address space on OS 9 to near the 2 GB hardware limit.
- The G5 isn't all that different. It has facilities for running 32-bit OSes, and early G5s thankfully left the Block Allocation Table mechanism intact.
Be sure to follow the thread on the forum if you're interested in this type of exotic hacking.
Meanwhile, also definitely 100% be sure to follow Steven Troughton-Smith, who, over the past few days, has been doing an absolutely crazy amount of work on things that go far beyond my comfort zone (he pointed the above thread out to me just now). He's been investigating all the work the Qemu people have been doing on PowerPC emulation, and he's trying to get all the early and often exotic Mac OS X builds to boot on Qemu. This includes things like altering and recompiling BootX, diving deep into Open Firmware to remove a number of 'fixes' put in place that prevented early OS X versions from booting, and tons of other things.
Jehanne is a new distributed operating system designed for programmers. The core values that lead the development are simplicity and security. Jehanne is a fork of Harvey (which in turn is a fork of Plan 9 from Bell Labs merged with Nix's kernel sources) but diverges from the design and conventions of its ancestors whenever they are at odds with its goals. Read about development progress made in 2016.
Today we are excited to be releasing Windows 10 Insider Preview Build 15002 for PC to Windows Insiders in the Fast ring. This is a BIG update so please take time to look through all of the new changes we detail below.
Usually, these new Windows 10 Insider Preview builds are a pretty low-key affair, but this one has a ton of changes, new features and fixes, and the blog post does a good job of summarising them. They cover things like improving resizing performance, various Edge updates, tile folders in the Start menu, a new share UI, and the first steps towards replacing the dreaded Character Map with a new, faster way of inputting special characters.
It really feels like Microsoft is at the point where they can address the various relatively minor things that start adding up when you use Windows.
Rux's goal is to become a safe general-purpose microkernel. It tries to take advantage of Rust's memory model - ownership and lifetime. While the kernel will be small, unsafe code should be kept minimal. This makes updating functionalities of the kernel hassle-free.
Rux uses a design that is similar to seL4. While there won't be formal verification in the short term, it tries to address some design issues of seL4, for example, capability allocation.
The code is very approachable for anyone interested in capability-based microkernel design.
Back before all-digital music, back before the Digital Compact Cassette, back before even the Digital Audio Tape existed, there was a strange audio device that briefly captured the imagination of Hi-Fi freaks across the world. The Elcaset, as it was called, was an enlarged cassette that started in Japan, wove its hidden, spinning spools around the world, and then finished, appropriately enough, in Finland.
As someone who swore by MiniDisc up until quite recently, I love obscure audio formats. This article is from the summer of last year, but I only came across it just now thanks to Atlas Obscura.
Viva Amiga is a wonderful look at the the history of the platform, the people who built it, and the users who loved it. The opening title says it all: "One Amazing Computer. One chance to save the company. One chance to win the PC wars." This message sets the stage nicely for a dramatic and passionate tale.
You can watch the documentary online, but it isn't free.