0.2.0 --- openkal 0.13: whether a node may be started - #2
Merged
Merged
Conversation
MEMFS keeps the mode a node was given, so this implementation claims KAL_FS_PROP_EXECUTABLE, reports KAL_INFO_EXECUTABLE for a file and performs kal_fs_set_executable_at with the three execute bits as one property. ENOEXEC maps to kal_err_not_program for completeness; openkal.process is not provided here, so nothing reaches it today. Comments carry no emoji.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follows mcpplibs/openkal#33 (branch
openkal-0.13). MEMFS keeps a node's mode, soKAL_FS_PROP_EXECUTABLEis claimed,KAL_INFO_EXECUTABLEis reported for a file, andkal_fs_set_executable_attreats the three execute bits as one property.ENOEXECmaps tokal_err_not_program. Comments carry no emoji.