G'day!
I AM LOST!
I read the FAQ (section 14), read man bioctl, read stsp@'s article on
undeadly.org and a couple of other sites on the 'net: IT IS NOT POSSIBLE
TO INSTALL A FULLY ENCRYPTED SYSTEM WITH KEYDISK FOLLOWING THE
DOCUMENTATION on an amd64-current system!
Full stop! (~current = the
On 2015-12-10, Stefan Wollny wrote:
> G'day!
>
> I AM LOST!
>
> I read the FAQ (section 14), read man bioctl, read stsp@'s article on
> undeadly.org and a couple of other sites on the 'net: IT IS NOT POSSIBLE
> TO INSTALL A FULLY ENCRYPTED SYSTEM WITH KEYDISK FOLLOWING THE
> DOCUMENTATION on an
On Thu, December 10, 2015 6:35 pm, Stefan Wollny wrote:
> YES: I did 'disklabel -E sd0' and 'disklabel -E sd1' accordingly,
setting every partition to type RAID
How many partitions are you making on sd0? For FDE, typically you make
one partition of type RAID filling the disk (or your desired Open
On December 11, 2015 1:27:52 AM GMT+01:00, Stuart Henderson
wrote:
>On 2015-12-10, Stefan Wollny wrote:
>> YES: I did 'bioctl -C force -c C -l /dev/sd0d -k /dev/sd1d softraid0'
>> YES: I did again 'sh ./MAKEDEV all' to catch the newly created sd2
>
>In the above step, you have run yourself out
On Thu, Dec 10, 2015 at 07:33:57PM -0500, trondd wrote:
On Thu, December 10, 2015 6:35 pm, Stefan Wollny wrote:
YES: I did 'disklabel -E sd0' and 'disklabel -E sd1' accordingly,
setting every partition to type RAID
How many partitions are you making on sd0? For FDE, typically you make
one par
On Fri, Dec 11, 2015 at 09:53:48AM +0100, Alexander Hall wrote:
> On December 11, 2015 1:27:52 AM GMT+01:00, Stuart Henderson
> wrote:
> >On 2015-12-10, Stefan Wollny wrote:
>
> >> YES: I did 'bioctl -C force -c C -l /dev/sd0d -k /dev/sd1d softraid0'
> >> YES: I did again 'sh ./MAKEDEV all' to
On Thu, Dec 10, 2015 at 07:33:57PM -0500, trondd wrote:
On Thu, December 10, 2015 6:35 pm, Stefan Wollny wrote:
YES: I did 'disklabel -E sd0' and 'disklabel -E sd1' accordingly,
setting every partition to type RAID
How many partitions are you making on sd0? For FDE, typically you make
one par
> Gesendet: Freitag, 11. Dezember 2015 um 11:33 Uhr
> Von: "Stefan Sperling"
> An: "Alexander Hall"
> Cc: "Stuart Henderson" , misc@openbsd.org
> Betreff: Re: NOT POSSIBLE: Fully encrypted system with keydisk
>
> On Fri, Dec 11, 2015 at 09:53:4
On Fri, Dec 11, 2015 at 01:18:55PM +0100, Stefan Wollny wrote:
> OK - follow up problem: After the installation on /dev/sd3 (plus setting up
> /dev/sd4 for /home) I did not reboot but run installboot(8) like so:
> # /usr/sbin/installboot sd3
>
> This last produced an error message about /usr/mdec
> Gesendet: Freitag, 11. Dezember 2015 um 14:52 Uhr
> Von: "Stefan Sperling"
> An: "Stefan Wollny"
> Cc: misc@openbsd.org
> Betreff: Re: NOT POSSIBLE: Fully encrypted system with keydisk
>
> On Fri, Dec 11, 2015 at 01:18:55PM +0100, Stefan Wollny wro
On Fri, Dec 11, 2015 at 03:30:04PM +0100, Stefan Wollny wrote:
Gesendet: Freitag, 11. Dezember 2015 um 14:52 Uhr
Von: "Stefan Sperling"
An: "Stefan Wollny"
Cc: misc@openbsd.org
Betreff: Re: NOT POSSIBLE: Fully encrypted system with keydisk
On Fri, Dec 11, 2015 at 01:1
On Fri, Dec 11, 2015 at 03:30:04PM +0100, Stefan Wollny wrote:
> I run the command like you adviced and no error message showed up.
>
> So far, so good - unfortunatelly the system still does not boot after the
> 'reboot'. Still stops at the manufacturers splash screen not recognizing any
> stora
On 2015-12-11, Stefan Wollny wrote:
> @stuart: dd fails with "file system ist full \ dd: /dev/rsd3c: No space left
> on device"
Guessing that you didn't create the sd3 device nodes before doing the dd.
At this point you probably have a file (not device node) named /dev/rsd3c.
On Fri, Dec 11, 2015 at 05:44:36PM +0100, Stefan Wollny wrote:
> fdisk(25692): syscall 54 "ioctl"
> Abort trap
> > disklabel sd3
> disklabel(3120): syscall 54 "ioctl"
> Abort trap
This is obviously not quite right.
It looks like you're using a snapshot with a pledge(2) bug.
What snapshot are yo
Am 12/11/15 um 18:34 schrieb Stefan Sperling:
On Fri, Dec 11, 2015 at 05:44:36PM +0100, Stefan Wollny wrote:
fdisk(25692): syscall 54 "ioctl"
Abort trap
disklabel sd3
disklabel(3120): syscall 54 "ioctl"
Abort trap
This is obviously not quite right.
It looks like you're using a snapshot wit
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
On Sat, Dec 12, 2015 at 12:27:46AM +0100, Stefan Wollny wrote:
> Am 12/11/15 um 18:34 schrieb Stefan Sperling:
> >On Fri, Dec 11, 2015 at 05:44:36PM +0100, Stefan Wollny wrote:
> >>fdisk(25692): syscall 54 "ioctl"
> >>Abort trap
>
On Sat, Dec 12, 2015 at 12:27:46AM +0100, Stefan Wollny wrote:
> Am 12/11/15 um 18:34 schrieb Stefan Sperling:
> >On Fri, Dec 11, 2015 at 05:44:36PM +0100, Stefan Wollny wrote:
> >>fdisk(25692): syscall 54 "ioctl"
> >>Abort trap
> >>> disklabel sd3
> >>disklabel(3120): syscall 54 "ioctl"
> >>Abor
On Sat, Dec 12, 2015 at 12:51:33AM +0100, Stefan Wollny wrote:
>
>
> Gesendet??von??meinem??BlackBerry??10-Smartphone.
> ?? Originalnachricht ??
> ???On Sat, Dec 12, 2015 at 12:27:46AM +0100, Stefan Wollny wrote:
> > Am 12/11/15 um 18:34 schrieb Stefan Sperling:
> > >On Fri, Dec 11, 2015 at 05:44
On Sat, Dec 12, 2015 at 12:27:46AM +0100, Stefan Wollny wrote:
> Am 12/11/15 um 18:34 schrieb Stefan Sperling:
> >On Fri, Dec 11, 2015 at 05:44:36PM +0100, Stefan Wollny wrote:
> >>fdisk(25692): syscall 54 "ioctl"
> >>Abort trap
> >>> disklabel sd3
> >>disklabel(3120): syscall 54 "ioctl"
> >>Abor
19 matches
Mail list logo
