grep (do it locally using pipe?)
dd (?)
ln / ln -s
- mknod
readlink
utime / utimes / futimes / futimens / l..
- mkfifo
more mk*temp calls
- readdir / readdir-and-stat
some sort of alloc/fallocate/posix_fallocate call to create empty space
realpath
trunc[ate??]
+ getfattr (also useful because gives us access to NTFS datastreams)
+ setfattr
ext2 properties:
chattr
Using objdump or readelf?
What about non-ELF files (eg. Windows, BSD).
+To do this properly requires some serious logic, eg. to cover Linux
+and Windows we'd need objdump and i686-pc-mingw32-objdump, and more to
+cover a.out, COFF and 64 bit Windows. Therefore this cannot be done
+inside the daemon, and should be done by a separate, external program
+similar to virt-inspector.
+
+Probably we should go all the way and have virt-inspector able to
+determine kernel and userspace architectures of guests.
+
----------------------------------------------------------------------
Other initrd-* commands, such as:
initrd-extract
initrd-replace
+
+----------------------------------------------------------------------
+
+Control guestfish from a pipe.
+
+For shell scripts - they can start up a long-running guestfish process
+and intermittently send it commands. Avoids the start-up overhead,
+but how do we reliably signal errors?
\ No newline at end of file