- Apr 2018
-
git-scm.com git-scm.com
-
By setting $strict_export configuration variable (see gitweb.conf[5]) to true value you can allow viewing only of repositories also shown on the overview page (i.e. only projects explicitly listed in projects list file will be accessible).
-
-
sublimetexttips.com sublimetexttips.com
-
def plugin_loaded()
executed whenever it is loaded
-
- Mar 2018
-
wiki.archlinux.org wiki.archlinux.org
-
After this, proceed to install the Syslinux boot code (mbr.bin or gptmbr.bin) to the Master Boot Record 440-byte boot code region
so after
syslinux -i
command, writembr.bin
or something else toMBR
is needed -
For a partitionless install, there is no need to install the Syslinux boot code to the MBR.
this is a
exception
to above quotation
Tags
Annotators
URL
-
-
wiki.ubuntu.com wiki.ubuntu.com
-
decided by a file called as “order” kept in that dir
the file called
ORDER
is generated on creating the initramfs file, see the run_scripts function definition
-
-
git.launchpad.net git.launchpad.net
-
run_scripts()
mkinitramfs
automatically addORDER
file in folders likeinit-top
,local-premount
, which run the scripts in the folder in order.the order is determined by analysis the output of
prereqs()
function in all boot scripts. see this anotation -
# For boot time only; this is overridden at build time in hook-functions
this comment seems obsolete and wrong
-
-
manpages.ubuntu.com manpages.ubuntu.com
-
No guarantees are made as to the order in which the different scripts are executed unless the prereqs are setup in the script. Please notice that PREREQ is only honored inside a single directory. So first the scripts in /usr/share/initramfs-tools are ordered according to their PREREQ values and executed. Then all scripts in /etc/initramfs-tools are ordered according to their PREREQ values and executed.
PREREQ
is used to determine the execution order of hook scripts
-
-
elixir.bootlin.com elixir.bootlin.com
-
1) <hex_major><hex_minor> device number in hexadecimal represents itself * no leading 0x, for example b302. * 2) /dev/nfs represents Root_NFS (0xff) * 3) /dev/<disk_name> represents the device number of disk * 4) /dev/<disk_name><decimal> represents the device number * of partition - device number of disk plus the partition number * 5) /dev/<disk_name>p<decimal> - same as the above, that form is * used when disk name of partitioned disk ends on a digit. * 6) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the * unique id of a partition if the partition table provides it. * The UUID may be either an EFI/GPT UUID, or refer to an MSDOS * partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero- * filled hex representation of the 32-bit "NT disk signature", and PP * is a zero-filled hex representation of the 1-based partition number. * 7) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation to * a partition with a known unique id. * 8) <major>:<minor> major and minor number of the device separated by * a colon.
this is all possible valid formats passed to root= option in linux boot command line
-
-
man7.org man7.org
-
'rootflags=...'
if we use overlay fs, the mount options should be specified here.
-
'root=...'
maybe we can set it to
overlay
to mount a overlay filesystem.
-