Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Thanks for that - I haven't tried it there...

Yup - single file operation was a design goal, but I bet there's a better way to get it working than the hack I used.



sort by: page size:

Single File works better IMHO.

SingleFile can do it.

Yea, have to try that some time.

I'll need to switch from one biiiig file to multiple than though. I think my biggest hindrance is setting up the refile targeting :)


OK, I'll give that a go too, thanks!

EDIT: I guess one disadvantage of this approach is that the file system structure is exposed. Convenient though.


Cool hack.

Though I'd definitely advise wanting to do this to Do The Right Thing™ and just put each thing in its own file.


What bothers me is that this requires a running linux kernel and root to eventually produce a single regular file. Why is this not refactored in such a way that it can be done conveniently from userspace?

Looks useful. Should make it single-header / single-file too. Regex would also be good to have.

How would that be possible without having to essentially keep track of two files? Nice idea though.

I will take a look -- however, since I only use a single file, it may not be needed.

For the single file case, if you pass --with-filename then it should work.

That is interesting. Could you please describe in short your methodology? Did you try to read/write many small files, or one big file?

What about with ReadyToRun and single file?

But only as long as it stays in a single file :(. And it does not have support for arrays as well

Wow, thanks for the script. Surprising in its simplicity. I would have thought this use-case was popular enough to warrant specialized tools etc. Especially in the scientific community where they transfer large files.

I mean multiple files.

I've been doing this with sshfs (Linux/Mac) or ExpanDrive (Windows) for years, with whatever my editor of choice is for the file in question.

Yeah, we only use simple mode - it's advanced mode that everyone needs to watch out for - it doesn't do what you expect (it's optimized for combining multiple files, not producing one file).

I didn't propose that. The point is to read the file once, then do multiple steps on it, and write it out just once.

That link talks about putting the entirety of very small files into their inodes. I don't see anything about combining the tails of multiple files in a single block.
next

Legal | privacy