Dennis wrote:
>
> At 10:48 PM 6/7/00 -0700, W Gerald Hicks wrote:
> >Peter Wemm wrote:
> >
> >> I suspect a generic chipset fault, or some design quirk that we are not
> >> working around. Note that the windoze drivers for these devices put them
> &
[EMAIL PROTECTED] wrote:
>
> > > I suspect a generic chipset fault, or some design quirk that we are not
> > > working around. Note that the windoze drivers for these devices put them
> > > permanently in store-and-forward mode. if_de has the exact same problem on
> > > all of the systems above
Peter Wemm wrote:
> I suspect a generic chipset fault, or some design quirk that we are not
> working around. Note that the windoze drivers for these devices put them
> permanently in store-and-forward mode. if_de has the exact same problem on
> all of the systems above.
>
I'll second this.
Arun Sharma wrote:
> I don't know if the gas support is public, but you can certainly get the
> Intel assembler for IA-64, which has been open sourced under the BSD
> license from developer.intel.com. It may not be of much practical use,
> but might help in understanding the architecture (which r
"Koster, K.J." wrote:
>
> Dear all,
>
> Is there someone on this list who's into the finer points of copyrighting? I
> would like to know what the implications are of this for the
> soon-to-be-coming native FreeBSD JDK port.
>
> In what form is Motif going to be available to the general FreeBSD
Once again I must ask... What do you know of Open Source?
Aside from your enlightened criticisms I've seen nothing in
the way of any sort of contribution. No ports maintenance,
no code contribution. Nothing other than pure profiteering
and never returning anything but a kick in the nuts.
Thank
Hi Felipe,
(You should probably be targeting -current for software under development)
Perhaps consulting /usr/src/usr.bin/top/machine.c might offer up
some clues.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the b
From: Kevin M Geraci <[EMAIL PROTECTED]>
> Maybe FreeBSD needs to "spin off" like Slackware is
> doing and let Walnut Creek merge.
I don't see why that thought even crossed your mind.
Anyone could "spinoff" FreeBSD anytime they wanted to.
So far, there has been no compelling reason to do so
and
I'm sorry Dennis but I find it a bit difficult to swallow
your assessment of other people's business acumen and
their ability to relate to markets.
The race isn't over yet, hell everybody's just warming up :-)
--
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
> I agree that this is not the time to change it. But in the long run,
> if the ports framework is misusing /bin/sh then the framework needs to
> be fixed. We shouldn't let bugs there influence what we do with the
> shell.
Haven't been convinced yet they are bugs :-)
Cheers,
Jerry Hicks
[EMA
> is not a word at all, so it can't be expanded, so I think
> bash is corrent to complain about a syntax error.
Epsilon anyone?
I really don't care (honestly) but a null word can be considered a word too!
In yacc-like terms:
wordlist:
| wordlist WORD
;
It doesn't really matte
From: Doug Barton <[EMAIL PROTECTED]>
> John Polstra already pointed this out, and Bash handles this like you
> would expect. There is a difference between expanding an empty list and
> trying to expand a list that isn't there.
Convince me that nothing like the following exists in the
por
From: Doug Barton <[EMAIL PROTECTED]>
Subject: Re: empty lists in for
Date: Sun, 05 Mar 2000 11:39:49 -0800
> W Gerald Hicks wrote:
> >
> > > > bash and ksh complain about unexpected ';'.
> > > > /bin/sh (FreeBSD) thinks it's ok and does no
> > bash and ksh complain about unexpected ';'.
> > /bin/sh (FreeBSD) thinks it's ok and does nothing.
> > Which behaviour is more POSIXly correct?
>
> Neither bash nor ksh claim to be particularly POSIX compliant. our
> /bin/sh does. I seem to remember POSIX being ambiguous on this one, but
From: "Jason Allum" <[EMAIL PROTECTED]>
Subject: powerpc cross compiler?
Date: Fri, 25 Feb 2000 09:58:01 -0500
> i'm trying to setup gcc 2.95.2 as a powerpc (7400/G4) cross compiler on
> freebsd 3.4-release... i'm having no luck, as it keeps bombing out when it
> tries to build libgcc.a... anyone
>
> > What sort of quality-control measures does Slackware have? Where
> > do I access their cvs tree? Where do I access their problem reports?
> > Where do I subscribe to get every commit message? How long are
> > their code freezes? How many committers do they have? What
> > mechanism crea
Hi Folks,
(included Daniel since he had other concerns we discussed elsewhere)
I haven't submitted a PR yet, pending the outcome of the discussion;
since the right group of people seems to be talking about it, I'll
just get out of the way :-)
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubs
> Out of curiosity, were the benchmarks done with any of the Haifa
> command-line-options, notably -fsched-interblock, -fsched-spec,
> -fsched-spec-load, and -fbranch-count-reg ?
> (toplev.c, grep for '#ifdef HAIFA', and read the comments
> scattered elsewhere (haifa-sched.c))
Not yet, but thank
> Er, global is part of the base system. :-)
Hehe, I knew that.
My point was that the entire package isn't built and the author's
going GPL anyway and since nobody recommended it ... That sure would
make a nice port ;-)
For the original poster gtags/htags is an excellent tool for your
purposes
I find it ironic that nobody has suggested global yet;
That sure would make a nice port, especially since we could
easily recommend gozilla as a nice way to browse and search
the source tree.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscrib
Just curious what effect using the --enable-haifa flag for building
gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone
benchmark from /usr/ports/benchmarks/bytebench.
This was run on a Ziatech 200Mhz Pentium cPCI system. I don't know
if this is really worth further testing but
> > Could things be done in such a way that like QNX, it can
> > kill and restart a misbehaving driver? What other cool things can be
> > done?
>
> QNX doesn't do that.
> Actually, in many cases it does. There are numerous advantages in a
> well-designed/optimized micro-kernel that FreeBSD wi
> On Slashdot, ...
>
> Under QNX, if your driver crashes, the kernel just restarts it.
That's not in the least bit how QNX works... oh well, it's slashdot.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
> doing state machines with switch statements is a big mess.
Still, you'll find a lot of them around. Do you have a favored
technique for coding complex state machines? (I'm a collector :)
One scheme I've been using for quite some time is to use a function
pointer as a 'state variable', somet
Tradition counts. GLOBAL isn't quite sendmail.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
> I think that Jerry, in using GLOBAL as an example to push his desire for a
> smaller FreeBSD, rather clouded the issue. I would wish that, if Shigio
> doesn't actually assign the copyright to the FSF, then he can release it
> under both copyrights, and please everyone. If Jerry wants to have
> > imho, global (a fine software package) shouldn't have been in the
> > OS source tree anyway. To me, the proper place seems to be in the
> > ports collection along with many other development utilities.
> It seems that you misunderstand.
> Current GLOBAL(3.53 and earlier) is BSD-style licens
I don't see much of a problem, other than requiring its removal
from the FreeBSD source tree. Although FreeBSD has a 'contrib'
and 'gnu' hierarchy in the source tree, I believe the trend
should be to reduce the existing members there and also to avoid
adding new ones.
imho, global (a fine softwar
I don't see much of a problem, other than requiring its removal
from the FreeBSD source tree. Although FreeBSD has a 'contrib'
and 'gnu' hierarchy in the source tree, I believe the trend
should be to reduce the existing members there and also to avoid
adding new ones.
imho, global (a fine softwa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
> Sorry if this is off topic for this list, but I'm about to dive head first
> into more advanced FreeBSD and I'm badly in need of a good reference book.
[snip]
I've not missed having a shelf of books about FreeBSD, mainly because of
the reference materials served by the FreeBSD CVSup servers.
If
> It would be better to create src/gnu/lib/libgnugetopt/Makefile and point
> ".PATH:" to the newest src file we have in the tree. If some package
> gets updated and there is a newer GNUgetopt(), then we change the
> ".PATH:". JDP suggested this is a cleaner way than extracting part of a
> GNU pac
> I'd really rather have the cross-compilers.
Me too, but for other reasons.
If you are using CVS then the problems you mention of working
between systems will be greatly minimized. Besides, we'd
really like to see you try FreeBSD :-)
My major problem with the approach you are considering rea
34 matches
Mail list logo
