9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adriano Verardo <adriano.verardo@mail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9atom usb image
Date: Thu, 27 Mar 2014 23:20:00 +0100	[thread overview]
Message-ID: <5334A410.2010201@mail.com> (raw)
In-Reply-To: <832ea38e28a7a015fa90e9ffe60bd018@brasstown.quanstro.net>

erik quanstrom ha scritto:
> thanks, i'll look into this.
>
> - erik
>
As i wrote in a previous mail,  I tried this procedure:
(pcbox is a working Atom/fossil, using the key to install on dell1).

download usbinstamd64.bz2, load the usb key
pcbox% usbsd
pcbox% disk/kfs -f /dev/sdu0/fs
pcbox% mount /srv/kfs /n/k
pcbox% du -a /n/k > /tmp/du_before
pcbox% disk/kfscmd check    # Only one kfs on pcbox
   ...
   ...   3005 free blocks
...
pcbox%

unmount the key from pcbox, use it to install dell1 ...
when the compilation stops, remove the key from dell1 and re-mount it
on pcbox

pcbox% usbsd
pcbox% disk/kfs -f /dev/sdu0/fs
pcbox% mount /srv/kfs /n/k
pcbox% du -a /n/k > /tmp/du_after
pcbox% disk/kfscmd check
   ...
   ...   0 free blocks
   ...
pcbox%
pcbox% wc /tmp/du_before /tmp/du_after
pcbox% diff /tmp/du_before /tmp/du_after

Looking at the diff output it seems that the compiled executables
are installed on the key instead of the target hdd.

This makes me think to a damned typo in a "bind" somewhere.

adriano





      parent reply	other threads:[~2014-03-27 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 17:34 erik quanstrom
2014-03-26 23:34 ` Adriano Verardo
2014-03-27  3:39   ` erik quanstrom
2014-03-27 20:49     ` David Hoskin
2014-03-27 20:54       ` erik quanstrom
2014-03-27 21:09         ` David Hoskin
2014-03-28  1:11       ` Matthew Bonner
2014-03-27 22:20     ` Adriano Verardo [this message]

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=5334A410.2010201@mail.com \
    --to=adriano.verardo@mail.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).