From: Arthur Perry <art@perryconsulting.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Sorry if this question is the beaten dead horse
Date: Mon, 19 May 2003 15:56:39 -0400 [thread overview]
Message-ID: <3EC936F7.1060207@perryconsulting.net> (raw)
In-Reply-To: 3EC92E0E.5090807@perryconsulting.net
Aww geesh.
I am such a fool.
All I have to say is 'less ./Documentation/Changes'.
I will give this a go first before I send another silly email.
remember to RTFM. ;)
Sorry about that.
Been a while since I had to read the kernel user's readmes.
Arthur Perry wrote:
> Hello All,
>
> I have a question, sorry if it is totally out of this league.
> I have been trying to compile a 2.5 kernel with modules support for a
> while, and have always been unsuccessful.
> There are always unresolved symbols.
> Always. Tons of em. If I didn't know any better, I'd say all of them of
> which I tried to compile as modules.
> I am not a newbie to Linux, I have been putting together distros for
> over 6 years, but the past year or two I have been maintaining stable
> releases in production environments.
> Just recently, I have tried to build the 2.5 tree, adn I know I am
> missing something.
>
> I am using Slackware 9.0, which is glibc 2.3.1 and gcc 3.2.2.
> Modutils 2.4.25 with Rusty's module-init-tools-0.9.12.
> It is mostly Vanilla otherwise.
>
> I know I must be missing a lot of tools and system-side changes to
> accomodate a 2.5 kernel, and I have been trying to identify what they are.
>
> No need to get too specific, I have been categorically a kernel "user"
> for quite some time (just not a 2.5 one), so I just need quick info and
> links.
>
>
> Thanks in advance!!
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-05-19 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 19:18 Sorry if this question is the beaten dead horse Arthur Perry
2003-05-19 19:56 ` Arthur Perry [this message]
2003-05-19 20:24 ` Arthur Perry
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=3EC936F7.1060207@perryconsulting.net \
--to=art@perryconsulting.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.