9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@9front.org
To: 9front@googlegroups.com
Subject: Re: Installing 9front
Date: Mon, 30 Jul 2012 09:57:19 -0500	[thread overview]
Message-ID: <1c421a0da52eeb6e8ccf98b953fb5205@yourdomain.dom> (raw)
In-Reply-To: <CAK=G1TitT0nZv=oJz=d5XZeTg8Cbq7vJBStKsjk+WU6OXuff6A@mail.gmail.com>

> 4) Yes, there is disk size advice in the Wiki Install page, but why
> should I look at the wiki? Anyway the install page is HUGE and is full
> of useless screendumps from the installer. Most of the useful bits of
> info from that page should just be incorporated into the installer
> itself (which anyway already prints too much useless shit, like
> endless streams of "config:").

The endless stream of "config:" is just output from the cwfs console
as it returns to the prompt ("config:") after each command is performed.
Perhaps the output could be run through sed or awk to remove things
we don't want to print on the screen.

The purpose of the wiki page is to demonstrate a typical install
and explain what each step of the process is doing. This is intended
to provide some insight for new users into how each necessary piece
of the system is configured. I agree, the portions that cover the installer
itself are too sparse in some places. If the installer were a bit clearer in
some places we could probably do without such an elaborate walkthrough.

I decided to include the complete text of the install because I couldn't
determine a good way to cut things out without potentially confusing
the reader. Which lines, specifically, should be removed? Keep in mind
that the purpose of the document is to walk through the install step-
by-step, providing some idea of what is happening. Also keep in mind
that edits are always welcome. Especially since you are coming to this
cold and can see gaps in the documentation we've all been taking as
givens.

The original wiki page had a bullet point list with six items that
essentially just said "insert the cd-rom and boot it and follow the
prompts." The complaints about that page were that it was too
short and didn't say enough.

-sl

  reply	other threads:[~2012-07-30 14:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 11:09 Uriel
2012-07-30 14:57 ` sl [this message]
2012-07-30 18:30   ` Uriel
2012-07-30 20:45     ` sl
2012-07-31 11:59     ` Ethan Grammatikidis
2012-07-31 12:51       ` Steven Ruckdashel
2012-07-30 16:22 ` Matthew Veety
2012-07-30 18:32   ` Uriel
2012-07-30 19:32   ` Julius Schmidt
2012-07-30 23:09     ` Matthew Veety
2012-07-30 23:14       ` Julius Schmidt
2012-07-30 23:57         ` Matthew Veety
2012-07-31 11:48   ` Ethan Grammatikidis
2012-07-31 11:46 ` Ethan Grammatikidis

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=1c421a0da52eeb6e8ccf98b953fb5205@yourdomain.dom \
    --to=sl@9front.org \
    --cc=9front@googlegroups.com \
    /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).