in place file splitter

[Igor Gueths]

Hi Chuck. I think you're probably right, as the file contents will have to
be stored in RAM until written to outfiles.

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Fri, 8 Nov 2002, Charles Hallenbeck wrote:

> Removing the input file before the output files are written is
> what we used to call a "bridge burn".
>
> When you make a list of the chunks of the input file, where are
> they held before writing them? Does this mean you have to have a
> ram total that is at least the size of the file?
>
> Just curious.
>
>
> On Fri, 8 Nov 2002, Tyler Spivey wrote:
>
> > well, normally the split command does something like:
> > 1. open the file for reading.
> > 2. take one chunk, open a new output file, place it there and close it.
> > 3. repeat until split.
> > this keeps the original file, and on a space limited system, e.g. a quota,
> > you're out of luck.
> > in place does:
> > 1. open the file for reading.
> > 2. read al the chunks into some kind of list.
> > 3. wait to press enter, so the user can suspend the program and remove the
> > file.
> > 4. write the output files.
> > if you remove the original file, the split files take up almost the same
> > space so quotas don't get in the way.
> > my program is no where complete, just a skeleton though.
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> The Moon is Waxing Crescent (22% of Full)
> So visit me at http://www.valstar.net/~hallenbeck
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>