From 9e8160f0edcbf56b0c52d2e5cc1a25dacab38364 Mon Sep 17 00:00:00 2001 From: freesource Date: Tue, 25 Feb 2003 18:24:54 +0000 Subject: [PATCH] More stuff --- Changes | 5 +++++ README | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/Changes b/Changes index 6ec4a5e..8159935 100644 --- a/Changes +++ b/Changes @@ -12,6 +12,11 @@ Updated BEGIN statements in gbootroot, expect_uml and yard_chrooted_tests, and made sure "." is always specified first in @INC. +Thanks to Stian Skjelstad for pointing out some bugs +- namely the former annoying @INC bug that never should have occurred +in the first place - after I asked him to try out gbootroot to help +with his MTD requirements. + Added a new if/elsif control structure. \ if ( condition ) \n statement(s) \n elsif ( condition ) \n statements elsif .. \ Nice functionality to have. diff --git a/README b/README index fb8368e..8f3cb81 100644 --- a/README +++ b/README @@ -1,4 +1,4 @@ -$Id: README,v 1.28 2003/02/16 00:47:23 freesource Exp $ +$Id: README,v 1.29 2003/02/18 18:28:06 freesource Exp $ Program: gBootRoot pronounced "bOOtrOOt" License: GNU General Public License @@ -8,7 +8,7 @@ BUILDING If you can compile a kernel on your system, then you should have no problems getting the Makefile to work, and if you are using the sources for the Debian package, then you can always do an "apt-get -build-dep gbootroot." to automatically figure out your build +build-dep gbootroot" to automatically figure out your build requirements. Gbootroot makes its own root_fs, when the output gets colorful (blue and red) you know this is happening. If things go wrong at this point you will want to look at the requirements below.