** Changed in: dhcp3 (Ubuntu)
Status: New = Confirmed
** Changed in: dhcp3 (Ubuntu)
Importance: Undecided = Wishlist
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: dhcp3 (Ubuntu)
Status: New = Confirmed
** Changed in: dhcp3 (Ubuntu)
Importance: Undecided = Wishlist
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
Bugs, which
Some of our workstations have a problem with switches that take a while before
the link is up (span-tree), which makes the nis client start before the
interface is completely up even if you set nis to start at S99 in rc2.d. A
simple solution is to add the following file to /etc/network/if-up.d
Some of our workstations have a problem with switches that take a while before
the link is up (span-tree), which makes the nis client start before the
interface is completely up even if you set nis to start at S99 in rc2.d. A
simple solution is to add the following file to /etc/network/if-up.d
Of course the script should not overwrite modifications done by the
user. If Debian doesn't allow to use a comment line tag like # DO NOT
EDIT THIS FILE, or remove this line, then you could store the md5sum of
yp.conf somewhere to check for user modifications on the next run. If
the md5sum file
Yes, the md5sum approach is what some other packages use - but ideally
there wouldn't be the all or nothing and it'd only be applied to a file
included from the main confiugration.
The other part of this bug was to get those options added to the default
dhclient.conf so this would all work out of
Of course the script should not overwrite modifications done by the
user. If Debian doesn't allow to use a comment line tag like # DO NOT
EDIT THIS FILE, or remove this line, then you could store the md5sum of
yp.conf somewhere to check for user modifications on the next run. If
the md5sum file
Yes, the md5sum approach is what some other packages use - but ideally
there wouldn't be the all or nothing and it'd only be applied to a file
included from the main confiugration.
The other part of this bug was to get those options added to the default
dhclient.conf so this would all work out of
You're missing the point with laptops and so on: these are use cases
that are already supported and can be broken by a poor DHCP
implementation. This is especially the case if your preferred
implementation with overwriting the configuration file were done - the
user configuration would be
You're missing the point with laptops and so on: these are use cases
that are already supported and can be broken by a poor DHCP
implementation. This is especially the case if your preferred
implementation with overwriting the configuration file were done - the
user configuration would be
Mark Brown wrote:
It's not quite that simple - people use NIS on computers which move
between networks, such as laptops, and run multiple NIS domains on the
same network (which means that any DHCP configuration will only apply to
some systems). This makes it difficult to tell if the
If the discussion is going on in Launchpad it's pretty much Ubuntu-
specific. Note that I'm the Debian NIS maintainer; it's unlikely that
I'll do anything directly with the Ubuntu packages.
No Debconf *note* (they're deprecated) but possibly a low priority
question offering to enable the option
Mark Brown wrote:
If the discussion is going on in Launchpad it's pretty much Ubuntu-
specific. Note that I'm the Debian NIS maintainer; it's unlikely that
I'll do anything directly with the Ubuntu packages.
A fix in Debian is fine for me. If its available in Debian, then it is
just a matter
It's not quite that simple - people use NIS on computers which move
between networks, such as laptops, and run multiple NIS domains on the
same network (which means that any DHCP configuration will only apply to
some systems). This makes it difficult to tell if the configuration on
the network
Mark Brown wrote:
It's not quite that simple - people use NIS on computers which move
between networks, such as laptops, and run multiple NIS domains on the
same network (which means that any DHCP configuration will only apply to
some systems). This makes it difficult to tell if the
Yes, a Debconf note would be the way forward, though it'd have to be a
low priority one. Note that I'm mostly talking about enabling this on
upgrade here - new systems are a bit different since you won't damage
anyone's running system.
Given that this is Launchpad I'd presume that any discussion
Yes, a Debconf note would be the way forward, though it'd have to be a
low priority one. Note that I'm mostly talking about enabling this on
upgrade here - new systems are a bit different since you won't damage
anyone's running system.
Given that this is Launchpad I'd presume that any discussion
You mean you would accept dhcpd's nis options for new installs by
providing a client script, and provide a debconf note pointing to the
change on an upgrade? I could live with that.
I am not sure that this discussion is Ubuntu-only. In general I would
suggest to keep Debian and Ubuntu in sync,
Usually root can always login to fix things on the console, unless you
explicitly disable root login, and rely upon an unprivileged user
running sudo, as Ubuntu does. So your system non-functional argument
is surely a home-made problem.
Maybe it would be possible to introduce some debconf menu to
Usually root can always login to fix things on the console, unless you
explicitly disable root login, and rely upon an unprivileged user
running sudo, as Ubuntu does. So your system non-functional argument
is surely a home-made problem.
Maybe it would be possible to introduce some debconf menu to
** Changed in: nis (Debian)
Status: Unknown = New
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs
** Bug watch added: Debian Bug tracker #456299
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456299
** Also affects: nis (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456299
Importance: Unknown
Status: Unknown
--
nis package must provide DHCP client scripts
** Changed in: nis (Debian)
Status: Unknown = New
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: nis (Ubuntu)
Status: New = Confirmed
** Also affects: dhcp3 (Ubuntu)
Importance: Undecided
Status: New
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
After I filed this I realized there was no facility for updating
dhclient.conf via dpkg scripting, so I also filed bug #246343 to have
these fields added to the dhclient.conf request line by default. It
won't hurt anything to have them requested there: if they're not
available from the server
Thank you for your suggestion. However, the changes you are requesting
aren't really a bug and require more discussion, which should be done on
an appropriate mailing list or forum. [WWW]
http://www.ubuntu.com/support/community/mailinglists might be a good
start for determining which mailing list
This seems like a perfectly valid wishlist bug which I'd have expected
to see forwarded on to Debian at least (I am the Debian NIS maintainer).
FWIW this is more complicated than the report suggests. For example,
it'd need to be optional and off by default like the similar
configuration for WINS
** Changed in: nis (Ubuntu)
Importance: Undecided = Wishlist
Status: Invalid = New
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: nis (Ubuntu)
Status: New = Confirmed
** Also affects: dhcp3 (Ubuntu)
Importance: Undecided
Status: New
--
nis package must provide DHCP client scripts
https://bugs.launchpad.net/bugs/246322
You received this bug notification because you are a member of Ubuntu
After I filed this I realized there was no facility for updating
dhclient.conf via dpkg scripting, so I also filed bug #246343 to have
these fields added to the dhclient.conf request line by default. It
won't hurt anything to have them requested there: if they're not
available from the server
The main reason to be extra careful with this sort of setup is that
messing up NIS can prevent users logging in to their system which is
obviously an extremely serious issue for upgrades since it could render
the system non-functional. This means that we need to be very
conservative about changes
31 matches
Mail list logo
