initial ramdisk in ubuntu

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to view Ramdisk Initialization Process

Dear all, I read some articles about initrd, but how to view this process in my computer :(? Is there anyway to display to the screen or write to the log file?

2. AIX

maximum size of a ramdisk on AIX 5.3

Hi, Do you know what is the maximum size I can use to create a ramdisk on AIX 5.3? I m pretty sure i've seen somewhere i can use more than 2 Gb but I can't remember where. I need to do some recommandations for one of my customer and they'll need to create a ramdisk of 20 Gb. Can this be done? ...

3. Shell Programming and Scripting

Sorting in ramdisk

Hi, I have sort command that sorts in ramdisk created by a script 'mktd' and later unmounted by script 'rmtd'. The platform is AIX. # code sudo -E mktd 44 # create ramdisk of size 44GB sort ... -k1,1 -2,2 ... # sort a file using the ramdisk on keys 1 and 2 sudo -E rmtd # unmount...

4. Shell Programming and Scripting

Ramdisk already defined

I am trying to mount the ramdisk for sorting, and i get the message "ramdisk already defined." What exactly is /dev/ramdisk0 and is it safe to remove it? # command sudo -S mktd 60 <<EOF initiate EOF # block of code for mktd ... && { print "ramdisk already defined." ...

5. Shell Programming and Scripting

how to create a ramdisk

Hi all, I wanted to make a ramdisk for a opensolaris distro. I have very little idea of how to create it? can anyone pls help me out? Is there any tutorial on creating it on the net??? Also can i make changes to the actual os itself by changing the scripts involved in ramdisk then use it to...

6. UNIX for Dummies Questions & Answers

Unix ramdisk?

This may be a stupid question but I've noticed that there is quite a bit out there currently for a ramdisk on that Redmond company's OS. Is there a ramdisk made for Unix and if not, why?

LEARN ABOUT OSX

systemd-cryptsetup-generator

SYSTEMD-CRYPTSETUP-GENERATOR(8) 			   systemd-cryptsetup-generator 			   SYSTEMD-CRYPTSETUP-GENERATOR(8)

NAME

       systemd-cryptsetup-generator - Unit generator for /etc/crypttab

SYNOPSIS

       /lib/systemd/system-generators/systemd-cryptsetup-generator

DESCRIPTION

       systemd-cryptsetup-generator is a generator that translates /etc/crypttab into native systemd units early at boot and when configuration of
       the system manager is reloaded. This will create systemd-cryptsetup@.service(8) units as necessary.

       systemd-cryptsetup-generator implements systemd.generator(7).

KERNEL COMMAND LINE

       systemd-cryptsetup-generator understands the following kernel command line parameters:

       luks=, rd.luks=
	   Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely.  rd.luks= is honored only by initial RAM disk
	   (initrd) while luks= is honored by both the main system and the initrd.

       luks.crypttab=, rd.luks.crypttab=
	   Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any devices configured in /etc/crypttab
	   (luks.uuid= will still work however).  rd.luks.crypttab= is honored only by initial RAM disk (initrd) while luks.crypttab= is honored
	   by both the main system and the initrd.

       luks.uuid=, rd.luks.uuid=
	   Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in
	   /etc/crypttab. This option may be specified more than once in order to set up multiple devices.  rd.luks.uuid= is honored only by
	   initial RAM disk (initrd) while luks.uuid= is honored by both the main system and the initrd.

	   If /etc/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the
	   device will have the name "luks-UUID".

	   If /etc/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.

       luks.name=, rd.luks.name=
	   Takes a LUKS super block UUID followed by an "=" and a name. This implies rd.luks.uuid= or luks.uuid= and will additionally make the
	   LUKS device given by the UUID appear under the provided name.

	   rd.luks.name= is honored only by initial RAM disk (initrd) while luks.name= is honored by both the main system and the initrd.

       luks.options=, rd.luks.options=
	   Takes a LUKS super block UUID followed by an "=" and a string of options separated by commas as argument. This will override the
	   options for the given UUID.

	   If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in
	   /etc/crypttab.

	   rd.luks.options= is honored only by initial RAM disk (initrd) while luks.options= is honored by both the main system and the initrd.

       luks.key=, rd.luks.key=
	   Takes a password file name as argument or a LUKS super block UUID followed by a "=" and a password file name.

	   For those entries specified with rd.luks.uuid= or luks.uuid=, the password file will be set to the one specified by rd.luks.key= or
	   luks.key= of the corresponding UUID, or the password file that was specified without a UUID.

	   rd.luks.key= is honored only by initial RAM disk (initrd) while luks.key= is honored by both the main system and the initrd.

SEE ALSO

       systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8), systemd-fstab-generator(8)

systemd 237													   SYSTEMD-CRYPTSETUP-GENERATOR(8)

Ubuntu