On Tue, Jan 11, 2011 at 03:38:23AM +0300, Andrey V. Elsukov wrote:
> On 11.01.2011 02:33, Luigi Rizzo wrote:
> > As a consequence, if we reboot without pressing an F-key, the system
> > boots from partition s1 even though the boot loader indicates F2.
>
> > So, to summarize, I guess that a possibl
On 11.01.2011 02:33, Luigi Rizzo wrote:
> As a consequence, if we reboot without pressing an F-key, the system
> boots from partition s1 even though the boot loader indicates F2.
> So, to summarize, I guess that a possible fix (that does not involve
> using gpart, or even worse, modifying boot0.S,
In order to understand the bug discussed in the recent thread
(original message attached at the end), Tom Judge passed me the
dump of the boot sector around the bug.
The system giving trouble has the following configuration
Fresh transcript:
file1: ORIGINAL BOOT SECTOR
# boot0cfg -v ad0
#
On 01/09/2011 04:44 PM, Luigi Rizzo wrote:
> On Sun, Jan 09, 2011 at 12:57:24PM -0600, Tom Judge wrote:
>> On 09/01/2011 12:33, Luigi Rizzo wrote:
>>> On Sun, Jan 09, 2011 at 12:39:28AM -0600, Tom Judge wrote:
Hi,
Today I ran into an issue where setting the default slice with boot0cf
On 01/10/2011 02:27, Daniel Braniss wrote:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig0AE178BF2380C8CAA3249E0C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 09/01/2011 04:38, Daniel Braniss wrote:
There was a post o
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --enig0AE178BF2380C8CAA3249E0C
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> On 09/01/2011 04:38, Daniel Braniss wrote:
> >> There was a post on the embedded list that sugg
On Sun, Jan 09, 2011 at 12:57:24PM -0600, Tom Judge wrote:
> On 09/01/2011 12:33, Luigi Rizzo wrote:
> > On Sun, Jan 09, 2011 at 12:39:28AM -0600, Tom Judge wrote:
> >> Hi,
> >>
> >> Today I ran into an issue where setting the default slice with boot0cfg
> >> -s is broken.
> > a few questions inlin
On 09/01/2011 12:33, Luigi Rizzo wrote:
> On Sun, Jan 09, 2011 at 12:39:28AM -0600, Tom Judge wrote:
>> Hi,
>>
>> Today I ran into an issue where setting the default slice with boot0cfg
>> -s is broken.
> a few questions inline:
>
Output inline, full script log attached.
If you need more info let
On Sun, Jan 09, 2011 at 12:39:28AM -0600, Tom Judge wrote:
> Hi,
>
> Today I ran into an issue where setting the default slice with boot0cfg
> -s is broken.
a few questions inline:
> This is related to a section of this revision:
>
> + commit Warner's patch "orb $NOUPDATE,_FLAGS(%bp)"
> to av
On 09/01/2011 04:38, Daniel Braniss wrote:
>> There was a post on the embedded list that suggested this work around:
>> echo 'a 2' | fdisk -f /dev/stdin ad0
>> boot0cfg -s 2 ad0
>>
>> There are 2 issues with this:
>> 1) It can't be done without setting kern.geom.debugflags to 0x10.
>> 2) It
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --enig51B4786EC9D39188BAE04052
> Content-Type: multipart/mixed; boundary="070003060308030201090207"
>
> This is a multi-part message in MIME format.
> --070003060308030201090207
> Content-Type: text/
Hi,
Today I ran into an issue where setting the default slice with boot0cfg
-s is broken.
This is related to a section of this revision:
+ commit Warner's patch "orb $NOUPDATE,_FLAGS(%bp)"
to avoid writing to disk in case of a timeout/default choice;
This issue is quite well documented in bin
12 matches
Mail list logo
