On 1 April 2015 at 10:57, Antti Kantee <[email protected]> wrote: > On 01/04/15 09:26, Justin Cormack wrote: >> >> I am at the stage with frankenlibc that I need to set up configuration. >> >> The big problem with configuration seems to be that the different >> implementations have very different access to configuration >> information. Xen has xenstore, which is a generic key-value store, >> userspace has some arrangement of files and block devices, while bare >> metal does not have much at all, although some platforms might have >> some persistent flash. > > > The idea was that the rumprun utility would create the configuration which > would then be interpreted at runtime by the rumpconfig module, like what > mato already implemented for Xen. I don't think deciding the actual > mechanism matters that much, since it can even be changed without the user > noticing. The user interface provided by the rumprun utility still needs > work and discussion and review.
I think it does matter in terms of configuration management. If the binary is being modified you may want to store the new version somewhere, or generate it before running it and run the preconfigured version. Deleting unused config files and so on, whether from xenstore or the file system is also necessary. In terms of the utility, the obvious to me missing stuff is: 1. set mac address 2. inet6,auto config 3. inet6,static config. May need multiple addresses, and I guess auto and static together are valid. 4. setting name servers 5. is the assumption that the "environment variable" mechanism is used to set custom info eg crypto keys? 6. setting fqdn, at the moment there is a name field, but we dont sethostname/setdomainname on host, although rump will make up a hostname. 7. support for mounts of other devices. The main thing missing here is to specify the fs type, rather than have it autodetected, eg for pci device mounts, or /proc or /tmpfs. Some way to specify netbsd per filesystem mount options (eg tmpfs size) would be useful eventually. You still need more generic mechanisms, which is why I think some generic discussion is useful. eg if you want to configure a packet filter you are not going to do it from command line options. Justin
