mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Sean Middleditch <elanthis@awesomeplay.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Via onboard audio
Date: Fri, 2 Nov 2001 19:51:02 +0100	[thread overview]
Message-ID: <20011102195102.G17407@khan.acc.umu.se> (raw)
In-Reply-To: <E15zii5-00037A-00@the-village.bc.nu> <1004724193.4883.21.camel@smiddle>
In-Reply-To: <1004724193.4883.21.camel@smiddle>; from elanthis@awesomeplay.com on Fri, Nov 02, 2001 at 01:03:13PM -0500

On Fri, Nov 02, 2001 at 01:03:13PM -0500, Sean Middleditch wrote:
> On Fri, 2001-11-02 at 13:06, Alan Cox wrote:
> > > OK, will do that.  RedHat uses your kernel trees, right?  I'll download
> > > new RPM's from rawhide if they're there (I'm in no hurry.)
> > 
> > Both Linus and -ac current trees support
> > 
> > make config
> > make rpm
> > 
> > rpm -Ivh blah...
> > 
> > then edit your lilo/grub config 8)
> 
> Hmm, good point, I forgot that was added.
> 
> I suppose I could be evil and ask when make deb support will be there for my
> more preferred Debian boxes... But I won't ask.  ~,^

Not needed.

fakeroot make-kpkg kernel_image

or similar should do the trick.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-11-02 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 16:01 Sean Middleditch
2001-11-02 16:14 ` Jeff Garzik
2001-11-02 16:21 ` Alan Cox
2001-11-02 17:51   ` Sean Middleditch
2001-11-02 18:06     ` Alan Cox
2001-11-02 18:03       ` Sean Middleditch
2001-11-02 18:51         ` David Weinehall [this message]
2001-11-03 16:21   ` Sean Middleditch
2001-11-02 17:52 ` Sean Middleditch
2001-11-02 17:55   ` Jeff Garzik

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=20011102195102.G17407@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=elanthis@awesomeplay.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®