Re: cvs commit: src/share/mk sys.mk
On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: At 20 Feb 2001 07:54:22 GMT, Kris Kennaway wrote: No, MACHINE_CPU is optional. If you don't have it set, you get the vanilla C code. So if you don't have it set at all, you'll get C code in OpenSSL as it's always been, then the next time you are using the updated make(1) and it will set it to i386, which will get you the i386 asm code. Or you can just set MACHINE_CPU immediately and it will build asm code on the first pass. I don't know this is local problem on my environment, but "make buildworld" with old make(1) failed if I did not set MACHINE_CPU in /etc/make.conf. So it seems invoked make(1) in src/secure/lib/libcrypto is old one... Oh, hmm. It seems we do need the bootstrapping code in sys.mk after all. Kris PGP signature
Re: Do we need a 3. level between stable and cuurent?
On Mon, Feb 19, 2001 at 10:30:17AM -0800, Alfred Perlstein wrote: * Leif Neland [EMAIL PROTECTED] [010219 08:54] wrote: We all know: -current is bleeding edge, expect it to break at random. Don't run it if you don't know how to fix it. -stable is for production, it works all the time. Do we need a level in between for people who just run current for the fun of it and for testing. So after the hardcore has tested it in -current, they commit it to all the monkeys trying to break it, and we then try it on n^m' combinations of hardware/software. I might not be able to fix a problem, but I can report what happens, and if my -current breaks for a few days, it is no big deal. While -current is not for everybody, I believe people like me helps in quality testing before the stuff hits -stable. Perhaps not a level, just a separate file, which contained the date of the last known version without known major problems. (or "." if no known problems) This is a good idea, however it would take someone dedicated to maintaining this as well as doing regression testing. Those regression tests could easily be ported to -stable making for happier -stable as well as -current users. Are you volunteering? :) IMHO, people who are not actively developing -CURRENT, those running it for fun or only occasionally hacking non-essential portions just need to realize that blindly tracking -CURRENT with a daily, weekly, or perhaps any regular make-world schedule is just not going to work. Find a reasonably stable version of -CURRENT and stick with it until you know that the current -CURRENT is also in decent shape. For example, I did a make world early in February and started getting kernel panics at boot. I tried to get some help and provide some data on freebsd-current to fix it, but I just did not have the time and tools. I ended up just CVSuping a back to a version I knew was in good shape and the box has been fine. I can use it for what I want, and I'm not upping it until I hear things have settled a bit... And I hope that's soon, I don't want it to diverge too much or else merging my changes in might get painful. What would help me and others like me is some way to actually figure out if the current -CURRENT is stable (I like that sentence). I am not saying it would be a substitute for freebsd-current and the commit list, but those can be very, very hard to follow. Rather than two versions of -CURRENT provide the data for people to fairly quickly determine if today's -CURRENT is solid enough for them. In some sense, each commit makes a new version, people need to decide up to what recent earth-shaking commit they can go to and be safe. Possibly some webpage summarizing what is broken, which essential pieces are in active development, etc. Obviously, this would take effort, but it may be worth it to those who want to track a stable -CURRENT. It is definately less work than maintaining two versions. How does it differ than reading the mailing lists? You don't need to dig through a dozen me-toos for each problem. Someone more knowledgeble on things can filter the claims that -CURRENT is broken from people who can't read UPDATING. And so on. And no, I am not volunteering. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/mk sys.mk
On Tue, 20 Feb 2001, Kris Kennaway wrote: On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: I don't know this is local problem on my environment, but "make buildworld" with old make(1) failed if I did not set MACHINE_CPU in /etc/make.conf. So it seems invoked make(1) in src/secure/lib/libcrypto is old one... Oh, hmm. It seems we do need the bootstrapping code in sys.mk after all. No. We must fix whatever cause the wrong (old) version of make to be used. I think it is just that make doesn't actually get bootstrapped unless the old make is _very_ old (older than the one in 2.2.0). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/mk sys.mk
On Tue, Feb 20, 2001 at 07:48:31PM +1100, Bruce Evans wrote: On Tue, 20 Feb 2001, Kris Kennaway wrote: On Tue, Feb 20, 2001 at 05:14:57PM +0900, Jun Kuriyama wrote: I don't know this is local problem on my environment, but "make buildworld" with old make(1) failed if I did not set MACHINE_CPU in /etc/make.conf. So it seems invoked make(1) in src/secure/lib/libcrypto is old one... Oh, hmm. It seems we do need the bootstrapping code in sys.mk after all. No. We must fix whatever cause the wrong (old) version of make to be used. I think it is just that make doesn't actually get bootstrapped unless the old make is _very_ old (older than the one in 2.2.0). That would be better -- I checked and we don't appear to rebuild make at all as part of the bootstrap process in make world. We can remove the sys.mk hacks once that works. Kris PGP signature
make buildkernel failed
Hi, I could make buildworld and installworld sucessfully but "make buildkernel" fails. (kernel is built but no modules could be compiled). CVSUP a few minutes ago. === 3dfx make: don't know how to make machine/lock.h. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/SMP. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Building procedure of krb5 is broken
Sorry if you have seen before.
I've found that current 5-current is broken, since krb5 cannot compile.
Here is a typical compiler message:
In file included from
/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5_locl.h:142,
from
/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/gssapi_locl.h:39,
from
/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/8003.c:34:
/usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43:krb5_err.h:
No such file or directory
It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to
src/kerberos5/lib/libgssapi/Makefile is required to fix this, since
krb5_err.h is not in ${KRB5DIR}/lib/krb5.
Any Kerberos5 gurus, would you please check this out?
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make buildkernel failed
Give it about an hour and re-cvsup. Once you have rev 1.94 of src/sys/conf/kmod.mk, you should be set. Or you can grab the delta by cvsweb if you are in a hurry. Jean Louis Ntakpe wrote: Hi, I could make buildworld and installworld sucessfully but "make buildkernel" fails. (kernel is built but no modules could be compiled). CVSUP a few minutes ago. === 3dfx make: don't know how to make machine/lock.h. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/SMP. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proper kernel config procedure ...
Matthew Jacob [EMAIL PROTECTED] writes: This doesn't work 100%. In particular if you have a sys that's not part of /usr/src/sys it doesn't always work. Yes, it does, if your sys tree is complete. There used to be a problem building modules, but it was fixed a month or two ago. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI-RPC and NFS6 status (100% done)
Hi,
I have finished now my work here with TI-RPC, and I'm only doing
bug-fixing now before this gets comitted.
I'd like that many people test these changes and send me bugreports
back. This is a port from NetBSD, and as in NetBSD, it uses Unix Domain
Sockets instead of TLI/XLI stuff. I'v taken the credential checking stuff
from our previous RPC implementation, thanks to Bill Paul for the work he
has done there.
There are still some little things to do in future:
- Fix manpages
- Fix 'bind to ip' for nfsd which is broken at the moment
- Upgrade locking stuff in rpc.library to latest version (ti-rpc2.3)
Here are the patches:
http://home.teleport.ch/freebsd/rpc.diff_02202001.tgz
http://home.teleport.ch/freebsd/before-patch.sh
To patch the CURRENT source-tree and to install these changes, do the
following steps:
1. cd /usr/src
2. run ./before-patch.sh
3. patch -I -E -p rpc.diff_02202001
4. make world
5. Run mergemaster
With these patches applied, all rpc dependent programms in FreeBSD still
work and compile, nfsd(8) and mountd(8) and the mount utilities
(mount_nfs, umount, prc.umntall) have been patched to support IPv6, and
I'm using here NFS over UDP6 on localhost sucessfully.
This is an output of rpcinfo(8), which also has been updated:
# rpcinfo
program version netid addressserviceowner
104tcp 0.0.0.0.0.111 rpcbindsuperuser
103tcp 0.0.0.0.0.111 rpcbindsuperuser
102tcp 0.0.0.0.0.111 rpcbindsuperuser
104udp 0.0.0.0.0.111 rpcbindsuperuser
103udp 0.0.0.0.0.111 rpcbindsuperuser
102udp 0.0.0.0.0.111 rpcbindsuperuser
104tcp6 ::.0.111 rpcbindsuperuser
103tcp6 ::.0.111 rpcbindsuperuser
104udp6 ::.0.111 rpcbindsuperuser
103udp6 ::.0.111 rpcbindsuperuser
104unix /var/run/rpcbind.sock rpcbindsuperuser
103unix /var/run/rpcbind.sock rpcbindsuperuser
102unix /var/run/rpcbind.sock rpcbindsuperuser
151udp 0.0.0.0.3.252 mountd superuser
153udp 0.0.0.0.3.252 mountd superuser
151tcp 0.0.0.0.3.254 mountd superuser
153tcp 0.0.0.0.3.254 mountd superuser
151udp6 ::.3.251 mountd superuser
153udp6 ::.3.251 mountd superuser
151tcp6 ::.3.253 mountd superuser
153tcp6 ::.3.253 mountd superuser
132udp 0.0.0.0.8.1nfssuperuser
133udp 0.0.0.0.8.1nfssuperuser
132udp6 ::.8.1 nfssuperuser
133udp6 ::.8.1 nfssuperuser
And I can do:
# mount -v ::1:/usr/ports/ /mnt
::1:/usr/ports on /mnt (nfs)
# ls -l /mnt
total 1353
-rw-r--r--1 root wheel 19 Jul 14 1997 .cvsignore
drwxr-xr-x2 root wheel 512 Dec 25 1999 CVS
[...]
# umount -v ::1:/usr/ports/
::1:/usr/ports: unmount from /mnt
Now to the other changes which are included in this patch:
- Portmapper(8) has been replaced by the son of portmap, rpcbind.
- There is also a fix included for ypbind, to not to sent 1ends of
requests out, if the yp-server is away for a little time.
- Umount(8) is also fixed to unmount pathnames longer than 80 chars, which
are currently truncated by the Kernel statfs structure.
- In rc.network, all rpc dependent programms and servers are only started
if ${portmap_enable} is set to "YES". In defaults/rc.conf there are some
comments about this. This should prevent some hangs for rpc dependent
programms (rpc.umntall, nfsd, ypbind etc.)
- Because I was to lazy to fix our rpc.lockd(8), I've included the working
NetBSD rpc.lockd(8) implementation, wich uses TI-RPC and works fine for
server side locking, client side locking is not implemented yet.
Im doing some patch splits now, so all necessary parts will hopefully
be commited by Alfred Perlstein in the next few days.
Martin
Martin Blapp, [EMAIL PROTECTED]
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +41 79 370 26 05, Fax: +41 61 826 93 01
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: name resolution problems
On 19 Feb, Wesley Morgan wrote: Since the big shake-up with -current, I find that mozilla and galeon can no longer function (both up to date), but lynx has no problems. Mozilla [...] Is anyone else seeing this? Yes (galeon-0.9b3 + mozilla-0.7). Netscape 4.76 works. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
as segfaulting during world-build
No, I don't think it is hardware. It died on the same spot for the third time in a row: tail -15 /var/tmp/w.log* == /var/tmp/w.log == cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error == /var/tmp/w.log.11 == cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error == /var/tmp/w.log.11-2 == cd /opt/src/lib/csu/i386-elf; make _EXTRADEPEND cc -O -pipe -march=i686 -elf -Wall -fkeep-inline-functions -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crti.S -o crti.o cc -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -c /opt/src/lib/csu/i386-elf/crtn.S -o crtn.o cc: Internal compiler error: program as got fatal signal 11 cc: Internal compiler error: program as got fatal signal 11 *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error This is my regular home machine, it usually runs SETI@Home, when I'm not here and is a NON-overclocked dual Pentium-II 300MHz. It has 320Mb of RAM and 390Mb of swap: Device 1K-blocks UsedAvail Capacity Type /dev/rda0b 393088 36 393052 0%Interleaved I tried building the elf/as manually, and it chokes on this file just the same. Here are my attempts to issue the same commands make and cc issue: # /usr/libexec/cpp0 -lang-asm -v -I/opt/src/lib/csu/i386-elf/../common -I/usr/obj/opt/src/i386/usr/include -$ -Di386 -Dunix -D__FreeBSD__=5 -D__FreeBSD_cc_version=52 -D__i386__ -D__unix__ -D__FreeBSD__=5 -D__FreeBSD_cc_version=52 -D__i386 -D__unix '-Acpu(i386)' '-Amachine(i386)' '-Asystem(unix)' '-Asystem(FreeBSD)' -D__ASSEMBLER__ '-Acpu(i386)' '-Amachine(i386)' -Di386 -D__i386 -D__i386__ -D__ELF__ /opt/src/lib/csu/i386-elf/crtn.S crtn.s # wc -l crtn.s 33 crtn.s # /usr/libexec/elf/as -v -o crtn.o crtn.s GNU assembler version 2.10.1 (i386-unknown-freebsdelf5.0) using BFD version 2.10.1 Segmentation fault - core dumped The crtn.s is rather simple: -- # 1 "/opt/src/lib/csu/i386-elf/crtn.S" [ empty lines ] .section .init,"ax",@progbits ret .section .fini,"ax",@progbits ret -- Yours, -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: as segfaulting during world-build
On Tue, Feb 20, 2001 at 11:27:17AM -0500, Mikhail Teterin wrote: No, I don't think it is hardware. It died on the same spot for the third time in a row: ... What date is the -CURRENT you are attempting the build on from? There were problems with as failing for a while not long ago. Check your version of src/lib/libc/stdio/findfp.c (the installed one...) to see if it is revision 1.15 or later. If not, you will have to get a working as (and as reported by Martin Blapp, the other binutiles in /usr/bin/ and /usr/libexec/elf too) from somwhere like an ftp snapshot... if this is not the problem, I dunno, I did not have any such problems even though I have just finished a buildworld... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic in irq14: ata0
Maxim Sobolev wrote: Soren Schmidt wrote: It seems Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] Hi, I'm not sure whether it's related to ata driver, but starting from several days ago (my previous kernel was from 30 January) my kernel panices on every more or less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it perfectly). The system in question is Toshiba Satellite Pro 445CDX with isa-based ATA controller. Following is relevant dmesg, kernel config and backtrace of crash dump. Try to go back to -current from about feb. 8 or there abouts... Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. Kabaev). Just to let you know that the problem in question is still here (r1.17 of ithread.c). -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic in irq14: ata0
It seems Maxim Sobolev wrote: Soren Schmidt wrote: It seems Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] Hi, I'm not sure whether it's related to ata driver, but starting from several days ago (my previous kernel was from 30 January) my kernel panices on every more or less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it perfectly). The system in question is Toshiba Satellite Pro 445CDX with isa-based ATA controller. Following is relevant dmesg, kernel config and backtrace of crash dump. Try to go back to -current from about feb. 8 or there abouts... Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. Kabaev). Just to let you know that the problem in question is still here (r1.17 of ithread.c). Well, I cant reproduce this problem and I havn't heard from others with this problem -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic in irq14: ata0
Soren Schmidt wrote: It seems Maxim Sobolev wrote: Soren Schmidt wrote: It seems Maxim Sobolev wrote: [Charset koi8-r unsupported, filtering to ASCII...] Hi, I'm not sure whether it's related to ata driver, but starting from several days ago (my previous kernel was from 30 January) my kernel panices on every more or less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it perfectly). The system in question is Toshiba Satellite Pro 445CDX with isa-based ATA controller. Following is relevant dmesg, kernel config and backtrace of crash dump. Try to go back to -current from about feb. 8 or there abouts... Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N. Kabaev). Just to let you know that the problem in question is still here (r1.17 of ithread.c). Well, I cant reproduce this problem and I havn't heard from others with this problem It's not an ata specific problem, but rather a problem of all ISA devices (I have an ISA based ata controller). -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic in irq14: ata0
It seems Maxim Sobolev wrote: Well, I cant reproduce this problem and I havn't heard from others with this problem It's not an ata specific problem, but rather a problem of all ISA devices (I have an ISA based ata controller). Well, seems -current is broken in yet another way -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic in irq14: ata0
Maxim Sobolev [EMAIL PROTECTED] writes: It's not an ata specific problem, but rather a problem of all ISA devices (I have an ISA based ata controller). I don't think it has anything to do with ISA. I've had similar problems on a PCI-only system (actually, PCI+EISA motherboard with no EISA cards) with no ATA devices (disks, CD-ROM and streamer are all SCSI). Considering that backing out rev 1.14 of ithread.c eliminates the panics, and that that revision is supposed to enable interrupt thread preemption, and that the crashed kernels show signs of stack smashing, I'd say the cause is probably a bug in the preemption code. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI-RPC and NFS6 status (100% done)
Hi, I've found some inconsistency in my CVS tree, and sbin/mountd/mountd.c was not the version it should have been. That's fixed now and world just finished on my box sucessfully. Thanks to Ruslan (new man-pages are included in second patch today). Location is still the same, I've just updated the patch to include the changes. http://home.teleport.ch/freebsd/rpc.diff_02202001-1.tgz Thanks to everybody who sent me email about bugs or just comments. Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildkernel failed
In message [EMAIL PROTECTED] Peter Wemm writes: : Give it about an hour and re-cvsup. Once you have rev 1.94 of : src/sys/conf/kmod.mk, you should be set. Or you can grab the delta by : cvsweb if you are in a hurry. find . -name .depend -delete also works. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -stable build of kernel fails
Sorry, my bad. I forgot an #include. In sys/netinet/ip_fw.c add this #include: @@ -48,6 +47,7 @@ #include net/route.h #include netinet/in.h #include netinet/in_systm.h +#include netinet/in_var.h #include netinet/in_pcb.h #include netinet/ip.h #include netinet/ip_var.h I have committed it. Poul-Henning In message [EMAIL PROTECTED], Kenneth Wayne Culver writes: With the recent commits to -STABLE (I'm assuming these are MFC that's why I sent to both freebsd-current and freebsd-stable) having to do with the ipfw code, I have had a problem compiling the kernel. These are the errors. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel ip_fw.o: In function `ip_fw_chk': ip_fw.o(.text+0xff7): undefined reference to `INADDR_TO_IFP' ip_fw.o(.text+0x1017): undefined reference to `INADDR_TO_IFP' *** Error code 1 Before anyone asks, I did a make depend first, and I used config -r instead of config when config'ing my kernel. Did I miss a message or something saying that I need something new in my kernel for firewalls? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: updating from 12/25/1999 -current?
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Feb 19, 2001 at 01:19:13AM -0800, Herman Tan wrote: Greetings everyone: Will I run into any problems doing a make world from a 12/25/1999 version of -CURRENT to the latest -current? I noticed on -RELEASE machines when I went from 3.3-R to 4.1-R, I had problems because the loaded kernel doesn't have the modules and I had to use the Generic kernel in 4.1R and reboot the machine. Any suggestions? Thanks. It can probably be done, perhaps with a bit of hoop-jumping (see /usr/src/UPDATING), but you may find a binary upgrade to be easier. Kris Wouldn't there be a problem after the world build since the currently loaded kernel won't support certain calls and there would be no way out? I know a binary upgrade would work but it would mess up the /etc directory which I plan to update manually... HT __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vinum fix take 2
Now that I've broken all you non-devfs users of vinum, I have a patch that may get it working again. Please let me know if: http://people.freebsd.org/~alfred/vinum2.diff (you'll need to be -current as of today) works, otherwise I'll be committing tonight or tomorrow as this patch _still_ works for my config. thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
* Akinori MUSHA [EMAIL PROTECTED] [010220 11:19] wrote: Hi, I have implemented -regex and -iregex options for find(1): Sounds good, just make sure the regex engine matches the one that the other find(1)'s use. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
At Wed, 21 Feb 2001 08:42:19 +1300,
Craig Carey wrote:
What about the -iname option?.
I recently installed GNU 'find' just to get that -iname problem fixed.
Can you do -iname too?.
Thanks for the info. It's added now.
I'm ashamed to say that I couldn't resist implementing -E option to
allow extended regexps. ;) The traditional and POSIX compliant basic
regexp is so hard to handle that you can't even say ".+\.S?o" but
"..*\.S{0,1}o".. (see re_format(7) for details)
Also, I revised the manpage to describe them in detail. Please check
it out:
http://people.FreeBSD.org/~knu/misc/find_regex.diff
I'd like to commit it after reviews if there is no convincing
objection against it. Any suggestion is welcome.
I would object if it is a new variant of regexp. I'd say it ought
be between egrep and perl, in its functionality.
I don't think I grasp your meaning.. GNU find(1)'s -regexp uses the
"basic regexp" that is _not_ the "extended regexp" which egrep(1) uses
nor the one perl(1) uses.
Anyway, here lists the facts:
- I implemented -regexp/-iregexp using FreeBSD's standard regex
library which is supposed to be compliant with POSIX.2
- The match is executed with REG_BASIC, which behavior is compatible
with GNU find(1) and NetBSD find(1)
- I, however, added -E so we can use extended regexp ;)
- Perl's regexp is known to be a unique variant that is different
from the "basic regexp" nor the "extended regexp" ;P
It sounds like a regexp would be nice.
Me too. :)
--
/
/__ __Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"We're only at home when we're on the run, on the wing, on the fly"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: proper kernel config procedure ...
On 20 Feb 2001, Dag-Erling Smorgrav wrote: Matthew Jacob [EMAIL PROTECTED] writes: This doesn't work 100%. In particular if you have a sys that's not part of /usr/src/sys it doesn't always work. Yes, it does, if your sys tree is complete. There used to be a problem building modules, but it was fixed a month or two ago. No, make clean doesn't work 100% always. I don't remember the details, but indeed it still was a problem. I sent mail to David Peter after this happened (because they both had last been involved) and never heard back. Oh, wait- Peter muttered something about module To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Slightly OT: XMMS on -CURRENT?
Hi all, Does anybody run xmms on -CURRENT? For some reason it hungs here on "poll". Any other (multithread included) program runs flawlessly. The only possibility I can see right now is plugin system (i.e. dl* functions) but there haven't been eny changes in ld-elf.so.1 as of lately. I'm really puzzled :-( Any clues? "uname -a" output: FreeBSD kushnir1.kiev.ua 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 18 09:50:07 EET 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KUSHNIR i386 -- ===|=== Vladimir Kushnir | [EMAIL PROTECTED] |Powered by FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What goes at the boot prompt
I have a kernel that hangs at boot, so when I try to boot kernel.old, I have a problem. At the Default: F1 prompt, I give it an F1 and then the space key give me FreeBSD/i386 BOOT Default: 0:wd(o,a)/boot/loader boot: _ What do I put at the boot prompt. I think the changes of the last few days have left me a little punchy. I thought that I always put kernel.old or /boot/kernel.old. I appologize for such a dumb question. I did check the boot manual and it says: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: bios_drive:interface(unit,part) filename [-aCcDdghPrsv] filename The pathname of the file to boot (relative to the root directory on the specified partition). Defaults to /kernel. Symbolic links are not supported (hard links are). I still don't get it. TIA, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
find(1) -regex/-iregex
Hi, I have implemented -regex and -iregex options for find(1): http://people.FreeBSD.org/~knu/misc/find_regex.diff They are meant to be compatible with those of GNU's and NetBSD's: -regex pattern: True if the whole path of the file matches pattern using basic regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. -iregex pattern: Like -regex, but the match is case insensitive. I'd like to commit it after reviews if there is no convincing objection against it. Any suggestion is welcome. Thanks, -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest alpha breakage
Matthew Jacob writes: === libcrypto ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) buildinf.h make: don't know how to make bn-alpha.pl. Stop *** Error code 2 This looks like the libcrypto breakage that I was complainging about. I thought this was fixed last night -- have you cvsup'ed recently? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
Akinori MUSHA wrote: Hi, I have implemented -regex and -iregex options for find(1): http://people.FreeBSD.org/~knu/misc/find_regex.diff I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. They are meant to be compatible with those of GNU's and NetBSD's: -regex pattern: True if the whole path of the file matches pattern using basic regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. -iregex pattern: Like -regex, but the match is case insensitive. You forgot -E (use extended regexp syntax), and the example you show above is extended regexp syntax, not basic regexp syntax. I'd like to commit it after reviews if there is no convincing objection against it. Any suggestion is welcome. Well, I expressed my concerns above. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
Alfred Perlstein wrote: * Akinori MUSHA [EMAIL PROTECTED] [010220 11:19] wrote: Hi, I have implemented -regex and -iregex options for find(1): Sounds good, just make sure the regex engine matches the one that the other find(1)'s use. It won't. GNU find certainly uses GNU regexp library, which has lots of extra stuff. Naturally, our find will be using our library instead. shrug Nothing we can do about it. It is the way of the Gnu to extend and embrace. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
Akinori MUSHA wrote: I would object if it is a new variant of regexp. I'd say it ought be between egrep and perl, in its functionality. ... - Perl's regexp is known to be a unique variant that is different from the "basic regexp" nor the "extended regexp" ;P For that matter, anyone talking about "standard" regexp of any kind I invite to take a look at the include file for gnu regexp, to see just how many slightly different variants of regexp there are out there in various utilities. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What goes at the boot prompt
Edwin Culp wrote: I have a kernel that hangs at boot, so when I try to boot kernel.old, I have a problem. At the Default: F1 prompt, I give it an F1 and then the space key give me FreeBSD/i386 BOOT Default: 0:wd(o,a)/boot/loader boot: _ What do I put at the boot prompt. I think the changes of the last few days have left me a little punchy. I thought that I always put kernel.old or /boot/kernel.old. On -current, /boot/kernel.old is a directory containing both kernel and modules. /boot/kernel.old/kernel would do, but why skip the loader phase? Let loader proceed, interrupt the ten second count and then type: boot kernel.old (or boot-conf kernel.old, if you are using loader to get some modules loaded) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-stable build of kernel fails
With the recent commits to -STABLE (I'm assuming these are MFC that's why I sent to both freebsd-current and freebsd-stable) having to do with the ipfw code, I have had a problem compiling the kernel. These are the errors. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel ip_fw.o: In function `ip_fw_chk': ip_fw.o(.text+0xff7): undefined reference to `INADDR_TO_IFP' ip_fw.o(.text+0x1017): undefined reference to `INADDR_TO_IFP' *** Error code 1 Before anyone asks, I did a make depend first, and I used config -r instead of config when config'ing my kernel. Did I miss a message or something saying that I need something new in my kernel for firewalls? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
At Wed, 21 Feb 2001 12:35:09 +0900, Daniel C. Sobral wrote: I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. Indeed. I'll do it soon, thanks. You forgot -E (use extended regexp syntax), and the example you show above is extended regexp syntax, not basic regexp syntax. Noted. -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What goes at the boot prompt
On Tue, Feb 20, 2001 at 04:14:02PM -0800, Edwin Culp wrote: I still don't get it. Should you really be running -current? This kind of support question isn't appropriate for this list, IMO. Kris PGP signature
latest alpha breakage
=== libcrypto ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) buildinf.h make: don't know how to make bn-alpha.pl. Stop *** Error code 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
At Wed, 21 Feb 2001 14:12:51 +0900, I wrote: At Wed, 21 Feb 2001 12:35:09 +0900, Daniel C. Sobral wrote: I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. Indeed. I'll do it soon, thanks. Updated. http://people.FreeBSD.org/~knu/misc/find_regex.diff You forgot -E (use extended regexp syntax), and the example you show above is extended regexp syntax, not basic regexp syntax. Well, it was added after I had posted the original article. The latest one's find.1 mentions it. .It Fl E Interpret regular expressions followed by .Ic -regex and .Ic -iregex options as extended (modern) regular expressions rather than basic regular expressions (BRE's). The .Xr re_format 7 manual page fully describes both formats. As for the syntax my examples conform to, I think they are valid both for basic and extended. True if the whole path of the file matches .Ar pattern using regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. Thanks for your suggestions. -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
Can an -iname option be provided. Then the FreeBSD find would be more like GNU find, and lines like this could be written: find /msdos-disk -iname "*txt" | xargs -n 1 ls -l I am doubtful that the -regexp needs to be inferior to the the -egrep option. What software would break: it was said that there is no regexp?. There are opinions around saying that egrep is better than grep. What is the -E option: perhaps this?: -eregex Suppose it is case sensitive. Then it could be -eiregex or -ieregex or -eregexi I hope for no regex if there is no '-iname' feature. [It would be nice if the advanced regexes settled onto the Perl regex, e.g. perhaps throughout all utilities. -pregex ] At 21-02-01 14:12 +0900 Wednesday, Akinori MUSHA wrote: At Wed, 21 Feb 2001 12:35:09 +0900, Daniel C. Sobral wrote: I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. Indeed. I'll do it soon, thanks. You forgot -E (use extended regexp syntax), and the example you show above is extended regexp syntax, not basic regexp syntax. Noted. ... What about improving 'ls' too?: can there be an option so that it refuses to list any information about directories (useful in the above example). Also, is there any plan to stop the wastage of space in the central columns of "ls"'s output, where it lists uninteresting information. Maybe a '-p' option, like GNU 'ls' has. E-mail: Craig Carey [EMAIL PROTECTED] (backup [EMAIL PROTECTED]) Auckland, NZ. | Snooz Metasearch: http://www.ijs.co.nz/info/snooz.htm To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
Akinori MUSHA wrote: I'm not familiar with find sources, but it seems to me you execute regcomp() for each file name to be compared? If so... change that! :-) Regcomp() does expensive setup so that regexec() can be run inexpensively many times over. Indeed. I'll do it soon, thanks. Updated. http://people.FreeBSD.org/~knu/misc/find_regex.diff You might have done it, but the version above is not it. :-) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Too bad sentience isn't a marketable commodity." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
At Wed, 21 Feb 2001 18:53:26 +1300, Craig Carey wrote: Can an -iname option be provided. Then the FreeBSD find would be more like GNU find, and lines like this could be written: Yes, it's already implemented as I wrote in the previous mail. I am doubtful that the -regexp needs to be inferior to the the -egrep option. What software would break: it was said that there is no regexp?. There are opinions around saying that egrep is better than grep. We are not aiming to be that GNU'ish. Being compatible with NetBSD is a good thing in a sense. What is the -E option: perhaps this?: -eregex Suppose it is case sensitive. Then it could be -eiregex or -ieregex or -eregexi I don't like it somehow.. I chose -E because it is consistent with (our) grep(1) and sed(1). What about improving 'ls' too?: can there be an option so that it refuses to list any information about directories (useful in the above example). Also, is there any plan to stop the wastage of space in the central columns of "ls"'s output, where it lists uninteresting information. Maybe a '-p' option, like GNU 'ls' has. Interesting, but it would be done at some other time. I'd like to focus on regex this time. -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: find(1) -regex/-iregex
At Wed, 21 Feb 2001 15:06:22 +0900, Daniel C. Sobral wrote: http://people.FreeBSD.org/~knu/misc/find_regex.diff You might have done it, but the version above is not it. :-) Oh, would you please reload it? When you see a function named do_c_regex(), that's it. :) -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
