Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-25 Thread Tim Heckman
On Fri, Nov 25, 2011 at 7:25 PM, Andrew Pollock wrote: > On Fri, Nov 25, 2011 at 01:25:39AM -0500, Tim Heckman wrote: > > On Thu, Nov 24, 2011 at 11:06 PM, Andrew Pollock >wrote: > > > > > > I've actually been poking at this some more, and it turns out

Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-24 Thread Tim Heckman
On Thu, Nov 24, 2011 at 11:06 PM, Andrew Pollock wrote: > > I've actually been poking at this some more, and it turns out I've made a > grave error in assuming that by not requesting a particular option you > don't > get it anyway. > > It turns out in testing, that even not requesting the host-name

Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-24 Thread Tim Heckman
On Tue, Nov 22, 2011 at 11:06 PM, Andrew Pollock wrote: > On Sun, Nov 20, 2011 at 07:06:52PM -0500, Tim Heckman wrote: > [snip] > > > > Andrew, > > > > Thanks for the information about how it'll be implemented moving forward. > > Not to shy too far off

Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-20 Thread Tim Heckman
On Sun, Nov 20, 2011 at 5:56 PM, Andrew Pollock wrote: > 4.2.2-2 is going to stop requesting the host-name option by default. I > don't > feel that dhclient-script should be making implicit assumptions by looking > at the state of the system, it should only do what it is explicitly > configured t

Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-20 Thread Tim Heckman
On Sun, Nov 20, 2011 at 12:22 AM, Andrew Pollock wrote: > > dhclient-script got some major overhauling in 4.2.2-1, and your patch is no > longer applicable. > > Is the original bug still present in 4.2.2-1? > > regards > > Andrew Andrew, It does appear to work normally in 4.2.2-1 on Sid. Howev

Bug#609851: hostname.sh patch for dhclient-script patch

2011-11-03 Thread Tim Heckman
Once the dhclient-script has been accepted I'll be opening a bug on the "initscripts" package to ensure hostname.sh is updated. Was posting the diff here to ensure the change needing to be made was noted with a fix. -Tim

Bug#609851: hostname.sh patch for dhclient-script patch

2011-11-03 Thread Tim Heckman
e)" @@ -28,6 +28,9 @@ # And set it to 'localhost' if no setting was found [ -z "$HOSTNAME" ] && HOSTNAME=localhost + # Or set to localhost if hostname is "(none)" + [ "$HOSTNAME" = "(none)" ] && HOSTNAME=localhost + [

Bug#609851: [updated] incorrect variables used to set hostname in dhclient-script

2011-11-02 Thread Tim Heckman
uot; -a -n "$host_name" -a \ - "$host_name" != "$old_host_name" ]; then -hostname "$new_host_name" + if [ ! -s /etc/hostname ]; then + # /etc/hostname > 0 set hostname + hostname "$new_host_name" fi if [ -n "$ol

Bug#609851: isc-dhcp NMU dhclient-script patch

2011-11-02 Thread Tim Heckman
dress" -a -n "$alias_ip_address" -a \ The hostname.sh issue isn't critical, but it's still a bit unsettling to see init scripts unhappy at boot. I'll work on something for "/etc/init.d/hostname.sh" so that it doesn't fail on boot. Things just can't be easy, can they? Tim Heckman dhclient-script.diff Description: Binary data