>> I think you yourself quite well demonstrated how "this might work" is not >> very convincing ;)
OK I haven’t convinced you as yet but I’ll work on it. Is there an alternate way for me to get json.cfg into the kernel? Maybe going back to compiling it in would be the best solution - that worked pretty well. It’s just far too time consuming and hard to be trying to get the kernel to mount an ext2 volume in EC2 HVM to get the network configured - I’m burning days that I don’t have just trying to read json.cfg and I still haven’t made it work. I’m completely blind as to what is going on when the rump kernel boots because at the moment it appears that HVM doesn’t write to the console/system log in the same way as paravirtual hosts do on EC2 (i.e. not at all) so until I solve that I can’t even see what’s going wrong in the process of trying to get the kernel to find the disk to get its json.cfg from. So I’m trying to diagnose without even being able to get control of the configuration of the disk and network. Basically just guessing and deducing. Ugh. I’m making progress getting things running on EC2 HVM but life would be dramatically easier if I could compile in the json.cfg or get it in some other way rather than loading it from disk. I’m begging ya! :-) thanks as
