Re: how to make my RAID device WORM(write once and read many)

2005-04-18 Thread Lowell Gilbert
Please don't top-post.

prasadam kumar [EMAIL PROTECTED] writes:

 Thanks for responding to my query,
 actually it is a raid5 storage device it contains
 firewire and usb ports, through this
 interface a user can store data to the  raid5 device
 irrespective of file system.
 once he copied data to the device it should be
 immutable(i.e cannot be modify and delete).
 Can u suggest any approach to achieve this task.

If the system immutable and system undeletable flags are not good
enough for what you want, then the OS can't help you, and you will
need a hardware solution.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: how to make my RAID device WORM(write once and read many)

2005-04-18 Thread
prasadam kumar wrote:
hai,
Thanks for responding to my query,
actually it is a raid5 storage device it contains
firewire and usb ports, through this
interface a user can store data to the  raid5 device
irrespective of file system.
once he copied data to the device it should be
immutable(i.e cannot be modify and delete).
Can u suggest any approach to achieve this task.
bye
ppk
---  
[EMAIL PROTECTED] wrote:
 

prasadam kumar wrote:
   

hai,
I am working Raid5 storage device and i want to
 

make
   

my device WORM(write once and read many) and
undeleatable. I formated the target device in vfat,
when 
i am mounting the device in host machine it should 
behavie like WORM. To achive this feature whether i
 

have to change in host machine or target machine,
which one is better approach and plz tell me how to
achive this.
bye
ppk

 

The first question is: for which purpose do you need
this feature ? In 
any case, you will need to have backup for this
RAID.
From my point of view, it looks like some version
control management 
system. May be, it will be wiser to use it ?

As i understand, you can't get this feature from
plain filesystem. Even 
if you hack vinum to allow write only once in every
block, usual 
filesystem will not work on such device. You can
make something like 
database with add-only interface (MySQL + some
scripting) and allow 
access from Web interface.

Take a look on some SCM solutions, it may be what
you want.
--
Best Regards,
Alexander Derevianko
___
freebsd-questions@freebsd.org mailing list
   

If users can't delete files, it indeed means that any attempt to open 
file for writing must create a new version of the file.
Or any user can put garbish (or zero length file) into any available to 
him.

Another approach will be to change permissions such that nobody can open 
again once created file. It seems for me, that it must be possible  to 
obtain such functionality via ACL permissions. But unfortunelly i don't 
have expirience with ACL permissions in latest FreeBSD's.

In any case, something like CVS repository with only last revision 
visible from user side will be best solution.
Where is some SCM systems based on versioning filesystem, you can take a 
look on them. For example, here http://www.daveeaton.com/scm/CMFAQ.html

But it seems for me that most of them are commercial. If you don't want 
to pay for it and have much spare time, you can make own
NFS server which will work under plain filesystem layer and will 
implement versioning.

Think deep about you task, and try to imagine how users will use this 
feature.

--
Best Regards,
Alexander Derevianko
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: how to make my RAID device WORM(write once and read many)

2005-04-18 Thread Roland Smith
On Mon, Apr 18, 2005 at 09:27:48AM -0400, Lowell Gilbert wrote:
 Please don't top-post.
 
 prasadam kumar [EMAIL PROTECTED] writes:
 
  Thanks for responding to my query,
  actually it is a raid5 storage device it contains
  firewire and usb ports, through this
  interface a user can store data to the  raid5 device
  irrespective of file system.
  once he copied data to the device it should be
  immutable(i.e cannot be modify and delete).
  Can u suggest any approach to achieve this task.

If it's OK to invoke a shell-script to do the archiving, and if you're
using UFS it would be possible, I think. That script should do the following:

- check for name clashes (abort with an error if a file already exists).
- copy the file to the target disk.
- chmod ugo-w the file to remove all write permissions.
- chflags schg,sunlnk,uchg,uunlnk file

Of course this is not foolproof, because the superuser can change the
flags and permissions.

Another option would be to use a revision control system that can handle
arbitrary files like subversion. If you write (commit) a new version
of a file, the old version is not lost. This also supposes that you
create a wrapper script to make things easier (because the first write
has to be an add rather than a commit, and other details like
creating directories etc).

Roland
-- 
R.F. Smith   /\ASCII Ribbon Campaign
r s m i t h @ x s 4 a l l . n l  \ /No HTML/RTF in e-mail
http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail
public key: http://www.keyserver.net / \Respect for open standards


pgpTYJhwAhBXS.pgp
Description: PGP signature


Re: how to make my RAID device WORM(write once and read many)

2005-04-17 Thread prasadam kumar

hai,

Thanks for responding to my query,
actually it is a raid5 storage device it contains
firewire and usb ports, through this
interface a user can store data to the  raid5 device
irrespective of file system.
once he copied data to the device it should be
immutable(i.e cannot be modify and delete).
Can u suggest any approach to achieve this task.

bye
ppk

--- Александр Деревянко
[EMAIL PROTECTED] wrote:
 prasadam kumar wrote:
 
 hai,
 
 I am working Raid5 storage device and i want to
 make
 my device WORM(write once and read many) and
 undeleatable. I formated the target device in vfat,
 when 
 i am mounting the device in host machine it should 
 behavie like WORM. To achive this feature whether i
 
 have to change in host machine or target machine,
 which one is better approach and plz tell me how to
 achive this.
 
 bye
 ppk
 
 
  
   
 
 The first question is: for which purpose do you need
 this feature ? In 
 any case, you will need to have backup for this
 RAID.
  From my point of view, it looks like some version
 control management 
 system. May be, it will be wiser to use it ?
 
 As i understand, you can't get this feature from
 plain filesystem. Even 
 if you hack vinum to allow write only once in every
 block, usual 
 filesystem will not work on such device. You can
 make something like 
 database with add-only interface (MySQL + some
 scripting) and allow 
 access from Web interface.
 
 Take a look on some SCM solutions, it may be what
 you want.
 
 -- 
 Best Regards,
 Alexander Derevianko
 
 ___
 freebsd-questions@freebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 



__ 
Do you Yahoo!? 
Plan great trips with Yahoo! Travel: Now over 17,000 guides!
http://travel.yahoo.com/p-travelguide
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: how to make my RAID device WORM(write once and read many)

2005-04-16 Thread
prasadam kumar wrote:
hai,
I am working Raid5 storage device and i want to make
my device WORM(write once and read many) and
undeleatable. I formated the target device in vfat,
when 
i am mounting the device in host machine it should 
behavie like WORM. To achive this feature whether i 
have to change in host machine or target machine,
which one is better approach and plz tell me how to
achive this.

bye
ppk
		
 

The first question is: for which purpose do you need this feature ? In 
any case, you will need to have backup for this RAID.
From my point of view, it looks like some version control management 
system. May be, it will be wiser to use it ?

As i understand, you can't get this feature from plain filesystem. Even 
if you hack vinum to allow write only once in every block, usual 
filesystem will not work on such device. You can make something like 
database with add-only interface (MySQL + some scripting) and allow 
access from Web interface.

Take a look on some SCM solutions, it may be what you want.
--
Best Regards,
Alexander Derevianko
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


how to make my RAID device WORM(write once and read many)

2005-04-14 Thread prasadam kumar
  
hai to all,

I am working Raid5 storage device and i want to make
my device WORM(write once and read many) and
undeleatable. I formated the target device in vfat,
when 
i am mounting the device in host machine it should 
behavie like WORM. To achive this feature whether i 
have to change in host machine or target machine,
which one is better approach and plz tell me how to
achive this.

bye
ppk



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


how to make my RAID device WORM(write once and read many)

2005-04-13 Thread prasadam kumar

hai,

I am working Raid5 storage device and i want to make
my device WORM(write once and read many) and
undeleatable. I formated the target device in vfat,
when 
i am mounting the device in host machine it should 
behavie like WORM. To achive this feature whether i 
have to change in host machine or target machine,
which one is better approach and plz tell me how to
achive this.

bye
ppk



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]