Allow specifying boot file, fix instructions and cope with smbserver name #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
+1 thanks for the fix! |
Owner
|
Thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will
BOOTFILE=shimx64.efiin order to control the boot file served by the PXE server.README.mdconcerning the alternative method of getting the BCD file. This makes use of theBOOTFILEvariable. (I removed the note about the BCD template file because as far as I seegrab-bcd.shtakes care of that.)start-smb-serverfunction agnostic of the name of the smbserver executable. This can either besmbserver.pywhen installed viapiporimpacket-smbserverwhen installed from Kali repositories. (There was a complaint in Success on HP ProBook 450 G10 #24)