When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker
complains about not finding the following symbols:
s_strlen
s_strcmp
vis_str
short2str
This all takes place during my attempt to do a make buildworld with the
3_4_0_RELEASE sources.
Regards
eT
P.S. please
It seems Peter Jeremy wrote:
On 2000-Jan-06 10:38:51 +1100, I wrote:
["dd if=/dev/rad0c of=/dev/null bs=64k" dies with an error]
I did some poking around and found that there are two bugs which
conspire together to cause this:
1) diskstrategy() does not detect dscheck() returning EOF,
Umm- I know I've done this before, but maybe this is something stupid I've
forgotten I went home to my shiny new 400Mhz intel with the 40GB IBM
drive in hand.. I'd pulled a couple of the 4.0 snapshot floppy sets off
off current.freebsd.org... boot the floppies- they see the de0 card I have
Hi,
i am looking at (minor) optimizations of the ipfw code in order to reduce
the running time in the common cases.
I have a few ideas (mostly along the lines of optimizing for the
most commonly-used rules). An obvious candidate is the 'match all'
rule (all from any to any), but can people
-On [2107 00:01], Poul-Henning Kamp ([EMAIL PROTECTED]) wrote:
In message [EMAIL PROTECTED], Steve Ames writes:
On the other hand, there are *plenty* of things already in 4.0 that really
need to get out there and get a workout by a larger audience.
Delaying *them* is a big
In message [EMAIL PROTECTED], Matthe
w Jacob writes:
Hmm! Better hold the 4.0 Code Freeze until this sorts out!
"No"
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before
I tried lint again since David O'Brien committed the new /usr/bin/cpp,
but it turns out that lint is hardwried to use /usr/libexec/cpp.
I changed it to use /usr/bin/cpp, and it works, but gives some
error messages.
Is this still on the list of things to fix, or should I get more details
and
On Fri, 07 Jan 2000 11:22:17 GMT, David Malone wrote:
I tried lint again since David O'Brien committed the new /usr/bin/cpp,
but it turns out that lint is hardwried to use /usr/libexec/cpp.
I changed it to use /usr/bin/cpp, and it works, but gives some
error messages.
I submitted a patch on
At 4:14 PM -0800 2000/1/6, Randy Bush wrote:
my point is that we can only wait politely and appreciatively for the kame
folk to continue their work to a point where it is more fully rounded.
until then, we should not forget that other features are also driving the
4.0 release train.
Thus spake Soren Schmidt ([EMAIL PROTECTED]):
Could wormcontrol at least stay as the wd* drivers stay?
Sure, I dont se why not, but it adds to the confusion...
ok. nice.
ata* doesn't work for me at the moment, thus I'm using the wd drivers.
What is your problem ??
I posted this to the
Pascal Hofstee [EMAIL PROTECTED] writes:
just noticed this again. And considering 4.0 is coming up soon, I really
Compiling this program with -ggdb will give normal results (a list of i =
0, upto i = 9). However when running the program through gdb Every Value
you can print is completely
On 07-Jan-00 Jordan K. Hubbard wrote:
It's a feature freeze, sorry. I still expect the loose-ends that are
in place as of that date to be tied up afterwards.
Doesn't this statement make the entire thread about IPv6 + PC-Card support
entirely moot? Feature freezes don't mean we can't improve
In some email I received from Randy Bush, sie wrote:
4.0-RELEASE sounds like it will start becoming available at about the same
time as other OS's make new releases *with* IPv6/IPSec. You work it out
whether or not FreeBSD will win or lose from those two being there or not
there.
In some email I received from Warner Losh, sie wrote:
In message [EMAIL PROTECTED] Josef Karthauser writes:
: My 3c589d works just fine now, along with suspend/resume :) (under 4.0).
The issue with the 3c589d is with its speed. It is falling back to
the timeout routine to send data
In freebsd-current [EMAIL PROTECTED] wrote:
Maybe I am wrong, but it seems to me that there is already quite a bit of
IPv6 and IPSec stuff in the tree. Most of the kernel stuff is there (albeit
seriously lacking documentation). To me this is not *too* critical right
now. I see the point for the
It seems Alexander Langer wrote:
ata* doesn't work for me at the moment, thus I'm using the wd drivers.
What is your problem ??
I posted this to the -current ml 3 weeks ago, when I wanted to switch.
See the "ata: Mount root failure: 6"-thread.
Hmm, that one, I thought (wrongly) that it
In some email I received from Poul-Henning Kamp, sie wrote:
[...]
In the meantime please enjoy:
NTFS filesytem
Netware support
Jail facility
Tons of new device drivers
Netgraph
etc, etc
Isn't that just that very incomplete list worth a
Whatever it is, results in ping times being 1000ms then 10ms then 1000ms
then 10ms...when it responds.
i.e. it's a mistake to use FreeBSD 3.x with the 3c589d.
FWIW, I'm using the 3c589d with 3.2-STABLE + PAO, and it's working just
fine.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
I tried the ATA_ENABLE_ATAPI_DMA option, it gave:
../../dev/ata/atapi-all.c: In function `atapi_attach':
../../dev/ata/atapi-all.c:150: syntax error before `)'
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166
It seems Fritz Heinrichmeyer wrote:
I tried the ATA_ENABLE_ATAPI_DMA option, it gave:
../../dev/ata/atapi-all.c: In function `atapi_attach':
../../dev/ata/atapi-all.c:150: syntax error before `)'
fixed.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Yikes! Seems fifi got out of the cage again. How did she figure out
the combination for the lock
* From: David Greenman [EMAIL PROTECTED]
* p.s. pardon the lack of capital letters but my paws can't quite reach
* the shift key and the alphabet keys at the same time
*
*If
Jordan K. Hubbard [EMAIL PROTECTED] wrote:
Any other SCSI CD owners here currently using tosha? I'd be
quite interested to know if this is drive-specific.
Works for me.
4.0-CURRENT from December 19,
Toshiba CD-ROM XM-3601TA 0175,
tosha-0.6.
--
Christian "naddy" Weisgerber
Why can't the driver enable the card instead. I can not shut the PNP OS
settings off on my mobo because of a Compaq "hack". Because of that my
Asante 10 does not start up - it does get detected though. Under Linux,
it detects that the card has not been enabled by the BIOS and then it does
it
This is a heads up to let you know that you need to
rm -f /sbin/chwon /bin/chgrp
after your next `make world'. Additionally you need to install a new
/dev/MAKEDEV (mergmaster(8) will assist you in this).
A while back I moved the install location for chown and chgrp from
/usr/sbin and
Hi,
Does anybody successfully using any DGA-based programs on recently
recompiled Xfree 3.3.5? I have a problem with it and for me it seems
broken. For example standart XFree86 test program 'dga' returns
following error on my two -current machines (Mach64 and CT 65554
servers recompiled
On Fri, Jan 07, 2000 at 05:48:09AM -0800, Satoshi Asami wrote:
Yikes! Seems fifi got out of the cage again. How did she figure out
the combination for the lock
I'm not sure, but I suspect she factored your private key. Maybe
if you didn't keep putting them in the INDEX commit logs...
This week, I have added chown-like functionality to mknod(8) and restored
chown chgrp back to their previous locations. MAKEDEV has been
updated to use the new functionality of mknod(8).
Thanks for doing this David!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Fri, Jan 07, 2000 at 01:29:27PM +0200, Sheldon Hearn wrote:
I think lint(1) might work with this given the following small patch.
I agree that lint might should continue to use /usr/libexec/cpp rather
than switch to /usr/bin/cpp. But not knowing anything about our lint, I
can't really say.
...
I strongly suggest to not release 4.0 till the IPv6 import has been finished.
Beside the need for IPv6 it would be wrong to ship a release with a half-
complete implementation.
I expect every person that has made similiar statements here and bore
all the developers with the additional
Around Yesterday, "Kenneth D. Merry" wrote :
Many of the opinions I've seen recently are that you jitter correction
isn't necessary for most newer CDROM drives. If you want jitter
correction, you can port cdd to CAM.
cdda2wav does jitter correction -
-P sectors --set-overlap
This shouldn't be a PNP-OS issue because this is a PCI card- the card is
seen during booting- which means it's getting detected. I don't know why
'ifconfig -l' doesn't see it though.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Hi Luigi,
i am looking at (minor) optimizations of the ipfw code in order to reduce
the running time in the common cases.
I have a few ideas (mostly along the lines of optimizing for the
most commonly-used rules). An obvious candidate is the 'match all'
rule (all from any to any), but can
I wouldn't think so. However, the problem disappears when the PNP OS
setting is set to OFF on another box - and it reappears when I turn it
back on. When Linux boots - it says something to the extent that the card
has not been initialized by the BIOS - and then it does it - this is when
the
Hmm. Very interesting and subtle. I'll check this out. Gawd, PCs are
*s* lame
On Fri, 7 Jan 2000, Thomas Veldhouse wrote:
I wouldn't think so. However, the problem disappears when the PNP OS
setting is set to OFF on another box - and it reappears when I turn it
back on. When Linux
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one skipto rule is enough to switch between two rulesets
Rodney W. Grimes wrote:
[complaining that people just complain instead of doing the work]
If you, the users, are not ready to do this, STOP asking those to be
the folks so described:
``We the willing have been doing so much with so little for so long
that we are now qualified to do
In message [EMAIL PROTECTED], Luigi Rizzo writes:
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one skipto
I still think we should split the current "one huge list of rules"
into several lists:
Two lists per interface:
one list of rules for inbound packets
one list of rules for outbound packets
Two lists for the IP stack:
one list of
In message [EMAIL PROTECTED], Luigi Rizzo writes:
I still think we should split the current "one huge list of rules"
into several lists:
Two lists per interface:
one list of rules for inbound packets
one list of rules for outbound packets
Two lists for
You know, the people reading this list are *not* the typical FreeBSD
users. The fact that releases occur at all is a concession to the
realities of the world - WCCDROM needs to pay it's bills by selling
CDROMs, and their business pressures require new updates on time and
to be as stable as
Doesn't this statement make the entire thread about IPv6 + PC-Card support
entirely moot? Feature freezes don't mean we can't improve those two areas,
right? Right? :-)
PC-card, perhaps, but I think IPv6 still needs "improvement" far less
that it needs significant integration. :)
- Jordan
I think you'd do far better to stop bitching and simply start helping.
The people I've heard yell the very loudest in this discussion are
also the people who:
a) Have not helped Yoshinobu Inoue to any great extent during his
calls for patch testing.
b) Have not volunteered to help with the
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one skipto rule is enough to switch between two rulesets
Matthew Dillon writes:
| Well guys, I tried upgrading one of my older machines today to the
| latest 4.0. It was running an older 4.0 kernel (Nov 29 1999).
I ran into a similar problem when upgrading my server at home. It is an
old 486 with an Intel Saturn chipset. I found the IDE
Hi,
I'm seeing the following error, and don't see any fixes in the
cvs repository yet. I am however, about an hour behind since I
get my updates from a standard mirror. My sources are current as
of about an hour ago...
If this is already fixed, just ignore
Thanks,
John
ln -sf
In message [EMAIL PROTECTED], Luigi Rizzo writes:
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one
Hi,
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1
incoming,
one list for ed1 outgoing, etc.).
I often do this manually in long rule sets by using
On Fri, Jan 07, 2000 at 11:37:02AM -0700, Nate Williams wrote:
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing,
I have a DEC Alpha at home running 4.0-current and am willing to help out with
the testing. I am not the worlds greatest coder, but am willing to do what I can
--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 07-Jan-00
Time: 12:09:03
FreeBSD 3.4
The issue with the 3c589d is with its speed. It is falling back to
the timeout routine to send data rather than getting an interrupt when
the tx has happened (or something like this, I'm reporting second hand
stuff).
Whatever it is, results in ping times being 1000ms then 10ms then
I agree that having a `switch' type of rule for selecting interfaces
would be a reasonable gain of efficiency (but then again.. how
many interfaces is one using!)
It doesn't matter, it has to do the lookup on a per-interface basis. On
my firewall box, I have 11 interfaces.
Two
On Fri, 7 Jan 2000, Michael Reifenberger wrote:
Hi,
after enabling the sym-driver I get drive-lockups after some time of accessing
the disks hanging on the sym-driver.
It seems that at least on disk hangs up (steady disk light) until a bus-reset
"(noperiph:sym0:0:-1:-1): SCSI BUS reset
Matthew Dillon wrote:
Well guys, I tried upgrading one of my older machines today to the
latest 4.0. It was running an older 4.0 kernel (Nov 29 1999).
..
HELP! Whats happening!!! :-( :-( :-(
At the moment I am stymied. I switched to a GENERIC kernel and
On Fri, Jan 07, 2000 at 09:48:22AM -0800, Matthew Jacob wrote:
This shouldn't be a PNP-OS issue because this is a PCI card- the card is
seen during booting- which means it's getting detected. I don't know why
'ifconfig -l' doesn't see it though.
I had an identical problem with de0 and 3.4
(don't you love all that quoting...)
I agree that having a `switch' type of rule for selecting interfaces
would be a reasonable gain of efficiency (but then again.. how
many interfaces is one using!)
It doesn't matter, it has to do the lookup on a per-interface basis.
On
my
I see from the FreeBSD driver database at http://www.posi.net/freebsd/drivers
that support for the Adaptec AAC-364 RAID controller (aka Dell PERC 2) has
been proposed, but it is stalled waiting on documentation from Adaptec.
For what it's worth, you can add us to the list of people who have
I see from the FreeBSD driver database at http://www.posi.net/freebsd/drivers
that support for the Adaptec AAC-364 RAID controller (aka Dell PERC 2) has
been proposed, but it is stalled waiting on documentation from Adaptec.
For what it's worth, you can add us to the list of people who
At 2:29 PM -0800 2000/1/7, Mike Smith wrote:
The aac-364 is likely to offer similar performance to the AMI MegaRAID
Enterprise 1500 and the Mylex eXtremeRAID 1164 controllers, both of which
we're currently supporting.
I'd be very interested to see a comparison of these controllers
No, this is completly reasonable now that I understand what it is your
proposing. Even the memory footprint is minimal if pointers to the
actual rules is all we store in the per interface list, my largest set
duplicated over 8 interfaces would only be 3200 rules. Stored as
pointers to
In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g
(and later CFLAGS=-g3), but ran into linker problems as a result.
blitz:~ gcc poll.c -pthread
/usr/lib/libc_r.so: undefined reference to `__sigisempty'
Even the simplest of C programs will get this linker error if
On Fri, Jan 07, 2000 at 07:36:11PM -0500, Luoqi Chen wrote:
In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g
(and later CFLAGS=-g3), but ran into linker problems as a result.
blitz:~ gcc poll.c -pthread
/usr/lib/libc_r.so: undefined reference to `__sigisempty'
...
install -c -o root -g wheel -m 444 README /usr/share/examples/dialog
install: README: No such file or directory
*** Error code 71
The following patch fixed the problem:
--- gnu/usr.bin/dialog/TESTS/Makefile.orig Fri Jan 7 22:35:43 2000
+++ gnu/usr.bin/dialog/TESTS/Makefile Fri Jan
These are my results:
% ifconfig -a
xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80:1::250:daff:fe20:495b prefixlen 64
inet 24.218.93.188 netmask 0xfc00 broadcast 24.218.95.255
ether 00:50:da:20:49:5b
On Fri, 7 Jan 2000, Luoqi Chen wrote:
In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g
(and later CFLAGS=-g3), but ran into linker problems as a result.
blitz:~ gcc poll.c -pthread
/usr/lib/libc_r.so: undefined reference to `__sigisempty'
Even the
64 matches
Mail list logo
