|
@ -10,8 +10,8 @@ several months ago for the reason just cited. Note: check_getty_type_call |
|
|
was removed from Yard.pm, but exists in chrooted tests without the termcap |
|
|
was removed from Yard.pm, but exists in chrooted tests without the termcap |
|
|
check. Also, added a close which was missing. |
|
|
check. Also, added a close which was missing. |
|
|
|
|
|
|
|
|
Removed an unnecessary check from the fstab test, and improved a regexp which |
|
|
Removed an unnecessary check from the fstab test, and improved a regexp |
|
|
was failing if tabs were used in the fstab. |
|
|
which was failing if tabs were used in the fstab. |
|
|
|
|
|
|
|
|
State is saved for all check buttons when the yard box is opened and |
|
|
State is saved for all check buttons when the yard box is opened and |
|
|
closed. Deciding whether to save state between invocations of gbootroot |
|
|
closed. Deciding whether to save state between invocations of gbootroot |
|
@ -28,8 +28,8 @@ Added several new FAQ questions, added a lot more information on |
|
|
"How do I use gBootRoot?" Updated the graphics for the documentation. |
|
|
"How do I use gBootRoot?" Updated the graphics for the documentation. |
|
|
|
|
|
|
|
|
Updated to version 2.4.14 of user-mode-linux. Note: 2.4.15 was buggy |
|
|
Updated to version 2.4.14 of user-mode-linux. Note: 2.4.15 was buggy |
|
|
in respect to rebooting, and produced an address number at login, it appears |
|
|
in respect to rebooting, and produced an address number at login, it |
|
|
to be a bad compile. |
|
|
appears to be a bad compile. |
|
|
|
|
|
|
|
|
The Yard Box has new check buttons which allows the parsing behavior of |
|
|
The Yard Box has new check buttons which allows the parsing behavior of |
|
|
the nss and pam configuration files to be turned off and on (default). |
|
|
the nss and pam configuration files to be turned off and on (default). |
|
@ -52,10 +52,10 @@ in the template if the pam parsing option in turned on. |
|
|
$ENV{RELEASE} is now initialized every time a check is run on the template. |
|
|
$ENV{RELEASE} is now initialized every time a check is run on the template. |
|
|
Information can come from three sources, the kernel version returned from |
|
|
Information can come from three sources, the kernel version returned from |
|
|
a selected kernel in the main section, the user defined kernel version |
|
|
a selected kernel in the main section, the user defined kernel version |
|
|
in the ABS, or `uname -r`. User defined kernel version overrides the kernel. |
|
|
in the ABS, or `uname -r`. User defined kernel version overrides the |
|
|
The root_fs needs to be built in relation to the actual kernel modules |
|
|
kernel. The root_fs needs to be built in relation to the actual kernel |
|
|
it will run on. Previously the $RELEASE value wasn't returned properly |
|
|
modules it will run on. Previously the $RELEASE value wasn't returned |
|
|
because of some bugs in kernel_version_check. This has been fixed. |
|
|
properly because of some bugs in kernel_version_check. This has been fixed. |
|
|
|
|
|
|
|
|
The proper ldd check is now used if a dynamically linked binary is detected |
|
|
The proper ldd check is now used if a dynamically linked binary is detected |
|
|
to require uClibc rather than libc6. The ldd from the default location of |
|
|
to require uClibc rather than libc6. The ldd from the default location of |
|
|