9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] suicide message on vmware
Date: Fri,  6 Jun 2014 11:35:08 -0400	[thread overview]
Message-ID: <1706efdd3a7186cc1c2a54f2aba1c56e@brasstown.quanstro.net> (raw)
In-Reply-To: <EFB8A5C8-2093-4F81-AE31-09805EAECEB2@bitblocks.com>

On Fri Jun  6 11:26:13 EDT 2014, bakul@bitblocks.com wrote:
>
> > On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> wrote:
> >
> > Hi,
> >
> > I just saw a suicide message on 9atom running on plan9 while updating
> > the system:
> >
> > % replica/pull -v /dist/replica/network
>
> I missed that you were running 9atom. Using old binaries to copy the new kernel to /n/9fat and rebooting means now you're running the bell labs kernel. I don't know how different the two kernels are but if you want to continue running 9atom everything, you may have to undo nsec related changes in the userland.
>
> More generally, as this nsec change demonstrates, if you rely on sources over which you have no control & you also have local changes, you pretty much have to treat the external sources as a "vendor branch" and do a careful merge to avoid such surprises.

that's not how replica works.  replica respects local changes.  however,
since in this case two different databases were mixed up, there is little
chance that the user has a sane system.

- erik



  reply	other threads:[~2014-06-06 15:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  3:15 Ramakrishnan Muthukrishnan
2014-06-06  3:21 ` erik quanstrom
2014-06-06  4:05   ` Ramakrishnan Muthukrishnan
2014-06-06  5:18     ` Ramakrishnan Muthukrishnan
2014-06-06  6:00       ` Bakul Shah
2014-06-06  7:32         ` Ramakrishnan Muthukrishnan
2014-06-06  8:00           ` Bakul Shah
2014-06-06  8:33             ` Ramakrishnan Muthukrishnan
2014-06-06 15:24 ` Bakul Shah
2014-06-06 15:35   ` erik quanstrom [this message]
2014-06-06 15:46     ` Ramakrishnan Muthukrishnan
2014-06-06 15:50       ` erik quanstrom
2014-06-06 16:49     ` Bakul Shah
2014-06-06 16:59       ` erik quanstrom
2014-06-06 15:52   ` Ramakrishnan Muthukrishnan
2014-06-06 15:55     ` erik quanstrom
2014-06-06 16:07       ` Ramakrishnan Muthukrishnan
2014-06-06 16:26         ` erik quanstrom
2014-06-06 16:38           ` Ramakrishnan Muthukrishnan
2014-06-07 11:24           ` Ramakrishnan Muthukrishnan
2014-06-07 11:29             ` Aram Hăvărneanu
2014-06-07 14:42             ` erik quanstrom
2014-06-07 17:11               ` Ramakrishnan Muthukrishnan

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=1706efdd3a7186cc1c2a54f2aba1c56e@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).