On Fri, Jun 6, 2014 at 9:05 PM, erik quanstrom <quans...@quanstro.net> wrote: > On Fri Jun 6 11:26:13 EDT 2014, ba...@bitblocks.com wrote: >> >> > On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan <vu3...@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.
What is the recommended way keep a 9atom system up to date? -- Ramakrishnan
