In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Wed, 2 Oct 2002, Sheldon Hearn wrote:
>
>> On (2002/10/02 16:27), Bruce Evans wrote:
>>
>> > It is a devfs issue that devfs moves things into the kernel where they
>> > harder to control and more fatal if they are got wrong.
>>
>> If it's jus
On Wed, 2 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
> >...
> >In fact, as the loudest supporter of MAKEDEV, you might be the best
> >person to drive its transcription into /etc/defaults/devfs.conf. :-)
>
> And with devfs(8), you can enact your pers
On Wed, 2 Oct 2002, Sheldon Hearn wrote:
> On (2002/10/02 16:27), Bruce Evans wrote:
>
> > It is a devfs issue that devfs moves things into the kernel where they
> > harder to control and more fatal if they are got wrong.
>
> If it's just ownerships and permissions you're worried about, I think
>
Hello,
On 07:43+0400, Oct 2, 2002, Robert Watson wrote:
>
> It looks like someone has broken support for NIS in /etc/master.passwd by
> tightening the formatting rules for the file incorrectly. Whereas a
> perfectly valid NIS password file used to work a month or so ago, it now
> generates a s
On Tue, 1 Oct 2002, Pete Carah wrote:
> There is a 't' modifier to a format in bin/sh that just crept in;
> it prevents a cross buildworld under stable without NO_WERROR.
>
> Perhaps the compiler+libc needs to be built first? (and does sh
> need to be a build tool; I'd hope the make scripts stuc
On Tue, Oct 01, 2002 at 10:37:26PM -0700, Pete Carah wrote:
> There is a 't' modifier to a format in bin/sh that just crept in;
> it prevents a cross buildworld under stable without NO_WERROR.
>
> Perhaps the compiler+libc needs to be built first? (and does sh
> need to be a build tool; I'd hop
In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
>On (2002/10/02 16:27), Bruce Evans wrote:
>
>> It is a devfs issue that devfs moves things into the kernel where they
>> harder to control and more fatal if they are got wrong.
>
>If it's just ownerships and permissions you're worried about, I
Robert Watson wrote:
> It looks like someone has broken support for NIS in /etc/master.passwd by
> tightening the formatting rules for the file incorrectly. Whereas a
> perfectly valid NIS password file used to work a month or so ago, it now
> generates a syntax error:
Ran into the same thing l
On (2002/10/02 16:27), Bruce Evans wrote:
> It is a devfs issue that devfs moves things into the kernel where they
> harder to control and more fatal if they are got wrong.
If it's just ownerships and permissions you're worried about, I think
the issue could be made moot by some /etc support for
On Wed, 2 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >One reason I have no confidence in devfs is that its quality is such as
> >to get things like this wrong. There are magic ownerships and permissions
> >in the source code for N drivers where the
Voici le résultat du formulaire envoyé par
[EMAIL PROTECTED] ([EMAIL PROTECTED]) le Mercredi, Octobre 2, 2002 at 07:52:52
---
wom:
TODAY MORTGAGE RATES HIT THE LOWEST EVER. WE CAN GIVE YOU A 3% RATE FOR 30 YEARS WITH
NO C
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Tue, 1 Oct 2002, Brooks Davis wrote:
>
>> I just added options GEOM on a kernel from yesterday and noticed today
>> that Amanda failed to dump my disks overnight. The problem is that the
>> entries in /dev have the wrong permissions. They s
There is a 't' modifier to a format in bin/sh that just crept in;
it prevents a cross buildworld under stable without NO_WERROR.
Perhaps the compiler+libc needs to be built first? (and does sh
need to be a build tool; I'd hope the make scripts stuck to a
fairly least-common-denominator shell syn
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
:
:Hmm, no. Backing out tcp_input.c change not fix this bug... I'll try to
:rollback on per-day basis...
:
:On Wed, Oct 02, 2002 at 05:06:51 +0400, Andrey A. Chernov wrote:
:> The death remains after ksiginfo backing out, so I start to suspect recent
:> TCPIP changes (tcp_input.c).
:
:--
:Andr
Hmm, no. Backing out tcp_input.c change not fix this bug... I'll try to
rollback on per-day basis...
On Wed, Oct 02, 2002 at 05:06:51 +0400, Andrey A. Chernov wrote:
> The death remains after ksiginfo backing out, so I start to suspect recent
> TCPIP changes (tcp_input.c).
--
Andrey A. Cherno
On Tue, 1 Oct 2002, Brooks Davis wrote:
> I just added options GEOM on a kernel from yesterday and noticed today
> that Amanda failed to dump my disks overnight. The problem is that the
> entries in /dev have the wrong permissions. They should be readable by
> group operator, but here's what I
On Wed, Oct 02, 2002 at 08:41:10AM +0900, Mitsuru IWASAKI wrote:
> Hi,
>
[...]
> > Can you try with the stuff I committed yesterday? It fixed the case (for
> > my tests at least) of legacy0 failing to attach or probe when acpi failed
> > to attach.
>
> If still failed, please try this.
> I've
On Tuesday, 1 October 2002 at 9:48:59 +0200, Sheldon Hearn wrote:
> On (2002/09/30 21:09), Poul-Henning Kamp wrote:
>
>> Provided nothing terminal pops up in the next 5 days, GEOM will
>> become default in -current on Saturday 5th of october.
>>
>> Please test it now on _your_ configuration and
On 02-Oct-2002 Alexander Langer wrote:
> Hi!
>
> Can anyone explain me why with a recent kernel (last kernel was from
> 1 year ago) the kernel boot messages disappear from the monitor
> once the "propellor" of the kernel boot has done like 5 rounds
> (last message is the last line of the
> "Boo
On 01-Oct-2002 Mitsuru IWASAKI wrote:
> Hi,
>
>> On 01-Oct-2002 Michael McGoldrick wrote:
>> > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote:
>> >>
>> >> On 01-Oct-2002 Michael McGoldrick wrote:
>> >> > 'Me too'
>> >> > Dmesg from working kernel attached, not sure how to get a dm
On 1 Oct, Sam Leffler wrote:
> I have repeated problems where a machine running -current locks up while
> running make over an NFS mounted filesystem. The NFS server is an up to
> date -stable machine. When the lockup occurs I get a message:
>
> nfs server : not responding 10 > 9
>
> The file
I have repeated problems where a machine running -current locks up while
running make over an NFS mounted filesystem. The NFS server is an up to
date -stable machine. When the lockup occurs I get a message:
nfs server : not responding 10 > 9
The filesystem is mounted r/w with no options. nfsio
The death remains after ksiginfo backing out, so I start to suspect recent
TCPIP changes (tcp_input.c).
On Tue, Oct 01, 2002 at 19:25:43 +0400, Andrey A. Chernov wrote:
> Now I constantly got cvsupd death on very recent -current. Either TCPIP or
> thread changes involved, all works two days ago.
Hi!
Can anyone explain me why with a recent kernel (last kernel was from
1 year ago) the kernel boot messages disappear from the monitor
once the "propellor" of the kernel boot has done like 5 rounds
(last message is the last line of the
"Booting kernel in X seconds" line, followed by a single "
On 01-Oct-2002 Lars Eggert wrote:
> Hi,
>
> I've been running the guidescope web ad blocker
> (http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a
> long time. The thing seems to fork a child for each web request it proxies.
>
> Under -current, it seems that the child proce
Duncan Barclay wrote:
> On 01-Oct-2002 Lars Eggert wrote:
>>
>>I've been running the guidescope web ad blocker
>>(http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a
>>long time. The thing seems to fork a child for each web request it proxies.
>>
>>Under -current, it seems tha
Hi,
> On 01-Oct-2002 Michael McGoldrick wrote:
> > On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote:
> >>
> >> On 01-Oct-2002 Michael McGoldrick wrote:
> >> > 'Me too'
> >> > Dmesg from working kernel attached, not sure how to get a dmesg from the
> >> > broken one. :(
> >> > Send me
OK; after building today's -CURRENt on my build machine, I had time to
try building the kernel again, but with GEOM.
3 observations so far:
* Nearly everything still works. :-)
* A verbose boot (my default on the machine in question, since I
often need to check things or quote boot messages)
* Andy Farkas <[EMAIL PROTECTED]> [021001 15:20] wrote:
> On Tue, 1 Oct 2002, Alfred Perlstein wrote:
>
> > Whoa :)
> >
> > I'm the RPC maintainer?
> >
> > Well ok, I've just checked in a fix for the prototypes being declared
> > into -current, I'll take a shot at -stable RSN (most likely tom
On Tue, 1 Oct 2002, Alfred Perlstein wrote:
> Whoa :)
>
> I'm the RPC maintainer?
>
> Well ok, I've just checked in a fix for the prototypes being declared
> into -current, I'll take a shot at -stable RSN (most likely tomorrow).
> As far as a manpage I don't know when I'll have time for that.
ProgressIT I/S
Nikolaj Hansen
Algade 15 - 2tv
9000 Ålborg
Denmark
Windows XP: A 32-bit graphical shell for a 16-bit patch to an 8-bit
operating system originally encoded for a 4 bit microprocessor by a 2-bit
company who can't stand 1 bit of competition.
To Unsubscribe: send mail to [EMAIL P
On 01-Oct-2002 Michael McGoldrick wrote:
> On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote:
>>
>> On 01-Oct-2002 Michael McGoldrick wrote:
>> > 'Me too'
>> > Dmesg from working kernel attached, not sure how to get a dmesg from the
>> > broken one. :(
>> > Send me a mail if any furth
Trying to buildworld on a -stable box does this:
--
>>> stage 2: build tools
--
cd /heffer/src; MAKEOBJDIRPREFIX=/usr/obj DESTDIR= INSTALL="sh
/heffer/src/tools/install.sh"
On Tue, Oct 01, 2002 at 12:48:47PM -0400, John Baldwin wrote:
>
> On 01-Oct-2002 Michael McGoldrick wrote:
> > 'Me too'
> > Dmesg from working kernel attached, not sure how to get a dmesg from the
> > broken one. :(
> > Send me a mail if any further info would help.
> > (I have built two kernels
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
I'm using the patch at
http://www.FreeBSD.org/~jhb/patches/firewire.patch
to compile firewire(4) support into kernels statically. It also
cleans up the modules a bit by removing unused header files. Any
objections to this being committed? (Note, I won't commit the
fwmem device line to NOTES sin
There has been some confusion regarding how to add new quirks to the SCSI
layer, when quirks are needed, and who is responsible. I will be taking
ownership of quirk maintenance to help clarify and expedite things. The
goal is to interoperate with as much hardware as possible while keeping
the ta
Hi,
I've been running the guidescope web ad blocker
(http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a
long time. The thing seems to fork a child for each web request it proxies.
Under -current, it seems that the child processes become zombies, and
the proxy stops working
Check out these natural health and beauty offers:
1) Go for Weeks Without Shaving!
Kalo Inhibits Unwanted Hair Growth Permanently.
http://www.freeyankee.com/cgi/fy2/to.cgi?l=em5000herb1
2) Slim Down - Guaranteed to lose 10-12 lbs in 30 days.
http://www.bluefoxmedia.com/cgi-bin/slimlead.cgi?id=32
In message <[EMAIL PROTECTED]>, Brooks Davis writes:
>I just added options GEOM on a kernel from yesterday and noticed today
>that Amanda failed to dump my disks overnight. The problem is that the
>entries in /dev have the wrong permissions. They should be readable by
>group operator, but here'
In message <[EMAIL PROTECTED]>, Takahashi Yoshihiro
writes:
>In article <[EMAIL PROTECTED]>
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>
>> Provided nothing terminal pops up in the next 5 days, GEOM will
>> become default in -current on Saturday 5th of october.
>>
>> Please test it now on _y
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
>
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
I just added options
Lars Eggert wrote:
>
> I'm slowly porting some local rc scripts we've been using for a few
> years on -STABLE to rc_ng and -CURRENT. Some of them may be useful to
> others, and I'd appreciate any comments.
I've put the latest revisions of our scripts up at
http://www.isi.edu/larse/etc.html.
L
On Tue, 1 Oct 2002, Jake Burkholder wrote:
> Apparently, On Tue, Oct 01, 2002 at 11:12:02AM -0400,
> Daniel Eischen said words to the effect of;
>
> > On Mon, 30 Sep 2002, Peter Wemm wrote:
> > > Longer term, I was thining that we could/should do what sparc64 does, ie:
> > > libc provides t
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Tue, 1 Oct 2002, Mark Murray wrote:
> I'm running a kernel with your very latest nexus.c 1.49.
>
> The problem of the disappearing HD has not been fixed by this.
>
> Enclosed are verbose mesg's, one from a three-hour-ago
> (1st Oct 2002, 11:00 am, BST) kernel (broken), and another
> from a wo
On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
I am unable to boot a GEO
On 01-Oct-2002 Michael McGoldrick wrote:
> 'Me too'
> Dmesg from working kernel attached, not sure how to get a dmesg from the
> broken one. :(
> Send me a mail if any further info would help.
> (I have built two kernels recently, both have had this problem)
What exact problem do you have. No P
[forgot to announce]
Please try the latest version acpica-unix-20020829, patches for
FreeBSD at:
http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020918-test20020920.diff
CHANGES.txt can be fould as always at:
http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt
I'll i
Now I constantly got cvsupd death on very recent -current. Either TCPIP or
thread changes involved, all works two days ago. Does anybody else saw
this too?
cvsup & cvsupd on the same machine talking to each other:
messages says:
kernel: pid 15533 (cvsupd), uid 2068: exited on signal 6 (core dump
Apparently, On Tue, Oct 01, 2002 at 11:12:02AM -0400,
Daniel Eischen said words to the effect of;
> On Mon, 30 Sep 2002, Peter Wemm wrote:
>
> > Daniel Eischen wrote:
> > > At the end is a potentially longer term fix for the ABI
> > > breakage that was introduced when the i386 mcontext_t
On Mon, 30 Sep 2002, Peter Wemm wrote:
> Daniel Eischen wrote:
> > At the end is a potentially longer term fix for the ABI
> > breakage that was introduced when the i386 mcontext_t
> > was changed/enlarged.
>
> > - ret = set_fpcontext(td, &ucp->uc_mcontext);
> > - if (ret !=
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Tue, 1 Oct 2002, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>> >On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
>> >
>> >> Provided nothing terminal pops up in the next 5 days, GEOM will
>> >> become defau
'Me too'
Dmesg from working kernel attached, not sure how to get a dmesg from the
broken one. :(
Send me a mail if any further info would help.
(I have built two kernels recently, both have had this problem)
On Tue, Oct 01, 2002 at 01:06:59PM +0100, Mark Murray wrote:
> Hi
>
> I'm running a kern
On Tue, 01 Oct 2002 23:29:34 +0900 (JST)
Yamada Ken Takeshi <[EMAIL PROTECTED]> wrote:
>
>3) HelloWorld.cc can't be compiled while 4.6R can do it,
> and it disables to compile kdebase3.
>
> #include int main(){ cout<<"Hello World\n";}
>
> c++ HelloWorld.cc -o HelloWo
On 01-Oct-2002 Mark Murray wrote:
> Hi
>
> I'm running a kernel with your very latest nexus.c 1.49.
>
> The problem of the disappearing HD has not been fixed by this.
>
> Enclosed are verbose mesg's, one from a three-hour-ago
> (1st Oct 2002, 11:00 am, BST) kernel (broken), and another
> from
Just FYI.
I'm running -current (9/30) on PIII x 2(smp) and notice
the followings;
1) buildworld on XFree86-4 panics silently to reboot.
2) fsck -b after above reason reboot core dumps like;
ffs_snapgone: lost snapshot vnode 3
fatal trap 12: page fault while in kernel mo
Sheldon Hearn wrote:
> There are problems in -CURRENT that have held me back from upgrading for
> two weeks. These include X crashes and kernel panics.
FWIW, I haven't seen an X crash since removing the TypeI directory
from my fontpath.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
> While local package initilization I get a panic. World and kernel from today.
> This I found in messages:
> Sep 30 15:49:55 leeloo kernel: panic: lockmgr: locking against myself
This problem is gone with today's kernel.
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe free
Hi
I'm running a kernel with your very latest nexus.c 1.49.
The problem of the disappearing HD has not been fixed by this.
Enclosed are verbose mesg's, one from a three-hour-ago
(1st Oct 2002, 11:00 am, BST) kernel (broken), and another
from a working Sept 22nd kernel.
M
--
o Mark Murra
On Tue, 1 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
> >
> >> In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
> >> >What are the exact steps you will take to make it the default; that we
> >> >s
On Tue, 1 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
> >
> >> Provided nothing terminal pops up in the next 5 days, GEOM will
> >> become default in -current on Saturday 5th of october.
> >>
> >> Please
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
>> >On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
>> >> Provided nothing terminal pops up in the next 5 days, GEOM wi
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
> >On Mon, Sep 30, 2002 at 09:09:46PM +0200, Poul-Henning Kamp wrote:
> >> Provided nothing terminal pops up in the next 5 days, GEOM will
> >> become default in -current on Saturday 5th of oct
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
>
>> Provided nothing terminal pops up in the next 5 days, GEOM will
>> become default in -current on Saturday 5th of october.
>>
>> Please test it now on _your_ configuration and tell me if it
>> fa
On Mon, 30 Sep 2002, Poul-Henning Kamp wrote:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
It failed to understandard the partitions on
On Tue, Oct 01, 2002 at 10:47:45AM +0200, Michael Hostbaek
<[EMAIL PROTECTED]> wrote:
> It it a style problem, and Will and Alan should be aware of it - and
> when code freeze is over they should commit a patch.
>
> A temp solution is to edit 'kdebase-3.0.3/ksysguard/FreeBSD/netdev.c'
> and movi
In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
>On (2002/09/30 21:09), Poul-Henning Kamp wrote:
>Maybe you'd get more testers if you wait until the latest serious
>problems are resolved before going ahead.
>
>Maybe you wouldn't, though. So I wouldn't be annoyed if you responded
>with "Wo
On 30 Sep, Juli Mallett wrote:
> No locks except for the lock of the process being signalled should be
> held when sending signals, IMHO, though I am mostly ignorant of the SIGIO
> locking.
BTW, kill() wants to hold the allproc_lock or a process group lock
while iterating over the list of proces
Hi!
I always get a bunch of ".. could sleep with..." and "lock order reversal" messages.
There appear in various parts of the kernel.The locks: pcm, xl, drm. The reversals:
spec_vnops, vfs_subr, if_xl, sys_pipe. And this was only a quick glance through the
logs. IIRC these are considered harmf
On Tue, Oct 01, 2002 at 01:11:04AM -0700, Dag-Erling Smorgrav wrote:
> ===> bin/sh
> cc1: warnings being treated as errors
> /h/des/src/bin/sh/mksyntax.c: In function `digit_convert':
> /h/des/src/bin/sh/mksyntax.c:396: warning: int format, different type arg (arg 3)
> *** Error code 1
>
> Stop
It it a style problem, and Will and Alan should be aware of it - and
when code freeze is over they should commit a patch.
A temp solution is to edit 'kdebase-3.0.3/ksysguard/FreeBSD/netdev.c'
and moving '#include ' to just above '#include
'
Hint: You should read the kde-freebsd list - as this to
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On (2002/09/30 21:09), Poul-Henning Kamp wrote:
> Provided nothing terminal pops up in the next 5 days, GEOM will
> become default in -current on Saturday 5th of october.
>
> Please test it now on _your_ configuration and tell me if it
> fails to work.
There are problems in -CURRENT that have h
In message <[EMAIL PROTECTED]>, Takahashi Yoshihiro
writes:
>In article <[EMAIL PROTECTED]>
>Takahashi Yoshihiro <[EMAIL PROTECTED]> writes:
>
>> In article <[EMAIL PROTECTED]>
>> Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>>
>> > Provided nothing terminal pops up in the next 5 days, GEOM wil
On 30 Sep, Juli Mallett wrote:
> * De: Don Lewis <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
>> I suggest looking especially closely at the sigio stuff. Even the old
>> code has a lock order reversal problem when I/O to a pipe wants to
>> signal the process at the other end of the pipe. I thought
78 matches
Mail list logo
