https://lwpwiki.webhosting.rug.nl/api.php?action=feedcontributions&feedformat=atom&user=Remco 2026-04-29T16:53:10Z User contributions MediaWiki 1.43.3 https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1189 2026-02-15T13:15:42Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''vlwp.rug.nl''' or by using a [https://download.nomachine.com/enterprise/?product=enterprise-client client]. <br /> In many circumstance the [https://download.nomachine.com/enterprise/?product=enterprise-client client] performs better.<br /> <br /> == Drag-n-drop files ==<br /> Both the web browser and the client support exchanging files between your own computer and the virtual LWP through drag-n-drop. Simply drag a file onto the desktop of the vLWP in your browser or client.<br /> This works both ways.<br /> <br /> == Dedicated client ==<br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> <br /> == More info ==<br /> General manuals on how to connect to a LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1188 2026-02-13T11:30:59Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''vlwp.rug.nl''' or by using a client. <br /> <br /> == Drag-n-drop files ==<br /> Both the web browser and the client support exchanging files between your own computer and the virtual LWP through drag-n-drop. Simply drag a file onto the desktop of the vLWP in your browser or client.<br /> This works both ways.<br /> <br /> == Dedicated client ==<br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> <br /> == More info ==<br /> General manuals on how to connect to a LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1187 2026-02-13T11:30:28Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''vlwp.rug.nl''' or by using a client. <br /> <br /> == Drag-n-drop files ==<br /> Both the web browser and the client support exchanging files between your own computer and the virtual LWP through drag-n-drop. Simply drag a file onto the desktop of the vlwp in your browser or client.<br /> This works both ways.<br /> <br /> == Dedicated client ==<br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> <br /> == More info ==<br /> General manuals on how to connect to a LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1186 2026-02-13T11:29:12Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''vlwp.rug.nl''' or by using a client. <br /> <br /> == Drag-n-drop files ==<br /> Both the web browser and the client support exchanging files between your own computer and the vlwp through drag-n-drop. Simply drag a file onto the desktop of the vlwp in your browser or client.<br /> This works both ways.<br /> <br /> == Dedicated client ==<br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> <br /> == More info ==<br /> General manuals on how to connect to a LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1185 2026-02-06T11:53:13Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''vlwp.rug.nl''' or by using a client. <br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> &lt;br&gt;<br /> General manuals on how to connect to a LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Virtual_LWP&diff=1184 2026-02-06T11:42:37Z

<p>Remco: </p> <hr /> <div>===Virtual LWP===<br /> Don't have your own PC? We now offer the virtual LWP ([https://vlwp.rug.nl/nxwebplayer vLWP]).&lt;/br&gt;<br /> <br /> It's accessible from your web browser at '''https://vlwp.rug.nl''' or by using a client. <br /> <br /> The client software makes it easy to share the clipboard and files and may have lower latency.<br /> But sharing the clipboard using the webplayer in the browser also works.<br /> # Enable clipboard sharing with ctrl-alt-0 (or by moving the mouse to the top right corner of the webplayer).<br /> # When the clipboard is enabled you will see a grey clipboard sharing area at the bottom of the webplayer<br /> &lt;br&gt;<br /> Manuals on how to connect to the LWP can be found below, just replace any hostname/ip-address with '''vlwp.rug.nl''':<br /> * [[SSH HowTo| SSH directly to the LWP]]<br /> * [[Remote desktop access with NoMachine]] (contains link to download client software)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Remote_desktop_access_with_NoMachine&diff=1183 2026-02-06T11:23:58Z

<p>Remco: </p> <hr /> <div>[[Category:remotexs-faq]]<br /> <br /> ===== On your RUG LWP desktop computer =====<br /> NoMachine works via SSH. '''This means you need to make sure your account name (P-nummer) is listed in the file /etc/users_allowed_ssh'''. You can edit this file only when logged in using the physical keyboard of the computer. After at most 15 minutes access is enabled.<br /> <br /> ==== On your own computer or laptop computer ====<br /> <br /> Download and install the NoMachine Enterprise Client for Windows, Linux or MacOS:&lt;br&gt;<br /> https://download.nomachine.com/enterprise/?product=enterprise-client&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: The normal client will also install a NX server on your machine, so unless you want remote desktop access to your own PC as well, use the enterprise client.''&lt;br&gt;<br /> <br /> [https://www.nomachine.com/support/documents/getting-started-with-nomachine Getting started with the NoMachine client]<br /> <br /> After you've installed the NoMachine client, open it and add a new connection.&lt;br&gt;<br /> [[File:NX first screen.png|thumb|none|Initial screen.]]<br /> Enter a '''Name''' for the connection and add the '''hostname or IP number''' for the '''Host''' you are trying to connect to.&lt;br&gt;<br /> [[File:NX add connection.png|thumb|none|Add connection.]]<br /> * Port = 4000<br /> * Protocol = NX<br /> [[File:NX configuration.png|thumb|none|Configuration.]]<br /> Next select '''Configuration'''. Make sure '''Use password authentication''' is selected and '''Use UDP communication for multimedia data''' is checked.&lt;br&gt;<br /> Click '''Connect'''.<br /> [[File:Nx verify host authenticity.png|thumb|none|Verify your hosts identity.]]<br /> The '''Verify host authenticity''' will only appear the first time you connect to your host or if you reinstall the host. If it does appear a second time on the same host, do not continue, this might indicate malicious activity on the host system and you should call support.&lt;br&gt;<br /> Click '''Yes''' to verify your hosts identity.<br /> [[File:Nx login.png|thumb|none|The login screen.]]<br /> Enter your '''Username''' and '''Password''' and click '''Login'''. Don't save your password if you're on a shared PC.<br /> [[File:NX connection setup audio.png|thumb|none|Audio on remote host.]]<br /> Hit the checkbox to mute audio on the remote host.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup display.png|thumb|none|Scale remote desktop to fit window.]]<br /> Select '''Scale the remote desktop to fit into the window'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup remote display.png|thumb|none|Don't resize remote display.]]<br /> Select '''Don't resize the remote display'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again.&lt;br&gt;<br /> Hit '''OK''' a last time to connect to the desktop of your remote host.<br /> [[File:NX connection settings.png|thumb|none|Change connection setting from top right corner.]]<br /> Now you can login as you would normally login on your LWP.&lt;br&gt;<br /> If you want to change any of the connection settings, hover over the top right corner of the window until it folds down and then click it.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:NX_add_connection.png&diff=1177 2025-11-17T09:46:16Z

<p>Remco: Remco uploaded a new version of File:NX add connection.png</p> <hr /> <div>Give a name and save the settings for your connection.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:NX_add_connection.png&diff=1176 2025-11-17T09:44:09Z

<p>Remco: Remco uploaded a new version of File:NX add connection.png</p> <hr /> <div>Give a name and save the settings for your connection.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Installing_the_LWP&diff=1154 2025-10-17T11:38:04Z

<p>Remco: </p> <hr /> <div>[[Category:install-faq]]<br /> == Before you begin ==<br /> Make a '''backup''' of your data stored on the disk of your PC, if any. You can use a usb device or your home directory. Your home directory is network storage and does not get touched during the installation.&lt;br&gt;<br /> If you have sudo rights, you should know where you’ve put your files. If you don’t have sudo rights, you can only place files in '''/var/tmp''' or maybe in '''/tmp''' if you never restart your PC.&lt;br&gt;<br /> Any extra disks in your PC will not be touched during the installation. Ask [mailto:lwp@rug.nl us] to make them available after the installation.&lt;br&gt;<br /> <br /> To use LWP we require the following partitions:&lt;br&gt;<br /> - EFI/esp type partition, can be between 100-500Mb (does not need to be formatted)&lt;br&gt;<br /> - linux boot: 1-2Gb, leave unformatted&lt;br&gt;<br /> - linux root: more then 80Gb, leave unformatted&lt;br&gt;<br /> - linux swap: optional but recommended for desktop systems to be equal to the amount of available RAM&lt;br&gt;<br /> <br /> If your disk already contains an EFI type partition, it is safe to remove all linux type partions. If the remaining free space is large enough all needed partitons will be created automatically.<br /> If there is no EFI partition and you want to be able to dualboot Windows/Linux you will have to start by re-installing Windows. THIS WILL WIPE THE DISK!<br /> <br /> Existing Windows partitions are left untouched. You can use the cfdisk command from the menu to delete and create partitions. Beware that resizing existing partitions will not change the underlying filesystem. &lt;br&gt;<br /> <br /> After you've made your backups, restart your PC.&lt;br&gt;<br /> <br /> == Make the BIOS UEFI ready ==<br /> <br /> It is probably best to ask for help with this, but you can do this yourself:<br /> - press ESC while the computer powers on<br /> - select BIOS menu<br /> - select Advanced<br /> - select Boot Options<br /> - enable UEFI boot <br /> - select Secure Boot Configuration<br /> - Legacy Support Disabled and Secure Boot disabled<br /> - save and reboot<br /> - press ESC while the computer powers on<br /> - select BIOS menu<br /> - select Advanced<br /> - select Boot Options<br /> - under UEFI boot order move network IPV4 to the top<br /> - save and reboot <br /> <br /> If you want to be able to use Windows (UWP/UFC) as well as Linux (LWP), install Windows first and leave about 100Gb free space for Linux.<br /> Installing Windows takes about 50 min. Installing LWP also takes about 50 min.<br /> <br /> == (re)Install the LWP ==<br /> On most systems, booting from the network is configured as default. If that is not the case on your system, you can press '''F12''' directly after you turn on your PC to boot from the network.&lt;br&gt;<br /> [[File:Ipxe-lwp.jpg|thumb|none|The ipxe menu for LWP only.]]<br /> * From the menu, choose '''Install LWP'''.&lt;br&gt;<br /> * That's it. The rest happens automatically.&lt;br&gt;<br /> When it’s done the login screen will appear and you can login.&lt;br&gt;<br /> [[File:Login-screen.png|thumb|none|The LWP login screen.]]<br /> <br /> == (re)Install dual-boot UWP/LWP ==<br /> If only the LWP has to be (re)installed follow the procedure for [[#(re)Install the LWP| '''(re)Install the LWP''']], but the '''Install LWP''' menu-item is in the '''Maintenance''' sub-menu.&lt;br&gt;<br /> [[File:Ipxe-dual-maintenance-select-install-lwp.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> The servicedesk can help you (re)install the UWP on your machine.&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: Reinstalling the UWP will also require reinstalling the LWP. Reinstalling the LWP does not require reinstalling the UWP, as long as there is enough disk space for the LWP to fit.''&lt;br&gt;<br /> <br /> == Not enough space ==<br /> === LWP only ===<br /> ==== Wipe the system disk ====<br /> First make sure you have not forgotten to backup any data on the disk.<br /> In the network boot menu (press '''F12''' directly after turning on your PC) from the '''Maintenance''' sub-menu, select '''Parted Magic''' to start it.&lt;br&gt; <br /> [[File:Ipxe-dual-maintenance-select-parted-magic.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> We are going to create a new and empty partition table for the disk. If it didn't start automatically (it should) start '''GParted''' by opening the '''Partition editor''' program from the desktop.<br /> [[File:Gparted-lwponly.png|thumb|none|Example partitions LWP only PC.]]<br /> Make sure you have your system disk selected in the top right corner; It should be selected by default.<br /> Go to '''Device''' and select '''Create Partition Table'''.<br /> [[File:Gparted-device-createptable.png|thumb|none|Create partition table.]]<br /> Select '''gpt''' as the new partition table type, click '''Apply''' and you're done. The disk is now completely empty and ready for a fresh installation.<br /> <br /> === Dual-boot ===<br /> ==== Resize the UWP partition ====<br /> If you’re familiar with resizing partitions and/or not afraid of losing anything because you make backups like you're supposed to, consider resizing the UWP NTFS partition if you have enough free space there. You can use '''Parted Magic''' for this.&lt;br&gt;<br /> In the network boot menu (press '''F12''' directly after turning on your PC) from the '''Maintenance''' sub-menu, select '''Parted Magic''' to start it.&lt;br&gt;<br /> [[File:Ipxe-dual-maintenance-select-parted-magic.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> Resize the NTFS partition using '''GParted''' (should start automatically, else open the &quot;Partition editor&quot; program from the desktop) so you have at least 80GB of free space to install the LWP in.&lt;br&gt;<br /> [[File:Gparted-dual.png|thumb|none|Example partitions dual-boot PC.]]<br /> A more detailed explanation on Parted Magic can be found [[Parted_Magic| here]].&lt;br&gt;<br /> After resizing is done, restart your system and [[#(re)Install the LWP| start the LWP installer]], the installation should now continue without any problems.&lt;br&gt;</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Installing_the_LWP&diff=1153 2025-10-17T10:29:11Z

<p>Remco: </p> <hr /> <div>[[Category:install-faq]]<br /> == Before you begin ==<br /> Make a '''backup''' of your data stored on the disk of your PC, if any. You can use a usb device or your home directory. Your home directory is network storage and does not get touched during the installation.&lt;br&gt;<br /> If you have sudo rights, you should know where you’ve put your files. If you don’t have sudo rights, you can only place files in '''/var/tmp''' or maybe in '''/tmp''' if you never restart your PC.&lt;br&gt;<br /> Any extra disks in your PC will not be touched during the installation. Ask [mailto:lwp@rug.nl us] to make them available after the installation.&lt;br&gt;<br /> <br /> To use LWP we require the following partitions:&lt;br&gt;<br /> - EFI/esp type partition, can be between 100-500Mb (does not need to be formatted)&lt;br&gt;<br /> - linux boot: 1-2Gb, leave unformatted&lt;br&gt;<br /> - linux root: more then 80Gb, leave unformatted&lt;br&gt;<br /> - linux swap: optional but recommended for desktop systems to be equal to the amount of available RAM&lt;br&gt;<br /> <br /> If your disk already contains an EFI type partition, it is safe to remove all linux type partions. If the remaining free space is large enough all needed partitons will be created automatically.<br /> If there is no EFI partition you will have to start by re-installing Windows. THIS WILL WIPE THE DISK!<br /> <br /> Existing Windows partitions are left untouched. You can use the cfdisk command from the menu to delete and create partitions. Beware that resizing existing partitions will not change the underlying filesystem. &lt;br&gt;<br /> <br /> After you've made your backups, restart your PC.&lt;br&gt;<br /> <br /> == Make the BIOS UEFI ready ==<br /> <br /> It is probably best to ask for help with this, but you can do this yourself:<br /> - press ESC while the computer powers on<br /> - select BIOS menu<br /> - select Advanced<br /> - select Boot Options<br /> - enable UEFI boot <br /> - select Secure Boot Configuration<br /> - Legacy Support Disabled and Secure Boot disabled<br /> - save and reboot<br /> - press ESC while the computer powers on<br /> - select BIOS menu<br /> - select Advanced<br /> - select Boot Options<br /> - under UEFI boot order move network IPV4 to the top<br /> - save and reboot <br /> <br /> If you want to be able to use Windows (UWP/UFC) as well as Linux (LWP), install Windows first and leave about 100Gb free space for Linux.<br /> Installing Windows takes about 50 min. Installing LWP also takes about 50 min.<br /> <br /> == (re)Install the LWP ==<br /> On most systems, booting from the network is configured as default. If that is not the case on your system, you can press '''F12''' directly after you turn on your PC to boot from the network.&lt;br&gt;<br /> [[File:Ipxe-lwp.jpg|thumb|none|The ipxe menu for LWP only.]]<br /> * From the menu, choose '''Install LWP'''.&lt;br&gt;<br /> * That's it. The rest happens automatically.&lt;br&gt;<br /> When it’s done the login screen will appear and you can login.&lt;br&gt;<br /> [[File:Login-screen.png|thumb|none|The LWP login screen.]]<br /> <br /> == (re)Install dual-boot UWP/LWP ==<br /> If only the LWP has to be (re)installed follow the procedure for [[#(re)Install the LWP| '''(re)Install the LWP''']], but the '''Install LWP''' menu-item is in the '''Maintenance''' sub-menu.&lt;br&gt;<br /> [[File:Ipxe-dual-maintenance-select-install-lwp.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> The servicedesk can help you (re)install the UWP on your machine.&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: Reinstalling the UWP will also require reinstalling the LWP. Reinstalling the LWP does not require reinstalling the UWP, as long as there is enough disk space for the LWP to fit.''&lt;br&gt;<br /> <br /> == Not enough space ==<br /> === LWP only ===<br /> ==== Wipe the system disk ====<br /> First make sure you have not forgotten to backup any data on the disk.<br /> In the network boot menu (press '''F12''' directly after turning on your PC) from the '''Maintenance''' sub-menu, select '''Parted Magic''' to start it.&lt;br&gt; <br /> [[File:Ipxe-dual-maintenance-select-parted-magic.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> We are going to create a new and empty partition table for the disk. If it didn't start automatically (it should) start '''GParted''' by opening the '''Partition editor''' program from the desktop.<br /> [[File:Gparted-lwponly.png|thumb|none|Example partitions LWP only PC.]]<br /> Make sure you have your system disk selected in the top right corner; It should be selected by default.<br /> Go to '''Device''' and select '''Create Partition Table'''.<br /> [[File:Gparted-device-createptable.png|thumb|none|Create partition table.]]<br /> Select '''gpt''' as the new partition table type, click '''Apply''' and you're done. The disk is now completely empty and ready for a fresh installation.<br /> <br /> === Dual-boot ===<br /> ==== Resize the UWP partition ====<br /> If you’re familiar with resizing partitions and/or not afraid of losing anything because you make backups like you're supposed to, consider resizing the UWP NTFS partition if you have enough free space there. You can use '''Parted Magic''' for this.&lt;br&gt;<br /> In the network boot menu (press '''F12''' directly after turning on your PC) from the '''Maintenance''' sub-menu, select '''Parted Magic''' to start it.&lt;br&gt;<br /> [[File:Ipxe-dual-maintenance-select-parted-magic.jpg|thumb|none|The ipxe maintenance sub menu for dual-boot.]]<br /> Resize the NTFS partition using '''GParted''' (should start automatically, else open the &quot;Partition editor&quot; program from the desktop) so you have at least 80GB of free space to install the LWP in.&lt;br&gt;<br /> [[File:Gparted-dual.png|thumb|none|Example partitions dual-boot PC.]]<br /> A more detailed explanation on Parted Magic can be found [[Parted_Magic| here]].&lt;br&gt;<br /> After resizing is done, restart your system and [[#(re)Install the LWP| start the LWP installer]], the installation should now continue without any problems.&lt;br&gt;</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Remote_desktop_access_with_NoMachine&diff=1135 2024-09-27T07:01:08Z

<p>Remco: /* On your home computer or laptop computer */</p> <hr /> <div>[[Category:remotexs-faq]]<br /> <br /> ===== On your RUG LWP desktop computer =====<br /> NoMachine works via SSH. '''This means you need to make sure your account name (P-nummer) is listed in the file /etc/users_allowed_ssh'''. You can edit this file only when logged in using the physical keyboard of the computer. After at most 15 minutes access is enabled.<br /> <br /> ==== On your own computer or laptop computer ====<br /> <br /> Download and install the NoMachine Enterprise Client for Windows, Linux or MacOS:&lt;br&gt;<br /> https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Client&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: The normal client will also install a NX server on your machine, so unless you want remote desktop access to your own PC as well, use the enterprise client.''&lt;br&gt;<br /> <br /> <br /> After you've installed the NoMachine client, open it and add a new connection.&lt;br&gt;<br /> [[File:NX first screen.png|thumb|none|Initial screen.]]<br /> Enter a '''Name''' for the connection and add the '''hostname or IP number''' for the '''Host''' you are trying to connect to.&lt;br&gt;<br /> [[File:NX add connection.png|thumb|none|Add connection.]]<br /> * Port = 4000<br /> * Protocol = NX<br /> [[File:NX configuration.png|thumb|none|Configuration.]]<br /> Next select '''Configuration'''. Make sure '''Use password authentication''' is selected and '''Use UDP communication for multimedia data''' is checked.&lt;br&gt;<br /> Click '''Connect'''.<br /> [[File:Nx verify host authenticity.png|thumb|none|Verify your hosts identity.]]<br /> The '''Verify host authenticity''' will only appear the first time you connect to your host or if you reinstall the host. If it does appear a second time on the same host, do not continue, this might indicate malicious activity on the host system and you should call support.&lt;br&gt;<br /> Click '''Yes''' to verify your hosts identity.<br /> [[File:Nx login.png|thumb|none|The login screen.]]<br /> Enter your '''Username''' and '''Password''' and click '''Login'''. Don't save your password if you're on a shared PC.<br /> [[File:NX connection setup audio.png|thumb|none|Audio on remote host.]]<br /> Hit the checkbox to mute audio on the remote host.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup display.png|thumb|none|Scale remote desktop to fit window.]]<br /> Select '''Scale the remote desktop to fit into the window'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup remote display.png|thumb|none|Don't resize remote display.]]<br /> Select '''Don't resize the remote display'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again.&lt;br&gt;<br /> Hit '''OK''' a last time to connect to the desktop of your remote host.<br /> [[File:NX connection settings.png|thumb|none|Change connection setting from top right corner.]]<br /> Now you can login as you would normally login on your LWP.&lt;br&gt;<br /> If you want to change any of the connection settings, hover over the top right corner of the window until it folds down and then click it.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Remote_desktop_access_with_NoMachine&diff=1134 2024-09-27T07:00:47Z

<p>Remco: </p> <hr /> <div>[[Category:remotexs-faq]]<br /> <br /> ===== On your RUG LWP desktop computer =====<br /> NoMachine works via SSH. '''This means you need to make sure your account name (P-nummer) is listed in the file /etc/users_allowed_ssh'''. You can edit this file only when logged in using the physical keyboard of the computer. After at most 15 minutes access is enabled.<br /> <br /> ==== On your home computer or laptop computer ====<br /> <br /> Download and install the NoMachine Enterprise Client for Windows, Linux or MacOS:&lt;br&gt;<br /> https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Client&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: The normal client will also install a NX server on your machine, so unless you want remote desktop access to your own PC as well, use the enterprise client.''&lt;br&gt;<br /> <br /> <br /> After you've installed the NoMachine client, open it and add a new connection.&lt;br&gt;<br /> [[File:NX first screen.png|thumb|none|Initial screen.]]<br /> Enter a '''Name''' for the connection and add the '''hostname or IP number''' for the '''Host''' you are trying to connect to.&lt;br&gt;<br /> [[File:NX add connection.png|thumb|none|Add connection.]]<br /> * Port = 4000<br /> * Protocol = NX<br /> [[File:NX configuration.png|thumb|none|Configuration.]]<br /> Next select '''Configuration'''. Make sure '''Use password authentication''' is selected and '''Use UDP communication for multimedia data''' is checked.&lt;br&gt;<br /> Click '''Connect'''.<br /> [[File:Nx verify host authenticity.png|thumb|none|Verify your hosts identity.]]<br /> The '''Verify host authenticity''' will only appear the first time you connect to your host or if you reinstall the host. If it does appear a second time on the same host, do not continue, this might indicate malicious activity on the host system and you should call support.&lt;br&gt;<br /> Click '''Yes''' to verify your hosts identity.<br /> [[File:Nx login.png|thumb|none|The login screen.]]<br /> Enter your '''Username''' and '''Password''' and click '''Login'''. Don't save your password if you're on a shared PC.<br /> [[File:NX connection setup audio.png|thumb|none|Audio on remote host.]]<br /> Hit the checkbox to mute audio on the remote host.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup display.png|thumb|none|Scale remote desktop to fit window.]]<br /> Select '''Scale the remote desktop to fit into the window'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup remote display.png|thumb|none|Don't resize remote display.]]<br /> Select '''Don't resize the remote display'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again.&lt;br&gt;<br /> Hit '''OK''' a last time to connect to the desktop of your remote host.<br /> [[File:NX connection settings.png|thumb|none|Change connection setting from top right corner.]]<br /> Now you can login as you would normally login on your LWP.&lt;br&gt;<br /> If you want to change any of the connection settings, hover over the top right corner of the window until it folds down and then click it.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Remote_desktop_access_with_NoMachine&diff=1133 2024-09-27T06:59:48Z

<p>Remco: </p> <hr /> <div>[[Category:remotexs-faq]]<br /> <br /> ===== On your RUG desktop computer =====<br /> NoMachine works via SSH. '''This means you need to make sure your account name (P-nummer) is listed in the file /etc/users_allowed_ssh'''. You can edit this file only when logged in using the physical keyboard of the computer. After at most 15 minutes access is enabled.<br /> <br /> ==== On the client (ie. your home computer or laptop) computer ====<br /> <br /> Download and install the NoMachine Enterprise Client for Windows, Linux or MacOS:&lt;br&gt;<br /> https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Client&lt;br&gt;<br /> &lt;br&gt;<br /> ''Note: The normal client will also install a NX server on your machine, so unless you want remote desktop access to your own PC as well, use the enterprise client.''&lt;br&gt;<br /> <br /> <br /> After you've installed the NoMachine client, open it and add a new connection.&lt;br&gt;<br /> [[File:NX first screen.png|thumb|none|Initial screen.]]<br /> Enter a '''Name''' for the connection and add the '''hostname or IP number''' for the '''Host''' you are trying to connect to.&lt;br&gt;<br /> [[File:NX add connection.png|thumb|none|Add connection.]]<br /> * Port = 4000<br /> * Protocol = NX<br /> [[File:NX configuration.png|thumb|none|Configuration.]]<br /> Next select '''Configuration'''. Make sure '''Use password authentication''' is selected and '''Use UDP communication for multimedia data''' is checked.&lt;br&gt;<br /> Click '''Connect'''.<br /> [[File:Nx verify host authenticity.png|thumb|none|Verify your hosts identity.]]<br /> The '''Verify host authenticity''' will only appear the first time you connect to your host or if you reinstall the host. If it does appear a second time on the same host, do not continue, this might indicate malicious activity on the host system and you should call support.&lt;br&gt;<br /> Click '''Yes''' to verify your hosts identity.<br /> [[File:Nx login.png|thumb|none|The login screen.]]<br /> Enter your '''Username''' and '''Password''' and click '''Login'''. Don't save your password if you're on a shared PC.<br /> [[File:NX connection setup audio.png|thumb|none|Audio on remote host.]]<br /> Hit the checkbox to mute audio on the remote host.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup display.png|thumb|none|Scale remote desktop to fit window.]]<br /> Select '''Scale the remote desktop to fit into the window'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.<br /> [[File:NX connection setup remote display.png|thumb|none|Don't resize remote display.]]<br /> Select '''Don't resize the remote display'''.&lt;br&gt;<br /> Hit the checkbox at the bottom left so this message does not appear again.&lt;br&gt;<br /> Hit '''OK''' a last time to connect to the desktop of your remote host.<br /> [[File:NX connection settings.png|thumb|none|Change connection setting from top right corner.]]<br /> Now you can login as you would normally login on your LWP.&lt;br&gt;<br /> If you want to change any of the connection settings, hover over the top right corner of the window until it folds down and then click it.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Getting_to_your_Windows_Y:-drive&diff=1120 2024-05-13T13:13:45Z

<p>Remco: update</p> <hr /> <div>[[Category:misc-faq]]<br /> === Generic instructions ===<br /> <br /> When you use the LWP then your UWP Y: drive is available at '''/media/ydrive'''.<br /> <br /> Otherwise from with the university network you can use the smb protocol to access the Y:-drive.<br /> <br /> $ sudo mkdir -p /mnt/ydrive/<br /> $ sudo mount -t smb3 //workspace.rug.nl/ydrive /mnt/ydrive/ -o user=&lt;p-number&gt;<br /> <br /> ==== From outside the university network ====<br /> <br /> From outside the university network you can use https://vlwp.rug.nl or https://uwp.rug.nl<br /> <br /> === From inside the university network using your own OS ===<br /> <br /> ==== MacOS ====<br /> <br /> First edit (as root) `/etc/nsmb.conf` to contain:<br /> <br /> [default]<br /> protocol_vers_map=4<br /> <br /> Then in `Finder` choose `Go -&gt; Connect to Server` and fill in:<br /> * `smb://&lt;p-number&gt;@workspace.rug.nl/ydrive`<br /> <br /> ==== Linux ====<br /> First edit `/etc/samba/smb.conf` to contain:<br /> <br /> [global]<br /> min protocol = SMB2<br /> client min protocol = SMB2<br /> workgroup=WORKPLACE<br /> <br /> Then use your file manager to connect to a network share:<br /> * `smb://&lt;p-number&gt;@workspace.rug.nl/ydrive`<br /> <br /> <br /> <br /> ===== Linux =====</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Google_Drive&diff=1106 2024-02-05T12:33:04Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> Google Drive has no desktop client for linux. There is however a tool which let's you mount your Google Drive. Here's how to use it.<br /> <br /> ----<br /> <br /> Install the tool:<br /> sudo apt-get install google-drive-ocamlfuse<br /> Create the folder you want to use for Google Drive:<br /> mkdir &quot;${gdrive:=~/gdrive}&quot; # replace ~/gdrive for &lt;the folder you want to use for google drive&gt;<br /> Run the following command to open a browser, directing you to a page that will ask you to allow access to your Google<br /> account (this might take a minute):<br /> google-drive-ocamlfuse<br /> The next command will actually mount your Google Drive on your folder:<br /> google-drive-ocamlfuse &quot;${gdrive:=~/gdrive}&quot; # replace ~/gdrive for &lt;the folder you want to use for google drive&gt;<br /> Because you don't want to do that every time you login, add the following to your ~/.bashrc file:<br /> [ -d &quot;${gdrive:=~/gdrive}&quot; ] || mkdir -p &quot;${gdrive}&quot; # or any other path<br /> if mount -v | grep -q &quot;fuse.google-drive-ocamlfuse&quot; ; then<br /> google-drive-ocamlfuse &quot;${gdrive}&quot;<br /> fi</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Google_Drive&diff=1105 2024-02-05T12:30:12Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> Google Drive has no desktop client for linux. There is however a tool which let's you mount your Google Drive. Here's how to use it.<br /> <br /> ----<br /> <br /> Install the tool:<br /> sudo apt-get install google-drive-ocamlfuse<br /> Create the folder you want to use for Google Drive:<br /> mkdir &lt;the folder you want to use for google drive&gt;<br /> Run the following command to open a browser, directing you to a page that will ask you to allow access to your Google<br /> account (this might take a minute):<br /> google-drive-ocamlfuse<br /> The next command will actually mount your Google Drive on your folder:<br /> google-drive-ocamlfuse &lt;the folder you want to use for google drive&gt;<br /> Because you don't want to do that every time you login, add the following to your ~/.bashrc file:<br /> [ -d &quot;${gdrive:=~/gdrive}&quot; ] || mkdir -p &quot;${gdrive}&quot; # or any other path<br /> if mount -v | grep -q &quot;fuse.google-drive-ocamlfuse&quot; ; then<br /> google-drive-ocamlfuse &quot;${gdrive}&quot;<br /> fi</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1065 2023-03-01T15:18:45Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system. Follow the instructions given by:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, use only one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D/&lt;subdir&gt;&lt;/kbd&gt; or &lt;kbd&gt;/var/tmp/&lt;subdir&gt;&lt;/kbd&gt; are good choices.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. That file and directory may not (yet) exist. Example:<br /> $ [ -d ~/.config/docker ] || mkdir -p ~/.config/docker<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D/&lt;subdir&gt;&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~/.local ~/local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit &lt;kbd&gt;~/.pam_mount.conf.xml&lt;/kbd&gt; to contain:<br /> <br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1064 2023-03-01T09:28:11Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D/&lt;subdir&gt;&lt;/kbd&gt; or &lt;kbd&gt;/var/tmp/&lt;subdir&gt;&lt;/kbd&gt; are good choices.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D/&lt;subdir&gt;&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~/.local ~/local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit &lt;kbd&gt;~/.pam_mount.conf.xml&lt;/kbd&gt; to contain:<br /> <br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1039 2023-01-11T13:15:38Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D/&lt;subdir&gt;&lt;/kbd&gt; or &lt;kbd&gt;/var/tmp/&lt;subdir&gt;&lt;/kbd&gt; are goot choices.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D/&lt;subdir&gt;&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~/.local ~/local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit &lt;kbd&gt;~/.pam_mount.conf.xml&lt;/kbd&gt; to contain:<br /> <br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1014 2022-09-30T09:25:55Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D/&lt;subdir&gt;&lt;/kbd&gt; or &lt;kbd&gt;/var/tmp/&lt;subdir&gt;&lt;/kbd&gt; are goot choices.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D/&lt;subdir&gt;&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit &lt;kbd&gt;~/.pam_mount.conf.xml&lt;/kbd&gt; to contain:<br /> <br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1013 2022-09-30T09:23:47Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D/&lt;subdir&gt;&lt;/kbd&gt; or &lt;kbd&gt;/var/tmp/&lt;subdir&gt;&lt;/kbd&gt; are goot choices.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D/&lt;subdir&gt;&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit <br /> $ edit ~/.pam_mount.conf.xml to contain:<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1012 2022-09-16T14:05:58Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach (make sure to remove &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt; when you do this!) is to store a small ext4 formatted diskimage in your homedir and make it mountable:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login. For that you need to edit <br /> $ edit ~/.pam_mount.conf.xml to contain:<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> <br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=1011 2022-09-16T14:03:40Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> <br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. There are 2 ways of resolving this, but only use one of them, because they conflict with each other.&lt;br&gt;<br /> <br /> '''Solution 1'''&lt;br&gt;<br /> <br /> To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ edit ~/.config/docker/daemon.json to contain:<br /> {<br /> &quot;data-root&quot;: &quot;/mnt/D&quot;<br /> }<br /> $ systemctl --user restart docker<br /> <br /> <br /> <br /> '''Solution 2'''&lt;br&gt;<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf.xml &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=987 2022-04-20T12:36:29Z

<p>Remco: Clarify when you can use the standard docker</p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ d=/mnt/D/docker; f=~/.config/docker/daemon.json<br /> $ mkdir -p $d<br /> $ echo &quot;$((cat $f || echo {}) | jq '.&quot;data-root&quot; = &quot;'$d'&quot;')&quot; &gt; $f<br /> $ systemctl --user restart docker<br /> <br /> You can also edit this file with a text editor.<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf.xml &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root) for your personal LWP (ie. not for any shared system such as systems in the computer labs or https://vlwp.rug.nl).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=986 2022-04-20T12:34:19Z

<p>Remco: Fixed a small error in the description</p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ d=/mnt/D/docker; f=~/.config/docker/daemon.json<br /> $ mkdir -p $d<br /> $ echo &quot;$((cat $f || echo {}) | jq '.&quot;data-root&quot; = &quot;'$d'&quot;')&quot; &gt; $f<br /> $ systemctl --user restart docker<br /> <br /> You can also edit this file with a text editor.<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> $ chmod 755 ~/.local/share<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf.xml &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Anaconda&diff=948 2021-08-02T11:23:00Z

<p>Remco: </p> <hr /> <div>[[Category:anaconda-faq]]<br /> The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.<br /> <br /> To make Anaconda available in just your current ''bash'' session:<br /> <br /> '''bash$''' source /opt/netapps/anaconda3/etc/profile.d/conda.sh # older lwp3 (Ubuntu 16.04)<br /> '''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh # current lwp4 (Ubuntu 20.04)<br /> '''bash$''' conda activate<br /> <br /> To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:<br /> <br /> '''bash$''' conda init<br /> <br /> And after this, close and re-open your shell. Note that this last command also works with a select few other shells.<br /> <br /> For more information see:<br /> <br /> * https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)<br /> * https://docs.anaconda.com/anaconda/user-guide/</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Anaconda&diff=947 2021-08-02T11:22:07Z

<p>Remco: </p> <hr /> <div>[[Category:anaconda-faq]]<br /> The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.<br /> <br /> To make Anaconda available in just your current ''bash'' session:<br /> <br /> '''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh # old lwp3 (Ubuntu 16.04)<br /> '''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh # current lwp4 (Ubuntu 20.04)<br /> '''bash$''' conda activate<br /> <br /> To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:<br /> <br /> '''bash$''' conda init<br /> <br /> And after this, close and re-open your shell. Note that this last command also works with a select few other shells.<br /> <br /> For more information see:<br /> <br /> * https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)<br /> * https://docs.anaconda.com/anaconda/user-guide/</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=It_is_possible_to_run_docker_containers_on_your_computer_or_use_them_for_teaching.&diff=893 2021-06-25T10:51:28Z

<p>Remco: Remco moved page It is possible to run docker containers on your computer or use them for teaching. to It is possible to run docker containers on your computer or use them for teaching: Die punt is onhandig</p> <hr /> <div>#REDIRECT [[It is possible to run docker containers on your computer or use them for teaching]]</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=892 2021-06-25T10:51:28Z

<p>Remco: Remco moved page It is possible to run docker containers on your computer or use them for teaching. to It is possible to run docker containers on your computer or use them for teaching: Die punt is onhandig</p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ d=/mnt/D/docker; f=~/.config/docker/daemon.json<br /> $ mkdir -p $d<br /> $ echo &quot;$((cat $f || echo {}) | jq '.&quot;data-root&quot; = &quot;'$d'&quot;')&quot; &gt; $f<br /> $ systemctl --user restart docker<br /> <br /> You can also edit this file with a text editor.<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Getting_to_your_Windows_Y:-drive&diff=891 2021-06-23T08:43:03Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> When you use the LWP then your UWP Y: drive is available at '''/media/ydrive'''.<br /> <br /> Otherwise from with the university network you can use the smb protocol to access the Y:-drive.<br /> <br /> - edit /etc/samba/smb.conf to contain:<br /> [global]<br /> client min protocol = SMB2_10<br /> client max protocol = SMB3_11<br /> workgroup = WORKSPACE<br /> <br /> Now you can use your GUI file manager to connect to smb://&lt;your account&gt;@workspace.rug.nl/ydrive<br /> If you want todo this from the command line eg. after login through ssh then:<br /> $ dbus-launch /bin/bash<br /> $ gvfs-mount smb://&lt;your account&gt;@workspace.rug.nl/ydrive<br /> $ ls -al /run/user/$(id -u)/gvfs<br /> <br /> From outside the university you can use https://vlwp.rug.nl or https://uwp.rug.nl</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=889 2021-06-10T12:33:42Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have made it possible to run docker containers rootless now. Ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. To solve this you need to find a suitable location on your local disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ d=/mnt/D/docker; f=~/.config/docker/daemon.json<br /> $ mkdir -p $d<br /> $ echo &quot;$((cat $f || echo {}) | jq '.&quot;data-root&quot; = &quot;'$d'&quot;')&quot; &gt; $f<br /> $ systemctl --user restart docker<br /> <br /> You can also edit this file with a text editor.<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> Then logout and login again (or do &lt;kbd&gt;ssh 127.0.0.1 exit&lt;/kbd&gt;)<br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker_rootless&diff=888 2021-06-10T12:28:03Z

<p>Remco: </p> <hr /> <div>[[Category:Docker-faq]]<br /> <br /> We have now made it possible to run docker containers rootless ie. as a normal user, without root access (for in depth info see: https://docs.docker.com/engine/security/rootless).<br /> <br /> You need to prepare your system:<br /> $ dockerd-rootless-setuptool.sh<br /> By default this will store docker images in &lt;kbd&gt;~/.local/share/docker&lt;/kbd&gt;. Unfortunately this does not work correctly with a network mounted homedisk. To solve this you need to find a suitable location on your disk to store files. Usually &lt;kbd&gt;/mnt/D&lt;/kbd&gt; is a good location.<br /> You set this by editing the &lt;kbd&gt;data-root&lt;/kbd&gt; in &lt;kbd&gt;~/.config/docker/daemon.json&lt;/kbd&gt;. Example:<br /> $ mkdir /mnt/D/docker<br /> $ f=~/.config/docker/daemon.json<br /> $ echo &quot;$((cat $f || echo {}) | jq '.&quot;data-root&quot; = &quot;/mnt/D/docker&quot;')&quot; &gt; $f<br /> $ systemctl --user restart docker<br /> <br /> You can also edit the file with a text editor.<br /> <br /> An alternative approach is to store a small ext4 formatted diskimage in your homedir:<br /> $ truncate -s 25G ~/.docker.img<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:X' ~<br /> $ nfs4_setfacl -a 'A::nobody@rug.nl:RWX' ~/.docker.img <br /> $ mkfs.ext4 -E root_owner -m0 -L docker ~/.docker.img<br /> Now you need to make sure this disk image is mounted when you login:<br /> $ cat ~/.pam_mount.conf &lt;&lt;EOF<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br /> &lt;!DOCTYPE pam_mount SYSTEM &quot;pam_mount.conf.xml.dtd&quot;&gt;<br /> &lt;pam_mount&gt;<br /> &lt;volume fstype=&quot;ext4&quot; mountpoint=&quot;~/.local/share/docker&quot; options=&quot;async,nosuid,loop,exec,noatime,nodev&quot; path=&quot;~/.docker.img&quot; /&gt;<br /> &lt;/pam_mount&gt;<br /> EOF<br /> The logout and login again. <br /> <br /> === testing docker ===<br /> <br /> $ docker run hello-world<br /> $ docker run -it ubuntu bash<br /> $ docker run -d -p 8881:8080 inanimate/echo-server<br /> Then check in your browser &lt;kbd&gt;localhost:8881&lt;/kbd&gt;<br /> <br /> == Standard docker installation ==<br /> <br /> It is still possible to request a standard docker installation (ie. the docker daemon runs as root).<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Main_Page&diff=801 2021-02-04T08:34:49Z

<p>Remco: trigger e-mail from lwpwiki</p> <hr /> <div>[[Category:Main]]<br /> = LWP Wiki =<br /> Welcome to the LWP-Wiki!! For general LWP information, [http://myuniversity.rug.nl/infonet/medewerkers/ict/werkplek/werkplekken/linuxwerkplek/ the LWP main page] is the starting point.&lt;br/&gt;<br /> If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before.&lt;br/&gt;<br /> &lt;!--<br /> !!! EDITOR's NOTES !!!<br /> When creating a new page DON'T forget to add eg. [[Category:faq]] on the page, else it won't show up in searches!<br /> Create a new announcement by pasting the next line underneath the === Announcements === header and replacing '2' with the actual information.<br /> To edit the side bar: https://lwpwiki.webhosting.rug.nl/index.php/MediaWiki:Sidebar<br /> {{Announcement| ~~~~| 2}}<br /> --&gt;<br /> <br /> == Corona ==<br /> Staff can have [[Remote access]] to their LWP. We will keep up support as best we can.<br /> <br /> Staff and students can have [[Remote access]] to lwp-ssh.service.rug.nl and Alfa Informatica students can also connect to karora.let.rug.nl.<br /> <br /> When logged in a physical PC at university premises you automatically have file system permissions to put your public key in place to be able to access karora/lwp-ssh remotely from outside the RUG network. As a corona-time alternative we can put it in place for you if you send us the public key together with a photo of your ID (RUG-card, drivers license,..) from a RUG e-mail address.<br /> <br /> == Announcements ==<br /> {{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 11:39, 7 March 2019 (CET)| Created [[Home directory|faq page about home directory]]. Moved page about [[quota]] to this new page, and created [[kerberos ticket expired|page about kerberos tickets expiration]] }}<br /> {{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 17:30, 25 October 2018 (CEST)| [[Dropbox]] has stopped supporting most linux file systems. We've thought of a workaround to still access your [[Dropbox]]. You could also just switch to using our own https://unishare.nl instead. You get a lot more space and it's free.}}<br /> {{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 17:21, 18 October 2018 (CEST)| Quota information updated. See: [[Quota]]}}<br /> {{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 12:31, 13 February 2018 (CET)| SPSS25 is now available.}}<br /> <br /> <br /> == Contact ==<br /> If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering &quot;support&quot; on a LWP command line or selecting it from the menu.&lt;br/&gt;<br /> For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].<br /> <br /> Kerberos ticket expired</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Data_retention_policy&diff=795 2020-05-26T06:50:13Z

<p>Remco: Created page with &quot;== RUG account life cycle and your home directory == ==== Summary / TL;DR: ==== When you leave the university your home directory may be deleted permanently after 2 years...&quot;</p> <hr /> <div>== RUG account life cycle and your home directory ==<br /> <br /> ==== Summary / TL;DR: ====<br /> <br /> When you leave the university your home directory may be deleted<br /> permanently after 2 years (but not before).<br /> <br /> ===== Details: =====<br /> <br /> Your general RUG account (p/s/f/g number account) is used to log<br /> in to an LWP and is subject to the general university policy<br /> governing these accounts. When you leave the university for any<br /> reason your account will be disabled.<br /> <br /> When your account has been disabled for more than 6 consecutive<br /> months we may archive your home directory. This means it will be<br /> compressed and put aside.<br /> <br /> In case your account becomes enabled once again after your home<br /> directory was archived, we can reinstate the home directory<br /> manually on request.<br /> <br /> When your account has been disabled uninterruptedly for two or<br /> more years we may delete your home directory and/or its archive<br /> entirely and permanently. It will still be possible to restore it<br /> from tape backup up for to 3 months after this, but this will<br /> only be done under exceptional circumstances.<br /> <br /> You will *not* recieve any warnings about this, since disabling<br /> RUG accounts is already accompanied with warning emails.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=FAQ&diff=794 2020-05-26T06:48:40Z

<p>Remco: </p> <hr /> <div>[[Category:faq]]<br /> Here we try to write down solutions to most common issues. If you think something is missing, please let [mailto:lwp@rug.nl us] know.<br /> ----<br /> &lt;br/&gt;<br /> * [[Installing]]<br /> * [[Remote access]]<br /> * [[Software]]<br /> * [[Printing]]<br /> * [[Networking]]<br /> * [[Graphics]]<br /> * [[Home directory]]<br /> * [[Docker]]<br /> * [[Anaconda]]<br /> * [[Miscellaneous]]<br /> * [[Data retention policy]]<br /> &lt;br/&gt;</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Docker&diff=759 2019-04-19T07:24:14Z

<p>Remco: Created page with &quot;It is possible to run docker containers on your computer or use them for teaching. === Personal use: === - just send a message to mailto:lwp@rug.nl stating your intentions...&quot;</p> <hr /> <div>It is possible to run docker containers on your computer or use them for teaching.<br /> <br /> === Personal use: ===<br /> - just send a message to mailto:lwp@rug.nl stating your intentions<br /> - by default you will be able to run any container but will not be able to mount a local path into the container.<br /> - these limitations can be lifted on a case by case basis (ie. we have to know about it)<br /> <br /> === Teaching use: ===<br /> - just send a message to mailto:lwp@rug.nl, we need to know the container name and whether you need to<br /> forward ports and use local storage. In principle we will mount local storage in /tmp, this way it is cleaned up when the LWP reboots</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=FAQ&diff=758 2019-04-19T07:10:02Z

<p>Remco: </p> <hr /> <div>[[Category:faq]]<br /> Here we try to write down solutions to most common issues. If you think something is missing, please let [mailto:lwp@rug.nl us] know.<br /> ----<br /> &lt;br/&gt;<br /> * [[Installing]]<br /> * [[Remote access]]<br /> * [[Software]]<br /> * [[Printing]]<br /> * [[Networking]]<br /> * [[Graphics]]<br /> * [[Home directory]]<br /> * [[Docker]]<br /> * [[Miscellaneous]]<br /> &lt;br/&gt;</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Miscellaneous&diff=757 2019-04-19T07:09:28Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> * [[LWP classroom locations]]<br /> * [[~/.bashrc]]<br /> * [[Fresh user profile| How to give yourself a fresh user profile]]<br /> * [[Fresh firefox profile while keeping bookmarks]]<br /> * [[UWP2]]<br /> * [[X-apps_in_windows| How to use x-deep 32 to get X applications under Windows to work]]<br /> * [[Getting to your Windows X:-drive| Getting to your Windows X: drive]]<br /> * [[Getting to your Windows Y:-drive| Getting to your Windows Y: drive]]<br /> * [[Shared directories]]<br /> * [[Xfce4 How To]]<br /> * [[Can I have root rights?]]<br /> * [[How do I lock my desktop?]]<br /> * [[When I log in, the system says it needs a reboot]]<br /> * [[Git server]]<br /> * [[Time Capsule]] (only for JBI and Alice users)<br /> * [[Google Drive]]<br /> * [[How to disable suspend/hibernate by screensaver]]<br /> * [[How to check which version of LWP you're running]]</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Dropbox&diff=719 2018-11-02T11:10:35Z

<p>Remco: </p> <hr /> <div>Dropbox has stopped the support of all linux file systems except ext4. You home dir is a network disk using NFS (Networked File System). We've tried moving Dropbox to a local disk formatted with the ext4 file system, but the Dropbox client will not move the data from your home drive to anywhere else... it claims it will, but then fails.&lt;br/&gt;<br /> As a (''probably permanent'') workaround, for RUG employees it's possible to either copy your files into [https://unishare.nl Unishare] or link your Dropbox account to your [https://unishare.nl Unishare] account as &quot;external storage&quot;, so you won't need the Dropbox client anymore. You can use the Owncloud client instead. Owncloud is the software used to create the Unishare environment. The Owncloud client is installed on all LWP's.&lt;br/&gt;<br /> <br /> ==Option 1 Move your files into unishare==<br /> # Stop de dropbox client<br /> # Start the owncloud client<br /> # After login you can either<br /> ## copy your files manually into the ~ownCloud directory <br /> ## or add ~/Dropbox as a sync folder<br /> # You now must use the ownCloud client on your other computers as well<br /> <br /> ==Option 2 Link your dropbox account==<br /> <br /> === First enable access to your Dropbox account===<br /> # Go to https://www.dropbox.com and login to your account.<br /> # In the bottom right corner, click the dot menu (the 3 dots) and select '''Developers'''.<br /> # On the new page select '''My apps'''.<br /> # Click '''Create app'''.<br /> # At '''1''' select '''Dropbox API'''<br /> # At '''2''' select '''Full Dropbox''' if you want to be able to access your entire Dropbox account from within your Unishare account. If you only need/want access to one specific folder, select '''App folder'''.<br /> # At '''3''' Enter any name for the app. Something like &quot;Unishare&quot; will help you recognize it in the future.<br /> # Click the '''Create app''' button.<br /> # On the next page we have to give an address at '''Redirect URIs'''. Enter the following address, '''&lt;nowiki&gt;https://unishare.nl/index.php/settings/personal?sectionid=storage&lt;/nowiki&gt;''' and don't forget to click '''Add'''.<br /> # Above the '''Redirect URIs''' you should see '''App key''' and '''App secret''', you'll need those to give Unishare access to your Dropbox.<br /> <br /> ===Next add your Dropbox account to Unishare===<br /> # Now go to https://unishare.nl/index.php/login and login there using your RUG account.<br /> # On your home page click in the upper right corner (on your name) and select '''Settings'''.<br /> # On the left side of your settings page, select '''Storage'''.<br /> # On the new page click the '''Add storage''' button and select '''Dropbox V2'''.<br /> # Change the '''Folder name''' (or don't).<br /> # For '''Client ID''' use the '''App key''' you took note of at the end of the previous section and for '''Client secret''' use the '''App secret'''.<br /> # Click the '''Grant access''' button and you should see it become green.<br /> <br /> That should be it, now there should be an extra folder between your files with the name you gave it (or didn't give it).<br /> <br /> You can now continue to use the Dropbox client on other computers or switch to the owncloud client.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Dropbox&diff=718 2018-11-02T11:06:14Z

<p>Remco: </p> <hr /> <div>Dropbox has stopped the support of all linux file systems except ext4. You home dir is a network disk using NFS (Networked File System). We've tried moving Dropbox to a local disk formatted with the ext4 file system, but the Dropbox client will not move the data from your home drive to anywhere else... it claims it will, but then fails.&lt;br/&gt;<br /> As a (''probably permanent'') workaround, for RUG employees it's possible to either copy your files into [[Unisharehttps://unishare.nl|Unishare]] or link your Dropbox account to your Unishare account as &quot;external storage&quot;, so you won't need the Dropbox client anymore. You can use the Owncloud client instead. Owncloud is the software used to create the Unishare environment. The Owncloud client is installed on all LWP's.&lt;br/&gt;<br /> <br /> ==Option 1 Move your files into unishare==<br /> # Stop de dropbox client<br /> # Start the owncloud client<br /> # After login you can either<br /> ## copy your files manually into the ~ownCloud directory <br /> ## or add ~/Dropbox as a sync folder<br /> # You now must use the ownCloud client on your other computers as well<br /> <br /> ==Option 2 Link your dropbox account==<br /> <br /> === First enable access to your Dropbox account===<br /> # Go to https://www.dropbox.com and login to your account.<br /> # In the bottom right corner, click the dot menu (the 3 dots) and select '''Developers'''.<br /> # On the new page select '''My apps'''.<br /> # Click '''Create app'''.<br /> # At '''1''' select '''Dropbox API'''<br /> # At '''2''' select '''Full Dropbox''' if you want to be able to access your entire Dropbox account from within your Unishare account. If you only need/want access to one specific folder, select '''App folder'''.<br /> # At '''3''' Enter any name for the app. Something like &quot;Unishare&quot; will help you recognize it in the future.<br /> # Click the '''Create app''' button.<br /> # On the next page we have to give an address at '''Redirect URIs'''. Enter the following address, '''&lt;nowiki&gt;https://unishare.nl/index.php/settings/personal?sectionid=storage&lt;/nowiki&gt;''' and don't forget to click '''Add'''.<br /> # Above the '''Redirect URIs''' you should see '''App key''' and '''App secret''', you'll need those to give Unishare access to your Dropbox.<br /> <br /> ===Next add your Dropbox account to Unishare===<br /> # Now go to https://unishare.nl/index.php/login and login there using your RUG account.<br /> # On your home page click in the upper right corner (on your name) and select '''Settings'''.<br /> # On the left side of your settings page, select '''Storage'''.<br /> # On the new page click the '''Add storage''' button and select '''Dropbox V2'''.<br /> # Change the '''Folder name''' (or don't).<br /> # For '''Client ID''' use the '''App key''' you took note of at the end of the previous section and for '''Client secret''' use the '''App secret'''.<br /> # Click the '''Grant access''' button and you should see it become green.<br /> <br /> That should be it, now there should be an extra folder between your files with the name you gave it (or didn't give it).<br /> <br /> You can now continue to use the Dropbox client on other computers or switch to the owncloud client.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:NetworkManager.png&diff=492 2016-11-10T14:34:04Z

<p>Remco: </p> <hr /> <div></div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:Shrew2.png&diff=486 2016-11-08T10:04:29Z

<p>Remco: </p> <hr /> <div></div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:Shrew1.png&diff=485 2016-11-08T10:04:08Z

<p>Remco: </p> <hr /> <div></div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:Properties.png&diff=480 2016-11-07T10:23:55Z

<p>Remco: </p> <hr /> <div></div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=File:Wizard.png&diff=479 2016-11-07T10:23:33Z

<p>Remco: </p> <hr /> <div></div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Miscellaneous&diff=476 2016-11-07T09:46:38Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> * [[LWP classroom locations]]<br /> * [[Fresh user profile| How to give yourself a fresh user profile]]<br /> * [[~/.bashrc]]<br /> * [[Fresh firefox profile while keeping bookmarks]]<br /> * [[UWP2]]<br /> * [[X-apps_in_windows| How to use x-deep 32 to get X applications under Windows to work]]<br /> * [[Getting to your Windows X:-drive| Getting to your Windows X: drive]]<br /> * [[Getting to your Windows Y:-drive| Getting to your Windows Y: drive]]<br /> * [[Shared directories]]<br /> * [[Xfce4 How To]]<br /> * [[Can I have root rights?]]<br /> * [[How do I lock my desktop?]]<br /> * [[When I log in, the system says it needs a reboot]]<br /> * [[Git server]]<br /> * [[Time Capsule]] (only for JBI and Alice users)<br /> * [[VPN]] (only for Alice users)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Time_Capsule&diff=471 2016-10-13T12:54:49Z

<p>Remco: Remco moved page JBI Time Capsule to Time Capsule without leaving a redirect</p> <hr /> <div>If you are *not* a member of:<br /> <br /> * Intelligent Systems<br /> * Scientific Visualization and Computer Graphics<br /> * Fundamental Computing<br /> * Software Engineering<br /> * Distributed Systems <br /> * Artificial Intelligence<br /> <br /> you will have to get in touch with me ([mailto:remco.wouts@rug.nl remco wouts]) first before you can use this Time Capsule service. <br /> <br /> On your mac choose '''''Finder-&gt;Go-&gt;Connect to Server'''''(⌘K). In the '''Connect to Server''' dialog, enter: <br /> <br /> &lt;span style=&quot;text-align:center; color:red; text-decoration:underline;&quot;&gt;afp://turing13.housing.rug.nl&lt;/span&gt;.<br /> <br /> Connect and provide your credentials (p-number and password). They are send encrypted to the server. You will be presented with an empty share named '''''Time capsule for &lt;your name&gt;'''''.<br /> <br /> If you successfully mounted your Time Capsule share, you can select it as the backup disk in the '''Time Machine''' ''System Preferences'' dialog. You should see your share and a few other disks on the network (ignore those). Selecting it will prompt you for your credentials once more. You can unmount the share from the Finder now. You can backup more then one computer on the same share. If you need more then the default space provided for then you will have to get in touch with me. YOu can also backup your computer at more then once place (eg. at home and at work).<br /> <br /> You may want to use the '''options''' button to exclude certain directories from your backup (Music, Pictures and Videos perhaps). I strongly urge you to add:<br /> <br /> * ~/Library/Suggestions #database with web suggestions, changes continously<br /> * ~/Library/Download <br /> <br /> Also useful is the option ''Show Time Machine in menubar''.<br /> <br /> The first backup will be a full backup and it will take quite long (throughput approx. 70-80MiB/s for a gigabit connection, slower over WiFi). The '''Time Machine''' ''System Preferences'' dialog will give you an optimistic prognosis of the time it will take. Just let it finish. Once setup Time Machine does hourly incremental back-ups and they are swift enough. Take note that laptops will not be backed up automatically by Time Machine when unplugged. You can of course start a back-up by hand once in a while.<br /> <br /> Mac help can tell you how to restore items backed up with Time Machine. It is also possible to mount your share on another mac and use it to copy files back and forth. Better maybe is to use your homedir for that.<br /> <br /> If you really think backing up is slow, try:<br /> <br /> $ sudo sysctl -w net.inet.tcp.delayed_ack=0<br /> It may do the trick if you have very many small files to backup.</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Miscellaneous&diff=470 2016-10-13T12:51:59Z

<p>Remco: </p> <hr /> <div>[[Category:misc-faq]]<br /> * [[LWP classroom locations]]<br /> * [[Fresh user profile| How to give yourself a fresh user profile]]<br /> * [[~/.bashrc]]<br /> * [[Fresh firefox profile while keeping bookmarks]]<br /> * [[UWP2]]<br /> * [[X-apps_in_windows| How to use x-deep 32 to get X applications under Windows to work]]<br /> * [[Getting to your Windows X:-drive| Getting to your Windows X: drive]]<br /> * [[Getting to your Windows Y:-drive| Getting to your Windows Y: drive]]<br /> * [[Shared directories]]<br /> * [[Xfce4 How To]]<br /> * [[Can I have root rights?]]<br /> * [[How do I lock my desktop?]]<br /> * [[When I log in, the system says it needs a reboot]]<br /> * [[Git server]]<br /> * [[Time Capsule]] (only for JBI and AI users)</div>

Remco https://lwpwiki.webhosting.rug.nl/index.php?title=Time_Capsule&diff=469 2016-10-13T12:51:32Z

<p>Remco: </p> <hr /> <div>If you are *not* a member of:<br /> <br /> * Intelligent Systems<br /> * Scientific Visualization and Computer Graphics<br /> * Fundamental Computing<br /> * Software Engineering<br /> * Distributed Systems <br /> * Artificial Intelligence<br /> <br /> you will have to get in touch with me ([mailto:remco.wouts@rug.nl remco wouts]) first before you can use this Time Capsule service. <br /> <br /> On your mac choose '''''Finder-&gt;Go-&gt;Connect to Server'''''(⌘K). In the '''Connect to Server''' dialog, enter: <br /> <br /> &lt;span style=&quot;text-align:center; color:red; text-decoration:underline;&quot;&gt;afp://turing13.housing.rug.nl&lt;/span&gt;.<br /> <br /> Connect and provide your credentials (p-number and password). They are send encrypted to the server. You will be presented with an empty share named '''''Time capsule for &lt;your name&gt;'''''.<br /> <br /> If you successfully mounted your Time Capsule share, you can select it as the backup disk in the '''Time Machine''' ''System Preferences'' dialog. You should see your share and a few other disks on the network (ignore those). Selecting it will prompt you for your credentials once more. You can unmount the share from the Finder now. You can backup more then one computer on the same share. If you need more then the default space provided for then you will have to get in touch with me. YOu can also backup your computer at more then once place (eg. at home and at work).<br /> <br /> You may want to use the '''options''' button to exclude certain directories from your backup (Music, Pictures and Videos perhaps). I strongly urge you to add:<br /> <br /> * ~/Library/Suggestions #database with web suggestions, changes continously<br /> * ~/Library/Download <br /> <br /> Also useful is the option ''Show Time Machine in menubar''.<br /> <br /> The first backup will be a full backup and it will take quite long (throughput approx. 70-80MiB/s for a gigabit connection, slower over WiFi). The '''Time Machine''' ''System Preferences'' dialog will give you an optimistic prognosis of the time it will take. Just let it finish. Once setup Time Machine does hourly incremental back-ups and they are swift enough. Take note that laptops will not be backed up automatically by Time Machine when unplugged. You can of course start a back-up by hand once in a while.<br /> <br /> Mac help can tell you how to restore items backed up with Time Machine. It is also possible to mount your share on another mac and use it to copy files back and forth. Better maybe is to use your homedir for that.<br /> <br /> If you really think backing up is slow, try:<br /> <br /> $ sudo sysctl -w net.inet.tcp.delayed_ack=0<br /> It may do the trick if you have very many small files to backup.</div>

Remco