reshuffle

admin-guide/troubleshooting/boot.md

@@ -20,7 +20,7 @@ The Linux Team can check in the journal of boot.psi.ch what was actually downloa
 
 If that is confirmed, then the issue is probably a so far unknown Vendor Class which is sent with the DHCP request of the firmware. It is configured in QIP:
 
-![Vendor Class to network boot configuration in QIP](boot/qip.png)
+![Vendor Class to network boot configuration in QIP](_static/boot_qip.png)
 
 Please inform the network team about the missing Vendor Class.
 
@@ -29,10 +29,10 @@ Please inform the network team about the missing Vendor Class.
 ## Redirect Serial Output to File in VMware
 
 To change the serial port settings the VM needs to be shut down. Then edit the VM settings and add a new serial device by clicking "ADD NEW DEVICE" on top right and there select "Serial Port".  
-![Add Serial Port](boot/add_serial_port.png)
+![Add Serial Port](_static/boot_add_serial_port.png)
 
 The serial port should then be connected to a file on the datastore `serial_console`:  
-![Serial Port Settings](boot/serial_port_settings.png)
+![Serial Port Settings](_static/boot_serial_port_settings.png)
 
 At the moment we have this setup for `lxdev06`, `lxdev07` and `lxdev08` already prepared.
 

admin-guide/troubleshooting/pam.md

@@ -40,7 +40,7 @@ auth        optional      pam_echo.so "Have passed pam_localuser and pam_unix"
 
 ## PAM Call Stack with SystemTap
 
-When debugging an PAM issue with the RedHat support, they provided us a neat Systemtab script to create a PAM call stack of the `do_pam_setcred()` function in sshd. You find it [here](pam/para-callgraph-pam.stp).
+When debugging an PAM issue with the RedHat support, they provided us a neat Systemtab script to create a PAM call stack of the `do_pam_setcred()` function in sshd. You find it [here](_static/para-callgraph-pam.stp).
 
 For other PAM functions or other processes this script would need changes.