public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent C Jones <vcjones@NetworkingUnlimited.com>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.6-rc3
Date: Wed, 28 Apr 2004 15:18:41 -0400	[thread overview]
Message-ID: <20040428191841.GA4449@NetworkingUnlimited.com> (raw)
In-Reply-To: <408FE8C4.33B3BDB4@users.sourceforge.net>

On Wed, Apr 28, 2004 at 08:24:20PM +0300, Jari Ruusu wrote:
> Sam Ravnborg wrote:
> > On Wed, Apr 28, 2004 at 10:48:01AM -0400, Vincent C Jones wrote:
> > >
> > > loop-AES 2.0g has refused to compile since 2.6.6-rc1. No problems up
> > > through 2.6.5. The make script cd's to the kernel source root, then
> > > can't find any of the kernel include files, and it's all downhill from
> > > there...
> > 
> > This is an external module - right?
> > Could you mail me privately the Makefile used, or even better
> > the full package (or link to it).
> 
> Full package:
> http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.0g.tar.bz2
> 
> Patch to fix build problem:
> http://loop-aes.sourceforge.net/updates/loop-AES-v2.0g-20040412.diff.bz2
> 
> New version of loop-AES will be released shortly after final 2.6.6 kernel is
> released.
> 
> -- 
> Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

Thanks much for the quick response. With the loop-AES makefile patched,
loop-AES and 2.6.6-rc3 are happy together.

One last question: Is there a reason there is no mention of the
compile problem or presence of a patch on the loop-AES sourceforge home
page (http://sourceforge.net/projects/loop-aes/)? Or is this common
knowledge that everyone is supposed to know about sourceforge projects?
At least with this thread, Google searches will no longer come up empty.

Now all I need is an APM implementation which suspends while on A/C
power and I can stop playing with kernel releases and concentrate
on work.

Thanks again!

Vince

-- 
Dr. Vincent C. Jones, PE              Expert advice and a helping hand
Computer Network Consultant           for those who want to manage and
Networking Unlimited, Inc.            control their networking destiny
14 Dogwood Lane, Tenafly, NJ 07670
http://www.networkingunlimited.com
VCJones@NetworkingUnlimited.com  +1 201 568-7810  Fax: +1 201 568-7269 

  parent reply	other threads:[~2004-04-28 20:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1PMQ9-5K6-3@gated-at.bofh.it>
2004-04-28 14:48 ` Linux 2.6.6-rc3 Vincent C Jones
2004-04-28 16:00   ` Sam Ravnborg
2004-04-28 17:24     ` Jari Ruusu
2004-04-28 19:08       ` Sam Ravnborg
2004-04-28 19:18       ` Vincent C Jones [this message]
     [not found] ` <1PVTx-4rY-25@gated-at.bofh.it>
     [not found]   ` <1R9hC-6rC-3@gated-at.bofh.it>
     [not found]     ` <1Rbjr-7Y5-17@gated-at.bofh.it>
     [not found]       ` <1RbW9-8sE-17@gated-at.bofh.it>
2004-05-01 23:26         ` 2.6.6-rc3: modular DVB tda1004x broken Andi Kleen
2004-05-01 23:34           ` Andrew Morton
2004-04-28  2:03 Linux 2.6.6-rc3 Linus Torvalds
2004-04-28  8:48 ` Måns Rullgård
2004-04-28  9:16 ` Florian Schirmer
2004-04-28  9:52   ` Armin Schindler
2004-04-28 11:56 ` Eyal Lebedinsky
2004-04-28 17:28 ` Maciej Soltysiak
2004-04-29  1:02 ` Craig Thomas
2004-04-29  0:59   ` CaT
2004-04-29 17:10     ` Craig Thomas
2004-04-29  2:11   ` Andrew Morton
2004-04-29 15:59     ` Craig Thomas
2004-04-29 17:01 ` Jacek Kawa
2004-04-29 17:32   ` Sam Ravnborg
2004-04-30  1:05     ` Jacek Kawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040428191841.GA4449@NetworkingUnlimited.com \
    --to=vcjones@networkingunlimited.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox