Some of these programs are just really thin wrappers around system calls.
I don't see how they would benefit from being rewritten in go.
Goblin was a fun way to learn go, not a project to be useful.
However i would be happy to see some new programs written in go.
For example we lack a picture mani
Hello again,
Wow i wrote this post a little while before falling asleep and
certainly didn't expect such a torrent of replies O.o
@ Aram Hăvărneanu :
Thanks for the interest! some of the tools you mentioned are already
implemented in Goblin, but i could always take a second look at them
see whet
Patching p -> scond = q -> scond in /sys/src/cmd/5l/noop.c fixes this
unfortunate linker bug.
On Sunday, April 28, 2013 10:54:18 PM UTC-7, Paul Patience wrote:
> Mischief reported a crash with on arm with
>
> winwatch when closing all windows excluding those
>
> ignored through the -e flag. Cin
> Gesendet: Montag, 29. April 2013 um 21:34 Uhr
> Von: "Richard Miller" <9f...@hamnavoe.com>
> An: 9fans@9fans.net
> Betreff: Re: [9fans] 5l bug
>
> > following up, theres my naive fix for this. instead of
> > emiting conditional division instruction by 5c... dont and
> > keep the branch. does t
i is not ovious to me why that would work without adding a conditiona branch.
maybe my assumptions are wrong. can you show the resulting assembly for the
testcase?
> Gesendet: Dienstag, 30. April 2013 um 11:07 Uhr
> Von: zephyr.pelle...@gmail.com
> An: 9fans@9fans.net
> Betreff: Re: [9fans] 5l bug
> The bad stuff for Plan9 would be the external dependencies of libtecla
> and ncurses (still have not been able to get ncurses to work :( ), so
> there would have to be lots of modifications probably.
if thine libraries offend thee, pluck them out
command line editing is not necessary, and
Hi,
Am 2013-04-28 23:07, schrieb Bakul Shah:
On 28 Apr 2013 22:01:17 +0200 "Holger Sebert"
wrote:
I did a quick hack on kbd.c and could make the "<,>,|" key
work. Awesome! Thank you all for your help.
What was the fix?
The relevant section from kbd.c is
if(kbscan->esc1){
Hi,
Am 2013-04-28 23:14, schrieb Richard Miller:
#include "../omap/random.c"
which should be
#include "../port/random.c"
Although it was easy to fix, I wonder where this inconsistency
in the source tree came from. Did I miss an update or something?
I think you did. /sys/src/9/bcm/random.c
>> I think you did. /sys/src/9/bcm/random.c should have been deleted.
>
> Should this have happened when I invoked 'pull'? Or is there a
> separate update mechanism?
Yes, it should have been deleted by the first 'pull' after 1 April:
term% grep sys/src/9/bcm/random.c /dist/replica/client/plan9.
> I don't see how they would benefit from being rewritten in go.
Go versions of base Plan 9 tools would be very useful to me for a
number of reasons. Unfortunately, none of them have to do anything
with Plan 9 (but then almost nothing posted on 9fans does) and
probably my reasons don't apply to ma
> with Plan 9 (but then almost nothing posted on 9fans does) and
nominated for the the geekier-than-thou meme of the week.
- erik
On Tue, Apr 30, 2013 at 11:31:48AM -0400, erik quanstrom wrote:
> > with Plan 9 (but then almost nothing posted on 9fans does) and
>
> nominated for the the geekier-than-thou meme of the week.
>
> - erik
>
I thought 9fans was a raspberry pi support list.
khm
I wasn't talking about rc(1). I was talking about echo, tee, cat, touch,
rm, sleep, etc..
2013/4/30 Aram Hăvărneanu
>
> Sometimes I need to deploy something written in rc(1) over a
> heterogenous Linux cluster, and a statically compiled rc(1) would be a
> blessing.
On Tue, Apr 30, 2013 at 05:26:50PM +0200, Aram H?v?rneanu wrote:
> > I don't see how they would benefit from being rewritten in go.
>
> Sometimes I need to deploy something written in rc(1) over a
> heterogenous Linux cluster,
This is in part Plan9 related. For kerTeX, simply because my compilat
Subject Sheevaplug and NVRAM
Every time I start the Sheevaplug, I have to enter the authentication
details that ought to be written to VNRAM. This seems unnecessary,
but my attempts to assign a single block of flash to NVRAM have so far
been unsuccessful.
Could somebody mail me an example of a s
On Tue Apr 30 11:57:34 EDT 2013, lu...@proxima.alt.za wrote:
> Subject Sheevaplug and NVRAM
>
> Every time I start the Sheevaplug, I have to enter the authentication
> details that ought to be written to VNRAM. This seems unnecessary,
> but my attempts to assign a single block of flash to NVRAM h
> Could somebody mail me an example of a successful allocation of flash
> memory for Plan 9 use on a Sheevaplug so I can figure out what I am
> doing wrong?
In you case, you may simply include the nvram in your kernel by
adding the "nvram" file to the bootdir section of your kernel
configuration a
If anyone is interested I have (re)ported rc(1) to linux
together with the few tools that are unique to plan9: p(1)
mc(1) and ls(1).
ls may seem a strange choice but I access Linux over ssh
from plan9 and want to be able to do things like "ls ../port" and
get the files listed with the ../port/ pat
LinkedIn
Fans,
I'd like to add you to my professional network on LinkedIn.
- Aram
Aram Sadogidis
Intern Software Engineer at Bell Laboratories
Ireland
Confirm that you know Aram Sadogidis:
https://www.linkedin.com/e/-b7ebtr-hg5hrqq5-2/isd/12884874408/ZlUc7Ynw/?hs=false&tok=2Kd01
I don't know if you've seen this,
but there is also a plan9portport
to windows [1]. Not everything
works, but sam and rc do.
[1] https://bitbucket.org/knieriem/pf9
I realise I have misrepresented this work, the Linux port of rc(1)
was Geoff Collyer's work, both the earlier port some years ago and
a recent update which makes the port work again. I provided a minor
patch or two.
There has been a win32.c in the labs distribution of rc(1) for years
but it has ne
> rc in go
Also, some extensions could be useful:
* Inferno shell style local variables with := statement
* <> $file { ... } statement
* <>{ ... } statement, which returns both input and output pipes of command
> * Inferno shell style local variables with := statement
already have. syntax is:
var=val cmd
> * <> $file { ... } statement
already have.
> * <>{ ... } statement, which returns both input and output pipes of command
? pipes aren't first-class language elements.
- erik
> syntax is: var=val cmd
Sure, foo=() bar=() baz=() { ... } works, but that's not very practical.
> ? pipes aren't first-class language elements.
Well, they are files:
; foo=>{cat} ; echo $foo
/dev/fd/6
(linux)
I'm talking about something, that returns list with input and output
fd to a com
On Tue Apr 30 18:50:42 EDT 2013, gleb.ax...@gmail.com wrote:
> > syntax is: var=val cmd
> Sure, foo=() bar=() baz=() { ... } works, but that's not very practical.
i don't see the practical issue. the idiom described works fine.
not liking the syntax is not a good reason to introduce incompatable
this is a follow up to the discussion about root from usb-hdd
on the raspberry pi discussion (http://9fans.net/archive/2013/03/499)
it's a roundabout trip.
on pcs, i'm using cinap's bios-only loader. it's tiny, and does its job well.
i've added the ability to find bios's first drive and pxe's fir
With := you can define locale variable where you need it.
That's like pascal style (where you define all variables before the
code) versus c style (where you define variables with code).
Not critical, but there is a practical issue.
2013/5/1 erik quanstrom :
> On Tue Apr 30 18:50:42 EDT 2013, gle
Just a nit, but the Algol style of assignment, "becomes" if you will, didn't
define the variable instance. It was just an assignment.
sent from my ipad
On Apr 30, 2013, at 4:45 PM, "suharik" wrote:
> With := you can define locale variable where you need it.
> That's like pascal style (where
On Tue Apr 30 19:45:29 EDT 2013, gleb.ax...@gmail.com wrote:
> With := you can define locale variable where you need it.
> That's like pascal style (where you define all variables before the
> code) versus c style (where you define variables with code).
> Not critical, but there is a practical issu
it turns out, a few updates have gone in recently.
they might be worth noting (even if you're not using 9atom)
a number of bug fixes that have gone in recently.
i was surprised reviewing the changes how many
crashes were fixed.
http://www.quanstro.net/plan9/9atom/index.html
- erik
On Apr 30, 2013, at 20:56, erik quanstrom wrote:
> On Tue Apr 30 19:45:29 EDT 2013, gleb.ax...@gmail.com wrote:
>> With := you can define locale variable where you need it.
>> That's like pascal style (where you define all variables before the
>> code) versus c style (where you define variables
> However, if you don't want to spread your passwords over
> your network, you would prefer to use the flash, simply
> by adding, for example, the following to your /cfg/*/cpurc:
>
> echo add nvram 0x10 0x12 >'#'F/flashctl
That's too late for wrkey.
There's a lot about the Sheeva that do
On Tue, Apr 30, 2013 at 07:18:16PM +0100, Steve Simon wrote:
>[...]
> I have also ported rc(1) and a base set of command line tools to
> win32. rc(1) builds standalone but some of the tools need libregexp
> libbio and libstring which included
>
Well, I'm definitively interested since I'd like to
33 matches
Mail list logo
