I am looking for some solution, working with Samba preferably, which
would allow multiple users to work on one document.
This means that if a user makes a change to the document, a previous
version of that document is saved somewhere else.
For example, user A opens a document (rw - read/write, ro - read-only
document):
rw \\server\share\document.txt
User makes some changes, and saves it to the same place.
This SVN/CVS-like share handles the change inteligently, and makes a
copy of the previous file to a ro file somewhere else:
ro \\server\share\backup\2005.12.22-16:24:04\document.txt
Do you have something in mind which would allow me to do something like
that *transparently* to the user (assuming the user doesn't know much
more about computers than opening Word document etc.)?

Hi!
Thu, Dec 22, 2005 at 04:24:59PM +0100, Tomasz Chmielewski wrote:
This SVN/CVS-like share handles the change inteligently, and makes a copy of the
previous file to a ro file somewhere else:
#id2618377
?
WBR

Thursday 22 December 2005 08:24, Tomasz Chmielewski wrote:
I am looking for some solution, working with Samba preferably, which
would allow multiple users to work on one document.

This means that if a user makes a change to the document, a previous
version of that document is saved somewhere else.

For example, user A opens a document (rw - read/write, ro - read-only
document):

rw \\server\share\document.txt

User makes some changes, and saves it to the same place.

This SVN/CVS-like share handles the change inteligently, and makes a
copy of the previous file to a ro file somewhere else:

ro \\server\share\backup\2005.12.22-16:24:04\document.txt
--
Do you have something in mind which would allow me to do something like
that *transparently* to the user (assuming the user doesn't know much
more about computers than opening Word document etc.)?

Folks, please refer all who ask deployment related questions to the "Samba-3
By Example book", not "The Samba-3 HWT and Reference Guide".

When you send a novice to read the HWT, it's like telling them to practice
for running a marathon before they can walk. It's like telling them to read a
mechanic's guide before they know what is a car.
- John T.

John H Terpstra schrieb:
Thursday 22 December 2005 08:24, Tomasz Chmielewski wrote:

>>I am looking for some solution, working with Samba preferably, which
>>would allow multiple users to work on one document.
>>
>>This means that if a user makes a change to the document, a previous
>>version of that document is saved somewhere else.
>>
>>For example, user A opens a document (rw - read/write, ro - read-only
>>document):
>>
>>rw \\server\share\document.txt
>>
>>User makes some changes, and saves it to the same place.
>>
>>This SVN/CVS-like share handles the change inteligently, and makes a
>>copy of the previous file to a ro file somewhere else:
>>
>>ro \\server\share\backup\2005.12.22-16:24:04\document.txt
>>
>>
>>Do you have something in mind which would allow me to do something like
>>that *transparently* to the user (assuming the user doesn't know much
>>more about computers than opening Word document etc.)?

Folks, please refer all who ask deployment related questions to the "Samba-3
By Example book", not "The Samba-3 HWT and Reference Guide".

Hmm? Have you actually read my original post?

There is no single occurance of (document) "versioning" nor "version
control" in the whole Samba-3 by Example.
And "version controlling" is mentioned only briefly in the HWT where
shadow_copy is described (with "do not use for version controlling" in
bold).

When you send a novice to read the HWT, it's like telling them to practice
for running a marathon before they can walk. It's like telling them to read a
mechanic's guide before they know what is a car.

Same happens when a "real proffessional" can't read more than half of
the subject of one's post

Tomasz,
You can use subversion to accomplish what you are doing easily. In
subversion there are these hook scripts (
#svn-ch-5-sect-2.1) that can
be invoked when a user commits or checkout a file. So in your case you can
write a simple commit hook that copies the last version to a ro filesystem
and then commits the document.

When you send a novice to read the HWT, it's like telling them to
practice
for running a marathon before they can walk. It's like telling them to
read a
mechanic's guide before they know what is a car.

John I think you are assuming too much here about the user from one simple
email question. I do see the point you are trying to make, but how is
Dmitriy to know what skill level Tomasz possess? Also often the user might
be just trying to find out that it can be done.

Vijay Avarachen
:wq!

12/22/05, Tomasz Chmielewski <mangoo (AT) wpkg (DOT) orgwrote:

I am looking for some solution, working with Samba preferably, which
would allow multiple users to work on one document.

This means that if a user makes a change to the document, a previous
version of that document is saved somewhere else.

For example, user A opens a document (rw - read/write, ro - read-only
document):

rw \\server\share\document.txt

User makes some changes, and saves it to the same place.

This SVN/CVS-like share handles the change inteligently, and makes a
copy of the previous file to a ro file somewhere else:

ro \\server\share\backup\2005.12.22-16:24:04\document.txt
--
Do you have something in mind which would allow me to do something like
that *transparently* to the user (assuming the user doesn't know much
more about computers than opening Word document etc.)?
--

While Samba is a great tool, there is no one tool that will work for
every occasion. The use you are describing may be very well served with
a collaboration tool, such as a Wiki. A web based solution, there are
many flavors out there which have various levels of security and
accessories. Personally, I happen to favor TWiki (see
http://www.twiki.org/). It has a fair CVS system built in, can support
multiple projects simultaneously, and many other useful features.

You user simply goes to a web page, views the document, edits it as
necessary, and moves on. It is fairly user friendly. If your user can
learn to log into a computer, open Word, edit a document, close it, and
later find the dame document, he should have little problem with a Wiki
site. Previous copies are retained, and there is a difference feature
which will highlight the changes between recent versions.

Just a thought.

Michael

Tomasz Chmielewski told me on 12/22/2005 09:24:
I am looking for some solution, working with Samba preferably, which
would allow multiple users to work on one document.

This means that if a user makes a change to the document, a previous
version of that document is saved somewhere else.

For example, user A opens a document (rw - read/write, ro - read-only
document):

rw \\server\share\document.txt

User makes some changes, and saves it to the same place.

This SVN/CVS-like share handles the change inteligently, and makes a
copy of the previous file to a ro file somewhere else:

ro \\server\share\backup\2005.12.22-16:24:04\document.txt

Do you have something in mind which would allow me to do something like
that *transparently* to the user (assuming the user doesn't know much
more about computers than opening Word document etc.)?

Thursday 22 December 2005 09:11, Tomasz Chmielewski wrote:
Hmm? Have you actually read my original post?

No, I did not read it in detail - I scanned it. Sorry, I did miss the thrust
of your question.

There is no single occurance of (document) "versioning" nor "version
control" in the whole Samba-3 by Example.

That is perfectly correct. There won't be either, unless someone contributes a
chapter geared towards example deployment of neat ways of implementing very
advanced capabilities.

And "version controlling" is mentioned only briefly in the HWT where
shadow_copy is described (with "do not use for version controlling" in
bold).

Correct. If you want flexible and managable file versioning on a Samba share
it will most likely be necessary to write a VFS module to do that.

When you send a novice to read the HWT, it's like telling them to
practice for running a marathon before they can walk. It's like telling
them to read a mechanic's guide before they know what is a car.

Same happens when a "real proffessional" can't read more than half of
the subject of one's post

I believe you are being a little unkind here.

I admit that I overlooked the thrust of your request. For that I apologise.

What has been "unprofessional" about my request? Did you mean to insult me?
- John T.

John H Terpstra schrieb:

()

>>And "version controlling" is mentioned only briefly in the HWT where
>>shadow_copy is described (with "do not use for version controlling" in
>>bold).

Correct. If you want flexible and managable file versioning on a Samba share
it will most likely be necessary to write a VFS module to do that.

some FUSE-like filesystem.

When you send a novice to read the HWT, it's like telling them to
practice for running a marathon before they can walk. It's like telling
them to read a mechanic's guide before they know what is a car.
>>
>>Same happens when a "real proffessional" can't read more than half of
>>the subject of one's post

I believe you are being a little unkind here.

I admit that I overlooked the thrust of your request. For that I apologise.

What has been "unprofessional" about my request? Did you mean to insult me?

No, just Santa doesn't love me and I had a bad day.
Sorry for being rude.

PGP SIGNED MESSAGE
Hash: SHA1

Tomasz Chmielewski wrote:

There is no single occurance of (document) "versioning" nor
"version control" in the whole Samba-3 by Example.
And "version controlling" is mentioned only briefly in the
HWT where shadow_copy is described (with "do not use
for version controlling" in bold).

Deryck does something like this at work but I think it's geared
to support multiple concurrent writers. Does use svn as the
backed IIRC.

Maybe he can add a few comments.

cheers, jerry

Alleviating the pain of Windows(tm) http://www.samba.org
Centeris http://www.centeris.com
"There's an anonymous coward in all of us."
PGP SIGNATURE
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

NkoaJafPaKDDe83Jae6xjqs=
=Q3pj
PGP SIGNATURE

1/4/06, Gerald (Jerry) Carter <jerry (AT) samba (DOT) orgwrote:
Deryck does something like this at work but I think it's geared
to support multiple concurrent writers. Does use svn as the
backed IIRC.

Maybe he can add a few comments.

In my setup, the share is itself a subversion working copy. At the
end of the day, I have a script commit the changes. My need is only
for an easy backup of the day's work. I don't have to negotiate
between changes by multiple users on the same file.

I'll probably work my setup into a proper VFS module at some point,
but I don't think it would do what the original poster wanted -- i.e.
make backup copies when users save the file. I'm not sure how you
could sanely negotiate merges from all those backups anyway, but maybe
there's a way.

Cheers,
deryck