-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
DietPi-PreBoot | Separate first boot and regular boot steps #2833
DietPi-PreBoot | Separate first boot and regular boot steps #2833
Conversation
Very nice 👍 Many thanks for the PR, i'll take a look and test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work 👍
Some minor changes required from my end, mostly for consistency.
Im glad to have your feedback. Im on a contract right now but Ill look at it in the next weeks |
I just measured the execution time, to see if there is any effect of unused code:
Largest impact is of course the two child scripts (CPU governor + LED settings) that are executed in subshell and load dietpi-globals in case. Actually it should be at least possible to skip led settings, an additional setting to revert to system defaults, which removes the settings file and then scripts the execution. Actually we could move this as well as the CPU governor adjustment into an own systemd unit each. It does not really matter when they run, just after DietPi-RAMdisk. So they can be Type=simple to not delay any other boot scripts. This also makes it again simpler to revert to system defaults => disable the related systemd unit. Once applied settings (settings file) can be preserved then while toggling the service. Finally with this the preboot script can be removed completely. Only thing that we need to run somewhere is:
Both are only required for RPi, hw_model estimation additionally is a failsafe thing for other devices as well.
|
This is resolved with current kernel under stretch. Can be removed. Done 🈯 #2833 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FredericGuilbault |
Sure, no problem. I think you could also create a branch and modify this pullrequest to change it to the new branch and merge it. But I don't mind it's up to you. |
+ DietPi-FirstBoot | Add all "(( $G_DIETPI_INSTALL_STAGE == -1 ))" steps here + DietPi-FirstBoot | Rename to ".bash" file ending to make shell requirement clear + DietPi-FirstBoot | Do obtain network details here, which is already done in DietPi-PreBoot + DietPi-FirstBoot | Failsafe dietpi.txt and .network value grabbing, to avoid errors and instead apply defaults + DietPi-FirstBoot | Minor coding and alignment
+ DietPi-Boot | In attempt to resolve conflict due to: 64bd543#diff-620191171f47b4763a532e984acd2e8b
@FredericGuilbault @Fourdee
EDIT: Made it, "HTTPS Everywhere" broke the web editor strangely 😄. |
Okay I merge the PR and run some tests. |
Nice work 💃 |
Please email me an address to [email protected]. I'll ship some DietPi stickers out to you for your excellent work on this PR. Apologies for the delay ^^ |
#2791
This PR separate the pre-network part of the first boot process into it's own .service file.
( post-login part is yet to be done. )
Tested on RPI , Qemu-ARM and Qemu-i686