[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
Matt Dillon wrote:
:Thanks for this commit, but it works exactly in the way, which
:I wanted to avoid. It is something like partially submitted and
:not approved by me. Please, could you look once again on it?
:Please please please... Thanks. ;-)
:
:- Hunk #1 from commit adds PS_NOCLDWAIT
:I really, really object to not setting the SA_NOCLDWAIT
:flag.
:
:At the very least, you need to add a SA_CLDWAIT flag, if you
:want to not have it show up in this case, and make it show
:up in the other case.
:
:I think doing this would be a mistake, since the intent of
:the flags is to have
I've asked -ports before whether it is suitable to let ports startup scripts
honor /etc/rc.conf{,.local} settings by sourcing /etc/defaults/rc.conf and
then running a source_rc_confs (or whatever is appropriate).
my suggestion:
this is the 'modified' loop for the ${local_startup} in
hi,
On Wed, Jun 13, 2001 at 09:47:52PM -0500, Chris Costello wrote:
If this ends up being the case (i.e., there's an issue approx. once a
month), how about archiving them on the web site? We used to have a
newsletter, but it quickly grew stale. This sounds like something
developers
Go for it.
In message [EMAIL PROTECTED], Dima Dorfman write
s:
Hi folks,
Would anybody have a tantrum if a program with a mount_mfs-like
interface to create an md disk and put a UFS filesystem on it was
imported into the base system? This has been suggested in the past,
and the only real
Good day!
On Mon, 28 May 2001, Søren Schmidt wrote:
As promised I've made up a list of reports I've received so far go to
http://freebsd.dk/ and follow the link.
I also have a patch for the Yamaha's (yamaha-cdr.p1) which also
can be found via the above URL. Let me know if that make things
Matt Dillon wrote:
The issue here is first: since we are fixing a bug we might
as well be as compatible as possible with other platforms and,
second: on general principles it does make sense to keep SIG_IGN
operation independant from the newer SA_NOCLDWAIT stuff. A program
Andrew Hesford [EMAIL PROTECTED] writes:
On Wed, Jun 13, 2001 at 06:04:23PM -0700, Gordon Tetlow wrote:
[snip]
Anyway, here's my status:
rcorder ported (one line code change)
CPPFLAGS - CFLAGS in Makefile I suppose ?
Alternatively, give up the handy feature of being able to start
On Wed, 13 Jun 2001, Dima Dorfman wrote:
Robert Watson [EMAIL PROTECTED] writes:
- Future Editions
Assuming there is some positive feedback on this idea, and that future
submissions get made such that there is content for future issues, the
goal is to release a development status
[EMAIL PROTECTED] said:
:- oops, rc2 isn't started. too bad.
I think that is exactly the desired design. The
RC *system* starts things correctly, but the manager,
*bypassing* the RC *system* can start and stop things
exactly as he wished. For debugging or whatever.
I'd argue that if you
To do some of the hierarchal start/stop at runtime stuff, you really need
a stateful rc system that stores its start/stop state in /var/run/rc.d or
the like. In this way, the system could track various activities and know
which dependencies were already started. However, this has a number of
Dear All,
To do some of the hierarchal start/stop at runtime stuff, you
really need
a stateful rc system that stores its start/stop state in
/var/run/rc.d or
the like. In this way, the system could track various
activities and know
which dependencies were already started.
How about
On Thu, 14 Jun 2001, Koster, K.J. wrote:
To do some of the hierarchal start/stop at runtime stuff, you
really need
a stateful rc system that stores its start/stop state in
/var/run/rc.d or
the like. In this way, the system could track various
activities and know
which
:Matt Dillon wrote:
: The issue here is first: since we are fixing a bug we might
: as well be as compatible as possible with other platforms and,
: second: on general principles it does make sense to keep SIG_IGN
: operation independant from the newer SA_NOCLDWAIT stuff. A
On Thu, Jun 14, 2001 at 10:49:11AM +0300, Danny Braniss wrote:
I've asked -ports before whether it is suitable to let ports startup scripts
honor /etc/rc.conf{,.local} settings by sourcing /etc/defaults/rc.conf and
then running a source_rc_confs (or whatever is appropriate).
my
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
in fact, the require keyword isn't sufficient in it's own. there
should be pre_require and post_require keywords since nfsd needs to
start mountd before to start nfsd then rpc.statd and rpc.lockd have to
be started after nfsd.
My answer to this, in the reasoning that NetBSD compatibility is
Cyrille Lefevre wrote:
in fact, the require keyword isn't sufficient in it's own. there
should be pre_require and post_require keywords since nfsd needs to
start mountd before to start nfsd then rpc.statd and rpc.lockd have to
be started after nfsd.
Cyrille has already made two
On Thu, Jun 14, 2001 at 09:57:17AM -0400, Robert Withrow wrote:
[EMAIL PROTECTED] said:
:- oops, rc2 isn't started. too bad.
I think that is exactly the desired design. The
RC *system* starts things correctly, but the manager,
*bypassing* the RC *system* can start and stop things
In message [EMAIL PROTECTED] Doug Barton writes:
: in fact, the require keyword isn't sufficient in it's own. there
: should be pre_require and post_require keywords since nfsd needs to
: start mountd before to start nfsd then rpc.statd and rpc.lockd have to
: be started after nfsd.
:
:
Peter Pentchev([EMAIL PROTECTED])@2001.06.14 20:19:27 +:
OK, and what do I do if I want to manually start/stop the service later,
and it needs variables defined in /etc/rc.conf{,local} ?
if [ x${_RC_CONF} != x1 ]; then . /etc/rc.conf; fi
in the beginning of the local startup script?
if it
On Thu, 14 Jun 2001, Warner Losh wrote:
With all due respect to Eivind, he's reinventing the wheel. I'd like
to see NetBSD's brought in with an absolute minimum of change.
Along those lines, I'm typing on my laptop that is using the scripts that
I have ported over... I've only gotten it up
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
On Thu, Jun 14, 2001 at 08:59:16PM +0200, Karsten W. Rohrbach wrote:
Peter Pentchev([EMAIL PROTECTED])@2001.06.14 20:19:27 +:
OK, and what do I do if I want to manually start/stop the service later,
and it needs variables defined in /etc/rc.conf{,local} ?
if [ x${_RC_CONF} != x1 ];
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
the idea is to modify /etc/rc to not start stuff in /usr/local/etc/rc.d
blindly,
and just 'extrapolate' rc.conf.
you can still start/stop the /usr/local/etc/rc.d/*.sh to your heart content,
i didn't propose changing them, though modifying mysql-server.sh to
mysql_server.sh would make things
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
On Thu, Jun 14, 2001 at 11:57:18AM -0700, Gordon Tetlow wrote:
On Thu, 14 Jun 2001, Warner Losh wrote:
With all due respect to Eivind, he's reinventing the wheel. I'd like
to see NetBSD's brought in with an absolute minimum of change.
Along those lines, I'm typing on my laptop that is
Also, NetBSD doesn't seem to formalize chaining to /usr/pkg/etc/rc.d or
/usr/local/etc/rc.d, unless I missed that.
packages are given startup space in /etc/rc.conf.d/$command, where
$command is setby the first argument to load_rc_config.
-Kevin Way
To Unsubscribe: send mail to [EMAIL
On Thu, 14 Jun 2001, Andrew Hesford wrote:
On Thu, Jun 14, 2001 at 11:57:18AM -0700, Gordon Tetlow wrote:
I've also made some (slight) changes to the boot order. Mostly just
formalizing the lock step nature of things. I did make one change that I
think will be helpful, I moved pccard
First, there are some weaknesses in netbsd's system that we don't want
to replicate.
Are these identified yet?
Second, Eivind has already done some excellent work in this area.
I'm guessing this code dates to before the new NetBSD startup system. It
almost looks like this could've been
On Thu, 14 Jun 2001, Kevin Way wrote:
Also, NetBSD doesn't seem to formalize chaining to /usr/pkg/etc/rc.d or
/usr/local/etc/rc.d, unless I missed that.
packages are given startup space in /etc/rc.conf.d/$command, where
$command is setby the first argument to load_rc_config.
I like the
Warner Losh [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] Doug Barton writes:
: in fact, the require keyword isn't sufficient in it's own. there
: should be pre_require and post_require keywords since nfsd needs to
: start mountd before to start nfsd then rpc.statd and rpc.lockd
Robert Watson [EMAIL PROTECTED] writes:
On Thu, 14 Jun 2001, Koster, K.J. wrote:
[snip]
How about /var/run/{$deamon}.pid?
So, one of the things I've always hated (and loved) about UNIX is the pid
system. One of the problems I have with (foo).pid is that pid's are
rapidly recycled, so
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
Koster, K.J. [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
Dear All,
To do some of the hierarchal start/stop at runtime stuff, you
really need
a stateful rc system that stores its start/stop state in
/var/run/rc.d or
the like. In this way, the system could track
On Thu, 14 Jun 2001, Andrew Hesford wrote:
Date: Thu, 14 Jun 2001 14:42:45 -0500
On Thu, Jun 14, 2001 at 11:57:18AM -0700, Gordon Tetlow wrote:
I take objection to the moving of pccard before mounting /usr. It works
just fine for those who place /var on the same partition as /, but for
:
:On Thu, 14 Jun 2001, Matt Dillon wrote:
:
:My advise: First make it work. THEN make it work better.
:
: Excellent advice, as long as you don't skip the steps of
:appropriately defining the problem domain and evaluating all of the
:possible solutions for it.
Well, now mind you
On Thu, 14 Jun 2001, Matt Dillon wrote:
:
:On Thu, 14 Jun 2001, Matt Dillon wrote:
:
:My advise: First make it work. THEN make it work better.
:
: Excellent advice, as long as you don't skip the steps of
:appropriately defining the problem domain and evaluating all of the
Hello Robert,
Thursday, June 14, 2001, 11:39:37 PM, you wrote:
RW On Thu, 14 Jun 2001, Koster, K.J. wrote:
To do some of the hierarchal start/stop at runtime stuff, you
really need
a stateful rc system that stores its start/stop state in
/var/run/rc.d or
the like. In this way,
http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm
Any obvious reasons why FreeBSD performed so poorly for these people?
rsi
--
[EMAIL PROTECTED] a.k.a. Rajappa Iyer.
They also surf who stand in the waves.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Thu, Jun 14, 2001 at 10:23:21PM -0400, Rajappa Iyer wrote:
http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm
Any obvious reasons why FreeBSD performed so poorly for these people?
Hrm... the filesystem test, I think, is fairly obvious. The default
filesystem configuration
* Rajappa Iyer [EMAIL PROTECTED] [010614 22:23] wrote:
http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm
Any obvious reasons why FreeBSD performed so poorly for these people?
Because they did benchmarks on systems without tuning.
A simple email to the lists asking for help would
On Fri, 15 Jun 2001, Alfred Perlstein wrote:
* Rajappa Iyer [EMAIL PROTECTED] [010614 22:23] wrote:
http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm
Any obvious reasons why FreeBSD performed so poorly for these people?
Because they did benchmarks on systems without
On Thursday 14 June 2001 9:13, Alfred Perlstein wrote:
* Rajappa Iyer [EMAIL PROTECTED] [010614 22:23] wrote:
http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm
Any obvious reasons why FreeBSD performed so poorly for these people?
Because they did benchmarks on systems
On Thu, 14 Jun 2001, Warner Losh wrote:
With all due respect to Eivind, he's reinventing the wheel. I'd like
to see NetBSD's brought in with an absolute minimum of change.
If the project decides that this is the direction we want to take,
so be it. The point I don't want to get lost
My advise: First make it work. THEN make it work better.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
On Thu, 14 Jun 2001, Matt Dillon wrote:
My advise: First make it work. THEN make it work better.
Excellent advice, as long as you don't skip the steps of
appropriately defining the problem domain and evaluating all of the
possible solutions for it.
--
If you're never wrong,
On Thu, 14 Jun 2001, Devin Butterfield wrote:
So why doesn't FreeBSD ship with a tuned configuration? Just curious...
--
Regards, Devin.
Why? Because you haven't sent in the changes which would implement it
yet. :)
Rather than a tuned configuration, what would be useful is a script that
Mike Silbersack wrote:
Matt's performance manpage covers a lot of this, but is probably not as
easy to digest as an interactive script.
What do I type to read this man page?
--
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
To Unsubscribe: send mail
On 15 Jun 2001 at 00:38 (-0500), Stephen Montgomery-Smith wrote:
| Mike Silbersack wrote:
|
|
| Matt's performance manpage covers a lot of this, but is probably not as
| easy to digest as an interactive script.
|
|
| What do I type to read this man page?
$ man tuning
To Unsubscribe:
52 matches
Mail list logo
