Virus Alert
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
Virus Notification: A virus has been detected in a message in which you where a recipient
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.jpg.vbs infected with the VBS/LoveLetter_based@mm virus - - - Virus Notification: A virus has been detected in a message in which you where a recipient! Check the original message. If the attachment could not be repaired it was Deleted from the message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Antigen found =*.vbs file
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/GAUNTLET. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FW: Postmaster notify: Data format error
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 Subsystem [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 02, 2000 8:44 AM
To: [EMAIL PROTECTED]
Subject: Postmaster notify: Data format error
The original message was received at Thu, 2 Nov 2000 08:43:35
+0100 (CET)
from mx1.FreeBSD.org [216.136.204.125]
- The following addresses had permanent fatal errors -
[EMAIL PROTECTED]
(expanded from: [EMAIL PROTECTED])
[EMAIL PROTECTED]
(expanded from: [EMAIL PROTECTED])
- Transcript of session follows -
ANTIVIRUS SYSTEM FOUND VIRUSES
/var/spool/mqueue/dfIAA91820 archive: Mail
/var/spool/mqueue/dfIAA91820/DOMEO.JPG.vbsinfected:
I-Worm.LoveLetter
This message contains viruses. You may detect it and clean with
Antiviral Toolkit Pro from http://www.avp.ru or with your
preferred antivirus software.
554 [EMAIL PROTECTED]... Viruses were detected
501 [EMAIL PROTECTED]... Data format error
554 [EMAIL PROTECTED]... Viruses were detected
501 [EMAIL PROTECTED]... Data format error
begin 600 ATT00940.TXT
M4F5P;W)T:6YG+4U403H@9YS.R!NRYD96-R;W,N8WH-"E)E8V5I=F5D+49R
M;VTM351!.B!$3E,[(UX,2YF5E0E-$+F]R9PT*07)R:79A;"U$871E.B!4
M:'4L(#(@3F]V(#(P,#`@,#@Z-#,Z,S4@*S`Q,#`@*$-%5"D-"@T*1FEN86PM
M4F5C:7!I96YT.B!21D,X,C([(#QP+G!R:6)`95CF]S+F-Z/@T*6"U!8W1U
M86PM4F5C:7!I96YT.B!21D,X,C([('`N')I8D!E-H86YG92YD96-R;W,N
M8WH-"D%C=EO;CH@9F%I;5D#0I3=%T=7,Z(#4N-BXP#0I296UO=4M351!
M.B!$3E,[(UX,2YF5E0E-$+F]R9PT*3%S="U!='1E;7!T+41A=4Z(%1H
M=2P@,B!.;W8@,C`P,"`P.#HT,SHS."`K,#$P,"`H0T54*0T*#0I:6YA;"U2
M96-IEE;G0Z(%)0S@R,CL@/')E:]`95CF]S+F-Z/@T*6"U!8W1U86PM
M4F5C:7!I96YT.B!21D,X,C([(')E:]`97AC:%N9V4N95CF]S+F-Z#0I!
M8W1I;VXZ(9A:6QE9`T*4W1A='5S.B`U+C8N,`T*4F5M;W1E+4U403H@1$Y3
M.R!M#$N1G)E94)31"YOF-"DQAW0M071T96UP="U$871E.B!4:'4L(#(@
?3F]V(#(P,#`@,#@Z-#,Z,S@@*S`Q,#`@*$-%5"D-"@==
`
end
begin 600 ATT00941.TXT
M4F5T=7)N+5!A=@Z(#QO=VYEBUFF5E8G-D+7-E8W5R:71Y0$9R965"4T0N
M3U)'/@T*4F5C96EV960Z(9R;VT@;7@Q+D9R965"4T0N;W)G("AM#$N1G)E
M94)31"YOF@6S(Q-BXQ,S8N,C`T+C$R-5TI#0H)8GD@;G,N95CF]S+F-Z
M("@X+CDN,R\X+CDN,RD@=VET:"!%4TU44"!I9"!)04$Y,3@R,#L-"@E4:'4L
M(#(@3F]V(#(P,#`@,#@Z-#,Z,S4@*S`Q,#`@*$-%5"D-"@DH96YV96QO4M
M9G)O;2!O=VYEBUFF5E8G-D+7-E8W5R:71Y0$9R965"4T0N3U)'*0T*4F5C
M96EV960Z(9R;VT@:'5B+F9R965BV0N;W)G("AH=6(N1G)E94)31"YOF@
M6S(Q-BXQ,S8N,C`T+C$X72D-"@EB2!M#$N1G)E94)31"YOF@*%!OW1F
M:7@I('=I=@@15--5%`-"@EI9"!$.$,R1C9%,S9"-SL@5V5D+"`@,2!.;W8@
M,C`P,"`R,SHT,CHR-2`M,#@P,"`H4%-4*0T*4F5C96EV960Z()Y(AU8BYF
MF5E8G-D+F]R9R`H4]S=9I"P@9G)O;2!UV5R:60@-3,X*0T*"6ED(#$P
M,S8X,S=".#,X.R!7960L("`Q($YO=B`R,#`P(#(S.C0R.C(R("TP.#`P("A0
M4U0I#0I296-E:79E9#H@9G)O;2!L;V-A;AOW0@*QO8V%L:]S="!;,3(W
M+C`N,"XQ72D-"@EB2!H=6(N9G)E96)S9"YOF@*%!OW1F:7@I('=I=@@
M4TU44`T*"6ED(#0S,#(X,D4X,$-!.R!7960L("`Q($YO=B`R,#`P(#(S.C0R
M.C(R("TP.#`P("A04U0I#0I296-E:79E9#H@8GD@:'5B+F9R965BV0N;W)G
M("AB=6QK7VUA:6QEB!V,2XQ,BD[(%=E9"P@,2!.;W8@,C`P,"`R,SHT,CHR
M,B`M,#@P,`T*15L:79EF5D+51O.B!FF5E8G-D+7-E8W5R:71Y09R965B
MV0N;W)G#0I296-E:79E9#H@9G)O;2!S=6YS:71E+F%U8FDN94@*UA:6PN
M875B:2UO;FQI;F4N94@6S8R+C$U.2XX,BXQ,S%=*0T*"6)Y(AU8BYFF5E
M8G-D+F]R9R`H4]S=9I"D@=VET:"!%4TU44`T*"6ED(#$T-4,W,S="-C8W
M.R!7960L("`Q($YO=B`R,#`P(#(S.C,X.C,W("TP.#`P("A04U0I#0I296-E
M:79E9#H@9G)O;2!E-H86YG96(N875B:2YD92`H97AC:%N9V5B+F%U8FDN
M94@6S$W,"XU-BXQ,C$N-UTI#0H)8GD@W5NVET92YA=6)I+F1E("@X+CDN
M,RM3=6XO."XY+C,I('=I=@@15--5%`@:60@2D%!,C,P-#[#0H)5AU+"`R
M($YO=B`R,#`P(#`Y.C,X.C,V("LP,C`P("A'350I#0I296-E:79E9#H@8GD@
M97AC:%N9V5B+F%U8FDN94@=VET:"!);G1EFYE="!-86EL(%-EG9I8V4@
M*#4N-2XR-C4P+C(Q*0T*"6ED(#Q664TS,S$Q33X[(%1H=2P@,B!.;W8@,C`P
M,"`P.3HS-#HU,B`M,#`P,`T*365SV%G92U)1#H@/#=",45%1#!#-40U.$0T
M,3%"-S,R,#`U,#A"1$4W-T(R,#1$1#%%05X8VAA;F=E8BYA=6)I+F1E/@T*
M1G)O;3H@45T97(@5V%G;F5R(#QW86=N97)P0%U8FDN94^#0I4;SH@1G)E
M94)31"!,:7-T(#QF5E0E-$3ES=$!A=6)I+F1E/@T*4W5B:F5C=#H@55,@
M4%)%4TE$14Y4($%.1"!0DD@4T5#4D544R`]4$Q%05-%(%9)4TE4(#T^("AH
M='1P.B\O5U=7+C(V,#`N0T\-"@E-*3P]#0I$871E.B!4:'4L(#(@3F]V(#(P
M,#`@,#DZ,S0Z-3$@+3`P,#`@#0I-24U%+59EG-I;VXZ(#$N,`T*6"U-86EL
M97(Z($EN=5R;F5T($UA:6P@4V5R=FEC92`H-2XU+C(V-3`N,C$I#0I#;VYT
M96YT+51Y4Z(UU;'1I%R="]M:7AE9#L-"@EB;W5N9%R3TB+2TM+5\]
M7TYE'1087)T7S`P,%\P,4,P-#1","XR-CQ,$0Y,"(-"E-E;F1ECH@;W=N
M97(M9G)E96)S9"US96-UFET4!F5E0E-$+D]21PT*6"U,;V]P.B!F5E
;0E-$+F]R9PT*4')E8V5D96YC93H@8G5L:PT*
`
end
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Virus Notification: A virus has been detected in a message in which you where a recipient
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.jpg.vbs infected with the VBS/LoveLetter_based@mm virus - - - Virus Notification: A virus has been detected in a message in which you where a recipient! Check the original message. If the attachment could not be repaired it was Deleted from the message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Virus Notification: A virus has been detected in a message in which you where a recipient
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.jpg.vbs infected with the VBS/LoveLetter_based@mm virus - - - Virus Notification: A virus has been detected in a message in which you where a recipient! Check the original message. If the attachment could not be repaired it was Deleted from the message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ALERTE: VIRUS DETECTE DANS UN MESSAGE ENVOYE PAR owner-freebsd-security@FreeBSD.ORG
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 [EMAIL PROTECTED] pour régler avec lui le problème. *** V I R U S A L E R T Our anti-virus system has detected a virus in an email sent by Peter Wagner [EMAIL PROTECTED]. We have stopped the delivery of this email. We invite you to contact Peter Wagner [EMAIL PROTECTED] to solve the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Antigen found =*.vbs file
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/GAUNTLET. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ALERTE: VIRUS DETECTE DANS UN MESSAGE ENVOYE PAR owner-freebsd-security@FreeBSD.ORG
* [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 message
Antigen found VBS/LoveLetter_based@mm virus
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-XIMS-1. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Antigen found VBS/LoveLetter_based@mm virus
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-XIMS-1. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
THIS IS A VIRUS, DONT OPEN!
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-VBSFile) Encoding: quoted-printable To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current paging strategy
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 adjustment rate of the page references count) increases high enough to still provide for a decent distribution of the counters and for the page LOU to be effective. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum fsck wrappers strangeness
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), I commented the line out during the reboot process. After bringing the new system online, I executed: /sbin/fsck -y /dev/vinum/raid5 and received the following error: fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory OK. That means that the disklabel checks are failing for type 'vinum'. I'll take a look at this. What you should be doing is running fsck with a type, ie fsck -t ufs /dev/vinum/raid5 So, it appears that fsck is attempting to determine a file system type, tries to use /etc/fstab, and then falls back to a secondary scheme. In the secondary scheme, ufs is what we want, but vinum is what we're getting. If anyone has any information about this please let me know. I'll try to look into it tomorrow. I'll try fix the autodetect for vinum partition types (if its possible, I seem to remember there being a vinum type in the header files). Its weird though, I would have thought a vinum device would be type FSTYPE (eg BSD4.3) rather than VINUM, which I'd associate with the underlying devices .. Adrian -- Adrian Chadd"Programming is like sex: [EMAIL PROTECTED] One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
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) version into lib/compat as usually? This would not require any ugly hacks at all. 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 will help old executables, because they won't even use the new libgcc_r. Nope it should help, because the bug is triggered if someone tries to use old executables with new libc_r. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make DESTDIR=foo failing in installkernel ?
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 KMODDIR. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX Thats all fine and good, but I don't want to touch the makefile magic. Can someone else proficient in Makefile h0h0magick do it if it hasn't been done already? :) Thanks! Adrian -- Adrian Chadd"Programming is like sex: [EMAIL PROTECTED] One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: VIRUS WARNING
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: Peter Wagner Cc: FreeBSD List Subject: VIRUS WARNING 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 M)=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Not a virus warning. This message is declared safe by Dumbscan2000
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 everyone and their dog to notify them of this rare occurence for this list. Should any other actual highly rare human generated messages be detected on this otherwise mail robot dominated list, our software will definitely notify you of this extraordinary occurence and deliver a novel form of list managed DoS through automated replies and thereby guarantee that your supply of highly repetitive robot messages is not put in jeopardy. We now return you to your regularly scheduled robots... -- Dragos Ruiu [EMAIL PROTECTED] dursec.com ltd. / kyx.net - we're from the future gpg/pgp key on file at wwwkeys.pgp.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VIRUS WARNING
[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 "unsubscribe freebsd-current" in the body of the message
Re: Not a virus warning. This message is declared safe by Dumbscan2000
joke Nice product... where can I download this?? ;) Perhaps you should put this in the ports tree?? *chuckle* /joke 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 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 everyone and their dog to notify them of this rare occurence for this list. Should any other actual highly rare human generated messages be detected on this otherwise mail robot dominated list, our software will definitely notify you of this extraordinary occurence and deliver a novel form of list managed DoS through automated replies and thereby guarantee that your supply of highly repetitive robot messages is not put in jeopardy. We now return you to your regularly scheduled robots... -- Dragos Ruiu [EMAIL PROTECTED] dursec.com ltd. / kyx.net - we're from the future gpg/pgp key on file at wwwkeys.pgp.net -- Change will happen whether we're still or moving... -- Toad the Wet Sprocket To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
small error in linux_ioctl.c
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 attached), both linux module and statically build are all fine on i386 platform. -- CirX - This site doesnt' exist. 9c k9o h9 s1bg s1f=, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38 =. ant sj m8r ob =? 1fj mwby a1 tao vg5 =. soq df v ' .a. CirX=. --- linux_ioctl.c~ Thu Nov 2 17:10:56 2000 +++ linux_ioctl.c Thu Nov 2 20:38:26 2000 @@ -57,7 +57,6 @@ #include machine/../linux/linux_proto.h #endif -#include linux_proto.h #ifdef __alpha__ #include machine/../linux/linux_ioctl.h #else
Re: * watchdog timeout (Was: dc0: watchdog timeout)
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 works ok. Generally watchdog timeouts from pccard devices mean that your irqs are fubar'd. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message 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? -- Loose bits sink chips. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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. Reported by: Wesley Morgan [EMAIL PROTECTED] Submitted by: gallatin Acknowledged by: phk After this change, it panics when you perform stat against a linux block device node. Actually, emulators/vmware2 port creates some block device nodes in /compat/linux/dev, so all the vmware2 users still have ones installed. And when they hit `ls /compat/linux/dev' or `pkg_delete vmware-2.0.x.yyy', they will see their boxen panic. ;) I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). Please fix it! ; -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
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 works fine and at top speed after the init, then the watchdog is happening just a tad fast. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
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 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 works fine and at top speed after the init, then the watchdog is happening just a tad fast. -- Speak softly and carry a cellular phone. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.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 a block device isn't that useful anymore. Reported by: Wesley Morgan [EMAIL PROTECTED] Submitted by: gallatin Acknowledged by: phk After this change, it panics when you perform stat against a linux block device node. Actually, emulators/vmware2 port creates some block device nodes in /compat/linux/dev, so all the vmware2 users still have ones installed. And when they hit `ls /compat/linux/dev' or `pkg_delete vmware-2.0.x.yyy', they will see their boxen panic. ;) I'm 100% sure this change caused the panic because the stack trace showed it panicked at vfinddev() called from linux_ustat(). Hmm.. I seem to remember seeing something similar yesterday when my alpha was booting a brand new kernel with a 2 day-old userland. It was crashing in vfinddev called out of savecore and dev_mkdb. Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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% confused looking alternatively at source and ddb console. Sorry for the false report, but I'm repoting the truth this time. ;) Anyway, I think you can reproduce the panic by installing vmware2 port and doing `ls /compat/linux/dev'. Regards, -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: small error in linux_ioctl.c
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) By removing the line 60 (see the patch attached), both linux module and statically build are all fine on i386 platform. .. Thanks. I've committed your fix. That snuck in when David I were tossing patches back and forth for linux/alpha support. Drew -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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() -- addaliasu() -- ufs_vinit(). Seems I was 100% confused looking alternatively at source and ddb console. Sorry for the false report, but I'm repoting the truth this time. ;) Anyway, I think you can reproduce the panic by installing vmware2 port and doing `ls /compat/linux/dev'. To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls? I don't suppose you could throw an older kernel on and show the output of /bin/ls /compat/linux/dev ? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev() (dev_t=#bpf/0)
[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 what needs to be done? I'm not aware someone is working on it. It doesn't look like it needs much work, but I don't know the details as I said. For pointers: mail archives. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SB32 turned to mono only
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
Re: cvs commit: src/sys/compat/linux linux_stats.c
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 5.0-CURRENT as of two days ago. This operation causes panic on the latest CURRENT: knu@archon[2]% uname -a FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Tue Oct 31 15:11:38 JST 2000 [EMAIL PROTECTED]:/usr/local/src/sys/compile/ARCHON i386 knu@archon[2]% ls -l /compat/linux/dev total 0 brw-r--r-- 1 root wheel - 0, 0x00010002 Nov 2 20:28 hda brw-r--r-- 1 root wheel - 0, 0x0001000a Nov 2 20:28 hdb crw-rw-rw- 1 root wheel - 2, 2 Nov 2 20:28 null crw-r--r-- 1 root wheel - 202, 0 Nov 2 20:17 rtc lrwxr-xr-x 1 root wheel - 22 Nov 2 20:28 tty0@ - /compat/linux/dev/tty1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty1@ - /dev/ttyv0 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty10@ - /dev/ttyv9 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty11@ - /dev/ttyva lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty12@ - /dev/ttyvb lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty2@ - /dev/ttyv1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty3@ - /dev/ttyv2 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty4@ - /dev/ttyv3 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty5@ - /dev/ttyv4 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty6@ - /dev/ttyv5 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty7@ - /dev/ttyv6 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty8@ - /dev/ttyv7 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty9@ - /dev/ttyv8 crw-r--r-- 1 root wheel - 200, 0 Nov 2 20:28 vmmon crw-r--r-- 1 root wheel - 149, 0x00010001 Nov 2 20:35 vmnet1 As you see, hda and hdb are block devices that might cause the panic.. -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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: vfinddev() -- addaliasu() -- ufs_vinit(). Seems I was 100% confused looking alternatively at source and ddb console. Yes, this is my bad. I'm looking at it right now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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 handling this, or anybody can give pointers as to what needs to be done? I'm not aware someone is working on it. It doesn't look like it needs much work, but I don't know the details as I said. For pointers: mail archives. 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: Index: bpf.c === RCS file: /usr/cvs/src/sys/net/bpf.c,v retrieving revision 1.68 diff -u -r1.68 bpf.c --- bpf.c 2000/10/09 14:19:09 1.68 +++ bpf.c 2000/11/02 20:26:09 @@ -363,7 +363,7 @@ */ if (d) return (EBUSY); - if (!dev-si_flags SI_NAMED) + if (!devfs_present) make_dev(bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, "bpf%d", dev2unit(dev)); MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); Hmm. Or try doing changing it to this instead: if (dev-si_flags SI_NAMED != 0) It could be an order of operations buglet. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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 archives. Somewhere... :-) Anybody handling this, or anybody can give pointers as to what needs to be done? I'm not aware someone is working on it. It doesn't look like it needs much work, but I don't know the details as I said. For pointers: mail archives. 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: Index: bpf.c === RCS file: /usr/cvs/src/sys/net/bpf.c,v retrieving revision 1.68 diff -u -r1.68 bpf.c --- bpf.c 2000/10/09 14:19:09 1.68 +++ bpf.c 2000/11/02 20:26:09 @@ -363,7 +363,7 @@ */ if (d) return (EBUSY); - if (!dev-si_flags SI_NAMED) + if (!devfs_present) make_dev(bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, "bpf%d", dev2unit(dev)); MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); Hmm. Or try doing changing it to this instead: if (dev-si_flags SI_NAMED != 0) It could be an order of operations buglet. Argh, that should be "== 0" not "!= 0". -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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 revision 1.68 diff -u -r1.68 bpf.c --- bpf.c 2000/10/09 14:19:09 1.68 +++ bpf.c 2000/11/02 20:26:09 @@ -363,7 +363,7 @@ */ if (d) return (EBUSY); - if (!dev-si_flags SI_NAMED) + if (!devfs_present) make_dev(bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, "bpf%d", dev2unit(dev)); MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); Hmm. Or try doing changing it to this instead: if (dev-si_flags SI_NAMED != 0) It could be an order of operations buglet. Give me a couple of days to play with it... -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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 panic is caused by a native binary? Not at all. Sorry, that was my mistaken assumption, after all. :( I confirmed linux ls didn't cause panic, so the culprit should belong somewhere else. Hopefully phk will catch it for us. :) -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
disabling tcp.newreno in 72 hours...
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. Anybody interested in studying the problem can find two packet captures at: http://phk.freebsd.dk/newreno -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
i386/20379
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.org/cgi/query-pr.cgi?pr=20379 -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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/bin/ls? Yes. How is linux_ustat involved if the panic is caused by a native binary? Not at all. Sorry, that was my mistaken assumption, after all. :( 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386/20379
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 aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/compat/linux linux_stats.c
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 that your fix solved the problem! Thanks! knu@archon[3]% uname -a FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #25: Fri Nov 3 06:28:04 JST 2000 [EMAIL PROTECTED]:/usr/local/src/sys/compile/ARCHON i386 knu@archon[3]% ls -l /compat/linux/dev total 0 brw-r--r-- 1 root wheel - 0, 0x00010002 Nov 2 20:28 hda brw-r--r-- 1 root wheel - 0, 0x0001000a Nov 2 20:28 hdb crw-rw-rw- 1 root wheel - 2, 2 Nov 2 20:28 null crw-r--r-- 1 root wheel - 202, 0 Nov 2 20:17 rtc lrwxr-xr-x 1 root wheel - 22 Nov 2 20:28 tty0@ - /compat/linux/dev/tty1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty1@ - /dev/ttyv0 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty10@ - /dev/ttyv9 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty11@ - /dev/ttyva lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty12@ - /dev/ttyvb lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty2@ - /dev/ttyv1 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty3@ - /dev/ttyv2 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty4@ - /dev/ttyv3 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty5@ - /dev/ttyv4 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty6@ - /dev/ttyv5 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty7@ - /dev/ttyv6 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty8@ - /dev/ttyv7 lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty9@ - /dev/ttyv8 crw-r--r-- 1 root wheel - 200, 0 Nov 2 20:28 vmmon crw-r--r-- 1 root wheel - 149, 0x00010001 Nov 2 20:35 vmnet1 knu@archon[3]% -- / /__ __ / ) ) ) ) /and.or.jp / ruby-lang.org Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Using tape drives in linux emulation
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 a can-be-done condition (what?) Do you know what you need? Nothing special just rewind, fsf, ... The density or compression stuff is not needed. That's a rewind using FreeBSD mt: 679 mt CALL open(0xbfbff86e,0,0x6) 679 mt NAMI "/dev/nrsa0" 679 mt RET open 3 679 mt CALL ioctl(0x3,MTIOCTOP,0xbfbff5c4) 679 mt RET ioctl 0 And here what claims to be a rewind with the linux app: 682 tapeexercise CALL open(0xbfbff8a8,0x2,0) 682 tapeexercise NAMI "/compat/linux/dev/nrsa0" 682 tapeexercise NAMI "/dev/nrsa0" 682 tapeexercise RET open 3 682 tapeexercise CALL ioctl(0x3,0x40086d01 ,0xbfbff634) 682 tapeexercise RET ioctl -1 errno -22 Unknown error: -22 682 tapeexercise CALL ktrace(0x810b000) 682 tapeexercise RET ktrace 135311360/0x810b000 682 tapeexercise CALL write(0x2,0xbfbfcb9c,0x3e) 682 tapeexercise GIO fd 2 wrote 62 bytes "tapeexercise: rewind ioctl failed, errno 22: Invalid argument " -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in vfinddev in -current
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,c0abe900,c0abed00,c877acec,c333f380) at ufs_vinit+0x4e ffs_vget(c0b01c00,1882,c877ad60,0,c7dc1900) at ffs_vget+0x267 ufs_lookup(c877adb8,c877adcc,c018e6fa,c877adb8,c7dc1900) at ufs_lookup+0x995 ufs_vnoperate(c877adb8,c7dc1900,c8770c03,c877aeb4,c877adc0 at ufs_vnoperate+15 vfs_cache_lookup(c877ae10,c877ae20,c0191804,c877ae10,c7dc1900) at vfs_cache_lookup+0x28a ufs_vnoperate(c877ae10,c7dc1900,c0b1c800,c877aeb4,c77e5840) at ufs_vnoperate+0x15 lookup(c877ae8c,c02b57d8,0,c77e5840,c77e5840) at lookup+0x290 namei(c877ae8c,c02b57d8,0,c77e5840,80b4340) at namei+0x178 lstat(c88e5840,c877af80,80b4348,80b5028,80b4300) at lstat+0x41 syscall2(2f,2f,2f,80b4300,80b5028) at syscall2+0x33c Xint0x80_syscall() at Xint0x80_syscall+0x1f Since addaliasu doesn't bother to check for NODEV, I take it this is a "can't happen" situation? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make DESTDIR=foo failing in installkernel ?
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=/crash/boot/kernel make install Don't explicitly add DESTDIR to KMODDIR. Thats all fine and good, but I don't want to touch the makefile magic. I mean when you set KMODDIR, only use "/boot/kernel", as the bsd.*.mk Makefiles will add DESTDIR for you. Can someone else proficient in Makefile h0h0magick do it if it hasn't been done already? :) Not sure what Makefile hackery is needed as I'm not sure what you're wanting to do. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in vfinddev in -current
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(,3,c877ac84,10002,1) at vfinddev+0xc = NODEV addaliasu(c7dc0a00,10002,c0b04800,c33e1180,c0b149e4) at ufs_vinit+0x44 ufs_vinit(c0b01c00,c0abe900,c0abed00,c877acec,c333f380) at ufs_vinit+0x4e ffs_vget(c0b01c00,1882,c877ad60,0,c7dc1900) at ffs_vget+0x267 ufs_lookup(c877adb8,c877adcc,c018e6fa,c877adb8,c7dc1900) at ufs_lookup+0x995 ufs_vnoperate(c877adb8,c7dc1900,c8770c03,c877aeb4,c877adc0 at ufs_vnoperate+15 vfs_cache_lookup(c877ae10,c877ae20,c0191804,c877ae10,c7dc1900) at vfs_cache_lookup+0x28a ufs_vnoperate(c877ae10,c7dc1900,c0b1c800,c877aeb4,c77e5840) at ufs_vnoperate+0x15 lookup(c877ae8c,c02b57d8,0,c77e5840,c77e5840) at lookup+0x290 namei(c877ae8c,c02b57d8,0,c77e5840,80b4340) at namei+0x178 lstat(c88e5840,c877af80,80b4348,80b5028,80b4300) at lstat+0x41 syscall2(2f,2f,2f,80b4300,80b5028) at syscall2+0x33c Xint0x80_syscall() at Xint0x80_syscall+0x1f Since addaliasu doesn't bother to check for NODEV, I take it this is a "can't happen" situation? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in vfinddev in -current
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) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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 patch nonetheless... I'll be back. -- I believe the technical term is "Oops!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD-current problem with my AC97 sound card
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: VIA VT82C686A AC'97 Audio at io 0xdc00 irq 5 (1p/1r channels duplex)
but when i play sound, the sound is very ugly, why?
The following is my dmesg message:
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Thu Nov 2 17:34:37 GMT 2000
[EMAIL PROTECTED]:/home/src/sys/compile/amd
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 700029408 Hz
CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x642 Stepping = 2
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
AMD Features=0xc044b18,AMIE,DSP,3DNow!
real memory = 134152192 (131008K bytes)
config di sn0
config di lnc0
config di le0
config di ie0
config di fe0
config di cs0
config di bt0
config di aic0
config di aha0
config di adv0
config q
avail memory = 126980096 (124004K bytes)
Preloaded elf kernel "kernel" at 0xc038b000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc038b09c.
Preloaded elf module "random.ko" at 0xc038b0ec.
module_register: module random already exists!
Module random failed to register: 17
Pentium Pro MTRR support enabled
WARNING: Driver mistake: repeat make_dev("random")
WARNING: Driver mistake: repeat make_dev("urandom")
md0: Malloc disk
Using $PIR table, 7 entries at 0xc00fdd20
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pcib1: VIA 8363 (KT133) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 0.0 irq 10
isab0: VIA 82C686 PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686 ATA66 controller port 0xd000-0xd00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: VIA 83C572 USB controller at 7.2 irq 11
pci0: VIA 83C572 USB controller at 7.3 irq 11
pcm0: VIA VT82C686A AC'97 Audio port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 5
at device 7.5 on pci0
ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xe800-0xe81f irq 11 at device 11.0 on
pci0
ed0: address 52:54:ab:1b:c6:05, type NE2000 (16 bit)
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
plip0: PLIP network interface on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources
unknown: PNP0f13 can't assign resources
unknown: PNP0700 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0400 can't assign resources
ad0: 19574MB WDC WD205BA [39770/16/63] at ata0-master UDMA66
acd0: CDROM SAMSUNG CD-ROM SC-140F at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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 === RCS file: /usr/cvs/src/sys/net/bpf.c,v retrieving revision 1.68 diff -u -r1.68 bpf.c --- bpf.c 2000/10/09 14:19:09 1.68 +++ bpf.c 2000/11/02 20:26:09 @@ -363,7 +363,7 @@ */ if (d) return (EBUSY); - if (!dev-si_flags SI_NAMED) + if (!devfs_present) make_dev(bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, "bpf%d", dev2unit(dev)); MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); Hmm. Or try doing changing it to this instead: if (dev-si_flags SI_NAMED != 0) It could be an order of operations buglet. Give me a couple of days to play with it... 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 . -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WARNING: driver bpf should register devices with make_dev()
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: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) BTW, I've not received your email; are you busy working? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation
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, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] There are things that are so serious that you can only joke about them. -- Werner Heisenberg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 morning. I'm Sorry. I wanted to test it on my machine with Celeron 300MHz. 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 compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) I understood the situation. I'll look into the Makefile's under src/sys. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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. I'll look into the Makefile's hosokawa under src/sys. Uncutted logfile of Nov/01/2000 may also helps you. You can fetch it from URL:ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/log/. However, this problem (use /usr/src/sys/modules for compilation) is disappeared already according to the logfile of Nov/02/2000. -- - Makoto `MAR' MATSUSHITA go to lunch right now... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern subr_diskslice.c src/sys/sys diskslice.h src/sys/cam/scsi scsi_cd.c
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/cam/scsi scsi_cd.c
Log:
Write support for the cd(4) driver.
I get the following messages when I hit "cdcontrol -f /dev/cd0 play"
against a music CD:
Oct 31 16:06:40 archon /boot/kernel/kernel: (cd0:ahc0:0:2:0): READ(10). CDB: 28 0 0
0 0 1 0 0 1 0
Oct 31 16:06:40 archon /boot/kernel/kernel: (cd0:ahc0:0:2:0): ILLEGAL REQUEST
asc:64,0
Oct 31 16:06:40 archon /boot/kernel/kernel: (cd0:ahc0:0:2:0): Illegal mode for this
track
Oct 31 16:06:40 archon /boot/kernel/kernel: (cd0:ahc0:0:2:0): cddone: got error 0x16
back
Though the music goes just fine.
I've got a patch, see if this fixes the problem.
Ken
--
Kenneth Merry
[EMAIL PROTECTED]
//depot/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c#13 -
/a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c
*** /tmp/tmp.13048.0Thu Nov 2 21:07:47 2000
--- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_cd.c Thu Nov 2 21:05:02
2000
***
*** 207,212
--- 207,213
u_int32_t sense_flags);
staticvoidcdprevent(struct cam_periph *periph, int action);
staticint cdsize(dev_t dev, u_int32_t *size);
+ staticint cdfirsttrackisdata(struct cam_periph *periph);
staticint cdreadtoc(struct cam_periph *periph, u_int32_t mode,
u_int32_t start, struct cd_toc_entry *data,
u_int32_t len);
***
*** 920,925
--- 921,937
}
/*
+* If we get a non-zero return, revert back to not reading the
+* label off the disk. The first track is likely audio, which
+* won't have a disklabel.
+*/
+ if ((error = cdfirsttrackisdata(periph)) != 0) {
+ softc-disk.d_dsflags = ~DSO_COMPATLABEL;
+ softc-disk.d_dsflags |= DSO_NOLABELS;
+ error = 0;
+ }
+
+ /*
* Build prototype label for whole disk.
* Should take information about different data tracks from the
* TOC and put it in the partition table.
***
*** 993,998
--- 1005,1017
cdprevent(periph, PR_ALLOW);
/*
+* Unconditionally set the dsopen() flags back to their default
+* state.
+*/
+ softc-disk.d_dsflags = ~DSO_NOLABELS;
+ softc-disk.d_dsflags |= DSO_COMPATLABEL;
+
+ /*
* Since we're closing this CD, mark the blocksize as unavailable.
* It will be marked as available whence the CD is opened again.
*/
***
*** 2540,2545
--- 2559,2638
return (error);
+ }
+
+ /*
+ * The idea here is to try to figure out whether the first track is data or
+ * audio. If it is data, we can at least attempt to read a disklabel off
+ * the first sector of the disk. If it is audio, there won't be a
+ * disklabel.
+ *
+ * This routine returns 0 if the first track is data, and non-zero if there
+ * is an error or the first track is audio. (If either non-zero case, we
+ * should not attempt to read the disklabel.)
+ */
+ static int
+ cdfirsttrackisdata(struct cam_periph *periph)
+ {
+ struct cdtocdata {
+ struct ioc_toc_header header;
+ struct cd_toc_entry entries[100];
+ };
+ struct cd_softc *softc;
+ struct ioc_toc_header *th;
+ struct cdtocdata *data;
+ int num_entries, i;
+ int error, first_track_audio;
+
+ error = 0;
+ first_track_audio = -1;
+
+ softc = (struct cd_softc *)periph-softc;
+
+ data = malloc(sizeof(struct cdtocdata), M_TEMP, M_WAITOK);
+
+ th = data-header;
+ error = cdreadtoc(periph, 0, 0, (struct cd_toc_entry *)data,
+ sizeof(*data));
+
+ if (error)
+ goto bailout;
+
+ if (softc-quirks CD_Q_BCD_TRACKS) {
+ /* we are going to have to convert the BCD
+* encoding on the cd to what is expected
+*/
+ th-starting_track =
+ bcd2bin(th-starting_track);
+ th-ending_track = bcd2bin(th-ending_track);
+ }
+ th-len = scsi_2btoul((u_int8_t *)th-len);
+
+ if ((th-len - 2) 0)
+ num_entries = (th-len - 2) / sizeof(struct cd_toc_entry);
+ else
+ num_entries = 0;
+
+ for (i = 0; i num_entries; i++) {
+ if (data-entries[i].track == th-starting_track) {
+ if (data-entries[i].control 0x4)
+ first_track_audio = 0;
+ else
+
new zero copy sockets and NFS snapshot
[ -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 welcome. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - Robert Picco's zero copy send code has been removed. It was never fixed to eliminate a data corruption problem, and it is likely that Drew Gallatin's code will make it into -current instead. - Bring the major number used in the ti(4) driver in line with the one we have reserved in sys/conf/majors. - Make sure calls to ti_hdr_split() are only made inside #ifdef TI_JUMBO_HDRSPLIT. - Convert the non-stock portions of the ti(4) driver from spls to mutexes. - Get rid of an extra make_dev(), and make sure the one in ti_attach() comes before we return. For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Zero copy send and receive code, written by Drew Gallatin [EMAIL PROTECTED]. - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. The Alteon header splitting and debugging code was written for Pluto Technologies (www.plutotech.com), which kindly agreed to let me release the code. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
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 will help old executables, because they won't even use the new libgcc_r. Nope it should help, because the bug is triggered if someone tries to use old executables with new libc_r. Yes, I think you're right after all. But since I've already worked around the problem in libc_r, there's no need to do anything else at this point. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABI is broken??
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" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 === 3dfx Warning: Object directory not changed from original /usr/src/sys/modules/3dfx Maybe it doesn't occur before, and today's make release is also failed. cd ../../modules env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMDDIR= make install === 3dfx install -c -o root -g wheel -m 555 3dfx.ko /R/stage/kernels install: 3dfx.ko: No such file or directory -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 compilation.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
