Re: bad tcp cksum fffe!
Dear Giorgos, Thanks for your suggestion! The problem has gone away by backing off to -O1 in kernel and -O2 in userland. Strange, because I have been using -O3 -fomit-frame-pointer for a while now (/usr/share/examples/etc/make.conf notwithstanding) with ill effects. My bad. Sorry, but I can't be more specific on which particular flag or which particular CVS update caused the problem. CPU too slow. Thanks again, -- Chris On Tuesday, Giorgos Keramidas said: On 2002-05-14 17:39, Cristan Szmajda wrote: Dear freebsd-current, Any suggestions you have regarding this problem would be much appreciated. My laptop running -CURRENT is suddenly generating bad TCP checksums when talking to some IPs but not others. For example, 129.94.209.220 is a problem, 17:08:47.026823 129.94.233.200.1032 129.94.209.220.22: S [bad tcp cksum fffe!] 3868790363:3868790363(0) win 65535 mss 1460,nop,wscale 1,nop,nop,timestamp 542813 0,nop,nop,ccnew 10 (DF) (ttl 64, id 347, len 68) I've seen this only twice. The first time I was using too funky optimizations to the CFLAGS of my kernel, and GCC was obviously doing something wrong with the checksum generation code. If this is the case, then rebuild your kernel and userland with the suggested optimizations from /usr/share/examples/etc/make.conf and see if this fixes things for you. The second one was when my tcpdump (and the rest of the userland) was really VERY out of sync with the running kernel (I had managed to upgrade only the kernel and tcpdump was probably reading random data from bpf). But there were other more important things wrong with this case. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: loader failure
On Wed, 15 May 2002, John Baldwin wrote: On 15-May-2002 Dag-Erling Smorgrav wrote: John Baldwin [EMAIL PROTECTED] writes: The kernel overflowed it's stack. In SRM, you can try to debug this by using 'e sp' to get the stack pointer then get a stack dump and save a copy of it in a log or something, reboot the machine, then use gdb's list command on the kernel.debug to figure out the source:line for all the kernel-text addresses in the stack dump to figure out the backtrace. How do I get a stack trace? I can't get the 'examine' command to actually print anything... It depends on which machine actually. :-/ First do 'e sp' to get the stack pointer. Then you want to do something like this: e -n 100 value of sp without any leading 0x At least for i386's, it can be useful to set $esp and $eip to non-preposterous values if they are hosed (record the old values first). Bugs in the pagefault handler make the behaviour for invalid pointers very bad. The main one trap_pfault() doesn't give up immediately if the pagefault is from within ddb. In old versions of FreeBSD, this is probably only fatal if trap_pfault() blocks, but in -current is is fatal in the usual case where trap_fault() acquires a sleep lock. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
/usr/ports/emulators/bochs on -CURRENT
# grep BOCHS /etc/make.conf WITH_BOCHS_CPU_LEVEL= 6 WITH_BOCHS_PROCESSORS= 1 # uname -v FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 [...] # cd /usr/ports/emulators/bochs make [...] gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include -I.. -I./.. -I../instrument/stubs -I./../instrument/stubs cdrom.cc -o cdrom.o In file included from cdrom.cc:40: /usr/include/arpa/inet.h:102: conflicting types for `typedef __uint32_t socklen_t' ../osdep.h:105: previous declaration as `typedef int socklen_t' gmake[1]: *** [cdrom.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' gmake: *** [iodev/libiodev.a] Error 2 *** Error code 2 I tryed with cdrom support disabled in Makefile and it go forward: # diff -u0 Makefile.orig Makefile --- Makefile.orig Thu May 16 09:48:29 2002 +++ MakefileThu May 16 10:32:58 2002 @@ -34 +34 @@ -CONFIGURE_ARGS=--enable-cdrom \ +CONFIGURE_ARGS=--disable-cdrom \ # make clean make [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include-I. -I./. -Iinstrument/stubs -I./instrument/stubs logio.cc -o logio.o c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include-I. -I./. -Iinstrument/stubs -I./instrument/stubs main.cc -o main.o main.cc: In function `int bx_init_hardware()': main.cc:1177: `i' undeclared (first use this function) main.cc:1177: (Each undeclared identifier is reported only once main.cc:1177: for each function it appears in.) gmake: *** [main.o] Error 1 *** Error code 2 I (badly?) hacked main.cc to remove line 1177 and it compile fine. # diff -u0 main.cc.orig main.cc --- main.cc.origWed Mar 27 17:05:14 2002 +++ main.cc Thu May 16 11:02:38 2002 @@ -1177 +1177 @@ - BX_CPU(0)-local_apic.set_id (i); + // BX_CPU(0)-local_apic.set_id (i); I'm not able to check if it run until 19:00 CEST because I compile it from a remote ssh. And I think that commenting previous line is really bad :-) Can you (help me to) check what is wrong (my config, my -CURRENT, port, ...)? TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: don't know how to make buildincludes in buildworld from -stable to -current
more info on this problem:
Hans Lambermont wrote:
cd /usr/src; make buildincludes; make installincludes
make: don't know how to make buildincludes. Stop
I found the buildincludes target in share/mk/bsd.incs.mk
These mk files should have been used (
MAKE= PATH=${PATH} make -m ${.CURDIR}/share/mk -f Makefile.inc1
in the main Makefile) but are not. If I do a
cd /usr/src; make -m share/mk -f Makefile.inc1 buildincludes
this target is made just fine.
I copied /usr/src/share/mk to /usr/share/mk , added the targets
'buildincludes installincludes' to 'TGTS' in the main Makefile , and now
cd /usr/src; make buildworld
breaks a little later with:
make: don't know how to make incsinstall. Stop
Is anyone else able to upgrade from stable to current ?
As usual any thoughts on this are welcome.
Hans Lambermont
--
http://lambermont.webhop.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
Terry Lambert [EMAIL PROTECTED] wrote: Thomas David Rivers wrote: Well - it's not counter-intuitive on many machines... For example, on the IBM mainframe - there is an instruction to load a character into a register - but not one that loads *and* sign-extends. So, you can get much better code if characters are unsigned by default. Sounds like time to get out the wire wrap tools... and fix the hardware, not the software. Ha! That may not be a bad idea :-) So in our C/C++ compilers for the mainframe, the default is unsigned as well. I wonder if the AIX people were looking for mainframe compatibility in this decision, or was it motivated by the PowerPC instruction set? Does anyone know what the Mac default is (since they are PowerPC based as well?) RS/6000's didn't used to use PPC processors at all; so it's probably intentional software compatability. I'm confused then - the one we have here seems to. There was a version of something very RS/6000-like that didn't, but I thought RS/6000s did... - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
[CC: obrien, who has been working on bringing in gcc 3.1]
At Wed, 15 May 2002 20:46:06 -0700,
Bill Fenner wrote:
So - yes - it seems gcc 3.1 does have a problem...
Indeed - easily determined by breaking down the expression.
So, who's gonna report it to gcc-bugs? knu?...
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
j = ((char)(i 1)) / 2;
printf(%d\n, j);
j = ((char)(i 1));
printf(%d\n, j / 2);
return 0;
}
Somehow, specifying -fsigned-char, which I thought was the default,
fixed the problem. So, the cause may be in our configuration of gcc?
I'll send-pr if it isn't.
--
/
/__ __Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
Somewhere out of a memory.. of lighted streets on quiet nights..
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
On Thu, 16 May 2002, Akinori MUSHA wrote:
[CC: obrien, who has been working on bringing in gcc 3.1]
At Wed, 15 May 2002 20:46:06 -0700,
Bill Fenner wrote:
So, who's gonna report it to gcc-bugs? knu?...
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
j = ((char)(i 1)) / 2;
printf(%d\n, j);
j = ((char)(i 1));
printf(%d\n, j / 2);
return 0;
}
Somehow, specifying -fsigned-char, which I thought was the default,
fixed the problem. So, the cause may be in our configuration of gcc?
-fsigned-char doesn't fix it for me. Neither does repacling char by
signed char.
moused is broken too. It assumes that plain chars are signed.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: don't know how to make buildincludes in buildworld from -stableto -current
On Thu, 2002-05-16 at 05:42, Hans Lambermont wrote: Is anyone else able to upgrade from stable to current ? I'm running current, and I'm experiencing the same problem you are. -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 2L, UST School of Law Minneapolis, Minnesota I am a nobody, and nobody is perfect; therefore, I am perfect. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pqv @mBGRx
¿¬¾Ö¶õ ³²ÀÚ°¡ ´Ü ÇÑ »ç¶÷ÀÇ ¿©ÀÚ¿¡ ¸¸Á·Çϱâ À§ÇØ Ä¡·ç´Â ³ë·ÂÀÌ´Ù. -Ç® Á¦¶ó¸£µð
±¸Çؼ ¾òÀº »ç¶ûÀº ÁÁÀº °ÍÀÌ´Ù. ±×·¯³ª ±¸ÇÏÁö ¾Ê°í ¾òÀº °ÍÀº ´õ¿í ÁÁ´Ù. -¼ÎÀͽºÇǾî
»ç¶ûÇÏ´Â °ÍÀÌ ÀλýÀÌ´Ù. ±â»ÝÀÌ ÀÖ´Â °÷¿¡ »ç¶÷°ú »ç¶÷ »çÀÌÀÇ °áÇÕÀÌ
¹ÞÀ¸½Ã´Â ºÐ²² ÇÊ¿äÇÑ Á¤º¸°¡ µÇ±æ ¹Ù¶ó¸ç º¸³»µå¸³´Ï´Ù.
±×·¸Áö ¾ÊÀº°æ¿ì¶ó¸é Áø½ÉÀ¸·Î »çÁ˵帳´Ï´Ù.
ÇÁ·Î±×·¥ ŸÀÌƲ 2100¿©Àå°ú µ¿¿µ»ó ŸÀÌƲ 500¿©ÆíµîÀÇ
ÀÎÅÍ³Ý ÃÖ´ÙÀÇ Á¦Ç°µéÀ» ÁÖ¹®¹Þ¾Æ¼ º¸³»µå¸®°í ÀÖ½À´Ï´Ù.
ÄÄÇ»Å͸¦ ¾²½Ã´ÂÇÑ ¾ðÁ¨°£ ÇÊ¿äÇϽÇÅ×´Ï ÀúÀåÇϼż
ÀÌ¿ëÇϽøé Æí¸®ÇϽʴϴÙ.
. Á¦Å¸ÀÌƲµéÀº ´ëºÎºÐ ¼ö½Ê¸¸¿ø¿¡¼ ¼öõ¸¸¿ø¾¿ÇÏ´Â Á¦Ç°µéÀÔ´Ï´Ù.
. ÀÎÅÍ³Ý Ãִ٠ŸÀÌƲÀ» º¸À¯ÇÏ°í ÀÖ½À´Ï´Ù.
. ¿Ïº®ÇÑ Å©·¢/ÆÐÄ¡µéÀ» º¸À¯ÇÏ°í ÀÖ½À´Ï´Ù.
Á¦°¡ Ãë±ÞÇÏ´Â
¼ÒÇÁÆ®¿þ¾î´Â ÃÖ½ÅÀÇ Ç®¹öÀüÀ̸ç
1 0 0 % ½ÇÇàÅ×½ºÆ®¸¦ ¸¶Ä£ Á¦Ç°µéÀÔ´Ï´Ù.
Åë½Å»ó¿¡¼ °¡Àå ¾çÁúÀÇ Á¦Ç°À̶ó ÀÚºÎÇÕ´Ï´Ù.
µ¿¿µ»óÀº ¼ºÀοëÀ̹ǷΠ¹Ì¼º³â²²´Â ÆǸÅÄ¡ ¾Ê½À´Ï´Ù.
¹°·Ð AS µµ ÃæºÐÈ÷ Áö¿øµÇ°í ÀÖ½À´Ï´Ù.
**¾ðÁ¦³ª ÃÖ½ÅÁ¦Ç°ÀÇ ¸ñ·Ï µéÀÌ ÇÊ¿äÇϽôٸé
ÀüÈÁֽøé Á¦ ¸ÞÀΠȨÆäÀÌÁö¸¦ ¾È³»ÇØ µå¸®°Ú½À´Ï´Ù.**
¾Æ¸¶ ãÀ¸½Ã´Â Á¦Ç°Àº °ÅÀÇ ´Ù ÀÖÀ»°Ì´Ï´Ù.
¾ø´õ¶óµµ ¹®ÀÇÁÖ½Ã¸é ±¸Çص帳´Ï´Ù.
---
-A/S¾È³»-
Å×½ºÆ®¸¦ ¸¶Ä£ Á¦Ç°µéÀ̱⠶§¹®¿¡ º°´Ù¸¥ A/S »çÇ×Àº ¾øÀ»
°ÍÀÔ´Ï´Ù. ¹°·Ð ¾î¶² °æ¿ì¶óµµ ¿Ïº®ÇÑ A/S ¸¦ º¸ÀåÇØ µå¸³´Ï´Ù.
¹®Á¦°¡ ¹ß»ýÇÒ °æ¿ì´Â '¹Ýµå½Ã' ¿¬¶ôÁֽʽÿÀ
²À! ÇØ°áÇØ µå¸³´Ï´Ù.
±âŸ¾÷ÀÚ¿¡°Ô¼ ½ÇÇà ¾ÈµÇ´Â Á¦Ç°À» ±¸ÀÔÇغ¸½Å ºÐµéÀ̳ª,
¼³Ä¡¹æ¹ý ¹°¾îº¸¸é ÀüȲ÷¾î¹ö¸®´Â^^ ¾÷ÀÚ³ª
È£Ãâ±â·Î ÁÖ¹®¹Þ´Â ¾÷ÀÚ¿¡°Ô¼ »ç±â´çÇϼż
¿¬¶ôµµ ¸øÇغ¸½Ã°í ¹ß¸¸ µ¿µ¿±¼·¯º¸½Å ºÐµé,
ºñ½Ñ°ªÁÖ°í ±¸ÀÔÇÑ°ÍÀÌ °Ü¿ì ¸³¹öÀüÀ̳ª ¼¼¾î¿þ¾î¿´´ø ºÐµé,
ÀÌÁ¦ ´ä´äÇÑ ¸¶À½À» ¹ö¸®½Ã°í Àú¿Í »óÀÇÇϽʽÿÀ
===
===[ ÀÌ¿ë¾È³» ]==
===
ÇÊ¿äÇÑ °ÍÀÌ ÀÖ´Ù¸é ¾Æ·¡¸¦ ÂüÁ¶ÇÏ¿© ÀüÈ·Î ÁÖ¹®ÁֽøéµË´Ï´Ù.
! . ¸ÞÀϷδ ÁÖ¹®¹ÞÁö ¾Ê½À´Ï´Ù . !
! . º¸³»µå¸° ¸ÞÀÏÁּҷδ ÁÖ¹®Áּŵµ Á¦°¡ ¹ÞÁö¸¦ ¸øÇÕ´Ï´Ù . !
-ÁÖ ¹® ¹æ ¹ý-
ÀüÈÁÖ½ÅÈÄ ¹°°ÇÀÇ ¹øÈ£¿Í ¹ÞÀ¸½Ã´ÂºÐÀÇ ÁÖ¼Ò¿Í ¼ºÇÔ,¿¬¶ôó
ÀÔ±ÝÇϽôºÐÀÇ ¼ºÇÔÀ» ¸»¾¸ÁÖ½ÅÈÄ ÀúÈñ°¡ ¾Ë·Áµå¸®´Â
°èÁ·ΠÀÔ±ÝÇϽøé , È®ÀÎÈÄ ¹ß¼ÛÇÕ´Ï´Ù.
ÈÞÀÏÀº ½±´Ï´Ù.. ÀºÇ൵ ¹è´ÞºÎµµ ½¬°Åµç¿ä..
-ÀԱݽà ȮÀλçÇ×-
Á¦°èÁ°¡ ÃàÇùÀÌ ³óÇùÀ¸·Î º¯ÇÑ°ÍÀÌ¶ó¼ ³óÇùÀÌ ¾Æ´Ñ ŸÇàÀԱݽÿ¡
Á¦ °èÁ¹øÈ£¸¸ ³ª¿À°í Á¦À̸§ÀÌ È¸é¿¡ ¾È ¶ß´Â °æ¿ì°¡ ÀÖÀ¾´Ï´Ù.
ÀÌ°æ¿ì °èÁ¹øÈ£¸¸ ÀÏÄ¡Çϸé ÀÔ±ÝÇϽøé Á¦°Ô·Î Á¤È®È÷
ÀÔ±Ý µË´Ï´Ù. (³óÇù¿¡¼ ÀÔ±ÝÇϽô °æ¿ì´Â »ó°üÀÌ ¾ø½À´Ï´Ù.)
-ÁÖ ¹® Àü È ¹ø È£-
ÇÚµåÆù : 0 ¢Ã 1 ¢Ã 1 - 9 ¢Ã 0 ¢Ã 2 ¢Ã 2 - 0 ¢Ã 6 ¢Ã 2 ¢Ã 1
ÇÚµåÆù : 0 ¢Ã 1 ¢Ã 1 - 9 ¢Ã 0 ¢Ã 2 ¢Ã 2 - 0 ¢Ã 6 ¢Ã 2 ¢Ã 1
-¿µ ¾÷ ½Ã °£-
¿ÀÀü 10½ÃºÎÅÍ ¿ÀÈÄ 6½Ã±îÁö. (°¡²û7½Ã±îÁöµµ ÄÕ´Ï´Ù)
°£È¤ ²¨Á®Àִ°æ¿ì 1½Ã°£ÈÄ ¿¬¶ôÁֽðųª ÀüȹøÈ£¸¦ ³²°ÜÁÖ¼¼¿ä.
1½Ã°£ À̳»·Î ¿¬¶ôµå¸®°Ú½À´Ï´Ù.
(Àú³áÀÏ°æ¿ì ÀÍÀÏ¿ÀÀü¿¡ ²À ¿¬¶ôµå¸³´Ï´Ù)
-¼Ò ¿ä ½Ã °£-
´ëºÎºÐ ÀÔ±ÝÇϽŠ´ÙÀ½³¯ ¹ÞÀ¸½Ê´Ï´Ù. (24½Ã°£À̳»)
-°¡ °Ý-
°¡°ÝÀº º°µµ Ç¥½ÃµÈ Á¦Ç°À» Á¦¿ÜÇÏ°í´Â ¸ðµÎ 1¸¸ 5õ¿øÀ¸·Î °è»ê
ÇÏ½Ã¸é µË´Ï´Ù.
Åùèºñ´Â 5õ¿øº°µµ . (5¸¸¿øÀÌ»ó½Ã Åùèºñ¹«·á)
(ÇѲ¨¹ø¿¡ 5Àå ±¸ÀԽà ¾ßµ¿1Àå ´õ ¼±Åð¡´É!)
-¸ñ·Ï±¸¼º¾È³»-
´ÙÀ½°ú °°Àº ¼ø¼·Î ±¸¼ºµÇ¾îÀÖ½À´Ï´Ù.
=
1 - * ÃֽŠ¾÷µ¥ÀÌÆ® ¸®½ºÆ® * -ÃÖ±Ù ¾÷µÈ ºÎºÐÀÔ´Ï´Ù.
2 - * ¸ÞÀθ®½ºÆ® * - Á¦ ¸®½ºÆ®ÀÇ Àüü¸ñ·ÏÀÔ´Ï´Ù.
Àüü¸ñ·ÏÀº ´ÙÀ½°ú °°Àº ¼ø¼·Î ±¸¼ºµÇ¾îÀÖ½À´Ï´Ù.
O - ¿î¿µÃ¼Á¦,Norton(¹ÙÀÌ·¯½º...)
W - »ç¹«¿ë ¿ÀÇǽº,¿öµå,ÀüÀÚÃâÆÇ,¹®ÀÚÀνÄ(OCR)
N - ³×Æ®¿öÅ©,DB°ü·Ã
L - ·©±ÍÁö,ÇÁ·Î±×·¡¹Ö Åø
C - ijµå.°ÇÃà.±â°è¼³°è.ÀüÀÚ.GIS°ü·Ã
S - ¼öÇÐ,Åë°è°ü·Ã
G - ±×·¡ÇÈ °ü·Ã(¸Æ½º,Æ÷Åä¼¥,ÇÁ¸®¹Ì¾îµî,,,)
T - ¸ÖƼ¹Ìµð¾î,À¥,ȨÆäÀÌÁö,Photo¾Ù¹üÁ¦ÀÛ
J - ±âŸ(À½¾Ç,·¹ÄÚµù,ÇØÅ·,µîµî)
E - ÇнÀ,±³À°¿ë(¹é°ú,¹ø¿ª,¹ÙµÏ,ƯÈ÷ »ó¾÷¿ëµµ)
D - ÀÇÇаü·Ã
X - Çѱ¹ÀÇ ¼ºÀο뵿¿µ»ó (¹é¾ç, ÁøÁÖÈñ µî)
Y - ÀϺ»ÀÇ ¼ºÀÎ¿ë µ¿¿µ»ó ( °¡Á¤±³»ç µî)
Z - ¼¾çÀÇ ¼ºÀÎ¿ë µ¿¿µ»ó (¹é¼³°øÁÖ µî..)
R- ·Î¸®Å¸ ¹× ±âŸ ¿±±âµ¿¿µ»ó ¸ðÀ½...
**¿ë·®°ü°è·Î Àüü ŸÀÌƲÀÇ ÇÑ ¼³¸íÀ» ½ÆÁö ¸øÇÑÁ¡
¾çÇØ ¹Ù¶ø´Ï´Ù. Á¦°¡°¡Áø ŸÀÌƲÀÇ ´ëºÎºÐÀÇ Á¦¸ñÀ» ½Ç¾úÀ¾´Ï´Ù.
¿ì¼± Á¦¸ñÀ¸·Î ã¾Æº¸½Ã°í, ÇÑ ¼³¸íÀÌ ÇÊ¿äÇϽźеéÀº
Á¦ ÀÓ½ÃȨÆäÀÌÁö¸¦ ¹æ¹®Çϼż È®ÀÎÇÏ½Ã¸é µË´Ï´Ù.**
Àӽà ȨÆäÀÌÁö´Â
http://rH3Fh1.dA.rU
http://rH3Fh1.cE.rO
http://rH3Fh1.kA.kY
ÀÔ´Ï´Ù.
ÀÓ½ÃȨÆäÀÌÁö Àå¾Ö½Ã ÀüÈÁÖ½Ã¸é ¸ÞÀÎȨÆäÀÌÁö¸¦ ¾Ë·Áµå¸³´Ï´Ù.
ÀüÈ»óÀ¸·Î ÇÊ¿äÇÏ½Å°É Á÷Á¢ ¹®ÀÇÇϼŵµ µË´Ï´Ù.
5¿ù ¾÷µ¥ÀÌÆ® ¸®½ºÆ®
* ¸ÞÀθ®½ºÆ®´Â ¾÷¸®½ºÆ®ÀÇ ´ÙÀ½¿¡ À̾îÁý´Ï´Ù.
¿î¿µÃ¼Á¦,À¯Æ¿ ¾÷µ¥ÀÌÆ® ==
O-009¹Ù¢Ã MS Windows 2000 Datacenter Server -2¸¸¿ø
- À©µµ¿ì 2000 °è¿ÀÔ´Ï´Ù.
O-011¶ó¢Ã MS Windows XP Home Edition(ÇÑ) -2¸¸¿ø
È®½ÇÈ÷ Ȩ¿¡µð¼Ç ÀÔ´Ï´Ù-½ÃÀÛȸ鿡¼ºÎÅÍ ´Ù¸§!
Re: moused(8): char signed-ness problem with gcc 3.1
I've submitted a bug report to GCC GNATS: http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gccpr=6677cmd=view+audit-trail Let's see how they handle this. -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp Somewhere out of a memory.. of lighted streets on quiet nights.. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tmp/des/obj/alpha/d/home/des/tinderbox/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === share/examples/ipfilter === share/man === share/man/man1 === share/man/man3 === share/man/man4 === share/man/man4/man4.alpha === share/man/man5 === share/man/man6 === share/man/man7 make: don't know how to make style.perl.7. Stop *** Error code 2 Stop in /d/home/des/tinderbox/src/share/man. *** Error code 1 Stop in /d/home/des/tinderbox/src/share. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
On Thu, May 16, 2002 at 08:31:19PM +0900, Akinori MUSHA wrote:
So - yes - it seems gcc 3.1 does have a problem...
Indeed - easily determined by breaking down the expression.
So, who's gonna report it to gcc-bugs? knu?...
Specifically what is the problem? Given the program below, take the
ISO-C spec and explain the problem. Or even w/o the spec -- I haven't
been reading this thread.
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
j = ((char)(i 1)) / 2;
printf(%d\n, j);
j = ((char)(i 1));
printf(%d\n, j / 2);
return 0;
}
Somehow, specifying -fsigned-char, which I thought was the default,
fixed the problem. So, the cause may be in our configuration of gcc?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
Specifically what is the problem? Given the program below, take the
ISO-C spec and explain the problem. Or even w/o the spec -- I haven't
been reading this thread.
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
This prints -2, which is correct -- (signed char)254 is -2.
j = ((char)(i 1)) / 2;
printf(%d\n, j);
This prints 127, which is incorrect. -2 / 2 is -1.
j = ((char)(i 1));
printf(%d\n, j / 2);
This breaks down the previous expression into two halves, and
results in the correct answer of -1. However, there should
be no difference between
((char)(i 1)) / 2
and
char j = ((char)(i 1); j / 2
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
On Thu, May 16, 2002 at 12:06:49PM -0700, Bill Fenner wrote:
Specifically what is the problem? Given the program below, take the
ISO-C spec and explain the problem. Or even w/o the spec -- I haven't
been reading this thread.
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
This prints -2, which is correct -- (signed char)254 is -2.
j = ((char)(i 1)) / 2;
printf(%d\n, j);
This prints 127, which is incorrect. -2 / 2 is -1.
j = ((char)(i 1));
printf(%d\n, j / 2);
This breaks down the previous expression into two halves, and
results in the correct answer of -1. However, there should
be no difference between
((char)(i 1)) / 2
and
char j = ((char)(i 1); j / 2
Sounds like you should forward this to [EMAIL PROTECTED] :-)
CC audit@ (and current@) so we can all see what the GNU people say.
Don't forget to show the output of `cc -v'.
Or run `gccbug' from a recient gcc31 port install. If you do this
instead, please send me the PR #.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: /usr/ports/emulators/bochs on -CURRENT
On Thu, May 16, 2002 at 01:14:01PM -0400, Mike Barcroft wrote: Riccardo Torrini [EMAIL PROTECTED] writes: # cd /usr/ports/emulators/bochs make [...] gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include -I.. -I./.. -I../instrument/stubs -I./../instrument/stubs cdrom.cc -o cdrom.o In file included from cdrom.cc:40: /usr/include/arpa/inet.h:102: conflicting types for `typedef __uint32_t socklen_t' ../osdep.h:105: previous declaration as `typedef int socklen_t' gmake[1]: *** [cdrom.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' gmake: *** [iodev/libiodev.a] Error 2 *** Error code 2 The problem appears to be that osdep.h is defining types it should not be defining. Software should include system headers to get new types, not try and out-smart the OS by defining its own (possibly incorrect) types. There is a patch in gnats to fix this error, but it still has errors, pat@ is currently looking at this and I'm building patches for him since I have a -current machine Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Skipping certain buildworld stages (was: Re: make includes)
On Thu, May 16, 2002 at 09:07:25AM +0300, Ruslan Ermilov wrote:
it's possible to achieve this with:
: make \
: -DNO_worldtmp -DNO_bootstrap-tools -DNO_cleanobj -DNO_obj \
: -DNO_build-tools -DNO_cross-tools \
: buildworld TARGET_ARCH=foo
Which in essence is equivalent to this sh(1) script:
: cd /whatever/usr/src
: for target in _includes _libraries _depend everything; do
: make -m `pwd`/share/mk -f Makefile.inc1 \
: ${target} TARGET_ARCH=foo
: done
Thanks!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Problem with Intel 2011b
Warner == Warner Losh [EMAIL PROTECTED] writes: Warner H, I've found that the Intel PRO/Wireless are 5.0V devices. Warner Maybe this is a different card than what I'm used to dealing Warner with. From the reseller, this is the main difference beetween 2011 2011b (chipset difference too, but no specs available atm) Warner Looks like i82365A/B do not have 3.3V support at all. I can't Warner find the data sheets for them, and the people that do have Warner access tell me that this is correct. Seems to, the 2011b can't physically plug into the slot on the Satellite. Warner I'm not sure why your thinkpad isn't working. Maybe it is an Warner issue related to the COR reset proceedure that we're not doing Warner anymore. Is there anything I can do to confirm/infirm this fact ? (cvs revision to extract ?) Eric Masson -- FYLG Tiens, vlà une URL qui va bien : FYLG ftp://127.0.0.1/WaReZ/NiouZeS/WinDoZe/NeWSMoNGeR/SuPeR c'est gentil sauf que l'adresse ne fonctionne pas sa me fais une erreur -+- Furtif in Guide du Neuneu Usenet : MODE CERVEAU OFF -+- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: moused(8): char signed-ness problem with gcc 3.1
On Thu, May 16, 2002 at 06:47:39AM -0400, Thomas David Rivers wrote: Terry Lambert [EMAIL PROTECTED] wrote: RS/6000's didn't used to use PPC processors at all; so it's probably intentional software compatability. I'm confused then - the one we have here seems to. There was a version of something very RS/6000-like that didn't, but I thought RS/6000s did... RS/6000s used to use Power before there was PowerPC. I'm doubting there is much difference between the two from a software point of view. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
__FreeBSD_version bump for loss of perl
Could we have a __FreeBSD_version bump for the diking out of perl from the base system please? A chunk of ports work needs to be done to conditionally use perl vs sed for in-line replacements on lots of Makefiles. Thanks, -aDe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
Ade Lovett wrote: Could we have a __FreeBSD_version bump for the diking out of perl from the base system please? A chunk of ports work needs to be done to conditionally use perl vs sed for in-line replacements on lots of Makefiles. I agree that a __FreeBSD_version bump is appropriate, but why not always simply use sed for this ? Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
On 05/16/02 17:46, Maxime Henrion [EMAIL PROTECTED] wrote:
I agree that a __FreeBSD_version bump is appropriate, but why not always
simply use sed for this ?
Because not everyone using the ports system has the in-place editing feature
of sed that was recently added, and thus it needs to be conditional on
${OSVERSION}.
-aDe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
On Thu, May 16, 2002 at 05:52:45PM -0500, Ade Lovett wrote:
On 05/16/02 17:46, Maxime Henrion [EMAIL PROTECTED] wrote:
I agree that a __FreeBSD_version bump is appropriate, but why not always
simply use sed for this ?
Because not everyone using the ports system has the in-place editing feature
of sed that was recently added, and thus it needs to be conditional on
${OSVERSION}.
Nor maybe do we want to use them. If I want to add Perl as a build
depends, that is my perorative as a maintainer.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
Ade == Ade Lovett [EMAIL PROTECTED] writes:
Ade Because not everyone using the ports system has the in-place
Ade editing feature of sed that was recently added, and thus it
Ade needs to be conditional on ${OSVERSION}.
Why can't we use ed for in-place edits?
--lyndon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: [PATCH] cross-arch bootstrapping is broken by GCC 3.1
On Wed, May 15, 2002 at 09:31:11AM +0300, Ruslan Ermilov wrote: This actually doesn't affect only cross-arch case, the subject is wrong. It affects any arch with HOST_BITS_PER_WIDE_INT HOST_BITS_PER_LONG e.g. alpha. This *is* only a cross issue. HOST_BITS_PER_WIDE_INT == HOST_BITS_PER_LONG on Alpha. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: ALTQ integration developer preview
We have started a ALTQ integration in FreeBSD project which is headed towards integrating Mr. Kejiro's ALTQ framework into FreeBSD 5.0-current (and perhaps 4-stable later). The FreeBSD Core Team has been advised and we have received on principle approval. We are looking for help with committing these bits to the CVS tree. Please have a look at the proposed ALTQ package for 5.0-current, which is found here: http://www.rofug.ro/projects/freebsd-altq/altq-freebsd-5.0-current-May14.tar.gz Installation details are found in the README file; for further details consult the documentation referenced below. Please send us any comments you have, your feedback is valuable. ALTQ integration implies some changes in the network drivers code and in the design of the the network queues management. Here is a summary of the ALTQ design document: The BSD systems need better output queueing abstraction to support packet scheduling (e.g., CBQ) or active queue management (e.g., RED). To introduce a new model, we need to convert the existing code to be conformant to the new model. But the problem is that there are too many drivers to convert all at once. This is a proposal that allows incremental transition to the new model. (If we are going to modify the existing drivers, we need to get it right.) The model is designed for ALTQ but it is general enough for other implementations so that we can make the driver conversion once and for all. The new model removes direct references to the fields within ifp-if_snd, and defines the following macros to manipulate ifp-if_snd: IFQ_ENQUEUE(ifq, m, err) IFQ_DEQUEUE(ifq, m) IFQ_POLL(ifq, m) IFQ_PURGE(ifq) IFQ_IS_EMPTY(ifq) The new model also enforces some rules regarding how to use these macros. Another requirement for a driver is to work under rate-limiting. - IFQ_DEQUEUE() could return NULL even when IFQ_IS_EMPTY() is FALSE under rate-limiting. a driver should always check if (m == NULL). - a driver is supposed to call if_start from the tx complete interrupt under late-limiting (in order to trigger the next dequeue). For most drivers, it is a simple task of replacing old-style lines by the corresponding new-style lines, and usually just a few lines need to be modified. But some drivers need more than that. The old-style drivers still work with the original FIFO queue but they cannot take advantage of new queueing disciplines. For locking an output queue to support SMP, ALTQ uses the same model as in FreeBSD-5.0. One restriction is that, if a driver uses poll-and-dequeue, the driver needs to explicitly lock the queue between the poll operation and the dequeue operation. You can find more details here: http://www.csl.sony.co.jp/person/kjc/kjc/software/altq-new-design.txt http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ Current development is headed by Kenjiro Cho and myself. If you want to join our efforts please subscribe to our mailing list by sending subscribe in the body of a message to [EMAIL PROTECTED] Adrian Penisoara Ady (@freebsd.ady.ro, @rofug.ro) ___ | Programming in BASIC causes brain damage. | | (Edsger Wybe Dijkstra)| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
[bogus From: address, because people cannot be bothered to respect Reply-To:]
On Thu, May 16, 2002 at 06:17:44PM -0600, Lyndon Nerenberg wrote:
Why can't we use ed for in-place edits?
perl -pi.hold -e 's/FOO/BAR/g' ${WRKSRC}/a/b/{X,Y}
is not as easy to do with `ed'.
People should find something else to worry about.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
perl -pi.hold -e 's/FOO/BAR/g' ${WRKSRC}/a/b/{X,Y}
is not as easy to do with `ed'.
It's not *that* hard. 10 lines of shell script is preferable to
XX MB of perl bloat. Especially for this sort of problem.
--lyndon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: __FreeBSD_version bump for loss of perl
On Thu, May 16, 2002 at 06:17:44PM -0600, Lyndon Nerenberg wrote:
Ade == Ade Lovett [EMAIL PROTECTED] writes:
Ade Because not everyone using the ports system has the in-place
Ade editing feature of sed that was recently added, and thus it
Ade needs to be conditional on ${OSVERSION}.
Why can't we use ed for in-place edits?
Someone just bump the __FreeBSD_version, please. It costs nothing,
and it's a landmark event by any definition.
Kris
msg38450/pgp0.pgp
Description: PGP signature
