-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List @ filesystems in root directory listing #21959
List @ filesystems in root directory listing #21959
Conversation
I wonder if we should add the @ filesystems that support directory listing to root of / ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure that the final logic is that clear
d68c1bf
to
f25adc8
Compare
I tested this in SITL, both MAVProxy and MissionPlanner, and on CUAVv5, both MAVProxy and MissionPlanner. |
f25adc8
to
f8143ee
Compare
Adds virtual directory entries for these virtual filesystems in / RTL> ftp list RTL> Listing / D @mission D @param D @RomfS D @sys D APM D log V5_BT.dfu 10541 bootlog.txt 297 dataman 350216 message-intervals-chan0.txt 7 Total size 352.60 kByte ftp list @mission RTL> Listing @mission LIST: OP seq:7 sess:2 opcode:129 req_opcode:3 size:2 bc:0 ofs:0 plen=2 [2] ftp list @RomfS RTL> Listing @RomfS bootloader.bin 16448 hwdef.dat 5743 io_firmware.bin 40880 Total size 61.59 kByte This PR also makes us *much* more lenient in what we accept for looking at virtual filesystems, so ftp list @sys ftp list /@sys ftp list @SYS/ ftp list /@SYS/ should all work
f8143ee
to
960eb6f
Compare
we should have a bool supports_dirlist() method on the backend, false for MISSION and PARAM until we add those |
ftp get