on 10/09/2011 14:03 Peter Jeremy said the following:
> On 2011-Sep-10 12:46:50 +0300, Andriy Gapon wrote:
>> on 10/09/2011 11:07 Andriy Gapon said the following:
>>> Actually, removing either -mrtd _or_ -fno-unit-at-a-time produces the
>>> correct code. Puzzled.
>>
>> The problem is reproducible
On Sat, 10 Sep 2011 21:10:44 +0400
Boris Samorodov wrote:
> On Sat, 10 Sep 2011 16:08:21 +0200 Gary Jennejohn wrote:
> > > On Tue, 06 Sep 2011 16:29:51 +0400 Boris Samorodov wrote:
> > >
> > > > the port does not work as expected (at least as per The Handbook,
> > > > 26.2.5 Serial Port Configur
on 11/09/2011 11:31 Andriy Gapon said the following:
> And I am actually wondering about -fno-unit-at-a-time option.
> In my opinion this is an anti-optimization option and it can actually increase
> a size of a final binary. In fact, it looks like the option was introduced to
> boot2 in r132870 i
Hi all,
I've discovered a small bug in dump. When dump reads
the /etc/dumpdates, at the moment the device name in the first column is
restricted to 32 characters.
With todays GEOM implementation, it's easy to make longer device names.
My device is named: "/dev/mirror/encrypted.elig.journal". An
On Tue, Sep 06, 2011 at 04:29:51PM +0400, Boris Samorodov wrote:
> the port does not work as expected (at least as per The Handbook,
> 26.2.5 Serial Port Configuration). Nether "init" nor "lock"
> devices can be used:
> -
> # uname -a
> FreeBSD host1.ipt.ru 9.0-BETA2 FreeBSD 9.0-BETA2 #14 r2253
Adrian Chadd wrote on 11.09.2011 04:56:
Please submit a PR so I/others don't forget.
Then just follow through with an email to me w/ the PR number.
Thanks,
Adrian
Done. http://bugs.freebsd.org/160652
--
Regards,
Ruslan
Tinderboxing kills... the drives.
_
On 2011-Sep-11 11:31:54 +0300, Andriy Gapon wrote:
>And I am actually wondering about -fno-unit-at-a-time option.
>In my opinion this is an anti-optimization option and it can actually increase
>a size of a final binary. In fact, it looks like the option was introduced to
>boot2 in r132870 in the
On 09/11/11 13:31, Peter Jeremy wrote:
On 2011-Sep-11 11:31:54 +0300, Andriy Gapon wrote:
And I am actually wondering about -fno-unit-at-a-time option.
In my opinion this is an anti-optimization option and it can actually increase
a size of a final binary. In fact, it looks like the option was
Hi.
On 04.09.2011 10:32, Andriy Gapon wrote:
> ahcich0: Timeout on slot 0 port 0
> ahcich0: is 0005 cs ss rs 0001 tfd 50 serr
> cmd 1000c017
> ahcich0: AHCI reset...
> ahcich0: SATA connect time=0us status=0113
> ahcich0: AHCI reset: device found
> ahcich0: A
On Sun, Sep 11, 2011 at 6:31 AM, Peter Jeremy wrote:
> In any case, size isn't an issue for any of gptboot, gptzfsboot or
> zfsboot (unlike boot2). For that matter, why do we need both
> gptboot and gptzfsboot? It would be more convenient to have a
> single GPT bootstrap that handled both UFS &
> > the result is:
> > db> show intrcnt
> > cpu0: timer4510
> > irq256: hdac0 1
> > cpu3: timer 29
> > cpu1: timer 3036
> > cpu2: timer 31
> > db>
> >
> > I did break at the mountfrom> prompt
> > If I break before I only have the cpu0 and irq256 entries.
>
> Hmmm, is there any w
I'm trying to use the iconv that's in FreeBSD-CURRENT and it's not reporting
errors the way I expect. To demonstrate, here's a test program that tries to
convert UTF-8 to KOI8-R. This should report an error, since the UTF-8 string
here "ĐÒÉ×ÅÔ" contains characters not available in KOI8-R.
On
Actually, I think this kind of question is for the freebsd-current list, so I
respond on that list.
Problem with the old sysinstall is that sysinstall expects installation sets to
be broken into 1392 KB chunks as opposed to a full .tgz, .tbz or .txz, or so I
believe: I could be wrong.
I though
On Sun, 11 Sep 2011 10:33:18 +0200 Gary Jennejohn wrote:
> On Sat, 10 Sep 2011 21:10:44 +0400
> Boris Samorodov wrote:
> > On Sat, 10 Sep 2011 16:08:21 +0200 Gary Jennejohn wrote:
> > > > On Tue, 06 Sep 2011 16:29:51 +0400 Boris Samorodov wrote:
> > > >
> > > > > the port does not work as expecte
On Sep 11, 2011 6:54 PM, "Boris Samorodov" wrote:
>
> On Sun, 11 Sep 2011 10:33:18 +0200 Gary Jennejohn wrote:
> > On Sat, 10 Sep 2011 21:10:44 +0400
> > Boris Samorodov wrote:
> > > On Sat, 10 Sep 2011 16:08:21 +0200 Gary Jennejohn wrote:
> > > > > On Tue, 06 Sep 2011 16:29:51 +0400 Boris Samoro
On Sun, 11 Sep 2011 13:02:58 +0200 Jilles Tjoelker wrote:
> On Tue, Sep 06, 2011 at 04:29:51PM +0400, Boris Samorodov wrote:
> > the port does not work as expected (at least as per The Handbook,
> > 26.2.5 Serial Port Configuration). Nether "init" nor "lock"
> > devices can be used:
> > -
> >
On Sun, 11 Sep 2011 19:31:33 -1000 David Cornejo wrote:
> It's been a long time,
It worked at 8.2-PRERELEASE for me (and seemed to be a bug
at 9.0-BETA2):
-
% uname -a
FreeBSD hht.ipt.ru 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0 r216685: Fri Dec 24
10:16:47 MSK 2010 b...@hht.ipt.ru:/z/ob
17 matches
Mail list logo
