Hi Tim,
On 20/12/10 03:10, Tim Darby wrote:
> [...] It issues the kill command but udevd apparently
> never responds. This might explain why /tmp fails to unmount and also
> the seg-fault error. I tried editing the rc script to change "kill
> $UDEVD_PID" to "kill -9" and those messages went away
Tim Darby wrote:
Chris: agreed, email is not the best way to document things. I've
experienced that same frustration trying to track down some important
detail that only ever appeared in an email thread.
well more my point was that DF stuff should be centralized on project
infrastructure - b
I've got more info on the messages I'm seeing below. I've determined that
the initrd rc script is failing to kill udevd at the end when it is cleaning
things up. It issues the kill command but udevd apparently never responds.
This might explain why /tmp fails to unmount and also the seg-fault er
Chris: agreed, email is not the best way to document things. I've
experienced that same frustration trying to track down some important detail
that only ever appeared in an email thread.
That said, I have a few more questions. :)
I now have encrypted root and encrypted swap set up (thanks, Alex)
Alex Hornung wrote:
For whatever it's worth,
I've added a task to google code-in a few weeks ago to document all this
dm stuff, both cryptsetup and lvm, basically.
A bit OT but shouldn't this stuff go in bugs / the wiki and then be
referenced to any "google code-in" or "foo barbaz-quux" to pre
Thanks! Yes, I'm using master because I need it for the SATA ports on my
motherboard. I'd be willing to put up some documentation for this stuff,
but I don't want to snatch the google code-in opportunity away from some
deserving person. ;-)
Tim
On Mon, Dec 13, 2010 at 12:00 AM, Alex Hornung w
I'm assuming you are using the 'master' branch, otherwise the
dm_target_crypt_load="YES" is not necessary. For whatever it's worth,
I've added a task to google code-in a few weeks ago to document all this
dm stuff, both cryptsetup and lvm, basically. Hopefully there will be a
taker.
For encry
I'm trying to set up an encrypted root filesystem with disk A containing
/boot and swap and disk B containing the encrypted root. Having never done
this before, I figured I'd use /share/examples/rconfig/encrypted_root.sh as
a guide. However, I ran into a couple of snags, so maybe someone can tell
