Build breakage (was: fail to compile kernel...)
Warner Losh writes: In message [EMAIL PROTECTED] Mike Meyer writes: : The nasty downside of the the module system is that people who don't : adequately test module code before checking it in will screw up kernel : builds for kernels that don't need that code. But I did test it. But I had an uncommitted file on my machine... Won't the 'cvs diff' command tell you about such things? If not, that's yet another argument for ditching cvs in favor of something without so many flaws (like Perforce). : Since you probably don't need the oldcard module. Just comment it out : of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want : to comment out pccard as well. Or you can just update your sources. There was a 8 hour window where this was broken... Well, it was still broken as of about 30 minutes before he asked the question. I'd look at it for trivial fixes, then just quit trying to build it because I wasn't going to need it. I didn't mean to finger you particularly. It's just a bit upsetting to realize that I can't remember the last time I managed to do an update to -current without some kind of breakage. I realize that -current isn't guaranteed to build, but that's a bit ridiculous. I mean - I was pleasantly surprised that I could build the world first time out. To find the kernel breaking for a module that I have no absolutely no use for on this machine was a bit upsetting. I'm beginning to wonder if I shouldn't use -stable as a buffer, and just let the committers deals with things not being up to -current. Or maybe check to see if the other *BSD's aren't a bit more demanding of committers. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
strange freeze while starting kde2 :(
While starting kde2 beta my pc freezes and i have to push power off button. After reboot i hade to run fsck, because of "strange inconsistency". Some files(created by kde startup) were broken and contain corrupted data. Kernel doesn't panic, it just freezes. How can i examine this situation more detailed? Can anybody help? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
In message [EMAIL PROTECTED] Mike Meyer writes: : Warner Losh writes: : In message [EMAIL PROTECTED] Mike Meyer writes: : : The nasty downside of the the module system is that people who don't : : adequately test module code before checking it in will screw up kernel : : builds for kernels that don't need that code. : But I did test it. But I had an uncommitted file on my machine... : : Won't the 'cvs diff' command tell you about such things? If not, : that's yet another argument for ditching cvs in favor of something : without so many flaws (like Perforce). Not when the files are in multiple different directories and you have mutliple patches cooking in your tree. I committed files in sys/pccard, but they depended on one in sys/dev/pccard which I honestly thought I'd checked in with an earlier newcard fix. I'd been running the patches long enough that I basically forgot. This was clearly my fault. : : Since you probably don't need the oldcard module. Just comment it out : : of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want : : to comment out pccard as well. : Or you can just update your sources. There was a 8 hour window where : this was broken... : : Well, it was still broken as of about 30 minutes before he asked the : question. I'd look at it for trivial fixes, then just quit trying to : build it because I wasn't going to need it. No. It is not still broken. I committed a fix for this a while ago (like Friday Morning after breaking it late Thursday night) and have done a buildworld and a kernel build on a different machine since then on fresher sources. If it truely is still broken, I need to know what you did. In fact, I did an cvsup and a cvs update and was able to build a kernel and modules w/o any problems on my -current box. : I didn't mean to finger you particularly. It's just a bit upsetting to : realize that I can't remember the last time I managed to do an update : to -current without some kind of breakage. I realize that -current : isn't guaranteed to build, but that's a bit ridiculous. I mean - I was : pleasantly surprised that I could build the world first time out. To : find the kernel breaking for a module that I have no absolutely no use : for on this machine was a bit upsetting. Well, that's the break's of -current. sometimes things are broken. Sometimes when you update, you get burned. Usually it just works. : I'm beginning to wonder if I shouldn't use -stable as a buffer, and : just let the committers deals with things not being up to -current. Or : maybe check to see if the other *BSD's aren't a bit more demanding of : committers. I know that you are frustrated, but I think that's unfair. You'll likely find that the other BSD's are just as bad at times as we get around here. At least that's my firsthand experience with them as a committer. There was a period of about 6 months that every time I went to upgrade the OpenBSD/arc installed on my Deskstation rPC44, someone had broken something and I had to fix it before it would compile. If you aren't a developer or have another compelling reason to track -current, track -stable. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
I didn't mean to finger you particularly. It's just a bit upsetting to realize that I can't remember the last time I managed to do an update to -current without some kind of breakage. I realize that -current isn't guaranteed to build, but that's a bit ridiculous. I mean - I was pleasantly surprised that I could build the world first time out. To find the kernel breaking for a module that I have no absolutely no use for on this machine was a bit upsetting. I'm beginning to wonder if I shouldn't use -stable as a buffer, and just let the committers deals with things not being up to -current. Or maybe check to see if the other *BSD's aren't a bit more demanding of committers. What if the machine building snapshots took a note of the time it cvsup'ped. Then if the build succeded, it would append this date to a file. We could then feed this date to our cvsup, to get a version which at least compiled. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
I'm seeing a small problem with up to the minute sources in the install phase: === usr.sbin/sendmail install -c -o root -g wheel -m 644 /dev/null /var/log/sendmail.st install -c -o root -g wheel -m 444 /usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/helpfile /etc/mail/helpfile install -c -s -o root -g wheel -m 4555 sendmail /usr/libexec/sendmail install -c -o root -g wheel -m 444 mailq.1.gz newaliases.1.gz /usr/share/man/man1 install -c -o root -g wheel -m 444 aliases.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 sendmail.8.gz /usr/share/man/man8 + cp /etc/aliases /etc/mail/aliases cp: not found *** Error code 127 Stop in /usr/src/usr.sbin/sendmail. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 1 error /etc/aliases and /etc/mail both exist. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sat, Aug 12, 2000 at 04:02:03PM -0700, Gregory Neil Shapiro wrote: hetzels Sendmail 8.11 has the ablity to due secure authentication with hetzels mail clients when compiled with Cyrus-SASL. hetzels Will the Cyrus-SASL library be imported to provide this hetzels capability? Or at least a make.conf variable. My first step in the process was to get sendmail up-to-date. Once it is MFC'ed to STABLE, I'll look at enhancements. After September 21, I want to turn on STARTTLS support. I'm not sure about importing SASL -- I might be convinced to put in Makefile support if it happens to already been installed via ports. Getting STARTTLS also means putting sfio into base. Also it would be fine if the hashed ca-cert links are created: bash-2.03# ls -al /etc/ssl/certs total 42 drwxr-xr-x 2 root wheel 1024 Jun 24 11:30 . drwxr-xr-x 4 root wheel 1024 Jun 24 11:21 .. lrwxr-xr-x 1 root wheel 9 Jun 24 11:26 052eae11.0 - tjhCA.pem lrwxr-xr-x 1 root wheel10 Jun 24 11:26 13810d42.0 - cacert.pem lrwxr-xr-x 1 root wheel12 Jun 24 11:26 18d46017.0 - vsigntca.pem lrwxr-xr-x 1 root wheel12 Jun 24 11:26 1ef89214.0 - nortelCA.pem lrwxr-xr-x 1 root wheel11 Jun 24 11:26 1f6c59cd.0 - ca-cert.pem lrwxr-xr-x 1 root wheel11 Jun 24 11:26 24867d38.0 - dsa-pca.pem lrwxr-xr-x 1 root wheel10 Jun 24 11:26 2edf7016.0 - vsign1.pem lrwxr-xr-x 1 root wheel12 Jun 24 11:26 3ecf89a3.0 - ICE-user.pem lrwxr-xr-x 1 root wheel10 Jun 24 11:26 6bee6be3.0 - ICE-CA.pem lrwxr-xr-x 1 root wheel10 Jun 24 11:26 73912336.0 - dsa-ca.pem lrwxr-xr-x 1 root wheel10 Jun 24 11:26 7651b327.0 - vsign3.pem lrwxr-xr-x 1 root wheel 9 Jun 24 11:26 8c401b31.0 - timCA.pem lrwxr-xr-x 1 root wheel12 Jun 24 11:26 8caad35e.0 - pca-cert.pem -rw-r--r-- 1 root wheel 2945 Jun 2 00:05 ICE-CA.pem -rw-r--r-- 1 root wheel 2314 Jun 2 00:05 ICE-root.pem -rw-r--r-- 1 root wheel 3240 Jun 2 00:05 ICE-user.pem [...] -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
On Sun, Aug 13, 2000 at 01:14:09AM -0600, Warner Losh wrote: : Won't the 'cvs diff' command tell you about such things? If not, : that's yet another argument for ditching cvs in favor of something : without so many flaws (like Perforce). Not when the files are in multiple different directories and you have mutliple patches cooking in your tree. I committed files in sys/pccard, but they depended on one in sys/dev/pccard which I honestly thought I'd checked in with an earlier newcard fix. I'd been running the patches long enough that I basically forgot. Which is why I keep a virgin src checkout and I CVSup (with "-i") right after large commit and try building the code again in the virgin tree. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fail to compile kernel...
On Sat, 12 Aug 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Idea Receiver writes: : i have try to upgrade one of my 4.1 release to -current. : however, when i try to build the kernel, it failed as following : message. Upgrade your sources and try again. Warner cvsed this morning (8 hrs ago..) and still doesnt work.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
Warner Losh writes: In message [EMAIL PROTECTED] Mike Meyer writes: : Warner Losh writes: : In message [EMAIL PROTECTED] Mike Meyer writes: : : The nasty downside of the the module system is that people who don't : : adequately test module code before checking it in will screw up kernel : : builds for kernels that don't need that code. : But I did test it. But I had an uncommitted file on my machine... : Won't the 'cvs diff' command tell you about such things? If not, : that's yet another argument for ditching cvs in favor of something : without so many flaws (like Perforce). Not when the files are in multiple different directories and you have mutliple patches cooking in your tree. I committed files in sys/pccard, but they depended on one in sys/dev/pccard which I honestly thought I'd checked in with an earlier newcard fix. I'd been running the patches long enough that I basically forgot. This was clearly my fault. Hmm - you mean 'cvs diff' can't be pointed at sys to get a list of everything you've touched? : : Since you probably don't need the oldcard module. Just comment it out : : of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want : : to comment out pccard as well. : Or you can just update your sources. There was a 8 hour window where : this was broken... : Well, it was still broken as of about 30 minutes before he asked the : question. I'd look at it for trivial fixes, then just quit trying to : build it because I wasn't going to need it. No. It is not still broken. I committed a fix for this a while ago (like Friday Morning after breaking it late Thursday night) and have done a buildworld and a kernel build on a different machine since then on fresher sources. If it truely is still broken, I need to know what you did. I just now grabbed the latest sources, and got the following: cc -O -pipe -march=pentium -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/oldcard/../../pccard/pccard.c cc -O -pipe -march=pentium -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/oldcard/../../pccard/pcic.c /usr/src/sys/modules/oldcard/../../pccard/pcic.c:1020: `card_get_memory_offset_desc' undeclared here (not in a function) /usr/src/sys/modules/oldcard/../../pccard/pcic.c:1020: initializer element is not constant /usr/src/sys/modules/oldcard/../../pccard/pcic.c:1020: (near initialization for `pcic_methods[16].desc') *** Error code 1 Stop in /usr/src/sys/modules/oldcard. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/EVE. In fact, I did an cvsup and a cvs update and was able to build a kernel and modules w/o any problems on my -current box. : I didn't mean to finger you particularly. It's just a bit upsetting to : realize that I can't remember the last time I managed to do an update : to -current without some kind of breakage. I realize that -current : isn't guaranteed to build, but that's a bit ridiculous. I mean - I was : pleasantly surprised that I could build the world first time out. To : find the kernel breaking for a module that I have no absolutely no use : for on this machine was a bit upsetting. Well, that's the break's of -current. sometimes things are broken. Sometimes when you update, you get burned. Usually it just works. If it usually "just worked", it wouldn't be a problem. I expected to have systems that would at times be a bit delicate for a time, or require old kernels, or the like. What I *didn't* expect was that the usual update procedure would be get new sources, watch the build fail, fix it if possible, or post a note to -current and repeat the process when someone claimed it was fixed. : I'm beginning to wonder if I shouldn't use -stable as a buffer, and : just let the committers deals with things not being up to -current. Or : maybe check to see if the other *BSD's aren't a bit more demanding of : committers. I know that you are frustrated, but I think that's unfair. You'll likely find that the other BSD's are just as bad at times as we get around here. At least that's my firsthand experience with them as a committer. There was a period of about 6 months that every time I went to upgrade the OpenBSD/arc installed on my Deskstation rPC44, someone had broken something and I had to fix it before it would compile. That may be true - which would mean it wouldn't be any better than FreeBSD has been for the past few months. Or any worse. On the other hand, breaking the build on other projects I've worked on was considered
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
ticso Getting STARTTLS also means putting sfio into base. Actually, it wouldn't. I was able to get Torek I/O working with STARTTLS as an FFR. I'm running with STARTTLS at home without using sfio. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
DougB I'm seeing a small problem with up to the minute sources in the install DougB phase: DougB + cp /etc/aliases /etc/mail/aliases DougB cp: not found DougB *** Error code 127 That is odd considering the step right before it uses 'mv' which is located in /bin/ (where 'cp' also lives). I assumed that if mv worked, cp would as well. In any case, that step was a hack for the short term until I could make arrangements to get src/etc/aliases moved to src/etc/mail/aliases by the CVS managers. This has now been done and I've removed the hack so things should return to normal again. Thanks for the report. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup overzealous
In article [EMAIL PROTECTED], Brian Somers [EMAIL PROTECTED] writes With world and kernel of 10th August, 01:00 GMT cvsup is reporting 'SetAttrs' adjustments for every file it encounters on repeated runs against a server that has not been updated. Running under an old kernel, cvsup is not performing any updates. This isn't by any chance because you cvsup'd from my laptop is it ? I chmod my repository with g+w, so if you sup from me, then from a real machine you get shed-loads of setattrs No, that was my first thought :) I'm used to that behaviour when I sup from 'hak', but I have not, in fact, sup'd 'lapbsd' from it since before July 16. I noticed this when 'lapbsd' was suping of 'shrewd' repeatedly (by mistake actually), where 'shrewd' had not sup'd off 'storm' itself. As I say, it's behaving under a new world. -- Mark Knight PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with ATAPI CD driver
It seems Donn Miller wrote: I've got a BTC 24x ATAPI CDROM driver, and I can't mount it. Attached is my dmesg.out. Typing mount /cdrom causes the mount command to hang, and it never did this before. Also, I'm getting these strange syslog messages. (See attached file messages.out.) I tried disabling DMA for ATAPI devices in my kernel config file to no avail. Seems I didnt' get enough sleep for that last commit, try it now after the latest fix (atapi-cd.c r1.62)... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with ATAPI CD driver
Soren Schmidt wrote: It seems Donn Miller wrote: I've got a BTC 24x ATAPI CDROM driver, and I can't mount it. Attached is my dmesg.out. Typing mount /cdrom causes the mount command to hang, and it never did this before. Also, I'm getting these strange syslog messages. (See attached file messages.out.) I tried disabling DMA for ATAPI devices in my kernel config file to no avail. Seems I didnt' get enough sleep for that last commit, try it now after the latest fix (atapi-cd.c r1.62)... Works OK now. Thanks. -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun, 13 Aug 2000, Gregory Neil Shapiro wrote:
DougB I'm seeing a small problem with up to the minute sources in the install
DougB phase:
DougB + cp /etc/aliases /etc/mail/aliases
DougB cp: not found
DougB *** Error code 127
That is odd considering the step right before it uses 'mv' which is located
in /bin/ (where 'cp' also lives). I assumed that if mv worked, cp would as
well.
This is because /bin is not in $PATH at install time. `mv' is actually
located in ${TMPDIR}/install.$$. `cp' is not there, although `cp' is
used to put `mv' there, since it would be a bug to use `cp' instead of
${INSTALL} to install things after `install' is bootstrapped.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sat, 12 Aug 2000 15:40:24 -0700 (PDT) Gregory Neil Shapiro [EMAIL PROTECTED] said: gshapiro sendmail has been updated from 8.9.3 to 8.11.0. Some of the more visible gshapiro changes that may immediately affect your configuration include: gshapiro - New default file locations from src/contrib/sendmail/cf/README gshapiro - newaliases limited to root and trusted users gshapiro - MSA port (587) turned on by default gshapiro - New queue file naming system so can't go from 8.11 - 8.9 gshapiro - mail.local FreeBSD-only -b option changed to -B gshapiro - FEATURE(`rbl') renamed to FEATURE(`dnsbl') gshapiro - FEATURE(`nullclient') is more full featured gshapiro - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' gshapiro - See src/contrib/sendmail/RELEASE_NOTES for more info Beacuse default confCW_FILE doesn't have -o option, freebsd.mc should have "define(`confCW_FILE', `-o /etc/mail/local-host-names)dnl" line. Unless this, /etc/mail/local-host-names will be mandatory. BTW, I love to see DAEMON_OPTIONS(`Name=MTA-v4, Family=inet')dnl DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')dnl lines. But, I know this requires IPv6 enabled kernel and to do this is difficult. NetBSD ships two version of sendmail.cf. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
In message [EMAIL PROTECTED] "David O'Brien" writes: : On Sun, Aug 13, 2000 at 01:14:09AM -0600, Warner Losh wrote: : : Won't the 'cvs diff' command tell you about such things? If not, : : that's yet another argument for ditching cvs in favor of something : : without so many flaws (like Perforce). : : Not when the files are in multiple different directories and you have : mutliple patches cooking in your tree. I committed files in : sys/pccard, but they depended on one in sys/dev/pccard which I : honestly thought I'd checked in with an earlier newcard fix. I'd been : running the patches long enough that I basically forgot. : : Which is why I keep a virgin src checkout and I CVSup (with "-i") right : after large commit and try building the code again in the virgin tree. Makes sense for a large commit. I try to do that after most big commits myself, or when things aren't inside the kernel. In this case, however, it wouldn't have saved much time. I made the commit and went to bed. The buildworld on the clean tree wouldn't have been ready for two hours and I was fast asleep by then. When I woke up, I had messages telling me of my mistake and fixed it then. If I had done a buildworld on a fresh tree, then I'd have done the same thing when I discovered it had failed in the morning... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fail to compile kernel...
In message [EMAIL PROTECTED] Idea Receiver writes: : In message [EMAIL PROTECTED] Idea :Receiver writes: : : i have try to upgrade one of my 4.1 release to -current. : : however, when i try to build the kernel, it failed as following : : message. : : Upgrade your sources and try again. : : Warner : : cvsed this morning (8 hrs ago..) : and still doesnt work.. Where did you get your sources? As of 12:00 last night, the sources I grabbed from cvsup8 completed both a make buildworld and make buildkernel in a fresh tree. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount_hpfs not built by default
On Sat, 12 Aug 2000, Alexander Langer wrote: Hello! In PR docs/20369 it was mentioned that mount_hpfs isn't built by default. Am I missing something? Why not? From the cvs-logs, it seems, it has just been forgotten :) However, I'm asking because maybe I missed a discussion back in December. I think there are too few people who really use HPFS. So it doesn't worth. Also, i'm not sure it's working at all. Sorry. I don't have HPFS partitions any more, so i even can't verify if it works. Bye. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
In message [EMAIL PROTECTED] Mike Meyer writes: : Hmm - you mean 'cvs diff' can't be pointed at sys to get a list of : everything you've touched? No, I mean that I have NEWCARD changes as well, that usually never get touched. And it is sometimes easy to get things confused. : I just now grabbed the latest sources, and got the following: Where did you get them? Before I sent the last mail message out I built the kernel on a fresh tree and kicked off a world build (which finished). : If it usually "just worked", it wouldn't be a problem. I expected to : have systems that would at times be a bit delicate for a time, or : require old kernels, or the like. What I *didn't* expect was that the : usual update procedure would be get new sources, watch the build fail, : fix it if possible, or post a note to -current and repeat the process : when someone claimed it was fixed. So we're down to stale sources at one of the mirrors, I think. My kernel tree here is completely clean and checked out from the my local cvs tree. Where do you get your sources from? What revision of src/sys/dev/pccard/card_if.m do you have? The following changed fixes it: revision 1.7 date: 2000/08/11 15:51:51; author: imp; state: Exp; lines: +8 -1 Define get_memory_offset method Which is Friday Morning MST (the time is GMT). Plenty of time for the mirrors to be updated. : That may be true - which would mean it wouldn't be any better than : FreeBSD has been for the past few months. Or any worse. On the other : hand, breaking the build on other projects I've worked on was : considered a major blunder. That doesn't seem to be the case here. That is the case here. Believe me. But sitting around pointing fingers after the problem has been fixed is usually not done. : If you aren't a developer or have another compelling reason to track : -current, track -stable. : : Well, I was hoping to chase out the last of the bugs in the usb modem : driver, and possibly try and recover some of the functionality lost : when the snd drivers quit working. But the latest version of the : former isn't in the tree yet, and new sound cards are cheaper than the : time to work on the latter (if only the documentation on pcm did and : didn't support were accurate). That was the justification for my : converting to -current in the first place. I figured I'd track : -current to make the lifes of the people actually committing the code : easier, but that seems sort of pointless. That's a compelling reason. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
In message 06e001c004fa$39e94d60$[EMAIL PROTECTED] "Leif Neland" writes: : What if the machine building snapshots took a note of the time it cvsup'ped. : Then if the build succeded, it would append this date to a file. : We could then feed this date to our cvsup, to get a version which at least : compiled. Preliminary inidications are that this is a mirroring problem. If the last date mechanism was independent of the mirroring process, then the problem would still persist because the date given would be after the breakage. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
At 01:49 PM 8/13/00 +0200, Johan Granlund wrote: I think we have to support rfc2554 autenthication (With MECH LOGIN for Outlook) out of the box if we are serius about mailserver and security. If you're serious about security, you shouldn't support LOGIN (or PLAIN) unless adequate privacy protections are in place. If you're serious about standards, you won't support LOGIN. Given that OpenSSL is in the base system, there is little reason not to support BOTH StartTLS and SASL "out of the box". I would suggest the authentication defaults be relative secure, as in "noplain,noanonymous". This will force use of StartTLS to allow use of PLAIN/LOGIN mechanisms. A make.conf knob to use a userinstalled library may create problems with different versions of Cysus-SASL. I had some problems with that when uppgrading my mailservers to Sendmail 8.10. I'd recommend bringing Cyrus-SASL into the base system eventually under the same rational used to bring OpenSSL in. Kurt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun, 13 Aug 2000 09:20:05 -0700 "Kurt D. Zeilenga" [EMAIL PROTECTED] said: Kurt At 01:49 PM 8/13/00 +0200, Johan Granlund wrote: I think we have to support rfc2554 autenthication (With MECH LOGIN for Outlook) out of the box if we are serius about mailserver and security. Kurt If you're serious about security, you shouldn't support LOGIN (or PLAIN) Kurt unless adequate privacy protections are in place. If you're serious Kurt about standards, you won't support LOGIN. I think so. Further worse, once PLAIN is activated by sendmail, netscape try to use AUTH, in anyway. If the user isn't registered in SASL db, the user cannot send mail anymore. That is, once you decide to use PLAIN, you must register all of your users in SASL db. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun 2000-08-13 (09:20), Kurt D. Zeilenga wrote: A make.conf knob to use a userinstalled library may create problems with different versions of Cysus-SASL. I had some problems with that when uppgrading my mailservers to Sendmail 8.10. I'd recommend bringing Cyrus-SASL into the base system eventually under the same rational used to bring OpenSSL in. What are the license issues on this? Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun, 13 Aug 2000, Kurt D. Zeilenga wrote: At 01:49 PM 8/13/00 +0200, Johan Granlund wrote: I think we have to support rfc2554 autenthication (With MECH LOGIN for Outlook) out of the box if we are serius about mailserver and security. If you're serious about security, you shouldn't support LOGIN (or PLAIN) unless adequate privacy protections are in place. If you're serious about standards, you won't support LOGIN. Tell that to Microsoft! They only support LOGIN and the users (god bless them) won't change to another client. Given that OpenSSL is in the base system, there is little reason not to support BOTH StartTLS and SASL "out of the box". I would suggest the authentication defaults be relative secure, as in "noplain,noanonymous". This will force use of StartTLS to allow use of PLAIN/LOGIN mechanisms. Works for me. I _have_ to keep OE5 working somehow until they start supporting a better mechanism, _Then_ i can ditch LOGIN. A make.conf knob to use a userinstalled library may create problems with different versions of Cysus-SASL. I had some problems with that when uppgrading my mailservers to Sendmail 8.10. I'd recommend bringing Cyrus-SASL into the base system eventually under the same rational used to bring OpenSSL in. I agree. /Johan Kurt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
BTW, I love to see DAEMON_OPTIONS(`Name=MTA-v4, Family=inet')dnl DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')dnl Yes that together with "CFLAGS+=-DNETINET6" in the sendmail/Makefile and I have a working ipv6 mailer going. There is just an annoying message because of the anycast address: Aug 13 16:38:47 angel sendmail[11947]: gethostbyaddr(3ffe:2900:fffa:4::) failed: 1 Is that because of a configuration error or just because sendmail needs to check for anycast addresses? The machine is also a router between a gif tunnel and this interface. My interface is configured like this: angel# ifconfig de0 de0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 146.64.84.9 netmask 0xff00 broadcast 146.64.84.255 inet6 fe80::200:e8ff:fe15:dbed%de0 prefixlen 64 scopeid 0x1 inet6 3ffe:2900:fffa:4:200:e8ff:fe15:dbed prefixlen 64 inet6 3ffe:2900:fffa:4:: prefixlen 64 anycast ether 00:00:e8:15:db:ed media: 10baseT/UTP status: active supported media: 100baseTX full-duplex 100baseTX 10base2/BNC 10baseT/UTP full-duplex 10baseT/UTP John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
In article [EMAIL PROTECTED], Mike Meyer [EMAIL PROTECTED] wrote: Won't the 'cvs diff' command tell you about such things? No, but "cvs -nq update" will, and it's a lot faster too. 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: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun, 13 Aug 2000 19:24:09 +0200 (SAT) John Hay [EMAIL PROTECTED] said: BTW, I love to see DAEMON_OPTIONS(`Name=MTA-v4, Family=inet')dnl DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')dnl jhay Yes that together with "CFLAGS+=-DNETINET6" in the sendmail/Makefile jhay and I have a working ipv6 mailer going. Yeh! I'm looking forward to see it. jhay There is just an annoying message because of the anycast jhay address: jhay Aug 13 16:38:47 angel sendmail[11947]: gethostbyaddr(3ffe:2900:fffa:4::) failed: 1 jhay Is that because of a configuration error or just because sendmail needs jhay to check for anycast addresses? The machine is also a router between a jhay gif tunnel and this interface. My interface is configured like this: jhay angel# ifconfig de0 jhay de0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 jhay inet 146.64.84.9 netmask 0xff00 broadcast 146.64.84.255 jhay inet6 fe80::200:e8ff:fe15:dbed%de0 prefixlen 64 scopeid 0x1 jhay inet6 3ffe:2900:fffa:4:200:e8ff:fe15:dbed prefixlen 64 jhay inet6 3ffe:2900:fffa:4:: prefixlen 64 anycast jhay ether 00:00:e8:15:db:ed jhay media: 10baseT/UTP status: active jhay supported media: 100baseTX full-duplex 100baseTX 10base2/BNC 10baseT/UTP full-duplex 10baseT/UTP I don't see any configuration problem here. As that machine is a router, anycast address has been assigned. (RFC2373) I simply registered PTR RRs of my anycast addresses into DNS. It may be good idea that sendmail checks for anycast address. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun 2000-08-13 (10:48), Kurt D. Zeilenga wrote: At 06:53 PM 8/13/00 +0200, Neil Blakey-Milner wrote: On Sun 2000-08-13 (09:20), Kurt D. Zeilenga wrote: A make.conf knob to use a userinstalled library may create problems with different versions of Cysus-SASL. I had some problems with that when uppgrading my mailservers to Sendmail 8.10. I'd recommend bringing Cyrus-SASL into the base system eventually under the same rational used to bring OpenSSL in. What are the license issues on this? None worse than those associated with OpenSSL. Ah, it seems to be a simplistic BSD-like license. For a second I thought it might be a non-commercial one, like cyrus-imapd has in some areas. OpenSSL is slightly more structured - Apache-like BSD license. So at least there won't be any insane license-wars over it. Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
On Sun, 13 Aug 2000, John Polstra wrote: In article [EMAIL PROTECTED], Mike Meyer [EMAIL PROTECTED] wrote: Won't the 'cvs diff' command tell you about such things? No, but "cvs -nq update" will, and it's a lot faster too. I normally use that, but "cvs status | grep Status" may be better (faster?). "cvs -nq update" is not as good as it used to be. It now prints noise about merging deltas, so I actually normally use "cvs -nq update | grep -v ^M". Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New sendmail: junk characters in header
To see the bug, just send any mail to yourself. Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e7DIV4a34899 for [EMAIL PROTECTED]; Sun, 13 Aug 2000 22:31:04 +0400 (MSD)?g ^ (envelope-from ache) ^^^ -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
ume Beacuse default confCW_FILE doesn't have -o option, freebsd.mc should ume have "define(`confCW_FILE', `-o /etc/mail/local-host-names)dnl" line. ume Unless this, /etc/mail/local-host-names will be mandatory. Good point. I've fixed this. ume BTW, I love to see ume DAEMON_OPTIONS(`Name=MTA-v4, Family=inet')dnl ume DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')dnl ume lines. But, I know this requires IPv6 enabled kernel and to do this ume is difficult. NetBSD ships two version of sendmail.cf. Adding IPv6 support to the sendmail binary is high on my list of things to do. You are correct, configuration support is a more difficult issue. I'm open to suggestions. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount_hpfs not built by default
Thus spake Ustimenko Semen ([EMAIL PROTECTED]): I think there are too few people who really use HPFS. So it That's not a good reason :) I don't have HPFS partitions any more, so i even can't verify if it works. Hmm. One should test it. I can't, unfortunately. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
jhay There is just an annoying message because of the anycast address: jhay Aug 13 16:38:47 angel sendmail[11947]: gethostbyaddr(3ffe:2900:fffa:4::) failed: 1 jhay Is that because of a configuration error or just because sendmail needs jhay to check for anycast addresses? sendmail tries to get the hostnames associated with all of it's interfaces to populate $=w (local host names). The best fix would be to create an entry in DNS for that address. Perhaps sendmail shouldn't bother warning on multicast addresses. Can you see if this patch makes the error go away? Index: conf.c === RCS file: /cvs/sendmail/conf.c,v retrieving revision 8.646.2.2.2.26 diff -u -u -r8.646.2.2.2.26 conf.c --- conf.c 2000/08/12 18:35:38 8.646.2.2.2.26 +++ conf.c 2000/08/13 19:03:51 @@ -5282,7 +5282,8 @@ if (LogLevel 3 #if NETINET6 !(sa-sa.sa_family == AF_INET6 - IN6_IS_ADDR_LINKLOCAL(sa-sin6.sin6_addr)) + (IN6_IS_ADDR_LINKLOCAL(sa-sin6.sin6_addr) || + IN6_IS_ADDR_MULTICAST(sa-sin6.sin6_addr)) #endif /* NETINET6 */ TRUE) sm_syslog(LOG_WARNING, NOQID, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
gshapiro Can you see if this patch makes the error go away? gshapiro Index: conf.c gshapiro === A better patch: Index: conf.c === RCS file: /cvs/sendmail/conf.c,v retrieving revision 8.646.2.2.2.26 diff -u -u -r8.646.2.2.2.26 conf.c --- conf.c 2000/08/12 18:35:38 8.646.2.2.2.26 +++ conf.c 2000/08/13 19:14:14 @@ -5282,7 +5282,8 @@ if (LogLevel 3 #if NETINET6 !(sa-sa.sa_family == AF_INET6 - IN6_IS_ADDR_LINKLOCAL(sa-sin6.sin6_addr)) + (IN6_IS_ADDR_LINKLOCAL(sa-sin6.sin6_addr) || + IN6_IS_ADDR_MULTICAST(sa-sin6.sin6_addr))) #endif /* NETINET6 */ TRUE) sm_syslog(LOG_WARNING, NOQID, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
jhay There is just an annoying message because of the anycast address: jhay Aug 13 16:38:47 angel sendmail[11947]: gethostbyaddr(3ffe:2900:fffa:4::) failed: 1 jhay Is that because of a configuration error or just because sendmail needs jhay to check for anycast addresses? sendmail tries to get the hostnames associated with all of it's interfaces to populate $=w (local host names). The best fix would be to create an entry in DNS for that address. Perhaps sendmail shouldn't bother warning on multicast addresses. Can you see if this patch makes the error go away? I tried your second patch, but it didn't make a difference. I'll take the easy way out for now and add a DNS entry like you and ume suggested. :-) I looked in ifconfig to see how they did the anycast detection and you basically have to open another socket into the kernel (this time an AF_INET6 one) and get the ipv6 flags and check them. Maybe too much work, except if it is going to bother too many people. :-/ John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build breakage (was: fail to compile kernel...)
Warner Losh writes: So we're down to stale sources at one of the mirrors, I think. My kernel tree here is completely clean and checked out from the my local cvs tree. Where do you get your sources from? What revision of src/sys/dev/pccard/card_if.m do you have? The following changed fixes it: revision 1.7 date: 2000/08/11 15:51:51; author: imp; state: Exp; lines: +8 -1 Define get_memory_offset method Which is Friday Morning MST (the time is GMT). Plenty of time for the mirrors to be updated. Yes, the version I have is out of date. It came from cvsup5.freebsd.org over 24 hours after the commit. : That may be true - which would mean it wouldn't be any better than : FreeBSD has been for the past few months. Or any worse. On the other : hand, breaking the build on other projects I've worked on was : considered a major blunder. That doesn't seem to be the case here. That is the case here. Believe me. But sitting around pointing fingers after the problem has been fixed is usually not done. Again, I didn't mean to point fingers or complain about any specific person. I've been sitting on this for most of the last week; your change just happened to be the one that caused the problem this time. Pointing fingers isn't the difference I was talking about. It's more in the attitude after the fact. On FreeBSD, it's "Ok, I fixed it." Elsewhere, people apologize for breaking the bulid. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
On Sun, 13 Aug 2000 21:28:20 +0200 (SAT)
John Hay [EMAIL PROTECTED] said:
jhay There is just an annoying message because of the anycast address:
jhay Aug 13 16:38:47 angel sendmail[11947]: gethostbyaddr(3ffe:2900:fffa:4::)
failed: 1
jhay Is that because of a configuration error or just because sendmail needs
jhay to check for anycast addresses?
sendmail tries to get the hostnames associated with all of it's interfaces
to populate $=w (local host names). The best fix would be to create an
entry in DNS for that address. Perhaps sendmail shouldn't bother warning
on multicast addresses. Can you see if this patch makes the error go away?
jhay I tried your second patch, but it didn't make a difference.
Please try this patch.
Index: sendmail-8.11.0/sendmail/conf.c
diff -u sendmail-8.11.0/sendmail/conf.c.orig sendmail-8.11.0/sendmail/conf.c
--- sendmail-8.11.0/sendmail/conf.c.origSun Jul 16 02:35:18 2000
+++ sendmail-8.11.0/sendmail/conf.c Mon Aug 14 05:34:18 2000
@@ -4771,6 +4771,11 @@
# undef __P
# endif /* (_AIX4 = 40300) !defined(_NET_IF_H) */
# include net/if.h
+#if NETINET6 !defined(SIOCGLIFCONF)
+# include net/if.h
+# include net/if_var.h
+# include netinet/in_var.h
+#endif /* NETINET6 !SIOCGLIFCONF */
#endif /* defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN */
void
@@ -5009,6 +5014,9 @@
# if NETINET6
char *addr;
struct in6_addr ia6;
+#ifdef SIOCGIFAFLAG_IN6
+ struct in6_ifreq ifr6;
+#endif /* SIOCGIFAFLAG_IN6 */
# endif /* NETINET6 */
struct in_addr ia;
# ifdef SIOCGIFFLAGS
@@ -5093,6 +5101,22 @@
addr == NULL ? "(NULL)" : addr);
continue;
}
+
+# ifdef SIOCGIFAFLAG_IN6
+ memset(ifr6, '\0', sizeof(struct in6_ifreq));
+ strncpy(ifr6.ifr_name, ifr-ifr_name,
+ sizeof(ifr-ifr_name));
+ ifr6.ifr_addr = sa-sin6;
+ if (ioctl(s, SIOCGIFAFLAG_IN6, ifr6) 0)
+ {
+ if (tTd(0, 4))
+ dprintf("SIOCGLIFFLAGS failed: %s\n",
+ errstring(errno));
+ continue;
+ }
+ if (ifr6.ifr_ifru.ifru_flags6 IN6_IFF_ANYCAST)
+ continue;
+# endif /* SIOCGIFAFLAG_IN6 */
/* save IP address in text from */
addr = anynet_ntop(ia6, buf6, sizeof buf6);
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current
On Mon, 14 Aug 2000, Hajimu UMEMOTO wrote: On Sun, 13 Aug 2000 09:20:05 -0700 "Kurt D. Zeilenga" [EMAIL PROTECTED] said: Kurt At 01:49 PM 8/13/00 +0200, Johan Granlund wrote: I think we have to support rfc2554 autenthication (With MECH LOGIN for Outlook) out of the box if we are serius about mailserver and security. Kurt If you're serious about security, you shouldn't support LOGIN (or PLAIN) Kurt unless adequate privacy protections are in place. If you're serious Kurt about standards, you won't support LOGIN. I think so. Further worse, once PLAIN is activated by sendmail, netscape try to use AUTH, in anyway. If the user isn't registered in SASL db, the user cannot send mail anymore. That is, once you decide to use PLAIN, you must register all of your users in SASL db. I agree that PLAIN/LOGIN should not be enabled by default as it is inherently insecure and should not be encouraged. It can easyly be enabled in a custom .mc file, if wanted, with define(`confAUTH_MECHANISMS', `')dnl define(`confTRUST_AUTH_MECH', `')dnl The snag is that is has to be enabled in the build of the SASL library. The same with KerberosIV and GSSAPI depending of what is installed. N.B This is for 8.10. I havent looked if it has changed for 8.11. If autentication is enabled with SASL, support should be added to adduser/rmuser, or we will have a supportbomb when locally defined user cant send mail remotely. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ 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: Build breakage (was: fail to compile kernel...)
In message [EMAIL PROTECTED] Mike Meyer writes: : Pointing fingers isn't the difference I was talking about. It's more : in the attitude after the fact. On FreeBSD, it's "Ok, I fixed : it." Elsewhere, people apologize for breaking the bulid. I sent out a message at the time saying I'm sorry for the breakage and I've fixed it. when it came up again, I just said that I;d fixed it. You're right. I shouldn't have sounded so... so... blasse about it. Warner "pass the connical hat" Losh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
ume Please try this patch.
ume Index: sendmail-8.11.0/sendmail/conf.c
ume diff -u sendmail-8.11.0/sendmail/conf.c.orig sendmail-8.11.0/sendmail/conf.c
Oops, previous patch is insufficient. I forgot to open INET6 socket.
Index: sendmail-8.11.0/sendmail/conf.c
diff -u sendmail-8.11.0/sendmail/conf.c.orig sendmail-8.11.0/sendmail/conf.c
--- sendmail-8.11.0/sendmail/conf.c.origSun Jul 16 02:35:18 2000
+++ sendmail-8.11.0/sendmail/conf.c Mon Aug 14 06:52:16 2000
@@ -4771,6 +4771,11 @@
# undef __P
# endif /* (_AIX4 = 40300) !defined(_NET_IF_H) */
# include net/if.h
+#if NETINET6 !defined(SIOCGLIFCONF)
+# include net/if.h
+# include net/if_var.h
+# include netinet/in_var.h
+#endif /* NETINET6 !SIOCGLIFCONF */
#endif /* defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN */
void
@@ -4958,6 +4963,9 @@
#else /* NETINET6 defined(SIOCGLIFCONF) */
# if defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN
int s;
+#if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ int s6;
+#endif /* NETINET6 SIOCGIFAFLAG_IN6 */
int i;
struct ifconf ifc;
int numifs;
@@ -4996,6 +5004,10 @@
return;
}
+#if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ s6 = socket(AF_INET6, SOCK_DGRAM, 0);
+#endif /* NETINET6 SIOCGIFAFLAG_IN6 */
+
/* scan the list of IP address */
if (tTd(0, 40))
dprintf("scanning for interface specific names, ifc_len=%d\n",
@@ -5009,6 +5021,9 @@
# if NETINET6
char *addr;
struct in6_addr ia6;
+#ifdef SIOCGIFAFLAG_IN6
+ struct in6_ifreq ifr6;
+#endif /* SIOCGIFAFLAG_IN6 */
# endif /* NETINET6 */
struct in_addr ia;
# ifdef SIOCGIFFLAGS
@@ -5094,6 +5109,22 @@
continue;
}
+# ifdef SIOCGIFAFLAG_IN6
+ memset(ifr6, '\0', sizeof(struct in6_ifreq));
+ strncpy(ifr6.ifr_name, ifr-ifr_name,
+ sizeof(ifr-ifr_name));
+ ifr6.ifr_addr = sa-sin6;
+ if (s6 0 || ioctl(s6, SIOCGIFAFLAG_IN6, ifr6) 0)
+ {
+ if (tTd(0, 4))
+ dprintf("SIOCGIFAFLAG_IN6 failed: %s\n",
+ errstring(errno));
+ continue;
+ }
+ if (ifr6.ifr_ifru.ifru_flags6 IN6_IFF_ANYCAST)
+ continue;
+# endif /* SIOCGIFAFLAG_IN6 */
+
/* save IP address in text from */
addr = anynet_ntop(ia6, buf6, sizeof buf6);
if (addr != NULL)
@@ -5123,6 +5154,10 @@
}
free(ifc.ifc_buf);
(void) close(s);
+# if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ if (s6 = 0)
+ (void) close(s6);
+# endif /* NETINET6 SIOCGIFAFLAG_IN6 */
# undef IFRFREF
# endif /* defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN */
#endif /* NETINET6 defined(SIOCGLIFCONF) */
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Problems with stable (believed to be in -current as well)
My server functions properly (harddrives inside). My diskless machines (mounting same filesystems via NFS) are having problems. Thanks in advance. bash-2.03$ top top: nlist failed bash-2.03$ vmstat vmstat: undefined symbols: _cp_time _kmemstatistics _bucket _zlist Occurs with both 4.0 and 4.1 (and various in between stages). As a related item, harddrives used in LARGE mode can cause the same problem until changed to LBA. df output - bash-2.03$ df Filesystem 1K-blocks UsedAvail Capacity Mounted on 10.0.0.2:/ 396895 136078 22906637%/ mfs:972943 886 182233%/conf/etc /conf/etc 2943 886 182233%/etc procfs 440 100%/proc mfs:117 1951 123 1672 7%/var mfs:131 1511 50 1341 4%/dev 10.0.0.2:/usr 2977230 1617820 112123259%/usr 10.0.0.2:/devel/archive 14757968 10399126 317820577% /devel/archive 10.0.0.2:/devel/archive2 6216820 5300977 41849893% /devel/archive2 10.0.0.2:/usr/home 7995310 852075 650361112%/usr/home dmesg output Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Mon Aug 7 11:17:37 EDT 2000 [EMAIL PROTECTED]:/devel/archive2/obj/devel/archive2/src/sys/DISKLESS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 268435456 (262144K bytes) avail memory = 258564096 (252504K bytes) K6-family MTRR support enabled (2 registers) md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib2: VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib2 pci1: NVidia Riva TNT2 graphics accelerator at 0.0 irq 11 isab0: VIA 82C586 PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 pci0: NVidia/SGS-Thomson Riva128 graphics accelerator at 9.0 irq 10 pcm0: AudioPCI ES1371 port 0xe800-0xe83f irq 12 at device 10.0 on pci0 xl0: 3Com 3c905-TX Fast Etherlink XL port 0xec00-0xec3f irq 5 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:de:4e:38 miibus0: MII bus on xl0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: Host to PCI bridge on motherboard pci2: PCI bus on pcib1 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,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 bootpc_init: wired to interface 'xl0' bootpc_init: using network interface 'xl0' Bootpc testing starting bootpc hw address is 0:60:97:de:4e:38 My ip address is 10.0.0.185 Server ip address is 10.0.0.2 Gateway ip address is 0.0.0.0 Server name is king.zort.on.ca boot file is /kernel.diskless Subnet mask is 255.0.0.0 Router is 10.0.0.1 Ignoring field type 15 rootfs is 10.0.0.2:/ Ignoring field type 28 Mounting root from nfs: NFS ROOT: 10.0.0.2:/ -- Rod Taylor "People get annoyed when you try to debug them." -- Larry Wall, 2nd State of the Onion. "A + B + C = Success if, A = Hard Work, B = Hard Play, C = Keeping your mouth shut." -- Albert Einstein -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with stable (believed to be in -current as well)
Wesley Morgan wrote: On Sun, 13 Aug 2000, Rod Taylor wrote: My server functions properly (harddrives inside). My diskless machines (mounting same filesystems via NFS) are having problems. Thanks in advance. bash-2.03$ top top: nlist failed If you installed a new kernel and have the original (or close to it) world, make world now. It's a perfectly matched kernel and world. This is what I attempted to show by stating that the diskless box and server run on the same filesystem. One mounted from the other. Server works, diskless boxes don't. (Yes, they've all been rebooted since then). -- Rod Taylor "People get annoyed when you try to debug them." -- Larry Wall, 2nd State of the Onion. "A + B + C = Success if, A = Hard Work, B = Hard Play, C = Keeping your mouth shut." -- Albert Einstein -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with stable (believed to be in -current as well)
Sean O'Connell wrote: Rod Taylor stated: : Wesley Morgan wrote: : : On Sun, 13 Aug 2000, Rod Taylor wrote: : : My server functions properly (harddrives inside). My diskless machines : (mounting same filesystems via NFS) are having problems. Thanks in : advance. : : bash-2.03$ top : top: nlist failed : : : If you installed a new kernel and have the original (or close to : it) world, make world now. : : It's a perfectly matched kernel and world. This is what I attempted to : show by stating that the diskless box and server run on the same : filesystem. One mounted from the other. Server works, diskless boxes : don't. (Yes, they've all been rebooted since then). Is the kernel beining netbooted identical to the one in the exported diskless partition? I would make sure that the kernel image in hte root of the exported filesystem is the same. I can netboot for inst- allation purposes from a floppy. I just have to be careful to keep the same kernel and etc files in sync (I install into a /netboot directory using: setenv DESTDIR /netboot; make installworld ... ). No, they're not identical. However I created it, and moved it to it's proper place. Being as make installkernel KERNEL=FEH seems to ignore the whole: makeoptions KERNEL=kernel.diskless seems to be completely ignored. The other way this problem can occur is if you load your kernel from the boot blocks (??) rather than from /boot/loader. I'm unsure as to how a network boot even considers bootblocks or loaders. It's coming from across the network via etherboot. Although the etherboot client is currently on a floppy on most boxes (Bad EProm burner). -- Rod Taylor "People get annoyed when you try to debug them." -- Larry Wall, 2nd State of the Onion. "A + B + C = Success if, A = Hard Work, B = Hard Play, C = Keeping your mouth shut." -- Albert Einstein -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Slow ssh throughput with -current
On 2000-Aug-10 15:36:01 +1000, Peter Jeremy [EMAIL PROTECTED] wrote: I just noticed a really peculiar network slowdown with -current from about a week ago. The machine has two NICs - an old 16-bit SMC card (ed0) running 10baseT and a PCI SMC card (tx0) running 100baseTX full duplex. When I scp (either ssh-1.2.27 or OpenSSH) to a remote machine via ed0, I get a throughput of ~8KB/sec. When I go via tx0, I get ~3MB/sec (CPU limited). If I use ftp via ed0, I get wire speed (just over 1MB/sec). Having done some more tests, and a bit more digging, I've found the culprit is net.inet.tcp.newreno. When set to 1 (the default), ssh (but not FTP) connections to hosts not on the same subnet (as determined by in_localaddr()) have an effective window size of 1 MSS. Unfortunately, I can't see any obvious reason why initialising maxburst to 4 results in only a single packet on each call to tcp_output() for ssh connections. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sendmail updated from 8.9.3 to 8.11.0 in -current
Yes, this fix it. I don't see the message anymore and it still works too. :-)
Thanks.
John
--
John Hay -- [EMAIL PROTECTED]
ume Please try this patch.
ume Index: sendmail-8.11.0/sendmail/conf.c
ume diff -u sendmail-8.11.0/sendmail/conf.c.orig sendmail-8.11.0/sendmail/conf.c
Oops, previous patch is insufficient. I forgot to open INET6 socket.
Index: sendmail-8.11.0/sendmail/conf.c
diff -u sendmail-8.11.0/sendmail/conf.c.orig sendmail-8.11.0/sendmail/conf.c
--- sendmail-8.11.0/sendmail/conf.c.orig Sun Jul 16 02:35:18 2000
+++ sendmail-8.11.0/sendmail/conf.c Mon Aug 14 06:52:16 2000
@@ -4771,6 +4771,11 @@
# undef __P
# endif /* (_AIX4 = 40300) !defined(_NET_IF_H) */
# include net/if.h
+#if NETINET6 !defined(SIOCGLIFCONF)
+# include net/if.h
+# include net/if_var.h
+# include netinet/in_var.h
+#endif /* NETINET6 !SIOCGLIFCONF */
#endif /* defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN */
void
@@ -4958,6 +4963,9 @@
#else /* NETINET6 defined(SIOCGLIFCONF) */
# if defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN
int s;
+#if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ int s6;
+#endif /* NETINET6 SIOCGIFAFLAG_IN6 */
int i;
struct ifconf ifc;
int numifs;
@@ -4996,6 +5004,10 @@
return;
}
+#if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ s6 = socket(AF_INET6, SOCK_DGRAM, 0);
+#endif /* NETINET6 SIOCGIFAFLAG_IN6 */
+
/* scan the list of IP address */
if (tTd(0, 40))
dprintf("scanning for interface specific names, ifc_len=%d\n",
@@ -5009,6 +5021,9 @@
# if NETINET6
char *addr;
struct in6_addr ia6;
+#ifdef SIOCGIFAFLAG_IN6
+ struct in6_ifreq ifr6;
+#endif /* SIOCGIFAFLAG_IN6 */
# endif /* NETINET6 */
struct in_addr ia;
# ifdef SIOCGIFFLAGS
@@ -5094,6 +5109,22 @@
continue;
}
+# ifdef SIOCGIFAFLAG_IN6
+ memset(ifr6, '\0', sizeof(struct in6_ifreq));
+ strncpy(ifr6.ifr_name, ifr-ifr_name,
+ sizeof(ifr-ifr_name));
+ ifr6.ifr_addr = sa-sin6;
+ if (s6 0 || ioctl(s6, SIOCGIFAFLAG_IN6, ifr6) 0)
+ {
+ if (tTd(0, 4))
+ dprintf("SIOCGIFAFLAG_IN6 failed: %s\n",
+ errstring(errno));
+ continue;
+ }
+ if (ifr6.ifr_ifru.ifru_flags6 IN6_IFF_ANYCAST)
+ continue;
+# endif /* SIOCGIFAFLAG_IN6 */
+
/* save IP address in text from */
addr = anynet_ntop(ia6, buf6, sizeof buf6);
if (addr != NULL)
@@ -5123,6 +5154,10 @@
}
free(ifc.ifc_buf);
(void) close(s);
+# if NETINET6 defined(SIOCGIFAFLAG_IN6)
+ if (s6 = 0)
+ (void) close(s6);
+# endif /* NETINET6 SIOCGIFAFLAG_IN6 */
# undef IFRFREF
# endif /* defined(SIOCGIFCONF) !SIOCGIFCONF_IS_BROKEN */
#endif /* NETINET6 defined(SIOCGLIFCONF) */
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
