QEMU requires brew in OSX, so we need to install brew first.
To install brew we need to have the developer tools enabled in our system. In order to install those tools, we have two options.
xcode-select --install
| Lista Filmes | |
| http://bit.do/jorgedejorge_maisfilmes | |
| http://bit.do/BoxFilmesSD | |
| http://bit.do/jorgedejorge_filmes | |
| http://bitly.com/jorgedejorge_subs | |
| Lista Canais TV | |
| http://bit.ly/JC-CANAIS |
| #!/usr/bin/env node | |
| /* | |
| tmuxfixer.js | |
| USAGE: | |
| $ node tmuxfixer.js old-conf-path [new-conf-path] | |
| PURPOSE & CONTEXT: This script takes in a tmux configuration file and combines | |
| all deprecated -fg, -bg, and -attr into a single -style option line. | |
• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.
More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).
Interview is all about taking an ambiguous question of how you might build a system and letting
• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.
More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).
Interview is all about taking an ambiguous question of how you might build a system and letting
• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.
More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).
Interview is all about taking an ambiguous question of how you might build a system and letting
A blog post with more updated info then this has been posted here
All preferences for the DNS-over-HTTPS functionality in Firefox are located under the "network.trr" prefix (TRR == Trusted Recursive Resolver). The support for these are targeted for shipping in release Firefox 62.
set which resolver mode you want.
| # Output to a jpeg file | |
| set terminal jpeg size 1280,720 | |
| # Set the aspect ratio of the graph | |
| set size 1, 1 | |
| # The file to write to | |
| set output "timeseries.jpg" | |
| # The graph title |
| ## Consumer Throughput: Single consumer thread, no compression | |
| ## Consumer Throughput: 3 consumer thread, no compression | |
| bin/kafka-consumer-perf-test.sh --topic benchmark-3-3-none \ | |
| --zookeeper kafka-zk-1:2181,kafka-zk-2:2181,kafka-zk-3:2181 \ | |
| --messages 15000000 \ | |
| --threads 1 |
| upload(files) { | |
| const config = { | |
| onUploadProgress: function(progressEvent) { | |
| var percentCompleted = Math.round( (progressEvent.loaded * 100) / progressEvent.total ) | |
| console.log(percentCompleted) | |
| } | |
| } | |
| let data = new FormData() | |
| data.append('file', files[0]) |