Re: Lock of struct filedesc, file, pgrp, session and sigio
On Thu, May 31, 2001 at 01:46:00PM -0700, John Baldwin wrote: It doesn't hurt to help distribute the load some, though. Requiring each person who makes a change to compile it on every possible arch is not something that will scale as more and more archs are added. If a committer can get someone else to perform some of these test compiles and fix any brokenness that comes up I think that is adequate. Forgot to add, if others use the Alpha owners as simple test-compile resources, (1) the Alpha owners will not get any other work done, (2) will get quite tired of testing things that the patch author could easily test himself. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release failure
On Sun, May 27, 2001 at 11:32:09PM -0700, Bruce A. Mah wrote: +.if !defined(NORELNOTES) Do we really need Yet Another Knob? Why isn't NODOC suffient? I cannot think of any reason that the people who typically use NODOC=yes would want release notes. Or please at least treat NODOCS=yes == NORELNOTES=yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 'make includes' ownership patch
On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote: This was on my TODO. The only problem with INCOWN/INCGRP not being used here is that they were introduced long after include/Makefile. And perhaps one should go read the commit message that introduced them... it was an experiment, a sample test designed to only be used in -current /usr/src/lib, that BDE, Sheldon and myself had long followon conversations about, and got dropped into the cracks. What was the reasoning for a serperate owner specification from BIN*? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src UPDATING
On Mon, May 28, 2001 at 10:16:46PM -0700, Doug Barton wrote: .UPDATING Log: Looks like -current is safe again, and has been since Friday. Alpha is in evern worse shape than x86. The statement that -current is safe is 110% wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Date for a working -current?
On Thu, May 24, 2001 at 04:56:41PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Joseph Koshy writes: : I'm in the processing of bring a 5-current system of Oct 2000 vintage : more upto-date. May 18th, 2001 12:00:00 is what I've been using. One must be careful posting something like this -- it isn't timezone clean. To get just before Afred's VM commit you can use -D '2001-05-19 01:27:00 UTC' -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: amd feature request (Re: AMD config file question.)
On Fri, May 25, 2001 at 09:56:42AM -0400, Mikhail Teterin wrote: Now that smbfs is in, can amd be used to mount smb shares? Of course, it can. But can we have something like host type, where all smb-shares available from a host are automaticly accessible? This may be added to the host-type together with NFS, or be made part of a separate smbhost type. I'd vote for the first one, personally... Send me a tested patch and I'll consider it. I want to make sure you won't be causing any problems in the generic case. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
wchar.h / Citrus import
I am going to import parts of the Citrus Project XPG4DL (an implementation of I18N (locale) framework). We *need* wchar.h and we just cannot wait. If there are known concerns or issues with this, please let me know. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: **HEADS-UP** ficl changes change `base' type
On Thu, May 10, 2001 at 05:20:46PM -0300, Daniel C. Sobral wrote: John Sadler is not a Unix user, and has no experience with Unix, and ... If you know exactly how to produce a .tar.gz under Windows that is suitable for our use, I'm sure he would appreciate the help. Ask him to use infozip/pkzip -- I know that is easy for Winloose users. Our unzip has a command line option to fix the text line termination. The zip he produces can be extracted fine. That's not the question. Then what's the question? Why can't people use the .zip file and not ask Sadler to produce a .tar.gz? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -u patch
Lets try another realistic example: cp -uvp ab* cde*.f* g? h/*.i? j/kl /m What's the find | cpio invocation for that? When you come up with it, it echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ... Messy - No, Portable - Yes. BT - wrong. cp flattens the hierarchy, cpio does not. I think this was a trick question :*P Yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: **HEADS-UP** ficl changes change `base' type
On Thu, May 10, 2001 at 02:21:09AM -0300, Daniel C. Sobral wrote: John Sadler is not a Unix user, and has no experience with Unix, and ... If you know exactly how to produce a .tar.gz under Windows that is suitable for our use, I'm sure he would appreciate the help. Ask him to use infozip/pkzip -- I know that is easy for Winloose users. Our unzip has a command line option to fix the text line termination. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/contrib/binutils/ld/emultempl elf32.em
On Thu, May 03, 2001 at 07:48:08AM -0700, David Wolfskill wrote: [Ref. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=574034+0+current/cvs-all] ... eelf_i386.c:158: elf-hints.h: No such file or directory Crap,crap,crap,crap,crap!!! I thought I had gotten my systems clean enough when I did the post-commit ``make buildworld'' test. *sigh* a nice bootstrap issue here. Problem is elf-hints.h is a new header and a buildtool uses it. I guess a -I/usr/src/include is needed (or an install of headers into /usr/obj). To get over this hump if you aren't interested in debugging the bootstrap issue: cd /usr/src/include make obj make install -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in fxp driver
On Tue, May 01, 2001 at 02:16:33PM -0700, Peter Wemm wrote: On the other hand, you might try using dwarf2 debugging, that is pretty complete. And what we'll be using when GCC 3.0 is imported. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -u patch
On Mon, Apr 30, 2001 at 09:56:09AM +0200, Sheldon Hearn wrote: Question is, do we want to add this to our cp? Bleh. :-) Blah. for i in `find /path/to/src`; do if [ $i -nt /path/to/dst/$i ]; then cp $i /path/to/dst/ fi done Do you also suggest we get rid of `more' as its functionality can be implimented using cat and sed? I personally find this option useful enough that I have to keep `gcp' around. I guess I got used to using a simular utility under M$-DOS and thus it makes sense to me. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Updated: cp -t patch (w/ commentary)
On Wed, Apr 25, 2001 at 06:08:15PM -0700, Dima Dorfman wrote: Dima Dorfman [EMAIL PROTECTED] P.S. obrien: that's a very clever and unintrusive way of avoiding getting two copies of a message; much better than [EMAIL PROTECTED] P.S. Dima: see the archives for my discussion of my requirements. I welcome your very clever and unintrusive way, but if it is just the statement use procmail, don't bother unless you're going to supply the rules that suit my needs. The standard simplistic delete dups doesn't. BTW, I am not the only one that feels procmail isn't suffient, and uses things like TrimYourCC. Those of us (well, at least me) who actually want a copy of the message in our inbox greatly appreciate it. Thanks! Yes, so I've discovered. I no longer trim them myself. I would just add a request to be removed from the CC line on replies to my emails, but nobody would pay attention to it. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Updated: cp -t patch (w/ commentary)
On Mon, Apr 23, 2001 at 11:33:24AM -0700, John W. De Boskey wrote: After some feedback, I have changed the patch slightly. Rename -d to -t and remove the requirement for the option to have a value. I thought people generally agreed the right fix was to add functionality to `xargs', not `cp' as you aren't scratching the general itch. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: One more typo in src/release/Makefile, rev 1.612? (w/patch)
On Mon, Apr 16, 2001 at 08:10:39PM -0700, John Baldwin wrote: Also, Bruce's fix is not entirely correct as it breaks for the non-debug kernel case, but I've already sent you a mail about that, just to let everyone know that it should be fixed shortly. :) I commited your "fix" for it. IMHO, it is cleaner before my commit and thus what it should be -- the release system should match what is known about the world. If someone has the need to disable debug kernels, they have the knowledge to edit src/release/Makefile... never the less, I committed what you desired. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Typo in src/release/Makefile, rev 1.161 (PATCH INCLUDED)
On Mon, Apr 16, 2001 at 10:05:03AM +0900, Makoto MATSUSHITA wrote: There is a small typo in src/release/Makefile rev 1.161; not 'kernel', but 'KERNEL' is correct. I think I got all these already. But I rev 1.161 is from back in 1995. Are you sure you've got the right /usr/src/release/Makefile? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One more typo in src/release/Makefile, rev 1.612? (w/patch)
On Mon, Apr 16, 2001 at 09:53:43AM -0700, Bruce A. Mah wrote: Thanks for fixing the typo in src/release/Makefile. I think however the real cause of the error that people were seeing is a typo on the line Damnit, I *tested* this and things landed in the right place. Grrr... Ok, no more hacking until I get a CVSup with the lastest release/Makefile and I'll kick off a fresh release to test. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: readline.h 1.12 incompatible with gdb.291/gdb/top.c 1.2, I think
On Fri, Apr 13, 2001 at 06:40:42PM +0400, Andrey A. Chernov wrote: Yes. Backward-compatible prototypes was enabled very recently to help old applications. I didn't expect it break gdb compilation again I need to update my box to test. It will probably be 2-3 hours and it will be fixed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 06:43:52PM +0400, Andrey A. Chernov wrote: On Wed, Apr 11, 2001 at 17:41:09 +0300, Maxim Sobolev wrote: GDB maintainer already notified with proposed patch. Awake now. Patch commited. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: World borken :((
On Wed, Apr 11, 2001 at 08:34:37PM +0400, Andrey A. Chernov wrote: Well, if you know about this problem why you did not wait for his reply before proceeding with importing? First of all, David ask me for readline importing, what I did was an response. But my request wasn't a request to break world. W/o doing the import myself (which typically means doing it in a local repo to test first), I could not have known the upgrade would break world. ;-) -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Failed to load linux.ko during boot
On Thu, Apr 05, 2001 at 11:30:21PM +0200, Morten Skriver wrote: [morten@mosk-pc]:/usr/home/morten$ linux kldload: can't load linux: Operation not permitted ELF binary type "3" not known. Abort trap You did not `brandelf' your /compat/linux/sbin/ldconfig. Did you install this from /usr/ports/emulators/linux_base? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i586 FP optimizations hosed.
On Sat, Mar 31, 2001 at 06:34:12PM +0200, Leif Neland wrote: CPU1 stopping CPUs: 0x0001... Stopped. Stopped at i586_bzero_oops+0x1: jmp i586_bzero_oops I get panics on that instructions too on my old 60MHz P5. I've got a core dump, will tell more when I can interpret it... Mark's machine is a dual SMP machine. I don't recall there being dual-P5-60's, but this is me guessing. You're going to have to provide a lot more details. Is your machine a UP or MP machine? The current sources are believed to work fine in a UP kernel. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i586 FP optimizations hosed.
On Fri, Mar 30, 2001 at 07:45:43AM +0200, Mark Murray wrote: I thought the 586 FP stuff was disabled? Nope. Depending on how current you are, it was either left broken. I commited BDE's fix to exeception.s that fixed things for K6-2 users. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
On Sun, Mar 25, 2001 at 04:08:47PM +0300, Valentin Nechayev wrote: 192.168.5 should be interpreted as 192.168.0.5 in host address context, but as 192.168.5.0 in network address context. (Such network address context is well seen in sentences such as "10/8", "192.168/16".) Where is this documented? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: upgrade tcpdump in -current?
On Sat, Mar 24, 2001 at 03:19:54PM +0100, Mark Huizer wrote: Are there any plans on upgrading tcpdump to e.g. 3.6.2, which has better support for e.g. NFS over IPv6? Bill Fenner was working on this. I don't know what happened to it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
On Sat, Mar 24, 2001 at 11:24:47PM -0400, The Hermit Hacker wrote: doing so right now ... one quick/stupid question ... how does one 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka make reinstall -or- make kernel-reinstall removing pcm fixes the panic, it appears ... Yep! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
On Sun, Mar 25, 2001 at 05:58:53AM +0100, Cameron Grant wrote: can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? Fixed my panics too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [FIX] Re: CFS - Portmap
On Fri, Mar 23, 2001 at 12:49:33AM +0100, Martin Blapp wrote: /etc/mount -o port=3049,intr localhost:/null /crypt What machine are you doing this on?? FreeBSD has no /etc/mount? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** HEADS UP ** portmap daemon renamed to rpcbind
The Portmapper binary has been renamed from `portmap' to `rpcbind'. The name change was taken care of in /etc/defaults/rc.conf and in the auto-dependacy code in /etc/rc. HOWEVER, you may need to edit your /etc/hosts.allow and make the name change there. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT instability
On Tue, Mar 20, 2001 at 03:23:55PM -0800, Edwin L. Culp wrote: It would really be nice to have this committed, if it doesn't break anything, to not have to be patching every time. It will be. I am waiting a responce back from someone. But one way or another it will be fixed -- I run two K6-2's myself, including my main desktop. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: swap-backed md-based /tmp to replace mfs-based one
On Tue, Mar 13, 2001 at 12:12:35AM +0900, Daniel C. Sobral wrote: A while ago someone suggested a /etc/md.conf and an mdon(1) similar to swapon(1). Putting it in terms of this analogy make this approach sound quite reasonable. This solution is much more flexible than simple /tmp fs on md devices, seems more appropriate (and scalable) than poluting rc.conf(5) with a host of new options, As long as someone that is familiar with all the "cool" and more esoteric uses of `md' was consulted to ensure the framework is sufficiently capable. and avoids the mount_mdfs criticism leveled by phk that md is not an fs (which is true enough). If it looks like a duck, swims like a duck, quacks like a duck, -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall option for softupdates
On Sat, Mar 10, 2001 at 10:32:23PM -0800, Dima Dorfman wrote: Peter Wemm [EMAIL PROTECTED] writes: The version of the patch for -current uses the softdep mount option only. If you remove the mount option, you dont get softupdates. In this case, it might be better to just turn it on by default and let Problem is many still feel it should not be used on / . -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: swap-backed md-based /tmp to replace mfs-based one
On Mon, Mar 12, 2001 at 08:27:54PM +0100, Poul-Henning Kamp wrote: If it looks like a duck, swims like a duck, quacks like a duck, Sorry David, but it there is nothing duck-like about at all... From a user's stand point, it acts just like the old MFS when used to create a swap backed /tmp. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall option for softupdates
On Mon, Mar 12, 2001 at 05:12:13PM -0800, Dima Dorfman wrote: There's always the 'nosoftdep' mount option. It's also possible to enable it by default on everything except the root filesystem, but that's a [minor] POLA violation. I fail to see what is wrong with defaulting to `off'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: swap-backed md-based /tmp to replace mfs-based one
On Sun, Mar 11, 2001 at 03:11:09PM -0800, Kris Kennaway wrote: We really need to provide a better rc.conf hook for doing this -- expecting people to write their own script just to create a /tmp is lame. It should be a wrapper called mount_mdfs or mount_mfs so people upgrading can keep their /etc/fstab [mostly] the same. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall option for softupdates
On Sat, Mar 10, 2001 at 11:51:54AM -0800, Jordan Hubbard wrote: I think this is really the only place to do it, just to ease confusion. You also wouldn't need to put superblock-frobbing code into sysinstall, just bundle tunefs into the mfsroot. Why not add the softupdates option to newfs? Since newfs contains every tunefs option other than softupdates, I consider it a bug that newfs didn't gain that functionality when it was added to tunefs. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, Mar 09, 2001 at 01:39:58PM -0800, Matthew Jacob wrote: Erm, just so you know. The 4100 here at WC doesn't even make it past the SCSI probe due to interrupt issues. Hmm. Well, it *was* working a couple of days ago :-) Uh, actually _your_ 4100 is the only I've ever known to work on post-SMPng. The WC 4100 has *never* worked on post SMPng. I don't believe I've heard that DFR's runs SMPng either. I guess I should get a `dd' of your system disk, or get you a console on the WC box. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall option for softupdates
On Sat, Mar 10, 2001 at 09:06:20PM -0800, Peter Wemm wrote: I seem to recall Paul Saab has a set for both -current and -stable. Someone else also just posted a URL to a set of patches. Is Paul going to commit his, or can I take this on and commit the ones posted? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall option for softupdates
On Sat, Mar 10, 2001 at 09:51:46PM -0800, Dima Dorfman wrote: Are you talking about se's patches to make softdep a mount option, yes The former isn't something you can just drop in. You'd have to decide if softdep should be the default. It defaults to what tunefs sets it to -- POLA. If softdep isn't made the default, then those who do use softdep have to add "softdep" to the appropriate lines to /etc/fstab. From my understanding of the last discussion on this, both methods can live side-by-side -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tape device names and devfs
On Wed, Mar 07, 2001 at 08:50:23PM +1100, Bruce Evans wrote: dump.8 and dump(8) both refer explicitly to nsa0 and nrsa0 whereas sa0 and nsa0 are the actual device names in -current. The dump sources also refer to only the 'r' devices (_PATH_DEFTAPE is still "/dev/rsa0"). Fixed. :-) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MFC of Perl 5.6?
On Wed, Mar 07, 2001 at 06:33:09PM -0500, Forrest Aldrich wrote: I searched the archives, and found this question asked, but no responses. I wonder when (if) Perl 5.6 will be MFC'd to 4.x. ^^ Uh, _*WHY*_ are you sending this to freebsd-current rather than freebsd-stable where it is applicable??? BTW, you need to do a much better search. The reason is there are known bugs and issues in Perl 5.6.0, and it is expected 5.6.1 will be MFCed when it comes out. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More on system hangs ... IRQ related?
On Mon, Mar 05, 2001 at 01:01:23AM -0600, GH wrote: http://people.freebsd.org/~jhb/intr2.patch has fixed my problems so far. This seems to be my luck: -- The file http://people.freebsd.org/~jhb/intr2.patch does not exist at this server. -- Where can I otherwise get this patch? John has committed it now. So you should be getting it soon in your usual way. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: well! That root didn't work! Let's try another!
On Sun, Mar 04, 2001 at 01:13:36PM -0800, Matthew Jacob wrote: This might also be the source of the 'going nowhere without my init' install failures that so plague alphas? No it is libdisk doing *err()* calls!! A library should *NOT* be exiting on its own. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More on system hangs ... IRQ related?
On Sun, Mar 04, 2001 at 11:42:22PM -0400, The Hermit Hacker wrote: Okay, are there any known problems with the SB128 cards? Figuring that it couldn't hurt to remove it, I did ... so far, X hasn't hung ... not Hum... interesting. I also have a PCI SB128 card and one hang when I was using mpg123 and then started a newfs. The SB128's IRQ isn't shared with anything else. But I was also having much hangs on heavy disk traffic. http://people.freebsd.org/~jhb/intr2.patch has fixed my problems so far. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getting a first build up and running?
On Sat, Mar 03, 2001 at 11:06:15AM -0800, George V. Neville-Neil wrote: I have a machine I want to use as a FreeBSD-Current machine since I want to work with some of the new features in 5.x that I require for a port (I'm ... The problem is that the machine is right now at 4.0-RELEASE. I've done a cvsup for current and am trying to build. You first want to CVSup to and `make world' to the latest RELENG_4. Then jump to -current from that. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make kernel failure: pecoff: machine/lock.h
On Tue, Feb 27, 2001 at 11:28:37AM -0800, John Baldwin wrote: Have you tried running make depend? I've got the same problem about a bogus dependancy on machine/lock.h. And yes, this is after a `make depend' on a /sys I *just* CVSup'ed. :-( -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dirty buffers on reboot again?
On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: login: (da0:ahc0:0:0:0): tagged openings now 16 ... syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up on 3 buffers ... I'm seeing a lot of this again. Anyone else? Yep. ahc controller also. By chance is that the commonality to this problem? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New GCC changes broken
On Sat, Feb 17, 2001 at 01:54:29PM +0100, Martin Blapp wrote: Do people test their changes ? warning: passing arg 1 of `unshare_all_rtl' from incompatible pointer type ... /usr/current/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/toplev .c:3828: too few arguments to function `unshare_all_rtl' *** Error code 1 Sounds like you CVSup'ed in between my import and fixing of conflicts. Please let me know if you still have problems. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, Feb 17, 2001 at 03:36:18PM -0800, Matthew Jacob wrote: One system got stuck in the current __sF bork... I'm not stuck with: One thing that may work is to set libc's version number in the Makefile to something that has never existed on your system. Try a `make world'. Move any /usr/lib/libc.so.5 to the side, and put the libc.so version number in the Makefile back to stock. Do another `make world'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: -current world broken since Feb 10
On Fri, Feb 16, 2001 at 10:44:10AM +0100, Stephan van Beerschoten wrote: DO NOT TRY TO UPGRADE -STABLE OR A PRE-FEB 10 -CURRENT TO A POST-FEB 10 -CURRENT UNTIL THIS IS RESOLVED. YOU HAVE BEEN WARNED. Any updates on this yet ? Warner committed a fix for this. But I'm having trouble building world with it. cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -DHESIOD -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/stdio/_flock_stub.c -o _flock_stub.o /usr/src/lib/libc/../libc/stdio/_flock_stub.c: In function `init_lock': /usr/src/lib/libc/../libc/stdio/_flock_stub.c:95: structure has no member named `_extra' /usr/src/lib/libc/../libc/stdio/_flock_stub.c: In function `_flockfile': /usr/src/lib/libc/../libc/stdio/_flock_stub.c:111: structure has no member named `_extra' ..snip.. Has anybody gotten world to build? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: -current world broken since Feb 10
On Fri, Feb 16, 2001 at 10:03:06AM -0700, Warner Losh wrote: Did you snag stdio.h as well? My buildworld on a virgin tree post my fix on a 4.2-stable system completed last night. My system was probably so hosed nothing was going to fix it. I backed up my sources to varisous dates and could not get a world to build. :-( I'm downloading a snapshot's bin.?? as I type this. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Wed, Feb 14, 2001 at 12:47:59AM +, Paul Richards wrote: Instead what we have now is libxyz.so.3 and libxyz.so.3 which are different from each other. No different than two libxyz.so.3.1 and libxyz.so.3.1 could be (a.out days). (well not entirely true, but in the a.out days, one could make a major change in the functionality of a lib routine w/o even a minor bump) If two libxyz.so.3 and libxyz.so.3 are incompatible, then a major shared version bump wasn't done when it should have been. When you login to a strange machine and you're trying to diagnose a problem there's no way to know whether the libc they've got installed is of version X or version Y because there's nothing to tell you what sources libc.so.Z was built from, it could be the .Z version with the X fixes or the Y fixes. When we had minor version numbers you still didnt' know if the X fixes or Y fixes were in it. You've missed the point I was trying to make. Our reluctance to bump what we perceive to be a major number is hampering our ability to differentiate between different versions. We aren't reluctant to bump in -STABLE if there is a need for it. The reluctance is in -CURRENT where we bump once and let that cover all the incompatibilities. We don't put our released version users thru the hoops we are willing to for the development version users. We could just as easily use a minor numbering scheme with Elf to indicate that a version change has occured but not an interface change. We only bumped due to interface changes in the .MAJOR.MINOR days. The difference is *adding* an interface today does in cause a bump. In the .MAJOR.MINOR days it would require a bump the MINOR number. In both days, an incompatible change in an existing interface require(s)(ed) a MAJOR bump. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Thu, Feb 15, 2001 at 11:14:38AM +, Paul Richards wrote: Commercial vendors will skip version numbers in their public releases if their internal development required more than one bump. Which ones? Sun Solaris still ships their libc as "libc.so.1", even in Solaris 8. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Thu, Feb 15, 2001 at 12:44:26PM +, Paul Richards_imap/mail.originative.co.uk/Inbox.sbd/New Mail.sbd/OpenLDAP.sbd/Devel wrote: I suggest you take a look at http://www.usenix.org/publications/library/proceedings/als2000/full_papers/browndavid/browndavid_html/ Yes, I know how Solaris does symbol versioning. FreeBSD does not have this technology today, so we cannot use it instead. The Linux way of doing this still has problems (see the Binutils mailing list). I'm waiting for the Linux way of doing this to fully settle and prove itself before I look at maybe using it for FreeBSD. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: ports/palm/pilot-link Makefile
On Thu, Feb 15, 2001 at 06:28:10PM +0900, Akinori MUSHA wrote: knu@archon[2]% uname -a FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Feb 14 16:49:24 JST 2001 [EMAIL PROTECTED]:/villa/work/obj/freebsd/src/usr/local/src/sys/ARCHON i386 knu@archon[2]% gcc --version 2.95.3 ...snip.. On the other hand, on another box it goes fine: knu@daemon[1]% uname -a FreeBSD daemon.local.idaemons.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 31 16:01:53 JST 2001 [EMAIL PROTECTED]:/var/work/world/usr/src/sys/DAEMON i386 knu@daemon[1]% gcc --version 2.95.2 I could **REALLY** use help from someone to pin point the problem. I just found out, I have very,very limited time to get needed FreeBSD changes into GCC 3.0, Binutils 2.11, and the way over-due 2.95.3. To test this, either compile and install the 2.95.3-test1 compiler on an updated RELENG_4 using the -CURRENT sources (just change /usr/src/contrib/gcc.295/config/freebsd.h to make __FreeBSD__=4 rather than "5". And/Or on a 5-CURRENT box showing the problem, back out the 2.95.3-test1 compiler by: cd /usr/src/contrib/gcc.295 cvs up -rBEFORE_GCC_2_95_3 cd /usr/src/gnu/usr.bin/cc cvs up -rBEFORE_GCC_2_95_3 make cleandir make cleandir make obj make all install -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major bumping of libFOO
On Wed, Feb 14, 2001 at 03:45:57PM -0700, Warner Losh wrote: Here's a patch that I think will fix the major breakage with major library versions. I haven't tried to build -current for a few days now. Can you summerize what breakage you are seeing? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Major bumping of libFOO
On Thu, Feb 15, 2001 at 12:32:33AM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] "David O'Brien" writes:
: On Wed, Feb 14, 2001 at 03:45:57PM -0700, Warner Losh wrote:
: Here's a patch that I think will fix the major breakage with major
: library versions.
:
: I haven't tried to build -current for a few days now. Can you summerize
: what breakage you are seeing?
The problem is that new libFOO.so.N have references to
__std{in,out,err}, instantly breaking all old binaries on the system.
Eg, libcam.so.2 used to have __sF, which as defined in libc.so.[345].
However, after the bump to lib.so.5.XXX and rebuild the world,
libcam.so.2 now references __std*. For apps that were linked before
against libc.so.[345], this causes undefined symbols at runtime.
I'm not happy about bumping every shared lib. Can you answer:
(1) does a ``make world'' will not work? Peter showed that we had no
choice with libc due to the use of the host's existing install programs.
(2) even if #1 works, will a 6mo. old binary (using one of these libs)
run w/o the change? Will a binary from 4.2-R run?
If this is just to keep one from having to reintall /usr/local/, I'm not
sure that is suffient reason for the bumpage.
Note that if you are going to bump shlib versions, you should follow the
libc.so versioning scheme.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter broken?
On Tue, Feb 13, 2001 at 04:00:26PM +0800, Donny Lee wrote: Dag-Erling Smorgrav wrote: ===ipfilter make: don't know how to make machine/lock.h Stop. *** Error code 2 Looks like a stale dependency file to me. Try 'make cleandir' twice, followed by the usual 'make depend make make install'. Yes, but got no luck, stops at the same place.:) cd /sys/compile/YOURKERNELFILE rm -rf modules make depend make To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter broken?
On Tue, Feb 13, 2001 at 05:18:04AM +0100, Dag-Erling Smorgrav wrote: Donny Lee [EMAIL PROTECTED] writes: ===ipfilter make: don't know how to make machine/lock.h Stop. *** Error code 2 Looks like a stale dependency file to me. Try 'make cleandir' twice, That only works in /usr/src userland, not kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter broken?
On Tue, Feb 13, 2001 at 11:15:24AM +0100, Dag-Erling Smorgrav wrote: "David O'Brien" [EMAIL PROTECTED] writes: On Tue, Feb 13, 2001 at 05:18:04AM +0100, Dag-Erling Smorgrav wrote: Donny Lee [EMAIL PROTECTED] writes: ===ipfilter make: don't know how to make machine/lock.h Stop. *** Error code 2 Looks like a stale dependency file to me. Try 'make cleandir' twice, That only works in /usr/src userland, not kernel. This is in a module build, and modules use the OBJDIR stuff so 'cleandir' had better work. Only if the kernel Makefile (which shells out a make on the modules Makefile), knows about the "cleandir" target. Remember where the cwd is for the person wanting to do this (assuming defaults). What you suggest will only work because I was forsitefull enough not that long ago to think that someone might actually try ``make cleandir'' and want something to happen. But ``make cleandir'' will only act in the modules build dir, it does not imply a `make clean' for the kernel. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Tue, Feb 13, 2001 at 04:24:00PM +, Paul RichardsF wrote: When we dropped minor numbers I had a worry that we'd run into one of Windows' greatest problems and we have. Applications that are developed and tested to work with a particular library might not work with a different version, How is that??? It is beter under ELF than a.out in that ld.so isn't making a guess as to which shared libs were compatible and which weren't. The ELF ld.so does not look for shared lib libxyz.so.2, find libxyz.so.3 and decide maybe they are close enough and use it instead. The a.out ld.so would use libxyz.so.2.2 when the binary was compiled and tested with libxyz.so.2.1. we're suffering a worst case scenario of this problem now but even "fixes" in new versions can cause applications to break and Don't confuse development (which in years past would have never made it out of the "company's" development machines, with deployed releases. we've already seen this many times in this iteration of -current. *Way*, way too many people are using -CURRENT that have no business doing so. I think we need some form of version control on libraries so that applications know whether they're linking with the version they're designed for and to be able to keep multiple versions around in the system so all applications continue to work. We have that today and it works very well [in our released product]. I understand the reasoning that Elf doesn't need minor numbers but they served an useful purpose in maintaining application compatibility that we now lack. NO! Please review the rules ld.so in both ELF and a.out varieties uses in finding a desired shared lib. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is -CURRENT in bad shape?
On Mon, Feb 12, 2001 at 01:20:36PM +0700, John Indra wrote: Now I'm in the middle of make -j10 buildworld. Is -CURRENT in bad shape? First thing to do when you're having problems building world is to STOP using -j. If you aren't hitting a race condition, you won't get able to figure out what is wrong due to the interleaved output. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT is bad for me...
On Mon, Feb 12, 2001 at 02:19:36PM -0700, Warner Losh wrote: Changes of this magnitude require a bump of the major number, even though we've already done that in -current. It breaks nearly everything, including the upgrade path. How does it break the upgrade path from 4.x to 5.0?? 5.0 has a higher libc.so version than 4.2. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT is bad for me...
On Mon, Feb 12, 2001 at 04:20:04PM -0800, Alex Zepeda wrote: How is this more acceptable than bumping the major number? Are they really so precious that they can only be incremented once for a release cycle? Yes. I don't want to be in a position where we wonder what happened to libc.so.5 when I don't see it in my /usr/lib/ or /usr/lib/compat/ Seems to me that a new major number is far cleaner than a gross hack. I am very against this. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT is bad for me...
On Mon, Feb 12, 2001 at 01:42:16PM -0800, Alex Zepeda wrote: Yup, I agree here. IMO so many things depend on the stdio bits, that a major number increase would have been desireable. So far, bzip2, pine/pico, GNU make, the GNU i18n stuff, fetchmail all needed to be rebuilt. Bumping the major number would at least allow these a stay of execution. /usr/ports is *very* easy to use. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Tue, Feb 13, 2001 at 01:48:33AM +0100, Dag-Erling Smorgrav wrote: Peter will likely commit a patch sometime soon. I am hoping it is posted for discussion to -arch before commit (so we get this right). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: installworld gotchas
On Sun, Feb 11, 2001 at 04:44:21PM -0800, Matt Dillon wrote: This is a major change to libc. The library maj must be bumped if you intend to change the sizeof(FILE), or every single third party application that uses stdio will break. For -stable this would be true. We've already done the bump in -current. -current users are expected to be able to work themselves over this huddle. Alternately, we should add symbol versioning to our shared libs like Solaris does. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: installworld gotchas
On Mon, Feb 12, 2001 at 11:47:04AM -0500, Garrett Wollman wrote: However, this may turn out to be so painful that we need to bump it again. That is (1) against Handbook documented policy, (2) too hackish (we aren't Linux). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 04:33:26PM -0800, Alex Zepeda wrote: How about this? :^) Because bumping the shared version again needs *DISCUSSING*. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 05:09:19PM -0800, Peter Wemm wrote: I can deal with /usr/local and /usr/X11R6 recompiles, but when the installworld dies because the dynamic linked copy of /usr/bin/* in /tmp/XXX/* gets the /usr/lib/libc.so.5 clobbered and explodes, leaving a 100% totally screwed up system, then I begin to think we are doing something wrong. If it wasn't for that, I could deal with a /usr/local and /usr/X11R6/lib recompile. 100% agreed. Before doing this, can we put out a *HEADS UP* for people to NOT update their -current boxes for a day or two, and take a look at fixing the `make installworld' problem? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Tue, Feb 13, 2001 at 02:14:03AM +0100, Dag-Erling Smorgrav wrote: No, it doesn't, because you bumped the libc major. Set it to 500 like we discussedm, and commit (or I will, damnit). Uh, NO. It was discussed on IRC, NOT -arch. It needs to go there before doing something like this. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel threading: the first steps [patch]
On Sun, Jan 28, 2001 at 01:27:04AM -0800, Julian Elischer wrote: This is the single most flagrant lack of cooperation I have experienced while working with the FreeBSD Project. I'm truly dumbfounded. It's not a lack of co-operation.. it's a lack of communication. I didn't see an any lists that anyone was doing this yet and thought I'd get the ball rolling to promote discussion.. I'm dumfounded to discover that you've done work here already as I thought I'd have heard of it. We've been waiting on JHB's (and others) locking changes on the proc structure because those will do nothing but make conflicts in the patches jasone has already. Has JHB made all the proc changes he was going to? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 05:20:51PM -0800, Peter Wemm wrote: It avoids the current problem: - RELENG_4 bumped from 3.0 to 4.0 - this forced a premature 4.0-5.0 bump in -current Actually "NO". I bumped libc.so because Garret said he had changes ready for libc, but was waiting for someone to bump the shared version number. - we missed our chance for major changes. (!!!) In the past, once it was bumped, incompatable changes to libc.so were fair game for -CURRENT. If we had taken -current to 500, we could go to 501, 502, etc as required to stop killing our developers, and prior to entering 5.0-BETA we go back to the next sequentially available major number (be it 5, or 6 if RELENG_4 bumps again). /me wonders if we'll also do something about all the other things we do that kills our developers in -current.. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 06:21:58PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Peter Wemm writes: : Personally, I think we place far too much weight on the major number thing. : I think we should be allowed to bump it when the alternative is 'major pain' : to developers. The more I think about this, the more that I think that you are right. I'd go farther and also say that we won't produce a libcompat/libc.so.5.uu or any other "current only" libc versions. Huh?? We've never made a compat lib of a -current shared lib before. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 06:26:06PM -0700, Warner Losh wrote:
I don't see why we need only an increment of 1. What does this buy us
other than a minor warm fuzzy.
It is hackish.
OpenBSD bumps libc bunchs of times per release cycle (they are up to
libc.so.24 if my sources are current).
They do not always get things right...
Actually going from libc.so.500 to libc.so.{x500} is easy.
Copy libc.so.500 into /usr/lib/compat. When the libc.so link is made to
libc.so.{x500}, that is the lib version number that will get burned into
objects. After the first `make world', rm /usr/lib/libc.so.500.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 06:31:53PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Peter Wemm writes: : If we had taken -current to 500, we could go to 501, 502, etc as : required to stop killing our developers, and prior to entering 5.0-BETA we : go back to the next sequentially available major number (be it 5, or 6 : if RELENG_4 bumps again). I've had problems in the past going backwards on major versions of shared libaries. The major problem is that if I have binaries that refer to libc.so.503, then when the major number is reverted back to 5, it is a nop because ld will use libc.so.503 for new binaries. In the a.out days, yes. Are you sure you've seen this in the ELF days? What's wrong with shipping with say libc.so.505 in 5.0 and then say libc.so.645 in 6.0? HACK. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Tue, Feb 13, 2001 at 02:42:15AM +0100, Dag-Erling Smorgrav wrote: Warner Losh [EMAIL PROTECTED] writes: I've had problems in the past going backwards on major versions of shared libaries. The major problem is that if I have binaries that refer to libc.so.503, then when the major number is reverted back to 5, it is a nop because ld will use libc.so.503 for new binaries. When we back down to 5, we add magic to the Makefiles to move libc.so.5?? to /usr/lib/compat - that way they're only used when needed at runtime, not for linking new programs. NO! No magic. No polution. If you are using -current when libc.so.5003 exists, you should be able to handle the `mv' yourself manually. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Mon, Feb 12, 2001 at 05:44:53PM -0800, Peter Wemm wrote:
"David O'Brien" wrote:
Actually going from libc.so.500 to libc.so.{x500} is easy.
Copy libc.so.500 into /usr/lib/compat. When the libc.so link is made to
libc.so.{x500}, that is the lib version number that will get burned into
objects. After the first `make world', rm /usr/lib/libc.so.500.
There is no need to rm /usr/lib/libc.so.500 - once a new libc is installed,
The need is a clean, uncluttered /usr/lib/
and the symlink points to it, then libc.so.500 will *never* get linked
against.
Yes, I know. :-) But it is true that I didn't state that to make sure
others did.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)
On Tue, Feb 13, 2001 at 02:29:54AM +0100, Dag-Erling Smorgrav wrote: We can keep that bias by using temporary three-digit majors in -CURRENT and backing down to a single-digit major right before the first -RELEASE. In this specific case, we'd go from 5 to 500 or 501, Please read your -arch mail to discuss this issue. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: *_ROOT removed
On Wed, Feb 07, 2001 at 06:28:42AM -0800, Peter Wemm wrote: No, there wasn't one.. The commit message was pretty clear - You are reading them, right? We usually do HEAD UP's for stuff that will break people pretty badly or get them in trouble (eg: an unviable kernel if the instructions are not followed). I thought we did them for any issue that can confuse or cause a lot of questions on this list... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld failure as of 01-15-2001 @ 8:30 CST
On Mon, Jan 15, 2001 at 08:37:43AM -0600, Thomas T. Veldhouse wrote:
I just installed the FreeBSD 5.0-20010107-CURRENT snapshot and have cvsup'd
to the latest source (as of subject). Buildworld fails as below:
Do not manually do anything to get around this yet.
Please apply and try this patch. Report here, if it works or not.
Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.179
diff -u -r1.179 Makefile.inc1
--- Makefile.inc1 2000/12/03 20:29:31 1.179
+++ Makefile.inc1 2001/01/15 17:39:37
@@ -564,7 +564,7 @@
build-tools:
.for _tool in bin/csh bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \
-${_libroken4} ${_libkrb5} lib/libncurses ${_share}
+usr.bin/rpcgen ${_libroken4} ${_libkrb5} lib/libncurses ${_share}
cd ${.CURDIR}/${_tool}; ${MAKE} build-tools
.endfor
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld failure as of 01-15-2001 @ 8:30 CST
On Mon, Jan 15, 2001 at 12:36:34PM -0600, Thomas T. Veldhouse wrote: I must have left some relics around or something. I am getting a different error: No, I goofed. I'm getting my current test box back into shape so I can build a world before making stupid suggestions. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Atomic breakage?
On Mon, Jan 15, 2001 at 09:25:45AM +1100, Peter Jeremy wrote: Due to incompatibilities between __asm in different versions of gcc, several different versions of various macros (and expansions) are necessary. Why is that?? The base, and *only* supported compiler for building kernels is GCC 2.95.x, period. GCC 2.8 and 2.7 support should be garbage collected. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: YES! laptop installing
On Thu, Jan 11, 2001 at 11:41:17PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Mark Murray writes: : My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy : MAC address, and then doesn't work. It doesn't even go UP. : : MAC=00:00:80:00:00:80, FWIW. There's about 4 different dc based cards that don't work because they don't get the nic address right. Well, that's what I think. Use an /etc/start_if.dc0 script that uses `ifconfig' to set the eithernet address. wpaul show me how to find mine, and I just put in the start_if.dc0 and forget about it. :) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall.8 Breaking buildworld
On Thu, Jan 11, 2001 at 02:38:55PM -0800, John Baldwin wrote: Erm, sysinstall can be used as a replacement for fdisk and disklabel, both of which are in /sbin. In fact, in 4.2 the only tool you can realistically use to splat a virgin disklabel onto a slice w/o weird hoop jumping that isn't documented _is_ sysinstall. disklabel should have that fixed by 4.3, however. But disklabel/fdisk can't even accept MB's as a unit. Until they grow the functionality of the NetBSD and OpenBSD versions of them, sysinstall is really the only tolerable disk label manipulation tool our users have. This includes those with a bummed /usr that needs to install a new disk to get it back. On Thu, Jan 11, 2001 at 02:22:23PM -0800, Peter Wemm wrote: Personally I would prefer it in src/usr.sbin/sysinstall and have it dynamically linked. That would be OK, *once* our fdisk/disklable grows some modern [heck even late 1990's] user interface. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall.8 Breaking buildworld
On Thu, Jan 11, 2001 at 02:22:23PM -0800, Peter Wemm wrote: I won't argue - move away! Just have one of the CVSmeisters do it as a repo-copy, of course. We cannot repo-copy it to src/sbin - there is a copy there already. We could blow the old one away and lose the history (RELEASE_2_0 and earlier) but I guess that is no big deal these days. It wouldn't be that much history (how about moving /home/ncvs/src/sbin/sysinstall/Attic to /home/ncvs/src/sbin/sysinstall/Old to preserve it??) Unfortuneatly in those days repo copies weren't done as well as now. :-(( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy bikesheds
On Thu, Jan 11, 2001 at 03:00:35PM -0800, Doug Barton wrote: Since this post actually has some content I'm moving it to -current. On Thu, 11 Jan 2001, Warner Losh wrote: I agree. RO / is absoultely *REQUIRED* for our application. As stated, all concerned are sympathetic to that. This is why it's configurable. Not really -- specifying /var as the home of these files will not work very well (as you even show why below). So things *appear* to be configurable, but aren't. The good thing about this ridiculous thread is that the next time someone asks me if I've read the code, I can simply respond with, "No one reads the code for my projects, even when I include the cvsweb links in my head's up mail, so why should I be bothered?" I *did* read the diff you committed. So don't use that on me. ;-) Do YOU Yahoo!? Yep! -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release still broken...
On Tue, Jan 09, 2001 at 09:11:20AM +0100, Poul-Henning Kamp wrote: === rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Let me start a release. This means rpcgen has been using /usr/libexec/cpp which is *only* for the compiler's use. rpcgen should have been using /usr/bin/cpp all this time. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Tue, Jan 09, 2001 at 02:04:05PM -0800, Peter Wemm wrote: We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. RELENG_4 and -current are the same in this reguard. I should bump __FreeBSD_version in both and then people can use that as the cut over date. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Wed, Jan 10, 2001 at 02:20:01AM +0200, Maxim Sobolev wrote: Yes, I know it's possible, but to provide a hack in one place istead of 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is much easier both in the terms of efforts and testing required. After all, it would only cost us one inode for symlink and probably two-three lines in appropriate Makefile. The answer is "NO". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: missing THREAD_UNLOCK in libc?
On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote: A program that previously worked (-current of November) with -pthread now fails with an abort and a " in free(): error: recursive call" warning. I need a copy of this program (source form) to test with. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** HEADS UP ** world build known broken
The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I suspected. I've got to head to an appointment, so the world will be broken for a little while. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** world build known broken
On Wed, Jan 03, 2001 at 10:26:30AM -0800, David O'Brien wrote: The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I suspected. I've got to head to an appointment, so the world will be broken for a little while. World should be buildable again. Quite sorry for the longer than expected delay, I'm not happy how long I took. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.
On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote: like either you or David O'Brien (I'm guessing, your guys names are I will fix it today. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is compatibility for old aout binaries broken?
On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote: The other day, on a whim, I decided to try running an old binary of SimCity (the same one found in the 'commerce' directory on many FBSD cds), and it failed in a odd way... Does anyone have any old a.out binaries other than SimCity that they have problems with? I've installed the SimCity package, compat20 and compat21 dists, but cannot get it to run: Starting SimCity ... SimCity Classic - UNIX / Tcl Tk Toolkit version 3.6b - Mattes Adding a player on dragon:0.0 ... Display Visual = truecolor Display Depth = 24 SimCity can't find an 8 bit color or 1 bit monochrome display on "dragon:0.0". SimCity: error in TCL code: bad window path name ".head0" -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is compatibility for old aout binaries broken?
On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote: This has been broken for new users for some time. :-( Those of us upgrading from source have been immune to this problem, because we retain the old a.out ld.so binary. /usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib /aout/libX11.so.6.1 at 0x20160644 When errno became a function that returns a pointer (previously it was a simple integer variable), recompiled libraries became incompatable with old binaries. So, I hacked the a.out loader (ld.so). The fix was in 3.0. Well, Nate called it a horrible hack, so maybe I should say "the hack was in 3.0". src/lib/libc/sys/__error.c suggests this was the case for 2.2.7+. What is out of sync is the X11 a.out libs. They are probably built on a 2.2.7 or 2.2.8 box, thus they refer to `___error' vs. `errno'. These libs are wrong for the SimCity binary. They are a.out yes, but not proper for compat20 use. Since SimCity needs `libgcc.so.261', I'll assume it was built that long ago. The problem isn't as much ld.so, as it should match the libc.so, et.al. you are using from the compat2[01] dist (needed to satisfy ``ldd lib/SimCity/res/sim''). And `ld.so' and the shared libs would be consistent on the system the a.out program was built on. What I would feel most comfortable with, is doing a MFC to RELENG_2_2 of the rtld-aout changes since then, building a new `ld.so' and putting that in the compat2? dists. Problem is I don't have access to a 2.2-STABLE box. I poked about with my old FreeBSD CD collection and found that version 3.0 through 3.2 have a fully functioning (fully hack enabled) ld.so, but an older binary has been substituted in 3.3 and onward, including 4.0 and 4.1, and most likely 4.2 also. Are you sure? src/lib/compat/compat2[012]/ld.so.gz.uu are all at rev 1.1. So there has been no change to them over the lifetime of their existence. All three are identical -- having the same MD5 checksum. Well, looking at the release tags compat22/ld.so was in 3.2. compat2[01]/ld.so was added for 3.3. I can only guess that some anonymous release engineer (nobody we know :-) picked the wrong CD at some point to get the master copy of ld.so once it stopped compiling. (Or at least stopped being easily compiled.) Not quite. I seem to remember that JKH was makeing a tarball of a.out libs from what ever was on his box at the time (thus probably the last a.out ld.so just before E-day on 3-CURRENT). When I committed the compat2? bits, I took ld.so from a 2.2.x release as this is the compat2? dist, not compat3.aout dist. Which is what you're suggesting should have been done. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is compatibility for old aout binaries broken?
On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote: Looks like you got a lot farther than I did with it... Are you sure you don't have an old aout ld.so on that machine? Nope. This is a box that was a virgin install of 5-CURRENT a month ago. I had to install the compat20 and compat21 dists, along with doing a ``pkg_add -r XFree86-aoutlibs''. The Tk is 8.0.5. Here's what I get: dmaddox SimCity Starting SimCity ... SimCity Classic - UNIX / Tcl Tk Toolkit version 3.6b - Mattes /usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644 Actually you're probably getting farther than I am. I believe I'm bombing so early in starting Tk, I'm not really getting to the point you are. What does `ldd /usr/local/lib/SimCity/res/sim'' report? Also, it looks to me like SimCity would probably run just fine for you if you started X on an 8-bit display... Maybe, but I'm not going to dink with my X server config. ;-) Mabye I'll try to find another box to try this on. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is compatibility for old aout binaries broken?
On Wed, Dec 20, 2000 at 05:09:45AM -0500, Donald J . Maddox wrote: res ldd sim sim: -lXext.6 = /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000) -lX11.6 = /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000) -lc.2 = /usr/lib/compat/aout/libc.so.2.2 (0x20166000) -lm.2 = /usr/lib/compat/aout/libm.so.2.0 (0x201cb000) -lgcc.261 = /usr/lib/compat/aout/libgcc.so.261.0 (0x201e5000) res Looks good. Can you install the XFree896-aoutlib port? You may have seen were someone posted the a.out libs from 3.3.6 are known to not be the the best to use for compatibility use. Heh :) You don't have to dink around with your config... Just do 'startx -- -bpp 8'. You assume I'm using an XFree86 server ;-) -- I am not. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is compatibility for old aout binaries broken?
On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote: Correcting slightly for your slightly off assumption: The X11 libs were probably built on a 3.x box. Their problem is that being newer than libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not supply it. My patches to rtld-aout (that first appeared in FreeBSD 3.0) supply ___error in this case. This is the only full fix for this situation. Why is not changing the XFree86-aoutlibs port to offer libs built on 2.2.x not the right fix? Emphasis again: the workaround ld.so was only found in 3.0 and onward, so just using a 2.2.x ld.so isn't enough. I am very uncomfortable putting in a ld.so built on 3.0 into the compat2? dists. I'm painfully aware of all the un-thought of issues that can come up when changing dynamic linking methods, etc.. just look at the two opposing threads in the past month about how to handle libcc and dynamic [and threaded] libs and binaries. In fact, I think we should build ld.so from source until such time as a.out building capability is removed (5.0 perhaps). Fine BUT IT ISN'T compat2?. PLEASE think about the issues for a moment. You are mixing bits that are not consistent. Maybe it fixes this one case, but what about all the other cases. What we need to do is offer a.out bits so users can duplicate the system the binary was built on. 4.2 a.out bits != 2.2.x a.out bits. There are two issues here -- binary format (a.out vs. ELF), _and_ library versions. On the other hand, merging back to 2.2.x and rebuilding should provide a working (and hack enabled) ld.so that has no more problems than the old binaries it is supporting. And is consistent with the binaries and libs of that release. Are you sure? src/lib/compat/compat2[012]/ld.so.gz.uu are all at rev 1.1. So there has been no change to them over the lifetime of their existence. All three are identical -- having the same MD5 checksum. Well, looking at the release tags compat22/ld.so was in 3.2. compat2[01]/ld.so was added for 3.3. This very fact is bothering me a lot. Get out your 3.2 disks and verify that they do not match these uuencoded binaries. Check the 3.0 and 3.1 disk 2 (live file system) and see that they don't match them either. I'm sure they don't -- I just wrote above I didn't add ld.so to the compat2? dists until 3.2 and 3.3. So of course the 3.0 and 3.1 a.out bits are different. You missed the fact that fixes were added to ld.so after those releases even though the purpose of ld.so is to run binaries that date from those releases. The existence of later, recompiled libraries requires this. No, you're missing the fact that these are comat2? bits, not a.out bits. If you want 3.x a.out bits then a compat3x.aout dist should be created. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
