--daemon does not work with --chroot

[mcamou]

When you run stud with --daemon and --chroot, it tries to reopen stdin as /dev/null after doing the chroot, which returns an ENOENT.

[mcamou]

Add @bixu to interested parties

[rohara]

I believe this is the same issue that I patched a while back.

#118

[bixu]

@rohara Ah - good call. Looks like we are seeing an issue with MIA repo owners (looks like there has been little owner activity since 2012) - is it time for there to be a community fork of the project?

[afterfate]

I think people would love to have one, bumptech seems to be the assumed default but there are several developers working on their own forks out there. Wasn't bump bought out?

[mcamou]

Yup, they were bought out by Google some time ago. I've looked at the
bumptech/stud network graph and there are A LOT of forks. We'd need some
sort of Grand Unified Fork I guess.

-Mario.

I want to change the world but they won't give me the source code.

On Wed, Sep 10, 2014 at 3:48 PM, afterfate notifications@github.com wrote:

I think people would love to have one, bumptech seems to be the assumed
default but there are several developers working on their own forks out
there. Wasn't bump bought out?

—
Reply to this email directly or view it on GitHub
#146 (comment).

[afterfate]

I'm not quite sure what the best method would be to choose. Most recent maintained and a notice to older forks to tell them to file pull requests if they'd like to have their work included? I'm not really sure how one accomplishes that with such a large audience.

[afterfate]

The most recent maintained method isn't a good one on second examination. There's a bunch of branches that either fork from this one, or even from the one I was on, to make 1 or two changes and then stop. There's some in there that seem to be taking ownership and not just adding a feature they need, things like log overhauls, doc changes.

There be dragons here.

[mcamou]

I've seen that, most branches have one or 2 commits and then stop. The
ipredator branch seems to be the most consistently maintained (at least
with the most commits) but I haven't looked at what they are doing. Or
perhaps, as you said, just fork from the original and message all the
forkers to submit PR's. Or message bumptech and ask them to take over the
repo (assuming they are still looking at messages from their GitHub
account).

-Mario.

I want to change the world but they won't give me the source code.

On Wed, Sep 10, 2014 at 4:29 PM, afterfate notifications@github.com wrote:

The most recent maintained method isn't a good one on second examination.
There's a bunch of branches that either fork from this one, or even from
the one I was on, to make 1 or two changes and then stop. There's some in
there that seem to be taking ownership and not just adding a feature they
need, things like log overhauls, doc changes.

There be dragons here.

—
Reply to this email directly or view it on GitHub
#146 (comment).