Hi,
Hmm... will it break for pbuilder-user-mode-linux create/update ?
COWFILE is not specified for pbuilder-user-mode-linux create and
update, and what would that mean?
In those cases, it should use the /etc/network/interfaces already
configured in the chroot in the UML image. (ie
On Wed, Mar 28, 2007 at 08:16:01AM +0900, Junichi Uekawa wrote:
Hi,
The below patch only overwrites the /etc/network/interfaces in
the chroot if a UML_IP is specified, and refuses to do so when
a COWFILE has not been specified, or if pbuilder-uml.conf has
UML_IP=dhcp
in it.
(You could
Hi,
Hmm. Aren't the variables in this resolved at EOF time, ie
outside the UML? UML_CHROOT_MOUNTPOINT would have the same
issue, otherwise.
Thanks, yes, of course.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL
The below patch only overwrites the /etc/network/interfaces in
the chroot if a UML_IP is specified, and refuses to do so when
a COWFILE has not been specified, or if pbuilder-uml.conf has
UML_IP=dhcp
in it.
Hmm... will it break for pbuilder-user-mode-linux create/update ?
COWFILE is not
On Thu, Mar 29, 2007 at 12:10:03AM +0900, Junichi Uekawa wrote:
The below patch only overwrites the /etc/network/interfaces in
the chroot if a UML_IP is specified, and refuses to do so when
a COWFILE has not been specified, or if pbuilder-uml.conf has
UML_IP=dhcp
in it.
Hmm... will it
Hi,
The below patch only overwrites the /etc/network/interfaces in
the chroot if a UML_IP is specified, and refuses to do so when
a COWFILE has not been specified, or if pbuilder-uml.conf has
UML_IP=dhcp
in it.
(You could change it to be UML_IP= if you change ${UML_IP} != 'dhcp'
to be -n
6 matches
Mail list logo