From owner-freebsd-hackers Sun Mar 26 4:56:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id 82FC037B6F3 for ; Sun, 26 Mar 2000 04:56:25 -0800 (PST) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.251.71] by wcn4.wcnet.net with ESMTP (SMTPD32-6.00) id A8F818920204; Sun, 26 Mar 2000 06:56:24 -0600 Message-ID: <38DE09AB.FDB7F9B@wcnet.net> Date: Sun, 26 Mar 2000 06:59:23 -0600 From: John Estess X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: suscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 5: 9: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hkis.com (hkis.com [192.41.38.67]) by hub.freebsd.org (Postfix) with ESMTP id 83E6F37B6DC for ; Sun, 26 Mar 2000 05:09:01 -0800 (PST) (envelope-from jason@hkis.com) Received: from hkupc ([203.185.58.151]) by hkis.com (8.8.5) id VAA27199; Sun, 26 Mar 2000 21:09:01 +0800 (HKT) X-Authentication-Warning: hkis.com: Host [203.185.58.151] claimed to be hkupc Message-ID: <38DE0BE7.48F5@hkis.com> Date: Sun, 26 Mar 2000 21:08:55 +0800 From: Jason Chan X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Virtual Machine Setup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear every FreeBSD experts, I was referrred from Joerg Wunsch that some of you may be interested in a project of setting up Virtual Machine on Intel FreeBSD platform. We are a startup web hosting company in Hong Kong and China. We are keen to develop a system which is capable of running multiple Virtual Machine which in turn run a standalone www/ftp/mail server. We aim to acheive the level of service that iServer.com and vservers.com offer. If you are inerested, we would discuss in full details. I would appreciate if you could give a quick reply. Thank you. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 5:54:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 533D637B7BE for ; Sun, 26 Mar 2000 05:54:33 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.224.48]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FS17YU01.N45; Sun, 26 Mar 2000 15:54:30 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id PAA05779; Sun, 26 Mar 2000 15:54:23 +0200 (CEST) (envelope-from asmodai) Date: Sun, 26 Mar 2000 15:54:23 +0200 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: hackers@freebsd.org Subject: Re: Shim Code #error needed Message-ID: <20000326155423.A5771@daemon.ninth-circle.org> References: <200003252043.NAA73526@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003252043.NAA73526@harmony.village.org>; from imp@village.org on Sat, Mar 25, 2000 at 01:43:12PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000326 00:00], Warner Losh (imp@village.org) wrote: > >However, I was thinking that it would be nice if there was something >simple to grep for to see what drivers still needed to be converted. I assume you mean PCI devices, since ISA are detailed in: /src/sys/i386/isa/isa_compat.h -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project The descent to hell is easy... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 7:12: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 6CA2037B911 for ; Sun, 26 Mar 2000 07:11:57 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 6558B24D16; Sun, 26 Mar 2000 10:11:56 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id EAF9A18613; Sun, 26 Mar 2000 10:11:51 -0500 (EST) Date: Sun, 26 Mar 2000 10:11:51 -0500 From: Keith Stevenson To: Jonathan Lemon Cc: justin@apple.com, hackers@freebsd.org Subject: Re: Request for review (HW checksum patches) Message-ID: <20000326101151.A75206@osaka.louisville.edu> References: <200003260056.SAA29089@prism.flugsvamp.com> <20000325212533.B73602@osaka.louisville.edu> <20000325223624.L71371@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000325223624.L71371@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Sat, Mar 25, 2000 at 10:36:24PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 10:36:24PM -0600, Jonathan Lemon wrote: > On Sat, Mar 25, 2000 at 09:25:33PM -0500, Keith Stevenson wrote: > > > > Which card(s) do your patches support? I have a 3Com 3CR990-TX (typhoon) > > which does both TCP checksumming and 3DES (for IPSec). I'd love to give > > it a try. > > Right now, just the Alteon cards. Support for the 3Com-XL can probably > be added without too much trouble. I don't see a driver for the 3Com-990 > though, and I can't find a reference to it on the 3Com website, is > this a new card? I'm not sure whether or not it is generally available yet. I got it as part of an early release preview program. Needless to say, the only drivers that come prepackaged with it are for Win2k. I'll see if I can find anything which resembles documentation in the stuff which came with the card. (I highly doubt that I will.) Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 9: 4:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id BDD9437B809 for ; Sun, 26 Mar 2000 09:04:16 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id LAA02735; Sun, 26 Mar 2000 11:04:08 -0600 (CST) (envelope-from dick) Date: Sun, 26 Mar 2000 11:04:08 -0600 From: "Richard Seaman, Jr." To: Arun Sharma Cc: FreeBSD Hackers Subject: Re: RTLD thread safety Message-ID: <20000326110408.A378@tar.com> References: <20000325225615.A11307@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000325225615.A11307@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Sat, Mar 25, 2000 at 10:56:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 10:56:15PM -0800, Arun Sharma wrote: > When I try to compile a simple multi threaded program using a wrapper > around rfork (from linuxthreads port), I get the following core dump: > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:54 > > Investigation into code reveals that lazy resolution of symbols > (using PLTs) was happening in multiple threads in the linker simultaneously. > > Also, the code in lockdflt.c is achieving mutual exclusion by blocking > signals. This doesn't work on a SMP machine using kernel threads. > > What would be the right solution for this ? A new set of primitives > registered using dllockinit or making the defaults SMP thread-safe ? > > I suppose the linuxthreads port works because it has been tested only > with Linux executables and Linux executables don't use lazy resolution > of symbols ? I'm just speculating here. No. See the file libc_thread.c in the linuxthreads port. Note that if you call rfork (RF_MEM...) without any supporting infrastructure (eg. as provided by the linuxthreads port) you are in dangerous territory. You do not get *any* of the thread safe behaviour in libc, libgcc, or in ld-ef.so. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 9:21:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 528EB37B947 for ; Sun, 26 Mar 2000 09:21:51 -0800 (PST) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id JAA12030; Sun, 26 Mar 2000 09:21:52 -0800 Date: Sun, 26 Mar 2000 09:21:52 -0800 From: Arun Sharma To: "Richard Seaman, Jr." Cc: FreeBSD Hackers Subject: Re: RTLD thread safety Message-ID: <20000326092152.A12009@sharmas.dhs.org> References: <20000325225615.A11307@sharmas.dhs.org> <20000326110408.A378@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000326110408.A378@tar.com>; from Richard Seaman, Jr. on Sun, Mar 26, 2000 at 11:04:08AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 11:04:08AM -0600, Richard Seaman, Jr. wrote: > No. See the file libc_thread.c in the linuxthreads port. > > Note that if you call rfork (RF_MEM...) without any supporting > infrastructure (eg. as provided by the linuxthreads port) you > are in dangerous territory. You do not get *any* of the > thread safe behaviour in libc, libgcc, or in ld-ef.so. So you went the dllockinit way. Why not put that code in ld-elf.so itself ? Same goes for other work you've done as a part of the linuxthreads port. If it is the GPL contamination issue, someone (perhaps me) can rewrite the relevant parts. When FreeBSD has it's own native kernel supported pthreads package, all these things will be very much necessary, irrespective of which threads model the package uses. So why not do this work now ? Also, what happened to all the discussion on -arch ? Was there a consensus reached ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 12:25:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id B8C2837B995; Sun, 26 Mar 2000 12:25:21 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from barracuda (barracuda [208.11.247.5]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id PAA17049; Sun, 26 Mar 2000 15:25:20 -0500 (EST) Date: Sun, 26 Mar 2000 15:25:20 -0500 (EST) From: Thomas Stromberg X-Sender: tstromberg@barracuda.aquarium.rtci.com To: Sue Blake Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: syslogd stops logging - caught in the act In-Reply-To: <20000326140241.C43926@welearn.com.au> 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 Me and my roommate saw a similar thing occuring when developing a Windows NT EventLog -> syslogd forwarder (http://www.schizo.com/software/sislog/) on an older 4.0-CURRENT machine and a 2.2.8-RELEASE machine.. We concluded that it appears to be if the host sending the syslog messages is unresolvable (in our case, the DNS server could not be contacted), it would stop logging for us. I'm not sure about any other situations. This drove me nuts for quite a while, but since we have no home connectivity I forgot about submitting a GNATS report later. Perhaps a good thing to check... ------------------------------------------------------------------------- > Thomas R. Stromberg Senior Systems Administrator : > smtp[tstromberg@rtci.com] Research Triangle Commerce, Inc. : > http[afterthought.org] pots[1.919.657.1317] : > irc[helixblue] FreeBSD Contributor, Perl Hacker : ------------------------------------------------------------------------- On Sun, 26 Mar 2000, Sue Blake wrote: > Let's solve this once and for all. > > I've run syslogd -d and sent output to a file and waited for the > inevitable cessation of logging although syslogd is still running. > (Refer PRs 2191 5548 6216 8847 8865 10553 and two or three threads > in -isp and/or -questions earlier this year that summarised the > problems and their scope but didn't reach the list archives) > > Now logging's stopped and I need to get it restarted again soon, but I'd > like to collect some useful information first. I need help to do that. > > This has been reported for almost all -release and -stable versions since > early 2.2, and it's been hard to pin down what circumstances cause it > or to repeat it on unaffected machines. > > The common facts are that syslogd is running, using CPU, but nothing > goes to the logs, not mark messages, logger messages, nothing. One > exception: the logs dutifully rotate and log that they have rotated. > Sending a sighup does not fix it, only completely killing and > restarting syslogd gets it going. Unless this is done, it will continue > with the same behaviour (running but not logging) until reboot. > All past speculation as to the cause has been met with counterexamples. > > There are five freebsd machines that exhibit this problem which I only > have access to for another couple of days, so if anyone is interested > in solving this long-standing failure of syslogd please take this > opportunity to work with me on it. > > These machines range from almost idle very vanilla 3.3R workstations > with only sendmail running, up to 3.4-STABLE of january running many > daemons and with reasonable load, for which reliable logging is > critical. > > Replies to my email address would be appreciated. > > -- > > Regards, > -*Sue*- > > > > > 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 Sun Mar 26 12:33:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 969AB37B6CB for ; Sun, 26 Mar 2000 12:33:21 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id PAA08648; Sun, 26 Mar 2000 15:33:02 -0500 (EST) Date: Sun, 26 Mar 2000 15:33:02 -0500 (EST) From: Daniel Eischen To: Arun Sharma Cc: "Richard Seaman, Jr." , FreeBSD Hackers Subject: Re: RTLD thread safety In-Reply-To: <20000326092152.A12009@sharmas.dhs.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 Sun, 26 Mar 2000, Arun Sharma wrote: > On Sun, Mar 26, 2000 at 11:04:08AM -0600, Richard Seaman, Jr. wrote: > > No. See the file libc_thread.c in the linuxthreads port. > > > > Note that if you call rfork (RF_MEM...) without any supporting > > infrastructure (eg. as provided by the linuxthreads port) you > > are in dangerous territory. You do not get *any* of the > > thread safe behaviour in libc, libgcc, or in ld-ef.so. > > So you went the dllockinit way. Why not put that code in ld-elf.so itself ? > Same goes for other work you've done as a part of the linuxthreads port. If > it is the GPL contamination issue, someone (perhaps me) can rewrite the > relevant parts. > > When FreeBSD has it's own native kernel supported pthreads package, all > these things will be very much necessary, irrespective of which threads > model the package uses. So why not do this work now ? > > Also, what happened to all the discussion on -arch ? Was there a consensus > reached ? I believe Julian, Jason Evans, and myself reached somewhat of a consensus. The details haven't been worked out AFAIK. I have some more diagrams and code snippets that try to work out some of the details, but they need a little more work. I also need to hash things out with Jason and -arch before proceeding much further. Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 12:41:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 27F4F37B960 for ; Sun, 26 Mar 2000 12:41:17 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id NAA21931 for ; Sun, 26 Mar 2000 13:41:14 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38DE764F.DDC999CD@softweyr.com> Date: Sun, 26 Mar 2000 13:42:55 -0700 From: Wes Peters Reply-To: Keri Carpenter Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: sourceXchange is calling all device driver developers!] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keri Carpenter wrote: > > sourceXchange is looking for a few good device driver developers! > > We are sending out this targeted email only to those developers who > have identified an interest in device drivers through the skills > listed in your technical profile on sourceXchange. > > Here's the deal: > > We are negotiating with two potential sponsors (large brand names within > the graphics card and sound card markets) who are interested in > sponsoring a number of projects having to do with graphics and sound > card drivers for Linux. > > If we can convince them that our talent pool is able to meet their needs > then they will sponsor a few projects to start, with MANY more to > follow if all goes well. > > In that vein, we need a quick response from you so that we can quickly go > back to the sponsors and show them the enthusiasm and level of skill of > our developer community. > > Please send an email back to us to indicate how interested you are in > participating in these types of projects and in what capacity -- as a > Developer, Spec Writer or Peer Reviewer. If you could include a line > about a previous experience writing device drivers, that would be great! > > Email us back soon so that we can get these sponsors on board as soon > as possible. Then, we can start posting funded RFPs and get > you, our developers, some cool RFPs to work on! > > Look forward to hearing from you. :-) > > Keri Carpenter > Developer Relations > keri@collab.net > http://www.sourcexchange.com -- "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 Sun Mar 26 15:41:12 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 B679E37BAD1 for ; Sun, 26 Mar 2000 15:41:08 -0800 (PST) (envelope-from imp@harmony.village.org) 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 QAA51274; Sun, 26 Mar 2000 16:41:07 -0700 (MST) (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 QAA87438; Sun, 26 Mar 2000 16:40:53 -0700 (MST) Message-Id: <200003262340.QAA87438@harmony.village.org> To: Mitsuru IWASAKI Subject: Reserving Resources Cc: winter@jurai.net, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 21:49:13 +0900." <200003261249.VAA05285@tasogare.imasy.or.jp> References: <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> Date: Sun, 26 Mar 2000 16:40:53 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ moved from stable to hackers ]] dodd> Ah. So what we really want is some mechanism to tell the kernel 'hey, dodd> you! don't use this ioport/irq whatever.' (or otherwise mark some dodd> resources as not being available to PnP devices.) imp> I think that a null driver could easily be written. imp> I also think that combined with the hint mechanism I posted to new-bus imp> a couple of days ago this could be a viable way to reserve interrupts imp> from the boot loader. Iwasaki-san then replied: : That would be good. I'm also having similer idea that loading kernel : loadable module for legacy non-PnP devices specifying thier resources, like; : : load pcm : load sbc port 0x220 irq 5 drq 1 flags 0x15 : : Or, null driver module maybe just enough to hold resources; : load resourceholder port 0x220 irq 5 drq 1 : load resourceholder port drq 5 : : # BTW, it seems that the discussion is away from ep driver and -stable already :) : # Should we move to somewhere? Here's what I'll be happy to do. First, I'll create a null driver. Let's call it "null" since "resourceplaceholder" is too long. This driver's probe routine would always succeed, and its attach routine would gobble up all the resources associated with this. Very much like the unknown driver does for pnp resources today. Maybe it would even have an identify routine that would go looking for hints for each null device and then attach the null children to the right place in the tree (likely the nexus, but I haven't thought through all the implications of doing this). Second, I'll create the hint driver. The hint driver is attached to the nexus and allows one to aribitrarily set hints for other drivers. The drivers are free to ignore these hints, of course, but the mechanism is generic. Alternatively, we could just make it run early in the boot process. So, to reserve irq 5 because it has real hardware that we don't have a driver for, one could add device null0 at nexus? irq 5 to the config line of your kernel. Alternatively, you could add the following in your boot environment: hint.null.0.irq=5 hint.null.1.irq=15 hint.null.1.iobase=0x330 hint.null.1.iolen=16 and these resources would be unavailable for other purposes. I'm not quite sure about the syntax for these variables, but you get the idea. I'm also not sure how to handle multiple rids, etc. The code for the hint driver has been written. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 15:42:13 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 8599437B6D6 for ; Sun, 26 Mar 2000 15:42:10 -0800 (PST) (envelope-from imp@harmony.village.org) 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 QAA51280; Sun, 26 Mar 2000 16:42:09 -0700 (MST) (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 QAA87457; Sun, 26 Mar 2000 16:41:55 -0700 (MST) Message-Id: <200003262341.QAA87457@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: Shim Code #error needed Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 15:54:23 +0200." <20000326155423.A5771@daemon.ninth-circle.org> References: <20000326155423.A5771@daemon.ninth-circle.org> <200003252043.NAA73526@harmony.village.org> Date: Sun, 26 Mar 2000 16:41:55 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000326155423.A5771@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: : I assume you mean PCI devices, since ISA are detailed in: : : /src/sys/i386/isa/isa_compat.h Yes. However, the #error should be in ISA too since it is a common pilot error, despite having an UPDATING entry for a while. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 17:29:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 9872637B7DB for ; Sun, 26 Mar 2000 17:29:15 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id PAA18720 for freebsd-hackers@freebsd.org; Sun, 26 Mar 2000 15:34:30 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003270134.PAA18720@mauibuilt.com> Subject: wi0 ISA adaptor To: freebsd-hackers@freebsd.org Date: Sun, 26 Mar 2000 15:34:25 -1000 (HST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using a WavLAN ISA adaptor.. it comes up as pcic0: at port 0x3e2 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 have it set in the kernel as. device pcic0 at isa? irq 10 port 0x3e2 iomem 0xd0000 I have also tired device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 device pcic0 at isa? port 0x3e2 all of the above seem to make the card come up in dmesg but when pccard starts it says. current /root 78% pccardd -f /etc/pccard.conf.sample current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") this card works in my 4.0 laptop and the ISA adaptor works great with PAO and works ok with 3.4 any help would be great. Thanks in advance.. Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 17:39:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 7A72137BAF1 for ; Sun, 26 Mar 2000 17:39:21 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.158]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FS200CTU4KQGO@mta4.snfc21.pbi.net> for hackers@freebsd.org; Sun, 26 Mar 2000 17:38:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 846A17C0D4 for ; Sun, 26 Mar 2000 17:38:55 -0800 (PST) Date: Sun, 26 Mar 2000 17:38:55 -0800 (PST) From: Alex Zepeda Subject: Whatever happened to TenDRA? To: hackers@freebsd.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 Hmm. So I've compiled the TenDRA port, and I'm toying around with it, trying to get it to compile Qt (and perhaps gnu's libstdc++), but not suprisingly it seems to dislike some of the more basic (QList and QString and other template stuff) code in Qt, meaning even something as simple as moc can't be compiled. So off I went to the TenDRA web page, but it seems to be down (can't connect, etc). Has development on this compiler stopped or what? - alex who would like to see tcc as the base compiler someday... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 18:36: 2 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 D550137B518 for ; Sun, 26 Mar 2000 18:35:59 -0800 (PST) (envelope-from imp@harmony.village.org) 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 TAA51772; Sun, 26 Mar 2000 19:35:58 -0700 (MST) (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 TAA88555; Sun, 26 Mar 2000 19:35:44 -0700 (MST) Message-Id: <200003270235.TAA88555@harmony.village.org> To: FreeBSD MAIL Subject: Re: wi0 ISA adaptor Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 15:34:25 -1000." <200003270134.PAA18720@mauibuilt.com> References: <200003270134.PAA18720@mauibuilt.com> Date: Sun, 26 Mar 2000 19:35:44 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003270134.PAA18720@mauibuilt.com> FreeBSD MAIL writes: : current /root 78% pccardd -f /etc/pccard.conf.sample : current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") : Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") This tells me that the card isn't being powered up properly. Asside from the obvious questions about "are you sure it is well seated" and such, I'm not sure what to tell you. What does the rest of your system look like? Do you have multiple of these things installed? 0x3e2 is a non-standard address... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 19:48:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 169BF37BAF2 for ; Sun, 26 Mar 2000 19:48:32 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id NAA23746; Mon, 27 Mar 2000 13:47:52 +1000 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200003270347.NAA23746@mycenae.ilion.eu.org> To: Alex Zepeda Cc: hackers@FreeBSD.ORG Subject: Re: Whatever happened to TenDRA? In-reply-to: Your message of "Sun, 26 Mar 2000 17:38:55 PST." Date: Mon, 27 Mar 2000 13:47:50 +1000 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm. So I've compiled the TenDRA port, and I'm toying around with it, > trying to get it to compile Qt (and perhaps gnu's libstdc++), but not > suprisingly it seems to dislike some of the more basic (QList and QString > and other template stuff) code in Qt, meaning even something as simple as > moc can't be compiled. So off I went to the TenDRA web page, but it seems > to be down (can't connect, etc). Has development on this compiler stopped > or what? > The project has been discontinued by DRA. I've set up a mirror of the site (as it was last avaliable) at http://siliconbreeze.com/TenDRA/. Hope it's of some help. Pat. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Patryk Zadarnowski University of New South Wales School of Computer Science and Engineering -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 20: 7:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from f04n01.cac.psu.edu (f04s01.cac.psu.edu [128.118.141.31]) by hub.freebsd.org (Postfix) with ESMTP id BF48B37BA63 for ; Sun, 26 Mar 2000 20:07:41 -0800 (PST) (envelope-from john@essenz.com) Received: from essenz.com (tnt2-184-156.cac.psu.edu [128.118.184.156]) by f04n01.cac.psu.edu (8.9.3/8.9.3) with ESMTP id XAA75776 for ; Sun, 26 Mar 2000 23:07:39 -0500 Message-ID: <38DEDDD3.23ED6088@essenz.com> Date: Sun, 26 Mar 2000 23:04:35 -0500 From: John Von Essen Organization: Essenz Consulting X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Onboard Intel Networking - i82559 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the status of support for onboard Intel networking? Intel EtherExpress PRO/100 PCI Cards work fine with the fxp0 driver, but I am have having alot of problems with the onboard intel networking. For example, SuperMicro PIIIDM3 motherboards, while setting up a firewall server, I get "Unsupported PHY type" errors from the onboard networking.. Whats the deal, Linux supports this onboard networking with their eepro100.c driver, why can't freebsd support this? -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 20:22:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 6276937BAF2 for ; Sun, 26 Mar 2000 20:22:17 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id VAA29848; Sun, 26 Mar 2000 21:21:49 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id VAA23651; Sun, 26 Mar 2000 21:21:48 -0700 (MST) (envelope-from nate) Date: Sun, 26 Mar 2000 21:21:48 -0700 (MST) Message-Id: <200003270421.VAA23651@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: FreeBSD MAIL , freebsd-hackers@FreeBSD.ORG Subject: Re: wi0 ISA adaptor In-Reply-To: <200003270235.TAA88555@harmony.village.org> References: <200003270134.PAA18720@mauibuilt.com> <200003270235.TAA88555@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200003270134.PAA18720@mauibuilt.com> FreeBSD MAIL writes: > : current /root 78% pccardd -f /etc/pccard.conf.sample > : current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") > : Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") > > This tells me that the card isn't being powered up properly. Or that it's a CardBus card, and the PCIC in legacy mode can't read it.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:16:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 951FF37BB90 for ; Sun, 26 Mar 2000 21:16:29 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 54F60106; Mon, 27 Mar 2000 09:16:27 +0400 (MSD) Date: Mon, 27 Mar 2000 09:16:27 +0400 From: Nikolai Saoukh To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reserving Resources Message-ID: <20000327091626.A18459@Draculina.otdel-1.org> References: <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003262340.QAA87438@harmony.village.org>; from imp@village.org on Sun, Mar 26, 2000 at 04:40:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 04:40:53PM -0700, Warner Losh wrote: > First, I'll create a null driver. Let's call it "null" since > "resourceplaceholder" is too long. This driver's probe routine would > always succeed, and its attach routine would gobble up all the > resources associated with this. Very much like the unknown driver > does for pnp resources today. No good, because with current 'unknown' driver any kldloadable driver for pnp device would not get its resources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:19:11 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 786E737BAF2 for ; Sun, 26 Mar 2000 21:19:08 -0800 (PST) (envelope-from imp@harmony.village.org) 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 WAA52196; Sun, 26 Mar 2000 22:19:03 -0700 (MST) (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 WAA89979; Sun, 26 Mar 2000 22:18:49 -0700 (MST) Message-Id: <200003270518.WAA89979@harmony.village.org> To: Nikolai Saoukh Subject: Re: Reserving Resources Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 09:16:27 +0400." <20000327091626.A18459@Draculina.otdel-1.org> References: <20000327091626.A18459@Draculina.otdel-1.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> Date: Sun, 26 Mar 2000 22:18:49 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000327091626.A18459@Draculina.otdel-1.org> Nikolai Saoukh writes: : On Sun, Mar 26, 2000 at 04:40:53PM -0700, Warner Losh wrote: : : > First, I'll create a null driver. Let's call it "null" since : > "resourceplaceholder" is too long. This driver's probe routine would : > always succeed, and its attach routine would gobble up all the : > resources associated with this. Very much like the unknown driver : > does for pnp resources today. : : No good, because with current 'unknown' driver any kldloadable : driver for pnp device would not get its resources. In theory, if one matches with a -1 or smaller rather than 0, then it will be detached on reprobe. Isn't that the case? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:25: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id ED12637B6DC for ; Sun, 26 Mar 2000 21:24:58 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id C7A45F9; Mon, 27 Mar 2000 09:24:52 +0400 (MSD) Date: Mon, 27 Mar 2000 09:24:52 +0400 From: Nikolai Saoukh To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reserving Resources Message-ID: <20000327092452.B18459@Draculina.otdel-1.org> References: <20000327091626.A18459@Draculina.otdel-1.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003270518.WAA89979@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003270518.WAA89979@harmony.village.org>; from imp@village.org on Sun, Mar 26, 2000 at 10:18:49PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 10:18:49PM -0700, Warner Losh wrote: > : No good, because with current 'unknown' driver any kldloadable > : driver for pnp device would not get its resources. > > In theory, if one matches with a -1 or smaller rather than 0, then it > will be detached on reprobe. Isn't that the case? Current 'unknown' driver attaches with 0 priority, thus kldloaded driver is not called at all. And even when 'unknown' driver attaches with very low priority, what happens when real driver will be kldunloaded? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:31: 7 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 2665B37BAE0 for ; Sun, 26 Mar 2000 21:31:04 -0800 (PST) (envelope-from imp@harmony.village.org) 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 WAA52246; Sun, 26 Mar 2000 22:31:02 -0700 (MST) (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 WAA90072; Sun, 26 Mar 2000 22:30:48 -0700 (MST) Message-Id: <200003270530.WAA90072@harmony.village.org> To: Nikolai Saoukh Subject: Re: Reserving Resources Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 09:24:52 +0400." <20000327092452.B18459@Draculina.otdel-1.org> References: <20000327092452.B18459@Draculina.otdel-1.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003270518.WAA89979@harmony.village.org> Date: Sun, 26 Mar 2000 22:30:48 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000327092452.B18459@Draculina.otdel-1.org> Nikolai Saoukh writes: : Current 'unknown' driver attaches with 0 priority, thus kldloaded : driver is not called at all. And even when 'unknown' driver attaches : with very low priority, what happens when real driver will be : kldunloaded? Hmmm. The unknown driver should attach with a negative priority. What should happen? The drivers that have a negative priority should detach, or at least drivers with a very low priority (set a threshold of -1000 or something) detached before a probe... I know that this was talked about at one point, but come to think about it, I don't recall it being committed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:41:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 7097F37B8FF for ; Sun, 26 Mar 2000 21:41:15 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 1AF2BF9; Mon, 27 Mar 2000 09:41:14 +0400 (MSD) Date: Mon, 27 Mar 2000 09:41:13 +0400 From: Nikolai Saoukh To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reserving Resources Message-ID: <20000327094113.A18747@Draculina.otdel-1.org> References: <20000327092452.B18459@Draculina.otdel-1.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003270518.WAA89979@harmony.village.org> <20000327092452.B18459@Draculina.otdel-1.org> <200003270530.WAA90072@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003270530.WAA90072@harmony.village.org>; from imp@village.org on Sun, Mar 26, 2000 at 10:30:48PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 10:30:48PM -0700, Warner Losh wrote: > In message <20000327092452.B18459@Draculina.otdel-1.org> Nikolai Saoukh writes: > : Current 'unknown' driver attaches with 0 priority, thus kldloaded > : driver is not called at all. And even when 'unknown' driver attaches > : with very low priority, what happens when real driver will be > : kldunloaded? > > Hmmm. The unknown driver should attach with a negative priority. > What should happen? The drivers that have a negative priority should > detach, or at least drivers with a very low priority (set a threshold > of -1000 or something) detached before a probe... I know that this > was talked about at one point, but come to think about it, I don't > recall it being committed. I was wrong. 'unknown' driver attaches with (-100) priority. I have another problem -- when 'unknown' driver attached to my device, my kldloaded driver is not called at all, so I can't override 'unknown' with higher priority. So for a while I just made #if 0 ... #endif for 'unknown'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:43: 0 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 7F60B37BBF2 for ; Sun, 26 Mar 2000 21:42:56 -0800 (PST) (envelope-from imp@harmony.village.org) 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 WAA52296; Sun, 26 Mar 2000 22:42:54 -0700 (MST) (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 WAA90275; Sun, 26 Mar 2000 22:42:40 -0700 (MST) Message-Id: <200003270542.WAA90275@harmony.village.org> To: Nikolai Saoukh Subject: Re: Reserving Resources Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 09:41:13 +0400." <20000327094113.A18747@Draculina.otdel-1.org> References: <20000327094113.A18747@Draculina.otdel-1.org> <20000327092452.B18459@Draculina.otdel-1.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003270518.WAA89979@harmony.village.org> <20000327092452.B18459@Draculina.otdel-1.org> <200003270530.WAA90072@harmony.village.org> Date: Sun, 26 Mar 2000 22:42:40 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000327094113.A18747@Draculina.otdel-1.org> Nikolai Saoukh writes: : I was wrong. 'unknown' driver attaches with (-100) priority. : I have another problem -- when 'unknown' driver attached : to my device, my kldloaded driver is not called at all, so I can't : override 'unknown' with higher priority. So for a while : I just made #if 0 ... #endif for 'unknown'. Hmmm. Sounds like a bug to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:51:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 9FC6137B8AF for ; Sun, 26 Mar 2000 21:51:34 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 15BA0109; Mon, 27 Mar 2000 09:51:33 +0400 (MSD) Date: Mon, 27 Mar 2000 09:51:32 +0400 From: Nikolai Saoukh To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Reserving Resources Message-ID: <20000327095132.A18782@Draculina.otdel-1.org> References: <200003261249.VAA05285@tasogare.imasy.or.jp> <200003260112.SAA76635@harmony.village.org> <200003261249.VAA05285@tasogare.imasy.or.jp> <200003262340.QAA87438@harmony.village.org> <20000327091626.A18459@Draculina.otdel-1.org> <200003270518.WAA89979@harmony.village.org> <20000327092452.B18459@Draculina.otdel-1.org> <200003270530.WAA90072@harmony.village.org> <20000327094113.A18747@Draculina.otdel-1.org> <200003270542.WAA90275@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003270542.WAA90275@harmony.village.org>; from imp@village.org on Sun, Mar 26, 2000 at 10:42:40PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 10:42:40PM -0700, Warner Losh wrote: > In message <20000327094113.A18747@Draculina.otdel-1.org> Nikolai Saoukh writes: > : I was wrong. 'unknown' driver attaches with (-100) priority. > : I have another problem -- when 'unknown' driver attached > : to my device, my kldloaded driver is not called at all, so I can't > : override 'unknown' with higher priority. So for a while > : I just made #if 0 ... #endif for 'unknown'. > > Hmmm. Sounds like a bug to me. Not the only one ;-) See also kern/17219 and kern/16712. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:56:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id B302237B83D for ; Sun, 26 Mar 2000 21:56:40 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id OAA18799 for ; Mon, 27 Mar 2000 14:56:10 +0900 (JST) Message-Id: <200003270556.OAA18799@shidahara1.planet.sci.kobe-u.ac.jp> To: hackers@freebsd.org Subject: FreeBSD-CURRENT on Bochs VM. Date: Mon, 27 Mar 2000 14:56:09 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I heard that bochs (ports/emulators/bochs) gets now LGPLed, so I tryed to run FreeBSD-CURRENT on bochs VM,then I got two problems. 1.ISA PnP module try to read 0x??3 address. and Virtual VGA controller in bochs does not accept to read on 0x3e3 then the bochs VM panics. 2.ATA driver always issues ATA_C_SETFEATURES(0xef) command and the command is not acceped by virtual disk controller on bochs does not accept the command then the bochs VM panics. I'll also report bochs ML about this.But Just FYI. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 26 21:57:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 71DC737B564 for ; Sun, 26 Mar 2000 21:57:11 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id VAA08983; Sun, 26 Mar 2000 21:56:59 -0800 (PST) Date: Sun, 26 Mar 2000 21:56:59 -0800 From: Brooks Davis To: John Von Essen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel Networking - i82559 Message-ID: <20000326215659.A6921@orion.ac.hmc.edu> References: <38DEDDD3.23ED6088@essenz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <38DEDDD3.23ED6088@essenz.com>; from john@essenz.com on Sun, Mar 26, 2000 at 11:04:35PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 11:04:35PM -0500, John Von Essen wrote: > What is the status of support for onboard Intel networking? Intel > EtherExpress PRO/100 PCI Cards work fine with the fxp0 driver, but I am > have having alot of problems with the onboard intel networking. For > example, SuperMicro PIIIDM3 motherboards, while setting up a firewall > server, I get "Unsupported PHY type" errors from the onboard > networking.. Whats the deal, Linux supports this onboard networking with > their eepro100.c driver, why can't freebsd support this? The problem is being worked. Currently, reports say that the adaptors may work despite the error. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 0:36:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 9953A37B920 for ; Mon, 27 Mar 2000 00:36:10 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id AAA14551; Mon, 27 Mar 2000 00:29:37 -0800 (PST) Message-Id: <200003270829.AAA14551@implode.root.com> To: John Von Essen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel Networking - i82559 In-reply-to: Your message of "Sun, 26 Mar 2000 23:04:35 EST." <38DEDDD3.23ED6088@essenz.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 27 Mar 2000 00:29:37 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What is the status of support for onboard Intel networking? Intel >EtherExpress PRO/100 PCI Cards work fine with the fxp0 driver, but I am >have having alot of problems with the onboard intel networking. For >example, SuperMicro PIIIDM3 motherboards, while setting up a firewall >server, I get "Unsupported PHY type" errors from the onboard >networking.. Whats the deal, Linux supports this onboard networking with >their eepro100.c driver, why can't freebsd support this? Some minor changes are needed. I'll make them as soon as I can find the time. Meanwhile, this change might get it working: Index: if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.77 diff -c -r1.77 if_fxp.c *** if_fxp.c 1999/09/30 19:03:12 1.77 --- if_fxp.c 2000/03/27 08:30:21 *************** *** 839,845 **** /* * Shift in address. */ ! for (x = 6; x > 0; x--) { if ((i + offset) & (1 << (x - 1))) { reg = FXP_EEPROM_EECS | FXP_EEPROM_EEDI; } else { --- 839,845 ---- /* * Shift in address. */ ! for (x = 8; x > 0; x--) { if ((i + offset) & (1 << (x - 1))) { reg = FXP_EEPROM_EECS | FXP_EEPROM_EEDI; } else { This will probably break support for those that were working, however. Let me know if it works. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 1:27:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from khelben.inrialpes.fr (khelben.inrialpes.fr [194.199.17.165]) by hub.freebsd.org (Postfix) with ESMTP id 5BC2437B507 for ; Mon, 27 Mar 2000 01:27:32 -0800 (PST) (envelope-from bellier@khelben.inrialpes.fr) Received: by khelben.inrialpes.fr (8.9.3/8.9.3) id LAA00334; Mon, 27 Mar 2000 11:29:17 +0200 (CEST) (envelope-from bellier) From: Ludovic Bellier Organization: Projet Planete To: hackers@FreeBSD.ORG Subject: freebsd and wavelan card Date: Mon, 27 Mar 2000 11:23:28 +0200 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain Cc: ludovic.bellier@inria.fr MIME-Version: 1.0 Message-Id: <00032711291700.00320@khelben> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello I have a pc under freebsd and a wavelan isa adapter. What I have to do to make this card works ? in the documentation, I saw that the i/o address is 3e2 so i put a line in my kernel configuration card : device wi0 at isa? port 0x3e2 net irq ? the boot process ouputs the error : wi0 not found at 0x3e2 i tried to find the irq, without success please use my personnal address to answer : ludovic.bellier@inria.fr -- Bellier Ludovic Projet PLANETE : mobilite IPv6 http://bounty.inrialpes.fr mailto: Ludovic.Bellier@inria.fr tel : 04 76 61 54 03 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 2:31:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70]) by hub.freebsd.org (Postfix) with ESMTP id BEFC837BB62 for ; Mon, 27 Mar 2000 02:31:48 -0800 (PST) (envelope-from ludovic.bellier@inrialpes.fr) Received: from iseran.inrialpes.fr (iseran.inrialpes.fr [194.199.24.100]) by ebene.inrialpes.fr (8.9.3/8.8.5) with ESMTP id MAA14092; Mon, 27 Mar 2000 12:25:46 +0200 (MET DST) Received: from inrialpes.fr (iseran.inrialpes.fr [194.199.24.100]) by iseran.inrialpes.fr (8.8.7/8.8.5) with ESMTP id MAA01776; Mon, 27 Mar 2000 12:31:38 +0200 (MET DST) Message-ID: <38DF388A.2E7E02DC@inrialpes.fr> Date: Mon, 27 Mar 2000 12:31:38 +0200 From: Bellier Ludovic X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG, Ludovic Bellier Subject: wavelan isa, second part Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i try to launch pccardd, but the deamon returns an error : Mar 27 12:28:39 mephistonaelle pccardd[302]: fatal error: no PC-CARD slots in my kernel configuration file, i have uncommented the lines : # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? whats wrong ? -- Bellier Ludovic Projet PLANETE : mobilite IPv6 http://bounty.inrialpes.fr mailto: Ludovic.Bellier@inria.fr tel : 04 76 61 54 03 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 3:48:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 675FA37BC81; Mon, 27 Mar 2000 03:48:09 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc343042.tokyo.jcom.ne.jp [203.140.143.42]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 03/13/00) with ESMTP id UAA15678; Mon, 27 Mar 2000 20:48:02 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id UAA07009; Mon, 27 Mar 2000 20:47:30 +0900 (JST) Date: Mon, 27 Mar 2000 20:47:29 +0900 Message-ID: <86pusgmy7i.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: freebsd-hackers@FreeBSD.org Cc: tomo@kuma-soft.com, freebsd-ports@FreeBSD.org Subject: Re: ports/17496: /usr/ports/editors/emacs termcap problem In-Reply-To: In your message of "Mon, 27 Mar 2000 02:10:08 -0800 (PST)" <200003271010.CAA14950@freefall.freebsd.org> References: <200003271010.CAA14950@freefall.freebsd.org> User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. emacs CANNOT use libtermcap.a (libncurses.a) of FreeBSD-4.0. Speaking of termcap problems, I recall Yokota-san's suggestion. http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=567231+569252+/usr/local/www/db/text/1999/freebsd-current/19991205.freebsd-current There has been many PR's regarding termcap and most of them are still left open. I suppose it's time for us to do the overall change. -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 5: 0: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id D927337BAF9; Mon, 27 Mar 2000 04:59:31 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id WAA63021; Mon, 27 Mar 2000 22:58:55 +1000 (EST) (envelope-from sue) Date: Mon, 27 Mar 2000 22:58:52 +1000 From: Sue Blake To: Thomas Stromberg Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: syslogd stops logging - caught in the act Message-ID: <20000327225851.B62756@welearn.com.au> Mail-Followup-To: Thomas Stromberg , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <20000326140241.C43926@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Thomas Stromberg on Sun, Mar 26, 2000 at 03:25:20PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 03:25:20PM -0500, Thomas Stromberg wrote: > Me and my roommate saw a similar thing occuring when developing a Windows > NT EventLog -> syslogd forwarder (http://www.schizo.com/software/sislog/) > on an older 4.0-CURRENT machine and a 2.2.8-RELEASE machine.. > > We concluded that it appears to be if the host sending the syslog messages > is unresolvable (in our case, the DNS server could not be contacted), it > would stop logging for us. I'm not sure about any other situations. > > This drove me nuts for quite a while, but since we have no home > connectivity I forgot about submitting a GNATS report later. Perhaps a > good thing to check... Yes, this seems to be exactly what is happening, but it does affect machines which only log for and to themselves. The DNS angle explains why at least five machines in the one building are showing the problems all the time when few others have seen this and only temporarily when it occurs to others. The primary name server for the affected machines is frequently rebooted to freshen it up a bit (sic). As I'm leaving tomorrow, I have left instructions that anyone who claims to have a valid reason for rebooting the nameserver is obliged to kill and restart syslogd on up to ten other machines immediately afterwards :-) Still, it would be real nice to have a suitproof syslogd one day. It looks like that won't be so far off, now that we know the cause. Thanks to all who helped and encouraged. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 6:14:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1-12.onmedia.com (mx1-12.onmedia.com [209.133.35.17]) by hub.freebsd.org (Postfix) with ESMTP id 4480237B70A for ; Mon, 27 Mar 2000 06:14:31 -0800 (PST) (envelope-from p_a_r@goplay.com) Received: from GP1 (root@localhost) by mx1-12.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id GAA12755 for hackers@freebsd.org; Mon, 27 Mar 2000 06:10:05 -0800 (PST) Received: from OnMedia Mail (GPX1) by mx1-12.onmedia.com ($Revision: 2.3 $) with OICP id 81491281; Mon, 27 Mar 2000 06:10:05 -0800 Subject: BSD VS BDS Date: Mon, 27 Mar 2000 06:10:01 -0800 Message-Id: <81491281.2.1636@mx1-12.onmedia.com> Reply-To: "p_a_r" From: "p_a_r" To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone tell me the differens in FreeBSD and NetBSD. I would like to set up 2 internet servers whitch one should i take? Lars Beinhoff +--------------------------------------------------------------------------+ | The coolest site for free home pages, email, chat, e-cards, movie info.. | | http://www.goplay.com - it's time to Go Play! | +--------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 6:47:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id 68AC037B80B for ; Mon, 27 Mar 2000 06:47:13 -0800 (PST) (envelope-from zab@zabbo.net) Received: (from zab@localhost) by devserv.devel.redhat.com (8.9.3/8.9.3) id JAA04701; Mon, 27 Mar 2000 09:46:34 -0500 X-Authentication-Warning: devserv.devel.redhat.com: zab set sender to zab@zabbo.net using -f Date: Mon, 27 Mar 2000 09:46:34 -0500 From: Zach Brown To: Jonathan Lemon Cc: Keith Stevenson , justin@apple.com, hackers@FreeBSD.ORG Subject: Re: Request for review (HW checksum patches) Message-ID: <20000327094634.F427@devserv.devel.redhat.com> References: <200003260056.SAA29089@prism.flugsvamp.com> <20000325212533.B73602@osaka.louisville.edu> <20000325223624.L71371@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000325223624.L71371@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Sat, Mar 25, 2000 at 10:36:24PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right now, just the Alteon cards. Support for the 3Com-XL can probably > be added without too much trouble. I don't see a driver for the 3Com-990 > though, and I can't find a reference to it on the 3Com website, is > this a new card? Its fairly new, and the future of support for it under free OSes looks grim. its basically got an arm core in it that does all the magic. rumor has it that there are lots of nasty nasty patents involved in the thing and 3com isn't too excited about giving out docs (or, even worse, are under patent licensing agreements that forbid them from doing so). I called 3com and asked to get a list of patents associated with the card but all they gave me were the 3com ones on doing typical ethernet interface stuff.. no magical driver interraction patents. I'd love to get more conclusive information. It looks like a fun little toy. in differnet news, the most recently released eepro100 linux driver from intel shows how to do csum offloading and shows how they load microcode to do interrupt mitigation and such. one would hope that they could now actually admit to the features and release docs, but.. :( Its worth noting that vendors like syskonnect actually want to _help_ people write drivers. they should be encouraged :) -- zach To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 8: 4: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 9E18137B637; Mon, 27 Mar 2000 08:04:03 -0800 (PST) (envelope-from john@athena.lightningone.net) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id LAA36007; Mon, 27 Mar 2000 11:08:57 -0500 (EST) (envelope-from john@athena.lightningone.net) Date: Mon, 27 Mar 2000 11:08:57 -0500 (EST) From: Essenz Consulting To: msmith@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Re: Onboard Intel NIC 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 Mike, I am sorry I was so jumpy with the description of my problem. Let me elaborate some more. I have two NIC's, a PCI Card Intel PRO/100 and an onboard Intel PRO/100. The onboard NIC is giving the following kernel error: /kernel: fxp1: warning: unsupported PHY, type = 17, addr = 2 Yes, the card itself is still working, it actually works fine, but every minute this error comes up. Since this is a firewall box, I dont want hundreds of these errors in my log every day. I did a little investigating, I am no where near as knowledgable as soom of the freebsd people, but I looked at the if_fxp.c driver src and saw that PHY Media refered to the Media of your LAN. (simplex, duplex, 10Mbit, 100Mbit) In any case, this is a signifacant bug to be worked out. David Greenman sent me an email with a little snipit of code to add the to fxp src, I will try that today. He also voiced his opinion about trying to fix this issue with onboard networking, because those supermicro boards are rolling out quickly. Getting back to my idea of this problem being with media type, I did ifconfig -a and got the following: fxp0: flags=8843 mtu 1500 inet 216.243.128.21 netmask 0xffffff80 broadcast 216.243.128.127 ether 00:90:27:b0:39:9d media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP fxp1: flags=8806 mtu 1500 inet 216.243.129.1 netmask 0xffffff00 broadcast 216.243.129.255 ether 00:30:48:10:0a:2d media: manual supported media: manual Obviously, they do not match. For starters I dont even know how to set these to be the same media. I tryed ifconfig fxp1 media 100BaseTX, but that was met with the error: SIOCSIFMEDIA: Device not configured. Again, any help on this would be great. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 8:48:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ra.nks.net (ra.nks.net [208.226.218.5]) by hub.freebsd.org (Postfix) with ESMTP id A87BF37BE7C for ; Mon, 27 Mar 2000 08:48:37 -0800 (PST) (envelope-from joeo@cracktown.com) Received: from localhost (joeo@localhost) by ra.nks.net (8.8.7/8.8.7) with ESMTP id LAA06856 for ; Mon, 27 Mar 2000 11:48:38 -0500 Date: Mon, 27 Mar 2000 11:48:38 -0500 (EST) From: X-Sender: joeo@ra.nks.net To: hackers@freebsd.org Subject: figuring out were an spl lock isn't being freed 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 playing with a third party kernel module under 4.0. Occasionally the box locks up during extended access to the device it supports, though the box will respond to pings and other hardware driven interupts, but will not let loggins happen, and open telnet sessions from remote hosts freeze. I'm guessing an spltty isn't being freed. What's the best way to go about figuring out what function isn't freeing the lock or returning? Thanks for any help, Joe Orthoefer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 9:12:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 4F3BE37B679; Mon, 27 Mar 2000 09:12:26 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb05.imasy.or.jp [202.227.24.133]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id CAA08158; Tue, 28 Mar 2000 02:12:20 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003271712.CAA08158@tasogare.imasy.or.jp> To: freebsd-mobile@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Call for review: new pccard.conf scheme X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 28 Mar 2000 02:12:20 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 220 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm working on new pccard.conf scheme, /etc/defaults/pccard.conf and /etc/pccard.conf in the same manner as rc.conf. Attached patch for pccardd(8) contains: 1. improved `include' keyword function for error handling. 2. changed available io, irq, mem pool so that they can be overridden. 3. default config file as /etc/defaults/pccard.conf instead of /etc/pccard.conf. Currently, /etc/pccard.conf.sample is provied as sample configuration file for pccard, most of users modify this file based on his/her laptop environment. However, on every upgrading, they have to merge new sample config into own config file. The pccard configuration can be separated into two parts; Default pccard configuration database for general purpose, and user specific configuration (further, available resource infomation and additional pccard entries). By separating the file into two (/etc/defaults/pccard.conf as default, /etc/pccard.conf as user config), upgrading pccard.conf would be much easier. Yes, just update /etc/defaults/pccard.conf! To test this stuff, apply the patch and compile & install src/usr.sbin/pccard/pccardd, and; # cp src/etc/pccard.conf.sample /etc/defaults/pccard.conf # echo include /etc/pccard.conf >> /etc/defaults/pccard.conf to make sample config to default config file. Then, create your own pccard config, you can change config entries here from default; # vi /etc/pccard.conf # change or add or delete contents or you can also do # rm /etc/pccard.conf Comments? Index: file.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/file.c,v retrieving revision 1.24 diff -u -r1.24 file.c --- file.c 2000/01/26 17:54:00 1.24 +++ file.c 2000/03/27 07:29:01 @@ -37,7 +37,12 @@ static FILE *in; static int includes = 0; -static FILE *files[MAXINCLUDES] = {NULL, }; +static struct { + FILE *filep; + char *filename; + int lineno; +} configfiles[MAXINCLUDES] = {{NULL, NULL, 0}}; + static int pushc, pusht; static int lineno; static char *filename; @@ -114,12 +119,15 @@ die("readfile"); } for (i = 0; i < MAXINCLUDES; i++) { - if (files[i]) { - fclose(files[i]); - files[i] = NULL; + if (configfiles[i].filep) { + fclose(configfiles[i].filep); + configfiles[i].filep = NULL; } } - files[includes = 0] = in; + includes = 0; + configfiles[includes].filep = in; + filename = configfiles[includes].filename = name; + parsefile(); for (cp = cards; cp; cp = cp->next) { if (cp->config == 0) @@ -132,50 +140,54 @@ parsefile(void) { int i; - int irq_init = 0; - int io_init = 0; - struct allocblk *bp; + struct allocblk *bp, *next; char *incl; pushc = 0; lineno = 1; - for (i = 0; i < 16 ; i++) - if (pool_irq[i]) { - irq_init = 1; - break; - } for (;;) switch (keyword(next_tok())) { case KWD_EOF: /* EOF */ return; case KWD_IO: - /* reserved I/O blocks */ + /* override reserved I/O blocks */ + bzero(io_avail, sizeof(io_avail)); + for (bp = pool_ioblks; bp; bp = next) { + next = bp->next; + free(bp); + } + pool_ioblks = NULL; + while ((bp = ioblk_tok(0)) != 0) { - if (!io_init) { - if (bp->size == 0 || bp->addr == 0) { - free(bp); - continue; - } - bit_nset(io_avail, bp->addr, - bp->addr + bp->size - 1); - bp->next = pool_ioblks; - pool_ioblks = bp; + if (bp->size == 0 || bp->addr == 0) { + free(bp); + continue; } + bit_nset(io_avail, bp->addr, + bp->addr + bp->size - 1); + bp->next = pool_ioblks; + pool_ioblks = bp; } - io_init = 1; pusht = 1; break; case KWD_IRQ: - /* reserved irqs */ + /* override reserved irqs */ + bzero(pool_irq, sizeof(pool_irq)); + while ((i = irq_tok(0)) > 0) - if (!irq_init) - pool_irq[i] = 1; - irq_init = 1; + pool_irq[i] = 1; pusht = 1; break; case KWD_MEMORY: - /* reserved memory blocks. */ + /* override reserved memory blocks. */ + bzero(mem_avail, sizeof(mem_avail)); + for (bp = pool_mem; bp; bp = next) { + next = bp->next; + free(bp); + } + pool_mem = NULL; + while ((bp = memblk_tok(0)) != 0) { if (bp->size == 0 || bp->addr == 0) { free(bp); @@ -732,7 +744,9 @@ if (includes) { fclose(in); includes--; - in = files[includes]; + in = configfiles[includes].filep; + filename = configfiles[includes].filename; + lineno = configfiles[includes].lineno; return _next_tok(); /* recursive */ } if (p != buf) { @@ -773,17 +787,29 @@ * Include configuration file */ static void -file_include(char *filename) +file_include(char *incl) { FILE *fp; - includes++; if (includes >= MAXINCLUDES) { error("include nesting overflow"); + pusht = 0; + goto out; } - if (!(fp = fopen(filename, "r"))) { + if (strcmp(incl, filename) == 0) { + error("can't include from the same file"); + pusht = 0; + goto out; + } + if (!(fp = fopen(incl, "r"))) { error("can't open include file"); - includes--; + pusht = 0; + goto out; } - in = files[includes] = fp; + configfiles[includes].lineno = lineno; + includes++; + in = configfiles[includes].filep = fp; + filename = configfiles[includes].filename = incl; +out: + return; } Index: pccardd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/pccardd.c,v retrieving revision 1.6 diff -u -r1.6 pccardd.c --- pccardd.c 1999/08/28 01:17:37 1.6 +++ pccardd.c 2000/03/27 06:23:56 @@ -37,7 +37,7 @@ #define EXTERN #include "cardd.h" -char *config_file = "/etc/pccard.conf"; +char *config_file = "/etc/defaults/pccard.conf"; /* * mainline code for cardd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 9:34:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 32E6237B60F for ; Mon, 27 Mar 2000 09:34:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA41640; Mon, 27 Mar 2000 09:34:27 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 09:34:27 -0800 (PST) From: Matthew Dillon Message-Id: <200003271734.JAA41640@apollo.backplane.com> To: Cc: hackers@FreeBSD.ORG Subject: Re: figuring out were an spl lock isn't being freed References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm playing with a third party kernel module under 4.0. : :Occasionally the box locks up during extended access to the device it :supports, though the box will respond to pings and other hardware driven :interupts, but will not let loggins happen, and open telnet sessions from :remote hosts freeze. I'm guessing an spltty isn't being freed. What's :the best way to go about figuring out what function isn't freeing the lock :or returning? : :Thanks for any help, : :Joe Orthoefer Enable DDB in the kernel config and when the machine locks up, assuming you aren't running X on the console (or if you are that you can ctl-alt-F? to get back to the a character screen), type ctl-alt-esc to get the DDB prompt. Then do a 'ps' to see what things are hanging on. It probably isn't an spl*() issue. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 9:53:49 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 E784837B60F; Mon, 27 Mar 2000 09:53:37 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA18212; Mon, 27 Mar 2000 12:54:06 -0500 (EST) Message-Id: <200003271754.MAA18212@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 12:49:46 -0500 To: Essenz Consulting , msmith@FreeBSD.ORG From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've asked about this several times and was beaten silly by Wes Peters and Co. . It seems that they dont like to be bothered by the thousands of people suffering from a driver that is not up to date (linux and netbsd were fixed months ago)......they are way too busy working on 5.0 or something else that about 1% of their user base is using to be bothered by routine driver maintenance. While the card "works" you wont be able to set media-related features..so you really do need the fix. I've successfully fixed our version and its working nicely.....I've forwarded the info to DG so hopefully it will be patched soon. DB At 11:08 AM 3/27/00 -0500, Essenz Consulting wrote: >Mike, > >I am sorry I was so jumpy with the description of my problem. Let me >elaborate some more. I have two NIC's, a PCI Card Intel PRO/100 and an >onboard Intel PRO/100. The onboard NIC is giving the following kernel >error: > >/kernel: fxp1: warning: unsupported PHY, type = 17, addr = 2 > >Yes, the card itself is still working, it actually works fine, but every >minute this error comes up. Since this is a firewall box, I dont want >hundreds of these errors in my log every day. > >I did a little investigating, I am no where near as knowledgable as soom >of the freebsd people, but I looked at the if_fxp.c driver src and saw >that PHY Media refered to the Media of your LAN. (simplex, duplex, >10Mbit, 100Mbit) In any case, this is a signifacant bug to be worked out. >David Greenman sent me an email with a little snipit of code to add the to >fxp src, I will try that today. He also voiced his opinion about trying to >fix this issue with onboard networking, because those supermicro boards >are rolling out quickly. > >Getting back to my idea of this problem being with media type, I did >ifconfig -a and got the following: > >fxp0: flags=8843 mtu 1500 > inet 216.243.128.21 netmask 0xffffff80 broadcast 216.243.128.127 > ether 00:90:27:b0:39:9d > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP >fxp1: flags=8806 mtu 1500 > inet 216.243.129.1 netmask 0xffffff00 broadcast 216.243.129.255 > ether 00:30:48:10:0a:2d > media: manual > supported media: manual > >Obviously, they do not match. For starters I dont even know how to set >these to be the same media. I tryed ifconfig fxp1 media 100BaseTX, but >that was met with the error: SIOCSIFMEDIA: Device not configured. > >Again, any help on this would be great. > >John > > > > >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 Mon Mar 27 10: 4:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from account.abs.net (account.abs.net [207.114.5.70]) by hub.freebsd.org (Postfix) with ESMTP id 9A93E37B918; Mon, 27 Mar 2000 10:04:44 -0800 (PST) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id NAA94040; Mon, 27 Mar 2000 13:04:42 -0500 (EST) (envelope-from howardl) From: Howard Leadmon Message-Id: <200003271804.NAA94040@account.abs.net> Subject: Troubles with network & buffers.. Any Ideas?? To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Date: Mon, 27 Mar 2000 13:04:42 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL72 (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 Hello, I am running a 4.0-STABLE machine which is being used to host an Undernet IRC server, and the machine keeps dying at times, or should I say the networking side of it is at least dying. At first I thought it might have been related to the dc (DEC Chip) based drivers, so I replaced it with a EEpro board using the fxp driver, but the same results. I have also set MNBCLUSTERS to 20480, and when I do a netstat I see in general plenty of free clusters, but suspect I must be running out of some other resource. If I do a netstat -m, I see info like this: u2$ netstat -m 1697/2144/81920 mbufs in use (current/peak/max): 498 mbufs allocated to data 1199 mbufs allocated to packet headers 221/514/20480 mbuf clusters in use (current/peak/max) 1296 Kbytes allocated to network (50% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines When the machine last froze, the Kbytes allocated to the network was 99% in use, and the mbufs were up to about 20K of the 80K allocated, but I saw no calls for memory denied or delayed. Still after a few hours of uptime, I start seeing errors like this, and then the machines network interface dies and I have to reboot to get everything back in operation: Mar 27 12:39:00 u2 /kernel: fxp0: device timeout Mar 27 12:39:00 u2 syslogd: sendto: No buffer space available Mar 27 12:39:38 u2 last message repeated 2 times Mar 27 12:41:32 u2 last message repeated 6 times Mar 27 12:44:15 u2 syslogd: sendto: No buffer space available Mar 27 12:44:04 u2 last message repeated 8 times Not sure what other information to send, but here is a dmesg on the machine, and if anyone has any ideas, or needs more info please let me know. It's very annoying to have to reboot this machine daily, sometimes more often.. :( Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #8: Wed Mar 22 18:31:51 EST 2000 howardl@u2.abs.net:/usr/src/sys/compile/U2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 402587648 (393152K bytes) config> q avail memory = 387022848 (377952K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02c8000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c809c. 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 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 7.2 irq 5 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x5000-0x500f at device 7.3 on pci0 fxp0: port 0xd400-0xd41f mem 0xd5400000-0xd54fffff,0xd5510000-0xd5510fff irq 17 at device 13.0 on pci0 fxp0: Ethernet address 00:a0:c9:c7:fb:ff pci0: at 15.0 irq 16 atapci1: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 18 at device 19.0 on pci0 atapci2: port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 18 at device 19.1 on pci0 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-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> 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: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 8693MB [17662/16/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s1a --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10: 7:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A263A37B779 for ; Mon, 27 Mar 2000 10:07:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA11275; Mon, 27 Mar 2000 20:07:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 12:49:46 CDT." <200003271754.MAA18212@etinc.com> Date: Mon, 27 Mar 2000 20:07:07 +0200 Message-ID: <11273.954180427@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis, You need to work with the maintainer of the driver on issues like this, and as you have found out that is David Greenman. If you have any issues regarding that, him or the result thereof, address your email to core. Under *NO* circumstances is behaviour like this acceptable. You have been warned about your cheap pot-shots many times before and if you continue it will not take long time before you have collected the box-tops you need to get filtered out of our mailing lists. Poul-Henning In message <200003271754.MAA18212@etinc.com>, Dennis writes: >I've asked about this several times and was beaten silly by Wes Peters and >Co. . It seems that they dont like to be bothered by the thousands of >people suffering from a driver that is not up to date (linux and netbsd >were fixed months ago)......they are way too busy working on 5.0 or >something else that about 1% of their user base is using to be bothered by >routine driver maintenance. > >While the card "works" you wont be able to set media-related features..so >you really do need the fix. I've successfully fixed our version and its >working nicely.....I've forwarded the info to DG so hopefully it will be >patched soon. > >DB -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:43:33 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 E78BA37BF58 for ; Mon, 27 Mar 2000 10:42:37 -0800 (PST) (envelope-from imp@harmony.village.org) 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 LAA55017; Mon, 27 Mar 2000 11:42:37 -0700 (MST) (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 LAA95141; Mon, 27 Mar 2000 11:42:20 -0700 (MST) Message-Id: <200003271842.LAA95141@harmony.village.org> To: Ludovic Bellier Subject: Re: freebsd and wavelan card Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 11:23:28 +0200." <00032711291700.00320@khelben> References: <00032711291700.00320@khelben> Date: Mon, 27 Mar 2000 11:42:20 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00032711291700.00320@khelben> Ludovic Bellier writes: : device wi0 at isa? port 0x3e2 net irq ? device pcic0 at isa? port 0x3e2 device wi0 Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:43:34 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 EB0F937BD5C for ; Mon, 27 Mar 2000 10:43:07 -0800 (PST) (envelope-from imp@harmony.village.org) 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 LAA55025; Mon, 27 Mar 2000 11:43:06 -0700 (MST) (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 LAA95159; Mon, 27 Mar 2000 11:42:50 -0700 (MST) Message-Id: <200003271842.LAA95159@harmony.village.org> To: Ludovic Bellier Subject: Re: freebsd and wavelan card Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 11:23:28 +0200." <00032711291700.00320@khelben> References: <00032711291700.00320@khelben> Date: Mon, 27 Mar 2000 11:42:50 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG P.S. You'll also need to launch pccardd and configure it just like you had a laptop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:43:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 8B35C37BD62; Mon, 27 Mar 2000 10:43:34 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA16040; Mon, 27 Mar 2000 10:36:22 -0800 (PST) Message-Id: <200003271836.KAA16040@implode.root.com> To: Dennis Cc: Essenz Consulting , msmith@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 12:49:46 EST." <200003271754.MAA18212@etinc.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 27 Mar 2000 10:36:22 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've asked about this several times and was beaten silly by Wes Peters and >Co. . It seems that they dont like to be bothered by the thousands of >people suffering from a driver that is not up to date (linux and netbsd >were fixed months ago)......they are way too busy working on 5.0 or >something else that about 1% of their user base is using to be bothered by >routine driver maintenance. > >While the card "works" you wont be able to set media-related features..so >you really do need the fix. I've successfully fixed our version and its >working nicely.....I've forwarded the info to DG so hopefully it will be >patched soon. While I appreciate the assistence that Dennis has provided me in the past few days with regard to this problem, I really don't think these barbs are justified. There have been some recent Intel boards that haven't worked with FreeBSD, but until just recently I wasn't able to find one and the person who orginally reported the problem just returned the card for one that did work. In fact I wasn't able to determine for several weeks that it even was a software issue. As for "thousands of people people suffering from a driver that is not up-to-date", I think you are *way* overstating the breadth of the problem. I'll also point out that hundreds of thousands of people find the fxp driver a lifesaver and one of the best functioning network drivers in the source tree. Your comments definately piss me off and definately provide for major negative motivation as far as my interest in solving this problem is concerned. Bludgeoning tactics like yours might sometimes work in business, but they sure as hell don't work in free software development. As said in previous mail, I'll implement a solution as soon as I can find some time. I'm extremely busy these days and if I can somehow squeeze in some quality development time inbetween multiple trips across te country, then I will. Otherwise people will either have to use the patch I mailed out or just wait. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:46:51 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 DEC4837BFC1 for ; Mon, 27 Mar 2000 10:44:03 -0800 (PST) (envelope-from imp@harmony.village.org) 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 LAA55037; Mon, 27 Mar 2000 11:43:59 -0700 (MST) (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 LAA95186; Mon, 27 Mar 2000 11:43:42 -0700 (MST) Message-Id: <200003271843.LAA95186@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: wi0 ISA adaptor Cc: FreeBSD MAIL , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 21:21:48 MST." <200003270421.VAA23651@nomad.yogotech.com> References: <200003270421.VAA23651@nomad.yogotech.com> <200003270134.PAA18720@mauibuilt.com> <200003270235.TAA88555@harmony.village.org> Date: Mon, 27 Mar 2000 11:43:42 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003270421.VAA23651@nomad.yogotech.com> Nate Williams writes: : > In message <200003270134.PAA18720@mauibuilt.com> FreeBSD MAIL writes: : > : current /root 78% pccardd -f /etc/pccard.conf.sample : > : current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") : > : Mar 27 01:27:20 current pccardd[215]: No card in database for ""("") : > : > This tells me that the card isn't being powered up properly. : : Or that it's a CardBus card, and the PCIC in legacy mode can't read : it.... That's possible, but if this is the wavelan card in a isa adapater, then it should just work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:51:42 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 76C4F37BF2E for ; Mon, 27 Mar 2000 10:51:36 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA18460; Mon, 27 Mar 2000 13:52:10 -0500 (EST) Message-Id: <200003271852.NAA18460@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 13:47:49 -0500 To: Poul-Henning Kamp From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <11273.954180427@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:07 PM 3/27/00 +0200, Poul-Henning Kamp wrote: > >Dennis, > >You need to work with the maintainer of the driver on issues like >this, and as you have found out that is David Greenman. Been there, done that...tired of waiting. What does one do when the maintainers dont maintain if complaining isnt allowed? > >If you have any issues regarding that, him or the result thereof, >address your email to core. > >Under *NO* circumstances is behaviour like this acceptable. > >You have been warned about your cheap pot-shots many times before >and if you continue it will not take long time before you have >collected the box-tops you need to get filtered out of our mailing >lists. Yes, lets silence the critics. Nice way to run an O/S. Last time I asked a simple question as to whether this problem had been fixed yet and I was told to figure it out myself. It seems that with the freebsd-slackers the only was to get results is to emphasize the importance of this to your user base. The fxp driver is "recommended" as the best driver, yet maintaining it is a burden and complaining is not allowed. When is that BSDI "support" going to kick-in? DB > >Poul-Henning > >In message <200003271754.MAA18212@etinc.com>, Dennis writes: >>I've asked about this several times and was beaten silly by Wes Peters and >>Co. . It seems that they dont like to be bothered by the thousands of >>people suffering from a driver that is not up to date (linux and netbsd >>were fixed months ago)......they are way too busy working on 5.0 or >>something else that about 1% of their user base is using to be bothered by >>routine driver maintenance. >> >>While the card "works" you wont be able to set media-related features..so >>you really do need the fix. I've successfully fixed our version and its >>working nicely.....I've forwarded the info to DG so hopefully it will be >>patched soon. >> >>DB > >-- >Poul-Henning Kamp FreeBSD coreteam member >phk@FreeBSD.ORG "Real hackers run -current on their laptop." >FreeBSD -- It will take a long time before progress goes too far! > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 10:56:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 08CAA37BDEA for ; Mon, 27 Mar 2000 10:55:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA11530; Mon, 27 Mar 2000 20:55:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 13:47:49 CDT." <200003271852.NAA18460@etinc.com> Date: Mon, 27 Mar 2000 20:55:35 +0200 Message-ID: <11528.954183335@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003271852.NAA18460@etinc.com>, Dennis writes: >At 08:07 PM 3/27/00 +0200, Poul-Henning Kamp wrote: >> >>Dennis, >> >>You need to work with the maintainer of the driver on issues like >>this, and as you have found out that is David Greenman. > >Been there, done that...tired of waiting. What does one do when the >maintainers dont maintain if complaining isnt allowed? I just told you: >>If you have any issues regarding that, him or the result thereof, >>address your email to core. Your tone in this email didn't improve btw. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 11:26: 5 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 A7BD137BAAE for ; Mon, 27 Mar 2000 11:26:01 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA18569; Mon, 27 Mar 2000 14:26:24 -0500 (EST) Message-Id: <200003271926.OAA18569@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 14:22:03 -0500 To: dg@root.com From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <200003271836.KAA16040@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As for "thousands of people people suffering from a driver that is not >up-to-date", I think you are *way* overstating the breadth of the problem. >I'll also point out that hundreds of thousands of people find the fxp driver >a lifesaver and one of the best functioning network drivers in the source >tree. Your comments definately piss me off and definately provide for major >negative motivation as far as my interest in solving this problem is >concerned. Bludgeoning tactics like yours might sometimes work in business, >but they sure as hell don't work in free software development. > As said in previous mail, I'll implement a solution as soon as I can find >some time. I'm extremely busy these days and if I can somehow squeeze in some >quality development time inbetween multiple trips across te country, then >I will. Otherwise people will either have to use the patch I mailed out or >just wait. If you dont have time then perhaps someone else should do it. THATS the point. Its an important driver. People get upset when they can't run full-duplex mode. It makes linux MUCH more attractive when you can run your $39. card at twice the speed. Whether you are angry at me or not is no reason to punish the communiity. If you think that you are just doing this for me because I'm the only one with the nerve to complain then you dont understand your obligation to the user base. Plus I've already fixed it myself. So if you fix it its not for me at all. DB > >-DG > >David Greenman >Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org >Creator of high-performance Internet servers - http://www.terasolutions.com >Pave the road of life with opportunities. > > >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 Mon Mar 27 12: 1:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6750C37BD51; Mon, 27 Mar 2000 12:01:22 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Mar 2000 21:01:20 +0100 (BST) To: hackers@freebsd.org Cc: des@freebsd.org, pb@freebsd.org Subject: Linprocfs observation. X-Request-Do: Date: Mon, 27 Mar 2000 21:01:19 +0100 From: David Malone Message-ID: <200003272101.aa58489@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice that we've just gained a linprocfs which aims to provide a Linux style procfs for the Linux binary compatibility stuff. It looks quite neat, and provides lots of the odd files those linux programs go looking for. However... I haven't checked carefully, but I expect that the linprocfs code has the same problem as the FreeBSD procfs code, in that it can expose suid executables which would not usually be run 'cos they are in inaccessible directories. The "file" file was removed from FreeBSD's /proc code (in 4.0 and 5.0) because of this, but it is probably important for Linux emulation so it can't really be removed from the linprocfs code. I guess this probably warrants at least a note in the man page. Linux itself is not subject to this problem because it's exe file is a synthetic symlink pointing to the executable, not something which returns the executables actual vnode. Also, on Linux the symlink is only readable by the process' owner. This suggests the following possible work around: 1) Add a directory /linproc/pid/private which is only executable and readable by the process' owner. 2) Make the "exe" file in /linproc/pid/ a symlink to "./private/exe", which is the file which gives you the executables real vnode. I think this will give the same behavior as the Linux procfs, and expose less suid stuff. It would be necessary to do something very like this if we ever have to implement /linproc/pid/fd/xx. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 12:10:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1x.pvt.net (ns.pvt.net [194.149.105.18]) by hub.freebsd.org (Postfix) with ESMTP id B8ADB37C021 for ; Mon, 27 Mar 2000 12:10:03 -0800 (PST) (envelope-from milon.papezik@oskarmobil.cz) Received: from oskarmobil.cz (nat.ceskymobil.cz [194.149.122.193]) by ns1x.pvt.net (8.9.3/8.9.3) with ESMTP id WAA16591; Mon, 27 Mar 2000 22:09:19 +0200 Message-ID: <38DFCD74.620123EC@oskarmobil.cz> Date: Mon, 27 Mar 2000 23:07:00 +0200 From: Milon Papezik X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: cz, cs, en MIME-Version: 1.0 To: dg@root.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003271836.KAA16040@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > ... Hi David, you wrote that you have trouble finding a person with Intel 82559 based NIC (regular or onboard), I am willing to assist you as much as I can to solve this problem. I alredy looked at the code in FBSD v3.4R and tried to create workaround a patch for my card supplied by Compaq. I could not finish the patch for 3.4R as my task had to be finished and I choose to swap the card. The problem with this particular card is that it's detected as i82558 based card, but the code for reading PHY type from EEPROM doesn't work as it is i82559 based card with integrated PHY. This can be detected by reading PHY identification from PHY's regiters (as documented in Intel docs). At the moment I have a spare machine and the NIC available for testing. Please let me know if you are interested in my offer to test your patches to 4.0 driver? Cheers, Milon PS: I sent similar message to -hackers a month and half ago but I never got any answer back (yes/no is enough). -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 12:10:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lowrider.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 5257D37BCE5 for ; Mon, 27 Mar 2000 12:10:03 -0800 (PST) (envelope-from deimos@lowrider.lewman.org) Received: from localhost (deimos@localhost) by lowrider.lewman.org (8.9.3/8.9.3) with ESMTP id PAA01484; Mon, 27 Mar 2000 15:08:30 -0500 (EST) (envelope-from deimos@lowrider.lewman.org) Date: Mon, 27 Mar 2000 15:08:30 -0500 (EST) From: Andy To: Dennis Cc: dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003271926.OAA18569@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 Mon, 27 Mar 2000, Dennis wrote: > If you dont have time then perhaps someone else should do it. THATS the > point. > Plus I've already fixed it myself. So if you fix it its not for me at all. Since you appear to have fixed the problems and updated the code, would you like to submit it for review? -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | I have more humility in my little finger than you have in your whole ____BODY! -- from "Cerebus" #82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 12:54:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163]) by hub.freebsd.org (Postfix) with ESMTP id 3120537B720 for ; Mon, 27 Mar 2000 12:54:27 -0800 (PST) (envelope-from gcorcora@mhmail.mh.lucent.com) Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1]) by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA08239 for ; Mon, 27 Mar 2000 15:54:17 -0500 (EST) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA08078 for ; Mon, 27 Mar 2000 15:54:04 -0500 (EST) Received: from mhmail.mh.lucent.com by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id PAA22339; Mon, 27 Mar 2000 15:54:02 -0500 (EST) Message-ID: <38DFCB7D.C86550@mhmail.mh.lucent.com> Date: Mon, 27 Mar 2000 15:58:37 -0500 From: "Gary T. Corcoran" Reply-To: gcorcoran@lucent.com Organization: Lucent Microelectronics - Modem and Multimedia Systems X-Mailer: Mozilla 4.06 [en] (Win98; U) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: How to make a PCI network device loadable module? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to know how to make the network device driver I'm working on a loadable module. It's for a PCI device. I was unable to find any examples of PCI network modules under /sys/pci. The examples under /usr/share/examples/kld are not very helpful either for a PCI network device. It appears I need to add an xxx_load() routine, but what should it do? How and when does my xxx_probe() routine get called? How and when does my xxx_attach() routine get called? What macro do I use to tell the system my driver is a kld? That is, I was unable to find a "NETDEV_MODULE" macro that might be equivalent to the "CDEV_MODULE" macro in the example character device module code... I'm running FreeBSD 3.4. I'm not subscribed to the -hackers list, so please copy me on all replies. Thanks, Gary -- ======================================================= Gary Corcoran - Distinguished Member of Technical Staff Lucent Microelectronics - Modem & Multimedia Systems Communications Protocol & Driver Development Group "We make the drivers that make communications work" Email: gcorcoran@lucent.com ------------------------------------------------------- There are only two kinds of machines - those that fail little by little, and those that fail all at once. ======================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13: 1: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 89D0637BD76 for ; Mon, 27 Mar 2000 13:00:51 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.32.254]) by piranha.amis.net (Postfix) with ESMTP id C32745D22; Mon, 27 Mar 2000 23:00:48 +0200 (CEST) Date: Mon, 27 Mar 2000 23:00:46 +0200 (CEST) From: Blaz Zupan To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003271852.NAA18460@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 > Been there, done that...tired of waiting. What does one do when the > maintainers dont maintain if complaining isnt allowed? Fix it yourself. If you don't know how or don't have the time - tough luck. Buy a support contract or use a commercial OS. > Yes, lets silence the critics. Nice way to run an O/S. Of course! I have many issues with FreeBSD myself, but I don't run to this mailing list and complain the way you do - it's not the complaining itself, it's the attitude that comes with it. The point of open source operating systems is, that they are user-supported. Users _volunteer_ their spare time to work on the system, answer questions, etc. It seems like you expect that everybody is just waiting to fix your problem and drop all the other work they have. The day you realise that this is a volunteer effort and that _everyone_ involved has to work on it (including you), will be the day of enlightment for you. > Last time I asked a simple question as to whether this problem had been > fixed yet and I was told to figure it out myself. It seems that with the > freebsd-slackers the only was to get results is to emphasize the importance > of this to your user base. The fxp driver is "recommended" as the best > driver, yet maintaining it is a burden and complaining is not allowed. The "fxp" driver works just fine. I use it in all my servers and would recommend it anytime to anyone. You seem to have a problem with a specific version of the card and now expect the developer to drop all his work and everybody else to listen to your problem. > When is that BSDI "support" going to kick-in? When you start paying for it? Dennis, please don't take this personal, but you don't seem to get it - complaining does not help, it only pisses people off. You can either 1) colaborate with developers as much as you can and hope they will be able to fix your problem 2) fix the problem yourself 3) pay someone to fix the problem Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13: 3: 0 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 C166F37BC5E for ; Mon, 27 Mar 2000 13:02:55 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id PAA18818; Mon, 27 Mar 2000 15:39:46 -0500 (EST) Message-Id: <200003272039.PAA18818@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 15:35:24 -0500 To: Andy From: Dennis Subject: Re: Onboard Intel NIC Cc: dg@root.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200003271926.OAA18569@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:08 PM 3/27/00 -0500, Andy wrote: >On Mon, 27 Mar 2000, Dennis wrote: > >> If you dont have time then perhaps someone else should do it. THATS the >> point. > >> Plus I've already fixed it myself. So if you fix it its not for me at all. > > Since you appear to have fixed the problems and updated the code, >would you like to submit it for review? I would, except as we speak Poul-Henning Kamp is trying to have my posts censored,so they dont seem to want my help. Hint: Look at the netbsd driver, file name is i82557.c Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13: 3:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id B76C337BC5E for ; Mon, 27 Mar 2000 13:03:17 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.32.254]) by piranha.amis.net (Postfix) with ESMTP id 155455D14; Mon, 27 Mar 2000 23:03:16 +0200 (CEST) Date: Mon, 27 Mar 2000 23:03:15 +0200 (CEST) From: Blaz Zupan To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003271926.OAA18569@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 > If you dont have time then perhaps someone else should do it. THATS the > point. Sure. Nobody will complain if you start working on it! > Its an important driver. People get upset when they can't run full-duplex > mode. It makes linux MUCH more attractive when you can run your $39. card > at twice the speed. I run the Intel Etherexpress in full duplex without any problems. > Whether you are angry at me or not is no reason to punish the communiity. > If you think that you are just doing this for me because I'm the only one > with the nerve to complain then you dont understand your obligation to the > user base. OBLIGATION? Excuse me? > Plus I've already fixed it myself. So if you fix it its not for me at all. Have you contributed the fix to FreeBSD? I think I know the answer. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:14: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C0DDA37BD2B for ; Mon, 27 Mar 2000 13:13:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA43370; Mon, 27 Mar 2000 13:13:53 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 13:13:53 -0800 (PST) From: Matthew Dillon Message-Id: <200003272113.NAA43370@apollo.backplane.com> To: Dennis Cc: Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003271926.OAA18569@etinc.com> <200003272039.PAA18818@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 03:08 PM 3/27/00 -0500, Andy wrote: :>On Mon, 27 Mar 2000, Dennis wrote: :> :>> If you dont have time then perhaps someone else should do it. THATS the :>> point. :> :>> Plus I've already fixed it myself. So if you fix it its not for me at all. :> :> Since you appear to have fixed the problems and updated the code, :>would you like to submit it for review? : :I would, except as we speak Poul-Henning Kamp is trying to have my posts :censored,so they dont seem to want my help. : :Hint: Look at the netbsd driver, file name is i82557.c : :Dennis Dennis, if you've fixed the problem yourself and want to see it in the master source tree, please just email the patch to the list so DG can look at it. Even if it isn't the right fix, it should make the problem and solution crystal clear to DG. It makes no sense whatsoever to make someone else's life difficult by only giving 'hints' -- this is not a classroom, and most everyone here has a life outside of FreeBSD development they must attend to. Remember that this is an open-source project and the developers are unpaid. The only responsibility any given person has to the project is that which they impose upon themselves. Out of respect the person who wrote the driver should always get first crack at reviewing/fixing/updating it. If he doesn't have time, then other developersr will take up the slack. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:18:15 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 042BE37BCE8; Mon, 27 Mar 2000 13:18:12 -0800 (PST) (envelope-from imp@harmony.village.org) 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 OAA55658; Mon, 27 Mar 2000 14:18:09 -0700 (MST) (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 OAA99918; Mon, 27 Mar 2000 14:17:52 -0700 (MST) Message-Id: <200003272117.OAA99918@harmony.village.org> To: David Malone Subject: Re: Linprocfs observation. Cc: hackers@FreeBSD.ORG, des@FreeBSD.ORG, pb@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 21:01:19 +0100." <200003272101.aa58489@salmon.maths.tcd.ie> References: <200003272101.aa58489@salmon.maths.tcd.ie> Date: Mon, 27 Mar 2000 14:17:52 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003272101.aa58489@salmon.maths.tcd.ie> David Malone writes: : The "file" file was removed from FreeBSD's /proc code (in 4.0 and : 5.0) because of this, but it is probably important for Linux : emulation so it can't really be removed from the linprocfs code. : I guess this probably warrants at least a note in the man page. File was removed because it was a huge, gaping security hole. It was effectively hard link to the file in question and circumvented some of the usual security protections that the file would otherwise be protected by. : Linux itself is not subject to this problem because it's exe file : is a synthetic symlink pointing to the executable, not something : which returns the executables actual vnode. And that's why it is still in the tree. A symbolic link doesn't have the security issues that the hard link has. : Also, on Linux the : symlink is only readable by the process' owner. This suggests the : following possible work around: : 1) Add a directory /linproc/pid/private which is only : executable and readable by the process' owner. : 2) Make the "exe" file in /linproc/pid/ a symlink to : "./private/exe", which is the file which gives : you the executables real vnode. : I think this will give the same behavior as the Linux procfs, and : expose less suid stuff. It would be necessary to do something very : like this if we ever have to implement /linproc/pid/fd/xx. Why bother? No body should be using file/exe at all. It is a useless misfeature. What actually uses it? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:19:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id A763837BB9A for ; Mon, 27 Mar 2000 13:19:55 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA16743; Mon, 27 Mar 2000 13:13:20 -0800 (PST) Message-Id: <200003272113.NAA16743@implode.root.com> To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 14:22:03 EST." <200003271926.OAA18569@etinc.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 27 Mar 2000 13:13:20 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If you dont have time then perhaps someone else should do it. THATS the >point. PLEASE, someone else fix the driver!!! Please, please, please!!! There, did that help? Probably not. I don't know what point you're trying to make. The driver isn't fixed because noone to this point has had both the knowledge and time to fix it, not because I've been some sort of impediment. I have yet to see a real fix for the problem. A real fix requires detecting the type of SEEPROM (6 vs. 8bit address) and doing the right thing. If NetBSD has it working, then great - I suggest that someone look at what they do and form an appropriate fix. If that doesn't happen before I get some time to work on it, then I will when I do. >Its an important driver. People get upset when they can't run full-duplex >mode. It makes linux MUCH more attractive when you can run your $39. card >at twice the speed. Do you really think that whether some small number of Intel cards work correctly in full-duplex with FreeBSD or not will have *any* measurable effect on the attractiveness of FreeBSD vs. Linux? If that prevented someone from installing FreeBSD, then I might agree, but let's be realistic. >Whether you are angry at me or not is no reason to punish the communiity. How is me not doing free work punishing the community? The 'community' should be happy that the driver (and FreeBSD!) exist at all. >If you think that you are just doing this for me because I'm the only one >with the nerve to complain then you dont understand your obligation to the >user base. I do have an obligation, yes. I also have many other obligations. Like anyone with 5 times more to do than can be done in a day, I have to prioritize and do the really important things first and if there is any time left over to do "fun" stuff (like work on free software), then I do. Life hasn't been fun for me for quite awhile. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:21:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9DB6A37BD41 for ; Mon, 27 Mar 2000 13:21:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA12578; Mon, 27 Mar 2000 23:21:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dennis Cc: Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 15:35:24 CDT." <200003272039.PAA18818@etinc.com> Date: Mon, 27 Mar 2000 23:21:23 +0200 Message-ID: <12576.954192083@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003272039.PAA18818@etinc.com>, Dennis writes: >At 03:08 PM 3/27/00 -0500, Andy wrote: >>On Mon, 27 Mar 2000, Dennis wrote: >> >>> If you dont have time then perhaps someone else should do it. THATS the >>> point. >> >>> Plus I've already fixed it myself. So if you fix it its not for me at all. >> >> Since you appear to have fixed the problems and updated the code, >>would you like to submit it for review? > >I would, except as we speak Poul-Henning Kamp is trying to have my posts >censored,so they dont seem to want my help. I don't want them censored, I want the tagged ("Subject: [TROLL] bla bla") so that people can be warned not to take you at all serious. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:22:26 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 CC09537BE72 for ; Mon, 27 Mar 2000 13:22:22 -0800 (PST) (envelope-from imp@harmony.village.org) 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 OAA55675; Mon, 27 Mar 2000 14:22:21 -0700 (MST) (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 OAA99954; Mon, 27 Mar 2000 14:22:04 -0700 (MST) Message-Id: <200003272122.OAA99954@harmony.village.org> To: Dennis Subject: Re: Onboard Intel NIC Cc: Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 15:35:24 EST." <200003272039.PAA18818@etinc.com> References: <200003272039.PAA18818@etinc.com> <200003271926.OAA18569@etinc.com> Date: Mon, 27 Mar 2000 14:22:04 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003272039.PAA18818@etinc.com> Dennis writes: : I would, except as we speak Poul-Henning Kamp is trying to have my posts : censored,so they dont seem to want my help. Bullshit. I've not seen anything in phk's mail that suggests that he wants your posts censored. He merely requests that you conduct yourself in a civilized manner, like everybody else on the list is doing. And even if he did, he is not core. He doesn't speak for core, unless he says he is doing so explictly. He didn't say he didn't want your help. He merely stated he didn't want your rotten attitude. : Hint: Look at the netbsd driver, file name is i82557.c Hint: cvs diff -u after you've fixed this in your local sources. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 13:33:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 4876137C217; Mon, 27 Mar 2000 13:31:52 -0800 (PST) From: "Jonathan M. Bresler" To: dennis@etinc.com Cc: deimos@lowrider.lewman.org, dg@root.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <200003272039.PAA18818@etinc.com> (message from Dennis on Mon, 27 Mar 2000 15:35:24 -0500) Subject: Re: Onboard Intel NIC Message-Id: <20000327213152.4876137C217@hub.freebsd.org> Date: Mon, 27 Mar 2000 13:31:52 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis, Your statement is false. Poul-Henning has NOT asked me to filter you from the lists. No one has (recently?) asked me to filter you from the lists. I do not believe that I have ever filtered you from the lists. as postmaster, i am responsible for spam filtering and removing serious problem people from teh lists. In the past 5 or 6 years, i have filtered about 6 people total. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve JMB193 http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB > Delivered-To: freebsd-hackers@freebsd.org > X-Sender: dennis@etinc.com > X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 > Date: Mon, 27 Mar 2000 15:35:24 -0500 > From: Dennis > Cc: dg@root.com, freebsd-hackers@FreeBSD.ORG > References: <200003271926.OAA18569@etinc.com> > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Sender: owner-freebsd-hackers@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > At 03:08 PM 3/27/00 -0500, Andy wrote: > >On Mon, 27 Mar 2000, Dennis wrote: > > > >> If you dont have time then perhaps someone else should do it. THATS the > >> point. > > > >> Plus I've already fixed it myself. So if you fix it its not for me at all. > > > > Since you appear to have fixed the problems and updated the code, > >would you like to submit it for review? > > I would, except as we speak Poul-Henning Kamp is trying to have my posts > censored,so they dont seem to want my help. > > Hint: Look at the netbsd driver, file name is i82557.c > > Dennis > > > 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 Mon Mar 27 14: 9:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by hub.freebsd.org (Postfix) with ESMTP id E9C0837B52B for ; Mon, 27 Mar 2000 14:08:57 -0800 (PST) (envelope-from wigstah@akitanet.co.uk) Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id XAA48101; Mon, 27 Mar 2000 23:08:28 +0100 (BST) Date: Mon, 27 Mar 2000 23:08:28 +0100 (BST) From: Paul Robinson To: Blaz Zupan Cc: Dennis , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC 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, 27 Mar 2000, Blaz Zupan wrote: > > Been there, done that...tired of waiting. What does one do when the > > maintainers dont maintain if complaining isnt allowed? > > Fix it yourself. If you don't know how or don't have the time - tough > luck. Buy a support contract or use a commercial OS. Encore! Encore! What's the betting this guy has been weened on either MS or SunOS/Solaris in his past? :-) -- Paul Robinson - Developer/Systems Administrator @ Akitanet Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:25:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D341C37BB03; Mon, 27 Mar 2000 14:25:05 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Mar 2000 23:25:02 +0100 (BST) To: Warner Losh Cc: hackers@FreeBSD.ORG, des@FreeBSD.ORG, pb@FreeBSD.ORG Subject: Re: Linprocfs observation. In-reply-to: Your message of "Mon, 27 Mar 2000 14:17:52 PDT." <200003272117.OAA99918@harmony.village.org> X-Request-Do: Date: Mon, 27 Mar 2000 23:25:02 +0100 From: David Malone Message-ID: <200003272325.aa69356@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > File was removed because it was a huge, gaping security hole. It was > effectively hard link to the file in question and circumvented some of > the usual security protections that the file would otherwise be > protected by. I know - AFAIK I was the one who reported it ;-) > : Linux itself is not subject to this problem because it's exe file > : is a synthetic symlink pointing to the executable, not something > : which returns the executables actual vnode. > > And that's why it is still in the tree. A symbolic link doesn't have > the security issues that the hard link has. I think I wasn't clear. The real Linux code doesn't have this problem, but the code in /usr/src/sys/miscfs/linprocfs, which was committed to 4.0 and 5.0 two days ago does. > : Also, on Linux the > : symlink is only readable by the process' owner. This suggests the > : following possible work around: > : 1) Add a directory /linproc/pid/private which is only > : executable and readable by the process' owner. > : 2) Make the "exe" file in /linproc/pid/ a symlink to > : "./private/exe", which is the file which gives > : you the executables real vnode. > : I think this will give the same behavior as the Linux procfs, and > : expose less suid stuff. It would be necessary to do something very > : like this if we ever have to implement /linproc/pid/fd/xx. > > Why bother? No body should be using file/exe at all. It is a useless > misfeature. What actually uses it? I think Linux programs may actually use it, and it is included in the linprocfs code to allow them to operate. Looking quickly on a Redhat box here: turing% grep -l '/proc.*exe' /lib/* /bin/* /usr/bin/* /usr/local/bin/* /lib/ld-2.1.2.so /lib/ld-linux.so.2 /lib/libc-2.1.2.so /lib/libc.so.6 /bin/ash.static /bin/rpm /usr/bin/killall /usr/bin/libgtop_daemon /usr/bin/ltrace /usr/bin/rpm2cpio Given that libc is using it for something, it is probably important to provide a working one in linprocfs, preferably without the security hole! David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:29:39 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 9D68337BA2D; Mon, 27 Mar 2000 14:29:34 -0800 (PST) (envelope-from imp@harmony.village.org) 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 PAA55892; Mon, 27 Mar 2000 15:29:33 -0700 (MST) (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 PAA00547; Mon, 27 Mar 2000 15:29:16 -0700 (MST) Message-Id: <200003272229.PAA00547@harmony.village.org> To: David Malone Subject: Re: Linprocfs observation. Cc: hackers@FreeBSD.ORG, des@FreeBSD.ORG, pb@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 23:25:02 +0100." <200003272325.aa69356@salmon.maths.tcd.ie> References: <200003272325.aa69356@salmon.maths.tcd.ie> Date: Mon, 27 Mar 2000 15:29:16 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003272325.aa69356@salmon.maths.tcd.ie> David Malone writes: : > File was removed because it was a huge, gaping security hole. It was : > effectively hard link to the file in question and circumvented some of : > the usual security protections that the file would otherwise be : > protected by. : : I know - AFAIK I was the one who reported it ;-) So many bugs. It is hard to put a face on them at times :-) : > : Linux itself is not subject to this problem because it's exe file : > : is a synthetic symlink pointing to the executable, not something : > : which returns the executables actual vnode. : > : > And that's why it is still in the tree. A symbolic link doesn't have : > the security issues that the hard link has. : : I think I wasn't clear. The real Linux code doesn't have this problem, : but the code in /usr/src/sys/miscfs/linprocfs, which was committed to : 4.0 and 5.0 two days ago does. Ah. That's a good point. : Given that libc is using it for something, it is probably important : to provide a working one in linprocfs, preferably without the : security hole! Agreed. I'm happy with just making it a symlink. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:30:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id E9FCD37BED5 for ; Mon, 27 Mar 2000 14:30:31 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id RAA26052 for ; Mon, 27 Mar 2000 17:30:30 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Mar 2000 17:30:29 -0500 (EST) From: "Eric D. Futch" To: freebsd-hackers@freebsd.org Subject: gif and faith as kld... Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1041744430-954196229=:24832" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1041744430-954196229=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII This all started with wanting to play with IPv6 without rebooting. I forgot to add the gif and faith pseudo-device lines in my kernel config last time I was playing in it. I noticed that gif and faith interfaces don't exist as modules. After playing around with trying to make faith and gif (for IPv6) into modules, I managed to get a working if_faith.ko, which seems to work ok so far (i.e. didn't panic :)). I'm using an almost identical Makefile to create the if_gif.ko module, however, when I try to load it I get: # kldload /modules/if_gif.ko kldload: can't load /modules/if_gif.ko: Exec format error # kldstat Id Refs Address Size Name 1 4 0xc0100000 2c213c kernel 2 1 0xc14be000 4000 logo_saver.ko 21 1 0xc16f3000 2000 if_disc.ko 23 1 0xc16f0000 2000 if_faith.ko <--- :) Feel free to slap me around or pass the pointy hat where applicable. I have attached the Makefile and the make output from both modules. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" --0-1041744430-954196229=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="make.gif" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="make.gif" V2FybmluZzogT2JqZWN0IGRpcmVjdG9yeSBub3QgY2hhbmdlZCBmcm9tIG9y aWdpbmFsIC91c3Ivc3JjL3N5cy9tb2R1bGVzL2lmX2dpZg0KQCAtPiAvdXNy L3NyYy9zeXMNCm1hY2hpbmUgLT4gL3Vzci9zcmMvc3lzL2kzODYvaW5jbHVk ZQ0KZWNobyAiI2RlZmluZSBJTkVUIDEiID4gb3B0X2luZXQuaA0KZWNobyAi I2RlZmluZSBJTkVUNiAxIiA+IG9wdF9pbmV0Ni5oDQplY2hvICIjZGVmaW5l IE5HSUYgMSIgPiBnaWYuaA0KY2MgLU8gLXBpcGUgICAtRF9LRVJORUwgLVdh bGwgLVdyZWR1bmRhbnQtZGVjbHMgLVduZXN0ZWQtZXh0ZXJucyAtV3N0cmlj dC1wcm90b3R5cGVzICAtV21pc3NpbmctcHJvdG90eXBlcyAtV3BvaW50ZXIt YXJpdGggLVdpbmxpbmUgLVdjYXN0LXF1YWwgIC1mZm9ybWF0LWV4dGVuc2lv bnMgLWFuc2kgLURLTERfTU9EVUxFIC1ub3N0ZGluYyAtSS0gIC1JLiAtSUAg LUlALy4uL2luY2x1ZGUgLUkvdXNyL2luY2x1ZGUgIC1tcHJlZmVycmVkLXN0 YWNrLWJvdW5kYXJ5PTIgLWMgL3Vzci9zcmMvc3lzL21vZHVsZXMvaWZfZ2lm Ly4uLy4uL25ldC9pZl9naWYuYw0KZ2Vuc2V0ZGVmcyBpZl9naWYubw0KY2Mg LU8gLXBpcGUgICAtRF9LRVJORUwgLVdhbGwgLVdyZWR1bmRhbnQtZGVjbHMg LVduZXN0ZWQtZXh0ZXJucyAtV3N0cmljdC1wcm90b3R5cGVzICAtV21pc3Np bmctcHJvdG90eXBlcyAtV3BvaW50ZXItYXJpdGggLVdpbmxpbmUgLVdjYXN0 LXF1YWwgIC1mZm9ybWF0LWV4dGVuc2lvbnMgLWFuc2kgLURLTERfTU9EVUxF IC1ub3N0ZGluYyAtSS0gIC1JLiAtSUAgLUlALy4uL2luY2x1ZGUgLUkvdXNy L2luY2x1ZGUgIC1tcHJlZmVycmVkLXN0YWNrLWJvdW5kYXJ5PTIgLWMgc2V0 ZGVmMC5jDQpjYyAtTyAtcGlwZSAgIC1EX0tFUk5FTCAtV2FsbCAtV3JlZHVu ZGFudC1kZWNscyAtV25lc3RlZC1leHRlcm5zIC1Xc3RyaWN0LXByb3RvdHlw ZXMgIC1XbWlzc2luZy1wcm90b3R5cGVzIC1XcG9pbnRlci1hcml0aCAtV2lu bGluZSAtV2Nhc3QtcXVhbCAgLWZmb3JtYXQtZXh0ZW5zaW9ucyAtYW5zaSAt REtMRF9NT0RVTEUgLW5vc3RkaW5jIC1JLSAgLUkuIC1JQCAtSUAvLi4vaW5j bHVkZSAtSS91c3IvaW5jbHVkZSAgLW1wcmVmZXJyZWQtc3RhY2stYm91bmRh cnk9MiAtYyBzZXRkZWYxLmMNCmxkIC1Cc2hhcmVhYmxlICAtbyBpZl9naWYu a28gc2V0ZGVmMC5vIGlmX2dpZi5vIHNldGRlZjEubyAgDQo= --0-1041744430-954196229=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="make.faith" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="make.faith" V2FybmluZzogT2JqZWN0IGRpcmVjdG9yeSBub3QgY2hhbmdlZCBmcm9tIG9y aWdpbmFsIC91c3Ivc3JjL3N5cy9tb2R1bGVzL2lmX2ZhaXRoDQpAIC0+IC91 c3Ivc3JjL3N5cw0KbWFjaGluZSAtPiAvdXNyL3NyYy9zeXMvaTM4Ni9pbmNs dWRlDQplY2hvICIjZGVmaW5lIElORVQgMSIgPiBvcHRfaW5ldC5oDQplY2hv ICIjZGVmaW5lIElORVQ2IDEiID4gb3B0X2luZXQ2LmgNCmVjaG8gIiNkZWZp bmUgTkZBSVRIIDEiID4gZmFpdGguaA0KY2MgLU8gLXBpcGUgICAtRF9LRVJO RUwgLVdhbGwgLVdyZWR1bmRhbnQtZGVjbHMgLVduZXN0ZWQtZXh0ZXJucyAt V3N0cmljdC1wcm90b3R5cGVzICAtV21pc3NpbmctcHJvdG90eXBlcyAtV3Bv aW50ZXItYXJpdGggLVdpbmxpbmUgLVdjYXN0LXF1YWwgIC1mZm9ybWF0LWV4 dGVuc2lvbnMgLWFuc2kgLURLTERfTU9EVUxFIC1ub3N0ZGluYyAtSS0gIC1J LiAtSUAgLUlALy4uL2luY2x1ZGUgLUkvdXNyL2luY2x1ZGUgIC1tcHJlZmVy cmVkLXN0YWNrLWJvdW5kYXJ5PTIgLWMgL3Vzci9zcmMvc3lzL21vZHVsZXMv aWZfZmFpdGgvLi4vLi4vbmV0L2lmX2ZhaXRoLmMNCmdlbnNldGRlZnMgaWZf ZmFpdGgubw0KY2MgLU8gLXBpcGUgICAtRF9LRVJORUwgLVdhbGwgLVdyZWR1 bmRhbnQtZGVjbHMgLVduZXN0ZWQtZXh0ZXJucyAtV3N0cmljdC1wcm90b3R5 cGVzICAtV21pc3NpbmctcHJvdG90eXBlcyAtV3BvaW50ZXItYXJpdGggLVdp bmxpbmUgLVdjYXN0LXF1YWwgIC1mZm9ybWF0LWV4dGVuc2lvbnMgLWFuc2kg LURLTERfTU9EVUxFIC1ub3N0ZGluYyAtSS0gIC1JLiAtSUAgLUlALy4uL2lu Y2x1ZGUgLUkvdXNyL2luY2x1ZGUgIC1tcHJlZmVycmVkLXN0YWNrLWJvdW5k YXJ5PTIgLWMgc2V0ZGVmMC5jDQpjYyAtTyAtcGlwZSAgIC1EX0tFUk5FTCAt V2FsbCAtV3JlZHVuZGFudC1kZWNscyAtV25lc3RlZC1leHRlcm5zIC1Xc3Ry aWN0LXByb3RvdHlwZXMgIC1XbWlzc2luZy1wcm90b3R5cGVzIC1XcG9pbnRl ci1hcml0aCAtV2lubGluZSAtV2Nhc3QtcXVhbCAgLWZmb3JtYXQtZXh0ZW5z aW9ucyAtYW5zaSAtREtMRF9NT0RVTEUgLW5vc3RkaW5jIC1JLSAgLUkuIC1J QCAtSUAvLi4vaW5jbHVkZSAtSS91c3IvaW5jbHVkZSAgLW1wcmVmZXJyZWQt c3RhY2stYm91bmRhcnk9MiAtYyBzZXRkZWYxLmMNCmxkIC1Cc2hhcmVhYmxl ICAtbyBpZl9mYWl0aC5rbyBzZXRkZWYwLm8gaWZfZmFpdGgubyBzZXRkZWYx Lm8gIA0K --0-1041744430-954196229=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Makefile.gif" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="Makefile.gif" IyAkRnJlZUJTRCQNCg0KLlBBVEg6ICAkey5DVVJESVJ9Ly4uLy4uL25ldA0K S01PRD0gICBpZl9naWYNClNSQ1M9ICAgaWZfZ2lmLmMgb3B0X2luZXQuaCBv cHRfaW5ldDYuaCBnaWYuaA0KTk9NQU49DQoNCk5HSUY/PSAxDQoNCkNGTEFH Uys9ICR7UFJPVE9TfQ0KDQpvcHRfaW5ldC5oOg0KCWVjaG8gIiNkZWZpbmUg SU5FVCAxIiA+IG9wdF9pbmV0LmgNCg0Kb3B0X2luZXQ2Lmg6DQoJZWNobyAi I2RlZmluZSBJTkVUNiAxIiA+IG9wdF9pbmV0Ni5oDQoNCmdpZi5oOg0KCWVj aG8gIiNkZWZpbmUgTkdJRiAke05HSUZ9IiA+IGdpZi5oDQoNCi5pbmNsdWRl IDxic2Qua21vZC5taz4NCg== --0-1041744430-954196229=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Makefile.faith" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="Makefile.faith" IyAkRnJlZUJTRCQNCg0KLlBBVEg6ICAkey5DVVJESVJ9Ly4uLy4uL25ldA0K S01PRD0gICBpZl9mYWl0aA0KU1JDUz0gICBpZl9mYWl0aC5jIG9wdF9pbmV0 Lmggb3B0X2luZXQ2LmggZmFpdGguaA0KTk9NQU49DQoNCk5GQUlUSD89IDEN Cg0KQ0ZMQUdTKz0gJHtQUk9UT1N9DQoNCm9wdF9pbmV0Lmg6DQoJZWNobyAi I2RlZmluZSBJTkVUIDEiID4gb3B0X2luZXQuaA0KDQpvcHRfaW5ldDYuaDoN CgllY2hvICIjZGVmaW5lIElORVQ2IDEiID4gb3B0X2luZXQ2LmgNCg0KZmFp dGguaDoNCgllY2hvICIjZGVmaW5lIE5GQUlUSCAke05GQUlUSH0iID4gZmFp dGguaA0KDQouaW5jbHVkZSA8YnNkLmttb2QubWs+DQo= --0-1041744430-954196229=:24832-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:35:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (pyramid.cdrom.com [204.216.28.136]) by hub.freebsd.org (Postfix) with ESMTP id 3DCA137B6AB for ; Mon, 27 Mar 2000 14:35:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01373; Mon, 27 Mar 2000 14:38:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003272238.OAA01373@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Eric D. Futch" Cc: freebsd-hackers@freebsd.org Subject: Re: gif and faith as kld... In-reply-to: Your message of "Mon, 27 Mar 2000 17:30:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Mar 2000 14:38:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # kldload /modules/if_gif.ko > kldload: can't load /modules/if_gif.ko: Exec format error Check the console or system log, you should have a better diagnostic that includes the symbol that it wasn't able to resolve. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:42: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 98F2D37B84D; Mon, 27 Mar 2000 14:42:02 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id RAA28652; Mon, 27 Mar 2000 17:42:01 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Mar 2000 17:42:01 -0500 (EST) From: "Eric D. Futch" To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: gif and faith as kld... In-Reply-To: <200003272238.OAA01373@mass.cdrom.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 Ahh.. thanks for the quick reply... Mar 27 16:43:35 quake /kernel: link_elf: symbol in_gif_output undefined Mar 27 17:06:08 quake /kernel: link_elf: symbol in_gif_output undefined Mar 27 17:08:33 quake /kernel: link_elf: symbol in_gif_output undefined Mar 27 17:10:25 quake /kernel: link_elf: symbol in_gif_output undefined Gonna go sit in the corner now and think about that one :) -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Mon, 27 Mar 2000, Mike Smith wrote: >Check the console or system log, you should have a better diagnostic that >includes the symbol that it wasn't able to resolve. > >-- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 14:58:33 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 2C67F37B5C4 for ; Mon, 27 Mar 2000 14:58:28 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA19266; Mon, 27 Mar 2000 17:58:55 -0500 (EST) Message-Id: <200003272258.RAA19266@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 17:54:32 -0500 To: Paul Robinson , Blaz Zupan From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:08 PM 3/27/00 +0100, Paul Robinson wrote: >On Mon, 27 Mar 2000, Blaz Zupan wrote: > >> > Been there, done that...tired of waiting. What does one do when the >> > maintainers dont maintain if complaining isnt allowed? >> >> Fix it yourself. If you don't know how or don't have the time - tough >> luck. Buy a support contract or use a commercial OS. dont have to. Just go to Linux. It works there. or NetBSD. And thats exactly what people do. thats what you folks dont get. Your "fix it yourself" attitude drives all except hackers away. You cant sell freebsd if it works better than linux, what makes you think you can sell it if it doesnt work as well? Do you see tumbleweek in your future? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:16:27 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 2DFA337BA02 for ; Mon, 27 Mar 2000 15:16:22 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id SAA19315; Mon, 27 Mar 2000 18:16:52 -0500 (EST) Message-Id: <200003272316.SAA19315@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 27 Mar 2000 18:12:29 -0500 To: Warner Losh From: Dennis Subject: Re: Onboard Intel NIC Cc: Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200003272122.OAA99954@harmony.village.org> References: <200003272039.PAA18818@etinc.com> <200003271926.OAA18569@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:22 PM 3/27/00 -0700, Warner Losh wrote: >In message <200003272039.PAA18818@etinc.com> Dennis writes: >: I would, except as we speak Poul-Henning Kamp is trying to have my posts >: censored,so they dont seem to want my help. > >Bullshit. I've not seen anything in phk's mail that suggests that he >wants your posts censored. He merely requests that you conduct >yourself in a civilized manner, like everybody else on the list is >doing. His message to me: >No, not really, but now that I have warned you, I'm going to solicit >votes to filter you on your mailing lists. >My preference will be that the Subject line of all postings from >you get a prefix like "Subject: [TROLL]" but I'll settle with >having your posts discard if that is the consensus. > >And even if he did, he is not core. He doesn't speak for core, unless >he says he is doing so explictly. > >He didn't say he didn't want your help. He merely stated he didn't >want your rotten attitude. My "attitude" is irrelevant. I got called "lazy and incompetent" last week for simply asking if it had been fixed. The guy who asked the same question today didnt get flamed. So its not what is said, its who says it. > >: Hint: Look at the netbsd driver, file name is i82557.c > >Hint: cvs diff -u after you've fixed this in your local sources. I have other stuff in my sources for our bridge code that others wont want, which is why did I didnt put it up. Dennis Emerging Technologies, Inc. ---------------------------------------------------------------------------- --------- http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:26:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by hub.freebsd.org (Postfix) with ESMTP id A365437BD3F for ; Mon, 27 Mar 2000 15:25:05 -0800 (PST) (envelope-from wigstah@akitanet.co.uk) Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id AAA48730; Tue, 28 Mar 2000 00:24:43 +0100 (BST) Date: Tue, 28 Mar 2000 00:24:43 +0100 (BST) From: Paul Robinson To: Dennis Cc: Warner Losh , Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003272316.SAA19315@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 Mon, 27 Mar 2000, Dennis wrote: > So its not what is said, its who says it. No, that isn't true. As my Mum would say, it's not what you say, it's the *way* that you say it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:26:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id CA7F537B69D; Mon, 27 Mar 2000 15:25:25 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id SAA07588; Mon, 27 Mar 2000 18:25:24 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Mar 2000 18:25:24 -0500 (EST) From: "Eric D. Futch" To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gif and faith as kld... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1766922628-954199524=:24832" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1766922628-954199524=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII For those that care I now have a working if_faith.ko and if_gif.ko. Thanks to Mike. Makefile's are attached. To get it to work do this... cd /usr/src/sys/modules mkdir if_gif mkdir if_faith copy in my Makefile.gif to if_gif/Makefile copy in my Makefile.faith to if_faith/Makefile cd if_gif make depend all install cd if_faith make depend all install kldload each when necessary I'm not sure this is all you need or if it DTRT but it works for me :) Maybe someone can test/commit it if they want to, or I could send-pr. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Mon, 27 Mar 2000, Eric D. Futch wrote: >Ahh.. thanks for the quick reply... > >Mar 27 16:43:35 quake /kernel: link_elf: symbol in_gif_output undefined >Mar 27 17:06:08 quake /kernel: link_elf: symbol in_gif_output undefined >Mar 27 17:08:33 quake /kernel: link_elf: symbol in_gif_output undefined >Mar 27 17:10:25 quake /kernel: link_elf: symbol in_gif_output undefined > >Gonna go sit in the corner now and think about that one :) --0-1766922628-954199524=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Makefile.gif" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="Makefile.gif" IyAkRnJlZUJTRCQNCg0KLlBBVEg6CSR7LkNVUkRJUn0vLi4vLi4vbmV0DQou UEFUSDoJJHsuQ1VSRElSfS8uLi8uLi9uZXRpbmV0DQouUEFUSDoJJHsuQ1VS RElSfS8uLi8uLi9uZXRpbmV0Ng0KS01PRD0JaWZfZ2lmDQpTUkNTPQlpZl9n aWYuYyBpbl9naWYuYyBpbjZfZ2lmLmMgb3B0X2luZXQuaCBvcHRfaW5ldDYu aCBvcHRfbXJvdXRpbmcuaCBcDQoJZ2lmLmgNCk5PTUFOPQ0KDQpOR0lGPz0J MQ0KDQpDRkxBR1MrPSAke1BST1RPU30NCg0Kb3B0X2luZXQuaDoNCgllY2hv ICIjZGVmaW5lIElORVQgMSIgPiBvcHRfaW5ldC5oDQoNCm9wdF9pbmV0Ni5o Og0KCWVjaG8gIiNkZWZpbmUgSU5FVDYgMSIgPiBvcHRfaW5ldDYuaA0KDQpv cHRfbXJvdXRpbmcuaDoNCgllY2hvICIjZGVmaW5lIE1ST1VUSU5HIDEiID4g b3B0X21yb3V0aW5nLmgNCg0KZ2lmLmg6DQoJZWNobyAiI2RlZmluZSBOR0lG ICR7TkdJRn0iID4gZ2lmLmgNCg0KLmluY2x1ZGUgPGJzZC5rbW9kLm1rPg0K --0-1766922628-954199524=:24832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Makefile.faith" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="Makefile.faith" IyAkRnJlZUJTRCQNCg0KLlBBVEg6ICAkey5DVVJESVJ9Ly4uLy4uL25ldA0K S01PRD0gICBpZl9mYWl0aA0KU1JDUz0gICBpZl9mYWl0aC5jIG9wdF9pbmV0 Lmggb3B0X2luZXQ2LmggZmFpdGguaA0KTk9NQU49DQoNCk5GQUlUSD89IDEN Cg0KQ0ZMQUdTKz0gJHtQUk9UT1N9DQoNCm9wdF9pbmV0Lmg6DQoJZWNobyAi I2RlZmluZSBJTkVUIDEiID4gb3B0X2luZXQuaA0KDQpvcHRfaW5ldDYuaDoN CgllY2hvICIjZGVmaW5lIElORVQ2IDEiID4gb3B0X2luZXQ2LmgNCg0KZmFp dGguaDoNCgllY2hvICIjZGVmaW5lIE5GQUlUSCAke05GQUlUSH0iID4gZmFp dGguaA0KDQouaW5jbHVkZSA8YnNkLmttb2QubWs+DQo= --0-1766922628-954199524=:24832-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:26:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id E781437BD38 for ; Mon, 27 Mar 2000 15:25:37 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id PAA47366 for ; Mon, 27 Mar 2000 15:25:37 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id PAA13510 for ; Mon, 27 Mar 2000 15:25:36 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <38DFEDF0.BFCC1DD8@sftw.com> Date: Mon, 27 Mar 2000 15:25:36 -0800 From: Nick Sayer Reply-To: nsayer@kfu.com X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Colaberation invited -- ports/net/mpd-netgraph + pppoe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I friend of mine just got Pac$Bell Internet (see the story in -questions), and he uses PPPoE over DSL to connect to the net. /usr/sbin/ppp works just fine, but being the sort I am, I am dissatisfied with the solution, since there's still so much context switching involved (given that the equivalent to ng_ppp is still in userland). The much better solution, IMHO, is to add PPPoE support to ports/net/mpd-netgraph, and I have embarked on a course to do so. It's slow going, as it's my first real grope into netgraph in a big way (playing with ngctl and ksockets doesn't count). I am plenty happy to talk with anyone about this and it would be particularly helpful if someone who uses PPPoE could test the result, when it's ready (my friend is not inclined to be a tester for this sort of thing. The current solution is good enough for him). The eventual goal, of course, is to have a pair of machines run PPP over a cross-connect 10baseT cable. At the moment, however, call "origination" is favored. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:28:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 3DE2B37BA2D for ; Mon, 27 Mar 2000 15:28:43 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id B63B8197; Mon, 27 Mar 2000 15:28:40 -0800 (PST) Date: Mon, 27 Mar 2000 15:28:40 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-hackers@freebsd.org Subject: Re: Onboard Intel NIC Message-ID: <20000327152840.A8310@lunatic.oneinsane.net> Reply-To: Ron Rosson References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wigstah@akitanet.co.uk on Mon, Mar 27, 2000 at 11:08:28PM +0100 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.4-STABLE X-Moon: The Moon is Waning Gibbous (51% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 3:20PM up 4 days, 17:14, 1 user, load averages: 0.00, 0.00, 0.00 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000, Paul Robinson was heard blurting out: > On Mon, 27 Mar 2000, Blaz Zupan wrote: > > > > Been there, done that...tired of waiting. What does one do when the > > > maintainers dont maintain if complaining isnt allowed? > > > > Fix it yourself. If you don't know how or don't have the time - tough > > luck. Buy a support contract or use a commercial OS. > > > > Encore! Encore! > > What's the betting this guy has been weened on either MS or SunOS/Solaris > in his past? :-) > Ummm.... This is getting a little old. I am no programmer but read this list to get insight on what things may not work or what might work.. It has saved my BACKSIDE many times. I am also a user of ETinc hardware and am aware of Dennis. I am also like I said someone who does not code. So go FIX IT yourself attitude gets kinda old. It happens on #FreeBSD on efnet all too much. I guess what I am really getting at is these attacks in a public forum is not get anycode fixed and his just purely wasting bandwidth. A Simple I don't have the time to get to it. or a reason without being snotty about it should suffice. Throwing names and being childish does know one any could. Also does not help the project since all what we say is archived and searchable via the web. This is not pointed to anyone whatsoever but just in plain general as being part of the FreeBSD user base. Now can we get back to the card because I do know people that have these cards that do not work. (it seems to be of the onboard type). Sorry for the interruption -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------- "Outside of a dog, a book is a man's best friend. Inside of a dog it's too dark to read." - Groucho Marx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 15:42:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C12837B99A for ; Mon, 27 Mar 2000 15:42:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA44725; Mon, 27 Mar 2000 15:42:22 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 15:42:22 -0800 (PST) From: Matthew Dillon Message-Id: <200003272342.PAA44725@apollo.backplane.com> To: Dennis Cc: Warner Losh , Andy , dg@root.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003272039.PAA18818@etinc.com> <200003271926.OAA18569@etinc.com> <200003272316.SAA19315@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :My "attitude" is irrelevant. I got called "lazy and incompetent" last week :for simply asking if it had been fixed. The guy who asked the same question :today didnt get flamed. So its not what is said, its who says it. Attitude is significant, since you are dealing with people who are under no obligation to respond, and generalizing one bozos response and applying it to the entire group isn't going to help. Frankly speaking, you will get the same sort of response from linux-kernel as you got from the this one if you were to approach a linux bug in the same way. I'd tell you to go over there and try it but linux-kernel is still recovering from the utterly stupid memory overcommit thread and don't deserve a second flame war this soon. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 16:44:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kitab.cisco.com (dhcp-193-220.ietf.connect.com.au [169.208.193.220]) by hub.freebsd.org (Postfix) with ESMTP id 43D2B37B709; Mon, 27 Mar 2000 16:44:05 -0800 (PST) (envelope-from raj@cisco.com) Received: (from raj@localhost) by kitab.cisco.com (8.9.2/8.9.2) id QAA00511; Mon, 27 Mar 2000 16:44:19 -0800 (PST) (envelope-from raj) From: Richard Johnson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14560.98.259388.61429@kitab.cisco.com> Date: Mon, 27 Mar 2000 16:44:18 -0800 (PST) To: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Small addition to pccard.conf syntax (ioaddr option) X-Mailer: VM 6.74 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In booting, sleeping, and resuming my laptop using the Lucent wavelan card at IETF I found that pccardd didn't always allocate the ioaddr space correctly. I had a modem card in slot 0 and the wavelan card in slot 1. When I initially boot, it allocates io space for the modem card and then the wavelan card next. With the following: io 0x2f8-0x340 it allocates 0x2f8-0x300 for the modem and then 0x300-0x340 for the wavelan. This is fine. After sleeping and resuming, however, pccardd allocates the io space for the wavelan card first, which puts it at the wrong location in memory and the card can not init. correctly. Looking at pccardd source I notice that it will allocate the correct space if that was specified in the cis info on the card, but I don't see that being specified for this card. So, the card seems to need specifically allocated 0x300-0x340 but it doesn't say so in the cis information. I see this same situation wrt to my Xircom modem card as well. I finally just decided that it would be easiest to simply modify pccardd to allow specifying the "ioaddr" location in the configuration file. These diffs add the "ioaddr" keyword for card configuration information like so: card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" 10 ioaddr 0x300 insert echo Cabletron RoamAbout inserted insert /etc/pccard_ether wi0 remove echo Cabletron RoamAbout removed This always allocates the correct io space and always works just fine. These diffs are based on the version of pccardd which came with 3.1, but I don't think it's changed that much. It would be nice to have these changes, or something else giving this same functionality, in future versions of pccardd. (Or maybe there's a different way to force the iobase address? I haven't found it.) diff -c orig_pccardd/cardd.c pccardd/cardd.c *** orig_pccardd/cardd.c Mon Mar 27 15:28:01 2000 --- pccardd/cardd.c Mon Mar 27 15:25:45 2000 *************** *** 38,44 **** #include "cardd.h" static struct card_config *assign_driver(struct card *); ! static int assign_io(struct slot *); static int setup_slot(struct slot *); static void card_inserted(struct slot *); static void card_removed(struct slot *); --- 38,44 ---- #include "cardd.h" static struct card_config *assign_driver(struct card *); ! static int assign_io(struct slot *, struct card *); static int setup_slot(struct slot *); static void card_inserted(struct slot *); static void card_removed(struct slot *); *************** *** 135,140 **** --- 135,141 ---- { struct slotstate state; + logmsg("Slot change for card %s", sp->name); if (ioctl(sp->fd, PIOCGSTATE, &state)) { logerr("ioctl (PIOCGSTATE)"); return; *************** *** 224,230 **** read_ether(sp); if ((sp->config = assign_driver(cp)) == NULL) return; ! if (assign_io(sp)) { logmsg("Resource allocation failure for %s", sp->cis->manuf); return; } --- 225,231 ---- read_ether(sp); if ((sp->config = assign_driver(cp)) == NULL) return; ! if (assign_io(sp, cp)) { logmsg("Resource allocation failure for %s", sp->cis->manuf); return; } *************** *** 338,344 **** * configuration index selected. */ static int ! assign_io(struct slot *sp) { struct cis *cis; struct cis_config *cisconf, *defconf; --- 339,345 ---- * configuration index selected. */ static int ! assign_io(struct slot *sp, struct card *cd) { struct cis *cis; struct cis_config *cisconf, *defconf; *************** *** 409,414 **** --- 410,418 ---- * decode gives the size. */ sp->io.size = 1 << cp->io_addr; + + if (cd->ioaddr) + sp->io.addr = cd->ioaddr; if (sp->io.addr == 0) { int i = bit_fns(io_avail, IOPORTS, sp->io.size); diff -c orig_pccardd/file.c pccardd/file.c *** orig_pccardd/file.c Mon Mar 27 15:28:01 2000 --- pccardd/file.c Mon Mar 27 15:26:17 2000 *************** *** 52,57 **** --- 52,58 ---- "ether", /* 9 */ "insert", /* 10 */ "remove", /* 11 */ + "ioaddr", /* 12 */ 0 }; *************** *** 66,71 **** --- 67,73 ---- #define KWD_ETHER 9 #define KWD_INSERT 10 #define KWD_REMOVE 11 + #define KWD_IOADDR 12 struct flags { char *name; *************** *** 184,189 **** --- 186,192 ---- cp->version = vers; cp->reset_time = 50; cp->next = cards; + cp->ioaddr = 0; /* init. */ cards = cp; for (;;) { switch (keyword(next_tok())) { *************** *** 248,253 **** --- 251,259 ---- case KWD_REMOVE: /* remove */ addcmd(&cp->remove); + break; + case KWD_IOADDR: + cp->ioaddr = num_tok(); break; default: pusht = 1; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 16:52:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 53CD237B899 for ; Mon, 27 Mar 2000 16:52:26 -0800 (PST) (envelope-from giffunip@tutopia.com) Received: from tutopia.com ([200.41.110.74]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.6) with ESMTP id AAA2F4; Mon, 27 Mar 2000 19:51:51 -0500 Message-ID: <38E00231.6737320C@tutopia.com> Date: Mon, 27 Mar 2000 19:52:01 -0500 From: "Pedro F. Giffuni" Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003271926.OAA18569@etinc.com> <200003272039.PAA18818@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > ... > > > > Since you appear to have fixed the problems and updated the code, > >would you like to submit it for review? > > I would, except as we speak Poul-Henning Kamp is trying to have my posts > censored,so they dont seem to want my help. > > Hint: Look at the netbsd driver, file name is i82557.c > Perhaps instead of having this negative attitude towards the core team members you should file a PR like the rest of us mortals do. hint: http://www.FreeBSD.org/send-pr.html Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 17:37:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id CE5E037B887; Mon, 27 Mar 2000 17:37:08 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id KAA24256; Tue, 28 Mar 2000 10:37:10 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id KAA11105; Tue, 28 Mar 2000 10:37:05 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id KAA22716; Tue, 28 Mar 2000 10:37:04 +0900 (JST) To: efutch@nyct.net Cc: msmith@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gif and faith as kld... In-Reply-To: References: <200003272238.OAA01373@mass.cdrom.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328103805K.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 10:38:05 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ahh.. thanks for the quick reply... > > Mar 27 16:43:35 quake /kernel: link_elf: symbol in_gif_output undefined > Mar 27 17:06:08 quake /kernel: link_elf: symbol in_gif_output undefined > Mar 27 17:08:33 quake /kernel: link_elf: symbol in_gif_output undefined > Mar 27 17:10:25 quake /kernel: link_elf: symbol in_gif_output undefined > > Gonna go sit in the corner now and think about that one :) in_gif_output() is defined in netinet/in_gif.c, and the files are only used when either of INET and gif are specified in config. Same thing applies to netinet6/in6_gif.c. from sys/conf/files: netinet/in_gif.c optional gif inet netinet6/in6_gif.c optional gif inet6 So should these also be used in the kld module? Cheers, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 18: 1:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 8846D37B631 for ; Mon, 27 Mar 2000 18:01:53 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id VAA03578; Mon, 27 Mar 2000 21:01:47 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Mar 2000 21:01:47 -0500 (EST) From: "Eric D. Futch" To: Yoshinobu Inoue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gif and faith as kld... In-Reply-To: <20000328103805K.shin@nd.net.fujitsu.co.jp> 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 fixed this obvious problem in the latest message I sent with new Makefile's. Note that there might be some side-effect of making gif into a kernel module. When I was using the gif kernel module I couldn't ping6 to anywhere. Now that it's compiled directly into the kernel I can. I have to do more testing I guess. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Tue, 28 Mar 2000, Yoshinobu Inoue wrote: > >in_gif_output() is defined in netinet/in_gif.c, and the files >are only used when either of INET and gif are specified in config. >Same thing applies to netinet6/in6_gif.c. > >from sys/conf/files: > netinet/in_gif.c optional gif inet > netinet6/in6_gif.c optional gif inet6 > >So should these also be used in the kld module? > >Cheers, >Yoshinobu Inoue > > >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 Mon Mar 27 18:25:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 972C637B7A0 for ; Mon, 27 Mar 2000 18:25:32 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id LAA05157; Tue, 28 Mar 2000 11:25:34 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id LAA06474; Tue, 28 Mar 2000 11:25:29 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id LAA24367; Tue, 28 Mar 2000 11:25:29 +0900 (JST) To: efutch@nyct.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gif and faith as kld... In-Reply-To: References: <20000328103805K.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328112629Q.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 11:26:29 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 50 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I fixed this obvious problem in the latest message I sent with new > Makefile's. Sorry, I received those mails in reversed order. > Note that there might be some side-effect of making gif into > a kernel module. When I was using the gif kernel module I couldn't ping6 > to anywhere. Now that it's compiled directly into the kernel I can. I > have to do more testing I guess. Ah, I noticed that gif routines need to be defiend in protosw, and they are defined like below with "#ifdef NGIF" directive. in netinet/in_gif.c #if NGIF > 0 { SOCK_RAW, &inet6domain, IPPROTO_IPV4, PR_ATOMIC|PR_ADDR, in6_gif_input,0, 0, 0, 0, 0, 0, 0, 0, &nousrreqs }, { SOCK_RAW, &inet6domain, IPPROTO_IPV6, PR_ATOMIC|PR_ADDR, in6_gif_input,0, 0, 0, 0, 0, 0, 0, 0, &nousrreqs }, #endif /* GIF */ in netinet6/in_gif.c #if NGIF > 0 { SOCK_RAW, &inet6domain, IPPROTO_IPV4, PR_ATOMIC|PR_ADDR, in6_gif_input,0, 0, 0, 0, 0, 0, 0, 0, &nousrreqs }, { SOCK_RAW, &inet6domain, IPPROTO_IPV6, PR_ATOMIC|PR_ADDR, in6_gif_input,0, 0, 0, 0, 0, 0, 0, 0, &nousrreqs }, #endif /* GIF */ Some consideration like in ip_mroute.c might be necessary. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 18:58: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id EBCC437B6B6 for ; Mon, 27 Mar 2000 18:57:57 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id VAA12379; Mon, 27 Mar 2000 21:57:54 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Mar 2000 21:57:53 -0500 (EST) From: "Eric D. Futch" To: Yoshinobu Inoue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gif and faith as kld... In-Reply-To: <20000328112629Q.shin@nd.net.fujitsu.co.jp> 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, 28 Mar 2000, Yoshinobu Inoue wrote: >Sorry, I received those mails in reversed order. > Not a problem. >Ah, I noticed that gif routines need to be defiend in protosw, >and they are defined like below with "#ifdef NGIF" directive. > [snip] > > >Some consideration like in ip_mroute.c might be necessary. > Ok. This part is beyond what I understand, which unfortunately, isn't all that much :). I'm not sure what needs to be done. I'm upgrading another computer in the office here to 4.0 so I can test this some more, since the computer I tried it on originally is somewhat important. >Yoshinobu Inoue -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 19:42:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id BA93E37B71F for ; Mon, 27 Mar 2000 19:42:40 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id TAA17969; Mon, 27 Mar 2000 19:36:02 -0800 (PST) Message-Id: <200003280336.TAA17969@implode.root.com> To: Milon Papezik Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 23:07:00 +0200." <38DFCD74.620123EC@oskarmobil.cz> From: David Greenman Reply-To: dg@root.com Date: Mon, 27 Mar 2000 19:36:01 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >At the moment I have a spare machine >and the NIC available for testing. > >Please let me know if you are interested >in my offer to test your patches to 4.0 driver? Thanks, Milon. I've attached patches which I believe will fix the problem as seen with the Compaq cards/motherboards, SuperMicro motherboards, and certain newer Pro/100+ cards. Please test and let me know if they work for you. I've tested this with (Compaq and Pro/100+) cards that some FreeBSD users shipped to me a few months ago when the problem was first noticed, and the driver now works fine with those. The algorithm for sizing the SEEPROM was taken from the NetBSD version of the driver. Thanks for your patience. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. Index: if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.77 diff -c -r1.77 if_fxp.c *** if_fxp.c 1999/09/30 19:03:12 1.77 --- if_fxp.c 2000/03/28 02:58:41 *************** *** 232,237 **** --- 232,238 ---- static int fxp_add_rfabuf __P((struct fxp_softc *, struct mbuf *)); static int fxp_mdi_read __P((struct fxp_softc *, int, int)); static void fxp_mdi_write __P((struct fxp_softc *, int, int, int)); + static void fxp_autosize_eeprom __P((struct fxp_softc *)); static void fxp_read_eeprom __P((struct fxp_softc *, u_int16_t *, int, int)); static int fxp_attach_common __P((struct fxp_softc *, u_int8_t *)); *************** *** 748,753 **** --- 749,759 ---- } /* + * Find out how large of an SEEPROM we have. + */ + fxp_autosize_eeprom(sc); + + /* * Get info about the primary PHY */ fxp_read_eeprom(sc, (u_int16_t *)&data, 6, 1); *************** *** 802,807 **** --- 808,883 ---- } /* + * From NetBSD: + * + * Figure out EEPROM size. + * + * 559's can have either 64-word or 256-word EEPROMs, the 558 + * datasheet only talks about 64-word EEPROMs, and the 557 datasheet + * talks about the existance of 16 to 256 word EEPROMs. + * + * The only known sizes are 64 and 256, where the 256 version is used + * by CardBus cards to store CIS information. + * + * The address is shifted in msb-to-lsb, and after the last + * address-bit the EEPROM is supposed to output a `dummy zero' bit, + * after which follows the actual data. We try to detect this zero, by + * probing the data-out bit in the EEPROM control register just after + * having shifted in a bit. If the bit is zero, we assume we've + * shifted enough address bits. The data-out should be tri-state, + * before this, which should translate to a logical one. + * + * Other ways to do this would be to try to read a register with known + * contents with a varying number of address bits, but no such + * register seem to be available. The high bits of register 10 are 01 + * on the 558 and 559, but apparently not on the 557. + * + * The Linux driver computes a checksum on the EEPROM data, but the + * value of this checksum is not very well documented. + */ + static void + fxp_autosize_eeprom(sc) + struct fxp_softc *sc; + { + u_int16_t reg; + int x; + + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, FXP_EEPROM_EECS); + /* + * Shift in read opcode. + */ + for (x = 3; x > 0; x--) { + if (FXP_EEPROM_OPC_READ & (1 << (x - 1))) { + reg = FXP_EEPROM_EECS | FXP_EEPROM_EEDI; + } else { + reg = FXP_EEPROM_EECS; + } + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, reg); + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, + reg | FXP_EEPROM_EESK); + DELAY(1); + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, reg); + DELAY(1); + } + /* + * Shift in address. + * Wait for the dummy zero following a correct address shift. + */ + for (x = 1; x <= 8; x++) { + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, FXP_EEPROM_EECS); + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, + FXP_EEPROM_EECS | FXP_EEPROM_EESK); + DELAY(1); + if ((CSR_READ_2(sc, FXP_CSR_EEPROMCONTROL) & FXP_EEPROM_EEDO) == 0) + break; + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, FXP_EEPROM_EECS); + DELAY(1); + } + CSR_WRITE_2(sc, FXP_CSR_EEPROMCONTROL, 0); + DELAY(1); + sc->eeprom_size = x; + } + /* * Read from the serial EEPROM. Basically, you manually shift in * the read opcode (one bit at a time) and then shift in the address, * and then you shift out the data (all of this one bit at a time). *************** *** 839,845 **** /* * Shift in address. */ ! for (x = 6; x > 0; x--) { if ((i + offset) & (1 << (x - 1))) { reg = FXP_EEPROM_EECS | FXP_EEPROM_EEDI; } else { --- 915,921 ---- /* * Shift in address. */ ! for (x = sc->eeprom_size; x > 0; x--) { if ((i + offset) & (1 << (x - 1))) { reg = FXP_EEPROM_EECS | FXP_EEPROM_EEDI; } else { Index: if_fxpvar.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v retrieving revision 1.9 diff -c -r1.9 if_fxpvar.h *** if_fxpvar.h 1999/09/30 19:03:12 1.9 --- if_fxpvar.h 2000/03/28 02:56:29 *************** *** 67,72 **** --- 67,73 ---- int phy_primary_addr; /* address of primary PHY */ int phy_primary_device; /* device type of primary PHY */ int phy_10Mbps_only; /* PHY is 10Mbps-only device */ + int eeprom_size; /* size of serial EEPROM */ }; /* Macros to ease CSR access. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 19:46:54 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 7C00037B582; Mon, 27 Mar 2000 19:46:47 -0800 (PST) (envelope-from imp@harmony.village.org) 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 UAA56890; Mon, 27 Mar 2000 20:46:45 -0700 (MST) (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 UAA02345; Mon, 27 Mar 2000 20:46:28 -0700 (MST) Message-Id: <200003280346.UAA02345@harmony.village.org> To: Richard Johnson Subject: Re: Small addition to pccard.conf syntax (ioaddr option) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 16:44:18 PST." <14560.98.259388.61429@kitab.cisco.com> References: <14560.98.259388.61429@kitab.cisco.com> Date: Mon, 27 Mar 2000 20:46:28 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14560.98.259388.61429@kitab.cisco.com> Richard Johnson writes: : I finally just decided that it would be easiest to simply modify : pccardd to allow specifying the "ioaddr" location in the configuration : file. These diffs add the "ioaddr" keyword for card configuration : information like so: I'd rather not do this. It is a move in the wrong direction. I'd like to see things move more into the kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 19:53:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kitab.cisco.com (dhcp-193-220.ietf.connect.com.au [169.208.193.220]) by hub.freebsd.org (Postfix) with ESMTP id 3B98A37B5F6; Mon, 27 Mar 2000 19:53:14 -0800 (PST) (envelope-from raj@cisco.com) Received: (from raj@localhost) by kitab.cisco.com (8.9.2/8.9.2) id TAA00757; Mon, 27 Mar 2000 19:53:14 -0800 (PST) (envelope-from raj) From: Richard Johnson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14560.11433.930491.310675@kitab.cisco.com> Date: Mon, 27 Mar 2000 19:53:13 -0800 (PST) To: Warner Losh Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Small addition to pccard.conf syntax (ioaddr option) In-Reply-To: <200003280346.UAA02345@harmony.village.org> References: <14560.98.259388.61429@kitab.cisco.com> <200003280346.UAA02345@harmony.village.org> X-Mailer: VM 6.74 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <14560.98.259388.61429@kitab.cisco.com> Richard Johnson writes: > : I finally just decided that it would be easiest to simply modify > : pccardd to allow specifying the "ioaddr" location in the configuration > : file. These diffs add the "ioaddr" keyword for card configuration > : information like so: > > I'd rather not do this. It is a move in the wrong direction. I'd > like to see things move more into the kernel. > > Warner Fine with me as long as there's a way to do it. If we could get the ioaddr information from the driver definition in the kernel and use that, I'd be satisfied. Afterall, I already have: device wi0 at isa? port 0x300 net irq 10 flags 0x1 which obviously specifies the ioaddr as "0x300" right there. That should be sufficient, but currently it's not. Same thing goes for the irq. /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 19:59:13 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 5E91037BD9F; Mon, 27 Mar 2000 19:59:06 -0800 (PST) (envelope-from imp@harmony.village.org) 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 UAA56934; Mon, 27 Mar 2000 20:59:04 -0700 (MST) (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 UAA02471; Mon, 27 Mar 2000 20:58:46 -0700 (MST) Message-Id: <200003280358.UAA02471@harmony.village.org> To: Richard Johnson Subject: Re: Small addition to pccard.conf syntax (ioaddr option) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 19:53:13 PST." <14560.11433.930491.310675@kitab.cisco.com> References: <14560.11433.930491.310675@kitab.cisco.com> <14560.98.259388.61429@kitab.cisco.com> <200003280346.UAA02345@harmony.village.org> Date: Mon, 27 Mar 2000 20:58:46 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14560.11433.930491.310675@kitab.cisco.com> Richard Johnson writes: : Fine with me as long as there's a way to do it. If we could get the : ioaddr information from the driver definition in the kernel and use : that, I'd be satisfied. Afterall, I already have: : : device wi0 at isa? port 0x300 net irq 10 flags 0x1 : : which obviously specifies the ioaddr as "0x300" right there. That : should be sufficient, but currently it's not. Same thing goes for the : irq. Hmmmm. It would have to be something like device wi0 at pccard? port 0x300 irq 10 flags 0x1 but that won't work in 4.x, nor in 3.x since pccards are outside config space in 3.x (well, kinda). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 20: 5: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kitab.cisco.com (dhcp-193-220.ietf.connect.com.au [169.208.193.220]) by hub.freebsd.org (Postfix) with ESMTP id 068E937BCEF; Mon, 27 Mar 2000 20:05:02 -0800 (PST) (envelope-from raj@cisco.com) Received: (from raj@localhost) by kitab.cisco.com (8.9.2/8.9.2) id UAA00771; Mon, 27 Mar 2000 20:04:16 -0800 (PST) (envelope-from raj) From: Richard Johnson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14560.12095.629999.492194@kitab.cisco.com> Date: Mon, 27 Mar 2000 20:04:15 -0800 (PST) To: Warner Losh Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Small addition to pccard.conf syntax (ioaddr option) In-Reply-To: <200003280358.UAA02471@harmony.village.org> References: <14560.11433.930491.310675@kitab.cisco.com> <14560.98.259388.61429@kitab.cisco.com> <200003280346.UAA02345@harmony.village.org> <200003280358.UAA02471@harmony.village.org> X-Mailer: VM 6.74 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <14560.11433.930491.310675@kitab.cisco.com> Richard Johnson writes: > Hmmmm. It would have to be something like > device wi0 at pccard? port 0x300 irq 10 flags 0x1 > but that won't work in 4.x, nor in 3.x since pccards are outside > config space in 3.x (well, kinda). > > Warner I'm currently running 3.1 and my system is configured this way currently. I realize that I need to upgrade to 4.0 but haven't done so yet. /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 20:27:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 38AF237BA28 for ; Mon, 27 Mar 2000 20:27:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA05985; Mon, 27 Mar 2000 20:27:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Dennis Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Mon, 27 Mar 2000 13:47:49 EST." <200003271852.NAA18460@etinc.com> Date: Mon, 27 Mar 2000 20:26:59 -0800 Message-ID: <5982.954217619@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Been there, done that...tired of waiting. What does one do when the > maintainers dont maintain if complaining isnt allowed? Fix it yourself. You know that already though and have known it for years, so we can safely assume that this is simply more of the usual Dennis emotion-over-logic behavior which has made his business such a resounding success. > Yes, lets silence the critics. Nice way to run an O/S. Silencing critics isn't the objective. Silencing Dennis would be nice though. He never says anything worth hearing and would appear to be more in love with seeing his name in print than with actual productive communication. Perhaps Dennis should just take a long walk off a short pier and make everyone's life a whole lot easier, including Dennis' - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 21:20:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id 3FE5A37BB7A for ; Mon, 27 Mar 2000 21:20:27 -0800 (PST) (envelope-from ziggy@panix.com) Received: from panix.com (panix.com [166.84.0.226]) by mail2.panix.com (Postfix) with ESMTP id DBF3315675; Tue, 28 Mar 2000 00:20:25 -0500 (EST) Received: (from ziggy@localhost) by panix.com (8.8.5/8.8.5/PanixN2.0) id AAA24881; Tue, 28 Mar 2000 00:20:25 -0500 (EST) From: Message-Id: <200003280520.AAA24881@panix.com> Subject: Problem installing 3.4-RELEASE: IDE Disk Geometry To: freebsd-hackers@freebsd.org Date: Tue, 28 Mar 2000 00:20:25 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Apologies if this question has been asked before; I couldn't seem to find any answers in the bug database. I've got a new BP6 dual Celeron configuration with a 20GB IBM HD. The BIOS reports the geometry as follows: 2495 cylinders 255 heads 63 sectors ---- 400082175 total blocks For some reason, fdisk cannot determine that during the install, and it finds a bogus geometry, sometimes adding up to 2GB, other times adding up to 4GB. Once I fire up the emergency shell and try to configure the geometry by hand on tty4, this is the only geometry that comes up: 65536 cylinders 1 head 63 sectors ----- 4128768 blocks When I reset the disk geometry in the graphical fdisk from sysinstall, the geometry appears to be reset, but the number of blocks available to allocate is unchanged (4M blocks). When I reset the geometry on tty4 using the CLI fdisk, the geometry reverts to 64K/1/63. Any way to work around this and allocate the full 20GB to freebsd? Thanks, -- Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 21:31:18 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 91E3B37BD2B; Mon, 27 Mar 2000 21:31:11 -0800 (PST) (envelope-from imp@harmony.village.org) 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 WAA57220; Mon, 27 Mar 2000 22:31:10 -0700 (MST) (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 WAA03455; Mon, 27 Mar 2000 22:30:52 -0700 (MST) Message-Id: <200003280530.WAA03455@harmony.village.org> To: Richard Johnson Subject: Re: Small addition to pccard.conf syntax (ioaddr option) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 20:04:15 PST." <14560.12095.629999.492194@kitab.cisco.com> References: <14560.12095.629999.492194@kitab.cisco.com> <14560.11433.930491.310675@kitab.cisco.com> <14560.98.259388.61429@kitab.cisco.com> <200003280346.UAA02345@harmony.village.org> <200003280358.UAA02471@harmony.village.org> Date: Mon, 27 Mar 2000 22:30:52 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14560.12095.629999.492194@kitab.cisco.com> Richard Johnson writes: : I'm currently running 3.1 and my system is configured this way : currently. I realize that I need to upgrade to 4.0 but haven't done : so yet. I wasn't prompting you to upgrade. Just letting you know the lay of the land. Minor nits will be corrected in 3.x. minor features (maybe major ones) will be added to 4.x. Major breakage will happen in -current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 27 22: 7:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B801937BD7A for ; Mon, 27 Mar 2000 22:07:40 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA25528; Mon, 27 Mar 2000 23:07:31 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38E04C8F.3213BC43@softweyr.com> Date: Mon, 27 Mar 2000 23:09:19 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ron Rosson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <20000327152840.A8310@lunatic.oneinsane.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ron 'The InSaNe One' Rosson wrote: > > Ummm.... This is getting a little old. I am no programmer but read this > list to get insight on what things may not work or what might work.. It > has saved my BACKSIDE many times. I am also a user of ETinc hardware and > am aware of Dennis. I am also like I said someone who does not code. So > go FIX IT yourself attitude gets kinda old. It happens on #FreeBSD on > efnet all too much. So you agree that you and Dennis have some legal and/or moral ground to stand on in DEMANDING that I and others donate our own personal time to you for free, simply because you're incapable of fixing something your- self? This argument has NOT been about whether the fxp driver needs to be fixed, but rather whether Dennis or anyone can DEMAND time from FreeBSD developers as opposed to asking them politely or proposing some remuneration so they can afford to dedicate time to an individual problem. I think my stance on this is pretty clear, but just in case you haven't gotten the message, those of you who think you have some RIGHT to DEMAND my time can stuff it. -- "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 Mon Mar 27 23:40:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 8CB8437BB57 for ; Mon, 27 Mar 2000 23:40:26 -0800 (PST) (envelope-from kheuer@gwdu60.gwdg.de) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.9.2/8.9.2) with ESMTP id JAA21945; Tue, 28 Mar 2000 09:39:11 +0200 (CEST) (envelope-from kheuer@gwdu60.gwdg.de) Date: Tue, 28 Mar 2000 09:39:11 +0200 (CEST) From: Konrad Heuer To: p_a_r Cc: hackers@FreeBSD.ORG Subject: Re: BSD VS BDS In-Reply-To: <81491281.2.1636@mx1-12.onmedia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000, p_a_r wrote: > Can anyone tell me the differens in FreeBSD and NetBSD. I would like=20 > to set up 2 internet servers whitch one should i take? Well, there's some risk to answer the question - someone may feel his/her favourite os to be treated inadequately. The most important strength of NetBSD is its availability on many different hardware platforms. If you plan to set up your servers on Intel or DECalpha software, FreeBSD might do better for you. For example, FreeBSD supports multi-processor systems, NetBSD does not. The FreeBSD install program is more user-friendly. Both, FreeBSD and NetBSD, are very solid os; but my experience is not to buy too cheap hardware for servers. The last times I set up server systems I decided to spend some more money to buy Dell hardware to run FreeBSD on, and the systems are exceedingly stable. Before, I used cheaper hardware and observed too often spontaneous reboots under heavy load I could not explain. Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 0:15: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 3D4F037BB28 for ; Tue, 28 Mar 2000 00:14:57 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id AAA13420; Tue, 28 Mar 2000 00:11:29 -0800 (PST) Date: Tue, 28 Mar 2000 00:11:28 -0800 From: Brooks Davis To: Konrad Heuer Cc: p_a_r , hackers@FreeBSD.ORG Subject: Re: BSD VS BDS Message-ID: <20000328001128.A10961@orion.ac.hmc.edu> References: <81491281.2.1636@mx1-12.onmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from kheuer@gwdu60.gwdg.de on Tue, Mar 28, 2000 at 09:39:11AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 09:39:11AM +0200, Konrad Heuer wrote: > > The most important strength of NetBSD is its availability on many > different hardware platforms. If you plan to set up your servers on Intel > or DECalpha software, FreeBSD might do better for you. For example, > FreeBSD supports multi-processor systems, NetBSD does not. The FreeBSD > install program is more user-friendly. Just FYI, NetBSD does now have early SMP support. Initial x86 SMP code was commited Feb 22. Obviously, you probably don't want to go running a high-availibility server application on SMP code that's only a month old, but it's coming along. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 0:19:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web110.yahoomail.com (web110.yahoomail.com [205.180.60.80]) by hub.freebsd.org (Postfix) with SMTP id 7F4A637B58A for ; Tue, 28 Mar 2000 00:19:16 -0800 (PST) (envelope-from dyeske@yahoo.com) Received: (qmail 25477 invoked by uid 60001); 28 Mar 2000 08:19:07 -0000 Message-ID: <20000328081907.25476.qmail@web110.yahoomail.com> Received: from [192.172.226.145] by web110.yahoomail.com; Tue, 28 Mar 2000 00:19:07 PST Date: Tue, 28 Mar 2000 00:19:07 -0800 (PST) From: David Yeske Subject: hard drive problems 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 I am getting a nasty error and I would like to resolve it. I know my hard drive is "ok" according to a couple of different tests including Western Digital DLT 2.2. Here is the error and after that is my dmesg. ad0: UDMA ICRC READ ERROR blk# 3500173 retrying ad0: UDMA ICRC READ ERROR blk# 3500173 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #4: Sun Mar 26 17:24:17 EST 2000 root@stuff:/usr/src/sys/compile/KERNEL Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 127004672 (124028K bytes) Preloaded elf kernel "kernel" at 0xc02f9000. 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 pci1: at 0.0 irq 11 ohci0: mem 0xdffff000-0xdfffffff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.00/1.00, addr 2 uhub1: 4 ports with 4 removable, bus powered ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 3, iclass 3/1 ums0: 4 buttons and Z dir. isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xdf80-0xdf9f,0xdbe4-0xdbe7,0xdfa8-0xdfaf,0xdfe4-0xdfe7,0xdff0-0xdff7 irq 5 at device 14.0 on pci0 atapci1: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 pci0: (vendor=0x1274, dev=0x1371) at 16.0 irq 11 fxp0: port 0xde80-0xdebf mem 0xdfe00000-0xdfefffff,0xdfffe000-0xdfffefff irq 11 at device 18.0 on pci0 fxp0: Ethernet address 00:d0:b7:49:9e:a8 fxp0: supplying EUI64: 00:d0:b7:ff:fe:49:9e:a8 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-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> 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/1 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 ata1-master: Aladdin: two atapi devices on this channel, no DMA acd0: CD-RW at ata1-master using PIO4 ata1-slave: Aladdin: two atapi devices on this channel, no DMA afd0: 120MB [963/8/32] at ata1-slave using PIO2 Mounting root from ufs:/dev/ad0s2a fxp0: starting DAD for fe80:0001::02d0:b7ff:fe49:9ea8 fxp0: DAD complete for fe80:0001::02d0:b7ff:fe49:9ea8 - no duplicates found ad0: UDMA ICRC READ ERROR blk# 3500173 retrying ad0: UDMA ICRC READ ERROR blk# 3500173 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709 retrying ad0: UDMA ICRC READ ERROR blk# 3499709ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode __________________________________________________ Do You Yahoo!? Talk to your friends online 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 Mar 28 0:26:11 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 3EF6E37BD65 for ; Tue, 28 Mar 2000 00:26:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA65235; Tue, 28 Mar 2000 10:26:03 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200003280826.KAA65235@freebsd.dk> Subject: Re: hard drive problems In-Reply-To: <20000328081907.25476.qmail@web110.yahoomail.com> from David Yeske at "Mar 28, 2000 00:19:07 am" To: dyeske@yahoo.com (David Yeske) Date: Tue, 28 Mar 2000 10:26:03 +0200 (CEST) Cc: freebsd-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 David Yeske wrote: > > ad0: UDMA ICRC READ ERROR blk# 3500173 retrying > ad0: UDMA ICRC READ ERROR blk# 3500173 retrying > ad0: UDMA ICRC READ ERROR blk# 3499709 retrying > ad0: UDMA ICRC READ ERROR blk# 3499709 retrying > ad0: UDMA ICRC READ ERROR blk# 3499709 retrying > ad0: UDMA ICRC READ ERROR blk# 3499709ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA > falling back to PIO mode You are having problems with the communication between drive and controller. Check you cabeling, it is likely a bad cable or you have it close to something that disturbs the signalling ie the powersupply or some of the switchmode stuff on the motherboard... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 0:26:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 7BCA137BD82 for ; Tue, 28 Mar 2000 00:26:10 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 736513E25; Tue, 28 Mar 2000 10:26:09 +0200 (CEST) Date: Tue, 28 Mar 2000 10:26:09 +0200 From: Jesper Skriver To: Brooks Davis Cc: Konrad Heuer , p_a_r , hackers@FreeBSD.ORG Subject: Re: BSD VS BDS Message-ID: <20000328102609.D38550@skriver.dk> References: <81491281.2.1636@mx1-12.onmedia.com> <20000328001128.A10961@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000328001128.A10961@orion.ac.hmc.edu>; from brooks@one-eyed-alien.net on Tue, Mar 28, 2000 at 12:11:28AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 12:11:28AM -0800, Brooks Davis wrote: > On Tue, Mar 28, 2000 at 09:39:11AM +0200, Konrad Heuer wrote: > > > > The most important strength of NetBSD is its availability on many > > different hardware platforms. If you plan to set up your servers on Intel > > or DECalpha software, FreeBSD might do better for you. For example, > > FreeBSD supports multi-processor systems, NetBSD does not. The FreeBSD > > install program is more user-friendly. > > Just FYI, NetBSD does now have early SMP support. Initial x86 SMP code > was commited Feb 22. Obviously, you probably don't want to go running a > high-availibility server application on SMP code that's only a month > old, but it's coming along. I was under the assumption that NetBSD's SMP code only initializes the second CPU, but never actually uses it for anything ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 2:45:29 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 4187937B679; Tue, 28 Mar 2000 02:45:22 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA24539; Tue, 28 Mar 2000 12:45:17 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: David Malone Cc: hackers@freebsd.org, pb@freebsd.org Subject: Re: Linprocfs observation. References: <200003272101.aa58489@salmon.maths.tcd.ie> From: Dag-Erling Smorgrav Date: 28 Mar 2000 12:45:16 +0200 In-Reply-To: David Malone's message of "Mon, 27 Mar 2000 21:01:19 +0100" Message-ID: Lines: 17 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 David Malone writes: > I haven't checked carefully, but I expect that the linprocfs code > has the same problem as the FreeBSD procfs code, in that it can > expose suid executables which would not usually be run 'cos they > are in inaccessible directories. That is indeed correct, and a severe oversight on my part. > 2) Make the "exe" file in /linproc/pid/ a symlink to > "./private/exe", which is the file which gives > you the executables real vnode. Sounds good. I'll get to it. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 2:53: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gilgamesch.bik-gmbh.de (T1-Hansenet.BIK-GmbH.de [192.76.134.246]) by hub.freebsd.org (Postfix) with ESMTP id 2301437B58E for ; Tue, 28 Mar 2000 02:52:55 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id MAA35779; Tue, 28 Mar 2000 12:51:37 +0200 (MET DST) Date: Tue, 28 Mar 2000 12:51:37 +0200 From: Martin Cracauer To: p_a_r Cc: hackers@FreeBSD.ORG Subject: Re: BSD VS BDS Message-ID: <20000328125137.A33556@cons.org> References: <81491281.2.1636@mx1-12.onmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <81491281.2.1636@mx1-12.onmedia.com>; from p_a_r@goplay.com on Mon, Mar 27, 2000 at 06:10:01AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <81491281.2.1636@mx1-12.onmedia.com>, p_a_r wrote: > > Can anyone tell me the differens in FreeBSD and NetBSD. I would like > to set up 2 internet servers whitch one should i take? As long as you can't tell by yourself, you are usually better off with FreeBSD, since it is easier to install and has more resources to support new users (handbook, people on mailinglists, user groups/people in your town). I think it is technically superiour in most ways that matter for me, but seem from an observer coming from Linux (or worse), that is not as relevant as the first point. As a side note, if you choose FreeBSD, take 4.0, not 3.4. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 3: 8:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web110.yahoomail.com (web110.yahoomail.com [205.180.60.80]) by hub.freebsd.org (Postfix) with SMTP id EA4AE37BE5D for ; Tue, 28 Mar 2000 03:08:33 -0800 (PST) (envelope-from dyeske@yahoo.com) Received: (qmail 7267 invoked by uid 60001); 28 Mar 2000 11:08:29 -0000 Message-ID: <20000328110829.7266.qmail@web110.yahoomail.com> Received: from [192.172.226.145] by web110.yahoomail.com; Tue, 28 Mar 2000 03:08:29 PST Date: Tue, 28 Mar 2000 03:08:29 -0800 (PST) From: David Yeske Subject: working together 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 I just started to notice a little hostility. Please feel free to flame me all you want, but do it in private. One of the best things that freebsd has is the teamwork. People from all over the world working together for a common belief. One day I will be part of a large software project, but until then I am going to help out other people any way I can. I am going to give them fish and teach them how to fish if I can. I think freebsd has a really bad "unofficial" support problem. One day there will be happy friendly people who are willing to help people online, and over other media like internet phone type systems, etc... Let's keep working together, it is the best thing we can do :)... __________________________________________________ Do You Yahoo!? Talk to your friends online 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 Mar 28 3:22:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web124.yahoomail.com (web124.yahoomail.com [205.180.60.192]) by hub.freebsd.org (Postfix) with SMTP id 0F4E437B61F for ; Tue, 28 Mar 2000 03:22:11 -0800 (PST) (envelope-from dyeske@yahoo.com) Received: (qmail 22986 invoked by uid 60001); 28 Mar 2000 11:22:08 -0000 Message-ID: <20000328112208.22985.qmail@web124.yahoomail.com> Received: from [192.172.226.145] by web124.yahoomail.com; Tue, 28 Mar 2000 03:22:08 PST Date: Tue, 28 Mar 2000 03:22:08 -0800 (PST) From: David Yeske Subject: onboard intel 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 I have an onboard intel chipset fxp0 and an intel management 100 adaptor. I have not gotten the error that is being discussed, but I am trying to make it netboot. I would like to help out with the problem everyone is having. Do I need to run a particular version and configuration of freebsd? I also have an occiliscope, and various other tools to see if it is a hardware issue. Regards, David Yeske __________________________________________________ Do You Yahoo!? Talk to your friends online 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 Mar 28 6:25: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8A1DB37B606 for ; Tue, 28 Mar 2000 06:24:56 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12Zwun-000AFX-00; Tue, 28 Mar 2000 16:24:18 +0200 From: Sheldon Hearn To: Johan Karlsson Cc: Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Thu, 23 Mar 2000 09:21:50 +0100." <200003230821.JAA27093@numeri.campus.luth.se> Date: Tue, 28 Mar 2000 16:24:17 +0200 Message-ID: <39402.954253457@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Mar 2000 09:21:50 +0100, Johan Karlsson wrote: > Before this is commited please have a look at the PR kern/17536 > which addresses a similar thing. When using the patch you provide on that PR, what does the How-To-Repeat do? The more detail you can give in your answer, the better. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 7:19: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 988B437C115 for ; Tue, 28 Mar 2000 07:18:59 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 8E6C7197; Tue, 28 Mar 2000 07:18:57 -0800 (PST) Date: Tue, 28 Mar 2000 07:18:57 -0800 From: Ron Rosson To: freebsd-hackers@freebsd.org Subject: Re: Onboard Intel NIC Message-ID: <20000328071857.A21087@lunatic.oneinsane.net> Reply-To: Ron Rosson References: <20000327152840.A8310@lunatic.oneinsane.net> <38E04C8F.3213BC43@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E04C8F.3213BC43@softweyr.com>; from wes@softweyr.com on Mon, Mar 27, 2000 at 11:09:19PM -0700 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.4-STABLE X-Moon: The Moon is Waning Crescent (45% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 7:04AM up 5 days, 8:57, 1 user, load averages: 0.01, 0.02, 0.00 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000, Wes Peters was heard blurting out: > Ron 'The InSaNe One' Rosson wrote: > > > > Ummm.... This is getting a little old. I am no programmer but read this > > list to get insight on what things may not work or what might work.. It > > has saved my BACKSIDE many times. I am also a user of ETinc hardware and > > am aware of Dennis. I am also like I said someone who does not code. So > > go FIX IT yourself attitude gets kinda old. It happens on #FreeBSD on > > efnet all too much. > > So you agree that you and Dennis have some legal and/or moral ground to > stand on in DEMANDING that I and others donate our own personal time to > you for free, simply because you're incapable of fixing something your- > self? > > This argument has NOT been about whether the fxp driver needs to be fixed, > but rather whether Dennis or anyone can DEMAND time from FreeBSD developers > as opposed to asking them politely or proposing some remuneration so they > can afford to dedicate time to an individual problem. > > I think my stance on this is pretty clear, but just in case you haven't > gotten the message, those of you who think you have some RIGHT to DEMAND > my time can stuff it. > I guess my wording was off a little. I guess the point I was tring to make was missed. It is the go fix it yourself attitude I guess that gets me sometimes in both the mailing lists and IRC. There is some people in the user base that can not code but are able to find issues on there systems and would like to share them with either of the forums mentioned. I guess the better answer than the "Go fix it yourself" would be "Please submit a PR". This way both the project and the party involved can track the progress. TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------- Voice on telephone to man seated at his computer: Thank you for calling the tech support hotline. If your computer becomes obsolete while you're holding, press 1 to reach our sales department. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 7:32:48 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 0D8A037B55D for ; Tue, 28 Mar 2000 07:32:42 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA21626; Tue, 28 Mar 2000 10:33:24 -0500 (EST) Message-Id: <200003281533.KAA21626@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 28 Mar 2000 10:28:53 -0500 To: Blaz Zupan From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200003271926.OAA18569@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Its an important driver. People get upset when they can't run full-duplex >> mode. It makes linux MUCH more attractive when you can run your $39. card >> at twice the speed. > >I run the Intel Etherexpress in full duplex without any problems. obviously not the one that has the error. Are you paying attention? > >> Whether you are angry at me or not is no reason to punish the communiity. >> If you think that you are just doing this for me because I'm the only one >> with the nerve to complain then you dont understand your obligation to the >> user base. > >OBLIGATION? Excuse me? > >> Plus I've already fixed it myself. So if you fix it its not for me at all. > >Have you contributed the fix to FreeBSD? I think I know the answer. I passed on the info to DG on how to fix it. Work I do belongs to my company because they pay me to do it. I know few of you understand that, So unless you want to attach the "copyright Emerging Technologies" to the driver you cant use it. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 7:52:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 1352937B54E for ; Tue, 28 Mar 2000 07:52:22 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.32.254]) by piranha.amis.net (Postfix) with ESMTP id 59D525D0B; Tue, 28 Mar 2000 17:52:16 +0200 (CEST) Date: Tue, 28 Mar 2000 17:52:16 +0200 (CEST) From: Blaz Zupan To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003281533.KAA21626@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 > >I run the Intel Etherexpress in full duplex without any problems. > obviously not the one that has the error. Are you paying attention? Of course I do, I just wanted to point out that you are generalizing. "The Intel Etherexpress does not work on FreeBSD" is not true - it works for me. There are SOME cards that don't work. > >Have you contributed the fix to FreeBSD? I think I know the answer. > I passed on the info to DG on how to fix it. Work I do belongs to my > company because they pay me to do it. I know few of you understand that, So > unless you want to attach the "copyright Emerging Technologies" to the > driver you cant use it. Now I really don't understand you. You demand others to work for you for free ("Hey I have this problem, everybody listen up and immediately start working on fixing it! Hey, nobody listens, so FreeBSD sux, Linux rox!") You don't want to contribute anything back yourself (you or your company). So you expect others to do what you don't want to do yourself. Is that correct? Yes, I also work for a company (an ISP) and all the work I do on FreeBSD (or other projects) *is* being contributed back to those. We use FreeBSD (for free, obviously) and we "pay" for it by contributing back what little we can. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 7:59:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id 0813037C1F0 for ; Tue, 28 Mar 2000 07:59:37 -0800 (PST) (envelope-from geoffr@is.co.za) Received: from hermwas.is.co.za (hermwas.is.co.za [196.23.0.8]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id RAA23818 for ; Tue, 28 Mar 2000 17:59:34 +0200 Received: (from geoffr@localhost) by hermwas.is.co.za (8.9.3/8.9.3) id RAA12143 for hackers@freebsd.org; Tue, 28 Mar 2000 17:59:34 +0200 (SAT) Date: Tue, 28 Mar 2000 17:59:33 +0200 From: Geoff Rehmet To: hackers@freebsd.org Subject: panic in tcp_output.c Message-ID: <20000328175933.A12122@hermwas.is.co.za> Reply-To: Geoff Rehmet Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've recently run into a panic in tcp_output.c (after Jonathon's latest commit, it seems), whereby, if I try to open a connection to a server on my local machine, I get a panic in line 540 of tcp_output.c. e.g.: telnet localhost 80 will cause the panic. I ahev not had much time to investigate yet, and I'm also in the process of reverting to the GENERIC config file, to rebuild my config after all the changes that have come into 5.0. I am also rebuilding with "INET6" enabled, and will see if that tickles the panic. Has anyone else run into this? Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za, geoff@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 8:56:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from incandescent.firedrake.org (incandescent.firedrake.org [195.157.96.1]) by hub.freebsd.org (Postfix) with ESMTP id B77F337C1E0 for ; Tue, 28 Mar 2000 08:56:32 -0800 (PST) (envelope-from float@firedrake.org) Received: from float by incandescent.firedrake.org with local (Exim 2.05 #1 (Debian)) id 12ZzHz-0001qv-00; Tue, 28 Mar 2000 17:56:23 +0100 Date: Tue, 28 Mar 2000 17:56:23 +0100 From: void To: Ron Rosson Cc: freebsd-hackers@freebsd.org Subject: Re: Onboard Intel NIC Message-ID: <20000328175623.A6362@firedrake.org> References: <20000327152840.A8310@lunatic.oneinsane.net> <38E04C8F.3213BC43@softweyr.com> <20000328071857.A21087@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <20000328071857.A21087@lunatic.oneinsane.net>; from insane@lunatic.oneinsane.net on Tue, Mar 28, 2000 at 07:18:57AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 07:18:57AM -0800, Ron Rosson wrote: > > It is the go fix it yourself attitude I guess that gets me sometimes in > both the mailing lists and IRC. There is some people in the user base > that can not code but are able to find issues on there systems and would > like to share them with either of the forums mentioned. I am one such person, and I don't seem to get flamed or told to fix it myself. Probably because I try not to be disrespectful of the people doing the work. > I guess the better answer than the "Go fix it yourself" would be "Please > submit a PR". Plenty of people said that to Dennis too. He seems to be more interested in making some kind of point than in getting anything fixed. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 9:57:36 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 A2E3637BFCC for ; Tue, 28 Mar 2000 09:57:28 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA59633; Tue, 28 Mar 2000 10:57:22 -0700 (MST) (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 KAA07345; Tue, 28 Mar 2000 10:57:02 -0700 (MST) Message-Id: <200003281757.KAA07345@harmony.village.org> To: Dennis Subject: Re: Onboard Intel NIC Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 28 Mar 2000 10:28:53 EST." <200003281533.KAA21626@etinc.com> References: <200003281533.KAA21626@etinc.com> <200003271926.OAA18569@etinc.com> Date: Tue, 28 Mar 2000 10:57:02 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003281533.KAA21626@etinc.com> Dennis writes: : I passed on the info to DG on how to fix it. Work I do belongs to my : company because they pay me to do it. I know few of you understand that, So : unless you want to attach the "copyright Emerging Technologies" to the : driver you cant use it. You should negotiate a better deal with your company. The deal I got here was that work I do on my own time belongs to me. Further, any work that I do for the comapny that the company (or at least my boss) believes will benefit the company by being in the base FreeBSD gets put into FreeBSD (with the usual approvals, caveats, etc). There's lots of code that I work on that will never be in FreeBSD because the hardware for it is so specialized we have the only instances of it. So I understand IP issues with one's employer. Patches are generally small enough that many employers don't care to claim exclusive rights to them. Oh well, everybody's employer is different. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 9:57:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0073137C023 for ; Tue, 28 Mar 2000 09:57:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA53022; Tue, 28 Mar 2000 09:57:27 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 09:57:27 -0800 (PST) From: Matthew Dillon Message-Id: <200003281757.JAA53022@apollo.backplane.com> To: Dennis Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003271926.OAA18569@etinc.com> <200003281533.KAA21626@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :>Have you contributed the fix to FreeBSD? I think I know the answer. : :I passed on the info to DG on how to fix it. Work I do belongs to my :company because they pay me to do it. I know few of you understand that, So :unless you want to attach the "copyright Emerging Technologies" to the :driver you cant use it. : :db Dennis, half the people on the list work for large companies or startups. If your company actually believes that witholding a simple bug fix is SOP, then it's one very screwed up company. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 10: 1:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4292A37B57C for ; Tue, 28 Mar 2000 10:01:06 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12ZyTi-000Dwt-00; Tue, 28 Mar 2000 17:04:26 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12ZyTi-0007pb-00; Tue, 28 Mar 2000 17:04:26 +0100 Date: Tue, 28 Mar 2000 17:04:26 +0100 From: Ben Smithurst To: Dennis Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC Message-ID: <20000328170426.C86036@strontium.scientia.demon.co.uk> References: <200003271926.OAA18569@etinc.com> <200003281533.KAA21626@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003281533.KAA21626@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > obviously not the one that has the error. Are you paying attention? DG has just committed a fix for this. Are *YOU* paying attention? > I passed on the info to DG on how to fix it. Work I do belongs to my > company because they pay me to do it. I know few of you understand that, So > unless you want to attach the "copyright Emerging Technologies" to the > driver you cant use it. Right, so you're not willing to share code you write because it's how you make your living (this is fair enough), but have the cheek to complain at DG when he doesn't fix the driver because he's too busy doing things to earn his living? The word "hypocrite" springs to mind. You'll be glad to know you've inspired me to investigate Mutt's killfiling rules though. HAND. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 11:14:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id 9336037BD60 for ; Tue, 28 Mar 2000 11:14:26 -0800 (PST) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id OAA10735; Tue, 28 Mar 2000 14:14:20 -0500 (EST) To: hackers@freeBSD.org Subject: DJB: FreeBSD4 alt MTA trick considered harmful From: Chris Shenton Date: 28 Mar 2000 14:14:19 -0500 Message-ID: Lines: 29 User-Agent: Gnus/5.0803 (Gnus v5.8.3) 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 Saw this on a qmail list. DJB's not got the best bedside manner, but he's pretty good about preventing loss or damage to mail. What about supporting his /etc/mta implementation instead? --Chris (not the poster below) From: "D. J. Bernstein" Subject: Re: FYI: FreeBSD 4 and alternate MTAs To: qmail@list.cr.yp.to Date: 19 Mar 2000 21:05:18 -0000 Chris Johnson writes: > It's very nice, and does away with the ugly symlinks. It does away with symlinks by inventing its own pointless file-based symlink format. It then needs an extra program to interpret that file. That program is, as it turns out, unreliable at high loads. If the kernel is low on file descriptors at the wrong moment then the program runs sendmail! What a disaster. Metzger should be ashamed of himself. See http://cr.yp.to/etc-mta.html for a simpler, faster, _correct_ configuration mechanism that doesn't try to reinvent the filesystem. Please encourage your OS vendor to support /etc/mta, not mailer.conf. ---Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 11:23:29 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 5381737BA4D for ; Tue, 28 Mar 2000 11:23:26 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA22806; Tue, 28 Mar 2000 14:24:05 -0500 (EST) Message-Id: <200003281924.OAA22806@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 28 Mar 2000 14:20:59 -0500 To: Ben Smithurst From: Dennis Subject: Re: Onboard Intel NIC Cc: hackers@freebsd.org In-Reply-To: <20000328170426.C86036@strontium.scientia.demon.co.uk> References: <200003281533.KAA21626@etinc.com> <200003271926.OAA18569@etinc.com> <200003281533.KAA21626@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:04 PM 3/28/00 +0100, you wrote: >Dennis wrote: > >> obviously not the one that has the error. Are you paying attention? > >DG has just committed a fix for this. Are *YOU* paying attention? Good, then we can end this stupid thread. If you fellows put as much time into freebsd as you do flaming me we wouldnt need this crap. :-) DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 12:19:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 4873137C023 for ; Tue, 28 Mar 2000 12:19:54 -0800 (PST) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA03490; Tue, 28 Mar 2000 12:19:39 -0800 (PST) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id MAA11058; Tue, 28 Mar 2000 12:19:49 -0800 (PST) Message-Id: <200003282019.MAA11058@papermill.wrs.com> To: Dennis Cc: hackers@FreeBSD.ORG From: David Holloway Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Tue, 28 Mar 2000 14:20:59 EST." <200003281924.OAA22806@etinc.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Tue, 28 Mar 2000 12:19:49 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It takes two to flame, really it does. In message <200003281924.OAA22806@etinc.com>, Dennis writes: >At 05:04 PM 3/28/00 +0100, you wrote: >>Dennis wrote: >> >>> obviously not the one that has the error. Are you paying attention? >> >>DG has just committed a fix for this. Are *YOU* paying attention? > >Good, then we can end this stupid thread. > >If you fellows put as much time into freebsd as you do flaming me we >wouldnt need this crap. :-) > >DB > > >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 Mar 28 13: 1:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id B912437BE3F for ; Tue, 28 Mar 2000 13:01:46 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id NAA48214; Tue, 28 Mar 2000 13:01:40 -0800 (PST) (envelope-from ulf) Date: Tue, 28 Mar 2000 13:01:40 -0800 From: Ulf Zimmermann To: Ron Rosson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC Message-ID: <20000328130140.A95709@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <20000327152840.A8310@lunatic.oneinsane.net> <38E04C8F.3213BC43@softweyr.com> <20000328071857.A21087@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000328071857.A21087@lunatic.oneinsane.net>; from insane@lunatic.oneinsane.net on Tue, Mar 28, 2000 at 07:18:57AM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 07:18:57AM -0800, Ron Rosson wrote: > On Mon, 27 Mar 2000, Wes Peters was heard blurting out: > > > Ron 'The InSaNe One' Rosson wrote: > > > > > > Ummm.... This is getting a little old. I am no programmer but read this > > > list to get insight on what things may not work or what might work.. It > > > has saved my BACKSIDE many times. I am also a user of ETinc hardware and > > > am aware of Dennis. I am also like I said someone who does not code. So > > > go FIX IT yourself attitude gets kinda old. It happens on #FreeBSD on > > > efnet all too much. > > > > So you agree that you and Dennis have some legal and/or moral ground to > > stand on in DEMANDING that I and others donate our own personal time to > > you for free, simply because you're incapable of fixing something your- > > self? > > > > This argument has NOT been about whether the fxp driver needs to be fixed, > > but rather whether Dennis or anyone can DEMAND time from FreeBSD developers > > as opposed to asking them politely or proposing some remuneration so they > > can afford to dedicate time to an individual problem. > > > > I think my stance on this is pretty clear, but just in case you haven't > > gotten the message, those of you who think you have some RIGHT to DEMAND > > my time can stuff it. > > > > I guess my wording was off a little. I guess the point I was tring to > make was missed. > > It is the go fix it yourself attitude I guess that gets me sometimes in > both the mailing lists and IRC. There is some people in the user base > that can not code but are able to find issues on there systems and would > like to share them with either of the forums mentioned. I guess the > better answer than the "Go fix it yourself" would be "Please submit a > PR". This way both the project and the party involved can track the > progress. As someone who usual not codes, but helps finding issues. This is my personal opinion from reading through this thread: Dennis got told fix it yourself, after he has not provided any help in getting down to the issue. I haven't seen in one of his email what exact chip on what exact motherboard doesn't work. He also grossly overstated the amount of people being affected by it. > > TIA > -- > ------------------------------------------------------------------- > Ron Rosson ... and a UNIX user said ... > The InSaNe One rm -rf * > insane@oneinsane.net and all was /dev/null and *void() > ------------------------------------------------------------------- > Voice on telephone to man seated at his computer: > Thank you for calling the tech support hotline. If your computer > becomes obsolete while you're holding, press 1 to reach our sales > department. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 13:39:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail3.aracnet.com (mail3.aracnet.com [216.99.193.38]) by hub.freebsd.org (Postfix) with ESMTP id BA3BC37BB34 for ; Tue, 28 Mar 2000 13:39:52 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail3.aracnet.com (8.9.3/8.9.3) with ESMTP id NAA32605; Tue, 28 Mar 2000 13:39:11 -0800 Received: by shell1.aracnet.com (8.9.3) id NAA10358; Tue, 28 Mar 2000 13:40:45 -0800 Date: Tue, 28 Mar 2000 13:40:45 -0800 (PST) From: Brian Beattie To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003281924.OAA22806@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 Tue, 28 Mar 2000, Dennis wrote: > > If you fellows put as much time into freebsd as you do flaming me we > wouldnt need this crap. :-) > *Plonk!* Brian Beattie | This email was produced using professional quality, beattie@aracnet.com | standards based software. Users of Microsoft beattie@aracnet.com | products or other substandard software should www.aracnet.com/~beattie | contact the author about receiving a Free upgrade to | FreeBSD or Linux. "FreeBSD: The power to serve" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 15:59: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1x.pvt.net (ns.pvt.net [194.149.105.18]) by hub.freebsd.org (Postfix) with ESMTP id E2D1C37B622 for ; Tue, 28 Mar 2000 15:59:02 -0800 (PST) (envelope-from milon.papezik@oskarmobil.cz) Received: from oskarmobil.cz (nat.ceskymobil.cz [194.149.122.193]) by ns1x.pvt.net (8.9.3/8.9.3) with ESMTP id BAA22384; Wed, 29 Mar 2000 01:58:25 +0200 Message-ID: <38E14688.397488E2@oskarmobil.cz> Date: Wed, 29 Mar 2000 01:55:52 +0200 From: Milon Papezik X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: cz, cs, en MIME-Version: 1.0 To: dg@root.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC References: <200003280336.TAA17969@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >At the moment I have a spare machine > >and the NIC available for testing. > > > >Please let me know if you are interested > >in my offer to test your patches to 4.0 driver? > > Thanks, Milon. I've attached patches which I believe will fix the problem > as seen with the Compaq cards/motherboards, SuperMicro motherboards, and > certain newer Pro/100+ cards. Please test and let me know if they work for > you. I've tested this with (Compaq and Pro/100+) cards that some FreeBSD users > shipped to me a few months ago when the problem was first noticed, and the > driver now works fine with those. The algorithm for sizing the SEEPROM was > taken from the NetBSD version of the driver. Thanks for your patience. Yupeee! Works like a champ. It would be nice to see it commited as it fixes the problem. The only thing remaining is that the card is reported as Intel EtherExpress Pro 10/100B (which used to have i82557), but it's a card with i82559. This can be detected by reading the revision code of integrated PHY (registers 2 and 3) through MDI in CSR space (pg. 87 in i82559 datasheet or pg. 67 for i82559ER). The value is different for i82558 and i82559[ER]. It is 0x02A8:0150 for i82558 and 0x02A8:0154 for both 82559 and i82559ER. Do you plan to change/improve the card/chipset reporting mechanism? Thanks a lot! Milon -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 16: 9:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1D8A437B629 for ; Tue, 28 Mar 2000 16:09:23 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA21237; Tue, 28 Mar 2000 16:01:52 -0800 (PST) Message-Id: <200003290001.QAA21237@implode.root.com> To: Milon Papezik Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Wed, 29 Mar 2000 01:55:52 +0200." <38E14688.397488E2@oskarmobil.cz> From: David Greenman Reply-To: dg@root.com Date: Tue, 28 Mar 2000 16:01:52 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The only thing remaining is that the card is reported as >Intel EtherExpress Pro 10/100B (which used to have i82557), >but it's a card with i82559. > >This can be detected by reading the revision code of >integrated PHY (registers 2 and 3) through MDI in CSR space >(pg. 87 in i82559 datasheet or pg. 67 for i82559ER). > >The value is different for i82558 and i82559[ER]. >It is 0x02A8:0150 for i82558 and 0x02A8:0154 for both 82559 >and i82559ER. > >Do you plan to change/improve the card/chipset >reporting mechanism? I wasn't planning to in the short term, but I'd be happy to review some patches for it! :-) -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 17: 9:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shrimp.baynetworks.com (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (Postfix) with ESMTP id 5CB7A37BAF0 for ; Tue, 28 Mar 2000 17:09:41 -0800 (PST) (envelope-from bwithrow@engeast.BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by shrimp.baynetworks.com (8.9.1/8.9.1) with ESMTP id UAA27343; Tue, 28 Mar 2000 20:03:51 -0500 (EST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id UAA07630; Tue, 28 Mar 2000 20:13:18 -0500 (EST) Received: from tuva.engeast.baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id UAA18379; Tue, 28 Mar 2000 20:08:36 -0500 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.9.3/8.9.3) with ESMTP id UAA33365; Tue, 28 Mar 2000 20:08:15 -0500 (EST) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <200003290108.UAA33365@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@freebsd.org Cc: bwithrow@engeast.BayNetworks.COM, witr@rwwa.com Subject: FreeBSD on PowerPC? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 20:08:15 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't see anything about this on the web page. Is there any activity/interest in porting FreeBSD to the PowerPC, and in particular to embedded (non-MAC) systems? I've been pinging "core" people about this but haven't seem to teak their interrest. I gather that BSDI has a powerPC port, but I'd rather use the FreeBSD codebase rather than theirs, for a number of reasons. Perhaps if just select portions of there code were used it would be OK. -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 17:13:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-189.ricochet.net [204.179.134.189]) by hub.freebsd.org (Postfix) with ESMTP id 9C2EB37B58C for ; Tue, 28 Mar 2000 17:13:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03103; Tue, 28 Mar 2000 17:16:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003290116.RAA03103@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Withrow Cc: hackers@freebsd.org, bwithrow@engeast.BayNetworks.COM, witr@rwwa.com Subject: Re: FreeBSD on PowerPC? In-reply-to: Your message of "Tue, 28 Mar 2000 20:08:15 EST." <200003290108.UAA33365@tuva.engeast.baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 17:16:54 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Don't see anything about this on the web page. Is there any > activity/interest in porting FreeBSD to the PowerPC, and in > particular to embedded (non-MAC) systems? I've been pinging > "core" people about this but haven't seem to teak their interrest. Yes, there is very real interest. Are you just curious, or looking to contribute to the port? > I gather that BSDI has a powerPC port, but I'd rather use the > FreeBSD codebase rather than theirs, for a number of reasons. > Perhaps if just select portions of there code were used it > would be OK. I think you mean NetBSD, and it's traditional for us to pick up their work - you might even say that it's their job. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 17:37: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.checkpoint.com (kinata.checkpoint.com [199.203.156.41]) by hub.freebsd.org (Postfix) with ESMTP id CD16637B61D for ; Tue, 28 Mar 2000 17:36:54 -0800 (PST) (envelope-from mellon@pobox.com) Received: (from mellon@localhost) by happy.checkpoint.com (8.9.3/8.9.3) id DAA14975; Wed, 29 Mar 2000 03:39:08 GMT (envelope-from mellon@pobox.com) Date: Wed, 29 Mar 2000 03:39:08 +0000 From: Anatoly Vorobey To: Christian Weisgerber Cc: hackers@freebsd.org Subject: Re: Unicode on FreeBSD Message-ID: <20000329033908.A14122@happy.checkpoint.com> References: <20000320194702.11223.qmail@web3101.mail.yahoo.com> <8bitar$2i4f$1@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <8bitar$2i4f$1@bigeye.rhein-neckar.de>; from naddy@mips.rhein-neckar.de on Sat, Mar 25, 2000 at 06:34:19PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 06:34:19PM +0100, Christian Weisgerber wrote: > MikeM wrote: > > > Has anyone thought of Unicode support on FreeBSD? > > It has crossed my mind... > > > I think that it is inevitable that eventually FreeBSD > > will *need* to support unicode if it wants to continue > > as a viable operating system in the future. > > Probably. The demand for Unicode support is currently rather limited, > but I expect it to pick up somewhat once it is pervasive under > Linux and applications programmers come to expect its availability. I wonder how useful it would be to teach syscons/kbd to handle Unicode. If I mess up royally in the details below, someone please correct me, I only browsed through the sources a bit. Currently, if I understand this correctly, the keyboard driver, and not the console driver, is aware of the current keymap. The keymap maps keycodes with modifiers to actions, which are either some misc actions or character codes. The console driver gets character codes from kbd driver and doesn't need to know anything about keymaps (?). It doesn't know about screen fonts either; it just throws charcodes to video driver which has current font installed. It converses with applications via charcodes as well; at that level, the charcodes also include terminal emulation sequences. The unhappy drawbacks are: a) different language encodings require separate keymap files even when the actual keyboard layout doesn't change. b) different language encodings require separate screen fonts because those are indexed by character codes. c) general 8-bit limitations. d) ...? Now suppose we change the keymap files to assign Unicode codes to keycodes with mofifiers. (the actual Unicode numbers seem better in this case than short UTF-8 sequences?). The kbd driver returns those to syscons. Syscons now has the notion of the current encoding table which translates 8-bit <--> Unicode. It translates the codes back to 8-bit and gives them to applications. When applications give output, syscons translates it back into Unicode after handling the terminal emulation stuff. The video driver now uses a font which only depends on screen size, but not on encoding. It displays the stuff. If this works, the next step would be to offer UTF-8 as the ultimate table and start teaching usermode apps to be happy with it. However, even before that, the immediate effect would be great simplification and reduction of keymaps/screen fonts structure. Does this sound reasonable? -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 17:57:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 92F8937C0F5; Tue, 28 Mar 2000 17:57:33 -0800 (PST) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com ([209.69.196.181]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id RAA96311; Tue, 28 Mar 2000 17:57:21 -0800 (PST) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 81C241A5E; Tue, 28 Mar 2000 19:53:08 -0500 (EST) Date: Tue, 28 Mar 2000 19:53:08 -0500 From: Will Andrews To: Akinori -Aki- MUSHA Cc: freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG, shige@FreeBSD.ORG Subject: Re: zsh compdef collection for FreeBSD Message-ID: <20000328195308.E9136@argon.blackdawn.com> References: <86ln38vutx.wl@archon.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86ln38vutx.wl@archon.local.idaemons.org>; from knu@idaemons.org on Sat, Mar 25, 2000 at 07:58:50AM +0900 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 25, 2000 at 07:58:50AM +0900, Akinori -Aki- MUSHA wrote: > Hi, FreeBSD hackers! Hi knu, fellow zsh user! :) > I suppose FreeBSD users who use zsh (the Z shell) must have been > customizing it so well and got some neat definitions for FreeBSD (or > *BSD rather) environment. My /etc/zlogin has about 20 or 30 compctl's in there. It's now about 10,000 bytes. I had help from other people though. :) > Why not we collect those useful compdef's to send to the zsh > development team? You know, the latest zsh 3.1.6-dev-19 includes > Debian specific functions in `Completion/Debian', then why not we have > ours? I'm afraid that zsh will only have Linux/Solaris oriented > configurations if we don't feed anything to the zsh team. Cool idea. > Anyway, I open mine at the following site. > > http://people.freebsd.org/~knu/etc/zsh/functions/ > > The stock contents: > - cvsup > - kldload / kldunload > - pkg_add / pkg_delete / pkg_info > - mount / umount (very poor for the present) I have a couple CVS compctls, but that's about it for really useful compctls. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 18:55:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 28EF937B8F8 for ; Tue, 28 Mar 2000 18:55:13 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id DAA62724; Wed, 29 Mar 2000 03:51:41 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id DAA04841; Wed, 29 Mar 2000 03:51:37 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003290251.DAA04841@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: nsayer@kfu.com Cc: freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Colaberation invited -- ports/net/mpd-netgraph + pppoe In-Reply-To: Message from Nick Sayer of "Mon, 27 Mar 2000 15:25:36 -0800." <38DFEDF0.BFCC1DD8@sftw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 03:51:37 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you want to test your results, I'd suggest using pppoed... if you can talk to yourself and to ppp(8) then you've probably got it right. FWIW, my eventual aim is to bring more netgraph stuff into ppp(8).... > I friend of mine just got Pac$Bell Internet (see the story in > -questions), and he uses PPPoE over > DSL to connect to the net. /usr/sbin/ppp works just fine, but being the > sort I am, I am dissatisfied > with the solution, since there's still so much context switching > involved (given that the equivalent > to ng_ppp is still in userland). > > The much better solution, IMHO, is to add PPPoE support to > ports/net/mpd-netgraph, and I have > embarked on a course to do so. It's slow going, as it's my first real > grope into netgraph in a big > way (playing with ngctl and ksockets doesn't count). > > I am plenty happy to talk with anyone about this and it would be > particularly helpful if someone > who uses PPPoE could test the result, when it's ready (my friend is not > inclined to be a tester for > this sort of thing. The current solution is good enough for him). > > The eventual goal, of course, is to have a pair of machines run PPP over > a cross-connect 10baseT cable. > At the moment, however, call "origination" is favored. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 18:56:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by hub.freebsd.org (Postfix) with ESMTP id BB5DA37B8F8 for ; Tue, 28 Mar 2000 18:56:17 -0800 (PST) (envelope-from wigstah@akitanet.co.uk) Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id DAA62886; Wed, 29 Mar 2000 03:56:00 +0100 (BST) Date: Wed, 29 Mar 2000 03:56:00 +0100 (BST) From: Paul Robinson To: Dennis Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003281533.KAA21626@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 Tue, 28 Mar 2000, Dennis wrote: OK, personally, I've had enough of reading this. This strikes me as Troll, and I think Dennis has lost it, but I actaully *want* the following in the archives... I have never submitted code to FreeBSD because somebody else has usually already beaten me to it, nor do I consider myself 'valuable' to the project in the same way that young 'Dennis' does... at the same time, I *really* want this to be said, because nobody else is saying it... > obviously not the one that has the error. Are you paying attention? You really are an arrogant prat aren't you. How do you know it's the same one? Have you asked him? Let me guess.. you're *assuming* aren't you. That's OK, I understand you want to assume. How about we all just assume you're somebody we don't want anywhere near this mailing list? It's supposed to be constructive, and if you can't offer something, as other people have told you - to be blunt, (and I *mean* blunt) - F**k off. Now. > I passed on the info to DG on how to fix it. Work I do belongs to my > company because they pay me to do it. I know few of you understand that, So > unless you want to attach the "copyright Emerging Technologies" to the > driver you cant use it. Wow. I wish I was like you. You must be *so* special to have work that is that secret. If your employer really doesn't want to contribute to the Open Source community, why shoud you expect the Open Source community to contribute to you and your company profiting? I've watched you in the last few days be incredibly arrogant, incredibly rude, overly obnoxious, and the conclusion I've come to is that FreeBSD would be better off without people like you. You employer is obviosuly going to benefit from FreeBSD, but I suspect that they might want to employ somebody else to handle that project. I suspect that a .zip of your mails to this list so far, sent to your employers might possibly assist them in that decision. I suspect that the moment your employer and you are both more open to contributing to the project, you might just *possibly* find the project is more open to helping you out of a tight spot. If you demand that things are done for your benefit, and you aren't prepared to offer anything back rather than your rude, obtuse, arrogant, obnoxious crap, go use another operating system. Please. No, really. Are you still reading this? Why? I don't want to see any more of your obnoxious posts, and I suspect that nobody else on this list is interested in seeing your posts until you have decided to start being valuable to the project, in the same way you demand others to become valuable to your project. I don't assume I'm valuable to this project, neither should you. Perhaps that's the difference between us. -- Paul Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 21:42:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id D68FA37B6DE for ; Tue, 28 Mar 2000 21:42:32 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA28307; Tue, 28 Mar 2000 22:42:26 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38E19835.D9C3554D@softweyr.com> Date: Tue, 28 Mar 2000 22:44:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Withrow Cc: hackers@FreeBSD.ORG, bwithrow@engeast.BayNetworks.COM, witr@rwwa.com, tlambert@primenet.com Subject: Re: FreeBSD on PowerPC? References: <200003290108.UAA33365@tuva.engeast.baynetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Withrow wrote: > > Don't see anything about this on the web page. Is there any > activity/interest in porting FreeBSD to the PowerPC, and in > particular to embedded (non-MAC) systems? I've been pinging > "core" people about this but haven't seem to teak their interrest. > > I gather that BSDI has a powerPC port, but I'd rather use the > FreeBSD codebase rather than theirs, for a number of reasons. > Perhaps if just select portions of there code were used it > would be OK. Terry Lambert was pretty interested in this once upon a time. You might want to ping him. I've cc'd him in case he's interested. -- "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 Tue Mar 28 21:46:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by hub.freebsd.org (Postfix) with ESMTP id 0961E37B614 for ; Tue, 28 Mar 2000 21:46:20 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-01-55.nv.iinet.net.au [203.59.62.55]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id NAA26455; Wed, 29 Mar 2000 13:43:49 +0800 Message-ID: <38E197AF.3F54BC7E@elischer.org> Date: Tue, 28 Mar 2000 21:42:07 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Brian Somers Cc: nsayer@kfu.com, freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Colaberation invited -- ports/net/mpd-netgraph + pppoe References: <200003290251.DAA04841@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > If you want to test your results, I'd suggest using pppoed... if you > can talk to yourself and to ppp(8) then you've probably got it right. > > FWIW, my eventual aim is to bring more netgraph stuff into ppp(8).... Nick, Everything you need to do should be found in the pppoe file in the ppp sources (was it called 'ether.c') basically the code in the ng_pppoe man page example should still be basically correct. (I'll have to check if it's out of date.) (looks pretty correct) One additional bit. you can now send a message to the socket node to tell it to close down when the last connection is removed from it. this allows the ppp program to detect that the session has been terminated. and you can close the control socket as soon as the session is established. to do all this IN the kernel, you don't need the socket node, but rather, can connect the pppoe node directly to the ppp node. > > > I friend of mine just got Pac$Bell Internet (see the story in > > -questions), and he uses PPPoE over > > DSL to connect to the net. /usr/sbin/ppp works just fine, but being the > > sort I am, I am dissatisfied > > with the solution, since there's still so much context switching > > involved (given that the equivalent > > to ng_ppp is still in userland). > > > > The much better solution, IMHO, is to add PPPoE support to > > ports/net/mpd-netgraph, and I have > > embarked on a course to do so. It's slow going, as it's my first real > > grope into netgraph in a big > > way (playing with ngctl and ksockets doesn't count). > > > > I am plenty happy to talk with anyone about this and it would be > > particularly helpful if someone > > who uses PPPoE could test the result, when it's ready (my friend is not > > inclined to be a tester for > > this sort of thing. The current solution is good enough for him). > > > > The eventual goal, of course, is to have a pair of machines run PPP over > > a cross-connect 10baseT cable. > > At the moment, however, call "origination" is favored. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 23:21:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 8103A37BFDC for ; Tue, 28 Mar 2000 23:21:34 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id JAA03069; Wed, 29 Mar 2000 09:22:11 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200003290722.JAA03069@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Tue, 28 Mar 2000 16:24:17 +0200." <39402.954253457@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 09:22:11 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 28 Mar 2000 16:24:17 +0200, Sheldon Hearn wrote: > > >On Thu, 23 Mar 2000 09:21:50 +0100, Johan Karlsson wrote: > >> Before this is commited please have a look at the PR kern/17536 >> which addresses a similar thing. > >When using the patch you provide on that PR, what does the How-To-Repeat >do? The more detail you can give in your answer, the better. :-) > Hi I have just submitted a 'follow-up' to the PR with this info. If you want any other info, please ask again :-) /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 28 23:56:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BC35A37B715 for ; Tue, 28 Mar 2000 23:56:08 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12aDKL-0004BG-00; Wed, 29 Mar 2000 09:55:45 +0200 From: Sheldon Hearn To: Johan Karlsson Cc: Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Wed, 29 Mar 2000 09:22:11 +0200." <200003290722.JAA03069@numeri.campus.luth.se> Date: Wed, 29 Mar 2000 09:55:45 +0200 Message-ID: <16073.954316545@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Mar 2000 09:22:11 +0200, Johan Karlsson wrote: > I have just submitted a 'follow-up' to the PR with this info. Are you sure you sent mail to freebsd-gnats-submit@FreeBSD.org with "kern/17536" on the subject line? I can't see any follow-up on the PR. :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 0: 8:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id E705537B9D7 for ; Wed, 29 Mar 2000 00:08:13 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id KAA25671 for ; Wed, 29 Mar 2000 10:08:08 +0200 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id KAA14860 for freebsd-hackers@freebsd.org; Wed, 29 Mar 2000 10:02:39 +0200 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id F041C52AAB for ; Wed, 29 Mar 2000 10:02:33 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id DE2C11F1C; Wed, 29 Mar 2000 10:02:27 +0200 (CEST) Subject: RFC: newsyslog enhancements To: freebsd-hackers@freebsd.org (FreeBSD Hackers) Date: Wed, 29 Mar 2000 10:02:27 +0200 (CEST) Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000329080227.DE2C11F1C@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've put a tarball of my enhancements to newsyslog on http://www.freebsd.org/~hm/newsyslog.tar.gz The differences to the in-tree versions are: - ability to archive rotated logfiles into a separate configurable directory - provide another method (in addition to the ISO 8601 format) of specifying log rotation times, i.e. it is now possible to specify rotate at the last day of every month at midnight or rotate every week on Sunday at 23:00 hr - much clean up source, run through bde's KNF filter The changes have in part or full already been reviewed by Sheldon Hearn and Gary Jennejohn. This version of newsyslog runs on several production (3.4) machines since November 3, 1999 without problems. If there are no strong objections, i'll commit it to current. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 0:51:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.ms-agentur.de (server.ms-agentur.de [195.243.50.9]) by hub.freebsd.org (Postfix) with ESMTP id 3E9BE37B665 for ; Wed, 29 Mar 2000 00:51:13 -0800 (PST) (envelope-from so@i-clue.de) Received: from i-clue.de (ente.i-clue.de [192.168.0.42]) by server.ms-agentur.de (8.9.3/8.8.8) with ESMTP id LAA07694; Wed, 29 Mar 2000 11:53:22 +0200 Message-ID: <38E1C431.1722FCE5@i-clue.de> Date: Wed, 29 Mar 2000 10:52:01 +0200 From: Christoph Sold Organization: i-clue GmbH X-Mailer: Mozilla 4.7 [de] (WinNT; I) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: Robert Withrow Subject: Re: FreeBSD on PowerPC? References: <200003290108.UAA33365@tuva.engeast.baynetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Withrow schrieb: > Don't see anything about this on the web page. Is there any > activity/interest in porting FreeBSD to the PowerPC, and in > particular to embedded (non-MAC) systems? I've been pinging > "core" people about this but haven't seem to teak their interrest. > > I gather that BSDI has a powerPC port, but I'd rather use the > FreeBSD codebase rather than theirs, for a number of reasons. > Perhaps if just select portions of there code were used it > would be OK. When a PowerPC port starts, I can contribute some work. Got some idle Power macs sitting in a shelf. Anyhow, my level of experience is limited. I can do compiles and patches, as well as do some limited bugfixing, but don't count me in as Unix expert. -Christoph Sold P.S: Apologies if my Netscape mailer misbehaves again... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 1:22:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id F07A637BDA1 for ; Wed, 29 Mar 2000 01:22:17 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id LAA03783; Wed, 29 Mar 2000 11:22:48 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200003290922.LAA03783@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Wed, 29 Mar 2000 09:55:45 +0200." <16073.954316545@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 11:22:48 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 29 Mar 2000 09:55:45 +0200, Sheldon Hearn wrote: > > >On Wed, 29 Mar 2000 09:22:11 +0200, Johan Karlsson wrote: > >> I have just submitted a 'follow-up' to the PR with this info. > >Are you sure you sent mail to freebsd-gnats-submit@FreeBSD.org with >"kern/17536" on the subject line? I can't see any follow-up on the PR. >:-( No I did not think at all and replyed to the mail I got back from gnats-admin@FreeBSD.org :-( Should I re-send it or will it show up anyway. /K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 1:26:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C9EBE37BEE4 for ; Wed, 29 Mar 2000 01:26:45 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12aEk2-0006TZ-00; Wed, 29 Mar 2000 11:26:22 +0200 From: Sheldon Hearn To: Johan Karlsson Cc: Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Wed, 29 Mar 2000 11:22:48 +0200." <200003290922.LAA03783@numeri.campus.luth.se> Date: Wed, 29 Mar 2000 11:26:22 +0200 Message-ID: <24896.954321982@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Mar 2000 11:22:48 +0200, Johan Karlsson wrote: > Should I re-send it or will it show up anyway. Re-send to freebsd-gnats-submit@FreeBSD.org, taking care to preserve the "kern/17536" on the subject line. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 1:30:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id 1454B37BFA2 for ; Wed, 29 Mar 2000 01:30:33 -0800 (PST) (envelope-from yusufg@outblaze.com) Received: (qmail 47354 invoked from network); 29 Mar 2000 09:30:17 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 29 Mar 2000 09:30:17 -0000 Received: (qmail 13245 invoked by uid 500); 29 Mar 2000 09:30:15 -0000 Date: 29 Mar 2000 09:30:15 -0000 Message-ID: <20000329093015.13244.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-hackers@freebsd.org Subject: OpenBSD says it has "optimised kernel fdalloc". Is this relevant for FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was browsing through the OpenBSD changelog and came across a line which said optimised kernel fdalloc which pointed to this URL http://www.usenix.org/publications/library/proceedings/usenix98/full_papers/banga/banga_html/banga.html Is this relevant for FreeBSD ? Regards, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 1:43:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id ADA1537C217 for ; Wed, 29 Mar 2000 01:43:23 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id LAA03972; Wed, 29 Mar 2000 11:44:04 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200003290944.LAA03972@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Tiny GENERIC patch In-reply-to: Your message of "Wed, 29 Mar 2000 11:26:22 +0200." <24896.954321982@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 11:44:04 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 29 Mar 2000 11:26:22 +0200, Sheldon Hearn wrote: > > >On Wed, 29 Mar 2000 11:22:48 +0200, Johan Karlsson wrote: > >> Should I re-send it or will it show up anyway. > >Re-send to freebsd-gnats-submit@FreeBSD.org, taking care to preserve the >"kern/17536" on the subject line. Done I have also seen the follow-up using the wed interface. /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 1:59: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0F90E37B696 for ; Wed, 29 Mar 2000 01:59:05 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA05187; Wed, 29 Mar 2000 11:58:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Yusuf Goolamabbas Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: OpenBSD says it has "optimised kernel fdalloc". Is this relevant for FreeBSD In-reply-to: Your message of "29 Mar 2000 09:30:15 -0000." <20000329093015.13244.qmail@yusufg.portal2.com> Date: Wed, 29 Mar 2000 11:58:57 +0200 Message-ID: <5185.954323937@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000329093015.13244.qmail@yusufg.portal2.com>, Yusuf Goolamabbas w rites: >I was browsing through the OpenBSD changelog > and came across a line which said >optimised kernel fdalloc which pointed to this URL > >http://www.usenix.org/publications/library/proceedings/usenix98/full_papers/banga/banga_html/banga.html > >Is this relevant for FreeBSD ? The problem: yes, the solution: maybe. Other people have worked on an eventqueue based solution. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 2: 6:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vali.uas.alaska.edu (vali.uas.alaska.edu [137.229.150.18]) by hub.freebsd.org (Postfix) with SMTP id C421B37BDC3 for ; Wed, 29 Mar 2000 02:06:13 -0800 (PST) (envelope-from russ.pagenkopf@uas.alaska.edu) Received: from 145-pm1.jdc.alaska.net [209.112.136.145] (HELO uas.alaska.edu) by vali.uas.alaska.edu (AltaVista Mail V2.0r/2.0r BL25r listener) id 0000_0070_38e1_d585_2f1c; Wed, 29 Mar 2000 01:05:57 -0900 Message-ID: <38E1D648.B691FC8D@uas.alaska.edu> Date: Wed, 29 Mar 2000 01:09:21 -0900 From: Russ Pagenkopf Reply-To: jnrp@uas.alaska.edu X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Killing threads Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone coment on the below with authority? I'm learning a bit about threads and I'm curious what the answer is. Thanks, rus --- "Vladimir Butenko, Stalker Software, Inc." wrote: >>Stefan Seiz wrote: [snip] >>To have it kill unneeded threads? > > It will kill "excessive" threads. AFAIR, it will start to kill if the > unemployment level is more then 1/3: if a thread finishes a job and the number > of unemployed threads waiting for a job is more than 1/3 of the Max number of > threads(channels) allowed for that service, the thread is not placed into the > wating pool, but is killed instead. > >>Is this recommended? > > That depends on OS. Killing threads is a dark area in many thread > implementations. We know that it is safe on Windows, Solaris, and looks like > safe on MacOSX. On other platforms - use on your own risk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 6: 0:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 9194137C0A0 for ; Wed, 29 Mar 2000 06:00:08 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 42002 invoked by uid 1001); 29 Mar 2000 13:59:52 +0000 (GMT) To: hackers@freebsd.org Subject: Anybody have tools to read a Digital Unix "vdump" tape on FreebSD? From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 29 Mar 2000 15:59:52 +0200 Message-ID: <42000.954338392@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD? I have a number of such tapes, and would prefer to read them on an (Intel) FreeBSD box instead of having to reinstall DU on a machine which has had its disks wiped. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 7:18:38 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 8F40A37C177 for ; Wed, 29 Mar 2000 07:18:33 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA25847; Wed, 29 Mar 2000 10:19:13 -0500 (EST) Message-Id: <200003291519.KAA25847@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 29 Mar 2000 10:16:01 -0500 To: Paul Robinson From: Dennis Subject: Re: Onboard Intel NIC Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200003281533.KAA21626@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> obviously not the one that has the error. Are you paying attention? > >You really are an arrogant prat aren't you. How do you know it's the same >one? Have you asked him? Let me guess.. you're *assuming* aren't you. Wait, so we were talking about the "newer" intel boards not being fully supported in the fxp driver and this drubb chimes in with "Im using an eepro with no problems"....clearly that isnt relevant, since on-one along the line ever said that all intel cards didnt work. So, it is clear that you too are not paying attention, yet you seem to have an opinion regarding things that you also know little about. Dont browbeat me for putting down some dope who doesnt know what hes talking about who feels compelled to voice an opinion based on ignorance. What is really funny is that, as usual, all of the people who feel compelled to make comments about me are not experiencing the problem....its real easy to pick on someone when the issue doenst effect you. Meanwhile, the problem is fixed, and scads of people who have experienced the problem are emailing me to thank me for lighting a fire under some butts. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 7:26:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by hub.freebsd.org (Postfix) with ESMTP id D9BF237C0C5 for ; Wed, 29 Mar 2000 07:26:37 -0800 (PST) (envelope-from wigstah@akitanet.co.uk) Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id QAA86745; Wed, 29 Mar 2000 16:26:33 +0100 (BST) Date: Wed, 29 Mar 2000 16:26:33 +0100 (BST) From: Paul Robinson To: Dennis Cc: Blaz Zupan , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-Reply-To: <200003291519.KAA25847@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 Wed, 29 Mar 2000, Dennis wrote: > So, it is clear that you too are not paying attention, yet you seem to have > an opinion regarding things that you also know little about. Dont browbeat > me for putting down some dope who doesnt know what hes talking about who > feels compelled to voice an opinion based on ignorance. > > What is really funny is that, as usual, all of the people who feel > compelled to make comments about me are not experiencing the problem....its > real easy to pick on someone when the issue doenst effect you. So, let me get this right, it's OK for you to be abusive to somebody who has a problem, but the rest of us have to keep quiet. Quite a hypocrite really, aren't you? Time to add some mail filters... -- Paul Robinson - Developer/Systems Administrator @ Akitanet Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 7:32:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id C1CFA37B680 for ; Wed, 29 Mar 2000 07:32:13 -0800 (PST) (envelope-from john@athena.lightningone.net) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id KAA47145; Wed, 29 Mar 2000 10:37:42 -0500 (EST) (envelope-from john@athena.lightningone.net) Date: Wed, 29 Mar 2000 10:37:42 -0500 (EST) From: Essenz Consulting To: Dennis Cc: freebsd-hackers@freebsd.org Subject: Re: Onboard Intel NIC In-Reply-To: <200003291519.KAA25847@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 Maybe I got lost in the hub-bub, but I am still having trouble getting my onboard NIC to work, still get unsupported phy errors. When you say its fixed are you refering to the patch the DG sent out the other day, or your patch. I applied DG's patch and the problem still exists. And I cant compile my kernel with your patch. Does your if_fxp.c file need to be compiled on a 3.4 system? Because I am running 4.0. In any case I am starting to get real frustrated again. Maybe I am using the wrong patch or something?! -John On Wed, 29 Mar 2000, Dennis wrote: > > >> obviously not the one that has the error. Are you paying attention? > > > >You really are an arrogant prat aren't you. How do you know it's the same > >one? Have you asked him? Let me guess.. you're *assuming* aren't you. > > Wait, so we were talking about the "newer" intel boards not being fully > supported in the fxp driver and this drubb chimes in with "Im using an > eepro with no problems"....clearly that isnt relevant, since on-one along > the line ever said that all intel cards didnt work. > > So, it is clear that you too are not paying attention, yet you seem to have > an opinion regarding things that you also know little about. Dont browbeat > me for putting down some dope who doesnt know what hes talking about who > feels compelled to voice an opinion based on ignorance. > > What is really funny is that, as usual, all of the people who feel > compelled to make comments about me are not experiencing the problem....its > real easy to pick on someone when the issue doenst effect you. > > Meanwhile, the problem is fixed, and scads of people who have experienced > the problem are emailing me to thank me for lighting a fire under some butts. > > DB > > > > 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 Wed Mar 29 8: 9:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id B17AF37B5CD for ; Wed, 29 Mar 2000 08:09:22 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id JAA3004707 for ; Wed, 29 Mar 2000 09:09:21 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id JAA02527 for ; Wed, 29 Mar 2000 09:09:20 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 29 Mar 2000 09:09:20 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@freebsd.org Subject: How good a job of PCI config will freebsd do? 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 Question, has anyone tried booting freebsd on raw hardware, i.e. absent a bios? I am curious as to how good a job it can do if, e.g., no enable bits are set in PIIX4, BARs are not set on PCI devices, no IRQs are assigned, and so on. Anyone feel they are close enough to this to say? See www.acl.lanl.gov/linuxbios to see why I am asking. I see no reason I could not also put FreeBSD as the BIOS in nvram as well. If you're trying to build a cluster, you have to kill the BIOS. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 8:10:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 2AF4237C044 for ; Wed, 29 Mar 2000 08:10:41 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JNM4MMRGRE0011ZQ@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 29 Mar 2000 18:10:38 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 29 Mar 2000 18:10:37 +0100 Content-return: allowed Date: Wed, 29 Mar 2000 18:10:37 +0100 From: "Koster, K.J." Subject: RE: Onboard Intel NIC To: 'Dennis' Cc: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E452201313A01@l04.research.kpn.com> 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 Dear Dennis, The reason Poul-Henning Kamp threatened to filter you is because you were insulting people (and yes, in response they insult you too). He did not do so because you were critisizing FreeBSD's method of working. Many have done that without getting threatening remarks from Poul-Henning Kamp. In the e-mail that sparked all this, you write two paragraphs. The second paragraph is clear and to the point. The first paragraph is not. Perhaps you could leave out the first paragraph and only send the second next time? Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 11: 2:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-053.ricochet.net [204.179.134.53]) by hub.freebsd.org (Postfix) with ESMTP id 0E79837BA71 for ; Wed, 29 Mar 2000 11:02:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01047; Wed, 29 Mar 2000 11:05:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003291905.LAA01047@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald G. Minnich" Cc: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-reply-to: Your message of "Wed, 29 Mar 2000 09:09:20 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 11:05:37 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Question, has anyone tried booting freebsd on raw hardware, i.e. absent a > bios? I am curious as to how good a job it can do if, e.g., no enable bits > are set in PIIX4, BARs are not set on PCI devices, no IRQs are assigned, > and so on. Anyone feel they are close enough to this to say? Not good. You'd also have to take care of PCI setup, interrupt routing, any board-specific hacks using the GPIO bits, etc. (eg. on most systems you'll need to turn the CPU fan, power LEDs, etc. on) Doing this without the BIOS is likely to be a major PITA, and different for every single board. Outside of some expensive and boring embedded vendors' products, you're unlikely to get the sort of information you need without reverse-engineering the BIOS that's already there. > See www.acl.lanl.gov/linuxbios to see why I am asking. I see no reason I > could not also put FreeBSD as the BIOS in nvram as well. If you're trying > to build a cluster, you have to kill the BIOS. Well, they're going to have the same basic stuff, and I can see that they're not having much fun trying to get there. I'm curious as to what you mean by "have to kill the BIOS" though; I'm not seeing why it's an issue. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 11:30:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 3335E37B633 for ; Wed, 29 Mar 2000 11:30:26 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA24436; Wed, 29 Mar 2000 11:23:03 -0800 (PST) Message-Id: <200003291923.LAA24436@implode.root.com> To: Essenz Consulting Cc: Dennis , freebsd-hackers@FreeBSD.ORG Subject: Re: Onboard Intel NIC In-reply-to: Your message of "Wed, 29 Mar 2000 10:37:42 EST." From: David Greenman Reply-To: dg@root.com Date: Wed, 29 Mar 2000 11:23:03 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Maybe I got lost in the hub-bub, but I am still having trouble getting my >onboard NIC to work, still get unsupported phy errors. > >When you say its fixed are you refering to the patch the DG sent out the >other day, or your patch. I applied DG's patch and the problem still >exists. And I cant compile my kernel with your patch. Your problem is unrelated to the problems that other people were having. I'll work with you privately to narrow it down. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 11:37:36 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 1225537B63F for ; Wed, 29 Mar 2000 11:37:13 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA26951; Wed, 29 Mar 2000 14:38:07 -0500 (EST) Message-Id: <200003291938.OAA26951@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 29 Mar 2000 14:34:53 -0500 To: Paul Robinson From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200003291519.KAA25847@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:26 PM 3/29/00 +0100, Paul Robinson wrote: >On Wed, 29 Mar 2000, Dennis wrote: > >> So, it is clear that you too are not paying attention, yet you seem to have >> an opinion regarding things that you also know little about. Dont browbeat >> me for putting down some dope who doesnt know what hes talking about who >> feels compelled to voice an opinion based on ignorance. >> >> What is really funny is that, as usual, all of the people who feel >> compelled to make comments about me are not experiencing the problem....its >> real easy to pick on someone when the issue doenst effect you. > >So, let me get this right, it's OK for you to be abusive to somebody who >has a problem, but the rest of us have to keep quiet. Quite a hypocrite >really, aren't you? No, I never "abused" anyone personally until they abused me. Its called "self defense" in free countries. The thread started: dennis> has the PHY problem in the fxp driver been fixed yet? if so is where can i get it? wes peters> why dont you just get it yourself - then called me lazy and incompetent DG> no, i havent fixed it yet, I've been sick dennis> ok, thanks, Thats all I wanted, if I listened to peters I would have wasted all that time on a wild goose chase --- flamed by many Im sorry that lots of folks like to make comments about subjects that dont involve them, but thats part of the public experience. I just wanted to know if the stupid driver was fixed yet. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 11:47:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 3307B37C1CF for ; Wed, 29 Mar 2000 11:45:58 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id MAA2708081 for ; Wed, 29 Mar 2000 12:45:53 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id MAA03674 for ; Wed, 29 Mar 2000 12:45:53 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 29 Mar 2000 12:45:53 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-Reply-To: <200003291905.LAA01047@mass.cdrom.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 Wed, 29 Mar 2000, Mike Smith wrote: > Well, they're going to have the same basic stuff, and I can see that > they're not having much fun trying to get there. actually, "they" is "me": that's my project. > I'm curious as to what you mean by "have to kill the BIOS" though; I'm > not seeing why it's an issue. Unless you've had to work with 1024 BIOS upgrades, it's not easy to see the need :-) Nevertheless, I'll drop it here. I was curious what FreeBSD could do. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 12:45: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C9DFF37B55C for ; Wed, 29 Mar 2000 12:44:46 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA18949; Wed, 29 Mar 2000 22:29:39 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02136; Wed, 29 Mar 2000 20:48:52 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 20:48:52 +0200 From: Wilko Bulte To: sthaug@nethelp.no Cc: hackers@freebsd.org Subject: Re: Anybody have tools to read a Digital Unix "vdump" tape on FreebSD? Message-ID: <20000329204851.C2044@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <42000.954338392@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <42000.954338392@verdi.nethelp.no>; from sthaug@nethelp.no on Wed, Mar 29, 2000 at 03:59:52PM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 03:59:52PM +0200, sthaug@nethelp.no wrote: > Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD? > I have a number of such tapes, and would prefer to read them on an (Intel) > FreeBSD box instead of having to reinstall DU on a machine which has had > its disks wiped. Vdump, the dump incarnation for Tru64 AdvFS, can to the best of my knowledge only be read by vrestore. I'm afraid your stuck to using a T64 box for this. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: 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 Wed Mar 29 12:54:17 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 1A2D737B860; Wed, 29 Mar 2000 12:54:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA12203; Wed, 29 Mar 2000 12:53:46 -0800 Date: Wed, 29 Mar 2000 12:54:02 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: Anybody have tools to read a Digital Unix "vdump" tape on FreebSD? In-Reply-To: <20000329204851.C2044@yedi.iaf.nl> 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 Yeah- and if you fund a public domain version of this, maybe you can also find something to read old DSC or BRU tapes? :-) On Wed, 29 Mar 2000, Wilko Bulte wrote: > On Wed, Mar 29, 2000 at 03:59:52PM +0200, sthaug@nethelp.no wrote: > > Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD? > > I have a number of such tapes, and would prefer to read them on an (Intel) > > FreeBSD box instead of having to reinstall DU on a machine which has had > > its disks wiped. > > Vdump, the dump incarnation for Tru64 AdvFS, can to the best of my knowledge > only be read by vrestore. I'm afraid your stuck to using a T64 box for this. > > -- > Wilko Bulte Arnhem, The Netherlands > http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org > > > 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 Wed Mar 29 12:58: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg135-034.ricochet.net [204.179.135.34]) by hub.freebsd.org (Postfix) with ESMTP id 1603937B757 for ; Wed, 29 Mar 2000 12:57:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00799; Wed, 29 Mar 2000 13:01:22 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003292101.NAA00799@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald G. Minnich" Cc: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-reply-to: Your message of "Wed, 29 Mar 2000 12:45:53 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 13:01:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 29 Mar 2000, Mike Smith wrote: > > Well, they're going to have the same basic stuff, and I can see that > > they're not having much fun trying to get there. > > actually, "they" is "me": that's my project. Yeep. You don't know Fra Dolcini, do you? That looks like a Really Unpleasant Undertaking. 8( > > I'm curious as to what you mean by "have to kill the BIOS" though; I'm > > not seeing why it's an issue. > > Unless you've had to work with 1024 BIOS upgrades, it's not easy to see > the need :-) Er. Ok, I can dig that. However, there are only about three or four different flash architectures commonly in use, and we can hope that people are going to start using things like the Intel Firmware Hub, and hopefully EFI later on. I realise that you're not about to throw your cluster hardware over for a pile of IA64 boxes just yet, but it strikes me that it'd be easier just to write a userland flash updater than to rewrite the BIOS from scratch. 8) > Nevertheless, I'll drop it here. I was curious what FreeBSD could do. Nothing, I'm afraid. We expect the plaform firmware to work as expected/ documented... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 13:23:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 2809A37B554 for ; Wed, 29 Mar 2000 13:22:58 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id OAA3100337 for ; Wed, 29 Mar 2000 14:22:56 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id OAA04399 for ; Wed, 29 Mar 2000 14:22:56 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 29 Mar 2000 14:22:56 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-Reply-To: <200003292101.NAA00799@mass.cdrom.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 Wed, 29 Mar 2000, Mike Smith wrote: > Yeep. You don't know Fra Dolcini, do you? That looks like a Really > Unpleasant Undertaking. 8( It's getting there. Also SiS is now a supporter. Long term, we may see motherboards specifically designed for the OSS community, with real docs yet. Also, I can't see any way to get to 3-second reboot (one of the things we need) given the stupid way BIOSes work. PXE is not an answer. > cluster hardware over for a pile of IA64 boxes just yet, but it strikes > me that it'd be easier just to write a userland flash updater than to > rewrite the BIOS from scratch. 8) You haven't look at how intel designs and documents some of their motherboards, particularly the L440GX+. They won't tell people what they need to know to update flash on this one. Result: you have to boot DOS to upgrade flash. Stupid of them. Also, there are an amazing number of advantages to having a real OS in the flash. Once you start thinking about it, it becomes hard to live without. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 13:58: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.fsnnet.net (mail.fsnnet.net [208.233.209.100]) by hub.freebsd.org (Postfix) with ESMTP id 5F71737B7B5 for ; Wed, 29 Mar 2000 13:57:56 -0800 (PST) (envelope-from keith@fsnnet.net) Received: from fsnnet.net (ws237.fsnnet.net [208.233.209.237]) by mail.fsnnet.net (8.9.3/8.9.3) with ESMTP id QAA25791 for ; Wed, 29 Mar 2000 16:58:06 -0500 (EST) (envelope-from keith@fsnnet.net) Message-ID: <38E27B10.CDB225AE@fsnnet.net> Date: Wed, 29 Mar 2000 16:52:16 -0500 From: Keith C Organization: Full Service Network X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: Join up Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to join the FreeBSD information group as I have become a newbie FreeBSD administrator for the last severa lmonths. I can be emailed at crawf@usaor.net or keith@fsnnet.net Thank you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 14:35:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg135-034.ricochet.net [204.179.135.34]) by hub.freebsd.org (Postfix) with ESMTP id 6ABAC37B824 for ; Wed, 29 Mar 2000 14:35:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01255; Wed, 29 Mar 2000 14:39:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003292239.OAA01255@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald G. Minnich" Cc: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-reply-to: Your message of "Wed, 29 Mar 2000 14:22:56 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 14:39:17 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 29 Mar 2000, Mike Smith wrote: > > Yeep. You don't know Fra Dolcini, do you? That looks like a Really > > Unpleasant Undertaking. 8( > > It's getting there. Also SiS is now a supporter. Long term, we may see > motherboards specifically designed for the OSS community, with real docs > yet. Also, I can't see any way to get to 3-second reboot (one of the > things we need) given the stupid way BIOSes work. PXE is not an answer. Having a chipset vendor onside isn't a bad thing, for sure, and I can see where the current design of PC BIOS code wouldn't help. One thing that puzzles me though is why you want to stick with the PC BIOS... > > cluster hardware over for a pile of IA64 boxes just yet, but it strikes > > me that it'd be easier just to write a userland flash updater than to > > rewrite the BIOS from scratch. 8) > > You haven't look at how intel designs and documents some of their > motherboards, particularly the L440GX+. They won't tell people what they > need to know to update flash on this one. Result: you have to boot DOS to > upgrade flash. Stupid of them. Er, I have, which is why I was observing that what you're trying to do on the larger scale is just a bit masochistic. > Also, there are an amazing number of advantages to having a real OS in the > flash. Once you start thinking about it, it becomes hard to live without. I'd prefer real firmware, actually. OF isn't all that bad, and I seem to recall that Parag Patel is porting it to run on the L440GX+. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 15:45:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 1B63C37B696; Wed, 29 Mar 2000 15:45:11 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id PAA27971; Wed, 29 Mar 2000 15:45:09 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: Mike Smith Cc: "Ronald G. Minnich" , hackers@FreeBSD.ORG Subject: Re: How good a job of PCI config will freebsd do? In-Reply-To: Message from Mike Smith of "Wed, 29 Mar 2000 14:39:17 PST." <200003292239.OAA01255@mass.cdrom.com> X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Wed, 29 Mar 2000 15:45:08 -0800 Message-ID: <27967.954373508@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: >I'd prefer real firmware, actually. OF isn't all that bad, and I seem to >recall that Parag Patel is porting it to run on the L440GX+. Heh - yup, I'm right in the middle of port SmartFirmware to the L440GX+. Definitely masochistic. I've decided that drilling a hole through my head would be faster with the same results, only with less pain. Anyway, we've had our L440GX+ surgically altered and it's now sporting a Meritec socket in place of the flash part. I've just now ordered a PromICE with trace as the old hit-n-miss techniques to get something out of the serial port from ROM just ain't working. I've come to the conclusion that there is absolutely nothing about PC hardware that is in any way shape or form designed correctly. *Everything* about it is wrong wrong wrong. Don't get me started. The port is progressing. I already have a RAM version of SF running happily, probing devices, booting images off of the net, etc. Getting it bootstrapped out of ROM is the current task. SF always runs in 32-bit `flat' mode, ROM or RAM. Ronald G. Minnich wrote: >> It's getting there. Also SiS is now a supporter. Long term, we may see >> motherboards specifically designed for the OSS community, with real docs >> yet. Also, I can't see any way to get to 3-second reboot (one of the >> things we need) given the stupid way BIOSes work. PXE is not an answer. Don't know if SmartFirmware will be able to meet the 3-second boot, but it should definitely be faster than a BIOS. For one thing, we don't pretend that we can run an exhaustive and completely trustworthy memory test. :) (Not even sure if this is possible, actually.) >> You haven't look at how intel designs and documents some of their >> motherboards, particularly the L440GX+. They won't tell people what they >> need to know to update flash on this one. Result: you have to boot DOS to >> upgrade flash. Stupid of them. This is why I'm burning the entire flash part in an external programmer. Once SmartFirmware is running on the motherboard, it'll be able to update and burn new images over the net, including your original one. Bootstrapping will still need a floppy to boot under the old BIOS, run a RAM version of SmartFirmware, download a ROM image over the net, burn it in, then reset. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 20:35:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obstruction.com (cr211472-a.ym1.on.wave.home.com [24.114.3.188]) by hub.freebsd.org (Postfix) with ESMTP id 6FD6D37B604 for ; Wed, 29 Mar 2000 20:35:18 -0800 (PST) (envelope-from guy@obstruction.com) Received: (from guy@localhost) by obstruction.com (8.9.2/8.9.2) id XAA00546 for freebsd-hackers@FreeBSD.ORG; Tue, 28 Mar 2000 23:34:26 -0500 (EST) (envelope-from guy) Date: Tue, 28 Mar 2000 23:34:26 -0500 From: Guy Middleton To: freebsd-hackers@FreeBSD.ORG Subject: can't install Linux compatibility, or, why RPM isn't our friend Message-ID: <20000328233426.A534@chaos.obstruction.com> References: <20000329214847.A18153@chaos.obstruction.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000329214847.A18153@chaos.obstruction.com>; from guy on Wed, Mar 29, 2000 at 09:48:47PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying without success to install the linux_base package. The install target in the makefile calls rpm to install the RPM-format package files, but the bash package mysteriously fails to install. Turning on debugging for rpm give no useful info. Has anybody seen this? I'm running 3.2-RELEASE, but with an up-to-date /usr/ports. order# make install ===> Installing for linux_base-6.1 setup-2.0.5-1.noarch.rpm filesystem-1.3.5-1.noarch.rpm basesystem-6.0-4.noarch.rpm ldconfig-1.9.5-15.i386.rpm glibc-2.1.2-11.i386.rpm termcap-9.12.6-15.i386.rpm libtermcap-2.0.8-18.i386.rpm bash-1.14.7-16.i386.rpm execution of script failed error: /usr/ports/distfiles/rpm/bash-1.14.7-16.i386.rpm cannot be installed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. order# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 22:45:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id AAD1E37B590 for ; Wed, 29 Mar 2000 22:45:21 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA55048 for ; Wed, 29 Mar 2000 22:45:21 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E2F801.548AAAF1@gorean.org> Date: Wed, 29 Mar 2000 22:45:21 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Proposed new Bourne shell init files Content-Type: multipart/mixed; boundary="------------9ABA32D60C072BD381454706" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------9ABA32D60C072BD381454706 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Still no comment on this, so here's to a wider audience. Doug -------- Original Message -------- Subject: Re: cvs commit: src/share/skel dot.cshrc dot.login src/etc/rootdot.cshrc dot.login Date: Sun, 26 Mar 2000 00:55:40 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority To: Robert Watson CC: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG References: <200003252023.MAA76070@freefall.freebsd.org> I'm really glad someone is taking a look at this. Please don't take any of my comments as criticism. :) Robert Watson wrote: > > rwatson 2000/03/25 12:23:40 PST > > Modified files: > share/skel dot.cshrc dot.login > etc/root dot.cshrc dot.login > Log: > o Migrate path, umask from dot.login to dot.cshrc I'm a little confused about moving umask. Doesn't it make more sense in dot.login, since it mostly applies to login shells? Maybe it has some application in non-interactive shells I'm not aware of. > o Comment out display of fortune by default. Good move. This made my boss nuts when we started using freebsd at work. > o Synch root's .cshrc/.login and non-root's .cshrc/.login in terms of > gratuitous variables set (EDITOR). Another good move. FWIW, you have two small gratuitous differences. --- /usr/src/share/skel/dot.cshrc Sat Mar 25 15:23:36 2000 +++ /usr/src/etc/root/dot.cshrc Sat Mar 25 15:23:43 2000 @@ -1,4 +1,4 @@ -# $FreeBSD: src/share/skel/dot.cshrc,v 1.11 2000/03/25 20:23:34 rwatson Exp $ +# $FreeBSD: src/etc/root/dot.cshrc,v 1.26 2000/03/25 20:23:38 rwatson Exp $ # # .cshrc - csh resource script, read at beginning of execution by each shell # @@ -22,6 +22,7 @@ if ($?prompt) then # An interactive shell -- set some stuff up + set prompt = "`hostname -s`# " set filec set history = 100 set savehist = 100 --- /usr/src/share/skel/dot.login Sat Mar 25 15:23:36 2000 +++ /usr/src/etc/root/dot.login Sat Mar 25 15:23:43 2000 @@ -1,4 +1,4 @@ -# $FreeBSD: src/share/skel/dot.login,v 1.15 2000/03/25 20:23:34 rwatson Exp $ +# $FreeBSD: src/etc/root/dot.login,v 1.21 2000/03/25 20:23:39 rwatson Exp $ # # .login - csh login script, read by login shell, after `.cshrc' at login. # @@ -6,4 +6,4 @@ # # Uncomment to display a random cookie each login: -# [ -x /usr/games/fortune ] && /usr/games/fortune -s +# [ -x /usr/games/fortune ] && /usr/games/fortune Also, one thing that's bugged me forever about the csh files is that "righteous" is misspelled. :) I also think that using "022" instead of just "22" would be less confusing to the user, since the man page says that the values should be specified in octal. > Similar changes probably need to be made in other dot.* files for root > and skel, as all of these files seem to set different aliases, environmental > variables, prompts, and have different semantics. I'm a bash/sh user, so I've taken the liberty of making up some new files. The intention is that you can do with these files what you've done with the csh ones, namely synch src/share/skel and src/etc/root, with the one exception mentioned below. Rather than submit patches, I've just attached them since the differences are pretty substantial in terms of organization. I used the existing files as a basis, and added the 'unlimit' function I've used for years. It's the one thing that csh has that I'm jealous of. :) Printing out what's being set helps unprivileged user understand what items aren't being changed. For root's dot.profile you need to add the following: --- dot.profile Sat Mar 25 23:24:25 2000 +++ dot.profile.root Sat Mar 25 23:41:15 2000 @@ -8,6 +8,8 @@ # Export all the environment variables to clean things up a bit set -o allexport +HOME=/root + # Remove /usr/games and /usr/X11R6/bin if you want PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:$HOME/bin If it turns out that putting the umask setting in the profile (roughly equal to dot.cshrc) then here is a patch for that: --- dot.profile.mine Sat Mar 25 23:24:25 2000 +++ dot.profile Sun Mar 26 00:14:52 2000 @@ -24,6 +24,9 @@ # Turn off allexport to prevent possible foot-shooting set +o allexport +# Allows permissions of -rwxr-xr-x +umask 022 + # Set ENV to a file invoked each time sh is started for interactive use. ENV=$HOME/.shrc; export ENV Commentary on my files. . . Using allexport instead of an explicit 'export' for every variable makes the file easier to read, and gives a novice user one less thing to worry about. The PATH may be a little much, but I wanted to bring it in line with the one you're using for csh. I also rearranged the order to try and put the most frequently used directories first. login sets the initial PATH to '/usr/bin:/bin' so I thought it would be a good idea to emulate that. Also, I checked 'hash' for a while as a rough statistical analysis, and this is the PATH that made the most sense. I don't have games in my path, but everything else is what I use. It might make sense to choose one "canonical" version of PATH and use that in dot.* and /etc/login.conf so the user has a reasonable expectation of a consistent environment. I added 'set -o emacs' to dot.shrc, it makes life much easier, and I don't see any reason not to use it. I also took the best of both worlds for the 'ls' aliases. The biggest difference is the 'll' alias. I tend to agree with the existing sh files that 'll' should show everything, so I used -a instead of -A. I also added the commented out version of the fortune command, since sh users have a sense of humor too. :) The _USERNAME gymnastics are necessary to take into account logging in as an unprivileged user, then su'ing. I would like to see dot.shrc added to src/etc/root, and src/etc/Makefile. If that happens I'd like to suggest uncommenting the first two "paranoid" aliases in the file. I use these every day for all of my login shells and they have saved my ass many a time. :) The 'rm' alias is too paranoid even for my tastes though. If this file gets added to /root, it's not necessary to link it into / since setting $HOME in root's dot.profile will take care of that (which is the reason for the patch above). I fully realize that treading in this area is likely to provoke lenghty arguments, goring of cows, etc. :) I tried to be as conservative as possible in terms of preserving what's in the existing files, etc. I'm hoping that the fact that someone was willing to step forward and get the ball rolling indicates that we're willing to finish the job. :) Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." --------------9ABA32D60C072BD381454706 Content-Type: text/plain; charset=us-ascii; name="dot.shrc" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dot.shrc" # $FreeBSD$ # # .shrc - Bourne shell startup file # # This file will be used if the shell is invoked for interactive use and # the environment variable ENV is set to the name of this file. # # See also sh(1), environ(7). # # Make interactive shells a little more friendly set -o emacs # Search path for cd(1) CDPATH=.:$HOME # Prompt _USERNAME=`whoami` PS1="$_USERNAME@`hostname -s`" case "$_USERNAME" in root) PS1="${PS1}# " ;; *) PS1="${PS1}$ " ;; esac # Allows permissions of -rwxr-xr-x umask 022 # General aliases alias la='ls -A' alias lf='ls -AF' alias ll='ls -loaF' alias m=$PAGER alias g='egrep -i' # Shell specific aliases alias h='fc -l' alias j=jobs # For the paranoid #alias cp='cp -ip' #alias mv='mv -i' #alias rm='rm -i' # Implement a csh-like unlimit command. Unpriviliged users may # not be able to change some of these limits. unlimit ( ) { echo ' Setting sock buf size'; ulimit -b unlimited echo ' Setting core file size'; ulimit -c unlimited echo ' Setting data size'; ulimit -d unlimited echo ' Setting file size'; ulimit -f unlimited echo ' Setting locked mem size'; ulimit -l unlimited echo ' Setting res size'; ulimit -m unlimited echo ' Setting fds'; ulimit -n unlimited echo ' Setting stack size'; ulimit -s unlimited echo ' Setting cpu time'; ulimit -t unlimited echo ' Setting max processes'; ulimit -u unlimited } # Uncomment to display a random cookie each login: #[ -x /usr/games/fortune ] && /usr/games/fortune --------------9ABA32D60C072BD381454706 Content-Type: text/plain; charset=us-ascii; name="dot.profile" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dot.profile" # $FreeBSD$ # # .profile - Bourne shell startup script for login shells # # See also sh(1), environ(7). # # Export all the environment variables to clean things up a bit set -o allexport # Remove /usr/games and /usr/X11R6/bin if you want PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:$HOME/bin # Setting TERM is normally done through /etc/ttys. Only override # if you're sure that you'll never log in via telnet, xterm or a # serial line. # Use cons25l1 for iso-* fonts TERM=${TERM:-cons25} EDITOR=vi PAGER=more BLOCKSIZE=K # Turn off allexport to prevent possible foot-shooting set +o allexport # Allows permissions of -rwxr-xr-x umask 022 # Set ENV to a file invoked each time sh is started for interactive use. ENV=$HOME/.shrc; export ENV --------------9ABA32D60C072BD381454706-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 23: 1:26 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 AB2E337B7D7 for ; Wed, 29 Mar 2000 23:01:23 -0800 (PST) (envelope-from imp@harmony.village.org) 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 AAA66942; Thu, 30 Mar 2000 00:01:22 -0700 (MST) (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 AAA21734; Thu, 30 Mar 2000 00:00:57 -0700 (MST) Message-Id: <200003300700.AAA21734@harmony.village.org> To: Doug Barton Subject: Re: Proposed new Bourne shell init files Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 29 Mar 2000 22:45:21 PST." <38E2F801.548AAAF1@gorean.org> References: <38E2F801.548AAAF1@gorean.org> Date: Thu, 30 Mar 2000 00:00:57 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38E2F801.548AAAF1@gorean.org> Doug Barton writes: : --- /usr/src/share/skel/dot.cshrc Sat Mar 25 15:23:36 2000 : +++ /usr/src/etc/root/dot.cshrc Sat Mar 25 15:23:43 2000 : @@ -1,4 +1,4 @@ ... : if ($?prompt) then : # An interactive shell -- set some stuff up : + set prompt = "`hostname -s`# " : set filec : set history = 100 : set savehist = 100 Ahem. This should be `hostname -s %` unless this is only for root. I thought that this was for everybody. Only root should have a # prompt. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 29 23:22:52 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 BC57B37B6FE for ; Wed, 29 Mar 2000 23:22:49 -0800 (PST) (envelope-from imp@harmony.village.org) 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 AAA67109 for ; Thu, 30 Mar 2000 00:22:48 -0700 (MST) (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 AAA21918 for ; Thu, 30 Mar 2000 00:22:23 -0700 (MST) Message-Id: <200003300722.AAA21918@harmony.village.org> To: hackers@freebsd.org Subject: Shared /bin and /sbin Date: Thu, 30 Mar 2000 00:22:23 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a system that has one file system on it (eg everything is on /). I'm finding that a lot of space is wasted on the multiple static copies of libc in /sbin and /bin. I was thinking about building, for this system only, /bin and /sbin dynamic. Has anybody ever done this? What are the implications of doing this. I can't think of anything that would stop this from working, but I thought I'd run it by people here. I'm aiming to have a system that is part way between PicoBSD and normal FreeBSD in terms of size. I need more flexibility than the PicoBSD crunchgen binary has to offer, but don't nee all of FreeBSD for the application I'm deploying. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 0:24:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1-12.onmedia.com (mx1-12.onmedia.com [209.133.35.17]) by hub.freebsd.org (Postfix) with ESMTP id 6FAD237B5C2 for ; Thu, 30 Mar 2000 00:24:22 -0800 (PST) (envelope-from p_a_r@goplay.com) Received: from GP1 (root@localhost) by mx1-12.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id AAA20817; Thu, 30 Mar 2000 00:20:39 -0800 (PST) Received: from OnMedia Mail (GPX1) by mx1-12.onmedia.com ($Revision: 2.3 $) with OICP id 81876428; Thu, 30 Mar 2000 00:20:39 -0800 Subject: Re: BSD VS BDS Date: Thu, 30 Mar 2000 00:18:35 -0800 Message-Id: <81876428.13.1636@mx1-12.onmedia.com> Reply-To: "p_a_r" From: "p_a_r" To: Martin Cracauer Cc: hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok but i downloaded the 3.3-stable is there some problems whit that and whats so good in the new 4.0?? Martin Cracauer wrote on Tuesday March 28, 2000 at 12:52pm: >In <81491281.2.1636@mx1-12.onmedia.com>, p_a_r wrote: >> >> Can anyone tell me the differens in FreeBSD and NetBSD. I would like >> to set up 2 internet servers whitch one should i take? > >As long as you can't tell by yourself, you are usually better off with >FreeBSD, since it is easier to install and has more resources to >support new users (handbook, people on mailinglists, user >groups/people in your town). > >I think it is technically superiour in most ways that matter for me, >but seem from an observer coming from Linux (or worse), that is not as >relevant as the first point. > >As a side note, if you choose FreeBSD, take 4.0, not 3.4. > >Martin >-- >%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >Martin Cracauer http://www.cons.org/cracauer/ >BSD User Group Hamburg, Germany http://www.bsdhh.org/ +--------------------------------------------------------------------------+ | The coolest site for free home pages, email, chat, e-cards, movie info.. | | http://www.goplay.com - it's time to Go Play! | +--------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 0:48: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from swebase.com (mail.swebase.com [212.75.75.45]) by hub.freebsd.org (Postfix) with ESMTP id 6DC2F37B510 for ; Thu, 30 Mar 2000 00:48:00 -0800 (PST) (envelope-from kasper@swebase.com) Received: from ns1 [212.75.75.43] by swebase.com (SMTPD32-6.00) id A5729F000D2; Thu, 30 Mar 2000 10:50:58 +0200 From: "Kasper" To: Subject: DEFUNCT Date: Thu, 30 Mar 2000 10:51:23 +0200 Message-ID: <000d01bf9a25$205d0de0$2b4b4bd4@swebase.com> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is my system often go into defunct. I cant do anything and have to reboot it, please can anyone tell me what to do. I can not do a reboot. My server is a webserver whit perl, php. Below is a picture of top. PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 1 root 18 0 8264 8204 8 R 0 98.5 11.5 128:56 init 12001 root 2 0 1016 1016 824 R 0 0.9 1.4 0:00 top 11980 nobody 0 0 2496 2496 2208 S 0 0.1 3.5 0:00 httpd 11981 nobody 0 0 2416 2416 2128 S 0 0.1 3.3 0:00 httpd 2 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kflushd 3 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kupdate 4 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kpiod 5 root 0 0 0 0 0 SW 0 0.0 0.0 0:17 kswapd 6 root -20 -20 0 0 0 SW< 0 0.0 0.0 0:00 mdrecoveryd 314 root 0 0 0 0 0 Z 0 0.0 0.0 0:03 klogd 330 root 0 0 168 112 84 S 0 0.0 0.1 0:00 crond 346 root 0 0 84 0 0 SW 0 0.0 0.0 0:00 inetd 362 root 0 0 216 100 84 S 0 0.0 0.1 0:02 sshd 400 root 0 0 468 288 236 S 0 0.0 0.4 0:00 sendmail 463 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 464 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 465 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 466 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 467 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 468 root 0 0 68 0 0 SW 0 0.0 0.0 0:00 mingetty 535 root 0 0 0 0 0 Z 0 0.0 0.0 0:02 httpd 11363 nobody 0 0 0 0 0 Z 0 0.0 0.0 0:00 sendmail 11607 nobody 0 0 0 0 0 Z 0 0.0 0.0 0:00 sendmail 11612 nobody 0 0 0 0 0 Z 0 0.0 0.0 0:00 sendmail 11883 root 0 0 1228 1216 952 R 0 0.0 1.7 0:00 sshd 11885 alfred 0 0 984 984 768 S 0 0.0 1.3 0:00 bash 11896 root 0 0 920 920 716 S 0 0.0 1.2 0:00 su 11897 root 0 0 976 976 760 S 0 0.0 1.3 0:00 bash 11977 root 0 0 2196 2196 2112 S 0 0.0 3.0 0:00 httpd 11978 nobody 0 0 2412 2412 2128 S 0 0.0 3.3 0:00 httpd 11979 nobody 0 0 2416 2416 2132 S 0 0.0 3.3 0:00 httpd 11982 nobody 0 0 2412 2412 2148 S 0 0.0 3.3 0:00 httpd 11985 nobody 0 0 2584 2584 2376 S 0 0.0 3.6 0:00 httpd 11988 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 httpd 11993 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 shutdown 12002 nobody 0 0 2220 2220 2128 S 0 0.0 3.1 0:00 httpd ./kasper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 0:54:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EDCD637B59D for ; Thu, 30 Mar 2000 00:54:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA69320; Thu, 30 Mar 2000 00:54:06 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 00:54:06 -0800 (PST) From: Matthew Dillon Message-Id: <200003300854.AAA69320@apollo.backplane.com> To: "Kasper" Cc: Subject: Re: DEFUNCT References: <000d01bf9a25$205d0de0$2b4b4bd4@swebase.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Why is my system often go into defunct. I cant do anything and have to :reboot it, please can anyone tell me what to do. I can not do a reboot. : :My server is a webserver whit perl, php. : :Below is a picture of top. : : : PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND : 1 root 18 0 8264 8204 8 R 0 98.5 11.5 128:56 init :12001 root 2 0 1016 1016 824 R 0 0.9 1.4 0:00 top :11980 nobody 0 0 2496 2496 2208 S 0 0.1 3.5 0:00 httpd :11981 nobody 0 0 2416 2416 2128 S 0 0.1 3.3 0:00 httpd : 2 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kflushd : 3 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kupdate : 4 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kpiod : 5 root 0 0 0 0 0 SW 0 0.0 0.0 0:17 kswapd : 6 root -20 -20 0 0 0 SW< 0 0.0 0.0 0:00 :... This is a linux system, you have to ask your question on a linux mailing list (and you should probably provide more details when you do). The mailing list you posted to is a FreeBSD mailing list. Linux and FreeBSD are totally different systems. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 1: 1:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 8CF3D37B620; Thu, 30 Mar 2000 01:01:10 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com (linuxcare.canberra.net.au [203.29.91.49]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id SAA12035; Thu, 30 Mar 2000 18:30:28 +0930 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id TAA03023; Thu, 30 Mar 2000 19:01:16 +1000 (EST) (envelope-from grog) Date: Thu, 30 Mar 2000 18:31:16 +0930 From: Greg Lehey To: Kasper Cc: FreeBSD Questions Subject: Re: DEFUNCT Message-ID: <20000330183116.N978@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <000d01bf9a25$205d0de0$2b4b4bd4@swebase.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000d01bf9a25$205d0de0$2b4b4bd4@swebase.com>; from kasper@swebase.com on Thu, Mar 30, 2000 at 10:51:23AM +0200 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] [Forwarding to -questions; this isn't an in-depth technical discussions] On Thursday, 30 March 2000 at 10:51:23 +0200, Kasper wrote: > Why is my system often go into defunct. I cant do anything and have > to reboot it, please can anyone tell me what to do. I can not do a > reboot. > > My server is a webserver whit perl, php. > > Below is a picture of top. Please don't wrap the lines. It makes it difficult to read. > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 314 root 0 0 0 0 0 Z 0 0.0 0.0 0:03 klogd (etc). This process is a zombie (see the state Z). It has died, but its parent is misbehaving and hasn't buried it. You can usually get rid of zombies by getting rid of the parent as well and hoping that the grandparent buries the whole family; possibly the whole tribe may need to be exterminated. Top won't tell you who the parent is. You need ps for that. For example, to find the parent of process 2998, do: $ ps lp2998 UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1004 2998 978 0 10 0 612 220 wait I+ p3 0:00.00 sh -c ec '/usr/home/grog/mutt-mojave-978-3 The parent is PPID (978 in this case). This one isn't a zombie, but in your case you will find the parent of process 314 (in this case). It would be interesting to see what the process is. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html 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 Thu Mar 30 1:37:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id A6BB137BB60 for ; Thu, 30 Mar 2000 01:37:20 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id TAA83436; Thu, 30 Mar 2000 19:37:06 +1000 (EST) (envelope-from sue) Date: Thu, 30 Mar 2000 19:37:01 +1000 From: Sue Blake To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files Message-ID: <20000330193658.V69444@welearn.com.au> Mail-Followup-To: Doug Barton , freebsd-hackers@FreeBSD.ORG References: <38E2F801.548AAAF1@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38E2F801.548AAAF1@gorean.org>; from Doug Barton on Wed, Mar 29, 2000 at 10:45:21PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 10:45:21PM -0800, Doug Barton wrote: > Commentary on my files. . . Using allexport instead of an explicit > 'export' for every variable makes the file easier to read, and gives a > novice user one less thing to worry about. I see your point, and offer an alternative view. I don't consider myself a novice user, but when I was I'd heard of export, yet I've still not heard of allexport until your email. (OK, I probably read about it and ignored it). My fear would be that turning something on in one part of the file and off again later is likely to assist novices to shoot themselves in the foot by removing only one of these lines. In one sense it simplifies, but it does so by making the file's structure more complex. Not too much so, but avoidable. The multiple exports take up more space and don't look as clever, but their purpose is crystal clear and one goof doesn't ruin the lot of them. It would be a good addition to a separate file with lengthy comments, supplied as an alternative and/or learning exercise. I might pinch your idea for that one day :-) -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 1:58:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 6BC1637B7D7 for ; Thu, 30 Mar 2000 01:58:29 -0800 (PST) (envelope-from transmogrify@sympatico.ca) Received: from sympatico.ca ([207.236.126.23]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20000330095828.GESA911.tomts2-srv.bellnexxia.net@sympatico.ca> for ; Thu, 30 Mar 2000 04:58:28 -0500 Message-ID: <38E324F7.88CC1065@sympatico.ca> Date: Thu, 30 Mar 2000 04:57:11 -0500 From: "[ -dp- ]" X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: Shoot the messenger.. Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG  
 Could anyone offer me some idea of what is happening here? Kernel is 3.4-Stable . Problem just started about a month ago.
Problem only occurs under low loads.

Mar 30 03:25:35 dissent /kernel: wd1s1f: wdstart: timeout waiting to give command writing fsbn 196672 of 196672-196687
(wd1s1 bn 7364672; cn 458 tn 109 sn 35) (status d0<busy,rdy,seekdone> error 1<no_dam>)
Mar 30 03:25:35 dissent /kernel: wd1s1f: wdstart: timeout waiting to give command writing fsbn 196672 of 196672-196687
(wd1s1 bn 7364672; cn 458 tn 109 sn 35) (status d0<busy,rdy,seekdone> error 1<no_dam>)
wd1s1a: wdstart: timeout waiting to give command writing fsbn 131136 of 131136-131151
(wd1s1 bn 131136; cn 8 tn 41 sn 33) (status d0<busy,rdy,seekdone> error 1<no_dam>)
Mar 30 04:40:19 dissent /kernel: wd1s1a: wdstart: timeout waiting to give command writing fsbn 131136 of 131136-131151
(wd1s1 bn 131136; cn 8 tn 41 sn 33) (status d0<busy,rdy,seekdone> error 1<no_dam>)
Mar 30 04:40:19 dissent /kernel: wd1s1a: wdstart: timeout waiting to give command writing fsbn 131136 of 131136-131151
(wd1s1 bn 131136; cn 8 tn 41 sn 33) (status d0<busy,rdy,seekdone> error 1<no_dam>)
Mar 30 04:40:19 dissent /kernel: sio0: 744 more tty-level buffer overflows (total 744)
Mar 30 04:40:19 dissent /kernel: sio0: 744 more tty-level buffer overflows (total 744)
Mar 30 04:40:19 dissent /kernel: sio0: 744 more tty-level buffer overflows (total 744)

 [ - deadpoint - ]

=============================================================
Don't underestimate the power of
                 stupid people in large groups.

GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F  D5EC 3D39 F274 4AA3 E8B9
Public Key available here: [ click ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 2:16:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 186A437B6CC for ; Thu, 30 Mar 2000 02:16:52 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id MAA01060; Thu, 30 Mar 2000 12:16:45 +0200 (CEST) Date: Thu, 30 Mar 2000 12:16:44 +0200 From: Martin Cracauer To: p_a_r Cc: Martin Cracauer , hackers@FreeBSD.ORG Subject: Re: BSD VS BDS Message-ID: <20000330121644.B1022@cons.org> References: <81876428.13.1636@mx1-12.onmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <81876428.13.1636@mx1-12.onmedia.com>; from p_a_r@goplay.com on Thu, Mar 30, 2000 at 12:18:35AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <81876428.13.1636@mx1-12.onmedia.com>, p_a_r wrote: > Ok but i downloaded the 3.3-stable is there some problems whit that > and whats so good in the new 4.0?? Oh no, not again. 3.3 is not "bad", but I would recommend updating to 4.0/4.1 instead of 3.4/3.5 when the time comes. Higher 3.x releases - in my opinion - suffer a little from not enough testing when teh developers were already approching 4.0. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 2:34:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 744D037B613 for ; Thu, 30 Mar 2000 02:34:50 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12acHi-000533-00; Thu, 30 Mar 2000 12:34:42 +0200 From: Sheldon Hearn To: "[ -dp- ]" Cc: hackers@FreeBSD.org Subject: Re: Shoot the messenger.. In-reply-to: Your message of "Thu, 30 Mar 2000 04:57:11 EST." <38E324F7.88CC1065@sympatico.ca> Date: Thu, 30 Mar 2000 12:34:42 +0200 Message-ID: <19408.954412482@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Mar 2000 04:57:11 EST, "[ -dp- ]" wrote: >
 Could anyone offer me some idea of what is happening here? Kernel > is 3.4-Stable . Problem just started about a month ago. Not on this mailing list, no. Please redirect your question (in plain text) to the freebsd-questions mailing list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 3: 8:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 4D42C37B739 for ; Thu, 30 Mar 2000 03:08:26 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 91390 invoked by uid 1001); 30 Mar 2000 11:08:24 -0000 Date: 30 Mar 2000 03:08:24 -0800 Date: Thu, 30 Mar 2000 03:08:24 -0800 From: Bill Swingle To: hackers@freebsd.org Subject: hardware donation needed Message-ID: <20000330030823.A91101@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all, In the past few months we've received quite a few test machines from different companies requesting that we verify that FreeBSD runs well on their hardware. This on top of the normal circus of machines that we use for release testing and development has exceeded our small network's capacity. Right now we're in great need of a few 10/100 switchs that we can use to expand our test network. We're not picky, we'll take what we can get. So if you have some equipment that you can donate to the project please contact me directly. -Bill -- -=| --- B i l l S w i n g l e --- http://www.freebsd.org/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Senior Systems Administrator - The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 3:19:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 379B337B690 for ; Thu, 30 Mar 2000 03:19:34 -0800 (PST) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id DAA27590; Thu, 30 Mar 2000 03:19:21 -0800 (PST) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id DAA14184; Thu, 30 Mar 2000 03:19:32 -0800 (PST) Message-Id: <200003301119.DAA14184@papermill.wrs.com> To: Martin Cracauer Cc: hackers@FreeBSD.ORG From: David Holloway Subject: Re: BSD VS BDS In-reply-to: Your message of "Thu, 30 Mar 2000 12:16:44 +0200." <20000330121644.B1022@cons.org> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Thu, 30 Mar 2000 03:19:31 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh I completely disagree. Many serious orgnanizations and people concerned with stability work with 3.x and plan on sticking with 3.x until many of the serious changes to 4.0 have proven themselves. The gcc (2.9.x -- 3.x) compiler for example, has only just recently become as rock solid as the standard gcc 2.7.2.3 for freebsd 3.x In message <20000330121644.B1022@cons.org>, Martin Cracauer writes: >In <81876428.13.1636@mx1-12.onmedia.com>, p_a_r wrote: >> Ok but i downloaded the 3.3-stable is there some problems whit that >> and whats so good in the new 4.0?? > >Oh no, not again. 3.3 is not "bad", but I would recommend updating to >4.0/4.1 instead of 3.4/3.5 when the time comes. Higher 3.x releases - >in my opinion - suffer a little from not enough testing when teh >developers were already approching 4.0. > >Martin >-- >%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >Martin Cracauer http://www.cons.org/cracauer/ > Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 > > >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 Thu Mar 30 3:24:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id DF79A37B612 for ; Thu, 30 Mar 2000 03:24:04 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id NAA01827; Thu, 30 Mar 2000 13:23:56 +0200 (CEST) Date: Thu, 30 Mar 2000 13:23:56 +0200 From: Martin Cracauer To: David Holloway Cc: Martin Cracauer , hackers@FreeBSD.ORG Subject: Re: BSD VS BDS Message-ID: <20000330132355.A1815@cons.org> References: <20000330121644.B1022@cons.org> <200003301119.DAA14184@papermill.wrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003301119.DAA14184@papermill.wrs.com>; from davidhol@windriver.com on Thu, Mar 30, 2000 at 03:19:31AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <200003301119.DAA14184@papermill.wrs.com>, David Holloway wrote: > Oh I completely disagree. > Many serious orgnanizations and people concerned > with stability work with 3.x and plan on sticking with > 3.x until many of the serious changes to 4.0 have proven > themselves. > > The gcc (2.9.x -- 3.x) compiler for example, has only just recently become > as rock solid as the standard gcc 2.7.2.3 for freebsd 3.x Um, yes, I would also like the compiler do move a little more conservativly, and there is some hardware that doesn't work in 4.x, but other than that I don't like 3.4-STABLE and don't think it is wise to update on older 3.x release to it due to stability. See the discussion on -stable and let us not get into the same flamewar here. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 3:37:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from explorer.tip.CSIRO.AU (explorer.tip.CSIRO.AU [130.155.191.10]) by hub.freebsd.org (Postfix) with ESMTP id 85EA237B72A for ; Thu, 30 Mar 2000 03:37:29 -0800 (PST) (envelope-from amy@explorer.tip.CSIRO.AU) Received: from explorer.tip.CSIRO.AU (localhost [127.0.0.1]) by explorer.tip.CSIRO.AU (8.9.3/8.9.1) with ESMTP id VAA82294; Thu, 30 Mar 2000 21:37:21 +1000 (EST) (envelope-from amy@explorer.tip.CSIRO.AU) Message-Id: <200003301137.VAA82294@explorer.tip.CSIRO.AU> To: freebsd-hackers@FreeBSD.ORG Cc: amy@explorer.tip.CSIRO.AU Subject: 4.0-RELEASE, PCMCIA, DHCP and IP MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <82290.954416240.1@explorer.tip.CSIRO.AU> Date: Thu, 30 Mar 2000 21:37:20 +1000 From: "Shaun Amy, CSIRO TIP/ATNF" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, If the subject line hasn't put you off then no doubt after reading this you will think I am crazy in a fairly standard configuration almost works but for the networking... Basically I am trying to install 4.0-RELEASE (off a CD I burnt from the ISO image whilst I wait for the WC CD kit) on a Dell Latitude CPi laptop (which has run FreeBSD 2.2.x and FreeBSD 3.2 in the past). I boot off floppy, do the install of the CD and everything works just fine, including finding the PCMCIA ethernet card (3Com 3C589B which I know works with FreeBSD) and using DHCP to get the correct network parameters over the network. The only problem is (and this sounds silly) is that with the PCMCIA card configured with DHCP addresses it won't pass any IP traffic, even a ping to another machine on the same subnet fails (so it isn't a routing issue). I have done a few installs to try different things and even configuring the IP address manually late in the sysinstall phase still exhibits the same problem. The interface config looks just fine (even after installation using the shell on vty4) but it won't pass IP traffic from what I can tell. I know the card is OK, the cable is OK, the hub/switch is OK as I can boot Win2K and it gets its address from DHCP and works fine. I think I understand networking and do a fair bit of Unix administration so I don't think/hope it is something I have overlooked but... Sorry that there isn't much to go on, but I am out of ideas at the moment and am wondering if anyone has seen something similar? Many thanks, Shaun. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 3:52:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (vpn.iscape.fi [195.170.146.67]) by hub.freebsd.org (Postfix) with ESMTP id 83EBE37B6E3 for ; Thu, 30 Mar 2000 03:52:20 -0800 (PST) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id OAA10716; Thu, 30 Mar 2000 14:48:48 +0300 (EEST) (envelope-from will) To: imp@village.org (Warner Losh) Cc: hackers@freebsd.org Subject: Re: Shared /bin and /sbin References: <200003300722.AAA21918@harmony.village.org> From: Ville-Pertti Keinonen Date: 30 Mar 2000 14:48:48 +0300 In-Reply-To: imp@village.org's message of "30 Mar 2000 10:23:30 +0300" Message-ID: <86hfdovftr.fsf@not.demophon.com> Lines: 16 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG imp@village.org (Warner Losh) writes: > I have a system that has one file system on it (eg everything is on > /). I'm finding that a lot of space is wasted on the multiple static > copies of libc in /sbin and /bin. I was thinking about building, for > this system only, /bin and /sbin dynamic. Has anybody ever done this? > What are the implications of doing this. I can't think of anything > that would stop this from working, but I thought I'd run it by people > here. I've done this, and did manage to get an almost complete system into a reasonably small space. It was 2.2.x, but I wouldn't expect any special new requirements with more current versions. IIRC it didn't require much more than fixing the appropriate Makefile.incs in the source tree. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 5:11:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 4D70337B645 for ; Thu, 30 Mar 2000 05:11:16 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Thu, 30 Mar 2000 07:10:51 -0600 From: Richard Wackerbarth To: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.0-RELEASE, PCMCIA, DHCP and IP Date: Thu, 30 Mar 2000 06:59:30 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain Cc: amy@explorer.tip.CSIRO.AU References: <200003301137.VAA82294@explorer.tip.CSIRO.AU> In-Reply-To: <200003301137.VAA82294@explorer.tip.CSIRO.AU> MIME-Version: 1.0 Message-Id: <00033007104300.07410@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Mar 2000, Shaun Amy, CSIRO TIP/ATNF wrote: > Basically I am trying to install 4.0-RELEASE (off a CD I burnt from the ISO > image whilst I wait for the WC CD kit) on a Dell Latitude CPi laptop (which > has run FreeBSD 2.2.x and FreeBSD 3.2 in the past). I boot off floppy, do > the install of the CD and everything works just fine, including finding the > PCMCIA ethernet card (3Com 3C589B which I know works with FreeBSD) and using > DHCP to get the correct network parameters over the network. > > The only problem is (and this sounds silly) is that with the PCMCIA card > configured with DHCP addresses it won't pass any IP traffic, even a ping to > another machine on the same subnet fails (so it isn't a routing issue). I saw similar problems on my laptop. I was trying to do a net install :-( I think that the problem is related to interrupts. From what I could see, they are getting lost. I gave up trying the net install. Since you already have a CD to get the info onto the HD, you should be able to investigate it further. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 6: 3:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 24BB337B97F for ; Thu, 30 Mar 2000 06:03:47 -0800 (PST) (envelope-from lloyd@brunel.uk1.vbc.net) Received: from localhost (lloyd@localhost) by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id PAA34391 for ; Thu, 30 Mar 2000 15:03:44 +0100 (BST) Date: Thu, 30 Mar 2000 15:03:44 +0100 (BST) From: Lloyd Rennie To: hackers@freebsd.org Subject: Mirror requirements 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 sent this to -questions, but have received no reply. Sorry to bug y'all, but... What are the hardware and bandwidth requirements to maintain a full FreeBSD mirror site? -- Lloyd Rennie VBCnet GB Ltd lloyd@vbc.net tel +44 (0) 117 929 1316 http://www.vbc.net fax +44 (0) 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 6:44:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from green.wl.vg (green.wl.vg.49.203.204.in-addr.arpa [204.203.49.94]) by hub.freebsd.org (Postfix) with ESMTP id 5C1E337B6FB for ; Thu, 30 Mar 2000 06:44:33 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Received: from whetstonelogic.com (patrick [205.252.46.171]) by green.wl.vg (8.9.3/8.9.3) with ESMTP id GAA09883; Thu, 30 Mar 2000 06:43:09 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Message-ID: <38E367E2.2FC11B7C@whetstonelogic.com> Date: Thu, 30 Mar 2000 09:42:42 -0500 From: Patrick Gardella Organization: Whetstone Logic, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Lloyd Rennie Cc: hackers@FreeBSD.ORG Subject: Re: Mirror requirements References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lloyd Rennie wrote: > > I sent this to -questions, but have received no reply. Sorry to bug > y'all, but... > > What are the hardware and bandwidth requirements to maintain a full > FreeBSD mirror site? Having asked this before, I can try to answer it... Hardware: Disk space to hold the parts you want to mirror. Are you looking to be just an FTP mirror, a WWW mirror (about 8 megs), a CVSUP mirror, or some combination of all of these? I would say that a safe bet would be an 8 gig HD for all of them. Bandwidth: No one has ever done a study of what it takes. Generally, you would need a good, stable connection. -- Patrick ---------- Patrick Gardella patrick@whetstonelogic.com VP-Technology patrick@freebsd.org Whetstone Logic, Inc. This space intentionally left blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 7:11:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id C85A737BCFE for ; Thu, 30 Mar 2000 07:11:47 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id BB1CC3E25; Thu, 30 Mar 2000 17:11:43 +0200 (CEST) Date: Thu, 30 Mar 2000 17:11:43 +0200 From: Jesper Skriver To: Patrick Gardella Cc: Lloyd Rennie , hackers@FreeBSD.ORG Subject: Re: Mirror requirements Message-ID: <20000330171143.A48758@skriver.dk> References: <38E367E2.2FC11B7C@whetstonelogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38E367E2.2FC11B7C@whetstonelogic.com>; from patrick@whetstonelogic.com on Thu, Mar 30, 2000 at 09:42:42AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 09:42:42AM -0500, Patrick Gardella wrote: > Lloyd Rennie wrote: > > > > I sent this to -questions, but have received no reply. Sorry to bug > > y'all, but... > > > > What are the hardware and bandwidth requirements to maintain a full > > FreeBSD mirror site? > > Having asked this before, I can try to answer it... > > Hardware: Disk space to hold the parts you want to mirror. Are you > looking to be just an FTP mirror, a WWW mirror (about 8 megs), a CVSUP > mirror, or some combination of all of these? I would say that a safe > bet would be an 8 gig HD for all of them. I keep a partial ftp mirror, and it barely fits 20 GB ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 8:47:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ludwig.troikanetworks.com (host03.troikanetworks.com [12.31.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 3011337B73E for ; Thu, 30 Mar 2000 08:47:47 -0800 (PST) (envelope-from ericp@troikanetworks.com) Received: by host03.troikanetworks.com with Internet Mail Service (5.5.2650.21) id ; Thu, 30 Mar 2000 08:47:59 -0800 Message-ID: From: Eric Peterson To: "'hackers@freebsd.org'" Subject: Deferred procedure call available? Date: Thu, 30 Mar 2000 08:47:52 -0800 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 Hi, Is there a facility in FreeBSD to do a deferred procedure call? Sometimes called "task queues" or "deferred callbacks", they allow an interrupt handler to schedule a (possibly predefined) function to be called outside the context of the interrupt. I dug a bit and found some "software interrupt" functions (swi_*()), but they are just a list of functions to be called immediately (no deferral); they don't seem to be of help to me. Regards, Eric -- Eric Peterson - Troika Networks, Inc. ericp@troikanetworks.com PGP: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x4DA8EEF1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 9:38:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 06DA637B56A; Thu, 30 Mar 2000 09:38:16 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id JAA60034; Thu, 30 Mar 2000 09:38:10 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E39101.D62147C2@gorean.org> Date: Thu, 30 Mar 2000 09:38:09 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG, rwatson@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files References: <38E2F801.548AAAF1@gorean.org> <200003300700.AAA21734@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <38E2F801.548AAAF1@gorean.org> Doug Barton writes: > : --- /usr/src/share/skel/dot.cshrc Sat Mar 25 15:23:36 2000 > : +++ /usr/src/etc/root/dot.cshrc Sat Mar 25 15:23:43 2000 > : @@ -1,4 +1,4 @@ > ... > : if ($?prompt) then > : # An interactive shell -- set some stuff up > : + set prompt = "`hostname -s`# " > : set filec > : set history = 100 > : set savehist = 100 > > Ahem. This should be `hostname -s %` unless this is only for root. I > thought that this was for everybody. Only root should have a # prompt. Grrrfl. This is entirely my fault. I diff'ed the normal user's and the root user's dot.cshrc files. Sorry Robert, I wasn't looking carefully enough. (I'm not a csh user, I think I added that disclaimer in there somewhere... :) The sh files that were attached to my post got much more careful scrutiny, rest assured. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 9:58:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 8DD0437B738 for ; Thu, 30 Mar 2000 09:58:47 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id JAA60087; Thu, 30 Mar 2000 09:58:29 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E395C5.DDBFCEB7@gorean.org> Date: Thu, 30 Mar 2000 09:58:29 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sue Blake Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files References: <38E2F801.548AAAF1@gorean.org> <20000330193658.V69444@welearn.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sue Blake wrote: > > On Wed, Mar 29, 2000 at 10:45:21PM -0800, Doug Barton wrote: > > > > > Commentary on my files. . . Using allexport instead of an explicit > > 'export' for every variable makes the file easier to read, and gives a > > novice user one less thing to worry about. > > I see your point, and offer an alternative view. > > I don't consider myself a novice user, but when I was I'd heard of > export, yet I've still not heard of allexport until your email. > (OK, I probably read about it and ignored it). > > My fear would be that turning something on in one part of the file and > off again later is likely to assist novices to shoot themselves in the > foot by removing only one of these lines. Actually it's much more likely that a novice user would fail to export a variable, which would result in it not working at all. The other alternatives are fairly harmless. First the user doesn't see/understand the allexport lines, and exports their variables explicitly anyway. They work. The user deletes the line that turns allexport off. Everything still works, and they have a few too many harmless shell settings exported into their environment. The user deletes the line that turns allexport on. Nothing works, the user goes and looks again at the file. Hopefully they see the line that turns it off, and figure it out. Or, maybe they see that the variables aren't exported, know how to export them, and does so. The number of possible outcomes where this fails to work are actually really small, compared to the large number of outcomes where it works. > In one sense it simplifies, > but it does so by making the file's structure more complex. You can't possibly support the argument that it's more complex. How can this: allexport on var1=foo var2=bar var3=baz var4=bic var5=schick allexport off Be more complex than: var1=foo export var1 var2=bar export var2 var3=baz export var3 var4=bic export var4 var5=schick export var5 > Not too > much so, but avoidable. The multiple exports take up more space and > don't look as clever, but their purpose is crystal clear and one goof > doesn't ruin the lot of them. I've addressed the "one goof" issue above. This isn't a matter of "looking clever," rather it's a matter of reducing the number of ways the user can shoot themselves in the foot, and to make the variables being set stand out more clearly. > It would be a good addition to a separate file with lengthy comments, > supplied as an alternative and/or learning exercise. Actually I added the comments I did to the file (in more places than just the allexport lines) to help make things more clear. If you feel that more verbose comments are warranted, I'm sure we would all welcome your suggestions. But shooting down a simple solution that solves several problems at the same time and has little or no down side just because you don't understand it isn't really constructive criticism. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 10:21: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 05AAB37BE08 for ; Thu, 30 Mar 2000 10:20:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id NAA91182; Thu, 30 Mar 2000 13:20:14 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003301820.NAA91182@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000330171143.A48758@skriver.dk> Date: Thu, 30 Mar 2000 13:20:13 -0500 (EST) From: John Baldwin To: Jesper Skriver Subject: Re: Mirror requirements Cc: hackers@FreeBSD.org, Lloyd Rennie , Patrick Gardella Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Mar-00 Jesper Skriver wrote: > On Thu, Mar 30, 2000 at 09:42:42AM -0500, Patrick Gardella wrote: >> Lloyd Rennie wrote: >> > >> > I sent this to -questions, but have received no reply. Sorry to bug >> > y'all, but... >> > >> > What are the hardware and bandwidth requirements to maintain a full >> > FreeBSD mirror site? >> >> Having asked this before, I can try to answer it... >> >> Hardware: Disk space to hold the parts you want to mirror. Are you >> looking to be just an FTP mirror, a WWW mirror (about 8 megs), a CVSUP >> mirror, or some combination of all of these? I would say that a safe >> bet would be an 8 gig HD for all of them. > > I keep a partial ftp mirror, and it barely fits 20 GB ... I was about to say. On ftp3.FreeBSD.org we use 3 9 Gb SCSI disks in a vinum stripe to hold just XFree86 and a partial mirror of FreeBSD and it runs at about 86% capacity. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Mar 30 10:39: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from griffin.aciri.org (griffin.aciri.org [192.150.187.12]) by hub.freebsd.org (Postfix) with ESMTP id 411D737BDF2; Thu, 30 Mar 2000 10:38:59 -0800 (PST) (envelope-from wilbertdg@hetnet.nl) Received: from hetnet.nl (localhost.aciri.org [127.0.0.1]) by griffin.aciri.org (8.9.3/8.9.3) with ESMTP id KAA45055; Thu, 30 Mar 2000 10:38:58 -0800 (PST) (envelope-from wilbertdg@hetnet.nl) Message-ID: <38E39F42.823A681B@hetnet.nl> Date: Thu, 30 Mar 2000 10:38:58 -0800 From: Wilbert de Graaf X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: free-bsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: The socket structure & igmpv3 Content-Type: multipart/mixed; boundary="------------CE6875120F7242AFB36C4312" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------CE6875120F7242AFB36C4312 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all, I'm working on an implementation of the IGMPv3 protocol in the Net/3 stack, and several questions popped up. The first one is about the socket structure. The IGMPv3 protocol allows a process to set (ip)source filters, which is a list of ip addresses of sources which indicates the process is not (exclude mode) or just (include mode) interested to receive data from those sources, on that particular socket. The igmpv3 extensions to the socket api allow you to add source filters to sockets subscribed to one or more multicast groups. So a process identifies a socket with a descriptor, which is a index into an array of pointers to file structures. These file structures reside in the kernel and could be shared among processes. Now I'm thinking about where to keep this sourcfilter-list. If it's possible to share a socket between processes it could be that one process is interested, but another is not. On the other hand, I believe the filter is a per socket and if it's shared ... so is the filter. So my question is ... Is it true that such a filter should be attached / stored within the socket datastructure ? Thanks in advance, Wilbert Btw. Besides the fact that a sourcefilter-list per socket should be implemented, there should also be a sourcefilter-list per (the in_multi{} structure). This in order to generate IGMPv3 reports, or maybe in later stage to do filtering at a lower level in order to improve performance. --------------CE6875120F7242AFB36C4312 Content-Type: text/x-vcard; charset=us-ascii; name="wilbertdg.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Wilbert de Graaf Content-Disposition: attachment; filename="wilbertdg.vcf" begin:vcard n:de Graaf;Wilbert x-mozilla-html:FALSE url:http://home.hetnet.nl/~wilbertdg/ org:KPN Research adr:;;;;;; version:2.1 email;internet:wilbertdg@hetnet.nl x-mozilla-cpt:;0 fn:Wilbert de Graaf end:vcard --------------CE6875120F7242AFB36C4312-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 10:53:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id E433737BDBD for ; Thu, 30 Mar 2000 10:53:21 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: by ada.eu.org (Postfix, from userid 1000) id 280EA19094; Thu, 30 Mar 2000 20:53:20 +0200 (CEST) To: freebsd-hackers@freebsd.org Subject: Remote GDB and call stack Date: 30 Mar 2000 20:53:19 +0200 Lines: 28 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-30-20-53-20+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am investigating i386/17228 (Installation floppies hang up on Compaq Armada V300 laptop) that I submitted. I built a custom kernel with no SCSI at all (it had been suggested that NCR probes could be the cause of the lockups) and with remote gdb enabled. I can enter remote gdb just fine using the keyboard interrupt, but the call stack is pretty useless to me: Program received signal SIGTRAP, Trace/breakpoint trap. 0xc02060ed in Debugger () (gdb) where #0 0xc02060ed in Debugger () #1 0xc02030f2 in scgetc (sc=0xc027d520, flags=2) at ../../dev/syscons/syscons.c:3134 #2 0xc0200169 in sckbdevent (thiskbd=0xc0276280, event=0, arg=0xc027d520) at ../../dev/syscons/syscons.c:634 #3 0xc01f82e6 in atkbd_intr () #4 0xc021add4 in atkbd_isa_intr () Is there a way to know what was executing before the keyboard interrupt and go there? I need to step in the code, because the freeze is a real one, no keyboard interrupts will be generated anymore. Sam -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 11:11:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 964AD37BDFD for ; Thu, 30 Mar 2000 11:11:36 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 551A019094; Thu, 30 Mar 2000 21:11:35 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id D20C8504; Thu, 30 Mar 2000 21:11:34 +0200 (CEST) Date: Thu, 30 Mar 2000 21:11:34 +0200 To: freebsd-hackers@freebsd.org Subject: Re: Remote GDB and call stack References: <2000-03-30-20-53-20+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <2000-03-30-20-53-20+trackit+sam@inf.enst.fr>; from sam@inf.enst.fr on Thu, Mar 30, 2000 at 08:53:19PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-30-21-11-34+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30/03, Samuel Tardieu wrote: | I can enter remote gdb just fine using the keyboard interrupt, but the | call stack is pretty useless to me: Nevermind, setting breakpoints when not knowing at all where it blocks is a pain but the dichotomy method should work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 11:15: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg137-078.ricochet.net [204.179.137.78]) by hub.freebsd.org (Postfix) with ESMTP id A7A0537BCF9 for ; Thu, 30 Mar 2000 11:14:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00571; Thu, 30 Mar 2000 10:21:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003301821.KAA00571@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Eric Peterson Cc: "'hackers@freebsd.org'" Subject: Re: Deferred procedure call available? In-reply-to: Your message of "Thu, 30 Mar 2000 08:47:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 10:21:34 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > Is there a facility in FreeBSD to do a deferred procedure call? > Sometimes called "task queues" > or "deferred callbacks", they allow an interrupt handler to schedule > a (possibly predefined) function to > be called outside the context of the interrupt. > > I dug a bit and found some "software interrupt" functions (swi_*()), > but they are just a list of functions to be > called immediately (no deferral); they don't seem to be of help to > me. Try timeout(9) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 11:17:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C169F37BF9C for ; Thu, 30 Mar 2000 11:17:09 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA19478; Thu, 30 Mar 2000 11:16:59 -0800 (PST) Date: Thu, 30 Mar 2000 11:16:58 -0800 (PST) From: Julian Elischer To: Samuel Tardieu Cc: freebsd-hackers@freebsd.org Subject: Re: Remote GDB and call stack In-Reply-To: <2000-03-30-21-11-34+trackit+sam@inf.enst.fr> 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 sometimes the low tech answer of using ^T can help On Thu, 30 Mar 2000, Samuel Tardieu wrote: > On 30/03, Samuel Tardieu wrote: > > | I can enter remote gdb just fine using the keyboard interrupt, but the > | call stack is pretty useless to me: > > Nevermind, setting breakpoints when not knowing at all where it blocks > is a pain but the dichotomy method should work. > > > > 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 Thu Mar 30 11:42:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 76B4B37BF1B for ; Thu, 30 Mar 2000 11:42:14 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA96102; Thu, 30 Mar 2000 14:41:36 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <38E395C5.DDBFCEB7@gorean.org> References: <38E2F801.548AAAF1@gorean.org> <20000330193658.V69444@welearn.com.au> <38E395C5.DDBFCEB7@gorean.org> Date: Thu, 30 Mar 2000 14:42:26 -0500 To: Doug Barton , Sue Blake From: Garance A Drosihn Subject: Re: Proposed new Bourne shell init files Cc: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:58 AM -0800 3/30/00, Doug Barton wrote: >Sue Blake wrote: > > > > On Wed, Mar 29, 2000 at 10:45:21PM -0800, Doug Barton wrote: > > > Commentary on my files. . . Using allexport instead of an explicit > > > 'export' for every variable makes the file easier to read, and gives > > > a novice user one less thing to worry about. > > > > I see your point, and offer an alternative view. > > > > My fear would be that turning something on in one part of the file and > > off again later is likely to assist novices to shoot themselves in the > > foot by removing only one of these lines. > >Actually it's much more likely that a novice user would fail to export >a variable, which would result in it not working at all. If the novice user is writing their own script, then they need to understand exporting variables. >The other alternatives are fairly harmless. First the user doesn't >see/understand the allexport lines, and exports their variables >explicitly anyway. They work. ...and setting allexport has not helped them. >The user deletes the line that turns allexport off. Everything >still works, and they have a few too many harmless shell settings >exported into their environment. This is where I'd disagree. Some scripts define variables that they really do not expect to be exported. Exporting those variables is not always "harmless", and (speaking from experience) can be quite confusing to track down. This is particularly true when a user is dealing with scripts that they did not write. > > In one sense it simplifies, > > but it does so by making the file's structure more complex. > >You can't possibly support the argument that it's more complex. It is more complex in the sense that the user has to realize that "allexport" is changing a basic shell behavior. If a person does not realize the connection between: var1=foo export var1 then how is it "more obvious" to them what is happening with: allexport on var1=foo allexport off The first one is explicitly stating what it's doing, whether or not the user understands the significance of "export". If you don't understand the significance of "export", then you're certainly not going to understand what "allexport" is there for. This is probably a matter of personal opinion, but then you did ask for people's opinions... :-) > > The multiple exports take up more space and don't look > > as clever, but their purpose is crystal clear and one goof > > doesn't ruin the lot of them. > >I've addressed the "one goof" issue above. This isn't a matter of >"looking clever," rather it's a matter of reducing the number of ways >the user can shoot themselves in the foot, and to make the variables >being set stand out more clearly. Again, as you were asking for opinions, I'd say that using "allexport" does nothing to reduce the number of ways the user can shoot themselves in the foot. It does reduce the clutter somewhat, but I would rather have the explicit 'export's than the reduced clutter. Another way to reduce clutter would be to export all the variables at once, at the end, but I am not overly fond of that idea either. (even if that is what I do for some of my scripts, I wouldn't put that in a default script for all users...). > > It would be a good addition to a separate file with lengthy > > comments, supplied as an alternative and/or learning exercise. > >Actually I added the comments I did to the file (in more places than >just the allexport lines) to help make things more clear. If you feel >that more verbose comments are warranted, I'm sure we would all welcome >your suggestions. But shooting down a simple solution that solves >several problems at the same time and has little or no down side just >because you don't understand it isn't really constructive criticism. The fact that *you* THINK it has no downside does not mean everyone will agree that it has no downside. If someone thinks there is a downside, then it is definitely constructive criticism for them to say so. You can't very well ask for opinions and then dismiss opinions as "not really constructive" just because they do not agree with some basic premise of your position. (I'm not really sure if your above paragraph refers to "allexport", or if it refers to the suggestion of a separate file with lengthy comments. In either case it seems very odd that you explicitly asked for comments, someone wrote up some perfectly reasonable comments, and you react by saying the person "don't understand it" and thus their comments aren't "really constructive criticism". Very odd) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 11:46:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id DCEE037BFE0 for ; Thu, 30 Mar 2000 11:46:15 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: by ada.eu.org (Postfix, from userid 1000) id 8A92619094; Thu, 30 Mar 2000 21:46:09 +0200 (CEST) To: Eric Peterson Cc: "'hackers@freebsd.org'" Subject: Re: Deferred procedure call available? References: Date: 30 Mar 2000 21:46:09 +0200 In-Reply-To: Eric Peterson's message of "Thu, 30 Mar 2000 08:47:52 -0800" Lines: 15 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-30-21-46-09+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Eric" == Eric Peterson writes: Eric> Sometimes called "task queues" or "deferred callbacks", they Eric> allow an interrupt handler to schedule a (possibly predefined) Eric> function to be called outside the context of the interrupt. (not an answer, just a suggestion) Is there anything you cannot do with a userland program, that will be resumed by the interrupt handler? Doing this even gives you the possibility of choosing the priority of the deferred handler relative to other handler and regular processes (as eCos does). Sam -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 11:53:41 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 012EA37B862 for ; Thu, 30 Mar 2000 11:53:35 -0800 (PST) (envelope-from imp@harmony.village.org) 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 MAA69757; Thu, 30 Mar 2000 12:53:32 -0700 (MST) (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 MAA26234; Thu, 30 Mar 2000 12:53:05 -0700 (MST) Message-Id: <200003301953.MAA26234@harmony.village.org> To: "Shaun Amy, CSIRO TIP/ATNF" Subject: Re: 4.0-RELEASE, PCMCIA, DHCP and IP Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 21:37:20 +1000." <200003301137.VAA82294@explorer.tip.CSIRO.AU> References: <200003301137.VAA82294@explorer.tip.CSIRO.AU> Date: Thu, 30 Mar 2000 12:53:05 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003301137.VAA82294@explorer.tip.CSIRO.AU> "Shaun Amy, CSIRO TIP/ATNF" writes: : The only problem is (and this sounds silly) is that with the PCMCIA card : configured with DHCP addresses it won't pass any IP traffic, even a ping to : another machine on the same subnet fails (so it isn't a routing issue). This is the classic interrupt configured wrong problem. pick a different one in /etc/pccard.conf. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 12:15: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 50E2E37BA4B for ; Thu, 30 Mar 2000 12:15:05 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id GAA86210; Fri, 31 Mar 2000 06:14:51 +1000 (EST) (envelope-from sue) Date: Fri, 31 Mar 2000 06:14:48 +1000 From: Sue Blake To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files Message-ID: <20000331061446.X69444@welearn.com.au> Mail-Followup-To: Doug Barton , freebsd-hackers@FreeBSD.ORG References: <38E2F801.548AAAF1@gorean.org> <20000330193658.V69444@welearn.com.au> <38E395C5.DDBFCEB7@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38E395C5.DDBFCEB7@gorean.org>; from Doug Barton on Thu, Mar 30, 2000 at 09:58:29AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 09:58:29AM -0800, Doug Barton wrote: > Sue Blake wrote: > > It would be a good addition to a separate file with lengthy comments, > > supplied as an alternative and/or learning exercise. > > Actually I added the comments I did to the file (in more places than > just the allexport lines) to help make things more clear. If you feel > that more verbose comments are warranted, I'm sure we would all welcome > your suggestions. Actually I was thinking of a separate project I'm looking at, rather than suggesting putting more into these default files. > But shooting down a simple solution that solves > several problems at the same time and has little or no down side just > because you don't understand it isn't really constructive criticism. Sorry Doug, I understood what you presented and didn't mean to shoot down or criticise in any way, just to present one alternative viewpoint as politely and humbly as possible, as others had done already. I've stepped on your toes again by mentioning alternatives because I didn't recognise you. My apologies. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 13: 7: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 3AE1E37B8C8 for ; Thu, 30 Mar 2000 13:06:55 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA61839; Thu, 30 Mar 2000 13:06:39 -0800 (PST) (envelope-from Doug@gorean.org) Date: Thu, 30 Mar 2000 13:06:39 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Garance A Drosihn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files 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, 30 Mar 2000, Garance A Drosihn wrote: > At 9:58 AM -0800 3/30/00, Doug Barton wrote: > >Sue Blake wrote: > > > > > > On Wed, Mar 29, 2000 at 10:45:21PM -0800, Doug Barton wrote: > > > > Commentary on my files. . . Using allexport instead of an explicit > > > > 'export' for every variable makes the file easier to read, and gives > > > > a novice user one less thing to worry about. > > > > > > I see your point, and offer an alternative view. > > > > > > My fear would be that turning something on in one part of the file and > > > off again later is likely to assist novices to shoot themselves in the > > > foot by removing only one of these lines. > > > >Actually it's much more likely that a novice user would fail to export > >a variable, which would result in it not working at all. > > If the novice user is writing their own script, then they need to > understand exporting variables. No argument there. I think it's more likely that they would explicitly export something that they were adding themselves, but then we're multiplying the ways that we can confuse them. > >The user deletes the line that turns allexport off. Everything > >still works, and they have a few too many harmless shell settings > >exported into their environment. > > This is where I'd disagree. Some scripts define variables that they > really do not expect to be exported. I agree, which is why I explicitly disabled it. ATST, I don't really think this is a big problem, but I'm starting to agree with you that allexport introduces more problems than it solves. > It does reduce the clutter somewhat, but I would rather have the > explicit 'export's than the reduced clutter. Another way to reduce > clutter would be to export all the variables at once, at the end, I briefly considered, then rejected that option. If we're going to tie the connection between setting then exporting an environment variable together then the two commands should be right next to each other. This helps reduce the possibility that the user would add the command in one place, but not the other. The exact problem I was trying to solve by using allexport. If you have one long list of variables to export the danger is that the list will get out of synch with the variables. > The fact that *you* THINK it has no downside does not mean everyone > will agree that it has no downside. If someone thinks there is a > downside, then it is definitely constructive criticism for them > to say so. You can't very well ask for opinions and then dismiss > opinions as "not really constructive" just because they do not agree > with some basic premise of your position. Your response was well reasoned, and obviously comes from a position of having some knowledge and experience with the subject. "I don't understand this, so I don't like it." is not a valid argument in my book. I will submit a follow-up to my original message with the change you suggested. Thanks, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 13: 9: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ludwig.troikanetworks.com (host03.troikanetworks.com [12.31.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 4AD8037BDF2; Thu, 30 Mar 2000 13:09:00 -0800 (PST) (envelope-from ericp@troikanetworks.com) Received: by host03.troikanetworks.com with Internet Mail Service (5.5.2650.21) id ; Thu, 30 Mar 2000 13:09:13 -0800 Message-ID: From: Eric Peterson To: 'Samuel Tardieu' Cc: "'hackers@freebsd.org'" , 'Mike Smith' Subject: RE: Deferred procedure call available? Date: Thu, 30 Mar 2000 13:09:10 -0800 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 > -----Original Message----- Samuel Tardieu [mailto:sam@inf.enst.fr] writes: > Sent: Thursday, March 30, 2000 11:46 AM > To: Eric Peterson > Cc: 'hackers@freebsd.org' > Subject: Re: Deferred procedure call available? > > > >>>>> "Eric" == Eric Peterson writes: > > Eric> Sometimes called "task queues" or "deferred callbacks", they > Eric> allow an interrupt handler to schedule a (possibly predefined) > Eric> function to be called outside the context of the interrupt. > > (not an answer, just a suggestion) Is there anything you cannot do > with a userland program, that will be resumed by the interrupt > handler? Doing this even gives you the possibility of choosing the > priority of the deferred handler relative to other handler and regular > processes (as eCos does). Sam, Thanks for the response. With regard to your suggestion (my ignorance of FreeBSD drivers certainly shows through here, but...): 1. I'm porting an existing driver, so am trying to keep its basic structure intact. I don't believe that a user-mode entity has access to the memory/device address space I need to get to. 2. I suspect that going from kernel to (even high priority) user mode entails a non-trivial performance penalty (somebody please correct me if not!) One other approach I was thinking about was to have a sleeping kernel thread that I could wakeup when I needed to schedule a function to be called. I'm going to try out the timeout(9) routine that Mike Smith suggested, looks like just the ticket (thanks again, Mike). Regards, Eric -- Eric Peterson WB6PYK ericp@troikanetworks.com PGP: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x4DA8EEF1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 13:20:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 1157037B814 for ; Thu, 30 Mar 2000 13:20:16 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA61965 for ; Thu, 30 Mar 2000 13:20:15 -0800 (PST) (envelope-from Doug@gorean.org) Date: Thu, 30 Mar 2000 13:20:15 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: freebsd-hackers@freebsd.org Subject: Re: Proposed new Bourne shell init files In-Reply-To: <38E2F801.548AAAF1@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1118915418-954451215=:61945" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1118915418-954451215=:61945 Content-Type: TEXT/PLAIN; charset=US-ASCII The use of allexport in my previous submission was considered "too clever," and the source of possible user confusion. Rather than fight that battle, here is a version with explicit exporting of variables, and a helpful message at the top that attempts to explain why exporting is important. The following one line would still need to be added to root's dot.profile, however the line numbering in the patch below will be off. > For root's dot.profile you need to add the following: > > --- dot.profile Sat Mar 25 23:24:25 2000 > +++ dot.profile.root Sat Mar 25 23:41:15 2000 > @@ -8,6 +8,8 @@ > # Export all the environment variables to clean things up a bit > set -o allexport > > +HOME=/root > + > # Remove /usr/games and /usr/X11R6/bin if you want > > PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:$HOME/bin All opinions to the contrary aside, I welcome additional comments or suggestions. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." --0-1118915418-954451215=:61945 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dot.profile" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Bourne shell .profile script Content-Disposition: attachment; filename="dot.profile" IyAkRnJlZUJTRCQNCiMNCiMgLnByb2ZpbGUgLSBCb3VybmUgU2hlbGwgc3Rh cnR1cCBzY3JpcHQgZm9yIGxvZ2luIHNoZWxscw0KIw0KIyBzZWUgYWxzbyBz aCgxKSwgZW52aXJvbig3KS4NCiMNCg0KIyBZb3Ugc2hvdWxkIHNldCB2YXJp YWJsZXMgaW4gdGhpcyBmaWxlIHRoYXQgYXJlIG5lZWRlZCBieSBib3RoIHlv dXIgc2hlbGwNCiMgYW5kIG90aGVyIHByb2Nlc3NlcyB0aGF0IGFyZSBzdGFy dGVkIGZyb20gaXQuICBUaGVzZSB2YXJpYWJsZXMgc2hvdWxkDQojIGJlIGV4 cG9ydGVkIHNvIHRoYXQgcHJvY2Vzc2VzIG91dHNpZGUgdGhlIHNoZWxsIGNh biBzZWUgdGhlbS4gIE90aGVyDQojIHZhcmlhYmxlcyB0aGF0IGFyZSBvbmx5 IG5lZWRlZCBieSB0aGUgc2hlbGwsIG9yIHRoYXQgb25seSBhcHBseSB0bw0K IyBpbnRlcmFjdGl2ZSAoYW5kL29yIGxvZ2luKSBzaGVsbHMgc2hvdWxkIGJl IHNldCBpbiAuc2hyYy4NCg0KIyBSZW1vdmUgL3Vzci9nYW1lcyBhbmQgL3Vz ci9YMTFSNi9iaW4gaWYgeW91IHdhbnQNClBBVEg9L3Vzci9iaW46L2Jpbjov dXNyL3NiaW46L3NiaW46L3Vzci9sb2NhbC9iaW46L3Vzci9sb2NhbC9zYmlu Oi91c3IvWDExUjYvYmluOi91c3IvZ2FtZXM6JEhPTUUvYmluDQpleHBvcnQg UEFUSA0KDQojIFNldHRpbmcgVEVSTSBpcyBub3JtYWxseSBkb25lIHRocm91 Z2ggL2V0Yy90dHlzLiAgT25seSBvdmVycmlkZQ0KIyBpZiB5b3UncmUgc3Vy ZSB0aGF0IHlvdSdsbCBuZXZlciBsb2cgaW4gdmlhIHRlbG5ldCwgeHRlcm0g b3IgYQ0KIyBzZXJpYWwgbGluZS4NCiMgVXNlIGNvbnMyNWwxIGZvciBpc28t KiBmb250cw0KVEVSTT0ke1RFUk06LWNvbnMyNX0NCmV4cG9ydCBURVJNDQoN CkVESVRPUj12aQ0KZXhwb3J0IEVESVRPUg0KUEFHRVI9bW9yZQ0KZXhwb3J0 IFBBR0VSDQpCTE9DS1NJWkU9Sw0KZXhwb3J0IEJMT0NLU0laRQ0KDQojIFNl dCBFTlYgdG8gYSBmaWxlIGludm9rZWQgZWFjaCB0aW1lIHNoIGlzIHN0YXJ0 ZWQgZm9yIGludGVyYWN0aXZlIHVzZS4NCkVOVj0kSE9NRS8uc2hyYzsgZXhw b3J0IEVOVg0KDQo= --0-1118915418-954451215=:61945-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 13:39:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 9A5F837B938 for ; Thu, 30 Mar 2000 13:38:35 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA11008 for hackers@freebsd.org; Thu, 30 Mar 2000 23:38:18 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E3B2B8796; Thu, 30 Mar 2000 21:29:50 +0200 (CEST) Date: Thu, 30 Mar 2000 21:29:50 +0200 From: Ollivier Robert To: hackers@freebsd.org Subject: Re: Shared /bin and /sbin Message-ID: <20000330212950.A92062@keltia.freenix.fr> Mail-Followup-To: hackers@freebsd.org References: <200003300722.AAA21918@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9i In-Reply-To: <200003300722.AAA21918@harmony.village.org>; from imp@village.org on Thu, Mar 30, 2000 at 12:22:23AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Warner Losh: > copies of libc in /sbin and /bin. I was thinking about building, for > this system only, /bin and /sbin dynamic. Has anybody ever done this? Ask Bruce. He used to have a completely dynamic system a while ago... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 14:33:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 6D53637B732 for ; Thu, 30 Mar 2000 14:33:40 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA23320 for freebsd-hackers@freebsd.org; Fri, 31 Mar 2000 00:33:39 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA09732 for freebsd-hackers@freebsd.org; Fri, 31 Mar 2000 00:23:51 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Proposed new Bourne shell init files Date: 31 Mar 2000 00:23:50 +0200 Message-ID: <8c0k5m$9fp$1@bigeye.rhein-neckar.de> References: <38E2F801.548AAAF1@gorean.org> To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > Commentary on my files. . . Using allexport instead of an explicit > 'export' for every variable makes the file easier to read, and gives a > novice user one less thing to worry about. I think Sue has a made a good argument against allexport. Also, from your reply to her I suspect you didn't know about export VAR=value which is what I use and would like to suggest. > I added 'set -o emacs' to dot.shrc, it makes life much easier, FWIW, "set -E" does the same in fewer letters but is a FreeBSDism. > I fully realize that treading in this area is likely to provoke lenghty > arguments, goring of cows, etc. :) I suggest we use nails with square heads for the south side of the bike shed. > # Search path for cd(1) > CDPATH=.:$HOME Hmpf. > # General aliases > alias la='ls -A' > alias lf='ls -AF' > alias ll='ls -loaF' > alias m=$PAGER > alias g='egrep -i' These are *very much* a matter of taste. I don't like a single one of them, but then again I wouldn't want to force mine on anybody else. One alias I think worth considering is alias r='fc -s' to provide ksh-style history access. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 16:37:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id C893B37BF6E; Thu, 30 Mar 2000 16:37:22 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-142.bellatlantic.net [151.198.117.142]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA08257; Thu, 30 Mar 2000 19:37:06 -0500 (EST) Message-ID: <38E3F526.79CBAE3B@bellatlantic.net> Date: Thu, 30 Mar 2000 19:45:26 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: wilko@freebsd.org Cc: sthaug@nethelp.no, hackers@freebsd.org Subject: Re: Anybody have tools to read a Digital Unix "vdump" tape on FreebSD? References: <42000.954338392@verdi.nethelp.no> <20000329204851.C2044@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Wed, Mar 29, 2000 at 03:59:52PM +0200, sthaug@nethelp.no wrote: > > Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD? > > I have a number of such tapes, and would prefer to read them on an (Intel) > > FreeBSD box instead of having to reinstall DU on a machine which has had > > its disks wiped. > > Vdump, the dump incarnation for Tru64 AdvFS, can to the best of my knowledge > only be read by vrestore. I'm afraid your stuck to using a T64 box for this. If AdvFS is just another incarnation of VXFS there may be a chance that it could be read by vxrestore on UnixWare. So if there is absolutely no Alpha machine around then free UnixWare (binary-only but still free except for the CD cost, like $17) may be worth a try. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 16:49: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by hub.freebsd.org (Postfix) with ESMTP id DB9DA37BF32 for ; Thu, 30 Mar 2000 16:48:57 -0800 (PST) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br (port04.tdnet.com.br [200.236.148.104]) by vicosa.dpi.ufv.br (AIX4.2/UCB 8.7/8.7) with ESMTP id VAA12274; Thu, 30 Mar 2000 21:48:54 -0300 (GRNLNDST) Message-ID: <38E3CAB5.8C23044@tdnet.com.br> Date: Thu, 30 Mar 2000 21:44:21 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: misc@openbsd.org, hackers@freebsd.org Subject: BSDs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hy folks! I have been playing with FreeBSD for the last 1 year and some time ago i decide to give openbsd a try. I have been loving Free! Now, playing with Open is no trouble. Some questions came up: 1) What are the advantages/disadavantages of using FreeBSD or OpenBSD? 2) FreeBSD has proven to be a high quality OS for stupid heavy loaded site (ftp.cdrom.com)! Can OpenBSD support such a very loaded site? Since i have never seen such a heavy loaded site using Open, i would like to know if it (Open) can support such a load using the same hardware Free uses. 3) What are the advantage from OpenBSD over FreeBSD, and FreeBSD over OpenBSD! Thanks a lot for time and cooperation. PS: I am not asking which is the best OS (a kind of question that should never be asked). I only want to know the good/bad things about both of them, since no OS is perfect! -- If you're happy, you're successful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 16:58:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9656F37BE4E for ; Thu, 30 Mar 2000 16:58:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA52176; Thu, 30 Mar 2000 16:58:37 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 16:58:37 -0800 (PST) From: Matthew Dillon Message-Id: <200003310058.QAA52176@apollo.backplane.com> To: Gustavo V G C Rios Cc: misc@openbsd.org, hackers@FreeBSD.ORG Subject: Re: BSDs References: <38E3CAB5.8C23044@tdnet.com.br> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hy folks! : :1) What are the advantages/disadavantages of using FreeBSD or OpenBSD? :.. : :PS: I am not asking which is the best OS (a kind of question that should :never be asked). : I only want to know the good/bad things about both of them, since no :OS is perfect! It's still a bad idea to post this sort of question to both mailing lists. I would recommend posting the question to the mailing lists separately or simply reading the documentation and messing with the distributions yourself to form your own opinion. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 18:24:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by hub.freebsd.org (Postfix) with ESMTP id 3043237BE4E for ; Thu, 30 Mar 2000 18:24:23 -0800 (PST) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br (port00.tdnet.com.br [200.236.148.100]) by vicosa.dpi.ufv.br (AIX4.2/UCB 8.7/8.7) with ESMTP id XAA17132; Thu, 30 Mar 2000 23:24:01 -0300 (GRNLNDST) Message-ID: <38E3E0FC.6E8FA631@tdnet.com.br> Date: Thu, 30 Mar 2000 23:19:24 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: misc@openbsd.org, hackers@FreeBSD.ORG Subject: Re: BSDs References: <38E3CAB5.8C23044@tdnet.com.br> <200003310058.QAA52176@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > It's still a bad idea to post this sort of question to both mailing > lists. Sorry, i did not realized that! Next time, i'll be carefull! -- If you're happy, you're successful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 18:33:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 1226937B93E; Thu, 30 Mar 2000 18:33:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id VAA91682; Thu, 30 Mar 2000 21:33:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003310233.VAA91682@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 30 Mar 2000 21:33:02 -0500 (EST) From: John Baldwin To: n_hibma@FreeBSD.org, hackers@FreeBSD.org Subject: USB Installation - Working Release! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've been working on trying to build a release that can be installed onto machines that have USB keyboards as well as other USB foo. My current patch to src/ for this is at http://www.FreeBSD.org/~jhb/patches/usb.release.patch. You can use it to build a release via 'make release LOCAL_PATCHES=usb.release.patch'. A release of -current made with this patch can be found at ftp://ftp.Baldwin.cx/pub/FreeBSD/5.0-BALDWIN_CX-USB-20000330/ 1) The kernel userconfig does not work with a USB keyboard. The result is that we can't put INTRO_USERCONFIG into the install floppy. Since we want this for installation whenever we can this means that we will have to have a seperate USB kern.flp until userconfig is moved out to the loader where it arguably belongs. 2) Right now the GENERIC kernel doesn't have the atkbd0 device in it, so it won't work on a system with just an AT keyboard. For a workaround, I'm thinking of adding kbdcontrol to the install floppy, and adding an entry into /etc/usbd.conf for ukbd0 that runs kbdcontrol to change the default keyboard to the first USB keyboard. Thus, on a system with both an AT and a USB keyboard, the USB keyboard would be used, and on a system with either the working one would be used. I'll be working on this later on this evening and then try to roll another release. However, this would require a change to /usr/src/etc/usbd.conf if that is ok with everyone. Comments? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Mar 30 18:43:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id A3FAB37B8FE for ; Thu, 30 Mar 2000 18:43:14 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com (linuxcare.canberra.net.au [203.29.91.49]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id MAA12910; Fri, 31 Mar 2000 12:12:29 +0930 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA06975; Fri, 31 Mar 2000 12:43:11 +1000 (EST) (envelope-from grog) Date: Fri, 31 Mar 2000 12:43:10 +1000 From: Greg Lehey To: Gustavo V G C Rios Cc: Matthew Dillon , misc@openbsd.org, hackers@FreeBSD.ORG Subject: Re: BSDs Message-ID: <20000331124310.C6764@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <38E3CAB5.8C23044@tdnet.com.br> <200003310058.QAA52176@apollo.backplane.com> <38E3E0FC.6E8FA631@tdnet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E3E0FC.6E8FA631@tdnet.com.br>; from kernel@tdnet.com.br on Thu, Mar 30, 2000 at 11:19:24PM +0000 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 30 March 2000 at 23:19:24 +0000, Gustavo V G C Rios wrote: > Matthew Dillon wrote: >> It's still a bad idea to post this sort of question to both mailing >> lists. > > Sorry, i did not realized that! > Next time, i'll be carefull! FWIW, that's Matt's opinion. I don't necessarily agree with it. There are some good reasons for people to know who you're asking. 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 Thu Mar 30 19: 1:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg128-098.ricochet.net [204.179.128.98]) by hub.freebsd.org (Postfix) with ESMTP id 1F5C037C2EE; Thu, 30 Mar 2000 19:01:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA00407; Thu, 30 Mar 2000 19:05:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003310305.TAA00407@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: n_hibma@FreeBSD.org, hackers@FreeBSD.org Subject: Re: USB Installation - Working Release! In-reply-to: Your message of "Thu, 30 Mar 2000 21:33:02 EST." <200003310233.VAA91682@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 19:05:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, I've been working on trying to build a release that can be > installed onto machines that have USB keyboards as well as other > USB foo. My current patch to src/ for this is at > http://www.FreeBSD.org/~jhb/patches/usb.release.patch. You can > use it to build a release via > 'make release LOCAL_PATCHES=usb.release.patch'. A release of > -current made with this patch can be found at > ftp://ftp.Baldwin.cx/pub/FreeBSD/5.0-BALDWIN_CX-USB-20000330/ > > > 1) The kernel userconfig does not work with a USB keyboard. The > result is that we can't put INTRO_USERCONFIG into the install > floppy. Since we want this for installation whenever we can > this means that we will have to have a seperate USB kern.flp > until userconfig is moved out to the loader where it arguably > belongs. INTRO_USERCONFIG should probably be smart enough to work out that there isn't an early input device and just punt. > 2) Right now the GENERIC kernel doesn't have the atkbd0 device > in it, so it won't work on a system with just an AT keyboard. > For a workaround, I'm thinking of adding kbdcontrol to the > install floppy, and adding an entry into /etc/usbd.conf for > ukbd0 that runs kbdcontrol to change the default keyboard to > the first USB keyboard. Thus, on a system with both an AT > and a USB keyboard, the USB keyboard would be used, and on a > system with either the working one would be used. I'll be > working on this later on this evening and then try to roll > another release. However, this would require a change to > /usr/src/etc/usbd.conf if that is ok with everyone. > > Comments? If there's an AT keyboard, it should always be used first. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 19:18:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web112.yahoomail.com (web112.yahoomail.com [205.180.60.82]) by hub.freebsd.org (Postfix) with SMTP id CB07937C2A9 for ; Thu, 30 Mar 2000 19:18:09 -0800 (PST) (envelope-from dyeske@yahoo.com) Received: (qmail 8428 invoked by uid 60001); 31 Mar 2000 03:18:08 -0000 Message-ID: <20000331031808.8427.qmail@web112.yahoomail.com> Received: from [192.172.226.145] by web112.yahoomail.com; Thu, 30 Mar 2000 19:18:08 PST Date: Thu, 30 Mar 2000 19:18:08 -0800 (PST) From: David Yeske Subject: usb stuff 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 I am using a usb mouse, and dlink ethernet nic connected to a belkin usb hub in FreeBSD 4.0R. I also have a "Solidtek ACK-298" keyboard, but I have not gotten any progress out of it in freebsd. Has anyone tried usb "direct connect" with freebsd? That would be much cooler than plip I think... __________________________________________________ Do You Yahoo!? Talk to your friends online 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 Thu Mar 30 20:28:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id B78C537B82B for ; Thu, 30 Mar 2000 20:28:53 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA65489; Thu, 30 Mar 2000 20:28:49 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E42987.856C2215@gorean.org> Date: Thu, 30 Mar 2000 20:28:55 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-hackers@freebsd.org Subject: Re: Proposed new Bourne shell init files References: <38E2F801.548AAAF1@gorean.org> <8c0k5m$9fp$1@bigeye.rhein-neckar.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > > Doug Barton wrote: > > > Commentary on my files. . . Using allexport instead of an explicit > > 'export' for every variable makes the file easier to read, and gives a > > novice user one less thing to worry about. > > I think Sue has a made a good argument against allexport. > Also, from your reply to her I suspect you didn't know about > > export VAR=value You might try giving me the benefit of the doubt. :) The problem with that option is that it's not portable. If we're going to be using the .files as a teaching experience, we should teach good habits. > which is what I use and would like to suggest. > > > I added 'set -o emacs' to dot.shrc, it makes life much easier, > > FWIW, "set -E" does the same in fewer letters but is a FreeBSDism. *Nod* Portability, and I like spelling out of the options as a general principle. It makes it easier for a new user to understand what's happening. > > I fully realize that treading in this area is likely to provoke lenghty > > arguments, goring of cows, etc. :) > > I suggest we use nails with square heads for the south side of the > bike shed. *Chuckle* > > # Search path for cd(1) > > CDPATH=.:$HOME > > Hmpf. > > > # General aliases > > alias la='ls -A' > > alias lf='ls -AF' > > alias ll='ls -loaF' > > alias m=$PAGER > > alias g='egrep -i' > > These are *very much* a matter of taste. I copied the above from the current files. I use the CDPATH in my .bashrc anyway, and I've never had a problem with it. I also use the ls aliases (well, not lf) and I have no experience with the other two, I just copied them. > I don't like a single one > of them, but then again I wouldn't want to force mine on anybody > else. Yeah, the file would be a lot longer if I included the stuff from my .bashrc. :) > One alias I think worth considering is > > alias r='fc -s' Hrrmm... ok. I have no experience with that, but I wouldn't object to its inclusion. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 21: 0:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 4DC2037B9A4 for ; Thu, 30 Mar 2000 21:00:35 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from root@localhost) by virtual-voodoo.com (8.10.0/8.10.0) id e2V50WP21098 for freebsd-hackers@freebsd.org; Fri, 31 Mar 2000 00:00:32 -0500 (EST) Date: Fri, 31 Mar 2000 00:00:32 -0500 (EST) From: Steve Ames Message-Id: <200003310500.e2V50WP21098@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: NO_SENDMAIL in /etc/make.conf Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have NO_SENDMAIL= true in /etc/make.conf but sendmail got rebuilt on the last makeworld anyway... this is -CURRENT from this morning (3/30). -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 21:46:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spock.org (cm-24-161-8-2.nycap.rr.com [24.161.8.2]) by hub.freebsd.org (Postfix) with ESMTP id 135C237C428 for ; Thu, 30 Mar 2000 21:45:39 -0800 (PST) (envelope-from jon@spock.org) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F8823AAA83545F7T for freebsd-hackers@freebsd.org; Fri, 31 Mar 2000 00:45:37 -0500 (EST) (envelope-from jon) Date: Fri, 31 Mar 2000 00:45:37 -0500 From: Jonathan Chen To: freebsd-hackers@freebsd.org Subject: realigning mbufs? Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: telnet Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing some network card drivers and have ran into a problem with mbuf alignment. In summary, the problem is that the network card expects its transmit buffers to be double word aligned, while I'm getting tx mbufs that are single word aligned. The details: The card in question is the IBM EtherJet Cardbus adaptor, AKA Xircom CardBus Ethernet X3201-3. The PCI-Cardbus bridge driver (my own) and this whole mess is running on RELENG_4, and the netcard driver is based on if_dc. Basically, after the whole processes of going through ether_output() and stuff, when dc_start is called, the mbufs I get there are usually misaligned. Currently, I get by this by doing some really nasty hack which I'm sure is dead wrong, since I have very little knowledge of how mbufs work and what supporting functions are defined. So, the object of the game now is how to get an mbuf that's double word aligned (both offset and length) from some mbuf that might not be aligned properly, using the most correct and least resource intensive method. I do realize that since the ethernet header is 14 bytes long, it'll be hard to ensure that the mbuf I get will be double-word aligned to begin with, so I must either copy it or move it to somewhere else. Here's where I am stuck. Should I copy it or move it, and what are the functions/macros that will aid me in my task? Please bear with me, I'm fairly new to kernel level programming. Why do I get the feeling that someone at Xircom was smoking crack when they designed this card? -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) WARNING:This email contains 100% nonbiodegradable electrons (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 22: 4:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 9194E37B592 for ; Thu, 30 Mar 2000 22:04:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BA7631CD7; Thu, 30 Mar 2000 22:04:34 -0800 (PST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NO_SENDMAIL in /etc/make.conf In-Reply-To: Message from Steve Ames of "Fri, 31 Mar 2000 00:00:32 EST." <200003310500.e2V50WP21098@virtual-voodoo.com> Date: Thu, 30 Mar 2000 22:04:34 -0800 From: Peter Wemm Message-Id: <20000331060434.BA7631CD7@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Ames wrote: > > I have NO_SENDMAIL= true in /etc/make.conf but sendmail got rebuilt > on the last makeworld anyway... this is -CURRENT from this morning > (3/30). > > -Steve man mailwrapper man mailer.conf Then see /etc/mail/mailer.conf Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 22:50:11 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 A0EE937B6C3; Thu, 30 Mar 2000 22:50:07 -0800 (PST) (envelope-from imp@harmony.village.org) 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 XAA72079; Thu, 30 Mar 2000 23:50:06 -0700 (MST) (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 XAA32945; Thu, 30 Mar 2000 23:49:38 -0700 (MST) Message-Id: <200003310649.XAA32945@harmony.village.org> To: John Baldwin Subject: Re: USB Installation - Working Release! Cc: n_hibma@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 21:33:02 EST." <200003310233.VAA91682@server.baldwin.cx> References: <200003310233.VAA91682@server.baldwin.cx> Date: Thu, 30 Mar 2000 23:49:38 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003310233.VAA91682@server.baldwin.cx> John Baldwin writes: : until userconfig is moved out to the loader where it arguably : belongs. It should be almost trivially easy to write the userconfig in the boot loader now that I have my hint driver working. All it would have to do is put a bunch of hints into the environment ala hint.aha.0.irq=#13 and the rest just happens. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 30 23:42:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from inet-tsb.toshiba.co.jp (inet-tsb.toshiba.co.jp [202.33.96.40]) by hub.freebsd.org (Postfix) with ESMTP id 097A137C277; Thu, 30 Mar 2000 23:41:56 -0800 (PST) (envelope-from shige@FreeBSD.org) Received: from tis2.tis.toshiba.co.jp (tis2 [133.199.160.66]) by inet-tsb.toshiba.co.jp (3.7W:TOSHIBA-ISC-2000030918) with ESMTP id QAA12021; Fri, 31 Mar 2000 16:41:32 +0900 (JST) Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp (8.8.4+2.7Wbeta4/3.3W9-95082317) id QAA16400; Fri, 31 Mar 2000 16:41:31 +0900 (JST) Received: from tas0470.sitc.toshiba.co.jp by toshiba.co.jp (8.7.1+2.6Wbeta4/3.3W9-TOSHIBA-GLOBAL SERVER) id QAA09704; Fri, 31 Mar 2000 16:35:39 +0900 (JST) Received: from amphitrite by tas0470.sitc.toshiba.co.jp (8.9.3/sitc-1.4) with SMTP id QAA27632; Fri, 31 Mar 2000 16:35:38 +0900 (JST) Message-ID: <015101bf9ae3$7ab06ee0$b7227185@sitc.toshiba.co.jp> From: "Shigeyuki Fukushima" To: "Akinori -Aki- MUSHA" , Cc: References: <86ln38vutx.wl@archon.local.idaemons.org> Subject: Re: zsh compdef collection for FreeBSD Date: Fri, 31 Mar 2000 16:33:58 +0900 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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why not we collect those useful compdef's to send to the zsh > development team? You know, the latest zsh 3.1.6-dev-19 includes > Debian specific functions in `Completion/Debian', then why not we have > ours? I'm afraid that zsh will only have Linux/Solaris oriented > configurations if we don't feed anything to the zsh team. > It might take so long, but we always have a port. :) For the present, may I add these nice compdefs to zsh-devel ports? > Then, who's next? :) Any input is welcome! But, I'm sorry that there is no compdefs which I can provide. ;) Thanks, knu-san! --- shige To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 1: 6: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 218AE37B82B; Fri, 31 Mar 2000 01:06:04 -0800 (PST) (envelope-from lloyd@brunel.uk1.vbc.net) Received: from localhost (lloyd@localhost) by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id KAA37325; Fri, 31 Mar 2000 10:06:02 +0100 (BST) Date: Fri, 31 Mar 2000 10:06:02 +0100 (BST) From: Lloyd Rennie To: John Baldwin Cc: Jesper Skriver , hackers@FreeBSD.org, Patrick Gardella Subject: Re: Mirror requirements In-Reply-To: <200003301820.NAA91182@server.baldwin.cx> 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, 30 Mar 2000, John Baldwin wrote: > On 30-Mar-00 Jesper Skriver wrote: > > On Thu, Mar 30, 2000 at 09:42:42AM -0500, Patrick Gardella wrote: > >> Lloyd Rennie wrote: > >> > > >> > I sent this to -questions, but have received no reply. Sorry to bug > >> > y'all, but... > >> > > >> > What are the hardware and bandwidth requirements to maintain a full > >> > FreeBSD mirror site? > >> > >> Having asked this before, I can try to answer it... > >> > >> Hardware: Disk space to hold the parts you want to mirror. Are you > >> looking to be just an FTP mirror, a WWW mirror (about 8 megs), a CVSUP > >> mirror, or some combination of all of these? I would say that a safe > >> bet would be an 8 gig HD for all of them. > > > > I keep a partial ftp mirror, and it barely fits 20 GB ... > > I was about to say. On ftp3.FreeBSD.org we use 3 9 Gb SCSI disks in a > vinum stripe to hold just XFree86 and a partial mirror of FreeBSD and it > runs at about 86% capacity. Right. Thanks to all who replied - will budget lots and lots of gigs ;-) -- Lloyd Rennie VBCnet GB Ltd lloyd@vbc.net tel +44 (0) 117 929 1316 http://www.vbc.net fax +44 (0) 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 1:20:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dwc-gw.dwc.edu (dwc-gw.dwc.edu [198.49.142.9]) by hub.freebsd.org (Postfix) with ESMTP id BA91F37BE58 for ; Fri, 31 Mar 2000 01:20:40 -0800 (PST) (envelope-from chess@terra.ee) Received: from home (home.terra.ee [195.50.199.195]) by dwc-gw.dwc.edu (8.8.5/8.6.9) with SMTP id EAA03168 for ; Fri, 31 Mar 2000 04:24:19 -0500 From: chess@terra.ee To: Subject: Chess Date: Fri, 31 Mar 2000 11:22:48 +0200 Message-Id: <36616.474174768518400.13149@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear chessplayer! Long time control tournament at http://www.chess.kiev.ua Join it now and win a prize. The First ICKT will start at Feb 10 –2000 and will before June- 10 2000. The place of competition is http://chess.terra.ee of Internet. Every chess players can take part of the FICKT. Participation is free of charge. Start games before June 10, 2000. Every participant may start several games as he want. Time control is 48 days to 40 moves for each player and 24 days for each player to the very end. Game start when Black do his first move. Winners. The players which will have most per cent result will a winners of the Cup. To start a White games participant must do first moves and wait Black`s reply. To start Black games player must choose games with Blacks and do his first reply. You can join the Cup just now. Sponsors will set an awards after players number accounting (2500 USD for 1000 players). New possibility to play blitz http://www.terra.ee/chess/blitz All questions are welcome at chess@noo.kiev.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 1:32: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 48C2937B922 for ; Fri, 31 Mar 2000 01:31:55 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12axlb-000MZR-00; Fri, 31 Mar 2000 11:30:59 +0200 From: Sheldon Hearn To: Peter Wemm Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: NO_SENDMAIL in /etc/make.conf In-reply-to: Your message of "Thu, 30 Mar 2000 22:04:34 PST." <20000331060434.BA7631CD7@overcee.netplex.com.au> Date: Fri, 31 Mar 2000 11:30:59 +0200 Message-ID: <86764.954495059@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Mar 2000 22:04:34 PST, Peter Wemm wrote: > man mailwrapper > man mailer.conf > > Then see /etc/mail/mailer.conf And for those who read the manual page and still don't want /usr/sbin/sendmail to be blown away by mailwrapper(8), there's now a NO_MAILWRAPPER knob. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 1:44:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 78C1137B9E9 for ; Fri, 31 Mar 2000 01:44:32 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12axyA-000MfE-00; Fri, 31 Mar 2000 11:43:58 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: hackers@freebsd.org Subject: Re: Shared /bin and /sbin In-reply-to: Your message of "Thu, 30 Mar 2000 21:29:50 +0200." <20000330212950.A92062@keltia.freenix.fr> Date: Fri, 31 Mar 2000 11:43:58 +0200 Message-ID: <87123.954495838@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Mar 2000 21:29:50 +0200, Ollivier Robert wrote: > > copies of libc in /sbin and /bin. I was thinking about building, for > > this system only, /bin and /sbin dynamic. Has anybody ever done this? > > Ask Bruce. He used to have a completely dynamic system a while ago... Bruce Evans? A completely dynamic system? *rotflmao* Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 3:53:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E713337B5A2; Fri, 31 Mar 2000 03:53:28 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id LAA97611; Fri, 31 Mar 2000 11:15:47 +0100 (BST) (envelope-from nik) Date: Fri, 31 Mar 2000 11:15:46 +0100 From: Nik Clayton To: Lloyd Rennie Cc: John Baldwin , Jesper Skriver , hackers@FreeBSD.org, Patrick Gardella Subject: Re: Mirror requirements Message-ID: <20000331111546.A97386@catkin.nothing-going-on.org> References: <200003301820.NAA91182@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Lloyd Rennie on Fri, Mar 31, 2000 at 10:06:02AM +0100 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lloyd, On Fri, Mar 31, 2000 at 10:06:02AM +0100, Lloyd Rennie wrote: > > I was about to say. On ftp3.FreeBSD.org we use 3 9 Gb SCSI disks in a > > vinum stripe to hold just XFree86 and a partial mirror of FreeBSD and it > > runs at about 86% capacity. > > Right. Thanks to all who replied - will budget lots and lots of gigs ;-) When you get this done, could you drop the -doc list a note saying what resources you used, and how much space it takes up. I think this sort of information should be in the FAQ or Handbook. Thanks, N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 3:57:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 2715637B62D for ; Fri, 31 Mar 2000 03:57:46 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id MAA10546 for hackers@freebsd.org; Fri, 31 Mar 2000 12:57:40 +0100 (BST) (envelope-from nik) Date: Fri, 31 Mar 2000 12:57:40 +0100 From: Nik Clayton To: hackers@freebsd.org Subject: No route for 127/8 to lo0 (?) Message-ID: <20000331125739.A97865@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Sigh. I had hoped to keep this to the uk mailing list, limiting the exposure of my ignorance. Sadly I now have to expose it to the whole world. This is on a 3.x-stable system. ] In the course of debugging why Samba was bringing my modem link up periodically, I discovered it was sending netbios packets to 127.255.255.255. Because the relevent entries from the routing table looked like Destination Gateway Flags Refs Use Netif Expire default 158.152.1.222 UGSc 22 0 tun0 127.0.0.1 127.0.0.1 UH 0 201 lo0 [...] 127.255.255.255 was going out of the default route, tun0, and bringing the line up. Obviously, there are several ways to fix this. You could add a network route ("route add -net 127 -interface lo0"), you could configure PPP's dial filter to ignore them, or you could filter them with a firewall. I thought that 127/8 was the "local net", and that packets sent to any of those addresses would go via the loopback interface. That seems to be how Linux and Windows 98 do things (the only systems I can check this on at the moment). Assuming that's the case, why does FreeBSD only add a a host route to 127.0.0.1, and not a network route for 127/8? Various other people have confirmed that they only have a 127.0.0.1 host route as well, so I don't believe this is a misconfiguration of my system. Or am I misguided, and need to go buy a copy of Stevens? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 4:35:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id B298F37B62D; Fri, 31 Mar 2000 04:35:13 -0800 (PST) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (pc343042.tokyo.jcom.ne.jp [203.140.143.42]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 03/13/00) with ESMTP id VAA21966; Fri, 31 Mar 2000 21:35:12 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id VAA45493; Fri, 31 Mar 2000 21:34:40 +0900 (JST) Date: Fri, 31 Mar 2000 21:34:39 +0900 Message-ID: <861z4rmi74.wl@daemon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: shige@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: zsh compdef collection for FreeBSD In-Reply-To: In your message of "Fri, 31 Mar 2000 16:33:58 +0900" <015101bf9ae3$7ab06ee0$b7227185@sitc.toshiba.co.jp> References: <86ln38vutx.wl@archon.local.idaemons.org> <015101bf9ae3$7ab06ee0$b7227185@sitc.toshiba.co.jp> User-Agent: Wanderlust/2.2.18 (Please Forgive Me) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Fri, 31 Mar 2000 16:33:58 +0900, Shigeyuki Fukushima wrote: > For the present, may I add these nice compdefs to zsh-devel ports? Sure. I put a tarball in the following site: http://people.FreeBSD.org/~knu/ports/distfiles/zsh-functions-freebsd-2000.03.31.tar.gz so you could use it in the port. :) > But, I'm sorry that there is no compdefs which I can provide. ;) It's okay. Thanks for your support! -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 5:20:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 0126737BE64; Fri, 31 Mar 2000 05:20:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id IAA92570; Fri, 31 Mar 2000 08:20:00 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003311320.IAA92570@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200003310305.TAA00407@mass.cdrom.com> Date: Fri, 31 Mar 2000 08:20:00 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: USB Installation - Working Release! Cc: hackers@FreeBSD.org, n_hibma@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Mar-00 Mike Smith wrote: >> Ok, I've been working on trying to build a release that can be >> installed onto machines that have USB keyboards as well as other >> USB foo. My current patch to src/ for this is at >> http://www.FreeBSD.org/~jhb/patches/usb.release.patch. You can >> use it to build a release via >> 'make release LOCAL_PATCHES=usb.release.patch'. A release of >> -current made with this patch can be found at >> ftp://ftp.Baldwin.cx/pub/FreeBSD/5.0-BALDWIN_CX-USB-20000330/ >> >> >> 1) The kernel userconfig does not work with a USB keyboard. The >> result is that we can't put INTRO_USERCONFIG into the install >> floppy. Since we want this for installation whenever we can >> this means that we will have to have a seperate USB kern.flp >> until userconfig is moved out to the loader where it arguably >> belongs. > > INTRO_USERCONFIG should probably be smart enough to work out that there > isn't an early input device and just punt. Hrmm. Ok. >> 2) Right now the GENERIC kernel doesn't have the atkbd0 device >> in it, so it won't work on a system with just an AT keyboard. >> For a workaround, I'm thinking of adding kbdcontrol to the >> install floppy, and adding an entry into /etc/usbd.conf for >> ukbd0 that runs kbdcontrol to change the default keyboard to >> the first USB keyboard. Thus, on a system with both an AT >> and a USB keyboard, the USB keyboard would be used, and on a >> system with either the working one would be used. I'll be >> working on this later on this evening and then try to roll >> another release. However, this would require a change to >> /usr/src/etc/usbd.conf if that is ok with everyone. >> >> Comments? > > If there's an AT keyboard, it should always be used first. The problem is that if atkbd0 is in the kernel we just assume an AT keyboard is installed, even if one isn't. Thus, for a system with an AT or PS/2 controller w/no keyboard but a USB keyboard, the non existent AT keyboard would still be chosen as the default keyboard, giving you a worthless system. I'm going to try flags 0x1 on the atbkd0 device though (detect keyboard) along with flags 0x100 on sc0 and see if that gives the desired results. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Mar 31 5:20:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 5AA7E37BE98; Fri, 31 Mar 2000 05:20:09 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id IAA92577; Fri, 31 Mar 2000 08:20:03 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003311320.IAA92577@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200003310649.XAA32945@harmony.village.org> Date: Fri, 31 Mar 2000 08:20:03 -0500 (EST) From: John Baldwin To: Warner Losh Subject: Re: USB Installation - Working Release! Cc: hackers@FreeBSD.org, n_hibma@FreeBSD.org, dcs@newsguy.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Mar-00 Warner Losh wrote: > In message <200003310233.VAA91682@server.baldwin.cx> John Baldwin writes: >: until userconfig is moved out to the loader where it arguably >: belongs. > > It should be almost trivially easy to write the userconfig in the boot > loader now that I have my hint driver working. All it would have to > do is put a bunch of hints into the environment ala > hint.aha.0.irq=#13 > and the rest just happens. Cool. The only extra part is reading the current config out of a loaded kernel. Now where did our Forth hackers go? :) > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Mar 31 6: 7:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id A0CA937BC48; Fri, 31 Mar 2000 06:07:49 -0800 (PST) (envelope-from fanf@demon.net) Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id PAA13248; Fri, 31 Mar 2000 15:07:39 +0100 (BST) Received: from fanf by fanf.eng.demon.net with local (Exim 3.12 #3) id 12b25H-000EWt-00; Fri, 31 Mar 2000 15:07:35 +0100 To: nik@freebsd.org From: Tony Finch Cc: hackers@freebsd.org Subject: Re: No route for 127/8 to lo0 (?) In-Reply-To: <20000331125739.A97865@catkin.nothing-going-on.org> Message-Id: Date: Fri, 31 Mar 2000 15:07:35 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > >I thought that 127/8 was the "local net", and that packets sent to any of >those addresses would go via the loopback interface. That seems to be >how Linux and Windows 98 do things (the only systems I can check this on >at the moment). Assuming that's the case, why does FreeBSD only add a >a host route to 127.0.0.1, and not a network route for 127/8? I did some further investigation to see how old this oddity is and it seems to be the way BSD has always handled the loopback interface. There's an explicit exclusion in the interface initialization code in in.c that gives loopback interfaces a host route instead of the network route that a normal interface gets and it's been that way for 15 years. Tony. -- f.a.n.finch fanf@demon.net dot@dotat.at 408 overlarge underplug afterburn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 6:51:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 52EA137BC11 for ; Fri, 31 Mar 2000 06:51:20 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12b2lO-0000BH-00 for hackers@FreeBSD.org; Fri, 31 Mar 2000 16:51:06 +0200 From: Sheldon Hearn To: hackers@FreeBSD.org Subject: Alpha & pc98 testers wanted Date: Fri, 31 Mar 2000 16:51:06 +0200 Message-ID: <698.954514266@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, The following patch to the 5.0-CURRENT sources allows the installkernel target to install multiple kernels. Given the following in /etc/make.conf: KERNEL= AXL AXLOPT GENERIC the installkernel target would install: AXL -> /kernel AXLOPT -> /kernel.AXLOPT GENERIC -> /kernel.GENERIC I've tested this for the i386 and would prefer to have it tested on the Alpha and pc98 before committing it, although I'm convinced that it should work on both of those platforms. Thanks, Sheldon. PS: This patch comes from PR 17698. Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.143 diff -u -d -r1.143 Makefile.inc1 --- Makefile.inc1 2000/03/30 13:06:53 1.143 +++ Makefile.inc1 2000/03/31 12:19:48 @@ -339,6 +339,7 @@ # properly. KERNEL?= GENERIC GENERIC98 +DESTKERNEL?= kernel # The only exotic MACHINE_ARCH/MACHINE combination valid at this # time is i386/pc98. In all other cases set MACHINE equal to @@ -357,11 +358,14 @@ BUILDKERNELS= INSTALLKERNEL= +INSTALLKERNELS= .for _kernel in ${KERNEL} .if exists(${KRNLCONFDIR}/${_kernel}) BUILDKERNELS+= ${_kernel} .if empty(INSTALLKERNEL) INSTALLKERNEL= ${_kernel} +.else +INSTALLKERNELS+= ${_kernel} .endif .endif .endfor @@ -392,12 +396,25 @@ # # installkernel # -# Install the kernel defined by INSTALLKERNEL +# Install the kernel defined by INSTALLKERNEL and INSTALLKERNELS # installkernel: + @echo + @echo "--------------------------------------------------------------" + @echo ">>> Installing kernel(s)" + @echo "--------------------------------------------------------------" + @echo "===> ${INSTALLKERNEL} as ${DESTDIR}/${DESTKERNEL}" cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \ ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \ - ${MAKE} install + DESTKERNEL=${DESTKERNEL} ${MAKE} install +.for _kernel in ${INSTALLKERNELS} + @echo "===> ${_kernel} as ${DESTDIR}/${DESTKERNEL}.${_kernel}" + cd ${KRNLOBJDIR}/${_kernel}; \ + ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} \ + DESTKERNEL=${DESTKERNEL}.${_kernel} ${MAKE} install +.endfor + + # # update Index: sys/conf/Makefile.alpha =================================================================== RCS file: /home/ncvs/src/sys/conf/Makefile.alpha,v retrieving revision 1.48 diff -u -d -r1.48 Makefile.alpha --- sys/conf/Makefile.alpha 2000/03/29 23:20:35 1.48 +++ sys/conf/Makefile.alpha 2000/03/31 14:40:39 @@ -21,6 +21,7 @@ # Can be overridden by makeoptions or /etc/make.conf KERNEL?= kernel +DESTKERNEL?= ${KERNEL} STD8X16FONT?= iso .if !defined(S) @@ -243,16 +244,16 @@ echo "You must build a kernel first." ; \ exit 1 ; \ fi -.if exists(${DESTDIR}/${KERNEL}) - -chflags noschg ${DESTDIR}/${KERNEL} - mv ${DESTDIR}/${KERNEL} ${DESTDIR}/${KERNEL}.old +.if exists(${DESTDIR}/${DESTKERNEL}) + -chflags noschg ${DESTDIR}/${DESTKERNEL} + mv -f ${DESTDIR}/${DESTKERNEL} ${DESTDIR}/${DESTKERNEL}.old .endif install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${DESTKERNEL} reinstall reinstall.debug: install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${DESTKERNEL} config.o: ${NORMAL_C} Index: sys/conf/Makefile.i386 =================================================================== RCS file: /home/ncvs/src/sys/conf/Makefile.i386,v retrieving revision 1.180 diff -u -d -r1.180 Makefile.i386 --- sys/conf/Makefile.i386 2000/03/29 23:20:35 1.180 +++ sys/conf/Makefile.i386 2000/03/31 12:16:50 @@ -21,6 +21,7 @@ # Can be overridden by makeoptions or /etc/make.conf KERNEL?= kernel +DESTKERNEL?= ${KERNEL} STD8X16FONT?= iso .if !defined(S) @@ -197,16 +198,16 @@ echo "You must build a kernel first." ; \ exit 1 ; \ fi -.if exists(${DESTDIR}/${KERNEL}) - -chflags noschg ${DESTDIR}/${KERNEL} - mv ${DESTDIR}/${KERNEL} ${DESTDIR}/${KERNEL}.old +.if exists(${DESTDIR}/${DESTKERNEL}) + -chflags noschg ${DESTDIR}/${DESTKERNEL} + mv -f ${DESTDIR}/${DESTKERNEL} ${DESTDIR}/${DESTKERNEL}.old .endif install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${DESTKERNEL} reinstall reinstall.debug: install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${DESTKERNEL} config.o: ${NORMAL_C} Index: sys/conf/Makefile.pc98 =================================================================== RCS file: /home/ncvs/src/sys/conf/Makefile.pc98,v retrieving revision 1.83 diff -u -d -r1.83 Makefile.pc98 --- sys/conf/Makefile.pc98 2000/03/29 23:20:35 1.83 +++ sys/conf/Makefile.pc98 2000/03/31 14:41:43 @@ -23,6 +23,7 @@ # Can be overridden by makeoptions or /etc/make.conf KERNEL?= kernel +DESTKERNEL?= ${KERNEL} #STD8X16FONT?= iso .if !defined(S) @@ -200,16 +201,16 @@ echo "You must build a kernel first." ; \ exit 1 ; \ fi -.if exists(${DESTDIR}/${KERNEL}) - -chflags noschg ${DESTDIR}/${KERNEL} - mv ${DESTDIR}/${KERNEL} ${DESTDIR}/${KERNEL}.old +.if exists(${DESTDIR}/${DESTKERNEL}) + -chflags noschg ${DESTDIR}/${DESTKERNEL} + mv -f ${DESTDIR}/${DESTKERNEL} ${DESTDIR}/${DESTKERNEL}.old .endif install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/install//} ${DESTDIR}/${DESTKERNEL} reinstall reinstall.debug: install -c -m 555 -o root -g wheel -fschg \ - ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${KERNEL} + ${KERNEL}${.TARGET:S/reinstall//} ${DESTDIR}/${DESTKERNEL} config.o: ${NORMAL_C} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 6:53:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id CACE237B652 for ; Fri, 31 Mar 2000 06:53:12 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.10.0/8.10.0) id e2VEqw219507; Fri, 31 Mar 2000 09:52:58 -0500 (EST) Date: Fri, 31 Mar 2000 09:52:58 -0500 From: Steve Ames To: Peter Wemm Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NO_SENDMAIL in /etc/make.conf Message-ID: <20000331095258.A86650@virtual-voodoo.com> References: <20000331060434.BA7631CD7@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000331060434.BA7631CD7@overcee.netplex.com.au>; from peter@netplex.com.au on Thu, Mar 30, 2000 at 10:04:34PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 10:04:34PM -0800, Peter Wemm wrote: > Steve Ames wrote: > > > > I have NO_SENDMAIL= true in /etc/make.conf but sendmail got rebuilt > > on the last makeworld anyway... this is -CURRENT from this morning > > (3/30). > > > > -Steve > > man mailwrapper > man mailer.conf > > Then see /etc/mail/mailer.conf Doh. I knew that. Now I'll go slap myself. As always, thanks for pointing out when I'm being dense :) -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 7:58:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 687B437B909; Fri, 31 Mar 2000 07:58:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA07737; Fri, 31 Mar 2000 17:52:54 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id IAA50613; Fri, 31 Mar 2000 08:14:27 +0200 (CEST) (envelope-from wilko) Date: Fri, 31 Mar 2000 08:14:27 +0200 From: Wilko Bulte To: Sergey Babkin Cc: wilko@FreeBSD.ORG, sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: Anybody have tools to read a Digital Unix "vdump" tape on FreebSD? Message-ID: <20000331081427.A50579@yedi.iaf.nl> Reply-To: wilko@FreeBSD.ORG References: <42000.954338392@verdi.nethelp.no> <20000329204851.C2044@yedi.iaf.nl> <38E3F526.79CBAE3B@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38E3F526.79CBAE3B@bellatlantic.net>; from babkin@bellatlantic.net on Thu, Mar 30, 2000 at 07:45:26PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 07:45:26PM -0500, Sergey Babkin wrote: > Wilko Bulte wrote: > > > > On Wed, Mar 29, 2000 at 03:59:52PM +0200, sthaug@nethelp.no wrote: > > > Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD? > > > I have a number of such tapes, and would prefer to read them on an (Intel) > > > FreeBSD box instead of having to reinstall DU on a machine which has had > > > its disks wiped. > > > > Vdump, the dump incarnation for Tru64 AdvFS, can to the best of my knowledge > > only be read by vrestore. I'm afraid your stuck to using a T64 box for this. > > If AdvFS is just another incarnation of VXFS there may be > a chance that it could be read by vxrestore on UnixWare. > So if there is absolutely no Alpha machine around then > free UnixWare (binary-only but still free except for the > CD cost, like $17) may be worth a try. It is a development of the Digital era, originally called MegaSafe Filesystem. It is not, AFAIK, based on VxFS at all. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: 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 Fri Mar 31 8: 8: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law2-f121.hotmail.com [216.32.181.121]) by hub.freebsd.org (Postfix) with SMTP id 76D8937B909 for ; Fri, 31 Mar 2000 08:08:06 -0800 (PST) (envelope-from karnanfans@hotmail.com) Received: (qmail 36798 invoked by uid 0); 31 Mar 2000 16:08:05 -0000 Message-ID: <20000331160805.36797.qmail@hotmail.com> Received: from 212.75.75.43 by www.hotmail.com with HTTP; Fri, 31 Mar 2000 08:08:05 PST X-Originating-IP: [212.75.75.43] From: "sdf dsg" To: hackers@freebsd.org Subject: FTP server Date: Fri, 31 Mar 2000 16:08:05 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after i have looked arround i cant find where to restrict ftp users to their home dir only, pleas help me!!!!! ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 8:15:45 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 017D437B6B2 for ; Fri, 31 Mar 2000 08:15:42 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2VGeYF29197; Fri, 31 Mar 2000 08:40:34 -0800 (PST) Date: Fri, 31 Mar 2000 08:40:34 -0800 From: Alfred Perlstein To: sdf dsg Cc: hackers@FreeBSD.ORG Subject: Re: FTP server Message-ID: <20000331084030.K21029@fw.wintelcom.net> References: <20000331160805.36797.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000331160805.36797.qmail@hotmail.com>; from karnanfans@hotmail.com on Fri, Mar 31, 2000 at 04:08:05PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * sdf dsg [000331 08:33] wrote: > after i have looked arround i cant find where to restrict ftp users to their > home dir only, pleas help me!!!!! 5. If the user name appears in the file /etc/ftpchroot, or the user is a member of a group with a group entry in this file, i.e. one prefixed with `@', the session's root will be changed to the user's login directory by chroot(2) as for an ``anonymous'' or ``ftp'' account (see next item). This facil- ity may also be triggered by enabling the boolean "ftp-chroot" capability in login.conf(5). However, the user must still supply a password. This feature is intended as a compromise between a fully anonymous account and a fully privileged ac- count. The account should also be set up as for an anonymous account. it's in the ftpd manpage. -- -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 Mar 31 8:17:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.networkrichmond.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id C601937BB6D for ; Fri, 31 Mar 2000 08:17:36 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: Network Richmond, LLC. http://www.networkrichmond.com/ Received: from localhost (kbyanc@localhost) by kronos.networkrichmond.com (8.9.3/8.9.3/antispam) with ESMTP id LAA89753; Fri, 31 Mar 2000 11:17:32 -0500 (EST) Date: Fri, 31 Mar 2000 11:17:32 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.networkrichmond.com To: sdf dsg Cc: hackers@FreeBSD.ORG Subject: Re: FTP server In-Reply-To: <20000331160805.36797.qmail@hotmail.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 Fri, 31 Mar 2000, sdf dsg wrote: > after i have looked arround i cant find where to restrict ftp users to their > home dir only, pleas help me!!!!! The man pages are always good places to start. See ftpd(8), particularly the paragraph: If the user name appears in the file /etc/ftpchroot, or the user is a member of a group with a group entry in this file, i.e. one prefixed with `@', the session's root will be changed to the user's login directory by chroot(2) as for an ``anonymous'' or ``ftp'' account (see next item). This facil- ity may also be triggered by enabling the boolean "ftp-chroot" capability in login.conf(5). However, the user must still supply a password. This feature is intended as a compromise between a fully anonymous account and a fully privileged ac- count. The account should also be set up as for an anonymous account. Personally, I'm fond of putting ftp-chroot in login.conf for a user class specific to FTP users, but your mileage may vary. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 8:38:39 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 A005E37B919; Fri, 31 Mar 2000 08:38:34 -0800 (PST) (envelope-from imp@harmony.village.org) 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 JAA73821; Fri, 31 Mar 2000 09:38:27 -0700 (MST) (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 JAA35513; Fri, 31 Mar 2000 09:37:58 -0700 (MST) Message-Id: <200003311637.JAA35513@harmony.village.org> To: John Baldwin Subject: Re: USB Installation - Working Release! Cc: hackers@FreeBSD.ORG, n_hibma@FreeBSD.ORG, dcs@newsguy.com In-reply-to: Your message of "Fri, 31 Mar 2000 08:20:03 EST." <200003311320.IAA92577@server.baldwin.cx> References: <200003311320.IAA92577@server.baldwin.cx> Date: Fri, 31 Mar 2000 09:37:58 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003311320.IAA92577@server.baldwin.cx> John Baldwin writes: : Cool. The only extra part is reading the current config out of a loaded : kernel. Now where did our Forth hackers go? :) Well, this would be pretty trivial if config has hacked to have similar hints and have those be loaded FIRST by the boot loader, then loader.conf and then fire up USERCONFIG. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 9: 8:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 98A9637B7BE; Fri, 31 Mar 2000 09:08:22 -0800 (PST) (envelope-from jgowdy@home.com) Received: from cx443070a ([24.4.93.90]) by mail.rdc1.va.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000331170821.ZJWY12441.mail.rdc1.va.home.com@cx443070a>; Fri, 31 Mar 2000 09:08:21 -0800 Message-ID: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> From: "Jeremiah Gowdy" To: , , "FreeBSD questions" Subject: JetDirect 500X and FreeBSD Date: Fri, 31 Mar 2000 09:17:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have any experiance or information about using HP JetDirect 500X Printer Hubs with FreeBSD ? This is mission critical for my company, so any information greatly appriciated. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 9: 8:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ludwig.troikanetworks.com (host03.troikanetworks.com [12.31.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 1F0B237BFC8; Fri, 31 Mar 2000 09:08:41 -0800 (PST) (envelope-from ericp@troikanetworks.com) Received: by host03.troikanetworks.com with Internet Mail Service (5.5.2650.21) id ; Fri, 31 Mar 2000 09:08:47 -0800 Message-ID: From: Eric Peterson To: 'Tony Finch' , nik@freebsd.org Cc: hackers@freebsd.org Subject: RE: No route for 127/8 to lo0 (?) - another use for loopback subn et? Date: Fri, 31 Mar 2000 09:08:39 -0800 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 Tony Finch [mailto:dot@dotat.at] wrote: > Nik Clayton wrote: >> >> I thought that 127/8 was the "local net", and that >> packets sent to any of those addresses would go via >> the loopback interface. That seems to be how Linux >> and Windows 98 do things (the only systems I can >> check this on at the moment). Assuming that's the >> case, why does FreeBSD only add a a host route to >> 127.0.0.1, and not a network route for 127/8? > > I did some further investigation to see how old this > oddity is and it seems to be the way BSD has always > handled the loopback interface. There's an explicit > exclusion in the interface initialization code in in.c > that gives loopback interfaces a host route instead of > the network route that a normal interface gets and it's > been that way for 15 years. I always thought it was a great waste of network address space to devote an entire class A network to a single loopback address. An idea I got from a co-worker a while ago was to allow the 127.* (or some smaller subnet of 127) to be devoted to "intra-box addresses", for example: 1. A cluster of devices/slots within a chassis 2. A parallel processing machine 3. A multi-processor computer/device All of the above may have inter-processor communications that do not need to leave the chassis. Analogous to how the 192.168.* (RFC1918) addresses are used for intranets, these addresses wouldn't be allowed to be seen by the outside world (i.e. outside the "chassis"), but would permit internal IP communication without having to waste (and configure) a "real" IP net number. If these devices needed to get to the outside world, they could use NAT (again, analogously to the RFC1918 case). Regards, Eric -- Eric Peterson ericp@troikanetworks.com (805) 370-3046 PGP: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x4DA8EEF1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 9:34:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 6727E37B9D9 for ; Fri, 31 Mar 2000 09:34:14 -0800 (PST) (envelope-from matt@thebiz.net) Received: (qmail 16474 invoked from network); 31 Mar 2000 12:34:12 -0500 Received: from mail2.thebiz.net (172.16.0.129) by mx1.thebiz.net with SMTP; 31 Mar 2000 12:34:12 -0500 Received: (qmail 14459 invoked by uid 0); 31 Mar 2000 12:34:11 -0500 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.thebiz.net with SMTP; 31 Mar 2000 12:34:11 -0500 Message-ID: <019001bf9b37$3111f430$1401eed8@mahatma> From: "Matthew Zahorik" To: Subject: BOOTP kernel modification Date: Fri, 31 Mar 2000 12:33:13 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have a problem where I'm trying to bootp an Alpha box. It works great over a hub, but through a switch it fails miserably. I tracked it down to a bad autoconfiguration. The switch is autonegotiating 100Mb/fdx and the client is autonegotiating 100Mb/hdx. Needless to say, this doesn't help with BOOTP requests - things tend to time out. Forcing the switch to 100Mb/hdx makes the process work smoothly. Forcing the switch to 100Mb/fdx causes more timeouts. For other reasons, I'd like to force the switch to 100Mb/fdx at all times, and just force the BOOTP process to initialize the card at a 100Mb/fdx. I'm new to kernel programming, so I'd like someone to tell me if this is the correct way to do this. In nfs/bootp_subr.c in the function bootpc_fakeup_interface you have: /* * Bring up the interface. * * Get the old interface flags and or IFF_UP into them; if * IFF_UP set blindly, interface selection can be clobbered. */ error = ifioctl(so, SIOCGIFFLAGS, (caddr_t)ireq, procp); if (error) panic("bootpc_fakeup_interface: GIFFLAGS, error=%d", error); ireq->ifr_flags |= IFF_UP; error = ifioctl(so, SIOCSIFFLAGS, (caddr_t)ireq, procp); if (error) panic("bootpc_fakeup_interface: SIFFLAGS, error=%d", error); to which I'd add: ireq->ifr_media = IFF_100_TX | IFF_FDX; error = ifioctl(so, SIOCSIFMEDIA, (caddr_t)ireq, procp); if (error) panic("bootpc_fakeup_interface: SIFMEDIA, error=%d", error); right before the SIOCGIFFFLAGS ioctl, so the media type would be set before the interface would be brought up. Will this work? (: Is the interface initialized somewhere else in the kernel? (excluding ifconfigs in startup scripts, which I'm well aware of) If it doesn't work, how do I get this bit of code to force 100Mb/fdx? I have no problem making this into a kernel option like 'option BOOTP_FORCE_MEDIA="IFF_100_TX | IFF_FDX" ' Also, netboot will have to be changed (yes, it works on Alpha just fine) b ut I can't get it to compile. Before I monkey around with it more, is there a magic trick? It currently breaks looking for net.h and net_if.h Finally, the link and activity lights don't work on these machines after the kernel boots: dc0: port 0x1100-0x117f mem 0x20c2000-0x20c23ff \ irq 29 at device 9.0 on pci0 dc0: interrupting at TSUNAMI irq 29 dc0: Ethernet address: 08:00:2b:86:28:54 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto What part of the code should I look at to get this working? This is all on 4.0-RELEASE on a Tsunami based Alpha (DS10, 466MHz EV6) Thanks! - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 11:16:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spcem01sgl.sugar-land.omnes.net (spcem01sgl.sugar-land.omnes.net [163.188.48.51]) by hub.freebsd.org (Postfix) with ESMTP id B868A37BDC7 for ; Fri, 31 Mar 2000 11:16:47 -0800 (PST) (envelope-from rayk@sugar-land.spc.slb.com) Received: from rayk-sgl.sugar-land.spc.slb.com ([163.188.49.242]) by spcem01sgl.sugar-land.omnes.net (Post.Office MTA v3.5.3 release 223 ID# 0-58147U25000L25000S0V35) with ESMTP id net for ; Fri, 31 Mar 2000 13:10:18 -0600 Message-Id: <4.3.1.2.20000331123429.00ad6890@163.188.48.51> X-Sender: rayk@163.188.48.51 X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 31 Mar 2000 13:16:36 -0600 To: freebsd-hackers@FreeBSD.ORG From: Keith Ray Subject: ssh timeouts & ipfw dyn_ack_lifetime 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 I am having a problem with ssh sessions from my windows box to my freebsd box timing out after a number of idle minutes. SecureCRT still shows a valid connection until I try to type some keys, and then after a minute it says "connecton reset". I believe I have isolated the problem to the ipfw firewall timing out the connection. I am currently using dynamic rules such as: add check-state add reset tcp from any to {myip} established add reset tcp from {myip} to any established add allow tcp from any to {myip} ssh setup keep-state The sysctl variable net.inet.ip.fw.dyn_ack_lifetime seems to be responsible for this, but I only want to set a very large lifetime for things like ssh. Is it possible to disable automatic timeouts or make long timeouts on a rule-by-rule basis? Or perhaps a way to keep the dynamic rule alive as long as the connection is alive? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 11:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 55DEA37BE6C for ; Fri, 31 Mar 2000 11:37:46 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA44427; Fri, 31 Mar 2000 21:38:18 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003311938.VAA44427@info.iet.unipi.it> Subject: Re: ssh timeouts & ipfw dyn_ack_lifetime In-Reply-To: <4.3.1.2.20000331123429.00ad6890@163.188.48.51> from Keith Ray at "Mar 31, 2000 01:16:36 pm" To: Keith Ray Date: Fri, 31 Mar 2000 21:38:18 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 As Larry Baird was suggesting in a private email, one way to handle this problem would be to have the firewall issue keepalives to refresh the state. Unfortunately the connection can be alive without any traffic flowing, and you cannot rely on keepalives on both sides of the connection. On the other hand, if you look at the sysctl variables, you see that the timeout after a FIN becomes quite short so i think it is not _that_ bad having much larger timeouts than the ones i set, because properly closed connection will still make the rule expire very quickly. Yes the timeouts could be made configurable on a per-rule basis, at the price of some additional parameter in the ipfw rules. But i am not planning such a change at the moment. cheers luigi > I am having a problem with ssh sessions from my windows box to my freebsd > box timing out after a number of idle minutes. SecureCRT still shows a > valid connection until I try to type some keys, and then after a minute it > says "connecton reset". I believe I have isolated the problem to the ipfw > firewall timing out the connection. I am currently using dynamic rules > such as: > > add check-state > add reset tcp from any to {myip} established > add reset tcp from {myip} to any established > add allow tcp from any to {myip} ssh setup keep-state > > The sysctl variable net.inet.ip.fw.dyn_ack_lifetime seems to be responsible > for this, but I only want to set a very large lifetime for things like > ssh. Is it possible to disable automatic timeouts or make long timeouts on > a rule-by-rule basis? Or perhaps a way to keep the dynamic rule alive as > long as the connection is alive? > -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 11:59:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg132-048.ricochet.net [204.179.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 2C24437B693 for ; Fri, 31 Mar 2000 11:59:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA00310; Fri, 31 Mar 2000 09:45:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003311745.JAA00310@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew Zahorik" Cc: freebsd-hackers@freebsd.org Subject: Re: BOOTP kernel modification In-reply-to: Your message of "Fri, 31 Mar 2000 12:33:13 EST." <019001bf9b37$3111f430$1401eed8@mahatma> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Mar 2000 09:45:56 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > I have a problem where I'm trying to bootp an Alpha box. It works great > over a hub, but through a switch it fails miserably. > > I tracked it down to a bad autoconfiguration. The switch is > autonegotiating 100Mb/fdx and the client is autonegotiating 100Mb/hdx. > Needless to say, this doesn't help with BOOTP requests - things tend to time > out. Forcing the switch to 100Mb/hdx makes the process work smoothly. > Forcing the switch to 100Mb/fdx causes more timeouts. > > For other reasons, I'd like to force the switch to 100Mb/fdx at all times, > and just force the BOOTP process to initialize the card at a 100Mb/fdx. The 'dc' driver will pick up the settings from SRM, so just initialise the SRM correctly to whatever you want. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 12:14:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spcem01sgl.sugar-land.omnes.net (spcem01sgl.sugar-land.omnes.net [163.188.48.51]) by hub.freebsd.org (Postfix) with ESMTP id 32CB537BF00 for ; Fri, 31 Mar 2000 12:14:35 -0800 (PST) (envelope-from rayk@sugar-land.spc.slb.com) Received: from rayk-sgl.sugar-land.spc.slb.com ([163.188.49.242]) by spcem01sgl.sugar-land.omnes.net (Post.Office MTA v3.5.3 release 223 ID# 0-58147U25000L25000S0V35) with ESMTP id net for ; Fri, 31 Mar 2000 14:07:59 -0600 Message-Id: <4.3.1.2.20000331141018.00ae0e10@163.188.48.51> X-Sender: rayk@163.188.48.51 X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 31 Mar 2000 14:14:16 -0600 To: freebsd-hackers@FreeBSD.ORG From: Keith Ray Subject: Re: ssh timeouts & ipfw dyn_ack_lifetime In-Reply-To: <4.3.1.2.20000331123429.00ad6890@163.188.48.51> 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 At 01:16 PM 3/31/00 -0600, you wrote: >I am having a problem with ssh sessions from my windows box to my freebsd >box timing out after a number of idle minutes. SecureCRT still shows a >valid connection until I try to type some keys, and then after a minute it >says "connecton reset". I believe I have isolated the problem to the ipfw >firewall timing out the connection. I am currently using dynamic rules >such as: > >add check-state >add reset tcp from any to {myip} established >add reset tcp from {myip} to any established >add allow tcp from any to {myip} ssh setup keep-state > >The sysctl variable net.inet.ip.fw.dyn_ack_lifetime seems to be >responsible for this, but I only want to set a very large lifetime for >things like ssh. Is it possible to disable automatic timeouts or make >long timeouts on a rule-by-rule basis? Or perhaps a way to keep the >dynamic rule alive as long as the connection is alive? I believe I may have found a solution. If I set net.inet.tcp.keepidle < net.inet.ip.fw.dyn_ack_lifetime, this appears to work. The defaults for these values are 2 hours and 5 minutes respectively. Would it be better to set the keepidle to something small like 2.5 minutes or would it be better to make the dyn_ack_lifetime big like 3 hours? Setting the keepalive small seems the best solution, but what repercussions would there be? Why is it two hours by default? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 12:37:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 09BEC37B9FC for ; Fri, 31 Mar 2000 12:37:10 -0800 (PST) (envelope-from edgold@mindspring.com) Received: from mindspring.com (user-37katqp.dialup.mindspring.com [207.69.119.89]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id PAA29546 for ; Fri, 31 Mar 2000 15:36:38 -0500 (EST) Message-ID: <38E50AF8.B9B279DF@mindspring.com> Date: Fri, 31 Mar 2000 15:30:49 -0500 From: Edward Gold X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "hackers@FreeBSD.ORG" Subject: I am having serious problems with ppi0, can anybody help? Content-Type: multipart/alternative; boundary="------------4C38CF90EFAA1418230E361F" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------4C38CF90EFAA1418230E361F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I seem to be crashing my system every time I attempt to open /dev/ppi0! I get a kernel panic, and it usually explains that nexus_setup_intr is unhappy. I traced this all down to /usr/src/sys/i386/i386/nexus.c where it claims that somebody tried to setup an irq that failed to allocate. I suspected that I might have a kernel slightly out of sync with my libraries, so I did the complete cvsup, buildworld, and installworld last night. Everything seems to be operating correctly, with the exception of the ppi driver. The piece of code I was running looks like this: #include #include #include #include #include #define PPIGDATA _IOR('P', 10, u_int8_t) #define PPIGSTATUS _IOR('P', 11, u_int8_t) #define PPIGCTRL _IOR('P', 12, u_int8_t) #define PPIGEPPD _IOR('P', 13, u_int8_t) #define PPIGECR _IOR('P', 14, u_int8_t) #define PPIGFIFO _IOR('P', 15, u_int8_t) #define PPISDATA _IOW('P', 16, u_int8_t) #define PPISSTATUS _IOW('P', 17, u_int8_t) #define PPISCTRL _IOW('P', 18, u_int8_t) #define PPISEPPD _IOW('P', 19, u_int8_t) #define PPISECR _IOW('P', 20, u_int8_t) #define PPISFIFO _IOW('P', 21, u_int8_t) #define PPIGEPPA _IOR('P', 22, u_int8_t) #define PPISEPPA _IOR('P', 23, u_int8_t) #define n(flags) (~(flags) & (flags)) /* * Parallel Port Chipset control bits. */ #define STROBE 0x01 #define AUTOFEED 0x02 #define nINIT 0x04 #define SELECTIN 0x08 #define IRQENABLE 0x10 #define PCD 0x20 #define nSTROBE n(STROBE) #define nAUTOFEED n(AUTOFEED) #define INIT n(nINIT) #define nSELECTIN n(SELECTIN) #define nPCD n(PCD) int pport_fd; main() { unsigned char data, status, ctrl; int pattern = 'A'; pport_fd = open( "/dev/ppi0", O_RDONLY ); if( pport_fd < 0 ) { fprintf( stderr, "\nFailed to open printer port! 0x%x\n", pport_fd ); exit( 1 ); } else { printf( "\nopened port\n" ); fflush( stdout ); } while( 1 ) { ioctl( pport_fd, PPIGDATA, &data ); ioctl( pport_fd, PPIGSTATUS, &status ); ioctl( pport_fd, PPIGCTRL, &ctrl ); printf("Status: 0x%.2x, Ctrl: 0x%.2x, Data: 0x%.2x\n", status, ctrl, data); sleep( 1 ); } } It explodes when it hits the open() statement. The only other clue I have is that I always find a lpd.core lying around in /, but the date is way off. Does anyone have a clue whats going on? Also, what I am really trying to do here is read a signal pin into FreeBSD somehow. Its either 0 or +5V and it doesn't have to be real-time or fast or anything but accurate. I just basically want to sample and detect whether or not a button on a custom panel is being pressed or not. We would even be willing to get the signal in through the PE, -ACK, or whatever pins. I have tried going through the /dev/joy0 interface and it doesn't seem to sense anything ( though the hardware is PC-104 stuff, so I didn't put much faith in this ). The joy device driver does detect the port and it seems to read something, but its always the same value. I don't actually have a joystick to test this, so this could actually be working but I might not be pulling the pins to ground or +5 or whatever they are supposed to be pulled to. One thing that makes me very proud of FreeBSD is that its device drivers actually did work with the sound card DSP whereas the manufacturer's drivers did not! Also, this sysem uses the M-systems Disk On Chip2000, and FreeBSD already had the support right there in the LINT file, while Linux would have required kernel and LILO patches. --------------4C38CF90EFAA1418230E361F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

I seem to be crashing my system every time I attempt to open /dev/ppi0!  I get a kernel panic, and it usually explains that nexus_setup_intr is unhappy.  I traced this all down to  /usr/src/sys/i386/i386/nexus.c  where it claims that somebody tried to setup an irq that failed to allocate.  I suspected that I might have a kernel slightly out of sync with my libraries, so I did the complete cvsup, buildworld, and installworld last night.  Everything seems to be operating correctly, with the exception of the ppi driver.

The piece of code I was running looks like this:

#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/ioctl.h>
#include <sys/fcntl.h>

#define PPIGDATA        _IOR('P', 10, u_int8_t)
#define PPIGSTATUS      _IOR('P', 11, u_int8_t)
#define PPIGCTRL        _IOR('P', 12, u_int8_t)
#define PPIGEPPD        _IOR('P', 13, u_int8_t)
#define PPIGECR         _IOR('P', 14, u_int8_t)
#define PPIGFIFO        _IOR('P', 15, u_int8_t)

#define PPISDATA        _IOW('P', 16, u_int8_t)
#define PPISSTATUS      _IOW('P', 17, u_int8_t)
#define PPISCTRL        _IOW('P', 18, u_int8_t)
#define PPISEPPD        _IOW('P', 19, u_int8_t)
#define PPISECR         _IOW('P', 20, u_int8_t)
#define PPISFIFO        _IOW('P', 21, u_int8_t)

#define PPIGEPPA        _IOR('P', 22, u_int8_t)
#define PPISEPPA        _IOR('P', 23, u_int8_t)
#define n(flags) (~(flags) & (flags))

/*
 * Parallel Port Chipset control bits.
 */
#define STROBE          0x01
#define AUTOFEED        0x02
#define nINIT           0x04
#define SELECTIN        0x08
#define IRQENABLE       0x10
#define PCD             0x20

#define nSTROBE         n(STROBE)
#define nAUTOFEED       n(AUTOFEED)
#define INIT            n(nINIT)
#define nSELECTIN       n(SELECTIN)
#define nPCD            n(PCD)
 

int pport_fd;

main()
{
  unsigned char data, status, ctrl;
  int pattern = 'A';

  pport_fd = open( "/dev/ppi0", O_RDONLY );
  if( pport_fd < 0 )
  {
    fprintf( stderr, "\nFailed to open printer port! 0x%x\n", pport_fd );
    exit( 1 );
  }
  else
  {
    printf( "\nopened port\n" ); fflush( stdout );
  }

  while( 1 )
  {
    ioctl( pport_fd, PPIGDATA,   &data );
    ioctl( pport_fd, PPIGSTATUS, &status );
    ioctl( pport_fd, PPIGCTRL,   &ctrl );

    printf("Status: 0x%.2x, Ctrl: 0x%.2x, Data: 0x%.2x\n", status, ctrl, data);
    sleep( 1 );
  }
}
 

It explodes when it hits the open() statement.  The only other clue I have is that I always find a lpd.core lying around in /, but the date is way off.  Does anyone have a clue whats going on?

Also, what I am really trying to do here is read a signal pin into FreeBSD somehow.  Its either 0 or +5V and it doesn't have to be real-time or fast or anything but accurate.  I just basically want to sample and detect whether or not a button on a custom panel is being pressed or not.  We would even be willing to get the signal in through the PE, -ACK, or whatever pins.

I have tried going through the /dev/joy0 interface and it doesn't seem to sense anything ( though the hardware is  PC-104 stuff, so I didn't put much faith in this ).  The joy device driver does detect the port and it seems to read something, but its always the same value.   I don't actually have a joystick to test this, so this could actually be working but I might not be pulling the pins to ground or +5 or whatever they are supposed to be pulled to.

One thing that makes me very proud of FreeBSD is that its device drivers actually did work with the sound card DSP whereas the manufacturer's drivers did not!  Also, this sysem uses the M-systems Disk On Chip2000, and FreeBSD already had the support right there in the LINT file, while Linux would have required kernel and LILO patches.
 
 
  --------------4C38CF90EFAA1418230E361F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 13: 5:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 791E537C1CE for ; Fri, 31 Mar 2000 13:05:17 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id XAA44689; Fri, 31 Mar 2000 23:05:27 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003312105.XAA44689@info.iet.unipi.it> Subject: Re: ssh timeouts & ipfw dyn_ack_lifetime In-Reply-To: <4.3.1.2.20000331141018.00ae0e10@163.188.48.51> from Keith Ray at "Mar 31, 2000 02:14:16 pm" To: Keith Ray Date: Fri, 31 Mar 2000 23:05:27 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > I believe I may have found a solution. If I set net.inet.tcp.keepidle < > net.inet.ip.fw.dyn_ack_lifetime, this appears to work. The defaults for yes, though this assumes thay you can set the keepalive interval on at least one end, and you know the lifetime of dynamic rules on the firewall, both things that you should not be required to do. [this is not to say that it doesn't work, just that ipfw should do something smarter!] > these values are 2 hours and 5 minutes respectively. Would it be better to > set the keepidle to something small like 2.5 minutes or would it be better > to make the dyn_ack_lifetime big like 3 hours? Setting the keepalive small > seems the best solution, but what repercussions would there be? Why is it > two hours by default? because a short keepalive would keep dialup connection up even if no traffic is flowing, etc. etc. -- so i would move both values to something like 10-30min. But for your setting, basically any solution would do. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 13:33:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 437B737B8D0 for ; Fri, 31 Mar 2000 13:33:27 -0800 (PST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id XAA12285; Fri, 31 Mar 2000 23:33:22 +0200 (CEST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: (from naddy@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA54968; Fri, 31 Mar 2000 22:43:27 +0200 (CEST) (envelope-from naddy) Date: Fri, 31 Mar 2000 22:43:27 +0200 From: Christian Weisgerber To: Doug Barton Cc: freebsd-hackers@freebsd.org Subject: Re: Proposed new Bourne shell init files Message-ID: <20000331224327.Y581@bigeye.rhein-neckar.de> References: <38E2F801.548AAAF1@gorean.org> <8c0k5m$9fp$1@bigeye.rhein-neckar.de> <38E42987.856C2215@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38E42987.856C2215@gorean.org>; from Doug@gorean.org on Thu, Mar 30, 2000 at 08:28:55PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton: > > export VAR=value > The problem with that option is that it's not portable. It's just as portable as "set -o" and "alias". None of them are available in the original Bourne shell, all of them in the POSIX shell. > > alias r='fc -s' > > Hrrmm... ok. I have no experience with that, but I wouldn't object to its > inclusion. It's a pre-defined alias in ksh where the entire POSIX history scheme is taken from. Roughly, it's the equivalent to the csh '!' history substitution, although less powerful. Use "r" to repeat the last command, "r cmd" to repeat the last command "cmd", and "r foo=bar ..." to effect a substitution on the recalled command line. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 13:42:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id A573837BA60 for ; Fri, 31 Mar 2000 13:42:36 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA73010; Fri, 31 Mar 2000 13:42:31 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 31 Mar 2000 13:42:31 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Christian Weisgerber Cc: freebsd-hackers@freebsd.org Subject: Re: Proposed new Bourne shell init files In-Reply-To: <20000331224327.Y581@bigeye.rhein-neckar.de> 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, 31 Mar 2000, Christian Weisgerber wrote: > Doug Barton: > > > > export VAR=value > > The problem with that option is that it's not portable. > > It's just as portable as "set -o" and "alias". None of them are > available in the original Bourne shell, all of them in the POSIX > shell. In my mind there is a difference between items that are freebsd-exclusive (like set -o and alias) and items that we have unique implementations of, like export. The latter are available on other platforms, and therefore, IMO we should follow the more generally accepted format. Extending that argument to either not take advantage of features unique to FreeBSD (silly and wasteful) or to doing everything FreeBSD'ish just because we can (teaches a bad lesson) goes too far in either direction for my taste. > > > alias r='fc -s' > > > > Hrrmm... ok. I have no experience with that, but I wouldn't object to its > > inclusion. > > It's a pre-defined alias in ksh where the entire POSIX history > scheme is taken from. Roughly, it's the equivalent to the csh '!' > history substitution, although less powerful. Use "r" to repeat > the last command, "r cmd" to repeat the last command "cmd", and "r > foo=bar ..." to effect a substitution on the recalled command line. Ok, that sounds like a valuable addition, thanks. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 14:54:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 1A01537B9CC for ; Fri, 31 Mar 2000 14:54:19 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id QAA02576; Fri, 31 Mar 2000 16:54:57 -0600 (CST) (envelope-from chris) Date: Fri, 31 Mar 2000 16:54:57 -0600 From: Chris Costello To: Doug Barton Cc: Christian Weisgerber , freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files Message-ID: <20000331165457.A2556@holly.calldei.com> Reply-To: chris@calldei.com References: <20000331224327.Y581@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, March 31, 2000, Doug Barton wrote: > In my mind there is a difference between items that are > freebsd-exclusive (like set -o and alias) and items that we have unique > implementations of, like export. The latter are available on other > platforms, and therefore, IMO we should follow the more generally accepted > format. Extending that argument to either not take advantage of features > unique to FreeBSD (silly and wasteful) or to doing everything FreeBSD'ish > just because we can (teaches a bad lesson) goes too far in either > direction for my taste. ``set -o'', ``alias'', and ``export'' are all portable. A few options for ``set -o'' may not be, but otherwise they are. Where did you get the idea that the first two were FreeBSD-exclusive? -- |Chris Costello |To be, or not to be, those are the parameters. `---------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 15:23:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 1FCF837B9CC for ; Fri, 31 Mar 2000 15:23:51 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id QAA05249; Fri, 31 Mar 2000 16:23:25 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38E533EC.30BE0E8B@softweyr.com> Date: Fri, 31 Mar 2000 16:25:32 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: hackers@FreeBSD.ORG Subject: Re: Shared /bin and /sbin References: <200003300722.AAA21918@harmony.village.org> <20000330212950.A92062@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > > According to Warner Losh: > > copies of libc in /sbin and /bin. I was thinking about building, for > > this system only, /bin and /sbin dynamic. Has anybody ever done this? > > Ask Bruce. He used to have a completely dynamic system a while ago... Whatever happened to the idea of putting the shared libs for /bin and /sbin in /lib? -- "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 Mar 31 15:57:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 0645837BA96 for ; Fri, 31 Mar 2000 15:57:13 -0800 (PST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id BAA21572; Sat, 1 Apr 2000 01:56:20 +0200 (CEST) (envelope-from naddy@bigeye.rhein-neckar.de) Received: (from naddy@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA61023; Sat, 1 Apr 2000 01:08:22 +0200 (CEST) (envelope-from naddy) Date: Sat, 1 Apr 2000 01:08:22 +0200 From: Christian Weisgerber To: Doug Barton Cc: freebsd-hackers@freebsd.org Subject: Re: Proposed new Bourne shell init files Message-ID: <20000401010822.A581@bigeye.rhein-neckar.de> References: <20000331224327.Y581@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from Doug@gorean.org on Fri, Mar 31, 2000 at 01:42:31PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton: > In my mind there is a difference between items that are > freebsd-exclusive (like set -o and alias) and items that we have unique > implementations of, like export. The latter are available on other > platforms, and therefore, IMO we should follow the more generally accepted > format. You're arguing from mistaken assumptions. "set -o" and "alias" are not in the least FreeBSD-exclusive. Nor do we have a unique implementation with "export VAR=value". These three features don't differ with respect to portability. To repeat: * They aren't part of the "original" Bourne shell (which was itself a moving target). * They were introduced with the Korn shell. * Later they were specified for the POSIX shell. * Every POSIX shell supports them. Whatever way you want to argue, if you want to stay coherent you have to treat these three features (and a bunch more) the same. And, considering the subject, I'd like to point out that FreeBSD's /bin/sh is not a Bourne shell clone but a POSIX shell. > Extending that argument to either not take advantage of features > unique to FreeBSD (silly and wasteful) or to doing everything FreeBSD'ish > just because we can (teaches a bad lesson) goes too far in either > direction for my taste. I think that's a bizarrely schizophrenic position, but anyway it isn't applicable to the actual shell features discussed above. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 16:50:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 4062537BAA7 for ; Fri, 31 Mar 2000 16:50:40 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustidentd@obie.softweyr.com [204.68.178.33]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id RAA05456; Fri, 31 Mar 2000 17:50:17 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <38E54847.EC9D152C@softweyr.com> Date: Fri, 31 Mar 2000 17:52:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Gustavo V G C Rios Cc: misc@openbsd.org, hackers@FreeBSD.ORG Subject: Re: BSDs References: <38E3CAB5.8C23044@tdnet.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo V G C Rios wrote: > > Hy folks! > > I have been playing with FreeBSD for the last 1 year and some time ago i > decide to give openbsd a try. > > I have been loving Free! Now, playing with Open is no trouble. > Some questions came up: > > 1) What are the advantages/disadavantages of using FreeBSD or OpenBSD? > 2) FreeBSD has proven to be a high quality OS for stupid heavy loaded > site (ftp.cdrom.com)! Can OpenBSD support such a very loaded site? > Since i have never seen such a heavy loaded site using Open, i would > like to know if it (Open) can support such a load using the same > hardware Free uses. > 3) What are the advantage from OpenBSD over FreeBSD, and FreeBSD over > OpenBSD! > > Thanks a lot for time and cooperation. > > PS: I am not asking which is the best OS (a kind of question that should > never be asked). > I only want to know the good/bad things about both of them, since no > OS is perfect! Gustavo, it probably didn't occur to you that you are more qualified than anyone to answer this question. As you say, no OS is perfect, and OpenBSD has a different focus than FreeBSD, even though the systems remain similar. I would be very interested in hearing what you have to say about the two systems in comparison. Reports of reliability, load handling, etc. will be greatly appreciated. It might even make a great article for Daemon News or SysAdmin magazine. -- "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 Mar 31 17:52:33 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 0D12737B7E3 for ; Fri, 31 Mar 2000 17:52:29 -0800 (PST) (envelope-from imp@harmony.village.org) 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 SAA75947; Fri, 31 Mar 2000 18:52:26 -0700 (MST) (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 SAA39111; Fri, 31 Mar 2000 18:51:55 -0700 (MST) Message-Id: <200004010151.SAA39111@harmony.village.org> To: Wes Peters Subject: Re: Shared /bin and /sbin Cc: Ollivier Robert , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Mar 2000 16:25:32 MST." <38E533EC.30BE0E8B@softweyr.com> References: <38E533EC.30BE0E8B@softweyr.com> <200003300722.AAA21918@harmony.village.org> <20000330212950.A92062@keltia.freenix.fr> Date: Fri, 31 Mar 2000 18:51:55 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38E533EC.30BE0E8B@softweyr.com> Wes Peters writes: : Whatever happened to the idea of putting the shared libs for /bin and : /sbin in /lib? People are afraid that it would mean more disk space used on /, not less. They worry that shared libraries are not robust enough to cope and your system will be completely useless if one file (/lib/libc.so) goes away. They also worry about duplicated disk usage between /usr/lib/libc.so and /lib/libc.so and possible version skew. I personally don't like the idea as default. However, in an embedded enviornment where the flash is read only, with spares on the shelf in case of failure (any failure) it may be an acceptible way to go. It won't save much space (my estimates are in the neighborhood of 3MB), but on a 16M flash, 3M can mean the difference between fitting and not fitting. Before this spirals out of hand, no, I'm not even suggesting that we do this by default. I was just asking if it could be done. So far no one has said no. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 18: 2:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 8E4AD37B880 for ; Fri, 31 Mar 2000 18:02:25 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA75450; Fri, 31 Mar 2000 18:02:14 -0800 (PST) (envelope-from Doug@gorean.org) Date: Fri, 31 Mar 2000 18:02:14 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Chris Costello Cc: Christian Weisgerber , freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files In-Reply-To: <20000331165457.A2556@holly.calldei.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 Fri, 31 Mar 2000, Chris Costello wrote: > On Friday, March 31, 2000, Doug Barton wrote: > > In my mind there is a difference between items that are > > freebsd-exclusive (like set -o and alias) and items that we have unique > > implementations of, like export. The latter are available on other > > platforms, and therefore, IMO we should follow the more generally accepted > > format. Extending that argument to either not take advantage of features > > unique to FreeBSD (silly and wasteful) or to doing everything FreeBSD'ish > > just because we can (teaches a bad lesson) goes too far in either > > direction for my taste. > > ``set -o'', ``alias'', and ``export'' are all portable. A few > options for ``set -o'' may not be, but otherwise they are. Where > did you get the idea that the first two were FreeBSD-exclusive? I guess that's not the best term to use, so let me try and rephrase my argument. All Bourne shells and derivatives have an export command. On all Bourne shells and derivatives, you _can_ do: var=foo export var It is not true however, that on all Bourne shells and derivatives that you can do: export var=foo A simple example is Sun's Bourne shell implementation, in which there is no set -o, there is no emacs mode, and there is no alias ability. There is, however, an export command. Other SysV systems that follow a more strict line of descent from the original Bourne shell are similarly limited. So to restate my point, in hopefully a more clear fashion, for those commands like export which are universal across all Bourne shells (and derivatives); my feeling is that we should use the syntax that will work across all platforms. For those commands that are found in the POSIX-like shells, I agree that using those commands is a good idea (even though they are not 100% portable) and using the most convenient, and/or the most obvious syntax is a good idea. I realize that this may seem contradictory, but my feeling is that if we are going to offer these files as the example implementation that the example they set should be a good one. At the same time, if the majority thinks that using 'export var=foo' is the best way to go, I'll live with it. Either way, I would like to see _something_ done. This is an area that has suffered from neglect for a long time. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 20: 2:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EBFFF37BA73 for ; Fri, 31 Mar 2000 20:02:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA36399; Fri, 31 Mar 2000 20:02:15 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 20:02:15 -0800 (PST) From: Matthew Dillon Message-Id: <200004010402.UAA36399@apollo.backplane.com> To: Warner Losh Cc: Wes Peters , Ollivier Robert , hackers@FreeBSD.ORG Subject: Re: Shared /bin and /sbin References: <38E533EC.30BE0E8B@softweyr.com> <200003300722.AAA21918@harmony.village.org> <20000330212950.A92062@keltia.freenix.fr> <200004010151.SAA39111@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :People are afraid that it would mean more disk space used on /, not :less. They worry that shared libraries are not robust enough to cope :and your system will be completely useless if one file (/lib/libc.so) :goes away. They also worry about duplicated disk usage between :/usr/lib/libc.so and /lib/libc.so and possible version skew. : :I personally don't like the idea as default. However, in an embedded :enviornment where the flash is read only, with spares on the shelf in :case of failure (any failure) it may be an acceptible way to go. It :won't save much space (my estimates are in the neighborhood of 3MB), :but on a 16M flash, 3M can mean the difference between fitting and not :fitting. : :Before this spirals out of hand, no, I'm not even suggesting that we :do this by default. I was just asking if it could be done. So far no :one has said no. : :Warner Linux kernel has a separate /lib and /usr/lib. If you install the linux compatibility port you will see what a huge bloated mess the linux /lib has become. I much prefer the FreeBSD way of doing things. There should be only one lib -- /usr/lib, and things critical to booting should be compiled static. Obviously people with special needs can compile the binaries up however they like, but I don't think we should change the base distribution's way of doing things. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 20:25:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 3A0FA37BA94 for ; Fri, 31 Mar 2000 20:25:13 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id WAA03117; Fri, 31 Mar 2000 22:25:51 -0600 (CST) (envelope-from chris) Date: Fri, 31 Mar 2000 22:25:50 -0600 From: Chris Costello To: Doug Barton Cc: Christian Weisgerber , freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files Message-ID: <20000331222550.B2556@holly.calldei.com> Reply-To: chris@calldei.com References: <20000331165457.A2556@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, March 31, 2000, Doug Barton wrote: > I guess that's not the best term to use, so let me try and > rephrase my argument. All Bourne shells and derivatives have an export > command. On all Bourne shells and derivatives, you _can_ do: > > var=foo > export var > > It is not true however, that on all Bourne shells and derivatives that you > can do: > > export var=foo However, on all _POSIX_ shells, ``export var=foo'' is valid, if I remember correctly. -- |Chris Costello |A closed mouth gathers no feet. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 20:39: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by hub.freebsd.org (Postfix) with ESMTP id A902437BABB for ; Fri, 31 Mar 2000 20:39:03 -0800 (PST) (envelope-from brianm@moffetimages.com) Received: from brianm (mg136-216.ricochet.net [204.179.136.216]) by rgate.ricochet.net (8.9.3/8.9.3) with SMTP id WAA22794; Fri, 31 Mar 2000 22:37:28 -0600 (CST) Message-Id: <3.0.5.32.20000331202005.00838660@orac.moffetimages.com> X-Sender: brianm@orac.moffetimages.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 31 Mar 2000 20:20:05 -0800 To: Warner Losh , ulf@Alameda.net From: "Brian D. Moffet" Subject: Re: Question about PCI vendor 0x127a Cc: Allen Pulsifer , freebsd-hackers@FreeBSD.ORG In-Reply-To: <200003232133.OAA43894@harmony.village.org> References: <20000323132712.H95709@PacHell.TelcoSucks.org> <200003232042.NAA43568@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:33 PM 3/23/00 -0700, Warner Losh wrote: >Yup. The 99.99% of all pci modems are winmodems of some flavor or >another. Yes, I spent a long time finding a PCI non-winmodem for my freeBSD box. Once I plugged in all the correct information, it works just fine, looking like a 16550A to the OS. It was quite a bit more expensive than the winmodems that I was looking at it. 3com/USRobotics. I had to remember (actually looked up) how to read the PCI bios entries to find out how to configure the serial port. No, I didn't use plug and play, it didn't make sense to. Eventually, I'll figure out hot to get it to do fax as well as login :-) when it becomes important... Brian Brian D. Moffet www.moffetimages.com brianm@ricochet.net photographer, pilot, musician, programmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 31 21:30:15 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 A67D337BABC for ; Fri, 31 Mar 2000 21:30:11 -0800 (PST) (envelope-from imp@harmony.village.org) 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 WAA76503; Fri, 31 Mar 2000 22:29:58 -0700 (MST) (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 WAA40432; Fri, 31 Mar 2000 22:29:25 -0700 (MST) Message-Id: <200004010529.WAA40432@harmony.village.org> To: "Brian D. Moffet" Subject: Re: Question about PCI vendor 0x127a Cc: ulf@Alameda.net, Allen Pulsifer , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Mar 2000 20:20:05 PST." <3.0.5.32.20000331202005.00838660@orac.moffetimages.com> References: <3.0.5.32.20000331202005.00838660@orac.moffetimages.com> <20000323132712.H95709@PacHell.TelcoSucks.org> <200003232042.NAA43568@harmony.village.org> Date: Fri, 31 Mar 2000 22:29:25 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3.0.5.32.20000331202005.00838660@orac.moffetimages.com> "Brian D. Moffet" writes: : Yes, I spent a long time finding a PCI non-winmodem for my freeBSD : box. Once I plugged in all the correct information, it works just : fine, looking like a 16550A to the OS. It was quite a bit more : expensive than the winmodems that I was looking at it. : 3com/USRobotics. I had to remember (actually looked up) how to read : the PCI bios entries to find out how to configure the serial port. Now you should be able to just use the sio driver :-) Or shortly, when I get the patches committed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Apr 1 15:44:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id DD68237BC5E; Sat, 1 Apr 2000 15:44:50 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id DAA07016; Sun, 2 Apr 2000 03:49:53 +0400 (MSD) Message-Id: <200004012349.DAA07016@aaz.links.ru> Subject: Re: No route for 127/8 to lo0 (?) - another use for loopback subn et? In-Reply-To: from "Eric Peterson" at "Mar 31, 0 09:08:39 am" To: ericp@troikanetworks.com (Eric Peterson) Date: Sun, 2 Apr 2000 03:49:53 +0400 (MSD) Cc: dot@dotat.at, nik@FreeBSD.ORG, hackers@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 Eric Peterson writes: [Charset iso-8859-1 unsupported, filtering to ASCII...] > Tony Finch [mailto:dot@dotat.at] wrote: > > Nik Clayton wrote: > >> > >> I thought that 127/8 was the "local net", and that > >> packets sent to any of those addresses would go via > >> the loopback interface. That seems to be how Linux > >> and Windows 98 do things (the only systems I can > >> check this on at the moment). Assuming that's the > >> case, why does FreeBSD only add a a host route to > >> 127.0.0.1, and not a network route for 127/8? > > > > I did some further investigation to see how old this > > oddity is and it seems to be the way BSD has always > > handled the loopback interface. There's an explicit > > exclusion in the interface initialization code in in.c > > that gives loopback interfaces a host route instead of > > the network route that a normal interface gets and it's > > been that way for 15 years. > > I always thought it was a great waste of network address > space to devote an entire class A network to a single > loopback address. An idea I got from a co-worker a while > ago was to allow the 127.* (or some smaller subnet of 127) > to be devoted to "intra-box addresses", for example: > > 1. A cluster of devices/slots within a chassis > 2. A parallel processing machine > 3. A multi-processor computer/device > > All of the above may have inter-processor communications > that do not need to leave the chassis. Analogous to how > the 192.168.* (RFC1918) addresses are used for intranets, > these addresses wouldn't be allowed to be seen by the outside > world (i.e. outside the "chassis"), but would permit internal > IP communication without having to waste (and configure) a > "real" IP net number. If these devices needed to get to the > outside world, they could use NAT (again, analogously to the > RFC1918 case). I use addresses from 127/8 net for p2p connections when security is useful. TCP/IP pakets with 127.X.X.X has only one hop to live and never be routed by BSD kernel. may be 0/8 net is similar - I don't remember. -- @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 Sat Apr 1 15:48: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (pachell.telcosucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 383B737B9EC; Sat, 1 Apr 2000 15:47:52 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id PAA87155; Sat, 1 Apr 2000 15:47:24 -0800 (PST) (envelope-from ulf) Date: Sat, 1 Apr 2000 15:47:24 -0800 From: Ulf Zimmermann To: "Aleksandr A.Babaylov" Cc: Eric Peterson , dot@dotat.at, nik@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: No route for 127/8 to lo0 (?) - another use for loopback subn et? Message-ID: <20000401154724.P95709@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: <200004012349.DAA07016@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200004012349.DAA07016@aaz.links.ru>; from babolo@links.ru on Sun, Apr 02, 2000 at 03:49:53AM +0400 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 03:49:53AM +0400, Aleksandr A.Babaylov wrote: > Eric Peterson writes: > [Charset iso-8859-1 unsupported, filtering to ASCII...] > > Tony Finch [mailto:dot@dotat.at] wrote: > > > Nik Clayton wrote: > > >> > > >> I thought that 127/8 was the "local net", and that > > >> packets sent to any of those addresses would go via > > >> the loopback interface. That seems to be how Linux > > >> and Windows 98 do things (the only systems I can > > >> check this on at the moment). Assuming that's the > > >> case, why does FreeBSD only add a a host route to > > >> 127.0.0.1, and not a network route for 127/8? > > > > > > I did some further investigation to see how old this > > > oddity is and it seems to be the way BSD has always > > > handled the loopback interface. There's an explicit > > > exclusion in the interface initialization code in in.c > > > that gives loopback interfaces a host route instead of > > > the network route that a normal interface gets and it's > > > been that way for 15 years. > > > > I always thought it was a great waste of network address > > space to devote an entire class A network to a single > > loopback address. An idea I got from a co-worker a while > > ago was to allow the 127.* (or some smaller subnet of 127) > > to be devoted to "intra-box addresses", for example: > > > > 1. A cluster of devices/slots within a chassis > > 2. A parallel processing machine > > 3. A multi-processor computer/device This is how Cisco is using it on their Catalyst switches for example. > > > > All of the above may have inter-processor communications > > that do not need to leave the chassis. Analogous to how > > the 192.168.* (RFC1918) addresses are used for intranets, > > these addresses wouldn't be allowed to be seen by the outside > > world (i.e. outside the "chassis"), but would permit internal > > IP communication without having to waste (and configure) a > > "real" IP net number. If these devices needed to get to the > > outside world, they could use NAT (again, analogously to the > > RFC1918 case). > I use addresses from 127/8 net for p2p connections > when security is useful. > TCP/IP pakets with 127.X.X.X has only one hop to live > and never be routed by BSD kernel. > may be 0/8 net is similar - I don't remember. > > -- > @BABOLO http://links.ru/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Apr 1 19:14:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.checkpoint.com (kinata.checkpoint.com [199.203.156.41]) by hub.freebsd.org (Postfix) with ESMTP id 0D7D737BB86; Sat, 1 Apr 2000 19:14:36 -0800 (PST) (envelope-from mellon@pobox.com) Received: (from mellon@localhost) by happy.checkpoint.com (8.9.3/8.9.3) id FAA54116; Sun, 2 Apr 2000 05:16:00 GMT (envelope-from mellon@pobox.com) Date: Sun, 2 Apr 2000 05:16:00 +0000 From: Anatoly Vorobey To: hackers@freebsd.org Cc: yokota@freebsd.org, peter@freebsd.org Subject: Re: Unicode on FreeBSD Message-ID: <20000402051559.A52041@happy.checkpoint.com> References: <20000320194702.11223.qmail@web3101.mail.yahoo.com> <8bitar$2i4f$1@bigeye.rhein-neckar.de> <20000329033908.A14122@happy.checkpoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000329033908.A14122@happy.checkpoint.com>; from mellon@pobox.com on Wed, Mar 29, 2000 at 03:39:08AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 03:39:08AM +0000, Anatoly Vorobey wrote: > I wonder how useful it would be to teach syscons/kbd to handle Unicode. No replies so far; let me try again. I was not trying to convey the attitude "let it be done" in my message; I was rather hoping for a reply of a "this would be a nice thing to have; if you do it, I'll review it and if works right, I'll commit it" kind. I believe that what I am suggesting is a Good Thing, but if this belief is not shared by others, there's not much sense in me trying to do it. Thus I suggest teaching kbd/syscons/vga to use Unicode internally. The picture would look as follows. A keymap specifies Unicode values (rather than 8-bit values as now) for keycodes; the console driver receives Unicode values from the keyboard driver. On the video side, the console driver has a bunch of Unicode characters (rather than 8-bit characters) to render; in text mode, it translates them into 8-bit codes and puts them on the screen, the correct font having been previously loaded; in raster mode, it uses the current font to draw them out directly on the screen. The benefits, rather considerable I think, are as follows: - keymaps for different languages don't need to depend on encodings as they do now (most of the languages currently have 2 and more different encodings schemes arranged for in /usr/share/syscons/keymaps ; if Unicode values are specified in keymaps, they all go away and only different key layouts will require separate keymap files); in fact, kbdcontrol(1) can then be written to be aware of the symbolic Unicode names which then would be used in keymap files, simplifying them greatly. - screen fonts as well don't need to depend on encodings - they will map Unicode symbols into screen shapes. The redundant screen font files go away. - in raster modes (SC_PIXEL_MODE on, etc.) more than 256 characters can now be trivially drawn. In fact, different languages that prevously occupied the same codespace in 8-bit (i.e. all languages except English) can now be displayed together in these modes. Maybe there are consequences for scripts such as hiragana etc.? Consider the convenience for users of scripts with relatively many characters. - /usr/share/syscons/scrnmaps goes away, this kludge being no longer needed. - the road is wide open for Unicode support in userland, through UTF-8. The drawbacks, as I see them, are as follows: - The format of screen font files must be changed. They may not be describing consecutive character codes anymore, and 8-bit indexed arrays go away. One font file may now describe lots of languages at once. - much more kernel memory used for font files if they are unified as above and used as a whole. Some mechanism may be used for telling kbdcontrol(1) and friends which subset of the font to load (doing this strictly by user's LANG won't let him use several languages at once though). In text modes, a mapping must be created to squeeze Unicode into the available 8-bit VGA font space, and if there isn't enough space, someone must decide which Unicode chars to let go and convert into blanks -- syscons is the module which will be doing this job, and userland may tell it what the really important Unicode chars are based on the user's LANG. - some rendering routines are slowed down due to the fact that simple 8-bit array lookups are no longer available for getting characters' information. This may be circumvented somewhat by smart searches/hash tables. Implementation considerations: - may be done in stages, which is good. For instance, keyboard driver together with kbdcontrol(1) and keymap files may be modified at first, with syscons translating Unicode codes into 8-bit using a translation table conveyed to it by kbdcontrol(1) and handling video exactly as before. Later video routines are changed, etc. - kbd driver changes aren't significant in the kernel, mainly type changes and the like (who else except syscons/pcvt is using the kbd driver?). - in syscons, virtual buffer stuff, font support, and the VGA renderer need to be significantly changed. - in userland, data files in /usr/share/syscons need to be changed, kbdcontrol(1) and vidcontrol(1) need to adapt to that, and a method for relaying to syscons the current Unicode<->8bit translation table (so that userland programs won't feel anything) needs to be added. The other alternative is to do that conversion in userland libraries and make syscons completely Unicode. What do you think? -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Apr 1 21: 2:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 6FF5D37BD11; Sat, 1 Apr 2000 21:02:13 -0800 (PST) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (uucp@localhost) by posgate.acis.com.au (8.9.3/8.9.3) with UUCP id PAA17375; Sun, 2 Apr 2000 15:01:58 +1000 Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245]) by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id NAA06549; Sun, 2 Apr 2000 13:55:25 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Sun, 2 Apr 2000 13:52:12 +1000 (EST) From: Andrew MacIntyre To: Jeremiah Gowdy Cc: freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD In-Reply-To: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Message-ID: X-X-Sender: andymac@bullseye.apana.org.au 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, 31 Mar 2000, Jeremiah Gowdy wrote: > Does anyone have any experiance or information about using HP JetDirect 500X > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > information greatly appriciated. These things have an LPD server built in IIRC, so your could just configure them as a remote LPD printer in /etc/printcap. However, I've not been totally satisfied with some of HP's earlier attempts at LPD support in JetDirect cards for their lasers printers, as they weren't particularly reliable, particularly when multiple jobs were queued simultaneously. I hope their more recent stuff is better behaved. You might want to check out LprNg or CUPS to see whether they support the native HP protocol (on port 9100???) if your box doesn't seem to cope, so that one box can be the "print server" and thus serialize all the jobs. We do this at work, although in that case NT is providing the "print server" function. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 andymac@pcug.org.au (play2) | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Apr 1 21:53:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3B59937B6B6; Sat, 1 Apr 2000 21:53:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA19677; Sat, 1 Apr 2000 22:52:42 -0700 (MST) (envelope-from ken) Date: Sat, 1 Apr 2000 22:52:42 -0700 From: "Kenneth D. Merry" To: Andrew MacIntyre Cc: Jeremiah Gowdy , freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD Message-ID: <20000401225242.A19443@panzer.kdm.org> References: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andymac@bullseye.apana.org.au on Sun, Apr 02, 2000 at 01:52:12PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 13:52:12 +1000, Andrew MacIntyre wrote: > On Fri, 31 Mar 2000, Jeremiah Gowdy wrote: > > > Does anyone have any experiance or information about using HP JetDirect 500X > > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > > information greatly appriciated. > > These things have an LPD server built in IIRC, so your could just > configure them as a remote LPD printer in /etc/printcap. > > However, I've not been totally satisfied with some of HP's earlier > attempts at LPD support in JetDirect cards for their lasers printers, as > they weren't particularly reliable, particularly when multiple jobs were > queued simultaneously. I hope their more recent stuff is better behaved. > > You might want to check out LprNg or CUPS to see whether they support the > native HP protocol (on port 9100???) if your box doesn't seem to cope, so > that one box can be the "print server" and thus serialize all the jobs. > We do this at work, although in that case NT is providing the "print > server" function. You can setup the stock FreeBSD lpd to talk the native HP printer protocol to a HP printer with a Jet Direct card. I've got the following setup on a -current box that talks to my HP LaserJet 4000 (hostname is "printer"): in /etc/printcap: lp|ps:\ :mx#0:lp=9100@printer:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh:\ :if=/usr/local/lib/filters/inputshell:\ :of=/usr/local/lib/filters/ofhp: /usr/local/lib/filters/inputshell is just this: #!/bin/sh /usr/local/lib/filters/ifhp -Ttbcp=on,model=5M exit 0 The ifhp/ofhp comes in the ifhp port, which is ports/print/ifhp. The above setup works well with either text files or postscript. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message