[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> From: Rainer Dorsch <[EMAIL PROTECTED]>
> Subject: Re: New install / loopback device
> To: [EMAIL PROTECTED]
> Date: Wed, 14 Jun 2000 09:55:45 +0200
> Resent-From: [EMAIL PROTECTED]
>
>
> > > but the new system has no network file. Interestingly the network file
> > > is not known on the upgraded system:
> > > rainer@rakete:~$ dpkg -S /etc/init.d/network
> > > dpkg: /etc/init.d/network not found.
> >
> > /etc/init.d/network has never been known by dpkg, btw, it used
> > to be created by boot-floppies, and never touched after. Now it's
> > /etc/network/interfaces instead. See the manpages referenced above.
>
> Thanks for the quick reply. It seems that all the upgraded systems use
> /etc/init.d/network, e.g.
>
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
> IPADDR=129.69.183.16
> NETMASK=255.255.255.0
> NETWORK=129.69.183.0
> BROADCAST=129.69.183.255
> GATEWAY=129.69.183.254
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> route add -net ${NETWORK}
> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
>
> Is the user supposed to migrate the settings manually from /etc/init.d/network
> to /etc/network/interfaces?
Yes, take a look at /var/lib/dpkg/info/netbase.postinst. The netbase
maintainer decided (wisely, IMHO) not to attempt to handle this
automatically.
As I read that postinst, that file should have some info added to it
on how to manually do the migration.
> If yes, this should be documented in the upgrade release notes.
I agree.
--
.....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
