-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unattended Install has garbled EULA screen on first boot #493
Comments
Hi! We are aware of this, and IIRC it's fixed in our Pinging @stormi |
It is also possible to fix it with a script called by the answerfile, during the installation process, without waiting for new ISOs. |
A script returned by the answerfile seems like the path of least resistance for us. We haven't set up a build environment for xcp-ng and just rely on the released ISOs. If there is a specific commit/pr/etc that I can refer to that has the fix, I'd appreciate being pointed in the right direction. |
The fixed EULA can be found at https://github.com/xcp-ng/branding-xcp-ng/blob/master/branding/EULA and must be copied the one in You can define a script to be run in the context of the installed system with The first argument passed to the script is the path to the directory where the filesystem is mounted. |
Oh, the fix is literally just replacing a single text file. I was thinking this was a much more convoluted issue with ncurses/xsconsole. I'll just repackage our image with the new file. I misunderstood the earlier comments, assuming that a true "build from source" was needed, instead of just replacing a single file in the finished image. Thanks, guys! |
When using an unattended installation with 8.2.0, the first (or subsequent) boot shows the EULA acceptance screen, but the text appears to be broken.
greppable text:
Our answerfile is as follows:
This only appears on some hardware, as the appropriate screen will show on other hardware using the same installation method. I wish there was some way to reliably reproduce it, but it seems specific to the host hardware. Any additional information you'd like about the hardware can be supplied, but it's difficult to just provide something succinct as this is on development OEM hardware (e.g. I can't just link to some document with all hardware specs).
The text was updated successfully, but these errors were encountered: