From owner-freebsd-current Sun Apr 23 00:23:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA15219 for current-outgoing; Sun, 23 Apr 1995 00:23:13 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA15206 for ; Sun, 23 Apr 1995 00:21:11 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA22446 for current@freebsd.org; Sun, 23 Apr 1995 17:18:27 +1000 Date: Sun, 23 Apr 1995 17:18:27 +1000 From: Bruce Evans Message-Id: <199504230718.RAA22446@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: LINT Sender: current-owner@FreeBSD.org Precedence: bulk Several modules in the LINT kernel no longer compile. if_fddi_subr.c has never been compilable in the FreeBSD tree. The warnings in the old net sources make it hard to see the errors. Bruce ./@/net/if_fddisubr.c: In function `fddi_input': ./@/net/if_fddisubr.c:486: `ac' undeclared (first use this function) ./@/net/if_fddisubr.c:486: (Each undeclared identifier is reported only once ./@/net/if_fddisubr.c:486: for each function it appears in.) ./@/net/if_fddisubr.c:487: `eh' undeclared (first use this function) In file included from ./@/netiso/tp_inet.c:102: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_inet.c:101: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' ./@/netiso/tp_inet.c:130: warning: return-type defaults to `int' ./@/netiso/tp_inet.c: In function `in_getsufx': ./@/netiso/tp_inet.c:138: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:139: warning: `return' with no value, in function returning non-void ./@/netiso/tp_inet.c:142: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:145: warning: control reaches end of non-void function ./@/netiso/tp_inet.c: In function `in_putsufx': ./@/netiso/tp_inet.c:166: warning: type of `sufxlen' defaults to `int' ./@/netiso/tp_inet.c:171: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:171: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `in_recycle_tsuffix': ./@/netiso/tp_inet.c:197: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:197: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `in_putnetaddr': ./@/netiso/tp_inet.c:227: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:234: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: At top level: ./@/netiso/tp_inet.c:258: warning: return-type defaults to `int' ./@/netiso/tp_inet.c: In function `in_cmpnetaddr': ./@/netiso/tp_inet.c:263: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:265: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:267: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:269: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `in_getnetaddr': ./@/netiso/tp_inet.c:299: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:300: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:303: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:304: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: At top level: ./@/netiso/tp_inet.c:333: warning: return-type defaults to `int' ./@/netiso/tp_inet.c: In function `tpip_mtu': ./@/netiso/tp_inet.c:338: warning: implicit declaration of function `logpri' ./@/netiso/tp_inet.c:339: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:341: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `tpip_output': ./@/netiso/tp_inet.c:372: warning: implicit declaration of function `tpip_output_dg' ./@/netiso/tp_inet.c:372: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:372: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c:373: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `tpip_input': ./@/netiso/tp_inet.c:535: warning: implicit declaration of function `tp_input' ./@/netiso/tp_inet.c:544: warning: statement with no effect ./@/netiso/tp_inet.c: In function `tpin_quench': ./@/netiso/tp_inet.c:575: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: In function `tpip_ctlinput': ./@/netiso/tp_inet.c:603: warning: redundant redeclaration of `inetctlerrmap' in same scope ./@/netinet/in_var.h:89: warning: previous declaration of `inetctlerrmap' ./@/netiso/tp_inet.c:604: warning: redundant redeclaration of `zeroin_addr' in same scope ./@/netinet/in_var.h:88: warning: previous declaration of `zeroin_addr' ./@/netiso/tp_inet.c:605: warning: redundant redeclaration of `tp_quench' in same scope ./@/netiso/tp_inet.c:556: warning: previous declaration of `tp_quench' ./@/netiso/tp_inet.c:618: warning: passing arg 1 of `in_pcbnotify' from incompatible pointer type ./@/netiso/tp_inet.c:627: warning: passing arg 1 of `in_pcbnotify' from incompatible pointer type ./@/netiso/tp_inet.c:647: warning: passing arg 1 of `in_pcbnotify' from incompatible pointer type ./@/netiso/tp_inet.c: At top level: ./@/netiso/tp_inet.c:673: warning: type mismatch with previous external decl ./@/netiso/tp_inet.c:606: warning: previous external decl of `tpin_abort' ./@/netiso/tp_inet.c: In function `tpin_abort': ./@/netiso/tp_inet.c:679: warning: implicit declaration of function `tp_driver' ./@/netiso/tp_inet.c:679: dereferencing pointer to incomplete type ./@/netiso/tp_inet.c: At top level: ./@/netiso/tp_inet.c:685: warning: return-type defaults to `int' ./@/netiso/tp_inet.c: In function `dump_inaddr': ./@/netiso/tp_inet.c:688: warning: control reaches end of non-void function ./@/netiso/tp_ip.h: At top level: ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_output.c:89: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_output.c:85: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' In file included from ./@/netiso/tp_output.c:89: ./@/netiso/tp_pcb.h:344: warning: redundant redeclaration of `time' in same scope ./@/sys/kernel.h:59: warning: previous declaration of `time' ./@/netiso/tp_output.c: In function `tp_consistency': ./@/netiso/tp_output.c:126: warning: implicit declaration of function `tp_mask_to_num' ./@/netiso/tp_output.c:129: warning: statement with no effect ./@/netiso/tp_output.c:134: warning: implicit declaration of function `logpri' ./@/netiso/tp_output.c:166: warning: comparison is always 0 due to limited range of data type ./@/netiso/tp_output.c:317: warning: statement with no effect ./@/netiso/tp_output.c: In function `tp_ctloutput': ./@/netiso/tp_output.c:377: warning: statement with no effect ./@/netiso/tp_output.c:416: warning: implicit declaration of function `tp_rsyset' ./@/netiso/tp_output.c:420: warning: implicit declaration of function `tp_emit' ./@/netiso/tp_output.c:490: dereferencing pointer to incomplete type ./@/netiso/tp_output.c:490: dereferencing pointer to incomplete type ./@/netiso/tp_output.c:658: warning: statement with no effect ./@/netiso/tp_output.c:663: warning: implicit declaration of function `tp_confirm' ./@/netiso/tp_output.c:703: warning: implicit declaration of function `m_compress' ./@/netiso/tp_ip.h: At top level: ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_pcb.c:97: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_pcb.c:95: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' ./@/netiso/tp_pcb.c:263: warning: redundant redeclaration of `in_pcbbind' in same scope ./@/netinet/in_pcb.h:87: warning: previous declaration of `in_pcbbind' ./@/netiso/tp_pcb.c:264: warning: redundant redeclaration of `in_pcbconnect' in same scope ./@/netinet/in_pcb.h:88: warning: previous declaration of `in_pcbconnect' ./@/netiso/tp_pcb.c:270: warning: redundant redeclaration of `in_pcballoc' in same scope ./@/netinet/in_pcb.h:86: warning: previous declaration of `in_pcballoc' ./@/netiso/tp_pcb.c:273: warning: redundant redeclaration of `tp_inpcb' in same scope ./@/netiso/tp_ip.h:88: warning: previous declaration of `tp_inpcb' ./@/netiso/tp_pcb.c:291: warning: redundant redeclaration of `tp_isopcb' in same scope ./@/netiso/tp_clnp.h:91: warning: previous declaration of `tp_isopcb' ./@/netiso/tp_pcb.c:294: warning: redundant redeclaration of `iso_putnetaddr' in same scope ./@/netiso/tp_pcb.c:276: warning: previous declaration of `iso_putnetaddr' ./@/netiso/tp_pcb.c:295: warning: redundant redeclaration of `iso_getnetaddr' in same scope ./@/netiso/tp_pcb.c:277: warning: previous declaration of `iso_getnetaddr' ./@/netiso/tp_pcb.c:296: warning: redundant redeclaration of `iso_cmpnetaddr' in same scope ./@/netiso/tp_pcb.c:278: warning: previous declaration of `iso_cmpnetaddr' ./@/netiso/tp_pcb.c:297: warning: redundant redeclaration of `iso_putsufx' in same scope ./@/netiso/tp_pcb.c:279: warning: previous declaration of `iso_putsufx' ./@/netiso/tp_pcb.c:298: warning: redundant redeclaration of `iso_getsufx' in same scope ./@/netiso/tp_pcb.c:280: warning: previous declaration of `iso_getsufx' ./@/netiso/tp_pcb.c:299: warning: redundant redeclaration of `iso_recycle_tsuffix' in same scope ./@/netiso/tp_pcb.c:281: warning: previous declaration of `iso_recycle_tsuffix' ./@/netiso/tp_pcb.c:300: warning: redundant redeclaration of `iso_pcbbind' in same scope ./@/netiso/tp_pcb.c:283: warning: previous declaration of `iso_pcbbind' ./@/netiso/tp_pcb.c:302: warning: redundant redeclaration of `tpclnp_mtu' in same scope ./@/netiso/tp_pcb.c:282: warning: previous declaration of `tpclnp_mtu' ./@/netiso/tp_pcb.c:303: warning: redundant redeclaration of `iso_pcbdisconnect' in same scope ./@/netiso/tp_pcb.c:285: warning: previous declaration of `iso_pcbdisconnect' ./@/netiso/tp_pcb.c:304: warning: redundant redeclaration of `iso_pcbdetach' in same scope ./@/netiso/tp_pcb.c:286: warning: previous declaration of `iso_pcbdetach' ./@/netiso/tp_pcb.c:305: warning: redundant redeclaration of `iso_pcballoc' in same scope ./@/netiso/tp_pcb.c:287: warning: previous declaration of `iso_pcballoc' ./@/netiso/tp_pcb.c:307: warning: redundant redeclaration of `tp_isopcb' in same scope ./@/netiso/tp_pcb.c:291: warning: previous declaration of `tp_isopcb' ./@/netiso/tp_pcb.c:332: warning: initialization from incompatible pointer type ./@/netiso/tp_pcb.c:332: warning: initialization from incompatible pointer type ./@/netiso/tp_pcb.c: In function `tp_init': ./@/netiso/tp_pcb.c:387: invalid use of undefined type `struct inpcb' ./@/netiso/tp_pcb.c:387: invalid use of undefined type `struct inpcb' ./@/netiso/tp_pcb.c: In function `tp_soisdisconnecting': ./@/netiso/tp_pcb.c:431: warning: statement with no effect ./@/netiso/tp_pcb.c: In function `tp_soisdisconnected': ./@/netiso/tp_pcb.c:476: warning: statement with no effect ./@/netiso/tp_pcb.c:482: warning: implicit declaration of function `tp_recycle_tsuffix' ./@/netiso/tp_pcb.c:483: warning: implicit declaration of function `tp_etimeout' ./@/netiso/tp_pcb.c: In function `tp_freeref': ./@/netiso/tp_pcb.c:513: warning: implicit declaration of function `logpri' ./@/netiso/tp_pcb.c:517: warning: statement with no effect ./@/netiso/tp_pcb.c: At top level: ./@/netiso/tp_pcb.c:605: warning: return-type defaults to `int' ./@/netiso/tp_pcb.c:649: warning: return-type defaults to `int' ./@/netiso/tp_pcb.c: In function `tp_attach': ./@/netiso/tp_pcb.c:656: warning: redundant redeclaration of `tp_conn_param' in same scope ./@/netiso/tp_pcb.c:110: warning: previous declaration of `tp_conn_param' ./@/netiso/tp_pcb.c:662: warning: statement with no effect ./@/netiso/tp_pcb.c:730: dereferencing pointer to incomplete type ./@/netiso/tp_pcb.c: In function `tp_detach': ./@/netiso/tp_pcb.c:787: warning: redundant redeclaration of `tp_freeref' in same scope ./@/netiso/tp_pcb.c:506: warning: previous declaration of `tp_freeref' ./@/netiso/tp_pcb.c:795: warning: statement with no effect ./@/netiso/tp_pcb.c: At top level: ./@/netiso/tp_pcb.c:897: warning: return-type defaults to `int' ./@/netiso/tp_pcb.c: In function `tp_tselinuse': ./@/netiso/tp_pcb.c:897: warning: type of `tlen' defaults to `int' ./@/netiso/tp_pcb.c:897: warning: type of `reuseaddr' defaults to `int' ./@/netiso/tp_pcb.c: At top level: ./@/netiso/tp_pcb.c:928: warning: return-type defaults to `int' ./@/netiso/tp_pcb.c: In function `tp_pcbbind': ./@/netiso/tp_pcb.c:933: warning: `tsel' might be used uninitialized in this function ./@/netiso/tp_pcb.c: At top level: ./@/netiso/tp_pcb.c:273: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_subr.c:94: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_subr.c:88: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' In file included from ./@/netiso/tp_subr.c:94: ./@/netiso/tp_pcb.h:344: warning: redundant redeclaration of `time' in same scope ./@/sys/kernel.h:59: warning: previous declaration of `time' ./@/netiso/tp_subr.c:102: warning: redundant redeclaration of `ticks' in same scope ./@/sys/kernel.h:66: warning: previous declaration of `ticks' ./@/netiso/tp_subr.c: In function `tp_goodXack': ./@/netiso/tp_subr.c:122: warning: statement with no effect ./@/netiso/tp_subr.c:143: warning: statement with no effect ./@/netiso/tp_subr.c: In function `tp_rtt_rtv': ./@/netiso/tp_subr.c:220: warning: implicit declaration of function `logpri' ./@/netiso/tp_subr.c:171: warning: `delta' might be used uninitialized in this function ./@/netiso/tp_subr.c: In function `tp_goodack': ./@/netiso/tp_subr.c:261: warning: statement with no effect ./@/netiso/tp_subr.c:266: warning: statement with no effect ./@/netiso/tp_subr.c:335: warning: implicit declaration of function `tpsbcheck' ./@/netiso/tp_subr.c:252: warning: `old_fcredit' might be used uninitialized in this function ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:420: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tp_send': ./@/netiso/tp_subr.c:496: warning: statement with no effect ./@/netiso/tp_subr.c:498: warning: statement with no effect ./@/netiso/tp_subr.c:502: warning: statement with no effect ./@/netiso/tp_subr.c:537: warning: statement with no effect ./@/netiso/tp_subr.c:618: warning: statement with no effect ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:629: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tp_packetize': ./@/netiso/tp_subr.c:636: warning: implicit declaration of function `tp_headersize' ./@/netiso/tp_subr.c:639: warning: redundant redeclaration of `m_split' in same scope ./@/sys/mbuf.h:388: warning: previous declaration of `m_split' ./@/netiso/tp_subr.c:633: warning: `n' might be used uninitialized in this function ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:725: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tp_stash': ./@/netiso/tp_subr.c:751: warning: statement with no effect ./@/netiso/tp_subr.c:763: warning: statement with no effect ./@/netiso/tp_subr.c:802: warning: statement with no effect ./@/netiso/tp_subr.c:807: warning: implicit declaration of function `tp_rsyset' ./@/netiso/tp_subr.c:834: warning: implicit declaration of function `tp_local_credit' ./@/netiso/tp_subr.c:840: warning: statement with no effect ./@/netiso/tp_subr.c:857: warning: statement with no effect ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:880: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tp_rsyflush': ./@/netiso/tp_subr.c:884: warning: statement with no effect ./@/netiso/tp_subr.c:882: warning: `mp' might be used uninitialized in this function ./@/netiso/tp_subr.c:897: warning: control reaches end of non-void function ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:900: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tp_rsyset': ./@/netiso/tp_subr.c:911: warning: `return' with no value, in function returning non-void ./@/netiso/tp_subr.c:918: warning: control reaches end of non-void function ./@/netiso/tp_subr.c: At top level: ./@/netiso/tp_subr.c:921: warning: return-type defaults to `int' ./@/netiso/tp_subr.c: In function `tpsbcheck': ./@/netiso/tp_subr.c:921: warning: type of `i' defaults to `int' ./@/netiso/tp_subr.c:948: warning: control reaches end of non-void function ./@/netiso/tp_ip.h: At top level: ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_subr2.c:103: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_subr2.c:96: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' In file included from ./@/netiso/tp_subr2.c:103: ./@/netiso/tp_pcb.h:344: warning: redundant redeclaration of `time' in same scope ./@/sys/kernel.h:59: warning: previous declaration of `time' ./@/netiso/tp_subr2.c: In function `tp_local_credit': ./@/netiso/tp_subr2.c:147: warning: implicit declaration of function `logpri' ./@/netiso/tp_subr2.c:156: warning: statement with no effect ./@/netiso/tp_subr2.c: In function `tp_protocol_error': ./@/netiso/tp_subr2.c:187: warning: statement with no effect ./@/netiso/tp_subr2.c: In function `tp_indicate': ./@/netiso/tp_subr2.c:230: warning: statement with no effect ./@/netiso/tp_subr2.c:273: warning: statement with no effect ./@/netiso/tp_subr2.c: At top level: ./@/netiso/tp_subr2.c:402: warning: return-type defaults to `int' ./@/netiso/tp_subr2.c: In function `tp_netcmd': ./@/netiso/tp_subr2.c:410: warning: `return' with no value, in function returning non-void ./@/netiso/tp_subr2.c:424: warning: implicit declaration of function `pk_disconnect' ./@/netiso/tp_subr2.c:437: warning: control reaches end of non-void function ./@/netiso/tp_subr2.c: In function `tp_mask_to_num': ./@/netiso/tp_subr2.c:461: warning: statement with no effect ./@/netiso/tp_subr2.c: At top level: ./@/netiso/tp_subr2.c:471: warning: return-type defaults to `int' ./@/netiso/tp_subr2.c: In function `copyQOSparms': ./@/netiso/tp_subr2.c:481: warning: control reaches end of non-void function ./@/netiso/tp_subr2.c: In function `tp_route_to': ./@/netiso/tp_subr2.c:631: warning: statement with no effect ./@/netiso/tp_subr2.c:640: warning: implicit declaration of function `Dump_buf' ./@/netiso/tp_subr2.c:656: warning: implicit declaration of function `iso_putsufx' ./@/netiso/tp_subr2.c:661: warning: empty body in an else-statement ./@/netiso/tp_subr2.c:672: warning: implicit declaration of function `clnp_route' ./@/netiso/tp_subr2.c:690: warning: implicit declaration of function `tp_set_npcb' ./@/netiso/tp_subr2.c:709: warning: statement with no effect ./@/netiso/tp_subr2.c: In function `tp0_stash': ./@/netiso/tp_subr2.c:733: warning: statement with no effect ./@/netiso/tp_subr2.c:743: warning: statement with no effect ./@/netiso/tp_subr2.c:760: warning: implicit declaration of function `pk_flowcontrol' ./@/netiso/tp_subr2.c: At top level: ./@/netiso/tp_subr2.c:828: warning: return-type defaults to `int' ./@/netiso/tp_subr2.c: In function `dump_addr': ./@/netiso/tp_subr2.c:832: warning: implicit declaration of function `dump_inaddr' ./@/netiso/tp_subr2.c:836: warning: implicit declaration of function `dump_isoaddr' ./@/netiso/tp_subr2.c:843: warning: control reaches end of non-void function ./@/netiso/tp_subr2.c: At top level: ./@/netiso/tp_subr2.c:854: warning: return-type defaults to `int' ./@/netiso/tp_subr2.c: In function `Dump_buf': ./@/netiso/tp_subr2.c:880: warning: control reaches end of non-void function ./@/netiso/tp_ip.h: At top level: ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_trace.c:89: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:83, from ./@/netiso/tp_trace.c:88: ./@/net/route.h:262: warning: `struct socket' declared inside parameter list ./@/net/route.h:262: warning: its scope is only this definition or declaration, ./@/net/route.h:262: warning: which is probably not what you want. ./@/net/route.h:264: warning: `struct socket' declared inside parameter list In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_trace.c:88: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' In file included from ./@/netiso/tp_trace.c:92: ./@/netiso/tp_trace.h:118: field `tpt_Inpcb' has incomplete type ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known In file included from ./@/netiso/tp_usrreq.c:91: ./@/netiso/tp_pcb.h:301: warning: `/*' within comment In file included from ./@/netiso/tp_ip.h:84, from ./@/netiso/tp_usrreq.c:90: ./@/netinet/in_pcb.h:47: warning: parameter names (without types) in function declaration ./@/netinet/in_pcb.h:47: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:50: parse error before `LIST_ENTRY' ./@/netinet/in_pcb.h:50: warning: no semicolon at end of struct or union ./@/netinet/in_pcb.h:51: parse error before `inp_hash' ./@/netinet/in_pcb.h:51: warning: data definition has no type or storage class ./@/netinet/in_pcb.h:64: parse error before `}' ./@/netiso/tp_usrreq.c: In function `dump_mbuf': ./@/netiso/tp_usrreq.c:117: warning: implicit declaration of function `logpri' ./@/netiso/tp_usrreq.c: At top level: ./@/netiso/tp_usrreq.c:173: warning: return-type defaults to `int' ./@/netiso/tp_usrreq.c: In function `tp_rcvoob': ./@/netiso/tp_usrreq.c:221: warning: implicit declaration of function `wakeup' ./@/netiso/tp_usrreq.c:257: warning: statement with no effect ./@/netiso/tp_usrreq.c: At top level: ./@/netiso/tp_usrreq.c:280: warning: return-type defaults to `int' ./@/netiso/tp_usrreq.c: In function `tp_sendoob': ./@/netiso/tp_usrreq.c:352: warning: statement with no effect ./@/netiso/tp_usrreq.c: In function `tp_usrreq': ./@/netiso/tp_usrreq.c:396: warning: statement with no effect ./@/netiso/tp_usrreq.c:402: warning: statement with no effect ./@/netiso/tp_usrreq.c:422: warning: large integer implicitly truncated to unsigned type ./@/netiso/tp_usrreq.c:435: warning: implicit declaration of function `tp_detach' ./@/netiso/tp_usrreq.c:445: warning: large integer implicitly truncated to unsigned type ./@/netiso/tp_usrreq.c:476: warning: statement with no effect ./@/netiso/tp_usrreq.c:496: warning: implicit declaration of function `Dump_buf' ./@/netiso/tp_usrreq.c:498: warning: implicit declaration of function `tp_route_to' ./@/netiso/tp_usrreq.c:524: warning: statement with no effect ./@/netiso/tp_usrreq.c:541: warning: statement with no effect ./@/netiso/tp_usrreq.c:549: warning: implicit declaration of function `tp_confirm' ./@/netiso/tp_usrreq.c:553: warning: statement with no effect ./@/netiso/tp_usrreq.c:558: warning: statement with no effect ./@/netiso/tp_usrreq.c:590: warning: implicit declaration of function `tp_snd_control' ./@/netiso/tp_usrreq.c:635: warning: statement with no effect ./@/netiso/tp_usrreq.c:645: warning: implicit declaration of function `tp_packetize' ./@/netiso/tp_usrreq.c:694: warning: statement with no effect ./@/netiso/tp_usrreq.c: At top level: ./@/netiso/tp_usrreq.c:705: warning: return-type defaults to `int' ./@/netiso/tp_usrreq.c: In function `tp_ltrace': ./@/netiso/tp_usrreq.c:711: warning: statement with no effect ./@/netiso/tp_usrreq.c:715: warning: control reaches end of non-void function ./@/netiso/tp_usrreq.c: At top level: ./@/netiso/tp_usrreq.c:718: warning: return-type defaults to `int' ./@/netiso/tp_usrreq.c:732: warning: return-type defaults to `int' ./@/netiso/tp_usrreq.c: In function `tp_snd_control': ./@/netiso/tp_usrreq.c:743: warning: implicit declaration of function `tp_ctloutput' ./@/netiso/tp_ip.h: At top level: ./@/netiso/tp_ip.h:88: storage size of `tp_inpcb' isn't known From owner-freebsd-current Sun Apr 23 03:07:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA20259 for current-outgoing; Sun, 23 Apr 1995 03:07:14 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA20252 for ; Sun, 23 Apr 1995 03:06:59 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA26362 for current@freebsd.org; Sun, 23 Apr 1995 20:03:35 +1000 Date: Sun, 23 Apr 1995 20:03:35 +1000 From: Bruce Evans Message-Id: <199504231003.UAA26362@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: cvs vs deleted repositories Sender: current-owner@FreeBSD.org Precedence: bulk `cvs update' in /usr/src aborted due to deleted Attics in sys/i386/isa/pcvt and elsewhere. I think the old version of cvs continued after finding such problems. It is annoying for a long update to abort in the middle. Bruce From owner-freebsd-current Sun Apr 23 03:57:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA21582 for current-outgoing; Sun, 23 Apr 1995 03:57:15 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA21576 for ; Sun, 23 Apr 1995 03:57:11 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id DAA03775; Sun, 23 Apr 1995 03:53:52 -0700 From: "Rodney W. Grimes" Message-Id: <199504231053.DAA03775@gndrsh.aac.dev.com> Subject: Re: cvs vs deleted repositories To: bde@zeta.org.au (Bruce Evans) Date: Sun, 23 Apr 1995 03:53:52 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504231003.UAA26362@godzilla.zeta.org.au> from "Bruce Evans" at Apr 23, 95 08:03:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 816 Sender: current-owner@FreeBSD.org Precedence: bulk > > `cvs update' in /usr/src aborted due to deleted Attics in sys/i386/isa/pcvt > and elsewhere. I think the old version of cvs continued after finding such > problems. It is annoying for a long update to abort in the middle. I take it that this happened on your local machine, since FreeFall and all of my tree's updated just fine here. Did you perhaps not use the -P option when you did the cvs co so that actually had these empty directories around in your checked out copy? It should not have even tried to traverse into there unless you failed to use cvs co -P and cvs update -P in the past. If you are not using these options, please reconsider!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun Apr 23 04:36:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA22481 for current-outgoing; Sun, 23 Apr 1995 04:36:25 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA22475 for ; Sun, 23 Apr 1995 04:36:14 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA28184; Sun, 23 Apr 1995 21:32:13 +1000 Date: Sun, 23 Apr 1995 21:32:13 +1000 From: Bruce Evans Message-Id: <199504231132.VAA28184@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: cvs vs deleted repositories Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >> `cvs update' in /usr/src aborted due to deleted Attics in sys/i386/isa/pcvt >> and elsewhere. I think the old version of cvs continued after finding such >> problems. It is annoying for a long update to abort in the middle. >I take it that this happened on your local machine, since FreeFall and >all of my tree's updated just fine here. Did you perhaps not use the -P It happened locally and to old checked out stuff on freefall. >option when you did the cvs co so that actually had these empty directories >around in your checked out copy? >It should not have even tried to traverse into there unless you failed to >use cvs co -P and cvs update -P in the past. If you are not using these >options, please reconsider!! I didn't even know about the -P option but I thought Rod might tell me :-). ... `cvs co -P src/gnu/usr.bin/ogroff' gets rid of all the stub directories in ogroff but not ogroff/CVS. Why isn't -P the default? Bruce From owner-freebsd-current Sun Apr 23 08:50:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA01659 for current-outgoing; Sun, 23 Apr 1995 08:50:25 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA01651 for ; Sun, 23 Apr 1995 08:50:22 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id IAA04244; Sun, 23 Apr 1995 08:47:02 -0700 From: "Rodney W. Grimes" Message-Id: <199504231547.IAA04244@gndrsh.aac.dev.com> Subject: Re: cvs vs deleted repositories To: bde@zeta.org.au (Bruce Evans) Date: Sun, 23 Apr 1995 08:47:02 -0700 (PDT) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199504231132.VAA28184@godzilla.zeta.org.au> from "Bruce Evans" at Apr 23, 95 09:32:13 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1587 Sender: current-owner@FreeBSD.org Precedence: bulk > > >> `cvs update' in /usr/src aborted due to deleted Attics in sys/i386/isa/pcvt > >> and elsewhere. I think the old version of cvs continued after finding such > >> problems. It is annoying for a long update to abort in the middle. > > >I take it that this happened on your local machine, since FreeFall and > >all of my tree's updated just fine here. Did you perhaps not use the -P > > It happened locally and to old checked out stuff on freefall. > > >option when you did the cvs co so that actually had these empty directories > >around in your checked out copy? > > >It should not have even tried to traverse into there unless you failed to > >use cvs co -P and cvs update -P in the past. If you are not using these > >options, please reconsider!! > > I didn't even know about the -P option but I thought Rod might tell me :-). :-) It has been mentioned a few times here and there over the years, but really needs to go into ``Rod's FAQ on using CVS on Freefall and at home''. > ... `cvs co -P src/gnu/usr.bin/ogroff' gets rid of all the stub directories > in ogroff but not ogroff/CVS. That because the remove of . would fail on must systems, so cvs tries to outsmart most systems and does not do ./CVS. If you cd ..; cvs update -P; it would remove ogroff/CVS and even ogroff. > Why isn't -P the default? I thought the same thing when I first figured this out, ask the cvs mailing list, I sure don't know. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun Apr 23 10:30:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02858 for current-outgoing; Sun, 23 Apr 1995 10:30:03 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA02827 for ; Sun, 23 Apr 1995 10:29:38 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA02574; Sun, 23 Apr 1995 19:29:01 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA09357 for current@freebsd.org; Sun, 23 Apr 1995 19:29:00 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id SAA01420 for current@freebsd.org; Sun, 23 Apr 1995 18:38:35 +0200 From: J Wunsch Message-Id: <199504231638.SAA01420@jette.heep.sax.de> Subject: Re: dumb Q. on sendmail To: current@FreeBSD.org Date: Sun, 23 Apr 1995 18:38:32 +0200 (MET DST) Reply-To: current@FreeBSD.org In-Reply-To: <9504212320.AA13507@brasil.moneng.mei.com> from "Joe Greco" at Apr 21, 95 06:20:53 pm Reply-To: joerg_wunsch@uriah.heep.sax.de X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1613 Sender: current-owner@FreeBSD.org Precedence: bulk > Actually, what you *might* want to do is to pass off all your mail to your > ISP, and have their machines deal with it. All you really need to do is > look at Sendmail's examples for "smarthost" delivery, where the local > Sendmail mostly disregards DNS/etc. This is the fix that will probably > serve you best. But the smarthost would not prevent you from the following: While you're actually connected to the net, it's highly probable that there will be several outgoing messages from freefall (e.g.) just within that time. Since freefall can reach your system directly, it will use this link instead of any less-preferrable MX. As the result, while you can upload your batched mails quickly to your smarthost, you'll still have to wait until all _incoming_ SMTP connections will be closed again. This can take forever, since there will be many new connections opened while the existing ones are serviced. If you break the line, the connection will timeout and the mail bounce (since the sender found your system reachable for some time, and hence didn't fall back to an MX). Why can't you use UUCP for this? It _is_ already batched, and you can run it separately as well as ``in background'' via TCP while your IP connection is up. Your provider must be the best MX for your machine, while the machine itself is not mentioned as an MX for itself. This way, sending smtp's should never use the A record directly (some old mailers do however). Your provider could then use a mailertable to decide where outgoing uucp connections will be fed to. The above is what i'm using regularly here. J"org From owner-freebsd-current Sun Apr 23 14:13:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07442 for current-outgoing; Sun, 23 Apr 1995 14:13:43 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA07436 ; Sun, 23 Apr 1995 14:13:36 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id XAA01216; Sun, 23 Apr 1995 23:12:34 +0200 From: John Hay Message-Id: <199504232112.XAA01216@zibbi.mikom.csir.co.za> Subject: make libc dies To: current@FreeBSD.org (FreeBSD-current), ache@FreeBSD.org Date: Sun, 23 Apr 1995 23:12:34 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 204 Sender: current-owner@FreeBSD.org Precedence: bulk I think the setregid changes to libc are not finnished yet. Shouldn't setregid.c and setreuid.c be removed from libc/compat-43/Makefile.inc? Or am I too impatient:) -- John Hay -- jhay@mikom.csir.co.za From owner-freebsd-current Sun Apr 23 14:16:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07478 for current-outgoing; Sun, 23 Apr 1995 14:16:22 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA07472 for ; Sun, 23 Apr 1995 14:16:20 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id WAA02198 for FreeBSD-current@FreeBSD.org; Sun, 23 Apr 1995 22:17:34 +0100 From: Paul Richards Message-Id: <199504232117.WAA02198@isl.cf.ac.uk> Subject: Switching vty's from software? To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Sun, 23 Apr 1995 22:17:33 +0100 (BST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 703 Sender: current-owner@FreeBSD.org Precedence: bulk Is there a way to switch vty's from software. If not can it be added. I want to add a feature to libforms that allows you to have two forms running on different vtys and then allow the app to switch between them. Displaying the forms on several vtys is not a problem, passing control from one form to another isn't either but it's a bit cludgy to have libforms pass control to a form on another vty and then require the user to have to manually change vty. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Sun Apr 23 15:38:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA12532 for current-outgoing; Sun, 23 Apr 1995 15:38:57 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA12525 for ; Sun, 23 Apr 1995 15:38:52 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA06722; Mon, 24 Apr 1995 00:38:49 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA11028; Mon, 24 Apr 1995 00:38:48 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id AAA02772; Mon, 24 Apr 1995 00:27:31 +0200 From: J Wunsch Message-Id: <199504232227.AAA02772@jette.heep.sax.de> Subject: Re: Switching vty's from software? To: paul@isl.cf.ac.uk (Paul Richards) Date: Mon, 24 Apr 1995 00:27:28 +0200 (MET DST) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: <199504232117.WAA02198@isl.cf.ac.uk> from "Paul Richards" at Apr 23, 95 10:17:33 pm Reply-To: joerg_wunsch@uriah.heep.sax.de X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 624 Sender: current-owner@FreeBSD.org Precedence: bulk > > Is there a way to switch vty's from software. If not can it be added. ioctl(fd, VT_ACTIVATE, vt_no); Note that vt_no is 1-based. Works with both, syscons and pcvt, for the latter only if compiled with XSERVER support enabled. I don't think there's a man page covering syscons. pcvt omits the USL-style VT compatibility commands in its man page, since they are considered to be compatibility cruft only. They do not fully fit into the berkeley ioctl style (e.g., they do not take an int* as their third argument, but rather the int itself). Remember, that libforms could also be run off a plain VT100. :-) Jörg From owner-freebsd-current Sun Apr 23 15:47:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA12640 for current-outgoing; Sun, 23 Apr 1995 15:47:00 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA12634 for ; Sun, 23 Apr 1995 15:46:56 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id XAA02523; Sun, 23 Apr 1995 23:47:10 +0100 From: Paul Richards Message-Id: <199504232247.XAA02523@isl.cf.ac.uk> Subject: Re: Switching vty's from software? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 23 Apr 1995 23:47:10 +0100 (BST) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: <199504232227.AAA02772@jette.heep.sax.de> from "J Wunsch" at Apr 24, 95 00:27:28 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 624 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > > > > Is there a way to switch vty's from software. If not can it be added. > > ioctl(fd, VT_ACTIVATE, vt_no); > > Note that vt_no is 1-based. Great. > > Remember, that libforms could also be run off a plain VT100. :-) > libforms isn't quite what it used to be. Wait and see :-) It'll still run on anything that supports ncurses though. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Sun Apr 23 18:14:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15690 for current-outgoing; Sun, 23 Apr 1995 18:14:42 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA15682 ; Sun, 23 Apr 1995 18:14:41 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Paul Richards cc: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Subject: Re: Switching vty's from software? In-reply-to: Your message of "Sun, 23 Apr 95 22:17:33 BST." <199504232117.WAA02198@isl.cf.ac.uk> Date: Sun, 23 Apr 1995 18:14:41 -0700 Message-ID: <15681.798686081@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Is there a way to switch vty's from software. If not can it be added. Open the VTY you want and do an ioctl on it! :-) Jordan From owner-freebsd-current Sun Apr 23 23:07:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA23508 for current-outgoing; Sun, 23 Apr 1995 23:07:46 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA23502 for ; Sun, 23 Apr 1995 23:07:43 -0700 Received: by pelican.com (Smail3.1.28.1 #5) id m0s3HJ7-000K0iC; Sun, 23 Apr 95 23:07 WET DST Message-Id: Date: Sun, 23 Apr 95 23:07 WET DST From: pete@pelican.com (Pete Carah) To: current@FreeBSD.org Subject: Re: bin/358: incorrect argument handling in "dump" In-Reply-To: <199504232109.XAA02387@jette.heep.sax.de> Organization: Pelican Consulting Sender: current-owner@FreeBSD.org Precedence: bulk In article <199504232109.XAA02387@jette.heep.sax.de> you write: >> >Synopsis: incorrect argument handling in "dump" >> >Description: >> The command "dump -0cu -b 8 -B 349525 -f /dev/nrst0 /" gives >> an error of "Unknown arguments to dump: 8 -B 349525 -f /dev/nrst0 /". >This is not expected to work. dump is a really old program with a >very specific syntax (same boat as `dd'). At least the 'dd' syntax somewhat resembles that of the card of the same name :-) (yes, I used to be the local jcl guru too...) -- Pete From owner-freebsd-current Mon Apr 24 04:36:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA01654 for current-outgoing; Mon, 24 Apr 1995 04:36:10 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA01648 ; Mon, 24 Apr 1995 04:36:09 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: dyson@freefall.cdrom.com cc: current@freefall.cdrom.com Subject: mmap panics still Date: Mon, 24 Apr 1995 04:36:09 -0700 Message-ID: <1647.798723369@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk Hi Satoshi jsut tried the same program on thud, and it still panic'd the kernel, although the message was different this time. Apr 24 02:47:57 thud savecore: reboot after panic: lockholder (%d) != 0 thud# kgdb ./kernel Reading symbol data from /d/local/src/sys/compile/THUDG/kernel...done. (kgdb) core-file /var/crash/vmcore.2 IdlePTD 1df000 panic: lockholder (%d) != 0 current pcb at 1d0ad0 Reading in symbols for ../../i386/i386/machdep.c...done. (kgdb) bt #0 boot (arghowto=260) (../../i386/i386/machdep.c line 869) #1 0xf0117bc5 in panic (...) #2 0xf0101311 in db_panic (...) #3 0xf01011fa in db_command (...) #4 0xf0101379 in db_command_loop (...) #5 0xf0103e3c in db_trap (...) #6 0xf01a3d0e in kdb_trap (...) #7 0xf01ab348 in trap (...) #8 0xf01a45d1 in exception:calltrap () #9 0xf0117bbf in panic (...) #10 0xf0192686 in ufs_lock (...) #11 0xf01a214d in vnode_pager_lock (...) #12 0xf0195ee4 in vm_fault (...) #13 0xf01ab5c7 in trap_pfault (...) #14 0xf01ab2c7 in trap (...) #15 0xf01a45d1 in exception:calltrap () #16 0xf0185535 in ffs_read (...) #17 0xf01329d2 in vn_read (...) #18 0xf0118d83 in read (...) #19 0xf01abcc3 in syscall (...) Any ideas? This was with a kernel compiled AFTER John's fixes to mmap() Gary From owner-freebsd-current Mon Apr 24 07:13:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA05599 for current-outgoing; Mon, 24 Apr 1995 07:13:26 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA05590 ; Mon, 24 Apr 1995 07:13:16 -0700 Received: (dyson@localhost) by Root.COM (8.6.8/8.6.5) id HAA10722; Mon, 24 Apr 1995 07:13:12 -0700 Date: Mon, 24 Apr 1995 07:13:12 -0700 From: John Dyson Message-Id: <199504241413.HAA10722@Root.COM> To: dyson@freefall.cdrom.com, gpalmer@freefall.cdrom.com Subject: Re: mmap panics still Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk I'll work on it tonite... John dyson@root.com From owner-freebsd-current Mon Apr 24 07:53:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA06674 for current-outgoing; Mon, 24 Apr 1995 07:53:15 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA06668 for ; Mon, 24 Apr 1995 07:53:12 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id KAA11634; Mon, 24 Apr 1995 10:52:09 -0400 From: Peter Dufault Message-Id: <199504241452.KAA11634@hda.com> Subject: Any install for me to test? To: freebsd-current@freefall.cdrom.com Date: Mon, 24 Apr 1995 10:52:09 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 562 Sender: current-owner@FreeBSD.org Precedence: bulk I have to install a FreeBSD system today. I have an old install floppy that I can use to get things started, and then I'll just switch over to doing it by hand. However, if there are some new install floppies I should test I'll be happy to. Since ftp.cdrom.com is down I have no idea where I should pick them up from. If someone gets back to me in a few hours I'll test the new floppies. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Mon Apr 24 07:59:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07022 for current-outgoing; Mon, 24 Apr 1995 07:59:19 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA07013 ; Mon, 24 Apr 1995 07:59:17 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Peter Dufault cc: freebsd-current@freefall.cdrom.com Subject: Re: Any install for me to test? In-reply-to: Your message of "Mon, 24 Apr 95 10:52:09 EDT." <199504241452.KAA11634@hda.com> Date: Mon, 24 Apr 1995 07:59:16 -0700 Message-ID: <7011.798735556@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504241452.KAA11634@hda.com>, Peter Dufault writes: >Since ftp.cdrom.com is down I have no idea where I should pick them up from. ftp://freebsd.org/pub/FreeBSD/2.0-950412-SNAP/floppies Gary From owner-freebsd-current Mon Apr 24 08:15:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA07512 for current-outgoing; Mon, 24 Apr 1995 08:15:53 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA07505 for ; Mon, 24 Apr 1995 08:15:49 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id JAA04485; Mon, 24 Apr 1995 09:19:03 -0600 Date: Mon, 24 Apr 1995 09:19:03 -0600 From: Nate Williams Message-Id: <199504241519.JAA04485@trout.sri.MT.net> In-Reply-To: "Rodney W. Grimes" "Re: cvs vs deleted repositories" (Apr 23, 8:47am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" , bde@zeta.org.au (Bruce Evans) Subject: Re: cvs vs deleted repositories Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk [ Making -Pd the default for cvs update ] > > Why isn't -P the default? > > I thought the same thing when I first figured this out, ask the cvs > mailing list, I sure don't know. This came up on the mailing lists this weekend, so I sent out a query to the maintainers on '-P' and '-d' not being the defaults (-d should be the default on non-branch revisions IMHO) so I hope to hear something from the maintainers. Nate From owner-freebsd-current Mon Apr 24 08:23:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA07782 for current-outgoing; Mon, 24 Apr 1995 08:23:14 -0700 Received: from zibbi.mikom.csir.co.za (some.schmuck.lame.delegated.to.RAIN.PSG.COM [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA07769 for ; Mon, 24 Apr 1995 08:22:55 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id RAA06382 for current@FreeBSD.ORG; Mon, 24 Apr 1995 17:21:47 +0200 From: John Hay Message-Id: <199504241521.RAA06382@zibbi.mikom.csir.co.za> Subject: libc don't make To: current@FreeBSD.org (FreeBSD-current) Date: Mon, 24 Apr 1995 17:21:46 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1410 Sender: current-owner@FreeBSD.org Precedence: bulk The last changes to libc broke it:( Setregid and setreuid don't exist in compat-43 anymore. Here is a fix for compat-43/Makefile.inc to fix it. Something that bothers me is that setregid.2 and setreuid.2 don't show up in my Attic directory. It look like they were directly moved to libc/sys. Is that the correct way to do it? Won't that break if a checkout of a previous TAG is done? -- John Hay -- jhay@mikom.csir.co.za *** src/lib/libc/compat-43/Makefile.inc.org Sun Aug 28 19:08:36 1994 --- src/lib/libc/compat-43/Makefile.inc Mon Apr 24 17:09:13 1995 *************** *** 4,14 **** .PATH: ${.CURDIR}/${MACHINE}/compat-43 ${.CURDIR}/compat-43 SRCS+= creat.c gethostid.c getwd.c killpg.c sethostid.c setpgrp.c \ ! setregid.c setreuid.c setrgid.c setruid.c sigcompat.c MAN2+= compat-43/creat.2 compat-43/killpg.2 \ ! compat-43/setregid.2 compat-43/setreuid.2 compat-43/sigblock.2 \ ! compat-43/sigpause.2 compat-43/sigsetmask.2 compat-43/sigvec.2 MAN3+= compat-43/gethostid.3 compat-43/setruid.3 --- 4,14 ---- .PATH: ${.CURDIR}/${MACHINE}/compat-43 ${.CURDIR}/compat-43 SRCS+= creat.c gethostid.c getwd.c killpg.c sethostid.c setpgrp.c \ ! setrgid.c setruid.c sigcompat.c MAN2+= compat-43/creat.2 compat-43/killpg.2 \ ! compat-43/sigblock.2 compat-43/sigpause.2 \ ! compat-43/sigsetmask.2 compat-43/sigvec.2 MAN3+= compat-43/gethostid.3 compat-43/setruid.3 From owner-freebsd-current Mon Apr 24 08:31:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA07960 for current-outgoing; Mon, 24 Apr 1995 08:31:25 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA07954 for ; Mon, 24 Apr 1995 08:31:22 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id IAA06117; Mon, 24 Apr 1995 08:27:36 -0700 From: "Rodney W. Grimes" Message-Id: <199504241527.IAA06117@gndrsh.aac.dev.com> Subject: Re: libc don't make To: jhay@mikom.csir.co.za (John Hay) Date: Mon, 24 Apr 1995 08:27:36 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504241521.RAA06382@zibbi.mikom.csir.co.za> from "John Hay" at Apr 24, 95 05:21:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 745 Sender: current-owner@FreeBSD.org Precedence: bulk > > The last changes to libc broke it:( Setregid and setreuid don't exist in > compat-43 anymore. Here is a fix for compat-43/Makefile.inc to fix it. > > Something that bothers me is that setregid.2 and setreuid.2 don't show up > in my Attic directory. It look like they were directly moved to libc/sys. > Is that the correct way to do it? Won't that break if a checkout of a previous > TAG is done? ARGHH!!! Did someone go into the repository and move and/or copy files around. If so will that person please contact me via private email ASAP and before doing ANYTHING on Freefall. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Mon Apr 24 08:58:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA08409 for current-outgoing; Mon, 24 Apr 1995 08:58:44 -0700 Received: from zibbi.mikom.csir.co.za (some.schmuck.lame.delegated.to.RAIN.PSG.COM [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA08403 for ; Mon, 24 Apr 1995 08:58:37 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id RAA06514 for current@FreeBSD.ORG; Mon, 24 Apr 1995 17:57:20 +0200 From: John Hay Message-Id: <199504241557.RAA06514@zibbi.mikom.csir.co.za> Subject: screensavers don't make anymore To: current@FreeBSD.org (FreeBSD-current) Date: Mon, 24 Apr 1995 17:57:20 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 753 Sender: current-owner@FreeBSD.org Precedence: bulk After the changes to cons.h the screensavers won't compile anymore: cc -O2 -DLKM -I/usr/src/lkm/syscons/blank/.. -I/usr/src/lkm/syscons/blank/../../../sys -DKERNEL -I/usr/src/lkm/syscons/blank/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/syscons/blank/blank_saver.c In file included from /usr/src/lkm/syscons/blank/../saver.h:7, from /usr/src/lkm/syscons/blank/blank_saver.c:38: /usr/src/lkm/syscons/blank/../../../sys/i386/i386/cons.h:56: sc.h: No such file or directory /usr/src/lkm/syscons/blank/../../../sys/i386/i386/cons.h:57: vt.h: No such file or directory /usr/src/lkm/syscons/blank/../../../sys/i386/i386/cons.h:66: sio.h: No such file or directory *** Error code 1 Stop. -- John Hay -- jhay@mikom.csir.co.za From owner-freebsd-current Mon Apr 24 09:15:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA08849 for current-outgoing; Mon, 24 Apr 1995 09:15:11 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA08843 for ; Mon, 24 Apr 1995 09:15:08 -0700 Received: from muzak by devnull.mpd.tandem.com (8.6.8/8.6.6) id LAA17950; Mon, 24 Apr 1995 11:14:53 -0500 Received: by muzak (4.1/TSS2.1) id AA09465; Mon, 24 Apr 95 11:15:05 CDT From: chain@mpd.tandem.com (Chain Lee) Message-Id: <9504241615.AA09465@muzak> Subject: Re: 950412-SNAP To: current@FreeBSD.org Date: Mon, 24 Apr 1995 11:15:04 -0500 (CDT) Cc: chain%muzak.mpd.tandem.com@mpd.tandem.com (Chain Lee) In-Reply-To: <9504201906.AA08080@muzak> from "Chain Lee" at Apr 20, 95 02:06:34 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 10094 Sender: current-owner@FreeBSD.org Precedence: bulk I said, > 2) My 'diskless' station has only a DOS partition and no FreeBSD > partition in a wd0 (ST506). It panics during diskless boot. I traced > down the panic to wdopen which was getting an integer division fault. > The trace is as follows: > configure() > swapconf() > wdsize() > wdopen() > ---idiv fault > Is this a known problem? I got around the problem by bypassing wdopen() > but wasn't able to trace further down because no symbols were loaded > into the kernel, and ddb trace shows no names. I modified netboot to > load symbol table over the net but it seems to have no effect. What > other things do I need to do to get the symbol table loaded into ddb? I've made a few small modifications to netboot to do the following: 1) Get wd0 disk geometry from bios and load bootinfo that includes disk geometry, so wd* driver can make use of it when fails to read from disk, rather than panic. 2) Load symbol tabel across the net so ddb works on diskless configuarion. 3) Build a mini netboot kernel that can be loaded by bios-boot, and then starts a 'diskless' boot. I am really hoping these features (mostly from biosboot) be included in the standard netboot so I don't have to change it later myself. I attached patched at the end. Also wd0 may need to be fixed so wdattach will fail if disk geometry cannot be obtained, rather than succeeds and later panics in wdopen when invalid geometry is used in calculation. Regards, -chain *** 1.1 1995/04/19 00:48:12 --- main.c 1995/04/23 15:04:03 *************** *** 33,39 **** **************************************************************************/ main() { ! int c; char *p; extern char edata[], end[]; for (p=edata; p 0) { + read_size = head.a_syms > NFS_READ_SIZE ? + NFS_READ_SIZE : head.a_syms; + if ((err = nfs_read(ARP_ROOTSERVER, root_nfs_port, + &kernel_handle, offset, read_size, loadpoint)) != + read_size) { + if (err < 0) { + printf("Unable to read symble table: "); + nfs_err(err); + } + longjmp(jmp_bootmenu, 1); + } + loadpoint += err; + head.a_syms -= err; + offset += err; + } + + /********************************************************/ + /* Load the string table size */ + /********************************************************/ + if ((err = nfs_read(ARP_ROOTSERVER, root_nfs_port, &kernel_handle, + offset, sizeof(int), &i)) < 0) { + printf("Unable to read %s: ",kernel); + nfs_err(err); + longjmp(jmp_bootmenu,1); + } + offset += err; + *((int *)loadpoint) = i; + i -= sizeof(int); + loadpoint += sizeof(int); + + /********************************************************/ + /* Load the string table */ + /********************************************************/ + printf("+0x%x+0x%x] ", sizeof(int), i); + while (i > 0) { + read_size = i > NFS_READ_SIZE ? + NFS_READ_SIZE : i; + if ((err = nfs_read(ARP_ROOTSERVER, root_nfs_port, + &kernel_handle, offset, read_size, loadpoint)) != + read_size) { + if (err < 0) { + printf("Unable to read string table: "); + nfs_err(err); + } + longjmp(jmp_bootmenu, 1); + } + loadpoint += err; + i -= err; + offset += err; + } + + bootinfo.bi_esymtab = (unsigned long)loadpoint; + printf("entry=0x%X.\n\r",head.a_entry); /* Jump to kernel */ bootinfo.bi_version = BOOTINFO_VERSION; bootinfo.bi_kernelname = kernel; bootinfo.bi_nfs_diskless = &nfsdiskless; + bootinfo.bi_size = sizeof(bootinfo); kernelentry = (void *)(head.a_entry & 0x00FFFFFF); ! (*kernelentry)(RB_BOOTINFO,NODEV,0,0,0,&bootinfo,0,0,0); printf("*** %s execute failure ***\n",kernel); } *** 1.1 1995/04/19 01:22:02 --- start2.S 1995/04/24 11:02:25 *************** *** 54,59 **** --- 54,64 ---- START - Where all the fun begins.... **************************************************************************/ .globl _start + #ifdef BOOTNET + _start: + lgdt gdtarg + call _prot_to_real + #else _start: cli cld *************** *** 74,79 **** --- 79,85 ---- movsb opsize ljmp $(RELOC>>4),$1f-RELOC /* Jmp to RELOC:1f */ + #endif 1: nop mov %cs,%ax *************** *** 330,332 **** --- 336,407 ---- gdtarg: .word 0x1f /* limit */ .long gdt /* addr */ + + /* + * + * get_diskinfo(): return a word that represents the + * max number of sectors and heads and drives for this device + * + */ + + .globl _get_diskinfo + _get_diskinfo: + push %ebp + mov %esp, %ebp + push %es + push %ebx + push %ecx + push %edx + + movb 0x8(%ebp), %dl /* diskinfo(drive #) */ + call _prot_to_real /* enter real mode */ + + movb $0x8, %ah /* ask for disk info */ + + sti + int $0x13 + cli + + jnc ok + /* + * Urk. Call failed. It is not supported for floppies by old BIOS's. + * Guess it's a 15-sector floppy. + */ + subb %ah, %ah /* %ax = 0 */ + movb %al, %al + movb %ah, %bh /* %bh = 0 */ + movb $2, %bl /* %bl bits 0-3 = drive type, + bit 2 = 1.2M */ + movb $79, %ch /* max track */ + movb $15, %cl /* max sector */ + movb $1, %dh /* max head */ + movb $1, %dl /* # floppy drives installed */ + /* es:di = parameter table */ + /* carry = 0 */ + ok: + opsize + call _real_to_prot /* back to protected mode */ + + /* + * form a longword representing all this gunk: + * 6 bit zero + * 10 bit cylinder + * 8 bit head + * 8 bit sector + */ + movb %cl, %al /* Upper two bits of cylinder count */ + andl $192,%eax + leal 0(,%eax,4),%eax /* << 2 */ + movb %ch, %al /* Lower 8 bits */ + sall $16,%eax /* << 16 */ + movb %dh, %ah /* max head */ + andb $0x3f, %cl /* mask of cylinder gunk */ + movb %cl, %al /* max sector (and # sectors) */ + + pop %edx + pop %ecx + pop %ebx + pop %es + pop %ebp + ret + *** 1.1 1995/04/21 23:33:26 --- Makefile 1995/04/23 15:12:43 *************** *** 19,31 **** # changing an option. # ! PROG= nb8390.com nb3c509.com nb8390.rom nb3c509.rom # Order is very important on the SRCS line for this prog SRCS= start2.S main.c misc.c bootmenu.c rpc.c BINDIR= /usr/mdec BINMODE= 555 ! CFLAGS= -O2 -DNFS -DROMSIZE=${ROMSIZE} -DRELOC=${RELOCADDR} -DASK_BOOT #NS8390= -DINCLUDE_WD -DWD_DEFAULT_MEM=0xD0000 NS8390+= -DINCLUDE_NE -DNE_BASE=0x340 #NS8390+= -DINCLUDE_3COM -D_3COM_BASE=0x300 --- 19,32 ---- # changing an option. # ! PROG= nb8390.com nb3c509.com nb8390.rom nb3c509.rom \ ! nb8390.kernel nb3c509.kernel # Order is very important on the SRCS line for this prog SRCS= start2.S main.c misc.c bootmenu.c rpc.c BINDIR= /usr/mdec BINMODE= 555 ! CFLAGS= -O2 -DNFS -DROMSIZE=${ROMSIZE} -DRELOC=${RELOCADDR} # -DASK_BOOT #NS8390= -DINCLUDE_WD -DWD_DEFAULT_MEM=0xD0000 NS8390+= -DINCLUDE_NE -DNE_BASE=0x340 #NS8390+= -DINCLUDE_3COM -D_3COM_BASE=0x300 *************** *** 39,49 **** ROMSIZE=16384 RELOCADDR=0x90000 ! .SUFFIXES: .ro .S.ro: ${CC} ${CFLAGS} -DBOOTROM -o ${.TARGET} -c ${.IMPSRC} ns8390.o: ns8390.c ${CC} $(CFLAGS) $(NS8390) -o ${.TARGET} -c $< --- 40,53 ---- ROMSIZE=16384 RELOCADDR=0x90000 ! .SUFFIXES: .ro .no .S.ro: ${CC} ${CFLAGS} -DBOOTROM -o ${.TARGET} -c ${.IMPSRC} + .S.no: + ${CC} ${CFLAGS} -DBOOTNET -o ${.TARGET} -c ${.IMPSRC} + ns8390.o: ns8390.c ${CC} $(CFLAGS) $(NS8390) -o ${.TARGET} -c $< *************** *** 74,78 **** --- 78,87 ---- size netboot.com dd ibs=32 skip=1 if=netboot.com of=${.TARGET} + nb8390.kernel: start2.no ${SRCS:N*.h:R:S/$/.o/g} ns8390.o + $(LD) -Bstatic -Z -T ${RELOCADDR} -o $@ -X ${OBJS:S/start2.o/start2.no/} ns8390.o + + nb3c509.kernel: start2.no ${SRCS:N*.h:R:S/$/.o/g} 3c509.o + $(LD) -Bstatic -Z -T ${RELOCADDR} -o $@ -X ${OBJS:S/start2.o/start2.no/} 3c509.o .include -- Chain Lee Tandem Computers, Inc. Voice: (512) 432-8969 14231 Tandem Boulevard Email: chain@isd.tandem.com Austin, TX 78728-6699 Office: 2359 From owner-freebsd-current Mon Apr 24 09:23:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA09067 for current-outgoing; Mon, 24 Apr 1995 09:23:03 -0700 Received: from irbs.com (irbs.com [199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA09059 for ; Mon, 24 Apr 1995 09:23:00 -0700 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id MAA01623; Mon, 24 Apr 1995 12:22:44 -0400 From: John Capo Message-Id: <199504241622.MAA01623@irbs.com> Subject: Re: libc don't make To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 24 Apr 1995 12:22:43 -0400 (EDT) Cc: freebsd-current@freefall.cdrom.com (freebsd-current) In-Reply-To: <199504241527.IAA06117@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 24, 95 08:27:36 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 852 Sender: current-owner@FreeBSD.org Precedence: bulk In addition to other things. cc -O -m486 -pipe -I/u1/usr/src/gnu/usr.bin/man/man/../lib/obj -I/u1/usr/src/gnu/usr.bin/man/man/../lib -DSTDC_HEADERS -DPOSIX -DHAS_TROFF -DDO_COMPRESS -DALT_SYSTEMS -DSETREUID -DCATMODE=0664 -o man man.o manpath.o glob.o -L/u1/usr/src/gnu/usr.bin/man/man/../lib/obj -lman man.o: Undefined symbol `_setreuid' referenced from text segment man.o: Undefined symbol `_setregid' referenced from text segment man.o: Undefined symbol `_setreuid' referenced from text segment man.o: Undefined symbol `_setregid' referenced from text segment man.o: Undefined symbol `_setreuid' referenced from text segment man.o: Undefined symbol `_setregid' referenced from text segment /usr/lib/libc.so.2.1: Undefined symbol `_setreuid' referenced /usr/lib/libc.so.2.1: Undefined symbol `_setregid' referenced *** Error code 1 John Capo From owner-freebsd-current Mon Apr 24 09:47:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA09989 for current-outgoing; Mon, 24 Apr 1995 09:47:18 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA09983 for ; Mon, 24 Apr 1995 09:47:06 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA04748; Tue, 25 Apr 1995 02:41:56 +1000 Date: Tue, 25 Apr 1995 02:41:56 +1000 From: Bruce Evans Message-Id: <199504241641.CAA04748@godzilla.zeta.org.au> To: current@FreeBSD.org, jhay@mikom.csir.co.za Subject: Re: screensavers don't make anymore Sender: current-owner@FreeBSD.org Precedence: bulk >After the changes to cons.h the screensavers won't compile anymore: >cc -O2 -DLKM -I/usr/src/lkm/syscons/blank/.. -I/usr/src/lkm/syscons/blank/../../../sys -DKERNEL -I/usr/src/lkm/syscons/blank/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/syscons/blank/blank_saver.c >In file included from /usr/src/lkm/syscons/blank/../saver.h:7, > from /usr/src/lkm/syscons/blank/blank_saver.c:38: >/usr/src/lkm/syscons/blank/../../../sys/i386/i386/cons.h:56: sc.h: No such file or directory I will fix this in a minute. Bruce From owner-freebsd-current Mon Apr 24 11:51:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA12619 for current-outgoing; Mon, 24 Apr 1995 11:51:10 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA12612 for ; Mon, 24 Apr 1995 11:51:09 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA02945; Mon, 24 Apr 95 13:50:37 CDT From: Joe Greco Message-Id: <9504241850.AA02945@brasil.moneng.mei.com> Subject: Re: dumb Q. on sendmail To: current@FreeBSD.org Date: Mon, 24 Apr 1995 13:50:37 -0500 (CDT) In-Reply-To: <199504231638.SAA01420@jette.heep.sax.de> from "J Wunsch" at Apr 23, 95 06:38:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 904 Sender: current-owner@FreeBSD.org Precedence: bulk > But the smarthost would not prevent you from the following: > > While you're actually connected to the net, it's highly probable > that there will be several outgoing messages from freefall (e.g.) > just within that time. Since freefall can reach your system > directly, it will use this link instead of any less-preferrable > MX. As the result, while you can upload your batched mails quickly ...which is, obviously, why you do not advertise your machine with a more preferable MX. :-) Or, for that matter, at all. Let your ISP do some work on your behalf, rather than just letting them suck up the contents of your wallet. :-) They should be more than willing to queue your mail. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Mon Apr 24 12:38:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA14313 for current-outgoing; Mon, 24 Apr 1995 12:38:10 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA14307 for ; Mon, 24 Apr 1995 12:38:09 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id MAA18981 for ; Mon, 24 Apr 1995 12:38:06 -0700 Message-Id: <199504241938.MAA18981@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: Resolver wierdness Date: Mon, 24 Apr 1995 12:38:06 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk I have the following for my resolv.conf: domain CS.Berkeley.EDU nameserver 128.32.42.47 nameserver 128.32.136.9 nameserver 128.32.136.12 search CS.Berkeley.EDU EECS.Berkeley.EDU CSUA.Berkeley.EDU Berkeley.EDU HIP.Berk eley.EDU Recently the first server's named died so I began to resolve through 128.32.136.9. The funny thing was that during that time, lookups for non-fully-qualified hostnames would fail for say a telnet or a ping, but nslookup would resolve them fine. Does any one know why? As soon as the first DNS machine got its named restarted, all resolving occured normally. __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Mon Apr 24 12:40:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA14370 for current-outgoing; Mon, 24 Apr 1995 12:40:38 -0700 Received: from mailman.bdeoss.com (root@[129.54.4.242]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA14362 for ; Mon, 24 Apr 1995 12:40:34 -0700 Received: by mailman with Microsoft Mail id <2F9BFE28@mailman>; Mon, 24 Apr 95 12:38:16 PDT From: "Paul, Chris bd 6-6487" To: bsdcurrent Date: Mon, 24 Apr 95 12:19:00 PDT Message-ID: <2F9BFE28@mailman> Encoding: 22 TEXT X-Mailer: Microsoft Mail V3.0 Sender: current-owner@FreeBSD.org Precedence: bulk Hello, I am new to BSD and UNIX, but I'm a quick learner, so please bear with me. I just downloaded the 2.0-950412-SNAP release. I know that I shouldn't be looking for current or snapshot releases for bug-fixes, but 2.0-RELEASE did not support my Adaptec AIC 7870 onboard SCSI controller. I was very happy when my 2.0-950412-SNAP boot disk saw my SCSI bus and I could Fdisk and label my partitions. However, when I get to the bin installation procedure and ftp the files over to /usr/tmp, the checksum routine fails. I don't think the checksums are the problem, as it responds too quickly without doing any work and I should have had problems unzipping them if the files were corrupt. Does anyone have any clues? Christopher Paul bd Systems MIS Vandenberg AFB, CA From owner-freebsd-current Mon Apr 24 14:26:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA17618 for current-outgoing; Mon, 24 Apr 1995 14:26:16 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA17546 for ; Mon, 24 Apr 1995 14:25:05 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA06457; Mon, 24 Apr 1995 23:24:24 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA18672 for current@freebsd.org; Mon, 24 Apr 1995 23:24:23 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id WAA04428 for current@freebsd.org; Mon, 24 Apr 1995 22:38:07 +0200 From: J Wunsch Message-Id: <199504242038.WAA04428@jette.heep.sax.de> Subject: Re: bin/358: incorrect argument handling in "dump" To: current@FreeBSD.org Date: Mon, 24 Apr 1995 22:38:04 +0200 (MET DST) Reply-To: current@FreeBSD.org In-Reply-To: from "Pete Carah" at Apr 23, 95 11:07:00 pm Reply-To: joerg_wunsch@uriah.heep.sax.de X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 376 Sender: current-owner@FreeBSD.org Precedence: bulk > >This is not expected to work. dump is a really old program with a > >very specific syntax (same boat as `dd'). > At least the 'dd' syntax somewhat resembles that of the card of the > same name :-) > (yes, I used to be the local jcl guru too...) While i kept my fingers away from JCL:), i could argue that the dd syntax is also resembling the OS-9 command syntax... Jörg From owner-freebsd-current Mon Apr 24 17:33:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA01204 for current-outgoing; Mon, 24 Apr 1995 17:33:40 -0700 Received: from fgwmail.fujitsu.co.jp (fgwmail.fujitsu.co.jp [164.71.1.133]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA01193 for ; Mon, 24 Apr 1995 17:33:34 -0700 Received: from fdmmail.fujitsu.co.jp by fgwmail.fujitsu.co.jp (8.6.12+2.4W/3.3W5-MX941209-Fujitsu Mail Gateway) id JAA02140; Tue, 25 Apr 1995 09:33:25 +0900 Received: from fdm.fujitsu.co.jp by fdmmail.fujitsu.co.jp (8.6.12+2.4W/3.3W5-MX950127-Fujitsu Domain Mail Master) id JAA26452; Tue, 25 Apr 1995 09:32:53 +0900 Received: from sysrap by fdm.fujitsu.co.jp (5.65/6.4J.6) id AA09062; Tue, 25 Apr 95 09:32:52 +0900 Received: from seki.sysrap.cs.fujitsu.co.jp by spad.sysrap.cs.fujitsu.co.jp with smtp (Smail3.1.28.1 #1) id m0s3Yg1-0002tnC; Tue, 25 Apr 95 09:40 JST Date: Tue, 25 Apr 95 09:28:46 JST From: Masahiro SEKIGUCHI Message-Id: <9504250028.AA04081@seki.sysrap.cs.fujitsu.co.jp> To: Cc: bsdcurrent Subject: 950412 SNAP ftp install (was: "") References: <2F9BFE28@mailman> Sender: current-owner@FreeBSD.org Precedence: bulk >However, when I get to the bin >installation procedure and ftp the files over to /usr/tmp, the checksum >routine fails. I don't think the checksums are the problem, as it responds >too quickly without doing any work I experienced similar case. When I met it, I found that the "status" screen (Alt-F2) showed the following messages: NcFTP: Could not get your passwd entry! (9): Bad file descriptor Login failed After some investigation, I found the following facts: My system had no "/etc/passwd" at the momemt. (This should be the reason NcFTP could not get the passwd entry...) I accessed a local ftp site to get bindist. The site runs a non-standard version of ftp srever. The server performs a "strict checking" on an email address sent as a password for an anonymous user. The server had logged that anonymous ftp requests from my machine had been rejected because of "invalid" mail addresses as passwords. The mail address NcFTP sent started with '@' -- no local part in the address. I invoked usual ftp, typed in my real email address, and then fetched bindist manually. This sounds like a bug of some kind... but I'm slightly confused now, because I found the ftp install sometimes success with the same boot floppy and the same ftp site. Hope this helps, anyway. From owner-freebsd-current Mon Apr 24 18:16:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03398 for current-outgoing; Mon, 24 Apr 1995 18:16:24 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA03387 ; Mon, 24 Apr 1995 18:16:19 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Masahiro SEKIGUCHI cc: PaulC@mef.bdeoss.com, bsdcurrent Subject: Re: 950412 SNAP ftp install (was: "") In-reply-to: Your message of "Tue, 25 Apr 95 09:28:46 +0200." <9504250028.AA04081@seki.sysrap.cs.fujitsu.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 24 Apr 1995 18:16:18 -0700 Message-ID: <3386.798772578@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > I accessed a local ftp site to get bindist. > > The site runs a non-standard version of ftp srever. > > The server performs a "strict checking" on an email address > sent as a password for an anonymous user. > Ahhhhh.. Well, this problem should hopefully go away soon as I go to libftp! Jordan From owner-freebsd-current Mon Apr 24 19:20:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA06352 for current-outgoing; Mon, 24 Apr 1995 19:20:14 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA06338 for ; Mon, 24 Apr 1995 19:20:06 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id KAA26915; Tue, 25 Apr 1995 10:20:18 +0800 Date: Tue, 25 Apr 1995 10:20:18 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: tunefs(8) man page Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk The section on the minfree policy reads: This value specifies the percentage of space held back from nor- mal users; the minimum free space threshold. The default value used is 8%. This value can be set to zero, however up to a fac- tor of three in throughput will be lost over the performance ob- tained at a 10% threshold. Settings of 5% and less force space ^^^^^^^^^^^^^ Should this be 8% now? -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Mon Apr 24 20:19:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09136 for current-outgoing; Mon, 24 Apr 1995 20:19:19 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA09106 for ; Mon, 24 Apr 1995 20:19:03 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id LAA27040; Tue, 25 Apr 1995 11:19:14 +0800 Date: Tue, 25 Apr 1995 11:19:14 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: tunefs(8) man page In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 25 Apr 1995, Brian Tao wrote: > [...] > Should this be 8% now? Eek... sorry about the lousy formatting. Didn't think vim would convert spaces to tabs when left-shifting a block. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Mon Apr 24 20:27:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09606 for current-outgoing; Mon, 24 Apr 1995 20:27:30 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA09596 for ; Mon, 24 Apr 1995 20:27:21 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id LAA27055; Tue, 25 Apr 1995 11:27:37 +0800 Date: Tue, 25 Apr 1995 11:27:37 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: FreeBSD Double CD-ROM set? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk A couple of friends new to FreeBSD brought up this point and I saw it go by on the newsgroup too. Since Satoshi is diligently working at cleaning up our ports/packages collection, would it be possible for Walnut Creek to sell a "FreeBSD 2.1 Collections CD-ROM" supplement as well as a double CD set (2.1 installation + Collections)? Not everyone has Ethernet or a T1 to the local mirror site. Most people are probably on a timed 14.4k SLIP/PPP connection to their ISP. It would make sense for these folks to drop $20 or whatever and get 500 megs of precompiled binaries and source for their new FreeBSD machine. Linux distributions are famous for this "throw-in-everything-including- the-kitchen-sink-and-let-the-user-sort-it-out" approach. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Mon Apr 24 21:52:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA13132 for current-outgoing; Mon, 24 Apr 1995 21:52:02 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA13122 ; Mon, 24 Apr 1995 21:52:00 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id VAA05143; Mon, 24 Apr 1995 21:51:59 -0700 From: Poul-Henning Kamp Message-Id: <199504250451.VAA05143@ref.tfs.com> Subject: Testers please! To: hackers@FreeBSD.org Date: Mon, 24 Apr 1995 21:51:58 -0700 (PDT) Cc: current@FreeBSD.org Content-Type: text Content-Length: 1103 Sender: current-owner@FreeBSD.org Precedence: bulk The file ftp://freefall.cdrom.com/incoming/fixit_kernel Contains the latest wonder, a complete fixit_floppy in one kernel. Please try and boot it, and tell me what you think. I don't think it will boot on a 4Mb system. (The compressed image is bigger than 1Mb and gets loaded @ 3Mb.) If it says anything about "OnTrack disk manager" please send me email and tell me if it looked right to you. What is it ? It's a kzip'ed (compressed) kernel with a MFS (memory filesystem) root filesystem compiled in. This means that you can boot it from anywhere, including your harddisk (The dos-boot program needs a fix before it will work, but that is underway). Why is that special ? You can remount the root R/W without destroying your fixit-floppy mount -u mfs_root / You can mount another floppy if you want You can boot it of you harddisk/ms-dos partition (soon)/floppy or even over the network (!) Have fun ! -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon Apr 24 22:47:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA14338 for current-outgoing; Mon, 24 Apr 1995 22:47:55 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA14323 for ; Mon, 24 Apr 1995 22:47:40 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA16942; Tue, 25 Apr 1995 15:37:24 +1000 Date: Tue, 25 Apr 1995 15:37:24 +1000 From: Bruce Evans Message-Id: <199504250537.PAA16942@godzilla.zeta.org.au> To: chain@mpd.tandem.com, current@FreeBSD.org Subject: Re: 950412-SNAP Cc: chain%muzak.mpd.tandem.com@mpd.tandem.com Sender: current-owner@FreeBSD.org Precedence: bulk >> 2) My 'diskless' station has only a DOS partition and no FreeBSD >> partition in a wd0 (ST506). It panics during diskless boot. I traced >> down the panic to wdopen which was getting an integer division fault. >> The trace is as follows: >> configure() >> swapconf() >> wdsize() >> wdopen() >> ---idiv fault >> Is this a known problem? I got around the problem by bypassing wdopen() It was known that the diskless boot doesn't support getting the BIOS geometry or debugging and that the BIOS geometry is sometimes used when it is invalid. >> but wasn't able to trace further down because no symbols were loaded >> into the kernel, and ddb trace shows no names. I modified netboot to >> load symbol table over the net but it seems to have no effect. What >> other things do I need to do to get the symbol table loaded into ddb? >I've made a few small modifications to netboot to do the following: >1) Get wd0 disk geometry from bios and load bootinfo that includes > disk geometry, so wd* driver can make use of it when fails > to read from disk, rather than panic. >2) Load symbol tabel across the net so ddb works on diskless configuarion. >3) Build a mini netboot kernel that can be loaded by bios-boot, and > then starts a 'diskless' boot. Now that you can debug, please determine why the BIOS geometry is used at all. It should only be used if the WDCC_READP command fails, and it should only fail for old (ST506) drives. The current wd.c has some changes related to this. The BIOS geometry is no longer used by the driver except when WDCC_READP fails (previously, another BIOS geometry was inferred from the partition table and used even when WDCC_READP succeeds). This means that drives for which WDCC_READP fails will no longer work unless the BIOS geometry in `bootinfo' is correct. More work is required to ensure that it is correct and to know when it is incorrect (it can't be correct if there are old drives that aren't supported by the BIOS). >I am really hoping these features (mostly from biosboot) be included >in the standard netboot so I don't have to change it later myself. >I attached patched at the end. Did you think about sharing the boot code? At least the boot --> kernel interface parts should be common. >Also wd0 may need to be fixed so wdattach will fail if disk geometry cannot >be obtained, rather than succeeds and later panics in wdopen when invalid >geometry is used in calculation. It was supposed to guard against errors such as division by zero so that it could bootstrap to better geometries inferred from the partition table and read from the disk label, but the bootinfo BIOS geometry changes broke that). The bootstrapping process is error prone and currently mostly disabled. It will probably go away. Bruce From owner-freebsd-current Mon Apr 24 22:52:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA14533 for current-outgoing; Mon, 24 Apr 1995 22:52:34 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA14516 for ; Mon, 24 Apr 1995 22:52:19 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA17451; Tue, 25 Apr 1995 15:48:15 +1000 Date: Tue, 25 Apr 1995 15:48:15 +1000 From: Bruce Evans Message-Id: <199504250548.PAA17451@godzilla.zeta.org.au> To: curt@mofo.emergent.com Subject: Re: kern/360: filesystem deadlock Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Synopsis: filesystem deadlock trivial to produce > the filesystem deadlocks when installing a file to itself. > a ktrace shows a strange sequence: > at this point, deadlock with ps -l reporting ufslk2 > >>How-To-Repeat: > cd /tmp > cp /etc/termcap . > install -c -m 0644 termcap /tmp > >lockup< I think the deadlock was fixed a couple of days ago. >>Fix: > don't install a file to itself. I tried it anyway :-). The mmapping stuff causes the installed copy to be filled to the correct size with garbage. No error is detected. Bruce From owner-freebsd-current Mon Apr 24 23:14:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA15228 for current-outgoing; Mon, 24 Apr 1995 23:14:03 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA15206 ; Mon, 24 Apr 1995 23:13:54 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Poul-Henning Kamp cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Testers please! In-reply-to: Your message of "Mon, 24 Apr 95 21:51:58 PDT." <199504250451.VAA05143@ref.tfs.com> Date: Mon, 24 Apr 1995 23:13:54 -0700 Message-ID: <15205.798790434@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > The file > > ftp://freefall.cdrom.com/incoming/fixit_kernel > > Contains the latest wonder, a complete fixit_floppy in one kernel. > > Please try and boot it, and tell me what you think. Interesting. First impressions: 1. Hey, neat idea! 2. Hmmm. But is it good for anything? :-) Testing environment was a 486/33 with 8MB of memory. Every command is DOG SLOW. I mean SLOW. So slow that I think I might be inclined to simply reformat rather than fix.. :-) Why does it take such an inhumanly long time? Everything from `date' to `ls' lags about 3 seconds before startup and this is without any I/O to the floppy at all! Hmmmmmmmm.. 3. spwd.db is 0 length, resulting in some anguish from the system. Other than that, it's pretty neat stuff! If the wrinkles can be ironed out, I could see this as a nice tool. Jordan From owner-freebsd-current Tue Apr 25 00:39:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA18225 for current-outgoing; Tue, 25 Apr 1995 00:39:47 -0700 Received: from dkuug.dk (dkuug.dk [193.88.44.89]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA18216 for ; Tue, 25 Apr 1995 00:39:29 -0700 Received: from kmd-ac.dk by dkuug.dk with UUCP id AA22898 (5.65c8/IDA-1.4.4j for freebsd.org!current); Tue, 25 Apr 1995 09:38:42 +0200 Message-Id: <199504250738.AA22898@dkuug.dk> Subject: Who messed up libc ?!? To: current@FreeBSD.org (FreeBSD current) Date: Tue, 25 Apr 1995 09:27:35 +0000 (GMT) From: "Soeren Schmidt" From: sos@FreeBSD.org (Soren Schmidt) Reply-To: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 382 X-Charset: ASCII X-Char-Esc: 29 Sender: current-owner@FreeBSD.org Precedence: bulk I vaguely remember seeing a discussion on removing setregid & friends some time ago. Now somebody has done exactly that, but the Makefiles etc hasn't been changed accordingly. Would the "guilty" please get this sorted out... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@kmd-ac.dk) FreeBSD Core Team .. From owner-freebsd-current Tue Apr 25 04:22:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA25390 for current-outgoing; Tue, 25 Apr 1995 04:22:10 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA25383 for ; Tue, 25 Apr 1995 04:22:07 -0700 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA18223; Tue, 25 Apr 95 04:18:46 -0700 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0s3iaY-0005OqC; Tue, 25 Apr 95 13:15 MSZ Message-Id: To: current%freebsd.org@inet-gw-1.pa.dec.com Subject: patch to gdb Reply-To: gj@FreeBSD.org Date: Tue, 25 Apr 95 11:15:30 GMT From: "gj%pcs.dec.com@inet-gw-1.pa.dec.com" Sender: current-owner@FreeBSD.org Precedence: bulk Below are patches to add a '-w' option to gdb. This option is only effective in conjunction with the '-k' flag. While I was at it I added some code to show the kernel debugging options when you do 'gdb --help'. I also did some other miscellaneous clean up. Someone please apply these. Thanx Gary J. ------------------------------------ SNIP --------------------------------- Index: main.c =================================================================== RCS file: /u1/cvs/gdb/gdb/main.c,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 main.c *** 1.1.1.1 1995/04/23 18:35:40 - --- main.c 1995/04/24 21:43:19 *************** *** 173,178 **** - --- 173,180 ---- #ifdef KERNEL_DEBUG {"kernel", no_argument, &kernel_debugging, 1}, {"k", no_argument, &kernel_debugging, 1}, + {"wcore", no_argument, &kernel_writablecore, 1}, + {"w", no_argument, &kernel_writablecore, 1}, #endif /* Allow machine descriptions to add more options... */ #ifdef ADDITIONAL_OPTIONS *************** *** 268,273 **** - --- 270,278 ---- case 'k': kernel_debugging = 1; break; + case 'w': + kernel_writablecore = 1; + break; #endif #ifdef ADDITIONAL_OPTION_CASES *************** *** 350,355 **** - --- 355,367 ---- --mapped Use mapped symbol files if supported on this system.\n\ --readnow Fully read symbol files on first access.\n\ ", gdb_stdout); + #ifdef KERNEL_DEBUG + fputs_unfiltered ("\ + --kernel Enable kernel debugging.\n\ + --wcore Make core file writable (only works for /dev/mem).\n\ + This option only works while debugging a kernel !!\n\ + ", gdb_stdout); + #endif /* KERNEL_DEBUGGING */ #ifdef ADDITIONAL_OPTION_HELP fputs_unfiltered (ADDITIONAL_OPTION_HELP, gdb_stdout); #endif Index: kcorelow.c =================================================================== RCS file: /u1/cvs/gdb/gdb/kcorelow.c,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 kcorelow.c *** 1.1.1.1 1995/04/23 18:35:48 - --- kcorelow.c 1995/04/24 21:02:27 *************** *** 181,187 **** error ("kgdb could not open the exec-file, please check the name you used !"); core_kd = kvm_open (exec_bfd->filename, filename, NULL, ! write_files? O_RDWR: O_RDONLY, "kgdb: "); if (core_kd < 0) perror_with_name (filename); - --- 181,187 ---- error ("kgdb could not open the exec-file, please check the name you used !"); core_kd = kvm_open (exec_bfd->filename, filename, NULL, ! kernel_writablecore? O_RDWR: O_RDONLY, "kgdb: "); if (core_kd < 0) perror_with_name (filename); Index: top.c =================================================================== RCS file: /u1/cvs/gdb/gdb/top.c,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 top.c *** 1.1.1.1 1995/04/23 18:35:48 - --- top.c 1995/04/24 20:59:46 *************** *** 322,327 **** - --- 322,328 ---- #ifdef KERNEL_DEBUG /* Non-zero means we are debugging a kernel core file */ int kernel_debugging = 0; + int kernel_writablecore = 0; #endif /* Return for reason REASON. This generally gets back to the command Index: freebsd-nat.c =================================================================== RCS file: /u1/cvs/gdb/gdb/freebsd-nat.c,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 freebsd-nat.c *** 1.1.1.1 1995/04/23 18:35:38 - --- freebsd-nat.c 1995/04/24 21:25:41 *************** *** 344,352 **** kvm_open (efile, cfile, sfile, perm, errout) char *efile; char *cfile; ! void *sfile; int perm; ! int errout; { struct stat stb; CORE_ADDR addr; - --- 344,352 ---- kvm_open (efile, cfile, sfile, perm, errout) char *efile; char *cfile; ! char *sfile; /* makes this kvm_open more compatible to the one in libkvm */ int perm; ! char *errout; /* makes this kvm_open more compatible to the one in libkvm */ { struct stat stb; CORE_ADDR addr; Index: defs.h =================================================================== RCS file: /u1/cvs/gdb/gdb/defs.h,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 defs.h *** 1.1.1.1 1995/04/23 18:35:36 - --- defs.h 1995/04/24 21:05:17 *************** *** 434,439 **** - --- 434,440 ---- #ifdef KERNEL_DEBUG extern int kernel_debugging; + extern int kernel_writablecore; #endif /* If the xm.h file did not define the mode string used to open the From owner-freebsd-current Tue Apr 25 06:11:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA02153 for current-outgoing; Tue, 25 Apr 1995 06:11:54 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA02146 for ; Tue, 25 Apr 1995 06:11:52 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id JAA15666; Tue, 25 Apr 1995 09:10:46 -0400 From: Peter Dufault Message-Id: <199504251310.JAA15666@hda.com> Subject: Install feedback To: current@freefall.cdrom.com Date: Tue, 25 Apr 1995 09:10:46 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2012 Sender: current-owner@FreeBSD.org Precedence: bulk I tried the install, installing using nfs from another system. Just a few points: 1. The system (A "Dell Dimension 486DX2/50") hung after trying to label the disk after saying "Label written successfully". The debug screen showed: " <10>" and everything was dead except the console key toggle. I finally had to press the reset button. I tried it a second time and it worked fine. 2. In the NFS install it wasn't obvious that I was going to get a chance to specify the directory the distribution was in (perhaps I should have realized that) and so I went and changed my export to specify -alldirs so that I could mount the distribution directory. 3. "fsck -y"? I was surprised to see that happen automatically every time you boot. Why not "fsck -p"? Having "-y" in there seems like an invitation to trashing the disks and the naive user assumes everything is fine since the system did it for them. Ease of use: I hesitate to comment on how easy this install was, since I'm not much of a target. I thought the disk editing screen would be kind of confusing to a beginner. A very nice thing would be a single "Set up for entire disk" button that assumed the full disk and set everything up for you with 20MB root, 32 MB swap and the balance /usr. Even better would be "Install on entire disk" in the previous screen that would take straight through to "insert cpio floppy". More minor: even when you have only one disk it keeps asking you for which disk. Another minor point: We recommend in the README against running on a 386SX. I hope we keep our minimal system at 4MB of RAM and potentially a 386SX, at least for another year or so. There are applications that can run OK on this. How about rephrasing this to say "against interactive use on a 386SX" or something else a little less sweeping? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue Apr 25 06:38:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA04603 for current-outgoing; Tue, 25 Apr 1995 06:38:20 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA04597 for ; Tue, 25 Apr 1995 06:38:19 -0700 Received: (from jkh@localhost) by time.cdrom.com (8.6.11/8.6.9) id HAA00422 for current@freefall; Tue, 25 Apr 1995 07:41:20 -0700 Date: Tue, 25 Apr 1995 07:41:20 -0700 From: "Jordan K. Hubbard" Message-Id: <199504251441.HAA00422@time.cdrom.com> To: current@freefall.cdrom.com Subject: TeX support in bsd.doc.mk? Sender: current-owner@FreeBSD.org Precedence: bulk How do people feel about adding in some standard handy rules for this? Sure, we don't supply TeX as part of the system but it's a pretty convenient and oft-used add-on package and there are lots of docs written in it that could use the nice simple Makefiles this would make possible. Jordan From owner-freebsd-current Tue Apr 25 07:56:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA12693 for current-outgoing; Tue, 25 Apr 1995 07:56:09 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA12680 for ; Tue, 25 Apr 1995 07:56:02 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id JAA11107; Tue, 25 Apr 1995 09:00:21 -0600 Date: Tue, 25 Apr 1995 09:00:21 -0600 From: Nate Williams Message-Id: <199504251500.JAA11107@trout.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? In-Reply-To: <199504251441.HAA00422@time.cdrom.com> References: <199504251441.HAA00422@time.cdrom.com> Sender: current-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > How do people feel about adding in some standard handy rules for this? I'm not sure I follow? What kind of rules? > Sure, we don't supply TeX as part of the system but it's a pretty > convenient and oft-used add-on package and there are lots of docs written > in it that could use the nice simple Makefiles this would make possible. Are you talking build scripts for the existing packages? Nate From owner-freebsd-current Tue Apr 25 08:09:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA14391 for current-outgoing; Tue, 25 Apr 1995 08:09:27 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA14380 ; Tue, 25 Apr 1995 08:09:23 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Nate Williams cc: current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? In-reply-to: Your message of "Tue, 25 Apr 95 09:00:21 MDT." <199504251500.JAA11107@trout.sri.MT.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Apr 1995 08:09:23 -0700 Message-ID: <14379.798822563@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Jordan K. Hubbard writes: > > How do people feel about adding in some standard handy rules for this? > > I'm not sure I follow? What kind of rules? TEXDOC= foo .include % make tex foo.tex ... ... End up with foo.ps in obj. Jordan From owner-freebsd-current Tue Apr 25 08:13:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA14896 for current-outgoing; Tue, 25 Apr 1995 08:13:21 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA14884 for ; Tue, 25 Apr 1995 08:13:17 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id KAA06714; Tue, 25 Apr 1995 10:12:55 -0500 Received: by olympus (4.1/TSS2.1) id AA03497; Tue, 25 Apr 95 10:13:07 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504251513.AA03497@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 10:13:06 -0500 (CDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504230651.XAA03319@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 22, 95 11:51:19 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1970 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > Rod, > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > boot floppy and the fixit disk do not. Everthing is cool until the PCI > > is found. > > > > Apr 22 15:05:09 catburg /kernel: Probing for devices on the pci0 bus: > > Apr 22 15:05:10 catburg /kernel: configuration mode 2 allows 16 devices. > > Apr 22 15:05:10 catburg /kernel: chip0 > > rev 4 on pci0:0 > > Apr 22 15:05:10 catburg /kernel: ncr0 rev 2 int a irq 9 on > > pci 0:1 > > Apr 22 15:05:10 catburg /kernel: reg20: virtual=0xf2fe9000 > > physical=0xfbf ef000 size=0x100 > > > > Up to here life is good, but the following never happens from floppy. > > > > Apr 22 15:05:10 catburg /kernel: ncr0: restart (scsi reset). > > Apr 22 15:05:10 catburg /kernel: ncr0 scanning for targets 0..6 > > (V2 pl21 95/03/21) > > > > I have waited over a minute. > > > > Seen this before? > > I tried all my boards here, and every one of them works. I will bring > in a PCI/I-486SP3G this week and see if I can track this down. You > mention that this works with a -current kernel, what happens if > you put that kernel on floppy? Or if you copy the floppy kernel to > hard disk as /kernel.flp and try to boot it? > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > I tried copying the boot floppy to the hard disk and it still will not boot. I looked at the BOOTFLP config file in /sys/i386/conf and found this entry that I do not have in CATBURG. options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers Could this be it? Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 08:51:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA18650 for current-outgoing; Tue, 25 Apr 1995 08:51:25 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA18639 ; Tue, 25 Apr 1995 08:51:21 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id JAA11538; Tue, 25 Apr 1995 09:55:47 -0600 Date: Tue, 25 Apr 1995 09:55:47 -0600 From: Nate Williams Message-Id: <199504251555.JAA11538@trout.sri.MT.net> In-Reply-To: "Jordan K. Hubbard" "Re: TeX support in bsd.doc.mk?" (Apr 25, 8:09am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Jordan K. Hubbard" Subject: Re: TeX support in bsd.doc.mk? Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk > > Jordan K. Hubbard writes: > > > How do people feel about adding in some standard handy rules for this? > > > > I'm not sure I follow? What kind of rules? > > TEXDOC= foo > > .include > > % make > tex foo.tex ... > ... > End up with foo.ps in obj. Ahh, gotcha. Do you want to go all the way to PS files, or just to .dvi files? Generally xdvi is installed, and there are lots of dvi->misc converters which do a better job than the dvi->PS->misc conversion. Nate From owner-freebsd-current Tue Apr 25 10:08:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01368 for current-outgoing; Tue, 25 Apr 1995 10:08:07 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01341 for ; Tue, 25 Apr 1995 10:07:50 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id SAA12850; Tue, 25 Apr 1995 18:12:59 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id SAA13256; Tue, 25 Apr 1995 18:12:59 +0200 Message-Id: <199504251612.SAA13256@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? Date: Tue, 25 Apr 1995 18:12:59 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > How do people feel about adding in some standard handy rules for this? > Sure, we don't supply TeX as part of the system but it's a pretty > convenient and oft-used add-on package and there are lots of docs written > in it that could use the nice simple Makefiles this would make possible. Yes please! (Rubs hands in glee!) M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Tue Apr 25 10:10:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01609 for current-outgoing; Tue, 25 Apr 1995 10:10:49 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01599 ; Tue, 25 Apr 1995 10:10:44 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA10222; Tue, 25 Apr 1995 10:08:03 -0700 From: "Rodney W. Grimes" Message-Id: <199504251708.KAA10222@gndrsh.aac.dev.com> Subject: Re: TeX support in bsd.doc.mk? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Tue, 25 Apr 1995 10:08:03 -0700 (PDT) Cc: nate@trout.sri.mt.net, current@freefall.cdrom.com In-Reply-To: <14379.798822563@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 25, 95 08:09:23 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 684 Sender: current-owner@FreeBSD.org Precedence: bulk > > > Jordan K. Hubbard writes: > > > How do people feel about adding in some standard handy rules for this? > > > > I'm not sure I follow? What kind of rules? > > TEXDOC= foo > > .include > > % make > tex foo.tex ... > ... > End up with foo.ps in obj. I only have one thing I would like to say about this, don't modify bsd.doc.mk to do this (that file has to get parsed for every make in the source we do, and this just adds stuff to it to parse that we well not use in /usr/src) add bsd.tex.mk to do this. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 10:21:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02093 for current-outgoing; Tue, 25 Apr 1995 10:21:02 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02087 for ; Tue, 25 Apr 1995 10:20:58 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA10270; Tue, 25 Apr 1995 10:18:08 -0700 From: "Rodney W. Grimes" Message-Id: <199504251718.KAA10270@gndrsh.aac.dev.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: faulkner@mpd.tandem.com (Boyd Faulkner) Date: Tue, 25 Apr 1995 10:18:07 -0700 (PDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <9504251513.AA03497@olympus> from "Boyd Faulkner" at Apr 25, 95 10:13:06 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1396 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > Rod, > > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > > boot floppy and the fixit disk do not. Everything is cool until the PCI > > > is found. > > > ... > > I tried all my boards here, and every one of them works. I will bring > > in a PCI/I-486SP3G this week and see if I can track this down. You > > mention that this works with a -current kernel, what happens if > > you put that kernel on floppy? Or if you copy the floppy kernel to > > hard disk as /kernel.flp and try to boot it? > > > I tried copying the boot floppy to the hard disk and it still will not boot. > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry > that I do not have in CATBURG. > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > Could this be it? Could be, but it worked here with the NCR810's on 4 different systems, and I am using the same disk drive you have (only more of them :-)). Do you have anything besides the DEC3053L disk on you scsi bus now? You also say that a -current kernel works fine, what happens if you build BOOTFLP from you -current sources and try to boot it? (I know, lots of questions and no real answers :-(). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 10:23:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02179 for current-outgoing; Tue, 25 Apr 1995 10:23:00 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02168 ; Tue, 25 Apr 1995 10:22:56 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA10286; Tue, 25 Apr 1995 10:19:58 -0700 From: "Rodney W. Grimes" Message-Id: <199504251719.KAA10286@gndrsh.aac.dev.com> Subject: Re: TeX support in bsd.doc.mk? To: nate@trout.sri.MT.net (Nate Williams) Date: Tue, 25 Apr 1995 10:19:57 -0700 (PDT) Cc: jkh@freefall.cdrom.com, current@freefall.cdrom.com In-Reply-To: <199504251555.JAA11538@trout.sri.MT.net> from "Nate Williams" at Apr 25, 95 09:55:47 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 767 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > Jordan K. Hubbard writes: > > > > How do people feel about adding in some standard handy rules for this? > > > > > > I'm not sure I follow? What kind of rules? > > > > TEXDOC= foo > > > > .include > > > > % make > > tex foo.tex ... > > ... > > End up with foo.ps in obj. > > Ahh, gotcha. Do you want to go all the way to PS files, or just to .dvi > files? Generally xdvi is installed, and there are lots of dvi->misc > converters which do a better job than the dvi->PS->misc conversion. The resulting file type should depend on what ${PRINTER} is set to, see 4.4 Lite bsd.doc.mk. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 10:45:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA03367 for current-outgoing; Tue, 25 Apr 1995 10:45:37 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA03361 for ; Tue, 25 Apr 1995 10:45:35 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id MAA13932; Tue, 25 Apr 1995 12:45:20 -0500 Received: by olympus (4.1/TSS2.1) id AA03681; Tue, 25 Apr 95 12:45:19 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504251745.AA03681@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 12:45:18 -0500 (CDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251718.KAA10270@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 10:18:07 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 3681 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > Rod, > > > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > > > boot floppy and the fixit disk do not. Everything is cool until the PCI > > > > is found. > > > > > ... > > > I tried all my boards here, and every one of them works. I will bring > > > in a PCI/I-486SP3G this week and see if I can track this down. You > > > mention that this works with a -current kernel, what happens if > > > you put that kernel on floppy? Or if you copy the floppy kernel to > > > hard disk as /kernel.flp and try to boot it? > > > > > I tried copying the boot floppy to the hard disk and it still will not boot. > > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry > > that I do not have in CATBURG. > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > > > Could this be it? > > Could be, but it worked here with the NCR810's on 4 different systems, > and I am using the same disk drive you have (only more of them :-)). > > Do you have anything besides the DEC3053L disk on you scsi bus now? > You also say that a -current kernel works fine, what happens if > you build BOOTFLP from you -current sources and try to boot it? > > (I know, lots of questions and no real answers :-(). > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > >From /var/log/messages : ncr0: restart (scsi reset). : ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) : ncr0 waiting for scsi devices to settle : (ncr0:0:0): "CDC 94171-9 5955" type 0 fixed SCSI 1 : sd0(ncr0:0:0): Direct-Access 286MB (586458 512 byte sectors) : (ncr0:1:0): "MAXTOR MXT-1240S F02S" type 0 fixed SCSI 2 : sd1(ncr0:1:0): Direct-Access : sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. : 1183MB (2423457 512 byte sectors) : (ncr0:2:0): "MAXTOR 7245-SCSI 1057" type 0 fixed SCSI 1 : sd2(ncr0:2:0): Direct-Access 234MB (479656 512 byte sectors) : (ncr0:3:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 : cd0(ncr0:3:0): CD-ROM cd present.[12571 x 2048 byte records] : (ncr0:4:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 : st0(ncr0:4:0): Sequential-Access st0: Archive Viper 150 is a known rogue : density code 0x0, drive empty : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 : sd3(ncr0:5:0): Direct-Access : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB : sd3 could not mode sense (4). Using ficticious geometry : 382MB (782600 512 byte sectors) : chip1 rev 3 on pci0:2 : vga0 rev 0 on pci0:6 : pci0: uses 8388864 bytes of memory from fb000000 upto fbfef0ff. : pci0: uses 256 bytes of I/O space from e800 upto e8ff. The IBM is a new acquisition and I removed all drives but the cdrom and the tape and it still didn't work. Could a jumper on the motherboard make a difference. I went through them to make sure they made sense. Perhaps I should again. I don't remember if I changed any or not. The bios are as you sent them. Standard but with write-through amd ISA gating disabled. I am rebuilding the boot floppy now and will try it tonight. If it fails, I will rebuild with the > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers line removed and try that. Boyd Why the restriction? -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 11:13:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA05043 for current-outgoing; Tue, 25 Apr 1995 11:13:44 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA05032 for ; Tue, 25 Apr 1995 11:13:36 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA10369; Tue, 25 Apr 1995 11:10:47 -0700 From: "Rodney W. Grimes" Message-Id: <199504251810.LAA10369@gndrsh.aac.dev.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: faulkner@mpd.tandem.com (Boyd Faulkner) Date: Tue, 25 Apr 1995 11:10:46 -0700 (PDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <9504251745.AA03681@olympus> from "Boyd Faulkner" at Apr 25, 95 12:45:18 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4709 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > > > > > > > Rod, > > > > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > > > > boot floppy and the fixit disk do not. Everything is cool until the PCI > > > > > is found. > > > > > > > ... > > > > I tried all my boards here, and every one of them works. I will bring > > > > in a PCI/I-486SP3G this week and see if I can track this down. You > > > > mention that this works with a -current kernel, what happens if > > > > you put that kernel on floppy? Or if you copy the floppy kernel to > > > > hard disk as /kernel.flp and try to boot it? > > > > > > > I tried copying the boot floppy to the hard disk and it still will not boot. > > > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry > > > that I do not have in CATBURG. > > > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > > > > > Could this be it? > > > > Could be, but it worked here with the NCR810's on 4 different systems, > > and I am using the same disk drive you have (only more of them :-)). > > > > Do you have anything besides the DEC3053L disk on you scsi bus now? > > You also say that a -current kernel works fine, what happens if > > you build BOOTFLP from you -current sources and try to boot it? > > > > (I know, lots of questions and no real answers :-(). > > > > >From /var/log/messages > > : ncr0: restart (scsi reset). > : ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) > : ncr0 waiting for scsi devices to settle > : (ncr0:0:0): "CDC 94171-9 5955" type 0 fixed SCSI 1 > : sd0(ncr0:0:0): Direct-Access 286MB (586458 512 byte sectors) > : (ncr0:1:0): "MAXTOR MXT-1240S F02S" type 0 fixed SCSI 2 > : sd1(ncr0:1:0): Direct-Access > : sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > : 1183MB (2423457 512 byte sectors) > : (ncr0:2:0): "MAXTOR 7245-SCSI 1057" type 0 fixed SCSI 1 > : sd2(ncr0:2:0): Direct-Access 234MB (479656 512 byte sectors) > : (ncr0:3:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 Can you remove this easily? I have seen CD-ROM drives hang the NCR code up :-(. And turning off the sync negotiation seems to make the problem worse, not better :-(. > : cd0(ncr0:3:0): CD-ROM cd present.[12571 x 2048 byte records] > : (ncr0:4:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 > : st0(ncr0:4:0): Sequential-Access st0: Archive Viper 150 is a known rogue > : density code 0x0, drive empty > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > : sd3(ncr0:5:0): Direct-Access > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > : sd3 could not mode sense (4). Using ficticious geometry Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that does not understand a mode sense to page 4?? Very strange! > : 382MB (782600 512 byte sectors) > : chip1 rev 3 on pci0:2 > : vga0 rev 0 on pci0:6 > : pci0: uses 8388864 bytes of memory from fb000000 upto fbfef0ff. > : pci0: uses 256 bytes of I/O space from e800 upto e8ff. > > The IBM is a new acquisition and I removed all drives but the cdrom and the > tape and it still didn't work. Of all the devices we have the most problem with it is CDROM and Tape drives, I know this is probably painfull to remove these, but it will help to track down the problem. > Could a jumper on the motherboard make a difference. I went through them to > make sure they made sense. Perhaps I should again. I don't remember if I > changed any or not. The board as shipped by me should have been set correctly, with perhaps the exception of the SCSI terminator since you are running both internal and external devices. Make sure you turned of the terminator on the motherboard. > The bios are as you sent them. Standard but with write-through amd > ISA gating disabled. Okay, good, that eliminates that set of questions! > I am rebuilding the boot floppy now and will try it tonight. If it fails, > I will rebuild with the > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > line removed and try that. Okay, thanks. > > Why the restriction? Attempt to fix some people's system that hang during sync negotiation due to devices that claim to be SCSI-2 compliant, but get this part of the spec wrong. Also fixes some very old SCSI-I devices that lock up if you try to do sync negotiation with them. It was suppose to make it better, but it may infact be making things worse :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 11:22:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA05794 for current-outgoing; Tue, 25 Apr 1995 11:22:32 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA05786 for ; Tue, 25 Apr 1995 11:22:31 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA07876; Tue, 25 Apr 1995 11:22:19 -0700 From: Poul-Henning Kamp Message-Id: <199504251822.LAA07876@ref.tfs.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 11:22:19 -0700 (PDT) Cc: faulkner@mpd.tandem.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251810.LAA10369@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 11:10:46 am Content-Type: text Content-Length: 755 Sender: current-owner@FreeBSD.org Precedence: bulk > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > : sd3(ncr0:5:0): Direct-Access > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > : sd3 could not mode sense (4). Using ficticious geometry > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > does not understand a mode sense to page 4?? Very strange! No, a "type 0" device ? doesn't make sense! This guy isn't by any chance a "differential" device ? Anyway, check out all connections & terminations as the first thing... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Tue Apr 25 11:34:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA06621 for current-outgoing; Tue, 25 Apr 1995 11:34:43 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA06613 for ; Tue, 25 Apr 1995 11:34:39 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA10452; Tue, 25 Apr 1995 11:31:45 -0700 From: "Rodney W. Grimes" Message-Id: <199504251831.LAA10452@gndrsh.aac.dev.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 25 Apr 1995 11:31:44 -0700 (PDT) Cc: faulkner@mpd.tandem.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251822.LAA07876@ref.tfs.com> from "Poul-Henning Kamp" at Apr 25, 95 11:22:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1048 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > : sd3(ncr0:5:0): Direct-Access > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > does not understand a mode sense to page 4?? Very strange! > > No, a "type 0" device ? doesn't make sense! Type 0 == disk drive, type 1== tape drive, type 5==cdrom. A type 0 makes PERFECT since here! > This guy isn't by any chance a "differential" device ? > > Anyway, check out all connections & terminations as the first thing... > > -- > Poul-Henning Kamp -- TRW Financial Systems, Inc. > 'All relevant people are pertinent' && 'All rude people are impertinent' > => 'no rude people are relevant' > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 11:55:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA07839 for current-outgoing; Tue, 25 Apr 1995 11:55:31 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA07832 ; Tue, 25 Apr 1995 11:55:29 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id LAA02726; Tue, 25 Apr 1995 11:53:59 -0700 From: Steven G Kargl Message-Id: <199504251853.LAA02726@troutmask.apl.washington.edu> Subject: Re: TeX support in bsd.doc.mk? To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 11:53:59 -0700 (PDT) Cc: jkh@freefall.cdrom.com, nate@trout.sri.mt.net, current@freefall.cdrom.com In-Reply-To: <199504251708.KAA10222@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 10:08:03 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1760 Sender: current-owner@FreeBSD.org Precedence: bulk According to Rodney W. Grimes: > > > > > > Jordan K. Hubbard writes: > > > > How do people feel about adding in some standard handy rules for this? > > > > > > I'm not sure I follow? What kind of rules? > > > > TEXDOC= foo > > > > .include > > > > % make > > tex foo.tex ... > > ... > > End up with foo.ps in obj. > > I only have one thing I would like to say about this, don't modify > bsd.doc.mk to do this (that file has to get parsed for every make > in the source we do, and this just adds stuff to it to parse that > we well not use in /usr/src) add bsd.tex.mk to do this. > I agree with Rodney about bsd.tex.mk. However, I was wondering if it can be made smart enough to distinguish between TeX (as in Knuth), LaTex2e, TeXinfo, ... Also, you need to consider the possibility of cross references in a TeX file. This normally means that tex (or latex) is run more than once to get things straight;i.e., %latex foo <--- produce *.log, *.aux, *.toc ... %latex foo <--- resolve cross references (e.g., Table of Contents) [%latex foo <--- again, resolve more cross references?] %dvips -o foo.ps foo If you incorporate a dvips step, are we assuming 300dpi on a Canon CX laser printer engine? This could probably be set in make.conf; i.e., DPI=300 or ENGINE=CX. Dvips needs to have the *.mf files for font creationr available, and a single place to build/store the *.300pk files? If the tex,dvips,xdvi packages are previously installed, then dvips should Do the Right Thing, but it's not guaranteed. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Tue Apr 25 12:02:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA08304 for current-outgoing; Tue, 25 Apr 1995 12:02:52 -0700 Received: from netcom9.netcom.com (bakul@netcom9.netcom.com [192.100.81.119]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA08294 ; Tue, 25 Apr 1995 12:02:49 -0700 Received: from localhost by netcom9.netcom.com (8.6.12/Netcom) id MAA20277; Tue, 25 Apr 1995 12:01:31 -0700 Message-Id: <199504251901.MAA20277@netcom9.netcom.com> To: "Rodney W. Grimes" cc: nate@trout.sri.mt.net (Nate Williams), jkh@freefall.cdrom.com, current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? In-reply-to: Your message of "Tue, 25 Apr 95 10:19:57 PDT." <199504251719.KAA10286@gndrsh.aac.dev.com> Date: Tue, 25 Apr 95 12:01:26 -0700 From: Bakul Shah Sender: current-owner@FreeBSD.org Precedence: bulk > > Ahh, gotcha. Do you want to go all the way to PS files, or just to .dvi > > files? Generally xdvi is installed, and there are lots of dvi->misc > > converters which do a better job than the dvi->PS->misc conversion. > > The resulting file type should depend on what ${PRINTER} is set to, > see 4.4 Lite bsd.doc.mk. IMHO .dvi being printer and resolution independent makes a better target because - if you have more than one printer or a PS/PCL printer or a printer and a fax modem, you can setup your print filters appropriately to translate dvi to the correct PDL (page descr. language), resolution, and any other printer peculiarities. - typically .dvi files are about 60% of the eventual .ps files. - if you are using metafont based fonts, xdvi output is far superior to what you can get with ghostscript/ghostview. This is partly because xdvi uses antialiased fonts. xdvi is also much faster and less of a resource hog compared to gs/ghostview. And BTW, it can deal with .eps just fine. Since xdvi output is so superior (and so much easier on eyes) and since .dvi files are only about 10% bigger on average than nroffed output, I use xdvi as my man page reader! Then there is hyperTeX and xhdvi. With suitable macros you can convert an ordinary latex file into a .dvi file with hyperlinks. With xhdvi you can follow any cross-references in an .dvi file by click of a button. Though, support for external URLs is not so well integrated. If groff tools (& man macros) are similarly enhanced, one can follow x-refs of ``see fcntl(2)'' style far more easily. xhdvi with such man macros would make a far better help tool than xman. Since it can also deal with .dvi from texinfo files, it has the potential of being one unified help tool. If interested, follow the links from http://xxx.lanl.gov/hypertex/ --bakul From owner-freebsd-current Tue Apr 25 12:31:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA10099 for current-outgoing; Tue, 25 Apr 1995 12:31:04 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA10093 for ; Tue, 25 Apr 1995 12:31:01 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id OAA19280; Tue, 25 Apr 1995 14:30:46 -0500 Received: by olympus (4.1/TSS2.1) id AA03975; Tue, 25 Apr 95 14:30:57 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504251930.AA03975@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 25 Apr 1995 14:30:56 -0500 (CDT) Cc: rgrimes@gndrsh.aac.dev.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251822.LAA07876@ref.tfs.com> from "Poul-Henning Kamp" at Apr 25, 95 11:22:19 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1152 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > : sd3(ncr0:5:0): Direct-Access > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > does not understand a mode sense to page 4?? Very strange! > > No, a "type 0" device ? doesn't make sense! > > This guy isn't by any chance a "differential" device ? Possibly, would it work with DOS? It does. It was a bear disklabeling it, though. That is a different thread, however. Boyd > > Anyway, check out all connections & terminations as the first thing... > > -- > Poul-Henning Kamp -- TRW Financial Systems, Inc. > 'All relevant people are pertinent' && 'All rude people are impertinent' > => 'no rude people are relevant' > -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 12:32:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA10186 for current-outgoing; Tue, 25 Apr 1995 12:32:09 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA10176 ; Tue, 25 Apr 1995 12:32:05 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA10580; Tue, 25 Apr 1995 12:28:36 -0700 From: "Rodney W. Grimes" Message-Id: <199504251928.MAA10580@gndrsh.aac.dev.com> Subject: Re: TeX support in bsd.doc.mk? To: bakul@netcom.com (Bakul Shah) Date: Tue, 25 Apr 1995 12:28:36 -0700 (PDT) Cc: nate@trout.sri.mt.net, jkh@freefall.cdrom.com, current@freefall.cdrom.com In-Reply-To: <199504251901.MAA20277@netcom9.netcom.com> from "Bakul Shah" at Apr 25, 95 12:01:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 908 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > Ahh, gotcha. Do you want to go all the way to PS files, or just to .dvi > > > files? Generally xdvi is installed, and there are lots of dvi->misc > > > converters which do a better job than the dvi->PS->misc conversion. > > > > The resulting file type should depend on what ${PRINTER} is set to, > > see 4.4 Lite bsd.doc.mk. > > IMHO .dvi being printer and resolution independent makes a > better target because Then for your site in /etc/make.conf you set PRINTER=dvi, simple enough?? My point was that the .mk file should not be written to assume any prefered output format. Output should be selectable at build time via ${PRINTER}. There should be a reasonalbe default value for this, but it must be overrideable via /etc/make.conf. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 25 12:37:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA10551 for current-outgoing; Tue, 25 Apr 1995 12:37:44 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA10543 for ; Tue, 25 Apr 1995 12:37:41 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id PAA19591; Tue, 25 Apr 1995 15:36:09 -0400 From: Peter Dufault Message-Id: <199504251936.PAA19591@hda.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 25 Apr 1995 15:36:09 -0400 (EDT) Cc: rgrimes@gndrsh.aac.dev.com, faulkner@mpd.tandem.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251822.LAA07876@ref.tfs.com> from "Poul-Henning Kamp" at Apr 25, 95 11:22:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 837 Sender: current-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > : sd3(ncr0:5:0): Direct-Access > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > does not understand a mode sense to page 4?? Very strange! > > No, a "type 0" device ? doesn't make sense! (Huh? type 0 is direct access is disk - I don't get what you mean) Is the IBM formatted? I've used drives that had problems reporting capacity until you formatted them. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue Apr 25 12:46:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11220 for current-outgoing; Tue, 25 Apr 1995 12:46:12 -0700 Received: from netcom9.netcom.com (bakul@netcom9.netcom.com [192.100.81.119]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA11212 ; Tue, 25 Apr 1995 12:46:09 -0700 Received: from localhost by netcom9.netcom.com (8.6.12/Netcom) id MAA26464; Tue, 25 Apr 1995 12:44:50 -0700 Message-Id: <199504251944.MAA26464@netcom9.netcom.com> To: "Rodney W. Grimes" cc: nate@trout.sri.mt.net, jkh@freefall.cdrom.com, current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? In-reply-to: Your message of "Tue, 25 Apr 95 12:28:36 PDT." <199504251928.MAA10580@gndrsh.aac.dev.com> Date: Tue, 25 Apr 95 12:44:45 -0700 From: Bakul Shah Sender: current-owner@FreeBSD.org Precedence: bulk > Then for your site in /etc/make.conf you set PRINTER=dvi, simple enough?? Simple but this defeats the purpose of the `PRINTER' var. > My point was that the .mk file should not be written to assume any > prefered output format. Output should be selectable at build time > via ${PRINTER}. There should be a reasonalbe default value for this, > but it must be overrideable via /etc/make.conf. Why not use a different variable? TEXOUT or something? PRINTER connotes a different thing and it will confuse people. I agree it must be overrideable but for TeX the default should be its `native' output format. From owner-freebsd-current Tue Apr 25 12:54:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11912 for current-outgoing; Tue, 25 Apr 1995 12:54:48 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA11901 for ; Tue, 25 Apr 1995 12:54:45 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id PAA19684; Tue, 25 Apr 1995 15:53:37 -0400 From: Peter Dufault Message-Id: <199504251953.PAA19684@hda.com> Subject: panic: pmap_zero_page: CMAP busy To: current@freefall.cdrom.com Date: Tue, 25 Apr 1995 15:53:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 677 Sender: current-owner@FreeBSD.org Precedence: bulk I built a kernel from this morning's sup and it dies on a "Dell Dimension 486DX250" with the panic: > pmap_zero_page: CMAP busy It starts up single user fine, but will panic as soon as you type ps. "ps" will go in to "pmap_zero_page" 26 times and on the 27'th time will find that CMAP2 is already non-zero. The Stack backtrace is pmap_zero_page vm_page_zero_fill vm_fault trap_pfault trap(27, ...) I don't have much experience with this system though it boots the GENERIC kernel on the last SNAP fine. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue Apr 25 12:55:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11963 for current-outgoing; Tue, 25 Apr 1995 12:55:25 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA11953 for ; Tue, 25 Apr 1995 12:55:23 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id OAA20157; Tue, 25 Apr 1995 14:55:07 -0500 Received: by olympus (4.1/TSS2.1) id AA04032; Tue, 25 Apr 95 14:55:18 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504251955.AA04032@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: dufault@hda.com (Peter Dufault) Date: Tue, 25 Apr 1995 14:55:17 -0500 (CDT) Cc: phk@ref.tfs.com, rgrimes@gndrsh.aac.dev.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251936.PAA19591@hda.com> from "Peter Dufault" at Apr 25, 95 03:36:09 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1179 Sender: current-owner@FreeBSD.org Precedence: bulk > > Poul-Henning Kamp writes: > > > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > > : sd3(ncr0:5:0): Direct-Access > > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > > does not understand a mode sense to page 4?? Very strange! > > > > No, a "type 0" device ? doesn't make sense! > > (Huh? type 0 is direct access is disk - I don't get what you mean) > > Is the IBM formatted? I've used drives that had problems reporting > capacity until you formatted them. > > -- > Peter Dufault Real Time Machine Control and Simulation > HD Associates, Inc. Voice: 508 433 6936 > dufault@hda.com Fax: 508 433 5267 > Yes, I lowlevel formatted it wuth the DOS NCR SCSIFMT utility. Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 13:18:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA13582 for current-outgoing; Tue, 25 Apr 1995 13:18:52 -0700 Received: from pp2.smc.south.telia.se (pp2.smc.south.telia.se [131.116.12.194]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA13566 for ; Tue, 25 Apr 1995 13:18:31 -0700 Received: (from paul@localhost) by pp2.smc.south.telia.se (8.6.8/8.6.6) id WAA09473; Tue, 25 Apr 1995 22:23:23 +0200 Date: Tue, 25 Apr 1995 22:23:22 +0200 (MET DST) From: Paul Pries Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: Boyd Faulkner cc: Poul-Henning Kamp , rgrimes@gndrsh.aac.dev.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <9504251930.AA03975@olympus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 25 Apr 1995, Boyd Faulkner wrote: > > > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > > : sd3(ncr0:5:0): Direct-Access > > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > > does not understand a mode sense to page 4?? Very strange! > > > > No, a "type 0" device ? doesn't make sense! > > > > This guy isn't by any chance a "differential" device ? > > Possibly, would it work with DOS? It does. It was a bear disklabeling it, though. > That is a different thread, however. I'd say it simply is some junk IBM disk. I had the same problem with an old 120MB IBM drive back in the good (bad??) old days of 386BSD-0.1. If it wasn't exactly the same errormessage, then it was pretty darn near it. If you get it to work, please feel free to tell me how you did it... :-) /Paul. > > Boyd > > > > > Anyway, check out all connections & terminations as the first thing... > > > > -- > > Poul-Henning Kamp -- TRW Financial Systems, Inc. > > 'All relevant people are pertinent' && 'All rude people are impertinent' > > => 'no rude people are relevant' > > > > > -- > _______________________________________________________________________ > > Boyd Faulkner faulkner@isd.tandem.com > _______________________________________________________________________ > -- Paul Pries email: Phone: Telia AB paul@smc.south.telia.se +46 40 445108 (home) Region Syd +46 40 272671 (work) 205 21 Malmo +46 10 201 8925 (mobile) SWEDEN +46 40 974865 (fax) Any opinions that might have been expressed in the above message are mine. If you like them, you can have them too. From owner-freebsd-current Tue Apr 25 14:21:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA18153 for current-outgoing; Tue, 25 Apr 1995 14:21:07 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA18139 for ; Tue, 25 Apr 1995 14:21:03 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id RAA22589; Tue, 25 Apr 1995 17:19:52 -0400 From: Peter Dufault Message-Id: <199504252119.RAA22589@hda.com> Subject: Re: panic: pmap_zero_page: CMAP busy To: dufault@hda.com (Peter Dufault) Date: Tue, 25 Apr 1995 17:19:51 -0400 (EDT) Cc: current@freefall.cdrom.com In-Reply-To: <199504251953.PAA19684@hda.com> from "Peter Dufault" at Apr 25, 95 03:53:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1209 Sender: current-owner@FreeBSD.org Precedence: bulk Peter Dufault writes: > > I built a kernel from this morning's sup and it dies on a "Dell Dimension > 486DX250" with the panic: > > > pmap_zero_page: CMAP busy > > It starts up single user fine, but will panic as soon as you type ps. > "ps" will go in to "pmap_zero_page" 26 times and on the 27'th time will > find that CMAP2 is already non-zero. > > The Stack backtrace is > > pmap_zero_page > vm_page_zero_fill > vm_fault > trap_pfault > trap(27, ...) > > I don't have much experience with this system though it boots the GENERIC > kernel on the last SNAP fine. I'll file a full bug report later when I determine exactly what is wrong. The panic is caused by the difference between these two lines in the config: >From GENERIC (works): > config kernel root on wd0 swap on wd0 and wd1 and wd2 and vn0 dumps on wd0 >From DESMOND (panics): > config kernel root on wd0 swap on wd0 dumps on wd0 DESMOND also has the references to "wd1" and "wd2" removed. Changing desmond back to have "wd1", "wd2" and "vn0" swap made it boot OK. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue Apr 25 14:58:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20920 for current-outgoing; Tue, 25 Apr 1995 14:58:04 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA20912 for ; Tue, 25 Apr 1995 14:57:56 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <11777-0@bunyip.cc.uq.oz.au>; Wed, 26 Apr 1995 07:57:30 +1000 Received: by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) id SAA15397; Tue, 25 Apr 1995 18:15:37 +1000 From: Stephen McKay Message-Id: <199504250815.SAA15397@pandora.devetir.qld.gov.au> To: current@FreeBSD.org cc: syssgm@devetir.qld.gov.au Subject: fcntl F_SETLK backward compatibility hack implemented Date: Tue, 25 Apr 95 18:15:37 EST Sender: current-owner@FreeBSD.org Precedence: bulk Well, since nobody objected :-) I went and implemented my proposed fix to fcntl locking. Here are patches to sys/fcntl.h and kern/kern_descrip.c plus two test programs. The 'break' program demonstrates how the scheme can fail, and allows you to look at the pretty console warnings. The ftest program sets a few random locks and checks for clashes. If any console messages turn up, it has failed. I compile it on a 1.1.5 system and a 2.0 system then run it like: $ ./ftest.1.1.5 & ./ftest.2.0 ; sleep 3 048901919: 374: OK F_WRLCK SEEK_CUR -3722 6989 == 2201 to 9189 048937427: 375: NO F_WRLCK SEEK_SET 6048 3952 == 6048 to 9999 048940850: 375: -> F_WRLCK SEEK_SET 2201 6989 == 2201 to 9189 PID:374 050970752: 375: OK F_WRLCK SEEK_SET 6048 3952 == 6048 to 9999 051003186: 374: OK F_WRLCK SEEK_CUR 33 1554 == 4191 to 5744 ... This shows a microsecond timestamp, the pid, success/failure/reason, and the expanded flock structure. I think the patch works well, and since it changes the real fcntl lock code so little, it won't make things any worse! Stephen. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # diffs # Makefile # ftest.c # break.c # echo x - diffs sed 's/^X//' >diffs << 'END-of-diffs' X--- sys/fcntl.h.dist Tue Aug 2 17:52:57 1994 X+++ sys/fcntl.h Sun Apr 23 22:13:31 1995 X@@ -135,10 +135,13 @@ X #ifndef _POSIX_SOURCE X #define F_GETOWN 5 /* get SIGIO/SIGURG proc/pgrp */ X #define F_SETOWN 6 /* set SIGIO/SIGURG proc/pgrp */ X+#define F_OGETLK 7 /* 4.3 backward compatible GETLK */ X+#define F_OSETLK 8 /* 4.3 backward compatible SETLK */ X+#define F_OSETLKW 9 /* 4.3 backward compatible SETLKW */ X #endif X-#define F_GETLK 7 /* get record locking information */ X-#define F_SETLK 8 /* set record locking information */ X-#define F_SETLKW 9 /* F_SETLK; wait if blocked */ X+#define F_GETLK 10 /* get record locking information */ X+#define F_SETLK 11 /* set record locking information */ X+#define F_SETLKW 12 /* F_SETLK; wait if blocked */ X X /* file descriptor flags (F_GETFD, F_SETFD) */ X #define FD_CLOEXEC 1 /* close-on-exec flag */ X@@ -164,6 +167,19 @@ X short l_type; /* lock type: read/write, etc. */ X short l_whence; /* type of l_start */ X }; X+ X+#ifndef _POSIX_SOURCE X+/* X+ * 4.3 backward compatible advisory lock structure. X+ */ X+struct oflock { X+ short ol_type; /* lock type: read/write, etc. */ X+ short ol_whence; /* type of l_start */ X+ long ol_start; /* starting offset */ X+ long ol_len; /* len = 0 means until end of file */ X+ short ol_pid; /* lock owner */ X+}; X+#endif X X X #ifndef _POSIX_SOURCE X--- kern/kern_descrip.c.dist Mon Oct 3 03:35:11 1994 X+++ kern/kern_descrip.c Tue Apr 25 18:07:52 1995 X@@ -263,6 +263,7 @@ X error = copyin((caddr_t)uap->arg, (caddr_t)&fl, sizeof (fl)); X if (error) X return (error); X+ f_setlk: X if (fl.l_whence == SEEK_CUR) X fl.l_start += fp->f_offset; X switch (fl.l_type) { X@@ -295,11 +296,138 @@ X error = copyin((caddr_t)uap->arg, (caddr_t)&fl, sizeof (fl)); X if (error) X return (error); X+ f_getlk: X if (fl.l_whence == SEEK_CUR) X fl.l_start += fp->f_offset; X if ((error = VOP_ADVLOCK(vp,(caddr_t)p,F_GETLK,&fl,F_POSIX))) X return (error); X return (copyout((caddr_t)&fl, (caddr_t)uap->arg, sizeof (fl))); X+ X+#if defined(COMPAT_43) || defined(COMPAT_SUNOS) X+ X+#define VALID_L_TYPE(t) ((t)==F_RDLCK || (t)==F_UNLCK || (t)==F_WRLCK) X+#define VALID_WHENCE(w) ((w)==SEEK_SET || (w)==SEEK_CUR || (w)==SEEK_END) X+ X+ /* X+ * Backward compatible fcntl lock calls weren't added when the X+ * flock structure was changed. We have to use some guesswork X+ * to make up for this omission. X+ * X+ * Code by: Stephen McKay X+ */ X+ case F_OSETLKW: X+ case F_OSETLK: X+ case F_OGETLK: { X+ int is_new = 1, is_old = 1; X+ long start_high, len_high; X+ struct oflock ofl; X+ X+ if (fp->f_type != DTYPE_VNODE) X+ return (EBADF); X+ vp = (struct vnode *)fp->f_data; X+ X+ /* X+ * Copy in the lock structure, being ultra cautious in case X+ * it is an old style structure at the end of memory. X+ */ X+ error = copyin((caddr_t)uap->arg, &fl, sizeof (fl)); X+ if (error) { X+ error = copyin((caddr_t)uap->arg, &ofl, sizeof (ofl)); X+ if (error) X+ return (error); X+ is_new = 0; X+ } else X+ bcopy(&fl, &ofl, sizeof (ofl)); X+ X+ /* X+ * Since 1.1.5 and 2.0 binaries both use the old lock calls X+ * but with different flock structures, we have to guess X+ * which one we have been passed by using whatever consistency X+ * checks are available. X+ */ X+ if (!VALID_L_TYPE(fl.l_type) || !VALID_WHENCE(fl.l_whence)) X+ is_new = 0; X+ X+ if (!VALID_L_TYPE(ofl.ol_type) || !VALID_WHENCE(ofl.ol_whence)) X+ is_old = 0; X+ X+ if (fl.l_len < 0 || fl.l_whence == SEEK_SET && fl.l_start < 0) X+ is_new = 0; X+ X+ if (ofl.ol_len<0 || ofl.ol_whence==SEEK_SET && ofl.ol_start<0) X+ is_old = 0; X+ X+ if (fl.l_whence == SEEK_CUR && fl.l_start + fp->f_offset < 0) X+ is_new = 0; X+ X+ if (ofl.ol_whence==SEEK_CUR && ofl.ol_start + fp->f_offset < 0) X+ is_old = 0; X+ X+ start_high = fl.l_start >> 32; X+ len_high = fl.l_len >> 32; X+ if (start_high != 0 && start_high != -1 || len_high != 0) X+ is_new = 0; X+ X+ /* X+ * If we can't be sure, assume it is 1.1.5 or older, and X+ * be a little noisy about it, in case we are wrong. X+ * X+ * XXXX It may be even better to return an error here and X+ * make no uncertain guesses. X+ */ X+ if (is_old == is_new) { X+ printf("pid %lu assuming old fcntl lock structure\n", X+ (u_long)curproc->p_pid); X+ is_new = 0; X+ is_old = 1; X+ } X+ X+ if (is_old) { X+ fl.l_type = ofl.ol_type; X+ fl.l_whence = ofl.ol_whence; X+ fl.l_start = ofl.ol_start; X+ fl.l_len = ofl.ol_len; X+ fl.l_pid = ofl.ol_pid; X+ } X+ X+ /* X+ * Now that we have the data in a new style flock structure X+ * most cases can be handled by jumping back into the normal X+ * locking code. F_GETLK on an old style lock is the only X+ * exception. X+ */ X+ switch (uap->cmd) { X+ case F_OSETLKW: X+ flg |= F_WAIT; X+ /* Fall into F_OSETLK */ X+ X+ case F_OSETLK: X+ goto f_setlk; X+ X+ case F_OGETLK: X+ if (is_new) X+ goto f_getlk; X+ X+ if (fl.l_whence == SEEK_CUR) X+ fl.l_start += fp->f_offset; X+ error = VOP_ADVLOCK(vp,(caddr_t)p,F_GETLK,&fl,F_POSIX); X+ if (error) X+ return (error); X+ X+ ofl.ol_type = fl.l_type; X+ ofl.ol_whence = fl.l_whence; X+ ofl.ol_start = (long)fl.l_start; X+ ofl.ol_len = (long)fl.l_len; X+ ofl.ol_pid = (short)fl.l_pid; X+ X+ return (copyout(&ofl, (caddr_t)uap->arg, sizeof (ofl))); X+ } X+ } X+ X+#undef VALID_L_TYPE X+#undef VALID_WHENCE X+ X+#endif /* defined(COMPAT_43) || defined(COMPAT_SUNOS) */ X X default: X return (EINVAL); END-of-diffs echo x - Makefile sed 's/^X//' >Makefile << 'END-of-Makefile' XCFLAGS= -O2 -Wall X Xall: ftest break X Xftest: ftest.o X $(CC) -o ftest ftest.o X Xbreak: break.o X $(CC) -o break break.o END-of-Makefile echo x - ftest.c sed 's/^X//' >ftest.c << 'END-of-ftest.c' X/* X * Simple tests to determine if the backward compatible fcntl lock X * mechanism works. X */ X X#include X#include X#include X#include X#include X#include X X#define FILE_SIZE 8192 X Xchar junk[FILE_SIZE]; X Xvoid lock_rnd(int fd); Xvoid try_lock(int fd, struct flock *fl); Xvoid unlock(int fd, struct flock *fl); Xvoid log(char *msg, struct flock *fl, int do_pid); X X#define FALSE 0 X#define TRUE 1 X X#define rnd(n) (random()%(n)) X Xoff_t where = 0;; X Xint Xmain(argc, argv) Xint argc; Xchar **argv; X { X int fd; X int i; X char *name = "TOAD"; X X srandom(getpid()); X X if ((fd = open(name, O_RDWR|O_CREAT|O_TRUNC, 0600)) == -1) X perror(name), exit(1); X X write(fd, junk, sizeof(junk)); X lseek(fd, where, SEEK_SET); X X for (i = 0; i < 5; i++) X lock_rnd(fd); X X return 0; X } X X Xvoid Xlock_rnd(int fd) X { X struct flock fl; X X fl.l_type = F_WRLCK; X switch (rnd(3)) X { X case 0: X fl.l_whence = SEEK_SET; X fl.l_start = rnd(FILE_SIZE); X fl.l_len = rnd(FILE_SIZE); X break; X X case 1: X fl.l_whence = SEEK_CUR; X where = lseek(fd, (off_t)rnd(FILE_SIZE), SEEK_SET); X if (where < 0) X { X perror("lseek"); X exit(1); X } X fl.l_start = rnd(FILE_SIZE) - where; X fl.l_len = rnd(FILE_SIZE); X break; X X case 2: X fl.l_whence = SEEK_END; X fl.l_start = rnd(FILE_SIZE) - FILE_SIZE; X fl.l_len = rnd(FILE_SIZE); X break; X } X X try_lock(fd, &fl); X sleep(2); X unlock(fd, &fl); X } X X#define MAGIC1 0x9174e2fa X#define MAGIC2 0x5d738fe2 X Xvoid Xtry_lock(int fd, struct flock *fl) X { X int set = F_SETLK; X volatile unsigned flank1 = MAGIC1; X volatile struct flock blocker; X volatile unsigned flank2 = MAGIC2; X X for (;;) X { X if (fcntl(fd, set, fl) == 0) X { X log("OK", fl, FALSE); X return; X } X if (errno != EWOULDBLOCK) X { X perror("SETLK"); X exit(1); X } X log("NO", fl, FALSE); X blocker = *fl; X if (fcntl(fd, F_GETLK, &blocker) < 0) X { X perror("GETLK"); X exit(1); X } X log("->", (struct flock *)&blocker, TRUE); X if (flank1 != MAGIC1) X { X printf("GETLK overwrote flank1\n"); X exit(1); X } X if (flank2 != MAGIC2) X { X printf("GETLK overwrote flank2\n"); X exit(1); X } X set = F_SETLKW; X } X } X X Xvoid Xunlock(int fd, struct flock *fl) X { X struct flock x; X X x = *fl; X x.l_type = F_UNLCK; X if (fcntl(fd, F_SETLK, &x) < 0) X { X perror("UNLCK"); X exit(1); X } X } X X Xchar *lock_names[] = X { X "", "F_RDLCK", "F_UNLCK", "F_WRLCK" X }; X Xchar *seek_names[] = X { X "SEEK_SET", "SEEK_CUR", "SEEK_END" X }; X Xvoid Xlog(char *msg, struct flock *fl, int do_pid) X { X off_t start; X struct timeval tv; X X gettimeofday(&tv, NULL); X X printf("%09ld: ", (tv.tv_sec % 1000) * 1000000 + tv.tv_usec); X printf("%ld: %s", (long)getpid(), msg); X printf(" %s %s", lock_names[fl->l_type], seek_names[fl->l_whence]); X printf(" %5ld %5ld", (long)fl->l_start, (long)fl->l_len); X start = fl->l_start; X switch (fl->l_whence) X { X case SEEK_CUR: X start += where; X break; X case SEEK_END: X start += FILE_SIZE; X break; X } X printf(" == %5ld to %5ld", (long)start, (long)(start+fl->l_len-1)); X if (do_pid) X printf(" PID:%ld", (long)fl->l_pid); X printf("\n"); X } END-of-ftest.c echo x - break.c sed 's/^X//' >break.c << 'END-of-break.c' X/* X * A test of the cases where the backward compatible fcntl locking X * doesn't work. X */ X X#include X#include X#include X#include X#include X Xint Xmain(argc, argv) Xint argc; Xchar **argv; X { X int fd; X char *name = "TOAD"; X struct X { X struct flock fl; X int pid; X short type; X short whence; X } it; X X if ((fd = open(name, O_RDWR|O_CREAT|O_TRUNC, 0600)) == -1) X perror(name), exit(1); X X /* X * This lock is ambiguous on a 2.0 system and will default to "old". X */ X it.fl.l_type = F_WRLCK; X it.fl.l_whence = SEEK_SET; X it.fl.l_start = 0x00010001; X it.fl.l_len = 0; X if (fcntl(fd, F_SETLK, &it.fl) < 0) X perror("set1"); X X /* X * This lock is ambiguous on a 1.1.5 system and will default to "old". X * Note that without the bzero(), the uninitialised areas usually X * remove the ambiguity. X */ X bzero(&it, sizeof(it)); X it.fl.l_type = F_WRLCK; X it.fl.l_whence = SEEK_SET; X it.fl.l_start = 0; X it.fl.l_len = 0; X it.type = F_RDLCK; X it.whence = SEEK_CUR; X if (fcntl(fd, F_SETLK, &it.fl) < 0) X perror("set2"); X X return 0; X } END-of-break.c exit From owner-freebsd-current Tue Apr 25 15:10:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA21709 for current-outgoing; Tue, 25 Apr 1995 15:10:52 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA21692 ; Tue, 25 Apr 1995 15:10:43 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <43057>; Wed, 26 Apr 1995 00:09:58 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id BAA20064; Mon, 24 Apr 1995 01:36:00 +0200 Message-Id: <199504232336.BAA20064@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: Julian Howard Stacey , velte@cdrom.com, current@freefall.cdrom.com Subject: Re: A Scenario for FreeBSD Commercial Support In-reply-to: Your message of "Sat, 22 Apr 1995 01:14:49 +0200." <24265.798506089@freefall.cdrom.com> Date: Mon, 24 Apr 1995 01:35:58 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.org Precedence: bulk > From: "Jordan K. Hubbard" > I don't much like this idea. ... > "Sorry, you're out of date. You need to upgrade your entire shop > and fix what isn't broken before we'll help you with your problem." No that's Not how it would work, you missed out my original : - "for free" - basic boot support only (no advanced free support) you also added "entire shop", you thus massively misunderstood what I suggested, so I'll re-state it: "Sorry, you're out of date. You need to upgrade the machine you are exhibiting the basic fail-to-boot problem on if you want to receive Free support" If a company wants corporate wide support of advanced problems, there's no way WC could possibly provide that for Free ! What I suggest is thet WC Inc might like to establish a Basic support net for first time boot people, to encourage production of 4 releases per year, to create revenue for them to subsidise Release Engineer, + Support staff. --- Julian Stacey Tel. +49 89 268616. Fax Modem: 2608126 Vector Systems Ltd: an Internet, Unix & C systems consultancy. From owner-freebsd-current Tue Apr 25 15:19:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA22230 for current-outgoing; Tue, 25 Apr 1995 15:19:27 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA22223 for ; Tue, 25 Apr 1995 15:19:25 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id RAA27062; Tue, 25 Apr 1995 17:19:09 -0500 Received: by olympus (4.1/TSS2.1) id AA04474; Tue, 25 Apr 95 17:19:02 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504252219.AA04474@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: paul@pp2.smc.south.telia.se (Paul Pries) Date: Tue, 25 Apr 1995 17:19:02 -0500 (CDT) Cc: faulkner@devnull.mpd.tandem.com, phk@ref.tfs.com, rgrimes@gndrsh.aac.dev.com, current@FreeBSD.org In-Reply-To: from "Paul Pries" at Apr 25, 95 10:23:22 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1531 Sender: current-owner@FreeBSD.org Precedence: bulk > > On Tue, 25 Apr 1995, Boyd Faulkner wrote: > > > > > > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > > > : sd3(ncr0:5:0): Direct-Access > > > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > > > I'd say it simply is some junk IBM disk. I had the same problem with an > old 120MB IBM drive back in the good (bad??) old days of 386BSD-0.1. > If it wasn't exactly the same errormessage, then it was pretty darn near it. > > If you get it to work, please feel free to tell me how you did it... :-) It works now. I had to scuttle disklabel to get it to write the damn disklabel in spite of what the kernel says. I don't think that is IBM drive specific. I have had the same problem with other drives before. 1 DOS partition (for games like DOOM and such) 1 much larger FreeBSD partition. > > -- > Paul Pries email: Phone: > Telia AB paul@smc.south.telia.se +46 40 445108 (home) > Region Syd +46 40 272671 (work) > 205 21 Malmo +46 10 201 8925 (mobile) > SWEDEN +46 40 974865 (fax) > > Any opinions that might have been expressed in the above message > are mine. If you like them, you can have them too. > > > -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 17:21:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA25127 for current-outgoing; Tue, 25 Apr 1995 17:21:56 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA25120 ; Tue, 25 Apr 1995 17:21:54 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Nate Williams cc: current@freefall.cdrom.com Subject: Re: TeX support in bsd.doc.mk? In-reply-to: Your message of "Tue, 25 Apr 95 09:55:47 MDT." <199504251555.JAA11538@trout.sri.MT.net> Date: Tue, 25 Apr 1995 17:21:54 -0700 Message-ID: <25119.798855714@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Ahh, gotcha. Do you want to go all the way to PS files, or just to .dvi > files? Generally xdvi is installed, and there are lots of dvi->misc > converters which do a better job than the dvi->PS->misc conversion. Either would actually be fine by me. Make it a new DOC_TARGET_TYPE variable or something and maintain max flexibility - the user could set their desired `output' format in make.conf. Jordan From owner-freebsd-current Tue Apr 25 17:26:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA25205 for current-outgoing; Tue, 25 Apr 1995 17:26:33 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA25199 for ; Tue, 25 Apr 1995 17:26:31 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id TAA01995; Tue, 25 Apr 1995 19:26:14 -0500 Received: by olympus (4.1/TSS2.1) id AA05151; Tue, 25 Apr 95 19:26:24 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504260026.AA05151@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 19:26:23 -0500 (CDT) Cc: faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251810.LAA10369@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 11:10:46 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 5370 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > > > > > > > > > > > > > > > > > > > > > Rod, > > > > > > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > > > > > > boot floppy and the fixit disk do not. Everything is cool until the PCI > > > > > > is found. > > > > > > > > > ... > > > > > I tried all my boards here, and every one of them works. I will bring > > > > > in a PCI/I-486SP3G this week and see if I can track this down. You > > > > > mention that this works with a -current kernel, what happens if > > > > > you put that kernel on floppy? Or if you copy the floppy kernel to > > > > > hard disk as /kernel.flp and try to boot it? > > > > > > > > > I tried copying the boot floppy to the hard disk and it still will not boot. > > > > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry > > > > that I do not have in CATBURG. > > > > > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > > > > > > > Could this be it? > > > > > > Could be, but it worked here with the NCR810's on 4 different systems, > > > and I am using the same disk drive you have (only more of them :-)). > > > > > > Do you have anything besides the DEC3053L disk on you scsi bus now? > > > You also say that a -current kernel works fine, what happens if > > > you build BOOTFLP from you -current sources and try to boot it? > > > > > > (I know, lots of questions and no real answers :-(). > > > > > > > >From /var/log/messages > > > > : ncr0: restart (scsi reset). > > : ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) > > : ncr0 waiting for scsi devices to settle > > : (ncr0:0:0): "CDC 94171-9 5955" type 0 fixed SCSI 1 > > : sd0(ncr0:0:0): Direct-Access 286MB (586458 512 byte sectors) > > : (ncr0:1:0): "MAXTOR MXT-1240S F02S" type 0 fixed SCSI 2 > > : sd1(ncr0:1:0): Direct-Access > > : sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > > : 1183MB (2423457 512 byte sectors) > > : (ncr0:2:0): "MAXTOR 7245-SCSI 1057" type 0 fixed SCSI 1 > > : sd2(ncr0:2:0): Direct-Access 234MB (479656 512 byte sectors) > > : (ncr0:3:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 > > Can you remove this easily? I have seen CD-ROM drives hang the > NCR code up :-(. And turning off the sync negotiation seems to > make the problem worse, not better :-(. > Makes no difference. > > : cd0(ncr0:3:0): CD-ROM cd present.[12571 x 2048 byte records] > > : (ncr0:4:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 > > : st0(ncr0:4:0): Sequential-Access st0: Archive Viper 150 is a known rogue > > : density code 0x0, drive empty > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > : sd3(ncr0:5:0): Direct-Access > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > : sd3 could not mode sense (4). Using ficticious geometry > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > does not understand a mode sense to page 4?? Very strange! Again, no difference. > > > : 382MB (782600 512 byte sectors) > > : chip1 rev 3 on pci0:2 > > : vga0 rev 0 on pci0:6 > > : pci0: uses 8388864 bytes of memory from fb000000 upto fbfef0ff. > > : pci0: uses 256 bytes of I/O space from e800 upto e8ff. > > > > The IBM is a new acquisition and I removed all drives but the cdrom and the > > tape and it still didn't work. > > Of all the devices we have the most problem with it is CDROM and Tape drives, > I know this is probably painfull to remove these, but it will help to > track down the problem. > > > Could a jumper on the motherboard make a difference. I went through them to > > make sure they made sense. Perhaps I should again. I don't remember if I > > changed any or not. > > The board as shipped by me should have been set correctly, with perhaps > the exception of the SCSI terminator since you are running both internal > and external devices. Make sure you turned of the terminator on the > motherboard. > > > The bios are as you sent them. Standard but with write-through amd > > ISA gating disabled. > > Okay, good, that eliminates that set of questions! > > > I am rebuilding the boot floppy now and will try it tonight. If it fails, > > I will rebuild with the > > > > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers > > > > line removed and try that. > > Okay, thanks. Tried both. No difference! I hate to say it but AMD 486/40? I am removing drivers from the floppy to try and figure which one is the bad boy. Boyd > > > > > Why the restriction? > > Attempt to fix some people's system that hang during sync negotiation due > to devices that claim to be SCSI-2 compliant, but get this part of the > spec wrong. Also fixes some very old SCSI-I devices that lock up if > you try to do sync negotiation with them. It was suppose to make it > better, but it may infact be making things worse :-( > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 18:31:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA28745 for current-outgoing; Tue, 25 Apr 1995 18:31:43 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA28708 for ; Tue, 25 Apr 1995 18:31:03 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id UAA03807; Tue, 25 Apr 1995 20:30:49 -0500 Received: by olympus (4.1/TSS2.1) id AA05342; Tue, 25 Apr 95 20:30:55 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504260130.AA05342@olympus> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 25 Apr 1995 20:30:54 -0500 (CDT) Cc: phk@ref.tfs.com, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org In-Reply-To: <199504251831.LAA10452@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 25, 95 11:31:44 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1110 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. > > > > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 > > > > : sd3(ncr0:5:0): Direct-Access > > > > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > > : sd3 could not mode sense (4). Using ficticious geometry > > > > > > Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that > > > does not understand a mode sense to page 4?? Very strange! > > > > No, a "type 0" device ? doesn't make sense! > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > OK. I recompiled the boot floppy kernel numerous times and removing the wt0 and mcdX entries allows the probe to continue. I have not unplugged my IDE devices, wd0 and wd1. I can't log in as root though. Hmmm. cute. Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 25 18:48:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA29539 for current-outgoing; Tue, 25 Apr 1995 18:48:29 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA29533 for ; Tue, 25 Apr 1995 18:48:16 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA03577; Tue, 25 Apr 95 19:41:42 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504260141.AA03577@cs.weber.edu> Subject: Re: fcntl F_SETLK backward compatibility hack implemented To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Tue, 25 Apr 95 19:41:42 MDT Cc: current@FreeBSD.org, syssgm@devetir.qld.gov.au In-Reply-To: <199504250815.SAA15397@pandora.devetir.qld.gov.au> from "Stephen McKay" at Apr 25, 95 06:15:37 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > Well, since nobody objected :-) I went and implemented my proposed fix to > fcntl locking. Here are patches to sys/fcntl.h and kern/kern_descrip.c > plus two test programs. The 'break' program demonstrates how the scheme > can fail, and allows you to look at the pretty console warnings. > The ftest program sets a few random locks and checks for clashes. If any > console messages turn up, it has failed. I compile it on a 1.1.5 system > and a 2.0 system then run it like: > > $ ./ftest.1.1.5 & ./ftest.2.0 ; sleep 3 > 048901919: 374: OK F_WRLCK SEEK_CUR -3722 6989 == 2201 to 9189 > 048937427: 375: NO F_WRLCK SEEK_SET 6048 3952 == 6048 to 9999 > 048940850: 375: -> F_WRLCK SEEK_SET 2201 6989 == 2201 to 9189 PID:374 > 050970752: 375: OK F_WRLCK SEEK_SET 6048 3952 == 6048 to 9999 > 051003186: 374: OK F_WRLCK SEEK_CUR 33 1554 == 4191 to 5744 > ... > > This shows a microsecond timestamp, the pid, success/failure/reason, and > the expanded flock structure. > > I think the patch works well, and since it changes the real fcntl lock code > so little, it won't make things any worse! Coolness, Parker. 8-) 8-). If you're still in the neighborhood, could you add a long of 'sysid' to the flock structure, pass 0 for the local machine, and use the number to preterb the pid hash and lookup and compare it where you compare the pid? You should force the sysid to 0 for the F_SETLK, F_SETLKW, and F_GETLK calls, and implement F_RSETLK, F_RSETLKW, and F_RGETLK, which fail for non-root users and respect the passed 'sysid' for root users? This would be a good step towards lockd support. If it's too much of a pain, forget it and I'll probably hit it at some indefinite future date myself. Regards, Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Apr 25 19:27:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01200 for current-outgoing; Tue, 25 Apr 1995 19:27:16 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA01174 for ; Tue, 25 Apr 1995 19:26:29 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id DAA00223 for FreeBSD-current@FreeBSD.org; Wed, 26 Apr 1995 03:26:47 +0100 From: Paul Richards Message-Id: <199504260226.DAA00223@isl.cf.ac.uk> Subject: w and spurious idle times To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Wed, 26 Apr 1995 03:26:47 +0100 (BST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1199 Sender: current-owner@FreeBSD.org Precedence: bulk I have 'w' in my .login and I've recently started seeing spurious idle times when I login. Anyone else seeing this? 7:22PM up 9:46, 4 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT asami p0 silvia.HIP.Berke Tue03PM 4:07 -bash (bash) asami p1 silvia.HIP.Berke Tue03PM 4:06 /usr/local/bin/bash jkh p2 morton 5:17PM 20 -bash (bash) paul p3 isl-gate.elsy.cf 7:22PM 7 w That's as I login on thud, noway I've been idle 7 mins. It shows I've just logged in from the LOGIN time. Happens on all -current boxes. thud:~% w 7:24PM up 9:47, 4 users, load averages: 0.02, 0.01, 0.00 USER TTY FROM LOGIN@ IDLE WHAT asami p0 silvia.HIP.Berke Tue03PM 4:08 -bash (bash) asami p1 silvia.HIP.Berke Tue03PM 4:08 /usr/local/bin/bash jkh p2 morton 5:17PM 21 -bash (bash) paul p3 isl-gate.elsy.cf 7:22PM - w Then it's fine again? -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-current Wed Apr 26 01:01:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA14115 for current-outgoing; Wed, 26 Apr 1995 01:01:45 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA14095 for ; Wed, 26 Apr 1995 01:01:31 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA10941; Wed, 26 Apr 1995 17:57:58 +1000 Date: Wed, 26 Apr 1995 17:57:58 +1000 From: Bruce Evans Message-Id: <199504260757.RAA10941@godzilla.zeta.org.au> To: dufault@hda.com Subject: Re: panic: pmap_zero_page: CMAP busy Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >The panic is caused by the difference between these two lines in >the config: >>From GENERIC (works): >> config kernel root on wd0 swap on wd0 and wd1 and wd2 and vn0 dumps on wd0 >>From DESMOND (panics): >> config kernel root on wd0 swap on wd0 dumps on wd0 Maybe this has something to do with the bogus test for the end of swdevt[] in i386/autoconf.c. The array is terminated by device NODEV but device 0 is tested for (the test for > 0 degenerates to == 0 because dev_t is unsigned). Apparently there are usually 0's sufficiently close to the end of swdevt[] for there to be no problems. Bruce From owner-freebsd-current Wed Apr 26 05:53:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22832 for current-outgoing; Wed, 26 Apr 1995 05:53:51 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA22824 for ; Wed, 26 Apr 1995 05:53:41 -0700 Resent-Message-Id: <199504261253.FAA22824@freefall.cdrom.com> Received: by FileServ1.MI.Uni-Koeln.DE id AA26438 (5.67b/IDA-1.5 for current@freebsd.org); Wed, 26 Apr 1995 14:53:27 +0200 Resent-From: se@MI.Uni-Koeln.DE (Stefan Esser) Resent-Date: Wed, 26 Apr 1995 14:53:27 +0200 X-Mailer: Mail User's Shell (7.2.5 10/14/92) Resent-To: current@FreeBSD.org Received: by FileServ1.MI.Uni-Koeln.DE id AA26385 (5.67b/IDA-1.5 for se); Wed, 26 Apr 1995 14:51:01 +0200 Message-Id: <199504261251.AA26385@FileServ1.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Wed, 26 Apr 1995 14:51:00 +0200 In-Reply-To: "Rodney W. Grimes" "Re: Problem booting SNAP floppy on PCI/I-486SP3G" (Apr 25, 11:10) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G Sender: current-owner@FreeBSD.org Precedence: bulk On Apr 25, 11:10, "Rodney W. Grimes" wrote: } Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G } > > > I looked at the BOOTFLP config file in /sys/i386/conf and found this entry } > > > that I do not have in CATBURG. } > > > } > > > options "SCSI_NCR_MAX_SYNC=0" #Restrict NCR to asynch. transfers } > > > } > > > Could this be it? No, this just prevents the NCR from actively trying to negotiate synchronous transfers. Requests from the drive are answered as if the NCR lacked sync. transfer capabilities, and that reply is in conformance with SCSI-2. This was introduced to the boot floppy to make it come up even in the case of severe misconfiguration or drive problems. } > > Could be, but it worked here with the NCR810's on 4 different systems, } > > and I am using the same disk drive you have (only more of them :-)). } > > } > > Do you have anything besides the DEC3053L disk on you scsi bus now? I've tried the SNAP install on my SP3G and using a DEC DSP3053L. Had no problems at all. } > : ncr0: restart (scsi reset). } > : ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) } > : ncr0 waiting for scsi devices to settle } > : (ncr0:0:0): "CDC 94171-9 5955" type 0 fixed SCSI 1 } > : sd0(ncr0:0:0): Direct-Access 286MB (586458 512 byte sectors) } > : (ncr0:1:0): "MAXTOR MXT-1240S F02S" type 0 fixed SCSI 2 } > : sd1(ncr0:1:0): Direct-Access } > : sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } > : 1183MB (2423457 512 byte sectors) } > : (ncr0:2:0): "MAXTOR 7245-SCSI 1057" type 0 fixed SCSI 1 } > : sd2(ncr0:2:0): Direct-Access 234MB (479656 512 byte sectors) } > : (ncr0:3:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 } } Can you remove this easily? I have seen CD-ROM drives hang the } NCR code up :-(. And turning off the sync negotiation seems to } make the problem worse, not better :-(. Well, if you have seen it, then I guess you sent the drive brand and model for us to include it into the list of known rogues. It won't do you any harm thereafter :) There is a problem with some drives not accepting an IDENTIFY message at certain times, while most drives require it in just this situation. Taking the wrong choice may screw up the drive in such a way that only a SCSI bus reset helps ... CDROM, QIC tape and DAT manufacturers often have their own cost saving interpretation of the SCSI specs. :( } > : cd0(ncr0:3:0): CD-ROM cd present.[12571 x 2048 byte records] } > : (ncr0:4:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 } > : st0(ncr0:4:0): Sequential-Access st0: Archive Viper 150 is a known rogue } > : density code 0x0, drive empty } > : (ncr0:5:0): 200ns (5 Mb/sec) offset 8. } > : (ncr0:5:0): "IBM 0661467 G l" type 0 fixed SCSI 2 } > : sd3(ncr0:5:0): Direct-Access } > : sd3(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB } > : sd3 could not mode sense (4). Using ficticious geometry } } Ahhh.. and unplug this guy too, it seems to be a SCSI 2 device that } does not understand a mode sense to page 4?? Very strange! Have seen this with an IBM 400MB drive that once lived inside an RS/6000 ... Glad we got rid of them. } > The IBM is a new acquisition and I removed all drives but the cdrom and the } > tape and it still didn't work. } } Of all the devices we have the most problem with it is CDROM and Tape drives, } I know this is probably painfull to remove these, but it will help to } track down the problem. True. But please send mail to my e-mail address and tell about drives that didn't work with the NCR ! We don't have a chance to get them supported, else. If we knew a generic solution, we were glad to implement it. But we didn't find any ... } > Why the restriction? } } Attempt to fix some people's system that hang during sync negotiation due } to devices that claim to be SCSI-2 compliant, but get this part of the } spec wrong. Also fixes some very old SCSI-I devices that lock up if } you try to do sync negotiation with them. It was suppose to make it } better, but it may infact be making things worse :-( If it really makes things worse, then please send details. We are religious about this change, but it seemed to increase the chance of getting through the first phase of a system install. Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Wed Apr 26 05:57:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22929 for current-outgoing; Wed, 26 Apr 1995 05:57:49 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA22923 for ; Wed, 26 Apr 1995 05:57:48 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <14282-0@bunyip.cc.uq.oz.au>; Wed, 26 Apr 1995 22:57:15 +1000 Received: by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) id WAA28305; Wed, 26 Apr 1995 22:16:15 +1000 From: Stephen McKay Message-Id: <199504261216.WAA28305@pandora.devetir.qld.gov.au> To: terry@cs.weber.edu (Terry Lambert) cc: syssgm@devetir.qld.gov.au (Stephen McKay), current@FreeBSD.org Subject: Re: fcntl F_SETLK backward compatibility hack implemented In-reply-to: Your message of Tue, 25 Apr 95 19:41:42. <9504260141.AA03577@cs.weber.edu> Date: Wed, 26 Apr 95 22:16:13 EST Sender: current-owner@FreeBSD.org Precedence: bulk terry@cs.weber.edu (Terry Lambert) wrote: >syssgm@devetir.qld.gov.au (Stephen McKay) wrote: >> Well, since nobody objected :-) I went and implemented my proposed fix to >> fcntl locking. > >Coolness, Parker. 8-) 8-). Pardon? I'm hip and groovy, but who's Parker? :-( >If you're still in the neighborhood, could you add a long of 'sysid' >to the flock structure, pass 0 for the local machine, and use the number >to preterb the pid hash and lookup and compare it where you compare >the pid? > >You should force the sysid to 0 for the F_SETLK, F_SETLKW, and F_GETLK >calls, and implement F_RSETLK, F_RSETLKW, and F_RGETLK, which fail >for non-root users and respect the passed 'sysid' for root users? > >This would be a good step towards lockd support. Well, stick my head out and have it run over by a bus! Ok, if we add 'sysid' to struct flock it will change size and we'll need more backward compatibility stuff in fcntl(). Looks like we'll need flock_43 for the 1.1.5 version and flock_44 for the 2.0 version and a slightly more complicated backward compatibility patch. So, should we strike while the iron is hot? >If it's too much of a pain, forget it and I'll probably hit it at some >indefinite future date myself. Now looks like the best time to me. Stephen. From owner-freebsd-current Wed Apr 26 06:50:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA24751 for current-outgoing; Wed, 26 Apr 1995 06:50:05 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA24745 for ; Wed, 26 Apr 1995 06:50:03 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id JAA27705; Wed, 26 Apr 1995 09:47:55 -0400 From: Peter Dufault Message-Id: <199504261347.JAA27705@hda.com> Subject: Re: panic: pmap_zero_page: CMAP busy To: bde@zeta.org.au (Bruce Evans) Date: Wed, 26 Apr 1995 09:47:54 -0400 (EDT) Cc: current@freefall.cdrom.com In-Reply-To: <199504260757.RAA10941@godzilla.zeta.org.au> from "Bruce Evans" at Apr 26, 95 05:57:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1433 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > > >The panic is caused by the difference between these two lines in > >the config: > > >>From GENERIC (works): > >> config kernel root on wd0 swap on wd0 and wd1 and wd2 and vn0 dumps on wd0 > > >>From DESMOND (panics): > >> config kernel root on wd0 swap on wd0 dumps on wd0 > > Maybe this has something to do with the bogus test for the end of > swdevt[] in i386/autoconf.c. The array is terminated by device NODEV > but device 0 is tested for (the test for > 0 degenerates to == 0 > because dev_t is unsigned). Apparently there are usually 0's sufficiently > close to the end of swdevt[] for there to be no problems. This is not reproducible. The scarey thing is it persisted through two full kernel builds, including the directory removal. The building was done on my production system so it isn't anything quirky about the new system. It went away when I reverted to GENERIC and stayed away as I slowly moved it back to the original reduced config. I stupidly didn't save the original config, but I'm 90% sure I now have the exact same reduced configuration I originally did and I'm not getting any problems. Now if I can figure out why it can't find the BOCA BB1008 multiport serial card at 0x100 - 0x138 IRQ12 ... Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Wed Apr 26 15:31:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA29370 for current-outgoing; Wed, 26 Apr 1995 15:31:31 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA29363 for ; Wed, 26 Apr 1995 15:31:26 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA09621; Wed, 26 Apr 95 16:19:47 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504262219.AA09621@cs.weber.edu> Subject: Re: fcntl F_SETLK backward compatibility hack implemented To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Wed, 26 Apr 95 16:19:46 MDT Cc: syssgm@devetir.qld.gov.au, current@FreeBSD.org In-Reply-To: <199504261216.WAA28305@pandora.devetir.qld.gov.au> from "Stephen McKay" at Apr 26, 95 10:16:13 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > >> Well, since nobody objected :-) I went and implemented my proposed fix to > >> fcntl locking. > > > >Coolness, Parker. 8-) 8-). > > Pardon? I'm hip and groovy, but who's Parker? :-( I see you don't get quite all of the US television down under. Good, it means I still want to visit Australia. 8-). There's a TV series called "Parker Lewis Can't Lose" which is sort of a "Ferris Buehler's Day off made into a TV series. Any time Parker comes up with an idea bound to get them into trouble, one of his friends says "Coolness, Parker" to encourage him to go ahead with it. 8-). > >This would be a good step towards lockd support. > > Well, stick my head out and have it run over by a bus! I should have honked. 8-). > Ok, if we add 'sysid' to struct flock it will change size and we'll need > more backward compatibility stuff in fcntl(). Looks like we'll need > flock_43 for the 1.1.5 version and flock_44 for the 2.0 version and a > slightly more complicated backward compatibility patch. > > So, should we strike while the iron is hot? In for a penny, in for a pound... 8-). I think you are the new file system locking semantics and compatability guru (self elected). 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Apr 26 17:38:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA03358 for current-outgoing; Wed, 26 Apr 1995 17:38:29 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA03352 for ; Wed, 26 Apr 1995 17:38:27 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id RAA13949; Wed, 26 Apr 1995 17:37:53 -0700 From: Poul-Henning Kamp Message-Id: <199504270037.RAA13949@ref.tfs.com> Subject: Re: panic: pmap_zero_page: CMAP busy To: bde@zeta.org.au (Bruce Evans) Date: Wed, 26 Apr 1995 17:37:53 -0700 (PDT) Cc: dufault@hda.com, current@freefall.cdrom.com In-Reply-To: <199504260757.RAA10941@godzilla.zeta.org.au> from "Bruce Evans" at Apr 26, 95 05:57:58 pm Content-Type: text Content-Length: 886 Sender: current-owner@FreeBSD.org Precedence: bulk > >The panic is caused by the difference between these two lines in > >the config: > > >>From GENERIC (works): > >> config kernel root on wd0 swap on wd0 and wd1 and wd2 and vn0 dumps on wd0 > > >>From DESMOND (panics): > >> config kernel root on wd0 swap on wd0 dumps on wd0 > > Maybe this has something to do with the bogus test for the end of > swdevt[] in i386/autoconf.c. The array is terminated by device NODEV > but device 0 is tested for (the test for > 0 degenerates to == 0 > because dev_t is unsigned). Apparently there are usually 0's sufficiently > close to the end of swdevt[] for there to be no problems. Be aware that the two termination entries are needed for diskless to work... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed Apr 26 18:32:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA05118 for current-outgoing; Wed, 26 Apr 1995 18:32:38 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA05104 for ; Wed, 26 Apr 1995 18:32:25 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA06056; Thu, 27 Apr 1995 11:29:27 +1000 Date: Thu, 27 Apr 1995 11:29:27 +1000 From: Bruce Evans Message-Id: <199504270129.LAA06056@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@ref.tfs.com Subject: Re: panic: pmap_zero_page: CMAP busy Cc: current@freefall.cdrom.com, dufault@hda.com Sender: current-owner@FreeBSD.org Precedence: bulk >> Maybe this has something to do with the bogus test for the end of >> swdevt[] in i386/autoconf.c. The array is terminated by device NODEV >> but device 0 is tested for (the test for > 0 degenerates to == 0 >Be aware that the two termination entries are needed for diskless to work... I think the first one is terminal as far as autoconf.c is concerned. Bruce From owner-freebsd-current Wed Apr 26 20:52:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA12687 for current-outgoing; Wed, 26 Apr 1995 20:52:24 -0700 Received: from Adonis.Dorm10.NCTU.edu.tw (Adonis.Dorm10.NCTU.edu.tw [140.113.145.84]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA12645 for ; Wed, 26 Apr 1995 20:52:01 -0700 Received: (from jdli@localhost) by Adonis.Dorm10.NCTU.edu.tw (8.6.11/8.6.9) id LAA15348 for freebsd-current@FreeBSD.ORG; Thu, 27 Apr 1995 11:52:26 +0800 From: ¾K¥Í¹Ú¦º µL¨¥¥H¹ï Message-Id: <199504270352.LAA15348@Adonis.Dorm10.NCTU.edu.tw> Subject: QUOTA on 0412-SNAP To: freebsd-current@FreeBSD.org Date: Thu, 27 Apr 1995 11:52:26 +0800 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 877 Sender: current-owner@FreeBSD.org Precedence: bulk hi : I think 0412-SNAP has bug in quota system about the "blocks" field.. when I type quota -v, it shows.. Disk quotas for user jdli (uid 10000): Filesystem blocks quota limit grace files quota limit grace /usr/local 19856 32 0 (null) 474 0 0 and when I edquota -u jdli as.. Quotas for user jdli: /usr/local: blocks in use: 19856, limits (soft = 10, hard = 20) inodes in use: 474, limits (soft = 10, hard = 20) quota -v shows.. Disk quotas for user jdli (uid 10000): Filesystem blocks quota limit grace files quota limit grace /usr/local 19856 42 10 (null) 474* 10 20 7days then I edquota -u jdli again...it shows.. Quotas for user jdli: /usr/local: blocks in use: 19856, limits (soft = 0, hard = 10) inodes in use: 474, limits (soft = 10, hard = 20) From owner-freebsd-current Wed Apr 26 23:38:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA21158 for current-outgoing; Wed, 26 Apr 1995 23:38:01 -0700 Received: from zibbi.mikom.csir.co.za (some.schmuck.lame.delegated.to.RAIN.PSG.COM [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA21130 for ; Wed, 26 Apr 1995 23:37:44 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id IAA27490 for current@FreeBSD.ORG; Thu, 27 Apr 1995 08:37:29 +0200 From: John Hay Message-Id: <199504270637.IAA27490@zibbi.mikom.csir.co.za> Subject: src/Makefile includes target incomplete To: current@FreeBSD.org (FreeBSD-current) Date: Thu, 27 Apr 1995 08:37:29 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 711 Sender: current-owner@FreeBSD.org Precedence: bulk With the ctm I received this morning, pkg_install won't compile anymore. On inspection I found that "Make includes" in /usr/src does not go into libftp. So I were compiling with an old FtpLibrary.h. Here is a patch for that. -- John Hay -- jhay@mikom.csir.co.za *** src/Makefile.org Tue Mar 28 20:14:17 1995 --- src/Makefile Thu Apr 27 08:30:57 1995 *************** *** 226,231 **** --- 226,232 ---- cd ${.CURDIR}/lib/libss && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libforms && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libscsi && ${MAKE} beforeinstall + cd ${.CURDIR}/lib/libftp && ${MAKE} beforeinstall lib-tools: @echo "--------------------------------------------------------------" From owner-freebsd-current Thu Apr 27 09:40:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23486 for current-outgoing; Thu, 27 Apr 1995 09:40:28 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA23431 ; Thu, 27 Apr 1995 09:39:36 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id JAA08071; Thu, 27 Apr 1995 09:39:02 -0700 Message-Id: <199504271639.JAA08071@precipice.shockwave.com> To: current@FreeBSD.org, hackers@FreeBSD.org cc: phk@FreeBSD.org Subject: looking for IP over printer port driver users Date: Thu, 27 Apr 1995 09:38:57 -0700 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk Do you currently use the lp driver for connecting two freebsd systems together ala laplink? Do you have it already running? I've rewritten the driver to be a tad less insane but I myself can't use the LPIP protocol that Jolitz designed because I don't have two BSD boxes with parallel ports available. I'm looking for one or two folks who already know about the lp driver and use it often to simply check out my rewrite of the driver to see if I've introduced any timing bugs or other oddities. Once I know the rewritten driver is happy, I'll be adding support for the Crynwr/Linux PLIP protocol format. Thanks, Paul From owner-freebsd-current Thu Apr 27 10:11:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24725 for current-outgoing; Thu, 27 Apr 1995 10:11:14 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA24710 ; Thu, 27 Apr 1995 10:11:05 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA13917; Thu, 27 Apr 95 11:04:38 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504271704.AA13917@cs.weber.edu> Subject: Current list offline? To: pst@shockwave.com (Paul Traina) Date: Thu, 27 Apr 95 11:04:37 MDT Cc: current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199504271639.JAA08071@precipice.shockwave.com> from "Paul Traina" at Apr 27, 95 09:38:57 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk I just got a message cc'ed to hackers and current, but I only got it one time. I noticed this because my mail volume was teeny today. Apparently I'm still getting hackers and questions. Is the reduced mail volume from a list failure, or is it from people actually taking the mento discussion offline or something? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Apr 27 11:09:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA27008 for current-outgoing; Thu, 27 Apr 1995 11:09:13 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26973 ; Thu, 27 Apr 1995 11:08:58 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA17131; Thu, 27 Apr 1995 11:08:52 -0700 From: Poul-Henning Kamp Message-Id: <199504271808.LAA17131@ref.tfs.com> Subject: Re: looking for IP over printer port driver users To: pst@shockwave.com (Paul Traina) Date: Thu, 27 Apr 1995 11:08:51 -0700 (PDT) Cc: current@FreeBSD.org, hackers@FreeBSD.org, phk@FreeBSD.org In-Reply-To: <199504271639.JAA08071@precipice.shockwave.com> from "Paul Traina" at Apr 27, 95 09:38:57 am Content-Type: text Content-Length: 882 Sender: current-owner@FreeBSD.org Precedence: bulk > Do you currently use the lp driver for connecting two freebsd systems together > ala laplink? Do you have it already running? I wrote it :-) > I've rewritten the driver to be a tad less insane but I myself can't use the > LPIP protocol that Jolitz designed because I don't have two BSD boxes with > parallel ports available. Jolitz didn't do this, I did. > I'm looking for one or two folks who already know about the lp driver and > use it often to simply check out my rewrite of the driver to see if I've > introduced any timing bugs or other oddities. Sure, send it to me. > Once I know the rewritten driver is happy, I'll be adding support for the > Crynwr/Linux PLIP protocol format. CooL! -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Thu Apr 27 11:51:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA28688 for current-outgoing; Thu, 27 Apr 1995 11:51:16 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA28682 for ; Thu, 27 Apr 1995 11:51:15 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id LAA03949 for ; Thu, 27 Apr 1995 11:51:15 -0700 Message-Id: <199504271851.LAA03949@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: aic7xxx Adapter support Date: Thu, 27 Apr 1995 11:51:14 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk I just commited a sweeping change to the aic7xxx sequencer code. This should fix the "device busy" problems that were reported with micropolis drives as well as make the card respect devices that win arbitration (there were cases that it would miss seeing the sucessful arbitration of another device and force re-arbitration - yuck!). The changes were tested on wcarchive which has drives from seagate, quantum and micropolis, so its hoped that this wont break anything, but if it does, I'd like to hear about it before 2.0.5 is released. So, if you use one of these cards, please try out the new driver. Thanks __ Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Thu Apr 27 14:12:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03688 for current-outgoing; Thu, 27 Apr 1995 14:12:45 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03677 ; Thu, 27 Apr 1995 14:12:23 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.6) id XAA00586; Thu, 27 Apr 1995 23:11:59 +0200 From: John Hay Message-Id: <199504272111.XAA00586@zibbi.mikom.csir.co.za> Subject: pkg_install does not compile To: current@FreeBSD.org (FreeBSD-current) Date: Thu, 27 Apr 1995 23:11:58 +0200 (SAT) Cc: jkh@FreeBSD.org X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 679 Sender: current-owner@FreeBSD.org Precedence: bulk It looks like there was a typo with the last changes to pkg_install. Here is what I think it should be: -- John Hay -- jhay@mikom.csir.co.za *** src/usr.sbin/pkg_install/add/perform.c.org Thu Apr 27 18:28:35 1995 --- src/usr.sbin/pkg_install/add/perform.c Thu Apr 27 23:04:44 1995 *************** *** 320,326 **** p ? p->name : "/"); if (!Fake) vsystem("/usr/sbin/mtree -u -f %s -d -e -p %s", ! MTREE_FNAME, p ? p->name : "/")) unlink(MTREE_FNAME); } --- 320,326 ---- p ? p->name : "/"); if (!Fake) vsystem("/usr/sbin/mtree -u -f %s -d -e -p %s", ! MTREE_FNAME, p ? p->name : "/"); unlink(MTREE_FNAME); } From owner-freebsd-current Thu Apr 27 15:55:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08142 for current-outgoing; Thu, 27 Apr 1995 15:55:04 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA08127 for ; Thu, 27 Apr 1995 15:54:51 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <43037>; Fri, 28 Apr 1995 00:54:23 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id OAA01876; Thu, 27 Apr 1995 14:14:18 +0200 Date: Thu, 27 Apr 1995 14:14:18 +0200 From: Julian Howard Stacey Message-Id: <199504271214.OAA01876@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: sendmail.cf "Smart" relay host Cc: stuart@vector.eikon.e-technik.tu-muenchen.de Sender: current-owner@FreeBSD.org Precedence: bulk Just to say Thanks again for the folks who reccomended I use DS as in DSeikon.regent.e-technik.tu-muenchen.de in my /etc/sendmail.cf file it works a treat, my outgoing mqueue flushes really fast now, no long waits anymore, keeping the modem line open (& paying phone company) just to flush the outgoing spool. Of course the wait for incoming sup went away when I converted to Poul-Henning'sCTM (patches by email), the 2 together should significantly reduce the phone bill :-) Thanks Guys :-) I reccomend both to anyone with high phone bills :-) Julian S Munich From owner-freebsd-current Thu Apr 27 20:22:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA22870 for current-outgoing; Thu, 27 Apr 1995 20:22:27 -0700 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA22864 for ; Thu, 27 Apr 1995 20:22:24 -0700 Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id XAA04974 for current@freebsd.org; Thu, 27 Apr 1995 23:22:00 -0400 Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id UAA16200; Thu, 27 Apr 1995 20:15:29 -0400 Date: Thu, 27 Apr 1995 20:15:29 -0400 From: Gene Stark Message-Id: <199504280015.UAA16200@starkhome.cs.sunysb.edu> To: current@FreeBSD.org Subject: Disk slicing problems Sender: current-owner@FreeBSD.org Precedence: bulk Over the past week or two, I have been trying to get various systems here bootstrapped over to the new disk slicing code. I have to say, I haven't fully understood it yet, and there are some serious problems I have come up against. Perhaps somebody (Bruce?) can tell me what I am missing: (1) Though I can mount, say /dev/wd0s4e, /dev/wd0s4f on /usr and /local, I am not yet able to use /dev/wd0s4a as / and /dev/wd0s4b as swap. Is this supported? Do I have to do something special in the kernel config, like change "root on wd0" to "root on wd0s4"? (2) After having gotten a kernel booted with disk slicing turned on, I find that I am unable to modify the MBR, and I am also unable to perform certain modifications to the disklabel. My understanding was that I am supposed to be able to use /dev/rwd0 as "the whole disk", and thus access and modify the MBR that way. However, when I try, say, "fdisk -u /dev/rwd0" it fails to write the MBR, complaining that the operation is not supported. Also, whereas under older kernels I was able to perform various kinds of "dangerous" modifications to the disklabel while the system is up, I can no longer do this. For example, I had my BSD slice starting at offset 1, with the a partition starting at offset 1008. I wanted to shrink the BSD slice so that it starts at offset 1008 to coincide with the start of the a partition, but there seems to be no way to do this once the initial slice table and disklabel have been written. Any attempt to change the disklabel in this way results in a complaint that the "change would shrink an open partition". This even happened while booted from the SCSI drive and attempting to modify the wd disklabel. I had to revert to an old kernel with no disk slicing, change the MBR and disklabel, then reboot the new kernel. In summary, I would like to be able to make these "dangerous" modifications, as long as I am willing to accept whatever consequences accrue from making them on the fly. Typically, what I would want to do is rewrite the MBR and disklabel, then reboot immediately if I moved the root area or something. The current system of interlocks seems to effectively prevent me from doing anything except reloading my entire disk from scratch. (3) I do not understand what the current wisdom is as far as laying out BSD partitions with respect to cylinder boundaries. With the advent of disk slicing, the disklabel now seems to be "relativized" to the beginning of the slice, with the effect that it gets very confused about what starts at a cylinder boundary and what does not. I am not particularly thrilled about this relativization; I would prefer it if the display were made the old way, but if you weren't supposed to enter values outside the slice the disk drivers simply prevented you from changing the disklabel to that. - Gene From owner-freebsd-current Thu Apr 27 21:17:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA27632 for current-outgoing; Thu, 27 Apr 1995 21:17:54 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA27626 ; Thu, 27 Apr 1995 21:17:54 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id VAA01128; Thu, 27 Apr 1995 21:17:19 -0700 X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol To: John Hay cc: current@FreeBSD.org (FreeBSD-current), jkh@FreeBSD.org Subject: Re: pkg_install does not compile In-reply-to: Your message of "Sat, 27 Apr 1995 23:11:58 +0200." <199504272111.XAA00586@zibbi.mikom.csir.co.za> Date: Thu, 27 Apr 1995 21:17:19 -0700 Message-ID: <1126.799042639@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > It looks like there was a typo with the last changes to pkg_install. Here is > what I think it should be: Thanks. Too sleepy! :-) I actually fixed this by putting the mtree return code check back but using -U, as Rod suggested. Jordan From owner-freebsd-current Thu Apr 27 22:13:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA28649 for current-outgoing; Thu, 27 Apr 1995 22:13:22 -0700 Received: from virgo ([140.109.40.247]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA28642 ; Thu, 27 Apr 1995 22:13:19 -0700 Received: (from taob@localhost) by virgo (8.6.11/8.6.9) id NAA00221; Fri, 28 Apr 1995 13:13:45 +0800 Date: Fri, 28 Apr 1995 13:13:44 +0800 (CST) From: Brian Tao To: Terry Lambert cc: Paul Traina , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Current list offline? In-Reply-To: <9504271704.AA13917@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Thu, 27 Apr 1995, Terry Lambert wrote: > > I noticed this because my mail volume was teeny today. Apparently > I'm still getting hackers and questions. I noticed the same thing too... only 9 messages on -current in the past 24 hours. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Thu Apr 27 22:33:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA29311 for current-outgoing; Thu, 27 Apr 1995 22:33:37 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA29296 for ; Thu, 27 Apr 1995 22:33:11 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA19697; Fri, 28 Apr 1995 15:27:25 +1000 Date: Fri, 28 Apr 1995 15:27:25 +1000 From: Bruce Evans Message-Id: <199504280527.PAA19697@godzilla.zeta.org.au> To: current@FreeBSD.org, gene@starkhome.cs.sunysb.edu Subject: Re: Disk slicing problems Sender: current-owner@FreeBSD.org Precedence: bulk > (1) Though I can mount, say /dev/wd0s4e, /dev/wd0s4f on > /usr and /local, I am not yet able to use /dev/wd0s4a > as / and /dev/wd0s4b as swap. Is this supported? > Do I have to do something special in the kernel config, > like change "root on wd0" to "root on wd0s4"? If you only have one FreeBSD partition, then you can continue to use wd0[a-h]. You can also continue to use these for the first of multiple FreeBSD partitions. If you have more than one, or just want use explicit slices, then you have to do something special: For swapping, something like "swap on wd0s4" is required and is supposed to work (it hasn't been tested much). A better solution is required. Already the swap list has to have all devices that you might want to swap on. Multiply this by up to 30 slices per device and the list is much too long. Booting from wd0s4 is not fully supported. The bootstrap passes the slice number but autoconfig.c neglects to use it, so only booting from the first slice works. The root device in normally autoconfig'ed to the root device, so it is hard to use wd0s4 for root. My fix for this got mixed up with correcting the floppy minor numbering and the time never seemed right to commit it. I haven't been using it either. > (2) After having gotten a kernel booted with disk slicing > turned on, I find that I am unable to modify the MBR, > and I am also unable to perform certain modifications > to the disklabel. My understanding was that I am > supposed to be able to use /dev/rwd0 as "the whole disk", > and thus access and modify the MBR that way. However, > when I try, say, "fdisk -u /dev/rwd0" it fails to write > the MBR, complaining that the operation is not supported. Here it has no problem writing the MBR, but it complains about not being able to write the possibly-modified label back to rwd0. There is no label on the disk for rwd0 and changing the dummy in-core label doesn't make much sense. The ioctl actually returns ENODEV, and disklabel(8) doesn't know what this means. > Also, whereas under older kernels I was able to perform > various kinds of "dangerous" modifications to the disklabel > while the system is up, I can no longer do this. You can probably still do this by running `open("/dev/rwd0", 0); sleep(~0u);' > For example, I had my BSD slice starting at offset 1, > with the a partition starting at offset 1008. I wanted > to shrink the BSD slice so that it starts at offset 1008 > to coincide with the start of the a partition, but there > seems to be no way to do this once the initial slice > table and disklabel have been written. Any attempt to Shrinking the slice in the MBR would work right provided no minors other than rwd0 are open. You would get a message about the C partition being too large and being shrunk when a minor is opened later (after rwd0 is closed). > change the disklabel in this way results in a complaint > that the "change would shrink an open partition". Well, it is open. setdisklabel() has always carefully checked for open partitions, but previous drivers lied to it and said that no partitions are open. There is obviously a problem handling the parition that you unfortunately have to have open to do an ioctl() on it. Perhaps drivers should pretend that the C partition is not open. However, it's not clear that changing the size of the C partition or the slice size should be allowed at all. These sizes are normally inherited from the DOSpartition table and are restricted by it. However^2, reducing them was supposed to work. We currently have better utilities for managing labels than slices. > In summary, I would like to be able to make these "dangerous" > modifications, as long as I am willing to accept whatever > consequences accrue from making them on the fly. Typically, > what I would want to do is rewrite the MBR and disklabel, > then reboot immediately if I moved the root area or something. > The current system of interlocks seems to effectively > prevent me from doing anything except reloading my entire > disk from scratch. The correct technique is: a) Close all minors on the disk. If the disk has your root partition then you will have to boot from another disk or possibly another slice on the same disk if you only want to do dangerous mods to the first slice. If the disk has swap activated on it, then reboot and don't activate swap. (BTW, I fixed(?) the disk close routines to not keep open swap partitions (activated or not). This makes it possible to close all minors on the disk provided all swap partitions on the disk are inactive. However, the vm system apparently caches the swap sizes (it has to for pstat -s to report inactive swap), so there would be big problems if you shrunk or moved the swap partition and then used it.) b) Change the MBR. c) Change all labels. Be careful to delete or fix all old labels that have reappeared or been invalidated by step (b). The interlocking is currently not complete, so you can do step (b) without affecting anything if some minor is open. This will be fixed using the new unfinished DIOCSYNCSLICES ioctl() in fdisk. The ioctl() may fail if some minors are open, but fdisk will be able to tell. > (3) I do not understand what the current wisdom is as far as > laying out BSD partitions with respect to cylinder boundaries. > With the advent of disk slicing, the disklabel now seems > to be "relativized" to the beginning of the slice, with > the effect that it gets very confused about what starts > at a cylinder boundary and what does not. I am not If cylinder boundaries matter, then all slices should be started on them. > particularly thrilled about this relativization; I would Neither am I. I'll think about changing this. There is probably more slice code to delete than old code to fix. Bruce From owner-freebsd-current Fri Apr 28 05:21:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11262 for current-outgoing; Fri, 28 Apr 1995 05:21:36 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA11256 for ; Fri, 28 Apr 1995 05:21:32 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id IAA08101; Fri, 28 Apr 1995 08:20:15 -0400 From: Peter Dufault Message-Id: <199504281220.IAA08101@hda.com> Subject: LINT will fail to build To: current@FreeBSD.org Date: Fri, 28 Apr 1995 08:20:14 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 469 Sender: current-owner@FreeBSD.org Precedence: bulk Unfortunately I had an extra copy of "aio.h" on my system when I tested things. This means that a build of LINT will fail looking for "aio.h" in "sys/i386/isa/labpc.c" until the changes I put in make their way around. The temporary fix is to change the include from "aio.h" to . Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 06:56:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA14066 for current-outgoing; Fri, 28 Apr 1995 06:56:58 -0700 Received: from obiwan.pmr.com (obiwan.pmr.com [199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA14054 for ; Fri, 28 Apr 1995 06:56:47 -0700 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0s4qWv-000308C; Fri, 28 Apr 95 08:56 CDT Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: aic7xxx Adapter support To: gibbs@estienne.CS.Berkeley.EDU (Justin T. Gibbs) Date: Fri, 28 Apr 1995 08:56:25 -0500 (CDT) Cc: current@FreeBSD.org In-Reply-To: <199504271851.LAA03949@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Apr 27, 95 11:51:14 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1441 Sender: current-owner@FreeBSD.org Precedence: bulk Justin T. Gibbs wrote: > > I just commited a sweeping change to the aic7xxx sequencer code. This > should fix the "device busy" problems that were reported with micropolis > drives as well as make the card respect devices that win arbitration > (there were cases that it would miss seeing the sucessful arbitration > of another device and force re-arbitration - yuck!). The changes were > tested on wcarchive which has drives from seagate, quantum and micropolis, > so its hoped that this wont break anything, but if it does, I'd like > to hear about it before 2.0.5 is released. So, if you use one of these > cards, please try out the new driver. Justin, I tried the latest kernel (from this mornings CTM) on my 2740 and Exabyte 8200 tape drive. I dumped one of my filesystems to the tape and everything was going fine till it got all done and rewound the tape. At that point I go the following sequence of messages on the console, followed by a system hang (no panic, just hang): ahc0: Target Busy ahc0: Target 6, lun0 (st2) timed out ahc0: Target 6, lun0 (st2) timed out ahc0: Target 6, lun0 (st2) timed out ahc0: Target 6, lun0 (st2) timed out Thought you'd like to know. Let me know if there is anything I can do to help track it down. Note the tape did in fact successfully rewind and the drive allowed me to remove it (whilst the system was hung). -- Bob Willcox bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-current Fri Apr 28 10:55:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19673 for current-outgoing; Fri, 28 Apr 1995 10:55:01 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA19664 for ; Fri, 28 Apr 1995 10:54:56 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id NAA09952; Fri, 28 Apr 1995 13:53:38 -0400 From: Peter Dufault Message-Id: <199504281753.NAA09952@hda.com> Subject: Where to put data base file To: freebsd-current@FreeBSD.org Date: Fri, 28 Apr 1995 13:53:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 989 Sender: current-owner@FreeBSD.org Precedence: bulk Where do I put this ASCII data base file? It can be used by /sbin/scsi to permit you to get and set SCSI mode pages, so for that reason it could go in "/etc/scsi_modes". However, the scsi program works without this so it can also go somewhere in /usr/share if we don't think symboloic setting and getting of mode pages is something that must be done out of a minimal boot. > # SCSI mode page data base. > > # Caching page: > 0x08 { > {Reserved} b5 > {WCE} b1 > {MF} b1 > {RCD} b1 > {Demand Retention Priority} b4 > {Write Retention Priority} b4 > {Disable Pre-fetch Transfer Length} i2 > {Minumum Pre-fetch} i2 > {Maximum Pre-fetch} i2 > {Maximum Pre-fetch Ceiling} i2 > } > > # Format device page: > 0x03 { > {Tracks per Zone} i2 > {Alternate Sectors per Zone} i2 > {Alternate Tracks per Zone} i2 ... -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 11:17:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20117 for current-outgoing; Fri, 28 Apr 1995 11:17:06 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA20111 for ; Fri, 28 Apr 1995 11:17:04 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA21619; Fri, 28 Apr 1995 11:16:01 -0700 From: Poul-Henning Kamp Message-Id: <199504281816.LAA21619@ref.tfs.com> Subject: Re: Where to put data base file To: dufault@hda.com (Peter Dufault) Date: Fri, 28 Apr 1995 11:16:01 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504281753.NAA09952@hda.com> from "Peter Dufault" at Apr 28, 95 01:53:37 pm Content-Type: text Content-Length: 198 Sender: current-owner@FreeBSD.org Precedence: bulk /usr/share/scsi -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Fri Apr 28 11:20:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20235 for current-outgoing; Fri, 28 Apr 1995 11:20:57 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA20229 for ; Fri, 28 Apr 1995 11:20:51 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA06619; Fri, 28 Apr 1995 11:17:48 -0700 From: "Rodney W. Grimes" Message-Id: <199504281817.LAA06619@gndrsh.aac.dev.com> Subject: Re: Where to put data base file To: dufault@hda.com (Peter Dufault) Date: Fri, 28 Apr 1995 11:17:47 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504281753.NAA09952@hda.com> from "Peter Dufault" at Apr 28, 95 01:53:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 796 Sender: current-owner@FreeBSD.org Precedence: bulk > > Where do I put this ASCII data base file? It can be used by > /sbin/scsi to permit you to get and set SCSI mode pages, so for > that reason it could go in "/etc/scsi_modes". > > However, the scsi program works without this so it can also go > somewhere in /usr/share if we don't think symboloic setting and > getting of mode pages is something that must be done out of a > minimal boot. I would say it falls in about the same class of things as /etc/termcap, which CSRG moved to /usr/share/misc. And we added a backwards compatibility hack by symlinking /etc/termcap to it. Let's put this *wonderful* scsi file in /usr/share/misc. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Fri Apr 28 12:54:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA23356 for current-outgoing; Fri, 28 Apr 1995 12:54:34 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA23350 for ; Fri, 28 Apr 1995 12:54:33 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id MAA00298; Fri, 28 Apr 1995 12:54:28 -0700 Message-Id: <199504281954.MAA00298@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: bob@obiwan.pmr.com (Bob Willcox) cc: current@FreeBSD.org Subject: Re: aic7xxx Adapter support In-reply-to: Your message of "Fri, 28 Apr 1995 08:56:25 CDT." Date: Fri, 28 Apr 1995 12:54:28 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >Justin T. Gibbs wrote: >> >> I just commited a sweeping change to the aic7xxx sequencer code. This >> should fix the "device busy" problems that were reported with micropolis >> drives as well as make the card respect devices that win arbitration >> (there were cases that it would miss seeing the sucessful arbitration >> of another device and force re-arbitration - yuck!). The changes were >> tested on wcarchive which has drives from seagate, quantum and micropolis, >> so its hoped that this wont break anything, but if it does, I'd like >> to hear about it before 2.0.5 is released. So, if you use one of these >> cards, please try out the new driver. > >Justin, I tried the latest kernel (from this mornings CTM) on my 2740 >and Exabyte 8200 tape drive. I dumped one of my filesystems to the tape >and everything was going fine till it got all done and rewound the tape. >At that point I go the following sequence of messages on the console, >followed by a system hang (no panic, just hang): > >ahc0: Target Busy >ahc0: Target 6, lun0 (st2) timed out >ahc0: Target 6, lun0 (st2) timed out >ahc0: Target 6, lun0 (st2) timed out >ahc0: Target 6, lun0 (st2) timed out When was the last time you updated your kernel before last night? I'm just wondering if you had run a kernel with Peter's tape drive fixes prior to last night. Other questions... How long does it take for your tape to rewind. Do you have disconnection enabeled for the tape drive and all other targets? Can you also enable the "AHC_DEBUG" defing in aic7xxx.c and see if you can reproduce it. I might get some diagnostic output that will help me understand what went wrong. > >Thought you'd like to know. Let me know if there is anything I can >do to help track it down. > >Note the tape did in fact successfully rewind and the drive allowed me >to remove it (whilst the system was hung). > >-- >Bob Willcox >bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) >Austin, TX -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Fri Apr 28 15:23:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA27335 for current-outgoing; Fri, 28 Apr 1995 15:23:33 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA27313 for ; Fri, 28 Apr 1995 15:23:28 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA17794; Sat, 29 Apr 1995 00:23:10 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA26214 for freebsd-current@FreeBSD.org; Sat, 29 Apr 1995 00:23:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA01851 for freebsd-current@FreeBSD.org; Sat, 29 Apr 1995 00:09:22 +0200 From: J Wunsch Message-Id: <199504282209.AAA01851@uriah.heep.sax.de> Subject: Re: Where to put data base file To: freebsd-current@FreeBSD.org Date: Sat, 29 Apr 1995 00:09:21 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <199504281753.NAA09952@hda.com> from "Peter Dufault" at Apr 28, 95 01:53:37 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 502 Sender: current-owner@FreeBSD.org Precedence: bulk As Peter Dufault wrote: > > Where do I put this ASCII data base file? It can be used by > /sbin/scsi to permit you to get and set SCSI mode pages, so for > that reason it could go in "/etc/scsi_modes". What about putting it into a script (/sbin/scsicontrol?), maybe this one could even replace your suggested scsiformat(8) script in a more universal way? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Apr 28 16:04:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA28326 for current-outgoing; Fri, 28 Apr 1995 16:04:46 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA28320 for ; Fri, 28 Apr 1995 16:04:42 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id SAA11278; Fri, 28 Apr 1995 18:54:23 -0400 From: Peter Dufault Message-Id: <199504282254.SAA11278@hda.com> Subject: Re: aic7xxx Adapter support To: gibbs@estienne.CS.Berkeley.EDU (Justin T. Gibbs) Date: Fri, 28 Apr 1995 18:54:23 -0400 (EDT) Cc: bob@obiwan.pmr.com, current@FreeBSD.org In-Reply-To: <199504281954.MAA00298@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Apr 28, 95 12:54:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 946 Sender: current-owner@FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > > > When was the last time you updated your kernel before last night? I'm > just wondering if you had run a kernel with Peter's tape drive fixes > prior to last night. What, me worry? Before anyone asks me about this I'll point out it is Julian's work, and though I'll be happy to help as much as I can I really don't know much about different types of tapes. Much to my pleasure my Exabyte has always worked without a hitch. > Other questions... How long does it take for your tape to rewind. Do > you have disconnection enabeled for the tape drive and all other > targets? This is what I was wondering. We don't have the IMMEDIATE bit set in the rewind command, and so I guess you will tie up the bus if you don't allow it to disconnect. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 16:12:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA28431 for current-outgoing; Fri, 28 Apr 1995 16:12:38 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA28424 for ; Fri, 28 Apr 1995 16:12:36 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: current@freefall.cdrom.com Subject: if_fddisubr.c Date: Fri, 28 Apr 1995 16:12:34 -0700 Message-ID: <28423.799110754@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk from LINT (with -Wall) ../../net/if_fddisubr.c: In function `fddi_input': ../../net/if_fddisubr.c:486: `ac' undeclared (first use this function) ../../net/if_fddisubr.c:486: (Each undeclared identifier is reported only once ../../net/if_fddisubr.c:486: for each function it appears in.) ../../net/if_fddisubr.c:487: `eh' undeclared (first use this function) Someone cure please... Gary From owner-freebsd-current Fri Apr 28 16:18:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA28565 for current-outgoing; Fri, 28 Apr 1995 16:18:03 -0700 Received: from obiwan.pmr.com (obiwan.pmr.com [199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA28559 for ; Fri, 28 Apr 1995 16:17:55 -0700 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0s4zHO-000308C; Fri, 28 Apr 95 18:16 CDT Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: aic7xxx Adapter support To: dufault@hda.com (Peter Dufault) Date: Fri, 28 Apr 1995 18:16:56 -0500 (CDT) Cc: gibbs@estienne.CS.Berkeley.EDU, current@FreeBSD.org In-Reply-To: <199504282254.SAA11278@hda.com> from "Peter Dufault" at Apr 28, 95 06:54:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1382 Sender: current-owner@FreeBSD.org Precedence: bulk Peter Dufault wrote: > > Justin T. Gibbs writes: > > > > > > When was the last time you updated your kernel before last night? I'm > > just wondering if you had run a kernel with Peter's tape drive fixes > > prior to last night. > > What, me worry? Looking back through my old mail, it appears that I may not have tried the tape drive between 4/10 and now (I generally update my sources and rebuild daily on this particular system, so it stays within a day of -current). > > Before anyone asks me about this I'll point out it is Julian's > work, and though I'll be happy to help as much as I can I really > don't know much about different types of tapes. Much to my pleasure > my Exabyte has always worked without a hitch. Which Exabyte drive do you have? Mine are the older 8200 (with latest firmware). They work reasonably well with my BT-747S adapters. I am having some problems with the one on the AHA-2740A, though. > > > Other questions... How long does it take for your tape to rewind. Do > > you have disconnection enabeled for the tape drive and all other > > targets? > > This is what I was wondering. We don't have the IMMEDIATE bit set > in the rewind command, and so I guess you will tie up the bus if > you don't allow it to disconnect. Yes. It is allowed to disconnect. -- Bob Willcox bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-current Fri Apr 28 16:46:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA28989 for current-outgoing; Fri, 28 Apr 1995 16:46:07 -0700 Received: from obiwan.pmr.com (obiwan.pmr.com [199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA28983 for ; Fri, 28 Apr 1995 16:46:02 -0700 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0s4zjN-00030hC; Fri, 28 Apr 95 18:45 CDT Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: scsi -f /dev/rst2 -d 1 fails To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Fri, 28 Apr 1995 18:45:53 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 330 Sender: current-owner@FreeBSD.org Precedence: bulk I have rebuilt my kernel with ``options SCSIDEBUG'' set and am now trying to turn on debug for the tape drive thats failing, but when I try I get: scsi -f /dev/rst2 -d 1 ioctl [SCIODEBUG]: Inappropriate ioctl for device Any ideas what I'm doing wrong? -- Bob Willcox bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-current Fri Apr 28 17:04:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA29524 for current-outgoing; Fri, 28 Apr 1995 17:04:13 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA29515 for ; Fri, 28 Apr 1995 17:04:06 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id UAA11561; Fri, 28 Apr 1995 20:02:47 -0400 From: Peter Dufault Message-Id: <199504290002.UAA11561@hda.com> Subject: Re: Where to put data base file To: freebsd-current@FreeBSD.org Date: Fri, 28 Apr 1995 20:02:46 -0400 (EDT) In-Reply-To: <199504282209.AAA01851@uriah.heep.sax.de> from "J Wunsch" at Apr 29, 95 00:09:21 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 789 Sender: current-owner@FreeBSD.org Precedence: bulk J Wunsch writes: > > As Peter Dufault wrote: > > > > Where do I put this ASCII data base file? It can be used by > > /sbin/scsi to permit you to get and set SCSI mode pages, so for > > that reason it could go in "/etc/scsi_modes". > > What about putting it into a script (/sbin/scsicontrol?), maybe this > one could even replace your suggested scsiformat(8) script in a more > universal way? What exactly do you mean? I don't follow your suggestion; take a look at the newly committed "/usr/share/misc/scsi_modes" and then send me your suggestion. You might have a really good one there that I've missed. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 18:45:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01947 for current-outgoing; Fri, 28 Apr 1995 18:45:28 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA01938 for ; Fri, 28 Apr 1995 18:45:07 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id VAA11807; Fri, 28 Apr 1995 21:43:39 -0400 From: Peter Dufault Message-Id: <199504290143.VAA11807@hda.com> Subject: Re: scsi -f /dev/rst2 -d 1 fails To: bob@obiwan.pmr.com (Bob Willcox) Date: Fri, 28 Apr 1995 21:43:38 -0400 (EDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: from "Bob Willcox" at Apr 28, 95 06:45:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 546 Sender: current-owner@FreeBSD.org Precedence: bulk Bob Willcox writes: > > I have rebuilt my kernel with ``options SCSIDEBUG'' set and am now trying > to turn on debug for the tape drive thats failing, but when I try I get: > > scsi -f /dev/rst2 -d 1 > ioctl [SCIODEBUG]: Inappropriate ioctl for device > > Any ideas what I'm doing wrong? The ioctl will only work against the control device. I guess it is /dev/st2ctl.0. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 18:50:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02168 for current-outgoing; Fri, 28 Apr 1995 18:50:41 -0700 Received: from obiwan.pmr.com (obiwan.pmr.com [199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA02162 for ; Fri, 28 Apr 1995 18:50:37 -0700 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0s51g0-00030sC; Fri, 28 Apr 95 20:50 CDT Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: scsi -f /dev/rst2 -d 1 fails To: dufault@hda.com (Peter Dufault) Date: Fri, 28 Apr 1995 20:50:32 -0500 (CDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199504290143.VAA11807@hda.com> from "Peter Dufault" at Apr 28, 95 09:43:38 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 555 Sender: current-owner@FreeBSD.org Precedence: bulk Peter Dufault wrote: > > Bob Willcox writes: > > > > I have rebuilt my kernel with ``options SCSIDEBUG'' set and am now trying > > to turn on debug for the tape drive thats failing, but when I try I get: > > > > scsi -f /dev/rst2 -d 1 > > ioctl [SCIODEBUG]: Inappropriate ioctl for device > > > > Any ideas what I'm doing wrong? > > The ioctl will only work against the control device. I guess it > is /dev/st2ctl.0. Right!!! I remember that now...sorry for the bother. -- Bob Willcox bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-current Fri Apr 28 18:50:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02182 for current-outgoing; Fri, 28 Apr 1995 18:50:53 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA02173 for ; Fri, 28 Apr 1995 18:50:46 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id VAA11818; Fri, 28 Apr 1995 21:49:10 -0400 From: Peter Dufault Message-Id: <199504290149.VAA11818@hda.com> Subject: Re: wcarchive.cdrom.com (also known as ftp.freebsd.org) back up. To: jkh@violet.berkeley.edu (Jordan K. Hubbard) Date: Fri, 28 Apr 1995 21:49:09 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: <199504281657.JAA14637@violet.berkeley.edu> from "Jordan K. Hubbard" at Apr 28, 95 09:57:17 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 911 Sender: current-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > We subsequently had some rather significant hardware hurdles to jump over, > not the least of which was 3 brand-new Quantum Grand Prix 4.3GB hard drives > going south unexpectedly. Given that this is 4 GPs I've lost in 4 weeks > (2 of which died in completely different environmental circumstances, so > it's not just our machine room), I think it's safe to say that Quantum may > be having some quality control problems with these drives! :-( I've > switched back to the Seagate Barracuda drives and all seems happy again. > The Seagates are even about $100 cheaper, so my traditional prejudice against > Seagate may be weakening here. Could someone provide details on the drive failures? Thanks. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Fri Apr 28 21:15:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA06888 for current-outgoing; Fri, 28 Apr 1995 21:15:48 -0700 Received: from emerald.oz.net (emerald.oz.net [198.68.184.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA06881 for ; Fri, 28 Apr 1995 21:15:44 -0700 Received: from wsantee.oz.net by emerald.oz.net via SMTP (931110.SGI/930416.SGI) for freebsd-current@freebsd.org id AA11372; Fri, 28 Apr 95 21:13:49 -0700 Received: (from wsantee@localhost) by wsantee.oz.net (8.6.11/8.6.9) id VAA00200 for freebsd-current@freebsd.org; Fri, 28 Apr 1995 21:14:15 -0700 From: Wes Santee Message-Id: <199504290414.VAA00200@wsantee.oz.net> Subject: How to write -current bootcode to disk? To: freebsd-current@FreeBSD.org Date: Fri, 28 Apr 1995 21:14:13 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 613 Sender: current-owner@FreeBSD.org Precedence: bulk Hey all. I'm currently running the April snapshot (both kernel and binaries). I just supped and compiled the -current kernel and all hell broke loose when trying to mount my disks. I understand that some changes have been made in the abilities to mount disks under -current (including ability to mount extended DOS partitions...can someone confirm?) At any rate, what -current binaries am I going to need to update the boot code to mount my disks correctly again, and what is the easiest way to write the new partition information without wiping out my current partitions? Cheers, -Wes wsantee@wsantee.oz.net From owner-freebsd-current Sat Apr 29 01:47:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15587 for current-outgoing; Sat, 29 Apr 1995 01:47:34 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA15575 for ; Sat, 29 Apr 1995 01:47:06 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA17007; Sat, 29 Apr 1995 18:45:29 +1000 Date: Sat, 29 Apr 1995 18:45:29 +1000 From: Bruce Evans Message-Id: <199504290845.SAA17007@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, wsantee@wsantee.oz.net Subject: Re: How to write -current bootcode to disk? Sender: current-owner@FreeBSD.org Precedence: bulk >I'm currently running the April snapshot (both kernel and binaries). >I just supped and compiled the -current kernel and all hell broke >loose when trying to mount my disks. >I understand that some changes have been made in the abilities to >mount disks under -current (including ability to mount extended DOS >partitions...can someone confirm?) Yes, the changes are in -current but not in the snapshot. >At any rate, what -current binaries am I going to need to update the >boot code to mount my disks correctly again, and what is the easiest None. It would help to have some utilities to summarize the slice/ partition layout, but they aren't written yet. >way to write the new partition information without wiping out my >current partitions? Not writing anything is safest. Ignore the boot-time warnings. You may have to edit /etc/fstab to change the names of non-BSD partitions. Bruce From owner-freebsd-current Sat Apr 29 02:09:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA16149 for current-outgoing; Sat, 29 Apr 1995 02:09:57 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA16143 for ; Sat, 29 Apr 1995 02:09:54 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA00163; Sat, 29 Apr 1995 11:09:37 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA29101; Sat, 29 Apr 1995 11:09:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA03864; Sat, 29 Apr 1995 09:34:30 +0200 From: J Wunsch Message-Id: <199504290734.JAA03864@uriah.heep.sax.de> Subject: Re: How to write -current bootcode to disk? To: wsantee@wsantee.oz.net (Wes Santee) Date: Sat, 29 Apr 1995 09:34:30 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <199504290414.VAA00200@wsantee.oz.net> from "Wes Santee" at Apr 28, 95 09:14:13 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 565 Sender: current-owner@FreeBSD.org Precedence: bulk As Wes Santee wrote: > > I'm currently running the April snapshot (both kernel and binaries). > I just supped and compiled the -current kernel and all hell broke > loose when trying to mount my disks. I'm not sure if the boot code is your only problem, but you can rewrite it with disklabel -B [-b /usr/mdec/sdboot] [-s /usr/mdec/bootsd] sd0 (The bracketed terms show the defaults.) For a wd-style disk: s/sd/wd/g -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Apr 29 12:33:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06956 for current-outgoing; Sat, 29 Apr 1995 12:33:05 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA06949 for ; Sat, 29 Apr 1995 12:32:51 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA16025; Sat, 29 Apr 1995 21:32:05 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA02686 for freebsd-current@FreeBSD.org; Sat, 29 Apr 1995 21:32:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id VAA00267 for freebsd-current@FreeBSD.org; Sat, 29 Apr 1995 21:26:46 +0200 From: J Wunsch Message-Id: <199504291926.VAA00267@uriah.heep.sax.de> Subject: object deallocated too many times To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 29 Apr 1995 21:26:45 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 486 Sender: current-owner@FreeBSD.org Precedence: bulk Something to care for? Newly-built kernel, last entry in commitlogs/sys from 95/04/28 12:26:02 (freefall time), panicked with "object deallocated too many times" during savecore on first boot. I wasn't eager to take a core dump, and the second attempt it booted fine. The system has it's /usr mounted via NFS, in case this would matter. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Apr 29 15:30:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA20810 for current-outgoing; Sat, 29 Apr 1995 15:30:04 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA20716 ; Sat, 29 Apr 1995 15:29:22 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id AAA00890; Sun, 30 Apr 1995 00:29:04 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id AAA10579; Sun, 30 Apr 1995 00:29:03 +0200 Message-Id: <199504292229.AAA10579@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: bugs@FreeBSD.org, current@FreeBSD.org Subject: pkg_manage has a problem? Date: Sun, 30 Apr 1995 00:29:03 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk Hi I suspect this is work-in-progress, so I am not filing it as a bug report, rather mentioning it in case it has slipped by?? pkg_manage looks like a SUPERB tool, just what I always wanted, thank you, only; when it starts, it seems to want to find all the info on my installed packages in tarballs in the /var/db/pkg/.. area. This fails 'cos I build all my packages myself, and bypass the tarball phase. OTOH, is this a blatant bug? should it not be looking directly at the 3 + files in the package directories? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-current Sat Apr 29 15:46:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA21971 for current-outgoing; Sat, 29 Apr 1995 15:46:17 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA21959 for ; Sat, 29 Apr 1995 15:46:11 -0700 Received: by pelican.com (Smail3.1.28.1 #5) id m0s5LH1-000K0jC; Sat, 29 Apr 95 15:46 WET DST Message-Id: From: pete@pelican.com (Pete Carah) Subject: fdisk+disklabel, etc To: current@FreeBSD.org Date: Sat, 29 Apr 1995 15:46:02 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1655 Sender: current-owner@FreeBSD.org Precedence: bulk I'm having a bear of a time getting a disk labelled - whatever I do, disklabel won't label the disk. This is a quantum 540 scsi with 1057758 sectors. This doesn't factor into anything which will fit into dos (or bios)'s idea of cyl-hd-record. To use these scsi drives, there has to be a way of getting fdisk and disklabel to buy the drive size without paying any attention *at all* to the slice table's cyl-hd-rec data. I saw some description fly by but it won't work for this drive no matter what I try (even go down to the next "cyl" value using xxx-64-32 or xxx-32-32 or xxx-16-63) I don't want to lose a meg at the end if possible, and it doesn't work even with that loss. We need a decent way to 1. Get the slice manager to buy ONLY beginning/size and totally ignore the bios data. 2. Fake out the size so it can be bigger than cyl*hd*sec as long as the real drive size isn't exceeded. The latter is supposed to work if #cyl is 1023 but this drive doesn't conveniently partition so that works. I also have to allocate a 1-cyl dos partition for all time to get the slice table accepted at boot time, no matter what - if I delete it and write the bsd slice as the whole disk then things fail when I try to disklabel. (actually, now, the fail when I try to disklabel anyhow, independent of the fbsd size. This is with disklabel aimed at: sd1 /dev/rsd1 /dev/rsd1c /dev/rsd1s4 /dev/rsd1s4c.) Mostly it complains that the a partition extends past the end of unit, even though the beg is 0 and size matches that in the slice table. The last complained about no such file. We need a GOOD writeup on this; I know it can be done. -- Pete From owner-freebsd-current Sat Apr 29 18:05:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA04494 for current-outgoing; Sat, 29 Apr 1995 18:05:15 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA04488 for ; Sat, 29 Apr 1995 18:05:13 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14793(6)>; Sat, 29 Apr 1995 18:04:25 PDT Received: by crevenia.parc.xerox.com id <49859>; Sat, 29 Apr 1995 18:04:19 -0700 From: Bill Fenner To: current@FreeBSD.org Subject: NCR assertion fails? Message-Id: <95Apr29.180419pdt.49859@crevenia.parc.xerox.com> Date: Sat, 29 Apr 1995 18:04:13 PDT Sender: current-owner@FreeBSD.org Precedence: bulk I just got a new Conner 1080S for my birthday. I installed it as sd1 and installed 950412-SNAP on it. I have a generic NCR810 card and a digital ethernet card which so far have been sharing the PCI bus okay. However, while the machine is coming up, I get the following messages: assertion "cp == np->header.cp" failed: file "../../pci/ncr.c", line 5235 assertion "cp" failed: file "../../pci/ncr.c", line 5236 ncr0 targ 1?: ERROR (80:100) (e-29-0) (8/13) @ (10d4:e000000). reg: da 10 0 13 47 8 1 1f 3 e 81 29 80 1 9 0. ncr0: restart (fatal error). sd1(ncr0:1:0): COMMAND FAILED (9 ff) @f055d000. vnode_pager_input: I/O read error vm_fault: pager input (probably hardware) error, PID 26 failure ncr0: reset by timeout. sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd1(ncr0:1:0): UNIT ATTENTION asc:29,0sd1(ncr0:1:0): Power on, reset, or bus device reset occurred , retries:3 The probe looks more or less normal: ncr0 rev 1 int a irq 9 on pci0:14 reg20: virtual=0xf2aa2800 physical=0xffbff800 size=0x100 using shared irq 9. ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) (ncr0:0:0): "IMPRIMIS 94241-7 1275" is a type 0 fixed SCSI 1 sd0(ncr0:0:0): Direct-Access 317MB (649502 512 byte sectors) (ncr0:1:0): "CONNER CFP1080S 3939" is a type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1030MB (2110812 512 byte sectors) (ncr0:2:0): "NEC CD-ROM DRIVE:500 2.5" is a type 5 removable SCSI 2 cd0(ncr0:2:0): CD-ROM cd0(ncr0:2:0): NOT READY asc:4,0 cd0(ncr0:2:0): Logical unit not ready, cause not reportable cd0: could not get size drive empty (ncr0:4:0): "TANDBERG TDC 360092X4180 I04:" is a type 1 removable SCSI 1 st0(ncr0:4:0): Sequential-Access st0: Tandberg tdc3600 is a known rogue density code 0xf, 512-byte blocks, write-enabled pci0: uses 384 bytes of memory from ffbff800 upto ffbffc7f. pci0: uses 384 bytes of I/O space from f800 upto fcff. But disk access is horrendously slow. fenestro: {35} time pwd /home/fenner 0.0u 0.0s 0:02.21 0.0% 0+0k 3+0io 0pf+0w fenestro: {36} dd if=/kernel of=snot 1943+1 records in 1943+1 records out 995064 bytes transferred in 20 secs (49753 bytes/sec) 50K/sec, I could do NFS over my ISDN line and be faster =) Anyone have any suggestions? Thanks, Bill From owner-freebsd-current Sat Apr 29 19:45:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA06284 for current-outgoing; Sat, 29 Apr 1995 19:45:12 -0700 Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA06276 for ; Sat, 29 Apr 1995 19:45:08 -0700 Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA06974; Sat, 29 Apr 1995 21:42:25 -0500 Message-Id: <9504300242.AA06974@iworks.InterWorks.org> Date: Sat, 29 Apr 1995 21:42:25 -0500 From: "Daniel M. Eischen" To: freebsd-current@FreeBSD.org Subject: Swap partition not mounting Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I just sup'd the src/sys tree and am having problems getting my swap partition recognized and enabled. Before tonight, I was running with an April 17th or thereabouts kernel. I've run with the Feb 25 snap, the April 10th snap, and the April 17th current src/sys without any problems. Do I need anything more than src/sys to get this to work? Below are the contents of /etc/fstab, a successful dmesg, and an unsuccessful dmesg. BTW, all attempts to enable swaping after boot fail. /etc/fstab: /dev/sd0a / ufs rw 1 1 /dev/sd0g /usr ufs rw 1 1 /dev/sd0b none swap sw 0 0 proc /proc procfs rw 0 0 -------------- Succesful boot: Apr 29 20:52:40 Rigel /kernel: ahc0 rev 0 int a irq 10 on pci0:6 Apr 29 20:52:40 Rigel /kernel: ahc0: reading board settings Apr 29 20:52:40 Rigel /kernel: ahc0: 294x Wide Channel, SCSI Id=7, aic7870, 16 SCBs Apr 29 20:52:41 Rigel /kernel: ahc0: Downloading Sequencer Program...Done Apr 29 20:52:41 Rigel /kernel: ahc0: Probing channel A Apr 29 20:52:41 Rigel /kernel: ahc0 waiting for scsi devices to settle Apr 29 20:52:41 Rigel /kernel: ahc0: target 0 using 16Bit transfers Apr 29 20:52:41 Rigel /kernel: (ahc0:0:0): "FUJITSU M2694EQ-512 4105" type 0 fixed SCSI 2 Apr 29 20:52:41 Rigel /kernel: sd0(ahc0:0:0): Direct-Access 1033MB (2117025 512 byte sectors) Apr 29 20:52:41 Rigel /kernel: ahc0: target 1 synchronous at 10.0MB/s, offset = 0xf Apr 29 20:52:42 Rigel /kernel: (ahc0:1:0): "SEAGATE ST5660N 0592" type 0 fixed SCSI 2 Apr 29 20:52:42 Rigel /kernel: sd1(ahc0:1:0): Direct-Access 520MB (1065664 512 byte sectors) Apr 29 20:52:42 Rigel /kernel: ahc0: target 2 synchronous at 4.0MB/s, offset = 0xf Apr 29 20:52:42 Rigel /kernel: (ahc0:2:0): "PLEXTOR CD-ROM PX-4XCH 1.22" type 5 removable SCSI 2 Apr 29 20:52:42 Rigel /kernel: cd0(ahc0:2:0): CD-ROM cd present.[325427 x 2048 byte records] Apr 29 20:52:43 Rigel /kernel: ahc0: target 3 synchronous at 10.0MB/s, offset = 0x8 Apr 29 20:52:43 Rigel /kernel: (ahc0:3:0): "HP C1533A 9406" type 1 removable SCSI 2 Apr 29 20:52:43 Rigel /kernel: st0(ahc0:3:0): Sequential-Access density code 0x24, drive empty Apr 29 20:52:43 Rigel /kernel: vga0 rev 1 on pci0:12 Apr 29 20:52:43 Rigel /kernel: pci0: uses 8392704 bytes of memory from a0000000 upto ffbfffff. Apr 29 20:52:43 Rigel /kernel: pci0: uses 256 bytes of I/O space from fc00 upto fcff. Apr 29 20:52:43 Rigel /kernel: changing root device to sd0a Apr 29 20:52:44 Rigel /kernel: sd0s1: start 63, end = 931769, size 931707: OK Apr 29 20:52:44 Rigel /kernel: sd0s2: start 931770, end = 1044224, size 112455: OK Apr 29 20:52:44 Rigel /kernel: sd0s4: start 1285200, end = 2117024, size 831825: OK Apr 29 20:52:44 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:44 Rigel /kernel: sd0: start 1285200, end 2117024, size 831825 Apr 29 20:52:44 Rigel /kernel: sd0d: start 0, end 2117024, size 2117025 Apr 29 20:52:44 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:44 Rigel /kernel: sd0e: start 63, end 931769, size 931707 Apr 29 20:52:44 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:44 Rigel /kernel: sd0f: start 931770, end 1044224, size 112455 Apr 29 20:52:44 Rigel /kernel: sd1s1: start 32, end = 718847, size 718816: OK Apr 29 20:52:44 Rigel /kernel: sd1s2: start 718848, end = 823295, size 104448: OK Apr 29 20:52:44 Rigel /kernel: sd1s3: start 823296, end = 1064959, size 241664: OK Apr 29 20:52:45 Rigel /kernel: sd0s1: start 63, end = 931769, size 931707: OK Apr 29 20:52:45 Rigel /kernel: sd0s2: start 931770, end = 1044224, size 112455: OK Apr 29 20:52:45 Rigel /kernel: sd0s4: start 1285200, end = 2117024, size 831825: OK Apr 29 20:52:45 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:45 Rigel /kernel: sd0: start 1285200, end 2117024, size 831825 Apr 29 20:52:45 Rigel /kernel: sd0d: start 0, end 2117024, size 2117025 Apr 29 20:52:45 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:45 Rigel /kernel: sd0e: start 63, end 931769, size 931707 Apr 29 20:52:45 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:45 Rigel /kernel: sd0f: start 931770, end 1044224, size 112455 Apr 29 20:52:45 Rigel /kernel: sd0s1: start 63, end = 931769, size 931707: OK Apr 29 20:52:45 Rigel /kernel: sd0s2: start 931770, end = 1044224, size 112455: OK Apr 29 20:52:45 Rigel /kernel: sd0s4: start 1285200, end = 2117024, size 831825: OK Apr 29 20:52:46 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:46 Rigel /kernel: sd0: start 1285200, end 2117024, size 831825 Apr 29 20:52:46 Rigel /kernel: sd0d: start 0, end 2117024, size 2117025 Apr 29 20:52:46 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:46 Rigel /kernel: sd0e: start 63, end 931769, size 931707 Apr 29 20:52:46 Rigel /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:52:46 Rigel /kernel: sd0f: start 931770, end 1044224, size 112455 Apr 29 20:52:34 Rigel lpd[67]: restarted ------------- Unsuccessful boot: Apr 29 20:48:13 Rigel kernel.test: ahc0 rev 0 int a irq 10 on pci0:6 Apr 29 20:48:13 Rigel kernel.test: ahc0: reading board settings Apr 29 20:48:13 Rigel kernel.test: ahc0: 294x Wide Channel, SCSI Id=7, aic7870, 16 SCBs Apr 29 20:48:13 Rigel kernel.test: ahc0: Using Edge Triggered Interrupts Apr 29 20:48:13 Rigel kernel.test: ahc0: Downloading Sequencer Program...Done Apr 29 20:48:13 Rigel kernel.test: ahc0: Probing channel A Apr 29 20:48:14 Rigel kernel.test: ahc0 waiting for scsi devices to settle Apr 29 20:48:14 Rigel kernel.test: ahc0: target 0 using 16Bit transfers Apr 29 20:48:14 Rigel kernel.test: (ahc0:0:0): "FUJITSU M2694EQ-512 4105" type 0 fixed SCSI 2 Apr 29 20:48:14 Rigel kernel.test: sd0(ahc0:0:0): Direct-Access 1033MB (2117025 512 byte sectors) Apr 29 20:48:14 Rigel kernel.test: ahc0: target 1 synchronous at 10.0MB/s, offset = 0xf Apr 29 20:48:14 Rigel kernel.test: (ahc0:1:0): "SEAGATE ST5660N 0592" type 0 fixed SCSI 2 Apr 29 20:48:14 Rigel kernel.test: sd1(ahc0:1:0): Direct-Access 520MB (1065664 512 byte sectors) Apr 29 20:48:14 Rigel kernel.test: ahc0: target 2 synchronous at 4.0MB/s, offset = 0xf Apr 29 20:48:14 Rigel kernel.test: (ahc0:2:0): "PLEXTOR CD-ROM PX-4XCH 1.22" type 5 removable SCSI 2 Apr 29 20:48:14 Rigel kernel.test: cd0(ahc0:2:0): CD-ROM cd present.[325427 x 2048 byte records] Apr 29 20:48:14 Rigel kernel.test: ahc0: target 3 synchronous at 10.0MB/s, offset = 0x8 Apr 29 20:48:14 Rigel kernel.test: (ahc0:3:0): "HP C1533A 9406" type 1 removable SCSI 2 Apr 29 20:48:14 Rigel kernel.test: st0(ahc0:3:0): Sequential-Access density code 0x24, drive empty Apr 29 20:48:15 Rigel kernel.test: vga0 rev 1 on pci0:12 Apr 29 20:48:15 Rigel kernel.test: pci0: uses 8392704 bytes of memory from a0000000 upto ffbfffff. Apr 29 20:48:15 Rigel kernel.test: pci0: uses 256 bytes of I/O space from fc00 upto fcff. Apr 29 20:48:15 Rigel kernel.test: changing root device to sd0a Apr 29 20:48:15 Rigel kernel.test: sd1s1: type 0x83, start 32, end = 718847, size 718816 : OK Apr 29 20:48:15 Rigel kernel.test: sd1s2: type 0x82, start 718848, end = 823295, size 104448 : OK Apr 29 20:48:15 Rigel kernel.test: sd1s3: type 0x6, start 823296, end = 1064959, size 241664 : OK Apr 29 20:48:15 Rigel kernel.test: sd0s1: type 0x83, start 63, end = 931769, size 931707 : OK Apr 29 20:48:15 Rigel kernel.test: sd0s2: type 0x82, start 931770, end = 1044224, size 112455 : OK Apr 29 20:48:15 Rigel kernel.test: sd0s4: type 0xa5, start 1285200, end = 2117024, size 831825 : OK Apr 29 20:48:15 Rigel kernel.test: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:48:15 Rigel kernel.test: sd0: start 1285200, end 2117024, size 831825 Apr 29 20:48:15 Rigel kernel.test: sd0d: start 0, end 2117024, size 2117025 Apr 29 20:48:16 Rigel kernel.test: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:48:16 Rigel kernel.test: sd0e: start 63, end 931769, size 931707 Apr 29 20:48:16 Rigel kernel.test: sd0: rejecting partition in BSD label: it isn't entirely within the slice Apr 29 20:48:16 Rigel kernel.test: sd0f: start 931770, end 1044224, size 112455 Apr 29 20:48:16 Rigel kernel.test: WARNING: no swap space found Thanks in advance, Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-current Sat Apr 29 21:07:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA07881 for current-outgoing; Sat, 29 Apr 1995 21:07:38 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA07871 for ; Sat, 29 Apr 1995 21:07:34 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id VAA00687; Sat, 29 Apr 1995 21:07:23 -0700 Message-Id: <199504300407.VAA00687@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: "Daniel M. Eischen" cc: freebsd-current@FreeBSD.org Subject: Re: Swap partition not mounting In-reply-to: Your message of "Sat, 29 Apr 1995 21:42:25 CDT." <9504300242.AA06974@iworks.InterWorks.org> Date: Sat, 29 Apr 1995 21:07:22 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk > >Hi, > > I just sup'd the src/sys tree and am having problems getting my swap partiti >on >recognized and enabled. Before tonight, I was running with an April 17th or >thereabouts kernel. I've run with the Feb 25 snap, the April 10th snap, and t >he >April 17th current src/sys without any problems. Do I need anything more than >src/sys to get this to work? > >Below are the contents of /etc/fstab, a successful dmesg, and an unsuccessful >dmesg. BTW, all attempts to enable swaping after boot fail. I had the same problem. I changed my config line to remove wd devices and it worked again: config kernel root on sd0 swap on sd0 and sd1 and vn0 dumps on sd0 I haven't looked into why this solved the problem. > >Dan Eischen >deischen@iworks.InterWorks.org -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Sat Apr 29 21:54:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA08815 for current-outgoing; Sat, 29 Apr 1995 21:54:29 -0700 Received: from macs.mxim.com (macs.mxim.com [204.17.143.130]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA08809 for ; Sat, 29 Apr 1995 21:54:26 -0700 Received: (from michaele@localhost) by macs.mxim.com (8.6.11/8.6.9) id VAA20266; Sat, 29 Apr 1995 21:56:03 -0700 Date: Sat, 29 Apr 1995 21:56:03 -0700 (PDT) From: Michael Enkelis To: current@FreeBSD.org Subject: make world fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I try to keep up-to-date by SUPing every few days. At last I decided to build from scratch, so I went to ".../src" and did a make world. When it got to "src/lib/libc/net" the build failed. I removed the .include net from the makefile, and continued on. My last SUP was done 4/28/95 at 09:52 (date shown on sup/lib/last) _ _ _ __ michaele@mxim.com ' ) ) ) / /) / ` / /) Michael Enkelis / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 / ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_ From owner-freebsd-current Sat Apr 29 22:19:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09235 for current-outgoing; Sat, 29 Apr 1995 22:19:09 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA09229 ; Sat, 29 Apr 1995 22:19:05 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id WAA23231; Sat, 29 Apr 1995 22:19:02 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id WAA03214; Sat, 29 Apr 1995 22:19:01 -0700 Message-Id: <199504300519.WAA03214@corbin.Root.COM> To: Gary Palmer (FreeBSD/ARM Team) cc: current@freefall.cdrom.com Subject: Re: if_fddisubr.c In-reply-to: Your message of "Fri, 28 Apr 95 16:12:34 PDT." <28423.799110754@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 29 Apr 1995 22:19:01 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk > >from LINT (with -Wall) > >../../net/if_fddisubr.c: In function `fddi_input': >../../net/if_fddisubr.c:486: `ac' undeclared (first use this function) >../../net/if_fddisubr.c:486: (Each undeclared identifier is reported only once >../../net/if_fddisubr.c:486: for each function it appears in.) >../../net/if_fddisubr.c:487: `eh' undeclared (first use this function) > >Someone cure please... This is the third report I've gotten about this. It is of course fixable, but the 'right' fix is probably to remove the netiso code. Noone in our group has the ability to test it, and as far as I know it is broken and useless. The errors are ocurring because LINT defines options "ISO" and the if_fddisubr.c's ISO code is out of date. -DG From owner-freebsd-current Sat Apr 29 23:18:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10432 for current-outgoing; Sat, 29 Apr 1995 23:18:51 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10426 for ; Sat, 29 Apr 1995 23:18:50 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id XAA27971 for current@freebsd.org; Sat, 29 Apr 1995 23:18:49 -0700 From: Poul-Henning Kamp Message-Id: <199504300618.XAA27971@ref.tfs.com> Subject: slices and all that To: current@FreeBSD.org Date: Sat, 29 Apr 1995 23:18:49 -0700 (PDT) Content-Type: text Content-Length: 499 Sender: current-owner@FreeBSD.org Precedence: bulk For those of you who need urgently to manipulate slices and partitions, in /src/release/libdisk you can make a program called 'tst01' which is evolving as we speak. The interface is horrible, and it may wipe out your disk entirely, but it may also work. Send bug-reports to me, use at your own (high) risk, no docs. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Sat Apr 29 23:37:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10761 for current-outgoing; Sat, 29 Apr 1995 23:37:29 -0700 Received: from macs.mxim.com (macs.mxim.com [204.17.143.130]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10755 for ; Sat, 29 Apr 1995 23:37:20 -0700 Received: (from michaele@localhost) by macs.mxim.com (8.6.11/8.6.9) id XAA23091; Sat, 29 Apr 1995 23:38:46 -0700 Date: Sat, 29 Apr 1995 23:38:46 -0700 (PDT) From: Michael Enkelis To: current@FreeBSD.org Subject: My last mail about make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Forget what i said about make world failing. I forgot to change my sym-link /sys to point to new source tree. _ _ _ __ michaele@mxim.com ' ) ) ) / /) / ` / /) Michael Enkelis / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 / ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_