On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote:
> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the
> issue of cdda:// access.
>
> I can confirm this issues, but don't know enough about driver access to fix
> this myself. Doug Barton reports that cdcontrol(1) do
I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the issue
of cdda:// access.
I can confirm this issues, but don't know enough about driver access to fix this
myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and mplayer
and audactiy also display issues
Rather than changing BKVASIZE, I would try running the cvs2svn
conversion on a 16K/2K filesystem and see if that sorts out the
problem. If it does, it tells us that doubling the main block
size and reducing the number of buffers by half is the problem.
If that is the problem, then we will have to i
On Thu, 29 Dec 2011, Randy Bush wrote:
bsdgrep works, grep does not
% echo foo | bsdgrep foo
foo
% echo foo | grep foo
%
Make sure you do not have an alias or function for grep. I have once or
twice in the past inadvertently created aliases or functions for grep
that did nothing.
That wa
bsdgrep works, grep does not
% echo foo | bsdgrep foo
foo
% echo foo | grep foo
%
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebs
>> % echo foo | grep foo
>> %
>
> I'm using pretty recent -current, and it works for me. Are you by any
> chance using bsdgrep? (it's not the default)
not to my knowledge
> If you haven't enabled the option for bsdgrep in src.conf then do the
> same thing in /usr/src/gnu/usr.bin/grep.
>
> make
On 12/28/2011 14:35, Randy Bush wrote:
> FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51
> UTC 2011 r...@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64
>
> % echo foo | grep foo
> %
>
> so i am csupping hoping to pick up the fix.
I'm using pretty recent -current,
On Wed, 2011-12-28 at 12:49 -0800, Michael Butler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I noticed updates come from SVN today but haven't yet seen them in CVS.
> Is it busted again?
>
Clusteradm@ can take a look at this ... I think.
Sean
signature.asc
Description: This
FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51
UTC 2011 r...@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64
% echo foo | grep foo
%
so i am csupping hoping to pick up the fix. but what do i need to do so
that the sucker can build a new kernel and world?
randy
__
Hello, Mdf.
You wrote 28 декабря 2011 г., 23:14:19:
> Not required by SU as they use an explicit BIO_FLUSH which should be
> handled by the driver.
No, they don't. It was discussed here about month ago.
--
// Black Lion AKA Lev Serebryakov
___
fre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed updates come from SVN today but haven't yet seen them in CVS.
Is it busted again?
imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk77gOs
On Wed, Dec 28, 2011 at 5:25 AM, Vincent Hoffman wrote:
> On 28/12/2011 06:30, Doug Barton wrote:
> > On 12/27/2011 22:08, Adrian Chadd wrote:
> >> Hi,
> >>
> >> Why not just list the things that sysinstall did that people like, and
> >> extract out / reimplement those bits?
> > That's sounds gre
On Wed, Dec 28, 2011 at 11:14:19AM -0800, m...@freebsd.org wrote:
> SU doesn't care about write ordering, as long as everything before a
> BIO_FLUSH is really flushed by the time the BIO_FLUSH is acknowledged.
No.
SU and SU+J only require that write completed notification is issued
when geom/drive
On Wed, Dec 28, 2011 at 8:54 AM, Maxim Khitrov wrote:
> On Wed, Dec 28, 2011 at 11:42 AM, Matthias Andree
> wrote:
>> Am 27.12.2011 22:53, schrieb David Thiel:
>>> I've had multiple machines now (9.0-RC3, amd64, i386 and earlier
>>> 9-CURRENT on ppc) running SU+J that have had unexplained panics
On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote:
> Am 12/28/11 19:10, schrieb Ed Schouten:
> > * Rainer Hurling , 20111228 17:31:
> >> error: macro "_Static_assert" passed 3 arguments, but takes just 2
> >> In file included from
> >> /usr/
Am 12/28/11 19:10, schrieb Ed Schouten:
> * Rainer Hurling , 20111228 17:31:
>> error: macro "_Static_assert" passed 3 arguments, but takes just 2
>> In file included from
>> /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:10
* Rainer Hurling , 20111228 17:31:
> error: macro "_Static_assert" passed 3 arguments, but takes just 2
> In file included from
> /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:103:0:
Hmmm... This seems to apply to my changes. I will look
On 28.12.11 17:31, Rainer Hurling wrote:
On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote:
On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote:
Am 12/28/11 14:58, schrieb Kostik Belousov:
On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
Hello out here.
I run into a prob
Am 12/28/11 17:31, schrieb Rainer Hurling:
> On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote:
>> On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote:
>>> Am 12/28/11 14:58, schrieb Kostik Belousov:
On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
> Hello out here.
>>
On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote:
On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote:
Am 12/28/11 14:58, schrieb Kostik Belousov:
On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
Hello out here.
I run into a problem since one of the last portupdates and
On Wed, Dec 28, 2011 at 11:42 AM, Matthias Andree
wrote:
> Am 27.12.2011 22:53, schrieb David Thiel:
>> I've had multiple machines now (9.0-RC3, amd64, i386 and earlier
>> 9-CURRENT on ppc) running SU+J that have had unexplained panics and
>> crashes start happening relating to disk I/O. When I en
On Wed, Dec 28, 2011 at 2:39 PM, Dimitry Andric wrote:
> On 2011-12-28 17:32, Renato Botelho wrote:
>>
>> On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric wrote:
>
> ...
>
>>> Most likely, it is due to the way you set CC, CXX and/or CPP in
>>> make.conf. Can you please post that file?
>>
>>
>> Su
Am 27.12.2011 22:53, schrieb David Thiel:
> I've had multiple machines now (9.0-RC3, amd64, i386 and earlier
> 9-CURRENT on ppc) running SU+J that have had unexplained panics and
> crashes start happening relating to disk I/O. When I end up running a
> full fsck, it keeps turning out that the di
On 2011-12-28 17:32, Renato Botelho wrote:
On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric wrote:
...
Most likely, it is due to the way you set CC, CXX and/or CPP in
make.conf. Can you please post that file?
Sure, follow my src.conf:
.if !defined(CC) || ${CC} == "cc"
CC=clang
.endif
.if !d
On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric wrote:
> On 2011-12-28 16:44, Renato Botelho wrote:
>>
>> On Tue, May 3, 2011 at 10:07 PM, Manfred Antar wrote:
>>>
>>> I get this error when trying to buildworld on current i386.
>>> It's been this way for awhile Any Ideas ?
>>>
>>> ===> boot/i386
On 2011-12-28 16:44, Renato Botelho wrote:
On Tue, May 3, 2011 at 10:07 PM, Manfred Antar wrote:
I get this error when trying to buildworld on current i386.
It's been this way for awhile Any Ideas ?
===> boot/i386/boot0 (all)
clang -O2 -pipe -DVOLUME_SERIAL -DPXE -DFLAGS=0x8f -DTICKS=0xb6
On Tue, May 3, 2011 at 10:07 PM, Manfred Antar wrote:
> I get this error when trying to buildworld on current i386.
> It's been this way for awhile Any Ideas ?
>
> ===> boot/i386/boot0 (all)
> clang -O2 -pipe -DVOLUME_SERIAL -DPXE -DFLAGS=0x8f -DTICKS=0xb6
> -DCOMSPEED="7 << 5 + 3" -ffreestand
Am 12/28/11 16:57, schrieb Dimitry Andric:
> On 2011-12-28 11:48, O. Hartmann wrote:
> ...
>> /usr/local/bin/ld:
>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o):
>>
>> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()'
>> can not be
On 2011-12-28 11:48, O. Hartmann wrote:
...
/usr/local/bin/ld:
/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o):
relocation R_X86_64_32 against `std::bad_exception::~bad_exception()'
can not be used when making a shared object; recompile with -fPIC
/usr
Am 12/28/11 15:24, schrieb Alexander Leidinger:
>
> Hi,
>
> you assume in your comment that development time "wasted" in the
> linuxulator is time lost for other development. This assumption could be
> valid for a commercially developed OS, but is wrong for FreeBSD. I tell
> this as a person who
On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote:
> Am 12/28/11 14:58, schrieb Kostik Belousov:
> > On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
> >> Hello out here.
> >>
> >> I run into a problem since one of the last portupdates and I do not know
> >> whether this has t
Hi,
you assume in your comment that development time "wasted" in the linuxulator is
time lost for other development. This assumption could be valid for a
commercially developed OS, but is wrong for FreeBSD. I tell this as a person
who spend a lot of time with the linux ports, mentored a GSoC s
Am 12/28/11 14:58, schrieb Kostik Belousov:
> On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
>> Hello out here.
>>
>> I run into a problem since one of the last portupdates and I do not know
>> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0
>> AMD64.
>>
>> Back
On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote:
> Hello out here.
>
> I run into a problem since one of the last portupdates and I do not know
> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0
> AMD64.
>
> Background:
> We use a scientific graphical toolset for
On 28/12/2011 06:30, Doug Barton wrote:
> On 12/27/2011 22:08, Adrian Chadd wrote:
>> Hi,
>>
>> Why not just list the things that sysinstall did that people like, and
>> extract out / reimplement those bits?
> That's sounds great. As soon as that's done, we can remove sysinstall
> from the base. Un
Hello out here.
I run into a problem since one of the last portupdates and I do not know
whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0
AMD64.
Background:
We use a scientific graphical toolset for planetary research called
ISIS3, which is provided by the USGS. We patched I
On Mon, 26 Dec 2011 22:42:36 -0500 (EST)
Rick Macklem wrote:
> First off, I had no idea which mailing list would be appropriate
> for this, so apologies in advance if I chose the wrong one.
>
> For NFSv4.1 pNFS, there are layout drivers in Linux that I would
> like to reuse for the FreeBSD clien
37 matches
Mail list logo
