Ed Greshko wrote:
Robin Laing wrote:
On 01/21/2010 08:32 AM, Ed Greshko wrote:
Dr. Michael J. Chudobiak wrote:
On 01/21/2010 09:40 AM, Bryn M. Reeves wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
On Thu, 2010-01-28 at 10:07 -0500, Bill Davidsen wrote:
Ed Greshko wrote:
The OP has some external encrypted disks that are not critical to system
operation. Other functions of the system are critical. The system is
configured to reboot when power is restored after a power failure. If
Robin Laing wrote:
On 01/21/2010 08:32 AM, Ed Greshko wrote:
Dr. Michael J. Chudobiak wrote:
On 01/21/2010 09:40 AM, Bryn M. Reeves wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
What
Robert Nichols wrote:
Bill Davidsen wrote:
Hum, I expected an answer on this one, guess I'm not the only one with no
fits
all cases answer. The only solution I found was to rewrite hal rules not to
auto-mount anything of any nature, which is ugly but better than fail to
boot.
Didn't
Bill Davidsen wrote:
Robert Nichols wrote:
Bill Davidsen wrote:
Hum, I expected an answer on this one, guess I'm not the only one with no
fits
all cases answer. The only solution I found was to rewrite hal rules not
to
auto-mount anything of any nature, which is ugly but better than
Robert Nichols wrote:
In my Fedora 12 system, if an external LUKS encrypted volume happens to be
connected to the system while it is booting, the boot sequence blocks
waiting for the password. This means that my system cannot boot unattended
(perhaps following a power failure) if an encrypted
Bill Davidsen wrote:
Robert Nichols wrote:
In my Fedora 12 system, if an external LUKS encrypted volume happens to be
connected to the system while it is booting, the boot sequence blocks
waiting for the password. This means that my system cannot boot unattended
(perhaps following a power
Kevin Fenzi wrote:
On Wed, 20 Jan 2010 19:52:11 -0600
Robert Nichols rnicholsnos...@comcast.net wrote:
In my Fedora 12 system, if an external LUKS encrypted volume happens
to be connected to the system while it is booting, the boot sequence
blocks waiting for the password. This means
Bryn M. Reeves wrote:
On Wed, 2010-01-20 at 19:45 -0700, Kevin Fenzi wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
But that doesn't seem to help if you have LUKS devices that you do want
activated during boot (I haven't
Dr. Michael J. Chudobiak wrote:
On 01/21/2010 09:40 AM, Bryn M. Reeves wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
But that doesn't seem to help if you have LUKS devices that you do want
activated during boot
On Thu, 2010-01-21 at 10:24 -0500, Dr. Michael J. Chudobiak wrote:
On 01/21/2010 09:40 AM, Bryn M. Reeves wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
But that doesn't seem to help if you have LUKS devices that you
On Thu, 2010-01-21 at 09:31 -0600, Robert Nichols wrote:
Bryn M. Reeves wrote:
On Wed, 2010-01-20 at 19:45 -0700, Kevin Fenzi wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
But that doesn't seem to help if you
On Thu, 2010-01-21 at 23:32 +0800, Ed Greshko wrote:
Dr. Michael J. Chudobiak wrote:
On 01/21/2010 09:40 AM, Bryn M. Reeves wrote:
From:
https://fedoraproject.org/wiki/Dracut/Options#crypto_LUKS
Pass: rd_NO_LUKS to your kernel boot line.
But that doesn't seem to help if
On Thu, 21 Jan 2010 23:32:51 +0800
Ed Greshko ed.gres...@greshko.com wrote:
What happens if you normally want a particular uuid to be activated on
boot...but there is a power fail and restore at 3am? Wouldn't you
still be stuck with a system waiting for the password when what you
may want
On Wed, 20 Jan 2010 19:52:11 -0600
Robert Nichols rnicholsnos...@comcast.net wrote:
In my Fedora 12 system, if an external LUKS encrypted volume happens
to be connected to the system while it is booting, the boot sequence
blocks waiting for the password. This means that my system cannot
boot
15 matches
Mail list logo
