Hello,

I was looking for an oss-bit-size bug/RFE to work on, and saw this one : 

*tar* tar needs 'z' functionality
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6267081

The basic idea is to implement -z (and why not -j) options to tar, like gnu-tar 
does.

I had a look at tar.c, and it seems the modifications needed are a bit more 
complicated than usual oss-bit-size bugs/RFE, at least to me, but that's an 
interesting task and I think it'd be usefull.

I don't know yet how this should be done, but I thought it could be to rewrite 
all file related syscalls (read,write,fseek ...). read() could be replaced by, 
say, Read(), which is a function that can read directly into bz2 or gzip files. 
Thus the changes in the actuel code would be minimal (replacing some syscalls 
by new function names), and we'd just need to add a few functions. I think that 
may work fine quite easily (but I may be wrong), at least for files located on 
disks (tar must work with tapes, and I don't know if writting/reading tapes 
requires specific knowledge).

I then wondered if it could be usefull to have this kind of functions for 
something else. I guess yes, and then why not having library functions that'd 
do that ? Reading/writting directly into bzip2 or gzip files like we do for 
"normal" files may be nice.

bz2_read(/* same args than read*/)
bz2_fseek(...)
bz2_write(...)
gzip_read(...)
....

Are there already such lib functions ?
Maybe it sounds a bit like having compression into ZFS, or Hurd's translators ?
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to