From: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>
To: michal.k.k.piotrowski@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Automatic Configuration of a Kernel
Date: Thu, 15 Sep 2005 02:56:58 -0700 (PDT) [thread overview]
Message-ID: <20050915095658.68775.qmail@web51005.mail.yahoo.com> (raw)
In-Reply-To: <6bffcb0e05091415533d563c5a@mail.gmail.com>
--- Michal Piotrowski
<michal.k.k.piotrowski@gmail.com> wrote:
> Hi,
>
> On 15/09/05, Ahmad Reza Cheraghi
> <a_r_cheraghi@yahoo.com> wrote:
> > Hi
> >
> > I wrote this Framework for making a .config based
> on
> > the System Hardwares. It would be a great help if
> some
> > people would give me their opinion about it.
> >
> > Regards
>
> It's for new linux users? They should use
> distributions kernels.
> It's for "power users"? They just do make
> menuconfig...
> It's for kernel developers? They just do vi .config.
>
> I'll try it later, but I'm a bit sceptical.
>
> How about networking options? It can detect what
> protocols are needed?
> Filesystems?
The Network option or the Filesystes are choosen as a
Standard. So it will be there without checking if they
needed or not. Because I think Protocols like TCP-IP
or Filesystems like NTFS or expt2 has to be installed
on the now days Systems. But if they are any
suggestion or ideas of detecting those thing. No
problem just send me rule that does that and I will
updated easily on the Framework.Thats the benefit of
this Framework.;-)
> Regards,
> Michal Piotrowski
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
next prev parent reply other threads:[~2005-09-15 9:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:38 Ahmad Reza Cheraghi
2005-09-14 22:53 ` Michal Piotrowski
2005-09-14 23:49 ` Daniel Thaler
2005-09-15 0:09 ` Marek W
2005-09-15 0:37 ` Hua Zhong
2005-09-15 2:03 ` David Lang
2005-09-15 3:04 ` Lee Revell
2005-09-15 3:37 ` Daniel Thaler
2005-09-15 4:16 ` Lee Revell
2005-09-15 8:12 ` Ahmad Reza Cheraghi
2005-09-15 11:20 ` Masoud Sharbiani
2005-09-15 20:58 ` Ahmad Reza Cheraghi
2005-09-15 21:04 ` Jesper Juhl
2005-09-15 4:18 ` Marek W
2005-09-15 6:18 ` Valdis.Kletnieks
2005-09-15 7:33 ` Marek W
2005-09-15 9:48 ` Ahmad Reza Cheraghi
2005-09-15 10:44 ` David Lang
2005-09-15 10:26 ` David Lang
2005-09-15 14:58 ` Nix
2005-09-15 17:08 ` David Lang
2005-09-15 20:36 ` Valdis.Kletnieks
2005-09-15 20:50 ` Nix
2005-09-15 8:53 ` Chris White
2005-09-15 7:58 ` Ahmad Reza Cheraghi
2005-09-15 9:12 ` Emmanuel Fleury
2005-09-15 9:56 ` Ahmad Reza Cheraghi [this message]
2005-09-16 4:02 ` Chris White
2005-09-16 7:12 ` Emmanuel Fleury
2005-09-16 17:38 ` Pavel Machek
2005-09-16 17:50 ` Enrico Weigelt
2005-09-15 11:21 ` Roman Zippel
2005-09-15 12:01 ` Emmanuel Fleury
2005-09-15 13:02 ` Ahmad Reza Cheraghi
2005-09-15 13:28 ` Emmanuel Fleury
2005-09-15 13:03 ` Ahmad Reza Cheraghi
2005-09-17 1:27 ` Roman Zippel
2005-09-16 8:11 ` Coywolf Qi Hunt
2005-09-16 8:19 ` Emmanuel Fleury
2005-09-16 8:32 ` Ahmad Reza Cheraghi
2005-09-16 8:50 ` Emmanuel Fleury
2005-09-16 9:19 ` Ahmad Reza Cheraghi
2005-09-26 12:08 Ahmad Reza Cheraghi
2005-09-26 13:57 ` Michal Piotrowski
2005-09-26 14:06 ` Michal Piotrowski
2005-09-27 8:05 ` Coywolf Qi Hunt
2005-09-27 8:11 ` Emmanuel Fleury
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=20050915095658.68775.qmail@web51005.mail.yahoo.com \
--to=a_r_cheraghi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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
Powered by JetHome