Electric Monk

https://www.electricmonk.nl/log/2015/06/22/keep-your-home-dir-in-git-w… has been working nicely for me on multiple computers.

The Red Book [1] (recently updated) is a good overview and has lots of useful references. Some might be too high-level, but this paper (really a short book!) is a good start at what makes up a database: "Architecture of a Database System"[2]. Keep in mind that the scope of a "database" can be huge, so you might want to start really small, e.g., writing a basic key-value store that can support things concurrent reads & write, isolation, etc. It all depends on what interests you. -- [1] http://www.redbook.io/ [2] http://www.electricmonk.nl/data/freeitebooks/fntdb07-architecture.pdf

"You've been smoking something really mind altering, and I think you should share it. x86 virtualization is about basically placing another nearly full kernel, full of new bugs, on top of a nasty x86 architecture which barely has correct page protection. Then running your operating system on the other side of this brand new pile of shit." The rest of the rant is here: http://www.electricmonk.nl/log/2007/10/25/virtualization-security/

> > lack of real GC for data structures with cycles > This has not been true since (AFAIK) Python 2.0, > which was released 12 years ago. Sorta. It seems that CPython still can't garbage collect objects in cycles if those objects have a __del__ method. See http://www.electricmonk.nl/log/2008/07/07/python-destructor-and-garbag… Or see gc.garbage, from http://docs.python.org/release/2.7.3/library/gc.html

It always amazes me that after all these years, Linux still hasn't fixed this. In my experience, any program that overloads I/O will make the system grind to a halt on Linux. Any notion of graceful degradation is gone and your system just thrashes for a while. My theory about this has always been that any I/O related to page faults is starved, which means that every process spends its time slice just trying to swap in its program pages (and evicting other programs from the cache, ensuring that the thrashing will continue). I've never gotten hard data to prove this, and part of me laments that SSDs are "fast enough" that this may never actually get fixed. Can anyone who knows more about this comment? It seems like a good rule inside Linux would be never to evict pages that are mapped executable if you can help it. Has anyone experimented with ionice or iotop? http://www.electricmonk.nl/log/2012/07/30/setting-io-priorities-on-lin…

Google has a history of not living up to that particular claim: https://www.electricmonk.nl/log/2005/12/21/how-google-fucked-up-usenet… https://thenextweb.com/news/google-groups-stopped-indexing-usenet-news… https://www.vice.com/en/article/jp5a77/google-a-search-company-has-mad… https://www.reddit.com/r/usenet/comments/3ggogo/google_has_lost_old_us… https://groups.google.com/g/comp.arch.embedded/c/zKo883p9AJQ

A good place to start is https://www.privacytools.io/#browser Spend some time using uMatrix (much better than NoScript these days). If you're running uMatrix you do not need NoScript. Some good documentation in regard to uMatrix: https://www.electricmonk.nl/docs/umatrix_tutorial/umatrix_tutorial.htm… https://github.com/gorhill/uMatrix/wiki/The-popup-panel https://github.com/gorhill/uMatrix/wiki/How-to-block-1st-party-scripts… https://github.com/gorhill/uMatrix/wiki/How-to-create-rules-which-appl…