From owner-freebsd-hackers Sun Sep 24 4:44: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id 8901037B422 for ; Sun, 24 Sep 2000 04:44:06 -0700 (PDT) Received: from student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.9.3/MQT) with ESMTP id NAA14192 for ; Sun, 24 Sep 2000 13:44:04 +0200 (METDST) Message-ID: <39CDE90F.32F1693@student.utwente.nl> Date: Sun, 24 Sep 2000 13:44:15 +0200 From: Theo van Klaveren X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: Getting data from the ATAPI-CD driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Having some time on my hands, I decided to work on AudioFS a bit. First thing was, of course, to get it to work at all :-) As detailed in my previous post to this list, the way Linux's AudioFS does this doesn't work for FreeBSD (using IOCTL's). So, Soren Schmidt's advice was to directly get data from the atapi_cd driver. Doing some research, I see two ways to do this: 1) Using atapi_queue_cmd(), like the way atapi_cd's ioctl handler does it but not copyout'ing the retrieved data. To do this _outside_ the atapi_cd driver, however, I need it's atapi_softc, and I haven't figured out how to do that yet, except that I have to use driver_get_softc(), which needs a device_t, which I don't know how to get. I'm not sure this is the 'right' way. 2) Using VOP_STRATEGY on the acd device in audiofs_strategy(), the way the cd9660 filesystem does it. I'm not sure this will work, but it sure looks like it. This would also reduce code complexity, but I'm not sure it's 'right' either. What would be the 'right' way? -- Theo van Klaveren http://home.student.utwente.nl/t.vanklaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 24 6: 6:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 668DA37B422 for ; Sun, 24 Sep 2000 06:06:34 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA06572; Sun, 24 Sep 2000 15:11:07 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009241311.PAA06572@freebsd.dk> Subject: Re: Getting data from the ATAPI-CD driver In-Reply-To: <39CDE90F.32F1693@student.utwente.nl> from Theo van Klaveren at "Sep 24, 2000 01:44:15 pm" To: t.vanklaveren@student.utwente.nl (Theo van Klaveren) Date: Sun, 24 Sep 2000 15:11:07 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Theo van Klaveren wrote: > As detailed in my previous post to this list, the way Linux's AudioFS > does this doesn't work for FreeBSD (using IOCTL's). So, Soren Schmidt's > advice was to directly get data from the atapi_cd driver. Doing some > research, I see two ways to do this: > > 1) Using atapi_queue_cmd(), like the way atapi_cd's ioctl handler does > it but not copyout'ing the retrieved data. To do this _outside_ the > atapi_cd driver, however, I need it's atapi_softc, and I haven't figured > out how to do that yet, except that I have to use driver_get_softc(), > which needs a device_t, which I don't know how to get. I'm not sure this > is the 'right' way. > > 2) Using VOP_STRATEGY on the acd device in audiofs_strategy(), the way > the cd9660 filesystem does it. I'm not sure this will work, but it sure > looks like it. This would also reduce code complexity, but I'm not sure > it's 'right' either. > > What would be the 'right' way? 2. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 24 9: 2: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id AACA937B422 for ; Sun, 24 Sep 2000 09:02:03 -0700 (PDT) Received: from stinky.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id SAA46457; Sun, 24 Sep 2000 18:05:46 +0200 (IST) Message-Id: <5.0.0.23.0.20000924174247.01fcf440@192.116.19.220> X-Sender: mustafa@192.116.19.220 X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.23 (Beta) Date: Sun, 24 Sep 2000 17:43:54 +0200 To: William Lloyd From: Mustafa Deeb Subject: Re: Denying ISDN using Radius Cc: freebsd-hackers@freebsd.org In-Reply-To: <20000923183542.A73405@galt.slap.net> References: <5.0.0.25.0.20000923225141.009f9dc0@mail.palnet.com> <5.0.0.25.0.20000923225141.009f9dc0@mail.palnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, it is cistron radius, what about a time limit, can I define a 20 working hours for this user, and after that he can't connect? cheers At 06:35 PM 9/23/2000 -0400, William Lloyd wrote: >Hi Mustafa! > >On Sat, 23 Sep 2000, Mustafa N. Deeb wrote: > > > hi, > > > > I don't know if someone did this before, > > I want to deny ISDN connections to my PRI's, unless the user is in the > > ISDN group. > > can I make radius allow/deny ISDN based on GID > > > >Yes it's easy. > >You didn't say which of the dozen Radius daemons you run. > >You do it in your users file. > >-bill > >-- >William Lloyd mailto:wlloyd@slap.net | No stuff here To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 24 14:47: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id B738F37B422 for ; Sun, 24 Sep 2000 14:46:59 -0700 (PDT) Received: from student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.9.3/MQT) with ESMTP id XAA27276; Sun, 24 Sep 2000 23:45:45 +0200 (METDST) Message-ID: <39CE7613.3640BA2@student.utwente.nl> Date: Sun, 24 Sep 2000 23:45:55 +0200 From: Theo van Klaveren X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: hackers@FreeBSD.ORG Subject: Re: Getting data from the ATAPI-CD driver References: <200009241311.PAA06572@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > 2) Using VOP_STRATEGY on the acd device in audiofs_strategy(), the way > > the cd9660 filesystem does it. I'm not sure this will work, but it sure > > looks like it. This would also reduce code complexity, but I'm not sure > > it's 'right' either. > > > > What would be the 'right' way? > > 2. > > -Søren Thanks, got it to work. I'm going to clean up my code, then test it some more and release it sometime this week. -- Theo van Klaveren http://home.student.utwente.nl/t.vanklaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 2: 2:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7077D37B422 for ; Mon, 25 Sep 2000 02:02:20 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA52122; Mon, 25 Sep 2000 11:02:09 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Pentchev Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: virtual console 'snapshot'? References: <20000923011753.A15311@ringwraith.office1.bg> From: Dag-Erling Smorgrav Date: 25 Sep 2000 11:02:09 +0200 In-Reply-To: Peter Pentchev's message of "Sat, 23 Sep 2000 01:17:53 +0300" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Pentchev writes: > Is there anything like Linux's /dev/vcs* in FreeBSD? That is, some way > to obtain the complete view of a virtual console - characters, attributes, > everything? The snoop device gives deltas, but never the complete > picture, unless the program running on that console decides to redraw > the whole thing. It shouldn't be difficult to implement, unless you want the snapshot to be consistent per-session - in which case you need to store a copy of the vty buffer at the moment the device is opened, which I don't think is possible in FreeBSD. Apart from that, the only ugliness is the need to fondle syscons' privates. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 2:58:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 87C7F37B43C; Mon, 25 Sep 2000 02:58:36 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13dV1u-0003ia-00; Mon, 25 Sep 2000 12:58:34 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13dV1s-0006JQ-00; Mon, 25 Sep 2000 12:58:32 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation In-reply-to: Your message of Thu, 21 Sep 2000 09:58:31 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Sep 2000 12:58:32 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009211658.JAA00670@mass.osd.bsdi.com>you write: }> In message <200009210648.XAA02252@mass.osd.bsdi.com>you write: }> }> }Mostly I guess I'd really like it to simply save *all* of the DHCP }> }response in the environment. Just "dhcp.xxx" where xxx is the parameter }> }value would probably do it, or we can argue about names for everything if }> }there aren't established names already. }> } }> what's in a name ;-) }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } ok, so now i can setenv(dhc.xxx, val). I would very much like to make them available as sysctl dhcp.xxx, the only problem, is that the sysctl interface is prety much static, so has anybody lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them into the mid ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 3: 1: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id CFD1D37B43E; Mon, 25 Sep 2000 03:00:58 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 86F8E2B22A; Mon, 25 Sep 2000 05:00:58 -0500 (CDT) Date: Mon, 25 Sep 2000 03:00:58 -0700 From: Paul Saab To: Danny Braniss Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation Message-ID: <20000925030058.A57787@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Mon, Sep 25, 2000 at 12:58:32PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > ok, so now i can setenv(dhc.xxx, val). > > I would very much like to make them available as sysctl dhcp.xxx, the only > problem, is that the sysctl interface is prety much static, so has anybody > lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them > into the mid ... It is dynamic in -current. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 3:10:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id C894037B42C for ; Mon, 25 Sep 2000 03:10:43 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13dVDa-0003tQ-00; Mon, 25 Sep 2000 13:10:38 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13dVDY-0006Kl-00; Mon, 25 Sep 2000 13:10:36 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: pxe@cs.huji.ac.il Cc: freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation In-reply-to: Your message of Mon, 25 Sep 2000 03:00:58 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Sep 2000 13:10:36 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000925030058.A57787@elvis.mu.org>you write: }Danny Braniss (danny@cs.huji.ac.il) wrote: }> ok, so now i can setenv(dhc.xxx, val). }> }> I would very much like to make them available as sysctl dhcp.xxx, the only }> problem, is that the sysctl interface is prety much static, so has anybody }> lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them }> into the mid ... } }It is dynamic in -current. } so now i have to get current to compile :-) btw, i asked this before, and got answers that were not to the point. i would very much like to be able and compile to /usr/obj, and install not on /, but say ${dest}/ ... danny }-- }Paul Saab }Technical Yahoo }paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org }Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 3:14:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 7CCCC37B422 for ; Mon, 25 Sep 2000 03:14:54 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1000) id 1B26E2B228; Mon, 25 Sep 2000 05:14:54 -0500 (CDT) Date: Mon, 25 Sep 2000 03:14:54 -0700 From: Paul Saab To: Danny Braniss Cc: pxe@cs.huji.ac.il, freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation Message-ID: <20000925031453.A58037@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from danny@cs.huji.ac.il on Mon, Sep 25, 2000 at 01:10:36PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > In message <20000925030058.A57787@elvis.mu.org>you write: > }Danny Braniss (danny@cs.huji.ac.il) wrote: > }> ok, so now i can setenv(dhc.xxx, val). > }> > }> I would very much like to make them available as sysctl dhcp.xxx, the only > }> problem, is that the sysctl interface is prety much static, so has anybody > }> lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them > }> into the mid ... > } > }It is dynamic in -current. > } > btw, i asked this before, and got answers that were not to the point. > i would very much like to be able and compile to /usr/obj, and install > not on /, but say ${dest}/ ... make DESTDIR=/path installworld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 7: 1:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by hub.freebsd.org (Postfix) with ESMTP id 8917137B422; Mon, 25 Sep 2000 07:01:32 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [161.44.133.25]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA12506; Mon, 25 Sep 2000 10:01:30 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id KAA18109; Mon, 25 Sep 2000 10:02:51 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200009251402.KAA18109@bmcgover-pc.cisco.com> To: qa@freebsd.org, jkh@freebsd.org Cc: hackers@freebsd.org Subject: Sysinstall HTTP Proxy install information... Date: Mon, 25 Sep 2000 10:02:51 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just in case someone has more time than I do to look at this, I've been playing with sysinstall, most notably installation through an HTTP proxy. I've found what I believe to be two distinct bugs. The first is when you try to set one of the pre-fab choices, such as installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears that the request sent to the web proxy does not include the "i386" part of the path. I tried to trace it down, and found in ftp.c that it should be being added. Strange, but... The second I experience when hand-entering the URL and proxy information. It appears in this case, it tries to download the .inf file, correctly (ie - bin.inf), and it claims it parses it. However, something odd seems to happen, and sysinstall does not realize that it is supposed to be receiving chunks, and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". This is after an hour or so of looking (the most time I could get in over the weekend with 3 kids). It looks like it should be an easy fix for someone who has time to get familiar with how sysinstall works (which is where most of my hour went). Anyhow, as mentioned, this is a pointer for anyone who may have more free time than I. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 7:23:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 26FF737B424 for ; Mon, 25 Sep 2000 07:23:13 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id 7B76EDC7E; Mon, 25 Sep 2000 10:17:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 679FBDC7D for ; Mon, 25 Sep 2000 10:17:58 -0400 (EDT) Date: Mon, 25 Sep 2000 10:17:58 -0400 (EDT) From: David Miller To: freebsd-hackers@freebsd.org Subject: Multipath routing in 4.x? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I searched the archives and found a few references to patches for 2.x for multipath routing. I'd like not to have to go that far back..... How did something as useful as this to anyone using freebsd as a router not make it into release 3 and 4? Is there any work going on to add it? Thanks! --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 8:32:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from trauco.colomsat.net.co (trauco.colomsat.net.co [200.13.195.2]) by hub.freebsd.org (Postfix) with ESMTP id EF3B037B43C for ; Mon, 25 Sep 2000 08:32:02 -0700 (PDT) Received: from yahoo.com (200.13.214.89) by trauco.colomsat.net.co (NPlex 4.0.068) id 39CBBB7000009A8F for hackers@FreeBSD.ORG; Mon, 25 Sep 2000 10:26:46 -0500 Message-ID: <39CF70A6.A7828890@yahoo.com> Date: Mon, 25 Sep 2000 10:35:02 -0500 From: "Yonny Cardenas B." Organization: Ingenieria Integral Ltda. X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Can't work out which disk we are booting from Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I apologize for ask this in the hackers list, but I have looked in the history mail list in the FreeBSD web site and I haven't found nothing similar. I can't start to install FreeBSD 4.0 or FreeBSD 3.8. It says: "Can't work which disk we are booting from." I have a IBM PC 300GL, with Pentiun II (333Mhz), Ram 64Mb and a H.D. IDE of 3228Mb. When I start to install FreeBSD 2.5 all run fine, and the installation is finished without problems. Can I do? Thanks for your help. The following are the complete messages: BTX loader 1.00 BTX version is 101 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/64501kB available memory FreeBSD/i386 bootstrap loader Revision 0.7 Can't work out which disk we are booting from. Guessed BIOS device 0x8b no found by probes, defaulting to disk0: Booting [kernel] can't load 'kernel' +-------------------------------------------------------------------------+ | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554 | | | 3451565, 2176251 ext. 16 | | Opus Ingenieria | Fax : +57 1 3458343 | | Calle 61 # 5-44 Piso 3 | E-mail: y-carden@uniandes.edu.co | | Santafe de Bogota D.C.,Colombia | ycardena@yahoo.com | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 11: 9:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sighup.aventail.com (sighup.aventail.com [64.94.142.130]) by hub.freebsd.org (Postfix) with ESMTP id B779437B422 for ; Mon, 25 Sep 2000 11:09:46 -0700 (PDT) Received: from leo.in.aventail.com (leo.in.aventail.com [192.168.1.136]) by sighup.aventail.com (8.11.0/8.11.0) with ESMTP id e8PI9kj08892 for ; Mon, 25 Sep 2000 11:09:46 -0700 (PDT) Received: from voyager (exit.dmz.aventail.com [192.168.25.132]) by leo.in.aventail.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id S55PFW52; Mon, 25 Sep 2000 11:08:13 -0700 From: "Kevin Mills" To: "FreeBSD Hackers" Subject: atomic operations Date: Mon, 25 Sep 2000 11:12:51 -0700 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the atomic_* functions in , but noticed that they have no return value. What I need is a function that increments/decrements the given value *and* returns the new value in an atomic operation. I suppose this is possible, yes? How would one modify the assembly to make this work? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 12:20:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-203.dsl.snfc21.pacbell.net [63.206.89.203]) by hub.freebsd.org (Postfix) with ESMTP id 5696137B43E for ; Mon, 25 Sep 2000 12:20:01 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8PJKmA13875; Mon, 25 Sep 2000 12:20:50 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009251920.e8PJKmA13875@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: dhcp boot was: Re: diskless workstation In-reply-to: Your message of "Mon, 25 Sep 2000 12:58:32 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Sep 2000 12:20:48 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > }> what's in a name ;-) > }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not > }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and > }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. > } > > ok, so now i can setenv(dhc.xxx, val). > > I would very much like to make them available as sysctl dhcp.xxx, the only > problem, is that the sysctl interface is prety much static, so has anybody > lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them > into the mid ... If you are setting stuff in the loader environment, you can get it back after the system has booted with 'kenv'. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 12:32:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-203.dsl.snfc21.pacbell.net [63.206.89.203]) by hub.freebsd.org (Postfix) with ESMTP id DA78837B50D for ; Mon, 25 Sep 2000 12:31:45 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8PJT9A13950; Mon, 25 Sep 2000 12:29:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009251929.e8PJT9A13950@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Yonny Cardenas B." Cc: hackers@FreeBSD.ORG Subject: Re: Can't work out which disk we are booting from In-reply-to: Your message of "Mon, 25 Sep 2000 10:35:02 CDT." <39CF70A6.A7828890@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Sep 2000 12:29:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Booting from CDROM is not (yet) supported on these systems. You will have to boot from floppy disk (you can install from CDROM OK). > I apologize for ask this in the hackers list, but I have looked in the > history mail list in the FreeBSD web site and I haven't found nothing > similar. > > I can't start to install FreeBSD 4.0 or FreeBSD 3.8. > > It says: "Can't work which disk we are booting from." > > I have a IBM PC 300GL, with Pentiun II (333Mhz), Ram 64Mb and a H.D. IDE > of 3228Mb. > > When I start to install FreeBSD 2.5 all run fine, and the installation > is finished without problems. > > Can I do? > > Thanks for your help. > > The following are the complete messages: > > BTX loader 1.00 BTX version is 101 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 639kB/64501kB available memory > > FreeBSD/i386 bootstrap loader Revision 0.7 > Can't work out which disk we are booting from. > Guessed BIOS device 0x8b no found by probes, defaulting to disk0: > Booting [kernel] > can't load 'kernel' > > +-------------------------------------------------------------------------+ > | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554 | > | | 3451565, 2176251 ext. 16 | > | Opus Ingenieria | Fax : +57 1 3458343 | > | Calle 61 # 5-44 Piso 3 | E-mail: y-carden@uniandes.edu.co | > | Santafe de Bogota D.C.,Colombia | ycardena@yahoo.com | > +-------------------------------------------------------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 12:49:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by hub.freebsd.org (Postfix) with ESMTP id 704BF37B422 for ; Mon, 25 Sep 2000 12:49:24 -0700 (PDT) Received: from rzstud1.rz.uni-karlsruhe.de (rzstud1.rz.uni-karlsruhe.de [129.13.197.1]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.16 #1) id 13deFf-0005LN-00; Mon, 25 Sep 2000 21:49:23 +0200 Received: from un1i by rzstud1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 13deFf-0003TB-00; Mon, 25 Sep 2000 21:49:23 +0200 From: Philipp Mergenthaler To: freebsd-hackers@FreeBSD.ORG, bmcgover@cisco.com Subject: Re: Sysinstall HTTP Proxy install information... X-Newsgroups: list.freebsd-hackers In-Reply-To: <200009251402.KAA18109@bmcgover-pc.cisco.com> User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (HP-UX/B.11.00 (9000/800)) Message-Id: Date: Mon, 25 Sep 2000 21:49:23 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009251402.KAA18109@bmcgover-pc.cisco.com> you wrote: > Just in case someone has more time than I do to look at this, I've been playing > with sysinstall, most notably installation through an HTTP proxy. [...] > The first is when you try to set one of the pre-fab choices, such as > installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears that > the request sent to the web proxy does not include the "i386" part of the Correct. The method by which the directory on the FTP server is found has been changed in ftp.c some time ago. Since installing via proxy relied on this, it is now broken. A patch is in PR bin/21449 > The second I experience when hand-entering the URL and proxy information. It > appears in this case, it tries to download the .inf file, correctly (ie - > bin.inf), and it claims it parses it. However, something odd seems to happen, > and sysinstall does not realize that it is supposed to be receiving chunks, > and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". Hm, I don't see this here - it correctly fetches all chunks of the desired distribution. IIRC, the installation falls back to "distribution.tgz" if it couldn't get "distribution.inf". I'll take another look at it. Bye, Philipp -- http://www.uni-karlsruhe.de/~un1i/ (,.) \\\00 ) \= ) cc_|\_,^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 12:57: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E85FC37B422; Mon, 25 Sep 2000 12:56:54 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8PJulU10089; Mon, 25 Sep 2000 12:56:47 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Philipp Mergenthaler Cc: freebsd-hackers@FreeBSD.ORG, bmcgover@cisco.com, jhb@FreeBSD.ORG Subject: Re: Sysinstall HTTP Proxy install information... In-Reply-To: Message from Philipp Mergenthaler of "Mon, 25 Sep 2000 21:49:23 +0200." Date: Mon, 25 Sep 2000 12:56:47 -0700 Message-ID: <10085.969911807@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Correct. The method by which the directory on the FTP server is found > has been changed in ftp.c some time ago. Since installing via proxy > relied on this, it is now broken. > > A patch is in PR bin/21449 Thanks! A lot of "cooks" have been in sysinstall lately and the upshot of it is that nobody really fully knows that code any more, including me. :) I'll review the patch and commit it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 12:59:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by hub.freebsd.org (Postfix) with ESMTP id C5A4837B43E; Mon, 25 Sep 2000 12:59:00 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [161.44.133.25]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA05873; Mon, 25 Sep 2000 15:58:58 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id QAA19569; Mon, 25 Sep 2000 16:00:18 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200009252000.QAA19569@bmcgover-pc.cisco.com> To: Philipp Mergenthaler Cc: freebsd-hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Sysinstall HTTP Proxy install information... In-reply-to: Your message of "Mon, 25 Sep 2000 21:49:23 +0200." Date: Mon, 25 Sep 2000 16:00:18 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <200009251402.KAA18109@bmcgover-pc.cisco.com> you wrote: > > Just in case someone has more time than I do to look at this, I've been pl aying > > with sysinstall, most notably installation through an HTTP proxy. > [...] > > The first is when you try to set one of the pre-fab choices, such as > > installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears t hat > > the request sent to the web proxy does not include the "i386" part of the > > Correct. The method by which the directory on the FTP server is found > has been changed in ftp.c some time ago. Since installing via proxy > relied on this, it is now broken. > > A patch is in PR bin/21449 > Ok. Well, if 4.1.1 hasn't been cut yet, Jordan should probably grab this patch and commit. > > The second I experience when hand-entering the URL and proxy information. It > > appears in this case, it tries to download the .inf file, correctly (ie - > > bin.inf), and it claims it parses it. However, something odd seems to happ en, > > and sysinstall does not realize that it is supposed to be receiving chunks , > > and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". > > Hm, I don't see this here - it correctly fetches all chunks of the > desired distribution. IIRC, the installation falls back to > "distribution.tgz" if it couldn't get "distribution.inf". I'll take > another look at it. This would be good. The debug screen had shown that it had fetched bin.inf, and had "parsed" it. Looking at my web proxy log, it had requested bin.inf, and the URL was correct, so I'm guessing it either a.) got it, parsed it, and something didn't go right, or, the web server sent it, and it didn't do the right thing with it. I appreciate the effort to look at this. I'd love to do more, but at the moment, I'm cramming in an hour here and there. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 14:40:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from trauco.colomsat.net.co (trauco.colomsat.net.co [200.13.195.2]) by hub.freebsd.org (Postfix) with ESMTP id 5403837B43C; Mon, 25 Sep 2000 14:40:25 -0700 (PDT) Received: from yahoo.com (200.13.214.89) by trauco.colomsat.net.co (NPlex 4.0.068) id 39CBBB700000D611; Mon, 25 Sep 2000 16:35:07 -0500 Message-ID: <39CFC702.D629C5C8@yahoo.com> Date: Mon, 25 Sep 2000 16:43:30 -0500 From: "Yonny Cardenas B." Organization: Ingenieria Integral Ltda. X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: Can't work out which disk we are booting from References: <200009251929.e8PJT9A13950@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike Of course, I tried with both CD-ROM and floppy, but the problem is the same. Thanks. Mike Smith wrote: > > Booting from CDROM is not (yet) supported on these systems. You will > have to boot from floppy disk (you can install from CDROM OK). > +-------------------------------------------------------------------------+ | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554 | | | 3451565, 2176251 ext. 16 | | Opus Ingenieria | Fax : +57 1 3458343 | | Calle 61 # 5-44 Piso 3 | E-mail: y-carden@uniandes.edu.co | | Santafe de Bogota D.C.,Colombia | ycardena@yahoo.com | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 14:59:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from penfold.transactionsite.com (penfold.transactionsite.com [203.14.245.1]) by hub.freebsd.org (Postfix) with SMTP id 49C8A37B424 for ; Mon, 25 Sep 2000 14:59:49 -0700 (PDT) Received: (qmail 1433 invoked from network); 25 Sep 2000 21:59:40 -0000 Received: from haym.transactionsite.com (HELO haym) (192.168.1.9) by penfold.transactionsite.com with SMTP; 25 Sep 2000 21:59:40 -0000 Message-ID: <00b701c0273b$39f7aaa0$0901a8c0@haym.transactionsite.com> From: "Jan Mikkelsen" To: "Kevin Mills" , "FreeBSD Hackers" Subject: Re: atomic operations Date: Tue, 26 Sep 2000 08:54:48 +1100 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.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Mills wrote: >I found the atomic_* functions in , but noticed that they >have no return value. What I need is a function that increments/decrements >the given value *and* returns the new value in an atomic operation. I >suppose this is possible, yes? How would one modify the assembly to make >this work? Atomic decrement, in the Intel style: long atomic_decrement(volatile long* address) { asm { mov ecx, [address] mov eax, -1 lock xadd [ecx], eax dec eax } /* Return value in EAX */ } An untested conversion into the GNU/AT&T style: long atomic_decrement(volatile long* address) { asm("movl 8(%ebp),%ecx"); asm("movl $-1, %eax"); asm("lock xaddl %eax,(%ecx)"); asm("decl %eax"); /* Return value in %eax */ } Deriving increment is straightforward. I haven't looked at the GNU inline assembler notation for indicating register usage. I'd be curious to see what is should look like. Jan Mikkelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 19:16:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id B773D37B42C for ; Mon, 25 Sep 2000 19:16:38 -0700 (PDT) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id TAA25565 for freebsd-hackers@FreeBSD.ORG; Mon, 25 Sep 2000 19:16:55 -0700 (PDT) (envelope-from joe) From: Joe McGuckin Message-Id: <200009260216.TAA25565@monk.via.net> Date: Mon, 25 Sep 2000 19:16:55 -0700 (PDT) To: freebsd-hackers@FreeBSD.ORG Subject: What's the difference between the ncr0 and sym0 drivers? X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is one preferable? Thanks, Joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 19:53:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id B848937B42C for ; Mon, 25 Sep 2000 19:53:47 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e8Q2rjn04826; Mon, 25 Sep 2000 19:53:46 -0700 (PDT) Date: Mon, 25 Sep 2000 19:53:45 -0700 (PDT) From: Doug White To: Zhiui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Sep 2000, Zhiui Zhang wrote: > > I am wondering whether there is a good reason for not putting FreeBSD in a > DOS extended partition. Good luck booting it. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 21:17:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2A38737B42C for ; Mon, 25 Sep 2000 21:17:17 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA05319; Mon, 25 Sep 2000 22:17:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09300; Mon, 25 Sep 2000 22:17:15 -0600 (MDT) Message-Id: <200009260417.WAA09300@harmony.village.org> To: Joe McGuckin Subject: Re: What's the difference between the ncr0 and sym0 drivers? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 25 Sep 2000 19:16:55 PDT." <200009260216.TAA25565@monk.via.net> References: <200009260216.TAA25565@monk.via.net> Date: Mon, 25 Sep 2000 22:17:15 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009260216.TAA25565@monk.via.net> Joe McGuckin writes: : Is one preferable? sym is generally preferable to ncr. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 25 21:29:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B0AD37B422 for ; Mon, 25 Sep 2000 21:29:11 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA00866; Mon, 25 Sep 2000 21:29:09 -0700 Date: Mon, 25 Sep 2000 21:29:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Joe McGuckin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What's the difference between the ncr0 and sym0 drivers? In-Reply-To: <200009260417.WAA09300@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sym is actively maintained, ncr isn't really. On Mon, 25 Sep 2000, Warner Losh wrote: > In message <200009260216.TAA25565@monk.via.net> Joe McGuckin writes: > : Is one preferable? > > sym is generally preferable to ncr. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 5:55:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by hub.freebsd.org (Postfix) with ESMTP id 9942E37B424 for ; Tue, 26 Sep 2000 05:55:02 -0700 (PDT) Received: from rzstud1.rz.uni-karlsruhe.de (rzstud1.rz.uni-karlsruhe.de [129.13.197.1]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.16 #1) id 13duGC-0000mf-00; Tue, 26 Sep 2000 14:55:00 +0200 Received: from un1i by rzstud1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 13duGE-0006C8-00; Tue, 26 Sep 2000 14:55:02 +0200 From: Philipp Mergenthaler To: roam@orbitel.bg, freebsd-hackers@FreeBSD.ORG Subject: Re: virtual console 'snapshot'? X-Newsgroups: list.freebsd-hackers In-Reply-To: <20000923011753.A15311@ringwraith.office1.bg> User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (HP-UX/B.11.00 (9000/800)) Message-Id: Date: Tue, 26 Sep 2000 14:55:02 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In article <20000923011753.A15311@ringwraith.office1.bg> you wrote: > Is there anything like Linux's /dev/vcs* in FreeBSD? That is, some way > to obtain the complete view of a virtual console - characters, attributes, > everything? I've written a module which implements something like this - for every console, there's a device where you can read that console's content or scrollback buffer (selectable per #define). It's still very crude, though. For example the output routine may need work. (Right now it renders similar to man(1), i.e. "more /dev/ttyvbuf0" shows kernel messages in bold.) Also, it doesn't take a "snapshot" which means that reading a buffer while there's output on that console may give a garbled view. You can find it here: http://www.uni-karlsruhe.de/~un1i/freebsd/misc/ttyvbuf.tgz I've written this on FreeBSD-current but I think it'll also work on 4.x. Maybe it is of some use to you. Bye, Philipp -- http://www.uni-karlsruhe.de/~un1i/ (,.) \\\00 ) \= ) cc_|\_,^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 8:26: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 73D1037B42C for ; Tue, 26 Sep 2000 08:26:05 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id LAA13371; Tue, 26 Sep 2000 11:25:54 -0400 (EDT) Date: Tue, 26 Sep 2000 11:25:35 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@opal To: Doug White Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Sep 2000, Doug White wrote: > On Sat, 23 Sep 2000, Zhiui Zhang wrote: > > > > > I am wondering whether there is a good reason for not putting FreeBSD in a > > DOS extended partition. > > Good luck booting it. Do you mean as long as I can boot it, the kernel itself has no problem with being putting into a DOS extended partition? First of all, it seems to me that there is no way to put FreeBSD in an extended partition without modifying /stand/sysintall. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 8:30:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 7CD1C37B42C for ; Tue, 26 Sep 2000 08:30:47 -0700 (PDT) Received: (qmail 8930 invoked by uid 1001); 26 Sep 2000 15:30:28 -0000 Date: Tue, 26 Sep 2000 18:30:28 +0300 From: Peter Pentchev To: Zhiui Zhang Cc: Doug White , freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition Message-ID: <20000926183028.D2616@ringwraith.office1.bg> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zzhang@cs.binghamton.edu on Tue, Sep 26, 2000 at 11:25:35AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess what Doug meant was (at least as far as I've seen in other postings) the current FreeBSD boot loader does not support booting from extended partitions. G'luck, Peter -- This sentence was in the past tense. On Tue, Sep 26, 2000 at 11:25:35AM -0400, Zhiui Zhang wrote: > On Mon, 25 Sep 2000, Doug White wrote: > > > On Sat, 23 Sep 2000, Zhiui Zhang wrote: > > > > > > > > I am wondering whether there is a good reason for not putting FreeBSD in a > > > DOS extended partition. > > > > Good luck booting it. > > Do you mean as long as I can boot it, the kernel itself has no problem > with being putting into a DOS extended partition? First of all, it seems > to me that there is no way to put FreeBSD in an extended partition without > modifying /stand/sysintall. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 8:39:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sighup.aventail.com (sighup.aventail.com [64.94.142.130]) by hub.freebsd.org (Postfix) with ESMTP id E6C0D37B422 for ; Tue, 26 Sep 2000 08:39:51 -0700 (PDT) Received: from leo.in.aventail.com (leo.in.aventail.com [192.168.1.136]) by sighup.aventail.com (8.11.0/8.11.0) with ESMTP id e8QFdpj05917 for ; Tue, 26 Sep 2000 08:39:51 -0700 (PDT) Received: by leo.in.aventail.com with Internet Mail Service (5.5.2650.21) id ; Tue, 26 Sep 2000 08:38:18 -0700 Message-ID: From: Jack Tavares To: "'freebsd-hackers@freebsd.org'" Subject: SIGCHLD and sigwait Date: Tue, 26 Sep 2000 08:38:33 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG all - I am attempting to use sigwait to wait for SIGCHLD from children of my process The following does not work (assumint that testchild just sleeps and then exits) I never get the signal. on solaris 2.7 to make this work, i have to call signal( SIGCHLD, sigHndlr ). The sigHndlr never gets called cause the sigprocmask blocks it What am I doing wrong? thanks jack -- begin testparent.c ---- #include #include #include #include #include #include int main( int argc, char ** argv ) { sigset_t newmask, oldmask; int signo; sigemptyset( &newmask ); if( sigaddset( &newmask, SIGCHLD ) ) perror( "sigaddset" ); if( sigprocmask( SIG_BLOCK, &newmask, NULL ) ) perror( "pthread_sigmask() error" ); char * argp[1]; argp[0] = NULL; pid_t pid = fork( ); if( pid == 0 ) { if( execv("./testchild", argp ) ) { perror( "execv" ); } } cout << "before sigwait" << endl; if( sigwait( &newmask, &signo ) ) perror( "sigwait error" ); if( signo == SIGCHLD ) cout << "testparent SIGCHLD" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 9:40:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pegasus.freibergnet.de (pegasus.freibergnet.de [194.123.255.9]) by hub.freebsd.org (Postfix) with ESMTP id 6361437B422 for ; Tue, 26 Sep 2000 09:40:32 -0700 (PDT) Received: (from holm@localhost) by pegasus.freibergnet.de (8.9.3/8.9.1) id SAA81419 for freebsd-hackers@freebsd.org; Tue, 26 Sep 2000 18:40:30 +0200 (CEST) (envelope-from holm) Date: Tue, 26 Sep 2000 18:40:30 +0200 From: Holm Tiffe To: freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000926184030.A81012@pegasus.freibergnet.de> Reply-To: holm@freibergnet.de Mail-Followup-To: Holm Tiffe , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Thu, Sep 21, 2000 at 09:37:16AM +0300 Organization: FreibergNet Internet Services X-Phone: +49-3731-781279 X-Fax: +49-3731-781377 X-PGP-fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [..] Sorry, can please anyone explain to me how the setup for etherboot is ? Have I to boot the kernel or the loader ? I have botting an kernel now but it asks nicely for the rootdevice; I've setup dhcpd like explained before in this thread. TIA Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 10:42:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id E605037B422 for ; Tue, 26 Sep 2000 10:42:30 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 26 Sep 2000 17:42:30 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D25F0@erlangen01.atrada.de> From: Alexander Maret To: 'Keith Kemp' Cc: "'freebsd-hackers@freebsd.org'" Subject: AW: Frustration with SCSI system Date: Tue, 26 Sep 2000 19:42:13 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Ursprungliche Nachricht----- > Von: Keith Kemp [mailto:kkemp@nwcr.net] > Gesendet: Freitag, 22. September 2000 00:29 > Cc: freebsd-hackers@FreeBSD.ORG; freebsd-isp@FreeBSD.ORG > Betreff: RE: Frustration with SCSI system > > > On the topic of Vinum, what do you guys do about the / > partion since it > appears that a vinum partion can not be the boot partion. We have a system here with two SCSI disks using vinum RAID1 to mirror them. To ensure that we can boot the system even of a / failure on the first disk. There is copy of the root partition on the second disk, so we can boot the system even if the first hd fails completely. As we don't want to copy the contents of the / partition on the first disk to the second disk on every change we do on it, we also mirror /etc. So there is nothing left on the root partition which changes regulary. Mirroring the /etc partition is a bit tricky, because you need some files at startup. On a 3.3-Stable system the only files you really need until /etc is remounted as a mirrored drive are: defaults/rc.conf rc.conf fstab gettytab login.conf rc ttys This shouldn't have changed until know. As you also want to be able to change these files when you remounted /etc I have hardlinks to these files in an /ETC directory. On the remounted /etc directory softlinks then point to the files in /ETC. In my opinion this is the smartest solution you get with vinum. You only have to copy the contents of the / partition of the first disk to the second disk if you change any of the files listed above or if you install a new kernel/new release of FreeBSD. Sorry for my bad english. Alexander Maret To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 11:38:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 4B4E737B42C for ; Tue, 26 Sep 2000 11:38:49 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13dzcu-0007HY-00; Tue, 26 Sep 2000 18:38:48 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8QIN1601592; Tue, 26 Sep 2000 20:23:01 +0200 (CEST) (envelope-from wkb) Date: Tue, 26 Sep 2000 20:23:01 +0200 From: Wilko Bulte To: Joe McGuckin Cc: freebsd-hackers@freebsd.org Subject: Re: What's the difference between the ncr0 and sym0 drivers? Message-ID: <20000926202301.C1524@freebie.demon.nl> References: <200009260216.TAA25565@monk.via.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009260216.TAA25565@monk.via.net>; from joe@via.net on Mon, Sep 25, 2000 at 07:16:55PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 25, 2000 at 07:16:55PM -0700, Joe McGuckin wrote: > > Is one preferable? sym. Gerard did an excellent job in this driver. Sym is the most activily maintained driver as well. ncr always worked fine for me as well, don't misunderstand, but the future belongs to sym ;-) -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 11:53:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id AA9D237B42C; Tue, 26 Sep 2000 11:53:23 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA62505; Tue, 26 Sep 2000 14:53:22 -0400 (EDT) (envelope-from wollman) Date: Tue, 26 Sep 2000 14:53:22 -0400 (EDT) From: Garrett Wollman Message-Id: <200009261853.OAA62505@khavrinen.lcs.mit.edu> To: developers@freebsd.org Cc: hackers@freebsd.org, stable@freebsd.org Subject: Announcement: Two new FreeBSD-related mailing-lists Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies in advance for the cross-posting. (Hopefully you have a mail system with duplicate suppression.) I've created two new FreeBSD-related mailing-lists which people may wish to subscribe to. FreeBSD's postmaster did not think there would be sufficient interest in these lists to justify their creation on FreeBSD.org, so they will instead live on my machine. (This means that there will be no public archives of the discussion, unless someone else volunteers to create one.) The two lists are and ; subscribe in the usual manner. Here are the info files for both lists: ------------------------------------ The freebsd-print mailing-list is intended for the discussion of print systems and software in the FreeBSD environment. Germane topics would include: - The standard FreeBSD print spooler system, lpr(1)/lpd(8). - Other print spooler systems, such as `rlpr' and `LPRng'. - Related document-management and translation software such as `a2ps', `psutils', and `ghostscript'. - Document-formatting systems such as groff(1) and TeX. - Standards relevant to printing, such as IPP. - Support for foreign printing protocols in FreeBSD using tools like `CAP' and `samba'. This list is maintained and retroactively moderated by Garrett Wollman, wollman@{{FreeBSD,bostonradio,decalcomania}.org,lcs.mit.edu} ------------------------------------ The purpose of the freebsd-standards list is to discuss the impact of various formal and informal standards on the FreeBSD operating system. Discussion will include the new POSIX 1003.1-200x / Single UNIX Specification v3 standards (currently in process), as well as other existing and future standards. This mailing-list specifically excludes discussion of standards for network protocol and APIs; these should take place exclusively on the list instead. This list is maintained and retroactively moderated by Garrett Wollman, wollman@{{FreeBSD,bostonradio,decalcomania}.org,lcs.mit.edu} ------------------------------------ -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-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 12:38:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (Postfix) with ESMTP id EBED137B43C for ; Tue, 26 Sep 2000 12:38:15 -0700 (PDT) Received: from androcles.com (localhost.com [127.0.0.1]) by androcles.com (8.9.3/8.9.3) with ESMTP id MAA29698 for ; Tue, 26 Sep 2000 12:38:10 -0700 (PDT) Message-Id: <200009261938.MAA29698@androcles.com> To: hackers@FreeBSD.ORG Subject: Alpha testers wanted; SHELLINIT/DIRLIST Date: Tue, 26 Sep 2000 12:38:09 -0700 From: "Duane H. Hesser" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a request for alpha testers for SHELLINIT/DIRLIST. SHELLINIT is a shell initialization package intended for use with any shell; DIRLIST is a component of SHELLINIT which implements directory lists. Brief explanations are included below. All inputs are welcome, but for this initial alpha release hackers experienced with one or more shells will most likely be able to cope (which is why I'm asking in this list). In the interest of brevity, you can delete now if you are not interested. If you aren't sure, the descriptions below may help. The preface and introductions to the documentation (http://androcles.com/dist/shellinit/using/) are slightly more forthcoming. The documentation is "complete" but very much a draft. It is included in the distribution tarfile (in postscript and HTML) and is also available separately at the address below. The alpha distribution may be downloaded at http://androcles.com/dist/shellinit/ Description of SHELLINIT: =================================================================== Shellinit is a framework for convenient and extensive customization of your *nix shell and working environment. It supports most common Bourne-style shells which offer function and alias support. Some support is available for csh/tcsh, but this is less well-developed due to the lack of function support in those shells (and the fact that the author has not used those shells for several years). The distribution includes 'basic' initialization files which define the framework and are intended to remain static, and a set of 'private' initialization files which may be customized by each user. The framework provides a means to initialize shell functions, aliases, variables and options, and a simple interface for 'maintaining' or modifying them. It is normally used in conjunction with the DIRLIST function set, although this is not required. The basic framework, once established, allows a user to conveniently: + edit basic or private shell initialization files + define and select shell prompts + establish tty parameters + monitor the current state of the shell (options) + replace the shell with a different shell + manipulate X terminals (size, location, color, etc.) when a shell is found to be running in one. + maintain directory lists (if DIRLIST is installed) The installed framework will _replace_ and enhance your existing shell initialization files (although you may easily include your existing intiializations through the framework). The framework does not attempt, however, to establish or mandate a specific user environment (aside from the framework itself); its primary purpose is in fact to provide a simple, consistent means for users to establish a private, custom working environment. =================================================================== Description of DIRLIST: Directory Lists differ from stacks (e.g. as maintained by csh's pushd/popd) in the following ways: 1. paths are maintained in a fixed order and position in the list, and can thus be referenced by number. 2. entries are unique; a pathname is not added to the list if it is already in the list. 3. multiple, named lists may be maintained. 4. lists may be maintained across logins. 5. directories in the list may be named as shell positional parameters (e.g. cp thisfile $4) 6. lists may be read-only and shared Lists are maintained interactively as shell variables. A simple program, "dirlist" is used via shell functions or aliases to manipulate the lists. The 'cd' command is (by default) aliased to 'dl_chdir' so that any directory change will maintain the current list. You may unalias 'cd', if you like, and alias 'dl_chdir' to something else, using a simple editor interface to the dirlist initialization files. Lists are maintained across logins in files named by the list name. When a list is selected, the list is read from the file into a shell variable. Changes to the list occur as changes to the variable (not the file). By default, interactive changes to a list are saved to the storage file only on command. An 'autosave' directive will turn on automatic saving of all changes to the list (provided that the list is not read-only). Commands are also provided to delete entries from the list, and to edit the list interactively. Of course, there are commands to create lists, and to select the list to use. Lists may be shared, but (ordinarily) updated only by the list owner (interactive changes may be made, but may not be saved, although they may be written to a private list). An alternate "system" list set may be created, which will be read-only to all users. The current distribution supports directory lists in all of the common Bourne-style functions shells (using shell functions). A degenerate form of directory lists is suppported for 'csh' and 'tcsh' (using aliases and sourceable files). CAVEAT: although directory lists were first implemented (and used for many years) in csh, the author abandoned csh when function shells became readily available--the current implementation for (t)csh has been updated a bit specifically for this distribution, but is not well tested. In addition, the absence of function support leaves the 'csh' implementation with fewer features and *much* less error checking. Nonetheless, if you are a diehard (t)csh user, you may find this distribution useful. =================================================================== -------------- Duane H. Hesser dhh@androcles.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 13:10:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front5.grolier.fr (front5.grolier.fr [194.158.96.55]) by hub.freebsd.org (Postfix) with ESMTP id 06CBC37B422 for ; Tue, 26 Sep 2000 13:10:24 -0700 (PDT) Received: from nas26-239.vlt.club-internet.fr (nas26-239.vlt.club-internet.fr [195.36.223.239]) by front5.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA04608; Tue, 26 Sep 2000 22:10:17 +0200 (MET DST) Date: Tue, 26 Sep 2000 20:11:23 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Joe McGuckin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What's the difference between the ncr0 and sym0 drivers? In-Reply-To: <200009260216.TAA25565@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Sep 2000, Joe McGuckin wrote: > Is one preferable? Here's the history: BSD ncr -> Linux ncr53c8xx -> Linux sym53c8xx -> FreeBSD sym The ncr is minimally maintained mainly against O/S changes since the latest real improvement that has been the support of 875/895/896 Ultra chips: - Ultra, Ultra 2 - On-chip RAM These changes came from the Linux ncr53c8xx driver, as I am using both Linux and FreeBSD since 1995. Note that Linux ncr53c8xx is now also minimally maintained. Only `sym53c8xx' and `sym' support phase mismatch handling from SCRIPTS, Ultra3 chips (SYM53C1010), residual calculation, completion queue (rather than walking CCB lists), etc ... (would be too long :) ). Speaking about Linux + FreeBSD + FreeEtc..., my main project at the moment is `sym' for all. Btw, this is not an original strategy. :-) It seems that a new driver is developped from scratch in the NetBSD project. That's a courageous effort. Just the `from scratch' approach has been a bad idea, in my opinion. About the `sym' driver, I try to maintain it up-to-date regarding both O/S features and chips features. It seems extremally stable in practice and is both very fast and scale perfectly with the number of simulatenous IOs, at least in theory :). Just a number: I have measured a bit more that 16000 small IOs per second (512 bytes READs) using a single old SYM53C895 chip, which let me think that theory should match practice here. :) G=E9rard. PS: LSILogic supports actively sym53c8xx and sym drivers development by providing me with controllers, documentations and hardware upgrades. > Thanks, >=20 > Joe >=20 >=20 >=20 > -- >=20 > Joe McGuckin >=20 > ViaNet Communications > 994 San Antonio Road > Palo Alto, CA 94303 >=20 > Phone: 650-969-2203 > Cell: 650-207-0372 > Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 16:32:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web9505.mail.yahoo.com (web9505.mail.yahoo.com [216.136.129.135]) by hub.freebsd.org (Postfix) with SMTP id B8FE237B424 for ; Tue, 26 Sep 2000 16:32:33 -0700 (PDT) Message-ID: <20000926233233.32018.qmail@web9505.mail.yahoo.com> Received: from [64.210.169.72] by web9505.mail.yahoo.com; Tue, 26 Sep 2000 16:32:33 PDT Date: Tue, 26 Sep 2000 16:32:33 -0700 (PDT) From: "j. roughan" Subject: subscribe To: freebsd-hackers@Freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===== jay roughan network super-hero __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 17:20:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 4795737B422 for ; Tue, 26 Sep 2000 17:20:22 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e8R0KFo55449; Tue, 26 Sep 2000 17:20:15 -0700 (PDT) Date: Tue, 26 Sep 2000 17:20:15 -0700 (PDT) From: Doug White To: Zhiui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Sep 2000, Zhiui Zhang wrote: > On Mon, 25 Sep 2000, Doug White wrote: > > > On Sat, 23 Sep 2000, Zhiui Zhang wrote: > > > > > > > > I am wondering whether there is a good reason for not putting FreeBSD in a > > > DOS extended partition. > > > > Good luck booting it. > > Do you mean as long as I can boot it, the kernel itself has no problem > with being putting into a DOS extended partition? Loader(8) can't grok it and the kernel can't mount it as root. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 18:16:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-203.dsl.snfc21.pacbell.net [63.206.89.203]) by hub.freebsd.org (Postfix) with ESMTP id AE85837B424 for ; Tue, 26 Sep 2000 18:16:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8R0QfA02285; Tue, 26 Sep 2000 17:26:43 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009270026.e8R0QfA02285@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug White Cc: Zhiui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition In-reply-to: Your message of "Tue, 26 Sep 2000 17:20:15 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Sep 2000 17:26:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> I am wondering whether there is a good reason for not putting FreeBSD in a >>>> DOS extended partition. >>> >>> Good luck booting it. >> >> Do you mean as long as I can boot it, the kernel itself has no problem >> with being putting into a DOS extended partition? > > Loader(8) can't grok it and the kernel can't mount it as root. Actually, that's not entirely true. The problem with booting is that you cannot mark an extended partition entry as 'active' (without some nasty, nonstandard hacks). If that were possible, it would be trivial to improve the loader to deal with that case. The kernel most certainly can mount an extended partition as root, however. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 26 21:34:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wind.lcs.mit.edu (wind.lcs.mit.edu [18.31.0.82]) by hub.freebsd.org (Postfix) with ESMTP id E631E37B422 for ; Tue, 26 Sep 2000 21:34:37 -0700 (PDT) Received: (from dga@localhost) by wind.lcs.mit.edu (8.10.2/8.10.2) id e8R4Ybn00067; Wed, 27 Sep 2000 00:34:37 -0400 Message-Id: <200009270434.e8R4Ybn00067@wind.lcs.mit.edu> Subject: natd bug with pptp, hack fix, question To: hackers@freeBSD.org Date: Wed, 27 Sep 2000 00:34:36 -0400 (EDT) Cc: dga@lcs.mit.edu From: "David G. Andersen" X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With natd+ipfw, I was setting up a front-end firewall for a client. The firewall has several real IP addresses (we'll call them 10.0.0.1 and 10.0.0.2) and two MS PPTP servers behind it. 10.0.0.1 10.0.0.2 World--------- | firewall | --------- PPTP-1 192.168.1.1 \---- PPTP-2 192.168.1.2 I setup the natd.conf file in the way one would expect: redirect_proto gre 192.168.1.1 10.0.0.1 redirect_port tcp 192.168.1.1:1723 10.0.0.1:1723 redirect_proto gre 192.168.1.2 10.0.0.2 redirect_port tcp 192.168.1.2:1723 10.0.0.2:1723 [With or without the redirect_proto gre; with the -current libalias, I would expect to perhaps not need it] Anyway, to make a long story short, it doesn't work. The first PPTP server is reachable and happy, but the virtual PPTP server on 10.0.0.2 is unreachable. When natd sees the first GRE packet, it calls FindPptpIn(), which then checks: link = FindLinkIn(dst_addr, alias_addr, NO_DEST_PORT, call_id, LINK_PPTP, 1); This check fails, and it falls back to a call to FindOriginalAddress(alias_addr); Two questions: a) I'm not sure about the location of the call to AddLink for for this connection in the PPTP aliasing code, so I couldn't determine the right way to set things up. b) Shouldn't this also check to see if there's a default GRE relay host for this alias address? One issue: I hacked my client's natd program in the interim to AddLink inside FindPptpIn if it doesn't get a returned link, and it works like a charm. However, it's definitely the wrong thing to do and only a temporary solution. The fact that it works, however, suggests that this should be something relatively straightforward for someone with a clue about how libalias works to fix. Anyone? I'm happy to fix it (though my client might not like that. :-), but I'd love a bit of a hint about the right way to address this within the libalias framework before I blunder through making changes that won't be accepted. Thanks! This is using the 4-stable natd and the libalias from -current. -Dave {I'm not on -hackers at the moment, so if you could CC: me on a response, I'd appreciate it}. -- work: dga@lcs.mit.edu me: dga@pobox.com MIT Laboratory for Computer Science http://www.angio.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 1:19:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 8E34E37B422 for ; Wed, 27 Sep 2000 01:18:51 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id LAA37172; Wed, 27 Sep 2000 11:17:48 +0300 (EEST) Date: Wed, 27 Sep 2000 11:17:48 +0300 From: Ruslan Ermilov To: "David G. Andersen" Cc: Erik Salander , hackers@FreeBSD.org Subject: Re: natd bug with pptp, hack fix, question Message-ID: <20000927111748.B34308@sunbay.com> Mail-Followup-To: "David G. Andersen" , Erik Salander , hackers@FreeBSD.org References: <200009270434.e8R4Ybn00067@wind.lcs.mit.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="X1bOJ3K7DJ5YkBrT" X-Mailer: Mutt 1.0i In-Reply-To: <200009270434.e8R4Ybn00067@wind.lcs.mit.edu>; from dga@lcs.mit.edu on Wed, Sep 27, 2000 at 12:34:36AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii On Wed, Sep 27, 2000 at 12:34:36AM -0400, David G. Andersen wrote: > With natd+ipfw, I was setting up a front-end firewall for > a client. The firewall has several real IP addresses > (we'll call them 10.0.0.1 and 10.0.0.2) and two > MS PPTP servers behind it. > > > 10.0.0.1 > 10.0.0.2 > World--------- | firewall | --------- PPTP-1 192.168.1.1 > \---- PPTP-2 192.168.1.2 > > I setup the natd.conf file in the way one would expect: > > redirect_proto gre 192.168.1.1 10.0.0.1 > redirect_port tcp 192.168.1.1:1723 10.0.0.1:1723 > > redirect_proto gre 192.168.1.2 10.0.0.2 > redirect_port tcp 192.168.1.2:1723 10.0.0.2:1723 > > [With or without the redirect_proto gre; with the > -current libalias, I would expect to perhaps not need it] > > Anyway, to make a long story short, it doesn't work. The > first PPTP server is reachable and happy, but the virtual > PPTP server on 10.0.0.2 is unreachable. When natd sees > the first GRE packet, it calls > > FindPptpIn(), which then checks: > > link = FindLinkIn(dst_addr, alias_addr, > NO_DEST_PORT, call_id, > LINK_PPTP, 1); > > This check fails, and it falls back to a call to > FindOriginalAddress(alias_addr); > > Two questions: > > a) I'm not sure about the location of the call to > AddLink for for this connection in the PPTP aliasing > code, so I couldn't determine the right way to set > things up. > > b) Shouldn't this also check to see if there's a default > GRE relay host for this alias address? > > One issue: > > I hacked my client's natd program in the interim to > AddLink inside FindPptpIn if it doesn't get a returned > link, and it works like a charm. However, it's definitely > the wrong thing to do and only a temporary solution. > The fact that it works, however, suggests that this > should be something relatively straightforward for someone > with a clue about how libalias works to fix. > > Anyone? I'm happy to fix it (though my client might > not like that. :-), but I'd love a bit of a hint about > the right way to address this within the libalias framework > before I blunder through making changes that won't be > accepted. > > Thanks! > > This is using the 4-stable natd and the libalias from -current. > > -Dave > > {I'm not on -hackers at the moment, so if you could CC: me on > a response, I'd appreciate it}. > Please try the attached patch. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: alias.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias.c,v retrieving revision 1.24 diff -u -p -r1.24 alias.c --- alias.c 2000/09/01 16:38:53 1.24 +++ alias.c 2000/09/27 08:13:23 @@ -711,13 +711,14 @@ GreAliasIn(struct ip *pip) { u_short call_id; struct alias_link *link; + static struct in_addr null_addr = {INADDR_NONE}; /* Return if proxy-only mode is enabled. */ if (packetAliasMode & PKT_ALIAS_PROXY_ONLY) return (PKT_ALIAS_OK); if (PptpGetCallID(pip, &call_id)) { - if ((link = FindPptpIn(pip->ip_src, pip->ip_dst, call_id)) != NULL) { + if ((link = FindPptpIn(pip->ip_src, pip->ip_dst, null_addr, call_id)) != NULL) { struct in_addr alias_address; struct in_addr original_address; Index: alias_db.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias_db.c,v retrieving revision 1.38 diff -u -p -r1.38 alias_db.c --- alias_db.c 2000/08/31 12:47:57 1.38 +++ alias_db.c 2000/09/27 08:13:24 @@ -1632,6 +1632,7 @@ FindUdpTcpOut(struct in_addr src_addr, struct alias_link * FindPptpIn(struct in_addr dst_addr, struct in_addr alias_addr, + struct in_addr src_addr, u_short call_id) { struct alias_link *link; @@ -1640,12 +1641,9 @@ FindPptpIn(struct in_addr dst_addr, NO_DEST_PORT, call_id, LINK_PPTP, 1); - if (link == NULL && !(packetAliasMode & PKT_ALIAS_DENY_INCOMING)) + if (link == NULL && src_addr.s_addr != INADDR_NONE) { - struct in_addr target_addr; - - target_addr = FindOriginalAddress(alias_addr); - link = AddLink(target_addr, dst_addr, alias_addr, + link = AddLink(src_addr, dst_addr, alias_addr, call_id, NO_DEST_PORT, call_id, LINK_PPTP); } Index: alias_local.h =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias_local.h,v retrieving revision 1.16 diff -u -p -r1.16 alias_local.h --- alias_local.h 2000/07/26 23:15:46 1.16 +++ alias_local.h 2000/09/27 08:13:24 @@ -108,7 +108,7 @@ struct alias_link * FindUdpTcpOut(struct in_addr, struct in_addr, u_short, u_short, u_char); struct alias_link * -FindPptpIn(struct in_addr, struct in_addr, u_short); +FindPptpIn(struct in_addr, struct in_addr, struct in_addr, u_short); struct alias_link * FindPptpOut(struct in_addr, struct in_addr, u_short); Index: alias_pptp.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias_pptp.c,v retrieving revision 1.3 diff -u -p -r1.3 alias_pptp.c --- alias_pptp.c 2000/08/09 11:25:44 1.3 +++ alias_pptp.c 2000/09/27 08:13:24 @@ -243,7 +243,7 @@ AliasHandlePptpIn(struct ip *pip, /* /* Find PPTP link for address and Call ID found in PPTP Control Msg */ pptp_link = FindPptpIn(GetDestAddress(link), GetAliasAddress(link), - *pcall_id); + GetOriginalAddress(link), *pcall_id); if (pptp_link != NULL) { int accumulate = *pcall_id; --X1bOJ3K7DJ5YkBrT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 4:40:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from millennium.stealth.net (millennium.stealth.net [206.252.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 9882937B43C for ; Wed, 27 Sep 2000 04:39:44 -0700 (PDT) Received: by millennium.stealth.net (Postfix, from userid 100) id EEBEA6A6F; Wed, 27 Sep 2000 07:39:38 -0400 (EDT) Delivered-To: digital@stealth.net Received: from mail17.enlist.com (mail17.enlist.com [216.34.53.8]) by millennium.stealth.net (Postfix) with SMTP id C5BB06A6F for ; Wed, 27 Sep 2000 01:15:04 -0400 (EDT) Received: (qmail 14299 invoked by uid 503); 27 Sep 2000 05:14:56 -0000 Date: 27 Sep 2000 05:14:56 -0000 From: "Intel" To: digital@stealth.net Subject: Intel Developer Update Magazine Message-Id: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0nlstbndry9 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0nlstbndry9 Content-Type: text/plain Dear Intel Developer Update Subscriber, News from last month’s Intel(R) Developer Forum Conference continues to emerge. This month’s issue of IDU gives you a closer look. "Intel(R) XScale(tm) Microarchitecture Serves Up Breakthrough I/O" – cover story – Breakthrough I/O performance for networking applications becomes a reality with the announcement of the Intel(R) 80310 I/O processor chipset, the first product with Intel(R) XScale(tm) microarchitecture. http://developer.intel.com/update/contents/ac10001.htm "Remote Access to Pre-Release IA-64 Systems" -- Intel(R) Early Access Services offers software developers cost-free, maintenance-free, high-speed Internet access to fully functional, secure IA-64 systems. http://developer.intel.com/update/contents/sw10001.htm "Accelerating Internet Expansion to Wireless Clients" -- The Intel(R) Personal Internet Client Architecture separates hardware and software design environments so applications can be developed independently, eliminating serial development and speeding time-to-market. http://developer.intel.com/update/contents/ac10002.htm "Deskpro IAPC Design Example" -- Compaq’s Deskpro EN series demonstrates a variety of ways OEMs can use S3 technology to differentiate their products from other platforms. http://developer.intel.com/update/contents/dt10001.htm "Real-Time 1394b Data Transfer for Consumer Electronics" – By choosing the right implementation of IEEE 1394b, manufacturers can achieve maximum throughput for the lowest cost and still provide significant product differentiation. http://developer.intel.com/update/contents/it10001.htm "PXE Manageability Technology for EFI" -- PXE (Preboot Execution Environment) provides standardized remote installation and manageability for enterprise network clients, and now it’s available for EFI (Extended Firmware Interface). http://developer.intel.com/update/contents/it10004.htm For details about ongoing developments, visit Intel Developer Update – your monthly conference between the Conferences. Regards, The Editorial Staff Intel Developer Update Magazine =============================================================================================== Know someone who’d be interested in the information Intel Developer Update provides? Forward them this section. Anyone can receive a free subscription. Benefits include monthly email reminders, alerts on major news from Intel, and more. To subscribe, your colleague can link to our subscription form from here or go through the magazine’s home page at http://developer.intel.com/update. In the left navigation bar, they should click on “Reader Services” then click on "Subscribe Now." If you don’t want to continue receiving Intel Developer Update mailings, send an email to mailto:developer.update@intel.com with "unsubscribe" as subject of the message. *For information regarding Intel Corporation's trademarks and acknowledgments please go to http://developer.intel.com/sites/developer/tradmarx.htm --0nlstbndry9 Content-Type: text/html Intel September Issue

Dear Intel Developer Update Subscriber,

News from last month’s Intel® Developer Forum Conference continues to emerge. This month’s issue of IDU gives you a closer look.

Intel® XScale™ Microarchitecture Serves Up Breakthrough I/O – cover story – Breakthrough I/O performance for networking applications becomes a reality with the announcement of the Intel® 80310 I/O processor chipset, the first product with Intel® XScale™ microarchitecture.
http://developer.intel.com/update/contents/ac10001.htm

Remote Access to Pre-Release IA-64 Systems -- Intel® Early Access Services offers software developers cost-free, maintenance-free, high-speed Internet access to fully functional, secure IA-64 systems.
http://developer.intel.com/update/contents/sw10001.htm

Accelerating Internet Expansion to Wireless Clients -- The Intel® Personal Internet Client Architecture separates hardware and software design environments so applications can be developed independently, eliminating serial development and speeding time-to-market.
http://developer.intel.com/update/contents/ac10002.htm

Deskpro IAPC Design Example -- Compaq’s Deskpro EN series demonstrates a variety of ways OEMs can use S3 technology to differentiate their products from other platforms.
http://developer.intel.com/update/contents/dt10001.htm

Real-Time 1394b Data Transfer for Consumer Electronics –- By choosing the right implementation of IEEE 1394b, manufacturers can achieve maximum throughput for the lowest cost and still provide significant product differentiation.
http://developer.intel.com/update/contents/it10001.htm

PXE Manageability Technology for EFI -- PXE (Preboot Execution Environment) provides standardized remote installation and manageability for enterprise network clients, and now it’s available for EFI (Extended Firmware Interface).
http://developer.intel.com/update/contents/it10004.htm

For details about ongoing developments, visit Intel Developer Update – your monthly conference between the Conferences.

Regards,

The Editorial Staff
Intel Developer Update Magazine

==================================================================================

Know someone who’d be interested in the information Intel Developer Update provides? Forward them this section. Anyone can receive a free subscription. Benefits include monthly email reminders, alerts on major news from Intel, and more. To subscribe, your colleague can link to our subscription form from here or go through the magazine’s home page at http://developer.intel.com/update. In the left navigation bar, they should click on “Reader Services” then click on "Subscribe Now."

If you don’t want to continue receiving Intel Developer Update mailings, send an email to developer.update@intel.com with "unsubscribe" as subject of the message.

*For information regarding Intel Corporation's trademarks and acknowledgments please go to
http://developer.intel.com/sites/developer/tradmarx.htm.

--0nlstbndry9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 7:37:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 1D7D837B423; Wed, 27 Sep 2000 07:37:25 -0700 (PDT) Received: from jade (jade.cs.binghamton.edu [128.226.140.161]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA05578; Wed, 27 Sep 2000 10:37:15 -0400 (EDT) Date: Wed, 27 Sep 2000 10:36:52 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@jade To: Mike Smith Cc: Doug White , freebsd-hackers@FreeBSD.ORG Subject: Re: putting FreeBSD in an extended partition In-Reply-To: <200009270026.e8R0QfA02285@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Sep 2000, Mike Smith wrote: > >>>> I am wondering whether there is a good reason for not putting FreeBSD in a > >>>> DOS extended partition. > >>> > >>> Good luck booting it. > >> > >> Do you mean as long as I can boot it, the kernel itself has no problem > >> with being putting into a DOS extended partition? > > > > Loader(8) can't grok it and the kernel can't mount it as root. > > Actually, that's not entirely true. > > The problem with booting is that you cannot mark an extended partition > entry as 'active' (without some nasty, nonstandard hacks). > > If that were possible, it would be trivial to improve the loader to deal > with that case. The kernel most certainly can mount an extended partition > as root, however. I know this is a minor subject. But Why Linux can be put in an extended partition while FreeBSD cannot? I can not find anywhere (e.g. kern/subr_diskslice.c) in the kernel that prevents this and I know LILO can boot FreeBSD. If it is the problem of booteasy, then we can use other boot loader. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 11:49:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c2-dbn-5.dial-up.net (c2-dbn-5.dial-up.net [196.34.155.133]) by hub.freebsd.org (Postfix) with ESMTP id 312FF37B423; Wed, 27 Sep 2000 11:49:08 -0700 (PDT) Received: (from rnordier@localhost) by c2-dbn-5.dial-up.net (8.8.7/8.6.12) id UAA20084; Wed, 27 Sep 2000 20:48:17 +0200 (SAST) From: Robert Nordier Message-Id: <200009271848.UAA20084@c2-dbn-5.dial-up.net> Subject: Re: putting FreeBSD in an extended partition In-Reply-To: "from Zhiui Zhang at Sep 27, 2000 10:36:52 am" To: Zhiui Zhang Date: Wed, 27 Sep 2000 20:48:14 +0200 (SAST) Cc: Mike Smith , Doug White , freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhiui Zhang wrote: > On Tue, 26 Sep 2000, Mike Smith wrote: > > If that were possible, it would be trivial to improve the loader to deal > > with that case. The kernel most certainly can mount an extended partition > > as root, however. > > I know this is a minor subject. But Why Linux can be put in an extended > partition while FreeBSD cannot? I can not find anywhere (e.g. > kern/subr_diskslice.c) in the kernel that prevents this and I know LILO > can boot FreeBSD. If it is the problem of booteasy, then we can use other > boot loader. The standard bootblocks (ie. boot2) don't support this at present, nor do our tools like fdisk(8) and the equivalent part of sysinstall; so there's a reasonable amount of work needed to make booting from extended partitions a properly-supported feature. I'll most likely be adding this support in the next few months, though. It hasn't been a priority item as there's been little interest till recently. It should be fairly easy to hack boot2 to get this working in your particular case, if you have the time and inclination. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 14:44:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 531D037B422 for ; Wed, 27 Sep 2000 14:44:03 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id RAA20926 for ; Wed, 27 Sep 2000 17:43:55 -0400 (EDT) Date: Wed, 27 Sep 2000 17:43:35 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: system hangs with BUS Reset Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am debugging a program that does a lot of disk I/O and the system hangs briefly with the some repeated messages that looks like: (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x88 (da0:ahc0:0:0:0): BDR message in message buffer (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x89 (da0:ahc0:0:0:0): no longer in timeout, status= 34b ahc0: Issued Channel A Bus Reset. 2SCBs aborted. What should I do now? The following is my dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Tue Sep 26 01:34:11 GMT 2000 root@mercury.cs.binghamton.edu:/usr/src/sys/compile/SUNYFS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 134205440 (131060K bytes) avail memory = 126341120 (123380K bytes) Preloaded elf kernel "kernel" at 0xc0419000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR chip1: port 0xe800-0xe80f at device 4.3 on pci0 ahc0: port 0xd000-0xd0ff mem 0xe3000000-0xe3000fff irq 10 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs dc0: port 0xb800-0xb8ff mem 0xe2800000-0xe28000ff irq 11 at device 10.0 on pci0 dc0: Ethernet address: 00:a0:cc:e4:b7:14 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) WARNING: / was not properly dismounted Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 15:14:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fap.abaid.com (fap.abaid.com [194.242.196.41]) by hub.freebsd.org (Postfix) with ESMTP id F264437B42C for ; Wed, 27 Sep 2000 15:14:34 -0700 (PDT) Received: from wap.sam.com ([212.104.25.194]) by fap.abaid.com (8.11.0/8.11.0) with ESMTP id e8RNGqJ44324; Wed, 27 Sep 2000 23:16:52 GMT Received: from localhost (amutsch@localhost) by wap.sam.com (8.9.3/8.9.3) with ESMTP id AAA02586; Thu, 28 Sep 2000 00:13:32 GMT (envelope-from amutsch@abaid.com) X-Authentication-Warning: wap.sam.com: amutsch owned process doing -bs Date: Thu, 28 Sep 2000 00:13:31 +0000 (GMT) From: Andreas Mutschlechner X-Sender: amutsch@wap.sam.com To: Zhiui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: system hangs with BUS Reset In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, first off, you should ask in freebsd-questions or freebsd-scsi second this is a typical scsi problem. To solve: - check cables - check termination and if the problem still exists, check again. I speak from my own expierence, since I had this kind of problems one year, cos I didn't see that there were two jumpers on the disc to set the termination :-( Greetings Andreas On Wed, 27 Sep 2000, Zhiui Zhang wrote: > > I am debugging a program that does a lot of disk I/O and the system hangs > briefly with the some repeated messages that looks like: > > (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x88 > (da0:ahc0:0:0:0): BDR message in message buffer > (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x89 > (da0:ahc0:0:0:0): no longer in timeout, status= 34b > ahc0: Issued Channel A Bus Reset. 2SCBs aborted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 15:31:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 3D37237B42C for ; Wed, 27 Sep 2000 15:31:49 -0700 (PDT) Received: (qmail 11630 invoked from network); 27 Sep 2000 22:31:48 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 27 Sep 2000 22:31:48 -0000 Date: Wed, 27 Sep 2000 15:31:47 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: hackers@freebsd.org Subject: Anybody know the OS in the Maxtor MAXAttach products? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the comments on the side is: "Caching file system with Soft Update technology". Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. Just curious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 15:51:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 4FFFC37B424 for ; Wed, 27 Sep 2000 15:51:55 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8RMr1A00542; Wed, 27 Sep 2000 15:53:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009272253.e8RMr1A00542@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? In-reply-to: Your message of "Wed, 27 Sep 2000 15:31:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Sep 2000 15:53:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. Last time I looked (a while back) they were using a patched-up FreeBSD 3.x variant. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 16:12:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A813937B422 for ; Wed, 27 Sep 2000 16:12:19 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8RNC8U87061; Wed, 27 Sep 2000 16:12:08 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? In-Reply-To: Message from Jaye Mathisen of "Wed, 27 Sep 2000 15:31:47 PDT." Date: Wed, 27 Sep 2000 16:12:08 -0700 Message-ID: <87058.970096328@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. It is. This product is based on FreeBSD 3.2 if I'm not mistaken. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 16:21:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8DE6637B424 for ; Wed, 27 Sep 2000 16:21:37 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8RNLYe04250; Wed, 27 Sep 2000 16:21:34 -0700 (PDT) Date: Wed, 27 Sep 2000 16:21:34 -0700 From: Alfred Perlstein To: Jordan Hubbard Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? Message-ID: <20000927162134.H9141@fw.wintelcom.net> References: <87058.970096328@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <87058.970096328@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Wed, Sep 27, 2000 at 04:12:08PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan Hubbard [000927 16:12] wrote: > > > > > > One of the comments on the side is: > > > > "Caching file system with Soft Update technology". > > > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > It is. This product is based on FreeBSD 3.2 if I'm not mistaken. Several other companies are using FreeBSD for thier all-in-one fileserver appliances, afaik Quantum as well. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 16:52:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 93DDC37B424 for ; Wed, 27 Sep 2000 16:52:42 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA07407; Wed, 27 Sep 2000 16:52:34 -0700 Date: Wed, 27 Sep 2000 16:52:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? In-Reply-To: <20000927162134.H9141@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Several other companies are using FreeBSD for thier all-in-one > fileserver appliances, afaik Quantum as well. > Connexus/FasTraak (http://www.traakan.com) uses large chunks of various FreeBSD internals- namely the tcp stack. Their own NFS/SFS-journalling filesystem and driver model. FYI/FYA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 17:39:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.worldwide.lemis.com (asbestos.linuxcare.com.au [203.17.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 3B8DC37B422 for ; Wed, 27 Sep 2000 17:39:42 -0700 (PDT) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.9.3/8.9.3) id LAA11465; Thu, 28 Sep 2000 11:38:52 +1100 (EST) (envelope-from grog) Date: Thu, 28 Sep 2000 11:38:52 +1100 From: Greg Lehey To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? Message-ID: <20000928113852.G11123@sydney.worldwide.lemis.com> References: <87058.970096328@winston.osd.bsdi.com> <20000927162134.H9141@fw.wintelcom.net> <87058.970096328@winston.osd.bsdi.com> <200009272253.e8RMr1A00542@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mrcpu@internetcds.com on Wed, Sep 27, 2000 at 03:31:47PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 27 September 2000 at 15:31:47 -0700, Jaye Mathisen wrote: > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > Just curious. Maxtor have done a storage box with a modified FreeBSD, including Samba in the kernel. I don't know the name, but IIRC it's a small purple box with a couple of IDE boxes. I've heard that, for reasons that don't directly relate to FreeBSD, Maxtor isn't overly happy with the results, and that the next generation box probably won't run FreeBSD. There has even been talk that it'll be running Microsoft instead. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 17:53:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3B58037B423 for ; Wed, 27 Sep 2000 17:53:05 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8S0qo407636; Wed, 27 Sep 2000 17:52:50 -0700 (PDT) Date: Wed, 27 Sep 2000 17:52:50 -0700 From: Alfred Perlstein To: Greg Lehey Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? Message-ID: <20000927175250.A7553@fw.wintelcom.net> References: <87058.970096328@winston.osd.bsdi.com> <20000927162134.H9141@fw.wintelcom.net> <87058.970096328@winston.osd.bsdi.com> <200009272253.e8RMr1A00542@mass.osd.bsdi.com> <20000928113852.G11123@sydney.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000928113852.G11123@sydney.worldwide.lemis.com>; from grog@lemis.com on Thu, Sep 28, 2000 at 11:38:52AM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey [000927 17:40] wrote: > On Wednesday, 27 September 2000 at 15:31:47 -0700, Jaye Mathisen wrote: > > One of the comments on the side is: > > > > "Caching file system with Soft Update technology". > > > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > > > Just curious. > > Maxtor have done a storage box with a modified FreeBSD, including > Samba in the kernel. I don't know the name, but IIRC it's a small > purple box with a couple of IDE boxes. > > I've heard that, for reasons that don't directly relate to FreeBSD, > Maxtor isn't overly happy with the results, and that the next > generation box probably won't run FreeBSD. There has even been talk > that it'll be running Microsoft instead. That's upsetting, is there any reason they haven't tried to contact our developer base to resolve these issues, or is MicroSoft just twisting arms over there? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 27 23:36:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id B8CC937B422; Wed, 27 Sep 2000 23:36:03 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13eXIU-0004TR-00; Thu, 28 Sep 2000 09:35:58 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13eXIS-0000dd-00; Thu, 28 Sep 2000 09:35:56 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: nfs v2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 09:35:56 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, with 4.1: there seems to be a problem with nfs2 mounts to non freebsd hosts: mainly, the special files - eg /dev/null - show up as something like 0 crw-r--r-- 1 root wheel 0, 0x00200002 Sep 28 09:29 /mnt/tmp/null it's ok if the exporting os is freebsd, but so far: netapp, procom, bsdi all show up to freebsd as 0, 0x00200002! btw, the problem is not with ls, loo> date > /mnt/tmp/null /mnt/tmp/null: Device not configured. loo> needless to say, this is screwing up my diskless project. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 0:49:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CE5F637B422; Thu, 28 Sep 2000 00:49:14 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8S7n1817835; Thu, 28 Sep 2000 00:49:01 -0700 (PDT) Date: Thu, 28 Sep 2000 00:49:01 -0700 From: Alfred Perlstein To: Danny Braniss Cc: Paul Saab , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: nfs v2 Message-ID: <20000928004901.J7553@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from danny@cs.huji.ac.il on Thu, Sep 28, 2000 at 09:35:56AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Danny Braniss [000927 23:36] wrote: > hi, > with 4.1: there seems to be a problem with nfs2 mounts to > non freebsd hosts: > mainly, the special files - eg /dev/null - show up as something like > 0 crw-r--r-- 1 root wheel 0, 0x00200002 Sep 28 09:29 /mnt/tmp/null > > it's ok if the exporting os is freebsd, but so far: netapp, procom, bsdi > all show up to freebsd as 0, 0x00200002! btw, the problem is not with ls, > > loo> date > /mnt/tmp/null > /mnt/tmp/null: Device not configured. > loo> > > > needless to say, this is screwing up my diskless project. I'm pretty sure that device major/minor are not same across different systems. I would use an MFS or a vn device created from a FreeBSD UFS over NFS. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 0:55: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 0BDCC37B422; Thu, 28 Sep 2000 00:54:56 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13eYWp-0005f2-00; Thu, 28 Sep 2000 10:54:51 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13eYWn-0000i8-00; Thu, 28 Sep 2000 10:54:49 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Alfred Perlstein Cc: Paul Saab , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: nfs v2 In-reply-to: Your message of Thu, 28 Sep 2000 00:49:01 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 10:54:49 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000928004901.J7553@fw.wintelcom.net>you write: }* Danny Braniss [000927 23:36] wrote: }> hi, }> with 4.1: there seems to be a problem with nfs2 mounts to }> non freebsd hosts: }> mainly, the special files - eg /dev/null - show up as something like }> 0 crw-r--r-- 1 root wheel 0, 0x00200002 Sep 28 09:29 /mnt/tmp/null }> }> it's ok if the exporting os is freebsd, but so far: netapp, procom, bsdi }> all show up to freebsd as 0, 0x00200002! btw, the problem is not with ls, }> }> loo> date > /mnt/tmp/null }> /mnt/tmp/null: Device not configured. }> loo> }> }> }> needless to say, this is screwing up my diskless project. } }I'm pretty sure that device major/minor are not same across different }systems. } }I would use an MFS or a vn device created from a FreeBSD UFS over NFS. } the client is FreeBSD, the mknod was done using FreeBSD, the NFS-server if: is FreeBSD then all is fine. if not: all is 'almost' fine except for the special files. im pretty sure about the almost, since the diskless is 'almost' working as long as /dev/ is not used :-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 2:41: 0 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from gate.atio.co.za (gate.atio.co.za [196.7.70.7]) by hub.freebsd.org (Postfix) with ESMTP id 2FF9237B422 for ; Thu, 28 Sep 2000 02:40:55 -0700 (PDT) Received: (from nobody@localhost) by gate.atio.co.za (8.8.8/8.6.9) id LAA12828 for ; Thu, 28 Sep 2000 11:40:43 +0200 (SAST) Received: by gate.atio.co.za via recvmail id 12667; Thu Sep 28 11:39:36 2000 Message-ID: <21EF5EE45919D111865200805FA61F8A0111DA54@mother.atio.co.za> From: Ivan van der Merwe To: "'freebsd-hackers@freefall.cdrom.com'" Subject: ftp transfers Date: Thu, 28 Sep 2000 11:39:33 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I need to do fequent ftp downloads. I would like to put this in the crontab if possible. In windows you can specify a file containing all the files that you want downloaded. Can I do the same on Unix Thanks Ivan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 2:43: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from roma.axis.se (roma.axis.se [193.13.178.2]) by hub.freebsd.org (Postfix) with ESMTP id 1247137B424 for ; Thu, 28 Sep 2000 02:43:00 -0700 (PDT) Received: from pctobiasa.axis.se (tobiasa@pctobiasa.axis.se [10.13.10.180]) by roma.axis.se (8.9.3/8.9.3) with ESMTP id LAA24407 for ; Thu, 28 Sep 2000 11:37:02 +0200 (MEST) Date: Thu, 28 Sep 2000 11:36:24 +0000 (/etc/localtime) From: Tobias Anderberg To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! (first time poster warning...) I'm porting an Linux application to FreeBSD, and I've stumbled across the dreaded SOCK_PACKET and SIOCGIFHWADDR. From what I understand, the FreeBSD equivaliant of SOCK_PACKET is to use BPF? Do I have to use that for the SIOCG.. call aswell? Any hints would be appreciated! /tobba The two functions in question: int InitSendSocket(char *device_name) { if ((sock_fd = socket(AF_INET, SOCK_PACKET, htons(ETH_P_ALL))) < 0) { perror("Socket call failed:"); exit(-1); } fcntl(sock_fd, F_SETFL, O_NDELAY); sock_addr.sa_family = AF_INET; strcpy(sock_addr.sa_data, device_name); return sock_fd; } void GetLocalEthAddr() { int fd; struct ifreq ifr; if ((fd = socket(AF_INET, SOCK_DGRAM, 0)) == -1) { perror("socket"); exit(1); } strcpy(ifr.ifr_name, device); if (ioctl(fd, SIOCGIFHWADDR, &ifr) < 0) { perror("ioctl"); exit(1); } memcpy(eth_addr_local, ifr.ifr_hwaddr.sa_data, 6); if (db1) printf("Ethernet adress for device %s is %2.2x-%2.2x-%2.2x-%2.2x-%2.2x-%2.2x\n", device, eth_addr_local[0], eth_addr_local[1], eth_addr_local[2], eth_addr_local[3], eth_addr_local[4], eth_addr_local[5]); shutdown(fd, 2); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 3: 4:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by hub.freebsd.org (Postfix) with ESMTP id DEA1F37B422 for ; Thu, 28 Sep 2000 03:04:49 -0700 (PDT) Received: from fbwi.fh-wilhelmshaven.de (rzpc101.rz.fh-wilhelmshaven.de [139.13.25.101]) by mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with ESMTP id MAA00784; Thu, 28 Sep 2000 12:04:21 +0200 (MET DST) Message-ID: <39D317A4.BC013D23@fbwi.fh-wilhelmshaven.de> Date: Thu, 28 Sep 2000 12:04:20 +0200 From: Olaf Hoyer Organization: Fachhochschule Oldenburg / Ostfriesland / Wilhelmshaven X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: de,en MIME-Version: 1.0 To: Alfred Perlstein Cc: Jordan Hubbard , Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Anybody know the OS in the Maxtor MAXAttach products? References: <87058.970096328@winston.osd.bsdi.com> <20000927162134.H9141@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Jordan Hubbard [000927 16:12] wrote: > > > > > > > > > One of the comments on the side is: > > > > > > "Caching file system with Soft Update technology". > > > > > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > > > It is. This product is based on FreeBSD 3.2 if I'm not mistaken. > > Several other companies are using FreeBSD for thier all-in-one > fileserver appliances, afaik Quantum as well. Hi! Yes, Quantum uses a patched BSD in their Snap! Servers. I will get one (Snap 2000/40GB)for promotion issues for a BSD booth at a local Linux fair. They also support those M$/Novell directory services/permissions... Regards Olaf Hoyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 4:17:37 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from gep18-5.nyircatv.broadband.hu (gep18-5.nyircatv.broadband.hu [195.184.160.117]) by hub.freebsd.org (Postfix) with ESMTP id 11BC837B423 for ; Thu, 28 Sep 2000 04:17:31 -0700 (PDT) Received: (from witch@localhost) by gep18-5.nyircatv.broadband.hu (8.11.0/8.11.0) id e8SBFZf14114; Thu, 28 Sep 2000 13:15:35 +0200 (CEST) (envelope-from witch) Date: Thu, 28 Sep 2000 13:15:33 +0200 (CEST) From: Ron Scott Reply-To: Ron Scott To: Ivan van der Merwe Cc: "'freebsd-hackers@freefall.cdrom.com'" Subject: Re: ftp transfers In-Reply-To: <21EF5EE45919D111865200805FA61F8A0111DA54@mother.atio.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Ivan van der Merwe wrote: > Hi > > I need to do fequent ftp downloads. I would like to put > this in the crontab if possible. > In windows you can specify a file containing > all the files that you want downloaded. > > Can I do the same on Unix > Sure, try wget (/usr/ports/ftp/wget). Put all URLs in a text file one/line and execute wget, i.e. wget -i inputfile ftp://.... See wget -h for more useful options. Cheers, -Ron -- UNIX was never designed to keep people from doing stupid things, because that policy would also keep them from doing clever things. (Doug Gwyn) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 5:17:53 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 111BD37B42C for ; Thu, 28 Sep 2000 05:17:49 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id QAA29239; Thu, 28 Sep 2000 16:17:25 +0400 (MSD) Message-Id: <200009281217.QAA29239@aaz.links.ru> Subject: Re: ftp transfers In-Reply-To: from "Ron Scott" at "Sep 28, 0 01:15:33 pm" To: ron.scott@subdimension.com Date: Thu, 28 Sep 2000 16:17:25 +0400 (MSD) Cc: Ivan@atio.co.za, freebsd-hackers@freefall.freebsd.org From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ron Scott writes: > Today Ivan van der Merwe wrote: > > I need to do fequent ftp downloads. I would like to put > > this in the crontab if possible. > > In windows you can specify a file containing > > all the files that you want downloaded. > > > > Can I do the same on Unix > > Sure, try wget (/usr/ports/ftp/wget). > > Put all URLs in a text file one/line and execute wget, > i.e. wget -i inputfile ftp://.... > See wget -h for more useful options. Or put URLs in a file and do cat file | xargs -n 1 fetch -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 6:27:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ellipse.mcs.drexel.edu (ellipse.mcs.drexel.edu [129.25.7.190]) by hub.freebsd.org (Postfix) with ESMTP id 74FA537B422 for ; Thu, 28 Sep 2000 06:27:32 -0700 (PDT) Received: from localhost (cosine@localhost) by ellipse.mcs.drexel.edu (8.11.0/8.9.3) with ESMTP id e8SDKf711257 for ; Thu, 28 Sep 2000 09:20:42 -0400 (EDT) (envelope-from cosine@ellipse.mcs.drexel.edu) Date: Thu, 28 Sep 2000 09:20:40 -0400 (EDT) From: Patrick Alken To: freebsd-hackers@freebsd.org Subject: ptrace question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Below I have provided a sample program to demonstrate the problem I am having. Basically, when I ptrace() an ncurses program (such has ncftp 2.4.3), I cannot do a PT_CONTINUE followed by a PT_STEP normally. To demonstrate, the program gets ncftp ready for ptracing and then calls ptrace() with PT_CONTINUE on it. This works perfectly, and if the program receives a signal, such as a SIGINT from a CTRL-C, I then attempt to use ptrace() with PT_STEP, to single-step the next instruction. This is where it fails. The wait() call after the ptrace(PT_STEP) call does not return until you hit the ENTER key, and I cannot figure out why. The first wait() call after the ptrace(PT_CONTINUE) returns normally, but when I use it after the singlestep call, it will not return normally unless I hit a key. As a side note, if I use ptrace(PT_CONTINUE) a second time (instead of PT_STEP), the wait() call will return normally without having to hit a key. Also, if I run a non-ncurses program through this same procedure, the wait() after the ptrace(PT_STEP) operates normally. I can only reproduce this problem under ncurses programs like ncftp v2.4.3 - but I did use tcgetattr() and tcsetattr() to reset the terminal settings, so I don't know why ncurses would be affecting it. If anyone knows what the problem could be, please let me know! ---- Cut here ---- /* * The goal of this program is to run an ncurses program normally * until a signal is caught, and then try to singlestep one * instruction. It should demonstrate that the wait() call after * the ptrace() singlestep call does not return as it should - * you need to hit the ENTER key for the wait() call to return. * * Compile: gcc -o ptest ptest.c * * Run: ./ptest, hit ^C and you will see that you must hit * a keystroke to get it to continue past the singlestep. */ #include #include #include #include #include #include #include #include /* * Location of an ncurses program (NcFTP v2.x.x) */ char filename[] = "/usr/local/bin/ncftp2"; int main() { int pid; /* child pid */ int waitval; int sig; struct termios SavedAttributes; signal(SIGINT, SIG_IGN); pid = fork(); switch (pid) { case -1: { perror("fork"); break; } /* * Child */ case 0: { /* * Allow parent to trace this child process */ ptrace(PT_TRACE_ME, 0, 0, 0); /* * Execute program to be debugged and cause child to * send a signal to parent, so the parent can switch * to PT_STEP */ execl(filename, filename, NULL); break; } /* * Parent */ default: { /* * Wait for child to stop (execl) */ wait(&waitval); /* save attributes */ tcgetattr(STDIN_FILENO, &SavedAttributes); if (ptrace(PT_CONTINUE, pid, (caddr_t) 1, 0) != 0) perror("ptrace"); wait(&waitval); /* restore attributes */ tcsetattr(STDIN_FILENO, TCSANOW, &SavedAttributes); fprintf(stderr, "\nwaitval1 = %d\n", waitval); if (WIFSTOPPED(waitval)) { sig = WSTOPSIG(waitval); fprintf(stderr, "signal = %d\n", sig); /* * OK, they did the CONTROL-C, now try singlestepping the * next instruction. */ fprintf(stderr, "SINGLESTEPPING - here is where you have to hit ENTER but shouldn't need to\n"); if (ptrace(PT_STEP, pid, (caddr_t) 1, 0) != 0) perror("ptrace"); /* * Here is where you have to hit a key to get wait() to * return??? */ wait(&waitval); tcsetattr(STDIN_FILENO, TCSANOW, &SavedAttributes); fprintf(stderr, "DONE SINGLESTEP, waitval2 = %d\n", waitval); } } } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 6:32:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by hub.freebsd.org (Postfix) with ESMTP id F151437B423 for ; Thu, 28 Sep 2000 06:32:16 -0700 (PDT) Received: from toad.stack.nl (toad.ipv6.stack.nl [3ffe:604:3:9:200:e8ff:fe55:346d]) by mailhost.stack.nl (Postfix) with ESMTP id 0F5FF14F46 for ; Thu, 28 Sep 2000 15:32:16 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 816) id D81A89717; Thu, 28 Sep 2000 15:32:15 +0200 (CEST) Subject: misc freebsd-internal questions. To: freebsd-hackers@freebsd.org Date: Thu, 28 Sep 2000 15:32:15 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000928133215.D81A89717@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (for the development of the Free Pascal compiler port): - Is there a way to easily check FreeBSD version (3.x or 4.x+, because of the different syscallnrs for signal functions) on syscall level? - Can I use the assembler instruction ENTER ? E.g. Linux doesn't allow it, because it would complicate the stack overflow handler? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 6:36:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 8147A37B424 for ; Thu, 28 Sep 2000 06:36:16 -0700 (PDT) Received: (qmail 5222075 invoked from network); 28 Sep 2000 13:36:14 -0000 Received: from r120m89.cybercable.tm.fr (HELO qualys.com) ([195.132.120.89]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 28 Sep 2000 13:36:14 -0000 Message-ID: <39D349C6.A89C9340@qualys.com> Date: Thu, 28 Sep 2000 15:38:15 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marco van de Voort , freebsd-hackers@freebsd.org Subject: Re: misc freebsd-internal questions. References: <20000928133215.D81A89717@toad.stack.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marco van de Voort wrote: > (for the development of the Free Pascal compiler port): > > - Is there a way to easily check FreeBSD version (3.x or 4.x+, because of > the different syscallnrs for signal functions) on syscall level? > Use the sysctl kern.osreldate. > > - Can I use the assembler instruction ENTER ? E.g. Linux doesn't allow it, > because it would complicate the stack overflow handler? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 6:46:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.221.73.131]) by hub.freebsd.org (Postfix) with ESMTP id 87AC137B43E for ; Thu, 28 Sep 2000 06:45:39 -0700 (PDT) Received: from govital.net ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id JAA78860 for ; Thu, 28 Sep 2000 09:38:25 -0400 (EDT) (envelope-from webmaster@govital.net) Message-ID: <39D34AFB.625012F4@govital.net> Date: Thu, 28 Sep 2000 09:43:23 -0400 From: Nathan Vidican X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: something strange about FreeBSD 4.1-STABLE booting? (on an IBM laptop) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone got FreeBSD running, successfully on an IBM ThinkPad A20M, (24U - PII 500/128megs Ram/6Gig HD) ? I have attempted to install twice now, both times have resulted in my having to replace the hardisk with a new one from IBM. Here's what happens: I boot off of the kernel disk (floppy), insert the MFSroot disk (also floppy), everything seems normal. I create a 4gig MSDOS partition, and set it bootable, I then create a FreeBSD partition with the remaining space on the disk. I then told it to use the BootBGR. The install goes fine, (installed over FTP to a local machine; laptop has Intel 'fxp0' PCI ethernet on-board). Everything seems well, then I reboot, and the trouble begins. The system runs it's ram test, scans the floppy, spins the cdrom, then halts. I cannot get into the bios, nor can I boot off of a floppy or bootable cdrom. If I remove the hardrive, then it still hangs, but I can at least get into the bios. The computer store tried replacing the drive with one from another identical machine... works fine, can enter/exit the bios, system boots up fine, (running win98se that is). They then tried putting my drive into another laptop, and it causes the same problem on the other laptop; system halts. The computer store then came to the conclusion that the hardrive was no good, (which is what I told them when I came...before they spent two hours trying to figure it out). It seems almost as if the BIOS maintains something in the MBR of the disk. The system works fine with Win98SE, as it came pre-installed, and it works fine if I use the IBM recovery cd-rom to install Win98SE with. I can't imagine that the machine is incapable of running FreeBSD. I suspect that it may have something to do with the way the system goes into 'hybernation' mode, (wherein it writes it's current status to hardisk, and shuts off; so as to resume operations when turned back on... similar to suspend mode, except that it's automatic when the lid is closed). This might explain why it wouldn't boot from the hardisk, as it may be looking for a 'last-left' image or something; but it doesn't produce any errors, and will not boot from floppy or cdrom either. IBM then sent out a brand new replacement drive. The computer store installed it, and made sure the system booted from a floppy; they did not touch the partitioning on the drive. I took it home, ran the FreeBSD install (again over LAN), and rebooted. Same problem, black-screen; no functions. I called IBM tech support directly this time, and after spending about an hour trying to tell their technician that his solutions, (eg boot of a floppy and run 'diskzap' utility), would not work, they opted for me to send the machine back for them to look at. The machine is currently in the mail somewhere, they should receive it tonight or tomorrow morning. They say there's a 3-5 working day return time, but somehow I doubt that it will come back fixed. Any ideas, comments, suggestions, or otherwise would be greatly appreciated at this point. I don't think it'd be something with FreeBSD, but just in case, should I try to install a different version maybe? (was trying to install FreeBSD 4.1-STABLE-20000924 I believe, or round the 24th's snapshot anyhow). -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 7: 1:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 8F17837B422 for ; Thu, 28 Sep 2000 07:01:33 -0700 (PDT) Received: (qmail 19070 invoked by uid 1001); 28 Sep 2000 14:00:59 -0000 Date: Thu, 28 Sep 2000 17:00:59 +0300 From: Peter Pentchev To: Maxime Henrion Cc: Marco van de Voort , freebsd-hackers@freebsd.org Subject: Re: misc freebsd-internal questions. Message-ID: <20000928170059.C5729@ringwraith.office1.bg> References: <20000928133215.D81A89717@toad.stack.nl> <39D349C6.A89C9340@qualys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39D349C6.A89C9340@qualys.com>; from mux@qualys.com on Thu, Sep 28, 2000 at 03:38:15PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 28, 2000 at 03:38:15PM +0200, Maxime Henrion wrote: > Marco van de Voort wrote: > > > (for the development of the Free Pascal compiler port): > > > > - Is there a way to easily check FreeBSD version (3.x or 4.x+, because of > > the different syscallnrs for signal functions) on syscall level? > > > > Use the sysctl kern.osreldate. If it is for a compile-time check, there's a __FreeBSD_version define in (the kern.osreldate sysctl returns exactly this). If it is a configure- or run-time thing, use the sysctl as Maxime suggested. G'luck, Peter -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 8:58:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.221.73.131]) by hub.freebsd.org (Postfix) with ESMTP id B951437B423 for ; Thu, 28 Sep 2000 08:58:35 -0700 (PDT) Received: from wmptl.com ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id LAA98841 for ; Thu, 28 Sep 2000 11:51:20 -0400 (EDT) (envelope-from webmaster@wmptl.com) Message-ID: <39D36A21.908A5E95@wmptl.com> Date: Thu, 28 Sep 2000 11:56:17 -0400 From: Nathan Vidican X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: something strange about FreeBSD 4.1-STABLE booting? (on an IBM laptop) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone got FreeBSD running, successfully on an IBM ThinkPad A20M, (24U - PII 500/128megs Ram/6Gig HD) ? I have attempted to install twice now, both times have resulted in my having to replace the hardisk with a new one from IBM. Here's what happens: I boot off of the kernel disk (floppy), insert the MFSroot disk (also floppy), everything seems normal. I create a 4gig MSDOS partition, and set it bootable, I then create a FreeBSD partition with the remaining space on the disk. I then told it to use the BootBGR. The install goes fine, (installed over FTP to a local machine; laptop has Intel 'fxp0' PCI ethernet on-board). Everything seems well, then I reboot, and the trouble begins. The system runs it's ram test, scans the floppy, spins the cdrom, then halts. I cannot get into the bios, nor can I boot off of a floppy or bootable cdrom. If I remove the hardrive, then it still hangs, but I can at least get into the bios. The computer store tried replacing the drive with one from another identical machine... works fine, can enter/exit the bios, system boots up fine, (running win98se that is). They then tried putting my drive into another laptop, and it causes the same problem on the other laptop; system halts. The computer store then came to the conclusion that the hardrive was no good, (which is what I told them when I came...before they spent two hours trying to figure it out). It seems almost as if the BIOS maintains something in the MBR of the disk. The system works fine with Win98SE, as it came pre-installed, and it works fine if I use the IBM recovery cd-rom to install Win98SE with. I can't imagine that the machine is incapable of running FreeBSD. I suspect that it may have something to do with the way the system goes into 'hybernation' mode, (wherein it writes it's current status to hardisk, and shuts off; so as to resume operations when turned back on... similar to suspend mode, except that it's automatic when the lid is closed). This might explain why it wouldn't boot from the hardisk, as it may be looking for a 'last-left' image or something; but it doesn't produce any errors, and will not boot from floppy or cdrom either. IBM then sent out a brand new replacement drive. The computer store installed it, and made sure the system booted from a floppy; they did not touch the partitioning on the drive. I took it home, ran the FreeBSD install (again over LAN), and rebooted. Same problem, black-screen; no functions. I called IBM tech support directly this time, and after spending about an hour trying to tell their technician that his solutions, (eg boot of a floppy and run 'diskzap' utility), would not work, they opted for me to send the machine back for them to look at. The machine is currently in the mail somewhere, they should receive it tonight or tomorrow morning. They say there's a 3-5 working day return time, but somehow I doubt that it will come back fixed. Any ideas, comments, suggestions, or otherwise would be greatly appreciated at this point. I don't think it'd be something with FreeBSD, but just in case, should I try to install a different version maybe? (was trying to install FreeBSD 4.1-STABLE-20000924 I believe, or round the 24th's snapshot anyhow). -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 9: 8: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 38D8037B424; Thu, 28 Sep 2000 09:07:48 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8SG7Da29419; Thu, 28 Sep 2000 09:07:13 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma029417; Thu, 28 Sep 2000 09:07:02 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id JAA32255; Thu, 28 Sep 2000 09:07:02 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009281607.JAA32255@bubba.whistle.com> Subject: Re: something strange about FreeBSD 4.1-STABLE booting? (on an IBM laptop) In-Reply-To: <39D36A21.908A5E95@wmptl.com> "from Nathan Vidican at Sep 28, 2000 11:56:17 am" To: Nathan Vidican Date: Thu, 28 Sep 2000 09:07:02 -0700 (PDT) Cc: lebel@lebel.org, freebsd-mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ note: moving this thread to freebsd-mobile ] Nathan Vidican writes: > Has anyone got FreeBSD running, successfully on an IBM ThinkPad A20M, > (24U - PII 500/128megs Ram/6Gig HD) ? I have attempted to install twice > now, both times have resulted in my having to replace the hardisk with a > new one from IBM. Check freebsd-mobile. David Lebel says he's got it working fine.. mine arrives next week :-) But earlier someone else posted with the same problem you had. Not sure what is going on with the boot process. David, did you install FreeBSD's boot0? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 9:30:54 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from hermes.avantgo.com (shadow.avantgo.com [63.251.249.148]) by hub.freebsd.org (Postfix) with ESMTP id 095BC37B43F for ; Thu, 28 Sep 2000 09:30:21 -0700 (PDT) Received: from nayarit.avantgo.com (nayarit.avantgo.com [10.1.30.1]) by hermes.avantgo.com (Postfix) with ESMTP id A3EBAB; Thu, 28 Sep 2000 09:30:20 -0700 (PDT) Received: from nayarit.avantgo.com (localhost.avantgo.com [127.0.0.1]) by nayarit.avantgo.com (Postfix) with ESMTP id 81F14F819; Thu, 28 Sep 2000 09:30:19 -0700 (PDT) X-Mailer: exmh version 2.1.1 10/15/1999 To: Ivan van der Merwe Cc: "'freebsd-hackers@freefall.cdrom.com'" Subject: Re: ftp transfers In-Reply-To: Your message of "Thu, 28 Sep 2000 11:39:33 +0200." <21EF5EE45919D111865200805FA61F8A0111DA54@mother.atio.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 09:30:19 -0700 From: Michael Kiernan Message-Id: <20000928163019.81F14F819@nayarit.avantgo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I need to do fequent ftp downloads. I would like to put > this in the crontab if possible. There is also the "mirror" port in /usr/ports/ftp. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 11:49:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id C48B837B424 for ; Thu, 28 Sep 2000 11:49:38 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13eikR-0000Px-00; Thu, 28 Sep 2000 21:49:35 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13eikP-00016O-00; Thu, 28 Sep 2000 21:49:33 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Guy Harris Cc: guy@netapp.com, freebsd-hackers@freebsd.org Subject: Re: nfs v2 In-reply-to: Your message of Thu, 28 Sep 2000 11:04:30 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 21:49:33 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000928110430.B362@quadrajet.flashcom.com>you write: }I'll have to check on this when I get into work (please reply not only }to my address at home, "gharris@flashcom.net", but also to my work }address, which I'm CCing), but, if I remember correctly, I had to put }some amount of gunk into the NFS V2 implementation on NetApp filers to }handle after mounting -2 on a fbsd box, i deleted the dev directory and MAKDEV all and things are ok now. } } 1) NFS V2 having, as I remember, insufficient bits in the } major/minor device value used when creating special files to } support more than 8 bits of major and 8 bits of minor device; if i remember correctly,i copied the / over to the NetAPP via nfsv3 either tar or dump, and all is ok. it's when it gets mounted v2 (which the diskcless boot does) it's when dev is wrong. } 2) some OSes - Solaris was the one with which we were having } problems, as I remember - requiring those extra bits. i tried solaris 2.6 and it's ok. } }NFS V3 is probably a better idea, if you can use it; we (NetApp) have }supported it for many years, and I suspect most if not all other vendors }of NFS servers do so as well. } and it's the prefered mount here too, the problem is the FreeBSD nfs_root/boot that is booting using V2. im trying to see how to get the boot to it's magic via V3, but that does not fix the problem :-) }Also, could you get a network trace of: } } the creation of the "/dev/null" entry, if it was done over NFS; } } attempts by the FreeBSD box to get the attributes of "/dev/null" } via NFS (e.g., an "ls -l /mnt/tmp/null", from your example); } }and send them to me? if you mena a tcpdump, that will have to wait till the morning (my morning :-) } Thanks, danny PS: out of curosity, what os is NetAPP base on? }(Note to self: } } % ls -l /dev/null } crw-rw-rw- 1 root wheel 2, 2 Sep 28 10:06 /dev/null } }.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 11:54:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 29C3437B423 for ; Thu, 28 Sep 2000 11:54:45 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13eipO-0000Ty-00; Thu, 28 Sep 2000 21:54:42 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13eipM-00016t-00; Thu, 28 Sep 2000 21:54:40 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: void Cc: freebsd-hackers@freebsd.org Subject: Re: nfs v2 In-reply-to: Your message of Thu, 28 Sep 2000 18:47:05 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 21:54:40 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000928184704.A21066@firedrake.org>you write: }Alfred is trying to tell you that the device files are not }NFS-importable because the device major/minor numbers are not the same }across OSs. You need to use a genuine FreeBSD /dev directory, and his }message suggests a couple of mechanisms that you could use to do that on }a diskless workstation. } }-- } Ben } and i thought my second message cleared that up. the os that makes the dev and uses it is FreeBSD, it's the server that if is not freebsd, does not work. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 13:51:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 9622937B42C for ; Thu, 28 Sep 2000 13:51:29 -0700 (PDT) Received: from localhost (1282 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 28 Sep 2000 16:51:27 -0400 (EDT) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 28 Sep 2000 16:51:27 -0400 From: Jim Mercer To: hackers@freebsd.org Subject: stuck on MD5 passwd's, host to revert to DES Message-ID: <20000928165127.L22260@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i installed some systems using the 4.0-RELEASE cd, then cvsup to 4.x-stable and those systems use DES passwds, which is what i want. 4.1-STABLE FreeBSD 4.1-STABLE #0: Thu Sep 14 10:01:02 EDT 2000 then i installed some more systems, using a 4.1-RELEASE cd, then cvsup to 4.x-stable but these systems insist on using MD5 crypts in the passwd file. 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Thu Sep 28 16:45:58 PKT 2000 is this a feature or a bug? how do i get these systems to revert to using DES crypts for the passwd file? (i am not on the hackers list, but generally check the searchable archives on www.freebsd.org. CC's to me directly would be appreciated) -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 13:57:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id C1BAC37B43F for ; Thu, 28 Sep 2000 13:57:28 -0700 (PDT) Received: from localhost (957 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 28 Sep 2000 16:57:27 -0400 (EDT) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 28 Sep 2000 16:57:27 -0400 From: Jim Mercer To: hackers@freebsd.org Subject: /etc/login.conf + passwd_format + new? MD5 default? Message-ID: <20000928165727.M22260@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as per my last message, i discovered that an entry of: :passwd_format=des: in /etc/login.conf will reset the crypts back to DES. note: passwd_format is not documented anywhere close to adequately to inform people of its function. also, is the new default for FreeBSD going to be MD5? if so, a note should be made somewhere. -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 14:27: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx02.netapp.com (mx02.netapp.com [198.95.226.52]) by hub.freebsd.org (Postfix) with ESMTP id 81B4837B424 for ; Thu, 28 Sep 2000 14:26:25 -0700 (PDT) Received: from frejya.corp.netapp.com (frejya.dmz.netapp.com [10.254.253.21]) by mx02.netapp.com (8.11.0/8.11.0/NTAP-1.0) with ESMTP id e8SLPkA07627; Thu, 28 Sep 2000 14:25:47 -0700 (PDT) Received: from tooting.eng.netapp.com (tooting.eng.netapp.com [10.100.4.46]) by frejya.corp.netapp.com (8.11.0/8.11.0/NTAP-1.1) with ESMTP id e8SLPjG22250; Thu, 28 Sep 2000 14:25:46 -0700 (PDT) Received: (from guy@localhost) by tooting.eng.netapp.com (8.8.8+Sun/8.8.8) id OAA25500; Thu, 28 Sep 2000 14:25:45 -0700 (PDT) From: Guy Harris Message-Id: <200009282125.OAA25500@tooting.eng.netapp.com> Subject: Re: nfs v2 In-Reply-To: from Danny Braniss at "Sep 28, 2000 09:49:33 pm" To: Danny Braniss Date: Thu, 28 Sep 2000 14:25:44 -0700 (PDT) Cc: Guy Harris , guy@netapp.com, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME++ PL59 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > } 1) NFS V2 having, as I remember, insufficient bits in the > } major/minor device value used when creating special files to > } support more than 8 bits of major and 8 bits of minor device; > if i remember correctly,i copied the / over to the NetAPP via nfsv3 > either tar or dump, and all is ok. it's when it gets mounted v2 (which the > diskcless boot does) it's when dev is wrong. Originally: UNIX systems had 8-bit major and 8-bit minor devices; NFS V2 had no mechanism for creating special files. Then Sun needed that V2 "mknod" support for NFS-only diskless operation, so they added a hack to V2 wherein a V2 CREATE operation in which the "mode" field of the "attributes" member of the arguments had the upper 4 bits set was treated as an attempt to create a file other than a plain file, and those bits contained a standard UNIX file type, e.g. 0020000 for a character special file; the "size" field of the attributes was to be interpreted as the major/minor device. Later, for SV-style named pipe support, they added an additional hack wherein a character special file create with a size of 0xffffffff meant that it would be an attempt to create a FIFO special file. (That was sufficiently long ago that I forget why passing a file type of 010000, i.e. IFIFO, wasn't the way it was done.) Later, SVR4 extended the major/minor device to 32 bits, with 14 bits of major device and 18 bits of minor device. To handle this over NFS V2, what SunOS 5.5.1's NFS server code, at least, appears to do is: 1) store the major and minor device as 14-bit and 18-bit fields in a 32-bit word; 2) in a V2 CREATE request that attempts to create a character or block special file, check whether any of the upper 16 bits of the 32-bit size field are 1 and: if not, treat the size field as an 8-bit major device and an 8-bit minor device, and store the upper 8 bits as the upper 14 bits of the resulting file's "rdev" and store the lower 8 bits as the lower 18 bits of the resulting file's "rdev"; if so, treat the size field as a 14-bit major device and an 18-bit minor device, and store the field as the resulting file's "rdev"; 3) when constructing V2 attributes of a file, if the major or minor device will both fit in 8 bits, shift the major left by 8 and OR in the minor and stuff the result into the "rdev" field, otherwise shift the major left by 14 and OR in the minor and stuff the result into the "rdev" field. This was, presumably, done to allow both SunOS 4.x (8-bit major, 8-bit minor) and SunOS 5.x (14-bit major, 18-bit minor) systems to work together. Then NFS V3 came along; in V3, there's a MKNOD operation, and it supplies "specdata1" and "specdata2" for character and block special files, which are, on UNIX systems, interpreted as major and minor devices, respectively. For V3, what SunOS 5.5.1 appears to do is: 1) in a V3 CREATE request that attempts to create a character or block special file, combine the "specdata1" and "specdata2" fields as if they were a 14-bit major and 18-bit minor; 2) when constructing V3 attributes for the file, stuff the major into "specdata1" and the minor into "specdata2". What FreeBSD 3.4's client code, at least, does on a "mknod" is: for V2, do a CREATE, pass the appropriate mode bits, and pass the "rdev" value as the size; for V3, do a MNNOD, and pass the major and minor as "specdata1" and "specdata2". The FreeBSD 32-bit major/minor value is 8 bits of major and 24 bits of minor, which isn't the same as SVR4's 14/18. On a "getattr", what FreeBSD 3.4's client code does is: for V2, treat the "rdev" value as a dev_t; for V3, treat "specdata1" as an 8-bit major and "specdata2" as a 24-bit minor, and combine them with "makedev" into an dev_t. NetApp filers originally just, as I remember, stuffed the size field into the 32-bit "rdev" field of our inode on a CREATE operation, and returned it in the "rdev" field of an "fattr" structure on a GETATTR operation. When we added V3 support, on a V2 CREATE we interpreted the "size" field as containing an 8-bit major and an 8-bit minor, and passed those on to the file system as the "specdata1" and "specdata2" values, and passed "specdata1" and "specdata2" from a V3 MKNOD on in the same fashion; the file system then treated them both as 8-bit values, and stuffed them into the "rdev" field of the inode. (At the time, Solaris didn't *support* NFS V3.) On a GETATTR operation, the file system split the "rdev" field into 8-bit "specdata1" and "specdata2" fields, and then: for V2, combined them into an 8-bit+8-bit rdev field in the NFS reply; for V3, returned them as "specdata1" and "specdata2" in the NFS reply. (NOTE: the rdev field occupies the same space as the top-level file block pointers; we don't waste 32 bits of the inode for files that aren't character or block special files - we don't have 32 bits to waste, as we have to stuff various DOS/Windows gunk in there as well, for Windows CIFS clients.) Later, when we had to support diskless Solaris clients using V3: for a V2 create, we just passed the size field on to the file system unchanged as what amounts to a "rdev" value; for a V3 create, we assumed that the client was a 14/18 system, stuffed "specdata1" into the upper 14 bits and "specdata2" into the lower 18 bits, and passed that on to the file as what amounts to an "rdev" value; we stuffed the "rdev" value into the inode's "rdev" field; for V2 GETATTR, we returned the "rdev" field as the "rdev" field; for V3 GETATTR, we checked whether the "rdev" field had the upper 16 bits set, and: if so, we split it into a 14-bit major and an 18-bit minor device, and returned those as "specdata1" and "specdata2"; if not (meaning that either the inode was created by a version of our software that didn't have support for 14/18 device values, or had a major device of 0), we split it into an 8-bit major and an 8-bit minor device, and returned those as "specdata1" and "specdata2". A V2 CREATE from FreeBSD of device (2, 2) looks as if it'd pass (2 << 24) | 2 over the wire, i.e. 0x02000002. We'd stuff 0x02000002 into the inode, and should, in an NFS V2 reply, return it as 0x02000002. It looks as if FreeBSD would handle that. A V3 MKNOD from FreeBSD of device (2, 2) would pass 2 over the wire as "specdata1" and 2 over the wire as "specdata2"; what the server does with that depends on the server: Solaris would, I suspect, turn that into 14 bits of 2 and 18 bits of 2, i.e. 0x00080002; NetApp filers would do the same; an OS with 12-bit majors and 20-bit minors would turn it into 0x00200002; an OS such as FreeBSD with 8-bit majors and 24-bit minors would turn it into 0x02000002. A V2 GETATTR would get back whichever of those the server's OS did, which would not be correctly interpreted unless the server had 8-bit majors and 24-bit minors and thus sent 0x02000002. > } 2) some OSes - Solaris was the one with which we were having > } problems, as I remember - requiring those extra bits. > i tried solaris 2.6 and it's ok. If the major device is non-zero, the size field won't fit in 16 bits, so the SunOS 5.5.1 server will probably misinterpret the size field of a V2 create as being 14/18 rather than 8/24. (If the major device *is* zero, then, at least with a SunOS 5.5 client and SunOS 5.5.1 server, the command mknod foobar c 0 8192 when using V2 created a file with a major device of 32 and a minor device of 0; the upper 16 bits of the size were zero, so the 5.5.1 server assumed that the request was probably coming from a 4.x client.) Perhaps later versions of SunOS 5.x don't do this; are you saying that you tried a Solaris 2.6 server? If so, what happens if you do an "ls -l", *on the Solaris server*, of the FreeBSD client's "/dev/null" file? Does it report "2, 2", or does it report something else? > }NFS V3 is probably a better idea, if you can use it; we (NetApp) have > }supported it for many years, and I suspect most if not all other vendors > }of NFS servers do so as well. > } > and it's the prefered mount here too, the problem is the FreeBSD nfs_root/boot > that is booting using V2. im trying to see how to get the boot to it's magic > via V3, but that does not fix the problem :-) To which problem are you referring? I don't think there *is* a solution to the "create special files using V3, get their attributes using V2" problem other than "only run servers whose OSes use the same major/minor bitfield sizes as your client". One solution to the "special files don't work" problem is "create all the special files using the same version of NFS as will be used to get their attributes", in which case, if you're going to be creating the special files with V3, getting the OS to mount the root file system using V3 *would* fix the problem. > > }Also, could you get a network trace of: > } > } the creation of the "/dev/null" entry, if it was done over NFS; > } > } attempts by the FreeBSD box to get the attributes of "/dev/null" > } via NFS (e.g., an "ls -l /mnt/tmp/null", from your example); > } > }and send them to me? > if you mena a tcpdump, that will have to wait till the morning (my morning :-) Yes, I mean tcpdumps - if you use tcpdump, use "-s 65535", so that tcpdump's annoying default teeny tiny snapshot length of 68 doesn't end up cutting off a lot of the interesting parts of the NFS requests and replies. Also, send me the raw tcpdump captures (i.e., capture with "-w" to a savefile), rather than tcpdump's printed interpretation thereof - I may want to run them through Ethereal or convert them to snoop format and run them through snoop. Do captures for all the servers on which you've tried this, both of the creation of the special files and the attempts to get the attributes. > PS: out of curosity, what os is NetAPP base on? The core kernel is our own; it's a message-passing, non-preemptive, kernel-mode-only, single-address-space, no-demand-paging kernel. The networking stack is 4.4-Lite-derived, with some bits of code from various later BSDs added in, although it's drifted a fair bit from the BSD base (i.e., it's not a no-brainer to move stuff into it from BSD stacks or from it to BSD stacks at this point). A number of the commands are 4.4-Lite-derived as well, although we had to assault them with a chainsaw to get them to run in our single-address-space environment. The NFS server code takes some stuff from 4.4-Lite, but we changed that code a lot. The file system is our own, as is the CIFS server code (no Samba involved), the disk/SCSI/Fibre Channel subsystem, and RAID. Some of the platform support code on x86 originally came from BSD, and the Alpha divide/remainder routine came from NetBSD, but, at this point, most of the platform code is our own, even on x86. I.e., it's based mostly on our code, with a bunch of BSD stuff, mainly in the networking area, but even that stuff's often been changed a fair bit. It's not running a standard general-purpose OS with an appliance wrapper. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 15:14:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 577F337B43C for ; Thu, 28 Sep 2000 15:13:53 -0700 (PDT) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by mailhost.tue.nl (8.11.0/8.11.0) with ESMTP id e8SMDpQ29861 for ; Fri, 29 Sep 2000 00:13:51 +0200 (MDT) Received: from deathstar (n186.dial.tue.nl [131.155.209.185]) by hermes.tue.nl (Postfix) with ESMTP id 3FE222E803 for ; Fri, 29 Sep 2000 00:13:50 +0200 (CEST) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Fri, 29 Sep 2000 00:15:24 +0100 Subject: Re: misc freebsd-internal questions. In-reply-to: <20000928170059.C5729@ringwraith.office1.bg> References: <39D349C6.A89C9340@qualys.com>; from mux@qualys.com on Thu, Sep 28, 2000 at 03:38:15PM +0200 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000928221350.3FE222E803@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If it is for a compile-time check, there's a __FreeBSD_version define in > (the kern.osreldate sysctl returns exactly this). If it is > a configure- or run-time thing, use the sysctl as Maxime suggested. No, it is runtime detection, and maybe it needs to be a very early one, therefore I requested the detection via syscall. (contrary to e.g. running uname or so). Compile time using C headers is totally impossible, since the compiler can't read C headers ;-) The sysctl call is not in the man pages, which had confused me. After Maxime's hint I started searching again, convinced that something called sysctl had to exist on syscall level (in uname and libc sources/headers), and found it The runtime checks would keep both versions binary compatible as it seems. Even weirder is that if I generate binaries on Linux, using our FreeBSD runtime library, the generated binaries run perfectly on FreeBSD (no, no linux compat :-). No crosslinker needed, and the ELF object file writer also works fine (eliminating AS) Well, I hope to implement this tomorrow, and create the port files next week. Thanks to the hackers list for all support! The ENTER part is interesting (since it is slightly tighter and on some processors faster), but not needed directly. Marco van de Voort (MarcoV@Stack.nl or marco@freepascal.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 18:14:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DC43E37B423; Thu, 28 Sep 2000 18:14:08 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA83958; Thu, 28 Sep 2000 18:14:08 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 28 Sep 2000 18:14:07 -0700 (PDT) From: Kris Kennaway To: Jim Mercer Cc: hackers@freebsd.org, Brian Feldman Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: <20000928165127.L22260@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Sep 2000, Jim Mercer wrote: > > i installed some systems using the 4.0-RELEASE cd, then > cvsup to 4.x-stable and those systems use DES passwds, which is what > i want. > > 4.1-STABLE FreeBSD 4.1-STABLE #0: Thu Sep 14 10:01:02 EDT 2000 > > then i installed some more systems, using a 4.1-RELEASE cd, then cvsup > to 4.x-stable but these systems insist on using MD5 crypts in the passwd > file. > > 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Thu Sep 28 16:45:58 PKT 2000 > > is this a feature or a bug? > > how do i get these systems to revert to using DES crypts for the passwd file? Set the value of the passwd_format login capability to "des" in /etc/login.conf. Brian Feldman neglected to document or mention this in the release notes at all, as far as I can tell. No cookie! Please fix this ASAP, Brian. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 18:14:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BBB1837B42C; Thu, 28 Sep 2000 18:14:47 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA84250; Thu, 28 Sep 2000 18:14:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 28 Sep 2000 18:14:47 -0700 (PDT) From: Kris Kennaway To: Jim Mercer Cc: hackers@freebsd.org Subject: Re: /etc/login.conf + passwd_format + new? MD5 default? In-Reply-To: <20000928165727.M22260@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Sep 2000, Jim Mercer wrote: > also, is the new default for FreeBSD going to be MD5? Yes. Only people with special circumstances need DES passwords. > if so, a note should be made somewhere. Indeed. See my previous message. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 19:29: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 6844F37B422 for ; Thu, 28 Sep 2000 19:29:01 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id WAA13756 for ; Thu, 28 Sep 2000 22:31:20 -0400 Date: Thu, 28 Sep 2000 22:31:20 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: writing to disk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the quickest way of writing large amounts of data to disk? For example, if using the character device driver to write directly to a disk, is filling a track quicker than filling the same sector on each platter (ie the same column of sectors in a cylinger)? If filling a track is quicker, is a certain pattern preferable over another: skip: 1, 6, 2, 7, 3, 8, 4, 9, 5 sequential: 1, 2, 3, 4, 5, 6, 7, 8, 9 Or perhaps could another method be devised using somekind of clever storing algorithm... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 20:33:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 3AEA037B50E; Thu, 28 Sep 2000 20:33:28 -0700 (PDT) Received: from localhost (1716 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 28 Sep 2000 23:33:26 -0400 (EDT) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Thu, 28 Sep 2000 23:33:26 -0400 From: Jim Mercer To: Kris Kennaway Cc: hackers@freebsd.org, Brian Feldman Subject: Re: stuck on MD5 passwd's, host to revert to DES Message-ID: <20000928233326.N22260@reptiles.org> References: <20000928165127.L22260@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Thu, Sep 28, 2000 at 06:14:07PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 28, 2000 at 06:14:07PM -0700, Kris Kennaway wrote: > Set the value of the passwd_format login capability to "des" in > /etc/login.conf. > > Brian Feldman neglected to document or mention this in the release notes > at all, as far as I can tell. No cookie! Please fix this ASAP, Brian. so, is the intention to have FreeBSD default to md5? or will there be a modification to move things back to des? the reason i ask, is that if people cvsup without seeing or noticing this, they may not realize until too late that the new passwords are md5. anyone using nis with non-freebsd systems might get really upset. especially if they end up chasing around trying to figure out what they "broke" to change the behaviour. -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 21: 1: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 853C037B422; Thu, 28 Sep 2000 21:01:03 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA63757; Thu, 28 Sep 2000 21:01:03 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 28 Sep 2000 21:01:03 -0700 (PDT) From: Kris Kennaway To: Jim Mercer Cc: hackers@freebsd.org, Brian Feldman Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: <20000928233326.N22260@reptiles.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Sep 2000, Jim Mercer wrote: > On Thu, Sep 28, 2000 at 06:14:07PM -0700, Kris Kennaway wrote: > > Set the value of the passwd_format login capability to "des" in > > /etc/login.conf. > > > > Brian Feldman neglected to document or mention this in the release notes > > at all, as far as I can tell. No cookie! Please fix this ASAP, Brian. > > so, is the intention to have FreeBSD default to md5? Yes. It's the more secure alternative and is quite suitable for most users. All the rest of you need to do is add the 'des' login capability in the default class. > the reason i ask, is that if people cvsup without seeing or noticing this, > they may not realize until too late that the new passwords are md5. > > anyone using nis with non-freebsd systems might get really upset. It should have been documented. It still can be :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 28 21:27: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from germanium.xtalwind.net (xtal1.xtalwind.net [205.160.242.52]) by hub.freebsd.org (Postfix) with ESMTP id 09BF737B422 for ; Thu, 28 Sep 2000 21:27:04 -0700 (PDT) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.0/8.11.0) with ESMTP id e8T4Que35064 for ; Fri, 29 Sep 2000 00:26:57 -0400 (EDT) Date: Fri, 29 Sep 2000 00:26:56 -0400 (EDT) From: jack To: hackers@FreeBSD.ORG Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 28 Kris Kennaway wrote: > On Thu, 28 Sep 2000, Jim Mercer wrote: > > > the reason i ask, is that if people cvsup without seeing or noticing this, > > they may not realize until too late that the new passwords are md5. > > > > anyone using nis with non-freebsd systems might get really upset. > > It should have been documented. It still can be :-) A change of this magnitude to default system behavior should have been preceded by a HEADS UP to the stable list, IMO. Would have save me several hours of aggravation. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 0:39: 2 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 69A8637B42C for ; Fri, 29 Sep 2000 00:38:54 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13euuS-0000Ck-00; Fri, 29 Sep 2000 01:48:44 -0600 Message-ID: <39D4495C.94354DE3@softweyr.com> Date: Fri, 29 Sep 2000 01:48:44 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ivan van der Merwe Cc: "'freebsd-hackers@freefall.cdrom.com'" Subject: Re: ftp transfers References: <21EF5EE45919D111865200805FA61F8A0111DA54@mother.atio.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ivan van der Merwe wrote: > > Hi > > I need to do fequent ftp downloads. I would like to put > this in the crontab if possible. > In windows you can specify a file containing > all the files that you want downloaded. > > Can I do the same on Unix Of course you can: ftp some.server.com << EOF username password cd /some/directory get file1 get file2 EOF This is called a 'here is' document. But really it's much easier to just use fetch. See the fetch(1) man page. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 0:48:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 64E5137B43F for ; Fri, 29 Sep 2000 00:47:43 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13eutC-0002MH-00; Fri, 29 Sep 2000 10:47:26 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13eutA-0001Z0-00; Fri, 29 Sep 2000 10:47:24 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Guy Harris Cc: Guy Harris , freebsd-hackers@freebsd.org Subject: Re: nfs v2 In-reply-to: Your message of Thu, 28 Sep 2000 14:25:44 -0700 (PDT) . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Sep 2000 10:47:24 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wow! your message was educational and refreshing. somebody actualy knows! i will keep it for reference. as to your requests: since from all my experiments i've poluted too many file systems, i will start from scratch and send you a full report asap. basicaly, if i understand your explanation, i will always have problems with mknod and v2/v3. so i see only one solution: only use v3 for nfs-root clients, correct? (i mean v3, since mount and automounters alike, unless specificaly requesting v2, will default to v3). danny Daniel Braniss e-mail: danny@cs.huji.ac.il Manager of Computing Facilities phone: +972 2 658 4385 School of Computer Science and Engineering Fax: +972 2 561 7723 The Hebrew University Jerusalem Edmond Safra Campus, Givat Ram, Israel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 10:45:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id B5B7A37B422; Fri, 29 Sep 2000 10:45:26 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id NAA16331; Fri, 29 Sep 2000 13:47:47 -0400 Date: Fri, 29 Sep 2000 13:47:47 -0400 (EDT) From: Marc Tardif To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: kld/cdev won't compile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently running 4.1-RELEASE and can't compile the code in: /usr/share/examples/kld/cdev/module The command "make" returns the following to stderr: cdevmod.c:142: macro `DEV_MODULE' used with too many (6) args cdevmod.c:84: `nostop' undeclared here (not in a function) cdevmod.c:84: initializer element is not constant cdevmod.c:84: (near initialization for `my_devsw.d_poll') cdevmod.c:85: `noreset' undeclared here (not in a function) cdevmod.c:85: initializer element is not constant cdevmod.c:85: (near initialization for `my_devsw.d_mmap') cdevmod.c:86: `nodevtotty' undeclared here (not in a function) cdevmod.c:86: initializer element is not constant cdevmod.c:86: (near initialization for `my_devsw.d_strategy') cdevmod.c:87: warning: initialization from incompatible pointer type cdevmod.c:88: warning: initialization makes integer from pointer without a cast cdevmod.c:89: warning: initialization from incompatible pointer type cdevmod.c:90: warning: initialization from incompatible pointer type cdevmod.c:91: `noparms' undeclared here (not in a function) cdevmod.c:91: initializer element is not constant cdevmod.c:91: (near initialization for `my_devsw.d_flags') cdevmod.c:93: warning: excess elements in struct initializer cdevmod.c:93: warning: (near initialization for `my_devsw') cdevmod.c:94: warning: excess elements in struct initializer cdevmod.c:94: warning: (near initialization for `my_devsw') cdevmod.c:95: warning: excess elements in struct initializer cdevmod.c:95: warning: (near initialization for `my_devsw') cdevmod.c:96: warning: excess elements in struct initializer cdevmod.c:96: warning: (near initialization for `my_devsw') cdevmod.c:98: warning: excess elements in struct initializer cdevmod.c:98: warning: (near initialization for `my_devsw') cdevmod.c:142: warning: initialization makes pointer from integer without a cast cdevmod.c:142: warning: initialization makes pointer from integer without a cast cdevmod.c:78: warning: `my_devsw' defined but not used cdevmod.c:113: warning: `cdev_load' defined but not used Also, "grep include cdevmod.c" returns: #include #include #include #include #include #include "cdev.h" but none of those include files contain "nostop", "noreset", etc. As for DEV_MODULES, the code in /usr/src/sys only uses 3 args, so I'm stumped on that one. Suggestions to solve these problems would be most appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 12:41:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 29A3637B651; Fri, 29 Sep 2000 12:41:24 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.9.3/8.9.3) with SMTP id PAA26543; Fri, 29 Sep 2000 15:29:54 -0400 (EDT) (envelope-from arr@watson.org) Date: Fri, 29 Sep 2000 15:29:54 -0400 (EDT) From: "Andrew R. Reiter" To: Marc Tardif Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: kld/cdev won't compile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc, Yes... This is known. I know I sent in a send-pr awhile back.. but it's not a big priority, in my opinion. HOWEVER, you can see working examples and a tutorial at: http://www.subterrain.net/~awr/KLD-Tutorial/intro.html This will also be in daemonnews on the 1st. Andrew On Fri, 29 Sep 2000, Marc Tardif wrote: > I'm currently running 4.1-RELEASE and can't compile the code in: > /usr/share/examples/kld/cdev/module > > The command "make" returns the following to stderr: > cdevmod.c:142: macro `DEV_MODULE' used with too many (6) args > cdevmod.c:84: `nostop' undeclared here (not in a function) > cdevmod.c:84: initializer element is not constant > cdevmod.c:84: (near initialization for `my_devsw.d_poll') > cdevmod.c:85: `noreset' undeclared here (not in a function) > cdevmod.c:85: initializer element is not constant > cdevmod.c:85: (near initialization for `my_devsw.d_mmap') > cdevmod.c:86: `nodevtotty' undeclared here (not in a function) > cdevmod.c:86: initializer element is not constant > cdevmod.c:86: (near initialization for `my_devsw.d_strategy') > cdevmod.c:87: warning: initialization from incompatible pointer type > cdevmod.c:88: warning: initialization makes integer from pointer without a cast > cdevmod.c:89: warning: initialization from incompatible pointer type > cdevmod.c:90: warning: initialization from incompatible pointer type > cdevmod.c:91: `noparms' undeclared here (not in a function) > cdevmod.c:91: initializer element is not constant > cdevmod.c:91: (near initialization for `my_devsw.d_flags') > cdevmod.c:93: warning: excess elements in struct initializer > cdevmod.c:93: warning: (near initialization for `my_devsw') > cdevmod.c:94: warning: excess elements in struct initializer > cdevmod.c:94: warning: (near initialization for `my_devsw') > cdevmod.c:95: warning: excess elements in struct initializer > cdevmod.c:95: warning: (near initialization for `my_devsw') > cdevmod.c:96: warning: excess elements in struct initializer > cdevmod.c:96: warning: (near initialization for `my_devsw') > cdevmod.c:98: warning: excess elements in struct initializer > cdevmod.c:98: warning: (near initialization for `my_devsw') > cdevmod.c:142: warning: initialization makes pointer from integer without a cast > cdevmod.c:142: warning: initialization makes pointer from integer without a cast > cdevmod.c:78: warning: `my_devsw' defined but not used > cdevmod.c:113: warning: `cdev_load' defined but not used > > Also, "grep include cdevmod.c" returns: > #include > #include > #include > #include > #include > #include "cdev.h" > > but none of those include files contain "nostop", "noreset", etc. > As for DEV_MODULES, the code in /usr/src/sys only uses 3 args, so > I'm stumped on that one. Suggestions to solve these problems > would be most appreciated. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 13:34:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ellipse.mcs.drexel.edu (ellipse.mcs.drexel.edu [129.25.7.190]) by hub.freebsd.org (Postfix) with ESMTP id A42DC37B502 for ; Fri, 29 Sep 2000 13:34:26 -0700 (PDT) Received: from localhost (cosine@localhost) by ellipse.mcs.drexel.edu (8.11.0/8.9.3) with ESMTP id e8TKRUk17596 for ; Fri, 29 Sep 2000 16:27:31 -0400 (EDT) (envelope-from cosine@ellipse.mcs.drexel.edu) Date: Fri, 29 Sep 2000 16:27:30 -0400 (EDT) From: Patrick Alken To: freebsd-hackers@freebsd.org Subject: ptrace question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Below I have provided a sample program to demonstrate the problem I am having. Basically, when I ptrace() an ncurses program (such has ncftp 2.4.3), I cannot do a PT_CONTINUE followed by a PT_STEP normally. To demonstrate, the program gets ncftp ready for ptracing and then calls ptrace() with PT_CONTINUE on it. This works perfectly, and if the program receives a signal, such as a SIGINT from a CTRL-C, I then attempt to use ptrace() with PT_STEP, to single-step the next instruction. This is where it fails. The wait() call after the ptrace(PT_STEP) call does not return until you hit the ENTER key, and I cannot figure out why. The first wait() call after the ptrace(PT_CONTINUE) returns normally, but when I use it after the singlestep call, it will not return normally unless I hit a key. As a side note, if I use ptrace(PT_CONTINUE) a second time (instead of PT_STEP), the wait() call will return normally without having to hit a key. Also, if I run a non-ncurses program through this same procedure, the wait() after the ptrace(PT_STEP) operates normally. I can only reproduce this problem under ncurses programs like ncftp v2.4.3 - but I did use tcgetattr() and tcsetattr() to reset the terminal settings, so I don't know why ncurses would be affecting it. I also tried putting the terminal into "raw" mode right before calling ptrace(PT_CONTINUE), but got the same results, so I'm not sure if this is a raw/cooked mode issue.. If anyone knows what the problem could be, please let me know! ---- Cut here ---- /* * The goal of this program is to run an ncurses program normally * until a signal is caught, and then try to singlestep one * instruction. It should demonstrate that the wait() call after * the ptrace() singlestep call does not return as it should - * you need to hit the ENTER key for the wait() call to return. * * Compile: gcc -o ptest ptest.c * * Run: ./ptest, hit ^C and you will see that you must hit * a keystroke to get it to continue past the singlestep. */ #include #include #include #include #include #include #include #include /* * Location of an ncurses program (NcFTP v2.x.x) */ char filename[] = "/usr/local/bin/ncftp2"; int main() { int pid; /* child pid */ int waitval; int sig; struct termios SavedAttributes; signal(SIGINT, SIG_IGN); pid = fork(); switch (pid) { case -1: { perror("fork"); break; } /* * Child */ case 0: { /* * Allow parent to trace this child process */ ptrace(PT_TRACE_ME, 0, 0, 0); /* * Execute program to be debugged and cause child to * send a signal to parent, so the parent can switch * to PT_STEP */ execl(filename, filename, NULL); break; } /* * Parent */ default: { /* * Wait for child to stop (execl) */ wait(&waitval); /* save attributes */ tcgetattr(STDIN_FILENO, &SavedAttributes); if (ptrace(PT_CONTINUE, pid, (caddr_t) 1, 0) != 0) perror("ptrace"); wait(&waitval); /* restore attributes */ tcsetattr(STDIN_FILENO, TCSANOW, &SavedAttributes); fprintf(stderr, "\nwaitval1 = %d\n", waitval); if (WIFSTOPPED(waitval)) { sig = WSTOPSIG(waitval); fprintf(stderr, "signal = %d\n", sig); /* * OK, they did the CONTROL-C, now try singlestepping the * next instruction. */ fprintf(stderr, "SINGLESTEPPING - here is where you have to hit ENTER but shouldn't need to\n"); if (ptrace(PT_STEP, pid, (caddr_t) 1, 0) != 0) perror("ptrace"); /* * Here is where you have to hit a key to get wait() to * return??? */ wait(&waitval); tcsetattr(STDIN_FILENO, TCSANOW, &SavedAttributes); fprintf(stderr, "DONE SINGLESTEP, waitval2 = %d\n", waitval); } } } return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 13:37:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id F2B6137B502 for ; Fri, 29 Sep 2000 13:37:39 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id QAA17775 for ; Fri, 29 Sep 2000 16:39:59 -0400 Date: Fri, 29 Sep 2000 16:39:59 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: finding source to functions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I find the source to specific functions in /usr/src/sys? I tried running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it dumps core because it can't accept so many args. I then tried creating a tags file for each subdirectory like so: for i in /usr/src/sys/ do if test -d $i then cd $i find ./ -type f -print | xargs ctags -w cd .. fi done But that didn't work either. Any suggestions to make browsing the source code easier? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 13:57:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 8882537B503 for ; Fri, 29 Sep 2000 13:57:30 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e8TKvRl24487; Fri, 29 Sep 2000 13:57:27 -0700 (PDT) Date: Fri, 29 Sep 2000 13:57:27 -0700 (PDT) From: Doug White To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: writing to disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Sep 2000, Marc Tardif wrote: > What is the quickest way of writing large amounts of data to disk? Sequentially. Disks run an order of magnitude faster if they have sequential data. Don't get too fancy with the ordering since the disk driver will just reorder it for you. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 14: 2:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (r148m178.cybercable.tm.fr [195.132.148.178]) by hub.freebsd.org (Postfix) with ESMTP id 15CEA37B502 for ; Fri, 29 Sep 2000 14:02:08 -0700 (PDT) Received: from cybercable.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id XAA71211; Fri, 29 Sep 2000 23:01:55 +0200 (CEST) (envelope-from herbelot@cybercable.fr) Message-ID: <39D50343.A70C22D5@cybercable.fr> Date: Fri, 29 Sep 2000 23:01:55 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif wrote: > > How can I find the source to specific functions in /usr/src/sys? I tried > running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it > dumps core because it can't accept so many args. I then tried creating a > tags file for each subdirectory like so: > for i in /usr/src/sys/ > do > if test -d $i > then > cd $i > find ./ -type f -print | xargs ctags -w > cd .. > fi > done > > But that didn't work either. Any suggestions to make browsing the source > code easier? There is glimpse in the ports tree (/usr/ports/textproc/glimpse), which can create a very efficient index for lots of text files (like source files) TfH > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 14:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 3E3FC37B503 for ; Fri, 29 Sep 2000 14:37:48 -0700 (PDT) Received: (from dervish@localhost) by goku.cl.msu.edu (8.11.0/8.11.0) id e8TLbir66737; Fri, 29 Sep 2000 17:37:44 -0400 (EDT) (envelope-from dervish) Date: Fri, 29 Sep 2000 17:37:44 -0400 From: Bush Doctor To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions Message-ID: <20000929173744.A66583@goku.cl.msu.edu> Mail-Followup-To: Marc Tardif , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from intmktg@CAM.ORG on Fri, Sep 29, 2000 at 04:39:59PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Organisation: Information Systems - Michigan State University Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Marc Tardif aka (intmktg@CAM.ORG) said: > How can I find the source to specific functions in /usr/src/sys? I tried > running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it > dumps core because it can't accept so many args. I then tried creating a > tags file for each subdirectory like so: > for i in /usr/src/sys/ > do > if test -d $i > then > cd $i > find ./ -type f -print | xargs ctags -w > cd .. > fi > done > > But that didn't work either. Any suggestions to make browsing the source > code easier? There's also cscope and cbrowser in the ports under /usr/ports/devel ... > > > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 15:19:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8FB2737B66C for ; Fri, 29 Sep 2000 15:19:18 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8TMJGf18738; Fri, 29 Sep 2000 15:19:16 -0700 (PDT) Date: Fri, 29 Sep 2000 15:19:16 -0700 From: Alfred Perlstein To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions Message-ID: <20000929151915.O27736@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from intmktg@CAM.ORG on Fri, Sep 29, 2000 at 04:39:59PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Marc Tardif [000929 13:37] wrote: > How can I find the source to specific functions in /usr/src/sys? I tried > running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it > dumps core because it can't accept so many args. I then tried creating a > tags file for each subdirectory like so: > for i in /usr/src/sys/ > do > if test -d $i > then > cd $i > find ./ -type f -print | xargs ctags -w > cd .. > fi > done > > But that didn't work either. Any suggestions to make browsing the source > code easier? Sorta lame but: cd /usr/src/sys grep ^function */* works for me. of course there's a bunch of stuff in ports/textproc and devel that may also help. cscope and glimpse are nice. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 15:33:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 9EE5537B502 for ; Fri, 29 Sep 2000 15:33:44 -0700 (PDT) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.10.2/8.10.2) with ESMTP id e8TMXJS14274; Fri, 29 Sep 2000 19:33:20 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Fri, 29 Sep 2000 19:33:19 -0300 (BRST) From: Rik van Riel X-Sender: riel@duckman.distro.conectiva To: Doug White Cc: Marc Tardif , freebsd-hackers@FreeBSD.ORG Subject: Re: writing to disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Sep 2000, Doug White wrote: > On Thu, 28 Sep 2000, Marc Tardif wrote: > > > What is the quickest way of writing large amounts of data to disk? > > Sequentially. Disks run an order of magnitude faster if they > have sequential data. Don't get too fancy with the ordering > since the disk driver will just reorder it for you. Also, lots of disks no longer seem to write individual sectors, but instead read/write whole tracks at a time. (and then the whole sector thing becomes moot) regards, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 16:24:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 30D3D37B66D; Fri, 29 Sep 2000 16:24:08 -0700 (PDT) Received: from localhost (z19sdi@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e8TNO5515121; Fri, 29 Sep 2000 19:24:06 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200009292324.e8TNO5515121@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Kris Kennaway Cc: Jim Mercer , hackers@FreeBSD.org, Brian Feldman Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message from Kris Kennaway of "Thu, 28 Sep 2000 21:01:03 PDT." From: "Brian F. Feldman" Date: Fri, 29 Sep 2000 19:24:04 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 28 Sep 2000, Jim Mercer wrote: > > > On Thu, Sep 28, 2000 at 06:14:07PM -0700, Kris Kennaway wrote: > > > Set the value of the passwd_format login capability to "des" in > > > /etc/login.conf. > > > > > > Brian Feldman neglected to document or mention this in the release notes > > > at all, as far as I can tell. No cookie! Please fix this ASAP, Brian. > > I didn't document it in login.conf(5) -- that was an oversight. I'll add that in a bit (soon). I documented it in login_cap(3), so the programmers know about it but not the sysadmins :( > > so, is the intention to have FreeBSD default to md5? > > Yes. It's the more secure alternative and is quite suitable for most > users. All the rest of you need to do is add the 'des' login capability in > the default class. > > > the reason i ask, is that if people cvsup without seeing or noticing this, > > they may not realize until too late that the new passwords are md5. > > > > anyone using nis with non-freebsd systems might get really upset. > > It should have been documented. It still can be :-) Agreed. It will work by default if FreeBSD systems are doing the yppasswdd, otherwise you'll probably get locked out of changing your password (because the remote yppasswdd must verify your old passwd, but then the new password probably won't have the same kinds of checks against it). Actually, you'd probably not be able to log in. This just needs to be documented; a FreeBSD system previously had to be manually set to use the DES libcrypt, but it would default the other way if the "secure" distribution was installed. Now it just needs a different change, and a bit of an easier one. > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 17:31:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id DE69B37B66D; Fri, 29 Sep 2000 17:31:26 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8U0VQv16780; Fri, 29 Sep 2000 17:31:26 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016777; Fri, 29 Sep 2000 17:31:18 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id RAA54873; Fri, 29 Sep 2000 17:31:18 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009300031.RAA54873@bubba.whistle.com> Subject: Driver for Intel 82801AA (ICH) SMBus controller To: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Date: Fri, 29 Sep 2000 17:31:18 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For anyone interested, I've written a first draft of a driver for the SMBus controller in the Intel 82801AA (ICH) chip. Not sure if or how well it works yet, but anyone wanting to play around with it is welcome to do so.. some hacking may be required. ftp://ftp.whistle.com/pub/archie/misc/ichsmb-driver.tgz This is for FreeBSD 4.1 but should work with more recent sources. Also compatible with the 82801AB (ICH0) chip. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 20:16:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id 74B9537B66C for ; Fri, 29 Sep 2000 20:16:46 -0700 (PDT) Received: (cpmta 25222 invoked from network); 29 Sep 2000 20:16:45 -0700 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.87) with SMTP; 29 Sep 2000 20:16:45 -0700 X-Sent: 30 Sep 2000 03:16:45 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id UAA00405; Fri, 29 Sep 2000 20:16:45 -0700 (PDT) (envelope-from gharris) Date: Fri, 29 Sep 2000 20:16:45 -0700 From: Guy Harris To: Danny Braniss Cc: Guy Harris , Guy Harris , freebsd-hackers@freebsd.org Subject: Re: nfs v2 Message-ID: <20000929201645.A365@quadrajet.flashcom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from danny@cs.huji.ac.il on Fri, Sep 29, 2000 at 10:47:24AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 29, 2000 at 10:47:24AM +0300, Danny Braniss wrote: > basicaly, if i understand your explanation, i will always have problems > with mknod and v2/v3. Yes, mknod done with V3 will, unless your server treats special file major/minor device numbers the way FreeBSD does, probably create a special file that FreeBSD won't see as having the right major/minor device number. > so i see only one solution: only use v3 for nfs-root clients, correct? That's probably the only solution that's guaranteed to work; given that FreeBSD's minor device number isn't stored in the lower N bits of the dev_t, I could see a V3 server, when it constructs a dev_t from the major and minor sent over the wire in a V3 MKNOD, overlapping bits from the major and minor device, causing information to be lost. Just in case there are servers that don't do V3, however, I'd try V3 and, if the server rejects the V3 request with PROG_MISMATCH, try V2 (and do a similar fallback with mount). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 29 23:30:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7812737B503; Fri, 29 Sep 2000 23:30:50 -0700 (PDT) Received: from localhost (8wh7f6@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e8U6Ui534066; Sat, 30 Sep 2000 02:30:47 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200009300630.e8U6Ui534066@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: jack Cc: hackers@FreeBSD.org Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message from jack of "Fri, 29 Sep 2000 00:26:56 EDT." From: "Brian F. Feldman" Date: Sat, 30 Sep 2000 02:30:44 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sep 28 Kris Kennaway wrote: > > > On Thu, 28 Sep 2000, Jim Mercer wrote: > > > > > the reason i ask, is that if people cvsup without seeing or noticing this, > > > they may not realize until too late that the new passwords are md5. > > > > > > anyone using nis with non-freebsd systems might get really upset. > > > > It should have been documented. It still can be :-) > > A change of this magnitude to default system behavior should have > been preceded by a HEADS UP to the stable list, IMO. Would have > save me several hours of aggravation. The default has always been one of two, DES or MD5 depending on whether or not you installed DES, so there isn't a change in behavior for most people (or, now that installing the "secure" distribution is really useful, I guess most people who already use it). Yes, I didn't quite document the switch enough; I've fixed that now. It wasn't necessarily easy to find the info in login_cap(3) when compared to login.conf(5). The yp(4) page also describes it. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 7:50:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2A80B37B502 for ; Sat, 30 Sep 2000 07:50:52 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA40690; Sat, 30 Sep 2000 10:49:33 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 30 Sep 2000 10:49:32 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: jack Cc: hackers@FreeBSD.ORG Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Sep 2000, jack wrote: > On Sep 28 Kris Kennaway wrote: > > > On Thu, 28 Sep 2000, Jim Mercer wrote: > > > > > the reason i ask, is that if people cvsup without seeing or noticing this, > > > they may not realize until too late that the new passwords are md5. > > > > > > anyone using nis with non-freebsd systems might get really upset. > > > > It should have been documented. It still can be :-) > > A change of this magnitude to default system behavior should have > been preceded by a HEADS UP to the stable list, IMO. Would have > save me several hours of aggravation. As someone who works in an environment where NIS is widely used with non-FreeBSD systems, I would comment that the current defaults (at least, change in them) are a disaster, especially given that they weren't documented. It was confusing enough before when I had to make sure (by phone, mind you) that people installed the DES support to get NIS to work. Now the defaults have magically switched, and in a way that wasn't documented. Joy. Maybe we should update ERRATA or the release notes for 4.1.1-RELEASE to make sure it's in there, and send out a formal note to -stable and possibly -announce. While I fortunately heard about this here first, I would frankly hate to have spent hours and hours remotely debugging a change that could potentially make it difficult for people to log in, and then propagated MD5 passwords into a DES password environment. The benefit of the old behavior was that, for FreeBSD to work in a mixed environment with NIS, DES had to be installed, meaning that DES would be the default for passwords. This was an implicit effect of allowing portable use of NIS. I wonder if there would be any way to force users of NIS to submit passwords using DES by default? The current framework doesn't seem to support or encourage that in a way that can be "default" and yet safe for normal use. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 9:29:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D11A137B66C; Sat, 30 Sep 2000 09:29:04 -0700 (PDT) Received: from localhost (p2dy1m@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e8UGSx538498; Sat, 30 Sep 2000 12:29:02 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200009301629.e8UGSx538498@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Robert Watson Cc: jack , hackers@FreeBSD.org Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message from Robert Watson of "Sat, 30 Sep 2000 10:49:32 EDT." From: "Brian F. Feldman" Date: Sat, 30 Sep 2000 12:28:58 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 29 Sep 2000, jack wrote: > > > On Sep 28 Kris Kennaway wrote: > > > > > On Thu, 28 Sep 2000, Jim Mercer wrote: > > > > > > > the reason i ask, is that if people cvsup without seeing or noticing this, > > > > they may not realize until too late that the new passwords are md5. > > > > > > > > anyone using nis with non-freebsd systems might get really upset. > > > > > > It should have been documented. It still can be :-) > > > > A change of this magnitude to default system behavior should have > > been preceded by a HEADS UP to the stable list, IMO. Would have > > save me several hours of aggravation. > > As someone who works in an environment where NIS is widely used with > non-FreeBSD systems, I would comment that the current defaults (at least, > change in them) are a disaster, especially given that they weren't > documented. It was confusing enough before when I had to make sure (by > phone, mind you) that people installed the DES support to get NIS to work. > Now the defaults have magically switched, and in a way that wasn't > documented. Joy. Maybe we should update ERRATA or the release notes for > 4.1.1-RELEASE to make sure it's in there, and send out a formal note to > -stable and possibly -announce. While I fortunately heard about this here > first, I would frankly hate to have spent hours and hours remotely > debugging a change that could potentially make it difficult for people to > log in, and then propagated MD5 passwords into a DES password environment. It was documented in login_cap(3). Now it's also documented in login.cap(5) and yp(4). There weren't any complaints about it before, so there was no way to know into the future that people wouldn't know what to do. I think the right thing to do is to update the release notes and send an announcement to -STABLE. > The benefit of the old behavior was that, for FreeBSD to work in a mixed > environment with NIS, DES had to be installed, meaning that DES would be > the default for passwords. This was an implicit effect of allowing > portable use of NIS. I wonder if there would be any way to force users of > NIS to submit passwords using DES by default? The current framework > doesn't seem to support or encourage that in a way that can be "default" > and yet safe for normal use. You had to install DES and _then_ add the +:::::::: line. Now there's one more step. Do you find this unreasonable for more secure defaults? DES passwords work under the assumption that there's just no way to get master.passwd or (for NIS) sniff the wire/add untrusted machines, and are quite trivial to crack, as you know. Other systems still using DES are just about as protected as the first Unix systems that stored only cleartext passwords. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 9:54:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from germanium.xtalwind.net (xtal1.xtalwind.net [205.160.242.52]) by hub.freebsd.org (Postfix) with ESMTP id 54AD737B503; Sat, 30 Sep 2000 09:54:13 -0700 (PDT) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.0/8.11.0) with ESMTP id e8UGsAe24990; Sat, 30 Sep 2000 12:54:10 -0400 (EDT) Date: Sat, 30 Sep 2000 12:54:10 -0400 (EDT) From: jack To: "Brian F. Feldman" Cc: Robert Watson , hackers@FreeBSD.org Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: <200009301629.e8UGSx538498@green.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Brian F. Feldman wrote: > You had to install DES and _then_ add the +:::::::: line. Now there's one > more step. Exactly. Since at least 2.0.5 those needing DES passwords installed DES, and later CRYPTO, and we had them. As you said, `Now there's one more step.' The problem is that nobody bothered to tell us ahead of time about the additional step. I still maintain that this is a change in default system behavior and therefore there should have been a HEADS UP, and it should have been mentioned in RELNOTES.TXT and UPDATING. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 10: 7:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E2B2237B503 for ; Sat, 30 Sep 2000 10:07:18 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA00573 for ; Sat, 30 Sep 2000 13:01:58 GMT (envelope-from dennis@etinc.com) Message-Id: <200009301301.NAA00573@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 30 Sep 2000 13:10:11 -0400 To: hackers@freebsd.org From: Dennis Subject: if_de driver woes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The saga continues. the de driver in 4.1 now doesnt properly detect the media of original SMC BNC cards. Upgrading an old system proved quite an adventure. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 10: 8:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 859D837B502; Sat, 30 Sep 2000 10:08:41 -0700 (PDT) Received: from localhost (1pxq7v@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e8UH8X538741; Sat, 30 Sep 2000 13:08:36 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200009301708.e8UH8X538741@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: jack Cc: "Brian F. Feldman" , Robert Watson , hackers@FreeBSD.org Subject: Re: stuck on MD5 passwd's, host to revert to DES In-Reply-To: Message from jack of "Sat, 30 Sep 2000 12:54:10 EDT." From: "Brian F. Feldman" Date: Sat, 30 Sep 2000 13:08:32 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Today Brian F. Feldman wrote: > > > You had to install DES and _then_ add the +:::::::: line. Now there's one > > more step. > > Exactly. Since at least 2.0.5 those needing DES passwords > installed DES, and later CRYPTO, and we had them. As you said, > `Now there's one more step.' The problem is that nobody bothered > to tell us ahead of time about the additional step. > > I still maintain that this is a change in default system behavior > and therefore there should have been a HEADS UP, and it should > have been mentioned in RELNOTES.TXT and UPDATING. Sorry. There wasn't anyone who both either remembered to and updated RELNOTES.TXT. It's now going to be in the errata as a documentation of the oversight -- which isn't really too bad, since everyone's supposed to read the relnotes and the latest errata, too :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 12:38:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by hub.freebsd.org (Postfix) with ESMTP id 8F78F37B66C for ; Sat, 30 Sep 2000 12:38:21 -0700 (PDT) Received: from earth.execpc.com (rmukerji@earth.execpc.com [169.207.16.1]) by mailgw02.execpc.com (8.9.1) id OAA08897; Sat, 30 Sep 2000 14:38:20 -0500 Received: (from rmukerji@localhost) by earth.execpc.com (8.9.0) id OAA19305; Sat, 30 Sep 2000 14:38:20 -0500 (CDT) Date: Sat, 30 Sep 2000 14:38:20 -0500 From: Arindum Mukerji To: Marc Tardif Cc: freebsd-hackers@freebsd.org Subject: Re: finding source to functions Message-ID: <20000930143820.A18501@earth.execpc.com> Mail-Followup-To: Marc Tardif , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Marc Tardif [000929 15:37]: > How can I find the source to specific functions in /usr/src/sys? I tried > running ctags (find /usr/src/sys/ -type f -print | xargs ctags -w), but it > dumps core because it can't accept so many args. I then tried creating a > tags file for each subdirectory like so: > for i in /usr/src/sys/ > do > if test -d $i > then > cd $i > find ./ -type f -print | xargs ctags -w > cd .. > fi > done > > But that didn't work either. Any suggestions to make browsing the source > code easier? > The ctags utility that comes with vim (http://www.vim.org/) accepts an argument of "-R" for recursive ctag-ing. I find it most useful in indexing my tree. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 18:40:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id E02AC37B502 for ; Sat, 30 Sep 2000 18:40:30 -0700 (PDT) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.0/8.11.0) id e911e3124913; Sat, 30 Sep 2000 21:40:03 -0400 (EDT) (envelope-from magus) To: Arindum Mukerji Cc: Marc Tardif , freebsd-hackers@freebsd.org Subject: Re: finding source to functions References: <20000930143820.A18501@earth.execpc.com> From: Nat Lanza Date: 30 Sep 2000 21:40:03 -0400 In-Reply-To: Arindum Mukerji's message of "Sat, 30 Sep 2000 14:38:20 -0500" Message-ID: Lines: 23 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arindum Mukerji writes: > The ctags utility that comes with vim (http://www.vim.org/) accepts an > argument of "-R" for recursive ctag-ing. I find it most useful in > indexing my tree. I tend to feed my tree to LXR, which has a nice function search, along with a wrapper for glimpse and some reasonable source browsing. I have my own hacked version, but the original code can be found at http://lxr.linux.no. It was written to index the Linux kernel, but works pretty well for the BSD kernel as well. If anyone wants, I could clean up what I have and produce a patch. If you want to take a look, my version is running at http://lxr.pdl.cs.cmu.edu/freebsd/source/. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 20:25:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ganja.nubisci.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id C246637B503 for ; Sat, 30 Sep 2000 20:25:35 -0700 (PDT) Received: (from dervish@localhost) by ganja.nubisci.net (8.11.0/8.11.0) id e913POY01531; Sat, 30 Sep 2000 23:25:24 -0400 (EDT) (envelope-from dervish) Date: Sat, 30 Sep 2000 23:25:24 -0400 From: bush doctor To: Nat Lanza Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions Message-ID: <20000930232524.A549@nubisci.net> Mail-Followup-To: Nat Lanza , freebsd-hackers@FreeBSD.ORG References: <20000930143820.A18501@earth.execpc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from magus@cs.cmu.edu on Sat, Sep 30, 2000 at 09:40:03PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://www.nubisci.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Nat Lanza aka (magus@cs.cmu.edu) said: > Arindum Mukerji writes: > > > The ctags utility that comes with vim (http://www.vim.org/) accepts an > > argument of "-R" for recursive ctag-ing. I find it most useful in > > indexing my tree. > > I tend to feed my tree to LXR, which has a nice function search, along > with a wrapper for glimpse and some reasonable source browsing. I have > my own hacked version, but the original code can be found at > http://lxr.linux.no. It was written to index the Linux kernel, but > works pretty well for the BSD kernel as well. If anyone wants, I could > clean up what I have and produce a patch. > > If you want to take a look, my version is running at > http://lxr.pdl.cs.cmu.edu/freebsd/source/. Nicely done :). I also installed lxr on my box. I also ran global. I found them both to be excellent tools, however I begining to lean towards cscope+cbrowser. The main advantage is that you don't need to have apache running ... > > > --nat > > -- > nat lanza --------------------- research programmer, parallel data lab, cmu scs > magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ > there are no whole truths; all truths are half-truths -- alfred north whitehead > #;^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 20:52:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 46E9A37B502 for ; Sat, 30 Sep 2000 20:52:37 -0700 (PDT) Received: (qmail 86484 invoked by uid 1000); 1 Oct 2000 03:52:36 -0000 Date: Sun, 1 Oct 2000 05:52:36 +0200 From: "Karsten W. Rohrbach" To: Greg Lehey Cc: Esko Petteri Matinsola , Clark Shishido , hackers@FreeBSD.ORG Subject: Re: Vinum RAID-5 performance problem Message-ID: <20001001055235.G83678@rohrbach.de> Reply-To: karsten@rohrbach.de References: <20000909113319.E5876@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000909113319.E5876@wantadilla.lemis.com>; from grog@lemis.com on Sat, Sep 09, 2000 at 11:33:19AM +0930 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey(grog@lemis.com)@Sat, Sep 09, 2000 at 11:33:19AM +0930: [...] > depends on what you're trying to do. But yes, having only two > controllers will halve your RAID-5 write performance. Note also that > with a 256 kB stripe, you'll run into drive contention problems > because all your superblocks will be on the same subdisk. Take a size > like 273 kB, for example. or (now proven fact) grog's first guess to solve my config problems: 511k ;-) which ran like a charm on dang big box (32x18.3gig) greg, you should underline that fact in your docs at a prominent location. i think that using a plex size which is even or too small are the most common configuration mistakes the people do... /k -- > If you think sex is a pain in the ass, try a different position. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 21: 8:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 03EC937B66C for ; Sat, 30 Sep 2000 21:08:43 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9149jh01025; Sat, 30 Sep 2000 21:09:45 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010010409.e9149jh01025@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: karsten@rohrbach.de Cc: Greg Lehey , Esko Petteri Matinsola , Clark Shishido , hackers@FreeBSD.ORG Subject: Re: Vinum RAID-5 performance problem In-reply-to: Your message of "Sun, 01 Oct 2000 05:52:36 +0200." <20001001055235.G83678@rohrbach.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 Sep 2000 21:09:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greg Lehey(grog@lemis.com)@Sat, Sep 09, 2000 at 11:33:19AM +0930: > [...] > > depends on what you're trying to do. But yes, having only two > > controllers will halve your RAID-5 write performance. Note also that > > with a 256 kB stripe, you'll run into drive contention problems > > because all your superblocks will be on the same subdisk. Take a size > > like 273 kB, for example. > or (now proven fact) grog's first guess to solve my config problems: > 511k ;-) which ran like a charm on dang big box (32x18.3gig) > greg, you should underline that fact in your docs at a prominent > location. i think that using a plex size which is even or too small are > the most common configuration mistakes the people do... I should point out (and undermine my position 8) that this is one of the *major* performance advantages that Vinum has over most, if not all hardware RAID controllers - oddball stripe sizes interact much better with FFS than the small-power-of-2 that you're stuck with on a hardware RAID controller. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 30 23: 1:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 56F0D37B502 for ; Sat, 30 Sep 2000 23:01:47 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id CAA17753 for ; Sun, 1 Oct 2000 02:01:57 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 1 Oct 2000 02:01:57 -0400 (EDT) From: Adam To: hackers@freebsd.org Subject: Re: if_de driver woes In-Reply-To: <200009301301.NAA00573@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Sep 2000, Dennis wrote: > >The saga continues. the de driver in 4.1 now doesnt properly detect the >media of original SMC BNC cards. Upgrading an old system proved quite an >adventure. > >db You seem to have forgotten to attach dmesg, pciconf -l, the card model name, description, and symptoms... maybe your mailer ate them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message