Re: problems with make world (Sunday)
On Tue, Sep 05, 2000 at 09:20:17AM +0200, Jean-Francois Dockes wrote: Gary Kline writes: For the record, I just cvsup'ed this morning Monday, 04sep00) and buildworld hangs here: === objdump ... cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump -I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils -I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils -DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -o objdump objdump.o prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a ../libbfd/libbfd.a ../libiberty/libiberty.a ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' *** Error code 1 I don't know if this applies to your case, but I had this error while trying a direct upgrade from 3.2-release to 4-stable. It appears that mkstemps() came in later than 3.2. I guess that a cvsup/buildworld to 3-stable would be the correct way to solve this issue, but I just ar'd the appropriate 4.x libc file into libiberty (cough, cough), in case it would save me one more cvsup and it did do it... I then remade world under 4-stable to clean things up. I should have grep'd my ~/Mail files earlier. On 20 August the same mkstemps snafu hit me. The fix was (and is) to add mkstemps.c to the SRCS list in /usr/src/gnu/usr.bin/binutils/libiberty/Makefile. The libiberty/Makefile still needs patching and the patch still needs a cvs commit. ...Anybody?? gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
cant make buildkernel
I have been tracking stable for a while without incident but since the last 2 weeks, after a cvsup and a make buildworld, make buildkernel fails with " make: dont know how to make /usr/src/sys/ufs/ffs/ffs_softdep.c. Stop " Any ideas as to why this happens ? my last cvsup was yesterday. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
"Sameer R. Manek" [EMAIL PROTECTED] wrote: Does anyone have any suggestions on how to have 802.11 wireless for home users? Naturally it should be supported by FreeBSD. Configuruation can be done on any pc os though. My only affordable solution so far is to use the Apple AirPort base station, and wavelan pcmcia cards, but I don't know if they can co-exist, and the AirPort needs a Macintosh to configure. My idea of affordable for this is less then $500, the lucent wavelan solution works out to about $900 startup, that's a little out of my budget. Just to let everyone know: I should be getting a TechWorks (Buffalo) AirStation in the next couple of days, and I'll be adding it to my FreeBSD Wireless documentation. A co-worker got one, and we played with it briefly; it doesn't look too bad. It's an actual base station (does not work in ad-hoc mode). I don't know if it supports NAT/DHCP though, although bridging appears to work fine. Other comments: * Configuration is done via a web browser (bleah). * Only supports 40-bit encryption. Don't know if it's like the AirPort when it comes to the 128-bit encryption upgrade, though. * Keys can be entered as hex (yes!). * The $279 model doesn't have a modem. With a modem, it's $299 (the same as the AirPort). * It works fine with my Lucent Orinoco (WaveLan) gold card (we didn't try enabling encryption, though). -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Cvsup mirrors
Hi, I have recently noticed that cvsup*.freebsd.org can happen to have different contents. In particular I cvsupped all from (AFAIR) cvsup3 and it deleted rsa_eay.c. Repeated (in about 5 minutes) cvsup from cvsup5 checked the file out again. Which cvsup server is the most accurate? Anyway, rsa_eay.c is a part of librsaINTL.a. How is it possible that it wasn't in the repository? -- , The power . Any sufficiently advan- dP to serve 7bKrzysztof Parzyszek . ced bug is indistingui- (8bd8) + shable from a feature. `88bo8FBSD8od88'[EMAIL PROTECTED]` -- Rich Kulawiec To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
"Kevin Oberman" [EMAIL PROTECTED] wrote: Even at 128 bits, WEP encryption is, at best, rather weak. The right answer is to use strong encryption for everything. OpenSSH is now a standard part of FreeBSD. Use it and stop sending clear passwords over the net. Then you don't care about the security of the link, only the end nodes. Very true. If people want to know why, see: http://mail-index.netbsd.org/tech-net/2000/02/04/0001.html -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1 STABLE broken since today!
It was indeed fixed. Nobody posted a HEADS UP. i know thats it has been fixed... i was wondering why there wasnt a HEADS UP when the problem was discovered. sometimes its not clear wether there is a problem or not... i mean there are almost daily mails that buildworld or whatever is broken, and most of the time its just the admin doing something wrong. there should be a official statement when something major is really broken, even if it has been fixed there should be a offical "fixed" notify mail. Bernhard Valenti To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
"KO" == Kevin Oberman [EMAIL PROTECTED] writes: KO OpenSSH is now a standard part of FreeBSD. Use it and stop sending KO clear passwords over the net. Then you don't care about the security KO of the link, only the end nodes. But without encryption, anyone can talk to your base station. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stop error in make world
[ On Tuesday, September 5, Bill Moran wrote: ] Just cvsupped yesterday, I've tried to `make buildworld' 3 times. The only time I didn't seem to get a stop error is when I did `make -k buildworld' However, immediately after doing that I did a `make buildworld' and got this error again. I know this system has problems ... Any hints as to where I need to focus to get them fixed? If I did the `make -k buildworld' and then `make installworld', could that possibly set the stage for a successful `make buildworld' ??? Egad! (For those of you who aren't familiar with this thread ... this is a production machine and I comitted a cardinal sin by not being careful enough during a cvs upgrade ... I'm on the verge of being in deep sh*t!) Well, I just cvsup'ed 1 hour ago and built world. No problems. That segfault you got when building perl looks really odd. Other people have said that segfaults during buildworld are generally hardware problems. Most likely memory. Any chance of you swapping out the memory in the machine? Anyway, just reporting "no errors" here with a fresh tree. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
At 9:11 AM -0700 2000/9/5, Kevin Oberman wrote: Even at 128 bits, WEP encryption is, at best, rather weak. The right answer is to use strong encryption for everything. If I'm not mistaken, this is actually using Triple DES at 128 bits, so this is still decently strong. The problem is that the normal WEP key is only 40 bits long, which we know can be cracked in a matter of only a few seconds. OpenSSH is now a standard part of FreeBSD. Use it and stop sending clear passwords over the net. Then you don't care about the security of the link, only the end nodes. OpenSSH is good, and I certainly use it (and other ssh products) where possible. However, it is not a panacea, it cannot be used everywhere, and if you can enable additional encryption at the link level, then you should certainly do that. -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cant make buildkernel
Gary Smith wrote: I have been tracking stable for a while without incident but since the last 2 weeks, after a cvsup and a make buildworld, make buildkernel fails with " make: dont know how to make /usr/src/sys/ufs/ffs/ffs_softdep.c. Stop " Any ideas as to why this happens ? my last cvsup was yesterday. The softupdates code was merged with current (the licence issues were resolved I guess), so when you cvsupped the system copied the updated ffs_softdep.c on your existing symlink, then deleted the target the symlink pointed to, leaving you with a dangling symlink. Delete those symlinks (ffs_softdep.c and softdep.h IIRC) and try cvsupping again. -- _ __ ___ ___ __ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED] / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stop error in make world
John Reynolds~ wrote:
Well, I just cvsup'ed 1 hour ago and built world. No problems. That segfault
you got when building perl looks really odd. Other people have said that
segfaults during buildworld are generally hardware problems. Most likely
memory.
I'd be surprised ... considering I did a successful `make world' about a
month ago with no problems, and I've done many compilations (Apache,
MySQL, php, ssh) on this machine with no problems prior to this. Still,
it's a possibility, things do wear out/break/etc.
Any chance of you swapping out the memory in the machine?
That's pretty much a last resort ... my goal is to fix this without
having to drive 3.5 hours to the location where it exists. If nothing
else works, I'll do that.
Anyway, just reporting "no errors" here with a fresh tree.
Well, that's good news, it means I've botched something. I think the
mistake is that I accidentally got a 3.X-STABLE tree over top the 4.X
tree and the version of perl from 3.X (whatever version that is) isn't
up to doing some of the chores that are required for a 4.X make world.
My plan of attack at this point is:
make -k buildworld
make installworld
make buildworld
If at that point I have no errors, I'm home free to rebuild a current
kernel and make installworld again.
If I'm still having trouble. I'm going to try cvsdowning to 4.0-STABLE
(which is what the machine was before this all started) and see if I can
get it working.
If that doesn't work and I can still get ssh access to the machine, I'll
get really desperate and try getting a 3.5.1 machine on here.
If that doesn't work, I'm driving 3.5 hours to do a clean installation
(please no)
If anyone has any better attack plans, I'm interested to hear them.
Thanks for all the help so far.
-Bill
--
FreeBSD ('BSD'):
No battles to the death are recalled. It is a small Daemon wearing
sneakers. It
is normally found on Internet servers and powerful desktops, and moves
very
quickly. A kill of this poweful creature is enough to tick off any
sysadmin. It
is highly magical, having the power to serve. It resists DoS and SYN
flood
attacks. Nothing is known about its attack.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Stop error in make world
"BM" == Bill Moran [EMAIL PROTECTED] writes: BM I'd be surprised ... considering I did a successful `make world' about a BM month ago with no problems, and I've done many compilations (Apache, BM MySQL, php, ssh) on this machine with no problems prior to this. Still, BM it's a possibility, things do wear out/break/etc. I had a machine with a CPU fan that stopped spinning. When doing a buildworld with anything else cpu-intensive running, it would do all sorts of flaky things, including segfaults. If the only thing running was buildworld, it would succeed. If I add in a cpu-intensive program, like the distributed.net client program, it would consistently fail at random points. I just put in a new fan and am testing out a buildworld with other things running as well. But this is most likely a hardware issue you're observing. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D.Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-301-545-6996 GPG MIME spoken herehttp://www.khera.org/~vivek/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
Brad, We can agree that the 40 bit stuff is not worth the trouble. My 128 bit Lucent card says "128-bit RC-4 encryption". Last I heard, RC-4 was not considered a "safe" algorithm. Also, in any multi-user environment, the secret must be too public. (I believe that when I know something, it's secure. When I tell someone, it's secret. When someone else is told, it's public.) Using an encrypted link is fine, but I worry that people will believe far too much in its security. (Especially when they see "128-bit".) If I'm wrong and it is 3DES, never mind! But still use ssh whenever possible. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cant make buildkernel
Thanks, I think that should work On Tue, 05 Sep 2000, Andresen,Jason R. wrote: Gary Smith wrote: I have been tracking stable for a while without incident but since the last 2 weeks, after a cvsup and a make buildworld, make buildkernel fails with " make: dont know how to make /usr/src/sys/ufs/ffs/ffs_softdep.c. Stop " Any ideas as to why this happens ? my last cvsup was yesterday. The softupdates code was merged with current (the licence issues were resolved I guess), so when you cvsupped the system copied the updated ffs_softdep.c on your existing symlink, then deleted the target the symlink pointed to, leaving you with a dangling symlink. Delete those symlinks (ffs_softdep.c and softdep.h IIRC) and try cvsupping again. -- _ __ ___ ___ __ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED] / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stop error in make world
Bill Moran wrote: John Reynolds~ wrote: Well, I just cvsup'ed 1 hour ago and built world. No problems. That segfault you got when building perl looks really odd. Other people have said that segfaults during buildworld are generally hardware problems. Most likely memory. I'd be surprised ... considering I did a successful `make world' about a month ago with no problems, and I've done many compilations (Apache, MySQL, php, ssh) on this machine with no problems prior to this. Still, it's a possibility, things do wear out/break/etc. Any chance of you swapping out the memory in the machine? That's pretty much a last resort ... my goal is to fix this without having to drive 3.5 hours to the location where it exists. If nothing else works, I'll do that. Anyway, just reporting "no errors" here with a fresh tree. Well, that's good news, it means I've botched something. I think the mistake is that I accidentally got a 3.X-STABLE tree over top the 4.X tree and the version of perl from 3.X (whatever version that is) isn't up to doing some of the chores that are required for a 4.X make world. My plan of attack at this point is: make -k buildworld make installworld make buildworld I think if you really loaded a 3.5 tree on top, you will need to follow the cvsup upgrade path for 3.5 to 4.1 in /usr/src/UPDATING. You could also upgrade the binaries to 4.1-R and then rebuild userland and the kernel. There were such massive changes to /etc and all of the /binutils. I thought my "i" key was going to wear out running mergemaster :). Kent If at that point I have no errors, I'm home free to rebuild a current kernel and make installworld again. If I'm still having trouble. I'm going to try cvsdowning to 4.0-STABLE (which is what the machine was before this all started) and see if I can get it working. If that doesn't work and I can still get ssh access to the machine, I'll get really desperate and try getting a 3.5.1 machine on here. If that doesn't work, I'm driving 3.5 hours to do a clean installation (please no) If anyone has any better attack plans, I'm interested to hear them. Thanks for all the help so far. -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
