It looks like it's using tcp flow tuple + tcp_seq to join things.

BPF programs attached to syscalls (via kprobe or fentry) can read arguments via helpers (bpf_probe_read_{user,kernel}). Seccomp uses "classic BPF" which has no concept of helpers or calls.

> The currently available objective evidence is not sufficient to conclude whether or not there is a widespread public health concern related to servicing, including by third party servicers, of medical devices that would justify imposing additional/different, burdensome regulatory requirements at this time. Rather, the objective evidence indicates that many OEMs and third party entities provide high quality, safe, and effective servicing of medical devices.

https://www.fda.gov/media/113431/download

From my personal experience poking at a CPAP machine, there's nothing magical about it. All the sensors and active elements I could track down are available from the respective manufacturers in large quantities. The CPU is a freaking off the shelf STM32F4 with the jtag header still on the board. This is not some impossible to debug hyper-integrated design.

Comments URL: https://news.ycombinator.com/item?id=18321928

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=15250920

Points: 3

# Comments: 1

Still, it's not as tested as, say btrfs and ext4. Can't wait to see its particular quirks.

In particular, everything is compiled down to lookup tables and hash tables within each odex/oat. Your point still stands but the hit is much lower than you would think and given the slow speed of the superfluous reads, it ends up being a net positive for A LOT of cases.

1) fsync cost. Yes, fsyncs are dangerously slow in any Android app. (SQLite for example is a common culprit. Shared Prefs are another). HOWEVER, it's possible that flushes cause reads to be queued behind them (either in the kernel or on the device itself) which is even worse because

2) Random read cost is super super important. Android mmap's literally everything and demand paging is particularly common AND horrendous as a workflow. To add insult to injury, Android does not madvise the byte code or the resources as MADV_RANDOM, so read-ahead (or read-around) kicks in and you end up paging in 16KB-32KB where you only wanted 4KB.

Also, history has shown custom flash-based file system on Android to be a world of pain. yaffs, jffs have some pretty atrocious bugs/quirks. I'd much rather see the world unify on common file systems, optimized for flash-like storage, rather than OEMs shipping their own in-house broken file "systems" (I'm looking at you, Samsung).

I call bullshit. There's no reason Google can't update everything AOSP-y in /system - libc, libart, libwebkit etc.

> Google (and Apple and Microsoft) can totally do it for devices that manufactures and maintains on its own

That's a low bar. When you buy a Dell laptop, you continue to receive updates from Microsoft. This is the bar we should hold Google to.

As for the certification process, surely having one update that ships to N models is easier to test than N updates shipping to N models?

Comments URL: https://news.ycombinator.com/item?id=10965347

Points: 2

# Comments: 0

It's really fascinating stuff.

Comments URL: https://news.ycombinator.com/item?id=9963327

Points: 3

# Comments: 0

I sometimes wonder whether I should continue my education somewhere like Oxford, just so I can experience the focused concentration of a library again.

I'm completely in awe of the feedback loop here. It even compiles and swaps code while you're in the game!

In this business, the big competitors all reserve a bunch of rooms in the hotels and manage their booking themselves. The hotel is then not allowed to touch these rooms.

The model here was to give the hotels a reception-desk piece of software and have them use it to maintain availability. A lot of the hotels that signed up had nothing like this, so it was definitely a win for them. Armed with exact availability, you can have a much better booking system (and of course, if the hotel only wanted to give you a chunk of their rooms, they're perfectly capable of doing that).

Hotels can sign up on their own (including local bank details, etc) and just need to be reviewed before showing up on the site. It supports i18n, scheduled payments, lots of bells and whistles.

The fact of the matter is that this failed because of market reasons (too small a market, dominated by big players, primarily) but it may have a niche somewhere else on this planet. :)

My parents attempted running a holiday-booking venture that didn't go anywhere. In the process, they had a fairly advanced web app built with things like custom refund policies and self-service registration for the hotels.

This web app cost a lot and it would be nice to get back some of that money, so how would you go about recovering the cost?

Any failed business sale forums I don't know about?

Comments URL: https://news.ycombinator.com/item?id=8093796

Points: 51

# Comments: 22