On 06/14/2011 04:06 AM, Lennart Poettering wrote:
On Mon, 13.06.11 19:02, Denys Vlasenko (dvlasenk(a)redhat.com) wrote:
> On Mon, 2011-06-13 at 12:37 -0400, Simo Sorce wrote:
>> On Mon, 2011-06-13 at 18:01 +0200, Denys Vlasenko wrote:
>>>> We invoke sethostname() from inside systemd since that is one of the
>>>> most trivial system calls known to men and doing this with a
>>> separate
>>>> binary is just absurd. This way we also can ensure that the hostname
>>> is
>>>> always initialised which is very useful for early boot logging and
>>> other
>>>> stuff. On systemd you get the guarantee that the hostname is always
>>> set
>>>> up if you run in userspace,
>>> You can't possibly know what kind of (possibly dynamic) hostname
>>> admin might want to assign to his machine. The static hostname
>>> may be as useless as default "(none)" which is set by kernel.
>>> Anyway, logging with default hostname is not a catastrophe.
>>>
>>> Why do you set up stuff no one asked you to?
>> Changing a machine hostname at random times is just asking for trouble.
> I just tried it. So far flames don't shoot out of my notebook.
Wow, that's convincing proof.
Lennart
One question - does systemd run /etc/rc.local script?
If not where do I put my own little things I want to happen at boot up.
--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark(a)netwolves.com
http://www.netwolves.com