Oliver Fromme wrote:
Maybe I'm just too dumb... It's my understanding that the
purpose of the ``NODESCRYPTLINKS'' option in make.conf is
to prevent overwriting the libcrypt symlinks in /usr/lib.
Well, it doesn't work.
I cvsupped today in the morning (~ 9:00 UTC on Sunday), added
Hi,
Building the world with -DNOCRYPT -DNOPROFILE as is my habit, I'm getting
the following in stage 4:
/source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5
4: blowfish.h: No such file or directory
Hi all,
Just saw two identical console messages on a 3-day old 4.0-CURRENT
machine:
dc0: TX underrun -- resetting
Nothing special was happening on the near or far end of the link, system
is very lightly loaded. The only network activity was a telnet session
from another host. No unusual
Jérome OUFELLA wrote:
Hi,
I need to use a quite big NFS server, serving ~120GB for ~200
clients, all OS's mixed (*BSD, Linux, HP-UX, IRIX, Solaris, Xterminals).
Is it worth it to use the -current branch (-release on next monday
perhaps?) for this important server, or should I
On Sun, 12 Mar 2000, Oliver Fromme wrote:
Maybe I'm just too dumb... It's my understanding that the
purpose of the ``NODESCRYPTLINKS'' option in make.conf is
to prevent overwriting the libcrypt symlinks in /usr/lib.
Well, it doesn't work.
I cvsupped today in the morning (~ 9:00 UTC on
Hi,
I am building a release and am getting a failure during the doc phase
due to a port problem, (/usr/ports/www/w3m to be exact). This port is
built during make release, and it builds a program called 'mktable',
which core dumps, causing the whole make release to fail:
[...]
cc -O -pipe
I am running CURRENT as of last week. I seem to be only able to get my
sound to work when I use:
option PNPBIOS
device pcm0
Here is the dmesg output:
unknown9: ESS0009 at port 0x800-0x807 on isa0
sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq
1,5 on isa0
At 06:04 PM 3/12/00 -0500, Brian Dean wrote:
Hi,
I am building a release and am getting a failure during the doc phase
due to a port problem, (/usr/ports/www/w3m to be exact). This port is
built during make release, and it builds a program called 'mktable',
which core dumps, causing the whole
On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote:
Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better
way of approaching this.
To get the all-1's number, maybe it's better to use ((uid_t)~0), but
that is a rather controversial topic anyway.
- Giorgos
Giorgos Keramidas wrote:
On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote:
Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better
way of approaching this.
To get the all-1's number, maybe it's better to use ((uid_t)~0), but
that is a rather controversial
=== libkadm
rm -f .depend
mkdep -f .depend -a
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include
-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb
On Mon, 13 Mar 2000 00:06:19 +, Paul Richards [EMAIL PROTECTED] said:
We could create a new include file that we use for constants that are
related to FreeBSD specific types or we can agree on a coding style for
performing bounds checking using tricks like ((uid_t)0-1)
Or we can do it
I've had this occur also; usually I get the message twice at startup, then
at seemingly random times while online. So far, my connection has only
been dropped once -- I got a flurry of "dc0: TX underrun --
resetting" messages, then my connection died. I was able to bring it back
up with
Dear FreeBSDers,
after a couple of days spent RTFMing like crazy, I am back at my
console at last ! (yawn ...)
I have read some of the recent messages about X not working on
-CURRENT as well as other issues. Although my -CURRENT sources are the
same (last cvsup on 06-Mar-2000 11pm GMT), I seem
On Mon, Mar 13, 2000 at 12:29:14AM +, Salvo Bartolotta wrote:
Dear FreeBSDers,
after a couple of days spent RTFMing like crazy, I am back at my
console at last ! (yawn ...)
snip
Am I the sole person running X (compiled with PAM support) without
problems under -CURRENT ? :-)
OK,
What is the correct one??
How do I calulate the IP from IPv6, what is the formula?
Shaun
On Mon, 13 Mar 2000, Daniel C. Sobral wrote:
Yoshinobu Inoue wrote:
Shouldn't this be 2002:e071:8253: instead?
Ah, if real IPv4 addr is 240:113:130:083, then I think it will be,
oh The IPv4 I want to use is 24.113.25.85 and 24.113.130.83
Thanks..
On Mon, 13 Mar 2000, Daniel C. Sobral wrote:
Yoshinobu Inoue wrote:
Shouldn't this be 2002:e071:8253: instead?
Ah, if real IPv4 addr is 240:113:130:083, then I think it will be,
2002:f071:8253:
Err, f0,
On Sun, 12 Mar 2000, Michael L. Imamura wrote:
I've had this occur also; usually I get the message twice at startup, then
at seemingly random times while online. So far, my connection has only
been dropped once -- I got a flurry of "dc0: TX underrun --
resetting" messages, then my connection
Garrett Wollman wrote:
On Mon, 13 Mar 2000 00:06:19 +, Paul Richards [EMAIL PROTECTED] said:
We could create a new include file that we use for constants that are
related to FreeBSD specific types or we can agree on a coding style for
performing bounds checking using tricks like
On 2000-Mar-13 12:01:03 +1100, Paul Richards [EMAIL PROTECTED] wrote:
id = strtoul(p, (char **)NULL, 10);
if ((errno == ERANGE) || (id = UID_MAX)) {
warnx("%s max uid value (%lu)", p, UID_MAX);
return (0);
}
You can do this now. Just add the following:
pid_t
OK,
What is the correct one??
How do I calulate the IP from IPv6, what is the formula?
oh The IPv4 I want to use is 24.113.25.85 and 24.113.130.83
Are you tring to do multihoming? Then things might be more
complicated.
Let's forget the 2nd IPv4 addr for simplicity, now.
If your addr is
In article [EMAIL PROTECTED],
Paul Richards [EMAIL PROTECTED] wrote:
They must not go into limits.h. That header file is defined by
the ANSI/ISO C standard. The standard doesn't permit polluting the
namespace with extra stuff.
Umm, ok. I don't think our limits.h actually has
In article [EMAIL PROTECTED],
Giorgos Keramidas [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote:
Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better
way of approaching this.
To get the all-1's number, maybe it's better to use
John Polstra wrote:
In article [EMAIL PROTECTED],
Paul Richards [EMAIL PROTECTED] wrote:
They must not go into limits.h. That header file is defined by
the ANSI/ISO C standard. The standard doesn't permit polluting the
namespace with extra stuff.
Umm, ok. I don't think our
In article [EMAIL PROTECTED],
Paul Richards [EMAIL PROTECTED] wrote:
John Polstra wrote:
I guess it could go into machine/limits.h in the
"!defined(_ANSI_SOURCE)" section. Bruce might have a better idea.
I don't think machine/limits.h is the right place. These are constants
that are
(Now I am comfirming a new rc.conf entry which automate above
IPv6 prefix calucuration, and etc, for 6to4 interface configuration.)
As I also said in my previous mail with this subject, this is
committed.
If anyone intersted, please try it.
If you have IPv4 1.2.3.4 for your 6to4 interface,
Peter Jeremy wrote:
On 2000-Mar-13 12:01:03 +1100, Paul Richards [EMAIL PROTECTED] wrote:
id = strtoul(p, (char **)NULL, 10);
if ((errno == ERANGE) || (id = UID_MAX)) {
warnx("%s max uid value (%lu)", p, UID_MAX);
return (0);
}
You can do this now. Just add the
John Polstra wrote:
In article [EMAIL PROTECTED],
Paul Richards [EMAIL PROTECTED] wrote:
John Polstra wrote:
I guess it could go into machine/limits.h in the
"!defined(_ANSI_SOURCE)" section. Bruce might have a better idea.
I don't think machine/limits.h is the right place.
On Sun, 12 Mar 2000, Kris Kennaway wrote:
On Sun, 12 Mar 2000, Oliver Fromme wrote:
Maybe I'm just too dumb... It's my understanding that the
purpose of the ``NODESCRYPTLINKS'' option in make.conf is
to prevent overwriting the libcrypt symlinks in /usr/lib.
Well, it doesn't work.
I get the following error:
atapci0 CMD640 ATA Controller !WARNING! buggy chip data loss possible port
0xff08-0xff0b,0x3f4-0x3f7,0x1f0-0x1f7, IRQ14 at device 3.0 on PCI0
atapci0:Bus mastering DMA not supported
panic - resource_list_alloc resource list entry is busy
uptime 0s
(sorry couldn't
I get the following error:
atapci0 CMD640 ATA Controller !WARNING! buggy chip data loss possible port
0xff08-0xff0b,0x3f4-0x3f7,0x1f0-0x1f7, IRQ14 at device 3.0 on PCI0
atapci0:Bus mastering DMA not supported
panic - resource_list_alloc resource list entry is busy
uptime 0s
(sorry couldn't
I get the following error:
atapci0 CMD640 ATA Controller !WARNING! buggy chip data loss possible port
0xff08-0xff0b,0x3f4-0x3f7,0x1f0-0x1f7, IRQ14 at device 3.0 on PCI0
atapci0:Bus mastering DMA not supported
panic - resource_list_alloc resource list entry is busy
uptime 0s
(sorry couldn't
Says, it can't chdir into the 4.0-2307-CURRENT directory.
It does work from current.FreeBSD.org. Looking on ftp.freebsd.org
I do not see a link under /pub/FreeBSD/releases/i386/ ? that maybe
the missing link ?
It's there, am hauling it down at present...
I get the following error:
atapci0 CMD640 ATA Controller !WARNING! buggy chip data loss
possible port 0xff08-0xff0b,0x3f4-0x3f7,0x1f0-0x1f7, IRQ14
at device 3.0 on PCI0
atapci0:Bus mastering DMA not supported
panic - resource_list_alloc resource list entry is busy
uptime 0s
---
[EMAIL PROTECTED] ICQ 13383291
Metro Tasmania Pty Ltd Phone 0419585308
- If it works, tear it apart and find out why!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 13 Mar 2000 13:07:47 +1100, Paul Richards [EMAIL PROTECTED] wrote:
Peter Jeremy wrote:
You can do this now. Just add the following:
pid_t UID_MAX = ~0;
somewhere before the code.
I assume you meant uid_t,
Ooops, I did :-(. And this should probably be
uid_t
On Sun, 12 Mar 2000, John Polstra wrote:
In article [EMAIL PROTECTED],
Giorgos Keramidas [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote:
Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better
way of approaching this.
To
Is it just me, or are the weak symbols in libc_r confusing the linker?
When I link the following program with "gcc -v -g -static -pthread"
#include stdio.h
#include time.h
int main (int argc, char *argv[])
{
struct timespec t1;
struct timespec t2;
t1.tv_sec = 5;
[ just go back from one week of skiing, catching up ]
According to Kris Kennaway:
This sounds bad. Are you referring to the -o syntax differences, or actual
incompatabilities? There have been unsubstantiated reports of
interoperability problems, but nothing well documented here.
You'll have
On 2000-Mar-13 14:45:16 +1100, John Birrell [EMAIL PROTECTED] wrote:
the linker gives me the weak symbol version which refers to
_thread_sys_nanosleep (i.e. the syscall), instead of the nanosleep
function in libc_r.
Out of interest, why does nanosleep appear in libc_r.a as a weak
symbol version
On Mon, Mar 13, 2000 at 03:16:39PM +1100, Peter Jeremy wrote:
Out of interest, why does nanosleep appear in libc_r.a as a weak
symbol version of _thread_sys_nanosleep at all? I would have thought
this was unnecessary (and based on my experiments, undesirable).
I don't think it is necessary.
Peter Jeremy wrote:
On 2000-Mar-13 13:14:40 +1100, Paul Richards [EMAIL PROTECTED] wrote:
#define UID_MAX ((uid_t)0-1)
...
I can see the flaw in that straight away in that uid_t isn't available
in sys/syslimits.h
Not a problem. C macros are just text expansions. The `uid_t' isn't
I built a -CURRENT kernel yesterday and had no problems. Today I
can't mount the root file system: I get a panic "bp not locked" out of
bremfree. Of course I can't take a dump (remind me whose idea it was
to take the dumpdev out of the config file), but here's the stack
trace I wrote down from
Kris Kennaway [EMAIL PROTECTED] wrote in list.freebsd-current:
DES crypt links have a "higher priority" than MD5 crypt links - if you do
a make install in secure/lib/libcrypt or lib/libcrypt, each will overwrite
the libcrypt links of the other. The difference is that make world runs
At 05:30 PM 3/12/00 -0600, Jeffrey J. Mountin wrote:
At 06:04 PM 3/12/00 -0500, Brian Dean wrote:
Hi,
I am building a release and am getting a failure during the doc phase
due to a port problem, (/usr/ports/www/w3m to be exact). This port is
built during make release, and it builds a program
On Mon, 13 Mar 2000, Oliver Fromme wrote:
"WANTDESCRYPTLINKS" is the historical behaviour which hasn't
changed.
Are you sure? I think the historical behaviour was to _not_
touch the symlinks at all, which I thought was a very sensible
and POLA-conforming default. I'm always using
And if you want to check 6to4 prefix for some IPv4 addr
without doing 6to4 interface configuration, please try
following command.
echo 24.113.25.85 | sed -e s/"\."/" "/g | awk '{$5 = $1*256 + $2; $6 = $3*256 + $4;
printf "2002:%x:%x:\n", $5, $6}'
Then it will print out first 6byte for your
echo 24.113.25.85 | sed -e s/"\."/" "/g | awk '{$5 = $1*256 + $2; $6 = $3*256 +
$4; printf "2002:%x:%x:\n", $5, $6}'
Then it will print out first 6byte for your 6to4 prefix.
just checking. from code inspection on cvsweb,
- rc.network6 is called before performing nfs
On Sun, 12 Mar 2000, John Polstra wrote:
Sheesh, criticism isn't enough? Now it has to be constructive too? ;-)
I guess it could go into machine/limits.h in the
"!defined(_ANSI_SOURCE)" section. Bruce might have a better idea.
This is the same as putting it in limits.h in the
On Sun, 12 Mar 2000, Randy Bush wrote:
riscom/8 used to work on this box when running 3.4-stable.
Try this fix.
Index: isa_compat.h
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
retrieving revision 1.27
diff -c -2
"Michael L. Imamura" wrote:
I haven't tried xfce, but I had some problems running Enlightenment 16.3,
all related to shared memory. I disabled shared pixmaps in my Imlib
configuration and that got rid of the random crashing, but is again not a
very optimal solution :) I'm guessing it's a
On Mon, Mar 13, 2000 at 02:52:02PM +1100, John Birrell wrote:
Is it just me, or are the weak symbols in libc_r confusing the linker?
Not just you. Jason and Mike Smith brought this to my attention on
Friday. I found that if one takes a fresh -CURRENT and then:
cd /usr/src/lib/libc_r
riscom/8 used to work on this box when running 3.4-stable.
Try this fix.
Index: isa_compat.h
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
retrieving revision 1.27
diff -c -2 -r1.27 isa_compat.h
***
On Sun, Mar 12, 2000 at 11:07:40PM -0800, David O'Brien wrote:
On Mon, Mar 13, 2000 at 02:52:02PM +1100, John Birrell wrote:
Is it just me, or are the weak symbols in libc_r confusing the linker?
Not just you. Jason and Mike Smith brought this to my attention on
Friday. I found that if
Hello, I'm trying to install FreeBSD-Current from a DOS (FAT32,
although attempts have been made from FAT16) partition onto a dedicated
FBSD disk. Everything runs smoothly until it reaches the 'attempting to
extract selected distributions' section of the install. The installation
locks up and
On Sat, Mar 11, 2000 at 10:24:16AM -0500, Bryan Liesner wrote:
The strange thing is that the network never goes down if I run tcpdump
in promiscuous mode on the interface - it's a workaround, but I don't
like it.
I saw a problem like this with the old driver some time ago, where
the
Just some error I got when I try to make release this afternoon.
(cvs up to the latest). Maybe it is worthful to anyone making
release all the time :_)
##
a - textlist.o
a - parsetag.o
ranlib libindep.a
cc -O -pipe -I/usr/local/include -I. -o mktable mktable.o hash.o
-L/usr/local/lib
Maybe I'm just too dumb... It's my understanding that the
purpose of the ``NODESCRYPTLINKS'' option in make.conf is
to prevent overwriting the libcrypt symlinks in /usr/lib.
Well, it doesn't work.
I cvsupped today in the morning (~ 9:00 UTC on Sunday), added
NODESCRYPTLINKS=true to
I have also seen this on both our -stable and -current snap building
machines.
John
--
John Hay -- [EMAIL PROTECTED]
Just some error I got when I try to make release this afternoon.
(cvs up to the latest). Maybe it is worthful to anyone making
release all the time :_)
##
a
Yoshinobu Inoue wrote:
So my IPv4 address is 24.113.130.83 that in IPv6 would be
2002:240:113:130:083 ??
No, no, because IPv6 address is printed in hex format each
2bytes separated by collon, so the 1st 6bytes will be,
2002:1871:8253:
Shouldn't this be 2002:e071:8253: instead?
--
I did a fresh install of 4.0-2308-current. I have a Compaq Presario
5170 128 megs of ram
and 10gig HD.
Installation went smoothly, except for these 2 problems.
1). The libXThrStub.so.6 file (elf) is missing. It is there for aout
2). I don't have the FAQ or handbook files! I have gone back
So my IPv4 address is 24.113.130.83 that in IPv6 would be
2002:240:113:130:083 ??
No, no, because IPv6 address is printed in hex format each
2bytes separated by collon, so the 1st 6bytes will be,
2002:1871:8253:
Shouldn't this be 2002:e071:8253: instead?
Ah, if real IPv4
Yoshinobu Inoue wrote:
Shouldn't this be 2002:e071:8253: instead?
Ah, if real IPv4 addr is 240:113:130:083, then I think it will be,
2002:f071:8253:
Err, f0, of course... :-)
(Now I am comfirming a new rc.conf entry which automate above
IPv6 prefix calucuration, and etc, for 6to4
Hi,
I've upgraded my desktop to Current. All is ok (small problems with
the ata driver but it works fine with the old wd driver) but my
network is slow to death :
Here are the results of a ping to my laptop (under current too) :
--- alex.titine.fr.eu.org ping statistics ---
306 packets
riscom/8 used to work on this box when running 3.4-stable.
in kernel conf, i have
# sdl riscom/8
device rc0 at isa? port 0x220 irq 12
the devices are there
# ls -l /dev/ttym* /dev/cuam*
crw-rw 1 uucp dialer 63, 128 Mar 12 11:18 /dev/cuam0
crw-rw 1
Hello,
I am getting the following errors out of FreeBSD 4.0-CURRENT trying to
run an IRC server, and was wondering if anyone had any ideas or recommended
tunables I should set??
Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for
[@163.152.216.46]:No buffer
66 matches
Mail list logo
