Hello,
On Sun, Jan 21, 2001 at 11:35:49PM -0800, John Baldwin wrote:
> I just do 'make includes' w/o the rm of /usr/include when I do this..
>
> I normally do this, FWIW:
>
> 1) make buildworld
> 2) make installworld
> 3) config FOO
> 4) compile kernel FOO
> 5) install kernel FOO
> 6) update /
Poul-Henning Kamp <[EMAIL PROTECTED]> types:
> But while you're at it, migrate to md(4) instead of vn(4), it does
> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
How close is the md rewrite to being able to replace mfs?
Thanxm
Poul-Henning
>
>
> In m
"Donald J . Maddox" wrote:
> Ok, fair enough. I have to confess that my usual procedure remains,
> as it has been for a long time, like this:
>
> 1) rm -r /usr/include; cd /usr/src; make includes
>
> This may be controversial, but it has always worked for me, and although
> it's not supposed to
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
> : 2) It hides the output from config(8). config(8) prints out all sorts of
> : useful warnings when options are deprecated, etc., but buildkernel hides th
ese
> : from the user. The problem is that config(8) is by des
In message <[EMAIL PROTECTED]>, Mike Meyer writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> types:
>> But while you're at it, migrate to md(4) instead of vn(4), it does
>> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
>
>How close is the md rewrite to being able to replace
On Sun, Jan 21, 2001 at 01:50:28PM -0600, Chris wrote:
>
> If you are currently running 4.0.1, I would seriously recommend skipping
> this
> minor revision. I have run into a multitude of problems with it, and am now
> back right where I started.
>
> One, is the lack of DRM support for the matr
On Sun, 21 Jan 2001, John Baldwin wrote:
> On 22-Jan-01 Donald J . Maddox wrote:
> > Ok, fair enough. I have to confess that my usual procedure remains,
> > as it has been for a long time, like this:
> >
> > 1) rm -r /usr/include; cd /usr/src; make includes
>
> I just do 'make includes' w/o th
Is this maybe fallout from the vm_zone changes?
===> usr.bin/vmstat
cc -O -pipe -I/usr/src/usr.bin/vmstat/../../sys -I/usr/obj/usr/src/i386/usr/include
-c /usr/src/usr.bin/vmstat/vmstat.c
gzip -cn /usr/src/usr.bin/vmstat/vmstat.8 > vmstat.8.gz
/usr/src/usr.bin/vmstat/vmstat.c:483: warning: `pg
My nfs server now always panics when it attempts to export ufs
filesystems. This is caused by my mount(8) being slightly out of
date. This shouldn't be a problem, but `struct export_args' contains
a `struct ucred' which contains a `struct mtx', so when `struct mtx'
shrunk by 1 pointer yesterday,
< said:
> If you want to or need to use network sockets,
> # syslogd -a localhost
> Should provide the behavior you want.
I.e., no security whatsoever.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
< said:
> So now, maybe someone can answer my question: why is timespec _KERNEL?
It's not. Some of the namespace pollution associated with it is.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
< said:
> work on stable, just do a #ifdef __FreeBSD_version > 4 use selinfo, else use
> select.h.
Make that:
#if __FreeBSD_version >= 500014
#include
#else
#include
#endif
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O S
< said:
> Somehow there were few problems when `struct mtx' was added to
> `struct ucred'. The critical args were probably usually 0.
It's a bug that mount(2) uses a bare `struct ucred' and not a
well-defined, user-exportable credential structure (like struct
cmsgcred used for SCM_CREDS ancilla
Hi folks,
Now I'm in process of writing a libvgl driver for SDL (almost finished - I'm
testing it right now) and found that two handy features are currently missed
from the libvgl: ability to query video modes supported by the video hardware
and ability to install custom mouse eventhandler. So I
* Garrett Wollman <[EMAIL PROTECTED]> [010122 10:27] wrote:
> < said:
>
> > Somehow there were few problems when `struct mtx' was added to
> > `struct ucred'. The critical args were probably usually 0.
>
> It's a bug that mount(2) uses a bare `struct ucred' and not a
> well-defined, user-export
I recently saw a thread regarding the Belkin KVM switches that had their
EEPROM's in the wrong sockets.
Can someone please point me to the link that was posted earlier,
could not find it in the archives.
Please CC me.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cur
In message <[EMAIL PROTECTED]> Alfred Perlstein writes:
: I looked at fixing this once, but got scared off because of binary
: compatibility issues. Would 'fixing' mount to use cmsgcred be
: acceptable?
I think so. Right now we have lots of killer, panic inducing binary
incompatibilities. One
On Sun, Jan 21, 2001 at 11:12:44PM -0800, John Baldwin wrote:
> Rarely if ever do you need the new tools. The only cases are for a
> binutils upgrade that is not backwards compatible (such as the 2.9
> -> 2.10 upgrade), or if you need a newer version of config, which
> can be handled by installi
< said:
> I looked at fixing this once, but got scared off because of binary
> compatibility issues. Would 'fixing' mount to use cmsgcred be
> acceptable?
No, it should use a structure appropriately named and designed for its
own purpose. (By preference, it should be binary-compatible with
4.x
I got quite upset about this last time, and I guess it's time to do it
again.
Folks, *please* stop exporting "pure" kernel structures to userland.
Make a sanitisied, versioned structure and just copy your damn args back
and forth. 'struct ucred' should probably never have been exported to
In message <[EMAIL PROTECTED]> Kris Kennaway writes:
: I agree that developers don't need to use buildkernel because we are
: mostly capable of doing the manual workarounds on the rare occasions
: when things need to be done differently. But if you cast your mind
: back to the many dozens of suppo
Warner Losh <[EMAIL PROTECTED]> types:
> It is in the handbook, and has been for some time. I'm reviewing the
> recent KERNEL -> KERNCONF changes to make sure that they make it into
> the handbook properly (I assume there will be a MFC in a few days,
> since putting KERNEL in /etc/make.conf is a
Robert,
You wrote:
> For the last few days (not sure when it started) I've been unable to build
> -STABLE on a -CURRENT machine. This has proven a problem for recent
> RELENG_3 MFC's of security fixes; I've tried upgrading to the most recent
> -CURRENT on the box, making sure /usr/include is u
In message <[EMAIL PROTECTED]> Mike Meyer writes:
: Warner Losh <[EMAIL PROTECTED]> types:
: > It is in the handbook, and has been for some time. I'm reviewing the
: > recent KERNEL -> KERNCONF changes to make sure that they make it into
: > the handbook properly (I assume there will be a MFC in
On 22-Jan-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mike Meyer writes:
>: Warner Losh <[EMAIL PROTECTED]> types:
>: > It is in the handbook, and has been for some time. I'm reviewing the
>: > recent KERNEL -> KERNCONF changes to make sure that they make it into
>: > the handbook pro
John Baldwin <[EMAIL PROTECTED]> types:
>
> On 22-Jan-01 Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Mike Meyer writes:
> >: Warner Losh <[EMAIL PROTECTED]> types:
> >: > It is in the handbook, and has been for some time. I'm reviewing the
> >: > recent KERNEL -> KERNCONF changes to ma
Title: untitled
Dear PC User,
Now you can make Windows 95 and 98 almost as dependable as
Windows NT/2000, Microsoft's professional version of Windows.
A new software product is available to very effectively improve the
reliability
of Windows. It lets Windows quickly repair itself when nec
In article <[EMAIL PROTECTED]>,
David Gobeille <[EMAIL PROTECTED]> wrote:
> I recently saw a thread regarding the Belkin KVM switches that had their
> EEPROM's in the wrong sockets.
>
> Can someone please point me to the link that was posted earlier,
> could not find it in the archives.
htt
On Mon, Jan 22, 2001 at 12:16:38PM -0800, Mike Smith wrote:
> In the meantime, perhaps we could
> ask that one of the SMPng rules of engagement mandate that no mutex
> structures or structure members should ever be exported as part of a
> userspace interface?
This sounds fine in principle, but
"David O'Brien" <[EMAIL PROTECTED]> writes:
>On Thu, Jan 11, 2001 at 02:38:55PM -0800, John Baldwin wrote:
>> Erm, sysinstall can be used as a replacement for fdisk and disklabel,
>> both of which are in /sbin. In fact, in 4.2 the only tool you can
>> realistically use to splat a virgin disklabel
In message <[EMAIL PROTECTED]> John Baldwin writes:
:
: On 22-Jan-01 Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Mike Meyer writes:
: >: Warner Losh <[EMAIL PROTECTED]> types:
: >: > It is in the handbook, and has been for some time. I'm reviewing the
: >: > recent KERNEL -> KERNCONF c
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebx
db> t
Debugger(c02b8303) at Debugger+0x44
panic(c02c9040,bfc0,581000,c02ea620,c030ab0c) at panic+0x70
kmem_malloc(c0312d20,bfc0,8,bfbff810,c898) at kmem_malloc+0xd7
malloc(bfbff810,c02ea620,8,c0ff1e00,c898) at malloc+0
* Matthew Jacob <[EMAIL PROTECTED]> [010122 15:32] wrote:
>
> Debugger("panic")
> Stopped at Debugger+0x44: pushl %ebx
> db> t
> Debugger(c02b8303) at Debugger+0x44
> panic(c02c9040,bfc0,581000,c02ea620,c030ab0c) at panic+0x70
> kmem_malloc(c0312d20,bfc0,8,bfbff810,c898) at km
> * Matthew Jacob <[EMAIL PROTECTED]> [010122 15:32] wrote:
> >
> > Debugger("panic")
> > Stopped at Debugger+0x44: pushl %ebx
> > db> t
> > Debugger(c02b8303) at Debugger+0x44
> > panic(c02c9040,bfc0,581000,c02ea620,c030ab0c) at panic+0x70
> > kmem_malloc(c0312d20,bfc0,8,bfbff
> > mountd exporting stuff causes a panic.
>
> This is and isn't my fault, struct ucred needs a lock for refcounts.
> Since mount uses ucreds in userspace and passes them to the kernel
> we have a issue when struct mtx changes. I'm going to take a shot
> at removing struct ucred from userland th
> On Mon, Jan 22, 2001 at 12:16:38PM -0800, Mike Smith wrote:
> > In the meantime, perhaps we could
> > ask that one of the SMPng rules of engagement mandate that no mutex
> > structures or structure members should ever be exported as part of a
> > userspace interface?
>
> This sounds fine in
In message <[EMAIL PROTECTED]> Mike Meyer writes:
: KERNEL is documented in make.conf(5), but not in
: /etc/defaults/make.conf. Since the only thing in the latter that's
: anything other than a comment is BDECFLAGS, I suggested nuking most of
: /etc/defaults/make.conf and putting in a pointer to m
In message <[EMAIL PROTECTED]> Randell Jesup
writes:
: A full set of disklabel patches to support MB, GB, KB, %, and *
: (everything not spoken for elsewhere) for sizes (and * for offsets to allow
: disklabel to calculate them for you), etc are in Warner's hands. (I got
: annoyed at it o
Hi,
attached in dbg.txt is some dbg output from a recent -current panic.
Anything else of interest to inspect?
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
...
IdlePTD 3731456
initial pcb at 2bd600
panicstr: getnewbuf: locked buf
panic messages:
---
panic: lockmgr: pid 5
On 22-Jan-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
>:
>: Erm, if it wasn't documented in the first place, making a change doesn't
>: put the burden of documenting the old behavior on the person making the
>: change.
>
> It was in the handbook, explicitly docum
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Nm. I was referring to the original request:
:
: >: >: Could you also make sure it makes it into /etc/defaults/make.conf
: >: >: (KERNEL isn't mentioned there at all) and make.conf(5)?
:
: Which basically says: "this wasn't documented before
I would, except that several attempts to get this to work have failed. It
hangs syncing disks, I couldn't get into ddbI'll keep trying as I can,
but, you know, this is really really easy to reproduce- can't you do it?
The best I can tell you at the moment is that objcopy is in sleeping on
'
:
:
:
:I would, except that several attempts to get this to work have failed. It
:hangs syncing disks, I couldn't get into ddbI'll keep trying as I can,
:but, you know, this is really really easy to reproduce- can't you do it?
:
:The best I can tell you at the moment is that objcopy is in sle
On Mon, 22 Jan 2001, Matt Dillon wrote:
>
> :
> :
> :
> :I would, except that several attempts to get this to work have failed. It
> :hangs syncing disks, I couldn't get into ddbI'll keep trying as I can,
> :but, you know, this is really really easy to reproduce- can't you do it?
> :
> :The
http://www.silby.com/patches/openssl-asm.patch
I've just thrown together a patch that enables the asm cores (where
available) in openssl. I've tested it on a p5, k6, and p6 - all show good
improvements (from 1.1x - 2.0x, depending on the core.) SHA1, blowfish,
and cast aren't running as fast a
Removing stale files from /var/preserve:
Cleaning out old system announcements:
Removing stale files from /var/rwho:
Backup passwd and group files:
kyra.unloved.org passwd diffs:
68d67
< orion:(password):2004:2004::0:0:Orion Server:/home/orion:/usr/local/bin/bash
69a69
> postfix:(password):200
Dear all...
First of all, sorry for cross-posting cause I don't know which mailing list
is the most appropriate for this kind of question and I think this affects
all mailing list I send this mail to.
Running -CURRENT with world and kernel of: Thu Jan 18 13:04:05 JAVT 2001
Blew away all /usr/X11
On Mon, Jan 22, 2001 at 12:40:00PM -0500, Garrett Wollman wrote:
> < said:
>
> > If you want to or need to use network sockets,
>
> > # syslogd -a localhost
>
> > Should provide the behavior you want.
>
> I.e., no security whatsoever.
Well, yeah, it's syslogd(8) and as the manpage says,
On Tue, Jan 23, 2001 at 10:12:00AM +0700, John Indra wrote:
> Running -CURRENT with world and kernel of: Thu Jan 18 13:04:05 JAVT 2001
> Blew away all /usr/X11R6 and /usr/local to have fresh ports on my system.
> Then, I install XFree86-4.0.2_5.
>
> Now, whenever I enter X (using startx) and try
On a current SMP box running a kernel from this morning I see messages
from the ahc driver I haven't seen before. The machine keeps on running
though. Should I worry about them or back down to kernel of yesterday?
ahc0: port 0xd000-0xd0ff mem
0xe100-0xe1000fff irq 19 at device 6.0 on pci0
a
50 matches
Mail list logo
