From: Charlie Lin <charlielin65@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 5th Edition
Date: Fri, 18 Nov 2016 14:58:39 -0500 [thread overview]
Message-ID: <CAJvBL5yqpNcnQJj9mWEweJx6zHCbS7q-uP-X=g7ASzk6xsM7uA@mail.gmail.com> (raw)
In-Reply-To: <CAJvBL5xRKJdifSBY=7rEhxhfx0o+2UUVsxJghBc=BKDZs8r5FA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
My mistake for hastiness: should we implement the filesystem in kernel or
user space?
On Fri, Nov 18, 2016 at 2:57 PM, Charlie Lin <charlielin65@gmail.com> wrote:
> Like efivarfs in the Linux kernel
>
> On Fri, Nov 18, 2016 at 2:54 PM, Charlie Lin <charlielin65@gmail.com>
> wrote:
>
>> My idea: implement a user-space filesystem to expose all EFI variables.
>> As for the bootloader, any ideas?
>>
>> On Wed, Nov 16, 2016 at 7:30 PM, Kurt H Maier <khm@sciops.net> wrote:
>>
>>> On Wed, Nov 16, 2016 at 07:21:14PM -0500, Charlie Lin wrote:
>>> > Add one more: EFI support
>>> > Also, can Plan 9 be booted on Open Firmware? (Used on at least Sun
>>> SPARC
>>> > workstations)
>>> >
>>> > On Nov 16, 2016 5:27 PM, "Charlie Lin" <charlielin65@gmail.com> wrote:
>>> >
>>> > > Any plans for Plan 9 5th edition?
>>> > >
>>> > > My desires:
>>> > > ISO-compliant C compiler and preprocessor
>>> > > Port other programming languages (especially Go) to here
>>> > > Start a source code repository
>>> > > Port Git, SVN, Mercurial, et cetera to here
>>> > >
>>>
>>>
>>> These are great ideas, is there some central place you can write these
>>> down so we don't lose track of our goals
>>>
>>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2505 bytes --]
next prev parent reply other threads:[~2016-11-18 19:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:27 Charlie Lin
2016-11-16 22:43 ` Stanley Lieber
2016-11-16 22:44 ` Ole-Hjalmar Kristensen
2016-11-16 23:53 ` Chris McGee
2016-11-17 0:34 ` James A. Robinson
2016-11-17 1:14 ` Charlie Lin
2016-11-17 16:16 ` Dave MacFarlane
2016-11-17 17:50 ` Ori Bernstein
2016-11-17 20:29 ` Chris McGee
2016-11-17 20:32 ` Ori Bernstein
2016-11-17 20:31 ` Chris McGee
2016-11-17 0:21 ` Charlie Lin
2016-11-17 0:30 ` Kurt H Maier
2016-11-18 19:54 ` Charlie Lin
2016-11-18 19:57 ` Charlie Lin
2016-11-18 19:58 ` Charlie Lin [this message]
2016-11-18 22:26 ` hiro
2016-11-18 22:28 ` hiro
2016-11-19 16:57 ` cinap_lenrek
2016-11-19 18:42 ` Steve Simon
[not found] ` <CAEVxPTMKBpWFEGr-k1diNa2BVgCjsL1g-OPZdhn9LmEn3uLB5g@mail.gmail.com>
[not found] ` <CAEVxPTN_KZn_4+s1xr-uiDzEY72wf2AtrXYN_FDgdaPbyqpLbw@mail.gmail.com>
2016-11-18 20:07 ` Jules Merit
2016-11-17 0:55 ` Charlie Lin
2016-11-17 1:02 ` Stanley Lieber
2016-11-17 1:18 ` Kurt H Maier
2016-11-19 22:27 ` David Arnold
2016-11-20 2:39 ` hiro
2016-11-20 4:26 ` Ryan Gonzalez
2016-11-20 6:22 ` Kurt H Maier
2016-11-20 6:54 ` James A. Robinson
2016-11-20 9:44 ` hiro
2016-11-21 2:19 ` Wes Kussmaul
2016-11-21 8:02 ` hiro
2016-11-21 8:02 ` Kurt H Maier
2016-11-21 8:46 ` Sigrid Haflinadóttir
2016-11-21 15:08 ` Wes Kussmaul
2016-11-21 15:42 ` Chris McGee
2016-11-19 20:19 ` Charlie Lin
2016-11-19 20:37 ` Charlie Lin
2016-11-19 21:51 ` Steve Simon
2016-11-19 22:27 ` Stanley Lieber
2016-11-20 15:23 ` Chris McGee
2016-11-20 18:09 ` hiro
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='CAJvBL5yqpNcnQJj9mWEweJx6zHCbS7q-uP-X=g7ASzk6xsM7uA@mail.gmail.com' \
--to=charlielin65@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).