9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] request for more GSoC project suggestions
Date: Wed, 25 Mar 2009 21:54:47 -0400	[thread overview]
Message-ID: <9ab217670903251854y6e95406bl70c4ebb83301d16e@mail.gmail.com> (raw)
In-Reply-To: <32d987d50903251709o5c7d4785m6d2702f2cecbcf3@mail.gmail.com>

2009/3/25 Federico G. Benavento <benavento@gmail.com>:
[snip]
> As for applications for Plan 9, the ones we need (read to cope with
> the rest of the world) are too big for a soc project, so even if I don't
> like gcc, a port would help on this matter.

Yes and no. As long as there are reasonable expectations for the
projects, there is no reason an application or application suite
cannot be duplicated or ported. GSoC isn't entirely about completing a
project: the scope of a project may just be laying groundwork or a
foundation for a later project which involves the porting. I think a
lot of your sentiment about the GSoC program is a bit short sighted
(based on emails in 2 threads now).

> right now, one can get by running old linux binaries and linuxemu+
> equis, so improving linuxemu is also a project I'm interested.
>
> just my opinion

Linux emulation can always use work everywhere, especially since those
assholes keep changing it every chance they get. More syscalls for
more glibc versions = good. FreeBSD's linux compat works great these
days (so it may not be a half bad place to start looking for
improvements, though, admittedly, I haven't used linuxemu on Plan 9)

--dho



  reply	other threads:[~2009-03-26  1:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 15:16 Charles Forsyth
2009-03-25 15:06 ` Devon H. O'Dell
2009-03-26  5:19   ` lucio
2009-03-26 13:18     ` Devon H. O'Dell
2009-03-26 15:03       ` lucio
2009-03-26 15:17         ` lucio
2009-03-25 19:57 ` Paul Lalonde
2009-03-25 20:12   ` Devon H. O'Dell
2009-03-25 20:19     ` erik quanstrom
2009-03-25 20:28       ` Devon H. O'Dell
2009-03-25 20:38       ` Chris Brannon
2009-03-26  0:47         ` erik quanstrom
2009-03-26  1:10           ` Chris Brannon
2009-03-26  2:02             ` Roman Shaposhnik
2009-03-25 20:39     ` Paul Lalonde
2009-03-25 21:12       ` Charles Forsyth
2009-03-26  1:11         ` Roman V. Shaposhnik
2009-03-26  1:51         ` Paul Lalonde
2009-03-26  2:01           ` Roman Shaposhnik
2009-03-26  2:01           ` Devon H. O'Dell
2009-03-25 20:40   ` James Tomaschke
2009-03-25 22:48     ` Paul Lalonde
2009-03-25 23:20       ` Devon H. O'Dell
2009-03-25 23:26         ` erik quanstrom
2009-03-26  2:03           ` Devon H. O'Dell
2009-03-26  4:43             ` erik quanstrom
2009-03-26  2:05           ` Roman Shaposhnik
2009-03-26 14:21           ` Joel C. Salomon
2009-03-26 15:09             ` Juan M. Mendez
2009-03-26 15:18               ` Devon H. O'Dell
2009-03-26 16:23         ` [9fans] LLVM & Exceptions (Was re. request for more GSoC project suggestions) Joel C. Salomon
2009-03-26  0:09 ` [9fans] request for more GSoC project suggestions Federico G. Benavento
2009-03-26  1:54   ` Devon H. O'Dell [this message]
2009-03-26 10:41     ` Charles Forsyth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ab217670903251854y6e95406bl70c4ebb83301d16e@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).