03-27-2009
yes i get a choice to select from. i pressed 'e' on the item i normally select and i get this:
root 08e28692-0f58-4adl-a240-7c617d1ff6d8
kernel /boot/vmlinuz-2.6.27-7 generic root=uuid=0828692-0f58-4adl-a-
initrd /boot/initrd.img-2.6.27-7-generic
what does that all mean?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have installed windows on this c: drive
i have linux installed on drive d:
when i disconnect d: it boots into c: into windows
when i have both drives connected it stops after sys check.
how do i get a dual boot goin ???? or a boot loader and if i reinstall linux 7. where should i... (1 Reply)
Discussion started by: perleo
1 Replies
2. UNIX for Dummies Questions & Answers
Hello,
One of my frend had a problem.
He had Windows XP installed on his system. Then he installed Red Hat Linux 8.0 in one of the partitions. After some time his XP got corrupt and then he reinstalled Windows XP. This over wrote the Grub loader entry, and due to this the grub loader is not... (2 Replies)
Discussion started by: rahulrathod
2 Replies
3. Shell Programming and Scripting
Hi Guys,
I am looking to develop a SQL Loader script that would bascially allow the user to have a txt file (or such) as an input file containing .sql scripts procedures, triggers, bascially anything against a database that could then be run automatically.
Let me break it down a bit more,... (2 Replies)
Discussion started by: LiquidChild
2 Replies
4. UNIX for Dummies Questions & Answers
Hi, I installed solaris 10 a few weeks ago. It was working fine during the past two weeks. However, now when I start to load to the drive, I get this problem:
The BIOS screen comes up like normal, then screen goes blank and a message "Grub loading stage 2" flashes real quick then the computer... (1 Reply)
Discussion started by: moesays
1 Replies
5. UNIX for Dummies Questions & Answers
I currently have Gutsy, Fedora Core 7, and Vista running on the same hard disk and want to add XP to it. XP will of course kill my grub which I can get back with supergrub easily. I have no worries that my two Linux Distros will come back when I do this because Grub only points from the mbr to... (2 Replies)
Discussion started by: dancingfool
2 Replies
6. Shell Programming and Scripting
hi all
i am new to shell scripting.
i have 35 flat files delimited files that i have to load in to a table.
i was asked to create a shell script that loads the data into the table...
could you please help me if you have a script.
Also .. how to create logs files...does my sql... (3 Replies)
Discussion started by: rajesh_tns
3 Replies
7. Solaris
Hi to everyone ;)
Yesterday I had to reinstall my dual boot because my bank smart card reader does not work with Solaris so I reinstalled Solaris after I installed Windows 7.
When I turn on PC I get grub stage 2 and Solaris has made an entry in menu.lst but does not boot windows .
Each OS... (4 Replies)
Discussion started by: solaris_user
4 Replies
8. UNIX for Dummies Questions & Answers
HI Experts,
We have a ksh file named ldr_empdelta.ksh and it is having the SQL*LOADER script as follows.
print "LOAD DATA" > $WEDB_GEN/ldrscan.ctl
print "INFILE '"$LED_SCAN"/delta/led_del.dat'" >> $WEDB_GEN/ldrparms.ctl
print "TRUNCATE" >> $WEDB_GEN/ldrscan.ctl
print "PRESERVE BLANKS" >>... (1 Reply)
Discussion started by: ajaykumarkona
1 Replies
9. Red Hat
Hi,
Can we specify which grub.conf to use while installing grub on RHEL.
We are working on application which requires different grub configurations needed, depending on certain criteria we need to update grub with correct grub.conf.
Can we use grub-install for this purpose? (4 Replies)
Discussion started by: successlin
4 Replies
10. UNIX for Dummies Questions & Answers
can someone please explain me the difference between these two files:
"/boot/grub/grub.conf" and "/etc/grub.conf" .. (7 Replies)
Discussion started by: stunn3r
7 Replies
LEARN ABOUT DEBIAN
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)