-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New package: boot-66serv-2.1.0 #23122
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
Conversation
8b5ee93 to
f2d6456
Compare
000a8cf to
7ad44eb
Compare
7255381 to
68e0e4c
Compare
80f132c to
c5b25b8
Compare
|
i'm interested in moving my Void system over to using 66, so i've been playing around with 66 on Void in a VM. Building i'm actually very new to s6 and 66, so i'm taking this opportunity to document things as i go, in the form of a putative section of the Handbook: https://github.com/flexibeast/void-docs/blob/add-s6-and-66/src/config/services/s6-and-66/index.md Please feel free to let me know of any errors i've made thus far, and to make suggestions about what else should/could be added! |
With this template, make sure, you take the v0.0.4.x branch and even this is not completely tested. (and feel free to pr to this branch). ;)
We are also working on void-docs. (again: feel free to PR to branch). If you compare this to yours, there is indeed one mistake: You don't have to enable tty* in the tree you are calling root, because that should be started in your boot tree. You can cofigure the amount off ttys in the step Configure As long as it is not merged, watch out for this #23330 PR, because 66 in repos has a small error, which creates folder '$datarootdir', where you invoke 66-tree. I am glad, that this PR works for you! :) |
Ah, thank you. :-)
Oh wow, great! Well, there's no need for my branch, then, so i'll remove it and work on your repo instead. To that end, i can submit PRs for ensuring the docs follow the Handbook style guide. i presume other members of the Void team have already given their okay for this information being included in the Handbook? Just need to check, as i'm one of the people who would be reviewing and/or merging such an inclusion. :-) Thanks for all your work! |
|
@flexibeast : Thank you for taking an interest in our experiments - they run our machines, so they are halfway to world domination :P |
ae79fec to
884d8f4
Compare
|
@mobinmob There is an update for this package. |
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on: void-linux#23122 void-linux#21142 [ci-skip]
based on #21142