From owner-freebsd-hackers Sun Jun 30 02:52:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28533 for hackers-outgoing; Sun, 30 Jun 1996 02:52:13 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA28481 for ; Sun, 30 Jun 1996 02:51:52 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA21941; Sun, 30 Jun 1996 11:50:43 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA26028; Sun, 30 Jun 1996 11:50:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA06125; Sun, 30 Jun 1996 11:06:02 +0200 (MET DST) From: J Wunsch Message-Id: <199606300906.LAA06125@uriah.heep.sax.de> Subject: Re: Alternate lists for more verbose CVS commit messages? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 30 Jun 1996 11:06:01 +0200 (MET DST) Cc: hsu@clinet.fi (Heikki Suonsivu) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199606292040.XAA19042@cantina.clinet.fi> from Heikki Suonsivu at "Jun 29, 96 11:40:57 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Heikki Suonsivu wrote: > > I often would like to know more about problems certain commit might fix, > and see what modifications were committed. Could it be possible to create > alternate commit lists which would receive detailed commit messages ? You've already got a couple of answers, but just in case: If you are subscribed to the various cvs-foo lists (or to cvs-all), this _is_ already the detailed commit message. It is as detailed as the committer felt it should be. You are, of course, free to pick it, review the changes, and create an alternate catalog of "Heikki's commented cvs commit messages". :-) Sorry, the commit message itself should not replicate the entire code that has been changed, it should _summarize_ the modifications, and give some insight into the reasons the committer had to make this change. You are infact expected to review the source if this doesn't suffice to you. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jun 30 04:40:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA05232 for hackers-outgoing; Sun, 30 Jun 1996 04:40:40 -0700 (PDT) Received: from actcom.co.il (root@actcom.co.il [192.114.47.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA05108 for ; Sun, 30 Jun 1996 04:39:14 -0700 (PDT) Received: from dinosaur by actcom.co.il with SMTP (8.6.12/actcom-0.1) id OAA20739; Sun, 30 Jun 1996 14:39:18 +0300 (rfc931-sender: denis@p5.ta1.actcom.co.il [192.115.23.35]) Message-ID: <31D675EB.171AA7AA@actcom.co.il> Date: Sun, 30 Jun 1996 14:41:15 +0200 From: denis X-Mailer: Mozilla 3.0b4Gold (X11; I; Linux 2.0.0 i586) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org CC: Mattias Pantzare , "Michael Hancock Jordan K. Hubbard" Subject: Re: Dynamically Allocatable Name Service (DANS) References: <8709.835583510@time.cdrom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > I understand what can be done. Rocket and bike analogies just makes it > > sound like name serving is a trivial exercise. > > It's also already in the works - he needs to read the RFCs (I sent > this on to Paul Vixie who was quite amused). > > Jordan Hi, I'm sorry I latened with my response, but I was away last week. I read all the discussion you led on the last Sunday about my proposition and I want to say everyone who participated in it thank you. Now, I want to answer the Jordan K. Hubbard's last message which is at the top of my replay and which is (as I know) was the last on the subject. Before starting writing this DNS server and posting my idea to the net, I've read all the material I had about the DNS service includ- ing various RFCs and internet draft and much more. I know about the Paul Vixie's work, but it is exactly what I called Rocket motor for a bike. You see, he does exactly what I want to do, but using textfile database, which doesn't improve performance and doesn't allow using TTL's too (as someone noticed about my idea) -- Regards, Denis -- +----------------------------------------------------------------+ | Denis Kopylenko, Tel Aviv, Israel. Unix System Programmer in | | Algorithmic Research Ltd. Data Protection Solutions. | | OSF1, IRIX, Linux, FreeBSD | +----------------------------------------------------------------+ From owner-freebsd-hackers Sun Jun 30 07:03:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA13837 for hackers-outgoing; Sun, 30 Jun 1996 07:03:08 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA13831 for ; Sun, 30 Jun 1996 07:03:05 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id HAA00809 for ; Sun, 30 Jun 1996 07:04:03 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id AAA14509 for freebsd-hackers@freebsd.org; Mon, 1 Jul 1996 00:01:57 +1000 From: Julian Assange Message-Id: <199606301401.AAA14509@suburbia.net> Subject: rsync To: freebsd-hackers@freebsd.org Date: Mon, 1 Jul 1996 00:01:56 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The below looks like a phenominally useful replacement for sup. According to the tech report, total uncompressed transfer between two kernel trees was around half the size of the *diffs*. It also streams data in both directions, effectively removing rtt as an important consideration. WHAT IS RSYNC? -------------- rsync is a replacement for rcp that has many more features. rsyns uses the "rsync algorithm" which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand. At first glance this may seem impossible because the calculation of diffs between two files normally requires local access to both files. A technical report describing the rsync algorithm is included with this package. USAGE ----- Basically you use rsync just like rcp, but rsync has many additional options. Here is a brief description of available options: -v, --verbose increase verbosity -c, --checksum always checksum -a, --archive archive mode (same as -rlptDog) -r, --recursive recurse into directories -b, --backup make backups (default ~ extension) -u, --update update only (don't overwrite newer files) -l, --links preserve soft links -H, --hard-links preserve hard links -p, --perms preserve permissions -o, --owner preserve owner (root only) -g, --group preserve group -D, --devices preserve devices (root only) -t, --times preserve times -S, --sparse handle sparse files efficiently -n, --dry-run show what would have been transferred -x, --one-file-system don't cross filesystem boundaries -B, --block-size SIZE checksum blocking size -e, --rsh COMMAND specify rsh replacement --rsync-path PATH specify path to rsync on the remote machine -C, --cvs-exclude auto ignore files in the same way CVS does --delete delete files that don't exist on the sending side -I, --ignore-times don't exclude files that match length and time --exclude FILE exclude file FILE --exclude-from FILE exclude files listed in FILE --suffix SUFFIX override backup suffix --csum-length LENGTH set the checksum length --version print version number SETUP ----- Rsync uses rsh or ssh for communication. It does not need to be setuid and requires no special privilages for installation. It does not require a inetd entry or a daemon. You must, however, have a working rsh or ssh system. Using ssh is recommended for its security and compression features. To install rsync, first run the "configure" script. This will create a Makefile and config.h appropriate for your system. Then type "make". Once built put a copy of rsync in your search path on the local and remote systems (or use "make install"). That's it! COPYRIGHT --------- Rsync was written by Andrew Tridgell and Paul Mackerras, and is available under the GPL. Andrew.Tridgell@anu.edu.au paulus@cs.anu.edu.au AVAILABILITY ------------ The main ftp site for rsync is ftp://samba.anu.edu.au/pub/rsync -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Sun Jun 30 09:49:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27284 for hackers-outgoing; Sun, 30 Jun 1996 09:49:59 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA27239; Sun, 30 Jun 1996 09:48:34 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id MAA10769; Sun, 30 Jun 1996 12:43:08 -0400 (EDT) Date: Sun, 30 Jun 1996 12:43:57 -0400 (EDT) From: Brian Tao To: Terry Lambert cc: hackers@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: I need help on this one - please help me track this guy down! In-Reply-To: <199606240651.XAA27306@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Jun 1996, Terry Lambert wrote: > > 9) Make sure you aren't running routed -q. Why not? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sun Jun 30 10:31:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA29450 for hackers-outgoing; Sun, 30 Jun 1996 10:31:41 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA29444 for ; Sun, 30 Jun 1996 10:31:39 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id aj12798; 30 Jun 96 17:08 +0100 Received: from am221.du.pipex.com ([193.130.252.221]) by relay-3.mail.demon.net id aa01237; 30 Jun 96 16:59 +0100 Received: (from james@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id PAA01382; Sun, 30 Jun 1996 15:53:34 GMT Date: Sun, 30 Jun 1996 15:53:34 GMT From: James Raynard Message-Id: <199606301553.PAA01382@jraynard.demon.co.uk> To: freebsd-hackers@freebsd.org Subject: DPT SCSI Controllers Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.bsd.netbsd.misc In-Reply-To: <4r5cdn$jc2@library.erc.clarkson.edu> Organization: A FreeBSD Box Cc: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has any progress been made on supporting these? This sounds like too good an offer to pass up! ------- start of forwarded message ------- From: shapircs@craft.camp.clarkson.edu (Carl S. Shapiro) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.bsd.netbsd.misc Subject: Re: SCSI Controllers Followup-To: comp.unix.bsd.freebsd.misc,comp.unix.bsd.netbsd.misc Date: 30 Jun 1996 08:04:07 GMT Organization: Clarkson University Lines: 18 Message-ID: <4r5cdn$jc2@library.erc.clarkson.edu> NNTP-Posting-Host: fire.camp.clarkson.edu James Raynard (james@jraynard.demon.co.uk) wrote: (stuff cut out) : None of the free OS's support them AFAIK as all the necessary info is : subject to NDA's. However, I remember seeing someone on one of the : FreeBSD mailing lists saying they were negotiating with DPT and they : thought it looked reasonably promising. Linux does indeed support the DPT caching SCSI cards. Juding by the comments in the Linux DPT driver source, DTP actually provided some measure of assistance. If somebody actually cares to write a driver for NetBSD/FreeBSD, I would not mind providing assitance in the form of an EISA SmartCache+ card loan/purchase (provided I had some kind of gaurantee of something being produce). Good Luck. Carl ------- end of forwarded message ------- From owner-freebsd-hackers Sun Jun 30 12:36:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09573 for hackers-outgoing; Sun, 30 Jun 1996 12:36:15 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09553 for ; Sun, 30 Jun 1996 12:36:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id NAA00892; Sun, 30 Jun 1996 13:35:59 -0600 (MDT) Message-Id: <199606301935.NAA00892@rover.village.org> To: Ulf Zimmermann Subject: Re: Cross compile of FreeBSD Cc: hackers@FreeBSD.org In-reply-to: Your message of Fri, 28 Jun 1996 23:17:17 PDT Date: Sun, 30 Jun 1996 13:35:58 -0600 From: Warner Losh Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : Has anyone every tried to cross compile the FreeBSD kernel or maybe even : make world ? For example on a SGI system ? That's going to be hard, as I'm not sure that ld is cross compilable in the FreeBSD distribution, and the ld in binutils doesn't support FreeBSD. Warner From owner-freebsd-hackers Sun Jun 30 14:47:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19719 for hackers-outgoing; Sun, 30 Jun 1996 14:47:52 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA19697 for ; Sun, 30 Jun 1996 14:47:47 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id OAA04945; Sun, 30 Jun 1996 14:45:17 -0700 (PDT) Message-Id: <199606302145.OAA04945@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: James Raynard cc: freebsd-hackers@freebsd.org Subject: Re: DPT SCSI Controllers In-reply-to: Your message of Sun, 30 Jun 96 15:53:34 +0000. <199606301553.PAA01382@jraynard.demon.co.uk> Date: Sun, 30 Jun 1996 14:45:17 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Has any progress been made on supporting these? This sounds like too >good an offer to pass up! Driver work is in progress, but in the very early stages... ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 30 15:20:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21672 for hackers-outgoing; Sun, 30 Jun 1996 15:20:49 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA21666 for ; Sun, 30 Jun 1996 15:20:46 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id PAA16250; Sun, 30 Jun 1996 15:21:57 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id IAA02188; Mon, 1 Jul 1996 08:20:26 +1000 From: Julian Assange Message-Id: <199606302220.IAA02188@suburbia.net> Subject: Re: rsync To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 1 Jul 1996 08:20:25 +1000 (EST) Cc: proff@suburbia.net, freebsd-hackers@freebsd.org In-Reply-To: <17184.836172801@time.cdrom.com> from "Jordan K. Hubbard" at Jun 30, 96 03:13:21 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It does look cool. There's a package version in: > ftp://time.cdrom.com/pub/rsync-1.4.5.tgz > > and here's a port of it: > > begin 664 rsync.tar.gz [...] > end What are the chances of installing it on freefall for world access? If need be I can hack it up to act like a daemon with random backoff (the only real advantage sup has) -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Sun Jun 30 15:56:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23705 for hackers-outgoing; Sun, 30 Jun 1996 15:56:28 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23699 for ; Sun, 30 Jun 1996 15:56:26 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA17731; Sun, 30 Jun 1996 15:54:58 -0700 (PDT) To: Julian Assange cc: freebsd-hackers@freebsd.org Subject: Re: rsync In-reply-to: Your message of "Mon, 01 Jul 1996 08:20:25 +1000." <199606302220.IAA02188@suburbia.net> Date: Sun, 30 Jun 1996 15:54:57 -0700 Message-ID: <17729.836175297@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What are the chances of installing it on freefall for world access? If need > be I can hack it up to act like a daemon with random backoff (the only real > advantage sup has) About nil until the various maintainers have had a couple of weeks to look at and test this new thing, first. :-) Jordan From owner-freebsd-hackers Sun Jun 30 17:50:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03230 for hackers-outgoing; Sun, 30 Jun 1996 17:50:12 -0700 (PDT) Received: from emout18.mail.aol.com (emout18.mx.aol.com [198.81.11.44]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA03216; Sun, 30 Jun 1996 17:50:07 -0700 (PDT) From: Eyeballl@aol.com Received: by emout18.mail.aol.com (8.6.12/8.6.12) id TAA06974; Sun, 30 Jun 1996 19:31:57 -0400 Date: Sun, 30 Jun 1996 19:31:57 -0400 Message-ID: <960630193156_567341975@emout18.mail.aol.com> To: Eyeballl@aol.com Subject: Are you a programmer? Do you wear glasses? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk No this isn't SPAM and this isn't a marketing letter. I found a great discount service for eyewear and I promised my buddy I would send this information to a few people on the internet. I was in a newsgroup recently and saw your comments. I thought you might be a programmer like me. If you are, chances are good you wear glasses. I wear glasses (as most of us do) and my buddy turned me on to a way of buying my glasses (my subscription sun glasses, too) at about 50% to 75% of retail. No big deal, no money in it for me...I was just thrilled with it and told him I would pass the word on to anyone I met. I figured I could help people the way he helped me...that's what the internet is supposed to be about, right? If you do wear glasses and you want more info about how to contact my buddy to get a discount on your glasses, too, just reply with "send more info please" to eyeballl@aol.com. I'll send you some more specifics and a phone and fax number where you can sign up if you like the plan this guy has. I know I do. It's pretty low-tech...not very exciting... Discount eye glasses. But, what the heck, if you wear them, this is a way to pay less for them. Again, this is not SPAM, this is not some marketing gimmick, this is just a user of the net, trying to help other net users with a simple discount on a commodity most of us use. If I find a great discount on bread or tires, I'll probably tell people about that stuff, too. :) See ya later and thanks for reading my message. Scott eyeballl@aol.com From owner-freebsd-hackers Sun Jun 30 18:15:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05799 for hackers-outgoing; Sun, 30 Jun 1996 18:15:24 -0700 (PDT) Received: from sujal.prognet.com (root@morrison-c00.aa.net [204.157.220.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05781 for ; Sun, 30 Jun 1996 18:15:21 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by sujal.prognet.com (8.7.5/8.6.12) with SMTP id SAA01794; Sun, 30 Jun 1996 18:14:56 -0700 (PDT) Date: Sun, 30 Jun 1996 18:14:55 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@sujal.prognet.com To: "Jordan K. Hubbard" cc: Heikki Suonsivu , freebsd-hackers@FreeBSD.org Subject: Re: Alternate lists for more verbose CVS commit messages? In-Reply-To: <13317.836105910@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Jun 1996, Jordan K. Hubbard wrote: > > I often would like to know more about problems certain commit might fix, > > and see what modifications were committed. Could it be possible to create > > alternate commit lists which would receive detailed commit messages ? > > Getting a full CVS diff would be helpful, if nothing else. > > Uh, what's wrong with simply subscribing to a cvs-* list and then > cross-referencing the revision numbers mentioned with the > http://www.freebsd.org/cgi-bin/cvsweb CGI script to get the diffs you > want? Or just pipe your piece of mail from cvs-* into the attached script and you'll get an instant diff :-) It works 98% of the time (gets confused on some branch commits, added files, and imports). If someone wants to make this really work well, that'll be cool (It's good enough for me :-) Sujal -- Cut -- #!/usr/bin/perl # FreeBSD cvs-* -> diff processor # Author: Sujal Patel # This program is in the Public Domain while (<>) { if (/^ ([\d.]*)\s*(\+\d* \-\d*)\s*([\S\/]*)\s*/) { $rev = $1; $changes = $2; $path = $3; if ($rev =~ /((\d*\.)+)(\d*)/) { if ($3 == 1) { printf ("\n *** Can't determine previous version of %s\n", $path); printf (" *** Skipping File\n\n"); next; } $oldrev = sprintf ("$1%d", $3 - 1); } $line = sprintf("GET /cgi-bin/cvsweb/$path?r1=text&tr1=$oldrev&r2=text&tr2=$rev&f=i\n"); $af_inet = 2; $sock_stream = 1; $sockaddr = 'S n a4 x8'; chop($hostname = `hostname`); ($name, $aliases, $proto) = getprotobyname('tcp'); ($name, $aliases, $type, $len, $thisaddr) = gethostbyname($hostname); ($name, $aliases, $type, $len, $thataddr) = gethostbyname("www.FreeBSD.org"); $this = pack($sockaddr, $af_inet, 0, $thisaddr); $that = pack($sockaddr, $af_inet, 80, $thataddr); socket(SOCK, $af_inet, $sock_stream, $proto) || die $!; bind(SOCK, $this) || die $!; connect(SOCK, $that) || die $!; select(SOCK); $| = 1; select(STDOUT); print SOCK $line; while () { print; } } } From owner-freebsd-hackers Sun Jun 30 18:52:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA09102 for hackers-outgoing; Sun, 30 Jun 1996 18:52:00 -0700 (PDT) Received: from wombat.gnu.ai.mit.edu (wombat.gnu.ai.mit.edu [128.52.46.26]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA09094 for ; Sun, 30 Jun 1996 18:51:56 -0700 (PDT) Received: by wombat.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id VAA06238; Sun, 30 Jun 1996 21:14:21 -0400 Date: Sun, 30 Jun 1996 21:14:21 -0400 Message-Id: <199607010114.VAA06238@wombat.gnu.ai.mit.edu> To: gpalmer@freebsd.org CC: dgy@rtd.com, freebsd-hackers@freefall.freebsd.org In-reply-to: <13617.836075023@palmer.demon.co.uk> (gpalmer@freebsd.org) Subject: Re: freefall.mc patch From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to discuss BUY-BACK PROVISIONS with at least six studio SLEAZEBALLS!! Don Yuniskis wrote in message ID <199606291241.FAA12411@seagull.rtd.com>: > Actually, none of the 3 lines that I've left in above are any use, to > my knowledge the UUCP_RELAY machine doesn't exist anymore, and I'm not > at all sure about the BITNET or CSNET stuff at all. At last check, BITNET died about a year and a half ago. At least, I recall throwing a party in the CS lab for it. I could be misteaken. Hack hack, Joel -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Sun Jun 30 22:38:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA27205 for hackers-outgoing; Sun, 30 Jun 1996 22:38:43 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA27107 for ; Sun, 30 Jun 1996 22:38:16 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id WAA05015 for freebsd-hackers@freefall.cdrom.com; Sun, 30 Jun 1996 22:37:58 -0700 (MST) From: Don Yuniskis Message-Id: <199607010537.WAA05015@seagull.rtd.com> Subject: Re: Are you a programmer? Do you wear glasses? To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD hackers) Date: Sun, 30 Jun 1996 22:37:58 -3100 (MST) In-Reply-To: <960630193156_567341975@emout18.mail.aol.com> from "Eyeballl@aol.com" at Jun 30, 96 07:31:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that Eyeballl@aol.com said: > > No this isn't SPAM and this isn't a marketing letter. I found a great Yeah, right. And the Pope is a Moslem! Sheesh, do we need to install a robot to start checking for garbage posts? This looks (from the headers) strangely suspicious... Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and mail it to this guy? Maybe 10K each day for the next year or so? Or, is it better to complain to the folks at AOL?? --don From owner-freebsd-hackers Sun Jun 30 23:14:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA00777 for hackers-outgoing; Sun, 30 Jun 1996 23:14:17 -0700 (PDT) Received: from cd.iidpwr.com ([204.33.177.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA00765 for ; Sun, 30 Jun 1996 23:14:12 -0700 (PDT) Received: (from tam@localhost) by cd.iidpwr.com (8.6.12/8.6.12) id XAA10539; Sun, 30 Jun 1996 23:16:26 -0700 Date: Sun, 30 Jun 1996 23:16:26 -0700 (PDT) From: Tony Tam To: FreeBSD hackers Subject: Netscape is out of memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am experiencing a very interesting error message with Netscape Ver. 2.02 and Ver. 3.0b4 for FreeBSD after I installed a commercial firewall called BorderWare. What is funny about this situation is I don't have any problem with Netscape for Windows or NT. The error message is "Netscape is out of memory. Try quitting some other applications or closing some windows." I got this error message as soon as I hit the "SEND" button on "Message Composition" window. But I don't have any problem with Netscape on Windows 3.1 or Windows NT. All the PC are on the same network. For the above PCs, the Outgoing SMTP server are all set to the same firewall machine. I can retrieve mail without any problem, but I cannot send mail with Netscape for FreeBSD. I was having the same problem even before I installed the firewall; however, by booting my FreeBSD box, I could send mail without too much problem. Now, with the firewall in place, reboot doesn't fix my problem anymore. Any idea? Yours truly, Tony Tam +------------------------------+--------------------------------+ | Tony Tam | Imperial Irrigation District | | Imperial Irrigation District | 333 E. Barioni Blvd. | | email: tam@cd.iidpwr.com | P.O. BOX 937 | | tel: (619) 339 9454 | Imperial, CA 92251 | | fax: (619) 339 9189 | U.S.A. | +------------------------------+--------------------------------+ From owner-freebsd-hackers Mon Jul 1 00:32:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05731 for hackers-outgoing; Mon, 1 Jul 1996 00:32:26 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA05724 for ; Mon, 1 Jul 1996 00:32:24 -0700 (PDT) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.7.4/8.6.12) with SMTP id DAA01547; Mon, 1 Jul 1996 03:32:09 -0400 (EDT) Message-Id: <199607010732.DAA01547@ns2.harborcom.net> Comments: Authenticated sender is From: "Bradley Dunn" Organization: Harbor Communications To: Don Yuniskis Date: Mon, 1 Jul 1996 03:27:06 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Are you a programmer? Do you wear glasses? Reply-to: dunn@harborcom.net CC: hackers@freebsd.org Priority: normal X-mailer: Pegasus Mail for Win32 (v2.31) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 30 Jun 96 at 22:37, Don Yuniskis wrote: > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > mail it to this guy? Maybe 10K each day for the next year or so? :). AOL has like a 300K limit on mail messages. Probably because people who use AOL tend to piss other people off. > Or, is it better to complain to the folks at AOL?? You could try it. They are quite clueless, though. They might tell you to go to the TOS chat room to report it. :) Bradley Dunn Harbor Communications From owner-freebsd-hackers Mon Jul 1 01:22:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09738 for hackers-outgoing; Mon, 1 Jul 1996 01:22:48 -0700 (PDT) Received: from aphrodite.funet.fi (root@[193.166.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA09676 for ; Mon, 1 Jul 1996 01:21:21 -0700 (PDT) Received: (from jau@localhost) by aphrodite.funet.fi (8.7.4/8.6.12+CSC-2.1) id LAA24412; Mon, 1 Jul 1996 11:18:09 +0300 (EET DST) From: Jukka Antero Ukkonen Message-Id: <199607010818.LAA24412@aphrodite.funet.fi> Subject: Re: POSIX.4 signals + other POSIX.4 stuff to FreeBSD... To: bde@zeta.org.au (Bruce Evans) Date: Mon, 1 Jul 1996 11:18:09 +0300 (EET DST) Cc: terry@lambert.org, bde@zeta.org.au, hackers@freebsd.org In-Reply-To: <199606290650.QAA27894@godzilla.zeta.org.au> from "Bruce Evans" at Jun 29, 96 04:50:04 pm Latin-Date: Lunti I Iulie a.d. MCMXCVI Organization: FUNET/CSC Phone: +358-0-6215280 (home) Content-Conversion: prohibited X-Mailer: ELM [version 2.4 PL25+pgp] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoting Bruce Evans: > > >/* > > * Signal vector "template" used in sigaction call. > > */ > >struct sigaction { > > union { > > /* > > * These two could be separate fields quite as well. > > * > > * Either a simple POSIX.1 signal handler > > * with additional BSD style parameters ... > > */ > > void (*sa_handler) _P((int, ...)); > > /* > > * ... or a more complex POSIX.4 signal handler > > */ > > void (*sa_sigaction) _P((int, siginfo_t *, void *)); > > }; > > How can POSIX.4 specify this? It is incompatible with the POSIX.1 > struct sigaction (as is the varargs sa_handler). I do not think that is really the case. You can still refer to sa.sa_handler just as before and it's positioning within the struct can remain unchanged. Oops. Don't bother too much with the variable ... arguments in the sa_handler field. The code above was extracted from the header files belonging to my personal C library, which in some cases may be a bit unorthodox beast. My C library has a rather relaxed attitude towards all kinds of BSD style and other extensions. It is a sort of "everything and then some" implementation. Those dots were put there just to keep the compiler quiet when I needed the BSD style extended argument list. They don't break anything really, but for reasons of strict POSIX portability one should of course envelope that within #ifdef _POSIX_SOURCE or something. > The user sigismember() is more or less required to check the bounds, so > it needs to be larger and uglier. The kernel should probably check `sig' > in advance and then use special kernel versions of the signal manipulation > functions. Right - the kernel should check that the signal code is within the range of known signals. It should be done almost the first thing at the beginning of the system calls that deal with the signals. It would be much more of an effort if the macros were really changed to check the range every time they are used. Cheers, // jau ------ / Jukka A. Ukkonen, FUNET / Centre for Scientific Computing /__ M.Sc. (sw-eng & cs) Tel: (Home) +358-0-6215280 / Internet: ukkonen@csc.fi (Work) +358-0-4573208 v Internet: jau@funet.fi (Mobile) +358-400-606671 From owner-freebsd-hackers Mon Jul 1 01:48:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA11140 for hackers-outgoing; Mon, 1 Jul 1996 01:48:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA11032 for ; Mon, 1 Jul 1996 01:47:29 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA18029; Mon, 1 Jul 1996 18:40:26 +1000 Date: Mon, 1 Jul 1996 18:40:26 +1000 From: Bruce Evans Message-Id: <199607010840.SAA18029@godzilla.zeta.org.au> To: bde@zeta.org.au, jau@aphrodite.funet.fi Subject: Re: POSIX.4 signals + other POSIX.4 stuff to FreeBSD... Cc: hackers@freebsd.org, terry@lambert.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >struct sigaction { >> > union { >> >.... >> > void (*sa_handler) _P((int, ...)); > then some" implementation. Those dots were put there just to keep > the compiler quiet when I needed the BSD style extended argument > list. They don't break anything really, but for reasons of strict They break the possibility of compiling (all) applications with -mrtd on i386's, and they break implementations where the equivalent of -mrtd or some other complicated (efficient) arg passing convention is standard. >> The user sigismember() is more or less required to check the bounds, so >> it needs to be larger and uglier. The kernel should probably check `sig' >> in advance and then use special kernel versions of the signal manipulation >> functions. > Right - the kernel should check that the signal code is within > the range of known signals. It should be done almost the first > thing at the beginning of the system calls that deal with the > signals. It would be much more of an effort if the macros were > really changed to check the range every time they are used. The kernel shouldn't use the user macros because it would become slower if the the user macros were fixed to actually meet their specification. Bruce From owner-freebsd-hackers Mon Jul 1 01:58:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA11598 for hackers-outgoing; Mon, 1 Jul 1996 01:58:43 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA11590 for ; Mon, 1 Jul 1996 01:58:36 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.6.11/8.6.9) id LAA04129; Mon, 1 Jul 1996 11:01:24 GMT Date: Mon, 1 Jul 1996 11:01:24 +0000 () From: Andrzej Bialecki To: FreeBSD hackers Subject: SLIP problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all, I have impression that SLIP implementation in 2.1R is somewhat broken. I tried hard to run SLIP between FreeBSD box and certain device (let's call it ``a station''). In order to run SLIP that device requires DTR to be low (so I had to prepare a special cable with DTR cut off). I didn't encounter ANY problems while running SLIP on the same physical machine, but under Win 3.11 (+Trumpet) (so the hardware part seems OK). But under FreeBSD there were strange things going. I configured sl0 exactly along The Handbook (with my own IPs, of course). ifconfig sl0 said something like: sl0: flags=c010 mtu 1000 148.81.175.2 ---> 148.81.175.1 netmask 0xffffff00 I configured remote station properly (it ran with Trumpets). Then I did slattach -h -l -s 9600 /dev/cuaa1 (COM2). After about 2 minutes I was able to ping the remote side (traceroute was also OK). Then I left ping running on one tty, and went to another in order to make telnet. And here something strange happened - ping got killed, i.e. no longer received echoes from remote side. The telnet didn't get through as well. The line seemed dead. I killed slattach and run it again, but the line still was dead (though netstat -r, and ifconfig both showed UP). Only through reboot I was able again to ping the remote station. Any ideas? Help? Where am I wrong? Thanks in advance, Andy +------------------------------------------------------------------------+ | ANDRZEJ BIALECKI, , NASK (WARMAN) | | Research and Academic Network in Poland, Warsaw Area Network | | phone: (+48 22) 414115, Bartycka 18, 00-716 Warsaw, Poland | +------------------------------------------------------------------------+ -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2i mQCNAzFydDYAAAEEALAheWaKO7Uny4bAmT6AC2tEAPK+9VSUxX5ynA3f3yTQtXwL xovpwTQNCbqjBle8sME1hTIqgTkCHmucpucejc1z5zevdVPX4mOCeDcKOyeRf5VA XjI8YaPan/SiAfw5+GtXeiEbdf5N78Xd0old/vPKXwKebHCv7nhAoCU+bhJVAAUR tCZBbmRyemVqIEJpYWxlY2tpIDxhYmlhbEB3YXJtYW4ub3JnLnBsPg== =xasZ -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hackers Mon Jul 1 02:59:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA14097 for hackers-outgoing; Mon, 1 Jul 1996 02:59:25 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA14092 for ; Mon, 1 Jul 1996 02:59:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id CAA00257; Mon, 1 Jul 1996 02:59:12 -0700 (PDT) Message-Id: <199607010959.CAA00257@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Andrzej Bialecki cc: FreeBSD hackers Subject: Re: SLIP problems In-reply-to: Your message of "Mon, 01 Jul 1996 11:01:24 -0000." From: David Greenman Reply-To: davidg@root.com Date: Mon, 01 Jul 1996 02:59:12 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I have impression that SLIP implementation in 2.1R is somewhat broken. I >tried hard to run SLIP between FreeBSD box and certain device (let's call >it ``a station''). In order to run SLIP that device requires DTR to be >low (so I had to prepare a special cable with DTR cut off). > >I didn't encounter ANY problems while running SLIP on the same physical >machine, but under Win 3.11 (+Trumpet) (so the hardware part seems OK). But >under FreeBSD there were strange things going. > >I configured sl0 exactly along The Handbook (with my own IPs, of course). >ifconfig sl0 said something like: > >sl0: flags=c010 mtu 1000 > 148.81.175.2 ---> 148.81.175.1 netmask 0xffffff00 > >I configured remote station properly (it ran with Trumpets). >Then I did slattach -h -l -s 9600 /dev/cuaa1 (COM2). After about 2 >minutes I was able to ping the remote side (traceroute was also OK). >Then I left ping running on one tty, and went to another in order to >make telnet. And here something strange happened - ping got killed, i.e. >no longer received echoes from remote side. The telnet didn't get through >as well. The line seemed dead. >I killed slattach and run it again, but the line still was dead (though >netstat -r, and ifconfig both showed UP). Only through reboot I was able >again to ping the remote station. > >Any ideas? Help? Where am I wrong? Here's a guess: you're running routed on the FreeBSD machine, but the Trumpet machine doesn't send RIP routing packets, so routed deletes the route to the interface. If this is the problem, stop running routed (see /etc/sysconfig), and add any needed static routes instead (you may not need any). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 1 04:02:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA19059 for hackers-outgoing; Mon, 1 Jul 1996 04:02:36 -0700 (PDT) Received: from aphrodite.funet.fi (root@[193.166.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18942 for ; Mon, 1 Jul 1996 04:01:09 -0700 (PDT) Received: (from jau@localhost) by aphrodite.funet.fi (8.7.4/8.6.12+CSC-2.1) id NAA24561; Mon, 1 Jul 1996 13:58:41 +0300 (EET DST) From: Jukka Antero Ukkonen Message-Id: <199607011058.NAA24561@aphrodite.funet.fi> Subject: Re: POSIX.4 signals + other POSIX.4 stuff to FreeBSD... To: bde@zeta.org.au (Bruce Evans) Date: Mon, 1 Jul 1996 13:58:41 +0300 (EET DST) Cc: hackers@freebsd.org In-Reply-To: <199607010840.SAA18029@godzilla.zeta.org.au> from "Bruce Evans" at Jul 1, 96 06:40:26 pm Latin-Date: Lunti I Iulie a.d. MCMXCVI Organization: FUNET/CSC Phone: +358-0-6215280 (home) Content-Conversion: prohibited X-Mailer: ELM [version 2.4 PL25+pgp] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoting Bruce Evans: > > >> >struct sigaction { > >> > union { > >> >.... > >> > void (*sa_handler) _P((int, ...)); > > > then some" implementation. Those dots were put there just to keep > > the compiler quiet when I needed the BSD style extended argument > > list. They don't break anything really, but for reasons of strict > > They break the possibility of compiling (all) applications with -mrtd on > i386's, and they break implementations where the equivalent of -mrtd or > some other complicated (efficient) arg passing convention is standard. How do you think one could compile a signal handler to assume there is the size of the argument list saved in the stack if the system does not use the same convention? Or how would one do the exact opposite thing using the simpler ret instruction when the size of the argument list has been saved in the stack? (The stack would be trashed and -fcaller-saves would certainly become a serious trouble.) If both the system and the signal handlers have been compiled to use the same calling convention the stack pointer will be modified correctly anyway independent of whether the calling method expects ret or rtd to be used. It is the fact that the system and the signal handler both use the same call/return method that counts, not whether the argument list is variable or not. The whole business is about the caller saving the correct size of the real parameter list in the stack when it is needed, not about the return from the called function becoming somehow different when the size of the argument list has been claimed variable in C. The prototype affects the caller. A system using rtd return convention would be expected to save the correct size of the argument list in the stack anyway. Right? BTW - As far as I know -mrtd has no meaning on iX86 machines. It is a valid option only for 680X0 family of processors. > The kernel shouldn't use the user macros because it would become slower > if the the user macros were fixed to actually meet their specification. Kernel could use it's own variations. The only thing that would be affected were that it were easier to change the real data type that is used represent sigset_t. Cheers, // jau ------ / Jukka A. Ukkonen, FUNET / Centre for Scientific Computing /__ M.Sc. (sw-eng & cs) Tel: (Home) +358-0-6215280 / Internet: ukkonen@csc.fi (Work) +358-0-4573208 v Internet: jau@funet.fi (Mobile) +358-400-606671 From owner-freebsd-hackers Mon Jul 1 04:44:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21434 for hackers-outgoing; Mon, 1 Jul 1996 04:44:15 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA21417 for ; Mon, 1 Jul 1996 04:44:12 -0700 (PDT) Message-Id: <199607011144.EAA21417@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA148541378; Mon, 1 Jul 1996 21:42:58 +1000 From: Darren Reed Subject: Re: rsync To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 1 Jul 1996 21:42:58 +1000 (EST) Cc: proff@suburbia.net, freebsd-hackers@FreeBSD.org In-Reply-To: <17184.836172801@time.cdrom.com> from "Jordan K. Hubbard" at Jun 30, 96 03:13:21 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Jordan K. Hubbard, sie said: > > > The below looks like a phenominally useful replacement for sup. According > > to the tech report, total uncompressed transfer between two kernel trees > > was around half the size of the *diffs*. It also streams data in both > > directions, effectively removing rtt as an important consideration. > > It does look cool. There's a package version in: [...] THe only un-cool thing is the GPL virus. From owner-freebsd-hackers Mon Jul 1 05:38:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA24516 for hackers-outgoing; Mon, 1 Jul 1996 05:38:38 -0700 (PDT) Received: from teil.soft.net (tata_elxsi.soft.net [164.164.10.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA24502 for ; Mon, 1 Jul 1996 05:37:56 -0700 (PDT) Received: by teil.soft.net (920330.SGI/920502.SGI.JF) for hackers@FreeBSD.ORG id AA14610; Mon, 1 Jul 96 18:07:09 -0800 From: rishim@teil.soft.net (Rishi Gautam) Message-Id: <9607020207.AA14610@teil.soft.net> Subject: Need info on Router Advt. To: hackers@FreeBSD.ORG Date: Mon, 1 Jul 1996 18:07:04 -0800 (PST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi I need information for the following things. If anybody has the information please help. 1. Does routed program of the FreeBSD version 2.1.0 supports the ICMP router advertisement protocol(RFC 1256). 2. If not, is there is any other program which supports that? 3. How it is possible to set the prefernce level for the router address, which are used in the advertisement messages. 4. incase freeBSD/any other BSD clone provides this router advertisement, how can i get the information from the kernel abt the list of router addresses and their preference levels? Thanks. Rishi From owner-freebsd-hackers Mon Jul 1 05:50:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA24972 for hackers-outgoing; Mon, 1 Jul 1996 05:50:48 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA24964 for ; Mon, 1 Jul 1996 05:50:42 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA00032; Mon, 1 Jul 1996 08:50:06 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 1 Jul 1996 08:50 EDT Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.12/8.6.5) with ESMTP id XAA01618; Sun, 30 Jun 1996 23:18:24 -0400 Received: (from rivers@localhost) by lakes (8.6.12/8.6.9) id XAA00249; Sun, 30 Jun 1996 23:21:20 -0400 Date: Sun, 30 Jun 1996 23:21:20 -0400 From: Thomas David Rivers Message-Id: <199607010321.XAA00249@lakes> To: freebsd-hackers@freefall.FreeBSD.org, hasty@rah.star-gate.com, lakes!rivers, smpatel@xi.dorm.umd.edu Subject: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2.1-RELEASE?) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I've chucked my Opti 8c929 card for a brand-new Sound Blaster PnP card.... I got tired of wrestling with it... I had previously grabbed Sujal's PnP stuff, and now have it "working" in a 2.1-RELEASE kernel. (I made several fixes, which I'm sure, by now, other people have reported... autoconf.c needs to #include "pnp.h" - and several changes to pnp.c - which I've attached below.) The problem is that something else isn't quite right yet. Here's the result of dmesg - (toward the top) - indicating the PNP code is at least doing something: FreeBSD 2.1.0-RELEASE #8: Sun Jun 30 23:06:05 EDT 1996 rivers@lakes.water.net:/usr/src/sys/compile/LAKES CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 12582912 (12288K bytes) avail memory = 10727424 (10476K bytes) Checking for Plug-n-Play devices... Board Vendor ID: CTL0028 Board Serial Number: 001c4a17 Configuring This Card Configuring This Card Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard Here's the result of dmesg - (toward the bottom) - indicating that the card was at least activated: sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvo0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: However, if I cat a .au file to /dev/audio0, all I get is a hung 'cat' command (indicating the IRQ or DRQ or port isn't right yet...) I've appended the result of running pnpinfo, and my version of pnp.c (to get the fixes.) If you look toward the top; you'll find my card's setup (the third one in the list.) The 4th element in the list is my attempt to try and set up the OPL-3 port... Note, this card contains an SoundBlaster Pro implementation, a MIDI port, a game port, an IDE port and OPL-3.... THanks for any help! - Dave Rivers - --------------------- cut here ---------------------------- The sound-related lines in my config (I also have a "controller pnp0" in there): # Controls all sound devices controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 conflicts The result of pnpinfo: Checking for Plug-n-Play devices... Board Vendor ID: CTL0028 Board Serial Number: 001c4a17 PnP Version: 1.0 Vendor Version: 16 Device Description: Creative SB16 PnP Logical Device ID: CTL0031 (31008c0e) Register Support 00 Device Description: Audio Start Dependent Function Good Configuration IRQ: 5 DMA: 0 1 DMA Stuff: 8 DMA: 5 DMA Stuff: 12 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x220 I/O alignment for minimum: 1 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x330 I/O Range maximum address: 0x330 I/O alignment for minimum: 1 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Acceptable Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA Stuff: 8 DMA: 5 6 7 DMA Stuff: 12 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Acceptable Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA Stuff: 8 DMA: 5 6 7 DMA Stuff: 12 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA Stuff: 8 DMA: 5 6 7 DMA Stuff: 12 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA Stuff: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA Stuff: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 11 DMA: 0 1 3 DMA Stuff: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 End Dependent Function Logical Device ID: CTL2011 (11208c0e) Register Support 00 Compatible Device ID: PNP0600 (0006d041) Device Description: IDE Start Dependent Function Good Configuration IRQ: 10 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x168 I/O Range maximum address: 0x168 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x36e I/O Range maximum address: 0x36e I/O alignment for minimum: 1 I/O length: 2 Start Dependent Function Acceptable Configuration IRQ: 11 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x1e8 I/O Range maximum address: 0x1e8 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x3ee I/O Range maximum address: 0x3ee I/O alignment for minimum: 1 I/O length: 2 Start Dependent Function Acceptable Configuration IRQ: 10 11 12 15 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x100 I/O Range maximum address: 0x1f8 I/O alignment for minimum: 8 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x3fe I/O alignment for minimum: 2 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 15 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x170 I/O Range maximum address: 0x170 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x376 I/O Range maximum address: 0x376 I/O alignment for minimum: 1 I/O length: 1 End Dependent Function Logical Device ID: PNPffff (ffffd041) Register Support 00 Device Description: Reserved Device decodes the full 16-bit ISA address I/O Range maximum address: 0x100 I/O Range maximum address: 0x3f8 I/O alignment for minimum: 8 I/O length: 1 Logical Device ID: CTL7001 (01708c0e) Register Support 00 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game Device decodes the full 16-bit ISA address I/O Range maximum address: 0x200 I/O Range maximum address: 0x200 I/O alignment for minimum: 1 I/O length: 8 End Tag My pnp.c: /* * Copyright (c) 1996, Sujal M. Patel * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by Sujal M. Patel * 4. Neither the name of the author nor the names of any co-contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $Id: pnp.c,v 1.5 1996/01/12 20:16:26 smpatel Exp smpatel $ */ #include #include #include #include #include "pnp.h" #define SEND(d, r) outb (ADDRESS, d); outb (WRITE_DATA, r); /* The READ_DATA port that we are using currently */ static int rd_port; /* * Hard coded for now -- Will need to use resource information from * ISA, PCI, and EISA drivers to auto-configure the PnP-devices */ static struct cinfo cinfo[] = { { 0x00008803, /* Serial Number */ -1, /* Logical Device Number */ { 15, -1 }, /* IRQ Number */ { -1, -1 }, /* DRQ Number */ { 0x3e8, /* Ports 1 */ -1, /* Ports 2 */ -1, /* Ports 3 */ -1, /* Ports 4 */ -1, /* Ports 5 */ -1, /* Ports 6 */ -1, /* Ports 7 */ } }, { 0xb1f5acc0, /* Serial Number */ -1, /* Logical Device Number */ { 11, -1 }, /* IRQ Number */ { -1, -1 }, /* DRQ Number */ { 0x340, /* Ports 1 */ -1, /* Ports 2 */ -1, /* Ports 3 */ -1, /* Ports 4 */ -1, /* Ports 5 */ -1, /* Ports 6 */ -1, /* Ports 7 */ } }, { 0x001c4a17, /* Serial Number */ 0, /* Logical Device Number */ { 5, -1 }, /* IRQ Number */ { 1, -1 }, /* DRQ Number */ { 0x220, /* Ports 1 */ -1, /* Ports 2 */ -1, /* Ports 3 */ -1, /* Ports 4 */ -1, /* Ports 5 */ -1, /* Ports 6 */ -1, /* Ports 7 */ } }, { 0x001c4a17, /* Serial Number */ 2, /* Logical Device Number */ { -1, -1 }, /* IRQ Number */ { -1, -1 }, /* DRQ Number */ { 0x388, /* Ports 1 */ -1, /* Ports 2 */ -1, /* Ports 3 */ -1, /* Ports 4 */ -1, /* Ports 5 */ -1, /* Ports 6 */ -1, /* Ports 7 */ } } }; int pow __P((int base, int exp)); void send_Initiation_LFSR __P((void)); int get_serial __P((unsigned char *data)); int get_resource_info __P((char *buffer, int len)); int handle_small_res __P((unsigned char *resinfo, int item, int len)); void handle_large_res __P((unsigned char *resinfo, int item, int len)); void config_device __P((unsigned char *data, int csn)); int isolation_protocol __P((void)); int pow(int base, int exp) { if (exp <= 1) return base; else return base * pow(base, exp - 1); } /* * Send Initiation LFSR as described in "Plug and Play ISA Specification, * Intel May 94." */ void send_Initiation_LFSR() { int cur, i; /* Reset the LSFR */ outb(ADDRESS, 0); outb(ADDRESS, 0); cur = 0x6a; outb(ADDRESS, cur); for (i = 1; i < 32; i++) { cur = (cur >> 1) | (((cur ^ (cur >> 1)) << 7) & 0xff); outb(ADDRESS, cur); } } /* * Get the device's serial number. Returns 1 if the serial is valid. */ int get_serial(data) unsigned char *data; { int i, bit, valid = 0, sum = 0x6a; bzero(data, sizeof(char) * 9); for (i = 0; i < 72; i++) { bit = inb((rd_port << 2) | 0x3) == 0x55; DELAY(250); /* Delay 250 usec */ /* Can't Short Circuit the next evaluation, so 'and' is last */ bit = (inb((rd_port << 2) | 0x3) == 0xaa) && bit; DELAY(250); /* Delay 250 usec */ valid = valid || bit; if (i < 64) sum = (sum >> 1) | (((sum ^ (sum >> 1) ^ bit) << 7) & 0xff); data[i / 8] = (data[i / 8] >> 1) | (bit ? 0x80 : 0); } valid = valid && (data[8] == sum); return valid; } /* * Dump all the information about configurations. */ void config_device(data, csn) unsigned char *data; int csn; { struct cinfo *ci; int i; #ifdef DEBUG printf("Card assigned CSN #%d\n", csn); #endif printf("Board Vendor ID: %c%c%c%02x%02x", ((data[0] & 0x7c) >> 2) + 64, (((data[0] & 0x03) << 3) | ((data[1] & 0xe0) >> 5)) + 64, (data[1] & 0x1f) + 64, data[2], data[3]); printf(" Board Serial Number: %08x\n", *(int *)&(data[4])); SEND(SET_CSN, csn); /* Move this out of this function XXX */ outb(ADDRESS, STATUS); for (ci = cinfo; (int)ci < ((int)cinfo + sizeof (cinfo)); ci++) { if (ci->serial == *(int *)&(data[4])) { printf ("Configuring This Card\n"); if (((int)ci->ldn) >= 0) SEND (SET_LDN, ci->ldn); for (i = 0; i < 8; i++) if (ci->port[i] > 0) { SEND (IO_CONFIG_BASE + i * 2, ci->port[i] >> 8); SEND (IO_CONFIG_BASE + i * 2 + 1, ci->port[i] & 0xff); } for (i = 0; i < 2; i++) if (ci->irq[i] > 0) { SEND (IRQ_CONFIG + i * 2, ci->irq[i]); } for (i = 0; i < 2; i++) if (ci->drq[i] > 0) { SEND (DRQ_CONFIG + i, ci->drq[i]); } SEND (IO_RANGE_CHECK, 0); SEND (ACTIVATE, 1); } } } /* * Run the isolation protocol. Use rd_port as the READ_DATA port value (caller * should try multiple READ_DATA locations before giving up). Upon exiting, * all cards are aware that they should use rd_port as the READ_DATA port; */ int isolation_protocol() { int csn; unsigned char data[9]; send_Initiation_LFSR(); /* Reset CSN for All Cards */ SEND(0x02, 0x04); for (csn = 1; (csn < MAX_CARDS); csn++) { /* Wake up cards without a CSN */ SEND(WAKE, 0); SEND(SET_RD_DATA, rd_port); outb(ADDRESS, SERIAL_ISOLATION); DELAY(1000); /* Delay 1 msec */ if (get_serial(data)) config_device(data, csn); else break; } return csn - 1; } void pnp_configure() { int num_pnp_devs; printf("Checking for Plug-n-Play devices...\n"); /* Try various READ_DATA ports from 0x203-0x3ff */ for (rd_port = 0x80; (rd_port < 0xff); rd_port += 0x10) { #ifdef DEBUG printf("Trying Read_Port at %x\n", (rd_port << 2) | 0x3); #endif num_pnp_devs = isolation_protocol(); if (num_pnp_devs) break; } if (!num_pnp_devs) { printf("No Plug-n-Play devices were found\n"); return; } } From owner-freebsd-hackers Mon Jul 1 05:57:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA25172 for hackers-outgoing; Mon, 1 Jul 1996 05:57:27 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA25162 for ; Mon, 1 Jul 1996 05:57:23 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id NAA26835; Mon, 1 Jul 1996 13:57:15 +0100 Date: Mon, 1 Jul 1996 13:57:14 +0100 (BST) From: Developer To: Joerg Wunsch cc: FreeBSD hackers Subject: Re: BSD V2.2 In-Reply-To: <199606290543.HAA27015@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Jun 1996, J Wunsch wrote: > As Developer wrote: > > > I tried it on a: AMD DX4x100Mzh, 16MB of memory. Award modular bios. > > Adaptec SCSI card (used the ahc driver) on VLB. 2x1GB SCSI drive. Enhanced > ^^^^^^^^ > > IO card (EIDE, 2 serial, 1 parallel, joystick etc). Green motherboard > ^^^^^^^ > > (Pretty standard really). Floppy drive. > > Does it perchance come with an own IDE BIOS? Disable it then, and try > again. (The WD Promise is for example a known offender.) I don't think so, but I can take a look... there are 2 bios's that I can configure, the Ami bios and the Adaptec bios. It did work fine on BSD 2.1, just 2.2 that doesn't work.. Strange. Thanks, Trefor S. From owner-freebsd-hackers Mon Jul 1 05:58:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA25221 for hackers-outgoing; Mon, 1 Jul 1996 05:58:17 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA25213 for ; Mon, 1 Jul 1996 05:58:15 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id FAA14862; Mon, 1 Jul 1996 05:59:17 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id WAA05320; Mon, 1 Jul 1996 22:57:37 +1000 From: Julian Assange Message-Id: <199607011257.WAA05320@suburbia.net> Subject: Re: rsync To: avalon@coombs.anu.edu.au (Darren Reed) Date: Mon, 1 Jul 1996 22:57:37 +1000 (EST) Cc: jkh@time.cdrom.com, proff@suburbia.net, freebsd-hackers@FreeBSD.org In-Reply-To: <199607011143.VAA00905@suburbia.net> from "Darren Reed" at Jul 1, 96 09:42:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > THe only un-cool thing is the GPL virus. I whole-heartedly support the GPL philosophy. Even though it has gone out of vouge. New information is built on and from existing information. The speed that information evolves in complexity and function is directly related how available it is. Retardation of information flows decreases the efficiency and efficacity of human knowledge. GPL does not forbid commercial use, providing source is made available. -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Mon Jul 1 06:09:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25808 for hackers-outgoing; Mon, 1 Jul 1996 06:09:23 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25803 for ; Mon, 1 Jul 1996 06:09:20 -0700 (PDT) Message-Id: <199607011309.GAA25803@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA168916544; Mon, 1 Jul 1996 23:09:04 +1000 From: Darren Reed Subject: Re: rsync To: proff@suburbia.net (Julian Assange) Date: Mon, 1 Jul 1996 23:09:03 +1000 (EST) Cc: jkh@time.cdrom.com, freebsd-hackers@FreeBSD.org In-Reply-To: <199607011257.WAA05320@suburbia.net> from "Julian Assange" at Jul 1, 96 10:57:37 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Julian Assange, sie said: > > > THe only un-cool thing is the GPL virus. > > I whole-heartedly support the GPL philosophy. Even though it has gone > out of vouge. New information is built on and from existing information. > The speed that information evolves in complexity and function is > directly related how available it is. Retardation of information flows > decreases the efficiency and efficacity of human knowledge. > > GPL does not forbid commercial use, providing source is made available. The GPL is crap. If you make any changes to that code, it is automatically GPL'd. It isn't the "commercial use" which I hate, but the restrictions the license puts on the code itself, those who want to use that code, etc. For example, Linux people can take *BSD software, port it to Linux, fix bugs, make enhancements and in the process, it is GPL'd, making it unsuitable for re-inclusion to the original BSD source, effectively penalising the *BSD groups because their license is too generous. I don't see how that helps information flows. From owner-freebsd-hackers Mon Jul 1 06:10:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25897 for hackers-outgoing; Mon, 1 Jul 1996 06:10:38 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25892 for ; Mon, 1 Jul 1996 06:10:36 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id GAA00190; Mon, 1 Jul 1996 06:10:25 -0700 (MST) From: Don Yuniskis Message-Id: <199607011310.GAA00190@seagull.rtd.com> Subject: Re: Are you a programmer? Do you wear glasses? To: dunn@harborcom.net Date: Mon, 1 Jul 1996 06:10:25 -0700 (MST) Cc: dgy@rtd.com, hackers@freebsd.org In-Reply-To: <199607010732.DAA01547@ns2.harborcom.net> from "Bradley Dunn" at Jul 1, 96 03:27:06 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > > mail it to this guy? Maybe 10K each day for the next year or so? > > :). AOL has like a 300K limit on mail messages. Probably because > people who use AOL tend to piss other people off. Actually, aren't the lists set up so that only subscribers can post to the lists? Or, is that considered too "unfriendly"? --don From owner-freebsd-hackers Mon Jul 1 06:18:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26334 for hackers-outgoing; Mon, 1 Jul 1996 06:18:06 -0700 (PDT) Received: from tav.kiev.ua (tav-sita.sita.kiev.ua [193.124.50.39]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26323 for ; Mon, 1 Jul 1996 06:17:56 -0700 (PDT) Received: (from root@localhost) by tav.kiev.ua (8.6.12/8.6.12) id QAA07851; Mon, 1 Jul 1996 16:07:49 +0300 Date: Mon, 1 Jul 1996 16:07:49 +0300 From: Oleg N Panashchenko Message-Id: <199607011307.QAA07851@tav.kiev.ua> To: abial@warman.org.pl (Andrzej Bialecki) Cc: hackers@freebsd.org Subject: Re: SLIP problems Organization: Maxis Labs X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article abial@warman.org.pl (Andrzej Bialecki) wrote: : I configured remote station properly (it ran with Trumpets). : Then I did slattach -h -l -s 9600 /dev/cuaa1 (COM2). After about 2 : minutes I was able to ping the remote side (traceroute was also OK). : Then I left ping running on one tty, and went to another in order to : make telnet. And here something strange happened - ping got killed, i.e. : no longer received echoes from remote side. The telnet didn't get through : as well. The line seemed dead. In addition to routed related advice I can add the following: Use -l slattach switch only if your modem reports that carrier is always on. Use "-r redial.script" if your modem DCD line state corresponds the state of data carrier. If you don't need to redial, just wait for carrier in redial.script Oleg From owner-freebsd-hackers Mon Jul 1 06:19:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26404 for hackers-outgoing; Mon, 1 Jul 1996 06:19:49 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26354 for ; Mon, 1 Jul 1996 06:18:20 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA27282; Mon, 1 Jul 1996 23:15:25 +1000 Date: Mon, 1 Jul 1996 23:15:25 +1000 From: Bruce Evans Message-Id: <199607011315.XAA27282@godzilla.zeta.org.au> To: bde@zeta.org.au, jau@aphrodite.funet.fi Subject: Re: POSIX.4 signals + other POSIX.4 stuff to FreeBSD... Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> > void (*sa_handler) _P((int, ...)); >> >> > then some" implementation. Those dots were put there just to keep >> > the compiler quiet when I needed the BSD style extended argument >> > list. They don't break anything really, but for reasons of strict >> >> They break the possibility of compiling (all) applications with -mrtd on >> i386's, and they break implementations where the equivalent of -mrtd or >> some other complicated (efficient) arg passing convention is standard. > How do you think one could compile a signal handler to assume > there is the size of the argument list saved in the stack if the > system does not use the same convention? The kernel has to know the convention(s) used by applications. Nonstandard ones could be specified using special sigaction flags. I just tried -mrtd (for the i386 gcc-2.6.3). It seems to imply -mregparm, and -mno-regparm doesn't affect this. > If both the system and the signal handlers have been compiled to > use the same calling convention the stack pointer will be modified > correctly anyway independent of whether the calling method expects > ret or rtd to be used. Except possibly with your union :-). It gives multiple conventions that are different in practice if -mrtd or maybe -mregparm is used, and FreeBSD only supports one convention. > A system using rtd return convention would be expected to save the > correct size of the argument list in the stack anyway. Right? No, it would be expected to be fully prototyped so that the callee always knows the number of args for non-varargs functions and the caller and the callee agree which functions are varargs so that only the caller cleans up the args for varargs functions. Passing the size of the args would usually be larger and slower than cleaning up the args in the caller in all cases. This is one reason why sa_handler shouldn't be varargs. The kernel must pass exactly the right number of args so that cleaning up the args in the callee can work. > BTW - As far as I know -mrtd has no meaning on iX86 machines. It is > a valid option only for 680X0 family of processors. It has always sort of worked for i386's and seems to be fully supported in gcc-2.7.2 because it is a standard Windows NT convention. 2.7.2 also has new attributes "stdcall" which gives per-function callee-pop, "regparm" which gives per-function args in registers, and "cdecl" which cancels any -mregparm -mrtd to give the "normal" (slow) C calling convention. Bruce From owner-freebsd-hackers Mon Jul 1 06:27:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26821 for hackers-outgoing; Mon, 1 Jul 1996 06:27:15 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26810 for ; Mon, 1 Jul 1996 06:27:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id GAA05292; Mon, 1 Jul 1996 06:25:18 -0700 (PDT) Message-Id: <199607011325.GAA05292@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Julian Assange cc: avalon@coombs.anu.edu.au (Darren Reed), jkh@time.cdrom.com, freebsd-hackers@FreeBSD.org Subject: Re: rsync In-reply-to: Your message of "Mon, 01 Jul 1996 22:57:37 +1000." <199607011257.WAA05320@suburbia.net> From: David Greenman Reply-To: davidg@root.com Date: Mon, 01 Jul 1996 06:25:15 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> THe only un-cool thing is the GPL virus. > >I whole-heartedly support the GPL philosophy. Even though it has gone >out of vouge. New information is built on and from existing information. >The speed that information evolves in complexity and function is >directly related how available it is. Retardation of information flows >decreases the efficiency and efficacity of human knowledge. > >GPL does not forbid commercial use, providing source is made available. Uh-oh. I can see where this is going. Please, folks, freebsd-hackers is not an appropriate mailing list to be discussing the GPL philosophy. Let me try to nip this one in the bud, as it were, right away. If you wish to discuss this in a public forum, please take it to Usenet in some gnu newsgroup. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 1 06:44:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27668 for hackers-outgoing; Mon, 1 Jul 1996 06:44:25 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA27658 for ; Mon, 1 Jul 1996 06:44:20 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA15128; Mon, 1 Jul 1996 08:43:31 -0500 From: Joe Greco Message-Id: <199607011343.IAA15128@brasil.moneng.mei.com> Subject: Re: Need info on Router Advt. To: rishim@teil.soft.net (Rishi Gautam) Date: Mon, 1 Jul 1996 08:43:31 -0500 (CDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <9607020207.AA14610@teil.soft.net> from "Rishi Gautam" at Jul 1, 96 06:07:04 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi > I need information for the following things. If anybody has the information > please help. > > 1. Does routed program of the FreeBSD version 2.1.0 supports the ICMP router > advertisement protocol(RFC 1256). I do not believe so. > 2. If not, is there is any other program which supports that? I believe gated does. More than this, I do not know. ... JG From owner-freebsd-hackers Mon Jul 1 06:44:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27686 for hackers-outgoing; Mon, 1 Jul 1996 06:44:29 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA27675 for ; Mon, 1 Jul 1996 06:44:27 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA15109; Mon, 1 Jul 1996 08:39:55 -0500 From: Joe Greco Message-Id: <199607011339.IAA15109@brasil.moneng.mei.com> Subject: Re: no subject (file transmission) To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 1 Jul 1996 08:39:54 -0500 (CDT) Cc: jkh@time.cdrom.com, pechter@shell.monmouth.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199606271804.UAA02454@uriah.heep.sax.de> from "J Wunsch" at Jun 27, 96 08:04:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Jordan K. Hubbard wrote: > > > > 2. Declare the BSD method (the REAL original crontab) the winner. > > > > I think this is probably our best bet. > > Objection. I voted against /etc/crontab back in the old days, and i'm > still against it (and always kill it as soon as i've installed a > system). I tend to see it as a mistake too... new sysadmins do a "crontab -e" as root and get.. nothing. :-( I see a benefit to having a method that allows the sysadmin to specify cron entries for users that (1) the user cannot change and (2) are centrally administered. > There's only a few things where i'm stating SysV to have the better > approach, but per-user crontabs certainly belong into this category. > > Remember, the original BSD crontab was even more braindead in that it > didn't allow crontab entries for users other than root, and the > current /etc/crontab would make a mess for crontab(1) to allow for > per-user cron commands, while the existing approach with one file per > user is there && has proven to work. On the opposite, i don't see > anything /etc/crontab would gain us that /var/cron/tabs/ doesn't > already give us as well. (Not counting nostalgic feelings. :) Cron entries "forced" upon a user. > Despite of this, i consider a world-readable /etc/crontab a BIG > security hole. Read "The Cuckoo's egg" for why intruders do like to > know when exactly system maintenance jobs are about to run... Yes, /etc/crontab and /var/cron/log* need to be protected.. :-) even so one can often dig appropriate hints out of /var/log/maillog... I would be happier with /etc/crontab if the crontab command at least noted that there were entries for this user in /etc/crontab (perhaps adding them as comments). That has its own problems. I would be happiest if we left /etc/crontab for the experienced admins but put the current contents in /var/cron/tabs/root... that also happens to be the least intrusive option, and also more secure since /etc/crontabs is readable.. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-hackers Mon Jul 1 07:12:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29020 for hackers-outgoing; Mon, 1 Jul 1996 07:12:53 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA29015 for ; Mon, 1 Jul 1996 07:12:48 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA15200; Mon, 1 Jul 1996 09:11:42 -0500 From: Joe Greco Message-Id: <199607011411.JAA15200@brasil.moneng.mei.com> Subject: Re: Are you a programmer? Do you wear glasses? To: dgy@rtd.com (Don Yuniskis) Date: Mon, 1 Jul 1996 09:11:41 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199607011310.GAA00190@seagull.rtd.com> from "Don Yuniskis" at Jul 1, 96 06:10:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > > > mail it to this guy? Maybe 10K each day for the next year or so? > > > > :). AOL has like a 300K limit on mail messages. Probably because > > people who use AOL tend to piss other people off. > > Actually, aren't the lists set up so that only subscribers can post > to the lists? Or, is that considered too "unfriendly"? That would be bad to do, people are often referred here when they encounter strange problems. It might make sense to hold their messages in an "approval queue" if they are not a list member. ... JG From owner-freebsd-hackers Mon Jul 1 07:29:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00255 for hackers-outgoing; Mon, 1 Jul 1996 07:29:27 -0700 (PDT) Received: from www.cas.unt.edu (www.cas.unt.edu [129.120.3.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00249; Mon, 1 Jul 1996 07:29:23 -0700 (PDT) Received: (from cofer@localhost) by www.cas.unt.edu (8.7.5/8.6.9) id JAA12421; Mon, 1 Jul 1996 09:29:00 -0500 (CDT) Date: Mon, 1 Jul 1996 09:29:00 -0500 (CDT) From: "Christopher D. Cofer" To: freebsd-hardware@FreeBSD.org cc: freebsd-hackers@FreeBSD.org Subject: Installing Stable on 386/33 No Boot Prompt. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I am trying to install stable on a 386/33 with 20 Meg. I have correctly downloaded and checked on another machine the boot.flp. After the machine goes through POST it hangs. The floppy is operational with other OS boot disks. Has anyone seen this before? : The MB has CHIPS chipset : EIDE bios controller by SIIG : Trident ISA VGA : DigiBoard PC/16e : 3com Etherlink III 3c509 The only thing that I was not able to find in the FAQ and posts is the controller. Is it supported? Would it cause my machine to hang? I wanted to use this machine to do routing between pppd and the network. I only need to route one ppp connection, so I am not worried about speed. The digiboard is important for other serial devices. The machine is currently running linux slakware 3.0 with kernel 2.0. This is not working very well because of the driver for the digiboard. I understand that the driver FreeBSD is better, therefore I am trying to install it. If the setup performs well, then I will upgrade the system to a faster machine. Any comments or suggestions would be helpful. Thanks in advance... ********************************************************** * Christopher Don Cofer College of Arts * * cofer@unt.edu and Science * * Computer Support Services * ********************************************************** From owner-freebsd-hackers Mon Jul 1 07:32:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00526 for hackers-outgoing; Mon, 1 Jul 1996 07:32:38 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00516 for ; Mon, 1 Jul 1996 07:32:28 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id HAA06436; Mon, 1 Jul 1996 07:31:06 -0700 (MST) From: Don Yuniskis Message-Id: <199607011431.HAA06436@seagull.rtd.com> Subject: Re: Are you a programmer? Do you wear glasses? To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 1 Jul 1996 07:31:06 -0700 (MST) Cc: dgy@rtd.com, hackers@freebsd.org In-Reply-To: <199607011411.JAA15200@brasil.moneng.mei.com> from "Joe Greco" at Jul 1, 96 09:11:41 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Actually, aren't the lists set up so that only subscribers can post > > to the lists? Or, is that considered too "unfriendly"? > > That would be bad to do, people are often referred here when they encounter > strange problems. > > It might make sense to hold their messages in an "approval queue" if they > are not a list member. Ahhh.... point well taken! --don From owner-freebsd-hackers Mon Jul 1 07:52:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02002 for hackers-outgoing; Mon, 1 Jul 1996 07:52:40 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA01990 for ; Mon, 1 Jul 1996 07:52:27 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.6.11/8.6.9) id QAA05171; Mon, 1 Jul 1996 16:54:44 GMT Date: Mon, 1 Jul 1996 16:54:43 +0000 () From: Andrzej Bialecki To: Oleg N Panashchenko cc: hackers@freebsd.org Subject: Re: SLIP problems In-Reply-To: <199607011307.QAA07851@tav.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Jul 1996, Oleg N Panashchenko wrote: > : Then I did slattach -h -l -s 9600 /dev/cuaa1 (COM2). After about 2 > Use -l slattach switch only if your modem reports that carrier is always on. I forgot to add that this was a cable link - no modem. Maybe this was unclear - the whole setup was as follows: +--------+ +----------+ |FreeBSD/| RS232 without DTR |A station | |Win 3.11|=====================| | +--------+ DB25 DB25 +----------+ So I think that as long as I have both ends electrically connected the DCD is always on. In fact, I checked this with a small device that shows level of every line of RS232 (two connectors with set of LEDs). Anyway, thanks for these suggestions. Andy +------------------------------------------------------------------------+ | ANDRZEJ BIALECKI, , NASK (WARMAN) | | Research and Academic Network in Poland, Warsaw Area Network | | phone: (+48 22) 414115, Bartycka 18, 00-716 Warsaw, Poland | +------------------------------------------------------------------------+ -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2i mQCNAzFydDYAAAEEALAheWaKO7Uny4bAmT6AC2tEAPK+9VSUxX5ynA3f3yTQtXwL xovpwTQNCbqjBle8sME1hTIqgTkCHmucpucejc1z5zevdVPX4mOCeDcKOyeRf5VA XjI8YaPan/SiAfw5+GtXeiEbdf5N78Xd0old/vPKXwKebHCv7nhAoCU+bhJVAAUR tCZBbmRyemVqIEJpYWxlY2tpIDxhYmlhbEB3YXJtYW4ub3JnLnBsPg== =xasZ -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hackers Mon Jul 1 08:53:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05689 for hackers-outgoing; Mon, 1 Jul 1996 08:53:09 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05682 for ; Mon, 1 Jul 1996 08:53:02 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.6.12) with SMTP id JAA01385; Mon, 1 Jul 1996 09:01:48 -0700 (PDT) Date: Mon, 1 Jul 1996 09:01:47 -0700 (PDT) From: Tom Samplonius To: Rishi Gautam cc: hackers@FreeBSD.ORG Subject: Re: Need info on Router Advt. In-Reply-To: <9607020207.AA14610@teil.soft.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Jul 1996, Rishi Gautam wrote: > Hi > I need information for the following things. If anybody has the information > please help. > > 1. Does routed program of the FreeBSD version 2.1.0 supports the ICMP router > advertisement protocol(RFC 1256). > > 2. If not, is there is any other program which supports that? rdisc does. > 3. How it is possible to set the prefernce level for the router address, which > are used in the advertisement messages. > > 4. incase freeBSD/any other BSD clone provides this router advertisement, how > can i get the information from the kernel abt the list of router addresses and > their preference levels? No idea. "man rdisc" > Thanks. > > Rishi > > > Tom From owner-freebsd-hackers Mon Jul 1 09:14:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07079 for hackers-outgoing; Mon, 1 Jul 1996 09:14:01 -0700 (PDT) Received: from mongoose.bostic.com (bostic@mongoose.BSDI.COM [205.230.230.129]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA07070 for ; Mon, 1 Jul 1996 09:13:54 -0700 (PDT) Received: (from bostic@localhost) by mongoose.bostic.com (8.7.4/8.7.3) id LAA15656; Mon, 1 Jul 1996 11:09:48 -0400 (EDT) Date: Mon, 1 Jul 1996 11:09:48 -0400 (EDT) From: Keith Bostic Message-Id: <199607011509.LAA15656@mongoose.bostic.com> To: bostic@cs.berkeley.edu Subject: Version 1.71 of nex/nvi. Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Version 1.71 of nex/nvi is now available. The changes in nvi 1.71 are almost entirely bug and compatibility fixes. There are two changes that may be of interest: + The read command now supports named pipes. + The Fg command has been implemented, so you can foreground a backgrounded screen by splitting the current screen. Also, you can name background screens by using the last filename component, e.g., ":Fg passwd" will foreground a backgrounded /etc/passwd edit buffer into a split screen. If you're interested in a further review of the changes that have been made, a complete change log is included with the distribution, in the file docs/changelog. Version 1.71 is available for anonymous ftp from the usual two sites. (Please note the name change from the previous ALPHA designation!) ftp.cs.berkeley.edu:ucb/4bsd/nvi-1.71.tar.gz ftp.bostic.com:pub/nvi-1.71.tar.gz (The UC Berkeley site is likely to provide faster transfer speeds.) Please let me know if you have any problems, and thanks for using nvi! --keith From owner-freebsd-hackers Mon Jul 1 09:36:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08722 for hackers-outgoing; Mon, 1 Jul 1996 09:36:04 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08702; Mon, 1 Jul 1996 09:36:01 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607011636.JAA08702@freefall.freebsd.org> Subject: Re: Are you a programmer? Do you wear glasses? To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 1 Jul 1996 09:36:00 -0700 (PDT) Cc: dgy@rtd.com, hackers@freebsd.org In-Reply-To: <199607011411.JAA15200@brasil.moneng.mei.com> from "Joe Greco" at Jul 1, 96 09:11:41 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joe Greco wrote: > > > > > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > > > > mail it to this guy? Maybe 10K each day for the next year or so? > > > > > > :). AOL has like a 300K limit on mail messages. Probably because > > > people who use AOL tend to piss other people off. > > > > Actually, aren't the lists set up so that only subscribers can post > > to the lists? Or, is that considered too "unfriendly"? > > That would be bad to do, people are often referred here when they encounter > strange problems. > > It might make sense to hold their messages in an "approval queue" if they > are not a list member. we had had vbery few incidents of this type. i get to the approval queue every day or two. because of that dealy, a new user might get left out in the cold for 48 hours. better to live with a spam or two every onnce in a while than to lose people because we are too distant. in spite of how much i hate spam....sigh jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. 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 From owner-freebsd-hackers Mon Jul 1 09:45:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09175 for hackers-outgoing; Mon, 1 Jul 1996 09:45:08 -0700 (PDT) Received: from Apollo.dmacc.cc.ia.us (apollo.dmacc.cc.ia.us [161.210.216.100]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA09160 for ; Mon, 1 Jul 1996 09:45:01 -0700 (PDT) Received: from vis-admin.dmacc.cc.ia.us (vis-admin.dmacc.cc.ia.us [161.210.217.130]) by Apollo.dmacc.cc.ia.us (8.6.9/8.6.9) with ESMTP id LAA06290 for <@apollo.dmacc.cc.ia.us:hackers@freebsd.org>; Mon, 1 Jul 1996 11:44:58 -0500 Received: by vis-admin.dmacc.cc.ia.us (940816.SGI.8.6.9/940406.SGI) for hackers@freebsd.org id LAA05641; Mon, 1 Jul 1996 11:44:54 -0500 From: "Charles F. Randall" Message-Id: <9607011144.ZM5639@vis-admin.dmacc.cc.ia.us> Date: Mon, 1 Jul 1996 11:44:54 -0500 X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail) To: hackers@freebsd.org Subject: 2.1-960627-SNAP install quirks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the express install, I noticed the following quirks: 1) NFS install using de0 device wouldn't work (hung in nslookup or NFS mount) unless I disabled other devices (not sure which, I just removed everything I didn't have) 2) Screen saver "Snake" didn't ask for timeout value and timeout option wasn't selectable. In post-install examination of /etc/sysconfig, saver="snake" was set, but "blanktime=NO" was also (net effect, no screen saver). 3) Ntpdate setting of "Other" doesn't stick (isn't shown on screen as selected) and isn't written to /etc/sysconfig 4) NFS install that misses a set of files (proflib, for example) doesn't give you a second chance (I think it used to). The old behavior was nice, because you could go fetch the files on the NFS server and then try again on the client and it would work. Keep up the good work, -Randy -- Charles F. Randall E-mail: crandall@dmacc.cc.ia.us UNIX Systems Programmer Voice: (515) 965-7057 Perl Hacker - Powered by FreeBSD! FAX: (515) 965-7305 From owner-freebsd-hackers Mon Jul 1 10:59:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17239 for hackers-outgoing; Mon, 1 Jul 1996 10:59:14 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA17055; Mon, 1 Jul 1996 10:58:05 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.12/1.53) id TAA07646; Mon, 1 Jul 1996 19:57:53 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199607011757.TAA07646@gvr.win.tue.nl> Subject: Re: Increasing openinfo.cachesize in pwd_mkdb (was Re: Incremental [s]pwd.db updates?) To: taob@io.org Date: Mon, 1 Jul 1996 19:57:52 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: from Brian Tao at "Jun 23, 96 10:23:31 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The diffs to support the -c switch are quite simple, if anyone is > interested in them (maybe even committing them?). I think it would be > a perfect compliment to gvr's enhancements to passwd/chpass/chfn/chsh. > I still need to edit the man page and patch vipw to pass a cachesize > parameter to pwd_mkdb. Wait a few days..I'll commit my diffs to -current then. -Guido From owner-freebsd-hackers Mon Jul 1 11:09:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18548 for hackers-outgoing; Mon, 1 Jul 1996 11:09:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA18511; Mon, 1 Jul 1996 11:08:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06008; Mon, 1 Jul 1996 11:07:07 -0700 From: Terry Lambert Message-Id: <199607011807.LAA06008@phaeton.artisoft.com> Subject: Re: I need help on this one - please help me track this guy down! To: taob@io.org (Brian Tao) Date: Mon, 1 Jul 1996 11:07:07 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG, security@FreeBSD.ORG In-Reply-To: from "Brian Tao" at Jun 30, 96 12:43:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 23 Jun 1996, Terry Lambert wrote: > > > > 9) Make sure you aren't running routed -q. > > Why not? The University of Utah was attacked by a guy in the Mac lab claiming to be the default gateway. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 1 11:09:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18577 for hackers-outgoing; Mon, 1 Jul 1996 11:09:10 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA18529 for ; Mon, 1 Jul 1996 11:09:00 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.12/1.53) id UAA07690; Mon, 1 Jul 1996 20:06:55 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199607011806.UAA07690@gvr.win.tue.nl> Subject: Re: Multiple delivery of UDP and IP aliases To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 1 Jul 1996 20:06:55 +0200 (MET DST) Cc: jcl@pavilion.co.uk, hackers@FreeBSD.org In-Reply-To: <199606251544.KAA07793@brasil.moneng.mei.com> from Joe Greco at "Jun 25, 96 10:44:53 am" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It's a Legitimate Bug in 2.1R and 2.0.5R (at least), and somebody devised > a patch. Check the -hackers list, and if you cannot locate the patch, > write to me and I will dredge it up. > > My apologies to whoever fixed it, I can't remember anymore :-( I made a fix. However, I believ this was fixed in 2.1R. In 2.1, an alias has an associated netmask of all-ones. In the udp code, a packet to an address is always checked to be a broadcast address using in_broadcast(). For an all-one netmask, this succeeds where it should not. I `fixed' this by adding a check for the all-one netmask in in_broadcast(). This is fixed in 2.1. The following patch should fix it on 2.05: -Guido --- in.c.orig Mon Jan 8 21:38:45 1996 +++ in.c Mon Jan 8 21:40:39 1996 @@ -609,7 +609,13 @@ /* * Check for old-style (host 0) broadcast. */ - t == ia->ia_subnet || t == ia->ia_net)) + t == ia->ia_subnet || t == ia->ia_net) && + /* + * Check for an all one subnetmask. These + * only exist when an interface gets a secondary + * address. + */ + ia->ia_subnetmask != (u_long)0xffffffff) return 1; return (0); #undef ia From owner-freebsd-hackers Mon Jul 1 11:14:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19476 for hackers-outgoing; Mon, 1 Jul 1996 11:14:31 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19460 for ; Mon, 1 Jul 1996 11:14:26 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA15675; Mon, 1 Jul 1996 13:13:07 -0500 From: Joe Greco Message-Id: <199607011813.NAA15675@brasil.moneng.mei.com> Subject: Re: Multiple delivery of UDP and IP aliases To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Mon, 1 Jul 1996 13:13:07 -0500 (CDT) Cc: jcl@pavilion.co.uk, hackers@FreeBSD.org In-Reply-To: <199607011806.UAA07690@gvr.win.tue.nl> from "Guido van Rooij" at Jul 1, 96 08:06:55 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I made a fix. However, I believ this was fixed in 2.1R. I don't believe it was, because when I first mentioned it, it was because I had upgraded one of my key machines from 2.0R to 2.1R... I do have this applied as a patch to the machine in question, and the machine is running 2.1.0-RELEASE, and it no longer exhibits this behaviour.. > In 2.1, an alias has an associated netmask of all-ones. > In the udp code, a packet to an address is always checked to > be a broadcast address using in_broadcast(). For an all-one > netmask, this succeeds where it should not. > I `fixed' this by adding a check for the all-one netmask in > in_broadcast(). This is fixed in 2.1. > The following patch should fix it on 2.05: The patch does work but I swear you need it for 2.1R as well ;-) ... JG From owner-freebsd-hackers Mon Jul 1 11:40:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22816 for hackers-outgoing; Mon, 1 Jul 1996 11:40:38 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA22801 for ; Mon, 1 Jul 1996 11:40:32 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.12/1.53) id UAA07764; Mon, 1 Jul 1996 20:38:55 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199607011838.UAA07764@gvr.win.tue.nl> Subject: Re: Multiple delivery of UDP and IP aliases To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 1 Jul 1996 20:38:55 +0200 (MET DST) Cc: jcl@pavilion.co.uk, hackers@FreeBSD.org In-Reply-To: <199607011813.NAA15675@brasil.moneng.mei.com> from Joe Greco at "Jul 1, 96 01:13:07 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > The patch does work but I swear you need it for 2.1R as well ;-) Indeed...I made a mistake. It is fixed in -stable and current. (I just checked). -Guido From owner-freebsd-hackers Mon Jul 1 11:50:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23513 for hackers-outgoing; Mon, 1 Jul 1996 11:50:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA23500 for ; Mon, 1 Jul 1996 11:49:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06135; Mon, 1 Jul 1996 11:46:30 -0700 From: Terry Lambert Message-Id: <199607011846.LAA06135@phaeton.artisoft.com> Subject: Re: Are you a programmer? Do you wear glasses? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Mon, 1 Jul 1996 11:46:30 -0700 (MST) Cc: jgreco@brasil.moneng.mei.com, dgy@rtd.com, hackers@FreeBSD.ORG In-Reply-To: <199607011636.JAA08702@freefall.freebsd.org> from "Jonathan M. Bresler" at Jul 1, 96 09:36:00 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > we had had vbery few incidents of this type. i get to the approval > queue every day or two. because of that dealy, a new user might > get left out in the cold for 48 hours. > > better to live with a spam or two every onnce in a while than > to lose people because we are too distant. in spite of how > much i hate spam....sigh How about a "companies who have spammed our lists" area on the WWW page so we can know who not to buy from? 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 1 12:18:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25773 for hackers-outgoing; Mon, 1 Jul 1996 12:18:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA25618 for ; Mon, 1 Jul 1996 12:17:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA06184; Mon, 1 Jul 1996 12:13:47 -0700 From: Terry Lambert Message-Id: <199607011913.MAA06184@phaeton.artisoft.com> Subject: Re: POSIX.4 signals + other POSIX.4 stuff to FreeBSD... To: jau@jau.csc.fi (Jukka Ukkonen) Date: Mon, 1 Jul 1996 12:13:47 -0700 (MST) Cc: terry@lambert.org, bde@zeta.org.au, hackers@freebsd.com In-Reply-To: <199606281632.TAA22857@jau.csc.fi> from "Jukka Ukkonen" at Jun 28, 96 07:32:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Use the extended structure size only in the extension interfaces, and > > assume defaults for the non-extension interfaces (you will have to > > do this as part of the ABI mapping in any case). I did something > > similar to this for the fcntl() calls for NFS server locking, which > > requires system and process ID's for the proxy. > > Eh? As I already said, the new and the old call interface would > have to co-exist for some time, so that the old programs using > the old interface would not break. (This might prove out to be > a slippery road to take, but maybe it would be possible. I don't > know about the shared libraries though.) Sorry for the delay... If it can be implemented without affecting binary compatability, then it should be permitted. If it must affect binary compatability, then I'm against it, and would prefer assigning another call ID to the new method, and force both to gate into the same code so the maintenance on the old call can't be orphaned by neglect. > There are only three completely new system calls or functions > defined by POSIX.4 for the signals. > > extern int sigqueue __P((pid_t, int, const union sigval)); > extern int sigwaitinfo __P((const sigset_t *, siginfo_t *)); > extern int sigtimedwait __P((const sigset_t *, siginfo_t *, > const struct timespec *)); I prefer multiplex calls through a single call for this type of thing: one call per subsystem interface to make it easier to replace. > Though Bruce Evans seems not to share my opinion, I suppose > using sigismember() etc. macros/functions within the kernel > would not be very much a resource hog, or what do you think > of the next macro? > > #define sigismember(set, sig) (set[((unsigned) (sig)) >> 5] \ > & (1 << ((sig) & 0x1F))) > > This does not really require too many extra machine instructions > when used instead of the simple bitwise and/or logic. This already > accounts for the ability to handle an extended signal set. I have to agree with Bruce: yhe POSIX interfaces are there for the applications, not the kernel. It should be permissable to optimize the hell out of the kernel, to the exclusion of POSIX macros from kernel code to make it more efficient, as necessary. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 1 12:31:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26976 for hackers-outgoing; Mon, 1 Jul 1996 12:31:30 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26965 for ; Mon, 1 Jul 1996 12:31:28 -0700 (PDT) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.7.5/8.7.3) id MAA29958 for freebsd-hackers@freefall.cdrom.com; Mon, 1 Jul 1996 12:31:44 -0700 (PDT) From: "Steven G. Kargl" Message-Id: <199607011931.MAA29958@troutmask.apl.washington.edu> Subject: sup server mirror out-of-sync To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD Hackers) Date: Mon, 1 Jul 1996 12:31:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hackers, I have happily used sup to maintain my local -stable source directory. However, lately I've notice that the sup server mirrors sup2, sup3, and sup5 appear to be either out-of-date or flawed in some way. For example, (wrapped to fit) src-secure release=stable host=sup3.FreeBSD.org hostbase=/home base=/usr \ prefix=/usr/src delete old use-rel-suffix should retrieve the src-secure distribution. However, it seems to get src-sys from sup3. On sup5, the following works src-base release=stable host=sup5.FreeBSD.org hostbase=/home base=/usr \ prefix=/usr/src delete old use-rel-suffix unfortunately this causes the creation of TODO-2.1/ with the accompanying out-of-date TODO files for several core team members (and contributors?). This was deleted long, long ago. The only recourse that one has is to sup from sup.freebsd.org. This is not a good thing from the stand point of the load on freefall. Yes, I know about CTM. Yes, I know that 2.1.5 has a BETA SNAP out, and -stable might be meeting a timely death (although Paul Richards(?) has volunteered to maintain a bugfix only branch for 2.1.5). Is it too much trouble to ask the maintainers of the sup server mirrors to check their distributions? -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html From owner-freebsd-hackers Mon Jul 1 12:59:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01880 for hackers-outgoing; Mon, 1 Jul 1996 12:59:43 -0700 (PDT) Received: from rocky.mt.sri.com ([206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01855 for ; Mon, 1 Jul 1996 12:59:39 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA11089; Mon, 1 Jul 1996 13:59:32 -0600 (MDT) Date: Mon, 1 Jul 1996 13:59:32 -0600 (MDT) Message-Id: <199607011959.NAA11089@rocky.mt.sri.com> From: Nate Williams To: "Steven G. Kargl" Cc: freebsd-hackers@freefall.freebsd.org (FreeBSD Hackers) Subject: Re: sup server mirror out-of-sync In-Reply-To: <199607011931.MAA29958@troutmask.apl.washington.edu> References: <199607011931.MAA29958@troutmask.apl.washington.edu> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On sup5, the following works > > src-base release=stable host=sup5.FreeBSD.org hostbase=/home base=/usr \ > prefix=/usr/src delete old use-rel-suffix > > unfortunately this causes the creation of TODO-2.1/ with the accompanying > out-of-date TODO files for several core team members (and contributors?). > This was deleted long, long ago. Actually, you probably get this from sup.freebsd.org, and it's a 'bug' in the sup-server mirror software. At least I get it and I sup directly from freefall. Nate From owner-freebsd-hackers Mon Jul 1 13:12:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04103 for hackers-outgoing; Mon, 1 Jul 1996 13:12:12 -0700 (PDT) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04074 for ; Mon, 1 Jul 1996 13:12:08 -0700 (PDT) Received: from schubert.promo.de by casparc.ppp.net with smtp (Smail3.1.28.1 #1) id m0uapK3-000I0NC; Mon, 1 Jul 96 22:11 MET DST Received: from quick.promo.de (quick.Promo.DE [194.45.188.67]) by schubert.promo.de (8.6.12/8.6.12) with SMTP id AAA00348 for ; Tue, 2 Jul 1996 00:12:33 +0200 Message-ID: Date: 1 Jul 1996 22:10:41 +0200 From: "Stefan Bethke" Subject: TCP time-outs on PPP line To: "FreeBSD Hackers" X-Mailer: Mail*Link SMTP-QM 3.0.2 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; Name="Message Body" Content-Transfer-Encoding: quoted-printable Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, we are connected through an analog leased line with two USR Courier, = using 2.1.0R and pppd. Since upgrading from Linux we experience some TCP "connection timed out" = failures. It seems that at those moments someone is downloading from our = HTTP or FTP server (looking at the modem leds and = ftpwho/xferlog/http-log). Trying to ping the terminal server of our ISP doesn't give a response; = after 5 or so pings, ping says "No buffer space available". My understanding is that the already established TCP connection quickly = fills the output buffer and saturates the line; at this point, a packet = inserted into the queue will be sent after (worst case) mtu / bandwith * = queue length (ifq_maxlen) =3D 1500 / 2880 * 50 =3D 27 seconds. (Or, = taking fastq into account, 54 secs). What's the solution? Possibilities are - reduce ifq_maxlen, so ENOBUF will be returned earlier, so TCP will (hopefully) send slower earlier; - reduce the mtu, so a full queue run will be faster, thereby allowing a = new packet to be sent faster; - devise a mechanism to promote those connections we want to precede our external users' connections to the fastq; possibly by promoting all packets smaller than xxx bytes to fastq; - upgrade to a 2 Mbit line :-) I didn't test any of these yet, because I rather like to have a slow but = working line... Any comments will be greatly appreciated. Stefan Bethke -- Promo Datentechnik | Tel. 040/431360-0 + Systemberatung GmbH | Fax. 040/431360-60 Waterloohain 6-8 | e-mail: stefan@Promo.DE D-22769 Hamburg | http://www.Promo.DE/ From owner-freebsd-hackers Mon Jul 1 13:31:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06234 for hackers-outgoing; Mon, 1 Jul 1996 13:31:06 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06110; Mon, 1 Jul 1996 13:30:17 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id QAA19774; Mon, 1 Jul 1996 16:29:43 -0400 (EDT) Date: Mon, 1 Jul 1996 16:29:42 -0400 (EDT) From: Brian Tao To: Guido van Rooij cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Increasing openinfo.cachesize in pwd_mkdb (was Re: Incremental [s]pwd.db updates?) In-Reply-To: <199607011757.TAA07646@gvr.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Jul 1996, Guido van Rooij wrote: > > Wait a few days..I'll commit my diffs to -current then. I've come across some master.passwd files that cause my patched version of pwd_mkdb to segfault, but work fine with the standard binary. It may not be possible to arbitrarily set the cachesize value without tweaking some of the other parameters passed to the db hashing functions. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-hackers Mon Jul 1 14:21:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13453 for hackers-outgoing; Mon, 1 Jul 1996 14:21:21 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13431 for ; Mon, 1 Jul 1996 14:21:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA06459; Mon, 1 Jul 1996 14:19:48 -0700 From: Terry Lambert Message-Id: <199607012119.OAA06459@phaeton.artisoft.com> Subject: Re: Cross compile of FreeBSD To: ulf@Lamb.net (Ulf Zimmermann) Date: Mon, 1 Jul 1996 14:19:47 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199606290617.XAA29930@Gatekeeper.lamb.net> from "Ulf Zimmermann" at Jun 28, 96 11:17:17 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Has anyone every tried to cross compile the FreeBSD kernel or maybe even > make world ? For example on a SGI system ? > > Have here an unused challenge at the moment ;-) I did a cross-compile of 386BSD on a SunOS system. Making LD work and making the header files independent of the system header files is hard (and something that should have been done a long time ago for FreeBSD itself, but hasn't been). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 1 14:55:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18214 for hackers-outgoing; Mon, 1 Jul 1996 14:55:20 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18204; Mon, 1 Jul 1996 14:55:16 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607012155.OAA18204@freefall.freebsd.org> Subject: new floppy tape program To: hackers Date: Mon, 1 Jul 1996 14:55:16 -0700 (PDT) Cc: hardware X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Richard Samuel has made available to us a new floppytape program. several people have used it and recommend it over our own ft. it is available on frefall in ~jmb/lft and in incoming/lft.tar.gz.uu if you have a floopy tape, please get this program and try it out. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. 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 From owner-freebsd-hackers Mon Jul 1 15:00:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18995 for hackers-outgoing; Mon, 1 Jul 1996 15:00:35 -0700 (PDT) Received: from ginger.vnet.net (root@ginger.vnet.net [166.82.1.69]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA18746; Mon, 1 Jul 1996 14:59:56 -0700 (PDT) Received: from vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.6.13/8.6.12) with SMTP id RAA00283; Mon, 1 Jul 1996 17:05:24 -0400 Received: from khan@vnet.net (artist.vnet.net) by vnet.net with SMTP id AA27641 (5.67b/IDA-1.5); Mon, 1 Jul 1996 17:55:44 -0400 From: khan Message-Id: X-Mailer: XFMail 0.3 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 In-Reply-To: <199607010321.XAA00249@lakes> Reply-To: khan@vnet.net Date: Mon, 01 Jul 1996 17:50:54 EDT To: Thomas David Rivers Subject: RE: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2 Cc: freebsd-hackers@freefall.freebsd.org, hasty@rah.star-gate.com, lakes!rivers@freefall.freebsd.org, smpatel@xi.dorm.umd.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk just for a test to see if you are get sound try this cat ?.au > /dev/dsp0 > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > > Here's the result of dmesg - (toward the bottom) - indicating >that the card was at least activated: > > sb0 at 0x220 irq 5 drq 1 on isa > sb0: > sbxvi0 at 0x0 drq 5 on isa > sbxvo0: > sbmidi0 at 0x330 on isa > > opl0 at 0x388 on isa > opl0: > > >However, if I cat a .au file to /dev/audio0, all I get is a hung 'cat' >command (indicating the IRQ or DRQ or port isn't right yet...) > >I've appended the result of running pnpinfo, and my version of >pnp.c (to get the fixes.) If you look toward the top; you'll >find my card's setup (the third one in the list.) The 4th >element in the list is my attempt to try and set up the OPL-3 >port... > >Note, this card contains an SoundBlaster Pro implementation, >a MIDI port, a game port, an IDE port and OPL-3.... > > THanks for any help! > > - Dave Rivers - > >--------------------- cut here ---------------------------- > >The sound-related lines in my config (I also have a "controller pnp0" >in there): > > # Controls all sound devices > controller snd0 > device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device opl0 at isa? port 0x388 conflicts > >The result of pnpinfo: > Checking for Plug-n-Play devices... > Board Vendor ID: CTL0028 > Board Serial Number: 001c4a17 > PnP Version: 1.0 > Vendor Version: 16 > Device Description: Creative SB16 PnP > Logical Device ID: CTL0031 (31008c0e) > Register Support 00 > Device Description: Audio > Start Dependent Function > Good Configuration > IRQ: 5 > DMA: 0 1 > DMA Stuff: 8 > DMA: 5 > DMA Stuff: 12 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x220 > I/O alignment for minimum: 1 > I/O length: 16 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x330 > I/O Range maximum address: 0x330 > I/O alignment for minimum: 1 > I/O length: 2 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x388 > I/O Range maximum address: 0x388 > I/O alignment for minimum: 1 > I/O length: 4 > Start Dependent Function > Acceptable Configuration > IRQ: 5 7 10 > DMA: 0 1 3 > DMA Stuff: 8 > DMA: 5 6 7 > DMA Stuff: 12 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x300 > I/O Range maximum address: 0x330 > I/O alignment for minimum: 48 > I/O length: 2 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x388 > I/O Range maximum address: 0x388 > I/O alignment for minimum: 1 > I/O length: 4 > Start Dependent Function > Acceptable Configuration > IRQ: 5 7 10 > DMA: 0 1 3 > DMA Stuff: 8 > DMA: 5 6 7 > DMA Stuff: 12 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x300 > I/O Range maximum address: 0x330 > I/O alignment for minimum: 48 > I/O length: 2 > Start Dependent Function > Sub-optimal Configuration > IRQ: 5 7 10 > DMA: 0 1 3 > DMA Stuff: 8 > DMA: 5 6 7 > DMA Stuff: 12 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > Start Dependent Function > Sub-optimal Configuration > IRQ: 5 7 10 > DMA: 0 1 3 > DMA Stuff: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x300 > I/O Range maximum address: 0x330 > I/O alignment for minimum: 48 > I/O length: 2 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x388 > I/O Range maximum address: 0x388 > I/O alignment for minimum: 1 > I/O length: 4 > Start Dependent Function > Sub-optimal Configuration > IRQ: 5 7 10 > DMA: 0 1 3 > DMA Stuff: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x300 > I/O Range maximum address: 0x330 > I/O alignment for minimum: 48 > I/O length: 2 > Start Dependent Function > Sub-optimal Configuration > IRQ: 5 7 10 11 > DMA: 0 1 3 > DMA Stuff: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x220 > I/O Range maximum address: 0x280 > I/O alignment for minimum: 32 > I/O length: 16 > End Dependent Function > Logical Device ID: CTL2011 (11208c0e) > Register Support 00 > Compatible Device ID: PNP0600 (0006d041) > Device Description: IDE > Start Dependent Function > Good Configuration > IRQ: 10 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x168 > I/O Range maximum address: 0x168 > I/O alignment for minimum: 1 > I/O length: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x36e > I/O Range maximum address: 0x36e > I/O alignment for minimum: 1 > I/O length: 2 > Start Dependent Function > Acceptable Configuration > IRQ: 11 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x1e8 > I/O Range maximum address: 0x1e8 > I/O alignment for minimum: 1 > I/O length: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x3ee > I/O Range maximum address: 0x3ee > I/O alignment for minimum: 1 > I/O length: 2 > Start Dependent Function > Acceptable Configuration > IRQ: 10 11 12 15 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x100 > I/O Range maximum address: 0x1f8 > I/O alignment for minimum: 8 > I/O length: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x300 > I/O Range maximum address: 0x3fe > I/O alignment for minimum: 2 > I/O length: 2 > Start Dependent Function > Sub-optimal Configuration > IRQ: 15 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x170 > I/O Range maximum address: 0x170 > I/O alignment for minimum: 1 > I/O length: 8 > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x376 > I/O Range maximum address: 0x376 > I/O alignment for minimum: 1 > I/O length: 1 > End Dependent Function > Logical Device ID: PNPffff (ffffd041) > Register Support 00 > Device Description: Reserved > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x100 > I/O Range maximum address: 0x3f8 > I/O alignment for minimum: 8 > I/O length: 1 > Logical Device ID: CTL7001 (01708c0e) > Register Support 00 > Compatible Device ID: PNPb02f (2fb0d041) > Device Description: Game > Device decodes the full 16-bit ISA address > I/O Range maximum address: 0x200 > I/O Range maximum address: 0x200 > I/O alignment for minimum: 1 > I/O length: 8 > End Tag > >My pnp.c: > >/* > * Copyright (c) 1996, Sujal M. Patel > * All rights reserved. > * > * Redistribution and use in source and binary forms, with or without > * modification, are permitted provided that the following conditions > * are met: > * 1. Redistributions of source code must retain the above copyright > * notice, this list of conditions and the following disclaimer. > * 2. Redistributions in binary form must reproduce the above copyright > * notice, this list of conditions and the following disclaimer in the > * documentation and/or other materials provided with the distribution. > * 3. All advertising materials mentioning features or use of this software > * must display the following acknowledgement: > * This product includes software developed by Sujal M. Patel > * 4. Neither the name of the author nor the names of any co-contributors > * may be used to endorse or promote products derived from this software > * without specific prior written permission. > * > * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND > * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE > * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE > * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE > * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL > * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS > * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) > * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT > * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY > * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > * SUCH DAMAGE. > * > * $Id: pnp.c,v 1.5 1996/01/12 20:16:26 smpatel Exp smpatel $ > */ > >#include >#include >#include >#include > >#include "pnp.h" > >#define SEND(d, r) outb (ADDRESS, d); outb (WRITE_DATA, r); > >/* The READ_DATA port that we are using currently */ >static int rd_port; > >/* > * Hard coded for now -- Will need to use resource information from > * ISA, PCI, and EISA drivers to auto-configure the PnP-devices > */ >static struct cinfo cinfo[] = >{ > { > 0x00008803, /* Serial Number */ > -1, /* Logical Device Number */ > { 15, -1 }, /* IRQ Number */ > { -1, -1 }, /* DRQ Number */ > { > 0x3e8, /* Ports 1 */ > -1, /* Ports 2 */ > -1, /* Ports 3 */ > -1, /* Ports 4 */ > -1, /* Ports 5 */ > -1, /* Ports 6 */ > -1, /* Ports 7 */ > } > }, > { > 0xb1f5acc0, /* Serial Number */ > -1, /* Logical Device Number */ > { 11, -1 }, /* IRQ Number */ > { -1, -1 }, /* DRQ Number */ > { > 0x340, /* Ports 1 */ > -1, /* Ports 2 */ > -1, /* Ports 3 */ > -1, /* Ports 4 */ > -1, /* Ports 5 */ > -1, /* Ports 6 */ > -1, /* Ports 7 */ > } > }, > { > 0x001c4a17, /* Serial Number */ > 0, /* Logical Device Number */ > { 5, -1 }, /* IRQ Number */ > { 1, -1 }, /* DRQ Number */ > { > 0x220, /* Ports 1 */ > -1, /* Ports 2 */ > -1, /* Ports 3 */ > -1, /* Ports 4 */ > -1, /* Ports 5 */ > -1, /* Ports 6 */ > -1, /* Ports 7 */ > } > }, > { > 0x001c4a17, /* Serial Number */ > 2, /* Logical Device Number */ > { -1, -1 }, /* IRQ Number */ > { -1, -1 }, /* DRQ Number */ > { > 0x388, /* Ports 1 */ > -1, /* Ports 2 */ > -1, /* Ports 3 */ > -1, /* Ports 4 */ > -1, /* Ports 5 */ > -1, /* Ports 6 */ > -1, /* Ports 7 */ > } > } >}; > >int pow __P((int base, int exp)); >void send_Initiation_LFSR __P((void)); >int get_serial __P((unsigned char *data)); >int get_resource_info __P((char *buffer, int len)); >int handle_small_res __P((unsigned char *resinfo, int item, int len)); >void handle_large_res __P((unsigned char *resinfo, int item, int len)); >void config_device __P((unsigned char *data, int csn)); >int isolation_protocol __P((void)); > >int >pow(int base, int exp) >{ > if (exp <= 1) > return base; > else > return base * pow(base, exp - 1); >} > >/* > * Send Initiation LFSR as described in "Plug and Play ISA Specification, > * Intel May 94." > */ >void >send_Initiation_LFSR() >{ > int cur, i; > > /* Reset the LSFR */ > outb(ADDRESS, 0); > outb(ADDRESS, 0); > > cur = 0x6a; > outb(ADDRESS, cur); > > for (i = 1; i < 32; i++) { > cur = (cur >> 1) | (((cur ^ (cur >> 1)) << 7) & 0xff); > outb(ADDRESS, cur); > } >} > >/* > * Get the device's serial number. Returns 1 if the serial is valid. > */ >int >get_serial(data) > unsigned char *data; >{ > int i, bit, valid = 0, sum = 0x6a; > > bzero(data, sizeof(char) * 9); > > for (i = 0; i < 72; i++) { > bit = inb((rd_port << 2) | 0x3) == 0x55; > DELAY(250); /* Delay 250 usec */ > > /* Can't Short Circuit the next evaluation, so 'and' is last */ > bit = (inb((rd_port << 2) | 0x3) == 0xaa) && bit; > DELAY(250); /* Delay 250 usec */ > > valid = valid || bit; > > if (i < 64) > sum = (sum >> 1) | > (((sum ^ (sum >> 1) ^ bit) << 7) & 0xff); > > data[i / 8] = (data[i / 8] >> 1) | (bit ? 0x80 : 0); > } > > valid = valid && (data[8] == sum); > > return valid; >} > >/* > * Dump all the information about configurations. > */ >void >config_device(data, csn) > unsigned char *data; > int csn; >{ > struct cinfo *ci; > int i; > >#ifdef DEBUG > printf("Card assigned CSN #%d\n", csn); >#endif > printf("Board Vendor ID: %c%c%c%02x%02x", > ((data[0] & 0x7c) >> 2) + 64, > (((data[0] & 0x03) << 3) | ((data[1] & 0xe0) >> 5)) + 64, > (data[1] & 0x1f) + 64, data[2], data[3]); > printf(" Board Serial Number: %08x\n", *(int *)&(data[4])); > > SEND(SET_CSN, csn); /* Move this out of this function XXX */ > outb(ADDRESS, STATUS); > > for (ci = cinfo; (int)ci < ((int)cinfo + sizeof (cinfo)); ci++) { > if (ci->serial == *(int *)&(data[4])) { > printf ("Configuring This Card\n"); > > if (((int)ci->ldn) >= 0) > SEND (SET_LDN, ci->ldn); > > for (i = 0; i < 8; i++) > if (ci->port[i] > 0) { > SEND (IO_CONFIG_BASE + i * 2, > ci->port[i] >> 8); > SEND (IO_CONFIG_BASE + i * 2 + 1, > ci->port[i] & 0xff); > } > > for (i = 0; i < 2; i++) > if (ci->irq[i] > 0) { > SEND (IRQ_CONFIG + i * 2, > ci->irq[i]); > } > > for (i = 0; i < 2; i++) > if (ci->drq[i] > 0) { > SEND (DRQ_CONFIG + i, > ci->drq[i]); > } > SEND (IO_RANGE_CHECK, 0); > SEND (ACTIVATE, 1); > } > } >} > >/* > * Run the isolation protocol. Use rd_port as the READ_DATA port value (caller > * should try multiple READ_DATA locations before giving up). Upon exiting, > * all cards are aware that they should use rd_port as the READ_DATA port; > */ >int >isolation_protocol() >{ > int csn; > unsigned char data[9]; > > send_Initiation_LFSR(); > > /* Reset CSN for All Cards */ > SEND(0x02, 0x04); > > for (csn = 1; (csn < MAX_CARDS); csn++) { > /* Wake up cards without a CSN */ > SEND(WAKE, 0); > SEND(SET_RD_DATA, rd_port); > outb(ADDRESS, SERIAL_ISOLATION); > DELAY(1000); /* Delay 1 msec */ > > if (get_serial(data)) > config_device(data, csn); > else > break; > } > return csn - 1; >} > >void >pnp_configure() >{ > int num_pnp_devs; > > printf("Checking for Plug-n-Play devices...\n"); > > /* Try various READ_DATA ports from 0x203-0x3ff */ > for (rd_port = 0x80; (rd_port < 0xff); rd_port += 0x10) { >#ifdef DEBUG > printf("Trying Read_Port at %x\n", (rd_port << 2) | 0x3); >#endif > num_pnp_devs = isolation_protocol(); > if (num_pnp_devs) > break; > } > if (!num_pnp_devs) { > printf("No Plug-n-Play devices were found\n"); > return; > } >} ---------------------------------- E-Mail: khan@vnet.net Date: 07/01/96 Time: 17:50:55 This message was sent by Edwin D. Burley ---------------------------------- From owner-freebsd-hackers Mon Jul 1 15:06:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA19939 for hackers-outgoing; Mon, 1 Jul 1996 15:06:47 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA19933 for ; Mon, 1 Jul 1996 15:06:41 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id PAA13386 for ; Mon, 1 Jul 1996 15:06:30 -0700 (PDT) Message-Id: <199607012206.PAA13386@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: hackers@FreeBSD.ORG Subject: cmu snmp ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Jul 1996 15:06:29 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Who has the latest and greatest port for the cmu snmp stuff? I would like to merge the snmpd on mrouted-3.8.2 with the working version of the cmu snmp version. Or if anyone cares to volunteer to complete the snmp section of mrouted-3.8.2 , you can find it on my ftp site: ftp://rah.star-gate.com/pub/mrouted3.8.2-src.tar.gz Tnks, Amancio From owner-freebsd-hackers Mon Jul 1 15:17:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21404 for hackers-outgoing; Mon, 1 Jul 1996 15:17:16 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA21359 for ; Mon, 1 Jul 1996 15:16:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id PAA01099; Mon, 1 Jul 1996 15:15:00 -0700 (PDT) Message-Id: <199607012215.PAA01099@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: guido@gvr.win.tue.nl (Guido van Rooij), jcl@pavilion.co.uk, hackers@FreeBSD.ORG Subject: Re: Multiple delivery of UDP and IP aliases In-reply-to: Your message of "Mon, 01 Jul 1996 13:13:07 CDT." <199607011813.NAA15675@brasil.moneng.mei.com> From: David Greenman Reply-To: davidg@root.com Date: Mon, 01 Jul 1996 15:14:59 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I made a fix. However, I believ this was fixed in 2.1R. > >I don't believe it was, because when I first mentioned it, it was because >I had upgraded one of my key machines from 2.0R to 2.1R... I do have this >applied as a patch to the machine in question, and the machine is running >2.1.0-RELEASE, and it no longer exhibits this behaviour.. > >> In 2.1, an alias has an associated netmask of all-ones. >> In the udp code, a packet to an address is always checked to >> be a broadcast address using in_broadcast(). For an all-one >> netmask, this succeeds where it should not. >> I `fixed' this by adding a check for the all-one netmask in >> in_broadcast(). This is fixed in 2.1. >> The following patch should fix it on 2.05: > >The patch does work but I swear you need it for 2.1R as well ;-) Joe is right - the fix didn't go in -stable until several months after the 2.1.0 release. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 1 15:23:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22457 for hackers-outgoing; Mon, 1 Jul 1996 15:23:54 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22430 for ; Mon, 1 Jul 1996 15:23:44 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id PAA14510; Mon, 1 Jul 1996 15:23:20 -0700 (PDT) Message-Id: <199607012223.PAA14510@ref.tfs.com> Subject: Re: sup server mirror out-of-sync To: kargl@troutmask.apl.washington.edu (Steven G. Kargl) Date: Mon, 1 Jul 1996 15:23:20 -0700 (PDT) From: "JULIAN Elischer" Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199607011931.MAA29958@troutmask.apl.washington.edu> from "Steven G. Kargl" at Jul 1, 96 12:31:43 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'd like to see an option on SUP that allows the 'last updated' flag be decremented by some amount when doing he updates.. e.g. I know I updated from sup2 at date xx/yy/zz at aa:bb but just to make sure I weant all changes since the day before that.. this would allow people to switch between sup servers..... > > Hackers, > > I have happily used sup to maintain my local -stable source > directory. However, lately I've notice that the sup server > mirrors sup2, sup3, and sup5 appear to be either out-of-date > or flawed in some way. For example, (wrapped to fit) [..] > > Is it too much trouble to ask the maintainers of the sup server mirrors > to check their distributions? > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~kargl/sgk.html > From owner-freebsd-hackers Mon Jul 1 15:26:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22857 for hackers-outgoing; Mon, 1 Jul 1996 15:26:34 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22838 for ; Mon, 1 Jul 1996 15:26:26 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA29568; Mon, 1 Jul 1996 15:25:17 -0700 (PDT) To: Julian Assange cc: avalon@coombs.anu.edu.au (Darren Reed), freebsd-hackers@FreeBSD.org Subject: Re: rsync In-reply-to: Your message of "Mon, 01 Jul 1996 22:57:37 +1000." <199607011257.WAA05320@suburbia.net> Date: Mon, 01 Jul 1996 15:25:17 -0700 Message-ID: <29566.836259917@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I whole-heartedly support the GPL philosophy. Even though it has gone > out of vouge. New information is built on and from existing information. > The speed that information evolves in complexity and function is > directly related how available it is. Retardation of information flows > decreases the efficiency and efficacity of human knowledge. Uh, I sense an impending GPL debate and I think that it would be most unwise to do so in the -hackers mailing list; we have more than enough traffic as it is. :-( Let it simply suffice for me to say that *whatever* attractions a given license may hold, it's been the project's overall philosophy that the simpler a license is, almost regardless of its intent, the better. We don't want to place ANY restrictions on what people do with our software, up to and including making a million bucks off of it if someone really has the motivation to try and make that happen (and if somebody's willing to pay that kind of money, it must mean our software's pretty good :-). The recent removal of BSD copyright clauses 3 and 4 from many of our own contributions only underscores our desire to simplify things, and whatever else you might say about the GPL, it's NOT a simple license. :-) Jordan From owner-freebsd-hackers Mon Jul 1 16:17:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26959 for hackers-outgoing; Mon, 1 Jul 1996 16:17:52 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26944 for ; Mon, 1 Jul 1996 16:17:44 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA29963; Mon, 1 Jul 1996 16:17:34 -0700 (PDT) To: "Charles F. Randall" cc: hackers@freebsd.org Subject: Re: 2.1-960627-SNAP install quirks In-reply-to: Your message of "Mon, 01 Jul 1996 11:44:54 CDT." <9607011144.ZM5639@vis-admin.dmacc.cc.ia.us> Date: Mon, 01 Jul 1996 16:17:33 -0700 Message-ID: <29961.836263053@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1) NFS install using de0 device wouldn't work (hung in nslookup > or NFS mount) unless I disabled other devices (not sure which, > I just removed everything I didn't have) Hmmm. > 2) Screen saver "Snake" didn't ask for timeout value and timeout > option wasn't selectable. In post-install examination of But the timeout option *is* selectable - it's about 3 items down. :-) > 3) Ntpdate setting of "Other" doesn't stick (isn't shown on > screen as selected) and isn't written to /etc/sysconfig Hmm, I'll look into that - thanks! > 4) NFS install that misses a set of files (proflib, for example) > doesn't give you a second chance (I think it used to). The old No, it's always been this boorish. :-) > behavior was nice, because you could go fetch the files on the > NFS server and then try again on the client and it would work. You can still do a retry now - does this not work for you? Strange. Jordan From owner-freebsd-hackers Mon Jul 1 16:19:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA27114 for hackers-outgoing; Mon, 1 Jul 1996 16:19:04 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA27108 for ; Mon, 1 Jul 1996 16:19:02 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id NAA25922 for ; Sat, 29 Jun 1996 13:00:02 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id MAA03375 for freebsd-hackers@freefall.cdrom.com; Sat, 29 Jun 1996 12:57:20 -0700 (MST) From: Don Yuniskis Message-Id: <199606291957.MAA03375@seagull.rtd.com> Subject: Re: freefall.mc patch To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD hackers) Date: Sat, 29 Jun 1996 12:57:20 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Another "no-brainer" diff... Damned if *I* can see where this was > > used in the new scheme of things... > > > define(`UUCP_RELAY', ucbvax.Berkeley.EDU)dnl > > define(`BITNET_RELAY', mailhost.Berkeley.EDU)dnl > > - define(`CSNET_RELAY', mailhost.Berkeley.EDU)dnl > > Actually, none of the 3 lines that I've left in above are any use, to > my knowledge the UUCP_RELAY machine doesn't exist anymore, and I'm not > at all sure about the BITNET or CSNET stuff at all. IMHO they should > all come out, but since Eric Allman has left them in the generic .cf > files he's shipping in sendmail 8.7.x, I haven't raised a fuss. But, "CSNET_RELAY" is not even *referenced* in any of the other macro files (i.e. it's as meaningful as "define(`ESMERELDA',`Mary had a little lamb')") The others I erred on the "safe" side :> -- at least UUCP_RELAY and BITNET_RELAY are actually *used* in the configuration files... I suspect E.A. isn't 100% aware of the little snafus in sendmail! :> --don From owner-freebsd-hackers Mon Jul 1 16:29:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA27967 for hackers-outgoing; Mon, 1 Jul 1996 16:29:36 -0700 (PDT) Received: from friday.keanesea.com (midnight.keanesea.com [206.213.110.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA27962 for ; Mon, 1 Jul 1996 16:29:34 -0700 (PDT) Received: (from root@localhost) by friday.keanesea.com (8.7.4/8.7.3) id AAA01657; Tue, 2 Jul 1996 00:27:35 +0800 Date: Tue, 2 Jul 1996 00:27:34 +0800 (GMT-8) From: Mission Control To: hackers@freebsd.org Subject: What is the best way to setup a drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm curios what the recomended drive setup is I have two hard drives a 540 and a 1.6 How would you divi up the space I will have about 55 Users to setup on it but none of them need much disk space because they are all just on it for mail. Any help would be apriciated Thanks Cyrus Gray From owner-freebsd-hackers Mon Jul 1 16:33:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA28289 for hackers-outgoing; Mon, 1 Jul 1996 16:33:11 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA28268 for ; Mon, 1 Jul 1996 16:32:58 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id AAA06136; Tue, 2 Jul 1996 00:32:38 +0100 (BST) To: Amancio Hasty cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: cmu snmp ? In-reply-to: Your message of "Mon, 01 Jul 1996 15:06:29 PDT." <199607012206.PAA13386@rah.star-gate.com> Date: Tue, 02 Jul 1996 00:32:38 +0100 Message-ID: <6134.836263958@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty wrote in message ID <199607012206.PAA13386@rah.star-gate.com>: > Who has the latest and greatest port for the cmu snmp stuff? CMU SNMP is dead and no longer being developed, as far as I know. > I would like to merge the snmpd on mrouted-3.8.2 with the working > version of the cmu snmp version. How about UCD SNMP? > Or if anyone cares to volunteer to complete the snmp section of > mrouted-3.8.2 , you can find it on my ftp site: > ftp://rah.star-gate.com/pub/mrouted3.8.2-src.tar.gz If you remind me, I'll take a look after 2.1.5 is out the door. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Mon Jul 1 17:55:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA06078 for hackers-outgoing; Mon, 1 Jul 1996 17:55:29 -0700 (PDT) Received: from irbs.irbs.com ([199.182.75.129]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA06069 for ; Mon, 1 Jul 1996 17:55:23 -0700 (PDT) Received: (from jc@localhost) by irbs.irbs.com (8.7.5/8.6.6) id UAA05090; Mon, 1 Jul 1996 20:54:14 -0400 (EDT) From: John Capo Message-Id: <199607020054.UAA05090@irbs.irbs.com> Subject: Re: sup server mirror out-of-sync To: kargl@troutmask.apl.washington.edu (Steven G. Kargl) Date: Mon, 1 Jul 1996 20:54:14 -0400 (EDT) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199607011931.MAA29958@troutmask.apl.washington.edu> from "Steven G. Kargl" at "Jul 1, 96 12:31:43 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steven G. Kargl writes: > > src-secure release=stable host=sup3.FreeBSD.org hostbase=/home base=/usr \ > prefix=/usr/src delete old use-rel-suffix > > should retrieve the src-secure distribution. However, it seems to > get src-sys from sup3. > On June 6 I reported sup3 being a bit confused: SUP Upgrade of src-secure-cvs at Thu Jun 6 02:44:32 1996 SUP Fileserver 9.13 (4.3 BSD) 25028 on lucus.fsl.orst.edu at 02:44:32 SUP Fileserver supports compression. SUP Requesting changes since Dec 31 19:00:00 1969 SUP Receiving file src/lkm/Makefile,v SUP Receiving file src/lkm/Makefile.inc,v SUP Receiving file src/lkm/atapi/Makefile,v src/lkm was not expected. I guess its still hosed. Sup5 had other strange problems and sup2 timed out too often. Switch to cvs tree updates via ctm. You'll like it. John Capo jc@irbs.com IRBS Engineering FreeBSD Servers and Workstations (954) 792-9551 Unix/Internet Consulting - ISP Solutions From owner-freebsd-hackers Mon Jul 1 17:58:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA06235 for hackers-outgoing; Mon, 1 Jul 1996 17:58:15 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA06229 for ; Mon, 1 Jul 1996 17:58:12 -0700 (PDT) Received: from cola124.scsn.net ([206.25.247.124]) by rosie.scsn.net (post.office MTA v1.9.3b ID# 0-13529) with SMTP id AAA190 for ; Mon, 1 Jul 1996 21:01:26 -0400 X-Sender: dmaddox@popmail.scsn.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-hackers@freebsd.org From: dmaddox@scsn.net (Donald J. Maddox) Subject: Sujal's PnP Stuff... Date: Mon, 1 Jul 1996 21:01:26 -0400 Message-ID: <19960702010124199.AAA190@cola124.scsn.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Where can I find the SoundBlaster PnP patches I've seen mentioned on this list? From owner-freebsd-hackers Mon Jul 1 19:51:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14229 for hackers-outgoing; Mon, 1 Jul 1996 19:51:02 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA14181 for ; Mon, 1 Jul 1996 19:50:39 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA05549; Mon, 1 Jul 1996 22:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 1 Jul 1996 22:50 EDT Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.12/8.6.5) with ESMTP id WAA01019; Mon, 1 Jul 1996 22:10:35 -0400 Received: (from rivers@localhost) by lakes (8.6.12/8.6.9) id WAA02976; Mon, 1 Jul 1996 22:14:05 -0400 Date: Mon, 1 Jul 1996 22:14:05 -0400 From: Thomas David Rivers Message-Id: <199607020214.WAA02976@lakes> To: vnet.net!khan@dg-rtp.dg.com, freebsd-hackers@freefall.FreeBSD.org, lakes!rivers Subject: RE: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2 Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > just for a test to see if you are get sound try this > > cat ?.au > /dev/dsp0 > Nope - still just get a locked-up 'cat' command... - Dave Rivers - From owner-freebsd-hackers Mon Jul 1 21:17:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24888 for hackers-outgoing; Mon, 1 Jul 1996 21:17:14 -0700 (PDT) Received: from sujal.prognet.com (root@lennon-c03.aa.net [204.157.220.167]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24882 for ; Mon, 1 Jul 1996 21:17:09 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by sujal.prognet.com (8.7.5/8.6.12) with SMTP id VAA01318; Mon, 1 Jul 1996 21:15:51 -0700 (PDT) Date: Mon, 1 Jul 1996 21:15:50 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@sujal.prognet.com To: Thomas David Rivers cc: freebsd-hackers@freefall.freebsd.org, smpatel@umiacs.umd.edu Subject: Re: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2.1-RELEASE?) In-Reply-To: <199607010321.XAA00249@lakes> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 30 Jun 1996, Thomas David Rivers wrote: > I've chucked my Opti 8c929 card for a brand-new Sound Blaster PnP > card.... I got tired of wrestling with it... Good Choice :-) The SB PnP is an excellent card. > > I had previously grabbed Sujal's PnP stuff, and now have it > "working" in a 2.1-RELEASE kernel. (I made several fixes, which > I'm sure, by now, other people have reported... autoconf.c needs to > #include "pnp.h" - and several changes to pnp.c - which I've attached > below.) You're using an older version of the PnP code. Try to upgrade to the code in: ftp://freefall.freebsd.org/incoming/ISA_PnP.May5.tar.gz There is one critical bug fix (which is why your card doesn't work). You need to change: #define SEND(d, r) outb (ADDRESS, d); outb (WRITE_DATA, r); TO #define SEND(d, r) {outb (ADDRESS, d); outb (WRITE_DATA, r);} This will fix your problem (99% sure!) I hope to get some time soon to improve this stuff, but work keeps me sooooo busy :-) Sujal From owner-freebsd-hackers Mon Jul 1 21:39:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26094 for hackers-outgoing; Mon, 1 Jul 1996 21:39:34 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA26089 for ; Mon, 1 Jul 1996 21:39:31 -0700 (PDT) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0uaxFD-0008rbC; Mon, 1 Jul 96 21:39 PDT Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Spam lists To: freebsd-hackers@freefall.freebsd.org Date: Mon, 1 Jul 1996 21:39:23 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > How about a "companies who have spammed our lists" area on the WWW > page so we can know who not to buy from? See http://www.ip.net/BL/blacklist.html for a more comprehensive listing, and a place to add such to... -- Alan Batie ______ We're Starfleet officers: batie@agora.rdrop.com \ / Weird is part of the job. +1 503 452-0960 \ / --Captain Janeway DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-hackers Tue Jul 2 00:23:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05254 for hackers-outgoing; Tue, 2 Jul 1996 00:23:03 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA05244 for ; Tue, 2 Jul 1996 00:22:57 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA05245; Tue, 2 Jul 1996 09:21:06 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA26683; Tue, 2 Jul 1996 09:21:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA10604; Tue, 2 Jul 1996 09:05:01 +0200 (MET DST) From: J Wunsch Message-Id: <199607020705.JAA10604@uriah.heep.sax.de> Subject: Re: Netscape is out of memory To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 2 Jul 1996 09:05:01 +0200 (MET DST) Cc: tam@cd.iidpwr.com (Tony Tam) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Tony Tam at "Jun 30, 96 11:16:26 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tony Tam wrote: > The error message is "Netscape is out of memory. Try quitting some > other applications or closing some windows." I got this error message as What about your swap usage? I assume you've got too few swap for running a memory-pig like Netcrap. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 2 01:32:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA08834 for hackers-outgoing; Tue, 2 Jul 1996 01:32:12 -0700 (PDT) Received: from ns.pa-consulting.com (ns.pa-consulting.com [193.118.224.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA08795 for ; Tue, 2 Jul 1996 01:32:02 -0700 (PDT) Received: from SMTPGATE.PA-CONSULTING.COM by ns.pa-consulting.com (8.6.4) id JAA18911; Tue, 2 Jul 1996 09:40:52 +0100 Received: by SMTPGATE.PA-CONSULTING.COM with Microsoft Mail id <31D95119@SMTPGATE.PA-CONSULTING.COM>; Tue, 02 Jul 96 09:40:57 PDT From: Duncan Barclay To: freebsd-hackers Subject: NEC Scsi Card Date: Tue, 02 Jul 96 09:26:00 PDT Message-ID: <31D95119@SMTPGATE.PA-CONSULTING.COM> Encoding: 22 TEXT X-Mailer: Microsoft Mail V3.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi In a junk shop last weekend I found a NEC scsi cdrom and ISA scsi card(no maunual, but DOS driver disk). The card probes fine as a NCR53C400 but doesnt seem to work with an old Rodime drive (R3000T or something). I haven't tried it with the cdrom drive, a mate had that. Can any one point me to where I can get a bit more info on the card, primarily there are three dip switches marked as 'see manual' :-) With the drive connected the probes get the drive type but can get mode page 4. After I turned on the nca driver debugging the drive seems to respond to the mode page request with a disconnect message. Any help appreicated. Duncan From owner-freebsd-hackers Tue Jul 2 01:56:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12034 for hackers-outgoing; Tue, 2 Jul 1996 01:56:36 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA11889 for ; Tue, 2 Jul 1996 01:55:25 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA12435; Tue, 2 Jul 1996 10:49:15 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id LAA02027; Tue, 2 Jul 1996 11:01:28 +0200 From: "Christoph P. Kukulies" Message-Id: <199607020901.LAA02027@gilberto.physik.rwth-aachen.de> Subject: Re: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2.1-RELEASE?) To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Tue, 2 Jul 1996 11:01:27 +0200 (MET DST) Cc: ponds!rivers@dg-rtp.dg.com, freebsd-hackers@freefall.freebsd.org, smpatel@umiacs.umd.edu In-Reply-To: from Sujal Patel at "Jul 1, 96 09:15:50 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 30 Jun 1996, Thomas David Rivers wrote: > > > I've chucked my Opti 8c929 card for a brand-new Sound Blaster PnP > > card.... I got tired of wrestling with it... > > Good Choice :-) The SB PnP is an excellent card. While being at it: Is the SB PnP suitable for doing full duplex i/o (dma) like the GUS cards making it an alternate choice for using it with conferencing tools? (vat, etc.) [patch deleted] > Sujal > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Tue Jul 2 04:22:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29671 for hackers-outgoing; Tue, 2 Jul 1996 04:22:06 -0700 (PDT) Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA29652 for ; Tue, 2 Jul 1996 04:21:57 -0700 (PDT) Received: (from alexis@localhost) by dawn.ww.net (8.7.5/alexis 2.5) id PAA04053 for freebsd-hackers@freebsd.org; Tue, 2 Jul 1996 15:21:31 +0400 (MSD) Message-Id: <199607021121.PAA04053@dawn.ww.net> Subject: aic glitch? To: freebsd-hackers@freebsd.org Date: Tue, 2 Jul 1996 15:21:31 +0400 (MSD) From: Alexis Yushin Reply-To: alexis@ww.net (Alexis Yushin) X-Office-Phone: +380 65 2 26.1410 X-Home-Phone: +380 65 2 27.0747 X-NIC-Handle: AY23 X-RIPE-Handle: AY6-RIPE X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I keep receiving the following (aic, Connor hard drive): scsi -f /dev/rsd0c -c "12 0 0 0 64 0" -i 64 "s8 z8 z16 z4" >SCIOCCOMMAND ioctl: Command accepted. > host adapter status 2 ^^^^^^^^^^^^^^^^^^^^^^^ Why? Is it CHECK CONDITION or CONDITION MET? >Command out (6 of 6): >12 00 00 00 64 00 > >Data in (64 of 64): >00 00 02 02 1f 00 00 12 43 4f 4e 4e 45 52 20 20 # ........CONNER >43 46 50 31 30 36 30 53 20 31 2e 30 35 47 42 20 # CFP1060S 1.05GB >32 34 35 46 00 00 00 00 00 00 00 00 00 00 00 00 # 245F............ >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 # ................ > >No sense sent. >CONNER CFP1060S 1.05GB 245F alexis -- Real Users hate Real Programmers From owner-freebsd-hackers Tue Jul 2 04:30:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA00351 for hackers-outgoing; Tue, 2 Jul 1996 04:30:01 -0700 (PDT) Received: from shell.monmouth.com (pechter@shell.monmouth.com [205.164.220.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA00343; Tue, 2 Jul 1996 04:29:56 -0700 (PDT) Received: (from pechter@localhost) by shell.monmouth.com (8.6.12/8.6.12) id HAA24901; Tue, 2 Jul 1996 07:25:14 -0400 From: Bill/Carolyn Pechter Message-Id: <199607021125.HAA24901@shell.monmouth.com> Subject: Re: Dual-booting FreeBSD and Windows95??? To: gpalmer@freebsd.org (Gary Palmer) Date: Tue, 2 Jul 1996 07:25:13 -0400 (EDT) Cc: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) In-Reply-To: <10391.836167322@palmer.demon.co.uk> from "Gary Palmer" at Jun 30, 96 09:42:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Brandon Gillespie wrote in message ID > : > > If the IBM PS/1 is a microchannel board you may have some serious > > problems getting FreeBSD working (last I checked Microchannel is not > > supported, has this changed?). > > It hasn't changed, no. I seem to remember several people offering to do > MCA support over the last 2 odd years, but nothing has ever come of > it. I would be very surpised if anything was done about MCA support > in the next year or so, as it isn't very common and is becoming less so. > > Gary Unfortunately, this is so. I work for IBM now and there's a Ton of 386's I'd be running FreeBSD on if I could get an idea of how to get Token Ring support and Microchannel support working. But both are way beyond me. The machines are cheap and surplus hardware internally (and just about the same externally at every used hardware company... I hear there's folks with Linux up on microchannel and I've got a Compaq running with Token Ring support under Linux now. Bill ------------------------------------------------------------------------------- Bill Pechter/Carolyn Pechter | 17 Meredith Drive, Tinton Falls, NJ 07724, 908-389-3592 | pechter@shell.monmouth.com I'll run Win95 on my box when you pry the keyboard from my cold, dead hands. FreeBSD, OS/2, CP/M, RT11, spoken here. From owner-freebsd-hackers Tue Jul 2 06:31:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07301 for hackers-outgoing; Tue, 2 Jul 1996 06:31:06 -0700 (PDT) Received: from adams.bathl.westnet.net.uk (adams.bathl.westnet.net.uk [194.6.102.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA07295 for ; Tue, 2 Jul 1996 06:31:00 -0700 (PDT) Received: from 158.125.14.18 (mac-sfres1.lut.ac.uk [158.125.14.18]) by adams.bathl.westnet.net.uk (8.6.11/8.6.9) with SMTP id OAA05397; Tue, 2 Jul 1996 14:37:45 +0100 Message-ID: <31D92471.6CAA@adams.bathl.westnet.net.uk> Date: Tue, 02 Jul 1996 14:30:25 +0100 From: Neil Moore Reply-To: neilod@adams.bathl.westnet.net.uk Organization: Loughborough Students' Union X-Mailer: Mozilla 2.0 (Macintosh; I; 68K) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having some problems installing FreeBSD onto my computer, from my MS-DOS partition, I have set aside 215MB for BSD's use and set up the partitions with in that as, a 100MB for /, B is a 16MB Swap file and E is a 99MB for /usr. the installation starts and seems to go ahead OK until I get a message saying ROOT Distribution not found, but all the files from the bin dir on the ftp server are in C:\FREEBSD\BIN so I can't see what the problem is, hope you can help, and could you reply by e-mail please. Neil Moore From owner-freebsd-hackers Tue Jul 2 06:50:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08789 for hackers-outgoing; Tue, 2 Jul 1996 06:50:42 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA08784 for ; Tue, 2 Jul 1996 06:50:38 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA10688; Tue, 2 Jul 1996 09:50:02 -0400 Date: Tue, 2 Jul 1996 09:50:01 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@freebsd.org Subject: OK, here goes fastlock: In-Reply-To: <199607020516.BAA01761@kropotkin.gnu.ai.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's a simple test-and-set function for the 386 (tested and works): int tset(int *i, int lockval, int unlockval) { int j = 0; asm("movl 16(%ebp), %eax"); asm("movl 8(%ebp),%ecx"); asm("movl 12(%ebp),%edx"); asm("cmpxchg %edx, (%ecx)"); asm("jne failed"); asm("movl %eax, -4(%ebp)"); asm("jmp done"); asm("failed: movl %eax, -4(%ebp)"); asm("done:"); return j; } This will run a bit faster than a file lock system call :-). But what about contention? notice that this function, if it fails, fails. so we need a retry strategy. IF you fail, should you spin forever? NO! Do that, and you eat the processor doing nothing. You ought to have a reasonable way to, say, spin one or two more times, then go to a more heavyweight sleep. SO: here's the fastlock library call (#ifdef USEMOD is for LKM ) void fastlock(int *address, int lockval, int unlockval) { int testval; #ifdef USEMOD static int syscallnum = -1; if (syscallnum < 0) syscallnum = syscallfind("fastlock"); if (syscallnum < 0) { perror("fastlock syscallfind"); return; } #endif testval = tset(address, lockval, unlockval); if (testval == unlockval) { #ifdef FASTLOCKDEBUG printf("(%d)fastlock quickout\n", getpid()); #endif return; } /* attempt to lock failed. test then wait in kernel sleep() */ while (1) { /* set the high-order bit. This tells the unlocker to do the system * call and free up the lock. */ (void) tset(address, testval|0x80000000,testval); #ifdef FASTLOCKDEBUG printf("(%d)hang in there\n", getpid()); #endif /* we should be checking here to make sure that high-order bit is * set. But this second tset fails only * in the event of contention, in which case * someone else has set the high-order * bit too ... seems pointless, esp. given that fastlock has a timeout */ syscall(syscallnum, 1, address, unlockval); testval = tset(address, lockval, unlockval); if (testval == unlockval) return; } } So what are we doing? We're doing the tset. If it fails, then we do one more tset, to set the high order bit, then drop into the fastlock system call. Once we return from that, we try to tset the variable again. If that fails, we drop once again into the system call. Here's fastunlock: void fastunlock(int *address, int unlockval) { int dosyscall = 0; static int syscallnum = -1; /* this is really in the file */ #ifdef USEMOD if (syscallnum < 0) syscallnum = syscallfind("fastlock"); if (syscallnum < 0) { perror("fastunlock syscallfind"); return; } #endif if (*address & 0x80000000) dosyscall = 1; *address = unlockval; #ifdef FASTLOCKDEBUG printf("(%d)fastunlock dosyscall is %d\n", getpid(), dosyscall); if (dosyscall) printf("conflict %d\n", getpid()); fflush(stdout); #endif if (dosyscall) syscall(syscallnum, 0, address, unlockval); } Ok, this one tests to see if it needs to wake any sleepers, clears the memory variable, then drops into the kernel if needed (if (dosyscall) ...) Here's the system call. Note several things: 1) the definition of 'unlocked' is passed in to the system call for the final test, not assumed to be zero. 2) The 'address' argument does NOT NEED TO BE AN ADDRESS. it's a number that all the procs have to agree on, that is all. 3) if you accidently awake more than one sleeper, the loop in fastlock handles that properly 4) This system call handles both waking up and sleeping 5) For my measurements, this thing is a whole lot faster than anything else available on (e.g.) freebsd. Questions to me. int fastlock(p, uap, retval) struct proc *p; struct flu *uap; int retval[]; { extern int hz; retval[0] = 0; /* printf("fastlockunlock: com %d address 0x%x unlocked %d\n", uap->com, uap->address, uap->unlocked); */ if (uap->com == 0) /* unlock */ wakeup((void *) uap->address); else { /* last chance */ /* try one last time to see if it is unlocked */ int curval = fuword((void *) uap->address); if (curval == uap->unlocked) return; tsleep((void *) uap->address, PUSER, NULL, 10*hz); } return 0; } Ron Minnich |"Inferno runs on MIPS ..., Intel ..., and AMD's rminnich@sarnoff.com |29-kilobit-per-second chip-based architectures ..." (609)-734-3120 | Comm. week, may 13, pg. 4. ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Tue Jul 2 06:51:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08823 for hackers-outgoing; Tue, 2 Jul 1996 06:51:15 -0700 (PDT) Received: from onyx.bios.unc.edu (onyx.bios.unc.edu [152.2.94.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA08815 for ; Tue, 2 Jul 1996 06:51:12 -0700 (PDT) Received: from localhost (walter@localhost) by onyx.bios.unc.edu (8.6.12/8.6.12) with SMTP id JAA11265 for ; Tue, 2 Jul 1996 09:50:59 -0400 Date: Tue, 2 Jul 1996 09:50:58 -0400 (EDT) From: Bruce Walter To: hackers@freebsd.org Subject: SIG's 11 and 6... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all! Just thought I'd share a little interesting thing with you. Several weeks back I remember a thread which had several people experiencing random SIG 11's and SIG 6's for unexplained reasons (usually during compiles for me). The party line has been to suspect your memory and motherboard, but I have actually found another possible culprit: HEAT! My pentium 120 was having the above problems. Switching out memory would solve them for a day or two, but the problems would then start to build up again. FINALLY I replaced the CPU fan and added a big waffle fan in the front of the case and VOILA... No more SIG's for the last week. Chances are that in the past the time involved in cracking the case and swapping memory dropped the temp enough to alleviate the problem. - Bruce ======================================================================== || Bruce Walter || CB #7400 McGavran-Greenberg Hall || || Information Technology Support || Chapel Hill, NC 27599-7400 || || Department of Biostatistics || Tel: 919-966-7279 || || University of North Carolina || Fax: 919-966-3804 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Tue Jul 2 07:45:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA12173 for hackers-outgoing; Tue, 2 Jul 1996 07:45:56 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA12164 for ; Tue, 2 Jul 1996 07:45:48 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id PAA20207 for ; Tue, 2 Jul 1996 15:47:33 +0100 Date: Tue, 2 Jul 1996 15:47:32 +0100 (BST) From: Developer To: hackers@freebsd.org Subject: Help V2.2 doesn't work In-Reply-To: <31D92471.6CAA@adams.bathl.westnet.net.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if anyone else has had any success in getting the new V2.2 kernel to run on their PC.. V2,1 runs fine for me on a wide variety of machines but V2.2 just resets right at the start before I even see any devices being scanned??!! Regards, Trefor S. From owner-freebsd-hackers Tue Jul 2 07:50:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA12463 for hackers-outgoing; Tue, 2 Jul 1996 07:50:21 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA12423 for ; Tue, 2 Jul 1996 07:50:12 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA16959; Tue, 2 Jul 1996 09:49:37 -0500 From: Joe Greco Message-Id: <199607021449.JAA16959@brasil.moneng.mei.com> Subject: Re: What is the best way to setup a drive To: root@friday.keanesea.com (Mission Control) Date: Tue, 2 Jul 1996 09:49:37 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: from "Mission Control" at Jul 2, 96 00:27:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm curios what the recomended > drive setup is I have two hard > drives a 540 and a 1.6 How would > you divi up the space I will have > about 55 Users to setup on it but > none of them need much disk space > because they are all just on it for > mail. It may sound silly, but... I usually partition disks in the following way. 40M / 60M swap (unless you expect to run a lot of progs, then 160 or 260M) 80M /usr 100M /usr/local (unless you expect to have a lot of progs, then 200M or 300M) 120M /var (more if you plan to have a LOT of mail in mailboxes) 140M /var/spool (if you plan on doing lots of mail or UUCP _ONLY_ otherwise don't bother with this partition) Split the rest between /usr/src and /home, as needed... This has the advantage of being quick, easy, and generally chops up a 540M root disk pretty well. Disadvantages: you'll probably have to put X11 someplace else (I usually choose /usr/local and make a symlink), and there isn't enough space for /usr/obj if you are doing a world build. ... JG From owner-freebsd-hackers Tue Jul 2 08:08:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13769 for hackers-outgoing; Tue, 2 Jul 1996 08:08:34 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA13757 for ; Tue, 2 Jul 1996 08:08:29 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA17016; Tue, 2 Jul 1996 10:07:19 -0500 From: Joe Greco Message-Id: <199607021507.KAA17016@brasil.moneng.mei.com> Subject: Re: Are you a programmer? Do you wear glasses? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Tue, 2 Jul 1996 10:07:18 -0500 (CDT) Cc: dgy@rtd.com, hackers@freebsd.org In-Reply-To: <199607011636.JAA08702@freefall.freebsd.org> from "Jonathan M. Bresler" at Jul 1, 96 09:36:00 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Joe Greco wrote: > > > > > > > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > > > > > mail it to this guy? Maybe 10K each day for the next year or so? > > > > > > > > :). AOL has like a 300K limit on mail messages. Probably because > > > > people who use AOL tend to piss other people off. > > > > > > Actually, aren't the lists set up so that only subscribers can post > > > to the lists? Or, is that considered too "unfriendly"? > > > > That would be bad to do, people are often referred here when they encounter > > strange problems. > > > > It might make sense to hold their messages in an "approval queue" if they > > are not a list member. > > we had had vbery few incidents of this type. i get to the approval > queue every day or two. because of that dealy, a new user might > get left out in the cold for 48 hours. > > better to live with a spam or two every onnce in a while than > to lose people because we are too distant. in spite of how > much i hate spam....sigh I would tend to agree, I was mainly trying to point out why closing the lists to non-subscriber posts would be a bad idea. ... JG From owner-freebsd-hackers Tue Jul 2 08:09:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13870 for hackers-outgoing; Tue, 2 Jul 1996 08:09:23 -0700 (PDT) Received: from scruz.net (nic.scruz.net [165.227.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA13858 for ; Tue, 2 Jul 1996 08:09:19 -0700 (PDT) Received: from Grizzly.COM by scruz.net (8.7.3/1.34) id IAA02668; Tue, 2 Jul 1996 08:08:07 -0700 (PDT) Received: (from markd@localhost) by Grizzly.COM (8.7.5/8.7.3) id IAA01591; Tue, 2 Jul 1996 08:03:29 -0700 (PDT) Date: Tue, 2 Jul 1996 08:03:29 -0700 (PDT) Message-Id: <199607021503.IAA01591@Grizzly.COM> From: Mark Diekhans To: proff@suburbia.net, avalon@coombs.anu.edu.au, freebsd-hackers@freebsd.org CC: jkh@time.cdrom.com In-reply-to: <29566.836259917@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: rsync Reply-to: med@scruznet.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I whole-heartedly support the GPL philosophy. Even though it has gone >> out of vouge. New information is built on and from existing information. >> The speed that information evolves in complexity and function is >> directly related how available it is. Retardation of information flows >> decreases the efficiency and efficacity of human knowledge. > >Uh, I sense an impending GPL debate and I think that it would be most >unwise to do so in the -hackers mailing list; we have more than enough >traffic as it is. :-( Paul Mackerras is a very smart and reasonable guy. Other software he created and made public available was under a BSD style copyright (Tk photo widget). Perhaps the best approach is to present a reasoned argument about why this software should be available under a difference copyright directly to the authors? Mark From owner-freebsd-hackers Tue Jul 2 08:29:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15528 for hackers-outgoing; Tue, 2 Jul 1996 08:29:37 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA15518 for ; Tue, 2 Jul 1996 08:29:30 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA02183; Tue, 2 Jul 1996 11:38:50 -0400 Date: Tue, 2 Jul 1996 11:38:50 -0400 Message-Id: <199607021538.LAA02183@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: batie@agora.rdrop.com (Alan Batie) From: dennis@etinc.com (Dennis) Subject: Re: Spam lists Cc: freebsd-hackers@freefall.freebsd.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> How about a "companies who have spammed our lists" area on the WWW >> page so we can know who not to buy from? > >See http://www.ip.net/BL/blacklist.html for a more comprehensive listing, >and a place to add such to... > >-- >Alan Batie ______ We're Starfleet officers: >batie@agora.rdrop.com \ / Weird is part of the job. >+1 503 452-0960 \ / --Captain Janeway >DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 > >It is my policy to avoid purchase of any products from companies which >use unrequested email advertisements or telephone solicitation. > real businessmen make decisions on the quality of the product, not where they advertise. But, if you're happy, what the heck! It amazes me that someone has so much time as to compile such a useless list of counterculture. Its a good thing that we dont have such policies about long-distance companies, otherwise we'd all be out of business with no service at all! Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Tue Jul 2 09:05:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18528 for hackers-outgoing; Tue, 2 Jul 1996 09:05:16 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18519; Tue, 2 Jul 1996 09:05:08 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607021605.JAA18519@freefall.freebsd.org> Subject: Re: What is the best way to setup a drive To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Tue, 2 Jul 1996 09:05:07 -0700 (PDT) Cc: root@friday.keanesea.com, hackers@freebsd.org In-Reply-To: <199607021449.JAA16959@brasil.moneng.mei.com> from "Joe Greco" at Jul 2, 96 09:49:37 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joe Greco wrote: > > I usually partition disks in the following way. > > 40M / > 60M swap (unless you expect to run a lot of progs, then 160 or 260M) > 80M /usr > 100M /usr/local (unless you expect to have a lot of progs, then 200M or 300M) > 120M /var (more if you plan to have a LOT of mail in mailboxes) > 140M /var/spool (if you plan on doing lots of mail or UUCP _ONLY_ otherwise > don't bother with this partition) > > Split the rest between /usr/src and /home, as needed... > > This has the advantage of being quick, easy, and generally chops up a 540M > root disk pretty well. > > Disadvantages: you'll probably have to put X11 someplace else (I usually > choose /usr/local and make a symlink), and there isn't enough space for > /usr/obj if you are doing a world build. add a separate partition for /tmp and you *might be* well on your way to being able to mount / read-only. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. 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 From owner-freebsd-hackers Tue Jul 2 09:41:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21118 for hackers-outgoing; Tue, 2 Jul 1996 09:41:13 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA21110 for ; Tue, 2 Jul 1996 09:41:09 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA17375; Tue, 2 Jul 1996 11:39:22 -0500 From: Joe Greco Message-Id: <199607021639.LAA17375@brasil.moneng.mei.com> Subject: Re: What is the best way to setup a drive To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Tue, 2 Jul 1996 11:39:22 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@freebsd.orgroot@friday.keanesea.com, hackers@freebsd.org In-Reply-To: <199607021605.JAA18519@freefall.freebsd.org> from "Jonathan M. Bresler" at Jul 2, 96 09:05:07 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Joe Greco wrote: > > > > I usually partition disks in the following way. > > > > 40M / > > 60M swap (unless you expect to run a lot of progs, then 160 or 260M) > > 80M /usr > > 100M /usr/local (unless you expect to have a lot of progs, then 200M or 300M) > > 120M /var (more if you plan to have a LOT of mail in mailboxes) > > 140M /var/spool (if you plan on doing lots of mail or UUCP _ONLY_ otherwise > > don't bother with this partition) > > > > Split the rest between /usr/src and /home, as needed... > > > > This has the advantage of being quick, easy, and generally chops up a 540M > > root disk pretty well. > > > > Disadvantages: you'll probably have to put X11 someplace else (I usually > > choose /usr/local and make a symlink), and there isn't enough space for > > /usr/obj if you are doing a world build. > > add a separate partition for /tmp and you *might be* well on your way > to being able to mount / read-only. Actually my ideal goal would be to shoot for "unmodified".. (read-only is a subset of that larger goal, in my mind). I would like "/" and "/usr" to be identical on all my machines. Adding a mfs /tmp is not hard and that leaves the kernel and /etc as the two outstanding issues. It becomes so much easier to secure a system then ;-) In any case, I have seen so many people do "silly" things with their disk layouts. People either do not understand the _reasons_ for going with multiple partitions, or they size them poorly... the big local ISP in these parts had a 1GB / filesystem at one time, in addition to the standard /var, /usr, etc.. I've yet to see an automated tool that sized things according to any reasonable rules that I could find out. The Sun tool works halfway well, but that's about it. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-hackers Tue Jul 2 10:21:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23710 for hackers-outgoing; Tue, 2 Jul 1996 10:21:14 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA23704 for ; Tue, 2 Jul 1996 10:21:07 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.6.12) with SMTP id KAA00957; Tue, 2 Jul 1996 10:28:37 -0700 (PDT) Date: Tue, 2 Jul 1996 10:28:36 -0700 (PDT) From: Tom Samplonius To: "Jonathan M. Bresler" cc: Joe Greco , root@friday.keanesea.com, hackers@freebsd.org Subject: Re: What is the best way to setup a drive In-Reply-To: <199607021605.JAA18519@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > add a separate partition for /tmp and you *might be* well on your way > to being able to mount / read-only. And say goodbye to changing your password... Tom From owner-freebsd-hackers Tue Jul 2 10:23:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23839 for hackers-outgoing; Tue, 2 Jul 1996 10:23:43 -0700 (PDT) Received: from mickey.umiacs.umd.edu (mickey.umiacs.umd.edu [128.8.120.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA23834 for ; Tue, 2 Jul 1996 10:23:40 -0700 (PDT) Received: (smpatel@localhost) by mickey.umiacs.umd.edu (8.7.5/UMIACS-0.9/04-05-88) id NAA07756; Tue, 2 Jul 1996 13:22:54 -0400 (EDT) Date: Tue, 2 Jul 1996 13:22:54 -0400 (EDT) From: Sujal Patel To: "Christoph P. Kukulies" cc: ponds!rivers@dg-rtp.dg.com, freebsd-hackers@freefall.freebsd.org Subject: Re: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2.1-RELEASE?) In-Reply-To: <199607020901.LAA02027@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Christoph P. Kukulies wrote: > While being at it: Is the SB PnP suitable for doing full duplex i/o (dma) > like the GUS cards making it an alternate choice for using it with > conferencing tools? (vat, etc.) This is not yet possible under FreeBSD, unless you use Amancio's TASD distribution(?)... Sujal From owner-freebsd-hackers Tue Jul 2 10:33:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24269 for hackers-outgoing; Tue, 2 Jul 1996 10:33:14 -0700 (PDT) Received: from iidpwr.com ([204.33.177.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA24264 for ; Tue, 2 Jul 1996 10:33:07 -0700 (PDT) Received: by mail.iidpwr.com id <15363>; Tue, 2 Jul 1996 10:35:31 -0700 Date: Tue, 2 Jul 1996 10:36:23 -0700 From: Tony Tam Organization: Imperial Irrigation District X-Mailer: Mozilla 2.0 (X11; I; BSD/386 uname failed) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape is out of memory References: <199607020705.JAA10604@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <96Jul2.103531pdt.15363@mail.iidpwr.com> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Tony Tam wrote: > > > The error message is "Netscape is out of memory. Try quitting some > > other applications or closing some windows." I got this error message as > > What about your swap usage? I assume you've got too few swap for > running a memory-pig like Netcrap. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) Well, as a matter of fact, I have 128M byte of swap space. I have some new discovery. That is Netscape Ver. 2.0 can send mail with FreeBSD-2.0.5 RELEASE. By the way, this mail is sent by the above box. But Netscape Ver. 2.0 doesn't work with FreeBSD 2.1.0-RELEASE. I move the same version of netscape to the 2.1.0 box. As soon as I hit the send mail button, I got the same error message. Since I am using the same version of X-Windows 3.1.2 in both RELEASEs, I am suspecting the "out-of-memory" problem is causing by the operating system. Any idea? Hackers. Tony Tam From owner-freebsd-hackers Tue Jul 2 10:51:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25580 for hackers-outgoing; Tue, 2 Jul 1996 10:51:45 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25573; Tue, 2 Jul 1996 10:51:44 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607021751.KAA25573@freefall.freebsd.org> Subject: Re: What is the best way to setup a drive To: tom@sdf.com (Tom Samplonius) Date: Tue, 2 Jul 1996 10:51:44 -0700 (PDT) Cc: jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jul 2, 96 10:28:36 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote: > > > On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > > > add a separate partition for /tmp and you *might be* well on your way > > to being able to mount / read-only. > > And say goodbye to changing your password... ah...true, true. i did say might ;) add /etc to the list, unless of course its a symlink to a file on some r/w filesystem jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. 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 From owner-freebsd-hackers Tue Jul 2 10:58:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25985 for hackers-outgoing; Tue, 2 Jul 1996 10:58:50 -0700 (PDT) Received: from sivka.rdy.com (sivka.rdy.com [205.149.182.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA25978 for ; Tue, 2 Jul 1996 10:58:47 -0700 (PDT) Received: from dima@localhost by sivka.rdy.com id KAA00355; (8.7/RDY) Tue, 2 Jul 1996 10:29:48 -0700 (PDT) From: "Dima Ruban" Message-Id: <960702102947.ZM353@sivka.rdy.com> Date: Tue, 2 Jul 1996 10:29:46 -0700 In-Reply-To: Ulf Zimmermann "Cross compile of FreeBSD" (Jun 28, 11:17pm) References: <199606290617.XAA29930@Gatekeeper.lamb.net> Organization: HackerDome, Inc. X-Mailer: Z-Mail (4.0b.514 14may96) To: Ulf Zimmermann , hackers@FreeBSD.org Subject: Re: Cross compile of FreeBSD MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Jun 28, 11:17pm, Ulf Zimmermann wrote: > Subject: Cross compile of FreeBSD > Hi. > > Has anyone every tried to cross compile the FreeBSD kernel or maybe even > make world ? For example on a SGI system ? I've done it some time ago for IRIX. Not kernel/make world, but it worked pretty good, when our customers were compiling their CGI scripts under IRIX, when WWW server was actually under FreeBSD. > Have here an unused challenge at the moment ;-) Don't you forget my address? :-) > > Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 > >-- End of excerpt from Ulf Zimmermann -- -- dima From owner-freebsd-hackers Tue Jul 2 11:27:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28359 for hackers-outgoing; Tue, 2 Jul 1996 11:27:44 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28354 for ; Tue, 2 Jul 1996 11:27:41 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.6.12) with SMTP id LAA01080; Tue, 2 Jul 1996 11:35:20 -0700 (PDT) Date: Tue, 2 Jul 1996 11:35:19 -0700 (PDT) From: Tom Samplonius To: "Jonathan M. Bresler" cc: jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG Subject: Re: What is the best way to setup a drive In-Reply-To: <199607021751.KAA25573@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > Tom Samplonius wrote: > > > > > > On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > > > > > add a separate partition for /tmp and you *might be* well on your way > > > to being able to mount / read-only. > > > > And say goodbye to changing your password... > > ah...true, true. i did say might ;) > add /etc to the list, unless of course its a symlink to a > file on some r/w filesystem Any say goodbye to your system booting at all, as your system won't be able to find /etc/fstab Tom From owner-freebsd-hackers Tue Jul 2 12:00:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00534 for hackers-outgoing; Tue, 2 Jul 1996 12:00:37 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00516 for ; Tue, 2 Jul 1996 12:00:30 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id UAA08117; Tue, 2 Jul 1996 20:00:15 +0100 (BST) To: Developer cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Help V2.2 doesn't work In-reply-to: Your message of "Tue, 02 Jul 1996 15:47:32 BST." Date: Tue, 02 Jul 1996 20:00:14 +0100 Message-ID: <8114.836334014@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Developer wrote in message ID : > > I was wondering if anyone else has had any success in getting the new V2.2 > kernel to run on their PC.. V2,1 runs fine for me on a wide variety of > machines but V2.2 just resets right at the start before I even see any > devices being scanned??!! You mean the -current kernel? Yes, I have a machine here which can run 2.2 quite easily ... What sort of hardware are you using? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Tue Jul 2 12:03:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00830 for hackers-outgoing; Tue, 2 Jul 1996 12:03:54 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA00825 for ; Tue, 2 Jul 1996 12:03:52 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA08635; Tue, 2 Jul 1996 12:02:23 -0700 From: Terry Lambert Message-Id: <199607021902.MAA08635@phaeton.artisoft.com> Subject: Re: Spam lists To: batie@agora.rdrop.com (Alan Batie) Date: Tue, 2 Jul 1996 12:02:23 -0700 (MST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: from "Alan Batie" at Jul 1, 96 09:39:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > How about a "companies who have spammed our lists" area on the WWW > > page so we can know who not to buy from? > > See http://www.ip.net/BL/blacklist.html for a more comprehensive listing, > and a place to add such to... 1) It should be readily available to FreeBSD users in particular. 2) We should not condemn those which have not spammed our lists, only those which have. 3) I am less likely to look through a page with a "blacklist" on it that is unrelated to FreeBSD. I don't care if people spam where I can't see it. 4) Blacklists are tehnically illegal. I was only calling for a "people who have spammed our lists" list, and the "we" was the royal "we" -- I won't buy from them, and I will advise my friends not to buy from them, but it would not be a good idea to advise people not to buy from them on the WWW page, since that could be legally construed as restraint of trade. A list of spammers has no such provable negative connotations; I may be a wierdo who will buy from them because they have taken notice of FreeBSD, and bad publicity is better than none (for example). "We've been spammed! We're SOMEBODY!". I have no desire to engage of "http://www.ip.net/BL/blacklist.html" style restraint of trade tactics, only notification of list spamming, where the lists constitute a "select group"... which is perfectly legal, if all you do is identify what they did, and not what you recommend people do about it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 2 12:13:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01815 for hackers-outgoing; Tue, 2 Jul 1996 12:13:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01810; Tue, 2 Jul 1996 12:13:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA08661; Tue, 2 Jul 1996 12:11:46 -0700 From: Terry Lambert Message-Id: <199607021911.MAA08661@phaeton.artisoft.com> Subject: Re: Dual-booting FreeBSD and Windows95??? To: pechter@shell.monmouth.com (Bill/Carolyn Pechter) Date: Tue, 2 Jul 1996 12:11:46 -0700 (MST) Cc: gpalmer@FreeBSD.org, FreeBSD-hackers@FreeBSD.org In-Reply-To: <199607021125.HAA24901@shell.monmouth.com> from "Bill/Carolyn Pechter" at Jul 2, 96 07:25:13 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > It hasn't changed, no. I seem to remember several people offering to do > > MCA support over the last 2 odd years, but nothing has ever come of > > it. I would be very surpised if anything was done about MCA support > > in the next year or so, as it isn't very common and is becoming less so. > > > > Gary > > Unfortunately, this is so. I work for IBM now and there's a Ton of > 386's I'd be running FreeBSD on if I could get an idea of how to get > Token Ring support and Microchannel support working. But both are > way beyond me. > > The machines are cheap and surplus hardware internally (and just about the > same externally at every used hardware company... > > I hear there's folks with Linux up on microchannel and I've got a Compaq > running with Token Ring support under Linux now. I have been looking for a cheap used PS/2 with a sufficiently large disk for some time now, with no luck. It's not worth paying premium rates for something like this. If I was still in Utah, I'd have access to a number of PS/2 machines and a full "Networking Center of Excellence" -- including a token ring net and fully documented hardware. I've been looking for token ring hardware, but it seems a hub is required, and it's not worth $1500 to me to squelch complaints about what is, essentially, obsolete technology. I don't know of many hot programmers up there following my "generation"; the ones I do know are all doing simulation graphics on military contract now, so I don't even know who to contact about conning someone into working on it. 8-(. An MCA port using ABIOS would probably be no more difficult than the PC98 support already integrated into the tree. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 2 12:14:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01842 for hackers-outgoing; Tue, 2 Jul 1996 12:14:02 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01836; Tue, 2 Jul 1996 12:14:01 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199607021914.MAA01836@freefall.freebsd.org> Subject: Re: What is the best way to setup a drive To: tom@sdf.com (Tom Samplonius) Date: Tue, 2 Jul 1996 12:14:01 -0700 (PDT) Cc: jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jul 2, 96 11:35:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote: > > > On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > > > Tom Samplonius wrote: > > > > > > > > > On Tue, 2 Jul 1996, Jonathan M. Bresler wrote: > > > > > > > add a separate partition for /tmp and you *might be* well on your way > > > > to being able to mount / read-only. > > > > > > And say goodbye to changing your password... > > > > ah...true, true. i did say might ;) > > add /etc to the list, unless of course its a symlink to a > > file on some r/w filesystem > > Any say goodbye to your system booting at all, as your system won't be > able to find /etc/fstab hahahahhah. okay tom, i am going to let you get this one working please write up a section form the handbook when its done ;) jmb From owner-freebsd-hackers Tue Jul 2 12:15:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01987 for hackers-outgoing; Tue, 2 Jul 1996 12:15:53 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01978 for ; Tue, 2 Jul 1996 12:15:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA08675; Tue, 2 Jul 1996 12:13:03 -0700 From: Terry Lambert Message-Id: <199607021913.MAA08675@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Tue, 2 Jul 1996 12:13:03 -0700 (MST) Cc: jmb@freefall.freebsd.org, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers%freebsd.orgroot@friday.keanesea.com, hackers@FreeBSD.ORG In-Reply-To: <199607021639.LAA17375@brasil.moneng.mei.com> from "Joe Greco" at Jul 2, 96 11:39:22 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've yet to see an automated tool that sized things according to any > reasonable rules that I could find out. The Sun tool works halfway well, > but that's about it. IBM's JFS. But that's cheating, I suppose... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 2 12:16:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02068 for hackers-outgoing; Tue, 2 Jul 1996 12:16:38 -0700 (PDT) Received: from premise.CS.Berkeley.EDU (root@premise.CS.Berkeley.EDU [128.32.33.172]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA02059 for ; Tue, 2 Jul 1996 12:16:30 -0700 (PDT) Received: from premise.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by premise.CS.Berkeley.EDU (8.6.11/8.6.9) with ESMTP id MAA09791 for ; Tue, 2 Jul 1996 12:16:27 -0700 Message-Id: <199607021916.MAA09791@premise.CS.Berkeley.EDU> X-Mailer: exmh version 1.6.7 5/3/96 To: hackers@freebsd.org Subject: Re: Are you a programmer? Do you wear glasses? In-reply-to: Your message of "Tue, 02 Jul 1996 10:07:18 CDT." <199607021507.KAA17016@brasil.moneng.mei.com> From: bmah@cs.berkeley.edu (Bruce A. Mah) Reply-to: bmah@cs.berkeley.edu X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jul 1996 12:16:25 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Let me make one observation. One luser posts a single SPAM. Since then, I've seen at least half a dozen email messages from list subscribers about the SPAM, how to respond to it, how to prevent further recurrances, and so forth. Bruce. From owner-freebsd-hackers Tue Jul 2 12:24:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02581 for hackers-outgoing; Tue, 2 Jul 1996 12:24:07 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA02558 for ; Tue, 2 Jul 1996 12:24:01 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA07137; Tue, 2 Jul 1996 21:21:48 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA04089; Tue, 2 Jul 1996 21:21:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA12457; Tue, 2 Jul 1996 21:01:39 +0200 (MET DST) From: J Wunsch Message-Id: <199607021901.VAA12457@uriah.heep.sax.de> Subject: Re: aic glitch? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 2 Jul 1996 21:01:38 +0200 (MET DST) Cc: alexis@ww.net Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607021121.PAA04053@dawn.ww.net> from Alexis Yushin at "Jul 2, 96 03:21:31 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Alexis Yushin wrote: > I keep receiving the following (aic, Connor hard drive): > > scsi -f /dev/rsd0c -c "12 0 0 0 64 0" -i 64 "s8 z8 z16 z4" > > >SCIOCCOMMAND ioctl: Command accepted. > > host adapter status 2 > ^^^^^^^^^^^^^^^^^^^^^^^ > Why? Is it CHECK CONDITION or CONDITION MET? I'm afraid nobody except the aic.c file can give you an answer. The aic driver seems to be orphaned. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 2 12:53:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA04607 for hackers-outgoing; Tue, 2 Jul 1996 12:53:15 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA04595 for ; Tue, 2 Jul 1996 12:53:13 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id MAA18355; Tue, 2 Jul 1996 12:50:28 -0700 (PDT) Message-Id: <199607021950.MAA18355@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: Sujal Patel cc: "Christoph P. Kukulies" , ponds!rivers@dg-rtp.dg.com, freebsd-hackers@freefall.freebsd.org Subject: Re: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2.1-RELEASE?) In-reply-to: Your message of "Tue, 02 Jul 1996 13:22:54 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jul 1996 12:50:28 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Sujal Patel : > On Tue, 2 Jul 1996, Christoph P. Kukulies wrote: > > > While being at it: Is the SB PnP suitable for doing full duplex i/o (dma) > > like the GUS cards making it an alternate choice for using it with > > conferencing tools? (vat, etc.) > > This is not yet possible under FreeBSD, unless you use Amancio's TASD > distribution(?)... > > In think what I have over here is sound driver 3.5 + enhancements + patches. You may be able to make the SB PnP work in full duplex however the driver will have to be changed slightly to accomodate the SB PnP. Is my understanding that the SB 16 supports simultaneously 8 bit recording and 16 bit playback. Tnks, Amancio From owner-freebsd-hackers Tue Jul 2 13:47:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08628 for hackers-outgoing; Tue, 2 Jul 1996 13:47:07 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA08588; Tue, 2 Jul 1996 13:46:40 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id VAA02578; Tue, 2 Jul 1996 21:47:02 +0100 Date: Tue, 2 Jul 1996 21:47:01 +0100 (BST) From: Developer To: Gary Palmer cc: hackers@FreeBSD.ORG Subject: Re: Help V2.2 doesn't work In-Reply-To: <8114.836334014@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Gary Palmer wrote: > Developer wrote in message ID > : > > > > I was wondering if anyone else has had any success in getting the new V2.2 > > kernel to run on their PC.. V2,1 runs fine for me on a wide variety of > > machines but V2.2 just resets right at the start before I even see any > > devices being scanned??!! > > You mean the -current kernel? Yes, I have a machine here which can run > 2.2 quite easily ... What sort of hardware are you using? Hmm, a DX4x100Mzh, 16MB of memory, 1GB scsi hard drive (Which is already running V2.1), Enhanced IDE/IO card, Adapetc scsi card (VLB) and a Cirrius logic 1MB video card. Any ideas? Regards, Trefor S. From owner-freebsd-hackers Tue Jul 2 13:54:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09215 for hackers-outgoing; Tue, 2 Jul 1996 13:54:38 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09196 for ; Tue, 2 Jul 1996 13:54:08 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id VAA02669; Tue, 2 Jul 1996 21:53:24 +0100 Date: Tue, 2 Jul 1996 21:53:23 +0100 (BST) From: Developer To: Joe Greco cc: Mission Control , hackers@freebsd.org Subject: Re: What is the best way to setup a drive In-Reply-To: <199607021449.JAA16959@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Joe Greco wrote: > > I'm curios what the recomended > > drive setup is I have two hard > > drives a 540 and a 1.6 How would > > you divi up the space I will have > > about 55 Users to setup on it but > > none of them need much disk space > > because they are all just on it for > > mail. Well, my usual setup (On a 1GB drive) goes like this: / 100MB sd0a swap 100MB sd0b /usr 500MB sd0e /usr/homes 300MB sd0f So on the 540MB drive I would put maybe 150MB of swap and the rest as /usr/homes. Then make the 1.6GB drive somthing like: /usr 500MB /var 300MB or more if you plan to take a lot of news /usr/source 500MB (Use this for compiling kernels and packages) /store 300MB (This for storing .tgz files and backups). Ive found that 100MB of swap can be easily used if you are running netscape and a few compiling sessions on a fairly active system. Regards, Trefor S. From owner-freebsd-hackers Tue Jul 2 14:16:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00233 for hackers-outgoing; Tue, 2 Jul 1996 14:16:43 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA00215 for ; Tue, 2 Jul 1996 14:16:28 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA19222; Tue, 2 Jul 1996 23:14:42 +0200 Received: by uni4nn.iaf.nl with UUCP id AA07449 (5.67b/IDA-1.5); Tue, 2 Jul 1996 23:14:10 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA00973 (5.67b/IDA-1.5); Tue, 2 Jul 1996 22:12:10 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id TAA00621; Tue, 2 Jul 1996 19:05:04 +0200 From: Wilko Bulte Message-Id: <199607021705.TAA00621@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: Netscape is out of memory To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 2 Jul 1996 19:05:04 +0200 (MET DST) Cc: freebsd-hackers@freebsd.org, tam@cd.iidpwr.com In-Reply-To: <199607020705.JAA10604@uriah.heep.sax.de> from "J Wunsch" at Jul 2, 96 09:05:01 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > > As Tony Tam wrote: > > > The error message is "Netscape is out of memory. Try quitting some > > other applications or closing some windows." I got this error message as > > What about your swap usage? I assume you've got too few swap for > running a memory-pig like Netcrap. Hmm, not necessarily. I've seen it happen once on my own system (32 Mbyte RAM, 64 Mb swap, one user and plenty of swap free.) Netscape itself is weird.. Wilko _ ____________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jul 2 14:28:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08628 for hackers-outgoing; Tue, 2 Jul 1996 13:47:07 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA08588; Tue, 2 Jul 1996 13:46:40 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id VAA02578; Tue, 2 Jul 1996 21:47:02 +0100 Date: Tue, 2 Jul 1996 21:47:01 +0100 (BST) From: Developer To: Gary Palmer cc: hackers@FreeBSD.ORG Subject: Re: Help V2.2 doesn't work In-Reply-To: <8114.836334014@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Gary Palmer wrote: > Developer wrote in message ID > : > > > > I was wondering if anyone else has had any success in getting the new V2.2 > > kernel to run on their PC.. V2,1 runs fine for me on a wide variety of > > machines but V2.2 just resets right at the start before I even see any > > devices being scanned??!! > > You mean the -current kernel? Yes, I have a machine here which can run > 2.2 quite easily ... What sort of hardware are you using? Hmm, a DX4x100Mzh, 16MB of memory, 1GB scsi hard drive (Which is already running V2.1), Enhanced IDE/IO card, Adapetc scsi card (VLB) and a Cirrius logic 1MB video card. Any ideas? Regards, Trefor S. From owner-freebsd-hackers Tue Jul 2 14:29:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09215 for hackers-outgoing; Tue, 2 Jul 1996 13:54:38 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09196 for ; Tue, 2 Jul 1996 13:54:08 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id VAA02669; Tue, 2 Jul 1996 21:53:24 +0100 Date: Tue, 2 Jul 1996 21:53:23 +0100 (BST) From: Developer To: Joe Greco cc: Mission Control , hackers@freebsd.org Subject: Re: What is the best way to setup a drive In-Reply-To: <199607021449.JAA16959@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Joe Greco wrote: > > I'm curios what the recomended > > drive setup is I have two hard > > drives a 540 and a 1.6 How would > > you divi up the space I will have > > about 55 Users to setup on it but > > none of them need much disk space > > because they are all just on it for > > mail. Well, my usual setup (On a 1GB drive) goes like this: / 100MB sd0a swap 100MB sd0b /usr 500MB sd0e /usr/homes 300MB sd0f So on the 540MB drive I would put maybe 150MB of swap and the rest as /usr/homes. Then make the 1.6GB drive somthing like: /usr 500MB /var 300MB or more if you plan to take a lot of news /usr/source 500MB (Use this for compiling kernels and packages) /store 300MB (This for storing .tgz files and backups). Ive found that 100MB of swap can be easily used if you are running netscape and a few compiling sessions on a fairly active system. Regards, Trefor S. From owner-freebsd-hackers Tue Jul 2 14:47:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA02759 for hackers-outgoing; Tue, 2 Jul 1996 14:47:25 -0700 (PDT) Received: from ginger.vnet.net (root@ginger.vnet.net [166.82.1.69]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA02754; Tue, 2 Jul 1996 14:47:23 -0700 (PDT) Received: from vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.6.13/8.6.12) with SMTP id QAA23825; Tue, 2 Jul 1996 16:55:56 -0400 Received: from khan@vnet.net (artist.vnet.net) by vnet.net with SMTP id AA07964 (5.67b/IDA-1.5); Tue, 2 Jul 1996 17:47:14 -0400 From: khan Message-Id: X-Mailer: XFMail 0.3 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 In-Reply-To: <199607020214.WAA02976@lakes> Reply-To: khan@vnet.net Date: Tue, 02 Jul 1996 17:40:17 EDT To: Thomas David Rivers Subject: RE: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2 Cc: khan@vnet.net, freebsd-hackers@freefall.freebsd.org, lakes!rivers@freefall.freebsd.org Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Nope - still just get a locked-up 'cat' command... > > - Dave Rivers - OK let's back up .... did you MAKEDEV in the /dev.......yes...good ..but sometim es this does not work right and you need to make each one ---one at a time...like EX: mknod dsp0 c 30 3 mknod audio0 c 30 4 mknod audio1 c 30 20 etc.....then test it .....~Maybe~ Hope_so From owner-freebsd-hackers Tue Jul 2 14:58:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03553 for hackers-outgoing; Tue, 2 Jul 1996 14:58:57 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA03539 for ; Tue, 2 Jul 1996 14:58:52 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id WAA08431; Tue, 2 Jul 1996 22:54:54 +0100 (BST) To: "Jonathan M. Bresler" cc: tom@sdf.com (Tom Samplonius), jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: What is the best way to setup a drive In-reply-to: Your message of "Tue, 02 Jul 1996 10:51:44 PDT." <199607021751.KAA25573@freefall.freebsd.org> Date: Tue, 02 Jul 1996 22:54:53 +0100 Message-ID: <8429.836344493@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jonathan M. Bresler" wrote in message ID <199607021751.KAA25573@freefall.freebsd.org>: > ah...true, true. i did say might ;) > add /etc to the list, unless of course its a symlink to a > file on some r/w filesystem Which creates the interesting problem of how can init read /etc/rc if it's on another filesystem? :-) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Tue Jul 2 15:12:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04537 for hackers-outgoing; Tue, 2 Jul 1996 15:12:26 -0700 (PDT) Received: from pancake.remcomp.fr (root@pancake.remcomp.fr [194.51.30.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA04524 for ; Tue, 2 Jul 1996 15:12:14 -0700 (PDT) Received: from aida.aida.org (aida [128.127.10.1]) by aida.aida.org (8.7.5/8.7.3) with SMTP id UAA00538 for ; Mon, 1 Jul 1996 20:28:56 GMT Date: Mon, 1 Jul 1996 22:28:56 +0200 (MET DST) From: didier@aida.org To: hackers@freebsd.org Subject: FreeBSD 2.2-CURRENT (snapshot CDROM) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for this version of FreeBSD uncredibly fast. -- Didier Derny | Private FreeBSD 2.2-CURRENT Site Email: didier@aida.org | Microsoft Free Computer. Homepage: http://www.codix.fr/~dderny | AMD 5x86-160 on a ASUS PVI-486SP3 From owner-freebsd-hackers Tue Jul 2 18:03:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18666 for hackers-outgoing; Tue, 2 Jul 1996 18:03:53 -0700 (PDT) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18655; Tue, 2 Jul 1996 18:03:51 -0700 (PDT) From: Mike Pritchard Message-Id: <199607030103.SAA18655@freefall.freebsd.org> Subject: Re: bit 7 in filenames To: bde@zeta.org.au (Bruce Evans) Date: Tue, 2 Jul 1996 18:03:51 -0700 (PDT) Cc: hackers@FreeBSD.org, phk@FreeBSD.org In-Reply-To: <199606090548.PAA26171@godzilla.zeta.org.au> from "Bruce Evans" at Jun 9, 96 03:48:18 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (I know this is old, but I'm just now getting caught up on some very old e-mail that I wanted to respond to). I think that lite2 corrects some of this anachronisms. It also fixes some of the hardcoded constants in some of the man pages. E.g. instead of using "1024", it will specify "MAXPATHLEN". Bruce Evans wrote: > > > The symbolic link succeeds unless: > > > [ENOTDIR] > > A component of the name2 prefix is not a directory. > > > [EINVAL] Either name1 or name2 contains a character with the high-order > > bit set. > > >HUH ???? > > This anachronism is in most of the man pages for system calls that involve > path names. > > >Actually there should be an error return, if I try to make a filename > >that is illegal for the filesystem. > > >For instance > > create("/msdosfs/foo:bar") > >is an invalid name... > > It's not invalid for msdosfs :-). :-(. Neither is creat("/msdosfs/a2345678: > this is a very long not to mention invalid msdos path.name", 0666). > falsely advertises that _POSIX_NO_TRUNC is 1 (no-trunc for > _all_ supported file systems) and man pages misspell > pathconf("/mountpoint", _PC_NAME_MAX) as 255. > > Bruce > -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-hackers Tue Jul 2 18:04:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18742 for hackers-outgoing; Tue, 2 Jul 1996 18:04:25 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA18730 for ; Tue, 2 Jul 1996 18:04:23 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id VAA07636; Tue, 2 Jul 1996 21:04:07 -0400 Date: Tue, 2 Jul 1996 21:04:07 -0400 Message-Id: <199607030104.VAA07636@kropotkin.gnu.ai.mit.edu> To: jmb@freefall.freebsd.org CC: tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-reply-to: <199607021751.KAA25573@freefall.freebsd.org> (jmb@freefall.freebsd.org) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm shaving!! I'M SHAVING!! >>> add a separate partition for /tmp and you *might be* well on your way >>> to being able to mount / read-only. >> And say goodbye to changing your password... > ah...true, true. i did say might ;) > add /etc to the list, unless of course its a symlink to a > file on some r/w filesystem But how would you mount your filesystems at boot time? -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Tue Jul 2 18:09:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA19392 for hackers-outgoing; Tue, 2 Jul 1996 18:09:40 -0700 (PDT) Received: from eagle.ais.net (root@eagle.ais.net [199.0.154.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA19381 for ; Tue, 2 Jul 1996 18:09:38 -0700 (PDT) Received: by eagle.ais.net (Smail3.1.29.1 #18) id m0ubGRb-000VyVC; Tue, 2 Jul 96 20:09 CDT Message-Id: From: delerium@eagle.ais.net (Synaesthesia) Subject: Re: SIG's 11 and 6... To: walter@biostat.sph.unc.edu (Bruce Walter) Date: Tue, 2 Jul 1996 20:09:27 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: from "Bruce Walter" at Jul 2, 96 09:50:58 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [...] > HEAT! My pentium 120 was having the above problems. Switching out memory > would solve them for a day or two, but the problems would then start to > build up again. FINALLY I replaced the CPU fan and added a big waffle fan > in the front of the case and VOILA... No more SIG's for the last week. > Chances are that in the past the time involved in cracking the case and > swapping memory dropped the temp enough to alleviate the problem. I've got a Pentium 133 here running 2.2-960612-SNAP, and it too was experiencing more or less random Segmentation Faults, Bus Errors, and/or Illegal Instructions. This behavior persisted despite swapping SIMMs several times. I finally resolved this with a strange fix: though the CPU can run at 133MHz, I clocked it down to 120MHz via jumper settings on the motherboard. I haven't had any problems with it since. I wonder if my problem is actually heat-related as well? Reducing the CPU clock may simply cause the chip to run cooler. Anyone else have similar troubles, or other ideas? -- delerium@ais.net From owner-freebsd-hackers Tue Jul 2 19:02:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA26568 for hackers-outgoing; Tue, 2 Jul 1996 19:02:35 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA26552 for ; Tue, 2 Jul 1996 19:02:29 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id WAA07812; Tue, 2 Jul 1996 22:02:21 -0400 Date: Tue, 2 Jul 1996 22:02:21 -0400 Message-Id: <199607030202.WAA07812@kropotkin.gnu.ai.mit.edu> To: delerium@eagle.ais.net CC: walter@biostat.sph.unc.edu, hackers@FreeBSD.ORG In-reply-to: (delerium@eagle.ais.net) Subject: Re: SIG's 11 and 6... From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk HUMAN REPLICAS are inserted into VATS of NUTRITIONAL YEAST... > I wonder if my problem is actually heat-related as well? Reducing > the CPU clock may simply cause the chip to run cooler. Anyone > else have similar troubles, or other ideas? It is the case that reducing the clock causes the chip to run cooler. In fact, the way that Intel (and others) decide on the speed of a given chip is by clocking one in the batch higher and higher until it fries, drop that speed by x%, and stamp it on. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Tue Jul 2 19:24:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA29167 for hackers-outgoing; Tue, 2 Jul 1996 19:24:34 -0700 (PDT) Received: from csgrad.cs.vt.edu (csgrad.cs.vt.edu [128.173.41.41]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA29153 for ; Tue, 2 Jul 1996 19:24:28 -0700 (PDT) Received: by csgrad.cs.vt.edu; (5.65v3.2/1.1.8.2/19Sep94-1023AM) id AA23823; Tue, 2 Jul 1996 22:24:20 -0400 Date: Tue, 2 Jul 1996 22:24:20 -0400 From: Tommy Johnson Message-Id: <9607030224.AA23823@csgrad.cs.vt.edu> To: delerium@eagle.ais.net, walter@biostat.sph.unc.edu Subject: Re: SIG's 11 and 6... Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk delerium@ais.net said: >[...] >> HEAT! My pentium 120 was having the above problems. Switching out memory >> would solve them for a day or two, but the problems would then start to [...] > >I've got a Pentium 133 here running 2.2-960612-SNAP, and it too was >experiencing more or less random Segmentation Faults, Bus Errors, >and/or Illegal Instructions. This behavior persisted despite swapping >SIMMs several times. I finally resolved this with a strange fix: >though the CPU can run at 133MHz, I clocked it down to 120MHz via jumper >settings on the motherboard. I haven't had any problems with it since. I have a 586-100 (Well, OK so it says pentium...). When I first got it, I was doing a burn in test, compiling about 6 kernels in parallel. I too kept getting SIG 11s. So I doublechecked all the jumpers and noticed that it was jumpered for 133MHz. When I set it to 100 MHz, the strange signals stopped, and the machine has been up ever since (25 days uptime sofar). For the record: Tyan S1462 tempest II dual 586 motherboard (only one 100MHz CPU right now), 512K L2 cache, Adaptec 2940, SMC DC21041 10Mb ethernet, 16MB ram, hercules video board, running FreeBSD 2.1.0-Release. The CPU is: Origin = "GenuineIntel" Id = 0x526 Stepping=6 >I wonder if my problem is actually heat-related as well? Reducing the >CPU clock may simply cause the chip to run cooler. Anyone else have >similar troubles, or other ideas? My case has two fans, I don't think I had any heat problems. -Tom "this isn't happening... this isn't happening..." a grey alien, X Files tjohnson@csgrad.cs.vt.edu "My other computer ALSO runs unix." -me <*> http://csgrad.cs.vt.edu/~tjohnson/ Message and signature (c) 1996 Tommy O. Johnson, all rights reserved From owner-freebsd-hackers Tue Jul 2 20:31:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09216 for hackers-outgoing; Tue, 2 Jul 1996 20:31:42 -0700 (PDT) Received: from eagle.ais.net (root@eagle.ais.net [199.0.154.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA09203 for ; Tue, 2 Jul 1996 20:31:38 -0700 (PDT) Received: by eagle.ais.net (Smail3.1.29.1 #18) id m0ubIf7-000W29C; Tue, 2 Jul 96 22:31 CDT Message-Id: From: delerium@eagle.ais.net (Synaesthesia) Subject: External cache weirdness To: hackers@FreeBSD.ORG Date: Tue, 2 Jul 1996 22:31:33 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've recently picked up a 512k pipeline burst cache module for my P133/Intel Triton system. Plugging this into the motherboard results in some very interesting if unsettling behavior when the system tries to boot. First off, with the cache enabled, the post-POST BIOS information screen misidentifies the size of my 1707MB IBM IDE drive as a drive with more or less random incorrect (in some cases inconceivable--25GB?) size. This is strange, because when I actually go into the CMOS setup, the drive is identified consistently as 1707MB without problem. Then the "Boot: " prompt appears. Hitting enter at this point, or allowing things to time out and begin the kernel load, results in the video shifting wildly out of whack such that the text on the screen jumps to strange positions. The system then stops cold for a few seconds, and promptly reboots. If I disable the external cache, none of the above symptoms occur. Ideas? Pentium-S 133MHz (what's the significance of the ``S'', anyway?) Intel Triton chipset (EIDE, PCI) 1.7GB IBM IDE drive 32mb 60ns EDO RAM (2 16mb 72-pin SIMMs) FreeBSD 2.2-960612-SNAP -- delerium@ais.net From owner-freebsd-hackers Tue Jul 2 22:39:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA04065 for hackers-outgoing; Tue, 2 Jul 1996 22:39:38 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA04038 for ; Tue, 2 Jul 1996 22:39:33 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA10663; Tue, 2 Jul 1996 22:39:05 -0700 (PDT) Message-Id: <199607030539.WAA10663@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: delerium@eagle.ais.net (Synaesthesia) cc: walter@biostat.sph.unc.edu (Bruce Walter), hackers@freebsd.org Subject: Re: SIG's 11 and 6... In-reply-to: Your message of Tue, 02 Jul 96 20:09:27 -0500. Date: Tue, 02 Jul 1996 22:39:05 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> HEAT! My pentium 120 was having the above problems. Switching out memory >> would solve them for a day or two, but the problems would then start to >> build up again. FINALLY I replaced the CPU fan and added a big waffle fan >> in the front of the case and VOILA... No more SIG's for the last week. >I've got a Pentium 133 here running 2.2-960612-SNAP, and it too was >experiencing more or less random Segmentation Faults, Bus Errors, >and/or Illegal Instructions. This behavior persisted despite swapping >SIMMs several times. I finally resolved this with a strange fix: >though the CPU can run at 133MHz, I clocked it down to 120MHz via jumper >settings on the motherboard. I haven't had any problems with it since. I would invest in a better heat sink and fan. You might also want to get some heat sink compound to make a more uniform heat transfer area between the chip surface and the heat sink surface. You can pick up heat sink compound at any Radio Shack, in a little blue and white tube. Well worth the couple bucks invested. >I wonder if my problem is actually heat-related as well? Reducing the >CPU clock may simply cause the chip to run cooler. Anyone else have >similar troubles, or other ideas? It's actually verified by several very fundamental laws of physics that it will run cooler. :-) But, since the chip is rated for 133MHz, it sounds like it's getting _too_ _hot_, not because of the clock speed, but because the cooling aparatus isn't doing an adequate job bring the chip down to operational levels. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jul 2 22:56:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA06613 for hackers-outgoing; Tue, 2 Jul 1996 22:56:16 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA06601 for ; Tue, 2 Jul 1996 22:56:12 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA10721; Tue, 2 Jul 1996 22:56:05 -0700 (PDT) Message-Id: <199607030556.WAA10721@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: delerium@eagle.ais.net (Synaesthesia) cc: hackers@freebsd.org Subject: Re: External cache weirdness In-reply-to: Your message of Tue, 02 Jul 96 22:31:33 -0500. Date: Tue, 02 Jul 1996 22:56:05 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've recently picked up a 512k pipeline burst cache module for my >P133/Intel Triton system. Plugging this into the motherboard results >in some very interesting if unsettling behavior when the system tries >to boot. [...] >If I disable the external cache, none of the above symptoms occur. >Ideas? Your COAST module is incompatible with your motherboard? Seriously, I've heard that not "just any" COAST module will work with "just any" motherboard. Apparently ASUS boards are pretty picky about the quality of COAST module you insert in them, and people generally recommend that you only put ASUS COASTS in an ASUS board, because they're known to work together. Evidently there are lots of "marginal" COAST modules floating around out there. Maybe you should send it back and insist on a name-brand module known to work with your specific motherboard. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jul 2 23:24:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA08911 for hackers-outgoing; Tue, 2 Jul 1996 23:24:49 -0700 (PDT) Received: from nike.efn.org (gurney_j@garcia.efn.org [198.68.17.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA08903 for ; Tue, 2 Jul 1996 23:24:45 -0700 (PDT) Received: from localhost (localhost.efn.org [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id XAA09311; Tue, 2 Jul 1996 23:24:56 -0700 (PDT) Date: Tue, 2 Jul 1996 23:24:53 -0700 (PDT) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Synaesthesia cc: Bruce Walter , hackers@FreeBSD.ORG Subject: Re: SIG's 11 and 6... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Synaesthesia wrote: > [...] > > HEAT! My pentium 120 was having the above problems. Switching out memory > > would solve them for a day or two, but the problems would then start to > > build up again. FINALLY I replaced the CPU fan and added a big waffle fan > > in the front of the case and VOILA... No more SIG's for the last week. > > Chances are that in the past the time involved in cracking the case and > > swapping memory dropped the temp enough to alleviate the problem. > > I've got a Pentium 133 here running 2.2-960612-SNAP, and it too was > experiencing more or less random Segmentation Faults, Bus Errors, > and/or Illegal Instructions. This behavior persisted despite swapping > SIMMs several times. I finally resolved this with a strange fix: > though the CPU can run at 133MHz, I clocked it down to 120MHz via jumper > settings on the motherboard. I haven't had any problems with it since. > > I wonder if my problem is actually heat-related as well? Reducing the > CPU clock may simply cause the chip to run cooler. Anyone else have > similar troubles, or other ideas? I had for a while over clocked a 486/33 to 40mhz... when the fan on the cpu stopped working I would get sig6s during a compile... as soon as I put a fan back on the chip it all went away... also... it could be the motherboard... I had a vlb motherboard running an amd5x86/133 and it just wouldn't recoginize memory and the memory it would recognize was "bad" as far as freebsd was conserned... i.e. bad data was being writen to the disk... TTYL.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-hackers Tue Jul 2 23:26:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA09104 for hackers-outgoing; Tue, 2 Jul 1996 23:26:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA09099 for ; Tue, 2 Jul 1996 23:26:27 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id XAA09969; Tue, 2 Jul 1996 23:21:10 -0700 From: Terry Lambert Message-Id: <199607030621.XAA09969@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: joelh@gnu.ai.mit.edu Date: Tue, 2 Jul 1996 23:21:09 -0700 (MST) Cc: jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.org In-Reply-To: <199607030104.VAA07636@kropotkin.gnu.ai.mit.edu> from "Joel Ray Holveck" at Jul 2, 96 09:04:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > But how would you mount your filesystems at boot time? Long answer: The device probe will call devfs_register_dev() on the device. The devfs_register_dev() will look for physical-to-logical and logical-to-logical device translations... like a DOS partition table or a BSD disklabel. When a translation is found, then devfs_register_dev() will call devfs_claim_logical_dev() on the logical area, calling into the *-to-logical driver. The physical-to-logical and logical-to-logical device drivers will call devfs_register_dev() on each one of the sub devices. When no physical-to-logical or logical-to-logical device drivers claim a given device (ie: it is a terminal device), then the devfs_register_dev() (which has not yet returned) will call devfs_mount_dev(). The devfs_mount_dev() will call each file systems xxx_mount() as if it were mounting a root volume to establish a vnode for the root of the file system. Mounts will be inserted into the fs hierarchy post-facto by mount-point mapping of the vnodes according to the content of the fstab. Short answer: easily Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 01:17:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16730 for hackers-outgoing; Wed, 3 Jul 1996 01:17:00 -0700 (PDT) Received: from ns.pa-consulting.com (ns.pa-consulting.com [193.118.224.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA16721 for ; Wed, 3 Jul 1996 01:16:55 -0700 (PDT) Received: from SMTPGATE.PA-CONSULTING.COM by ns.pa-consulting.com (8.6.4) id JAA28114; Wed, 3 Jul 1996 09:25:56 +0100 Received: by SMTPGATE.PA-CONSULTING.COM with Microsoft Mail id <31DA9EFA@SMTPGATE.PA-CONSULTING.COM>; Wed, 03 Jul 96 09:25:30 PDT From: Duncan Barclay To: freebsd-hackers Subject: Re: SIG's 11 and 6... Date: Wed, 03 Jul 96 09:10:00 PDT Message-ID: <31DA9EFA@SMTPGATE.PA-CONSULTING.COM> Encoding: 39 TEXT X-Mailer: Microsoft Mail V3.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Although not on FreeBSD, I have seen similar odd crashes on a high end petium box which was shipped without a CPU fan. Putting one on solved the problem, again it was found that running the box with the lid off helped before the fan went on. Duncan ---------- From: owner-freebsd-hackers To: walter Cc: hackers Subject: Re: SIG's 11 and 6... Date: 02 July 1996 20:09 [...] > HEAT! My pentium 120 was having the above problems. Switching out memory > would solve them for a day or two, but the problems would then start to > build up again. FINALLY I replaced the CPU fan and added a big waffle fan > in the front of the case and VOILA... No more SIG's for the last week. > Chances are that in the past the time involved in cracking the case and > swapping memory dropped the temp enough to alleviate the problem. I've got a Pentium 133 here running 2.2-960612-SNAP, and it too was experiencing more or less random Segmentation Faults, Bus Errors, and/or Illegal Instructions. This behavior persisted despite swapping SIMMs several times. I finally resolved this with a strange fix: though the CPU can run at 133MHz, I clocked it down to 120MHz via jumper settings on the motherboard. I haven't had any problems with it since. I wonder if my problem is actually heat-related as well? Reducing the CPU clock may simply cause the chip to run cooler. Anyone else have similar troubles, or other ideas? -- delerium@ais.net From owner-freebsd-hackers Wed Jul 3 05:24:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA03876 for hackers-outgoing; Wed, 3 Jul 1996 05:24:56 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA03871 for ; Wed, 3 Jul 1996 05:24:52 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.12/1.53) id OAA12279; Wed, 3 Jul 1996 14:24:49 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199607031224.OAA12279@gvr.win.tue.nl> Subject: ntp question To: freebsd-hackers@freebsd.org Date: Wed, 3 Jul 1996 14:24:49 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When reading the docs for ntp, the stability of the clock should drop to about 0.1 ppm after some time. There even is a kernel variable counting the time that the stability is less then 25 ppm. However, when I look at my system, running xntpd the way it has been setup in rc, I get the following: (the system is up for 12 days) xntpdc> sysinfo system peer: ntp0.NL.net system peer mode: client leap indicator: 00 stratum: 2 precision: -18 root distance: 0.06630 s root dispersion: 0.05202 s reference ID: [193.78.241.12] reference time: b584e376.989e4000 Wed, Jul 3 1996 14:17:58.596 system flags: pll monitor stats frequency: 0.000 ppm stability: 78.071 ppm broadcastdelay: 0.003906 s authdelay: 0.000122 s Question: what is wromng? I thought I did not have to manually use tickadj... -Guido From owner-freebsd-hackers Wed Jul 3 06:11:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA05788 for hackers-outgoing; Wed, 3 Jul 1996 06:11:47 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA05781 for ; Wed, 3 Jul 1996 06:11:45 -0700 (PDT) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.7.4/8.6.12) with SMTP id JAA15975 for ; Wed, 3 Jul 1996 09:11:43 -0400 (EDT) Message-Id: <199607031311.JAA15975@ns2.harborcom.net> Comments: Authenticated sender is From: "Bradley Dunn" Organization: Harbor Communications To: hackers@freebsd.org Date: Wed, 3 Jul 1996 09:06:25 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: async flag to mount(8) Reply-to: dunn@harborcom.net Priority: normal X-mailer: Pegasus Mail for Win32 (v2.31) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone ever had the stomach to mount a fs async? What have been your experiences? Bradley Dunn Harbor Communications From owner-freebsd-hackers Wed Jul 3 06:17:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA06671 for hackers-outgoing; Wed, 3 Jul 1996 06:17:04 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA06664 for ; Wed, 3 Jul 1996 06:17:02 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ac28156; 3 Jul 96 14:16 +0100 Received: from longacre.demon.co.uk ([158.152.156.24]) by relay-3.mail.demon.net id aa25552; 3 Jul 96 14:12 +0100 From: Michael Searle Message-ID: To: hackers@freefall.freebsd.org Subject: Re: Sound Blaster PNP - just how to do it (using Sujal's PNP & 2 References: <199607021445.HAA12182@freefall.freebsd.org> Date: Wed, 03 Jul 1996 11:34:31 BST X-Mailer: Offlite 0.09 / Termite Internet for Acorn RISC OS Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ponds!rivers@dg-rtp.dg.com wrote: >> just for a test to see if you are get sound try this >> cat ?.au > /dev/dsp0 > Nope - still just get a locked-up 'cat' command... My SB16 isn't PNP, but when I do this (by 'cat' or 'cp'), I get the sound OK and then the command locks up. Any ideas? -- Michael Searle - searle@longacre.demon.co.uk From owner-freebsd-hackers Wed Jul 3 06:36:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07732 for hackers-outgoing; Wed, 3 Jul 1996 06:36:28 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07726 for ; Wed, 3 Jul 1996 06:36:26 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id IAA23553 for ; Wed, 3 Jul 1996 08:37:38 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id IAA23547 for ; Wed, 3 Jul 1996 08:37:36 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id IAA08875; Wed, 3 Jul 1996 08:39:17 -0500 (CDT) Date: Wed, 3 Jul 1996 08:39:17 -0500 (CDT) Message-Id: <199607031339.IAA08875@fa.tdktca.com> From: Alex Nash To: dunn@harborcom.net Cc: hackers@freebsd.org Subject: async flag to mount(8) Reply-to: alex@fa.tdktca.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone ever had the stomach to mount a fs async? What have been > your experiences? At the risk of experiencing Terry's wrath :), async is very useful, and under *some* scenarios (like rm -rf), very fast. I think (almost) everyone agrees that it's risky, but for filesystems such as /tmp one really shouldn't care. Alex From owner-freebsd-hackers Wed Jul 3 07:17:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA09524 for hackers-outgoing; Wed, 3 Jul 1996 07:17:39 -0700 (PDT) Received: from watt.cae.uwm.edu (hench@watt.cae.uwm.edu [129.89.55.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA09512 for ; Wed, 3 Jul 1996 07:17:37 -0700 (PDT) Received: (from hench@localhost) by watt.cae.uwm.edu (8.6.12/8.6.12) id JAA22545; Wed, 3 Jul 1996 09:17:35 -0500 From: Mike Hench Message-Id: <199607031417.JAA22545@watt.cae.uwm.edu> Subject: Re: async flag to mount(8) To: dunn@harborcom.net Date: Wed, 3 Jul 1996 09:17:34 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199607031311.JAA15975@ns2.harborcom.net> from "Bradley Dunn" at Jul 3, 96 09:06:25 am X-Mailer: ELM [version 2.4 PL21] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Has anyone ever had the stomach to mount a fs async? What have been > your experiences? > > Bradley Dunn > Harbor Communications > do it all the time. even whilst kernel hacking (read random HARD crashes) havent had a nasty problem yet :-) YOUR MILAGE MAY OF COURSE VARY mike hench hench@cae.uwm.edu From owner-freebsd-hackers Wed Jul 3 08:38:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17584 for hackers-outgoing; Wed, 3 Jul 1996 08:38:18 -0700 (PDT) Received: from p54c.spnet.com (p54c.spnet.com [204.156.130.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17579 for ; Wed, 3 Jul 1996 08:38:13 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by p54c.spnet.com (8.7.5/8.6.9) with SMTP id IAA08333; Wed, 3 Jul 1996 08:38:10 -0700 (PDT) Message-Id: <199607031538.IAA08333@p54c.spnet.com> X-Authentication-Warning: p54c.spnet.com: Host localhost [127.0.0.1] didn't use HELO protocol To: hackers@freebsd.org Cc: elh_fbsd@spnet.com Subject: Re: SIG's 11 and 6... In-reply-to: Your message of "Tue, 02 Jul 1996 20:09:27 CDT." Date: Wed, 03 Jul 1996 08:38:10 -0700 From: Ed Hudson Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [...] > HEAT! My pentium 120 was having the above problems. Switching out memory > would solve them for a day or two, but the problems would then start to > build up again. FINALLY I replaced the CPU fan and added a big waffle fan > in the front of the case and VOILA... No more SIG's for the last week. > Chances are that in the past the time involved in cracking the case and howdy. simple cmos transistor circuits have 'speed' variation of order t**-1.5 (t absolute). 'weak' circuits (eg rams) can have much larger variation with temperature, and two chips interacting with each other at a fixed cycle time can see their variations add. if you have a hardware bios or jumpers with tuneable cache/memory/bus speeds and you 'tune' them on a cold day you can easily get into trouble on a nice warm summer day - a 20deg f (11deg k) ambient temperature variation alone can affect peak operating speed by 10-20% easily. backing off on speed (this is not always cpu hz, but sometimes memory/cache clock cycles) is a very rational check for hardware timing problems - establish functionality first, then optimize speed. if you try BLOCKING your input air ducts for an hour or two (a less traumatic way of making things warmer than removing the cpu fan), you may see the problems get worse. (of course, don't do this on a system with ir-recoverable data! back it up first. beware: i've had disks go into thermal shutdown and destroy data, and have seen power supplies die and kill hardware when thermally overloaded). complex, multi-tasking operating systems can stress many paths in a chip/system not exercised by dos systems (less true with windows 95). in the old days unix used to break many machines that ran dos happily. an analogous circumstance perhaps exists today with speed paths (i never run dos or windows, thanks to you folks, so i'm not certain about their crash rates). -elh (former cpu/ram designer). From owner-freebsd-hackers Wed Jul 3 09:21:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19918 for hackers-outgoing; Wed, 3 Jul 1996 09:21:54 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19913 for ; Wed, 3 Jul 1996 09:21:50 -0700 (PDT) Received: (from mark@localhost) by scooter.quickweb.com (8.7.5/8.6.12) id MAA21903; Wed, 3 Jul 1996 12:14:55 -0400 (EDT) Date: Wed, 3 Jul 1996 12:14:55 -0400 (EDT) From: Mark Mayo To: Tony Tam cc: hackers@freebsd.org Subject: Re: Netscape is out of memory In-Reply-To: <96Jul2.103531pdt.15363@mail.iidpwr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Tony Tam wrote: > > J Wunsch wrote: > > > > As Tony Tam wrote: > > > > > The error message is "Netscape is out of memory. Try quitting some > > > other applications or closing some windows." I got this error message as > > > > What about your swap usage? I assume you've got too few swap for > > running a memory-pig like Netcrap. > > > > Well, as a matter of fact, I have 128M byte of swap space. > > I have some new discovery. That is Netscape Ver. 2.0 can send mail with > FreeBSD-2.0.5 RELEASE. By the way, this mail is sent by the above box. > > But Netscape Ver. 2.0 doesn't work with FreeBSD 2.1.0-RELEASE. I move the > same version of netscape to the 2.1.0 box. As soon as I hit the send mail > button, I got the same error message. Since I am using the same version of > X-Windows 3.1.2 in both RELEASEs, I am suspecting the "out-of-memory" problem > is causing by the operating system. > > Any idea? Hackers. I run Netscape 2.02 on FreeBSD 2.1R just fine. Did you follow the README instructions? There are a couple symbolic links you must setup into X11R6 to get FreeBSD to run it fine... Make sure you are running 2.02 - 2.0 had some bugs for me. Just for the record, I run it on a 486 with 16MB of RAM and only 65MB of swap... no memory problems at all.. I use pop for sending mail with Netscape. -Mark :%t$sig -- Oops, thought I was in vi.. ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- > > Tony Tam > From owner-freebsd-hackers Wed Jul 3 11:31:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08105 for hackers-outgoing; Wed, 3 Jul 1996 11:31:39 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08089 for ; Wed, 3 Jul 1996 11:31:36 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id NAA00426 for ; Wed, 3 Jul 1996 13:32:44 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id NAA00418 for ; Wed, 3 Jul 1996 13:32:44 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id NAA11349; Wed, 3 Jul 1996 13:34:19 -0500 (CDT) Date: Wed, 3 Jul 1996 13:34:19 -0500 (CDT) From: Alex Nash To: Terry Lambert cc: dunn@harborcom.net, hackers@freebsd.org Subject: Re: async flag to mount(8) In-Reply-To: <199607031826.LAA10899@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Jul 1996, Terry Lambert wrote: > Matt Day (next cubicle over from mine) has implemented soft updates, > though without some of my FS changes, they can not be integrated > into FreeBSD. > > An FS using soft updates operates within ~5% of memory speed, according > to the Ganger/Patt paper from the University of Michigan. > > This is faster than pure async because of write gathering during the > soft update timer period. > > Async sucks. Get over it. So async only sucks *when* we get your patches. I'm sure Poul can't wait! :) Alex From owner-freebsd-hackers Wed Jul 3 11:32:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08304 for hackers-outgoing; Wed, 3 Jul 1996 11:32:44 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA08289 for ; Wed, 3 Jul 1996 11:32:42 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA10899; Wed, 3 Jul 1996 11:26:01 -0700 From: Terry Lambert Message-Id: <199607031826.LAA10899@phaeton.artisoft.com> Subject: Re: async flag to mount(8) To: alex@fa.tdktca.com Date: Wed, 3 Jul 1996 11:26:01 -0700 (MST) Cc: dunn@harborcom.net, hackers@freebsd.org In-Reply-To: <199607031339.IAA08875@fa.tdktca.com> from "Alex Nash" at Jul 3, 96 08:39:17 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Has anyone ever had the stomach to mount a fs async? What have been > > your experiences? > > At the risk of experiencing Terry's wrath :), async is very useful, > and under *some* scenarios (like rm -rf), very fast. I think (almost) > everyone agrees that it's risky, but for filesystems such as /tmp one > really shouldn't care. Matt Day (next cubicle over from mine) has implemented soft updates, though without some of my FS changes, they can not be integrated into FreeBSD. An FS using soft updates operates within ~5% of memory speed, according to the Ganger/Patt paper from the University of Michigan. This is faster than pure async because of write gathering during the soft update timer period. Async sucks. Get over it. It is only useful until soft updates are integrated, and arguably a more dangerous cure than the disease even before that time. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 11:36:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08982 for hackers-outgoing; Wed, 3 Jul 1996 11:36:03 -0700 (PDT) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08929 for ; Wed, 3 Jul 1996 11:35:58 -0700 (PDT) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.6.12) with SMTP id LAA23355 for ; Wed, 3 Jul 1996 11:36:53 -0700 (PDT) Date: Wed, 3 Jul 1996 11:36:53 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Is there a real live actual working deluser script? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Even if it's rudimentary? I did a search on -hackers, and there's lots of talk about it, and about how complicated it would be, and on and on, but no actual script, and I don't see a port or a package. Anyone? From owner-freebsd-hackers Wed Jul 3 12:18:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14244 for hackers-outgoing; Wed, 3 Jul 1996 12:18:45 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA14235 for ; Wed, 3 Jul 1996 12:18:40 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ab15624; 3 Jul 96 20:18 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa00951; 3 Jul 96 20:17 +0100 Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id LAA00977; Wed, 3 Jul 1996 11:08:07 GMT Date: Wed, 3 Jul 1996 11:08:07 GMT Message-Id: <199607031108.LAA00977@jraynard.demon.co.uk> From: James Raynard To: delerium@eagle.ais.net CC: hackers@freebsd.org In-reply-to: (delerium@eagle.ais.net) Subject: Re: External cache weirdness Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've recently picked up a 512k pipeline burst cache module for my > P133/Intel Triton system. Plugging this into the motherboard results > in some very interesting if unsettling behavior when the system tries > to boot. There seem to be a lot of hardware-related discussions suddenly appearing in -hackers. Could this be the reason? [from Majordomo's reply to a 'list' command] freebsd-fs Filesystems freebsd-hackers Hardware issues ^^^^^^^^ freebsd-hackers-digest digest of Technical discussions mailing list freebsd-hardware General discussion of FreeBSD hardware As freebsd-hackers is not exactly a low-volume list, could anyone wishing to discuss hardware do so on freebsd-hardware? Thanks! -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk http://www.freebsd.org/~jraynard/ From owner-freebsd-hackers Wed Jul 3 12:48:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19140 for hackers-outgoing; Wed, 3 Jul 1996 12:48:14 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19133 for ; Wed, 3 Jul 1996 12:48:12 -0700 (PDT) Received: from orion.webspan.net (scanner@orion.webspan.net [206.154.70.41]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id PAA13654; Wed, 3 Jul 1996 15:48:02 -0400 (EDT) Date: Wed, 3 Jul 1996 15:48:02 -0400 (EDT) From: Scanner To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Is there a real live actual working deluser script? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Jul 1996, Jaye Mathisen wrote: > > > Even if it's rudimentary? I did a search on -hackers, and there's lots of > talk about it, and about how complicated it would be, and on and on, but > no actual script, and I don't see a port or a package. Here is one that is like 2 lines mine and the rest gary's :) Mine started out simeple as 4 lines. But under use of those less unix knowledable it went haywire. So it was re-written all but 2 lines. It works pretty good. Hope it does the job for you. -------CUT HERE-------------- #!/bin/sh if [ $# != 1 ]; then echo "Please run as $0 " exit 1 fi LUSER=$1 PASSWD=`egrep ^$1: /etc/passwd` if [ -z "$PASSWD" ]; then echo "No such user \"$LUSER\". Aborting." exit 1 fi GID=`echo $PASSWD | awk -F : ' { print $4 } '` if [ $GID != "1001" ]; then echo "\"$LUSER\" is not in group 1001 (users). Aborting." exit 1 fi echo "Removing $LUSER's files" rm -r /home/$1 rm /var/mail/$1 rm /var/mail/.$1.pop vipw ----------CUT HERE------------- -- ===================================| Webspan Inc., ISP Division. FreeBSD 2.1.0 is available now! | Phone: 908-367-8030 ext. 126 -----------------------------------| 500 West Kennedy Blvd., Lakewood, NJ-08701 Turning PCs into Workstations | E-Mail: scanner@webspan.net http://www.freebsd.org | SysAdmin / Network Engineer / Security ===================================| Member BSDNET team! http://www.bsdnet.org From owner-freebsd-hackers Wed Jul 3 13:00:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20835 for hackers-outgoing; Wed, 3 Jul 1996 13:00:57 -0700 (PDT) Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA20800; Wed, 3 Jul 1996 13:00:48 -0700 (PDT) From: mikebo@tellabs.com Received: from sunc210.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0ubY5w-0004fYC; Wed, 3 Jul 96 15:00 CDT Received: by sunc210.tellabs.com (SMI-8.6/1.9) id OAA13711; Wed, 3 Jul 1996 14:59:42 -0500 Message-Id: <199607031959.OAA13711@sunc210.tellabs.com> Subject: 2.1-960627-SNAP: YP problem To: bugs@freebsd.org Date: Wed, 3 Jul 1996 14:59:41 -0500 (CDT) Cc: hackers@freebsd.org, mikebo (Mike Borowiec) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings - I believe a bug has been introduced into the 2.1-960627-SNAP YP code. Previously, I had been able to use NIS netgroups in the password file: +@mygroup::::::::: The FreeBSD client is bound to a SunOS 4.1.x server. When I attempt to login, FreeBSD attempts : NIS: ----- Network Information Service ----- NIS: Proc = 4 (Return first key-value pair in map) NIS: Domain = mydomain NIS: Map = master.passwd.byname Of course, my Sun NIS domain has no such map "master.passwd.byname", and that's the end of that. The FreeBSD client goes on to try and get the passwd.byname entry for my login, which succeeds. Nevertheless, the login is refused. Here is a high-level packet trace: 1 0.00000 toybox -> sunc NIS C FIRST 2 0.01581 sunc -> toybox NIS R FIRST No such map 3 0.00321 toybox -> sunc NIS C MATCH mikebo in passwd.byname 4 0.01115 sunc -> toybox NIS R MATCH OK If I take the SunOS map entry from my account, and massage it to fit the format of the FreeBSD vipw, I am able to login just fine. This means that the password encryption and comparison is working. (Yes, DES is installed and working). I really need netgroup security. Am I doing something wrong? Is anyone else using NIS netgroup security successfully with this SNAP? - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 3 13:26:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22436 for hackers-outgoing; Wed, 3 Jul 1996 13:26:21 -0700 (PDT) Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22410; Wed, 3 Jul 1996 13:26:15 -0700 (PDT) From: mikebo@tellabs.com Received: from sunc210.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0ubYUa-0004fOC; Wed, 3 Jul 96 15:25 CDT Received: by sunc210.tellabs.com (SMI-8.6/1.9) id PAA13743; Wed, 3 Jul 1996 15:25:09 -0500 Message-Id: <199607032025.PAA13743@sunc210.tellabs.com> Subject: 2.1-960627-SNAP: YP problem To: bugs@freebsd.org Date: Wed, 3 Jul 1996 15:25:09 -0500 (CDT) Cc: hackers@freebsd.org, mikebo (Mike Borowiec) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Previously, I wrote: > I believe a bug has been introduced into the 2.1-960627-SNAP YP code. > Previously, I had been able to use NIS netgroups in the password file: > +@mygroup::::::::: > As it turns out, netgroups have nothing to do with this problem. It is a problem with any YP password entries from my Sun server... I've added +::::::::: when editing the password file (with vipw), but NONE of the users in the NIS password map can login. > The FreeBSD client is bound to a SunOS 4.1.x server. When I attempt to > login, FreeBSD attempts : > NIS: ----- Network Information Service ----- > NIS: Proc = 4 (Return first key-value pair in map) > NIS: Domain = mydomain > NIS: Map = master.passwd.byname > > Of course, my Sun NIS domain has no such map "master.passwd.byname", > and that's the end of that. The FreeBSD client goes on to try and get > the passwd.byname entry for my login, which succeeds. Nevertheless, > the login is refused. Here is a high-level packet trace: > > 1 0.00000 toybox -> sunc NIS C FIRST > 2 0.01581 sunc -> toybox NIS R FIRST No such map > 3 0.00321 toybox -> sunc NIS C MATCH mikebo in passwd.byname > 4 0.01115 sunc -> toybox NIS R MATCH OK > > If I take the SunOS map entry from my account, and massage it to fit > the format of the FreeBSD vipw, I am able to login just fine. This means > that the password encryption and comparison is working. (Yes, DES is > installed and working). > Let me rephrase my closing comments. I really need NIS password file support to work. Is anyone else seeing this problem? Is there anything I should check out that might be incorrectly configured? Is anyone else successfully using NIS password entries when bound to a SunOS server? Any help would be greatly appreciated. Thanks, - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 3 13:53:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA24569 for hackers-outgoing; Wed, 3 Jul 1996 13:53:51 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA24562 for ; Wed, 3 Jul 1996 13:53:47 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.6.12) with SMTP id OAA06755; Wed, 3 Jul 1996 14:03:17 -0700 (PDT) Date: Wed, 3 Jul 1996 14:03:16 -0700 (PDT) From: Tom Samplonius To: mikebo@tellabs.com cc: hackers@freebsd.org, Mike Borowiec Subject: Re: 2.1-960627-SNAP: YP problem In-Reply-To: <199607031959.OAA13711@sunc210.tellabs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Jul 1996 mikebo@tellabs.com wrote: > Greetings - > I believe a bug has been introduced into the 2.1-960627-SNAP YP code. > Previously, I had been able to use NIS netgroups in the password file: > +@mygroup::::::::: Did you also modify your /etc/group file? Tom From owner-freebsd-hackers Wed Jul 3 13:58:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA24796 for hackers-outgoing; Wed, 3 Jul 1996 13:58:13 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA24783 for ; Wed, 3 Jul 1996 13:58:07 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id VAA11008; Wed, 3 Jul 1996 21:57:44 +0100 (BST) To: Scanner cc: Jaye Mathisen , hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Is there a real live actual working deluser script? In-reply-to: Your message of "Wed, 03 Jul 1996 15:48:02 EDT." Date: Wed, 03 Jul 1996 21:57:43 +0100 Message-ID: <11006.836427463@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Scanner wrote in message ID : > Here is one that is like 2 lines mine and the rest gary's :) > Mine started out simeple as 4 lines. But under use of those less unix > knowledable it went haywire. So it was re-written all but 2 lines. > It works pretty good. Hope it does the job for you. You might have told people that it only works if the user is in group 1001 :-) I put that in to stop you deleting yourself Chris :-) > GID=`echo $PASSWD | awk -F : ' { print $4 } '` > if [ $GID != "1001" ]; then > echo "\"$LUSER\" is not in group 1001 (users). Aborting." > exit 1 > fi This bit of code is possibly only applicable to people like WebSpan... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Wed Jul 3 14:05:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25405 for hackers-outgoing; Wed, 3 Jul 1996 14:05:09 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25392; Wed, 3 Jul 1996 14:05:05 -0700 (PDT) Received: from orion.webspan.net (scanner@orion.webspan.net [206.154.70.41]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id RAA16164; Wed, 3 Jul 1996 17:04:58 -0400 (EDT) Date: Wed, 3 Jul 1996 17:04:58 -0400 (EDT) From: Scanner To: Gary Palmer cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Is there a real live actual working deluser script? In-Reply-To: <11006.836427463@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Jul 1996, Gary Palmer wrote: > Scanner wrote in message ID > : > > Here is one that is like 2 lines mine and the rest gary's :) > > Mine started out simeple as 4 lines. But under use of those less unix > > knowledable it went haywire. So it was re-written all but 2 lines. > > It works pretty good. Hope it does the job for you. > > You might have told people that it only works if the user is in group > 1001 :-) I put that in to stop you deleting yourself Chris :-) > This bit of code is possibly only applicable to people like WebSpan... My fudge up. Again im my drunken/lackofsleep/brain dead state i failed to mention that. Oh by the way everyone it only works of your users are in a group called 'users', and that group has GID 1001. Unless you can modify the script to suit your needs. -- ===================================| Webspan Inc., ISP Division. FreeBSD 2.1.0 is available now! | Phone: 908-367-8030 ext. 126 -----------------------------------| 500 West Kennedy Blvd., Lakewood, NJ-08701 Turning PCs into Workstations | E-Mail: scanner@webspan.net http://www.freebsd.org | SysAdmin / Network Engineer / Security ===================================| Member BSDNET team! http://www.bsdnet.org From owner-freebsd-hackers Wed Jul 3 14:14:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25955 for hackers-outgoing; Wed, 3 Jul 1996 14:14:29 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25945 for ; Wed, 3 Jul 1996 14:14:25 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id OAA01694 for hackers@freebsd.org; Wed, 3 Jul 1996 14:14:03 -0700 (PDT) Date: Wed, 3 Jul 1996 14:14:03 -0700 (PDT) From: Julian Elischer Message-Id: <199607032114.OAA01694@ref.tfs.com> To: hackers@freebsd.org Subject: New (BIOS) bootblock ?feature? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk do we want to integrate this? Since I originally ported the bootblocks to freeBSD, I haven't done much with them.. This is my first real return to the area.. I have been askled to make the following patches to the bootblocks, together with a user-level program to control it...... The patches are now complete and working, so I want to know if the gang thinks I should integrate them to our sources or whether my client should just keep them separate.. Programmable one-time bootstring.. (or many time) block 2 (usually untouched if you are using an fdisk block and have not used the first cylinder (as DOS does) is examined for a magic number, and if it matches, is examined for the default bootstring e.g. 2:sd(1,d)/kernel.goofy if the "WRITEBACK" option is used, then this string is zero'd out of block 2 after being read, meaning that should this boot fail, it will not be tried again the same. the second block can contain as many strings (zero separated, each with a 2 byte magic header ('D','N' ) as can be fit in, with a '0xff' indicating the end of the strings. thus: nextboot -f /dev/rwd0 kernel kernel kernel kernel.bak \ wd(0,d)/kernel wd(0,d)/kernel \ wd(0,d)/kernel.bak wd(1,a)/kernel will try successively each of those kernels on each successive boot. note: they are NOT tried successively if they do not exist within the same boot.. if a kernel does not exist, then after one attempt, the bootblock will revert to /kernel, as it does now. if the WRITEBACK feature is not enabled, then the first entry is used only, as the system doesn't know it has already used it. reason for existance..: 1/ remote booting an experimental kernel.. 2/ upgrading to a different (newer) root partition, but with a fallback if the install was bad. 3/ place a dummy bsd part on wd0 and redirect the default boot to sd2 where the real bsd part is? The theory is that the rc script writes the new block back again if and only if the boot succeeded.. if it didn't then the rc will not have been able to touch it, and the next string will be used when the system reboots. anyway, the install program will not normally install on a block that doesn't have the magic number already, and will require a special flag to pre-place the magic number on block 2. It will (possibly) examing block 1 to ensure that there are no fdisk partitions using block 2. thoughts? julian From owner-freebsd-hackers Wed Jul 3 14:27:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA26823 for hackers-outgoing; Wed, 3 Jul 1996 14:27:10 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA26813 for ; Wed, 3 Jul 1996 14:27:03 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id XAA07512; Wed, 3 Jul 1996 23:26:47 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id XAA04413; Wed, 3 Jul 1996 23:26:14 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id XAA12258; Wed, 3 Jul 1996 23:17:24 +0200 (MET DST) From: Ollivier Robert Message-Id: <199607032117.XAA12258@keltia.freenix.fr> Subject: Re: async flag to mount(8) To: alex@fa.tdktca.com Date: Wed, 3 Jul 1996 23:17:24 +0200 (MET DST) Cc: dunn@harborcom.net, hackers@freebsd.org In-Reply-To: <199607031339.IAA08875@fa.tdktca.com> from Alex Nash at "Jul 3, 96 08:39:17 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#2178 X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems that Alex Nash said: > At the risk of experiencing Terry's wrath :), async is very useful, > and under *some* scenarios (like rm -rf), very fast. I think (almost) > everyone agrees that it's risky, but for filesystems such as /tmp one > really shouldn't care. At the risk of appearing totally foolish, I've been mounting /usr/src (useful for cvs update), /usr/obj (useful during "make world") and /news (expire is happy!) and the CVS tree (useful for CTM) async for more than a year. Had a few crashes, still have to lost anything. Even during the earlier time of async support by John, I didn't got any unsolvable problem with it. /dev/sd0a on / (local) /dev/sd0d on /usr (local) /dev/sd0h on /usr/local (local) /dev/sd12e on /var (local) /dev/sd0f on /users (local) /dev/sd12f on /news (asynchronous, local, nosuid) Usenet (small part.) /dev/sd0g on /src (asynchronous, local) /usr/src /dev/sd12g on /spare (asynchronous, local) CVS tree /dev/sd0e on /work (asynchronous, local) mostly build of prgs /dev/sd11a on /x (local, nosuid) FTP server /dev/sd12h on /y (asynchronous, local) /usr/obj procfs on /proc (local) Sound scary I know, but works perfectly well. Result ? 4h50mn for "make world" on 486DX4/100, 32 MB, 2x SCSI controllers (sd0 on bt0 and sd11 and sd12 on ahb0). Yeah, I enjoy risk :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #12: Sun Jun 30 14:10:07 MET DST 1996 From owner-freebsd-hackers Wed Jul 3 14:40:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27889 for hackers-outgoing; Wed, 3 Jul 1996 14:40:08 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA27837 for ; Wed, 3 Jul 1996 14:39:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA11356; Wed, 3 Jul 1996 14:37:43 -0700 From: Terry Lambert Message-Id: <199607032137.OAA11356@phaeton.artisoft.com> Subject: Re: async flag to mount(8) To: alex@fa.tdktca.com (Alex Nash) Date: Wed, 3 Jul 1996 14:37:43 -0700 (MST) Cc: terry@lambert.org, dunn@harborcom.net, hackers@FreeBSD.ORG In-Reply-To: from "Alex Nash" at Jul 3, 96 01:34:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Matt Day (next cubicle over from mine) has implemented soft updates, > > though without some of my FS changes, they can not be integrated > > into FreeBSD. > > > > An FS using soft updates operates within ~5% of memory speed, according > > to the Ganger/Patt paper from the University of Michigan. > > > > This is faster than pure async because of write gathering during the > > soft update timer period. > > > > Async sucks. Get over it. > > So async only sucks *when* we get your patches. I'm sure Poul can't > wait! :) When you get the Lite2 integration so my patches can be accepted, when you get my patches, when you get Matt's patches. But actually, "sucks" is like "phloegisten"; something has "sucksness" or it doesn't. Async mounts have "sucksness", and the amount of "sucksness" is independent of the situation. Red is red independent of having blue to compare it to. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 14:44:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28423 for hackers-outgoing; Wed, 3 Jul 1996 14:44:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28408 for ; Wed, 3 Jul 1996 14:44:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA11380; Wed, 3 Jul 1996 14:41:43 -0700 From: Terry Lambert Message-Id: <199607032141.OAA11380@phaeton.artisoft.com> Subject: Re: New (BIOS) bootblock ?feature? To: julian@ref.tfs.com (Julian Elischer) Date: Wed, 3 Jul 1996 14:41:42 -0700 (MST) Cc: hackers@FreeBSD.org In-Reply-To: <199607032114.OAA01694@ref.tfs.com> from "Julian Elischer" at Jul 3, 96 02:14:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > do we want to integrate this? > Since I originally ported the bootblocks to freeBSD, I haven't done much > with them.. This is my first real return to the area.. > > I have been askled to make the following patches to the bootblocks, > together with a user-level program to control it...... > > The patches are now complete and working, so I want to know if the gang > thinks I should integrate them to our sources or whether my client should > just keep them separate.. > > Programmable one-time bootstring.. (or many time) How does this interact with erich@uruk.org's "multiboot" proposed standard and code? It sounds like a step forward, and any step forward should be integrated (IMO). It would certaily solve that Italian PC Week reviewer's boot problems... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 14:50:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28904 for hackers-outgoing; Wed, 3 Jul 1996 14:50:27 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28896 for ; Wed, 3 Jul 1996 14:50:25 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id OAA08573; Wed, 3 Jul 1996 14:49:35 -0700 (PDT) To: dunn@harborcom.net cc: hackers@freebsd.org Subject: Re: async flag to mount(8) In-reply-to: Your message of "Wed, 03 Jul 1996 09:06:25 CDT." <199607031311.JAA15975@ns2.harborcom.net> Date: Wed, 03 Jul 1996 14:49:34 -0700 Message-ID: <8571.836430574@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I do it all the time - it really does speed things up a fair bit. Jordan > Has anyone ever had the stomach to mount a fs async? What have been > your experiences? > > Bradley Dunn > Harbor Communications From owner-freebsd-hackers Wed Jul 3 15:04:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29927 for hackers-outgoing; Wed, 3 Jul 1996 15:04:30 -0700 (PDT) Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29917 for ; Wed, 3 Jul 1996 15:04:27 -0700 (PDT) From: mikebo@tellabs.com Received: from sunc210.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0uba1a-0004f9C; Wed, 3 Jul 96 17:03 CDT Received: by sunc210.tellabs.com (SMI-8.6/1.9) id RAA13882; Wed, 3 Jul 1996 17:03:20 -0500 Message-Id: <199607032203.RAA13882@sunc210.tellabs.com> Subject: Re: 2.1-960627-SNAP: YP problem To: mrm@Mole.ORG (M.R.Murphy) Date: Wed, 3 Jul 1996 17:03:19 -0500 (CDT) Cc: hackers@freebsd.org, mikebo (Mike Borowiec) In-Reply-To: <199607032149.OAA10177@meerkat.mole.org> from "M.R.Murphy" at Jul 3, 96 02:49:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Murphy wrote: > > From owner-freebsd-hackers@freefall.freebsd.org Wed Jul 3 13:36:13 1996 > > From: mikebo@tellabs.com > > Subject: 2.1-960627-SNAP: YP problem > > To: bugs@freebsd.org > > Date: Wed, 3 Jul 1996 15:25:09 -0500 (CDT) > > > > I believe a bug has been introduced into the 2.1-960627-SNAP YP code. > > As it turns out, netgroups have nothing to do with this problem. It is > > a problem with any YP password entries from my Sun server... I've added > > +::::::::: when editing the password file (with vipw), but NONE of the > > users in the NIS password map can login. > > > Make the last line of the master password file > +:::::0:0::: > with vipw. This works for me. > A typical entry in /var/yp/etc/passwd is > mrm::101:200:M.R.Murphy:/home/mrm:/bin/sh > The corresponding entry in /var/yp/etc/master.passwd is > mrm::101:200::0:0:M.R.Murphy:/home/mrm:/bin/sh > Unfortunately, this did nothing... The passwd(5) man page states: The simplest way to activate NIS is to add an empty record with only a plus sign (`+') in the name field, such as this: +::::::::: The `+' will tell the getpwent(3) routines in FreeBSD's standard C li- brary to begin using the NIS passwd maps for lookups. This does not work. Only those users hardcoded into the local password file can login. I'm bound to the master YP server, and I can ypmatch my passwd.byname record all day... but can't login. HELP! - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 3 15:05:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29995 for hackers-outgoing; Wed, 3 Jul 1996 15:05:17 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA29988 for ; Wed, 3 Jul 1996 15:05:15 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id PAA02238; Wed, 3 Jul 1996 15:02:51 -0700 (PDT) Message-Id: <199607032202.PAA02238@ref.tfs.com> Subject: Re: New (BIOS) bootblock ?feature? To: terry@lambert.org (Terry Lambert) Date: Wed, 3 Jul 1996 15:02:50 -0700 (PDT) From: "JULIAN Elischer" Cc: hackers@freebsd.org In-Reply-To: <199607032141.OAA11380@phaeton.artisoft.com> from "Terry Lambert" at Jul 3, 96 02:41:42 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > do we want to integrate this? > > Since I originally ported the bootblocks to freeBSD, I haven't done much > > with them.. This is my first real return to the area.. > > > > I have been askled to make the following patches to the bootblocks, > > together with a user-level program to control it...... > > > > The patches are now complete and working, so I want to know if the gang > > thinks I should integrate them to our sources or whether my client should > > just keep them separate.. > > > > Programmable one-time bootstring.. (or many time) > > How does this interact with erich@uruk.org's "multiboot" proposed > standard and code? can you give me a pointer? > > It sounds like a step forward, and any step forward should be > integrated (IMO). It would certaily solve that Italian PC Week > reviewer's boot problems... which were? > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-hackers Wed Jul 3 15:29:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02528 for hackers-outgoing; Wed, 3 Jul 1996 15:29:21 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA02523 for ; Wed, 3 Jul 1996 15:29:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA11550; Wed, 3 Jul 1996 15:26:57 -0700 From: Terry Lambert Message-Id: <199607032226.PAA11550@phaeton.artisoft.com> Subject: Re: New (BIOS) bootblock ?feature? To: julian@ref.tfs.com (JULIAN Elischer) Date: Wed, 3 Jul 1996 15:26:57 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607032202.PAA02238@ref.tfs.com> from "JULIAN Elischer" at Jul 3, 96 03:02:50 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > do we want to integrate this? > > > Since I originally ported the bootblocks to freeBSD, I haven't done much > > > with them.. This is my first real return to the area.. > > > > > > I have been askled to make the following patches to the bootblocks, > > > together with a user-level program to control it...... > > > > > > The patches are now complete and working, so I want to know if the gang > > > thinks I should integrate them to our sources or whether my client should > > > just keep them separate.. > > > > > > Programmable one-time bootstring.. (or many time) > > > > How does this interact with erich@uruk.org's "multiboot" proposed > > standard and code? > > can you give me a pointer? http://www.uruk.org/grub/boot-proposal.html He recently released code in several news groups... he's the Intel employee working with the SMP project. > > It sounds like a step forward, and any step forward should be > > integrated (IMO). It would certaily solve that Italian PC Week > > reviewer's boot problems... > > which were? IDE controller 1 master disk OS-BS slave controller 2 master disk FreeBSD slave He gets "can't mount root" because FreeBSD tries to mount root from wd1, but the root is actually on wd2. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 16:01:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA05931 for hackers-outgoing; Wed, 3 Jul 1996 16:01:02 -0700 (PDT) Received: from chain.iafrica.com (root@chain.iafrica.com [196.31.1.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA05925 for ; Wed, 3 Jul 1996 16:00:57 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.5/8.6.12) with SMTP id BAA06738 for ; Thu, 4 Jul 1996 01:00:46 +0200 (SAT) Date: Thu, 4 Jul 1996 01:00:46 +0200 (SAT) From: Khetan Gajjar To: hackers@freebsd.org Subject: Re: Are you a programmer? Do you wear glasses? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Jul 1996, Don Yuniskis wrote: >Actually, aren't the lists set up so that only subscribers can post >to the lists? Or, is that considered too "unfriendly"? Should just set it up to ban all aol'ers. No intelligent f'bsd user would use aol as well Regards, Khetan Gajjar. --- http://www.chain.iafrica.com/~khetan/ UUNet-Internet Africa Operations - 0800-030-002 From owner-freebsd-hackers Wed Jul 3 16:21:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07335 for hackers-outgoing; Wed, 3 Jul 1996 16:21:10 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07317 for ; Wed, 3 Jul 1996 16:20:38 -0700 (PDT) Received: from campa.panke.de ([130.149.17.213]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id BAA03230; Thu, 4 Jul 1996 01:07:53 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id BAA02465; Thu, 4 Jul 1996 01:04:14 +0200 Date: Thu, 4 Jul 1996 01:04:14 +0200 From: Wolfram Schneider Message-Id: <199607032304.BAA02465@campa.panke.de> To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Is there a real live actual working deluser script? In-Reply-To: References: Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen writes: >Even if it's rudimentary? I did a search on -hackers, and there's lots of >talk about it, and about how complicated it would be, and on and on, but >no actual script, and I don't see a port or a package. ftp://ftp.dsu.edu/pub/FreeBSD/ghelmer/removeuser.tar.gz From owner-freebsd-hackers Wed Jul 3 16:41:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08755 for hackers-outgoing; Wed, 3 Jul 1996 16:41:04 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA08746; Wed, 3 Jul 1996 16:41:01 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA09153; Wed, 3 Jul 1996 16:40:29 -0700 (PDT) To: Wolfram Schneider cc: Jaye Mathisen , hackers@freebsd.org Subject: Re: Is there a real live actual working deluser script? In-reply-to: Your message of "Thu, 04 Jul 1996 01:04:14 +0200." <199607032304.BAA02465@campa.panke.de> Date: Wed, 03 Jul 1996 16:40:28 -0700 Message-ID: <9151.836437228@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stuff like this, PLEASE feel free to upload into the ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-incoming/experimental/ Directory. :-) Also, don't forget: ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-incoming/commercial/ If you have a commercial shareware/demo package you'd like included on the 2.1.5 CD. Each contribution should have an accompanying README and go into its own subdirectory. Remember - if you don't get it in there soon and then come back to me after 2.1.5 is out, crying about how your experimental feature or commercial demo didn't make it on and "why didn't I warn you!", I will simply point you at this posting. :-) Thanks! Jordan > Jaye Mathisen writes: > >Even if it's rudimentary? I did a search on -hackers, and there's lots of > >talk about it, and about how complicated it would be, and on and on, but > >no actual script, and I don't see a port or a package. > > ftp://ftp.dsu.edu/pub/FreeBSD/ghelmer/removeuser.tar.gz From owner-freebsd-hackers Wed Jul 3 16:41:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08788 for hackers-outgoing; Wed, 3 Jul 1996 16:41:27 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA08781 for ; Wed, 3 Jul 1996 16:41:26 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id QAA03550; Wed, 3 Jul 1996 16:39:02 -0700 (PDT) Message-Id: <199607032339.QAA03550@ref.tfs.com> Subject: Re: New (BIOS) bootblock ?feature? To: terry@lambert.org (Terry Lambert) Date: Wed, 3 Jul 1996 16:39:00 -0700 (PDT) From: "JULIAN Elischer" Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607032226.PAA11550@phaeton.artisoft.com> from "Terry Lambert" at Jul 3, 96 03:26:57 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > > How does this interact with erich@uruk.org's "multiboot" proposed > > > standard and code? > > > > can you give me a pointer? > > http://www.uruk.org/grub/boot-proposal.html > > He recently released code in several news groups... he's the Intel > employee working with the SMP project. I looked at his stuff. I don't think it's really relevant to these changes.... julian From owner-freebsd-hackers Wed Jul 3 19:42:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19318 for hackers-outgoing; Wed, 3 Jul 1996 19:42:53 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19293 for ; Wed, 3 Jul 1996 19:42:47 -0700 (PDT) Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id VAA25101; Wed, 3 Jul 1996 21:42:35 -0500 (CDT) Message-Id: <199607040242.VAA25101@sierra.zyzzyva.com> To: Julian Elischer cc: hackers@freebsd.org Subject: Re: New (BIOS) bootblock ?feature? In-reply-to: julian's message of Wed, 03 Jul 1996 14:14:03 -0700. <199607032114.OAA01694@ref.tfs.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Jul 1996 21:42:35 -0500 From: Randy Terbush Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sounds like these would be very useful additions. > > do we want to integrate this? > Since I originally ported the bootblocks to freeBSD, I haven't done much > with them.. This is my first real return to the area.. > > I have been askled to make the following patches to the bootblocks, > together with a user-level program to control it...... > > The patches are now complete and working, so I want to know if the gang > thinks I should integrate them to our sources or whether my client should > just keep them separate.. > > Programmable one-time bootstring.. (or many time) > > block 2 (usually untouched if you are using an fdisk block and have not used > the first cylinder (as DOS does) is examined for a magic number, > and if it matches, is examined for the default bootstring > e.g. 2:sd(1,d)/kernel.goofy > > if the "WRITEBACK" option is used, then this string is zero'd out > of block 2 after being read, meaning that should this boot fail, > it will not be tried again the same. > > the second block can contain as many strings (zero separated, each with > a 2 byte magic header ('D','N' ) as can be fit in, with a '0xff' > indicating the end of the strings. > > thus: > > nextboot -f /dev/rwd0 kernel kernel kernel kernel.bak \ > wd(0,d)/kernel wd(0,d)/kernel \ > wd(0,d)/kernel.bak wd(1,a)/kernel > > will try successively each of those kernels on each successive boot. > note: they are NOT tried successively if they do not exist within the > same boot.. > if a kernel does not exist, then after one attempt, > the bootblock will revert to /kernel, as it does now. > > if the WRITEBACK feature is not enabled, then the first entry is used > only, as the system doesn't know it has already used it. > > reason for existance..: > > > 1/ remote booting an experimental kernel.. > 2/ upgrading to a different (newer) root partition, but with a fallback > if the install was bad. > 3/ place a dummy bsd part on wd0 and redirect the default boot to sd2 > where the real bsd part is? > > The theory is that the rc script writes the new block back again if and only > if the boot succeeded.. if it didn't then the rc will not have been able to > touch it, and the next string will be used when the system reboots. > > anyway, the install program will not normally install on a block that doesn't > have the magic number already, and will require a special flag > to pre-place the magic number on block 2. It will (possibly) > examing block 1 to ensure that there are no fdisk partitions using block 2. > > thoughts? > > julian From owner-freebsd-hackers Wed Jul 3 20:29:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA23458 for hackers-outgoing; Wed, 3 Jul 1996 20:29:42 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA23447 for ; Wed, 3 Jul 1996 20:29:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA12079; Wed, 3 Jul 1996 20:27:10 -0700 From: Terry Lambert Message-Id: <199607040327.UAA12079@phaeton.artisoft.com> Subject: Re: New (BIOS) bootblock ?feature? To: julian@ref.tfs.com (JULIAN Elischer) Date: Wed, 3 Jul 1996 20:27:10 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607032339.QAA03550@ref.tfs.com> from "JULIAN Elischer" at Jul 3, 96 04:39:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > How does this interact with erich@uruk.org's "multiboot" proposed > > > > standard and code? > > > > > > can you give me a pointer? > > > > http://www.uruk.org/grub/boot-proposal.html > > > > He recently released code in several news groups... he's the Intel > > employee working with the SMP project. > > I looked at his stuff. > I don't think it's really relevant to these changes.... Well, that's why I asked. 8-). I say integrate the changes, they are a win. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 20:49:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24638 for hackers-outgoing; Wed, 3 Jul 1996 20:49:14 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA24632 for ; Wed, 3 Jul 1996 20:49:10 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id XAA14514; Wed, 3 Jul 1996 23:48:59 -0400 Date: Wed, 3 Jul 1996 23:48:59 -0400 Message-Id: <199607040348.XAA14514@kropotkin.gnu.ai.mit.edu> To: terry@lambert.org CC: jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.org In-reply-to: <199607030621.XAA09969@phaeton.artisoft.com> (message from Terry Lambert on Tue, 2 Jul 1996 23:21:09 -0700 (MST)) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> But how would you mount your filesystems at boot time? > Mounts will be inserted into the fs hierarchy post-facto by > mount-point mapping of the vnodes according to the content of the > fstab. But with /etc as a symlink to something on a different filesystem, then how would the fstab be read, since the root filesystem is the only one that can be mounted before fstab is availible? I think that this point has been made and remade many times before my post made it. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Wed Jul 3 21:07:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25907 for hackers-outgoing; Wed, 3 Jul 1996 21:07:26 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA25902 for ; Wed, 3 Jul 1996 21:07:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA12261; Wed, 3 Jul 1996 21:01:44 -0700 From: Terry Lambert Message-Id: <199607040401.VAA12261@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: joelh@gnu.ai.mit.edu Date: Wed, 3 Jul 1996 21:01:44 -0700 (MST) Cc: terry@lambert.org, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.org In-Reply-To: <199607040348.XAA14514@kropotkin.gnu.ai.mit.edu> from "Joel Ray Holveck" at Jul 3, 96 11:48:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >> But how would you mount your filesystems at boot time? > > > > Mounts will be inserted into the fs hierarchy post-facto by > > mount-point mapping of the vnodes according to the content of the > > fstab. > > But with /etc as a symlink to something on a different filesystem, > then how would the fstab be read, since the root filesystem is the > only one that can be mounted before fstab is availible? > > I think that this point has been made and remade many times before my > post made it. Incorrect. All file systems will have mount point vnode assignments as a result of a callback as a result of device probe. This means all mount structure will be filled out. What will not be filled out is the hierarchy assignment, including covered vnodes. This is what is filled out by /etc/fstab, if we don't choose to make fstab "go away" entirely. The root file system is identifiable by a preinitialized "last mounted on" field. This field, and additional metadata from a file on the file system itself (it works for quotas, after all), or from an extended superblock, can be used to encode all necessary mount options. The "/etc" directory is not allowed to be other than on the root file system, by definition. That resolves the symlink problem. I think perhaps that the confusion is coming from the (incorrect) idea that system configuration information will exist or be acted upon prior to the file systems mounted vnodes being mapped into the mounted FS hierarchy? The idea that /etc must be localizable by file modification instead of being localizable by data madification in /var (or elsewhere) is a lame idea. It is unacceptable for the idea of sharing a read-only root among multiple clients, and must be discarded as historical cruft, which we may ignore at our leisure. IP mapping can be achieved via bootp followed by a DNS call, since there is sufficient information to get there without a valid "/etc/hosts" file. I don't see any contradictions. If you think non-DNS-based host name assignment for identification purposes must occur early in the boot process (I don't see why you would be under this incorrect impression), then you can always implement DHCP... there are RFC's which handle that "need" quite nicely (for instance, if during the boot process you need to do a "netaddname" call for 1001/1002 NetBIOS support (NetBIOS is not a boot critical system component, so that's quite unlikely in any case). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 21:46:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA28472 for hackers-outgoing; Wed, 3 Jul 1996 21:46:16 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA28460 for ; Wed, 3 Jul 1996 21:46:13 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id FAA12471; Thu, 4 Jul 1996 05:40:58 +0100 (BST) To: Terry Lambert cc: joelh@gnu.ai.mit.edu, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: What is the best way to setup a drive In-reply-to: Your message of "Wed, 03 Jul 1996 21:01:44 PDT." <199607040401.VAA12261@phaeton.artisoft.com> Date: Thu, 04 Jul 1996 05:40:55 +0100 Message-ID: <12468.836455255@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote in message ID <199607040401.VAA12261@phaeton.artisoft.com>: > The "/etc" directory is not allowed to be other than on the root file > system, by definition. That resolves the symlink problem. Umm? What was being talked about (if you remember) was having a read-only root filesystem. Then someone pointed out that that'd stop you changing passwords, so then a symlink from /etc to a read-write FS was suggested ... Which makes me wonder where your FS ``improvements'' fit in? They don't solve the problem of how to figure out where to get the /etc directory from. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Wed Jul 3 22:06:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29542 for hackers-outgoing; Wed, 3 Jul 1996 22:06:15 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA29534; Wed, 3 Jul 1996 22:06:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id WAA12377; Wed, 3 Jul 1996 22:04:15 -0700 From: Terry Lambert Message-Id: <199607040504.WAA12377@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Wed, 3 Jul 1996 22:04:14 -0700 (MST) Cc: terry@lambert.org, joelh@gnu.ai.mit.edu, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-Reply-To: <12468.836455255@palmer.demon.co.uk> from "Gary Palmer" at Jul 4, 96 05:40:55 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The "/etc" directory is not allowed to be other than on the root file > > system, by definition. That resolves the symlink problem. > > Umm? What was being talked about (if you remember) was having a > read-only root filesystem. Then someone pointed out that that'd stop > you changing passwords, so then a symlink from /etc to a read-write FS > was suggested ... Which makes me wonder where your FS ``improvements'' > fit in? They don't solve the problem of how to figure out where to get > the /etc directory from. I thought that was clear. That /etc has to be writeable is a bogus assumption. The NIS suggestion for "where do I get my passwords from" frees up /etc/passwd. What's left is /etc/fstab (dealt with by mount changes, which aren't the same thing as FS changes), /etc/rc* (bogus) and /etc/sysconfig (also bogus). I really don't see where the problem is: throw out your bogositieis and fix the rest to comply with the design documents, and the problems all fade away. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 3 22:43:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA01958 for hackers-outgoing; Wed, 3 Jul 1996 22:43:38 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA01953 for ; Wed, 3 Jul 1996 22:43:36 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id WAA16437; Wed, 3 Jul 1996 22:44:11 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id PAA00558; Thu, 4 Jul 1996 15:42:32 +1000 From: Julian Assange Message-Id: <199607040542.PAA00558@suburbia.net> Subject: Re: What is the best way to setup a driver To: terry@lambert.org (Terry Lambert) Date: Thu, 4 Jul 1996 15:42:31 +1000 (EST) Cc: joelh@gnu.ai.mit.edu, terry@lambert.org, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@freebsd.org In-Reply-To: <199607040401.VAA12261@phaeton.artisoft.com> from "Terry Lambert" at Jul 3, 96 09:01:44 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > All file systems will have mount point vnode assignments as a result > of a callback as a result of device probe. > > This means all mount structure will be filled out. > > What will not be filled out is the hierarchy assignment, including > covered vnodes. This is what is filled out by /etc/fstab, if we > don't choose to make fstab "go away" entirely. > > The root file system is identifiable by a preinitialized "last mounted > on" field. This field, and additional metadata from a file on the > file system itself (it works for quotas, after all), or from an > extended superblock, can be used to encode all necessary mount > options. > > The "/etc" directory is not allowed to be other than on the root file > system, by definition. That resolves the symlink problem. This is not clear to me. Can you explain in more detail how this resolves the problem? -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Wed Jul 3 22:52:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA02855 for hackers-outgoing; Wed, 3 Jul 1996 22:52:45 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA02850 for ; Wed, 3 Jul 1996 22:52:39 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA09155 for ; Thu, 4 Jul 1996 07:51:11 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA11643 for freebsd-hackers@freebsd.org; Thu, 4 Jul 1996 07:51:11 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA19380 for freebsd-hackers@freebsd.org; Thu, 4 Jul 1996 07:41:55 +0200 (MET DST) From: J Wunsch Message-Id: <199607040541.HAA19380@uriah.heep.sax.de> Subject: Re: async flag to mount(8) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 4 Jul 1996 07:41:55 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607031339.IAA08875@fa.tdktca.com> from Alex Nash at "Jul 3, 96 08:39:17 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Alex Nash wrote: > > Has anyone ever had the stomach to mount a fs async? What have been > > your experiences? > > At the risk of experiencing Terry's wrath :), async is very useful, > and under *some* scenarios (like rm -rf), very fast. Don't forget that you can do mount -o async -u /usr rm -rf /usr/obj ... mount -o noasync -u /usr as well. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jul 3 22:59:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA03335 for hackers-outgoing; Wed, 3 Jul 1996 22:59:38 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA03330; Wed, 3 Jul 1996 22:59:36 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id BAA14799; Thu, 4 Jul 1996 01:59:26 -0400 Date: Thu, 4 Jul 1996 01:59:26 -0400 Message-Id: <199607040559.BAA14799@kropotkin.gnu.ai.mit.edu> To: terry@lambert.org CC: gpalmer@FreeBSD.ORG, terry@lambert.org, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-reply-to: <199607040504.WAA12377@phaeton.artisoft.com> (message from Terry Lambert on Wed, 3 Jul 1996 22:04:14 -0700 (MST)) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>> The "/etc" directory is not allowed to be other than on the root >>> file system, by definition. That resolves the symlink problem. >> Umm? What was being talked about (if you remember) was having a >> read-only root filesystem. Then someone pointed out that that'd >> stop you changing passwords, so then a symlink from /etc to a >> read-write FS was suggested ... Which makes me wonder where your >> FS ``improvements'' fit in? They don't solve the problem of how to >> figure out where to get the /etc directory from. > I thought that was clear. That /etc has to be writeable is a > bogus assumption. The NIS suggestion for "where do I get my > passwords from" frees up /etc/passwd. I had been responding to the symlink idea that jmb proposed. Is there any problem with symlinking /etc/passwd to something on a r/w filesystem instead of dealing with NIS, to deal with pre-yp programs that don't think to call getpwent()? I suppose that the /etc/ptmp lockfile would have to be dealt with accordingly in that event, but there should be ways to handle that. Where are the perms for /dev/tty* stored? > What's left is /etc/fstab (dealt with by mount changes, which > aren't the same thing as FS changes), /etc/rc* (bogus) and > /etc/sysconfig (also bogus). Hmmm... We may also want to change paths.h (and src/sbin/nologin/nologin.5; why is it in that directory instead of shutdown or login?) to take care of /etc/nologin, although shutdown will work fine without changing it. (Just be sure to remove it manually your first attempt to boot with / r/o!) Should the comment from /etc/rc concern us?: "root must be read/write both for NFS diskless and for VFS LKMs before proceeding any further." > I really don't see where the problem is: throw out your > bogositieis and fix the rest to comply with the design documents, > and the problems all fade away. Who said there's a problem? I can't fix the programs at the current time (no net connection on my test machine, forgot to pay the phone bill), so I'm just pointing 'em out. I'm new at this; what design documents are you referring to? -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Wed Jul 3 23:16:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04216 for hackers-outgoing; Wed, 3 Jul 1996 23:16:22 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA04211 for ; Wed, 3 Jul 1996 23:16:20 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id CAA14851; Thu, 4 Jul 1996 02:16:12 -0400 Date: Thu, 4 Jul 1996 02:16:12 -0400 Message-Id: <199607040616.CAA14851@kropotkin.gnu.ai.mit.edu> To: terry@lambert.org CC: terry@lambert.org, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.org In-reply-to: <199607040401.VAA12261@phaeton.artisoft.com> (message from Terry Lambert on Wed, 3 Jul 1996 21:01:44 -0700 (MST)) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I cringe at the though of another branch of this thread, but here goes... > All file systems will have mount point vnode assignments as a result > of a callback as a result of device probe. What about conflicting mount points? Or suppose I'm diagnosing a dead /usr disk from another computer... will I have to worry about my working /usr being overwritten, or will there be some sort of identification, say, a timestamp written to all disks late during bootup (after probe and hierarchy fill), to ensure that they're on the same computer? And if so, how do we handle the whole point of sharing these? Semaphores, first one to mount stamps? Danger: hair ahead. Actually, I don't quite recall the point of your augmented superblocks to begin with. > It is unacceptable for the idea of sharing a read-only > root among multiple clients, and must be discarded as historical > cruft, which we may ignore at our leisure. Just so long as we don't break any code which depends on said historical cruft, I'm all for it. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Thu Jul 4 03:54:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA19550 for hackers-outgoing; Thu, 4 Jul 1996 03:54:36 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA19543 for ; Thu, 4 Jul 1996 03:54:32 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ae03245; 4 Jul 96 11:53 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa04309; 4 Jul 96 11:51 +0100 Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id AAA05227; Thu, 4 Jul 1996 00:41:51 GMT Date: Thu, 4 Jul 1996 00:41:51 GMT Message-Id: <199607040041.AAA05227@jraynard.demon.co.uk> From: James Raynard To: scanner@webspan.net CC: mrcpu@cdsnet.net, hackers@freebsd.org In-reply-to: (message from Scanner on Wed, 3 Jul 1996 15:48:02 -0400 (EDT)) Subject: Re: Is there a real live actual working deluser script? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Scanner writes: > > > talk about it, and about how complicated it would be, and on and on, but > > no actual script, and I don't see a port or a package. > Here is one that is like 2 lines mine and the rest gary's :) > Mine started out simeple as 4 lines. But under use of those less unix > knowledable it went haywire. So it was re-written all but 2 lines. > It works pretty good. Hope it does the job for you. [snip] Not bad! (maybe a crontab -u $LUSER -r in there somewhere would be a good idea). For bonus points, how about removing any files owned by them in /tmp and /var/tmp and killing any jobs they have left running - that should get rid of most of the "little surprises" that people occasionally leave behind... -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk http://www.freebsd.org/~jraynard/ From owner-freebsd-hackers Thu Jul 4 05:18:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA23549 for hackers-outgoing; Thu, 4 Jul 1996 05:18:17 -0700 (PDT) Received: from teil.soft.net (tata_elxsi.soft.net [164.164.10.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA23543 for ; Thu, 4 Jul 1996 05:18:06 -0700 (PDT) Received: by teil.soft.net (920330.SGI/920502.SGI.JF) for hackers@freeBSD.ORG id AA07436; Thu, 4 Jul 96 17:47:20 -0800 From: suren@teil.soft.net (S. Arockia Suren) Message-Id: <9607050147.AA07436@teil.soft.net> Subject: HI! Help please... To: hackers@freeBSD.ORG Date: Thu, 4 Jul 1996 17:47:18 -0800 (PST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, i need some help regarding finding the interface through which a limited braodcast packet was received. An icmp socket is opened to receive limited broadcast messages (ffff). 1. is it true that if the socket is bind by an address it cannot receive the limited broadcast message??? because the only information i could get from "pr_input" function that to receive limited broadcast messages only two things r possible 1. bind it with limited broadcast address 2. donot bind it. if my conclusion is true, then which possibility would be better to use? if there r other possibilities please let me know abt them and suggest the best to use. 2. in case of a node with multiple interfaces, how can i determine the interface from which i received a limited broadcast (icmp) packet. freebsd does not seem to distinguish the sockets based on the interface on which they r functioning. instead when it gets a packet it sends a copy to all the sockets that r eligible to receive the packet. please help me solve these two problems. thanking you in anticipation, suren. From owner-freebsd-hackers Thu Jul 4 06:30:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26115 for hackers-outgoing; Thu, 4 Jul 1996 06:30:16 -0700 (PDT) Received: from teil.soft.net (tata_elxsi.soft.net [164.164.10.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26110 for ; Thu, 4 Jul 1996 06:30:08 -0700 (PDT) Received: by teil.soft.net (920330.SGI/920502.SGI.JF) for hackers@freeBSD.ORG id AA10479; Thu, 4 Jul 96 18:59:29 -0800 From: suren@teil.soft.net (S. Arockia Suren) Message-Id: <9607050259.AA10479@teil.soft.net> Subject: HI! Need Help..(ignore earlier one) To: hackers@freeBSD.ORG Date: Thu, 4 Jul 1996 18:59:28 -0800 (PST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, i need some help regarding finding the interface through which a limited braodcast packet was received. An icmp socket is opened to receive limited broadcast messages (ffff). 1. is it true that if the socket is bind by an address it cannot receive the limited broadcast message??? because the only information i could get from "rip_input" function that to receive limited broadcast messages only two things r possible 1. bind it with limited broadcast address 2. donot bind it. if my conclusion is true, then which possibility would be better to use? if there r other possibilities please let me know abt them and suggest the best to use. 2. in case of a node with multiple interfaces, how can i determine the interface from which i received a limited broadcast (icmp) packet. freebsd does not seem to distinguish the sockets based on the interface on which they r functioning. instead when it gets a packet it sends a copy to all the sockets that r eligible to receive the packet. please help me solve these two problems. thanking you in anticipation, suren. From owner-freebsd-hackers Thu Jul 4 12:24:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14005 for hackers-outgoing; Thu, 4 Jul 1996 12:24:17 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA13996 for ; Thu, 4 Jul 1996 12:24:15 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id PAA16322; Thu, 4 Jul 1996 15:23:57 -0400 Date: Thu, 4 Jul 1996 15:23:57 -0400 Message-Id: <199607041923.PAA16322@kropotkin.gnu.ai.mit.edu> To: fhackers@jraynard.demon.co.uk CC: scanner@webspan.net, mrcpu@cdsnet.net, hackers@freebsd.org In-reply-to: <199607040041.AAA05227@jraynard.demon.co.uk> (message from James Raynard on Thu, 4 Jul 1996 00:41:51 GMT) Subject: Re: Is there a real live actual working deluser script? From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Here is one that is like 2 lines mine and the rest gary's :) > Not bad! (maybe a crontab -u $LUSER -r in there somewhere would be > a good idea). > For bonus points, how about removing any files owned by them in > /tmp and /var/tmp and killing any jobs they have left running - > that should get rid of most of the "little surprises" that people > occasionally leave behind... If we really want to get fancy, also kill their mailfile, and add something to /etc/aliases to send their mail through a vacation-style script, and then at now+1 week grep -v that line out of existance, as well as sed -e s/${LUSER}// them out of any mailing lists they may be on. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Thu Jul 4 12:55:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16221 for hackers-outgoing; Thu, 4 Jul 1996 12:55:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA16206; Thu, 4 Jul 1996 12:55:53 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA13427; Thu, 4 Jul 1996 12:53:36 -0700 From: Terry Lambert Message-Id: <199607041953.MAA13427@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: joelh@gnu.ai.mit.edu Date: Thu, 4 Jul 1996 12:53:36 -0700 (MST) Cc: terry@lambert.org, gpalmer@FreeBSD.ORG, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG In-Reply-To: <199607040559.BAA14799@kropotkin.gnu.ai.mit.edu> from "Joel Ray Holveck" at Jul 4, 96 01:59:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I had been responding to the symlink idea that jmb proposed. > > Is there any problem with symlinking /etc/passwd to something on a r/w > filesystem instead of dealing with NIS, to deal with pre-yp programs > that don't think to call getpwent()? I suppose that the /etc/ptmp > lockfile would have to be dealt with accordingly in that event, but > there should be ways to handle that. I don't think there is a problem with symlinking /etc/passwd; in theory, it's not in use until after the mounts are done. The lock wants to go into /var/spool/lock; since it's a mounted FS, it means that the directory structure should either be skeletonized then union mounted, so that the lock file can be created before the mount has taken place. For that matter, one can replace the passwd file with a union mount (I wonder if *this* was how the breakin was done?). > Where are the perms for /dev/tty* stored? Ideally, in the kernel. It's kind of bogus to make the distinction that rc.serial does to avoid what every other UNIX system in existance uses (except Microport or a SunOS machine with bad serial flags settings), the partial open hack. The idea is that an open with O_NDELAY allows an open without DCD present, and communication with the port. Since the O_NDELAY also also sets non-blocking I/O, the correction is to reopen the port *without* the O_NDELAY flag. Since a first open exists, the second open is not blocked pending DCD, even though DCD is not present, and a first open would block... that is, the second open succeeds, since the device is already "partially open". The idea that devices should be templated is a correct one. But using rc.serial to set the template values is incorrect. The template values can be set to the industry standard defaults, pending the DCD coming high. It is possible for programs (like getty) to set the defaults by using the now-open device. The magic is in then waiting for DCD. The *best* way to do this is to reset the partially open flag by specifying a blocking open (to be implemented by ioctl()) if in fact things need to be set. About the only thing that *does* need to be set in this category is the RTS/CTS out of band flow control. Note that an open prior to DCD being raised must assert outbound CTS/RTS and ingore-as-if-present inbound CTS/RTS. This allows use of a NULL-modem cable to bidirectionally permit logins over serial connections between directly connected machines, *without* falling into the "getty respawing too rapidly" trap from the getty's talking to each other. In point of fact, getty is supposed o override all port settings anyway with the gettytab defaults; this is traditional behaviour for support of SLIP or PPP as line disciplines. For mgetty, there was already a long discussion, the gist of which is that yet another open flag is necessary, to allow the open to remain incomplete pending a "ring indicate" signal. Ideally, you want this on the RS232 RI input, but could substitute one of the other signals in a pinch. This removes all of the lock/timer crap necessary for use of an mgetty port for outbound connections, as necessary (for instance, a UUCP mail or netnews relay site). This leaves the /etc/ttys and the /etc/gettytab, which are permitted to be symbolic links, since they will not be referenced until the RC file has completed the mount of /var. > > What's left is /etc/fstab (dealt with by mount changes, which > > aren't the same thing as FS changes), /etc/rc* (bogus) and > > /etc/sysconfig (also bogus). > > Hmmm... We may also want to change paths.h (and > src/sbin/nologin/nologin.5; why is it in that directory instead of > shutdown or login?) to take care of /etc/nologin, although shutdown > will work fine without changing it. (Just be sure to remove it > manually your first attempt to boot with / r/o!) Yes. There are a number of things, like the password lock file, that could be handled by lstat() to read the link target and pointing there instead. The password lock file could then always exist in /etc, without disrupting the vipw, etc.. This is a less elegant soloution than simply moving the target elsewhere and fixing the software (which is BSD software, after all). > Should the comment from /etc/rc concern us?: "root must be read/write > both for NFS diskless and for VFS LKMs before proceeding any further." The NFS diskless issue is an obvious one, and can be resolved through ordering. It is my firm opinion that system configuration data should be *data*, not procedurally encoded. I would desperately like to see a /etc/rc/... directory; I would prefer run levels, but could live with a single directory for third party startup insertions. Along with that, one would expect a /var/rc/... directory, to be mixed in. Run levels would allow "minimal system" setup before proceeding to a run level which should reference /var. For instance, "run level 1" would get /var and everything else mounted before proceeding to startups requiring a mounted /var. All third party startup script installation would go into /var, freeing us from the need to change /etc for local differences in function. This is slightly different from the SYSV interpretation of "run level", which more closes resembles "run states". I can choose to go from one state to another, and all necessary state transitions will take place automatically. This is the ideal; in reality, we probably won't be allowed to murder /etc/rc* in its sleep. The next best thing would be to have it call an rc on /var after the mounts have occurred. The runtime changes shiuld still go on /var, an the /etc directory can remain unchanged. > > I really don't see where the problem is: throw out your > > bogositieis and fix the rest to comply with the design documents, > > and the problems all fade away. > > Who said there's a problem? I can't fix the programs at the current > time (no net connection on my test machine, forgot to pay the phone > bill), so I'm just pointing 'em out. 8-). > I'm new at this; what design documents are you referring to? For the FS, the Heidemann thesis. For BSD in general, the 4.4 Daemon book. There's actually a *lot* of reference material out there that has already been designated "design document". I'd like to see some additional design documents "ratified", or for the VM and associated work, written. Hell, there's some things I ought to document. 8-). That's a different battle, for another time. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 4 13:11:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18133 for hackers-outgoing; Thu, 4 Jul 1996 13:11:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18119 for ; Thu, 4 Jul 1996 13:11:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA13455; Thu, 4 Jul 1996 13:06:56 -0700 From: Terry Lambert Message-Id: <199607042006.NAA13455@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: joelh@gnu.ai.mit.edu Date: Thu, 4 Jul 1996 13:06:56 -0700 (MST) Cc: terry@lambert.org, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.org In-Reply-To: <199607040616.CAA14851@kropotkin.gnu.ai.mit.edu> from "Joel Ray Holveck" at Jul 4, 96 02:16:12 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I cringe at the though of another branch of this thread, but here goes... > > > All file systems will have mount point vnode assignments as a result > > of a callback as a result of device probe. > > What about conflicting mount points? Conflicting mount points can be resolved by date. > Or suppose I'm diagnosing a dead /usr disk from another computer... > will I have to worry about my working /usr being overwritten, or > will there be some sort of identification, say, a timestamp written > to all disks late during bootup (after probe and hierarchy fill), > to ensure that they're on the same computer? There's one written already on shutdown. Actually, I was thinking more in terms of "System ID" to resolve the rest (the same function is used by locense managers for key generation). > And if so, how do we handle the whole point of sharing > these? Semaphores, first one to mount stamps? Unmount stamps. For a dead system, the mount/umount times will be earlier than the live system performing the diagnostics, since by definition, you will insert dead system volumes into a live system, instead of the other way around. 8-). > Danger: hair ahead. > > Actually, I don't quite recall the point of your augmented superblocks > to begin with. The point was to move some of the mount options out of /etc/fstab, should it be necessary (as was suggested). Personally, I don't believe it will be necessary. If all mounts are minimal mounts, like / is mounted during boot, then the on disk structure will not be modified, and the issue becomes one of mapping. Consider a DOS system (hold your jeers, please), which has a resource identifier per mountable volume, called "drive letter". I wouldn't go so far as to call it "A:, B:, C:, ...", since I think that's a limited (26, to be exact) soloution. But if you delay the mapping of the FS into the hierarchy until after the creation of a resource ID for it, then you can (fstab) dictate mapping by resource ID. For boot-required resources (like / or /var, if we have our way with /etc), an identifier can be written to the disk. We can identify volumes in our "volume set" by stamping the root create time on our own volumes, or some similar approach, and we can identify system critical mount points by resource identifiers (so if /var was last mounted on /mnt, we know to put it back on /var without being told by an fstab we can't access until we get it mounted). We are going to require some type of volume set identification method in any case to implement multiple volume spanning drivers for the logical-to-physical device translation layer that implements it (currently ccd) in the devfs. Volumes will need to be assembled (part 3 of 4, part 1 of 4, and the last one in the set will cause a call to the devfs_register_dev() to trigger the mount, etc.). > > It is unacceptable for the idea of sharing a read-only > > root among multiple clients, and must be discarded as historical > > cruft, which we may ignore at our leisure. > > Just so long as we don't break any code which depends on said > historical cruft, I'm all for it. I think symlinks brolke V7 "ls"... not to mention long names. 8-). I think the issue is remaining internally consistent and continuing to support programmatic tinterfaces which third parties and ABI services already depend on. We could go back to the previosu (tty) discussion to find an example of where we break ABI compliance (SCO and Solaris both want the partial open hack for running thirs party comm software under ABI emulation), for instance. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 4 14:22:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28485 for hackers-outgoing; Thu, 4 Jul 1996 14:22:54 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28473 for ; Thu, 4 Jul 1996 14:22:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA13601; Thu, 4 Jul 1996 14:14:59 -0700 From: Terry Lambert Message-Id: <199607042114.OAA13601@phaeton.artisoft.com> Subject: Re: What is the best way to setup a driver To: proff@suburbia.net (Julian Assange) Date: Thu, 4 Jul 1996 14:14:58 -0700 (MST) Cc: terry@lambert.org, joelh@gnu.ai.mit.edu, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@freebsd.org In-Reply-To: <199607040542.PAA00558@suburbia.net> from "Julian Assange" at Jul 4, 96 03:42:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The "/etc" directory is not allowed to be other than on the root file > > system, by definition. That resolves the symlink problem. > > This is not clear to me. Can you explain in more detail how this resolves > the problem? If /etc is not allowed to be a symlink, you do not have to worry about the target of the link not being mounted. One wonders how you would run /etc/rc to mount the volume with the link target to get at the rc file without first running the rc file in any case. Patient: "Doctor, it hurts when I do this..." Doctor: "Don't do that." Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 4 15:14:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06898 for hackers-outgoing; Thu, 4 Jul 1996 15:14:39 -0700 (PDT) Received: from kavemachine.magna.com.au (kavemachine.magna.com.au [203.4.215.219]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA06866 for ; Thu, 4 Jul 1996 15:14:34 -0700 (PDT) Received: (from kaveman@localhost) by kavemachine.magna.com.au (8.6.12/8.6.12) id IAA17084; Fri, 5 Jul 1996 08:14:50 +1000 Date: Fri, 5 Jul 1996 08:14:50 +1000 (EST) From: Julian Jenkins To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: What is the best way to setup a drive In-Reply-To: <199607041953.MAA13427@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Jul 1996, Terry Lambert wrote: > I don't think there is a problem with symlinking /etc/passwd; in theory, > it's not in use until after the mounts are done. Except when booting single user with an insecure console. :) > > I'm new at this; what design documents are you referring to? > > For the FS, the Heidemann thesis. Is there somewhere this can be downloaded from? Or some other way to get a copy? Kaveman kaveman@magna.com.au From owner-freebsd-hackers Thu Jul 4 15:58:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13368 for hackers-outgoing; Thu, 4 Jul 1996 15:58:25 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13356 for ; Thu, 4 Jul 1996 15:58:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA13790; Thu, 4 Jul 1996 15:55:33 -0700 From: Terry Lambert Message-Id: <199607042255.PAA13790@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: kaveman@magna.com.au (Julian Jenkins) Date: Thu, 4 Jul 1996 15:55:33 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: from "Julian Jenkins" at Jul 5, 96 08:14:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I don't think there is a problem with symlinking /etc/passwd; in theory, > > it's not in use until after the mounts are done. > > Except when booting single user with an insecure console. :) THere is no such thing as an insecure console, IMO. If they can use a screwdriver to remove the hard drive, single user non-password root access isn't a problem. > > > I'm new at this; what design documents are you referring to? > > > > For the FS, the Heidemann thesis. > > Is there somewhere this can be downloaded from? Or some other way to get > a copy? ftp.cs.ucla.edu Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 4 16:27:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17443 for hackers-outgoing; Thu, 4 Jul 1996 16:27:17 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17435; Thu, 4 Jul 1996 16:27:14 -0700 (PDT) Received: from localhost by misery.sdf.com with SMTP id <1237-12613>; Thu, 4 Jul 1996 16:36:57 -0800 Date: Thu, 4 Jul 1996 16:36:52 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: joelh@gnu.ai.mit.edu, gpalmer@FreeBSD.ORG, jmb@freefall.freebsd.org, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG Subject: Re: What is the best way to setup a drive In-Reply-To: <199607041953.MAA13427@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Jul 1996, Terry Lambert wrote: > I don't think there is a problem with symlinking /etc/passwd; in theory, > it's not in use until after the mounts are done. Well, actually the system never uses /etc/passwd at all. Now, if you were to symlink /etc/pwd.db and /etc/spwd.db somewhere else, you won't be able to login if you boot single-user on a insecure console. From owner-freebsd-hackers Fri Jul 5 00:11:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA26111 for hackers-outgoing; Fri, 5 Jul 1996 00:11:40 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA26103 for ; Fri, 5 Jul 1996 00:11:34 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.6.11/8.6.9) id JAA00318; Fri, 5 Jul 1996 09:11:27 GMT Date: Fri, 5 Jul 1996 09:11:27 +0000 () From: Andrzej Bialecki To: FreeBSD hackers Subject: running Linux ELF bins Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all, I wonder if it's possible to run Linux ELF binaries under FreeBSD. There is a linux_libs in port collection, but I'm not sure if it allows to run QMAGIC only, ELF 32 only, or both. There is virtually no documentation in handbook and FAQs concerning this issue... Andy PS. I'm not so curious by myself - I have some binaries that I _must_ run, but I don't want to install Linux for that, you know .... ;-> +------------------------------------------------------------------------+ | ANDRZEJ BIALECKI, , NASK (WARMAN) | | Research and Academic Network in Poland, Warsaw Area Network | | phone: (+48 22) 414115, Bartycka 18, 00-716 Warsaw, Poland | +------------------------------------------------------------------------+ -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2i mQCNAzFydDYAAAEEALAheWaKO7Uny4bAmT6AC2tEAPK+9VSUxX5ynA3f3yTQtXwL xovpwTQNCbqjBle8sME1hTIqgTkCHmucpucejc1z5zevdVPX4mOCeDcKOyeRf5VA XjI8YaPan/SiAfw5+GtXeiEbdf5N78Xd0old/vPKXwKebHCv7nhAoCU+bhJVAAUR tCZBbmRyemVqIEJpYWxlY2tpIDxhYmlhbEB3YXJtYW4ub3JnLnBsPg== =xasZ -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hackers Fri Jul 5 00:55:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA28050 for hackers-outgoing; Fri, 5 Jul 1996 00:55:56 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA28045 for ; Fri, 5 Jul 1996 00:55:53 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA24567; Fri, 5 Jul 1996 09:55:41 +0200 Message-Id: <199607050755.JAA24567@ra.dkuug.dk> Subject: Re: running Linux ELF bins To: abial@warman.org.pl (Andrzej Bialecki) Date: Fri, 5 Jul 1996 09:55:41 +0200 (MET DST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: from "Andrzej Bialecki" at Jul 5, 96 09:11:27 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Andrzej Bialecki who wrote: > > > Hi all, > > I wonder if it's possible to run Linux ELF binaries under FreeBSD. There > is a linux_libs in port collection, but I'm not sure if it allows to run > QMAGIC only, ELF 32 only, or both. There is virtually no documentation in > handbook and FAQs concerning this issue... If you get the linux_libs package and installs all the libs therein, you should be running both QMAGIC & ELF bins. The support in the kernel is allready there as a LKM. If you are having troubles with certain bins, let us know, maybe we have a fix for that allready... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-hackers Fri Jul 5 01:06:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28507 for hackers-outgoing; Fri, 5 Jul 1996 01:06:34 -0700 (PDT) Received: from mail0.iij.ad.jp (root@mail0.iij.ad.jp [192.244.176.61]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA28502 for ; Fri, 5 Jul 1996 01:06:30 -0700 (PDT) Received: from uucp1.iij.ad.jp (uucp1.iij.ad.jp [192.244.176.73]) by mail0.iij.ad.jp (8.6.12+2.4W/3.3W9-MAIL) with ESMTP id RAA08875 for ; Fri, 5 Jul 1996 17:06:27 +0900 Received: (from uucp@localhost) by uucp1.iij.ad.jp (8.6.12+2.4W/3.3W9-UUCP) with UUCP id RAA04162 for freebsd-hackers@FreeBSD.ORG; Fri, 5 Jul 1996 17:06:27 +0900 Received: from xxx.fct.kgc.co.jp by yyy.kgc.co.jp (8.7.5/3.4W:95122611) id OAA05731; Fri, 5 Jul 1996 14:47:14 +0900 (JST) Received: from localhost by xxx.fct.kgc.co.jp (8.6.12/3.3W8:95062916) id OAA15001; Fri, 5 Jul 1996 14:47:13 +0900 Message-Id: <199607050547.OAA15001@xxx.fct.kgc.co.jp> To: freebsd-hackers@FreeBSD.ORG Subject: test(1) -h behavior (bug??) X-Mailer: Mew version 1.06 on Emacs 19.28.2, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 05 Jul 1996 14:47:13 +0900 From: Toshihiro Kanda Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If a symbolic link file ``foo'' points non-existence file, should ``/bin/test foo'' return 0 or 1? In FreeBSD 2.1R, /bin/test returns 1. While built-in command `test' of `GNU bash, version 1.14.2(1)' returns 0. bash$ ln -s nofile foo bash$ /bin/test -h foo ; echo $? 1 bash$ test -h foo ; echo $? 0 I've tested `SunOS 4.1.3_U1 sun4c', `NetBSD 1.1 sparc' and `IRIX64 6.2 IP19'. Then all these /bin/test returned 0. candy@fct.kgc.co.jp (Toshihiro Kanda) From owner-freebsd-hackers Fri Jul 5 01:37:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA00643 for hackers-outgoing; Fri, 5 Jul 1996 01:37:18 -0700 (PDT) Received: from nike.efn.org (gurney_j@garcia.efn.org [198.68.17.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA00636 for ; Fri, 5 Jul 1996 01:37:15 -0700 (PDT) Received: from localhost (localhost.efn.org [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id BAA00666; Fri, 5 Jul 1996 01:37:31 -0700 (PDT) Date: Fri, 5 Jul 1996 01:37:29 -0700 (PDT) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Andrzej Bialecki cc: FreeBSD hackers Subject: Re: running Linux ELF bins In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Jul 1996, Andrzej Bialecki wrote: > > Hi all, > > I wonder if it's possible to run Linux ELF binaries under FreeBSD. There > is a linux_libs in port collection, but I'm not sure if it allows to run > QMAGIC only, ELF 32 only, or both. There is virtually no documentation in > handbook and FAQs concerning this issue... if you are running -current and you get the linux ELF binaries you can... I'm running quake over here with 2.2-960323-SNAP... just needed to get the elf binaries from a (wierd) friend of mine that is running linux... it runs quite nicely... if you would like I would be willing to send you the libs.... > Andy > > PS. I'm not so curious by myself - I have some binaries that I _must_ > run, but I don't want to install Linux for that, you know .... ;-> know what you mean :) John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-hackers Fri Jul 5 03:53:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA07298 for hackers-outgoing; Fri, 5 Jul 1996 03:53:29 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA07293 for ; Fri, 5 Jul 1996 03:53:26 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id KAA23720 for ; Fri, 5 Jul 1996 10:53:23 GMT Date: Fri, 5 Jul 1996 19:53:23 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: hackers@freebsd.org Subject: MAKEDEV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I added a Jaz drive to my system and screwed up my devices so I deleted them and recreated them. cd /dev rm sd2* rm rsd2* sh MAKEDEV sd2 This exits with an error in ttyminor(), expecting a ")" I then comment out ttyminor() sh MAKEDEV sd2 This time it works. What's the deal with ttyminor? The jaz drive seems to have an odd feature that the driver doesn't grok. What is the Invalid field in CDB error mean below? ncr0 rev 3 int a irq 10 on pci0:15 (ncr0:1:0): "SEAGATE ST32550N 0021" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2047MB (4194058 512 byte sectors) (ncr0:4:0): "TOSHIBA CD-ROM XM-3701TA 0236" type 5 removable SCSI 2 cd0(ncr0:4:0): CD-ROM cd0(ncr0:4:0): asynchronous. cd present [223645 x 2048 byte records] (ncr0:5:0): "iomega jaz 1GB G.60" type 0 removable SCSI 2 sd2(ncr0:5:0): Direct-Access sd2(ncr0:5:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd2(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry 1021MB (2091050 512 byte sectors) -mike hancock From owner-freebsd-hackers Fri Jul 5 04:06:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA07901 for hackers-outgoing; Fri, 5 Jul 1996 04:06:22 -0700 (PDT) Received: from cyberport.com (root@puma.cyberport.com [204.134.75.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA07880; Fri, 5 Jul 1996 04:06:12 -0700 (PDT) Received: from hippo.cyberport.com (kevin@hippo.cyberport.com [204.134.75.2]) by cyberport.com (8.7.5/8.7.3) with SMTP id FAA08811; Fri, 5 Jul 1996 05:06:10 -0600 (MDT) Date: Fri, 5 Jul 1996 05:06:11 -0600 (MDT) From: Kevin Rosenberg To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Can file accessed time be disabled? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've heard of someone who has disabled the directory updating of last accessed time for files. They found a significant improvement in their news server performance. For a news server, storing last accessed time is not particularly important. I've glanced through the code, but I am unsure where to disable the writing of last access time in directory. Has anyone ever done this with FreeBSD? -------------------------------------------------------------------- Kevin Rosenberg | CyberPort Station Chief System Administrator | The Finest Internet Service Possible! kevin@cyberport.com | http://www.cyberport.com Finger kevin@cyberport.com for PGP Public Key -------------------------------------------------------------------- From owner-freebsd-hackers Fri Jul 5 05:15:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA11895 for hackers-outgoing; Fri, 5 Jul 1996 05:15:50 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA11888; Fri, 5 Jul 1996 05:15:47 -0700 (PDT) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.7.5/jtpda-5.2) with ESMTP id OAA05710 ; Fri, 5 Jul 1996 14:15:45 +0200 (METDST) Received: from angrand.prism.uvsq.fr (angrand.prism.uvsq.fr [193.51.25.85]) by guillotin.prism.uvsq.fr (8.7.5/jtpda-5.2) with ESMTP id OAA12377 ; Fri, 5 Jul 1996 14:15:44 +0200 (MET DST) Received: from (son@localhost) by angrand.prism.uvsq.fr (8.7.5/jtpda-5.2) id PAA00393 ; Fri, 5 Jul 1996 15:18:27 +0200 (MET DST) Date: Fri, 5 Jul 1996 15:18:27 +0200 (MET DST) Message-Id: <199607051318.PAA00393@angrand.prism.uvsq.fr> From: Nicolas Souchu To: freebsd-announce@freebsd.org CC: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk linux-parport@torque.net, grant@torque.net Subject: Iomega Zip 100 PPA3 driver The Iomega Zip 100 drive is an external drive with removable 100Mo disks. It is connected either to the parallel port (with an embedded SCSI-2 adapter) or to a SCSI-2 adapter. An IDE version is also available. The driver allows you to access the Iomega Zip 100 parallel drive throw your favorite msdos filesystem. It is a port of the Linux driver to FreeBSD R2.1.0. see http://www.prism.uvsq.fr/~son/ppa3.html nicolas -- Nicolas.Souchu@prism.uvsq.fr Laboratoire PRiSM - Versailles, FRANCE From owner-freebsd-hackers Fri Jul 5 06:42:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17009 for hackers-outgoing; Fri, 5 Jul 1996 06:42:55 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA17003; Fri, 5 Jul 1996 06:42:49 -0700 (PDT) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.7.5/jtpda-5.2) with ESMTP id PAA07253 ; Fri, 5 Jul 1996 15:42:44 +0200 (METDST) Received: from sisley.prism.uvsq.fr (sisley.prism.uvsq.fr [193.51.25.73]) by guillotin.prism.uvsq.fr (8.7.5/jtpda-5.2) with ESMTP id PAA13516 ; Fri, 5 Jul 1996 15:42:42 +0200 (MET DST) Received: from (son@localhost) by sisley.prism.uvsq.fr (8.7.3/jtpda-5.1) id PAA00795 ; Fri, 5 Jul 1996 15:42:40 +0200 (MET DST) Date: Fri, 5 Jul 1996 15:42:40 +0200 (MET DST) Message-Id: <199607051342.PAA00795@sisley.prism.uvsq.fr> From: Nicolas SOUCHU To: freebsd-announce@freebsd.org CC: linux-parport@torque.net, freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org, grant@torque.net Subject: Iomega Zip 100 PPA3 driver Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry, the previous mail had no subject... The Iomega Zip 100 drive is an external drive with removable 100Mo disks. It is connected either to the parallel port (with an embedded SCSI-2 adapter) or to a SCSI-2 adapter. An IDE version is also available. The driver allows you to access the Iomega Zip 100 parallel drive throw your favorite msdos filesystem. It is a port of the Linux driver to FreeBSD R2.1.0. see http://www.prism.uvsq.fr/~son/ppa3.html nicolas -- Nicolas.Souchu@prism.uvsq.fr From owner-freebsd-hackers Fri Jul 5 07:50:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA20947 for hackers-outgoing; Fri, 5 Jul 1996 07:50:12 -0700 (PDT) Received: from alpha.dsu.edu (ghelmer@alpha.dsu.edu [138.247.32.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA20942 for ; Fri, 5 Jul 1996 07:50:08 -0700 (PDT) Received: from localhost (ghelmer@localhost) by alpha.dsu.edu (8.7.5/8.7.3) with SMTP id JAA09087; Fri, 5 Jul 1996 09:50:00 -0500 (CDT) Date: Fri, 5 Jul 1996 09:49:59 -0500 (CDT) From: Guy Helmer To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Is there a real live actual working deluser script? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Jul 1996, Jaye Mathisen wrote: > Even if it's rudimentary? I did a search on -hackers, and there's lots of > talk about it, and about how complicated it would be, and on and on, but > no actual script, and I don't see a port or a package. My latest version of removeuser is at ftp://ftp.dsu.edu/pub/FreeBSD/ghelmer/removeuser-2-beta.tar.gz Improvements include: Removes user's crontab and at jobs No longer requires h2ph'ed versions of several files in /usr/include/machine - just install and use Uses "rm -rf" to remove user's home directory instead of removing it by hand (therefore avoids problems with uchg flag) Catches most non-fatal errors and issues warnings Maintains ownership and privileges of /etc/group after modification This code is new and should be treated as such - please test it out and let me know if you find any problems. Thanks, Guy Helmer Guy Helmer, Dakota State University Computing Services - ghelmer@alpha.dsu.edu From owner-freebsd-hackers Fri Jul 5 09:00:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27352 for hackers-outgoing; Fri, 5 Jul 1996 09:00:48 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA27315; Fri, 5 Jul 1996 09:00:42 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id RAA28514; Fri, 5 Jul 1996 17:02:50 +0100 Date: Fri, 5 Jul 1996 17:02:49 +0100 (BST) From: Developer To: Gary Palmer cc: hackers@FreeBSD.ORG Subject: Re: Help V2.2 doesn't work - solved In-Reply-To: <8114.836334014@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Jul 1996, Gary Palmer wrote: > Developer wrote in message ID > : > > > > I was wondering if anyone else has had any success in getting the new V2.2 > > kernel to run on their PC.. V2,1 runs fine for me on a wide variety of > > machines but V2.2 just resets right at the start before I even see any > > devices being scanned??!! > > You mean the -current kernel? Yes, I have a machine here which can run > 2.2 quite easily ... What sort of hardware are you using? Ive finally solved it:)) I updated the boot strap code on the drive to the new one and it worked:) Thanks for all your help. Regards, Trefor S. From owner-freebsd-hackers Fri Jul 5 10:24:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11080 for hackers-outgoing; Fri, 5 Jul 1996 10:24:10 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11020 for ; Fri, 5 Jul 1996 10:24:01 -0700 (PDT) Received: from campa.panke.de (anonymous234.ppp.cs.tu-berlin.de [130.149.17.234]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id TAA01668; Fri, 5 Jul 1996 19:18:50 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id TAA00676; Fri, 5 Jul 1996 19:10:04 +0200 Date: Fri, 5 Jul 1996 19:10:04 +0200 From: Wolfram Schneider Message-Id: <199607051710.TAA00676@campa.panke.de> To: Toshihiro Kanda Cc: freebsd-hackers@FreeBSD.org Subject: test(1) -h behavior (bug??) In-Reply-To: <199607050547.OAA15001@xxx.fct.kgc.co.jp> References: <199607050547.OAA15001@xxx.fct.kgc.co.jp> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Already fixed. test.c revision 1.12 date: 1995/10/28 11:54:42; author: ache; state: Exp; lines: +2 -2 Fix -h option: sense symlink even it is unresolved Toshihiro Kanda writes: > If a symbolic link file ``foo'' points non-existence file, should >``/bin/test foo'' return 0 or 1? > > In FreeBSD 2.1R, /bin/test returns 1. While built-in command `test' >of `GNU bash, version 1.14.2(1)' returns 0. > > bash$ ln -s nofile foo > bash$ /bin/test -h foo ; echo $? > 1 > bash$ test -h foo ; echo $? > 0 > > I've tested `SunOS 4.1.3_U1 sun4c', `NetBSD 1.1 sparc' and `IRIX64 >6.2 IP19'. Then all these /bin/test returned 0. > >candy@fct.kgc.co.jp (Toshihiro Kanda) From owner-freebsd-hackers Fri Jul 5 12:08:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27226 for hackers-outgoing; Fri, 5 Jul 1996 12:08:15 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA27174 for ; Fri, 5 Jul 1996 12:08:07 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA18333 for ; Fri, 5 Jul 1996 12:08:00 -0700 (PDT) To: hackers@freebsd.org Subject: How would you like the FreeBSD DOC CD presented/indexed? Date: Fri, 05 Jul 1996 12:08:00 -0700 Message-ID: <18315.836593680@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Those of you who got the previous DOC CD (or heard me talk about it) know that: 1. I had nothing to do with it. 2. I was not particularly pleased at how it was put together. To be specific, it wasn't very easy to use and the data was not provided in a format that lent itself to searching or re-use. Now, as a direct result of #2, #1 has changed - I'm going to do the next DOC CD and I'm currently looking over ways of presenting the data. My basic concept so far is that I'll provide the news in its original form along with a tiny "nntp" equivalent that just delivers the news off the CDROM to a standard newsreader configured to point at localhost, and the mailing lists will be provided also in raw form with a pre-created glimpse databse for easy searching. Anything else people would like to see on this CD, or ways in which they'd like the news/mail indexed? Please speak up now! :-) Thanks! Jordan From owner-freebsd-hackers Fri Jul 5 12:17:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29051 for hackers-outgoing; Fri, 5 Jul 1996 12:17:45 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29035 for ; Fri, 5 Jul 1996 12:17:42 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id UAA17246; Fri, 5 Jul 1996 20:14:54 +0100 (BST) To: sos@FreeBSD.ORG cc: abial@warman.org.pl (Andrzej Bialecki), freebsd-hackers@freefall.freebsd.org From: "Gary Palmer" Subject: Re: running Linux ELF bins In-reply-to: Your message of "Fri, 05 Jul 1996 09:55:41 +0200." <199607050755.JAA24567@ra.dkuug.dk> Date: Fri, 05 Jul 1996 20:14:53 +0100 Message-ID: <17244.836594093@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org wrote in message ID <199607050755.JAA24567@ra.dkuug.dk>: > In reply to Andrzej Bialecki who wrote: > > > > > > Hi all, > > > > I wonder if it's possible to run Linux ELF binaries under FreeBSD. There > > is a linux_libs in port collection, but I'm not sure if it allows to run > > QMAGIC only, ELF 32 only, or both. There is virtually no documentation in > > handbook and FAQs concerning this issue... > > If you get the linux_libs package and installs all the libs therein, you > should be running both QMAGIC & ELF bins. The support in the kernel is > allready there as a LKM. What Soren forgot to mention was that you need to be running -current in order to use ELF binaries. -stable (and hence 2.1-RELEASE and the forthcoming 2.1.5-RELEASE) does NOT support ELF binaries. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Fri Jul 5 12:33:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02490 for hackers-outgoing; Fri, 5 Jul 1996 12:33:12 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02474 for ; Fri, 5 Jul 1996 12:33:05 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id MAA00445 for ; Fri, 5 Jul 1996 12:33:03 -0700 (PDT) Message-Id: <199607051933.MAA00445@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: hackers@FreeBSD.ORG Subject: thread support in gdb for -current?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jul 1996 12:33:02 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Now that we have thread support in -current it will be very nice if someone could add thread support in gdb. The latest version of gdb has thread support for Irix and Linx so at the very least the current thread support in gdb serves as an example. Tnks! Amancio From owner-freebsd-hackers Fri Jul 5 12:38:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03445 for hackers-outgoing; Fri, 5 Jul 1996 12:38:11 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA03417 for ; Fri, 5 Jul 1996 12:38:03 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.6.11/8.6.9) id VAA05980; Fri, 5 Jul 1996 21:37:46 GMT Date: Fri, 5 Jul 1996 21:37:45 +0000 () From: Andrzej Bialecki To: Gary Palmer cc: sos@FreeBSD.ORG, freebsd-hackers@freefall.freebsd.org Subject: Re: running Linux ELF bins In-Reply-To: <17244.836594093@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you all for answering my question. It's good to have a hacker nearby... 8) Andy +------------------------------------------------------------------------+ | ANDRZEJ BIALECKI, , NASK (WARMAN) | | Research and Academic Network in Poland, Warsaw Area Network | | phone: (+48 22) 414115, Bartycka 18, 00-716 Warsaw, Poland | +------------------------------------------------------------------------+ -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2i mQCNAzFydDYAAAEEALAheWaKO7Uny4bAmT6AC2tEAPK+9VSUxX5ynA3f3yTQtXwL xovpwTQNCbqjBle8sME1hTIqgTkCHmucpucejc1z5zevdVPX4mOCeDcKOyeRf5VA XjI8YaPan/SiAfw5+GtXeiEbdf5N78Xd0old/vPKXwKebHCv7nhAoCU+bhJVAAUR tCZBbmRyemVqIEJpYWxlY2tpIDxhYmlhbEB3YXJtYW4ub3JnLnBsPg== =xasZ -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hackers Fri Jul 5 13:07:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05925 for hackers-outgoing; Fri, 5 Jul 1996 13:07:01 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05920 for ; Fri, 5 Jul 1996 13:06:56 -0700 (PDT) Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id QAA09584; Fri, 5 Jul 1996 16:00:40 -0400 (EDT) Received: from netrix.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA07819; Fri, 5 Jul 1996 16:00:39 -0400 Received: from localhost by netrix.lkg.dec.com; (5.65v3.2/1.1.8.2/28May95-0415PM) id AA11110; Fri, 5 Jul 1996 16:00:52 -0400 Message-Id: <9607052000.AA11110@netrix.lkg.dec.com> To: tech-kern@netbsd.org, freebsd-hackers@freebsd.org Subject: Some interesting papers on BSD ... Date: Fri, 05 Jul 96 16:00:52 -0400 From: Matt Thomas X-Mts: smtp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While for something else, I ran across these 3 papers... ftp://deas-ftp.harvard.edu/techreports/tr-31-95.ps.gz TR-31-95 [tr-31-95.ps.gz (61 K)] Christopher Small and Margo Seltzer. 1995. ``Scheduler Activations on BSD: Sharing Thread Management Between Kernel and Application.'' There are two commonly used thread models: kernel level threads and user level threads. Kernel level threads suffer from the cost of frequent user-kernel domain crossings and fixed kernel scheduling priorities. User level threads are not integrated with the kernel, blocking all threads whenever one thread is blocked. The Scheduler Activations model, proposed by Anderson et al., combines kernel CPU allocation decisions with application control over thread scheduling. This paper discusses the performance characteristics of an implementation of Scheduler Activations for a uniprocessor BSD system, and proposes an analytic model for determining the class of applications that benefit from its use. Our implementation required fewer than two hundred lines of kernel code and provides an order of magnitude performance improvement over process-level facilities. ftp://deas-ftp.harvard.edu/techreports/tr-19-95.ps.gz TR-19-95 [tr-19-95.ps.gz (541 K)] Diane L. Tang. 1995. ``Benchmarking Filesystems.'' One of the most widely researched areas in operating systems is filesystem design, implementation, and performance. Almost all of the research involves reporting performance numbers gathered from a variety of different benchmarks. The problem with such results is that existing filesystem benchmarks are inadequate, suffering from problems ranging from not scaling with advancing technology to not measuring the filesystem. A new approach to filesystem benchmarking is presented here. This methodology is designed both to help system designers understand and improve existing systems and to help users decide which filesystem to buy or run. For usability, the benchmark is separated into two parts: a suite of micro-benchmarks, which is actually run on the filesystem, and a workload characterizer. The results from the two separate parts can be combined to predict the performance of the filesystem on the workload. The purpose for this separation of functionality is two-fold. First, many system designers would like their filesystem to perform well under diverse workloads: by characterizing the workload independently, the designers can better understand what is required of the filesystem. The micro-benchmarks tell the designer what needs to be improved while the workload characterizer tells the designer whether that improvement will affect filesystem performance under that workload. This separation also helps users trying to decide which system to run or buy, who may not be able to run their workload on all systems under consideration, and therefore need this separation. The implementation of this methodology does not suffer from many of the problems seen in existing benchmarks: it scales with technology, it is tightly specified, and it helps system designers. This benchmark's only drawbacks are that it does not accurately predict the performance of a filesystem on a workload, thus limiting its applicability: it is useful to system designers, but not for users trying to decide which system to buy. The belief is that the general approach will work, given additional time to manipulate the prediction algorithm. ftp://deas-ftp.harvard.edu/techreports/tr-09-95.ps.gz TR-09-95 [tr-09-95.ps.gz (77 K)] J. Bradley Chen, Yasuhiro Endo, Kee Chan, David Mazieres, Antonio Dias, Margo Seltzer, and Michael Smith. 1995. ``The Impact of Operating System Structure on Personal Computer Performance.'' This paper presents a comparative study of the performance of three operating systems that run on the personal computer architecture derived from the IBM-PC. The operating systems, Windows for Workgroups (tm), Windows NT (tm), and NetBSD (a freely available UNIX (tm) variant) cover a broad range of system functionality and user requirements, from a single address space model to full protection with preemptive multitasking. Our measurements were enabled by hardware counters in Intel's Pentium (tm) processor that permit measurement of a broad range of processor events including instruction counts and on-chip cache miss rates. We used both microbenchmarks, which expose specific differences between the systems, and application workloads, which provide an indication of expected end-to-end performance. Our microbenchmark results show that accessing system functionality is more expensive in Windows than in the other two systems due to frequent changes in machine mode and the use of system call hooks. When running native applications, Windows NT is more efficient than Windows, but it does incur overhead from its microkernel structure. Overall, system functionality can be accessed most efficiently in NetBSD; we attribute this to its monolithic structure, and to the absence of the complications created by backwards compatibility in the other sys tems. Measurements of application performance show that the impact of these differences is significant in terms of overall execution time. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-hackers Fri Jul 5 13:13:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06416 for hackers-outgoing; Fri, 5 Jul 1996 13:13:23 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA06397 for ; Fri, 5 Jul 1996 13:13:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA15385; Fri, 5 Jul 1996 13:10:09 -0700 From: Terry Lambert Message-Id: <199607052010.NAA15385@phaeton.artisoft.com> Subject: Re: How would you like the FreeBSD DOC CD presented/indexed? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 5 Jul 1996 13:10:08 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <18315.836593680@time.cdrom.com> from "Jordan K. Hubbard" at Jul 5, 96 12:08:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Those of you who got the previous DOC CD (or heard me talk about it) > know that: > > 1. I had nothing to do with it. > > 2. I was not particularly pleased at how it was put together. > To be specific, it wasn't very easy to use and the data was not > provided in a format that lent itself to searching or re-use. > > Now, as a direct result of #2, #1 has changed - I'm going to do the > next DOC CD and I'm currently looking over ways of presenting the > data. My basic concept so far is that I'll provide the news in its > original form along with a tiny "nntp" equivalent that just delivers > the news off the CDROM to a standard newsreader configured to point at > localhost, and the mailing lists will be provided also in raw form > with a pre-created glimpse databse for easy searching. > > Anything else people would like to see on this CD, or ways in which > they'd like the news/mail indexed? Please speak up now! :-) I would like to see the mail archives threaded. I don't know if the message ID field has been there long enough to do this, though. I would like to see included binaries for some type of HTML reader. I would like to see a file in the top level called "autorun.sh" that invokes the binary for the reader on the start of the index page. Wiring for "autorunning" will eventually go into BSD at some point in time for insertion-based activation. I'd like to see everything use relative paths, or an implicit relative root. You can assume that the autorun.sh will be started with the directory containing it as the current directory. Since the browser would be included, I'd like to see the HTML take specific advantage of the browser capabilities instead of being minimallist. A forms-based interface is the next best thing to a "books on line" style interface. I'd like to see auto-insertion of cross references in the standard documentation. In short, I'd like to see more than you could possibly pack into the available time. 8-) 8-). I know some tradeoffs need to be made, but still... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jul 5 14:26:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12732 for hackers-outgoing; Fri, 5 Jul 1996 14:26:43 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA12721 for ; Fri, 5 Jul 1996 14:26:36 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id OAA15823; Fri, 5 Jul 1996 14:24:21 -0700 (PDT) Message-Id: <199607052124.OAA15823@ref.tfs.com> Subject: Re: Some interesting papers on BSD ... To: thomas@lkg.dec.com (Matt Thomas) Date: Fri, 5 Jul 1996 14:24:20 -0700 (PDT) From: "JULIAN Elischer" Cc: tech-kern@netbsd.org, freebsd-hackers@freebsd.org In-Reply-To: <9607052000.AA11110@netrix.lkg.dec.com> from "Matt Thomas" at Jul 5, 96 04:00:52 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk just resonding to let you know that I appreciate the pointers.. :) julian > > > > While for something else, I ran across these 3 papers... > > ftp://deas-ftp.harvard.edu/techreports/tr-31-95.ps.gz [...] From owner-freebsd-hackers Fri Jul 5 14:58:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14717 for hackers-outgoing; Fri, 5 Jul 1996 14:58:21 -0700 (PDT) Received: from haldjas.folklore.ee ([193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA14579 for ; Fri, 5 Jul 1996 14:55:43 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id WAA04379; Wed, 3 Jul 1996 22:18:17 +0300 Date: Wed, 3 Jul 1996 22:18:17 +0300 (EET DST) From: Narvi To: Don Yuniskis cc: dunn@harborcom.net, dgy@rtd.com, hackers@FreeBSD.org Subject: Re: Are you a programmer? Do you wear glasses? In-Reply-To: <199607011310.GAA00190@seagull.rtd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Jul 1996, Don Yuniskis wrote: > > > Could someone please UUENCODE (i.e. *expand*) the CVS hierarchy and > > > mail it to this guy? Maybe 10K each day for the next year or so? > > > > :). AOL has like a 300K limit on mail messages. Probably because > > people who use AOL tend to piss other people off. > > Actually, aren't the lists set up so that only subscribers can post > to the lists? Or, is that considered too "unfriendly"? It should be possible for unsubscribed people to send messages to the lists - they might for example get involved in the cc: lists... And it would be no good if their messages to that list mysteriously disappared or even bounced... Sander > > --don > From owner-freebsd-hackers Fri Jul 5 15:49:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17544 for hackers-outgoing; Fri, 5 Jul 1996 15:49:06 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17538 for ; Fri, 5 Jul 1996 15:48:59 -0700 (PDT) Received: (from mark@localhost) by scooter.quickweb.com (8.7.5/8.6.12) id SAA26718; Fri, 5 Jul 1996 18:50:09 -0400 (EDT) Date: Fri, 5 Jul 1996 18:50:08 -0400 (EDT) From: Mark Mayo To: hackers@freebsd.org Subject: Re: How would you like the FreeBSD DOC CD presented/indexed? In-Reply-To: <199607052010.NAA15385@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Jul 1996, Terry Lambert wrote: > > Those of you who got the previous DOC CD (or heard me talk about it) > > know that: > > > > 1. I had nothing to do with it. > > > > 2. I was not particularly pleased at how it was put together. > > To be specific, it wasn't very easy to use and the data was not > > provided in a format that lent itself to searching or re-use. > > > > they'd like the news/mail indexed? Please speak up now! :-) > > > I would like to see included binaries for some type of HTML reader. I second this. Having the docs in html format is a great idea. As a bare minimum, include lynx, and maybe Mosaic (netscape would be super, but I'm sure it's impossible to license for free..) Personally, I like having the doc CD available on my machine (remote) so I can point an httpd document root to it. Then I can get to the stuff easily from at home, at work, etc.. > > I would like to see a file in the top level called "autorun.sh" > that invokes the binary for the reader on the start of the index > page. Wiring for "autorunning" will eventually go into BSD at > some point in time for insertion-based activation. > Neat idea. I like this one too, and the relative paths are of course mandatory so people can move the collection around :-) Autorun (although it smells like win95) is a great feature, especially for novice FreeBSD'ers. > I'd like to see everything use relative paths, or an implicit relative > root. You can assume that the autorun.sh will be started with the > directory containing it as the current directory. > > > -Mark :%t$sig -- Oops, thought I was in vi.. ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- From owner-freebsd-hackers Fri Jul 5 17:09:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21388 for hackers-outgoing; Fri, 5 Jul 1996 17:09:12 -0700 (PDT) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21383 for ; Fri, 5 Jul 1996 17:09:09 -0700 (PDT) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.7.3) with SMTP id RAA00728 for ; Fri, 5 Jul 1996 17:08:57 -0700 (PDT) X-Authentication-Warning: schizo.cdsnet.net: mrcpu owned process doing -bs Date: Fri, 5 Jul 1996 17:08:57 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Cool! DPT RAID Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk DPT released source for a driver for BSD/OS 2.1 and their RAID controller card today. While I have not the technical skill to incorporate the driver, I could probably acquire a card if somebody is willing to do some serious work on the card... If interested, let me know. From owner-freebsd-hackers Fri Jul 5 17:27:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21959 for hackers-outgoing; Fri, 5 Jul 1996 17:27:11 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA21945 for ; Fri, 5 Jul 1996 17:27:05 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0uc88q-000QcuC; Fri, 5 Jul 96 12:29 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id MAA15302 for hackers@freebsd.org; Fri, 5 Jul 1996 12:11:51 +0200 Message-Id: <199607051011.MAA15302@allegro.lemis.de> Subject: gcc lies? To: hackers@freebsd.org (FreeBSD Hackers) Date: Fri, 5 Jul 1996 12:11:51 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I ran into a bug in gcc yesterday: certain initializers caused it to SIGSEGV. Before sending in a bug report, I tried it with the BSD/OS cc, and it worked fine. So I ported 2.7.2, and that worked fine as well, so I decided not to file a bug report (though I do intend to try it with the released version of 2.7.2). So I installed 2.7.2 as my standard compiler, and hey! suddenly I get thousands of warnings from my kernel builds. For example, gcc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -g -nostdinc -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DI586_CPU -DHARDFONTS -DSCSIDEBUG -DIPACCT -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../kern/kern_descrip.c ../../kern/kern_descrip.c: In function `getdtablesize': ../../kern/kern_descrip.c:99: warning: unused parameter `uap' ../../kern/kern_descrip.c: In function `dup2': ../../kern/kern_descrip.c:127: warning: comparison between signed and unsigned ../../kern/kern_descrip.c:130: warning: comparison between signed and unsigned ../../kern/kern_descrip.c:136: warning: comparison between signed and unsigned ../../kern/kern_descrip.c:139: warning: comparison between signed and unsigned ../../kern/kern_descrip.c: In function `dup': ../../kern/kern_descrip.c:181: warning: comparison between signed and unsigned ../../kern/kern_descrip.c: In function `fcntl': ../../kern/kern_descrip.c:213: warning: comparison between signed and unsigned ../../kern/kern_descrip.c:222: warning: comparison between signed and unsigned ../../kern/kern_descrip.c: In function `close': (that's not all, but it's enough). If I compile the same module with the standard release gcc, I get no warnings at all. How come? At first I thought it might be the header files, but there's a -nostdinc in there, and I checked: it really does include just the kernel header files. Greg From owner-freebsd-hackers Fri Jul 5 18:20:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24171 for hackers-outgoing; Fri, 5 Jul 1996 18:20:21 -0700 (PDT) Received: from Gatekeeper.lamb.net (root@Gatekeeper.Lamb.net [206.169.44.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24165 for ; Fri, 5 Jul 1996 18:20:17 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.lamb.net (8.7.5/8.7.3) id SAA21547; Fri, 5 Jul 1996 18:18:27 -0700 (PDT) From: "Ulf Zimmermann" Message-Id: <960705181827.ZM21545@Gatekeeper.Lamb.net> Date: Fri, 5 Jul 1996 18:18:27 -0700 In-Reply-To: Jaye Mathisen "Cool! DPT RAID" (Jul 5, 5:08pm) References: X-Mailer: Z-Mail (4.0b.514 14may96) To: Jaye Mathisen , hackers@freebsd.org Subject: Re: Cool! DPT RAID MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 5, 5:08pm, Jaye Mathisen wrote: > Subject: Cool! DPT RAID > > > DPT released source for a driver for BSD/OS 2.1 and their RAID controller > card today. While I have not the technical skill to incorporate the > driver, I could probably acquire a card if somebody is willing to do some > serious work on the card... > > If interested, let me know. > >-- End of excerpt from Jaye Mathisen Sure, always. :) Waiting for that a long time. I once talked with someone from DPT, they said at that time, if enough people would ask for the controller and driver for FreeBSD, they would do it. Ulf. -- --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 From owner-freebsd-hackers Fri Jul 5 18:34:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25293 for hackers-outgoing; Fri, 5 Jul 1996 18:34:43 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA25285 for ; Fri, 5 Jul 1996 18:34:38 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id SAA01781; Fri, 5 Jul 1996 18:34:18 -0700 (PDT) Message-Id: <199607060134.SAA01781@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Cool! DPT RAID In-reply-to: Your message of Fri, 05 Jul 96 17:08:57 -0700. Date: Fri, 05 Jul 1996 18:34:15 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >DPT released source for a driver for BSD/OS 2.1 and their RAID controller >card today. While I have not the technical skill to incorporate the >driver, I could probably acquire a card if somebody is willing to do some >serious work on the card... It's already in progress. But it's still in the very early stages. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Fri Jul 5 19:18:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA29524 for hackers-outgoing; Fri, 5 Jul 1996 19:18:42 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA29518 for ; Fri, 5 Jul 1996 19:18:36 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id CAA28969; Sat, 6 Jul 1996 02:18:25 GMT Date: Sat, 6 Jul 1996 11:18:25 +0900 (JST) From: Michael Hancock To: Greg Lehey cc: FreeBSD Hackers Subject: Re: gcc lies? In-Reply-To: <199607051011.MAA15302@allegro.lemis.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is probably why BSDI uses gcc 1.x for the kernel and gives their screaming customers 2.7.2. -mike hancock On Fri, 5 Jul 1996, Greg Lehey wrote: > I ran into a bug in gcc yesterday: certain initializers caused it to > SIGSEGV. Before sending in a bug report, I tried it with the BSD/OS > cc, and it worked fine. So I ported 2.7.2, and that worked fine as > well, so I decided not to file a bug report (though I do intend to try > it with the released version of 2.7.2). > > So I installed 2.7.2 as my standard compiler, and hey! suddenly I get > thousands of warnings from my kernel builds. For example, > > gcc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -g -nostdinc -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DI586_CPU -DHARDFONTS -DSCSIDEBUG -DIPACCT -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../kern/kern_descrip.c > ../../kern/kern_descrip.c: In function `getdtablesize': > ../../kern/kern_descrip.c:99: warning: unused parameter `uap' > ../../kern/kern_descrip.c: In function `dup2': > ../../kern/kern_descrip.c:127: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:130: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:136: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:139: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `dup': > ../../kern/kern_descrip.c:181: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `fcntl': > ../../kern/kern_descrip.c:213: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:222: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `close': > > (that's not all, but it's enough). > > If I compile the same module with the standard release gcc, I get no > warnings at all. How come? At first I thought it might be the header > files, but there's a -nostdinc in there, and I checked: it really does > include just the kernel header files. > > Greg > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F 2-5-12, Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 From owner-freebsd-hackers Fri Jul 5 20:58:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08027 for hackers-outgoing; Fri, 5 Jul 1996 20:58:53 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA08021 for ; Fri, 5 Jul 1996 20:58:48 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id UAA22247 for hackers@freebsd.org; Fri, 5 Jul 1996 20:58:48 -0700 Date: Fri, 5 Jul 1996 20:58:48 -0700 From: Sean Eric Fagan Message-Id: <199607060358.UAA22247@kithrup.com> To: hackers@freebsd.org Subject: patches to mail -- thoughts, comments? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This adds a "|" command to Mail. I'm not extremely happy with it, mind you, which is why I'm soliciting comments ;). These are relative to my sources, but should apply with some fuzz to stock freebsd sources ;). *** /usr/src/usr.bin/mail/cmd2.c Sat Jun 12 07:50:30 1993 --- cmd2.c Fri Jul 5 20:56:28 1996 *************** *** 145,150 **** --- 145,156 ---- return save1(str, 0, "copy", saveignore); } + pipeto(str) + char str[]; + { + return save1(str, 0, "pipe", saveignore); + } + /* * Save/copy the indicated messages at the end of the passed file name. * If mark is true, mark the message "saved." *************** *** 157,166 **** register int *ip; register struct message *mp; char *file, *disp; ! int f, *msgvec; FILE *obuf; msgvec = (int *) salloc((msgCount + 2) * sizeof *msgvec); if ((file = snarf(str, &f)) == NOSTR) return(1); if (!f) { --- 163,174 ---- register int *ip; register struct message *mp; char *file, *disp; ! int f, *msgvec, dopipe; FILE *obuf; msgvec = (int *) salloc((msgCount + 2) * sizeof *msgvec); + dopipe = !strcmp(cmd, "pipe"); + if ((file = snarf(str, &f)) == NOSTR) return(1); if (!f) { *************** *** 173,187 **** } if (f && getmsglist(str, msgvec, 0) < 0) return(1); if ((file = expand(file)) == NOSTR) return(1); printf("\"%s\" ", file); fflush(stdout); ! if (access(file, 0) >= 0) disp = "[Appended]"; else disp = "[New file]"; ! if ((obuf = Fopen(file, "a")) == NULL) { perror(NOSTR); return(1); } --- 181,218 ---- } if (f && getmsglist(str, msgvec, 0) < 0) return(1); + if (!dopipe) { if ((file = expand(file)) == NOSTR) return(1); printf("\"%s\" ", file); + } else if (file[0] == *(file + strlen(file) - 1)) { + char delim = file[0]; + char *endstr = file + strlen(file) - 1; + /* + * pipes are a special case... we want to remove any + * delimitting quotes, so we check for file[0] equal + * to '\'' or '"'; if it is, and the last character is + * the same, then we remove them. + */ + if (delim == '"' || delim == '\'') { + memmove (file, file+1, endstr - file); + file[strlen(file)] = 0; + } + } + fflush(stdout); ! if (dopipe) ! disp = "[Pipe]"; ! else if (access(file, 0) >= 0) disp = "[Appended]"; else disp = "[New file]"; ! if (dopipe) { ! if ((obuf = Popen(file, "w")) == NULL) { ! perror(NOSTR); ! return(1); ! } ! } else if ((obuf = Fopen(file, "a")) == NULL) { perror(NOSTR); return(1); } *************** *** 190,196 **** touch(mp); if (send(mp, obuf, ignore, NOSTR) < 0) { perror(file); ! Fclose(obuf); return(1); } if (mark) --- 221,227 ---- touch(mp); if (send(mp, obuf, ignore, NOSTR) < 0) { perror(file); ! (dopipe ? Pclose : Fclose)(obuf); return(1); } if (mark) *************** *** 199,205 **** fflush(obuf); if (ferror(obuf)) perror(file); ! Fclose(obuf); printf("%s\n", disp); return(0); } --- 230,236 ---- fflush(obuf); if (ferror(obuf)) perror(file); ! (dopipe ? Pclose : Fclose)(obuf); printf("%s\n", disp); return(0); } *** /usr/src/usr.bin/mail/cmdtab.c Sat Jun 12 07:50:29 1993 --- cmdtab.c Thu Jul 4 16:21:20 1996 *************** *** 53,58 **** --- 53,59 ---- extern int folders(), igfield(), Type(), retfield(), more(), More(); extern int saveigfield(), saveretfield(); extern int unread(); /* , Header(); */ + extern int pipeto(); struct cmd cmdtab[] = { "next", next, NDMLIST, 0, MMNDEL, *************** *** 82,87 **** --- 83,89 ---- "chdir", schdir, M|RAWLIST, 0, 1, "cd", schdir, M|RAWLIST, 0, 1, "save", save, STRLIST, 0, 0, + "|", pipeto, STRLIST, 0, 0, "source", source, M|RAWLIST, 1, 1, "set", set, M|RAWLIST, 0, 1000, "shell", dosh, I|NOLIST, 0, 0, From owner-freebsd-hackers Sat Jul 6 00:04:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24004 for hackers-outgoing; Sat, 6 Jul 1996 00:04:58 -0700 (PDT) Received: from Gatekeeper.lamb.net (root@Gatekeeper.Lamb.net [206.169.44.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23993 for ; Sat, 6 Jul 1996 00:04:56 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.lamb.net (8.7.5/8.7.3) id AAA01550 for hackers@freebsd.org; Sat, 6 Jul 1996 00:05:22 -0700 (PDT) From: "Ulf Zimmermann" Message-Id: <960706000521.ZM1548@Gatekeeper.Lamb.net> Date: Sat, 6 Jul 1996 00:05:21 -0700 X-Mailer: Z-Mail (4.0b.514 14may96) To: hackers@freebsd.org Subject: Question about Exabyte EXB-8505 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. Has anyone the specs for this drive ? it is not the -XL version. Ulf. -- --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 From owner-freebsd-hackers Sat Jul 6 00:21:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25464 for hackers-outgoing; Sat, 6 Jul 1996 00:21:34 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA25458 for ; Sat, 6 Jul 1996 00:21:32 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA04881 for ; Sat, 6 Jul 1996 09:21:25 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA05642 for freebsd-hackers@freebsd.org; Sat, 6 Jul 1996 09:21:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA04488 for freebsd-hackers@freebsd.org; Sat, 6 Jul 1996 08:55:03 +0200 (MET DST) From: J Wunsch Message-Id: <199607060655.IAA04488@uriah.heep.sax.de> Subject: Re: gcc lies? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sat, 6 Jul 1996 08:55:03 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607051011.MAA15302@allegro.lemis.de> from Greg Lehey at "Jul 5, 96 12:11:51 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > So I installed 2.7.2 as my standard compiler, and hey! suddenly I get > thousands of warnings from my kernel builds. For example, That has been reported before, e.g. by Peter Wemm. > ../../kern/kern_descrip.c:127: warning: comparison between signed and unsigned gcc 2.6 doesn't warn these (RTFM -- it does only warn comparision of unsigned > 0 or <= 0). Most (if not all) of your examples refer to the structure tag fd_nfiles which is declared `int', but continously used in an unsigned context. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jul 6 00:22:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25560 for hackers-outgoing; Sat, 6 Jul 1996 00:22:43 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA25546 for ; Sat, 6 Jul 1996 00:22:30 -0700 (PDT) Received: from helmholtz (helmholtz [198.202.70.34]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id AAA18851 for ; Sat, 6 Jul 1996 00:22:26 -0700 (PDT) Date: Sat, 6 Jul 1996 00:22:25 -0700 (PDT) From: Tom Bartol X-Sender: bartol@helmholtz To: hackers@freebsd.org Subject: Shared Memory Questions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello FreeBSD Hackers, I have a few questions regarding shared memory in FreeBSD. I've been using FreeBSD 2.1.0-release since it came out in November, 1995 and think is the best free unix for intels machines without a doubt. Many thanks to the FreeBSD team and hackers for your heroic contribution to the OS world! Now for my questions: I'm running an excellent image manipulation tool called "The Gimp" on a P5/133 with 64MB RAM and FreeBSD 2.1.0-release. This program makes extensive use of shared memory for iterprocess communication with external image manipulation modules called "plug-ins". These plug-ins are user customizable and give the gimp incredible power and potential. The documentation with the gimp talks about how most unix varieties have default shared memory parameters which are set too low to handle many of the things that the gimp needs to do, especially when you try to operate on large images. Sure enough, on my machine I run out of shared memory when I try to manipulate or load large images. ipcs -M gives me the following output: shminfo: shmmax: 4194304 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 32 (max number of shared memory identifiers) shmseg: 8 (max shared memory segments per process) shmall: 1024 (max amount of shared memory in pages) which I suppose is telling me that my max seg size is only ~4MB, and since the pagesize command tells me that a page is only 4096 bytes I can only allocate a total of 1024*4096 bytes in shared memory anyway! I've poked around in the kernel sources and FAQ's that come with 2.1.0-release and have found only one small FAQ regarding shared memory, namely that in addition to enabling shared memory with the SYSVSHM kernel config option there is an option called SHMMAXPGS which can be set thusly: options "SHMMAXPGS=64" The FAQ shows shared memory being set to 64 pages, or 256KB -- not quite big enough. The LINT kernel config file does not list this option. Upon further investigation I found a kernel source file called /usr/src/sys/conf/param.c which sets the default values for shmmax, shmmin, shmmni, shmseg, and shmall reported by the ipcs -M command as above. Setting SHMMAXPGS to 16384 gave me the expected result of increasing available shared memory to 64MB and I can now open large images but gimp now sometimes runs short on shmseg. I tried increasing this parameter by editing param.c directly and setting shmseg to a nice round figure of 128. The kernel this generated was unstable in that the ipcs -b command would sometimes seg fault and would report nonsense values for which shared memory segments were currently in use etc... I reduce shmseg to 16 which SEEMS to be working O.K. for now, though I still run out of segs in gimp from time to time, but I'd like to be able to choose and tune the shared memory parameters at will, and to do so with config options if possible. Or better yet, why can't the kernel just allow these resources to grow without bound until RAM and VM are exhausted? So, the bottom line is this -- can any of you give some advice on how to tune shared memory in FreeBSD? Are these numbers meant to be hard coded and un-tweekable? Can it be done at all? I really know next to nothing about shared memory and any help you can give would be greatly appreciated (virtual beers etc...) :) Thanx, Tom From owner-freebsd-hackers Sat Jul 6 00:28:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA26116 for hackers-outgoing; Sat, 6 Jul 1996 00:28:49 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA26088 for ; Sat, 6 Jul 1996 00:28:45 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id IAA20832; Sat, 6 Jul 1996 08:28:35 +0100 (BST) To: grog@lemis.de (Greg Lehey) cc: hackers@FreeBSD.ORG (FreeBSD Hackers) From: "Gary Palmer" Subject: Re: gcc lies? In-reply-to: Your message of "Fri, 05 Jul 1996 12:11:51 +0200." <199607051011.MAA15302@allegro.lemis.de> Date: Sat, 06 Jul 1996 08:28:34 +0100 Message-ID: <20829.836638114@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Lehey wrote in message ID <199607051011.MAA15302@allegro.lemis.de>: > ../../kern/kern_descrip.c: In function `getdtablesize': > ../../kern/kern_descrip.c:99: warning: unused parameter `uap' > ../../kern/kern_descrip.c: In function `dup2': > ../../kern/kern_descrip.c:127: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:130: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:136: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:139: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `dup': > ../../kern/kern_descrip.c:181: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `fcntl': > ../../kern/kern_descrip.c:213: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c:222: warning: comparison between signed and unsigned > ../../kern/kern_descrip.c: In function `close': > (that's not all, but it's enough). > If I compile the same module with the standard release gcc, I get no > warnings at all. How come? At first I thought it might be the header > files, but there's a -nostdinc in there, and I checked: it really does > include just the kernel header files. No, it's not GCC lies, the tightened up quite a bit on their parser and the error checking is a lot more thorough as a result. The end product: LINT has gone from about 100 warnings up to 4000. I'm going to be looking to kill a few of these once 2.1.5 is out and I have time. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sat Jul 6 00:57:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA29519 for hackers-outgoing; Sat, 6 Jul 1996 00:57:56 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA29495 for ; Sat, 6 Jul 1996 00:57:52 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id IAA21010; Sat, 6 Jul 1996 08:57:42 +0100 (BST) To: Tom Bartol cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Shared Memory Questions In-reply-to: Your message of "Sat, 06 Jul 1996 00:22:25 PDT." Date: Sat, 06 Jul 1996 08:57:42 +0100 Message-ID: <21008.836639862@palmer.demon.co.uk> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Bartol wrote in message ID : > segs in gimp from time to time, but I'd like to be able to choose and tune > the shared memory parameters at will, and to do so with config options if > possible. Or better yet, why can't the kernel just allow these > resources to grow without bound until RAM and VM are exhausted? If you read param.c: /* * Values in support of System V compatible shared memory. XXX */ #ifdef SYSVSHM #ifndef SHMMAX #define SHMMAX (SHMMAXPGS*NBPG) #endif [etc, etc] In other words, if you put an option in your kernel configuration file saying: options "SHMMAX=1024" (or whatever), then that'll over-ride the value calculated in param.c. This does allow you to specify the values at config-time, rather than hard-coding them. In answer to your second question, in /sys/i386/i386/machdep.c, kernel memory is pre-allocated during boot time to handle the SYS V IPC primitives (they need contiguous memory?). I'm also betting that the user-land applications would be mightily confused by dynamic memory areas. > So, the bottom line is this -- can any of you give some advice on how to > tune shared memory in FreeBSD? Are these numbers meant to be hard coded > and un-tweekable? Can it be done at all? I really know next to nothing > about shared memory and any help you can give would be greatly > appreciated (virtual beers etc...) :) Sorry, can't help with the virtual beers. I don't drink :-) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sat Jul 6 02:52:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA13976 for hackers-outgoing; Sat, 6 Jul 1996 02:52:13 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA13966 for ; Sat, 6 Jul 1996 02:52:05 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA07421; Sat, 6 Jul 1996 11:51:43 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA06461; Sat, 6 Jul 1996 11:51:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA09833; Sat, 6 Jul 1996 11:27:54 +0200 (MET DST) From: J Wunsch Message-Id: <199607060927.LAA09833@uriah.heep.sax.de> Subject: Re: Shared Memory Questions To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sat, 6 Jul 1996 11:27:53 +0200 (MET DST) Cc: bartol@salk.edu (Tom Bartol) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Tom Bartol at "Jul 6, 96 00:22:25 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tom Bartol wrote: > So, the bottom line is this -- can any of you give some advice on how to > tune shared memory in FreeBSD? Are these numbers meant to be hard coded > and un-tweekable? Can it be done at all? I really know next to nothing > about shared memory and any help you can give would be greatly > appreciated (virtual beers etc...) :) I'm afraid you've just qualified to become the most knowledgable person about FreeBSD's SysV shared mem implementation. :-) SysV shared mem seems not to be used that heavily these days. Now that you've already went this way, can't you go on and see *why* it is crashing? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jul 6 10:24:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24668 for hackers-outgoing; Sat, 6 Jul 1996 10:24:08 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA24638 for ; Sat, 6 Jul 1996 10:24:00 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA10798 for hackers@freebsd.org; Sat, 6 Jul 1996 13:22:33 -0400 From: Bill Paul Message-Id: <199607061722.NAA10798@skynet.ctr.columbia.edu> Subject: gdb and dynamic symbol information To: hackers@freebsd.org Date: Sat, 6 Jul 1996 13:22:32 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A while ago I discovered that gdb for the SunOS 4.1.x, Solaris 2.x (SPARC and x86, probably PPC too), IRIX 5.x targets can read dynamic symbol information from stripped binaries. (There may be other targets where this is possible; these are just the ones I know off the top of my head.) This is to say that if you have a dynamically linked binary that has been stripped, you can still run gdb on it and accomplish a fair amount of useful things. This is true even if the executable has _not_ been compiled with -g. This is especially useful when trying to track down problems with vendor software for which source is not available. (Ever binary-edit an executable to toggle on a hidden debug flag? :) My understanding is that gdb manages this little trick with Solaris and IRIX because both systems use the ELF executable format, which has a special section (.dynsym, I think) that is used for storing symbol information used by the runtime linker. (I don't know if gdb for Linux/ELF has the same capabilities since I don't have a system to test with. If someone knows one way or the other, I'd be interested to hear.) For SunOS 4.x, gdb has been taught to understand Sun's shared library hackery for a.out binaries. What I would like to know is what sort of work would be required to make our gdb do this for dynamically linked FreeBSD a.out executables. I tried looking through the gdb sources but I couldn't actually find the part that reads the SunOS dynamic symbol info. (While I dearly love gdb, I must confess that its sources make my brain itch.) Is our shared library implementation similar enough to SunOS's that we could reuse some of the same code? If so, does anyone know how to turn the feature on when building for an i386-freebsd target? Am I dreaming? -Bill PS: I don't suppose anyone out there has tried to make dbx from the 4.4BSD-Lite/Lite2 distribution work with FreeBSD, have they? (Gdb far outstripps dbx (pardon the pun) but it would still be fun to have it.) -- ============================================================================= -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 ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-hackers Sat Jul 6 10:35:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25156 for hackers-outgoing; Sat, 6 Jul 1996 10:35:42 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA25146 for ; Sat, 6 Jul 1996 10:35:36 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id TAA00102; Sat, 6 Jul 1996 19:15:29 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id SAA00433; Sat, 6 Jul 1996 18:27:19 +0200 (MET DST) Date: Sat, 6 Jul 1996 18:27:19 +0200 (MET DST) From: Andreas Klemm Reply-To: Andreas Klemm To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: How would you like the FreeBSD DOC CD presented/indexed? In-Reply-To: <18315.836593680@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Jul 1996, Jordan K. Hubbard wrote: > Anything else people would like to see on this CD, or ways in which > they'd like the news/mail indexed? Please speak up now! :-) If it's possible, I'd like to have the Berkeley BSD manuals on it. The manual stuff, that also can be ordered in manual/book form. Is there a copyright on it ... i don't know exactly. The BSD docu in source (troff) and PS form, so that it can be viewed with ghostscript. I'm not sure, but if I remember right it is located somewhere at Berkeley CS, but I lost the info, where exactly. I think, Terry's ideas are fine, hope you get the time ;-)) BTW: thanks, that you'll try to produce a better one. Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Sat Jul 6 14:15:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA05437 for hackers-outgoing; Sat, 6 Jul 1996 14:15:23 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA05421 for ; Sat, 6 Jul 1996 14:15:19 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id RAA21928; Sat, 6 Jul 1996 17:15:04 -0400 Date: Sat, 6 Jul 1996 17:15:04 -0400 Message-Id: <199607062115.RAA21928@kropotkin.gnu.ai.mit.edu> To: terry@lambert.org CC: kaveman@magna.com.au, terry@lambert.org, hackers@FreeBSD.ORG In-reply-to: <199607042255.PAA13790@phaeton.artisoft.com> (message from Terry Lambert on Thu, 4 Jul 1996 15:55:33 -0700 (MST)) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>> I don't think there is a problem with symlinking /etc/passwd; in >>> theory, it's not in use until after the mounts are done. >> Except when booting single user with an insecure console. :) > THere is no such thing as an insecure console, IMO. If they can > use a screwdriver to remove the hard drive, single user > non-password root access isn't a problem. Well, in the lab across the room from me, somebody can easily set up an insecure suid program in no time and not be noticed. But somebody is sure to notice through the glass walls the guy with a screwdriver and a maniacal look. This is the same idea behind encryption: make it hard enough to make it not worth the time spent to break root, for whatever reason. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Sat Jul 6 15:27:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA08077 for hackers-outgoing; Sat, 6 Jul 1996 15:27:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA08072 for ; Sat, 6 Jul 1996 15:27:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA18933; Sat, 6 Jul 1996 15:23:49 -0700 From: Terry Lambert Message-Id: <199607062223.PAA18933@phaeton.artisoft.com> Subject: Re: What is the best way to setup a drive To: joelh@gnu.ai.mit.edu Date: Sat, 6 Jul 1996 15:23:49 -0700 (MST) Cc: terry@lambert.org, kaveman@magna.com.au, hackers@FreeBSD.ORG In-Reply-To: <199607062115.RAA21928@kropotkin.gnu.ai.mit.edu> from "Joel Ray Holveck" at Jul 6, 96 05:15:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >>> I don't think there is a problem with symlinking /etc/passwd; in > >>> theory, it's not in use until after the mounts are done. > >> Except when booting single user with an insecure console. :) > > THere is no such thing as an insecure console, IMO. If they can > > use a screwdriver to remove the hard drive, single user > > non-password root access isn't a problem. > > Well, in the lab across the room from me, somebody can easily set up > an insecure suid program in no time and not be noticed. But somebody > is sure to notice through the glass walls the guy with a screwdriver > and a maniacal look. > > This is the same idea behind encryption: make it hard enough to make > it not worth the time spent to break root, for whatever reason. How obvious is rebooting from a floppy? Are all the power connectors, switches, etc. secured? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jul 6 17:03:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA12131 for hackers-outgoing; Sat, 6 Jul 1996 17:03:41 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA12125 for ; Sat, 6 Jul 1996 17:03:38 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id UAA22194; Sat, 6 Jul 1996 20:03:29 -0400 Date: Sat, 6 Jul 1996 20:03:29 -0400 Message-Id: <199607070003.UAA22194@kropotkin.gnu.ai.mit.edu> To: terry@lambert.org Sent-via: terry@lambert.org CC: terry@lambert.org, kaveman@magna.com.au, hackers@FreeBSD.ORG Sent-via: terry@lambert.org, kaveman@magna.com.au, hackers@FreeBSD.ORG In-reply-to: <199607062223.PAA18933@phaeton.artisoft.com> (message from Terry Lambert on Sat, 6 Jul 1996 15:23:49 -0700 (MST)) Subject: Re: What is the best way to setup a drive From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> I don't think there is a problem with symlinking /etc/passwd; >>>> Except when booting single user with an insecure console. :) >>> THere is no such thing as an insecure console, IMO. If they can >>> use a screwdriver to remove the hard drive, single user >>> non-password root access isn't a problem. >> Well, in the lab across the room from me, somebody can easily set >> up an insecure suid program in no time and not be noticed. But >> somebody is sure to notice through the glass walls the guy with a >> screwdriver and a maniacal look. > How obvious is rebooting from a floppy? Depends on whether or not a lock is sitting over the drive door, or whether or not a floppy drive is installed. > Are all the power connectors, switches, etc. secured? How that lab is set up is irrelevant. I think that the single user bit is a topic of concern. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu Fourth law of computing: Anything that can go wro .signature: segmentation violation -- core dumped From owner-freebsd-hackers Sat Jul 6 20:18:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA20764 for hackers-outgoing; Sat, 6 Jul 1996 20:18:25 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA20758 for ; Sat, 6 Jul 1996 20:18:21 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id DAA05111; Sun, 7 Jul 1996 03:18:09 GMT Date: Sun, 7 Jul 1996 12:18:09 +0900 (JST) From: Michael Hancock To: Joel Ray Holveck cc: hackers@freebsd.org Subject: Re: What is the best way to setup a drive In-Reply-To: <199607062115.RAA21928@kropotkin.gnu.ai.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Jul 1996, Joel Ray Holveck wrote: > This is the same idea behind encryption: make it hard enough to make > it not worth the time spent to break root, for whatever reason. Speaking of encryption, has anyone ported Matt Blaze's crypto-fs to FreeBSD? There is BSDI support. I think you can find the source at ftp.research.att.com. -mike From owner-freebsd-hackers Sat Jul 6 21:19:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23328 for hackers-outgoing; Sat, 6 Jul 1996 21:19:57 -0700 (PDT) Received: from ormail.intel.com (ormail.intel.com [134.134.248.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA23323 for ; Sat, 6 Jul 1996 21:19:55 -0700 (PDT) Received: from ichips.intel.com (ichips.intel.com [134.134.50.200]) by ormail.intel.com (8.7.4/8.7.3) with ESMTP id VAA17790; Sat, 6 Jul 1996 21:19:39 -0700 (PDT) Received: from incognito.intel.com by ichips.intel.com (8.7.4/jIII) id VAA00254; Sat, 6 Jul 1996 21:15:44 -0700 (PDT) Received: from loopback.jf.intel.com (loopback.jf.intel.com [127.0.0.1]) by incognito.intel.com (8.7.5/8.7.3) with SMTP id VAA10923; Sat, 6 Jul 1996 21:20:46 -0700 (PDT) Message-Id: <199607070420.VAA10923@incognito.intel.com> X-Authentication-Warning: incognito.intel.com: Host loopback.jf.intel.com [127.0.0.1] didn't use HELO protocol To: Bill Paul cc: hackers@freebsd.org Subject: Re: gdb and dynamic symbol information In-reply-to: Your message of "Sat, 06 Jul 1996 13:22:32 EDT." <199607061722.NAA10798@skynet.ctr.columbia.edu> Date: Sat, 06 Jul 1996 21:20:46 -0700 From: Mike Haertel Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What I would like to know is what sort of work would be required to >make our gdb do this for dynamically linked FreeBSD a.out executables. >I tried looking through the gdb sources but I couldn't actually find >the part that reads the SunOS dynamic symbol info. (While I dearly >love gdb, I must confess that its sources make my brain itch.) Is >our shared library implementation similar enough to SunOS's that we >could reuse some of the same code? If so, does anyone know how to >turn the feature on when building for an i386-freebsd target? Am >I dreaming? The part of gdb that reads the dynamic symbols is in the "BFD" library. Take a look at bfd/sunos.c in a standard gdb distribution. The gdb in FreeBSD's /usr/src probably doesn't have this file, although I haven't checked...