Hello, On Tue, 08 Aug 2017, Walter Dnes wrote: >> Try a: >> >> ftp> cd incoming > > Thank you, that was it. I just pushed over a file from a Gentoo >machine to my desktop for a test. The OS/2 Warp ftp client still >doesn't work, but that's probably a VM networking issue. There are >other ways of getting data from inside the VM to the host machine, then >I can ftp from there. > > Annoying "feature"... if I set "anon_root=/home/ftp/incoming/", then >vsftpd refuses to run, complaining about a writable chroot directory.
Yeah, it's all about the writeable root (of the chroot). Whichever path that is. Writeable chroot-root is just a "no-no" ;) And having those rights on /incoming is quite sane... >So I have to do an anonymous login, starting of in /home/ftp/ and then >manually "cd incoming". Or just add the target-dir at the end of the 'put foo /incoming/'. And have a look at your client configuration ... For the plain net-ftp/ftp client, it's ~/.netrc (see 'man 5 netrc'). Uhhm, that's not quite intuitive to use... So here's a working example: ==== ~/.netrc ==== machine localhost login anonymous password "test@localhost" macdef init pwd cd /incoming pwd default login anonymous password "invalid@invalid.invalid" ==== That way, you'd be auto-logged-in and auto-chdired to incoming on localhost. Ain't that nice? You could add more commands to that init-macro... Like a 'put foo' ;) Add a host-alias to your /etc/hosts use that for a 'machine foo' directive in your .netrc and *tada* all can be automated ;) That's Unix: a large box of pieces that can all be combined creatively - or less so. The 'pwd' are just for debugging (and the macro-definition (here the special init macro) ends at the empty line). That should get you started :) Anyway, TUI/GUI clients like ncftp and gftp often have similar features... Or even read ~/.netrc. HTH, -dnh, lovin' it to know the basics, learned in the 90ies, still valid today ... -- Truth's a bitch. -- Beka Valentine, Andromeda 3x04 - "Cui Bono"