2 ----------------------------------------------------------------------
4 All action functions are generated automatically, so there are only
5 two files you need to edit:
7 (1) src/generator.ml: Add your new action, parameters, description,
8 etc. to the big list called 'functions' at the top of this file.
10 (2) Edit/create a C file in daemon/ subdirectory which implements your
11 'do_action' function. Take a look at one of the numerous examples
14 You will need to run src/generator.ml (from the top directory) which
15 regenerates all the auto-generated files, and then continue with the
16 ordinary build process.
18 PLEASE LOOK AT THE TOP OF EACH FILE BEFORE EDITING to see whether it
19 is automatically generated or not.
22 ----------------------------------------------------------------------
24 Try to use GNU / Emacs default formatting, following the convention
25 used elsewhere in the source.
27 Please make sure that the code compiles without warnings.
29 Please test any changes.
32 ----------------------------------------------------------------------
35 The daemon that runs inside the guest and carries out actions.
41 Guestfish (the command-line program / shell)
44 Some guest images to test against. These are gzipped to save
45 space. You have to unzip them before use.
48 M4 macros used by autoconf.
60 Source code to the C library.
61 Also contains the crucial generator program.
64 ----------------------------------------------------------------------
66 It's a good idea to use guestfish to try out new commands.
68 Debugging the daemon is a problem because it runs inside a minimal
69 qemu environment. However you can print messages from the daemon, and
70 they will show up if you use 'guestfish -v'.
73 ----------------------------------------------------------------------
75 Submit patches to the fedora-virt mailing list:
76 http://www.redhat.com/mailman/listinfo/fedora-virt
77 and CC to rjones@redhat.com