> "Manoj" == M C Vernon <[EMAIL PROTECTED]> writes:
Chad> My personal guidelines (and really, I hope all that one would
Chad> need to know) exist in /usr/doc/kernel-package/README.gz. I have
Chad> included in there a step by step process to creating kernel
Chad> packages. If I have missed some
On 15 Sep 1998, Manoj Srivastava wrote:
> Hi,
> >>"Chad" == Chad Walstrom <[EMAIL PROTECTED]> writes:
>
> Chad> No, I haven't R-all-TFM's out there, but I'm getting burnt out
> Chad> on 'em. So, I'd like to hear a little about what some of you
> Chad> do personally to keep track of things. W
Hi,
>>"John" == John Larkin <[EMAIL PROTECTED]> writes:
John> I'd say "Don't touch them. Ever." is a bit harsh.
No, it is the only technically correct thing to
do. Unfortunately, it also seems to be something very few people
think through, and very often one sees incorrect information
> > Chad> .deb-installed headers from the /usr/include directory.
> >
> > Ans rightly so. Don't touch them. Ever.
> ^
> My question is what if one wants to upgrade the kernel
> from non-debian sources? Do we still use the old kernel
> headers from t
On 15 Sep 1998, Manoj Srivastava wrote:
> Hi,
> >>"Chad" == Chad Walstrom <[EMAIL PROTECTED]> writes:
>
> Chad> No, I haven't R-all-TFM's out there, but I'm getting burnt out
> Chad> on 'em. So, I'd like to hear a little about what some of you
> Chad> do personally to keep track of things.
Hi,
>>"Chad" == Chad Walstrom <[EMAIL PROTECTED]> writes:
Chad> No, I haven't R-all-TFM's out there, but I'm getting burnt out
Chad> on 'em. So, I'd like to hear a little about what some of you
Chad> do personally to keep track of things. What you like to do to
Chad> back up old kernels, etc
6 matches
Mail list logo
