Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Jeremiah <jjgpg@cet.com>
To: linux-hams@vger.kernel.org
Subject: Re: error when trying to run kissattach on 2.6.13-15.8 Suse Kernel
Date: Tue, 2 May 2006 05:35:55 -0700	[thread overview]
Message-ID: <200605020535.56134.jjgpg@cet.com> (raw)
In-Reply-To: <002401c664ae$c436a340$650ea8c0@LoJackOne.LoJack.com>

Hello all:

Well I'm a happy guy today, I got 2.6.16 installed from the RPM on my Suse 
10.0 box, and so far it seems to run happy. I had to do the install a few 
times, but after doing a "rpm -iv --nodeps ..." to keep it from complaning 
that it didn't have the right version of perl-bootloader it seems to work. 

So I can have my packet base station back, YEAH!!!!

I'll keep every one up to date on this if I find any problems with running 
this non-distro stander kernel.

Thanks all for that help ^_^

Jeremiah
KD7DMP

On Thursday 20 April 2006 12:15, Mike McCarthy, W1NR wrote:
> There is another gotcha...
>
> SuSE 10.1 RC1 does not include libax25 any longer.  However, the kernel is
> still built with the mkiss and ax25 modules so no kernel recompile is
> needed.  This causes the current 10.0 packages to fail dependencies when
> you try and install them through YaST.
>
> There is hope.  I am attempting to build a libax25 rpm file.  I am also
> looking at creating an "add-on" for all of the packages using the new 10.1
> features of YaST.
>
> More later.
>
> Mike, W1NR
>
> ----- Original Message -----
> From: "Mike McCarthy, W1NR" <lists@w1nr.net>
> To: "Douglas Cole" <doug.n7bfs@gmail.com>
> Cc: "Jeremiah" <jjgpg@cet.com>; <linux-hams@vger.kernel.org>
> Sent: Wednesday, April 19, 2006 12:02 PM
> Subject: Re: error when trying to run kissattach on 2.6.13-15.8 Suse Kernel
>
> > Yes.
> >
> > ----- Original Message -----
> > From: "Douglas Cole" <doug.n7bfs@gmail.com>
> > To: "Mike McCarthy, W1NR" <lists@w1nr.net>
> > Cc: "Jeremiah" <jjgpg@cet.com>; <linux-hams@vger.kernel.org>
> > Sent: Wednesday, April 19, 2006 9:25 AM
> > Subject: Re: error when trying to run kissattach on 2.6.13-15.8 Suse
> > Kernel
> >
> >
> > After downloading the ISO images of 10.1rc1 and searching disc one, it
> > uses 2.6.16.20 as the "default" kernel, so would that have a fair
> > chance of working with ax25 and mkiss ?
> >
> > tnx for any input/help
> >
> > Doug
> > N7BFS
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-05-02 12:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  3:21 error when trying to run kissattach on 2.6.13-15.8 Suse Kernel Jeremiah
2006-04-18 11:51 ` Mike McCarthy, W1NR
2006-04-18 23:33   ` Mike McCarthy, W1NR
2006-04-19  0:55     ` Douglas Cole
2006-04-19 12:18       ` Mike McCarthy, W1NR
2006-04-19 12:26         ` Jeremiah
2006-04-19 12:04     ` Jeremiah
2006-04-19 12:28       ` Mike McCarthy, W1NR
2006-04-19 13:25         ` Douglas Cole
2006-04-19 16:02           ` Mike McCarthy, W1NR
2006-04-20 19:15             ` Mike McCarthy, W1NR
2006-05-02 12:35               ` Jeremiah [this message]
     [not found] ` <000701c6629a$f803c4c0$e14689d8@oem7paq6co5hph>
2006-04-19 11:59   ` Jeremiah

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=200605020535.56134.jjgpg@cet.com \
    --to=jjgpg@cet.com \
    --cc=linux-hams@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