9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Re: mainly just spelling and typos
Date: Mon, 01 Nov 2021 22:24:54 +0000	[thread overview]
Message-ID: <A925E412-E305-4856-95EE-84741FF285DF@stanleylieber.com> (raw)
In-Reply-To: <CABB-WO-2P5-2Y3bK5Hpo5z2jyd0OyRPx4UqODEbJDuLt8rJ1hA@mail.gmail.com>

On November 1, 2021 8:55:12 PM UTC, Stuart Morrow <morrow.stuart@gmail.com> wrote:
>Some that have nothing to do with /dist/plan9front.
>The fqa ones are self-explanatory, the wiki one is
>so that fshalt will hit all cwfs's, which couldn't hurt.
>
>
>--- migrating-cwfs.md
>+++ /mnt/acme/4/body
>@@ -114,7 +114,7 @@
> ## Bring up new FS
>
> 	cpu% bind -a '#S' /dev
>-	cpu% cwfs64x -n newcwfs -f /dev/sdD0/fscache -C -c
>+	cpu% cwfs64x -n cwfsnew -f /dev/sdD0/fscache -C -c
> 	config: service cwfs
> 	config: config /dev/sdD0/fscache
> 	config: filsys main c(/dev/sdD0/fscache)(/dev/sdD0/fsworm)
>@@ -130,8 +130,8 @@
>
> You can now mount the new filesystem:
>
>-	cpu% mount /srv/newcwfs /n/newroot
>-	cpu% mount /srv/newcwfs /n/newdump dump
>+	cpu% mount /srv/cwfsnew /n/newroot
>+	cpu% mount /srv/cwfsnew /n/newdump dump
> 	cpu%
>
> ## Copy 9fat and nvram
>
>
>--- fqa.ms
>+++ /mnt/acme/4/body
>@@ -277,7 +277,7 @@
> .ihtml a
>
> .ihtml a <a href="fqa1.html#1.11.1.2">
>-1.11.1.2 - Mercurial repository
>+1.11.1.2 - Git repository
> .ihtml a
>
> .ihtml h1 <h1>
>--- fqa1.ms
>+++ /mnt/acme/10/body
>@@ -1391,7 +1391,7 @@
> .ihtml ul <ul>
> .IP
> .ihtml a <a href="http://git.9front.org/plan9front/plan9front">
>-https://code.9front.org/hg/plan9front (official)
>+https://git.9front.org/plan9front/plan9front (official)
> .ihtml a
> .LP
> .ihtml ul
>--- fqa3.ms
>+++ /mnt/acme/11/body
>@@ -2783,7 +2783,7 @@
>
> Multiboot can be used to start the 9front kernel directly, skipping
>the bootloader step:
> .P1
>--qemu -kernel 9pc -initrd plan9.ini
>+qemu -kernel 9pc -initrd plan9.ini
> .P2
>
> .html - <a name="3.3.1.4" />
>

applied to fqa, thanks.

sl

  parent reply	other threads:[~2021-11-01 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 20:49 [9front] " Stuart Morrow
2021-11-01 20:55 ` [9front] " Stuart Morrow
2021-11-01 22:03   ` qwx
2021-11-01 22:24   ` Stanley Lieber [this message]
2021-11-01 21:54 ` [9front] " qwx
2021-11-02 20:15   ` Stuart Morrow
2021-11-02 20:39     ` qwx
2021-11-03 22:03     ` qwx

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=A925E412-E305-4856-95EE-84741FF285DF@stanleylieber.com \
    --to=sl@stanleylieber.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).