[9fans] newbie question - keeping up to date

[9fans] newbie question - keeping up to date

[Tim Newsham]

Hi,  I'm using the plan9 vmware image.  Following the wiki
I do the following to keep up to date:

      disk/kfscmd allow
      replica/pull -v /dist/replica/network >[2] up.txt

after reviewing up.txt and removing any conflicting files (its
a clean dist so I figure updating everything is best) and repeating
I get a complete update.

At this point I reboot and login again and I notice a few things
no longer work properly:

   - up/down keys in rc windows.  Instead of paging up and down
     within the window they now just output some odd character.
   - menus in rc windows - never pop up.
   - status window - the status window (which is started by default
     for the glenda account) suicides.

What's going wrong here?  Are there additional update steps I
need to perform?

(Thankfully this is vmware and I can just revert the changes).

Tim N.

Re: [9fans] newbie question - keeping up to date

[andrey mirtchovski]

>    - up/down keys in rc windows.  Instead of paging up and down
>      within the window they now just output some odd character.

that should be fixed after a kernel recompile.

>    - menus in rc windows - never pop up.

never seen that before...

>    - status window - the status window (which is started by default
>      for the glenda account) suicides.

which status window?  /usr/glenda/bin/rc/riostart starts them all so
try and see which one particularly fails.  if it's 'stats' try
executing the command itself and see if it'll still crash...

which conflicting files did you have when you pulled?

andrey

Re: [9fans] newbie question - keeping up to date

[Tim Newsham]

> >    - status window - the status window (which is started by default
> >      for the glenda account) suicides.
>
> which status window?  /usr/glenda/bin/rc/riostart starts them all so
> try and see which one particularly fails.  if it's 'stats' try
> executing the command itself and see if it'll still crash...

The strip-scrolling system status (cpu load, etc..) utility.
Sounds like something that could benefit from a kernel rebuild.

> which conflicting files did you have when you pulled?

it said that the /386/lib and /386/lib/acme files were locally
built and that it wouldnt replace them.  I manually deleted
them and repeated the update.  There were a few other files
as well (some .8 files and one or two .c and .h files).

Let me try again and rebuild a kernel this time.

> andrey

Tim N.

Re: [9fans] newbie question - keeping up to date

[andrey mirtchovski]

i forgot to mention -- you can just copy the kernel from /386.  run
'9fat:' and see what's in /n/9fat (plan9.ini and a kernel are there)
and copy the same kernel from /386, it should have all updates.

as far as i can see on my system all kernels in /386 contain the
vmware graphics device so you ought to be safe :)

>> which conflicting files did you have when you pulled?
>
> it said that the /386/lib and /386/lib/acme files were locally
> built and that it wouldnt replace them.  I manually deleted
> them and repeated the update.  There were a few other files
> as well (some .8 files and one or two .c and .h files).
>
> Let me try again and rebuild a kernel this time.
>

next time do 'replica/pull -vs', which will overwrite conflicting
files with the ones from sources and save you the trouble of having to
delete them by hand.  just make sure you don't overwrite important
configuration files like /rc/bin/{cpu,term}rc or /lib/ndb/local which
you may have modified for your system (until you've set up venti, or
fossil snapshots at the very least:)

Re: [9fans] newbie question - keeping up to date

[Tim Newsham]

> i forgot to mention -- you can just copy the kernel from /386.  run
> '9fat:' and see what's in /n/9fat (plan9.ini and a kernel are there)
> and copy the same kernel from /386, it should have all updates.

Thank you.  This resolved all of my problems and had the added
bonus of supporting mousing out of the vmware window.  Nice.

Tim N.