mirror of
https://github.com/fspc/gbootroot.git
synced 2025-03-03 19:43:22 -05:00
Changes, and soon to come changes.
This commit is contained in:
parent
19ffe4b981
commit
bcef76cf23
30
Changes
30
Changes
@ -1,3 +1,33 @@
|
||||
|
||||
** not yet
|
||||
Now the templated called Helper.yard used to create the root_fs_helper is
|
||||
included with root_fs_helper.
|
||||
|
||||
Root_fs_helper was working fine, but because I hadn't committed, let alone
|
||||
copied the new changes to CVS I didn't notice any aberrations until I
|
||||
installed the new released version of gbootroot. This is related to the new
|
||||
securretty requirements of uml. Problem fixed.
|
||||
|
||||
*** Better check on this below
|
||||
Initrd was not working with any fs other than ext2. After
|
||||
contacting the trinux-uml project, Matthew Franz <mfranz@cisco.com> confirmed
|
||||
that he was having problems creating a working uml for the initrd created
|
||||
by Bill Burdick <bill@appliedreasoning.com>. I talked Bill into sending
|
||||
me his uml .config, and narrowed down the problem to cramfs. Cramfs has
|
||||
known bugs as documented in the kernel sources. Because cramfs was placed
|
||||
before just about every fs in the VFS check order, and trinux-uml's initrd
|
||||
was minix, the kernel failed, but an ext2 initrd didn't. Changing the order
|
||||
in which filesystems are checked during the VFS stage by editing fs/Makefile
|
||||
solves the problem. Thanks for Henrik Nordstrom <hno@marasystems.com> for
|
||||
pointing out how to do this at user-mode-linux-devel. I am hoping the patch
|
||||
I posted at -devel becomes part of uml. This should have been corrected
|
||||
ages ago in the standard Linux kernel.
|
||||
** not yet
|
||||
|
||||
Removed unecessary warning which warned that left-hand side replacements
|
||||
couldn't be a directory if it happened to find that directory on the hostfs.
|
||||
Directories can be replacements.
|
||||
|
||||
1.3.4 - 02/08/2002
|
||||
------------------
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user