OpenSSH 2.1

[Kris Kennaway]

Okay, I've just committed OpenSSH 2.1 to -current. It was a difficult
merge because the OpenSSH guys basically ripped apart the source code when
they were rearranging it for SSH2 support, so I hope I put all of our
local changes back in the right places. I've tested this as much as I
could locally, but not all of the possibilities.

New in this version:

* SSH2 support. See www.openssh.com for interoperability details with
other SSH2 clients (I tested it with the ssh2 port and it seemed to work
well). See /usr/src/crypto/openssh/README.openssh2 for some brief
installation/operation notes, as well as the manpages. Note that if you
don't create a DSA key manually then one will be created for you on next
boot if you have sshd_enable=yes in your rc.conf

* OPIE support. This only works with the SSH1 protocol, unfortunately. I
still need to improve the way the sshd generates fake challenges for
nonexistent users, but it makes some attempt at present.

* Kerberos support is also limited to SSH1.

* No longer a dependency on RSA (and therefore rsaref for US folks): SSH2
can handle DSA keys which have no patent or usage restrictions. This means
we could now enable SSH2 out of the box in a crypto installation, with no
post-installation configuration requirements. We now have a truly free SSH
client/server!

Please let me know of any problems you find in the new code.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

cvsup6.freebsd.org

[Donn Miller]

It seems to be responding very well to ping, but when I connect to
this server with cvsup, it basically says "connecting to
cvsup6.freebsd.org", and does nothing else.  Is this server working?

 
- Donn


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have acurrent that compiles?)

[Brian W. Buchanan]

On Mon, 15 May 2000, Greg Lehey wrote:

> > I see this money scheme as an extension of the "finger pointing"
> > which does nothing to build team spirit.
> 
> That depends very much on the way it's taken.  At the moment, people
> take the pointy hat voluntarily, not because it's forced on them.
> It's my expectation that the $5 should be in the the same spirit.

Exactly... it's not meant to be a complicated system of fines or to
discourage people from developing (at Desktop, we certainly don't want
that!), it's just a little bit of good-natured public humiliation to
encourage people to think (and maybe test) before they commit. :-)

- Brian Buchanan
[EMAIL PROTECTED]
[EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Greg Lehey]

On Monday, 15 May 2000 at 13:48:19 +1000, Darren Reed wrote:
> In some email I received from Greg Lehey, sie wrote:
>> On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
>>> On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:

>>> Maybe the comitters ought to take an idea from many software companies and
>>> contribute $5 to the beer fund every time they break the build.  Have it
>>> all come due at the next BSDcon to fund a committer beer bash. :-)
>
> I think that we should make it $5.00 the first time.  $10 the second
> time.  $20 the third time, etc.
>>>
>>> Or perhaps we should tie it to the time it takes the security officer
>>> to fix, either with his own patches or by inviting patches from
>>> others, security holes that have been reported in certain libraries.
>>> If it takes the committer longer to fix the world breakage than it
>>> takes the security officer to deal with the hole, then the committer
>>> may be fined.  In all other cases, the security officer can be fined.
>>> At committer's discretion.
>>>
>>> We can then add bonuses.  Say, for example, I fix someone else's world
>>> breakage fast enough that they are able to avoid the fine, then they
>>> have to pay me either $5.00, $10, or $20.
>>>
>>> In cases where more than one committer was responsible, either
>>> indirectly or directly, then all involved should be fined.
>>
>> I think you're missing the point.  The intention was the equivalent of
>> the pointy hat, just with the additional benefit that others might
>> have something out of it as well, no more.
>
> Just one other thing to add here...
>
> How often is it that the actions of just one person make the build
> fail ?

In nearly every case.

> I imagine if one person commits code, it works and bulids cleanly
> for them, but it's when it's imported into a source tree that others
> have changed that the previous compile-testing can be rendered
> useless.

I'd suggest it's more normally superficial testing.

> If anything, such moves as this will make people less likely to
> commit code and hence further impede the development of FreeBSD.  I
> know I personally do not have the resources (both physical and
> otherwise) to maintain a FreeBSD-current system to test any change I
> might want to commit.
>
> I see this money scheme as an extension of the "finger pointing"
> which does nothing to build team spirit.

That depends very much on the way it's taken.  At the moment, people
take the pointy hat voluntarily, not because it's forced on them.
It's my expectation that the $5 should be in the the same spirit.

On Sunday, 14 May 2000 at 23:50:08 -0400, Kent Hauser wrote:
> Hi all,
>
> I think I might have an even better solution. Continue passing the
> pointy hat around & I'll buy the committer's keg at the next
> BSDcon. I for one appreciate the exceptional funcitionality of
> FreeBSD (especially the IPSec support). And also, if I buy the key,
> maybe I'll also be invited.

Everybody's invited.  And yes, we'll gratefully accept the keg.  But
that has nothing to do with the original idea :-)

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Kent Hauser]

Hi all,

I think I might have an even better solution. Continue passing
the pointy hat around & I'll buy the committer's keg at the
next BSDcon. I for one appreciate the exceptional funcitionality
of FreeBSD (especially the IPSec support). And also, if I buy the
key, maybe I'll also be invited.

Regards all,
Kent


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Darren Reed]

In some email I received from Greg Lehey, sie wrote:
> On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
> > On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
> >>
> > Maybe the comitters ought to take an idea from many software companies and
> > contribute $5 to the beer fund every time they break the build.  Have it
> > all come due at the next BSDcon to fund a committer beer bash. :-)
> >>>
> >>> I think that we should make it $5.00 the first time.  $10 the second
> >>> time.  $20 the third time, etc.
> >
> > Or perhaps we should tie it to the time it takes the security officer
> > to fix, either with his own patches or by inviting patches from
> > others, security holes that have been reported in certain libraries.
> > If it takes the committer longer to fix the world breakage than it
> > takes the security officer to deal with the hole, then the committer
> > may be fined.  In all other cases, the security officer can be fined.
> > At committer's discretion.
> >
> > We can then add bonuses.  Say, for example, I fix someone else's world
> > breakage fast enough that they are able to avoid the fine, then they
> > have to pay me either $5.00, $10, or $20.
> >
> > In cases where more than one committer was responsible, either
> > indirectly or directly, then all involved should be fined.
> 
> I think you're missing the point.  The intention was the equivalent of
> the pointy hat, just with the additional benefit that others might
> have something out of it as well, no more.

Just one other thing to add here...

How often is it that the actions of just one person make the build fail ?

I imagine if one person commits code, it works and bulids cleanly for them,
but it's when it's imported into a source tree that others have changed that
the previous compile-testing can be rendered useless.  If anything, such
moves as this will make people less likely to commit code and hence further
impede the development of FreeBSD.  I know I personally do not have the
resources (both physical and otherwise) to maintain a FreeBSD-current system
to test any change I might want to commit.

I see this money scheme as an extension of the "finger pointing" which does
nothing to build team spirit.

Darren

p.s. since there was no currency specified, I imagine "$5 local", wherever
that maybe, so the Italians would get off light at 5Lire :)
p.p.s. for those of you that live inside the USA, sending such small amounts
of money to the USA will cost more than the penalty, more than likely.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Greg Lehey]

On Sunday, 14 May 2000 at 23:21:21 -0400, Tim Vanderhoek wrote:
> On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
>>
> Maybe the comitters ought to take an idea from many software companies and
> contribute $5 to the beer fund every time they break the build.  Have it
> all come due at the next BSDcon to fund a committer beer bash. :-)
>>>
>>> I think that we should make it $5.00 the first time.  $10 the second
>>> time.  $20 the third time, etc.
>
> Or perhaps we should tie it to the time it takes the security officer
> to fix, either with his own patches or by inviting patches from
> others, security holes that have been reported in certain libraries.
> If it takes the committer longer to fix the world breakage than it
> takes the security officer to deal with the hole, then the committer
> may be fined.  In all other cases, the security officer can be fined.
> At committer's discretion.
>
> We can then add bonuses.  Say, for example, I fix someone else's world
> breakage fast enough that they are able to avoid the fine, then they
> have to pay me either $5.00, $10, or $20.
>
> In cases where more than one committer was responsible, either
> indirectly or directly, then all involved should be fined.

I think you're missing the point.  The intention was the equivalent of
the pointy hat, just with the additional benefit that others might
have something out of it as well, no more.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Tim Vanderhoek]

On Sun, May 14, 2000 at 10:23:07PM -0400, Tim Vanderhoek wrote:
>
 Maybe the comitters ought to take an idea from many software companies and
 contribute $5 to the beer fund every time they break the build.  Have it
 all come due at the next BSDcon to fund a committer beer bash. :-)
>> 
>> I think that we should make it $5.00 the first time.  $10 the second
>> time.  $20 the third time, etc.

Or perhaps we should tie it to the time it takes the security officer
to fix, either with his own patches or by inviting patches from
others, security holes that have been reported in certain libraries.
If it takes the committer longer to fix the world breakage than it
takes the security officer to deal with the hole, then the committer
may be fined.  In all other cases, the security officer can be fined.
At committer's discretion.

We can then add bonuses.  Say, for example, I fix someone else's world
breakage fast enough that they are able to avoid the fine, then they
have to pay me either $5.00, $10, or $20.

In cases where more than one committer was responsible, either
indirectly or directly, then all involved should be fined.


-- 
Signature withheld by request of author.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Tim Vanderhoek]

On Sun, May 14, 2000 at 11:06:50AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : > Maybe the comitters ought to take an idea from many software companies and
> : > contribute $5 to the beer fund every time they break the build.  Have it
> : > all come due at the next BSDcon to fund a committer beer bash. :-)
> 
> I think that we should make it $5.00 the first time.  $10 the second
> time.  $20 the third time, etc.

I think this'd be a great idea, provided we also implemented some sort
of scheme that paid for committer time that was wasted as a result of
reading needless crossposts that add little to one of the lists and
nothing to the other.


-- 
Signature withheld by request of author.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposed patch for PR misc/18466

[Matthew Dillon]

:Matthew Dillon <[EMAIL PROTECTED]> writes:
:> Index: anonFTP.c
:> ===
:> RCS file: /home/ncvs/src/release/sysinstall/anonFTP.c,v
:> retrieving revision 1.29
:> diff -u -r1.29 anonFTP.c
:> --- anonFTP.c2000/01/25 19:16:31 1.29
:> +++ anonFTP.c2000/05/14 17:44:11
:> @@ -217,7 +217,7 @@
:>  SAFE_STRCPY(tconf.upload, FTP_UPLOAD);
:>  SAFE_STRCPY(tconf.comment, FTP_COMMENT);
:>  SAFE_STRCPY(tconf.homedir, FTP_HOMEDIR);
:
:why not call strlcpy instead of the SAFE_STRCPY macro that calls the
:sstrncpy and the strncpy?

I didn't write SAFE_STRCPY.  Replacement is a good idea, but
would be future work.

:> -char *line = malloc(21);
:> -sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
:> +char *line = malloc(URMSIZE);
:> +snprintf(line, URMSIZE, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
:>  lines[0] = line;
:>  nlines = 1;
:>  }
:
:Why not call asprintf/safe_asprintf here?

Look a little down in the code, you will notice that it rewrites 
the buffer.  asprintf only allocates what it needs, which may
not be enough.

(If I had written it I would have simply reallocated the buffer,
but since I didn't this would be a future improvement to make).

:> +void
:> +safe_asprintf(char **pptr, const char *ctl, ...)
:
:It would seem to me a good idea to make a v-version of this function,
:even if there's no place right now that wants to call it.
:
:/assar

Under normal conditions, yes, but there is not a single line of code
in sysinstall which uses varargs, and it only takes 10 seconds to
add a v-version so we'll leave that for another pass (perhaps a
later pass to get rid of all the static buffers).

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Real Player not working

[emre]

FUJISHIMA Satsuki wrote:

> branded as FreeBSD with old method and then it will always be treated
> as FreeBSD binary. The effort to brand it as Linux with new method
> will be ignored.
>
> Stripping Linux binary with Linux strip would be a workaround.

Following Sean O'Connell's advice, I downloaded Real Player 7.0 (beta) from real.com,
put it into /usr/compat/linux/opt and installed it.  It worked.  I see alot of 
"lagging" when I
use it though.  The same media clips run smoother in the windows version of real 
player,
but I'm not really surprised, as this player is still in "beta".  At least it works 
now.

Thanks for all the help

Cheers



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

kern/18524 - SMP cpu stats

[Arun Sharma]

Can someone responsible for SMP please look at this PR:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18524

This is necessary for tools like xosview, ktop etc to display per cpu
stats.

-Arun


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Make World kdump failure

[David O'Brien]

On Sun, May 14, 2000 at 05:02:48PM +, Andrew M. Miklic wrote:
> I'm getting a "make world" failure with Alpha -current (cvsup'ed fresh
> as of a few minutes ago, although this problem has persisted for over a
> week, as far as I can tell)..it seems to be dying in kdump, strangely
> apparently on i386-specific stuff.

I'll try to take a look at fixing this.

> Is anyone else seeing this?

Yes.  I just removed kdump from usr.bin/Makefile as I was busy doing
other development.
 
-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Warning on boot

[Assar Westerlund]

"Andrew Tulloch" <[EMAIL PROTECTED]> writes:
> Device char-major=116 minor=196608 opened in block mode, convert to char
> mode with /dev/MAKEDEV before 2000-07-01

It has been fixed in sys/kern/vfs_subr.c:1.255.  cvsup or grab the
patch and apply.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[David O'Brien]

On Sun, May 14, 2000 at 02:50:02PM -0500, Steve Price wrote:
> I too like this idea and along the lines of what Lyndon suggested
> how about the attached patch instead?

This is a better patch to the proposed functionality.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[David O'Brien]

On Sun, May 14, 2000 at 03:46:40PM -0400, Will Andrews wrote:
> Ok, what do other people think?  I mean, it'd be easy to change the flag to
> use this feature.  -dl seems fine for this particular feature.

-d is a better place to put this than "-l", as this is a debugging
feature.
 
-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Review and commit of bin/14911?

[Lyndon Nerenberg]

> "David" == David O'Brien <[EMAIL PROTECTED]> writes:

David> You might get more interest if you mention what the PR
David> fixes.

It adds missing binary/manpage links from opiekey to otp-md4 and otp-md5.

Some of our remote users run software that semi-automates OTP logins,
and that software expects the otp-* commands to be on the remote system.
The opiekey(1) manpage also mentions the otp-* commands by name.

--lyndon


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Review and commit of bin/14911?

[David O'Brien]

On Sun, May 14, 2000 at 01:14:19PM -0600, Lyndon Nerenberg wrote:
> Could someone with commit privs please take a look at bin/14911? I'd

You might get more interest if you mention what the PR fixes.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposed patch for PR misc/18466

[Assar Westerlund]

Matthew Dillon <[EMAIL PROTECTED]> writes:
> Index: anonFTP.c
> ===
> RCS file: /home/ncvs/src/release/sysinstall/anonFTP.c,v
> retrieving revision 1.29
> diff -u -r1.29 anonFTP.c
> --- anonFTP.c 2000/01/25 19:16:31 1.29
> +++ anonFTP.c 2000/05/14 17:44:11
> @@ -217,7 +217,7 @@
>  SAFE_STRCPY(tconf.upload, FTP_UPLOAD);
>  SAFE_STRCPY(tconf.comment, FTP_COMMENT);
>  SAFE_STRCPY(tconf.homedir, FTP_HOMEDIR);

why not call strlcpy instead of the SAFE_STRCPY macro that calls the
sstrncpy and the strncpy?

> Index: config.c
> ===
> RCS file: /home/ncvs/src/release/sysinstall/config.c,v
> retrieving revision 1.156.2.1
> diff -u -r1.156.2.1 config.c
> --- config.c  2000/03/30 08:12:02 1.156.2.1
> +++ config.c  2000/05/14 17:46:38
> @@ -373,8 +375,8 @@
>  FILE *fp;
>  
>  if (!file_readable(config)) {
> - char *line = malloc(21);
> - sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
> + char *line = malloc(URMSIZE);
> + snprintf(line, URMSIZE, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
>   lines[0] = line;
>   nlines = 1;
>  }

Why not call asprintf/safe_asprintf here?

> Index: misc.c
> ===
> RCS file: /home/ncvs/src/release/sysinstall/misc.c,v
> retrieving revision 1.40
> diff -u -r1.40 misc.c
> --- misc.c1999/11/27 14:33:07 1.40
> +++ misc.c2000/05/14 17:55:41
> @@ -34,6 +34,7 @@
>  #include "sysinstall.h"
>  #include 
>  #include 
> +#include 
>  #include 
>  #include 
>  #include 
> @@ -209,6 +210,17 @@
>  if (!ptr)
>   msgFatal("Out of memory!");
>  return ptr;
> +}
> +
> +void
> +safe_asprintf(char **pptr, const char *ctl, ...)
> +{
> +va_list va;
> +
> +va_start(va, ctl);
> +if (vasprintf(pptr, ctl, va) < 0)
> + msgFatal("Out of memory!");
> +va_end(va);
>  }
>  /* Create a path biased from the VAR_INSTALL_ROOT variable (if not /) */

It would seem to me a good idea to make a v-version of this function,
even if there's no place right now that wants to call it.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[Lyndon Nerenberg]

Chuck> Compatibility with those other makes is pretty low to begin
Chuck> with, but it doesn't hurt, I guess, to allow for this.  -dl
Chuck> is ok with me.  I just wouldn't consider the compatibility
Chuck> thing a real issue if it weren't this easy to satisfy.

It's not a big deal for me. I just get annoyed at all the seemingly
gratuitous incompatibilities between the different versions of
something as fundamental as make.

--lyndon


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: vn.ko load/unload/mount = panic

[Mike Smith]

> In message , Nick Hibma wri
> tes:
> >
> >Correct me if I am wrong, but I don't think you actually have to
> >disassociate any dev_t's from the driver (by clearing the si_drv[12]
> >fields) because we call destroy_dev and cdevsw_remove, so any later uses
> >of dev_t's get an error because the device has gone away.
> 
> destroy_dev will clear the necessary fields in a dev_t, cdevsw_remove
> will not.

Is it correct to assume that destroy_dev() still isn't working correctly? 
(disk_destroy certainly isn't).

Also, while you still can, that should be dev_destroy().

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: vn.ko load/unload/mount = panic

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> In message , Nick Hibma wri
>> tes:
>> >
>> >Correct me if I am wrong, but I don't think you actually have to
>> >disassociate any dev_t's from the driver (by clearing the si_drv[12]
>> >fields) because we call destroy_dev and cdevsw_remove, so any later uses
>> >of dev_t's get an error because the device has gone away.
>> 
>> destroy_dev will clear the necessary fields in a dev_t, cdevsw_remove
>> will not.
>
>Is it correct to assume that destroy_dev() still isn't working correctly? 
>(disk_destroy certainly isn't).

disk_destroy is different from destroy_dev, and I'll get to it real soon.

>Also, while you still can, that should be dev_destroy().

No, because the corresponding is called make_dev().

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles

[Chuck Robey]

On Sun, 14 May 2000, Will Andrews wrote:

> On Sun, May 14, 2000 at 01:25:16PM -0600, Lyndon Nerenberg wrote:
> > I like the idea, but the -l flag conflicts with a different usage for
> > SVR4 derived makes (on at least AIX, Irix, and Solaris):
> > 
> >   -l load
> >Specifies that no new jobs (commands) should be started
> >if there are others jobs running and the load average
> >is at least load (a floating-point number).  With no
> >argument, removes a previous load limit.

Compatibility with those other makes is pretty low to begin with, but it
doesn't hurt, I guess, to allow for this.  -dl is ok with me.  I just
wouldn't consider the compatibility thing a real issue if it weren't this
easy to satisfy.


Chuck Robey| Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles

[Steve Price]

On Sun, 14 May 2000, Will Andrews wrote:

# Some time ago I was complaining about how there is no way to force make(1)
# to display the commands executed by @-prefixed commands in Makefiles.
[snip]

I too like this idea and along the lines of what Lyndon suggested
how about the attached patch instead?  Aside from being somewhat
poorly named my hat's off to you for coming up with such a simple
solution to a (mis)feature that has bugged me for a long time. :)

-steve


Index: compat.c
===
RCS file: /home/ncvs/src/usr.bin/make/compat.c,v
retrieving revision 1.17
diff -u -r1.17 compat.c
--- compat.c2000/04/14 06:39:10 1.17
+++ compat.c2000/05/14 19:40:52
@@ -240,7 +240,7 @@
 
 while ((*cmd == '@') || (*cmd == '-')) {
if (*cmd == '@') {
-   silent = TRUE;
+   silent = DEBUG(LOUD) ? FALSE : TRUE;
} else {
errCheck = FALSE;
}
Index: job.c
===
RCS file: /home/ncvs/src/usr.bin/make/job.c,v
retrieving revision 1.17
diff -u -r1.17 job.c
--- job.c   2000/01/17 06:43:40 1.17
+++ job.c   2000/05/14 19:40:34
@@ -555,7 +555,7 @@
  */
 while (*cmd == '@' || *cmd == '-') {
if (*cmd == '@') {
-   shutUp = TRUE;
+   shutUp = DEBUG(LOUD) ? FALSE : TRUE;
} else {
errOff = TRUE;
}
Index: main.c
===
RCS file: /home/ncvs/src/usr.bin/make/main.c,v
retrieving revision 1.35
diff -u -r1.35 main.c
--- main.c  1999/11/23 10:35:24 1.35
+++ main.c  2000/05/14 19:37:40
@@ -262,6 +262,9 @@
case 'j':
debug |= DEBUG_JOB;
break;
+   case 'l':
+   debug |= DEBUG_LOUD;
+   break;
case 'm':
debug |= DEBUG_MAKE;
break;
Index: make.h
===
RCS file: /home/ncvs/src/usr.bin/make/make.h,v
retrieving revision 1.12
diff -u -r1.12 make.h
--- make.h  1999/09/11 13:17:35 1.12
+++ make.h  2000/05/14 19:41:05
@@ -359,7 +359,8 @@
 #defineDEBUG_SUFF  0x0080
 #defineDEBUG_TARG  0x0100
 #defineDEBUG_VAR   0x0200
-#define DEBUG_FOR  0x0400
+#defineDEBUG_FOR   0x0400
+#defineDEBUG_LOUD  0x0800
 
 #ifdef __STDC__
 #define CONCAT(a,b)a##b

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[Will Andrews]

On Sun, May 14, 2000 at 01:25:16PM -0600, Lyndon Nerenberg wrote:
> I like the idea, but the -l flag conflicts with a different usage for
> SVR4 derived makes (on at least AIX, Irix, and Solaris):
> 
>   -l load
>Specifies that no new jobs (commands) should be started
>if there are others jobs running and the load average
>is at least load (a floating-point number).  With no
>argument, removes a previous load limit.
> 
> Maybe this should instead be a -d sub-option?
> 
> And I like the idea of adding the -l functionality described above.

Ok, what do other people think?  I mean, it'd be easy to change the flag to
use this feature.  -dl seems fine for this particular feature.

-- 
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ 
G++>+++ e-> h! r-->+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[Lyndon Nerenberg]

I like the idea, but the -l flag conflicts with a different usage for
SVR4 derived makes (on at least AIX, Irix, and Solaris):

  -l load
   Specifies that no new jobs (commands) should be started
   if there are others jobs running and the load average
   is at least load (a floating-point number).  With no
   argument, removes a previous load limit.

Maybe this should instead be a -d sub-option?

And I like the idea of adding the -l functionality described above.

--lyndon


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixedcommands in Makefiles

[Chuck Robey]

On Sun, 14 May 2000, Will Andrews wrote:

> Hi all,
> 
> Some time ago I was complaining about how there is no way to force make(1)
> to display the commands executed by @-prefixed commands in Makefiles.  So I
> went around and talked to a few people and one guy clued me in on how I
> would add something like this (sorry, I don't remember the name right now
> as this was a few weeks ago..).
> 
> This option is useful for people with complex Makefile hierarchies who
> cannot simply insert a `@${ECHO} "SOMEVAR = ${SOMEVAR}"` as needed in their
> Makefiles or remove all the @'s in their Makefiles. In particular, I would
> use this feature to debug ports.
> 
> Attached is the patch.  If I can get permission, I'd like to commit this to
> code on -current, with a possible MFC in a few weeks (?).  I'd like to hear
> any complaints about this code, including any style(9) mistakes, whether
> this option would be considered bloat, and whether the variable name
> ``beLoud'' is appropriate in this context.  ;-)

Oh, what a nice present!  Thanks!

> 
> Thanks,
> 


Chuck Robey| Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED]  | electronics, communications, and signal processing.

New Year's Resolution:  I will not sphroxify gullible people into looking up
fictitious words in the dictionary.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Review and commit of bin/14911?

[Lyndon Nerenberg]

Could someone with commit privs please take a look at bin/14911? I'd
really appreciate it if that could get committed, and MFC'd into
RELENG_4. Also, bin/6997 has been aging away for quite some time as
well.

Thanks,

--lyndon


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[Poul-Henning Kamp]

It sounds like a useful feature to me.


--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles

[Will Andrews]

Hi all,

Some time ago I was complaining about how there is no way to force make(1)
to display the commands executed by @-prefixed commands in Makefiles.  So I
went around and talked to a few people and one guy clued me in on how I
would add something like this (sorry, I don't remember the name right now
as this was a few weeks ago..).

This option is useful for people with complex Makefile hierarchies who
cannot simply insert a `@${ECHO} "SOMEVAR = ${SOMEVAR}"` as needed in their
Makefiles or remove all the @'s in their Makefiles. In particular, I would
use this feature to debug ports.

Attached is the patch.  If I can get permission, I'd like to commit this to
code on -current, with a possible MFC in a few weeks (?).  I'd like to hear
any complaints about this code, including any style(9) mistakes, whether
this option would be considered bloat, and whether the variable name
``beLoud'' is appropriate in this context.  ;-)

Thanks,
-- 
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ 
G++>+++ e-> h! r-->+++ y?


Index: compat.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/compat.c,v
retrieving revision 1.17
diff -u -r1.17 compat.c
--- compat.c2000/04/14 06:39:10 1.17
+++ compat.c2000/05/13 17:38:22
@@ -241,6 +241,8 @@
 while ((*cmd == '@') || (*cmd == '-')) {
if (*cmd == '@') {
silent = TRUE;
+   if (beLoud)
+   silent = FALSE;
} else {
errCheck = FALSE;
}
Index: job.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/job.c,v
retrieving revision 1.17
diff -u -r1.17 job.c
--- job.c   2000/01/17 06:43:40 1.17
+++ job.c   2000/05/13 17:38:12
@@ -556,6 +556,8 @@
 while (*cmd == '@' || *cmd == '-') {
if (*cmd == '@') {
shutUp = TRUE;
+   if (beLoud)
+   shutUp = FALSE;
} else {
errOff = TRUE;
}
Index: main.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/main.c,v
retrieving revision 1.35
diff -u -r1.35 main.c
--- main.c  1999/11/23 10:35:24 1.35
+++ main.c  2000/05/13 17:47:35
@@ -138,6 +138,7 @@
 BooleanbeVerbose;  /* -v flag */
 BooleanoldVars;/* variable substitution style */
 BooleancheckEnvFirst;  /* -e flag */
+BooleanbeLoud; /* -l flag */
 LstenvFirstVars;   /* (-E) vars to override from env */
 static Boolean jobsRunning;/* TRUE if the jobs might be running */
 
@@ -175,9 +176,9 @@
 
optind = 1; /* since we're called more than once */
 #ifdef REMOTE
-# define OPTFLAGS "BD:E:I:L:PSV:d:ef:ij:km:nqrstv"
+# define OPTFLAGS "BD:E:I:L:PSV:d:ef:ij:klm:nqrstv"
 #else
-# define OPTFLAGS "BD:E:I:PSV:d:ef:ij:km:nqrstv"
+# define OPTFLAGS "BD:E:I:PSV:d:ef:ij:klm:nqrstv"
 #endif
 rearg: while((c = getopt(argc, argv, OPTFLAGS)) != -1) {
switch(c) {
@@ -322,6 +323,10 @@
case 'k':
keepgoing = TRUE;
Var_Append(MAKEFLAGS, "-k", VAR_GLOBAL);
+   break;
+   case 'l':
+   beLoud = TRUE;
+   Var_Append(MAKEFLAGS, "-l", VAR_GLOBAL);
break;
case 'm':
Dir_AddDir(sysIncPath, optarg);
Index: make.h
===
RCS file: /extra/cvsroot/src/usr.bin/make/make.h,v
retrieving revision 1.12
diff -u -r1.12 make.h
--- make.h  1999/09/11 13:17:35 1.12
+++ make.h  2000/05/13 17:41:09
@@ -322,6 +322,8 @@
 
 extern Boolean checkEnvFirst;  /* TRUE if environment should be searched for
 * all variables before the global context */
+extern Boolean beLoud; /* Force all commands to be outputted; ignores
+* @-prefixes, etc. */
 extern Lst envFirstVars;   /* List of specific variables for which the
 * environment should be searched before the
 * global context */

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Will Andrews]

On Sun, May 14, 2000 at 10:19:21AM +0930, Greg Lehey wrote:
> I'd go along with that.  What do the other committers think?

Can I drink pop instead?  I'm underage, and I don't like alcohol anyway. :)

-- 
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ 
G++>+++ e-> h! r-->+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Proposed patch for PR misc/18466

[Matthew Dillon]

This is a general bounded-buffer patch for sysinstall plus it fixes
PR misc/18466 (limited 'device name' size screws up FTP installs).
It does not fix all the potential buffer overflows -- there are still
a lot of strcpy's, but it gets half way there with the introduction
and use of safe_asprintf().

My recommendation is that (eventually) the entire program use asprintf
rather then statically-bounded buffers to hold things.

I don't have time to test this extensively so if the maintainer of
sysinstall wants it (I believe that's you, Jordan!), you'll need to
review it and perhaps test it a little then give me the commit goahead.

Note that simply increasing the DEV_NAME_MAX as a quick solution is
not safe, there are a couple of places where an unbounded sprintf() 
was being used with the device name as an argument.

-Matt

Index: anonFTP.c
===
RCS file: /home/ncvs/src/release/sysinstall/anonFTP.c,v
retrieving revision 1.29
diff -u -r1.29 anonFTP.c
--- anonFTP.c   2000/01/25 19:16:31 1.29
+++ anonFTP.c   2000/05/14 17:44:11
@@ -168,7 +168,7 @@
return DITEM_SUCCESS;   /* succeeds if already exists */
 }
 
-sprintf(pwline, "%s:*:%s:%d::0:0:%s:%s:/nonexistent\n", FTP_NAME, tconf.uid, gid, 
tconf.comment, tconf.homedir);
+snprintf(pwline, sizeof(pwline), "%s:*:%s:%d::0:0:%s:%s:/nonexistent\n", 
+FTP_NAME, tconf.uid, gid, tconf.comment, tconf.homedir);
 
 fptr = fopen(_PATH_MASTERPASSWD,"a");
 if (! fptr) {
@@ -207,7 +207,7 @@
 ANONFTP_DIALOG_HEIGHT - 11, ANONFTP_DIALOG_WIDTH - 17,
 dialog_attr, border_attr);
 wattrset(ds_win, dialog_attr);
-sprintf(title, " Path Configuration ");
+snprintf(title, sizeof(title), " Path Configuration ");
 mvwaddstr(ds_win, ANONFTP_DIALOG_Y + 7, ANONFTP_DIALOG_X + 22, title);
 
 /** Initialize the config Data Structure **/
@@ -217,7 +217,7 @@
 SAFE_STRCPY(tconf.upload, FTP_UPLOAD);
 SAFE_STRCPY(tconf.comment, FTP_COMMENT);
 SAFE_STRCPY(tconf.homedir, FTP_HOMEDIR);
-sprintf(tconf.uid, "%d", FTP_UID);
+snprintf(tconf.uid, sizeof(tconf.uid), "%d", FTP_UID);
 
 /* Some more initialisation before we go into the main input loop */
 obj = initLayoutDialog(ds_win, layout, ANONFTP_DIALOG_X, ANONFTP_DIALOG_Y, &max);
@@ -250,7 +250,7 @@
 
 /*** Use defaults for any invalid values ***/
 if (atoi(tconf.uid) <= 0)
-   sprintf(tconf.uid, "%d", FTP_UID);
+   snprintf(tconf.uid, sizeof(tconf.uid), "%d", FTP_UID);
 
 if (!tconf.group[0])
SAFE_STRCPY(tconf.group, FTP_GROUP);
@@ -296,7 +296,7 @@
if (!msgYesNo("Create a welcome message file for anonymous FTP users?")) {
char cmd[256];
vsystem("echo Your welcome message here. > %s/etc/%s", tconf.homedir, 
MOTD_FILE);
-   sprintf(cmd, "%s %s/etc/%s", variable_get(VAR_EDITOR), tconf.homedir, 
MOTD_FILE);
+   snprintf(cmd, sizeof(cmd), "%s %s/etc/%s", variable_get(VAR_EDITOR), 
+tconf.homedir, MOTD_FILE);
if (!systemExecute(cmd))
i = DITEM_SUCCESS;
else
Index: config.c
===
RCS file: /home/ncvs/src/release/sysinstall/config.c,v
retrieving revision 1.156.2.1
diff -u -r1.156.2.1 config.c
--- config.c2000/03/30 08:12:02 1.156.2.1
+++ config.c2000/05/14 17:46:38
@@ -238,11 +238,11 @@
 for (i = 0; i < cnt; i++) {
char cdname[10];

-   sprintf(cdname, "/cdrom%s", i ? itoa(i) : "");
+   snprintf(cdname, sizeof(cdname), "/cdrom%s", i ? itoa(i) : "");
if (Mkdir(cdname))
msgConfirm("Unable to make mount point for: %s", cdname);
else
-   fprintf(fstab, "/dev/%s\t\t%s\tcd9660\tro,noauto\t0\t0\n", devs[i]->name, 
cdname);
+   fprintf(fstab, "/dev/%s\t\t%s\tcd9660\tro,noauto\t0\t0\n", devs[i]->pname, 
+cdname);
 }
 
 /* And finally, a /proc. */
@@ -364,6 +364,8 @@
 }
 }
 
+#define URMSIZE21
+
 /* Set up the make.conf file */
 void
 configMake_conf(char *config)
@@ -373,8 +375,8 @@
 FILE *fp;
 
 if (!file_readable(config)) {
-   char *line = malloc(21);
-   sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
+   char *line = malloc(URMSIZE);
+   snprintf(line, URMSIZE, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
lines[0] = line;
nlines = 1;
 }
@@ -386,7 +388,7 @@
if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
free(lines[i]);
lines[i] = malloc(21);  /* big enough */
-   sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
+   snprintf(lines[i], URMSIZE, "USA_RESIDENT=%s\n", USAResident ? "YES" : 
+"NO");
}
}
 }
@@ -865,7 +867,7 @@

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

[Warner Losh]

In message <[EMAIL PROTECTED]> Greg Lehey writes:
: > Maybe the comitters ought to take an idea from many software companies and
: > contribute $5 to the beer fund every time they break the build.  Have it
: > all come due at the next BSDcon to fund a committer beer bash. :-)
: 
: I'd go along with that.  What do the other committers think?

I think that we should make it $5.00 the first time.  $10 the second
time.  $20 the third time, etc.

BTW, if the committer fixes this before N amount of time has passwed
(say an hour or two), then there should be no fine.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Linux emulation causes a halt

[Jesper Skriver]

On Sun, May 14, 2000 at 06:29:59PM +0200, Eric Jacoboni wrote:
> > "Jesper" == Jesper Skriver <[EMAIL PROTECTED]> writes:
> 
> Jesper> Just upgraded my laptop from a late march -current to
> Jesper> -current as of a couple of hours ago. 
> 
> Jesper> When it loads the "Linux binary compatibility" it
> Jesper> shutdown, if apm is enabled it looks like when one do a
> Jesper> 'shutdown -p now'. 
> 
> 
> Jesper> Anyone seen anything like this ?
> 
> Have you read /usr/src/UPDATING ?

No, I thought I could remember, but it works now, I think if we could
give a warning instead of a just shutting down, it would be nice.

Next time, I will read UPDATING ...

/Jesper


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Linux emulation causes a halt

[Eric Jacoboni]

> "Jesper" == Jesper Skriver <[EMAIL PROTECTED]> writes:

Jesper> Just upgraded my laptop from a late march -current to
Jesper> -current as of a couple of hours ago. 

Jesper> When it loads the "Linux binary compatibility" it
Jesper> shutdown, if apm is enabled it looks like when one do a
Jesper> 'shutdown -p now'. 


Jesper> Anyone seen anything like this ?

Have you read /usr/src/UPDATING ?

-- 
-
Éric Jacoboni   « No sport, cigars! »  (W. Churchill)
-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Linux emulation causes a halt

[Jesper Skriver]

Hi,

Just upgraded my laptop from a late march -current to -current as of a
couple of hours ago.

When it loads the "Linux binary compatibility" it shutdown, if apm is
enabled it looks like when one do a 'shutdown -p now'.

When I set linux_enable="NO" in /etc/rc.conf the machine boots properly,
but my Linux applications doesn't work.

I did a full buildworld, installworld installed the new kernel, and
updated /etc with mergemaster ...

Anyone seen anything like this ?

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk  -  CCIE #5456
Work:Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek@ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Make World kdump failure

[Andrew M. Miklic]

I'm getting a "make world" failure with Alpha -current (cvsup'ed fresh
as of a few minutes ago, although this problem has persisted for over a
week, as far as I can tell)..it seems to be dying in kdump, strangely
apparently on i386-specific stuff.

Is anyone else seeing this?

(Just in case people are thinking the path has anything to do with it, I
saw the exact same errors when the src tree was rooted /usr--I just
moved it to /usr/local to see if anything would change...)

The stream of errors and warnings is below:

***

===> usr.bin/kdump
sh /usr/local/src/usr.bin/kdump/mkioctls
/usr/obj/usr/local/src/alpha/usr/include > ioctl.c
In file included from :62:
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:51:
opt_pcvt.h: No such file or directory
In file included from
/usr/obj/usr/local/src/alpha/usr/include/sys/param.h:96,
 from
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:53,

 from :62:
/usr/obj/usr/local/src/alpha/usr/include/machine/limits.h:64: warning:
`INT_MAX' redefined
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/include/if_wl_wavelan.h:149:
warning: this is the location of the previous definition
In file included from
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:53,

 from :62:
/usr/obj/usr/local/src/alpha/usr/include/sys/param.h:206: warning: `MAX'
redefined
/usr/obj/usr/local/src/alpha/usr/include/netinet/ip_compat.h:146:
warning: this is the location of the previous definition
In file included from :62:
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:71:
machine/pcvt_ioctl.h: No such file or directory
In file included from :62:
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:77:
dev/kbd/kbdreg.h: No such file or directory
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:78:
dev/kbd/atkbdcreg.h: No such file or directory
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:80:
i386/isa/pcvt/pcvt_conf.h: No such file or directory
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:132:
#error "Supported keyboard scancode sets are 1 and 2 only (for now)!!!"
In file included from :82:
/usr/obj/usr/local/src/alpha/usr/include/sys/sys/cdrio.h:59: warning:
`CDRIOCBLANK' redefined
/usr/obj/usr/local/src/alpha/usr/include/sys/pc98/pc98/wormio.h:102:
warning: this is the location of the previous definition
In file included from :93:
/usr/obj/usr/local/src/alpha/usr/include/sys/sys/kbio.h:47: warning:
`KB_OTHER' redefined
/usr/obj/usr/local/src/alpha/usr/include/sys/i386/isa/pcvt/pcvt_hdr.h:100:
warning: this is the location of the previous definition
In file included from :94:
/usr/obj/usr/local/src/alpha/usr/include/sys/sys/memrange.h:18: warning:
`MDF_ACTIVE' redefined
/usr/obj/usr/local/src/alpha/usr/include/pccard/cardinfo.h:80: warning:
this is the location of the previous definition
rm -f .depend
mkdep -f .depend -a-I/usr/local/src/usr.bin/kdump/../ktrace
-I/usr/local/src/usr.bin/kdump/../..
-I/usr/obj/usr/local/src/alpha/usr/include
/usr/local/src/usr.bin/kdump/kdump.c ioctl.c
/usr/local/src/usr.bin/kdump/../ktrace/subr.c
In file included from ioctl.c:88:
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:51:
opt_pcvt.h: No such file or directory
In file included from ioctl.c:88:
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:71:
machine/pcvt_ioctl.h: No such file or directory
In file included from ioctl.c:88:
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:77:
dev/kbd/kbdreg.h: No such file or directory
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:78:
dev/kbd/atkbdcreg.h: No such file or directory
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:80:
i386/isa/pcvt/pcvt_conf.h: No such file or directory
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:132:
#error "Supported keyboard scancode sets are 1 and 2 only (for now)!!!"
In file included from ioctl.c:108:
/usr/local/src/usr.bin/kdump/../../sys/sys/cdrio.h:59: warning:
`CDRIOCBLANK' redefined
/usr/local/src/usr.bin/kdump/../../sys/pc98/pc98/wormio.h:102: warning:
this is the location of the previous definition
In file included from ioctl.c:119:
/usr/local/src/usr.bin/kdump/../../sys/sys/kbio.h:47: warning:
`KB_OTHER' redefined
/usr/local/src/usr.bin/kdump/../../sys/i386/isa/pcvt/pcvt_hdr.h:100:
warning: this is the location of the previous definition
In file included from ioctl.c:120:
/usr/local/src/usr.bin/kdump/../../sys/sys/memrange.h:18: warning:
`MDF_ACTIVE' redefined
/usr/obj/usr/local/src/alpha/usr/include/pccard/cardinfo.h:80: warning:
this is the location of the previous definition
mkdep: compile failed
*** Error code 1

Stop in /usr/local/src/usr.bin/kdump.
*** Error code 1

Stop in /usr/local/src/usr.bin.
*** Error code 1

Stop i

Re: vn.ko load/unload/mount = panic

[Poul-Henning Kamp]

In message , Nick Hibma wri
tes:
>
>Correct me if I am wrong, but I don't think you actually have to
>disassociate any dev_t's from the driver (by clearing the si_drv[12]
>fields) because we call destroy_dev and cdevsw_remove, so any later uses
>of dev_t's get an error because the device has gone away.

destroy_dev will clear the necessary fields in a dev_t, cdevsw_remove
will not.

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Warning on boot

[Andrew Tulloch]

Hi,
I just up'd my sources to -current to try sblive support out. Did make world
and new kernel but now I get a warning at boot.

Device char-major=116 minor=196608 opened in block mode, convert to char
mode with /dev/MAKEDEV before 2000-07-01

I'm sure it just a simple command to fix, but I don't know what :)

Thanks
Andrew



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: vn.ko load/unload/mount = panic

[Nick Hibma]

Correct me if I am wrong, but I don't think you actually have to
disassociate any dev_t's from the driver (by clearing the si_drv[12]
fields) because we call destroy_dev and cdevsw_remove, so any later uses
of dev_t's get an error because the device has gone away.

Apart from that I don't think we the calls to cdevsw_add/_destroy in the
first place, because we create the cdevsw on demand (with make_dev).

Poul, is this correct?

nick

On Fri, 28 Apr 2000, Peter Edwards wrote:

> I had a longer look at this, and a more complete patch is logged as PR
> kern/18270 (try at your own risk: it works for me).
> I'd appreciate someone more experienced having a look at it and
> commenting.
> Cheers,
> Peter.
> 
> 
> Wilko Bulte wrote:
> > 
> > On Wed, Apr 26, 2000 at 04:25:46PM +0100, Peter Edwards (local) wrote:
> > 
> > How about send-pr ing this stuff?
> > 
> > Wilko
> > 
> > > Hi,
> > > After a (very) quick look at the source it looks like there's a missing
> > > cdevsw_remove() missing from the MOD_UNLOAD/MOD_SHUTDOWN event handling
> > > I haven't time to test it, but try this:
> > >
> > > *** vn.c.oldWed Apr 26 16:23:03 2000
> > > --- vn.cWed Apr 26 16:24:06 2000
> > > ***
> > > *** 762,767 
> > > --- 762,768 
> > > case MOD_UNLOAD:
> > > /* fall through */
> > > case MOD_SHUTDOWN:
> > > +   cdevsw_remove(&vn_cdevsw);
> > > for (;;) {
> > > vn = SLIST_FIRST(&vn_list);
> > > if (!vn)
> > >
> > >
> > > Maxim Sobolev wrote:
> > > >
> > > > Hi,
> > > >
> > > > I've already submitted this crash report earlier but it seems that developers
> > > > in -current list are too busy discussing whether Matt allowed to commit his SMP
> > > > work into 4.0 to pay attention to "ordinary" panic reports :-(. Following is
> > > > slightly simplified course of actions which is known to produce kernel panic on
> > > > both 4.0 and 5.0:
> > > >
> > > > root@notebook# kldstat
> > > > Id Refs AddressSize Name
> > > >  12 0xc010 1c2f48   kernel
> > > >  21 0xc02c3000 30c8 splash_bmp.ko
> > > > root@notebook# mount /dev/vn0c /mnt
> > > > mount: Device not configured
> > > > root@notebook# kldload /modules/vn.ko
> > > > root@notebook# kldstat
> > > > Id Refs AddressSize Name
> > > >  13 0xc010 1c2f48   kernel
> > > >  21 0xc02c3000 30c8 splash_bmp.ko
> > > >  31 0xc0823000 3000 vn.ko
> > > > root@notebook# kldunload -i 3
> > > > root@notebook# mount /dev/vn0c /mnt
> > > > [BINGO]
> > > > Fatal trap 12: page fault while in kernel mode
> > > > [...]
> > > >
> > > > -Maxim
> > 
> > --
> > Wilko Bulte Powered by FreeBSD  http://www.freebsd.org
> > http://www.tcja.nl
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Real Player not working

[FUJISHIMA Satsuki]

At Sat, 13 May 2000 15:45:02 -0500,
emre <[EMAIL PROTECTED]> wrote:
> bash-2.03# rvplayer
> ELF interpreter /lib/ld-linux.so.1 not found
> Abort trap

This is the same problem as ports/18489, caused by binary branding
confusion.

$ file /usr/local/bin/rvplayer 
/usr/local/bin/rvplayer: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
dynamically linked, stripped

/usr/bin/strip(used during INSTALL_PROGRAM) forces Linux binary to be
branded as FreeBSD with old method and then it will always be treated
as FreeBSD binary. The effort to brand it as Linux with new method
will be ignored.

Stripping Linux binary with Linux strip would be a workaround.

-- 
FUJISHIMA Satsuki

Index: Makefile
===
RCS file: /home/ncvs/ports/audio/linux-realplayer/Makefile,v
retrieving revision 1.12
diff -u -r1.12 Makefile
--- Makefile2000/04/08 21:23:56 1.12
+++ Makefile2000/05/14 06:37:17
@@ -20,6 +20,8 @@
 NO_BUILD=  yes
 WRKSRC=${WRKDIR}/rvplayer5.0/
 
+STRIP= # linux binary should not be stripped by INSTALL_PROGRAM
+
 LIBFILES=  libdecdnet.so libra14_4.so libra28_8.so libradnet.so \
librarv10.so librasipr.so librv10dec.so librvcore.so \
librvplayer.so
@@ -58,6 +60,7 @@
 .endfor
 
${INSTALL_PROGRAM} ${WRKSRC}/rvplayer ${PREFIX}/bin/
+   /compat/linux/usr/bin/strip ${PREFIX}/bin/rvplayer
/usr/bin/brandelf -t Linux ${PREFIX}/bin/rvplayer
 
${INSTALL_DATA} ${WRKSRC}/welcome.rm ${PREFIX}/share/rvplayer5.0/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message