[9fans] can acme clients (Wiki) access acme's clean/dirty status?

[9fans] can acme clients (Wiki) access acme's clean/dirty status?

[Axel Belinfante]

Right now acme Wiki maintains its own ``dirtied'' state,
in addition to the ``dirty/clean'' state that acme
already maintains.
However, the ``dirtied'' state that Wiki maintains
is much less sophisticated, for example, it is not
aware of Undo undoing edits thereby returning a file
to a ``clean'' state.

Could there be a way to make acme's clean/dirty state
available to it clients (like Wiki) such that they don't
have to maintain their own state in this regard?

Axel.

Re: [9fans] can acme clients (Wiki) access acme's clean/dirty status?

[Axel Belinfante]

To answer my own question (thanks to quick response in #9fans):
``yes, modified state is available, see acme(4)''.

Sorry for the noise,
Axel.

[9fans] accesing a local fossil

[Ezequiel Reyes]

Hi, I wanted to install plan 9 in my second partition using the option 1 of
the menu in the liveCD. It stoped trying to find a file in sdD0, so I gave
it the same path for the file but with sdC1 (my cd drive) and some questions
later it started rio and a series of programas that made easy questions and
led the instalation through without problems. The last of these programs
asked for a booting option, giving me to select from (floppy,boot from plan9
,win9x,winnt), something like that. As mine is a dual boot disk, I could not
select to start my system directly with plan 9, wich I guess would have been
the easier for the installer, so I selected first floppy, but it could not
find it, as it tried to find it on sdD0 (this time with no possibility of
providing my own path like before), then I tried winnt, but it could not
find a .ini nt file on my Windows partition. So I gave it a ctrl-d and the
next option was [finish]. I happend to have a NetBSD bootloader before so I
could still have the bootmenu and use the option NetBSD which was now
pointing to the newly installed plan 9 system, But plan 9 stoped when
reading the plan9.ini file in the installed system since it mentioned fd0 as
the booting media. Then I thought I could mount the installed system using
the liveCD system that came with the CD and from there using sam or
something edit the ini file and point it to the correct file in the new
partition (and some more info about screen res, mouse and of course, the
vesa driver in case it weren't already there). So I fired up the liveCD
option, went through the manuals and tried something like:

%fossil/fossil -f /dev/sdC0/fossil

then I listed /srv but there was no /srv/fossil entry there, so I could not
mount. Besides, I noticed a text something like rfork ### fsave, printed
somewhere over the screen (over the windows, not inside them), being ### the
id of the fork I guess. I rememberd seeing /srv/fossil during the
instalation, so I went back and started the instalation process again (as I
had noticed it used a different rio version since it have smaller fonts and
circular menus unlike the liveCD option which I think is older) just to see
if I could mount the already instaled system from there. As the instalation
started I looked for fossil in /srv and it was there, so I opened a new
window and tried:
 fossil/fossil -f /dev/sdC0/fossil again, this time I could later add mount
/srv/fossil /n/9fat and it worked ok showing me the new installed tree
there. The problem is I have no sam or acme available from the instalation
system so I could not edit anything, just browse.
Did I miss something while trying to start fossil on /dev/sdC0/fossil using
the liveCD system? Is is possible at all to perform an instalation this way?
I would like not to depend on the floppy disk every time I boot in plan 9.
Is it possible?

Re: [9fans] accesing a local fossil

[Federico Benavento]

>then I tried winnt, but it could not
> find a .ini nt file on my Windows partition.
there is not suport for ntfs partitions

> option, went through the manuals and tried something like:
> 
> %fossil/fossil -f /dev/sdC0/fossil
check where is your fossil partition
% ls /dev/sd*/fossil

> mount. Besides, I noticed a text something like rfork ### fsave, printed
it is a debug print in 9/pc/trap.c, grep for fsave.

> had noticed it used a different rio version since it have smaller fonts and
> circular menus unlike the liveCD option which I think is older) just to see
circular menus?

> there. The problem is I have no sam or acme available from the instalation
> system so I could not edit anything, just browse.
open a new window
% cat file
edit whatevet you want, snarf the hole thing
% cat > file

> Did I miss something while trying to start fossil on /dev/sdC0/fossil using
again try:
% ls /dev/sd*/fossil
to see where is your fossil partition in case you have one

> I would like not to depend on the floppy disk every time I boot in plan 9.
> Is it possible?
http://btmgr.sourceforge.net

fgb

Re: [9fans] accesing a local fossil

[Federico Benavento]

> open a new window
> % cat file
> edit whatevet you want, snarf the hole thing
> % cat > file
paste the buf and
^D
> 

fgb

Re: [9fans] accesing a local fossil

[Christoph Lohmann]

Good day.

On Mon, 15 Aug 2005 07:37:38 -0700
"Ezequiel Reyes" <ezequiel.reyes@newhotel.co.cu> wrote:

> process again (as I had noticed it used a different rio version since it
> have smaller fonts and circular menus unlike the liveCD option which I
> think is older)

That was the old 9grid.de ISO, as it used the binaries from the server. It
is now build from the binaries in the mirror and the "circular menus"[0]
should disappear, since they are not in the distribution and are only a
patch that can be applied.

Sincerely,

Christoph

[0] /n/sources/patch/saved/rio-piemenu-update

Re: [9fans] accesing a local fossil

[Ezequiel Reyes]

----- Original Message -----
From: "Federico Benavento" <benavento@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Sent: Monday, August 15, 2005 9:32 AM
Subject: Re: [9fans] accesing a local fossil

>> had noticed it used a different rio version since it have smaller fonts
and
>> circular menus unlike the liveCD option which I think is older) just to
see
> circular menus?

well, that's what I would call them anyway. In the liveCD system, rio has
normal drop down rectangular menus, while using option 1 starts a rio whose
menus are like pie slice graphic charts with every menu option in a pie. I
think the reason behind it is ergonomics, since the mouse is in the center
of the circle and only a minor move in the right direction will hilight the
correct menu entry. I just recibed a mail telling me these are menus from
and old iso image, so I think what is happening is that the vesa enabled iso
image is old compared to the current standard iso since I am using the
former. Well, in tha case I can only hope vesa becomes part of the standard
iso soon :)

>> %fossil/fossil -f /dev/sdC0/fossil
>check where is your fossil partition
>% ls /dev/sd*/fossil

I did that, my installed fossil went to /dev/sdC0/fossil, I seem to remember
the installer tells it in an auxiliar console while performing install
operations. I even removed the CD just to be sure I could still browse sdC0
without it, besides, only 386 from the arch especific folders was there. In
my system, the CD showed in sdC1 and when I try to boot from hard drive the
message right before stopping tells sdC0 as well.

> open a new window
> % cat file
> edit whatevet you want, snarf the hole thing
> % cat > file
paste the buf and

Yes. I can do that, but I was just curious on why I could not start fossil
on /dev/sdC0/fossil using the liveCD demo but could start it and get the
need /srv/fossil using the install system. Any ideas? I am new to plan 9,
but for what I've read, all I needed was the command: fossil/fossil -f
/dev/sdC0. Is it a problem with the liveCD option or a bad procedure of
mine?

Re: [9fans] accesing a local fossil

[Steve Simon]

Hi,

> %fossil/fossil -f /dev/sdC0/fossil
> 
> then I listed /srv but there was no /srv/fossil entry there, so I could not
> mount.

This happens because the fossil config file burnt onto the start of the fossil
partition does not contain a srv command, it is passed on the command line when fossil
is envoked.

/sys/src/9/boot/local.c:256
	run("/boot/fossil", "-f", partition, "-c", "srv -A fboot", "-c", "srv -p fscons", 0);

You could start the bootable CDROM and then type:

	% fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
	% mount /srv/open /n/open

Your fossil filesystem should now appear in /n/open/active/ and all permission
checking will be turned off so you can fix anything you like.

It is definitely possible to boot using other boot managers, and you can even use
the NT/Win2k/XP boot manager though the installer only knows about FAT filesystems,
you will have to edit the files on NTFS partition by hand.

I suggest you check the 9fans archives there are several theads on this subject, E.G.
http://groups.google.com/group/comp.os.plan9/browse_frm/thread/8dbf0f7e64f51541

-Steve

Re: [9fans] accesing a local fossil

[Ezequiel Reyes]

----- Original Message -----
From: "Christoph Lohmann" <20h@r-36.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Sent: Monday, August 15, 2005 9:42 AM
Subject: Re: [9fans] accesing a local fossil

> That was the old 9grid.de ISO, as it used the binaries from the server. It
> is now build from the binaries in the mirror and the "circular menus"[0]
> should disappear, since they are not in the distribution and are only a
> patch that can be applied.
>

does that mean that if I redownload the vesa enabled iso now it will be more
up to date with standard than the one I download some days ago?

Re: [9fans] accesing a local fossil

[Christoph Lohmann]

Good day.

On Mon, 15 Aug 2005 12:09:29 -0700
"Ezequiel Reyes" <ezequiel.reyes@newhotel.co.cu> wrote:

> does that mean that if I redownload the vesa enabled iso now it will be
> more up to date with standard than the one I download some days ago?

No, because the floppy for the installation of the VESA ISO is not rebuild
every day. Just the "Boot from CD" will get you into the updated binaries.

Sincerely,

Christoph

Re: [9fans] accesing a local fossil

[Ezequiel Reyes]

----- Original Message -----
From: "Steve Simon" <steve@quintile.net>
To: <9fans@cse.psu.edu>
Sent: Monday, August 15, 2005 10:26 AM
Subject: Re: [9fans] accesing a local fossil


> This happens because the fossil config file burnt onto the start of the
fossil
> partition does not contain a srv command, it is passed on the command line
when fossil
> is envoked.
>
> /sys/src/9/boot/local.c:256
> run("/boot/fossil", "-f", partition, "-c", "srv -A fboot", "-c", "srv -p
fscons", 0);
>
> You could start the bootable CDROM and then type:
>
> % fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
> % mount /srv/open /n/open
>
> Your fossil filesystem should now appear in /n/open/active/ and all
permission
> checking will be turned off so you can fix anything you like.
>

I did just that, I first listed to find all fossils:

ls /dev/sd*/foosil

which gave me /dev/sdC0 twise

Then:

% fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
% mount /srv/open /n/open

But there was no /n/open/active. In /n/open there was I filesystem very
similar to the one on the CD but with some files missing and different date
signatures.
When I tried to cp some file  there:

can't create "/n/open/PLAN9.INI" : mounted directory forbids creation

I had installed plan 9 using the option 1 of the CD and the 9pccd.gz in it
to run the instalation system. I am sure it installed, there were no errors
during the process and the progress bar took some time. When I boot I get
these 3 final lines:

using sdC0!9fat!plan9.ini
Boot devices: fd0 ether0 sdC0!9fat
boot from:

Then I tried sdC0!9fat!9pcdisk.gz but: error walking to 9pcdisk.gz

So, there is a plan 9 system installed, but I can not access it because the
plan9.ini is not well configured or does not mention the proper kernel file.
I can not depend on the floppy because it does not have vesa driver on it so
rio won't start. That's why I am trying to create or modify a plan9.ini file
on the instalation using the cd demo system.
Is it at all possible to do this? I mean, accesing the just installed system
using the CD demo and modifying or copying the plan9.ini file?
In case it is, why can't I write on the mounted fossil?
where should I put (or look for in order to modify) the plan9.ini on the
disk?
The booting system finds it on sdC0!9fat!plan9.ini
But I can't find it on the mounted fossil.

Re: [9fans] accesing a local fossil

[Robert Raschke]

Hi,Ezequiel

you wrote:
> I did just that, I first listed to find all fossils:
> 
> ls /dev/sd*/foosil
> 
> which gave me /dev/sdC0 twise
> 
> Then:
> 
> % fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
> % mount /srv/open /n/open
> 
> But there was no /n/open/active. In /n/open there was I filesystem very
> similar to the one on the CD but with some files missing and different date
> signatures.
> When I tried to cp some file  there:
> 
> can't create "/n/open/PLAN9.INI" : mounted directory forbids creation
> 

You won't want to copy plan9.ini to your fossil file system.  You want
to copy (or edit) plan9.ini on your 9fat partition.  This will have
been set up during the CD installation.

Once you have booted (in some fashion or other) you should be able to do
; 9fat:
; cd /n/9fat

and now see your plan9.ini and any kernels that you may want to boot
directly from your HD. (9fat: is a script in /rc/bin)

I hope this might point you into the right direction.  The man pages
for booting ( plan9.ini(8), 9load(8), booting(8), boot(8) and some
more you can get to from them) are little bit hard to understand, as
they have extremely high informational content, but I can recommend
going through them at regular intervals.

> I had installed plan 9 using the option 1 of the CD and the 9pccd.gz in it
> to run the instalation system. I am sure it installed, there were no errors
> during the process and the progress bar took some time. When I boot I get
> these 3 final lines:
> 
> using sdC0!9fat!plan9.ini
> Boot devices: fd0 ether0 sdC0!9fat
> boot from:
> 
> Then I tried sdC0!9fat!9pcdisk.gz but: error walking to 9pcdisk.gz

Maybe your 9fat partition doesn't have that particular kernel?

> So, there is a plan 9 system installed, but I can not access it because the
> plan9.ini is not well configured or does not mention the proper kernel file.
> I can not depend on the floppy because it does not have vesa driver on it so
> rio won't start. That's why I am trying to create or modify a plan9.ini file
> on the instalation using the cd demo system.
> Is it at all possible to do this? I mean, accesing the just installed system
> using the CD demo and modifying or copying the plan9.ini file?
> In case it is, why can't I write on the mounted fossil?
> where should I put (or look for in order to modify) the plan9.ini on the
> disk?
> The booting system finds it on sdC0!9fat!plan9.ini
> But I can't find it on the mounted fossil.

Hope this helps a little,
Robby

Re: [9fans] accesing a local fossil

[Micah Stetson]

> % fossil/fossil -f /dev/sdC0/fossil -c 'srv -APW open' -c 'srv -p fscons'
> % mount /srv/open /n/open
 ...
> When I tried to cp some file  there:
> 
> can't create "/n/open/PLAN9.INI" : mounted directory forbids creation

As Robby said, you probably don't want to copy your plan9.ini there. 
But the reason the copy fails is that Plan 9 mounts don't allow
creation by default, you have to use 'mount -c /srv/open /n/open'.

Micah