anything major comes up. Added some links to the webpage, information
how to customize the kernel in the source package, and ups the date,
though that will probably be done one more time.
EXPECT, and a bug where .options wasn't being written to disk or the
path was being altered when a variable was being altered. This also
gets things trim and ready with the coolest discovery being that a
nested kernel can run on the host and in it's nest. I'll be testing
other nested levels to discover how far this can go and be
incorporated in one package which is nice.
find port-helper, or otherwise root_fs complain. Have no idea why
this change exists with port-helper because wasn't the case before.
Also, added path for user-mode-linux/usr/bin to find the other tools.
Also, improves all in Makefile
effectively known as the create stage. This avoids the unecessary previous
requirement of having to select the copy stage again just to create a file
for /dev/ubd/0. The file created is sparse, got this idea from a discussion
Jeff had with a user on uml-user.
bit more, but have tested this with an initrd, and it works pretty nicely
even with large fs assuming mem is set high enough. Mtdram was chosen over
blkmtd for now.
During the boot stage the filsystem type was used to determine whether
to use the genext2fs (non-root) method or the normal method used by root.
Now the user type is used, this is better because it prevents conflicts
if a different filesystem type is chosen, or if a non-root user changes to a
different filesystem type in the filesystem box and forgets to change back
to genext2fs; however, it prevents root from using the genext2fs method,
which isn't a problem. The sudo requirement for lilo is too much of a
requirement, and will be changed in future versions.
root_fs by using the libraries from the initrd. Liav instigated this by
asking a question related to FAQ question 14, "So if I understand correctly,
it is not possible to copy libc from /dev/ram0 to /dev/ram1 before mounting
/dev/ram1 as / ?
Liav pointed out how Yard can make boot/root floppies with a compressed root
filesystem. Edited FAQ question 13 to correctly reflect how gz compressed
root filesystems may be booted without an initrd.
entry won't be the same as that found in Root Filename, but instead reflects
the newly compressed file. This change was precipitated by the previous
change to the Accept behavior.
freesource