-
Notifications
You must be signed in to change notification settings - Fork 29
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
Fix some bitrot in enter_grain #252
Fix some bitrot in enter_grain #252
Conversation
Maybe hold off on this one until we decide whether to just switch over to using nsenter. |
@zenhack Agreed on that. |
I'm excited to see the bitrot being fixed, and also excited to see the
possibility that we'll delete this code. :)
For what it's worth, some of the flags I was using were due to my desire to
keep the output binary file as small as possible. Maybe this was one of
them.
|
Hm, the binary on master is >600K vs this one at 200K, so if that's the case, the compiler has gotten better by a margin that swallows those savings pretty thoroughly. We still shouldn't commit it to the repo though... |
Since #253 is concerned about excess commits of binary files, if you fix the enter-grain binary, can we get both this fix and that fix in a single commit, so we are only adding one copy of the binary? |
Sure, I'll --amend it onto this one. We can maybe do the PyPI packaging soonish so we don't have to worry about this again. |
6abf69b
to
11f9474
Compare
@ocdtrekkie, updated. should work now. |
This is one commit instead of two because we didn't want to bloat the repository with two updates to the executable. We should really just remove the binary from the repo and build it; see sandstorm-io#253 The bitrot: With #![feature(alloc_system)] I get an error from the rust toolchain that the feature has been removed. We don't appear to actually be using this anyway, so let's just remove it.
11f9474
to
8ce6bd4
Compare
I tested this locally and I'm happy with it. |
with #![feature(alloc_system)] I get an error from the rust toolchain
that the feature has been removed. We don't appear to actually be using
this anyway, so let's just remove it.