tych0

7 ms·

1.
by tych0 2mo ago
I live in the southwest, didn't realize this data was available, so thank you. It would be super interesting to have a (heat) map of it all.
2.
by tych0 4mo ago
Hey Andrew, I've been an admirer of your work for a long time. Sounds awful, glad you are on the mend.
3.
by tych0 10mo ago
[disclaimer, maintainer here] > Doesn't this require the environment to be owned by root? Doesn't it make more sense to leave things that are in /opt as root-owned anyway? (Or at least, change them back after running the i
4.
by tych0 3y ago
> Hi Tycho. I was The Guy at LSS who tested positive for COVID about 12 hours after we sat next to each other at that Japanese restaurant in Vancouver the week before last. I really hope you didn't catch it. So far, to my knowledge,
5.
by tych0 3y ago
> Or am I misunderstanding you? Oh, I see, you're suggesting exactly, > (Another maybe-interesting thing would be to just delete that check.) I agree.
6.
by tych0 3y ago
> Couple of things: 1. Should prepare_to_wait_event check if the task is in PF_EXITING, and if so, refuse to wait unless a specific flag is provided? I'd be curious if you just add a kprobe to prepare_to_wait_event that checks for P
7.
by tych0 3y ago
I think they definitely should not. I've considered sending a patch that adds a WARN() or some syzkaller test for it or something, especially now that I've seen it in other filesystems.
8.
by tych0 3y ago
Author here (hi Sargun), it's not really about rediscovering killable vs. unkillable waits, and any confusion is probably a result of my poor writing. The crux of it is that once you've called exit_signals() from do_exit(), signal
9.
by tych0 4y ago
docker-the-company maintained https://github.com/linuxkit/linuxkit when I worked there. I have no idea who maintains it now, but it looks like it is still active (presumably still docker-the-company, since their adopte
10.
by tych0 4y ago
And at least in SBF/Alameda's case, they did, and you can google it. IIUC it was basic arbitrage, the hard part was figuring out how to interface with Japan's banks. Maybe the guy is a bad dude, I don't have a horse in t
11.
by tych0 4y ago
Use the freezer cgroup to freeze everything, then kill it all off however you like.
12.
by tych0 4y ago
> Could it be that some Oracle employed contributors are using a different email when submitting pull requests? Yes, and if you contribute from an e-mail address that Greg K-H's scripts don't understand, you get an e-mail from
13.
by tych0 4y ago
> Note that seccomp has limited visibility into recvmsg / sendmsg args because bpf can't dereference syscall arg pointers. I guess landlock can't help you here since it is still mostly about filesystem access right now, bu
14.
by tych0 4y ago
Hi Matt, speaking of PyCon, thanks for your talk on Qtile many years ago. It remains one of the funniest lightning talks I've seen, and also influenced my talk style to some degree. https://youtu.be/r_8om4dsEmw
15.
by tych0 4y ago
I have news for you: drivers don't think laws apply to them either. I've nearly been killed several times because of it, and I know people who have been killed. RIP Dan Spira, one of the faster guys in Denver at the time of his de
16.
by tych0 4y ago
> Files that were previously in /usr/bin or in /bin can now be found in EITHER of these locations, since one symlinks the other. So no previous expectation was really broken. I don't know, I just hit breakage the othe
17.
by tych0 5y ago
Fastmail has great calendar (CalDAV), contacts (whatever the open protocol for this is) support in addition to their e-mail. I migrated from Google Calendar & friends several years ago and have had no issues.
18.
by tych0 5y ago
The problem with this argument is that the set of programs that just fork() and then exec() is fairly small. Sure, shells are small and do this, but then the article argues that shells are a good use of fork(). In larger programs, you'
19.
by tych0 5y ago
In my experience, integration with products is not really that hard. I've used sqlite3 bindings in half a dozen languages over the years, and they are generally fairly robust.
20.
by tych0 5y ago
Yeah, I'd just use whatever the output of ./scripts/get_maintainer.pl says. It will also suggest any recent committers to that area of the code, which I've found useful in the past. Usually I put the maintainers as To:,
21.
by tych0 5y ago
I'd say sending the patch with git send-email --in-reply-to=<the header of your last email> is good. A patch is much easier to apply than write :)
22.
by tych0 5y ago
Standard advice is to wait two full weeks, then bump your thread (or rebase the patch and send a v2 if there's new conflicts with the maintainer's tree).
23.
by tych0 5y ago
This is pretty cool, though it would be nice if it worked with caldav instead of just google calendar :)
24.
by tych0 5y ago
They wouldn't accept my .pizza e-mail address as valid though, so there's still room for improvement :)
25.
by tych0 5y ago
Companies/directors can (and do, see e.g. Theranos/Elizabeth Holmes) settle without admitting fault. Presumably the goal is to lower the number of three letter agencies investigating you.
26.
by tych0 5y ago
Seems like GP might be talking about Joe Rogan.
27.
by tych0 5y ago
I use it a lot to figure out why things fail. For example, what if you get an -EPERM from mount()? Was it denied by seccomp, an LSM, because you don't own the user namespace that owns your mount namespace? strace will tell you it faile
28.
by tych0 5y ago
You might try it again later; my coworkers and I have been having problems registering all morning.
29.
by tych0 5y ago
I think you get tickets with BRK.B too. A friend of mine sells the tickets he gets on ebay and says that's a bigger dividend than the stock will ever pay :)
30.
by tych0 5y ago
> Or does this refer to something else, besides safety checks? I think it largely refers to the Spectre + Meltdown class of attacks, which caused the kernel to introduce a whole class of fixes (retpolines, etc.).

More ›