On Tue, Jun 19, 2001 at 06:50:33PM -0300, John R Lenton wrote:
>
> make-kpkg takes care of all that for you (it's part of kernel-package)
It does. But only for Debian users like you and me.
Regards,
Anuradha
--
Penguin : Linux 2.4.6-pre5 on an i586
"Language shapes the way we think, and de
On Tue, Jun 19, 2001 at 04:55:10PM -0400, Tom Diehl wrote:
> On Tue, 19 Jun 2001, Alan Cox wrote:
>
> > Other than making sure you configure it for the box it will eventually run
> > on - nope you have it all sorted. If you use modules you'll want to install
> > the modules on the target machine
"McHarry, John" wrote:
>
> I am trying to compile the 2.2.19 kernel one one machine for installation
> on another. I believe I need to do more than just copy over bzImage and
> modify lilo.conf, but I don't know what. Is there documentation somewhere
> on how to do this? Thanks.
This is eno
On Tue, Jun 19, 2001 at 10:23:47PM -0400, John Weber wrote:
> On a related note... is System.map also necessary? Anyone care to explain
Debugging. ksymoops and klogd can both make use of it.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us liv
Alan Cox wrote:
>>I am trying to compile the 2.2.19 kernel one one machine for installation
>>on another. I believe I need to do more than just copy over bzImage and
>>modify lilo.conf, but I don't know what. Is there documentation somewhere
>>on how to do this? Thanks.
>>
>
> Other than ma
the 'compile in one place and export the product via nfs' mentality
really kicks in under *bsd, where you may have a server farm and want to
upgrade all at once...the tarball idea works for one machine, but for
multiples, its all about exporting it... just my 2 cents. --gabe
,[ On Tue, Jun 1
Gabriel Rocha wrote:
> you could always compile on one machine and nfs mount the /usr/src/linux
> and do a make modules_install from the nfs mounted directory...
The way I've always managed this sort of thing is to tar up your kernel source,
transfer it to the "compile box" however you please, t
On Tue, Jun 19, 2001 at 04:45:24PM -0500, Eli Carter wrote:
> Gabriel Rocha wrote:
> > you could always compile on one machine and nfs mount the /usr/src/linux
> > and do a make modules_install from the nfs mounted directory...
>
> Which would require exporting that filesystem with root permissio
hey, how and where you export the filesystem is an exercise left for the
reader, i have no problem exporting nfs filesystems in my internal
network, what you do or dont, is up to you. and there is always
cfs...
,[ On Tue, Jun 19, at 04:45PM, Eli Carter wrote: ]--
| Gabriel Rocha w
Quoting Tom Diehl <[EMAIL PROTECTED]> from ml.linux.kernel:
:What is the best way to install the modules? Is there a directory _all_ of
:the modules exist in b4 you do "make modules_install". I usually end up
:setting EXTRAVERSION to something unique and doing a make modules_install.
:That way it
On Tue, Jun 19, 2001 at 04:55:10PM -0400, Tom Diehl wrote:
> What is the best way to install the modules? Is there a directory _all_ of
> the modules exist in b4 you do "make modules_install". I usually end up
> setting EXTRAVERSION to something unique and doing a make modules_install.
> That way
-Original Message-
From: Tom Diehl [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 4:55 PM
To: [EMAIL PROTECTED]
Subject:Re: How to compile on one machine and install on another?
On Tue, 19 Jun 2001, Alan Cox wrote:
> Other than making sure you configure
On Tue, 19 Jun 2001, Alan Cox wrote:
> Other than making sure you configure it for the box it will eventually run
> on - nope you have it all sorted. If you use modules you'll want to install
> the modules on the target machine too
What is the best way to install the modules? Is there a director
I am trying to compile the 2.2.19 kernel one one machine for installation
on another. I believe I need to do more than just copy over bzImage and
modify lilo.conf, but I don't know what. Is there documentation somewhere
on how to do this? Thanks.
-
To unsubscribe from this list: send the line
14 matches
Mail list logo
