Re: make installworld failure in usr.bin/tip
Mark, Poul-Henning, So, what was the concensus? Should we fix this in Makefile, or just put this as an UPDATING entry and have users manually remove the old UUCP stuff? Erm, it _is_ fixed in the makefile. If you have a better method, lets hear it. :-) M On Sat, Nov 03, 2001 at 05:07:01PM +0100, Poul-Henning Kamp wrote: === usr.bin/tip install -c -s -o root -g wheel -m 555 tip /flat/syv/usr/bin /flat/syv/usr/bin/cu - /flat/syv/usr/bin/tip ln: /flat/syv/usr/bin/cu: Operation not permitted *** Error code 1 flat# ls -l /flat/syv/usr/bin/cu -r-sr-sr-x 1 uucp dialer 124384 Oct 21 13:04 /flat/syv/usr/bin/cu flat# /flat/src/usr.bin/tip flat# cvs log Makefile | less [...] total revisions: 10;selected revisions: 10 description: revision 1.7 date: 2001/10/30 21:22:08; author: markm; state: Exp; lines: +1 -1 Make the dirty, rotten hack failsafe and quiet if cu(1) does not exist. I'm sure there is a connection somewhere... -- 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 -- Ruslan ErmilovOracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED]FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.orgThe Power To Serve http://www.oracle.com Enabling The Information Age -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/compat/svr4 svr4_stream.c src/sys/kern kern_descrip.c sys_socket.c uipc_socket.c uipc_socket2.c uipc_syscalls.c uipc_usrreq.c src/sys/net raw_cb.c raw_usrreq.c src/sys/netatalk ddp_usrreq.c src/sys/netatm atm_socket.c ...
In article [EMAIL PROTECTED] Matt Dillon [EMAIL PROTECTED] wrote: dillon 2001/11/16 19:07:12 PST Modified files: sys/compat/svr4 svr4_stream.c sys/kern kern_descrip.c sys_socket.c uipc_socket.c uipc_socket2.c uipc_syscalls.c uipc_usrreq.c sys/net raw_cb.c raw_usrreq.c sys/netatalk ddp_usrreq.c sys/netatm atm_socket.c sys/netinet in_pcb.c sys/netinet6 in6_pcb.c sys/netipx ipx_pcb.c ipx_usrreq.c sys/netnatm natm.c sys/netnsidp_usrreq.c ns_pcb.c sys/nfsservernfs_syscalls.c sys/sys file.h socketvar.h Log: Give struct socket structures a ref counting interface similar to vnodes. This will hopefully serve as a base from which we can expand the MP code. We currently do not attempt to obtain any mutex or SX locks, but the door is open to add them when we nail down exactly how that part of it is going to work. There is at least one more usage of the deleted by this commit 'holdsock' in the sys/compat/linux/linux_socket.c which makes the kernel unbuildable. Unfortunately I can not fix this case mechanically as in many other places where 'holdsock' was used before. N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: building cvsup from ports
John I have a patch (courtesy of Brian Somers) that fixes M3. I believe he has submitted it to you. May I/We commit it? M Hello all, Sounds like a silly place to post this but...here goes. I'm getting errors compiling cvsup from ports. The ports tree installed is the default coming with the 11/12/01 snapshot. I want would use CVS, but I don't know how (and yet I call my self a computer science student). It complains about nfs/nfs.h not existing (I checked, it doesn't). This is the first thing I have built from ports except X in -current, so all of the dependencies besides X were built with this port during make install. I remeber seeing this post on stable a while ago, but can't find the message for the life or me. The error is appended for amusment to those individuals who understand such things. regards, Galen Sampson # cd /usr/ports/net/cvsup # make install To build this port without X11 (and without the GUI), define WITHOUT_X11. === Extracting for cvsup-16.1e Checksum OK for cvsup-snap-16.1e.tar.gz. === cvsup-16.1e depends on file: /usr/local/lib/m3/FreeBSD4/libm3formsvbt.so.7 - not found ===Verifying install for /usr/local/lib/m3/FreeBSD4/libm3formsvbt.so.7 in /usr/ports/lang/pm3-forms === Extracting for pm3-forms-1.1.15 No MD5 checksum file. === pm3-forms-1.1.15 depends on file: /usr/local/lib/m3/FreeBSD4/libm3vbtkit.so.7 - not found ===Verifying install for /usr/local/lib/m3/FreeBSD4/libm3vbtkit.so.7 in /usr/ports/lang/pm3-gui === Extracting for pm3-gui-1.1.15 No MD5 checksum file. === pm3-gui-1.1.15 depends on file: /usr/local/lib/m3/FreeBSD4/libm3tcp.so.7 - not found ===Verifying install for /usr/local/lib/m3/FreeBSD4/libm3tcp.so.7 in /usr/ports/lang/pm3-net === Extracting for pm3-net-1.1.15 No MD5 checksum file. === pm3-net-1.1.15 depends on file: /usr/local/lib/m3/FreeBSD4/libm3.so.7 - not found ===Verifying install for /usr/local/lib/m3/FreeBSD4/libm3.so.7 in /usr/ports/lang/pm3-base === Installing for pm3-base-1.1.15 cd boot-FreeBSD4/m3core/FreeBSD4; gmake -f make.boot CC=cc CFLAGS=-O -pipe AS=as ASFLAGS= AR=ar ARFLAGS=rv RANLIB=touch EXTRALIBS=-lm LDFLAGS= gmake[1]: Entering directory `/usr/ports/lang/pm3-base/work/pm3-1.1.15/boot-FreeBSD4/m3core/FreeBSD4' cc -O -pipe-c -o RTHeapDepC.o RTHeapDepC.c RTHeapDepC.c:101: nfs/nfs.h: No such file or directory RTHeapDepC.c: In function `mount': RTHeapDepC.c:719: dereferencing pointer to incomplete type RTHeapDepC.c:719: dereferencing pointer to incomplete type RTHeapDepC.c:720: dereferencing pointer to incomplete type RTHeapDepC.c:720: dereferencing pointer to incomplete type RTHeapDepC.c:721: dereferencing pointer to incomplete type RTHeapDepC.c:721: dereferencing pointer to incomplete type gmake[1]: *** [RTHeapDepC.o] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/pm3-base/work/pm3-1.1.15/boot-FreeBSD4/m3core/FreeBSD4' gmake: *** [boot] Error 2 *** Error code 2 Stop in /usr/ports/lang/pm3-base. *** Error code 1 Stop in /usr/ports/lang/pm3-base. *** Error code 1 Stop in /usr/ports/lang/pm3-base. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-net. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-gui. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/lang/pm3-forms. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. *** Error code 1 Stop in /usr/ports/net/cvsup. __ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To
XawTV dump a core in CURRENT
XawTV dump a core in CURRENT? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: building cvsup from ports
John I have a patch (courtesy of Brian Somers) that fixes M3. I believe he has submitted it to you. May I/We commit it? M could this patch please be made available via HTTP or anon FTP? so those of us unable to install cvsup can get it? :) thnx -Erik [EMAIL PROTECTED] [http://math.smsu.edu/~erik] The opinions expressed by me are not necessarily opinions. In all probability, they are random rambling, and to be ignored. Failure to ignore may result in severe boredom or confusion. Shake well before opening. Keep Refrigerated. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Cyrille Lefevre writes: : I don't know -current. what is the feature which replace kget ? : does boot -c (or whatever) still exists ? is it possible to : edit KERNEL.hints at boot time ? set/unset works. I've removed ISA devices at boot time by unsetting the 'at' hint. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sysinstall is still horribly broken.
nelsont I had to toss my 2001 snapshot because it still had nelsont the /mnt/dev sysinstall problem which was apparently nelsont fixed as of 2002. It isn't. I'll try to investigate tomorrow (strictly speaking, 'late today in JST'; I'm sleepy), but according to my intuition, this is yet another bug; something goes wrong when there are partitions already in a disk. I have several questions to you before I reproduce this bug: 1) What's in your slice 1 and 2? Windows? other FreeBSD? 2) You said that your ad0s3 was already partitioned. Does this mean that you have already installed FreeBSD to ad0s3 and try to overwrite existing installations? 3) Do you have other fresh (i.e., non-partitioned) disk to install FreeBSD again? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sysinstall is still horribly broken.
On Sun, Nov 18, 2001 at 05:10:30AM +0900, Makoto Matsushita wrote: nelsont I had to toss my 2001 snapshot because it still had nelsont the /mnt/dev sysinstall problem which was apparently nelsont fixed as of 2002. It isn't. I'll try to investigate tomorrow (strictly speaking, 'late today in JST'; I'm sleepy), but according to my intuition, this is yet another bug; something goes wrong when there are partitions already in a disk. I have several questions to you before I reproduce this bug: 1) What's in your slice 1 and 2? Windows? other FreeBSD? The following is what the partition editor reports from the 5.0 snapshot. I've included it 'cause I've always found it amusing how the partitions ended up being arranged on these drives. (It was originally a PartitionMagic effort to resize the factory def- ault Windows partition). Offset Size(MB) End Name Ptype Desc Subtype 0 0 62- 6 unused0 63599212273659ad0s2 3freebsd 165 C 12273660349819438649ad0s3 3freebsd 165 19438650558530876929ad0s4 3freebsd 165 308769300 30876882- 6 unused0 30876993400039070079ad0s1 2fat 12 ad0s2 has 4.4-STABLE on it. ad0s4 is just a shared area. ad0s3 is for -CURRENT, and ad0s1 gets the grand responsibility of looking after the stock Windows ME that came with the laptop. 2) You said that your ad0s3 was already partitioned. Does this mean that you have already installed FreeBSD to ad0s3 and try to overwrite existing installations? Well, yes and no. I actually already had a -CURRENT installed on ad0s3. But this was from a slightly older 5.0 snapshot where I Ctrl-C'd in the middle of the bin installation, then made all the appropriate links to correct the problem of /mnt/xxx not existing. At the time I sent out the e-mail, I had manually newfs'd ad0s3[efg] from -CURRENT, then newfs'd ad0s3a when I was running 4.4-STABLE. 3) Do you have other fresh (i.e., non-partitioned) disk to install FreeBSD again? In light of what you've just said about this being a different problem to what other people have been reporting, I marked each slice as being UFS+S Y so they were recreated with newfs. This has worked! So, it looks like it's just a problem with existing partitions. Makoto `MAR' Matsushita Thanks for your quick reply. Trent. -- Trent Nelson - Software Engineer - [EMAIL PROTECTED] A man with unlimited enthusiasm can achieve almost anything. --unknown To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[Fwd: AMD not existing USB devices]
Hi, i dont know where is the right place for this questions. On my -current FreeBSD system exist a USB device which is not always attached. My amd is configured to automount this device: cam type:=pcfs;dev:=/dev/da0s1;opts:=rw which runs quite fine, if the device is attached at boot time. So i can attach/detach it and it will be mounted/dismounted. But if i havent attached the device at boot time my system hangs at startup from amd. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: re-entrancy and the IP stack.
Are y'all going to discuss this at BSDCon? I'm probably going there and would like to contribute if I could. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: re-entrancy and the IP stack.
I recommend you all look at The Click Modular router http://www.pdos.lcs.mit.edu/click/ which is a step in the right direction. Of course given the current architecture it may be very hard to adapt it to this kind of model. I led/worked on a project at Wind River Systems to do a multi-instance stack based off of the 4.4 BSD lite code. I can tell you that without quite a bit of rearchitecting what you get is always a hack. There are (were?) over 100 global variables in the 4.4BSD lite code. I've not counted on 4.4 or -CURRENT so I can't say. There are also the issues of the locks though I suspect in -CURRENT (since the kernel is MP) you have handled these in some way. An extensible, multi-threaded TCP/IP would NOT look like the 4.4BSD-Lite code. Is this a goal of FreeBSD now? I am working on some things to make this possible but it is independent of FreeBSD and very very early days as yet. Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: In message [EMAIL PROTECTED] Cyrille Lefevre writes: : I don't know -current. what is the feature which replace kget ? : does boot -c (or whatever) still exists ? is it possible to : edit KERNEL.hints at boot time ? set/unset works. I've removed ISA devices at boot time by unsetting the 'at' hint. thanks for the trick. but show/set/unset are really less intuitive than boot -c, specifically to novice users. unfortunately, I'm not forth aware at all, so, don't ask me about writting such tool using forth :P Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: re-entrancy and the IP stack.
* George V. Neville-Neil [EMAIL PROTECTED] [07 16:17] wrote: I recommend you all look at The Click Modular router http://www.pdos.lcs.mit.edu/click/ which is a step in the right direction. Of course given the current architecture it may be very hard to adapt it to this kind of model. I led/worked on a project at Wind River Systems to do a multi-instance stack based off of the 4.4 BSD lite code. I can tell you that without quite a bit of rearchitecting what you get is always a hack. Actually, usually when you rearchitect what you get is a hack to allow multi-instance instead of relying on tried and true algorithms like Van Jacobson. :) There are (were?) over 100 global variables in the 4.4BSD lite code. I've not counted on 4.4 or -CURRENT so I can't say. There are also the issues of the locks though I suspect in -CURRENT (since the kernel is MP) you have handled these in some way. An extensible, multi-threaded TCP/IP would NOT look like the 4.4BSD-Lite code. I really can't agree with this, there isn't all that much that makes the version of the stack in FreeBSD not modular, I usually find that with enough study one quickly learns why things are done versus immediatly screaming this needs to be rewritten so that _I_ can understand it. Is this a goal of FreeBSD now? I am working on some things to make this possible but it is independent of FreeBSD and very very early days as yet. The goal right now is more MPsafe than extensable, an extensable stack would be an interesting project but I doubt it would be as stable nor as fast as what we already have. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Cyrille Lefevre writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre writes: : : I don't know -current. what is the feature which replace kget ? : : does boot -c (or whatever) still exists ? is it possible to : : edit KERNEL.hints at boot time ? : : set/unset works. : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : thanks for the trick. but show/set/unset are really less intuitive : than boot -c, specifically to novice users. unfortunately, I'm not : forth aware at all, so, don't ask me about writting such tool using : forth :P Right. There is a forth tool available (authored I think by matsushita-san), and now that matsushita-san is a committer, maybe it will be done in time for 5.0. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: In message [EMAIL PROTECTED] Cyrille Lefevre writes : : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre wr ites: : : I don't know -current. what is the feature which replace kget ? : : does boot -c (or whatever) still exists ? is it possible to : : edit KERNEL.hints at boot time ? : : set/unset works. : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : thanks for the trick. but show/set/unset are really less intuitive : than boot -c, specifically to novice users. unfortunately, I'm not : forth aware at all, so, don't ask me about writting such tool using : forth :P Right. There is a forth tool available (authored I think by matsushita-san), and now that matsushita-san is a committer, maybe it will be done in time for 5.0. :-) As a fallback, I've been threatening to do a simple userconfig-style thing in loader itself as a fallback if necessary.. I'd rather not since that would just make loader bigger still, but it's always there as a quick/dirty fallback option. If my memory serves me correctly, we dont enable bootforth on the 5.0 boot floppies. This is probably more a symptom of having an identical config for floppies and cd boot. Now that we have cdboot for i386 all but there, we should be able to finally do a complete boot for the CD case and a smaller stripped kernel with esoteric drivers on a seperate disk for the floppy-only case. 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: Today's kernel can't seem to load linux.
Edwin Culp wrote: I just rebooted and was put into single user with the following message: /boot/kernel/kernel: KLD linprocfs.ko: depends on linux - not available I just had to comment out my linproc entry in fstab and booted fine but linux emulation doesn't work. If I try to load it manually, I get and Exec format error. Do you get a console error message when you try to kldload linux? Perhaps an undefined symbol reported? 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: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Peter Wemm writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre writes : : : : Warner Losh wrote: : : In message [EMAIL PROTECTED] Cyrille Lefevre wr : ites: : : : I don't know -current. what is the feature which replace kget ? : : : does boot -c (or whatever) still exists ? is it possible to : : : edit KERNEL.hints at boot time ? : : : : set/unset works. : : : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : : : thanks for the trick. but show/set/unset are really less intuitive : : than boot -c, specifically to novice users. unfortunately, I'm not : : forth aware at all, so, don't ask me about writting such tool using : : forth :P : : Right. There is a forth tool available (authored I think by : matsushita-san), and now that matsushita-san is a committer, maybe it : will be done in time for 5.0. :-) : : As a fallback, I've been threatening to do a simple userconfig-style : thing in loader itself as a fallback if necessary.. I'd rather not since : that would just make loader bigger still, but it's always there as : a quick/dirty fallback option. : : If my memory serves me correctly, we dont enable bootforth on the 5.0 boot : floppies. This is probably more a symptom of having an identical config : for floppies and cd boot. Now that we have cdboot for i386 all but there, : we should be able to finally do a complete boot for the CD case and a : smaller stripped kernel with esoteric drivers on a seperate disk for the : floppy-only case. Actually, now that I think about it, the module I saw was in 'C'. So someone needs to learn forth to do this. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: [snip] Actually, now that I think about it, the module I saw was in 'C'. So someone needs to learn forth to do this. :-) what are you waiting for ? :P it's still possible to install gforth (don't know if it's compatible w/ loader ?) and to begin to read the gforth info files (don't know if they are really accurate ?). well, I'm the maintainer, but that's all :-)) I still know nothing to forth ! Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make installworld failure in usr.bin/tip
On Fri, 16 Nov 2001, Mark Murray wrote: Mark, Poul-Henning, So, what was the concensus? Should we fix this in Makefile, or just put this as an UPDATING entry and have users manually remove the old UUCP stuff? Erm, it _is_ fixed in the makefile. If you have a better method, lets hear it. :-) Back out the entire tip commit? This would also restore all the FreeBSD changes clobbered by it. It doesn't even compile cleanly: /usr/src/usr.bin/tip/aculib/courier.c:312: warning: `cour_write' was declared implicitly `extern' and later `static' /usr/src/usr.bin/tip/aculib/courier.c:306: warning: previous declaration of `cour_write' /usr/src/usr.bin/tip/aculib/courier.c:312: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/courier.c:306: warning: previous implicit declaration of `cour_write' /usr/src/usr.bin/tip/aculib/courier.c:312: warning: `cour_write' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/df.c:126: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/df.c:85: warning: previous implicit declaration of `df_disconnect' /usr/src/usr.bin/tip/aculib/df.c:126: warning: `df_disconnect' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/hayes.c:148: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/hayes.c:141: warning: previous implicit declaration of `hay_disconnect' /usr/src/usr.bin/tip/aculib/hayes.c:148: warning: `hay_disconnect' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/hayes.c:214: warning: `error_rep' was declared implicitly `extern' and later `static' /usr/src/usr.bin/tip/aculib/hayes.c:122: warning: previous declaration of `error_rep' /usr/src/usr.bin/tip/aculib/hayes.c:214: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/hayes.c:122: warning: previous implicit declaration of `error_rep' /usr/src/usr.bin/tip/aculib/hayes.c:214: warning: `error_rep' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/hayes.c:255: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/hayes.c:156: warning: previous implicit declaration of `goodbye' /usr/src/usr.bin/tip/aculib/hayes.c:255: warning: `goodbye' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/t3000.c:123: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/t3000.c:117: warning: previous implicit declaration of `t3000_disconnect' /usr/src/usr.bin/tip/aculib/t3000.c:123: warning: `t3000_disconnect' was previously implicitly declared to return `int' /usr/src/usr.bin/tip/aculib/t3000.c:328: warning: `t3000_write' was declared implicitly `extern' and later `static' /usr/src/usr.bin/tip/aculib/t3000.c:322: warning: previous declaration of `t3000_write' /usr/src/usr.bin/tip/aculib/ventel.c:143: warning: type mismatch with previous implicit declaration /usr/src/usr.bin/tip/aculib/ventel.c:117: warning: previous implicit declaration of `ven_disconnect' /usr/src/usr.bin/tip/aculib/ventel.c:143: warning: `ven_disconnect' was previously implicitly declared to return `int' Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
