On 01/28/2013 12:47 PM, Alexander Sack wrote:
On Mon, Jan 28, 2013 at 7:37 PM, Michael Hudson-Doyle
<[email protected]> wrote:
>Paul Sokolovsky<[email protected]> writes:
>
>>I tried to investigate how it happened that lava-dispatcher doesn't try
>>to set hostname, and actually found it used to, but that was tied to
>>recognition of test prompts, and once that was refactored, setting
>>hostname also gone, see
>>http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revision/402
>>(grep for "_customize_ubuntu" - it got factored out to another file,
>>and lost /etc/hostname setting in progress).
>>
>>So, please let me know if the above makes sense, and should be files as
>>lava-dispatcher bug, or are there other reasons for not setting a
>>hostname.
>
>Seems reasonable. Do you want hostname set to the device name
>("panda01") or just something generic? Previously the dispatcher just
>set it to "linaro" I think...
I'd vote for the device name, ie panda01. Seems the most useful and unique.
I don't feel we should start encoding anything useful into the
hostname that doesn't help LAVA to reliably match the prompt.
Think prompt and hostname are orthogonal. We (LAVA) set the prompt to
something very specific. It just so happens a default Ubuntu prompt
normally includes the hostname in it.
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
