Forget to note:
matusita> Warning: Object directory not changed from original /usr/src/sys/modules/3dfx
dinosaur % pwd
${CHROOT_DIRECTORY_FOR_CURRENT}/usr/src/sys/modules
dinosaur % ls */*.o
3dfx/setdef0.o 3dfx/setdef1.o 3dfx/tdfx_pci.o
Only 3dfx module uses /usr/src/sys/modules for compilat
matusita> However, this problem (use /usr/src/sys/modules for compilation) is
matusita> disappeared already according to the logfile of Nov/02/2000.
Hmm, sorry, it is not yet fixed.
cd ../../modules && env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMODIR=
make obj all
===> 3dfx
===
In article <[EMAIL PROTECTED]>,
Max Khon <[EMAIL PROTECTED]> wrote:
> do we still need uthread_autoinit.cc?
It still might be needed by old executables. Anyway I don't see a
good reason to get rid of it.
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
In article <[EMAIL PROTECTED]>, Maxim Sobolev
<[EMAIL PROTECTED]> wrote:
> John Polstra wrote:
>
> > The bug wasn't in libc_r -- it was in libgcc_r. That's a
> > static library, so it doesn't have a version number. And it is
> > statically linked into old executables. Nothing we do to libgcc_r
[ -arch and -current BCC'ed for wider coverage, please direct followups to
-net and/or me ]
I have put a new copy of the zero copy sockets and NFS patches, against
-current as of early October 30th, 2000, here:
http://people.FreeBSD.ORG/~ken/zero_copy/
Questions, comments and feedback are welco
On Tue, Oct 31, 2000 at 16:16:26 +0900, Akinori MUSHA wrote:
> At Sun, 29 Oct 2000 23:03:02 -0800 (PST),
> Kenneth Merry wrote:
> > ken 2000/10/29 23:03:02 PST
> >
> > Modified files:
> > sys/kern subr_diskslice.c
> > sys/sys diskslice.h
> > sys/ca
hosokawa> Last night, I tested "make release" on my machine, and
hosokawa> failed twice because of unloaded vn driver (this causes last
hosokawa> trouble). It successfly finished this morning. I'm Sorry.
'vn' device is a great pitfall of "make release" :-)
hosokawa> I understood the situation
At Fri, 03 Nov 2000 12:05:46 +0900,
Makoto MATSUSHITA <[EMAIL PROTECTED]> wrote:
>
> BTW, I've not received your email; are you busy working?
Last night, I tested "make release" on my machine, and failed twice
because of unloaded vn driver (this causes last trouble). It
successfly finished this
I'm not sure who all has been messing with the linuxulator in the last
couple of days but as of my last several builds (the latest of a cvsup
this afternoon) any attempt to manipulate entries in /compat/linux/dev
(even to look at them with ls) causes a kernel page fault.
--
Michael D. Harnois, R
hosokawa> Maybe it's current.jp.freebsd.org's problem
I don't think so. It's a mismatch that all object files are created
under /usr/src/modules but make install assumes that these are under
(maybe) /usr/obj. Maybe it's a fault of some Makefiles (sorry I dunno
who change the policy of module co
John Baldwin wrote:
>
> I already managed to test it locally here and commit the proper fix.
> It was an order of operations bug due to the fact that ! is
> evaluated before &.
Ok, thanks!
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe
On 02-Nov-00 Marcel Moolenaar wrote:
> John Baldwin wrote:
>>
>> Quick question: Is this a problem for people _without_ DEVFS?
>
> That's a yes for me.
>
>> non-DEVFS case. Try this hackish patch:
>>
>> Index: bpf.c
>> ===
>> R
System is : FreeBSD -current 11,2000
I compile my system and kernel with device pcm, the system say message
when I run cat /dev/sndstat:
FreeBSD Audio Driver (newpcm) Nov 2 2000 17:31:39
Installed devices:
pcm0: at io 0xdc00 irq 5 (1p/1r channels duplex)
but when i play sound, the sound is ve
>
> Quick question: Is this a problem for people _without_ DEVFS? Poul
> may have accidentally broke calling make_dev for the bpf device in the
> non-DEVFS case. Try this hackish patch:
Personally, I surely get it with DEVFS and I think I also got it when running
without it. I will try the pat
In message <[EMAIL PROTECTED]>, "Justin T. Gibbs" wri
tes:
>I beleive that I've somehow corrupted my /dev on my laptop.
>An ls -l in there causes an instant panic:
>
>Copied by hand...
>
>vfinddev(,3,c877ac84,10002,1) at vfinddev+0xc
><= NODEV
Just fixed in current (I hope
Hmm. I've seen several panics over the last day or so with -current where /
got corrupted (ino 2).
On Thu, 2 Nov 2000, Justin T. Gibbs wrote:
> I beleive that I've somehow corrupted my /dev on my laptop.
> An ls -l in there causes an instant panic:
>
> Copied by hand...
>
> vfinddev(,
On Thu, Nov 02, 2000 at 10:20:36AM +0100, Adrian Chadd wrote:
> On Mon, Oct 30, 2000, David O'Brien wrote:
> > On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
> > > cd /crash/usr/src/sys/modules && env
> > > MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
> > > KMODDIR=/c
I beleive that I've somehow corrupted my /dev on my laptop.
An ls -l in there causes an instant panic:
Copied by hand...
vfinddev(,3,c877ac84,10002,1) at vfinddev+0xc
<= NODEV
addaliasu(c7dc0a00,10002,c0b04800,c33e1180,c0b149e4) at ufs_vinit+0x44
ufs_vinit(c0b01c00,c0abe
On Wed, Nov 01, 2000 at 11:40:15PM -0800, Marcel Moolenaar wrote:
> [cc'd to [EMAIL PROTECTED]; please remove -current on future
> replies]
>
> It's quite likely we don't support less frequently used or very
> specialized ioctls. These are mostly implemented on a need-to-have basis
> triggered by
At Thu, 02 Nov 2000 22:15:45 +0100,
Poul-Henning Kamp wrote:
> >I confirmed linux ls didn't cause panic, so the culprit should belong
> >somewhere else. Hopefully phk will catch it for us. :)
>
> I hope I just did. Please report back if this has or hasn't solve
> the problem.
Just confirmed th
Sorry, this should not have sent to current. I've forwarded it to
stable, so please follow to that if you have comments on this PR,
thanks.
--
/
/__ __
/ ) ) ) ) /and.or.jp / ruby-lang.org
Akinori -Aki- MUSHA
In message <[EMAIL PROTECTED]>, "Akinori MUSHA" writes:
>At Thu, 02 Nov 2000 15:26:29 -0500,
>Marcel Moolenaar wrote:
>>
>> Akinori MUSHA wrote:
>> >
>> > At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
>> > Andrew Gallatin wrote:
>> > > To clarify -- this is the native /bin/ls and NOT /compat/linux/b
Would someone take a look at i386/20379, which adds support for Intel
450GX chipset?
The fix is simple enough to get into 4.2-RELEASE. Intel 450GX used to
be a highend chipset for servers in the PentiumPro era, and such a
chipset should be supported by 4.2-RELEASE! :)
http://www.freebsd
We have several people who report that tcp.newreno seriously hurts their
network performance and Yan doesn't seem to have time to fix it.
Unless there are compelling reasons to not do so presented in the next
72 hours I will change the kernel default from newreno enabled to
newreno disabled.
An
At Thu, 02 Nov 2000 15:26:29 -0500,
Marcel Moolenaar wrote:
>
> Akinori MUSHA wrote:
> >
> > At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
> > Andrew Gallatin wrote:
> > > To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls?
> >
> > Yes.
>
> How is linux_ustat involved if the pan
John Baldwin wrote:
>
> Quick question: Is this a problem for people _without_ DEVFS?
That's a yes for me.
> non-DEVFS case. Try this hackish patch:
>
> Index: bpf.c
> ===
> RCS file: /usr/cvs/src/sys/net/bpf.c,v
> retrieving re
On 02-Nov-00 John Baldwin wrote:
>
> On 02-Nov-00 Marcel Moolenaar wrote:
>> [EMAIL PROTECTED] wrote:
>>>
>>> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
>>> > to be updated, but is otherwise harmless. I forgot the details, but it's
>>> > all in the mailinglist ar
On 02-Nov-00 Marcel Moolenaar wrote:
> [EMAIL PROTECTED] wrote:
>>
>> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
>> > to be updated, but is otherwise harmless. I forgot the details, but it's
>> > all in the mailinglist archives. Somewhere... :-)
>>
>> Anybody han
Akinori MUSHA wrote:
>
> At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
> Andrew Gallatin wrote:
> > To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls?
>
> Yes.
How is linux_ustat involved if the panic is caused by a native binary?
--
Marcel Moolenaar
mail: [EMAIL PROTECTED]
In message <[EMAIL PROTECTED]>, "Akinori MUSHA" writes:
>At Fri, 03 Nov 2000 02:02:50 +0900,
>I wrote:
>> I'm 100% sure this change caused the panic because the stack trace
>> showed it panicked at vfinddev() called from linux_ustat().
>
>D'uh, I lied! Actually `ls /compat/linux/dev' panics at: v
At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
Andrew Gallatin wrote:
> To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls?
Yes.
> I don't suppose you could throw an older kernel on and show the output
> of /bin/ls /compat/linux/dev ?
Here is the output from the native /bin/ls on
Hi.
After recent changes in the pcm driver my SB32 refuses to play
stereo. Is anyone else seeing this ?
--gt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[EMAIL PROTECTED] wrote:
>
> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
> > to be updated, but is otherwise harmless. I forgot the details, but it's
> > all in the mailinglist archives. Somewhere... :-)
>
> Anybody handling this, or anybody can give pointers as to
Akinori MUSHA writes:
> At Fri, 03 Nov 2000 02:02:50 +0900,
> I wrote:
> > I'm 100% sure this change caused the panic because the stack trace
> > showed it panicked at vfinddev() called from linux_ustat().
>
> D'uh, I lied! Actually `ls /compat/linux/dev' panics at: vfinddev()
> <-- adda
Clive Lin writes:
> Hi,
>
> Cvsuped today from cvsup8, there might a small error in
> /usr/src/sys/compat/linux/linux_ioctl.c ...
>
> Building linux module is ok, but broken if I want a statically
> build in the kernel. (the options COMPAT_LINUX in kernel config file)
>
>
At Fri, 03 Nov 2000 02:02:50 +0900,
I wrote:
> I'm 100% sure this change caused the panic because the stack trace
> showed it panicked at vfinddev() called from linux_ustat().
D'uh, I lied! Actually `ls /compat/linux/dev' panics at: vfinddev()
<-- addaliasu() <-- ufs_vinit(). Seems I was 100% c
Akinori MUSHA writes:
> At Wed, 1 Nov 2000 22:08:26 -0800 (PST),
> Marcel Moolenaar wrote:
> > marcel 2000/11/01 22:08:26 PST
> >
> > Modified files:
> > sys/compat/linux linux_stats.c
> > Log:
> > Fix linux_ustat syscall. We only have cdevs now, so looking
> > for
That's just what I figured out. I'm compiling a kernel with XE_DEBUG and will
try increasing the if_timeout, let's see if this helps.
I should be able to do this in a rather short time.
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
> : Mmm... I don't know, the PC
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: Mmm... I don't know, the PC card gets IRQ 3, which would be used by the IR
: COM2, which is disabled in the BIOS. In fact, I only get one such message,
: after that the xe0 is working great. Maybe it just takes too long to init?
If it wor
At Wed, 1 Nov 2000 22:08:26 -0800 (PST),
Marcel Moolenaar wrote:
> marcel 2000/11/01 22:08:26 PST
>
> Modified files:
> sys/compat/linux linux_stats.c
> Log:
> Fix linux_ustat syscall. We only have cdevs now, so looking
> for a block device isn't that useful anymore.
>
>
Marcel Moolenaar wrote:
> [EMAIL PROTECTED] wrote:
> >
> > WARNING: driver bpf should register devices with make_dev() (dev_t = "#bpf/0")
> >
> > probably at first usage. Card is an xe PC Card.
> > I know I will probably get flamed for not RTF*, but I couldn't find a clue
> > anywhere...
>
> I
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
> : Probably not related at all, but on -current I am seeing:
> : xe0: watchdog timeout; resetting card
> : It happens just once, at boot time or after I insert the PC Card (Compaq
> : whatever). After that, everything w
Hi,
Cvsuped today from cvsup8, there might a small error in
/usr/src/sys/compat/linux/linux_ioctl.c ...
Building linux module is ok, but broken if I want a statically
build in the kernel. (the options COMPAT_LINUX in kernel config file)
By removing the line 60 (see the patch attache
Nice product... where can I download this?? ;)
Perhaps you should put this in the ports tree?? *chuckle*
Cheers,
Marc
On Thu, Nov 02, 2000 at 01:14:49AM -0800, Dragos Ruiu wrote:
> This mail message was not automatically generated by our Stupid2000 release
> of Dumbscan which did not fin
[EMAIL PROTECTED] wrote:
>
> WARNING!
Mail robots uproar... :-)
--
With Best Regards.
Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514
Granch Ltd. system administrator, e-mail: [EMAIL PROTECTED]
tel/fax (383-2) 24-2363
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
This mail message was not automatically generated by our Stupid2000 release
of Dumbscan which did not find any virus infected files in the (0) or more
attached file(s) in this message(s) in this/these posting(s). As such it seems
to be an exceptional condition and we are choosing to respond to ev
Hello guys,
I received many of warnings from You. I'm interested in what are U using to
check e-mails for virus. I'm using sendmail.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
> Sent: Thursday, November 02, 2000 9:38 AM
> To:
On Mon, Oct 30, 2000, David O'Brien wrote:
> On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
> > cd /crash/usr/src/sys/modules && env
> > MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
> > KMODDIR=/crash/boot/kernel make install
>
>
> Don't explicitly add DESTDIR to KM
John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> > John Polstra wrote:
> > > Overall I would lean toward putting the hack into pthread_mutex_lock.
> > > Comments?
> >
> > Huh, why we can't just bump libc_r version number and put older (buggy) ver
On Sun, Oct 29, 2000, John W. De Boskey wrote:
> Hi,
>
>I ran into an interesting gotcha with fsck and vinum...
>
>I have the following line in /etc/fstab:
>
> /dev/vinum/raid5/pubufs rw 2 2
>
>and during an upgrade (old current to current
>Interesting. THis needs about two bytes per page for the counter?
Actually, we found that a single byte per page was sufficient. Pages tended
to be either heavily accessed or rarely accessed. Even in the unusual case
where all pages are frequently accessed, the page reclaim rate (and thus
adj
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:34 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
THIS IS A VIRUS!
Peter Wagner wrote:
> VERY JOKE..! SEE PRESIDENT AND FBI TOP SECRET PICTURES..
>
>
> Name: DOMEO.JPG.vbs
>DOMEO.JPG.vbsType: VBScript File (application/x-unknown-content-type-V
Antigen for Exchange found DOMEO.JPG.vbs infected with
VBS/LoveLetter_based@mm virus.
The file is currently Deleted. The message, "US PRESIDENT AND FBI SECRETS
=PLEASE VISIT => (http://WWW.2600.CO", was
sent from Peter Wagner and was discovered in IMC Queues\Inbound
located at SONY/AMEXCH1/US-TI
Antigen for Exchange found DOMEO.JPG.vbs infected with
VBS/LoveLetter_based@mm virus.
The file is currently Deleted. The message, "US PRESIDENT AND FBI SECRETS
=PLEASE VISIT => (http://WWW.2600.CO", was
sent from Peter Wagner and was discovered in IMC Queues\Inbound
located at SONY/AMEXCH1/US-TI
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001102 03:06]:
>
> A L E R T E V I R U S
Your fucked up configuration is spewing this shit into a mailing list by
the dozen. Turn it off.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Antigen for Exchange found DOMEO.JPG.vbs matching =*.vbs file filter.
The file is currently Deleted. The message, "US PRESIDENT AND FBI SECRETS
=PLEASE VISIT => (http://WWW.2600.CO", was
sent from Peter Wagner and was discovered in IMC Queues\Inbound
located at SanBernardinoCounty/SBCOINT/GAUNTL
A L E R T E V I R U S
Notre système de détection automatique anti-virus
a détecté un virus dans un message qui vous a été
envoyé par Peter Wagner <[EMAIL PROTECTED]>.
La distribution de ce message a été stoppée.
Veuillez vous rapprocher de l'émetteur Peter Wagner
From: Peter Wagner [SMTP:[EMAIL PROTECTED]]
To:
Date: Thu, Nov 02 2000, 3:34:51 AM
Subject:US PRESIDENT AND FBI SECRETS =PLEASE VISIT
=> (http://WWW.2600.CO M)<=
The message contained 1 virus(es):
domeo.jp
From: Peter Wagner [SMTP:[EMAIL PROTECTED]]
To:
Date: Thu, Nov 02 2000, 4:34:51 AM
Subject:US PRESIDENT AND FBI SECRETS =PLEASE VISIT
=> (http://WWW.2600.CO M)<=
The message contained 1 virus(es):
domeo.jp
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
You have a problem :-(
Petr
-
DECROS s.r.o. J.S.Baara 40, Ceske Budejovice, Czech Republic
Tel: +420-38-7312808 Fax: +420-38-7311480 http://www.decros.cz
> -Original Message-
> From: Mail Delivery Subsy
Antigen for Exchange found DOMEO.JPG.vbs matching =*.vbs file filter.
The file is currently Deleted. The message, "US PRESIDENT AND FBI SECRETS
=PLEASE VISIT => (http://WWW.2600.CO", was
sent from Peter Wagner and was discovered in IMC Queues\Inbound
located at SanBernardinoCounty/SBCOINT/GAUNTL
From: Peter Wagner [SMTP:[EMAIL PROTECTED]]
To:
Date: Thu, Nov 02 2000, 4:34:51 AM
Subject:US PRESIDENT AND FBI SECRETS =PLEASE VISIT
=> (http://WWW.2600.CO M)<=
The message contained 1 virus(es):
domeo.jp
Have detected a virus (VBS_LOVELETTR.AS) in your mail traffic on 11/02/2000 08:43:04
with an action move.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
72 matches
Mail list logo
