From owner-freebsd-current Sun Oct 25 00:39:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15261 for freebsd-current-outgoing; Sun, 25 Oct 1998 00:39:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15255 for ; Sun, 25 Oct 1998 00:39:00 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA12380; Sun, 25 Oct 1998 09:37:41 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810250737.JAA12380@gratis.grondar.za> To: ulf@Alameda.net cc: "Daniel M. Eischen" , tomppa@fidata.fi, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 + CAM + xmcd-2.3 In-Reply-To: Your message of " Sat, 24 Oct 1998 22:06:19 MST." <19981024220619.A12748@Alameda.net> References: <199810250257.VAA06346@iworks.interworks.org> <19981024220619.A12748@Alameda.net> Date: Sun, 25 Oct 1998 09:37:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > I got the package to work, but only after installing Kerberus and DES libs. > Wth does it need libdes.so.3 and libker.so.3 ? Probably because the package was built on a machine with kerberised X. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 01:08:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16748 for freebsd-current-outgoing; Sun, 25 Oct 1998 01:08:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16743 for ; Sun, 25 Oct 1998 01:08:39 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id BAA25748; Sun, 25 Oct 1998 01:07:57 -0700 (PDT) Message-ID: <19981025010757.A21744@Alameda.net> Date: Sun, 25 Oct 1998 01:07:57 -0700 From: Ulf Zimmermann To: Mark Murray Cc: "Daniel M. Eischen" , tomppa@fidata.fi, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 + CAM + xmcd-2.3 Reply-To: ulf@Alameda.net References: <199810250257.VAA06346@iworks.interworks.org> <19981024220619.A12748@Alameda.net> <199810250737.JAA12380@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810250737.JAA12380@gratis.grondar.za>; from Mark Murray on Sun, Oct 25, 1998 at 09:37:41AM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 25, 1998 at 09:37:41AM +0200, Mark Murray wrote: > Ulf Zimmermann wrote: > > I got the package to work, but only after installing Kerberus and DES libs. > > Wth does it need libdes.so.3 and libker.so.3 ? > > Probably because the package was built on a machine with kerberised X. That is probably the reason and there seem to be many packages like that. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 01:23:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21749 for freebsd-current-outgoing; Sun, 25 Oct 1998 01:23:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21744 for ; Sun, 25 Oct 1998 01:23:57 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA01239; Sun, 25 Oct 1998 01:23:11 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA04448; Sun, 25 Oct 1998 01:23:10 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA25064; Sun, 25 Oct 1998 01:23:08 -0800 (PST) From: Don Lewis Message-Id: <199810250923.BAA25064@salsa.gv.tsc.tdk.com> Date: Sun, 25 Oct 1998 01:23:08 -0800 In-Reply-To: Kris Kennaway "Re: nestea v2 against freebsd 3.0-Release (fwd)" (Oct 25, 1:25am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Kris Kennaway , Don Lewis , dfr@nlsystems.com, wollman@khavrinen.lcs.mit.edu Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 25, 1:25am, Kris Kennaway wrote: } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) } On Sat, 24 Oct 1998, Don Lewis wrote: } } > } rootshell.com has a .tgz containing a linux compiled binary - that's the one I } > } ran [1]. Perhaps it was the linuxulator which crashed me, instead of what the } > } program itself did. } > } > Could be. Can you get a stack trace, either with DDB, or with a crash dump } > and gdb? } } (kgdb) where } #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 } #1 0xf012f5e8 in at_shutdown (function=0xf0227772 , } arg=0xf2c7dc34, queue=-267277140) at ../../kern/kern_shutdown.c:430 } #2 0xf011acfd in db_panic (addr=-266858820, have_addr=0, count=-1, } modif=0xf2c7dbbc "") at ../../ddb/db_command.c:432 } #3 0xf011acac in db_command (last_cmdp=0xf0240c34, cmd_table=0xf0240a94, } aux_cmd_tablep=0xf02550b4) at ../../ddb/db_command.c:332 } #4 0xf011ad62 in db_command_loop () at ../../ddb/db_command.c:454 } #5 0xf011d4f3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 } #6 0xf01e545d in kdb_trap (type=12, code=0, regs=0xf2c7dd00) } at ../../i386/i386/db_interface.c:157 } #7 0xf01f13eb in trap_fatal (frame=0xf2c7dd00) at ../../i386/i386/trap.c:874 } #8 0xf01f10e4 in trap_pfault (frame=0xf2c7dd00, usermode=0) } at ../../i386/i386/trap.c:772 } #9 0xf01f0d27 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -263534592, } tf_esi = -263533804, tf_ebp = -221782688, tf_isp = -221782744, } tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, } tf_err = 0, tf_eip = -266858820, tf_cs = 8, tf_eflags = 66118, } tf_esp = -263533804, tf_ss = -266075918}) at ../../i386/i386/trap.c:396 } #10 0xf0180ebc in ip_reass (m=0xf04ac800, fp=0xf04acb14, where=0xf025bfc8) } at ../../netinet/ip_input.c:802 } #11 0xf0180c3f in ip_input (m=0xf04ac800) at ../../netinet/ip_input.c:585 } #12 0xf0181bdb in ipintr () at ../../netinet/ip_input.c:669 } #13 0xf01e72c9 in swi_net_next () } #14 0xf0148c40 in sendit (p=0xf2c69880, s=3, mp=0xf2c7debc, flags=0) } at ../../kern/uipc_syscalls.c:484 } #15 0xf0148e8b in sendmsg (p=0xf2c69880, uap=0xf2c7defc) } at ../../kern/uipc_syscalls.c:632 } #16 0xf0222a5b in linux_sendto_hdrincl (p=0xf2c69880, bsd_args=0xf2c7df1c) } at ../../i386/linux/linux_socket.c:245 } #17 0xf0223435 in linux_socketcall (p=0xf2c69880, args=0xf2c7df84) } at ../../i386/linux/linux_socket.c:624 } #18 0xf01f15f7 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639092, } tf_esi = 0, tf_ebp = 16, tf_isp = -221782060, tf_ebx = 11, tf_edx = 11, } tf_ecx = -272639160, tf_eax = 102, tf_trapno = 12, tf_err = 2, } tf_eip = 671593638, tf_cs = 31, tf_eflags = 534, tf_esp = -272639180, } tf_ss = 39}) at ../../i386/i386/trap.c:1031 } #19 0xf01e5dec in Xint0x80_syscall () } Cannot access memory at address 0x10. } (kgdb) quit Ok, I figured out what's going on. When I compiled the nestea2.c under FreeBSD, it didn't run at all because rip_output() does some sanity checking between ip_len in the packet and the actual packet length, so it doesn't send the third fragment and causes sendto() to return EINVAL. The Linux emulation code in the kernel is kind enough to fix ip_len, so the sanity check passes. Even after I fixed this in nestea2.c, running it still didn't cause the system to panic. The reason for this is some differences in byte swapping in the IP header fields between Linux and FreeBSD that nestea2.c attempted to compensate for, but didn't get right. Once I fixed the byte swapping problem, I got the same panic you did, except for the linux emulation which I was not using. The panic is caused by a bug in the new ip fragment reassembly code that can be provoked into playing with an mbuf after it has been freed. Here's a patch. --- ip_input.c.orig Fri Oct 23 02:17:19 1998 +++ ip_input.c Sun Oct 25 01:50:20 1998 @@ -750,7 +750,7 @@ * if they are completely covered, dequeue them. */ for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; - p = q, q = nq) { + q = nq) { i = (ip->ip_off + ip->ip_len) - GETIP(q)->ip_off; if (i < GETIP(q)->ip_len) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 01:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23510 for freebsd-current-outgoing; Sun, 25 Oct 1998 01:46:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23505 for ; Sun, 25 Oct 1998 01:46:22 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t3o29p34.telia.com [194.236.215.34]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id KAA01929; Sun, 25 Oct 1998 10:45:44 +0100 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id KAA23114; Sun, 25 Oct 1998 10:38:58 +0100 (CET) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199810250938.KAA23114@phoenix.granlund.nu> From: "Johan Granlund" To: Matthew Jacob Date: Sun, 25 Oct 1998 09:37:23 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Exabyte EXB-8200 and CAM, Take3 CC: "Kenneth D. Merry" , freebsd-current@FreeBSD.ORG References: <199810242252.AAA00377@phoenix.granlund.nu> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There's a bit of a contradiction between your first email > and the last one. The first email says that dump exits > right away: I'ts hard to be precise. When dump has finished mapping and (i guess) start to write i get End of tape within a second or two. On a preCAM kernel i get a pause here before i see transfers again on the SCSI bus. I guess i got zero-write from the tar message. > > ...I'medially get "DUMP: End of tape detected" as soon dump tries > to write to the tape. > > The last email implies that that dump succeeded (150 or so writes > succeeded). What did the dump program for the script in the last email > say? It's the same script and the behavior is always the same. > > More importantly, are there any log messages that correlate with the > initial error messages you report? > Nothing, no I/O errors/device busy or anything. It behaves correctly as if i had a zerolength tape in it. /Johan > > > > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 02:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26327 for freebsd-current-outgoing; Sun, 25 Oct 1998 02:33:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26322 for ; Sun, 25 Oct 1998 02:33:26 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id EAA03104; Sun, 25 Oct 1998 04:29:36 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 25 Oct 1998 04:29:36 -0600 (CST) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: Craig Johnston Subject: RE: ELF XFree86 in ports Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Oct-98 Craig Johnston wrote: > > Wanted to hear from anyone who's running ELF XFree86 from the ports > collection on -current. I'm running an aout installation right now -- I'd > like to upgrade but I really don't need to hose X. Rebuilt X the other day to accommodate the (broken?) ports that look for it under /ports. Seems to be fine. -- Conrad Sabatier Eeny, Meeny, Jelly Beanie, the spirits are about to speak! -- Bullwinkle Moose To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 04:16:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10071 for freebsd-current-outgoing; Sun, 25 Oct 1998 04:16:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10064 for ; Sun, 25 Oct 1998 04:16:23 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id MAA15457; Sun, 25 Oct 1998 12:16:05 GMT Date: Sun, 25 Oct 1998 12:16:05 +0000 (GMT) From: Doug Rabson To: Don Lewis cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: <199810250923.BAA25064@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Don Lewis wrote: > Ok, I figured out what's going on. When I compiled the nestea2.c under > FreeBSD, it didn't run at all because rip_output() does some sanity > checking between ip_len in the packet and the actual packet length, so > it doesn't send the third fragment and causes sendto() to return > EINVAL. The Linux emulation code in the kernel is kind enough to fix > ip_len, so the sanity check passes. Even after I fixed this in > nestea2.c, running it still didn't cause the system to panic. The > reason for this is some differences in byte swapping in the IP header > fields between Linux and FreeBSD that nestea2.c attempted to compensate > for, but didn't get right. Once I fixed the byte swapping problem, I > got the same panic you did, except for the linux emulation which I was > not using. > > The panic is caused by a bug in the new ip fragment reassembly code > that can be provoked into playing with an mbuf after it has been freed. > Here's a patch. > > --- ip_input.c.orig Fri Oct 23 02:17:19 1998 > +++ ip_input.c Sun Oct 25 01:50:20 1998 > @@ -750,7 +750,7 @@ > * if they are completely covered, dequeue them. > */ > for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; > - p = q, q = nq) { > + q = nq) { > i = (ip->ip_off + ip->ip_len) - > GETIP(q)->ip_off; > if (i < GETIP(q)->ip_len) { > I don't understand how this patch works. Won't it end up using the wrong value for 'p' later on in the loop? Could you explain which mbuf is being used after its freed and in what circumstances. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 05:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14637 for freebsd-current-outgoing; Sun, 25 Oct 1998 05:56:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14631 for ; Sun, 25 Oct 1998 05:56:29 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id IAA18264; Sun, 25 Oct 1998 08:55:32 -0500 (EST) Date: Sun, 25 Oct 1998 08:55:31 -0500 (EST) From: Brian Feldman To: Mike Smith cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: countdown to ELF kernel? In-Reply-To: <199810190601.XAA16588@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I've been testing 3.0 for a while, and I have a question about ELF kernels and modules: will KLD modules work like LKM's still do for a.out? (i.e. they get autoloaded (the VFS ones)) Brian Feldman On Sun, 18 Oct 1998, Mike Smith wrote: > > Now that we're out of freeze, when are we throwing the switch again? > > MHO, give us a week or so to catch the 3.0-release generated bug traffic > before we launch this one. We're getting the usual post-release > betatesters showing up just now. 8) > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 06:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15325 for freebsd-current-outgoing; Sun, 25 Oct 1998 06:09:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15320 for ; Sun, 25 Oct 1998 06:09:47 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id PAA09251 for ; Sun, 25 Oct 1998 15:08:48 +0100 Date: Sun, 25 Oct 1998 15:08:47 +0100 (CET) From: N To: current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: <19981024192707.C183@Alameda.net> Message-ID: <981025150204.9115A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Ulf Zimmermann: > I have problems with the 3.0-R install on a net 10 install. The company I > work at uses 10.0/16 as the local address space and then a NAT/Firewall wall. > Adding a default route to 10.0.1.1 hangs for ever, even with a nameserver > configured. Installing with no DNS settings and using just plain IPs, the > install works fine. My experience: insert boot disk, boot computer, configure fxp0, hang on "Adding default route". Slap forehead, insert Ethernet cable. Unfortunately, once a DNS timeout seems to always be a DNS timeout on the boot disks; ^C'ing out of that particular message box is pretty impossible as well (it'll reboot if you try). Another thing I noticed yesterday: you can't have more than about ten disks attached when installing from boot.flp, else it'll run out of inodes creating the devices in /dev and have no space left for any temporary files in /tmp. I had to disconnect most of the external SCSI disks to even install 3.0. I tried some older boot disks but to no avail, they're all pretty short on inodes. Disklabel fails with a non-intuitive error if you try to disklabel a disk with half-complete entries in /dev, too. For the rest, 3.0 screams. :-) Take care, -- Niels. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 06:16:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15794 for freebsd-current-outgoing; Sun, 25 Oct 1998 06:16:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15772 for ; Sun, 25 Oct 1998 06:16:45 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id RAA21046; Sun, 25 Oct 1998 17:15:56 +0300 (MSK) Date: Sun, 25 Oct 1998 17:15:56 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: N cc: current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: <981025150204.9115A-100000@liquid.tpb.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, N wrote: > Date: Sun, 25 Oct 1998 15:08:47 +0100 (CET) > From: N > To: current@FreeBSD.ORG > Subject: Re: 3.0 installation problems > > Quoth Ulf Zimmermann: > > > I have problems with the 3.0-R install on a net 10 install. The company I > > work at uses 10.0/16 as the local address space and then a NAT/Firewall wall. > > Adding a default route to 10.0.1.1 hangs for ever, even with a nameserver > > configured. Installing with no DNS settings and using just plain IPs, the > > install works fine. > > My experience: insert boot disk, boot computer, configure fxp0, hang on > "Adding default route". Slap forehead, insert Ethernet cable. > Unfortunately, once a DNS timeout seems to always be a DNS timeout on the > boot disks; ^C'ing out of that particular message box is pretty impossible > as well (it'll reboot if you try). > I have the same problem - 3.0 works with fxp0, but I can't install it via it. (hangs on "Adding default route"). Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 06:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16327 for freebsd-current-outgoing; Sun, 25 Oct 1998 06:22:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16317 for ; Sun, 25 Oct 1998 06:22:00 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA21911; Sun, 25 Oct 1998 09:21:21 -0500 (EST) Date: Sun, 25 Oct 1998 09:21:20 -0500 (EST) From: Brian Feldman To: Studded cc: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <362B74B6.B9B256B4@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id GAA16319 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why don't we just use pdksh? It's even more compact than our current Bourne/partially-Korn shell, and has lots of great Korn shell features everyone loves but sh doesn't have. Cheers, Brian Feldman On Mon, 19 Oct 1998, Studded wrote: > "Dag-Erling C. Smørgrav" wrote: > > > > Why doesn't ~ expansion work in the following case: > > > > export GLORB=~ > > > > as it does in > > > > GLORB=~; export GLORB > > I've seen a couple of people complain about 'export foo=bar' causing > problems in our implementation of sh. I haven't looked at why it's a > problem but if it's any comfort, yes, it seems to be a bug. I've gotten > into the habit of using 'foo=bar; export foo' when using sh anyway since > it's more portable. > > Doug > -- > *** Chief Operations Officer, DALnet IRC network *** > > Go PADRES! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 06:24:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16557 for freebsd-current-outgoing; Sun, 25 Oct 1998 06:24:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16552 for ; Sun, 25 Oct 1998 06:24:15 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id PAA09402; Sun, 25 Oct 1998 15:23:11 +0100 Date: Sun, 25 Oct 1998 15:23:11 +0100 (CET) From: N To: Dmitry Valdov , current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: Message-ID: <981025151624.9339A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dmitry (and current), >> My experience: insert boot disk, boot computer, configure fxp0, hang on >> "Adding default route". Slap forehead, insert Ethernet cable. > I have the same problem - 3.0 works with fxp0, but I can't install it > via it. (hangs on "Adding default route"). In the end I succeeded without further obstacles, not even a single ftp timeout :-) although downloading seemed to go faster than actually extracting to disk. fxp0: rev 0x01 int a irq 16 on pci0.12.0 I also installed a box with an on-board 82558 (the above is an 82557 chipset), no trouble there either - as long as it's connected. :) I used IP addresses everywhere in the network configuration, except when selecting the ftp site where to retrieve the distribution from. The name server I use is on the same physical subnet, but I've seen it work with it on another physical subnet (so packets had to go via the default gateway)... -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 07:08:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18766 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:08:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18761 for ; Sun, 25 Oct 1998 07:08:36 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id KAA17233; Sun, 25 Oct 1998 10:07:02 -0500 (EST) Date: Sun, 25 Oct 1998 10:07:01 -0500 (EST) From: Chuck Robey To: Brian Feldman cc: Studded , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Brian Feldman wrote: > Why don't we just use pdksh? It's even more compact than our current > Bourne/partially-Korn shell, and has lots of great Korn shell features > everyone loves but sh doesn't have. Not being a pdksh user, well, I know YOU are aware of the importance of not breaking ANY sh scripts for users, whether they're part of our base or not, because sh is the shell everyone writes in for portability, and it mustn't ever be broken ... so, is pdksh 100% compatible with sh, at least upwardly? I mean wth NO changes to ANY sh script? Do buildworlds complete, with pdksh in place as the shell, instead of sh? I'm not against this per se, but those are pretty important hurdles to go over, and I'm wary. Give us a lecture on it. Making this change would be neat, if it's truly possible. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 07:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21168 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:35:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21159 for ; Sun, 25 Oct 1998 07:35:29 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA22757; Sun, 25 Oct 1998 10:34:34 -0500 (EST) Date: Sun, 25 Oct 1998 10:34:34 -0500 (EST) From: Brian Feldman To: Doug Rabson cc: Don Lewis , Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's _my_ patch: insert in sys/netinet/ip_input.c:796 if (fp->ipq_frags == NULL) /* XXX */ goto dropfrag; (hint: goes after the "next = 0;") Cheers, Brian Feldman On Sun, 25 Oct 1998, Doug Rabson wrote: > On Sun, 25 Oct 1998, Don Lewis wrote: > > > Ok, I figured out what's going on. When I compiled the nestea2.c under > > FreeBSD, it didn't run at all because rip_output() does some sanity > > checking between ip_len in the packet and the actual packet length, so > > it doesn't send the third fragment and causes sendto() to return > > EINVAL. The Linux emulation code in the kernel is kind enough to fix > > ip_len, so the sanity check passes. Even after I fixed this in > > nestea2.c, running it still didn't cause the system to panic. The > > reason for this is some differences in byte swapping in the IP header > > fields between Linux and FreeBSD that nestea2.c attempted to compensate > > for, but didn't get right. Once I fixed the byte swapping problem, I > > got the same panic you did, except for the linux emulation which I was > > not using. > > > > The panic is caused by a bug in the new ip fragment reassembly code > > that can be provoked into playing with an mbuf after it has been freed. > > Here's a patch. > > > > --- ip_input.c.orig Fri Oct 23 02:17:19 1998 > > +++ ip_input.c Sun Oct 25 01:50:20 1998 > > @@ -750,7 +750,7 @@ > > * if they are completely covered, dequeue them. > > */ > > for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; > > - p = q, q = nq) { > > + q = nq) { > > i = (ip->ip_off + ip->ip_len) - > > GETIP(q)->ip_off; > > if (i < GETIP(q)->ip_len) { > > > > I don't understand how this patch works. Won't it end up using the wrong > value for 'p' later on in the loop? Could you explain which mbuf is being > used after its freed and in what circumstances. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > Fax: +44 181 381 1039 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 07:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21647 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:39:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21614 for ; Sun, 25 Oct 1998 07:39:15 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA22777; Sun, 25 Oct 1998 10:38:33 -0500 (EST) Date: Sun, 25 Oct 1998 10:38:33 -0500 (EST) From: Brian Feldman To: Chuck Robey cc: Studded , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IIRC, OpenBSD uses it... Anyway, by definition, the Korn shell is a superset of the Bourne shell, so it's entirely backward-compatible. In fact, I'll let you know in a few minutes, I'll replace /bin/sh with /bin/ksh, reboot, and see how all the rc initialization works. I expect it to work completely correctly, so if it doesn't, I'll be surprised :) So of course, it should be 100% compatible, but I'll try a reboot with ksh in place of sh, and I'll try a make world with ksh instead. More later. Cheers, Brian Feldman P.S: NO, this is _nothing_ like Linux using BASH. BASH is horrible :P On Sun, 25 Oct 1998, Chuck Robey wrote: > On Sun, 25 Oct 1998, Brian Feldman wrote: > > > Why don't we just use pdksh? It's even more compact than our current > > Bourne/partially-Korn shell, and has lots of great Korn shell features > > everyone loves but sh doesn't have. > > Not being a pdksh user, well, I know YOU are aware of the importance of > not breaking ANY sh scripts for users, whether they're part of our base > or not, because sh is the shell everyone writes in for portability, and > it mustn't ever be broken ... so, is pdksh 100% compatible with sh, at > least upwardly? I mean wth NO changes to ANY sh script? > > Do buildworlds complete, with pdksh in place as the shell, instead of > sh? > > I'm not against this per se, but those are pretty important hurdles to > go over, and I'm wary. Give us a lecture on it. Making this change > would be neat, if it's truly possible. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 07:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22410 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:49:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22405 for ; Sun, 25 Oct 1998 07:49:11 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA22909; Sun, 25 Oct 1998 10:48:23 -0500 (EST) Date: Sun, 25 Oct 1998 10:48:22 -0500 (EST) From: Brian Feldman To: Chuck Robey cc: Studded , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion: ksh testing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, all the rc(5) scripts work flawlessly! :) All my user scripts work flawlessly, GNU configure works flawlessly, and PERL5's config scripts work fine too. As a bonus, pdksh has better PS[1-4] support, and co-processes (blah |&). I'll be using pdksh as /bin/sh from now on, and if I run into any trouble, I'll let you know. {"/home/green"}$ l /bin/*sh* -r-xr-xr-x 1 root wheel 258328 Oct 19 01:37 /bin/csh -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh lrwxr-xr-x 1 root wheel 3 Oct 25 10:39 /bin/sh -> ksh -r-xr-xr-x 1 root wheel 321120 Oct 19 01:37 /bin/sh.old {"/home/green"}$ what /bin/ksh | head -2 /bin/ksh: PD KSH v5.2.13 97/10/27 Cheers, Brian Feldman On Sun, 25 Oct 1998, Brian Feldman wrote: > IIRC, OpenBSD uses it... Anyway, by definition, the Korn shell is a > superset of the Bourne shell, so it's entirely backward-compatible. In > fact, I'll let you know in a few minutes, I'll replace /bin/sh with > /bin/ksh, reboot, and see how all the rc initialization works. I expect it > to work completely correctly, so if it doesn't, I'll be surprised :) So of > course, it should be 100% compatible, but I'll try a reboot with ksh in > place of sh, and I'll try a make world with ksh instead. More later. > > Cheers, > Brian Feldman > > P.S: NO, this is _nothing_ like Linux using BASH. BASH is horrible :P > > On Sun, 25 Oct 1998, Chuck Robey wrote: > > > On Sun, 25 Oct 1998, Brian Feldman wrote: > > > > > Why don't we just use pdksh? It's even more compact than our current > > > Bourne/partially-Korn shell, and has lots of great Korn shell features > > > everyone loves but sh doesn't have. > > > > Not being a pdksh user, well, I know YOU are aware of the importance of > > not breaking ANY sh scripts for users, whether they're part of our base > > or not, because sh is the shell everyone writes in for portability, and > > it mustn't ever be broken ... so, is pdksh 100% compatible with sh, at > > least upwardly? I mean wth NO changes to ANY sh script? > > > > Do buildworlds complete, with pdksh in place as the shell, instead of > > sh? > > > > I'm not against this per se, but those are pretty important hurdles to > > go over, and I'm wary. Give us a lecture on it. Making this change > > would be neat, if it's truly possible. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (NetBSD). > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 07:55:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22914 for freebsd-current-outgoing; Sun, 25 Oct 1998 07:55:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22909 for ; Sun, 25 Oct 1998 07:55:38 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA23021; Sun, 25 Oct 1998 10:55:03 -0500 (EST) Date: Sun, 25 Oct 1998 10:55:02 -0500 (EST) From: Brian Feldman To: Nathan Dorfman cc: freebsd-current@FreeBSD.ORG Subject: Re: libmytinfo breaks vim-5.3 port, maybe others? In-Reply-To: <19981023205115.A5357@rtfm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... I never bothered checking that. I noticed that tputs broke it, so I commented out that define (HAVE_TERMWHATEVER) in that single file with tputs. But pleased to know someone figured out what was really going on, even if it doesn't matter much to me since changing that tputs works as well :) Cheers, Brian Feldman On Fri, 23 Oct 1998, Nathan Dorfman wrote: > Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with > libmytinfo. At first I thought it was vim breakage, or Motif/Athena > or even X11 breakage. But read on: > > CPU states: 14.8% user, 0.0% nice, 84.0% system, 1.2% interrupt, 0.0% idle > > 5411 root 89 0 3692K 2960K RUN 0:33 92.19% 76.98% vim > 243 nathan 2 0 12344K 4060K select 21:49 4.39% 4.39% XF86_SVGA > > After gdb vim 5411, it has this to say: > > (gdb) bt > #0 0x283524da in tputs () > #1 0x80a7146 in XtVaGetApplicationResources () > #2 0x807bb81 in XtVaGetApplicationResources () > #3 0x808c865 in XtVaGetApplicationResources () > #4 > #5 0x283524da in tputs () > #6 0x80a7146 in XtVaGetApplicationResources () > #7 0x80a7ab9 in XtVaGetApplicationResources () > #8 0x806f84d in XtVaGetApplicationResources () > #9 0x804b275 in XtVaGetApplicationResources () > > Anyway, I noticed something weird: > > libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000) > > According to find -exec grep, this library is not mentioned anywhere > in the vim port or work dir. Are things being linked with it automagically > for some reason? Anyway, moving libtmyinfo.so.2 to foo and rebuilding > vim: built and ran fine. Anyone? Pilot error? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 08:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25260 for freebsd-current-outgoing; Sun, 25 Oct 1998 08:40:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25253 for ; Sun, 25 Oct 1998 08:40:03 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id KAA05408; Sun, 25 Oct 1998 10:36:59 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <363353AB.BCE48ADC@webwizard.org.mx> Date: Sun, 25 Oct 1998 10:36:59 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Feldman CC: Chuck Robey , Studded , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > IIRC, OpenBSD uses it... Anyway, by definition, the Korn shell is a > superset of the Bourne shell, so it's entirely backward-compatible. In > fact, I'll let you know in a few minutes, I'll replace /bin/sh with > /bin/ksh, reboot, and see how all the rc initialization works. I expect it > to work completely correctly, so if it doesn't, I'll be surprised :) So of > course, it should be 100% compatible, but I'll try a reboot with ksh in > place of sh, and I'll try a make world with ksh instead. More later. > > Cheers, > Brian Feldman > > P.S: NO, this is _nothing_ like Linux using BASH. BASH is horrible :P > > On Sun, 25 Oct 1998, Chuck Robey wrote: > > > On Sun, 25 Oct 1998, Brian Feldman wrote: > > > > > Why don't we just use pdksh? It's even more compact than our current > > > Bourne/partially-Korn shell, and has lots of great Korn shell features > > > everyone loves but sh doesn't have. > > > > Not being a pdksh user, well, I know YOU are aware of the importance of > > not breaking ANY sh scripts for users, whether they're part of our base > > or not, because sh is the shell everyone writes in for portability, and > > it mustn't ever be broken ... so, is pdksh 100% compatible with sh, at > > least upwardly? I mean wth NO changes to ANY sh script? > > > > Do buildworlds complete, with pdksh in place as the shell, instead of > > sh? > > > > I'm not against this per se, but those are pretty important hurdles to > > go over, and I'm wary. Give us a lecture on it. Making this change > > would be neat, if it's truly possible. > > I've been using pdksh for more than three years, first on Linux and then FreeBSD. I haven't even had a /bin/sh or much less bash in a passwd file for several years and haven't had a problem. I make world almost every day, make release about once a week, etc. saludos ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 09:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00263 for freebsd-current-outgoing; Sun, 25 Oct 1998 09:54:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00258 for ; Sun, 25 Oct 1998 09:54:30 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id MAA94118; Sun, 25 Oct 1998 12:54:31 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: References: <19981024083632.N28824@freebie.lemis.com> <199810232221.PAA08852@usr07.primenet.com>; from Terry Lambert on Fri, Oct 23, 1998 at 10:21:23PM +0000 <199810232221.PAA08852@usr07.primenet.com> Date: Sun, 25 Oct 1998 13:58:39 -0400 To: Bob Bishop From: Garance A Drosihn Subject: Re: Interesting 3.0 bug Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:03 PM +0000 10/24/98, Bob Bishop wrote: > Hi, > > FWIW I get the same result as Terry both on 2.2.5R and 3.0-CURRENT. > > I wonder if it's a TERM thang? vt100 here It is not a TERM thing. It is old enough that the problem is even mentioned in the man page for 'more'. There have been a half-dozen send-pr reports about this, one of which included a patch to fix the bug. (perhaps not the best fix imaginable, but a fix nonetheless). See problem report bin/7296, for instance. Last I knew someone was testing this bug fix along the way to including it in the official distribution. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 09:54:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00315 for freebsd-current-outgoing; Sun, 25 Oct 1998 09:54:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00298; Sun, 25 Oct 1998 09:54:47 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id SAA05168; Sun, 25 Oct 1998 18:54:13 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id SAA01103; Sun, 25 Oct 1998 18:38:10 +0100 (MET) (envelope-from wosch) Message-ID: <19981025183809.A1096@panke.de.freebsd.org> Date: Sun, 25 Oct 1998 18:38:09 +0100 From: Wolfram Schneider To: current@FreeBSD.ORG Cc: wosch@FreeBSD.ORG Subject: Missing IDE CD-ROM after 3.0 upgrade Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just updated from 2.2.6R to 3.0. The new 3.0 kernel does not find the CD-ROM anymore ;-( What's wrong? I can still boot from the 2.2.6R CD-ROM so it seems not a hardware problem. I'm using the GENERIC kernel. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #8: Fri Oct 23 09:57:01 GMT 1998 root@paula.panke.de.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 1476 ns CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 127787008 (124792K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0xc3 on pci0.7.0 ide_pci0: rev 0xc1 int a irq 0 on pci0. 15.0 ide_pci: controller is simplex, no DMA on secondary channel Probing for devices on PCI bus 1: vga0: rev 0x10 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 ^^^^^^^^^^^^^^^^^^^^^^^ the 2.2.6R kernel found wdc1 and wcd at irq 15. Wolfram -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 10:09:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01597 for freebsd-current-outgoing; Sun, 25 Oct 1998 10:09:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01590 for ; Sun, 25 Oct 1998 10:09:30 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Sun, 25 Oct 1998 18:08:26 -0000 Message-ID: From: Paul Richards To: "'Terry Lambert'" , dnelson@emsphone.com Cc: sthaug@nethelp.no, freebsd-current@FreeBSD.ORG Subject: RE: What kind of SCSI controller is in a Compaq Proliant 3000? Date: Sun, 25 Oct 1998 18:08:25 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a little late, I've got a hefty -current backlog I'm clearing. I've definately seen Compaq's with AMD SCSI controllers, I can't remember whether they were proliants though. I thought we had support for them as well? Paul Richards Ph.D. Originative Solutions Ltd > -----Original Message----- > From: Terry Lambert [mailto:tlambert@primenet.com] > Sent: Thursday, October 08, 1998 3:18 AM > To: dnelson@emsphone.com > Cc: sthaug@nethelp.no; freebsd-hardware@freebsd.org; > freebsd-current@freebsd.org > Subject: Re: What kind of SCSI controller is in a Compaq > Proliant 3000? > > > > > Just got my hands on a nice shiny new Compaq Proliant > 3000 server (yes, > > > I know Compaqs are weird in some ways, but this is beyond > my control). > > > I'd like to install FreeBSD on it, but the problem is > that no SCSI disk > > > controller is detected (and thus no SCSI disks) by the > 3.0 boot disk. > > > The standard Proliant 3000 config: > > > > > > http://www.compaq.com/products/servers/proliant3000/index.html > > > > > > mentions a dual channel wide-ultra SCSI-3 controller, and > this is indeed > > > what the BIOS claims it has. > > > > I believe all of the Compaq SCSI adaptors (except possible the RAID > > ones) are Symbios/NCR chipsets. At least out Proliant 2500 is, and > > there is just one Compaq SCSI HAM driver for Netware, so it > must cover > > all the Compaq cards. > > If this is the RAID controller, a driver was written, but not > integrated into -current. Check the list archives for "compaq RAID". > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 10:20:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02356 for freebsd-current-outgoing; Sun, 25 Oct 1998 10:20:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seawall.ninthwave.com (ninthwave.com [209.31.6.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02265 for ; Sun, 25 Oct 1998 10:19:41 -0800 (PST) (envelope-from jdi@ninthwave.com) Received: from ninthwave.com (kuta.ninthwave.com [10.0.0.2]) by seawall.ninthwave.com (8.9.1/8.9.1) with ESMTP id KAA01236; Sun, 25 Oct 1998 10:16:13 -0800 (PST) (envelope-from jdi@ninthwave.com) Message-ID: <36336AF4.EEBFFC63@ninthwave.com> Date: Sun, 25 Oct 1998 10:16:20 -0800 From: John Irwin X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" , wolf@cologne.de, se@mi.Uni-Koeln.de CC: Michael Class , current@FreeBSD.ORG Subject: Re: CAM and quantum disc References: <199809231405.IAA21990@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > The Atlas II's will keep returning queue full until we have reduced the tag > count to 0. That's why we put in a lower limit of 24. We don't allow the > tag count to go below that; we just retry. Unfortunately the retry code for the NCR controller appears to have problems. I get a very consistent "page fault in kernel mode" panic when trying to restore a dumped filesystem to my Atlas II. This is with the 3.0-release tag, but ncr.c doesn't appear to have changed since then. My setup: rev 0x04 int a irq 9 on pci0.10.0 Fixed Direct Access SCSI2 device Serial Number PCB=2011300002 ; HDA=182710655437 40.0MB/s transfers (20.0MHz, offset 16, 16bit), Tagged Queueing Enabled Before the panic occurs, I get the expected series of kernel messages showing that the tagged openings limit is reduced in stages to 24. A while later, during the file part of the restore, I get the panic. I've been unable to get a kernel core dump as the panic doesn't complete. >From the 'ddb' output, the page fault is at 0x34, with the PC in: ncr_int_sir ncr.c 6405 pushl 0x34(%eax) from (ncr_exception, ncr.c, 5442) from (ncr_intr, ncr.c, 3912) which implies that the ccb is null. Unfortunately my knowledge of SCSI & CAM is insufficient to get much past there without a long climb up the learning curve. (Last filesystem hacking was in 4.3 era). Thanks, -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 10:58:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05100 for freebsd-current-outgoing; Sun, 25 Oct 1998 10:58:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05086 for ; Sun, 25 Oct 1998 10:57:58 -0800 (PST) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id UAA05229; Sun, 25 Oct 1998 20:57:18 +0200 (EET) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id UAA05964; Sun, 25 Oct 1998 20:57:17 +0200 (EET) From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13875.29837.857622.135349@zeta.fidata.fi> Date: Sun, 25 Oct 1998 20:57:17 +0200 (EET) To: "Daniel M. Eischen" CC: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 + CAM + xmcd-2.3 In-Reply-To: <199810250257.VAA06346@iworks.interworks.org> References: <199810250257.VAA06346@iworks.interworks.org> X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Reply-To: tomppa@fidata.fi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel M. Eischen writes: > It works OK for me. I just rebuilt it from ports just to > be sure. My system is -current from Oct 18. > > Are you sure you're using the passN device? > Thanks! I had only four pass devices but I need six of them. Tomppa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 11:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07375 for freebsd-current-outgoing; Sun, 25 Oct 1998 11:27:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07369 for ; Sun, 25 Oct 1998 11:27:40 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id WAA26214 for ; Sun, 25 Oct 1998 22:27:00 +0300 (MSK) Date: Sun, 25 Oct 1998 22:27:00 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@FreeBSD.ORG Subject: todays kernel won't compile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout ../../kern/kern_synch.c ../../kern/kern_synch.c: In function oundrobin': ../../kern/kern_synch.c:146: ' undeclared (first use this function) ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only once ../../kern/kern_synch.c:146: for each function it appears in.) *** Error code 1 Stop. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 11:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08560 for freebsd-current-outgoing; Sun, 25 Oct 1998 11:37:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08551 for ; Sun, 25 Oct 1998 11:37:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id LAA17155; Sun, 25 Oct 1998 11:36:59 -0800 Date: Sun, 25 Oct 1998 11:36:59 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dmitry Valdov cc: freebsd-current@FreeBSD.ORG Subject: Re: todays kernel won't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm- it sounds like your update didn't happen right. I just did an update, got some CVS warnings about checksum errors on a patch and then a refetch of files. The junk that your compile urped on I never saw. On Sun, 25 Oct 1998, Dmitry Valdov wrote: > Hi! > > Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- > -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout > ../../kern/kern_synch.c > ../../kern/kern_synch.c: In function oundrobin': > ../../kern/kern_synch.c:146: ' undeclared (first use this function) > ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only > once > ../../kern/kern_synch.c:146: for each function it appears in.) > *** Error code 1 > > Stop. > > > Dmitry. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 11:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08991 for freebsd-current-outgoing; Sun, 25 Oct 1998 11:40:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08957 for ; Sun, 25 Oct 1998 11:40:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA01172; Sun, 25 Oct 1998 20:38:27 +0100 (CET) To: Dmitry Valdov cc: freebsd-current@FreeBSD.ORG Subject: Re: todays kernel won't compile In-reply-to: Your message of "Sun, 25 Oct 1998 22:27:00 +0300." Date: Sun, 25 Oct 1998 20:38:27 +0100 Message-ID: <1170.909344307@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG looks like your file is corrupt... I can't see that corruption on freefall... In message , Dmitry Vald ov writes: >Hi! > >Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > >cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit >-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >-Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- >-I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout >../../kern/kern_synch.c >../../kern/kern_synch.c: In function oundrobin': >../../kern/kern_synch.c:146: ' undeclared (first use this function) >../../kern/kern_synch.c:146: (Each undeclared identifier is reported only >once >../../kern/kern_synch.c:146: for each function it appears in.) >*** Error code 1 > >Stop. > > >Dmitry. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 11:45:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09515 for freebsd-current-outgoing; Sun, 25 Oct 1998 11:45:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09467 for ; Sun, 25 Oct 1998 11:45:16 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id WAA26735; Sun, 25 Oct 1998 22:44:21 +0300 (MSK) Date: Sun, 25 Oct 1998 22:44:21 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Matthew Jacob cc: freebsd-current@FreeBSD.ORG Subject: Re: todays kernel won't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May be You have SMP defined? kern_synch.c has an #ifdef SMP there. On Sun, 25 Oct 1998, Matthew Jacob wrote: > Date: Sun, 25 Oct 1998 11:36:59 -0800 (PST) > From: Matthew Jacob > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: todays kernel won't compile > > > Umm- it sounds like your update didn't happen right. I just > did an update, got some CVS warnings about checksum errors > on a patch and then a refetch of files. The junk that your compile > urped on I never saw. > > On Sun, 25 Oct 1998, Dmitry Valdov wrote: > > > Hi! > > > > Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > > > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- > > -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout > > ../../kern/kern_synch.c > > ../../kern/kern_synch.c: In function oundrobin': > > ../../kern/kern_synch.c:146: ' undeclared (first use this function) > > ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only > > once > > ../../kern/kern_synch.c:146: for each function it appears in.) > > *** Error code 1 > > > > Stop. > > > > > > Dmitry. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 11:51:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10528 for freebsd-current-outgoing; Sun, 25 Oct 1998 11:51:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10521 for ; Sun, 25 Oct 1998 11:51:29 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA18492; Sun, 25 Oct 1998 12:42:51 -0700 (MST) Date: Sun, 25 Oct 1998 12:42:51 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199810251942.MAA18492@narnia.plutotech.com> To: John Irwin cc: current@FreeBSD.ORG Subject: Re: CAM and quantum disc X-Newsgroups: pluto.freebsd.current In-Reply-To: <199809231405.IAA21990@panzer.plutotech.com> <36336AF4.EEBFFC63@ninthwave.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <36336AF4.EEBFFC63@ninthwave.com> you wrote: > > > "Kenneth D. Merry" wrote: > >> The Atlas II's will keep returning queue full until we have reduced the tag >> count to 0. That's why we put in a lower limit of 24. We don't allow the >> tag count to go below that; we just retry. > > Unfortunately the retry code for the NCR controller appears to have problems. > I get a very consistent "page fault in kernel mode" panic when trying to > restore a dumped filesystem to my Atlas II. This is with the 3.0-release > tag, but ncr.c doesn't appear to have changed since then. > > My setup: > rev 0x04 int a irq 9 on pci0.10.0 > > Fixed Direct Access SCSI2 device > Serial Number PCB=2011300002 ; HDA=182710655437 > 40.0MB/s transfers (20.0MHz, offset 16, 16bit), Tagged Queueing Enabled You should be running LYK8 on that drive. That doesn't excuse the ncr driver panicing of course, but it may help you to avoid the problem. Can you hook up a serial console or remote gdb and give me an exact traceback? Either that or transpose the traceback by hand. A listing of the contents of the ncr_ccb would be useful too. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 12:08:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12787 for freebsd-current-outgoing; Sun, 25 Oct 1998 12:08:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12782 for ; Sun, 25 Oct 1998 12:08:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA00981; Sun, 25 Oct 1998 09:09:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810251709.JAA00981@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Paul Richards cc: freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-reply-to: Your message of "Sun, 25 Oct 1998 18:08:25 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Oct 1998 09:09:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a little late, I've got a hefty -current backlog I'm clearing. > > I've definately seen Compaq's with AMD SCSI controllers, I can't > remember whether they were proliants though. I thought we had support > for them as well? Older ones did, yes. We lost the support with the CAM changeover; the old AMD driver is impenetrable and nobody surfaced to convert it or maintain it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 12:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13332 for freebsd-current-outgoing; Sun, 25 Oct 1998 12:12:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13325 for ; Sun, 25 Oct 1998 12:12:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA01008; Sun, 25 Oct 1998 09:12:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810251712.JAA01008@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: countdown to ELF kernel? In-reply-to: Your message of "Sun, 25 Oct 1998 08:55:31 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Oct 1998 09:12:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, I've been testing 3.0 for a while, and I have a question about ELF > kernels and modules: > will KLD modules work like LKM's still do for a.out? (i.e. they > get autoloaded (the VFS ones)) No, we've abandoned all the convenience features that everybody didn't really like anyway. You need to connect a microphone to a Soundblaster-compatible soundcard and issue VFS load instructions in Esperanto. You should only speak while the cursor is off (there isn't enough CPU left over while the cursor is on to handle the translation). Actually, I'm not sure if demand-loading VFS modules works yet; Peter is busy being eaten alive by the ATO (the Australian eqivalent of the IRS) and I have a sneaking suspicion that the old code may have been LKM specific. Tell us whether it works, hmm? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 12:18:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13840 for freebsd-current-outgoing; Sun, 25 Oct 1998 12:18:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13835 for ; Sun, 25 Oct 1998 12:18:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id MAA17470; Sun, 25 Oct 1998 12:17:45 -0800 Date: Sun, 25 Oct 1998 12:17:45 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dmitry Valdov cc: freebsd-current@FreeBSD.ORG Subject: Re: todays kernel won't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops you were right- but the messages seemed to indicate otherwise (^R for 'r', ^P for 'p'). On Sun, 25 Oct 1998, Matthew Jacob wrote: > > Umm- it sounds like your update didn't happen right. I just > did an update, got some CVS warnings about checksum errors > on a patch and then a refetch of files. The junk that your compile > urped on I never saw. > > On Sun, 25 Oct 1998, Dmitry Valdov wrote: > > > Hi! > > > > Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > > > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- > > -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout > > ../../kern/kern_synch.c > > ../../kern/kern_synch.c: In function oundrobin': > > ../../kern/kern_synch.c:146: ' undeclared (first use this function) > > ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only > > once > > ../../kern/kern_synch.c:146: for each function it appears in.) > > *** Error code 1 > > > > Stop. > > > > > > Dmitry. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 12:23:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14455 for freebsd-current-outgoing; Sun, 25 Oct 1998 12:23:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA14447 for ; Sun, 25 Oct 1998 12:23:46 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 22818 invoked by uid 1001); 25 Oct 1998 20:23:11 +0000 (GMT) To: mike@smith.net.au Cc: paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-Reply-To: Your message of "Sun, 25 Oct 1998 09:09:05 -0800" References: <199810251709.JAA00981@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 25 Oct 1998 21:23:11 +0100 Message-ID: <22816.909346991@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've definately seen Compaq's with AMD SCSI controllers, I can't > > remember whether they were proliants though. I thought we had support > > for them as well? > > Older ones did, yes. We lost the support with the CAM changeover; the > old AMD driver is impenetrable and nobody surfaced to convert it or > maintain it. The Proliant 3000 I was asking about has an NCR/Symbios 53c876 based dual channel controller. Up and running 2.2.7 at the moment. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 12:25:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14907 for freebsd-current-outgoing; Sun, 25 Oct 1998 12:25:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14894 for ; Sun, 25 Oct 1998 12:25:47 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id XAA27481; Sun, 25 Oct 1998 23:24:59 +0300 (MSK) Date: Sun, 25 Oct 1998 23:24:59 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Matthew Jacob cc: freebsd-current@FreeBSD.ORG Subject: Re: todays kernel won't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! It's because JOE interprets ` as insertion of control character :( There must be: `p' undeclared ... :) On Sun, 25 Oct 1998, Matthew Jacob wrote: > Date: Sun, 25 Oct 1998 12:17:45 -0800 (PST) > From: Matthew Jacob > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: todays kernel won't compile > > > Oops you were right- but the messages seemed to indicate > otherwise (^R for 'r', ^P for 'p'). > > On Sun, 25 Oct 1998, Matthew Jacob wrote: > > > > > Umm- it sounds like your update didn't happen right. I just > > did an update, got some CVS warnings about checksum errors > > on a patch and then a refetch of files. The junk that your compile > > urped on I never saw. > > > > On Sun, 25 Oct 1998, Dmitry Valdov wrote: > > > > > Hi! > > > > > > Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > > > > > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- > > > -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout > > > ../../kern/kern_synch.c > > > ../../kern/kern_synch.c: In function oundrobin': > > > ../../kern/kern_synch.c:146: ' undeclared (first use this function) > > > ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only > > > once > > > ../../kern/kern_synch.c:146: for each function it appears in.) > > > *** Error code 1 > > > > > > Stop. > > > > > > > > > Dmitry. > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 13:13:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18202 for freebsd-current-outgoing; Sun, 25 Oct 1998 13:13:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18197 for ; Sun, 25 Oct 1998 13:13:13 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id PAA05993; Sun, 25 Oct 1998 15:12:01 -0600 (CST) From: Kevin Day Message-Id: <199810252112.PAA05993@home.dragondata.com> Subject: Re: todays kernel won't compile In-Reply-To: from Matthew Jacob at "Oct 25, 98 12:17:45 pm" To: mjacob@feral.com Date: Sun, 25 Oct 1998 15:12:01 -0600 (CST) Cc: dv@dv.ru, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oops you were right- but the messages seemed to indicate > otherwise (^R for 'r', ^P for 'p'). > This is due to pasting text directly into joe... joe considers ` a control character.... typing `R is interpreted as ^R. Kevin > On Sun, 25 Oct 1998, Matthew Jacob wrote: > > > > > Umm- it sounds like your update didn't happen right. I just > > did an update, got some CVS warnings about checksum errors > > on a patch and then a refetch of files. The junk that your compile > > urped on I never saw. > > > > On Sun, 25 Oct 1998, Dmitry Valdov wrote: > > > > > Hi! > > > > > > Just CVSuped 3.0-CURRENT...I've a problem compiling kernel: > > > > > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > > -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- > > > -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout > > > ../../kern/kern_synch.c > > > ../../kern/kern_synch.c: In function oundrobin': > > > ../../kern/kern_synch.c:146: ' undeclared (first use this function) > > > ../../kern/kern_synch.c:146: (Each undeclared identifier is reported only > > > once > > > ../../kern/kern_synch.c:146: for each function it appears in.) > > > *** Error code 1 > > > > > > Stop. > > > > > > > > > Dmitry. > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 13:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18569 for freebsd-current-outgoing; Sun, 25 Oct 1998 13:17:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18562 for ; Sun, 25 Oct 1998 13:17:18 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA06504; Sun, 25 Oct 1998 13:16:35 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36339533.49D5D9F0@gorean.org> Date: Sun, 25 Oct 1998 13:16:35 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Feldman CC: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > > Why don't we just use pdksh? Oh dear. I've had in the back of my mind for a long time to suggest us replacing our pseudo-implementation of sh with Bash in posix mode, but I haven't made the suggestion because I can think of at least 3 holy wars that it would start right off hand, and I can guess that there are more I don't know about. :) In my opinion if we're going to replace our sh with anything it should be something as posix as possible. That is the trend amongst the various vendors and right now there is no clear winner between continuing with "historic" bourne shell implementations and posix versions, although the trend is toward posix and that direction seems to have the momentum. Amongst the publicly available shells Bash has a lot of virtues for a project like this. It's one of the older public shells, has a broad and deep installed base, and is being actively developed. It incorporates the best features from other shells, and posix compliance is a high priority. Some may think that the fact linux uses bash would be a drawback, personally I think it's an advantage since linux users who migrate would have a common point of contact. Finally, I've gathered from various comments that Chet (the principle maintainer for Bash) has made that he uses FreeBSD as his main platform. :) The other thing I would suggest is that anyone who's serious about making something like this happen read comp.unix.shell for about a month before the debate continues. There is a lot of information available, and if we're serious about making this kind of change those making the decision should be as well informed as possible. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 13:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19298 for freebsd-current-outgoing; Sun, 25 Oct 1998 13:27:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19293 for ; Sun, 25 Oct 1998 13:27:25 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id QAA26955; Sun, 25 Oct 1998 16:25:53 -0500 (EST) Date: Sun, 25 Oct 1998 16:25:53 -0500 (EST) From: Chuck Robey To: Studded cc: Brian Feldman , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <36339533.49D5D9F0@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Studded wrote: > Brian Feldman wrote: > > > > Why don't we just use pdksh? > > Oh dear. I've had in the back of my mind for a long time to suggest us > replacing our pseudo-implementation of sh with Bash in posix mode, but I > haven't made the suggestion because I can think of at least 3 holy wars > that it would start right off hand, and I can guess that there are more > I don't know about. :) In my opinion if we're going to replace our sh > with anything it should be something as posix as possible. That is the > trend amongst the various vendors and right now there is no clear winner > between continuing with "historic" bourne shell implementations and > posix versions, although the trend is toward posix and that direction > seems to have the momentum. Doug, think about this ... sh is used universally because it's the lowest common denominator, and all scripts are done that way. Any change to our default 'sh' must, first and foremost, work with distributed shell scripts. Posix compatibility has nearly nothing at all to do with that, and bash is an extremely poor choice for that. Posix compatibility in this case is a buzzword only, and not a goal to be considered as good. General sh compatibility is the only touchstone here. Pdksh happens to hold a position close (but not, as Tor Egge pointed out, completely) sh compatible, so it could be at least considered as a candidate. Bash, unfortunately, isn't in that league. > > Amongst the publicly available shells Bash has a lot of virtues for a > project like this. It's one of the older public shells, has a broad and > deep installed base, and is being actively developed. It incorporates > the best features from other shells, and posix compliance is a high > priority. Some may think that the fact linux uses bash would be a > drawback, personally I think it's an advantage since linux users who > migrate would have a common point of contact. Finally, I've gathered > from various comments that Chet (the principle maintainer for Bash) has > made that he uses FreeBSD as his main platform. :) > > The other thing I would suggest is that anyone who's serious about > making something like this happen read comp.unix.shell for about a month > before the debate continues. There is a lot of information available, > and if we're serious about making this kind of change those making the > decision should be as well informed as possible. > > Doug > -- > *** Chief Operations Officer, DALnet IRC network *** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 13:53:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21382 for freebsd-current-outgoing; Sun, 25 Oct 1998 13:53:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21377 for ; Sun, 25 Oct 1998 13:53:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id NAA03599 for current@freebsd.org; Sun, 25 Oct 1998 13:52:54 -0800 (PST) (envelope-from obrien) Message-ID: <19981025135254.A3545@nuxi.com> Date: Sun, 25 Oct 1998 13:52:54 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: sh and ~ expansion Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Sun, Oct 25, 1998 at 10:07:01AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Give us a lecture on it. Making this change would be neat, if it's > truly possible. License-wise it is OK (MIT/BSD/CMU-style copyright). There is one file, aclocal.m4, that is a modified version of some GNU autoconf file. So it is under the GLP, but once Bmaked (ie, no GNU configure), this is not an issue. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 14:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24409 for freebsd-current-outgoing; Sun, 25 Oct 1998 14:45:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24404 for ; Sun, 25 Oct 1998 14:45:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA15593; Sun, 25 Oct 1998 17:44:09 -0500 (EST) Date: Sun, 25 Oct 1998 17:44:09 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith cc: Paul Richards , freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-Reply-To: <199810251709.JAA00981@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Mike Smith wrote: > > This is a little late, I've got a hefty -current backlog I'm clearing. > > > > I've definately seen Compaq's with AMD SCSI controllers, I can't > > remember whether they were proliants though. I thought we had support > > for them as well? > > Older ones did, yes. We lost the support with the CAM changeover; the > old AMD driver is impenetrable and nobody surfaced to convert it or > maintain it. Which older ones? I know the to old Compaq box I have with builtin SCSI uses the NCR 53c7xx chip which, to my knowledge, we never supported. (I do have the databook on it though...) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 15:36:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28621 for freebsd-current-outgoing; Sun, 25 Oct 1998 15:36:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28606 for ; Sun, 25 Oct 1998 15:36:04 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA07424; Sun, 25 Oct 1998 15:34:59 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <3633B5A2.F1068A0F@gorean.org> Date: Sun, 25 Oct 1998 15:34:58 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey CC: Brian Feldman , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And so it begins... Chuck Robey wrote: > Doug, think about this ... sh is used universally because it's the > lowest common denominator, and all scripts are done that way. Any > change to our default 'sh' must, first and foremost, work with > distributed shell scripts. Ok, WHICH version of sh do you want to maintain compatability with? I can think of 3 off hand. The original version of the Bourne shell which no one is compatible with anymore, the "original + BSD'isms" that we have now, or the "sysv'ish" version which is favored by sun. There is also the sysv'ish verion favored by AT&T, but that one is not used very extensively any more. > Posix compatibility has nearly nothing at > all to do with that, and bash is an extremely poor choice for that. > > Posix compatibility in this case is a buzzword only, and not a goal to > be considered as good. I thought that the whole point of posix was to provide standards that all platforms could use to avoid the exact miasma I described above? Also, as I mentioned previously the general trend that I've been able to identify is towards a posix sh implementation. However as all such things these kinds of trends move slowly, and tend to wander a bit before they settle in. > General sh compatibility is the only touchstone > here. I submit that there is no such thing currently, if there ever was. Which is why I suggest posix compliance as a goal, rather than trying to chase some subjective (and essentially fictionalized) "general sh compatibility." > Pdksh happens to hold a position close (but not, as Tor Egge > pointed out, completely) sh compatible, so it could be at least > considered as a candidate. Bash, unfortunately, isn't in that league. Why not? What specifically does Bash do or not do that makes it incompatible with your idea of sh? And remember, my proposal was to use Bash in posix mode, AKA Bash called as sh. Finally, this is one of those holy wars that I really wasn't interested in touching off, namely the "My shell is better than your shell" bit. I'm sure that all of you pdksh people are happy with your shell, and more power to you. But if we're going to seriously consider replacing sh we need hard data to work with, not generalizations. -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 15:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00245 for freebsd-current-outgoing; Sun, 25 Oct 1998 15:54:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00239 for ; Sun, 25 Oct 1998 15:54:31 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id PAA03006; Sun, 25 Oct 1998 15:53:59 -0800 (PST) Message-ID: <19981025155359.E21744@Alameda.net> Date: Sun, 25 Oct 1998 15:53:59 -0800 From: Ulf Zimmermann To: current@FreeBSD.ORG Subject: Again, questions, questions Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, it seems I am now able to read and write to the Mylex system drive. it is still slow because the kernel is giving me a single block request. So how can I tell the kernel I can do more then 1 at a time ? And how can I tell the kernel the size of a drive ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 16:10:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01732 for freebsd-current-outgoing; Sun, 25 Oct 1998 16:10:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01727 for ; Sun, 25 Oct 1998 16:10:25 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA08950; Sun, 25 Oct 1998 17:09:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810260009.RAA08950@panzer.plutotech.com> Subject: Re: Again, questions, questions In-Reply-To: <19981025155359.E21744@Alameda.net> from Ulf Zimmermann at "Oct 25, 98 03:53:59 pm" To: ulf@Alameda.net Date: Sun, 25 Oct 1998 17:09:47 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote... > Ok, it seems I am now able to read and write to the Mylex system drive. > it is still slow because the kernel is giving me a single block request. > So how can I tell the kernel I can do more then 1 at a time ? Are you going through a block or character device? > And how can I tell the kernel the size of a drive ? I assume this is sort of a disk driver (like da(4)) and a controller driver (ahc(4), ahb(4)) rolled into one? If so, your interface to the upper-level code will have to be like a disk device. That means you'll have a size routine that is registered in your cdevsw structure. You may want to take a look at src/sys/cam/scsi/scsi_da.c for an example disk driver. It has a routine, dasize(), that returns the size of the disk. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 16:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01931 for freebsd-current-outgoing; Sun, 25 Oct 1998 16:10:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01923 for ; Sun, 25 Oct 1998 16:10:45 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id TAA27279; Sun, 25 Oct 1998 19:08:44 -0500 (EST) Date: Sun, 25 Oct 1998 19:08:44 -0500 (EST) From: Chuck Robey To: Studded cc: Brian Feldman , "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <3633B5A2.F1068A0F@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Studded wrote: > And so it begins... No, you're the one trying to turn this into "holy war". You bragged about bash, and promptly said anyone who replies to your comments at all is flaming. This isn't a shell fight, it's a hunt for sh compatibility only, so any bragging about shells is misdirected. We're not picking a standard shell here, we're picking (probably have picked, negatively) a possible ash replacement. ash? That's the sh we're using now. I am not a pdksh fan myself, but I recognize it as a superior shell than sh IF IT HAS COMPATIBILITY. I'd say that same thing about bash, except bash isn't sh compatible. I am not here championing any one shell. You've done all the "holy war" talk, please don't start that. The pdksh man page says it's compatible with sh. Tor Egge brought up some bugs, which were enought to make me rethink. The nice thing about pdksh is, statically linked, it's smaller than our sh, and it's got extra features that are neat. If it's got bugs or is incompatible, it's outta here. I am solely interested in NOT breaking sh compatibility here with FreeBSD. As far as sh goes, that's my only interest, and bash breaks that real well. Posix does too, I understand. I am not going to argue any shell's features *beyond* sh compatiblity. I've never heard of various flavors or sh, it's all the Bourne shell. If you've got any comment about THAT, I'd love to hear it, I've never heard of multiple versions of sh. Teach me. I use tcsh myself, and you aren't going to get me to ask for that one, it would be utterly ridiculous. > Finally, this is one of those holy wars that I really wasn't interested > in touching off, namely the "My shell is better than your shell" bit. > I'm sure that all of you pdksh people are happy with your shell, and > more power to you. But if we're going to seriously consider replacing sh > we need hard data to work with, not generalizations. > > -- > *** Chief Operations Officer, DALnet IRC network *** > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 16:23:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02990 for freebsd-current-outgoing; Sun, 25 Oct 1998 16:23:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02984 for ; Sun, 25 Oct 1998 16:23:51 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA04246; Sun, 25 Oct 1998 16:23:18 -0800 (PST) Message-ID: <19981025162317.F21744@Alameda.net> Date: Sun, 25 Oct 1998 16:23:17 -0800 From: Ulf Zimmermann To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG Subject: Re: Again, questions, questions Reply-To: ulf@Alameda.net References: <19981025155359.E21744@Alameda.net> <199810260009.RAA08950@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810260009.RAA08950@panzer.plutotech.com>; from Kenneth D. Merry on Sun, Oct 25, 1998 at 05:09:47PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 25, 1998 at 05:09:47PM -0700, Kenneth D. Merry wrote: > Ulf Zimmermann wrote... > > Ok, it seems I am now able to read and write to the Mylex system drive. > > it is still slow because the kernel is giving me a single block request. > > So how can I tell the kernel I can do more then 1 at a time ? > > Are you going through a block or character device? Character. > > > And how can I tell the kernel the size of a drive ? > > I assume this is sort of a disk driver (like da(4)) and a controller > driver (ahc(4), ahb(4)) rolled into one? Yes. > > If so, your interface to the upper-level code will have to be like a disk > device. That means you'll have a size routine that is registered in your > cdevsw structure. I have a size routine, but it never gets called. > > You may want to take a look at src/sys/cam/scsi/scsi_da.c for an example > disk driver. It has a routine, dasize(), that returns the size of the > disk. > > Ken > -- > Kenneth Merry > ken@plutotech.com -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 16:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03382 for freebsd-current-outgoing; Sun, 25 Oct 1998 16:29:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03376 for ; Sun, 25 Oct 1998 16:29:22 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA09070; Sun, 25 Oct 1998 17:28:45 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810260028.RAA09070@panzer.plutotech.com> Subject: Re: Again, questions, questions In-Reply-To: <19981025162317.F21744@Alameda.net> from Ulf Zimmermann at "Oct 25, 98 04:23:17 pm" To: ulf@Alameda.net Date: Sun, 25 Oct 1998 17:28:44 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote... > On Sun, Oct 25, 1998 at 05:09:47PM -0700, Kenneth D. Merry wrote: > > Ulf Zimmermann wrote... > > > Ok, it seems I am now able to read and write to the Mylex system drive. > > > it is still slow because the kernel is giving me a single block request. > > > So how can I tell the kernel I can do more then 1 at a time ? > > > > Are you going through a block or character device? > > Character. I may be off base here, but I think you need to go through a block device if you want block device semantics. > > > > > And how can I tell the kernel the size of a drive ? > > > > I assume this is sort of a disk driver (like da(4)) and a controller > > driver (ahc(4), ahb(4)) rolled into one? > > Yes. > > > > > If so, your interface to the upper-level code will have to be like a disk > > device. That means you'll have a size routine that is registered in your > > cdevsw structure. > > I have a size routine, but it never gets called. It may have something to do with going through the character instead of the block device. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:09:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07487 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:09:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.rdu (mail.rdu.bellsouth.net [205.152.32.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07482 for ; Sun, 25 Oct 1998 17:09:39 -0800 (PST) (envelope-from zaz@null.net) Received: from null.net (host-209-214-161-48.rdu.bellsouth.net [209.214.161.48]) by mail.rdu (8.8.8-spamdog/8.8.5) with ESMTP id UAA22270; Sun, 25 Oct 1998 20:08:59 -0500 (EST) Message-ID: <3633C8F8.EF8E14D5@null.net> Date: Sun, 25 Oct 1998 19:57:28 -0500 From: Nathan Grass Reply-To: zaz@null.net Organization: zaz.net X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey CC: current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 25 Oct 1998, Studded wrote: > > > And so it begins... > > No, you're the one trying to turn this into "holy war". You might want to go back and re-read his post. He mentioned standards and to consider the options, not "use bash!". He is obviously much more familiar with bash than the other available options that should be considered, or at least feels that bash is a good shell to consider. If you re-read it you will see he mentions that those who are to make this decision should spend a LOT of time getting to know ALL of the shells out there before they make that choice. Stop trying to make this a matter of personal differences and preference. // zaz@null.net -=- This sig footer was last updated Oct 05 1998 -=- \\ | From: Nathan Grass http://home.dreamhaven.net/zaz/ | | Employer: ComSys http://www.comsysinc.com/ * Technical Consultant | \\ -=- Unless otherwise noted, expressed views are my opinions. -=- // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08629 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:24:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seawall.ninthwave.com (ninthwave.com [209.31.6.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08624 for ; Sun, 25 Oct 1998 17:24:26 -0800 (PST) (envelope-from jdi@ninthwave.com) Received: from ninthwave.com (kuta.ninthwave.com [10.0.0.2]) by seawall.ninthwave.com (8.9.1/8.9.1) with ESMTP id RAA09540; Sun, 25 Oct 1998 17:23:50 -0800 (PST) (envelope-from jdi@ninthwave.com) Message-ID: <3633CF2E.595D825A@ninthwave.com> Date: Sun, 25 Oct 1998 17:23:58 -0800 From: John Irwin X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Justin T. Gibbs" CC: current@FreeBSD.ORG Subject: Re: CAM and quantum disc References: <199810251942.MAA18492@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > > Fixed Direct Access SCSI2 device > > Serial Number PCB=2011300002 ; HDA=182710655437 > > 40.0MB/s transfers (20.0MHz, offset 16, 16bit), Tagged Queueing Enabled > > You should be running LYK8 on that drive. That doesn't excuse the > ncr driver panicing of course, but it may help you to avoid the problem. Thanks for the tip. I eventually found a pointer to the updated firmware in the archives, and after several frustrating hours (turns out only the newest Fireport DOS driver is capable of running qshr_ldr) was able to flash the drive to LYK8. Unfortunately I got the same crash as before, although it took quite a bit longer to occur. > Can you hook up a serial console or remote gdb and give me an exact traceback? > Either that or transpose the traceback by hand. A listing of the contents > of the ncr_ccb would be useful too. I did list the top few frames. You need the frames from before the ncr_intr() call? If you're referring to the cp->ccb at the time of the crash, it is null, which is why it crashes. :-' I'll try to get a remote gdb working and get some more info. -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09000 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:29:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08993 for ; Sun, 25 Oct 1998 17:29:18 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA27476; Sun, 25 Oct 1998 20:27:24 -0500 (EST) Date: Sun, 25 Oct 1998 20:27:24 -0500 (EST) From: Chuck Robey To: Nathan Grass cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <3633C8F8.EF8E14D5@null.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Nathan Grass wrote: > > On Sun, 25 Oct 1998, Studded wrote: > > > > > And so it begins... > > > > No, you're the one trying to turn this into "holy war". > > You might want to go back and re-read his post. He mentioned standards and to > consider the options, not "use bash!". He is obviously much more familiar with > bash than the other available options that should be considered, or at least > feels that bash is a good shell to consider. > > If you re-read it you will see he mentions that those who are to make this > decision should spend a LOT of time getting to know ALL of the shells out there > before they make that choice. > > Stop trying to make this a matter of personal differences and preference. I don't see where your comment comes from. I said that it's not about best, it's only about compatibility. He responded that bash is better. I said better doesn't matter, only compatibility. Explain to me how *I'M* making it about preference! I didn't say bash is better/worse. Reread it. He said bash was better, and I said that was not the point. He did allude to 3 different levels of sh, which I said I'd never heard of, and invited him to go on about that. I'd still like it to go in that direction, compatibility, else just drop. Better/worse hasn't anything to do with this. I am not a bash OR pdksh hacker, compatibility is my only interest. We aren't picking favorite shells, we're discussing picking a system sh. Read, then fire, please. If you (or Doug) were mistakenly after "best shell" then that's confusion about topic. I won't discuss best shell without 4 large drinks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09162 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:30:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09154 for ; Sun, 25 Oct 1998 17:30:27 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 25 Oct 1998 20:29:21 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 25 Oct 1998 17:29:20 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 25 Oct 1998 20:29:19 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: zaz@null.net cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Nathan Grass's (zaz@null.net) message dated Sun, 25 Oct 1998 19:57:28. <3633C8F8.EF8E14D5@null.net> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Oct 1998 20:29:19 -0500 Message-ID: <7577.909365359@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I still want to see csh replaced with tcsh. So there. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09751 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:37:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08951 for ; Sun, 25 Oct 1998 17:28:33 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id EAA02526; (8.8.8/D) Mon, 26 Oct 1998 04:23:38 +0300 (MSK) Message-ID: <19981026042338.40761@demos.su> Date: Mon, 26 Oct 1998 04:23:38 +0300 From: "Mikhail A. Sokolov" To: freebsd-current@FreeBSD.ORG Subject: fsck inoperability/CAM? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, when doing fsck -y (since -p fails) on just rebuilt RAID-5 (due to disk loss), I come out to way strange results.. The FS is obviously broken, but I never thought it will come up that way with RAID-5, and even then, why would it break fsck? Actually, the OS is 2 days old, ELF -current with aout kernel, the device is DPT-4333-UW with 5 seagate barracuda's 19171 RAID-5. The loss of the FS is probably caused by cp -R from other disks, after which one of the discs was announced to not to be able to work by RAID, which is itself scarry, - the system sometimes freezes tight when more or less big disk activity (like, make world) starts. I've pulled these and other disks out one by one and checked, all of those seem to be ok according to multi-verifications on low level, other machines and so on. Different controllers were used as well, so, that might be software problem. One time I was lucky to find console shouting about: -- infinete wait buffer: device 0x20401 SEYQADDR = 0x9 STAT1 = 0xa da2:(ahc0:0:2:0) Bus device RESET message sent -- Unfortunately, I can't reproduce the whole messages. CAM and SMP is enabled, no softupdates. the fsck part of my message: Program terminated with signal 11, Segmentation fault. #0 0x8049b68 in iblock () (gdb) where #0 0x8049b68 in iblock () #1 0x804980e in ckinode () #2 0x804a301 in clri () #3 0x804cc2d in pass4 () #4 0x804ac7b in checkfilesys () #5 0x804a9e1 in main () #6 0x80480c9 in _start () UNKNOWN FILE TYPE I=367275 CLEAR? yes 137699129 BAD I=367276 571373860 BAD I=367276 -618920435 BAD I=367276 EXCESSIVE BAD BLKS I=367276 CONTINUE? yes INCORRECT BLOCK COUNT I=367276 (-659171574 should be 80) CORRECT? yes UNKNOWN FILE TYPE I=367277 CLEAR? yes 56583624 BAD I=367278 -2131332271 BAD I=367278 -303071672 BAD I=367278 -1759035936 BAD I=367300 CONTINUE? yes CLEAR? yes UNKNOWN FILE TYPE I=367314 CLEAR? yes INCORRECT BLOCK COUNT I=367334 (582170220 should be 80) CORRECT? yes HOLD BAD BLOCK? yes UNKNOWN FILE TYPE I=367335 CLEAR? yes UNKNOWN FILE TYPE I=367336 CLEAR? yes PARTIALLY ALLOCATED INODE I=367337 CLEAR? yes .... DUP/BAD I=250882 OWNER=ms MODE=100644 SIZE=1359981 MTIME=Apr 1 00:00 1997 FILE=/local/vh/ftp.demos.net/pub/ripe/dbase/others/radb.db.gz ... nice mtime: BAD/DUP FILE I=366762 OWNER=620986308 MODE=14133 SIZE=15034536333323123082 MTIME=Jan 20 23:14 1904 CLEAR? yes BAD/DUP FILE I=366766 OWNER=3356080835 MODE=142347 SIZE=6917460694118870189 MTIME=Nov 25 03:32 1956 CLEAR? yes BAD/DUP FILE I=366768 OWNER=3727934015 MODE=121546 SIZE=2981631057524013585 MTIME=Dec 4 09:39 2012 CLEAR? yes BAD/DUP FILE I=366777 OWNER=325407338 MODE=126433 SIZE=4111564472578667750 MTIME=Feb 3 13:00 1974 CLEAR? yes BAD/DUP FILE I=366779 OWNER=611695138 MODE=140257 SIZE=11195809982008702958 MTIME=Feb 13 13:51 1967 CLEAR? yes BAD/DUP FILE I=366781 OWNER=119711167 MODE=144570 SIZE=5364355988561614553 MTIME=Jan 29 09:53 2029 CLEAR? yes BAD/DUP FILE I=366783 OWNER=2012960013 MODE=15317 SIZE=7763439426879057780 MTIME=May 3 04:45 1982 CLEAR? yes BAD/DUP FILE I=366791 OWNER=4058534106 MODE=103417 SIZE=15639337409666208743 MTIME=Mar 6 19:23 1965 CLEAR? yes BAD/DUP FILE I=366806 OWNER=4235278789 MODE=12543 SIZE=5585102475081859373 MTIME=Sep 9 13:56 1917 CLEAR? yes BAD/DUP FILE I=366807 OWNER=2295127275 MODE=126642 BAD/DUP FILE I=366969 OWNER=359404662 MODE=142653 SIZE=5489296613212808044 MTIME=Oct 14 13:17 2029 CLEAR? yes Segmentation fault {skraldespand}/home/mishania# Thanks for hints, -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 17:52:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10885 for freebsd-current-outgoing; Sun, 25 Oct 1998 17:52:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10877 for ; Sun, 25 Oct 1998 17:52:14 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id SAA16326; Sun, 25 Oct 1998 18:51:37 -0700 (MST) Message-Id: <199810260151.SAA16326@pluto.plutotech.com> To: John Irwin cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: CAM and quantum disc In-reply-to: Your message of "Sun, 25 Oct 1998 17:23:58 PST." <3633CF2E.595D825A@ninthwave.com> Date: Sun, 25 Oct 1998 18:44:48 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Can you hook up a serial console or remote gdb and give me an exact >> traceback? >> Either that or transpose the traceback by hand. A listing of the contents >> of the ncr_ccb would be useful too. > >I did list the top few frames. You need the frames from before the ncr_intr() >call? I want the arguments to the functions, etc, etc. >If you're referring to the cp->ccb at the time of the crash, it is null, which >is why it crashes. :-' I'm talking about the contents of cp, which is a pointer to an NCR CCB. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 18:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11584 for freebsd-current-outgoing; Sun, 25 Oct 1998 18:06:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11491 for ; Sun, 25 Oct 1998 18:05:35 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id UAA02955; Sun, 25 Oct 1998 20:43:46 -0500 (EST) Date: Sun, 25 Oct 1998 20:43:46 -0500 (EST) To: Dan Swartzendruber cc: Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-Reply-To: <3.0.5.32.19981024165102.0095ed30@mail.kersur.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Dan Swartzendruber wrote: > certainly no X apps/libraries. Emacs is handy to have to edit configuration > files and such when one telnets to the machine to make a change. I agree... have you, perhaps, tried uemacs? Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 18:36:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13771 for freebsd-current-outgoing; Sun, 25 Oct 1998 18:36:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13766 for ; Sun, 25 Oct 1998 18:36:30 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id UAA00207; Sun, 25 Oct 1998 20:30:18 -0500 (EST) Date: Sun, 25 Oct 1998 20:30:17 -0500 (EST) To: "Stephen J. Roznowski" cc: current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-Reply-To: <199810241850.OAA11330@istari.home.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Stephen J. Roznowski wrote: > 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP > install (via a cable modem). I deleted all of the other network > devices -- the card was recognized, but the install hung during > the "adding route" step. FWIW, while installing 3.0-REL here on a number of systems with various 3Com cards, I've noticed the "'adding route' step" takes a lot longer than it used to... maybe it's just a coincidence... but it's a coincidence that's happened 5-6 times so far. :P > ld.so failed: Can't find shared library "libXt.so.6.0" Not my specialty, but is this libary actually on your system (find)? If so, is it in a valid directory (rc.conf)? Perhaps you can find it and either move it to a valid directory, symlink it or ldconfig -m it. Best of luck, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 18:41:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14175 for freebsd-current-outgoing; Sun, 25 Oct 1998 18:41:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14167 for ; Sun, 25 Oct 1998 18:41:31 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA27681; Sun, 25 Oct 1998 21:40:07 -0500 (EST) Date: Sun, 25 Oct 1998 21:40:07 -0500 (EST) From: Chuck Robey To: Harlan Stenn cc: zaz@null.net, current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <7577.909365359@brown.pfcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Harlan Stenn wrote: > I still want to see csh replaced with tcsh. > > So there. Ha! After all the controversy, I'm sorry I answered the first thread, but I *liked* that above! > > H > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 19:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17029 for freebsd-current-outgoing; Sun, 25 Oct 1998 19:14:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17024 for ; Sun, 25 Oct 1998 19:14:27 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with SMTP id TAA00417 for ; Sun, 25 Oct 1998 19:13:52 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Sun, 25 Oct 1998 19:13:52 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998 mike@seidata.com wrote: > On Sat, 24 Oct 1998, Stephen J. Roznowski wrote: > > > 1) I have an "Intel EtherExpress Pro/10+" and was trying to do an FTP > > install (via a cable modem). I deleted all of the other network > > devices -- the card was recognized, but the install hung during > > the "adding route" step. > > FWIW, while installing 3.0-REL here on a number of systems with > various 3Com cards, I've noticed the "'adding route' step" takes a lot > longer than it used to... maybe it's just a coincidence... but it's > a coincidence that's happened 5-6 times so far. :P Someone I was helping install 3.0 reported that this step required rediculous amounts of time (I think it was ~5 minutes when I was watching), but in his experience, this happened only on the Berkeley reshall network. He had a 3C9xx card, IIRC. -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 21:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28208 for freebsd-current-outgoing; Sun, 25 Oct 1998 21:01:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28201 for ; Sun, 25 Oct 1998 21:01:07 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id XAA03834; Sun, 25 Oct 1998 23:00:18 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id WAA03749; Sun, 25 Oct 1998 22:59:49 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Sun, 25 Oct 1998 22:59:48 -0600 (CST) From: Jay Nelson To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to add a little more heat than light -- pdksh seems to be as close to the "standard Bourne shell" as our current sh (or any other Bourne/Korn/POSIX shell, for that matter.) I like the file completion for interactive use, but I still write scripts to the lowest common denominator because I've burned myself too many times. I have had some difficulty with functions, pdksh seems to differ in the "name ()" syntax and the "function name" syntax doesn't necessarily behave the same as other Korn shell implementations. Of course, I rarely use functions or Korn shell peculiarities, so you can write that off as pilot error. Other than that, I've not seen any incompatibilities with our current Bourne shell scripts. -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 21:39:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01962 for freebsd-current-outgoing; Sun, 25 Oct 1998 21:39:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01957 for ; Sun, 25 Oct 1998 21:39:30 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id AAA16381; Mon, 26 Oct 1998 00:38:52 -0500 (EST) Date: Mon, 26 Oct 1998 00:38:52 -0500 (EST) From: Brian Feldman To: Jay Nelson cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it certainly is! All of Tor's points were valid, but not too relevant, as he was talking about a few bugs in the Korn _superset_ of pdksh, not the standard Bourne part. By and far, pdksh supports more Korn and Bourne scripts than any other shell I've used, which is of course THE advantage we want. May I also add, that there's a release that should be due any day now: -rw-r--r-- 1 root wheel 445226 Oct 29 1996 pdksh-5.2.12.tar.gz -rw-r--r-- 1 root wheel 458840 Oct 27 1997 pdksh-5.2.13.tar.gz ? If it doesn't show up, I'll send e-mail to one of the developers to put out a release *grin*. I know it's actively developed. Cheers, Brian Feldman On Sun, 25 Oct 1998, Jay Nelson wrote: > Just to add a little more heat than light -- pdksh seems to be as > close to the "standard Bourne shell" as our current sh (or any other > Bourne/Korn/POSIX shell, for that matter.) I like the file completion > for interactive use, but I still write scripts to the lowest common > denominator because I've burned myself too many times. > > I have had some difficulty with functions, pdksh seems to differ in > the "name ()" syntax and the "function name" syntax doesn't > necessarily behave the same as other Korn shell implementations. > Of course, I rarely use functions or Korn shell peculiarities, so you > can write that off as pilot error. Other than that, I've not seen any > incompatibilities with our current Bourne shell scripts. > > -- Jay > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 21:41:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02242 for freebsd-current-outgoing; Sun, 25 Oct 1998 21:41:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02236 for ; Sun, 25 Oct 1998 21:41:21 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id VAA02085; Sun, 25 Oct 1998 21:40:43 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36340B59.DC0FEEBF@gorean.org> Date: Sun, 25 Oct 1998 21:40:41 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey CC: current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: [some snipping] > On Sun, 25 Oct 1998, Studded wrote: > > > And so it begins... > > No, you're the one trying to turn this into "holy war". I've specifically stated several times that I'd like to avoid that. My comment was meant to be ironic, given that whether anyone wants it to be a battle or not it's still an ugly can of worms. > You bragged about bash, and promptly said anyone who replies to your comments at all > is flaming. I said nothing of the kind. I stated what I hoped were objective criteria that make bash a better choice as a replacement for our sh and asked you to state objective criteria for using pdksh. > We're not picking a standard shell here, Actually if we use Bash in posix mode as sh having it available as a standard shell will be a fine bonus. :) > we're picking (probably have picked, negatively) I don't know what this means. > a possible ash replacement. > > ash? That's the sh we're using now. Kind of. We have a lot of FreeBSD specific extensions in our sh. > The pdksh man page says it's compatible with sh. Tor Egge brought up > some bugs, which were enought to make me rethink. The nice thing about > pdksh is, statically linked, it's smaller than our sh, and it's got > extra features that are neat. If it's got bugs or is incompatible, it's > outta here. > > I am solely interested in NOT breaking sh compatibility here with > FreeBSD. As far as sh goes, that's my only interest, and bash breaks > that real well. Posix does too, I understand. You still haven't defined which version of sh you want to have compatibility with, or why specifically Bash isn't compatible with it. We can't continue this conversation if you're not willing to give some sort of objective criteria to base it on. > I am not going to argue > any shell's features *beyond* sh compatiblity. I've never heard of > various flavors or sh, it's all the Bourne shell. If you've got any > comment about THAT, I'd love to hear it, I've never heard of multiple > versions of sh. Teach me. As I said previously, spend a month reading comp.unix.shell and then talk to us again. :) You could learn a lot from the FAQ's in that group, and of course there is the PR database and the mailing list archives. Try to believe me when I say that this isn't intended as an insult, but if you're not familiar with the various incarnations of the Bourne shell then your arguing about whether one shell or another is compatible or not isn't very valuable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 21:59:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03955 for freebsd-current-outgoing; Sun, 25 Oct 1998 21:59:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chickenbean.ais-gwd.com (chickenbean.com [205.160.97.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03574; Sun, 25 Oct 1998 21:57:41 -0800 (PST) (envelope-from charlespeters@chickenbean.com) Received: from ci1000971-d.sptnbrg1.sc.home.com (ci1000971-d.sptnbrg1.sc.home.com [24.4.115.200]) by chickenbean.ais-gwd.com (8.8.8/8.8.8) with SMTP id BAA02260; Mon, 26 Oct 1998 01:09:12 -0500 (EST) (envelope-from charlespeters@chickenbean.com) Reply-To: From: "Charles A. Peters" To: , , , , , , , , , , , , , , , , Date: Mon, 26 Oct 1998 00:51:11 -0500 Message-ID: <000001be00a5$5e2d8d40$c8730418@ci1000971-d.sptnbrg1.sc.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 22:36:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07448 for freebsd-current-outgoing; Sun, 25 Oct 1998 22:36:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07434 for ; Sun, 25 Oct 1998 22:36:23 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA06254; Sun, 25 Oct 1998 22:35:30 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA21994; Sun, 25 Oct 1998 22:35:29 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA26219; Sun, 25 Oct 1998 22:35:26 -0800 (PST) From: Don Lewis Message-Id: <199810260635.WAA26219@salsa.gv.tsc.tdk.com> Date: Sun, 25 Oct 1998 22:35:26 -0800 In-Reply-To: Brian Feldman "Re: nestea v2 against freebsd 3.0-Release (fwd)" (Oct 25, 10:34am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Brian Feldman , Doug Rabson Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: Don Lewis , Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 25, 10:34am, Brian Feldman wrote: } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) } Here's _my_ patch: } insert in sys/netinet/ip_input.c:796 } if (fp->ipq_frags == NULL) /* XXX */ } goto dropfrag; } (hint: goes after the "next = 0;") This is just papering over the panic that this particular set of packets is causing. It is quite possible to trigger the bug and *not* have fp->ipq_frags be NULL. Now that I look at the code some more, I think the consequences of that are more benign that I first imagined, it should only cause an mbuf leak instead of keeping a persistent pointer to an mbuf on the free list. Of course, this means that a persistent attacker can cause you to throw away all your mbufs, even with your patch. Doesn't it seem odd to you that after executing some code to find the insertion point for a new fragment into a list of fragments, and inserting the fragment into the list that the list would be empty? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 23:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10482 for freebsd-current-outgoing; Sun, 25 Oct 1998 23:15:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10477 for ; Sun, 25 Oct 1998 23:15:23 -0800 (PST) (envelope-from btman@ugcs.caltech.edu) Received: from localhost (btman@localhost) by lionking.org (8.9.1a/8.9.1) with ESMTP id XAA29408 for ; Sun, 25 Oct 1998 23:14:49 -0800 (PST) X-Authentication-Warning: lionking.org: btman owned process doing -bs Date: Sun, 25 Oct 1998 23:14:49 -0800 (PST) From: Brian Tiemann X-Sender: btman@lionking.org To: freebsd-current@FreeBSD.ORG Subject: Problem making world in gnu/usr.bin/ld/rtld Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a cvsup just a few hours ago... timon# pwd /usr/src/gnu/usr.bin/ld/rtld timon# make cc -O -pipe -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD -nostdlib -Wl,-Bshareable -Wl,-Bsymbolic -Wl,-assert -Wl,nosymbolic -o ld.so mdprologue.o rtld.o malloc.o shlib.o md.o support.o sbrk.o -lc_pic -lgcc_pic mdprologue.o(.text+0x22): undefined reference to `_rtld' mdprologue.o(.text+0x40): undefined reference to `_binder' rtld.o: In function `reloc_map': rtld.o(.text+0xe99): undefined reference to `binder_entry' *** Error code 1 Stop. None of the files in this dir seem to have been updated anytime recently. Am I missing something? Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 23:15:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10643 for freebsd-current-outgoing; Sun, 25 Oct 1998 23:15:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10638 for ; Sun, 25 Oct 1998 23:15:49 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id XAA06374; Sun, 25 Oct 1998 23:15:03 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id XAA22530; Sun, 25 Oct 1998 23:15:02 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA26243; Sun, 25 Oct 1998 23:15:00 -0800 (PST) From: Don Lewis Message-Id: <199810260715.XAA26243@salsa.gv.tsc.tdk.com> Date: Sun, 25 Oct 1998 23:15:00 -0800 In-Reply-To: Doug Rabson "Re: nestea v2 against freebsd 3.0-Release (fwd)" (Oct 25, 12:16pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Doug Rabson , Don Lewis Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 25, 12:16pm, Doug Rabson wrote: } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) } On Sun, 25 Oct 1998, Don Lewis wrote: } } > Ok, I figured out what's going on. When I compiled the nestea2.c under } > FreeBSD, it didn't run at all because rip_output() does some sanity } > checking between ip_len in the packet and the actual packet length, so } > it doesn't send the third fragment and causes sendto() to return } > EINVAL. The Linux emulation code in the kernel is kind enough to fix } > ip_len, so the sanity check passes. Even after I fixed this in } > nestea2.c, running it still didn't cause the system to panic. The } > reason for this is some differences in byte swapping in the IP header } > fields between Linux and FreeBSD that nestea2.c attempted to compensate } > for, but didn't get right. Once I fixed the byte swapping problem, I } > got the same panic you did, except for the linux emulation which I was } > not using. } > } > The panic is caused by a bug in the new ip fragment reassembly code } > that can be provoked into playing with an mbuf after it has been freed. } > Here's a patch. } > } > --- ip_input.c.orig Fri Oct 23 02:17:19 1998 } > +++ ip_input.c Sun Oct 25 01:50:20 1998 } > @@ -750,7 +750,7 @@ } > * if they are completely covered, dequeue them. } > */ } > for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; } > - p = q, q = nq) { } > + q = nq) { } > i = (ip->ip_off + ip->ip_len) - } > GETIP(q)->ip_off; } > if (i < GETIP(q)->ip_len) { } > } } I don't understand how this patch works. Won't it end up using the wrong } value for 'p' later on in the loop? Could you explain which mbuf is being } used after its freed and in what circumstances. Lets say we start off with fp->ipq_frags pointing to the list: fp->ipq_frags => frag1(offset 0) => frag2(offset 6) => NULL and we receive a new fragment with offset 0 that overlaps both frag1 and frag2. /* * Find a segment which begins after this one does. */ for (p = NULL, q = fp->ipq_frags; q; p = q, q = q->m_nextpkt) if (GETIP(q)->ip_off > ip->ip_off) break; after the above loop, we'll have: fp->ipq_frags => frag1(offset 0) => frag2(offset 6) => NULL ^ ^ | | p q Next, we remove the beginning part of the new fragment that overlaps frag1 if any (code not shown). Next, we want to throw away any fragments starting at q that are completely covered by the new fragment, and if we find a fragment in the list that partially overlaps the new fragment, we want to remove data from its beginning to remove the overlap. /* * While we overlap succeeding segments trim them or, * if they are completely covered, dequeue them. */ for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; p = q, q = nq) { i = (ip->ip_off + ip->ip_len) - GETIP(q)->ip_off; if (i < GETIP(q)->ip_len) { GETIP(q)->ip_len -= i; GETIP(q)->ip_off += i; m_adj(q, i); break; } nq = q->m_nextpkt; if (p) p->m_nextpkt = nq; else fp->ipq_frags = nq; m_freem(q); } The 'if (i < GETIP(q)->ip_len)' clause takes care of the partial overlap case. Using 'p = q, q = nq' in the for loop causes the following to be executed at the end of each loop. m_freem(q); p = q; q = nq; This means that 'p' references something on the free list. Also, we don't want to change 'p' because that is our insertion point for the new fragment. if (p == NULL) { m->m_nextpkt = fp->ipq_frags; fp->ipq_frags = m; } else { m->m_nextpkt = p->m_nextpkt; p->m_nextpkt = m; } If 'p' is pointing to an mbuf on the free list, we have just linked the new fragment in mbuf 'm' to the mbuf on the free list instead of linking it into the fragment list. No panic here, though. What we wanted though as a result was: fp->ipq_frags => frag1(offset 0) => newfrag => NULL However, if the first packet on the original fragment list had an offset greater than the incoming packet, the first loop will exit with 'p' == NULL. When we execute the second loop to free any fragments that are totally covered, we'll do: nq = q->m_nextpkt; /* NULL */ if (p) p->m_nextpkt = nq; else fp->ipq_frags = nq; m_freem(q); p = q; q = nq; and exit the loop because 'q' is now NULL. Because 'p' was initially NULL, we'll set fp->ipq_frags to NULL, and reset 'p' to the mbuf on the free list. Because 'p' is no longer NULL, we'll link the the new fragment to the mbuf on the free list again, instead of modifying fp->ipq_frags to point to it. if (p == NULL) { m->m_nextpkt = fp->ipq_frags; fp->ipq_frags = m; } else { m->m_nextpkt = p->m_nextpkt; p->m_nextpkt = m; } This leaves fp->ipq_frags set to NULL, so the following loop exits immediately, with 'p' being NULL. for (p = NULL, q = fp->ipq_frags; q; p = q, q = q->m_nextpkt) { if (GETIP(q)->ip_off != next) return (0); next += GETIP(q)->ip_len; } And when we execute the following, we dereference a NULL pointer. /* Make sure the last packet didn't have the IP_MF flag */ if (p->m_flags & M_FRAG) return (0); BOOM! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 25 23:59:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14121 for freebsd-current-outgoing; Sun, 25 Oct 1998 23:59:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p66.tfs.net [139.146.210.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14116 for ; Sun, 25 Oct 1998 23:59:22 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id BAA13325; Mon, 26 Oct 1998 01:58:16 -0600 (CST) From: Jim Bryant Message-Id: <199810260758.BAA13325@unix.tfs.net> Subject: Re: sh and ~ expansion In-Reply-To: <7577.909365359@brown.pfcs.com> from Harlan Stenn at "Oct 25, 98 08:29:19 pm" To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Mon, 26 Oct 1998 01:58:15 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Question: What do you call a Republican on Viagra? X-Answer: A Democrat, of course! X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > I still want to see csh replaced with tcsh. > > So there. It would be nice, but I doubt that it will happen, as there are certain minor incompatabilities that exist between the two that are well documented. I'd rather see tcsh distributed as ONE of the "standard" shells though. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 00:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17874 for freebsd-current-outgoing; Mon, 26 Oct 1998 00:42:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17863 for ; Mon, 26 Oct 1998 00:42:40 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA18335; Mon, 26 Oct 1998 08:43:22 GMT Date: Mon, 26 Oct 1998 08:43:22 +0000 (GMT) From: Doug Rabson To: Don Lewis cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: <199810260715.XAA26243@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Don Lewis wrote: > Lets say we start off with fp->ipq_frags pointing to the list: > > fp->ipq_frags => frag1(offset 0) => frag2(offset 6) => NULL > > and we receive a new fragment with offset 0 that overlaps both > frag1 and frag2. > > /* > * Find a segment which begins after this one does. > */ > for (p = NULL, q = fp->ipq_frags; q; p = q, q = q->m_nextpkt) > if (GETIP(q)->ip_off > ip->ip_off) > break; > > after the above loop, we'll have: > > fp->ipq_frags => frag1(offset 0) => frag2(offset 6) => NULL > ^ ^ > | | > p q > > Next, we remove the beginning part of the new fragment that overlaps frag1 if > any (code not shown). > > Next, we want to throw away any fragments starting at q that are completely > covered by the new fragment, and if we find a fragment in the list that > partially overlaps the new fragment, we want to remove data from its beginning > to remove the overlap. > > [...] > > The 'if (i < GETIP(q)->ip_len)' clause takes care of the partial overlap > case. > > Using 'p = q, q = nq' in the for loop causes the following to be executed > at the end of each loop. > > m_freem(q); > p = q; > q = nq; > > This means that 'p' references something on the free list. Also, we > don't want to change 'p' because that is our insertion point for the > new fragment. Thanks for the explanation. Would you like to commit the patch or shall I? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 00:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17958 for freebsd-current-outgoing; Mon, 26 Oct 1998 00:44:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17952 for ; Mon, 26 Oct 1998 00:43:57 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA06923; Mon, 26 Oct 1998 00:43:11 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA23777; Mon, 26 Oct 1998 00:43:10 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA26326; Mon, 26 Oct 1998 00:43:08 -0800 (PST) From: Don Lewis Message-Id: <199810260843.AAA26326@salsa.gv.tsc.tdk.com> Date: Mon, 26 Oct 1998 00:43:08 -0800 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Don Lewis , Doug Rabson Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a similar patch that also does some rearrangement so that it can optimize out some conditional code. I think it's also a bit easier to understand. I've only lightly tested this patch. --- ip_input.c.orig Fri Oct 23 02:17:19 1998 +++ ip_input.c Mon Oct 26 00:34:42 1998 @@ -711,13 +711,13 @@ fp->ipq_id = ip->ip_id; fp->ipq_src = ip->ip_src; fp->ipq_dst = ip->ip_dst; - fp->ipq_frags = 0; + fp->ipq_frags = m; + m->m_nextpkt = NULL; #ifdef IPDIVERT fp->ipq_divert = 0; fp->ipq_div_cookie = 0; #endif - q = 0; - goto insert; + goto inserted; } #define GETIP(m) ((struct ip*)((m)->m_pkthdr.header)) @@ -732,7 +732,8 @@ /* * If there is a preceding segment, it may provide some of * our data already. If so, drop the data from the incoming - * segment. If it provides all of our data, drop us. + * segment. If it provides all of our data, drop us, otherwise + * stick new segment in the proper place. */ if (p) { i = GETIP(p)->ip_off + GETIP(p)->ip_len - ip->ip_off; @@ -743,6 +744,11 @@ ip->ip_off += i; ip->ip_len -= i; } + m->m_nextpkt = p->m_nextpkt; + p->m_nextpkt = m; + } else { + m->m_nextpkt = fp->ipq_frags; + fp->ipq_frags = m; } /* @@ -750,7 +756,7 @@ * if they are completely covered, dequeue them. */ for (; q != NULL && ip->ip_off + ip->ip_len > GETIP(q)->ip_off; - p = q, q = nq) { + q = nq) { i = (ip->ip_off + ip->ip_len) - GETIP(q)->ip_off; if (i < GETIP(q)->ip_len) { @@ -760,14 +766,11 @@ break; } nq = q->m_nextpkt; - if (p) - p->m_nextpkt = nq; - else - fp->ipq_frags = nq; + m->m_nextpkt = nq; m_freem(q); } -insert: +inserted: #ifdef IPDIVERT /* @@ -782,16 +785,8 @@ #endif /* - * Stick new segment in its place; - * check for complete reassembly. + * Check for complete reassembly. */ - if (p == NULL) { - m->m_nextpkt = fp->ipq_frags; - fp->ipq_frags = m; - } else { - m->m_nextpkt = p->m_nextpkt; - p->m_nextpkt = m; - } next = 0; for (p = NULL, q = fp->ipq_frags; q; p = q, q = q->m_nextpkt) { if (GETIP(q)->ip_off != next) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 00:48:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18321 for freebsd-current-outgoing; Mon, 26 Oct 1998 00:48:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18312 for ; Mon, 26 Oct 1998 00:48:08 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA06956; Mon, 26 Oct 1998 00:47:23 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA23796; Mon, 26 Oct 1998 00:47:22 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA26341; Mon, 26 Oct 1998 00:47:21 -0800 (PST) From: Don Lewis Message-Id: <199810260847.AAA26341@salsa.gv.tsc.tdk.com> Date: Mon, 26 Oct 1998 00:47:21 -0800 In-Reply-To: Doug Rabson "Re: nestea v2 against freebsd 3.0-Release (fwd)" (Oct 26, 8:43am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Doug Rabson , Don Lewis Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) Cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 26, 8:43am, Doug Rabson wrote: } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) } Thanks for the explanation. Would you like to commit the patch or shall } I? Well, since I don't have commit privs ... You might also consider the followon patch that I just sent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 00:58:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19206 for freebsd-current-outgoing; Mon, 26 Oct 1998 00:58:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19199 for ; Mon, 26 Oct 1998 00:58:36 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA08620 for ; Mon, 26 Oct 1998 09:57:58 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA11260 for ; Mon, 26 Oct 1998 09:57:58 +0100 (MET) Received: (qmail 3631 invoked by uid 666); 26 Oct 1998 08:58:18 -0000 Date: Mon, 26 Oct 1998 09:58:18 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: /boot/loader hangs after arrow/function key pressed at prompt Message-ID: <19981026095818.A3590@hal.mpn.cp.philips.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This appears to happen with yesterday's loader. Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 01:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19749 for freebsd-current-outgoing; Mon, 26 Oct 1998 01:05:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles239.castles.com [208.214.165.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19744 for ; Mon, 26 Oct 1998 01:05:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA04652; Mon, 26 Oct 1998 01:04:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810260904.BAA04652@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jos Backus cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-reply-to: Your message of "Mon, 26 Oct 1998 09:58:18 +0100." <19981026095818.A3590@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 01:04:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This appears to happen with yesterday's loader. I just noticed this one; it's on the notes I'll be working from tomorrow. Thanks for the corroboration; I have only noticed it on one system so far (Toshiba laptop). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 01:16:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20752 for freebsd-current-outgoing; Mon, 26 Oct 1998 01:16:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20741 for ; Mon, 26 Oct 1998 01:16:15 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA17750; Mon, 26 Oct 1998 10:20:12 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 26 Oct 1998 10:20:12 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Jos Backus , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: <199810260904.BAA04652@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Mike Smith wrote: > > This appears to happen with yesterday's loader. > > I just noticed this one; it's on the notes I'll be working from > tomorrow. Thanks for the corroboration; I have only noticed it on one > system so far (Toshiba laptop). I noticed this one too, on my desktop (Shuttle HOT-553 MB). I also encountered another problem: /boot/loader sometimes ignores all keypresses (I wasn't able even to break the countdown), but I'm not sure in what circumstances it happens - it sometimes happens, when I type something on the boot: prompt, then delete it. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 01:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22102 for freebsd-current-outgoing; Mon, 26 Oct 1998 01:32:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22055 for ; Mon, 26 Oct 1998 01:32:27 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id KAA23650 for current@FreeBSD.ORG; Mon, 26 Oct 1998 10:31:42 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 342091508; Mon, 26 Oct 1998 10:13:54 +0100 (CET) Date: Mon, 26 Oct 1998 10:13:54 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: sh and ~ expansion: ksh testing Message-ID: <19981026101354.A14251@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Brian Feldman on Sun, Oct 25, 1998 at 10:48:22AM -0500 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4731 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Feldman: > -r-xr-xr-x 1 root wheel 258328 Oct 19 01:37 /bin/csh > -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh > -r-xr-xr-x 1 root wheel 321120 Oct 19 01:37 /bin/sh.old Just to be sure... Please verify that you /bin/ksh is statically linked and not dynamically. The original "/bin/sh" is static. What does surprise me is that our csh is now smaller than sh... text data bss dec hex filename 302081 10088 36588 348757 55255 /bin/sh 241557 8224 39116 288897 46881 /bin/csh 422919 16308 179296 618523 9701b /bin/tcsh 477165 27556 57340 562061 8938d /bin/zsh -r-xr-xr-x 1 root wheel 258280 Oct 15 21:04 /bin/csh* -r-xr-xr-x 1 root wheel 321120 Oct 15 21:04 /bin/sh* -rwxr-xr-x 1 root wheel 509414 Oct 2 22:23 /bin/tcsh* -rwxr-xr-x 1 root staff 514344 Sep 30 23:59 /bin/zsh* -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 01:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23292 for freebsd-current-outgoing; Mon, 26 Oct 1998 01:44:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-9-dbn.dial-up.net [196.34.155.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23254 for ; Mon, 26 Oct 1998 01:43:55 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA26041; Mon, 26 Oct 1998 11:41:05 +0200 (SAT) From: Robert Nordier Message-Id: <199810260941.LAA26041@ceia.nordier.com> Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: from Andrzej Bialecki at "Oct 26, 98 10:20:12 am" To: abial@nask.pl (Andrzej Bialecki) Date: Mon, 26 Oct 1998 11:41:03 +0200 (SAT) Cc: mike@smith.net.au, Jos.Backus@nl.origin-it.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Mon, 26 Oct 1998, Mike Smith wrote: > > > > This appears to happen with yesterday's loader. > > > > I just noticed this one; it's on the notes I'll be working from > > tomorrow. Thanks for the corroboration; I have only noticed it on one > > system so far (Toshiba laptop). > > I noticed this one too, on my desktop (Shuttle HOT-553 MB). > > I also encountered another problem: /boot/loader sometimes ignores > all keypresses (I wasn't able even to break the countdown), but I'm not > sure in what circumstances it happens - it sometimes happens, when I type > something on the boot: prompt, then delete it. If this happened with the new boot1/boot2, can you confirm this is still a problem? Your original report of this was some time ago, and various changes have been made, including to the input routine. Thanks. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 04:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05779 for freebsd-current-outgoing; Mon, 26 Oct 1998 04:33:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from world.virtual-earth.de (world.virtual-earth.de [194.231.209.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05764 for ; Mon, 26 Oct 1998 04:33:06 -0800 (PST) (envelope-from mathiasp@mp.virtual-earth.de) Received: from mp.virtual-earth.de (mp.virtual-earth.de [194.231.209.35]) by world.virtual-earth.de (8.9.1/8.8.5) with ESMTP id NAA27436 for ; Mon, 26 Oct 1998 13:32:24 +0100 (MET) Received: from mp.virtual-earth.de (localhost.virtual-earth.de [127.0.0.1]) by mp.virtual-earth.de (8.9.1/8.8.5) with ESMTP id NAA00406 for ; Mon, 26 Oct 1998 13:32:21 +0100 (MET) Message-Id: <199810261232.NAA00406@mp.virtual-earth.de> Date: Mon, 26 Oct 1998 13:32:14 +0100 (MET) From: Mathias Picker Subject: 3.0 release tags? (going from current to -stable) To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: MULTIPART/signed; micalg=pgp-md5; protocol="application/pgp-signature"; BOUNDARY="0-1804289383-909405143=:315" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-909405143=:315 Content-Type: TEXT/plain; CHARSET=US-ASCII I've been tracking current to make the transition from 2.2-stable to 3.0. Now I wan't to go back to -stable (3.0). Trying RELENG_3_0 (guesswork) in my cvsup configuration did not work. I can see that 3.0 is not yet really -stable :-), so maybe I need to stay with -current to track 3.0?? Thanks, Mathias -- Mathias Picker Consultant Information Architecture Mathias.Picker@virtual-earth.de +49 172 / 89 19 381 --0-1804289383-909405143=:315 Content-Type: APPLICATION/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBNjRr06zvoSjVwVSdAQHAiQP/SJ02Xf4nWTPoY2WXtxCy5d9KnVv6dWjW GM9T75SBIAVmK7L4qeJSKwqrunij57jtPtoraJtRcsjy3+X6TWsvnTZRg6aFOec2 NvVDG3vsJtWFSnAxY1vUv9pkrnEe6TppA25F/nIFRIqDE+/kplRBCO3ubPac9Feg e2kFcBxJ/2g= =34ys -----END PGP MESSAGE----- --0-1804289383-909405143=:315-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 04:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06729 for freebsd-current-outgoing; Mon, 26 Oct 1998 04:47:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06724 for ; Mon, 26 Oct 1998 04:47:55 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA20685; Mon, 26 Oct 1998 07:47:12 -0500 (EST) Date: Mon, 26 Oct 1998 07:47:12 -0500 (EST) From: Brian Feldman To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion: ksh testing In-Reply-To: <19981026101354.A14251@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course it is! Sheesh, think I'm trying to pepper results? :) {"/home/green"}$ ls -l /bin/ksh -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh {"/home/green"}$ file /bin/ksh /bin/ksh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped Cheers, Brian Feldman On Mon, 26 Oct 1998, Ollivier Robert wrote: > According to Brian Feldman: > > -r-xr-xr-x 1 root wheel 258328 Oct 19 01:37 /bin/csh > > -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh > > -r-xr-xr-x 1 root wheel 321120 Oct 19 01:37 /bin/sh.old > > Just to be sure... Please verify that you /bin/ksh is statically linked and > not dynamically. The original "/bin/sh" is static. What does surprise me is > that our csh is now smaller than sh... > > text data bss dec hex filename > 302081 10088 36588 348757 55255 /bin/sh > 241557 8224 39116 288897 46881 /bin/csh > 422919 16308 179296 618523 9701b /bin/tcsh > 477165 27556 57340 562061 8938d /bin/zsh > > -r-xr-xr-x 1 root wheel 258280 Oct 15 21:04 /bin/csh* > -r-xr-xr-x 1 root wheel 321120 Oct 15 21:04 /bin/sh* > -rwxr-xr-x 1 root wheel 509414 Oct 2 22:23 /bin/tcsh* > -rwxr-xr-x 1 root staff 514344 Sep 30 23:59 /bin/zsh* > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 05:26:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09461 for freebsd-current-outgoing; Mon, 26 Oct 1998 05:26:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09450 for ; Mon, 26 Oct 1998 05:26:06 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (root@caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id OAA00260 for ; Mon, 26 Oct 1998 14:25:30 +0100 (MET) Received: from via.ecp.fr (dae.via.ecp.fr [138.195.136.50]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id OAA11181 for ; Mon, 26 Oct 1998 14:25:29 +0100 (MET) Message-ID: <36347B36.1D70050B@via.ecp.fr> Date: Mon, 26 Oct 1998 14:37:58 +0100 From: X-dae X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: fatal trap 12: page fault while in kernel mode Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i've cvsupped to 3.0 RELEASE two days ago, and made aout-to-elf (was an august snap). i've compiled a kernel with my old options and it works great. then i've compiled one with options "VM86" and the system crashes just after my login: (hand copy) fatal trap 12: page fault while in kernel mode fault virtual address = 0xeffd3004 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01bfe5b stack pointer = 0x10:0xf4ba5d34 code segment = base 0x0, limit 0xfffff, type 0x16 = DLP 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL=0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic:page fault syncing disks .... and stays there forever, hard reboot required i've got a intel 166MMX with 96 megs sdram , a matrox mystique 4M and a awe 64 pnp. could you guys help me with that one ? -- Krapf Andres, Engineering student at the Ecole Centrale Paris IRCnet: X-dae -- dae@via.ecp.fr -=- FreeBSD:The Power To Serve -=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 06:12:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14667 for freebsd-current-outgoing; Mon, 26 Oct 1998 06:12:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14662 for ; Mon, 26 Oct 1998 06:12:19 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (root@caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id PAA01492 for ; Mon, 26 Oct 1998 15:11:43 +0100 (MET) Received: from via.ecp.fr (dae.via.ecp.fr [138.195.136.50]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id PAA13125 for ; Mon, 26 Oct 1998 15:11:42 +0100 (MET) Message-ID: <3634860C.B3F83EAC@via.ecp.fr> Date: Mon, 26 Oct 1998 15:24:12 +0100 From: X-dae X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: fatal trap 12: page fault while in kernel mode References: <36347B36.1D70050B@via.ecp.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I browsed through the archives and saw that a few things were missing in my last post: > instruction pointer = 0x8:0xf01bfe5b 26/10 15:05 ~% /usr/libexec/aout/nm /kernel.old | grep f01bf f01bf2c4 t __pmap_allocpte f01bf628 t _get_pv_entry f01bf384 t _pmap_allocpte f01bf6c0 T _pmap_collect f01bf5f4 T _pmap_destroy f01bfdb4 T _pmap_enter f01bf478 T _pmap_growkernel f01bf834 t _pmap_insert_entry f01bf0c0 T _pmap_pinit f01bf040 T _pmap_pinit0 f01bfbd4 T _pmap_protect f01bf618 T _pmap_reference f01bf3dc T _pmap_release f01bf200 t _pmap_release_free_page f01bf980 T _pmap_remove f01bfa8c t _pmap_remove_all f01bf744 t _pmap_remove_entry f01bf93c t _pmap_remove_page f01bf8b4 t _pmap_remove_pte does that help ? -- Krapf Andres, Engineering student at the Ecole Centrale Paris IRCnet: X-dae -- dae@via.ecp.fr -=- FreeBSD:The Power To Serve -=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 06:27:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15978 for freebsd-current-outgoing; Mon, 26 Oct 1998 06:27:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles352.castles.com [208.214.167.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15958 for ; Mon, 26 Oct 1998 06:27:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id GAA06190; Mon, 26 Oct 1998 06:26:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810261426.GAA06190@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: X-dae cc: current@FreeBSD.ORG Subject: Re: fatal trap 12: page fault while in kernel mode In-reply-to: Your message of "Mon, 26 Oct 1998 15:24:12 +0100." <3634860C.B3F83EAC@via.ecp.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 06:26:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I browsed through the archives and saw that a few things were missing in > my last post: > > > instruction pointer = 0x8:0xf01bfe5b > > 26/10 15:05 ~% /usr/libexec/aout/nm /kernel.old | grep f01bf > f01bf2c4 t __pmap_allocpte > f01bf628 t _get_pv_entry > f01bf384 t _pmap_allocpte > f01bf6c0 T _pmap_collect > f01bf5f4 T _pmap_destroy > f01bfdb4 T _pmap_enter > f01bf478 T _pmap_growkernel > f01bf834 t _pmap_insert_entry > f01bf0c0 T _pmap_pinit > f01bf040 T _pmap_pinit0 > f01bfbd4 T _pmap_protect > f01bf618 T _pmap_reference > f01bf3dc T _pmap_release > f01bf200 t _pmap_release_free_page > f01bf980 T _pmap_remove > f01bfa8c t _pmap_remove_all > f01bf744 t _pmap_remove_entry > f01bf93c t _pmap_remove_page > f01bf8b4 t _pmap_remove_pte > > does that help ? You really need to pipe this through sort for it to be useful. At any rate, it doesn't seem related to the VM86 issue. Also try updating to -current. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 06:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16773 for freebsd-current-outgoing; Mon, 26 Oct 1998 06:31:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16768 for ; Mon, 26 Oct 1998 06:31:06 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA24849; Mon, 26 Oct 1998 15:30:15 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA26023; Mon, 26 Oct 1998 15:30:14 +0100 (MET) Message-ID: <19981026153014.41345@follo.net> Date: Mon, 26 Oct 1998 15:30:14 +0100 From: Eivind Eklund To: Mathias Picker , current@FreeBSD.ORG Subject: Re: 3.0 release tags? (going from current to -stable) References: <199810261232.NAA00406@mp.virtual-earth.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810261232.NAA00406@mp.virtual-earth.de>; from Mathias Picker on Mon, Oct 26, 1998 at 01:32:14PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 01:32:14PM +0100, Mathias Picker wrote: > I've been tracking current to make the transition from 2.2-stable to > 3.0. Now I wan't to go back to -stable (3.0). Trying RELENG_3_0 > (guesswork) in my cvsup configuration did not work. > > I can see that 3.0 is not yet really -stable :-), so maybe I need to > stay with -current to track 3.0?? Yes, you need to stay with -current to track 3.0 (at the moment, at least - RELENG_3_0 will most likely be put down before the next release of 3.0). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 06:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17150 for freebsd-current-outgoing; Mon, 26 Oct 1998 06:36:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17145 for ; Mon, 26 Oct 1998 06:36:48 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id PAA28713 for ; Mon, 26 Oct 1998 15:36:03 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id PAA21177 for ; Mon, 26 Oct 1998 15:36:00 +0100 (MET) Received: (qmail 824 invoked by uid 666); 26 Oct 1998 14:36:19 -0000 Date: Mon, 26 Oct 1998 15:36:19 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt Message-ID: <19981026153619.A807@hal.mpn.cp.philips.com> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199810260941.LAA26041@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: <199810260941.LAA26041@ceia.nordier.com>; from Robert Nordier on Mon, Oct 26, 1998 at 11:41:03AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 11:41:03AM +0200, Robert Nordier wrote: > Andrzej Bialecki wrote: > > I also encountered another problem: /boot/loader sometimes ignores > > all keypresses (I wasn't able even to break the countdown), Fwiw, I saw this too after a reboot this morning, with a loader built on October 20th. If there is anything I can test to track these down, I will (but I'm not much of a BTX-hacker :-( ) Hth, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 06:37:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17325 for freebsd-current-outgoing; Mon, 26 Oct 1998 06:37:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17317 for ; Mon, 26 Oct 1998 06:37:26 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA11150; Mon, 26 Oct 1998 09:36:46 -0500 (EST) Date: Mon, 26 Oct 1998 09:36:46 -0500 (EST) Message-Id: <199810261436.JAA11150@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Re: 3.0 release tags? (going from current to -stable) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When is "-stable" going to be 3.0? Did I miss something... is it already? We have a bunch of customers that want to know when that is going to happen. Also, once 3.0 is "-stable" our corporate folks can "officially" say that we support FreeBSD. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 07:00:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19274 for freebsd-current-outgoing; Mon, 26 Oct 1998 07:00:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19260 for ; Mon, 26 Oct 1998 07:00:18 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from fenja.ifi.uio.no (2602@fenja.ifi.uio.no [129.240.65.174]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id PAA06800; Mon, 26 Oct 1998 15:59:09 +0100 (MET) Received: (from dag-erli@localhost) by fenja.ifi.uio.no ; Mon, 26 Oct 1998 15:58:59 +0100 (MET) Mime-Version: 1.0 To: Craig Johnston Cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF XFree86 in ports References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Oct 1998 15:58:59 +0100 In-Reply-To: Craig Johnston's message of "Sat, 24 Oct 1998 15:07:00 -0500 (CDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA19270 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Craig Johnston writes: > Wanted to hear from anyone who's running ELF XFree86 from the ports > collection on -current. I'm running an aout installation right now -- I'd > like to upgrade but I really don't need to hose X. I've been running it on one box almost since E-day, and am planning to upgrade my home box to ELF XFree86 tonight so I can install XKoules from /usr/ports/games/xkoules :) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 07:53:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23138 for freebsd-current-outgoing; Mon, 26 Oct 1998 07:53:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23127 for ; Mon, 26 Oct 1998 07:53:20 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA18400; Mon, 26 Oct 1998 10:52:12 -0500 (EST) (envelope-from wollman) Date: Mon, 26 Oct 1998 10:52:12 -0500 (EST) From: Garrett Wollman Message-Id: <199810261552.KAA18400@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Dan Swartzendruber , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-Reply-To: <199810242040.NAA07711@dingo.cdrom.com> References: <3.0.5.32.19981024160121.009bc430@mail.kersur.net> <199810242040.NAA07711@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > If the machine is "stripped down", then you sure don't want Emacs on it. > Try one of the lighter clones, and save yourself the worry. Nonsense. If you want Emacs, you want Emacs, not some poor imitation. This has nothing to do with whether the machine is ``stripped down'' or not. The answer to the original question is that the package is built with X support because that's what most people want. If you build your own Emacs from the port, it will automatically take notice of whether you have X installed or not and take appropriate measures. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 08:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24712 for freebsd-current-outgoing; Mon, 26 Oct 1998 08:12:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24705 for ; Mon, 26 Oct 1998 08:12:20 -0800 (PST) (envelope-from chet@nike.ins.cwru.edu) Received: (chet@localhost) by nike.ins.cwru.edu (8.8.7/CWRU-2.5-bsdi) id LAA28052; Mon, 26 Oct 1998 11:11:03 -0500 (EST) (from chet) Date: Mon, 26 Oct 1998 11:10:37 -0500 From: Chet Ramey To: Studded@gorean.org Subject: Re: sh and ~ expansion Cc: green@zone.syracuse.net, dag-erli@ifi.uio.no, current@FreeBSD.ORG, chet@po.cwru.edu Reply-To: chet@po.cwru.edu In-Reply-To: Message from Studded@gorean.org of Sun, 25 Oct 1998 13:16:35 -0800 (id <36339533.49D5D9F0@gorean.org>) Message-ID: <981026161037.AA28001.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Finally, I've gathered > from various comments that Chet (the principle maintainer for Bash) has > made that he uses FreeBSD as his main platform. :) Yes, I do. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 08:19:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25339 for freebsd-current-outgoing; Mon, 26 Oct 1998 08:19:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25334 for ; Mon, 26 Oct 1998 08:19:44 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA22829; Mon, 26 Oct 1998 11:18:49 -0500 (EST) Date: Mon, 26 Oct 1998 11:18:49 -0500 (EST) From: Brian Feldman To: Mike Smith cc: X-dae , current@FreeBSD.ORG Subject: Re: fatal trap 12: page fault while in kernel mode In-Reply-To: <199810261426.GAA06190@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Even tho it's not piped, it seems to be located in pmap_enter when you do a mental_sort()... Brian Feldman On Mon, 26 Oct 1998, Mike Smith wrote: > > I browsed through the archives and saw that a few things were missing in > > my last post: > > > > > instruction pointer = 0x8:0xf01bfe5b > > > > 26/10 15:05 ~% /usr/libexec/aout/nm /kernel.old | grep f01bf > > f01bf2c4 t __pmap_allocpte > > f01bf628 t _get_pv_entry > > f01bf384 t _pmap_allocpte > > f01bf6c0 T _pmap_collect > > f01bf5f4 T _pmap_destroy > > f01bfdb4 T _pmap_enter > > f01bf478 T _pmap_growkernel > > f01bf834 t _pmap_insert_entry > > f01bf0c0 T _pmap_pinit > > f01bf040 T _pmap_pinit0 > > f01bfbd4 T _pmap_protect > > f01bf618 T _pmap_reference > > f01bf3dc T _pmap_release > > f01bf200 t _pmap_release_free_page > > f01bf980 T _pmap_remove > > f01bfa8c t _pmap_remove_all > > f01bf744 t _pmap_remove_entry > > f01bf93c t _pmap_remove_page > > f01bf8b4 t _pmap_remove_pte > > > > does that help ? > > You really need to pipe this through sort for it to be useful. At any > rate, it doesn't seem related to the VM86 issue. Also try updating to > -current. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 08:25:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26236 for freebsd-current-outgoing; Mon, 26 Oct 1998 08:25:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26107 for ; Mon, 26 Oct 1998 08:25:27 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id RAA26914; Mon, 26 Oct 1998 17:24:45 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA26441; Mon, 26 Oct 1998 17:24:44 +0100 (MET) Message-ID: <19981026172443.50390@follo.net> Date: Mon, 26 Oct 1998 17:24:43 +0100 From: Eivind Eklund To: HighWind Software Information , current@FreeBSD.ORG Subject: Re: 3.0 release tags? (going from current to -stable) References: <199810261436.JAA11150@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810261436.JAA11150@highwind.com>; from HighWind Software Information on Mon, Oct 26, 1998 at 09:36:46AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 09:36:46AM -0500, HighWind Software Information wrote: > > When is "-stable" going to be 3.0? When 3.0 is stable enough and we do the next release. Probably somewhere between january and june; most likely january/february. > Did I miss something... is it already? No. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 08:25:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26280 for freebsd-current-outgoing; Mon, 26 Oct 1998 08:25:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26272 for ; Mon, 26 Oct 1998 08:25:52 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA05378; Mon, 26 Oct 1998 08:24:53 -0800 (PST) (envelope-from jdp) Message-Id: <199810261624.IAA05378@austin.polstra.com> To: rock@cs.uni-sb.de Subject: Re: vmstat, nfsstat broken In-Reply-To: <3632462A.A9A4503A@cs.uni-sb.de> References: <199810241942.MAA05846@dingo.cdrom.com> <3632462A.A9A4503A@cs.uni-sb.de> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Mon, 26 Oct 1998 08:24:53 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3632462A.A9A4503A@cs.uni-sb.de>, Daniel Rock wrote: > Mike Smith schrieb: > > > > > vmstat doesn't seem to like ELF kernels. With aout kernels "vmstat -i" > > > works, but with ELF ones, I get the following error message: > > > vmstat: symbol intrcnt not defined > > > After taking a short look at the code, I suspect it may be associated > > > with the now missing leading "_" in ELF symbols, but I'm not sure. > > > > It's odd that intrcnt isn't found, but eintrcnt is. If you use 'nm' on > > your kernel, is it present as 'intrcnt' or '_intrcnt'? > The problem isn't the leading "_", but: > The variables intrnames, eintrname, intrcnt, eintrcnt from the namelist > have the type N_UNDF associated, although they have the right value. If I > just ignore n_type, I get the right output even on ELF kernels: I took a quick look at this. Depending on your point of view, it's a bug in nlist(3) and/or in the relevant symbols in the kernel. The symbols come out with an object type of "none", which nlist() then decides to interpret as undefined. I think it's best to fix it in nlist(). I know how to fix it, and will try to get to it before the week is out. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 08:34:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26772 for freebsd-current-outgoing; Mon, 26 Oct 1998 08:34:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26767 for ; Mon, 26 Oct 1998 08:34:48 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA24967; Mon, 26 Oct 1998 09:33:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA21074; Mon, 26 Oct 1998 09:33:21 -0700 Date: Mon, 26 Oct 1998 09:33:21 -0700 Message-Id: <199810261633.JAA21074@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Garrett Wollman Cc: Mike Smith , Dan Swartzendruber , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: 3.0 installation problems In-Reply-To: <199810261552.KAA18400@khavrinen.lcs.mit.edu> References: <3.0.5.32.19981024160121.009bc430@mail.kersur.net> <199810242040.NAA07711@dingo.cdrom.com> <199810261552.KAA18400@khavrinen.lcs.mit.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the machine is "stripped down", then you sure don't want Emacs on it. > > Try one of the lighter clones, and save yourself the worry. > > Nonsense. If you want Emacs, you want Emacs, not some poor imitation. Actuall, uemacs is a pretty good 'clone' of emacs, and doesn't take 16MB of memory to run well. :) I remember when EMACS stood for 'Eight Megabytes And Constantly Swapping', but it now stands for 'Eighteen Megabytes And Constantly Swapping', and will soon stand for 'Eighty Megabytes And Constantly Swapping.' ( For the humor impaired, this is sarcasm. I happen to use XEmacs as my primary editor on my workstation, but I also don't even bother trying to install it on my low-end box which is a slow 486 with very little memory, where I've installed uemacs.) > This has nothing to do with whether the machine is ``stripped down'' > or not. Sure it does. Emacs doesn't a relatively *LONG* time to come up, while I can edit a file and be done with it using uemacs in about the same time I finally get emacs to get the file open and displayed on my screen. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 09:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03868 for freebsd-current-outgoing; Mon, 26 Oct 1998 09:52:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03860 for ; Mon, 26 Oct 1998 09:52:18 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA06035; Mon, 26 Oct 1998 12:51:33 -0500 (EST) Message-ID: <19981026125133.A2717@netmonger.net> Date: Mon, 26 Oct 1998 12:51:33 -0500 From: Christopher Masto To: current@FreeBSD.ORG Subject: Shells for you and shells for me References: <3633C8F8.EF8E14D5@null.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Chuck Robey on Sun, Oct 25, 1998 at 08:27:24PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just keep the damn /bin/sh we have now. Who actually uses it as their login shell? Nobody. It's there to write /bin/sh scripts, which by their very nature should be FreeBSD-specific or else extremely lowest-common-denominator. If there are bugs affecting the latter, they can be fixed. Do people really want better "sh compatability"? I don't think that's what this is about. I think the semiconscious desire is to have tab completion in single-user mode, which is not at all related to compatability for sh scripts. My only problem with the sh we have now is that weird signal-handling thing that, IIRC, got fixed and then unfixed because of side effects. The only time I run into compatability problems is when I'm installing some Linux thing that mistakenly uses a bash feature in an sh script. Personally, I use zsh, weenie that I am. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ What we'll all end up doing if Netscape doesn't play better is we will have instantiated the Microsoft Network. We'll just call it the Internet. - GEOFFREY MOORE, Marketing Guru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 10:28:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06827 for freebsd-current-outgoing; Mon, 26 Oct 1998 10:28:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06822 for ; Mon, 26 Oct 1998 10:28:53 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA01688; Mon, 26 Oct 1998 19:33:20 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 26 Oct 1998 19:33:20 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Christopher Masto cc: current@FreeBSD.ORG Subject: Re: Shells for you and shells for me In-Reply-To: <19981026125133.A2717@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Christopher Masto wrote: > Just keep the damn /bin/sh we have now. Who actually uses it as their > login shell? Nobody. It's there to write /bin/sh scripts, which by I do. I always change shell for root account from /bin/csh to /bin/sh. Also, I very often write quite complicated multi-line scripts on command line (using /bin/sh line editing and history), just to get the job done quickly. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 10:34:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07399 for freebsd-current-outgoing; Mon, 26 Oct 1998 10:34:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA07392 for ; Mon, 26 Oct 1998 10:34:11 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zXrSB-0004s4-00; Mon, 26 Oct 1998 11:33:19 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id LAA10458; Mon, 26 Oct 1998 11:33:21 -0700 (MST) Message-Id: <199810261833.LAA10458@harmony.village.org> To: mike@seidata.com Subject: Re: 3.0 installation problems Cc: Dan Swartzendruber , Mike Smith , "Stephen J. Roznowski" , current@FreeBSD.ORG, jkh@time.cdrom.com In-reply-to: Your message of "Sun, 25 Oct 1998 20:43:46 EST." References: Date: Mon, 26 Oct 1998 11:33:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message mike@seidata.com writes: : > certainly no X apps/libraries. Emacs is handy to have to edit configuration : > files and such when one telnets to the machine to make a change. : : I agree... have you, perhaps, tried uemacs? emacs can be configured to be used w/o X. When I need one of these on a machine that already has X installed, I usually cd to /usr/ports/editors/emacs do a make configure, let it finish, then cd to work/whatever and do a ./configure `./config.status` --without-x11, then cd ../.. and build. Unless the machine has < 3M of memory, emacs isn't a horrible choice for an editor. I've used emacs on machines with as little as 4M of memory from time to time. While I wouldn't want to use it all the time every day on those machines, it is better than having to recall my vi skills. uemacs is interesting, but it isn't gnu emacs. This is both good and bad :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 11:03:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09488 for freebsd-current-outgoing; Mon, 26 Oct 1998 11:03:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09483 for ; Mon, 26 Oct 1998 11:03:48 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA25965; Mon, 26 Oct 1998 12:02:14 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA21553; Mon, 26 Oct 1998 12:02:13 -0700 Date: Mon, 26 Oct 1998 12:02:13 -0700 Message-Id: <199810261902.MAA21553@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki Cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me In-Reply-To: References: <19981026125133.A2717@netmonger.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just keep the damn /bin/sh we have now. Who actually uses it as their > > login shell? Nobody. It's there to write /bin/sh scripts, which by > > I do. I always change shell for root account from /bin/csh to /bin/sh. That's what the 'toor' account is there for. The only difference between it and root is the shell. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 11:17:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10591 for freebsd-current-outgoing; Mon, 26 Oct 1998 11:17:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10584 for ; Mon, 26 Oct 1998 11:17:35 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA08159; Mon, 26 Oct 1998 12:16:57 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd008118; Mon Oct 26 12:16:52 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id MAA15070; Mon, 26 Oct 1998 12:16:50 -0700 (MST) From: Terry Lambert Message-Id: <199810261916.MAA15070@usr04.primenet.com> Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 26 Oct 1998 19:16:50 +0000 (GMT) Cc: tlambert@primenet.com, john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: <10639.909296170@time.cdrom.com> from "Jordan K. Hubbard" at Oct 24, 98 11:16:10 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Still, even if the new file must stay, it would be nice to know > > that at least it was the result of someone is steering, instead > > of being the result of people not communicating. > > "Dear Terry, we were here and we waited for you, but you didn't show up. What > happened? Signed - Jordan & Mark" > > This _was_ discussed in -current. I raised the issue of disabling > things like kerberos authentication for kerberized binaries and > setting the default password time. Discussion ensued. Code was > thrown indiscriminately around. Things evolved and Mark subsequently > committed the kerberos knob. The password knob remains to follow. Are you sure it wasn't discussed on -committers or -core instead? It's pretty obvious that the "knob" to use is the existance of the symbol in the shared library. I know this idea isn't popular, since a system with a corrupt /kernel is ever so much more likely to boot than one with a corrupt /libexec/ld.so.1. Not. As far as disabling goes -- don't you just say "rlogin -K" instead of "rlogin", etc.? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 11:22:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11024 for freebsd-current-outgoing; Mon, 26 Oct 1998 11:22:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11016 for ; Mon, 26 Oct 1998 11:22:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00466; Mon, 26 Oct 1998 11:21:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810261921.LAA00466@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-reply-to: Your message of "Mon, 26 Oct 1998 10:52:12 EST." <199810261552.KAA18400@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 11:21:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > If the machine is "stripped down", then you sure don't want Emacs on it. > > Try one of the lighter clones, and save yourself the worry. > > Nonsense. If you want Emacs, you want Emacs, not some poor imitation. > This has nothing to do with whether the machine is ``stripped down'' > or not. The point being, of course, that what Dan wants is a text editor, and preferably one that is sufficiently similar to emacs that the hardwiring in his fingers will still work. My argument was that he was confusing this with wanting Emacs, which is a common mistake. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 12:04:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16114 for freebsd-current-outgoing; Mon, 26 Oct 1998 12:04:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ccsales.com (ccsales.com [216.0.22.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16093; Mon, 26 Oct 1998 12:04:49 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from ntrkcasa (pool96.hiper.net [216.0.22.96]) by ccsales.com (8.9.1/8.9.0) with SMTP id MAA19254; Mon, 26 Oct 1998 12:03:54 -0800 (PST) Message-Id: <3.0.5.32.19981026115650.05103b10@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 26 Oct 1998 11:56:50 -0800 To: Bill Sandiford , freebsd-current@FreeBSD.ORG From: "Randy A. Katz" Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check your $PATH. At 05:28 PM 10/22/98 -0400, Bill Sandiford wrote: > > >We are having a problem with FreeBSD 3.0 Release and it's associated pw >command. We have scripts that used to work perfectly in the 2.2.x line. >The script still works perfectly when we run it manually as root (logged >in at the terminal) however when cron executes the script, the pw commands >in the script don't work. We are executing the script using the crontab >for root. We know that the script is executing because some of the >other commands in the script are happening and working. The script is >designed to add a new user to our system and the line with pw looks >something like this : > >echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir > >obviously we substitute a correct numeric id for uid and proper groupname >for group, etc. > >We are not sure if this is a problem with our system or a bug with the pw >command that is in the 3.0 release...we have also tried invoking the >script from and inetd process as well.....we have tried this script on 3 >different systems and it doesn't work on any of them except when invoked >manually. > >Any help please!!! > >------------------------------------------ >Bill Sandiford Jr. - Systems Administrator >Interlinks - http://www.interlinks.net >sysop@interlinks.net - bill@interlinks.net >(905)404-0810 > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 12:23:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18542 for freebsd-current-outgoing; Mon, 26 Oct 1998 12:23:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18521 for ; Mon, 26 Oct 1998 12:23:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id PAA14037 for ; Mon, 26 Oct 1998 15:23:00 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id PAA01651; Mon, 26 Oct 1998 15:22:59 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 26 Oct 1998 15:22:59 -0500 (EST) To: freebsd-current@FreeBSD.ORG Subject: panic mounting MFS filesystems X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13876.55104.517860.916965@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just started seeing the following panic when mounting MFS filesystems: #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 ../../kern/kern_shutdown.c:268: No such file or directory. (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:268 #1 0xf0129d16 in db_fncall (dummy1=-153441480, dummy2=0, dummy3=-265935856, dummy4=0xf6daaaf4 "\n") at ../../ddb/db_command.c:531 #2 0xf0129b41 in db_command (last_cmdp=0xf0238d50, cmd_table=0xf0238bb0, aux_cmd_tablep=0xf0260fd0) at ../../ddb/db_command.c:332 #3 0xf0129c06 in db_command_loop () at ../../ddb/db_command.c:454 #4 0xf012bf67 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #5 0xf01e6945 in kdb_trap (type=12, code=0, regs=0xf6daac34) at ../../i386/i386/db_interface.c:157 #6 0xf01f01ef in trap_fatal (frame=0xf6daac34) at ../../i386/i386/trap.c:874 #7 0xf01efee0 in trap_pfault (frame=0xf6daac34, usermode=0) at ../../i386/i386/trap.c:772 #8 0xf01efb33 in trap (frame={tf_es = -153485296, tf_ds = -266993648, tf_edi = -256442880, tf_esi = -153403552, tf_ebp = -153441036, tf_isp = -153441188, tf_ebx = 0, tf_edx = 255, tf_ecx = 32, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -266961014, tf_cs = 8, tf_eflags = 66199, tf_esp = -266070304, tf_ss = -256399296}) at ../../i386/i386/trap.c:396 #9 0xf0167f8a in vfs_object_create (vp=0xf6db3f60, p=0xf6d28940, cred=0xf0b5c200, waslocked=0) at ../../kern/vfs_subr.c:2535 #10 0xf01cc973 in ffs_mountfs (devvp=0xf6db3f60, mp=0xf0b6fe00, p=0xf6d28940, malloctype=0xf02416e0) at ../../ufs/ffs/ffs_vfsops.c:619 #11 0xf01cf187 in mfs_mount (mp=0xf0b6fe00, path=0xefbfddd0 "/tmp", data=0xefbfd688 "", ndp=0xf6daaeb8, p=0xf6d28940) at ../../ufs/mfs/mfs_vfsops.c:342 #12 0xf016883a in mount (p=0xf6d28940, uap=0xf6daaf94) at ../../kern/vfs_syscalls.c:285 #13 0xf01f0473 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 8192, tf_esi = 134647648, tf_ebp = -272638808, tf_isp = -153440284, tf_ebx = 0, tf_edx = -272638744, tf_ecx = 0, tf_eax = 21, tf_trapno = 12, tf_err = 2, tf_eip = 134539072, tf_cs = 31, tf_eflags = 598, tf_esp = -272640436, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #14 0xf01e729c in Xint0x80_syscall () #15 0x80480c9 in ?? () Line 312 of mfs_vfsops.c,v 1.51 is assigning a major number of 255 to the mfs devvp. This vp is then falling through the cracks in the check around line 2553 of vfs_subr.c,v 1.169 because nblkdev == 128. vnode_pager_alloc() never gets called & object remains null. The access done by object->ref_count causes-- the panic. The appended kludge allows me to again use MFS, but I'd appreciate it if somebody who knows the code better could look into this.. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Index: vfs_subr.c =================================================================== RCS file: /scratch/freebsd-cvs/src/sys/kern/vfs_subr.c,v retrieving revision 1.169 diff -c -r1.169 vfs_subr.c *** vfs_subr.c 1998/10/26 08:07:00 1.169 --- vfs_subr.c 1998/10/26 20:06:04 *************** *** 2524,2531 **** if ((error = VOP_GETATTR(vp, &vat, cred, p)) != 0) goto retn; object = vnode_pager_alloc(vp, vat.va_size, 0, 0); ! } else if (major(vp->v_rdev) < nblkdev && ! bdevsw[major(vp->v_rdev)] != NULL) { /* * This simply allocates the biggest object possible * for a VBLK vnode. This should be fixed, but doesn't --- 2524,2532 ---- if ((error = VOP_GETATTR(vp, &vat, cred, p)) != 0) goto retn; object = vnode_pager_alloc(vp, vat.va_size, 0, 0); ! } else if ((vp->v_tag == VT_MFS) ! || ( major(vp->v_rdev) < nblkdev ! && bdevsw[major(vp->v_rdev)] != NULL)) { /* * This simply allocates the biggest object possible * for a VBLK vnode. This should be fixed, but doesn't To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 12:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19479 for freebsd-current-outgoing; Mon, 26 Oct 1998 12:31:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19474 for ; Mon, 26 Oct 1998 12:31:23 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id MAA02622 for current@freebsd.org; Mon, 26 Oct 1998 12:29:46 -0800 (PST) (envelope-from dhw) Date: Mon, 26 Oct 1998 12:29:46 -0800 (PST) From: David Wolfskill Message-Id: <199810262029.MAA02622@pau-amma.whistle.com> To: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <7577.909365359@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 25 Oct 1998 20:29:19 -0500 >From: Harlan Stenn >I still want to see csh replaced with tcsh. Though it's not relevant to the original thread, the following excerpt from my ~/.cshrc may be of interest to those with the above perception: set tcsh = `which tcsh` if ( $?HOSTTYPE && ${?tcsh} && "${tcsh}" == "$SHELL" ) then else if ( $?prompt && { test -x ${tcsh} } ) then setenv SHELL "$tcsh" exec tcsh endif endif Naturally, this is done after the $path is set. And /bin/csh is my defined "login shell" -- but given what I do for a living, sometimes the machine in question can't get to /usr/local/bin (which is made visible via NFS & amd). Need to be a little careful, since the "`which tcsh`" invokes csh all over again.... :-} david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:08:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22741 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:08:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22728 for ; Mon, 26 Oct 1998 13:07:56 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id QAA24144; Mon, 26 Oct 1998 16:08:04 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <19981026125133.A2717@netmonger.net> References: ; from Chuck Robey on Sun, Oct 25, 1998 at 08:27:24PM -0500 <3633C8F8.EF8E14D5@null.net> Date: Mon, 26 Oct 1998 16:07:00 -0500 To: Christopher Masto , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Shells for you and shells for me Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:51 PM -0500 10/26/98, Christopher Masto wrote: > Just keep the damn /bin/sh we have now. Who actually uses it as > their login shell? Nobody. It's there to write /bin/sh scripts, > which by their very nature should be FreeBSD-specific or else > extremely lowest-common-denominator. If there are bugs affecting > the latter, they can be fixed. Do people really want better "sh > compatability"? I don't think that's what this is about. To give a recent example I've stumbled across, a few 'autoconf'- generated scripts will not work under freebsd, due to the way our /bin/sh handles IFS processing. This is more than a someone wanting tab completion or ~ expansion in /bin/sh, it's a practical issue when porting software. The problem with this particular example is that 'autoconf' is probably wrong in what it's doing. Sure, it works on most platforms, but various standards imply that it should not work. Also, there is another way for it to do what it wants to do, which is certain to work in all cases were it currently works, as well as FreeBSD's '/bin/sh' and a few other shells. Hmm, seems to me I had an important point to make when I started to write this, but I've been interrupted enough times that I've now forgotten what it was... :-) No, I remember. I disagree with the idea that /bin/sh scripts "should" be FreeBSD-specific. There is nothing to be gained by having /bin/sh dramatically different than what other OS's have for /bin/sh, precisely because so many people use that for "common" (cross-platform) scripts. At the same time, changing /bin/sh is disruptive enough that I agree with Chris's later comment. If we do come across something which is a problem, then it would be much less disruptive (or at least, "less scary") to just fix that problem in our /bin/sh than it is to abandon the one we have for some completely different one. And we should get the autoconf guys to fix the way they generate some of their scripts... :-) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23586 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:17:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23581 for ; Mon, 26 Oct 1998 13:17:45 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id PAA08946 for ; Mon, 26 Oct 1998 15:17:11 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <3634E6D6.6F1A8863@webwizard.org.mx> Date: Mon, 26 Oct 1998 15:17:11 -0600 From: Edwin Culp Reply-To: eculp@mexcom.net.mx X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: dummynet - mpath Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just saw yet another post on isp, asking about load balancing and bandwidth limiting over two connections and I remembered that dummynet was going to be integrated in current, after the smoke settled. I also recall that there was mention of mpath doing the same. Does anyone know if and when either or both will form part of 3.0? Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:25:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24465 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:25:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24457 for ; Mon, 26 Oct 1998 13:24:56 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 26 Oct 1998 16:23:53 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 26 Oct 1998 13:23:52 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 26 Oct 1998 16:23:51 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Garance A Drosihn cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me In-Reply-To: Garance A Drosihn's (drosih@rpi.edu) message dated Mon, 26 Oct 1998 16:07:00. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 16:23:51 -0500 Message-ID: <9698.909437031@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the actual fragments that are art of autoconf causing the problem, or is it in the configure.in that the package author has written? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24821 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:29:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24816 for ; Mon, 26 Oct 1998 13:29:48 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA14549; Mon, 26 Oct 1998 22:34:13 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 26 Oct 1998 22:34:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Nordier cc: mike@smith.net.au, Jos.Backus@nl.origin-it.com, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: <199810260941.LAA26041@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Robert Nordier wrote: > > I also encountered another problem: /boot/loader sometimes ignores > > all keypresses (I wasn't able even to break the countdown), but I'm not > > sure in what circumstances it happens - it sometimes happens, when I type > > something on the boot: prompt, then delete it. > > If this happened with the new boot1/boot2, can you confirm this is > still a problem? Your original report of this was some time ago, and > various changes have been made, including to the input routine. I just checked it with the newest sources - I built the binaries, and installed them, and rebooted... Well, after several times I kind of see a pattern. /boot/loader seems to choke when I press Enter _twice_ very quickly at the boot: prompt (but again, not always..). Seems to me that some junk left in some buffer confuses it... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25158 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:35:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25145 for ; Mon, 26 Oct 1998 13:34:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01233; Mon, 26 Oct 1998 13:33:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810262133.NAA01233@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Robert Nordier , mike@smith.net.au, Jos.Backus@nl.origin-it.com, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-reply-to: Your message of "Mon, 26 Oct 1998 22:34:13 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 13:33:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just checked it with the newest sources - I built the binaries, and > installed them, and rebooted... Well, after several times I kind of see a > pattern. /boot/loader seems to choke when I press Enter _twice_ very > quickly at the boot: prompt (but again, not always..). Seems to me that > some junk left in some buffer confuses it... Which "boot" prompt is this? Are you using the new boot1/boot2 or the old one? Sounds like the garbage-flushing check is still broken. Thanks for the tip. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:38:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25565 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:38:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25557 for ; Mon, 26 Oct 1998 13:38:52 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id QAA15372 for ; Mon, 26 Oct 1998 16:38:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id QAA23127; Mon, 26 Oct 1998 16:38:17 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="u/bhGx7dXr" Content-Transfer-Encoding: 7bit Date: Mon, 26 Oct 1998 16:38:16 -0500 (EST) To: freebsd-current@FreeBSD.ORG Subject: Re: panic mounting MFS filesystems In-Reply-To: <13876.55104.517860.916965@grasshopper.cs.duke.edu> References: <13876.55104.517860.916965@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13876.60202.257941.268374@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --u/bhGx7dXr Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Andrew Gallatin writes: > > > The appended kludge allows me to again use MFS, but I'd appreciate it > if somebody who knows the code better could look into this.. > Actually, the above mentioned kludge allows me to mount an mfs fs, but the first call to ufs_bmap on an mfs file will cause another panic. Here's a better kludge. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 --u/bhGx7dXr Content-Type: application/octet-stream Content-Description: get mfs working again Content-Disposition: attachment; filename="patch" Content-Transfer-Encoding: base64 SW5kZXg6IGtlcm4vdmZzX3N1YnIuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvc2NyYXRj aC9mcmVlYnNkLWN2cy9zcmMvc3lzL2tlcm4vdmZzX3N1YnIuYyx2CnJldHJpZXZpbmcgcmV2 aXNpb24gMS4xNjkKZGlmZiAtdSAtcjEuMTY5IHZmc19zdWJyLmMKLS0tIHZmc19zdWJyLmMJ MTk5OC8xMC8yNiAwODowNzowMAkxLjE2OQorKysgdmZzX3N1YnIuYwkxOTk4LzEwLzI2IDIx OjA5OjQ2CkBAIC0yNTMzLDggKzI1MzMsMTAgQEAKIAkJCSAqLwogCQkJb2JqZWN0ID0gdm5v ZGVfcGFnZXJfYWxsb2ModnAsIElEWF9UT19PRkYoSU5UX01BWCksIDAsIDApOwogCQl9Ci0J CW9iamVjdC0+cmVmX2NvdW50LS07Ci0JCXZwLT52X3VzZWNvdW50LS07CisJCWlmKG9iamVj dCkgeworCQkJb2JqZWN0LT5yZWZfY291bnQtLTsKKwkJCXZwLT52X3VzZWNvdW50LS07CisJ CX0KIAl9IGVsc2UgewogCQlpZiAob2JqZWN0LT5mbGFncyAmIE9CSl9ERUFEKSB7CiAJCQlW T1BfVU5MT0NLKHZwLCAwLCBwKTsKSW5kZXg6IG1pc2Nmcy9zcGVjZnMvc3BlY192bm9wcy5j Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9zY3JhdGNoL2ZyZWVic2QtY3ZzL3NyYy9zeXMv bWlzY2ZzL3NwZWNmcy9zcGVjX3Zub3BzLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNzUK ZGlmZiAtdSAtcjEuNzUgc3BlY192bm9wcy5jCi0tLSBzcGVjX3Zub3BzLmMJMTk5OC8xMC8y NiAwODo1MzoxMwkxLjc1CisrKyBzcGVjX3Zub3BzLmMJMTk5OC8xMC8yNiAyMToyNjoyNApA QCAtMjg1LDcgKzI4NSw4IEBACiAJCQlyZXR1cm4gKEVJTlZBTCk7CiAJCWJzaXplID0gQkxL REVWX0lPU0laRTsKIAkJZGV2ID0gdnAtPnZfcmRldjsKLQkJaWYgKChpb2N0bCA9IGJkZXZz d1ttYWpvcihkZXYpXS0+ZF9pb2N0bCkgIT0gTlVMTCAmJgorCQlpZiAobWFqb3IoZGV2KSA8 IG5ibGtkZXYgJiYKKwkJICAgIChpb2N0bCA9IGJkZXZzd1ttYWpvcihkZXYpXS0+ZF9pb2N0 bCkgIT0gTlVMTCAmJgogCQkgICAgKCppb2N0bCkoZGV2LCBESU9DR1BBUlQsIChjYWRkcl90 KSZkcGFydCwgRlJFQUQsIHApID09IDAgJiYKIAkJICAgIGRwYXJ0LnBhcnQtPnBfZnN0eXBl ID09IEZTX0JTREZGUyAmJgogCQkgICAgZHBhcnQucGFydC0+cF9mcmFnICE9IDAgJiYgZHBh cnQucGFydC0+cF9mc2l6ZSAhPSAwKQpJbmRleDogdWZzL3Vmcy91ZnNfYm1hcC5jCj09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0KUkNTIGZpbGU6IC9zY3JhdGNoL2ZyZWVic2QtY3ZzL3NyYy9zeXMvdWZzL3Vm cy91ZnNfYm1hcC5jLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjIzCmRpZmYgLXUgLXIxLjIz IHVmc19ibWFwLmMKLS0tIHVmc19ibWFwLmMJMTk5OC8xMC8yNiAwODo1MzoxMwkxLjIzCisr KyB1ZnNfYm1hcC5jCTE5OTgvMTAvMjYgMjE6MjU6MjkKQEAgLTE0OSw3ICsxNDksOCBAQAog CQkgKi8KIAkJZGV2dnAgPSBpcC0+aV9kZXZ2cDsKIAotCQlpZiAoZGV2dnAgIT0gTlVMTCAm JiBkZXZ2cC0+dl90eXBlID09IFZCTEspIHsKKwkJaWYgKGRldnZwICE9IE5VTEwgJiYgZGV2 dnAtPnZfdHlwZSA9PSBWQkxLICYmCisJCSAgICAobWFqb3IoZGV2dnAtPnZfcmRldikgPCBu YmxrZGV2KSkgewogCQkJaWYgKGJkZXZzd1ttYWpvcihkZXZ2cC0+dl9yZGV2KV0tPmRfbWF4 aW8gPiBNQVhQSFlTKSB7CiAJCQkJbWF4cnVuID0gTUFYUEhZUzsKIAkJCQl2cC0+dl9tYXhp byA9IE1BWFBIWVM7Cg== --u/bhGx7dXr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:43:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26029 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:43:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26019 for ; Mon, 26 Oct 1998 13:43:52 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA23517; Mon, 26 Oct 1998 22:48:19 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 26 Oct 1998 22:48:19 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Robert Nordier , Jos.Backus@nl.origin-it.com, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: <199810262133.NAA01233@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Mike Smith wrote: > > I just checked it with the newest sources - I built the binaries, and > > installed them, and rebooted... Well, after several times I kind of see a > > pattern. /boot/loader seems to choke when I press Enter _twice_ very > > quickly at the boot: prompt (but again, not always..). Seems to me that > > some junk left in some buffer confuses it... > > Which "boot" prompt is this? Are you using the new boot1/boot2 or the > old one? The new one. I.e. cd /sys/boot make depend all install cd /boot disklabel -B -b boot1 -s boot2 /dev/rwd1s1 reboot Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:44:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26129 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:44:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26124 for ; Mon, 26 Oct 1998 13:44:50 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (root@caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id WAA11469 for ; Mon, 26 Oct 1998 22:44:13 +0100 (MET) Received: from via.ecp.fr (dae.via.ecp.fr [138.195.136.50]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id WAA03209 for ; Mon, 26 Oct 1998 22:44:11 +0100 (MET) Message-ID: <3634F018.ACDD1F78@via.ecp.fr> Date: Mon, 26 Oct 1998 22:56:41 +0100 From: X-dae X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: fatal trap 12: page fault while in kernel mode References: <199810261426.GAA06190@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i updated to -current, works like a charm now. thanks for your time, -- Krapf Andres, Engineering student at the Ecole Centrale Paris IRCnet: X-dae -- dae@via.ecp.fr -=- FreeBSD:The Power To Serve -=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 13:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27281 for freebsd-current-outgoing; Mon, 26 Oct 1998 13:57:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-7-dbn.dial-up.net [196.34.155.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27270 for ; Mon, 26 Oct 1998 13:57:12 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA01438; Mon, 26 Oct 1998 23:54:34 +0200 (SAT) From: Robert Nordier Message-Id: <199810262154.XAA01438@ceia.nordier.com> Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: from Andrzej Bialecki at "Oct 26, 98 10:34:13 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Mon, 26 Oct 1998 23:54:26 +0200 (SAT) Cc: rnordier@nordier.com, mike@smith.net.au, Jos.Backus@nl.origin-it.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Mon, 26 Oct 1998, Robert Nordier wrote: > > > > I also encountered another problem: /boot/loader sometimes ignores > > > all keypresses (I wasn't able even to break the countdown), but I'm not > > > sure in what circumstances it happens - it sometimes happens, when I type > > > something on the boot: prompt, then delete it. > > > > If this happened with the new boot1/boot2, can you confirm this is > > still a problem? Your original report of this was some time ago, and > > various changes have been made, including to the input routine. > > I just checked it with the newest sources - I built the binaries, and > installed them, and rebooted... Well, after several times I kind of see a > pattern. /boot/loader seems to choke when I press Enter _twice_ very > quickly at the boot: prompt (but again, not always..). Seems to me that > some junk left in some buffer confuses it... That's great, thanks. I've managed to get it happening fairly reproducibly. FWIW, it needs Enter three times at the boot manager prompt here. I think I may have found the problem: anyway, I found something. I'll just have to work on my keyboard technique to test it. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 14:02:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28062 for freebsd-current-outgoing; Mon, 26 Oct 1998 14:02:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28050 for ; Mon, 26 Oct 1998 14:02:06 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA20374; Mon, 26 Oct 1998 17:01:20 -0500 (EST) Message-ID: <19981026170120.A19969@netmonger.net> Date: Mon, 26 Oct 1998 17:01:20 -0500 From: Christopher Masto To: Garance A Drosihn , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me References: ; <3633C8F8.EF8E14D5@null.net> <19981026125133.A2717@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Garance A Drosihn on Mon, Oct 26, 1998 at 04:07:00PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 04:07:00PM -0500, Garance A Drosihn wrote: > No, I remember. I disagree with the idea that /bin/sh scripts > "should" be FreeBSD-specific. There is nothing to be gained > by having /bin/sh dramatically different than what other OS's > have for /bin/sh, precisely because so many people use that for > "common" (cross-platform) scripts. At the same time, changing I meant that there are two classes of /bin/sh scripts: one of them is intended to be portable (such as what autoconf should generate), and thus should not touch on the more esoteric areas. The other category would be things like, say, /usr/bin/linux.. they can use FreeBSD-isms, 'cause they have no reason to be portable. This is a much smaller category than the former. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ Suppose you made a desktop application like a spreadsheet and all of a sudden Microsoft were to call you one day and say "you know, we've just decided we're not gonna give you the information necessary to let you write a product that runs on top of our operating system. On top of our desktop." I mean, what would you do? You go, you look at the room, you stare at the ceiling? What would you do, call me, file a lawsuit? You're a little company, come on. - GARY REBACK, Antitrust attorney To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 15:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04177 for freebsd-current-outgoing; Mon, 26 Oct 1998 15:00:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04172 for ; Mon, 26 Oct 1998 15:00:06 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) id OAA26805 for current@freebsd.org; Mon, 26 Oct 1998 14:59:16 -0800 (PST) Message-ID: <19981026145916.A25703@best.com> Date: Mon, 26 Oct 1998 14:59:16 -0800 From: "Jan B. Koum " To: current@FreeBSD.ORG Subject: error in share/doc/usd/13.viref Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I am trying to bring my 486 with plain, vanilla 3.0 install from -RELEASE to -CURRENT. Unfortunately I get an odd error when I run: {coredump}/usr/src # make -DNOLKM -DNOGAMES buildworld [snip] ===> share/doc/usd/13.viref sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' /usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' *** Error code 3 Stop. *** Error code 1 Of course, going into /usr/src/share/doc/usd/13.viref and doing "make" does not give me such error. Any hints? I guess I can always run make world with -DNOSHARE ... -- Yan I don't have the password .... + Jan Koum But the path is chainlinked .. | Spelled Jan, pronounced Yan. There. So if you've got the time .... | Web: http://www.best.com/~jkb Set the tone to sync ......... + OS: http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 15:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05112 for freebsd-current-outgoing; Mon, 26 Oct 1998 15:10:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05105 for ; Mon, 26 Oct 1998 15:10:02 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.Sendmail.ORG (8.9.1/8.9.1) with ESMTP id PAA03606; Mon, 26 Oct 1998 15:09:28 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id PAA27194; Mon, 26 Oct 1998 15:09:38 -0800 (PST) Message-Id: <199810262309.PAA27194@flamingo.McKusick.COM> To: Don Lewis Subject: Re: Soft-Updates aware fsck available. cc: Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 23 Oct 1998 00:03:34 PDT." <199810230703.AAA20052@salsa.gv.tsc.tdk.com> Date: Mon, 26 Oct 1998 15:09:37 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Don Lewis Message-Id: <199810230703.AAA20052@salsa.gv.tsc.tdk.com> Date: Fri, 23 Oct 1998 00:03:34 -0700 In-Reply-To: Kirk McKusick "Re: Soft-Updates aware fsck available." (Oct 22, 10:40pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Kirk McKusick , Don Lewis Subject: Re: Soft-Updates aware fsck available. Cc: Julian Elischer , current@FreeBSD.ORG On Oct 22, 10:40pm, Kirk McKusick wrote: } Subject: Re: Soft-Updates aware fsck available. } If there were a bad block, then `resolved' would not be true } and we would not take this action. I added the resolved variable, } so if we find something fishy in the first or second pass, we } will back off on the aggressive tossing in later passes. If you } remove a large file tree, then some of the subdirectories may not } be completely cleaned out yet, but you still want to nuke them. } So using empty as a criterion is likely to put a bunch of } undesirable stuff in lost+found. Does this seem reasonable? Ok, I feel somewhat better about this now, though autonuking has always bothered me. My big concern is that resolved might be cleared later on, and by then it would be too late ... By the time that we have gotten to the auto-nuking stage, we have had to read all the inodes, indirect blocks, and directory contents. If any of those reads fails, then we will not auto-nuke. In short, everything of importance that might be read has already been found, plus we have not found any unexpected inconsistencies. I could imagine a senario that passed these tests and still had serious errors, but they are pretty unlikely and almost certainly would be serious enough that you would still be stuck with restoring your disk from tape. Something that occurred to me in another thread where I was thinking that unreferenced empty directories should be cleared (the more conservative approach), is that unless you cleared the directories in the correct order, you could end up with links (usually "..") pointing to unallocated inodes if fsck were interrupted while it was cleaning. This would be bad because a subsequent fsck run could stumble over these dangling links and require manual intervention. The case of ".." referring to an unallocated inode is treated specially in fsck. Specifically, it is viewed as the top of an orphaned tree, so is stuck in lost+found with the comment "previous parent was XX" where XX is the inode value for "..". So, here, unlike any other name that references an unallocated inode, the ordering of removals does not matter. ~Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 15:16:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05603 for freebsd-current-outgoing; Mon, 26 Oct 1998 15:16:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05598 for ; Mon, 26 Oct 1998 15:16:33 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA17268; Mon, 26 Oct 1998 15:15:49 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Brian Feldman cc: Jay Nelson , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-reply-to: Your message of "Mon, 26 Oct 1998 00:38:52 EST." Date: Mon, 26 Oct 1998 15:15:48 -0800 Message-ID: <17264.909443748@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate to be a wet blanket, but has anyone compared sizes? /bin/sh is also a necessary component of the boot floppy and if pdksh bloats us past 1.44MB and the space can't be reasonably reclaimed elsewhere (and good luck there since all the obvious avenues of doing so have long since been tried and/or implemented), that's a show-stopper. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 15:20:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06079 for freebsd-current-outgoing; Mon, 26 Oct 1998 15:20:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-57-dbn.dial-up.net [196.34.155.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06058 for ; Mon, 26 Oct 1998 15:20:13 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA02936; Tue, 27 Oct 1998 01:16:39 +0200 (SAT) From: Robert Nordier Message-Id: <199810262316.BAA02936@ceia.nordier.com> Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: <199810262154.XAA01438@ceia.nordier.com> from Robert Nordier at "Oct 26, 98 11:54:26 pm" To: freebsd-current@FreeBSD.ORG Date: Tue, 27 Oct 1998 01:16:14 +0200 (SAT) Cc: abial@nask.pl, rnordier@nordier.com, mike@smith.net.au, Jos.Backus@nl.origin-it.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Andrzej Bialecki wrote: > > On Mon, 26 Oct 1998, Robert Nordier wrote: > > > > > > I also encountered another problem: /boot/loader sometimes ignores > > > > all keypresses (I wasn't able even to break the countdown), but I'm not > > > > sure in what circumstances it happens - it sometimes happens, when I type > > > > something on the boot: prompt, then delete it. > > > > > > If this happened with the new boot1/boot2, can you confirm this is > > > still a problem? Your original report of this was some time ago, and > > > various changes have been made, including to the input routine. > > > > I just checked it with the newest sources - I built the binaries, and > > installed them, and rebooted... Well, after several times I kind of see a > > pattern. /boot/loader seems to choke when I press Enter _twice_ very > > quickly at the boot: prompt (but again, not always..). Seems to me that > > some junk left in some buffer confuses it... > > That's great, thanks. I've managed to get it happening fairly > reproducibly. FWIW, it needs Enter three times at the boot manager > prompt here. > > I think I may have found the problem: anyway, I found something. I'll > just have to work on my keyboard technique to test it. :-) There following patch makes a difference here, though I'm not sure this is necessarily the only problem. Index: vidconsole.c =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/libi386/vidconsole.c,v retrieving revision 1.6 diff -u -r1.6 vidconsole.c --- vidconsole.c 1998/10/11 10:07:52 1.6 +++ vidconsole.c 1998/10/26 23:07:53 @@ -120,9 +120,7 @@ v86.addr = 0x16; v86.eax = 0x100; v86int(); - if (!(v86.efl & PSL_Z)) - return(v86.eax & 0xff); - return(0); + return(!(v86.efl & PSL_Z)); } #if KEYBOARD_PROBE The function vidc_ischar() was attempting to return the ASCII code of the key pressed, even though several PC keys don't have an ASCII representation. The corresponding serial function comc_ischar() is less ambitious, so the patch reduces the behavior to the lower common denominator. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:08:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12240 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:08:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12235 for ; Mon, 26 Oct 1998 16:08:06 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id QAA17686; Mon, 26 Oct 1998 16:07:24 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-reply-to: Your message of "Mon, 26 Oct 1998 19:16:50 GMT." <199810261916.MAA15070@usr04.primenet.com> Date: Mon, 26 Oct 1998 16:07:24 -0800 Message-ID: <17682.909446844@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you sure it wasn't discussed on -committers or -core instead? Quite sure. http://www.freebsd.org/search/search.html#mailinglists is your friend: Date: Sun, 04 Oct 1998 11:10:51 -0700 From: "Jordan K. Hubbard" To: Mark Murray Cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with Kerberos and /etc/auth.conf Message-ID: <7857.907524651@time.cdrom.com> In-Reply-To: Your message of "Sun, 04 Oct 1998 19:59:49 +0200." <199810041759.TAA06181@gratis.grondar.za> Etc.. > As far as disabling goes -- don't you just say "rlogin -K" instead > of "rlogin", etc.? Assuming you're the kind of user who RTFMs rather than posting messages to various lists and newsgroups saying "Why does my rlogin command hang?!", sure, that's a fine suggestion. You must also hang out with a better class of users than I do. Anyway, please see the cited discussion. This is turning into a rehash. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12599 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:12:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12592 for ; Mon, 26 Oct 1998 16:12:45 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id TAA196180; Mon, 26 Oct 1998 19:12:50 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <9698.909437031@brown.pfcs.com> References: Garance A Drosihn's (drosih@rpi.edu) message dated Mon, 26 Oct 1998 16:07:00. Date: Mon, 26 Oct 1998 19:11:45 -0500 To: Harlan Stenn From: Garance A Drosihn Subject: Re: Shells for you and shells for me Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:23 PM -0500 10/26/98, Harlan Stenn wrote: > Is the actual fragments that are art of autoconf causing the > problem, or is it in the configure.in that the package author > has written? Some general macros in autoconf, such as AC_PATH_PROGS, can (with the right parameters) result in something like: IFS=: (and some other things) for ac_dir in $PATH:/other/path:/another/path ; do if test -f $ac_dir/$ac_word ; then ...do stuff... fi done IFS= (what it used to equal) The problem is that IFS should effect what happens with the expansion of $PATH, but it should not (apparently) effect the rest of the line. The guy who put together this autoconf-ed program in question believes that he was using autoconf 2.12. It does look like 2.12 is trying to avoid this problem, and code he ended up with *did* work on the all platforms that we tried except for /bin/sh under FreeBSD. I must admit I don't really know enough about autoconf to figure out how all the various pieces of autoconf come together, though. [not that this is critical to the original topic of this thread, but I thought I'd supply a few more details...] --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13643 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:24:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13636 for ; Mon, 26 Oct 1998 16:24:29 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA27842; Mon, 26 Oct 1998 19:23:14 -0500 (EST) Date: Mon, 26 Oct 1998 19:23:14 -0500 (EST) From: Brian Feldman To: "Jordan K. Hubbard" cc: Jay Nelson , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <17264.909443748@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've specified multiple times, pdksh is SMALLER then our current FreeBSD-as. (Not meaning to be rude tho) {"/home/green"}$ ls -l /bin/{,k}sh -r-xr-xr-x 1 root wheel 297488 Oct 18 21:32 /bin/ksh -r-xr-xr-x 1 root wheel 321120 Oct 19 01:37 /bin/sh {"/home/green"}$ file /bin/{,k}sh /bin/sh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped /bin/ksh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped BTW, as per the floppy, it seems the newest floppies have minigzip AND gzip? If I'm wrong, correct me, but that would be a waste of space. Besides, if you really want to take more out, take compression out of gzip since all we need is the uncompression. Cheers, Brian Feldman On Mon, 26 Oct 1998, Jordan K. Hubbard wrote: > I hate to be a wet blanket, but has anyone compared sizes? /bin/sh is > also a necessary component of the boot floppy and if pdksh bloats us > past 1.44MB and the space can't be reasonably reclaimed elsewhere (and > good luck there since all the obvious avenues of doing so have long > since been tried and/or implemented), that's a show-stopper. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:24:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13798 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:24:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13791 for ; Mon, 26 Oct 1998 16:24:45 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA16435; Mon, 26 Oct 1998 17:24:03 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd016407; Mon Oct 26 17:23:59 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA29067; Mon, 26 Oct 1998 17:23:52 -0700 (MST) From: Terry Lambert Message-Id: <199810270023.RAA29067@usr07.primenet.com> Subject: Re: sh and ~ expansion To: Studded@gorean.org (Studded) Date: Tue, 27 Oct 1998 00:23:52 +0000 (GMT) Cc: green@zone.syracuse.net, dag-erli@ifi.uio.no, current@FreeBSD.ORG In-Reply-To: <36339533.49D5D9F0@gorean.org> from "Studded" at Oct 25, 98 01:16:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why don't we just use pdksh? > > Oh dear. I've had in the back of my mind for a long time to suggest us > replacing our pseudo-implementation of sh with Bash in posix mode, but I > haven't made the suggestion because I can think of at least 3 holy wars > that it would start right off hand, and I can guess that there are more > I don't know about. :) Issues (not wars), in order of perceived importance: 1) License; /bin/sh is in the boot path 2) 100% bug compatability with existing /bin/sh 3) size in a "crunched" boot floppy 4) size in general a) image size b) memory footprint 5) standards compliance 6) All other compatability issues 7) All other preference issues 8) Blue. We'll paint the boxes blue. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14069 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:27:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galois.boolean.net (galois.boolean.net [209.133.111.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14064 for ; Mon, 26 Oct 1998 16:27:01 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (galois.boolean.net [209.133.111.74]) by galois.boolean.net (8.8.8/8.8.8) with SMTP id AAA28586 for ; Tue, 27 Oct 1998 00:32:50 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981026163758.009dd550@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 26 Oct 1998 16:37:58 -0800 To: current@FreeBSD.ORG From: "Kurt D. Zeilenga" Subject: Changing sh for compatibility sake In-Reply-To: References: <19981026125133.A2717@netmonger.net> <3633C8F8.EF8E14D5@null.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD sh is not the lowest common denominator. Neither is bash. Neither is pdsh. Neither is ksh or whatever your favorite shell is. They are all factors of the lowest common denominator. Changing FreeBSD sh to something else will: 1) not improve the portability of existing scripts. In fact, the change can only decrease portability of existing scripts. 2) not change the lowest common denominator for script developers. That is, FreeBSD sh will still be in use and, hence, will still be a factor. Even if the target is just FreeBSD, both old and new shells would be factors. This change can only add new factors to the lowest common denominator. Changing the sh for compatibility sake does not make much sense. If you are going to change sh, do it for functionality sake... just make sure the functionality gain is worth the resulting portability losses. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:34:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14669 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:34:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14664 for ; Mon, 26 Oct 1998 16:34:01 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA20882; Mon, 26 Oct 1998 17:33:25 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd020862; Mon Oct 26 17:33:21 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA29513; Mon, 26 Oct 1998 17:33:20 -0700 (MST) From: Terry Lambert Message-Id: <199810270033.RAA29513@usr07.primenet.com> Subject: Re: fatal trap 12: page fault while in kernel mode To: green@zone.syracuse.net (Brian Feldman) Date: Tue, 27 Oct 1998 00:33:19 +0000 (GMT) Cc: mike@smith.net.au, dae@via.ecp.fr, current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Oct 26, 98 11:18:49 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Even tho it's not piped, it seems to be located in pmap_enter when you do > a mental_sort()... This is the insert bug that somone used my diagnostic patch with the panic on an insertion of an already inserted page to find, and for which David Greenman committed a fix the other day. Common Sense: If you have a problem with -current, before posting to the -current list about it, update to the most recent sources and try again. If it persists, THEN post about it... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14713 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:34:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14707 for ; Mon, 26 Oct 1998 16:34:40 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA27973; Mon, 26 Oct 1998 19:33:22 -0500 (EST) Date: Mon, 26 Oct 1998 19:33:22 -0500 (EST) From: Brian Feldman To: Terry Lambert cc: Studded , dag-erli@ifi.uio.no, current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <199810270023.RAA29067@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I'll try and answer as many of those as possible in one shot: License: Public Domain (hence PDKSH). VERY BSD-friendly! :) Compatibility with /bin/sh: hasn't broken one single script size of binary (static ELF): text data bss dec hex filename 302081 10088 36588 348757 55255 /bin/sh 283681 5496 37692 326869 4fcd5 /bin/ksh bmakeability: pdksh uses autoconf but its Makefile is bmake-compatible Image size: green 753 0.0 0.4 500 284 p2 Ss+ 7:31PM 0:00.03 ksh green 756 0.5 0.5 600 356 p3 Ss+ 7:31PM 0:00.04 sh Standards: /bin/sh is Bourne, with a few Korn features, pdksh has just about every Korn feature, and Korn shells by definition are backward-compatible with Bourne shells. That should be about all I can think of now. From a user perspective, pdksh has a better vi mode and tab-completion, so is a better interactive shell. Cheers, Brian Feldman On Tue, 27 Oct 1998, Terry Lambert wrote: > > > Why don't we just use pdksh? > > > > Oh dear. I've had in the back of my mind for a long time to suggest us > > replacing our pseudo-implementation of sh with Bash in posix mode, but I > > haven't made the suggestion because I can think of at least 3 holy wars > > that it would start right off hand, and I can guess that there are more > > I don't know about. :) > > Issues (not wars), in order of perceived importance: > > 1) License; /bin/sh is in the boot path > > 2) 100% bug compatability with existing /bin/sh > > 3) size in a "crunched" boot floppy > > 4) size in general > > a) image size > b) memory footprint > > 5) standards compliance > > 6) All other compatability issues > > 7) All other preference issues > > 8) Blue. We'll paint the boxes blue. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15196 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:38:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15171 for ; Mon, 26 Oct 1998 16:38:28 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA28001; Mon, 26 Oct 1998 19:37:35 -0500 (EST) Date: Mon, 26 Oct 1998 19:37:34 -0500 (EST) From: Brian Feldman To: "Kurt D. Zeilenga" cc: current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake In-Reply-To: <3.0.5.32.19981026163758.009dd550@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See my reply to Terry's questions. Pdksh is a better Bourne shell, AKA the Korn shell (albeit a very good clone). It has SIGNIFICANT feature improvements, and has a smaller a. space b. memory footprint. It will improve compatibility with Korn scripts. Imagine /bin/sh being linked to /bin/ksh. Now there's some _real_ disk space savings. Oh, and if I'm not mistaken, ksh would allow us to remove -lalias from the boot.flp. Brian Feldman On Mon, 26 Oct 1998, Kurt D. Zeilenga wrote: > FreeBSD sh is not the lowest common denominator. Neither is bash. > Neither is pdsh. Neither is ksh or whatever your favorite shell is. > They are all factors of the lowest common denominator. > > Changing FreeBSD sh to something else will: > 1) not improve the portability of existing scripts. In fact, > the change can only decrease portability of existing scripts. > > 2) not change the lowest common denominator for script > developers. That is, FreeBSD sh will still be in use and, > hence, will still be a factor. Even if the target is > just FreeBSD, both old and new shells would be factors. > This change can only add new factors to the lowest > common denominator. > > Changing the sh for compatibility sake does not make much sense. > If you are going to change sh, do it for functionality sake... just > make sure the functionality gain is worth the resulting portability > losses. > > Kurt > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:40:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15391 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:40:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15379 for ; Mon, 26 Oct 1998 16:40:50 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA28017; Mon, 26 Oct 1998 19:39:27 -0500 (EST) Date: Mon, 26 Oct 1998 19:39:27 -0500 (EST) From: Brian Feldman To: Terry Lambert cc: mike@smith.net.au, dae@via.ecp.fr, current@FreeBSD.ORG Subject: Re: fatal trap 12: page fault while in kernel mode In-Reply-To: <199810270033.RAA29513@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree with you entirely! No reason to complain about bugs in dead code. Idea: let's get the Correct Patch for that ip_input.c bug committed :) Cheers, Brian Feldman On Tue, 27 Oct 1998, Terry Lambert wrote: > > Even tho it's not piped, it seems to be located in pmap_enter when you do > > a mental_sort()... > > This is the insert bug that somone used my diagnostic patch with the > panic on an insertion of an already inserted page to find, and for > which David Greenman committed a fix the other day. > > > Common Sense: If you have a problem with -current, before posting > to the -current list about it, update to the most recent sources > and try again. If it persists, THEN post about it... > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15441 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:41:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15431 for ; Mon, 26 Oct 1998 16:41:14 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA19731; Mon, 26 Oct 1998 17:40:36 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd019684; Mon Oct 26 17:40:27 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id RAA29779; Mon, 26 Oct 1998 17:40:25 -0700 (MST) From: Terry Lambert Message-Id: <199810270040.RAA29779@usr07.primenet.com> Subject: Re: Shells for you and shells for me To: drosih@rpi.edu (Garance A Drosihn) Date: Tue, 27 Oct 1998 00:40:25 +0000 (GMT) Cc: chris@netmonger.net, current@FreeBSD.ORG In-Reply-To: from "Garance A Drosihn" at Oct 26, 98 04:07:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To give a recent example I've stumbled across, a few 'autoconf'- > generated scripts will not work under freebsd, due to the way our > /bin/sh handles IFS processing. This is more than a someone wanting > tab completion or ~ expansion in /bin/sh, it's a practical issue when > porting software. Yes, recursive macro expansion does not work; that's either a "make" issue or a "sh" issue, depending on where you want to push the blame. > The problem with this particular example is that 'autoconf' is > probably wrong in what it's doing. Sure, it works on most > platforms, but various standards imply that it should not > work. Also, there is another way for it to do what it wants > to do, which is certain to work in all cases were it currently > works, as well as FreeBSD's '/bin/sh' and a few other shells. Exactly my opinion, actually. There is one autoconf generated makefile that assumes recursive macro expansion (in general, files generates by configure generated by autoconf are tending to require GNU make for the reason that ..uh...er... no good reason). In fact, there is one set of code, the Cyrus ACAPD code, that is known to not compile with the GNU toolchain, yet require GNU make after the configure. Bletch. Depending on features that result in undefined behaviour according to the relevent standards is Just Plain Wrong(tm). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:41:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15474 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:41:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15463 for ; Mon, 26 Oct 1998 16:41:31 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id SAA07275; Mon, 26 Oct 1998 18:40:34 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id SAA00702; Mon, 26 Oct 1998 18:23:11 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Mon, 26 Oct 1998 18:23:11 -0600 (CST) From: Jay Nelson To: "Jordan K. Hubbard" cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <17264.909443748@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Jordan K. Hubbard wrote: >I hate to be a wet blanket, but has anyone compared sizes? /bin/sh is >also a necessary component of the boot floppy and if pdksh bloats us >past 1.44MB and the space can't be reasonably reclaimed elsewhere (and >good luck there since all the obvious avenues of doing so have long >since been tried and/or implemented), that's a show-stopper. > >- Jordan -r-xr-xr-x 1 bin bin 307200 Oct 4 15:22 /bin/sh -r-xr-xr-x 1 bin bin 167936 Mar 22 1998 /usr/local/bin/ksh @(#)PD KSH v5.2.13 97/10/27 FreeBSD acp.qiv.com 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Sat Oct 17 13:26:42 \ CDT 1998 root@acp.qiv.com:/usr2/src/sys/compile/ACP i386 On a 3.0-BETA system from 10/17, sh = 321104 and ksh = 297440. Not as great a difference, but still a gain. >From a size perspective, pdksh may be a benefit. I normally develop scripts for AIX on my FreeBSD box, and so far, have had more trouble between 3.2.5/4.2.1 versions of AIX than between FBSD and AIX. -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 16:42:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15584 for freebsd-current-outgoing; Mon, 26 Oct 1998 16:42:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15545 for ; Mon, 26 Oct 1998 16:42:26 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 10872 invoked by uid 1000); 27 Oct 1998 01:45:44 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 26 Oct 1998 20:45:44 -0400 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-scsi@FreeBSD.ORG Subject: DPT Hangs at Boot (Especially with 2.2.7) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ To those who do not know; I am the orignal author and the maintainer of the DPT drivers for FreeBSD ] Recently I have been receiving a rather constant stream of complaints that sound more or less like: When running DPT PM3334 (mainly) on FreeBSD 2.2.7 (almost always) I run into the problem where the system simply hangs during boot, or during fsck, or when switching from single-user to multi-user. The system also tends to hang when the system installation creates new file-systems during fresh installation. When the system freezes, diagnostic LED 1 is either permanently ON, or slowly blinking. The motherboard I have is ASUS model ____ (almost always and has a 300MHz (or faster) Pentium-II. The motherboard uses the Intel BX chipset (almost without exception). The DPT runs firmware version 7M0. Another thing that happens to me is that the file-system creation crashes when using a very large ``disk'' (array) and creating huge (over 4GB) file-systems. If the above sounds familiar, read on. Analysis (which was partially funded by some good souls with horrible problems of this nature) shows the following: a. The huge file-system newfs crash is probably not directly DPT related; The DPT controller simply makes it easy to come up with a 20-100GB ``disk''. This is a known (to me, at least) problem in FreeBSD-2.x.y. It appears as something in the sysinstall code (I admit to have no clue what/where) assumes that file-system sizes (in bytes) are expressed as 32bit integers. This is obviously not good enough for file-systems larger than 4GB. The solution here is to simply avoid creating any file-system ,during fresh install!) larger than 1-2GB. The problem does not seem to inflict normal fdisk/disklabel/newfs. b. Replace firmware 7M0 with 7Li. You can find 7Li in my ftp server: ftp://simon-shapiro.org/crash/fw/476d07li.fwi. This will improve things. It appears as if 7M0 is a bit confusable with the data rate that FreeBSD can send its way. This is less critical with 3.0+CAM, but very noticeable with 2.2.7. c. Move the DPT card to another slot. Move the video card to another slot. If you have multiple DPTs, swap between them. This seems to cure or greatly improve things. It cam also make things go real bad. I have a test system (sent to me by a ``customer'') that I can routinely cause to hang during POST (way before FreeBSD is loaded in any was shape or form) by simply plugging the DPT to the slot closest to the CPU. d. Upgrade to 3.0. It seems 2.2.7 does something funny (or does not do something important?) during shutdown. This is evidenced by the difference in behavior between power-up and reboot. Pushing the reset button produces results that are somewhere between power-up and all-software reboot. Folks, I am sorry I can only give you work around solutions (and not perfect ones!) and cannot give you a correction. Be assured I am working with the factory people to isolate and narrow-down the problem. BTW, I am not a regular reader of -questions, so please drop me a line if you think I can help... Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 17:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19230 for freebsd-current-outgoing; Mon, 26 Oct 1998 17:21:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19224 for ; Mon, 26 Oct 1998 17:21:46 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA126840; Mon, 26 Oct 1998 20:21:58 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199810270040.RAA29779@usr07.primenet.com> References: from "Garance A Drosihn" at Oct 26, 98 04:07:00 pm Date: Mon, 26 Oct 1998 20:20:53 -0500 To: Terry Lambert From: Garance A Drosihn Subject: Re: Shells for you and shells for me Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:40 AM +0000 10/27/98, Terry Lambert wrote: >> To give a recent example I've stumbled across, a few 'autoconf'- >> generated scripts will not work under freebsd, due to the way our >> /bin/sh handles IFS processing. This is more than a someone wanting >> tab completion or ~ expansion in /bin/sh, it's a practical issue when >> porting software. > >Yes, recursive macro expansion does not work; that's either a "make" >issue or a "sh" issue, depending on where you want to push the blame. Hmm. For the problem I ran into, I wouldn't think of it as recursive macro expansion. Seems to me that it's just a difference in how IFS processing is handled. The following script will show the issue I happened to run into: ftp://eclipse.its.rpi.edu/pub/fbsd/bugs/ifs_bug.sh (that script doesn't have 'make' in it at all, so I suspect you're referring to a different issue than the one I tripped into). The above script "works" under many bourne-like shells, although there is some reason to believe that it should not work (and it does not work under FreeBSD's /bin/sh). --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 17:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19410 for freebsd-current-outgoing; Mon, 26 Oct 1998 17:22:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19399 for ; Mon, 26 Oct 1998 17:22:37 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA03245; Mon, 26 Oct 1998 20:21:02 -0500 (EST) Date: Mon, 26 Oct 1998 20:21:02 -0500 (EST) From: Chuck Robey To: "Kurt D. Zeilenga" cc: current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake In-Reply-To: <3.0.5.32.19981026163758.009dd550@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Kurt D. Zeilenga wrote: > FreeBSD sh is not the lowest common denominator. I'm sorry, that's not true. Ask anyone who writes shell scripts that install software (or perform any necessarily portable function) across multiple platforms. sh is the shell to use ONLY BECAUSE it's the lowest common denominator. Why else would they use the dumbest shell? People use sh because it's the most likely to be universally available. It may seem strange, but it's certainly true, and if you write your scripts using sh, they'll just work anywhere (stepping over the problem of a badly written script ab initio). Please understand, I'm not talking user shells, I'm talking sysadmin and installer type shells, which means sh, and only sh. No 2nd choice. Have you ever seen an installer script written by a company that *didn't* supply the entire OS, be written in any shell BUT sh? > Neither is bash. > Neither is pdsh. Neither is ksh or whatever your favorite shell is. > They are all factors of the lowest common denominator. That's true of user shells, it's NOT TRUE for sh, which is unique. All the other shells (including the one I like) are for us users; sh is for sysadmins and installer-writers. You don't think I use sh, do you? I use tcsh, which I wouldn't dream of suggesting be used to replace sh. Likewise bash (which is a great shell), likewise scsh, etc. The only reason I saw for putting forward pdksh was because it boasted 100% sh compatibility, it IS being actively developed (new versions still coming out with bug-fixes), and it's smaller (as far as static image) than sh. I was never, ever referring to it's larger, non-compatible-to-sh extensions. If they didn't come without changing the sh compatibility, they weren't worth it. Extra features are a distraction here, and shouldn't be part of the discussion. The point isn't choosing a user shell, it's choosing *sh*, which IS UNIQUE, and must remain so. We use ash now for sh (no, we don't use the original sh code, that's AT&T code). > > Changing FreeBSD sh to something else will: > 1) not improve the portability of existing scripts. In fact, > the change can only decrease portability of existing scripts. > > 2) not change the lowest common denominator for script > developers. That is, FreeBSD sh will still be in use and, > hence, will still be a factor. Even if the target is > just FreeBSD, both old and new shells would be factors. > This change can only add new factors to the lowest > common denominator. but sh *is* the lcd! You can't change the lcd, you can only match it more closely, and that's the single *only* reason I considered pdksh, in just that light. > > Changing the sh for compatibility sake does not make much sense. > If you are going to change sh, do it for functionality sake... just > make sure the functionality gain is worth the resulting portability > losses. > > Kurt > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 18:35:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26844 for freebsd-current-outgoing; Mon, 26 Oct 1998 18:35:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26839 for ; Mon, 26 Oct 1998 18:35:19 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA18417; Mon, 26 Oct 1998 18:34:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Brian Feldman cc: Jay Nelson , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-reply-to: Your message of "Mon, 26 Oct 1998 19:23:14 EST." Date: Mon, 26 Oct 1998 18:34:14 -0800 Message-ID: <18413.909455654@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've specified multiple times, pdksh is SMALLER then our current > FreeBSD-as. (Not meaning to be rude tho) OK, fine. I came in late to this conversation due to being away. That's good to know. What about the bmake aspects of it, since you'd now be talking about having it somewhere in /usr/src? > BTW, as per the floppy, it seems the newest floppies have minigzip AND > gzip? If I'm wrong, correct me, but that would be a waste of space. Wrong. They're the same. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 18:49:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27928 for freebsd-current-outgoing; Mon, 26 Oct 1998 18:49:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27921 for ; Mon, 26 Oct 1998 18:49:33 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id SAA20641; Mon, 26 Oct 1998 18:48:50 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id SAA11532; Mon, 26 Oct 1998 18:48:49 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA00493; Mon, 26 Oct 1998 18:48:48 -0800 (PST) From: Don Lewis Message-Id: <199810270248.SAA00493@salsa.gv.tsc.tdk.com> Date: Mon, 26 Oct 1998 18:48:47 -0800 In-Reply-To: Andrew Gallatin "Re: panic mounting MFS filesystems" (Oct 26, 4:38pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: panic mounting MFS filesystems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 26, 4:38pm, Andrew Gallatin wrote: } Subject: Re: panic mounting MFS filesystems } Actually, the above mentioned kludge allows me to mount an mfs fs, but the } first call to ufs_bmap on an mfs file will cause another panic. Here's } a better kludge. It's working for me so far ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 18:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28621 for freebsd-current-outgoing; Mon, 26 Oct 1998 18:54:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28608 for ; Mon, 26 Oct 1998 18:54:23 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA29458; Mon, 26 Oct 1998 21:53:27 -0500 (EST) Date: Mon, 26 Oct 1998 21:53:27 -0500 (EST) From: Brian Feldman To: "Jordan K. Hubbard" cc: Jay Nelson , current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: <18413.909455654@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see zero problems bmaking it. I suppose I shall integrate it in the tree and get it working that way, but a question: it wouldn't go in src/contrib would it? AFAIK that's for GNU stuff right? and PDKSH is PD... BTW, looking at the dates, a new version of pdksh should be out any day now, so we'll see. I'll send an e-mail to the current maintainer. Cheers, Brian Feldman On Mon, 26 Oct 1998, Jordan K. Hubbard wrote: > > I've specified multiple times, pdksh is SMALLER then our current > > FreeBSD-as. (Not meaning to be rude tho) > > OK, fine. I came in late to this conversation due to being away. > That's good to know. What about the bmake aspects of it, since > you'd now be talking about having it somewhere in /usr/src? > > > BTW, as per the floppy, it seems the newest floppies have minigzip AND > > gzip? If I'm wrong, correct me, but that would be a waste of space. > > Wrong. They're the same. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 20:32:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07607 for freebsd-current-outgoing; Mon, 26 Oct 1998 20:32:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07601 for ; Mon, 26 Oct 1998 20:32:15 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-103.camalott.com [208.229.74.103]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id WAA30548; Mon, 26 Oct 1998 22:32:22 -0600 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA10486; Mon, 26 Oct 1998 18:46:29 -0600 (CST) (envelope-from joelh) To: Chuck Robey Cc: "David O'Brien" , Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: 3.0 installation problems References: From: Joel Ray Holveck Date: 26 Oct 1998 18:46:26 -0600 In-Reply-To: Chuck Robey's message of "Sat, 24 Oct 1998 19:04:01 -0400 (EDT)" Message-ID: <86btmyq1b1.fsf@detlev.UUCP> Lines: 48 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not terribly difficult to make it build without X11. A primary > requirement, however, is to have absolutely NO X11 stuff on your > machine, because emacs will hunt it down and use X11 if it finds any > vestiges around. It's not all that rabid, and can be avoided (see my last paragraph, below). Emacs's configure relies on a combination of user-specified paths, xmkmf, X11/Intrinsic.h, and XtMalloc. If you specify x-includes or x-libraries on the `configure' command line, then configure takes your word for it. If you don't, then configure will use xmkmf to find them. If that fails, then it will look for X11/Intrinsic.h in a list of standard locations, and XtMalloc in -lXt in a similar list. If locations for both include files and libraries are found, then Emacs will use X. Otherwise, it won't. The places checked for X11/Intrinsic.h are: Your default #include <> path /usr/{X11,X11R[654]}/include /usr/include/{X11,X11R[654]} /usr/local/{X11,X11R[654]}/include /usr/local/include/{X11,X11R[654]} /usr/[xX]386/include /usr/XFree86/include/X11 /usr/include /usr/{local,unsupported,athena}/include /usr/local/x11r5/include /usr/lpp/Xamples/include /usr/openwin/include /usr/openwin/share/include A similar list is used for -lXt. > If you _have_ any pieces of X11 around, then making emacs ignore it > is a PITA. "./configure --without-x" will disable X11 (and its `configure' checks). You can have X in your default -I and -L paths, and Emacs will ignore it completely. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 20:32:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07653 for freebsd-current-outgoing; Mon, 26 Oct 1998 20:32:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07634 for ; Mon, 26 Oct 1998 20:32:25 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-103.camalott.com [208.229.74.103]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id WAA30554; Mon, 26 Oct 1998 22:32:27 -0600 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA10490; Mon, 26 Oct 1998 18:50:33 -0600 (CST) (envelope-from joelh) To: Edwin Culp Cc: Brian Feldman , Chuck Robey , Studded , "Dag-Erling C. Smørgrav" , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: <363353AB.BCE48ADC@webwizard.org.mx> From: Joel Ray Holveck Date: 26 Oct 1998 18:50:31 -0600 In-Reply-To: Edwin Culp's message of "Sun, 25 Oct 1998 10:36:59 -0600" Message-ID: <86af2iq148.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been using pdksh for more than three years, first on Linux and > then FreeBSD. I haven't even had a /bin/sh or much less bash in a > passwd file for several years and haven't had a problem. I make > world almost every day, make release about once a week, etc. passwd files are irrelevant. Most scripts have #! lines to force /bin/sh. While we're at it, I probably should try configuring a few GNU utils using pdksh instead of sh; autoconf gets notoriously hairy at times, and would probably be a better stress test than `make world' for shell compatibility. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 20:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08450 for freebsd-current-outgoing; Mon, 26 Oct 1998 20:41:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galois.boolean.net (galois.boolean.net [209.133.111.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08445 for ; Mon, 26 Oct 1998 20:41:43 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (galois.boolean.net [209.133.111.74]) by galois.boolean.net (8.8.8/8.8.8) with SMTP id EAA01402; Tue, 27 Oct 1998 04:47:36 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981026205249.009cd860@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 26 Oct 1998 20:52:49 -0800 To: Chuck Robey From: "Kurt D. Zeilenga" Subject: Re: Changing sh for compatibility sake Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981026163758.009dd550@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck wrote: >I'm sorry, that's not true. Ask anyone who writes shell scripts that >install software (or perform any necessarily portable function) across >multiple platforms. sh is the shell to use ONLY BECAUSE it's the lowest >common denominator. Why else would they use the dumbest shell? I've written numerous system/install sh scripts. But it's not to one specific implementation, its many. It seems like every OS has it's own variant of sh. I do not know of any version of sh that can reliable used as a golden target sh. Each and very implementation of sh has its quirks that have to be dealt with. FreeBSD sh definitely has its, as do the others. Any change will likely cause problems in some existing scripts. Also, any change will cause developers to deal with additional portability issues. This is life. Most multiple platform sh developers have already adapted to specific quicks of popular sh implementations. Changing from one to another should not be that big of a deal. I suspect a few FreeBSD-only sh scripts will choke. Don't change sh for compatibility sake, our scripts are already compatible! Do change for functionality sake, we'll adapt as necessary. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 21:16:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10557 for freebsd-current-outgoing; Mon, 26 Oct 1998 21:16:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10549 for ; Mon, 26 Oct 1998 21:16:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA08046; Tue, 27 Oct 1998 16:16:06 +1100 Date: Tue, 27 Oct 1998 16:16:06 +1100 From: Bruce Evans Message-Id: <199810270516.QAA08046@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, gallatin@cs.duke.edu Subject: Re: panic mounting MFS filesystems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Line 312 of mfs_vfsops.c,v 1.51 is assigning a major number of 255 to the mfs >devvp. This vp is then falling through the cracks in the check around >line 2553 of vfs_subr.c,v 1.169 because nblkdev == 128. It would fail completely if nblkdev == 256, and used to overflow the minor number after only 256 mfs mounts. Now it doesn't overflow the minor number until after 2^24 mfs mounts. >vnode_pager_alloc() never gets called & object remains null. The >access done by object->ref_count causes-- the panic. > >The appended kludge allows me to again use MFS, but I'd appreciate it >if somebody who knows the code better could look into this.. >Index: vfs_subr.c >=================================================================== >RCS file: /scratch/freebsd-cvs/src/sys/kern/vfs_subr.c,v >retrieving revision 1.169 >diff -c -r1.169 vfs_subr.c >*** vfs_subr.c 1998/10/26 08:07:00 1.169 >--- vfs_subr.c 1998/10/26 20:06:04 >*************** >*** 2524,2531 **** > if ((error = VOP_GETATTR(vp, &vat, cred, p)) != 0) > goto retn; > object = vnode_pager_alloc(vp, vat.va_size, 0, 0); >! } else if (major(vp->v_rdev) < nblkdev && >! bdevsw[major(vp->v_rdev)] != NULL) { > /* > * This simply allocates the biggest object possible > * for a VBLK vnode. This should be fixed, but doesn't >--- 2524,2532 ---- > if ((error = VOP_GETATTR(vp, &vat, cred, p)) != 0) > goto retn; > object = vnode_pager_alloc(vp, vat.va_size, 0, 0); >! } else if ((vp->v_tag == VT_MFS) >! || ( major(vp->v_rdev) < nblkdev >! && bdevsw[major(vp->v_rdev)] != NULL)) { > /* > * This simply allocates the biggest object possible > * for a VBLK vnode. This should be fixed, but doesn't The VT_MFS check should probably be in the callers. There are only 2 callers for the VBLK case, both in ffs_vfsops.c, and these used to check that major(vp->v_rdev) < nblkdev, so the buggy check here never succeeded. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 21:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12044 for freebsd-current-outgoing; Mon, 26 Oct 1998 21:38:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.rdu (mail.rdu.bellsouth.net [205.152.32.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12039 for ; Mon, 26 Oct 1998 21:38:46 -0800 (PST) (envelope-from zaz@null.net) Received: from null.net (host-209-214-162-147.rdu.bellsouth.net [209.214.162.147]) by mail.rdu (8.8.8-spamdog/8.8.5) with ESMTP id AAA28057 for ; Tue, 27 Oct 1998 00:38:09 -0500 (EST) Message-ID: <3635598B.3AB54817@null.net> Date: Tue, 27 Oct 1998 00:26:35 -0500 From: Nathan Grass Reply-To: zaz@null.net Organization: zaz.net X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: bin.inf corrupt? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From the DOS SETUP.EXE I get the following when trying to prepare for a DOS install. "BIN.INF: .INF file is corrupt. Press ESC" While in the FreeBSD install/setup program (from the boot floppy) I can't get the system to find the packages. Everything has been put in C:\FREEBSD (all caps too if that matters) and I even tried converting the bin.inf file to DOS ASCII and get the same problem. The file system is FAT (not FAT32) running Win98 and I can't figure out what might be wrong. Any tips? // zaz@null.net -=- This sig footer was last updated Oct 05 1998 -=- \\ | From: Nathan Grass http://home.dreamhaven.net/zaz/ | | Employer: ComSys http://www.comsysinc.com/ * Technical Consultant | \\ -=- Unless otherwise noted, expressed views are my opinions. -=- // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 26 23:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20307 for freebsd-current-outgoing; Mon, 26 Oct 1998 23:14:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-4-dbn.dial-up.net [196.34.155.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20300 for ; Mon, 26 Oct 1998 23:14:14 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA04645; Tue, 27 Oct 1998 09:12:34 +0200 (SAT) From: Robert Nordier Message-Id: <199810270712.JAA04645@ceia.nordier.com> Subject: Re: bin.inf corrupt? In-Reply-To: <3635598B.3AB54817@null.net> from Nathan Grass at "Oct 27, 98 00:26:35 am" To: zaz@null.net Date: Tue, 27 Oct 1998 09:12:31 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Grass wrote: > >From the DOS SETUP.EXE I get the following when trying to prepare for > >a DOS install. > "BIN.INF: .INF file is corrupt. Press ESC" > > While in the FreeBSD install/setup program (from the boot floppy) I > can't get the system to find the packages. > > Everything has been put in C:\FREEBSD (all caps too if that matters) > and I even tried converting the bin.inf file to DOS ASCII and get the > same problem. > > The file system is FAT (not FAT32) running Win98 and I can't figure > out what might be wrong. > > Any tips? Don't use SETUP.EXE. It is usually very out of date, even if you got it off a Walnut Creek CDROM. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 00:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26270 for freebsd-current-outgoing; Tue, 27 Oct 1998 00:34:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26265 for ; Tue, 27 Oct 1998 00:34:18 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA21314; Tue, 27 Oct 1998 08:34:36 GMT Date: Tue, 27 Oct 1998 08:34:36 +0000 (GMT) From: Doug Rabson To: Don Lewis cc: Kris Kennaway , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) In-Reply-To: <199810260847.AAA26341@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, Don Lewis wrote: > On Oct 26, 8:43am, Doug Rabson wrote: > } Subject: Re: nestea v2 against freebsd 3.0-Release (fwd) > > } Thanks for the explanation. Would you like to commit the patch or shall > } I? > > Well, since I don't have commit privs ... > > You might also consider the followon patch that I just sent. I'll probably commit both, one after the other. I would prefer to keep bugfixes separate from optimisations in the logs and it gives an easy way of backing out either. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 02:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03482 for freebsd-current-outgoing; Tue, 27 Oct 1998 02:19:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03477 for ; Tue, 27 Oct 1998 02:19:45 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id EAA15729; Tue, 27 Oct 1998 04:19:05 -0600 (CST) Message-ID: <19981027041904.32792@futuresouth.com> Date: Tue, 27 Oct 1998 04:19:04 -0600 From: "Matthew D. Fuller" To: Nate Williams Cc: Andrzej Bialecki , Christopher Masto , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me References: <19981026125133.A2717@netmonger.net> <199810261902.MAA21553@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199810261902.MAA21553@mt.sri.com>; from Nate Williams on Mon, Oct 26, 1998 at 12:02:13PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 12:02:13PM -0700, Nate Williams woke me up to tell me: > > > Just keep the damn /bin/sh we have now. Who actually uses it as their > > > login shell? Nobody. It's there to write /bin/sh scripts, which by > > > > I do. I always change shell for root account from /bin/csh to /bin/sh. > > That's what the 'toor' account is there for. The only difference > between it and root is the shell. Whee! So I'm not the only one who does this? {~} mortis:{358} %head -2 /etc/passwd root:*:0:0:SysAdmin:/root:/bin/sh toor:*:0:0:SysAdmin part deux:/root:/bin/tcsh {~} mortis:{359} %which su su: aliased to su toor *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 03:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05799 for freebsd-current-outgoing; Tue, 27 Oct 1998 03:01:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05794 for ; Tue, 27 Oct 1998 03:01:02 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id MAA29465; Tue, 27 Oct 1998 12:05:22 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 27 Oct 1998 12:05:21 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Nordier cc: freebsd-current@FreeBSD.ORG, mike@smith.net.au, Jos.Backus@nl.origin-it.com Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: <199810262316.BAA02936@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Robert Nordier wrote: > There following patch makes a difference here, though I'm not sure > this is necessarily the only problem. This patch fixes the problem here. Thanks. I'm wondering, though, why the cursor in boot: prompt is non-destructive, i.e. when I press backspace, the cursor moves back but doesn't erase the character from the screen. After some doing mistakes in input, the screen looks messy... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 03:14:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06645 for freebsd-current-outgoing; Tue, 27 Oct 1998 03:14:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-39-dbn.dial-up.net [196.34.155.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06640 for ; Tue, 27 Oct 1998 03:13:53 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA06325; Tue, 27 Oct 1998 13:11:48 +0200 (SAT) From: Robert Nordier Message-Id: <199810271111.NAA06325@ceia.nordier.com> Subject: Re: /boot/loader hangs after arrow/function key pressed at prompt In-Reply-To: from Andrzej Bialecki at "Oct 27, 98 12:05:21 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 27 Oct 1998 13:11:45 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG, mike@smith.net.au, Jos.Backus@nl.origin-it.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Tue, 27 Oct 1998, Robert Nordier wrote: > > > There following patch makes a difference here, though I'm not sure > > this is necessarily the only problem. > > This patch fixes the problem here. Thanks. Good to know, thanks. > I'm wondering, though, why the cursor in boot: prompt is non-destructive, > i.e. when I press backspace, the cursor moves back but doesn't erase the > character from the screen. After some doing mistakes in input, the screen > looks messy... You're right. The old (biosboot) code outputs "\b \b" where the new code just does '\b'. I'll commit a fix for it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 04:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13027 for freebsd-current-outgoing; Tue, 27 Oct 1998 04:23:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13021 for ; Tue, 27 Oct 1998 04:23:15 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA19501; Tue, 27 Oct 1998 13:22:25 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA00412; Tue, 27 Oct 1998 13:22:23 +0100 (MET) Message-ID: <19981027132222.54378@follo.net> Date: Tue, 27 Oct 1998 13:22:22 +0100 From: Eivind Eklund To: Brian Feldman , "Jordan K. Hubbard" Cc: Jay Nelson , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: <18413.909455654@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Brian Feldman on Mon, Oct 26, 1998 at 09:53:27PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 26, 1998 at 09:53:27PM -0500, Brian Feldman wrote: > I see zero problems bmaking it. I suppose I shall integrate it in the tree > and get it working that way, but a question: it wouldn't go in src/contrib > would it? AFAIK that's for GNU stuff right? and PDKSH is PD... BTW, > looking at the dates, a new version of pdksh should be out any day now, so > we'll see. I'll send an e-mail to the current maintainer. It would go in src/contrib. src/contrib is for anything that is maintained outside our tree. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 04:31:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13587 for freebsd-current-outgoing; Tue, 27 Oct 1998 04:31:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13582 for ; Tue, 27 Oct 1998 04:31:55 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA05463; Tue, 27 Oct 1998 07:31:16 -0500 (EST) Date: Tue, 27 Oct 1998 07:31:15 -0500 (EST) From: Brian Feldman To: "Kurt D. Zeilenga" cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake In-Reply-To: <3.0.5.32.19981026205249.009cd860@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me repeat this once more: not a SINGLE script breaks with pdksh! Brian Feldman On Mon, 26 Oct 1998, Kurt D. Zeilenga wrote: > Chuck wrote: > >I'm sorry, that's not true. Ask anyone who writes shell scripts that > >install software (or perform any necessarily portable function) across > >multiple platforms. sh is the shell to use ONLY BECAUSE it's the lowest > >common denominator. Why else would they use the dumbest shell? > > I've written numerous system/install sh scripts. But it's not to > one specific implementation, its many. It seems like every OS > has it's own variant of sh. I do not know of any version of sh > that can reliable used as a golden target sh. Each and very > implementation of sh has its quirks that have to be dealt with. > FreeBSD sh definitely has its, as do the others. > > Any change will likely cause problems in some existing scripts. > Also, any change will cause developers to deal with additional > portability issues. This is life. Most multiple platform sh > developers have already adapted to specific quicks of popular > sh implementations. Changing from one to another should not > be that big of a deal. I suspect a few FreeBSD-only sh scripts > will choke. > > Don't change sh for compatibility sake, our scripts are already > compatible! Do change for functionality sake, we'll adapt as > necessary. > > Kurt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 06:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24950 for freebsd-current-outgoing; Tue, 27 Oct 1998 06:58:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24942 for ; Tue, 27 Oct 1998 06:58:11 -0800 (PST) (envelope-from chet@nike.ins.cwru.edu) Received: (chet@localhost) by nike.ins.cwru.edu (8.8.7/CWRU-2.5-bsdi) id JAA08060; Tue, 27 Oct 1998 09:57:20 -0500 (EST) (from chet) Date: Tue, 27 Oct 1998 09:56:00 -0500 From: Chet Ramey To: chuckr@mat.net Subject: Re: Changing sh for compatibility sake Cc: Kurt@OpenLDAP.Org, current@FreeBSD.ORG Reply-To: chet@po.CWRU.Edu In-Reply-To: Message from chuckr@mat.net of Mon, 26 Oct 1998 20:21:02 -0500 (EST) (id ) Message-ID: <981027145600.AA08055.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have you ever seen an installer script written by a company that > *didn't* supply the entire OS, be written in any shell BUT sh? Checkpoint writes all of its Firewall-1 installation (and other) scripts in csh. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 07:49:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28804 for freebsd-current-outgoing; Tue, 27 Oct 1998 07:49:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28798 for ; Tue, 27 Oct 1998 07:49:32 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id KAA03737 for ; Tue, 27 Oct 1998 10:51:33 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 27 Oct 1998 10:51:33 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: current@FreeBSD.ORG Subject: sys/kern/subr_bus.c ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sys/kern/subr_bus.c line 37: #include "opt_bus.h" This makes "make depend" fail on my kernel, I can't find this file anywhere on my machine, this leaked in sometime last night as I was able to get a kernel to compile however MFS was broken, cvsup'd some changes in this morning noting fixes to mfs/vfs but now this has crept in. Simply commenting this line out seems to have worked (no warnings whatsoever), I'm gonna reboot with this kernel and see what's up. I still have my kernel from about 2 weeks ago which was amazingly stable, i just wanted to have the anti-nestea patches. thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 08:18:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00764 for freebsd-current-outgoing; Tue, 27 Oct 1998 08:18:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00759 for ; Tue, 27 Oct 1998 08:18:29 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id RAA18291 for ; Tue, 27 Oct 1998 17:17:49 +0100 (CET) Message-ID: <3635F22D.1A6B9EB4@simultan.ch> Date: Tue, 27 Oct 1998 17:17:49 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: IPv6 in -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm using FreeBSD as my main and almost exclusive networking platform, at university (STU Bratislva, Slovakia), at work, and at home since a long time ago. Since I do research in networking, I'd really love to see IPv6 in FreeBSD; moreover I'm ready to do a lot about this. To my knowledge there are at least two IPv6 implementations for FreeBSD: INRIA and KAME. I'm working for over 1 year with INRIA, in fact I'm operating two 6bone sites (STUBA and SIMULTAN) and have also experience with programming for IPv6, as well as quite deep insight into the INRIA IPv6 protocol stack (and BSD networking of course :-)). INRIA seems to have a much more mature status than KAME (with my full respect to the latter), so I'd opt for the integration of INRIA IPv6 into FreeBSD-current. INRIA's distribution is quite huge. Among others it contains ALTQ, some additional ATM stuff etc. I'd prefer to separate the core protocol and its support (mainly in libc) from this additional stuff. For example I've seen the offer of Andre Oppermann to integrate ALTQ on this list. Here's my proposal: 1. I could integrate INRIA's IPv6 implementation into -current. That means the kernel code, changes to libraries and network utilities (like ifconfig etc). Additional IPv6 applications could be packaged (ported) separately. 2. I'd watch for changes in the INRIA distribution and integrate them into -current. Possible caveats: 1. License. As far as I've seen, there shouldn't be any problem, but this is only IMHO. 2. Alternative IPv6 implementations. I could imagine the life of the KAME team not getting easier with the presence of another IPv6 protocol implementation in -current. Please let me know what you think. If there is a more appropriate way of doing what I want to do, I'd be thankful for hints. In fact, I could start with the integration next week. Thank you very much Regards, Thomas -- ========================================================== Dipl.-Ing. Thomas Seidmann Senior IT systems architect Simultan AG, CH-6246 Altishofen, Switzerland mailto:tseidmann@simultan.ch tel +41.62.7489000 http://www.simultan.ch/~thomas fax +41.62.7489010 ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 09:27:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06504 for freebsd-current-outgoing; Tue, 27 Oct 1998 09:27:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06499 for ; Tue, 27 Oct 1998 09:27:50 -0800 (PST) (envelope-from root@troutmask.apl.washington.edu) Received: (from root@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id JAA01480 for current@freebsd.org; Tue, 27 Oct 1998 09:31:35 -0800 (PST) (envelope-from root) From: Charlie Root Message-Id: <199810271731.JAA01480@troutmask.apl.washington.edu> Subject: missing opt_bus.h To: current@FreeBSD.ORG Date: Tue, 27 Oct 1998 09:31:35 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources cvsup'd at 0930 pst. Rebuilt config. Configure kernel. cd ../../compile/TROUTMASK make depend ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory mkdep: compile failed *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 09:34:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07077 for freebsd-current-outgoing; Tue, 27 Oct 1998 09:34:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.solplus.de (rossel.solplus.de [195.125.160.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07071 for ; Tue, 27 Oct 1998 09:34:38 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [193.24.63.232]) by rossel.solplus.de (8.8.8/8.8.8) with ESMTP id SAA28554; Tue, 27 Oct 1998 18:34:58 +0100 (MET) Received: from exchange.aubi.de ([170.56.121.91]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id TAA27741; Tue, 27 Oct 1998 19:44:05 +0100 Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Tue, 27 Oct 1998 18:30:05 +0100 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'Charlie Root'" , current@FreeBSD.ORG Subject: RE: missing opt_bus.h Date: Tue, 27 Oct 1998 18:29:03 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA07072 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > make depend > > ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory > mkdep: compile failed > *** Error code 1 Had similar error try to delete the whole TROUTMASK subtree and build again with config TROUTMASK. It should run properly. hope this helps -- Markus Döhr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 09:45:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08005 for freebsd-current-outgoing; Tue, 27 Oct 1998 09:45:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08000 for ; Tue, 27 Oct 1998 09:45:48 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id JAA02471; Tue, 27 Oct 1998 09:49:29 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199810271749.JAA02471@troutmask.apl.washington.edu> Subject: Re: missing opt_bus.h In-Reply-To: from =?ISO-8859-1?Q?Markus_D=F6hr?= at "Oct 27, 1998 6:29: 3 pm" To: doehrm@aubi.de (Markus =?ISO-8859-1?Q?D=F6hr?=) Date: Tue, 27 Oct 1998 09:49:29 -0800 (PST) Cc: root@troutmask.apl.washington.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Markus Döhr: > > make depend > > > > ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory > > mkdep: compile failed > > *** Error code 1 > > Had similar error > > try to delete the whole TROUTMASK subtree and build again with config > TROUTMASK. It should run properly. > Been there. Seems to be an incomplete commit to recent changes in sys/kern/subr_bus.c $ Id: subr_bus.c,v 1.8 1998/10/27 09:21:43 dfr Exp $ -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 11:47:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17781 for freebsd-current-outgoing; Tue, 27 Oct 1998 11:47:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from du248-02.cc.iastate.edu (du248-02.cc.iastate.edu [129.186.248.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17774; Tue, 27 Oct 1998 11:47:17 -0800 (PST) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by du248-02.cc.iastate.edu (8.8.5/8.8.5) with SMTP id NAA21108; Tue, 27 Oct 1998 13:46:34 -0600 (CST) Message-Id: <199810271946.NAA21108@du248-02.cc.iastate.edu> To: freebsd-mobile@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Reply-To: kent@iastate.edu Subject: Notebook install Date: Tue, 27 Oct 1998 13:46:32 CST From: Kent Vander Velden Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I would like to install FreeBSD on a Digital HiNote 745. I am concerned about the support that FreeBSD has for pcmcia cards. I would like to have a fast ethernet/modem combo card and a scsi card. What models does FreeBSD support? Will the internal CDROM and floppy be usable? Honestly, how does FreeBSD and Linux compare in laptop technology? It would seem from my glance that Linux has more complete support. I would like to continue to use FreeBSD but if the support is not there there is little choice. Thanks. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 11:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18320 for freebsd-current-outgoing; Tue, 27 Oct 1998 11:54:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18315 for ; Tue, 27 Oct 1998 11:54:41 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id NAA18066; Tue, 27 Oct 1998 13:54:00 -0600 (CST) Received: from klinzhai-74.isdn.mke.execpc.com(169.207.65.202) by peak.mountin.net via smap (V1.3) id sma018064; Tue Oct 27 13:53:41 1998 Message-Id: <3.0.3.32.19981027135403.00fe7a3c@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 27 Oct 1998 13:54:03 -0600 To: Brian Feldman From: "Jeffrey J. Mountin" Subject: Re: Changing sh for compatibility sake Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981026205249.009cd860@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:31 AM 10/27/98 -0500, Brian Feldman wrote: >Let me repeat this once more: not a SINGLE script breaks with pdksh! Agreed, but on one of lists someone pointed out some other issues with pdksh. This was quite a while back on -isp or -security. Korn is supposed to 100% bourne compatible. Coming from BSDi to FBSD, I was rather put out that I needed to install it. 8-) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 11:56:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18595 for freebsd-current-outgoing; Tue, 27 Oct 1998 11:56:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18576 for ; Tue, 27 Oct 1998 11:56:11 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.175]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3A24; Tue, 27 Oct 1998 20:55:09 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810271324.IAA26380@shell.monmouth.com> Date: Tue, 27 Oct 1998 20:58:41 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Bill/Carolyn Pechter , Bill/Carolyn Pechter , FreeBSD Current Subject: Re: Some problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-98 Bill/Carolyn Pechter wrote: >> I would love to comment on yer mails Andrzej and the rest, but >> at the moment my CURRENT installation has problems executing >> ppp, keeps giving me these libdes.so.3.0 not found errors. So I >> am going to /stand/sysinstall the DES distribution tonight and >> see if that works. > > > No need to use /stand/sysinstall. > You can just use the install.sh from the directory with the des > in it. > > I did run into a problem with init, libcypher*, rcp etc. being > chflag'd schg... but that was easy to work around. What worked was that I had to edit /etc/rc and modify it to /usr/lib/aout and then copy libdes.so.3.0 in it. That did the trick to get ppp working again. I also copied libl.a to it and if this enables me to make world then I am wondering why such a thing is as far as I have been able to determine (after about 3-5 hours searching online @ www.freebsd.org) that it isn't a standard change or procedure in either make world or somewhere in the docs... Anyways, thanks and if ye don't mind I forward it to -current so they know of how and what. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 12:01:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18971 for freebsd-current-outgoing; Tue, 27 Oct 1998 12:01:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18966; Tue, 27 Oct 1998 12:01:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00830; Tue, 27 Oct 1998 12:00:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810272000.MAA00830@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kent@iastate.edu cc: freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Notebook install In-reply-to: Your message of "Tue, 27 Oct 1998 13:46:32 CST." <199810271946.NAA21108@du248-02.cc.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 12:00:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi. I would like to install FreeBSD on a Digital HiNote 745. > I am concerned about the support that FreeBSD has for pcmcia cards. We all are. > I would like to have a fast ethernet/modem combo card and a scsi > card. No combo cards are supported. We currently only support the Linksys fast ethernet card (and it's not). Until Cardbus is a reality, fast ethernet on PCCARD doesn't make any sense anyway. > What models does FreeBSD support? For 10Mbps ethernet, almost anything NE2000 compatible, or the 3Com 3c589. Modem cards almost all work fine. SCSI card support in 3.0 is nonexistent, as the aic driver hasn't been CAMified yet. Practically, SCSI support in a laptop is almost useless anyway; you don't want to be lugging all the extra peripherals around. I have an Adaptec 1460 and I think I've used it once in the last 12 months. OTOH, I also have an Iomega Jaz Traveler, and I tend to use it by preference (it *is* supported in 3.0). > Will the internal CDROM and floppy be usable? Yes. > Honestly, how does FreeBSD and Linux compare in laptop technology? Linux defintely has broader support. FreeBSD's support is good enough for enough of us that it's not been a critical development issue for a while. > It would seem from my glance that Linux has more complete support. I > would like to continue to use FreeBSD but if the support is not there > there is little choice. That depends on what you want to do. If you want the best laptop support, you should be running Windows 98. Don't put the cart before the horse; pick the platform and the peripherals to do the job. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 12:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19217 for freebsd-current-outgoing; Tue, 27 Oct 1998 12:02:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19203 for ; Tue, 27 Oct 1998 12:02:47 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA18108; Tue, 27 Oct 1998 14:02:00 -0600 (CST) Received: from klinzhai-74.isdn.mke.execpc.com(169.207.65.202) by peak.mountin.net via smap (V1.3) id sma018101; Tue Oct 27 14:01:44 1998 Message-Id: <3.0.3.32.19981027140207.007466e0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 27 Oct 1998 14:02:07 -0600 To: Mike Smith , Bill Sandiford From: "Jeffrey J. Mountin" Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810222152.OAA01173@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:52 PM 10/22/98 -0700, Mike Smith wrote: > >It is almost *never* correct to post to both -current and -stable. >Please pick the one list that suits only. > >> We are having a problem with FreeBSD 3.0 Release and it's associated pw >> command. We have scripts that used to work perfectly in the 2.2.x line. >> The script still works perfectly when we run it manually as root (logged >> in at the terminal) however when cron executes the script, the pw commands >> in the script don't work. > >"Help, my car doesn't work. Help me!". Don't you mean "new car" in this case. ;) >You might want to start by offering some more details. Any error >messages and the return code would be a good start. It could be run in debug mode too, if it is a shell script or PERL. Knowing what type script would have allowed other to add to the suggestions. 8-) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 12:20:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20798 for freebsd-current-outgoing; Tue, 27 Oct 1998 12:20:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hschpt06.hou.ucarb.com ([144.68.7.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20785 for ; Tue, 27 Oct 1998 12:20:21 -0800 (PST) (envelope-from miker@hschpt06.hou.ucarb.com) Received: (from miker@localhost) by hschpt06.hou.ucarb.com (8.8.8/8.8.8) id OAA21052; Tue, 27 Oct 1998 14:19:27 -0600 (CST) (envelope-from mikenguyen@sprintmail.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.3.32.19981027135403.00fe7a3c@207.227.119.2> Date: Tue, 27 Oct 1998 14:19:27 -0600 (CST) From: Mike Nguyen To: "Jeffrey J. Mountin" Subject: Re: Changing sh for compatibility sake Cc: current@FreeBSD.ORG, Brian Feldman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-98 Jeffrey J. Mountin uttered: > At 07:31 AM 10/27/98 -0500, Brian Feldman wrote: >>Let me repeat this once more: not a SINGLE script breaks with pdksh! > > Agreed, but on one of lists someone pointed out some other issues with > pdksh. This was quite a while back on -isp or -security. > > Korn is supposed to 100% bourne compatible. > > Coming from BSDi to FBSD, I was rather put out that I needed to install it. > 8-) First thing I do when I install a new FreeBSD box is install the BSDi ksh binaries from the AT&T software reuse website as /bin/ksh. A real ksh93, no less. I haven't had the guts to replace /bin/sh with it yet (though the man page does have a toggle to display either as sh(1) or ksh(1)). Mike. ------------------------------------------------------------------------------- Mike Nguyen - UNIX Sysadmin and Geek Pager (800) SKY-8888 pin# 1138368 or 1138368@skytel.com "Heisenberg may have slept here" ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 13:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24553 for freebsd-current-outgoing; Tue, 27 Oct 1998 13:13:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.tor.accglobal.net (mail1.tor.accglobal.net [204.92.55.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24548 for ; Tue, 27 Oct 1998 13:13:43 -0800 (PST) (envelope-from josh@ican.net) From: josh@ican.net Received: from staff.tor.acc.ca ([204.92.55.27]) by mail1.tor.accglobal.net with esmtp (Exim 2.02 #1) id 0zYGQE-0000E5-01; Tue, 27 Oct 1998 16:12:58 -0500 Received: from josh by staff.tor.acc.ca with local (Exim 1.92 #1) id 0zYGQE-0002Pg-00; Tue, 27 Oct 1998 16:12:58 -0500 Message-ID: <19981027161257.40034@ican.net> Date: Tue, 27 Oct 1998 16:12:57 -0500 To: current@FreeBSD.ORG Cc: josh@ican.net Subject: Secure RPC/NIS/NIS+ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A number of questions: 1. Long, long ago (May) there was talk about work being done on getting NIS+ support into -current, possibly by the time 3.0-release rolls about. That time is obviously past, and I was just wondering as to the status of this. 2. I've been poking about trying to find some reasonably useful information on Secure RPC. From what I've been able to tell, all Secure RPC buys you is the ability for one machine to (securely) identify itself to the server, but doesnt actually do any end-to-end encryption of the data stream. Does this mean, were NIS hacked to use Secure RPC, that the encrypted passwords (stored on the master) would still be transmitted on the wire unencrypted (as it were)? Having just set up a small NIS domain, I was struck with the thought that the use of ssh to improve security is somewhat obviated if peoples (albeit encrypted) passwords are flying about in the clear. Would Secure RPC solve this problem? (My guess is no, but it wouldnt hurt to have this confirmed) 3. Long, long, longer ago (last June), Bill Paul made mention of having NIS use Secure RPC. Has anything been done in this direction? thanks josh -- Josh Tiefenbach - Member - ACC Corps of Internet Engineers - josh@ican.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 14:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03588 for freebsd-current-outgoing; Tue, 27 Oct 1998 14:38:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03583 for ; Tue, 27 Oct 1998 14:38:30 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id OAA25269; Tue, 27 Oct 1998 14:36:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 27 Oct 1998 14:36:20 -0800 (PST) From: Doug White To: steven cc: current@FreeBSD.ORG Subject: Re: 3.0-Current/3Com 509B ether problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Oct 1998, steven wrote: > > > > > Um, disable the ethernet card drivers you're not using? Some ether card > > probes are destructive. Ican't say I've noticed the same thing on my > > systems with ie and ep both turned on, it sees no ie0 but the ep0 at IRQ > > 10 port 0x300 is detected properly. > > well i updated my src again, i disabled all unecessary probes. > > same thing.. > > my two last tries are turn off PNP (bad since it makes my tuner card and > sound work so nicely) or get another card (not a good choice since it will > have to be ISA). No, no, turn the PnP setting on teh 3com card off, not the system! :-) Go grab the driver disk, boot to DOS, and run 3c5x9cfg off of it. Select 'Configure NIC' from the menu and you'll see what I mean... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 15:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07642 for freebsd-current-outgoing; Tue, 27 Oct 1998 15:03:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07637 for ; Tue, 27 Oct 1998 15:03:42 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA00580; Tue, 27 Oct 1998 15:02:50 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 27 Oct 1998 15:02:49 -0800 (PST) From: Doug White To: Mike Smith cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-Reply-To: <199810242259.PAA25534@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Oct 1998, Mike Smith wrote: > > > The 'adding route' freeze irritates the *&^%( out of me. There are > > > several different things that can go wrong at this point and there's no > > > easy way to tell which one it is. > > > > Is there *ANY* way to debug this? I never had this problem this problem > > in 2.2.5 days. But now I get it for *every* install of 2.2.7 or 3.0. > > I'm seeing "hangs" upto 5 minutes. > > > > All ranges of cards (fxp0, de0, ed0, xl0) on several different subnets > > with different hubs/routers on campus. > > Sysinstall ifconfig's the interface, then exec's > "route -n add default x.x.x.x" > > I added the '-n' in an attempt to reduce the delay in the case where > the nameserver was slow or unreachable (eg. due to error). > > Debugging it is relatively straightforward; build yourself a copy of > sysinstall (cd src/release/sysinstall; make), then run it. You can > experiment with taking various interfaces down before you start it, > reboot and come up single-user, etc. It's not route, it's the (unannounced) nameserver lookup for the FTP site that immediately follows the route add. If you turn debugging on and watch quickly you can see 'Found DNS entry for ftp.freebsd.org successfully...' come up just after the 'add route' box and then the 'logging in to ftp.freebsd.org' box immediately replaces it. Poking through sysinstall, in media.c line 370, it calls init(networkDev) which calls the route add. Upon sucess is sets up some ftp items then calls inet_addr and gethostbyname, without notifying the user or printing a debug, so it appears that its jamming on the route add when in fat it's gethostbyname. Someone should throw a dialog box or debug entry in there to let the user know whats really going on, then try to figure out why inet_addr and/or gethostbyname never times out. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 15:05:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07976 for freebsd-current-outgoing; Tue, 27 Oct 1998 15:05:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07970 for ; Tue, 27 Oct 1998 15:05:49 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA06187; Tue, 27 Oct 1998 16:05:10 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd006116; Tue Oct 27 16:05:00 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA11621; Tue, 27 Oct 1998 16:04:58 -0700 (MST) From: Terry Lambert Message-Id: <199810272304.QAA11621@usr04.primenet.com> Subject: Re: Changing sh for compatibility sake To: green@zone.syracuse.net (Brian Feldman) Date: Tue, 27 Oct 1998 23:04:57 +0000 (GMT) Cc: Kurt@OpenLDAP.Org, chuckr@mat.net, current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Oct 27, 98 07:31:15 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let me repeat this once more: not a SINGLE script breaks with pdksh! Can I have a copy of your TET/ETET validation suite for /bin/sh? Alternately, can I have a copy of your branch path analysis and boundary case generation tool that runs against Bourne shell scripts? I'm not being facetious -- it's just that your claim is a rather bold one, and really requires sustaining evidence of a rather in depth nature before it can be taken at face value. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 16:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18828 for freebsd-current-outgoing; Tue, 27 Oct 1998 16:19:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18817 for ; Tue, 27 Oct 1998 16:19:10 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA16463 for ; Tue, 27 Oct 1998 16:18:26 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 27 Oct 1998 16:18:26 -0800 (PST) From: Doug White To: current@FreeBSD.ORG Subject: Who built XFree86 with Kerberos? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a mailing list of confused users who want to meet you. Please rebuild X without Kerberos; Kerberos is certainly *NOT* the common case. Thanks! Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 16:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20994 for freebsd-current-outgoing; Tue, 27 Oct 1998 16:31:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20958 for ; Tue, 27 Oct 1998 16:31:15 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA21390; Tue, 27 Oct 1998 19:29:42 -0500 (EST) Date: Tue, 27 Oct 1998 19:29:41 -0500 (EST) From: Brian Feldman To: Terry Lambert cc: Kurt@OpenLDAP.Org, chuckr@mat.net, current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake In-Reply-To: <199810272304.QAA11621@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, let me clarify this: not a _single_ script I've ever run into, which uses /bin/sh, breaks whenusing the Korn shell. I have received word from the team that there currently is a bug that (when in Korn mode, no run as 'sh') ((command ); (othercommand)) is attempted to be interpreted in the same manner as (( a = b + c )). This is the Wonrg Way to do this anyway, since there should be spaces between the parenthases.... He says that in some way Netscape makes use of these, I'll have to look for that. A new release should be out soon, and the ((l);(l)) bug will get fixed soon as well. Brian Feldman On Tue, 27 Oct 1998, Terry Lambert wrote: > > Let me repeat this once more: not a SINGLE script breaks with pdksh! > > Can I have a copy of your TET/ETET validation suite for /bin/sh? > > Alternately, can I have a copy of your branch path analysis and > boundary case generation tool that runs against Bourne shell > scripts? > > I'm not being facetious -- it's just that your claim is a rather > bold one, and really requires sustaining evidence of a rather > in depth nature before it can be taken at face value. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 17:02:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25884 for freebsd-current-outgoing; Tue, 27 Oct 1998 17:02:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25839; Tue, 27 Oct 1998 17:02:16 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA00981; Tue, 27 Oct 1998 20:01:32 -0500 (EST) (envelope-from lee) Message-ID: <19981027200132.A977@tidalwave.net> Date: Tue, 27 Oct 1998 20:01:32 -0500 From: Lee Cremeans To: hackers@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Call for help on UDMA on Acer chipsets... Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got myself a shiny new Seagate Medalist Pro 9140 9GB UDMA drive yesterday, and I noticed as I was setting it up last night, that if I enabled DMA on it, it got the dreaded interrupt timeout spasms people have seen. I think I know why...my motherboard, an Amptron 9600, uses an Acer chipset, which isn't explicitly covered in ide_pci.c...so I've had to do what all those others have had to do, and turn off _all_ IDE DMA support on this drive. :( The purpose of this message is to get some help in fixing this--I can be helpful myself, with coding, testing, etc, but I need someone who has an Acer Aladdin IV+ or Aladdin V chipset, runs 3.0-CURRENT, and can get access to the Acer M1543 data sheet (which is available on the web at acerlabs.com, but it's behind a Username/Password box and I don't know how to register). I think it's a real shame to have to run my drive in PIO mode just because of this. Also, a workaround I can think of for other non-supported chipsets (like SiS) would be to put the drive in Multiword DMA mode 2 instead of UDMA--but I'm not sure if this is possible without stepping on any timing toes, I'll see. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 17:57:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02241 for freebsd-current-outgoing; Tue, 27 Oct 1998 17:57:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02235 for ; Tue, 27 Oct 1998 17:57:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02550; Tue, 27 Oct 1998 17:55:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280155.RAA02550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Eric" cc: "Mike Smith" , current@FreeBSD.ORG Subject: Re: Notebook install In-reply-to: Your message of "Tue, 27 Oct 1998 17:35:45 PST." <01df01be0213$48640060$5a3c18d1@so.lame.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 27 Oct 1998 17:55:44 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA02236 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >No combo cards are supported. We currently only support the Linksys > >fast ethernet card (and it's not). Until Cardbus is a reality, fast > >ethernet on PCCARD doesn't make any sense anyway. > > > > Cardbus isn't a reality? I've seen it quite a bit lately. My Compaq Presario has it, most of the ChemBook USA notebooks have it, and I'm sure many other major notebooks have it. We don't support it, so it's not a reality for us. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 19:17:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11518 for freebsd-current-outgoing; Tue, 27 Oct 1998 19:17:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp2.andrew.cmu.edu (SMTP2.ANDREW.CMU.EDU [128.2.10.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11509 for ; Tue, 27 Oct 1998 19:17:54 -0800 (PST) (envelope-from mwhite@cmu.edu) Received: from FRAUGHT.NET.CMU.EDU (FRAUGHT.NET.CMU.EDU [128.2.6.66]) by smtp2.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id WAA04665 for ; Tue, 27 Oct 1998 22:17:14 -0500 (EST) Date: Tue, 27 Oct 1998 22:17:14 -0500 From: Matt White To: freebsd-current@FreeBSD.ORG Subject: Disk space for current Message-ID: <3288535361.909526634@FRAUGHT.NET.CMU.EDU> Originator-Info: login-id=; server=cyrus.andrew.cmu.edu X-Mailer: Mulberry (Win32) [1.4.0, s/n S-100002] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pondering installing -current on my laptop so that I can improve the state of laptop support under freebsd. Could someone list out the disk space needed by /usr/src, /usr/cvs, /usr/obj, etc? I'd like to make intelligent partitioning decisions since a little disk space for games would be nice (I don't know if I could make it through an IETF meeting without them...). Any other disk hits, gotchas and advice are warmly welcomed. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 19:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13320 for freebsd-current-outgoing; Tue, 27 Oct 1998 19:37:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13187; Tue, 27 Oct 1998 19:37:16 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810280337.TAA13187@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLQ; Tue, 27 Oct 1998 19:42:54 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:37:02 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 20:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16985 for freebsd-current-outgoing; Tue, 27 Oct 1998 20:24:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16980; Tue, 27 Oct 1998 20:24:51 -0800 (PST) (envelope-from soren@soekris.dk) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) with SMTP id UAA20773; Tue, 27 Oct 1998 20:24:05 -0800 (PST) X-SMTP: helo soren.soekris from soren@soekris.dk server @207.90.187.212 ip 207.90.187.212 Message-ID: <36369C62.1F92@soekris.dk> Date: Tue, 27 Oct 1998 20:24:02 -0800 From: Soren Kristensen Reply-To: soren@soekris.dk Organization: Soekris Engineering X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: lcremean@tidalwave.net CC: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... References: <19981027200132.A977@tidalwave.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Lee, I would be happy to help you with a UDMA driver for the Acer Aladdin chipsets, not only to be nice, but also because I'm working on a hardware project using the Aladdin IV+, which eventually are going to run freebsd on UDMA drives :-) First, If you haven't got the datasheets, you can get them on my server: http://www.soekris.dk/ds1543v125.pdf -- M1543 http://www.soekris.dk/ds1543cv08.pdf -- M1543C Note that there is both a M1543 and M1543C, but I think that the UDMA programming is the same, even as the M1543C has a slightly larger IDE buffer. Right now I've got a standard motherboard using the Aladdin IV chipset, and although I'm not a freeBSD programmer, I would be able to do testing, and might be helpful on the really low level stuff. And I will probably have prototypes of my own hardware in 6-8 weeks. Best Regards, Soren Kristensen Soekris Engineering Alameda, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 21:20:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20834 for freebsd-current-outgoing; Tue, 27 Oct 1998 21:20:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20826 for ; Tue, 27 Oct 1998 21:20:54 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id IAA08677 for ; Wed, 28 Oct 1998 08:20:09 +0300 (MSK) Date: Wed, 28 Oct 1998 08:20:09 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@FreeBSD.ORG Subject: mkdep failed. missing files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! There is a problem compiling kernel: ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory mkdep: compile failed *** Error code 1 Also, tomorrow CVSup said that there is a file opt_bus.h to update, but there is no such file :)) Please del then commit this file to synchonise. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 21:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22559 for freebsd-current-outgoing; Tue, 27 Oct 1998 21:57:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22551 for ; Tue, 27 Oct 1998 21:57:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00731; Tue, 27 Oct 1998 21:56:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280556.VAA00731@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matt White cc: freebsd-current@FreeBSD.ORG Subject: Re: Disk space for current In-reply-to: Your message of "Tue, 27 Oct 1998 22:17:14 EST." <3288535361.909526634@FRAUGHT.NET.CMU.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 21:56:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm pondering installing -current on my laptop so that I can improve the > state of laptop support under freebsd. Could someone list out the disk > space needed by /usr/src, /usr/cvs, /usr/obj, etc? I'd like to make > intelligent partitioning decisions since a little disk space for games > would be nice (I don't know if I could make it through an IETF meeting > without them...). You will need about 2GB to have an installed system, a copy of the CVS repository and still build the world with comfortable space left over. Putting everything on one partition means that you don't have to second-guess how big everything is going to be (can you say "minidisk" anyone?). > Any other disk hits, gotchas and advice are warmly welcomed. I'll offer a 'hint', and that's get one of the $400 6GB disks and have lots of space for everything. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 22:12:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23405 for freebsd-current-outgoing; Tue, 27 Oct 1998 22:12:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23397 for ; Tue, 27 Oct 1998 22:12:56 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg137-068.ricochet.net (mg137-068.ricochet.net [204.179.137.68]) by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id AAA22538; Wed, 28 Oct 1998 00:12:01 -0600 (CST) Date: Tue, 27 Oct 1998 22:11:53 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Matt White cc: freebsd-current@FreeBSD.ORG Subject: Re: Disk space for current In-Reply-To: <3288535361.909526634@FRAUGHT.NET.CMU.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Matt White wrote: > Date: Tue, 27 Oct 1998 22:17:14 -0500 > From: Matt White > To: freebsd-current@FreeBSD.ORG > Subject: Disk space for current > > I'm pondering installing -current on my laptop so that I can improve the > state of laptop support under freebsd. Could someone list out the disk > space needed by /usr/src, /usr/cvs, /usr/obj, etc? I'd like to make > intelligent partitioning decisions since a little disk space for games > would be nice (I don't know if I could make it through an IETF meeting > without them...). I run -current on my laptop (Dell Latitude CPi). Here's my partition set up: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 92160 0 4.2BSD 0 0 0 # (Cyl. 0 - 5*) b: 524288 92160 swap # (Cyl. 5*- 38*) c: 6281415 0 unused 0 0 # (Cyl. 0 - 390) d: 2257095 4024320 4.2BSD 0 0 0 # (Cyl. 250*- 390*) e: 262144 616448 4.2BSD 0 0 0 # (Cyl. 38*- 54*) f: 1048576 878592 4.2BSD 0 0 0 # (Cyl. 54*- 119*) g: 1048576 1927168 4.2BSD 0 0 0 # (Cyl. 119*- 185*) h: 1048576 2975744 4.2BSD 0 0 0 # (Cyl. 185*- 250*) /dev/wd0s3a 44111 23253 17330 57% / /dev/wd0s3f 508655 328718 139245 70% /usr /dev/wd0s3h 508655 430598 37365 92% /usr/local /dev/wd0s3g 508655 426542 41421 91% /usr/src /dev/wd0s3e 127151 19435 97544 17% /var /dev/wd0s3d 1094370 967957 38864 96% /usr/home I don't have a separate partition for /usr/obj or /cvs. I've put the cvs tree in /home/ncvs (/home is the largest partition). I've just put left /usr/obj in /usr. There are a few times that I've wanted my /usr partition larger, since /usr/obj can get rather large. A full 'make buildworld' takes nearly 250MB. Overall this works pretty well for me, though it'd be nice to have more partitions. > Any other disk hits, gotchas and advice are warmly welcomed. -- Christopher Nielsen Scient: The Art and Science of Electronic Business cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 22:15:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23584 for freebsd-current-outgoing; Tue, 27 Oct 1998 22:15:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rgate2.ricochet.net (rgate2.ricochet.net [204.179.143.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23579 for ; Tue, 27 Oct 1998 22:15:50 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg137-068.ricochet.net (mg137-068.ricochet.net [204.179.137.68]) by rgate2.ricochet.net (8.8.8/8.8.8) with ESMTP id AAA24844; Wed, 28 Oct 1998 00:14:46 -0600 (CST) Date: Tue, 27 Oct 1998 22:14:37 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Mike Smith cc: Matt White , freebsd-current@FreeBSD.ORG Subject: Re: Disk space for current In-Reply-To: <199810280556.VAA00731@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Mike Smith wrote: > > Any other disk hits, gotchas and advice are warmly welcomed. > > I'll offer a 'hint', and that's get one of the $400 6GB disks and have > lots of space for everything. 8) I have one of these. ;-) Though, I have multiple operating systems partitioned on it. :-) 3.5GB seems to work pretty well for me. -- Christopher Nielsen Scient: The Art and Science of Electronic Business cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 22:25:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24287 for freebsd-current-outgoing; Tue, 27 Oct 1998 22:25:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24282; Tue, 27 Oct 1998 22:25:18 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id BAA01457; Wed, 28 Oct 1998 01:27:18 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 28 Oct 1998 01:27:18 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... In-Reply-To: <19981027200132.A977@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From personal experiances with Acer i'd avoid them like the f'ing plague Took 2 tech support people over a week of daily contact before i bit the bullet and manually guessed as to what jumpers where what on a motherboard. One other time i needed jumper info, it only took 3 days of emailing back and forth to get the sheets. After asking why it's not on thier site i was told "it's not something we want the customer to mess with." Anyone familiar with the legal ramifications of having a site up that has anti-testimonials about companies, I have quite a few on my sh*tlist and email corrispondance with these companies to show why. I'm quite sure stuff like that falls under "fair use" no? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 27 Oct 1998, Lee Cremeans wrote: > I just got myself a shiny new Seagate Medalist Pro 9140 9GB UDMA drive > yesterday, and I noticed as I was setting it up last night, that if I > enabled DMA on it, it got the dreaded interrupt timeout spasms people have > seen. I think I know why...my motherboard, an Amptron 9600, uses an Acer > chipset, which isn't explicitly covered in ide_pci.c...so I've had to do > what all those others have had to do, and turn off _all_ IDE DMA support on > this drive. :( > > The purpose of this message is to get some help in fixing this--I can be > helpful myself, with coding, testing, etc, but I need someone who has an > Acer Aladdin IV+ or Aladdin V chipset, runs 3.0-CURRENT, and can get access > to the Acer M1543 data sheet (which is available on the web at acerlabs.com, > but it's behind a Username/Password box and I don't know how to register). I > think it's a real shame to have to run my drive in PIO mode just because of > this. Also, a workaround I can think of for other non-supported chipsets > (like SiS) would be to put the drive in Multiword DMA mode 2 instead of > UDMA--but I'm not sure if this is possible without stepping on any timing > toes, I'll see. > > > -- > Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net > http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 23:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29128 for freebsd-current-outgoing; Tue, 27 Oct 1998 23:27:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28758; Tue, 27 Oct 1998 23:23:43 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id IAA02865; Wed, 28 Oct 1998 08:22:48 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id XAA01341; Tue, 27 Oct 1998 23:32:57 +0100 (MET) (envelope-from wosch) Message-ID: <19981027233255.A1336@panke.de.freebsd.org> Date: Tue, 27 Oct 1998 23:32:55 +0100 From: Wolfram Schneider To: current@FreeBSD.ORG Subject: calcru: negative time of -695317300 usec for pid Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get randomly negative time errors during make world tests: calcru: negative time of -695317300 usec for pid 6931 (cc1) $ uptime 11:32PM up 1 day, 1:28, 4 users, load averages: 1.29, 1.04, 0.81 $ dmesg Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #8: Fri Oct 23 09:57:01 GMT 1998 root@paula.panke.de.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 1476 ns CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 127787008 (124792K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0xc3 on pci0.7.0 ide_pci0: rev 0xc1 int a irq 0 on pci0.15.0 ide_pci: controller is simplex, no DMA on secondary channel Probing for devices on PCI bus 1: vga0: rev 0x10 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a rtinit: wrong ifa (0xf0a16d00) was (0xf0a16f80) calcru: negative time of -695317300 usec for pid 6931 (cc1) swap_pager: suggest more swap space: 253 MB calcru: negative time of -695437148 usec for pid 9990 (test) calcru: negative time of -592101957 usec for pid 20635 (cvsup) -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 23:27:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29138 for freebsd-current-outgoing; Tue, 27 Oct 1998 23:27:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from badlans.lanminds.com (badlans.lanminds.com [208.25.91.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29123 for ; Tue, 27 Oct 1998 23:27:19 -0800 (PST) (envelope-from rrs@badlans.lanminds.com) Received: (from rrs@localhost) by badlans.lanminds.com (8.8.6/8.8.6) id XAA11027 for freebsd-current@freebsd.org; Tue, 27 Oct 1998 23:27:59 -0800 (PST) Date: Tue, 27 Oct 1998 23:27:59 -0800 (PST) From: Robert Schulhof Message-Id: <199810280727.XAA11027@badlans.lanminds.com> To: freebsd-current@FreeBSD.ORG Subject: MFS_ROOT panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HI! Today's commits fixed the problem with panics upon mounting MFS filesystems, but I still get a panic when booting off PicoBSD floppies: mfs_mountroot : can't find rootvperror 6: panic cannot mount root (2) This is source that was cvsupped about an hour ago on an AMD K-6 233MHZ, I've tested this on three machines. I wish I could provide more information but can't figure out how to dump the core image when I don't have SCSI device drivers. Thanks, Rob Robert Schulhof UNIX System Administrator LanMinds Internet. (LMI Net) rrs@lmi.net http://www.lmi.net (510) 843-6389 VOX (510) 843-6390 FAX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 27 23:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01442 for freebsd-current-outgoing; Tue, 27 Oct 1998 23:45:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01310; Tue, 27 Oct 1998 23:45:35 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810280745.XAA01310@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLQ; Tue, 27 Oct 1998 19:42:54 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:37:02 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 02:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11930 for freebsd-current-outgoing; Wed, 28 Oct 1998 02:06:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11911 for ; Wed, 28 Oct 1998 02:06:12 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA25264; Wed, 28 Oct 1998 10:05:27 GMT Date: Wed, 28 Oct 1998 10:05:27 +0000 (GMT) From: Doug Rabson To: "Steven G. Kargl" cc: Markus =?ISO-8859-1?Q?D=F6hr?= , root@troutmask.apl.washington.edu, current@FreeBSD.ORG Subject: Re: missing opt_bus.h In-Reply-To: <199810271749.JAA02471@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Steven G. Kargl wrote: > According to Markus Dhr: > > > make depend > > > > > > ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory > > > mkdep: compile failed > > > *** Error code 1 > > > > Had similar error > > > > try to delete the whole TROUTMASK subtree and build again with config > > TROUTMASK. It should run properly. > > > > Been there. > > Seems to be an incomplete commit to recent changes in > sys/kern/subr_bus.c > > $ Id: subr_bus.c,v 1.8 1998/10/27 09:21:43 dfr Exp $ Fixed, thanks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 02:06:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11970 for freebsd-current-outgoing; Wed, 28 Oct 1998 02:06:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11955 for ; Wed, 28 Oct 1998 02:06:49 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA25268; Wed, 28 Oct 1998 10:07:48 GMT Date: Wed, 28 Oct 1998 10:07:48 +0000 (GMT) From: Doug Rabson To: Dmitry Valdov cc: freebsd-current@FreeBSD.ORG Subject: Re: mkdep failed. missing files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Dmitry Valdov wrote: > Hi! > > There is a problem compiling kernel: > > ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Also, tomorrow CVSup said that there is a file opt_bus.h to update, but > there is no such file :)) > Please del then commit this file to synchonise. Fixed, thanks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 02:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12981 for freebsd-current-outgoing; Wed, 28 Oct 1998 02:18:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bryggen.bgnett.no (bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAB12976 for ; Wed, 28 Oct 1998 02:18:22 -0800 (PST) (envelope-from erikhb@bgnett.no) Received: from server (ti21a96-0274.dialup.online.no [130.67.199.18]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with SMTP id KAA25514; Wed, 28 Oct 1998 10:17:16 GMT Message-ID: <002001be025c$19d4dd20$1401a8c0@server.habatech.no> From: "Erik H. Bakke" To: "Wolfram Schneider" , Subject: Re: calcru: negative time of -695317300 usec for pid Date: Wed, 28 Oct 1998 11:16:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I get randomly negative time errors during make world tests: >calcru: negative time of -695317300 usec for pid 6931 (cc1) > Are you using APM? --- Erik H. Bakke Habatech AS erikhb@bgnett.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 03:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18448 for freebsd-current-outgoing; Wed, 28 Oct 1998 03:20:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([212.242.41.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18434 for ; Wed, 28 Oct 1998 03:20:51 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA00665; Wed, 28 Oct 1998 12:19:30 +0100 (CET) To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Tue, 27 Oct 1998 23:32:55 +0100." <19981027233255.A1336@panke.de.freebsd.org> Date: Wed, 28 Oct 1998 12:19:30 +0100 Message-ID: <663.909573570@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to 10 and tell me if it works. Poul-Henning In message <19981027233255.A1336@panke.de.freebsd.org>, Wolfram Schneider write s: >I get randomly negative time errors during make world tests: >calcru: negative time of -695317300 usec for pid 6931 (cc1) >[...] >calcru: negative time of -695437148 usec for pid 9990 (test) >calcru: negative time of -592101957 usec for pid 20635 (cvsup) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 04:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23869 for freebsd-current-outgoing; Wed, 28 Oct 1998 04:06:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thor.KanServu.ca (thor.KanServU.ca [205.206.200.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23863 for ; Wed, 28 Oct 1998 04:06:43 -0800 (PST) (envelope-from sebulgin@kanservu.ca) Received: from thor.kanservu.ca (ts9p16.bmts.com [204.191.101.86]) by thor.KanServu.ca (8.8.5/8.8.5) with SMTP id GAA01668 for ; Wed, 28 Oct 1998 06:54:56 -0500 (EST) Message-Id: <3.0.6.32.19980827190448.0079e690@kanservu.ca> X-Sender: sebulgin@kanservu.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 27 Aug 1998 19:04:48 -0700 To: FreeBSD-current@FreeBSD.ORG From: Scott Bulgin Subject: Subscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 06:00:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02405 for freebsd-current-outgoing; Wed, 28 Oct 1998 06:00:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02400 for ; Wed, 28 Oct 1998 06:00:35 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from yggdrasil.ifi.uio.no (2602@yggdrasil.ifi.uio.no [129.240.64.182]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA23424; Wed, 28 Oct 1998 14:59:37 +0100 (MET) Received: (from dag-erli@localhost) by yggdrasil.ifi.uio.no ; Wed, 28 Oct 1998 14:59:36 +0100 (MET) Mime-Version: 1.0 To: Jay Nelson Cc: "Jordan K. Hubbard" , Brian Feldman , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 28 Oct 1998 14:59:35 +0100 In-Reply-To: Jay Nelson's message of "Mon, 26 Oct 1998 18:23:11 -0600 (CST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA02401 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jay Nelson writes: > -r-xr-xr-x 1 bin bin 307200 Oct 4 15:22 /bin/sh > -r-xr-xr-x 1 bin bin 167936 Mar 22 1998 /usr/local/bin/ksh That's not a fair comparison, since /bin/sh is statically linked while /usr/local/bin/ksh is probably dynamically linked. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 06:02:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02544 for freebsd-current-outgoing; Wed, 28 Oct 1998 06:02:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02536 for ; Wed, 28 Oct 1998 06:02:29 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from yggdrasil.ifi.uio.no (2602@yggdrasil.ifi.uio.no [129.240.64.182]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id PAA23804; Wed, 28 Oct 1998 15:01:34 +0100 (MET) Received: (from dag-erli@localhost) by yggdrasil.ifi.uio.no ; Wed, 28 Oct 1998 15:01:33 +0100 (MET) Mime-Version: 1.0 To: Brian Feldman Cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 28 Oct 1998 15:01:33 +0100 In-Reply-To: Brian Feldman's message of "Mon, 26 Oct 1998 19:37:34 -0500 (EST)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA02539 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > /bin/ksh. Now there's some _real_ disk space savings. Oh, and if I'm not > mistaken, ksh would allow us to remove -lalias from the boot.flp. What does libalias have to do with the shell? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 06:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05049 for freebsd-current-outgoing; Wed, 28 Oct 1998 06:36:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA05043; Wed, 28 Oct 1998 06:36:19 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: Mike Smith Cc: kent@iastate.edu, freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Notebook install References: <199810272000.MAA00830@dingo.cdrom.com> From: "Robert V. Baron" Date: 28 Oct 1998 09:35:34 -0500 In-Reply-To: Mike Smith's message of Tue, 27 Oct 1998 12:00:47 -0800 Message-ID: Lines: 15 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > For 10Mbps ethernet, almost anything NE2000 compatible, or the 3Com > 3c589. Modem cards almost all work fine. > One observation here. You can either use the zp0 driver for the 3c589 which will happen when you install and keep running with it. Or you can install with the zp0 and then cut over to pccard and friends and use the ep0 driver. In my experience, the zp0 driver is not stable under normal usage and will wedge. You need to ifconfig it up/down. The ep0 driver works. And a thought ... it would be nice if sysinstall made cutting over to the pccard scheme transparent. It would mimimally have to install a /etc/pccard.conf file and switch you to a PCCARD kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 07:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08152 for freebsd-current-outgoing; Wed, 28 Oct 1998 07:05:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hschpt06.hou.ucarb.com (hschpt06.hou.ucarb.com [144.68.7.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08147 for ; Wed, 28 Oct 1998 07:05:31 -0800 (PST) (envelope-from miker@hschpt06.hou.ucarb.com) Received: (from miker@localhost) by hschpt06.hou.ucarb.com (8.8.8/8.8.8) id JAA23194; Wed, 28 Oct 1998 09:02:57 -0600 (CST) (envelope-from mikenguyen@sprintmail.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <363658A9.FAD19060@gorean.org> Date: Wed, 28 Oct 1998 09:02:57 -0600 (CST) From: Mike Nguyen To: Studded , current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-98 Studded uttered: > Mike Nguyen wrote: >> >> On 27-Oct-98 Jeffrey J. Mountin uttered: >> > At 07:31 AM 10/27/98 -0500, Brian Feldman wrote: >> >>Let me repeat this once more: not a SINGLE script breaks with pdksh! >> > >> > Agreed, but on one of lists someone pointed out some other issues with >> > pdksh. This was quite a while back on -isp or -security. >> > >> > Korn is supposed to 100% bourne compatible. >> > >> > Coming from BSDi to FBSD, I was rather put out that I needed to install >> > it. >> > 8-) >> >> First thing I do when I install a new FreeBSD box is install the BSDi ksh >> binaries from the AT&T software reuse website as /bin/ksh. > > Do you have a URL for this? I'd love to give ksh a try. Doug, I got ksh93 from http://www.research.att.com/sw/tools/reuse/ It's statically linked so I can run it in single-user (and therefore as root's shell). Downside is that it's about twice as big as /bin/sh, and it isn't freeware (free for non-commercial use). Otherwise it's very nice. I think I got this URL (or it's predecessor, before the AT&T/Lucent split) from the -current list a long whiles back. It's the so called 'astkit'. For some reason, the BSDi binaries weren't at www.kornshell.com. What you want is the ast-base-98, which has binaries only for BSDi. I don't know what the difference is between that and ast-base-97, which is what is available for all other platforms. Mike. ------------------------------------------------------------------------------- Mike Nguyen - UNIX Sysadmin and Geek Pager (800) SKY-8888 pin# 1138368 or 1138368@skytel.com Your lucky number is 3552664958674928. Watch for it everywhere. ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 08:31:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16024 for freebsd-current-outgoing; Wed, 28 Oct 1998 08:31:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16011; Wed, 28 Oct 1998 08:31:37 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id LAA00990; Wed, 28 Oct 1998 11:30:43 -0500 (EST) (envelope-from lee) Message-ID: <19981028113037.A974@tidalwave.net> Date: Wed, 28 Oct 1998 11:30:37 -0500 From: Lee Cremeans To: Alfred Perlstein , lcremean@tidalwave.net, hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... Reply-To: lcremean@tidalwave.net References: <19981027200132.A977@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Wed, Oct 28, 1998 at 01:27:18AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 01:27:18AM -0500, Alfred Perlstein wrote: > > >From personal experiances with Acer i'd avoid them like the f'ing plague > > Took 2 tech support people over a week of daily contact before i bit the > bullet and manually guessed as to what jumpers where what on a > motherboard. > > One other time i needed jumper info, it only took 3 days of emailing > back and forth to get the sheets. > > After asking why it's not on thier site i was told "it's not something we > want the customer to mess with." We've had some bad problems with Acer America tech support here at work...a server we had blew up (it wasn't being used as a server at the time, thank god), and it took like 3 weeks and lots of BS to get it fixed. Acer Labs seems to be just as bad at providing tech specs on their chipsets as Acer Computer is at jumper setting. All the sites I went to either didn't have the sheet for the M1543, or had it locked behind a Username/Password box. It was only after writing to this list that I got the info I needed. As for the UDMA support, all the really dirty stuff (like handling data flow) has been done already, since all IDE DMA controllers are compatible with the Intel PIIX in that respect. I just have to program the chip to use UDMA mode...it should be done this weekend, barring any unforseen stopgaps. --- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 08:42:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17323 for freebsd-current-outgoing; Wed, 28 Oct 1998 08:42:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17316 for ; Wed, 28 Oct 1998 08:42:37 -0800 (PST) (envelope-from root@psa.at) Received: from uvo1-45.univie.ac.at ([131.130.231.45] helo=entropy.quake.at) by darkstar.psa.at with esmtp (Exim 2.05 #1) id 0zYYm4-0007gO-00 for freebsd-current@freebsd.org; Wed, 28 Oct 1998 17:48:45 +0100 Received: from localhost ([127.0.0.1]) by entropy.quake.at with esmtp (Exim 2.05 #1) id 0zYXuV-0000Ru-00 for freebsd-current@freebsd.org; Wed, 28 Oct 1998 16:53:23 +0100 Date: Wed, 28 Oct 1998 16:53:23 +0100 (CET) From: Alexander Sanda X-Sender: root@darkstar.vmx To: freebsd-current@FreeBSD.ORG Subject: Nestea fix on 3.0-* Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have running some systems, which I recently upgraded to 3.0-RELEASE. Everything is running fine, but I would feel more comfortable with a kernel not vulnerable to the Nestea (sp?) attack. So is it safe, to install a -current kernel on a 3.0-RELEASE system ? I mainly ask, because I noticed a lot of changes under src/sys recently. Or should I only checkout netinet/ip_input.c and recompile the kernel ? -- # /AS/ http://privat.schlund.de/entropy/ # # GNU is not Unix, BSD is. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 09:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20075 for freebsd-current-outgoing; Wed, 28 Oct 1998 09:09:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20068 for ; Wed, 28 Oct 1998 09:09:39 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA26788; Wed, 28 Oct 1998 12:08:53 -0500 (EST) (envelope-from wollman) Date: Wed, 28 Oct 1998 12:08:53 -0500 (EST) From: Garrett Wollman Message-Id: <199810281708.MAA26788@khavrinen.lcs.mit.edu> To: "Robert V. Baron" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Notebook install In-Reply-To: References: <199810272000.MAA00830@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > And a thought ... it would be nice if sysinstall made cutting over to > the pccard scheme transparent. It would mimimally have to install a > /etc/pccard.conf file and switch you to a PCCARD kernel. I don't think this will be an issue for the 3.1 release. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 09:42:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22509 for freebsd-current-outgoing; Wed, 28 Oct 1998 09:42:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles337.castles.com [208.214.167.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22478 for ; Wed, 28 Oct 1998 09:42:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03776; Wed, 28 Oct 1998 09:40:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810281740.JAA03776@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Erik H. Bakke" cc: "Wolfram Schneider" , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Wed, 28 Oct 1998 11:16:20 +0100." <002001be025c$19d4dd20$1401a8c0@server.habatech.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 09:40:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I get randomly negative time errors during make world tests: > >calcru: negative time of -695317300 usec for pid 6931 (cc1) > > > > > Are you using APM? It doesn't matter. He's using our currently buggy timer code. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 09:54:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23859 for freebsd-current-outgoing; Wed, 28 Oct 1998 09:54:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23854 for ; Wed, 28 Oct 1998 09:54:50 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.31]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6292 for ; Wed, 28 Oct 1998 18:54:05 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 28 Oct 1998 18:57:46 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Another compile error Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG install -c -o root -g wheel -m 644 drivers/make_device_driver.sh,v /usr/share/ex amples/drivers/make_device_driver.sh,v install -c -o root -g wheel -m 644 etc/Attic/ttys,v /usr/share/examples/etc/Atti c/ttys,v install: /usr/share/examples/etc/Attic/ttys,v: No such file or directory *** Error code 71 Am I wrong into thinking that Attic isn't needed for the example directory in /usr/share/examples/etc or am I just blabbering? =) If someone could at least enlighten me about Attic. Oh btw, I managed to solve the previous stop error. I simply needed to cp libl.a from /usr/lib to /usr/lib/aout and change the /etc/rc to point to /usr/lib/aout. HTH and thanks, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 09:58:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24135 for freebsd-current-outgoing; Wed, 28 Oct 1998 09:58:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24088 for ; Wed, 28 Oct 1998 09:57:55 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id SAA18221; Wed, 28 Oct 1998 18:55:53 +0100 (MET) Message-ID: <19981028185553.A18168@cons.org> Date: Wed, 28 Oct 1998 18:55:53 +0100 From: Martin Cracauer To: Brian Feldman , Studded Cc: =?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav?= , current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: <362B74B6.B9B256B4@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Brian Feldman on Sun, Oct 25, 1998 at 09:21:20AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Brian Feldman wrote: > Why don't we just use pdksh? It's even more compact than our current > Bourne/partially-Korn shell, and has lots of great Korn shell features > everyone loves but sh doesn't have. pdksh has a number of (IMHO) bugs with respect to signal handling. The problem here is "what happens when a sh child uses SIGINT and/or SIGQUIT intentionally, without using it as an indication that the user wants to exit?". I.e. emacs does this. In my opinion, and I'm going to prove it once I get through the Posix specs, the shell should abort a shell script only if a child exited with a signal exit status. In pdksh's opinion, a shell script is exited when a SIGINT was received while a child was running, no matter what the child does with it. Consider this script: #! /bin/sh emacs -nw /tmp/bla cp /tmp/bla ~/useful.txt emacs doesn't exit with signal status. If the user used C-g during his emacs session, pdksh will not execute the cp. If the user didn't hit C-g, pdksh will execute cp. Since C-g is a normal key in emacs and has nothing to do with exiting anything, this isn't useful behaviour. Our sh after the fixes BDE and me applied recently, will execute the cp in any case. The drawback of our behaviour is that chlients *must* exit with signal status on signals to abort the script. That means, if SIGINT or SIGQUIT is being chatched and the handler does some cleanup but will then exit instead of continuing the application, it has to kill itself. The FreeBSD build toolchain does this, but some ports fail, i.e. rsync. Nothingtheless our scheme is the only one that can truely support applications that use SIGINT and SIGQUIT for other purposes than exiting. Also, like bash pdksh fails to execute traps while a child that blocks signals is running. Consider this: #! /bin/sh trap 'echo aborting ; exit 1' 2 ./hardguy-that-blocks-sigint In bash and pdksh, the trap will be run *after* the blocking child exited, while in our sh it will run the trap immediatly. You strictly need this feature in system startup, where in /usr/local/etc/rc.d you will loose bedaly if you ever have a thing in startup that blocks signals, but hangs for some reason. You'll never get control back to the rest of the /etc/rc script if the shell executing it will execute traps only after the next child's exit. And I don't like that pdksh doesn't do . lib.sh if lib.sh is in the current directory, is not executable and '.' is not the $PATH. You have to use '. ./lib.sh' instead. I have to look up what Posix says, but this is counter-intuitive for me. For me, the file to read is not an executable, but something like a library, a config file, just a normal file and loading should follow file access rules ($PWD or absolute path), not executable loading rules ($PATH). I guess you will remark that this *is* in fact an exectable (at least potentially) and that an implicit '.' in whatever loading rules it follows causes the same problems as usual, so I hope POSIX is clear on the issue :-/ For me, using pdksh instead of ash is a primary reason why I thing that OpenBSD tends to solve problems with a big hammer too often. The same applies to pax vs. tar which has been exchanged before fixing the tar compatiblity mode. If you through away your shell and use a new one, you'll use a valuable resource: All the PRs collected over the years. For pdksh, you'll start from scratch, while the remaining problems in our sh are documented and me and Tor Egge (and BDE if something goes wrong) work on then from time to time. Maybe not enough, but I tend to say that volunteer situation is better than for many other parts of the system :-) For tests about proper sh and signal behaviour see http://www.freebsd.org/~cracauer/sh-sigint-testsuite/ Hope that helps. I don't think pdksh is a bad shell, but in my opinion FreeBSD is better served with ash for now. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 10:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26770 for freebsd-current-outgoing; Wed, 28 Oct 1998 10:24:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-pm3-02--090.sirius.net [205.134.231.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26751 for ; Wed, 28 Oct 1998 10:24:03 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id KAA15056 for ; Wed, 28 Oct 1998 10:22:45 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810281822.KAA15056@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Stupid ksh tricks [Was: Re: Changing sh for compatibility sake] In-reply-to: Your message of "Wed, 28 Oct 1998 09:02:57 CST." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 10:22:45 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A minor aside regarding some stupid ksh tricks... My fingers have gotten used to hitting TAB in bash for completing file names. I'd avoided pdksh only for this one reason. (Sad, I know.) I recently dug through the man-page for pdksh and discovered that adding these following lines: case "$KSH_VERSION" in *"PD KSH"*) bind '^I=complete' bind '^I^I=complete-list' ;; esac to my .kshrc (which is linked to .bashrc for me) and things work just fine. It's not *exactly* the same output, but it's pretty much the same behavior and so my fingers don't have to be retrained. I've switched over to pdksh now. I also have some ksh functions to mimic the csh/bash pushd/popd commands, so if anyone's interested in these, please let me know and I'll email my .kshrc or put it up for ftp. As an added bonus you also get a function for setting the title bar in several terminal emulators (xterm, hpterm, and Mac NCSA Telnet) to the current directory stack. -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 10:27:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27222 for freebsd-current-outgoing; Wed, 28 Oct 1998 10:27:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27037; Wed, 28 Oct 1998 10:26:41 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810281826.KAA27037@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLQ; Tue, 27 Oct 1998 19:42:54 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:37:02 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 10:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29814 for freebsd-current-outgoing; Wed, 28 Oct 1998 10:52:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from under.suspicion.org ([216.27.37.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29808 for ; Wed, 28 Oct 1998 10:52:26 -0800 (PST) (envelope-from ventrex@UNDER.suspicion.org) Received: from UNDER.SUSPICION.ORG (x0@UNDER.SUSPICION.ORG [216.27.37.14]) by under.suspicion.org (8.9.1/8.9.1) with ESMTP id NAA28309 for ; Wed, 28 Oct 1998 13:51:29 -0500 (EST) (envelope-from ventrex@UNDER.suspicion.org) Date: Wed, 28 Oct 1998 13:51:26 -0500 (EST) From: Thomas Stromberg X-Sender: ventrex@under.suspicion.org To: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Wed, 28 Oct 1998 13:50:07 -0500 (EST) From: Thomas Stromberg To: Mike Smith Subject: Re: calcru: negative time of -695317300 usec for pid When I put APM into my 3.0 kernel, I stopped getting the calcru messages and the core dumps associated with it.. ====================================================================== Thomas Stromberg, System Administrator @ RTCI | thomas@stromberg.org (919) 380-9771 ext. 3210 | //thomas.stromberg.org "the more we know, the less we are" | ====================================================================== On Wed, 28 Oct 1998, Mike Smith wrote: > > >I get randomly negative time errors during make world tests: > > >calcru: negative time of -695317300 usec for pid 6931 (cc1) > > > > > > > > > Are you using APM? > > It doesn't matter. He's using our currently buggy timer code. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 10:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29887 for freebsd-current-outgoing; Wed, 28 Oct 1998 10:53:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from sos@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29876; Wed, 28 Oct 1998 10:53:12 -0800 (PST) (envelope-from sos) Message-Id: <199810281853.KAA29876@hub.freebsd.org> Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: from Doug White at "Oct 27, 98 04:18:26 pm" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 28 Oct 1998 10:53:11 -0800 (PST) Cc: current@FreeBSD.ORG From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Doug White who wrote: > I have a mailing list of confused users who want to meet you. > > Please rebuild X without Kerberos; Kerberos is certainly *NOT* the common > case. Same holds for lots of the packages :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 11:17:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02611 for freebsd-current-outgoing; Wed, 28 Oct 1998 11:17:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02606 for ; Wed, 28 Oct 1998 11:17:28 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id NAA09326 for ; Wed, 28 Oct 1998 13:16:54 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <36376DA6.9E37121A@webwizard.org.mx> Date: Wed, 28 Oct 1998 13:16:54 -0600 From: Edwin Culp Reply-To: eculp@mexcom.net.mx X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Make Release with KERNFORMAT=elf Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did a make release and forgot to change my KERNFORMAT variable to aout and got the following results. text data bss dec hex filename 1444540 103344 112556 1660440 195618 kernel ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols kzip -v /R/stage/boot.std/kernel kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel < respective error and stop messages> Any time frame on the release kernel being elf? thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 11:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04144 for freebsd-current-outgoing; Wed, 28 Oct 1998 11:29:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04098; Wed, 28 Oct 1998 11:29:15 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA13785; Wed, 28 Oct 1998 21:28:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810281928.VAA13785@gratis.grondar.za> To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Wed, 28 Oct 1998 10:53:11 PST." <199810281853.KAA29876@hub.freebsd.org> References: <199810281853.KAA29876@hub.freebsd.org> Date: Wed, 28 Oct 1998 21:28:28 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wrote: > In reply to Doug White who wrote: > > I have a mailing list of confused users who want to meet you. > > > > Please rebuild X without Kerberos; Kerberos is certainly *NOT* the common > > case. > > Same holds for lots of the packages :( The problem is obly on one machine; the port-builder. That one clearly has KerberosIV (eBones) enabled, and the X is Kerberos-enabled. As a consequence, all X-ports are Kerberos-enabled. Fix 1 thing, fix'em all. What machine is used to build all the ports? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 12:10:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11979 for freebsd-current-outgoing; Wed, 28 Oct 1998 12:10:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11971 for ; Wed, 28 Oct 1998 12:10:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00408; Wed, 28 Oct 1998 12:08:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282008.MAA00408@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eculp@mexcom.net.mx cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Wed, 28 Oct 1998 13:16:54 CST." <36376DA6.9E37121A@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 12:08:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just did a make release and forgot to change my KERNFORMAT variable to > aout and got the following results. > > text data bss dec hex filename > 1444540 103344 112556 1660440 195618 kernel > ./dumpnlist /R/stage/boot.std/kernel > > /tmp/mnt_xx/stand/symbols > kzip -v /R/stage/boot.std/kernel > kzip: bad magic in file /R/stage/boot.std/kernel, probably > not a kernel > < respective error and stop messages> > > Any time frame on the release kernel being elf? When we do the default cutover to ELF kernels. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 12:39:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15630 for freebsd-current-outgoing; Wed, 28 Oct 1998 12:39:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15602; Wed, 28 Oct 1998 12:39:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00616; Wed, 28 Oct 1998 12:37:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282037.MAA00616@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-reply-to: Your message of "Wed, 28 Oct 1998 21:28:28 +0200." <199810281928.VAA13785@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 12:37:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is obly on one machine; the port-builder. That one clearly > has KerberosIV (eBones) enabled, and the X is Kerberos-enabled. As > a consequence, all X-ports are Kerberos-enabled. > > Fix 1 thing, fix'em all. What machine is used to build all the ports? Bento was used this time around. I think Justin is probably feeling pretty embarrassed about now. Ouch. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 13:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22061 for freebsd-current-outgoing; Wed, 28 Oct 1998 13:37:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22055 for ; Wed, 28 Oct 1998 13:37:03 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA28006; Wed, 28 Oct 1998 13:36:03 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: eculp@mexcom.net.mx, "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Wed, 28 Oct 1998 12:08:50 PST." <199810282008.MAA00408@dingo.cdrom.com> Date: Wed, 28 Oct 1998 13:36:02 -0800 Message-ID: <28002.909610562@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Any time frame on the release kernel being elf? > > When we do the default cutover to ELF kernels. Though we could always substitute kzip for gzip now, I guess. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 13:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23087 for freebsd-current-outgoing; Wed, 28 Oct 1998 13:44:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23082 for ; Wed, 28 Oct 1998 13:44:17 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA25322 for ; Wed, 28 Oct 1998 22:49:38 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 28 Oct 1998 22:49:38 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: MFS_ROOT is broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is with latest sources as well - I confirm the report below. This is with MFS compiled in kernel and used as root. The only thing that comes to my mind are recent changes in /sys/i386/i386 to remove references to bdevsw... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- ---------- Forwarded message ---------- Date: Mon, 26 Oct 1998 17:48:34 -0800 (PST) From: Robert Schulhof To: abial@nask.pl Subject: PicoBSD panic Hello, I am trying to make the router version of PicoBSD that I cvsupped today. The build is fine, but when I boot from the floppy, I get: mfs_mountroot : can't find rootvperror 6: panic cannot mount root (2) Am I doing something wrong? I would also like to let you know that I am very interested in your work and would like to offer any help. Best regards, Rob Robert Schulhof UNIX System Administrator LanMinds Internet. (LMI Net) rrs@lmi.net http://www.lmi.net (510) 843-6389 VOX (510) 843-6390 FAX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 14:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28259 for freebsd-current-outgoing; Wed, 28 Oct 1998 14:52:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28251 for ; Wed, 28 Oct 1998 14:52:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00752; Wed, 28 Oct 1998 14:49:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282249.OAA00752@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Mike Smith , eculp@mexcom.net.mx, "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Wed, 28 Oct 1998 13:36:02 PST." <28002.909610562@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 14:49:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Any time frame on the release kernel being elf? > > > > When we do the default cutover to ELF kernels. > > Though we could always substitute kzip for gzip now, I guess. I'm not following you here. You can't use kzip on an ELF kernel, so if we cut over to an ELF kernel for the install, you have to gzip it and use the new loader. This will probably push us to the two-disk install. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 15:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29715 for freebsd-current-outgoing; Wed, 28 Oct 1998 15:05:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29709 for ; Wed, 28 Oct 1998 15:05:44 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA01886; Wed, 28 Oct 1998 15:04:55 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: eculp@mexcom.net.mx, "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Wed, 28 Oct 1998 14:49:45 PST." <199810282249.OAA00752@dingo.cdrom.com> Date: Wed, 28 Oct 1998 15:04:55 -0800 Message-ID: <1882.909615895@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not following you here. You can't use kzip on an ELF kernel, so if > we cut over to an ELF kernel for the install, you have to gzip it and > use the new loader. This will probably push us to the two-disk install. I'm suggesting that we eventually go to gzip for all kernels and use the new loader with a loader script, yes. As far as it all fitting on one floppy, I wouldn't write that off just yet. The gzip'd kernel is about the same size and the loader is 80K, something which could possibly also be built in a "stripped down" configuration. It's nothing I'd want to do immediately, but I think it might be possible with a little sweat. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00731 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:10:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00721 for ; Wed, 28 Oct 1998 17:10:12 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id SAA15302; Wed, 28 Oct 1998 18:20:26 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id SAA04627; Wed, 28 Oct 1998 18:19:24 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Wed, 28 Oct 1998 18:19:24 -0600 (CST) From: Jay Nelson To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For completness: FreeBSD 2.2.7-STABLE #0: Sat Oct 17 13:26:42 CDT 1998 -r-xr-xr-x 1 bin bin 307200 Oct 4 15:22 /bin/sh -r-xr-xr-x 1 bin bin 286720 Oct 28 18:09 /usr/local/bin/ksh /usr/local/bin/ksh: FreeBSD/i386 compact demand paged executable FreeBSD 3.0-BETA #11: Sat Oct 17 14:17:23 CDT 1998 -r-xr-xr-x 1 root wheel 321104 Oct 4 01:47 /bin/sh -r-xr-xr-x 1 root wheel 297440 Sep 26 20:10 /usr/local/bin/ksh /usr/local/bin/ksh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped Thanks for pointing out the dynamic linking. I didn't realize it was and have corrected that. -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:10:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00748 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:10:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00727 for ; Wed, 28 Oct 1998 17:10:14 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id SAA15283; Wed, 28 Oct 1998 18:00:28 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with ESMTP id RAA00663; Wed, 28 Oct 1998 17:49:50 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Wed, 28 Oct 1998 17:49:50 -0600 (CST) From: Jay Nelson To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops -- you're right. Sorry for the noise. -- Jay On 28 Oct 1998, Dag-Erling C. Smørgrav wrote: >Jay Nelson writes: >> -r-xr-xr-x 1 bin bin 307200 Oct 4 15:22 /bin/sh >> -r-xr-xr-x 1 bin bin 167936 Mar 22 1998 /usr/local/bin/ksh > >That's not a fair comparison, since /bin/sh is statically linked while >/usr/local/bin/ksh is probably dynamically linked. > >DES >-- >Dag-Erling Smørgrav - dag-erli@ifi.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01609 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:15:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-pm3-02--072.sirius.net [205.134.231.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01590 for ; Wed, 28 Oct 1998 17:15:17 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id RAA20993; Wed, 28 Oct 1998 17:01:53 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810290101.RAA20993@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jeffrey J. Mountin" cc: current@FreeBSD.ORG Subject: Re: Stupid ksh tricks [Was: Re: Changing sh for compatibility sake] In-reply-to: Your message of "Wed, 28 Oct 1998 18:00:06 CST." <3.0.3.32.19981028180006.00f404c4@207.227.119.2> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 17:01:53 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Why not do 'set -o vi' followed by 'set -o vi-tabcomplete' and all is well. Because I like to run the shell in emacs mode. >Are you sure it needs to mimic them? Don't know bash, but ksh does have >pushd/popd and it is supposed to be similar to csh's, which I don't do either. pdksh doesn't seem to have pushd/popd built-in. If ksh does, it's a recent addition as the AT&T ksh I'm used to from long-ago days at HP certainly didn't have it. >Might suggest O'Reilly's "Learning the Korn Shell" since the man pages >don't cover everything. I'd rather fix the pdksh man-page, but I suspect it's accurate. :-) -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01628 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:15:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-pm3-02--072.sirius.net [205.134.231.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01602 for ; Wed, 28 Oct 1998 17:15:20 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id QAA20847; Wed, 28 Oct 1998 16:57:31 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810290057.QAA20847@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: tjm@codegen.com, eric@needhams.com Subject: Mod to doscmd's port.c to directly access parallel ports X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 16:57:31 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just acquired a Needhams EMP-10 EPROM programmer and wanted to run it directly under FreeBSD 3.0-CURRENT. So I modified doscmd's port.c to let me run the Needham DOS software which wants direct access to a parallel port. I needed the following patch to let me access the real I/O ports from the emulator to get to the parallel port. With this patch, I can run "doscmd -x -b -i0x378:8 -o0x378:8" as root, connect up the EMP-10, and the Needhams software directly accesses the parallel port from the DOS emulator window. Nice! Would someone who knows this stuff better than me (not difficult) check the mod for me, and if it's sane, please check it in? Thanks! -- Parag Index: port.c =================================================================== RCS file: /src/freebsd/src/usr.bin/doscmd/port.c,v retrieving revision 1.1 diff -c -r1.1 port.c *** port.c 1997/08/09 01:42:54 1.1 --- port.c 1998/10/29 00:48:31 *************** *** 59,73 **** static void iomap(int port, int cnt) { ! fatal("iomap not supported"); } static void iounmap(int port, int cnt) { ! fatal("iomap not supported"); } - #else static void iomap(int port, int cnt) --- 59,88 ---- static void iomap(int port, int cnt) { ! if (port + cnt >= MAXPORT) { ! errno = ERANGE; ! goto bad; ! } ! if (i386_set_ioperm(port, cnt, 1) < 0) { ! bad: ! perror("iomap"); ! quit(1); ! } } static void iounmap(int port, int cnt) { ! if (port + cnt >= MAXPORT) { ! errno = ERANGE; ! goto bad; ! } ! if (i386_set_ioperm(port, cnt, 1) < 0) { ! bad: ! perror("iounmap"); ! quit(1); ! } } #else static void iomap(int port, int cnt) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01840 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:16:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01833 for ; Wed, 28 Oct 1998 17:16:38 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id BAA12045; Thu, 29 Oct 1998 01:15:06 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id AAA22601; Thu, 29 Oct 1998 00:18:49 +0100 (CET) (envelope-from andreas) Message-ID: <19981029001848.A22320@klemm.gtn.com> Date: Thu, 29 Oct 1998 00:18:48 +0100 From: Andreas Klemm To: Thomas Seidmann , current@FreeBSD.ORG Subject: Re: IPv6 in -current References: <3635F22D.1A6B9EB4@simultan.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3635F22D.1A6B9EB4@simultan.ch>; from Thomas Seidmann on Tue, Oct 27, 1998 at 05:17:49PM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 27, 1998 at 05:17:49PM +0100, Thomas Seidmann wrote: > Please let me know what you think. If there is a more appropriate way of > doing what I want to do, I'd be thankful for hints. In fact, I could > start with the integration next week. There has been a discussion about that some months ago on the freebsd net mailinglist if this helps. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:25:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03206 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:25:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from badlans.lanminds.com (badlans.lanminds.com [208.25.91.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03177 for ; Wed, 28 Oct 1998 17:25:29 -0800 (PST) (envelope-from rrs@badlans.lanminds.com) Received: (from rrs@localhost) by badlans.lanminds.com (8.8.6/8.8.6) id RAA13997; Wed, 28 Oct 1998 17:26:51 -0800 (PST) Date: Wed, 28 Oct 1998 17:26:51 -0800 (PST) From: Robert Schulhof Message-Id: <199810290126.RAA13997@badlans.lanminds.com> To: mike@smith.net.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: MFS_ROOT and picobsd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike, You're right. The problem is in the check on the block device. I was stupid and just decided to modify bdevvp in kern/vfs_ops.c as follows: - if (dev == NODEV || major(dev) >= nblkdev || - bdevsw[major(dev)] == NULL) { *vpp = NULLVP; return (ENXIO); } + if (dev == NODEV ) { *vpp = NULLVP; return (ENXIO); } This solved my problem with MFS_ROOT mount panics, but I don't know the kernel code well and this is just a bandaid. Thanks! Rob Robert Schulhof UNIX System Administrator LanMinds Internet. (LMI Net) rrs@lmi.net http://www.lmi.net (510) 843-6389 VOX (510) 843-6390 FAX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:30:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04368 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:30:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04317 for ; Wed, 28 Oct 1998 17:30:41 -0800 (PST) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id QAA23229 for ; Wed, 28 Oct 1998 16:36:40 -0800 (PST) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981028163458.00a11c60@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 16:36:39 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: DSL ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quick question Does anybody have any experience using PacBell DSL with FreeBSD ? Thanks Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 17:34:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05422 for freebsd-current-outgoing; Wed, 28 Oct 1998 17:34:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net ([207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05409 for ; Wed, 28 Oct 1998 17:34:50 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA23404; Wed, 28 Oct 1998 18:01:04 -0600 (CST) Received: from harkol-76.isdn.mke.execpc.com(169.207.64.204) by peak.mountin.net via smap (V1.3) id sma023402; Wed Oct 28 18:00:50 1998 Message-Id: <3.0.3.32.19981028180006.00f404c4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 28 Oct 1998 18:00:06 -0600 To: Parag Patel , current@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Stupid ksh tricks [Was: Re: Changing sh for compatibility sake] In-Reply-To: <199810281822.KAA15056@pinhead.parag.codegen.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:22 AM 10/28/98 -0800, Parag Patel wrote: > >A minor aside regarding some stupid ksh tricks... > >My fingers have gotten used to hitting TAB in bash for completing file names. I'd avoided pdksh only for this one reason. (Sad, I know.) > >I recently dug through the man-page for pdksh and discovered that adding these following lines: > > case "$KSH_VERSION" in > *"PD KSH"*) > bind '^I=complete' > bind '^I^I=complete-list' > ;; > esac > >to my .kshrc (which is linked to .bashrc for me) and things work just fine. It's not *exactly* the same output, but it's pretty much the same behavior and so my fingers don't have to be retrained. I've switched over to pdksh now. Why not do 'set -o vi' followed by 'set -o vi-tabcomplete' and all is well. >I also have some ksh functions to mimic the csh/bash pushd/popd commands, so if anyone's interested in these, please let me know and I'll email my .kshrc or put it up for ftp. Are you sure it needs to mimic them? Don't know bash, but ksh does have pushd/popd and it is supposed to be similar to csh's, which I don't do either. Might suggest O'Reilly's "Learning the Korn Shell" since the man pages don't cover everything. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11225 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:09:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11218 for ; Wed, 28 Oct 1998 18:09:27 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id UAA13367; Wed, 28 Oct 1998 20:09:23 -0600 (CST) From: Kevin Day Message-Id: <199810290209.UAA13367@home.dragondata.com> Subject: Re: Mod to doscmd's port.c to directly access parallel ports In-Reply-To: <199810290057.QAA20847@pinhead.parag.codegen.com> from Parag Patel at "Oct 28, 98 04:57:31 pm" To: parag@cgt.com (Parag Patel) Date: Wed, 28 Oct 1998 20:09:23 -0600 (CST) Cc: current@FreeBSD.ORG, tjm@codegen.com, eric@needhams.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I just acquired a Needhams EMP-10 EPROM programmer and wanted to run it > directly under FreeBSD 3.0-CURRENT. > > So I modified doscmd's port.c to let me run the Needham DOS software > which wants direct access to a parallel port. I needed the following > patch to let me access the real I/O ports from the emulator to get to > the parallel port. > > With this patch, I can run "doscmd -x -b -i0x378:8 -o0x378:8" as root, > connect up the EMP-10, and the Needhams software directly accesses the > parallel port from the DOS emulator window. Nice! > > Would someone who knows this stuff better than me (not difficult) check > the mod for me, and if it's sane, please check it in? Thanks! > > > -- Parag > I ended up using something similar to run the EMP-10 on freebsd, but be careful. the device is extremely sensitive to timings. (especially when programming EPROMs... flash isn't so bad). Either nice it to -20, or diddle with rtprio. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12402 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:17:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12382 for ; Wed, 28 Oct 1998 18:17:17 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA08846; Wed, 28 Oct 1998 21:17:03 -0500 (EST) Date: Wed, 28 Oct 1998 21:17:02 -0500 (EST) From: Brian Feldman To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: Changing sh for compatibility sake In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id SAA12394 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Haha, sorry, I mean -ledit *thwaps himself* Brian Feldman On 28 Oct 1998, Dag-Erling C. Smørgrav wrote: > Brian Feldman writes: > > /bin/ksh. Now there's some _real_ disk space savings. Oh, and if I'm not > > mistaken, ksh would allow us to remove -lalias from the boot.flp. > > What does libalias have to do with the shell? > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:20:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13006 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:20:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail (needhams.quiknet.com [207.183.237.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA12983 for ; Wed, 28 Oct 1998 18:20:14 -0800 (PST) (envelope-from eric@needhams.com) Received: from needhams.com by mail with smtp (Smail3.1.29.1 #3) id m0zYhf0-00093oC; Wed, 28 Oct 98 18:18 PST Message-ID: <3637D059.80889AB6@needhams.com> Date: Wed, 28 Oct 1998 18:18:01 -0800 From: Eric Cox X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Parag Patel CC: current@FreeBSD.ORG, tjm@codegen.com Subject: Re: Mod to doscmd's port.c to directly access parallel ports References: <199810290057.QAA20847@pinhead.parag.codegen.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Parag! I don't know that much about FreeBSD (the only thing I've done on FreeBSD is setup a news feeder), but it looks to me like i386_set_ioperm is being called with the same parameters under iomap or iounmap (i.e. the two calls are the same, functionally). For all I know this is the way it's supposed to be - just caught my eye. Thanks (!) for your help on this. I'll have to try this at home, and if successful, I'll stick it up on the website... Eric Parag Patel wrote: > I just acquired a Needhams EMP-10 EPROM programmer and wanted to run it > directly under FreeBSD 3.0-CURRENT. > > So I modified doscmd's port.c to let me run the Needham DOS software > which wants direct access to a parallel port. I needed the following > patch to let me access the real I/O ports from the emulator to get to > the parallel port. > > With this patch, I can run "doscmd -x -b -i0x378:8 -o0x378:8" as root, > connect up the EMP-10, and the Needhams software directly accesses the > parallel port from the DOS emulator window. Nice! > > Would someone who knows this stuff better than me (not difficult) check > the mod for me, and if it's sane, please check it in? Thanks! > > -- Parag > > Index: port.c > =================================================================== > RCS file: /src/freebsd/src/usr.bin/doscmd/port.c,v > retrieving revision 1.1 > diff -c -r1.1 port.c > *** port.c 1997/08/09 01:42:54 1.1 > --- port.c 1998/10/29 00:48:31 > *************** > *** 59,73 **** > static void > iomap(int port, int cnt) > { > ! fatal("iomap not supported"); > } > > static void > iounmap(int port, int cnt) > { > ! fatal("iomap not supported"); > } > - > #else > static void > iomap(int port, int cnt) > --- 59,88 ---- > static void > iomap(int port, int cnt) > { > ! if (port + cnt >= MAXPORT) { > ! errno = ERANGE; > ! goto bad; > ! } > ! if (i386_set_ioperm(port, cnt, 1) < 0) { > ! bad: > ! perror("iomap"); > ! quit(1); > ! } > } > > static void > iounmap(int port, int cnt) > { > ! if (port + cnt >= MAXPORT) { > ! errno = ERANGE; > ! goto bad; > ! } > ! if (i386_set_ioperm(port, cnt, 1) < 0) { > ! bad: > ! perror("iounmap"); > ! quit(1); > ! } > } > #else > static void > iomap(int port, int cnt) -- NEEDHAM'S ELECTRONICS : (916) 924-8037 (Voice) Device Programmers : (916) 924-8065 (Fax) 4630 Beloit Drive, #20 : (916) 924-8094 (BBS) Sacramento, CA 95838 : http://www.needhams.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13435 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:23:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13428 for ; Wed, 28 Oct 1998 18:23:42 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA20121; Wed, 28 Oct 1998 18:23:44 -0800 (PST) Message-ID: <19981028182343.D14495@Alameda.net> Date: Wed, 28 Oct 1998 18:23:43 -0800 From: Ulf Zimmermann To: Manfred Antar , current@FreeBSD.ORG Subject: Re: DSL ? Reply-To: ulf@Alameda.net References: <4.1.19981028163458.00a11c60@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <4.1.19981028163458.00a11c60@192.168.0.1>; from Manfred Antar on Wed, Oct 28, 1998 at 04:36:39PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 04:36:39PM -0800, Manfred Antar wrote: > Quick question > Does anybody have any experience using PacBell DSL with FreeBSD ? No, but I haven't heard the best in general about PacHell and their service. (That includes me as a ISP customer of PacHell Telco). How about using an ISP who runs on FreeBSD for DSL feed ? ;-) > Thanks > Manfred > ============================== > || mantar@netcom.com || > || pozo@infinex.com || > || Ph. (415) 681-6235 || > ============================== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14610 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:32:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14605 for ; Wed, 28 Oct 1998 18:32:28 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA09055; Wed, 28 Oct 1998 21:32:09 -0500 (EST) Date: Wed, 28 Oct 1998 21:32:08 -0500 (EST) From: Brian Feldman To: Parag Patel cc: current@FreeBSD.ORG Subject: Re: Stupid ksh tricks [Was: Re: Changing sh for compatibility sake] In-Reply-To: <199810281822.KAA15056@pinhead.parag.codegen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG set -o vi-tabcomplete -Brian Feldman On Wed, 28 Oct 1998, Parag Patel wrote: > > A minor aside regarding some stupid ksh tricks... > > My fingers have gotten used to hitting TAB in bash for completing file names. I'd avoided pdksh only for this one reason. (Sad, I know.) > > I recently dug through the man-page for pdksh and discovered that adding these following lines: > > case "$KSH_VERSION" in > *"PD KSH"*) > bind '^I=complete' > bind '^I^I=complete-list' > ;; > esac > > to my .kshrc (which is linked to .bashrc for me) and things work just fine. It's not *exactly* the same output, but it's pretty much the same behavior and so my fingers don't have to be retrained. I've switched over to pdksh now. > > I also have some ksh functions to mimic the csh/bash pushd/popd commands, so if anyone's interested in these, please let me know and I'll email my .kshrc or put it up for ftp. > > As an added bonus you also get a function for setting the title bar in several terminal emulators (xterm, hpterm, and Mac NCSA Telnet) to the current directory stack. > > > -- Parag > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14670 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:33:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14664 for ; Wed, 28 Oct 1998 18:33:31 -0800 (PST) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id SAA19138; Wed, 28 Oct 1998 18:33:19 -0800 (PST) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981028183238.00a108a0@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 18:33:19 -0800 To: ulf@Alameda.net, current@FreeBSD.ORG From: Manfred Antar Subject: Re: DSL ? In-Reply-To: <19981028182343.D14495@Alameda.net> References: <4.1.19981028163458.00a11c60@192.168.0.1> <4.1.19981028163458.00a11c60@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:23 PM 10/28/98 -0800, Ulf Zimmermann wrote: >On Wed, Oct 28, 1998 at 04:36:39PM -0800, Manfred Antar wrote: >> Quick question >> Does anybody have any experience using PacBell DSL with FreeBSD ? > >No, but I haven't heard the best in general about PacHell and their >service. (That includes me as a ISP customer of PacHell Telco). > >How about using an ISP who runs on FreeBSD for DSL feed ? ;-) > I'll do some searching for a local one (S.F) Thanks Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 18:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16952 for freebsd-current-outgoing; Wed, 28 Oct 1998 18:48:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16929 for ; Wed, 28 Oct 1998 18:48:10 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA09223; Wed, 28 Oct 1998 21:47:30 -0500 (EST) Date: Wed, 28 Oct 1998 21:47:30 -0500 (EST) From: Brian Feldman To: "Jordan K. Hubbard" cc: Mike Smith , eculp@mexcom.net.mx, "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-Reply-To: <28002.909610562@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What bootloader handles the gzip format? BTX I guess, since libstand has zipfs.... but then again, what about the floppy that can't fit BTX, only the standard bootblocks? My opinion is kzip should leave, but only when something better comes along. I'll look at how small a bare-bones gunzip can be. Brian Feldman On Wed, 28 Oct 1998, Jordan K. Hubbard wrote: > > > Any time frame on the release kernel being elf? > > > > When we do the default cutover to ELF kernels. > > Though we could always substitute kzip for gzip now, I guess. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 19:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20845 for freebsd-current-outgoing; Wed, 28 Oct 1998 19:25:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20827 for ; Wed, 28 Oct 1998 19:25:20 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id LAA03677; Thu, 29 Oct 1998 11:23:31 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810290323.LAA03677@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: "Jordan K. Hubbard" , Mike Smith , eculp@mexcom.net.mx, "freebsd-current@FreeBSD.ORG" Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Wed, 28 Oct 1998 21:47:30 EST." Date: Thu, 29 Oct 1998 11:23:31 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > What bootloader handles the gzip format? BTX I guess, since libstand has > zipfs.... but then again, what about the floppy that can't fit BTX, only > the standard bootblocks? My opinion is kzip should leave, but only when > something better comes along. I'll look at how small a bare-bones gunzip > can be. The new bootloader handles gzip "just fine". As far as size goes, that's the eternal problem. There are other ways around this. The bootloader supports loading components, so there's no dire need to have a huge GENERIC kernel on the floppy containing all the drivers one could ever want. We could build a much smaller kernel that contains the most popular drivers and has the rest loaded via PCI or PnP id matching, either from floppy or the install media. Mike is working this sort of thing now it seems. The odds are pretty good that we will eventually be able to have a boot floppy containing *nothing* but the boot loader. It'll load or build a kernel from cdrom, ftp, http, tftp, nfs, dosfs, etc. > Brian Feldman > > On Wed, 28 Oct 1998, Jordan K. Hubbard wrote: > > > > > Any time frame on the release kernel being elf? > > > > > > When we do the default cutover to ELF kernels. > > > > Though we could always substitute kzip for gzip now, I guess. > > > > - Jordan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 20:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29548 for freebsd-current-outgoing; Wed, 28 Oct 1998 20:41:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29531 for ; Wed, 28 Oct 1998 20:41:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id UAA28414; Wed, 28 Oct 1998 20:40:53 -0800 Date: Wed, 28 Oct 1998 20:40:53 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Ulf Zimmermann cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: DSL ? In-Reply-To: <19981028182343.D14495@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG LANMINDS (http://www.lanminds.com) does a DSL coinstall with Covad- they run some BSDI machines, but also some FreeBSD machines too I believe. There certainly is at least one person there keenly interested in FreeBSD. As an ISP they do a pretty decent job. I've had some difficulties with the DSL install, but I consider myself really an edge case and would still give them a 'recommend' rating. The basic hookup gets you a DSL router/modem- so it's not really germane to a *BSD or Linux or Solaris or what have you kind of OS issue, except that for most cases IPNAT is your friend and I gather FreeBSD has that fairly well in hand. I've heard some negative experiences with IPNAT under FreeBSD and PacBELL's DSL hookup, but the person reporting that to me wasn't entirely clear what the issue was- I believe that there might have been some unfriendly router filtering on http proxy responses, but I really don't have the details. FWIW -matt On Wed, 28 Oct 1998, Ulf Zimmermann wrote: > On Wed, Oct 28, 1998 at 04:36:39PM -0800, Manfred Antar wrote: > > Quick question > > Does anybody have any experience using PacBell DSL with FreeBSD ? > > No, but I haven't heard the best in general about PacHell and their > service. (That includes me as a ISP customer of PacHell Telco). > > How about using an ISP who runs on FreeBSD for DSL feed ? ;-) > > > Thanks > > Manfred > > ============================== > > || mantar@netcom.com || > > || pozo@infinex.com || > > || Ph. (415) 681-6235 || > > ============================== > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 20:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29798 for freebsd-current-outgoing; Wed, 28 Oct 1998 20:43:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29783 for ; Wed, 28 Oct 1998 20:43:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id UAA28431; Wed, 28 Oct 1998 20:43:11 -0800 Date: Wed, 28 Oct 1998 20:43:11 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Manfred Antar cc: ulf@Alameda.net, current@FreeBSD.ORG Subject: Re: DSL ? In-Reply-To: <4.1.19981028183238.00a108a0@192.168.0.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, btw, LanMind's and Covad's service area includes SF (feral.com is physically down on 3rd street). Make sure you ask them 3 times for sure about what data rates that are possible for how far you are from the Central Office - and use a phone number along with your addresss that *matches* the address because they use that to figure out where your Central Office is... On Wed, 28 Oct 1998, Manfred Antar wrote: > At 06:23 PM 10/28/98 -0800, Ulf Zimmermann wrote: > >On Wed, Oct 28, 1998 at 04:36:39PM -0800, Manfred Antar wrote: > >> Quick question > >> Does anybody have any experience using PacBell DSL with FreeBSD ? > > > >No, but I haven't heard the best in general about PacHell and their > >service. (That includes me as a ISP customer of PacHell Telco). > > > >How about using an ISP who runs on FreeBSD for DSL feed ? ;-) > > > I'll do some searching for a local one (S.F) > Thanks > Manfred > ============================== > || mantar@netcom.com || > || pozo@infinex.com || > || Ph. (415) 681-6235 || > ============================== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 21:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03650 for freebsd-current-outgoing; Wed, 28 Oct 1998 21:25:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03644; Wed, 28 Oct 1998 21:25:34 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id IAA18843; Thu, 29 Oct 1998 08:25:25 +0300 (MSK) (envelope-from ache) Message-ID: <19981029082524.A16434@nagual.pp.ru> Date: Thu, 29 Oct 1998 08:25:24 +0300 From: "Andrey A. Chernov" To: jdp@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: FreeBSD_cc_... Mail-Followup-To: jdp@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, why you choose to have such complex bitfielding-like thing in one variable? It is too difficult to compare with it. Imagine that next time GNU will issue release something like 2.7.2.1.12345, what happens with your cdefs.h checking then? Better way just put FreeBSD extensions version in separate variable without tracking GNU version at all. GNU compiler presence can be checked with __GNUC__ predefined variable separately. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 21:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04479 for freebsd-current-outgoing; Wed, 28 Oct 1998 21:36:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04471 for ; Wed, 28 Oct 1998 21:36:07 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id VAA29610; Wed, 28 Oct 1998 21:36:01 -0800 (PST) (envelope-from jdp) Message-Id: <199810290536.VAA29610@austin.polstra.com> To: "Andrey A. Chernov" cc: current@FreeBSD.ORG Subject: Re: FreeBSD_cc_... In-reply-to: Your message of "Thu, 29 Oct 1998 08:25:24 +0300." <19981029082524.A16434@nagual.pp.ru> Date: Wed, 28 Oct 1998 21:36:01 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John, why you choose to have such complex bitfielding-like thing > in one variable? It is too difficult to compare with it. Imagine > that next time GNU will issue release something like 2.7.2.1.12345, > what happens with your cdefs.h checking then? Better way just put > FreeBSD extensions version in separate variable without tracking GNU > version at all. GNU compiler presence can be checked with __GNUC__ > predefined variable separately. I wanted the variable to be self-contained, and interpretable without the context of __GNUC__ and __GNUC_MINOR__. That simplifies the #ifs, because it allows the use of just one comparison instead of several. If you look at you'll see what a mess results from needing to check several variables. We already do a similar thing with and __FreeBSD_version. I think it's pretty unlikely that GNU will release a version with a 5-component revision number. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 21:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05779 for freebsd-current-outgoing; Wed, 28 Oct 1998 21:45:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05680; Wed, 28 Oct 1998 21:45:31 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id HAA15428; Thu, 29 Oct 1998 07:44:32 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810290544.HAA15428@gratis.grondar.za> To: Mike Smith cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Wed, 28 Oct 1998 12:37:51 PST." <199810282037.MAA00616@dingo.cdrom.com> References: <199810282037.MAA00616@dingo.cdrom.com> Date: Thu, 29 Oct 1998 07:44:31 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > The problem is obly on one machine; the port-builder. That one clearly > > has KerberosIV (eBones) enabled, and the X is Kerberos-enabled. As > > a consequence, all X-ports are Kerberos-enabled. > > > > Fix 1 thing, fix'em all. What machine is used to build all the ports? > > Bento was used this time around. I think Justin is probably feeling > pretty embarrassed about now. Ouch. I'm busy dekerberising that box... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 21:55:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06925 for freebsd-current-outgoing; Wed, 28 Oct 1998 21:55:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06920 for ; Wed, 28 Oct 1998 21:55:28 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA01776; Wed, 28 Oct 1998 23:55:24 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id XAA11789; Wed, 28 Oct 1998 23:46:09 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13880.289.190601.379232@zuhause.zuhause.mn.org> Date: Wed, 28 Oct 1998 23:46:09 -0600 (CST) To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: DSL ? In-Reply-To: <4.1.19981028163458.00a11c60@192.168.0.1> References: <4.1.19981028163458.00a11c60@192.168.0.1> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Manfred Antar writes: > Quick question > Does anybody have any experience using PacBell DSL with FreeBSD ? I don't have any experience with DSL yet, but in the case of US West's DSL offerings in Minnesota, the DSL "modem" is really a ethernet <-> ATM bridge. I picked up a $50 486 box to be my router (with FreeBSD, of course) when I get DSL installed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 22:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11711 for freebsd-current-outgoing; Wed, 28 Oct 1998 22:49:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11706 for ; Wed, 28 Oct 1998 22:49:57 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA01276; Wed, 28 Oct 1998 22:49:57 -0800 (PST) Message-ID: <19981028224957.A1241@Alameda.net> Date: Wed, 28 Oct 1998 22:49:57 -0800 From: Ulf Zimmermann To: mjacob@feral.com Cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: DSL ? Reply-To: ulf@Alameda.net References: <19981028182343.D14495@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Wed, Oct 28, 1998 at 08:40:53PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 08:40:53PM -0800, Matthew Jacob wrote: > > LANMINDS (http://www.lanminds.com) does a DSL coinstall with Covad- they > run some BSDI machines, but also some FreeBSD machines too I believe. > There certainly is at least one person there keenly interested in FreeBSD. > > As an ISP they do a pretty decent job. I've had some difficulties > with the DSL install, but I consider myself really an edge case > and would still give them a 'recommend' rating. > > The basic hookup gets you a DSL router/modem- so it's not really > germane to a *BSD or Linux or Solaris or what have you kind of > OS issue, except that for most cases IPNAT is your friend and > I gather FreeBSD has that fairly well in hand. > > I've heard some negative experiences with IPNAT under FreeBSD > and PacBELL's DSL hookup, but the person reporting that to > me wasn't entirely clear what the issue was- I believe that > there might have been some unfriendly router filtering on > http proxy responses, but I really don't have the details. My company, Alameda Networks, does DSL with Rhythms and we give real address space. Rhtyhms delivers a straight ethernet outlet, you just point your default route at it. > > FWIW > > -matt > > > On Wed, 28 Oct 1998, Ulf Zimmermann wrote: > > > On Wed, Oct 28, 1998 at 04:36:39PM -0800, Manfred Antar wrote: > > > Quick question > > > Does anybody have any experience using PacBell DSL with FreeBSD ? > > > > No, but I haven't heard the best in general about PacHell and their > > service. (That includes me as a ISP customer of PacHell Telco). > > > > How about using an ISP who runs on FreeBSD for DSL feed ? ;-) > > > > > Thanks > > > Manfred > > > ============================== > > > || mantar@netcom.com || > > > || pozo@infinex.com || > > > || Ph. (415) 681-6235 || > > > ============================== > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 23:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13084 for freebsd-current-outgoing; Wed, 28 Oct 1998 23:07:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13077 for ; Wed, 28 Oct 1998 23:07:06 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id KAA15385; Thu, 29 Oct 1998 10:06:40 +0300 (MSK) (envelope-from ache) Message-ID: <19981029100640.A13026@nagual.pp.ru> Date: Thu, 29 Oct 1998 10:06:40 +0300 From: "Andrey A. Chernov" To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: FreeBSD_cc_... Mail-Followup-To: John Polstra , current@freebsd.org References: <19981029082524.A16434@nagual.pp.ru> <199810290536.VAA29610@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810290536.VAA29610@austin.polstra.com>; from jdp@polstra.com on Wed, Oct 28, 1998 at 09:36:01PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 09:36:01PM -0800, John Polstra wrote: > We already do a similar thing with and __FreeBSD_version. Not so similar because _we_ control version numbering scheme for us. > I think it's pretty unlikely that GNU will release a version with a > 5-component revision number. Consider following alternatives: 2.72.1 2.7.2.1 2.721 27.2.1 and so on - they will be the same in your check. The main point is that GNU version numbering scheme is out of our control, so we can assume _anything_ can happens there. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 23:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13596 for freebsd-current-outgoing; Wed, 28 Oct 1998 23:13:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seawall.ninthwave.com (ninthwave.com [209.31.6.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13590 for ; Wed, 28 Oct 1998 23:13:03 -0800 (PST) (envelope-from jdi@ninthwave.com) Received: from ninthwave.com (kuta.ninthwave.com [10.0.0.2]) by seawall.ninthwave.com (8.9.1/8.9.1) with ESMTP id XAA29131; Wed, 28 Oct 1998 23:13:00 -0800 (PST) (envelope-from jdi@ninthwave.com) Message-ID: <3638158C.9D253C0E@ninthwave.com> Date: Wed, 28 Oct 1998 23:13:16 -0800 From: John Irwin X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Manfred Antar CC: current@FreeBSD.ORG Subject: Re: DSL ? References: <4.1.19981028163458.00a11c60@192.168.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Manfred Antar wrote: > Quick question > Does anybody have any experience using PacBell DSL with FreeBSD ? I've been using FreeBSD as my DSL firewall/NAT/web-server/mail-server since I got the DSL line installed. I chose Concentric over PacBell for an ISP -- their service has in general been fine. Ipfilter rewls. -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 23:33:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14871 for freebsd-current-outgoing; Wed, 28 Oct 1998 23:33:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14866 for ; Wed, 28 Oct 1998 23:33:02 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id XAA28808; Wed, 28 Oct 1998 23:32:51 -0800 Date: Wed, 28 Oct 1998 23:32:51 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Ulf Zimmermann cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: DSL ? In-Reply-To: <19981028224957.A1241@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My company, Alameda Networks, does DSL with Rhythms and we give > real address space. Rhtyhms delivers a straight ethernet outlet, > you just point your default route at it. For free? All places offer chunks of address space- but possibly because of ARINet's policies they typically are having to charge for it (and it ain't cheap). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 28 23:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15927 for freebsd-current-outgoing; Wed, 28 Oct 1998 23:43:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15920 for ; Wed, 28 Oct 1998 23:42:59 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id XAA03615; Wed, 28 Oct 1998 23:43:00 -0800 (PST) Message-ID: <19981028234300.A3163@Alameda.net> Date: Wed, 28 Oct 1998 23:43:00 -0800 From: Ulf Zimmermann To: mjacob@feral.com Cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: DSL ? Reply-To: ulf@Alameda.net References: <19981028224957.A1241@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Wed, Oct 28, 1998 at 11:32:51PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 11:32:51PM -0800, Matthew Jacob wrote: > > > My company, Alameda Networks, does DSL with Rhythms and we give > > real address space. Rhtyhms delivers a straight ethernet outlet, > > you just point your default route at it. > > For free? All places offer chunks of address space- but possibly because > of ARINet's policies they typically are having to charge for it (and > it ain't cheap). We give as much address space as someone can satisfying explain to need. >From a certain size we ask for a form to fill out and take the right to scan the IP range to see how the address space is used. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26662 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:26:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26657 for ; Thu, 29 Oct 1998 01:26:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26413; Thu, 29 Oct 1998 01:26:21 -0800 (PST) (envelope-from obrien) Message-ID: <19981029012621.A26396@nuxi.com> Date: Thu, 29 Oct 1998 01:26:21 -0800 From: "David O'Brien" To: Christopher Masto , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me Reply-To: obrien@NUXI.com References: <3633C8F8.EF8E14D5@null.net> <19981026125133.A2717@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981026125133.A2717@netmonger.net>; from Christopher Masto on Mon, Oct 26, 1998 at 12:51:33PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just keep the damn /bin/sh we have now. Who actually uses it as their > login shell? Nobody. I actually do for many maintance accounts where I can't be bothered if Bash has been installed or removed or what not. I'd prefer to remove ash for pdksh as it is a little bit nicer in the interactive department. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28467 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:41:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28458 for ; Thu, 29 Oct 1998 01:41:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26457; Thu, 29 Oct 1998 01:40:58 -0800 (PST) (envelope-from obrien) Message-ID: <19981029014058.B26396@nuxi.com> Date: Thu, 29 Oct 1998 01:40:58 -0800 From: "David O'Brien" To: Studded Cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion Reply-To: obrien@NUXI.com References: <36340B59.DC0FEEBF@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36340B59.DC0FEEBF@gorean.org>; from Studded on Sun, Oct 25, 1998 at 09:40:41PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We're not picking a standard shell here, > > Actually if we use Bash in posix mode as sh having it available as a > standard shell will be a fine bonus. :) IMHO, Bash will never go into the tree since it is GPL vs. UCB/MIT/CMU-style license. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28906 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:42:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28901 for ; Thu, 29 Oct 1998 01:42:36 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id EAA21626; Thu, 29 Oct 1998 04:42:34 -0500 (EST) Date: Thu, 29 Oct 1998 04:42:34 -0500 (EST) Message-Id: <199810290942.EAA21626@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm worried about the thread scheduler. Here is a disturbing test program out for folks to try. As you can probably guess, we are now battling the scheduler because some of our application's threads are getting seriously starved by other threads. I'm compiling on 3.0 with the latest libc_r. This program works fine on IRIX, Solaris, and (gasp..) Linux. Isn't FreeBSD supposed to handle this without the explicit yield() call? -Rob ---- /***************************************************************************** File: schedBug.C Contents: FreeBSD Scheduling Bug Illustrator This program SHOULD print "Marking Time : 1", etc. However, the thread scheduler appears to NOT schedule the markTimeThread because the ioThread is so busy. If you uncomment the "::pthread_yield()" it works a little better. Ideally, you should get a print every second. g++ -o schedBug -D_REENTRANT -D_THREAD_SAFE -g -Wall schedBug.C -pthread *****************************************************************************/ #include #include #include #include #include #include #include unsigned int LENGTH = 1024 * 1024; void *ioThread(void *) { char *data = new char[LENGTH]; ::memset(data, 0, LENGTH); while (true) { int file = ::open("scrap", O_CREAT | O_TRUNC | O_WRONLY, 0666); assert(file != -1); assert(::write(file, data, LENGTH) == static_cast(LENGTH)); // // Uncomment the next line to make things a bit better // // ::pthread_yield(); // assert(!::close(file)); } } void *markTimeThread(void *) { time_t start = ::time(0); while (true) { timeval timeout; timeout.tv_sec = 1; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); ::printf("Marking Time: %lu\n", ::time(0) - start); } } int main(int, char **) { // Set up Thread Arguments pthread_t tid; pthread_attr_t attr; assert(!::pthread_attr_init(&attr)); assert(!::pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_DETACHED)); // Spawn markTimeThread assert(!::pthread_create(&tid, &attr, markTimeThread, 0)); // Spawn ioThread assert(!::pthread_create(&tid, &attr, ioThread, 0)); // main() goes away for a long time timeval timeout; timeout.tv_sec = 3600; timeout.tv_usec = 0; ::select(0, 0, 0, 0, &timeout); return EXIT_SUCCESS; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28997 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:43:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28987 for ; Thu, 29 Oct 1998 01:43:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26484; Thu, 29 Oct 1998 01:43:17 -0800 (PST) (envelope-from obrien) Message-ID: <19981029014317.C26396@nuxi.com> Date: Thu, 29 Oct 1998 01:43:17 -0800 From: "David O'Brien" To: Martin Cracauer Cc: current@FreeBSD.ORG Subject: Re: sh and ~ expansion Reply-To: obrien@NUXI.com References: <362B74B6.B9B256B4@gorean.org> <19981028185553.A18168@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981028185553.A18168@cons.org>; from Martin Cracauer on Wed, Oct 28, 1998 at 06:55:53PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > pdksh has a number of (IMHO) bugs with respect to signal handling. The > problem here is "what happens when a sh child uses SIGINT and/or So, lets fix them and submit the patches back to the pdksh developers. > If you through away your shell and use a new one, you'll use a > valuable resource: All the PRs collected over the years. Why are old PRs so valuable? > For pdksh, you'll start from scratch So? For 3.0+ we added so many new things that we had to start from scratch on. ELF, new boot loader, Amd, 4.4Lite2 in the kernel, etc... -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29496 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:48:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29485 for ; Thu, 29 Oct 1998 01:48:35 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26521; Thu, 29 Oct 1998 01:48:24 -0800 (PST) (envelope-from obrien) Message-ID: <19981029014824.D26396@nuxi.com> Date: Thu, 29 Oct 1998 01:48:24 -0800 From: "David O'Brien" To: Andreas Klemm , current@FreeBSD.ORG Subject: Re: IPv6 in -current Reply-To: obrien@NUXI.com References: <3635F22D.1A6B9EB4@simultan.ch> <19981029001848.A22320@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981029001848.A22320@klemm.gtn.com>; from Andreas Klemm on Thu, Oct 29, 1998 at 12:18:48AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There has been a discussion about that some months ago on > the freebsd net mailinglist if this helps. Can you summerize the conclusions? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29536 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:49:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29531 for ; Thu, 29 Oct 1998 01:49:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26529; Thu, 29 Oct 1998 01:49:05 -0800 (PST) (envelope-from obrien) Message-ID: <19981029014905.E26396@nuxi.com> Date: Thu, 29 Oct 1998 01:49:05 -0800 From: "David O'Brien" To: Thomas Seidmann , current@FreeBSD.ORG Subject: Re: IPv6 in -current Reply-To: obrien@NUXI.com References: <3635F22D.1A6B9EB4@simultan.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3635F22D.1A6B9EB4@simultan.ch>; from Thomas Seidmann on Tue, Oct 27, 1998 at 05:17:49PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IPv6 protocol stack (and BSD networking of course :-)). INRIA seems to > have a much more mature status than KAME (with my full respect to the But some of the KAME developers have commit privs. Thus they can maintain the code. This bonus should not be overlooked. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 01:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29937 for freebsd-current-outgoing; Thu, 29 Oct 1998 01:52:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29919; Thu, 29 Oct 1998 01:52:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id BAA26539; Thu, 29 Oct 1998 01:51:58 -0800 (PST) (envelope-from obrien) Message-ID: <19981029015157.F26396@nuxi.com> Date: Thu, 29 Oct 1998 01:51:57 -0800 From: "David O'Brien" To: Mark Murray , Mike Smith Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? Reply-To: obrien@NUXI.com References: <199810282037.MAA00616@dingo.cdrom.com> <199810290544.HAA15428@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810290544.HAA15428@gratis.grondar.za>; from Mark Murray on Thu, Oct 29, 1998 at 07:44:31AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bento was used this time around. I think Justin is probably feeling > > pretty embarrassed about now. Ouch. > > I'm busy dekerberising that box... But it needs to be kerberised to live in the FreeBSD network, right? (as per the upcoming changes in cvs-commiters). Only the chrooted environment that Justin builds in needs to be dekerberised. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 02:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02388 for freebsd-current-outgoing; Thu, 29 Oct 1998 02:10:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02368 for ; Thu, 29 Oct 1998 02:10:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA28723; Thu, 29 Oct 1998 10:11:24 GMT Date: Thu, 29 Oct 1998 10:11:24 +0000 (GMT) From: Doug Rabson To: Alexander Sanda cc: freebsd-current@FreeBSD.ORG Subject: Re: Nestea fix on 3.0-* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Alexander Sanda wrote: > > Hi > > I have running some systems, which I recently upgraded to 3.0-RELEASE. > Everything is running fine, but I would feel more comfortable with a > kernel not vulnerable to the Nestea (sp?) attack. > > So is it safe, to install a -current kernel on a 3.0-RELEASE system ? I > mainly ask, because I noticed a lot of changes under src/sys recently. > > Or should I only checkout netinet/ip_input.c and recompile the kernel ? For what its worth, the change to ip_input.c has no dependencies (as far as I know) to any other recent kernel changes. You can safely update this one file. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 02:28:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04494 for freebsd-current-outgoing; Thu, 29 Oct 1998 02:28:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04478 for ; Thu, 29 Oct 1998 02:28:39 -0800 (PST) (envelope-from pc@shaw.wave.ca) Received: from pool-207-205-237-248.dlls.grid.net (pool-207-205-237-248.dlls.grid.net [207.205.237.248]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with SMTP id FAA02209 for ; Thu, 29 Oct 1998 05:28:36 -0500 (EST) From: pc@shaw.wave.ca (C. Peter Constantinidis) To: freebsd-current@FreeBSD.ORG Subject: Re: Make Release with KERNFORMAT=elf Date: Thu, 29 Oct 1998 10:28:36 GMT Reply-To: pc@shaw.wave.ca Message-ID: <363942ad.8393637@mail.mindspring.com> References: <1882.909615895@time.cdrom.com> In-Reply-To: <1882.909615895@time.cdrom.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA04483 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998 15:04:55 -0800, "Jordan K. Hubbard" wrote: >> I'm not following you here. You can't use kzip on an ELF kernel, so if >> we cut over to an ELF kernel for the install, you have to gzip it and >> use the new loader. This will probably push us to the two-disk install. >I'm suggesting that we eventually go to gzip for all kernels and use >the new loader with a loader script, yes. As far as it all fitting on >one floppy, I wouldn't write that off just yet. The gzip'd kernel is >about the same size and the loader is 80K, something which could >possibly also be built in a "stripped down" configuration. It's >nothing I'd want to do immediately, but I think it might be possible >with a little sweat. I'm a bit of a newbie, so umm.. I hope I'm not saying something here that isn't possible, or what.. but.. Why not have all the files on the boot floppy compressed, and have the kernel or whatever is on the floppy extract the files into a temporary ramdisk on the PC? Also, what about 1.7 meg formatting tricks? Both tricks seem to work fine under DOS. Best, P. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 02:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05099 for freebsd-current-outgoing; Thu, 29 Oct 1998 02:31:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05092 for ; Thu, 29 Oct 1998 02:31:06 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA04146; Thu, 29 Oct 1998 02:30:20 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: pc@shaw.wave.ca cc: freebsd-current@FreeBSD.ORG Subject: Re: Make Release with KERNFORMAT=elf In-reply-to: Your message of "Thu, 29 Oct 1998 10:28:36 GMT." <363942ad.8393637@mail.mindspring.com> Date: Thu, 29 Oct 1998 02:30:20 -0800 Message-ID: <4142.909657020@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm a bit of a newbie, so umm.. I hope I'm not saying something here that > isn't possible, or what.. but.. Why not have all the files on the boot > floppy compressed, and have the kernel or whatever is on the floppy extract > the files into a temporary ramdisk on the PC? That's exactly what it does already. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 04:39:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19059 for freebsd-current-outgoing; Thu, 29 Oct 1998 04:39:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19054 for ; Thu, 29 Oct 1998 04:39:22 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id OAA21028; Thu, 29 Oct 1998 14:38:14 +0200 (SAT) From: John Hay Message-Id: <199810291238.OAA21028@zibbi.mikom.csir.co.za> Subject: Re: IPv6 in -current In-Reply-To: <19981029014905.E26396@nuxi.com> from David O'Brien at "Oct 29, 98 01:49:05 am" To: obrien@NUXI.com Date: Thu, 29 Oct 1998 14:38:14 +0200 (SAT) Cc: tseidmann@simultan.ch, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > IPv6 protocol stack (and BSD networking of course :-)). INRIA seems to > > have a much more mature status than KAME (with my full respect to the > > But some of the KAME developers have commit privs. Thus they can > maintain the code. This bonus should not be overlooked. Well I'm also looking at IPv6 at the moment and it would really be nice if we can get a version of IPv6 standard in FreeBSD. I have been looking at (and using) the KAME stuff the last few weeks and am quite impressed with it. One of the advantages (for me) about the KAME stack is that we also get their IPSEC stuff, while with INRIA being in France, it makes things a little more complicated. It does mean that we will probably have to decide beforehand how we will deal with the crypto code. Maybe somehow seperate it and make it available from internat.freebas.org for the nonUSA people, like the rest of the FreeBSD crypto code? I know the last IPv6 discussion ended with the idea that the different IPv6 groups should "get together" and figure out what should go into FreeBSD and where it should go into FreeBSD, but I'm not sure that anything happened after that? Or was it just behind the scenes? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 04:56:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20155 for freebsd-current-outgoing; Thu, 29 Oct 1998 04:56:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20149 for ; Thu, 29 Oct 1998 04:56:01 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id NAA26796; Thu, 29 Oct 1998 13:54:20 +0100 (CET) Message-ID: <36386575.35E337FC@simultan.ch> Date: Thu, 29 Oct 1998 13:54:13 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: John Hay CC: current@FreeBSD.ORG Subject: Re: IPv6 in -current References: <199810291238.OAA21028@zibbi.mikom.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > (and using) the KAME stuff the last few weeks and am quite impressed > with it. One of the advantages (for me) about the KAME stack is that we > also get their IPSEC stuff, while with INRIA being in France, it makes > things a little more complicated. It does mean that we will probably > have to decide beforehand how we will deal with the crypto code. Maybe > somehow seperate it and make it available from internat.freebas.org for > the nonUSA people, like the rest of the FreeBSD crypto code? INRIA's IPSEC code is IMHO a no-brainer. In the last distribution, complete AH has been added, since this can be exported from France. The ESP stuff cannot be, however, but it take only to copy 4-5 files with the missing code and adding a couple of options in the kernel config file (I do have these files, ehce theyt could be stored for instance at internat.freebas.org). > I know the last IPv6 discussion ended with the idea that the different > IPv6 groups should "get together" and figure out what should go into > FreeBSD and where it should go into FreeBSD, but I'm not sure that > anything happened after that? Or was it just behind the scenes? I'm intereseted in this, too. > John > -- > John Hay -- John.Hay@mikom.csir.co.za Regards, Thomas -- ========================================================== Dipl.-Ing. Thomas Seidmann Senior IT systems architect Simultan AG, CH-6246 Altishofen, Switzerland mailto:tseidmann@simultan.ch tel +41.62.7489000 http://www.simultan.ch/~thomas fax +41.62.7489010 ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 06:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28854 for freebsd-current-outgoing; Thu, 29 Oct 1998 06:29:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28833; Thu, 29 Oct 1998 06:29:54 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA01270; Thu, 29 Oct 1998 09:28:56 -0500 (EST) Date: Thu, 29 Oct 1998 09:28:56 -0500 (EST) From: John Fieber To: "David O'Brien" cc: Mark Murray , Mike Smith , sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: <19981029015157.F26396@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, David O'Brien wrote: > > > Bento was used this time around. I think Justin is probably feeling > > > pretty embarrassed about now. Ouch. > > > > I'm busy dekerberising that box... > > But it needs to be kerberised to live in the FreeBSD network, right? > (as per the upcoming changes in cvs-commiters). You shouldn't need to de-kerberize...so long as you don't build XFree86 with kerberos it shouldn't infect the rest of the X ports. (The infection is spread by imake). -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 06:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29524 for freebsd-current-outgoing; Thu, 29 Oct 1998 06:34:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29507; Thu, 29 Oct 1998 06:34:09 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id QAA16778; Thu, 29 Oct 1998 16:32:40 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810291432.QAA16778@gratis.grondar.za> To: John Fieber cc: "David O'Brien" , Mike Smith , sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Thu, 29 Oct 1998 09:28:56 EST." References: Date: Thu, 29 Oct 1998 16:32:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Fieber wrote: > > > I'm busy dekerberising that box... > > > > But it needs to be kerberised to live in the FreeBSD network, right? > > (as per the upcoming changes in cvs-commiters). > > You shouldn't need to de-kerberize...so long as you don't build > XFree86 with kerberos it shouldn't infect the rest of the X > ports. (The infection is spread by imake). The box needed a big cleanup anyway. I have done that :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 07:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03682 for freebsd-current-outgoing; Thu, 29 Oct 1998 07:03:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03592 for ; Thu, 29 Oct 1998 07:03:14 -0800 (PST) (envelope-from chet@nike.ins.cwru.edu) Received: (chet@localhost) by nike.ins.cwru.edu (8.8.7/CWRU-2.5-bsdi) id KAA16785; Thu, 29 Oct 1998 10:02:36 -0500 (EST) (from chet) Date: Thu, 29 Oct 1998 09:57:13 -0500 From: Chet Ramey To: cracauer@cons.org Subject: Re: sh and ~ expansion Cc: green@zone.syracuse.net, Studded@gorean.org, dag-erli@ifi.uio.no, current@FreeBSD.ORG, chet@po.cwru.edu Reply-To: chet@po.cwru.edu In-Reply-To: Message from cracauer@cons.org of Wed, 28 Oct 1998 18:55:53 +0100 (id <19981028185553.A18168@cons.org>) Message-ID: <981029145713.AA16764.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, like bash pdksh fails to execute traps while a child that blocks > signals is running. Consider this: > > #! /bin/sh > trap 'echo aborting ; exit 1' 2 > ./hardguy-that-blocks-sigint > > In bash and pdksh, the trap will be run *after* the blocking child > exited, while in our sh it will run the trap immediatly. The bash/pdksh behavior is required by POSIX.2, section 3.11. The FreeBSD sh is non-compliant. > And I don't like that pdksh doesn't do > . lib.sh > if lib.sh is in the current directory, is not executable and '.' is > not the $PATH. You have to use '. ./lib.sh' instead. Again, the pdksh behavior obeys POSIX.2 to the letter. Bash defaults to the current directory after looking in $PATH, but that is an extension. I assume that the FreeBSD sh does the same. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 07:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04334 for freebsd-current-outgoing; Thu, 29 Oct 1998 07:07:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04321 for ; Thu, 29 Oct 1998 07:07:33 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id KAA02424; Thu, 29 Oct 1998 10:07:20 -0500 (EST) Date: Thu, 29 Oct 1998 10:07:20 -0500 (EST) From: Daniel Eischen Message-Id: <199810291507.KAA02424@pcnet1.pcnet.com> To: current@FreeBSD.ORG, info@highwind.com Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm worried about the thread scheduler. Here is a disturbing test > program out for folks to try. > > As you can probably guess, we are now battling the scheduler because > some of our application's threads are getting seriously starved by > other threads. > > I'm compiling on 3.0 with the latest libc_r. > > This program works fine on IRIX, Solaris, and (gasp..) Linux. > > Isn't FreeBSD supposed to handle this without the explicit yield() call? It looks like setitimer isn't working as the threads library expects it to. The timer isn't going off, but it seems to be set properly. If you manually kill -VTALRM the running process, you'll see the markTimeThread run. I placed a print statement in the threads library where the timer is set, and it is being called with the proper values (100msec time slice). Why does heavy IO stop the timer from going off and the process from being signaled? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 07:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07505 for freebsd-current-outgoing; Thu, 29 Oct 1998 07:38:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07483 for ; Thu, 29 Oct 1998 07:38:00 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA00450; Thu, 29 Oct 1998 10:37:35 -0500 (EST) (envelope-from wollman) Date: Thu, 29 Oct 1998 10:37:35 -0500 (EST) From: Garrett Wollman Message-Id: <199810291537.KAA00450@khavrinen.lcs.mit.edu> To: John Hay Cc: obrien@NUXI.com, tseidmann@simultan.ch, current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810291238.OAA21028@zibbi.mikom.csir.co.za> References: <19981029014905.E26396@nuxi.com> <199810291238.OAA21028@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > we can get a version of IPv6 standard in FreeBSD. I have been looking at > (and using) the KAME stuff the last few weeks and am quite impressed > with it. One of the advantages (for me) about the KAME stack is that we > also get their IPSEC stuff, while with INRIA being in France, it makes > things a little more complicated. Don't forget there's also the group of people who worked on the NRL stack.... The other question that people have to consider whenever IPv6 comes up: with whom are you going to communicate? Right now, there is no globally-routed IPv6 infrastructure, and there is unlikely to be any, any time soon (IOS 12, anyone?). I am prefectly happy with the state of the world where we can advance our technological goals in the context of IPv4, and let other parties provide an IPv6 implementation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09695 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:02:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09689 for ; Thu, 29 Oct 1998 08:02:03 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id KAA14098; Thu, 29 Oct 1998 10:01:54 -0600 (CST) Message-Id: <199810291601.KAA14098@ns.tar.com> From: "Richard Seaman, Jr." To: "current@FreeBSD.ORG" , "Daniel Eischen" , "info@highwind.com" Date: Thu, 29 Oct 98 10:01:53 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 10:07:20 -0500 (EST), Daniel Eischen wrote: >> I'm worried about the thread scheduler. Here is a disturbing test >> program out for folks to try. >> >> As you can probably guess, we are now battling the scheduler because >> some of our application's threads are getting seriously starved by >> other threads. >> >> I'm compiling on 3.0 with the latest libc_r. >> >> This program works fine on IRIX, Solaris, and (gasp..) Linux. >> >> Isn't FreeBSD supposed to handle this without the explicit yield() call? > >It looks like setitimer isn't working as the threads library >expects it to. The timer isn't going off, but it seems to be >set properly. > >If you manually kill -VTALRM the running process, you'll see >the markTimeThread run. > >I placed a print statement in the threads library where the >timer is set, and it is being called with the proper values >(100msec time slice). > >Why does heavy IO stop the timer from going off and the >process from being signaled? Possibly the VTALRM timer measures only time spent in user mode and not in kernel mode. This heavy I/O takes place almost entirely in kernel mode and it is the only process running. Therefore, very little user time is being accumulated. Possibly it you waited long enough, you'd still get the SIGVTALRM. If you add some user mode processing to the thread, you'll see the SIGVTALRM sooner. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:10:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11013 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:10:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11001 for ; Thu, 29 Oct 1998 08:10:12 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA11080; Thu, 29 Oct 1998 11:10:06 -0500 (EST) Date: Thu, 29 Oct 1998 11:10:06 -0500 (EST) From: Daniel Eischen Message-Id: <199810291610.LAA11080@pcnet1.pcnet.com> To: current@FreeBSD.ORG, eischen@vigrid.com, info@highwind.com, lists@tar.com Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >It looks like setitimer isn't working as the threads library > >expects it to. The timer isn't going off, but it seems to be > >set properly. > > > >If you manually kill -VTALRM the running process, you'll see > >the markTimeThread run. > > > >I placed a print statement in the threads library where the > >timer is set, and it is being called with the proper values > >(100msec time slice). > > > >Why does heavy IO stop the timer from going off and the > >process from being signaled? > > Possibly the VTALRM timer measures only time spent in user mode > and not in kernel mode. This heavy I/O takes place almost entirely > in kernel mode and it is the only process running. Therefore, very > little user time is being accumulated. > > Possibly it you waited long enough, you'd still get the SIGVTALRM. > If you add some user mode processing to the thread, you'll see > the SIGVTALRM sooner. Yeah, I just figured this out (should pay closer attention to the man pages). Seems like the profiling timer would be closer to what we'd want (not to say the threads library should use the profiling timer). A quick hack to replace occurrences of SIGVTALRM with SIGPROF in the threads library seems to make the test program work more correctly. Perhaps SIGALRM should be used instead of SIGVTALRM? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12492 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:25:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12486 for ; Thu, 29 Oct 1998 08:25:07 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id KAA14241; Thu, 29 Oct 1998 10:25:02 -0600 (CST) Message-Id: <199810291625.KAA14241@ns.tar.com> From: "Richard Seaman, Jr." To: "current@FreeBSD.ORG" , "eischen@vigrid.com" , "info@highwind.com" Date: Thu, 29 Oct 98 10:25:02 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 11:10:06 -0500 (EST), Daniel Eischen wrote: >Yeah, I just figured this out (should pay closer attention to >the man pages). Seems like the profiling timer would be closer >to what we'd want (not to say the threads library should use >the profiling timer). A quick hack to replace occurrences of >SIGVTALRM with SIGPROF in the threads library seems to make >the test program work more correctly. > >Perhaps SIGALRM should be used instead of SIGVTALRM? Of course, it we had kernel threads, the pthreads code would be a *lot* simpler and maybe less prone to bugs, the kernel would do the preemption for us, and context switches would be much faster than the current user thread implementation. :) I've been poking around in the code, and I'd guess that a uniprocessor kernel threads implementation wouldn't involve all that much work. However, I understand there's are fair amount of kernel work that needs to be done for SMP kernel threads. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13318 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:33:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13309 for ; Thu, 29 Oct 1998 08:33:11 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id QAA12809; Thu, 29 Oct 1998 16:32:51 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma012804; Thu, 29 Oct 98 16:32:45 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zYvBv-0001OS-00; Thu, 29 Oct 1998 16:44:55 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG From: Tony Finch Subject: Re: Thread Scheduler bug In-Reply-To: <199810290942.EAA21626@highwind.com> X-Mailer: VM 6.34 under Emacs 19.34.1 Message-Id: Date: Thu, 29 Oct 1998 16:44:55 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HighWind Software Information wrote: > >I'm worried about the thread scheduler. Here is a disturbing test >program out for folks to try. > >As you can probably guess, we are now battling the scheduler because >some of our application's threads are getting seriously starved by >other threads. We've been having what seem to be related problems. We're currently running Squid on a number of 2.2 boxen, but we're keen to move to 3.0 because of the potential performace improvement that asynchronous IO can provide -- normal Squid tends to get IO bound, and the threaded async-io version could fix that. Unfortunately libc_r doesn't seem up to the task :-( The problematic code is the async-io initialisation: [...] pthread_attr_init(&globattr); pthread_attr_setscope(&globattr, PTHREAD_SCOPE_SYSTEM); globsched.sched_priority = 1; main_thread = pthread_self(); pthread_setschedparam(main_thread, SCHED_OTHER, &globsched); globsched.sched_priority = 2; pthread_attr_setschedparam(&globattr, &globsched); /* Create threads and get them to sit in their wait loop */ [...] This won't compile owing to the lack of some of the scheduling functions, and if you try simply taking them out (as has been suggested in the past on freebsd-questions) then Squid fails to start because it cannot communicate with the dnsserver child processes. This seems to indicate a scheduling problem of some sort. Squid doesn't make any sort of yield calls; would this cause such problems? What is the status of the kernel threads project? It occurs to me that some of the other new functionality of 3.0 is quite similar to that used by the linuxthreads implementation -- rfork() is quite similar to Linux's clone(); does the POSIX.1b stuff help for thread scheduling? Tony. -- fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:42:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14299 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:42:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14249 for ; Thu, 29 Oct 1998 08:42:29 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA11625 for ; Thu, 29 Oct 1998 11:45:00 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 29 Oct 1998 11:45:00 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: current@FreeBSD.ORG Subject: NFS broken with large files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have /com nfs mounted: from fstab: xxx:/com /com nfs rw,tcp,bg,nfsv3 0 0 ii'm trying to manipulate this file: /com/bkup % ls -l www1-local.tar -rw-r--r-- 1 root wheel 2162790400 Oct 27 21:56 www1-local.tar /com/bkup % tar tf www1-local.tar /com/bkup % /com/bkup % dd if=www1-local.tar of=/dev/null bs=128k 0+0 records in 0+0 records out 0 bytes transferred in 0.000073 secs (0 bytes/sec) /com/bkup % less www1-local.tar Cannot seek to that file position (press RETURN) Solaris (local file system): /com/bkup>tar tf www1-local.tar tar: Cannot open www1-local.tar: Value too large for defined data type tar: Error is not recoverable: exiting now however dd is able to read from it IRIX (also NFS mounted) /com/bkup>tar tf www1-local.tar FLEXlm/ FLEXlm/release.notes bin/ bin/ar bin/b2m bin/c++ ...and so on I thought NFSv3 provided for very large file support? not only that, this file is not _that_ large... just 2gigs. the amusing part is although SUN is the NFS server, only IRIX seems to be able to handle this file properly via NFS, solaris bombs out even on the local system. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 08:49:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15073 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:49:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15064 for ; Thu, 29 Oct 1998 08:49:32 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA16122; Thu, 29 Oct 1998 11:49:27 -0500 (EST) Date: Thu, 29 Oct 1998 11:49:27 -0500 (EST) From: Daniel Eischen Message-Id: <199810291649.LAA16122@pcnet1.pcnet.com> To: current@FreeBSD.ORG, eischen@vigrid.com, info@highwind.com, lists@tar.com Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of course, it we had kernel threads, the pthreads code would be > a *lot* simpler and maybe less prone to bugs, the kernel would > do the preemption for us, and context switches would be much > faster than the current user thread implementation. :) Yeah, but you will still want to be able to have userland threads mixed with kernel threads. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 09:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18586 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:16:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18581 for ; Thu, 29 Oct 1998 09:16:46 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA04055; Thu, 29 Oct 1998 09:16:24 -0800 (PST) (envelope-from jdp) Message-Id: <199810291716.JAA04055@austin.polstra.com> To: "Andrey A. Chernov" cc: current@FreeBSD.ORG Subject: Re: FreeBSD_cc_... In-reply-to: Your message of "Thu, 29 Oct 1998 10:06:40 +0300." <19981029100640.A13026@nagual.pp.ru> Date: Thu, 29 Oct 1998 09:16:24 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We already do a similar thing with and __FreeBSD_version. > > Not so similar because _we_ control version numbering scheme for us. > > > I think it's pretty unlikely that GNU will release a version with a > > 5-component revision number. > > Consider following alternatives: > > 2.72.1 > 2.7.2.1 > 2.721 > 27.2.1 > > and so on - they will be the same in your check. > > The main point is that GNU version numbering scheme is out of our control, > so we can assume _anything_ can happens there. Yes, I see your point. I'll change it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 09:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21911 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:50:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--172.sirius.net [205.134.241.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21900 for ; Thu, 29 Oct 1998 09:50:53 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id JAA23862; Thu, 29 Oct 1998 09:50:22 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810291750.JAA23862@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: Stupid ksh tricks [Was: Re: Changing sh for compatibility sake] In-reply-to: Your message of "Wed, 28 Oct 1998 21:32:08 EST." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 09:50:22 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >set -o vi-tabcomplete Doesn't work in emacs mode, unfortunately. -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 09:54:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22520 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:54:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--172.sirius.net [205.134.241.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22515 for ; Thu, 29 Oct 1998 09:54:47 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id JAA23912; Thu, 29 Oct 1998 09:54:45 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810291754.JAA23912@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Day cc: current@FreeBSD.ORG, tjm@codegen.com, eric@needhams.com Subject: Re: Mod to doscmd's port.c to directly access parallel ports In-reply-to: Your message of "Wed, 28 Oct 1998 20:09:23 CST." <199810290209.UAA13367@home.dragondata.com> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 09:54:44 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I ended up using something similar to run the EMP-10 on freebsd, but be >careful. the device is extremely sensitive to timings. (especially when >programming EPROMs... flash isn't so bad). > >Either nice it to -20, or diddle with rtprio. :) Thanks for the tip - I'll definitely up its priority (as it were). -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 09:56:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22770 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:56:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--172.sirius.net [205.134.241.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22765 for ; Thu, 29 Oct 1998 09:56:40 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id JAA23932; Thu, 29 Oct 1998 09:55:57 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810291755.JAA23932@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eric Cox cc: current@FreeBSD.ORG, tjm@codegen.com Subject: Re: Mod to doscmd's port.c to directly access parallel ports In-reply-to: Your message of "Wed, 28 Oct 1998 18:18:01 PST." <3637D059.80889AB6@needhams.com> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 09:55:57 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I don't know that much about FreeBSD (the only thing I've done on >FreeBSD is setup a news feeder), but it looks to me like >i386_set_ioperm is being called with the same parameters under >iomap or iounmap (i.e. the two calls are the same, functionally). Oops - you're right. The second call to unmap should have the last parameter as "0", dammit. Thanks! -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 09:59:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23053 for freebsd-current-outgoing; Thu, 29 Oct 1998 09:59:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23047 for ; Thu, 29 Oct 1998 09:59:50 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (dial-35-227.easystreet.com [206.103.35.227]) by mail.easystreet.com (8.8.7/8.8.7) with SMTP id JAA04928 for ; Thu, 29 Oct 1998 09:59:47 -0800 (PST) Message-ID: <003401be036e$086894b0$0d787880@apex> From: "Carlos C. Tapang" To: Subject: Plugging a FreeBSD server to the net: need advice Date: Thu, 29 Oct 1998 10:57:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I'm about ready to plug a server to the net. Frankly, I was leaning on using Windows NT for some time, but now I am convinced that FreeBSD is a much better choice. (I just read Yahoo's testimonial on FreeBSD.) I now need to decide on which version of FreeBSD to use. Should I go with 2.2.7 or 3.0. Is 3.0 ready for it? The server will be a web, mail, and ftp server. Will I get double mileage with having a 2-processor SMP system? Is FreeBSD.ORG behind a firewall? If it's not, then my server probably does not need to be behind a firewall. (I am paranoid about malignant attacks, but if FreeBSD.ORG can survive, so should my server.) Are DTP raid controllers really as good as they're cracked up to be? Do I really need RAID, or should a regular SCSI drive/controller do as well? My feeling is that regular SCSI drives should be reliable enough for my purposes. I would like my server to be a mirror site for FreeBSD-current downloads. My server will plug to the net using an SDSL line from GTE (it's cheap!) at 384Kbits/sec, so probably I do not need the processing power for now. I do plan to upgrade to higher bandwidth xDSL later. --Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 10:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26477 for freebsd-current-outgoing; Thu, 29 Oct 1998 10:17:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--172.sirius.net [205.134.241.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26471 for ; Thu, 29 Oct 1998 10:16:59 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id KAA24369; Thu, 29 Oct 1998 10:17:04 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810291817.KAA24369@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: tjm@codegen.com, eric@needhams.com Subject: Re: Mod to doscmd's port.c to directly access parallel ports In-reply-to: Your message of "Wed, 28 Oct 1998 16:57:31 PST." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 10:17:04 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was just pointed out to me that I'd screwed up the mod for iounmap(). > static void > iounmap(int port, int cnt) > { >! if (port + cnt >= MAXPORT) { >! errno = ERANGE; >! goto bad; >! } >! if (i386_set_ioperm(port, cnt, 1) < 0) { ^^^ 0 >! bad: >! perror("iounmap"); >! quit(1); >! } > } Oops. I've submitted the proper fix using send-pr. Thanks! Actually, this rather slows down the whole port-access quite a bit. I'm inclined to set the port access on at startup and off on exit. -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 10:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02953 for freebsd-current-outgoing; Thu, 29 Oct 1998 10:59:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02948 for ; Thu, 29 Oct 1998 10:59:10 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id UAA26651; Thu, 29 Oct 1998 20:58:49 +0200 (SAT) From: John Hay Message-Id: <199810291858.UAA26651@zibbi.mikom.csir.co.za> Subject: Re: IPv6 in -current In-Reply-To: <199810291537.KAA00450@khavrinen.lcs.mit.edu> from Garrett Wollman at "Oct 29, 98 10:37:35 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 29 Oct 1998 20:58:48 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > we can get a version of IPv6 standard in FreeBSD. I have been looking at > > (and using) the KAME stuff the last few weeks and am quite impressed > > with it. One of the advantages (for me) about the KAME stack is that we > > also get their IPSEC stuff, while with INRIA being in France, it makes > > things a little more complicated. > > Don't forget there's also the group of people who worked on the NRL > stack.... I didn't. I explicitly left them about because of two reasons. Because I'm not in the USA and I'm not a USA citizen, I can't get hold of it. Then also according to their web site they only cater for BSDI, NetBSD and Linux, with a promise that they will support FreeBSD in their next release. But I don't really mind which one we are using. Any one that is part of FreeBSD will make my life easier. Most of the stacks available only support a specific release, so if you are running stable or current you have to constantly merge. (Well actually current is out of the question at the moment because none of them support 3.0 let alone current and that is actually where it would like it, because most of our test boxes run current.) > The other question that people have to consider whenever IPv6 comes > up: with whom are you going to communicate? Right now, there is no > globally-routed IPv6 infrastructure, and there is unlikely to be any, > any time soon (IOS 12, anyone?). I am prefectly happy with the state > of the world where we can advance our technological goals in the > context of IPv4, and let other parties provide an IPv6 implementation. While it is not native, the 6bone is up and running and people are using it to test compatability of the different stacks and other things. Our side of the 6bone tunnel is a FreeBSD box running the KAME stack and the other side is a Cisco somewhere in the USA. I do agree that IPv4 will be the main protocol for while, the other side is that IPv6 is coming and we shouldn't wait too long to incorporate it. By having a standard stack we can unite the FreeBSD IPv6 users and get it better tested than currently where we are split up between the different stacks. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 12:17:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15855 for freebsd-current-outgoing; Thu, 29 Oct 1998 12:17:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15849 for ; Thu, 29 Oct 1998 12:17:22 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id PAA02026; Thu, 29 Oct 1998 15:16:40 -0500 (EST) Date: Thu, 29 Oct 1998 15:16:40 -0500 (EST) Message-Id: <199810292016.PAA02026@highwind.com> From: HighWind Software Information To: eischen@vigrid.com CC: current@FreeBSD.ORG, eischen@vigrid.com, lists@tar.com In-reply-to: <199810291610.LAA11080@pcnet1.pcnet.com> (message from Daniel Eischen on Thu, 29 Oct 1998 11:10:06 -0500 (EST)) Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Possibly the VTALRM timer measures only time spent in user mode > and not in kernel mode. This heavy I/O takes place almost entirely > in kernel mode and it is the only process running. Therefore, very > little user time is being accumulated. > > Possibly it you waited long enough, you'd still get the SIGVTALRM. > If you add some user mode processing to the thread, you'll see > the SIGVTALRM sooner. Yeah, I just figured this out (should pay closer attention to the man pages). Seems like the profiling timer would be closer to what we'd want (not to say the threads library should use the profiling timer). A quick hack to replace occurrences of SIGVTALRM with SIGPROF in the threads library seems to make the test program work more correctly. Interesting analysis. This seems to be a very NASTY problem. If you have a collection of threads that spend a lot of time in system space, you can REALLY starve other threads. I can't imagine that this is a rare occurance. Is using SIGPROF a viable alternative? Sounds a bit drastic. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 13:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23562 for freebsd-current-outgoing; Thu, 29 Oct 1998 13:13:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23544 for ; Thu, 29 Oct 1998 13:13:51 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA19289; Thu, 29 Oct 1998 16:13:44 -0500 (EST) Date: Thu, 29 Oct 1998 16:13:44 -0500 (EST) From: Daniel Eischen Message-Id: <199810292113.QAA19289@pcnet1.pcnet.com> To: eischen@vigrid.com, info@highwind.com Subject: Re: Thread Scheduler bug Cc: current@FreeBSD.ORG, lists@tar.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Possibly the VTALRM timer measures only time spent in user mode > > and not in kernel mode. This heavy I/O takes place almost entirely > > in kernel mode and it is the only process running. Therefore, very > > little user time is being accumulated. > > > > Possibly it you waited long enough, you'd still get the SIGVTALRM. > > If you add some user mode processing to the thread, you'll see > > the SIGVTALRM sooner. > > Yeah, I just figured this out (should pay closer attention to > the man pages). Seems like the profiling timer would be closer > to what we'd want (not to say the threads library should use > the profiling timer). A quick hack to replace occurrences of > SIGVTALRM with SIGPROF in the threads library seems to make > the test program work more correctly. > > Interesting analysis. This seems to be a very NASTY problem. If you > have a collection of threads that spend a lot of time in system space, > you can REALLY starve other threads. I can't imagine that this is a > rare occurance. > > Is using SIGPROF a viable alternative? Sounds a bit drastic. I doubt it, as it would probably break POSIX semantics. Threaded applications then wouldn't be able to use SIGPROF. A new signal or two, used only for the threads library would be better. I think Solaris uses a set of signals reserved just for the threads library. I think we're already max'd out with signals though. Is there any intention of allowing more than 32 signals? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 13:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27756 for freebsd-current-outgoing; Thu, 29 Oct 1998 13:52:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27676 for ; Thu, 29 Oct 1998 13:51:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id NAA29227; Thu, 29 Oct 1998 13:51:33 -0800 (PST) (envelope-from obrien) Message-ID: <19981029135133.P25158@nuxi.com> Date: Thu, 29 Oct 1998 13:51:33 -0800 From: "David O'Brien" To: Garrett Wollman , John Hay Cc: tseidmann@simultan.ch, current@FreeBSD.ORG Subject: Re: IPv6 in -current Reply-To: obrien@NUXI.com References: <19981029014905.E26396@nuxi.com> <199810291238.OAA21028@zibbi.mikom.csir.co.za> <199810291537.KAA00450@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810291537.KAA00450@khavrinen.lcs.mit.edu>; from Garrett Wollman on Thu, Oct 29, 1998 at 10:37:35AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am prefectly happy with the state of the world where we can advance > our technological goals in the context of IPv4, and let other parties > provide an IPv6 implementation. BUT people want IPv6 (for what ever reasons) and putting of the decision which to bring into the tree will only create more fractions. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 13:54:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28259 for freebsd-current-outgoing; Thu, 29 Oct 1998 13:54:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28238 for ; Thu, 29 Oct 1998 13:54:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id NAA29253 for current@FreeBSD.ORG; Thu, 29 Oct 1998 13:54:13 -0800 (PST) (envelope-from obrien) Message-ID: <19981029135412.Q25158@nuxi.com> Date: Thu, 29 Oct 1998 13:54:12 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: IPv6 in -current Reply-To: obrien@NUXI.com References: <19981029014905.E26396@nuxi.com> <199810291238.OAA21028@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810291238.OAA21028@zibbi.mikom.csir.co.za>; from John Hay on Thu, Oct 29, 1998 at 02:38:14PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > with it. One of the advantages (for me) about the KAME stack is that we > also get their IPSEC stuff, while with INRIA being in France, it makes IMHO, this is a big issue. We are trying to correct the insecurities of the existing protocols. W/o IPSec we are emasculating these efforts. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 14:36:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03342 for freebsd-current-outgoing; Thu, 29 Oct 1998 14:36:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shasta.wstein.com (shasta.wstein.com [206.163.206.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03323; Thu, 29 Oct 1998 14:36:08 -0800 (PST) (envelope-from joes@shasta.wstein.com) Received: (from joes@localhost) by shasta.wstein.com (8.9.1/8.9.1) id OAA05082; Thu, 29 Oct 1998 14:36:00 -0800 (PST) (envelope-from joes) From: Joseph Stein Message-Id: <199810292236.OAA05082@shasta.wstein.com> Subject: Question about making the world To: freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Date: Thu, 29 Oct 1998 14:36:00 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made the move to 3.0, and I've been thinking, "What kind of loose junk is still hanging around the hierarchy from when I was running 2.1.0?" So I cleaned up the file systems (rather thoroughly!) Deleted inadvertantly the files for groff... No problem, I'll just make world It barfed, 'cause it couldn't find the files I was trying to replace. :( I finally got around it by unpacking the bin dist over my system and that seems to have cured it (making appropriate back ups, of course). Any ideas whether this really *is* a bug, or just something that needs to be fixed somewhere in the Makefile's or .mk files? thanks in advance for any ideas, joe -- Joseph Stein; Beaverton, Oregon USA email: joes@wstein.com Finger joes@shasta.wstein.com for contact information and PGP Public Key! Oregon FirePage http://www.ofp.org [OFP-504] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 14:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05248 for freebsd-current-outgoing; Thu, 29 Oct 1998 14:47:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05230 for ; Thu, 29 Oct 1998 14:47:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00372; Thu, 29 Oct 1998 14:46:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292246.OAA00372@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Richard Seaman, Jr." cc: "current@FreeBSD.ORG" , "eischen@vigrid.com" , "info@highwind.com" Subject: Kernel threading (was Re: Thread Scheduler bug) In-reply-to: Your message of "Thu, 29 Oct 1998 10:25:02 EST." <199810291625.KAA14241@ns.tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 14:46:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 29 Oct 1998 11:10:06 -0500 (EST), Daniel Eischen wrote: > Of course, it we had kernel threads, the pthreads code would be > a *lot* simpler and maybe less prone to bugs, the kernel would > do the preemption for us, and context switches would be much > faster than the current user thread implementation. :) > > I've been poking around in the code, and I'd guess that a > uniprocessor kernel threads implementation wouldn't involve > all that much work. However, I understand there's are fair > amount of kernel work that needs to be done for SMP kernel > threads. My suggestion to you: get started. Once you run into the SMP-related issues, you'll find that there are people that can help you. But if you wait for an SMP-kernel-thread-guru to materialise from nowhere, we're never going to get anywhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 14:48:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05417 for freebsd-current-outgoing; Thu, 29 Oct 1998 14:48:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05403 for ; Thu, 29 Oct 1998 14:48:24 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id OAA05813; Thu, 29 Oct 1998 14:47:42 -0800 (PST) (envelope-from jdp) Message-Id: <199810292247.OAA05813@austin.polstra.com> To: asmodai@wxs.nl Subject: Re: Another compile error In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 29 Oct 1998 14:47:42 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jeroen Ruigrok/Asmodai wrote: > install -c -o root -g wheel -m 644 drivers/make_device_driver.sh,v /usr/share/ex > amples/drivers/make_device_driver.sh,v > install -c -o root -g wheel -m 644 etc/Attic/ttys,v /usr/share/examples/etc/Atti > c/ttys,v > install: /usr/share/examples/etc/Attic/ttys,v: No such file or directory > *** Error code 71 > > Am I wrong into thinking that Attic isn't needed for the example directory in > /usr/share/examples/etc or am I just blabbering? =) > > If someone could at least enlighten me about Attic. It looks to me like you did a CVSup update using cvs mode (no "tag" or "data" specification in your cvsupfile), and spammed your /usr/src tree with a bunch of RCS files. I'd suggest that you study the CVSup tutorial in the FreeBSD Handbook, the CVSup FAQ at , and the cvsup(1) manual page. Pay special attention to the difference between "cvs mode" and "checkout mode". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 14:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05714 for freebsd-current-outgoing; Thu, 29 Oct 1998 14:50:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05635 for ; Thu, 29 Oct 1998 14:50:06 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id WAA01708; Thu, 29 Oct 1998 22:47:04 GMT (envelope-from nik) Message-ID: <19981029224704.64945@nothing-going-on.org> Date: Thu, 29 Oct 1998 22:47:04 +0000 From: Nik Clayton To: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: Plugging a FreeBSD server to the net: need advice References: <003401be036e$086894b0$0d787880@apex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <003401be036e$086894b0$0d787880@apex>; from Carlos C. Tapang on Thu, Oct 29, 1998 at 10:57:52AM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 10:57:52AM -0800, Carlos C. Tapang wrote: > to decide on which version of FreeBSD to use. Should I go with 2.2.7 or 3.0. > Is 3.0 ready for it? 2.2.7. 3.0 is almost certainly ready for it. However, since you're (apparently) new to this, save yourself the hassle. You don't need the bleeding edge. > The server will be a web, mail, and ftp server. Will I get double mileage > with having a 2-processor SMP system? Not on 2.2.7 (it doesn't do SMP). And even on 3.0, web, mail, and ftp are not CPU intensive tasks (unless you have *lots* of complex CGI, even then something like mod_perl in the Apache server (if they're Perl scripts and you're running Apache) is a better solution. > Is FreeBSD.ORG behind a firewall? Yes. > If it's not, then my server probably does > not need to be behind a firewall. (I am paranoid about malignant attacks, > but if FreeBSD.ORG can survive, so should my server.) Be paranoid. Firewall. Only allow access to ports you know about. Drop packets from 'unroutable' nets immediately (10/8, 172.16/16, 192.168/16). Log odd connections to either a seperate machine, or (better yet) to a line printer somewhere. Install tcp_wrappers from the ports, and wrap services. Hope that helps, N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 14:51:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06049 for freebsd-current-outgoing; Thu, 29 Oct 1998 14:51:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05912 for ; Thu, 29 Oct 1998 14:51:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00408; Thu, 29 Oct 1998 14:50:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292250.OAA00408@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Parag Patel cc: current@FreeBSD.ORG, tjm@codegen.com, eric@needhams.com Subject: Re: Mod to doscmd's port.c to directly access parallel ports In-reply-to: Your message of "Thu, 29 Oct 1998 10:17:04 PST." <199810291817.KAA24369@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 14:50:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It was just pointed out to me that I'd screwed up the mod for iounmap(). > > > static void > > iounmap(int port, int cnt) > > { > >! if (port + cnt >= MAXPORT) { > >! errno = ERANGE; > >! goto bad; > >! } > >! if (i386_set_ioperm(port, cnt, 1) < 0) { > ^^^ > 0 > >! bad: > >! perror("iounmap"); > >! quit(1); > >! } > > } > > Oops. I've submitted the proper fix using send-pr. Thanks! > > Actually, this rather slows down the whole port-access quite a bit. I'm inclined to set the port access on at startup and off on exit. That would definitely be the preferred option. Please update the PR when you've made the changes; I have an interest in seeing this work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 16:12:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19587 for freebsd-current-outgoing; Thu, 29 Oct 1998 16:12:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19560; Thu, 29 Oct 1998 16:12:04 -0800 (PST) (envelope-from jseger@jseger.scds.com) Received: from jseger.scds.com (localhost.scds.com [127.0.0.1]) by freebsd.scds.com (8.9.1/8.8.8) with ESMTP id TAA02893; Thu, 29 Oct 1998 19:10:56 -0500 (EST) (envelope-from jseger@jseger.scds.com) Message-Id: <199810300010.TAA02893@freebsd.scds.com> To: Mike Smith cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-reply-to: Your message of "Wed, 28 Oct 1998 12:37:51 PST." <199810282037.MAA00616@dingo.cdrom.com> Date: Thu, 29 Oct 1998 19:10:56 -0500 From: "Justin M. Seger" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem is obly on one machine; the port-builder. That one clearly > > has KerberosIV (eBones) enabled, and the X is Kerberos-enabled. As > > a consequence, all X-ports are Kerberos-enabled. > > > > Fix 1 thing, fix'em all. What machine is used to build all the ports? > > Bento was used this time around. I think Justin is probably feeling > pretty embarrassed about now. Ouch. Yeppers. Sorry about that guys. I was in a rush to setup a new chroot'ed environ to get 3.0-RELEASE packages out the door and overlooked disabling Kerberos :( Anyway, it's in my procedure now and shouldn't happen again. Sorry, -Justin Seger- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 16:25:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20929 for freebsd-current-outgoing; Thu, 29 Oct 1998 16:25:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20723 for ; Thu, 29 Oct 1998 16:24:59 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA29999; Thu, 29 Oct 1998 19:24:34 -0500 (EST) Date: Thu, 29 Oct 1998 19:24:34 -0500 (EST) From: Brian Feldman To: John Hay cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810291858.UAA26651@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would look Really Good on, say, 3.1-RELEASE release notes to say: * Full IPv6 implementation in-kernel and libc! Just a thought :) Cheersm Brian Feldman On Thu, 29 Oct 1998, John Hay wrote: > > > > > we can get a version of IPv6 standard in FreeBSD. I have been looking at > > > (and using) the KAME stuff the last few weeks and am quite impressed > > > with it. One of the advantages (for me) about the KAME stack is that we > > > also get their IPSEC stuff, while with INRIA being in France, it makes > > > things a little more complicated. > > > > Don't forget there's also the group of people who worked on the NRL > > stack.... > > I didn't. I explicitly left them about because of two reasons. Because > I'm not in the USA and I'm not a USA citizen, I can't get hold of it. > Then also according to their web site they only cater for BSDI, NetBSD > and Linux, with a promise that they will support FreeBSD in their next > release. > > But I don't really mind which one we are using. Any one that is part > of FreeBSD will make my life easier. Most of the stacks available > only support a specific release, so if you are running stable or > current you have to constantly merge. (Well actually current is out > of the question at the moment because none of them support 3.0 let > alone current and that is actually where it would like it, because > most of our test boxes run current.) > > > The other question that people have to consider whenever IPv6 comes > > up: with whom are you going to communicate? Right now, there is no > > globally-routed IPv6 infrastructure, and there is unlikely to be any, > > any time soon (IOS 12, anyone?). I am prefectly happy with the state > > of the world where we can advance our technological goals in the > > context of IPv4, and let other parties provide an IPv6 implementation. > > While it is not native, the 6bone is up and running and people are using > it to test compatability of the different stacks and other things. Our > side of the 6bone tunnel is a FreeBSD box running the KAME stack and the > other side is a Cisco somewhere in the USA. > > I do agree that IPv4 will be the main protocol for while, the other side > is that IPv6 is coming and we shouldn't wait too long to incorporate it. > By having a standard stack we can unite the FreeBSD IPv6 users and get > it better tested than currently where we are split up between the > different stacks. > > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 16:33:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22340 for freebsd-current-outgoing; Thu, 29 Oct 1998 16:33:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22333 for ; Thu, 29 Oct 1998 16:33:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01188; Thu, 29 Oct 1998 16:30:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300030.QAA01188@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: John Hay , Garrett Wollman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-reply-to: Your message of "Thu, 29 Oct 1998 19:24:34 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 16:30:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would look Really Good on, say, 3.1-RELEASE release notes to say: > * Full IPv6 implementation in-kernel and libc! > Just a thought :) It would suck, however, if the consensus was that we rushed the integration just to get the check-mark item. The people in the driving seat are acutely aware of the pros and cons, and I'm inclined to accept their judgement (while also accepting that supportive noise from the userbase such as yours is also *extremely* valuable). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 16:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23168 for freebsd-current-outgoing; Thu, 29 Oct 1998 16:39:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23151 for ; Thu, 29 Oct 1998 16:39:10 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA00253; Thu, 29 Oct 1998 19:38:41 -0500 (EST) Date: Thu, 29 Oct 1998 19:38:40 -0500 (EST) From: Brian Feldman To: Mike Smith cc: John Hay , Garrett Wollman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810300030.QAA01188@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I can understand this. I mean, when things get rushed, noone is happy (I won't open the 3.0 can of worms, but I'm glad Jordan (or whoever else did them?) had the guts to say it is a _developer_release_! Damn nestea bug...)) I am expressing my sentiments that this would be a GREAT selling point for a later FreeBSD release, just like CAM, SoftUpdates, new VM system, SMP,the new boot-loader, ELF, all sorts of code rewirtes, etc. are great selling points for 3.x. Whenever a regional ISP does IPv6, I wouldn't mind at all in testing/implementing IPv6 in various parts of the system (and yes, I mean modem ISP *sigh*). Let's not rush it, but we should get KAME or another IPv6 stack in a vendor branch as soon as feasible/comfortable. Cheers, Brian Feldman On Thu, 29 Oct 1998, Mike Smith wrote: > > It would look Really Good on, say, 3.1-RELEASE release notes to say: > > * Full IPv6 implementation in-kernel and libc! > > Just a thought :) > > It would suck, however, if the consensus was that we rushed the > integration just to get the check-mark item. The people in the driving > seat are acutely aware of the pros and cons, and I'm inclined to accept > their judgement (while also accepting that supportive noise from the > userbase such as yours is also *extremely* valuable). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 16:50:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24316 for freebsd-current-outgoing; Thu, 29 Oct 1998 16:50:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24311 for ; Thu, 29 Oct 1998 16:50:34 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id TAA25978; Thu, 29 Oct 1998 19:52:37 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 29 Oct 1998 19:52:37 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Smith cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810300030.QAA01188@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't at least 3 commercial versions of unix ship with IPv6? (AIX and a few others) However I'm not sure what their definition of IPv6 is. They might just have the "check mark on the shrinkwrap" you're talking about.... :) Hasn't the tradition been BSD implements something first, then everyone else uses/emulates/implements it? FreeBSD should keep its place as a leader in OS innovation and design concepts, it should not become a follower in the OS world. I trust the FreeBSD team _much_ more with the future of UNIX standards than any other group of programmers/computer standards orginization out there. mmap, sockets, bpf, etc... Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Thu, 29 Oct 1998, Mike Smith wrote: > > It would look Really Good on, say, 3.1-RELEASE release notes to say: > > * Full IPv6 implementation in-kernel and libc! > > Just a thought :) > > It would suck, however, if the consensus was that we rushed the > integration just to get the check-mark item. The people in the driving > seat are acutely aware of the pros and cons, and I'm inclined to accept > their judgement (while also accepting that supportive noise from the > userbase such as yours is also *extremely* valuable). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 17:19:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28701 for freebsd-current-outgoing; Thu, 29 Oct 1998 17:19:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28696 for ; Thu, 29 Oct 1998 17:19:53 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id CAA01119 for current@FreeBSD.ORG; Fri, 30 Oct 1998 02:19:49 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 9ED18145A; Thu, 29 Oct 1998 19:36:19 +0100 (CET) Date: Thu, 29 Oct 1998 19:36:19 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: IPv6 in -current Message-ID: <19981029193619.A25691@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <3635F22D.1A6B9EB4@simultan.ch> <19981029014905.E26396@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <19981029014905.E26396@nuxi.com>; from David E . O'Brien on Thu, Oct 29, 1998 at 01:49:05AM -0800 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4731 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E . O'Brien: > But some of the KAME developers have commit privs. Thus they can > maintain the code. This bonus should not be overlooked. And it would be easy to add Francis to our list of committers so the argument is moot :) I don't know of they intent to get together (KAME and Francis) but be assured they know each others very well (just talked to Francis today). Francis told me he planned a 2.2.8 release (as soon as it gets released of course :)) then a 3.0 one. In the mean time, an old (2.2.6 I think) version of the code was converted for CURRENT by one of us (Pierre Beyssac, committer too) and another person has proposed to do it again (for 3.0-RELEASE) in this list. So I would say there is support for the INRIA code too. As for the encryption stuff, it would be easy to put on our international repository. Another point to consider is that NetBSD took Francis' code for the next release... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 18:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14030 for freebsd-current-outgoing; Thu, 29 Oct 1998 18:30:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13976 for ; Thu, 29 Oct 1998 18:30:47 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id NAA01785; Fri, 30 Oct 1998 13:30:19 +1100 (EST) X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs Date: Fri, 30 Oct 1998 13:30:18 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Another compile error In-Reply-To: <199810292247.OAA05813@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... I'd suggest that you > study the CVSup tutorial in the FreeBSD Handbook, the CVSup FAQ at > , and the cvsup(1) > manual page. ^^^^^^^^ :-) zippy# apropos cvs cvs(1) - Concurrent Versions System cvs(5) - Concurrent Versions System support files cvsbug(8) - send problem report (PR) about CVS to a central support site cvsinit(8) - Concurrent Versions System repository initialization script mkmodules(1) - Rebuild modules database for CVS -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 19:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22247 for freebsd-current-outgoing; Thu, 29 Oct 1998 19:02:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22196 for ; Thu, 29 Oct 1998 19:02:40 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id TAA07259; Thu, 29 Oct 1998 19:02:31 -0800 (PST) (envelope-from jdp) Message-Id: <199810300302.TAA07259@austin.polstra.com> To: Andy Farkas cc: current@FreeBSD.ORG Subject: Re: Another compile error In-reply-to: Your message of "Fri, 30 Oct 1998 13:30:18 +1100." Date: Thu, 29 Oct 1998 19:02:30 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ... I'd suggest that you > > study the CVSup tutorial in the FreeBSD Handbook, the CVSup FAQ at > > , and the cvsup(1) > > manual page. ^^^^^^^^ > > :-) > > zippy# apropos cvs > cvs(1) - Concurrent Versions System > cvs(5) - Concurrent Versions System support files > cvsbug(8) - send problem report (PR) about CVS to a central support site > cvsinit(8) - Concurrent Versions System repository initialization script > mkmodules(1) - Rebuild modules database for CVS Sorry, but the joke's on you. It's in /usr/local/man/man1 and it gets installed when you install CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 19:07:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25987 for freebsd-current-outgoing; Thu, 29 Oct 1998 19:07:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25944 for ; Thu, 29 Oct 1998 19:07:22 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA12445 for current@FreeBSD.ORG; Fri, 30 Oct 1998 04:07:16 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 921001556; Fri, 30 Oct 1998 02:22:05 +0100 (CET) Date: Fri, 30 Oct 1998 02:22:03 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: IPv6 in -current Message-ID: <19981030022203.A1073@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199810300030.QAA01188@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Alfred Perlstein on Thu, Oct 29, 1998 at 07:52:37PM -0500 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4731 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alfred Perlstein: > Don't at least 3 commercial versions of unix ship with IPv6? > (AIX and a few others) AIX does (they integrated the INRIA stuff), Solaris 2.7 (or whatever they'll call it) supposedly will has one, NetBSD has the INRIA stuff too (for next release) and Linux has been shipping with IPv6 for quite some time now. DEC UNIX has its own stack too (although it is not shipped I think). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 19:18:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08378 for freebsd-current-outgoing; Thu, 29 Oct 1998 19:18:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08237 for ; Thu, 29 Oct 1998 19:18:50 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id OAA01857; Fri, 30 Oct 1998 14:18:03 +1100 (EST) X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs Date: Fri, 30 Oct 1998 14:18:03 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Another compile error In-Reply-To: <199810300302.TAA07259@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, John Polstra wrote: > Sorry, but the joke's on you. It's in /usr/local/man/man1 and it > gets installed when you install CVSup. > Please feel free to sling [insert favourite gooey stuff here] this direction anytime for the next few days .... :-( -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 19:40:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29587 for freebsd-current-outgoing; Thu, 29 Oct 1998 19:40:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29495 for ; Thu, 29 Oct 1998 19:40:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id TAA03491; Thu, 29 Oct 1998 19:39:38 -0800 (PST) (envelope-from obrien) Message-ID: <19981029193938.E25158@nuxi.com> Date: Thu, 29 Oct 1998 19:39:38 -0800 From: "David O'Brien" To: Doug White , Mike Smith Cc: current@FreeBSD.ORG Subject: Re: 3.0 installation problems Reply-To: obrien@NUXI.com References: <199810242259.PAA25534@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug White on Tue, Oct 27, 1998 at 03:02:49PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not route, it's the (unannounced) nameserver lookup for the FTP site > that immediately follows the route add. If you turn debugging on and I've added output to the debugging screen (ALT-F2) if the DEBUG option is turned on. Hopefully this will help us pin it down. If perfered, I can make the debug output appear on the alt-F2 screen even if the DEBUG option isn't set. This should appear at at daily current SNAP by tomarrow (Friday). -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 20:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24507 for freebsd-current-outgoing; Thu, 29 Oct 1998 20:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles148.castles.com [208.214.165.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24502 for ; Thu, 29 Oct 1998 20:12:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00414; Thu, 29 Oct 1998 20:11:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300411.UAA00414@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com cc: Doug White , Mike Smith , current@FreeBSD.ORG Subject: Re: 3.0 installation problems In-reply-to: Your message of "Thu, 29 Oct 1998 19:39:38 PST." <19981029193938.E25158@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 20:11:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's not route, it's the (unannounced) nameserver lookup for the FTP site > > that immediately follows the route add. If you turn debugging on and > > I've added output to the debugging screen (ALT-F2) if the DEBUG option is > turned on. Hopefully this will help us pin it down. If perfered, I can > make the debug output appear on the alt-F2 screen even if the DEBUG > option isn't set. > > This should appear at at daily current SNAP by tomarrow (Friday). It should probably actually remove the "adding default route" message and replace it with a "looking for ..." message. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 20:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24929 for freebsd-current-outgoing; Thu, 29 Oct 1998 20:20:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24924 for ; Thu, 29 Oct 1998 20:20:40 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id GAA05125; Fri, 30 Oct 1998 06:20:12 +0200 (SAT) From: John Hay Message-Id: <199810300420.GAA05125@zibbi.mikom.csir.co.za> Subject: Re: IPv6 in -current In-Reply-To: <19981030022203.A1073@keltia.freenix.fr> from Ollivier Robert at "Oct 30, 98 02:22:03 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Fri, 30 Oct 1998 06:20:12 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Alfred Perlstein: > > Don't at least 3 commercial versions of unix ship with IPv6? > > (AIX and a few others) > > AIX does (they integrated the INRIA stuff), Solaris 2.7 (or whatever > they'll call it) supposedly will has one, NetBSD has the INRIA stuff too > (for next release) and Linux has been shipping with IPv6 for quite some > time now. > > DEC UNIX has its own stack too (although it is not shipped I think). BSDI 4.0 also have an IPv6 stack. According to the NRL web pages it's the NRL stack that is being used. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 20:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26036 for freebsd-current-outgoing; Thu, 29 Oct 1998 20:33:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26027 for ; Thu, 29 Oct 1998 20:33:45 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id GAA05271; Fri, 30 Oct 1998 06:32:47 +0200 (SAT) From: John Hay Message-Id: <199810300432.GAA05271@zibbi.mikom.csir.co.za> Subject: Re: IPv6 in -current In-Reply-To: <199810300030.QAA01188@dingo.cdrom.com> from Mike Smith at "Oct 29, 98 04:30:12 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 30 Oct 1998 06:32:47 +0200 (SAT) Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It would look Really Good on, say, 3.1-RELEASE release notes to say: > > * Full IPv6 implementation in-kernel and libc! > > Just a thought :) > > It would suck, however, if the consensus was that we rushed the > integration just to get the check-mark item. The people in the driving > seat are acutely aware of the pros and cons, and I'm inclined to accept > their judgement (while also accepting that supportive noise from the > userbase such as yours is also *extremely* valuable). Well it is because I don't want it rushed that I'm talking about it now. It is just after the release with a few months before the next 3.x release and also we have waited until a few other OS vendors have brought versions with IPv6 included and others have anounced that their next version will have it in. That is not rushing, that is running in the middle of the pack. :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 29 22:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06011 for freebsd-current-outgoing; Thu, 29 Oct 1998 22:33:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06006 for ; Thu, 29 Oct 1998 22:33:39 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id HAA29722; Fri, 30 Oct 1998 07:33:27 +0100 (CET) Message-ID: <36395DB5.E8854464@simultan.ch> Date: Fri, 30 Oct 1998 07:33:25 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com CC: current@FreeBSD.ORG Subject: Re: IPv6 in -current References: <19981029014905.E26396@nuxi.com> <199810291238.OAA21028@zibbi.mikom.csir.co.za> <19981029135412.Q25158@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > with it. One of the advantages (for me) about the KAME stack is that we > > also get their IPSEC stuff, while with INRIA being in France, it makes > > IMHO, this is a big issue. We are trying to correct the insecurities of > the existing protocols. W/o IPSec we are emasculating these efforts. I agree; this _is_ a big issue. We'd get IPsec with INRIA, too. > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 00:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02052 for freebsd-current-outgoing; Fri, 30 Oct 1998 00:06:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02013 for ; Fri, 30 Oct 1998 00:06:28 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg134-015.ricochet.net (mg134-015.ricochet.net [204.179.134.15]) by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id CAA20626; Fri, 30 Oct 1998 02:05:14 -0600 (CST) Date: Fri, 30 Oct 1998 00:04:23 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Brian Feldman cc: Mike Smith , John Hay , Garrett Wollman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I talked to the KAME folks a while back about helping to integrate their work into -current. The response I received was that they were integrating into one of the 3.0-BETA snapshots (unsure of which one), and that any patches I had to bring it up to -current would be useful once that integration was complete. My life's been kinda turned upside down recently, so I've been too busy to work on this (and other things I sorta committed to for FreeBSD) I'm not sure of the status on their integration. I'd certainly be willing to help out with testing, and when my life settles down a bit, I might be able to help with implementation, too. I'm another one that would really like to see IPv6 and IPSEC in FreeBSD. On Thu, 29 Oct 1998, Brian Feldman wrote: > Yes, I can understand this. I mean, when things get rushed, noone is happy > (I won't open the 3.0 can of worms, but I'm glad Jordan (or whoever else > did them?) had the guts to say it is a _developer_release_! Damn nestea > bug...)) I am expressing my sentiments that this would be a GREAT selling > point for a later FreeBSD release, just like CAM, SoftUpdates, new VM > system, SMP,the new boot-loader, ELF, all sorts of code rewirtes, etc. are > great selling points for 3.x. Whenever a regional ISP does IPv6, I > wouldn't mind at all in testing/implementing IPv6 in various parts of the > system (and yes, I mean modem ISP *sigh*). Let's not rush it, but we > should get KAME or another IPv6 stack in a vendor branch as soon as > feasible/comfortable. > > Cheers, > Brian Feldman > > On Thu, 29 Oct 1998, Mike Smith wrote: > > > > It would look Really Good on, say, 3.1-RELEASE release notes to say: > > > * Full IPv6 implementation in-kernel and libc! > > > Just a thought :) > > > > It would suck, however, if the consensus was that we rushed the > > integration just to get the check-mark item. The people in the driving > > seat are acutely aware of the pros and cons, and I'm inclined to accept > > their judgement (while also accepting that supportive noise from the > > userbase such as yours is also *extremely* valuable). > > > > -- > > \\ Sometimes you're ahead, \\ Mike Smith > > \\ sometimes you're behind. \\ mike@smith.net.au > > \\ The race is long, and in the \\ msmith@freebsd.org > > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Christopher Nielsen Scient: The Art and Science of Electronic Business cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 02:12:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13936 for freebsd-current-outgoing; Fri, 30 Oct 1998 02:12:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jkoshy@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13918; Fri, 30 Oct 1998 02:12:13 -0800 (PST) (envelope-from jkoshy) Date: Fri, 30 Oct 1998 02:12:13 -0800 (PST) From: Joseph Koshy Message-Id: <199810301012.CAA13918@hub.freebsd.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG cc: Subject: PRs/fixes to be merged to -stable? Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, If you have any PRs (or other fixes in -current) that you would like to see merged into 2.2-STABLE, please drop me a note (with a cc to committers@freebsd.org). Regards, Koshy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 02:21:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14604 for freebsd-current-outgoing; Fri, 30 Oct 1998 02:21:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14585 for ; Fri, 30 Oct 1998 02:21:38 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA09006; Fri, 30 Oct 1998 21:21:25 +1100 Date: Fri, 30 Oct 1998 21:21:25 +1100 From: Bruce Evans Message-Id: <199810301021.VAA09006@godzilla.zeta.org.au> To: bright@hotjobs.com, current@FreeBSD.ORG Subject: Re: NFS broken with large files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i have /com nfs mounted: >from fstab: >xxx:/com /com nfs rw,tcp,bg,nfsv3 0 0 > >ii'm trying to manipulate this file: >/com/bkup % ls -l www1-local.tar >-rw-r--r-- 1 root wheel 2162790400 Oct 27 21:56 www1-local.tar >... >I thought NFSv3 provided for very large file support? >not only that, this file is not _that_ large... just 2gigs. Only in theory. Known bugs include gratuitous truncation of the file size to u_long: nfs/nfs_bio.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_subs.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_subs.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)vap->va_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)np->n_size); The casts are K&R support for the 4.4Lite vnode_pager_setsize() which doesn't only supports u_long sizes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 02:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15670 for freebsd-current-outgoing; Fri, 30 Oct 1998 02:31:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15662 for ; Fri, 30 Oct 1998 02:31:34 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id LAA28200; Fri, 30 Oct 1998 11:30:57 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA15504; Fri, 30 Oct 1998 11:30:51 +0100 (MET) Message-ID: <19981030113051.46830@follo.net> Date: Fri, 30 Oct 1998 11:30:51 +0100 From: Eivind Eklund To: Nik Clayton , "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: Plugging a FreeBSD server to the net: need advice References: <003401be036e$086894b0$0d787880@apex> <19981029224704.64945@nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19981029224704.64945@nothing-going-on.org>; from Nik Clayton on Thu, Oct 29, 1998 at 10:47:04PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 10:47:04PM +0000, Nik Clayton wrote: > On Thu, Oct 29, 1998 at 10:57:52AM -0800, Carlos C. Tapang wrote: > > Is FreeBSD.ORG behind a firewall? > > Yes. As far as I know, this is incorrect. I'm not able see it with traceroute, at least, and there isn't anything that look like one... > > If it's not, then my server probably does > > not need to be behind a firewall. (I am paranoid about malignant attacks, > > but if FreeBSD.ORG can survive, so should my server.) > > Be paranoid. Firewall. Only allow access to ports you know about. Drop > packets from 'unroutable' nets immediately (10/8, 172.16/16, 192.168/16). > Log odd connections to either a seperate machine, or (better yet) to a > line printer somewhere. Install tcp_wrappers from the ports, and wrap > services. This is always good advice. And don't run more services than you _absolutely_ need. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 03:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19857 for freebsd-current-outgoing; Fri, 30 Oct 1998 03:10:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19852 for ; Fri, 30 Oct 1998 03:10:25 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.30.193]) by atena.eurocontrol.fr (8.9.1/8.9.1/atena-1.1/nospam) with ESMTP id MAA08111 for ; Fri, 30 Oct 1998 12:10:10 +0100 (MET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (VMailer, from userid 1193) id 5AE5910C; Fri, 30 Oct 1998 12:10:09 +0100 (CET) Date: Fri, 30 Oct 1998 12:10:09 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: LKM fastvid Message-ID: <19981030121009.D9648@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody have an updated version of the Fastvid LKM... ? -- Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 03:25:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21061 for freebsd-current-outgoing; Fri, 30 Oct 1998 03:25:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf43.cruzers.com [205.215.232.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21056 for ; Fri, 30 Oct 1998 03:25:57 -0800 (PST) (envelope-from brian@top.worldcontrol.com) Received: (from brian@localhost) by top.worldcontrol.com (8.9.1/8.8.8) id LAA00369 for freebsd-current@freebsd.org; Fri, 30 Oct 1998 11:26:45 GMT (envelope-from brian) Date: Fri, 30 Oct 1998 03:26:45 -0800 From: Brian Litzinger To: freebsd-current@FreeBSD.ORG Subject: pcm0: /dev/dsp: Undefined error: 0 Message-ID: <19981030032627.A356@top.worldcontrol.com> Mail-Followup-To: freebsd-current@top.worldcontrol.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.9i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just starting using the pcm audio driver on my new laptop. The sound system is the Yamaha YMF 715 chipset which seems to have emulation for everything. It is detected as: ... try to identify the yamaha pcm0 at 0x530 irq 9 drq 0 flags 0xa200 on isa mss_attach 0 at 0x530 irq 9 dma 0:0 flags 0xa200 And much works: xanim, rvplayer. however a simple utility dies: brian@top>vplay -S -s 22050 -b 8 < l.dsp Playing raw data : Speed 22050 Hz Stereo ... /dev/dsp: Undefined error: 0 (I hate 'Undefined error: 0' by the way) Most of the audio settings however were made as: brian@top>cat >/dev/dsp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 07:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20690 for freebsd-current-outgoing; Fri, 30 Oct 1998 07:20:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20684 for ; Fri, 30 Oct 1998 07:20:53 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id KAA12632; Fri, 30 Oct 1998 10:19:54 -0500 (EST) Date: Fri, 30 Oct 1998 10:19:54 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Garrett Wollman cc: John Hay , obrien@NUXI.com, tseidmann@simultan.ch, current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810291537.KAA00450@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Garrett Wollman wrote: > > we can get a version of IPv6 standard in FreeBSD. I have been looking at > > (and using) the KAME stuff the last few weeks and am quite impressed > > with it. One of the advantages (for me) about the KAME stack is that we > > also get their IPSEC stuff, while with INRIA being in France, it makes > > things a little more complicated. > > Don't forget there's also the group of people who worked on the NRL > stack.... > > The other question that people have to consider whenever IPv6 comes > up: with whom are you going to communicate? Right now, there is no > globally-routed IPv6 infrastructure, and there is unlikely to be any, > any time soon (IOS 12, anyone?). I am prefectly happy with the state > of the world where we can advance our technological goals in the > context of IPv4, and let other parties provide an IPv6 implementation. On the other hand, there are a lot of people who use FreeBSD for network research and development (well, certainly at CMU, and I assume other places). As time goes by, will we start to lose some of these researchers because we don't offer the next generation of network support? I admit that I was extremely impressed when I looked at the BSD/OS 4.0 release notes and saw so many of the features I would look for in a network operating system/server platform (good SMP, IPsec, IPv6, and many many other new features). I would guess that relatively few people actually use a number of these features, but it is nice to know they are available. On the other hand, it is useful to note that a number of groups have been developing IPv6 and IPsec on FreeBSD, and we don't want to leave them high and dry, as it were. One of the issues that I've raised in the Coda group previously is adaptability of the current Coda software for use in new network environments, including IPv6 and IPsec. I don't have the time to integrate IPsec and IPv6 into an operating system, but I would benefit from an operating system where they were already present. :) Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 08:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25223 for freebsd-current-outgoing; Fri, 30 Oct 1998 08:13:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25218 for ; Fri, 30 Oct 1998 08:13:15 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA04296; Fri, 30 Oct 1998 11:13:05 -0500 (EST) (envelope-from wollman) Date: Fri, 30 Oct 1998 11:13:05 -0500 (EST) From: Garrett Wollman Message-Id: <199810301613.LAA04296@khavrinen.lcs.mit.edu> To: Brian Feldman Cc: John Hay , Garrett Wollman , current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: References: <199810291858.UAA26651@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > It would look Really Good on, say, 3.1-RELEASE release notes to say: > * Full IPv6 implementation in-kernel and libc! It would look much better to say: * Complete single-copy TCP/IP implementation -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 08:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27745 for freebsd-current-outgoing; Fri, 30 Oct 1998 08:35:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27739 for ; Fri, 30 Oct 1998 08:35:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00359; Fri, 30 Oct 1998 08:33:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301633.IAA00359@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Nik Clayton , "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: Plugging a FreeBSD server to the net: need advice In-reply-to: Your message of "Fri, 30 Oct 1998 11:30:51 +0100." <19981030113051.46830@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 08:33:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Oct 29, 1998 at 10:47:04PM +0000, Nik Clayton wrote: > > On Thu, Oct 29, 1998 at 10:57:52AM -0800, Carlos C. Tapang wrote: > > > Is FreeBSD.ORG behind a firewall? > > > > Yes. > > As far as I know, this is incorrect. I'm not able see it with > traceroute, at least, and there isn't anything that look like one... It's actually behind several filters; one at CRL and another one here. Neither of them are "fish-ass-tight"; our primary concern is actually DoS attacks eating the T1. It'll close up more as we tighten the security on the cluster, but because we need to allow external logins it'll never be as tight as would be desired. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 08:51:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29459 for freebsd-current-outgoing; Fri, 30 Oct 1998 08:51:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29454 for ; Fri, 30 Oct 1998 08:51:05 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA11828; Fri, 30 Oct 1998 08:50:56 -0800 (PST) (envelope-from jdp) Message-Id: <199810301650.IAA11828@austin.polstra.com> To: nik@nothing-going-on.demon.co.uk Subject: Re: Plugging a FreeBSD server to the net: need advice In-Reply-To: <19981029224704.64945@nothing-going-on.org> References: <003401be036e$086894b0$0d787880@apex> <19981029224704.64945@nothing-going-on.org> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 30 Oct 1998 08:50:56 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Minor correction: > Be paranoid. Firewall. Only allow access to ports you know about. Drop > packets from 'unroutable' nets immediately (10/8, 172.16/16, 192.168/16). ^^ || 12 John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08434 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:17:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08427 for ; Fri, 30 Oct 1998 10:17:17 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id KAA12367 for ; Fri, 30 Oct 1998 10:17:11 -0800 (PST) (envelope-from jdp) Message-Id: <199810301817.KAA12367@austin.polstra.com> To: current@FreeBSD.ORG Subject: New boot loader and alternate kernels Date: Fri, 30 Oct 1998 10:17:11 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question about the new boot loader. My /boot/boot.conf file looks like this: load /kernel autoboot 10 Now suppose I want to boot an alternate kernel. To do that, it seems I have to interrupt the autoboot sequence by pressing a key, then do "unload /kernel", then do "boot /kernel.alt". Is that right? It's the unload step that I'm wondering about. Can it be avoided? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09971 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:30:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09958 for ; Fri, 30 Oct 1998 10:30:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01109; Fri, 30 Oct 1998 10:29:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301829.KAA01109@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:17:11 PST." <199810301817.KAA12367@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 10:29:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a question about the new boot loader. My /boot/boot.conf > file looks like this: > > load /kernel > autoboot 10 > > Now suppose I want to boot an alternate kernel. To do that, it seems > I have to interrupt the autoboot sequence by pressing a key, then do > "unload /kernel", then do "boot /kernel.alt". Is that right? It's > the unload step that I'm wondering about. Can it be avoided? Unloading is an all or nothing proposition; it throws everything away (it doesn't take any arguments). This avoids having holes in the loaded region, as well as having to deal with dependancy issues. You can use the fact that 'boot' and 'autoboot' will look for a kernel for you to avoid having to load a kernel explicitly in your default case. The variable $bootfile is a comma-separated list of kernel names to try to boot. By default, it's implicitly set to 'kernel,kernel.old'. In your current case, you could leave your /boot/boot.conf file empty, because the default behaviour is to wait 10 seconds and then boot. If you wanted the equivalent of load /kernel.test autoboot 10 but without needing to unload the kernel, you could say: set bootfile=/kernel.test autoboot 10 (Yes, the comma-separated list sucks. I'm not sure what would be a better approach; I had reasons for not using semicolons that I've now forgotten.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:36:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10439 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:36:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10432 for ; Fri, 30 Oct 1998 10:36:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01153; Fri, 30 Oct 1998 10:34:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301834.KAA01153@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: John Polstra , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:29:58 PST." <199810301829.KAA01109@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 10:34:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a question about the new boot loader. My /boot/boot.conf > > file looks like this: > > > > load /kernel > > autoboot 10 > > > > Now suppose I want to boot an alternate kernel. To do that, it seems > > I have to interrupt the autoboot sequence by pressing a key, then do > > "unload /kernel", then do "boot /kernel.alt". Is that right? It's > > the unload step that I'm wondering about. Can it be avoided? > > Unloading is an all or nothing proposition; it throws everything away > (it doesn't take any arguments). This avoids having holes in the > loaded region, as well as having to deal with dependancy issues. I also forgot to point out that in the more complex case: load /kernel load /modules/foo.ko ... autoboot 10 you could just add unload to the end of the script. There's probably a call for a 'bootmodules' variable as well; until we get more people using this and asking for features I'm not sure what's worth adding and what's just fluff. How many people would be interested in labels and conditional branches, for example? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11293 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:44:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11288 for ; Fri, 30 Oct 1998 10:44:21 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA17331; Fri, 30 Oct 1998 10:44:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: John Polstra , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:34:59 PST." <199810301834.KAA01153@dingo.cdrom.com> Date: Fri, 30 Oct 1998 10:44:04 -0800 Message-ID: <17327.909773044@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How many people would be interested in labels and conditional branches, > for example? Probably quite a few, but then you get into the predictable debate of "why not just add atlast to the loader? It's only 7K!" :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11516 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:46:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11501 for ; Fri, 30 Oct 1998 10:46:11 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id NAA08188; Fri, 30 Oct 1998 13:48:33 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Fri, 30 Oct 1998 13:48:33 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810301834.KAA01153@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > I also forgot to point out that in the more complex case: > > load /kernel > load /modules/foo.ko > ... > autoboot 10 > > you could just add > > unload > > to the end of the script. > > There's probably a call for a 'bootmodules' variable as well; until we > get more people using this and asking for features I'm not sure what's > worth adding and what's just fluff. > > How many people would be interested in labels and conditional branches, > for example? if the code fits wear^H^H^H^H^H do it. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11706 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:47:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11694 for ; Fri, 30 Oct 1998 10:47:46 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id UAA17640; Fri, 30 Oct 1998 20:47:16 +0200 (SAT) From: John Hay Message-Id: <199810301847.UAA17640@zibbi.mikom.csir.co.za> Subject: Re: IPv6 in -current In-Reply-To: <199810301613.LAA04296@khavrinen.lcs.mit.edu> from Garrett Wollman at "Oct 30, 98 11:13:05 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 30 Oct 1998 20:47:16 +0200 (SAT) Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It would look Really Good on, say, 3.1-RELEASE release notes to say: > > * Full IPv6 implementation in-kernel and libc! > > It would look much better to say: > > * Complete single-copy TCP/IP implementation > And even better if we could list both. :-) I think the needs of the FreeBSD group is diverse enough that this isn't unreasonable. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:49:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11829 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:49:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11824 for ; Fri, 30 Oct 1998 10:49:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01266; Fri, 30 Oct 1998 10:48:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301848.KAA01266@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:44:04 PST." <17327.909773044@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 10:48:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How many people would be interested in labels and conditional branches, > > for example? > > Probably quite a few, but then you get into the predictable debate > of "why not just add atlast to the loader? It's only 7K!" :-) Actually, it's about 45k. I've been looking at all sorts of small script interpreters; there doesn't seem to be much in the "useful" category under about 40k, and that's too big for the Alpha at the moment. All of the usual scripting plusses apply; I just want to keep things as tight as possible. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 10:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11848 for freebsd-current-outgoing; Fri, 30 Oct 1998 10:49:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11841 for ; Fri, 30 Oct 1998 10:49:09 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA04753; Fri, 30 Oct 1998 13:48:39 -0500 (EST) (envelope-from wollman) Date: Fri, 30 Oct 1998 13:48:39 -0500 (EST) From: Garrett Wollman Message-Id: <199810301848.NAA04753@khavrinen.lcs.mit.edu> To: John Hay Cc: current@FreeBSD.ORG Subject: Re: IPv6 in -current In-Reply-To: <199810301847.UAA17640@zibbi.mikom.csir.co.za> References: <199810301613.LAA04296@khavrinen.lcs.mit.edu> <199810301847.UAA17640@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> > * Full IPv6 implementation in-kernel and libc! >> * Complete single-copy TCP/IP implementation > And even better if we could list both. :-) I think the needs of the > FreeBSD group is diverse enough that this isn't unreasonable. The needs are one thing; the capabilities quite another. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:14:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14169 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:14:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14147 for ; Fri, 30 Oct 1998 11:14:00 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA24817; Fri, 30 Oct 1998 20:18:53 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 30 Oct 1998 20:18:53 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810301848.KAA01266@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > > How many people would be interested in labels and conditional branches, > > > for example? > > > > Probably quite a few, but then you get into the predictable debate > > of "why not just add atlast to the loader? It's only 7K!" :-) > > Actually, it's about 45k. I've been looking at all sorts of small > script interpreters; there doesn't seem to be much in the "useful" > category under about 40k, and that's too big for the Alpha at the > moment. There are Forth implementations for x86 which take around 8kB. These implement the subset of CORE words only, but you can have a /boot/core-ext.4th, /boot/menus.4th, etc, etc... - all these would be added to dictionary at run-time. This includes also all sorts of conditionals, loops, help screens etc, etc... Imagine something like that: /boot/boot.config: ----------------------------- include /boot/help.4th \ Here I define words "run_tests" and "load_tests" include /boot/my_loading_and_unloading_test.4th include /boot/menus.4th run_tests 0= if \ All tests are ok, boot experimental set of modules load_tests boot then ." The tests failed. Booting last known good kernel..." cr boot /kernel.good ------------------------- This idea has a nice touch about it - "Forth? The Suns and FreeBSD's use it as their boot monitor.." :-) Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:20:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14808 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:20:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14802 for ; Fri, 30 Oct 1998 11:20:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01422; Fri, 30 Oct 1998 11:18:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301918.LAA01422@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 20:18:53 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 11:18:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 30 Oct 1998, Mike Smith wrote: > > > > > How many people would be interested in labels and conditional branches, > > > > for example? > > > > > > Probably quite a few, but then you get into the predictable debate > > > of "why not just add atlast to the loader? It's only 7K!" :-) > > > > Actually, it's about 45k. I've been looking at all sorts of small > > script interpreters; there doesn't seem to be much in the "useful" > > category under about 40k, and that's too big for the Alpha at the > > moment. > > There are Forth implementations for x86 which take around 8kB. These It needs to be portable. I haven't seen a decent portable Forth under about 40k. Atlast isn't very decent. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15514 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15473 for ; Fri, 30 Oct 1998 11:26:00 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA17557; Fri, 30 Oct 1998 11:25:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Andrzej Bialecki cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 20:18:53 +0100." Date: Fri, 30 Oct 1998 11:25:39 -0800 Message-ID: <17553.909775539@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are Forth implementations for x86 which take around 8kB. These > implement the subset of CORE words only, but you can have a > /boot/core-ext.4th, /boot/menus.4th, etc, etc... - all these would be > added to dictionary at run-time. This includes also all sorts of > conditionals, loops, help screens etc, etc... Imagine something like that: It would be nice if a "tiny4th" interpreter could be written in C so that it will port straight over to the alpha; I don't think a truly minimal 4th set would be that large, even in a HLL like C. Somebody figured out what the truly minimal # of 4th words required for an interpreter was at some point though I don't remember what it is - 8? I figure if you have key, emit, ?terminal and fload, you've got enough of an I/O system to make this work. :) Except for atlast, TILE forth, cforth and pratt forth, all of which are too large, what are our options here anyway? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16077 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:32:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16072 for ; Fri, 30 Oct 1998 11:32:29 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA05296; Fri, 30 Oct 1998 20:37:21 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 30 Oct 1998 20:37:20 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810301918.LAA01422@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > It needs to be portable. I haven't seen a decent portable Forth under > about 40k. Atlast isn't very decent. Atlast is NOT Forth, and it's implementation leaves much to desire... Tell you somethin: please go to www.taygeta.com, and see some pretty, tiny Forth implementations in versions for 3-4 architectures. There are such. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16792 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:36:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16760 for ; Fri, 30 Oct 1998 11:35:56 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id OAA24680 for ; Fri, 30 Oct 1998 14:35:40 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Fri, 30 Oct 1998 14:35:40 -0500 (EST) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: How? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I modify my supfile to _not_ grab certain directories? For example, I'd like to exclude 'ports/[all languages other than english]'. Thanks for the help... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:36:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16880 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:36:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16868 for ; Fri, 30 Oct 1998 11:36:11 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id LAA12903; Fri, 30 Oct 1998 11:35:57 -0800 (PST) (envelope-from jdp) Message-Id: <199810301935.LAA12903@austin.polstra.com> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:34:59 PST." <199810301834.KAA01153@dingo.cdrom.com> Date: Fri, 30 Oct 1998 11:35:56 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I also forgot to point out that in the more complex case: > > load /kernel > load /modules/foo.ko > ... > autoboot 10 > > you could just add > > unload > > to the end of the script. Thanks for the advice. This looks perfect. Am I right in assuming that the unload will be executed if and only if I interrupt the autoboot by pressing a key during the countdown? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17092 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:37:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17081 for ; Fri, 30 Oct 1998 11:37:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01533; Fri, 30 Oct 1998 11:36:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301936.LAA01533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 20:37:20 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 11:36:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 30 Oct 1998, Mike Smith wrote: > > > > > It needs to be portable. I haven't seen a decent portable Forth under > > about 40k. Atlast isn't very decent. > > Atlast is NOT Forth, and it's implementation leaves much to desire... Tell > you somethin: please go to www.taygeta.com, and see some pretty, tiny > Forth implementations in versions for 3-4 architectures. There are such. Been there, done that. The portable ones are all too big. 8) Actually, ~40k doesn't bother me much, once we get the alpha issues sorted out. But Forth is more intimidating than it needs to be; something with an sh-like syntax would be nicer. (Yes, I agree that Forth would be more powerful. Compromises...) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:38:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17202 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:38:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17154 for ; Fri, 30 Oct 1998 11:38:24 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA09011; Fri, 30 Oct 1998 20:43:19 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 30 Oct 1998 20:43:19 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Jordan K. Hubbard" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <17553.909775539@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Jordan K. Hubbard wrote: > > There are Forth implementations for x86 which take around 8kB. These > > implement the subset of CORE words only, but you can have a > > /boot/core-ext.4th, /boot/menus.4th, etc, etc... - all these would be > > added to dictionary at run-time. This includes also all sorts of > > conditionals, loops, help screens etc, etc... Imagine something like that: > > It would be nice if a "tiny4th" interpreter could be written in C so > that it will port straight over to the alpha; I don't think a truly > minimal 4th set would be that large, even in a HLL like C. Somebody > figured out what the truly minimal # of 4th words required for an > interpreter was at some point though I don't remember what it is - 8? > I figure if you have key, emit, ?terminal and fload, you've got enough > of an I/O system to make this work. :) Except for atlast, TILE forth, > cforth and pratt forth, all of which are too large, what are our > options here anyway? You can find a decent list of free implementations on www.taygeta.com. We should also ask those lurking Forth'ers among us - I know there are quite a few of them, some of them even written Forth implementations. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:48:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17723 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:48:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17718 for ; Fri, 30 Oct 1998 11:48:45 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id OAA00413 for ; Fri, 30 Oct 1998 14:51:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Fri, 30 Oct 1998 14:51:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: current@FreeBSD.ORG Subject: if anyone is interested VESA seems broken. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently enabled "options USER_LDT" in my kernel to test some things out. I also enabled VESA and VM86 (figured if i was gonna reboot...) Well vidcontrol seems only able to set a very small subset of modes that seem available to my machine (from boot -v and vidcontrol -i mode) Modes that I could get to work: 80x25, 132x25, VESA_800x600 no more :( However it seems stable enough, but I don't have Xfree around to test the VESA server. Another odd thing with VESA, if you notice how it seems the top of my dmesg it gone? Well right about there at bootup my screen goes blank for a split second and again either a second before or after the cut part. (This happens twice while probing VESA it seems) What's up? vidcontrol -i mode: mode# flags type size font window linear buffer ------------------------------------------------------------------------------ 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 0k 1 (0x001) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 0k 2 (0x002) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 0k 3 (0x003) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 0k 4 (0x004) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 0k 5 (0x005) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 0k 6 (0x006) 0x00000003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x00000000 0k 7 (0x007) 0x00000000 T 80x25 8x14 0xb0000 32k 32k 0x00000000 0k 13 (0x00d) 0x00000003 G 320x200x4 4 8x8 0xa0000 64k 64k 0x00000000 0k 14 (0x00e) 0x00000003 G 640x200x4 4 8x8 0xa0000 64k 64k 0x00000000 0k 15 (0x00f) 0x00000002 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 0k 16 (0x010) 0x00000003 G 640x350x2 2 8x14 0xa0000 64k 64k 0x00000000 0k 17 (0x011) 0x00000002 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 0k 18 (0x012) 0x00000003 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 0k 19 (0x013) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 0k 20 (0x014) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 0k 21 (0x015) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 0k 22 (0x016) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 0k 23 (0x017) 0x00000001 T 40x25 8x16 0xb8000 32k 32k 0x00000000 0k 24 (0x018) 0x00000001 T 80x25 8x16 0xb8000 32k 32k 0x00000000 0k 25 (0x019) 0x00000000 T 80x25 8x16 0xb0000 32k 32k 0x00000000 0k 26 (0x01a) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 0k 27 (0x01b) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 0k 28 (0x01c) 0x00000003 G 320x200x8 1 8x8 0xa0000 64k 64k 0x00000000 0k 30 (0x01e) 0x00000001 T 80x50 8x8 0xb8000 32k 32k 0x00000000 0k 31 (0x01f) 0x00000000 T 80x50 8x8 0xb0000 32k 32k 0x00000000 0k 32 (0x020) 0x00000001 T 80x30 8x16 0xb8000 32k 32k 0x00000000 0k 33 (0x021) 0x00000000 T 80x30 8x16 0xb0000 32k 32k 0x00000000 0k 34 (0x022) 0x00000001 T 80x60 8x8 0xb8000 32k 32k 0x00000000 0k 35 (0x023) 0x00000000 T 80x60 8x8 0xb0000 32k 32k 0x00000000 0k 37 (0x025) 0x00000003 G 320x240x8 1 8x8 0xa0000 64k 64k 0x00000000 0k 112 (0x070) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 0k 113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 0k 200 (0x0c8) 0x00000001 T 80x25 8x16 0xb8000 32k 32k 0x00000000 0k 201 (0x0c9) 0x00000001 T 80x30 8x16 0xb8000 32k 32k 0x00000000 0k 202 (0x0ca) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 0k 203 (0x0cb) 0x00000001 T 80x50 8x8 0xb8000 32k 32k 0x00000000 0k 204 (0x0cc) 0x00000001 T 80x60 8x8 0xb8000 32k 32k 0x00000000 0k 205 (0x0cd) 0x00000009 T 132x25 8x16 0xb8000 32k 32k 0x00000000 0k 208 (0x0d0) 0x00000009 T 132x50 8x8 0xb8000 32k 32k 0x00000000 0k 209 (0x0d1) 0x00000009 T 132x60 8x8 0xb8000 32k 32k 0x00000000 0k 256 (0x100) 0x0000000f G 640x400x8 1 8x16 0xa0000 64k 64k 0xfd000000 250k 257 (0x101) 0x0000000f G 640x480x8 1 8x16 0xa0000 64k 64k 0xfd000000 300k 258 (0x102) 0x0000000b G 800x600x4 4 8x14 0xa0000 64k 64k 0x00000000 0k 259 (0x103) 0x0000000f G 800x600x8 1 8x16 0xa0000 64k 64k 0xfd000000 600k 261 (0x105) 0x0000000f G 1024x768x8 1 8x16 0xa0000 64k 64k 0xfd000000 768k 263 (0x107) 0x0000000f G 1280x1024x8 1 8x16 0xa0000 64k 64k 0xfd000000 1280k 264 (0x108) 0x00000009 T 80x60 8x8 0xb8000 32k 32k 0x00000000 0k 265 (0x109) 0x00000009 T 132x25 8x16 0xb8000 32k 32k 0x00000000 0k 267 (0x10b) 0x00000009 T 132x50 8x8 0xb8000 32k 32k 0x00000000 0k 268 (0x10c) 0x00000009 T 132x60 8x8 0xb8000 32k 32k 0x00000000 0k 272 (0x110) 0x0000000f G 640x480x16 1 8x16 0xa0000 64k 64k 0xfd000000 600k 273 (0x111) 0x0000000f G 640x480x16 1 8x16 0xa0000 64k 64k 0xfd000000 600k 274 (0x112) 0x0000000f G 640x480x32 1 8x16 0xa0000 64k 64k 0xfd000000 1200k 275 (0x113) 0x0000000f G 800x600x16 1 8x16 0xa0000 64k 64k 0xfd000000 1125k 276 (0x114) 0x0000000f G 800x600x16 1 8x16 0xa0000 64k 64k 0xfd000000 1125k 277 (0x115) 0x0000000f G 800x600x32 1 8x16 0xa0000 64k 64k 0xfd000000 1875k 278 (0x116) 0x0000000f G 1024x768x16 1 8x16 0xa0000 64k 64k 0xfd000000 1536k 279 (0x117) 0x0000000f G 1024x768x16 1 8x16 0xa0000 64k 64k 0xfd000000 1536k 280 (0x118) 0x0000000f G 1024x768x32 1 8x16 0xa0000 64k 64k 0xfd000000 3072k 281 (0x119) 0x0000000f G 1280x1024x16 1 8x16 0xa0000 64k 64k 0xfd000000 2560k 282 (0x11a) 0x0000000f G 1280x1024x16 1 8x16 0xa0000 64k 64k 0xfd000000 2560k 284 (0x11c) 0x0000000f G 1600x1200x8 1 8x16 0xa0000 64k 64k 0xfd000000 1950k 285 (0x11d) 0x0000000f G 1600x1200x16 1 8x16 0xa0000 64k 64k 0xfd000000 3750k 286 (0x11e) 0x0000000f G 1600x1200x16 1 8x16 0xa0000 64k 64k 0xfd000000 3750k boot -v: (from /var/run/dmesg.boot) 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VESA: v2.0, 4096k memory, flags:0x1, mode table:0xf027999e (1000022) VESA: Matrox Graphics Inc. VESA: Matrox VESA: MISTRAL VESA: 00 VESA: mode:0x100, flags:0x009b, G 640x400x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0x3e800 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x101, flags:0x009b, G 640x480x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0x4b000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x102, flags:0x001b, G 800x600x4 4, font:8x14 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x103, flags:0x009b, G 800x600x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0x96000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x105, flags:0x009b, G 1024x768x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0xc0000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x107, flags:0x009b, G 1280x1024x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0x140000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x108, flags:0x000b, T 80x60, font:8x8 VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k VESA: mode:0x109, flags:0x000b, T 132x25, font:8x16 VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k VESA: mode:0x10b, flags:0x000b, T 132x50, font:8x8 VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k VESA: mode:0x10c, flags:0x000b, T 132x60, font:8x8 VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k VESA: mode:0x110, flags:0x009b, G 640x480x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x96000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x111, flags:0x009b, G 640x480x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x96000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x112, flags:0x009b, G 640x480x32 1, font:8x16, mem:6, LFB:0xfd000000, off:0x12c000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x113, flags:0x009b, G 800x600x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x119400 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x114, flags:0x009b, G 800x600x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x119400 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x115, flags:0x009b, G 800x600x32 1, font:8x16, mem:6, LFB:0xfd000000, off:0x1d4c00 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x116, flags:0x009b, G 1024x768x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x180000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x117, flags:0x009b, G 1024x768x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x180000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x11c, flags:0x009b, G 1600x1200x8 1, font:8x16, mem:4, LFB:0xfd000000, off:0x1e7800 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x118, flags:0x009b, G 1024x768x32 1, font:8x16, mem:6, LFB:0xfd000000, off:0x300000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x119, flags:0x009b, G 1280x1024x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x280000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x11a, flags:0x009b, G 1280x1024x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x280000 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x11d, flags:0x009b, G 1600x1200x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x3a9800 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k VESA: mode:0x11e, flags:0x009b, G 1600x1200x16 1, font:8x16, mem:6, LFB:0xfd000000, off:0x3a9800 VESA: window A:0xa000 (7), window B:0x0 (0), size:64k, gran:64k sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> .... thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 11:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18318 for freebsd-current-outgoing; Fri, 30 Oct 1998 11:54:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18311 for ; Fri, 30 Oct 1998 11:54:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01641; Fri, 30 Oct 1998 11:54:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301954.LAA01641@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: if anyone is interested VESA seems broken. In-reply-to: Your message of "Fri, 30 Oct 1998 14:51:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 11:54:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I recently enabled "options USER_LDT" in my kernel to test some things > out. I also enabled VESA and VM86 (figured if i was gonna reboot...) > > Well vidcontrol seems only able to set a very small subset of modes > that seem available to my machine (from boot -v and vidcontrol -i mode) > > Modes that I could get to work: 80x25, 132x25, VESA_800x600 no more :( Which other ones did you try? There should probably be an option to set explicitly based on the mode number, but I haven't seen anything that doesn't work as expected. > Another odd thing with VESA, if you notice how it seems the top of my > dmesg it gone? Well right about there at bootup my screen goes blank for > a split second and again either a second before or after the cut part. > (This happens twice while probing VESA it seems) The top of your dmesg output is probably missing because the kernel message buffer is too small. The screen blank is normal (video reset). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 12:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19906 for freebsd-current-outgoing; Fri, 30 Oct 1998 12:08:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19901 for ; Fri, 30 Oct 1998 12:08:41 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id VAA26233; Fri, 30 Oct 1998 21:13:35 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 30 Oct 1998 21:13:34 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810301936.LAA01533@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > On Fri, 30 Oct 1998, Mike Smith wrote: > > > > > > > > It needs to be portable. I haven't seen a decent portable Forth under > > > about 40k. Atlast isn't very decent. > > > > Atlast is NOT Forth, and it's implementation leaves much to desire... Tell > > you somethin: please go to www.taygeta.com, and see some pretty, tiny > > Forth implementations in versions for 3-4 architectures. There are such. > > Been there, done that. The portable ones are all too big. 8) They are big because either they use termcap, or curses, or they define complete CORE, CORE-EXT, DOUBLE, FLOATING, LOCALS, and whatnot... We wouldn't need most of it. Heck, there are Forth's for PICs! This can be done, and IMVHO advantages are obvious... > Actually, ~40k doesn't bother me much, once we get the alpha issues > sorted out. But Forth is more intimidating than it needs to be; > something with an sh-like syntax would be nicer. It depends. When you use Sparc's boot monitor you don't need to be aware what's behind a word "help" or "power-off". > (Yes, I agree that Forth would be more powerful. Compromises...) Ah, well. I guess I'm proposing Forth so strongly because it's so powerful and compact, and fast... and so incredibly extensible when you need it. No need to reinvent the same things each time, writing yet another incompatible language... I think this is important opportunity - let's not miss it without good reasons... As I said, there are people among us who can even write small enough Forth kernel for our purposes. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 12:13:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20286 for freebsd-current-outgoing; Fri, 30 Oct 1998 12:13:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20279 for ; Fri, 30 Oct 1998 12:13:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01772 for ; Fri, 30 Oct 1998 12:13:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810302013.MAA01772@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 21:13:34 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 12:13:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually, ~40k doesn't bother me much, once we get the alpha issues > > sorted out. But Forth is more intimidating than it needs to be; > > something with an sh-like syntax would be nicer. > > It depends. When you use Sparc's boot monitor you don't need to be aware > what's behind a word "help" or "power-off". No, but when you want to script it, your existing knowledge as an admin or script programmer is worthless. We don't want to limit the people that can write scripts for the loader too much. > > (Yes, I agree that Forth would be more powerful. Compromises...) > > Ah, well. I guess I'm proposing Forth so strongly because it's so powerful > and compact, and fast... and so incredibly extensible when you need it. No > need to reinvent the same things each time, writing yet another > incompatible language... > > I think this is important opportunity - let's not miss it without good > reasons... As I said, there are people among us who can even write small > enough Forth kernel for our purposes. I have no desire to miss it. Give me a compact Forth interpreter that links against libstand and you'll be seeing it everywhere Real Soon. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 12:34:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22512 for freebsd-current-outgoing; Fri, 30 Oct 1998 12:34:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22500 for ; Fri, 30 Oct 1998 12:34:24 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA05168; Fri, 30 Oct 1998 13:34:17 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA24638; Fri, 30 Oct 1998 13:34:16 -0700 Date: Fri, 30 Oct 1998 13:34:16 -0700 Message-Id: <199810302034.NAA24638@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810301848.KAA01266@dingo.cdrom.com> References: <17327.909773044@time.cdrom.com> <199810301848.KAA01266@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > How many people would be interested in labels and conditional branches, > > > for example? > > > > Probably quite a few, but then you get into the predictable debate > > of "why not just add atlast to the loader? It's only 7K!" :-) > > Actually, it's about 45k. I've been looking at all sorts of small > script interpreters; there doesn't seem to be much in the "useful" > category under about 40k, and that's too big for the Alpha at the > moment. What about Forth? (Cheap dig at Jordan :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 13:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25203 for freebsd-current-outgoing; Fri, 30 Oct 1998 13:03:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25198 for ; Fri, 30 Oct 1998 13:03:52 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id VAA18322 for ; Fri, 30 Oct 1998 21:39:05 +0100 (CET) Message-Id: <199810302039.VAA18322@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: LKM fastvid Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 30 Oct 1998 12:10:09 +0100." <19981030121009.D9648@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 21:39:05 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: >Does anybody have an updated version of the Fastvid LKM... ? > I got it working with some trivial changes. Unfortunately, it's at work and I'm at home. But it was obvious what had to be changed from looking at one of the working LKMs. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 13:48:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28932 for freebsd-current-outgoing; Fri, 30 Oct 1998 13:48:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28877 for ; Fri, 30 Oct 1998 13:47:52 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id PAA18798; Fri, 30 Oct 1998 15:47:42 -0600 (CST) Date: Fri, 30 Oct 1998 15:47:41 -0600 From: Dan Nelson To: Alfred Perlstein , current@FreeBSD.ORG, Mike Smith Subject: Re: if anyone is interested VESA seems broken. Message-ID: <19981030154741.A18571@emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: ; from "Alfred Perlstein" on Fri Oct 30 14:51:22 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 30), Alfred Perlstein said: > I recently enabled "options USER_LDT" in my kernel to test some > things out. I also enabled VESA and VM86 (figured if i was gonna > reboot...) > > Well vidcontrol seems only able to set a very small subset of modes > that seem available to my machine (from boot -v and vidcontrol -i > mode) > > Modes that I could get to work: 80x25, 132x25, VESA_800x600 no more > :( vidcontrol should only let you set the text modes and 800x600, I think. If you can't get 132x50, make sure you have an 8x8 font loaded. I know I have gotten 132x43 on my system (cheap s3 chipset won't do 132x50) > Another odd thing with VESA, if you notice how it seems the top of my > dmesg it gone? Well right about there at bootup my screen goes blank for > a split second and again either a second before or after the cut part. > (This happens twice while probing VESA it seems) That's because the default dmesg buffer in the kernel is 8k by default. Add "options MSGBUF_SIZE=16384" to your kernel config file to double it. > VESA: mode:0x109, flags:0x000b, T 132x25, font:8x16 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k > VESA: mode:0x10b, flags:0x000b, T 132x50, font:8x8 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k > VESA: mode:0x10c, flags:0x000b, T 132x60, font:8x8 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k Your card definitely should be able to do 132x50, since it claims to support it here. Maybe check to see that vidcontrol and syscons.c handle them correctly (I don't have access to 3.0 at the moment) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 15:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09826 for freebsd-current-outgoing; Fri, 30 Oct 1998 15:40:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09817 for ; Fri, 30 Oct 1998 15:40:28 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.8/8.8.5) with UUCP id RAA22949; Fri, 30 Oct 1998 17:40:23 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id RAA00777; Fri, 30 Oct 1998 17:37:37 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Fri, 30 Oct 1998 17:37:37 -0600 (CST) From: Jay Nelson To: "Alok K. Dhir" cc: current@FreeBSD.ORG Subject: Re: How? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Alok K. Dhir wrote: > >How can I modify my supfile to _not_ grab certain directories? For >example, I'd like to exclude 'ports/[all languages other than english]'. > >Thanks for the help... Put the following lines in /usr/sup/ports-all/refuse: ports/chinese/* ports/german/* ports/japanese/* ports/korean/* ports/russian/* ports/vietnamese/* -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 18:28:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26969 for freebsd-current-outgoing; Fri, 30 Oct 1998 18:28:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26964 for ; Fri, 30 Oct 1998 18:28:41 -0800 (PST) (envelope-from jamesh@swcp.com) Received: from localhost (jamesh@localhost) by kitsune.swcp.com (8.8.8/1.2.3) with SMTP id TAA21854 for ; Fri, 30 Oct 1998 19:28:38 -0700 (MST) Date: Fri, 30 Oct 1998 19:28:37 -0700 (MST) From: James Hamilton To: current@FreeBSD.ORG Subject: System Upgrade Via /stand/sysinstall Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I did the system upgrade via the /stand/sysinstall. However it died in the middle taking my system with it. It got to the end where it talks about making device files for the new OS. When it said that the swap pager was out of space. I'm using it for my desktop machine so it has an expects to have access to much more memory? My swap space was not full so I don't know. I guess I'll do the good ol floppy install and start over since my file system is broken. Any advice or reasons why this happened would be more than welcomed. James Hamilton SWCP Technical Support (505)-232-7992 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 18:54:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00905 for freebsd-current-outgoing; Fri, 30 Oct 1998 18:54:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00900 for ; Fri, 30 Oct 1998 18:54:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03867 for ; Fri, 30 Oct 1998 18:54:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810310254.SAA03867@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: New bootstrap HEADS UP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 18:54:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a warning that I've changed the interface between the bootstrap and libstand. You *must* rebuild and reinstall libstand before rebuilding the bootloader. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 30 21:47:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15477 for freebsd-current-outgoing; Fri, 30 Oct 1998 21:47:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15426 for ; Fri, 30 Oct 1998 21:47:22 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id NAA18245; Sat, 31 Oct 1998 13:46:50 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810310546.NAA18245@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: John Polstra , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Fri, 30 Oct 1998 10:34:59 PST." <199810301834.KAA01153@dingo.cdrom.com> Date: Sat, 31 Oct 1998 13:46:50 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I have a question about the new boot loader. My /boot/boot.conf > > > file looks like this: > > > > > > load /kernel > > > autoboot 10 > > > > > > Now suppose I want to boot an alternate kernel. To do that, it seems > > > I have to interrupt the autoboot sequence by pressing a key, then do > > > "unload /kernel", then do "boot /kernel.alt". Is that right? It's > > > the unload step that I'm wondering about. Can it be avoided? > > > > Unloading is an all or nothing proposition; it throws everything away > > (it doesn't take any arguments). This avoids having holes in the > > loaded region, as well as having to deal with dependancy issues. > > I also forgot to point out that in the more complex case: > > load /kernel > load /modules/foo.ko > ... > autoboot 10 > > you could just add > > unload > > to the end of the script. > > There's probably a call for a 'bootmodules' variable as well; until we > get more people using this and asking for features I'm not sure what's > worth adding and what's just fluff. > > How many people would be interested in labels and conditional branches, > for example? What I'd like is something like this: timeout 10 "Press enter to boot now, any other key to abort" load kernel load foo.ko boot Ie: have an abort-script type capability. It'd save all that loading and unloading. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 03:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11053 for freebsd-current-outgoing; Sat, 31 Oct 1998 03:26:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11027; Sat, 31 Oct 1998 03:26:14 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sjx-ca115-43.ix.netcom.com [207.223.162.107]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id DAA16994; Sat, 31 Oct 1998 03:25:10 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id DAA10351; Sat, 31 Oct 1998 03:25:05 -0800 (PST) Date: Sat, 31 Oct 1998 03:25:05 -0800 (PST) Message-Id: <199810311125.DAA10351@silvia.hip.berkeley.edu> To: mike@smith.net.au CC: mark@grondar.za, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG In-reply-to: <199810282037.MAA00616@dingo.cdrom.com> (message from Mike Smith on Wed, 28 Oct 1998 12:37:51 -0800) Subject: Re: Who built XFree86 with Kerberos? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Mike Smith * Bento was used this time around. I think Justin is probably feeling * pretty embarrassed about now. Ouch. I don't see any reason why he should be embarrassed. This is exactly the kind of thing that a good round of testing will uncover but is very hard to detect on the building machine. The scheduling, which didn't leave him any time to put the ELF packages up for testing before the release, is at fault. Justin did a tremendous job IMO. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 04:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19027 for freebsd-current-outgoing; Sat, 31 Oct 1998 04:17:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19022 for ; Sat, 31 Oct 1998 04:17:07 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id NAA15149; Sat, 31 Oct 1998 13:12:44 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id NAA17278; Sat, 31 Oct 1998 13:07:02 +0100 (MET) (envelope-from wosch) Message-ID: <19981031130659.A17271@panke.de.freebsd.org> Date: Sat, 31 Oct 1998 13:06:59 +0100 From: Wolfram Schneider To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid References: <19981027233255.A1336@panke.de.freebsd.org> <663.909573570@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <663.909573570@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Oct 28, 1998 at 12:19:30PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: > Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to > 10 and tell me if it works. The 18th `make world' got a calcru: negative time of -695373488 usec for pid 23724 (as) and a little bit later died with pid 4542 (ld), uid 0: exited on signal 11 (core dumped) Wolfram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 05:23:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23535 for freebsd-current-outgoing; Sat, 31 Oct 1998 05:23:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23513; Sat, 31 Oct 1998 05:23:01 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id PAA00418; Sat, 31 Oct 1998 15:21:15 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810311321.PAA00418@gratis.grondar.za> To: asami@FreeBSD.ORG (Satoshi Asami) cc: mike@smith.net.au, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Sat, 31 Oct 1998 03:25:05 PST." <199810311125.DAA10351@silvia.hip.berkeley.edu> References: <199810311125.DAA10351@silvia.hip.berkeley.edu> Date: Sat, 31 Oct 1998 15:21:13 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Justin did a tremendous job IMO. Hear, Hear! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 06:11:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29079 for freebsd-current-outgoing; Sat, 31 Oct 1998 06:11:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29072 for ; Sat, 31 Oct 1998 06:11:10 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id PAA13696; Sat, 31 Oct 1998 15:09:53 +0100 (CET) To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 13:06:59 +0100." <19981031130659.A17271@panke.de.freebsd.org> Date: Sat, 31 Oct 1998 15:09:53 +0100 Message-ID: <13694.909842993@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So is this better or worse than normal ? In message <19981031130659.A17271@panke.de.freebsd.org>, Wolfram Schneider writes: >On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: >> Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to >> 10 and tell me if it works. > >The 18th `make world' got a >calcru: negative time of -695373488 usec for pid 23724 (as) > >and a little bit later died with >pid 4542 (ld), uid 0: exited on signal 11 (core dumped) > >Wolfram > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 06:56:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03338 for freebsd-current-outgoing; Sat, 31 Oct 1998 06:56:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03314; Sat, 31 Oct 1998 06:56:31 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA15703; Sat, 31 Oct 1998 06:56:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: asami@FreeBSD.ORG (Satoshi Asami) cc: mike@smith.net.au, mark@grondar.za, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-reply-to: Your message of "Sat, 31 Oct 1998 03:25:05 PST." <199810311125.DAA10351@silvia.hip.berkeley.edu> Date: Sat, 31 Oct 1998 06:56:40 -0800 Message-ID: <15699.909845800@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > very hard to detect on the building machine. The scheduling, which > didn't leave him any time to put the ELF packages up for testing > before the release, is at fault. You can say that again. Despite having plenty of warning, and we're talking several month's worth here, the task was apparently dumped at the very last moment on Justin and Steve. I know that Steve certainly wasn't very happy about how this was done and it certainly took Mike and I by surprise as well - there was some even doubt, for awhile there, as to whether 3.0 would ship with a packages collection at all. In any case, all finger-pointing and indignation aside, if the ports/packages phase of each new release is to occur both on-time and with minimum stress on all concerned, we're going to have to figure out well in advance just who's going to take on the job of physically generating and segregating all the packages and distfiles. I certainly don't want to be scratching my head and trying to figure out who's "job" it's even supposed to be a day before a release is due and the various ports volunteers don't want to be stuck with doing the job on a moment's notice, either. My suggestion would be that we either: a) go to some sort of automation scheme which [re]builds packages on an ongoing basis and, at release time, I just take a snapshot of the collection or b) We try appointing a ports/packages releasemeister who's responsible for doing in ports what I do for src each time a release rolls around. This person could be paid since it's important to Walnut Creek CDROM that packages and distfiles be rendered into ISO images periodically, especially now that we have this "toolkit" CD for FreeBSD in addition to the usual 4 CD sets. Thoughts? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:23:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06426 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:23:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06409 for ; Sat, 31 Oct 1998 07:23:17 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id SAA01603 for ; Sat, 31 Oct 1998 18:23:12 +0300 (MSK) Date: Sat, 31 Oct 1998 18:23:11 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@FreeBSD.ORG Subject: kernel compile problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've just cvsuped -current and there is a problem compiling kernel: cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout ../../kern/vfs_bio.c ../../kern/vfs_bio.c: In function `bufinit': ../../kern/vfs_bio.c:182: structure has no member named `le_next' ../../kern/vfs_bio.c:182: `NOLIST' undeclared (first use this function) ../../kern/vfs_bio.c:182: (Each undeclared identifier is reported only once ../../kern/vfs_bio.c:182: for each function it appears in.) *** Error code 1 Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:24:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06824 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:24:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06798; Sat, 31 Oct 1998 07:24:34 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA00776; Sat, 31 Oct 1998 17:24:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810311524.RAA00776@gratis.grondar.za> To: "Jordan K. Hubbard" cc: asami@FreeBSD.ORG (Satoshi Asami), mike@smith.net.au, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Sat, 31 Oct 1998 06:56:40 PST." <15699.909845800@time.cdrom.com> References: <15699.909845800@time.cdrom.com> Date: Sat, 31 Oct 1998 17:24:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > My suggestion would be that we either: a) go to some sort of > automation scheme which [re]builds packages on an ongoing basis and, > at release time, I just take a snapshot of the collection or b) We try > appointing a ports/packages releasemeister who's responsible for doing > in ports what I do for src each time a release rolls around. This > person could be paid since it's important to Walnut Creek CDROM > that packages and distfiles be rendered into ISO images periodically, > especially now that we have this "toolkit" CD for FreeBSD in addition > to the usual 4 CD sets. How about breaking the ports collection into pieces, or at least breaking away large chunks. I would be quite happy to donate a regular CRON job to build a nominated set of ports (eg: all the security stuff, all shells, teTeX, p5-*, m[y]sql, all four emacsen, and tcl8*/tk8*; I could easily be talked into doing a lot more.) Do that with a few other suckers^h^h^h^h^h^hvolunteers, and the load on Satoshi /et al/ should drop quite a bit for very little effort. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08599 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:38:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08567 for ; Sat, 31 Oct 1998 07:37:57 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zZEdu-00004I-00; Fri, 30 Oct 1998 13:31:06 +0000 To: Mike Nguyen Cc: "Jeffrey J. Mountin" , current@FreeBSD.ORG, Brian Feldman Subject: Re: Changing sh for compatibility sake References: From: Dom Mitchell In-Reply-To: Mike Nguyen's message of "Tue, 27 Oct 1998 14:19:27 -0600 (CST)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Fri, 30 Oct 1998 13:31:06 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nguyen writes: > First thing I do when I install a new FreeBSD box is install the BSDi ksh > binaries from the AT&T software reuse website as /bin/ksh. A real ksh93, no > less. I haven't had the guts to replace /bin/sh with it yet (though the man > page does have a toggle to display either as sh(1) or ksh(1)). I wouldn't replace /bin/sh with ksh93... It is a *lot* bigger. It's practically a whole new shell, compared to ksh88. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08910 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:40:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08876 for ; Sat, 31 Oct 1998 07:40:03 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zZEYK-000047-00; Fri, 30 Oct 1998 13:25:20 +0000 To: obrien@NUXI.com Cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: Shells for you and shells for me References: <3633C8F8.EF8E14D5@null.net> <19981026125133.A2717@netmonger.net> <19981029012621.A26396@nuxi.com> From: Dom Mitchell In-Reply-To: "David O'Brien"'s message of "Thu, 29 Oct 1998 01:26:21 -0800" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Fri, 30 Oct 1998 13:25:20 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > I'd prefer to remove ash for pdksh as it is a little bit nicer in the > interactive department. Not only that, but it allows to say that we have a ksh in the base system, which for a lot of commercial unix shops is quite an important feature these days. To be frank, I think that pdksh is definitely something that we should be looking at for that reason alone. If we import it into the tree and leave it installed as /bin/ksh, then people can test it at their leisure to see if it is worth replacing /bin/sh, and we also gain a ksh. It's a good situation. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09582 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:46:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09576 for ; Sat, 31 Oct 1998 07:46:19 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id KAA07696; Sat, 31 Oct 1998 10:44:55 -0500 (EST) Date: Sat, 31 Oct 1998 10:44:55 -0500 (EST) From: Chuck Robey To: Dom Mitchell cc: Mike Nguyen , "Jeffrey J. Mountin" , current@FreeBSD.ORG, Brian Feldman Subject: Re: Changing sh for compatibility sake In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Dom Mitchell wrote: > Mike Nguyen writes: > > First thing I do when I install a new FreeBSD box is install the BSDi ksh > > binaries from the AT&T software reuse website as /bin/ksh. A real ksh93, no > > less. I haven't had the guts to replace /bin/sh with it yet (though the man > > page does have a toggle to display either as sh(1) or ksh(1)). > > I wouldn't replace /bin/sh with ksh93... It is a *lot* bigger. It's > practically a whole new shell, compared to ksh88. That was never even an option, since ksh93 isn't public code. It was all revolving around the pdksh code base (take a look at ports/shells/pdksh). Or maybe your comments meant that? > > -Dom > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 07:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11389 for freebsd-current-outgoing; Sat, 31 Oct 1998 07:59:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11363 for ; Sat, 31 Oct 1998 07:58:50 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id XAA20449; Sat, 31 Oct 1998 23:57:51 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810311557.XAA20449@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Dmitry Valdov cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel compile problem In-reply-to: Your message of "Sat, 31 Oct 1998 18:23:11 +0300." Date: Sat, 31 Oct 1998 23:57:50 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: > Hi! > > I've just cvsuped -current and there is a problem compiling kernel: > ../../kern/vfs_bio.c: In function `bufinit': > ../../kern/vfs_bio.c:182: structure has no member named `le_next' > ../../kern/vfs_bio.c:182: `NOLIST' undeclared (first use this function) > ../../kern/vfs_bio.c:182: (Each undeclared identifier is reported only once > ../../kern/vfs_bio.c:182: for each function it appears in.) You got a cvsup in between commits.. Try again and you should be OK. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 08:37:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14353 for freebsd-current-outgoing; Sat, 31 Oct 1998 08:37:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14348 for ; Sat, 31 Oct 1998 08:37:00 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id RAA16403; Sat, 31 Oct 1998 17:33:10 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id RAA20303; Sat, 31 Oct 1998 17:26:07 +0100 (MET) (envelope-from wosch) Message-ID: <19981031172606.A20248@panke.de.freebsd.org> Date: Sat, 31 Oct 1998 17:26:06 +0100 From: Wolfram Schneider To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid References: <19981031130659.A17271@panke.de.freebsd.org> <13694.909842993@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <13694.909842993@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Oct 31, 1998 at 03:09:53PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-10-31 15:09:53 +0100, Poul-Henning Kamp wrote: > So is this better or worse than normal ? I see no differences to the version without the NTIMECOUNTER hack. One of 26 `make world' failed, usually after 27 hours. I'm running `make world' in a chroot environment. My host is connected with a laplink cable. Wolfram > In message <19981031130659.A17271@panke.de.freebsd.org>, Wolfram Schneider writes: > >On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: > >> Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to > >> 10 and tell me if it works. > > > >The 18th `make world' got a > >calcru: negative time of -695373488 usec for pid 23724 (as) > > > >and a little bit later died with > >pid 4542 (ld), uid 0: exited on signal 11 (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 09:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19381 for freebsd-current-outgoing; Sat, 31 Oct 1998 09:10:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19375 for ; Sat, 31 Oct 1998 09:10:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA14102; Sat, 31 Oct 1998 18:09:19 +0100 (CET) To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 17:26:06 +0100." <19981031172606.A20248@panke.de.freebsd.org> Date: Sat, 31 Oct 1998 18:09:18 +0100 Message-ID: <14100.909853758@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19981031172606.A20248@panke.de.freebsd.org>, Wolfram Schneider writes: >On 1998-10-31 15:09:53 +0100, Poul-Henning Kamp wrote: >> So is this better or worse than normal ? > >I see no differences to the version without the NTIMECOUNTER hack. >One of 26 `make world' failed, usually after 27 hours. >I'm running `make world' in a chroot environment. >My host is connected with a laplink cable. Hmm, theres a clue, the if_lp0 stuff may disable interrupts for VERY long periods of time. Try setting NTIMERCOUNTER way up, lets try 300 for a go. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 09:50:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23750 for freebsd-current-outgoing; Sat, 31 Oct 1998 09:50:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23744; Sat, 31 Oct 1998 09:50:09 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id JAA07445; Sat, 31 Oct 1998 09:49:38 -0800 (PST) Message-ID: <19981031094937.A18462@Alameda.net> Date: Sat, 31 Oct 1998 09:49:37 -0800 From: Ulf Zimmermann To: Mark Murray , "Jordan K. Hubbard" Cc: Satoshi Asami , mike@smith.net.au, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? Reply-To: ulf@Alameda.net References: <15699.909845800@time.cdrom.com> <199810311524.RAA00776@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810311524.RAA00776@gratis.grondar.za>; from Mark Murray on Sat, Oct 31, 1998 at 05:24:16PM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 31, 1998 at 05:24:16PM +0200, Mark Murray wrote: > "Jordan K. Hubbard" wrote: > > My suggestion would be that we either: a) go to some sort of > > automation scheme which [re]builds packages on an ongoing basis and, > > at release time, I just take a snapshot of the collection or b) We try > > appointing a ports/packages releasemeister who's responsible for doing > > in ports what I do for src each time a release rolls around. This > > person could be paid since it's important to Walnut Creek CDROM > > that packages and distfiles be rendered into ISO images periodically, > > especially now that we have this "toolkit" CD for FreeBSD in addition > > to the usual 4 CD sets. > > How about breaking the ports collection into pieces, or at least > breaking away large chunks. > > I would be quite happy to donate a regular CRON job to build a > nominated set of ports (eg: all the security stuff, all shells, > teTeX, p5-*, m[y]sql, all four emacsen, and tcl8*/tk8*; I could > easily be talked into doing a lot more.) Do that with a few > other suckers^h^h^h^h^h^hvolunteers, and the load on Satoshi /et > al/ should drop quite a bit for very little effort. I offer to be one of that suckers^h^h^h^h^h^hvolunteers. I would also think about doing a regular packages-current or so. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 10:16:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26686 for freebsd-current-outgoing; Sat, 31 Oct 1998 10:16:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26679 for ; Sat, 31 Oct 1998 10:16:53 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.57]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA492E; Sat, 31 Oct 1998 19:16:44 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810292247.OAA05813@austin.polstra.com> Date: Sat, 31 Oct 1998 19:20:26 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: John Polstra Subject: Re: Another compile error Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John, On 29-Oct-98 John Polstra wrote: > In article , > Jeroen Ruigrok/Asmodai wrote: >> install -c -o root -g wheel -m 644 drivers/make_device_driver.sh,v >> /usr/share/ex >> amples/drivers/make_device_driver.sh,v >> install -c -o root -g wheel -m 644 etc/Attic/ttys,v >> /usr/share/examples/etc/Atti >> c/ttys,v >> install: /usr/share/examples/etc/Attic/ttys,v: No such file or directory >> *** Error code 71 >> >> Am I wrong into thinking that Attic isn't needed for the example directory >> in >> /usr/share/examples/etc or am I just blabbering? =) > It looks to me like you did a CVSup update using cvs mode (no > "tag" or "data" specification in your cvsupfile), and spammed your > /usr/src tree with a bunch of RCS files. I'd suggest that you > study the CVSup tutorial in the FreeBSD Handbook, the CVSup FAQ at > , and the cvsup(1) > manual page. Pay special attention to the difference between "cvs > mode" and "checkout mode". Well, that's the fun part ;) I have the handbook and studied the man pages for CVSup, and this is the result of my cvsupfile (any recommendations welcome offcourse ;): [diabolique] asmodai $ more cvsupfile *default tag=. *default release=cvs *default host=cvsup.internat.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/src *default delete *default use-rel-suffix *default compress src-all cvs-crypto doc-all ports-archivers ports-base ports-comms ports-devel ports-editors ports-lang ports-mail ports-net ports-news ports-security ports-shells ports-sysutils ports-textproc ports-www ports-x11 When I do a cvsup -L2 cvsupfile the update goes well... And the following make world goes a LOOOONG end before giving errors. So IMHO if the mode I am using isn't correct I should have gotten errors a lot earlier in the process. For reference I use 'time make world -j4 | tee make-world.year.month.day.try.txt' to log my attempts at making world. While I was typing this mail another make world just failed, but at a different point. Looking at the size it's about 400k larger than the first one. So I think that the workaround (if it really is one that is) I used worked. I did a mkdir /usr/share/examples/etc/Attic and cp'd ttys,v into it. time needed: 9190.99s real 5767.59s user 1207.92s system I will take a look at yer page though John, thanks for the pointer. Regards, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 10:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26705 for freebsd-current-outgoing; Sat, 31 Oct 1998 10:16:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26677 for ; Sat, 31 Oct 1998 10:16:50 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.57]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA27C for ; Sat, 31 Oct 1998 19:16:41 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 31 Oct 1998 19:20:24 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: sys/msdosfs problems? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after trying yet another make world today I got this (I use a standard make world -j4 mostly preceeded by a make clean): --- msdosfs_vnops.o --- cc -nostdinc -O -pipe -DMSDOSFS -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- -I/usr/obj/aout/src/src/lkm/msdos -I/usr/obj/aout/src/src/lkm/msdos/@ -I/usr/obj/aout/src/src/tmp/usr/include -aout -DVFS_LKM -DMODVNOPS=msdos_modvnops -c /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c --- msdosfs_vfsops.o --- /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c: In function `msdosfs_sync': /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c:916: structure has no member named `lh_first' *** Error code 1 --- msdosfs_vnops.o --- /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c: In function `msdosfs_fsync': /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c:838: structure has no member named `lh_first' /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c:839: structure has no member named `le_next' /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c:831: warning: `bp' might be used uninitialized in this function /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c:831: warning: `nbp' might be used uninitialized in this function *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Hope this is of use to someone. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 10:31:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28013 for freebsd-current-outgoing; Sat, 31 Oct 1998 10:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28008 for ; Sat, 31 Oct 1998 10:31:53 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id CAA21104; Sun, 1 Nov 1998 02:31:30 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810311831.CAA21104@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: FreeBSD Current Subject: Re: sys/msdosfs problems? In-reply-to: Your message of "Sat, 31 Oct 1998 19:20:24 +0100." Date: Sun, 01 Nov 1998 02:31:30 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > Hi, > > after trying yet another make world today I got this (I use a standard make > world -j4 mostly preceeded by a make clean): [..] > cc -nostdinc -O -pipe -DMSDOSFS -DKERNEL -Wreturn-type -Wcomment > -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat > -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- > -I/usr/obj/aout/src/src/lkm/msdos -I/usr/obj/aout/src/src/lkm/msdos/@ > -I/usr/obj/aout/src/src/tmp/usr/include -aout -DVFS_LKM > -DMODVNOPS=msdos_modvnops -c > /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c > --- msdosfs_vfsops.o --- > /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c: In function > `msdosfs_sync': > /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c:916: structure has no > member named `lh_first' This is most likely because you've got a snapshot of the tree in between a series of commits. Try another cvsup and see how you go. Make sure you can compile your kernel before you restart your make world - to make sure that you're up to date. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 10:44:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29339 for freebsd-current-outgoing; Sat, 31 Oct 1998 10:44:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29322 for ; Sat, 31 Oct 1998 10:44:00 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from bellatlantic.net (client201-122-108.bellatlantic.net [151.201.122.108]) by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id NAA10487 for ; Sat, 31 Oct 1998 13:43:37 -0500 (EST) Message-ID: <363B13DA.4DF649DF@bellatlantic.net> Date: Sat, 31 Oct 1998 13:42:50 +0000 From: Donn Miller X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Latest gcc (2.8.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone know when the stock gcc in FreeBSD will be upgraded to => 2.8.1? I don't think it's worth upgrading at this time. It might be worth waiting until gcc matures a little bit more (i.e. namespaces become implemented) before any development begins on integrating the latest gcc into FreeBSD.. Thanks Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 10:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29343 for freebsd-current-outgoing; Sat, 31 Oct 1998 10:44:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29330 for ; Sat, 31 Oct 1998 10:44:01 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.57]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAAE0C; Sat, 31 Oct 1998 19:43:57 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810311831.CAA21104@spinner.netplex.com.au> Date: Sat, 31 Oct 1998 19:47:39 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Peter Wemm Subject: Re: sys/msdosfs problems? Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Oct-98 Peter Wemm wrote: > Jeroen Ruigrok/Asmodai wrote: >> Hi, >> >> after trying yet another make world today I got this (I use a standard make >> world -j4 mostly preceeded by a make clean): > [..] >> cc -nostdinc -O -pipe -DMSDOSFS -DKERNEL -Wreturn-type -Wcomment >> -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes >> -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat >> -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- >> -I/usr/obj/aout/src/src/lkm/msdos -I/usr/obj/aout/src/src/lkm/msdos/@ >> -I/usr/obj/aout/src/src/tmp/usr/include -aout -DVFS_LKM >> -DMODVNOPS=msdos_modvnops -c >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c >> --- msdosfs_vfsops.o --- >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c: In function >> `msdosfs_sync': >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c:916: structure has no >> member named `lh_first' > > This is most likely because you've got a snapshot of the tree in between a > series of commits. Try another cvsup and see how you go. Make sure you > can compile your kernel before you restart your make world - to make sure > that you're up to date. Just did. Ehm, now I am confused ;) I am supposed to get a successfull make world before I can attempt to make a new kernel or can one try them at whim? As in no dependancy on each other but the cvsup files. Thanks, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01537 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:02:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01532 for ; Sat, 31 Oct 1998 11:02:33 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id LAA22746; Sat, 31 Oct 1998 11:02:28 -0800 (PST) (envelope-from jdp) Message-Id: <199810311902.LAA22746@austin.polstra.com> To: Jeroen Ruigrok/Asmodai cc: current@FreeBSD.ORG Subject: Re: Another compile error In-reply-to: Your message of "Sat, 31 Oct 1998 19:20:26 +0100." Date: Sat, 31 Oct 1998 11:02:28 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, that's the fun part ;) > I have the handbook and studied the man pages for CVSup, and this is the result > of my cvsupfile (any recommendations welcome offcourse ;): > > [diabolique] asmodai $ more cvsupfile > *default tag=. > *default release=cvs > *default host=cvsup.internat.freebsd.org > *default base=/usr/local/etc/cvsup > *default prefix=/src > *default delete > *default use-rel-suffix > *default compress > src-all [...] That looks good. But there shouldn't be any directories in your tree named "Attic", and there shouldn't be any files named "*,v". I think that at some point when you were first experimenting with CVSup, you must have done an update without the "tag=." statement in your supfile. I recommend that you do this to clean it up: cd /src find . \( -name '*,v' -o -name .depend -o -type l \) -print | xargs rm -f find -d . -name Attic | xargs rm -rf cd /usr/obj rm -rf * # (You will get some error messages -- don't worry chflags -R 0 * rm -rf * # (Yes, again) Now do another CVSup update just for good measure. Then try your make world, and I think it will work this time. Good luck, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:14:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02778 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:14:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02767 for ; Sat, 31 Oct 1998 11:14:10 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.57]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1CD9; Sat, 31 Oct 1998 20:14:03 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810311557.XAA20449@spinner.netplex.com.au> Date: Sat, 31 Oct 1998 20:17:37 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Peter Wemm Subject: Re: kernel compile problem Cc: freebsd-current@FreeBSD.ORG, Dmitry Valdov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Oct-98 Peter Wemm wrote: > Dmitry Valdov wrote: >> Hi! >> >> I've just cvsuped -current and there is a problem compiling kernel: > >> ../../kern/vfs_bio.c: In function `bufinit': >> ../../kern/vfs_bio.c:182: structure has no member named `le_next' >> ../../kern/vfs_bio.c:182: `NOLIST' undeclared (first use this function) >> ../../kern/vfs_bio.c:182: (Each undeclared identifier is reported only once >> ../../kern/vfs_bio.c:182: for each function it appears in.) > > You got a cvsup in between commits.. Try again and you should be OK. just spotted this one too ;) How can ye make sure ye ain't between commits? cvsup it about 15-30 minutes later and try again to make? regards, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:15:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03142 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:15:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03128 for ; Sat, 31 Oct 1998 11:15:35 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id DAA21351; Sun, 1 Nov 1998 03:15:17 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810311915.DAA21351@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: FreeBSD Current Subject: Re: sys/msdosfs problems? In-reply-to: Your message of "Sat, 31 Oct 1998 19:47:39 +0100." Date: Sun, 01 Nov 1998 03:15:17 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > On 31-Oct-98 Peter Wemm wrote: > > Jeroen Ruigrok/Asmodai wrote: > >> Hi, > >> > >> after trying yet another make world today I got this (I use a standard mak e > >> world -j4 mostly preceeded by a make clean): > > [..] > >> cc -nostdinc -O -pipe -DMSDOSFS -DKERNEL -Wreturn-type -Wcomment > >> -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes > >> -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat > >> -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- > >> -I/usr/obj/aout/src/src/lkm/msdos -I/usr/obj/aout/src/src/lkm/msdos/@ > >> -I/usr/obj/aout/src/src/tmp/usr/include -aout -DVFS_LKM > >> -DMODVNOPS=msdos_modvnops -c > >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vnops.c > >> --- msdosfs_vfsops.o --- > >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c: In function > >> `msdosfs_sync': > >> /src/src/lkm/msdos/../../sys/msdosfs/msdosfs_vfsops.c:916: structure has n o > >> member named `lh_first' > > > > This is most likely because you've got a snapshot of the tree in between a > > series of commits. Try another cvsup and see how you go. Make sure you > > can compile your kernel before you restart your make world - to make sure > > that you're up to date. > > Just did. > > Ehm, now I am confused ;) > I am supposed to get a successfull make world before I can attempt to make a > new kernel or can one try them at whim? As in no dependancy on each other but > the cvsup files. > > Thanks, If msdos_vfsops.c is referring to lh_first, then you are missing some updates. Check that you have: /* $Id: msdosfs_vfsops.c,v 1.38 1998/10/31 15:31:24 peter Exp $ */ Don't forget there is a time lag when cvsup mirrors are involved. It's possible that the mirror you are using took it's periodic snapshot in between the commits. The other problem was that the tree was broken for an uncomfortably long time - half an hour or so. I try and commit stuff with log messages that are applicable to the files being committed rather than huge jumbo commits with huge log messages that are not relavant to 95% of the touched files. However, this doesn't work when your 3-year-old disturbs you right in the middle.. :-] So, the source tree got left for a short while in a state where the kernel and LKMs would not compile. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:17:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03257 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:17:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03240 for ; Sat, 31 Oct 1998 11:17:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00692; Sat, 31 Oct 1998 11:16:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810311916.LAA00692@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: Mike Smith , John Polstra , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Sat, 31 Oct 1998 13:46:50 +0800." <199810310546.NAA18245@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 11:16:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There's probably a call for a 'bootmodules' variable as well; until we > > get more people using this and asking for features I'm not sure what's > > worth adding and what's just fluff. > > > > How many people would be interested in labels and conditional branches, > > for example? > > What I'd like is something like this: > > timeout 10 "Press enter to boot now, any other key to abort" > load kernel > load foo.ko > boot > > Ie: have an abort-script type capability. It'd save all that loading and > unloading. That's what I meant about the bootmodules comment: set bootfile /kernel set bootmodules foo;bar;nfs;linux autoboot 10 "Press enter to boot, any other key to abort" I probably want to extend 'read' to do something useful with single keystrokes: read -a -t 10 -p "Press enter to boot, other to abort" key if $key == 10 goto boot if $key == 13 goto boot exit :boot load kernel load foo.ko boot This would make single-key point-and-shoot menus pretty easy too; you could even use the response to determine the goto target: :loop set key 1 echo "1 kernel" echo "2 kernel.test" read -t 10 -p "Select >" key -goto label$key goto loop :label1 boot kernel :label2 boot kernel.test By ignoring the error, you get the "if this label doesn't exist" behaviour. I think it's pretty clear that scripts shouldn't be echoed as the default. I hate the DOS "echo on" syntax; any better suggestions? Just another variable? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:24:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03787 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:22:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03710 for ; Sat, 31 Oct 1998 11:22:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA10842; Sat, 31 Oct 1998 19:23:42 GMT Date: Sat, 31 Oct 1998 19:23:42 +0000 (GMT) From: Doug Rabson To: Donn Miller cc: current@freebsd.org Subject: Re: Latest gcc (2.8.1) In-Reply-To: <363B13DA.4DF649DF@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 31 Oct 1998, Donn Miller wrote: > Anyone know when the stock gcc in FreeBSD will be upgraded to => 2.8.1? > I don't think it's worth upgrading at this time. It might be worth > waiting until gcc matures a little bit more (i.e. namespaces become > implemented) before any development begins on integrating the latest gcc > into FreeBSD.. Egcs supports namespaces (I use them and they appear to work correctly). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:35:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05307 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:35:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05297 for ; Sat, 31 Oct 1998 11:35:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00799; Sat, 31 Oct 1998 11:30:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810311930.LAA00799@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wolfram Schneider cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 13:06:59 +0100." <19981031130659.A17271@panke.de.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 11:30:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got these yesterday: /kernel.tc: microtime: 909767572.611009 > 909767572.-694775046 /kernel.tc: getmicrotime: 909800392.486279 > 909800392.476272 /kernel.tc: mi_switch: switching history 35692.614679 > 35692.-694771102 /kernel.tc: mi_switch: switching history 35694.694002225 > 35692.617390 /kernel.tc: calcru: negative time of -1390738769 usec for pid 271 (xconsole) /kernel.tc: pid 262 (XF86_SVGA), uid 0: exited on signal 6 (core dumped) /kernel.tc: calcru: negative time of -336242384 usec for pid 262 (XF86_SVGA) also with NTIMECOUNTER set to 10 (and the code that uses it is in the kernel). > On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: > > Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to > > 10 and tell me if it works. > > The 18th `make world' got a > calcru: negative time of -695373488 usec for pid 23724 (as) > > and a little bit later died with > pid 4542 (ld), uid 0: exited on signal 11 (core dumped) > > Wolfram > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:37:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05758 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:37:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05737; Sat, 31 Oct 1998 11:37:38 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id NAA30816; Sat, 31 Oct 1998 13:37:19 -0600 (CST) Date: Sat, 31 Oct 1998 13:37:18 -0600 (CST) From: Steve Price To: "Jordan K. Hubbard" cc: Satoshi Asami , mike@smith.net.au, mark@grondar.za, sos@FreeBSD.ORG, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: <15699.909845800@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 31 Oct 1998, Jordan K. Hubbard wrote: # > very hard to detect on the building machine. The scheduling, which # > didn't leave him any time to put the ELF packages up for testing # > before the release, is at fault. # # You can say that again. Despite having plenty of warning, and we're # talking several month's worth here, the task was apparently dumped at # the very last moment on Justin and Steve. I know that Steve certainly # wasn't very happy about how this was done and it certainly took Mike # and I by surprise as well - there was some even doubt, for awhile # there, as to whether 3.0 would ship with a packages collection at all. Yes, I was indeed frazzled. Justin did a great job! I just wished he had let me help a wee bit more. I'm sure he got quite annoyed after awhile with all my "here's a patch" messages. It was just too much for one person to do in the limited time available. # In any case, all finger-pointing and indignation aside, if the # ports/packages phase of each new release is to occur both on-time and # with minimum stress on all concerned, we're going to have to figure # out well in advance just who's going to take on the job of physically # generating and segregating all the packages and distfiles. I # certainly don't want to be scratching my head and trying to figure out # who's "job" it's even supposed to be a day before a release is due and # the various ports volunteers don't want to be stuck with doing the job # on a moment's notice, either. I know my half-witted attempt at creating a tool to help with this flopped miserably, but my offer still stands. I'd like to talk to you some more about what you require in such a tool. # My suggestion would be that we either: a) go to some sort of # automation scheme which [re]builds packages on an ongoing basis and, # at release time, I just take a snapshot of the collection or b) We try I've got a reasonably fast, well-connected machine that I could offer up to help with this. All I need is a little direction from Justin on how he setup his chroot'd build environment. # appointing a ports/packages releasemeister who's responsible for doing # in ports what I do for src each time a release rolls around. This Having more than one would be even better. :) I'll volunteer to be one of 'em for the next release. # person could be paid since it's important to Walnut Creek CDROM # that packages and distfiles be rendered into ISO images periodically, # especially now that we have this "toolkit" CD for FreeBSD in addition # to the usual 4 CD sets. # # Thoughts? # # - Jordan # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-current" in the body of the message # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:43:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06345 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:43:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06338 for ; Sat, 31 Oct 1998 11:43:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00852; Sat, 31 Oct 1998 11:38:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810311938.LAA00852@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Wolfram Schneider , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 15:09:53 +0100." <13694.909842993@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 11:38:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So is this better or worse than normal ? In my case, it's hard to tell. Sometimes I won't see anything for days, sometimes it's impossible to do anything for a few hours. I'd say perhaps a _little_ better, but not much. > In message <19981031130659.A17271@panke.de.freebsd.org>, Wolfram Schneider writes: > >On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: > >> Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to > >> 10 and tell me if it works. > > > >The 18th `make world' got a > >calcru: negative time of -695373488 usec for pid 23724 (as) > > > >and a little bit later died with > >pid 4542 (ld), uid 0: exited on signal 11 (core dumped) > > > >Wolfram > > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07009 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:49:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07003 for ; Sat, 31 Oct 1998 11:49:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA14688; Sat, 31 Oct 1998 20:47:26 +0100 (CET) To: Mike Smith cc: Wolfram Schneider , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 11:30:59 PST." <199810311930.LAA00799@dingo.cdrom.com> Date: Sat, 31 Oct 1998 20:47:26 +0100 Message-ID: <14686.909863246@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could you try to change these lines from the bottom of mi_switch() ... if (switchtime.tv_sec) p->p_switchtime = switchtime; else microuptime(&p->p_switchtime); ... to simply: microuptime(&p->p_switchtime); Poul-Henning In message <199810311930.LAA00799@dingo.cdrom.com>, Mike Smith writes: > >I got these yesterday: > >/kernel.tc: microtime: 909767572.611009 > 909767572.-694775046 >/kernel.tc: getmicrotime: 909800392.486279 > 909800392.476272 >/kernel.tc: mi_switch: switching history 35692.614679 > 35692.-694771102 >/kernel.tc: mi_switch: switching history 35694.694002225 > 35692.617390 >/kernel.tc: calcru: negative time of -1390738769 usec for pid 271 (xconsole) >/kernel.tc: pid 262 (XF86_SVGA), uid 0: exited on signal 6 (core dumped) >/kernel.tc: calcru: negative time of -336242384 usec for pid 262 (XF86_SVGA) > >also with NTIMECOUNTER set to 10 (and the code that uses it is in the >kernel). > >> On 1998-10-28 12:19:30 +0100, Poul-Henning Kamp wrote: >> > Please try to increase "NTIMECOUNTER" in /sys/kern/kern_clock.c to >> > 10 and tell me if it works. >> >> The 18th `make world' got a >> calcru: negative time of -695373488 usec for pid 23724 (as) >> >> and a little bit later died with >> pid 4542 (ld), uid 0: exited on signal 11 (core dumped) >> >> Wolfram >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:49:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07034 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:49:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07025 for ; Sat, 31 Oct 1998 11:49:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00899; Sat, 31 Oct 1998 11:44:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810311944.LAA00899@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Wolfram Schneider , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 18:09:18 +0100." <14100.909853758@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 11:44:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a reminder; laptop, NE2000 ethernet. No nasty interrupt-eating code. > In message <19981031172606.A20248@panke.de.freebsd.org>, Wolfram Schneider writes: > >On 1998-10-31 15:09:53 +0100, Poul-Henning Kamp wrote: > >> So is this better or worse than normal ? > > > >I see no differences to the version without the NTIMECOUNTER hack. > >One of 26 `make world' failed, usually after 27 hours. > >I'm running `make world' in a chroot environment. > > >My host is connected with a laplink cable. > > Hmm, theres a clue, the if_lp0 stuff may disable interrupts for VERY long > periods of time. Try setting NTIMERCOUNTER way up, lets try 300 for a go. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07606 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:55:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07601 for ; Sat, 31 Oct 1998 11:55:05 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.58.57]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA11F3 for ; Sat, 31 Oct 1998 19:55:01 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 31 Oct 1998 20:58:44 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: cvsup .4.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------------------- building m3core ---------------------- mkdir FreeBSD2 --- building in FreeBSD2 --- m3 -w1 -why -O -times -a libm3core.a -F/var/tmp/qkU24275 new source -> compiling ../src/Csupport/Common/hand.c [snip more of these new source lines] new source -> compiling ../src/runtime/FreeBSD2/RTHeapDepC.c ../src/runtime/FreeBSD2/RTHeapDepC.c: In function `semctl': ../src/runtime/FreeBSD2/RTHeapDepC.c:927: number of arguments doesn't match prototype /usr/include/sys/sem.h:174: prototype declaration new source -> compiling ../src/runtime/FreeBSD2/_fpsetjmp.s [snip more of these new source lines] new source -> compiling ../src/word/Word.m3 compilation failed => not building library "libm3core.a" [ But why? =) ] *** error code 1 (ignored) missing libm3core.a: not building libm3core.so.6.0 [ Not surprisingly ;) ] [ following might all be related ] install: libm3core.a: No such file or directory *** error code 71 "/usr/ports/lang/modula-3-lib/work/m3/m3core/FreeBSD2/.M3SHIP", line 322: command execute failed *** call stack *** "/usr/ports/lang/modula-3-lib/work/m3/m3core/FreeBSD2/.M3SHIP", line 322: call to built-in exec "/usr/ports/lang/modula-3-lib/work/m3/m3core/FreeBSD2/.M3SHIP", line 6: call to procedure install_file m3ship: /usr/ports/lang/modula-3-lib/work/installed/bin/quake failed (status = 256) *** error code 255 "/usr/ports/lang/modula-3-lib/work/m3/src/m3makefile", line 61: command execute failed *** call stack *** "/usr/ports/lang/modula-3-lib/work/m3/src/m3makefile", line 61: call to built-in exec "/usr/ports/lang/modula-3-lib/work/m3/src/m3makefile", line 84: call to procedure BuildChunk m3build: /usr/ports/lang/modula-3-lib/work/installed/bin/quake failed (status = 256) *** Error code 255 Stop. *** Error code 1 John, if I missed something, could ye give me a hint? ;) Thanks... The autofetching and patching went like a breeze... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 11:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08023 for freebsd-current-outgoing; Sat, 31 Oct 1998 11:57:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08009 for ; Sat, 31 Oct 1998 11:57:20 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id NAA23144; Sat, 31 Oct 1998 13:56:47 -0600 (CST) Message-Id: <199810311956.NAA23144@ns.tar.com> From: "Richard Seaman, Jr." To: "Mike Smith" Cc: "info@highwind.com" , "eischen@vigrid.com" , "current@freebsd.org" Date: Sat, 31 Oct 98 13:56:47 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Kernel threading (was Re: Thread Scheduler bug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 14:46:14 -0800, Mike Smith wrote: >> Of course, it we had kernel threads, the pthreads code would be >> a *lot* simpler and maybe less prone to bugs, the kernel would >> do the preemption for us, and context switches would be much >> faster than the current user thread implementation. :) >> >> I've been poking around in the code, and I'd guess that a >> uniprocessor kernel threads implementation wouldn't involve >> all that much work. However, I understand there's are fair >> amount of kernel work that needs to be done for SMP kernel >> threads. > >My suggestion to you: get started. Once you run into the SMP-related >issues, you'll find that there are people that can help you. But if >you wait for an SMP-kernel-thread-guru to materialise from nowhere, >we're never going to get anywhere. Here's what my "poking around" amounts to at this point. I'd be willing to carry it further, if there's interest. But, I also think that others want to see a somewhat different direction (ie. mixed user/kernel threads). I've grafted some of John Dyson's kernel threading code into the existing pthread code: 1) pthread_create will create a kernel thread via a call to Dyson's thrfork call, which in turn calls rfork. 2) pthread wait calls (eg. mutex wait, cond wait, etc) use the syscall thr_sleep 3) pthread wakeup calls (eg. in mutex and cond unlocks) use the syscall thr_wakeup 4) sched_yield and pthread_yield use the syscall yield, though when _POSIX_PRIORITY_SCHEDULING is enabled in the kernel, it would be easy enough to use the sched_yield syscall. I've only tested a handful of programs, and I know there's more work to be done to put this into any kind of shape for general testing. However, I can at least verify the following: 1) It runs my benchmark programs correctly that I was using when I found a few of the user thread scheduler bugs. It appears that context switches are 2-3 times faster than the current implemenation of user threads, maybe more in some circumstances. (This is contrary to conventional wisdom that user threads should be faster, but the reasons have been discussed on this list recently). 2) Highwinds schedBug.C test code runs as I think Highwinds intends it. 3) Highwinds condBug.C test code runs correctly. Things the current code doesn't do: 1) Lots, probably. It hasn't been tested, really. 2) Mixed user/kernel threads. I haven't even attempted to code for this. (AFAIK you can compile one app against the user thread library and another against the kernel thread library and run them both at the same time. You just can't mix user and kernel threads in the same app). 3) SMP kernel threads. I haven't actually tried this, but my reading of the rfork code is that the RFMEM option needed for kernel threads is not currently implemented for SMP kernels. John Dyson has also listed other SMP kernel issues that need to be addressed for SMP kernel threads. However, I'm not aware of much, if any SMP specific coding that needs to be done in the pthreads library itself. The only possible areas I know of might be enhanced spinlock handling, and the question of whether some kind of memory barrier instruction is needed in the mutex locking code. 4) sigwait. Also signal handling is untested and no doubt needs work. 5) I think more work needs to be done for proper exit and termination handling. This is largely unexplored, though pthread_join and pthread_exit at least "work", ie. threads get joined and/or terminated. Whether all the proper cleanup gets done is untested. My general strategy was this. I took the existing libc_r code and copied it to a new directory. The "uthread" code was split into 2 directories: 1) code that is user thread specific. I have modified this code only very slightly so that the interfaces to the "generic" code is the same for user and kernel threads. Also, I've added code for a bug fix or two, and added code for deferred cancelation points in some of the wrapped syscalls. 2) code that is "generic" or could easily be made "generic", where what I mean by generic is that it could be used for either kernel or user thread libraries. I've made some changes to this code in addition to making the interfaces to the kernel/user schedulers consistent. a) I've coded, but not tested, pthread_mutexattr type interfaces and altered the mutex code to handle the 4 mutex types in the XSH5 spec. I've also tried to bring the mutex error checking up to spec, and made the default mutex type handling conform to the spec. b) Added added error checks to the pthread_cond code as indicated in the spec. c) I've coded, but not tested, pthread_canel interfaces and added deferred cancellation points to syscalls as indicated in the specs. Asynchronous cancellation coding still needs to be done. d) The _POSIX_THREAD_PRIORITY_SCHEDULING interfaces are coded but untested. Then, I've created a third directory which contains the kernel thread specific code. I've preserved separate make files so that both user thread and kernel thread libraries can be generated useing the same "generic" pthread code. If this general approach is of any interest, let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 12:35:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13126 for freebsd-current-outgoing; Sat, 31 Oct 1998 12:35:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13117 for ; Sat, 31 Oct 1998 12:35:43 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA10845; Sun, 1 Nov 1998 07:43:04 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810312043.HAA10845@cimlogic.com.au> Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-Reply-To: <199810311956.NAA23144@ns.tar.com> from "Richard Seaman, Jr." at "Oct 31, 98 01:56:47 pm" To: lists@tar.com Date: Sun, 1 Nov 1998 07:43:04 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. wrote: > Here's what my "poking around" amounts to at this point. I'd be willing > to carry it further, if there's interest. But, I also think that others > want to see a somewhat different direction (ie. mixed user/kernel threads). [...] > My general strategy was this. I took the existing libc_r code and > copied it to a new directory. The "uthread" code was split into 2 > directories: [...] > Then, I've created a third directory which contains the kernel thread > specific code. I've preserved separate make files so that both user > thread and kernel thread libraries can be generated useing the same > "generic" pthread code. > > If this general approach is of any interest, let me know. Kernel threads should use libpthread and libc, not libc_r. You can't mix kernel thread syscalls with user-thread syscalls because the styles are incompatible (blocking vs non-blocking). You can't mix kernel thread scheduling with user-thread scheduling. It doesn't sound like you have made any attempt to update the user-space knowledge of the running thread. As a result you will mix all errno codes and all user-space locking. This is a fundamental issue that needs to be designed, not hacked. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 13:18:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18116 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:18:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18109 for ; Sat, 31 Oct 1998 13:18:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00662; Sat, 31 Oct 1998 13:18:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810312118.NAA00662@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: lists@tar.com, current@FreeBSD.ORG Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-reply-to: Your message of "Sun, 01 Nov 1998 07:43:04 +1100." <199810312043.HAA10845@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 13:18:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Richard Seaman, Jr. wrote: > > If this general approach is of any interest, let me know. > > Kernel threads should use libpthread and libc, not libc_r. You can't mix > kernel thread syscalls with user-thread syscalls because the styles are > incompatible (blocking vs non-blocking). You can't mix kernel thread > scheduling with user-thread scheduling. It doesn't sound like you have > made any attempt to update the user-space knowledge of the running thread. > As a result you will mix all errno codes and all user-space locking. This > is a fundamental issue that needs to be designed, not hacked. It sounds like the two of you should cooperate on it then; Richard has clearly managed to get his head around at least some of the kernel issues, while you're on top of the user-space stuff. This issue calls for constructive cooperation as well as design. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 13:21:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18544 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:21:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18539 for ; Sat, 31 Oct 1998 13:21:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00643; Sat, 31 Oct 1998 13:15:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810312115.NAA00643@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Mike Smith , Wolfram Schneider , current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 20:47:26 +0100." <14686.909863246@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 13:15:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Two, about 35 minutes apart: mi_switch: switching history 1030.150249 > 1030.-695235605 calcru: negative time of -669373627 usec for pid 295 (xterm) mi_switch: switching history 3252.553835 > 3252.-694832079 pid 258 (XF86_SVGA), uid 0: exited on signal 6 (core dumped) calcru: negative time of -652603588 usec for pid 258 (XF86_SVGA) getmicrotime: 909868434.985186 > 909868434.975187 > Could you try to change these lines from the bottom of mi_switch() > > ... > if (switchtime.tv_sec) > p->p_switchtime = switchtime; > else > microuptime(&p->p_switchtime); > ... > > to simply: > > microuptime(&p->p_switchtime); > > Poul-Henning -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 13:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18979 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:27:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18973 for ; Sat, 31 Oct 1998 13:27:03 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id PAA23692; Sat, 31 Oct 1998 15:26:50 -0600 (CST) Message-Id: <199810312126.PAA23692@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" Cc: "current@freebsd.org" Date: Sat, 31 Oct 98 15:26:50 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Kernel threading (was Re: Thread Scheduler bug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998 07:43:04 +1100 (EST), John Birrell wrote: >Richard Seaman, Jr. wrote: >Kernel threads should use libpthread and libc, not libc_r. Agreed, sort of. I don't use libc_r. If you're going to implement deferred cancellation points, I think you still need to wrap some syscalls, so you still need to generate a separate libc somewhere. The "kernel" syscalls drop into libpthread, in a manner analagous to what happens in libc_r, but the wrappers are different, and the syscalls that are wrapped are different. >You can't mix >kernel thread syscalls with user-thread syscalls because the styles are >incompatible (blocking vs non-blocking). Agreed. A pure kernel thread implementation seems much simpler because you just get rid of all the syscall wrapping that's needed to implement user thread blocking i/o. Or, am I missing something? >You can't mix kernel thread >scheduling with user-thread scheduling. Agreed. In kernel threads the kernel scheduler does all the work. You can get rid of all the 19 pages of user thread scheduling code. >It doesn't sound like you have >made any attempt to update the user-space knowledge of the running thread. >As a result you will mix all errno codes and all user-space locking. This >is a fundamental issue that needs to be designed, not hacked. Well, the user-space knowledge of the running thread comes from pthread_self, which in the case I've implemented this comes from the code John Dyson provided to the list a while back. errno codes are returned on the thread stack, if I understand his code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 13:28:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19288 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:28:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19281 for ; Sat, 31 Oct 1998 13:28:10 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA10997; Sun, 1 Nov 1998 08:35:32 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810312135.IAA10997@cimlogic.com.au> Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-Reply-To: <199810312118.NAA00662@dingo.cdrom.com> from Mike Smith at "Oct 31, 98 01:18:12 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 1 Nov 1998 08:35:32 +1100 (EST) Cc: jb@cimlogic.com.au, lists@tar.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > It sounds like the two of you should cooperate on it then; Richard has > clearly managed to get his head around at least some of the kernel > issues, while you're on top of the user-space stuff. I think that the code in the FreeBSD kernel is inappropriate for a POSIX thread implementation. The syscall design needs to change. And the management of pid entries for threads needs to change too. Then there are the multi-architecture issues. I doubt that I'll have time in the next 6 months. Unless someone finds some dollars. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 13:40:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20721 for freebsd-current-outgoing; Sat, 31 Oct 1998 13:40:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20713 for ; Sat, 31 Oct 1998 13:40:04 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA11039; Sun, 1 Nov 1998 08:47:34 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199810312147.IAA11039@cimlogic.com.au> Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-Reply-To: <199810312126.PAA23692@ns.tar.com> from "Richard Seaman, Jr." at "Oct 31, 98 03:26:50 pm" To: lists@tar.com Date: Sun, 1 Nov 1998 08:47:34 +1100 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. wrote: > Agreed, sort of. I don't use libc_r. If you're going to implement > deferred cancellation points, I think you still need to wrap some > syscalls, so you still need to generate a separate libc somewhere. > The "kernel" syscalls drop into libpthread, in a manner analagous > to what happens in libc_r, but the wrappers are different, and the > syscalls that are wrapped are different. If you wrapper the syscalls, you get compatibility problems. If the syscalls block in the kernel, then that's where thay should be cancelled. > Well, the user-space knowledge of the running thread comes from pthread_self, > which in the case I've implemented this comes from the code John Dyson > provided to the list a while back. errno codes are returned on the > thread stack, if I understand his code. Is that the user LDT implementation? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 14:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23321 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:08:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23316 for ; Sat, 31 Oct 1998 14:08:55 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA16996; Sat, 31 Oct 1998 14:08:44 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: John Birrell , lists@tar.com, current@FreeBSD.ORG Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-reply-to: Your message of "Sat, 31 Oct 1998 13:18:12 PST." <199810312118.NAA00662@dingo.cdrom.com> Date: Sat, 31 Oct 1998 14:08:43 -0800 Message-ID: <16992.909871723@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It sounds like the two of you should cooperate on it then; Richard has > clearly managed to get his head around at least some of the kernel > issues, while you're on top of the user-space stuff. I agree. While not perhaps adopting the perfect approach, at least Richard brings some very welcome *movement* to an issue which has been stalled for a regrettably long period of time. Let's try to run (cooperatively) with this and hopefully arrive at some working, architecturally clean kernel threads for FreeBSD! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 14:30:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25402 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:30:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25395 for ; Sat, 31 Oct 1998 14:30:25 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id QAA24045; Sat, 31 Oct 1998 16:30:14 -0600 (CST) Message-Id: <199810312230.QAA24045@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" Cc: "current@freebsd.org" Date: Sat, 31 Oct 98 16:30:13 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Kernel threading (was Re: Thread Scheduler bug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998 08:47:34 +1100 (EST), John Birrell wrote: >If you wrapper the syscalls, you get compatibility problems. If the >syscalls block in the kernel, then that's where thay should be cancelled. Well, I don't know nearly as much about this as you do, so please bear with me. The syscall wrapper I am talking about looks like this (for the syscalls that are defined as canellation points): pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, &oldtype); _thread_sys_xxx (..........) pthread_setcanceltype (oldtype, NULL); Then, if another thread does a pthread_cancel on the thread that's in the syscall, and if the cancel state of the thread is CANCEL_ENABLE, it sends it a signal SIGCANCEL. SIGCANCEL will have to be defined (Linux uses SIGUSR2, if I'm not mistaken). You have to have a signal handler setup too, obviously, which does a pthread_exit (in the case of ASYNCHRONOUS cancellation). If the syscall can be interrupted by the signal, you'll break out of the wait and exit. If not, you'll exit when the second pthread_setcanceltype function is called. What am I missing? >Is that the user LDT implementation? I don't know. Its whatever code was posted in John Dyson's message of August 20, 1998, to the -hackers list, titled "rfork stuff". I have a copy if you need one. I'm just copying some of his code blindly, with only partial (or no) comprehension. If there's something fundamentally wrong with it, it would be helpful if you noted it so I don't waste my time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 14:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26289 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:38:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26284 for ; Sat, 31 Oct 1998 14:38:04 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id QAA24079; Sat, 31 Oct 1998 16:37:48 -0600 (CST) Message-Id: <199810312237.QAA24079@ns.tar.com> From: "Richard Seaman, Jr." To: "Jordan K. Hubbard" Cc: "John Birrell" , "current@freebsd.org" Date: Sat, 31 Oct 98 16:37:47 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Kernel threading (was Re: Thread Scheduler bug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 31 Oct 1998 14:08:43 -0800, Jordan K. Hubbard wrote: >I agree. While not perhaps adopting the perfect approach, at least >Richard brings some very welcome *movement* to an issue which has been >stalled for a regrettably long period of time. Let's try to run >(cooperatively) with this and hopefully arrive at some working, >architecturally clean kernel threads for FreeBSD! Just to be clear. I'm happy to co-operate and share code with anyone. In fact, I'd be happy for someone else to just handle it all. In the absence of someone else will to handle it all, I'm happy to contribute what I can. The *only* reason I'd be hesitant to share any code at this moment is that its still pretty messy, and I'd be embarrassed, and since its barely tested, people would rightfully shoot all kinds of holes in it. When its in a better state I'd be happy to post it somewhere where anyone can whack at it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 14:54:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27853 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:54:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27837 for ; Sat, 31 Oct 1998 14:53:59 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id XAA09921; Sat, 31 Oct 1998 23:59:13 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 31 Oct 1998 23:59:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-Reply-To: <199810302013.MAA01772@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > I think this is important opportunity - let's not miss it without good > > reasons... As I said, there are people among us who can even write small > > enough Forth kernel for our purposes. > > I have no desire to miss it. Give me a compact Forth interpreter that > links against libstand and you'll be seeing it everywhere Real Soon. Here it is: it's called FICL (Forth Inspired Command Language), written in ANSI C, designed to be embedded in other programs, implements ANS-Forth CORE, CORE-EXT, TOOLS, SEARCH wordlists and its own OOP extensions. You can find it on taygeta. It's freeware, and actively maintained. Because of its purpose, it comes in a form of library. Here is its contents: abial# size libficl.a text data bss dec hex filename 2403 0 0 2403 963 dict.o (ex libficl.a) 989 20 0 1009 3f1 ficl.o (ex libficl.a) 892 0 0 892 37c math64.o (ex libficl.a) 63 3130 0 3193 c79 softcore.o (ex libficl.a) 674 0 0 674 2a2 stack.o (ex libficl.a) 253 0 0 253 fd sysdep.o (ex libficl.a) 2154 44 0 2198 896 vm.o (ex libficl.a) 18222 92 0 18314 478a words.o (ex libficl.a) (this can be still reduced if we limit ourselves to CORE words - I think 1/3 of words.o would go away). I haven't tried to link it against libstand, and you probably know better than I what is and what is not possible with it, so below is list of the symbols it needs from libc, when linking a simple test program: abial# nm testmain|grep "U "|sort -u U ___runetype U ___tolower U __assert U atexit U exit U fputs U free U longjmp U malloc U puts U setjmp U sprintf U strcat U strcmp U strncpy U vsprintf So, how about that? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 17:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15504 for freebsd-current-outgoing; Sat, 31 Oct 1998 17:32:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15499 for ; Sat, 31 Oct 1998 17:32:06 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id UAA06957 for ; Sat, 31 Oct 1998 20:32:02 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16601; Sat, 31 Oct 1998 20:32:02 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id UAA04810 for freebsd-current@freebsd.org; Sat, 31 Oct 1998 20:32:02 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199811010132.UAA04810@bb01f39.unx.sas.com> Subject: scsi disk (cam?) problems To: freebsd-current@FreeBSD.ORG Date: Sat, 31 Oct 1998 20:32:02 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My -CURRENT system has been experiencing problems since I converted it to cam awhile back. The following show up on my console, and then my disks are useless until I completely shutdown, powerdown my drive array, power it back on, and reboot. I have 4 identical drives configured as a ccd. They have been serving me well more about a year... If anyone has any ideas on how I can track down the problem, please let me know! Thanks, John /dev/ccd0a 2155550 1268428 714678 64% /snap /dev/ccd0b 2155550 1020154 962952 51% /usr/obj /dev/ccd0d 17244630 12876242 2988818 81% /pub Snipped from messages: (This kernel was built on the 28th), I'm now on a kernel built Oct 31. Oct 28 18:34:56 FreeBSD /kernel: ccd0-3: Concatenated disk drivers Oct 28 18:34:56 FreeBSD /kernel: Waiting 5 seconds for SCSI devices to settle Oct 28 18:34:56 FreeBSD /kernel: changing root device to wd0s1a Oct 28 18:34:56 FreeBSD /kernel: da0 at ahc0 bus 0 target 1 lun 0
da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI2 device da3: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI2 device da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) Oct 29 02:25:00 FreeBSD /kernel: (da1:ahc0:0:2:0): tagged openings now 64 Oct 29 02:25:00 FreeBSD /kernel: (da1:ahc0:0:2:0): tagged openings now 63 Oct 29 02:25:16 FreeBSD /kernel: (da0:ahc0:0:1:0): tagged openings now 64 Oct 29 02:25:16 FreeBSD /kernel: (da0:ahc0:0:1:0): tagged openings now 63 Oct 29 02:26:21 FreeBSD /kernel: (da2:ahc0:0:3:0): tagged openings now 64 Oct 29 02:26:21 FreeBSD /kernel: (da2:ahc0:0:3:0): tagged openings now 63 Oct 29 02:28:46 FreeBSD /kernel: (da3:ahc0:0:4:0): tagged openings now 64 Oct 29 02:28:46 FreeBSD /kernel: (da3:ahc0:0:4:0): tagged openings now 63 Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 17:47:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17204 for freebsd-current-outgoing; Sat, 31 Oct 1998 17:47:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17199 for ; Sat, 31 Oct 1998 17:47:03 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id RAA24376; Sat, 31 Oct 1998 17:46:57 -0800 (PST) (envelope-from jdp) Message-Id: <199811010146.RAA24376@austin.polstra.com> To: asmodai@wxs.nl Subject: Re: kernel compile problem In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sat, 31 Oct 1998 17:46:57 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jeroen Ruigrok/Asmodai wrote: > > On 31-Oct-98 Peter Wemm wrote: > > > > You got a cvsup in between commits.. Try again and you should be OK. > > just spotted this one too ;) > > How can ye make sure ye ain't between commits? cvsup it about 15-30 minutes > later and try again to make? There's no way, in general. Remember, almost everybody CVSups from a mirror site. Mirrors can get updated in the middle of a commit too. In that case, the problem doesn't get fixed until the next time that the mirror updates itself from freefall. Many mirrors update hourly, but not all of them do. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 18:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20088 for freebsd-current-outgoing; Sat, 31 Oct 1998 18:08:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20077 for ; Sat, 31 Oct 1998 18:08:56 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA27408; Sat, 31 Oct 1998 19:08:50 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811010208.TAA27408@panzer.plutotech.com> Subject: Re: scsi disk (cam?) problems In-Reply-To: <199811010132.UAA04810@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Oct 31, 98 08:32:02 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Sat, 31 Oct 1998 19:08:50 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote... > Hi, > > My -CURRENT system has been experiencing problems since I converted > it to cam awhile back. The following show up on my console, and then > my disks are useless until I completely shutdown, powerdown my drive > array, power it back on, and reboot. I have 4 identical drives configured > as a ccd. They have been serving me well more about a year... > > If anyone has any ideas on how I can track down the problem, please > let me know! > > Thanks, > John > > /dev/ccd0a 2155550 1268428 714678 64% /snap > /dev/ccd0b 2155550 1020154 962952 51% /usr/obj > /dev/ccd0d 17244630 12876242 2988818 81% /pub > > Snipped from messages: (This kernel was built on the 28th), I'm now on > a kernel built Oct 31. [ ... ] > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack Well, what's happening here is that one of your disks is returning an error, and keeps returning that error. Reads and writes in the da driver have a retry count of 4. So by the time we print out the message above, the command has already been retried four times. We may also have taken a number of error recovery actions to try to bring the device back. Because your disk is in a CCD array, though, you won't be able to access the CCD array when one disk in the array is marked as invalid. For some reason, though, the sense information for the error in question isn't getting printed out. It may be that there's a bug in the sense code table somewhere. How often does this happen? Could you try booting with -v, and see if you can reproduce the problem? I think that that (booting with -v) should cause the error to be printed out. If I know the error, I may be able to help you work around it, or at least tell you that one of your disks is on the blink. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 18:26:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22290 for freebsd-current-outgoing; Sat, 31 Oct 1998 18:26:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22283 for ; Sat, 31 Oct 1998 18:26:10 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id EAA12766; Sun, 1 Nov 1998 04:26:05 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id FAA05026; Sun, 1 Nov 1998 05:26:22 +0200 (EET) (envelope-from vallo) Message-ID: <19981101052621.B291@matti.ee> Date: Sun, 1 Nov 1998 05:26:21 +0200 From: Vallo Kallaste To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: scsi disk (cam?) problems Reply-To: vallo@matti.ee References: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811010208.TAA27408@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811010208.TAA27408@panzer.plutotech.com>; from Kenneth D. Merry on Sat, Oct 31, 1998 at 07:08:50PM -0700 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack > > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack > > Well, what's happening here is that one of your disks is returning an > error, and keeps returning that error. Reads and writes in the da driver > have a retry count of 4. So by the time we print out the message above, > the command has already been retried four times. We may also have taken a > number of error recovery actions to try to bring the device back. *** My machine panicked half a hour ago with same 'Invalidating pack' messages. BTW, I forget to remove softupdates and I'm running SMP right now and maybe this was the cause. I'm in the middle of upgrading my hardware so it may be related. Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 18:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22597 for freebsd-current-outgoing; Sat, 31 Oct 1998 18:26:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22592 for ; Sat, 31 Oct 1998 18:26:34 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA24541; Sat, 31 Oct 1998 18:26:27 -0800 (PST) (envelope-from jdp) Message-Id: <199811010226.SAA24541@austin.polstra.com> To: asmodai@wxs.nl Subject: Re: cvsup .4.2 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sat, 31 Oct 1998 18:26:27 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jeroen Ruigrok/Asmodai wrote: > ---------------------- building m3core ---------------------- > mkdir FreeBSD2 > --- building in FreeBSD2 --- > m3 -w1 -why -O -times -a libm3core.a -F/var/tmp/qkU24275 > new source -> compiling ../src/Csupport/Common/hand.c > > [snip more of these new source lines] > > new source -> compiling ../src/runtime/FreeBSD2/RTHeapDepC.c > ../src/runtime/FreeBSD2/RTHeapDepC.c: In function `semctl': > ../src/runtime/FreeBSD2/RTHeapDepC.c:927: number of arguments doesn't match > prototype > /usr/include/sys/sem.h:174: prototype declaration [...] > John, if I missed something, could ye give me a hint? ;) Please let me know what version of FreeBSD you're running. Also please send me the output of: ident /usr/include/sys/sem.h and grep define /usr/include/osreldate.h Then I can help you fix it. PS - CVSup problems really should be reported to . John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 18:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22780 for freebsd-current-outgoing; Sat, 31 Oct 1998 18:28:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22775 for ; Sat, 31 Oct 1998 18:28:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA27505; Sat, 31 Oct 1998 19:28:29 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811010228.TAA27505@panzer.plutotech.com> Subject: Re: scsi disk (cam?) problems In-Reply-To: <19981101052621.B291@matti.ee> from Vallo Kallaste at "Nov 1, 98 05:26:21 am" To: vallo@matti.ee Date: Sat, 31 Oct 1998 19:28:29 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste wrote... > "Kenneth D. Merry" wrote: > > > > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack > > > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack > > > > Well, what's happening here is that one of your disks is returning an > > error, and keeps returning that error. Reads and writes in the da driver > > have a retry count of 4. So by the time we print out the message above, > > the command has already been retried four times. We may also have taken a > > number of error recovery actions to try to bring the device back. > > *** > > My machine panicked half a hour ago with same 'Invalidating pack' > messages. BTW, I forget to remove softupdates and I'm running SMP > right now and maybe this was the cause. I'm in the middle of upgrading > my hardware so it may be related. Softupdates and SMP don't have anything to do with the 'Invalidating pack' messages. They're most likely because of some hardware failure. Try booting with -v, and see if you see sense information printed out along with the 'Invalidating pack' message. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 19:15:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26880 for freebsd-current-outgoing; Sat, 31 Oct 1998 19:15:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26873 for ; Sat, 31 Oct 1998 19:15:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA00686; Sat, 31 Oct 1998 19:15:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811010315.TAA00686@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels In-reply-to: Your message of "Sat, 31 Oct 1998 23:59:13 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 19:15:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 30 Oct 1998, Mike Smith wrote: > > Here it is: it's called FICL (Forth Inspired Command Language), written in > ANSI C, designed to be embedded in other programs, implements ANS-Forth > CORE, CORE-EXT, TOOLS, SEARCH wordlists and its own OOP extensions. You > can find it on taygeta. It's freeware, and actively maintained. Yes, I looked at it before. > Because of its purpose, it comes in a form of library. Here is its > contents: > > abial# size libficl.a > text data bss dec hex filename > 2403 0 0 2403 963 dict.o (ex libficl.a) > 989 20 0 1009 3f1 ficl.o (ex libficl.a) > 892 0 0 892 37c math64.o (ex libficl.a) > 63 3130 0 3193 c79 softcore.o (ex libficl.a) > 674 0 0 674 2a2 stack.o (ex libficl.a) > 253 0 0 253 fd sysdep.o (ex libficl.a) > 2154 44 0 2198 896 vm.o (ex libficl.a) > 18222 92 0 18314 478a words.o (ex libficl.a) > > (this can be still reduced if we limit ourselves to CORE words - I think > 1/3 of words.o would go away). It builds a little bigger here; it weighs in at about 40k. If you strip the OO extensions out it comes down to about 22k. I don't know whether there's much we can strip from the core wordset; I'll leave that for the FORTH guruen to argue over. At 22k (plus whatever it costs to bind it in) I think we have a goer. Doug's resolved the Alpha space issues too, so it should be comfy. > I haven't tried to link it against libstand, and you probably know better > than I what is and what is not possible with it, so below is list of > the symbols it needs from libc, when linking a simple test program: > > abial# nm testmain|grep "U "|sort -u > U ___runetype > U ___tolower These are ctype noise; the libstand ctype replacements are simpler (more stupid). > U __assert We need an assert. > U atexit > U exit There's no exit callout yet, but this looks like it may be noise as well (there are no calls in the library) > U fputs > U puts These are in the sysdep shim, and a trivial putchar() routine solves that. > U free > U malloc > U strcat > U strcmp > U strncpy > U sprintf > U vsprintf Easy enough; we need to grow a vsprintf though. > U longjmp > U setjmp These could be tricky; I'll have to look at how the Alpha does them to be sure. Worst case I guess they just come in from libc; they should be self-contained. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 21:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12321 for freebsd-current-outgoing; Sat, 31 Oct 1998 21:38:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12316 for ; Sat, 31 Oct 1998 21:38:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA01330; Sat, 31 Oct 1998 21:37:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811010537.VAA01330@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Andrzej Bialecki , current@FreeBSD.ORG Subject: BootForth (was Re: New boot loader and alternate kernels) In-reply-to: Your message of "Sat, 31 Oct 1998 19:15:10 PST." <199811010315.TAA00686@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 21:37:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 30 Oct 1998, Mike Smith wrote: > > > > Here it is: it's called FICL (Forth Inspired Command Language), written in > > ANSI C, designed to be embedded in other programs, implements ANS-Forth > > CORE, CORE-EXT, TOOLS, SEARCH wordlists and its own OOP extensions. You > > can find it on taygeta. It's freeware, and actively maintained. Ok. The infrastructure and making it build "right" were pretty easy. It can probably lose some more weight still, and I have no idea if it works properly on the Alpha yet, but one thing at a time. So, how do I integrate it into the loader? Do we want to make it optional? Do we want to strip the loader back to the bare essentials and use BootFORTH for as much as possible? Is a "middle road" approach preferred? It's quite likely that we could actually save a fair amount of weight by using Forth code for quite a lot of smarts. If we decide to lose some of the ANS Forth words we indeed go below 25k, and that wouldn't be hard to bloat out past with only a little more code elsewhere. Any Forth hackers want to play with something new and funky? In particular, some ideas on "standard" system-interface words would be handy. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 31 22:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18722 for freebsd-current-outgoing; Sat, 31 Oct 1998 22:47:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18706 for ; Sat, 31 Oct 1998 22:47:16 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id HAA05374; Sun, 1 Nov 1998 07:44:52 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Sun, 1 Nov 1998 07:44:52 +0100 (CET) From: Leif Neland To: Jeroen Ruigrok/Asmodai cc: Peter Wemm , freebsd-current@FreeBSD.ORG, Dmitry Valdov Subject: Re: kernel compile problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You got a cvsup in between commits.. Try again and you should be OK. > > just spotted this one too ;) > > How can ye make sure ye ain't between commits? cvsup it about 15-30 minutes > later and try again to make? > Is the problem that committing isn't 'atomical'? How about if the committer started by committing /usr/src/DONT_MAKE_WORLD_NOW then committed various stuff, then removed /usr/src/DONT_MAKE_WORLD_NOW This file could contain an explanation why the world shouldn't be made. The makefile should then check for the existance of this file. This could be implemented right now. It won't require updating cvsup and cvsupd. But this will give problems when several people are updating different parts of the tree... To make it more clean, it should be done in cvsupd and perhaps cvsup. It could be implemented by modifying using cvsupd's ability to check out the version of the tree as it were on a certain time. The committer sends it a command/file/signal, and then new additions made after that time is not seen by someone who requests the latest versions. After everything is committed, the committer removes the lock. Perhaps this should lock be on committer-resolution, so one committer forgetting a lock/being hit by an 18-wheeler won't lock the entire tree. If somebody _really_ wants the latest versions, one could specify an date=-1 or something instead of date=. What happens if somebody starts a cvsup, and files gets committed before the cvsup is finished? Are those updates seen? The tag date=. shouldn't mean "as late as possible", but "at the start of this cvsup-run", so to get a consistent snapshot of the tree. cvsupd should keep track of each clients starttime, and not supply later checkouts. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message