Re: NODESCRYPTLINKS=true doesn't work
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 NODESCRYPTLINKS=true to /etc/make.conf, "make buildworld", "make installworld", and couldn't log in anymore because the symlinks had been set to libscrypt (and I'm using DES passwords). Hmmm If you ARE using DES passwords, don't you want to have crypt linked to it so you CAN use DES passwords? As I understand it, the purpose of the NODESCRYPTLINKS is to allow the "real" DES libraries to be on the system but have crypt link to the md5 versions. Maybe I don't understand what you're trying to accomplish here... Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World not building
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 /source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5 6: rc5.h: No such file or directory /source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5 9: cast.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /source/cleansrc/usr.sbin/tcpdump/tcpdump. *** Error code 1 Stop in /source/cleansrc/usr.sbin/tcpdump. *** Error code 1 Stop in /source/cleansrc/usr.sbin. *** Error code 1 Stop in /source/cleansrc. *** Error code 1 Have I missed something? Any ideas? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
dc0: TX underrun -- resetting
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 daemons running (actually, just the stock daemons). This card is communicating directly with another identical card, 100BaseTX full duplex. I never saw these messages with the pn0 driver under -STABLE or earlier with the same card. (FA310TX (Lite-On chipset)). Is this just a new diagnostic message in 4.0? No connections were dropped that I could see. -- Ryan Thompson [EMAIL PROTECTED] Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4 vs. 4.0 NFS Code performance
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 rather use the 3.4-STABLE NFS implementation ? For heavy NFS use I wouldn't consider anything else. We've had September-vintage 4.0-current (as in, right after the big NFS fixes went in) machines in production and never had problems with them. We're getting ready to go to 4.0-Release when we get a chance. I'm already using it for other things. That said, you shouldn't expect 4.0-Release to be like a -Stable branch, not yet anyway. Be ready to live up to the usual -current responsibilities, like following this list, etc. Good luck, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NODESCRYPTLINKS=true doesn't work
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 Sunday), added NODESCRYPTLINKS=true to /etc/make.conf, "make buildworld", "make installworld", and couldn't log in anymore because the symlinks had been set to libscrypt (and I'm using DES passwords). I guess that's not how it's supposed to work, is it? No :) 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 secure/lib/libcrypt last, so the DES links win. So, as the name suggests, unless you want no DES crypt links (keep the MD5 links, please!), you don't use it. "WANTDESCRYPTLINKS" is the historical behaviour which hasn't changed. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release failing in /usr/ports/www/w3m/work/w3m
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/usr/local/include -I. -c indep.c cc -O -pipe -I/usr/local/include -I. -c regex.c cc -O -pipe -I/usr/local/include -I. -c textlist.c cc -O -pipe -I/usr/local/include -I. -c parsetag.c ar rv libindep.a Str.o indep.o regex.o textlist.o parsetag.o a - Str.o a - indep.o a - regex.o 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 -L. -lindep -lgc -lm -lncurses ./mktable 100 tagtable.tab tagtable.c Segmentation fault - core dumped *** Error code 139 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. The core dump is optimization related, i.e., if I go in and manually build 'mktable' without optimization, it works. Is anyone else seeing this? Thanks, -Brian -- Brian Dean [EMAIL PROTECTED] SAS Institute Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound driver
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 pcm0: SB DSP 3.01 (ESS mode) on sbc0 unknown10: ESS0001 at port 0x201 on isa0 I would like to get rid of all the unknowns caused by the PNPBIOS option. If anyone has any ideas I am game to try. Sorry for the cross-post TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- Errors have been made others will be blamed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failing in /usr/ports/www/w3m/work/w3m
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 make release to fail: Ironically just built docproj and it did register, but complained after doing so. === Registering installation for docproj-1.1 docproj-1.1: "/working/usr/ports/www/w3m" non-existent -- dependency list incomplete It's listed in the RUN_DEPENDS, but didn't build it. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 Keramidas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 topic anyway. Well it would be worth deciding on some standard way of dealing with this problem. I've been wandering around the code for the last few days and the same issue crops up all over the place i.e. bounds checking. There are a lot of programs that currently work on alpha only because no-one is hitting the boundary conditions e.g. ipfw checks for rule number limits based upon ULONG_MAX rather than the size of the field that holds the rule number. 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) The code solution is robust in that if the type changes size the code still works. Using constants has the advantage that it is easy to document what the limits are on certain paramters such as IPFW rule numbers since you'll be able to look them up. All we have to do then is write all the bounds checking code :-) Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libkadm buildworld failure
=== 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 -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78, from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c:34: /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro name mkdep: compile failed *** Error code 1 Stop in /usr/src/kerberosIV/lib/libkadm. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 the right way, by assigning to a variable of the correct type and checking that the value remains unchanged. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0: TX underrun -- resetting
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 "ifconfig dc0 up", but it was a little unsettling. I'm using 4.0-RC2 with the following chipset: dc0: 82c168 PNIC 10/100BaseTX port 0xb400-0xb4ff mem 0xe000-0xe0ff irq 10 at device 11.0 on pci0 Michael L. Imamura Georgia Institute of Technology, Atlanta Georgia, 30332 Email: [EMAIL PROTECTED] On Sun, 12 Mar 2000, Ryan Thompson wrote: 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 daemons running (actually, just the stock daemons). This card is communicating directly with another identical card, 100BaseTX full duplex. I never saw these messages with the pn0 driver under -STABLE or earlier with the same card. (FA310TX (Lite-On chipset)). Is this just a new diagnostic message in 4.0? No connections were dropped that I could see. -- Ryan Thompson [EMAIL PROTECTED] Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
upgraded to -CURRENT et al -- solved; X and PAM work for me
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 to have solved most of my difficulties. Remark I Since I am a bit paranoid, I remade the world once more (exactly by the book, except for m.m. of course), and, wait for it, I met NO errors in making installworld. NO errors. Even sysinstall, after making (it) clean, was made smoothly. I am running a full-blown -CURRENT :-)) [wild screams of joy censored] In the past few weeks, under a -STABLE installation of mine (which was to become my present -CURRENT), I had compiled XFree86-3.3.6 with PAM support, among other things. As I wrote a couple of days ago, I met authentication errors with my freshly-(re)made -CURRENT. However, my pam.conf and ttys files were perfectly correct. Thus I recompiled X (with PAM support yet again!) and this time ... it worked seamlessly. Am I the sole person running X (compiled with PAM support) without problems under -CURRENT ? :-) HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: upgraded to -CURRENT et al -- solved; X and PAM work for me
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 ? :-) Well, it works for me too. I use wdm with pam for pam_ssh.so's session features. Works great and it's a lot handier than having to open an xterm every session to 'ssh-add' or having ssh-askpass load up after login. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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, 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 interface configuration.) Nice. You have been doing a great job. -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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, of course... :-) (Now I am comfirming a new rc.conf entry which automate above IPv6 prefix calucuration, and etc, for 6to4 interface configuration.) Nice. You have been doing a great job. -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0: TX underrun -- resetting
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 died. I was able to bring it back up with "ifconfig dc0 up", but it was a little unsettling. I'm using 4.0-RC2 with the following chipset: I get the same messages on my dc1 on my "lan" - just a win98 box connected to the freebsd box. dc0 is connected to the internet with a DSL modem and I've yet to see this on dc0. I swapped interfaces also, but it only seems to happen on the local network. My local network also goes down, it could be five minutes or two hours and I have to do an ifconfig dc1 down/up to make it right again. As a workaround, I found that running tcpdump on the dc1 interface keeps things alive, so far indefinitely. -Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 ((uid_t)0-1)
Or we can do it the right way, by assigning to a variable of the
correct type and checking that the value remains unchanged.
I'm not just trying to determine whether a value fits into a type, I'm
also trying to find out what the maximum value the type can hold is.
e.g. in the following code snippet
id = strtoul(p, (char **)NULL, 10);
if (errno == ERANGE) {
warnx("%s max uid value (%lu)", p, ULONG_MAX);
return (0);
}
you also have to print out the maximum value. Not an uncommon
requirement for error reporting.
You're solution doesn't help with the second part.
What I'm looking at is the following.
id = strtoul(p, (char **)NULL, 10);
if ((errno == ERANGE) || (id = ((uid_t)0-1))) {
warnx("%s max uid value (%lu)", p, ((uid_t)0-1));
return (0);
}
or the alternative
id = strtoul(p, (char **)NULL, 10);
if ((errno == ERANGE) || (id = UID_MAX)) {
warnx("%s max uid value (%lu)", p, UID_MAX);
return (0);
}
When you see it written out like that the latter is a lot more
informative. It also provides the flexibility to limit the parameters
max value even if the type allows it to be larger. This is of particular
significance to UIDs which are currently limited to a far smaller value
than would fit in a uid_t.
Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 UID_MAX = ~0;
somewhere before the code.
When you see it written out like that the latter is a lot more
informative. It also provides the flexibility to limit the parameters
max value even if the type allows it to be larger. This is of particular
significance to UIDs which are currently limited to a far smaller value
than would fit in a uid_t.
AFAIK, there's no real hard limit. adduser(8) limits uids to 32000
to prevent portability problems with systems using a signed 16-bit
uid_t (whilst allowing for a few `special' uids near the top of the
range). Other potential limits are ~65000 (16-bit unsigned) and
9 (5 decimal digits).
It would be nice if there was a system-wide constant that could be
used for this, but it's not obvious where this should be located.
(And note that adduser(8) is a perl script, so it can't use a C
header file without some contortions).
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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 24.113.25.85, and you have updated your
source, and your /etc dir, then I think you can setup your
6to4 interface by specifying rc.conf entry.
If following entry is added to /etc/rc.conf, and system rebooted,
stf_interface_ipv4addr="24.113.25.85"
then I expect your stf interface to be collectly setup.
The result and the 6to4 prefix can be check by "ifconfig stf0".
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 6to4 prefix.
And then let's talk about 2 IPv4 addr issue.
Do you want to setup 2 6to4 interface on same host?
Unfortunately, current implementation don't support it.
If you have 2 separate machine, then each host can setup 6to4
interface. But there will be another general multihoming issue.
-Which 6to4 interface should be choosed for outgoing
connection, from your site to outside.
-Which source addr(source prefix) should be choosed for
outgoing connection.
(because there will be 2 different 6to4 prefixes.)
-Which internal routes should be announced to which interface.
(because there will be 2 different 6to4 prefix routes.)
-Do packets for a connection traverse same 6to4 interface for
outgoing case and incoming case?
etc.
Cheers,
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 anything in it that meets the ANSI/ISO standard, every line is ifdef'd :-) Where would be a better place for constants like this? 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. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 ((uid_t)~0), but that is a rather controversial topic anyway. That works, but on machines like the Alpha where longs are bigger than ints it only works by virtue of sign extension. Our existing headers seem to prefer ((uid_t)0-1). That's what is used in the i386's machine/limits.h. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 limits.h actually has anything in it that meets the ANSI/ISO standard, every line is ifdef'd :-) Where would be a better place for constants like this? 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. I don't think machine/limits.h is the right place. These are constants that are definately not architecture dependent. The whole problem at the moment is that the code is abusing architecture dependent constants in lieu of anything better. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 definately not architecture dependent. The whole problem at the moment is that the code is abusing architecture dependent constants in lieu of anything better. Hmm, you're right. How about sys/syslimits.h? John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
(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, and if you add following entry, and reboot, stf_interface_ipv4addr="1.2.3.4" then your stf(6to4) interface will be automatically configured. Now 7th and 8th octet value(Site Level Aggregator) for the prefix of stf interface is set to 0 by default. To change them, please add stf_interface_ipv6_slaid="" and change the value between and as you like. Also interface id of stf 6to4 IPv6 addr is set to 0:0:0:1 by default. To change them, please add stf_interface_ipv6_ifid="0:0:0:1" and change the value. If you want it to be automatically set to something like used for your other interface's IPv6 link local addr, then please choose AUTO, like below. stf_interface_ipv6_ifid="AUTO" Also, the prefixlen of stf interface can be set to longer than 16, to limit the remote site to some extent of IPv4 address scope. It can be changed by adding following entry, stf_interface_ipv4plen="0" and change the value between 0 to 31. Nice. You have been doing a great job. You are welcome. :-) And also much part of acknowledgments should go to other KAME members, testers and patches contributor for FreeBSD project and KAME project. Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 following:
pid_t UID_MAX = ~0;
somewhere before the code.
I assume you meant uid_t, but anyway, yes that can be done but I'm
looking for a more generic solution since this is a widespread problem
in the userland code.
When you see it written out like that the latter is a lot more
informative. It also provides the flexibility to limit the parameters
max value even if the type allows it to be larger. This is of particular
significance to UIDs which are currently limited to a far smaller value
than would fit in a uid_t.
AFAIK, there's no real hard limit. adduser(8) limits uids to 32000
to prevent portability problems with systems using a signed 16-bit
uid_t (whilst allowing for a few `special' uids near the top of the
range). Other potential limits are ~65000 (16-bit unsigned) and
9 (5 decimal digits).
The actual limit is 4294967295, which is the largest number that will
fit into the the 32-bit uid_t. This does work, I've been playing around
with it for the last few days. At least, it works from a kernel
perspective, there are many applications that screw things up, most of
them use atol to do conversions which limits the UID to half that. If
you stick within the signed 32 bit limits most things seem to work.
It would be nice if there was a system-wide constant that could be
used for this, but it's not obvious where this should be located.
(And note that adduser(8) is a perl script, so it can't use a C
header file without some contortions).
Perl can use C include files (after performing some magic) so that
wouldn't be a problem.
Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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. These are constants that are definately not architecture dependent. The whole problem at the moment is that the code is abusing architecture dependent constants in lieu of anything better. Hmm, you're right. How about sys/syslimits.h? That sounds ideal :-) I guess my next question is, are there any objections to #define UID_MAX ((uid_t)0-1) which would actually give us the best of both worlds. I assume that gcc optimises the calculation away so it's effectively a constant but automagically of the right size. I can see the flaw in that straight away in that uid_t isn't available in sys/syslimits.h On the other hand, since you may want to limit the MAX_UID (or some other paramter) independently of the size of the type then its probably best to maintain the value manually in any case. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NODESCRYPTLINKS=true doesn't work
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 cvsupped today in the morning (~ 9:00 UTC on Sunday), added NODESCRYPTLINKS=true to /etc/make.conf, "make buildworld", "make installworld", and couldn't log in anymore because the symlinks had been set to libscrypt (and I'm using DES passwords). I guess that's not how it's supposed to work, is it? No :) 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 secure/lib/libcrypt last, so the DES links win. So, as the name suggests, It's a bug for install rules to overwrite each others results. unless you want no DES crypt links (keep the MD5 links, please!), you don't use it. "WANTDESCRYPTLINKS" is the historical behaviour which hasn't changed. The historical behaviour was not to touch existing links. This was broken in rev.1.20 of libcrypt/Makefile. This Makefile even overwrites its own links after creating them the first time. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Booting from the 4.0 RC3 Floppy disks..
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 resist the last entry)... Ok.. Got this in an attempt to install the RC3, onto a machine presently running 3.4 successfully... The only change I made to the configuration was to change the port on the NE2000 network card from 0x280 to 0x300 (what it's set to). To sum it up... HELP --- dmesg from the boot after trying to install 4.0 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RELEASE #0: Wed Jan 5 11:21:46 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/Snoopy Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 36826433 Hz CPU: Pentium/P54C (36.83-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping = 1 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 41943040 (40960K bytes) avail memory = 38539264 (37636K bytes) Bad BIOS32 Service Directory! Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x10 on pci0.0.0 chip1: Intel 82378ZB PCI to ISA bridge rev 0x03 on pci0.2.0 wdc0: CMD 640B IDE rev 0x01 int a irq 14 on pci0.3.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:00:e8:a3:65:34, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: CMD640B workaround enabled wdc0: unit 0 (wd0): QUANTUM FIREBALL_TM2550A wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): ST5850A wd2: 815MB (1669248 sectors), 1656 cyls, 16 heads, 63 S/T, 512 B/S ppc0 not found ze0 not probed due to I/O address conflict with ed0 at 0x300 zp0 not probed due to I/O address conflict with ed0 at 0x300 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Booting from the 4.0 RC3 Floppy disks..
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 resist the last entry)... Ok.. Got this in an attempt to install the RC3, onto a machine presently running 3.4 successfully... The only change I made to the configuration was to change the port on the NE2000 network card from 0x280 to 0x300 (what it's set to). To sum it up... HELP --- dmesg from the boot after trying to install 4.0 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RELEASE #0: Wed Jan 5 11:21:46 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/Snoopy Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 36826433 Hz CPU: Pentium/P54C (36.83-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping = 1 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 41943040 (40960K bytes) avail memory = 38539264 (37636K bytes) Bad BIOS32 Service Directory! Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x10 on pci0.0.0 chip1: Intel 82378ZB PCI to ISA bridge rev 0x03 on pci0.2.0 wdc0: CMD 640B IDE rev 0x01 int a irq 14 on pci0.3.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:00:e8:a3:65:34, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: CMD640B workaround enabled wdc0: unit 0 (wd0): QUANTUM FIREBALL_TM2550A wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): ST5850A wd2: 815MB (1669248 sectors), 1656 cyls, 16 heads, 63 S/T, 512 B/S ppc0 not found ze0 not probed due to I/O address conflict with ed0 at 0x300 zp0 not probed due to I/O address conflict with ed0 at 0x300 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Booting from the 4.0 RC3 Floppy disks..
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 resist the last entry)... Ok.. Got this in an attempt to install the RC3, onto a machine presently running 3.4 successfully... The only change I made to the configuration was to change the port on the NE2000 network card from 0x280 to 0x300 (what it's set to). To sum it up... HELP --- dmesg from the boot after trying to install 4.0 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RELEASE #0: Wed Jan 5 11:21:46 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/Snoopy Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 36826433 Hz CPU: Pentium/P54C (36.83-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping = 1 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 41943040 (40960K bytes) avail memory = 38539264 (37636K bytes) Bad BIOS32 Service Directory! Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x10 on pci0.0.0 chip1: Intel 82378ZB PCI to ISA bridge rev 0x03 on pci0.2.0 wdc0: CMD 640B IDE rev 0x01 int a irq 14 on pci0.3.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:00:e8:a3:65:34, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: CMD640B workaround enabled wdc0: unit 0 (wd0): QUANTUM FIREBALL_TM2550A wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): ST5850A wd2: 815MB (1669248 sectors), 1656 cyls, 16 heads, 63 S/T, 512 B/S ppc0 not found ze0 not probed due to I/O address conflict with ed0 at 0x300 zp0 not probed due to I/O address conflict with ed0 at 0x300 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: 4.0 RC3 install problem from ftp.FreeBSD.org
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... `ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT/' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Booting from the 4.0 RC3 Floppy disks..
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 resist the last entry)... Ok.. Got this in an attempt to install the RC3, onto a machine presently running 3.4 successfully... The only change I made to the configuration was to change the port on the NE2000 network card from 0x280 to 0x300 (what it's set to). To sum it up... HELP --- dmesg from the boot after trying to install 4.0 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RELEASE #0: Wed Jan 5 11:21:46 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/Snoopy Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 36826433 Hz CPU: Pentium/P54C (36.83-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping = 1 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 41943040 (40960K bytes) avail memory = 38539264 (37636K bytes) Bad BIOS32 Service Directory! Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x10 on pci0.0.0 chip1: Intel 82378ZB PCI to ISA bridge rev 0x03 on pci0.2.0 wdc0: CMD 640B IDE rev 0x01 int a irq 14 on pci0.3.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:00:e8:a3:65:34, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: CMD640B workaround enabled wdc0: unit 0 (wd0): QUANTUM FIREBALL_TM2550A wd0: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): ST5850A wd2: 815MB (1669248 sectors), 1656 cyls, 16 heads, 63 S/T, 512 B/S ppc0 not found ze0 not probed due to I/O address conflict with ed0 at 0x300 zp0 not probed due to I/O address conflict with ed0 at 0x300 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Heh Heh Ooops... Sorry Stuffed sendmail.cf file ... Sorry...
--- [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
Re: MAX_UID ?
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 UID_MAX = ~0L; to avoid problems if int != long (as John mentioned in passing). The actual limit is 4294967295, which is the largest number that will fit into the the 32-bit uid_t. This does work, I had an idea that NFSv2 only allowed 16-bit UIDs, but I can't find any code in FreeBSD, or the relevant RFCs, to support this (possibly some NFS clients/servers ignore the top 16 bits). I did notice, however, that VNOVAL (-1) is used to mean the UID isn't present in some places - and (uid_t)2^32-1 == (uid_t)-1. 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 evaluated unless/until the macro is used - at which point uid_t must be available. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 get the all-1's number, maybe it's better to use ((uid_t)~0), but that is a rather controversial topic anyway. That works, but on machines like the Alpha where longs are bigger than ints it only works by virtue of sign extension. Our existing headers seem to prefer ((uid_t)0-1). That's what is used in the i386's machine/limits.h. All 3 of these are broken in general. ((uquad_t)0-1) in machine/limits.h works because it is known that uquad_t is no smaller than int. If foo_t is smaller than int, then (foo_t)0 in an expression gets promoted to plain 0, which is rarely what you want. ((uid_t)~(uid_t)0) is probably best. The first cast gives a sufficient number of 0 bits and the second cast discards unwanted 1 bits. -1 is sometimes used instead of ~0 because there is a good rule for converting -1 to an unsigned type. I can never quite remember this rule, so I prefer to use ~something. Part of the rule is that (unsigned int)-1 has all bits 1 even if -1 doesn't have all bits 1. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weak symbols in libc_r broken?
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;
t1.tv_nsec = 0;
nanosleep(t1,t2);
printf("Remaining time %ld.%09ld\n",(long) t2.tv_sec, (long) t2.tv_nsec);
return(0);
}
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.
Is there someone with a recent -current system who has time to try
this out? Link the program and use gdb to disassemble the nanosleep
function. If you get:
(gdb) disassemble nanosleep
Dump of assembler code for function nanosleep:
0x804821c nanosleep: leal 0xf0,%eax
0x8048222 nanosleep+6:int$0x80
0x8048224 nanosleep+8:jb 0x8048214 atexit+92
0x8048226 nanosleep+10: ret
0x8048227 nanosleep+11: nop
End of assembler dump.
... then libc_r is broken.
TIA.
--
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
[EMAIL PROTECTED] [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
[ 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 a problem if you have very old "identity" files laying in .ssh because in the Old Days[tm] the private key was protected with IDEA on disk... You'll have to recreate the private/public RSA keys with ssh-keygen and copy the "identity.pub" content into your remote "authorized_keys" files. Ollivier, who got bitten by this :) -rw--- 1 roberto staff 540 Sep 7 1995 identity -rw-r--r-- 1 roberto staff 344 Sep 7 1995 identity.pub -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols in libc_r broken?
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 of _thread_sys_nanosleep at all? I would have thought this was unnecessary (and based on my experiments, undesirable). Is there someone with a recent -current system who has time to try this out? I have -current from 9th March and get the same results you do. Looking at last night's buildworld results, there doesn't appear to be any change in the symbols in libc_r.a and when I try manually performing the link with the ld in /usr/obj/..., I still get the same result. ... then libc_r is broken. This is a particularly bad time to discover what appears to be a fairly serious bug in the threaded libraries and/or linker. I just tried fiddling with the order in which uthread_nanosleep.o and nanosleep.o appear in libc_r.a. It seems that the linker always picks the first definition of the symbol found after the first reference to the symbol - whether it is weak or not. Since nanosleep.o appears before uthread_nanosleep.o, the non thread-safe version will be picked. I suspect the only solution is to dispose of the weak symbols - re-ordering the object file isn't an option given the requirement for the non-weak symbol to always appear between the reference and the weak symbol. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols in libc_r broken?
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. It got caught up in the cancellation changes that Jason made. Is there someone with a recent -current system who has time to try this out? I have -current from 9th March and get the same results you do. Looking at last night's buildworld results, there doesn't appear to be any change in the symbols in libc_r.a and when I try manually performing the link with the ld in /usr/obj/..., I still get the same result. ... then libc_r is broken. This is a particularly bad time to discover what appears to be a fairly serious bug in the threaded libraries and/or linker. I just tried fiddling with the order in which uthread_nanosleep.o and nanosleep.o appear in libc_r.a. It seems that the linker always picks the first definition of the symbol found after the first reference to the symbol - whether it is weak or not. Since nanosleep.o appears before uthread_nanosleep.o, the non thread-safe version will be picked. I suspect the only solution is to dispose of the weak symbols - re-ordering the object file isn't an option given the requirement for the non-weak symbol to always appear between the reference and the weak symbol. I agree. Thanks for helping out. -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 evaluated unless/until the macro is used - at which point uid_t must be available. Uhh, yeah. It's the middle of the night here I obviously wasn't awake when I said that :-) Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic mounting root from today's kernel
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 ddb: bremfree+0x5d getnewbuf+0x1ca geteblk+0x1f dsinit+0x1b dsopen+0xde spec_open+0xfd ffs_mountfs+0x1cf ffs_mount+0x7c vfs_mountroot_try+0x13d Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NODESCRYPTLINKS=true doesn't work
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 secure/lib/libcrypt last, so the DES links win. So, as the name suggests, unless you want no DES crypt links (keep the MD5 links, please!), you don't use it. Ah, now I understand. Thankyou very much for the explanation. May I suggest that the above paragraph is added to the setting in etc/defaults/make.conf? The current comment in that file is not really helpful. At least not for me. :-) "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 the DES-capable crypt lib (to be able to share passwords with Solaris boxes), and a "make world" never changed the symlinks. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failing in /usr/ports/www/w3m/work/w3m
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 called 'mktable', which core dumps, causing the whole make release to fail: Ironically just built docproj and it did register, but complained after doing so. === Registering installation for docproj-1.1 docproj-1.1: "/working/usr/ports/www/w3m" non-existent -- dependency list incomplete It's listed in the RUN_DEPENDS, but didn't build it. Never mind. Pilot error. Missing parts of the port tree and at first glance missed the lines in the saved build output. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NODESCRYPTLINKS=true doesn't work
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 the DES-capable As Bruce explained, someone broke it a while back. crypt lib (to be able to share passwords with Solaris boxes), and a "make world" never changed the symlinks. For the reason I already explained. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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 6to4 prefix.
just checking. from code inspection on cvsweb,
- rc.network6 is called before performing nfs mounts.
- awk and sed are in /usr
so the above sentence disallows NFS-mounted /usr. is it really okay
to do?
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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 mounts.
I think this need to be done before nfs mount, because nfs
might also use IPv6 in the future.
- awk and sed are in /usr
so the above sentence disallows NFS-mounted /usr. is it really okay
to do?
Wmmm, on the first place, all of gifconfig, rtadvd, route6d,
pim6dd, pim6sd, are already under /usr
This issue need to be resolved, but I think it can't be done
before 4.0. Maybe this become a known problem for 4.0?,
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
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 "!defined(_ANSI_SOURCE)" section. Anyway, the names should be FOO_MAX, not MAX_FOO. In C99, there are about 50 *_MAX and *_MIN values defined in stdint.h for Standard C types alone. I would prefer standard maxof() and minof() interfaces that work on any arithmetic type. These can almost be written in portable C, at least in C89 where types are restricted to char, signed char, ..., long double: #define isfloat(type) ((type)0.5 != 0) #define issigned(type) ((type)-1 0) #define isschar(type) (!isfloat(type) issigned(type) sizeof(type) == 1) #define isuchar(type) (!isfloat(type) !issigned(type) sizeof(type) == 1) ... #define maxof(type) ((type)(isschar(type) ? SCHAR_MAX : isuchar(type) ? UCHAR_MAX ...)) Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: riscom/8
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 -r1.27 isa_compat.h
*** isa_compat.h2000/02/28 07:52:22 1.27
--- isa_compat.h2000/03/13 06:30:25
***
*** 176,180
{ INTR_TYPE_TTY, labpcdriver },
#endif
! #if NRCD 0
{ INTR_TYPE_TTY, rcdriver },
#endif
--- 176,180
{ INTR_TYPE_TTY, labpcdriver },
#endif
! #if NRC 0
{ INTR_TYPE_TTY, rcdriver },
#endif
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
"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 problem with the current GTK version and X4. Try starting xfce with "--no-xshm" and/or "--no-shm" and see if the problem clears up. Unfortunately those options aren't available, either at run time or compile time AFAICS. I'm in no hurry to migrate to X4 though, so I don't really mind. I've heard enough people give good reports about it that I thought it was worth a try, but I can wait. Thanks, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols in libc_r broken?
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 cvs -q up -D 1/27/2000 make all install the susp.c code from the AW Ptheads Programming book (http://www.aw.com/cseng/titles/0-201-63392-2/code/) would then work with compiled with "-static -pthread". Your analysis if what is currently happening is correct. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: riscom/8
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
*** isa_compat.h 2000/02/28 07:52:22 1.27
--- isa_compat.h 2000/03/13 06:30:25
***
*** 176,180
{ INTR_TYPE_TTY, labpcdriver },
#endif
! #if NRCD 0
{ INTR_TYPE_TTY, rcdriver },
#endif
--- 176,180
{ INTR_TYPE_TTY, labpcdriver },
#endif
! #if NRC 0
{ INTR_TYPE_TTY, rcdriver },
#endif
Bruce
yes!
rc0 at port 0x220-0x22e irq 12 on isa0
rc0: 8 chans, firmware rev. C
rc0: driver is using old-style compatability shims
randy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols in libc_r broken?
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 one takes a fresh -CURRENT and then: cd /usr/src/lib/libc_r cvs -q up -D 1/27/2000 make all install the susp.c code from the AW Ptheads Programming book (http://www.aw.com/cseng/titles/0-201-63392-2/code/) would then work with compiled with "-static -pthread". I don't think it is the linker's fault. To me it makes no sense to have a weak symbol and a strong symbol of the same name in the same library. I deleted the weak definitions in the _THREAD_SAFE PRSYSCALL in lib/libc/i386/SYS.h and the problem goes away. I don't understand why Jason needed to add them in the first place. -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DOS Install Problem
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 switching to the second vty it says that the last operation performed was the creation of /etc/fstab. I'm not sure whether this is an installation problem or whether im doing something wrong? Thanks, Ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unexplained network outages
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 automatic media detection stuff on one of those cards would get confused if the hub the card was plugged into went away for a few seconds. The card would switch to the AUI or coax port and then get stuck that was. You had to up and down the interface to fix it. This problem is seemingly due to the disign of the media detection on the cards, so similar trouble may still exist with some cards? You could try hard wiring the media type and see if that makes a difference. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
some error got from make release this afternoon..
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 -L. -lindep -lgc -lm -lncurses ./mktable 100 tagtable.tab tagtable.c cc -O -pipe -I/usr/local/include -I. -c tagtable.c tagtable.c:8: syntax error before character 0340 tagtable.c:11: syntax error before character 0320 tagtable.c:11: warning: initialization makes integer from pointer without a cast tagtable.c:17: syntax error before character 0370 tagtable.c:17: warning: initialization makes integer from pointer without a cast tagtable.c:22: syntax error before character 0220 tagtable.c:22: warning: initialization makes integer from pointer without a cast tagtable.c:24: `tfoot' undeclared here (not in a function) tagtable.c:24: syntax error before `x' tagtable.c:24: warning: initialization makes integer from pointer without a cast tagtable.c:30: `HTML_N_COLGcolgroup' undeclared here (not in a function) tagtable.c:30: initializer element is not constant tagtable.c:30: (near initialization for `MyHashItem[25].value') tagtable.c:41: syntax error before `,' tagtable.c:41: warning: initialization makes integer from pointer without a cast tagtable.c:45: syntax error before character 07 tagtable.c:45: warning: initialization makes integer from pointer without a cast tagtable.c:49: syntax error before character 0200 tagtable.c:49: warning: initialization makes integer from pointer without a cast tagtable.c:55: syntax error before character 07 tagtable.c:56: `HTML_E' undeclared here (not in a function) tagtable.c:56: `tbody' undeclared here (not in a function) tagtable.c:56: syntax error before `HTML_N' tagtable.c:56: warning: initialization makes integer from pointer without a cast tagtable.c:57: syntax error before character 07 tagtable.c:57: warning: initialization makes integer from pointer without a cast tagtable.c:69: `Hthead' undeclared here (not in a function) tagtable.c:69: initializer element is not constant tagtable.c:69: (near initialization for `MyHashItem[64].value') tagtable.c:91: syntax error before character 07 tagtable.c:94: syntax error before character 07 tagtable.c:94: warning: initialization makes integer from pointer without a cast tagtable.c:105: syntax error before character 0270 tagtable.c:106: syntax error before `w' tagtable.c:112: syntax error before character 07 tagtable.c:112: warning: initialization makes integer from pointer without a cast tagtable.c:118: syntax error before character 0250 tagtable.c:118: warning: initialization makes integer from pointer without a cast *** Error code 1 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /mnt/ad5s1e/FreeBSD-CURRENT/src/release. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NODESCRYPTLINKS=true doesn't work
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 /etc/make.conf, "make buildworld", "make installworld", and couldn't log in anymore because the symlinks had been set to libscrypt (and I'm using DES passwords). I guess that's not how it's supposed to work, is it? Regards Oliver PS: Apart from that, all is working well. I had to compile the system without openssh, though. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: some error got from make release this afternoon..
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 - 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 -L. -lindep -lgc -lm -lncurses ./mktable 100 tagtable.tab tagtable.c cc -O -pipe -I/usr/local/include -I. -c tagtable.c tagtable.c:8: syntax error before character 0340 tagtable.c:11: syntax error before character 0320 tagtable.c:11: warning: initialization makes integer from pointer without a cast tagtable.c:17: syntax error before character 0370 tagtable.c:17: warning: initialization makes integer from pointer without a cast tagtable.c:22: syntax error before character 0220 tagtable.c:22: warning: initialization makes integer from pointer without a cast tagtable.c:24: `tfoot' undeclared here (not in a function) tagtable.c:24: syntax error before `x' tagtable.c:24: warning: initialization makes integer from pointer without a cast tagtable.c:30: `HTML_N_COLGcolgroup' undeclared here (not in a function) tagtable.c:30: initializer element is not constant tagtable.c:30: (near initialization for `MyHashItem[25].value') tagtable.c:41: syntax error before `,' tagtable.c:41: warning: initialization makes integer from pointer without a cast tagtable.c:45: syntax error before character 07 tagtable.c:45: warning: initialization makes integer from pointer without a cast tagtable.c:49: syntax error before character 0200 tagtable.c:49: warning: initialization makes integer from pointer without a cast tagtable.c:55: syntax error before character 07 tagtable.c:56: `HTML_E' undeclared here (not in a function) tagtable.c:56: `tbody' undeclared here (not in a function) tagtable.c:56: syntax error before `HTML_N' tagtable.c:56: warning: initialization makes integer from pointer without a cast tagtable.c:57: syntax error before character 07 tagtable.c:57: warning: initialization makes integer from pointer without a cast tagtable.c:69: `Hthead' undeclared here (not in a function) tagtable.c:69: initializer element is not constant tagtable.c:69: (near initialization for `MyHashItem[64].value') tagtable.c:91: syntax error before character 07 tagtable.c:94: syntax error before character 07 tagtable.c:94: warning: initialization makes integer from pointer without a cast tagtable.c:105: syntax error before character 0270 tagtable.c:106: syntax error before `w' tagtable.c:112: syntax error before character 07 tagtable.c:112: warning: initialization makes integer from pointer without a cast tagtable.c:118: syntax error before character 0250 tagtable.c:118: warning: initialization makes integer from pointer without a cast *** Error code 1 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m/work/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/www/w3m. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/ports/textproc/docproj. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /mnt/ad5s1e/FreeBSD-CURRENT/src/release. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libXThrStub.so.6 and FAQ/handbook
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 into /stand/sysinstall 3 times and watched it download. There is a difference when I type "df", and I have tried a "locate handbook" or "locate faq", "locate FAQ", but they don't show anywhere. The /usr/share/doc directory is there and has other directories, but not these 2. I even looked on / for them. Has anybody else had this problem? Mike __ OS of CHOICE? FreeBSD, LINUX (Debian), OS/2 Warp34, Amiga 500/4000 __ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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 addr is 240:113:130:083, then I think it will be, 2002:f071:8253: (Now I am comfirming a new rc.conf entry which automate above IPv6 prefix calucuration, and etc, for 6to4 interface configuration.) Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
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 interface configuration.) Nice. You have been doing a great job. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current and ep driver : sloooow !
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 transmitted, 147 packets received, 51% packet loss round-trip min/avg/max/stddev = 4044.251/60604.022/101000.012/26950.039 ms Here are the relevant lines of /sbin/dmesg : ep0: 3Com 3C509-TPO EtherLink III at port 0x300-0x30f irq 11 on isa0 ep0: Ethernet address 00:20:af:c4:92:fc Here are the lines from /sbin/ifconfig ep0 ep0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 ether 00:20:af:c4:92:fc media: 10baseT/UTP supported media: 10baseT/UTP and here is the netstat -rn command : Routing tables Internet: DestinationGatewayFlags Netif Expire default212.27.50.254 UGSc tun0 127.0.0.1 127.0.0.1 UH lo0 192.168.2 link#1 UC ep0 = 192.168.2.100 0:80:c8:bc:91:94 UHLWep0626 212.27.50.254 212.27.51.46 UH tun0 Under 3.4-Stable, all was ok, and my laptop (with a NE2K compatible PCMCIA card) works fine with others networks at work. My kernel config file only contains the line device ep I wonder why this happens. Any idea ? -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
riscom/8
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 uucp dialer 63, 129 Mar 12 11:18 /dev/cuam1 crw-rw 1 uucp dialer 63, 130 Mar 12 11:18 /dev/cuam2 crw-rw 1 uucp dialer 63, 131 Mar 12 11:18 /dev/cuam3 crw-rw 1 uucp dialer 63, 132 Mar 12 11:18 /dev/cuam4 crw-rw 1 uucp dialer 63, 133 Mar 12 11:18 /dev/cuam5 crw-rw 1 uucp dialer 63, 134 Mar 12 11:18 /dev/cuam6 crw-rw 1 uucp dialer 63, 135 Mar 12 11:18 /dev/cuam7 crw--- 1 root wheel63, 0 Mar 12 11:18 /dev/ttym0 crw--- 1 root wheel63, 1 Mar 12 11:18 /dev/ttym1 crw--- 1 root wheel63, 2 Mar 12 11:18 /dev/ttym2 crw--- 1 root wheel63, 3 Mar 12 11:18 /dev/ttym3 crw--- 1 root wheel63, 4 Mar 12 11:18 /dev/ttym4 crw--- 1 root wheel63, 5 Mar 12 11:18 /dev/ttym5 crw--- 1 root wheel63, 6 Mar 12 11:18 /dev/ttym6 crw--- 1 root wheel63, 7 Mar 12 11:18 /dev/ttym7 but nothing in dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Mar 12 11:17:35 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/PSG Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 501138467 Hz CPU: Pentium III/Pentium III Xeon (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 134205440 (131060K bytes) avail memory = 127356928 (124372K bytes) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 4.2 irq 10 chip1: Intel 82371AB Power management controller port 0xe800-0xe80f at device 4.3 on pci0 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xd000-0xd0ff mem 0xe200-0xe2000fff irq 10 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xb800-0xb81f mem 0xe180-0xe18f,0xe300-0xe3000fff irq 11 at device 7.0 on pci0 fxp0: Ethernet address 00:e0:18:98:63:22 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 34837MB Maxtor 93652U8 [70780/16/63] at ata0-master using UDMA33 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DNES-309170W S80K Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Buffer troubles, and machine hangs?
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 space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available I have actually been fighting a problem with this machine locking up, and requiring a hard reset, and this is the only type errors I am actually seeing in the messages file. Not sure if this can cause such problems, so kind of grasping at straws to try and correct it. FYI, the IRC machine supports 4000+ clients connected at the same time, so if anyone has recommended tunables for this type of setup with so many active connections I would love to hear about it.. --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
