public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jalvo@mbay.net (John Alvord)
To: David Ford <david@linux.com>
Cc: reiserfs-list@namesys.com, <reiser@namesys.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink  related)
Date: Sun, 04 Feb 2001 03:24:00 GMT	[thread overview]
Message-ID: <3a7dc9fb.47468112@mail.mbay.net> (raw)
In-Reply-To: <E14OoD8-0007GI-00@the-village.bc.nu> <3A7BC808.E9BF5B44@linux.com>
In-Reply-To: <3A7BC808.E9BF5B44@linux.com>

On Sat, 03 Feb 2001 00:57:45 -0800, David Ford <david@linux.com>
wrote:

>How about a simple patch to the top level makefile that checks the gcc
>version then prints a distinct message ..'this compiler hasn't been approved
>for compiling the kernel', sleeping for one second, then continuing on.  This
>solution doesn't stop compiling and makes a visible indicator without forcing
>anything.

A while ago I worked up a nasty bit of make logic which prompted the
user for yes or no... and then did one thing or the other. You could
ask the user if he REALLY wants to continue and wait for a response.
Following is the model code...
John Alvord
=================

_ECHO=@

all:  t0 t1 t2 t3 t4 t5 t6

# prompt for input, must be in a separate rule to unbuffer terminal
# output.
t0:
     $(_ECHO)echo Enter Y or N: \\c

# capture a line of terminal input, copy to a file, tell user
t1:
     $(_ECHO)echo $(shell read ans; echo ans) > ans
     $(_ECHO)echo The answer is \\c
     $(_ECHO)cat ans

# take first character of answer, upper case, store in another file
# then create two files, one for yes and one for no
# the || exit 0 is to mask the potential grep error, which
# would result in an error message even a - was used to ignore error
# and continue. The result is two files, which may be zero byte
t2:
     $(_ECHO)cat ans | cut -c 1-1 | tr 'a-z' 'A-Z' >ans1
     $(_ECHO)rm -f ansy
     $(_ECHO)rm -f ansn
     $(_ECHO)grep Y ans1 > ansy || exit 0
     $(_ECHO)grep N ans1 > ansn || exit 0

# Check for case where neither answer file is > 0 bytes
t3:
     $(_ECHO)test -s ansy || test -s ansn && exit 0; \
 echo Answer [$(shell cat ans)] is neither Y or N! && exit 1

# handle Yes case. Exit if Y answer file is 0 bytes or missing
t4:
     $(_ECHO)test ! -s ansy  && exit 0; \
     echo in YES processing

# handle No case
t5:
     $(_ECHO)test ! -s ansn  && exit 0; \
     echo in NO processing


# remove files used during processing
t6:
     $(_ECHO)rm -f ans
     $(_ECHO)rm -f ans1
     $(_ECHO)rm -f ansn
     $(_ECHO)rm -f ansy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-02-04  3:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57   ` Alan Cox
2001-02-02 22:06     ` Arthur Erhardt
2001-02-02 22:06     ` Hans Reiser
2001-02-02 22:57       ` Ion Badulescu
2001-02-05  2:50       ` Brian Wolfe
2001-02-05  4:08         ` Albert D. Cahalan
2001-02-05 11:58           ` Alan Cox
2001-02-05 11:36             ` Hans Reiser
2001-02-05 12:44               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16                 ` Hans Reiser
2001-02-05 12:52                   ` Alan Cox
2001-02-05 12:33                     ` Hans Reiser
2001-02-05 12:57                   ` Dr. David Gilbert
2001-02-05 16:57               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12  3:41               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12  9:45                 ` Hans Reiser
2001-02-05 12:16             ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05  5:21         ` Gregory Maxwell
2001-02-05 12:02           ` Alan Cox
2001-02-05 11:38             ` Hans Reiser
2001-02-05 11:55         ` Alan Cox
2001-02-05 11:35           ` Hans Reiser
2001-02-05 20:19           ` Brian Wolfe
2001-02-02 22:42     ` Ion Badulescu
2001-02-03  3:43       ` Johan Kullstam
2001-02-03  8:57     ` [reiserfs-list] " David Ford
2001-02-03 10:00       ` J . A . Magallon
2001-02-03 23:26         ` Felix von Leitner
2001-02-04 11:04           ` Alan Cox
2001-02-04  3:24       ` John Alvord [this message]
2001-02-02 11:28 Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16   ` Jan Kasprzak
2001-02-02 12:34     ` Alan Cox
2001-02-02 13:09       ` Jan Kasprzak
2001-02-02 16:36         ` Jan Kasprzak
2001-02-02 16:46           ` Alan Cox
2001-02-02 12:15 ` John Morrison

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=3a7dc9fb.47468112@mail.mbay.net \
    --to=jalvo@mbay.net \
    --cc=david@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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