Re: import NetBSD rc system [summary]
In message [EMAIL PROTECTED] Jordan Hubbard writes: : I think that since we use CVS around here, we should simply import the I agree. Let's just cvs import the NetBSD stuff verbatim and unmodified on a vendor branch, but allow for limited commits to those files by folks that have really been working on it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
[EMAIL PROTECTED] wrote: At 10:01 PM -0400 6/12/01, Kevin Way wrote: David Xu wrote: Is there any plan to import NetBSD rc system, I am willing to see it appears in FreeBSD 5.0. Here's the status of this project at the moment as I see. Please let me know if I've misunderstood anything, or if anybody has had a change of heart. I see no reference to the thread Plan to import NetBSD rc system from Sheldon Hearn, where he said: Thanks Garance, that's exactly why I posted the summary. My current status is: -setup dedicated net freebsd -CURRENT boxes -made sure rcorder worked on fbsd -ported rc, rc.subr, and started with the individual rc.d scripts Seeing as there are a few of us who are working on independant implementations of this port, perhaps we should follow Sheldon's original advice, and after USENIX, let Sheldon decide what changes each of us made were good/bad, and go from there? I apologize if the formatting of this message is botched, I'm using an awful web-mail client, as the machine i read e-mail on bit the dust this morning. Kevin Way To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
I think that since we use CVS around here, we should simply import the first semi-working model and let the other committers dive in and commit their refinements as we go along. Up to now, this whole NetBSD rc thing has looked more like one of those baseball scenes were 5 people all yell I got it! and then either slam together in mid-field or all stand still looking stupid as the ball hits the ground in front of them. I've seen a lot of hands go up but I STILL haven't seen anything committed or even just a URL to some prototype bits to test. :( - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
On Thu, Jun 14, 2001 at 10:48:49AM -0700, Jordan Hubbard wrote: I think that since we use CVS around here, we should simply import the Some time tonight I will be vendor importing the NetBSD rc system. (no it will not be functional at that time). I am doing this to help the various efforts that are working on this so they can pass round patches vs. entire files. Doing the vendor import will also help remind us the goal here is to adopt the NetBSD RC system -- not go off and have a second syndrome party, or other results of NIH. Once the vendor import is done, we can coordinate with the NetBSD folks the minor changes that FreeBSD will require to use their system. There may be places where the NetBSD RC system could doing things better, but the ongoing relationship we can create with NetBSD is something far more valuable than a few efficiency/functionality tweaks. If we do find short comings we should resolve them by working with the NetBSD guys. With any hope, maybe BSD/OS could pick up this RC system also. ** ** I ask that no one commit to NetBSD RC files until diffs have been ** posted on [EMAIL PROTECTED] for review and we have agreement ** ** that the change is necessary. ** -- -- David([EMAIL PROTECTED]) Disclaimer: Not speaking for Wind River systems. I am making no claims or promises about BSD/OS. I am speaking purely with a FreeBSD hat on, stating a wouldn't it be nice prase. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
On Thu, Jun 14, 2001 at 12:03:02PM -0700, David O'Brien wrote: On Thu, Jun 14, 2001 at 10:48:49AM -0700, Jordan Hubbard wrote: I think that since we use CVS around here, we should simply import the Some time tonight I will be vendor importing the NetBSD rc system. (no it will not be functional at that time). I am doing this to help the various efforts that are working on this so they can pass round patches vs. entire files. Erm.. Sheldon Hearn has expressed a desire to discuss things with Luke Mewburn in the hope of coming to some mutual agreement as to directions and improvements. Have you discussed this vendor import of the current NetBSD RC system with him? Wouldn't it be better to wait until Luke himself says something about the possible future directions the common RC system might want to take? G'luck, Peter -- What would this sentence be like if it weren't self-referential? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
On Thu, Jun 14, 2001 at 10:08:48PM +0300, Peter Pentchev wrote: Some time tonight I will be vendor importing the NetBSD rc system. (no it will not be functional at that time). Erm.. Sheldon Hearn has expressed a desire to discuss things with Luke Mewburn in the hope of coming to some mutual agreement as to directions and improvements. My actions in no way changes Sheldon's efforts. In fact it helps them. We will have a way to see proposed changes in the form of a diff. This makes it easy to see where we are deviating from the NetBSD RC system. It also gives Sheldon the diff to send to Luke for discussion. If Luke agrees and makes a change in the NetBSD RC sources, we will get the fruits of Sheldon's effort on the next vendor import. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system [summary]
Jordan Hubbard [EMAIL PROTECTED] writes: ground in front of them. I've seen a lot of hands go up but I STILL haven't seen anything committed or even just a URL to some prototype bits to test. :( before coding anything, it's a common usage to know the way to go. for instance, I'm not sure there is a consensus about the way to follow. except if the consensus is just : ok, grab the NetBSD framework, cut and past things from FreeBSD files to NetBSD files, and go. this could be done in a few hours by almost anybody, but, IMHO, is a waste of time until a good way is defined. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
import NetBSD rc system [summary]
Is there any plan to import NetBSD rc system, I am willing to see it appears in FreeBSD 5.0. Here's the status of this project at the moment as I see. Please let me know if I've misunderstood anything, or if anybody has had a change of heart. Both Gordon Tetlow and myself have volunteered to start the work seperately (which I'm assuming isn't entirely a bad thing). Doug Barton started work on this before, but got sidetracked by unrelated -CURRENT troubles. Any chance you have anything helpful for us, from your previous efforts, Doug? Mike Meyer has volunteered to assist, (and those of you who have CueCat's should check out his nifty little CueCat utility) and last but certainly not least, Jordan Hubbard just wants somebody to stop talking and code. :-) [EMAIL PROTECTED] mentioned the first of the many adjustments to be made, this one regarding mergemaster. I've started a project homepage at http://overtone.org/rc.d/ as I get code together, and released, I'll keep it updated, unless it turns out that Gordon Tetlow is a machine, and integrates the whole thing before I can get NetBSD -current and FreeBSD -current installed. -Kevin Way PGP signature
