> On Sat, 8 Mar 2014, Theo de Raadt wrote:
> > > I follow "-current" for several years but recently a thing puzzles me.
> > >
> > > My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
> > > think) the "amd64/i386 installboot" change, each time I upgrade via
> > > "bsd.rd", I h
> To be clear, the old amd64/i386 installboot never updated /boot - it only
> ever
> patched biosboot and installed it into the PBR. It was entirely up to the
> user (or the install script) to copy /usr/mdec/boot file to /boot - if you
> used cp or cat the old PBR may have continued to work, bu
On Sat, 8 Mar 2014, Theo de Raadt wrote:
> > I follow "-current" for several years but recently a thing puzzles me.
> >
> > My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
> > think) the "amd64/i386 installboot" change, each time I upgrade via
> > "bsd.rd", I have to gener
Le 07/03/2014 12:13 PM, Theo de Raadt a écrit :
actually more painful than having to boot windows is to always have
something handy to boot the snap from in order to dd the bootblock off
in case you forget to do it before rebooting, or you're fucked.
The new installboot was enabled around a mon
Le 07/03/2014 12:02 PM, Bob Beck a écrit :
actually more painful than having to boot windows is to always have
something handy to boot the snap from in order to dd the bootblock off
in case you forget to do it before rebooting, or you're fucked.
Hi Bob,
Yeah and hopefully, with a recent post
> >> > Meaning that the pbr must be updated with the new location.
> >>
> >> It doesn't just "tend" to move around (ie. tend == "prone to move").
> >> It moves every time, since it is using mkstemp to create a new file.
> >
> > But isn't this a good thing?
> >
> > Now it moves around consistentl
On Fri, Mar 07, 2014 at 17:44, Mark Kettenis wrote:
>> > Meaning that the pbr must be updated with the new location.
>>
>> It doesn't just "tend" to move around (ie. tend == "prone to move").
>> It moves every time, since it is using mkstemp to create a new file.
>
> But isn't this a good thing?
t; -Original Message-
> From: Bob Beck [mailto:b...@obtuse.com]
> Sent: Friday, March 07, 2014 2:01 PM
> To: Kenneth Westerback
> Cc: Wade, Daniel; OpenBSD Tech
> Subject: Re: 5.5 and dual-boot
>
> ... although having scripted the fdisk on openbsd quite nicely so I
> can&#
riday, March 07, 2014 2:01 PM
To: Kenneth Westerback
Cc: Wade, Daniel; OpenBSD Tech
Subject: Re: 5.5 and dual-boot
... although having scripted the fdisk on openbsd quite nicely so I
can't screw it up, proceeed to forget that windows numbers partitions
starting at 1, not 0, in diskpart, and am n
;>
>> Ken
>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of
>> Bob Beck
>>> Sent: Friday, March 07, 2014 12:15 PM
>>> To: Theo de Raad
in mg just to keep that line alive! :-)
>
> Ken
>
>>
>>
>>
>> -Original Message-
>> From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of
> Bob Beck
>> Sent: Friday, March 07, 2014 12:15 PM
>> To: Theo de Raadt
: Friday, March 07, 2014 12:15 PM
> To: Theo de Raadt
> Cc: Mark Kettenis; Stuart Henderson; Jean-Philippe Luiggi; OpenBSD
technical list
> Subject: Re: 5.5 and dual-boot
>
> It will affect everyone who needs windows on a laptop for work - or
> filling out pdf forms for foundations,
--Original Message-
From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of Bob
Beck
Sent: Friday, March 07, 2014 12:15 PM
To: Theo de Raadt
Cc: Mark Kettenis; Stuart Henderson; Jean-Philippe Luiggi; OpenBSD technical
list
Subject: Re: 5.5 and dual-boot
It will affect ev
It will affect everyone who needs windows on a laptop for work - or
filling out pdf forms for foundations, things like that.
It is a good way to ensure snaps get tested less on real hardware.
On Fri, Mar 7, 2014 at 10:13 AM, Theo de Raadt wrote:
>> actually more painful than having to boot windo
> actually more painful than having to boot windows is to always have
> something handy to boot the snap from in order to dd the bootblock off
> in case you forget to do it before rebooting, or you're fucked.
The new installboot was enabled around a month ago. The issue is only
being talked about
Le 2014-03-07 11:24, Bob Beck a écrit :
If you're using windows bootloader, you need to re-get the openbsd.pbr
file to the windows side like you did in the first place
according to the instructions here:
http://www.openbsd.org/faq/faq4.html#Multibooting
Someone really needs to put it in the mul
actually more painful than having to boot windows is to always have
something handy to boot the snap from in order to dd the bootblock off
in case you forget to do it before rebooting, or you're fucked.
On Fri, Mar 7, 2014 at 9:50 AM, Bob Beck wrote:
> before it was just that you had to be aware
Le 2014-03-07 11:21, Stuart Henderson a écrit :
On 2014/03/07 11:04, Jean-Philippe Luiggi wrote:
Hi everybody,
I follow "-current" for several years but recently a thing puzzles me.
My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
think) the
"amd64/i386 installboot" c
before it was just that you had to be aware to redo it when something
changed. (which for me usually means booting from external media,
dd'ing the pbr file onto a usb stick, booting into windows, and
copying it into the right place.
having to boot windows every time you upgrade is a pain.
On Fri,
No, because moving it means that you have to manually redo it every
time you install a snap. which is really a pita.
On Fri, Mar 7, 2014 at 9:44 AM, Mark Kettenis wrote:
>> From: Theo de Raadt
>> Date: Fri, 07 Mar 2014 09:24:13 -0700
>>
>> > Whereas new installboot tends to shift it around:
>>
> From: Theo de Raadt
> Date: Fri, 07 Mar 2014 09:24:13 -0700
>
> > Whereas new installboot tends to shift it around:
> >
> > # installboot -v sd1 2>&1 | grep shift
> > fs block shift 2; part offset 64; inode block 56, offset 2344
> > # installboot -v sd1 2>&1 | grep shift
> > fs block shift 2;
>>
>> Meaning that the pbr must be updated with the new location.
>
> It doesn't just "tend" to move around (ie. tend == "prone to move").
> It moves every time, since it is using mkstemp to create a new file.
Hmm.. yeah that'll be fun to deal with in multi-boot setups.
> Whereas new installboot tends to shift it around:
>
> # installboot -v sd1 2>&1 | grep shift
> fs block shift 2; part offset 64; inode block 56, offset 2344
> # installboot -v sd1 2>&1 | grep shift
> fs block shift 2; part offset 64; inode block 48, offset 16168
> # installboot -v sd1 2>&1 | gr
If you're using windows bootloader, you need to re-get the openbsd.pbr
file to the windows side like you did in the first place
according to the instructions here:
http://www.openbsd.org/faq/faq4.html#Multibooting
Someone really needs to put it in the multiboot FAQ that if you're
booting with the
On 2014/03/07 11:04, Jean-Philippe Luiggi wrote:
> Hi everybody,
>
> I follow "-current" for several years but recently a thing puzzles me.
>
> My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
> think) the
> "amd64/i386 installboot" change, each time I upgrade via "bsd.r
> I follow "-current" for several years but recently a thing puzzles me.
>
> My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
> think) the
> "amd64/i386 installboot" change, each time I upgrade via "bsd.rd", I have to
> generate a new "openbsd.pbr" and copy it to "Seven
Hi everybody,
I follow "-current" for several years but recently a thing puzzles me.
My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I
think) the
"amd64/i386 installboot" change, each time I upgrade via "bsd.rd", I have to generate a new
"openbsd.pbr" and copy it to "S
27 matches
Mail list logo
