From: Giacomo Catenazzi <cate@debian.org>
To: linux-kernel@vger.kernel.org
Subject: [ANNONCE] Kernel Autoconfiguration utility v.0.9.1.2
Date: Thu, 15 Feb 2001 11:42:19 +0100 [thread overview]
Message-ID: <3A8BB28B.B2A51C57@debian.org> (raw)
Hello!
I just release a new verion of kernel autoconfig.
The kernel autoconfiguration utility will help user to detect and
configure the kernel. The detection is soft, thus no hangs!
It is still in test phase, thus now it prints only the proposed
configuration. To change real configurations, I'm still waiting for
a working CML2.
On my hardware database there are:
1007 pci cards
111 devices (block and char)
37 file systems
7 console drivers
8 net protocols
511 resources strings.
+ some extra special detection.
Project homepage:
http://sourceforge.net/projects/kautoconfigure/
How to use: (now, testing phase)
unpack the files (better: in a new directory)
> bash autoconfigure.sh | less
check the output.
no super user privileges required!
I need some help:
- Some drivers detect pci in a strange way, I could not check every
files.
Please check if your cards are included.
- Check, add extra detections
I will do:
- updates to the database when a new official kernel version is released
- interface with CML2 (partially done, but CML2-9.0.1 has still bugs)
- better 'CONFIG_*=N' handling (e.g. I will check is a drivers depends
on PCI. If this PCI card is not found, I can safely tell you that the
device is not in the box).
- generate inverse dependences.
Comments?
giacomo
PS. I have done the autodetection reading the source and not using
real hardware, thus ... no warranty.
PPS: This tools is designed mainly for newbies (in kernel compiling...),
thus I don't expect to have a real autodetection on very special
machines. [But I expect in the future to do this :-) ]
next reply other threads:[~2001-02-15 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 10:42 Giacomo Catenazzi [this message]
2001-02-15 14:34 ` [ANNONCE] Kernel Autoconfiguration utility v.0.9.1.2 Andrey Panin
2001-02-15 16:20 ` William Stearns
2001-02-15 16:56 ` Andreas Schwab
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=3A8BB28B.B2A51C57@debian.org \
--to=cate@debian.org \
--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