On Sat, 23 Sep 2000, Tom Hoover wrote:
> Is there any advantage to building the kernel outside of fakeroot?
The fakeroot man page says quite clearly that "Thou shall never configure a
anything under fakeroot", so I try to only do the install targets under
fakeroot to avoid hard-to-track problems.
On Sat, Sep 23, 2000 at 06:57:48PM -0300, Henrique M Holschuh wrote:
>
> I don't know. What I could suggest you to do is this:
>
> make-kpkg --revision... build
> fakeroot make -f debian/rules kernel-image-deb
> fakeroot make-kpkg modules_image
>
> The above sequence has never failed me. It buil
On Sat, Sep 23, 2000 at 07:11:23PM -0300, Henrique M Holschuh wrote:
> On Sat, 23 Sep 2000, Henrique M Holschuh wrote:
> > > Am I misreading the docs?
> > I don't know. What I could suggest you to do is this:
>
> Well, now I know. The make-kpkg man page makes it very clear that the only
> target
On Sat, 23 Sep 2000, Henrique M Holschuh wrote:
> > Am I misreading the docs?
> I don't know. What I could suggest you to do is this:
Well, now I know. The make-kpkg man page makes it very clear that the only
target which knows how to deal with rootcmd is buildpackage. I never use it,
though. I
On Sat, 23 Sep 2000, Tom Hoover wrote:
> I've successfully built a new kernel package with make-kpkg, but only if I
> use:
>
> fakeroot -- make-kpkg --revision=custom.X.XX. kernel_image
I'll usually run fakeroot make-kpkg ... I've never needed that --
> Am I misreading the docs?
On Sat, Sep 23, 2000 at 07:30:19AM -0700, Nuhn Yobiznez wrote:
>
> Debian is great for newbie kernel building
> because it has a wonderful package called kpkg. This
> package does ALMOST everything for you! I highly
> recommend doing an apt-get for it! It simplifies the
> process to the point
--- "John C. Plummer" <[EMAIL PROTECTED]> wrote:
>Thanks to Nuhn, Tom, John and Andrew for your
> responses. Here's how it has progressed: uname
> indicates a 2.2.12 kernel. The existing source is
> in
> /usr/src/kernel-headers-2.2.12/include. The apt-
> get as Nuhn suggested created a set
Hi,
my suggestion is that you do what other helpful
souls have already said:
uname -r (or a for the full listing)
to find which kernel you're running.
And then get online go to a prompt and type
apt-get install kernel-source.2.2.XX
After that installs you should find
kernel-source.
Hi,
my suggestion is that you do what other helpful
souls have already said:
uname -r (or a for the full listing)
to find which kernel you're running.
And then get online go to a prompt and type
apt-get install kernel-source.2.2.XX
After that installs you should find
kernel-source.
Tom Pfeifer wrote:
> The precompiled VMware modules should be located in:
> /usr/lib/vmware/modules/binary
Of course, they have to be located in /lib/modules/2.2.XX/misc at run
time. The VMware installation should normally put them there during the
install.
Here's what you should see there: (on
I'd guess (maybe incorrectly) that you are running a newer version of
the kernel than 2.2.12, because the latest release of VMWare for Linux
(2.02, build 621) has precompiled modules for kernels up to 2.2.15
including 2.2.12. So if you are actually running 2.2.12, then VMware
should have just used
On Wed, Sep 20, 2000 at 05:29:12PM -0400, John C. Plummer wrote:
> When it asked for the
> headers location I gave it /usr/src/kernel-headers-2.2.12.
Make sure this is the kernel you have. The command `uname -r` will
tell you which kernel you are using. Make sure this is the headers
you have.
O
Hi,
Found in the archives that others have loaded vmware on Debian 2.2
w/o too much difficulty.
But I had one small problem trying with the install of the current
release for Linux. It did not
find any prebuilt vmnet modules that worked and wanted to build one.
When it asked for the
headers lo
13 matches
Mail list logo
