LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   *BSD (https://www.linuxquestions.org/questions/%2Absd-17/)
-   -   [Not Really] Doas Scriptablitiy (https://www.linuxquestions.org/questions/%2Absd-17/%5Bnot-really%5D-doas-scriptablitiy-4175655893/)

anon033 06-18-2019 12:00 PM

Thank you for the link to the flak post, I myself love reading more about the applications I use and have a huge respect for the OpenBSD project. I know, but I also feel bad when a post of mine turns heated even if over ideological difference :(

hitest 06-18-2019 02:10 PM

Quote:

Originally Posted by FOSSilized_Daemon (Post 6006791)
I wouldn't asked this question had I known this thread would have gotten this out of hand....

Your question was a good question. We have no control over how other members post. I found this thread to be worthwhile and informative.

anon033 06-22-2019 01:37 PM

Quote:

Originally Posted by hitest (Post 6006872)
Your question was a good question. We have no control over how other members post. I found this thread to be worthwhile and informative.

I myself was actually considering adding stdin support as an optional patch to doas (if for other reason than to use doas over sudo as I wouldn't use enough of sudo to make it viable over doas). Do you think anyone else would be interested? Upstream maybe?

hitest 06-22-2019 01:49 PM

Quote:

Originally Posted by FOSSilized_Daemon (Post 6008055)
I myself was actually considering adding stdin support as an optional patch to doas (if for other reason than to use doas over sudo as I wouldn't use enough of sudo to make it viable over doas). Do you think anyone else would be interested? Upstream maybe?

You can always try to submit it. I also like sudo and have it installed on OpenBSD 6.5.

jggimi 06-22-2019 02:18 PM

I think you should give it a try. The appropriate steps would be:
  1. Check the misc@ and tech@ archives for any prior history. I just looked and didn't note any, but you should do more than trust my cursory review.
  2. Develop your enhancement against -current, conforming to style(9) guidelines.
  3. Submit a unified diff(1) to the tech@ mailing list.
  4. You may get some criticism in response. Don't take it personally. Review the recommendation, revise accordingly, then resubmit.
  5. Your code may then be accepted. If so, congratulations! If not, well, you've got your peronal enhanced doas(1) you can use, and others can find your proposal in the tech@ archives. :)


All times are GMT -5. The time now is 11:17 PM.