On Mon, 31 Jan 2005 10:41:35 -0800, Ben Huntsman <BHuntsman@...> wrote: > printing? 'man 2 print' is enlightening, though I've never messed with it. There's also an inferno device for 'gs' on Plan 9, which I *suspect* converts PostScript to the Inferno bitmap format (which could also be fun), but don't quote me on that. -Jack
I've been poking around with this mk bug. Here's some more to the puzzle. When I bind bufio.dis from a remote plan9 machine mk works. But if I copy the same bufio.dis to the local Linux machine, mk hangs. Very strange. Also, a bug from the 20041217 release % mk yacc.dis limbo -I/module -gw yacc.b fatal limbo compiler error: can't ecom const (0) int 48 97 mk: limbo -I/module -gw yacc.b : exit status=8356 "Sh":fail:error yacc.b will complie fine using native limbo compiler. -caerwyn
On Thu, 27 Jan 2005 15:46:17 -0800, Ben Huntsman <BHuntsman@...> wrote: > There's been an awful lot of people bailing on the list lately... everyone else still interested, or is Inferno dying out, especially in the face of plan9port, which is cross-platform, too? > I use inferno instead of plan9port. It was around the time plan9port was first coming out that I was trying to switch to inferno instead of my own port of plan9 tools. I was getting fed up with writing C code and having trouble porting it to every machine I used. I just couldn't maintain a consistent environment using C tools. So when plan9port came out I was a little torn, but decided to go with inferno anyway because of the VM, the promise of consistency everywhere and deep support for 9p, not the shallow support in plan9port. I don't deliver to my customer any applications based on inferno. I use it as an IDE, for integrating the various systems I need to manage, for writing my own tools to support what I do. This is how I would have used plan9port too. I'm a big fan of inferno. I think more people should consider Inferno as a replacement for plan9port.
A quick fix for the compiler inlining bug (limbo -gw yacc.b) :-
add the line
sumark(elem);
at the beginning of the function arraydefault() in /appl/cmd/limbo/ecom.b so
that it looks like
arraydefault(a, elem: ref Node)
{
e: ref Node;
if(debug['A'])
print("arraydefault: %s %s\n", nodeconv(a), nodeconv(elem));
sumark(elem);
t := mkn(Olen, a, nil);
.....
Ditto for the C version in /limbo/ecom.c which exhibits the same problem but
happens to compile yacc.b correctly by chance.
john firth
jrf@...
I hope the list won't find this too commercial ! I'm looking for a post-doc to work with me at Indiana University in the area of embedded software. One current project is the use of Inferno/Plan 9 type file systems in deeply embedded environments, e.g. file servers at the chip level to manage SoC resources. The official advertisement is at: http://www.cs.indiana.edu/Contacts/employment/ Geoffrey Brown geobrown@...
Hello,
Has anyone got the installer to work in panther (mac os x). When i
follow the instructions i get:
megabitch:/Volumes/Inferno20040830/MacOSX/power/bin inferno$ sh
/Volumes/Inferno20040830/install/MacOSX-power.sh /Users/inferno/inferno
/Volumes/Inferno20040830/install/MacOSX-power.sh: line 41: 2317
Illegal instruction "$CDPATH/$BIN/emu" -c1 -G -r "$CDPATH"
/dis/install/install.dis -r "$INSTALLDIR" -p $PLATFORM
Clues/Hints anyone??
Thanks
Robin Darby...
When Inferno starts, depending on if you're running emu or native, the VM executes osinit.dis or emuinit.dis. Is there any way to cause either to launch a shell script, such that once the initialization is done, the shell script executes, and upon its completion, turns final control over to the user? (or is this already done, and I'm just not aware?) Thanks! -Ben
On Fri, 11 Feb 2005 16:33:48 -0800, Ben Huntsman <BHuntsman@...> wrote: > When Inferno starts, depending on if you're running emu or native, the VM executes osinit.dis or emuinit.dis. > > Is there any way to cause either to launch a shell script, such that once the initialization is done, the shell script executes, and upon its completion, turns final control over to the user? (or is this already done, and I'm just not aware?) > > Thanks! > -Ben > from man emu: emu [ -gXsizexYsize ] [ -c[0-9] ] [ -d daemon ] [ -m[0-9] ] [-s] [ -ppool=maxsize ] [ -ffont ] [ -rrootpath ] [-7] [ -C channel ] [ -S ] [ -v ] [ cmd [ arg ... ] ] If you run emu, you can run any dis binary with an arbitrary set of parameters from the "command line", if I understand correctly. If you run inferno natively, I don't understand "turns final control over to the user".
RSS Feed4 | |
|---|---|
24 | |
22 | |
14 | |
9 | |
10 | |
4 | |
23 | |
15 | |
1 | |
4 | |
23 | |
8 | |
2 | |
1 | |
43 | |
38 | |
12 | |
24 | |
5 | |
1 | |
2 | |
23 | |
23 | |
27 | |
13 | |
6 | |
56 | |
14 | |
13 | |
5 | |
16 | |
17 | |
15 | |
22 | |
21 | |
36 | |
24 | |
50 | |
43 | |
43 | |
55 | |
72 | |
38 | |
65 | |
73 | |
36 | |
51 | |
41 | |
116 | |
20 | |
38 | |
15 | |
36 | |
59 | |
32 | |
29 | |
55 | |
78 | |
57 | |
54 | |
48 | |
49 | |
109 | |
63 | |
104 | |
213 | |
74 | |
85 | |
36 | |
62 | |
48 | |
85 | |
308 | |
151 | |
72 | |
30 | |
8 | |
72 | |
57 | |
72 | |
37 | |
19 | |
42 | |
63 | |
141 | |
63 | |
70 | |
119 | |
98 | |
19 | |
122 | |
58 | |
19 | |
66 | |
51 | |
133 | |
38 | |
59 | |
46 | |
21 | |
30 | |
72 | |
36 | |
73 | |
60 | |
140 | |
165 | |
180 |
