All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Perchine <dyp@perchine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: Fri, 24 Aug 2001 14:13:29 +0700	[thread overview]
Message-ID: <20010824041500.BBE381FD71@mx.webmailstation.com> (raw)
In-Reply-To: <20010822030807.N120@pervalidus> <20010824020119.42D951FD7D@mx.webmailstation.com> <20010824093508.A17415@francoudi.com>
In-Reply-To: <20010824093508.A17415@francoudi.com>

On Friday 24 August 2001 13:35, Leonid Mamtchenkov wrote:
> Once you wrote about "Re: Will 2.6 require Python for any configuration ?
> (CML2)": DP> On Friday 24 August 2001 02:41, Tom Rini wrote:
> DP> > On Thu, Aug 23, 2001 at 09:26:33PM +0200, Jes Sorensen wrote:
> DP> > > >>>>> "Tom" == Tom Rini <trini@kernel.crashing.org> writes:
> DP> > You've said this before. :)  Just how small of an 'embedded' system are
> DP> > you talking about?  I know of people who do compile a kernel now and
> DP> > again on a 'small' system, for fun.  On a larger (cPCI) system, I
> DP> > don't see your point.  If you can somehow transport the 21mb[1] bzip2
> DP> > kernel source to your system, you can transport python.  If you're
> DP> > porting to a brand new arch, there's still good tests before you
> DP> > have shlib support (You've mentioned that before too I think).
> DP> There is another point why having Python installed is a problem. Usually when
> DP> you install a server you remove everything from it because of space, and
> DP> security reasons. The main security concern is the less is installed the
> DP> better security is. I always remove python from any servers I have. As I
> DP> remove guile, forth, and other useless (in terms of server) languages. Now
> DP> you tell me that I should have this bloat installed just to configure my
> DP> kernel. Do not you think that it is too much? Current kernel does not require
> DP> anything like this.

> Why should you have gcc and make on the server then?  Compile you kernel
> on another machine and then just install it on your servers.  This way
> you will not only save space and improve security, but also gain some
> time, which is always good.

That's nice idea, but it does not have any connection to subj.
I prefer to do things the way I do them now. Anyway I need compiler for other things.
I have lot of C/C++ daemons running, and want to fix problems right there.
But having Python just to configure a kernel is an overkill. Why not Sather, or other rarely used language.
Oberon-2 would be also nice.

This is just a laziness of people who do not want to make things right. Actually interesting question
is what Linus think of all this crap?

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

  reply	other threads:[~2001-08-24  7:11 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  6:08 Will 2.6 require Python for any configuration ? (CML2) =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-08-23 12:05 ` Roland Bauerschmidt
2001-08-23 15:36   ` Bob Glamm
2001-08-23 15:55     ` Disconnect
2001-08-23 18:36       ` Daniel Phillips
2001-08-23 18:44         ` Disconnect
2001-08-23 19:01           ` David Weinehall
2001-08-23 19:22             ` Alan Cox
2001-08-23 19:02           ` Roland Bauerschmidt
2001-08-23 19:09           ` Rik van Riel
2001-08-23 19:31             ` Disconnect
2001-08-23 22:52               ` John Alvord
2001-08-24  1:51                 ` Keith Owens
2001-08-23 15:55     ` Joshua Schmidlkofer
2001-08-23 15:59     ` Tom Rini
2001-08-23 19:26       ` Jes Sorensen
2001-08-23 19:32         ` David Weinehall
2001-08-23 19:41         ` Tom Rini
2001-08-23 19:50           ` Tom Rini
2001-08-23 20:02           ` Jes Sorensen
2001-08-23 20:13             ` Tom Rini
2001-08-23 20:43               ` Jes Sorensen
2001-08-23 21:12                 ` Tom Rini
2001-08-24  4:59           ` Denis Perchine
2001-08-24  6:35             ` Leonid Mamtchenkov
2001-08-24  7:13               ` Denis Perchine [this message]
2001-08-24 15:01                 ` Mark Hahn
2001-08-24 13:35             ` Ryan W. Maple
2001-08-25  1:14               ` Michael Peddemors
2001-08-24 17:42             ` David Lang
2001-08-23 16:24     ` Roland Bauerschmidt
2001-08-23 17:57     ` Kurt Roeckx
2001-08-24  8:10 ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2001-08-23 20:41 Samium Gromoff
2001-08-23 20:53 ` Tom Rini
2001-08-25  4:11   ` Ben Ford
2001-08-25 14:51     ` Tom Rini
2001-08-23 20:56 Samium Gromoff
2001-08-23 21:14 ` Tom Rini
2001-08-23 21:08 Rick Hohensee
2001-08-23 21:01 ` Tom Rini
2001-08-23 21:12 Samium Gromoff
2001-08-23 21:32 ` Tom Rini
2001-08-23 21:18 Samium Gromoff
2001-08-23 21:34 ` Tom Rini
2001-08-24 12:59   ` Jes Sorensen
2001-08-24 15:37     ` Tom Rini
2001-08-24 15:42       ` Jes Sorensen
2001-08-24 15:50         ` Tom Rini
2001-08-24 16:03           ` Jes Sorensen
2001-08-23 21:39 Samium Gromoff
     [not found] <20010823191423.I14302@cpe-24-221-152-185.az.sprintbbd.net>
2001-08-24  3:01 ` Rick Hohensee

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=20010824041500.BBE381FD71@mx.webmailstation.com \
    --to=dyp@perchine.com \
    --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.