[15:49:31]  dcantrell: 506384 [15:50:16]  hello :D [15:52:02]  excellent [15:53:20]  it's not a dupe, but I wouldn't close it as notabug.  it needs to go to another package, perhaps setup [15:57:07]  ok [15:57:11]  I'll send it to them, then [16:00:09]  initscripts gets involved, NetworkManager, anaconda, setup, and so on [16:00:41]  Yep, said we no longer write to /etc/hosts due to other bug, sent on [16:13:59]  dcantrell: but it can't be setup's job since setup just has a static file [16:14:29]  and it can't be networkmanager's job since you need a resolvable internal hostname potentially before networkmanager is started... [16:15:24]  hmm, well maybe that last part isn't true [16:39:17]  ***  alindebe_ (n=alindebe@nat/redhat/x-107bf4397723f236) has joined chat #anaconda. [16:39:30]  ***  alindebe has left chat #anaconda (Nick collision from services.). [16:39:34]  ***  alindebe_ is now known as alindebe. [16:51:20]  halfline: yeah, it's probably not setup that should own it.  unsure about NM owning it or not.  this was a discussion we had last week, but no solution came up.  anaconda is writing out HOSTNAME to /etc/sysconfig/network for now, but not touching /etc/hosts [16:52:37]  dcantrell: probably makes sense for anaconda to write out /etc/hosts after setup is installed [16:53:06]  * alindebe sulks [16:53:17]  coulda had this discussion *before* I started playing ping pong :P [16:55:33]  halfline: for some reason I thought we were doing that at some point (earlier than what happened in 491808) and bugs were opened to change it.  could be wrong [16:57:17]  funky [16:57:45]  maybe code just got rewritten/refactored so the order changed (wrt to setup getting installed) unintentionally [16:57:51]  nonetheless, it's entirely reasonable. [16:57:55]  that's also entirely possible [16:58:13]  alindebe: assign it to me and put it back to anaconda, por favor.  I want to look at this more once I get through my endless to do list [16:58:30]  ok [16:59:25]  halfline: I think I'm getting confused with the bugs that you've opened that go down the path of "what do you want to call the computer?" question rather than just hostname. [17:00:25]  different side of the same issue i guess [17:00:50]  fundamentally, for the computer to function it needs a "hostname" it can resolve locally [17:01:06]  it doesn't necessarily need a name others can resolve [17:01:26]  and the internal hostname doesn't need to make the external hostname [17:01:39]  s/make/match/ [17:02:06]  halfline: right.  adding the hostname entered by the user to the localhost line has caused people to go ape in the past [17:03:14]  I'll take a look at it later though.  so many things to process right now [17:03:27]  probably because there's some app out there that does a lookup on the hostname to figure out which interface to bind to [17:03:50]  which is a totally broken thing to do [17:04:40]  yeah, I seem to remember those reports too.  ah well [17:38:08]  ***  denise has left chat #anaconda (Remote closed the connection). [18:09:29]  ***  rudi (n=rlandman@nat/redhat/x-fc459d79e89f0914) has joined chat #anaconda. [19:00:13]  dcantrell: we switched to writing it out before when we switched to writing out all netconfig before.  which we need for things like root-on-iscsi [19:02:21]  at least that's what my fuzzy memory is saying.  if you want me to add a comment to that effect to the bug in question I can [19:52:58]