Progress report: Multilingual sysinstall for -current
Hi! I've ported Multilingual sysinstall to -current. I put the latest source and binaries (Japanese/Englush only) is at http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ (please note that non-English docuemnt files are based on 4.2-RELEASE) Currently, this implementation supports Japanese, Korean, Traditional Chinese, and Russian. The status of translation work is: Japanese: finished Korean: finished Traditional Chinese:about to finish Russian:only *.hlp files have been translated This code has some minor problems, but it works. I think it's better to change the development of this project to open style. I would like to import this code to -current CVS repositry soon if there's no objections. FYI: for 4.2-RELEASE, http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ contains source, and binaries for all supported languages. -- 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: Progress report: Multilingual sysinstall for -current
On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | I've ported Multilingual sysinstall to -current. I put the latest | source and binaries (Japanese/Englush only) is at | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | (please note that non-English docuemnt files are based on 4.2-RELEASE) | | Currently, this implementation supports Japanese, Korean, Traditional | Chinese, and Russian. The status of translation work is: | | Japanese: finished | Korean: finished | Traditional Chinese: about to finish | Russian: only *.hlp files have been translated | | This code has some minor problems, but it works. I think it's better | to change the development of this project to open style. I would like | to import this code to -current CVS repositry soon if there's no | objections. As we wait for libh development, I do not think we should exert efforts to try for another solution. This tends to allow for slack in further development of better products. A good example would be a proposal by Alfred Pernstein to slightly modify RELENG_4 SMP for the duration of SMPNG development. The proposal was not well accepted due to the reason I stated above. We really should concentrate on libh as a complete and _clean_ solution. In addition, the purpose of putting localized sysinstall in -CURRENT is rather dubious. -CURRENT/HEAD is a developers' branch, people who use this branch should be able to read English and the system error messages. If they cannot install the system with English sysinstall, I would have doubts on their programming and testing ability. People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. I would have no objections to L10N'ized sysinstall being maintained in the same way that PAO is maintained. The boot floppies and iso images can be put up somewhere for download, and maintained in RELENG_4. Normally, I would welcome any I18N/L10N efforts in FreeBSD. However, the FreeBSD Project's official position paraphrased is "If you don't know what to do with -CURRENT, don't install it." Combined with the point that we should not divert efforts from libh, I hold the opinion that we should not import this. Finally, still many thanks and applause to Tatsumi and others for this work. | FYI: for 4.2-RELEASE, | http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ | contains source, and binaries for all supported languages. -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
* Michael C . Wu [EMAIL PROTECTED] [001206 01:46] wrote: On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | I've ported Multilingual sysinstall to -current. I put the latest | source and binaries (Japanese/Englush only) is at | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | (please note that non-English docuemnt files are based on 4.2-RELEASE) | | Currently, this implementation supports Japanese, Korean, Traditional | Chinese, and Russian. The status of translation work is: | | Japanese: finished | Korean: finished | Traditional Chinese: about to finish | Russian: only *.hlp files have been translated | | This code has some minor problems, but it works. I think it's better | to change the development of this project to open style. I would like | to import this code to -current CVS repositry soon if there's no | objections. As we wait for libh development, I do not think we should exert efforts to try for another solution. This tends to allow for slack in further development of better products. No, this motivates those working for a greater good to produce more than just promises of what's to come. A good example would be a proposal by Alfred Pernstein to slightly modify RELENG_4 SMP for the duration of SMPNG development. The proposal was not well accepted due to the reason I stated above. The proposal was only rejected as something that wasn't going to be the be all and end all of our threading system. As a middle ground it would have many advantages over what's currently in place. The same applies here. Sure libh is supposed to be an order of magnitude better than internationalized sysinstall, but at the current time libh is as much vapourware as KSEs are. We really should concentrate on libh as a complete and _clean_ solution. Yes, and no, you should continue doing so, and I have high hopes that it's the best installer system ever, however an interm solution would be a great way to attract new users and developers. In addition, the purpose of putting localized sysinstall in -CURRENT is rather dubious. -CURRENT/HEAD is a developers' branch, people who use this branch should be able to read English and the system error messages. If they cannot install the system with English sysinstall, I would have doubts on their programming and testing ability. People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. Why? It's my native tongue and even I have issues on occasion with comments and manpage additions that forieners correct (Bruce, Eivind, Asmodai and Sheldon to name a few.) Having a problem with english doesn't make anyone less of an intellectual. I would have no objections to L10N'ized sysinstall being maintained in the same way that PAO is maintained. The boot floppies and iso images can be put up somewhere for download, and maintained in RELENG_4. Maybe after libh is released... since you guys aren't basing your work on sysinstall, it's not like you'd have to deal with a code merger. Normally, I would welcome any I18N/L10N efforts in FreeBSD. However, the FreeBSD Project's official position paraphrased is "If you don't know what to do with -CURRENT, don't install it." Combined with the point that we should not divert efforts from libh, I hold the opinion that we should not import this. I think it should be brought in and quickly MFC'd for the next 4.3 release. I see no conflict between these two efforts and since one seems pretty much completed, I'd like to see it in the base system. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
On Wed, Dec 06, 2000 at 02:30:21AM -0800, Alfred Perlstein scribbled: | * Michael C . Wu [EMAIL PROTECTED] [001206 01:46] wrote: | On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | | I've ported Multilingual sysinstall to -current. I put the latest | | source and binaries (Japanese/Englush only) is at | | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | | (please note that non-English docuemnt files are based on 4.2-RELEASE) | | | | Currently, this implementation supports Japanese, Korean, Traditional | | Chinese, and Russian. The status of translation work is: | | | | Japanese: finished | | Korean: finished | | Traditional Chinese: about to finish | | Russian: only *.hlp files have been translated | | | | This code has some minor problems, but it works. I think it's better | | to change the development of this project to open style. I would like | | to import this code to -current CVS repositry soon if there's no | | objections. | | As we wait for libh development, I do not think we should exert | efforts to try for another solution. This tends to allow for | slack in further development of better products. | | No, this motivates those working for a greater good to produce | more than just promises of what's to come. [snip] | People who run -CURRENT should be able to read and write English to | understand the code comments, report bugs, and post to the lists in English. | | Why? It's my native tongue and even I have issues on occasion with | comments and manpage additions that forieners correct (Bruce, Eivind, | Asmodai and Sheldon to name a few.) Having a problem with english | doesn't make anyone less of an intellectual. | | I would have no objections to L10N'ized sysinstall being maintained in | the same way that PAO is maintained. The boot floppies and iso images | can be put up somewhere for download, and maintained in RELENG_4. | | Maybe after libh is released... since you guys aren't basing your | work on sysinstall, it's not like you'd have to deal with a code | merger. | This is not about a code merge, this is about how we will support users who use this stuff. If we want to do this, we need to have a centralized support system/mailing lists, instead of the currently very segmented local support systems. I would have no objections if we can figure out a way to support this in a bug reporting system, mailing lists. But I agree you are right, we could use this in 4.x. Perhaps I did not think this one thoroughly. | I think it should be brought in and quickly MFC'd for the next | 4.3 release. | | I see no conflict between these two efforts and since one seems | pretty much completed, I'd like to see it in the base system. -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
As we wait for libh development, I do not think we should exert efforts to try for another solution. This tends to allow for slack in further development of better products. A good example would be a proposal by Alfred Pernstein to slightly modify RELENG_4 SMP for the duration of SMPNG development. The proposal was not well accepted due to the reason I stated above. We really should concentrate on libh as a complete and _clean_ solution. Sure, libh is a better solution. But, don't you think it's still good to have something working until it will become available. In addition, the purpose of putting localized sysinstall in -CURRENT is rather dubious. -CURRENT/HEAD is a developers' branch, people who use this branch should be able to read English and the system error messages. If they cannot install the system with English sysinstall, I would have doubts on their programming and testing ability. People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. I think you are missing the point here. As you point out, the -current is for developers; it's for development and for testing. I don't think Tatsumi wants -current users to use I18N sysinstall to install -current, but, rather wants them to have a look at the code and test it. I would have no objections to L10N'ized sysinstall being maintained in the same way that PAO is maintained. The boot floppies and iso images can be put up somewhere for download, and maintained in RELENG_4. Why should it be in RELENG_4? If it's maintained in -current and regularly MFCed to RELENG_4, it is exposed to wide audience of -current developers and -stable users. That will attract more comments and bug reports, and will also minimize the delay between regular releases of FreeBSD and I18N/L10N sysinstall for them; the delay normally associated with L10N sysinstall (and PAO) after regular FreeBSD releases. Normally, I would welcome any I18N/L10N efforts in FreeBSD. However, the FreeBSD Project's official position paraphrased is "If you don't know what to do with -CURRENT, don't install it." See my comments above. Combined with the point that we should not divert efforts from libh, I hold the opinion that we should not import this. I don't think importing multilingual sysinstall will detract effort from libh. You see, even if it is maintained separately from the -current, it has its own maintainers and developers. I expect they are the same people who will maintain and develop I18N sysinstall when it is imported to the -current. They may or may not be libh developers at the same time. But, I don't think I18N sysinstall is suddenly needing a large army of developers and will steal them from the libh developer base. Finally, still many thanks and applause to Tatsumi and others for this work. The same from me to them too. Kazu | FYI: for 4.2-RELEASE, | http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001205-1/ | contains source, and binaries for all supported languages. -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems in making world
Hi! On Tue, 5 Dec 2000, David O'Brien wrote: On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote: I have a following problem in making world for some time already: ... Any suggestions? rm -rf /usr/obj/* cd /usr/src make cleandir update your /usr/src and try again Yes, that helped, thank You. I did the 'rm -rf /usr/obj/*' several times, but didn't 'make cleandir'... And I'm cvsup'ing automatically once a day, so that wasn't a problem ;) Adios, /KONG Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATM broken in -current
Hi,
the ATM stuff in /sys/dev/h{e,f}a and /sys/netatm seems to be seriously
broken in current. A simple 'atm show config' command leads to a kernel
panic. I have tracked down the problem (and had to learn, that bzero is a
function pointer rather than a function on i386).
I cannot track, how the problem was introduced, but it appears to be
somehow connected to phk's header file reorganisation in the ATM code in
october. Many of the files miss a sys/systm.h include and give a missing
prototyp warning for functions like splnet, printf, log, bzero...
This appears to be deadly for bzero(), because this is a function pointer
now. (I always had the fealing, that the ANSI-C syntax for calling
functions through pointers is bad ( fooptr() instead of (*fooptr)()).
Now I know why :-( ) Adding a #include sys/systm.h to the following
files seem to fix the problem:
dev/hea/eni_intr.c
dev/hea/eni_vcm.c
netatm/atm_if.c
netatm/atm_signal.c
netatm/atm_socket.c
netatm/atm_usrreq.c
netatm/ipatm/ipatm_event.c
netatm/ipatm/ipatm_if.c
netatm/ipatm/ipatm_load.c
netatm/ipatm/ipatm_output.c
netatm/ipatm/ipatm_vcm.c
netatm/spans/spans_cls.c
netatm/spans/spans_subr.c
netatm/uni/sscf_uni.c
netatm/uni/sscf_uni_lower.c
netatm/uni/sscf_uni_upper.c
netatm/uni/sscop.c
netatm/uni/sscop_lower.c
netatm/uni/sscop_subr.c
netatm/uni/sscop_upper.c
netatm/uni/uni_load.c
netatm/uni/uniarp_input.c
netatm/uni/uniarp_output.c
netatm/uni/uniarp_vcm.c
netatm/uni/unisig_encode.c
netatm/uni/unisig_mbuf.c
netatm/uni/unisig_msg.c
netatm/uni/unisig_print.c
netatm/uni/unisig_proto.c
netatm/uni/unisig_sigmgr_state.c
Regards,
harti
--
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
At Wed, 06 Dec 2000 20:25:30 +0900, Kazutaka YOKOTA [EMAIL PROTECTED] wrote: As we wait for libh development, I do not think we should exert efforts to try for another solution. This tends to allow for slack in further development of better products. A good example would be a proposal by Alfred Pernstein to slightly modify RELENG_4 SMP for the duration of SMPNG development. The proposal was not well accepted due to the reason I stated above. We really should concentrate on libh as a complete and _clean_ solution. Sure, libh is a better solution. But, don't you think it's still good to have something working until it will become available. Multilingual sysinstall project started when FreeBSD is 2.0.5, and maintained in PAO-like style, but it's very larger patch than PAO (especially, it replaces almost all messages in release/sysinstall/menus.c) and it makes that "keeping current" work very difficult. Almost all code of this project is written when FreeBSD is 2.x, and it's in "maintainance-only" phase for years. If it's on -current tree, our work can be easier, and many developpers other than us also can do this work. If this makes us the spare time, perhaps we can help libh work. I don't think sysinstall is better solution, but it's available now. I'll glad to cvs delete this code entirely, if we can use better solution. In addition, the purpose of putting localized sysinstall in -CURRENT is rather dubious. -CURRENT/HEAD is a developers' branch, people who use this branch should be able to read English and the system error messages. If they cannot install the system with English sysinstall, I would have doubts on their programming and testing ability. People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. I think you are missing the point here. As you point out, the -current is for developers; it's for development and for testing. I don't think Tatsumi wants -current users to use I18N sysinstall to install -current, but, rather wants them to have a look at the code and test it. My main target is RELENG_4 and I hope this won't live until 5.x-RELEASE. It's in -current for only testing purpose. I would have no objections to L10N'ized sysinstall being maintained in the same way that PAO is maintained. The boot floppies and iso images can be put up somewhere for download, and maintained in RELENG_4. Why should it be in RELENG_4? If it's maintained in -current and regularly MFCed to RELENG_4, it is exposed to wide audience of -current developers and -stable users. That will attract more comments and bug reports, and will also minimize the delay between regular releases of FreeBSD and I18N/L10N sysinstall for them; the delay normally associated with L10N sysinstall (and PAO) after regular FreeBSD releases. And the delay has been prolonged sometimes because only a few developper was busy :-). Normally, I would welcome any I18N/L10N efforts in FreeBSD. However, the FreeBSD Project's official position paraphrased is "If you don't know what to do with -CURRENT, don't install it." See my comments above. Combined with the point that we should not divert efforts from libh, I hold the opinion that we should not import this. I don't think importing multilingual sysinstall will detract effort from libh. You see, even if it is maintained separately from the -current, it has its own maintainers and developers. I expect they are the same people who will maintain and develop I18N sysinstall when it is imported to the -current. They may or may not be libh developers at the same time. But, I don't think I18N sysinstall is suddenly needing a large army of developers and will steal them from the libh developer base. Yes. Programmers are needed when some change in source tree break this code and we can find it easier if it's in -current tree. Otherwise, only translators are needed for maintainance of *.TXT, *.hlp, and catalog files. Finally, still many thanks and applause to Tatsumi and others for this work. The same from me to them too. Thank you ! hosokawa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
asm error in compiling SMP kernel
I got this one this time.
Val
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-march=i686 -mpreferred-stack-boundary=2 ../../cam/cam_periph.c
../../cam/cam_periph.c: In function `cam_periph_unmapmem':
../../cam/cam_periph.c:687: internal error--unrecognizable insn:
(insn/i 287 1124 288 (parallel[
(set (mem/s/v:SI (plus:SI (reg:SI 0 %eax)
(const_int 284 [0x11c])) 0)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl
%2; pushl %3; callmtx_exit_hard; addl$8,%%esp;1:#
exitlock_norecurse") ("=m") 0[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(set (reg:SI 0 %eax)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl
%2; pushl %3; callmtx_exit_hard; addl$8,%%esp;1:#
exitlock_norecurse") ("=a") 1[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(clobber (reg:QI 1 %dl))
(clobber (reg:QI 2 %cl))
(clobber (mem:BLK (scratch) 0))
] ) -1 (insn_list 286 (nil))
(nil))
*** Error code 1
Stop in /usr/src/sys/compile/SQUID.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
On Wed, Dec 06, 2000 at 02:30:21AM -0800, Alfred Perlstein wrote: magnitude better than internationalized sysinstall, but at the current time libh is as much vapourware as KSEs are. No, KSE has paid developers working on it. When was the last cycle spent on libh? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XJp[` [i[ÌNX}Xv[gÀ{
±ñÉ¿íB
ËRÌ[Å·ÝܹñB
ܽÔáÁÄd¡µÄ[ªÍ¢½ûA{ɲßñȳ¢B
²»¡ÌÈ¢ûÍA[¨lÑ\µã°Ü·ÆÆàÉA
¨èÅ·ªA±ÌÜÜíµÄº³é椨è¢\µã°Ü·B
ü¡AXJp[`
[i[ÌNX}Xv[gÀ{I
IÅP¼lÉXJCp[tFNsuIbrfW^úóMZbg
sSU-CS5SETtðv[g¢½µÜ·B
ǵǵ²å¾³¢B
÷ßØèFPQQOúPUÜÅ
IÒÌ\FPQQQú
PQQSúɨͯ·é\èÅ·B
v[gÌåͱ¿ç©ç
@http://www.rakuten.co.jp/matuya/421062/427982/
¬Úªªªªªªªªªªªªªªª
E¨ÎéR[i[E¨µZbgÍ¿³¿
EIB~±µAçÐ̤¯wü
ENX}Xv[g
@EÌ¡o çÐ
@EШ̤l ·®«
@EÊ©Ð
¯ªªªªªªªªªªªªªªªªªªª®
¡ ¡ ¨ÎéR[i[E¨µZbgÍ¿³¿ ¡ ¡
@PQRPúÜÅͨÎéE¨µÐ¨Zbg̿ͳ¿Å·B
@@¨ÎéR[i[@http://www.rakuten.co.jp/matuya/410527/
@@¨µZbg@@@http://www.rakuten.co.jp/matuya/413025/
¡ ¡ ¤¯wü ¡ ¡
@ wüvª¦éÙÇvCX_EµÄ¢¨¢¨û®
@uyV¤¯wüvðÀ{IIÀ¿iÅwü·é½ßÉêvcÅ·I
@IB~±µ Qs¡~iÍ¿ÝÂüj ÊíÌ¿i WTOO~(ÁïÅÊ)
@@µIµ½IB~ðÆ©Ì»@ÉæèAÍ¿ÝÂÆS|ðÁ¦
@@¶ÁèÆÔð©¯ÄЯ °½AÜëâ©È¡ÉÈÁĢܷB
@@ªFñW
@@ÌúÔ 1201ú0000ª`1215ú2300ª
@üDÒª½¢ÙÇÀÈé
@ÝñÈŦͷêÎÅÅQOOO~ÌøI
@¿Í½ÂÁÄàSê¥ÌUOO~Å·B
@@üDͱ¿ç©ç@http://www.rakuten.co.jp/matuya/422498/429304/
@çÐ PTO ÊíÌ¿i VOO~(ÁïÅÊ)
@@µI³ê½¹ì@©ÔçðØèAÅÌ©zðgÁÄЯÝܵ½B
@@ÌúÔ 1201ú0000ª`1215ú2300ª
@üDÒª½¢ÙÇÀÈé
@ÝñÈŦͷêÎÅżzÉI
@¿Í½ÂÁÄàSê¥ÌUOO~Å·B
@@üDͱ¿ç©ç@http://www.rakuten.co.jp/matuya/422498/429504/
¡ ¡ NX}Xv[g ¡ ¡
ÜÂâ©çÌNX}Xv[gÍXJp[`
[i[ZbgB
å³ê½©çIÅP¼lÉNX}Xv[g¢½µÜ·B
v[gÌåͱ¿ç©ç
http://www.rakuten.co.jp/matuya/421062/427982/
¡ ¡ Ì¡o çÐ ¡ ¡
Ì~̨Ƣ¦ÎAçÐBêê±±ëð±ßÄЯ
½A¯àÌÌã\IÈçÅ·B
©zçÐ@@PTO VOO~
MçÐ@@@PTO VOO~
shçÐ@PTO VOO~
©zçÐ@@PTO VOO~
http://www.rakuten.co.jp/matuya/414998/427884/
¡ ¡ ¤¯wüÆÊí¤ið¯wüÌ¿ ¡ ¡
ÊíXÅ̵Ģé¤iƤ¯wüÅDµ½¤ið¯Éwüµ½
êAz檯¶Å êÎÊíwüÌ¿ªDæ³êÜ·B
ȨAPzæÉ«¨¢ °vª5000~ÈãÍ¿³¿Å·B
EÊí¤i{¤¯wü ¨ Êíwṳ̈iÌ¿ÌÝ¢½¾«Ü·
E¤¯wü{¤¯wü ¨ Sê¥ÌUOO~iPª̿j
EÊí¤i{I[NV ¨ Êíwṳ̈iÌ¿ÌÝ¢½¾«Ü·
ãLÉLڵĢéðͤiªPÂûƵĨͯūéêÌÝÅ·B
¤iªÇ¤µÄàQÂûÉÈéêͼûÉ¿ª©©èÜ·B
¯wüµ½êÍARgâõlɻ̱Æð¾LµÄº³êÎ
ū龯¿ª]ªÉ©©çÈ¢æ¤Éw͵ܷB
¡ ¡ Ш̤l ·®« ¡ ¡
u·®«vÍçЯÆÀÔA¯àÌÌã\Å·B èÃèZ@Å
@Ôð©¯ÄЯÝA©RÌ¡í¢ð³mÉ`¦Ä¢Ü·B
@sãêÎnûÉÆêé·®«©ÔçðÞ¿ÉAÌȪçÌè@ðg¢A
@½ñËñÉĢˢÉSð±ßÄЯ±ñÅ¢«Ü·B
·®«@SOO POOO~
http://www.rakuten.co.jp/matuya/414998/414999/
¡ ¡ Ê©Ð ¡ ¡
@X©Ìu
ÖqÊ©ÐvÌúàà¤IíÁĵܢܵ½ªA±ç©
@çÍ{ÐÌ{ÌìØðÐîµÄ¢\èÅ·BèÔÌÓZEÖq©çÃÐD
@«Ìû̽ßÉØ¢èÊ©ÐâLxc¢èÊ©ÐÜÅ¢ë¢ë èÜ·B
Ê©ÐR[i[
http://www.rakuten.co.jp/matuya/410530/
@ ¨Ð¨ÌÜÂâ
URLFhttp://www.rakuten.co.jp/matuya/
E-mail[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
"TH" == Tatsumi Hosokawa [EMAIL PROTECTED] writes: TH Multilingual sysinstall project started when FreeBSD is 2.0.5, and TH maintained in PAO-like style, but it's very larger patch than PAO TH (especially, it replaces almost all messages in TH release/sysinstall/menus.c) and it makes that "keeping current" work TH very difficult. Almost all code of this project is written when TH FreeBSD is 2.x, and it's in "maintainance-only" phase for years. I am working for translating sysinstall messages, release notes and help files to Korean for 4 years, from 2.2.1-RELEASE. I would be very happy if it will be included in -current and RELENG_4 system. Sometimes the release of I18N sysinstall(and former PAO) was delayed until next release, so if we can release I18N sysinstall timely for each release, it would help non-english users for FreeBSD very much. No other linux or BSD distribution(except localized ones) has such installer. It is very attractive thing for novice FreeBSD users to install in their mother tongue, even if he can understand English. And until libh is really working(hopefully 5.0-RELEASE?), I18N sysinstall is a good alternative. If we have it in -current, it would be relatively easy for debug and improve. I18N sysinstall still have a few bugs to be fixed although Tatsumi and other some CJK developers work. Finally, still many thanks and applause to Tatsumi and others for this work. The same from me to them too. Me too! TH Thank you ! -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [now sleeping]http://www.kr.FreeBSD.org/~cjh [when sleeping][EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Korea FreeBSD Users Group/www.kr.FreeBSD.org Web Data Bank/www.wdb.co.kr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. "If you don't know what to do with -CURRENT, don't install it." You seem to be working from the assumption that people who understand English can't understand any other language. I don't know anything about the design question you raise, except that code which has not yet been written always seems more perfect than that which has. :-) -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
On Wed, Dec 06, 2000 at 01:03:29PM -0500, Trevor Johnson wrote: People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. "If you don't know what to do with -CURRENT, don't install it." You seem to be working from the assumption that people who understand English can't understand any other language. The reverse is generally true: native speakers of the English/American language often don't understand any other language :-P -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PNA?
Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNA?
Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom refuse to give us documentation. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
My feeling on this is that sysinstall is (and always has been :-) at the end of its life and adding multi-lingual capabilities to it is a reasonable part of its retirement. The libh project is promising but suffers from a lack of volunteers, volunteers who aren't working on sysinstall either so I'm not worried about it somehow sucking the necessary time and attention away from libh. Hacking on sysinstall I18N in -current gives the developers the current.freebsd.org snapshot machine as a testing vehicle (why should the SMP people get all the benefit?) and is entirely reasonable as a staging area for -stable, which is also what -current is supposed to be. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
No, KSE has paid developers working on it. When was the last cycle spent on libh? I'm glad you brought that up - I've been trying to find more things for you to do. I'll bring it up during the engineering staff meeting today. ;-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs-cur.6925.gz appears to be corrupt
With
# ctm -b /cvs cvs-cur.6925.gz
I get
FR: /cvs/CVSROOT/history md5 mismatch.
cvs-cur.6925.gz Fatal error: Corrupt patch.
Expected "\n" but didn't find it {20}.
ctm: exit(96)
Anybody like to comment?
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million keyboards could produce
the Complete Works of Shakespeare; now, thanks to the Internet, we know
this is not true."Robert Wilensky, University of California
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PNA?
Mike Smith wrote: Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom refuse to give us documentation. I don't know whether their chips support version 2.0 of the standard (how important is this?) but Davicom Semiconductor is listed at http://www.freebsd.org/commercial/hardware.html . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Other Linux stuff...
For trivial cases, the simplest solution would be to just remove /compat/linux/usr/bin/ldd and have our native ldd do the work. If something depends on the switches, this won't work. At http://huizen.dds.nl/~frodol/glibc/problems.html it says: * ldd gives real strange output, sometimes... The ldd script that comes with glibc-2.0.6 handles libc5 executables incorrectly, resulting in strange output. You are probably better off if you always use the ldd that comes with ld.so-1.9.9. Implement this by deleting or renaming /usr/i486-linux-libc6/bin/ldd I've done this under Linux itself, and it worked well. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS
In my bios I have PnPOS=NO, USB-IRQ=Disabled. The commit below results in a PCI interrupt storm and a terminally wedged system right after interrupts are enabled. Poul-Henning | nsayer 2000/12/03 09:07:24 PST | | Modified files: | sys/pci ohci_pci.c uhci_pci.c | Log: | We now have the ability to assign the correct IRQ when PNP-OS is turned | on. So stop failing the attach if the IRQ is unassigned. With this | patch, I can now boot with PNP-OS YES in my BIOS no differently than | PNP-OS NO (which is a good thing since Windows hangs with PNP-OS NO). | | Obtained from:msmith | | Revision ChangesPath | 1.21 +1 -11 src/sys/pci/ohci_pci.c | 1.32 +1 -11 src/sys/pci/uhci_pci.c -- 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: -current kernel hangs machine solid ...
Just checking in ... I haven't had one of these random hangs in the last week or so. Anyone else? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel hangs machine solid ...
Actually... I just noticed that my hanging machine had been up for 5 days. I started it doing 'make -j8 world' in a continual loop a couple hours ago before leaving work... I'll see tomorrow. -Steve On Wed, Dec 06, 2000 at 05:37:14PM -0600, Michael Harnois wrote: Just checking in ... I haven't had one of these random hangs in the last week or so. Anyone else? -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis 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: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS
In my bios I have PnPOS=NO, USB-IRQ=Disabled. The commit below results in a PCI interrupt storm and a terminally wedged system right after interrupts are enabled. This would be a bug in the UHCI or OHCI driver then. You can avoid it by not running the driver. Poul-Henning | nsayer 2000/12/03 09:07:24 PST | | Modified files: | sys/pci ohci_pci.c uhci_pci.c | Log: | We now have the ability to assign the correct IRQ when PNP-OS is turned | on. So stop failing the attach if the IRQ is unassigned. With this | patch, I can now boot with PNP-OS YES in my BIOS no differently than | PNP-OS NO (which is a good thing since Windows hangs with PNP-OS NO). | | Obtained from:msmith | | Revision ChangesPath | 1.21 +1 -11 src/sys/pci/ohci_pci.c | 1.32 +1 -11 src/sys/pci/uhci_pci.c -- 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 -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS
In my bios I have PnPOS=NO, USB-IRQ=Disabled. The commit below results in a PCI interrupt storm and a terminally wedged system right after interrupts are enabled. This would be a bug in the UHCI or OHCI driver then. You can avoid it by not running the driver. I should have mentioned; you can probably also avoid it by letting your BIOS give the USB controller an IRQ, since it'll almost certainly also perform whatever initialisation the driver is currently missing out on. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS
In message [EMAIL PROTECTED], Mike Smith writes: In my bios I have PnPOS=NO, USB-IRQ=Disabled. The commit below results in a PCI interrupt storm and a terminally wedged system right after interrupts are enabled. This would be a bug in the UHCI or OHCI driver then. You can avoid it by not running the driver. I should have mentioned; you can probably also avoid it by letting your BIOS give the USB controller an IRQ, since it'll almost certainly also perform whatever initialisation the driver is currently missing out on. Right, that is what I did once I realized that this particular commit was the culprit. -- 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: Progress report: Multilingual sysinstall for -current
In message [EMAIL PROTECTED] Wilko Bulte writes: : You seem to be working from the assumption that people who understand : English can't understand any other language. : : The reverse is generally true: native speakers of the English/American : language often don't understand any other language hai! so desu. americanjin wa nihongo wakarimasen. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS
I should have mentioned; you can probably also avoid it by letting your BIOS give the USB controller an IRQ, since it'll almost certainly also perform whatever initialisation the driver is currently missing out on. Right, that is what I did once I realized that this particular commit was the culprit. The commit isn't (really) the culprit; it's just exposed a bug in the USB chipset driver in question. (I'm mostly just making this point so that other people don't go blaming 'correct' PCI behaviour for their problems 8). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled: | I've ported Multilingual sysinstall to -current. I put the latest | source and binaries (Japanese/Englush only) is at | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/ | (please note that non-English docuemnt files are based on 4.2-RELEASE) Just an idea. :) Do you have Alpha boot floppies? Does kons25/big5con/korean compile on Alpha? Would this fit on our ever growing mfsroot.flp and kern.flp? I recall seeing the release engineers struggling with fitting the kernel. It would be hard to make OpenBOOT and SRM do what we do in kons25. (Doable, but someone has to do it.) I also know that Alpha SRM+vidcontrol+sc0 can only have one video mode, 80x25. Can Mr. Yokota clarify this for me? If this makes into the normal sysinstall, can we simply have several versions of the boot floppies built during make release? Thanks, -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel hangs machine solid ...
On Wednesday, 6 December 2000 at 17:37:14 -0600, Michael Harnois wrote: Just checking in ... I haven't had one of these random hangs in the last week or so. Anyone else? Yup. My freshly installed machine has hung up again. Completely dead, apparently during a make world. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP kernel builds borked
Builds are failing for SMP kernels with sources CVSup'd a couple
of hours ago using the GENERIC config file with the following diffs.
Index: GENERIC
===
RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v
retrieving revision 1.291
diff -u -r1.291 GENERIC
--- GENERIC 2000/11/15 18:36:24 1.291
+++ GENERIC 2000/12/07 00:43:09
@@ -18,7 +18,7 @@
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.291 2000/11/15 18:36:24 imp Exp $
machinei386
-cpuI386_CPU
+#cpu I386_CPU
cpuI486_CPU
cpuI586_CPU
cpuI686_CPU
@@ -59,8 +59,8 @@
optionsKBD_INSTALL_CDEV# install a CDEV entry in /dev
# To make an SMP kernel, the next two are needed
-#options SMP # Symmetric MultiProcessor Kernel
-#options APIC_IO # Symmetric (APIC) I/O
+optionsSMP # Symmetric MultiProcessor Kernel
+optionsAPIC_IO # Symmetric (APIC) I/O
device isa
device eisa
It looks like revision 1.132 of src/sys/sys/proc.h might be the
culprit. I'll look deeper right after dinner. Here's the output
of the build.
steve@bsd(/usr/src/sys/compile/GENERIC)$ make
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../cam/cam_periph.c
../../cam/cam_periph.c: In function `cam_periph_unmapmem':
../../cam/cam_periph.c:687: internal error--unrecognizable insn:
(insn/i 287 1112 288 (parallel[
(set (mem/s/v:SI (plus:SI (reg:SI 0 %eax)
(const_int 284 [0x11c])) 0)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl
%2; pushl %3; callmtx_exit_hard; addl$8,%%esp;1:#
exitlock_norecurse") ("=m") 0[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(set (reg:SI 0 %eax)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f; pushl
%2; pushl %3; callmtx_exit_hard; addl$8,%%esp;1:#
exitlock_norecurse") ("=a") 1[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(clobber (reg:QI 1 %dl))
(clobber (reg:QI 2 %cl))
(clobber (mem:BLK (scratch) 0))
] ) -1 (insn_list 286 (nil))
(nil))
*** Error code 1
Stop in /b/src/sys/compile/GENERIC.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PNA?
Mike Smith wrote: Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom refuse to give us documentation. I don't know whether their chips support version 2.0 of the standard (how important is this?) but Davicom Semiconductor is listed at http://www.freebsd.org/commercial/hardware.html . 10 seconds with their site confirms that they only support the 1Mbps standard. 2.0 is the standard revision which covers 10Mbps operation. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current kernel build failure -- cam_periph.c
I've been trying to build a current kernel from current sources for a day now
and I keep getting this:
cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../i386/i386/locore.s
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../cam/cam_periph.c
../../cam/cam_periph.c: In function `cam_periph_unmapmem':
../../cam/cam_periph.c:687: internal error--unrecognizable insn:
(insn/i 376 1397 377 (parallel[
(set (mem/s/v:SI (plus:SI (reg:SI 0 %eax)
(const_int 284 [0x11c])) 0)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2;
pushl %3; callmtx_exit_hard; addl$8,%%esp;1:# exitlock_norecurse")
("=m") 0[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(set (reg:SI 0 %eax)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2;
pushl %3; callmtx_exit_hard; addl$8,%%esp;1:# exitlock_norecurse")
("=a") 1[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(clobber (reg:QI 1 %dl))
(clobber (reg:QI 2 %cl))
(clobber (mem:BLK (scratch) 0))
] ) -1 (insn_list 375 (nil))
(nil))
*** Error code 1
Stop in /usr/src/sys/compile/pro2
I did a make world last night from current sources
and still no go
Thanks
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- cam_periph.c
On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). -- 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: Current kernel build failure -- cam_periph.c
On Wed, 6 Dec 2000, John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). ah, so I take it a 'make buildworld' doesn't fix thsi one :) ah well, had to do it anyway ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- cam_periph.c
At 05:49 PM 12/6/2000 -0800, you wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). -- 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 Yes It's a different kind of error. I've never seen this building a kernel before. The same kernel config without SMP enabled builds fine ! == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current kernel build failure -- cam_periph.c
On Wed, Dec 06, 2000 at 06:13:50PM -0800, Manfred Antar wrote: # At 05:49 PM 12/6/2000 -0800, you wrote: # # I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() # compiles in dozens of other places just fine (and has for months now). # # Yes # It's a different kind of error. # I've never seen this building a kernel before. # The same kernel config without SMP enabled builds fine ! At least according to my tests thus far it appears it occurs when 'cpu I386_CPU' is not in your config file. It isn't really an SMP issue as far as I can tell, except that you must remove 'cpu I386_CPU' to build an SMP kernel. -steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- cam_periph.c
On 07-Dec-00 John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). Nope, it was a sublte bug in the 486 optimized mutex operations, which had invalid register constraints probably dating back to several older revisions in BSD/OS before we got the code. It should be fixed now. -- 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: Lucent Orinoco Gold PCCard?
There is definately a trend to lower prices. I just found this. A new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia cards for $699. The access point sounds interesting. I personally would like to use it as a repeater and network bridge. http://www.intel.com/network/products/wireless.htm https://merchant.hibbertco.com/servlet/InteComServlet?SessionID=319728709221315074OrderID=71803ItemCnt=1Adapters=yes ed Doug Ambrisko wrote: Warner Losh writes: | In message [EMAIL PROTECTED] Doug Ambrisko writes: | : Well this is what I'm doing with the Aironet stuff. I have a script | : to flip between modes until it sync's up. I bought the PCMCIA ISA | : adapter for $25 from a local surplus place. | | Does this mean that the an driver can operate in "base station" mode? No, just ad-hoc (atleast that's what is published). So on my laptop my script flips between modes (ad-hoc infrastructure) until it sync's up with whatever it can find. I start it out of pccard.conf so it is automatic on card insertion, reboot or wakeup. | : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around | : $220 that can do 128 bit encryption, has an antenna and is Web administered. | : I haven't used it but it looks interesting. | | I'll have to check this out as well. Let us know what you find out. Doug A. 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: Lucent Orinoco Gold PCCard?
On Tue, Dec 05, 2000 at 01:46:51PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Doug Ambrisko writes: : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around : $220 that can do 128 bit encryption, has an antenna and is Web administered. : I haven't used it but it looks interesting. I'll have to check this out as well. FWIW, I ordered one of these today.. I'll pass on my discoveries with my various wireless cards (mostly Lucent) if y'all are interested.. -aDe [today's toy is powered by the letters 'I', 'R' and 'S'] -- Ade Lovett, Austin, TX. [EMAIL PROTECTED] FreeBSD: 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: Current kernel build failure -- cam_periph.c
At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: On 07-Dec-00 John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). Nope, it was a sublte bug in the 486 optimized mutex operations, which had invalid register constraints probably dating back to several older revisions in BSD/OS before we got the code. It should be fixed now. John It compiles now fine but panics on booting: Doing initial network setup: hostname. panic: mutex sched lock owned at ../../kern/kern_mutex.c:322 cpuid = 0; lapic.id = boot() called on cpu#0 syncing disks... Fatal double fault: eip = 0xc02b0e7d esp = 0xcafce000 ebp = 0xcafce020 cpuid = 0; lapic.id = I built another one and got a different panic: Initial rc.i386 panic: spin lock sched lock held by 0x0xc0390a01 for 5 seconds cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 syncing disks... Just frozen at this point Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lucent Orinoco Gold PCCard?
Warner Losh wrote: In message [EMAIL PROTECTED] Doug Ambrisko writes: : Well this is what I'm doing with the Aironet stuff. I have a script : to flip between modes until it sync's up. I bought the PCMCIA ISA : adapter for $25 from a local surplus place. Does this mean that the an driver can operate in "base station" mode? : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around : $220 that can do 128 bit encryption, has an antenna and is Web administered. : I haven't used it but it looks interesting. Linksys has a new one, WAP-11, that has all of the above and dual antennas (should be much better for signal diversity) for about $240, but nobody really has it in stock yet. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
