From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Regarding GUID partitioning
Date: Sun, 21 Apr 2019 08:48:41 +0200 [thread overview]
Message-ID: <CAJQ9t7ieUU3G2JV+Vkoysuz9YY=GcZqFPq-Q6pVKwhcGuJvS9g@mail.gmail.com> (raw)
In-Reply-To: <3FA78BE442B9E14B1EF77737F0AA50F1@felloff.net>
On 4/21/19, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
> its documented in prep(8)
>
Thanks to you both, Kurt and specially Cinap. As I said, accessing
9front persistently remains on my wish list (no encouragement needed,
I just need to find the time to invest in some research).
It is good news that GPT is addressed. The hybrid option sounds like
wanting to have one's cake and eat it, I would almost certainly take a
similar approach, were I to choose.
Lucio.
next prev parent reply other threads:[~2019-04-21 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 6:25 cinap_lenrek
2019-04-21 6:48 ` Lucio De Re [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-21 5:09 Lucio De Re
2019-04-21 6:01 ` Kurt H Maier
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='CAJQ9t7ieUU3G2JV+Vkoysuz9YY=GcZqFPq-Q6pVKwhcGuJvS9g@mail.gmail.com' \
--to=lucio.dere@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).