From owner-freebsd-current Mon May 18 00:02:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21384 for freebsd-current-outgoing; Mon, 18 May 1998 00:02:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from runner.jjsoft.com (jahanur.intur.net [206.97.149.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21372 for ; Mon, 18 May 1998 00:02:32 -0700 (PDT) (envelope-from jahan@pc.jaring.my) Received: from pc.jaring.my (klg-41-50.tm.net.my [202.188.41.50]) by runner.jjsoft.com (8.8.7/8.8.7) with ESMTP id CAA17983 for ; Mon, 18 May 1998 02:01:09 -0500 (CDT) (envelope-from jahan@pc.jaring.my) Message-ID: <3560AD80.BF17AA1B@pc.jaring.my> Date: Mon, 18 May 1998 14:52:00 -0700 From: Jahan X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Undefined symbol "___error" References: <199805122155.QAA04191@unix.tfs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look, no one is pushing us for using FreeBSD.If we use, its our problem or benefit. I WANNA STRESS THIS POINT TO MAINTNERS. Plz HAVE PROPER DOCUMNET ON HOW TO UPGRADE FROM FreeBSD x.x.x to FreeBSD x.x.x We are users ( me alone ?) really having problem upgrading. I have mentioned earlier.I had problem compiling from one point of cvsupped files. I mailed the problem here. We ( me alone ?) do not want to spoon fed too, but guideline. Even some faq's are not listed in faq ( telnet, ip accounting, lpr, increasing swap space,sound card). Plz do something about that. I will prefer better document than better fency new version of OS. Jim Bryant wrote: > In reply: > > Jim Bryant writes: > > > this has got to be one of the most damnned inconvenient changes i > > > have ever seen freebsd take... > > > > So who forced you to run current? If you don't like this, stick to stable. > > > > > does this mean that ALL third party programs that use curses MUST be > > > recompiled?!?!?! > > > > Recompiled, no. Relinked, yes. > > > > > just because, as i understand it, they didn't want to bump the lib > > > version numbers?!?!?! > > > > > > > > > does anyone realize how much this change breaks????!!!! > > > > Again, this is -current. If you can't stand the heat, stay out of the > > kitchen. > > > > BTW, are your ? and ! keys stuck?????!?!?!??!!!! > > i understand the meaning of -current... even the one that says some > idiotic change could bring down 60% of the apps ever written for > FreeBSD. that is why such changes are made in -current. if such > changes ever made it to -release, then watch how fast people split the > fold and go to openbsd, or even linux for fear that anything they > write will have to be re-released with the very next version of > -release. > > i'll submit a diff tonight/tomorrow that will satisfy the requirements > for the call without even relinking the target; a do-nothing stub that > should have been factored in when the original __error was removed. > > jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message