Re: Dselect reinstalls kernel
On a similar topic, I notice that if I do a --revision.1.0 and later a
--revision.2.0, that the --revision.1.0 still shows up as being installed.
Is there a way to remove it without causing problems with 2.0, since there
is only one /lib/modules/2.x.x directory? I got arount this by cp'ing the
modules to a temporary name, but is there a better way (like getting dpkg
to remove the first when the second is installed?)
Bob
On Fri, 29 Jan 1999, Hamish Moffatt wrote:
> On Wed, Jan 27, 1999 at 03:43:55PM -0600, Nathan E Norman wrote:
> > As someone else suggested, be sure to use the `--revision=foo' option to
> > make-kpkg, and that should solve the problem. It's never failed me
> > here.
>
> But depending on what you make your --revision, dselect might still
> upgrade it. I suggest using something like --revision=2:1.00. There's
> ~0% chance dselect will ever upgrade that.
>
>
> Hamish
> --
> Hamish Moffatt VK3TYD hamish@debian.org, hamish@rising.com.au
> Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
> CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
----
Bob Nielsen Internet: nielsen@primenet.com
Tucson, AZ AMPRnet: w6swe@w6swe.ampr.org
DM42nh http://www.primenet.com/~nielsen
Reply to: