9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] RFC: add a downloads.md page
Date: Thu, 20 Aug 2020 04:14:56 +0200	[thread overview]
Message-ID: <CAFSF3XPdo-EkWur2RJRLuR2gCN3rtFCnfR3ecpTm3wpRQMg0xQ@mail.gmail.com> (raw)
In-Reply-To: <E534C497-FFB7-45C8-BC0C-CAC265019A2B@stanleylieber.com>

the way it is right now it emphasizes there's something special about
our version of dd (linking to it is already too much detail).
this doesn't help explain *why* it would be possible to just dd a .iso
to a disk and have it be bootable without extra instructions.

for example somebody might wonder if they have to set their bios up in
a particular ISO on disk way.

the idea that you can just dd the ISO and there's magically already a
MBR is non-obvious but easily understandable by dropping the unique
word that explains the hack "isohybrid". most people, even the ones
who will never google this term will still be helped bec. they will at
least know there's a dedicated mechanism that makes this possible.

i hope this adds some info being phrased slightly differently and
obviously longer

On 8/20/20, Stanley Lieber <sl@stanleylieber.com> wrote:
> On August 19, 2020 7:12:59 PM EDT, hiro <23hiro@gmail.com> wrote:
>>> i don't have any problem adding the word, but this is a thin argument
>>
>>clarity is often subtle, so perhaps a thin argument should be enough.
>>otoh what's your argument to omit the mention? it's not like i went
>>into some distracting details...
>
> i don't have an argument against it, hiro. you seem to need to see it
> mentioned, and i have no reason to refuse you. but this was framed as if
> omitting it was a problem, so i was asking why it was a problem. i'm trying
> to follow your chain of logic so i understand it clearly. so far, we have:
> "it's subtle." my point was that i doubt the information is critical. we
> already say it works. if it doesn't work, knowing the magic word isn't going
> to make it work. i've typed a long paragraph here to answer your question as
> comprehensively as i can.
>
> i think we should also still provide a fuller explanation in the fqa section
> about bootable media.
>
> sl
>


  reply	other threads:[~2020-08-20  2:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 20:27 hiro
2020-08-18 22:20 ` [9front] " ori
2020-08-18 22:50 ` Stanley Lieber
2020-08-18 23:08   ` Stanley Lieber
2020-08-18 23:34 ` Stanley Lieber
2020-08-18 23:40   ` Kurt H Maier
2020-08-19  3:52     ` sl
     [not found]     ` <158A09494BC07582889006A200849F02@ewsd.inri.net>
2020-08-19 12:20       ` hiro
2020-08-19 13:20         ` Stanley Lieber
2020-08-19 13:25           ` hiro
2020-08-19 13:37             ` Stanley Lieber
2020-08-19 13:53               ` hiro
2020-08-19 20:01                 ` hiro
2020-08-19 21:59                   ` Stanley Lieber
2020-08-20  2:14                 ` sl
     [not found]                 ` <54754B562FB01625084E1BA75A9A12C3@ewsd.inri.net>
2020-08-20  2:18                   ` hiro
2020-08-20  2:24                     ` hiro
2020-08-20  2:30                       ` hiro
2020-08-20  2:46                         ` ori
2020-08-19 23:12               ` hiro
2020-08-19 23:40                 ` Stanley Lieber
2020-08-20  2:14                   ` hiro [this message]
2020-08-21 17:24                     ` Ethan Gardener
2020-08-22 12:59                       ` hiro
2020-08-22 15:34                         ` Stanley Lieber
2020-08-19 12:15   ` hiro
2020-08-19 12:49     ` telephil9
2020-08-19 13:02       ` hiro
2020-08-19 13:06         ` 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=CAFSF3XPdo-EkWur2RJRLuR2gCN3rtFCnfR3ecpTm3wpRQMg0xQ@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \
    /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).