Re: [9fans] fossil+fossi=suicide

Re: [9fans] fossil+fossi=suicide

[David Presotto]

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

with the new fossil (after you get past your linker problems) you can say
'fsys main srv -AWP unprotected' (actually pick your own name).  This
will create a /srv/unprotected for the same file system you are currently
using.  You can then mount that and use it to get unprotected access.

[-- Attachment #2: Type: message/rfc822, Size: 2279 bytes --]

From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: [9fans] fossil+fossi=suicide
Date: Mon, 24 Nov 2003 12:27:46 +0200
Message-ID: <81132473206F3A46A72BD6116E1A06AE479CAE@black.aprote.com>

This is probably an exceptionally dumb course of
actions, but I got my fossil crashed and burned
rather nicely by opening the same device twice,
one of them with permission checking off.

I should've halted one of them, shouldn't I?

Tiit

Re: [9fans] fossil+fossi=suicide

[andrey mirtchovski]

Is it possible to 'undo' the srv command? Say if a script is used to run
replica it could tell fossil to create /srv/replica with -AWP, run pull,
remove /srv/replica and tell fossil to remove the posted fd.

Running replica on an -AWP-ed fossil fd is really preferable, since things
like yesterday permissions changes just don't work in a situation where
I do a pull with my user being a member of the sys group. In my case
replica was unable to modify the permissions of the files in antiword/
because they are owned by my user locally and by sys on sources, so
fossil wouldn't allow a chmod.

andrey

On Mon, 24 Nov 2003, David Presotto wrote:

> with the new fossil (after you get past your linker problems) you can say
> 'fsys main srv -AWP unprotected' (actually pick your own name).  This
> will create a /srv/unprotected for the same file system you are currently
> using.  You can then mount that and use it to get unprotected access.

Re: [9fans] fossil+fossi=suicide

[jmk]

Do you mean
	srv -d /srv/replica
?

On Wed Nov 26 16:33:44 EST 2003, mirtchov@cpsc.ucalgary.ca wrote:
> Is it possible to 'undo' the srv command? Say if a script is used to run
> replica it could tell fossil to create /srv/replica with -AWP, run pull,
> remove /srv/replica and tell fossil to remove the posted fd.
>
> Running replica on an -AWP-ed fossil fd is really preferable, since things
> like yesterday permissions changes just don't work in a situation where
> I do a pull with my user being a member of the sys group. In my case
> replica was unable to modify the permissions of the files in antiword/
> because they are owned by my user locally and by sys on sources, so
> fossil wouldn't allow a chmod.
>
> andrey
>
> On Mon, 24 Nov 2003, David Presotto wrote:
>
> > with the new fossil (after you get past your linker problems) you can say
> > 'fsys main srv -AWP unprotected' (actually pick your own name).  This
> > will create a /srv/unprotected for the same file system you are currently
> > using.  You can then mount that and use it to get unprotected access.

Re: [9fans] fossil+fossi=suicide

[mirtchov]

> Do you mean
> 	srv -d /srv/replica
> ?

Is that it?  I'm somewhat adverse to trying random undocumented
options since they manage to crash my system with astounding
regularity (case in point: "fsys main srv -AWP replica", the command
line suggested in the original email by Presotto, silently hung my
fossil requiring a reboot).

Here's what the man page says:

          srv [ -APWdp ] name

then later:

          Srv behaves like listen but uses /srv/name rather than a
          network address.  With the -p flag, srv edits a list of con-
          sole services rather than 9P services.  See the [fsys] open
          command below for a description of the -APW options.


To be honest to the man page, the -d flag is explained in the case of
'listen' and should be obvious to anyone with half a brain who read it
thoroughly, sadly this is not the case with me :)

andrey

Re: [9fans] fossil+fossi=suicide

[jmk]

I admit the manual page might not be as clear as it could be.

Re: [9fans] fossil+fossi=suicide

[okamoto]

> I admit the manual page might not be as clear as it could be.
from man page of srv;
          -d   Enable debugging.

What does this mean 'debugging' in this case?

Kenji

Re: [9fans] fossil+fossi=suicide

[mirtchov]

>> I admit the manual page might not be as clear as it could be.
> from man page of srv;
>           -d   Enable debugging.
>
> What does this mean 'debugging' in this case?

we were talking about the fossil command "srv", which is described in
fossilcons(8), that's where I had pasted the comment from.

Re: [9fans] fossil+fossi=suicide

[okamoto]

> we were talking about the fossil command "srv", which is described in
> fossilcons(8), that's where I had pasted the comment from.

Ahaha, no, I've not read enough of fossil related.
It's your work, not myself, sorry. ☺

Kenji

Re: [9fans] fossil+fossi=suicide

[David Presotto]

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

rm /srv/unprotected works fine.

[-- Attachment #2: Type: message/rfc822, Size: 3250 bytes --]

From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+fossi=suicide
Date: Wed, 26 Nov 2003 14:32:34 -0700 (MST)
Message-ID: <Pine.LNX.4.44.0311261420070.12183-100000@fbsd.cpsc.ucalgary.ca>

Is it possible to 'undo' the srv command? Say if a script is used to run
replica it could tell fossil to create /srv/replica with -AWP, run pull,
remove /srv/replica and tell fossil to remove the posted fd.

Running replica on an -AWP-ed fossil fd is really preferable, since things
like yesterday permissions changes just don't work in a situation where
I do a pull with my user being a member of the sys group. In my case
replica was unable to modify the permissions of the files in antiword/
because they are owned by my user locally and by sys on sources, so
fossil wouldn't allow a chmod.

andrey

On Mon, 24 Nov 2003, David Presotto wrote:

> with the new fossil (after you get past your linker problems) you can say
> 'fsys main srv -AWP unprotected' (actually pick your own name).  This
> will create a /srv/unprotected for the same file system you are currently
> using.  You can then mount that and use it to get unprotected access.

RE: [9fans] fossil+fossi=suicide

[Tiit Lankots]

OK, this was dumb. I actually managed to send 
two mails before I started thinking.

Thou shalt not send any mail before thy wakeup
coffee.

Tiit

RE: [9fans] fossil+fossi=suicide

[Tiit Lankots]

s/open/write/

Lousy bony fingers! (Grim Fandango)

RE: [9fans] fossil+fossi=suicide

[Tiit Lankots]

Correct me if I'm wrong. Anyone who can open
/srv/fscons has unlimited access to the file system?

Tiit

[9fans] fossil+fossi=suicide

[Tiit Lankots]

This is probably an exceptionally dumb course of
actions, but I got my fossil crashed and burned
rather nicely by opening the same device twice,
one of them with permission checking off.

I should've halted one of them, shouldn't I?

Tiit