On Sat, 8 Jun 2013, Glen Barber wrote:
The problem is creating the gpart(8) partition scheme on the md(4)
device.
Below follows script(1) output of what the make-memstick.sh script does:
Script started on Sun Jun 9 00:41:08 2013
root@snap:/snap/releng # chroot /snap/releng/10-i386-snap
roo
On Sun, Jun 09, 2013 at 05:01:00AM +0900, Hiroki Sato wrote:
> gj> Because the userland is 32-bit and the kernel is 64-bit, "something"
> gj> goes wrong, but interestingly not wrong enough that the script fails
> gj> entirely. So, the paritions appear to be created, but in reality, they
> gj> are
On Sat, Jun 08, 2013 at 02:18:48PM -0500, Nathan Whitehorn wrote:
> On 06/08/13 14:17, Glen Barber wrote:
> > On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
> >> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> >>
> >>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>
On 06/08/13 14:17, Glen Barber wrote:
> On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>>
>>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> Has anyone else tried the i386 memstick and having the same problem?
>>>
Tim Kientzle wrote
in <926ef579-8ac9-4a98-8a81-4e978a627...@kientzle.com>:
ti>
ti> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
ti>
ti> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
ti> >>> Has anyone else tried the i386 memstick and having the same problem?
ti> >>>
ti> >>
t
Glen Barber wrote
in <20130608173411.gd13...@glenbarber.us>:
gj> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
gj> Because the userland is 32-bit and the kernel is 64-bit, "something"
gj> goes wrong, but interestingly not wrong enough that the script fails
gj> entirely. So, the
On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>
> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>
> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> >>> Has anyone else tried the i386 memstick and having the same problem?
> >>>
> >>
> >> Hmm. Thanks for the re
On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>>> Has anyone else tried the i386 memstick and having the same problem?
>>>
>>
>> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
>> they are generated the sa
On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> > Has anyone else tried the i386 memstick and having the same problem?
> >
>
> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
> they are generated the same way as the amd64, so in theory should not
> have any
On 06/07/13 22:51, Jimmy wrote:
Greetings -
I had originally started playing with the 10-CURRENT amd64 release
a couple of months ago (no complaints here - keep up the good work!)
and had used the memstick snapshot to set things up back then with
no problems.
Now I'd like to wipe everything and
On Fri, Jun 07, 2013 at 03:51:29PM -0500, Jimmy wrote:
> Greetings -
>
> I had originally started playing with the 10-CURRENT amd64 release
> a couple of months ago (no complaints here - keep up the good work!)
> and had used the memstick snapshot to set things up back then with
> no problems.
>
Greetings -
I had originally started playing with the 10-CURRENT amd64 release
a couple of months ago (no complaints here - keep up the good work!)
and had used the memstick snapshot to set things up back then with
no problems.
Now I'd like to wipe everything and switch to the i386 version, but
t
12 matches
Mail list logo
