[9fans] vmware?

[9fans] vmware?

[Anssi Porttikivi]

I can not find a Plan 9 disk image for vmware. Is there? Or do I have
to make my own? But I think I can not do that with the free vmware
palyer?

Re: [9fans] vmware?

[Lluís Batlle i Rossell]

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

Anssi Porttikivi wrote:
> I can not find a Plan 9 disk image for vmware. Is there? Or do I have
> to make my own? But I think I can not do that with the free vmware
> palyer?
> 
I think Vmware Server got free - maybe it helps, although I have not
tried it.

Plan9 runs quite well on qemu/linux, btw.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]

Re: [9fans] vmware?

[Richard Bilson]

On 8/4/06, Lluís Batlle i Rossell <viriketo@gmail.com> wrote:
> Anssi Porttikivi wrote:
> > I can not find a Plan 9 disk image for vmware. Is there? Or do I have
> > to make my own? But I think I can not do that with the free vmware
> > palyer?
> >
> I think Vmware Server got free - maybe it helps, although I have not
> tried it.

I have installed Plan 9 on VMware server and it works fine except for
the graphics. That didn't bother me, but might affect other people's
decisions.

The graphics seem almost correct, but certain things don't get drawn,
which results in it being unusable.

Re: [9fans] vmware?

[erik quanstrom]

which certian things don't get drawn correctly?

- erik

On Fri Aug  4 10:27:30 CDT 2006, rcbilson@gmail.com wrote:
> On 8/4/06, Lluís Batlle i Rossell <viriketo@gmail.com> wrote:
> > Anssi Porttikivi wrote:
> > > I can not find a Plan 9 disk image for vmware. Is there? Or do I have
> > > to make my own? But I think I can not do that with the free vmware
> > > palyer?
> > >
> > I think Vmware Server got free - maybe it helps, although I have not
> > tried it.
> 
> I have installed Plan 9 on VMware server and it works fine except for
> the graphics. That didn't bother me, but might affect other people's
> decisions.
> 
> The graphics seem almost correct, but certain things don't get drawn,
> which results in it being unusable.

Re: [9fans] vmware?

[Richard Bilson]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On 8/4/06, erik quanstrom <quanstro@quanstro.net> wrote:
> which certian things don't get drawn correctly?

See attached, which shows the screen for a cd boot off of a recent
(July) cd, accepting the default options (xga@640x480x8).

If I draw a window over top, I don't see the frame as I'm drawing or
when I'm done, but I do see the window contents. Also, stats doesn't
render properly initially but it updates properly.

If I specify monitor=vesa the virtual machine crashes.

Richard

[-- Attachment #2: 9vmserver.png --]
[-- Type: image/png, Size: 42829 bytes --]

Re: [9fans] vmware?

[Federico Benavento]

Hola,

I posted this last week think...

echo hwaccel off > /dev/vgactl

Federico G. Benavento

On 8/7/06, Richard Bilson <rcbilson@gmail.com> wrote:
> On 8/4/06, erik quanstrom <quanstro@quanstro.net> wrote:
> > which certian things don't get drawn correctly?
>
> See attached, which shows the screen for a cd boot off of a recent
> (July) cd, accepting the default options (xga@640x480x8).
>
> If I draw a window over top, I don't see the frame as I'm drawing or
> when I'm done, but I do see the window contents. Also, stats doesn't
> render properly initially but it updates properly.
>
> If I specify monitor=vesa the virtual machine crashes.
>
> Richard
>
>
>


-- 
Federico G. Benavento

Re: [9fans] vmware?

[Gorka guardiola]

I dont know if it is the same problem, but VMware in linux fullscreen had
graphic problems. It had to do with having a software cursor, so things
didn't get redrawn properly below where the cursor had passed. My
solution was not to use VMWare in full screen. I don't know if you are
having the same problem. This was
a long time ago. Then I started using VMware under windows.
Nowadays I use qemu with kqemu.

On 8/4/06, Richard Bilson <rcbilson@gmail.com> wrote:
> On 8/4/06, Lluís Batlle i Rossell <viriketo@gmail.com> wrote:
> > Anssi Porttikivi wrote:
> > > I can not find a Plan 9 disk image for vmware. Is there? Or do I have
> > > to make my own? But I think I can not do that with the free vmware
> > > palyer?
> > >
> > I think Vmware Server got free - maybe it helps, although I have not
> > tried it.
>
> I have installed Plan 9 on VMware server and it works fine except for
> the graphics. That didn't bother me, but might affect other people's
> decisions.
>
> The graphics seem almost correct, but certain things don't get drawn,
> which results in it being unusable.
>


-- 
- curiosity sKilled the cat

[9fans] Environment variable

[arisawa]

Hello 9fans,

I found something weird about environment variable.

term% a=alice
term% b=$a
term% xd -c /env/a
0000000   a  l  i  c  e 00
0000006
term% xd -c /env/b
0000000   a  l  i  c  e 00
0000006
term%

OK. /env/a is same as /env/b as it should be.

term% a=''		# null string is assigned to a
term% b=$a
term% xd -c /env/a
0000000  00
0000001
term% xd -c /env/b
0000000  00
0000001
term%

This is also OK.


term% b=`{cat /env/a}
term% xd -c /env/b
0000000
0000000
term% b=`{echo $a}
term% xd -c /env/b
0000000
0000000
term% b=`{echo ''}	# echo null string
term% xd -c /env/b
0000000
0000000
term%

??? /env/b is empty ! not same as /env/a

term% xd -c $a
xd: can't open
term%

OK I have not a file of $a

term% xd -c $b

xd is waiting a data from stdin!

Bug or specification?

Kenji Arisawa

Re: [9fans] Environment variable

[Martin Neubauer]

Hello,

I don't think that this really is weird. My understanding is that
the terminating '\0' is not treated as part of the content of a
string but merely of its representation in memory. So if you output
a null string, you don't actually output anything (and therefore
assign nothing to $b). That then explains why xd fails to open $a
(which is an actual string, albeit with length zero) and waits for
standard input because $b isn't expanded to anything.

I hope my attempt at an explanation wasn't utter nonsense and helped
clarifying a bit.

Regards,
   Martin

Re: [9fans] Environment variable

[arisawa]

Thanks Martin,

Then, how to bring up an environment variable a to a shell variable b?
command
b=`{cat /env/a}
does not work all the time.

On 2006/08/09, at 20:03, Martin Neubauer wrote:

> Hello,
>
> I don't think that this really is weird. My understanding is that
> the terminating '\0' is not treated as part of the content of a
> string but merely of its representation in memory. So if you output
> a null string, you don't actually output anything (and therefore
> assign nothing to $b). That then explains why xd fails to open $a
> (which is an actual string, albeit with length zero) and waits for
> standard input because $b isn't expanded to anything.
>
> I hope my attempt at an explanation wasn't utter nonsense and helped
> clarifying a bit.
>
> Regards,
>    Martin

Re: [9fans] Environment variable

[Martin Neubauer]

* arisawa@ar.aichi-u.ac.jp (arisawa@ar.aichi-u.ac.jp) wrote:
> Thanks Martin,
> 
> Then, how to bring up an environment variable a to a shell variable b?
> command
> b=`{cat /env/a}
> does not work all the time.
> 

Hello,

I haven't tried, but
b=`{ifs='' cat /env/a}
might do the Right Thing.

Re: [9fans] Environment variable

[arisawa]

Not for me.

On 2006/08/09, at 20:27, Martin Neubauer wrote:
>
> I haven't tried, but
> b=`{ifs='' cat /env/a}
> might do the Right Thing.

Re: [9fans] Environment variable

[Martin Neubauer]

* Martin Neubauer (m.ne@gmx.net) wrote:
> * arisawa@ar.aichi-u.ac.jp (arisawa@ar.aichi-u.ac.jp) wrote:
> > Thanks Martin,
> > 
> > Then, how to bring up an environment variable a to a shell variable b?
> > command
> > b=`{cat /env/a}
> > does not work all the time.
> > 
> 
> Hello,
> 
> I haven't tried, but
> b=`{ifs='' cat /env/a}
> might do the Right Thing.
Well, now I have tried. It doesn't do the trick.
b=`{cat /env/a}^''
gives a warning if a is an empty string but works otherwise.
b=$`{basename /env/a}
is the cleanest solution, I think.

Re: [9fans] Environment variable

[arisawa]

On 2006/08/09, at 20:39, Martin Neubauer wrote:
> Well, now I have tried. It doesn't do the trick.
> b=`{cat /env/a}^''
> gives a warning if a is an empty string but works otherwise.
> b=$`{basename /env/a}
> is the cleanest solution, I think.

The solution is same as
b=$a
this works if a is already a shell variable.

Try
c=''	# null string
a=()
b=()
cp /env/c /env/a
then exec
b=$`{basename /env/a}

Re: [9fans] Environment variable

[Martin Neubauer]

* arisawa@ar.aichi-u.ac.jp (arisawa@ar.aichi-u.ac.jp) wrote:
> 
> On 2006/08/09, at 20:39, Martin Neubauer wrote:
> >Well, now I have tried. It doesn't do the trick.
> >b=`{cat /env/a}^''
> >gives a warning if a is an empty string but works otherwise.
> >b=$`{basename /env/a}
> >is the cleanest solution, I think.
> 
> The solution is same as
> b=$a
> this works if a is already a shell variable.
> 
> Try
> c=''	# null string
> a=()
> b=()
> cp /env/c /env/a
> then exec
> b=$`{basename /env/a}

I see what you are trying to accomplish. Probably
b=$"`{cat /env/a}
will do.

Re: [9fans] Environment variable

[Martin Neubauer]

* Martin Neubauer (m.ne@gmx.net) wrote:
> * arisawa@ar.aichi-u.ac.jp (arisawa@ar.aichi-u.ac.jp) wrote:
> > 
> > On 2006/08/09, at 20:39, Martin Neubauer wrote:
> > >Well, now I have tried. It doesn't do the trick.
> > >b=`{cat /env/a}^''
> > >gives a warning if a is an empty string but works otherwise.
> > >b=$`{basename /env/a}
> > >is the cleanest solution, I think.
> > 
> > The solution is same as
> > b=$a
> > this works if a is already a shell variable.
> > 
> > Try
> > c=''	# null string
> > a=()
> > b=()
> > cp /env/c /env/a
> > then exec
> > b=$`{basename /env/a}
> 
> I see what you are trying to accomplish. Probably
> b=$"`{cat /env/a}
> will do.

And iterating a bit further, I found this doesn't work with out a
temp:
tmp=`{cat /env/a}
b=$"tmp

Re: [9fans] Environment variable

[arisawa]

* Martin Neubauer (m.ne@gmx.net) wrote:

>>
>> I see what you are trying to accomplish. Probably
>> b=$"`{cat /env/a}
>> will do.
>>
>
> And iterating a bit further, I found this doesn't work with out a
> temp:
> tmp=`{cat /env/a}
> b=$"tmp
>

term% a=()
term% xd -c /env/c
0000000   a  l  i  c  e 00
0000006
term% c=''		# null string
term% cp /env/c /env/a
term% xd -c /env/a
0000000  00
0000001
term% b=$`{cat /env/a}
rc: variable name not singleton!
term% b=$"`{cat /env/a}
rc: variable name not singleton!
term%
term%
term% t=`{cat /env/a}
term% xd -c /env/t
0000000
0000000
term% b=$t
term% xd -c /env/t
0000000
0000000
term% b=$"t
term% xd -c /env/t
0000000
0000000
term%

NG!

Re: [9fans] Environment variable

[arisawa]

On 2006/08/09, at 21:58, arisawa@ar.aichi-u.ac.jp wrote:

> * Martin Neubauer (m.ne@gmx.net) wrote:
>
>>>
>>> I see what you are trying to accomplish. Probably
>>> b=$"`{cat /env/a}
>>> will do.
>>>
>>
>> And iterating a bit further, I found this doesn't work with out a
>> temp:
>> tmp=`{cat /env/a}
>> b=$"tmp
>>
>
> term% a=()
> term% xd -c /env/c
> 0000000   a  l  i  c  e 00
> 0000006
> term% c=''		# null string
> term% cp /env/c /env/a
> term% xd -c /env/a
> 0000000  00
> 0000001
> term% b=$`{cat /env/a}
> rc: variable name not singleton!
> term% b=$"`{cat /env/a}
> rc: variable name not singleton!
> term%
> term%
> term% t=`{cat /env/a}
> term% xd -c /env/t
> 0000000
> 0000000
> term% b=$t
> term% xd -c /env/t
> 0000000
> 0000000
> term% b=$"t
> term% xd -c /env/t
> 0000000
> 0000000
> term%
>
> NG!
>
>

Oh! That works!
It is so hot tonight that I did incorrect experiment.
Sorry!

Re: [9fans] Environment variable

[Martin Neubauer]

I was more thinking about this:
term% a=()
term% c=''
term% cp /env/c /env/a
term% xd -c /env/a
0000000  00
0000001 
term% t=`{cat /env/a}
term% xd -c /env/t
0000000 
0000000 
term% b=$"t
term% xd -c /env/b
0000000  00
0000001 
term%

Re: [9fans] Environment variable

[erik quanstrom]

this doesn't do what you think it does.  the second line excerpted tries
to set b to the value of the variable named the empty list!

the first one who figures out what that means can meet me on the other
side of this möbius strip.

- erik

On Wed Aug  9 08:08:22 CDT 2006, arisawa@ar.aichi-u.ac.jp wrote:
> term% a=()
[...]
> term% b=$`{cat /env/a}
[...]
> NG!
> 
> 

[9fans] editor, man/less, dns setup, screen setup

[bituman]

Ahoi all.. well my computer had seen plan9 a few times before : )
Now i just got a new laptop. I could finally install plan9 after a few
smaller probs.
The machine is a gericom laptop.. i know... with a geforce GO video
card, plus a TFT capable of 1024x768x32bit
prob#1: i cant seem to make GUI work. its that simple.
prob#2: prob#1 wouldnt be a big problem, i love console : ), but there's
no more and less commands, and i cant scroll console. how can this be
done? can't seem to find in the wiki
prob#3: is there a simple text editor like nano or vi available for
plan9? im sure i will love plan9's ed but becouse of prob#2 i cant even
really read its man page...
and i am not in the mood to execute man ed | sed 10q, then man ed | sed
20q and so on... just to read it
and i do need the editor, becouse i have set 195.56.77.141 as my default
domain name server.
thanks for your help in advance guys : )

Re: [9fans] editor, man/less, dns setup, screen setup

[Martin Neubauer]

* bituman (bituman@enerla.net) wrote:
> Ahoi all.. well my computer had seen plan9 a few times before : )
> Now i just got a new laptop. I could finally install plan9 after a few
> smaller probs.
> The machine is a gericom laptop.. i know... with a geforce GO video
> card, plus a TFT capable of 1024x768x32bit
> prob#1: i cant seem to make GUI work. its that simple.
> prob#2: prob#1 wouldnt be a big problem, i love console : ), but there's
> no more and less commands, and i cant scroll console. how can this be
> done? can't seem to find in the wiki
> prob#3: is there a simple text editor like nano or vi available for
> plan9? im sure i will love plan9's ed but becouse of prob#2 i cant even
> really read its man page...
> and i am not in the mood to execute man ed | sed 10q, then man ed | sed
> 20q and so on... just to read it
> and i do need the editor, becouse i have set 195.56.77.141 as my default
> domain name server.
> thanks for your help in advance guys : )

Hello,

I think you need p(1).

Oh, and its manpage fits on a screenful.

Re: [9fans] editor, man/less, dns setup, screen setup

[Robert Raschke]

> prob#2: prob#1 wouldnt be a big problem, i love console : ), but there's
> no more and less commands, and i cant scroll console. how can this be
> done? can't seem to find in the wiki

man ed |p

-robby

Re: [9fans] editor, man/less, dns setup, screen setup

[Rodolfo (kix)]

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

prob#1: i cant seem to make GUI work. its that simple.

do you make the installation in text mode?

I don't know if this card is supported, but if rio starts in the
installation, probably is supported. Try to change the monitor and/or the
vgasize in /n/9/plan9.ini (you must run "9fat:" first).

slds.

2006/8/9, Robert Raschke <rrplan9@tombob.com>:
>
> > prob#2: prob#1 wouldnt be a big problem, i love console : ), but there's
> > no more and less commands, and i cant scroll console. how can this be
> > done? can't seem to find in the wiki
>
> man ed |p
>
> -robby
>
>


-- 
Rodolfo García "kix"

[-- Attachment #2: Type: text/html, Size: 923 bytes --]

Re: [9fans] Environment variable

[erik quanstrom]

the "problem" is backquoting.  you can see this clearly by distilling
your example:

	; a = ''
	; b = `{cat /env/a}
	; whatis b
	b: not found
	; ls -l /env/^(a b)
	--rw-rw-rw- e 0 quanstro quanstro 1 Jul  6 19:33 /env/a
	--rw-rw-rw- e 0 quanstro quanstro 0 Jul  6 19:33 /env/b

since backquoting always treats '\0' as an ifs character

	; x = `{echo -n ''}

is the same as

	; x = ()

that is, 
	; ls -l /env/x
	--rw-rw-rw- e 0 quanstro quanstro 0 Jul  6 19:33 /env/x

the only asymmetric thing to me is the fact that

	; x = ()

sets /env/x, yet $x throws an error.  (byron's rc does the opposite.)

- erik

On Wed Aug  9 05:01:18 CDT 2006, arisawa@ar.aichi-u.ac.jp wrote:
> 
> term% b=`{cat /env/a}
> term% xd -c /env/b
> 0000000
> 0000000
> term% b=`{echo $a}
> term% xd -c /env/b
> 0000000
> 0000000
> term% b=`{echo ''}	# echo null string
> term% xd -c /env/b
> 0000000
> 0000000
> term%
> 
> ??? /env/b is empty ! not same as /env/a