Not booting anymore & fvdw-sl-16.1: telnet timeout

[tenhouse]

Hi guys got another question:

Is there any way to either mount my ntfs disk or to access a windows share via network? Or create a samba share?

I tried out all "common" commands which know for that, but no tool is available in this kernel (which is obviously ok to keep it small).

[fvdw]

Samba is a little complicated, I am working on package containing an ftp server. Maybe I can finish that this weekend

[tenhouse]

I see. Don't rush yourself, I don't need it that badly, I will just reformat my disk to ext3 in this case :)

[tenhouse]

Hi

Yet another follow up question.

I formated my external HD with ext3 and to backup the data I wanted to use "rsync", however it appears it's not installed. Is it possible to easily static compile it? Or is it also complicated? Or do you have a good alterantive for it? I know I can do it with "cp -r" but this seems a little "error prone", if the telnet times out etc and no progress is shown.

Greetings

[fvdw]

In the meantime I developed a pacakage that will start a ftp server that you can connect to with a ftp client. Still doing some test but it seems to work ok and also fast. A little more patience

[tenhouse]

Hello I'm copying with cp now but I ran into problems:

Code: Select all

cp: can't open 'xyz': File too large


I don't know why this happens, I formatted my external disks with ext3....
With some googling I read, that some kernels do not support big files - is thiss such a case?

Here is some information which may help:

Code: Select all

root@fvdw-sta-kirkwood:/ # sysctl -a | egrep -i 'huge|size|memory'
fs.pipe-max-size = 1048576
kernel.random.poolsize = 4096
sysctl: error reading key 'net.ipv4.route.flush': Permission denied
net.ipv4.route.max_size = 2147483647
sysctl: error reading key 'net.ipv6.route.flush': Permission denied
net.ipv6.route.max_size = 4096
vm.overcommit_memory = 0
root@fvdw-sta-kirkwood:/ # ulimit -f
unlimited



edit:

ah just saw your post, I see thank you maybe I can use the ftp server later if needed...

[fvdw]

I see, you can test it already if you want
put the attached tar archive in the tftp folder of the fvdw-sl console
upload it to the nas via standalone kernel, be sure to be in root of system (/)

Code: Select all


cd /
tftp -r vsftpd-303-standalone-4jun16.tar -l vsftpd-303-standalone-4jun16.tar -g ip-pc

replace ip-pc by actual ip of your pc

extract the archive

Code: Select all

tar -xvf vsftpd-303-standalone-4jun16.tar

Start the ftp server

Code: Select all

vsftpd &

Connect to the server using a ftp client like FileZilla
username: root
password: giveit2me
port 21

VERY IMPORTANT: be sure your ftp client is set to binary transfer mode !
If you don't do that then some file will become corrupt as in ftp protocol will take out <CR> characters in certain files. This is not an error but by design of the protocol. If you use binary transfer this won't happen.

---edit---
With the last version 6.0,  you need no longer to upload vsftpd manually. Use a new option with fvdw-programs menu :
* run on the telnet window the command: fvdw-sl-programs
(then a menu will appear)
* select "Upload and extract glibc mini and tools"

Jocko

[tenhouse]

Hi

Just tried the ftp for a single file (2.90 GB size, which didn't work with "cp"). Worked like a charm, I had a speed of 80 MB/s - pretty neat!

I'm going a way for holidays for a few days (actually even to amsterdam ;) ) - will probably test for a really "big" directory (with many many files) afer I'm back.

Thanks again for the nice work :)

[tenhouse]

So I couldn't resist and let it run overnight, to backup a part of my data...¨

The screenshot speaks for itself:

http://www.fotos-hochladen.net/uploads/ftprkyzwx5sna.png


The 11 failed files only failed because their path is too long for windows ;)

I'll have to more some more comparisons to see if everythign fully worked, but I'm very confident!

[fvdw]

thanks for testing I think this package is ok and will be helpful to many