From owner-freebsd-arch Sun Aug 26 0:20: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 936C037B409 for ; Sun, 26 Aug 2001 00:19:58 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id AAA67118; Sun, 26 Aug 2001 00:36:07 -0700 (PDT) Message-ID: <3B88A229.C07CCBB4@elischer.org> Date: Sun, 26 Aug 2001 00:15:53 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 Cc: "bsd-api-discuss@wasabisystems.com" Subject: Re: changes to BSD APIs for THREADS support References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Todd Vierling wrote: > > On Sat, 25 Aug 2001, Julian Elischer wrote: > [Note: I'm not a Solaris weenie; in fact, I really don't like Solaris much > at all. However, I have cited it several times below, mostly because it's > already traveled down all these roads successfully where we are treading > anew.] > > : how does PS extract state from the kernel when a process is simultaniously in > : several states? > > : Which wmesg is shown if there are 8 sleeping threads? > > I'd presume that the only useful way to deal with this is to provide > per-thread info in a ps display. Solaris may be one possible prior art to > look at (particularly with a multithreaded process under their compatibility > /usr/ucb/ps). the question as far as interfaces is to decide whether in a copy of ps being run with the 'threaded' option not set (in solaris the "-L" option) whether the ps goes the same as it does now and gets just process info, and the kernel agregates that for it, or it always looks for thread info and agregates it itself and then only displays the totals. for procfs there is no choice.. the kernel does it, but procfs must always show all the information, so how would we show this information in the procfs hierarchy? /proc/curproc/threads/12332/status /proc/curproc/lwps/1234/status? > > : What does "%cpu" actually indicate? > > There's two components to this. > > * Whether 100% = 1 CPU or 100% = all CPUs; > > * What to show for a process without expanding the individual threads in a > display. > > Personally I prefer that 100% = all CPUs, but that's my take. Other prior > art may be in Solaris /usr/bin/ps and /usr/ucb/ps for this. I looked at the man pages but haven't got the answer there. I'd like to see one in action.. > > : Inside the kernel, how are the proiority adjustments calculated when > : a process might be running and sleeping at the same time? > > Process priorities are a really implementation-specific concept, as a > "complete" threading subsystem will have more complex scheduling than simple > priorities (for RT ability) and multi-level scheduling (for limiting time > allocation to all threads within a process and/or for honoring CPU affinity > requests). So there's no real way to provide a standard for this. We have a cunning plan... well we're covering it.. see the KSE doc at http://www.freebsd.org/~jasone for some starter information. > > What's displayed to the user via ps or top isn't all that important > otherwise; it might as well be a formula averaging the threads' priorities > or somesuch, appropriate for the particular threading implementation. > > : How does ^T decide what thread/proc to report? > > Again, we might see if Solaris provides decent prior art with its LWPs. It's not that important but it's one of the points I encountered while threading the FreeBSD kernel that really I had to 'kludge' because I couldn't figure out what the right answer is.... > > : All this is separate to what syscalls we will be wanting to add to > : actually give the multithreading libraries access to the new kernel > : support. > : > : On that front FreeBSD is looking at at least 4 new syscalls. > : I'm going to describe them by function rather than name as the names are > : not decided: > : > : 1/ Add a new kernel schedulable entity (KSE). > > I'm using the term "kernel thread" below, to define it as a thread of > program flow scheduled by the kernel. It's less confusing to me, but only > because of prior experience with kernel-scheduled threading. 8-) Ahhhh but you see in this world a KSE and a thread are two different things... A KSe is similar I thinkl to a schedular activation in the landmark SA paper that is being implemented in NetBSD. A thread is the short term line of execution that enters the kernel, and might block.. it's saved to one side, and hte KSE continues on by upcalling to the Userland scheduler, and asking for more work. > > : 2/ A yield() call which tells the kernel that the user thread scheduler has no > : present use for the current processor and it may be used by another process. > > By this I presume that you're talking about some sort of many-to-one > userland thread scheduler? well, yes, I agree that the win isn't neccesarily that great, but we're going to try it out.. > > You might want to know that, after some personal conversation with Solaris > developers at USENIX, they've decided that a two-level (userspace plus > kernelspace) thread system is actually more overhead than it is worth and > will be phasing it out in future releases. It turns out that reusing the > existing context switch code available in the kernel is simpler and faster > than jumping around with the userland scheduler's setjmp/longjmp-alike. I have a cunning plan sire.. (again) We have a scheme that simplifies this tremendously. if it works it'll make things so simple that it won'e be much overhead at all. > > I believe that the forthcoming NetBSD implementation also will leave > scheduling entirely to the kernel, but the person in charge of writing it > would know better than I.... No, actually as an SA (Scheduler activations) implememtnation it has a userland scheduler in control. (If not then ist isnt an SA implementation) > > : 3/ A call that can be used by the user thread scheduler to 'unyield' > : a previously yielded processor. i.e. it could do with it, now, if it's > : available. > > Unyield a processor, or a kernel thread? What it sounds like you're > proposing here is to combine processor affinity and kernel thread > pause/resume actions into one group. The Scheduler activation is released from the processor. One KSE can run many threads.. It's a kind of CPU reservation on behalf of the user thread scheduler. if the UTS doesn't need it it needs to release the reservation. > > Processor affinity should really be separate from the operation of kernel > threads. To define the differences, a kernel thread should be able to run > on any available processor by default, but can be set to prefer a specific > CPU or CPU group. CPU-specific operation is available as a subset of the > available operations in this arrangement. threads can run on any KSe they are allowed to. and KSEs MIGHT be linked to certain processors. > > : 4/ A call by which a KSE suicides.. It will never return > : and the #1 frame (upcall frame) associated with this KSE will never be used > : again and can be freed. > > AKA a kernel thread exit point; normal. yep > > : 5/ It is possible that we may need a call by which the user thread scheduler can > : 'cancel' the syscall that a particular kernel thread is currently operating > : on. (particularly if it is waiting). > > Solaris also has a way to do this, but I don't remember what it is off the > top of my head. It is kind of the bottom end of what happens now when a signal is delivered to a process that is in the kernel. Except now it is a thread. All the same logic should remain pretty much untouched. > > : In addition there may be the need for one or two synchronisation primatives > : though this is not certain. > > NetBSD will require kernel-level synchronization primitives as a fallback, > because not all processors NetBSD supports have atomic instructions. I don't think FreeBSD has the 4004 as a target architecture. (Isn't there a MIPS like that?) > > There's one more thing having serious interactions with threads that should > be addressed: > > Multithreaded process signal delivery. There's an intricate way that this > is handled in Solaris, as "async signals". More prior art that's probably > worth imitating for code compatibility's sake. I covered this in another email > > -- > -- Todd Vierling * Wasabi NetBSD: Run with it. > -- NetBSD 1.5.2 available on CD-ROM soon! -- http://www.wasabisystems.com/ -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 8:50:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5AD4537B40A for ; Sun, 26 Aug 2001 08:50:44 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA09918; Sun, 26 Aug 2001 11:49:49 -0400 (EDT) Date: Sun, 26 Aug 2001 11:49:47 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "bsd-api-discuss@wasabisystems.com" , Arch@FreeBSD.ORG Subject: Re: changes to BSD APIs for THREADS support In-Reply-To: <3B885ED0.9DFCA5B5@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 25 Aug 2001, Julian Elischer wrote: > > On that front FreeBSD is looking at at least 4 new syscalls. > I'm going to describe them by function rather than name as the names are > not decided: How do we create and destroy new KSE Groups? Is that just an option to creating a new KSE? I assume we'll also eventually have a method of [sg]etting the priority and scheduling class of a KSE Group. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 11:39:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 03EF537B409 for ; Sun, 26 Aug 2001 11:39:41 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA69261; Sun, 26 Aug 2001 11:52:27 -0700 (PDT) Message-ID: <3B89408C.54CCB390@elischer.org> Date: Sun, 26 Aug 2001 11:31:40 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Daniel Eischen Cc: "bsd-api-discuss@wasabisystems.com" Subject: Re: changes to BSD APIs for THREADS support References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Daniel Eischen wrote: > > On Sat, 25 Aug 2001, Julian Elischer wrote: > > > > On that front FreeBSD is looking at at least 4 new syscalls. > > I'm going to describe them by function rather than name as the names are > > not decided: > > How do we create and destroy new KSE Groups? Is that just an option > to creating a new KSE? yes > > I assume we'll also eventually have a method of [sg]etting the priority > and scheduling class of a KSE Group. My current thought on that is that the current process priority calls, when applied to the current process will apply to the calling ksegrp.., > > -- > Dan Eischen -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 13:15: 7 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 3806437B40B for ; Sun, 26 Aug 2001 13:15:03 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA46406; Sun, 26 Aug 2001 13:10:07 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f7QKA6f28508; Sun, 26 Aug 2001 13:10:06 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200108262010.f7QKA6f28508@arch20m.dellroad.org> Subject: Re: changes to BSD APIs for THREADS support In-Reply-To: <3B885ED0.9DFCA5B5@elischer.org> "from Julian Elischer at Aug 25, 2001 07:28:32 pm" To: Julian Elischer Date: Sun, 26 Aug 2001 13:10:06 -0700 (PDT) Cc: arch@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer writes: > 5/ It is possible that we may need a call by which the user thread > scheduler can 'cancel' the syscall that a particular kernel thread > is currently operating on. (particularly if it is waiting). I think this is going to be required. The UTS needs to have the ability to cancel a thread at any time. If the thread is in userland then it can just do it; otherwise it needs a way to wake up the thread in the kernel. The thread's syscall should then return immediately with EINTR or somesuch; alternately, the thread can just never return. Mabye both options would be good to have. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 13:39:27 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 3509237B403 for ; Sun, 26 Aug 2001 13:39:24 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA69706; Sun, 26 Aug 2001 13:58:03 -0700 (PDT) Message-ID: <3B895DF7.709DB10C@elischer.org> Date: Sun, 26 Aug 2001 13:37:11 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Archie Cobbs Cc: arch@freebsd.org Subject: Re: changes to BSD APIs for THREADS support References: <200108262010.f7QKA6f28508@arch20m.dellroad.org> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Archie Cobbs wrote: > > Julian Elischer writes: > > 5/ It is possible that we may need a call by which the user thread > > scheduler can 'cancel' the syscall that a particular kernel thread > > is currently operating on. (particularly if it is waiting). > > I think this is going to be required. The UTS needs to have the > ability to cancel a thread at any time. If the thread is in userland > then it can just do it; otherwise it needs a way to wake up the > thread in the kernel. The thread's syscall should then return > immediately with EINTR or somesuch; alternately, the thread can > just never return. Mabye both options would be good to have. the mechanics are the same as for the current code that aborts a syscall when a signal is sent to the process, except that the method of finding the sleeping party to unblock is slightly different. The syscall returns just like the current one would until it reaches the kernel boundary. (it needs to unlock and free anything it may have locked or allocated on the way in). At the boundary we can just let it report a failure. The UTS can then cancel it. > > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 14:55: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 73F4337B406 for ; Sun, 26 Aug 2001 14:55:03 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.135.64.Dial1.SanJose1.Level3.net [209.245.135.64]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA03576; Sun, 26 Aug 2001 14:54:55 -0700 (PDT) Message-ID: <3B89705A.A6EABECB@mindspring.com> Date: Sun, 26 Aug 2001 14:55:38 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Archie Cobbs , arch@freebsd.org Subject: Re: changes to BSD APIs for THREADS support References: <200108262010.f7QKA6f28508@arch20m.dellroad.org> <3B895DF7.709DB10C@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > Archie Cobbs wrote: > > Julian Elischer writes: > > > 5/ It is possible that we may need a call by which the user thread > > > scheduler can 'cancel' the syscall that a particular kernel thread > > > is currently operating on. (particularly if it is waiting). > > > > I think this is going to be required. The UTS needs to have the > > ability to cancel a thread at any time. If the thread is in userland > > then it can just do it; otherwise it needs a way to wake up the > > thread in the kernel. The thread's syscall should then return > > immediately with EINTR or somesuch; alternately, the thread can > > just never return. Mabye both options would be good to have. > > the mechanics are the same as for the current code that aborts a > syscall when a signal is sent to the process, except that the > method of finding the sleeping party to unblock is slightly different. > > The syscall returns just like the current one would until it > reaches the kernel boundary. (it needs to unlock and free anything > it may have locked or allocated on the way in). At the boundary > we can just let it report a failure. The UTS can then cancel it. Julian, are you talking about EINTR handling (Archie's last sentence), or are you talking about his whole statement? If you are talking about his whole statement, I have to side with Archie: a blocking O_EXCL open on something like a modem would never be interruptable, without the ability to explicitly abort the system call as part of aborting/EINTR'ing the thread currently blocked on the call's completion. With POSIX signal handling, it's not like alarm(2) will do the right thing, as it would on a non-threaded program, and cause the call you want interrupted to properly return EINTR. I rather expect that you would have to establish a timer, take the signal on a particular thread (personally, I would suggest that whatever thread has registered a handler for a signal be chosen for delivery, over all other threads), and then re-throw the signal using pthread_kill or whatever. The EINTR would have to come from the interrupted call in the pthread_kill'ed thread. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 15:39:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id F132037B407 for ; Sun, 26 Aug 2001 15:39:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA70165; Sun, 26 Aug 2001 15:45:38 -0700 (PDT) Message-ID: <3B897729.FF577A21@elischer.org> Date: Sun, 26 Aug 2001 15:24:41 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: Archie Cobbs , arch@freebsd.org Subject: Re: changes to BSD APIs for THREADS support References: <200108262010.f7QKA6f28508@arch20m.dellroad.org> <3B895DF7.709DB10C@elischer.org> <3B89705A.A6EABECB@mindspring.com> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Julian Elischer wrote: > > Archie Cobbs wrote: > > > Julian Elischer writes: > > > > 5/ It is possible that we may need a call by which the user thread > > > > scheduler can 'cancel' the syscall that a particular kernel thread > > > > is currently operating on. (particularly if it is waiting). > > > > > > I think this is going to be required. The UTS needs to have the > > > ability to cancel a thread at any time. If the thread is in userland > > > then it can just do it; otherwise it needs a way to wake up the > > > thread in the kernel. The thread's syscall should then return > > > immediately with EINTR or somesuch; alternately, the thread can > > > just never return. Mabye both options would be good to have. > > > > the mechanics are the same as for the current code that aborts a > > syscall when a signal is sent to the process, except that the > > method of finding the sleeping party to unblock is slightly different. > > > > The syscall returns just like the current one would until it > > reaches the kernel boundary. (it needs to unlock and free anything > > it may have locked or allocated on the way in). At the boundary > > we can just let it report a failure. The UTS can then cancel it. > > Julian, are you talking about EINTR handling (Archie's last > sentence), or are you talking about his whole statement? > > If you are talking about his whole statement, I have to side > with Archie: a blocking O_EXCL open on something like a modem > would never be interruptable, without the ability to explicitly > abort the system call as part of aborting/EINTR'ing the thread > currently blocked on the call's completion. I think you are getting a little carried away here.. Basically any sleeping kernel thread must be cancelable. When it is cancelled it must free any resources it has. To do this it needs to rewind through it's stack to the user boundary. When it reaches there, we can do what ever we want with it.. My suggestion is that we report a 'cancelled' state back to the UTS, and let it decide what to do (restart it, erase the whole userland thread, whatever). This is the same mechanism as used by the current code to abort a syscall when a signal is caught (kill -9 should abort most syscalls). the actual code returned is probably neither EINTR or ERESTART or anything, but probably a code specific to the KSE environment. Signals are a whole different topic. They are delivered on the next upcall to any KSE within the process. The UTS is notified of the signals , and can do what it likes with them, including ignoring them, or passing them o a particular thread, or even starting a separate thread to handle them. That is the UTS's perogative. > > With POSIX signal handling, it's not like alarm(2) will do the > right thing, as it would on a non-threaded program, and cause > the call you want interrupted to properly return EINTR. I > rather expect that you would have to establish a timer, take > the signal on a particular thread (personally, I would suggest > that whatever thread has registered a handler for a signal be > chosen for delivery, over all other threads), and then re-throw > the signal using pthread_kill or whatever. The EINTR would > have to come from the interrupted call in the pthread_kill'ed > thread. you are being too specific here. That's all the UTS's decision. > > -- Terry -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 20: 1:54 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A60037B407 for ; Sun, 26 Aug 2001 20:01:50 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA29536; Sun, 26 Aug 2001 23:00:58 -0400 (EDT) Date: Sun, 26 Aug 2001 23:00:58 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: tlambert2@mindspring.com, Archie Cobbs , arch@FreeBSD.ORG Subject: Re: changes to BSD APIs for THREADS support In-Reply-To: <3B897729.FF577A21@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 26 Aug 2001, Julian Elischer wrote: > Terry Lambert wrote: > > > > Julian Elischer wrote: > > > Archie Cobbs wrote: > > > > Julian Elischer writes: > > > > > 5/ It is possible that we may need a call by which the user thread > > > > > scheduler can 'cancel' the syscall that a particular kernel thread > > > > > is currently operating on. (particularly if it is waiting). > > > > > > > > I think this is going to be required. The UTS needs to have the > > > > ability to cancel a thread at any time. If the thread is in userland > > > > then it can just do it; otherwise it needs a way to wake up the > > > > thread in the kernel. The thread's syscall should then return > > > > immediately with EINTR or somesuch; alternately, the thread can > > > > just never return. Mabye both options would be good to have. > > > > > > the mechanics are the same as for the current code that aborts a > > > syscall when a signal is sent to the process, except that the > > > method of finding the sleeping party to unblock is slightly different. > > > > > > The syscall returns just like the current one would until it > > > reaches the kernel boundary. (it needs to unlock and free anything > > > it may have locked or allocated on the way in). At the boundary > > > we can just let it report a failure. The UTS can then cancel it. > > > > Julian, are you talking about EINTR handling (Archie's last > > sentence), or are you talking about his whole statement? > > > > If you are talking about his whole statement, I have to side > > with Archie: a blocking O_EXCL open on something like a modem > > would never be interruptable, without the ability to explicitly > > abort the system call as part of aborting/EINTR'ing the thread > > currently blocked on the call's completion. > > I think you are getting a little carried away here.. > Basically any sleeping kernel thread must be cancelable. > When it is cancelled it must free any resources it has. > To do this it needs to rewind through it's stack to the user boundary. > When it reaches there, we can do what ever we want with it.. > My suggestion is that we report a 'cancelled' state back to the UTS, > and let it decide what to do (restart it, > erase the whole userland thread, whatever). This is the same > mechanism as used by the current code to abort a syscall when a > signal is caught (kill -9 should abort most syscalls). > the actual code returned is probably neither EINTR or ERESTART > or anything, but probably a code specific to the KSE environment. If the signal handler is installed with SA_RESTART, how does the UTS restart the thread after normal return of the signal handler (as opposed to when the thread longjmps out of the signal handler in which case the system call will never be restarted)? Does it save the context from just after being canceled in the kernel, and then munge it a bit to restart the system call again? Or is the context already restartable and it needs to be munged to bypass the system call (returning EINTR)? Can we tell the kernel what type of context to pass back based on whether SA_RESTART is set or not? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Aug 26 22:19:21 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id A22AA37B40C for ; Sun, 26 Aug 2001 22:19:09 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA71531; Sun, 26 Aug 2001 22:38:54 -0700 (PDT) Message-ID: <3B89D7F1.74D834C9@elischer.org> Date: Sun, 26 Aug 2001 22:17:37 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Daniel Eischen Cc: tlambert2@mindspring.com, Archie Cobbs , arch@FreeBSD.ORG Subject: Re: changes to BSD APIs for THREADS support References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Daniel Eischen wrote: > If the signal handler is installed with SA_RESTART, how does the > UTS restart the thread after normal return of the signal handler > (as opposed to when the thread longjmps out of the signal handler > in which case the system call will never be restarted)? well the signal will be delivered to the UTS as a pure notification. The UTS decides that it should be deliverd to thread (X). The UTS discoveres that thread (X) is suspended in the kernel. It sends a "cancel syscall" bomb to thread (X). Thread (X) returns to the user boundary. Here, we have two possibilities (A) the kernel stores the state of the thread as if it had finished the syscall. -or- (B) the kernel stores the state of the thread as if it was about to do the syscall. In either case, the UTS can compensate. to get the other case. The signal trampoline code is placed on the stack of the thread. The saved context is placed correctly in the trampoline code (as now). The signal is processed. The system call is either reported as failed, or re-done. (depending on what we chose to do) > > Does it save the context from just after being canceled in > the kernel, and then munge it a bit to restart the system call > again? Or is the context already restartable and it needs to > be munged to bypass the system call (returning EINTR)? Can > we tell the kernel what type of context to pass back based > on whether SA_RESTART is set or not? we could do it either way.. we could even make it an argument to the "cancel_syscall(thread, how)" syscall. Which ever you'd prefer.. > > -- > Dan Eischen -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Aug 27 5: 3:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id DD01837B403 for ; Mon, 27 Aug 2001 05:03:12 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA04895; Mon, 27 Aug 2001 08:02:22 -0400 (EDT) Date: Mon, 27 Aug 2001 08:02:22 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: tlambert2@mindspring.com, Archie Cobbs , arch@FreeBSD.ORG Subject: Re: changes to BSD APIs for THREADS support In-Reply-To: <3B89D7F1.74D834C9@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 26 Aug 2001, Julian Elischer wrote: > Daniel Eischen wrote: > > > If the signal handler is installed with SA_RESTART, how does the > > UTS restart the thread after normal return of the signal handler > > (as opposed to when the thread longjmps out of the signal handler > > in which case the system call will never be restarted)? > > well the signal will be delivered to the UTS as a pure notification. > The UTS decides that it should be deliverd to thread (X). > The UTS discoveres that thread (X) is suspended in the kernel. > It sends a "cancel syscall" bomb to thread (X). > Thread (X) returns to the user boundary. > Here, we have two possibilities > (A) the kernel stores the state of the thread as if it had finished the > syscall. > -or- > (B) the kernel stores the state of the thread as if it was about to do > the syscall. > In either case, the UTS can compensate. to get the other case. > The signal trampoline code is placed on the stack of the thread. > The saved context is placed correctly in the trampoline code (as now). > The signal is processed. > The system call is either reported as failed, or re-done. (depending > on what we chose to do) > > > > > Does it save the context from just after being canceled in > > the kernel, and then munge it a bit to restart the system call > > again? Or is the context already restartable and it needs to > > be munged to bypass the system call (returning EINTR)? Can > > we tell the kernel what type of context to pass back based > > on whether SA_RESTART is set or not? > > we could do it either way.. we could even make it an argument to > the "cancel_syscall(thread, how)" syscall. > > Which ever you'd prefer.. I like the latter. Having the UTS tell the kernel how to cancel the thread with an option to cancel_syscall like you show above. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Aug 27 20:19:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 6A47E37B401 for ; Mon, 27 Aug 2001 20:19:23 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA76848; Mon, 27 Aug 2001 20:27:50 -0700 (PDT) Date: Mon, 27 Aug 2001 20:27:49 -0700 (PDT) From: Julian Elischer To: Trent Nelson Cc: freebsd-arch@FreeBSD.org, dillon@earth.backplane.com Subject: Re: Paper detailing blocking heuristics based on Scheduler Activiations. In-Reply-To: <20010828110811.C1562@freebsd06.udt> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG thanks for the reference On Tue, 28 Aug 2001, Trent Nelson wrote: > > http://citeseer.nj.nec.com/28629.html > > I'd like to hear peoples' opinion on this research paper. It > details a method of using Scheduler Activations to support a new > form of synchronisation primitives. > > How applicable is their work (which was a natural progression from > Anderson, et. al.) to our current situation? Could their suggested > blocking heuristics be incorporated into our kernel threads? > > Matt, I've CC'd you specifically because of your post to -current > that expressed your concern with the current state of locking > primitives in -CURRENT; which got me thinking to post this in the > first place. Julian, well, you get CC'd for obvious reasons. > > Regards, > > Trent. > > -- > Trent Nelson - Software Engineer - nelsont@switch.aust.com > "A man with unlimited enthusiasm can achieve > almost anything." --unknown > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Aug 27 20:20:32 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8035C37B405 for ; Mon, 27 Aug 2001 20:20:30 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA76856; Mon, 27 Aug 2001 20:34:55 -0700 (PDT) Date: Mon, 27 Aug 2001 20:34:54 -0700 (PDT) From: Julian Elischer To: Trent Nelson Cc: freebsd-arch@FreeBSD.org, dillon@earth.backplane.com Subject: Re: Paper detailing blocking heuristics based on Scheduler Activiations. In-Reply-To: <20010828110811.C1562@freebsd06.udt> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ok so how do you get the actual paper? On Tue, 28 Aug 2001, Trent Nelson wrote: > > http://citeseer.nj.nec.com/28629.html > > I'd like to hear peoples' opinion on this research paper. It > details a method of using Scheduler Activations to support a new > form of synchronisation primitives. > > How applicable is their work (which was a natural progression from > Anderson, et. al.) to our current situation? Could their suggested > blocking heuristics be incorporated into our kernel threads? > > Matt, I've CC'd you specifically because of your post to -current > that expressed your concern with the current state of locking > primitives in -CURRENT; which got me thinking to post this in the > first place. Julian, well, you get CC'd for obvious reasons. > > Regards, > > Trent. > > -- > Trent Nelson - Software Engineer - nelsont@switch.aust.com > "A man with unlimited enthusiasm can achieve > almost anything." --unknown > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Aug 27 20:34:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 9F46537B405 for ; Mon, 27 Aug 2001 20:34:12 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f7S3XpW07303; Mon, 27 Aug 2001 20:33:51 -0700 Date: Mon, 27 Aug 2001 20:33:51 -0700 From: Brooks Davis To: Julian Elischer Cc: Trent Nelson , freebsd-arch@FreeBSD.ORG, dillon@earth.backplane.com Subject: Re: Paper detailing blocking heuristics based on Scheduler Activiations. Message-ID: <20010827203351.A6548@Odin.AC.HMC.Edu> References: <20010828110811.C1562@freebsd06.udt> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Mon, Aug 27, 2001 at 08:34:54PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 27, 2001 at 08:34:54PM -0700, Julian Elischer wrote: > ok so how do you get the actual paper? As with most citeseer entries, you can get it from the links at the upper right hand corner of the page. The cached copy has always worked for me and the other copy often works if the author hasn't moved. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ixEfXY6L6fI4GtQRApWeAJ9pnrAEjtYYjRTZXYk3SOne1XQs3gCcCuQr H2gjKh0vDAzbuVcPwgmgXZE= =yw0E -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 5:13:35 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 5AEAB37B403; Wed, 29 Aug 2001 05:13:23 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (dialup13-19.iptelecom.net.ua [212.9.229.19]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id PAA51088; Wed, 29 Aug 2001 15:13:01 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f7TCBSo60696; Wed, 29 Aug 2001 15:11:28 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B8CDC38.EC1EE32C@FreeBSD.org> Date: Wed, 29 Aug 2001 15:12:40 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Alexander Langer Cc: arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alexander Langer wrote: > Hi folks! > > You probably followed the arch-mailinglist. > > I want to move all ports-related bits into a ports-specific ports.conf. > > Now I need your help: > - Location of ports.conf? > $PORTSDIR/ports.conf ? > $PORTSDIR/defaults/ports.conf ? (my favourite) > $PORTSDIR/Mk/ports.conf ? > > I've also created this patch. Ok, now I've read the thread and can give my comments on the topic. To me it seems that ports.conf file isn't really necessary, because it would be just another file that gets unconditionally included from the bsd.ports.mk, perhaps we could just merge content of hypotetic ports.conf with bsd.ports.mk instead. This would solve "where to put it" and "at which point to include it" problems. Comments? -Maxim > Index: bsd.port.mk > =================================================================== > RCS file: /storage/ncvs/ports/Mk/bsd.port.mk,v > retrieving revision 1.377 > diff -u -r1.377 bsd.port.mk > --- bsd.port.mk 27 Aug 2001 00:09:05 -0000 1.377 > +++ bsd.port.mk 28 Aug 2001 20:05:47 -0000 > @@ -606,6 +606,15 @@ > .else > PORTSDIR?= /usr/ports > .endif > + > +.if exists(${PORTSDIR}/ports.conf) > +.include "${PORTSDIR}/ports.conf" > +.endif > + > +.if exists(/etc/ports.conf) > +.include > +.endif > + > LOCALBASE?= ${DESTDIR}/usr/local > X11BASE?= ${DESTDIR}/usr/X11R6 > LINUXBASE?= ${DESTDIR}/compat/linux > > However, I'm not satisfied with it, since it includes it quite late, > maybe too late. But it is the first possible line after $PORTSDIR > is set. > > That's where I need your help. > > Thanks > > Alex > > PS: A _fast_ decision would be appreciated, since this also affects > src/ ;-) [I know you guys are busy :-)] > > PPS: I'd like to see it in 4.4-RELEASE! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 5:20:17 2001 Delivered-To: freebsd-arch@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 25F9437B405 for ; Wed, 29 Aug 2001 05:20:07 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f7TCK3M10490 for ; Wed, 29 Aug 2001 05:20:03 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A2A7C3906; Wed, 29 Aug 2001 05:20:03 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: Julian Elischer , Trent Nelson , freebsd-arch@FreeBSD.ORG, dillon@earth.backplane.com Subject: Re: Paper detailing blocking heuristics based on Scheduler Activiations. In-Reply-To: <20010827203351.A6548@Odin.AC.HMC.Edu> Date: Wed, 29 Aug 2001 05:20:03 -0700 From: Peter Wemm Message-Id: <20010829122003.A2A7C3906@overcee.netplex.com.au> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Going direct worked for me: fetch ftp://ftp.cs.rochester.edu/pub/papers/systems/93.PPoPP.Using_scheduler_information_barrier_synchr_performance.ps.Z Thanks.. Brooks Davis wrote: > > --J2SCkAp4GZ/dPZZf > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Mon, Aug 27, 2001 at 08:34:54PM -0700, Julian Elischer wrote: > > ok so how do you get the actual paper? > > As with most citeseer entries, you can get it from the links at the > upper right hand corner of the page. The cached copy has always worked > for me and the other copy often works if the author hasn't moved. > > -- Brooks > > --=20 > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 > > --J2SCkAp4GZ/dPZZf > Content-Type: application/pgp-signature > Content-Disposition: inline > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE7ixEfXY6L6fI4GtQRApWeAJ9pnrAEjtYYjRTZXYk3SOne1XQs3gCcCuQr > H2gjKh0vDAzbuVcPwgmgXZE= > =yw0E > -----END PGP SIGNATURE----- > > --J2SCkAp4GZ/dPZZf-- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 6:56:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 40B4A37B408 for ; Wed, 29 Aug 2001 06:56:02 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 2582 invoked by uid 1000); 29 Aug 2001 13:55:44 -0000 Date: Wed, 29 Aug 2001 16:55:44 +0300 From: Peter Pentchev To: Maxim Sobolev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf Message-ID: <20010829165544.C780@ringworld.oblivion.bg> Mail-Followup-To: Maxim Sobolev , Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Aug 29, 2001 at 03:12:40PM +0300 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev wrote: > Alexander Langer wrote: > > > Hi folks! > > > > You probably followed the arch-mailinglist. > > > > I want to move all ports-related bits into a ports-specific ports.conf. > > > > Now I need your help: > > - Location of ports.conf? > > $PORTSDIR/ports.conf ? > > $PORTSDIR/defaults/ports.conf ? (my favourite) > > $PORTSDIR/Mk/ports.conf ? > > > > I've also created this patch. > > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. This would solve "where to put it" and "at which > point to include it" problems. Comments? Errr.. I believe that the whole point of ports.conf is that it is a place for user-specified settings. bsd.port.mk gets unconditionally overwritten at each CVSup run (and not everyone is using checked-out CVS trees); ports.conf does not. The situation is similar to /etc/defaults/rc.conf and /etc/rc.conf. G'luck, Peter -- If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 7:31:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from franklin.physics.purdue.edu (franklin.physics.purdue.edu [128.210.146.222]) by hub.freebsd.org (Postfix) with ESMTP id 8693837B408; Wed, 29 Aug 2001 07:31:30 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: from physics.purdue.edu (bohr.physics.purdue.edu [128.210.67.12]) by franklin.physics.purdue.edu (Postfix) with ESMTP id 2AAB920F16; Wed, 29 Aug 2001 09:33:22 -0500 (EST) Received: by physics.purdue.edu (Postfix, from userid 12409) id A24095BC3; Wed, 29 Aug 2001 09:33:30 -0500 (EST) Date: Wed, 29 Aug 2001 09:33:30 -0500 From: Will Andrews To: Maxim Sobolev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf Message-ID: <20010829093330.T35352@bohr.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: Maxim Sobolev , Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Aug 29, 2001 at 03:12:40PM +0300 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev (sobomax@FreeBSD.org) wrote: > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. This would solve "where to put it" and "at which > point to include it" problems. Comments? We already .include several things that could be used as a substitute for the hypothetical ports.conf, like $PORTSDIR/Makefile.inc or similar... -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 7:36:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id EC2D737B40B; Wed, 29 Aug 2001 07:36:40 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (dialup9-6.iptelecom.net.ua [212.9.228.6]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id RAA77260; Wed, 29 Aug 2001 17:36:32 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f7TEZLo61158; Wed, 29 Aug 2001 17:35:21 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B8CFDF0.E716421F@FreeBSD.org> Date: Wed, 29 Aug 2001 17:36:32 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Peter Pentchev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> <20010829165544.C780@ringworld.oblivion.bg> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev wrote: > > Alexander Langer wrote: > > > > > Hi folks! > > > > > > You probably followed the arch-mailinglist. > > > > > > I want to move all ports-related bits into a ports-specific ports.conf. > > > > > > Now I need your help: > > > - Location of ports.conf? > > > $PORTSDIR/ports.conf ? > > > $PORTSDIR/defaults/ports.conf ? (my favourite) > > > $PORTSDIR/Mk/ports.conf ? > > > > > > I've also created this patch. > > > > Ok, now I've read the thread and can give my comments on the topic. To me > > it seems that ports.conf file isn't really necessary, because it would be > > just another file that gets unconditionally included from the bsd.ports.mk, > > perhaps we could just merge content of hypotetic ports.conf with > > bsd.ports.mk instead. This would solve "where to put it" and "at which > > point to include it" problems. Comments? > > Errr.. I believe that the whole point of ports.conf is that it is > a place for user-specified settings. bsd.port.mk gets unconditionally > overwritten at each CVSup run (and not everyone is using checked-out > CVS trees); ports.conf does not. The situation is similar to > /etc/defaults/rc.conf and /etc/rc.conf. Err, as I already clarified I meant *defaults* could be placed into bsd.ports.mk. The whole my point is that I do not see any reason for a separate ${PORTSDIR}/ports.conf (or ports.conf in any other dir in ${PORTSDIR}), which gets unconditionally included into bsd.port.mk. For the record, I do not see any reason for separating user-configurable /etc/ports.conf from /etc/make.conf too, but I do not care either, because I could simply ignore it and continue using /etc/make.conf just like I was doing during the last several years. IMO, proposed change and whole thread in spite of 4.4 release helps nothing and only drives developers' attention from the real problems ("how many bento errors have you fixed today?"). Am I alone feeling like this? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 10:39: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 10D2737B401 for ; Wed, 29 Aug 2001 10:39:01 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f7THcsT47493; Wed, 29 Aug 2001 10:38:54 -0700 (PDT) (envelope-from dillon) Date: Wed, 29 Aug 2001 10:38:54 -0700 (PDT) From: Matt Dillon Message-Id: <200108291738.f7THcsT47493@earth.backplane.com> To: Peter Wemm Cc: Brooks Davis , Julian Elischer , Trent Nelson , freebsd-arch@FreeBSD.ORG Subject: Re: Paper detailing blocking heuristics based on Scheduler Activiations. References: <20010829122003.A2A7C3906@overcee.netplex.com.au> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Going direct worked for me: : :fetch ftp://ftp.cs.rochester.edu/pub/papers/systems/93.PPoPP.Using_scheduler_information_barrier_synchr_performance.ps.Z : :Thanks.. Ok, I printed out and read this paper. I think there are some serious flaws in the paper. The assumptions being made are so specialized (such as assuming that the 'work' section for each thread between barrier points is about the same length), that I don't think the results can be applied generally. Also, the test programs appear to be very simple and thus probably fairly small - which means that there are major assumptions being made in regards to cache effects when spinning verses blocking. It seems to devolve down into essentially non-preemptive cooperative scheduling, and I think the last two graphs pretty much prove that. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 14:28:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id E54C937B405; Wed, 29 Aug 2001 14:28:37 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA10450; Wed, 29 Aug 2001 14:28:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org> Date: Wed, 29 Aug 2001 14:28:41 -0700 (PDT) From: John Baldwin To: Maxim Sobolev Subject: Re: ports.conf Cc: ports@FreeBSD.org, arch@FreeBSD.org, Alexander Langer Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29-Aug-01 Maxim Sobolev wrote: > Alexander Langer wrote: > >> Hi folks! >> >> You probably followed the arch-mailinglist. >> >> I want to move all ports-related bits into a ports-specific ports.conf. >> >> Now I need your help: >> - Location of ports.conf? >> $PORTSDIR/ports.conf ? >> $PORTSDIR/defaults/ports.conf ? (my favourite) >> $PORTSDIR/Mk/ports.conf ? >> >> I've also created this patch. > > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. This would solve "where to put it" and "at which > point to include it" problems. Comments? ports.conf is useful for the same reason that we have make.conf instead of making people read bsd.foo.mk buried in some obscure directory: it's more convenient to users. Also, ports/Mk/ports.conf can easily just be a default file with everything commented out that doesn't even get included. Rather, if a user wants to customize, they create a /etc/ports.conf with teh appropriate knobs set, and bsd.port.mk just includes /etc/ports.conf. The reason for putting the default ports.conf in ports/Mk (or ports/defaults?) instead of /usr/share/examples or some such is the same reason the ports makefiles are in ports/Mk and not /usr/share/mk: it needs to be in sync with the ports tree. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 14:28:53 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 0570237B401; Wed, 29 Aug 2001 14:28:41 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA10471; Wed, 29 Aug 2001 14:28:37 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B8CFDF0.E716421F@FreeBSD.org> Date: Wed, 29 Aug 2001 14:28:42 -0700 (PDT) From: John Baldwin To: Maxim Sobolev Subject: Re: ports.conf Cc: ports@FreeBSD.org, arch@FreeBSD.org, Alexander Langer , Peter Pentchev Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29-Aug-01 Maxim Sobolev wrote: > Err, as I already clarified I meant *defaults* could be placed into > bsd.ports.mk. This is developer friendly, but not user friendly. That is an obscure place to find this information for a non-ports developer. Please keep users in mind. > The whole my > point is that I do not see any reason for a separate ${PORTSDIR}/ports.conf > (or ports.conf in > any other dir in ${PORTSDIR}), which gets unconditionally included into > bsd.port.mk. For the > record, I do not see any reason for separating user-configurable > /etc/ports.conf from > /etc/make.conf too, but I do not care either, because I could simply ignore > it and continue > using /etc/make.conf just like I was doing during the last several years. Because make.conf affects _EVERY_ instance of make that is run. This is a bug. /etc/make.conf should only be used for stuff that people want to affect every make command. (I.e., overriding things in sys.mk.) Other modules should use their own configuration file (ports.conf, world.conf, etc.) This concept has been discusssed for years on the mailing lists. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 18:36:28 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aramis.rutgers.edu (aramis.rutgers.edu [128.6.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 214C737B401; Wed, 29 Aug 2001 18:36:24 -0700 (PDT) (envelope-from muralir@aramis.rutgers.edu) Received: from localhost (muralir@localhost) by aramis.rutgers.edu (8.8.8/8.8.8) with SMTP id VAA19558; Wed, 29 Aug 2001 21:35:47 -0400 (EDT) Date: Wed, 29 Aug 2001 21:35:46 -0400 (EDT) From: Murali Rangarajan To: freebsd-hackers@FreeBSD.org Subject: Fault type in the page fault handler Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is it possible to figure out the fault type(READ or WRITE fault) from inside the page fault handler in user space? I can get the faulting address fine but I have trouble figuring out the fault type. I looked at the i386/i386/machdep.c but couldn't find anything about the access/fault type. Any help would be appreciated. Thanks, Murali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Aug 29 20:39:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id CF57337B408; Wed, 29 Aug 2001 20:39:49 -0700 (PDT) (envelope-from steve@havk.org) Received: from bsd.havk.org (user-24-214-56-224.knology.net [24.214.56.224]) by mail.hiwaay.net (8.11.6/8.11.6) with ESMTP id f7U3dcS20189; Wed, 29 Aug 2001 22:39:39 -0500 (CDT) Received: by bsd.havk.org (Postfix, from userid 1001) id 37FEE1A85D; Wed, 29 Aug 2001 22:39:37 -0500 (CDT) Date: Wed, 29 Aug 2001 22:39:37 -0500 From: Steve Price To: John Baldwin Cc: Maxim Sobolev , ports@FreeBSD.ORG, arch@FreeBSD.ORG, Alexander Langer Subject: Re: ports.conf Message-ID: <20010829223937.Q56784@bsd.havk.org> References: <3B8CDC38.EC1EE32C@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Wed, Aug 29, 2001 at 02:28:41PM -0700 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 29, 2001 at 02:28:41PM -0700, John Baldwin wrote: > > Also, ports/Mk/ports.conf can easily just be a default file with everything > commented out that doesn't even get included. Rather, if a user wants to > customize, they create a /etc/ports.conf with teh appropriate knobs set, and > bsd.port.mk just includes /etc/ports.conf. The reason for putting the default > ports.conf in ports/Mk (or ports/defaults?) instead of /usr/share/examples or > some such is the same reason the ports makefiles are in ports/Mk and not > /usr/share/mk: it needs to be in sync with the ports tree. Like /etc/defaults/make.conf is always in sync with 'make world'? -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 30 0:51:53 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id F13A037B401; Thu, 30 Aug 2001 00:51:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7U7pmZ08043; Thu, 30 Aug 2001 00:51:48 -0700 (PDT) (envelope-from obrien) Date: Thu, 30 Aug 2001 00:51:48 -0700 From: "David O'Brien" To: Maxim Sobolev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf Message-ID: <20010830005148.A7371@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Aug 29, 2001 at 03:12:40PM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev wrote: > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. You weren't paying attention where I mentioned that across my various FreeBSD machines, I need differing ports knobs settings. I share a single NFS /usr/ports across these machines. There *must* be some ports-related make config file in /etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 30 0:58:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 6CADC37B403; Thu, 30 Aug 2001 00:57:59 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (dialup6-40.iptelecom.net.ua [212.9.227.104]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id KAA04774; Thu, 30 Aug 2001 10:57:54 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f7U7vNo65547; Thu, 30 Aug 2001 10:57:23 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B8DF22B.135E063B@FreeBSD.org> Date: Thu, 30 Aug 2001 10:58:35 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: obrien@FreeBSD.org Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> <20010830005148.A7371@dragon.nuxi.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev wrote: > > Ok, now I've read the thread and can give my comments on the topic. To me > > it seems that ports.conf file isn't really necessary, because it would be > > just another file that gets unconditionally included from the bsd.ports.mk, > > perhaps we could just merge content of hypotetic ports.conf with > > bsd.ports.mk instead. > > You weren't paying attention where I mentioned that across my various > FreeBSD machines, I need differing ports knobs settings. I share a > single NFS /usr/ports across these machines. There *must* be some > ports-related make config file in /etc. Hell, you are the *third* person that asks me the same question (see below). -------- Original Message -------- Subject: Re: ports.conf Date: Wed, 29 Aug 2001 17:36:32 +0300 From: Maxim Sobolev Organization: Vega International Capital To: Peter Pentchev CC: Alexander Langer , arch@FreeBSD.ORG, ports@FreeBSD.ORG References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> <20010829165544.C780@ringworld.oblivion.bg> Peter Pentchev wrote: >[...] > Errr.. I believe that the whole point of ports.conf is that it is > a place for user-specified settings. bsd.port.mk gets unconditionally > overwritten at each CVSup run (and not everyone is using checked-out > CVS trees); ports.conf does not. The situation is similar to > /etc/defaults/rc.conf and /etc/rc.conf. Err, as I already clarified I meant *defaults* could be placed into bsd.ports.mk. The whole my point is that I do not see any reason for a separate ${PORTSDIR}/ports.conf (or ports.conf in any other dir in ${PORTSDIR}), which gets unconditionally included into bsd.port.mk. For the record, I do not see any reason for separating user-configurable /etc/ports.conf from /etc/make.conf too, but I do not care either, because I could simply ignore it and continue using /etc/make.conf just like I was doing during the last several years. IMO, proposed change and whole thread in spite of 4.4 release helps nothing and only drives developers' attention from the real problems ("how many bento errors have you fixed today?"). Am I alone feeling like this? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Aug 30 11:26:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 7A80737B408; Thu, 30 Aug 2001 11:26:36 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA07164; Thu, 30 Aug 2001 11:25:18 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010829223937.Q56784@bsd.havk.org> Date: Thu, 30 Aug 2001 11:25:24 -0700 (PDT) From: John Baldwin To: Steve Price Subject: Re: ports.conf Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org, Maxim Sobolev Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 30-Aug-01 Steve Price wrote: > On Wed, Aug 29, 2001 at 02:28:41PM -0700, John Baldwin wrote: >> >> Also, ports/Mk/ports.conf can easily just be a default file with everything >> commented out that doesn't even get included. Rather, if a user wants to >> customize, they create a /etc/ports.conf with teh appropriate knobs set, and >> bsd.port.mk just includes /etc/ports.conf. The reason for putting the >> default >> ports.conf in ports/Mk (or ports/defaults?) instead of /usr/share/examples >> or >> some such is the same reason the ports makefiles are in ports/Mk and not >> /usr/share/mk: it needs to be in sync with the ports tree. > > Like /etc/defaults/make.conf is always in sync with 'make world'? In theory it is if you mergemaster or do something else to update /etc with each world, so yes. > -steve -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 9:49:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 87DF137B406; Fri, 31 Aug 2001 09:49:45 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id SAA26852; Fri, 31 Aug 2001 18:49:44 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VGnkd16922; Fri, 31 Aug 2001 18:49:47 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 18:49:45 +0200 From: Alexander Langer To: "David O'Brien" Cc: Ruslan Ermilov , arch@FreeBSD.org Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831184945.A16872@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831084811.B95710@dragon.nuxi.com>; from obrien@FreeBSD.org on Fri, Aug 31, 2001 at 08:48:11AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.org): Hi David, > NO. You need to step back and resume your discussion on arch@. > Either you are doing things you didn't have a concensis on, or I *really* > blew reading that thread. I even have a mail from you asking why /usr/share/examples/etc isn't a good place for the example make.conf. This was one week ago. Nobody objected in one week, so I commited it yesterday. BTW, this is not a very dramatic change, but a step into seperate {world,ports,docs,...}.conf files. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 10: 2:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 0091E37B407; Fri, 31 Aug 2001 10:02:21 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7VH2Hw17549; Fri, 31 Aug 2001 10:02:17 -0700 (PDT) (envelope-from obrien) Date: Fri, 31 Aug 2001 10:02:16 -0700 From: "David O'Brien" To: Alexander Langer Cc: Ruslan Ermilov , arch@FreeBSD.org Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831100216.A17397@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831184945.A16872@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 06:49:45PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 06:49:45PM +0200, Alexander Langer wrote: > > NO. You need to step back and resume your discussion on arch@. > > Either you are doing things you didn't have a concensis on, or I *really* > > blew reading that thread. > > I even have a mail from you asking why /usr/share/examples/etc > isn't a good place for the example make.conf. Lets put this in context. :-) The Subject: of the thread was "ports.conf". Your introduction statement was: Inspired by a comment from JHB on IRC, I removed all ports relevant entries from /etc/defaults/make.conf and put them into a new ports.conf Reviewing the thread I see you made a switch from talking about ports.conf (which I was still talking about) to etc/defaults/make.conf. I am not sure I am the only one that did not know we were changing the topic of discussion. I saw another surprised reply to your commit. I am asking that you verify the concensis you thought you had to make sure we all knew what your desires were. > This was one week ago. Nobody objected in one week, so I commited > it yesterday. I was not fully aware of you desires, and I am not sure others were either. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 10:39:54 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 648A637B406; Fri, 31 Aug 2001 10:39:47 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id TAA28459; Fri, 31 Aug 2001 19:39:46 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VHdm317109; Fri, 31 Aug 2001 19:39:49 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 19:39:47 +0200 From: Alexander Langer To: "David O'Brien" Cc: Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831100216.A17397@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Aug 31, 2001 at 10:02:16AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.ORG): > Reviewing the thread I see you made a switch from talking about > ports.conf (which I was still talking about) to etc/defaults/make.conf. Ah, yes. I'm sorry. > I am not sure I am the only one that did not know we were changing the > topic of discussion. I saw another surprised reply to your commit. I am > asking that you verify the concensis you thought you had to make sure we > all knew what your desires were. Ok, thanks for doing this, David. Has anyone strong objections against the removal? I can of course back it out, if there is general agreement. If not, there is my current plan: - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file which is included for /usr/src builds. This needs extensive testing. - Teach /usr/doc/ similar. - A patch to bsd.port.mk has already been submitted to portmgr@ and is under development. - Make /etc/make.conf a place for REAL defaults, e.g. CPUTYPE stuff. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11: 1:26 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 5F55F37B403; Fri, 31 Aug 2001 11:01:24 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7VI1Mv21374; Fri, 31 Aug 2001 11:01:22 -0700 (PDT) (envelope-from obrien) Date: Fri, 31 Aug 2001 11:01:22 -0700 From: "David O'Brien" To: Alexander Langer Cc: Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831110121.B21276@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831193947.A17086@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 07:39:47PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 07:39:47PM +0200, Alexander Langer wrote: > If not, there is my current plan: > > - A patch to bsd.port.mk has already been submitted to portmgr@ and > is under development. Can you post the patch? /usr/share/mk/sys.mk, /etc/defaults/make.conf, /etc/make.conf, and /usr/share/examples/etc/make.conf just seem like too many files to chase around. Maybe totally do away with /etc/defaults/make.conf and put BDECFLAGS into either your new world.conf or sys.mk or some other bsd.*.mk in /usr/share/mk. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11: 5:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from femail46.sdc1.sfba.home.com (femail46.sdc1.sfba.home.com [24.254.60.40]) by hub.freebsd.org (Postfix) with ESMTP id DCA7737B406; Fri, 31 Aug 2001 11:05:30 -0700 (PDT) Received: from intruder.bmah.org ([24.176.204.87]) by femail46.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010831180529.EUSR29437.femail46.sdc1.sfba.home.com@intruder.bmah.org>; Fri, 31 Aug 2001 11:05:29 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.5/8.11.3) id f7VI5TP98430; Fri, 31 Aug 2001 11:05:29 -0700 (PDT) (envelope-from bmah) Message-Id: <200108311805.f7VI5TP98430@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Alexander Langer Cc: "David O'Brien" , Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Comments: In-reply-to Alexander Langer message dated "Fri, 31 Aug 2001 19:39:47 +0200." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_826601216P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 31 Aug 2001 11:05:28 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_826601216P Content-Type: text/plain; charset=us-ascii If memory serves me right, Alexander Langer wrote: > Thus spake David O'Brien (obrien@FreeBSD.ORG): > If not, there is my current plan: > > - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file > which is included for /usr/src builds. This needs extensive testing. > - Teach /usr/doc/ similar. Is it my imagination or is this the first time that you've proposed changes to doc/ in this discussion? I think a mention of this over on the -doc list would be real nice. Two things to keep in mind: 1. doc/ isn't branched. Any changes to the doc/ infrastructure will be noticed by (for example) RELENG_4 machines trying to build the doc/ tree. 2. RELNOTESng lives in src/, but it depends on some infrastructure in doc/. Ergo, any changes to the doc/ infrastructure will be noticed by machines (regardless of what version they currently run) trying to build RELNOTESng. (Not so long ago, someone gave me a huge headache by making large-scale changes to the doc/ tree without remembering these two points.) Cheers, Bruce. --==_Exmh_826601216P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7j9Hn2MoxcVugUsMRAqRTAKDPgaYlcHg7w2LZvM5WKP+xeIaufACeMmG4 jMdrZT6g52RilZGXmYWtqQI= =Usr+ -----END PGP SIGNATURE----- --==_Exmh_826601216P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:11:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from franklin.physics.purdue.edu (franklin.physics.purdue.edu [128.210.146.222]) by hub.freebsd.org (Postfix) with ESMTP id 0A4F437B403 for ; Fri, 31 Aug 2001 11:10:08 -0700 (PDT) Received: from physics.purdue.edu (curie.physics.purdue.edu [128.210.68.223]) by franklin.physics.purdue.edu (Postfix) with ESMTP id C63F820F17 for ; Fri, 31 Aug 2001 13:11:43 -0500 (EST) Received: by physics.purdue.edu (Postfix, from userid 12409) id DE5A576; Fri, 31 Aug 2001 13:12:41 -0500 (EST) Date: Fri, 31 Aug 2001 13:12:41 -0500 From: Will Andrews To: arch@FreeBSD.org Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831131241.N30764@curie.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: arch@FreeBSD.org References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200108311805.f7VI5TP98430@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <200108311805.f7VI5TP98430@intruder.bmah.org>; from bmah@FreeBSD.ORG on Fri, Aug 31, 2001 at 11:05:28AM -0700 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 11:05:28AM -0700, Bruce A. Mah (bmah@FreeBSD.ORG) wrote: > 2. RELNOTESng lives in src/, but it depends on some infrastructure in > doc/. Ergo, any changes to the doc/ infrastructure will be noticed by > machines (regardless of what version they currently run) trying to build > RELNOTESng. Why isn't RELNOTESng in doc/ instead where (IMO) it belongs? -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:20:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from femail33.sdc1.sfba.home.com (femail33.sdc1.sfba.home.com [24.254.60.23]) by hub.freebsd.org (Postfix) with ESMTP id 1861837B406 for ; Fri, 31 Aug 2001 11:20:15 -0700 (PDT) Received: from intruder.bmah.org ([24.176.204.87]) by femail33.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010831182014.TMLR4276.femail33.sdc1.sfba.home.com@intruder.bmah.org>; Fri, 31 Aug 2001 11:20:14 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.5/8.11.3) id f7VIKEg13025; Fri, 31 Aug 2001 11:20:14 -0700 (PDT) (envelope-from bmah) Message-Id: <200108311820.f7VIKEg13025@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Will Andrews Cc: arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <20010831131241.N30764@curie.physics.purdue.edu> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200108311805.f7VI5TP98430@intruder.bmah.org> <20010831131241.N30764@curie.physics.purdue.edu> Comments: In-reply-to Will Andrews message dated "Fri, 31 Aug 2001 13:12:41 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_884082668P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 31 Aug 2001 11:20:14 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_884082668P Content-Type: text/plain; charset=us-ascii If memory serves me right, Will Andrews wrote: > On Fri, Aug 31, 2001 at 11:05:28AM -0700, Bruce A. Mah (bmah@FreeBSD.ORG) wro > te: > > 2. RELNOTESng lives in src/, but it depends on some infrastructure in > > doc/. Ergo, any changes to the doc/ infrastructure will be noticed by > > machines (regardless of what version they currently run) trying to build > > RELNOTESng. > > Why isn't RELNOTESng in doc/ instead where (IMO) it belongs? Because RELNOTESng needs to be branched (i.e. HEAD, RELENG_4) and doc/ isn't. Put another way, RELNOTESng belongs with the code that it describes. Bruce. --==_Exmh_884082668P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7j9Vd2MoxcVugUsMRAn/IAJ0QBZ0i1Q9a2m/9sk5Nf6ueP4CERACfa59a NB5mm6ylB54Q84E+OVS54b4= =6L9P -----END PGP SIGNATURE----- --==_Exmh_884082668P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:22:57 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 7B47937B410 for ; Fri, 31 Aug 2001 11:22:28 -0700 (PDT) Received: (qmail 96558 invoked from network); 31 Aug 2001 18:22:27 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Aug 2001 18:22:27 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Date: Fri, 31 Aug 2001 11:22:33 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: Re: cvs commit: src/share/mk sys.mk Cc: arch@FreeBSD.ORG, Ruslan Ermilov , "David O'Brien" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-Aug-01 Alexander Langer wrote: > Thus spake David O'Brien (obrien@FreeBSD.ORG): > >> Reviewing the thread I see you made a switch from talking about >> ports.conf (which I was still talking about) to etc/defaults/make.conf. > > Ah, yes. I'm sorry. > >> I am not sure I am the only one that did not know we were changing the >> topic of discussion. I saw another surprised reply to your commit. I am >> asking that you verify the concensis you thought you had to make sure we >> all knew what your desires were. > > Ok, thanks for doing this, David. > > Has anyone strong objections against the removal? I can of course > back it out, if there is general agreement. > > If not, there is my current plan: > > - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file > which is included for /usr/src builds. This needs extensive testing. The only problem with this is that then world.conf isn't used for one-off test builds. I..e, I do 'cd /usr/src/usr.bin/foo ; make' and world.conf isn't used. I think you should just leave /etc/defaults/make.conf where it is for now and focus on getting ports.conf done and working on the world.conf problem (I don't think doc uses anything in make.conf right now). When those are done, make.conf will be a very small file, and then at that point you can either axe it or move it somewhere else. I would wait to mess with make.conf though until you've finished the other tasks. Don't put the cart before the horse. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:25:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id A938437B403; Fri, 31 Aug 2001 11:25:27 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id UAA29970; Fri, 31 Aug 2001 20:25:26 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VIPTQ17269; Fri, 31 Aug 2001 20:25:30 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 20:25:29 +0200 From: Alexander Langer To: "David O'Brien" Cc: Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831202529.B17086@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831110121.B21276@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831110121.B21276@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Aug 31, 2001 at 11:01:22AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.ORG): > > - A patch to bsd.port.mk has already been submitted to portmgr@ and > > is under development. > Can you post the patch? Of course. cvs diff: Diffing . Index: bsd.port.mk =================================================================== RCS file: /storage/FreeBSD/ncvs/ports/Mk/bsd.port.mk,v retrieving revision 1.377 diff -u -r1.377 bsd.port.mk --- bsd.port.mk 2001/08/27 00:09:05 1.377 +++ bsd.port.mk 2001/08/29 19:48:46 @@ -489,6 +489,10 @@ _PREMKINCLUDED= yes +.if exists(/etc/ports.conf) +.include +.endif + AWK?= /usr/bin/awk BASENAME?= /usr/bin/basename CAT?= /bin/cat Note that $PORTSDIR/Mk/bsd.port.mk defines reasonable defaults, ports.conf is just for overriding these. ports.conf is supped to be maintained in the ports-tree. I just noticed, that we should probably modify src/share/mk/bsd.port.mk instead: include /etc/ports.conf before it sets PORTSDIR via ?=, for obvious reasons. > /usr/share/mk/sys.mk, /etc/defaults/make.conf, /etc/make.conf, and > /usr/share/examples/etc/make.conf just seem like too many files to chase > around. Maybe totally do away with /etc/defaults/make.conf and put > BDECFLAGS into either your new world.conf or sys.mk or some other > bsd.*.mk in /usr/share/mk. Hmm. This seems to be what is the actual situation :-) - We need to keep /usr/share/mk/sys.mk, no question - /etc/make.conf is for local overrides, so are world.conf, docs.conf, www.conf and ports.conf. Maybe they should be moved to a new /etc/make/ dir, as we do with most programs that need/can have multiple files in /etc, such as mail, ssh or isdn. - /etc/defaults/make.conf is gone - /usr/share/examples/etc/make.conf is for maintaining example entries, e.g. CPUTYPE documentation. The ports cvs tree will have an equivalent in future, for documenting example ports.conf entries such as WITHOUT_X11, PORTSDIR, LOCALBASE, etc. Users probably want to use BDECFLAGS in the non-world context, but I also don't really like it in sys.mk. However, bsd.prog.mk could be a correct place, though I don't like to pollution of this file with a variable like this. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:31:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id D548437B407; Fri, 31 Aug 2001 11:31:55 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id UAA30149; Fri, 31 Aug 2001 20:31:55 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VIVv717313; Fri, 31 Aug 2001 20:31:58 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 20:31:57 +0200 From: Alexander Langer To: "Bruce A. Mah" Cc: arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831203157.C17086@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200108311805.f7VI5TP98430@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108311805.f7VI5TP98430@intruder.bmah.org>; from bmah@FreeBSD.ORG on Fri, Aug 31, 2001 at 11:05:28AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Bruce A. Mah (bmah@FreeBSD.ORG): > (Not so long ago, someone gave me a huge headache by making large-scale > changes to the doc/ tree without remembering these two points.) Thanks, I'll keep in mind. I'll do a world.conf first anyways if any, and will contact the doc list, when it's doc/'s turn ;-) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:40:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AB4C37B401; Fri, 31 Aug 2001 11:40:36 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id UAA30405; Fri, 31 Aug 2001 20:40:35 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VIebh17345; Fri, 31 Aug 2001 20:40:37 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 20:40:36 +0200 From: Alexander Langer To: John Baldwin Cc: arch@FreeBSD.org, Ruslan Ermilov , "David O'Brien" Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831204036.D17086@fump.kawo2.rwth-aachen.de> References: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Aug 31, 2001 at 11:22:33AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake John Baldwin (jhb@FreeBSD.org): > The only problem with this is that then world.conf isn't used for one-off test > builds. I..e, I do 'cd /usr/src/usr.bin/foo ; make' and world.conf isn't used. Yes, that's true. However, bsd.{prog,lib}.mk include ../Makefile.inc, which can be used to source /etc/make.conf if not already done. But I hope there are cleaner ways. > (I don't think doc uses anything in make.conf right now). Yes, they do. DOC_LANG for example. However, doc.conf is the last one on my list. > you've finished the other tasks. Don't put the cart before the horse. :) Correct :) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:53:10 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 5FEE037B40B; Fri, 31 Aug 2001 11:53:03 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7VIr0d22086; Fri, 31 Aug 2001 11:53:00 -0700 (PDT) (envelope-from obrien) Date: Fri, 31 Aug 2001 11:53:00 -0700 From: "David O'Brien" To: Alexander Langer Cc: Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831115300.A21541@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831110121.B21276@dragon.nuxi.com> <20010831202529.B17086@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831202529.B17086@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 08:25:29PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 08:25:29PM +0200, Alexander Langer wrote: > Thus spake David O'Brien (obrien@FreeBSD.ORG): > > > > - A patch to bsd.port.mk has already been submitted to portmgr@ and > > > is under development. > > Can you post the patch? > > --- bsd.port.mk 2001/08/27 00:09:05 1.377 > +++ bsd.port.mk 2001/08/29 19:48:46 > @@ -489,6 +489,10 @@ > > _PREMKINCLUDED= yes > > +.if exists(/etc/ports.conf) > +.include > +.endif This is what I expected. Has this been tested? Someone mentioned, correctly, on ports@ that ports.conf will be read after the invidual port's Makefile, where as /etc/make.conf is read before. How does this affect the typical values that one might put in ports.conf? > Users probably want to use BDECFLAGS in the non-world context, understandable > I also don't really like it in sys.mk. Why? > However, bsd.prog.mk could be a correct place, though I don't like to > pollution of this file with a variable like this. bsd.prog.mk is not used for all make invocations. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 11:55:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id A091637B408; Fri, 31 Aug 2001 11:55:15 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7VItDc22152; Fri, 31 Aug 2001 11:55:13 -0700 (PDT) (envelope-from obrien) Date: Fri, 31 Aug 2001 11:55:13 -0700 From: "David O'Brien" To: Alexander Langer Cc: John Baldwin , arch@FreeBSD.org, Ruslan Ermilov Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831115513.B21541@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831204036.D17086@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831204036.D17086@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 08:40:36PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 08:40:36PM +0200, Alexander Langer wrote: > Thus spake John Baldwin (jhb@FreeBSD.org): > > > The only problem with this is that then world.conf isn't used for > > one-off test builds. I..e, I do 'cd /usr/src/usr.bin/foo ; make' and > > world.conf isn't used. > > Yes, that's true. However, bsd.{prog,lib}.mk include ../Makefile.inc, which > can be used to source /etc/make.conf if not already done. Huh? /etc/make.conf is "sourced" (ie, included) by sys.mk. This happens before the Makefile is read. Wasn't JHB taking about world.conf? You seem to be changing the discussion again. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 12: 5:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 1808E37B401; Fri, 31 Aug 2001 12:05:21 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id VAA31223; Fri, 31 Aug 2001 21:05:20 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VJ5Mn17459; Fri, 31 Aug 2001 21:05:23 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 21:05:21 +0200 From: Alexander Langer To: "David O'Brien" Cc: John Baldwin , arch@FreeBSD.ORG, Ruslan Ermilov Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831210521.A17435@fump.kawo2.rwth-aachen.de> References: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831204036.D17086@fump.kawo2.rwth-aachen.de> <20010831115513.B21541@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831115513.B21541@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Aug 31, 2001 at 11:55:13AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.ORG): > > > The only problem with this is that then world.conf isn't used for > > > one-off test builds. I..e, I do 'cd /usr/src/usr.bin/foo ; make' and > > > world.conf isn't used. > > Yes, that's true. However, bsd.{prog,lib}.mk include ../Makefile.inc, which > > can be used to source /etc/make.conf if not already done. > Huh? /etc/make.conf is "sourced" (ie, included) by sys.mk. This Sorry, braino. I meant "can be used to source /etc/world.conf" of course. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 12:44:29 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id EC82B37B403; Fri, 31 Aug 2001 12:44:24 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id VAA32542; Fri, 31 Aug 2001 21:44:24 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f7VJiPC17563; Fri, 31 Aug 2001 21:44:26 +0200 (CEST) (envelope-from alex) Date: Fri, 31 Aug 2001 21:44:25 +0200 From: Alexander Langer To: "David O'Brien" Cc: Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831214424.B17435@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831110121.B21276@dragon.nuxi.com> <20010831202529.B17086@fump.kawo2.rwth-aachen.de> <20010831115300.A21541@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831115300.A21541@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Aug 31, 2001 at 11:53:00AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.ORG): > > @@ -489,6 +489,10 @@ > > > > _PREMKINCLUDED= yes > > > > +.if exists(/etc/ports.conf) > > +.include > > +.endif > This is what I expected. Has this been tested? Well, not well enought, it seems (see below): It's in my tree now, with my various options (e.g. XFREE86_VERSION=4), and stuff like XFREE86 OR WANT_GTK works flawlessly. > Someone mentioned, > correctly, on ports@ that ports.conf will be read after the invidual > port's Makefile, where as /etc/make.conf is read before. How does this > affect the typical values that one might put in ports.conf? I just noticed a fail-test, e.g. .if defined(WITHOUT_X11) CONFIGURE_ARGS+= --without-x11 .endif if occuring before bsd.port.mk was included. At the moment I don't see a solution for this w/o hacking sys.mk. (Alex, this is _BAD_!) > > I also don't really like it in sys.mk. > Why? Pollution of sys.mk with such stuff. Still seems to be the best place, though. > > However, bsd.prog.mk could be a correct place, though I don't like to > > pollution of this file with a variable like this. > bsd.prog.mk is not used for all make invocations. Correct. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Aug 31 13:16:32 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id B3E9737B406; Fri, 31 Aug 2001 13:16:27 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6C45466C80; Fri, 31 Aug 2001 13:16:27 -0700 (PDT) Date: Fri, 31 Aug 2001 13:16:27 -0700 From: Kris Kennaway To: Alexander Langer Cc: David O'Brien , Ruslan Ermilov , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010831131627.A86427@xor.obsecurity.org> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831193947.A17086@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 07:39:47PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2001 at 07:39:47PM +0200, Alexander Langer wrote: > - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file > which is included for /usr/src builds. This needs extensive testing. I couldn't figure out how to do this without adding in .include "../Makefile.inc" on a couple hundred directories to tie them into one big tree so they all have an include path back to /usr/src/world.conf or whatever you want to call it. Having the file only read by make world isn't really acceptible because building parts of the source tree is a common developer activity and needs to use the same file. Anyway, one thing at a time. Kris --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7j/CbWry0BWjoQKURAnIPAKDYO7PDtuNm0bug666MA+Jfc/7+NQCg9SAP XUwvu2ffcmxINidxY61EdeI= =7Drt -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 0:28:11 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.chem.msu.ru (mail.chem.msu.ru [195.208.208.19]) by hub.freebsd.org (Postfix) with ESMTP id 2846037B406; Sat, 1 Sep 2001 00:28:04 -0700 (PDT) Received: from comp.chem.msu.su ([158.250.32.97]) by mail.chem.msu.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id Q5PY2NCA; Sat, 1 Sep 2001 11:17:56 +0400 Received: (from yar@localhost) by comp.chem.msu.su (8.11.1/8.11.1) id f817S1x40110; Sat, 1 Sep 2001 11:28:01 +0400 (MSD) (envelope-from yar) Date: Sat, 1 Sep 2001 11:28:01 +0400 From: Yar Tikhiy To: arch@freebsd.org, doc@freebsd.org Subject: brk(2) manpage seems erroneous and confusing Message-ID: <20010901112800.A26502@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, A friend of mine who is a Unix newbie tried to study various ways of memory allocation, and got confused by the brk(2) page. I read it and became confused either. The current version of the page contains a number doubtful and ambiguous statements. I've found at least six of them: - brk() should return int, not char* - it's a problem of our unistd.h, too - the break isn't the lowest address of the process' data segment - the statement on "data addressing" is likely to be interpreted that one may address memory only between the break and the stack pointer - sbrk() isn't described at all - char* functions are said to return ints - actually, sbrk() returns not new, but prior break value Despites the page is of little use to programmers now, it has certain historical value for those who wish to know how Unix developed. I'd suggest taking the brk(2) page from NetBSD, which language looks much better. If noone minds, I'll do that. Of course, I'll change the function prototypes in the manpage to match our unistd.h unless we decide to fix the latter, too. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 3:48:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id CA69837B405; Sat, 1 Sep 2001 03:48:29 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA17781; Sat, 1 Sep 2001 20:48:27 +1000 Date: Sat, 1 Sep 2001 20:48:14 +1000 (EST) From: Bruce Evans X-X-Sender: To: Yar Tikhiy Cc: , Subject: Re: brk(2) manpage seems erroneous and confusing In-Reply-To: <20010901112800.A26502@comp.chem.msu.su> Message-ID: <20010901204223.K1753-100000@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 1 Sep 2001, Yar Tikhiy wrote: > The current version of the page contains a number doubtful and > ambiguous statements. I've found at least six of them: > > - brk() should return int, not char* - it's a problem of our unistd.h, too > ... > Despites the page is of little use to programmers now, it has > certain historical value for those who wish to know how Unix > developed. I think it started as returning char *. That's what it returns inv V7. > I'd suggest taking the brk(2) page from NetBSD, which language > looks much better. If noone minds, I'll do that. Of course, I'll > change the function prototypes in the manpage to match our unistd.h > unless we decide to fix the latter, too. Better change unistd.h. The kernel returns int. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 8:27:57 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 76BA937B405 for ; Sat, 1 Sep 2001 08:27:53 -0700 (PDT) Received: (qmail 766 invoked by uid 1000); 1 Sep 2001 15:27:44 -0000 Date: Sat, 1 Sep 2001 18:27:44 +0300 From: Peter Pentchev To: Alexander Langer Cc: David O'Brien , John Baldwin , arch@FreeBSD.ORG, Ruslan Ermilov Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010901182744.A590@ringworld.oblivion.bg> Mail-Followup-To: Alexander Langer , David O'Brien , John Baldwin , arch@FreeBSD.ORG, Ruslan Ermilov References: <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831204036.D17086@fump.kawo2.rwth-aachen.de> <20010831115513.B21541@dragon.nuxi.com> <20010831210521.A17435@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831210521.A17435@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Aug 31, 2001 at 09:05:21PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 09:05:21PM +0200, Alexander Langer wrote: > Thus spake David O'Brien (obrien@FreeBSD.ORG): > > > > > The only problem with this is that then world.conf isn't used for > > > > one-off test builds. I..e, I do 'cd /usr/src/usr.bin/foo ; make' and > > > > world.conf isn't used. > > > Yes, that's true. However, bsd.{prog,lib}.mk include ../Makefile.inc, which > > > can be used to source /etc/make.conf if not already done. > > Huh? /etc/make.conf is "sourced" (ie, included) by sys.mk. This > > Sorry, braino. I meant "can be used to source /etc/world.conf" of course. This would still be included at the end of the program's Makefile, meaning the Makefile would not be able to test for world.conf overrides. G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 9:53:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 11FC937B405; Sat, 1 Sep 2001 09:53:15 -0700 (PDT) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.5/8.11.5) with ESMTP id f81Gq5o82518; Sat, 1 Sep 2001 12:52:07 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200109011652.f81Gq5o82518@aldan.algebra.com> Date: Sat, 1 Sep 2001 12:52:04 -0400 (EDT) From: Mikhail Teterin Subject: proctitle progress reporting for dump(8) To: current@freebsd.org, arch@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does this look like a good idea to anyone else? 79239 ?? I 0:00,89 dump 0ushf 1048576 0 - /dev/da0h (dump) 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) 79241 ?? S 0:13,93 dump 0ushf 1048576 0 - /dev/da0h (dump) 79242 ?? S 0:13,92 dump 0ushf 1048576 0 - /dev/da0h (dump) 79243 ?? S 0:13,90 dump 0ushf 1048576 0 - /dev/da0h (dump) Does anyone think, it is a bad idea? If no, I'll send-pr the patch... For me, dump is driven by a remote amanda and its nice to know, when it is going to be over (I have a fairly slow link to the backup server). Comments? -- -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 10:46:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fepD.post.tele.dk (fepD.post.tele.dk [195.41.46.149]) by hub.freebsd.org (Postfix) with ESMTP id D018B37B405; Sat, 1 Sep 2001 10:46:41 -0700 (PDT) Received: from arnold.neland.dk ([62.243.124.171]) by fepD.post.tele.dk (InterMail vM.4.01.03.21 201-229-121-121-20010307) with ESMTP id <20010901174640.CWJU19779.fepD.post.tele.dk@arnold.neland.dk>; Sat, 1 Sep 2001 19:46:40 +0200 Received: from gina ([192.168.5.109]) by arnold.neland.dk (8.11.5/8.11.5) with SMTP id f81Hlab20288; Sat, 1 Sep 2001 19:47:36 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <004f01c1330d$f34d37c0$6d05a8c0@neland.dk> From: "Leif Neland" To: "Mikhail Teterin" , , References: <200109011652.f81Gq5o82518@aldan.algebra.com> Subject: Re: proctitle progress reporting for dump(8) Date: Sat, 1 Sep 2001 19:45:17 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I like it. I se no problem. > Does this look like a good idea to anyone else? > > 79239 ?? I 0:00,89 dump 0ushf 1048576 0 - /dev/da0h (dump) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 10:47:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep15-int.chello.nl (amsfep15-int.chello.nl [213.46.243.27]) by hub.freebsd.org (Postfix) with ESMTP id 1559237B40C; Sat, 1 Sep 2001 10:47:15 -0700 (PDT) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep15-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20010901174419.UONB2849.amsfep15-int.chello.nl@daemon.chronias.ninth-circle.org>; Sat, 1 Sep 2001 19:44:19 +0200 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f81Hl6S35638; Sat, 1 Sep 2001 19:47:06 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Sep 2001 19:47:06 +0200 From: Jeroen Ruigrok/Asmodai To: Mikhail Teterin Cc: current@freebsd.org, arch@freebsd.org Subject: Re: proctitle progress reporting for dump(8) Message-ID: <20010901194706.C33712@daemon.ninth-circle.org> References: <200109011652.f81Gq5o82518@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109011652.f81Gq5o82518@aldan.algebra.com> User-Agent: Mutt/1.3.19i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20010901 19:00], Mikhail Teterin (mi@aldan.algebra.com) wrote: >79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) >Does anyone think, it is a bad idea? If no, I'll send-pr the patch... >For me, dump is driven by a remote amanda and its nice to know, when >it is going to be over (I have a fairly slow link to the backup server). Looks nice. Would definately be an improvement. I would like it. How often does it update the proctitle? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ I dream of gardens in the desert sand... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 10:55:33 2001 Delivered-To: freebsd-arch@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id 0879D37B40C; Sat, 1 Sep 2001 10:55:24 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA18849; Sat, 1 Sep 2001 19:55:22 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.4) id f81HtMS26111; Sat, 1 Sep 2001 19:55:22 +0200 (CEST) (envelope-from wkb) Date: Sat, 1 Sep 2001 19:55:22 +0200 From: Wilko Bulte To: Leif Neland Cc: Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) Message-ID: <20010901195522.A26047@freebie.xs4all.nl> References: <200109011652.f81Gq5o82518@aldan.algebra.com> <004f01c1330d$f34d37c0$6d05a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004f01c1330d$f34d37c0$6d05a8c0@neland.dk>; from leifn@neland.dk on Sat, Sep 01, 2001 at 07:45:17PM +0200 X-OS: FreeBSD 4.4-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 07:45:17PM +0200, Leif Neland wrote: > I like it. I se no problem. > > > Does this look like a good idea to anyone else? > > > > 79239 ?? I 0:00,89 dump 0ushf 1048576 0 - /dev/da0h (dump) Nice idea IMO. -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 11:43:11 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 98E4137B408 for ; Sat, 1 Sep 2001 11:43:08 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 7C73C81D01; Sat, 1 Sep 2001 13:43:03 -0500 (CDT) Date: Sat, 1 Sep 2001 13:43:03 -0500 From: Alfred Perlstein To: John Polstra Cc: arch@freebsd.org Subject: AMD defaults? (was: Re: Tuning UDP for NFS) Message-ID: <20010901134303.X81307@elvis.mu.org> References: <20010831130902.A15501@nomad.lets.net> <20010831125120.O81307@elvis.mu.org> <200108312003.f7VK3k004259@vashon.polstra.com> <20010831154119.S81307@elvis.mu.org> <200109011601.f81G1tY09116@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109011601.f81G1tY09116@vashon.polstra.com>; from jdp@polstra.com on Sat, Sep 01, 2001 at 09:01:55AM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Any AMD gurus in the house? Alfred Perlstein wrote: > > Using UDP is usually a bad idea, I would use tcp, I find that these > flags make for a decent mount point that's quite fast: > rw,tcp,intr,nfsv3,-w=32768,-r=32768 * John Polstra [010901 11:02] wrote: > In article <20010831154119.S81307@elvis.mu.org>, > Alfred Perlstein wrote: > > * John Polstra [010831 15:03] wrote: > > > FreeBSD's "src/etc/amd.map" file still has "vers=2,proto=udp". Do > > > you think we should change it? > > > > I'm not familiar with amd, what implications would that have? > > > > What worries me is people using amd against a v2 server, also those > > tunables are good at tickling bugs in other NFS implementations > > (as well as ours, at least a year or two ago). So if amd is smart > > enough to downgrade then yes, otherwise perhaps just a comment to > > indicate that the person may want to use better mount options... ? > > I have the same concerns. Unfortunately I don't know enough about > NFS interoperability issues to say whether it would cause problems > or not. > > OTOH we have been moving toward giving our default configurations > better performance at the expense of a small amount of failsafe-ness. > I'm inclined to think this might be a good candidate for that trend. Since niether of us are sure, I'm reposting this to -arch in hopes of getting more feedback. Oh and don't forget 'rdirplus'. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 11:56:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 3726B37B40D for ; Sat, 1 Sep 2001 11:56:53 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id LAA06815; Sat, 1 Sep 2001 11:56:30 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda06813; Sat Sep 1 11:56:29 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id f81IuSK57599; Sat, 1 Sep 2001 11:56:28 -0700 (PDT) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdZ57275; Sat Sep 1 11:55:44 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id f81ItpL00748; Sat, 1 Sep 2001 11:55:51 -0700 (PDT) Message-Id: <200109011855.f81ItpL00748@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdjlK743; Sat Sep 1 11:55:04 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Alfred Perlstein Cc: John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) In-reply-to: Your message of "Sat, 01 Sep 2001 13:43:03 CDT." <20010901134303.X81307@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Sep 2001 11:55:04 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010901134303.X81307@elvis.mu.org>, Alfred Perlstein writes: > Any AMD gurus in the house? > > Alfred Perlstein wrote: > > > > Using UDP is usually a bad idea, I would use tcp, I find that these > > flags make for a decent mount point that's quite fast: > > rw,tcp,intr,nfsv3,-w=32768,-r=32768 I'm far from being an amd guru, however I've been running am-utils-6.0[79] on FreeBSD for the past few months. Am-utils >= 6.07 does support rdirplus. If you want to try it yourself download a copy of am-utils-6.09 and untar it into /usr/src/contrib. If after reading this, you would like to try it out, I can send you a patch that will update some makefiles in the source tree to allow am-utils-6.09 to compile. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 12: 6: 3 2001 Delivered-To: freebsd-arch@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5044A37B403; Sat, 1 Sep 2001 12:05:57 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f81J5tB95403; Sat, 1 Sep 2001 15:05:55 -0400 (EDT) (envelope-from wollman) Date: Sat, 1 Sep 2001 15:05:55 -0400 (EDT) From: Garrett Wollman Message-Id: <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> To: Jeroen Ruigrok/Asmodai Cc: Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) In-Reply-To: <20010901194706.C33712@daemon.ninth-circle.org> References: <200109011652.f81Gq5o82518@aldan.algebra.com> <20010901194706.C33712@daemon.ninth-circle.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: >> 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) SIGINFO! SIGINFO! SIGINFO! -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 12:52:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 9DD8C37B407; Sat, 1 Sep 2001 12:52:07 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA06938; Sat, 1 Sep 2001 12:51:51 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda06936; Sat Sep 1 12:51:47 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id f81Jpk844764; Sat, 1 Sep 2001 12:51:46 -0700 (PDT) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdC44664; Sat Sep 1 12:51:05 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id f81Jp4v01081; Sat, 1 Sep 2001 12:51:04 -0700 (PDT) Message-Id: <200109011951.f81Jp4v01081@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdqg1075; Sat Sep 1 12:50:31 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Garrett Wollman Cc: Jeroen Ruigrok/Asmodai , Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) In-reply-to: Your message of "Sat, 01 Sep 2001 15:05:55 EDT." <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Sep 2001 12:50:31 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu>, Garrett Wollman w rites: > < > said: > > >> 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:4 > 3 (dump) > > SIGINFO! SIGINFO! SIGINFO! Much better idea! Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 12:55:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep11-int.chello.nl (amsfep11-int.chello.nl [213.46.243.19]) by hub.freebsd.org (Postfix) with ESMTP id 1446637B40B; Sat, 1 Sep 2001 12:55:14 -0700 (PDT) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep11-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20010901195232.KPTP15398.amsfep11-int.chello.nl@daemon.chronias.ninth-circle.org>; Sat, 1 Sep 2001 21:52:32 +0200 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f81Jt9g36607; Sat, 1 Sep 2001 21:55:09 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Sep 2001 21:55:09 +0200 From: Jeroen Ruigrok/Asmodai To: Garrett Wollman Cc: Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) Message-ID: <20010901215509.D33712@daemon.ninth-circle.org> References: <200109011652.f81Gq5o82518@aldan.algebra.com> <20010901194706.C33712@daemon.ninth-circle.org> <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.3.19i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20010901 21:48], Garrett Wollman (wollman@khavrinen.lcs.mit.edu) wrote: >< said: > >>> 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) > >SIGINFO! SIGINFO! SIGINFO! Heh. :) Let me elaborate your, erm, somewhat terse reply so that I understand you. You mean dump should get a signal handler for SIGINFO to print/display the current status of the application? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Someone help me, I think I've lost control... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 13:12:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A545437B408; Sat, 1 Sep 2001 13:12:32 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f81KCU295997; Sat, 1 Sep 2001 16:12:30 -0400 (EDT) (envelope-from wollman) Date: Sat, 1 Sep 2001 16:12:30 -0400 (EDT) From: Garrett Wollman Message-Id: <200109012012.f81KCU295997@khavrinen.lcs.mit.edu> To: Jeroen Ruigrok/Asmodai Cc: Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) In-Reply-To: <20010901215509.D33712@daemon.ninth-circle.org> References: <200109011652.f81Gq5o82518@aldan.algebra.com> <20010901194706.C33712@daemon.ninth-circle.org> <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> <20010901215509.D33712@daemon.ninth-circle.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > You mean dump should get a signal handler for SIGINFO to print/display > the current status of the application? Yes! Just like in fsck, and for the same reasons. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 13:48:50 2001 Delivered-To: freebsd-arch@freebsd.org Received: from zevs.idi.ntnu.no (zevs.idi.ntnu.no [129.241.110.12]) by hub.freebsd.org (Postfix) with ESMTP id 11AE537B406; Sat, 1 Sep 2001 13:48:46 -0700 (PDT) Received: from idi.ntnu.no (IDENT:1892@vier.idi.ntnu.no [129.241.103.4]) by zevs.idi.ntnu.no (8.9.3/8.9.3) with ESMTP id WAA25779; Sat, 1 Sep 2001 22:48:38 +0200 (MEST) Message-Id: <200109012048.WAA25779@zevs.idi.ntnu.no> X-Mailer: exmh version 2.2 10/02/2000 with version: MH 6.8.3 #1[UCI] To: Garrett Wollman Cc: Jeroen Ruigrok/Asmodai , Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG, adf@idi.ntnu.no Subject: Re: proctitle progress reporting for dump(8) In-reply-to: Your message of "Sat, 01 Sep 2001 15:05:55 EDT." <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Sep 2001 22:48:37 +0200 From: Arne Dag Fidjestøl Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > < said: > > >> 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) > > SIGINFO! SIGINFO! SIGINFO! You'd still need somewhere to put the status message; the dump process above has no controlling terminal. -adf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 14:36:33 2001 Delivered-To: freebsd-arch@freebsd.org Received: from amsfep16-int.chello.nl (amsfep16-int.chello.nl [213.46.243.25]) by hub.freebsd.org (Postfix) with ESMTP id 5AB8637B403; Sat, 1 Sep 2001 14:36:26 -0700 (PDT) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep16-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20010901213316.MJYP2039.amsfep16-int.chello.nl@daemon.chronias.ninth-circle.org>; Sat, 1 Sep 2001 23:33:16 +0200 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f81LaL337345; Sat, 1 Sep 2001 23:36:21 +0200 (CEST) (envelope-from asmodai) Date: Sat, 1 Sep 2001 23:36:20 +0200 From: Jeroen Ruigrok/Asmodai To: Arne Dag =?unknown-8bit?Q?Fidjest=F8l?= Cc: Garrett Wollman , Mikhail Teterin , current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) Message-ID: <20010901233620.E33712@daemon.ninth-circle.org> References: <200109011905.f81J5tB95403@khavrinen.lcs.mit.edu> <200109012048.WAA25779@zevs.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200109012048.WAA25779@zevs.idi.ntnu.no> User-Agent: Mutt/1.3.19i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20010901 23:24], Arne Dag Fidjestøl (adf@idi.ntnu.no) wrote: >You'd still need somewhere to put the status message; the dump process above >has no controlling terminal. Putting it into syslog might be a bit too verbose for this? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Give me the rest to accept what I cannot change, give me the strength to change when I can, and give me the wisdom to see the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 15:59:19 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 705FF37B40B; Sat, 1 Sep 2001 15:59:15 -0700 (PDT) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.5/8.11.5) with ESMTP id f81MwAo84783; Sat, 1 Sep 2001 18:58:11 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200109012258.f81MwAo84783@aldan.algebra.com> Date: Sat, 1 Sep 2001 18:58:07 -0400 (EDT) From: Mikhail Teterin Subject: Re: proctitle progress reporting for dump(8) To: asmodai@wxs.nl Cc: current@freebsd.org, arch@freebsd.org In-Reply-To: <20010901194706.C33712@daemon.ninth-circle.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 1 Sep, Jeroen Ruigrok/Asmodai wrote: > -On [20010901 19:00], Mikhail Teterin (mi@aldan.algebra.com) wrote: >>79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:43 (dump) > > Looks nice. Would definately be an improvement. > > I would like it. How often does it update the proctitle? Whenever it outputs a line to the stderr -- I personally find no regularity in that :(. SIGINFO handling is a different thing, though. I'll look at that too. Thanks, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 18:27: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 47BDC37B40F for ; Sat, 1 Sep 2001 18:27:02 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f821Q8n51533; Sat, 1 Sep 2001 18:26:08 -0700 (PDT) (envelope-from obrien) Date: Sat, 1 Sep 2001 18:26:08 -0700 From: "David O'Brien" To: Cy Schubert - ITSD Open Systems Group Cc: Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) Message-ID: <20010901182608.A51464@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010901134303.X81307@elvis.mu.org> <200109011855.f81ItpL00748@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109011855.f81ItpL00748@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Sat, Sep 01, 2001 at 11:55:04AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 11:55:04AM -0700, Cy Schubert - ITSD Open Systems Group wrote: > I'm far from being an amd guru, however I've been running > am-utils-6.0[79] on FreeBSD for the past few months. Am-utils >= 6.07 > does support rdirplus. If you want to try it yourself download a copy > of am-utils-6.09 and untar it into /usr/src/contrib. If after reading > this, you would like to try it out, I can send you a patch that will > update some makefiles in the source tree to allow am-utils-6.09 to > compile. Why have you not either (1) sent this to me, or (2) opened a PR with the patches?? am-utils until recently[*] did not properly configure and build on a FreeBSD host. I had offers from the am-utils maintainer to fix this if given an account on a reference box. FreeBSD Core has shown their inability to follow thru and make this happen. Thus I have refused to update src/contrib/amd for quite sometime. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 19: 8: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 2412037B40A; Sat, 1 Sep 2001 19:08:03 -0700 (PDT) Received: from madman.nectar.com (madman.nectar.com [10.0.1.111]) by gw.nectar.com (Postfix) with ESMTP id 7AD82369; Sat, 1 Sep 2001 21:08:02 -0500 (CDT) Received: (from nectar@localhost) by madman.nectar.com (8.11.3/8.11.3) id f82281p54670; Sat, 1 Sep 2001 21:08:01 -0500 (CDT) (envelope-from nectar) Date: Sat, 1 Sep 2001 21:08:01 -0500 From: "Jacques A. Vidrine" To: "David O'Brien" Cc: Cy Schubert - ITSD Open Systems Group , Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) Message-ID: <20010901210800.A54656@madman.nectar.com> References: <20010901134303.X81307@elvis.mu.org> <200109011855.f81ItpL00748@cwsys.cwsent.com> <20010901182608.A51464@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010901182608.A51464@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sat, Sep 01, 2001 at 06:26:08PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 06:26:08PM -0700, David O'Brien wrote: > On Sat, Sep 01, 2001 at 11:55:04AM -0700, Cy Schubert - ITSD Open Systems Group wrote: > > I'm far from being an amd guru, however I've been running > > am-utils-6.0[79] on FreeBSD for the past few months. Am-utils >= 6.07 > > does support rdirplus. If you want to try it yourself download a copy > > of am-utils-6.09 and untar it into /usr/src/contrib. If after reading > > this, you would like to try it out, I can send you a patch that will > > update some makefiles in the source tree to allow am-utils-6.09 to > > compile. > > Why have you not either (1) sent this to me, or (2) opened a PR with the > patches?? > > am-utils until recently[*] did not properly configure and build on a > FreeBSD host. I had offers from the am-utils maintainer to fix this if > given an account on a reference box. FreeBSD Core has shown their > inability to follow thru and make this happen. Thus I have refused to > update src/contrib/amd for quite sometime. Hey, if core@ gets around to approving Cy's port commit bit, maybe you could also mentor him into maintaining am-utils. Then it wouldn't be your problem :-) Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 1 20:47:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1BCE637B407 for ; Sat, 1 Sep 2001 20:47:32 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f823lEi80038; Sat, 1 Sep 2001 20:47:14 -0700 (PDT) (envelope-from obrien) Date: Sat, 1 Sep 2001 20:47:13 -0700 From: "David O'Brien" To: "Jacques A. Vidrine" Cc: Cy Schubert - ITSD Open Systems Group , Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) Message-ID: <20010901204713.A80020@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010901134303.X81307@elvis.mu.org> <200109011855.f81ItpL00748@cwsys.cwsent.com> <20010901182608.A51464@dragon.nuxi.com> <20010901210800.A54656@madman.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010901210800.A54656@madman.nectar.com>; from n@nectar.com on Sat, Sep 01, 2001 at 09:08:01PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 09:08:01PM -0500, Jacques A. Vidrine wrote: > Hey, if core@ gets around to approving Cy's port commit bit, maybe you > could also mentor him into maintaining am-utils. Then it wouldn't be > your problem :-) It would still be a problem -- or do we not care if things compile and work out of the box on FreeBSD? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message