public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: info <5740@mail.ru>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org, John Jasen <jjasen@datafoundation.com>
Subject: Re: 2.4.3 compile error No 3
Date: Wed, 11 Apr 2001 20:34:26 +0400	[thread overview]
Message-ID: <01041120540000.05702@sh.lc> (raw)
In-Reply-To: <4AC3B9077C6@vcnet.vc.cvut.cz>
In-Reply-To: <4AC3B9077C6@vcnet.vc.cvut.cz>

þÔ×, 12 áÐÒ 2001, × ÓÏÏÂÝÅÎÉÉ ÎÁ ÔÅÍÕ "Re: 2.4.3 compile error No 3", Petr Vandrovec ÎÁÐÉÓÁÌ:
> On 11 Apr 01 at 20:15, info wrote:
> > 
> > By the way, I thung that it is a good idea - to modify
> > xconfig/meniconfig script  in manner to make disable ipx if sysctl
> > setted off - like in many other cross-dependance options. 
> 
> Without sysctl you cannot disable Netbios propagation packet routing.
> And no machine with enabled Netbios routing passes our 'you must not
> participate in broadcast storms' test if it has enabled more than
> one IPX frame on each interface. So you'll get disconnected from our 
> university net.
>                                     Petr Vandrovec
>                                     vandrove@vc.cvut.cz

Sorry, Petr, I can't understand your mind: my knowlege in programming
and English isn't enougth.

My user's mind was: if sysctl is needed for ipx, then:
1-st variant -  to modify config script in such manner that sysctl
turned on automatically (maybe as other needable functions, if they
are) if ipx selected. 
2-nd variant - to modify it in such manner that you can't select ipx
before you select sysctl 

The second variant is more easy (for example: you can't select reiserfs now
if you doesn't select one of another option, I don't remember it's
name).
But  the first way is more user-friendly. This is the same principle
as in rpm during installation. For example: when I select in Mandrake
installer that I want to have Klyx in my KDE, the installer
automatically select tetex, latex, ghostscript and other packages.
Because klyx can't work without them. It is very  comfortable for
user.

I think that you, as kernel programmer, work with .config
directly. But  I - as user - work only on level of "menu xconfig"
screen when I try to compile.

I speake only about user's friendlyness of kernel config screen, not
about frames and other programming topics. I don't know what is it at
all. It is not my user's level.

  reply	other threads:[~2001-04-11 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 18:23 2.4.3 compile error No 3 Petr Vandrovec
2001-04-11 16:34 ` info [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 18:59 Petr Vandrovec
     [not found] <4AB83BD5FB4@vcnet.vc.cvut.cz>
2001-04-11 16:02 ` Petr Vandrovec
2001-04-11 13:29   ` Arnaldo Carvalho de Melo
2001-04-11 16:15   ` info

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=01041120540000.05702@sh.lc \
    --to=5740@mail.ru \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jjasen@datafoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox