Re: Upgrading to hamm
No there were no modutils.dpkg* after the upgrade, strange, since modules was not a symlink, it was
the actual file...
On Wed, Aug 05, 1998 at 01:15:33PM -0400, Michael Stone wrote:
> Quoting Javier Fdz-Sanguino Pen~a (firstname.lastname@example.org):
> > The problem is, in Debian 1.3 the script /etc/init.d/boot would call
> > the script to do this, and would allow either /etc/init.d/modutils or
> > /etc/init.d/modules. But in hamm, the script is run like any other script in
> > /etc/init.d by a symlink in /etc/rcS.d, the point is the symlink was made to
> > /etc/init.d/modutils NOT /etc/init.d/modules, and modutils was NOT provided
> > by the packages (whomever they are :)
> On my bo system, the modutils package has /etc/init.d/modutils as a conf
> file and /etc/init.d/modules as a link to /etc/init.d/modutils. What I
> don't understand is what happened to your original
> /etc/init.d/modutils--that's why I asked about it. Was there a
> /etc/init.d/modutils.dpkg-* after your hamm upgrade?
> Michael Stone, Sysadmin, ITRI PGP: key 1024/76556F95 from mit keyserver,
> email@example.com finger, or email with "Subject: get pgp key"
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com