Rework demo scripts

[talk-cockpit-auth-anywhere.git] / cockpit-auth-anywhere.md

diff --git a/cockpit-auth-anywhere.md b/cockpit-auth-anywhere.md
index e633e2bb73294353cffc2b532d2b88fc8c62513a..05298e25f34b64ec5032c15f1eaf66ea6e9ae0da 100644 (file)
--- a/cockpit-auth-anywhere.md
+++ b/cockpit-auth-anywhere.md
@@ -48,7 +48,6 @@ resize2fs /dev/vg0/data1
  - Zero configuration
 
 :::notes
  - Zero configuration
 
 :::notes

-- TODO: check out bots in "make deps", add ./vm-run windows-10 to prep.sh

 - Switch to Windows virt-viewer, open Edge, show Cockpit
 - Quit virt-viewer
 - Zero configuration so far, other than possibly installing cockpit pkg and enabling cockpit.socket
 - Switch to Windows virt-viewer, open Edge, show Cockpit
 - Quit virt-viewer
 - Zero configuration so far, other than possibly installing cockpit pkg and enabling cockpit.socket


@@ -107,7 +106,6 @@ resize2fs /dev/vg0/data1
 nothing Cockpit specific running outside of the user session
 
 :::notes
 nothing Cockpit specific running outside of the user session
 
 :::notes

-- TODO: start rhel7 VM in prep.sh, set hostname

 - ws and the login session don't need to run on the same machine
 - cockpit-session is meant to be customizable for your purposes
 - most obvious replacement is to let ssh start a session; that already does the
 - ws and the login session don't need to run on the same machine
 - cockpit-session is meant to be customizable for your purposes
 - most obvious replacement is to let ssh start a session; that already does the