> I downloaded a fresh 9atom iso and installed under virtual box again.
> After the installation (I got an error while the copydist was ~80%,
> which again I forgot to note down) when I booted up the new
> installation, it hangs after printing:
posting this error might be helpful.
- erik
On Sat, Jun 7, 2014 at 1:24 PM, Ramakrishnan Muthukrishnan
wrote:
> it hangs after printing:
> ...
> init: starting /bin/rc
Probably a problem with timesync(8), disable it in your cpurc/termrc.
--
Aram Hăvărneanu
My vm installation does not boot anymore with the new kernel (I forgot
to note down the error, but probably it is not worth reporting because
I messed up the system beyond repair).
I downloaded a fresh 9atom iso and installed under virtual box again.
After the installation (I got an error while th
> What two databases?
the divergent versions of /sys/lib/dist/replica/plan9.db and its log
on the sources and 9atom.
> Replica respects local changes at the file level. You still
> have to do a manual merge if the server version changed as
> well.
that's what i said, but this is remove vs remot
On Fri, 06 Jun 2014 11:35:08 EDT erik quanstrom wrote:
> On Fri Jun 6 11:26:13 EDT 2014, ba...@bitblocks.com wrote:
> >
> > > On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan
> wrote:
> > >
> > > Hi,
> > >
> > > I just saw a suicide message on 9atom running on plan9 while updating
> >
On Fri, Jun 6, 2014 at 9:56 PM, erik quanstrom wrote:
> On Fri Jun 6 12:08:28 EDT 2014, vu3...@gmail.com wrote:
>> On Fri, Jun 6, 2014 at 9:25 PM, erik quanstrom wrote:
>> >> I thought that replica/pull on a 9atom would pull 9atom binaries and
>> >> not the labs version. Looks like that assumpti
On Fri Jun 6 12:08:28 EDT 2014, vu3...@gmail.com wrote:
> On Fri, Jun 6, 2014 at 9:25 PM, erik quanstrom wrote:
> >> I thought that replica/pull on a 9atom would pull 9atom binaries and
> >> not the labs version. Looks like that assumption is wrong?
> >
> > only on .iso versions of 9atom several
On Fri, Jun 6, 2014 at 9:25 PM, erik quanstrom wrote:
>> I thought that replica/pull on a 9atom would pull 9atom binaries and
>> not the labs version. Looks like that assumption is wrong?
>
> only on .iso versions of 9atom several years old. to correct this issue,
> you'd have to sync /usr/glenda
> I thought that replica/pull on a 9atom would pull 9atom binaries and
> not the labs version. Looks like that assumption is wrong?
only on .iso versions of 9atom several years old. to correct this issue,
you'd have to sync /usr/glenda/bin/rc/pull first.
- erik
On Fri, Jun 6, 2014 at 8:54 PM, Bakul Shah wrote:
>
>> On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan
>> 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 ru
> > 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?
running pull as user glenda, same
On Fri, Jun 6, 2014 at 9:05 PM, erik quanstrom wrote:
> On Fri Jun 6 11:26:13 EDT 2014, ba...@bitblocks.com wrote:
>>
>> > On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan
>> > wrote:
>> >
>> > Hi,
>> >
>> > I just saw a suicide message on 9atom running on plan9 while updating
>> > the sy
On Fri Jun 6 11:26:13 EDT 2014, ba...@bitblocks.com wrote:
>
> > On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan
> > wrote:
> >
> > Hi,
> >
> > I just saw a suicide message on 9atom running on plan9 while updating
> > the system:
> >
> > % replica/pull -v /dist/replica/network
>
> I
> On Jun 5, 2014, at 8:15 PM, Ramakrishnan Muthukrishnan
> 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
Hi,
On Fri, Jun 6, 2014 at 1:30 PM, Bakul Shah wrote:
> On Fri, 06 Jun 2014 13:02:14 +0530 Ramakrishnan Muthukrishnan
> wrote:
>> On Fri, Jun 6, 2014 at 11:30 AM, Bakul Shah wrote:
>> > On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan > .com> wrote:
>> >> Well, looks like I cannot
On Fri, 06 Jun 2014 13:02:14 +0530 Ramakrishnan Muthukrishnan
wrote:
> On Fri, Jun 6, 2014 at 11:30 AM, Bakul Shah wrote:
> > On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan .com> wrote:
> >> Well, looks like I cannot run any binaries anymore and getting the
> >> suicide message!
On Fri, Jun 6, 2014 at 11:30 AM, Bakul Shah wrote:
> On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan
> wrote:
>> Well, looks like I cannot run any binaries anymore and getting the
>> suicide message! I don't have anything critical on this vm image and
>> can re-install it. But I wa
On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan
wrote:
> Well, looks like I cannot run any binaries anymore and getting the
> suicide message! I don't have anything critical on this vm image and
> can re-install it. But I want to see if I can recover it and how. I
> will re-read the
Well, looks like I cannot run any binaries anymore and getting the
suicide message! I don't have anything critical on this vm image and
can re-install it. But I want to see if I can recover it and how. I
will re-read the "syscall 53" thread to look for any solutions.
Ramakrishnan
On Fri, Jun 6,
On Fri, Jun 6, 2014 at 8:51 AM, erik quanstrom wrote:
> On Thu Jun 5 23:17:37 EDT 2014, 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
>>
>> After a while, I saw this printed,
On Thu Jun 5 23:17:37 EDT 2014, 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
>
> After a while, I saw this printed, but the replica/pull is proceeding
> without any problem.
>
>
Hi,
I just saw a suicide message on 9atom running on plan9 while updating
the system:
% replica/pull -v /dist/replica/network
After a while, I saw this printed, but the replica/pull is proceeding
without any problem.
(not completely readable because stats window overwrote the screen)
... bad sy
22 matches
Mail list logo
