↳
I did not have sufficient knowledge in filesystems to answer that question.
↳
I remember the way how I did it when I was in college is to first to know the current directory then you iterate each of file/directory nodes in the file system at that level and print out each of them one at time. Less
↳
If this is in reference to the command line. Typing ls in terminal in the "desired" file directory, will output all files within that file. So, for example if you navigate to your "documents" folder and type "ls" you will see all files contained inside your documents folder. Less
↳
this depends a lot on the executable file format and what the OS expects an 'executable' to be (a DOS COM file won't work like a Linux ELF or an OSX Mach-O file) however, the loader should be ready to resolve dynamic symbols needed by the file, by loading and mapping libraries into the new process' address space (unless symbols are loaded lazily, such as GetProcAddress() in Win32). once all this is complete, the loader should give control to the start routine of the process, which in most cases is not going to be the user's provided main() but some standard library initializing routine Less
↳
dunno. Seen it in college, never had to worry about those details.
↳
Deletion of node was easy and middle node also...