From owner-freebsd-hackers Sun Nov 22 00:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14319 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 00:05:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aniwa.sky (p37-max6.wlg.ihug.co.nz [209.78.48.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14297; Sun, 22 Nov 1998 00:05:29 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from localhost (andrew@localhost) by aniwa.sky (8.8.8/8.8.7) with ESMTP id VAA13024; Sun, 22 Nov 1998 21:03:34 +1300 (NZDT) (envelope-from andrew@squiz.co.nz) Date: Sun, 22 Nov 1998 21:03:34 +1300 (NZDT) From: Andrew McNaughton X-Sender: andrew@aniwa.sky Reply-To: andrew@squiz.co.nz To: Don Lewis cc: Robert Watson , Mikael Karpberg , William McVey , hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Would this make FreeBSD more secure? In-Reply-To: <199811220606.WAA00417@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Nov 1998, Don Lewis wrote: > On Nov 17, 5:02pm, Robert Watson wrote: > } Subject: Re: Would this make FreeBSD more secure? > > } It might be nice to just have a file system socket any process can bind to > } that mediates access to the authentication system. On the one side of the > } socket is any client attempting to authenticate a user (possibly using PAM > } as the API, and then some record based protocol over the socket), and on > } the other side is Mr Auth Server that listens on the socket, accepts > } connections, and is a place where throttling of attempts could be > } performed. Similarly, it could take advantage of the SCM_AUTH (or > } whatever) uid/gid passing to authenticate the processes on the other side. > > I think this is the best solution. Unless the process is setuid root (su), > if the auth server sees that billybob is trying to validate a password, > then the auth server should only validate billybob's password. This > prevents billybob from trying to use the auth server to crack passwords, but > it allows billybob to install and use his own private screen or terminal > locker. If the server puts in a few seconds of delay for authentication of a particular user after a failed attempt, (optionally increasing with number of recent failures) then that's going to be enough to make brute force infeasible. Are there any situations where it might be desirable not to run a process as root, but where that process should be able to authorize users using the main pw table? I wonder if the auth server shouldn't be dealing with more than just the username and password. Perhaps it should also be passed enough details to implement restrictions based on which service is being requested and the location the request is coming from. This would facilitate a centralized access policy. Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 01:07:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18546 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 01:07:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18528; Sun, 22 Nov 1998 01:07:22 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from client201-122-2.bellatlantic.net (client201-122-2.bellatlantic.net [151.201.122.2]) by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id EAA06002; Sun, 22 Nov 1998 04:05:23 -0500 (EST) Date: Sun, 22 Nov 1998 04:04:15 +0000 (GMT) From: Donn Miller X-Sender: dmm125@localhost To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Distortion/RealPlayer 5.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, has anyone solved the problem of distortion and bad video playback on FreeBSD-current? Video frames won't play back smooth, sound is distorted/raspy. Maybe some sys/IO calls aren't being made correctly? Also, while I'm at it, can anyone tell me if using cvsup with default release=cvs will be the same as running -current? Thanks Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 02:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24902 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 02:53:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24897 for ; Sun, 22 Nov 1998 02:53:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA08874; Sun, 22 Nov 1998 02:52:40 -0800 (PST) (envelope-from obrien) Message-ID: <19981122025240.A8758@nuxi.com> Date: Sun, 22 Nov 1998 02:52:40 -0800 From: "David O'Brien" To: Joel Ray Holveck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Password generator Reply-To: obrien@NUXI.com References: <86n25mdn2q.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <86n25mdn2q.fsf@detlev.UUCP>; from Joel Ray Holveck on Fri, Nov 20, 1998 at 04:19:24PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > passwd+ (ftp://ftp.dartmouth.edu/pub/security/) is also frequently > recommended. Actually the latest is at ftp://nob.cs.ucdavis.edu/pub/sec-tools/ as the author has moved from Dartmouth to UC-Davis many years ago. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 03:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26783 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 03:07:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26778 for ; Sun, 22 Nov 1998 03:07:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id DAA09074; Sun, 22 Nov 1998 03:05:40 -0800 (PST) (envelope-from obrien) Message-ID: <19981122030540.B8758@nuxi.com> Date: Sun, 22 Nov 1998 03:05:40 -0800 From: "David O'Brien" To: Robert Withrow , hackers@FreeBSD.ORG Subject: Re: AMD/NFS problems with 3.0 Reply-To: obrien@NUXI.com References: <199811182229.RAA25694@tuva.engeast.baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811182229.RAA25694@tuva.engeast.baynetworks.com>; from Robert Withrow on Wed, Nov 18, 1998 at 05:29:07PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At first I though this might be related to these messages that went > to the log the first time I started amd: > > noconn option exists, and was turned OFF! (May cause NFS hangs > on some systems...) These are always printed out. I guess I should comment them out, or determine if we really can use the optimization. The comments in the code by the Columbia people are often out of date with respect to FreeBSD-CURRENT. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 03:12:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27912 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 03:12:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27905 for ; Sun, 22 Nov 1998 03:12:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id DAA09164; Sun, 22 Nov 1998 03:11:27 -0800 (PST) (envelope-from obrien) Message-ID: <19981122031126.C8758@nuxi.com> Date: Sun, 22 Nov 1998 03:11:26 -0800 From: "David O'Brien" To: Robert Withrow , Robert Withrow Cc: hackers@FreeBSD.ORG Subject: Re: AMD/NFS problems with 3.0 Reply-To: obrien@NUXI.com References: <199811182229.RAA25694@tuva.engeast.baynetworks.com> <199811201503.KAA25644@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811201503.KAA25644@spooky.rwwa.com>; from Robert Withrow on Fri, Nov 20, 1998 at 10:03:59AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All of my *AMD* problems were cured by upgrading to the latest > version: am-utils-6.0b2s3. Sounds really good to me. I may wait a little bit to see if the Columbia people move that version out of the `snapshots' directory. I would be very interested to hear if others find that am-utils-6.0b2s3 at ftp://shekel.mcl.cs.columbia.edu//pub/am-utils/ does better for them than am-utils-6.0b1. > I'd like to suggest that 2.2.8 and 3.next upgrade to, at least, the 6.0 > beta stream instead of the alpha code that is in there now. Amd will not be updated in 2.2.8 as it is too big a change for the 2.2.x branch at this point. 3.0 went to the beta code Nov 14th. But I did forget to change the version number that is printed out until just recently. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 04:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06023 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 04:31:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06015 for ; Sun, 22 Nov 1998 04:30:58 -0800 (PST) (envelope-from dmlb@ragnet.demon.co.uk) Received: from [158.152.46.40] (helo=ragnet.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.053 #1) id 0zhYem-0006zt-00; Sun, 22 Nov 1998 12:30:25 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0zhXZ3-0001En-00; Sun, 22 Nov 1998 11:20:25 +0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811220148.UAA01381@spoon.beta.com> Date: Sun, 22 Nov 1998 11:20:25 -0000 (GMT) From: Duncan Barclay To: "Brian J. McGovern" Subject: RE: PortalFS Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Nov-98 Brian J. McGovern wrote: > I'd be very interested in PortalFS. Problem is, I'm not an FS guru yet :) > As a matter of fact, I don't think I've ever gotten PortalFS working quite > right (maybe you could point out what I'm doing wrong...). > > I take the portal config file from the mount_portal man page, stick it > in /etc under portal.conf. > > Then, I run mount_portal /etc/portal.conf /p > > The mount command blocks, but then if I: > > int x; > x = open("/p/tcp/localhost/telnet",O_RDWR); > > x comes back as -1, with errno set (you'll have to excuse me, its been > a long time since I tinkered). > > However, as an end result, if you've got more portalfs tid-bits, and I can > actually get the code working, I'd very much enjoy playing with it. > -Brian I've checked my routines against 2.2.6 and current. Apart from some minor Lite2 stuff everything hasn't changed. The 2.x versions are all falling over sending the file descriptor back to the kernel via a socket using sendmsg(2). I get Nov 22 11:07:54 computer portald[4459]: send: Invalid argument in /var/log/messages I will try and fix this today. I have also written a tcplisten type which I submit too. In the portal tcp code, sbin/mount_portal/pt_tcp.c, one can get a socket to a reserved port by doing fd = open("/p/tcp/localhost/daytime/priv", O_RD); In pt_tcp.c if a reserved port is asked for it does so = rresvport(...) otherwise so = socket(...) is used. My understanding of the use of the tcp portal is to open a connection to a service already listening, so you don't need to use rresvport. Is this a big hole? I have also thrown away root privs around the connect. diff -wur pt_tcp.c ncvs/c* @@ -126,6 +144,9 @@ while (ipp[0]) { int so; + if (priv) + so = rresvport((int *) 0); + else so = socket(AF_INET, SOCK_STREAM, 0); if (so < 0) { syslog(LOG_ERR, "socket: %m"); @@ -133,13 +154,10 @@ } sain.sin_addr = *ipp[0]; - setuid (pcr->pcr_uid); if (connect(so, (struct sockaddr *) &sain, sizeof(sain)) == 0) { - setuid (geteuid ()); /* XXX getuid? */ *fdp = so; return (0); } - setuid (geteuid ()); /* XXX getuid? */ (void) close(so); (+ is from current, - my code) Which is right? Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 05:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07669 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 05:15:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07655; Sun, 22 Nov 1998 05:15:08 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id OAA01918; Sun, 22 Nov 1998 14:14:28 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id MAA00601; Sun, 22 Nov 1998 12:03:24 GMT Message-ID: <19981122120323.61496@breizh.prism.uvsq.fr> Date: Sun, 22 Nov 1998 12:03:23 +0000 From: Nicolas Souchu To: Randy Bunchun Lim Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: attach OKIDATA office44 to FreeBSD on PC? References: <3650891D.41C67EA6@aht.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3650891D.41C67EA6@aht.com>; from Randy Bunchun Lim on Mon, Nov 16, 1998 at 12:20:45PM -0800 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 16, 1998 at 12:20:45PM -0800, Randy Bunchun Lim wrote: > >Hi, > > I tried to send print jobs to OKIDATA office44 through parallel port >but only to fail. Later on I figured out that this printer was a > multifunction machine(supporting fax, scanning, and printing) so I >could NOT send print jobs to printer using lpr to parallel port >directly. There is a MFPI(Multi Function Peripheral Interface) driver >between the Host and the MFP. Also the MFPI driver communicate to MFP >using Bi-Centro I/F. But the current MFPI driver only support Window >95. There was NO Unix MFPI driver so far. I plan to implement MFPI >driver on FreeBSD. And I need the following helps: Great! You'll appreciate the Linux work about this I think. But this is GPLed :( The best would be to rewrite it. I've already tried to understand there work and think about a common project, but without the hardware... > >1, How did MFPI driver read/write the parallel port before lpr can >start the burst data transfer? You'll certainly find such info at the Linux parport project's home page (see below) > >2, where can I find more information about parallel port driver? man ppbus on -current Here are few urls relating to parallel port: http://www.lvr.com/parport.htm http://www.lpt.com/pti.htm There's a Linux project for the HP OfficeJet devices, see the following links: http://www.torque.net/parport.html http://www.ifs.physik.uni-stuttgart.de/Personal/RSchreiter/hpoj/ > > Also I would like to ask if anybody had any experiences before to >attach such printers to FreeBSD? > > Your quick response will be appreiated Sorry :) > > /Randy > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sun Nov 22 06:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12194 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 06:26:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12189 for ; Sun, 22 Nov 1998 06:26:12 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id HAA08388; Sun, 22 Nov 1998 07:25:39 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id HAA21510; Sun, 22 Nov 1998 07:25:38 -0700 Date: Sun, 22 Nov 1998 07:25:38 -0700 Message-Id: <199811221425.HAA21510@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: leisner@rochester.rr.com Cc: Nate Williams , hackers@FreeBSD.ORG Subject: Re: Wrapping a function In-Reply-To: <199811220702.CAA01604@rochester.rr.com> References: <199811170517.WAA22627@mt.sri.com> <199811220702.CAA01604@rochester.rr.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In recent gnu ld's: > `--wrap SYMBOL' > Use a wrapper function for SYMBOL. Any undefined reference to > SYMBOL will be resolved to `__wrap_SYMBOL'. Any undefined > reference to `__real_SYMBOL' will be resolved to SYMBOL. Cool! Does our ld do this? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 06:59:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13815 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 06:59:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13810 for ; Sun, 22 Nov 1998 06:59:14 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id JAA29218 for ; Sun, 22 Nov 1998 09:58:36 -0500 (EST) Date: Sun, 22 Nov 1998 09:58:36 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: How to time system calls? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a question on how to record the time it takes to execute a system call. I have heard of something like profile and trace. Could any one give me some hints and, preferebly, point out where is the source code I can insert statements to time a system call? Thanks for any help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 08:05:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18355 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 08:05:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18348 for ; Sun, 22 Nov 1998 08:05:04 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id KAA09470 for ; Sun, 22 Nov 1998 10:04:31 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma009468; Sun, 22 Nov 98 10:04:21 -0600 Received: (from nectar@localhost) by spawn.nectar.com (8.9.1/8.9.1) id KAA05384 for hackers@FreeBSD.org; Sun, 22 Nov 1998 10:04:21 -0600 (CST) (envelope-from nectar) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE Date: Sun, 22 Nov 1998 10:04:21 -0600 (CST) From: nectar@FreeBSD.ORG To: hackers@FreeBSD.ORG Subject: errno Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following code snippet won't compile on -CURRENT, or on -STABLE with _THREAD_SAFE defined due to ``errno'' being a macro in : #include struct example { int errno; }; I understand why, but is this code incorrect ANSI C? I'm just trying to find a reference that prohibits this use. Thanks, Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 09:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22100 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 09:06:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22083; Sun, 22 Nov 1998 09:06:35 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA08261; Sun, 22 Nov 1998 12:05:16 -0500 (EST) Date: Sun, 22 Nov 1998 12:05:15 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Andrew McNaughton cc: Don Lewis , Mikael Karpberg , William McVey , hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Would this make FreeBSD more secure? 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 Sun, 22 Nov 1998, Andrew McNaughton wrote: > On Sat, 21 Nov 1998, Don Lewis wrote: > > > On Nov 17, 5:02pm, Robert Watson wrote: > > } Subject: Re: Would this make FreeBSD more secure? > > > > } It might be nice to just have a file system socket any process can bind to > > } that mediates access to the authentication system. On the one side of the > > } socket is any client attempting to authenticate a user (possibly using PAM > > } as the API, and then some record based protocol over the socket), and on > > } the other side is Mr Auth Server that listens on the socket, accepts > > } connections, and is a place where throttling of attempts could be > > } performed. Similarly, it could take advantage of the SCM_AUTH (or > > } whatever) uid/gid passing to authenticate the processes on the other side. > > > > I think this is the best solution. Unless the process is setuid root (su), > > if the auth server sees that billybob is trying to validate a password, > > then the auth server should only validate billybob's password. This > > prevents billybob from trying to use the auth server to crack passwords, but > > it allows billybob to install and use his own private screen or terminal > > locker. > > If the server puts in a few seconds of delay for authentication of a > particular user after a failed attempt, (optionally increasing with number > of recent failures) then that's going to be enough to make brute force > infeasible. Are there any situations where it might be desirable not to > run a process as root, but where that process should be able to authorize > users using the main pw table? > > I wonder if the auth server shouldn't be dealing with more than just the > username and password. Perhaps it should also be passed enough details to > implement restrictions based on which service is being requested and the > location the request is coming from. This would facilitate a centralized > access policy. My feeling was that this could actually be extremely general purpose protocol spoken on the wire, and that it could be used in a number of situations. For example, the server could accept kerberosIV or V authenticators to check against the local rcmd for authentication. It would probably not, however, return the shared secret, as that would allow unpriveledged users to retrieve secrets from sniffed sessions. I think a PAM like functionality is best. An example of a daemon that could use this behavior is the CMU Cyrus server -- they already have a rudimentary password checker of this form (ungeneralized) so that their imap/pop servers can be spawned by inetd as the cyrus user. This way, holes in their IMAP code do not yield root access. Also, this mechanism could be used to submit password changes without a setuid binary -- the daemon, by virtue of ancillary data passing, could be aware of the remote uid, and accept an old, plus a new password, with similar delays instituted for incorrect old passwords. I started writing code to do this based on my 'kernel tokens' work -- essentially, I had a priviledged daemon acting as a token manager. Other processes, using a file system socket, could submit existing tokens and request new tokens based on them. So a kerberos ticket in a token could be used to retrieve local UID and GID tokens. When login ran, it would receive some sort or authenticating data, generate a token, send it to the tokend, and then receive back tokens authorizing it for local access to files, etc. I only partially completed the implementation (enough to allow normal users with UID/GID tokens to retrieve authorization tokens for a few specific capabilities, such as port binding), but no doubt a subset of this behavior could used without tokens. What would make people like Terry (and myself) really happy would be to make this a 'session manager' storing session keys, etc. This requires some kind of kernel integration to be useful, and that was the aspect I hoped to acquire using my token behavior. This way, samba code running in the kernel, or pseudo-user-land code such as Coda could speak to a single session manager to retrieve keys, and ask for the prompting of new keys for the user, if an interactive user was available. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 09:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24099 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 09:29:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-58-dbn.dial-up.net [196.34.155.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24077; Sun, 22 Nov 1998 09:29:03 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA07219; Sun, 22 Nov 1998 19:27:27 +0200 (SAT) From: Robert Nordier Message-Id: <199811221727.TAA07219@ceia.nordier.com> Subject: Re: errno In-Reply-To: from "nectar@FreeBSD.ORG" at "Nov 22, 98 10:04:21 am" To: nectar@FreeBSD.ORG Date: Sun, 22 Nov 1998 19:27:25 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nectar@FreeBSD.ORG wrote: > The following code snippet won't compile on -CURRENT, or on -STABLE with > _THREAD_SAFE defined due to ``errno'' being a macro in : > > #include > struct example { > int errno; > }; > > I understand why, but is this code incorrect ANSI C? I'm just > trying to find a reference that prohibits this use. 7.1.4: .... It is unspecified whether errno is a macro or an identifier declared with external linkage. If a macro definition is suppressed in order to access an actual object, or a program defines an identifier with the name errno, the behavior is undefined. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 09:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25886 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 09:45:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25870 for ; Sun, 22 Nov 1998 09:45:11 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA08408; Sun, 22 Nov 1998 12:44:35 -0500 (EST) Date: Sun, 22 Nov 1998 12:44:35 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Thierry Besancon cc: besancon@lps.ens.fr, hackers@FreeBSD.ORG Subject: Re: Mounting MFS without a swap partition In-Reply-To: <199811221739.RAA10904@excalibur.lps.ens.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 On Sun, 22 Nov 1998, Thierry Besancon wrote: > About 2 months ago, you asked in questions@FreeBSD.ORG how to mount a MFS > partition without any swap. > I'm in the same configuration. > > Did you get any answer ? The thread in empty how your question... > > Thanks for any piece of information. Thierry, Unfortunately I never did receive a response about that. I'm CC'ing this message to -hackers in the hopes of a suggestion. Essentially, the problem is as follows -- mount_mfs appears to require a device that it can associate itself with; this is normally the name of the swap device used. However, if you use vnconfig and a swap file, you do not have a swap file exactly; or at least, you do, but apparently mount_mfs does not like vn0b. Does anyone have any suggestions as to how to go about doing this when using only swap files on a machine? Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 10:05:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27019 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 10:05:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (29-sweet.camalott.com [208.239.153.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27014 for ; Sun, 22 Nov 1998 10:05:05 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id MAA09374; Sun, 22 Nov 1998 12:04:24 -0600 (CST) (envelope-from joelh) To: freebsd-hackers@FreeBSD.ORG Subject: cd size probes From: Joel Ray Holveck Date: 22 Nov 1998 12:04:21 -0600 Message-ID: <86zp9job8a.fsf@detlev.UUCP> Lines: 12 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a reason to probe cd's for size at bootup? It is personally annoying to me, and doesn't seem to serve any purpose from what I can see. I'd like to dike that out. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 10:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27802 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 10:13:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (29-sweet.camalott.com [208.239.153.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27627; Sun, 22 Nov 1998 10:13:09 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id MAA13668; Sun, 22 Nov 1998 12:12:29 -0600 (CST) (envelope-from joelh) To: nectar@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: errno References: From: Joel Ray Holveck Date: 22 Nov 1998 12:12:25 -0600 In-Reply-To: nectar@FreeBSD.ORG's message of "Sun, 22 Nov 1998 10:04:21 -0600 (CST)" Message-ID: <86yap3oauu.fsf@detlev.UUCP> Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following code snippet won't compile on -CURRENT, or on -STABLE with > _THREAD_SAFE defined due to ``errno'' being a macro in : > #include > struct example { > int errno; > }; > I understand why, but is this code incorrect ANSI C? I'm just > trying to find a reference that prohibits this use. This may be better in comp.lang.c. The way I understand it, errno is explicitly allowed to be defined as a macro evaluating to a modifiable lvalue. I don't have a C standard handy, but I'm nearly (95%) certain that the ISO standard allows our macro. I don't know about ANSI, but it is usually the same. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 10:44:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01082 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 10:44:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01075 for ; Sun, 22 Nov 1998 10:44:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA29870; Sun, 22 Nov 1998 10:43:52 -0800 (PST) (envelope-from dillon) Date: Sun, 22 Nov 1998 10:43:52 -0800 (PST) From: Matthew Dillon Message-Id: <199811221843.KAA29870@apollo.backplane.com> To: Robert Watson Cc: Thierry Besancon , besancon@lps.ens.fr, hackers@FreeBSD.ORG Subject: Re: Mounting MFS without a swap partition References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can run mount_mfs using a file for backing store. The 'device' specification is virtually irrelevant, it is simply used by mfs_mount to get default filesystem parameters I believe. It need not be swap. While it is possible to mount MFS with unbacked storage (i.e. when the system has no swap), I wouldn't recommend it. The memory space is still used up even if you rm files out of the MFS partition. If you *do* do this, make the MFS volume as small as possible. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) :On Sun, 22 Nov 1998, Thierry Besancon wrote: : :> About 2 months ago, you asked in questions@FreeBSD.ORG how to mount a MFS :> partition without any swap. :> I'm in the same configuration. :> :> Did you get any answer ? The thread in empty how your question... :> :> Thanks for any piece of information. : :Thierry, : :Unfortunately I never did receive a response about that. I'm CC'ing this :message to -hackers in the hopes of a suggestion. : :Essentially, the problem is as follows -- mount_mfs appears to require a :device that it can associate itself with; this is normally the name of the :swap device used. However, if you use vnconfig and a swap file, you do :not have a swap file exactly; or at least, you do, but apparently :mount_mfs does not like vn0b. Does anyone have any suggestions as to how :to go about doing this when using only swap files on a machine? : : Robert N Watson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 10:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01603 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 10:53:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01598; Sun, 22 Nov 1998 10:53:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA29962; Sun, 22 Nov 1998 10:52:02 -0800 (PST) (envelope-from dillon) Date: Sun, 22 Nov 1998 10:52:02 -0800 (PST) From: Matthew Dillon Message-Id: <199811221852.KAA29962@apollo.backplane.com> To: Donn Miller Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Distortion/RealPlayer 5.0 References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, has anyone solved the problem of distortion and bad video playback on :FreeBSD-current? Video frames won't play back smooth, sound is :distorted/raspy. Maybe some sys/IO calls aren't being made correctly? : :Also, while I'm at it, can anyone tell me if using cvsup with default :release=cvs will be the same as running -current? : :Thanks : :Donn Go into preferences and find the 8 bit audio option. It's somewhere in there. The problem is probably that you have an 8 bit sound card. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 12:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08226 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 12:10:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08218 for ; Sun, 22 Nov 1998 12:10:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA00438 for ; Sun, 22 Nov 1998 12:10:25 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811222010.MAA00438@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: ftp.freebsd.org and slow downloads... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 12:10:25 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG {hasty} traceroute ftp.freebsd.org traceroute to wcarchive.cdrom.com (209.155.82.18), 30 hops max, 40 byte packets 1 flow (209.249.129.137) 0.759 ms 0.730 ms 0.653 ms 2 test (209.249.128.141) 7.955 ms 7.740 ms 7.713 ms 3 main2-133-3.sjc.above.net (209.133.3.3) 9.962 ms 8.516 ms 8.564 ms 4 core2-main2.sjc.above.net (207.126.96.137) 11.331 ms 12.017 ms 10.338 ms 5 ames-core2-ds3.sjc.above.net (207.126.96.194) 10.107 ms 12.956 ms 10.753 ms 6 mae-west1.US.CRL.NET (198.32.136.10) 12.103 ms 13.555 ms 11.557 ms 7 sfo-ames.2.T3.us.crl.net (165.113.50.93) 12.703 ms 12.761 ms 14.210 ms 8 wcarchive.cdrom.com (209.155.82.18) 14.997 ms 16.911 ms 20.400 ms I am getting fairly decent packet response time from ftp.freebsd.org however whenever I tried to download something it takes a very long time and very frequently drops my ftp connection. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 12:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08772 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 12:17:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08767; Sun, 22 Nov 1998 12:17:13 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zhfw0-0006dr-00; Sun, 22 Nov 1998 13:16:40 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA26560; Sun, 22 Nov 1998 13:16:34 -0700 (MST) Message-Id: <199811222016.NAA26560@harmony.village.org> To: nectar@FreeBSD.ORG Subject: Re: errno Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Nov 1998 10:04:21 CST." References: Date: Sun, 22 Nov 1998 13:16:34 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message nectar@FreeBSD.ORG writes: : #include : struct example { : int errno; : }; : I understand why, but is this code incorrect ANSI C? I'm just : trying to find a reference that prohibits this use. No. ANSI C specifically allows errno to be a macro. Since it could be a macro, a strictly conforming compiler need not accept this program. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 12:25:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09450 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 12:25:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from furrball.dyn.ml.org (hou2-09.flex.net [207.18.136.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09438 for ; Sun, 22 Nov 1998 12:25:00 -0800 (PST) (envelope-from chris@furrball.dyn.ml.org) Received: (from chris@localhost) by furrball.dyn.ml.org (8.9.1a/8.8.8) id OAA02232; Sun, 22 Nov 1998 14:21:29 -0600 (CST) (envelope-from chris) Date: Sun, 22 Nov 1998 14:21:29 -0600 (CST) From: Chris Costello Message-Id: <199811222021.OAA02232@furrball.dyn.ml.org> To: hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: ftp.freebsd.org and slow downloads... Reply-To: phoenix@calldei.com In-Reply-To: <199811222010.MAA00438@rah.star-gate.com> X-Mailer: mail(1) -- the One True(TM) mail client Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To: hackers@FreeBSD.ORG > Subject: ftp.freebsd.org and slow downloads... > Date: Sun, 22 Nov 1998 12:10:25 -0800 > From: Amancio Hasty > > I am getting fairly decent packet response time from ftp.freebsd.org however > whenever I tried to download something it takes a very long time and very > frequently drops my ftp connection. Server's constantly busy. It's the world's busiest FTP archive. Try a mirror nearby. > > Tnks, > Amancio > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 12:51:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11285 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 12:51:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mhs.mhs.rosmail.com (mhs.rosmail.com [195.90.130.88]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11264 for ; Sun, 22 Nov 1998 12:51:05 -0800 (PST) (envelope-from 0824@08700000.mhs.rosmail.com) Received: from NetWare MHS (SMF70) by mhs.mhs.rosmail.com via Connect2-SMTP 4.32.03; Sun, 22 Nov 1998 23:49:52 +0300 Message-ID: <161BD2D781F0D57E%161BD2D781F0D57E@mhs.mhs.rosmail.com> Date: Sun, 22 Nov 1998 23:41:10 +0300 From: Vladislav SAFRONOV <0824@08700000.mhs.rosmail.com> Organization: Rosnet To: freebsd-hackers@FreeBSD.ORG Subject: Help! Modifying Linux sources to compile under 2.2.7R. X-SMF-Hop-Count: 3 MIME-Version: 1.0 Content-type: text/plain; charset="KOI8-R" Content-transfer-encoding: 7bit X-Mailer: Connect2-SMTP 4.32.03 MHS/SMF to SMTP Gateway Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to compile a little c program under Freebsd, but the source warns: "Linux 2.0.33 source, will compile on BSD if you modify the ip header etc." I thought small tcp/ip applications could be copmiled under any Unix :(, Well what should I modify? What's the difference between BSD ip header and Linux ip header? the source: ... struct iphdr *iph=(struct iphdr *)buf; struct udphdr *udp=(struct udphdr *)(buf + 20); ... iph->version=4; iph->ihl=5; iph->tos=0; iph->tot_len=htons(sizeof(buf)); iph->id=htons(1234); iph->frag_off=0; iph->ttl=255; iph->protocol=17; iph->saddr=inet_addr(SIP); iph->daddr=resolve_address(argv[1]); Should I modify udp header as well? Sincerely, Vlad Safronov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 13:12:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13627 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 13:12:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13617 for ; Sun, 22 Nov 1998 13:12:53 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Mon, 23 Nov 1998 08:11:36 +1100 Date: Mon, 23 Nov 1998 08:12:02 +1100 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #314 To: hackers@FreeBSD.ORG Message-Id: <98Nov23.081136est.40323@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998 08:39:16 -0800 (PST), EE wrote: >I'm looking for a password generator. And various people responded with things like: "it's really piece of cake to write that kind of program in perl or C", and a couple of people posted sample code. Unfortunately, all of the postings I've seen so far suffer from a fatal flaw - all of them use pseudo-random numbers and hence generate pseudo-random passwords. This means that the password can be fairly readily broken by knowing the algorithm used to generate the password. (On the positive side, one of them did attempt to increase the entropy of the generated password, but srandom() only provides 32-bits, which is trivial to crack nowadays. On the negative side, another program made no attempt to seed the random number, thus providing a conveniently repeatable list of passwords for any cracker). A true random password requires random numbers, which are very difficult to generate within a computer. Depending on your needs, /dev/random may be adequate (see random(4)). srandomdev(3) is a start, but unfortunately uses /dev/urandom instead of /dev/random and can quietly fall back to srandom(3) in some cases. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 13:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17344 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 13:56:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17332 for ; Sun, 22 Nov 1998 13:56:42 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id NAA10631; Sun, 22 Nov 1998 13:56:23 -0800 (PST) Message-Id: <199811222156.NAA10631@root.com> To: Amancio Hasty cc: hackers@FreeBSD.ORG Subject: Re: ftp.freebsd.org and slow downloads... In-reply-to: Your message of "Sun, 22 Nov 1998 12:10:25 PST." <199811222010.MAA00438@rah.star-gate.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 22 Nov 1998 13:56:23 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >{hasty} traceroute ftp.freebsd.org >traceroute to wcarchive.cdrom.com (209.155.82.18), 30 hops max, 40 byte packets > 1 flow (209.249.129.137) 0.759 ms 0.730 ms 0.653 ms > 2 test (209.249.128.141) 7.955 ms 7.740 ms 7.713 ms > 3 main2-133-3.sjc.above.net (209.133.3.3) 9.962 ms 8.516 ms 8.564 ms > 4 core2-main2.sjc.above.net (207.126.96.137) 11.331 ms 12.017 ms 10.338 ms > 5 ames-core2-ds3.sjc.above.net (207.126.96.194) 10.107 ms 12.956 ms >10.753 ms > 6 mae-west1.US.CRL.NET (198.32.136.10) 12.103 ms 13.555 ms 11.557 ms > 7 sfo-ames.2.T3.us.crl.net (165.113.50.93) 12.703 ms 12.761 ms 14.210 ms > 8 wcarchive.cdrom.com (209.155.82.18) 14.997 ms 16.911 ms 20.400 ms > >I am getting fairly decent packet response time from ftp.freebsd.org however >whenever I tried to download something it takes a very long time and very >frequently drops my ftp connection. -hackers is not the proper forum to be discussing problems with FreeBSD Project or WC CDROM machines. Contact me directly about these issues. There have been a whole lot of things happening this past weekend that have caused connectivity problems, not the least of which was a physical move of wcarchive to a new facility and the re-homing of the PB-NAP OC3 and other peering point DS3's. At this very moment, MCI's PB-NAP router is down, which is having the indirect effect of overloading CRL's MAE-west circuits. Engineers are working on that. Things will continue to be flakey for another two weeks until CRL has completed the move of their core to the new data center. -DG David Greenman Co-founder/Principal Architect, 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 Sun Nov 22 14:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22398 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 14:51:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22393 for ; Sun, 22 Nov 1998 14:51:06 -0800 (PST) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id RAA02458; Sun, 22 Nov 1998 17:50:20 -0500 (EST) From: "Allen Smith" Message-Id: <9811221750.ZM2456@beatrice.rutgers.edu> Date: Sun, 22 Nov 1998 17:50:20 -0500 In-Reply-To: Peter Jeremy "Re: freebsd-hackers-digest V4 #314" (Nov 22, 4:13pm) References: <98Nov23.081136est.40323@border.alcanet.com.au> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #314 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 22, 4:13pm, Peter Jeremy (possibly) wrote: > On Fri, 20 Nov 1998 08:39:16 -0800 (PST), EE wrote: > >I'm looking for a password generator. > > And various people responded with things like: > "it's really piece of cake to write that kind of program in perl or C", > and a couple of people posted sample code. > > Unfortunately, all of the postings I've seen so far suffer from a > fatal flaw - all of them use pseudo-random numbers and hence generate > pseudo-random passwords. Well... no, actually, mine didn't. It uses pgp's random source, which is composed of key timings whenever you're entering text into it. > A true random password requires random numbers, which are very > difficult to generate within a computer. Depending on your needs, > /dev/random may be adequate (see random(4)). srandomdev(3) is a > start, but unfortunately uses /dev/urandom instead of /dev/random > and can quietly fall back to srandom(3) in some cases. Certainly, using /dev/random is nice... but the code I wrote was for IRIX originally. (It's possible that pgp 5 may use /dev/random if it's available; I haven't gotten around to downloading it yet and checking.) -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 15:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27904 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 15:53:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27883 for ; Sun, 22 Nov 1998 15:53:13 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA18256; Mon, 23 Nov 1998 00:51:59 +0100 (CET) (envelope-from olli) Date: Mon, 23 Nov 1998 00:51:59 +0100 (CET) From: Oliver Fromme Message-Id: <199811222351.AAA18256@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? Cc: mike@smith.net.au Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote in list.freebsd-hackers: > > [...] > > The bootloader (I'm using rawboot from a floppy) correctly > > loads the kernel to 00400000, but it hangs right after that. > > Did I miss anything? > > > > Any help would be greatly appreciated. > > Changing the kernel load address will require a great amount of effort. > There are almost certainly hardcoded copies of the value scattered > around. My experiments led me to the same conclusion. :-( > > Background of the problem: I'm trying to boot a diskless > > computer with a network boot ROM by LanWorks > > (www.lanworks.com). They require to make a bootable floppy > > first, then put an image of that floppy on a tftp server. > > The ROM loads that image, makes a RAM disk from it and boots > > it. The problem is: That RAM disks seems to overlap with the > > kernel at 00100000. There doesn't seem to be a way to change > > the location of the RAM disk. > > That's ugly. 8( Yes. Meanwhile I found out that the overlapping memory locations are only half of the problem. Thanks to Lanworks tech support, I got a new version of their image loader stub that relocates the RAM disk to a different location. But there's still the same problem. I tracked it down to some strange and subtl interference between the 2nd stage bootloader and the RAM disk's INT 0x13 interface. It occurs as soon as the bootloader switches to protected mode. After some dirty hacking, it works now -- I created a modified version of rawboot (I called it ramboot) which reads the kernel directly from the RAM disk in memory. Should I give the code to someone who can commit it? On the other hand, it's really ugly code, and (AFAIK) there will be a new ELF-based bootloader soon, so it might not be worth bothering. Anyway, if someone needs some code to boot his/her FreeBSD box with a Lanworks ROM, I've put the "ramboot" stuff on the web: http://dorifer.heim3.tu-clausthal.de/~olli/ramboot.tar.gz Regards Oliver PS: I'm not an employee of Lanworks, but a happy customer. :) -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 16:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01346 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 16:17:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01340 for ; Sun, 22 Nov 1998 16:17:48 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id QAA02775; Sun, 22 Nov 1998 16:17:12 -0800 (PST) Date: Sun, 22 Nov 1998 16:17:12 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811230017.QAA02775@math.berkeley.edu> To: obrien@NUXI.com Subject: Re: AMD/NFS problems with 3.0 Cc: dan@math.berkeley.edu, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From majordom@FreeBSD.ORG Sun Nov 22 03:07:21 1998 > Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) > by math.berkeley.edu (8.8.7/8.8.7) with ESMTP id DAA15699 > for ; Sun, 22 Nov 1998 03:07:20 -0800 (PST) > Delivered-To: vmailer-hackers@freebsd.org > Received: by hub.freebsd.org (VMailer, from userid 1) > id 4753B9993; Sun, 22 Nov 1998 03:07:34 -0800 (PST) > Received: (from majordom@localhost) > by hub.freebsd.org (8.8.8/8.8.8) id DAA26783 > for freebsd-hackers-outgoing; Sun, 22 Nov 1998 03:07:33 -0800 (PST) > (envelope-from owner-freebsd-hackers@FreeBSD.ORG) > Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) > by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26778 > for ; Sun, 22 Nov 1998 03:07:31 -0800 (PST) > (envelope-from obrien@NUXI.com) > Received: (from obrien@localhost) > by relay.nuxi.com (8.9.1/8.9.1) id DAA09074; > Sun, 22 Nov 1998 03:05:40 -0800 (PST) > (envelope-from obrien) > Message-ID: <19981122030540.B8758@nuxi.com> > Date: Sun, 22 Nov 1998 03:05:40 -0800 > From: "David O'Brien" > To: Robert Withrow , hackers@FreeBSD.ORG > Subject: Re: AMD/NFS problems with 3.0 > Reply-To: obrien@NUXI.com > References: <199811182229.RAA25694@tuva.engeast.baynetworks.com> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > X-Mailer: Mutt 0.93.2i > In-Reply-To: <199811182229.RAA25694@tuva.engeast.baynetworks.com>; from Robert Withrow on Wed, Nov 18, 1998 at 05:29:07PM -0500 > X-Operating-System: FreeBSD 3.0-CURRENT > Organization: The NUXI BSD group > X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A > X-Pgp-Keyid: 34F9F9D5 > Sender: owner-freebsd-hackers@FreeBSD.ORG > Precedence: bulk > X-Loop: FreeBSD.ORG > Status: RO > > > At first I though this might be related to these messages that went > > to the log the first time I started amd: > > > > noconn option exists, and was turned OFF! (May cause NFS hangs > > on some systems...) > > These are always printed out. I guess I should comment them out, or > determine if we really can use the optimization. The comments in the > code by the Columbia people are often out of date with respect to > FreeBSD-CURRENT. > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@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 Sun Nov 22 16:33:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02670 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 16:33:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02665 for ; Sun, 22 Nov 1998 16:33:00 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id QAA03103; Sun, 22 Nov 1998 16:32:25 -0800 (PST) Date: Sun, 22 Nov 1998 16:32:25 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811230032.QAA03103@math.berkeley.edu> To: obrien@NUXI.com Subject: Re: AMD/NFS problems with 3.0 Cc: dan@math.berkeley.edu, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Please ignore my previous posting. I somehow neglected to rewrite the temporary mail message file after editing it into this:) > > At first I though this might be related to these messages that went > > to the log the first time I started amd: > > > > noconn option exists, and was turned OFF! (May cause NFS hangs > > on some systems...) > > These are always printed out. I guess I should comment them out, or > determine if we really can use the optimization. The comments in the > code by the Columbia people are often out of date with respect to > FreeBSD-CURRENT. I have often wondered what this was really about. Can someone explain? At first I thought the issue was tcp versus udp, but this turns out to be wrong. The issue seems to be if the BSD connect() system call is used to associate the local BSD datagram (i.e. UDP) "socket" with the remote nfs server datagram "socket". The alternative would be to skip the connect() and specify the destination address every time a packet is sent and examine the source address every time a packet is received. I don't really understand the issue here. UDP is essentially a connectionless protocol. I don't understand the function of the BSD connect() system call other than as a programming convenience. I don't see why it should cause a noticeable performance improvement. It does have the effect of causing NFS responses to be rejected if they don't come from the same IP address/port# to which the NFS request was sent and this causes NFS mounts to hang if the NFS server has multiple internet interfaces and chooses to send its responses back through a different interface. (I have not yet noticed an NFS server responding through a different port#.) My workaround has always been to specify the "noconn" option for amd nfs mounts. Beginning sometime between 2.2.5-RELEASE and 3.0-RELEASE, the amd automounter and perhaps the OS were changed so that the thing to do was to specify the "conn" option in the amd maps. Then you don't get the above warning message and your remote mounts don't hang. This is contrary to my weak understanding of the issue. Can someone explain why we must now "conn" where previously we had to "noconn"? The 3.0-RELEASE/RELNOTES.TXT file says: The Amd automounter has been updated from the 1993 4.4BSD version to the latest current version of am-utils. Map options have changed somewhat, and a new configuration file, /etc/amd.conf, is supported. See ``man 5 amd.conf''. It might be helpful if the "conn" change was specifically mentioned and this paragraph was restored to the "USERLAND CHANGES" section of the release notes. It certainly confused the heck out of me for a while. I had to read the amd sources to figure out how to fix my amd configuration. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 16:58:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04556 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 16:58:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04548 for ; Sun, 22 Nov 1998 16:58:27 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40343>; Mon, 23 Nov 1998 11:57:14 +1100 Date: Mon, 23 Nov 1998 11:57:40 +1100 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #314 To: easmith@beatrice.rutgers.edu Cc: hackers@FreeBSD.ORG Message-Id: <98Nov23.115714est.40343@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allen Smith wrote: >Well... no, actually, mine didn't. It uses pgp's random source, which >is composed of key timings whenever you're entering text into it. My apologies, you are correct. I didn't look closely enough and was reading `md5' instead of `pgp' at a critical point. > (It's possible that pgp 5 may use /dev/random if it's >available; I haven't gotten around to downloading it yet and checking.) It appears it does - it definitely has the hooks. (Which would make it a complete circle - some of the ideas behind /dev/random come from pgp). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 17:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05116 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 17:05:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05110 for ; Sun, 22 Nov 1998 17:05:04 -0800 (PST) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id UAA02854; Sun, 22 Nov 1998 20:04:20 -0500 (EST) From: "Allen Smith" Message-Id: <9811222004.ZM2852@beatrice.rutgers.edu> Date: Sun, 22 Nov 1998 20:04:20 -0500 In-Reply-To: Peter Jeremy "Re: freebsd-hackers-digest V4 #314" (Nov 22, 7:59pm) References: <98Nov23.115714est.40343@border.alcanet.com.au> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #314 Cc: 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 On Nov 22, 7:59pm, Peter Jeremy (possibly) wrote: > Allen Smith wrote: > >Well... no, actually, mine didn't. It uses pgp's random source, which > >is composed of key timings whenever you're entering text into it. > > My apologies, you are correct. I didn't look closely enough and was > reading `md5' instead of `pgp' at a critical point. No problem; I've made similar goofs myself. What it uses MD5 for is in processing the file that pgp produces. > > (It's possible that pgp 5 may use /dev/random if it's > >available; I haven't gotten around to downloading it yet and checking.) > > It appears it does - it definitely has the hooks. (Which would make it > a complete circle - some of the ideas behind /dev/random come from pgp). Ah, good. Now if I could only persuade the idiots at SGI to include /dev/random et al... there are reasons that we're going with FreeBSD for a firewall machine. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 19:16:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16227 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 19:16:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16222 for ; Sun, 22 Nov 1998 19:16:25 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 14827 invoked by uid 1001); 23 Nov 1998 03:16:02 -0000 Message-ID: <19981122221602.D8814@numachi.com> Date: Sun, 22 Nov 1998 22:16:02 -0500 From: Brian Reichert To: freebsd-hackers@FreeBSD.ORG Subject: serial console vs ttyd0 vs cuaa0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wrangled an exploration of a serial console under 2.2.7-R, and noticed an anomoly: Well, the serial console did work right off, once I put '-P' in /boot.config. What I ran into was during my efforts to also run getty on ttyd0, so that I could freely make use of either the video console or the tty port with relative freedom. What I found: Without getty, if I simply hung the terminal off of the serial port, I could, as root, type: # cat > /dev/cuaa0 and I could get output _to_ the terminal. If I typed: # cat /dev/ttyd0 I would get no input _from_ the terminal, but # cat /dev/cuaa0 _would_ ?! Did I miss something? I had thought that ttyd was for incoming connections, and cuaa was for outgoing connections. For a workaround, I changed /etc/ttys to attach getty to cuaa0. But, that flies in the face on convention. _If_ I have muntant hardware (a Dasher 211 and a homespun cable), why did the serial console work to begin with? -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (603)-434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 19:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19347 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 19:42:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-207.airnet.net [207.242.81.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19291 for ; Sun, 22 Nov 1998 19:41:58 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id VAA10089; Sun, 22 Nov 1998 21:37:29 -0600 (CST) Message-ID: <3658D878.B60A1874@airnet.net> Date: Sun, 22 Nov 1998 21:37:28 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: dg@root.com CC: hackers@FreeBSD.ORG Subject: Re: ftp.freebsd.org and slow downloads... References: <199811222156.NAA10631@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: > > >{hasty} traceroute ftp.freebsd.org > >traceroute to wcarchive.cdrom.com (209.155.82.18), 30 hops max, 40 byte packets > > 1 flow (209.249.129.137) 0.759 ms 0.730 ms 0.653 ms > > 2 test (209.249.128.141) 7.955 ms 7.740 ms 7.713 ms > > 3 main2-133-3.sjc.above.net (209.133.3.3) 9.962 ms 8.516 ms 8.564 ms > > 4 core2-main2.sjc.above.net (207.126.96.137) 11.331 ms 12.017 ms 10.338 ms > > 5 ames-core2-ds3.sjc.above.net (207.126.96.194) 10.107 ms 12.956 ms > >10.753 ms > > 6 mae-west1.US.CRL.NET (198.32.136.10) 12.103 ms 13.555 ms 11.557 ms > > 7 sfo-ames.2.T3.us.crl.net (165.113.50.93) 12.703 ms 12.761 ms 14.210 ms > > 8 wcarchive.cdrom.com (209.155.82.18) 14.997 ms 16.911 ms 20.400 ms > > > >I am getting fairly decent packet response time from ftp.freebsd.org however > >whenever I tried to download something it takes a very long time and very > >frequently drops my ftp connection. > > -hackers is not the proper forum to be discussing problems with FreeBSD > Project or WC CDROM machines. Contact me directly about these issues. I suppose there is a web page or so for those of us who aren't on the west coast to check the "health of the net"? I am more interested in who has a overloaded router than WC CDROM. It's not my business anyway. :-) -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 22:26:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02157 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 22:26:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02145 for ; Sun, 22 Nov 1998 22:26:39 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA02549 for ; Sun, 22 Nov 1998 22:26:06 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA16613 for ; Sun, 22 Nov 1998 22:26:04 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA02686 for hackers@freebsd.org; Sun, 22 Nov 1998 22:26:03 -0800 (PST) Date: Sun, 22 Nov 1998 22:26:03 -0800 (PST) From: Don Lewis Message-Id: <199811230626.WAA02686@salsa.gv.tsc.tdk.com> To: hackers@FreeBSD.ORG Subject: questions about adding sysctl knobs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for some guidance about adding sysctl knobs to the kernel. My immediate task is to allow the new F_SETOWN code that I recently committed to 3.0-current to be tuned by using sysctl instead of having some fairly arbitrary policy decisions hard coded into the kernel. I figure I need two knobs to do this. The first knob would limit the allowable range of arguments to fcntl(F_SETOWN). The limits from most to least restrictive would be: the current process the current process group a process or process group in the current session any process or process group The second knob would control whether credentials are be checked at the time signals are sent. Where should these knobs go in the name space, and what are the other magic values I need to plug into the sysctl infrastructure? Once I get this implemented, I've got another little project that I want to build a sysctl tunable into from the start. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 22 22:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04158 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 22:48:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04153 for ; Sun, 22 Nov 1998 22:48:23 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id XAA15351; Sun, 22 Nov 1998 23:47:16 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Sun, 22 Nov 1998 23:47:15 -0700 (MST) From: Doug Russell To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: [Vinum] Stupid benchmark: newfsstone In-Reply-To: <98Nov13.140613est.40335@border.alcanet.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 On Fri, 13 Nov 1998, Peter Jeremy wrote: > Greg Lehey wrote: > > And it's almost impossible to find > >spindle synchronized disks nowadays. > > Seagate Barracuda's support it, I assumed that the newer Seagates did My Quantum Atlas-IIs have the same setup. I've never actually tried it either, but according to the manual, you basically just wire them together. You can even program a certain number of degrees to skew each disk in the chain from directly synced to compensate for command delays, etc. Kinda cool if you ask me. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 00:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16269 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 00:45:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from faber.elte.hu (faber.elte.hu [157.181.78.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA16264 for ; Mon, 23 Nov 1998 00:45:31 -0800 (PST) (envelope-from DBECK@ludens.elte.hu) Received: from ludens.elte.hu by ludens.elte.hu (MX V4.2 VAX) with SMTP; Mon, 23 Nov 1998 09:41:11 +0100 Date: Mon, 23 Nov 1998 09:40:46 +0000 From: David Beck To: Terry Lambert CC: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG Subject: Re: SYSV Semaphores & mmap problems In-Reply-To: <199811210335.UAA09506@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Nov 1998, Terry Lambert wrote: > Date: Sat, 21 NOV 1998 03:35:51 +0000 (GMT) > From: Terry Lambert > To: David Beck > Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG > Subject: Re: SYSV Semaphores & mmap problems > > > > > I ran into two problems with FreeBSD: > > > > 1., If I create a program with a few threads and then I block > > > > one thread with a SYSV semaphore, then it blocks all threads. > > > > Any ideas ? > > > > > > Use a mutex instead. SYSV semaphores are not process reentrant > > > (they're semaphores). Neither are pthreads mutexes, but at > > > least you will only block threads wanting the mutex instead of > > > all threads. > > > > Yep. The problem is to control access to a shared memory segment > > between unrelated processes and in the same time the server process > > actually is a multithreaded process. > > Use fcntl(2) based locks. > > Preferrably against an mmap'ed file as the shared memory region > instead of a SYSV shared memory region, to avoid using up kernel > virtual address space. > > Alternately, someone need to write a non-blocking version of > the system call and implement call conversion in a (new) libipc_r. > Thank you. The sysv semaphore seems fairly slow on other systems, anyway. Do you know is fcnt faster ? Regards, David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 00:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16332 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 00:46:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m1-12-dbn.dial-up.net [196.34.155.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16319 for ; Mon, 23 Nov 1998 00:46:02 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA12135; Mon, 23 Nov 1998 10:44:55 +0200 (SAT) From: Robert Nordier Message-Id: <199811230844.KAA12135@ceia.nordier.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811222351.AAA18256@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Nov 23, 98 00:51:59 am" To: freebsd-hackers@FreeBSD.ORG Date: Mon, 23 Nov 1998 10:44:52 +0200 (SAT) Cc: mike@smith.net.au X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > Mike Smith wrote in list.freebsd-hackers: > > > Background of the problem: I'm trying to boot a diskless > > > computer with a network boot ROM by LanWorks > > > (www.lanworks.com). They require to make a bootable floppy > > > first, then put an image of that floppy on a tftp server. > > > The ROM loads that image, makes a RAM disk from it and boots > > > it. The problem is: That RAM disks seems to overlap with the > > > kernel at 00100000. There doesn't seem to be a way to change > > > the location of the RAM disk. > > > > That's ugly. 8( > > Yes. Meanwhile I found out that the overlapping memory > locations are only half of the problem. Thanks to Lanworks > tech support, I got a new version of their image loader stub > that relocates the RAM disk to a different location. But > there's still the same problem. > > I tracked it down to some strange and subtl interference > between the 2nd stage bootloader and the RAM disk's INT 0x13 > interface. It occurs as soon as the bootloader switches to > protected mode. > > After some dirty hacking, it works now -- I created a modified > version of rawboot (I called it ramboot) which reads the kernel > directly from the RAM disk in memory. > > Should I give the code to someone who can commit it? On the > other hand, it's really ugly code, and (AFAIK) there will be a > new ELF-based bootloader soon, so it might not be worth > bothering. We do need a more capable netboot replacement, and if Lanworks is as responsive as they appear to be, then supporting their product may be an easy route to satisfying this requirement. It might be a reasonable solution to make something like this available as a port; after all, the boot blocks are *expected* to be somewhat out of sync with kernel development. Though I'd quite like to see it working with the new boot1/boot2 and boot/loader code, in some form, now that Oliver has shown the way. > Anyway, if someone needs some code to boot his/her FreeBSD box > with a Lanworks ROM, I've put the "ramboot" stuff on the web: > http://dorifer.heim3.tu-clausthal.de/~olli/ramboot.tar.gz Thanks. I've just fetched a copy. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 02:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26060 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 02:22:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.online.samara.ru (SamaraOnline.customers.samara.net [195.128.128.206]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26055 for ; Mon, 23 Nov 1998 02:22:11 -0800 (PST) (envelope-from sa@ns.online.samara.ru) Received: (from sa@localhost) by ns.online.samara.ru (8.8.8/8.8.5) id OAA28202 for freebsd-hackers@freebsd.org; Mon, 23 Nov 1998 14:20:34 GMT To: freebsd-hackers@FreeBSD.ORG Message-ID: Organization: Cronyx Ltd. From: "SysAdmin" Date: Mon, 23 Nov 98 14:20:33 +0000 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: breakpoint on i/o in kernel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need breakpoint on i/o in kernel How doing this in ddb, or exist another way ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 02:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26921 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 02:29:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26908 for ; Mon, 23 Nov 1998 02:29:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA07493; Mon, 23 Nov 1998 20:56:30 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id UAA14376; Mon, 23 Nov 1998 20:56:20 +1030 (CST) Message-ID: <19981123205619.Q430@freebie.lemis.com> Date: Mon, 23 Nov 1998 20:56:19 +1030 From: Greg Lehey To: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from SysAdmin on Mon, Nov 23, 1998 at 02:20:33PM +0000 WWW-Home-Page: http://www.lemis.com/~grog 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 Monday, 23 November 1998 at 14:20:33 +0000, SysAdmin wrote: > I need breakpoint on i/o in kernel > How doing this in ddb, or exist another way ? Well, the syntax is: b
can be a hex value or an expression, possibly symbolic. Are you asking which address to choose? Then you need to say what you want to do. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 02:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28023 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 02:41:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28015 for ; Mon, 23 Nov 1998 02:41:01 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id KAA19819 for ; Mon, 23 Nov 1998 10:40:24 GMT (envelope-from didier@omnix.net) Date: Mon, 23 Nov 1998 11:40:24 +0100 (CET) From: Didier Derny To: hackers@FreeBSD.ORG Subject: help! booting 3.0-RELEASE from ide zip Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm trying to boot from an ide zip drive. I generated a boot disk on a scsi zip but I'm unable to boot from the ide zip drive. It refuses to see the zip drive except as a floppy disk. in that cases it sees the boot block but I'm unable to go further (it tries to load from fd) I've not succedded in trying to override manually to 0:wd(0,a) Thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 03:19:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02120 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 03:19:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kryten.cms.livjm.ac.uk (kryten.cms.livjm.ac.uk [150.204.51.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02113 for ; Mon, 23 Nov 1998 03:19:25 -0800 (PST) (envelope-from cmspsum1@livjm.ac.uk) Received: from boole.cms.livjm.ac.uk (boole.cms.livjm.ac.uk [150.204.48.17]) by kryten.cms.livjm.ac.uk (8.8.8+Sun/8.8.8) with ESMTP id LAA02998 for ; Mon, 23 Nov 1998 11:18:50 GMT Message-ID: <365943F3.2B6DC314@livjm.ac.uk> Date: Mon, 23 Nov 1998 11:16:03 +0000 From: putra Organization: LJMU X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: FreeBSD 2.0.5 X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm Putra from Liverpool John Moores University. I'm a researcher and one of my project uses FreeBSD 2.0.5 release. Do still have the copy for this version. It is very important for me in order to finish my course. I hope you dont mind, please. Putra Sumari Room 706 Distributed Multimedia Group School of Computing and Mathematical Sciences University of Liverpool Byrom St. Liverpool L3 3AF. Tel : +44(0)151-231-2089 Fax : +44(0)151-207-4594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 05:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15742 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 05:44:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15734 for ; Mon, 23 Nov 1998 05:44:04 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KFCFOFAJ; Mon, 23 Nov 98 13:43:30 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 23 Nov 1998 14:43:19 +0100 To: Joel Ray Holveck From: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: Terry Lambert , dillon@apollo.backplane.com (Matthew Dillon), rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <86hfvuia7y.fsf@detlev.UUCP> References: <199811181842.KAA06180@apollo.backplane.com> <3.0.5.32.19981120103442.0099f460@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It would require changing libc to read the kernel config file. Do we >really want to mess with this? Unless it adds too much complexity, I'd say 'yes'. A major strength of FreeBSD is its speed. Increasing its speed, and ability to specificially utilize your platform, would widen our lead. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 05:45:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16090 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 05:45:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16083 for ; Mon, 23 Nov 1998 05:45:11 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KFCFVAOK; Mon, 23 Nov 98 13:44:38 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 23 Nov 1998 14:44:27 +0100 To: John Polstra , joelh@gnu.org From: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: hackers@FreeBSD.ORG In-Reply-To: <199811201714.JAA18156@vashon.polstra.com> References: <86hfvuia7y.fsf@detlev.UUCP> <199811181842.KAA06180@apollo.backplane.com> <3.0.5.32.19981120103442.0099f460@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Of course we don't. Nobody who cares about speed is going to use a 486. Are you saying that we're going to say to people "Hey, FreeBSD is not intended to run on anything less than a Pentium, we don't wish to get involved with anything less, the people out there who're stuck with a 486 had better go support Linux instead?" --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 05:57:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17243 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 05:57:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17238 for ; Mon, 23 Nov 1998 05:56:58 -0800 (PST) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id IAA07151; Mon, 23 Nov 1998 08:58:35 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <199811231358.IAA07151@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dan@math.berkeley.edu (Dan Strick) cc: obrien@NUXI.com, hackers@FreeBSD.ORG Subject: Re: AMD/NFS problems with 3.0 In-reply-to: Your message of "Sun, 22 Nov 1998 16:32:25 PST." <199811230032.QAA03103@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 08:58:35 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dan@math.berkeley.edu said: :- I have not yet noticed an NFS server responding through a different :- port#. I have (buggy ?) sunos 4.1.4 servers that do that. I havn't yet sniffed the wire to see if that is the source of my current NFS problems. Everthing here is now switched 100 to the desktop through a Baystack 350. I have to get a hub to put the client system and the sniffer on so I can capture the NFS session... (And, it might be that the Baystack is a problem too, for all I know...). --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 07:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25140 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 07:16:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25057 for ; Mon, 23 Nov 1998 07:16:57 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA009764095; Mon, 23 Nov 1998 10:14:55 -0500 Date: Mon, 23 Nov 1998 10:14:55 -0500 (EST) From: Bill Fumerola To: Marius Bendiksen Cc: John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> 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, 23 Nov 1998, Marius Bendiksen wrote: > >Of course we don't. Nobody who cares about speed is going to use a 486. > > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" When the change adds complexity without a significant return, yes. The change only affects a small userbase as well. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 07:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26591 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 07:35:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26584 for ; Mon, 23 Nov 1998 07:35:45 -0800 (PST) (envelope-from pb@ludd.luth.se) Received: from father.ludd.luth.se (pb@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id QAA28024 for ; Mon, 23 Nov 1998 16:35:09 +0100 From: Peter Brevik Received: (pb@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id QAA01781 for freebsd-hackers@freebsd.org; Mon, 23 Nov 1998 16:35:08 +0100 Message-Id: <199811231535.QAA01781@father.ludd.luth.se> Subject: DMA boosted PPP via parallell port ..? To: freebsd-hackers@FreeBSD.ORG Date: Mon, 23 Nov 1998 16:35:07 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL15 (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 Would be a good idea to implement the "LapLink" PPP as a ECP mode DMA driven PPP ..? I think advantages would be definitly both speed and less cpu load. Have a ECP specification at: http://wave.campus.luth.se/~pb/comp/standards/ecpmode.htm When I use PPP via Laplink as it now. The computer is not particular useful when transfer is in progress.. ;( /Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 08:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01420 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 08:25:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01413 for ; Mon, 23 Nov 1998 08:25:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA18513; Mon, 23 Nov 1998 08:24:45 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA28993; Mon, 23 Nov 1998 08:24:44 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> Date: Mon, 23 Nov 1998 08:24:44 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: hackers@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Nov-98 Marius Bendiksen wrote: >>Of course we don't. Nobody who cares about speed is going to use a 486. > > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" No. Have you even read this thread? This thread is about whether to expend significant effort and sacrifice significant elegance and maintainability in order to _slightly_ _optimize_ system calls for 486 systems. It has nothing to do with whether we support 486 systems or not. --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 09:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06032 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 09:01:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06027 for ; Mon, 23 Nov 1998 09:01:14 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA03695; Mon, 23 Nov 1998 18:00:40 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA07198; Mon, 23 Nov 1998 18:00:39 +0100 (MET) Message-ID: <19981123180039.T24412@follo.net> Date: Mon, 23 Nov 1998 18:00:39 +0100 From: Eivind Eklund To: Marius Bendiksen , Joel Ray Holveck Cc: Terry Lambert , Matthew Dillon , rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model References: <3.0.5.32.19981120103442.0099f460@mail.scancall.no> <86hfvuia7y.fsf@detlev.UUCP> <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.5.32.19981123144319.00a4d560@mail.scancall.no>; from Marius Bendiksen on Mon, Nov 23, 1998 at 02:43:19PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 23, 1998 at 02:43:19PM +0100, Marius Bendiksen wrote: > >It would require changing libc to read the kernel config file. Do we > >really want to mess with this? > > Unless it adds too much complexity, I'd say 'yes'. It adds too much complexity/interdependcies, in my opinion. Unless somebody can show significant speed gains (well into the measurable range), I don't think it is worthwhile. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 09:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07337 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 09:14:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07322 for ; Mon, 23 Nov 1998 09:14:02 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id RAA02776; Mon, 23 Nov 1998 17:13:22 GMT (envelope-from didier@omnix.net) Date: Mon, 23 Nov 1998 18:13:22 +0100 (CET) From: Didier Derny To: Kevin Van Maren cc: hackers@FreeBSD.ORG Subject: Re: network board with several 10baseT (fwd) In-Reply-To: <199810082003.OAA15474@fast.cs.utah.edu> 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, 8 Oct 1998, Kevin Van Maren wrote: > > > Is tehre any working network board with several lan interfaces on the same > > board > > > Adaptec makes a 4-port card (6944/A) that is supported. Znyx > also makes one that *I believe* works -- both those use the DEC > 21140 chip and the if_de driver. All three retail for around > $695 (actual cost is $500-$550, or a little less for the Phobos card). > Hi I'm trying to use an adaptec ANA 6944A. with FreeBSD 3.0-RELEASE it works fine on one port (de0) but crashes when I try to configure a second port (the machine froze) do you have any idea ? thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 10:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13806 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:07:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13800 for ; Mon, 23 Nov 1998 10:07:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA18693; Mon, 23 Nov 1998 11:06:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA25928; Mon, 23 Nov 1998 11:06:24 -0700 Date: Mon, 23 Nov 1998 11:06:24 -0700 Message-Id: <199811231806.LAA25928@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Marius Bendiksen Cc: John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> References: <86hfvuia7y.fsf@detlev.UUCP> <199811181842.KAA06180@apollo.backplane.com> <3.0.5.32.19981120103442.0099f460@mail.scancall.no> <199811201714.JAA18156@vashon.polstra.com> <3.0.5.32.19981123144427.00b40940@mail.scancall.no> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Of course we don't. Nobody who cares about speed is going to use a 486. > > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" Huh? No, what *was* said that for the .01% performance increase on slow hardware it isn't worth the extra complexity it gives to the entire code-base. If you need it faster, use a faster processor. This is just good engineering. Optimization is only done if positively affects the majority of your users. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 10:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14678 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:13:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14670 for ; Mon, 23 Nov 1998 10:13:12 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA12834; Mon, 23 Nov 1998 11:12:38 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd012731; Mon Nov 23 11:12:30 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA18985; Mon, 23 Nov 1998 11:12:25 -0700 (MST) From: Terry Lambert Message-Id: <199811231812.LAA18985@usr02.primenet.com> Subject: Re: SYSV Semaphores & mmap problems To: DBECK@ludens.elte.hu (David Beck) Date: Mon, 23 Nov 1998 18:12:25 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "David Beck" at Nov 23, 98 09:40:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Use fcntl(2) based locks. > > > > Preferrably against an mmap'ed file as the shared memory region > > instead of a SYSV shared memory region, to avoid using up kernel > > virtual address space. > > > > Alternately, someone need to write a non-blocking version of > > the system call and implement call conversion in a (new) libipc_r. > > > > Thank you. The sysv semaphore seems fairly slow on other systems, anyway. > Do you know is fcnt faster ? I haven't explictly timed them in FreeBSD, but I expect that fcntl is faster. I *did* time them on UnixWare, SunOS, AIX, and Solaris, and fcntl() was faster on those platforms by a significant amount; the AIX system used had a unified VM model, so I expect it to be predictive of FreeBSD. The semantics of SYSV semaphores are such that they expect to be in regions such that the calls are required to maintain the cache coherency on a split VM and buffer cache. They are built for function, not for speed. I do know that anonymous shared memory segments, such as those which arise from SYSV shared memory are vastly faster than those that arise from mmap'ing a file. This is because John Dyson did a lot of work to make the SYSV SHM faster for the Oracle database, which uses SYSV SHM. The work is directly applicable to mmap, as well, but mmap has an implied write-though caching to the backing object, making it somewhat slower as a result of needing to write through. You can actually get mmap'ed memory that is as fast as SYSV SHM by mmap'ing anonymous memory off of fd -1, or off of an fd that is attached to /dev/zero. The problem with this is that there is no way to rendezvous this memory between processes, unless they are all descendents of the original process that did the mapping. BSD really needs to fix this deficiency, probably by adding a method, similar to that for passing fd's, to pass region mappings to other processes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 10:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16890 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:33:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16885 for ; Mon, 23 Nov 1998 10:33:01 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23245; Mon, 23 Nov 1998 10:31:30 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA23238; Mon Nov 23 18:31:25 1998 Date: Mon, 23 Nov 1998 10:30:36 -0800 (PST) From: Julian Elischer To: Robert Nordier cc: freebsd-hackers@FreeBSD.ORG, ambrisko@whistle.com Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811230844.KAA12135@ceia.nordier.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 check with ambrisko@whistle.com he's done a lot with netbooting. On Mon, 23 Nov 1998, Robert Nordier wrote: > > We do need a more capable netboot replacement, and if Lanworks is > as responsive as they appear to be, then supporting their product > may be an easy route to satisfying this requirement. > > It might be a reasonable solution to make something like this > available as a port; after all, the boot blocks are *expected* to > be somewhat out of sync with kernel development. > > Though I'd quite like to see it working with the new boot1/boot2 > and boot/loader code, in some form, now that Oliver has shown the > way. > julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 10:42:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00421 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:42:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00400 for ; Mon, 23 Nov 1998 10:42:24 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23138; Mon, 23 Nov 1998 10:29:15 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA23131; Mon Nov 23 18:29:09 1998 Date: Mon, 23 Nov 1998 10:28:17 -0800 (PST) From: Julian Elischer To: freebsd-hackers@FreeBSD.ORG cc: mike@smith.net.au Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811222351.AAA18256@dorifer.heim3.tu-clausthal.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 when I got the original bootblocks working, I experimented with loading the kernel all over the place.. you SHOULD just need to to LINK it to a different address the old bootblocks would and the link address (in the aout header) with 0xff0000 (or something similar) (0xf00000 ?) and load there. so you would link for 0xf0200000 to load at 2MB. (the link address was in the Makefile at the time.) julian On Mon, 23 Nov 1998, Oliver Fromme wrote: > Mike Smith wrote in list.freebsd-hackers: > > > [...] > > > The bootloader (I'm using rawboot from a floppy) correctly > > > loads the kernel to 00400000, but it hangs right after that. > > > Did I miss anything? > > > > > > Any help would be greatly appreciated. > > > > Changing the kernel load address will require a great amount of effort. > > There are almost certainly hardcoded copies of the value scattered > > around. > > My experiments led me to the same conclusion. :-( > > > > Background of the problem: I'm trying to boot a diskless > > > computer with a network boot ROM by LanWorks > > > (www.lanworks.com). They require to make a bootable floppy > > > first, then put an image of that floppy on a tftp server. > > > The ROM loads that image, makes a RAM disk from it and boots > > > it. The problem is: That RAM disks seems to overlap with the > > > kernel at 00100000. There doesn't seem to be a way to change > > > the location of the RAM disk. > > > > That's ugly. 8( > > Yes. Meanwhile I found out that the overlapping memory > locations are only half of the problem. Thanks to Lanworks > tech support, I got a new version of their image loader stub > that relocates the RAM disk to a different location. But > there's still the same problem. > > I tracked it down to some strange and subtl interference > between the 2nd stage bootloader and the RAM disk's INT 0x13 > interface. It occurs as soon as the bootloader switches to > protected mode. > > After some dirty hacking, it works now -- I created a modified > version of rawboot (I called it ramboot) which reads the kernel > directly from the RAM disk in memory. > > Should I give the code to someone who can commit it? On the > other hand, it's really ugly code, and (AFAIK) there will be a > new ELF-based bootloader soon, so it might not be worth > bothering. > Anyway, if someone needs some code to boot his/her FreeBSD box > with a Lanworks ROM, I've put the "ramboot" stuff on the web: > http://dorifer.heim3.tu-clausthal.de/~olli/ramboot.tar.gz > > Regards > Oliver > > PS: I'm not an employee of Lanworks, but a happy customer. :) > > -- > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > > 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 Nov 23 10:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00524 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:42:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00467 for ; Mon, 23 Nov 1998 10:42:36 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA22729; Mon, 23 Nov 1998 10:20:59 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdQ22695; Mon Nov 23 18:20:49 1998 Date: Mon, 23 Nov 1998 10:19:38 -0800 (PST) From: Julian Elischer To: Amancio Hasty cc: Sabrina Minshall , hackers@FreeBSD.ORG Subject: Re: Availability of FREEBSD 3.0 in San Jose In-Reply-To: <199811210228.SAA00439@rah.star-gate.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 hey is your domain working now? I've bee trying to tell you we need a contractor... julian On Fri, 20 Nov 1998, Amancio Hasty wrote: > Try Central Computers on Stevens Creek. > > Cheers, > Amancio > > > > 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 Nov 23 10:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01629 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:52:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01623 for ; Mon, 23 Nov 1998 10:52:27 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA05222; Mon, 23 Nov 1998 11:52:14 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd005124; Mon Nov 23 11:52:07 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA21705; Mon, 23 Nov 1998 11:52:02 -0700 (MST) From: Terry Lambert Message-Id: <199811231852.LAA21705@usr02.primenet.com> Subject: Re: Would this make FreeBSD more secure? To: jdp@polstra.com (John Polstra) Date: Mon, 23 Nov 1998 18:52:01 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199811200316.TAA17171@vashon.polstra.com> from "John Polstra" at Nov 19, 98 07:16:13 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Someone should now go through the Sun CERT and other security > > advisories; I think at last count there were 40 some-odd that > > involved PAM. > > Per your suggestion back around August, I looked through them. I > didn't find anything relevant to us. The advisories were either > very old or they applied to modules that we don't use. > > Of course, it's entirely possible I missed an important one. So > anyone else is also encouraged to look for reports and see whether > the problems exist in the code I imported. You need to look at Bugtraq as well; go to: http://www.geek-girl.com/bugtraq/search.html And search for "PAM". Kick the "Maximum number of files returned" up to 1000; you'll need it. Also, I think the point of PAM is to let people use modules other than the ones that we use... so that argument is rather pointless. Here is a bug that will be common in network applications like ftpd linked to use PAM: http://geek-girl.com/bugtraq/1998_1/0111.html I don't know if you are using the rhost module, but if so, this may be relevent: http://geek-girl.com/bugtraq/1997_4/0000.html Also, PAM can become vulnerable based on libc implementation, since it is a consumer of libc; here's one example: http://geek-girl.com/bugtraq/1997_2/0228.html Of course, the list os so huge that I can't post it all here... Also, is our qpopper port still vulnerable to: http://geek-girl.com/bugtraq/1998_2/0657.html ??? I know that it violates the POP3 RFC on an APOP auth failure by not waiting for the "QUIT\r\n" after the "-ERR" before putting up "+OK" and shutting down the connection, so it's pretty old... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 10:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01648 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:52:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from soprano.psn.ie (soprano.psn.ie [194.106.150.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01640 for ; Mon, 23 Nov 1998 10:52:37 -0800 (PST) (envelope-from andy@psn.ie) Received: from gromit.psn.ie ([194.106.150.251] helo=gw.home) by soprano.psn.ie with esmtp (Exim 2.02 #1) id 0zi162-0000F8-00 for freebsd-hackers@freebsd.org; Mon, 23 Nov 1998 18:52:27 +0000 Received: from localhost (andy@localhost) by gw.home (8.8.8/8.8.8) with SMTP id SAA00296 for ; Mon, 23 Nov 1998 18:44:36 GMT (envelope-from andy@psn.ie) X-Authentication-Warning: gw.home: andy owned process doing -bs Date: Mon, 23 Nov 1998 18:44:36 +0000 (GMT) From: Andy Doran X-Sender: andy@gw.home To: freebsd-hackers@FreeBSD.ORG Subject: Kernel threads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all! I'm porting the NetBSD RAIDframe driver to FreeBSD at the moment, and I need a little help. Firstly, is there any way to dynamically create and destroy kernel threads like kthreads in NetBSD? I could create them statically but it would require a lot of changes to the code. Two other things; it is possible to guarantee that a psuedo device is attached only after all other psuedo devices? Also, do I have to modify the kernel to guarantee that my device can do it's RAID array setup as soon as all disklabels and partition tables have been read, or is there some sort of hook for this? Thanks for the help, Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:01:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02489 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:01:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02476 for ; Mon, 23 Nov 1998 11:00:55 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA09643; Mon, 23 Nov 1998 12:00:26 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd009542; Mon Nov 23 12:00:21 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA22251; Mon, 23 Nov 1998 12:00:15 -0700 (MST) From: Terry Lambert Message-Id: <199811231900.MAA22251@usr02.primenet.com> Subject: Re: SysV Init To: bs@adimus.de (Benedikt Stockebrand) Date: Mon, 23 Nov 1998 19:00:15 +0000 (GMT) Cc: syssgm@dtir.qld.gov.au, pechter@shell.monmouth.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Benedikt Stockebrand" at Nov 20, 98 10:26:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thursday, 19th November 1998, Bill/Carolyn Pechter wrote: > > > > >This is one area where SysV is superior. > > What's "superior"? Just additional functionality? Then it definitely > *is* superior. Easier handling? Then it's a big step in the wrong > direction. Which init is "superior" depends on your particular > needs. And SysV init has been developed to cover someones needs. Right. For example, if FreeBSD wanted to become the Oracle "appliance" operating system, as alluded to in Larry Ellison's COMDEX keynote, wherein he mentioned FreeBSD *first* in a list of candidate OS's: http://www.news.com/News/Item/0,4,28816,00.html then FreeBSD should probably work on bettering the SMP support, and on providing the necessary rc file hooks to allow third-party daemons that require system startup/shutdown notification (like, oh, say, Oracle?) to drop in and function. Let's see... what rc file hooks would a large UNIX database vendor be looking for? > Actually, making a SysV init use standard BSD-style rc scripts isn't > *that* much of a problem. And I strongly propose to keep the rc > scripts BSD-style because they're usually easier to understand > especially by newcomers. And especially since newcomers don't modify the things because they're afraid to, so it doesn't matter if they understand them or not... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02994 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:06:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (40-sweet.camalott.com [208.239.153.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02988 for ; Mon, 23 Nov 1998 11:06:38 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA62124; Mon, 23 Nov 1998 13:05:16 -0600 (CST) (envelope-from joelh) To: Terry Lambert Cc: DBECK@ludens.elte.hu (David Beck), freebsd-hackers@FreeBSD.ORG Subject: Re: SYSV Semaphores & mmap problems References: <199811231812.LAA18985@usr02.primenet.com> From: Joel Ray Holveck Date: 23 Nov 1998 13:05:15 -0600 In-Reply-To: Terry Lambert's message of "Mon, 23 Nov 1998 18:12:25 +0000 (GMT)" Message-ID: <86lnl2mdqs.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can actually get mmap'ed memory that is as fast as SYSV SHM > by mmap'ing anonymous memory off of fd -1, or off of an fd that > is attached to /dev/zero. The problem with this is that there > is no way to rendezvous this memory between processes, unless they > are all descendents of the original process that did the mapping. > BSD really needs to fix this deficiency, probably by adding a > method, similar to that for passing fd's, to pass region mappings > to other processes. Have you tried passing an fd attached to /dev/zero around and see if each process can mmap it separately and get shared memory? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03311 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:10:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (40-sweet.camalott.com [208.239.153.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03305 for ; Mon, 23 Nov 1998 11:10:14 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA62127; Mon, 23 Nov 1998 13:09:34 -0600 (CST) (envelope-from joelh) To: "Allen Smith" Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #314 References: <98Nov23.115714est.40343@border.alcanet.com.au> <9811222004.ZM2852@beatrice.rutgers.edu> From: Joel Ray Holveck Date: 23 Nov 1998 13:09:33 -0600 In-Reply-To: "Allen Smith"'s message of "Sun, 22 Nov 1998 20:04:20 -0500" Message-ID: <86k90mmdjm.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> (It's possible that pgp 5 may use /dev/random if it's >>>available; I haven't gotten around to downloading it yet and checking.) >> It appears it does - it definitely has the hooks. (Which would make it >> a complete circle - some of the ideas behind /dev/random come from pgp). > Ah, good. Now if I could only persuade the idiots at SGI to include > /dev/random et al... there are reasons that we're going with FreeBSD > for a firewall machine. Speaking of such things, what are some apps that use /dev/random, or at least have hooks to use a random device? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:15:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03651 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:15:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03645; Mon, 23 Nov 1998 11:15:50 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA27496; Mon, 23 Nov 1998 12:15:43 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd027361; Mon Nov 23 12:15:34 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA23348; Mon, 23 Nov 1998 12:15:06 -0700 (MST) From: Terry Lambert Message-Id: <199811231915.MAA23348@usr02.primenet.com> Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle To: mike@smith.net.au (Mike Smith) Date: Mon, 23 Nov 1998 19:15:06 +0000 (GMT) Cc: kaleb@ics.com, hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <199811210510.VAA00363@dingo.cdrom.com> from "Mike Smith" at Nov 20, 98 09:10:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I also now know why the de probe doesn't print out a message when the > > probe fails. Which is not to say that I think that's good. On the > > contrary, I think it's bad. C'est la vie. > > Printing out an error message when a PCI match fails would be stupid; > every PCI device is (currently) presented to every PCI driver until one > claims it. Printing a message when the match failed ("no, not for me") > would produce a useless spew of garbage. You need a pseudo-device at the end of the inquiry chain to catch id's that haven't been caught by the real drivers, and to print out a message ("PCI: no driver: id xxx ..."). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:29:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05537 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:29:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (40-sweet.camalott.com [208.239.153.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05530 for ; Mon, 23 Nov 1998 11:29:05 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA62221; Mon, 23 Nov 1998 13:28:42 -0600 (CST) (envelope-from joelh) To: Greg Lehey Cc: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: <19981123205619.Q430@freebie.lemis.com> From: Joel Ray Holveck Date: 23 Nov 1998 13:28:41 -0600 In-Reply-To: Greg Lehey's message of "Mon, 23 Nov 1998 20:56:19 +1030" Message-ID: <86iug6mcnq.fsf@detlev.UUCP> Lines: 34 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I need breakpoint on i/o in kernel >> How doing this in ddb, or exist another way ? > Well, the syntax is: > b
>
can be a hex value or an expression, possibly symbolic. Are > you asking which address to choose? Then you need to say what you > want to do. I think he's asking for an I/O breakpoint, not an address breakpoint; eg, break whenever a particular I/O port is accessed. I don't know what CPUs have instrumentation for this. To the best of my knowledge, neither DDB nor GDB have any hooks to handle this. (It might theoretically be possible with GDB using a semicomplex series of isteps and tests, but it would slow down your system possibly hundredfold.) I generally recommend another method of debugging than I/O breakpoints. If this is an ISA address, it's fairly simple to build a device to trigger an IRQ whenever a particular I/O port is accessed. Several of these exist. (It's also possible under some other busses, of course.) What are you trying to do? Are you debugging a driver, or a userland program using /dev/io, or what? We may be able to come up with a better way. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07085 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:38:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07079 for ; Mon, 23 Nov 1998 11:38:02 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA29676; Mon, 23 Nov 1998 12:38:01 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd029554; Mon Nov 23 12:37:50 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA25048; Mon, 23 Nov 1998 12:37:45 -0700 (MST) From: Terry Lambert Message-Id: <199811231937.MAA25048@usr02.primenet.com> Subject: Re: SYSV Semaphores & mmap problems To: joelh@gnu.org (Joel Ray Holveck) Date: Mon, 23 Nov 1998 19:37:45 +0000 (GMT) Cc: tlambert@primenet.com, DBECK@ludens.elte.hu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <86lnl2mdqs.fsf@detlev.UUCP> from "Joel Ray Holveck" at Nov 23, 98 01:05:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You can actually get mmap'ed memory that is as fast as SYSV SHM > > by mmap'ing anonymous memory off of fd -1, or off of an fd that > > is attached to /dev/zero. The problem with this is that there > > is no way to rendezvous this memory between processes, unless they > > are all descendents of the original process that did the mapping. > > BSD really needs to fix this deficiency, probably by adding a > > method, similar to that for passing fd's, to pass region mappings > > to other processes. > > Have you tried passing an fd attached to /dev/zero around and see if > each process can mmap it separately and get shared memory? No. But the /dev/zero device is not instanced per open, and the memory mapped is anonymous, not backed by /dev/zero, so it won't work. I think that it would be a long shot, in any case. One problem here is that /dev/zero, like all devices, is not notified of closes other than the last close, so everything you ever instanced would hang around until the last close; in other words, you would leak memory like a sieve in many common cases, even if everyone who had the mapping active went away, so long as *someone* had /dev/zero open. Actually, I think DG and PHK have both complained of this in the past and rumbled about doing something about close notification, but I don't remember seeing that happen, and I'm unfortunately too lazy to walk over to a 3.x machine and check. 8-). My gut feeling is that nothing was done, since all device drivers would need to be touched, which is about as popular as touching all the VFS implementations to effect an interface change in that area. Another possible approach is, if the region mappings within a process image are exposed seperately via /proc, open the region mapping for the anonymous region of the other program as a file, and then mmap it. This approach would be more work (IMO) than "enhancing" the descriptor passing mechanism. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:38:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07304 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:38:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (40-sweet.camalott.com [208.239.153.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07299; Mon, 23 Nov 1998 11:38:24 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA62289; Mon, 23 Nov 1998 13:38:08 -0600 (CST) (envelope-from joelh) To: Terry Lambert Cc: mike@smith.net.au (Mike Smith), kaleb@ics.com, hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle References: <199811231915.MAA23348@usr02.primenet.com> From: Joel Ray Holveck Date: 23 Nov 1998 13:38:07 -0600 In-Reply-To: Terry Lambert's message of "Mon, 23 Nov 1998 19:15:06 +0000 (GMT)" Message-ID: <86g1bamc80.fsf@detlev.UUCP> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I also now know why the de probe doesn't print out a message when the >>> probe fails. Which is not to say that I think that's good. On the >>> contrary, I think it's bad. C'est la vie. >> Printing out an error message when a PCI match fails would be stupid; >> every PCI device is (currently) presented to every PCI driver until one >> claims it. Printing a message when the match failed ("no, not for me") >> would produce a useless spew of garbage. > You need a pseudo-device at the end of the inquiry chain to catch > id's that haven't been caught by the real drivers, and to print > out a message ("PCI: no driver: id xxx ..."). That's catching the wrong set. kaleb wanted the to know the drivers without cards. You're giving us the set of cards without drivers. (This is also possibly a useful set, but not what kaleb wanted.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:45:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07862 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:45:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07852 for ; Mon, 23 Nov 1998 11:45:00 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA14766; Mon, 23 Nov 1998 12:44:53 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd014683; Mon Nov 23 12:44:47 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA25401; Mon, 23 Nov 1998 12:44:45 -0700 (MST) From: Terry Lambert Message-Id: <199811231944.MAA25401@usr02.primenet.com> Subject: Re: FreeBSD on i386 memory model To: Marius.Bendiksen@scancall.no (Marius Bendiksen) Date: Mon, 23 Nov 1998 19:44:45 +0000 (GMT) Cc: jdp@polstra.com, joelh@gnu.org, hackers@FreeBSD.ORG In-Reply-To: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> from "Marius Bendiksen" at Nov 23, 98 02:44:27 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" Not to mention that Intel has a not-very-publicized macrocell called the 486GX, which is a 486 without an FPU that you can get burnt on a piece of silicon with other macrocells like, oh, say, 2 10/100 ethernet interfaces, a couple of UARTS, a USART for T1, Frame Relay, or DSL, an integrated 8254, and maybe some EEPROM interface hardware... And they *don't* offer a Pentium macrocell for similar uses, since the Pentium is such a lunker. As a router or net connectivity ASIC, this would be hard to beat, expecially if you could throw 8M onto the thing and run a small UNIX-like OS there... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:46:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08074 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:46:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08067 for ; Mon, 23 Nov 1998 11:46:30 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA15141; Mon, 23 Nov 1998 12:46:15 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd015110; Mon Nov 23 12:46:11 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA25506; Mon, 23 Nov 1998 12:46:10 -0700 (MST) From: Terry Lambert Message-Id: <199811231946.MAA25506@usr02.primenet.com> Subject: Re: FreeBSD on i386 memory model To: jdp@polstra.com (John Polstra) Date: Mon, 23 Nov 1998 19:46:10 +0000 (GMT) Cc: Marius.Bendiksen@scancall.no, hackers@FreeBSD.ORG, joelh@gnu.org In-Reply-To: from "John Polstra" at Nov 23, 98 08:24:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No. Have you even read this thread? > > This thread is about whether to expend significant effort and > sacrifice significant elegance and maintainability in order to > _slightly_ _optimize_ system calls for 486 systems. It has nothing > to do with whether we support 486 systems or not. Sounds more like a libc compilation option anyway; we have to maintain the old entrypoint anyway, for binary backward compataibility. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 11:53:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08547 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 11:53:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08537 for ; Mon, 23 Nov 1998 11:53:09 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA18759; Mon, 23 Nov 1998 12:53:06 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd018726; Mon Nov 23 12:53:02 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA25806; Mon, 23 Nov 1998 12:52:58 -0700 (MST) From: Terry Lambert Message-Id: <199811231952.MAA25806@usr02.primenet.com> Subject: Re: Kernel threads To: andy@psn.ie (Andy Doran) Date: Mon, 23 Nov 1998 19:52:57 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Andy Doran" at Nov 23, 98 06:44:36 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello all! > I'm porting the NetBSD RAIDframe driver to FreeBSD at the moment, and I > need a little help. Firstly, is there any way to dynamically create and > destroy kernel threads like kthreads in NetBSD? I could create them > statically but it would require a lot of changes to the code. Two other > things; it is possible to guarantee that a psuedo device is attached > only after all other psuedo devices? Also, do I have to modify the kernel > to guarantee that my device can do it's RAID array setup as soon as all > disklabels and partition tables have been read, or is there some sort > of hook for this? Kernel threads, or kernel processes? Do all the threads have the same pid, or do they have different pid's? If you look at the code in /sys/kern/init_main.c, you will see that it is relatively trivial to start kernel processes. If you need to make them go away, then you need to look at the code for the "exit" and/or "kill" system calls. At one point in time, I wrote a compressing VFS stacking layer that operated on a per file basis. It started a "helper" process to do the compression and decompression so as to "cache" an decompressed image for a while after it was no longer used before compressing it again (no, this code won't run in an unmodified FreeBSD because of the VFS stacking problems FreeBSD has). It starts the helper process, and, if load requires it, starts up several of them and shuts them down. I was actually thinking of doing nfsd and nfsiod like this at some point. So not only is it possible, it's relatively easy, and there's code to do it already in the kernel. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:08:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10274 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:08:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rgate.ricochet.net (rgate1.ricochet.net [204.179.143.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10253 for ; Mon, 23 Nov 1998 12:08:56 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg-20425418-139.ricochet.net (mg-20425418-139.ricochet.net [204.254.18.139]) by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id OAA16413; Mon, 23 Nov 1998 14:08:13 -0600 (CST) Date: Mon, 23 Nov 1998 12:06:40 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: cnielsen@pobox.com To: Marius Bendiksen cc: John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> 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, 23 Nov 1998, Marius Bendiksen wrote: > >Of course we don't. Nobody who cares about speed is going to use a 486. > > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" The point being made is that if you're interested in high performance, you're not going to be using a 486 based server. You'll spend the extra money and buy a faster CPU. That does not mean FreeBSD won't support 486 based machines. What's the point in improving performance by a miniscule amount for an already slow CPU? It's a waste of developer time, IMHO. -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:09:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10318 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:09:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10286 for ; Mon, 23 Nov 1998 12:09:04 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA08069 for freebsd-hackers@FreeBSD.ORG; Mon, 23 Nov 1998 21:08:52 +0100 (CET) (envelope-from olli) Date: Mon, 23 Nov 1998 21:08:52 +0100 (CET) From: Oliver Fromme Message-Id: <199811232008.VAA08069@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote in list.freebsd-hackers: > when I got the original bootblocks working, > I experimented with loading the kernel all over the place.. > > you SHOULD just need to to LINK it to a different address As Mike Smith pointed out, it does not work. At least not with a -current kernel. Seems like the address is hardcoded in many places. > the old bootblocks would and the link address (in the aout header) > with 0xff0000 (or something similar) (0xf00000 ?) 0x00ffffff > and load there. > so you would link for 0xf0200000 to load at 2MB. That's what I tried (I think I explained that in the first posting). I linked the kernel for 0xf0400000, the bootloader loaded it to 0x00400000 (4 Mb, because 2 Mb would still be too low), and it did not work. I checked the kernel startup code in locore, KERNBASE and all that stuff, and I wasn't able to find the problem. I gave up when I found out that a different load address would not solve the problem anyway, so I wrote the modified rawboot loader which works. > (the link address was in the Makefile at the time.) It still is. And it's hardcoded in kern/link_aout.c, and probably in other files. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:16:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10976 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:16:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10967 for ; Mon, 23 Nov 1998 12:16:25 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4028.ime.net [209.90.195.38]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id PAA08829; Mon, 23 Nov 1998 15:15:11 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981123150953.00adf4a0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 23 Nov 1998 15:11:57 -0500 To: cnielsen@pobox.com, Marius Bendiksen From: Drew Baxter Subject: Re: FreeBSD on i386 memory model Cc: John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:06 PM 11/23/98 -0800, Christopher Nielsen wrote: >On Mon, 23 Nov 1998, Marius Bendiksen wrote: > >> >Of course we don't. Nobody who cares about speed is going to use a 486. >> >> Are you saying that we're going to say to people "Hey, FreeBSD is not >> intended to run on anything less than a Pentium, we don't wish to get >> involved with anything less, the people out there who're stuck with a 486 >> had better go support Linux instead?" > >The point being made is that if you're interested in high performance, >you're not going to be using a 486 based server. You'll spend the extra >money and buy a faster CPU. That does not mean FreeBSD won't support 486 >based machines. What's the point in improving performance by a miniscule >amount for an already slow CPU? It's a waste of developer time, IMHO. Well peoples versions of amounts and sizes are varying anyway. But people still actively use 486 machines for FreeBSD. I've heard in some cases machines as low as 386 class being used as low-cost Terminal Servers. So I wouldn't be one to pull them out of the loop just yet. Although the cost of equipment has gone down, some of us bought the Pentium Class machine for ourselves, and then used the old 486-100 for FreeBSD. Fortunately I was able to work in a place where I got to buy a PII-333 for the sole purpose of FreeBSD. Is it overkill? You bet your ass on it. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12234 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:29:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12201 for ; Mon, 23 Nov 1998 12:29:07 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA08250 for freebsd-hackers@FreeBSD.ORG; Mon, 23 Nov 1998 21:29:03 +0100 (CET) (envelope-from olli) Date: Mon, 23 Nov 1998 21:29:03 +0100 (CET) From: Oliver Fromme Message-Id: <199811232029.VAA08250@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote in list.freebsd-hackers: > We do need a more capable netboot replacement, and if Lanworks is > as responsive as they appear to be, then supporting their product > may be an easy route to satisfying this requirement. They are. They support only DOS and Windows "officially", but they have a UNIX person which answers to technical questions quite fast. They also send free (!) evaluation packages upon request. I ordered one, and it arrived two days later by UPS express (from Canada to Germany). BTW, Linux supports the Lanworks boot ROMs. It would be nice to have FreeBSD support for those ROMs, too, in one way or another. Even if we had a working netboot code, many people aren't able to make their own EPROMs. Especially those QPGA/FPGA (?) Flash memories required for many PCI cards (like the EtherExpress Pro/100) aren't easy to make on your own. Therefore people have to buy ready-made solutions, and it would be nice to be able to point at such a product and say "take this one, it works with FreeBSD". > It might be a reasonable solution to make something like this > available as a port; after all, the boot blocks are *expected* to > be somewhat out of sync with kernel development. > > Though I'd quite like to see it working with the new boot1/boot2 > and boot/loader code, in some form, now that Oliver has shown the > way. > > > Anyway, if someone needs some code to boot his/her FreeBSD box > > with a Lanworks ROM, I've put the "ramboot" stuff on the web: > > http://dorifer.heim3.tu-clausthal.de/~olli/ramboot.tar.gz > > Thanks. I've just fetched a copy. You're welcome. If people are really interested in this, I can create some documentation with step-by-step instructions (how to set up bootp and tftp servers, build the kernel, create the tftpboot image, etc.). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:35:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13351 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:35:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13340 for ; Mon, 23 Nov 1998 12:35:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA43270; Mon, 23 Nov 1998 12:36:47 -0800 (PST) To: Marius Bendiksen cc: John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-reply-to: Your message of "Mon, 23 Nov 1998 14:44:27 +0100." <3.0.5.32.19981123144427.00b40940@mail.scancall.no> Date: Mon, 23 Nov 1998 12:36:46 -0800 Message-ID: <43266.911853406@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Of course we don't. Nobody who cares about speed is going to use a 486. > > Are you saying that we're going to say to people "Hey, FreeBSD is not > intended to run on anything less than a Pentium, we don't wish to get > involved with anything less, the people out there who're stuck with a 486 > had better go support Linux instead?" I think you read this incorrectly. Read it again. "Anyone who cares about speed is not going to use a 486" - does anyone else fail to see the logic in that statement? To put it another way, if I have an application that requires speed, I'm not going to use a Coleco Color Computer no matter how many optimizations someone may have added for it. I'll use the right tool for the job. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 12:38:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13520 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:38:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13510 for ; Mon, 23 Nov 1998 12:37:55 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id VAA02360; Mon, 23 Nov 1998 21:37:28 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id WAA00688; Mon, 23 Nov 1998 22:28:20 GMT Message-ID: <19981123222820.65307@breizh.prism.uvsq.fr> Date: Mon, 23 Nov 1998 22:28:20 +0000 From: Nicolas Souchu To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: LPIP losing clock interrupts - need new spl...() call References: <199807192325.JAA05650@gsms01.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199807192325.JAA05650@gsms01.alcatel.com.au>; from Peter Jeremy on Mon, Jul 20, 1998 at 09:25:01AM +1000 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 20, 1998 at 09:25:01AM +1000, Peter Jeremy wrote: > >The solution (from my point of view) is a new spllpip() (or maybe >splplip()). Technically, this is easy, but I have a number of >stylistic questions: >- Should it go in i386/include/spl.h (since it's an spl()) or > i386/isa/lpt.c (the only place it's used)? I tend towards the > former. >- How should a mask of `all 1's except the hardclock() and statclock() > IRQs' be declared? Some options include: > >a) GENSPL(spllpip, cpl |= SWI_MASK | 0xfefe) > >b) #include > GENSPL(spllpip, cpl |= SWI_MASK | (HWI_MASK & ~(IRQ0 | IRQ8))) > >c) In an include file somewhere: > #define HWI_CLOCK 0 > #define HWI_STATCLOCK 8 > In i386/include/spl.h: > GENSPL(spllpip, cpl |= SWI_MASK | (HWI_MASK & ~((1 << HWI_CLOCK) | (1 << HWI_STATCLOCK)))) > And update i386/isa/clock.c to use the new macros. > >BTW, as far as I can tell, none of IF_DROP(), IF_ENQUEUE(), >IF_QFULL(), bpf_tap(), m_devget(), m_freem() or schednetisr() must be >called at non-zero spl's. Can anyone confirm this? > I could not find any reply to this mail in my archives. Did you send a PR? I'm about to look at ECP+DMA with a basic master/slave protocol. Did you do some work or do you have any idea about the suject? >Peter >-- >Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au >Alcatel Australia Limited >41 Mandible St Phone: +61 2 9690 5019 >ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Mon Nov 23 12:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13565 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:38:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13546 for ; Mon, 23 Nov 1998 12:38:03 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id VAA25936; Mon, 23 Nov 1998 21:37:34 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id WAA00682; Mon, 23 Nov 1998 22:25:34 GMT Message-ID: <19981123222534.13906@breizh.prism.uvsq.fr> Date: Mon, 23 Nov 1998 22:25:34 +0000 From: Nicolas Souchu To: Peter Brevik Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DMA boosted PPP via parallell port ..? References: <199811231535.QAA01781@father.ludd.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199811231535.QAA01781@father.ludd.luth.se>; from Peter Brevik on Mon, Nov 23, 1998 at 04:35:07PM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is a 2 month old message about it... >>>>> Alex Povolotsky wrote: >Does PPP over LPT utilize byte-oriented exchange with FIFO, possible with >parralel port in EPP mode? Definitely no in -stable. It uses nybble mode transfers with a laplink-style cable. I'm not sure if anyone has implemented it in the ppbus device in -current (last time I brought up the subject in -hackers, no-one seemed to be working on it). The major problem with byte-wide transfers is that the port becomes half-duplex (it can't simultaneously read and write). This means that you need to add appropriate hand-shaking to resolve (or prevent) contention. This probably means a changing the driver to master- slave. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 <<<<< On Mon, Nov 23, 1998 at 04:35:07PM +0100, Peter Brevik wrote: > > >Would be a good idea to implement the "LapLink" PPP as a ECP mode DMA driven >PPP ..? Of course! > >I think advantages would be definitly both speed and less cpu load. Yes, but developper load would increase considerably ;) > >Have a ECP specification at: > http://wave.campus.luth.se/~pb/comp/standards/ecpmode.htm > When do you start ;) > > >When I use PPP via Laplink as it now. The computer is not particular useful >when transfer is in progress.. ;( > This is also due to the spl level of the plip driver which is splhigh(). Moreover, the driver polls the port :) > /Peter > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Mon Nov 23 12:40:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13739 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 12:40:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fs.IConNet.NET (fs.IConNet.NET [199.173.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13733 for ; Mon, 23 Nov 1998 12:40:08 -0800 (PST) (envelope-from chuck@iconnet.net) Received: from ncc-ws03. (ncc-ws03.IConNet.NET [199.173.160.198]) by fs.IConNet.NET (IConNet Sendmail) with SMTP id PAA18027; Mon, 23 Nov 1998 15:40:02 -0500 (EST) Received: from localhost by ncc-ws03. (SMI-8.6/SMI-SVR4) id PAA20107; Mon, 23 Nov 1998 15:41:07 -0500 Date: Mon, 23 Nov 1998 15:41:07 -0500 (EST) From: chuck X-Sender: chuck@ncc-ws03 To: "Jordan K. Hubbard" cc: Marius Bendiksen , John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <43266.911853406@zippy.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 Yipes! The Color Computer was *NOT* from Coleco ;) It was a 6809-based box that could run a certain realtime UNIX-derivative (i.e., OS-9) rather well. Chuck Youse - Icon CMT Network Operations Center chuck@iconnet.net > application that requires speed, I'm not going to use a Coleco Color > Computer no matter how many optimizations someone may have added for > - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 13:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16896 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 13:05:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16890 for ; Mon, 23 Nov 1998 13:05:14 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Tue, 24 Nov 1998 08:04:35 +1100 Date: Tue, 24 Nov 1998 08:05:01 +1100 From: Peter Jeremy Subject: /dev/random usage To: joelh@gnu.org Cc: hackers@FreeBSD.ORG Message-Id: <98Nov24.080435est.40327@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: >Speaking of such things, what are some apps that use /dev/random, or >at least have hooks to use a random device? Going thru the 3.0-RELEASE source tree, the following programs all use srandomdev(3) - which gives you a pseudo-random sequence starting from a random point within the sequence: games/adventure, games/arithmetic, games/atc, games/backgammon, games/battlestar, games/bs, games/canfield, games/cribbage, games/fish, games/fortune, games/hack, games/hangman, games/larn, games/mille, games/phantasia, games/quiz, games/rain, games/random, games/robots, games/rogue, games/sail, games/snake, games/trek, games/worm, games/wump, sbin/fsirand, sbin/newfs, usr.bin/jot, usr.bin/passwd, usr.sbin/ppp, usr.sbin/pw Also arc4random(3) uses /dev/urandom for seeding it - and arc4random(3) is used by mktemp(3). Modifying an application to use /dev/random is not that difficult: 1) If pseudo-random numbers starting from a fairly random point within the sequence are adequate, and the application already uses random(3), just add a call to srandomdev(3) in place of srandom(3). 2) For a slightly better random starting point, it would be possible to rewrite srandomdev(3) to use /dev/random, waiting until sufficient key information became available. Having read the comments in the random(4) code, this is unlikely to provide any benefit over 1) above. 3) For truely random numbers, roll your own random(3) (or rand(3) or drand48(3) etc - the main differences are the type and range of the return value) implementation that uses /dev/random: long random() { static int rand_fd = -1; int wanted; long rnd; if (rand_fd < 0 && (rand_fd = open("/dev/random", O_RDONLY)) < 0) { perror("Failed to open /dev/random"); abort(); } wanted = sizeof(rnd); do { int len; len = read(rand_fd, ((char *)&rnd) + sizeof(rnd) - wanted, wanted); if (len < 0) { perror("read /dev/random failed"); abort(); } wanted -= len; if (wanted > 0) sleep(1); /* adjust as appropriate */ else return (rnd & 0x7fffffffL); } while (1); } Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 13:41:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20972 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 13:41:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20962 for ; Mon, 23 Nov 1998 13:41:09 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40335>; Tue, 24 Nov 1998 08:40:33 +1100 Date: Tue, 24 Nov 1998 08:40:58 +1100 From: Peter Jeremy Subject: Re: LPIP losing clock interrupts - need new spl...() call To: nsouch@teaser.fr Cc: hackers@FreeBSD.ORG Message-Id: <98Nov24.084033est.40335@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: >On Mon, Jul 20, 1998 at 09:25:01AM +1000, Peter Jeremy wrote: >>The solution (from my point of view) is a new spllpip() (or maybe >>splplip()). [deleted] >I could not find any reply to this mail in my archives. Did you send a PR? I didn't explicitly send a PR on this issue. There are a number of open PR's (i386/5698, kern/6099) covering LPIP problems. I don't recall seeing any reply either. >I'm about to look at ECP+DMA with a basic master/slave protocol. Did you >do some work or do you have any idea about the suject? I haven't done any further work. I have done a bit of thinking about how to go about handling contention, but didn't come to any firm conclusions. I only have one ECP machine, so I can't use an ECP protocol in any case. My only comment is that it would be useful if the protocol could also be used on a normal bi-directional parallel port. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 14:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24494 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 14:13:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from set.scient.com ([208.29.209.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA24488 for ; Mon, 23 Nov 1998 14:13:18 -0800 (PST) (envelope-from enkhyl@scient.com) Received: by set.scient.com; (5.65v4.0/1.3/10May95) id AA31647; Mon, 23 Nov 1998 14:12:22 -0800 Received: from somewhere by smtpxd Date: Mon, 23 Nov 1998 14:11:17 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: cnielsen@pobox.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <199811231952.MAA25806@usr02.primenet.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, 23 Nov 1998, Terry Lambert wrote: > it again (no, this code won't run in an unmodified FreeBSD because > of the VFS stacking problems FreeBSD has). It starts the helper Is the VFS stacking problem a result of the new VM implementation? What needs to be done to fix it? I'm curious because I was looking into writing an encrypting VFS layer, but I decided it was biting off more than I could chew when I discovered the VFS stacking problems. -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 14:33:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26583 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 14:33:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (48-sweet.camalott.com [208.239.153.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26571 for ; Mon, 23 Nov 1998 14:33:26 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA63181; Mon, 23 Nov 1998 16:33:12 -0600 (CST) (envelope-from joelh) To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: /dev/random usage References: <98Nov24.080435est.40327@border.alcanet.com.au> From: Joel Ray Holveck Date: 23 Nov 1998 16:33:10 -0600 In-Reply-To: Peter Jeremy's message of "Tue, 24 Nov 1998 08:05:01 +1100" Message-ID: <86emqum449.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Speaking of such things, what are some apps that use /dev/random, or >> at least have hooks to use a random device? > Going thru the 3.0-RELEASE source tree, the following programs all use > srandomdev(3) - which gives you a pseudo-random sequence starting from [snip] > Also arc4random(3) uses /dev/urandom for seeding it - and arc4random(3) > is used by mktemp(3). That's interesting. What about apps not in our tree? Mostly, I'm wondering what apps need large quantities of completely random numbers, and use our hooks to get it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 14:43:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27593 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 14:43:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27587 for ; Mon, 23 Nov 1998 14:43:00 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA20186; Mon, 23 Nov 1998 14:42:41 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA00812; Mon, 23 Nov 1998 14:42:28 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 23 Nov 1998 14:42:28 -0800 (PST) Message-Id: <199811232242.OAA00812@vashon.polstra.com> To: nate@mt.sri.com Subject: Re: Wrapping a function Newsgroups: polstra.freebsd.hackers In-Reply-To: <199811221425.HAA21510@mt.sri.com> References: <199811170517.WAA22627@mt.sri.com> <199811220702.CAA01604@rochester.rr.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811221425.HAA21510@mt.sri.com>, Nate Williams wrote: > > In recent gnu ld's: > > `--wrap SYMBOL' > > Use a wrapper function for SYMBOL. Any undefined reference to > > SYMBOL will be resolved to `__wrap_SYMBOL'. Any undefined > > reference to `__real_SYMBOL' will be resolved to SYMBOL. > > Cool! Does our ld do this? I doubt if the a.out one does. But it should work in the ELF linker. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 14:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28699 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 14:53:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28693 for ; Mon, 23 Nov 1998 14:53:54 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id OAA13825; Mon, 23 Nov 1998 14:50:43 -0800 (PST) (envelope-from marcs@znep.com) Date: Mon, 23 Nov 1998 14:50:42 -0800 (PST) From: Marc Slemko To: Dan Strick cc: hackers@FreeBSD.ORG Subject: Re: AMD/NFS problems with 3.0 In-Reply-To: <199811230032.QAA03103@math.berkeley.edu> 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, 22 Nov 1998, Dan Strick wrote: > (Please ignore my previous posting. I somehow neglected to rewrite the > temporary mail message file after editing it into this:) > > > > At first I though this might be related to these messages that went > > > to the log the first time I started amd: > > > > > > noconn option exists, and was turned OFF! (May cause NFS hangs > > > on some systems...) > > > > These are always printed out. I guess I should comment them out, or > > determine if we really can use the optimization. The comments in the > > code by the Columbia people are often out of date with respect to > > FreeBSD-CURRENT. > > I have often wondered what this was really about. Can someone explain? I have no idea what this is really about, but... > > At first I thought the issue was tcp versus udp, but this turns out to > be wrong. The issue seems to be if the BSD connect() system call is used > to associate the local BSD datagram (i.e. UDP) "socket" with the remote nfs > server datagram "socket". The alternative would be to skip the connect() > and specify the destination address every time a packet is sent and > examine the source address every time a packet is received. > > I don't really understand the issue here. UDP is essentially a > connectionless protocol. I don't understand the function of the BSD > connect() system call other than as a programming convenience. The issue is that if you don't do a connect(), then there is a lot more processing that that the kernel has to do. It doesn't have a pcb with info about the sender/recipient without a connect(), it has to figure out stuff about the source and destination each time, etc. See udp_output(), especially the in_pcb{connect|disconnect} calls that are done if an address is passed instead of being connect()ed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 15:06:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29865 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 15:06:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29860 for ; Mon, 23 Nov 1998 15:06:16 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA10023; Tue, 24 Nov 1998 09:35:44 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA60036; Tue, 24 Nov 1998 09:35:37 +1030 (CST) Message-ID: <19981124093537.R430@freebie.lemis.com> Date: Tue, 24 Nov 1998 09:35:37 +1030 From: Greg Lehey To: Joel Ray Holveck Cc: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: <19981123205619.Q430@freebie.lemis.com> <86iug6mcnq.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <86iug6mcnq.fsf@detlev.UUCP>; from Joel Ray Holveck on Mon, Nov 23, 1998 at 01:28:41PM -0600 WWW-Home-Page: http://www.lemis.com/~grog 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 Monday, 23 November 1998 at 13:28:41 -0600, Joel Ray Holveck wrote: >>> I need breakpoint on i/o in kernel >>> How doing this in ddb, or exist another way ? >> Well, the syntax is: >> b
>>
can be a hex value or an expression, possibly symbolic. Are >> you asking which address to choose? Then you need to say what you >> want to do. > > I think he's asking for an I/O breakpoint, not an address breakpoint; > eg, break whenever a particular I/O port is accessed. Ah, that could be. > I don't know what CPUs have instrumentation for this. All i386 architectures, in varying degrees. > To the best of my knowledge, neither DDB nor GDB have any hooks to > handle this. Correct. > (It might theoretically be possible with GDB using a semicomplex > series of isteps and tests, but it would slow down your system > possibly hundredfold.) The correct thing to do would be to implement I/O (and memory access) breakpoints, not kludge it. I look at it once, and the code turned my stomach. I once wrote a kernel debugger (for BSD/386) which implemented these features. I've been meaning to do it ever since for FreeBSD, but I still haven't got round to it. > I generally recommend another method of debugging than I/O > breakpoints. That's a workaround, not a solution. I/O breakpoints are really useful. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 15:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02888 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 15:34:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02879 for ; Mon, 23 Nov 1998 15:34:17 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po9.andrew.cmu.edu (8.8.5/8.8.2) id SAA10367; Mon, 23 Nov 1998 18:34:07 -0500 (EST) Received: via switchmail; Mon, 23 Nov 1998 18:34:07 -0500 (EST) Received: from unix14.andrew.cmu.edu via qmail ID ; Mon, 23 Nov 1998 18:33:03 -0500 (EST) Received: from unix14.andrew.cmu.edu via qmail ID ; Mon, 23 Nov 1998 18:33:02 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix14.andrew.cmu.edu.sun4m.54 via MS.5.6.unix14.andrew.cmu.edu.sun4_51; Mon, 23 Nov 1998 18:33:02 -0500 (EST) Message-ID: Date: Mon, 23 Nov 1998 18:33:02 -0500 (EST) From: Thomas Valentino Crimi To: Joel Ray Holveck , Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> References: <199811181842.KAA06180@apollo.backplane.com> <3.0.5.32.19981120103442.0099f460@mail.scancall.no> <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excerpts from FreeBSD-Hackers: 23-Nov-98 Re: FreeBSD on i386 memory .. by Marius Bendiksen@scancal >>It would require changing libc to read the kernel config file. Do we >>really want to mess with this? > >Unless it adds too much complexity, I'd say 'yes'. > >A major strength of FreeBSD is its speed. Increasing its speed, and ability >to specificially utilize your platform, would widen our lead. > Might it be better to add a new option to make.conf? If I'm following things correctly how would the libc makefile be able to dermine which config file is in use on the machine (read out out of the dmesgs?) What if the build machine is building world to then be exported to a slower machine for the installworld - something that I do very often and has obvious benefits. I definitely agree the hooks should exist, making it easilly tweekable is important, though. If it is made default an obvious warning should be printed out in make-world noting that the libc generated will not work on pre-Pentium/XXX machines. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 15:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05309 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 15:59:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from irc.pcnet.ro (irc.pcnet.ro [193.230.186.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05300 for ; Mon, 23 Nov 1998 15:59:47 -0800 (PST) (envelope-from fnicoles@pcnet.pcnet.ro) Received: from uucp1.pcnet.ro (uucp1.pcnet.ro [193.230.188.6]) by irc.pcnet.ro (8.9.1/8.8.5) with ESMTP id DAA29860 for ; Tue, 24 Nov 1998 03:11:17 +0200 Received: (from uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id BAA00074 for freebsd-hackers@FreeBSD.ORG; Tue, 24 Nov 1998 01:56:32 +0200 Received: (from nick@localhost) by nick.ro (8.8.8/8.8.8) id BAA00552 for freebsd-hackers@FreeBSD.ORG; Tue, 24 Nov 1998 01:46:27 +0200 (EET) (envelope-from nick) From: Florin Nicolescu Message-Id: <199811232346.BAA00552@nick.ro> Subject: Re: sever ide hdd crash To: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Date: Tue, 24 Nov 1998 01:46:27 +0200 (EET) X-OS: FreeBSD-2.2.7-RELEASE X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: application/pgp; format=text; x-action=sign Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hello, I posted about two weeks ago a possible kernel bug regarding the hdd crush I have experienced. I couldn't continue this discussion earlier, because I couldn't make my computer running until now. All the answers suggested something like >What you have there sounds like a plain, old-fashioned, simple, hard disk failure. Not >space aliens, not the ghost of Elvis trying to communicate with the living through your >hard drive, but what the spanish call "el seagate muerte" Your drive is dead, Jim. Maybe I was exaggerating a little (I had just lost my two month work in a quite big project), but it wasn't so simple. After two days, I changed my burned hdd (Quantum Fireball 4.3Gb) with a brand new IBM 4.3Gb. When I came home and start reinstalling the os, I just witness the second hdd crash. I changed again the hdd (also a IBM 4.3 Gb) together (as suggested by my supplier) with the ide atapi cdrom (the two crashes happened during cdrom copy) and with the cables. Again, trying to install my box, I start receiving messages like: wd0: interrupt timeout: wd0: status 50 error 0 wd0: interrupt timeout: wd0: status 50 error 1 I canceled everything. After rebooting, for about five minutes the hdd wasn't seen by bios, and after that was seen being 435Mb. After a low level format it was ok. Finally, I succeeded installing my box using a lpt Iomega ZIP drive (I got the dist copied on ZIP, than I put it on a dos partition, ...). With this occasion, I saw the famous blue error window of M$ Windows stating hdd write error during cdrom access. Now I changed everything in my computer (except the ATX case and the CPU) but I am seeing the same errors (the only thing that is quasi-the-same is the cdrom brand, the rest is brand new - I insisted in breaking the seal personally). Does anyone have any clue about this? I traced some previous threads about wd timeouts, but they were no help. The only chance to have it accessing the cdrom for more that 1 minute (but finally get the same error) is to disable both UDMA and PIO mode for wd and wcd. Thanks, Florin. BTW: I don't belive in aliens nor in ghosts or vampires :) - -- - ------------------------------------------------------------------ | Florin-Nicolae Nicolescu | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | - ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | - ------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNlnzzW95n9Jm9dehAQFO5QQAt/RnQ1HnoLe+k9rrpL11R42o9cWMdkfZ Y90dachRluk2o+n/JjTlxD9UIQv6u3NmKxhTH9eU5qEsPLO4kFp46+JEYkcSMF0o PkDl9XS0ZeN0V6C6xlyXvlyfUuKBsYopmT701m8irwM629p3cxIuH1fUhARoKBgZ 77AGQWhD/6w= =QTWt -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 16:03:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06097 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:03:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06083 for ; Mon, 23 Nov 1998 16:03:06 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA08453 for ; Mon, 23 Nov 1998 15:52:52 -0800 (PST) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdrJ8450; Mon Nov 23 23:52:46 1998 Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id PAA38750 for freebsd-hackers@FreeBSD.ORG; Mon, 23 Nov 1998 15:52:02 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199811232352.PAA38750@whistle.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811232029.VAA08250@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Nov 23, 98 09:29:03 pm" To: freebsd-hackers@FreeBSD.ORG Date: Mon, 23 Nov 1998 15:52:02 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (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 Oliver Fromme writes: | Robert Nordier wrote in list.freebsd-hackers: | > We do need a more capable netboot replacement, and if Lanworks is | > as responsive as they appear to be, then supporting their product | > may be an easy route to satisfying this requirement. | | They are. They support only DOS and Windows "officially", but | they have a UNIX person which answers to technical questions | quite fast. They also send free (!) evaluation packages upon | request. I ordered one, and it arrived two days later by UPS | express (from Canada to Germany). | | BTW, Linux supports the Lanworks boot ROMs. | | It would be nice to have FreeBSD support for those ROMs, too, | in one way or another. Even if we had a working netboot code, | many people aren't able to make their own EPROMs. Especially | those QPGA/FPGA (?) Flash memories required for many PCI cards | (like the EtherExpress Pro/100) aren't easy to make on your | own. Actually it is pretty easy to do it for the Intel cards since they is a utility from IBM that programs the flash boot rom on Intel cards. Various methods are at: http://www.slug.org.au/etherboot/ or archived in the netboot mailing list. Also it may be worth looking at: http://www.slug.org.au/etherboot/nilo/ I've hacked Etherboot to load FreeBSD/aout again and now to load FreeBSD/elf. I like the menu-options so I can load various things from the client. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 16:07:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07761 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:07:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07754 for ; Mon, 23 Nov 1998 16:07:01 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA04135; Mon, 23 Nov 1998 16:06:58 -0800 (PST) Message-ID: <19981123160658.F2807@Alameda.net> Date: Mon, 23 Nov 1998 16:06:58 -0800 From: Ulf Zimmermann To: Florin Nicolescu , FreeBSD-hackers Subject: Re: sever ide hdd crash Reply-To: ulf@Alameda.net References: <199811232346.BAA00552@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811232346.BAA00552@nick.ro>; from Florin Nicolescu on Tue, Nov 24, 1998 at 01:46:27AM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 01:46:27AM +0200, Florin Nicolescu wrote: > Hello, > > I posted about two weeks ago a possible kernel bug regarding the hdd crush I have > experienced. I couldn't continue this discussion earlier, because I couldn't make my > computer running until now. > All the answers suggested something like > >What you have there sounds like a plain, old-fashioned, simple, hard disk failure. Not > >space aliens, not the ghost of Elvis trying to communicate with the living through your > >hard drive, but what the spanish call "el seagate muerte" Your drive is dead, Jim. > Maybe I was exaggerating a little (I had just lost my two month work in a quite big > project), but it wasn't so simple. After two days, I changed my burned hdd (Quantum > Fireball 4.3Gb) with a brand new IBM 4.3Gb. When I came home and start reinstalling the > os, I just witness the second hdd crash. I changed again the hdd (also a IBM 4.3 Gb) > together (as suggested by my supplier) with the ide atapi cdrom (the two crashes > happened during cdrom copy) and with the cables. Again, trying to install my box, I > start receiving messages like: > wd0: interrupt timeout: > wd0: status 50 error 0 > wd0: interrupt timeout: > wd0: status 50 error 1 > I canceled everything. After rebooting, for about five minutes the hdd wasn't seen by > bios, and after that was seen being 435Mb. After a low level format it was ok. > Finally, I succeeded installing my box using a lpt Iomega ZIP drive (I got the dist > copied on ZIP, than I put it on a dos partition, ...). With this occasion, I saw the > famous blue error window of M$ Windows stating hdd write error during cdrom access. > Now I changed everything in my computer (except the ATX case and the CPU) but I am > seeing the same errors (the only thing that is quasi-the-same is the cdrom brand, the > rest is brand new - I insisted in breaking the seal personally). > Does anyone have any clue about this? I traced some previous threads about wd timeouts, > but they were no help. > The only chance to have it accessing the cdrom for more that 1 minute (but finally get > the same error) is to disable both UDMA and PIO mode for wd and wcd. I would suggest to swap the Power supply of the case. What you might have could be an unstable 12V power source for the harddrive. > > Thanks, > Florin. > > BTW: I don't belive in aliens nor in ghosts or vampires :) > > -- > ------------------------------------------------------------------ > | Florin-Nicolae Nicolescu | > | University of Bucharest, Faculty of Mathematics | > | Bucharest,Romania | > ------------------------------------------------------------------ > | Friends don't let friends use Windows. | > | Double your hard drive space instantly! Delete Windows! | > ------------------------------------------------------------------ > > > 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 Mon Nov 23 16:13:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08604 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:13:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wolf.com (ns1.wolf.com [207.137.58.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA08599 for ; Mon, 23 Nov 1998 16:13:57 -0800 (PST) (envelope-from dan@wolf.com) Received: (qmail 11317 invoked by uid 100); 24 Nov 1998 00:22:58 -0000 Message-ID: <19981123162257.A8896@wolf.com> Date: Mon, 23 Nov 1998 16:22:57 -0800 From: Dan Mahoney To: Florin Nicolescu , FreeBSD-hackers Subject: Re: sever ide hdd crash References: <199811232346.BAA00552@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199811232346.BAA00552@nick.ro>; from Florin Nicolescu on Tue, Nov 24, 1998 at 01:46:27AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I normally hesitate to recommend such low-level steps, but my next recommendation would be to get your hands on a good digital voltmeter and look at the output of the PC power supply. If you have an unused disk-drive power connector, monitor the voltages there while the machine is running - preferably, while it is performing the same type of operation that has been leading up to system failures. Look at the DC voltage levels, and look also at any AC component that might be present. If you have tried swapping out everything except the case and the CPU, then that might be the problem - since the power supply stays with the case. BUT BE CAREFUL! Doing anything with the system running is risky, and messing around with the power connectors while power is applied makes it very easy to toast your system if you jumper the wrong points together. > I posted about two weeks ago a possible kernel bug regarding the hdd crush I have > experienced. I couldn't continue this discussion earlier, because I couldn't make my > computer running until now. > All the answers suggested something like > >What you have there sounds like a plain, old-fashioned, simple, hard disk failure. Not > >space aliens, not the ghost of Elvis trying to communicate with the living through your > >hard drive, but what the spanish call "el seagate muerte" Your drive is dead, Jim. > Maybe I was exaggerating a little (I had just lost my two month work in a quite big > project), but it wasn't so simple. After two days, I changed my burned hdd (Quantum > Fireball 4.3Gb) with a brand new IBM 4.3Gb. When I came home and start reinstalling the > os, I just witness the second hdd crash. I changed again the hdd (also a IBM 4.3 Gb) > together (as suggested by my supplier) with the ide atapi cdrom (the two crashes > happened during cdrom copy) and with the cables. Again, trying to install my box, I > start receiving messages like: > wd0: interrupt timeout: > wd0: status 50 error 0 > wd0: interrupt timeout: > wd0: status 50 error 1 > I canceled everything. After rebooting, for about five minutes the hdd wasn't seen by > bios, and after that was seen being 435Mb. After a low level format it was ok. > Finally, I succeeded installing my box using a lpt Iomega ZIP drive (I got the dist > copied on ZIP, than I put it on a dos partition, ...). With this occasion, I saw the > famous blue error window of M$ Windows stating hdd write error during cdrom access. > Now I changed everything in my computer (except the ATX case and the CPU) but I am > seeing the same errors (the only thing that is quasi-the-same is the cdrom brand, the > rest is brand new - I insisted in breaking the seal personally). > Does anyone have any clue about this? I traced some previous threads about wd timeouts, > but they were no help. > The only chance to have it accessing the cdrom for more that 1 minute (but finally get > the same error) is to disable both UDMA and PIO mode for wd and wcd. > > Thanks, > Florin. > > BTW: I don't belive in aliens nor in ghosts or vampires :) > > -- > ------------------------------------------------------------------ > | Florin-Nicolae Nicolescu | > | University of Bucharest, Faculty of Mathematics | > | Bucharest,Romania | > ------------------------------------------------------------------ > | Friends don't let friends use Windows. | > | Double your hard drive space instantly! Delete Windows! | > ------------------------------------------------------------------ > > > 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 Nov 23 16:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09793 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:25:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09785 for ; Mon, 23 Nov 1998 16:25:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id QAA20612; Mon, 23 Nov 1998 16:25:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA01171; Mon, 23 Nov 1998 16:25:37 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811231852.LAA21705@usr02.primenet.com> Date: Mon, 23 Nov 1998 16:25:37 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Terry Lambert Subject: Re: Would this make FreeBSD more secure? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You need to look at Bugtraq as well I did already. > Also, I think the point of PAM is to let people use modules other > than the ones that we use... so that argument is rather pointless. What argument? I have no intention of taking responsibility for bugs in modules that other people wrote. If you want to use them, it's up to you to convince yourself that they're OK. > Here is a bug that will be common in network applications like ftpd > linked to use PAM: > > http://geek-girl.com/bugtraq/1998_1/0111.html This is a bug in the Solaris ftpd, and has nothing to do with PAM. > I don't know if you are using the rhost module, but if so, this may > be relevent: I didn't use any of the Linux modules. > Also, PAM can become vulnerable based on libc implementation, since > it is a consumer of libc; here's one example: > > http://geek-girl.com/bugtraq/1997_2/0228.html This is about a Linux libc bug, combined with a stupid blunder by a Linux system "administrator". Anyway, everything that is linked with libc is vulnerable to bugs in it. PAM is not special in that sense. > Also, is our qpopper port still vulnerable to: > > http://geek-girl.com/bugtraq/1998_2/0657.html > > ??? I have no idea. What is the relevance to PAM? --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 16:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10298 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:33:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10292 for ; Mon, 23 Nov 1998 16:33:40 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40372>; Tue, 24 Nov 1998 11:32:53 +1100 Date: Tue, 24 Nov 1998 11:31:54 +1100 From: Peter Jeremy Subject: Re: /dev/random usage To: joelh@gnu.org Cc: hackers@FreeBSD.ORG Message-Id: <98Nov24.113253est.40372@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >That's interesting. What about apps not in our tree? ssh, ncpfs and pgp5 that I have. I don't know about SSLeay, but that is another obvious candidate. > Mostly, I'm >wondering what apps need large quantities of completely random >numbers, and use our hooks to get it. I think few apps need large quantities of random numbers. The main one I can think of is creating one-time pads. Pseudo-random numbers are adequate for most non-crypto applications, and most crypto applications require relatively small quantities of true randomness (usually only for key generation). This is good since generating large quantities of random numbers is difficult (I'm not sure what the rate of entropy creation within /dev/random is for a typical system). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 16:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10658 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:36:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10653 for ; Mon, 23 Nov 1998 16:36:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA44638; Mon, 23 Nov 1998 16:37:31 -0800 (PST) To: Drew Baxter cc: cnielsen@pobox.com, Marius Bendiksen , John Polstra , joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-reply-to: Your message of "Mon, 23 Nov 1998 15:11:57 EST." <4.1.19981123150953.00adf4a0@genesis.ispace.com> Date: Mon, 23 Nov 1998 16:37:31 -0800 Message-ID: <44635.911867851@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well peoples versions of amounts and sizes are varying anyway. But people > still actively use 486 machines for FreeBSD. I've heard in some cases This topic is diverging. I thought this was a performance discussion. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 16:39:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10894 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 16:39:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from irc.pcnet.ro (irc.pcnet.ro [193.230.186.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10879 for ; Mon, 23 Nov 1998 16:39:47 -0800 (PST) (envelope-from fnicoles@pcnet.pcnet.ro) Received: from uucp1.pcnet.ro (uucp1.pcnet.ro [193.230.188.6]) by irc.pcnet.ro (8.9.1/8.8.5) with ESMTP id DAA30873; Tue, 24 Nov 1998 03:51:14 +0200 Received: (from uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id CAA02419; Tue, 24 Nov 1998 02:35:19 +0200 Received: (from nick@localhost) by nick.ro (8.8.8/8.8.8) id CAA01113; Tue, 24 Nov 1998 02:28:24 +0200 (EET) (envelope-from nick) From: Florin Nicolescu Message-Id: <199811240028.CAA01113@nick.ro> Subject: Re: sever ide hdd crash In-Reply-To: <19981123162257.A8896@wolf.com> from Dan Mahoney at "Nov 23, 98 04:22:57 pm" To: dan@wolf.com (Dan Mahoney) Date: Tue, 24 Nov 1998 02:28:24 +0200 (EET) Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) X-OS: FreeBSD-2.2.7-RELEASE X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: application/pgp; format=text; x-action=sign Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- > I normally hesitate to recommend such low-level steps, > but my next recommendation would be to get your hands > on a good digital voltmeter and look at the output of > the PC power supply. If you have an unused disk-drive > power connector, monitor the voltages there while the > machine is running - preferably, while it is performing > the same type of operation that has been leading up to > system failures. > > Look at the DC voltage levels, and look also at any AC > component that might be present. If you have tried > swapping out everything except the case and the CPU, > then that might be the problem - since the power > supply stays with the case. > > BUT BE CAREFUL! Doing anything with the system running > is risky, and messing around with the power connectors > while power is applied makes it very easy to toast your > system if you jumper the wrong points together. > What is the accepted variance of the voltage (in mv)? I think I will take the chance as soon as I get one VU meter. Thanks. Florin - -- - ------------------------------------------------------------------ | Florin-Nicolae Nicolescu | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | - ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | - ------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNln9mG95n9Jm9dehAQEKWAQAoP8kjMyGOwPhJ6zc66G35q4l1bkshpbH f33nVr+whnNwHbvwQYFdZZxfotRkuJB0siockQ26aD0gcWexhAApGd3rLW/jpd/C IQHp+1isSRLAuqCdWUoyaEIjVGbDuHkBPugL8sqXyO89UCbhK8/KFdwQ31lUsY5h pndEz2TxlQo= =N+SG -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 17:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17244 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 17:47:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17239 for ; Mon, 23 Nov 1998 17:47:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id RAA11543; Mon, 23 Nov 1998 17:47:24 -0800 (PST) (envelope-from dillon) Date: Mon, 23 Nov 1998 17:47:24 -0800 (PST) From: Matthew Dillon Message-Id: <199811240147.RAA11543@apollo.backplane.com> To: Terry Lambert Cc: joelh@gnu.org (Joel Ray Holveck), tlambert@primenet.com, DBECK@ludens.elte.hu, freebsd-hackers@FreeBSD.ORG Subject: Re: SYSV Semaphores & mmap problems References: <199811231937.MAA25048@usr02.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The difference between mmap() and SysV shared memory isn't so bad. The mmap()'d file will basically get synced every 30 seconds or so by the syncer daemon. madvise() can be used to pre-fault any pages already in the cache. I think all that is needed is a way to flag a file so the syncer doesn't touch it under normal circumstances, instead allowing its pages to be synced by normal paging activity. You can then madvise(... MADV_FREE) the pages after you are through with the shared memory segment to throw them away. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 18:14:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19802 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 18:14:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mitnick.cudenver.edu (dialinl3-7.cudenver.edu [132.194.10.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19782 for ; Mon, 23 Nov 1998 18:14:53 -0800 (PST) (envelope-from alex@MSCD.EDU) Received: from localhost (alex@localhost) by mitnick.cudenver.edu (8.9.1/8.9.1) with SMTP id TAA01890; Mon, 23 Nov 1998 19:14:34 -0700 (MST) Date: Mon, 23 Nov 1998 19:14:27 -0700 (MST) From: SirSparc To: putra cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD 2.0.5 In-Reply-To: <365943F3.2B6DC314@livjm.ac.uk> 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 -----BEGIN PGP SIGNED MESSAGE----- Hello, this url was given by someone at freebsd-quesions. http://www.itworks.com.au/~gavin/FBSDsites.php3 and the direct links to 2.0.5-R: ftp://ftp5.br.FreeBSD.org/pub/FreeBSD/2.0.5-RELEASE ftp://ftp2.internat.freebsd.org/pub/FreeBSD/2.0.5-RELEASE ftp://ftp.internat.freebsd.org/pub/FreeBSD/2.0.5-RELEASE ftp://ftp2.za.freebsd.org/pub/FreeBSD/2.0.5-RELEASE ftp://ftp.za.freebsd.org/pub/FreeBSD/2.0.5-RELEASE Hope it helps, comes in handy for those of us too lazy to upgrade internal servers that have been running great for years:) On Mon, 23 Nov 1998, putra wrote: %Hi, I'm Putra from Liverpool John Moores University. I'm a researcher %and one of my project uses FreeBSD 2.0.5 release. Do still have the copy %for this version. It is very important for me in order to finish my %course. I hope you dont mind, please. % %Putra Sumari %Room 706 %Distributed Multimedia Group %School of Computing and Mathematical Sciences %University of Liverpool %Byrom St. Liverpool L3 3AF. %Tel : +44(0)151-231-2089 %Fax : +44(0)151-207-4594 % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-hackers" in the body of the message % -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNloWiAZbpLqArVSVAQEzJwP/YCVUlsS/IcvDZc/j1CSd0FUDJ8FE7frl UGoP2rayQfeGWxA8BepBg17yj4JXawt5RxvTR6fnR52Q2rrBisXGfXGSPd7+cxPN KUZEB9ki7yeIJw9BL+EQo260GMPr+E19epZ5F8J+jUIslmcnMBlFl4gF7H7F4W5W HIPePXzgze4= =QIO9 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 18:29:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21119 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 18:29:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21108 for ; Mon, 23 Nov 1998 18:29:35 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id PAA12114; Tue, 24 Nov 1998 15:29:21 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id PAA16928; Tue, 24 Nov 1998 15:29:20 +1300 (NZDT) Message-ID: <19981124152920.D16629@clear.co.nz> Date: Tue, 24 Nov 1998 15:29:20 +1300 From: Joe Abley To: Robert Withrow , Dan Strick Cc: obrien@NUXI.com, hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: AMD/NFS problems with 3.0 References: <199811230032.QAA03103@math.berkeley.edu> <199811231358.IAA07151@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811231358.IAA07151@spooky.rwwa.com>; from Robert Withrow on Mon, Nov 23, 1998 at 08:58:35AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 23, 1998 at 08:58:35AM -0500, Robert Withrow wrote: > > dan@math.berkeley.edu said: > :- I have not yet noticed an NFS server responding through a different > :- port#. > > I have (buggy ?) sunos 4.1.4 servers that do that. > > I havn't yet sniffed the wire to see if that is the source of my > current NFS problems. Everthing here is now switched 100 to the > desktop through a Baystack 350. I have to get a hub to put the > client system and the sniffer on so I can capture the NFS session... > (And, it might be that the Baystack is a problem too, for all I know...). The BayStack 350T supports port mirroring (I think Bay calls it "conversation steering"). You should be able to configure a monitor port which contains combined traffic from up to two other ports (depending on port load, obviously). If you can't see the menu option to set it up, check you've got a recent firmware image. I've done this lots of times - and it's definitely less hassle than messing about with hubs, since I don't have to leave my desk :) Joe -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Communications Ltd http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 18:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21921 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 18:41:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21915 for ; Mon, 23 Nov 1998 18:41:08 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA248495197; Mon, 23 Nov 1998 21:39:57 -0500 Date: Mon, 23 Nov 1998 21:39:56 -0500 (EST) From: Bill Fumerola To: Joe Abley Cc: Robert Withrow , hackers@FreeBSD.ORG Subject: Re: AMD/NFS problems with 3.0 In-Reply-To: <19981124152920.D16629@clear.co.nz> 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, 24 Nov 1998, Joe Abley wrote: > The BayStack 350T supports port mirroring (I think Bay calls it "conversation > steering"). You should be able to configure a monitor port which contains > combined traffic from up to two other ports (depending on port load, > obviously). My BayStack 450's call it port mirroring. > I've done this lots of times - and it's definitely less hassle than messing > about with hubs, since I don't have to leave my desk :) I keep a spare NIC in my Win95 workstatsion just for NetXray, though as sson as Ethereal supports as many protocols as NetXray, I can be assured I'll be switching. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 19:29:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27030 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 19:29:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27019 for ; Mon, 23 Nov 1998 19:29:04 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id WAA26688; Mon, 23 Nov 1998 22:28:58 -0500 (EST) (envelope-from luoqi) Date: Mon, 23 Nov 1998 22:28:58 -0500 (EST) From: Luoqi Chen Message-Id: <199811240328.WAA26688@lor.watermarkgroup.com> To: cnielsen@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 23 Nov 1998, Terry Lambert wrote: > > > it again (no, this code won't run in an unmodified FreeBSD because > > of the VFS stacking problems FreeBSD has). It starts the helper > > Is the VFS stacking problem a result of the new VM implementation? What > needs to be done to fix it? I'm curious because I was looking into writing > an encrypting VFS layer, but I decided it was biting off more than I could > chew when I discovered the VFS stacking problems. > We need a cache manager (as described in Heidemann's paper) to ensure coherence between vm objects hanging off vnodes from upper and lower layer. For a transparent layer (no data translation, such as null/union/umap), maybe we could do without the cache manager by implementing vm object sharing between upper and lower vnodes. But for a data translation layer, a cache manager is definitely required. -lq > -- > Christopher Nielsen > Scient: The eBusiness Systems Innovator > > cnielsen@scient.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 19:50:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29190 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 19:50:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (47-sweet.camalott.com [208.239.153.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29160 for ; Mon, 23 Nov 1998 19:50:12 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id VAA64166; Mon, 23 Nov 1998 21:49:47 -0600 (CST) (envelope-from joelh) To: Greg Lehey Cc: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: <19981123205619.Q430@freebie.lemis.com> <86iug6mcnq.fsf@detlev.UUCP> <19981124093537.R430@freebie.lemis.com> From: Joel Ray Holveck Date: 23 Nov 1998 21:49:46 -0600 In-Reply-To: Greg Lehey's message of "Tue, 24 Nov 1998 09:35:37 +1030" Message-ID: <86af1hn411.fsf@detlev.UUCP> Lines: 63 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't know what CPUs have instrumentation for this. > All i386 architectures, in varying degrees. Since I wrote that message, I dragged out my Intel docs so I could follow along with the rest of the class. >> (It might theoretically be possible with GDB using a semicomplex >> series of isteps and tests, but it would slow down your system >> possibly hundredfold.) > The correct thing to do would be to implement I/O (and memory access) > breakpoints, not kludge it. Memory access breakpoints are already implemented: watch addr,size Set a watchpoint for a region. Execution stops when an attempt to modify the region occurs. The size argument defaults to 4. If you specify a wrong space address, the request is rejected with an error message. Warning: Attempts to watch wired kernel memory may cause unrecoverable error in some systems such as i386. Watchpoints on user addresses work best. > I look at it once, and the code turned my stomach. Was this for kdb, ddb, or kgdb? I don't know much about ddb. Going over its code, it appears that ddb uses the VMM to handle watchpoints instead of using the processor's debugging instrumentation. (This is fine with me, and more portable to boot.) A quick review doesn't show any major problems implementing I/O breakpoints. Is there any reason that the same entry mechanism to enter ddb on a page fault couldn't also enter ddb on a debug exception? If that's the case, then it would appear that all we need to do is to write something to manage four I/O breakpoints and we've got the basics. gdb already has some instrumentation for hardware breakpoints; it may be extendable to allow for this sort of thing. I haven't looked into that. >> I generally recommend another method of debugging than I/O >> breakpoints. > That's a workaround, not a solution. I/O breakpoints are really > useful. Yes, but they are also frequently misused. I myself used to be a frequent debugger abuser, and would rely on the debugger instead of thinking about the driver and knowing what's going on wrong. I didn't say that I/O breakpoints don't have their time and place, but they can also be misused easily. And now I hope that I'm not starting a holy war. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 20:34:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03061 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 20:34:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03051 for ; Mon, 23 Nov 1998 20:34:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA12209; Mon, 23 Nov 1998 20:33:57 -0800 (PST) (envelope-from dillon) Date: Mon, 23 Nov 1998 20:33:57 -0800 (PST) From: Matthew Dillon Message-Id: <199811240433.UAA12209@apollo.backplane.com> To: Luoqi Chen Cc: cnielsen@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads References: <199811240328.WAA26688@lor.watermarkgroup.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> needs to be done to fix it? I'm curious because I was looking into writing :> an encrypting VFS layer, but I decided it was biting off more than I could :> chew when I discovered the VFS stacking problems. :> :We need a cache manager (as described in Heidemann's paper) to ensure :coherence between vm objects hanging off vnodes from upper and lower layer. :For a transparent layer (no data translation, such as null/union/umap), :maybe we could do without the cache manager by implementing vm object sharing :between upper and lower vnodes. But for a data translation layer, a cache :manager is definitely required. : :-lq Ok, I'm going to put forth a general wide-view infomercial for general discussion. I am definitely *not* planning on implementing this here, it would be too much work for one person (or even two), but it's basically something I have been working on for one of my side OS projects. What we really need to do is integrate the VFS layer abstraction into the buffer cache and get rid of all the baggage in the buffer pointer (bp) layer. That is, abstract the backing store out of the core vm_page_t structure and put it into a vm_cache_t type of structure. We then preallocate the vm_page_t's as we currently do (one per physical page of memory), and preallocate the smaller vm_cache_t backing store reference structures as well. For example, preallocate 4x the number of vm_cache_t's as we have vm_page_t's. We get rid of the KVM maps entirely and instead do a simple direct map of all physical memory into KVM (John doesn't like this part because it limits the amount of physical memory to the KVM address space, typically 2GB on a 32 bit machine). Devices drivers would no longer use consolidated KVM buffers (e.g. the filesystem code would make distinctions on page boundries when indexing into filesystem buffers rather then filesystem block boundries. Raw disk units would consolidate disk I/O into page-sized blocks, which they pretty much do anyway). Each vm_cache_t would contain a reference to an underlying vm_page_t, the backing store abstraction (vnode, block#), a lock, and a chain to other vm_cache_t's sharing the same page. vm_cache_t's are mostly throw-away structures, but with strict unwinding rules to maintain cache consistancy. For example, the vm_cache_t representing the ultimate physical backing store of an object can not be deleted until vm_cache_t's higher in the chain (referencing the same page) are deleted, but vm_cache_t's in the middle of a stacking chain might very well be deletable if they can be resynthesized later. It also becomes trivial to break and unify chains depending. For example, a 'hole' or 'fragment' in a file that grows into a page can be unified with the disk backing store for the file when the full block is allocated by the filesystem, but can remain detached until then. Here are the disadvantages: * no buffer concatenation in KVM, i.e. if the filesystem block size is 8K, the coding of the filesystem device must still lookup data in the cache on page boundries. * All of physical memory must be mapped into KVM for easy reference. (typically gives us a 2G limit on a 32 bit cpu). Or most of it, anyway. * KVM maps go away entirely or almost entirely (We might have to keep a few around to optimize memory management of some of the larger kernel structures). * vm_cache_t eats wired memory. If it is a 64 byte structure and we have four for each page of physical memory, we eat 6.25% of physical memory for our preallocate vm_cache_t array. With a 32 byte structure size we eat 3.125% of physical memory. ( Even so I would still recommend preallocation in order to eek out extreme performance). Here are the advantages: * supervisor code does not have to touch UVM at all, which means it doesn't have to touch page tables for kernel operations (except to map/unmap things for user processes). i.e. there is no hardware MMU interaction required for kernel-mode operations. * no KVM maps need be maintained for kernel memory pools, buffer pointers, or other related items. We would still need them for the per-process kernel stack and a few of the larger kernel structures. * breaking and consolidating VFS stacks is trivialized. * physical devices are well and truely abstracted into a VNode with no loss in performance. * most of the kernel level page and VM locking issues as related to manipulation of kernel data goes away. * remaining locking issues become more clear. * vm_cache_t structures can be used to temporarily cluster backing store operations, including swap operations, delaying consolidation of pages into swap structures. * 'dummy' vnodes can be used to abstract memory maps almost trivially. * intermediate short-lasting vm_cache_t's can be used to handle simple mappings, such as a disk stripe. More complex mappings such as RAID5 and MIRRORing would require the vm_cache_t to remain in the chain in order to handle fail-over, parity consolidation, and other RAID features. * If you thought page tables were throw away before, they are *truely* throwaway and abstracted now. In fact, it is even theoretically possible to share pagetables across like-maps (e.g. 100 processes mmap()ing shared+rw or ro the same file and start poking at it need not cost more then one common pagetable). The biggest operational feature is that when you lookup a page in the buffer cache, you are now looking up an arbitrary (vnode,block#) pair and getting a vm_cache_t in return. And when I mean 'arbitrary vnode', I really mean 'arbitrary vnode'. This can be inclusive of a pseudo vnode representing a memory map for a process, for example. In fact, all the side effects both synchronous and asynchronous wind up being encapsulated in the buffer cache code with very little additional complexity. The cache routines devolve down into (taking from some of the unrelated-to-FreeBSD code that I am working on in my side project): vm_cache_t *bcread(VNode *vn, block_t blkNo); Lookup (vn,block#), issue asynchronous I/O as required, return vm_cache_t with underlying page either suitable for reading or undergoing I/O that we can block on if we want. vm_cache_t *bcwrite(VNode *vn, block_t blkNo); Lookup (vn,block#), issue asynchronous I/O as required, return vm_cache_t with underlying page either suitable for writing or undergoing I/O that we can block on if we want. This may also result in a copy-on-write, chain detachment, or other side effects necessary to return a writable page. (e.g. the vnode might represent a file in a MAP_SHARED+RW situation, or might represent a dummy vnode that abstracts a MAP_PRIVATE+RW situation. A copy on write would allocate a new page and associate it directly with the dummy vnode. A fork would fork the dummy vnode into two new vnodes A and B that both abstract the original dummy vnode V that itself abstracted the file). vm_cache_t *bcfree(VNode *vn, block_t blkNo); Indicate that a page can be thrown away entirely. There are all sorts of cool optimizations that can be implemented with this sort of scheme as well, but I'm only going to mention the most common one: caching block maps in order to avoid having to dive into a device in the 'cache' case. For example, you can abstract a file block map like this (note the negative block number supplied to bcread()) (also note that this whole schmear could be encapsulated and hidden in a procedure): block_t blkMapNo = fileOffset >> MMUPageShift; vc = bcread(vnFile, -blkMapNo); while ((kvmptr = bckvmaddress(vc)) == NULL) block chainBlk = ((block_t *)kvmptr)[blkMapNo & (MMUBlocksInPage - 1)]; if (chainBlk == (block_t)-1) fvc = ... attach zero-fill page ... else fvc = bcread(vnFile->vn_UnderlyingDevice, chainBlk); Etc. I could go on forever. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 21:44:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09661 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 21:44:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09654 for ; Mon, 23 Nov 1998 21:44:14 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA11954; Tue, 24 Nov 1998 16:13:12 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA67364; Tue, 24 Nov 1998 16:13:05 +1030 (CST) Message-ID: <19981124161305.W63366@freebie.lemis.com> Date: Tue, 24 Nov 1998 16:13:05 +1030 From: Greg Lehey To: Joel Ray Holveck Cc: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: <19981123205619.Q430@freebie.lemis.com> <86iug6mcnq.fsf@detlev.UUCP> <19981124093537.R430@freebie.lemis.com> <86af1hn411.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <86af1hn411.fsf@detlev.UUCP>; from Joel Ray Holveck on Mon, Nov 23, 1998 at 09:49:46PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 X-Mutt-References: <86af1hn411.fsf@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 23 November 1998 at 21:49:46 -0600, Joel Ray Holveck wrote: >>> I don't know what CPUs have instrumentation for this. >> All i386 architectures, in varying degrees. > > Since I wrote that message, I dragged out my Intel docs so I could > follow along with the rest of the class. > >>> (It might theoretically be possible with GDB using a semicomplex >>> series of isteps and tests, but it would slow down your system >>> possibly hundredfold.) >> The correct thing to do would be to implement I/O (and memory access) >> breakpoints, not kludge it. > > Memory access breakpoints are already implemented: > > watch addr,size > Set a watchpoint for a region. Execution stops when an attempt to modify > the region occurs. The size argument defaults to 4. If you specify a > wrong space address, the request is rejected with an error message. Last time I looked, watchpoints worked by tracing the program and only stopping if the condition was met. That makes it ridiculously slow, especially if you're debugging over a serial line. It also applies only for write access, not for read access. Here's the relevant part of the documentation for Lowbug (September 1992): 3.1.2 Breakpoints Up to four breakpoints can be set using the hardware breakpoint facility of the 386 architecture. These enable breakpoints to be set not only on instructions but also on memory read and memory write. To set a breakpoint, enter b addr [option [, option]] for a persistent breakpoint or B addr [option [, option]] for a temporary breakpoint The first form (persistent breakpoint) will create a breakpoint which will remain in effect until explicitly removed. The second form (temporary breakpoint) will create a breakpoint which will go away as soon as it is encountered. This form is useful to get to a certain point and then forget the breakpoint. It is also used internally by the leave command. addr is an expression which represents a symbolic address. This is the first byte of the address upon which the breakpoint will be set. options modify the breakpoint action. They can be any combination of: a action [; action] After encountering the breakpoint, the commands specified as action are executed. The commands may be any valid Lowbug command, including instructions to con- tinue execution. If this happens, there may be no indication that the breakpoint was hit. Breakpoint actions are executed for each breakpoint whose condition is fulfilled, in the order of the breakpoint number (which corresponds to the hardware breakpoint register). In particular, if two breakpoint conditions are valid at the same time, and the action of the first (i.e. lower numbered) breakpoint involves a return to the program, the second breakpoint will not be recognised, and its actions will not be executed. Note that action may consist of several subcommands, separated by semicolons (;). Since this is also the Lowbug command delimiter, some restrictions are imposed. Breakpoint subcommands are separated by commas. The action subcommand is taken to start immediately after the letter a and to continue to the next comma or to the end of the input line. If something is input like b _myioctl#23,al;&;v;b;c the commands b and c will be considered part of the action and will be executed when the breakpoint is encountered. In order to continue execution immediately, enter b _myioctl#23,al;&;v,b;c It is probably better, however, to never put further instructions behind a breakpoint instruction. i[f] condition Only stop program execution if the expression condition evaluates to non-zero. l expr The memory address monitored by the breakpoint starts at the address addr; it continues for 1, 2 or 4 bytes. This length defaults to 1, but may be specified by the l subcommand. Note that alignment rules are enforced by 80386 and 80486 hardware; a length of 2 implies that the high-order 31 address bits are the same. In addition, an instruction breakpoint may only have a length of 1, and in the case of a multi-byte opcode, it must be on the first byte. A length of 4 implies that the high-order 30 address bits are the same. Lowbug will reject combinations of start address and length which do not adhere to the length and alignment rules, but it cannot detect when an instruction breakpoint is set on other than the first byte of an instruction. p pid The breakpoint only applies to process pid. It will be ignored for others. t type Normally, a breakpoint occurs when an instruction starting at address addr is exe- cuted. The 80386 and 80486 hardware also support breakpoints which occur when memory reads or write are made at the specified location. This is specified with the t subcommand: type may be one of i (default), for instruction breakpoint, w, memory write - a breakpoint trap will occur after the memory write occurs; or m - memory read or write breakpoint. An breakpoint trap will occur after a data word is transferred to the memory location, a trap will not occur on an instruction fetch. Breakpoints slow the execution of the program minimally, since some of the internal pipelining of the chip must be turned off in order to get the correct address for the breakpoint return. In practice, this does not make much difference unless many "invisible" conditional breakpoints are executed. >> I look at it once, and the code turned my stomach. > > Was this for kdb, ddb, or kgdb? I don't know much about ddb. gdb. ddb is too limited to be of much use. > Going over its code, it appears that ddb uses the VMM to handle > watchpoints instead of using the processor's debugging > instrumentation. (This is fine with me, and more portable to boot.) The question is speed. > A quick review doesn't show any major problems implementing I/O > breakpoints. Is there any reason that the same entry mechanism to > enter ddb on a page fault couldn't also enter ddb on a debug > exception? If that's the case, then it would appear that all we need > to do is to write something to manage four I/O breakpoints and we've > got the basics. The main reason is that it's so slow as to be unusable. We have an alternative which *is* usable. > gdb already has some instrumentation for hardware breakpoints; it may > be extendable to allow for this sort of thing. I haven't looked into > that. It must be new, then. If you point me to it, I may take a look at it. >>> I generally recommend another method of debugging than I/O >>> breakpoints. >> >> That's a workaround, not a solution. I/O breakpoints are really >> useful. > > Yes, but they are also frequently misused. I myself used to be a > frequent debugger abuser, and would rely on the debugger instead of > thinking about the driver and knowing what's going on wrong. Sure, there's a certain tendency to do that. That doesn't make the tool bad, though. > And now I hope that I'm not starting a holy war. Who knows? :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 22:51:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15451 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 22:51:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (47-sweet.camalott.com [208.239.153.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15429 for ; Mon, 23 Nov 1998 22:51:27 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA65326; Tue, 24 Nov 1998 00:48:29 -0600 (CST) (envelope-from joelh) To: Greg Lehey Cc: SysAdmin , freebsd-hackers@FreeBSD.ORG Subject: Re: breakpoint on i/o in kernel References: <19981123205619.Q430@freebie.lemis.com> <86iug6mcnq.fsf@detlev.UUCP> <19981124093537.R430@freebie.lemis.com> <86af1hn411.fsf@detlev.UUCP> <19981124161305.W63366@freebie.lemis.com> From: Joel Ray Holveck Date: 24 Nov 1998 00:48:27 -0600 In-Reply-To: Greg Lehey's message of "Tue, 24 Nov 1998 16:13:05 +1030" Message-ID: <86n25hy4ar.fsf@detlev.UUCP> Lines: 116 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> The correct thing to do would be to implement I/O (and memory access) >>> breakpoints, not kludge it. >> Memory access breakpoints are already implemented: >>>> watch addr,size >>>> Set a watchpoint for a region. Execution stops when an attempt to modify >>>> the region occurs. The size argument defaults to 4. If you specify a >>>> wrong space address, the request is rejected with an error message. > Last time I looked, watchpoints worked by tracing the program and only > stopping if the condition was met. Are we talking about ddb or gdb here? I've only been lightly skimming the ddb code, but it looks like it uses the VMM; no single-stepping. gdb does what you suggest if there is no h/w support for watchpoints, or possibly if the number of watchpoints exceeds what the hardware can handle. The i386 has no h/w support presently. > That makes it ridiculously slow, especially if you're debugging over > a serial line. It also applies only for write access, not for read > access. There is that. But I think ddb uses the VM protection to trap writes, not single-stepping. > Here's the relevant part of the documentation for Lowbug (September > 1992): This is the debugger you made? It looks nice. I'd like to see the same functionality in kgdb. >>> I look at it once, and the code turned my stomach. >> Was this for kdb, ddb, or kgdb? I don't know much about ddb. > gdb. ddb is too limited to be of much use. Yes, but it's simple at least, and would be easily augmented for I/O traps from the look of it (which would solve the immediate problem). >> Going over its code, it appears that ddb uses the VMM to handle >> watchpoints instead of using the processor's debugging >> instrumentation. (This is fine with me, and more portable to boot.) > The question is speed. How does the speed differ using VMM vs. debugging exceptions? >> A quick review doesn't show any major problems implementing I/O >> breakpoints. Is there any reason that the same entry mechanism to >> enter ddb on a page fault couldn't also enter ddb on a debug >> exception? If that's the case, then it would appear that all we need >> to do is to write something to manage four I/O breakpoints and we've >> got the basics. > The main reason is that it's so slow as to be unusable. We have an > alternative which *is* usable. What is unusable? Single-stepping through? I'm not talking about that! What alternative? Lowbug? Does it still work? I'm suggesting adding commands to ddb and/or kgdb to allow manipulation of the CPU's debug registers. Admittedly, I don't know much about this facility, only what's in Intel's docs. But I don't know of any faster alternatives. How is what I'm proposing slow? >> gdb already has some instrumentation for hardware breakpoints; it may >> be extendable to allow for this sort of thing. I haven't looked into >> that. > It must be new, then. If you point me to it, I may take a look at it. gdb doesn't look like it has hardware support for the i386 yet. This is probably because the debug registers are only accessible from ring 0, so nobody felt it was worthwhile to add. The only platform I am aware of with hardware support is the SPARClite DSU. (The following is based on the gdb in -current.) However, the hbreak (hardware break) command is in place, and a quick review looks like watchpoints use hardware when they can. Look in breakpoint.c; grep for "hardware" to find key points. If you want to see a breakpoint structure allocated, start with hbreak_command and watch_command_1, and follow from there. Other highlights are insert_breakpoints (called to instrument the code and create hardware breakpoints / watchpoints), bpstat_should_step (called to check for software watchpoints), and target_insert_watchpoint (I don't know where that is). *** XXX *** To whoever hacks this: breakpoint.c:2447 seems to imply that hardware breakpoints are implemented using watchpoints. However the existance of separate functions target_insert_hw_breakpoint and target_insert_watchpoint would seem to imply differently. Please double-check that code. (For the i386 it may not matter, since 2447 tests the number of watchpoints remaining, which for us is the same as the number of hardware breakpoints remaining.) >>>> I generally recommend another method of debugging than I/O >>>> breakpoints. >>> That's a workaround, not a solution. I/O breakpoints are really >>> useful. >> Yes, but they are also frequently misused. I myself used to be a >> frequent debugger abuser, and would rely on the debugger instead of >> thinking about the driver and knowing what's going on wrong. > Sure, there's a certain tendency to do that. That doesn't make the > tool bad, though. I agree. I'm all for doling out rope, and letting the recipient judge whether to tie a ladder or a noose. That's why I say, "I generally recommend..." rather than "You should use...". Not knowing his situation, I don't want to make any judgements one way or the next. (You may also notice I'm considering implementing this.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 23 23:51:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19189 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 23:51:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19184 for ; Mon, 23 Nov 1998 23:50:57 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id HAA23949; Tue, 24 Nov 1998 07:50:49 GMT (envelope-from rb@gid.co.uk) Received: from localhost by seagoon.gid.co.uk; Tue, 24 Nov 1998 07:41:43 GMT Date: Tue, 24 Nov 1998 07:41:43 +0000 (GMT) From: Bob Bishop X-Sender: rb@seagoon To: Matthew Dillon cc: Luoqi Chen , cnielsen@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <199811240433.UAA12209@apollo.backplane.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 Hi, On Mon, 23 Nov 1998, Matthew Dillon wrote: > What we really need to do is integrate the VFS layer abstraction into > the buffer cache and get rid of all the baggage in the buffer pointer > (bp) layer. [etc] What does this do to the minimum kernel footprint (think picobsd etc)? -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20157 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:02:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whitewater.chem.wisc.edu (bayou.chem.wisc.edu [128.104.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20152 for ; Tue, 24 Nov 1998 00:02:41 -0800 (PST) (envelope-from jagapen@whitewater.chem.wisc.edu) Received: from billybob (billybob [10.2.71.93]) by whitewater.chem.wisc.edu (8.9.1/8.9.1) with ESMTP id CAA00869 for ; Tue, 24 Nov 1998 02:02:39 -0600 (CST) Date: Tue, 24 Nov 1998 02:02:38 -0600 (CST) From: Jonathan Gapen X-Sender: jagapen@billybob.chem.wisc.edu To: freebsd-hackers@FreeBSD.ORG Subject: ELF Global Constructors In-Reply-To: <9811190535.AA01429@tiptree.brainstorm.co.uk> 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 in the process of porting GNUstep to FreeBSD 3.0, and I've run into a lack of documentation. Consequently, I don't know where the problem lies. It's like this: GNUstep needs to have a function _gnu_process_args() called before main() to set up information about the process for use by the Foundation library. On non-Linux ELF systems, it tries this bit of code: static void *__gnustep_base_subinit_args__ __attribute__ ((section ("_libc_subinit"))) = &(_gnu_process_args); This is where the lack of documentation is getting me. I can't find out what *will* work. I don't know if this is the correct way to hook in a function call before main() and FreeBSD is broken, or egcs is broken, or if it's the wrong way entirely. I'm not even sure where to dig into the system source to find out what's going on, so I'd appreciate any help/pointers. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:17:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21594 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:17:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21575 for ; Tue, 24 Nov 1998 00:17:07 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA07814; Tue, 24 Nov 1998 19:22:04 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811240822.TAA07814@cimlogic.com.au> Subject: Re: ELF Global Constructors In-Reply-To: from Jonathan Gapen at "Nov 24, 98 02:02:38 am" To: jagapen@whitewater.chem.wisc.edu (Jonathan Gapen) Date: Tue, 24 Nov 1998 19:22:04 +1100 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Gapen wrote: > I'm in the process of porting GNUstep to FreeBSD 3.0, and I've run > into a lack of documentation. Consequently, I don't know where the > problem lies. It's like this: > GNUstep needs to have a function _gnu_process_args() called before > main() to set up information about the process for use by the Foundation > library. On non-Linux ELF systems, it tries this bit of code: > > static void *__gnustep_base_subinit_args__ > __attribute__ ((section ("_libc_subinit"))) = &(_gnu_process_args); > > This is where the lack of documentation is getting me. I can't find > out what *will* work. I don't know if this is the correct way to hook in > a function call before main() and FreeBSD is broken, or egcs is broken, or > if it's the wrong way entirely. > I'm not even sure where to dig into the system source to find out > what's going on, so I'd appreciate any help/pointers. Thanks! For an example of a constructor, have a look at: src/lib/libc_r/uthread/uthread_autoinit.cc This is how a threaded process is initialised prior to the process calling main(). This code works with the in-tree compiler (I haven't used egcs, so I'm not sure about that). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:26:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22326 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:26:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA22321 for ; Tue, 24 Nov 1998 00:26:45 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KFROIRJJ; Tue, 24 Nov 98 08:26:43 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981124092630.00b7b1e0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 24 Nov 1998 09:26:30 +0100 To: John Polstra From: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: hackers@FreeBSD.ORG, joelh@gnu.org In-Reply-To: References: <3.0.5.32.19981123144427.00b40940@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >No. Have you even read this thread? Yes. >This thread is about whether to expend significant effort and >sacrifice significant elegance and maintainability in order to >_slightly_ _optimize_ system calls for 486 systems. It has nothing >to do with whether we support 486 systems or not. I know that. I'm simply wondering how much extra complexity we would be adding, and what kind of impact it would have on syscall times. And, if you've read the thread yourself, you'll see that the answer I recieved some time ago indicated that we didn't want to do this because it applied to the 486, it did not say 'we don't want to add this complexity for such a small performance gain on the 486'. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22382 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:27:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA22377 for ; Tue, 24 Nov 1998 00:27:38 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KFRONVDJ; Tue, 24 Nov 98 08:27:33 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981124092721.00b9a6f0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 24 Nov 1998 09:27:21 +0100 To: Eivind Eklund , Joel Ray Holveck From: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: Terry Lambert , Matthew Dillon , rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19981123180039.T24412@follo.net> References: <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> <3.0.5.32.19981120103442.0099f460@mail.scancall.no> <86hfvuia7y.fsf@detlev.UUCP> <3.0.5.32.19981123144319.00a4d560@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It adds too much complexity/interdependcies, in my opinion. Unless >somebody can show significant speed gains (well into the measurable >range), I don't think it is worthwhile. Of course, the speed gains would have to be significant. I totally agree on that part. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:52:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24540 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:52:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24532 for ; Tue, 24 Nov 1998 00:52:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA13083; Tue, 24 Nov 1998 00:52:18 -0800 (PST) (envelope-from dillon) Date: Tue, 24 Nov 1998 00:52:18 -0800 (PST) From: Matthew Dillon Message-Id: <199811240852.AAA13083@apollo.backplane.com> To: Bob Bishop Cc: Luoqi Chen , cnielsen@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :On Mon, 23 Nov 1998, Matthew Dillon wrote: : :> What we really need to do is integrate the VFS layer abstraction into :> the buffer cache and get rid of all the baggage in the buffer pointer :> (bp) layer. [etc] : :What does this do to the minimum kernel footprint (think picobsd etc)? Well, with the scheme I outlined it's a straight percentage, so the minimum footprint scales to the amount of memory in the machine. You could also reduce the number of cache entries you preallocate, but the minimum there is going to come in at around 1x the number of pages in the system (plus enough to handle active I/O) - considerably fewer then the 4x recommended. It would work, you would simply be trading off cpu for memory as it would take more cpu to resolve cache misses. Still, there is a huge amount of memory savings to be had in other areas. I just don't know how feasible it all is... it would mean a huge amount of rewriting. If we add this sort of cache in, we'd definitely want to get rid of the buffer pointer code. Since the BP code combines vnode block mapping for I/O and managed KVM buffers (abstracting files into linear segments of KVM for device operation and block resizing purposes), the only way I can think of to remove it would require going to the direct-physical-map scheme and rewriting all the devices to use it. For example, UFS could still have an 8K filesystem block size but the indexing code would have to operate through the hardware page size'd buffer cache. The disadvantage of this scheme is that it limits main memory to around 2GB on a 32 bit machine. The list of advantages goes on forever, though... everything I outlined in previous messages plus even more. Although a lot of rewriting would have to be done, the end result would be a much smaller kernel due to the huge amounts of code that I think could be removed. BP's go away, kernel page table manipulation and related special casing dissolves away leaving only a few managed areas (w/ preallocated page tables) to handle supervisor stacks. Direct access to UVM goes away, removing all the special casing related to that and cleaning up UIO considerably (instead, the kernel code accesses UVM directly through the new buffer cache). Most of the MMU complexity disappears. Virtually every part of the kernel would be simplified. Interrupts could even be moved into kernel threads without adding much (or any) overhead, which reduces the size of the per-process supervisor stack considerably. Async device I/O would become trivial - e.g. read() -> internal_read(curprc->p_UVMVNode, uptr, bytes) with devices accessing UVM through the buffer cache rather then directly, which also makes it trivial to move async operations into kernel threads. The benefits cascade very quickly.... if one is willing to give up > 2GB memory configurations on 32 bit cpus. -Matt :-- :Bob Bishop +44 118 977 4017 :rb@gid.co.uk fax +44 118 989 4254 : : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 00:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24664 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 00:53:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from garius.magnet.at (garius.magnet.at [195.170.70.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24647 for ; Tue, 24 Nov 1998 00:53:25 -0800 (PST) (envelope-from r.friess@msg.at) Received: from ws-raf (gateway.msgeuro.com [193.154.204.102]) by garius.magnet.at (8.9.0/8.9.0/magnet) with SMTP id JAA16654 for ; Tue, 24 Nov 1998 09:53:17 +0100 (MET) X-magnet-rcpt: Received: by localhost with Microsoft MAPI; Tue, 24 Nov 1998 09:58:48 +0100 Message-ID: <01BE1791.0824F890.r.friess@msg.at> From: Rudolf Friess Reply-To: "r.friess@msgeuro.com" To: "'freebsd-hackers@FreeBSD.ORG'" Subject: RE: Changing the load address of the kernel? Date: Tue, 24 Nov 1998 09:58:47 +0100 Organization: Marketing Service GmbH X-Mailer: Microsoft Internet E-Mail/MAPI - 8.0.0.4211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Oliver Fromme [SMTP:olli@dorifer.heim3.tu-clausthal.de] Sent: Monday, November 23, 1998 9:29 PM To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? Robert Nordier wrote in list.freebsd-hackers: > We do need a more capable netboot replacement, and if Lanworks is > as responsive as they appear to be, then supporting their product > may be an easy route to satisfying this requirement. They are. They support only DOS and Windows "officially", but they have a UNIX person which answers to technical questions quite fast. They also send free (!) evaluation packages upon request. I ordered one, and it arrived two days later by UPS express (from Canada to Germany). BTW, Linux supports the Lanworks boot ROMs. It would be nice to have FreeBSD support for those ROMs, too, in one way or another. Even if we had a working netboot code, many people aren't able to make their own EPROMs. Especially those QPGA/FPGA (?) Flash memories required for many PCI cards (like the EtherExpress Pro/100) aren't easy to make on your own. Therefore people have to buy ready-made solutions, and it would be nice to be able to point at such a product and say "take this one, it works with FreeBSD". > It might be a reasonable solution to make something like this > available as a port; after all, the boot blocks are *expected* to > be somewhat out of sync with kernel development. > > Though I'd quite like to see it working with the new boot1/boot2 > and boot/loader code, in some form, now that Oliver has shown the > way. > > > Anyway, if someone needs some code to boot his/her FreeBSD box > > with a Lanworks ROM, I've put the "ramboot" stuff on the web: > > http://dorifer.heim3.tu-clausthal.de/~olli/ramboot.tar.gz > > Thanks. I've just fetched a copy. You're welcome. If people are really interested in this, I can create some documentation with step-by-step instructions (how to set up bootp and tftp servers, build the kernel, create the tftpboot image, etc.). [R. Friess >] I'd raise my hands and clap. Hacking some code to solve a problem is a good thing. Creating also some good documentation is what makes the hack a usable product. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) 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 Nov 24 01:36:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28842 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 01:36:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28836 for ; Tue, 24 Nov 1998 01:36:04 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id JAA05549 for ; Tue, 24 Nov 1998 09:36:01 GMT (envelope-from didier@omnix.net) Date: Tue, 24 Nov 1998 10:36:01 +0100 (CET) From: Didier Derny To: hackers@FreeBSD.ORG Subject: URGENT: problem with Adaptec ANA 6944A Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think I've discovered why the ports other that the first one are not working. In fact it seems that the board is seen as 4 standard de0..de3 board and not a 6944A board. extract from dmesg ------------------ Probing for devices on PCI bus 2: de0: rev 0x22 int a irq 12 on pci2.4.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:00:d1:1b:e9:ae de1: rev 0x22 int a irq 9 on pci2.5.0 de1: 21140A [10-100Mb/s] pass 2.2 de1: address 00:00:d1:1b:e9:af de2: rev 0x22 int a irq 9 on pci2.6.0 de2: 21140A [10-100Mb/s] pass 2.2 de2: address 00:00:d1:1b:e9:b0 de3: rev 0x22 int a irq 11 on pci2.7.0 de3: 21140A [10-100Mb/s] pass 2.2 de3: address 00:00:d1:1b:e9:b1 result of pciconf -l -------------------- chip0@pci0:0:0: class=0x060000 card=0x154110b9 chip=0x154110b9 rev=0x04 hdr=0x00 chip1@pci0:1:0: class=0x060400 card=0x000000e0 chip=0x524310b9 rev=0x04 hdr=0x01 chip2@pci0:3:0: class=0x068000 card=0x710110b9 chip=0x710110b9 rev=0x00 hdr=0x00 chip3@pci0:7:0: class=0x060100 card=0x00000000 chip=0x153310b9 rev=0xc3 hdr=0x00 chip4@pci0:10:0: class=0x060400 card=0x000000dc chip=0x00241011 rev=0x03 hdr=0x01 ahc0@pci0:11:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 hdr=0x00 ide_pci0@pci0:15:0: class=0x0101ea card=0x00000000 chip=0x522910b9 rev=0xc1 hdr=0x00 vga0@pci1:0:0: class=0x030000 card=0x1100102b chip=0x051f102b rev=0x00 hdr=0x00 de0@pci2:4:0: class=0x020000 card=0x24001109 chip=0x00091011 rev=0x22 hdr=0x00 de1@pci2:5:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x22 hdr=0x00 de2@pci2:6:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x22 hdr=0x00 de3@pci2:7:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x22 hdr=0x00 thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 05:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20849 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 05:13:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20843 for ; Tue, 24 Nov 1998 05:13:53 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id NAA12969 for ; Tue, 24 Nov 1998 13:13:50 GMT (envelope-from didier@omnix.net) Date: Tue, 24 Nov 1998 14:13:50 +0100 (CET) From: Didier Derny To: hackers@FreeBSD.ORG Subject: problem with adaptec ANA 6944A TX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I now have a patch for the Adaptec/Cogent ANA 6944A TX *** if_de.c.orig Tue Nov 24 14:07:25 1998 --- if_de.c Tue Nov 24 14:08:06 1998 *************** *** 2755,2760 **** --- 2755,2761 ---- { tulip_identify_znyx_nic, { 0x00, 0xC0, 0x95 } }, { tulip_identify_cogent_nic, { 0x00, 0x00, 0x92 } }, { tulip_identify_asante_nic, { 0x00, 0x00, 0x94 } }, + { tulip_identify_cogent_nic, { 0x00, 0x00, 0xD1 } }, { tulip_identify_accton_nic, { 0x00, 0x00, 0xE8 } }, { NULL } }; It works with FreeBSD 3.0-RELEASE -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 06:13:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26660 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 06:13:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail2.rochester.rr.com (mail2-1.twcny.rr.com [24.92.226.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26653 for ; Tue, 24 Nov 1998 06:13:01 -0800 (PST) (envelope-from leisner@rochester.rr.com) Received: from rochester.rr.com ([24.93.25.38]) by mail2.rochester.rr.com (Post.Office MTA v3.5.2 release 221 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Tue, 24 Nov 1998 09:13:25 -0500 Received: from dw (localhost [127.0.0.1]) by rochester.rr.com (8.8.5/8.8.5) with ESMTP id JAA00724; Tue, 24 Nov 1998 09:12:48 -0500 Message-Id: <199811241412.JAA00724@rochester.rr.com> X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: leisner@rochester.rr.com To: Nate Williams cc: hackers@FreeBSD.ORG Subject: Re: Wrapping a function In-reply-to: Your message of "Sun, 22 Nov 1998 07:25:38 MST." <199811221425.HAA21510@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 09:12:48 -0500 From: "Marty Leisner" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In recent gnu ld's: > > `--wrap SYMBOL' > > Use a wrapper function for SYMBOL. Any undefined reference to > > SYMBOL will be resolved to `__wrap_SYMBOL'. Any undefined > > reference to `__real_SYMBOL' will be resolved to SYMBOL. > > Cool! Does our ld do this? > > > Nate I haven't tried an ELF system yet, using GNU binutils. Which is one of the reasons I really like to see the GNU binutils used (becaused it has these neat options...) Marty Leisner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 07:20:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02451 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 07:20:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02442; Tue, 24 Nov 1998 07:20:08 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id KAA26375; Tue, 24 Nov 1998 10:20:00 -0500 (EST) Message-ID: <365ACE9F.8566C16B@ics.com> Date: Tue, 24 Nov 1998 10:19:59 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: questions@FreeBSD.ORG CC: hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle References: <199811231915.MAA23348@usr02.primenet.com> <86g1bamc80.fsf@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > > >>> I also now know why the de probe doesn't print out a message when the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >>> probe fails. Which is not to say that I think that's good. On the > >>> contrary, I think it's bad. C'est la vie. > >> Printing out an error message when a PCI match fails would be stupid; Yup; but then I said as much. > >> every PCI device is (currently) presented to every PCI driver until one > >> claims it. Printing a message when the match failed ("no, not for me") > >> would produce a useless spew of garbage. > > You need a pseudo-device at the end of the inquiry chain to catch > > id's that haven't been caught by the real drivers, and to print > > out a message ("PCI: no driver: id xxx ..."). > > That's catching the wrong set. Yes and no. > Kaleb wanted the to know the drivers without cards. Not really. I wanted to know why the de driver wasn't recognizing my NIC. According to the FAQ and the Handbook it is supposed to be the driver for my card. Turns out it's not, but there ought to be a better way to discover this than by sprinkling the kernel with printfs, or try-each-one-until-one-succeeds, or turn-everything-on-to-discover-which-it-is. > You're giving us the set of cards without drivers. > (This is also possibly a useful set, but not what kaleb wanted.) Seems to me -- from the cursory look-see that I took while figuring out my card -- that the PCI ethernet stuff could be unified into something like a single pci (pseudo?) ethernet device. That could be fun to hack on. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 07:29:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02954 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 07:29:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02948 for ; Tue, 24 Nov 1998 07:29:05 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id KAA27425 Tue, 24 Nov 1998 10:28:56 -0500 (EST) Message-ID: <365AD0B8.E50AC6C3@ics.com> Date: Tue, 24 Nov 1998 10:28:56 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: ELF Global Constructors References: <199811240822.TAA07814@cimlogic.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 John Birrell wrote: > > Jonathan Gapen wrote: > > I'm in the process of porting GNUstep to FreeBSD 3.0, and I've run > > into a lack of documentation. Consequently, I don't know where the > > problem lies. It's like this: > > GNUstep needs to have a function _gnu_process_args() called before > > main() to set up information about the process for use by the Foundation > > library. On non-Linux ELF systems, it tries this bit of code: > > > > static void *__gnustep_base_subinit_args__ > > __attribute__ ((section ("_libc_subinit"))) = &(_gnu_process_args); > > > > This is where the lack of documentation is getting me. I can't find > > out what *will* work. I don't know if this is the correct way to hook in > > a function call before main() and FreeBSD is broken, or egcs is broken, or > > if it's the wrong way entirely. > > I'm not even sure where to dig into the system source to find out > > what's going on, so I'd appreciate any help/pointers. Thanks! > > For an example of a constructor, have a look at: > > src/lib/libc_r/uthread/uthread_autoinit.cc > > This is how a threaded process is initialised prior to the process calling > main(). This code works with the in-tree compiler (I haven't used egcs, so > I'm not sure about that). The ELF Specification (a.k.a. the System V ABI) says that the .init() function in the shared lib(s) is/are called before main(). Likewise the .fini() function is called after the program exits normally. Any initialization the shared library needs, e.g. calling global constructors, can be put there. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 08:17:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06673 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 08:17:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06668 for ; Tue, 24 Nov 1998 08:17:23 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id IAA08037; Tue, 24 Nov 1998 08:14:35 -0800 (PST) (envelope-from dhw) Date: Tue, 24 Nov 1998 08:14:35 -0800 (PST) From: David Wolfskill Message-Id: <199811241614.IAA08037@pau-amma.whistle.com> To: hackers@FreeBSD.ORG, kpielorz@tdx.co.uk Subject: Re: Getting PID of parent pipe? In-Reply-To: <36555721.8E3D2CDF@tdx.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 20 Nov 1998 11:48:49 +0000 >From: Karl Pielorz >Is there an 'easy' way of getting the PID of a parent process feeding a >command's stdin? >e.g. >cat something | foo | bar >I need to get the PID of foo while running as bar... If "bar" is something you can control/modify, it would seem that getppid() would be an appropriate tool. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 08:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09205 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 08:39:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from o2.cs.rpi.edu (o2.cs.rpi.edu [128.113.96.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09197 for ; Tue, 24 Nov 1998 08:39:17 -0800 (PST) (envelope-from crossd@o2.cs.rpi.edu) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id LAA33678; Tue, 24 Nov 1998 11:39:06 -0500 (EST) Date: Tue, 24 Nov 1998 11:38:58 -0500 From: "David E. Cross" To: David Wolfskill cc: hackers@FreeBSD.ORG, kpielorz@tdx.co.uk Subject: Re: Getting PID of parent pipe? In-Reply-To: <199811241614.IAA08037@pau-amma.whistle.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, 24 Nov 1998, David Wolfskill wrote: > >Date: Fri, 20 Nov 1998 11:48:49 +0000 > >From: Karl Pielorz > > >Is there an 'easy' way of getting the PID of a parent process feeding a > >command's stdin? > > >e.g. > > >cat something | foo | bar > > >I need to get the PID of foo while running as bar... > > If "bar" is something you can control/modify, it would seem that > getppid() would be an appropriate tool. that would return to him the PID of the shell process, not the PID of 'foo' (the process which is feeding the pipe). I don't know of an easy way from 'bar' to get the PID of 'foo'. You could do it with a method similar too lsof, but that would require special privs that you may or may not have, and a good deal of effort. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 09:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13262 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 09:08:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whitewater.chem.wisc.edu (bayou.chem.wisc.edu [128.104.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13257 for ; Tue, 24 Nov 1998 09:08:32 -0800 (PST) (envelope-from jagapen@whitewater.chem.wisc.edu) Received: from billybob (billybob [10.2.71.93]) by whitewater.chem.wisc.edu (8.9.1/8.9.1) with ESMTP id LAA03921 for ; Tue, 24 Nov 1998 11:08:28 -0600 (CST) Date: Tue, 24 Nov 1998 11:08:28 -0600 (CST) From: Jonathan Gapen X-Sender: jagapen@billybob.chem.wisc.edu To: freebsd-hackers@FreeBSD.ORG Subject: Re: ELF Global Constructors In-Reply-To: <199811240822.TAA07814@cimlogic.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 On Tue, 24 Nov 1998, John Birrell wrote: > For an example of a constructor, have a look at: > src/lib/libc_r/uthread/uthread_autoinit.cc > > This is how a threaded process is initialised prior to the process calling > main(). This code works with the in-tree compiler (I haven't used egcs, so > I'm not sure about that). Doh! I forgot to mention that most of GNUstep is written in Objective C, so C++ constructors aren't going to work. Further, the global class trick doesn't work. That does suggest to me the bad hack of linking in a C++ class which calls that function. Still, I'd like to find out how the C++ compiler hooks in those constructors to be called before main(), so I can do the same. -- Jonathan Gapen - sysadmin - biker - caver - collecter of old computers I think you know exactly what I mean when I say it's a shpadoinkle day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 09:10:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13500 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 09:10:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13495 for ; Tue, 24 Nov 1998 09:10:31 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA15679; Tue, 24 Nov 1998 12:14:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 24 Nov 1998 12:14:14 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "David E. Cross" cc: David Wolfskill , hackers@FreeBSD.ORG, kpielorz@tdx.co.uk Subject: Re: Getting PID of parent pipe? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, David E. Cross wrote: > > >Is there an 'easy' way of getting the PID of a parent process feeding a > > >command's stdin? > > > > >e.g. > > > > >cat something | foo | bar > > > > >I need to get the PID of foo while running as bar... > > > > If "bar" is something you can control/modify, it would seem that > > getppid() would be an appropriate tool. > > that would return to him the PID of the shell process, not the PID of > 'foo' (the process which is feeding the pipe). I don't know of an easy > way from 'bar' to get the PID of 'foo'. You could do it with a method > similar too lsof, but that would require special privs that you may or may > not have, and a good deal of effort. > This would be very hard to do considering that pipes are full duplex and the fact that many processes can have a pipe open. In fact getting the uid associated with a socket/pipe is difficult as well. Consider fd passing as another problem but perhaps a solution. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 09:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14273 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 09:17:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ntmail1.cskauto.com (csknet.cskauto.com [207.247.103.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14254; Tue, 24 Nov 1998 09:16:57 -0800 (PST) (envelope-from JFOSTER@CSKAUTO.COM) Received: by v128041.vandenberg.af.mil with Internet Mail Service (5.5.2232.9) id ; Tue, 24 Nov 1998 10:18:22 -0700 Message-ID: From: "Foster, Jim" To: "'freebsd-questions@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: Getting to Stable and boot floppies Date: Tue, 24 Nov 1998 10:18:08 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am trying to work my way from 2.2.7-Release to 2.2.7-Stable. While most of my questions were answered by the folks over on FreeBSD-stable, one very important question (at least to me) was left unanswered. I need to boot my machine from a floppy, but I can't seem to find out where the floppy image will be at to rebuild the disk. Will it be a single file like boot.flp, or will it be a set of files that need to be installed? I assume that it will be made after the kernel is re-built. Is that a correct assumption? Thanks, and please be sure to cc directly to me since I don't subscribe to FreeBSD-questions or FreeBSD-hackers because of the volume of mail that I receive. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 11:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28792 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 11:47:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28782 for ; Tue, 24 Nov 1998 11:47:55 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02152; Tue, 24 Nov 1998 11:47:53 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00814; Tue, 24 Nov 1998 11:47:52 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 24 Nov 1998 11:47:52 -0800 (PST) Message-Id: <199811241947.LAA00814@vashon.polstra.com> To: jagapen@whitewater.chem.wisc.edu Subject: Re: ELF Global Constructors Newsgroups: polstra.freebsd.hackers In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jonathan Gapen wrote: > I'm in the process of porting GNUstep to FreeBSD 3.0, and I've run > into a lack of documentation. Consequently, I don't know where the > problem lies. It's like this: > GNUstep needs to have a function _gnu_process_args() called before > main() to set up information about the process for use by the Foundation > library. Check out the gcc info pages, in the section "Function Attributes". Here's the section of interest: `constructor' `destructor' The `constructor' attribute causes the function to be called automatically before execution enters `main ()'. Similarly, the `destructor' attribute causes the function to be called automatically after `main ()' has completed or `exit ()' has been called. Functions with these attributes are useful for initializing data that will be used implicitly during the execution of the program. It does go on to say this, though, so you'll have to use C: These attributes are not currently implemented for Objective C. Anyway, it should work for C if you add "__attribute__ ((constructor))" at the end of the function declaration. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 13:07:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06519 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 13:07:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06514 for ; Tue, 24 Nov 1998 13:07:20 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id QAA18618; Tue, 24 Nov 1998 16:06:55 -0500 (EST) Date: Tue, 24 Nov 1998 16:06:54 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Nik Clayton cc: hackers@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981118211919.10512@nothing-going-on.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 Personally (and I'm biased since I just started kicking around my Sparc2), I think there are some serious gains here for people new to FBSD, and some major conveniences for wizened users. I would have killed for ./nfsd.sh top/start this past week. There seem to be more and more people using databases and some of them (mysql for one) don't like the way they are currently shutdown. If rather than killing the daemon we could call 'mysqladmin shutdown', that would be swell. Since you're going through rc.conf for options you could even have something along the lines of 'ed0 restart/stop/start', which could be handy. A nice advantage of this is if you get in the habit of configuring things in one config file and testing your changes from there rather than on the fly is that you end up with a more organized and stable system. And it's not too SysV, as they don't yet have a central config file. This is better. $.02, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Wed, 18 Nov 1998, Nik Clayton wrote: > On Tue, Nov 17, 1998 at 09:01:38PM +0000, Nik Clayton wrote: > > If there are no more comments by Thursday I'll take it as tacit agreement, > > and go ahead. I'll do sendmail first. > > Well, that's certainly one way to kick off a discussion. > > Attached is a quick implementation of what I've been talking about. All > it does is provide startup scripts for inetd and an NFS server. This is > a minimal implementation, provided for people to kick around. > > To use these; > > 1. mkdir /etc/rc.d > > 2. Copy inetd.sh and nfs_server.sh (attached) to this directory. Make > them executable. > > 3. Edit /etc/rc and change the line that starts inetd to > > /etc/rc.d/inet.sh start > > (keep it wrapped in the test for ${inetd_enable} though) > > 4. Edit /etc/rc.network. Find the block that tests for ${nfs_server_enable} > and replace the contents of the block with > > /etc/rc.d/nfs_server.sh start > > You can then start playing around. > > inetd.sh is how I expect most of these scripts to look. There's only one > daemon to start, which makes the surrounding code look somewhat extraneous > for all it's got to do. > > Hopefully, nfs_server.sh makes my point a little more clearly. As you can > see there are a number of daemons that need to be started and/or stopped for > NFS serving. > > Suppose you've changed the NFS server flags in /etc/rc.conf, and want to > test that they work. > > Currently, you would do this by; > > - Reading /etc/rc.network to determine what daemons have been started. > > - Kill them. In some cases killall or kill will be sufficient. In others > you need to stop programs in a specific order -- for these programs > you have to make sure you know what that order is. > > - Restart them. Either by typing/cutting-pasting the commands from > /etc/rc.network, plugging in the same values as you have put in > /etc/rc.conf. Or by crafting together a small shell script to pull > in the values from /etc/rc.conf and starting the daemons in this > script. > > - Even now, you're not 100% guaranteed that what you've just done > mirrors what will be run the next time the system boots. > > With this (new) approach, you just > > # /etc/rc.d/nfs_server restart > > and watch as it kills the daemons, and restarts them with whatever > values you currently have in /etc/rc.conf. It does it consistently, > correctly, and will happen the same way when the system boots. > > To answer some of the points raised by other people; > > Yes, this will make booting slower, and push up the PID of the first > login process run. So what? The slow down is imperceptible, and I would > expect it to be on the order of 3 or 4 seconds maximum if this approach > is fully adopted (and even then your disks would need to be pretty slow > for it to be that drastic). You waste more time than that checking that > you've killed all the daemons and restarted them properly, so over time > it's probably a net win. > > Yes, it's different from how things have been done before. So what? > It's not change for change's sake, it brings the benefits I've outlined > above and in earlier messages which (IMHO) make the change worthwhile. > > Yes, it will confuse old-hand BSD administrators. So did the introduction > of /etc/rc.conf (nee' /etc/sysconfig). Perhaps confuse is the wrong > word. It might disorient them slightly, but only briefly. All that's > happened is that the content of some of the /rc/rc.* files has been > moved out into other files in another directory. init hasn't changed, > the order hasn't changed, the mechanism for deciding what order to run > things in hasn't changed. > > N > -- > C.R.F. Consulting -- we're run to make me richer. . . > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 13:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10625 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 13:43:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from furrball.dyn.ml.org ([207.18.137.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10599; Tue, 24 Nov 1998 13:43:46 -0800 (PST) (envelope-from chris@furrball.dyn.ml.org) Received: (from chris@localhost) by furrball.dyn.ml.org (8.9.1a/8.8.8) id LAA03292; Tue, 24 Nov 1998 11:34:55 -0600 (CST) (envelope-from chris) Date: Tue, 24 Nov 1998 11:34:55 -0600 (CST) From: Chris Costello Message-Id: <199811241734.LAA03292@furrball.dyn.ml.org> To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, JFOSTER@CSKAUTO.COM Subject: Re: Getting to Stable and boot floppies Reply-To: phoenix@calldei.com In-Reply-To: X-Mailer: mail(1) -- the One True(TM) mail client Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: "Foster, Jim" > To: "'freebsd-questions@freebsd.org'" , > "'freebsd-hackers@freebsd.org'" > Subject: Getting to Stable and boot floppies > Date: Tue, 24 Nov 1998 10:18:08 -0700 > > Hi all, > > I am trying to work my way from 2.2.7-Release to 2.2.7-Stable. While most > of my questions were answered by the folks over on FreeBSD-stable, one very > important question (at least to me) was left unanswered. > > I need to boot my machine from a floppy, but I can't seem to find out where > the floppy image will be at to rebuild the disk. Will it be a single file > like boot.flp, or will it be a set of files that need to be installed? I > assume that it will be made after the kernel is re-built. Is that a correct > assumption? You will need the stable supfile and the directions. They should be in the handbook. Basically, you will type something similar to cvsup stable-supfile (as the root user) and it will download a group of files into /usr/src. From there, you go to single-user mode and go into /usr/src and type: (make buildworld && make installworld) this would take a few hours, depending on your hardware. Make sure it was successful, and if so, you will have a new set of binaries installed, and then you would go and make your kernel. If your kernel is GENERIC, for example, you could do: cd /usr/src/sys/i386/conf config GENERIC cd ../../compile/GENERIC (make && make install) If all goes well, your system should be upgraded to FreeBSD 2.2.7-STABLE. Just type 'reboot' when finished. > > Thanks, and please be sure to cc directly to me since I don't subscribe to > FreeBSD-questions or FreeBSD-hackers because of the volume of mail that I > receive. > > Jim > -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 14:25:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15046 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 14:25:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu ([155.99.198.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15033 for ; Tue, 24 Nov 1998 14:25:30 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from torrey.cs.utah.edu (torrey.cs.utah.edu [155.99.212.91]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id PAA23390; Tue, 24 Nov 1998 15:25:26 -0700 (MST) Received: (from danderse@localhost) by torrey.cs.utah.edu (8.9.1/8.9.1) id PAA00518; Tue, 24 Nov 1998 15:25:25 -0700 (MST) (envelope-from danderse@cs.utah.edu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 24 Nov 1998 15:25:25 -0700 (MST) From: "David G. Andersen" To: hackers@FreeBSD.ORG CC: vanmaren@cs.utah.edu, sclawson@cs.utah.edu Subject: MFS hang when copying large file to it (vm problem?) X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13915.12507.346867.242762@torrey.cs.utah.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brief summary: System: 3.0-release (plus a few days of -current) Memory: 128M Swap: 512M on /dev/wd0s3b /tmp: 256M MFS backed to /dev/wd0s3b dd if=/dev/zero of=/tmp/zero bs=64k count={large enough to force swapping of the file being DD'd. 3000 does the trick nicely} will cause the system to hang. The symptoms are very similar to those reported in Feb. 1998 in: http://www.freebsd.org/cgi/getmsg.cgi?fetch=412721+415177+/usr/local/www/db/text/1998/freebsd-hackers/19980215.freebsd-hackers (Search for "VM AND messed" in -hackers to get the full thread) where Don Lewis stated: Do you think this could explaint the MFS related hangs I've been seeing in 2.1-stable? If I use MFS for /tmp, copy a large file into /tmp, delete the file, then copy it into /tmp again, the machine will hang. It responds to pings. It will also respond to ^T until I try to interrupt a process with ^C. The only way to unhang it is to use the reset button. It's fairly trivial to reproduce, but we're running SMP with our typical heavily networked environment. Has anyone encountered this, have a fix for it, or care to try to reproduce it on a less complicated machine, before I submit a PR and/or dig more deeply into it? Thanks in advance, -Dave -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Department of Computer Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 14:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15767 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 14:31:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15746 for ; Tue, 24 Nov 1998 14:30:52 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA24638 for hackers@FreeBSD.ORG; Tue, 24 Nov 1998 23:30:46 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A881E14BE; Tue, 24 Nov 1998 20:27:35 +0100 (CET) Date: Tue, 24 Nov 1998 20:27:35 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: First Impression of 3.0-RELEASE Message-ID: <19981124202735.A22588@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <36519613.52DA940@ics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from Doug Rabson on Wed, Nov 18, 1998 at 09:54:24AM +0000 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Doug Rabson: > Try using 'objdump -p libfoo.so'. This will tell you all kinds of useful > stuff about the lib, including its list of dependancies. ...and it is not documented in the manpage, only in "--help". -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 14:31:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15807 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 14:31:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15794 for ; Tue, 24 Nov 1998 14:31:07 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA24646 for hackers@FreeBSD.ORG; Tue, 24 Nov 1998 23:31:01 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 45CFB14BE; Tue, 24 Nov 1998 20:34:41 +0100 (CET) Date: Tue, 24 Nov 1998 20:34:41 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Netscape (Was: Re: Accelerated X 4.1) Message-ID: <19981124203441.B22588@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <199811172219.QAA29498@furrball.dyn.ml.org> <834.911342120@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <834.911342120@verdi.nethelp.no>; from sthaug@nethelp.no on Tue, Nov 17, 1998 at 11:35:20PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to sthaug@nethelp.no: > One small observation here: 4.06 for FreeBSD was very stable for me > under 2.2.7. Under 3.0 stability has gone down the drain. Another one: 4.5 for FreeBSD is the most stable release of Netscape I've ever seen. 4.5b1 was more or less stable (only a core dump sometimes, 4.5b2 was Hell (regular coredump from the dns thingy) but 4.5 has yet to core dump on my system. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 15:55:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24937 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 15:55:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24927 for ; Tue, 24 Nov 1998 15:55:43 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA12085 for ; Tue, 24 Nov 1998 15:55:40 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 24 Nov 1998 15:55:39 -0800 (PST) From: Doug White To: hackers@FreeBSD.ORG Subject: select() a bpf? 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 Here's a tricky one. Can you select() on an appropriately configured bpf device? It would make things infinitely easier for me if it were possible to do that. Looking at the libpcap code, it should be possible, but I just wanted to check around before committing on a architecture decision. Thanks! Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org PS: Brian, you know what I'm talking about :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 16:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27990 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 16:11:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jtrevick.student.simons-rock.edu ([207.51.114.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27960; Tue, 24 Nov 1998 16:11:51 -0800 (PST) (envelope-from root@jtrevick.student.simons-rock.edu) Received: from localhost (root@localhost) by jtrevick.student.simons-rock.edu (8.9.1/8.8.7) with ESMTP id TAA04153; Tue, 24 Nov 1998 19:05:34 -0500 Date: Tue, 24 Nov 1998 19:05:34 -0500 (EST) From: root To: "Kaleb S. KEITHLEY" cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle In-Reply-To: <365ACE9F.8566C16B@ics.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 Out of curiosity, If I have a Linksys NIC and want to do a FTP install of FreeBSD, how would I go about it since support isnt config'ed into the kernel On Tue, 24 Nov 1998, Kaleb S. KEITHLEY wrote: > Joel Ray Holveck wrote: > > > > >>> I also now know why the de probe doesn't print out a message when the > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > >>> probe fails. Which is not to say that I think that's good. On the > > >>> contrary, I think it's bad. C'est la vie. > > >> Printing out an error message when a PCI match fails would be stupid; > > Yup; but then I said as much. > > > >> every PCI device is (currently) presented to every PCI driver until one > > >> claims it. Printing a message when the match failed ("no, not for me") > > >> would produce a useless spew of garbage. > > > You need a pseudo-device at the end of the inquiry chain to catch > > > id's that haven't been caught by the real drivers, and to print > > > out a message ("PCI: no driver: id xxx ..."). > > > > That's catching the wrong set. > > Yes and no. > > > Kaleb wanted the to know the drivers without cards. > > Not really. I wanted to know why the de driver wasn't recognizing my > NIC. According to the FAQ and the Handbook it is supposed to be the > driver for my card. Turns out it's not, but there ought to be a better > way to discover this than by sprinkling the kernel with printfs, or > try-each-one-until-one-succeeds, or > turn-everything-on-to-discover-which-it-is. > > > You're giving us the set of cards without drivers. > > (This is also possibly a useful set, but not what kaleb wanted.) > > Seems to me -- from the cursory look-see that I took while figuring out > my card -- that the PCI ethernet stuff could be unified into something > like a single pci (pseudo?) ethernet device. That could be fun to hack > on. > > > -- > Kaleb > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Nov 24 16:27:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00260 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 16:27:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from varmail.net (varmail.net [203.46.50.11] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29525; Tue, 24 Nov 1998 16:24:44 -0800 (PST) (envelope-from offer@varmail.net) Received: from localhost (root@localhost) by varmail.net (8.8.8/8.8.8) with SMTP id KAA08558; Wed, 25 Nov 1998 10:22:43 +1000 (EST) (envelope-from offer@varmail.net) Date: Wed, 25 Nov 1998 10:22:43 +1000 (EST) Received: by varmail.net (bulk_mailer v1.11); Wed, 25 Nov 1998 02:07:25 +1000 From: melanie@varmail.net To: members@wetmelanie.com Subject: A Great Selection of FREE Adult Sites! Message-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have put together a list of 4 Great Adult sites for your viewing pleasure, all FREE and exclusive. Just click on http://www.varmail.net/1011/ to browse the great, FREE content on offer. Click Here ------------------------------------------------ You are receiving this message because you, or someone pretending to be you, added your contact address to our list. To remove yourself from this mailing list please reply to this message with "Remove" in the subject field. ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 16:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02367 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 16:41:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02360 for ; Tue, 24 Nov 1998 16:41:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA26569; Tue, 24 Nov 1998 16:41:40 -0800 (PST) (envelope-from dillon) Date: Tue, 24 Nov 1998 16:41:40 -0800 (PST) From: Matthew Dillon Message-Id: <199811250041.QAA26569@apollo.backplane.com> To: "David G. Andersen" Cc: hackers@FreeBSD.ORG, vanmaren@cs.utah.edu, sclawson@cs.utah.edu Subject: Re: MFS hang when copying large file to it (vm problem?) References: <13915.12507.346867.242762@torrey.cs.utah.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :(Search for "VM AND messed" in -hackers to get the full thread) : :where Don Lewis stated: : : Do you think this could explaint the MFS related hangs I've been seeing : in 2.1-stable? If I use MFS for /tmp, copy a large file into /tmp, : delete the file, then copy it into /tmp again, the machine will hang. : It responds to pings. It will also respond to ^T until I try to : interrupt a process with ^C. The only way to unhang it is to use : the reset button. : :It's fairly trivial to reproduce, but we're running SMP with our :typical heavily networked environment. Has anyone encountered this, :have a fix for it, or care to try to reproduce it on a less :complicated machine, before I submit a PR and/or dig more deeply into :it? : :Thanks in advance, Check the RSS of the MFS process handling /tmp. You will probably find that it grows and never gets swapped out. I have included one of my patches below. This is an old patch, so you will have to mess with it manually, but it should help with your problem if you can figure out where all the mods go. I never did get this patch into the CVS tree, oh well. -Matt : -Dave : :-- :work: danderse@cs.utah.edu me: angio@pobox.com : University of Utah http://www.angio.net/ : Department of Computer Science : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) Index: mfs_vfsops.c =================================================================== RCS file: /src/FreeBSD-CVS/ncvs/src/sys/ufs/mfs/mfs_vfsops.c,v retrieving revision 1.41 diff -r1.41 mfs_vfsops.c 48a49,50 > #include /* for msync_args */ > #include /* for msync_args */ 432a435,441 > /* > * must mark the calling process as a system process > * so the pager doesn't try to kill it. Doh! And the > * pager may because the resident set size may be huge. > */ > p->p_flag |= P_SYSTEM; > 471c480,481 < * EINTR/ERESTART. --- > * EINTR/ERESTART. It will return EWOULDBLOCK if the timer > * expired. 482,483c492,495 < } < else if (tsleep((caddr_t)vp, mfs_pri, "mfsidl", 0)) --- > } else { > int r = tsleep((caddr_t)vp, mfs_pri, "mfsidl", hz * 10); > > if (r && r != EWOULDBLOCK) 484a497,522 > } > > /* > * we should call msync on the backing store every 30 seconds, > * otherwise the pages are not associated with the file and guess > * what! the syncer never sees them. msync has no effect > * if the backing store is swap, but a big effect if it's a file > * (e.g. an NFS mounted file). > */ > { > static long lsec; > int dt = time_second - lsec; > > if (dt < -30 || dt > 30) { > struct msync_args uap; > > lsec = time_second; > > uap.addr = mfsp->mfs_baseoff; > uap.len = mfsp->mfs_size; > uap.flags = MS_ASYNC; > > msync(curproc, &uap); > } > } > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 17:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07573 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 17:28:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparcy.delanet.com (sparcy.delanet.com [208.9.136.54]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA07535 for ; Tue, 24 Nov 1998 17:27:58 -0800 (PST) (envelope-from stevec@delanet.com) Received: (qmail 13896 invoked from network); 25 Nov 1998 01:23:22 -0000 Received: from unknown (HELO oemcomputer) (208.9.136.17) by sparcy.delanet.com with SMTP; 25 Nov 1998 01:23:22 -0000 Message-ID: <003901be1811$a2777140$118809d0@oemcomputer> From: "Stephen Comoletti" To: "root" , "Kaleb S. KEITHLEY" Cc: , Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle Date: Tue, 24 Nov 1998 20:19:16 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0031_01BE17E7.B5A31280" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0031_01BE17E7.B5A31280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Which model? I have a Lynksys 10bt in a 3.0 box running fine. I had to use a win95/98 boot disk with the lynksys setup util on it..but other than that it runs fine. BSD recognizes it as a KTI card however. I've noticed win95 and 98 both see it as a KTI as well. > >Out of curiosity, If I have a Linksys NIC and want to do a FTP install of >FreeBSD, how would I go about it since support isnt config'ed into the >kernel > >On Tue, 24 Nov 1998, Kaleb S. KEITHLEY wrote: > >> Joel Ray Holveck wrote: >> > >> > >>> I also now know why the de probe doesn't print out a message when the >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > >>> probe fails. Which is not to say that I think that's good. On the >> > >>> contrary, I think it's bad. C'est la vie. >> > >> Printing out an error message when a PCI match fails would be stupid; >> >> Yup; but then I said as much. >> >> > >> every PCI device is (currently) presented to every PCI driver until one >> > >> claims it. Printing a message when the match failed ("no, not for me") >> > >> would produce a useless spew of garbage. >> > > You need a pseudo-device at the end of the inquiry chain to catch >> > > id's that haven't been caught by the real drivers, and to print >> > > out a message ("PCI: no driver: id xxx ..."). >> > >> > That's catching the wrong set. >> >> Yes and no. >> >> > Kaleb wanted the to know the drivers without cards. >> >> Not really. I wanted to know why the de driver wasn't recognizing my >> NIC. According to the FAQ and the Handbook it is supposed to be the >> driver for my card. Turns out it's not, but there ought to be a better >> way to discover this than by sprinkling the kernel with printfs, or >> try-each-one-until-one-succeeds, or >> turn-everything-on-to-discover-which-it-is. >> >> > You're giving us the set of cards without drivers. >> > (This is also possibly a useful set, but not what kaleb wanted.) >> >> Seems to me -- from the cursory look-see that I took while figuring out >> my card -- that the PCI ethernet stuff could be unified into something >> like a single pci (pseudo?) ethernet device. That could be fun to hack >> on. >> >> >> -- >> Kaleb >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > ------=_NextPart_000_0031_01BE17E7.B5A31280 Content-Type: text/x-vcard; name="Stephen C. Comoletti.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Stephen C. Comoletti.vcf" BEGIN:VCARD VERSION:2.1 N:Comoletti;Stephen;C. FN:Stephen C. Comoletti ORG:DelaNET, Inc. TITLE:Asst. Systems Administrator TEL;WORK;VOICE:(302) 326-5800 / (888) DELANET TEL;WORK;FAX:(302) 326-5802 ADR;WORK:;;262 Quigley Boulevard;New Castle;DE;19720;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:262 Quigley = Boulevard=3D0D=3D0ANew Castle, DE 19720=3D0D=3D0AUSA URL: URL:http://www.delanet.com/ EMAIL;PREF;INTERNET:stevec@delanet.com REV:19981125T011915Z END:VCARD ------=_NextPart_000_0031_01BE17E7.B5A31280-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 17:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08748 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 17:38:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08739; Tue, 24 Nov 1998 17:38:03 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA03175; Tue, 24 Nov 1998 20:36:07 -0500 (EST) (envelope-from lee) Message-ID: <19981124203607.A3161@tidalwave.net> Date: Tue, 24 Nov 1998 20:36:07 -0500 From: Lee Cremeans To: Stephen Comoletti , root , "Kaleb S. KEITHLEY" Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle Reply-To: lcremean@tidalwave.net References: <003901be1811$a2777140$118809d0@oemcomputer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <003901be1811$a2777140$118809d0@oemcomputer>; from Stephen Comoletti on Tue, Nov 24, 1998 at 08:19:16PM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 08:19:16PM -0500, Stephen Comoletti wrote: > Which model? I have a Lynksys 10bt in a 3.0 box running fine. I had to use a > win95/98 boot disk with the lynksys setup util on it..but other than that it > runs fine. BSD recognizes it as a KTI card however. I've noticed win95 and 98 > both see it as a KTI as well. FWIW, the Linksys 10BaseT ISA cards I've seen so far are actually made in Taiwan by D-Link. They're stock NE-2000/National 8390x clone cards. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 17:58:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10444 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 17:58:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10438; Tue, 24 Nov 1998 17:58:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02454; Tue, 24 Nov 1998 17:57:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811250157.RAA02454@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Foster, Jim" cc: "'freebsd-questions@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: Re: Getting to Stable and boot floppies In-reply-to: Your message of "Tue, 24 Nov 1998 10:18:08 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 17:57:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > > I am trying to work my way from 2.2.7-Release to 2.2.7-Stable. While most > of my questions were answered by the folks over on FreeBSD-stable, one very > important question (at least to me) was left unanswered. > > I need to boot my machine from a floppy, but I can't seem to find out where > the floppy image will be at to rebuild the disk. Will it be a single file > like boot.flp, or will it be a set of files that need to be installed? I > assume that it will be made after the kernel is re-built. Is that a correct > assumption? Do you boot the kernel off the floppy, or just use the floppy bootblocks? If the latter, there's nothing you need to change. If the former, then you'll need to copy a new kernel onto the floppy as well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 17:59:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10758 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 17:59:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10753 for ; Tue, 24 Nov 1998 17:59:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02468; Tue, 24 Nov 1998 17:58:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811250158.RAA02468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Didier Derny cc: hackers@FreeBSD.ORG Subject: Re: problem with adaptec ANA 6944A TX In-reply-to: Your message of "Tue, 24 Nov 1998 14:13:50 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 17:58:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I now have a patch for the Adaptec/Cogent ANA 6944A TX > > *** if_de.c.orig Tue Nov 24 14:07:25 1998 > --- if_de.c Tue Nov 24 14:08:06 1998 > *************** > *** 2755,2760 **** > --- 2755,2761 ---- > { tulip_identify_znyx_nic, { 0x00, 0xC0, 0x95 } }, > { tulip_identify_cogent_nic, { 0x00, 0x00, 0x92 } }, > { tulip_identify_asante_nic, { 0x00, 0x00, 0x94 } }, > + { tulip_identify_cogent_nic, { 0x00, 0x00, 0xD1 } }, > { tulip_identify_accton_nic, { 0x00, 0x00, 0xE8 } }, > { NULL } > }; > > It works with FreeBSD 3.0-RELEASE The 'de' driver is maintained by Matt Thomas (matt@3am-software.com), you'll want to pass this back to him. If there's no general disagreement, this should probably go into -current and -stable ASAP as an interim patch. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 18:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11114 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 18:02:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jtrevick.student.simons-rock.edu ([207.51.114.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11108; Tue, 24 Nov 1998 18:02:53 -0800 (PST) (envelope-from root@jtrevick.student.simons-rock.edu) Received: from localhost (root@localhost) by jtrevick.student.simons-rock.edu (8.9.1/8.8.7) with ESMTP id UAA04522; Tue, 24 Nov 1998 20:56:53 -0500 Date: Tue, 24 Nov 1998 20:56:52 -0500 (EST) From: root To: lcremean@tidalwave.net cc: Stephen Comoletti , "Kaleb S. KEITHLEY" , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle In-Reply-To: <19981124203607.A3161@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a Linksys EtherFast PCI card On Tue, 24 Nov 1998, Lee Cremeans wrote: > On Tue, Nov 24, 1998 at 08:19:16PM -0500, Stephen Comoletti wrote: > > Which model? I have a Lynksys 10bt in a 3.0 box running fine. I had to use a > > win95/98 boot disk with the lynksys setup util on it..but other than that it > > runs fine. BSD recognizes it as a KTI card however. I've noticed win95 and 98 > > both see it as a KTI as well. > > FWIW, the Linksys 10BaseT ISA cards I've seen so far are actually made in > Taiwan by D-Link. They're stock NE-2000/National 8390x clone cards. > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| > | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 18:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11953 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 18:12:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11947; Tue, 24 Nov 1998 18:12:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02572; Tue, 24 Nov 1998 18:08:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811250208.SAA02572@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: root cc: lcremean@tidalwave.net, Stephen Comoletti , "Kaleb S. KEITHLEY" , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle In-reply-to: Your message of "Tue, 24 Nov 1998 20:56:52 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 18:08:33 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I got a Linksys EtherFast PCI card Older Linksys cards are supported by the 'de' driver; you can tell these because the large chip on the card has "digital" written on it. New ones use a new chipset and require a new driver not yet integrated into FreeBSD. > On Tue, 24 Nov 1998, Lee Cremeans wrote: > > > On Tue, Nov 24, 1998 at 08:19:16PM -0500, Stephen Comoletti wrote: > > > Which model? I have a Lynksys 10bt in a 3.0 box running fine. I had to use a > > > win95/98 boot disk with the lynksys setup util on it..but other than that it > > > runs fine. BSD recognizes it as a KTI card however. I've noticed win95 and 98 > > > both see it as a KTI as well. > > > > FWIW, the Linksys 10BaseT ISA cards I've seen so far are actually made in > > Taiwan by D-Link. They're stock NE-2000/National 8390x clone cards. > > > > -- > > +--------------------------------------------------------------------+ > > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| > > | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 19:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15133 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 19:01:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15128 for ; Tue, 24 Nov 1998 19:01:11 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id EAA12885 for freebsd-hackers@FreeBSD.ORG; Wed, 25 Nov 1998 04:00:53 +0100 (CET) (envelope-from olli) Date: Wed, 25 Nov 1998 04:00:53 +0100 (CET) From: Oliver Fromme Message-Id: <199811250300.EAA12885@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Ambrisko wrote in list.freebsd-hackers: > Oliver Fromme writes: > | It would be nice to have FreeBSD support for those ROMs, too, > | in one way or another. Even if we had a working netboot code, > | many people aren't able to make their own EPROMs. Especially > | those QPGA/FPGA (?) Flash memories required for many PCI cards > | (like the EtherExpress Pro/100) aren't easy to make on your > | own. > > Actually it is pretty easy to do it for the Intel cards since they is > a utility from IBM that programs the flash boot rom on Intel cards. It's not mentioned in intel's docs. They don't even mention at all that it is possible to do something like that. However, it still leaves the problem to get such a flash ROM somewhere. I don't know about the US, but over here in Germany it's not easy to find them. > I've hacked Etherboot to load FreeBSD/aout again and now to load FreeBSD/elf. Is your code available from somewhere? If it's usable, why not commit it? Would make things probably much easier for me. :-) I assume that the FreeBSD kernel will be ELF-only some day, so my own a.out hackery won't work anymore then... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem StЭck Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 20:27:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21916 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 20:27:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21896; Tue, 24 Nov 1998 20:27:43 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA14790; Tue, 24 Nov 1998 22:25:54 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: root , lcremean@tidalwave.net, Stephen Comoletti , "Kaleb S. KEITHLEY" , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle References: <199811250208.SAA02572@dingo.cdrom.com> From: Joel Ray Holveck Date: 24 Nov 1998 22:25:49 -0600 In-Reply-To: Mike Smith's message of "Tue, 24 Nov 1998 18:08:33 -0800" Message-ID: <867lwkxusy.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I got a Linksys EtherFast PCI card > Older Linksys cards are supported by the 'de' driver; you can tell > these because the large chip on the card has "digital" written on it. > New ones use a new chipset and require a new driver not yet integrated > into FreeBSD. Which brings me to a question I've been wondering for a week or so. Is it possible to, at boot time, load lkms? Would it be possible to put, say, the Linksys driver in an lkm and load it with GENERIC to allow just such a thing? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 21:10:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25284 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 21:09:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ksnews.com (venus.ksnews.com [204.233.167.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25275 for ; Tue, 24 Nov 1998 21:09:09 -0800 (PST) (envelope-from jeverett@ksnews.com) Received: from charli (199.240.187.67) by ksnews.com with SMTP (Eudora Internet Mail Server 2.0); Tue, 24 Nov 1998 23:13:53 -0600 Message-Id: <1.5.4.32.19981125050622.0067c018@mailhost.ksnews.com> X-Sender: jeverett@mailhost.ksnews.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Nov 1998 23:06:22 -0600 To: freebsd-hackers@FreeBSD.ORG From: "Wilma J. Everett" Subject: I need help Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have reported this same message 7 times and I do not know what else to do, I am not sure who to report it to. When I try to open my own uploaded files in the geobuilder graphics, backgrounds, ect. I get messages saying: An internal error has occurred in the server. Please report the following information in a bug report: java.lang.NullPointerException at com.geocities.geobuilder.WebPage.renderEditMode(Compiled Code) at com.geocities.geobuilder.WebPage.error(Compiled Code) at com.geocities.geobuilder.WebPage.doAction(Compiled Code) at com.geocities.geobuilder.Server.handleRequest(Compiled Code) at com.geocities.geobuilder.WebClient.run(Compiled Code) at java.lang.Thread.run(Compiled Code) Please tell me what this means if you would be so kind, and what to do about it? I do not know what caused this but I need it corrected so I can continue working on my pages. The site is at SouthBeach/Port/3782 username:silvershadow3 Also I recieve a similar message when I try to import a file I have already published, for instance, the site at SouthBeach/3782/index.html I know there must be someplace I can get help but have not been able to find it yet, can you please help me with this problem or tell me what to do about it? I do not know very much about html and cant do this by myself. Please help me if you can or tell me where to get proper help. thank you, Pat everett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 24 21:22:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26423 for freebsd-hackers-outgoing; Tue, 24 Nov 1998 21:22:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26417 for ; Tue, 24 Nov 1998 21:22:33 -0800 (PST) (envelope-from J_Shevland@TurnAround.com.au) Received: from simbarchi (dhcp110.turnaround.com.au [192.168.1.110] (may be forged)) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with SMTP id QAA11007; Wed, 25 Nov 1998 16:27:20 +1100 (EST) (envelope-from J_Shevland@TurnAround.com.au) Reply-To: From: "Joe Shevland" To: "Wilma J. Everett" , Subject: RE: I need help Date: Wed, 25 Nov 1998 16:21:26 +1100 Message-ID: <001101be1833$72eff600$6e01a8c0@simbarchi.turnaround.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <1.5.4.32.19981125050622.0067c018@mailhost.ksnews.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has nothing whatsoever to do with FreeBSD, let alone -hackers. Not surprised you haven't had any replies if you post this kind of problem to unrelated forums. > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Wilma J. Everett > Sent: Wednesday, November 25, 1998 4:06 PM > To: freebsd-hackers@FreeBSD.ORG > Subject: I need help > > > I have reported this same message 7 times and I do not know > what else > to do, I am not sure who to report it to. When I try to open my > own uploaded > files in the geobuilder > graphics, backgrounds, ect. I get messages saying: > > > > An internal error has occurred in > the server. Please report the > following information in a bug > report: > > java.lang.NullPointerException > at com.geocities.geobuilder.WebPage.renderEditMode(Compiled Code) > at com.geocities.geobuilder.WebPage.error(Compiled Code) > at com.geocities.geobuilder.WebPage.doAction(Compiled Code) > at com.geocities.geobuilder.Server.handleRequest(Compiled Code) > at com.geocities.geobuilder.WebClient.run(Compiled Code) > at java.lang.Thread.run(Compiled Code) > > Please tell me what this means if you would be so kind, and what > to do about it? It is a problem with the Java applet they're using; it is having a problem with an object reference of something similar and spitting out your NULL pointer exception. Report it to one of the Geocities area masters or whatever they're called. > I do not know what caused this but I need it corrected so I can continue > working on my pages. The site is at SouthBeach/Port/3782 > username:silvershadow3 > > Also I recieve a similar message when I try to import a file I > have already > published, for instance, the site at SouthBeach/3782/index.html > > I know there must be someplace I can get help but have not been > able to find > it yet, can you please help me with this problem or tell me what > to do about > it? I do not know very much about html and cant do this by myself. > Please help me if you can or tell me where to get proper help. > thank you, > Pat everett > The fact that this is coming out after the '> An internal error has occurred in...' message leads me to thinking its a server-side servlet or application bug. Again, I'd just report it to the Geocities people and see what they've got to say. The stack trace you've included would be useful to _them_. Joe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 02:50:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20878 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 02:50:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m1-12-dbn.dial-up.net [196.34.155.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20870 for ; Wed, 25 Nov 1998 02:50:28 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA14976 for freebsd-hackers@FreeBSD.ORG; Wed, 25 Nov 1998 12:12:10 +0200 (SAT) From: Robert Nordier Message-Id: <199811251012.MAA14976@ceia.nordier.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811250300.EAA12885@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Nov 25, 98 04:00:53 am" To: freebsd-hackers@FreeBSD.ORG Date: Wed, 25 Nov 1998 12:12:08 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > Doug Ambrisko wrote in list.freebsd-hackers: > > I've hacked Etherboot to load FreeBSD/aout again and now to load FreeBSD/elf. > > Is your code available from somewhere? If it's usable, why not > commit it? Would make things probably much easier for me. :-) > > I assume that the FreeBSD kernel will be ELF-only some day, so > my own a.out hackery won't work anymore then... We are already actively examining netboot options as part of the new boot code project. (I've checked out several possibilities myself in the last six months, and Mike Smith has had the whole issue in mind for considerably longer.) The new boot/loader already provides a generic solution by making both disk and network devices available to boot from. So the issue is mainly that of low-level NIC support. However alternatives choices are always good; and this is one of the reasons the ports collection exists. There's actually just little particular benefit in maintaining such code in the source tree itself. When an ELF kernel becomes standard, I'd be strongly in favor of moving even existing code like dosboot into ports. There is precedence for this: mkisofs, for instance. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 05:58:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05671 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 05:58:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05658 for ; Wed, 25 Nov 1998 05:58:26 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id IAA10947; Wed, 25 Nov 1998 08:58:11 -0500 (EST) Date: Wed, 25 Nov 1998 08:58:11 -0500 (EST) From: Snob Art Genre Reply-To: ben@rosengart.com To: Marius Bendiksen cc: John Polstra , hackers@FreeBSD.ORG, joelh@gnu.org Subject: Re: FreeBSD on i386 memory model In-Reply-To: <3.0.5.32.19981124092630.00b7b1e0@mail.scancall.no> 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, 24 Nov 1998, Marius Bendiksen wrote: > I know that. I'm simply wondering how much extra complexity we would be > adding, and what kind of impact it would have on syscall times. Why don't you implement it and find out? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 06:37:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09983 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 06:37:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA09976; Wed, 25 Nov 1998 06:37:22 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA25244; Wed, 25 Nov 1998 09:40:00 -0500 From: Bill Paul Message-Id: <199811251440.JAA25244@skynet.ctr.columbia.edu> Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle To: mike@smith.net.au (Mike Smith) Date: Wed, 25 Nov 1998 09:39:59 -0500 (EST) Cc: lcremean@tidalwave.net, stevec@dalnet.com, kaleb@ics.com, questions@FreeBSD.ORG, hackers@FreeBSD.ORG, root@jtrevick.student.simons-rock.edu In-Reply-To: <199811250208.SAA02572@dingo.cdrom.com> from "Mike Smith" at Nov 24, 98 06:08:33 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Mike Smith had to walk into mine and say: > > I got a Linksys EtherFast PCI card > > Older Linksys cards are supported by the 'de' driver; you can tell > these because the large chip on the card has "digital" written on it. > > New ones use a new chipset and require a new driver not yet integrated > into FreeBSD. Aw c'mon Mike, why didn't you tell him how to get the driver so he can test it? I need testers. First of all, the actual model of the card should be LNE100TX. Look closely at the largest chip on the card: if it says LINKSYS and 82c169 on it, then it's a PNIC chip and you need the pn driver from: http://www.freebsd.org/~wpaul/PNIC There's code for FreeBSD 3.0 and 2.2.x, and a README to explain how to make a custom kernel with the driver in it. BTW, there's a reason I've held off on merging this driver for the moment: I've just recently figured out how to crank the transmit performance up to 11MB/sec on these tulip clones and I want to fine tune things a little. If you have problems, report them to wpaul@skynet.ctr.columbia.edu. -Bill P.S. If somebody knows where I can get a Macronix 98713 card (that's 98713, _NOT_ 98713A) or has one they aren't using, please get in touch with me. The 98713 is a little different from the 98713A: it should receive and transmit okay with the mx driver, but the NWAY support is broken and I can't fix it without a sample card. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 08:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19413 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 08:35:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19388; Wed, 25 Nov 1998 08:35:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00590; Wed, 25 Nov 1998 08:31:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251631.IAA00590@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck cc: Mike Smith , root , lcremean@tidalwave.net, Stephen Comoletti , "Kaleb S. KEITHLEY" , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle In-reply-to: Your message of "24 Nov 1998 22:25:49 CST." <867lwkxusy.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 08:31:13 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I got a Linksys EtherFast PCI card > > Older Linksys cards are supported by the 'de' driver; you can tell > > these because the large chip on the card has "digital" written on it. > > New ones use a new chipset and require a new driver not yet integrated > > into FreeBSD. > > Which brings me to a question I've been wondering for a week or so. > Is it possible to, at boot time, load lkms? Would it be possible to > put, say, the Linksys driver in an lkm and load it with GENERIC to > allow just such a thing? Yes, it's possible. The new bootloader makes it easier again. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 09:24:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22832 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 09:24:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22827; Wed, 25 Nov 1998 09:24:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA00932; Wed, 25 Nov 1998 09:19:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251719.JAA00932@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: mike@smith.net.au (Mike Smith), lcremean@tidalwave.net, stevec@dalnet.com, kaleb@ics.com, questions@FreeBSD.ORG, hackers@FreeBSD.ORG, root@jtrevick.student.simons-rock.edu Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle In-reply-to: Your message of "Wed, 25 Nov 1998 09:39:59 EST." <199811251440.JAA25244@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 09:19:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of all the gin joints in all the towns in all the world, Mike Smith had > to walk into mine and say: > > > > I got a Linksys EtherFast PCI card > > > > Older Linksys cards are supported by the 'de' driver; you can tell > > these because the large chip on the card has "digital" written on it. > > > > New ones use a new chipset and require a new driver not yet integrated > > into FreeBSD. > > Aw c'mon Mike, why didn't you tell him how to get the driver so he can > test it? I need testers. Whoops, sorry. 8( > P.S. If somebody knows where I can get a Macronix 98713 card (that's > 98713, _NOT_ 98713A) or has one they aren't using, please get in > touch with me. The 98713 is a little different from the 98713A: > it should receive and transmit okay with the mx driver, but the > NWAY support is broken and I can't fix it without a sample card. I was actually looking for these the other day for FTL. Unfortunately the same white-box supplier I got the last one from (went to Matt Thomas) is now shipping cards using the ASIX AX88140. (This looks like another Tulip clone; possibly more faithful than some of the others.) Should I grab one of these while I can? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 10:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26782 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 10:21:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26777 for ; Wed, 25 Nov 1998 10:21:20 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA18210 for ; Wed, 25 Nov 1998 10:12:14 -0800 (PST) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdj18193; Wed Nov 25 18:12:04 1998 Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id KAA51210 for freebsd-hackers@FreeBSD.ORG; Wed, 25 Nov 1998 10:11:34 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199811251811.KAA51210@whistle.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811250300.EAA12885@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Nov 25, 98 04:00:53 am" To: freebsd-hackers@FreeBSD.ORG Date: Wed, 25 Nov 1998 10:11:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (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 Oliver Fromme writes: | Doug Ambrisko wrote in list.freebsd-hackers: | > Actually it is pretty easy to do it for the Intel cards since they is | > a utility from IBM that programs the flash boot rom on Intel cards. | | It's not mentioned in intel's docs. They don't even mention at | all that it is possible to do something like that. | | However, it still leaves the problem to get such a flash ROM | somewhere. I don't know about the US, but over here in Germany | it's not easy to find them. Yep here in Silicon Valley (US) we can go to the corner store and pick them up! The utility is at: ftp://ftp.networking.ibm.com/pub/products/lanprods/ethernet/etpflsh.exe Part is: Intel 28F020 | > I've hacked Etherboot to load FreeBSD/aout again and now to load FreeBSD/elf. | | Is your code available from somewhere? If it's usable, why not | commit it? Would make things probably much easier for me. :-) | | I assume that the FreeBSD kernel will be ELF-only some day, so | my own a.out hackery won't work anymore then... I've stalled on it since I made some gross hacks to make the a.out stuff work that was messy. I need to clean it up some more. I promise to clean it up this weekend if my daughter doesn't decide to come into the world this weekend . If you could review and test it that would be great. The worst part is that it needs to be built under linux development. The good part is they support a lot more NIC's then we do. There is atleast one nagging bug that I've been running into lately with memory corruption of variables in the etherboot code. I've fixed a few problems in that area but atleast one persists. Also I've been waiting in the wings to see what will become of FreeBSD's netboot code. It seems to be somewhat orphaned and won't work with elf kernels and the supported NIC list is weak. I guess worst case I could patch it to support elf kernel booting. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 10:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27845 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 10:41:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27839 for ; Wed, 25 Nov 1998 10:41:26 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA18848; Wed, 25 Nov 1998 10:33:13 -0800 (PST) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdS18841; Wed Nov 25 18:33:04 1998 Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id KAA79623; Wed, 25 Nov 1998 10:32:09 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199811251832.KAA79623@whistle.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811251012.MAA14976@ceia.nordier.com> from Robert Nordier at "Nov 25, 98 12:12:08 pm" To: rnordier@nordier.com (Robert Nordier) Date: Wed, 25 Nov 1998 10:32:08 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Robert Nordier writes: | When an ELF kernel becomes standard, I'd be strongly in favor of | moving even existing code like dosboot into ports. There is | precedence for this: mkisofs, for instance. That sounds reasonable, I guess I could make the etherboot stuff into a port and put the patches in there for loading FreeBSD aout/elf kernels. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 10:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28129 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 10:46:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA28122 for ; Wed, 25 Nov 1998 10:46:16 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGPVHZEJ; Wed, 25 Nov 98 18:46:12 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125194556.00998cb0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 19:45:56 +0100 To: ben@rosengart.com From: Marius Bendiksen Subject: Re: FreeBSD on i386 memory model Cc: hackers@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981124092630.00b7b1e0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Why don't you implement it and find out? (1) I lack the required knowledge of BSD internals (2) I doubt I have sufficient mastery of C to rewrite libc (3) If the effort is going to be wasted (ie. if noone will commit it), there's no point in doing so. Correct at least two of the above, and I'll give it my best shot, and get back to you. I assume it would be -quite- a lot of work? --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 11:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29337 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 11:01:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m1-29-dbn.dial-up.net [196.34.155.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29330 for ; Wed, 25 Nov 1998 11:00:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA19622; Wed, 25 Nov 1998 20:59:00 +0200 (SAT) From: Robert Nordier Message-Id: <199811251859.UAA19622@ceia.nordier.com> Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811251832.KAA79623@whistle.com> from Doug Ambrisko at "Nov 25, 98 10:32:08 am" To: ambrisko@whistle.com (Doug Ambrisko) Date: Wed, 25 Nov 1998 20:58:56 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Ambrisko wrote: > Robert Nordier writes: > | When an ELF kernel becomes standard, I'd be strongly in favor of > | moving even existing code like dosboot into ports. There is > | precedence for this: mkisofs, for instance. > > That sounds reasonable, I guess I could make the etherboot stuff into > a port and put the patches in there for loading FreeBSD aout/elf kernels. I'm sure folks would appreciate it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 11:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04310 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 11:57:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04304 for ; Wed, 25 Nov 1998 11:57:26 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id PAA08293; Wed, 25 Nov 1998 15:01:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 25 Nov 1998 15:01:13 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Marius Bendiksen cc: ben@rosengart.com, hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model In-Reply-To: <3.0.5.32.19981125194556.00998cb0@mail.scancall.no> 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, 25 Nov 1998, Marius Bendiksen wrote: > >Why don't you implement it and find out? > > (1) I lack the required knowledge of BSD internals > (2) I doubt I have sufficient mastery of C to rewrite libc > (3) If the effort is going to be wasted (ie. if noone will commit it), > there's no point in doing so. > > Correct at least two of the above, and I'll give it my best shot, and get > back to you. I assume it would be -quite- a lot of work? > The syscall entry into the kernel is done via a macro afaik, redefine it, and code the alternate entry into the kernel. If you wanted a libc that you could "move" between machines..., you could recode the libc bootstrap to sysctl the processor model number and provide a jump point to either entry point. However, you then slow down both entry methods by the cost of an additional jump/return and you cause the instruction cache to be less effective as you jump execution around in memory. Another idea is 2 lib directories, one optimized for <= 486 and the other optimized for > 486, then you double the amount of space you need for shared libs... Not worth the cycles unless you were doing long term modeling, and then, as asked before, why use a 486? It could be made into a Makeworld option perhaps? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 12:01:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04608 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 12:01:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sol. (toscana-209-79-56-101.snfc21.pacbell.net [209.79.56.101]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA04597 for ; Wed, 25 Nov 1998 12:01:30 -0800 (PST) (envelope-from myers@iname.com) From: myers@iname.com Received: from iname.com by sol. (SMI-8.6/SMI-SVR4) id MAA01573; Wed, 25 Nov 1998 12:00:05 -0800 Message-Id: <199811252000.MAA01573@sol.> Date: Wed, 25 Nov 1998 12:00:02 -0800 (PST) Subject: Non-kernel hacker needs serial help! 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 Folks: Help a non-kernel hacker out here. I've got an ancient HP DeskWriter printer with a serial interface. It came off a Macintosh. Specs are 57.6K, 8N1. Under Win98, I can make it print, but only after manually specifying a slowed transfer rate from the UART (under "Advanced Port Settings", or something like that). However, I can't make it print at all from my FreeBSD box. Or rather, it will print, but only the first two inches or so of the first page. After that, it just hangs. So, I speculate: Macs must have a non-standard H/W handshaking protocol. The FreeBSD box never sees a "buffer full" message from the printer, so it blindly blasts out the bits, but the printer barfs on them, and ends up flushing its buffer and giving up. It only makes it through two inches of output before dying. My solution: introduce a delay into the serial port output stream, just like Win98 lets me do. I go kernel hacking. I locate /usr/src/sys/i386/isa/sio.c, find the function siointr1, and throw in two DELAY(1000) statements, like this: in function siointr1... if (com->tx_fifo_size > 1) { u_int ocount; ocount = com->obufq.l_tail - ioptr; if (ocount > com->tx_fifo_size) ocount = com->tx_fifo_size; com->bytes_out += ocount; do { outb(com->data_port, *ioptr++); /* dcm, 11/25/98 */ -----> DELAY(1000); } while (--ocount != 0); } else { outb(com->data_port, *ioptr++); ++com->bytes_out; /* dcm, 11/25/98 */ -----> DELAY(1000); } Why DELAY(1000)? Who knows? This is blind hacking! But know what? It works! Long documents now print out fine from my DeskWriter. But, those of you who *are* kernel hackers are probably snickering in the background at the moment. Unlike me, you realized that introducing a delay at this point in the code (interrupt mode, I'm presuming) stalls processing for everything else. Network transfers, for example, become annoyingly slow while this box is printing. My question, to make a long story short: what is the "proper" way to slow down the serial ports in the manner I've described, without bogging down all other interrupt processing? Thanks for reading this far. -David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 12:29:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07275 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 12:29:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07269 for ; Wed, 25 Nov 1998 12:29:17 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Thu, 26 Nov 1998 07:28:20 +1100 Date: Thu, 26 Nov 1998 07:28:49 +1100 From: Peter Jeremy Subject: Re: Kernel threads To: hackers@FreeBSD.ORG Message-Id: <98Nov26.072820est.40325@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998 00:52:18 -0800 (PST), Matthew Dillon wrote: [Redesign the entire KVM subsystem] > I just don't know how feasible it all is... it would mean a huge amount of > rewriting. And I don't suppose you currently have the time to examine it in detail :-). > The disadvantage of this > scheme is that it limits main memory to around 2GB on a 32 bit machine. Whilst I don't believe this is a serious problem at present, I can see that it might be in a couple of years. I presume that the problem is that something is signed - although I'm not sure what in particular. Is there a real reason for that object to be signed? If it's just to allow a `-1 on error', could it be unsigned with 0xFFFFFFFF reserved? Alternatively, could it have a granularity larger than 1 byte? > The benefits cascade very quickly.... if one is willing to give up > 2GB > memory configurations on 32 bit cpus. In which case it would seem worthwhile doing some more detailed examination. In particular, how much effort would be involved and whether the 2GB boundary can be avoided. Now 3.0 is nearly stable, we need a new bleeding edge for -current. This sounds like a good start for FreeBSD 4.x :-). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 12:51:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09545 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 12:51:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA09535 for ; Wed, 25 Nov 1998 12:51:25 -0800 (PST) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig1.fw.att.com by cagw1.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Wed Nov 25 15:20 EST 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id PAA00214 for ; Wed, 25 Nov 1998 15:29:53 -0500 (EST) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1460.8) id ; Wed, 25 Nov 1998 15:29:53 -0500 Message-ID: To: myers@iname.com, freebsd-hackers@FreeBSD.ORG Subject: RE: Non-kernel hacker needs serial help! Date: Wed, 25 Nov 1998 15:29:52 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: myers@iname.com [SMTP:myers@iname.com] > > if (com->tx_fifo_size > 1) { > u_int ocount; > > ocount = com->obufq.l_tail - ioptr; > if (ocount > com->tx_fifo_size) > ocount = com->tx_fifo_size; > com->bytes_out += ocount; > do { > outb(com->data_port, *ioptr++); > /* dcm, 11/25/98 */ > -----> DELAY(1000); > } while (--ocount != 0); > } else { > outb(com->data_port, *ioptr++); > ++com->bytes_out; > /* dcm, 11/25/98 */ > -----> DELAY(1000); > } > > > > Why DELAY(1000)? Who knows? This is blind hacking! But know what? > It works! Long documents now print out fine from my DeskWriter. But, > those of you who *are* kernel hackers are probably snickering in the > background at the moment. Unlike me, you realized that introducing a > delay at this point in the code (interrupt mode, I'm presuming) stalls > processing for everything else. Network transfers, for example, become > annoyingly slow while this box is printing. > > My question, to make a long story short: what is the "proper" way to > slow down the serial ports in the manner I've described, without bogging > down all other interrupt processing? > DELAY(1000) makes an approximately 1ms delay. The best thing you can achieve with the timer clock without speeding it up is 10ms. You can try something like this (this is just an example of logic, there is no guarantee that it will work exactly in this form): struct somewhat_com { ... int charcnt; }; static void comdelayedwrite(com) struct somewhat_com *com; { int s; char *ioptr; s=spltty(); /* calculate ioptr here and make sure the transmitter is idle, then: */ outb(com->data_port, *ioptr++); com->charcnt=0; splx(s); } .... /* in any place before outb(com->data_port, *ioptr++) */ /* you may want to increase the number "10" to get slightly faster printing */ if(com->charcnt<10) { com->charcnt++; timeout( (timeout_t *)comdelayedwrite, (void *)com, HZ/100); return; } else outb(com->data_port, *ioptr++); .... Or may be you can just get a proper 7-wire cable and configure the RTS/CTS handshake on the port (see man stty). -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 13:35:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13340 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 13:35:05 -0800 (PST) (envelope-from owner-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 (8.8.8/8.8.8) with ESMTP id NAA13323 for ; Wed, 25 Nov 1998 13:34:59 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA06718; Wed, 25 Nov 1998 21:34:34 GMT (envelope-from nik) Message-ID: <19981125213433.14108@nothing-going-on.org> Date: Wed, 25 Nov 1998 21:34:33 +0000 From: Nik Clayton To: hackers@FreeBSD.ORG Subject: FreeBSD and the Euro? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Has anyone looked at the Linux Euro patch available at I confess I know almost nothing about how this issue is going to affect FreeBSD (except for the requirement for a new character for the euro currency, which looks like a 'C' and '=' superimposed). I'm mentioning it in the hope that someone else does. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 14:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19710 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 14:33:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19680 for ; Wed, 25 Nov 1998 14:33:20 -0800 (PST) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by samizdat.uucom.com (8.9.1/8.9.0) id RAA14365; Wed, 25 Nov 1998 17:33:11 -0500 To: freebsd-hackers@FreeBSD.ORG Subject: 2.2.7 on K6/2, SCSI ncr0 hangs/aborts at boot, then recovers From: Chris Shenton Date: 25 Nov 1998 17:33:11 -0500 Message-ID: <86iug3l7x4.fsf@samizdat.uucom.com> Lines: 37 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [should this go to -stable or -scsi lists instead?] I got a FIC 503+ mobo with AMD K6/2-300 CPU and an older NCR PCI scsi controller. It couldn't boot initially because -- and I'm not sure I'm using the right terms -- neither NCR nor the mobo had boot code in BIOS for the NCR. So I flashed the mobo with a BIOS to which someone added NCR boot code. It can now see the scsi disks and begin to boot. (I don't have any IDE so I was losing totally before this). But when it boots, it goes through the boot loader/selector, finds the boot code, and scans the devices, and tries to mount / from the disk. Then it just hangs for a minute -- but finally reports and error and completes the boot. I'm very concerned this is going to cause me mucho trouble in the future but it does seem to work, in a sketchy way. Here's my transcript of the boot sequence from dmesg: [scans devices] changing root device to sd1s2a [hangs for about 60 seconds] ncr0: aborting job ... ncr0:2: ERROR (90:0) (8-0-0) (0/3) @ (script 5b4:50000000). ncr0: script cmd = 80000000 ncr0: regdump: de 00 00 03 47 00 06 1f 35 08 80 00 90 00 0f 02. ncr0: restart (fatal error). sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f051e000. sd1(ncr0:2:0): 10.0 MB/s (100 ns, offset 8) WARNING: / was not properly dismounted. [...] I don't understand how it can read the boot code from the disk with no complaints, but then has this weird hang when mounting /. This is on 2.2.7-RELEASE. Suggestions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 14:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20208 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 14:35:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20199 for ; Wed, 25 Nov 1998 14:35:49 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id RAA08021; Wed, 25 Nov 1998 17:35:18 -0500 (EST) Date: Wed, 25 Nov 1998 17:35:18 -0500 (EST) From: Snob Art Genre Reply-To: ben@rosengart.com To: Nik Clayton cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? In-Reply-To: <19981125213433.14108@nothing-going-on.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 Wed, 25 Nov 1998, Nik Clayton wrote: > currency, which looks like a 'C' and '=' superimposed). I'm mentioning ^^^^^^^^^^^^^^^^^^^^^^^ Somehow I knew Commodore would eventually take over the world. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 15:26:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26952 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 15:26:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26926 for ; Wed, 25 Nov 1998 15:25:59 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA07142 for hackers@FreeBSD.ORG; Thu, 26 Nov 1998 00:25:44 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9F08215BC; Thu, 26 Nov 1998 00:18:33 +0100 (CET) Date: Thu, 26 Nov 1998 00:18:33 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? Message-ID: <19981126001833.A10601@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19981125213433.14108@nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <19981125213433.14108@nothing-going-on.org>; from Nik Clayton on Wed, Nov 25, 1998 at 09:34:33PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nik Clayton: > I confess I know almost nothing about how this issue is going to affect > FreeBSD (except for the requirement for a new character for the euro > currency, which looks like a 'C' and '=' superimposed). I'm mentioning Apart from the fact that you need new fonts and new syscons/xmodmap entries, why does Linux need a patch ? (I'm not connected right now so I can't go to the site). Anyway, we already have a ISO-8859-15 (aka Latin9) font for syscons in the tree. -------- roberto 1998/11/05 07:35:39 PST Modified files: share/syscons/fonts INDEX.fonts Added files: share/syscons/fonts iso15-thin-8x16.fnt Log: New ISO-8859-15 thin font. It includes some missing characters from 8859-1 (like OE & oe diphthong) and the Euro character. It also includes the VTxx semi-graphic characters. -------- I plan to upgrade the fr.iso syscons keyboard map to put the Euro code on AltGr-E (unless there is any objection ?). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 16:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04681 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 16:41:06 -0800 (PST) (envelope-from owner-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 (8.8.8/8.8.8) with ESMTP id QAA04670 for ; Wed, 25 Nov 1998 16:40:59 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id XAA15017; Wed, 25 Nov 1998 23:57:34 GMT (envelope-from nik) Message-ID: <19981125235734.51261@nothing-going-on.org> Date: Wed, 25 Nov 1998 23:57:34 +0000 From: Nik Clayton To: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? References: <19981125213433.14108@nothing-going-on.org> <19981126001833.A10601@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19981126001833.A10601@keltia.freenix.fr>; from Ollivier Robert on Thu, Nov 26, 1998 at 12:18:33AM +0100 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 26, 1998 at 12:18:33AM +0100, Ollivier Robert wrote: > According to Nik Clayton: > > I confess I know almost nothing about how this issue is going to affect > > FreeBSD (except for the requirement for a new character for the euro > > currency, which looks like a 'C' and '=' superimposed). I'm mentioning > > Apart from the fact that you need new fonts and new syscons/xmodmap > entries, why does Linux need a patch ? Don't know. As I say, I know very little about this, but was hoping someone would. If we are ready (or as ready as we can be) for it, then it's nice to know because a) We can put a "Euro-ready" logo on the web site b) Someone (me, or someone else, I don't mind) can put together something for the Handbook that explains what this all means. > Anyway, we already have a ISO-8859-15 (aka Latin9) font for syscons in the > tree. That's part of it. But I don't know if that's all that's required. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 16:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05510 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 16:48:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05453 for ; Wed, 25 Nov 1998 16:47:50 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.50]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA17337 for ; Wed, 25 Nov 1998 19:50:15 +0500 Message-ID: <365CA57D.CD0117A5@bachue.usc.unal.edu.co> Date: Wed, 25 Nov 1998 19:49:01 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Labview for Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think someone in this list was looking forward to see Labview for FreeBSD. Maybe this (from SAL) may help: http://www.natinst.com/linux/release.html#Resources cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 17:26:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08464 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 17:26:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA08456 for ; Wed, 25 Nov 1998 17:26:37 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 23145 invoked by uid 1000); 26 Nov 1998 01:28:13 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <365CA57D.CD0117A5@bachue.usc.unal.edu.co> Date: Wed, 25 Nov 1998 20:28:13 -0500 (EST) X-Face: *0^4Iw) To: hackers@FreeBSD.ORG Subject: RE: Labview for Linux Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-Nov-98 Pedro F. Giffuni wrote: > I think someone in this list was looking forward to see Labview for > FreeBSD. Maybe this (from SAL) may help: > > http://www.natinst.com/linux/release.html#Resources It says it requires glibc2 and POSIX threads for LabView 5 but also comes with v4.1.1 on the CD for libc5 based systems. I sent a note to my National Instruments rep to see if I can get him to bring me a copy in the next week or so. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 17:32:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08972 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 17:32:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phrozen.org (c61781-a.lakwod2.co.home.com [24.1.12.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08952 for ; Wed, 25 Nov 1998 17:32:00 -0800 (PST) (envelope-from geniusj@phrozen.org) Received: from localhost (geniusj@localhost) by phrozen.org (8.8.7/8.8.7) with ESMTP id SAA02012; Wed, 25 Nov 1998 18:29:58 -0700 Date: Wed, 25 Nov 1998 18:29:58 -0700 (MST) From: # rm -rf * To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? In-Reply-To: <19981126001833.A10601@keltia.freenix.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 On Thu, 26 Nov 1998, Ollivier Robert wrote: > According to Nik Clayton: > > I confess I know almost nothing about how this issue is going to affect > > FreeBSD (except for the requirement for a new character for the euro > > currency, which looks like a 'C' and '=' superimposed). I'm mentioning > > Apart from the fact that you need new fonts and new syscons/xmodmap > entries, why does Linux need a patch ? (I'm not connected right now so I > can't go to the site). [SNIP] I'm confused on how your sending this email than.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 19:13:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17952 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 19:13:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17763 for ; Wed, 25 Nov 1998 19:13:20 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id EAA15394; Thu, 26 Nov 1998 04:10:05 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811260310.EAA15394@ocean.campus.luth.se> Subject: Re: FreeBSD and the Euro? In-Reply-To: <19981126001833.A10601@keltia.freenix.fr> from Ollivier Robert at "Nov 26, 98 00:18:33 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Thu, 26 Nov 1998 04:10:05 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ollivier Robert: > Apart from the fact that you need new fonts and new syscons/xmodmap > entries, why does Linux need a patch ? (I'm not connected right now so I > can't go to the site). It doesn't. The "patch" is a tarfile of fonts and keymaps, etc. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 21:15:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25935 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 21:15:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25929 for ; Wed, 25 Nov 1998 21:15:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00609; Wed, 25 Nov 1998 21:13:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260513.VAA00609@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: myers@iname.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Non-kernel hacker needs serial help! In-reply-to: Your message of "Wed, 25 Nov 1998 12:00:02 PST." <199811252000.MAA01573@sol.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:13:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Folks: > > Help a non-kernel hacker out here. I've got an ancient HP DeskWriter > printer with a serial interface. It came off a Macintosh. Specs are > 57.6K, 8N1. Under Win98, I can make it print, but only after > manually specifying a slowed transfer rate from the UART (under > "Advanced Port Settings", or something like that). However, I can't > make it print at all from my FreeBSD box. > > Or rather, it will print, but only the first two inches or so of the > first page. After that, it just hangs. > > So, I speculate: Macs must have a non-standard H/W handshaking > protocol. The FreeBSD box never sees a "buffer full" message from the > printer, so it blindly blasts out the bits, but the printer barfs on > them, and ends up flushing its buffer and giving up. It only makes it > through two inches of output before dying. > > My solution: introduce a delay into the serial port output stream, just > like Win98 lets me do. I go kernel hacking. I locate > /usr/src/sys/i386/isa/sio.c, find the function siointr1, and throw in > two DELAY(1000) statements, like this: Bad. Fix your cable and the port settings to handshake properly. There's probably a Linux FAQ about this somewhere; most of it should be applicable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 21:26:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26479 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 21:26:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26471 for ; Wed, 25 Nov 1998 21:26:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00686; Wed, 25 Nov 1998 21:24:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260524.VAA00686@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Shenton cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.7 on K6/2, SCSI ncr0 hangs/aborts at boot, then recovers In-reply-to: Your message of "25 Nov 1998 17:33:11 EST." <86iug3l7x4.fsf@samizdat.uucom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:24:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But when it boots, it goes through the boot loader/selector, finds the > boot code, and scans the devices, and tries to mount / from the disk. > Then it just hangs for a minute -- but finally reports and error and > completes the boot. I'm very concerned this is going to cause me mucho > trouble in the future but it does seem to work, in a sketchy way. When you say "in a sketchy way", do you mean that the system is working OK from this point on, or are there other problems? > Here's my transcript of the boot sequence from dmesg: > > [scans devices] > > changing root device to sd1s2a > > [hangs for about 60 seconds] > > ncr0: aborting job ... > ncr0:2: ERROR (90:0) (8-0-0) (0/3) @ (script 5b4:50000000). > ncr0: script cmd = 80000000 > ncr0: regdump: de 00 00 03 47 00 06 1f 35 08 80 00 90 00 0f 02. > ncr0: restart (fatal error). > sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f051e000. > sd1(ncr0:2:0): 10.0 MB/s (100 ns, offset 8) > WARNING: / was not properly dismounted. > [...] > > > I don't understand how it can read the boot code from the disk with no > complaints, but then has this weird hang when mounting /. Different code talking to the device; the bootstrap uses the BIOS, while the kernel uses its own driver. It looks like the NCR part is left in a funny state that takes a restart (several?) to recover from. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 25 23:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05520 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 23:35:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05512 for ; Wed, 25 Nov 1998 23:35:33 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA28592 for hackers@FreeBSD.ORG; Thu, 26 Nov 1998 08:35:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C44FA14BE; Thu, 26 Nov 1998 08:15:22 +0100 (CET) Date: Thu, 26 Nov 1998 08:15:22 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? Message-ID: <19981126081522.A13662@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19981125213433.14108@nothing-going-on.org> <19981126001833.A10601@keltia.freenix.fr> <19981125235734.51261@nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <19981125235734.51261@nothing-going-on.org>; from Nik Clayton on Wed, Nov 25, 1998 at 11:57:34PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nik Clayton: > That's part of it. But I don't know if that's all that's required. Here is a patch for the two fr.* keymaps for syscons. Index: fr.iso.acc.kbd =================================================================== RCS file: /spare/FreeBSD-current/src/share/syscons/keymaps/fr.iso.acc.kbd,v retrieving revision 1.1 diff -u -2 -r1.1 fr.iso.acc.kbd --- fr.iso.acc.kbd 1998/01/27 13:36:51 1.1 +++ fr.iso.acc.kbd 1998/11/26 07:13:54 @@ -21,5 +21,5 @@ 016 'a' 'A' soh soh 226 228 dc1 dc1 C 017 'z' 'Z' sub sub 'z' 'Z' etb etb C - 018 'e' 'E' enq enq 'e' 'E' enq enq C + 018 'e' 'E' enq enq 164 'E' enq enq C 019 'r' 'R' dc2 dc2 'r' 'R' dc2 dc2 C 020 't' 'T' dc4 dc4 't' 'T' dc4 dc4 C Index: fr.iso.kbd =================================================================== RCS file: /spare/FreeBSD-current/src/share/syscons/keymaps/fr.iso.kbd,v retrieving revision 1.10 diff -u -2 -r1.10 fr.iso.kbd --- fr.iso.kbd 1998/01/27 13:36:52 1.10 +++ fr.iso.kbd 1998/11/26 07:13:39 @@ -21,5 +21,5 @@ 016 'a' 'A' soh soh 226 228 dc1 dc1 C 017 'z' 'Z' sub sub 'z' 'Z' etb etb C - 018 'e' 'E' enq enq 'e' 'E' enq enq C + 018 'e' 'E' enq enq 164 'E' enq enq C 019 'r' 'R' dc2 dc2 'r' 'R' dc2 dc2 C 020 't' 'T' dc4 dc4 't' 'T' dc4 dc4 C -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 01:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13861 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 01:48:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from imo18.mx.aol.com (imo18.mx.aol.com [198.81.17.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13855 for ; Thu, 26 Nov 1998 01:48:12 -0800 (PST) (envelope-from Ymrojost@aol.com) From: Ymrojost@aol.com Received: from Ymrojost@aol.com by imo18.mx.aol.com (IMOv16.10) id HAAa026097 for ; Thu, 26 Nov 1998 04:47:38 -0500 (EST) Message-ID: Date: Thu, 26 Nov 1998 04:47:38 EST To: hackers@FreeBSD.ORG Mime-Version: 1.0 Subject: timer on demo Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: AOL 3.0 for Mac sub 84 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am interested in software to disable the timer on demo versions of software. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 02:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15942 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 02:23:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15933 for ; Thu, 26 Nov 1998 02:23:28 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id KAA96730; Thu, 26 Nov 1998 10:23:16 GMT Message-ID: <365D2C12.C14B7CC8@tdx.co.uk> Date: Thu, 26 Nov 1998 10:23:14 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Ymrojost@aol.com CC: hackers@FreeBSD.ORG Subject: Re: timer on demo References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ymrojost@aol.com wrote: > I am interested in software to disable the timer on demo versions of > software. I think you've mis-understood the list name - maybe your looking for 'crackers' somewhere else? not 'hackers'? - either way disabling timers on demo software isn't something your going to find details of here... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 04:12:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24016 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 04:12:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24001 for ; Thu, 26 Nov 1998 04:11:58 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA18300; Thu, 26 Nov 1998 13:11:47 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA03347; Thu, 26 Nov 1998 13:11:46 +0100 (MET) Message-ID: <19981126131146.Q17813@follo.net> Date: Thu, 26 Nov 1998 13:11:46 +0100 From: Eivind Eklund To: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: Kernel threads References: <98Nov26.072820est.40325@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Nov26.072820est.40325@border.alcanet.com.au>; from Peter Jeremy on Thu, Nov 26, 1998 at 07:28:49AM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 26, 1998 at 07:28:49AM +1100, Peter Jeremy wrote: > On Tue, 24 Nov 1998 00:52:18 -0800 (PST), Matthew Dillon wrote: > [Redesign the entire KVM subsystem] > > I just don't know how feasible it all is... it would mean a huge amount of > > rewriting. > And I don't suppose you currently have the time to examine it in detail :-). > > > The disadvantage of this > > scheme is that it limits main memory to around 2GB on a 32 bit machine. > > Whilst I don't believe this is a serious problem at present, I can see > that it might be in a couple of years. Presently, the code is almost ready to handle Intels memory extension stuff - modifications should be needed in pmap.c only, if I understood John correctly (private conversation as a result of wanting to run with more than 4GB of memory...) I think giving up this could really limit us for heavy duty server use. With the RAM prices at the level they are today (and dropping), wanting to run more than 2GB is not that exotic. > > The benefits cascade very quickly.... if one is willing to give up > 2GB > > memory configurations on 32 bit cpus. > In which case it would seem worthwhile doing some more detailed > examination. In particular, how much effort would be involved and > whether the 2GB boundary can be avoided. > > Now 3.0 is nearly stable, we need a new bleeding edge for -current. This > sounds like a good start for FreeBSD 4.x :-). I don't think 4.0 should be the next branch. It is easy to bounce it to 4.0 if we want to, but not easy to decrease from 4.0 to 3.1, so let us start at 3.1 :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 06:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01858 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 06:07:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01853 for ; Thu, 26 Nov 1998 06:07:29 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id PAA16223; Thu, 26 Nov 1998 15:03:55 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811261403.PAA16223@ocean.campus.luth.se> Subject: Re: FreeBSD and the Euro? In-Reply-To: <19981126081522.A13662@keltia.freenix.fr> from Ollivier Robert at "Nov 26, 98 08:15:22 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Thu, 26 Nov 1998 15:03:54 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ollivier Robert: > According to Nik Clayton: > > That's part of it. But I don't know if that's all that's required. > > Here is a patch for the two fr.* keymaps for syscons. Similar patches should probably go into all (or at least most) european keyboard mappings. All that doesn't have a special meaning bound to AltGr-e already, if any map has that. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 09:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14989 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 09:07:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14984 for ; Thu, 26 Nov 1998 09:07:24 -0800 (PST) (envelope-from lyndon@execmail.com) Received: from execmail.com (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.0.4/SMS 2.0.4) with ESMTP id KAA11041; Thu, 26 Nov 1998 10:07:14 -0700 Message-Id: <199811261707.KAA11041@rembrandt.esys.ca> Date: Thu, 26 Nov 1998 10:07:10 -0700 From: Lyndon Nerenberg Subject: Re: FreeBSD and the Euro? To: nik@nothing-going-on.demon.co.uk cc: hackers@FreeBSD.ORG In-Reply-To: <19981125235734.51261@nothing-going-on.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Anyway, we already have a ISO-8859-15 (aka Latin9) font for syscons in the >> tree. > > That's part of it. But I don't know if that's all that's required. Groff will need an update. -- Finger lyndon@execmail.com for PGP key. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 10:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19131 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 10:01:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19121 for ; Thu, 26 Nov 1998 10:01:52 -0800 (PST) (envelope-from lyndon@execmail.com) Received: from execmail.com (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.0.4/SMS 2.0.4) with ESMTP id LAA13399 for ; Thu, 26 Nov 1998 11:01:44 -0700 Message-Id: <199811261801.LAA13399@rembrandt.esys.ca> Date: Thu, 26 Nov 1998 11:01:41 -0700 From: Lyndon Nerenberg Subject: anoncvs.freebsd.org pserver access method 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 Is it possible to access anonCVS via the :pserver: authentication scheme? There looks to be a server on port 2401, but I can't find mention of a password anywhere on the web site or mailing list archives. Is pserver supported? If not, could it be? Rsh doesn't work through firewalls ... -- Finger lyndon@execmail.com for PGP key. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 12:24:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01908 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 12:24:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01899 for ; Thu, 26 Nov 1998 12:24:14 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40338>; Fri, 27 Nov 1998 07:23:21 +1100 Date: Fri, 27 Nov 1998 07:23:59 +1100 From: Peter Jeremy Subject: Re: FreeBSD on i386 memory model To: hackers@FreeBSD.ORG Message-Id: <98Nov27.072321est.40338@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998 15:01:13 -0500 (EST), Alfred Perlstein wrote: >Another idea is 2 lib directories, one optimized for <= 486 and the other >optimized for > 486, then you double the amount of space you need for >shared libs... Another option (which I have promoted previously for other reasons) would be to split libc.so into two parts - a machine-independent part and a smaller (optional) machine-dependent part. This is the approach used by Solaris - during the dynamic loading of libc.so, it looks for a file `/usr/platform/{systemtype}/lib/libc_psr.so.1' (where {systemtype} reflects the hardware and kernel architecture). If this library is found, entry points within it are used in preference to those in libc.so. On Solaris, this is all transparent to the user and application developer. >Not worth the cycles unless you were doing long term modeling, Actually, it probably wouldn't be worth it in this case either. The only win would be when the process was generating massive numbers of system calls. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 13:07:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05558 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 13:07:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cnc-mail.crednet.com ([209.51.73.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05553 for ; Thu, 26 Nov 1998 13:07:26 -0800 (PST) (envelope-from theron@crednet.com) Received: from cnc (pdx2-94.transport.com [209.51.88.221]) by cnc-mail.crednet.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id XVZJYW2L; Thu, 26 Nov 1998 13:11:20 -0800 Message-ID: <001b01be1981$998a3600$dd5833d1@cnc> Reply-To: "Theron" From: "Theron" To: Date: Thu, 26 Nov 1998 13:13:19 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01BE193E.8967CAA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0018_01BE193E.8967CAA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable auth 1656e4d6 unsubscribe freebsd-hackers ------=_NextPart_000_0018_01BE193E.8967CAA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
auth 1656e4d6 unsubscribe freebsd-hackers
------=_NextPart_000_0018_01BE193E.8967CAA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 14:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09386 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 14:05:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09361 for ; Thu, 26 Nov 1998 14:05:28 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA18538; Thu, 26 Nov 1998 23:05:09 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id XAA01059; Thu, 26 Nov 1998 23:31:49 GMT Message-ID: <19981126233149.59686@breizh.prism.uvsq.fr> Date: Thu, 26 Nov 1998 23:31:49 +0000 From: Nicolas Souchu To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: LPIP losing clock interrupts - need new spl...() call References: <98Nov24.084033est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <98Nov24.084033est.40335@border.alcanet.com.au>; from Peter Jeremy on Tue, Nov 24, 1998 at 08:40:58AM +1100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the PRs references. On Tue, Nov 24, 1998 at 08:40:58AM +1100, Peter Jeremy wrote: >I haven't done any further work. I have done a bit of thinking about >how to go about handling contention, but didn't come to any firm >conclusions. I only have one ECP machine, so I can't use an ECP >protocol in any case. My only comment is that it would be useful if >the protocol could also be used on a normal bi-directional parallel >port. Yes, but certainly slow. Nicolas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Nov 26 14:15:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10117 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 14:15:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10112 for ; Thu, 26 Nov 1998 14:15:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id XAA09201 for ; Thu, 26 Nov 1998 23:15:35 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA07368 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Thu, 26 Nov 1998 23:00:28 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA00732 for FreeBSD-hackers@freebsd.org; Thu, 26 Nov 1998 23:02:42 +0100 (CET) From: Wilko Bulte Message-Id: <199811262202.XAA00732@yedi.iaf.nl> Subject: building -current for Alpha To: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Date: Thu, 26 Nov 1998 23:02:42 +0100 (CET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anything special I need to do to build -current for Alpha? I have a -current tree on my Intel box that is exported via NFS to the Alpha box (NoName 200Mc, so it takes a while ;-) The NoName currently runs FreeBSD 3.0-CURRENT #1: Thu Oct 22 03:37:32 PDT 1998 taken as a binary from freefall. A make -j 2 buildworld failed in the parse.c module of 'make'. Leaving out -j2 seems to work better. If I remember correctly 'making' current for Intel worked with -j 2 Please bear with me, playing with -current is pretty new to me, esp. on ALpha. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 14:23:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10873 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 14:23:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10868 for ; Thu, 26 Nov 1998 14:23:05 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id JAA16342; Fri, 27 Nov 1998 09:28:55 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811262228.JAA16342@cimlogic.com.au> Subject: Re: building -current for Alpha In-Reply-To: <199811262202.XAA00732@yedi.iaf.nl> from Wilko Bulte at "Nov 26, 98 11:02:42 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Fri, 27 Nov 1998 09:28:55 +1100 (EST) Cc: FreeBSD-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Please use freebsd-alpha@freebsd.org for this sort of thing] Wilko Bulte wrote: > Is there anything special I need to do to build -current for Alpha? > > I have a -current tree on my Intel box that is exported via NFS to the > Alpha box (NoName 200Mc, so it takes a while ;-) The NoName currently runs > FreeBSD 3.0-CURRENT #1: Thu Oct 22 03:37:32 PDT 1998 taken as a binary > from freefall. > > A make -j 2 buildworld failed in the parse.c module of 'make'. Leaving > out -j2 seems to work better. If I remember correctly 'making' current for > Intel worked with -j 2 > > Please bear with me, playing with -current is pretty new to me, esp. on > ALpha. I built -current a few days ago on noname, but without the -j option. I encountered a problem with lib/libdisk which still references installed boot objects. After building and installing sys/boot (IIRC), a `make world' worked fine. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 14:54:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13109 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 14:54:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA13070 for ; Thu, 26 Nov 1998 14:54:19 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 18185 invoked by alias); 26 Nov 1998 22:54:11 -0000 Delivered-To: fixup-freebsd-hackers@FreeBSD.ORG@fixme Received: (qmail 18172 invoked by uid 0); 26 Nov 1998 22:54:10 -0000 Received: from dialupb172.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.96.172) by omahpop1.omah.uswest.net with SMTP; 26 Nov 1998 22:54:10 -0000 Date: Thu, 26 Nov 1998 16:54:10 -0600 (CST) From: "Open Systems Inc." To: Lyndon Nerenberg cc: freebsd-hackers@FreeBSD.ORG Subject: Re: anoncvs.freebsd.org pserver access method In-Reply-To: <199811261801.LAA13399@rembrandt.esys.ca> 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 There is a section in the handbook i believe on keeping current with FreeBSD that details how to do anoncvs. I really wish i could tell you I just dont remember. And im *WAY* to stuffed on prime rib and turkey to even blink let alone look :-) I HOPE this helps you :-) Chris "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 14:59:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13427 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 14:59:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13422 for ; Thu, 26 Nov 1998 14:59:16 -0800 (PST) (envelope-from lyndon@execmail.com) Received: from execmail.com (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.0.4/SMS 2.0.4) with ESMTP id PAA26723; Thu, 26 Nov 1998 15:59:02 -0700 Message-Id: <199811262259.PAA26723@rembrandt.esys.ca> Date: Thu, 26 Nov 1998 15:58:59 -0700 From: Lyndon Nerenberg Subject: Re: anoncvs.freebsd.org pserver access method To: opsys@open-systems.net 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 On 26 Nov, Open Systems Inc. wrote: > > There is a section in the handbook i believe on keeping current with > FreeBSD that details how to do anoncvs. It describes the rsh access method, which does not work through most firewalls. :pserver: does work through firewalls. -- Finger lyndon@execmail.com for PGP key. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 15:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13709 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 15:01:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13704 for ; Thu, 26 Nov 1998 15:01:06 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id RAA24354 for ; Thu, 26 Nov 1998 17:00:19 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id QAA26857 for ; Thu, 26 Nov 1998 16:59:58 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Thu, 26 Nov 1998 16:59:58 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: FreeBSD Hackers Subject: Where is microtime()? 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 was trying to find the answer to two questions: 1. What exactly does microtime() do ? 2. I found it's declaration in time.h. Where is it defined? (the code?) Can someone help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 15:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16435 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 15:33:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hal-pc.org (hal-pc.org [204.52.135.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16425 for ; Thu, 26 Nov 1998 15:33:28 -0800 (PST) (envelope-from chasm@hal-pc.org) Received: from darcy-s-machine (206.180.128.167.dial-ip.hal-pc.org [206.180.128.167]) by hal-pc.org (8.9.1/8.9.0) with SMTP id RAA17132 for ; Thu, 26 Nov 1998 17:33:21 -0600 (CST) From: "Chas Mulhall" To: Subject: Please assist introducing PowerQuest to FreeBSD. Date: Thu, 26 Nov 1998 17:33:01 -0600 Message-ID: <000001be1995$1b6555c0$a780b4ce@darcy-s-machine> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On numerous occasions I have requested Powerquest to take a serious look at supporting FreeBSD, but they don't seem to understand that FreeBSD is at least as powerful and free as Linux which they now support. In particular, I have requested that their product PartitionMagic support FreeBSD, PartitionMagix is an excellent product. I feel that a little letter from you might help them see that support of FreeBSD would be in their best interests also. Please introduce yourself to Powerquest and request that they support FreeBSD. TOP O'THE DAY TO YA! Chas Mulhall 7445 Haywood Dr. Houston, Texas 77061-1505 ph: (713)644-7988 email: chasm@hal-pc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 17:37:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28280 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 17:37:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from portal.net.au (galley.portal.net.au [202.12.71.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28275; Thu, 26 Nov 1998 17:37:32 -0800 (PST) (envelope-from matt@portal.net.au) Received: (from matt@localhost) by portal.net.au (8.8.8/8.8.8) id MAA02318; Fri, 27 Nov 1998 12:07:23 +1030 (CST) From: Matt Baker Message-Id: <199811270137.MAA02318@portal.net.au> Subject: sendmail stats? To: freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Fri, 27 Nov 1998 12:07:23 +1030 (CST) X-Mailer: ELM [version 2.4 PL25] 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 I'm looking around for a some good stats summary scripts for a large mail site using sendmail 8.9.1 So far either I can find scripts to produce either not enough or too much. ie, either they only tell me a total number of bytes transfered, or they try to tell me who got what. I'm more after bytes in out broken down into hours per day, or top ten users or something. Something similar to the stats produced by a web server stats package would be great. Does anyone know if something like this exists? thanks, Matthew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 26 23:45:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21659 for freebsd-hackers-outgoing; Thu, 26 Nov 1998 23:45:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21652 for ; Thu, 26 Nov 1998 23:45:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id IAA06803; Fri, 27 Nov 1998 08:45:41 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA01616 (5.67b/IDA-1.5); Fri, 27 Nov 1998 08:37:03 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id IAA05092; Fri, 27 Nov 1998 08:38:26 +0100 (CET) From: Wilko Bulte Message-Id: <199811270738.IAA05092@yedi.iaf.nl> Subject: Re: building -current for Alpha In-Reply-To: <199811262228.JAA16342@cimlogic.com.au> from John Birrell at "Nov 27, 98 09:28:55 am" To: jb@cimlogic.com.au (John Birrell) Date: Fri, 27 Nov 1998 08:38:26 +0100 (CET) Cc: FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As John Birrell wrote... > [ Please use freebsd-alpha@freebsd.org for this sort of thing] > > Wilko Bulte wrote: > > Is there anything special I need to do to build -current for Alpha? > > > > I have a -current tree on my Intel box that is exported via NFS to the > > Alpha box (NoName 200Mc, so it takes a while ;-) The NoName currently runs > > FreeBSD 3.0-CURRENT #1: Thu Oct 22 03:37:32 PDT 1998 taken as a binary > > from freefall. > > > > A make -j 2 buildworld failed in the parse.c module of 'make'. Leaving > > out -j2 seems to work better. If I remember correctly 'making' current for > > Intel worked with -j 2 > > > > Please bear with me, playing with -current is pretty new to me, esp. on > > ALpha. > > I built -current a few days ago on noname, but without the -j option. > I encountered a problem with lib/libdisk which still references installed > boot objects. After building and installing sys/boot (IIRC), a `make world' > worked fine. It now ran much longer than with -j 2 but falls over in/with: ===> libgroff c++ -I/usr/obj/elf/usr/src/tmp/usr/include/g++ -O -pipe -fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/assert.cc -o assert.o In file included from /usr/obj/elf/usr/src/tmp/usr/include/stdio.h:44, from /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/assert.cc:20: /usr/obj/elf/usr/src/tmp/usr/include/machine/ansi.h:57: Internal compiler error. /usr/obj/elf/usr/src/tmp/usr/include/machine/ansi.h:57: Please submit a full bug report to `bug-g++@prep.ai.mit.edu'. *** Error code 1 Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 00:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25088 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 00:28:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25080; Fri, 27 Nov 1998 00:28:33 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA13976; Fri, 27 Nov 1998 09:28:32 +0100 (MET) Date: Fri, 27 Nov 1998 09:28:18 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: freebsd-current@FreeBSD.ORG cc: FreeBSD hackers mailing list Subject: USB support 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 USB support has been committed to FreeBSD Current. Feel free to switch it on (by uncommenting the last block in GENERIC) and report success or failure. Supported are mice, keyboards, generic devices (have not seen any company selling those, but we support them already!). Mice actually do something, keyboards and generic devices only give you silly output. BEWARE: This is preliminary. Do _not_ leave a USB device attached while running anything operational leaving the USB stack compiled in is already dangerous, although I have not seen big problems on my laptop yet. With Easter coming up, I've left a number of bugs in there. So let me know if you find one! The debugging output is bad, and we are going to solve that, to make it more selective, but for now, 'a lot' is the only setting for it. Keep me informed: n_hibma@www.etla.net Cheers, Nick P.S.: Mouse support, the road to success: (make kernel with ums in there and reboot) (start the usbd daemon, reprobing the bus once in while) usbd (or cd /usr/src/usr.sbin/usbd; make; ./usbd) (plug in mouse) mknod /dev/ums0 c 138 0 moused -p /dev/ums0 The major number might change in the future. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 01:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29126 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 01:09:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA29121 for ; Fri, 27 Nov 1998 01:09:28 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KHVBBAXJ; Fri, 27 Nov 98 09:09:22 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981127100909.009499b0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 27 Nov 1998 10:09:09 +0100 To: "Chas Mulhall" , From: Marius Bendiksen Subject: Re: Please assist introducing PowerQuest to FreeBSD. In-Reply-To: <000001be1995$1b6555c0$a780b4ce@darcy-s-machine> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How about a mail adress? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 02:55:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07968 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 02:55:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07963 for ; Fri, 27 Nov 1998 02:55:31 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip24.nwnexus.net [204.57.235.24]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id CAA23925; Fri, 27 Nov 1998 02:54:41 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id CAA02161; Fri, 27 Nov 1998 02:51:21 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981127025121.A2117@halcyon.com> Date: Fri, 27 Nov 1998 02:51:21 -0800 From: "William R. Somsky" To: Leigh Hart , Alfred Perlstein Cc: Nik Clayton , hackers@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? References: <199811172307.JAA18179@at.dotat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811172307.JAA18179@at.dotat.com>; from Leigh Hart on Wed, Nov 18, 1998 at 09:37:40AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 18, 1998 at 09:37:40AM +1030, Leigh Hart wrote: > > And far more dangerous on a production system - and Nik - can > I suggest you also implement the scripts as start|restart|stop > rather than just start|stop as far as arguments go! Here, I think that start|stop should be considered a required minimum for any of these scripts, but that any additional arguments would be allowed as appropriate. (Eg, I've written rc.d scripts w/ "restart", "install", "gentlerestart", etc...) Are you suggesting that "restart" should be a required argument? ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 03:09:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08552 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 03:09:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA08545 for ; Fri, 27 Nov 1998 03:09:16 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA11281; Fri, 27 Nov 1998 10:14:18 +0100 From: Luigi Rizzo Message-Id: <199811270914.KAA11281@labinfo.iet.unipi.it> Subject: 64 char limit for #!/ command interpreters ? To: hackers@FreeBSD.ORG Date: Fri, 27 Nov 1998 10:14:17 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I use to put in my MagicPoint presentations a first line of the form #!/usr/local/bin/mgp ...bla bla bla... so that the interpreter is invoked automatically on the presentation file. Not without surprise, i just noticed that the process fails if the first line is longer than 64 characters (this is on 2.2.6). The limit is apparently in /sys/kern/imgact_shell.c: #define MAXSHELLCMDLEN 64 Now, any idea why the limit is so small, and is there any danger to raise it to a much larger value such as 256 or so ? The reason i am asking is because this mechanism becomes more useful as the number of parameters increases... (and i happen to have hit the limit!) I think i know why the limit is there -- to avoid that some arbitrary binary file can be mistaken for a shell script with an interpreter name if an newline is not found "soon". Still, as we can have a pathname up to 1KB (PATH_MAX in syslimits.h) the 64byte constraint seems a bit inconsistent... luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 03:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11618 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 03:50:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA11613 for ; Fri, 27 Nov 1998 03:50:28 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KHWOKYUJ; Fri, 27 Nov 98 11:50:21 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981127125003.0090ca60@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 27 Nov 1998 12:50:03 +0100 To: Luigi Rizzo , hackers@FreeBSD.ORG From: Marius Bendiksen Subject: Re: 64 char limit for #!/ command interpreters ? In-Reply-To: <199811270914.KAA11281@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >pathname up to 1KB (PATH_MAX in syslimits.h) the 64byte constraint >seems a bit inconsistent... Indeed. Unless there's any good reason why this shouldn't be changed, I suggest we raise the default to 256, at the very least. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 05:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20680 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 05:33:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20671 for ; Fri, 27 Nov 1998 05:33:22 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id NAA06270; Fri, 27 Nov 1998 13:32:58 GMT (envelope-from didier@omnix.net) Date: Fri, 27 Nov 1998 14:32:58 +0100 (CET) From: Didier Derny To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD and the Euro? In-Reply-To: <19981126001833.A10601@keltia.freenix.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 On Thu, 26 Nov 1998, Ollivier Robert wrote: > > I plan to upgrade the fr.iso syscons keyboard map to put the Euro code on > AltGr-E (unless there is any objection ?). > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 > I think it's the way it's implemented in Solaris 5.7 -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 06:14:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23371 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 06:14:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from at.dotat.com (zed.dotat.com [203.38.154.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23365; Fri, 27 Nov 1998 06:14:51 -0800 (PST) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.8/8.8.8) with ESMTP id AAA19958; Sat, 28 Nov 1998 00:50:43 +1030 (CST) Message-Id: <199811271420.AAA19958@at.dotat.com> To: Matt Baker cc: freebsd-isp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: sendmail stats? In-reply-to: Your message of "Fri, 27 Nov 1998 12:07:23 +1030." <199811270137.MAA02318@portal.net.au> Reply-To: freebsd-isp@FreeBSD.ORG Date: Sat, 28 Nov 1998 00:50:43 +1030 From: Leigh Hart Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Matt, Followups to freebsd-isp, this isn't really -hackers material. Matt Baker wrote: > > I'm looking around for a some good stats summary scripts > for a large mail site using sendmail 8.9.1 Aren't we all :) > So far either I can find scripts to produce either not enough > or too much. ie, either they only tell me a total number of > bytes transfered, or they try to tell me who got what. > > I'm more after bytes in out broken down into hours per day, > or top ten users or something. Something similar to the > stats produced by a web server stats package would be great. > > Does anyone know if something like this exists? http://www.sendmail.org/faq/section4.html#4.7 has a few links: ] Subject: Q4.7 -- How can I summarize the statistics generated ] by sendmail in the syslog? ] ] Date: April 9, 1997 ] ] This question is addressed on pages 445-449 of _sendmail, ] 2nd Ed_ (see page 319 of first edition) by Bryan Costales ] (see entry sendmail-faq//book/ISBN/1-56592-222-0 in Q6.1). ] ] An updated version of this syslog-stat.pl script (so that ] it understands the log format used in version 8 sendmail) ] is at ftp://ftp.his.com/pub/brad/sendmail/syslog_stats. ] ] The updated version of ssl has been uploaded to the SMTP ] Resources Directory (in ftp://ftp.is.co.za/networking/mail/tools/), ] as well as ftp://ftp.his.com/pub/brad/sendmail/ssl. There is ] also another program (written by Bryan Beecher) at ] ftp://ftp.his.com/pub/brad/sendmail/smtpstats. ] ] If you're interested in summarizing POP statistics, there is ] ftp://ftp.his.com/pub/brad/sendmail/popstats, also written by ] Bryan Beecher. ] ] To see what else is available today, check the Comprehensive ] Perl Archive Network ftp://ftp.funet.fi/pub/languages/perl/CPAN/CPAN ] or ftp://ftp.cis.ufl.edu/pub/perl/CPAN/CPAN for the site nearest ] you. For the scripts themselves, look under CPAN/scripts/mailstuff/ ] at any CPAN site. For more information, see the comp.lang.perl.* ] FAQs at ftp://ftp.cis.ufl.edu:/pub/perl/faq/FAQ or ] ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/lang/perl/. ] ] There is also the "Sendmail Statistics Project" which has a web ] page at http://www.josnet.se/projects/ssp/. Although they have ] examples online of what the output might look like, it now appears ] that this project is either dead or at least indefinitely on hold. ] Still, you may be able to talk to the authors in order to get what ] code from them you can. ] ] If you're interested in using these kinds of tools to help you ] do some near real-time monitoring of your system, you might be ] interested in MEWS (Mail Early Warning System). From the README: ] ] If you've ever written a perl script to parse sendmail ] log files looking for errors, MEWS might be of interest to ] you. If you've ever thought about writing a perl script to ] munge sendmail log files, cringed a little and hurriedly ] came up with an excuse not to do it, read on. ] ] If you don't have a Solaris 2.5 machine, you can probably ] stop reading here. ] ] The Mail Early Warning System (MEWS) gives postmasters ] immediate notification of trouble spots on your mail ] backbone. It only works with sendmail. ] ] To explain it in a nutshell, whenever sendmail returns a ] 4xx or 5xx SMTP code, with the MEWS modifications, it also ] sends the code over UDP to a daemon which then replays the ] error message to interested parties. The man pages go into ] a little bit more detail. ] ] If this sounds like something you might be interested in getting ] more details about, you can find the MEWS archive at ] ] ftp://ftp.qualcomm.com/pub/people/eamonn/mews.tar.Z. Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 09:13:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08562 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 09:13:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from irc.pcnet.ro (irc.pcnet.ro [193.230.186.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08535 for ; Fri, 27 Nov 1998 09:12:10 -0800 (PST) (envelope-from fnicoles@pcnet.pcnet.ro) Received: from uucp1.pcnet.ro (uucp1.pcnet.ro [193.230.188.6]) by irc.pcnet.ro (8.9.1/8.8.5) with ESMTP id RAA19930 for ; Fri, 27 Nov 1998 17:21:07 +0200 Received: (from uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id QAA00024 for freebsd-hackers@FreeBSD.ORG; Fri, 27 Nov 1998 16:02:39 +0200 Received: (from nick@localhost) by nick.ro (8.8.8/8.8.8) id PAA00317 for freebsd-hackers@FreeBSD.ORG; Fri, 27 Nov 1998 15:51:59 +0200 (EET) (envelope-from nick) From: Florin Nicolescu Message-Id: <199811271351.PAA00317@nick.ro> Subject: multiple keyboard support To: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Date: Fri, 27 Nov 1998 15:51:59 +0200 (EET) X-OS: FreeBSD-2.2.7-RELEASE X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: application/pgp; format=text; x-action=sign Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hello, I need to make FreeBSD support more than one keyboard (actually 10 or 11). I don't need multiple console suport, just to have multiple keyboards - these are in fact handheld barcode scanners with keyboard connector. Usually, I can conect one, together with the keyboard, and it just sends keystrokes to the system. How is it possible to connect more than one keyboard? Does anywere exist some serial devices that can act as a hub for one/many keyboard/ps2 devices? Thanks, Florin - -- - ------------------------------------------------------------------ | Florin-Nicolae Nicolescu | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | - ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | - ------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNl6ufW95n9Jm9dehAQESmgP/cyfVqBvaFMAHO5HCbZu5/toPy2T6SS4P Qf3EVzJrU/na581c3Y6Lc6RwlVnwnz7x/NSnQKRbYVet9no4v7GlBEUD91ukIh8r hMUyQkC4rr4pr3ewwWPC0+tzAPYLUx6NH9N12z/mu9/BDKkb+MJNNaiyGvpKTHen wmawd4Atnis= =oYXW -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 09:40:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10885 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 09:40:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nts006.visionsys.com.br (nts006.visionsys.com.br [200.224.232.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10880 for ; Fri, 27 Nov 1998 09:40:43 -0800 (PST) (envelope-from mjabbur@microtecvision.com.br) Received: from microtecvision.com.br (acme.visionsys.com.br [200.224.232.54]) by nts006.visionsys.com.br with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id XNRNC816; Fri, 27 Nov 1998 16:40:34 -0200 Message-ID: <365EE42C.3CC5F40E@microtecvision.com.br> Date: Fri, 27 Nov 1998 15:41:00 -0200 From: Marlon Jabbur X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-19981117-SNAP i386) MIME-Version: 1.0 To: "hackers@FreeBSD.ORG" Subject: 3c905B - PLEASE HELP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using a 30.19981117-SNAP and i have a 3c905B Nic, when i s3et this nic in promiscuous mode , i lose my net, i can't send and receive anything , any idea ??????? I need desperately to put this working. PLEASE HELP !!!!!!!!! Marlon Jabbur To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 09:43:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11029 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 09:43:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11024 for ; Fri, 27 Nov 1998 09:43:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03231; Fri, 27 Nov 1998 09:39:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811271739.JAA03231@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Florin Nicolescu cc: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Subject: Re: multiple keyboard support In-reply-to: Your message of "Fri, 27 Nov 1998 15:51:59 +0200." <199811271351.PAA00317@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 09:39:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I need to make FreeBSD support more than one keyboard (actually 10 or 11). > I don't need multiple console suport, just to have multiple keyboards - these > are in fact handheld barcode scanners with keyboard connector. Usually, I can > conect one, together with the keyboard, and it just sends keystrokes to the > system. How is it possible to connect more than one keyboard? Does anywere > exist some serial devices that can act as a hub for one/many keyboard/ps2 > devices? These guys normally go in-line between the keyboard and the system, right? If you need that many of them connected to one system, you don't want the keyboard interface version - it will probably cost more to connect 11 keyboard interfaces to your PC than it would to replace all of the scanners with ones that have serial port interfaces. Of course, if you haven't bought them yet, that's even better. The problem is that the keyboard interface isn't really suited to being adapted to a serial port, and short of buying a pile of the 4-display adapter cards (which are expensive, and give you lots of display hardware as well as keyboard interfaces) you'll have to build microprocessor-based adapters for the translation. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 09:59:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12131 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 09:59:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12126 for ; Fri, 27 Nov 1998 09:59:04 -0800 (PST) (envelope-from pechter@shell.monmouth.com) Received: (from pechter@localhost) by shell.monmouth.com (8.9.0/8.9.0) id MAA09191 for hackers@FreeBSD.ORG; Fri, 27 Nov 1998 12:58:25 -0500 (EST) From: Bill/Carolyn Pechter Message-Id: <199811271758.MAA09191@shell.monmouth.com> Subject: Partion Magic support (Powerquest) To: hackers@FreeBSD.ORG Date: Fri, 27 Nov 1998 12:58:25 -0500 (EST) In-Reply-To: <199811271713.JAA08569@hub.freebsd.org> from "freebsd-hackers-digest" at Nov 27, 98 09:13:12 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One month ago I made the same request. One thing, about a month ago when Partition Magic came out I noticed a Linux hacker wrote the filesystem support for ext2fs Partition Magic. Perhaps we need to locate a resource. Bill > Date: Thu, 26 Nov 1998 17:33:01 -0600 > From: "Chas Mulhall" > Subject: Please assist introducing PowerQuest to FreeBSD. > > On numerous occasions I have requested Powerquest to take a serious look at > supporting FreeBSD, but they don't seem to understand that FreeBSD is at > least as powerful and free as Linux which they now support. > In particular, I have requested that their product PartitionMagic support > FreeBSD, PartitionMagix is an excellent product. > I feel that a little letter from you might help them see that support of > FreeBSD would be in their best interests also. > > Please introduce yourself to Powerquest and request that they support > FreeBSD. > > TOP O'THE DAY TO YA! > Chas Mulhall > 7445 Haywood Dr. > Houston, Texas 77061-1505 > ph: (713)644-7988 > email: chasm@hal-pc.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 11:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20889 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 11:57:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20884 for ; Fri, 27 Nov 1998 11:57:30 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id UAA03767 for ; Fri, 27 Nov 1998 20:57:33 +0100 (MET) Date: Fri, 27 Nov 1998 20:57:19 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: USB devices, anyone any spare ones? 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 [begging mode on] At the moment we could do with some new devices to write USB drivers for. We could definitely use one or more of the following devices: hub keyboard (without/with hub) modem speakers cameras trackballs or other pointing devices floppy drives networking devices Printers, monitors and scanners are probably too big to send around, but if someone is willing to lend it to a driver developer, just let me know, and we might be able to come up with some solution. Addresses to send them to are available in Europe and the States (and if someone in Asia is willing to start writing code, there as well). If anyone would be willing to lend the USB device to someone to write the driver for it. That would be very much appreciated. Of course, sample devices from companies in support of our effort would be highly appreciated. [begging more off] Or if you need a skeleton driver and are willing to finish it yourself, let me know. Cheers, Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 12:01:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21517 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 12:01:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21512 for ; Fri, 27 Nov 1998 12:01:56 -0800 (PST) (envelope-from gozer@ludd.luth.se) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id VAA28309 for ; Fri, 27 Nov 1998 21:01:48 +0100 Date: Fri, 27 Nov 1998 21:01:48 +0100 (CET) From: Johan Larsson To: FreeBSD Hackers Subject: Bootmanager -> Bootmanager -> Bootmanager.. :-) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i have a rather peculiar problem. The thing is that the bootmanager on one of our computers loads a bootmanager itself (at least it seems like it). Because first it comes up a choice of: F1 Freebsd Default: F1 and if i press F1 the same screen comes up again but now the default choice if F?. I have reinstalled the computer a few times with different configuration on the partitions but with no luck. I have also reinstalled the bootstrap code (disklabel -B da0 (right?)), both in /stand/sysinstall and manually. I can succesfully boot the computer if i load the kernel from the harddrive booting from a floppy. It worked before then i had NT and FreeBSD installed, and then we removed NT to test Rhapsody, and it was after that i tried to remove Rhapsody with no luck and had to install freebsd that this problem occured. Is this i known problem with an easy solution so please let me know. :-) The computer is an HP Vectra XU 6/200 (PPro200), with an onboard Adaptec aic7880 Ultra SCSI adapter and a QUANTUM VIKING 2.3 NSE 8808 HD. It's running 3.0-RELEASE. Johan -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * Powered by FreeBSD. http://www.se.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 Nov 27 12:58:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24196 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 12:58:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-16-dbn.dial-up.net [196.34.155.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24190 for ; Fri, 27 Nov 1998 12:58:44 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA29837; Fri, 27 Nov 1998 22:57:38 +0200 (SAT) From: Robert Nordier Message-Id: <199811272057.WAA29837@ceia.nordier.com> Subject: Re: Bootmanager -> Bootmanager -> Bootmanager.. :-) In-Reply-To: from Johan Larsson at "Nov 27, 98 09:01:48 pm" To: gozer@ludd.luth.se (Johan Larsson) Date: Fri, 27 Nov 1998 22:57:36 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Larsson wrote: > Hi, i have a rather peculiar problem. The thing is that the bootmanager on > one of our computers loads a bootmanager itself (at least it seems like > it). Because first it comes up a choice of: > > F1 Freebsd > Default: F1 > > and if i press F1 the same screen comes up again but now the default > choice if F?. > > I have reinstalled the computer a few times with different configuration > on the partitions but with no luck. I have also reinstalled the bootstrap > code (disklabel -B da0 (right?)), both in /stand/sysinstall and manually. As you're using slices, the disklabel command needs a slice argument: eg. da0s1 rather than da0. It seems you may have a second copy of the boot manager installed where the boot blocks should be. If the proper disklabel command doesn't fix this, take a look at the fdisk(8) output for the disk and verify that the slice starts in the correct location: typically cyl=0 head=1 sector=1. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 13:12:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24864 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 13:12:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24859 for ; Fri, 27 Nov 1998 13:12:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00446; Fri, 27 Nov 1998 13:10:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811272110.NAA00446@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Johan Larsson cc: FreeBSD Hackers Subject: Re: Bootmanager -> Bootmanager -> Bootmanager.. :-) In-reply-to: Your message of "Fri, 27 Nov 1998 21:01:48 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 13:10:30 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, i have a rather peculiar problem. The thing is that the bootmanager on > one of our computers loads a bootmanager itself (at least it seems like > it). Because first it comes up a choice of: > > F1 Freebsd > Default: F1 > > and if i press F1 the same screen comes up again but now the default > choice if F?. This indicates that the geometry that you've used when partitioning the disk doesn't agree with the geometry that the BIOS thinks you have. Boot the install floppy with '-v' at the boot: prompt. When the initial sysinstall screen comes up, hit Scroll Lock, then use the cursor keys to scroll back. You'll soon come to a listing of BIOS geometries; you need to set the disk geometry to match these when you're slicing the disk up. If you're *really* lucky, you might be able to tweak the BIOS geometry setting to match the one you already used for the disk. Note that if you're using an Adaptec SCSI controller, you should frob the "extended translation for disks > 1GB" option to ON for FreeBSD to be able to install/boot from the disk. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 13:47:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27357 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 13:47:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27352 for ; Fri, 27 Nov 1998 13:47:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA16497; Fri, 27 Nov 1998 13:47:33 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id NAA07730; Fri, 27 Nov 1998 13:47:20 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 27 Nov 1998 13:47:20 -0800 (PST) Message-Id: <199811272147.NAA07730@vashon.polstra.com> To: rnordier@nordier.com Subject: Re: Bootmanager -> Bootmanager -> Bootmanager.. :-) Newsgroups: polstra.freebsd.hackers In-Reply-To: <199811272057.WAA29837@ceia.nordier.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811272057.WAA29837@ceia.nordier.com>, Robert Nordier wrote: > > As you're using slices, the disklabel command needs a slice argument: > eg. da0s1 rather than da0. Maybe so, but you'd sure never know it from the man page. All of the text and all of the examples reference either "sd0" or "/dev/rsd0c". Besides that, it should say "da" now, not "sd". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 13:55:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28115 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 13:55:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28110 for ; Fri, 27 Nov 1998 13:55:08 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA25737 for ; Fri, 27 Nov 1998 13:55:44 -0800 (PST) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id XAA14631 for ; Fri, 27 Nov 1998 23:43:37 +0100 (CET) Message-Id: <199811272243.XAA14631@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@freefall.cdrom.com Subject: Re: USB devices, anyone any spare ones? Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 27 Nov 1998 20:57:19 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 23:43:37 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > >[begging mode on] > >At the moment we could do with some new devices to write USB drivers >for. We could definitely use one or more of the following devices: > > hub > keyboard (without/with hub) > modem > speakers > cameras > trackballs or other pointing devices > floppy drives > networking devices > USB ISDN controller maybe ? I know that AVM has one on the market. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 14:04:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29043 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 14:04:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29035 for ; Fri, 27 Nov 1998 14:04:08 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id RAA04406 for ; Fri, 27 Nov 1998 17:04:07 GMT Message-Id: <199811271704.RAA04406@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 27 Nov 1998 17:01:55 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: vnode_if.c wont compile Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Standard 3.0-RELEASE...get errors with GENERIC and custom kernel....... I remember reading something about this, but cant find it. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 14:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29169 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 14:06:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from furrball.dyn.ml.org ([207.18.137.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29164 for ; Fri, 27 Nov 1998 14:06:41 -0800 (PST) (envelope-from chris@furrball.dyn.ml.org) Received: (from chris@localhost) by furrball.dyn.ml.org (8.9.1a/8.8.8) id QAA01519; Fri, 27 Nov 1998 16:03:27 -0600 (CST) (envelope-from chris) Date: Fri, 27 Nov 1998 16:03:27 -0600 (CST) From: Chris Costello Message-Id: <199811272203.QAA01519@furrball.dyn.ml.org> To: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: vnode_if.c wont compile Reply-To: phoenix@calldei.com In-Reply-To: <199811271704.RAA04406@etinc.com> X-Mailer: mail(1) -- the One True(TM) mail client Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Fri, 27 Nov 1998 17:01:55 -0500 > To: hackers@FreeBSD.ORG > From: Dennis > Subject: vnode_if.c wont compile > > > Standard 3.0-RELEASE...get errors with GENERIC and custom kernel....... > > I remember reading something about this, but cant find it. Perhaps you could provide us with the errors so we can figure out what is wrong. -Chris > > 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 Fri Nov 27 14:42:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01160 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 14:29:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01149 for ; Fri, 27 Nov 1998 14:29:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id OAA27594 for ; Fri, 27 Nov 1998 14:30:14 -0800 (PST) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00848; Fri, 27 Nov 1998 14:26:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811272226.OAA00848@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gary Jennejohn cc: freebsd-hackers@freefall.cdrom.com Subject: Re: USB devices, anyone any spare ones? In-reply-to: Your message of "Fri, 27 Nov 1998 23:43:37 +0100." <199811272243.XAA14631@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 14:26:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG > Nick Hibma writes: > > > >[begging mode on] > > > >At the moment we could do with some new devices to write USB drivers > >for. We could definitely use one or more of the following devices: > > > > hub > > keyboard (without/with hub) > > modem > > speakers > > cameras > > trackballs or other pointing devices > > floppy drives > > networking devices > > > > USB ISDN controller maybe ? I know that AVM has one on the market. We spoke with some people at Comdex about this; I believe they're in the Netherlands. Jordan has their information at the moment; I'll be out of the country for a couple of weeks, so you probably want to take this up with him for now. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:39:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07979 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:39:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07974 for ; Fri, 27 Nov 1998 15:39:12 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA21039; Fri, 27 Nov 1998 16:39:00 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd021003; Fri Nov 27 16:38:55 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA24805; Fri, 27 Nov 1998 16:38:18 -0700 (MST) From: Terry Lambert Message-Id: <199811272338.QAA24805@usr02.primenet.com> Subject: Re: Would this make FreeBSD more secure? To: jdp@polstra.com (John Polstra) Date: Fri, 27 Nov 1998 23:38:18 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: from "John Polstra" at Nov 23, 98 04:25:37 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Also, I think the point of PAM is to let people use modules other > > than the ones that we use... so that argument is rather pointless. > > What argument? I have no intention of taking responsibility for bugs > in modules that other people wrote. If you want to use them, it's up > to you to convince yourself that they're OK. If you provide a PAM framework, expect people to Plug Authentication Modules into it. It's like the ISA bus. If you provide one on your hardware, expect people to plug ISA cards into your hardware. > > Here is a bug that will be common in network applications like ftpd > > linked to use PAM: > > > > http://geek-girl.com/bugtraq/1998_1/0111.html > > This is a bug in the Solaris ftpd, and has nothing to do with PAM. This is a member of a class of bugs which may or may not be present in FreeBSD code, and for which linking against PAM exposes a vulnerability. Yes, this instance of the class is Solaris ftpd specific, but I haven't seen the results of a FreeBSD security audit that say that FreeBSD isn't also getting an exposed vulnerability as a result of the same act that caused Solaris to gain an exposed vulnerability. Security is a chain, not a fence. > > I don't know if you are using the rhost module, but if so, this may > > be relevent: > > I didn't use any of the Linux modules. OK, so you're not vulnerable, but that module is not on a list of known rogues in the FreeBSD implementation to preven its use. > > Also, PAM can become vulnerable based on libc implementation, since > > it is a consumer of libc; here's one example: > > > > http://geek-girl.com/bugtraq/1997_2/0228.html > > This is about a Linux libc bug, combined with a stupid blunder by a > Linux system "administrator". Anyway, everything that is linked with > libc is vulnerable to bugs in it. PAM is not special in that sense. True. But PAM exposes a heck of a lot more code through its interface bottleneck and code modules than was exposed prior to its integration. > > Also, is our qpopper port still vulnerable to: > > > > http://geek-girl.com/bugtraq/1998_2/0657.html > > > > ??? > > I have no idea. What is the relevance to PAM? OK, the point is that there is no such thing as being partially ommitted to security. You are either totally committed, or you might as well be diddling yourself. I think it was a mistake to bring in PAM at this time, without first making sure that the bolts are all tightened. It's like having a boat that you trust on a lake, and then deciding that you can sail to Fiji in the thing without inspecting why, each time you pulled it out of the water, there was a gallon of water in the bilge. Throwing PAM into FreeBSD is like sailing to Fiji in a boat that's not leaky enough that you have to worry about it when you go on a day trip. Or maybe it's more like dynamiting the reef between the boat and the open sea; once it's there, then FreeBSD no longer controls its authentication process through the source code. Don't get me wrong; now is as good a time as any to integrate new features; it's post-release, and that's what the -current source tree is for. But PAM is *such* a mess (compared to some of the stuff Mike Smith discussed on -current that would do what PAM does, but without the architectural risks) that I think its necessary to advice great caution. So that's what I'm doing: "I advise great caution", Terry said. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08350 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:41:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08342 for ; Fri, 27 Nov 1998 15:41:23 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA08064; Fri, 27 Nov 1998 16:41:16 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd008053; Fri Nov 27 16:41:13 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA24991; Fri, 27 Nov 1998 16:41:09 -0700 (MST) From: Terry Lambert Message-Id: <199811272341.QAA24991@usr02.primenet.com> Subject: Re: SYSV Semaphores & mmap problems To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 27 Nov 1998 23:41:09 +0000 (GMT) Cc: tlambert@primenet.com, joelh@gnu.org, DBECK@ludens.elte.hu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811240147.RAA11543@apollo.backplane.com> from "Matthew Dillon" at Nov 23, 98 05:47:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The difference between mmap() and SysV shared memory isn't so bad. The > mmap()'d file will basically get synced every 30 seconds or so by the > syncer daemon. madvise() can be used to pre-fault any pages already in > the cache. > > I think all that is needed is a way to flag a file so the syncer doesn't > touch it under normal circumstances, instead allowing its pages to be > synced by normal paging activity. You can then madvise(... MADV_FREE) > the pages after you are through with the shared memory segment to throw > them away. The question to ask is "Why did Oracle pay John Dyson to make FreeBSD's SYSV SHM faster, and reject mmap(), even though the Oriacle source code supports using mmap()?". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:50:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09039 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:50:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09034 for ; Fri, 27 Nov 1998 15:50:50 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA27465; Fri, 27 Nov 1998 16:50:43 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd027450; Fri Nov 27 16:50:39 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA25484; Fri, 27 Nov 1998 16:50:39 -0700 (MST) From: Terry Lambert Message-Id: <199811272350.QAA25484@usr02.primenet.com> Subject: Re: /etc/rc.d, and changes to /etc/rc? To: spork@super-g.com (spork) Date: Fri, 27 Nov 1998 23:50:39 +0000 (GMT) Cc: nik@nothing-going-on.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: from "spork" at Nov 24, 98 04:06:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Personally (and I'm biased since I just started kicking around my Sparc2), > I think there are some serious gains here for people new to FBSD, and some > major conveniences for wizened users. I would have killed for ./nfsd.sh > top/start this past week. There seem to be more and more people using > databases and some of them (mysql for one) don't like the way they are > currently shutdown. If rather than killing the daemon we could call > 'mysqladmin shutdown', that would be swell. I've got to say that it ruins LDAP's whole day, if the directory has been written, since there are no write-atomicity guarantees beyond the object level in the current LDAP incarnations. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09335 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:55:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09330 for ; Fri, 27 Nov 1998 15:55:16 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id SAA04699; Fri, 27 Nov 1998 18:55:13 GMT Message-Id: <199811271855.SAA04699@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 27 Nov 1998 18:53:00 -0500 To: phoenix@calldei.com, hackers@FreeBSD.ORG From: Dennis Subject: Re: vnode_if.c wont compile In-Reply-To: <199811272203.QAA01519@furrball.dyn.ml.org> References: <199811271704.RAA04406@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:03 PM 11/27/98 -0600, Chris Costello wrote: >> Date: Fri, 27 Nov 1998 17:01:55 -0500 >> To: hackers@FreeBSD.ORG >> From: Dennis >> Subject: vnode_if.c wont compile >> >> >> Standard 3.0-RELEASE...get errors with GENERIC and custom kernel....... >> >> I remember reading something about this, but cant find it. > > Perhaps you could provide us with the errors so we can figure out >what is wrong. > >-Chris In file included from vnode_if.c:9: ../../sys/vnode.h:472: warning: `struct vop_lease_args' declared inside paramete r list ../../sys/vnode.h:472: warning: its scope is only this definition or declaration , ../../sys/vnode.h:472: warning: which is probably not what you want. ../../sys/vnode.h:486: warning: `struct vop_lease_args' declared inside paramete r list ../../sys/vnode.h:517: warning: `struct vop_lookup_args' declared inside paramet er list ../../sys/vnode.h:522: warning: `struct vop_islocked_args' declared inside param eter list ../../sys/vnode.h:523: warning: `struct vop_lock_args' declared inside parameter list ../../sys/vnode.h:528: warning: `struct vop_unlock_args' declared inside paramet er list ../../sys/vnode.h:529: warning: `struct vop_pathconf_args' declared inside param eter list ../../sys/vnode.h:530: warning: `struct vop_poll_args' declared inside parameter list ../../sys/vnode.h:531: warning: `struct vop_revoke_args' declared inside paramet er list ../../sys/vnode.h:532: warning: `struct vop_lock_args' declared inside parameter list vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant vnode_if.c:47: parse error before `int' *** Error code 1 Just did a 'config GENERIC" and a make. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09569 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:55:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09564 for ; Fri, 27 Nov 1998 15:55:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01337; Fri, 27 Nov 1998 15:53:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811272353.PAA01337@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: jdp@polstra.com (John Polstra), hackers@FreeBSD.ORG Subject: Re: Would this make FreeBSD more secure? In-reply-to: Your message of "Fri, 27 Nov 1998 23:38:18 GMT." <199811272338.QAA24805@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 15:53:18 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think it was a mistake to bring in PAM at this time, without > first making sure that the bolts are all tightened. It's like > having a boat that you trust on a lake, and then deciding that > you can sail to Fiji in the thing without inspecting why, each > time you pulled it out of the water, there was a gallon of > water in the bilge. Actually, the timing and content of the import is close to optimal. Your argument that importing PAM is bad because there are bad PAM modules out there is really kinda stupid; there's bad code everywhere, and a PAM module is no more or less risky than a setuid program. The PAM import contains only components which have been tightened. If you wish to try to sail to Fiji while experimenting with underwater portholes, that's entirely your own failure as a captain. I can't see how a list of "known rogue" modules would help; there's nothing that would let you usefully identify such an animal anyway. > Don't get me wrong; now is as good a time as any to integrate > new features; it's post-release, and that's what the -current > source tree is for. But PAM is *such* a mess (compared to some > of the stuff Mike Smith discussed on -current that would do what > PAM does, but without the architectural risks) that I think its > necessary to advice great caution. PAM is a pragmatic choice. There are a lot of good things you could do to reduce the risk profile, but they represent a great deal of work, and they don't necessarily return in proportion to the effort involved. On the other hand, PAM is an order of magnitude better than the existing authentication code, which is a horrible mess all unto itself. > So that's what I'm doing: "I advise great caution", Terry said. I hardly think that it's necessary to suggest that to John. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 15:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09684 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 15:57:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09679 for ; Fri, 27 Nov 1998 15:57:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01360; Fri, 27 Nov 1998 15:55:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811272355.PAA01360@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis cc: phoenix@calldei.com, hackers@FreeBSD.ORG Subject: Re: vnode_if.c wont compile In-reply-to: Your message of "Fri, 27 Nov 1998 18:53:00 EST." <199811271855.SAA04699@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 15:55:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) > vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant > vnode_if.c:47: parse error before `int' > *** Error code 1 > > Just did a 'config GENERIC" and a make. Did you 'make depend' first? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 16:56:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16524 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 16:56:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from k6n1.znh.org (dialup20.gaffaneys.com [208.155.161.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16518 for ; Fri, 27 Nov 1998 16:55:56 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id AAA10773 for hackers@FreeBSD.ORG; Sat, 28 Nov 1998 00:55:44 GMT (envelope-from zach) Message-ID: <19981127185544.A2982@znh.org> Date: Fri, 27 Nov 1998 18:55:44 -0600 From: Zach Heilig To: hackers@FreeBSD.ORG Subject: Reading values out of/Writing values to a PCI device... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently attempting to write a network device driver for the VIA 86C100A (Rhine?) Fast Ethernet Controller, as this seems to not be currently supported, and does not have an NE2000 compatability mode. (A grep for '1106' and '3043' in /sys/pci shows nothing, except a VIA motherboard chipset). Writing the "probe" was rather easy (it detects just fine) :-). Writing the "attach" function has hit a snag: I have #1 the Linux driver [this is kinda confusing], #2 the 86C100A spec sheets [the linux driver is less relavent now ;-)], and #3 the eeprom info sheets [difficult to make sense of parts of #2 above without it]. This is what the card looks like (to FreeBSD): found-> vendor=0x1106, dev=0x3043, revid=0x06 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 00006100, size 7 map[1]: type 1, range 32, base f1000000, size 7 I'm presuming I want to use the 'type 1' map (memory map rather than port map). I'm also going to guess that I can't just read/write to 'memory address 0xf100 0000', and I somehow need to get that mapped into my driver space. Another guess is the 'range 32' means 32*4 bytes (that's the only interpretation that makes sense given 128 bytes of pci registers). I can't figure out what the 'size 7' means (or even if it is important). It does require a 32-bit aligned data buffer. Do we have the same problem as Linux (they have 14-byte headers, so "need" a data copy to an alignment buffer). This chip can be programmed to put different parts of an ethernet frame into different buffers, so maybe that isn't really a problem... except with that particular driver. Also, I see this '...softc' structure.. Is there any description for it anywhere (other than poking around in the source)? -- Zach Heilig (zach@gaffaneys.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 17:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16822 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 17:00:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16816 for ; Fri, 27 Nov 1998 17:00:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01827; Fri, 27 Nov 1998 16:59:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811280059.QAA01827@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Zach Heilig cc: hackers@FreeBSD.ORG Subject: Re: Reading values out of/Writing values to a PCI device... In-reply-to: Your message of "Fri, 27 Nov 1998 18:55:44 CST." <19981127185544.A2982@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 16:59:00 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Save yourself. http://www.freebsd.org/~wpaul/VIA > I'm currently attempting to write a network device driver for the VIA > 86C100A (Rhine?) Fast Ethernet Controller, as this seems to not be > currently supported, and does not have an NE2000 compatability mode. > (A grep for '1106' and '3043' in /sys/pci shows nothing, except a > VIA motherboard chipset). > > Writing the "probe" was rather easy (it detects just fine) :-). > Writing the "attach" function has hit a snag: > > I have #1 the Linux driver [this is kinda confusing], #2 the 86C100A > spec sheets [the linux driver is less relavent now ;-)], and #3 the > eeprom info sheets [difficult to make sense of parts of #2 above > without it]. > > This is what the card looks like (to FreeBSD): > > found-> vendor=0x1106, dev=0x3043, revid=0x06 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=9 > map[0]: type 4, range 32, base 00006100, size 7 > map[1]: type 1, range 32, base f1000000, size 7 > > I'm presuming I want to use the 'type 1' map (memory map rather than > port map). I'm also going to guess that I can't just read/write to > 'memory address 0xf100 0000', and I somehow need to get that mapped > into my driver space. Another guess is the 'range 32' means 32*4 > bytes (that's the only interpretation that makes sense given 128 bytes > of pci registers). I can't figure out what the 'size 7' means (or > even if it is important). > > It does require a 32-bit aligned data buffer. Do we have the same > problem as Linux (they have 14-byte headers, so "need" a data copy to > an alignment buffer). This chip can be programmed to put different > parts of an ethernet frame into different buffers, so maybe that isn't > really a problem... except with that particular driver. > > Also, I see this '...softc' structure.. Is there any description for > it anywhere (other than poking around in the source)? > > -- > Zach Heilig (zach@gaffaneys.com) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 17:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17410 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 17:09:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from k6n1.znh.org (dialup20.gaffaneys.com [208.155.161.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17399 for ; Fri, 27 Nov 1998 17:09:45 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id BAA37109; Sat, 28 Nov 1998 01:09:23 GMT (envelope-from zach) Message-ID: <19981127190922.B2982@znh.org> Date: Fri, 27 Nov 1998 19:09:22 -0600 From: Zach Heilig To: Mike Smith , Zach Heilig Cc: hackers@FreeBSD.ORG Subject: Re: Reading values out of/Writing values to a PCI device... References: <19981127185544.A2982@znh.org> <199811280059.QAA01827@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811280059.QAA01827@dingo.cdrom.com>; from Mike Smith on Fri, Nov 27, 1998 at 04:59:00PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 27, 1998 at 04:59:00PM -0800, Mike Smith wrote: > Save yourself. http://www.freebsd.org/~wpaul/VIA Ok, thanks! (I'm off to test that now :-) -- Zach Heilig (zach@gaffaneys.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 27 23:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14825 for freebsd-hackers-outgoing; Fri, 27 Nov 1998 23:35:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orbit.flnet.com (orbit.flnet.com [205.240.232.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14820 for ; Fri, 27 Nov 1998 23:35:26 -0800 (PST) (envelope-from henrich@orbit.flnet.com) Received: (from henrich@localhost) by orbit.flnet.com (8.8.5/8.8.4) id CAA15127; Sat, 28 Nov 1998 02:35:12 -0500 (EST) Message-ID: <19981127233512.57497@orbit.flnet.com> Date: Fri, 27 Nov 1998 23:35:12 -0800 From: Charles Henrich To: hasty@rah.star-gate.com, freebsd-hackers@FreeBSD.ORG Subject: Re: SDSL in Silicon Valley Mail-Followup-To: hasty@rah.star-gate.com, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Operating-System: FreeBSD 2.2-BETA_A X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In lists.freebsd.hackers you write: >I upgraded my net connection from 128kb isdn line to 416kb SDSL line provided >by http://www.dspeed.net. Currently, I am paying $170 flat fee and that >includes telco charges and isp charges for my sdsl line or about 50% less >than what I was paying for my 128kb isdn line. >My router is a FlowPoint/2200 SDSL [CM] Router which cost me $490. >The router has four ether ports very nice - it saves me the expense >of having an ether hub. Wow, where did you get it for $490? We just bought a pair for a WAN connection but at $800 a crack. The coolio thing about these little guys is you can stick two of them back to back with upwards of 12,000 feet of copper between them and run at 1.1Mbps. We use em as a WAN for our facility... No expensive repeaters necessary! Plug and play! -Crh Charles Henrich Manex Visual Effects henrich@flnet.com http://orbit.flnet.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 02:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26126 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 02:01:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-47-dbn.dial-up.net [196.34.155.111]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26117 for ; Sat, 28 Nov 1998 02:00:53 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA01702; Sat, 28 Nov 1998 11:59:16 +0200 (SAT) From: Robert Nordier Message-Id: <199811280959.LAA01702@ceia.nordier.com> Subject: Re: Bootmanager -> Bootmanager -> Bootmanager.. :-) In-Reply-To: <199811272147.NAA07730@vashon.polstra.com> from John Polstra at "Nov 27, 98 01:47:20 pm" To: jdp@polstra.com (John Polstra) Date: Sat, 28 Nov 1998 11:59:08 +0200 (SAT) Cc: rnordier@nordier.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <199811272057.WAA29837@ceia.nordier.com>, > Robert Nordier wrote: > > > > As you're using slices, the disklabel command needs a slice argument: > > eg. da0s1 rather than da0. > > Maybe so, but you'd sure never know it from the man page. All of the > text and all of the examples reference either "sd0" or "/dev/rsd0c". My advice was misleading. The compatibility slice is implied, in these context, if the disk is sliced and a slice is not specified. So one should be able to use the same commands on sliced and unsliced disks. I tend to consider multiple FreeBSD slices per disk a bigger win than this kind of compatibility (and the new boot blocks allow booting off any FreeBSD slice) so I just prefer being explicit about the slice. > Besides that, it should say "da" now, not "sd". I've updated the man page. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 05:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12345 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 05:10:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12340 for ; Sat, 28 Nov 1998 05:10:42 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id QAA09579 for ; Sat, 28 Nov 1998 16:10:27 +0300 (MSK) Received: by sunny.aha.ru id QAA05576; (8.8.8/vak/1.9) Sat, 28 Nov 1998 16:10:04 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma005562; Sat Nov 28 16:10:03 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id PAA13941 for ; Sat, 28 Nov 1998 15:59:19 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id QAA06478 for ; Sat, 28 Nov 1998 16:00:34 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sat, 28 Nov 1998 15:59:58 +0300 (MSK) From: oZZ!!! To: hackers@FreeBSD.ORG Subject: SCOs Informix online on FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Does some1 use SCOs Informix online on FreeBSD? I compile kernel with ibcs2, then successfully install it, then successfully install Informix Online, but can't run oninit. oninit: Fatal error in shared memory creation Any idea? Rgdz, osa@etrust.ru FreeBSD - Да пребудет с нами сила! http://www.freebsd.org.ru Ассоциация русскоязычных пользователей FreeBSD P.S. SCOs Oracle successfully run under FreeBSD. Why not Informix ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 07:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18330 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 07:13:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from irc.pcnet.ro (irc.pcnet.ro [193.230.186.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18324 for ; Sat, 28 Nov 1998 07:12:54 -0800 (PST) (envelope-from fnicoles@pcnet.pcnet.ro) Received: from uucp1.pcnet.ro (uucp1.pcnet.ro [193.230.188.6]) by irc.pcnet.ro (8.9.1/8.8.5) with ESMTP id MAA12780 for ; Sat, 28 Nov 1998 12:20:55 +0200 Received: (from uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id LAA10815 for freebsd-hackers@FreeBSD.ORG; Sat, 28 Nov 1998 11:04:47 +0200 Received: (from nick@localhost) by nick.ro (8.8.8/8.8.8) id LAA00378 for freebsd-hackers@FreeBSD.ORG; Sat, 28 Nov 1998 11:01:57 +0200 (EET) (envelope-from nick) From: Florin Nicolescu Message-Id: <199811280901.LAA00378@nick.ro> Subject: multiple keyboard support (fwd) To: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Date: Sat, 28 Nov 1998 11:01:57 +0200 (EET) X-OS: FreeBSD-2.2.7-RELEASE X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to be a Pine error. From what I am keep receiving, I reach to the conclusion that Pine is not able to read a pgp signed mail, and it displays it like a mime attachement. 8-) So I send it again, this time not signed. ----- Begin of forwarded message from Florin Nicolescu ----- Hello, I need to make FreeBSD support more than one keyboard (actually 10 or 11). I don't need multiple console suport, just to have multiple keyboards - these are in fact handheld barcode scanners with keyboard connector. Usually, I can conect one, together with the keyboard, and it just sends keystrokes to the system. How is it possible to connect more than one keyboard? Does anywere exist some serial devices that can act as a hub for one/many keyboard/ps2 devices? Thanks, Florin -- ------------------------------------------------------------------ | Florin-Nicolae Nicolescu | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | ------------------------------------------------------------------ ----- End of forwarded message from Florin Nicolescu ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 07:24:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18983 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 07:24:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18978 for ; Sat, 28 Nov 1998 07:24:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id HAA00587; Sat, 28 Nov 1998 07:23:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811281523.HAA00587@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: oZZ!!! cc: hackers@FreeBSD.ORG Subject: Re: SCOs Informix online on FreeBSD? In-reply-to: Your message of "Sat, 28 Nov 1998 15:59:58 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 28 Nov 1998 07:23:08 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA18979 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > Does some1 use SCOs Informix online on FreeBSD? I understand there are people doing this, yes. You should be asking emulation-related questions on the -emulation list of course. > I compile kernel with ibcs2, then successfully install it, > then successfully install Informix Online, but can't run oninit. > > oninit: Fatal error in shared memory creation > > Any idea? Sounds like you might be missing the SYSV* options in your kernel config: options SYSVSEM options SYSVMSG options SYSVSHM -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 07:55:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21288 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 07:55:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21282 for ; Sat, 28 Nov 1998 07:55:42 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id SAA12781; Sat, 28 Nov 1998 18:55:32 +0300 (MSK) Received: by sunny.aha.ru id SAA25721; (8.8.8/vak/1.9) Sat, 28 Nov 1998 18:55:09 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma025691; Sat Nov 28 18:55:03 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id SAA14147; Sat, 28 Nov 1998 18:48:11 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id SAA00698; Sat, 28 Nov 1998 18:43:37 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sat, 28 Nov 1998 18:43:01 +0300 (MSK) From: oZZ!!! To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: SCOs Informix online on FreeBSD? In-Reply-To: <199811281523.HAA00587@dingo.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 Sat, 28 Nov 1998, Mike Smith wrote: > > Hello! > > Does some1 use SCOs Informix online on FreeBSD? > > I understand there are people doing this, yes. You should be asking > emulation-related questions on the -emulation list of course. > > > I compile kernel with ibcs2, then successfully install it, > > then successfully install Informix Online, but can't run oninit. > > > > oninit: Fatal error in shared memory creation > > > > Any idea? > > Sounds like you might be missing the SYSV* options in your kernel > config: > > options SYSVSEM > options SYSVMSG > options SYSVSHM i have it, but oninit don't work... > another idea? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 08:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21589 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 08:00:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21569 for ; Sat, 28 Nov 1998 08:00:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id HAA00817; Sat, 28 Nov 1998 07:58:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811281558.HAA00817@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: oZZ!!! cc: hackers@FreeBSD.ORG Subject: Re: SCOs Informix online on FreeBSD? In-reply-to: Your message of "Sat, 28 Nov 1998 18:43:01 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 07:58:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Sat, 28 Nov 1998, Mike Smith wrote: > > > > Hello! > > > Does some1 use SCOs Informix online on FreeBSD? > > > > I understand there are people doing this, yes. You should be asking > > emulation-related questions on the -emulation list of course. > > > > > I compile kernel with ibcs2, then successfully install it, > > > then successfully install Informix Online, but can't run oninit. > > > > > > oninit: Fatal error in shared memory creation > > > > > > Any idea? > > > > Sounds like you might be missing the SYSV* options in your kernel > > config: > > > > options SYSVSEM > > options SYSVMSG > > options SYSVSHM > i have it, but oninit don't work... > > > > another idea? ktrace, and the ibcs2 syscall table. Work out what's failing and causing it to print the above message. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 08:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22498 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 08:11:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22493 for ; Sat, 28 Nov 1998 08:11:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00921; Sat, 28 Nov 1998 08:10:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811281610.IAA00921@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Didier Derny cc: hackers@FreeBSD.ORG Subject: Re: help! booting 3.0-RELEASE from ide zip In-reply-to: Your message of "Mon, 23 Nov 1998 11:40:24 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 08:10:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to boot from an ide zip drive. This is a bit difficult. > I generated a boot disk on a scsi zip but I'm unable to boot from the > ide zip drive. > > It refuses to see the zip drive except as a floppy disk. > in that cases it sees the boot block but I'm unable to go further > (it tries to load from fd) That's because the drive is presented by the BIOS as a floppy drive. > I've not succedded in trying to override manually to 0:wd(0,a) That won't help either; it will try to use BIOS unit 0x80, where the IDE zip is 0x0. You may have better luck with the new boot1/boot2 code; I haven't got that far in testing yet. If you're interested in working on this for the new bootstrap code, drop me a line and I can explain the (relatively simple) issues involved and get you going in the right direction. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 08:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22717 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 08:14:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22706 for ; Sat, 28 Nov 1998 08:14:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00945; Sat, 28 Nov 1998 08:13:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811281613.IAA00945@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Vladislav SAFRONOV <0824@08700000.mhs.rosmail.com> cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help! Modifying Linux sources to compile under 2.2.7R. In-reply-to: Your message of "Sun, 22 Nov 1998 23:41:10 +0300." <161BD2D781F0D57E%161BD2D781F0D57E@mhs.mhs.rosmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 08:13:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I want to compile a little c program under Freebsd, but the source > warns: > > "Linux 2.0.33 source, will compile on BSD if you modify the ip > header etc." Sounds like you're trying to compile an exploit or an attack program. Bad, Bad boy. > I thought small tcp/ip applications could be copmiled under any Unix > :(, Linux is not Unix. > Well what should I modify? What's the difference between BSD ip > header and Linux ip header? Look at the structure definitions and work it out yourself; this is part of the learning process. See what gives you errors when you try to compile it; work out what it should do; fix it. > the source: > ... > struct iphdr *iph=(struct iphdr *)buf; > struct udphdr *udp=(struct udphdr *)(buf + 20); > ... > iph->version=4; > iph->ihl=5; > iph->tos=0; > iph->tot_len=htons(sizeof(buf)); > iph->id=htons(1234); > iph->frag_off=0; > iph->ttl=255; > iph->protocol=17; > > iph->saddr=inet_addr(SIP); > iph->daddr=resolve_address(argv[1]); > > Should I modify udp header as well? No, don't do that. If you get it wrong, you'll reverse the charge on all the electrons in the left half of your body. That would be bad. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 08:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25834 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 08:46:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25826 for ; Sat, 28 Nov 1998 08:46:25 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA08665; Sat, 28 Nov 1998 11:45:52 GMT Message-Id: <199811281145.LAA08665@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 28 Nov 1998 11:43:31 -0500 To: Mike Smith From: Dennis Subject: Re: vnode_if.c wont compile Cc: phoenix@calldei.com, hackers@FreeBSD.ORG In-Reply-To: <199811272355.PAA01360@dingo.cdrom.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 At 03:55 PM 11/27/98 -0800, Mike Smith wrote: >> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) >> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant >> vnode_if.c:47: parse error before `int' >> *** Error code 1 >> >> Just did a 'config GENERIC" and a make. > >Did you 'make depend' first? Yes. 'make depend' completes successfully. Dennis > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 08:55:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26606 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 08:55:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26599 for ; Sat, 28 Nov 1998 08:55:40 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id TAA13940; Sat, 28 Nov 1998 19:55:32 +0300 (MSK) Received: by sunny.aha.ru id TAA02785; (8.8.8/vak/1.9) Sat, 28 Nov 1998 19:55:27 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma002720; Sat Nov 28 19:55:03 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id TAA14245; Sat, 28 Nov 1998 19:52:22 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id TAA15380; Sat, 28 Nov 1998 19:47:17 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sat, 28 Nov 1998 19:47:16 +0300 (MSK) From: oZZ!!! To: Mike Smith cc: hackers@FreeBSD.ORG Subject: SCOs Informix Online... part 2 In-Reply-To: <199811280059.QAA01827@dingo.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 Hello! My kernel is: .......... machine "i386" cpu "I586_CPU" ident INFORMIX maxusers 64 ...................... options SYSVSHM options SYSVSEM options SYSVMSG options "IBCS2" options KTRACE #kernel tracing .............. informix@ozz$ ktrace oninit oninit: Fatal error in shared memory informix@ozz$ kdump 15359 ktrace RET ktrace 0 15359 ktrace CALL readlink(0x280bcaf8,0xefbfd710,0x3f) 15359 ktrace NAMI "/etc/malloc.conf" 15359 ktrace RET readlink -1 errno 2 No such file or directory 15359 ktrace CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0) 15359 ktrace RET mmap 671944704/0x280d1000 15359 ktrace CALL break(0x804c000) 15359 ktrace RET break 0 15359 ktrace CALL break(0x804d000) 15359 ktrace RET break 0 15359 ktrace CALL execve(0xefbfd818,0xefbfdcdc,0xefbfdce4) 15359 ktrace NAMI "/usr/informix/bin/oninit" Make some changes in "Shared Memory Parametrs" in $INFORMIX/etc/onconfig.std ??? ............. # Shared Memory Parameters LOCKS 2000 # Maximum number of locks BUFFERS 200 # Maximum number of shared buffers NUMAIOVPS # Number of IO vps PHYSBUFF 32 # Physical log buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes) LOGSMAX 6 # Maximum number of logical log files CLEANERS 1 # Number of buffer cleaner processes SHMBASE 0x82000000L # Shared memory base address SHMVIRTSIZE 8000 # initial virtual shared memory segment size SHMADD 8192 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # Check point interval (in sec) LRUS 8 # Number of LRU queues LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit LTXHWM 50 # Long transaction high water mark percentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 300 # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) ....................... Any idea? Some utilites like dbaccess work, but oninit not. Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 09:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27293 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 09:00:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27288 for ; Sat, 28 Nov 1998 09:00:24 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA44242; Sat, 28 Nov 1998 12:02:44 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 28 Nov 1998 12:02:44 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: oZZ!!! cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: SCOs Informix Online... part 2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Nov 1998, oZZ!!! wrote: > > informix@ozz$ ktrace oninit > oninit: Fatal error in shared memory > informix@ozz$ kdump > 15359 ktrace RET ktrace 0 > 15359 ktrace CALL readlink(0x280bcaf8,0xefbfd710,0x3f) > 15359 ktrace NAMI "/etc/malloc.conf" > 15359 ktrace RET readlink -1 errno 2 No such file or directory > 15359 ktrace CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0) > 15359 ktrace RET mmap 671944704/0x280d1000 > 15359 ktrace CALL break(0x804c000) > 15359 ktrace RET break 0 > 15359 ktrace CALL break(0x804d000) > 15359 ktrace RET break 0 > 15359 ktrace CALL execve(0xefbfd818,0xefbfdcdc,0xefbfdce4) > 15359 ktrace NAMI "/usr/informix/bin/oninit" > > Make some changes in "Shared Memory Parametrs" > in $INFORMIX/etc/onconfig.std ??? No idea about this, but instead of the 'head' of your ktrace, perhaps you want to show us the end of it? Where it actually has a problem? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 09:06:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27838 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 09:06:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27790 for ; Sat, 28 Nov 1998 09:06:00 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id MAA08754; Sat, 28 Nov 1998 12:06:03 GMT Message-Id: <199811281206.MAA08754@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 28 Nov 1998 12:03:42 -0500 To: Mike Smith From: Dennis Subject: Re: vnode_if.c wont compile Cc: 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 At 03:55 PM 11/27/98 -0800, Mike Smith wrote: >> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) >> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant >> vnode_if.c:47: parse error before `int' >> *** Error code 1 >> >> Just did a 'config GENERIC" and a make. > >Did you 'make depend' first? >Yes. 'make depend' completes successfully. one example: struct vop_lease_args I cant find this structure defined anywhere? Its seems that some include file is missing, or in the wrong path...where should these vop_ functions be declared? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 09:21:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28798 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 09:21:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cam.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28784 for ; Sat, 28 Nov 1998 09:21:07 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from gvinpin.grad.kiev.ua (root@gvinpin [10.0.0.32]) by cam.grad.kiev.ua (8.8.8/8.8.5) with ESMTP id TAA24904; Sat, 28 Nov 1998 19:15:52 +0200 (EET) Received: from Shevchenko.Kiev.UA ([10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id TAA17362; Sat, 28 Nov 1998 19:20:11 +0200 Message-ID: <36604D02.97E37689@Shevchenko.Kiev.UA> Date: Sat, 28 Nov 1998 19:20:34 +0000 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: "oZZ!!!" , hackers@FreeBSD.ORG Subject: Re: SCOs Informix online on FreeBSD? References: <199811281558.HAA00817@dingo.cdrom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > > On Sat, 28 Nov 1998, Mike Smith wrote: > > > > > > Hello! > > > > Does some1 use SCOs Informix online on FreeBSD? > > > > > > I understand there are people doing this, yes. You should be asking > > > emulation-related questions on the -emulation list of course. > > > > > > > I compile kernel with ibcs2, then successfully install it, > > > > then successfully install Informix Online, but can't run oninit. > > > > > > > > oninit: Fatal error in shared memory creation > > > > > > > > Any idea? > > > > > > Sounds like you might be missing the SYSV* options in your kernel > > > config: > > > > > > options SYSVSEM > > > options SYSVMSG > > > options SYSVSHM > > i have it, but oninit don't work... > > > > > > > another idea? > > ktrace, and the ibcs2 syscall table. Work out what's failing and > causing it to print the above message. > default value of sharwed memory segment size in FreeBSD is *very* small. May be you try ti increase it (and number of semaphors) for values near 10M and 100 > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Sat Nov 28 09:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01392 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 09:57:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01385 for ; Sat, 28 Nov 1998 09:57:09 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id MAA08897 for ; Sat, 28 Nov 1998 12:57:16 GMT Message-Id: <199811281257.MAA08897@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 28 Nov 1998 12:54:54 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: Re: vnode_if.c wont compile - MORE INFO 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:55 PM 11/27/98 -0800, Mike Smith wrote: >> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) >> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant >> vnode_if.c:47: parse error before `int' >> *** Error code 1 >> >> Just did a 'config GENERIC" and a make. > >Did you 'make depend' first? >Yes. 'make depend' completes successfully. >one example: >struct vop_lease_args >I cant find this structure defined anywhere? Its seems that some include >file is >missing, or in the wrong path...where should these vop_ functions be declared? Well, if I generate vnode_if.c and vnode_if.h manually from /usr/src/sys/kern and copy the results into the compile directory and vnode_if compiles OK, but I get other, similar failures. It seems that the scripts are not running with the correct files. Any ideas would be appreciated. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 10:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03836 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 10:45:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03830 for ; Sat, 28 Nov 1998 10:45:35 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id NAA00334 for ; Sat, 28 Nov 1998 13:45:18 GMT Message-Id: <199811281345.NAA00334@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 28 Nov 1998 13:43:19 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: Re: vnode_if.c wont compile -FIXED, BUT? 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:55 PM 11/27/98 -0800, Mike Smith wrote: >> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) >> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant >> vnode_if.c:47: parse error before `int' >> *** Error code 1 >> >> Just did a 'config GENERIC" and a make. > >Did you 'make depend' first? >Yes. 'make depend' completes successfully. >one example: >struct vop_lease_args >I cant find this structure defined anywhere? Its seems that some include >file is >missing, or in the wrong path...where should these vop_ functions be Well, i scrubbed the directory manually and reloaded the kernel source and now it works... I do notice that 'config XXXXX" doesnt scrub the directory anymore, is this a good thing? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 10:55:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04432 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 10:55:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04427 for ; Sat, 28 Nov 1998 10:55:44 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA05523; Sat, 28 Nov 1998 10:55:36 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA12103; Sat, 28 Nov 1998 10:55:36 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811280959.LAA01702@ceia.nordier.com> Date: Sat, 28 Nov 1998 10:55:36 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Robert Nordier Subject: Re: Bootmanager -> Bootmanager -> Bootmanager.. :-) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Nov-98 Robert Nordier wrote: > John Polstra wrote: > >> In article <199811272057.WAA29837@ceia.nordier.com>, >> Robert Nordier wrote: >> > >> > As you're using slices, the disklabel command needs a slice argument: >> > eg. da0s1 rather than da0. >> >> Maybe so, but you'd sure never know it from the man page. All of the >> text and all of the examples reference either "sd0" or "/dev/rsd0c". > > My advice was misleading. > > The compatibility slice is implied, in these context, if the disk is > sliced and a slice is not specified. So one should be able to use the > same commands on sliced and unsliced disks. Ah, OK. Thanks for clearing that up. >> Besides that, it should say "da" now, not "sd". > > I've updated the man page. Super! Thanks. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 12:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12520 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 12:42:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12513 for ; Sat, 28 Nov 1998 12:42:07 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id VAA01256; Sat, 28 Nov 1998 21:34:54 +0100 (CET) Message-Id: <199811282034.VAA01256@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: vnode_if.c wont compile -FIXED, BUT? Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 28 Nov 1998 13:43:19 EST." <199811281345.NAA00334@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 21:34:54 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: >At 03:55 PM 11/27/98 -0800, Mike Smith wrote: >>> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) >>> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant >>> vnode_if.c:47: parse error before `int' >>> *** Error code 1 >>> >>> Just did a 'config GENERIC" and a make. >> >>Did you 'make depend' first? > >>Yes. 'make depend' completes successfully. > >>one example: > >>struct vop_lease_args > >>I cant find this structure defined anywhere? Its seems that some include >>file is >>missing, or in the wrong path...where should these vop_ functions be > >Well, i scrubbed the directory manually and reloaded the kernel source and >now it works... > >I do notice that 'config XXXXX" doesnt scrub the directory anymore, is this >a good thing? > the behavior was changesd quite a while ago. ``config -r'' trashes the old directory. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 13:30:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16129 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 13:30:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16124 for ; Sat, 28 Nov 1998 13:30:41 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id PAA00891 for ; Sat, 28 Nov 1998 15:29:52 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id PAA05279 for ; Sat, 28 Nov 1998 15:29:32 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Sat, 28 Nov 1998 15:29:32 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: FreeBSD Hackers Subject: Packet Delay calculation 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 trying to see how much delay a packet typically suffers in the FreeBSD tcp/ip stack. This is what I thought of doing: trace the path of data flow from the place a socket write call is made to the place where the data is actually passed on to the network interface; place calls to microtime() at these locations and see the time difference between them. Could anyone point out potential problems with this approach? Any better alternatives? I'm rather new to this kind of thing and would appreciate some feedback. Thanks, Guru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 16:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03451 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 16:52:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03304 for ; Sat, 28 Nov 1998 16:52:53 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id BAA20748; Sun, 29 Nov 1998 01:52:16 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA02099; Sun, 29 Nov 1998 01:52:15 +0100 (MET) Message-ID: <19981129015215.L9226@follo.net> Date: Sun, 29 Nov 1998 01:52:15 +0100 From: Eivind Eklund To: Dennis , Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: vnode_if.c wont compile References: <199811281206.MAA08754@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811281206.MAA08754@etinc.com>; from Dennis on Sat, Nov 28, 1998 at 12:03:42PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 28, 1998 at 12:03:42PM -0500, Dennis wrote: > At 03:55 PM 11/27/98 -0800, Mike Smith wrote: > >> vnode_if.c:40: `vop_strategy_desc' undeclared here (not in a function) > >> vnode_if.c:40: initializer element for `vfs_op_descs[1]' is not constant > >> vnode_if.c:47: parse error before `int' > >> *** Error code 1 > >> > >> Just did a 'config GENERIC" and a make. > > > >Did you 'make depend' first? > > >Yes. 'make depend' completes successfully. > > one example: > > struct vop_lease_args > > I cant find this structure defined anywhere? Its seems that some include > file is > missing, or in the wrong path...where should these vop_ functions be declared? They're declaredin /sys/kern/vnode_if.src (which is automatically processed to make the C declarations). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 17:00:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04082 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 17:00:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04073 for ; Sat, 28 Nov 1998 17:00:48 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA03968; Sun, 29 Nov 1998 11:30:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA10096; Sun, 29 Nov 1998 11:30:33 +1030 (CST) Message-ID: <19981129113033.R6182@freebie.lemis.com> Date: Sun, 29 Nov 1998 11:30:33 +1030 From: Greg Lehey To: Alfred Perlstein , oZZ!!! Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: SCOs Informix Online... part 2 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alfred Perlstein on Sat, Nov 28, 1998 at 12:02:44PM -0500 WWW-Home-Page: http://www.lemis.com/~grog 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 Saturday, 28 November 1998 at 12:02:44 -0500, Alfred Perlstein wrote: > > On Sat, 28 Nov 1998, oZZ!!! wrote: > >> >> informix@ozz$ ktrace oninit >> oninit: Fatal error in shared memory >> informix@ozz$ kdump >> 15359 ktrace RET ktrace 0 >> 15359 ktrace CALL readlink(0x280bcaf8,0xefbfd710,0x3f) >> 15359 ktrace NAMI "/etc/malloc.conf" >> 15359 ktrace RET readlink -1 errno 2 No such file or directory >> 15359 ktrace CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0) >> 15359 ktrace RET mmap 671944704/0x280d1000 >> 15359 ktrace CALL break(0x804c000) >> 15359 ktrace RET break 0 >> 15359 ktrace CALL break(0x804d000) >> 15359 ktrace RET break 0 >> 15359 ktrace CALL execve(0xefbfd818,0xefbfdcdc,0xefbfdce4) >> 15359 ktrace NAMI "/usr/informix/bin/oninit" >> >> Make some changes in "Shared Memory Parametrs" >> in $INFORMIX/etc/onconfig.std ??? > > No idea about this, but instead of the 'head' of your ktrace, > perhaps you want to show us the end of it? Where it actually has > a problem? I'd guess that this indicates that /usr/informix/bin/oninit is setuid. Try running it again as root. Or do we have a sysctl which will enable tracing setuid programs? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 18:35:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11338 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 18:35:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11282 for ; Sat, 28 Nov 1998 18:34:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id SAA47781; Sat, 28 Nov 1998 18:32:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811290232.SAA47781@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Charles Henrich cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SDSL in Silicon Valley In-reply-to: Your message of "Fri, 27 Nov 1998 17:47:26 PST." <199811280147.RAA01750@crh.mvfx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 18:32:32 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Charles! I got my sdsl router thru http://www.dspnet.net it was part of signing up with them . If you want to know more about the FlowPoint routers here the pointer to the company http://www.flowpoint.com We can do 1.1 MB/sec and it depends on the distance to switch center in fact I had the option of signing up for 1.1 MB/sec however I chose the 416kb/sec rate which for most mbone sessions is more than enough 8) Enjoy Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 19:22:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14828 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 19:22:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14822 for ; Sat, 28 Nov 1998 19:22:08 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id WAA23071 for ; Sat, 28 Nov 1998 22:21:57 -0500 (EST) Date: Sat, 28 Nov 1998 22:21:56 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: random number and primitive polynomial Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am now interested in how a truly random number is generated. The source code is contained in file random_machdep.c. Can anyone tell me where I can find good reference on how the primitive polynomial is related to random number generation (i.e., its properties and role in a random number generator). By the way, I can not find where the file stdlib.h is located. According to the manual, rand() are defined in it. I want to look at the source code of rand() too (although it is said to be a bad random number generator). Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 20:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18136 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 20:01:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from furrball.dyn.ml.org ([207.18.137.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18126 for ; Sat, 28 Nov 1998 20:01:38 -0800 (PST) (envelope-from chris@furrball.dyn.ml.org) Received: (from chris@localhost) by furrball.dyn.ml.org (8.9.1a/8.8.8) id VAA01271; Sat, 28 Nov 1998 21:58:27 -0600 (CST) (envelope-from chris) Date: Sat, 28 Nov 1998 21:58:27 -0600 (CST) From: Chris Costello Message-Id: <199811290358.VAA01271@furrball.dyn.ml.org> To: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: random number and primitive polynomial Reply-To: phoenix@calldei.com In-Reply-To: X-Mailer: mail(1) -- the One True(TM) mail client Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From chris Sat Nov 28 21:43:00 1998 > Date: Sat, 28 Nov 1998 22:21:56 -0500 (EST) > From: zhihuizhang > To: hackers > Subject: random number and primitive polynomial > > > Hi, I am now interested in how a truly random number is generated. The > source code is contained in file random_machdep.c. Can anyone tell me > where I can find good reference on how the primitive polynomial is related > to random number generation (i.e., its properties and role in a random > number generator). In /usr/src/lib/libc/stdlib/rand.c: int rand() { return ((next = next * 1103515245 + 12345) % ((u_long)RAND_MAX + 1)); } In /usr/include/stdlib.h: #define RAND_MAX 0x7fffffff > > By the way, I can not find where the file stdlib.h is located. According > to the manual, rand() are defined in it. I want to look at the source > code of rand() too (although it is said to be a bad random number > generator). /usr/include/stdlib.h It only declares the function in the .h file. Try looking around in /usr/src/lib/libc/stdlib for the stdlib function sources. (NOTE: You must have installed the source distribution to see this.) > > Any help is appreciated. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > > -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 22:03:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27073 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 22:03:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27066 for hackers; Sat, 28 Nov 1998 22:03:07 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199811290603.WAA27066@hub.freebsd.org> Subject: tun interfaces not returned by SIOCGIFCONF ?? To: hackers Date: Sat, 28 Nov 1998 22:03:07 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kernel info: 3.0-CURRENT FreeBSD 3.0-CURRENT #10: Fri Nov 27 12:00:05 tried nmap over ppp on a tun interface. nmap claims it cant find the source address (my address on tun0). nmap uses SIOCGIFCONF to get a ifconf (/sys/net/if.h) which contains a list of ifreq structures. neither tun0 nor ppp0 appear on the list. (ifconfig -a uses a sysctl to get the list, by the way). is it a bug or a misconfiguration on my part? ~~~~~~~~~~~~~~~~~~~~ in this code snippit, i always call inet_ntoa() eventhough the argument may no be an address but rather other data. code from nmap (printf()'s are my additions): for (ifr = (struct ifreq *) pbuf; ifr && *((char *) ifr) && ((char *) ifr) < pbuf + ifc.ifc_len; ((*(char **) &ifr) += sizeof(ifr->ifr_name) + len)) { sin = (struct sockaddr_in *) & ifr->ifr_addr; printf("ifc_len: %d (currently at %u)\n", ifc.ifc_len, (char *)ifr - pbuf); printf("trying: %s: %s\n", ifr->ifr_name, inet_ntoa(sin->sin_addr)); if (sin->sin_addr.s_addr == addr->s_addr) { /* * Stevens does this in UNP, so it may be useful in * some cases */ if ((p = strchr(ifr->ifr_name, ':'))) *p = '\0'; /* * If an app gives me less than 64 bytes, they * deserve to be overflowed! */ strncpy(dev, ifr->ifr_name, 63); dev[63] = '\0'; return 1; } } if (!ifr) printf("ifr\n"); else if (!(*((char *)ifr))) printf("*((char *)ifr)\n"); else if (!((char *)ifr < pbuf + ifc.ifc_len)) printf("(char *) ifr < pbuf + ifc.ifc_len\n"); ~~~~~~~~~~~~~~~~~~~~ nmap shows: Aspen:[399] ./nmap -s -D -n -v -S 207.172.87.229 ....... Starting nmap V. 1.51 by Fyodor (fyodor@dhp.com, www.dhp.com/~fyodor/nmap/) ifc_len: 412 (currently at 0) trying: lp0: 34.3.0.0 ifc_len: 412 (currently at 36) trying: ep0: 6.3.6.0 ifc_len: 412 (currently at 72) trying: ep0: 192.168.250.10 *((char *)ifr) Could not figure out what device to send the packet out on! You might possibly want to try -S (but this is probably a bigger problem) ~~~~~~~~~~~~~~~~~~~~ ifconfig -a shows: Aspen:[400] ifconfig -a lp0: flags=8810 mtu 1500 ep0: flags=c843 mtu 1500 inet 192.168.250.10 netmask 0xffffff00 broadcast 192.168.250.255 ether 00:60:8c:79:b5:4a tun0: flags=8051 mtu 1006 inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000 inet 207.172.87.115 --> 255.255.255.255 netmask 0xffffffff inet 207.172.87.229 --> 10.11.64.66 netmask 0xffffff00 tun1: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 sl1: flags=c010 mtu 552 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ~~~~~~~~~~~~~~~~~~~~ jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 28 23:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02491 for freebsd-hackers-outgoing; Sat, 28 Nov 1998 23:41:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02486 for ; Sat, 28 Nov 1998 23:41:42 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:CwN2DzFmjwqpvAetNi8muvrnJ8yi2Kj7@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA16372; Sun, 29 Nov 1998 09:41:30 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:ShCVU8W/dBwXBSdStJLVBv7WAIw0grcm@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id JAA15510; Sun, 29 Nov 1998 09:41:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811290741.JAA15510@greenpeace.grondar.za> To: zhihuizhang cc: hackers Subject: Re: random number and primitive polynomial In-Reply-To: Your message of " Sat, 28 Nov 1998 22:21:56 EST." References: Date: Sun, 29 Nov 1998 09:41:27 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG zhihuizhang wrote: > Hi, I am now interested in how a truly random number is generated. The > source code is contained in file random_machdep.c. Can anyone tell me > where I can find good reference on how the primitive polynomial is related > to random number generation (i.e., its properties and role in a random > number generator). Dig through the RFC's; there is one that describes RNGs quite well (Its name is obvious enough). The polynomial is used to "stir" the "entropy pool", to make sure that the numbers have a decent probability spectrum. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message