From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] DigiLand DL701Q quad core tablet
Date: Fri, 19 Dec 2014 09:33:27 +0000 [thread overview]
Message-ID: <86db177ccac37021891fee0ce1e0c1f9@hamnavoe.com> (raw)
In-Reply-To: <0EB3385A-BD60-47B0-B7F4-B4CE2EF3FA7F@quintile.net>
> in reality the kernel is the same modulo some drivers and one variable ( e.g. no vga in cpu servers).
It's actually quite easy to make a single binary which can be configured
at boot time to be either cpu or terminal, depending on a plan9.ini variable.
IIRC it's a few lines of code in each of boot.c and main.c.
However I can imagine a scenario in which this would be a security hole.
next prev parent reply other threads:[~2014-12-19 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 16:15 cigar562hfsp952fans
2014-11-17 14:03 ` erik quanstrom
2014-11-19 15:41 ` cigar562hfsp952fans
2014-12-18 20:06 ` cigar562hfsp952fans
2014-12-18 23:48 ` Charles Forsyth
2014-12-19 3:15 ` da Tyga
2014-12-19 7:43 ` Quintile
2014-12-19 9:33 ` Richard Miller [this message]
2014-12-19 15:14 ` Iruatã Souza
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=86db177ccac37021891fee0ce1e0c1f9@hamnavoe.com \
--to=9fans@hamnavoe.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).