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 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!
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
Glenda's world weary cousin
https://pbs.twimg.com/media/BpZjUjXIYAIJiua.jpg
-Steve
>I'm a Unix fan, I use BSD, Minix, Linux, and any unix-like OS I can get my
hands on.
Why?
P.S. The kernel is monolithic. Although, IIRC, there were attempts to make
it a hybrid.
2014-06-05 23:33 GMT+03:00 Yoann Padioleau :
> Nice!
>
> On Jun 4, 2014, at 8:14 PM, s...@9front.org wrote:
>
> >
>
On 06/06/2014 11:10, Steve Simon wrote:
Glenda's world weary cousin
https://pbs.twimg.com/media/BpZjUjXIYAIJiua.jpg
Maybe the nsec patch would have been refused by this guy, right?!
(not a troll, just kidding!)
Nicolas
> P.S. The kernel is monolithic. Although, IIRC, there were attempts to make
> it a hybrid.
this is far from the full story. because of the mount driver, many things
may be in the kernel or userland according to what makes sense. for
example, the ip stack has moved back and forth several times.
On Fri Jun 6 08:16:20 EDT 2014, nberc...@yahoo.fr wrote:
> On 06/06/2014 11:10, Steve Simon wrote:
> > Glenda's world weary cousin
> >
> > https://pbs.twimg.com/media/BpZjUjXIYAIJiua.jpg
>
> Maybe the nsec patch would have been refused by this guy, right?!
> (not a troll, just kidding!)
there wa
> 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
i know it's not used much, but this is very curious, and if the kernel
version is correct, the user space version needs correcting, too.
the rb kernel version starts with
TEXT_xdec(SB), $0
SYNC
why is a sync necessary? i would think, if LL/SC don't do what
they do at
> thus, while the kernel is fairly traditional, the capabilities are not.
They should be, but tradition is slow to catch on.
L.
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 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
> > 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 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
> 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 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
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: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
the /sys/src/9/ppc kernel adds this line
to both _xinc and _xdec
DCBF(R4)/* fix for 603x bug */
would this also be needed for the c library version?
- erik
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
> >
> 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, Jun 6, 2014 at 7:14 AM, Nicolas Bercher wrote:
> On 06/06/2014 11:10, Steve Simon wrote:
>>
>> Glenda's world weary cousin
>>
>> https://pbs.twimg.com/media/BpZjUjXIYAIJiua.jpg
>
>
> Maybe the nsec patch would have been refused by this guy, right?!
> (not a troll, just kidding!)
I thought
DONE, now beer.
http://code.google.com/p/plan9front/source/detail?r=2f51489d42116c85159dc1649ab82cec9a766542
--
cinap
i was kindly sent this by someone who's had success with a modern
laptop:
> Hello Erik
>
> Just tried the latest usb image and wanted to let you know it works quite
> well. I get this message, though:
>
> acpinitr: pm1sts 0x400 pm1en 0x100
>
> repeated all the time, getting a lot of context sw
>> So here is another proof that plan9 can run on recent hardware, including
>> beautiful notebooks :)
Is any more specific information available about the manufacturer and model
of the laptop?
sl
On Sat Jun 7 00:34:03 EDT 2014, s...@9front.org wrote:
> >> So here is another proof that plan9 can run on recent hardware, including
> >> beautiful notebooks :)
>
> Is any more specific information available about the manufacturer and model
> of the laptop?
>
i quote,
dell xps 15 (mode
Hi,
I was curious to know which core features of the Linux kernel are not
implemented
in the plan9 kernel. By core I mean that I know plan9 does not have all the
drivers,
filesystems, buses, etc Linux has, but it has many of its core
features (virtual memory, paging, swapping, demand loading, co
> I was curious to know which core features of the Linux kernel are not
> implemented
> in the plan9 kernel. By core I mean that I know plan9 does not have all the
> drivers,
> filesystems, buses, etc Linux has, but it has many of its core
> features (virtual memory, paging, swapping, demand load
theres a kernel file cache for cached mounts (see the -C option),
tho its broken in labs plan9.
pages of executables are cached.
the disk fileservers implement a buffer cache to avoid going to disk
and do lazy writing out dirty filesystem blocks.
plan9 is a distributed system. the disk fileserve
30 matches
Mail list logo
