News for hackers. Stuff that matters.

hugelgupf

You should be able to disable write protection on the firmware flash using a suzyq cable to enable closed case debugging as well, and from there disable write protection. The screw is not the only way
I don't really get their headline.

Google extended the AUE to 8 years. They're complaining that most Chromebooks only have 4 years of software life left. Are they buying devices released 4 years ago? Or refurbished devices?

[twitter OP] This is true. Appears once a day or so, you hit OK. Sometimes during a show you're watching, sometimes while it starts up. Don't know if it becomes blocking some day...
[OP here] I filed a thing for them and this person will get it in front of the right people. I have more faith in that more than generic Apple support anyway.
Why on earth did he agree to those FBI interviews where he admitted all this?
Re:Some items from my “reliability list” on Thursday July 25, 2019 @02:45PM (#20528198)
It is a failure, but not of the HTTP service. It's a failure of the RPC call.

404 means "this API doesn't exist", not "the API exists but it returns an error"

Re:Gut bacteria may offer a treatment for autism on Saturday December 08, 2018 @02:20PM (#18636980)
Brain fog, intestinal inflammation. Sounds so very familiar.

Do you have research notes, on methodology and things tried? I'm now very curious for myself.

Re:GoAWK: an AWK interpreter written in Go on Saturday November 17, 2018 @11:54PM (#18478937)
here are some basic linux tools in Go:

https://github.com/u-root/u-root

Re:Linux compatibility in IncludeOS on Wednesday November 07, 2018 @03:52AM (#18397896)
That sounds much more attainable than what the blog post suggested - sorry if I took that the wrong way!
Re:Linux compatibility in IncludeOS on Wednesday November 07, 2018 @03:17AM (#18397755)
Given what I just read about IncludeOS (I'm not really familiar), it feels like implementing as much of musl as possible is probably the best you can do compatibility wise. There are going to be a lot of Linux features simply incompatible with includeOS, so claiming that 400 syscalls will be implemented is unlikely.

That said - why do you have to get musl compatibility by implementing the Linux syscalls? Is contributing to musl an option?

Re:Linux compatibility in IncludeOS on Wednesday November 07, 2018 @03:08AM (#18397722)
The number of system calls says close to nothing of the actual API surface present here. It's a poor measure. What actually matters is: what can I run?

That said, 42 is not enough to run a lot of applications.

It'll be interesting to get to the point where they can run a language's runtime or unit tests.

Take it from someone who worked on gVisor: this is gonna take a long time, and eventually you'll end up with a system that's just Linux. You'll end up either being bug-for-bug compatible, which means bringing in loads of compatibility code and architecting your kernel just like Linux, or you'll end up having to change applications (and then you're not all that compatible anymore).

Neither are fun or sustainable compatibility stories. You'd probably actually get Linux apps to work on a random OS faster & nicer by porting gVisor.

> Moreover, since implementing a system call is typically pretty simple [...]

You're in for a fun ride, folks.

Re:Making sense of the alleged Supermicro motherboard attack on Friday October 05, 2018 @03:01PM (#18150792)
I think the board that is pictured by Bloomberg is just an illustration.

For example, Elemental never used that board. See my tweets here for the actual specs: https://twitter.com/hugelgupf/status/1048160794565861377?s=1...

Elemental boards come with GPUs. The blade pictured has neither GPUs nor PCIe.

Do you have a source for the Norwegians?
See the "Serverless Containers" section on https://www.google.com/amp/s/gweb-cloudblog-publish.appspot....

It's still in alpha, so Google is not advertising it wide. It was announced about a week before Zeit's Serverless docker at GCP Next.

Disclaimer: I work at Google and I've had some involvement in the tech behind this.

Re:Go 1.11 Beta 1 is released on Tuesday June 26, 2018 @08:31PM (#17404986)
Almost complete, but stalled, and based on Go 1.8: https://github.com/riscv/riscv-go
Haskell is 28 years old.
Re:Open-sourcing gVisor, a sandboxed container runtime on Wednesday May 02, 2018 @01:25PM (#16979144)
You can indeed safely run containers as root inside the sandbox. The UID/GID you run as is configurable.
Re:Open-sourcing gVisor, a sandboxed container runtime on Wednesday May 02, 2018 @01:23PM (#16979126)
You can implement a custom file system as a separate process (called Gofers) and have the sandbox connect to that. The custom file system has to adhere to the p9.File API (see pkg/p9/file.go) - the protocol is an extended version of 9P2000.L.

(I work on gVisor.)

No, what sigjuice said is right. The name was derived off u-boot, though, and u-root can be used (and is in use) with LinuxBoot.
Shameless self-promotion: also take a look at https://github.com/u-root/u-root :)

(The gokrazy and u-root people all work at Google, I just contacted them to see if we can help each other. Not a competing project.)

They are effectively measuring how fast AWS infrastructure can reach whatever it needs (VM?) for each language.

But these are not even cold start times. I'm assuming after the first request this is using the same VM (/backend job, whatever) to reply, so now it just depends on latency to get to that VM. (I'm assuming the runtimes' ability to return "200 OK" is similar and the latency of that is negligible compared to AWS infra that is involved.) Not completely meaningless, but not super useful either, esp without any details while making those bold statements. This is not "Go is equal to Java". This is "AWS Lambda infrastructure for Go is comparable to AWS infra for Java". Article is unclear on that.

Maybe this tells us AWS lambda backend infra is way different for .NET Core than Go and Java? ¯\_(ツ)_/¯

Re:Strace – My Favourite Secret Weapon (2011) on Sunday February 11, 2018 @03:41PM (#16354680)
Binaries can also use dlopen to open libraries that aren't listed by ldd.
Re:Plan 9 public grid on Saturday February 03, 2018 @03:55AM (#16296854)
Seems to be down right now, so not sure what services are implemented, but... someone should port this stuff to upspin. :)
Re:LinuxBoot: Linux as Firmware on Tuesday January 30, 2018 @11:16PM (#16271247)
The front page of LinuxBoot has links to talks' videos and slides.
Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @09:43PM (#16262507)
They didn't create this page. You can follow the development of the page at https://github.com/linuxboot/linuxboot.org
Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @06:12PM (#16261453)
Booting via kexec is the intended idea here. Theoretically, it should be possible to boot any other OS with kexec. We may have to test that assumption for this project...
Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @05:25PM (#16261193)
You could have a tiny initramfs that mounts the disk you want with your actual init and then switch_root to that. You'd have the kernel from flash, and init from disk.
Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @05:22PM (#16261174)
We also have a mode that rewrites all commands' sources given so it can be compiled into one binary. It ahem needs some improvements, though :)
Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @04:07PM (#16260619)
Yes, there should be firmware updates for the kernel in flash. (And we haven't really figured out how to handle that yet.)

But such firmware updates likely have different constraints and a different schedule than your kernel-in-production updates. People will likely have much different requirements for the kernel in flash than for the kernel in production. It may be that for your use case and threat model, they'd be the same - but that's up to you to figure out and decide.

Re:LinuxBoot: Linux as Firmware on Monday January 29, 2018 @03:27PM (#16260364)
We should clarify that. Our example is an OCP Winterfell node, where boot time went from 8 minutes to 20 seconds.

Older »