This guide will show you how to download, compile and install the nvidia-legacy-340xx-driver on Debian 12. Some people install the driver directly from sid but this will mix packages from both stable and unstable which may create issues. It's recommended to update and upgrade your system before you start.
It was reported to work with nvidia-legacy-390xx-driver just replace the appropriate package names.
Install these packages.
sudo apt install build-essential fakeroot devscripts
| ----------------------------------------------------------------------------------------------------- | |
| Read Test | |
| fio --name=randread --ioengine=libaio --iodepth=16 --rw=randread --bs=4k --direct=0 --size=512M --numjobs=4 --runtime=240 --group_reporting | |
| ----------------------------------------------------------------------------------------------------- | |
| writes a total 2GB files [4 jobs x 512 MB = 2GB] running 4 processes at a time: | |
| fio --name=randwrite --ioengine=libaio --iodepth=1 --rw=randwrite --bs=4k --direct=0 --size=512M --numjobs=4 --runtime=240 --group_reporting | |
| ----------------------------------------------------------------------------------------------------- | |
| Read Write Performance Test | |
| fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=random_read_write.fio --bs=4k --iodepth=64 --size=4G --readwrite=randrw --rwmixread=75 |
| # Wrap credentials from azure-identity to be compatible with SDK that needs msrestazure or azure.common.credentials | |
| # Need msrest >= 0.6.0 | |
| # See also https://pypi.org/project/azure-identity/ | |
| from msrest.authentication import BasicTokenAuthentication | |
| from azure.core.pipeline.policies import BearerTokenCredentialPolicy | |
| from azure.core.pipeline import PipelineRequest, PipelineContext | |
| from azure.core.pipeline.transport import HttpRequest |
| This is free and unencumbered software released into the public domain. | |
| Anyone is free to copy, modify, publish, use, compile, sell, or | |
| distribute this software, either in source code form or as a compiled | |
| binary, for any purpose, commercial or non-commercial, and by any | |
| means. | |
| In jurisdictions that recognize copyright laws, the author or authors | |
| of this software dedicate any and all copyright interest in the | |
| software to the public domain. We make this dedication for the benefit |
| WAYLAND_PROTOCOLS=/usr/share/wayland-protocols | |
| # wayland-scanner is a tool which generates C headers and rigging for Wayland | |
| # protocols, which are specified in XML. wlroots requires you to rig these up | |
| # to your build system yourself and provide them in the include path. | |
| xdg-shell-protocol.h: | |
| wayland-scanner server-header \ | |
| $(WAYLAND_PROTOCOLS)/stable/xdg-shell/xdg-shell.xml $@ | |
| xdg-shell-protocol.c: xdg-shell-protocol.h |
install packages first:
yay -S xl2tpd strongswan networkmanager-l2tpref: https://wiki.archlinux.org/index.php/Openswan_L2TP/IPsec_VPN_client_setup
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
| # -*- mode:conf-unix -*- | |
| ### hosts win10 extra | |
| ### More info: https://github.com/crazy-max/WindowsSpyBlocker | |
| 0.0.0.0 answers.microsoft.com | |
| 0.0.0.0 apps.skype.com | |
| 0.0.0.0 az361816.vo.msecnd.net | |
| 0.0.0.0 az512334.vo.msecnd.net | |
| 0.0.0.0 cdn.content.prod.cms.msn.com | |
| 0.0.0.0 choice.microsoft.com |
[ Update 2025-03-24: Commenting is disabled permanently. Previous comments are archived at web.archive.org. ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
| @echo off | |
| setlocal EnableDelayedExpansion | |
| ver | find "10." > nul | |
| if errorlevel 1 ( | |
| echo Your Windows version is not Windows 10... yet. Brace yourself, Windows 10 is coming^^! | |
| pause | |
| exit | |
| ) |
