*- On 3 Oct, Brian Servis wrote about "RE: make-kpkg and apt-get updates"
> *- On 3 Oct, peter karlsson wrote about "RE: make-kpkg and apt-get updates"
>>> kernel-package is the way to go. Name your revisions like
>>> .-, and you'll not have problem
*- On 3 Oct, peter karlsson wrote about "RE: make-kpkg and apt-get updates"
>> kernel-package is the way to go. Name your revisions like
>> .-, and you'll not have problems
>> (I haven't, anyway :)
>
> One problem is how do I have several compila
> kernel-package is the way to go. Name your revisions like
> .-, and you'll not have problems
> (I haven't, anyway :)
One problem is how do I have several compilations of the same kernel version
installed? Right now, I have two 2.2.12 compilations installed, for
instance. How do I do that with m
On Sun, 3 Oct 1999, Darxus wrote:
: On Sat, 2 Oct 1999, peter karlsson wrote:
:
: > > you can use dselect and use "H" on the package. This will hold the
package
: > > and prevent "accidental" upgrading.
: >
: > Yeah, but that's not a very good solution, especially since I need to
: > rem
On Sat, 2 Oct 1999, peter karlsson wrote:
> > you can use dselect and use "H" on the package. This will hold the package
> > and prevent "accidental" upgrading.
>
> Yeah, but that's not a very good solution, especially since I need to
> remember to do that manually each time I compile a new kerne
On Sat, Oct 02, 1999 at 09:43:30PM +0200, peter karlsson wrote:
> > Use epochs for your revision= when using make-kpkg:
> > make-kpkg --revision=1:custom.1.0 kernel_image
> > (see /usr/doc/kernel-package/README.gz)
>
> Hmm, sounds good. Any way to get it to do that without me having to remember
>
> Use epochs for your revision= when using make-kpkg:
> make-kpkg --revision=1:custom.1.0 kernel_image
> (see /usr/doc/kernel-package/README.gz)
Hmm, sounds good. Any way to get it to do that without me having to remember
to add that each time? I couldn't find any parameter I could put in the
conf
> you can use dselect and use "H" on the package. This will hold the package
> and prevent "accidental" upgrading.
Yeah, but that's not a very good solution, especially since I need to
remember to do that manually each time I compile a new kernel.
Plus that I have to go into dselect, which I don'
-BEGIN PGP SIGNED MESSAGE-
On Sat, 2 Oct 1999, peter karlsson wrote:
> I compiled and installed a kernel with make-kpkg, but now apt-get seems to
> want to overwrite it with one from the archive. I do not want that to
> happen, how do I tell apt-get to keep its hands off it?
I always giv
Use epochs for your revision= when using make-kpkg:
make-kpkg --revision=1:custom.1.0 kernel_image
(see /usr/doc/kernel-package/README.gz)
On Sat, Oct 02, 1999 at 02:57:39PM +0200, peter karlsson wrote:
> I compiled and installed a kernel with make-kpkg, but now apt-get seems to
> want to overwr
y, October 02, 1999 7:58 AM
> To: debian-user@lists.debian.org
> Subject: make-kpkg and apt-get updates
>
>
> I compiled and installed a kernel with make-kpkg, but now apt-get seems to
> want to overwrite it with one from the archive. I do not want that to
> happen, how do I tell ap
I compiled and installed a kernel with make-kpkg, but now apt-get seems to
want to overwrite it with one from the archive. I do not want that to
happen, how do I tell apt-get to keep its hands off it?
--
\\//
peter - http://www.softwolves.pp.se/
- and God said: nohup make World >& World.log
12 matches
Mail list logo
