mirror of
https://github.com/fspc/gbootroot.git
synced 2025-02-23 09:03:23 -05:00
Added another technique in the FAQ to show how space can be saved on the
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.
This commit is contained in:
freesource
parent
8cac3030ca
commit
6dbb2d58c7
11
Changes
11
Changes
@ -1,3 +1,14 @@
|
|||||||
|
|
||||||
|
Added another technique in the FAQ to show how space can be saved on the
|
||||||
|
root_fs by using the libraries from the initrd. Liav instigated this by
|
||||||
|
asking a question related to FAQ question 16, "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 16 to correctly reflect how gz compressed
|
||||||
|
root filesystems may be booted without an initrd.
|
||||||
|
|
||||||
State is saved for the Compression off check box and the Root Filename save
|
State is saved for the Compression off check box and the Root Filename save
|
||||||
check box.
|
check box.
|
||||||
|
|
||||||
|
|||||||
@ -3,7 +3,7 @@
|
|||||||
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E"
|
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E"
|
||||||
alink="#FF0000">
|
alink="#FF0000">
|
||||||
|
|
||||||
<center>$Id: index.html,v 1.76 2002/01/11 04:51:36 freesource Exp $</center>
|
<center>$Id: index.html,v 1.78 2002/01/11 13:51:56 freesource Exp $</center>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
@ -490,23 +490,25 @@ and things should become more clear.
|
|||||||
<br>
|
<br>
|
||||||
14. <a href="#14">If libc is included in the boot disk, why is it needed in the root disk as well?</a>
|
14. <a href="#14">If libc is included in the boot disk, why is it needed in the root disk as well?</a>
|
||||||
<br>
|
<br>
|
||||||
15. <a href="#15">There isn't enough room left on my 1440 floppy to make a Boot or Root disk. Is there any way to free up more space apart from reducing the size of the kernel?</a>
|
15. <a href="#15">So if I understand correctly, it is not possible to copy libc from dev/ram0 to /dev/ram1 before mounting /dev/ram1 as / ?</a>
|
||||||
<br>
|
<br>
|
||||||
16. <a href="#16">Last, but not least...the boot disk boots, waits for the root disk, and now fails. "Can't open console"??? or sth like this (I'm pretty tired right now, recheck later), which appears after "VFS:ext2fs was found..."</a>
|
16. <a href="#16">There isn't enough room left on my 1440 floppy to make a Boot or Root disk. Is there any way to free up more space apart from reducing the size of the kernel?</a>
|
||||||
<br>
|
<br>
|
||||||
17. <a href="#17">What are the kernel's drivers/fs that must be directly compiled, not as modules, except ext2, floppy? Could you attach your kernel's .config?</a>
|
17. <a href="#17">Last, but not least...the boot disk boots, waits for the root disk, and now fails. "Can't open console"??? or sth like this (I'm pretty tired right now, recheck later), which appears after "VFS:ext2fs was found..."</a>
|
||||||
<br>
|
<br>
|
||||||
18. <a href="#18">What is the root_fs_helper 2Mb file in the grootboot package?</a>
|
18. <a href="#18">What are the kernel's drivers/fs that must be directly compiled, not as modules, except ext2, floppy? Could you attach your kernel's .config?</a>
|
||||||
<br>
|
<br>
|
||||||
19. <a href="#19">
|
19. <a href="#19">What is the root_fs_helper 2Mb file in the grootboot package?</a>
|
||||||
|
<br>
|
||||||
|
20. <a href="#20">
|
||||||
Now the creation works, but actually the whole image is less than 1440k... Still, unclear to me is the purpose of the device/size in the main widget - is it only for the boot or also for the root disk? After all, the root fs image size has been already entered in the ARS.</a>
|
Now the creation works, but actually the whole image is less than 1440k... Still, unclear to me is the purpose of the device/size in the main widget - is it only for the boot or also for the root disk? After all, the root fs image size has been already entered in the ARS.</a>
|
||||||
<br>
|
<br>
|
||||||
20. <a href="#20">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
|
21. <a href="#21">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
|
||||||
<br>
|
<br>
|
||||||
21. <a href="#21">If you roll the floppy density counter down to 0 and then try go back up towards 1440 and 1722, you get very funny figures.</a>
|
22. <a href="#22">If you roll the floppy density counter down to 0 and then try go back up towards 1440 and 1722, you get very funny figures.</a>
|
||||||
</a>
|
</a>
|
||||||
<br>
|
<br>
|
||||||
22. <a href="#22">Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</a>
|
23. <a href="#23">Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</a>
|
||||||
<br>
|
<br>
|
||||||
|
|
||||||
<P><a name="1"><b>What's the advantage of using this program?</b></a> <a href="#FAQ">[back]</a></P>
|
<P><a name="1"><b>What's the advantage of using this program?</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
@ -1126,20 +1128,20 @@ filesystem.</P>
|
|||||||
<p>
|
<p>
|
||||||
|
|
||||||
If you are creating a boot disk in which the kernel knows where to
|
If you are creating a boot disk in which the kernel knows where to
|
||||||
find the root filesystem and the root filesystem is not compressed with
|
find the root filesystem and the root filesystem is
|
||||||
gzip or bzip2 (i.e. a cramfs could be used), then nothing
|
either compressed with gzip or not compressed (i.e. a cramfs could be used),
|
||||||
else but a kernel is required
|
then nothing else but a kernel is required
|
||||||
assuming it is copied in a way that is starts at block 0 on the device
|
assuming it is copied in a way that is starts at block 0 on the device
|
||||||
media, and then rdeved in such a way that it knows that the ramdisk and the
|
media, and then rdeved in such a way that it knows that the ramdisk and the
|
||||||
prompt
|
prompt
|
||||||
flag are on, i.e., rdev -r /dev/fd0 49152, and that the root filesystem starts
|
flag are on, i.e., rdev -r /dev/fd0 49152, and that the root filesystem starts
|
||||||
at block
|
at block
|
||||||
0 on the other floppy.
|
0 on the other floppy.
|
||||||
However, the 2 disk compression method copies over a compressed (gz or bz2)
|
However, the 2 disk compression method was designed to uncompress bzip2
|
||||||
root filesystem
|
root filesystems as well as gzipped root filesystems from
|
||||||
to the second disk.  In order to boot /dev/fd0 from /dev/fd0 when
|
to the second disk.  In order to boot /dev/fd0 from /dev/fd0 when
|
||||||
the root
|
the root
|
||||||
filesystem is compressed with gzip or bzip2 the kernel has to
|
filesystem is compressed with bzip2 the kernel has to
|
||||||
mount the initial boot disk, and then after the new root disk is inserted it
|
mount the initial boot disk, and then after the new root disk is inserted it
|
||||||
uncompresses the root filesystem and then changes over to the real root
|
uncompresses the root filesystem and then changes over to the real root
|
||||||
device,
|
device,
|
||||||
@ -1207,7 +1209,35 @@ root. You can experiment with this by removing libc-*.so and
|
|||||||
ld-*.so from a root filesystem which previously worked, first test it with
|
ld-*.so from a root filesystem which previously worked, first test it with
|
||||||
UML, and then try to boot it; in both cases it won't work.
|
UML, and then try to boot it; in both cases it won't work.
|
||||||
|
|
||||||
<p><a name="15"><b>There isn't enough room left on my 1440 floppy to make a Boot or Root
|
|
||||||
|
<p><a name="15"><b>So if I understand correctly, it is not possible to copy libc from /dev/ram0 to /dev/ram1 before mounting /dev/ram1 as / ? </b></a> <a href="#FAQ">[back]</a></p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
|
||||||
|
Actually, this could be accomplished before the change_root or pivot_root
|
||||||
|
call, however, there is a much easier solution.
|
||||||
|
Make a working root
|
||||||
|
filesystem, edit it either on a loop device as root, or on a different
|
||||||
|
ubd?=root_fs as any user from a Linux virtual machine.
|
||||||
|
Add an initrd
|
||||||
|
device to the mounted filesystem with <code>mknod initrd b 1 250</code>
|
||||||
|
in the /dev
|
||||||
|
directory.
|
||||||
|
Make a directory called /initrd.
|
||||||
|
Delete libc*so and then
|
||||||
|
<code>ln -sf /initrd/lib/libc(real numbers)so libc*so</code>.
|
||||||
|
Umount, compress, and copy
|
||||||
|
over to your root disk (2 disk compression method - make sure compression
|
||||||
|
and filesystem name match).
|
||||||
|
The reason why this works is that the initrd
|
||||||
|
remains mounted if /dev/initrd and the directory /initrd exist on the root
|
||||||
|
filesystem after the root change.
|
||||||
|
Ofcourse, you won't be able to run the
|
||||||
|
filesystem without the initrd, but this is another great way to save
|
||||||
|
space.
|
||||||
|
|
||||||
|
|
||||||
|
<p><a name="16"><b>There isn't enough room left on my 1440 floppy to make a Boot or Root
|
||||||
disk. Is there any way to free up more space apart from reducing
|
disk. Is there any way to free up more space apart from reducing
|
||||||
the size of the kernel?</b></a> <a href="#FAQ">[back]</a></p>
|
the size of the kernel?</b></a> <a href="#FAQ">[back]</a></p>
|
||||||
|
|
||||||
@ -1244,7 +1274,7 @@ to add your comments to the Feature Request. Thanks.</p>
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<a name="16"><b>Last, but not least...the boot disk boots, waits for the root disk, and
|
<a name="17"><b>Last, but not least...the boot disk boots, waits for the root disk, and
|
||||||
now fails. "Can't open console"??? or sth like this (I'm pretty tired
|
now fails. "Can't open console"??? or sth like this (I'm pretty tired
|
||||||
right now, recheck later), which appears after "VFS:ext2fs was found..."</b></a> <a href="#FAQ">[back]</a></P>
|
right now, recheck later), which appears after "VFS:ext2fs was found..."</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
|
|
||||||
@ -1267,7 +1297,7 @@ to make sure your filesystem is running properly.
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<a name="17"><b>What are the kernel's drivers/fs that must be directly compiled, not as
|
<a name="18"><b>What are the kernel's drivers/fs that must be directly compiled, not as
|
||||||
modules, except ext2, floppy? Could you attach your
|
modules, except ext2, floppy? Could you attach your
|
||||||
kernel's .config?</b></a> <a href="#FAQ">[back]</a></P>
|
kernel's .config?</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
|
|
||||||
@ -1289,7 +1319,7 @@ here.
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<a name="18"><b>What is the root_fs_helper 2Mb file in the grootboot package?</b></a> <a href="#FAQ">[back]</a></P>
|
<a name="19"><b>What is the root_fs_helper 2Mb file in the grootboot package?</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
@ -1311,7 +1341,7 @@ to unless Preserve Ownership is off.
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<a name="19"><b>Now the creation works, but actually the whole image is less than
|
<a name="20"><b>Now the creation works, but actually the whole image is less than
|
||||||
1440k... Still, unclear to me is the purpose of the device/size in the
|
1440k... Still, unclear to me is the purpose of the device/size in the
|
||||||
main widget - is it only for the boot or also for the root disk?
|
main widget - is it only for the boot or also for the root disk?
|
||||||
After all, the root fs image size has been already entered in the ARS.</b></a> <a href="#FAQ">[back]</a></P>
|
After all, the root fs image size has been already entered in the ARS.</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
@ -1339,11 +1369,11 @@ represents the mounted device provided in the main section.
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<a name="20"><b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></a> <a href="#FAQ">[back]</a></P>
|
<a name="21"><b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></a> <a href="#FAQ">[back]</a></P>
|
||||||
|
|
||||||
<p>This program requires Gtk-Perl available from <a href="http://www.perl.com/CPAN">CPAN</a>, <a href="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
|
<p>This program requires Gtk-Perl available from <a href="http://www.perl.com/CPAN">CPAN</a>, <a href="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
|
||||||
|
|
||||||
<p><a name="21"><b>If you roll the floppy density counter down to 0 and then try go back
|
<p><a name="22"><b>If you roll the floppy density counter down to 0 and then try go back
|
||||||
up towards 1440 and 1722, you get very funny figures.</b></a> <a href="#FAQ">[back]</a></p>
|
up towards 1440 and 1722, you get very funny figures.</b></a> <a href="#FAQ">[back]</a></p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
@ -1390,7 +1420,7 @@ page up with the second button to 1440 and step with the first button to
|
|||||||
<LI> Ctrl-V Paste from clipboard </LI>
|
<LI> Ctrl-V Paste from clipboard </LI>
|
||||||
</UL>
|
</UL>
|
||||||
|
|
||||||
<p><a name="22"><b>Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</b></a> <a href="#FAQ">[back]</a></p>
|
<p><a name="23"><b>Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</b></a> <a href="#FAQ">[back]</a></p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user