Update of the site
parent
e6c02525ca
commit
a5c65a3694
|
@ -1,4 +1,4 @@
|
|||
baseurl = "https://blog.spanskiduh.xyz/"
|
||||
baseurl = "https://blog.spanskiduh.dev/"
|
||||
languageCode = "en-us"
|
||||
# Add it only if you keep the theme in the `themes` directory.
|
||||
# Remove it if you use the theme as a remote Hugo Module.
|
||||
|
@ -79,7 +79,7 @@ paginate = 5
|
|||
missingBackButtonLabel = "Back to home page"
|
||||
|
||||
[languages.en.params.logo]
|
||||
logoText = "blog.spanskiduh.xyz"
|
||||
logoText = "blog.spanskiduh.dev"
|
||||
logoHomeLink = "/"
|
||||
|
||||
[languages.en.menu]
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Clipboard"
|
||||
description="click to read about Clipboard"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Compression"
|
||||
description="click to read about Compression"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Curl"
|
||||
description="click to read about Curl"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Dig"
|
||||
description="click to read about Dig"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Find"
|
||||
description="click to read about Find"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-17"
|
||||
author="spanskiduh"
|
||||
title="GIT"
|
||||
description="click to read about GIT"
|
||||
|
@ -38,3 +38,69 @@ You can also add `-v` flag to increase verbosity to get more details about liste
|
|||
### Switch to remote branch that is not on local computer
|
||||
|
||||
`git switch <branch_name>`
|
||||
|
||||
|
||||
### I had many reduntant commits on this branch how would I squash them?
|
||||
- If you have many redundant commits on your local branch and you want to squash them into a single commit, you can use the git rebase command with the interactive mode to rewrite the commit history.
|
||||
Here are the steps to squash redundant commits on your local branch:
|
||||
|
||||
First, switch to your local branch by running the following command:
|
||||
|
||||
git checkout your_local_branch
|
||||
Use the following command to start an interactive rebase:
|
||||
|
||||
```
|
||||
git rebase -i HEAD~n
|
||||
```
|
||||
|
||||
Replace n with the number of commits you want to include in the rebase. For example, if you want to squash the last five commits into a single commit, you would use git rebase -i HEAD~5.
|
||||
|
||||
This will open a text editor with a list of your recent commits. The word "pick" will appear before each commit. To squash the redundant commits, replace "pick" with "squash" or "s" for the commits that you want to squash into a single commit.
|
||||
|
||||
Save and close the file. Git will apply the changes and open another text editor to allow you to edit the commit message for the new squashed commit.
|
||||
|
||||
Edit the commit message as needed, then save and close the file.
|
||||
|
||||
Git will apply the changes and create a new commit with the squashed changes. If there are any conflicts, Git will pause the rebase process and prompt you to resolve them manually.
|
||||
|
||||
After you've resolved all conflicts, run the following command to continue the rebase:
|
||||
|
||||
```
|
||||
git rebase --continue
|
||||
```
|
||||
If you encounter any issues during the rebase process, you can use the git rebase --abort command to abort the process and return your local branch to its original state.
|
||||
Once the rebase is complete, your local branch will contain a single commit with the changes from the redundant commits squashed into it. You can then push your changes to your remote repository if needed.
|
||||
|
||||
|
||||
### I have a local branch, but the main git branch was recently updated and I want those changes to be included into my local branch. How would I do that?
|
||||
Here are the steps to follow to update your local branch using git rebase:
|
||||
|
||||
First, switch to your local branch by running the following command:
|
||||
```
|
||||
git checkout your_local_branch
|
||||
```
|
||||
|
||||
Fetch the latest changes from the main Git branch by running:
|
||||
```
|
||||
git fetch origin
|
||||
```
|
||||
This command will update your local copy of the main Git branch to match the version on the remote repository.
|
||||
|
||||
Use the following command to start the rebase process:
|
||||
```
|
||||
git rebase origin/main
|
||||
```
|
||||
|
||||
This will take the changes in the main branch and apply them to your local branch by replaying your local changes on top of them.
|
||||
|
||||
Resolve any conflicts that may arise during the rebase process. When there are conflicts, Git will pause the rebase process and show you which files have conflicts. You can then use a merge tool or a text editor to resolve the conflicts manually.
|
||||
|
||||
After you've resolved all conflicts, run the following command to continue the rebase:
|
||||
```
|
||||
git rebase --continue
|
||||
```
|
||||
This will apply the remaining changes and complete the rebase process.
|
||||
|
||||
If you encounter any issues during the rebase process, you can use the git rebase --abort command to abort the process and return your local branch to its original state.
|
||||
|
||||
Once the rebase is complete, your local branch will contain the changes from the main Git branch, and your local commits will be replayed on top of them. You can then push your changes to your remote repository if needed.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Locate"
|
||||
description="click to read about Locate"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="MPI"
|
||||
description="click to read about MPI"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Networking"
|
||||
description="click to read about Networking"
|
||||
|
@ -29,7 +29,7 @@ description="click to read about Networking"
|
|||
| ifconfig enp6s0 192.168.2.24 | ip addr add 192.168.2.24/24 dev enp6s0 |
|
||||
| ifconfig enp6s0 netmask 255.255.255.0 | ip addr add 192.168.1.1/24 dev enp6s0 |
|
||||
| ifconfig enp6s0 mtu 9000 | ip link set enp6s0 mtu 9000 |
|
||||
| ifconfig enp6s0:0 192.168.2.25 | ip addr add 192.168.2.25/24 dev enp6s0 |
|
||||
| ifconfig enp7s0:0 192.168.2.25 | ip addr add 192.168.2.25/24 dev enp6s0 |
|
||||
| netstat | ss |
|
||||
| netstat -tulpn | ss -tulpn |
|
||||
| netstat -neopa | ss -neopa |
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-25"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="SSH"
|
||||
description="click to read about SSH"
|
||||
|
@ -29,7 +29,7 @@ ssh-keygen -t ed25519 -f ~/.ssh/keys/id_ed2552_devel_server
|
|||
### Copy to remote
|
||||
|
||||
```bash
|
||||
ssh-copy-id devel@devel.hsrv -i ~/.ssh/keys/id_ed25519_devel_server
|
||||
ssh-copy-id -i ~/.ssh/keys/id_ed25520_devel_server devel@devel.hsrv
|
||||
```
|
||||
|
||||
### FAIL2BAN
|
||||
|
@ -67,3 +67,21 @@ oli@bert:~$ ssh tim
|
|||
oli@tim:~$ export DISPLAY=:0
|
||||
oli@tim:~$ firefox
|
||||
```
|
||||
|
||||
### Reverse SSH tunnel
|
||||
If you want some port that is behind the firewall, but exposed on the server.
|
||||
You can spawn a reverse ssh tunnel to that port issuing this command:
|
||||
|
||||
```bash
|
||||
ssh -L 8888:localhost:8888 -f -N hsrv_devel
|
||||
```
|
||||
|
||||
or: `ssh -L [LOCAL_IP:]LOCAL_PORT:DESTINATION:DESTINATION_PORT [USER@]SSH_SERVER`
|
||||
|
||||
read [here](https://linuxize.com/post/how-to-setup-ssh-tunneling/) more.
|
||||
|
||||
or forcily:
|
||||
|
||||
```bash
|
||||
ssh -L 8888:localhost:8888 -f -N hsrv_devel -o ClearAllForwardings=yes
|
||||
```
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="Tracks"
|
||||
description="click to read about Tracks"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="VFS"
|
||||
description="click to read about VFS"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-04"
|
||||
author="spanskiduh"
|
||||
title="VIM"
|
||||
description="click to read about VIM"
|
||||
|
@ -48,3 +48,25 @@ Comment Multiple Lines
|
|||
|
||||
### Nvim tree mappings
|
||||
` :help nvim-tree-default-mappings`
|
||||
|
||||
|
||||
## Marks
|
||||
|
||||
Add mark with `ma`
|
||||
|
||||
And then list them with `:marks`
|
||||
|
||||
Select the mark with `'x` where x is the character thas is next to the mark listed using `:marks` command.
|
||||
|
||||
|
||||
| Command | Description |
|
||||
|:---------:|:-------------------------------------------------------------:|
|
||||
| ma | set mark a at current cursor location |
|
||||
| 'a | jump to line of mark a (first non-blank character in line) |
|
||||
| `a | jump to position (line and column) of mark a |
|
||||
| d'a | delete from current line to line of mark a |
|
||||
| d`a | delete from current cursor position to position of mark a |
|
||||
| c'a | change text from current line to line of mark a |
|
||||
| y`a | yank text to unnamed buffer from cursor to position of mark a |
|
||||
| :marks | list all the current marks |
|
||||
| :marks aB | list marks a, B |
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="address_space"
|
||||
description="click to read about address_space"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="ansible"
|
||||
description="click to read about ansible"
|
||||
|
|
|
@ -0,0 +1,15 @@
|
|||
|
||||
+++
|
||||
date="2023-02-06"
|
||||
author="spanskiduh"
|
||||
title="autorandr"
|
||||
description="click to read about autorandr"
|
||||
+++
|
||||
# Autorandr
|
||||
|
||||
## Save current display setup
|
||||
`autorandr --save laptop`
|
||||
|
||||
## Automatically reload setup
|
||||
`autorandr --change` or `autorandr <profile>`
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="bash"
|
||||
description="click to read about bash"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="binary-patching"
|
||||
description="click to read about binary-patching"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="binary_vs_text_files"
|
||||
description="click to read about binary_vs_text_files"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="burpsuite"
|
||||
description="click to read about burpsuite"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="certs"
|
||||
description="click to read about certs"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="disk-usage"
|
||||
description="click to read about disk-usage"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="disk-utils"
|
||||
description="click to read about disk-utils"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-25"
|
||||
date="2023-02-09"
|
||||
author="spanskiduh"
|
||||
title="docker"
|
||||
description="click to read about docker"
|
||||
|
@ -257,3 +257,9 @@ basically add this segment to file `/etc/ufw/after.rules`.
|
|||
COMMIT
|
||||
# END UFW AND DOCKER
|
||||
```
|
||||
|
||||
|
||||
## Best flag for debugging dockerfile
|
||||
`docker compose --verbose up --build`
|
||||
But do not fuck up the order of the arguments!
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="emacs"
|
||||
description="click to read about emacs"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="exec"
|
||||
description="click to read about exec"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="ffmpeg"
|
||||
description="click to read about ffmpeg"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="forensics"
|
||||
description="click to read about forensics"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="fork"
|
||||
description="click to read about fork"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="gcc"
|
||||
description="click to read about gcc"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="gdb"
|
||||
description="click to read about gdb"
|
||||
|
|
|
@ -0,0 +1,12 @@
|
|||
|
||||
+++
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="hardware"
|
||||
description="click to read about hardware"
|
||||
+++
|
||||
# Hardware
|
||||
|
||||
## Display information about graphics cards
|
||||
|
||||
`sudo lshw -c video`
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="hydra"
|
||||
description="click to read about hydra"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="lxc"
|
||||
description="click to read about lxc"
|
||||
|
|
|
@ -0,0 +1,44 @@
|
|||
|
||||
+++
|
||||
date="2023-02-26"
|
||||
author="spanskiduh"
|
||||
title="milvus_db"
|
||||
description="click to read about milvus_db"
|
||||
+++
|
||||
# Milvus DB
|
||||
|
||||
Milvus is a powerful open-source vector database that is designed to handle large-scale machine learning and deep learning applications. Some of the best use cases for Milvus include:
|
||||
|
||||
- Image and Video Search: Milvus can store and retrieve large amounts of image and video data quickly and accurately. It can be used to power search engines for online marketplaces, social media platforms, and other applications where visual search is important.
|
||||
- Natural Language Processing: Milvus can be used to store and retrieve large amounts of text data, making it ideal for natural language processing applications. It can be used for sentiment analysis, chatbots, and other text-based applications.
|
||||
- Anomaly Detection: Milvus can be used to detect anomalies in large datasets. It can be used in fraud detection, network intrusion detection, and other applications where identifying outliers is important.
|
||||
- Recommendation Systems: Milvus can be used to power recommendation systems, providing users with personalized recommendations based on their past behavior and preferences.
|
||||
- Facial Recognition: Milvus can be used to store and match facial recognition data quickly and accurately. It can be used for security systems, access control, and other applications where facial recognition is important.
|
||||
|
||||
|
||||
### Milvus cli
|
||||
|
||||
#### Installation
|
||||
|
||||
```bash
|
||||
pip install milvus-cli
|
||||
```
|
||||
|
||||
```
|
||||
:: fedora > milvis_cli
|
||||
__ __ _ _ ____ _ ___
|
||||
| \/ (_) |_ ___ _ ___ / ___| | |_ _|
|
||||
| |\/| | | \ \ / / | | / __| | | | | | |
|
||||
| | | | | |\ V /| |_| \__ \ | |___| |___ | |
|
||||
|_| |_|_|_| \_/ \__,_|___/ \____|_____|___|
|
||||
|
||||
Milvus cli version: 0.3.2
|
||||
Pymilvus version: 2.2.1
|
||||
|
||||
Learn more: https://github.com/zilliztech/milvus_cli.
|
||||
|
||||
|
||||
milvus_cli >
|
||||
```
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="mosquitto"
|
||||
description="click to read about mosquitto"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="mount"
|
||||
description="click to read about mount"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-31"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="multiprocessing"
|
||||
description="click to read about multiprocessing"
|
||||
|
@ -535,3 +535,103 @@ and to enable the efficient exchange of data between them.
|
|||
- `MPI_Gatherv` and `MPI_Scatterv`
|
||||
- Same as Scatter and gather, but you have control over displacenents and send counts for each process
|
||||
- basically you can control how larg chunk everey process will handle
|
||||
|
||||
## CUDA C
|
||||
|
||||
Cuda program consists:
|
||||
- Code thet runs on host(CPU)
|
||||
- Kernel that runs on GPU
|
||||
- Threads are organized in block, which make up grid
|
||||
- Every kernel executes single grid
|
||||
|
||||
Code execution:
|
||||
- Copy data to GPU
|
||||
- request for computation
|
||||
- compute
|
||||
- copu data from GPU memory to main system memory
|
||||
|
||||
### Streaming multiprocessor(SM)
|
||||
|
||||
```
|
||||
| I cache |
|
||||
| MT issue |
|
||||
| C cache |
|
||||
| SP | SP |
|
||||
| SP | SP |
|
||||
| ... | ... |
|
||||
| SP | SP |
|
||||
| SFU | SFU |
|
||||
| registers |
|
||||
| Shared Memory |
|
||||
| Local Memory |
|
||||
```
|
||||
|
||||
Consists of:
|
||||
- `SP` ~ streaming processors -> 2times the clock speed (fast clock)
|
||||
- `SFU` ~ special function units
|
||||
- `Shared memory`
|
||||
- `cache`
|
||||
|
||||
Properties:
|
||||
- A block of thread is executed by single streaming multiprocessor.
|
||||
- SM can process many blocks concurrently.
|
||||
- Threads that are in the same block are easily synchronized.
|
||||
- Threads that are executed on different SM **cannot** be synchronized ((efficently)) -> hence faster computation!
|
||||
- All the threads in the same block execute the same code
|
||||
- Every SM has 8 SP, and a warp has 32 threads, so threads are executed in four steps (pipeline)
|
||||
- Each instruction in ALE/MAD unit takes about 4 ticks(fast clock), So it lines up with warp pipeline execution (each fast tick 8 threads are created and computed)
|
||||
|
||||
Function units:
|
||||
- 8 32bit FP(floating point) ALU/MAD(multiply and add)
|
||||
- 8 integer units for jump instructions
|
||||
- 2 SFUs, trigonometric functions,..
|
||||
- 1 64 bit MAD unit (allows 64 bit operations), that means that computation with 64bit values will be at least 8-12 times slower than 32bit
|
||||
|
||||
Shared memory:
|
||||
- Really fast memory, but very limited in size.
|
||||
- It is meant for communication between threads in the same SM.
|
||||
- Meant for saving some value (example counter sum for all threads)
|
||||
- All data is lost when the kernel finishes.
|
||||
- Data from and into shared memory is transfered to and from registers using `LOAD/STORE`.
|
||||
|
||||
Registers:
|
||||
- Each SM has a few registers(static), faster than shared memory
|
||||
- Then each SP has a few dynamically allocated registers
|
||||
|
||||
Local memory:
|
||||
- private for each thread
|
||||
- used when there are no registers left
|
||||
- a bit slower
|
||||
|
||||
Warp (micro architecture):
|
||||
- consists of 32 parallel threads, that execute the same code
|
||||
- each SM can execute 32 warps
|
||||
|
||||
|
||||
### Global & constant & texture memory:
|
||||
- It is slower
|
||||
- All threads can access it
|
||||
- CPU can write and read from it.
|
||||
- Memory stays there when the kernel finishes (You must clean it up after usage).
|
||||
- constant memory: small, around 64KB, used for instructions
|
||||
- texture memory: used for storing constatns and textures in graphichal applications
|
||||
|
||||
|
||||
### CUDA kernel
|
||||
|
||||
- Does not return anything
|
||||
- Accepts arguments, but pointers from device memory
|
||||
|
||||
Compiler function labels:
|
||||
- `__global__` ~ Function is ran on device, and the one calling it is the host
|
||||
- `__device__` ~ Function is ran on device, and can be called only from within device
|
||||
- `__host__` ~ Function is ran on the host ( default )
|
||||
|
||||
### Some CUDA functions
|
||||
|
||||
- `cudaMalloc()`
|
||||
- Allocate memory on the GPU
|
||||
- `cudaFree()`
|
||||
- Free memory on the GPU
|
||||
- `cudaMemcpy(p1, p2, ssize_t, cudaMemcpyDeviceToHost | cudaMemcpyHostToDevice)`
|
||||
- Copy from main memory to gpu memory and vice versa.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="named_pipes"
|
||||
description="click to read about named_pipes"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="nmap"
|
||||
description="click to read about nmap"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-25"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="os_flashing"
|
||||
description="click to read about os_flashing"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="pdf"
|
||||
description="click to read about pdf"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="permissions"
|
||||
description="click to read about permissions"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="pipewire"
|
||||
description="click to read about pipewire"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="powerusage"
|
||||
description="click to read about powerusage"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="proces_sorting_algorithms"
|
||||
description="click to read about proces_sorting_algorithms"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="proxmox"
|
||||
description="click to read about proxmox"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="pwn"
|
||||
description="click to read about pwn"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="python_specifics"
|
||||
description="click to read about python_specifics"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="qemu"
|
||||
description="click to read about qemu"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="regex"
|
||||
description="click to read about regex"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="rstudio"
|
||||
description="click to read about rstudio"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-25"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="rust"
|
||||
description="click to read about rust"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="services-and-process-management"
|
||||
description="click to read about services-and-process-management"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="squid"
|
||||
description="click to read about squid"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="symlinks"
|
||||
description="click to read about symlinks"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="system-information"
|
||||
description="click to read about system-information"
|
||||
|
|
|
@ -1,12 +1,11 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-04"
|
||||
author="spanskiduh"
|
||||
title="tmux"
|
||||
description="click to read about tmux"
|
||||
+++
|
||||
# Tmux
|
||||
|
||||
### Window operations
|
||||
- `ctrl+b c` - spawn new window
|
||||
- `ctrl+b n` - move to next window
|
||||
|
@ -60,3 +59,8 @@ tmux new-session ssh "${ssh_list[0]}" ';' \
|
|||
set-option -w synchronize-panes
|
||||
```
|
||||
[source](https://unix.stackexchange.com/a/533673)
|
||||
|
||||
|
||||
## Source updated config file?
|
||||
|
||||
`:source-file ~/.tmux.conf`
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="uart"
|
||||
description="click to read about uart"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="ufw"
|
||||
description="click to read about ufw"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="vim_tutor"
|
||||
description="click to read about vim_tutor"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="wasm"
|
||||
description="click to read about wasm"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="wl-mirror"
|
||||
description="click to read about wl-mirror"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
+++
|
||||
date="2022-12-24"
|
||||
date="2023-02-03"
|
||||
author="spanskiduh"
|
||||
title="yaml"
|
||||
description="click to read about yaml"
|
||||
|
|
|
@ -5,7 +5,7 @@ header = {
|
|||
"author": "spanskiduh",
|
||||
}
|
||||
|
||||
MD_NOTES_DIR = "../../md-notes/"
|
||||
MD_NOTES_DIR = "../../../md-notes/"
|
||||
POSTS_DIR = "../content/posts/"
|
||||
|
||||
def main():
|
||||
|
|
Loading…
Reference in New Issue