public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: New user encountering problems
Date: Sat, 23 Sep 2000 15:59:52 -0700	[thread overview]
Message-ID: <000201c025bd$c5f9c120$37059ed8@wang> (raw)
In-Reply-To: <3.0.6.32.20000922225521.007db9a0@mail.ufw2.com>

I always suggest to take RedHat kernel as it is and just load modules.
Best,
Vic

******* ******* *******
have you thought of visiting Cybertsar's Internet Kingdom? It is still
alive!
Here is the URL:
http://nimbus.ocis.temple.edu/~vtsaran/
******* ******* *******
----- Original Message -----
From: "Brent Harding" <bharding@ufw2.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, September 22, 2000 8:55 PM
Subject: Re: New user encountering problems


> I've liked debian for awhile, but tons of stuff won't compile, because the
> locations of files are a little screwy. Why put stuff in non standard
> places I don't know. How does one configure a redhat kernel when compiling
> anyways? I'm thinking about using it some time, suppose I need the 3c59x
> driver support for networking, can I config it like a normal kernel or
does
> redhat have tools to make this easier?
> At 11:24 PM 9/22/00 -0400, you wrote:
> >Hi
> > It is possible to build a speakup kernel from the Red Hat source
> >RPM. Just skip the patches that can't find their files, they don't apply
> >to the i386.
> > However, the kernel will build, but unless you use a rh supplied
> >config, your modules will have unresolved symbols all over the place. I
> >don't think speakup agrees with some of the patches RH applied to their
> >kernel rpm, for it is not a clean source. They've applied all sorts of
> >stuff that are beta, or even alpha. Not wise, I believe they do it to try
> >to get their distro to support more hardware.
> > Personally, I think slackware is the best, closely followed by
> >debian.
> >
> >On Fri, 22 Sep 2000, Kirk Wood wrote:
> >
> >> I believe this is a kernel problem. Once the kernel starts expanding
(you
> >> get the loading and the dots, then the kernel quickly takes over. My
guess
> >> is that you used the kernell source provided by RedHat. If you did,
then
> >> you should download the kernel (possibly from kernel.org) and apply the
> >> patch compile, etc.) RedHat doesn't provide the complete kernel and as
a
> >> result the built images don't work correct. Sorry I can't give you more
> >> complete details. Just that it is common to discover you can't build a
> >> working kernel with speakup from the RedHat source package.
> >>
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jerry Robinette
 ` Gorgotek Systems
 ` Kirk Wood
   ` Jacob Schmude
     ` Brent Harding
       ` Geoff Shang
         ` Brent Harding
       ` Jacob Schmude
         ` Kirk Wood
         ` Brent Harding
           ` Jacob Schmude
     [not found]         ` <Pine.LNX.4.21.0009231155110.1013-100000@localhost.localdom ain>
           ` Brent Harding
       ` Victor Tsaran [this message]
         ` Brent Harding
           ` Victor Tsaran
       ` Kerry Hoath
         ` Kirk Wood
         ` Victor Tsaran
           ` Distro discusion Kirk Wood
             ` Chris Nestrud
               ` Kirk Wood
             ` Gene Collins
               ` Victor Tsaran
                 ` Jacob Schmude
                 ` Brent Harding
                   ` Victor Tsaran
                     ` Brent Harding
           ` New user encountering problems Brent Harding
             ` HOWTOs (was Re: New user encountering problems) Jacob Schmude
 ` New user encountering problems Jacob Schmude
 ` William F. Acker WB2FLW +1-303-777-8123

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='000201c025bd$c5f9c120$37059ed8@wang' \
    --to=vtsaran@nimbus.ocis.temple.edu \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).