Debian Linux Setup Guide For ThinkStation P330 Guidelines for Debian 9.5 and later Section 1 - BIOS Setup

container image, select one of the following modes: ‣ Interactive ‣ If you have Docker 19.03 or later, a typical command to launch the container is: docker run --gpus all -it --rm -v local_dir:container_dir local_dir:container_dir nvcr.io/nvidia/ pytorch:-py3 ‣ Non-interactive ‣ If you have Docker 19.03 or later, a typical command to launch the container is: docker run --gpus all -it --rm -v local_dir:container_dir release 530 or later. However, if you are running on a data center GPU (for example, T4 or any other data center GPU), you can use NVIDIA driver release 450.51 (or later R450), 470.57 (or later R470), 510

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. In many configurations with authentication, where the value using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. Other configuration changes Some other small adjustments using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch

using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch requests is now configurable. Support for Unix domain sockets to the backend (available in 2.4.7 and later). mod_proxy_balancer More runtime configuration changes for BalancerMembers via balancer-manager

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. In many configurations with authentication, where the value using either ERRORLOG or CUSTOMLOG were in- voked using /bin/sh -c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). MOD PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. In many configurations with authentication, where the value using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch

using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch requests is now configurable. Support for Unix domain sockets to the backend (available in 2.4.7 and later). mod_proxy_balancer More runtime configuration changes for BalancerMembers via balancer-manager

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. In many configurations with authentication, where the value using either ERRORLOG or CUSTOMLOG were in- voked using /bin/sh -c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). MOD PROXY The PROXYPASS directive is now most optimally configured within a LOCATION or LOCATIONMATCH

try to avoid it when upgrading: either keep old directives and then migrate to the new ones on a later stage or just migrate everything in bulk. In many configurations with authentication, where the value using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore the old behaviour, see the piped logging EC keys are now supported in addition to RSA and DSA. Support for TLS-SRP (available in 2.4.4 and later). mod_proxy The ProxyPass directive is now most optimally configured within a Location or LocationMatch