I've begun to draft the October newsletter on blog.centos.org If your SIG would like to report anything to the broader CentOS community, please do let me know what you'd like to say.
Or, if you'd like to edit it yourself, please go right ahead and make your edits directly in my draft.
If there's other content you'd like to contribute to the newsletter, please do let me know. The centos-promo list is the best place to discuss your newsletter ideas.
The deadline for content is end of day, October 1st.
If you've not edited anything in the blog before: Blog logins are tied to your CentOS account. After you've logged into the blog editing interface once - https://blog.centos.org/wp-admin - just let me know, and I can add you to the Editors group.
Thanks!
I just received a new computer which cannot install or run Windows 7. So...of course I immediately thought of KVM and virt-viewer in kiosk mode. I've searched and cannot find any setup instructions or advice for how to do several things. Any assistance or pointers would be appreciated. Let me know if someone has already created the wheel or if there is a better way to manage this.
1) Configure the host so that users cannot escape the virt-viewer app or other do anything to the host. Perhaps disable GDM or use a different windows manager?
My plan is to have the hosts boot in run level 5, start the guest, auto- matically log in as the kiosk user, then auto-lauch virt-viewer. Upon shutdown of the guest, the guest would be restarted.
2) Configure a read-only image with Windows 7 that can automatically update its computer name and hostname.
If needed I would consider having a generic image which I'll need to make a custom copy for each of several similar computers.
3) Remove the pointer on the host so only the guest pointer is visible.
Also, it's likely that I will use ansible to manage configuration files and set up times when the guest is started in read-write mode to update Windows and various apps. Although I'm hoping to be able to update a single image and roll it out without needing to touch each host.
Thanks for any guidance!
c
Final notice:
The newsletter should go out tomorrow (possibly Wednesday). If you wish to submit a SIG report, you can:
* Email me * Put it directly into the draft blog post (email me for instructions) * Send it to me via any other method that works for you.
Meanwhile, I'll be using your SIG meeting minutes instead, unless I hear from you. Thanks.
On 9/20/18 4:31 PM, Rich Bowen wrote:
I've begun to draft the October newsletter on blog.centos.org If your SIG would like to report anything to the broader CentOS community, please do let me know what you'd like to say.
Or, if you'd like to edit it yourself, please go right ahead and make your edits directly in my draft.
If there's other content you'd like to contribute to the newsletter, please do let me know. The centos-promo list is the best place to discuss your newsletter ideas.
The deadline for content is end of day, October 1st.
If you've not edited anything in the blog before: Blog logins are tied to your CentOS account. After you've logged into the blog editing interface once - https://blog.centos.org/wp-admin - just let me know, and I can add you to the Editors group.
Thanks!
-
Carl T. Miller -
Rich Bowen