Is this SMP ?
In message <[EMAIL PROTECTED]>, N writes:
>Poul-Henning Kamp wrote:
>
>> I still hear reports of sporadic calcru() warnings.
>>
>> If any of you see these, could you try to see if they correlate
>> to the uptime of the machine in question ?
>
>Should they start or stop when a mach
On Thu, Nov 25, 1999 at 10:38:56AM +1030, Daniel O'Connor <[EMAIL PROTECTED]>
wrote:
>
> On 24-Nov-99 Poul-Henning Kamp wrote:
> > I still hear reports of sporadic calcru() warnings.
> >
> > If any of you see these, could you try to see if they correlate
> > to the uptime of the machine in
[EMAIL PROTECTED] wrote:
>> *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in
>>PR bin/7587) need to be implemented.
It's good news for me.
I hope to port xmovie -- QuickTime movie Player for Linux to FreeBSD.
But I can not compile it under FreeBSD, because it
At 8:03 AM + 11/24/99, Brian Somers wrote:
> > This was discussed close to death before the changes were committed,
> > and the current behaviour (restricted access) has been agreed by
> > general consensus to be the most appropriate.
>
>My reading of the thread was ``I'm going to cache ps arg
On 24-Nov-99 Poul-Henning Kamp wrote:
> I still hear reports of sporadic calcru() warnings.
>
> If any of you see these, could you try to see if they correlate
> to the uptime of the machine in question ?
I have had them for Seti@Home occasionally. The system hadn't been up for more
than 24
Jason,
On Mon, Nov 22, 1999 at 06:52:20PM -0800, Jason Evans wrote:
> Walnut Creek has hired me as a full time employee to work primarily on
> improving and expanding FreeBSD's threads support. This is very exciting
> to me, and I hope my work will be of benefit the FreeBSD community.
That's
Poul-Henning Kamp wrote:
> I still hear reports of sporadic calcru() warnings.
>
> If any of you see these, could you try to see if they correlate
> to the uptime of the machine in question ?
Should they start or stop when a machine has been running a while? I see
neither (negative calcru noti
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Peter Wemm writes:
> :
> : In a dedicated server role, again it might be appropriate to default
> : it to "open" (dedicated server being something like a squid box),
> : again there will be a couple of sysadmin type users or people who
> : ha
> > In the last episode (Nov 23), Lyndon Nerenberg said:
> > > After you verify that this change isn't going to break things that
> > > assume they can see the *argv list via ps(1). I.e. lightning bolts
> > > that do 'kill -MUMBLE `ps -ax|grep foo`'. Which may not be elegant
> > > style, but somet
I've been working on the cvsup-master route table leaks. I haven't
found the bug yet, but I've got some clues now. If this info inspires
a Eureka! from any of you, please let me know.
I started by running this script to print out key information every
2 seconds while I ran a test:
#! /bin/
I got a few calcru() warnings on a dual Pentium-III Xeon system. It had been
up for around 9 or 10 days or so; I've since rebooted it. Specific
configuration
available if you need it.
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Holm Tiffe writes:
| Is an NFS root supported in -current ?
| How is the syntax to set the rootdevice ?
| How about /boot/loader and friends <-> and etherboot ?
| (the port is outdated, it references etherboot-2.4.5.tar.gz
| and no one has this old file anymore, current is 2.4.10)
Yes it is possi
Hi,
At 8:00 pm +0100 24/11/99, Poul-Henning Kamp wrote:
>I still hear reports of sporadic calcru() warnings.
>
>If any of you see these, could you try to see if they correlate
>to the uptime of the machine in question ?
Nov 23 00:03:35 bludnok /kernel: [boot]
Nov 24 09:02:06 bludnok /kernel
Hi,
I have an unconventional setup at home, my PC and an little 386/40 w/o
NPU and disk that is routing my net over an ISDN line with i4b
to the world.
(the router is because there are no free slots anymore in the PC to put
the ISDN card in, it is an oldish dual P100 EISA/PCI machine running -cur
I still hear reports of sporadic calcru() warnings.
If any of you see these, could you try to see if they correlate
to the uptime of the machine in question ?
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
Fr
I belive I have now fully assimilated the bdevs into the cdevs in
the kernel. This means that we have reached the day where it should
be of no consequence if you mount /dev/wd0a or /dev/rwd0a.
Vinum users: Don't do anything to your vinum configuration until
grog tells you it is OK!
To test thi
On Wed, Nov 24, 1999 at 01:31:44PM +, Nick Hilliard wrote:
> > Why do we need to smite the Linux database servers? With threads in their
> > current state they already outperform Linux's native threads by ~50x for
> > things like sending mail. I would assume that the differences in database
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: So please explain the logic you want implemented once people have
: stopped haggeling about it, it is rather trivial.
OK. I'll likely state what I'd like to see as a patch.
: I pressume we want the same policy for /proc/*/cmdline as for
On Tue, 23 Nov 1999, David O'Brien wrote:
> > Anyone have any ideas whats going on here?
>
> Yep. ;-)
>
> > yacc: e - line 30 of "c-parse.y", syntax error
> > %expect 51
> > ^
> > *** Error code 1
>
> The problem is rev 1.92 of src/Makefile.inc1. With that change, the
> tools needed to buil
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Warner Losh writes:
>: sef has sent me patches that I've not had a chance to review that
>: appear to implement this.
>
>Actually, these patches do something else. My mistake for reading
>them before caffeine.
So
| sizeof() is an operator whose value is determined at compile time.
| sizeof(*buf) gives the size of what buf points to. This would be `1' if
| buf were a char*, or `4' if buf were an int* [on the i386].
Ahh, so I've probably seen this concept used only on structures then.
--
Dan Moschuk ([E
> I've never done this myself, but I've always been under the impression that
> sizeof(*buf) would work for dynamically allocated buffers.
sizeof() is an operator whose value is determined at compile time.
sizeof(*buf) gives the size of what buf points to. This would be `1' if
buf were a char*,
I will admit that I have had odd behaviours with threads in developing
Lyris on FreeBSD that I have not seen on Solaris, NT, or Linux. I will
see things like what appears to be the thread scheduler stop scheduling
threads and just do a busy wait. I have not tracked it down any further
for lack
| Now rather than try to call us stupid, Kris (and only Kris) could say,
| "well, I've decided to go with a dynamically allocated buffer, so of
| course I can't use sizeof() any more".
I've never done this myself, but I've always been under the impression that
sizeof(*buf) would work for dynamic
In message <[EMAIL PROTECTED]> Dan Moschuk writes:
: I have a set up diff's that introduce OpenBSDs concept of random pids and
: source port (with a sysctl knob for you sequential weenies) that will have
: to be updated again before I commit them.
I'd like to review this before it goes in, but if
Garrett Wollman wrote:
>
> Perhaps if name[] had been declared thus:
>
> #define INTTYPE_NCHARS(t) ((sizeof(t) * 3 * CHAR_BIT + 7) / 8)
>
> char name[(sizeof "ipfw: ") + INTTYPE_NCHARS(int)];
Or alternatively (removing a bit more magic):
#include
#define INTTYPE_NCHARS(t) (how
In message <[EMAIL PROTECTED]> Warner Losh writes:
: sef has sent me patches that I've not had a chance to review that
: appear to implement this.
Actually, these patches do something else. My mistake for reading
them before caffeine.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
In message <[EMAIL PROTECTED]> Alexey Zelkin writes:
: What's going on with FreeBSD Auditing Project
: (http://www.FreeBSD.org/auditors.html) ? Is it still alive ?
: I think this task is task of this project members. Or will be ;-)
Went gangbusters for a short while. Everybody was jazzed. Part
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: For example, in "workstation" mode, the reasonable default is "open",
: because typically there is one user on the box (other than root) and that
: person has root access. Excessive hiding info from that user just means
: that they'll have to us
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Warner Losh writes:
:
: >Not all will agree with this, and it is a change from the past so
: >there needs to be a sysctl to control this. And given that it is a
: >radical change from the past, it needs to
| Hello FreebSD'ers!
|
| [ Apologies to committers, I have Bcc'ed you to ensure you got
| this; you may get two copies. ]
|
| I have been charged with the duty of ensuring that FreeBSD gets a
| security audit that has the credibility of OpenBSD's.
|
| Consider this to be a request-for-discus
< said:
> This was discussed close to death before the changes were committed,
Where, and by whom? I don't recall seeing any such discussion on
-security.
> and the current behaviour (restricted access) has been agreed by
> general consensus to be the most appropriate.
Agreed by whom? Remem
< said:
> #define SNPARGS(buf, len) buf + len, sizeof(buf) > len ? sizeof(buf) - len : 0
> char action2[32], proto[47], name[18], fragment[17];
> /* Print command name */
> snprintf(SNPARGS(name, 0), "ipfw: %d", f ? f->fw_number : -1);
> Despite the fact that the buffer n
On Wed, Nov 24, 1999 at 09:58:51AM +0200, John Hay wrote:
> Well the original line is plain wrong if Brian's patch is being used,
> because there message is a pointer and the size of a pointer is 4.
Yes, yes, yes. Warner and I are *not* that stupid WRT C. We were both
commenting on the *origina
On Tue, 23 Nov 1999, Brian Fundakowski Feldman wrote:
> On Wed, 24 Nov 1999, Bruce Evans wrote:
>
> > Hmm. My netscape works, but I didn't use merge that commit. I had already
> > inadvertly fixed the bug in another way while cleaning up.
> > ...
> > #if defined(COMPAT_43) || defined(COMPAT_SU
> Why do we need to smite the Linux database servers? With threads in their
> current state they already outperform Linux's native threads by ~50x for
> things like sending mail. I would assume that the differences in database
> performance is similar.
The threads (& the old nfs issues which h
Buildworld of today current is broken due to
importing of ip_filter's header files with ioctls which
in turn broke building 'usr.bin/kdump'.
It seems to me that 'mkioctls' script in
'kdump' is "over-automated" - it build the list of the
'ioctl_includes' 'grepping' through the 'inc
Here is how i compiled XFree86 today (an additonal file for
/usr/ports/x11/XFree86/patches):
http://es-i2.fernuni-hagen.de/~jfh/FreeBSD_Documentation/node7.html
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-35
>
> "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
>
> > It's not so much that they where ``allowed'' to do it, it is more the
> > matter that they where never directly served with legal papers from USL/Novell
> > to cease all use of Net/2. Nor did they ever enter into any agreement,
> > that I
Firstly there is some threads discussion going on in -arch so
I'm going to really reply to this over there..
This is just redirector mail
julian
On Mon, 22 Nov 1999, Jason Evans wrote:
> Walnut Creek has hired me as a full time employee to work primarily on
> improving and expanding FreeBSD'
David Scheidt wrote:
>
> On Tue, 23 Nov 1999, David O'Brien wrote:
>
> > > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current
> > > buildworld running on an older -current system now progresses much
> > > further - in fact it now completes :-).
> >
> > Actually, I've been seeing
Mark Murray wrote:
>
> > I'm not sure how to fix this problem. Unlike our other build tools,
> > perl is not designed to be able to be cross-built: It builds bits
> > of itself and assumes they can be safely executed to build other bits.
>
> Perl is hugely fragile; cross-building it is a big P
Sørens new ATA driver can handle all IDE disks as far as has been
tested now, but it doesn't provide bad sector remapping which is
needed for ESDI and ST-506 disks.
Having two drivers fight for the same class of drivers is a rather
messy process, and it complicates the code a fair bit, not to
me
At 1:41 AM -0500 1999/11/24, Brian Fundakowski Feldman wrote:
> Our code doesn't run an a system _anything_ like that.
That may well be true today, however as FreeBSD gets more widely
ported to other platforms, and as the "native" platforms it runs on
progress, this might change in the
hi,
MM> I have been charged with the duty of ensuring that FreeBSD gets a
MM> security audit that has the credibility of OpenBSD's.
What's going on with FreeBSD Auditing Project
(http://www.FreeBSD.org/auditors.html) ? Is it still alive ?
I think this task is task of this project members. Or
On Wed, 24 Nov 1999, Doug Rabson wrote:
> We need to put audit tags into the source tree when a file is audited.
> That allows the diffs to be audited later which should be a smaller job
> and then the audit tag slides forward.
Not to interrupt in the middle of this discussion but you mi
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> : Warner ?
[.. reasons for and against ..]
> Not all will agree with this, and it is a change from the past so
> there needs to be a sysctl to control this. And given that it is a
> radical change from the past, it
On Tue, 23 Nov 1999, David O'Brien wrote:
> > So when Joe Blow clicks on (say) src->bin->cat he'll find that
> > (say) markm eyballed the code and kris diffed it with OpenBSD
> > and merged in fixes - "cat now considered safe".
>
> Until the next commit to cat.
>
> A security review is never d
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>I'm trying to figure out how what started as a fix to a panic turned into
>such a big mess. And I don't even think the panic has even been fixed ---
>it's just been made more obscure.
The panic hasn't been fixed, as has been re
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>Not all will agree with this, and it is a change from the past so
>there needs to be a sysctl to control this. And given that it is a
>radical change from the past, it needs to default to open.
Now, I can't tell if you wore the security-maste
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: Warner ?
Like I've said in private mail to many different people on this issue,
there needs to be a sysctl which controls this, and it needs to be
open by default.
There are many cases where unwanted information is disclosed
inadvertantl
51 matches
Mail list logo
