also sprach Cassandra Lynette Ludwig <cass@ophiuchi.net> [2002.01.16.0442 +0100]: > Did you read the initial message? For those who have not read it, or > are unable to read english here is it detailed (I hate having to do > this for men all the time *sigh*) quite a statement, hey! yes, i did read you initial message, and no, i am not 100% stupid, but i couldn't really get all the info. and on a side note, please keep in mind: you are the one asking for help. so please think twice before bitching! > > Is your fileserver on Windows? If that is the case you will have a > > problem since Windows filesystems suffer the 2GB limit, as far as I > > know (maybe recent NTFS does not, I know FATxx all do). In the case > > of FTP and Samba, both of these have a 2GB limit as well. > > No, read the original message. maybe it should give you a hint that many people seem to have misunderstood.. > > The simplest thing, might be to send the files across in 2GB chunks > > and re-assemble them at the destination. NFS is not a very good > > protocol for file transfer so I would not suggest using that. 100GB > > of data would take ages to send across. Even 2GB could take a > > while. But V3 NFS does support large files. V2 NFS does not. If > > you have to try to do it with Windows NT NFS support, I would not > > expect good results (it isn't even very good at ordinary tasks). > > I cannot split the video data into multiple files - this is not text > it is compressed DVI data. If you do not know the file format, do not > suggest options like this. if you do not files, then don't complain. iterate 2^32-1 bytes, then *cut*. start the second chunk at offset 2^32, and *cut* after 2^32-1 bytes. on unix, all you then do is `cat` them back together. works for every file, even compressed-inverted-encrypted-signed-unicode. > > You might be able to get the file across using HTTP, I do not > > believe there is a size limit for that. Other options, if you get > > desperate, might include ZModem over telnet, IRC DCC, or even 20 > > lines of C code to open a socket and just send the raw data without > > any regard to file size. > > > > The problem though, is with the file transfer protocol, not with > > Linux. :} > > Actually, Linux programmers implemented the file transfer protocol, > therefore the fault is with linux. get your history straight. Linux Is Not UniX > Don't annoy me anymore with messages as un thought out as this. It > feels like the sort of responses I used to get from the Redhat > technical support team. do you always behave that way around people trying to help you? -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck this email was written on an os using the viral 'gpl' as it's license. please check with billy gates before continuing to read this message.
Attachment:
pgpPtpWJ6eUD4.pgp
Description: PGP signature