Commit Graph

10 Commits

Author SHA1 Message Date
Christoph Moench-Tegeder 6f6e58f4ae explicitly test the hostname we'll be setting
getent queries the system resolver for the hostname - but it's not
the resolver we're interested in. In fact, the hostname-to-be-set
may already exist in DNS (becuase DNS really is a nifty thing and
can do a lot of things which are not that possible with /etc/hosts
alone), in which case getent will "not fail" and vagrant will believe
the hostname had already been set.
Instead, query hostnamectl for the "static" hostname - that's the
one we will be setting, so we're ok IFF hostnamectl returns exactly
what we would be setting.
2019-11-01 15:41:04 +01:00
Gregor Dschung 8442b6b59f Use hostnamectl instead of hostname to set the hostname under SUSE 2019-10-03 14:46:14 +02:00
Matthias Haag a139dd2b59 use basename for setting hostname 2017-11-22 11:09:51 +01:00
Chris Roberts e62d71b645 Remove comment removal from /etc/hosts file on guests
Fixes: #7794
2017-04-20 17:07:56 -07:00
Seth Vargo cf91bcf029
guests: Always search for FQDN without sudo 2016-07-18 21:12:54 -04:00
Seth Vargo b091f4fe82
guests/suse: Change host name in one command 2016-06-06 11:58:41 -04:00
Mitchell Hashimoto d04ec704c1 update CHANGELOG 2014-10-23 10:12:27 -07:00
Thomas Boerger 063a903bdb Fixed and extended suse guest capabilities
In order to get a SUSE guest running and installing fine i have added a
correct capability for installing rsync and nfs-client.

I have included SUSE naming fixes as well because SUSe doesnt get
spelled SuSE anymore :).
2014-09-11 17:07:49 +02:00
Deepak Seshadri 497ebb0f72 Fix setting persistent hostname on SLES guests. 2013-05-31 19:31:43 +10:00
Mitchell Hashimoto 439499fc11 Solaris capabilities 2013-04-04 12:25:10 -07:00