On Tue, Nov 16, 1999 at 03:17:43PM +1100, Bruce Evans wrote:
On Mon, 15 Nov 1999, Pierre Beyssac wrote:
- volatile u_short answer = 0;
+ union {
+ u_int16_t us;
+ u_int8_t uc[2];
+ } answer;
This has indentation bugs.
Uh, which one(s) do you mean exactly? The
On Tue, 16 Nov 1999 09:45:36 +0100, Pierre Beyssac wrote:
- volatile u_short answer = 0;
+ union {
+ u_int16_t us;
+ u_int8_t uc[2];
+ } answer;
Uh, which one(s) do you mean exactly? The 4-space indented union
(I just followed style(9))
The word ``union''
And, also, we need to get rid of the 'e' option to ps entirely. It's a
major security hole.
I agree that we need to get rid of 'e' and any other options that allow
reading another process's environment.
How about protecting the -e option by a test for setuid() == 0 instead
of
On Tue, Nov 16, 1999 at 10:58:06AM +0200, Sheldon Hearn wrote:
The word ``union'' doesn't appear in style(9) and a 1 tab indent is used
consistently in the examples of structs. Use 1 tab.
Right, I reread style(9) and I apparently misunderstood the following part
which only applies to code
On Tue, 16 Nov 1999 07:19:52 +0100, Poul-Henning Kamp wrote:
Why don't we get rid of the 'e' option to ps while we are at it
considering how much of a security hole it is.
Hmm, well, I like to have it around for root at least...
Exactly.
In a perfect world, the -e option will
On Mon, 15 Nov 1999 16:27:12 PST, Matthew Dillon wrote:
I shudder to think that people might actually start depending on this
non-feature.
Your shuddering comes too late. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
In message [EMAIL PROTECTED], Sheldon Hearn writes:
On Tue, 16 Nov 1999 07:19:52 +0100, Poul-Henning Kamp wrote:
Why don't we get rid of the 'e' option to ps while we are at it
considering how much of a security hole it is.
Hmm, well, I like to have it around for root at least...
On Mon, 15 Nov 1999 13:22:23 PST, Manfred Antar wrote:
I did the same and everything works.
But XFree86 from the ports collection will not build.
That's not a very useful description of the problem. :-)
Did you answer "YES" or "NO" to the following question?
Do you want to compile
On Tue, 16 Nov 1999, Pierre Beyssac wrote:
On Tue, Nov 16, 1999 at 03:17:43PM +1100, Bruce Evans wrote:
On Mon, 15 Nov 1999, Pierre Beyssac wrote:
- volatile u_short answer = 0;
+ union {
+ u_int16_t us;
+ u_int8_t uc[2];
+ } answer;
This has indentation bugs.
On Mon, Nov 15, 1999 at 02:18:24PM -0800, Matthew Dillon wrote:
Why don't we get rid of the 'e' option to ps while we are at it
considering how much of a security hole it is. I've never liked the
'e' option.
If we get rid of the 'e' option we should also get rid of showing
the
I was running a kernel from end of august, and everything worked
fine (IBM PC 300 PL, PII-350, 128 MB RAM, built-in audio):
Oct 5 13:28:29 aylee /kernel: pcm1 (CS423x/Yamaha/AD1816 CS4235 sn 0x) at
0x530-0x537 irq 5 drq 1 flags 0x13 on isa
Since make world last
Speaking of which, is their an archive (web based?) of the FreeBSD-current
mailing list (how about others?)? I didn't see one linked in my searches
around the web pages.
I am currently working on a full-text search/archive of Open Source
mailing lists, which should be up at
On Mon, 15 Nov 1999 13:22:23 PST, Manfred Antar wrote:
I did the same and everything works.
But XFree86 from the ports collection will not build.
By the way, I just tested the build using gcc-2.95.2 both with and
without the threads support. So you really are going to need to provide
more
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Monday, 15 November 1999 at 11:01:05 -0800, Matthew Jacob wrote:
On Mon, 15 Nov 1999, Rodney W. Grimes wrote:
Reread/reresponse, sorry- ENOCOFFEE:
1 filemark can not be used for EOT, it is EOF, you can't tell if what you
read next is another file or not that may have been left by a
On Monday, 15 November 1999 at 9:36:16 -0800, Matthew Jacob wrote:
There seems to be a great amount of confusion about the 2 EOF marks on
tapes. It has nothing to do with physical EOT, even the 556BPI 1/2"
tape drives on an IBM 1401 can detect physical EOT. The problem is
with LOGICAL
Every night, I do a partial backup, one file on tape for each file
system, about 12 in all. Subsequently I read the tape and list
contents until I hit EOT. OK, the first time I use a tape, there will
be nothing behind it. But the next time, the total length of tape
written may be
Sorry, no. When you write a tape with these devices there's always a
leading erased area. That's why if you overwrite the front a tape you
can't skip past this area to recover data you really need. A misfeature of
modern technology.
Is this anchored in the standards? What about
For some reason, after recompiling the kernel over the last few days,
systat -vm no longer even shows an rtc0 device. It only shows the clk
device. I know this is not supposed to happen, so can anyone give me any
ideas on how to fix the problem???
Just looking at the results of a make world from a cvsup at about 4:40
PST.
ed
/usr/obj/usr/src/tmp/usr/include/sys/ttydev.h:60: warning: `B115200'
redefined
/usr/obj/usr/src/tmp/usr/include/termios.h:227: warning: this is the
location of the previous definition
cc -nostdinc -O -pipe -DBSD
On Tue, 16 Nov 1999, Edwin Culp wrote:
/usr/src/games/larn/monster.c: In function `hitm':
/usr/src/games/larn/monster.c:856: syntax error before `amt'
My first breakage of world, how neat.
Thanks to Marcel for fixing what was the result of me having too many
local copies of src/games on my
Too many people have objected. I didn't make my case clearly enough, but
because enough people of have raised issues, the default won't be changed.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Phil Regnauld writes:
| I was running a kernel from end of august, and everything worked
| fine (IBM PC 300 PL, PII-350, 128 MB RAM, built-in audio):
|
| Oct 5 13:28:29 aylee /kernel: pcm1 (CS423x/Yamaha/AD1816 CS4235 sn 0x) at
|0x530-0x537 irq 5 drq 1 flags 0x13 on isa
|
So wouldn't be the impact if a server was compromized in the absence
of an available fix :)
At 02:46 PM 11/16/99 +0800, Peter Wemm wrote:
Ben Rosengart wrote:
On Mon, 15 Nov 1999, Forrest Aldrich wrote:
Will we be updating 4.0-current to the latest BIND-8.22-P5?
Or -stable for that
Well, I finally decided to try to get my sound card working again.
It is not detected as a PNP device, but rather as a motherboard
resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed,
I use ESS drivers on Windows. But Compaq obviously decided to lay
it's fingerprints on the poor
On Monday, 15 November 1999 at 16:27:12 -0800, Matthew Dillon wrote:
:Matthew Why don't we get rid of the 'e' option to ps while we
:Matthew are at it considering how much of a security hole it is.
:
:I wouldn't nuke it completely. Make -e a noop unless the real uid ps
:is
On Mon, Nov 15, 1999 at 05:59:23PM -0800, Kris Kennaway wrote:
On Tue, 16 Nov 1999, Pierre Beyssac wrote:
I've checked, the answer is no: apparently, in_cksum() in routed/rdisc.c
is only called in two places, both with an even size.
Can it hurt to pre-emptively fix it anyway in case some
In message [EMAIL PROTECTED], Pierre Beyssac writes:
Since in_cksum is used in several places (there's another optimized
copy in libstand), a cleaner solution would be to put it in some
library.
Isn't there one in libalias already ?
--
Poul-Henning Kamp FreeBSD coreteam member
On Tue, Nov 16, 1999 at 07:29:35PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Pierre Beyssac writes:
Since in_cksum is used in several places (there's another optimized
Isn't there one in libalias already ?
Right. I missed it because it's called
On Wed, 17 Nov 1999, Daniel C. Sobral wrote:
Well, I finally decided to try to get my sound card working again.
It is not detected as a PNP device, but rather as a motherboard
resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed,
I use ESS drivers on Windows. But Compaq
On Tuesday, 16 November 1999 at 8:04:05 -0800, Matthew Jacob wrote:
Too many people have objected. I didn't make my case clearly enough,
but because enough people of have raised issues, the default won't
be changed.
I think this is the correct decision in the short term. In the longer
On Tue, 16 Nov 1999, Greg Lehey wrote:
On Tuesday, 16 November 1999 at 8:04:05 -0800, Matthew Jacob wrote:
Too many people have objected. I didn't make my case clearly enough,
but because enough people of have raised issues, the default won't
be changed.
I think this is the correct
In message [EMAIL PROTECTED], "Justin T. Gibbs" wri
tes:
I must have missed a thread somewhere. Can I get a reference to what
this problem is?
Run this on a SMP box and it will die in seconds:
i=0
while [ $i -lt 200 ]
do
i=`expr $i + 1`
(
Make release was working fine a week ago. The past four days I get the
following error every time I try:
(cd /usr/src/etc/..; install -c -o root -g wheel -m 444 COPYRIGHT
/reserve/)
(cd /usr/src/etc/../share/man; make makedb; )
makewhatis /reserve/usr/share/man
makewhatis
At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote:
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
Ok Sheldon here are some of the Errors I get when building XFee86 with the
new compiler
A few of these :
cc -c -O -I../..
At 05:14 PM 11/16/99 -0800, Manfred Antar wrote:
At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote:
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
Ok Sheldon here are some of the Errors I get when building XFee86 with the
new compiler
A
On Tue, 16 Nov 1999, Manfred Antar wrote:
-DDEFAULT_CONFIG=\"/usr/
X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c
server.c: In function `putenv':
server.c:790: argument `s' doesn't match prototype
/usr/include/stdlib.h:117: prototype declaration
*** Error code 1 (continuing)
There are
On Tuesday, 16 November 1999 at 8:04:05 -0800, Matthew Jacob wrote:
Too many people have objected. I didn't make my case clearly enough,
but because enough people of have raised issues, the default won't
be changed.
I think this is the correct decision in the short term. In the
At 09:35 PM 11/16/99 -0500, Bill Fumerola wrote:
On Tue, 16 Nov 1999, Manfred Antar wrote:
-DDEFAULT_CONFIG=\"/usr/
X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c
server.c: In function `putenv':
server.c:790: argument `s' doesn't match prototype
/usr/include/stdlib.h:117: prototype
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800)
At 09:50 PM 11/16/99 -0500, Bill Fumerola wrote:
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
Maybe it's something else, there might
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
Something weird is going on... I can confirm Manfred's claim, I also just
build
On Tue, 16 Nov 1999 20:15:17 PST, "Rodney W. Grimes" wrote:
Something weird is going on... I can confirm Manfred's claim, I also
just build XFree86 just before the compiler change. I'm certainly not
going to cvs update right now... :-)
Gentlemen, would you please use the right terminology
43 matches
Mail list logo
