On 13/11/14 18:57, Martin Lucina wrote:
Also, I'd prefer to call it 'stubetc' rather than 'etc' to make it clearer
that it's not supposed to be used as a normal /etc.
I'd prefer it to be completely hidden from the user. But sure, call it
stubetc for now.
This brings up another question; what to do with resolv.conf, for example?
Is resolv.conf an example, i.e. are there other files with similar
needs? Or can we figure out how to handle it as a special case?
Can't think of any. Went and looked in /etc on my laptop to see if anything
of note gets modified regularly and found nothing besides resolv.conf.
If we want to go down the route of not having a user-visible /etc at all
(which I think is a good idea) then perhaps we could modify the libc
resolver to add an API to set the DNS servers directly, which the
rumpconfig and/or dhcp stuff can call.
user-visible != internally visible. We can for example build /etc into
the image as data and mount it as a memory file system at runtime or
symlink /etc/resolv.conf to /resolv.conf. I'd completely avoid
modifying libc until there's a better understanding of the role of /etc
with experience from dozens of varying applications. Modifying over
upstream is a balancing act, because then we stop getting the
*pre-tested* code for free.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
