Chad David wrote:
> On Tue, Oct 29, 2002 at 07:04:21PM -0800, Terry Lambert wrote:
> > Chad David wrote:
> > > Does anybody know if there is a good reason why libobjc is built with
> > > thr-single.c?
> >
> > Historical threads problems.
>
> A few are obvious from simply reading the code. Do you
At Tue, 29 Oct 2002 16:03:49 + (UTC),
Poul-Henning Kamp wrote:
> http://phk.freebsd.dk/misc/_.release
>
> I think it is related to all the crypto magic in make release...
I got same result as Poul-Henning. It seems installed libssh.a in
chroot does not have mm_auth_krb5().
I don't kno
David O'Brien wrote:
> On Tue, Oct 29, 2002 at 07:09:41PM -0700, Chad David wrote:
> > Does anybody know if there is a good reason why libobjc is built with
> > thr-single.c? As well, who is the current maintainer of Objective-C?
>
> Few of us have ObjC clue. Do you have a patch that makes thing
On (2002/10/29 13:06), Matthew Dillon wrote:
> :Most of the speed difference is WITNESS, INVARIANTS, and other
> :debugging code that's turned on by default in the config files
> :for -current. You can turn most of it off. That said, -current
> :is slower than -stable in a number of places, so e
On Wed, 30 Oct 2002, Dag-Erling Smorgrav wrote:
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > I'd rather fix it like this:
>
> Oomph, of course this doesn't work in the !ssl case. I would really
> prefer a solution that allowed wlen == 0 if we actually *intended* not
> to write anything,
I was working on (wlen == 0 && iov->iov_cnt != 0) for a while, thinking
that it would work in both cases, even though the logic is a little weird
in the writev case, but it would fail in the race where the connection
closed at the same time as the writev() with the zero length iov_len.
Bill
To
On Tue, Oct 29, 2002 at 10:01:07PM -0800, Paul A. Scott wrote:
> XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and
> 4.7. It is not possible to run the graphical configuration utility at all.
> After running curses configuration utility, running startx produces signal
> 11. N
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and
4.7. It is not possible to run the graphical configuration utility at all.
After running curses configuration utility, running startx produces signal
11. No other debugging information is available. No other messages from the
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> I'd rather fix it like this:
Oomph, of course this doesn't work in the !ssl case. I would really
prefer a solution that allowed wlen == 0 if we actually *intended* not
to write anything, but I can't figure out a clean, quick way to do it
right now
While moving a large (1GB) file from one parition to another today, I
noticed an odd, reproducable pause. Basicly you create a large file
somewhere and then delete it like so:
[9:32pm] brooks@minya (/var/tmp): dd if=/dev/zero of=bigfile bs=1m count=1000
1000+0 records in
1000+0 records out
104857
Bill Fenner <[EMAIL PROTECTED]> writes:
> Turns out my writev patch for fetch broke SSL, since it could create
> iov[0].iov_len = 0, which would cause SSL_write(..,0), which would
> return 0, which would look like a short write and cause an error, which
> then gets ignored by http.c . Ignoring the
* De: Chad David <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
[ Subjecte: Re: Objective-C threads ]
> >
> > > As well, who is the current maintainer of Objective-C?
> >
> > Chad David?
>
> By default, since there seem to be no other users?
I'm willing to help out with testing Objective-C st
I'm installing on a pc98 machine (The NEC PC-9821 Nr Lavie).
About 40% into the base install, I got the following panic:
kernel: trap 12 trap, code=0
Stopped at ufs_ihashget+0x70: cmpl 0x30(%eax),%ebx
db> tr
ufs_ihashget(c1ee6000,2128,2,c8957854,c4ddc0ae) at ufs_ihashget_0x70
ffs_vget(...) at ff
I wrote:
> If memory serves me right, John wrote:
>
> >How many other people are testing the 5.0 sysinstall booted
> > from a cd and running a local (cd/dvd) install? Try booting and
> > installing from the iso at usw2.freebsd.org and see if it works
> > for you.
>
> I'm able to boot and ins
On Tue, Oct 29, 2002 at 07:04:21PM -0800, Terry Lambert wrote:
> Chad David wrote:
> > Does anybody know if there is a good reason why libobjc is built with
> > thr-single.c?
>
> Historical threads problems.
A few are obvious from simply reading the code. Do you have any
knowledge of specific (n
On Tue, Oct 29, 2002 at 07:11:56PM -0800, David O'Brien wrote:
> On Tue, Oct 29, 2002 at 07:09:41PM -0700, Chad David wrote:
> > Does anybody know if there is a good reason why libobjc is built with
> > thr-single.c? As well, who is the current maintainer of Objective-C?
>
> Few of us have ObjC c
Not sure if a fix was ever implemented for this problem directly, but I
thought I'd note that the problem I experienced mounting my NTFS partition
has gone away. I hadn't tried it for a while, so I don't know the exact
date/commit that did the deed.
Thanks!
--
Jason Young, CCIE #8607, MCSE
Sr.
On Tue, Oct 29, 2002 at 07:12:25PM -0800, Bill Fenner wrote:
> then gets ignored by http.c . Ignoring the bigger picture of the error
> checking, this fix at least gets https: working again by making sure
> that _fetch_putln doesn't construct an iov with iov_len == 0. (Yes,
> this is against rev
On Tue, Oct 29, 2002 at 07:09:41PM -0700, Chad David wrote:
> Does anybody know if there is a good reason why libobjc is built with
> thr-single.c? As well, who is the current maintainer of Objective-C?
Few of us have ObjC clue. Do you have a patch that makes things better
that you can explain t
Turns out my writev patch for fetch broke SSL, since it could create
iov[0].iov_len = 0, which would cause SSL_write(..,0), which would
return 0, which would look like a short write and cause an error, which
then gets ignored by http.c . Ignoring the bigger picture of the error
checking, this fix
Chad David wrote:
> Does anybody know if there is a good reason why libobjc is built with
> thr-single.c?
Historical threads problems.
> As well, who is the current maintainer of Objective-C?
Chad David?
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
I have to agree with Daniel here, John. I've worked on 'A'uto quite
a bit and it is simply not possible to create 'A'uto values that
everyone is satisfied with. It also doesn't make much sense to
arbitrarily scale what are normally small partitions just because
you have a larg
>In this day of larger disk drives, I've modified
> the code in sysinstall to automatically create a /home
> partition and increase the rest of the sizes if the
> size of the disk (or slice) exceeds a given size (currently
> 58gig in my patch). For example, using A(uto in the label
> editor on
On Tue, 29 Oct 2002, Poul-Henning Kamp wrote:
> I don't think we need to go overboard, but we are in the run{up,down}
> to a release now, so some extra testing would be nice.
I think this point may not have gotten the attention it deserves. Being so
close to a major release, why are we changing m
Does anybody know if there is a good reason why libobjc is built with
thr-single.c? As well, who is the current maintainer of Objective-C?
--
Chad David[EMAIL PROTECTED]
www.FreeBSD.org [EMAIL PROTECTED]
ISSci Inc.Calgary, Alberta Canada
To Unsubscribe: send mail to [EMAIL PRO
Hi again,
If anyone is interested, I have the following binaries of apache
available 1.3.27, 2.0.43 for platforms:
1) freebsd: 5.0-current, 4.7-release
2) solaris: sparc-sun-solaris2.7
http://p6m7g8.net/apache
Philip M. Gollucci wrote:
Hi all,
Just want to say thanks for all the great work.
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
In message: <[EMAIL PROTECTED]>
Garrett Wollman <[EMAIL PROTECTED]> writes:
: Has anyone managed to make one of these work? I get the following
: messages:
:
: cardbus1: Expecting link target, got 0x59
: cardbus1: Resource not specified in CIS: id=10, size=100
: cardbus1: Resource not
Has anyone managed to make one of these work? I get the following
messages:
cardbus1: Expecting link target, got 0x59
cardbus1: Resource not specified in CIS: id=10, size=100
cardbus1: Resource not specified in CIS: id=14, size=400
cardbus1: (vendor=0x1737, dev=0xab09) at 0.0 irq 11
cbb1: CardBu
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Matthew Dillon wrote:
> Interrupt threads have 'grown' on me. I like them.
> But I come from an embedded world where switching threads
> costs no more then a procedure call. The way I figure it,
> we will eventually be able to make -current's scheduler
> efficient enough such
:I agree that "it's to be expected", but the "it doesn't matter"
:argument is pretty lame. It matters. Coming to FreeBSD the
:first time, I would definitely make a decision for 4.7 vs. 5.x
:if performance were an issue for me. I still have not seen a
:reasonable justification for interrupt thre
Matthew Dillon wrote:
> That said, it should be noted that nearly all the
> really cool development projects are only happening in -current.
Not by choice... 8-) 8-).
> And, of course, there is the fact that computing power seems to
> double every year. Since -current's overhead
On Tue, 29 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > The point is that with the current setup of the XFree86-4-libraries port,
> > you don't have any choice, since libX11 links to libXThrStub. This is the
> > key problem, IMHO. I have a machine running RedHat 8.0 and they don't have
:Most of the speed difference is WITNESS, INVARIANTS, and other
:debugging code that's turned on by default in the config files
:for -current. You can turn most of it off. That said, -current
:is slower than -stable in a number of places, so expect some
:slowdown, if you are running non-concurre
Doug Rabson wrote:
> The point is that with the current setup of the XFree86-4-libraries port,
> you don't have any choice, since libX11 links to libXThrStub. This is the
> key problem, IMHO. I have a machine running RedHat 8.0 and they don't have
> any such thing. On RedHat, libXThrStub doesn't ev
Raymond Kohler wrote:
> I'm now a stable user, and I'm considering moving to current to get a jump
> on upgrading and help with the testing effort. I have some questions about
> its performance:
>
> 1) How is the speed compared to stable? I remember it being just too slow
> some months ago and was
On 2002-10-29 11:40 +, Raymond Kohler wrote:
> I'm now a stable user, and I'm considering moving to current to get a jump on
>upgrading and help with the testing effort. I have some questions about its
>performance:
>
> 1) How is the speed compared to stable? I remember it being just too slo
On Tue, 29 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > On investigating one of the crashes more carefully, I discovered that all
> > calls to pthread_*() were being resolved to stubs in libXThrStub.so in
> > spite of the fact that libc_r was also loaded. This caused problems for
> > e.
Raymond Kohler ([EMAIL PROTECTED]) wrote:
> 3) Are there any Very Important Packages (mozilla, kde, &c) that
> won't build or refuse to work right?
I've been compiling mozilla/phoenix for months now, out of CVS,
and it was only broken twice, and for no more than a couple of days.
--
Eric Hodel
Doug Rabson wrote:
> > When a symbol is defined in multiple libraries, the first library
> > wins. That's how it has always been in Unix, for archive libraries
> > and for shared libraries.
>
> This is a big problem then since X11.so links to XThrStub.so. This means
> that XThrStub will be ahead
Juli Mallett wrote:
> * De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
> > Having a set of regression tests for make under src/tools/regression
> > would be really cool as well.
>
> I agree with you 100%. It'd be nice if people with esoteric-but-valid
> build systems using our mak
Doug Rabson wrote:
> On investigating one of the crashes more carefully, I discovered that all
> calls to pthread_*() were being resolved to stubs in libXThrStub.so in
> spite of the fact that libc_r was also loaded. This caused problems for
> e.g. flockfile which failed to initialise its mutex (ut
Juli Mallett wrote:
> > Please test make(1) changes on "make release" in the future.
>
> The standard metric has been 'make buildworld' I thought? Anyway, try
> with revision 1.2 of var_modify.c, that should do it.
>
> Realistically, to prevent any sort of breakage to make(1), we should
> test m
At 11:40 AM -0700 10/29/02, Raymond Kohler wrote:
I'm now a stable user, and I'm considering moving to current to
get a jump on upgrading and help with the testing effort.
Note that -current is a much wilder place than -stable.
I have some questions about its performance:
1) How is the speed
Daniel Eischen writes:
> > It might have been slightly clearer if the _foo and __foo names had been
> > reversed, so that "foo" always weakly referenced "_foo" whether or not
> > the function was a cancellation point. But that would have probably
> > caused a lot of changes in existing code (?).
>
On 29-Oct-2002 clark shishido wrote:
> On Tue, Oct 29, 2002 at 11:40:53AM -0700, Raymond Kohler wrote:
>> 1) How is the speed compared to stable? I remember it being just too slow some
>months ago and
>> was wondering how it was improving.
>>
>> 2) Are the random hangs in X fixed yet? I can put
On Tue, Oct 29, 2002 at 11:40:53AM -0700, Raymond Kohler wrote:
> 1) How is the speed compared to stable? I remember it being just too slow some
>months ago and was wondering how it was improving.
>
> 2) Are the random hangs in X fixed yet? I can put up with a few issues (it is
>current, after a
Hi all,
Just want to say thanks for all the great work.
Figure its time for me to start contributing more actively to our
communities.
I have the following setup, and would be happy to test some things for
people not having access to an envirnment like this.
Architecture
350MHz Intel PII w/ 64M
I'm now a stable user, and I'm considering moving to current to get a jump on
upgrading and help with the testing effort. I have some questions about its
performance:
1) How is the speed compared to stable? I remember it being just too slow some months
ago and was wondering how it was improving
On Tue, 29 Oct 2002, Archie Cobbs wrote:
> John Polstra writes:
> > > > I think it would work if the symbol were defined strongly in libc_r.
> > >
> > > I think so too. I was trying to work out why this wasn't how things were
> > > done already. FWIW, linux's libpthread appears to be defining the
John Polstra writes:
> > > I think it would work if the symbol were defined strongly in libc_r.
> >
> > I think so too. I was trying to work out why this wasn't how things were
> > done already. FWIW, linux's libpthread appears to be defining the
> > pthread_* symbols strongly.
>
> I think the we
Hmm. I haven't experienced this with my 5.0 boxes not running
WITNESS/INVARIANTS/etc, but I'm updating a box to give it a try.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Tue, 29 Oct 2002, John De Boskey wrote:
On Tue, 29 Oct 2002, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Doug Rabson <[EMAIL PROTECTED]> wrote:
> > On Tue, 29 Oct 2002, John Polstra wrote:
> > > I think it would work if the symbol were defined strongly in libc_r.
> >
> > I think so too. I was trying to work out why this was
On 29-Oct-2002 Joe Marcus Clarke wrote:
> On Mon, 2002-10-28 at 16:37, John Baldwin wrote:
>>
>> On 28-Oct-2002 Joe Marcus Clarke wrote:
>> > On Mon, 2002-10-28 at 16:27, John Baldwin wrote:
>> >>
>> >> On 28-Oct-2002 Terry Lambert wrote:
>> >> > John Baldwin wrote:
>> >> >> I mean, do you know
If memory serves me right, Doug Barton wrote:
> This should go on the "Comprehensive guide to updating from source to 5.0"
> that I'm sure our trusty release engineers are producing?
Some of this is described in the early adopter's guide (still a work in
progress) that I committed to the release
In article <[EMAIL PROTECTED]>,
Doug Rabson <[EMAIL PROTECTED]> wrote:
> On Tue, 29 Oct 2002, John Polstra wrote:
> > I think it would work if the symbol were defined strongly in libc_r.
>
> I think so too. I was trying to work out why this wasn't how things were
> done already. FWIW, linux's lib
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> Inside the chroot.
>
>'make release' checks out src in the sandbox, then chroots to it and
>does a plain 'make world' right? There's no chance the sources in the
>sandbox were stale, or it
Apparently, On Tue, Oct 29, 2002 at 08:55:03AM -0500,
Andrew Gallatin said words to the effect of;
>
> David O'Brien writes:
> > On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote:
> > > You can also get various new machines on sun.com for around $1000 USD,
> > > IIRC a 50
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> Inside the chroot.
'make release' checks out src in the sandbox, then chroots to it and
does a plain 'make world' right? There's no chance the sources in the
sandbox were stale, or it was trying to do something fancy? What
about the sandbox itself
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>> > You must have cvsupped at a bad time - looks like you missed the three
>> > Makefile deltas in src/secure.
>> I just started
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
> > You must have cvsupped at a bad time - looks like you missed the three
> > Makefile deltas in src/secure.
> I just started over, and cvsup did not pull any files down...
Well, mm_auth_kr
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> auth1.o: In function `do_authloop':
>> auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
>> *** Error code 1
>> 1 error
>> *** Error code 2
>
>You must have cvsupped at a bad time
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> auth1.o: In function `do_authloop':
> auth1.o(.text+0x220): undefined reference to `mm_auth_krb5'
> *** Error code 1
> 1 error
> *** Error code 2
You must have cvsupped at a bad time - looks like you missed the three
Makefile deltas in src/secure.
D
cc -O -pipe -mcpu=pentiumpro -I/usr/src/secure/usr.sbin/sshd/../../../crypto/ope
nssh -DKRB5 -DHEIMDAL -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\" -DNO_IDEA -o ssh
d sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o sshpty.o sshlogin.
o servconf.o serverloop.o uidswap.o auth.o auth1.o auth
On Tue, 29 Oct 2002, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Doug Rabson <[EMAIL PROTECTED]> wrote:
> > On Tue, 29 Oct 2002, John Polstra wrote:
> > > When a symbol is defined in multiple libraries, the first library
> > > wins. That's how it has always been in Unix, for archive
In article <[EMAIL PROTECTED]>,
Doug Rabson <[EMAIL PROTECTED]> wrote:
> On Tue, 29 Oct 2002, John Polstra wrote:
> > When a symbol is defined in multiple libraries, the first library
> > wins. That's how it has always been in Unix, for archive libraries
> > and for shared libraries.
>
> This is
On Tue, 29 Oct 2002, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Doug Rabson <[EMAIL PROTECTED]> wrote:
> > I just spent a few hours trying to get gnome working on one of my systems,
> > since kde still appears to be completely hosed. Unfortunately, not much of
> > it worked reliably.
David O'Brien writes:
> On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote:
> > You can also get various new machines on sun.com for around $1000 USD,
> > IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours.
>
> A $1000 (new) 500 MHz blade running GENERIC (minus WITNES
In article <[EMAIL PROTECTED]>,
Doug Rabson <[EMAIL PROTECTED]> wrote:
> I just spent a few hours trying to get gnome working on one of my systems,
> since kde still appears to be completely hosed. Unfortunately, not much of
> it worked reliably. In particular, all the sawfish preferences applets
* De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
[ Subjecte: Re: make(1) broken! ]
> >Realistically, to prevent any sort of breakage to make(1), we should
> >test make(1) by building every port that does not USE_GMAKE, and do
> >release, and do cross-release. Or just not mo
In message <[EMAIL PROTECTED]>, Juli Mallett writes:
>> Please test make(1) changes on "make release" in the future.
>
>The standard metric has been 'make buildworld' I thought? Anyway, try
>with revision 1.2 of var_modify.c, that should do it.
There are a lot of weird make targets which are onl
I just spent a few hours trying to get gnome working on one of my systems,
since kde still appears to be completely hosed. Unfortunately, not much of
it worked reliably. In particular, all the sawfish preferences applets
crash instantly.
On investigating one of the crashes more carefully, I discov
* De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
[ Subjecte: make(1) broken! ]
>
> I've wasted most of my morning on locating why make release was broken.
>
> The answer is that make(1) does not do variable substitutions right
> now, and in particular the line
>
> C
Hi,
I've implemented pccardc power and boot_deactivated support code for
NEWCARD. They are needed for some mobile users including me.
- Add pccardc power support code. Yes, it's OLDCARD compatible.
- Add new loader tunable hw.cbb.boot_deactivated to prevent pccards
from attaching automatic
I've wasted most of my morning on locating why make release was broken.
The answer is that make(1) does not do variable substitutions right
now, and in particular the line
CATDIR= ${MANDIR:H:S/$/\/cat/}
in bsd.man.mk produces the breaking bogosity. Notice that the "man" seems
t
On Mon, 28 Oct 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Loren James Rittle <[EMAIL PROTECTED]> writes:
> This works. I'm not sure why this isn't the default. It looks like
> we have hacks in the local tree to do this, which is why I thought
> that it worked gr
In article <[EMAIL PROTECTED]> imp writes:
> This works. I'm not sure why this isn't the default. It looks like
> we have hacks in the local tree to do this, which is why I thought
> that it worked great by default
> This is true too. See the fpsetprec() call that I had to add to make
> th
> Claiming 53 bits but supporting 64, and then not raising an exception
> and/or giving a "NaN" or "INF" result on overflow to the 54th bit is
> broken. If you do this, you will fail runtime validation suites.
Huh? The 53-bit quantity refers to the mantissa not the exponent.
Unless I'm sorely co
On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote:
> You can also get various new machines on sun.com for around $1000 USD,
> IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours.
A $1000 (new) 500 MHz blade running GENERIC (minus WITNESS) builds world
in a little under 3 ho
On Sat, Oct 26, 2002 at 08:13:18PM -0700, Julian Elischer wrote:
> I have an ATAPI dvd writer on a firewire<->atapi converter
> that connects to CAM via SBP-2.
> Using some patches for cdrecord that are available on the internet I
> got it to write fine, so tehatapi and SCSI commands for writing a
81 matches
Mail list logo
