The custom initrd format was originally useful when it was mounted, however it has been extracted into the ramfs for a very long time and has no advantages over the standard tar format which can be readily created and modified using standard tools. The kernel initrd(7) support already supports tar, so this change simply switches the format.
31 lines
622 B
Groff
31 lines
622 B
Groff
.Dd October 5, 2015
|
|
.Dt INITRD 7
|
|
.Os
|
|
.Sh NAME
|
|
.Nm initrd
|
|
.Nd initialization ramdisk
|
|
.Sh SYNOPSIS
|
|
.Pa /boot/sortix.initrd
|
|
.Sh DESCRIPTION
|
|
.Pa /boot/sortix.initrd
|
|
is a
|
|
.Xr tar 1
|
|
archive of a minimal userland loaded by the bootloader and passed to the
|
|
.Xr kernel 7
|
|
that extracts it into the initial kernel memory root filesystem.
|
|
The kernel invokes the
|
|
.Xr init 8
|
|
extracted from the initrd as
|
|
.Pa /sbin/init .
|
|
.Pp
|
|
The
|
|
.Xr update-initrd 8
|
|
program creates a minimal initrd that locates the root filesystem and chain
|
|
boots it as described in
|
|
.Xr init 8 .
|
|
.Sh SEE ALSO
|
|
.Xr tar 1 ,
|
|
.Xr kernel 7 ,
|
|
.Xr init 8 ,
|
|
.Xr update-initrd 8
|