[9fans] Update APE

[9fans] Update APE

[Charlie Lin]

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]

Since the POSIX standard is updated to POSIX.1-2008 with the 2016 TC, the
commands should be updated as well.

Also, how to submit either a patch or a contribution?

[-- Attachment #2: Type: text/html, Size: 209 bytes --]

Re: [9fans] Update APE

[Jens Staal]

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

If someone could backport apex from Harvey, that would be cool.

Den 20 feb. 2017 19:50 skrev "Charlie Lin" <charlielin65@gmail.com>:

> Since the POSIX standard is updated to POSIX.1-2008 with the 2016 TC, the
> commands should be updated as well.
>
> Also, how to submit either a patch or a contribution?
>

[-- Attachment #2: Type: text/html, Size: 628 bytes --]

Re: [9fans] Update APE

[Steve Simon]

sadly there doesn't seem to be a way to add users to the labs sources server,
unless somone knows different.

I think the best thing would be to post diffs to this mailing list.

I have some small changes to APE I have been meaning to post, nothing substantial
mut enough to make porting some tools easier.

-Steve

Re: [9fans] Update APE

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

David du Colombier has kept up a comprehensive list of patches at 9legacy (
https://www.9legacy.org/patch.html); it's the best place to start.

Although patches can still be submitted to Labs' sources, the last time any
kernels in that repository were updated was in 2014. Fortunately there are
other maintained distributions[*]
I'm not sure how patches made in one distribution make their way into other
distributions.

I don't know how long this form of patches against Labs' frozen version
would be possible.  As patches pile on, a set of deltas need to be kept
going back to the Labs' sources.  It begs the question of how do we
organize a community maintained repository?

[*] list of Plan 9 distro's I'm aware of:
9legacy distro: maintained by David du Colombier
9front distro: kept up by ɔᴉuɐd lǝuɹǝʞ and 9 people's front people
9atom distro: kept up by Erik Quanstrom
9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib area
on Labs' sources



On Mon, Feb 20, 2017 at 4:47 PM Steve Simon <steve@quintile.net> wrote:

> sadly there doesn't seem to be a way to add users to the labs sources
> server,
> unless somone knows different.
>
> I think the best thing would be to post diffs to this mailing list.
>
> I have some small changes to APE I have been meaning to post, nothing
> substantial
> mut enough to make porting some tools easier.
>
> -Steve
>
>

[-- Attachment #2: Type: text/html, Size: 2360 bytes --]

Re: [9fans] Update APE

[Lyndon Nerenberg]

> On Feb 20, 2017, at 6:59 PM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> 
> 9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib area on Labs' sources

We really need to make sure the Labs' public fileserver is getting mirrored someplace.  I doubt it will be very long before it vanishes altogether.  (I'm surprised it's still around, in fact.)

Re: [9fans] Update APE

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

9p.io mirrors sources.

On Mon, Feb 20, 2017, 7:54 PM Lyndon Nerenberg <lyndon@orthanc.ca> wrote:

>
> > On Feb 20, 2017, at 6:59 PM, Skip Tavakkolian <
> skip.tavakkolian@gmail.com> wrote:
> >
> > 9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib
> area on Labs' sources
>
> We really need to make sure the Labs' public fileserver is getting
> mirrored someplace.  I doubt it will be very long before it vanishes
> altogether.  (I'm surprised it's still around, in fact.)
>
>
>

[-- Attachment #2: Type: text/html, Size: 1046 bytes --]

Re: [9fans] Update APE

[Kurt H Maier]

On Tue, Feb 21, 2017 at 02:59:27AM +0000, Skip Tavakkolian wrote:
>
> It begs the question of how do we organize a community maintained
> repository?

There isn't "a" community, so it's pretty pointless.  The list you
posted is the complete list of stuff that matters with the possible
exception of Forsyth's 9k repository [1], which doesn't appear to have
got much updating recently.  The point is, there's not that much to keep
track of, and anyone who cares will not have a terrible time keeping up.

The only time this has failed me was when a 9legacy patch written
specifically for Go took us by surprise (we got users mentioning a
release candidate wouldn't build).  I whined on Go's issue tracker and
they promised to mention such breaking changes in the release notes.[2]

In short, the people who give a shit about revision control are already
using it, the SP9SSS isn't going to start using it in public, and trying
to get everyone under one tent isn't going to work because git hipsters
literally suffer from organ failure when you ask them to try mercurial,
even though there isn't a (public) git port for Plan 9.

What it boils down to is two classes of makework:  watch the commit logs
for 9k[1] and 9front[3], and write a script that automates pulling
9legacy's patch list or 9atom's image and diffing them for you.  Both
9k and 9front have facilities for having commit logs mailed to you, if
you'd prefer.  They both also support rss/atom feeds.

khm





[1] https://bitbucket.org/forsyth/plan9-9k

[2] Instead we got instructions to read the Go wiki, which documents
required Plan 9 changes and when some were put in, but not which
particular Bavarian fire drill affects which particular release of Go.
But this is a Go problem, not a failure of the Plan 9 world.  And the
wiki is better than nothing.

[3] http://code.9front.org/hg/plan9front/

Re: [9fans] Update APE

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 278 bytes --]

On 21 February 2017 at 04:12, Kurt H Maier <khm@sciops.net> wrote:

> with the possible
> exception of Forsyth's 9k repository [1], which doesn't appear to have
> got much updating recently.
>

Yes, I've been busy with things other than Plan 9 to try to make ends meet.

[-- Attachment #2: Type: text/html, Size: 631 bytes --]

Re: [9fans] Update APE

[Kurt H Maier]

On Tue, Feb 21, 2017 at 08:38:58AM +0000, Charles Forsyth wrote:
> On 21 February 2017 at 04:12, Kurt H Maier <khm@sciops.net> wrote:
>
> > with the possible
> > exception of Forsyth's 9k repository [1], which doesn't appear to have
> > got much updating recently.
> >
>
> Yes, I've been busy with things other than Plan 9 to try to make ends meet.

Sorry if I wasn't clear; my intention was to highlight the fact that the
repo is worth looking at, despite the current trend of dismissing any
project as 'dead' whose last commit was greater than fifteen minutes
ago.

khm

Re: [9fans] Update APE

[cigar562hfsp952fans]

Jens Staal <staal1978@gmail.com> writes:

> If someone could backport apex from Harvey, that would be cool.

I've seen this "Harvey" thing mentioned here and there, but does it
really exist?  I tried subscribing to the "Harvey" mailing list, but my
subscription request was rejected.  So I just assumed it was a secret,
dark project hidden to all but a select inner circle of digital ninjas.

Re: [9fans] Update APE

[Jadon Bennett]

On Tue, Feb 21, 2017 at 10:20:32PM +0000, cigar562hfsp952fans@icebubble.org wrote:
> Jens Staal <staal1978@gmail.com> writes:
>
> > If someone could backport apex from Harvey, that would be cool.
>
> I've seen this "Harvey" thing mentioned here and there, but does it
> really exist?  I tried subscribing to the "Harvey" mailing list, but my
> subscription request was rejected.  So I just assumed it was a secret,
> dark project hidden to all but a select inner circle of digital ninjas.
>

https://duckduckgo.com/?q=plan+9+harvey
Welcome to the select inner circle!

Re: [9fans] Update APE

[Jens Staal]

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]

https://github.com/Harvey-OS/apex



Den 21 feb. 2017 23:28 skrev <cigar562hfsp952fans@icebubble.org>:

> Jens Staal <staal1978@gmail.com> writes:
>
> > If someone could backport apex from Harvey, that would be cool.
>
> I've seen this "Harvey" thing mentioned here and there, but does it
> really exist?  I tried subscribing to the "Harvey" mailing list, but my
> subscription request was rejected.  So I just assumed it was a secret,
> dark project hidden to all but a select inner circle of digital ninjas.
>
>

[-- Attachment #2: Type: text/html, Size: 1002 bytes --]

Re: [9fans] Update APE

[Dave MacFarlane]

Doesn't being a secret, dark hidden project imply existence?

On Tue, Feb 21, 2017 at 5:20 PM,  <cigar562hfsp952fans@icebubble.org> wrote:
> Jens Staal <staal1978@gmail.com> writes:
>
>> If someone could backport apex from Harvey, that would be cool.
>
> I've seen this "Harvey" thing mentioned here and there, but does it
> really exist?  I tried subscribing to the "Harvey" mailing list, but my
> subscription request was rejected.  So I just assumed it was a secret,
> dark project hidden to all but a select inner circle of digital ninjas.
>



--
- Dave

Re: [9fans] Update APE

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

SP9SSS is the dark matter of open source communities; there is no direct
evidence of it but, on balance, there has to be something there.


On Wed, Feb 22, 2017 at 9:28 AM Dave MacFarlane <driusan@gmail.com> wrote:

> Doesn't being a secret, dark hidden project imply existence?
>
> On Tue, Feb 21, 2017 at 5:20 PM,  <cigar562hfsp952fans@icebubble.org>
> wrote:
> > Jens Staal <staal1978@gmail.com> writes:
> >
> >> If someone could backport apex from Harvey, that would be cool.
> >
> > I've seen this "Harvey" thing mentioned here and there, but does it
> > really exist?  I tried subscribing to the "Harvey" mailing list, but my
> > subscription request was rejected.  So I just assumed it was a secret,
> > dark project hidden to all but a select inner circle of digital ninjas.
> >
>
>
>
> --
> - Dave
>
>

[-- Attachment #2: Type: text/html, Size: 1680 bytes --]

Re: [9fans] Update APE

[michaelian ennis]

[-- Attachment #1: Type: text/plain, Size: 505 bytes --]

I think the work that Erik Quanstrom did in on APE at is built in to 9
Atom. I attempted to put this up as a pull request to 0intro/plan9 but
nothing became of it.[1] Erik did this at least in part because an update
was needed for the 2.7 Python and Mercurial work that Jeff Sickle did for
Plan9 in 2013.[2]   They talked about the work at the 8th International
Workshop on Plan 9. [3]

Ian

[1] https://github.com/0intro/plan9/pull/1
[2] https://bitbucket.org/jas/cpython
[3] http://iwp9.org

[-- Attachment #2: Type: text/html, Size: 762 bytes --]