From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] RFC: add a downloads.md page
Date: Tue, 18 Aug 2020 15:20:33 -0700 [thread overview]
Message-ID: <D31AEB82A2465B710FBC9D24BB1C8004@eigenstate.org> (raw)
In-Reply-To: <CAFSF3XO_3U9FPMU5zePrHLS2ZdOCVd9jzV5zpurmbY+Lp0PA0w@mail.gmail.com>
> i would replace in the side-menu the downloads section and the
> sublinks mirrors,dash1, with just this single page.
>
> reasoning:
>
> 1) right now the only way to find out about isohybrid possibility is
> by reading the release notes from 2016, so i thought about what page
> this would fit on best.
> 2) no images -> faster to get to actual download link (in comparison
> to mirrors link that points to fqa)
> 3) dash1 can get directly downloaded with one click, but the iso not.
>
> alternatively could add download page link to top bar, like current code link.
Looks good, just a couple of nitpicks:
> For PC the images can be either burned to CD as normal, or dd'ed
> directly to disk (relies on the ISOHYBRID mechanism). The 386
> version supports more drivers, amd64 having less.
DD'ed to disk sounds like you just write it to the hard drive, rather
than using it as install media. It also makes it sound like the default
for a new user should be the 386 version, and I'm not sure that's true.
(Maybe it is?)
For PC the images can be either burned to CD, or dd'ed to a USB disk.
The amd64 version supports larger quantities of memory, and is the
focus of development. The 386 image has some drivers that may not
yet be supported on amd64.
I also like the release artwork -- but fine. It can go.
next prev parent reply other threads:[~2020-08-18 22:20 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 ` ori [this message]
2020-08-18 22:50 ` [9front] " 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
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=D31AEB82A2465B710FBC9D24BB1C8004@eigenstate.org \
--to=ori@eigenstate.org \
--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).