| 1 |
On Mon, 1 Nov 2010, Ladislav Laska wrote: |
| 2 |
|
| 3 |
> thanks for your reply. This is what I suspected, but I don't use NM |
| 4 |
> and don't recall that any of my networks try to set my hostname (I |
| 5 |
> connect only to a dorm network, and eduroam, sometimes some dnsmasq |
| 6 |
> driven lan). |
| 7 |
> |
| 8 |
> I have no idea who tries to set my hostname and will investigate it |
| 9 |
> (it really seems that setting my hostname to empty string is the |
| 10 |
> cause, but still I don't know why. One idea is that something is |
| 11 |
> corrupting my memory (I would point at i915 driver, but don't really |
| 12 |
> have time for debugging). |
| 13 |
|
| 14 |
The DHCP client itself can obey instructions from the LAN to do this. |
| 15 |
There are options in most of them to set it locally. Most DHCP networks |
| 16 |
assign really long obnoxious hostnames to clients, so you can end up |
| 17 |
seeing these names at your shell prompt sometimes if you don't override |
| 18 |
it yourself. |
| 19 |
|
| 20 |
-- |
| 21 |
+ Brent A. Busby + "We've all heard that a million monkeys |
| 22 |
+ UNIX Systems Admin + banging on a million typewriters will |
| 23 |
+ University of Chicago + eventually reproduce the entire works of |
| 24 |
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet, |
| 25 |
+ James Franck Institute + we know this is not true." -Robert Wilensky |
Archives