[9fans] a litle note on my dead vmware system

[9fans] a litle note on my dead vmware system

[ron minnich]

looks like it's fossil (which is why I did the rebuild ...)

After rebuilding the universe, rebuild pcf, reboot, once fossil starts,
nothing can be found on the file system (/adm/timzeon/etc, /bin/rc, ...)

The older pcf kernel is fine; it's newer kernels using newer fossil that
die.

Anybody seen this?

To complicate the picture, I've seen none of this probelm on non-vmware
systems. I'd just as soon restart from a clean vmware image that has
fossil if such exists.

thanks


ron

Re: [9fans] a litle note on my dead vmware system

[vic zandy]

> Anybody seen this?

I just updated a vmware machine, and tested a new pcf and fossil.
Works fine.

> I'd just as soon restart from a clean vmware image that has
> fossil if such exists.

Clean vmware images are easy to make by normal installation.  I seem
to do it for one reason or another once a week.  It seems slow if you
stay to watch the fossil get loaded, but otherwise it's painless.

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Tue, 18 May 2004, vic zandy wrote:

> > Anybody seen this?
>
> I just updated a vmware machine, and tested a new pcf and fossil.
> Works fine.

dang it. I loaded from the install cd into vmware, tried using fossil, and
it suicided. Did the same with kfs, no problem.

OK, another thing to try to figure out :-)

Vic, is your vmware windows or linux?

ron

Re: [9fans] a litle note on my dead vmware system

[vic zandy]

> Vic, is your vmware windows or linux?

windows, version 4.0.5.

i just did a fresh fossil install from the cd image and it worked fine.

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Wed, 19 May 2004, vic zandy wrote:

> windows, version 4.0.5.
>
> i just did a fresh fossil install from the cd image and it worked fine.

arg. OK, I'll drop another 512M in my linux box and try again with fossil.

ron

Re: [9fans] a litle note on my dead vmware system

[Ishwar Rattan]

I am trying to install in VMware-4.0.5 (Windoz XP host) using
the bootable plan 9 CD.

The process gets stuck at
..
distribution disk [no default]: /dev/sdD0/data
9660srv 1707: serving /srv/9660
mouny: mount /n/distmedia: I/O read error
distribution disk [no default]:
..

CD is configured with 'Legacy mode on'.

Any ideas?
-ishwar


On Tue, 18 May 2004, vic zandy wrote:

> > Anybody seen this?
>
> I just updated a vmware machine, and tested a new pcf and fossil.
> Works fine.
>
> > I'd just as soon restart from a clean vmware image that has
> > fossil if such exists.
>
> Clean vmware images are easy to make by normal installation.  I seem
> to do it for one reason or another once a week.  It seems slow if you
> stay to watch the fossil get loaded, but otherwise it's painless.
>

Re: [9fans] a litle note on my dead vmware system

[vic zandy]

> CD is configured with 'Legacy mode on'.

that means you are using a physical cd, right?
have you tried using the iso image?

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Wed, 19 May 2004, Ishwar Rattan wrote:

> I am trying to install in VMware-4.0.5 (Windoz XP host) using
> the bootable plan 9 CD.
>
> The process gets stuck at
> ..
> distribution disk [no default]: /dev/sdD0/data
> 9660srv 1707: serving /srv/9660
> mouny: mount /n/distmedia: I/O read error
> distribution disk [no default]:

on vmware 4.0.5, my cd was sdC1, not sdD0

ron

Re: [9fans] a litle note on my dead vmware system

[Ishwar Rattan]

I reported a problem with installation of plan9 using the
physical cdrom under vmware-4.0 workstation. I was suggested
that I connect cdrom to plan9.iso file.

Now it does not boot at all, it gets stuck at boot from:
prompt.

Is one supposed to boot using a floppy image and cdrom connected to
plan9.iso file?

-ishwar

On Tue, 18 May 2004, vic zandy wrote:

> > Anybody seen this?
>
> I just updated a vmware machine, and tested a new pcf and fossil.
> Works fine.
>
> > I'd just as soon restart from a clean vmware image that has
> > fossil if such exists.
>
> Clean vmware images are easy to make by normal installation.  I seem
> to do it for one reason or another once a week.  It seems slow if you
> stay to watch the fossil get loaded, but otherwise it's painless.
>

Re: [9fans] a litle note on my dead vmware system

[Russ Cox]

> Is one supposed to boot using a floppy image and cdrom connected to
> plan9.iso file?

You can do it with just the CD-ROM.
Connect the CD-ROM as IDE1:0 to make your life easiest.
I just did this a few days ago, I'm pretty sure it works.

Russ

Re: [9fans] a litle note on my dead vmware system

[Ishwar Rattan]

With CD-ROM connected as IDE1:0, I got stuck at
..
Distribution disk [no default]: /dev/sdD0/data
9660srv 1707: serving /srv/9660
mount: mount /n/distmedia: I/O read error
Distribution disk [no default]
..
the install process did list /dev/sdD0/data as 9660 iso image too??

-ishwar


On Wed, 19 May 2004, Russ Cox wrote:

> > Is one supposed to boot using a floppy image and cdrom connected to
> > plan9.iso file?
>
> You can do it with just the CD-ROM.
> Connect the CD-ROM as IDE1:0 to make your life easiest.
> I just did this a few days ago, I'm pretty sure it works.
>
> Russ
>

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Wed, 19 May 2004, Ishwar Rattan wrote:

> With CD-ROM connected as IDE1:0, I got stuck at
> ..
> Distribution disk [no default]: /dev/sdD0/data
> 9660srv 1707: serving /srv/9660
> mount: mount /n/distmedia: I/O read error
> Distribution disk [no default]
> ..
> the install process did list /dev/sdD0/data as 9660 iso image too??

sorry if you said it, is this linux or windows vmware?

ron

Re: [9fans] a litle note on my dead vmware system

[Russ Cox]

I've been using Linux VMware 4.5 recently with no problems.

Re: [9fans] a litle note on my dead vmware system

[Ishwar Rattan]

Winodz-Xp is the host.

-ishwar


On Wed, 19 May 2004, ron minnich wrote:

> On Wed, 19 May 2004, Ishwar Rattan wrote:
>
> > With CD-ROM connected as IDE1:0, I got stuck at
> > ..
> > Distribution disk [no default]: /dev/sdD0/data
> > 9660srv 1707: serving /srv/9660
> > mount: mount /n/distmedia: I/O read error
> > Distribution disk [no default]
> > ..
> > the install process did list /dev/sdD0/data as 9660 iso image too??
>
> sorry if you said it, is this linux or windows vmware?
>
> ron
>

[9fans] A question on fossil-FS??

[Ishwar Rattan]

I need a little pointer to using command that modify files when
terminal is installed with fossil-FS.

echo 'srv -AWP fs.noauth' >> /srv/fscons
mount /srv/fs.noauth /n/boot

Unprotected view of FS is via /n/boot

If one wants to delete /amd/keys
  rm /n/boot/adm/keys

If one wants to create a file /sys/log/cron then how to do it
as cd /n/boot/sys/log and trying create doesn't work.

What is an easy way to do things? For example, to execute the
command

	aux/ssh_genkey

always tries as /sys/.. and results in permission denied.
Is there a way to bind /n/boot to '/' and then unbind(?) it???

-ishwar

Re: [9fans] A question on fossil-FS??

[Russ Cox]

> If one wants to create a file /sys/log/cron then how to do it
> as cd /n/boot/sys/log and trying create doesn't work.

what do you mean?  what error do you get?

    >/n/boot/sys/log/cron
    chmod +alrw /n/boot/sys/log/cron

should work just fine.

> What is an easy way to do things? For example, to execute the
> command
>
>         aux/ssh_genkey
>
> always tries as /sys/.. and results in permission denied.
> Is there a way to bind /n/boot to '/' and then unbind(?) it???

you could draw a new window, bind /n/boot /, do your work,
and then delete the window.

alternately, you could bind /n/boot/sys /sys and then unmount /sys.

the best solution is putting yourself in the sys group and
not using the /srv/fs.noauth kludge.

Re: [9fans] A question on fossil-FS??

[Ishwar Rattan]

On Mon, 24 May 2004, Russ Cox wrote:

> the best solution is putting yourself in the sys group and
> not using the /srv/fs.noauth kludge.

How do I put glenda (for example) in sys group?

-ishwar

Re: [9fans] A question on fossil-FS??

[Kenji Okamoto]

> How do I put glenda (for example) in sys group?

man fossilcons(8)

Kenji

[9fans] pla9.bell-labs.com->vmware.zip

[Ishwar Rattan]

Last try before throwing the towel in.

Context is VMware-4 workstation on Windoz-XP host.

At attempts to install plan9 failed from bootable cd, so, I want
to try Cox's prebuilt vmware.zip. It shows a number of files:
Plan9.vmx, disk-02.vmdk, disk-03.vmdk, disk-04.vmdk, disk-05.vmdk,
disk.vmdk, nvram

Which one is connected to preexisting disk to use during installation?
Using disk.vmdk (larges in size) does not produce success, boot process
hangs as:
--
MBR..PBS..Plan 9 from Bell Labs
ECLR: 0C00
apm ax=f000 cx=f000 dx=40 di=ffff ebc=5a49 esi=-1
dev A0 port 1F0 config 427A capabilities 2F00 mwdma 0007 udma 0407
dev A0 port 170 config 85C4 capabilities 0F00 mwdma 0007 udma 0407
--

_ishwar

Re: [9fans] pla9.bell-labs.com->vmware.zip

[Russ Cox]

You can just "Open Virtual Machine" and point it at Plan9.vmx.

Russ

Re: [9fans] pla9.bell-labs.com->vmware.zip

[vic zandy]

vmware cdrom devices have a "connect at power on" flag.
in my vmware, if a vm has a cdrom device with that flag
NOT set, then the vm hangs in the way ishwar describes
when i boot plan 9.  it doesn't matter if the cdrom is
physical or iso.

we'll see if we can fix that particular hang; in the
meantime, does anyone have another way to hang vmware?

Re: [9fans] pla9.bell-labs.com->vmware.zip

[boyd, rounin]

> vmware cdrom devices have a "connect at power on" flag.

iirc IDE drives have a spin up on power or a jumper to set it.

stuff like that can cause untold woe.

Re: [9fans] pla9.bell-labs.com->vmware.zip

[ron minnich]

On Fri, 21 May 2004, boyd, rounin wrote:

> iirc IDE drives have a spin up on power or a jumper to set it.

I couldn't find the virtual jumper.

And I lost my virtual soldering iron.

ron

Re: [9fans] pla9.bell-labs.com->vmware.zip

[ron minnich]

On Fri, 21 May 2004, vic zandy wrote:

> in my vmware, if a vm has a cdrom device with that flag
> NOT set, then the vm hangs in the way ishwar describes
> when i boot plan 9.  it doesn't matter if the cdrom is
> physical or iso.

yeah, bug bug bug.

> we'll see if we can fix that particular hang; in the
> meantime, does anyone have another way to hang vmware?


That IDE issue is the only one I've found that consistently cause trouble,
other than the occasional where it absolutely will not take keyboard input
(i.e. takes it in 9load but not Plan 9). That one is fixable by reboot.

Like I say, vmware 4 is less useful for Plan 9 than vmware 3.

Another problem is my vmware really badly screws up the mouse unless you
turn off the settings that let you move it out of the vmware window
without having to hit CTL-ALT. Set it up so that you MUST high ctl-alt to
get out of the vmware window to save your sanity.

ron

Re: [9fans] pla9.bell-labs.com->vmware.zip

[ron minnich]

On Fri, 21 May 2004, Ishwar Rattan wrote:

> apm ax=f000 cx=f000 dx=40 di=ffff ebc=5a49 esi=-1
> dev A0 port 1F0 config 427A capabilities 2F00 mwdma 0007 udma 0407
> dev A0 port 170 config 85C4 capabilities 0F00 mwdma 0007 udma 0407
  (this second line is secondary ide channel)


disable secondary ide channel and I bet it boots.

Worked for me.

ron

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Wed, 19 May 2004, Russ Cox wrote:

> I just did this a few days ago, I'm pretty sure it works.

one variable in here is linux vs. windows. But it has worked for me too
for the most part on linux -- just a few glitches, and occasional hard
failures in vmware 4.x

ron

Re: [9fans] a litle note on my dead vmware system

[ron minnich]

On Wed, 19 May 2004, Ishwar Rattan wrote:

> I reported a problem with installation of plan9 using the
> physical cdrom under vmware-4.0 workstation. I was suggested
> that I connect cdrom to plan9.iso file.
>
> Now it does not boot at all, it gets stuck at boot from:
> prompt.
>

the occasional problem I have had occurs when there is a second IDE
controller. Sometimes turning of the secondary IDE has helped get the
thing to boot.

Overall, vmware 4.0 seems like more glitz and eye candy and no substantive
improvement in capability, reliability, or performance over 3.0.

ron