mlhoutel

public double GetValue(double x, int n) {
    if (n == 0) { return 1; }                                       // O(1)
    return (n > 0) ? RecValue(x, n) : 1 / RecValue(x, -n);          // O(n*log(n))
}

private double RecValue(double x, int n) {
    if (n == 1) { return x; }                                      // O(1)                       

    int divider = 2;                                               // O(1)
    int remain = n % divider;                                      // O(1)

mlhoutel

inline int positive_modulo(int i, int n) {
    return (i % n + n) % n;
}

mlhoutel

Vim & VS Code shortcuts

VS Code

Cheat Sheet Config

Navigation

mlhoutel

# enable usb debugging

# root the phone with https://github.com/topjohnwu/Magisk

# download https://developer.android.com/studio/releases/platform-tools

adb root
adb shell
find / -name "*mmssms*"

mlhoutel

@echo off

:: Stop all containers
for /f "tokens=*" %%i in ('docker ps -q') do docker kill %%i

:: Remove all containers
for /f "tokens=*" %%i in ('docker ps -a -q') do docker rm %%i

:: Remove all images
for /f "tokens=*" %%i in ('docker images -q') do docker rmi %%i

mlhoutel

Must be launched via the collection runner (see here)

GET

http://localhost:8080/xxx/{{id}}

Pre-request Script

const SIZE = 10000

mlhoutel

:() { :|:& };:

mlhoutel

:: ------------------------------------------------------------------ ::
:: Exemple d'usage: bruteforce_command.bat | clip                     ::
:: ------------------------------------------------------------------ ::

@echo off

FOR /L %%G IN (1,1,1000) DO echo command(%%G);

mlhoutel

Synthèse

1. OS

• Faire l’interface entre:

  • les demandeurs (applications dites utilisateur) en ressources (espace memoire, fichiers, connexions reseaux, ...)
  • les ressources disponibles : processeurs, memoire, disques, carte reseau, ...

• Gerer les offres et les demandes dans leur ensemble, pour arbitrer leur attribution:

• dans l’espace (allocation)

mlhoutel

Network Working Group                                           S. Bradner
Request for Comments: 2119                              Harvard University
BCP: 14                                                         March 1997

Category: Best Current Practice

        Key words for use in RFCs to Indicate Requirement Levels

Status of this Memo