bike/gbootroot
1
0
Fork 0
mirror of https://github.com/fspc/gbootroot.git synced 2025-03-11 23:33:23 -04:00
Code Issues Projects Releases Wiki Activity

More stuff

Browse Source
This commit is contained in:
freesource 2003-02-25 18:24:54 +00:00
parent d32a4477b1
commit 9e8160f0ed
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Changes
View File

@ -12,6 +12,11 @@ Updated BEGIN statements in gbootroot, expect_uml and
yard_chrooted_tests, and made sure "." is always specified first in yard_chrooted_tests, and made sure "." is always specified first in
@INC. @INC.
Thanks to Stian Skjelstad <stian@nixia.no> 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 Added a new if/elsif control structure. \ if ( condition ) \n
statement(s) \n elsif ( condition ) \n statements elsif .. \ Nice statement(s) \n elsif ( condition ) \n statements elsif .. \ Nice
functionality to have. functionality to have.

4
README
View File

@ -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" Program: gBootRoot pronounced "bOOtrOOt"
License: GNU General Public License License: GNU General Public License
@ -8,7 +8,7 @@ BUILDING
If you can compile a kernel on your system, then you should have no 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 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 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 requirements. Gbootroot makes its own root_fs, when the output gets
colorful (blue and red) you know this is happening. If things go 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. wrong at this point you will want to look at the requirements below.