Michael Biebl wrote:
> Magnus Therning wrote:
>
>
>> It doesn't seem to work for me. These are the steps I take to create my
>> encrypted partition:
>>
>> # cryptsetup luksFormat /dev/sdc
>> # cryptsetup luksOpen /dev/sdc silly
>> # mkfs.ext3 -L silly /dev/mapper/silly
>> # cryptsetup luksC
Magnus Therning wrote:
>
> It doesn't seem to work for me. These are the steps I take to create my
> encrypted partition:
>
> # cryptsetup luksFormat /dev/sdc
> # cryptsetup luksOpen /dev/sdc silly
> # mkfs.ext3 -L silly /dev/mapper/silly
> # cryptsetup luksClose /dev/mapper/silly
>
> Then
Michael Biebl wrote:
> Magnus Therning wrote:
>
>> On Wed, May 23, 2007 at 12:19:51 +0200, Michael Biebl wrote:
>>
>>> Magnus Therning wrote:
>>>
On Sun, Apr 22, 2007 at 01:01:22 +0200, Michael Biebl wrote:
>> exists, but the "luks mapping" didn't happened auto
Magnus Therning wrote:
> On Wed, May 23, 2007 at 12:19:51 +0200, Michael Biebl wrote:
>> Magnus Therning wrote:
>>> On Sun, Apr 22, 2007 at 01:01:22 +0200, Michael Biebl wrote:
> exists, but the "luks mapping" didn't happened automatically. So after=
> a while I started gnome-volume-manage
On Wed, May 23, 2007 at 12:19:51 +0200, Michael Biebl wrote:
>Magnus Therning wrote:
>> On Sun, Apr 22, 2007 at 01:01:22 +0200, Michael Biebl wrote:
exists, but the "luks mapping" didn't happened automatically. So after=
a while I started gnome-volume-manager and the "luks mapping" appea
Magnus Therning wrote:
> On Sun, Apr 22, 2007 at 01:01:22 +0200, Michael Biebl wrote:
>>> exists, but the "luks mapping" didn't happened automatically. So after=
>>> a while I started gnome-volume-manager and the "luks mapping" appeared
>>> together with /dev/dm-3. No automatic mounting of the en
On Sun, Apr 22, 2007 at 01:01:22 +0200, Michael Biebl wrote:
>> exists, but the "luks mapping" didn't happened automatically. So after=
>
>> a while I started gnome-volume-manager and the "luks mapping" appeared
>> together with /dev/dm-3. No automatic mounting of the encrypted
>> partition thoug
Magnus Therning wrote:
> On Fri, Apr 20, 2007 at 17:45:49 +0200, Michael Biebl wrote:
>> Have you stopped the running hald instance at first? If not, run
>> "/etc/dbus-1/event.d/20hal stop", and then rerun "hald --daemon=3Dno
>> --verbose=3Dyes". Otherwise we don't get a useful output of hald.
>=20
Magnus Therning schrieb:
> Package: hal
> Version: 0.5.8.1-9
> Severity: normal
>
>>
>> It's most likely a problem within hal or udev.
>> After unlocking the crypto device, do you have a /dev/dm-0 device?
>> If not, what does grep dm /etc/udev/rules.d/* say?
>> Do you have a rule which suppresses
Package: hal
Version: 0.5.8.1-9
Severity: normal
Raising this after a discussion on the gtk-gnome list:
http://lists.debian.org/debian-gtk-gnome/2007/04/msg00028.html
Added the following in an email CCd to
[EMAIL PROTECTED]:
>This is getting offtopc for this list, so I changed to pkg-utopia.
>
>
10 matches
Mail list logo
